yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] sgeos:
Excellent... but this is not working. I can flash recovery, but I can't get into recovery. When I try to flash a stock ROM with Odin it fails on system.img because the partition is too small. Heimdall fails to "to initialise protocol". I only have access to Odin, fastboot and nvflash. No adb and the device is stuck on a boot loop. Am I simply out of luck?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] muzzy996:
What image are you trying to flash via Odin? Have you tried to go back to bone stock 3.1 (http://xdaforums.com/showthread.php?t=1342995) ?

How did you get into this situation, flashed an incorrect ROM? Seems odd to have partition size errors.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] sgeos:
I tried to install CyanogenMod for the SCH-i905, but it failed to install. ROM Manager recommended the wifi ROM. I installed that and it worked without sound. I figured if one wifi ROM works, another one should too, right? Big mistake. I flashed CleanROM and have been in a bootloop ever since.

I can flash with fastboot, nvflash and Odin, but all of them fail to flash system.img. I dumped the system partition and partition information with nvflash, and it appears to be 256M. The system.img is larger than 256M in all of the ROMs I have found that can be flashed with Odin. I'm pretty sure the system.img in EG01 is 312M, but I will download it again and try to reflash after recharging the unit. There is a custom ROM with a system.img that is less than 256M, but it appears that ROM can only be flashed via recovery and I can not get into recovery.

Unless something is totally wonky, it seems like I should be able to reflash *if* I can repartition. I know how big I want the partitions to be, but I do not know how to repartition the device. PIT files are nowhere to be found. (At this point I have backups of all but the user data partition.)
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] sgeos:
I downloaded EG01 yet again and tried to flash it. The recovery.img file flashes to SOS without issue. The system.img file fails to flash to APP. Odin fails with the following output:

<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

The following is displayed on the device:

WriteExt4Partition: Fail to OpenCompExt4![err:0xa]
DownloadPartition_odin: Fail to WriteExt4Partition![err:0xa]
Tegra_Nand_Write: Fail to DowloadPartition_odin![err:0xa]

A peek inside the tar file indicates the system.img is indeed a little over 312M. I think the flash is failing because the APP partition is only 256M. FWIW, the SOS partition is 5M and recovery.img is ~4.28M so a successful flash makes sense here.

$ tar -tvf PDA_HC31_EG01Ba_AP352081user_CP1033580_LTE20110704_0708.tar
-rwxr-xr-x 0 0 0 4485120 Jan 1 2009 recovery.img
-rwxr-xr-x 0 0 0 327200196 Jan 1 2009 system.img
-rwxr-xr-x 0 0 0 9376048 May 2 2011 cache.img
-rwxr-xr-x 0 0 0 16 May 2 2011 fusetrigger.bin
-rwxr-xr-x 0 0 0 10747904 Jun 24 2011 lte_modem.bin
-rwxr-xr-x 0 0 0 3962240 Jul 4 2011 modem.bin
-rwxr-xr-x 0 0 0 4051200 Jul 8 2011 boot.img
$

So far as I can tell, there are no tools that I can use to partition my device. I can not find any files to repartition my SCH-i905 with nvflash, Odin or fastboot. Am I simply out of luck? (Anyone who wants to help is free to PM me if that makes sense in this case.)
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] muzzy996:
Had a feeling that the wrong ROM was flashed at some point; ROM manager should not be used for these tabs. As you just found out, the structure of the different variants of the 10.1 is indeed different. I'm not sure how to fix the issue, hopefully someone can chime in who does.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] sgeos:
Twice, actually. ROM manager recommended CyanogenMod for the wifi tablet. It worked without sound, and I figured if one wifi ROM works they all should, right? Big mistake. I've been in a boot loop ever since flashing CleanROM.

These tablets are confusing at first, but this ordeal has taught me a lot. There should be a sticky post at the top of these forums warning people not to flash anything until they know the version of their device, and the model the ROM will run on. It should also warn about ROM manager and state "when in doubt do not flash anything".

My guess is that I could restore my tablet with nvflash dumps of a working partition table. Maybe parts 2 ~ 4 (BCT, PT, EBT)? I'm not sure what the GP1 partition is. I'm also not sure if partitions like MDM or LTE need to be intact for the tablet to run. I may have wiped something out with fastboot before I figured out how all of this works (this would be after getting stuck in a boot loop.).

If someone with a working SCH-i905 is willing to work with me, I should be able to restore my tablet. If anyone is feeling helpful, please PM me.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] DroidLX:
The link to the thread is not accurate

Hello - I know you were not trying to be an "A-hole" as i am not either. The link you provided is to a gingerbread root (3.2)... the original post stated ICS (4.04). So though you may not have been trying to be an A-Hole.... i think you may have made yourself look like one :confused: I am off to find out how to root my SGT 10.1 LTE (SCH-i905) running ICS 4.04 - If anyone has advice on where to find a How To, please let us know. Thank you -Bryan
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] muzzy996:
See here: http://xdaforums.com/showthread.php?t=1888755.

You DO NOT need to flash the first link in the original post of that thread but you should download superuser using the second link and clockwork mod recovery from droidbasement.com. It is best to disable auto restart in Odin when you flash CWM because the tab will boot into android and erase CWM if you don't catch the proper key presses quickly enough once Odin flashes, so uncheck that option and monitor Odin for a successful flash. Reboot into recovery and install superuser. Get busybox installer via the Play store and install busybox. At this point you can install a root checker from play store to verify root. You will have lost cwm at this first boot into stock ICS but root will have been installed and will remain on subsequent boots from this point on.

I did not try any other kernels to see if I could find one that would allow me to keep cwm so anyone looking to do that is on their own and does so at their own risk.

This is all I remember for stock ICS since once I had it I quickly went into CM9.
[HTC Rezound] SR3TLAW:
Odd issue. Seems like a degenerative disease almost. Ill plug my phone to charge overnight and when I wake in the morning it will have frozen with the orange LED illuminated. Screen wont turn on and the only way to reboot is to pull the battery. After booting up the battery appears it hasn't charged at all staying at the percentage when first plugging it in. Is this a charger issue? My only thought is the charger is pushing .7 amps rather than the 1 amp oem charger.

Any ideas?
[HTC Rezound] GrayBoltWolf:
Might have a battery issue.
[HTC Rezound] dottat:
What ROM are you running ?
[HTC Rezound] PhantasmRezound:
What kernel and any custom settings (governor, undervolt, sweep2wake, etc.) do you have as well.

Have had issues with sweep2wake freezing the screen to off before, that is the first thing to look at. Disable it or try another kernel if it is present.
[HTC Rezound] SR3TLAW:
No I'm running everything stock on Nils 3.6 as far as customization goes. 4G/data connection went in and out these past couple days too. Might be the battery you say? What are your thoughts?

Sent from my ADR6425LVW

Ts
[Desire HD Themes and Apps] nielshouten:
Hi all,

I've just signed up to let you know this:

I'm using Sabsa Prime V6.0 and discovered a graphical issue.

The buttons on the right of the dialer screen (wich appears when you have to typ your pin) are a little bit smaller then the others..

How to fix this? It's not the worst thing on earth of course but it would be nice to see it fixed!

Take a look at the attachment..
[Desire HD Themes and Apps] if4ct0r:
Hmm... Doesn't happen on mine. I'm on the same ROM.. Dialer looks fine.

Maybe its because you're on a different language?

Anyway, I hate to be the one to point this out but wrong section buddy. This thread should've been in the Q&A.

Edit: In anycase, a new version v6.5 is out with a fixed dialer. Flash that one over your current ROM and see if it fixes it.
[Desire HD Themes and Apps] narvinye:
He does not mean the phone dialer but the number screen that appears when you need to type your password to unlock your phone/screen. It happens to me as well and I'm on sabsa prime 6.5. I would like to see it fixed if it's even possible.

Sent from my HTC Desire HD
[Desire HD Themes and Apps] nielshouten:
Yes, that´s what I mean, but since I´m new here I´m not able to post this kind of 'graphic bug' in the official Sabsa Prime development thread :S
[Desire HD Themes and Apps] killersRquiet:
It haa been mentioned in the dev forum. Happens for me as well.
[Desire HD Themes and Apps] waelwa:
Try version 6.5 and perform a clean install , I use the same ROM and I don't have this issue
[Desire HD Themes and Apps] narvinye:
I'm using 6.5 and I did a clean install and have this graphical error.

Sent from my HTC Desire HD
[Desire HD Themes and Apps] JediDevil:
I´m using Version 6.5 and my dialer looks perfect.
[Desire HD Themes and Apps] narvinye:
If only you were paying attention when you looked the attached image. Look again it is not the dialer..

Sent from my HTC Desire HD
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Z_Black:
Let me preface this by saying I am a paying customer of the chameleon home screen and when I get home this evening I will be contacting the developer to see if I can obtain an apk to try and install on the fire HD.

I was mainly curious if someone else has tried this home screen / launcher replacement on the fire. The app itself I love, and it's getting better with additional widgets being added and also an api for other developers.

If I am able to get an apk to try and install, would I go about doing what most others have done with other launchers?

Set proper permissions for the apk

Move apk into system/app and reboot?

If it's more complicated than that, I'm going to give Nova a try using one of the other threads since I'm fairly novice with this stuff. I am however rooted.

Thanks!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] siafu:
I tried it, and it is easy to get working, just like you said, move, change permissions, and I did not need to reboot. After it was in system/app and proper permissions were set, I pressed the home button and I was prompted to pick which launcher to use.

I thought Chamelon looked good in it's adverts, but I was unable to get the widgets to look the way I wanted. I also had a problem with the weather widget. No location was found (even using wifi) and when I selected by zipcode it found my city but would not get the weather information.

I am sure it's user error, but I removed it and gave up for something else.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Z_Black:
Thanks for the reply! I haven't had a chance to try Chameleon yet, but still want to do so, hopefully this weekend. I did try Nova launcher and it just force closes any time I try to select it, but I am getting the choice between stock and Nova. Chameleon certainly has it's work ahead for it, but it's promising imo as long as more developers take to it to make some great widgets.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] no99sqrd:
ADW Launcher EX (paid version) works fine.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] alkemist80:
GO launcher EX works fine also in the system/apps folder.
[Android Q&A, Help & Troubleshooting] iLochie:
Hey guys, CoD Elite is a free app and I'd like the APK for it. Could someone please spare a few minutes and upload it for me? Much appreciated!

EDIT: Got it!
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] _Burst_:
Anyone have or know where I can get the odin file for the newest update?

I guess i could odin to lh2 and just accept the update or is flashing the stock recovery an option?
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] bert269:
LI3, you mean.

There is no LI8, it's LI3
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] _Burst_:
Oooops. GS3 fart.

Either way, I still want it. But it looks like I'll have to Odin LH2 then wait for the update. ;(
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] Z a p i x:
Um. You could just ODIN back to stock recovery and get the update. It comes in 2 flavors. Stock to LI3 at around 75mb I believe and LH2 to LI3 at 40mb. No need for LH2 to get it.
[Asus  Eee Pad Transformer Prime] litetaker:
Hi there,

It's been a long time since I posted anything on these forums. We all know that the TFP has several issues, starting from random reboots all the way up to poor I/O performance, WiFi (for some) and no GPS. Alright.

But among them all, on a day-to-day basis, 2-3 issues are really all that matter and they are - (1) I/O Performance, (2) random reboots (bigger deal than I/O) and (3)

a lesser known issue, which I faced on Stock ROMs primarily

, some screen glitches that happen at very high brightness and with a white background.

For now I want your feedback on 1 and 2. So far, I faced no random reboots but I did notice quite sluggish performance upon restoring apps from Titanium Backup. Also while downloading big apps or files from Appstore/browser, there seems to be a little sluggishness at some point. however I can't tell if it is better than before. Benchmarks also seem to suggest no big improvement in I/O performance.

So, please respond to the poll and if you wish leave comments explaining your opinion as well. Please keep things civil and let this not boil down to a ASUS bash festival! lol :angel: Personally, I am very happy overall with the update. I just feel it can be better, especially as Infinity pad got that I/O fix a while back (if I remember correctly).

Cheers, y'all! :)
[Asus  Eee Pad Transformer Prime] Theshawty:
Better I/O Performance, No random reboots.

Right now, it feels as if the I/O performance is as good as it can get, software wise. We must not forget that the NAND chip inside is of a questionable quality, a quality that makes me wonder if Asus imported from Chinese hoax-phones manufacturers.
[Asus  Eee Pad Transformer Prime] valentinrascu:
The problem si hardware. Jelly is bether but the emmc is the same.

Inviato dal mio Transformer Prime TF201 con Tapatalk 2
[Asus  Eee Pad Transformer Prime] Bugblatter:
I hadn't had random reboots in a long long time. With JB it's happening fairly often; seems to be when the screen turns off.

On ICS I had the screen set to only turn off when I turned it off, i.e. it would never sleep automatically. That could be why I didn't have the issue.

I've now set JB the same way so I'll see if it still reboots randomly.
[Asus  Eee Pad Transformer Prime] seeknom:
Are you using the dock with an SD card? There's a known issue related to it (the tf300 had it as well).
[Asus  Eee Pad Transformer Prime] mythoc:
we should petition asus to change our internal hardware a long time ago.. but jb sorted out many issues from software side anyway. Check development section for i/o data2sd thread.. makes prime a lot more stable and faster!

Tapatalked!
[Asus  Eee Pad Transformer Prime] TANIS8585:
Sadly after updating mine two days ago ive had nothing but problems from programs force closing to the power button not working all the time.

would almost believe that it's a hardware issue except it started literally right after the update.Can't even run Bad Piggies but for a few minutes before it starts to studder and then finally lock up.

Even my browser locks up now which before the update had only happened twice....thought this was supposed to be a update but instead i got a downgrade lol. Hope they work this out.
[Asus  Eee Pad Transformer Prime] mystril:
Do a factory reset after JB Update. There could be bugs ported to JB. My camera was disabled after JB update. Did a Factory reset, works much better.

I did mine and my Prime is now much faster. Strongly recommend.
[Asus  Eee Pad Transformer Prime] Bugblatter:
There was a card in the dock so that could have been the issue; thanks for the heads-up. Since I disabled sleeping I've not had a reboot.

I used to get frequent random reboots and pauses whenever I had a microSD inserted. My solution was to format it to NTFS. FAT and FAT32 were also ok but NTFS allows for bigger files. I think it was the default Ext4 format that caused the issue; can't remember for sure.

I mention it in case someone wants to try an NTFS-formatted SD card; it might avoid the problem while we wait for Asus to fix it.
[Asus  Eee Pad Transformer Prime] jamesey10:
I've had the Prime since December, and use it just about every day.

The JB update for me is just like all the other past updates. It's awesome at first, then I get ANR's. I even did the factory reset and after 2 days, the ANR's made their come back. My 2.5 year old Samsung Vibrant (Galaxy S) outperforms the Prime at browsing.
[Asus  Eee Pad Transformer Prime] JoeDaddy0710:
Would this issue be related to having a USB mouse plugged in to the dock and getting random reboots? I have a wireless Logitech mouse that I use when my prime is in the dock and since the JB update it always seems to reboot within a few minutes of having the mouse transmitter plugged in. I haven't see it reboot without the mouse transmitter plugged in while using the dock so I suspect that is the culprit. I tried a different wireless mouse (also Logitech) and I had the same results. I did not notice this issue with ICS.

Otherwise the JB update has been pretty solid. I did do a factor reset right after JB rollout because of some other glitches that were happening. I also haven't seen the screen tearing issue which was happening daily with the last ICS firmware.
[Asus  Eee Pad Transformer Prime] sorceror171:
Apparently this happened to the TF300, too. If you have something plugged into the dock - SD card and/or USB device - and the screen goes to sleep, on wakeup the thing is likely to reboot. One can hope ASUS plans an update to fix this...
[Asus  Eee Pad Transformer Prime] aznmode:
JB made it a little better but its still laggy and I still get ANRs but not as much as before. Having an Sd card in the dock also causes random reboots. I've done a factory reset and I'm no longer rooted and was never unlocked. As soon as I see a better tablet out this ones gonna have to go. Its been almost a year and so many updates. I really dont think any software will ever make this tablet any better...at least mine in particular.
[Asus  Eee Pad Transformer Prime] ThiaiZ:
Haven't seen 1 reboot on my prime since JB update 2 weeks ago. Have sdcard all the time in and a pen drive or external hard drive almost all the time.
[Asus  Eee Pad Transformer Prime] bjfrank:
I have only started to have random reboots since going to JB. It's good to know this could be caused by having an SD card in the dock. I really hope removing my SD card resolves the reboots. Other than this, I am very happy with the JB update and my prime is running better.
[Asus  Eee Pad Transformer Prime] litetaker:
It is great to know that a vast majority of you guys seem to have experienced fewer issues with JB than on ICS. I too have noticed that my tablet is working way better on JB, and there may be imperfections here and there, but that is the hardware's limitations. I am glad that the whole experience is soo much smoother especially in the areas I use it the most.

I look forward to kick ass ROMs with the latest Kernel. But though I am unlocked, I don't mind the stock ROM. It is good.. :D :good:
[Asus  Eee Pad Transformer Prime] ronski71:
Random reboots using 'any' device via USB in dock

Hi there,

since I updated my TF201 (TF Prime) to JB I have random reboots while using the USB mouse. I didn't try this before but when using another device via the USB port in the dock I immediately experience reboots. If I don't use the USB port it works like a charm, way smoother than ICS. But the ability to use devices via USB was an important reason to choose the TF201. Please ASUS / Android, fix this. I'm wondering if the other unfortunates among us have similar behaviour of their TF201 or other ASUS tablets.
[Asus  Eee Pad Transformer Prime] vt220:
USB devices work great for me, I use both the dock port and the adaptor to plug USB devices into the tablet itself. I did do a complete factory reset though, before and after installing JB.
[Asus  Eee Pad Transformer Prime] Rytkonen:
My Prime is rebooting too at least with my usb mouse and usb hard drive. It worked fine before JB. Did factory reset before and after update.
[Asus  Eee Pad Transformer Prime] Mancubus99:
Count me in as someone experiencing reboots after the update. Same scenario as everyone else. I get reboots when the screen shuts off with a mouse plugged in. Is there a fix for this yet?

Sent from my Galaxy Nexus
[Asus  Eee Pad Transformer Prime] funfair:
My IO has been a little better since JB. Though I still experience ANR's when browsing.

Random reboot increased! and the device seems to crash when Wifi is left on when in standby.

Next to that, my prime is starting to suffer new issues. One of them is the vibrate motor that's coming loose and the dock not beeing recoqnised after the tablet has gone into deep sleep. (at least, that's what I suspect). But these are hardware issues and not Jellybean's faule (I hope). The device is at asus RMA for the 3rd time now :(
[Asus  Eee Pad Transformer Prime] Subsonic44:
Are you unlocked?
[Asus  Eee Pad Transformer Prime] Mancubus99:
No, I'm on stock jellybean. I did perform a wipe after flashing.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mmk92:
So before my GNEX i used to own a Motorola Atrix 4G, so one time when i was flashing some img files through fastboot, by mistake i overwrote one of the img files that store the phone's stock touch calibration, so as soon as i turned on the phone i noticed that wherever i touched the screen, the reaction was as if i was touching the screen 2cm above, and to my surprise, even below the screen on the black frame there was also touch response for 2cm above.

So I concluded that the entire glass sheet over the display is capable of detecting touch input, but it is calibrated to take input only within the display itself.

This got me thinking, what if the GNEX's touch surface had the same property, what if we could recalibrate the area of the bottom frame and possibly map (back, home, and recents) buttons into them and get rid of the space consuming,burn-in inducing nav-bar.

Discuss
[Samsung Galaxy Nexus] crixley:
considering the led is housed there I really doubt it's possible
[Samsung Galaxy Nexus] jimmyco2008:
But maybe to the left and right of the LED... I like the idea, man, like the Palm Phones, we could just remember that left of LED is home and right of LED is back or long press Menu on left side for home, I dunno, but I like the idea!

Messing with my old thunderbolt, I can start flicking down the navbar before my finger makes it to the actual screen, it works just above it.
[Samsung Galaxy Nexus] mmk92:
Touch should work over the LED area because technically it is uniform over the entire touch surface.

I understand the logic of your conclusion, but think of it this way, the display is technically the same thing, its a display with the touch surface a few millimeters above it. The reason there's no touch response on the frame around the display is because the touch response is calibrated to respond within those perimeters.
[Samsung Galaxy Nexus] Citizen_Snips:
Cool idea. Any idea how to go about it?