yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Q&A, Help & Troubleshooting] untouCh_68:
happened to me too!

exactly the same **** happened to me too :( i don't know what happened, i didn't root it or did anything to it. it just randomly turned itself off and didn't start up again. then suddenly it happened to load the battery again and i was able to boot it, but here the ****ed up part came... it showed me the samsung startup logo and everything but then weird green vertical stripes(like the matrix) appeared and nothing more happened. few reboots after, same problem as in the beginning, it's not starting up again. help me please
[Galaxy S III Mini Q&A, Help & Troubleshooting] sosznik:
Hello , I have installed Dmod V4 ROM and it's great but I wanted to install other emoticons by Xposed Framework like in this thread http://xdaforums.com/showthread.php?t=1574401 but when I install it and granted root permission Xposed Framework is not installed by clicking on install/update ...I have errors that there is no Xposed framework and have nothing in XposedBridge,jar (like --- )...and have rrors like can't create'/data/xposed/XposedBridge.jar newversion:Path does not exist...
[Galaxy S III Mini Q&A, Help & Troubleshooting] dariolob:
Just update your busybox through the market app "Busybox Installer" :)
[Galaxy S III Mini Q&A, Help & Troubleshooting] ZeussPL:
Hi, I have problems with xposed framework. Anyone can tell me, what is it? Illegal Instruction

Tapatalked from my HTC One SV using Tapatalk 4
[Galaxy S III Mini Q&A, Help & Troubleshooting] alexischino:
you have to push the xposed installer app in to the system apps.
[Galaxy S III Mini Q&A, Help & Troubleshooting] shouviksarkar92:
Xposed framework not updating

I am getting this errors while trying to update framework... Plz help... Its urgent...
[Galaxy S III Mini Q&A, Help & Troubleshooting] factorexh:
root acces? using dalvik?

Sent from my I8190 NovaFusion CM11
[Galaxy S 4 Q&A, Help & Troubleshooting] chalger:
Hi folks,

Having searched the forums I couldn't find an answer.

The problem I'm getting is when I get into download mode. I see the normal green android icon but at the top there is a grey caption saying: Write protection: Enabled.

I've been trying to flash twrp custom recovery but odin tries to do it and at the end it tells me success:0 failed:0.

That's all strange enough as previosly I managed to root the s4 using chainfire's Autoroot.

Could anyone tell me why is this happening and how to jump over it and install TWRP recovery.

//edit

I didn't check before I rooted the device but now I can't access stock recovery.

Cheers.

Ps. the device is: rooted i9505 running XXUAMDC stock rom, network: Three UK.
[Galaxy S 4 Q&A, Help & Troubleshooting] chalger:
Attached is a screenshot of what I mean.

Thank you.
[Galaxy S 4 Q&A, Help & Troubleshooting] jejb:
Didn't the TWRP site suggest using GooManager to install if you're rooted? Maybe give that a shot.
[Galaxy S 4 Q&A, Help & Troubleshooting] jongilluley:
My unbranded UK s4 also said write protection enabled however I've had no problem installing twrp recovery.

Flashed via odin after putting phone into download mode... Have twrp in pda and it's checked in the box next to it...
[Galaxy S 4 Q&A, Help & Troubleshooting] Obagleyfreer:
I have the same issue. I'm stock XXUAMDE with CF-ROOT.

I haven't tried to flash TWRP but I can't boot into stock recovery.

It says 'booting recovery' in blue but then just hangs.

Have you tried using Super SU app and unrooting?
[Galaxy S 4 Q&A, Help & Troubleshooting] chalger:
Ok.

I tried using GOOmanager, it cannot find suitable recovery for my device (which is strange as you may find it through TWRP web page).

When I choose in GOO to reboot to recovery it actually gets me to stock recovery (I still can NOT get into recovery using power+home+UP)

When i try to flash TWRP using (newly discovered via GOO) stock recovery it looks like that:

There is a broken android icon (see 1st attached file) and the text

-reboot system now

-apply update via ADB

[.....]

# MANUAL MODE #

Applying Multi-CSC

Applied the CSC-Code : H3G (btw H3G is my carrier, three UK)

Successfully applied multi-CSC

when I choose the recovery file to flash I'm getting response that E:\signature verification failed

Again

everything I've done with the phone was CFroot

, that is it. No custom rom etc or other playing with it.

//edit

I've got EXACTLY the same behaviour. I discovered GOO manager allowed me to boot into stock recovery.

Thanks for your interest.

chalger
[Galaxy S 4 Q&A, Help & Troubleshooting] thunderserpent:
If you're having problems check the thread here: http://xdaforums.com/showthread.php?t=2266336

It's the same method I used to root my phone and flash TWRP. (I too have write protection enabled)
[Galaxy S 4 Q&A, Help & Troubleshooting] AMDPOWERFIST:
write protection enabled means nothing

I have the exact same thing written on mine.

I have CF-Auto-Rooted mine AND TWRP 2.5 placed on mine, both using ODIN method.

No issues at all - both work perfectly fine.
[Galaxy S 4 Q&A, Help & Troubleshooting] jejb:
Try using just the Vol Up+Power. Once the phone vibrates, let go of the power but keep holding the up key until you see something appear on the screen. That works on my non-rooted phone to get into recovery.
[Galaxy S 4 Q&A, Help & Troubleshooting] chalger:
Hiya

Just for your information.

I've done factory reset, it preserved root access (which I found strange) and now I've managed to flash twrp recovery (which in my view is way too much touch sensitive :) )

Thanks for all the replies.
[Galaxy S 4 Q&A, Help & Troubleshooting] Anjamil:
problem rooting i9505

Hi All,

Just got my galaxy s4 i9505 with baseband XXUAME2. Have been trying to root this using CFROOT via odin numerous times but each time it fails. The error message includes "write operation failed" and "No PIT partion".

I have downloaded the correct PIT file and tried again but the same problem again.

I have further tried to flash pre-rooted firmware and another stock firmware but again - nothing I do seems to work.

Have tried the factory reset as well but again does not work.

Have tried flashing using motochopper method but also does not work.

Was hoping if someone could kindly extend his/her expertise - I am completely clueless at this point..:eek:
[Galaxy S 4 Q&A, Help & Troubleshooting] artnada:
Ok for those getting the following error using Odin,

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Removed!!

<ID:0/004> There is no PIT partition.

<OSM> All threads completed. (succeed 0 / failed 1)

I was getting the same errors whenever I tried to flash anything and couldn't figure out why. Now I seem to have sorted it.

Try this.

DO NOT HAVE ODIN OPEN YET

Stop KIES on your PC if it is on.

1) Put your phone into Download mode, (Home, Vol Down, Power at same time).

2) Connect your USB to PC/Laptop and phone.

3) Press UP on your phone.

4) now, open ODIN. <---only open AFTER your have pressed UP on your phone. COM and "Added" should be showing.

5) Flash what you need to flash.

(I noticed previously when I had Odin open, then pressed UP, it would show as "Added" and a Com would show, but I would ALWAYS get the Pit error and a Red FAIL)

I have now tried this method several times on the trot, flashed CWM with success, (where as it was always failing previously), and re-flashed other ROMS with success each time.

Hope this helps others.
[Galaxy S 4 Q&A, Help & Troubleshooting] Anjamil:
Still failing to flash anything usin odin

Hi i have tried the above. Same problem persists.

I do not have Kies on my pc. Have tried steps listed above as is but still no luck.

need help:eek:
[Galaxy S 4 Q&A, Help & Troubleshooting] indra9110:
Me too i have the same problem .. any other method to flash back to original fiemware ?

cheers

Indra
[Galaxy S 4 Q&A, Help & Troubleshooting] Anjamil:
problem solved

I used odin 1.85 and original usb cable that came in the

box. Problem solved am now able to flash all roms
[Galaxy S 4 Q&A, Help & Troubleshooting] _MirageX_:
I'm having exxcactly the same problem, but i can't boot the phone, it's just stuck on s4 screen, can someone help?

Thanks in advance.
[Galaxy S 4 Q&A, Help & Troubleshooting] cathpah:
Thanks for this. That solved my issue.
[Galaxy S 4 Q&A, Help & Troubleshooting] MrFuZZy92:
First time i tried to install a custom recovery on my S4 I9505 LTE. With Odin.. It didn't work..

I knew about heimdall.. And i gave that a try. And it worked perfectly. The one thing that's a bit weird.. After it first worked through heimdall. I could flash any custom recovery through Odin. But I think you should give heimdall a try..

Here is a link to how to install CWM on the cyanogenmod wiki: wiki.cyanogenmod.org/w/Install_CM_for_jfltexx#Installing_a_custom_recovery_on_Galaxy_S4_.28International_LTE.29 (I can't post links yet. So i just removed the http)
[Galaxy S 4 Q&A, Help & Troubleshooting] thanhsmr:
i flashed modern , and, it is fail, what wrong [/url][/IMG]

my phone have this entry : "write protection : enable"
[Galaxy S 4 Q&A, Help & Troubleshooting] tolas74:
on my phone is also 'write protected- enable' but odin and cwm work fine
[Android Q&A, Help & Troubleshooting] tryin:
Hi all, researcher and enthusiast,

I own a complete backup of all partition of the LG P990 with stock ICS, made it with nvflash with a command like this,

nvflash -r -read <-partition number-> my_partition.img

for all the partition listed in the partition table.

I guess that in someone of that raw image file, (outputted by nvflash), is located the entry system partition, (PartitionId=23 for the LG P990 ICS partition layout).

It's easy for every linux user to mount the raw image file, simply with 'mount' utility.

Browsing them we can find as already hypothesized the entrie android system partition!

If I copying in it the 'su' executable compiled for my platform, it could work?
[Android Q&A, Help & Troubleshooting] louiscypherbr:
Yes. Simple as that. Just be careful with permissions.

There's a topic I made on the ancient v28g time with stock v28g rooted system, on dev section. There you'll find useful info.

Do not say "thanks"; just press it under here.
[Android Q&A, Help & Troubleshooting] tryin:
Thanks! I'll have a close look to your work now, for others that consider this stuff interesting, louiscypherbr's work is here:

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

Nice job!
[Android Q&A, Help & Troubleshooting] tryin:
Ok louis, but the partition23 image file after adding su binary or other things is bigger than the previous that we had read with nvflash, right?

If I flash back it with

--bl fastboot.bin --download 23 image.img

how can this work..?

In the part table is write that have been reserved 536.870.912 bytes for the partiton 23, but we want flash an img file bigger than that size (because we added some stuff), this not causes problem?

And what do you mean for careful?
[Android Q&A, Help & Troubleshooting] louiscypherbr:
The extracted file is a dd partition image, meaning it's extracted byte by byte. So it includes the empty space, which you can see with "df" command after mounting it.

You can add files that fit in that position and it will be ok when flashed.

Do not say "thanks"; just press it under here.
[Android Q&A, Help & Troubleshooting] tryin:
Stupid thing! You're right!

And, what you mean for careful with perm?

The su binary should be have the setuid bit set in addition to the obvious x, is this enough?
[Android Q&A, Help & Troubleshooting] tryin:
Have you compiled su by yourself...?
[Android Q&A, Help & Troubleshooting] tryin:
Where have you found the executable of su packed in your v28g louis...???
[Android Q&A, Help & Troubleshooting] louiscypherbr:
Hey, sorry for being far from this.

What I was talking about permissions is that you should keep su permissions/owner. I did this just copying the su from a rooted Rom zip to /system/xbin and pasting inside your loop mounted /system with file manager (I'm kde fan, so I used dolphin, the kde graphical file manager, but you can use any other as well).
[Android Q&A, Help & Troubleshooting] Dexter_nlb:
I believe the latest Android releases somehow broke connection to Icade devices, and now they can no longer authenticate although you try and try to enter the 6 digit code.

I believe i found a workaround, at least because it works here now.

I think i got it working by pure luck here.

- install the Bluez IME from Play store

- enter the app and configure the bluetooth device by searching for the Icadecore (only one i tested)

- select IME (bluez ime) and activate your Bluez IME keyboard.

- try to connect with wrong code and let it fail.

- disable selected IME as keyboard and just use ordinary keyboard now.

- in regular android Settings, you will see the device is paired, and that you can configure it or connect to it. I tried to connect a few times using the white E2 button and after a few tries in got connected.

I believe the Bluez IME somehow makes the device authenticated in Bluetooth settings, and although it fails at native bluetooth connection a few times, it does connect after 3rd or 4th try.

if it still fails , re-enable the IME -> Bluez IME keyboard and when it connect try to type code, although it will fail. and then go back and deselect the IME and use internal keyboard. and then enable bluetooth in android settings and it should be connecting now after 3 or 4 tries and it always work the first time after this step. remember one of the white buttons awakens the devices and connect to android device

i can now connect without using the "Bluez IME" app.

hope it helps those trying to use it on Android4.2.2 (CM10.2)
[Android Q&A, Help & Troubleshooting] truehybridx:
I think i went through your motions right, couldnt get it to work :(

I was hoping my iCade Core could work with my nexus 7 so i could get controls working in a game I'm making, but for now looks like the controls will be iOS only *tear*

Nuxes 7 running 4.2.2

Thanks for your tips though I guess you're the lucky one :D
[Android Q&A, Help & Troubleshooting] kriegschluesser:
yes of good course:good::good:
[Android Q&A, Help & Troubleshooting] tecnoworld:
hello, I tried several times but I was unable to pair the device on my nexus 7 with 4.2.1 rooted :(

any hint?

I can pair it with my galaxy tab 2, but after this, under mame, it won't work even if I can map the keys! Why is that??
[Android Q&A, Help & Troubleshooting] franciscope10:
I reason I went through your motions right, couldn’t get it to work.:good:
[Android Q&A, Help & Troubleshooting] reycat:
Thanks a lot. I thought I couldn't make this work because in my Nexus 10 running 4.3, Bluez IME wasn't able to connect (I got differente errors regarding BT sockets). However, after trying to use Bluez IME, the iCade appears as already paired in Android Bluetooth settings. I had to try several times but finally it worked (I don't remember if touching "iCade" or the settings icon next to the name in the Bluetooth settings screen).

Off to play some Snow Bros now :)
[Android Q&A, Help & Troubleshooting] Dexter_nlb:
Just tested this under 4.4.2 and it still works fine with BluezIME just so you know.

Trick seems to be to select Icade in BluezIME as controller type, and to make it fail a few times when you select BluezIME as keyboard and code fails. then after some tries to connect the device appear as authenticated in Bluetooth devices and you no longer need BluesIME as previously explained.

Bug somewhere in bluetooth, but it is working after some combo's to connect in that app.
[Android Q&A, Help & Troubleshooting] tecnoworld:
For those that can use this method with success:

Would you please make a video of the whole process? And after the joystick is somewhat recognized, how do you enable it in, say, mame? Thanks!
[Android Q&A, Help & Troubleshooting] vanzan:
What do you mean when you say to select the BluezIME as keyboard and code fails? I can't get any response from the iCade let alone a failed code message. This is a nightmare. I purchased a HP Touchpad and installed CyanogenMod 9 thinking I saved a bundle on an iPad!

:Edit: I figured it out! You don't try to enter any code at all on the iCade. Open the BluezIME app and turn on Bluetooth. Then scan for the iCade and while it's scanning hold down the five buttons on the iCade to make it visible and select it. Then go down and enable and select BluezIME keyboard. With bluetooth still on keep selecting the BluezIME keyboard again and again. Then (again making sure bluetooth is on) select the Android keyboard. Eventually with a bit of messing you'll have a paired iCade.

The big Eureka moment for me was when I realise you didn't need to do the traditional process advised by the iCade's makers at all. You don't need to go pressing buttons and moving the joystick to enter any code at all.

When it's paired don't forget to enable it as an input device in its bluetooth settings. Also it needs to be enabled in Mame4Droid too! Happy days lads! :)
[Android Q&A, Help & Troubleshooting] EricBlade:
Hi all. Sorry to thread resurrect, but it looks like this one comes back every now and then as people figure out a method to make it work.

Here's what worked for me (HP TouchPad, using one of the early-ish CM9 betas, never bothered to upgrade):

Install BlueZ from Play Store. Install the BlueZ HID enabler thingee from the main android-bluez-ime repo over on google code (i can't link because i've hardly ever posted here)

Attempt to pair the iCade from the regular Android Bluetooth menu. When it asks me to enter the code on the iCade, I instead open BlueZ's menu, hit "Select device", then select the iCade. Then "Select Device Driver" and select iCade (HID). Then "Select IME", and select the BlueZ IME.

If it gives any errors, make sure the default IME is set to Default Android (otherwise BlueZ will repeatedly try to connect and fail and you won't be able to get the regular Android settings to try to pair), then go to the Android Bluetooth menu, set the iCade to pairing mode, select it in the Android bluetooth menu, when it asks to enter the code, flip back to BlueZ and hit Select IME and select the BlueZ IME. The connection works every time for me this way.

Then, I select my buttons in the main MAME keyboard settings. If you go this route, you are using BlueZ's IME, and you should NOT select the iCade option in MAME.

Of course, something that I discovered from randomly mashing buttons, is that it seems to be impossible in MAME's UI to actually -unset- buttons without possibly pairing an actual keyboard, or uninstalling the app and/or possibly the roms you want to reset, or something. Haven't figured it out yet, but I need to, because I really screwed up some keyboard settings.

Right now, this does seem to be getting some mixed results in some games that have 2 buttons seeming to always think that I'm pressing both buttons at the same time.. but I think that's because I screwed up my keyboard settings and can't figure out how to unset some of them.
[Android Q&A, Help & Troubleshooting] xbs:
Got it working a couple of times on the TF101 KitKat but now it doesn't work anymore. The ROM is the same as before, same version too. Bluez keeps reporting an error with bt socket. The icade works fine on the iPad. Is there a way to reset it or anything I can do? TIA
[Android Q&A, Help & Troubleshooting] Ace Grace:
Hi,

I've just bought an iCade for use with an nVidia Shield tablet and cannot get it to work at all. I have tried the suggestions a couple of posts above but I constantly get 'BT socket errors' when using Bluez IME.

I have tried it on the shield and a hudl2 which are both Lollipop.

The iCade must be working because I can enter the 6 digit pairing code using the controller and buttons to successfully pair it.

Has anyone got it working with Lollipop?

Regards
[Android Q&A, Help & Troubleshooting] ElKurgan:
My experience:

- Nexus 10 Tablet

- Ion iCade Core

Install BluezIme 1.20 and the HIDenabler.

Select your Icade in Bluezime and in driver: [iControliPad], I have not been able to make it work with [iCade (HID)] because it returns a connection failure [bt socket connect failed icade].

Select the IME Bluez IME.

In the bluetooth settings of your tablet select the iCade will try to appear between the synchronized items. Go back to the BluezIme menu and select the Gboard in IME.

Go back to the bluetooth settings of your tablet and select the iCade again and now it will connect.

The only problem I have is that the iCade does not disconnect automatically, I have to do it manually.
[Android Q&A, Help & Troubleshooting] ElKurgan:
1

2
[Android Q&A, Help & Troubleshooting] ElKurgan:
I have used an App, Bluetooth Auto Connect and it seems that the problem of always turning on the Icade has been solved. :eek:

Edit: In the end the auto disconnection works. I have chosen ICade (HID) again and the strength to insist at the end the bluetooth of the tablet has recognized it.
[MDA II, XDA II, 2060 ROM Development] VW_ELM:
Hya

I tried to downgrade my MDAII from the ROM 1.72 to ROM 1.66.

But after downgrading it, it looks like my MDA II is dead now...

It doesnt do anything anymore :(

Now I got a white screen with upper writing "SERIAL"

and down "V1.03" and no backlight at all...

Can somebody help/guide me how to fix my device?

I'm a newbee and need yoru help

Many thanks.
[MDA II, XDA II, 2060 ROM Development] philask:
'Serial' just means that its trying to communicate in Serial mode, if you drop it onto the dock/charger (assuming that is connected to your PC) the word 'Serial' should change to 'USB'. If it does then try the downgrade again.
[MDA II, XDA II, 2060 ROM Development] tadzio:
Don't worry, it's not dead. If the downgrade process completed normally, you just need to do a hard reset (press power button while holding stylus in reset hole). If this doesn't help, the downgrade failed.

The most likely reason is that you connected the cradle to a USB hub. Try connecting it directly to your PC, then perform the flash procedure again.

Another possibility is that you used Windows 95/98/ME. Some users have reported problems. Try the flash procedure from a Windows 2000/XP system again.

Hope this helps!

Daniel
[MDA II, XDA II, 2060 ROM Development] Wishy:
nope it doesn't work, i've got the same problem!

Don't know what to do...
[MDA II, XDA II, 2060 ROM Development] johnsonbaby:
Thanks tadzio: B4 l have same problem Rom failure , and l try to reinstall

again, flash Rom now :lol:
[MDA II, XDA II, 2060 ROM Development] ewdb:
I post a original latest belgian rom on this forum (rom from dangard), try to install this version.

http://xdaforums.com/viewtopic.php?t=8403&postdays=0&postorder=asc&start=75

you need to dowload this file (a shortcut) on your pc, then execute it following the procedure.

Bye
[MDA II, XDA II, 2060 ROM Development] axbl:
I solved the problem for me:

With HimaUpgradeUt.exe there was no connection. It was a too old version (0.5.0.0).

So I replaced it with Version 0.6.0.0 and it runs !!!
[AT&T Samsung Galaxy Note I717] redman9:
Hello wonderful, helpful people. Problem, need to send back old Gnote after "no sim card" errors and warranty replacement. I have used Odin to flash the stock ATT crapRom. Is boots into the ATT new phone set up so I know that worked. I have gone into recovery three times and wiped all data and reset. When I boot up phone and connect it to my desktop and open it...it still shows all the old folders. ALL of them, pics, app folders, CWM folders. everything. WTF? How do I wipe this mofo clean so I can return it? It's been a week now and I need to send it back TODAY.

Thanks guys...

K
[AT&T Samsung Galaxy Note I717] redman9:
OK I did factory reset from inside settings, not recovery, and that seems to have done it. I checked "myfiles" folder and Kies and nothing shows, and USB'd to desktop shows empty.

Sorry if I wasted anyone's time.

Do I need to wade thru the counter reset nowadays, or can I ship this thing?

It's going back thru warranty, for "no sim card" errors.

Gnote 1 i717