yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] m0han:
+1. did not work. device: Micromax A116 Canvas HD. recovery: TWRP v2.6.3.0.
[Android Software/Hacking General [Developers Only]] n-0-s:
thanks :)
[Android Software/Hacking General [Developers Only]] makers_mark:
Your recovery has to have ADB enabled! I wish I could tell you I know how to enable adb on all recoveries, but I can't.
[Android Software/Hacking General [Developers Only]] makers_mark:
I don't know. Your best bet is to ask in the forum thread you downloaded your recovery from.
[Android Software/Hacking General [Developers Only]] EnerJon:
Thanks For The Tool... Its Working Fine...

Device: QMobile A900 (MT6589)

Screen Resolution: 720x1280

Stride: 16

Pixel Format: rgb565

1) Don't Know If Its A Bug :confused: But The Screenshot Taken With Option (1 - Get the top framebuffer.) Seems Cropped A Bit At Bottom...

Please Check Attached PNGs

2) Screenshot Taken With Option (2 - Get the bottom framebuffer.) Is Fine... :good:
[Android Software/Hacking General [Developers Only]] EnerJon:
Brother, There Is No ADB Inside TWRPv2.6.3 For CanvasHD... I Think Its Removed By Your Recovery Maker Due To Small Size Recovery Partition...
[Android Software/Hacking General [Developers Only]] makers_mark:
Thanks for the feedback! What you are seeing is something with twrp, I think. I've noticed on mine, if I try to capture the splashscreen on twrp quickly at boot; it will do that same thing at the bottom on my screenshot too. If you look at it when it boots twrp draws like the whole top of the screen then quickly the very bottom as its calling for a fb swap. Even after my Nexus is sitting there for a minute, one framebuffer will look like that until the clock on twrp changes. Then it's fine.

Not real sure what causes it, but have you tried to do it after that? Does it do it everytime? If you open settings.cfg is this the first four numbers in it; 720 1280 16 736 ?
[Android Software/Hacking General [Developers Only]] EnerJon:
No Its Not The SplashScreen... Its Main Screen Which Comes Right After SplashScreen...

Yes It Works Fine After Clock Changes...

Yes It Do It Everytime After First Bootup...

Yes The First Four Numbers Are Same...

720 1280 16 736 7536640 rgb565

Great Tool...!
[Android Software/Hacking General [Developers Only]] makers_mark:
Thanks for pointing that out. Added to the OP:

Notes:

If you change your recovery, you may have to clear the settings, it depends if there is a different pixel format. You can do so easily in the program, or you can just delete 'settings.cfg'

Sometimes your screenshot may seem disorganized or torn. This may happen when the very first screen is drawn, and also in between framebuffer swaps and writes. This is totally normal. This tool grabs your current framebuffer in its current state (in your devices memory). It can't automatically discern if the image is in fact what you see on your device in a given moment. If your screenshot is torn, you can:

Grab both framebuffers (option 3 in normal mode)

Quit hitting buttons to change the screen when you are pulling the framebuffer! lol

Wait for the framebuffer to swap with a clock change, or force it to change by going anywhere in the menu and then back to where you want to get your screenshot. A sub note on that: A button highlighting, and then a screen change will result in two swaps of the framebuffer and your next image will be on the same side of the framebuffer. If your screen was on the top and you hit a button (that highlights), then the next screen will also be on top. If there is no button highlight, hence just a draw of the next screen and a swap: The next screen will be on the opposite side. Same goes for any other change to your device screen, such as a clock digit changing. What was up now is down, and vice versa.

Aroma only uses the top framebuffer. It never calls for a swap, and the bottom framebuffer will stay whatever was last on it.
[Android Software/Hacking General [Developers Only]] EnerJon:
Keep Up The Good Work...!
[Android Software/Hacking General [Developers Only]] m0han:
maybe you're right. now, is there a recovery for canvas hd that has adb enabled? thanks for any info.
[Android Software/Hacking General [Developers Only]] EnerJon:
Try TWRPv2.5.0 or CWMR or CTR For Your CanvasHD... Their Size Iz Small, So The Chances Are High For ABD In These Recoveries... But I Personally Tested Your TWRPv2.6.3... ADB Is Not Included In It...
[Android Software/Hacking General [Developers Only]] digyvijaykumar123:
I am using same series device CANVAS 2+ and it worked on CWM recovery.

Thanks [MENTION=5448769]makers_mark[/MENTION]
[Android Software/Hacking General [Developers Only]] yihongyuelan:
work fine for me

That's great job.

thanks for your sharing, work fine on my device, MTK 6589 platform
[Android Software/Hacking General [Developers Only]] m0han:
got this working!

i'm now on twrp v2.5.0.0. i set up my configuration and am now able to grab screenshots of the recovery screens. thanks a lot, guys.
[Android Software/Hacking General [Developers Only]] Ticklefish:
This works brilliantly on my Xperia Z. Thanks so much! :D
[Android Software/Hacking General [Developers Only]] manuhackzzz:
chose proper height and width of your device ,

i had the same issue having Redmi 1s

follow that link
[Android Software/Hacking General [Developers Only]] m0han:
check this post - just a couple before yours.

btw, that link of yours does not work - due to incorrect formatting. this does.
[Android Software/Hacking General [Developers Only]] millerboy3:
NVM.
[Android Software/Hacking General [Developers Only]] CSeb95:
Hi,

I have a Honor 6, android 4.4.2, TWRP 2.8.0.2 recovery

Screen should be 1920x1080 (FullHD)

To activate ADB on TWRP, I had to go to "Mount" menu, and then click "USB Storage", elseway no devices shown in adb.

But I can't find a clear pic of my screen.

I have attached a zip file with framebuffer.raw

Edit : This said, in TWRP there is a screen capture function, just press voulme down + power, the screen flash, screenshot done.

You'll find them in /sdcard/picture/screenshot (if rooted)

if not maybe you'll have to access them via TWRP file manager or USB connexion.

Thanks.

Seb

Here is what I get :

[IMG="Screen copy"]http://i61.tinypic.com/8wdtuf.jpg[/IMG]
[Android Software/Hacking General [Developers Only]] ch3mn3y:
Have same problem with CWM on my PLAY.

When set to 800x480 or 848x480 there is no good image, but when set to 400x480 there is one, but its cut in the middle (only top), there is no bottom part unfortunately.

SOLVED: When doubled height I got stretched pictures, but they are right and its not a problem to resize them.

EDIT2: On LG L7 resolution is OK, but pictures are rotated 180 degrees.

And on my Z Ultra it take years to pull Framebuffer (8MB file is created).

Anyway, its great tool
[Android Software/Hacking General [Developers Only]] chrisrg:
Only six years since the last post here!

Thanks for this .

Works great on Sony Xperia XA2 running /e/OS. Got the screen resolution from GSM arena, no probs.
[Android Software/Hacking General [Developers Only]] Bi_Nom:
it's been long, sorry to come back to this. i am getting an ffmpeg error when trying to set up a configuration. does anyone have an idea why that could be? i am getting a ~3MB frmbfr file, but then the following error message:

OnePlus 6, /e/OS Recovery 1.3. Using 1080 x 2280 as Resolution parameters.

ffmpeg version N-59742-gd9481dc Copyright (c) 2000-2014 the FFmpeg developers

built on Jan 9 2014 22:01:53 with gcc 4.8.2 (GCC)

configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib

libavutil 52. 62.100 / 52. 62.100

libavcodec 55. 47.101 / 55. 47.101

libavformat 55. 22.103 / 55. 22.103

libavdevice 55. 5.102 / 55. 5.102

libavfilter 4. 1.100 / 4. 1.100

libswscale 2. 5.101 / 2. 5.101

libswresample 0. 17.104 / 0. 17.104

libpostproc 52. 3.100 / 52. 3.100

Hyper fast Audio and Video encoder

usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Use -h to get full help or, even better, run 'man ffmpeg'

WIDTH=1080

HEIGHT2280

STRIDE=8

Pixel Format is rgb565,rgb565be,bgr24,rgb24,rgb32,argb,rgba,abgr,bgra,0rgb,rgb0,0bgr,bgr0,gbrp

S to Y=

Width with stride=1088

K=1

FINAME=frmbfr

ECHO is off.

ECHO is off.

There was an error in ffmpeg.
[Android Software/Hacking General [Developers Only]] :
Hi, i think Im a bit noob to do this since im kinda lost with how this works but i tried used this tool with both 1 and 2 configurations set up and it showed message

"Adb is not connected.

Try "Safely Removing" your device from your computer.

Then unplug your usb cable, and reinsert it."

And i tried but i didn't work. Also I dont know what is the framebuffer, stride and that settings.cfg so maybe thats why im strugguling with this to work, if someone can gently explain me whats going on I would appreciate it.

Device: sweet (2400widthx1080height)

Recovery: OrangeFox R11.1_2 (beta)
[Android Software/Hacking General [Developers Only]] m0han:
Have you tried pressing (volume down) and (power) buttons together while in 'OrangeFox'? It normally works in the newer recoveries without having to do anything else. The screenshots are saved in /Pictures/Screenshots. Just try.
[Android Software/Hacking General [Developers Only]] :
Oh, didn't see that coming. I Though it was more complicated. It woked, thanks!
[Android Q&A, Help & Troubleshooting] pelon273:
Can someone help me fix my galaxy s i did a bad flash now i cant get it to work i flashed it to galaxy s gt-i9000 and i keep going into recovery mode and cant select any of the options
[Samsung Galaxy Nexus] onelovekir:
Already loving Kit Kat! Thanks Carbon!
[Samsung Galaxy Nexus] cmoG530:
Man, this ROM is SOLID! It's great to be back home. I hope Carbon gets to relive its glory days, as it did in 4.3. Great job team! :)
[Samsung Galaxy Nexus] jayshocka:
Nice!
[Samsung Galaxy Nexus] winnici:
Can someone provide a direct link to rom download. Left sidebar device tree doesn't show up in phone or laptop browsers and even when I Google found my way to toroplus download page there's nothing linked after select a release type. Thanks
[Samsung Galaxy Nexus] cmoG530:
Use Google Chrome.
[Samsung Galaxy Nexus] winnici:
I did. Mobile and desktop view and then on a Mac

If it works for you, please copy paste the dl link here or pm so I can try it out. Thanks

Update: download page working now
[Samsung Galaxy Nexus] Gamer819:
Please ignore
[Samsung Galaxy Nexus] tommy1121:
Can anyone let me know how data is please. A lot of devs have perfected the icons showing but data is sketchy. I like the features that are listed here and I would love to make this my everyday driver. I have been a CM fan for ever but I don't like the change in policy. Build and send out then hope for the best. This ROM seems like the one to replace CM. Thank you.
[Samsung Galaxy Nexus] onelovekir:
data for me has been nothing short of a miracle! It has been switching seamlessly between 3G and LTE with no issues what-so-ever. I used to hate having to always reboot the phone just to get LTE in an area I know has LTE. I am also on the newest radio the GJ04 and have been for quite some time.

---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------

The only issue I have so far (and its not a deal breaker by any means) is screen rotation...when the screen rotates, it sort of gets fuzzy, like a bad picture, but then quickly fixes itself. Running Carbon KitKat on my SGS4 as well and it does not do that, so I'm thinking its something with the Toroplus??
[Samsung Galaxy Nexus] fatal99:
dirty flashed the most recent nightly and running well. digging the pie controls. any way that the Carbon Updates in about phone could work to update to the latest nightly as there are no KK milestones?
[Samsung Galaxy Nexus] tonso:
Very impressed with this Rom !

downloaded and flashed yesterday, very nice and stable. I like that the dialer has the Google local business search function built-in, I remember earlier cm builds didn't have it...

Haven't noticed any hiccups yet!:good:
[Samsung Galaxy Nexus] tonso:
Anyone flash a custom kernel with this Rom? any kernel suggestions?
[Samsung Galaxy Nexus] tonso:
Alternative Kernel

flashed the tinykernel-5.5-ASRAM.zip yesterday and everything seems to be running smooth after a day of use. This kernel is giving me 733mb of RAM to work with, so you gain around 30mb over the included rom kernel. I've tested WIFI, GPS, camera, etc., everything seems to function as it should. I've also underclocked to 230MHz and kept the max set at 1200, although you can go over 1500MHz if your phone can handle it...mine usually freezes instantly around 1500. Currently I'm still on build from 2-13, but will be updating soon.

This Rom seems to be very stable and one of the best KitKat Roms I've tried ! I've also reduced animations setting, along w/ other available related settings down to .25 within developer options. Under this set up my phone is pretty snappy!

Data switching (3g/4g, Wifi) has been flawless so far!
[Samsung Galaxy Nexus] tonso:
Although the tiny kernel I mention above works on this Rom, I was experiencing pretty often freeze ups requiring battery pulls, so running the included kernel since updating the rom and haven't had to battery pull yet... so for now will stick w/ the included cyanogenmod kernel.

Overall Great Rom !
[Samsung Galaxy Nexus] jcruz767:
Do any of the KK builds have LTE working?
[Samsung Galaxy Nexus] onelovekir:
Yes mine is working.
[Samsung Galaxy Nexus] jcruz767:
Do you mind sharing what build you are on?
[Samsung Galaxy Nexus] mondragon21:
What happened to the nightly? I have seen lot fixes on the change log but nightly hasn't been updated since March 2:(
[Samsung Galaxy Nexus] mondragon21:
Oh ok:(
[Samsung Galaxy Nexus] onelovekir:
Sorry for the late reply but I'm on 2/16 build.
[Samsung Galaxy Nexus] onelovekir:
just updated to the 3/17 build and I do not have any LTE now...guess i'm nandroiding back to my 2/16 build

---------- Post added at 08:15 AM ---------- Previous post was at 08:11 AM ----------

why does it seem like this carbon thread is so dead, but the JB carbon thread was always rockin!
[Samsung Galaxy Nexus] jcruz767:
Same here with LTE and I know this is one of my favorite roms just because I always found it so clean.
[Samsung Galaxy Nexus] onelovekir:
I know for sure the 2/16 build has LTE working. I will try to pinpoint when and where it went wrong and I will report back. It just seems like no one is monitoring this thread for the bug issues and whatnot.

UPDATE : so far 03/01 is the latest build with working LTE for me. I'll keep trying later builds as the day(s) progress.
[Samsung Galaxy Nexus] onelovekir:
has anyone on the carbon dev team figured out why since the 03/01 build that LTE has not been working? what changes to LTE was made that would affect the new builds? can we just swap out files to make it work on new builds?
[Upgrading, Modifying and Unlocking] jinks420:
Please can someone help me. I have an SPV M2000 and tried to update the software using the official orange site. Well It's all gone Pete Tong. I have a blank screen with the word serial at the top and the version number at the bottom. Have tried a hard reset. Nothing happened. Active sync cannot detect my phone. Please tell me what I have to do to fix it. Thanks.
[Upgrading, Modifying and Unlocking] Rudegar:
read this ?

http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel
[Sprint Samsung Galaxy S 4 General] happyoutkast:
reserved for future use
[Sprint Samsung Galaxy S 4 General] cruise350:
Another guide on how to root your S4!! Yeah!! And way to complicated again. Let me give you my simple guide and easiest method. This method also doesn't trip the knox warranty counter.

1. Turn on usb debugging on your phone.

2. Install Samsung USB drivers. If not already installed.

3. Connect your phone to your Windows PC. (No need to enter download mode, just connect as an MTP device.)

4. Run Safe Root .bat file found here & attached below(unzip the bat file from the zip file): http://www.droidviews.com/root-verizon-galaxy-s4-sch-i545-on-android-4-3-vruemk2/

(This file works on Sprint, Verizon, and AT&T so don't worry about the Verizon reference)

5. Follow instructions on screen and profit.

If you want a custom recovery installed, WHICH WILL TRIP THE KNOX WARRANTY FLAG, download goo manager from the play store and install TWRP.

Now that was easy!
[Sprint Samsung Galaxy S 4 General] ibcenu:
Dude cut OP some slack, I got my s4 about a month ago and can honestly say that after reading all I can about rooting an out of box s4 with knox/4.3 and mk2, no mod has set a sticky in place to explain a simple way.

All I hear is all the prior MK2 people whining about how we should read.. Guess what, we do, it's not as clear cut as pre-knox, and I can promise you, if you recently came from another phone, you would be in our boat.

Ive read where your safe root gives all your private info to someone other than nsa. Oh, that sounds like something I want to do.. Is it true? No clue, but I'll pass to be safe

All the countless posts, threads would go away if a mod would simply put a sticky near qb77's, that way we wouldn't be posting and whining to drive you all nuts!

By the way, thank you to the OP for taking your time to do this, it's more than most would do
[Sprint Samsung Galaxy S 4 General] cruise350:
Well now there are 4 threads on the first page of the general section on how to root MK2. Besides the fact that cf autoroot works on all versions of the software and is the reason why the mods haven't stickied another thread since qbkings method is still valid. Safe Root is not the Chinese method and is safe to use. And if this forum didn't need another simple thread that is actually way over complicated. As others have said, a little searching will turn up the answers. I don't mean to rain on anyone's parade but at least when I added my post, I offered a truly simple method to root opposed to the OP.
[Sprint Samsung Galaxy S 4 General] ibcenu:
Many people have reported issues with chain fire method on newer preloaded 4.3 phones, so how can you say it works on all..

Others have reported safe root, not safe

It's just way to many threads, to many people reporting different issues with (after mk2) newer phones, to say that what's on the 1st page works for everyone

So my 02 cents worth, a sticky of after mk2 newer phones root method would be very helpful.... Ask anyone who has a newer preloaded phone
[Sprint Samsung Galaxy S 4 General] daniel4653:
Saferoot and Kingo app are very easy to root. You literally click one button.
[Sprint Samsung Galaxy S 4 General] princebabyeater:
Safe root is easy, but can I flash a recovery simply by installing goo manager and flashing from inside the app? I've been flashing and rooting since the g1, and honestly this mk2 update is difficult to figure out. There are a lot of mixed answers out there. So I appreciate this post very much. Thank you sir.
[Sprint Samsung Galaxy S 4 General] daniel4653:
Installing recovery will trip Knox.
[Sprint Samsung Galaxy S 4 General] slothicka:
If this is correct, can I just do this to flash custom rom without having root first? Not really worried about knox, as surely there will be a fix..eventually?
[Sprint Samsung Galaxy S 4 General] cruise350:
Goo manager requires root.
[Sprint Samsung Galaxy S 4 General] princebabyeater:
No, a custom recovery is still required to flash a different rom. In order to first flash a custom recovery, root is required.
[Moto X General] nated0gg618:
i am trying to root my sprint moto x running 4.4 kitkat and im using videos from youtube on how too (ill post link in this tread, for you guys to view) in the first video after i installed the 2 packages, my adb did not have the .exe it was just adb, but i continue on with the video and after i edit the path, (i check it several times) the command adb is not working, im getting that it was not recognized internal or external. but if i click on the adb it does show on the things as if it would in the command prompt, but it has to work in the command prompt and wont, and es i ran it as an administrator too

it wont let me put the links in because im a new member

i cant figure out why its not working someone please help thanks
[Moto X General] nhizzat:
No idea which guide you used nor no idea what you've already done. Kinda difficult to help since we'd be throwing darts blindly.

Your best bet is to post your questions in the YouTube video comments.
[Moto X General] ken1645:
Did you try reading the stickied post about rooting? http://xdaforums.com/showthread.php?t=2603358
[Moto X General] hovax615@hotmail.com:
The only thing that stopped me was the alegebra equation.... Not the best in algebra....
[Sprint HTC One (M7)] jeremyp1:
I am wanting to download the Google edition of the 4.4.2 kit Kat update for the Sprint HTC One but am having no luck, can someone help me? I need a sense Rom and I don't like the new update Sprint provides. I'm currently on viperrom 3.5.0 because they don't have the newer versions for Sprint. Everything I look for good Roms they say I need TWRP 2.6.3.3 but the Sprint version is only 2.6.3.0. I'm just sad about this I really want the Google edition.
[Sprint HTC One (M7)] Sloth:
Use the latest version of TWRP,CWM, or PhilzTouch and you should be ok
[Sprint HTC One (M7)] weidnerj:
I don't think that you can run Google edition. That is a GSM version and not CDMA. I would wait to see if someone can confirm that before you hose your phone. Know that they have unbrick directions for those that flash the GSM version on Sprint (which is CDMA).
[Sprint HTC One (M7)] jeremyp1:
I actually set my phone to gsm because I have a bad esn and i SIM unlocked my phone, the HTC one is everything compatible
[Sprint HTC One (M7)] jeremyp1:
I can't find a better version of twrp for Sprint everything says they need 2.6.3.3 and when I try it fails every time
[Sprint HTC One (M7)] Sloth:
2.6.3.0 is the latest version for Sprint

Try CWM 6.0.4.3

PhilZ Touch
[Sprint HTC One (M7)] jeremyp1:
How do I flash a different recovery onto my phone?
[Sprint HTC One (M7)] Sloth:
Same way you flash TWRP
[Sprint HTC One (M7)] jeremyp1:
I dont remember how I did all that without relocking my phone. Do I use a computer? I really can't recall and don't know how to replace the twrp
[Sprint HTC One (M7)] Sloth:
Download the recovery you want

Put the file in your platform tools folder

Open a cmd window from that folder

Type adb reboot bootloader

It should say fastbootusb

Type fastboot flash recovery recoveryname.img

Type fastboot erase cache

Done
[Sprint HTC One (M7)] jeremyp1:
thank you im going to try it out
[Sprint HTC One (M7)] jeremyp1:
I am backing up my phone because i like the rom and everything on my phone right now, is taking forever, but i just realized it isn't a sense rom like i thought it was. do you know if there is a way to get the phone to work with the sim unlock because the guy who posted the guide to sim unlock said i have to have a sense rom for the sim to work properly. it works right now i just dont want for it to not work and not be able to fix it
[Sprint HTC One (M7)] jeremyp1:
it failed again
[Sprint HTC One (M7)] Sloth:
I know nothing about sim unlock

I would suggest running an RUU and start fresh
[Sprint HTC One (M7)] Kraizk:
Setting the phone to GSM and owning a GSM phone are two different things. Flashing a GSM rom on the Sprint One

WILL NOT WORK
[Sprint HTC One (M7)] im0rtalz:
The easiest way to flash twrp is to just download Goo Manager and select install openscript recovery.