yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] corey_r:
How can you tell if your phone does this? Can someone explain to me what it looks like
[HD2 Android Q&A, Help & Troubleshooting and Genera] elesbb:
I've been reading .. and in my readings I've read different people saying different things . I heard running task29 a lot can cause bad blocks .. and I flash a lot of ROMs . So I created a task29 zip flash from recovery which formats all nand partitions 3 times in a row to wipe out everything . Is that good for the memory and is that enough to wipe everything clean or should I use task29 every time and not worry about that being the cause of bad blocks ? In short , which is safer ?
[HD2 Android Q&A, Help & Troubleshooting and Genera] samsamuel:
Well do the math,, task 29 wipes every block once, your zip wipes some three times, which would you suspect as being there times more likely to end in bad blocks?

To be honest what's the point? In 999 out of 1000 flashes its enough to do a 'wipe data factory reset' and then flash.
[HD2 Android Q&A, Help & Troubleshooting and Genera] elesbb:
Well , in every ROM thread ive read , it says to task29 before flashing . and i thought task29 was a more "harsh" way of wiping the nand . Like a format , does it not just clear the blocks without writing to them ? I personally think either way is still "not good" for the flash memory . But i could be wrong . And i always thought there were "leftovers" from just doing a factory reset ?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Marvlesz:
In my opinion, task29 is very unnecessary.

Only do it if your device is having issues, otherwise flash roms and bootloaders directly without task29'ing.

By the way, by "task29" they mean empty-rom.nbh .. not empty-rom.zip .

As for the .zip, a full wipe does the same.
[HD2 Android Q&A, Help & Troubleshooting and Genera] elesbb:
A full wipe cleans all partitions of the nand ? i thought it just did /userdata . and thank you thats what i thought task29 was . but is flashing an empty .nbh worse then running the format command ?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Marvlesz:
Let me clarify a few things for you:

Task29: removes everything off your device's internal memory, when you boot your phone after a task29 you will get stuck at bootscreen (first splash), because there is nothing on your device (no bootloader).

Under CWM:

Wipe data/factory reset is different from format that can be found in (mount & storage):

Wipe data/factory reset: does not remove your OS, it will only delete your personal data retaining your ROM intact.

But a format will completely remove your ROM and you will be stuck at the bootscreen if you do so.

Every thing under CWM does not touch your device's bootloader (cLK or MAGLDR), and they only affect the Android ROM within CWM.

Hope this help you :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] elesbb:
Yes this i knew thanks though . My question is this , is it safer to wipe the bootloader off using task29 , then starting over , or is it safer to format all partitions of the NAND in CWM before changing to another ROM ?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Marvlesz:
I don't know which is safer. (or in other words, I don't know which is dangerous :D )

But if you must do a wipe, I'd recommend "Wipe data/factory reset" . That should do the job. (Most roms format partitions upon installation anyway so I coudn't care less :D )

:)
[HD2 Android Q&A, Help & Troubleshooting and Genera] samsamuel:
it also wipes cache partition, the sd-ext partition on your sd card, and clears the .android folder on the fat32 part of the sd card. These last two are the reason many roms wont boot after flashing, even with a task29, since those two areas aren't touched by task29 (or your format zip presumably)

Im with Marvlesz, steer away from task29, , whats the use in removing magldr and cwm only to reflash it?

For me, a clean install would be ,,, cwm - wipe data factory reset - flash the new rom.

Only if the fresh rom doesn't boot after a few times rebooting (and performing a wipe data on the fresh rom, just like how in winmo it was recommended to do a hard reset straight after flashing) would i consider a task29.
[HD2 Android Q&A, Help & Troubleshooting and Genera] elesbb:
Okay thanks ! I wasnt sure if the single format they do upon installation was enough . Ive been getting small app crashes in some ROM's ive tried , so i formated each partition at least once before flashing the ROM and it fixed it . I remember when flashing WinMo ROMs a task29 was a must on my Rhodium . But i was pretty sure wiping the partitions in CWM was indeed good enough . I just kept getting confused when each ROM's thread said YOU MUST TASK29 so i was like well now im just confused lol . I'll mark thread solved

Thanks again guys !
[HD2 Android Q&A, Help & Troubleshooting and Genera] showlyshah:
For me clean install means first do a factory/data reset. Will clean ext, and previous roms leftover folders. Then i will go to mounts in cwm. Do format every thing i got except sd.

On next boot, magldr, cwm is there. But no boot or rom. Then from magldr, i go to cwm and install the zip. I barely had done task 29 2 times in 3 mnths, just for repartition. ( though its not needed for repartition).
[Droid 2 General] bobturismo:
Trying to help a buddy with his Droid 2 (i do not have one). The first one he had wasn't updated i assume, then he had Verizon replace it with a new after it broke.

According to him the new one had an updated ginger bread which says 2.3.3.

He says it's slow and he doesn't seem to like it, can the older version be installed? Which one is it?

Is there something in there that slows the phone down? Mine had CIQ which sent "anonymous" info to them.

I know the best thing is to root and do a custom ROM, I just want it to work for him the way it was before.
[Droid 2 General] MissionImprobable:
It's probably slow because of all the bloatware Verizon puts on it. It makes a lot of unnecessary social media crap, amazon, blockbuster, and other things run in the background all the time. He could root the phone and freeze the apps, or get rid of them completely. I suggest you point him to droidforums.net or androidforums.com and tell him to start reading up on rooting and other mods he can do his phone.

If he want's to go back to Froyo (2.2) he just needs to look up "Droid 2 SBF" on youtube and he can see a walkthrough of how to do it, though all the VZ crap is still going to slow it down.
[Droid 2 General] bobturismo:
Thanks for the info that what i was looking for
[Member-Found Deals] TravisAntonio:
Hello people I want to buy an Atrix Laptop Dock shoot me your best offers.

Thanks a lot and God bless you all.
[Member-Found Deals] chils41:
thanks for the blessings BUT...

YOU POST IN WRONG SECTION.

post in Wanting To Buy

thnx.
[Member-Found Deals] TravisAntonio:
My bad :( I didn't read the "Accessories" line in WTB Section, because like 1 month ago it was only for phones.

Anyways THANKS A LOT :D
[Motorola Droid 3] redsox985:
INSERT USUAL DISCLAIMER HERE. I THINK (HOPE) YOU ALL KNOW THE RISKS BY NOW. Blah blah brick, blah blah not my fault, you know.

Well, using Willis111's Canadian Bell 2.3.6 build from here, somemadcaaant, ZOMBI3, and I have been slowly patching this up to work on the XT862.

I've made up a stock (tweaked for VZW) 2.3.6 ROM and a lightly debloated one as well. Both have the same build.prop tweaks for battery life, the usual wifi scan, as well as the camera video modes tweak, plus some other stuff tacked onto the end of the build.prop.

What we changed was the build.prop (IIRC, I used a Liberty3 one that I touched up to my liking), eri.xml inside framework_res.apk, and libmoto_ril.so to get this up and running on the XT862. Since, I have added in 5.7.905 system apps to get some things running (MMS messaging mainly).

I have flashed these without a wipe (over SD 4.5 I think) and it seems to be fine, although I've only had it running maybe an hour now, so I can't attest to battery life. It may be fine without a wipe, it may be better with it. IDK. :p

One note for HandCent users, go into HC, menu> settings> application settings> default messaging application> all(sms & mms). This should fix double texts.

NOT WORKING:

It seems the first boot bootloops. Just battery pull and restart. It should boot. I'm running this debloated build exactly.

My stock camera FCs when entering panoramic mode. 3rd party apps such as ProCapture still work. This will be addressed after I get 1% battery and power menu buttons added (Thanks to BuckMarble!)

Here's the links to my DropBox.

Bloated 02/23/12 20:04

Debloated 02/23/12 18:83

1% Mod Still getting reboots, experimental only

Dark Theme (incomplete theming, WIP)

Hopeful goals...

Working 1% Mod

Dark (WIP) & light theme

Power button reboot options

Pulldown power widgets

Pulldown music controls??

...and, I know how to do none of those. :D Anyone wanna do it or teach/guide me though it?
[Motorola Droid 3] buckmarble:
Oh boy! I can teach the reboot and 1% stuff(gotta dig up the code for this one, been a while) I've recently become quite the android.policy master. Lol. As for the messaging stuff, im not sure where to go with that one.

EDIT: noticed quite a few com files missing from the framework folder that our xt862 uses. Compare an xt862 vzw rom to this one and try patching in the missing ones and see if that helps with the messaging. In system/framework.
[Motorola Droid 3] redsox985:
Touched up the /system/framework folder with the missing files. If it isn't apparent already, I'm pretty new to this and really don't have too much of an idea of what I'm doing. Oh well, gotta learn somehow!

EDIT: Well, this didn't fix MMS, but it couldn't have hurt. Also, I've been getting some FCs from conversations.apk when receiving a text. I'll look into it tomorrow and keep working at this.
[Motorola Droid 3] ZOMBI3:
I cant wait to get back to my house, and have wifi again, and my pc! =D tomorrow morning for sure i will

Sent From My Dark Fire DROID3
[Motorola Droid 3] jchenny:
Why is the Debloated version removed?

Is there any problem with it? Because I am about to flash it now....
[Motorola Droid 3] buckmarble:
The next thing I would do is go through all the rest of the folders and compare file for file and see if anything else is missing.
[Motorola Droid 3] somemadcaaant:
Nice work,

@jchenny i'd prefer a bloated version to go nuts on anyways.

Definately deserves it's own thread to be sure, you will have reboot/screenshot power menu functions plus power widgets and whatever else is needed on the weekend unless some1 else wants to get it done? Looking at you buckmarble and ZOMBI3, i'm using my phone for oncall work this week.

Again awesome release, can't wait to try it.

Edit: Grab my giant APN list apns-conf.zip from my sig link below and see if that fixes mms, most providers have been added manually... could simply be the conversations app not working correctly with the cdma buildprop commands changed and/or rot.mot.phonemode.vzwglobalphone=1, swap out with the vzw versions of conversations.apk, mms.apk, messaging.apk, might also have to swap out the bluremail.apk, bluremailengine.apk and blursnmessagingengine.apok or perhaps use the aosp versions?

Could it be a google restoring settings thing, always gives me grief when i forget this after flashing lol.

-smc
[Motorola Droid 3] buckmarble:
I can get the power menu/widgets/etc stuff in. Would rather teach red how to do it though. Expand the knowledge base of the new developers. I like to give back what I've learned so that at some point we can all help each other. Hopefully your apn stuff fixes the mms problem he's got.
[Motorola Droid 3] redsox985:
Debloated is back up. I think all I changed was removing Blur Car Dock and adding in my preferred Google Car Dock. I believe I left the Blur Multimedia Dock intact.

I would like to learn this rather than just having it done as well. I'd like to further my knowledge on this kind of modding (do I dare call it dev, I feel like I haven't done much really) stuff.

@SMC, where is that APN list in your sig?

As I play with this, I'm going to try tossing together a build for myself (and others?) to test with 5.7.905 deodexed system apps from ZOMBI3's .zip. Also, Hash has a deodexed 5.6.890 build on his blog right? I'm blocked here on the school network.
[Motorola Droid 3] buckmarble:
Red, shoot me a pm with your email for gtalk.
[Motorola Droid 3] somemadcaaant:
True true, pardon my eagerness guys.

You will find the apn list on the top link in my signature, will be at the bottom of the page with the files.

I suspect you will have all the kinks out by the weekend, just in time for me to flash lol.
[Motorola Droid 3] redsox985:
Well, I patched up the APN file and that didn't fix it, but it did add "Verizon Wireless" to the status bar...time to revert or fix that. Hmm. Adding back the old APN file didn't fix it up.

FIXED: Hex edited some null entries into eri.xml.

Sent.

EDIT: 4:15 PM. I received a picture! It seems kind of weird how it came through, but it coming through is what matters. Hitting download doesn't do anything but just fail to DL, but again, I got a photo so...IDC!

This project, and subsequent thread, has become my baby. I keep wanting to work on it.
[Motorola Droid 3] raiden:
I can't seem to download the debloated version. Dropbox gives me a 404.
[Motorola Droid 3] redsox985:
Refreshed them...it should work now.
[Motorola Droid 3] ZOMBI3:
Well well, nice good job redsox, im dl the debloated, have you been able to send anything yet?, im leaving again tonight, so I haven't had time really to do any work today (long day) =/ but as soon as im free again ill take it on and try and beat it to you ;) adding all the features that is, buck and somemad, thank you for all the help into this you guys are awesome :)

Sent From My Dark Fire DROID3
[Motorola Droid 3] redsox985:
I believe I have the freshest build on my DropBox. IIRC, I removed messaging.apk and dropped in mms.apk and that enabled MMS messaging. For my purposes, it's a fully working build. I haven't had any errors. Keep me updated if you hit any.

I think I'm going to start adding a time stamp to my .zips, I can't keep them straight. :p (Now I've added date and time stamps to preserve my sanity, or what remains.)
[Motorola Droid 3] redsox985:
Oh yea! This is getting themed! I taught myself UOT Kitchen (it's so easy) and applied a META-INF workaround listed on their site to fix a flashing error and it's looking great. And is it just me, or does this boot quickly? Maybe I don't pay attention...

New links in OP.
[Motorola Droid 3] ZOMBI3:
Nice :) very good job :) theme, and one percent awesome :) already, haven't tried it though, I got stuck on after the safe boot menu something went wrong no big deal tho ill check it out keep it up though I wanna see that reboot and screenshot from you soon ;) way to go ! Congrats

Sent From My Dark Fire DROID3
[Motorola Droid 3] somemadcaaant:
Nice work, its all done lol.

I remember having media player control status widgets, or what ever its called, on my old LG optimus 2x and I liked it, very convenient - maybe we can port that over or use code, like adding the controls to the far right as you scroll thru.

If that's makes sense.

Definitely lots of performance tweaks in there for boot, memory and gui speed.
[Motorola Droid 3] redsox985:
I definitely want to implement more tweaks for battery life, speed, etc. Also, the 1% mod wasn't playing nicely with services.jar and causing reboots, so I marked that as experimental. I'm talking to BuckMarble on GTalk and he's helping me do this since my current knowledge is minimal in comparison.

EDIT: I'll be trying this later...

http://xdaforums.com/showthread.php?t=1437712 No dice. I need a tester device haha. This is so much flashing!
[Motorola Droid 3] davwman:
Tried both bloated and de-bloated and both would boot loop upon initial boot. Yes I wiped.
[Motorola Droid 3] redsox985:
I got that once or twice as well. Usually a battery pull and reboot would fix it, but there are new bloated and debloated ones posted. Check the date/time stamp in the file to see if you have the newest one.
[Motorola Droid 3] nemiroG1:
I'm having the same issue on an XT862 setup for GSM (TMo).
[Motorola Droid 3] redsox985:
I'm assuming you've done the needed GSM changes? If it bootloops, just battery pull and restart. I'm currently running the debloated link in the OP with that theme, so it DOES work. Just more kinks to sort out... *sigh*
[Motorola Droid 3] nemiroG1:
Got it to boot! That's the good news. The bad news is that I am getting tons of FC's on bluetooth, USB, and others. I have apparently also lost root. I cannot access USB settings to get it to connect to the PC to do anything. I cannot edit the build.prop due to no root. grrrrr.....

Yes, I did a full wipe.

This is last night's version, not the latest!

Not upset with the dev at all, just want the upgrade! :) Will dl the latest tonight, and give it another whirl.
[Motorola Droid 3] redsox985:
Sorry to hear that. This is weird that you lost root? I have flashed MANY tweaked builds of this and never lost root, many of which never made it here for various reasons. I wonder if I'm not hitting issues due to the fact that I flashed directly over SD4.5 with no wipe? My only suggestion is to try the latest build in the OP. I haven't actually tested the bloated version, but the only difference is that I took the 5.7.905 apps removed to make the debloated version and left them in.
[Motorola Droid 3] nemiroG1:
OK, got the latest one to boot. I still have root (yay!), and all seems well. However, the build.prop changes do not seem to be working to make GSM work. Have any other TMo/ATT users gotten this going yet?
[Motorola Droid 3] redsox985:
Well, I set build.prop to 4 CDMA, but I'm also assuming you changed that. You may have to swap out libmoto_ril.so and eri.xml as well, which are things I had to switch to get this working on VZW.
[Motorola Droid 3] nemiroG1:
Bear with me, as I am learning :)

I know where the ril is, but where is eri.xml stored? I will swap those out with ones from the XT883.
[Motorola Droid 3] redsox985:
Open framework_res.apk with a .zip manager and it should be in /res/xml IIRC. And tell me about learning! Buck has been taking me to school via GTalk lol.
[Motorola Droid 3] nemiroG1:
I am still working this. I moved the libril.so over, but that made no change. I tried replacing the eri.xml in frameworks-res.apk, but apparently I am not getting it signed right, because it bootloops with it. I have merged the build.prop changes in. Everything seems to work, including wifi, but no cell reception.
[Motorola Droid 3] redsox985:
Are you using APK Manager or APK Multitool? You can replace eri.xml with 7zip and not worry about it. Just drag and drop in the stock eri.xml.
[Motorola Droid 3] nemiroG1:
OK, I tried 7Zip, and I still get boot loops. Attached is the eri.xml file from the working GSM setup. I had to change the extension to .txt to get it to attach.

Can I get you to try to put it in the frameworks-res.apk for me? I cannot seem to get this right for some reason. Thanks!
[Motorola Droid 3] ZOMBI3:
Have you tried winrar? Using store when you drag it in if its zip already?

Sent From My BLAZING FAST DARK FIRE DROID 3
[Motorola Droid 3] nemiroG1:
Tried WinRar and 7Zip. Both give me boot loops.
[Motorola Droid 3] redsox985:
Weird. I'll try throwing it in there later today. Is that the eri.xml you used to get other builds up and running?
[Motorola Droid 3] nemiroG1:
It came from the working 2.3.4 build that is on the phone now. I tried everything I can think of with the build.prop, and no success. The ROM does not seem to recognize the radio, as it will list it as 'unknown' in the About Phone section. And yet wifi works.
[Motorola Droid 3] redsox985:
Honestly, this is mostly all over my head once we get into it recognizing the radio. I had to follow the steps listed in the original 2.3.6 ROM thread to even get this working on VZW.
[Motorola Droid 3] redsox985:
Sorry about no updates here. I have been swamped, but am looking to get another build up soon. Maybe tonight.
[Motorola Droid 3] nemiroG1:
OK, I'll keep working it!
[Motorola Droid 3] redsox985:
My intentions for tonight is to drop the 5.7 apps, stick with Bell's, just change the basics for full VZW functionality (on my end, at least, maybe a GSM build) and then get 1% battery and power menu options working.
[Motorola Droid 3] redsox985:
Working now. This is going very fast. I hope this new method works. This could be <1 hour to go from Bell 2.3.6 to running VZW ROM with 1% and power menu...hope springs eternal here.

EDIT: Ok! Got the bloated version built. Time to make a Nand and flash. :D Let's hope for 1% and reboot menu options. I hit my 1 hour guess-timate too. 11:03-11:49

Booting...hopefully not forever....****.

2nd EDIT:

Ok, so it's awesome at bootlooping. I'm going to upload it here if anyone wants to play with it though. What I did, as an effort to hopefully get 1% battery and reboot menu options working quickly, was I used the files from Maverick and patched them into this build. Here's a condensed run-down of what I did exactly. Maybe Buckmarble or another dev person could chime in here...

I realize that trying to patch in the Maverick files may be what caused the issues, but I was feeling kind of lazy and wanted to toss something together quickly and easily, hoping it would work. :p Oh well!

Here's the link if you want to play with it.

BOOTLOOPS! For testing/experimenting only.

Pull Mav android.policy.jar, rename to .apk, baksmali, repeat for stock android.poilcy,jar.

Grab Mav's Globalactions.smali and replace the stock one

Add GlobalActions$ 10, 11, & 12

Decompile both Mav's and the stock framework_res.apk with APK Manager

Pull public.xml and strings.xml from Mav and replace the stock ones.

Added 3 reboot menu images to Drawable-hdpi

Add screenshot to /bin and CMScreenshot.apk to /app

Pull Mav's stat_sys_battery.xml and replace the stock one in both drawable and drawable-hdpi

Grab Mav's services.jar, rename to .apk, and baksmali.

Repeat for stock services.jar

Pull out Mav's BatteryService.smali and replace it in the stock services.jar.

Smali services.jar and android.policy.jar.

Compile framework_res.apk and sign it.

Dropped all 3 into the 2.3.6 .zip file

Added my tweaked VZW eri.xml (tweaked to remove Verizon Wireless from the status bar)

Add in that massive apns-conf file as well as the 5.7.905 deodexed messaging apps for MMS

Patch up missing /framework files.

Add my previous build's build.prop.

Added Google Car Dock and the 2.3.4 keyboard files to get the assignments/mapping correct.

Flash in SafeStrap after a data/cache/dalvik wipe, only to bootloop.
[Epic 4G General] saramon:
http://www.youtube.com/watch?v=ZQozs5tXxwY

Damn that looks sexy...

Edit: video works now
[Epic 4G General] blong82:
that is slick....but after a couple times i would probably get over it...still super nice tho
[Epic 4G General] ÜBER™:
That is pretty awesome :D
[Epic 4G General] muyoso:
Not only HDMI, but a dual core. Pretty sure that requires a dual core.
[Epic 4G General] ipmsci:
Yeah there is a bit more info on the Ubuntu website.

With cm9 I thought I could go a while without upgrading my phone. Then I read about this...
[Epic 4G General] saramon:
I know right?

Sprint needs a goddamn new phone with a keyboard for godsakes...
[Epic 4G General] pvtjoker42:
don't i know it!

if i could have a full fledged ubuntu running on my phone, i'd get rid of my laptop and probably even my tablet!
[Epic 4G General] saramon:
Probably one of those Atrix docks would be sweet with that...
[Epic 4G General] gastricpenguin:
Very impressed. Whatever happened to video out on the epic? Was that eventually hacked?
[Epic 4G General] dohturdima:
It was abandoned in its infancy :(
[Epic 4G General] saramon:
Video out wouldn't be enough, needs a video dock, or HDMI... and a dual core

Would be nice for devs, compile the kernel directly on the phone, reboot, clockwork done
[Epic 4G General] knightsriot:
I'm trying to watch this! But it appears like they removed it..

Boo.