yashsingh1/xdaforums huggingface dataset:
[Nexus 7 General] mr_tris:
Well if I was you I'd just use mskips toolkit, its absolutely epic it'll save you a lot of farting around. I take it that your fully updated? ( Not that it matters) You seem to know and understand your way around adb so just go for it and enjoy. :)

Its works smooth as silk and save you a lot off time. The options available to you are just staggering!

http://xdaforums.com/showthread.php?t=1809195
[Nexus 7 General] O_G:
Thread Cleaned​

No need for personal insults, lets just try to help each other out and show each other some respect.​
[Nexus 7 General] psycho2097:
going to recovery from bootloader works fine after 3.41.....wat r u talkin abt? (i m stock rooted+twrp)

oh yea...u hav 2 remove that recovery stock.p file thingy first.
[Nexus 7 General] formula84:
There are plenty of people that are having issues with recovery on 3.41 bootloader.... Its confirmed some have it some don't.

The issue is that with 3.41 bootloader on some Nexus 7 Devices a custom recovery is unbootable no matter how you try, every time it will try to load recovery and fail at a black screen then reboot into the OS. It does not matter how you try from ADB reboot to recovery or from bootloader with USB attached or not.
[Nexus 7 General] kieso:
Ohh crap I read about that in some thread. Any idea exactly what has to be done. The only way I can get into cwm is with ROM toolbox but I have to reflash cwm every time then hit boot into recovery.
[Nexus 7 General] mr_tris:
In your system folder there's a file called 'recovery-from-boot.p'

Go into a file manager with w/r access and rename it ' recovery-from-boot.p.bak'

When the system boots it reads that file and resets the recovery to stock, by changing the name you remove the problem.
[Nexus 7 General] kieso:
Thank you for all the help! I appreciate it.
[Nexus 7 General] mr_tris:
No problem, a click on the 'Thanks' button for me and my colleagues on this thread would really make our day. :D:thumbup::)

I hope you get sorted mate, I wouldn't be able to sleep at night until I got custom recovery working properly on any of my devices! :(
[Nexus 7 General] death_skt:
i tried changing the name of the file, but.. after reboot, the tablet gets stuck on google screen, recovery never loads... any suggestion? Thanks =)
[Sony Xperia T, TL, TX, V] waqsuk:
Hi I'm looking at buying this handset having sold my s3, I don't want to support Samsung. How does CM10 run, I realise its still early but would like to get some indication.

Thanks
[Sony Xperia T, TL, TX, V] gregbradley:
It runs well. I have read a few reports about phone becoming silent every now and again and the headset does not work yet (But there is a patch for it)

I ran it for a few days but went back to stock as I wanted to listen to music, otherwise its good.

Dont forget, Q&A
[General Questions and Answers] mangelasakis:
Hi again. I have tried to install cm9.1-20121021-nightly-coconut but I get this error:

Data wipe complete.

-- Wiping cache...
Formatting /cache...
mtd: not erasing bad block at 0x03000000
Cache wipe complete.
I:Can't partition unsafe device: /dev/block/mmcblk0p1
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
rm: can't remove '/data/dalvik-cache': No such file or directory
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
Battery Stats wiped.

-- Installing: /sdcard/cm-9.1.0-coconut/cm-9-20121021-NIGHTLY-coconut.zip
Finding update package...
I:Update location: /sdcard/cm-9.1.0-coconut/cm-9-20121021-NIGHTLY-coconut.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "WT19a" || getprop("ro.build.product") == "WT19a" ||
getprop("ro.product.device") == "WT19i" || getprop("ro.build.product") == "WT19i" ||
getprop("ro.product.device") == "coconut" || getprop("ro.build.product") == "coconut"
assert failed: getprop("ro.product.device") == "WT19a" || getprop("ro.build.product") == "WT19a" || getprop("ro.product.device") == "WT19i" || getprop("ro.build.product") == "WT19i" || getprop("ro.product.device") == "coconut" || getprop("ro.build.product") == "coconut"
E:Error in /sdcard/cm-9.1.0-coconut/cm-9-20121021-NIGHTLY-coconut.zip
(Status 7)
Installation aborted.
I:Can't partition unsafe device: /dev/block/mmcblk0p1
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc

My device is a Wt19i Sony ericsson live with walkman.

What I am doing wrong?
[General Questions and Answers] mangelasakis:
I love cyanogenmod

After some attempts I managed to install the cm9.1-20121021-nightly-coconut and I am so excited. Finaly we have cyanogenmod update via OTA, I think. There is a "cyanogenmod update" option.
[General Questions and Answers] Madness_logic:
About the installation

Have you unlock the bootloared already? because when i started in this kind of things i see that message over and over again and it's because you don't have unlock the bootloader
[General Questions and Answers] vitiweet:
Dear friends please help

i have lava s12 [android 2.2 ]phone which i rooted.then i replaced stock launcher any may other applications.the phone was working fine.

then i installed rom manager and installed wrong clock work recovery mod .now my phone was unable to factory reset either by pressing home volume plus power key or by pressing the reset button in settings.

although phone was working.recently i tried to change the resolution of phone and installed a application the phone rebooted and showed the launcher has stopped working,the phone process has stopped working force close and gets stuck there.

the phone has become unusable ,i cant remove that application beacuse it does not allow me to go beyond force close messages,i cant format my phone also .please provide a solution
[General Questions and Answers] _Variable:
You need to call Huawei for them to fix.
[General Questions and Answers] post-mortem:
Read this:

http://xdaforums.com/showthread.php?t=1827723
[AT&T Samsung Galaxy Note I717] Raiderman:
Just as the title says. Hoping someone has something brewing. A note 2 port would be great.t
[AT&T Samsung Galaxy Note I717] johnrippa:
Nymphomaniacal elf queens would be awesome too. We can all wish...
[AT&T Samsung Galaxy Note I717] dparrothead1:
I already have one of those!!:thumbup::D:)
[AT&T Samsung Galaxy Note I717] jimmer411:
I agree it would be nice to have even an aosp jb rom instead of all these damn kangs. Almost all the real devs have left xda.
[AT&T Samsung Galaxy Note I717] welchertc:
Complain a bit more about stuff you get for free, see if it helps.
[AT&T Samsung Galaxy Note I717] gdbusby:
Just a simple search will turn up great work from some devs that have merely setup their own sites. Think Hot cakes
[AT&T Samsung Galaxy Note I717] Clark Joseph Kent:
Thread Closed....
[HTC Sensation] fashofasho:
I am wondering if I made any major changes or done anything wrong.

1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?

2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.

Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
[HTC Sensation] rzr86:
when you did S-OFF in order to install Cyanogen JB first you had to flash the latest fw version and then the rom

the rom you tried to install requires the latest fw version

now are you still s-off?

what is now your hboot version?

what is your fw version?
[HTC Sensation] Skipjacks:
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.

2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)

Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.

If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.

If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!

Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.

It should not boot.

This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!

I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
[HTC Sensation] rzr86:
i got confused:confused:

.i think your answer is going for fashofasho
[HTC Sensation] fashofasho:
Thanks for the reply. Okay so here is where I am currently at. I haven't done anything since I reflashed stock ROM throguh RUU after the fail cyanogen flash. On this stock ROM whenever I load into bootloader it still says s-off 1.17 but I did lose my clockworkmod. So according to your instructions I should either clockworkmod again or 4ext now, that's okay right? If so, going to flash firmware then cyanogen!! :) Or is there a problem that I have s-off but not recovery.

P.s. there is no point in running revolutionary and have it s-off again when I already have it right, just thought it might be necessary to make things fresh
[HTC Sensation] Skipjacks:
If you have a bootable phone right now this is easy as you may not need adb or fast boot or anything.

First off you will need to install 4ext. Get the app from the Play Store. Then run it and let it install its recovery module. (You may need to be rooted to do thus, which your stock rom is not. Im not sure if you can flash the recovery without root or not because Ive never tried without root. If so, then you will have to install Superuser via fastboot I think. You any guide for rooting to get instructions on this. Its easy.)

You may also find a way to install 4ext recovery via flashing from bootloader, but you will have to search for that. You MAY even be able to install it with the firmware upgrade. You will have to see if that is an available option.

Get your firmware from this thread...

xdaforums.com/showthread.php?t=1459767

Follow the instructions to update. Once you have 3.3x firmware and 4ext simply boot to recovery, do a full wipe, and flash cm10 (make sure cm10 is on your sd card. You can download it from your currently working gingerbread rom so you have it available)

You have like 15-20 minutes worth of work to do, so its not a monumental obstacle to overcome. It just seems like alot
[HTC Sensation] fashofasho:
I am not rooted but am S-off. So my next step would be to root. I am suppose to have Clockworkmod to root AND 4EXT after right? Its not one or the other? I keep reading that people recommend 4ext is better than CWM but in order to root

su-2.3.6.3-ef-signed.zip

I need CWM first correct?
[HTC Sensation] rzr86:
flash su-2.3.6.3-ef-signed.zip first and then install 4ext recovery
[Samsung Galaxy R i9103] khpatel4991:
http://xdaforums.com/showthread.php?t=1932069

Above is the link for getting source code of having vertical CRT OFF..

Someone can port for CM10 of our device??
[Samsung Galaxy R i9103] Adam77Root:
It can be ported, but I would give it low priority now. Maybe later.
[Samsung Galaxy R i9103] khpatel4991:
K.buddy, there's no hurry... you can do it in your leisure time
[Galaxy Note II Accessories] gauravr:
Hi guys,

Which is a better flip cover ? Grey or Blue?

I am liking blue but a bit confused so thought will ask here..

Cheers !
[Galaxy Note II Accessories] audiobookman:
this is purely down to personal prefence, i had a horrbile pebble white phone (sorry i dont like white as the ipod has runied white forever for me) and bought the grey case and love it.
[myTouch 3G, Magic General] edba2000:
Is it possible to enable the USB audio feature? (digital audio out)
[myTouch 3G, Magic General] E.Cadro:
Thread moved to general

Sent from my Nocturnalized One XL using Forum Runner
[Galaxy S III Q&A, Help & Troubleshooting] Vinaltap:
So last week I ODIN over the Swedish Jelly Bean for S3 as I was getting bored of waiting for the update. However, Vodafone have released the Jelly Bean update this morning so I wonder if it was possible to revert back to Vodafone's Ice Cream Sandwich to then get the official update from Vodafone.

So to summarise:

Non rooted Vodafone UK Samsung S3

Pushed the Swedish Official ROM using ODIN

Would like to go back to enable OTA updates to get official S3 JB ROM

Cheers
[Galaxy S III Q&A, Help & Troubleshooting] drew071:
Download stock Vodafone ics firmware.

The best things to do is cfroot your device using Odin, then download triangle away and use it.

Then go to recovery and format system, and data under storage and mounts.

And wipe cache.

Then enter download mode and flash Vodafone stock using Odin.

The reason I say use cfroot and do it that way is to prevent any backwards compatibility that may occur if you flash straight over the top as odin does not format before flashing

Drew
[Galaxy S III Q&A, Help & Troubleshooting] istoner:
Just out of curiosity, you are giving OP the most fool proof solution?

I thought rooting voids warranty (?), so my plan was to simply flash the older stock ROM from my region over the new stock ROM and then update OTA. Will that drastically increase the chances of ****ing up?
[Galaxy S III Q&A, Help & Troubleshooting] Vinaltap:
Great, thanks very much. I would like to keep it unrooted at the moment, so do I need to just unroot it prior to flashing the Vodafone stock ROM.

At the moment when I connect my phone to Kies it tells me that it is not available to update firmware and I would like to not have this with the original Jelly Bean ROM.
[Galaxy S III Q&A, Help & Troubleshooting] drew071:
If you use triangle away you should have no issue. At the stage you enter recovery and wipe system and data you will have no rom on the phone. When you flash stock Vodafone ics it will be unrooted.

If you didn't want to go through all of this you could download the Vodafone branded Odin flashable jb rom and flash it over the top.

The only reason I'm suggesting cfroot is because you are talking of going back to ics first. Using this method would avoid all potential problems of flashing backwards, is more of a precaution that's all.

Drew
[RAZR i Q&A, Help & Troubleshooting] limestar:
Hi Guys,

I am lucky enough to have a black one with final software and a White one with test keys.

Does anyone have a guide and the software to flash the Razr i?

I would really like to get my white one on final software.

Cheers
[RAZR i Q&A, Help & Troubleshooting] TrippleT:
U need RSD Lite and the FirmwarE

...and...

if u are unlocked u need This FirmwarE
[RAZR i Q&A, Help & Troubleshooting] limestar:
Thank you
[RAZR i Q&A, Help & Troubleshooting] JackyJack:
What test keys ?
[RAZR i Q&A, Help & Troubleshooting] mattlgroff:
Can you pull this software for us to be able to flash? The system and boot.img would be awesome.

Once rooted the commands to pull them to your SD card (internal) is:

adb shell
su
make_ext4fs -s -l 885768704 -a system /sdcard/system.img.ext4 /system
dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img

I would really like to take a look at these. Cheers!
[Samsung Galaxy Tab Plus] arfian:
Good news for our device..

http://www.sammobile.com/2012/10/21/after-months-of-speculation-exynos-will-go-open-source/
[Samsung Galaxy Tab Plus] anzuo:
Excellent news. Was waiting for this for quite long, there could be some fun project with quite a few Exynos based development boards.
[Samsung Galaxy Tab Plus] juniorhxcx:
Please look at the developers Tab P62XX

The codeworkx already would quit developing for the Galaxy SII and SIII probably, he is striving to continue development without the necessary documentation. The Aorth doing a great job. I hope that Samsung fulfill his word without even rolling over yet, so I think matter of time before we ROMs more stable and officially supported by CM. I do not know if Aorth part of Team CM, but I believe the same CM10 having official support (I wish so much ^ ^) should continue with him at the helm, after he saved us!! Thank Aorth too!!!

I'm very anxious, just want to see the development of this increase!!

Waiting CyanogenMod support and other Builds now .... Hopefully soon I started as vai be disponiabilizada documentation.
[HTC Incredible S] TaLEntZ96:
Hey all, I've been flashing Roms for ages but I'd love to start making Roms. I've been watching tutorials. but none have been of much use to me. I can use command prompt etc, and i have done a bit of programming. So, could you guys link me to some useful tutorials or even teach me yourself? Thanks guys!

BTW, my ultimate aim would be a fully functioning ICS Rom!
[HTC Incredible S] TaLEntZ96:
Lol, just found a useful tutorial! Would still love your input though ;D
[HTC Incredible S] vizzy:
What was the tutorials found ?

Also are you going for most topics made in a day ?
[HTC Incredible S] poondog:
These are from my bookmarks folder on my computer :) Hope they are of relevance

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

http://xdaforums.com/showthread.php?t=1272270
[HTC Incredible S] TaLEntZ96:
Thanks mate, second link is very useful!
[HTC Incredible S] TaLEntZ96:
Ok, so tonight I learnt how to use Kitchen and etc, so now i need to get into understanding the build.prop language and etc...
[HTC Incredible S] poondog:
Have you looked here too?

http://xdaforums.com/forumdisplay.php?f=613

Plenty of info there
[HTC Incredible S] TaLEntZ96:
Ah, exactly the kind of forums i was like for... Didn't think it would be called chef central though :D Thanks!
[HTC Incredible S] ZaySk:
Check this out. Lots of goodies in there :)
[HTC Incredible S] TaLEntZ96:
Just about to flash an ICS Rom I just finished, wish me luck! :D
[HTC Incredible S] poondog:
Good luck :) Mind telling us what it is?
[HTC Incredible S] Lasantha:
thanks op for this thread was looking for one like this
[HTC Incredible S] TaLEntZ96:
Well, first i took a Galaxy Nexus ICS rom, which someone kindly ported already, and I fixed up GPS and MMS (I think).

But just about an hour ago, i took IceColdSandwich, and I am going to see if i can do any good with it :D
[HTC Incredible S] magius:
Just felt the need to chime in. Thanks for the very useful links. This thread is why I love coming to XDA.
[HTC Incredible S] poondog:
Nice mate :) Successful?
[HTC Incredible S] TaLEntZ96:
Not anymore, im getting an error when trying to flash the rom, something like error 6?
[HTC Incredible S] TaLEntZ96:
I'll try fix it before school tomorrow. Thanks for the helps guys!
[HTC Incredible S] Nonverbose:
That's an updater-script problem. Check your recovery.log
[HTC Incredible S] TaLEntZ96:
Will do!
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] saeed-constantine:
I changed launcher icons Of Ics stock contacts and messaging to GB icons
[XPERIA X8 Q&A, Help & Troubleshooting] HashyCode:
Delete the out folder..try to build again :)

Sent by Vince™
[XPERIA X8 Q&A, Help & Troubleshooting] Kinger KH:
OK,i will try ~~ thank you ~!!:D
[Asus  Eee Pad Transformer Prime] Gage_Hero:
If you don't have universal naked drivers downloaded and installed, do that.... also you should install twrp as your recovery, just make sure you get the right one.... I think I read at the top you installed JB so your bootloader is probably JB...... don't install the ics twrp over the jb bootloader or you will have a unrecoverable mess I think.....
[Asus  Eee Pad Transformer Prime] flueterflam:
Hey thanks for the help. Unfortunately, as I mentioned, I already tried the naked drivers to no avail. Just to be safe, I tried once more, removed/deleted/uninstalled the drivers and even force turned off driver installation for good measure to make sure. I have the same behavior with both the ASUS drivers and the Universal Naked drivers.

I think I forgot to mention explicitly that I tried installing twrp as recovery. I was careful to get the JB bootloader. It hasn't helped. I tried it again today after the re-install of naked drivers. Same behavior as before. Fastboot appears to flash the blob successfully,, but then the prime becomes unresponsive, will not reboot via fastboot, and sticks at flash screen and no RCK.

Any other things that I could have missed or done incorrectly?
[Asus  Eee Pad Transformer Prime] netxxl:
Bootloader Error

Hi,

any solution to this yet? I do have the exact same problem!

It seems to me the procedure is locked and it accepts only one comand (maybe the key) then rejects al subsequent comands.

.
[Asus  Eee Pad Transformer Prime] whycali:
From everything I have seen "Unrecoverable bootloader error" means exactly what it says. its unrecoverable. You need a new motherboard
[Asus  Eee Pad Transformer Prime] netxxl:
Bootloader Error

Well, that's exactly what Asus wants us to think. My logical thinking tells me there is no defect other than a software failure in connection with Asus locking down bootloaders in order to torture their customers.

I can still access Fastboot, it is just locked down. I guess the first comand (which it always accepts should be a key to unlock the fastboot procedure, without that key nothing is possible. Why can they not recover it at the service center? Maybe they do not want the key to get public.

It's all business after all.

Still, they use open source software for free and then neglect warranty...

I just cannot understand. Well, not Asus for me again I guess...
[Asus  Eee Pad Transformer Prime] Johnst:
Same problem, posted http://xdaforums.com/showthread.php?t=2154851