yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] nicholas1520:
I've been using the nightly builds for sometime and the battery drain issue has gotten better than if you were to use the RC1.

You could Siyah kernel, with its own tweaks to give you better battery life. What I also do, I undervolt all the CPU steps and downclocked CPU to further save battery.
[Galaxy S II Q&A, Help & Troubleshooting] themadba:
Download the latest nightly and extract the kernel yourself. Not difficult, and this is the same advice given to you by GaboWinter on the RR FAQ thread.
[Galaxy S II Q&A, Help & Troubleshooting] Vink67:
For me CM9 nighly + siyah 3.3.3 do a huge battery drain and overheating....
[Galaxy S II Q&A, Help & Troubleshooting] feden84:
Vink67 how would you use both kernels siyah and cm9 at the same time?
[Galaxy S II Q&A, Help & Troubleshooting] Immortalis:
No no he's running CM9 ROM and Siyah Kernel. You misunderstood his post.
[Galaxy S II Q&A, Help & Troubleshooting] feden84:
I see. But I don t want to install another rom. Just wanna flash a new kernel. Can I? Is it from the link on the post above?
[Galaxy S II Q&A, Help & Troubleshooting] Immortalis:
Sure, you can. Just visit this thread, choose your kernel, download .zip and flash via CWMR :D

Link above contains CM9 zips.
[Galaxy S II Q&A, Help & Troubleshooting] feden84:
So what s the difference between cm9 kernel from this last post and the cm9 kernels on the link from the post above?

Thanks
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] pofadda:
I have asked this in Q&A but no replies as yet...Does anyone know what the line in Odin, after the START!!! has been displayed:

<1> e - big partition size!! '

means, please?

All the usual stuff has been complied with (cooper, drivers, firmware - tried

'S5830XWKS3_S5830XWKS2_S5830VIRKP1_HOME.tar.md5',

S5830XWKT5_S5830HTSKT2_S5830NEKT2_HOME.tar.md5;

S5830XWKT7_S5830XWKT3_S5830OXFKT1_HOME.tar.md5,

latest Odin, no running Kies)
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] panpjp:
It means the file is big, but it will go as normal.
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] junpeikawada:
I guess the directory where you put your odin and frimware is too complexed. try relocating your file in a major directory, like on C:\, and dont put spaces and special characters on files so that odin does not have a hard time locating your file.
[Desire HD General] smanfly:
Hello.

i am searching for a stock rom for desire hd, rooted if possible.

i have surfed the internet and forum and found nothing... just some broken links.

thank you.
[Desire HD General] soleil10:
If you want a rooted ROM, why not this one:

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

If you try to find a stock ROM, check here:

http://xdaforums.com/showthread.php?t=1335027
[Desire HD General] lrm537:
This is the latest stock ROM. And it is rooted.

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

And here's a list of stock RUU. Not rooted

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

This link is the same as in above post
[Motorola Droid RAZR] njmeyers83:
The title gets to the point. I'm after the google now with working voice. I have a solid JB Rom for the Nexus. Any way to port? I prefer aosp.
[Motorola Droid RAZR] jkat797:
+1...anyone know of jellybean getting ported over to our razrs?
[Motorola Droid RAZR] Newbieshwa:
I assume that porting it will be difficult with a locked bootloader...but what do I know?
[Motorola Droid RAZR] hihipunkt:
Top right corner! Search Box!

http://xdaforums.com/showthread.php?t=1764065
[Droid X General] mallard6453:
I am currently running CyanogenMod 9.000-RC0-shadow KANG on my Droid X. I would like to go back to stock because it is being handed down to my wife. What is the easiest way to accomplish this? Thanks in advance.
[Droid X General] SomeDooD123:
I'm in a similar situation! Anyone know the right way to do so?
[Droid X General] infazzdar:
Please ask questions in the general section, thanks =P

You need only SBF to .602. Google can help you with finding the needed tools and files, as well as plenty of guides.
[Droid X General] Archer:
As stated above, questions should not be asked in Development forums.

Thread moved.
[Sprint HTC EVO 4G LTE] MikeC84:
I was wondering if someone can pull their config file? I don't have the phone yet but already starting on a kernel.. Only thing is I need the confi file from a working phone.

Post the config file here.

First one pulls the config the other gives us the config. Thanks guys

./adb pull /proc/config.gz

gunzip config.gz
[Sprint HTC EVO 4G LTE] david279:
Gimmie a sec...

EDIT: Here you go.

https://docs.google.com/open?id=0Byr5K8BpE_yQMlFnVWROd0wtQ2c

Sent from my EVO 4G LTE

---------- Post added at 07:37 PM ---------- Previous post was at 07:33 PM ----------

You kernel building?
[Sprint HTC EVO 4G LTE] MikeC84:
Yup :D Might need some testers till I get the phone. Waiting for the white one and still saving up..
[Sprint HTC EVO 4G LTE] david279:
Cool. I've been able to build but i don't know how to get it into a boot.img so i can boot it. Im a noob at that part.
[Sprint HTC EVO 4G LTE] MikeC84:
I need the emmc partition info so I know what block to use for flashing. I have to go pick up the old lady so if someone can find a link for me till I get one that would be nice.

I already have a build kernel with lulzactive governor :D
[Sprint HTC EVO 4G LTE] david279:
cat /proc/partitions?

Sent from my EVO 4G LTE
[Sprint HTC EVO 4G LTE] MikeC84:
Yea try it.

I need the system and boot.img block names
[Sprint HTC EVO 4G LTE] david279:
app_198@android:/ $ cat /proc/partitions

major minor #blocks name

179 0 15267840 mmcblk0

179 1 128 mmcblk0p1

179 2 256 mmcblk0p2

179 3 130671 mmcblk0p3

179 4 1 mmcblk0p4

179 5 16 mmcblk0p5

179 6 256 mmcblk0p6

179 7 15577 mmcblk0p7

179 8 256 mmcblk0p8

179 9 1024 mmcblk0p9

179 10 256 mmcblk0p10

179 11 2048 mmcblk0p11

179 12 1024 mmcblk0p12

179 13 32 mmcblk0p13

179 14 6144 mmcblk0p14

179 15 1024 mmcblk0p15

179 16 1024 mmcblk0p16

179 17 46080 mmcblk0p17

179 18 10240 mmcblk0p18

179 19 5120 mmcblk0p19

179 20 8190 mmcblk0p20

179 21 16384 mmcblk0p21

179 22 16383 mmcblk0p22

179 23 1022 mmcblk0p23

179 24 4096 mmcblk0p24

179 25 4096 mmcblk0p25

179 26 20480 mmcblk0p26

179 27 4 mmcblk0p27

179 28 256 mmcblk0p28

179 29 16 mmcblk0p29

179 30 1280 mmcblk0p30

179 31 64 mmcblk0p31

179 32 256 mmcblk0p32

179 33 256 mmcblk0p33

179 34 99239 mmcblk0p34

179 35 1277951 mmcblk0p35

179 36 229375 mmcblk0p36

179 37 2260991 mmcblk0p37

179 38 10418176 mmcblk0p38

179 64 30657536 mmcblk1

179 65 30653440 mmcblk1p1

Mount output

https://docs.google.com/document/d/1moR9C9iOpFTvZXGEH8s9bnBtexyQ3VPO4Yl1RU8WyQ8/edit

Sent from my EVO 4G LTE
[Sprint HTC EVO 4G LTE] MikeC84:
Thanks that helps now I need toknow which one of those is the system and which one is boot.img

I'll see if I can find another way to grab em..
[Sprint HTC EVO 4G LTE] david279:
CHeck the link i added to the post above
[Sprint HTC EVO 4G LTE] MikeC84:
Boot img not in there. Try partition table from Google play.

Try this too

cat /proc/mtd
[Sprint HTC EVO 4G LTE] david279:
cat /proc/mtd gave no results and no partition table app in the market.
[Sprint HTC EVO 4G LTE] MikeC84:
http://db.tt/QEWboCNP
[Sprint HTC EVO 4G LTE] david279:
No go.

Sent from my EVO 4G LTE
[Sprint HTC EVO 4G LTE] MikeC84:
Found it!
[Sprint HTC EVO 4G LTE] david279:
Cool

Sent from my EVO 4G LTE
[Sprint HTC EVO 4G LTE] MikeC84:
I'll have a kernel to test later today if any one wants to test...
[Android Q&A, Help & Troubleshooting] nachoalt:
Hello everyone!

Does anyone know if it is possible to unlock 850 MHZ 3g band on Zopo or X310e, because it seems it comes pre-configured to 2100 MHZ 3g and it is not possible to change it through engineer mode network settings. Would it be possible to change it modifying the baseband or radio.img file?

Thank you very much in advance,

Ignacio
[Android Q&A, Help & Troubleshooting] nachoalt:
Anyone?

Enviado desde mi Nexus S usando Tapatalk 2
[Nexus 7 Q&A, Help & Troubleshooting] sc4fpse:
Was trying to use a one-click root/unlock program for the Nexus 7. Apparently all the drivers did not install correctly. My tablet rebooted into bootloader mode, but is not responding to any volume button or power button pushes, or any combinations of button presses that I could think of.

I'm stuck at the "Start" bootloader screen. The text in the bottom left says the following:

ADB is no longer detecting the tablet as being detected, and no fastboot commands did anything at all.

I have no idea how to do a hard reset on this tablet, and can't find anything about it. Somebody? Anybody? Help? :(

edit: Power + VolDown seemed to work, but I had to hold it for quite awhile... much longer than I ever expected. Phew. :(
[Nexus 7 Q&A, Help & Troubleshooting] loonie01:
Did you get it to reboot normally? Go do a search for the Nus 7 image files. It will be a life saver.
[Nexus 7 Q&A, Help & Troubleshooting] scott8281:
As long as you have boot loader mode your in good shape. Download the system images from https://developers.google.com/android/nexus/images#nakasijrn84d and flash the images via terminal or cmd prompt
[Nexus 7 Q&A, Help & Troubleshooting] conor253:
I have got the exact same problem. I have tried to flash the stock images to the device but as the bootloader is locked it won't work. Does anyone have any other solutions?

Edit: How long roughly should you have to hold down power and VolDown to hard reset the device?
[Nexus 7 Q&A, Help & Troubleshooting] Brishen:
Until it turns off.

You can also pull the back off with a fingernail or something and pull the battery connector, it isn't too hard.
[Nexus 7 Q&A, Help & Troubleshooting] renwood:
Google brought up this topic. I received a used Nexus 7 bought from Amazon Warehouse Deals today. It seems that whoever had it before me botched something, as I cannot get past the initial boot. I was able to get to the bootloader mode, and the info near the bottom of the screen is identical to the original poster. I've never learned how to root or unlock a device before, but before I even try to learn that, I would highly appreciate if someone here can let me know if such a fix is even possible since the lock state is marked as "locked". If the bootloader is not unlocked, how will I reinstall the original firmware correctly?

Thanks so much to anyone that can help me. The physical device seems great - no creaks or screen lift, and very little backlight bleed. It'd be a shame to have to return this if I can just figure out how to undo whatever the previous owner messed up.
[Nexus 7 Q&A, Help & Troubleshooting] janedoesmith:
You can easily unlock it but before you do that, can you get into recovery? Make sure your device is connected to a powered on PC before going into recovery. Once in recovery, you can attempt to restore to factory.
[Nexus 7 Q&A, Help & Troubleshooting] renwood:
I plugged the tablet into my MacBook before entering the bootloader screen. When I select "Recovery" from the options available to me, it just brings up the white Google logo and then the screen cuts to black.

Glad to know I'll be able to unlock the device... I was just worried that the fact that it is locked in its current state might make such a task difficult. Guess I'll start looking into how to go about unlocking the device - thanks for your help!
[Nexus 7 Q&A, Help & Troubleshooting] renwood:
Well, problem I'm running into is that I can't put the tablet into the correct mode to be recognized by a program like mskip's Nexus 7 toolkit. The only part of the tablet I can access in the fastboot or bootloader menu (not sure of the correct term...), so when I attempted to connect the device up to my computer to use the program, it just got hung up on attempting to find my device. All the instructions talk about putting the tablet into USB mode and such, but I can't actually get into the OS to change any settings.
[Nexus 7 Q&A, Help & Troubleshooting] janedoesmith:
I only know how to do it on a PC. Maybe someone with a mac can chime in.
[Nexus 7 Q&A, Help & Troubleshooting] renwood:
I do have access to a PC; could you explain what is needed? Thanks!
[Nexus 7 Q&A, Help & Troubleshooting] janedoesmith:
Go here, download and install the android sdk. Once complete, the android sdk manger will open. From the sdk manger, also install the android platform tools and google USB driver. Other options are not necessary.

http://developer.android.com/sdk/index.html

Then come back here for additional instructions. I'll be here for the next hour.
[Nexus 7 Q&A, Help & Troubleshooting] renwood:
Done and done. Thanks very much for your assistance! What's next?
[Nexus 7 Q&A, Help & Troubleshooting] janedoesmith:
Now, go to the installation directory of the android sdk and you should see several files and folders. Of the folders, there should one labeled "platform tools" and another labeled "extras".

Go in to the "extras" folder then "google" folder. Within the google folder, there is a folder labeled "usb-driver". Just make sure the usb driver files and folders are in there.

Now, put your device in bootloader mode and connect it to the PC. Your PC will start installing the drivers. If it succeeds then double check it in device manager. If it does not, you need to manually install the drivers from device manager and point it to the "extras" folder as the location of the driver.

When the drivers are properly installed, in the device manager, it should say "android bootloader interface" under "android device" or something similar to that. If it doesn't, review the previous steps as you can’t go any further if the PC does not recognize the device.
[Nexus 7 Q&A, Help & Troubleshooting] renwood:
Okay that is done - I see "Android Device" listed under Device Manager, as well as an entry for Google Nexus 7 Bootloader Interface... next? :)
[Nexus 7 Q&A, Help & Troubleshooting] janedoesmith:
Presuming the drivers are properly installed, go back to the android sdk installation folder and go in to the "platform-tools" folder. In that folder you should see several folders and files including “adb.exe” and “fastboot.exe”. Once in that folder, press the "shift" key AND the right mouse button to bring up the context menu. In the context menu selection, click "open command window here" and a command window will open up.

With your device still connected to the PC and the device in bootloader mode, in the command window, type “fastboot devices” without the quotes. If the drivers are properly installed, it will display your device’s serial number in the command window. If it does not, you have to review the above steps and correct the issue before proceeding forth.
[Nexus 7 Q&A, Help & Troubleshooting] renwood:
The serial number is displaying; progress! Now?
[Nexus 7 Q&A, Help & Troubleshooting] janedoesmith:
Very good!!!

Once it displays your device’s serial number, you are all set to start flashing the factory image. Leave the device connected to you PC and leave the command window open. Go here and download the factory image:

https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz

Once downloaded, extract it using winrar or whatever archive decompressor you are currently using. When extracted, you should have the following files:

bootloader-grouper-3.34.img

flash-all.sh

flash-base.sh

image-nakasi-jro03d.zip

Copy the “bootloader-grouper-3.34.img” and “image-nakasi-jro03d.zip” files into the “platform-tools” folder.
[Nexus 7 Q&A, Help & Troubleshooting] radkor:
Or, just read this: http://xdaforums.com/showthread.php?t=1907796 ;)
[Nexus 7 Q&A, Help & Troubleshooting] renwood:
Ok, did that. Then?
[Nexus 7 Q&A, Help & Troubleshooting] KiNG OMaR:
he liked getting all the thanks ;)
[Nexus 7 Q&A, Help & Troubleshooting] janedoesmith:
These are the last set of instructions.

From this point forth, you will start flashing the factory image and I must warn you to do it at your own risk.

With the device still connected to the PC and the device in bootloader, in the command window, type “fastboot devices” without the quotes again just to make sure your device is recognized by the PC. It should display your device’s serial number. If it doesn’t, STOP!!!! Review the above steps and resolve the issue before proceeding forth.

Once it displays your device’s serial number, type “fastboot oem unlock”. On your device, you will be presented with a warning about unlocking your bootloader. Use your device’s volume buttons to select “yes” or “no” and press your device’s power button to confirm. You have to select “yes” to proceed forward. The bootloader screen should now say the bootloader is unlocked.

Now, type the following commands one by one while waiting for each command to complete before proceeding with the next command.

fastboot erase boot

fastboot erase cache

fastboot erase recovery

fastboot erase system

fastboot erase userdata

fastboot flash bootloader bootloader-grouper-3.34.img

fastboot reboot-bootloader

fastboot -w update image-nakasi-jro03d.zip

***During the last step, you will get 3 errors about *.sig files missing or something similar to that. It is normal. Also, flashing the “system” portion will take some time to complete so don’t interrupt it****

It will reboot automatically once completed. It will take some time to boot into the system and it may bootloop couple of times. You are now done.!!!

If you have no intentions whatsoever to flash custom recoveries, kernels and/or ROMs, then you can relock the bootloader by following the directions below. Be warned that if you relock the bootloader now and at some point in the future, you decide you want to unlock the bootloader, you will lose all your data at the time you unlock your bootloader.

To relock you bootloader:

1.	If not already, connect the device to the PC and place the device in bootloader.

2.	Go into the platform-tools folder and open a command window using the shift key and the right mouse button and selecting “open command window here”.

3.	Type “fastboot devices” without the quotes in the command window to verify the device is recognized by the PC.

4.	Type “fastboot oem lock”. Your bootloader screen now should state it is locked.

5.	Type “fastboot reboot” without the quotes.

6.	You are done!!!!!
[Nexus 7 Q&A, Help & Troubleshooting] Masrawy:
Hello Janedoesmith

I wanted to update my ROM this morning, I was using XenonHD 13, wanted to go to XenonHD 14. So as I did it at least 20 times before that, rebooted to recovery (CWM touch) and then cleared dalvik, cleared cache. Then, I installed the update. It gave told me that the update wasn't installed. I didn't have time to see what's the problem as I'm going to school so I just rebooted the device. Now the problem starts...

It didn't want to reboot at all, it was actually stuck on the boot screen (google written in white in the middle and the unlocked locker on the bottom in white). So I hard reset the Nexus 7 and it goes back to the boot screen. After a few times doing that, as soon as it shuts down, I instantly press on volume down button, so it goes to the bootloader. I select recovery, then, same problem, stuck in the boot screen.

If I plug my USB cable, the fastboot doesn't even respond, even if I unplug the cable. I have to restart my N7 and instantly press on volume down. I have another cable that I use with all my other devices, it's not the one that came with the nexus, but I never had any problem. I even tried another one, same thing!

So basically, I can't even do your instructions, because it requires to plug the cable and it directly freezes.

Any solution? would it work with the stock cable?

thank you!
[Nexus 7 Q&A, Help & Troubleshooting] janedoesmith:
1. In order to get into recovery from bootloader, your device has to be plugged in to a pc. Apparently, it is know bug with the bootloader.

2. In reference to the bootloader freezing when plugged into a pc-- I have experienced this issue and reinstalling the drivers corrected the issue for me. Others have reported the same issue and they determined it to be a bad connection at the usb/micro usb end. They resolved it by wiggling the usb/micro usb connector. I also noticed when I was having the freezing issue, unplugging it did nothing and the bootloader remained frozen until I hard reset again.

3. Always use the OEM micro usb cable. I have purchased several replacement micro usb cables and I noticed the micro usb connector (the metallic portion) to vary in length. My OEM micro usb connector end was approximately 6mm in length. The lengths of my replacement cable's micro usb metallic end varied from 5mm to 7mm. If you have to use a replacement micro usb cable, make sure the micro usb metallic end is at least 6mm in length. If it is not, at your option, consider shaving off some of the plastic bulkhead from the micro usb connector to increase the length of the metallic portion.
[Nexus 7 Q&A, Help & Troubleshooting] TomorrowSpace:
Thank you everyone. I'm pretty sure what worked for me was just finding the original charger that is rated as "2A" instead of "1A" which all most phones chargers have.
[Nexus 7 Q&A, Help & Troubleshooting] godtoall:
FROZEN

I have been having this issue now for some time now. One day I booted my 7 and it just hung on the CM10 loading screen. When I tried to boot into recovery to wipe, it just hung on the Google screen until the battery died. Decided to use ADB to restore it, but the bootloader froze as soon as I plugged it into my PC. Thinking this was an issue with my PC, I tried plugging it into several others and it kept freezing. The bootloader freezes even when plugged into the AC adapter. I have also tried several different USB cables which have not worked either.

Has anyone been able to fix this issue? I have read through the thread and tried everyone's solutions but none of them have worked for me.
[Nexus 7 Q&A, Help & Troubleshooting] jeremy.m.williams:
problem with bootloader freezing with usb connection

ANY IDEAS YET?

I also am able to get into bootloader. but as mentioned above, the problem is that whenever the USB cable is plugged in, the buttons don't navigate through the options. whenever the USB cable is NOT plugged in (and reboot bootloader) the button work just fine.

I don't have a recovery currently installed.

the issue is not with drivers on the computer or the usb cable...

happens while USB plugged in windows, linux or simply just plugged into a wall outlet to charge.

I need to get into fastboot but i'm having this issue with the bootloader (corrupted?).

any help would be appreciated.

bootloader version 3.34

nexus 7 (grouper)
[Nexus 7 Q&A, Help & Troubleshooting] kdhbarca:
help

I followed the instructions (thanks for putting these up here) to the letter and everything seemed to go ok. except after the cmd window finished my nexus 7 was ejected and the my PC would no longer recognise the device. the Nexus was left with the Google and the unlocked padlock icons,. It would not respond at all, but I managed to switch it off and now it won't power up it is still totally unresponsive. Can you help me please?
[Sony Xperia P, U, Sola, Go] batman_112:
STOP!! THIS IS FOR XPERIA S LT26i

Please don't forget to hit the "THANKS" button! :p

This is the generic and unbranded firmware.

1. Download FW from HERE or HERE.

2. Install flashtool.

3. Copy and past the downloaded ftf file from step 1 into the firmware folder of flashtool. The path is typically C:\Flashtool\firmwares unless you chose another directory when installing flashtool.

4. If you haven't already, make sure you run Sony PC Companion (while your phone is connected to the PC) at least once to ensure that the proper phone drivers have been installed.

5. Run flashtool and follow on screen instructions.

6. Please hit the THANKS button! :D

ENJOY!! :D

The OLD ICS FW can be found on hotfile.

Happy flashing! :D
[Sony Xperia P, U, Sola, Go] Spectre51:
Should post it here and lock this thread: http://xdaforums.com/showthread.php?t=1599303
[Sony Xperia P, U, Sola, Go] batman_112:
Oh nice. Silly me I did not see that thread. Thanks!
[Sony Xperia P, U, Sola, Go] SEFanX10i:
So this has Music & Video Unlimited, Playstation pocket and everything else? :)
[Sony Xperia P, U, Sola, Go] Spectre51:
Yes. But those apps have been available even if they didn't come on your phone.