yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] bubbly193:
A ROM for those who want to return their device to stock without replacing FireFireFire and their custom recovery. One possible reason for a switch is that on some non-stock roms, Kindle for Tablets can't sync to the store.

***IMPORTANT NOTICES***

**PLEASE RUN "FIX PERMISSIONS" (IN TWRP UNDER "ADVANCED" TAB, I'VE NEVER USED CWM, SO I"M NOT SURE WHERE IT IS THERE)**

**ALPHA STATE ROMS, TESTING IS INADEQUATE (PLEASE DEBUG), BRICKING IS A POSSIBILITY, YOU ARE WARNED**

What it is-

*A truly stock from, apart from SU and Superuser.

*Based on Kindle Fire 6.3.1 and 6.3.2 system Sofrware/Android 2.3.4

*For the First Gen Only

What it isn't-

*Modaco

*Amazon's default 6.3.2 ROM, which isn't rooted and replaces the recovery and FFF boot loader.

What is included-

*SU

*Superuser.

*As it is stock, a PC/adb will treat it like a standard KF

*Basic Unix Utilities (DD Etc.) on the 6.3.2

What isn't included

*Everything else, including a custom launcher and the play store (fear not, you can install them yourself.)

6.3.1 APLHA

LINK: http://d-h.st/WRnL

6.3.2 + Utils ALPHA

LINK: http://d-h.st/6BL6

6.3.2 + Utils BETA (WORKING NO SPUERUSER/SUPERSU)

LINK: http://d-h.st/ceRR
[Kindle Fire Android Development] sd_shadow:
Had Twrp 2.2.2.1 and FFF 1.4a installed

Downloaded your Otter-Stock-ROM.zip, verified, md5:74669b2d85d7e5f32e392ebf1d600edf, installed in twrp,rebooted.

Installed root checker, and root browser, both have failed to get root access.

Wiped everything in TWRP and reinstalled same thing, no superuser.

Install script looks good, at a glance, but must be missing something...

rooted with Saferoot, now superuser is installed, and working.

Everything else looks good, but did not sign in to amazon.

Edit: did not try signing in to Amazon
[Kindle Fire Android Development] bubbly193:
Found the problem, I left out the Superuser app. It should be rooted, but I left out the root management app. I'll fix this. I'll look into the amazon account problem as well.
[Kindle Fire Android Development] sd_shadow:
I did not try to sign in to amazon.
[One (M7) Q&A, Help & Troubleshooting] mssrivathsan:
Hello !

I own a HTC One and somehow I made the partitions corrupted. And so I am not able to mount /system /data and /cache. I am not even sure if the partitions exist. I tried to run cat /proc/emmc and the following was the result :

The following is the output of fastboot getvar all

Once I tried to clear my cache memory and it got stuck in the middle. When I tried to reboot the device into recovery this error occured and I'm stuck since then

I tried the methods mentioned in this thread http://xdaforums.com/show...2512105&page=3 But that doesn't seem to work for me for some reasons I'm not sure what. Any help would be much appreciated. Thanks in advance
[Fire TV Q&A, Help & Troubleshooting] QA Bot:
Q&A for BusyDrop 1.02: SSH & Busybox for the Fire TV

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for BusyDrop 1.02: SSH & Busybox for the Fire TV. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Fire TV Q&A, Help & Troubleshooting] random llama:
Since this also installs BusyBox, it strikes me as a bit silly to use hard coded binary wrappers instead of shell scripts. Anyways, I've partially replaced them like so on my FTV:

#!/system/bin/sh

/system/xbin/echo "Starting dropbear..."
[ -n "$1" ] && SSH_PASSWORD="$1" || SSH_PASSWORD="password"
/system/xbin/su -c "/data/jocala/ssh/dropbear -A -N root -U 0 -G 0 -C "$SSH_PASSWORD" -R /data/jocala/ssh/dropbear_authorized_keys"
/system/xbin/sshstatus

#!/system/bin/sh

/system/xbin/echo "Killing dropbear..."
/system/xbin/su -c "killall dropbear"
/system/xbin/sshstatus

#!/system/bin/sh

/system/xbin/pidof dropbear > /dev/null
[ $? -eq 0 ] && /system/xbin/echo "Dropbear is running." || /system/xbin/echo "Dropbear is NOT running!"

I assume /system/xbin is already in $PATH when these scripts are run, but used the full paths because I'm too lazy to find out.
[XDA Assist] XDA Visitor:
Hello, could anyone recommend me some kind of chinese or w/e tablet that is 150$ or something around that price. I would prefer to have root on it.
[XDA Assist] Perseus:
Please Review and post in **DEVICE SUGGESTION THREAD** -- Not sure what device to buy? Ask here!

You'd need to register in order to do so.

Thread closed. Thank you.
[Defy Android Development] Octanium91:
Recovery BootStrap (TWRP) - Motorola Defy\Bravo

Version:

4.0

Install Recovery BootStrap (TWRP) for Motorola Defy\Bravo via a USB cable. For computers running the Windows\Linux (port version) operating system.

Download: (

Windows

: MEGA / Google Drive) | (

Linux

: port by nastys post>>)

Install Recovery BootStrap (TWRP) you can right out stock firmware (without custom recovery) with superuser. :cool:

Recovery BootStrap (TWRP) - for the recovery say thank Quarx, after installation, you can install the rom CyanogenMod from Quarx for December 2014 (but do not forget about

resize.zip

).

Can be installed on Defy (MB525), Defy Plus (MB526), Bravo (MB520).

Requirements for smartphone:

Enable USB debugging

Superuser (ROOT)

Free space on the memory card of 100 megabytes

Instructions:

1. Download the archive

2. Unpack it somewhere else with a short path, for example D:\andro

3. Connect your phone via USB cable ("debugging on USB" should be included)

4. Run the

install_bootstrap.cmd

5. When you see the label "Let's Start? =)", press any key

6. If the superuser ask permission for full access "ADB Shell", allow.

7. After installing the smart phone will automatically restart

!IMPORTANT! after restarting the Stock firmware will not start!, but you will have BootStrap (TWRP) so you can safely install custom firmware\rom

Change log:

V3:

Changed how the script

Fixed installation errors recovery on Android 4.x and later

V4:

The script changed drastically

After installation removes trash from the memory card (so far only on Android 4.x and later)

Made for normal (mortals) users :), before you start the installation script checks (by model) which smartphone connected to the computer, if your smartphone is not supported script report it and stop installation, if supported will give something "Device: MB525".

Serviceability checked on the Chinese 231 (Defy) firmware with superuser (what say thank borndead), and on the Asian 231 (Defy) :)

Questions\FAQ:

Error "[ERROR] Verify device!", what to do?

Error "[ERROR] Verify device!", it is may mean the following:

1. You have not enabled USB debugging

2. Your smartphone does not support this Recovery. (only for MB525, MB526, MB520)

3. You need to confirm the action ADB on your smartphone

4. Or you have some other connection problems

Stock transition to CyanogenMod 11 of Quarx

Stock transition to CyanogenMod 11 (firmware and find all necessary files can be here) of Quarx in short (generally as described on the website Quarx, only simpler and under Windows)

1. Install Recovery BootStrap (TWRP) via USB

2. Enter Recovery install resize.zip

3. Restart your smartphone

4. Install CyanogenMod 11 and GApps
[Defy Android Development] borndead:
Good work, comrade! I flashed CM11 on the Moto Defy - everything works!
[Defy Android Development] starbright_:
We did observed some cases, where a "new life (resized)" Defy is not booting anymore. Only solution was to reflash SBF and start from scratch.

Does this mean, it is possible to recover TWRP from PC? That would be a step a head!
[Defy Android Development] nastys:
This is amazing! Everytime I needed to reflash the stock ROM I needed to install cm10, then cm11, then new bootsrap etc...

Unfortunately I don't use Windows...
[MENTION=5849688]Octanium91[/MENTION] Would you mind if I port your script to GNU/Linux? :)
[Defy Android Development] Octanium91:
I tried to do something like that, is not yet happened. Perhaps in the future even try :)

Maybe. If Iunderstand with GNU/Linux scripts :)
[Defy Android Development] Octanium91:
The new version, V4

The new version, V4

Changes:

The script changed drastically

After installation removes trash from the memory card (so far only on Android 4.x and higher)

More debugging: Now the script itself is not closed, and tells the user exactly what happened.

Sorry debris removal only works on Android 4.x and later.
[Defy Android Development] nastys:
Linux port done!

[MENTION=5849688]Octanium91[/MENTION] I ported it to C++ (for Linux only at the moment). Please add it to the first post :). Here is the link: MediaFire | MEGA

On Ubuntu just

mount

the ISO

as image

(not archive) then click 'Run' (or you can also extract the ISO and run the executable directly). It works on x86 (32 bit) and x86_64 (64 bit) CPUs. The source code is also included in the ISO. Tested on Ubuntu 14.10 and 16.04 (64 bit).

I tested it with both stock 2.3.6 rooted and CM11. It seems that the stock ROM won't boot after flashing the new bootstrap, but the recovery works fine ;)

Also your version has a very bad bug: it flashes Defy bootstrap even on Bravo!!! It should flash Motorola Bravo specific bootstrap instead. My version only works for Motorola Defy and Defy+ at the moment, but you can edit the source code. EDIT: they are the same file with different names. I updated my version to support MB520.
[Defy Android Development] evilinheaven:
After run the command script, when i boot in TWRP SDcard shows 0mb.

Already tried flashing the SBF recommended by quarx and after that the root SBF, but the result is always the same.

With CM recovery i can see the SDcard properly, but after the resize, or bootstrap, i always get 0mb at SDcard.

Any help?

Thanks!
[Defy Android Development] nastys:
Format your SD card (to FAT32) or use another one.
[Defy Android Development] Aceofzeroz:
Greetings guys, I'm a user from the Atrix 2 section and a part of the current device supporters there. It's a pleasure to finally post here, 'the domain of Quarx' haha.;):)

I was wondering if this recovery is able to flash and boot android Lollipop 5.0 roms yet? If so, then is there some way to port it from source to my or other similar Moto devices in the OMAP bracket with locked bootloaders?:confused::o

I'm an Android novice, but I'm experienced in building custom recoveries and roms, as well as beginner git commands, so no need to hold anything back, lol.:D:cool: I appreciate the work you're all doing here, please continue to make the difference. Thanks for reading this and take care!
[Defy Android Development] Octanium91:
answer

Hi!

flash and boot android Lollipop 5.0 roms - just can not say, but it is theoretically possible (need to check).

If so, then is there some way to port it from source to my or other similar Moto device - No, this is not possible (specifically, in this case). BUT this method you can set recovery to another smartphone (it is theoretically, need to try)

Here recovery that are in the public domain, I think that they can install Lollipop 5.0 roms - TWRP2 \ Safestrap

Moto devices in the OMAP bracket with locked bootloaders? - Most likely will not work, but no one stops to try :)
[Defy Android Development] Aceofzeroz:
Many thanks for the prompt and well ordered reply!:D I'll look into your suggestions and I'm aware that there aren't many available recovery software for our locked bootloader phones.

We were actually trying to get Safestrap working on our device since last month, but it's failing to work correctly in booting our kexec roms.:( So I thought I'd ask here since the Defy works by using the 2nd boot like us, but it's still under investigation. Thanks again for your assistance, we're not out of the game yet and we'll get things rolling eventually. Take care!:cool::thumbup:

Sent from the Ace's MB865 using Tapatalk
[Defy Android Development] LoeWn:
Error. More than one device and emulator

what am i doing wrong?
[Defy Android Development] Octanium91:
Perhaps you have not enabled USB debugging

Requirements for smartphone:

Enable USB debugging

Superuser (ROOT)

Free space on the memory card of 100 megabytes
[Defy Android Development] LoeWn:
I did enable usb debugging :cowboy:
[Defy Android Development] Octanium91:
You can send us a screenshot?
[Defy Android Development] marcooleo:
I had a successful installation of a december build and twrp 2,6x installed, everything ran just fine. But when the CM tells me there is a update and i download it does not install from recovery, get errormsg. Also apps like rom manager pro tells my phone is not compatible with any updates, and that i should install CWM recovery. So is it possible to install a real CWM on a defy mb526?
[Defy Android Development] Haldy:
Hi, I flashed Recovery BootStrap v4 on the Defy MB525, but its not working. After flash and reboot, phone starts booting, but it ends up with the following screen.

Doesn't matter if I choose Recovery or continue. I can press the menu button (to choose recovery) and nothing happen, till the 3rd press. Than display goes black and thats all :(.

Any idea where could be the problem or what I'm doing wrong?

Edit: maybe its related to the bootloader version, which is 09.10
[Defy Android Development] Octanium91:
Based on first screenshots, Recovery installed. Now you need to install system.

Than display goes black and thats all - maybe have to wait
[Defy Android Development] Octanium91:
In principle it is possible, but it does not make sense.
[Nexus 7 Q&A, Help & Troubleshooting] spark001uk:
Ive had a good look but i cannot find anything on this particular behaviour. Please could anyone help, its driving me round the bend now!

The battery will not charge past about 15 to 20%, no matter what, or how long I charge it (used original charger, plus another couple rated at least 2A, no difference). Ive had the back off and measured with a multimeter directly across the battery at this point, which reads around 4.2v, which is fine, thats what a fully charged cell should be. However, in this fully charged state, with a number of battery apps that read voltage from the os, it reports only 3.7v. Similarly, when the unit reports around 3.5v, consequently turning off, the battery is actually still at 4v!

I just dont get it, i cant seem to get it to correct itself, ive tried everything. Does anyone have any other ideas? Cant be the battery, its reaching full charge just fine, and is not nearly becoming discharged.
[Nexus 7 Q&A, Help & Troubleshooting] spark001uk:
This is strange, have a look at this battery history screenshot, after staying for hours on 20 to 30% it jumps straight to 2%, while still on charge. And also once its shut down, i turn it straight back on again and its miraculously got 20 odd percent back in it. As you can see it keeps doing it. Anyone?
[Nexus 7 Q&A, Help & Troubleshooting] luckyrumo:
Someone recommended me this app against slow charging problems in another thread on xda. However I haven't had time to try it out yet.

Years ago my Moto Defy+ only charged to 80% because I had flashed the wrong firmware. The correct one restored the normal behaviour. So, it's just an idea, but you could try to flash a factory image, to make sure it's not a software issue.
[ONE Q&A, Help & Troubleshooting] ksekhar:
I've a problem with any CM11 or CM12 ROMs. When I make/receive call, screen stays dark. I cannot turn it on with power button or volume keys or anything until call ends. Accidental wake up is Off. I've no problem when using ColorOS. This is making phone unusable. Appreciate help, please. Thanks.

Sent from my A0001
[ONE Q&A, Help & Troubleshooting] nchantmnt:
Sounds like an issue with proximity sensor. Mine was not functioning propperlz as well after trying color is. To fix your problem you have to flash stock images and then reflash your desired ROM.

And yes you can skip flashing recovery and userdata partition images ;)
[ONE Q&A, Help & Troubleshooting] ksekhar:
Thanks, will try that out.
[ONE Q&A, Help & Troubleshooting] ksekhar:
It worked, thanks [MENTION=4460139]nchantmnt[/MENTION]
[ONE Q&A, Help & Troubleshooting] nchantmnt:
Sure ;)
[ONE Q&A, Help & Troubleshooting] blueray2009:
help

I'm new to this, and my phone is unusable HELP

how do I do this?

thank you
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Did you recently change from KitKat to Lollipop or from Lollipop to KitKat?

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] nchantmnt:
First we need to know what you did before. Have you flashed any Rom? Cm11 -> cm12, coloros, oxygen OS? or from 5.x base downgraded to a 4.4 based Rom?
[ONE Q&A, Help & Troubleshooting] blueray2009:
thank you

I had previously tried to flash the new CM12.

Well I flashed the stock 44s, and the problem was there. after an OTA to 5Q it solved the problem.

now all is ok.

do you recommend flashing the CM12 or is it still too buggy...

thank you for your time

nuno
[Nexus 5 Q&A, Help & Troubleshooting] gobak:
Hello,

after updating the system to 5.0.1 I have lost my IMAP. No matter what I try the outgoing server setup ends with "couldn't open connection to server" message. K-9 works flawlessly though... any ideas please?
[8125, K-JAM, P4300, MDA Vario ROM Development] the-equinoxe:
At last:

Now we have a way to have a big button Dailer Skin WITH Smartdail.

I have rebuild the dll from scratch, and now we can use it for dailerskinning WM6.

The attached skin is a BETA, this means not everyting looks nice, but it is a great starting point for making new skins, or adapting existing skins.

To do (DLL):

-Layout tweaking (I am not happy yet with the overal layout)

Please post your suggestions here, and I'll consider them, and the good ones will be incorperated into the dll, and eventualy into the dailer-skin builder I am working on.

Skin:

See attached jpg:
[8125, K-JAM, P4300, MDA Vario ROM Development] marscandybars:
OMG I freaking LOVE you man! It looks amazing! I am going to keep it! It looks a lot better than the standard layout, and GREAT for dialing with the fingers (I have an invidisible shield screen pretector so its practically scratch resistant). Not only that, for some reason, it FIXED my redialing issue. With the new crossbow rom, it wouldn't call the most recent person on the history list because it was organized in alphabetical order. A history log should obviously be organized by TIME. But i dunno man, it works and I just wanted to say kudos! U have really made my device a million times easier to call vai touch screen. To begin, touch screens alone are rather annoying to call from because there simply isn't any "physical push-back" button response. But with the large buttons, its practically FLAWLESS. THANKS AGAIN!

It is something i would consider using permanently. However some minor suggestions would be to shrink the text of the list of last people called so you and possibly widen it across the screen, so you could see more than just two recent entries.
[8125, K-JAM, P4300, MDA Vario ROM Development] the-equinoxe:
Thanks for your comments :)

As for the sugestions:

The backspace button is a bit in the way for the calllist, but I'll try to widen the list and still keep a backspace button in one form or another, or else find a way to edit the fontsize of the list.
[8125, K-JAM, P4300, MDA Vario ROM Development] pencilcase:
great work on that! I wish I knew how to help you fix the last few things or make new similar skins (colours). If you need any help let me know!
[8125, K-JAM, P4300, MDA Vario ROM Development] the-equinoxe:
One step ahead

Well, I am working on a program that will create the skin for you.

Just choose the background, select the button-layout, adjust the transparency of the buttons, press: build cab, and presto, you have created a new skin :)

I am beta testing a part of it now, looks very promissing :)
[8125, K-JAM, P4300, MDA Vario ROM Development] SpH1nX:
but there isn't video call button?
[8125, K-JAM, P4300, MDA Vario ROM Development] the-equinoxe:
For the wizard??

Never saw this function on the wizard wm6.
[8125, K-JAM, P4300, MDA Vario ROM Development] chowchow1678:
It's work on my dopod 838 (wizard)

Thanks a lot.
[8125, K-JAM, P4300, MDA Vario ROM Development] easymob:
thanks great skin works well
[8125, K-JAM, P4300, MDA Vario ROM Development] the-equinoxe:
Updated Beta new layout

V2 is out.. (BUT STILL A BETA)

In this version I have incorperated the suggestions from Marscandybars.

Thanks for the input MCB!

[edit: works also with Faria's new WM6 ROM ]

The preview:
[8125, K-JAM, P4300, MDA Vario ROM Development] SpH1nX:
Sorry man i didn't notice that i was speakin' on the wizard forum.

I was referring to hermes.
[8125, K-JAM, P4300, MDA Vario ROM Development] the-equinoxe:
If you would send me the tapres.dll and the tapres.dll.0419.mui I could try to make it compatible with the hermes.

However I can't test it because I don't own a tytn (yet ;) ).

Best regards,

EqX
[8125, K-JAM, P4300, MDA Vario ROM Development] techlogik:
Very nice...I used this for WM5 and it was cool too.

Thanks for the work, I really needed this, keep 'em coming.
[8125, K-JAM, P4300, MDA Vario ROM Development] jcostantino:
This version works on WM5? I can't upgrade to WM6 year because BT DUN has been removed so I'm stuck for now.
[8125, K-JAM, P4300, MDA Vario ROM Development] w4rmk:
FYI this is working great on my Cingular 8525 (Hermes) with WM6.
[8125, K-JAM, P4300, MDA Vario ROM Development] danik_iceman:
Wow! Really nice dialer! I love it!

I wonder if you could do the same thing with the dialer from the wm5 that looks cool. I downloaded from somewhere and it is the dialer in Vista style! I am attaching it.
[8125, K-JAM, P4300, MDA Vario ROM Development] yozh:
Thank you very much for this before I saw this post I was about to give up on the wm6,(fingers are too big for the small dialer)
[8125, K-JAM, P4300, MDA Vario ROM Development] yozh:
1 question,

When I start dialing and numbers come up if I press the down on the pad and then the middle pad button it shows me the last dial screen, before it used to dial the number ?
[8125, K-JAM, P4300, MDA Vario ROM Development] marscandybars:
I'd love to help... but i don't quite understand the question... u might wanna rephrase that... i read it a couple of times and i'm so confused as to what you are asking ...
[8125, K-JAM, P4300, MDA Vario ROM Development] the-equinoxe:
It's a feature from wm6..

You 'll see the contact info, and then dail.
[8125, K-JAM, P4300, MDA Vario ROM Development] yozh:
Ah I see,

Ugly feature lol, have to press 5 times to dial number. Ah well atleast the buttons are big and it does predict the number :)

Tahnks for the reply
[8125, K-JAM, P4300, MDA Vario ROM Development] zakhir_n:
Hey this is a great skin. Loved this in WM5, and now we have it for WM6, thanks a lot!

If you wait to immediately dial the number, don't press the center button, press the send button. It won't go through the contact to dial the number.

Thanks again for the great work.