yashsingh1/xdaforums huggingface dataset:
[MDA II, XDA II, 2060 ROM Development] cojones:
There follows a detailed account of my xda problems...

1. The xda is stuck in bootloader mode, the screen shows "Serial v1.01" in black text even after all (button pressing combinations of) hard resets.

2. When placed in the (mains powered, usb connected) cradle the screen shows "USB v1.01".

3. On running Himaupgradeut, and clicking next, i get the "checking the pocket pc..." message, after 30 seconds the XDA II turns itself off.

4. The confirmation screen appears on the PC after another 20 seconds or so with the upgrade and cancel buttons. No current device versions are displayed. As the xda has powered itself off the upgrade does not work.

5. On removing the xda from the cradle the xda shows "Serial v1.01" in black text on a red line background.

6. On replacing the xda in the cradle the xda shows "USB v1.01" in black text on a red line background. Retrying the upgrade procedure produces the same results.

I have also tried upgrading/flashing from the SD Card but get the error message ROM image is wrong size. I get no other error messages.
[MDA II, XDA II, 2060 ROM Development] tscshk:
I am not an expert, but I just recover my dead XDA II device last night. Maybe you needed to take care the following items. That I have over look.

1. Connect directly to the USB port and don't use USB hub.

2. Hard reset each time before upgrade again.

3. Make sure that Windows can detect the device as "Microsoft Sync......". In the web some people say it is not a must. But I found that I can upgrade my device only when the device is successfully detected.

Before successful recover the dead device. I always got communicate problem to Pocket PC.

Hopes my experience can help.
[MDA II, XDA II, 2060 ROM Development] blackfoot:
Hi Cojones, had exactly the same problem.

Follow the instructions from the previous poster (tscshk), not through usb hub, etc direct on motherboard. I also removed the usb connection, reset my PC, so it cleared all activesync/usb settings, device on the cradle, THEN connect to usb.

If you see the 'found new hardware/device...' dialog etc, then it should work. (mine did, twice! can't resist playing) :wink:

Also I downloaded the original Roms direct from the O2 site and used those to get back to 'standard'.

HTH
[MDA II, XDA II, 2060 ROM Development] cojones:
ah, thanks for your help everyone. I managed to get hold of an upgrade that didn't check country id and that did the trick. I now have my cherished xdaII back...hooray.
[Sony Xperia ZR] itandy:
I take no credit for this root method. It's completely the work of DoomLoRD and you can check out this thread here.

Please download the file and read the instructions from the original post since mirror is not allowed. Version v17 works just fine for our phone.

Remarks:

You need to change your phone to use Mass Storage Mode (MSC) instead of Media Transfer Mode (MTP) before you can successfully connect via ADB. Do this in Settings -> Xperia -> USB Connectivity -> USB connection mode.

You can download ADB driver here. During installation, select Xperia A driver, Flashmode Drivers and Fastboot Drivers.

After rooting my phone, I found that whenever I use Titanium Backup to uninstall a system app, my phone would reboot itself. If you're having the same issue, you need to apply the Remount-Reboot fix. Download it from this thread.
[Sony Xperia ZR] akash4357:
Installing ADB Drivers

This will help a lot!
[Sony Xperia ZR] djpeesh:
Superuser App instead of SuperSu

I've found that the Superuser app works better than the SuperSU app that installs on the ZR when using the rooting kit. To install the Superuser app, do the the following:

1. Go to the SuperSU app and click on options.

2. In the settings page, click the install another Superuser app.

3. Download Superuser [the chainsdd one] from play store

4. Once it installs, update the binaries and you're done.
[Sony Xperia ZR] hendriksan:
Do we need fastboot driver to flash ftf ROM?

I did mine last time with Z without installing any fastboot driver.

Just want to get confirmation before flashing my ZR

Also, I can't find the Xperia A driver on the list from flashtool-drivers file.
[Sony Xperia ZR] St_Ranger:
Fastboot driver need for flashing kernel only, i think.

In flashtool-0.9.11.0 it is present(driver for Xperia A)
[Sony Xperia ZR] hendriksan:
Thanks for pointing that out!

Just a bit confused with the above screenshot, since I only used flashtool in the past with my Z
[Sony Xperia ZR] itandy:
I've just updated the flashtool driver. The previous one was an old version without Xperia A driver.
[Sony Xperia ZR] 12345a:
Hi Itandy,

Just see your singnature for Root 4.2.2 of Xperia ZR, Could you pl. let me know that you have rooted Xperia ZR 4.2.2 in 10.3.1.A.0.244.

Also, pl. instruct how to do it, I have search through internet and Xda but could not find a correct methol to do it.

Thanks,
[Sony Xperia ZR] itandy:
Just follow instructions in this thread. It involves multiple steps but not that complicated if you understand them.

EDIT: If you've already upgraded to 4.2.2, then you need to downgrade back to 4.1.2 first.
[Sony Xperia ZR] nbnn:
xperia zr root

dear itandy

good day to you

first i ,d like to thank you for your reply.

2nd i did every thing but it showing c5503 not supported

this is the issue,

thanks

nabeel
[Sony Xperia ZR] itandy:
Where did you see the C5503 not supported message?
[Sony Xperia ZR] nbnn:
xperia zr root

Dear Itandy

thanks alot

file attached for my issue

thanks

nabeel
[Sony Xperia ZR] MrSpiceGuy:
Hi,

in order to this: http://xdaforums.com/showthread.php?t=2386405

Do someone have the old and the newest Kernel ftf files for the Xperia ZR?

Searched everywhere but couldn't find anything.

Thanks in advance

Chris
[Sony Xperia ZR] chewdaniel:
if u already have the firmware ftf file u can always extract the kernel.sin file using any file compression tool...
[Sony Xperia ZR] adryanodej:
doesen`t work that link for drivers .. pls upload somewhere else . thank you
[HTC Vivid, Raider, Velocity] forddent:
Wondering if I'm the only fella with this problem:

I recently flashed CM 10 (nightly build 2013-07-21) using TWRP (I'd originally used CWM, but it corrupted my internal SD card so I wiped everything and switched and that solved the problem). I'm s-on, so I manually flashed the kernal, went into TWRP, flashed the ROM, everything's hunky-dory. Used gapps-jb-20130301 (which is the most recent version), upgraded Talk to Hangout, everything's working fine.

Except I can't seem to get a dang video Hangout to work. Every time I try I get an error saying the network connection has timed out--and I'm on an AT&T Vivid, so no using the mobile network for me to see if it's just a wifi problem. I get kind of lousy signal here at my house, so I tried it at the office and at a friend's place, and got the same result.

So two questions:

1. Am I the only unfortunate sod having this problem?

2. Is there any way to fix it?

I really, really like CM 10 (it is seriously a revelation--this was my first foray into flashing my phone, and it's gone incredibly well--dang near a religious experience after the long dark of Sense), and it's currently stable and functional enough that I'd like to keep it if possible. Is this just Hangouts being weird, the Vivid being weird (from what I can tell that's a pretty common occurrence), or what?

Any help is appreciated.
[HTC Vivid, Raider, Velocity] bkman08:
If you are on CM 10 and not 10.1 and you are using those gapps, those gapps are for 4.2.2 and not 4.1.2.. and I'm pretty sure it is 20121011 or something like that if you need 4.1.2
[HTC Vivid, Raider, Velocity] forddent:
Sorry, I meant to say I'm using CM 10.1. I've installed the wrong gapps before and that just made everything crash all the time, forever (the keyboard in particular). Everything seems to work except for video calls on Hangouts.
[HTC Vivid, Raider, Velocity] p$ng:
I have the exact same problem now. Everything works perfect except every time when I tried to start the video/voice call on Hangout it timeout/crash. Really hope this to be fixed.
[Samsung Galaxy Nexus] NyPlaya513:
Hey guys so I tether once and a while when needed with my verizon gnex which works just fine with multiple devices like my laptop and nexus 7. I figured this was a piece of cake easy thing for my chromecast as well, but it appears I was wrong. I am currently on the kevdliu 4.3 rom which continues to allow my tethering ability but for some reason my chromecast cannot seem to work with it. Even if I do manage to connect to it which is rare, I cannot then access it from another device*nexus 7*. The cast button doesnt appear and when I then run the chromecast app it states that my chromecast isnt connected and tries to go through the connection process again.

So I know you are all about to say things like "maybe it wont work on the phone" or "this should go in the chromecast threads section" which for the second I almost did, but the interesting thing is my coworker with his galaxy s4 tethered just fine between my tablet and chromecast. He has tmobile and uses the official free one through them as he isnt rooted.

any suggestions?

edit, I am now seeing something interesting. It seems that although both my laptop and tablet appear to be connected to the tethering, if I started using my laptop first then the moment I picked up my tablet it then disconnects me from the internet on my laptop.
[Samsung Galaxy Nexus] droijo:
Have you figured anything out?

I currently am in the same situation too. I don't have a home wifi yet and use tethering for most of the things I do online.

I can't get anything to work whether trying to set it up from the phone or laptop.
[Nexus 4 Q&A, Help & Troubleshooting] dynamo147:
Hey guys so I am coming over from using a jailbroken iphone to now using a rooted nexus 4, which i found harder to do than jb an iphone (yeah ik i'm that bad)

And so here I am today I have my nexus 4 on the 4.2.2 update, no custom rom or kernel or anything, just super user access. And I really wanna start doing more such as the 4.3 update, custom roms and tweaks and such but before then I wanna make sure I got my back up down.

I rooted using the "Nexus 4 toolkit" and by choosing the one option does all option, which installed the twrp backup I believe.

Now I am super noob to android and i've already read the pinned guides for introduction to android and rooting but the rooting one was too complicated for me.

So I'm asking for easy 4th grade instruction for anyone who has the patience and time to help me accomplish these things

1. get onto 4.3

2. have backups for future use

3. be able to have a custom rom installed.

4. not end up with a new paper weight (like I did before when I first tried rooting, yes I'm that bad)

plz and thank you very much,
[Nexus 4 Q&A, Help & Troubleshooting] Tanmaynarang:
1. Download the Nexus 4 Toolkit which I'm assuming you already have since you rooted your phone.

2. Install a custom recovery, I recommend TWRP for ease of use and because its awesome (:D).

3. Download the 4.3 flashable zip from the Android Development forum and put it on your external storage.

4. Turn off your phone.

5. Hold down the power + vol down button til you get a screen which says start, and a bunch of scary looking things :P

6. Use the volume keys to scroll down to Recovery Mode

7. Click the power button

8. Once you're in TWRP, click Backup

9. Click start :P

10. It'll take a while, but once its finished, go back to the start screen of TWRP and click Install

11. Click wipe, then yes

12. Find the zip file of the 4.3 flashable you downloaded.

13. Click it :P

14. Wait a bit, and you have successfully installed Android 4.3!

Additional Info:

Regarding wanting to flash a custom ROM, do the same process you just did except with a custom rom zip rather than stock android.

If you ever want to restore, wipe then go to restore and select the backup you'd like to restore from

I hope this helped! :D
[Nexus 4 Q&A, Help & Troubleshooting] Droid2drummer:
Pretty good. I do believe they already have twrp. So just power off. Or download quick reboot app. Or ROM manager to reboot recovery if you Dont want to hold power and volume down till you get to fast boot. Or boot loader. But its all easy. With twrp you'll see you swype to engage. First thing when you get into your recovery is just click backup. Follow prompts. Rename or leave as date. I name mine virgin flash. Then back out to twrp opening again. Then wipe data factory reset wipe cache and dalvick cache. Then most cases no need to wipe system unless changing base. In this case of 4.3 I would. And returning I would. So just reboot once your backed up. So you can go download all your ****.

Gooim. App fave. Play store you'll find it. Then ROM toolbox. Then titanium backup. Then Franco kernel app. Then system tuner or system panel. Then kernel tweaking apps. All are up to you and optional. If your looking for something worthy to flash I like these.

Carbon. Liquid , and jelly beer. Also miui is the "Different ui" as most others will look identical. The ones I named can have themes in the chooser downloaded. Gives android its ui overhaul. Just enjoy ...
[Nexus 4 Q&A, Help & Troubleshooting] EddyOS:
OP:

Do NOT use toolkits. Take the time to learn how to do things manually. It will serve you so much better in the future than just pressing a button as you'll actually KNOW what's going on and how to fix any potential issues.

To everyone recommending the use of toolkits, shame on you
[Nexus 4 Q&A, Help & Troubleshooting] dynamo147:
Thanks for the input everyone gonna go down the list and try the instructions you guys have given and come back and tell you how it goes
[Nexus 4 Q&A, Help & Troubleshooting] sujith1994:
As you mentioned about nexus 4 toolkit just use it to relock the boot loader and then do a normal reboot

Now go to setting>>about phone>>system update there you will see that 4.3 update is available just do it now you should be in 4.3

Now follow this guide for rooting and stuff http://xdaforums.com/showthread.php?t=2384824

by following the guide u will be able to get root access in 4.3 and can be able to install a custom recovery

Using custom recovery u can flash a custom ROM NOTE:- FOLLOW THE INSTURCTION GIVEN BY THE DEVELOPER OF THE ROM IN THE THREAD

ITS SO SIMPLE THSN USING A CRAPPY IPHONE ;)
[Verizon Samsung Galaxy S 4] jdub251:
Can't seem to download it from Scotts site. Would someone happen to have it? Thanks.

Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] ZooDad:
As requested

http://db.tt/1EE2Mjnm

via TapaTalk on GS4
[Verizon Samsung Galaxy S 4] jdub251:
Thank you so much. :thumbup:

Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] narayangopal:
Hi,

I have been looking for making my xperia Ray bootable with two operating system i.e. (Multiboot Operating System) . I have heard one project Modaco.switch of making the dual booting in the HTC One and it is working on the Samsung Galaxy S4 in near future. Can we make something like this which is compatible with the Xperia devices. Although I'm not a kernel developer however I do make android apps and I have good experience on Java Programming. I would love to hear more about this features possibility from admin and users.

Thanks

Narayan
[Nexus 4 Q&A, Help & Troubleshooting] glancer2315:
so before i had my nexus 4 rooted, and now i just updated to 4.3 via OTA.

do i need to do the unlock and root thing all over again from the beginning, as I did with 4.2?

BTW, where is the "thank you" button people have been talking about, there are posts i really to "thank" but i never found the "thank you" button. i might being dumb but plz do tell me.
[Nexus 4 Q&A, Help & Troubleshooting] glancer2315:
actually i got a "fallen on the ground" Android while doing OTA. should i refer to any other upgrade method? or just choose wipe to factory reset?
[Nexus 4 Q&A, Help & Troubleshooting] Chrono_Tata:
Normally even with root, you can do an OTA update and it would be fine, but it seems that 4.3 has changed something and loads of people are having problems when doing OTA update while rooted. I would highly suggest doing a factory reset before updating to 4.3.
[Nexus 4 Q&A, Help & Troubleshooting] DecypherT:
Seems I'm in luck (except for losing root). Coming from rooted 4.2.2 I installed the OTA without errors.

My build is: JWR66V, I saw there also is another build.

Is there a problem with only one build?
[Nexus 4 Q&A, Help & Troubleshooting] glancer2315:
god my screen has been stuck with the big X for quite a long time. guess I need to do some bootload and wipe?
[Nexus 4 Q&A, Help & Troubleshooting] glancer2315:
omg it just keeps rebooting after every 10 minutes of use. damnit
[Nexus 4 Q&A, Help & Troubleshooting] Droid2drummer:
Wipe data. This happens.
[Nexus 4 Q&A, Help & Troubleshooting] Chrono_Tata:
Well there is only one OTA build I think. The other one you saw was probably the leaked 4.3 rom.
[Nexus 4 Q&A, Help & Troubleshooting] adkshirsagar:
Nexus 4 rendered in a hapless state

List of bugs:

Quick Settings has disappeared

No/incessant notifications

Voice calls automatically disconnected

Lock screen disabled

Home button function unresponsive

Screen timeout on launching applications

Search does not open in the browser

Power Off sans any other options

Sync fails

Abrupt disruption in Network connections

The problem was solved by a factory data reset with a Google Backup.

Anyone else faced similar issues?
[Nexus 4 Q&A, Help & Troubleshooting] Mercado_Negro:
Yes, go to recovery and do a full wipe.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] trinireddman:
Could someone mod stock 4.1.2 odex services.jar so that our default launcher stays in memory (and maybe crt on/off). Or can it be done as a xposed module? Was reading about it but i just couldn't do it.

thanks in advance
[Sony Xperia ZR] halfbloodmutant:
Any one got any flip case for zr like the samsung's? If you do the post a pic, price and link to the site please.
[Sony Xperia ZR] iamsuperuser:
Here is a flip case on eBay but I'm using a Silicone Case and i would recommend this to every zr user.

Flip cases are for big and broad phones, our XZR is a pocket-able phone .

A flip case would be not be so easy to use.

I request mods to move this topic to accessories section.
[Sony Xperia ZR] Konstigt:
Nillkin has one, check their homepage or ads on eBay.
[Sony Xperia ZR] halfbloodmutant:
Actually I want a flip case to protect the screen when the phone is in the pocket.
[Sony Xperia ZR] TK8:
How about using a scratchfree screen guard ?? that's way more comfortable..although it wont protect from breaking :good:
[HTC One S] OccupyDemonoid:
I am looking for a Stock T-Mobile Jelly Bean image that won't brick my phone. I tried searching for one, but I couldn't find anything or I found RUUs for outdated versions of HBoot. I am trying to revert back to stock, but I am sorta scared to do so with an outdated RUU. I have HBoot version 2.15 and Radio version 1.13.50.05.31. Thanks in advance.
[HTC One S] OccupyDemonoid:
Would this be the RUU I have to download? http://bugsylawson.com/files/file/1...531-10305008l-release-309489-signed-ics-2exe/

I would just prefer a nandroid backup of the stock image that I can just flash with CWM.

I downloaded the RUU, I just need to know if that is the correct one for my phone before I use it. I really don't want a bricked phone. I checked the MD5sum already and it matches, that is the only thing holding me back.
[HTC One S] tivofool:
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?

(didn't download from that site though)

http://xdaforums.com/showthread.php?t=2094414
[HTC One S] OccupyDemonoid:
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.

I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
[HTC One S] khan.orak:
If you are on TMOB US then it's for you. Furthermore, you can match thr CID of your phone to that in the RUU.exe --> Firmware.zip --> android-info.txt.

You'll have to extract firmware.zip from temporary files when you run RUU without connecting phone.
[HTC One S] OccupyDemonoid:
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
[HTC One S] khan.orak:
The RUU installs the Stock Recovery automatically. You don't have to do anything extra.

You can find stock recovery (if you want to keep it for any purpose) inside the RUU (extraction would require you to run the RUU and then extract the recovery from Temporary Files)

OR

you can find it in the forums.
[HTC One S] OccupyDemonoid:
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
[HTC One S] tivofool:
I believe that is the stock recovery. The red exclamation mark is telling you that you don't have access to it. Perfectly normal.
[HTC One S] DroidLuvver:
Can I also run this same RUU as quoted in this thread ?

I have the same radio but different hboot ...

SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?

VLE PVT SHIP S-ON RL

HBOOT-1.13.0000

RADIO-1-13.50.05.31

I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
[HTC One S] tivofool:
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
[HTC One S] DroidLuvver:
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
[HTC One S] tivofool:
It will install the newer hboot to 2.15
[HTC One S] DroidLuvver:
So I should be able to run the RUU with lower boot like mine and it will upgrade the boot to 2.15 -

Is it true that with 2.15 hboot, modifying the CID is not allowed ?

Any reason why I should stay with 1.13 HBOOT and not go to 2.15 Hboot? Meaning any disadvantages of upgrading to HBOOT 2.15 ?
[HTC One S] tivofool:
Well, say you updated your phone via ota & your cid is European or something. And all of the ruus for that CID are lower hboots. If u are s-on and and needed to ruu you wouldn't be able to.

But there is a guide to run a ota.zip for those people, so it isn't hopeless.

So not too many disadvantages.

In fact I just installed the newest Rom and firmware today. So my hboot is 2.16.

And the gossip is that update will be officially put out by HTC in a few weeks.
[HTC One S] real187:
Remember this.

if you want to go stock again in future (warranty purpose)

some providers have only provided an ota (only ruu with lower hboots) when upgrading to jb. So downgrading gets hard

It's not that easy to flash an ota as is a ruu.

If your s-off downgrading is no issue.

Verstuurd van mijn HTC One S met Tapatalk
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] wshealy:
Uncontrolable laughing is permitted in this area!!

For several days I have been cleaning up my BA.

I did a rebuild from the ground up with all the latest stuff

including updating my ext ROM.

Well while deleting unused programs I deleted CE4Arab since I don't speak Arabic. Next reset it is back. I delete it again.

In the mean time my unlock tools keep disappearing.

Well it turns out the unlock tools are in a reused cab internally named CE4Arab...Customization.

How do you keep me entertained for hours? Kind of like the sheet of paper that says "See other side" on both sides!

Bottom line I have uploaded a copy of the cab with the information updated if one of the lords of the ftp would move it over!