yashsingh1/xdaforums huggingface dataset:
[One (M9) Q&A, Help & Troubleshooting] chemo713:
Thank you but my computer no longer reads my phone sd or even shows up . Recovery is no longer an option as it only shows a red triangle with a explation point in the middle . When i put adb devices nothing shows up or adb get-state show nothing at all . Only thing im able to do is sideload but when i try to it shows it not a signed software and abort update. I think i no longer have any rom just a build number shows up when i open up htc nero,
[One (M9) Q&A, Help & Troubleshooting] shivadow:
Send it to htc.
[One (M9) Q&A, Help & Troubleshooting] gregsarg:
What I mean is....take sd card out of your phone and place the file to it using a PC card adapter.

Once the file has been loaded to the card and renamed to OPJAIMG.zip....then put it back into your powered off phone and boot into your bootloader.....and see if the file will flash....g
[One (M9) Q&A, Help & Troubleshooting] chemo713:
it says E:failed to map file
[One (M9) Q&A, Help & Troubleshooting] gregsarg:
Ouch....

You may be sending that phone in for repair....g
[One (M9) Q&A, Help & Troubleshooting] Arthas92:
What did you do?

does your computer reconiges your phone in bootloader mode?
[One (M9) Q&A, Help & Troubleshooting] Aldo101t:
if you are using a card above 32gb it won't work, has tyo be 32gb or smaller(SDHC). 64gb is SDXC.

also you need to boot it into download mode for the phone to pick up the file. if it picks it up you will see an option to press volume up to continue
[One (M9) Q&A, Help & Troubleshooting] shivadow:
Not so sure of the entire truth in this. I'm using a 128gb card with no issues. The problem i have is my pc won't recognise it. Otherwise it works as it should.
[One (M9) Q&A, Help & Troubleshooting] Aldo101t:
remove the card from the phone and use an adapter and transfer the file to the card from your computer, if you think this is not true about the size of the card, then you can keep your phone in the state it's in now, up to you. I told you what Jesus told John, The Truth
[One (M9) Q&A, Help & Troubleshooting] Roobwz:
when youre in recovery mode, just hold the power button and press volume up once. Should get you into recovery

Skickat från min iPad med Tapatalk
[One (M9) Q&A, Help & Troubleshooting] chemo713:
yes but only show ruu version no htc sense or andriod version
[One (M9) Q&A, Help & Troubleshooting] shivadow:
I already stated that my pc cannot see the 128gb card.

How far can you get with the device?. Bootloader? (vol+ & power once), download mode? (vol- & power once) , does it even try?.

Is there any change on your pc when you plug the device into a usb on the motherboard while the device is in either download mode or bootloader? Any noise etc?

Remove htc sync but keep its drivers installed.
[One (M9) Q&A, Help & Troubleshooting] Aldo101t:
You don't have a card reader on your computer?

As I said before if you even get the Ruu on the sd card a 128gb the phone will not pick it up when you boot to download mode, you need 32gb or smaller

your saying after you remove the card from your phone, your computer won't see it? If so then your card reader needs a driver update.
[One (M9) Q&A, Help & Troubleshooting] chemo713:
will it work with a 128 sim card
[One (M9) Q&A, Help & Troubleshooting] shivadow:
Really.. He told you in the previous post that 128gb cards wont work. You can try it but a lot of people report that it isn't working on cards above 32gb.

Beamed in by telepathy.
[One (M9) Q&A, Help & Troubleshooting] jollywhitefoot:
That should be 0PJAIMG.zip (first character is ZERO, not the letter O).
[One (M9) Q&A, Help & Troubleshooting] chemo713:
Delete this post
[MTCB Android Head Units Q&A] Daemos:
I'm looking to purchasing a MTCB double din head unit, however, I've been reading about microphone issues even with external microphones. This requires hardware modification to fix for some models. However, I cannot determine if all units are like this, or only some. Please let me know!

Thanks!
[MTCB Android Head Units Q&A] dakkara303:
All the devices I have seen are basically the same and I think actuall built by the same people. They are just sold by many different vendors. So I don't think any of them are free from this problem. The repair itself is not too bad, a fine tip soldering iron really helps. But if anyone knows one without the problem I would be happy to be wrong!
[MTCB Android Head Units Q&A] carter.w.jason:
I have a Joying HU and have not done the mic mod or even hooked up the external mic. Using only the onboard mic, my android voice control works fine and BT calls work as expected. Friends say I sound fine and no echo issues on their end.
[MTCB Android Head Units Q&A] Geekybiker:
I too have a joying unit with no mic issues. I think there might have been a hardware revision recently. FWIW pumpkin is selling what looks to be a MTCB with a parrot bluetooth in it.
[MTCB Android Head Units Q&A] halloj:
I've the new Pumpkin and the microphones are still in parallel making the sound as bad as it use to be. No real improvement. Had to cut the wires

on the front one.

The thing is that they promise 24h response, but sine it's Chinese New Year the response time is 7 days.
[MTCB Android Head Units Q&A] gordonscicluna:
I have a joying and did not connect the external mic. Bluetooth works fine, I hear them and they hear me no problem. I had an Erisin with no external mic and had no problems either.
[MTCB Android Head Units Q&A] roscored1000:
I was just wondering which country people are in, I am in Australia so we drive on the right hand side of the car and the mic is on the left hand side of the units, therefore the mic is closer to the user [potentially] than us, maybe that is why it is clearer? just a thought bubble.
[MTCB Android Head Units Q&A] carter.w.jason:
LHD, wouldn't think RHD would effect it much, if any. Road noise and speech volume would have a greater effect.
[G3 Q&A, Help & Troubleshooting] akis75:
hi guys i have lg g3 d855 with 6.0 is there a way to root the phone? i think one click root not supported yet this android version. and a second question, is it possible to unlock bootloader with custom stock, no changes rom,kernel... thanks:)
[General Questions and Answers] Messerschmitt262:
Hi gang.

So I was planning on buying a battery bank, like the Aukey or Akon, they go for about 20-40$ depending on how big the battery bank is. However, I really would only use it if I am traveling out of the country, which is once every 2-3 years. It's for my Nexus 4 which struggles to go 1 full day of vacation while using he GPS and taking photos with it

However, I have a Tab 4 tablet, which I carry with me (movies in the ariplane) but don't really use it much otherwise. But I found out that I could use the tablet (or phone) to charge another android tablet/phone via a USB OTG.

So I was going to buy something like this:

http://www.amazon.com/Micro-USB-OTG-Adapter-Cable/dp/B00D8YZ2SA

But those kind of cables go from 2 to 5$.

Then found these:

http://www.ebay.ca/itm/Mini-Android...152408?hash=item542a132c18:g:sBEAAOSwstxVd1A~

They usually end up only costing 50c depending on the auction.

So my question would be, do those USB OTG from ebay work as intended (to at least charge my N4 from my Tab4)?
[General Questions and Answers] Messerschmitt262:
Anyone please?
[Verizon LG G3] ChivoLoko:
Hello and thank you in advace for your responses... I was flashing the Jasmine 9.0 to my vs 985 and after the reboot, the display just wouldn´t turn on... this is not the first time that I flash a rom on any of my phones... yet this is the first time something like this happens... my question is... that is it possible to mess up the display because of a malfunction (?) or for a possible corrupted rom? The phone seems to be turning off and on normally... because it does the sounds and when I plug it in the charger it does show the led charging the phone... I even tried to trigger the camera by holding the volume button and it sounds like its taking pictures.... i tried to plug it in my computer and it does the sound of being recognized but it doesnt show anything... any help would be much appreciated... thank you.
[Verizon LG G3] roirraW "edor" ehT:
Sounds like you need to put in Download mode (even if the display doesn't show anything - check in Windows Device Manager if it shows the phone in Download mode under the Modem section) and use LG Flash Tool 2014 to flash the 10B KDZ.

A common cause of this problem over the last six months is for someone to flash the 35B bootstack before JasmineROM 9 or SkyDragon 6. If you either flash the 24B bootstack before, or the 35B bootstack AFTER the ROM then it's fine.
[Nokia X] RoMinded:
i had found this rom from internet for y300

can somebody ported it to our phone??
[Nokia X] matrixex:
error
[Nokia X] akshaygalaxystarmod:
ill Help Guys Goo On Personal message Me Link
[Nokia X] nareach:
That is imposible.
[Nokia X] Deleted member 5892241:
Rom Development

Can I also Join :confused: I can Fix Bugs and also help you in porting ;)

PM me..:D:highfive:
[Nokia X] matrixex:
Nothing to show here
[Nokia X] Deleted member 5892241:
Yeah !! just post the link here

actually i cant find it for y300 :p

---------- Post added at 04:22 PM ---------- Previous post was at 03:51 PM ----------

I think there is one problem if the rom is not android based then it will not boot up as we have to make some more new partitions and make the firefox os.iso boot in those partitions and there is one guy tried dual boot on nokia x here are the results http://xdaforums.com/nokia-x/help/nokia-x-nokia-t3291656

thats the problem so finally i am thinking to port android based roms .. sorry for dissapointing you guys.

BTW if working as a team and want to port other roms i am still here to help
[Nexus 7 (2013) Q&A] Doctorimpossible:
Ever since I updated to 6.01 I've been having some extremely bad freezing issues. The whole device will freeze up at times and wont except any input from the touch screen. The buttons still work but the screen won't work at all, even if its rebooted or put into twrp. If I force a reboot while that is happening then the google splash that is displayed before the device starts booting often hangs there for a long period of time before continuing to boot. The only way that I've found to get out of it is to wait for a varying amount of time.

The other problem is that the orientation will occasionally freeze and won't change unless I reboot. After that it returns to normal.

Thank you for your time
[Nexus 7 (2013) Q&A] k23m:
As it freezes also in TWRP I'd suspect a hardware issue. Check internal connections and consider a new touch digitizer.
[Nexus 7 (2013) Q&A] Doctorimpossible:
But the strange part is that it comes back just by waiting a few minutes. If it was completely a hardware issue than wouldn't that not have happened?
[Nexus 7 (2013) Q&A] k23m:
I still vote for hardware issue but if you have any doubts then go back to v5.1.1 and let us know.

Wait, didn't you make a v5.1.1 TWRP backup? Just restore it.
[Nexus 7 (2013) Q&A] Doctorimpossible:
Thanks, I'll take a look at the hardware side. I don't have a backup for 5.1.1 sadly. I've been on 6.01 and just dealing with the issues for the last few months. I'm pretty sure I deleted my old backups already but I'll try flashing 5.1.1 stock to see if it makes a difference.
[Nexus 7 (2013) Q&A] mikengcm:
I have the same issue as yours. My Nexus 7 2013 32GB WiFi freezing at bootup screen as attcahed. Even I flash it with NRT 2.1.4 from ktu84p, lmy48t & mmb29q, it still freezing at bootup screen with the unlock icon. And I tried to flash the TWRP recovery, it is no response with any touch action.....

I can boot it into bootloader mode with the PWR and VOL- key.

How can I know is it the touch digitizer (that mean the hardware) problem? Thanks a lot!
[Nexus 7 (2013) Q&A] k23m:
Please clarify - can you boot TWRP and see the graphic TWRP screen?
[Nexus 7 (2013) Q&A] mikengcm:
Normally, I can't bootup to recovery (TWRP/CWM).

When I use the NRT to flash stock rom & unroot it, it running all the command without any error. But it can't bootup and freezing in the Google with lock screen in the previous message. Then I boot it into bootloader mode, and run 'Root and also flash Custom Recovery' in the NRT as attached jpg. It will boot into the TWRP, but it is no response for any touch action on screen as attached jpg2. :confused:

Thanks a lot!
[Nexus 7 (2013) Q&A] k23m:
Before we condemn the touch digitizer please run TWRP with a mouse on OTG adaptor. Note the attached picture. TWRP is fully controlled by a mouse, you can see the cursor.
[Nexus 7 (2013) Q&A] graphdarnell:
Once in TWRP you can just use a wireless mouse (the receiver might need an adapter -OTG cable). It happened once to me that the internal storage kept some residual files that messed up all flashing. But to wipe and format everything requires your touch to work since afterwards you'll need fimware on the OTG flash (internal storage completed erased).

If you use fastboot, check to see if it connects to your PC first. If it does, then you can wipe and format everything twice within TWRP; reboot to bootloader page; and flash by command lines, or use Nexus Tookit (skipsoft) to flash a stock or custom rom. Once done, boot it up and see if touch works again.

Failing that, you can tackle the hardware. Remove the back cover; disconnect the battery FIRST; remove and reseat the silver cable making it snug-fits at both ends. Then remove and reseat the two-pronged amber cable coming out of the touchscreen and connected to the lower board. Be gentle as the lock tabs might break. Use something flat to lift the locks slowly. Re-attach the battery LAST.

That's all you can do. If it still doesn't work, then we can discuss further. Touchscreens have been known to fail on their own in this model, but very rarely.
[Nexus 7 (2013) Q&A] mikengcm:
Thanks for your help! Sorry for my bad english!

I follow your 1st method, I can use the mouse to control in TWRP 2.8.7.0. I tried to factory reset my N7, it show 02 error......Then I wipe twice the all the options in 'Advanced Wipe' (see 04) and 'Format Data' twice time (see 06) successful respectively. And then I follow your 2nd method (using Skipsoft toolkit) to flash the kk4.4 stock rom.... my N7 still freeze on bootup screen (see 08).

And then I use the NRT to flash the TWRP 2.8.7.0 against, and I copy the TWRP 3.0.0.0.img into my N7. I boot to TWRP 2.8.7.0 recovery and flash the TWRP 3.0.0.0.img file into it and reboot to TWRP 3.0.0.0 recovery and once I tried to 'Format Data'... it show the 07 error on screen....

'flash_image /dev/block/platform/msm_sdcc.1/by-name/ metadata /dev/zero process ended with ERROR:255'

I can't goolge this error meaning.......And my N7's touch function still not working!!!

Finally, thanks for your help again very very much......
[Nexus 7 (2013) Q&A] graphdarnell:
Your freezing differs from the OP. He talked about touches being not registered, while yours is the tablet would not boot up past the initial Google Screen. Am I right? If this is the case, you need to be careful. Before you do anything, I'd suggest you go back to KitKat custom rom first because a lot have bricked their tablet trying to upgrade to Lollipop and newer official roms. Go back to older Bootloader if necessary before installing KK.

I have the feeling you're not familiar with the mechanics of what's being discussed. I apologize if I'm wrong but if not, it behooves to read this thread to get an idea. You don't need to wipe and format again with 3000 as it serves no purpose. 2870 had already done that. Remember that if you're not comfortable with fastboot uses, you're treading treacherous territory here, and the probability of inadvertently bricking the tablet is more than good. Once whatever software blocks writing to the internal storage, you're toast.

If you want to flash a custom rom to find out if anything in the software caused the freezing, you need to sideload as detailed in the above thread. Since you don't currently have an OS installed, you need to trick NRT to take you to TWRP (2.7.1.1) before you can sideload. Thereafter, it's automated.

Once you can boot again into Android, you can test touches. If the problem persists, the cause lies elsewhere. If it stops, you can upgrade back to TWRP 2870 or 3000.
[Nexus 7 (2013) Q&A] k23m:
Both Doctorimpossible & mikengcm explicitly reported no touch control in TWRP so let's see what the touch controller says.

boot TWRP

connect PC

run: adb shell dmesg > dmesg.txt

Copy dmesg here.
[Nexus 7 (2013) Q&A] Doctorimpossible:
Thank you for attempting to help me but strangely I haven't had that problem again since I posted. I used to have that problem daily when I was on 6.01 but when I somehow managed to get it to connect during flashboot and update it to the latest February update + flash the new Franko kernel + new exposed and root I haven't had that problem since.
[Nexus 7 (2013) Q&A] mikengcm:
I am very sorry if I post in wrong area/forum!

I tried to paste the dmesg.txt into Pastebin.com, I don't know I pasted it or not..

And I attached dmesg.txt also.

Thank you so so much!!
[Nexus 7 (2013) Q&A] k23m:
Your dmesg is SCREAMING about touch control errors: elan_ktf3k_ts_recv_data: i2c_master_recv error?!

ELAN is the touch controller IC.​

For start, reattach the silver cable on both ends.

If this does not help, then reattach cables going to TPCON1 and TPCON2 (the red chip is your ELAN).

Disconnect the black battery plug before doing anything.

---------- Post added at 10:07 ---------- Previous post was at 09:53 ----------

I wouldn't celebrate just yet, it was an intermittent issue, also confirmed by TWRP. If/when it happens again, grab a dmesg log and share it here.
[Nexus 7 (2013) Q&A] graphdarnell:
I don't know that the touchscreen mechanics function independently of the OS. The guy's tab has no OS right now. Where would it get the necessary firmware?
[Nexus 7 (2013) Q&A] k23m:
No worries, TWRP is his OS right now, with user interface and all necessary firmware.
[Nexus 7 (2013) Q&A] Doctorimpossible:
Ok so I did start celebrating too early. I left the house 3 hours ago and just came back to find it completely frozen. There was a sort of warning sign a few hours before where the screen would refuse to rotate like it did before. I grabbed the log http://pastebin.com/8hdhctin
[Nexus 7 (2013) Q&A] k23m:
But after rebooting everything was OK, right? So is the dmesg log.

The problem is intermittent and we need a log from TWRP when the touch screen does not respond.

Btw you have a Kingston :eek:

I see these in your dmesg

<7>[ 9.451599] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 120188
<7>[ 9.457580] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 358667
<7>[ 9.462524] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 223937
<7>[ 9.463195] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 223936
<7>[ 9.463348] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 223935
<7>[ 9.463470] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 223934
<7>[ 9.463592] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 223923
<7>[ 9.465148] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 390919
<7>[ 9.471221] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 366605
<7>[ 9.472015] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 390918
<7>[ 9.476715] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 138802

Probably an after-freeze mess.
[Nexus 7 (2013) Q&A] graphdarnell:
My question came from personal experience. Once I wiped and formatted everything and TWRP would not respond to touch but only to an attached mouse. As soon as I used fastboot to flash an OS, touch came back. Can you confirm that TWRP would allow touch without an OS? It's just too much for me right now to replicate.
[Nexus 7 (2013) Q&A] k23m:
Sure thing, and remember that mikengcm had an OS before and still no touch.

Also how else could you do the advanced total wipe if TWRP had to rely on some OS bits?
[Nexus 7 (2013) Q&A] Doctorimpossible:
No, after I rebooted I tried to enter the bootloader but that was completely frozen with nothing working at all. I couldn't hard restart it or use the volume keys to try and launch TWRP. I only managed to get into TWRP after it unfroze. How am I supposed to get to TWRP when it's frozen?

Thanks for the warning about Kingston. How bad is it? Like what effects will it have on my device?
[Nexus 7 (2013) Q&A] mikengcm:
Thanks for your help!

But I am not famous the tear down operation.

And I think I killed my Nexus 7 right now!! :angel:

Finally, thank you very much again. And I will find a shop to repair my N7 later.....
[Nexus 7 (2013) Q&A] graphdarnell:
The wipe command was issued before the OS was wiped; and this thing does have 2GB of ram, does it not?

---------- Post added at 08:30 PM ---------- Previous post was at 08:26 PM ----------

Slow down mate. All you need is a standing loupe of sort. A bit of patience. Reseat the cable, make sure they fit snugly before locking them, reconnect the battery and you're good to go. There's a white line across the cables. You know they're well positioned when the locks either align with, or barely overlap that white line.
[Nexus 7 (2013) Q&A] Doctorimpossible:
Ok, I got the log while the screen was frozen this time. http://pastebin.com/1fs28apZ
[Nexus 7 (2013) Q&A] k23m:
Separate the daughterboard

Excellent, note: elan-ktf3k 3-0010: [elan] elan_ktf3k_ts_set_power_source: i2c_master_send failed

ELAN, the touch controller is very unhappy ;)

Please make one more test. Disconnect the silver cable and just run it like that for a while. There will be no touch/usb of course but if you need to use it you can control it with a BT mouse/keyboard if you wish.

As you can see on my pictures, the motherboard does not care about separation with daughterboard :cool:
[Nexus 7 (2013) Q&A] k23m:
Oh dear, I was just explaining it the other day.

Your N7 problem has the following probabilities:

touch digitizer 60%

daughterboard 30%

cables 10%

The daughterboard is now useless but it could've been the problem in the first place!

---------- Post added at 10:52 ---------- Previous post was at 10:47 ----------

You don't need a "loupe" to see the socket being ripped out of the PCB. Case closed.
[Nexus 7 (2013) Q&A] Doctorimpossible:
What would I be checking for once I do that?
[Nexus 7 (2013) Q&A] k23m:
...for freeze-free operation.

See the extreme error flood from DB? When DB is disconnected AND MB is OK everything (except touch/usb) should work. This is only a confirmation test - or would you rather pay blindly for a new DB or touch digitizer?

Also, as it is intermittent, the probabilities are rather different:

cables 50%

touch digitizer 40%

daughterboard 10%
[Nexus 7 (2013) Q&A] Doctorimpossible:
Thanks, I just wasn't sure what I should be checking for. I'll give it a try after I get home tomorrow
[Nexus 7 (2013) Q&A] graphdarnell:
My bad, I didn't look closely at the thumbs. You're right. The whole connector was pulled off. How did the person manage to do that so cleanly? Now he really needs a loupe to solder it back.
[Nexus 7 (2013) Q&A] k23m:
Please don't keep us in suspense for so long ;)

What have you established?
[Nexus 7 (2013) Q&A] Doctorimpossible:
I haven't been able to figure out how to use the screen without the touchscreen since I don't have an otg cable. I've tried a couple different wireless mouses but I haven't been able to properly connect them. I'm in the process of researching my options and I'll let you know as soon as I get a definitive answer
[Nexus 7 (2013) Q&A] k23m:
OTG/USB is not an option, it can not work without the DaughterBoard - note my previous post. Try this test only:

fully recharge it

disconnect DB

boot TWRP

every hour wake up TWRP with any of the 3 buttons to see if it is

not frozen

conclude when battery runs down

Let us know...
[Nexus 7 (2013) Q&A] Doctorimpossible:
Sorry about that, I completely forgot about that. I'll give it a try when I get back then