yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Q&A, Help & Troubleshooting] manekineko:
I was good when I first got my Tab, and followed all best practices, and made a Roto Backup of my Tab right after rooting.

I just tried to flash my Roto Restore back, and now my Tab is messed up. On startup, it will flash some corrupted graphics and static, play the Samsung sound and then sit on a black screen until it shuts off.

Fortunately, I still seem able to boot to download mode.

This is the procedure I followed to Roto Restore:

Then from a Linux system, I executed:

tar -cf mybackup.tar cache.rfs dbdata.rfs factoryfs.rfs modem.bin param.lfs zImage

Then I opened up Odin, connected in download mode, and flashed the tar as PDA, with all options default.

How do I fix my tab, and how do I restore my Roto Backup?
[Galaxy Tab Q&A, Help & Troubleshooting] manekineko:
Hmm in case anyone is able to help, now the situation is slightly worse. I realized I had a .pit file in my Roto Backup folder that I had not accounted for, so I flashed that again via Odin/download mode together with the .tar as PDA.

Now Odin seems to be hung doing nothing with this text:

<ID:0/005> Added!!

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Set PIT file..

<ID:0/005> DO NOT TURN OFF TARGET!!

It's been like this for about 15 minutes now with no activity.

Any advice on what to do?
[Galaxy Tab Q&A, Help & Troubleshooting] manekineko:
Is anyone able to help me?

After Odin sat there for 4 hours doing nothing, I finally closed it and turned off the Tab. Now I can no longer get to download mode, and whenever I turn it on, there's a picture of a cell phone and a picture of a computer with a yellow exclamation mark in between.
[Galaxy Tab Q&A, Help & Troubleshooting] manekineko:
Okay, final update for today, I found out from another thread that if you're lucky it's still in download mode even though it you get the dreaded yellow triangle.

I was lucky.

I used the fact that Odin could still flash it to reflash to Team Overcome's European stock safe ROM. Not exactly where I wanted to end up, but I'm just happy my Tab isn't a brick.

I'm a little scared to try and use my Roto Backup again, can anyone advise me on what the proper way to use this is without turning your Tab into a brick?
[Galaxy Tab Q&A, Help & Troubleshooting] rangercaptain:
If you are in download mode, just flash a JME or other froyo rom. You have to use a .pit file and check the repartition box.

Get your tab working, then work on getting it to stock.
[Galaxy Tab Q&A, Help & Troubleshooting] manekineko:
Yeah, it's working again now, I'm running Overcome's stock safe ROM which is JQ1 I believe.

How can I use my Roto Backup now to re-stock?
[Galaxy Tab Q&A, Help & Troubleshooting] rangercaptain:
Not until you flash a froyo rom first, like I already told you above, or you will get the crazy rainbows from messed up bootloaders.
[Galaxy Tab Q&A, Help & Troubleshooting] avishai0528:
so you say, flash stock rom froyo (lets say from samfirm)

use p1.pit (as it says in the site)

check the repartition

also to put the 'tar' (rom) file in pda and go?
[Galaxy Tab Q&A, Help & Troubleshooting] avishai0528:
after checking on my tab, that's a yes. :)
[Galaxy Tab Q&A, Help & Troubleshooting] rangercaptain:
When you get your froyo rom flashed, and you confirm everything works, you must do this next step:

Go find the chainfire bootloader patch. Froyo roms have bootloaders that can make your tab dead.

With the bootloader safely patched, then you are free to do anything.
[HTC Aria Q&A, Help & Troubleshooting] chaldeman1984:
So I'm running my aria on CM7-07282011-Nightly. I'm having battery issues, not battery-life issues, but general battery function issues. My stock battery died, then I bought two identical 1500mah batteries, which I have been charging with a standard Li-ion smart charger which I normally use for battery packs I build for various other projects. I just charge one battery while I use the other battery. Anyways the problem is that my phone's battery meter will never go over 80%. I boot up on a fully charged battery, and after two or three minutes have passed(when it first boots up it just shows the % it was at when I took the other battery out), the phone reads something like 74%.

I've thought maybe there was just a problem using two different batteries, so I tried charging one of these batteries in the phone and of course they stop a little above 70%, and sometimes the battery even drains while plugged into, well, any, of my 4 AC wall-plug type chargers or my computer.

I've tried wiping the battery stats, but it didn't do anything, and all the calibration methods I see say to charge until it's at 100%, which I can't get to...

I just wish there was a way to plug in an externally charged battery and reset the battery meter and force it to recognize whatever value is actually 100%....I've searched these forums and googled for two days and found no solution.

Does anyone know how I can fix this??
[HTC Aria Q&A, Help & Troubleshooting] jlayton15:
Try fixing permissions
[HTC Aria Q&A, Help & Troubleshooting] drumist:
I'm not sure if there is anything you can do about it. There's almost always going to be some quirks with third party batteries.
[HTC Aria Q&A, Help & Troubleshooting] Moh_Jay:
A tip is never get 3rd party batteries and the batteries we use love charging so charge whenever possible because if you let your battery die before charging waste builds up and leaves less space for charging.

Signatures are fancy.
[HTC Aria Q&A, Help & Troubleshooting] chaldeman1984:
well, the phone works as long as if the battery has been charged to 100%, so I just wondered if the was something I could do...
[HTC Aria Q&A, Help & Troubleshooting] chaldeman1984:
So even if the batteries work a long time when fully charged from my external charger, there is no way to fix the battery meter? If I continue using it normally would battery stats eventually callibrate? they are good batteries...just seems like a software problem to me :confused:
[HTC Aria Q&A, Help & Troubleshooting] cHarley04:
Where did you buy the batteries from, E-bay??? E-bay and other on-line markets are loaded with Chinese knock-off batteries & SD cards that are fakes and/or not to manufacturer spec products.

If that's what you have, you can't expect the phone to "fix" it.

Battery stats do take a few days to calibrate, but I believe it should still show 100% when charged, if you have a real battery and not something out of spec.
[HTC Aria Q&A, Help & Troubleshooting] chaldeman1984:
I don't know what the manufacturer specs are, but a fully charged battery reads 4.2v, well within standard Li-ion open-circuit values. There is nothing wrong with these batteries....
[HTC Aria Q&A, Help & Troubleshooting] tedkunich:
Problem is that the percent battery available is not determined my measuring the cell voltage, rather reading a value out of the fuel gauge built into the battery pack. Li-Ion batteries have a rather flat discharge profile then crater at the end, making the cell voltage an unreliable predictor/measure of battery capacity.

T
[HTC EVO 3D] texasez:
It will be a while before the custom roms are 100% stable so is there any advantage to the current root method or is it better to wait for the HTC to release their updates to the 3D?
[HTC EVO 3D] DDiaz007:
Root now... It'll only take like 10 minutes..

Also at the pace these Devs are operating at, ROMs will become stable fairly fast.

Like my help? Thank me :-)
[HTC EVO 3D] rockypr:
Only thing we have to wait for htc is to change the bootloader, nothing else...
[HTC EVO 3D] Compusmurf:
Considering all the current roms that are there are just modifications of the STOCK rom and devs haven't branched out much yet, those roms you're seeing are nearly as stable or more so than stock depending on which rom and how much change was done.

When the AOSP roms start hitting with no sense and most of the HTC stuff stripped out, then it gets interesting.

Now, to your original question, is it worth it to root now or wait for HTC. HTC has promised UNLOCKED bootloaders. Nobody is quite sure WHAT HTC will deliver. Unencrypted? S-OFF? Will they track or not? They will NOT provide you root. NOR is there any guarantee that the current methods of gaining root/s-off will work on that rom update if/when it comes.

I chose NOT to wait. I didn't want to end up like some of the EVO folks that took updates that can no longer root.
[HTC EVO 3D] Joey_UFC:
i wanna know why everyone thinks aosp will take forever to get stable. more then half the developers in the market all have 3vo's and Come on people, WE JUST GOT S OFF A MONTH EARLIER THEN HTC PROMISED US! give the guys credit.

I'm not saying the first batch of aosp roms will be 100% but it will not take long. soon as aosp hits the shelves things are going to be turning for the better.

By the time HTC gets off there asses and deliver we will all have cm7, miui, deck or whatever your preference is ALREADY on our phones.
[HTC EVO 3D] sonic41592:
I would go ahead and root. At least you can try out some new kernels and oc it.
[HTC EVO 3D] life64x:
Your gonna get unlocked with HTC but not rooted, why wait for something your going to do anyway?
[HTC EVO 3D] Drake9897:
um there is allways an advantage to getting s-off via the hacked way cause im shure htc will have some kind of stupid catch to s-off
[Captivate Q&A, Help & Troubleshooting] BlackSideburns:
I've searched a lot for this but most posts are very old and I'm searching for a more updated opinion. Is it possible to use the wiimote with the captivate for use with an emulator?
[Captivate Q&A, Help & Troubleshooting] speedy_11:
Yes with an aosp rom (cm7) can, but Samsung based rom can't has something to do with how Samsung setup Bluetooth stack
[Captivate Q&A, Help & Troubleshooting] BlackSideburns:
Do you think that the gingerbread update will change anything?
[Captivate Q&A, Help & Troubleshooting] speedy_11:
No, Samsung didn't change the Bluetooth stack in the sgs 2.3 update so they probably wont change in the captivate version.
[Sony Ericsson XPERIA X10 Mini] wwy1027:
hi all

my problem is ,when i reboot my cell or shut down ...always get into CWM ,whatever i tried to reboot again and again...till doesnt work well..
[Sony Ericsson XPERIA X10 Mini] Eyama:
Flash my hotfix v2 via Cwm recovery it is on page 14 and post 139 in FroyoBread thread ;)
[Sony Ericsson XPERIA X10 Mini] kormatoes:
Lisen to eyama and folow his instructions to the note a9d u will be fine if he helped hit his thanks button

;)
[Sony Ericsson XPERIA X10 Mini] Eyama:
@kormatoes thanks for supporting me hehe :)
[Sony Ericsson XPERIA X10 Mini] wwy1027:
i m doing it ..thx
[HTC Sensation] du1sbo:
Hello everyone, I am starting this thread to find if there are any Devs who can figure out on what is really wrong on the Sensation's speaker volume.

My experience during my HD2 days, I flashed different android roms with some low volume and some have high or loud volume. I think it had to do with the Rom. Is there any ways for the Devs who will make or currently making custom roms to take a look on this? Maybe there is an adjustment in the rom itself where you can override or adjust the overall volume of the speaker. Just a thought, thank you all more power.
[HTC Sensation] Pinepig:
Gave ya a thanks for asking this one in the hopes that a dev takes notice.

The external speaker volume ( or lack thereof ) is the only thing that chaps my ass about the Sensation.
[HTC Sensation] kripwalk:
You should try using Volume+ it solved my speaker problem
[HTC Sensation] Pinepig:
Using it now with the settings suggested in one of the posts around here, it's still pathetic ( almost as pathetic as my old ass ears ).
[HTC Sensation] cellsitetechstl:
voodoo sound and video is what the sensation needs combine that with OC/UV it will be insane
[HTC Sensation] daemonfly:
Great question, imho. Still have my HD2 (soon upgrading to Sens.), and I'm well aware of the volume level being all over the place with different roms. It seemed as if they weren't even aware, although with all the complaints I don't understand how.

Volume+ is a band-aid workaround, while the issue should just be fixed altogether. I doubt it's a hardware issue.
[HTC Sensation] trail1091:
Volume+ does works
[HTC Sensation] vegetaleb:
Did you try Equaliser or DSP Manager?

Boosting treble can increase the volume output
[HTC Sensation] chisleu:
midrange is most of the good volume. I think we have plenty of treble already. I boost +15 with a slight mid hump and it sounds great! :)
[HTC Sensation] Diesel73:
I got to play with an evo this past weekend and the volume on that phone is incredible. I'm hoping to get nearly the same levels from my sensation. Tried the market fixes with no real improvement. Thanks for bringing this issue up. The previous answers to the problem were either the market app fixes or wait till s-off. Now we have it....subscribed.
[HTC Sensation] CB620:
Volume+ and equalizer works, but it would be nice to have a volume hack like the Inspire built into the roms.
[HTC Sensation] du1sbo:
I agree with you all about the App market volume or any other, but would like a built in the Rom itself, permanent.
[HTC Sensation] secano:
We think alike.
[HTC Sensation] greengoldmello:
Mine is still a bit quiet even with volume +
[HTC Sensation] wchiri:
I'm also disappointed with volume on htc sensation. I've tried volume+ but it made no difference!
[HTC Sensation] Lucky Thirteen:
Interesting question. Following this post now.
[HTC Sensation] NYCguy2020:
Anybody knows if there is a working version of DSP manager for the Sensation??!
[HTC Sensation] lightforce:
Volume + added nothing for my sensation
[HTC Sensation] Huppen:
Same here.

Even tried to play with the echosettings and stuff, but nothing happened.
[HTC Sensation] vegetaleb:
Alas Volume+ is not compatible with all custom roms, Equaliser and DSP are...from my experience on DHD.

On N1 volume boost was included in Kernels

If the Sensation has the same speaker as N1 and DHD don't expect miracles, the trick is too boost treble to the maximum, it will make ringtones loud but it will kill the quality too.

The only 2 things that are refraining me to swap my sgs2 to Sensation are the speaker and death grip
[HTC Sensation] BigBoppa:
I think it is based on the source of custom rom.

In the EU we have restrictive limits to prevent people from damage :mad::mad::mad:

So htc might have implemented a software limit.

In old motorola KRZR days there was a table in the mobile to modify...
[HTC Sensation] kayroccs:
heres what.. the great news is there is a fix coming and it has to do with the custom kernel but at this moment devs are concentrating on fixing this camera flash issue with the kernel so it should be out pretty soon just have some patients
[HTC Sensation] dhies:
Tried Volume+ on my Sensation but it constantly force closed.
[HTC Sensation] du1sbo:
:) Kool I'm glad to hear that a FIX is coming about this low volume issue, Thanks for all the response and took a time to look on this problem. more power. :):):)
[HTC Sensation] tn6478:
camera flash issue has already been resolve with leedroid custom kernel.
[HTC Sensation] Rnapole:
Can u send me the link to get the volume Plus???
[HTC Sensation] Diesel73:
Its in the market. It doesn't do anything for our phones though. Save your time, volume + isn't worth it.
[HTC Sensation] shorty87:
I've been using Equalizer from the market and it makes a difference for me.
[HTC Sensation] TheEyes:
Any updates on this? The speakerphone volume on the Sensation is really awful; even worse, the microphone seems like it's too quiet when in speakerphone mode, such that people on the other end don't seem to be able to hear me. The odd thing is that music seems to play much louder on the phone's speaker than the maximum volume of the speakerphone. Even odder: the volume of the speakerphone is much louder when I call T-mobile's voicemail than when I call other people.

I've been hearing word that a fix is on the way, and T-mobile did send an OTA software update this afternoon, but the problem persists.
[HTC Sensation] du1sbo:
Bump.

Quick question, where is the software cap that HTC put to limit the volume of the speaker? is it inside the kernel? can it be adjusted so the volume on the sensation will be louder?
[HTC Sensation] du1sbo:
Bump.... any news about the Volume situation?
[HTC Sensation] Freaknik:
A temporary solution for ringtones and notifications until a fix is implemented. http://xdaforums.com/showthread.php?t=1302570
[Captivate Q&A, Help & Troubleshooting] Wally72:
I'm lookin for two very specific app's...

1. gmail but the app has clear background

2. facebook app but same "scenario"...background is black

I looked using google in my laptop but can't find neither.:( Can anybody poit me in the right direction so i can download those 2 app's? If u can help..."BIG UPS" to u my friend!!!
[Captivate Q&A, Help & Troubleshooting] speedy_11:
Your probably wont find them and more over their is little chance of finding them exactly the way you want. I've seen a few transparent background apps, but their out dated by now. You can do, by editing them yourself to get the apps the way you want.
[Captivate Q&A, Help & Troubleshooting] cappysw10:
^^^This^^^ would be your best bet as any update to these apps would need to be fixed.
[Captivate Q&A, Help & Troubleshooting] Wally72:
Thx...I do know I've seen both apps! I dont really care that much about the gmail one...but I really liked the fb one in black. Looks hot. I'll see if i can find it. Thx anyways guys!!!:rolleyes:
[Captivate Q&A, Help & Troubleshooting] Devo7v:
I was able to find the last version of Facebook with the black background here.

It also might be worth watching this and this forum for apps with black and transparent backgrounds. That's where I get most of mine from and if anybody knows of another source, please chime in.
[HTC Aria Q&A, Help & Troubleshooting] brswattt:
Does anybody have this .zip?
[HTC Aria Q&A, Help & Troubleshooting] themacman1000:
I'm just curious, what exactly is this Lakture you're requesting?

Sent from my mind using a HTC Intruder
[HTC Aria Q&A, Help & Troubleshooting] jasonyump:
i happen to have this zip on one of my externals around here somewhere. maybe ill look for it. BUT its not gonna come cheap
[Captivate Q&A, Help & Troubleshooting] tatro:
Resolved, delete please
[Xoom Q&A, Help & Troubleshooting] big flamingo:
I have followed the tutorial (http://xdaforums.com/showthread.php?t=1170760) after reading through it several times to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb

Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
[Xoom Q&A, Help & Troubleshooting] big flamingo:
follow-up

i have since uninstalled the "other device" instance, copied the superuser, su and rootboot to platform tools and re-tried, but no joy. tried with elevated admin privileges, etc., still no joy. next i will stand on one foot with a sparkler in my...ear and see how that goes. there must be a simple solution that i am too dense to see: check list 1-usb debugging on...check 2-necessary files Xoom USB drivers and Fastboot, boot (kernel) partition and Superuser.apk and su binary...check 3-Place rootboot.img, superuser.apk & su binary in the same place you will open your command window...check (hell, i put them all over and no place works)...check 4-read this bad boy cover to cover 3 times (http://xdaforums.com/showthread.php?t=879701)...check 5- open command window in 10 different places where the files above are...check 6-type in adb devices and get device returned...(loser klaxton sound)
[Xoom Q&A, Help & Troubleshooting] Legato Bluesummers:
I had the same problem. And also saw my Xoom as the MZ#. I just reinstalled the drivers. Worked fine after that. If all else Fails..try rebooting the pc first...sometimes dumb crap like that is all it takes. Once you see it in adb the rest is easy.

Took me awhile to get mine working. Had all the adnroid SDK stuff installed. And was in the c:\android-sdk-windows\platform-tools\ directory with all the files for rooting there while in command prompt. I thought I had the right drivers installed cause it could see my Xooms drives on USB. Guess not, cause once i Just reinstalled the drivers and unplugged and plugged back in the device and boom. I saw it connect. XD felt great to see that.
[Xoom Q&A, Help & Troubleshooting] mattiL:
I had the same problem as you, this is what I did:

1. Activate USB Debugging

2. Disconnect pad from computer

3. You need the Moto Drivers - Read this thread to START you - http://xdaforums.com/showthread.php?t=981578

4. Restart computer

5. Connect pad
[Xoom Q&A, Help & Troubleshooting] okantomi:
check out the "Idiot's Guide to Flashing..." in the Development section. http://xdaforums.com/showthread.php?t=1130996 Follow the steps there, except substitute the actual rooting section from the thread you quoted for the same portion (step #5), but also using the files in jase33's post--the Idiot's Guide was for rooting from HC3.1 and you are coming from 3.2.

Most important...you have to have the files you will be flashing through ADB (only img files, never zip files!) in your platform tools folder (sdk)...you can't just change directory. It sounds like you have a few issues going on at the same time, so I suggest you start over, get everything prepared in advance, run through your steps, then go for it.

On edit, I see you put all your files in one place...good.

Best of luck!
[Xoom Q&A, Help & Troubleshooting] big flamingo:
thanks to all

i have now attempted each of the methods above, but am having no luck getting adb to recognize my xoom. i have rebooted both laptop and xoom several times while uninstalling and reinstalling drivers, but still no listed adb devices. i feel it is something simple. i have installed everything you can download and install through sdk manager. i have no experience with sdk or adb so i don't know if i have too much or too little of whatever in there.

View attachment 673621

View attachment 673622

two captures, i don't know what to do about mz604. i can move files around and interact with the xoom from the laptop all i want, so maybe it is unimportant...maybe not?

to summarize: I WENT BACK (TWICE) and removed xoom and all sdk things rebooted and started anew. result: the same as originally posted. i am officially stumped and any help would be greatly appreciated.
[Xoom Q&A, Help & Troubleshooting] big flamingo:
problem solved

had to download 64 bit driver from motodev arcanely called handset drivers

View attachment 673634

thanks to all again and wish me luck as i hopefully end up with a rooted device
[Xoom Q&A, Help & Troubleshooting] okantomi:
Please keep us posted. Good luck!
[Xoom Q&A, Help & Troubleshooting] big flamingo:
another problem

i cannot chmod for some reason. this is what it says...

View attachment 673644

i retried because of the syntax error, but that didn't work either so i am holding right here until someone saves my bacon
[Xoom Q&A, Help & Troubleshooting] big flamingo:
solved

syntax error way earlier...all is well and rooted