yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] AlDrag:
Thanks for the quick reply and tip! For now on I will definitely install from recovery only.

I tried reflashing the Clockwork recovery thing but it didn't seem to fix it.

So I was thinking about flashing the Siyah kernel? Is this a good idea? I flash just the PDA file only right?

Sorry for not knowing much about this flashing stuff xD
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Yeah, you might as well try the Odin version of Siyah even tho it probably won't work. Can't hurt put it that way. Yep, flash it in the PDA section of Odin. If that doesn't work flash a stock rom with Odin as I mentioned (also in the PDA section). If you get stuck, look for Hopper8's 'Odin won't flash' thread.
[Galaxy S II Q&A, Help & Troubleshooting] AlDrag:
Ok I tried flashing Siyah and didn't work :/ Ok I will give flashing a stock rom a try. I presume that puts it back to the way it is? Then I have to re root etc?

Thanks!
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Yep.
[Galaxy S II Q&A, Help & Troubleshooting] AlDrag:
Reflashed to a pre-release version of JB from Samsung :) Thanks heaps for your help! Appreciate it. Will probably go back to Cyanogen tomorrow.

One question though. Is Cyanogen 10.1 supposed to be quite stuttery? I know it's a nightly build and all. But using this official pre-release from Samsung, it's JUST SOOOOO MUCH MORE SMOOTHER! But I expect Cyanogen to be a lot faster :/ Maybe my kernel was just having problems the whole time?

Thanks!
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Good man ;) Can't comment on CM10 as I've never used it, used CM9 for ages & got fed up with various things not working as they should/being flaky & have never bothered with CM10 as a result, I'm sure someone else will be able to answer those queries.
[Galaxy S II Q&A, Help & Troubleshooting] keithross39:
I'm guessing you flashed the 0824 nightly of 10.2. According to the discussion thread, anybody who uses this nightly will experience the broken recovery....they've posted a link to a kernel + recovery which needs to be flashed before the phone is rebooted for the first time in order to replace the broken recovery. Concerning the stability of the ROMs.........

10.2.....IMO...NOT stable enough for daily use....

10.1.....fast and smooth, and no bugs that make me want to stop using it.......

10.0.....not as fast as 10.1 but just as smooth but with the same lack of noticeable bugs as 10.1.....

JB Firmware.....obviously the most stable, but simply not as fast.....even if rooted and debloated......

Back to 10.1 for now.....
[Galaxy S II Q&A, Help & Troubleshooting] AlDrag:
Sorry about the late reply.

Yes that was the exact build! xD

Oh well :) I am actually quite happy with the official JB firmware from Samsung atm. It's A LOT SMOOTHER than 10.1 for some reason :/ I don't know why. Just is. I had lots of problems with 10.1. At times the RAM seemed to leak so much I would have to restart it otherwise it would just be so stuttery. ESPECIALLY with Swift Keyboard and Facebook heads xD It's ashame because I really liked Cyanogen. Missed some of the features.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Filitov:
I have a shiny new V1620 as Vodafone call it and I'm O2 bound.

Is it at all possible to simply update my device with the latest O2 compatible ROMs etcetera or would this just plain not work? Would this mean I could use an O2 SIM without any further unlock?

Also, does anyone else have the exact model I do as listed below, as I haven't read any topics about this specific model ID.

Thanks in advance guys.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] BoSJo:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel

Here is all the info you need :)
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Filitov:
I have the model with the 520Mhz processor, will that make any difference to the ROM I'm choosing?

Also it's not really clear that when I have updated my dvice if it will still be locked to Vodafone.

Anyone any ideas?
[Galaxy S 4 Q&A, Help & Troubleshooting] atricus:
Hi all my pb is I need to replace camera sensor of my gt-i9505 (exmor r) with the one of i9500(exmor rs) to have best quality.

but when I do that the sensor is not known by my phone so how to fix that plz
[Galaxy S 4 Q&A, Help & Troubleshooting] ranger4740:
I'd think you would need to also change camera firmware as well as camera sensor. No idea how though.
[Galaxy S 4 Q&A, Help & Troubleshooting] atricus:
Yes I think too . But the solution is ?
[Galaxy S 4 Q&A, Help & Troubleshooting] Febby:
I'm sure its not going to work.... I9500 runs an exynos processor so all the hardware is set at system files made for that processor and motherboard I'd imagine. If it was as simple as that I would see people exchanging their sensors on worse phones with a better one. I could be wrong though. Good luck!
[Xperia Arc Q&A, Help & Troubleshooting] malimukk:
Hi Guys

The aosp dialer in Gin2Yellybean doesn't support t9 dialing :( How can I change it to one that does support and where to get it?

Thanks
[Galaxy S III Q&A, Help & Troubleshooting] laura almeida:
Hi Guys...

I was wondering Is there any way to change BootLoader image ? (The image which shows before Bootscreen ?)

I think i would have to flash a boot loader with a modified animation in order to customize it.

Can anyone help me with this ?
[Galaxy S III Q&A, Help & Troubleshooting] boomboomer:
No, the bootloader is encrypted and can't be modified.
[Galaxy S III Q&A, Help & Troubleshooting] SnowPluralism:
Image might be on kernel i think

Try decompile kernel and search rle images i think u can change there

Offtopic in non abuse way: *from your photo u look beautifull :)

Take care
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Identical post yesterday
[Galaxy S III Q&A, Help & Troubleshooting] laura almeida:
:eek::(:(:(:(:(
[Galaxy S III Q&A, Help & Troubleshooting] laura almeida:
Sounds like a very easy task.:D

I definitly needs to do more research.

Ohh thank you...

Offtopic in non abuse way : I look much more beautifull in person.

But sadly i don't have a Foto-Face..:(

Just Kidding....:D:D:D:D:D
[Galaxy S III Q&A, Help & Troubleshooting] laura almeida:
Actually i haved searched for it.

I am not stupid, i really used the search Button.

But could find anything usefull.

Anyways I'm Sorry if similar post does exist...
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
Not an obvious title:

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

Image is not in the kernel by the way. Siyah kernel puts a boot splash on but this actuallty inserts between the actual boot splash and the boot animation, to give time to boot into 2nd rom. Nothing to do with the actual boot splash and does not replace it.
[Galaxy S III Q&A, Help & Troubleshooting] laura almeida:
I thought Siyah replaces the orginal boot loader image...

Hum it seems I have to stick with the orginal...

My bad
[Galaxy S III Q&A, Help & Troubleshooting] SnowPluralism:
Sorry i couldnt help i hinted that because on my previous phone it was there.

Again oftopic:** beautifull and confident :thumbup::thumbup:

And we are neighbors im portugueses and u are spanish ;)
[XPERIA X8 Q&A, Help & Troubleshooting] KalolParty:
I have an Xperia W8 (Same as X8). I flashed nAa 2.6.32.61 jb kernel on my device. Before flashing this I had the nAa jb 05 kernel. But then I decided to flash my minicm10 ROM again. I took a backup and made a full wipe.

When I selected the zip file, it showed an error instantly and aborted. Then I tried the latest nightly. Even that didn't work. (Though I could restore a backup of jelly bean)

Finally I read that Mimicm7 2.2.2 could also be installed. It worked and I am very happy with it now. And have flashed mimicm7 again without problems. I have no plans of going back to jelly bean.

Yesterday, I tried to flash odex zip file (on mimicm7) I got the same error. As I don't have access to a computer for a while, could anyone suggest a fix. Why odex zip file is not flashing using this kernel? I have searched a lot. Am I the only one facing the problems? Please provide a way to flash Odex.
[XPERIA X8 Q&A, Help & Troubleshooting] iks8:
First: You can't flash minicm10 because instalation script need nAa5 so you can edit script or fash rom on nAa 5 and then flash nAa 6

Second: Odex.zip is only for jellybean and minicm7 is already odexed.
[XPERIA X8 Q&A, Help & Troubleshooting] KalolParty:
Thanks a lot. I wasn't aware that minicm7 is already odexed. Can you recommend any other ROM(with custom kernel) with at least 60-70 free ram and a battery backup that lasts for a day with moderate usage?

Is the minijb ROM by davee10 good? because minicm10 is very Slow even when a few apps are running. With good battery backup?
[XPERIA X8 Q&A, Help & Troubleshooting] iks8:
Every cm9/10 is slow. Apps are heavy because system is designed for new, faster than our old x8, devices. I'm using lite cm7 by fabe with oxydo zcf 4 and it's work pretty cool but I advise to test for yourself. If you don't need ginglerbread look at froyo pro with alfs 8 - it's one of the fastest combinations.
[XPERIA X8 Q&A, Help & Troubleshooting] KalolParty:
I can't find lite cm7 by fabe. please provide the link.

Froyo pro is pretty old. any gingerbread ROMs with great performance and battery life. Does oxydo kernel have smartass H3 governor?

Thanks a lot iks8 :)
[XPERIA X8 Q&A, Help & Troubleshooting] iks8:
Yes it has. Lite cm7 is in lite cm10 thread. Sorry but I'm on mobile so I can't provide you a link.
[XPERIA X8 Q&A, Help & Troubleshooting] KalolParty:
Can't find that thread . Even googled it. Please PM me if you can. I found the kernel.

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

this is it, right?

But not the ROM. thanks for the help.

#you #are #great
[XPERIA X8 Q&A, Help & Troubleshooting] Titan9119:
Here's a link to LiteCM7 http://xdaforums.com/showthread.php?t=2356960
[XPERIA X8 Q&A, Help & Troubleshooting] KalolParty:
Thanks man. I downloaded it. But iks8 said that he's using oxydo zcf 04 kernel and so is Sgt. meow. I can only find oxydo zcf 03. Searched both xda and even googled. can't find 04
[Nexus 7 Q&A, Help & Troubleshooting] man33sh:
NOOB ALERT! :D

I had ParanoidAndroid installed on my N7 when I decided to go back to the stock rom. I tried installing 4.3.0 but it didn't work and I have no OS installed. All I can get into is the bootloader mode and TWRP.

I used NRT 1.7.1 and ended up with error - Device version-bootloader is '4.18' Update requires '4.23' or something on those lines.

Have no idea now what to do... tried a few things that I googled but still stuck.

Please help.

Thanks.
[Nexus 7 Q&A, Help & Troubleshooting] jkkk88:
Download original factory image 4.2.2 for your n7, boot n7 into boot loader mode, and flash-all.

Optionally you can then do the same with 4.3 image.

Then you can begin with others ROMs again.
[HTC One X] krGemini:
hi,

I just want to ask some noob questions, as I don't play around my set so much.

1) First of all, do I have to be on stock recovery to check for updates also ?

2) I rooted my phone using Hasoon's Toolkit and installed TWRP Recovery (didn't install a custom rom yet, on stock 4.1.1), but made a backup before flashing recovery. Do i have to flash stock RUU to come again to stock, or I can flash the backup I made before flashing the recovery ?

3) How i can find my stock RUU, my CID is TMOB_005.

Regards,

Kashif Rafiq
[HTC One X] krGemini:
100+ views no reply, no one is ready to help ?

Can anyone with same CID confirm, whether update recieved or not ?
[HTC One X] Craiglivesey94:
You can receive OTA updates if you have the following; stock recovery, stock rom, locked or unlocked bootloader.

I don't know where the RUU is for your CID but I'm sure there is a thread with it in somewhere.
[HTC One X] n1kos:
Since u haven't flash a custom Rom you are stock, u just need to flash back the stock recovery and wait for tmobile to release the update. No need to relock.

Sent from my HTC One X
[HTC One X] krGemini:
I have downloaded stock recovery for my CID (TMOB-005), will executing these commands in fastboot mode restore stock status

fastboot flash recovery nameofrecoveryfile.img

fastboot erase cache

I have stock 4.1.1 rom already installed.
[HTC One X] daninantro:
correct :)
[HTC One X] nogotaclue:
And just to answer your other question, save the backup you made in twrp onto your computer in case you need it later, this is your nandroid. Then if you install a custom Rom and need to go back to stock at some time you just need to flash the boot.img from your backup and then flash your nandroid in recovery

Now go get the cakes
[HTC One X] krGemini:
i've flashed the stock recovery, but after flashing when i try to go into recovery it shows red triangle with exclamation mark
[HTC One X] nogotaclue:
That's correct

Now go get the cakes
[HTC One X] krGemini:
is this the stock recovery, with no options of backup and restore (i haven't seen this before) ??? strange
[HTC One X] krGemini:
anyone with CID TMOB-005 confirm whether update received or not ?
[HTC One X] n1kos:
Nothing yet, we'll be one of the last carriers to get it as always...

Sent from my HTC One X
[Galaxy S 4 Active Q&A, Help & Troubleshooting] salwansk:
what I found is upon menu boot up the android robot falls and reports "No Command" and flashes "Error". Then when selecting wipe cache partition, the robot falls and reports "Error" then automatically reboots. its MF3 ...

also it losing signal sometimes....this phone is brand new out of the box..... all what i did rooted it with AR.apk for few days and then unrooted it with SUsuper unroot option. so i tried to do wipe after that, and found out my issue ....i did four time factory reset but i still feel the phone laggy, especially when i open the browser sometimes take a minute to load the page or gives me "page cannot display" so i have to refresh the page every time...

BTW i have a good signal 4G LTE and have no issue with my other phone HTC one
[Galaxy S 4 Active Q&A, Help & Troubleshooting] sleze:
Did you ever resolve this?
[General Questions and Answers] xtreambart:
before i had bananabread on it and amonra recovery, used a rom manger and changed the recovery with it then the phone only started in recovery, retried to put bananabread back on it (no luck). so decided to go back to stock rom got the one from htcdev

then it realy started with the htcdev flash and then the unlock, did it with SAPP10000_Sapphire_hboot_1.76.0013.exe, it states on the site of htcdev that it is for the htc magic belgacom one.

after this i get fastboot remote not allowed.

already tried amonra trick with gold card and sappimg and hboot tried 6 they load and then i'm back at the hboot screen and phone still wont load past the first screen (splashimg?) and still no remote allowed

SPL/hboot version: 1.76.0013.

Radio version: 3.22.20.17.

Main software version: 3.54.0.0.

cid: vodap024.

cpld: 12.

product: sapphire.

mid: sapp10000.

security: on.

build-mode: ship.

does anyone have a suggestion?
[General Questions and Answers] xtreambart:
still need help

SPL/hboot version: 1.76.0013.

Radio version: 3.22.20.17.

Main software version: 3.54.0.0.

cid: vodap024.

cpld: 12.

product: sapphire.

mid: sapp10000.

security: on.

build-mode: ship.

does anyone have a suggestion?[/QUOTE]

tried xdaforums.com/showthread.php?t=548218

it loads, after i goes back to hboot screen, restart phone everything stays the same... is my goldcard invalid?
[General Questions and Answers] xtreambart:
this phone is meant to be a present for my son.... so got till 09-02-2013 to fix it or to get a new one.
[Miscellaneous Android Development] Deleted member 5186178:
DISCLAIMER:

Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.

Basic computer skills are required and minimal knowledges about phones and phones utilities too.

Make sure that whatever you do, you are doing it at your own responsibility.

UPDATE:

I updated the recovery to a new version, more stable, with CWM 6.0.4.4 basic structure (updated by me).

After a hard work with many failed builds, I succeded to compile from source a fully working recovery with touch support for ZTE V967S. I used for this the Project Open Cannibal source, named Cannibal Open Touch Recovery. It's a well done recovery, compatible with CWM, with usefull functions: for example advanced backup - you can backup only that partition you want, posibility to use themes, etc.
​

Here you can see more images of the recovery, from a device with smaller screen, but you can check the options.

Touch navigation is made by touching bottom buttons menu, just like in Philz recovery or similar. First button is for exit or go back, second is key down, third key up and last is select or enter. Now you can save your phone buttons.

You should read this:

First time you boot in recovery will be a touchscreen calibration set up: you have to touch three times the red square. Also, first time you do a backup, it will take a little longer time, because it will be create directory structure and free up the space. After that it will be a joy, is fast, is powerfull, is full of options and is funny.
​

CREDITS:

Project Open Cannibal who release and mantains this wonderful recovery.

Sblood86 for his help.

C3C076 for his help on tweaking recovery source.

bgcngm for his unpacking tool.​

​

Download from attachment.
[Miscellaneous Android Development] Deleted member 5186178:
Deleted.
[Miscellaneous Android Development] SuperDroid-BOND:
Need your Help Master

Great to Have you Master in our MTK Community.

Today as master [MENTION=4478781]yuweng[/MENTION] told us try to port this recovery to our MT6577 Device with his auto port tool, but I failed doing so with that tool. So master will you assist me in doing these things for my device. I don't have a linux system and neither my Lappy is accepting it in any form, not even on VM.

My Device Info:-

Micromax A110

Resolution :- 480*854

MT6577 Device with JB 4.1 & 4.2.

Will please help in this. As I failed in philz recovery. So asking for your help here in this recovery also.

Thanks a ton for your time and for this awesome recovery.
[Miscellaneous Android Development] Deleted member 5186178:
Thanks for appreciations, :)

This recovery is underestimated by users, but is very good. Only one thing, is dependat on display resolution. For your device this is not gonna work. Try this one here. I did it for yuweng to test his device (Ihope he will not be upset). But don't use the port tool. Instead, unpack it with michfood tool, change in ramdisk my files with yours from original or a working recovery (recovery.fstab from dev folder, and from root all files that are not for your phone except init executable), repack it and see if it works.
[Miscellaneous Android Development] SuperDroid-BOND:
Thanks for your help master, I did like you said but other than touch screen, everything is working fine. Now need your suggestion on this. Got this recovery and really saying, users have under estimated it cause it have great potentials for future.

Also will like to know how to create a theme for this recovery, as, I am themer and know for my theming only.

BTW, Hats off to you Master. Recovery is awesome. And Touch will make it great further.
[Miscellaneous Android Development] Deleted member 5186178:
Hm, I'm a little bit confused. Which recovery did you tried to port: mine from here from first post or the one I gave you that link? Because mine is for 540x960 resolution and the one from link is for 480x854. If you port that one it should work touch screen. Attention! is not the same as koush touch recovery, the touch area is only for those four nav buttons from bottom, like in early philz recoveries. I read that ProjectOpenCannibal's next recovery will be full screen touch and much improved.

For theme you need to create a folder in cotrecovery folder on sdcard, name it themes and look here https://github.com/ProjectOpenCannibal/sdcard_themes to see how a theme should look, then create one for your resolution and apply from recovery=>COT settings=>theme=>sdcard theme.
[Miscellaneous Android Development] SuperDroid-BOND:
No Sir I am not getting any touch in the below navigation buttons and a new problem also arised just now. Now all bitmap of recovery is not able to find any image inside the recovery. Do you know what problem is it actually....???

Its says like "E/ Couldn't able to find bitmap icon_overlay01.

Though I cross checked all are there.

I am using recovery of Master Yuweng that you suggested few post back.

EDIT:-

Got the Images back after installing the default theme. Actually I selected the theme RED but it was not there so it was saying like that. Now will create a theme and share to you also. BTW how can I adjust size and something to do with touch also...

Master You are awesome and your creations also.
[Miscellaneous Android Development] Deleted member 5186178:
That error appear when you select sdcard theme but there is no theme on sdcard. You see first position "Boot Android", navigate with volume buttons volume up two times, power button to enter, volume down once, power to enter, volume down once, power button enter, select hydro press power and now you should see back all images.

I saw in yuweng post that he didn't gave you that link, so if he didn't gave it to you by pm, I don't think you have the right recovery to port.

Look I'll give you again, please try with this COT Recovery 480x854. The reason the touch won't work in your actual ported recovery is because you use mine and the touch area is out of your screen.

If you have that one (named yuweng-recovery.img) and the ported one don't work that must be related to your phone touch module location, and I will have to documents on this when I have time.
[Miscellaneous Android Development] SuperDroid-BOND:
Just a last question Master,

Sorry for bothering you in everything. Do we have to replace the kernel files also or not...

Cause I am replacing that also So it could be the reason that touch is not working.....????
[Miscellaneous Android Development] Deleted member 5186178:
Of course you should pack with your kernel, you only need my ramdisk. I don't think it's about kernel, I think is that resolution thing. In my first builds I didn't setup resolution, for debugging reason, and I didn't have touch either, but after setting correct width and height, everything worked like a charm. I'm using this recovery since I compiled and I'm very happy. The part I like most is the possibility to backup only that partition you want (if I want to backup data I can select to backup only data).

Good luck on porting. I hope this time it will work. ;)
[Miscellaneous Android Development] SuperDroid-BOND:
Sorry to bother you again master,

But other than touch everything is working fine, may I know is it related to touch drivers or only resolutions.

Cause just checked my device specs and the resolution is saying "480*800" and the file that you gave me is 480*854 so because of this it is not working only for 54 pixels, though I know it's possible as like .9pngs.

If yes so please either do a favor and create another files with resolution "480*800" please.

The last favor please.....
[Miscellaneous Android Development] Deleted member 5186178:
Aahh, there you go! Of course this is the reason. I will try to compile one for that resolution these days and I will post it here.
[Miscellaneous Android Development] SuperDroid-BOND:
No Problem Master,

I can wait. I am posting this Recovery in my thread and Credits are yours and Master Yuweng's also for showing me this thread.

Thanks a ton for this awesome recovery.
[Miscellaneous Android Development] Deleted member 5186178:
Here it is COT Recovery 480x800 for MTK devices. I hope it works.

Enjoy porting.