yashsingh1/xdaforums huggingface dataset:
[Defy General] Guitwo2:
That was a good move actually. They got the XT682 to work with ICS XT687 ROM ?

This seems odd that you can flash one way but not the other. They can't reflash XT682 ROM, but can they reflash XT687 ROM ? Maybe they should try wipe clean the phone before flashing... It happens that it gets stuck. Happened to me when flashing ROM on defy mini. I retried 1 or 2 times and it works.

2 or 3. Formatting will erase partitions' signatures but RSD Lite do not care about that. It signs partitions once they are flashed so that bootloader agree to boot on these.

One can try. Maybe this can do the trick. But I guess this would change nothing.
[Defy General] MauroSZ:
Works partially. No IMEI, No data network and maybe no wifi. I don't know if there is force close frequently and about the dial/SMS compatibility from dual SIM to single SIM. This device has a restrict market unlikely defy mini. No developers interested.

I recommended all wipes they can and after trying reflash, but I didn't say trying twice or three times. Thanks. I also said, if not work format all partitions using CWM except boot partition.

Thanks. This is a good information! :) As for boot partition, I know if format it and just reboot the phone will brick. In this case, you can't boot recovery anymore. I wonder it is possible initializing in FLASH MODE. In others words, hard brick or soft brick ? :confused:

Yes, I think so. One stucks just with it.
[Defy General] Guitwo2:
Yeah well erase boot is not very clever.

here for more info

Soft brick I guess. This has nothing to do with the bootloader.
[Defy General] MauroSZ:
One of them opened a thread

[MENTION=4745666]Guitwo2[/MENTION], One of them decided to open a thread, look if you want

I haven't known about error 0201

http://xdaforums.com/showthread.php?t=2370053
[Defy General] Guitwo2:
I saw that. There is not much I can do.

I suggest to ask motorola for more info about error 0201.
[Defy General] MauroSZ:
About CWM 6.0.2.9, why does it fail backuping defy mini sd—ext ?

Others partitions are backaped Ok.

CWM 6.0.2.7 by enox happens the same when i backup xt687.
[Defy General] Guitwo2:
I guess when creating the recovery image, you should add a custom recovery.fstab like this:

# mount point	fstype	device	[device2]

/boot	mtd	boot
/cache	yaffs2	cache
/data	yaffs2	userdata
/flex	yaffs2	flex
/misc	mtd	misc
/recovery	mtd	recovery
/sdcard	vfat	/dev/block/mmcblk0p1	/dev/block/mmcblk0
/system	yaffs2	system
/splash	mtd	splash
[B]/sd-ext	ext4	/dev/block/mmcblk0p2[/B]
[Defy General] MauroSZ:
I tested with CWM 6.0.2.7 by enox using my XT687. No Defy Mini available at that moment.

# mount point fstype device [device2]

/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
/misc mtd misc
/misc2 mtd misc2
/splash mtd splash
/ftm mtd ftm
/hidden yaffs2 hidden
/hidden/data yaffs2 cda
/sd-ext ext4 /dev/block/mmcblk0p2

Didn't work. Does It work for you ? I modified recovery.fstab on PC using notepad++ showing all characters and after pushed it back to its place and fixed permission 644. Before testing, I saw it again using cat command in its place. It was like I modified. Then I did a backup and "No sd-ext found" again. It seems is too late to modify this file after CWM is running, maybe it isn't read but at CWM initialization only.

then I tried again using this simultaneously :

mount -t ext4 -o rw /dev/block/mmcblk0p2 /sd-ext

Then I did a backup and "No sd-ext found" again, but this code works to access sd-ext.
[Defy General] Guitwo2:
When building the CWM recovery you can add a custom recovery.fstab file (http://builder.clockworkmod.com/)
[Defy General] MauroSZ:
I got it built

Thank You ! I've just backuped my XT687 including sd-ext. My CWM 6.0.3.5 Touch recovery was built.

Before this I tested mounting sd-ext via new recovery built menu and I inspected EXT4 second partition via ADB SHELL using ls -l command.

But I got worried cause a warning on screen just in beginning: NO CONTEXTS_FILES. What is this ? :confused:

The old version, 6.0.2.7 doesn't warn anything.
[Defy General] Guitwo2:
Can I have the CWM log ? It'll help me understand. Full path is : /cache/recovery/log
[Defy General] Guitwo2:
Well, this could be ignore I guess :

from https://github.com/M66B/cm-xtended/issues/140

I guess yes, but I cannot tell for sure. If the block does not exist, it may raise errors.

from http://forums.androidcentral.com/lg-optimus-s-rooting-roms-hacks/124019-not-writing-bad-block-0x004c0000-what-am-i-doing-wrong.html

But no sd-ext support for this one

Sure but nothing to be afraid of.

Here the sd-ext partition is specified in the recovery.fstab file. So it is working.

You should eventually try with this recovery.fstab (attached)
[Defy General] MauroSZ:
The result

[MENTION=4745666]Guitwo2[/MENTION], the result about custom fstab you attached:

I've seem using notpad++ you replaced spaces with double tab as delimiter.

I built a new recovery 6.0.3.5 using the custom fstab you attached and the result was the same: warning, 3 bad blocks and proper functioning :) to backup the device including EXT4 SD second partition. CWM builder can "understand" both fstab: "mine" and yours the same way. Thank you any way. I think it will suit.

Anothers questions:

When I boot my XT687 in CWM, I realize a little freak on screen before to appear the initial CWM menu. Do you think this is related to bad blocks ? :confused: I haven't noticed this on Defy Mini.

Is very difficult building XT687 (or any device) recovery.img ? To upload proper Motorola SBF works ? Maybe no bad blocks anymore ... sorry for noobie question !
[Defy General] Guitwo2:
Very easy to build a recovery.img

Extract the stock recovery.img (http://www.android-dls.com/wiki/?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images) and use the on line cwm recovery builder.
[Defy General] MauroSZ:
Hi,

To find out recovery mtd

cat /proc/mtd
dev: size erasesize name
mtd0: 00700000 00020000 "boot"
mtd1: 00300000 00020000 "misc"
mtd2: 00300000 00020000 "misc2"
mtd3: 00200000 00020000 "splash"
mtd4: 00700000 00020000 "recovery"
mtd5: 00d00000 00020000 "ftm"
mtd6: 00d00000 00020000 "hidden"
mtd7: 01500000 00020000 "cda"
mtd8: 00060000 00020000 "dbgmsk"
mtd9: 19500000 00020000 "system"
mtd10: 06e00000 00020000 "cache"
mtd11: 183e0000 00020000 "userdata"
root@android:/ #

mtd4 found !

Then I used this

# cat /dev/mtd/mtd4 > /sdcard/mtd4.img

I opened recovery builder internet page an uploaded mtd4.img twice (Recovery Image File (stock or other) )

1- Using Touch Recovery checked

2- Using Touch Recovery unchecked

I did not use anything on graphics.c (optional) nor postrecoveryboot.sh (optional)

It built two recovery.img and both have not worked well

- I downloaded android_device_motorola_XT687.zip created by Recovery Builder

- I extracted from this ZIP recovery.fstab that was identical the extracted using motoluxe XT615 recovery with spaces as delimiters in last rows. - I Attached it before an you modified replacing space with double tab and attached back, remember ?

- The recovery with touch functionality works a little, but It is very aloof

- The recovery no-touch performs with very very small letters

- Both performs with weird vertical screen split when I focus some odd number option

- The driver "Motorola Composit ADB Interface" doesn't load, so it is impossible to run ADB SHELL
[Defy General] MauroSZ:
- This driver loads and all work well in any other situation as 6029 recovery or both phones USB debug mode: XT321 and XT687.
[Defy General] rootdefyxt320:
I have extracted XT682 stock recovery.img from the XT682 Gingerbread SBF. Now download it and go to builder.clockworkmod.com

to build ATRIX TV XT682 CWM. I will extract XT687 ICS recovery.img from ICS SBF when I have time.

[MENTION=5013979]MauroSZ[/MENTION], I have also extracted recovery.img from the XT687 VERSION G 2009 SBF

PS: Can you my permanent CWM I made, make sure you press Vol- until you see Android Bootmenu after restarting the device.

Link: http://xdaforums.com/showpost.php?p=44445911&postcount=393
[Defy General] MauroSZ:
There is no GB for XT687, only ICS. Two firms only: 2_27D_2009 (has fastboot) and 2_27G_2009 (has not). Mine is 2_27G_2009 with fastboot of the other (older) because i aplied AR method.

I will thank you if u extract but i wonder where did go wrong when i tried.

If motoluxe xt615 recovery works reasonably maybe xt682 recovery works very well on xt687.

___ update ___

[MENTION=4880538]rootdefyxt320[/MENTION]

I built a CWM recovery.img from mtd4.img that i extract from my xt687 and did not work well as i already explained in 14-aug.

Well. I've done the same using xt687 stock recovery img that you extracted and the result has been the same.

Result details: you can read what i wrote in 14-aug just after i tried using recovery built from mdt4.img
[Defy General] rootdefyxt320:
It looks like it's a glitch from the clockworkmod source in github. Have you tried the permanent CWM yet?

[MENTION=5013979]MauroSZ[/MENTION] Go to cmd and type:

adb shell

then

su

then

mount

This will tell you where the mount locations are located now copy and paste the line from cmd with the word sd-ext and edit recovery.fstab using Notepad++.
[Defy General] rootdefyxt320:
[MENTION=5013979]MauroSZ[/MENTION] It looks like that loggerlauncher doesn't exist in /system/bin. Motorola must of patched the exploit. I think you should flash Version_D_2009 kernel on your phone. To get the kernel on your phone just extract bootsec.mbn out of CG2.SMG and then flash it via fastboot by using the command:

fastboot flash boot bootsec.mbn

Then try reinstalling CWM and then tell me the results.
[Defy General] rootdefyxt320:
This can be easily fixed by this command in cmd:

adb shell su -c 'busybox ln -S /system/bootmenu/binary/bootmenu /system/bin/loggerlauncher_Qualcomm/'
[Galaxy Note II Q&A, Help & Troubleshooting] Framedtrash:
Ive recently installed a qi charger in my phone and im wondeing if there is a app out there that displays the battery status on the lock screen in a large format

I no the phone already does this but its very small

I want a large readout so I can keep a eye on the charge withour having to pick up the phone

Cheers
[Galaxy Note II Q&A, Help & Troubleshooting] Droiderr:
Dunno if this helps you.. But you try go locker (will work with go launcher). They have quite a few themes to play with.
[AT&T, Rogers HTC One X, Telstra One XL] DESERT.TECH:
I must say that hoxl life has been great , nothing more to ask from such a great device. As things progress; change is inevitably coming with days to come. Just a simple message to our great community ..thanks for everything and hard work. Post your experiences and memories of this great adventure..... My bigest joy was day s off became possible....
[AT&T, Rogers HTC One X, Telstra One XL] Desertman123:
What ROM are you on?

My best experience with it has to be the fact I went from a broken iPhone 3GS to this, then I rooted it and flashed CM10 and I experienced a phone like I wanted too. Not held down by the shackles of Apple anymore.
[AT&T, Rogers HTC One X, Telstra One XL] DESERT.TECH:
I have used about every Rom avail on xda and another site. By far for me viperxl 3.2.by turge and kernel elementalx by flar2 is best sense based Rom and I am torn between nonsense roms. Jellybam was cool to play around. Great thing about roms is there is no 1 best Rom for every1, with so many its a personal choice. I know quite a few who think best Rom is a new one so it can be played with . Rom flashing addiction is growing at unstoppable pace....watchout ....
[AT&T, Rogers HTC One X, Telstra One XL] RollTribe:
+1 I love the choices in Sense ROMs. Tweaks? Viper. AOSPish? RebelROM. Simple, smooth? CleanRom. Audio? HatkaXL. The list goes on and on. Love this phone's dev community!
[AT&T, Rogers HTC One X, Telstra One XL] DESERT.TECH:
1600 hrs
[AT&T, Rogers HTC One X, Telstra One XL] panda_mode:
I was going to get the sgs3 coming from the original sgs, but the One X was $50 so I took the offer. If I was forced to go back to a S-AMOLED screen, I'll definitely cry. And I'll cry even more if GPS won't lock. This is an excellent phone :thumbup:
[AT&T, Rogers HTC One X, Telstra One XL] jhonsok:
I've been really happy with mine as well. To be honest this is the longest I have ever owned a modern smartphone. My previous phones would last 6-8 months before I got bored.

As much as I want the One... I honestly wouldn't mind skipping a generation and hanging onto this until it dies.

With s off and development getting even better the one xl is pretty fun.

With my setup the battery life is very much improved! JB Sense roms rock.

I am thinking of changing the housing to the one x+ housing since mine is getting beat up. It's going to feel like a brand new phone :)

Sent from beautiful Evita- Viperxl 3.2.6 | ElementalX 5.4
[AT&T, Rogers HTC One X, Telstra One XL] The_Zodiac:
Lol not quite sure what your inferring here

---------- Post added at 04:56 PM ---------- Previous post was at 04:54 PM ----------

I've been extremely happy with build quality. My last phone was a Samsung captivate & infuse and it didn't hold up very well at all. I miss the no locked bootloader nonsense that Samsung has.

Build quality has been great, screen and camera are awesome.

I've dropped the phone at least 20-30 times with a tpu case and have had no damage.
[AT&T, Rogers HTC One X, Telstra One XL] panda_mode:
"I miss the no locked bootloader nonsense that Samsung has."

Yeah me too. I remember flashing the gingerbread I9000 bootloaders just so I can go to download mode and recovery easier on the captivate lol
[AT&T, Rogers HTC One X, Telstra One XL] Herc08:
funny you mention that, my wife has the captivate...and flashing is much fun on that..i mean i like my HOX and all..but hboot can be a pain...but odin is just so simple, yet so advanced
[AT&T, Rogers HTC One X, Telstra One XL] panda_mode:
Yeah the all mighty Odin. Thanks to that program and kernels with injected cwm, flashing Roms was a blast. I probably will NEVER see an UNBRICKABLE MOD in future Samsung devices. IMO its the best phone in terms of hacking.

GPS was horrible on that phone, though. I couldn't get a lock that would stick for 6 seconds lol, whereas my One X didn't break a sweat. And I'm glad I took a chance with HTC. I was getting tired of the blue-ish white on s-amoled screen
[AT&T, Rogers HTC One X, Telstra One XL] The_Zodiac:
gps was horrid on my captive!!!

lol no matter what i did.

also a huge odin fan!!

tons of one clicks, and non one clicks are fun

Although I wore out more then one back door from battery pulls on my captivate LOL
[AT&T, Rogers HTC One X, Telstra One XL] Herc08:
Lol yeah. My wife gps sucked too...it got so bad i had to use my iPhone 3gs at times lol
[AT&T, Rogers HTC One X, Telstra One XL] Melamunna:
For a while I kept coming on to xda and checked out the cm10 thread but was so concerned about bricking and didn't have money to buy an unsubsidized phone, but when I finally decided to root, I got the vanilla-ish experience I really wanted and it has only gotten better with cm10.1 and roms like the one I'm on now, xylon.
[Android Q&A, Help & Troubleshooting] nitishv:
I hav finally rooted my android.,,,so i wanted to use chainfire 3d. ,I installed it but when i open chainfire 3d and attempt to install CF3D drivers i get this warning...(the image is attatched) ,another question is,Do i need to install cwm recovery and custom rom after rooting.,is it necessary? pls help guys... :(
[Android Q&A, Help & Troubleshooting] amith007:
You better install CWM and take a NANDROID backup before attempting this. So in case any thing goes wrong. you can easily come back. All the best!!
[Android Q&A, Help & Troubleshooting] jacksparao:
I have THL W3 Gapps + CMW.

Any one please guide me how to install Gapps + CMW, I'm looking for 4.1 update also.. any one pls guide me..
[Android Q&A, Help & Troubleshooting] Nokia1234:
Jelly Bean working on W3?
[Android Q&A, Help & Troubleshooting] luminelx64:
jellybean

I'm also longing for jellybean rom for my cj thl
[Galaxy S III General] TechMasta:
Hi guys! This is a noob-proof guide on how to flash stock samsung firmware on your i9300. Whether you have bricked it or just want the stock firmware back. Here's how to do it (detailed explaination)

WARNING! : This is only for the GT i9300 (international version) , Check your device before proceeding. Also you might lose all your data. So backup! i am not responsible if you brick your phone(although very unlikely) by not following the guide properly

Also you will lose your custom recovery, Custom ROM and will not longer have root

Ok lets begin!

1. Make sure you have the samsung drivers installed on your pc (http://bit.ly/SDaIIE)

2. Your device should have at least 80% battery left

3. Enable USB Debugging by going to Settings>Developer Options>Tick the Usb debugging tick box!

Files needed :

1. Android 4.1.2 I9300XXEMA1 for Galaxy S3 I9300 - http://bit.ly/10vkxdj

2. Odin 3.07 - http://bit.ly/16aRzF4

Extract The firmware Zip file until you get a file with a .tar extension and some other files. Do not extract furthur

Extract odin zip file till you get Odin3 v3.07.exe

Now here comes the actual flashing part

1. Power off your smartphone. Wait 5-6 seconds for vibration to confirm complete switch off.

2. Now, get into Download Mode by pressing and holding Volume Down, Home and Power button simultaneously until Samsung Galaxy logo appears in phone screen. Wait few seconds and your phone will be in download mode.

3.Open odin as administrator and connect your s3 to your computer with usb cable

4. You will get a message "Added" in the message box in odin and You should also see COM port with a number in Yellow if you successfully added your device.

if you don't get this , try another usb port.. if it still doesn't come , reinstall drivers.

5. Select these files from I9300XXEMA1 folder in Odin at respective buttons:

Click the PDA Button, and select the .tar.md5 file here with *code* appearing in its name

Click the Phone Button, and select file with *modem* in its name (leave if there is no such file)

Click the CSC Button, and select file with *csc* in its name (leave if there is no such file)

Click the PIT Button, and select the .pit file. Use only if you got it while extracting , otherwise ignore it.

6. make sure Auto Reboot and F. Reset Time checkboxes are selected. Also, make sure that Re-Partition checkbox is selected, only if you are using a .pit file

7. Double check everything above and hit start!

8. once flashing is complete the phone will reboot automatically and soon you will see a PASS message with green background in the left-most box at the very top of the Odin. You can then unplug the USB cable to disconnect your device from computer.

congratz , you have just restored your i9300!

If this has helped you make sure to hit the thanks button! :cowboy:
[Galaxy S III General] Glebun:
what have you developed?
[Galaxy S III General] qtwrk:
We already know Odin, and this doesn't UNBRICK anything
[Galaxy S III General] Ausboy 2011:
This is so worthy of development thread. ...:banghead:
[Galaxy S III General] k6?:
Helpful post to some,,,,,however the unbrick part is misleading as all this does is flash a stock ROM.
[Galaxy S III General] Primokorn:
Only soft brick... like any other Samsung device.
[Galaxy S III General] JJEgan:
Reported not development plus we have all this information already posted .

OP is splattering this post all over the forum .

jje
[MDA, XDA, 1010 Software Upgrading] decodertje:
last week i upgrade my xda to the 2003 versie

now i wanne go back

I've I tryed to "update" to the new XDA-Def. 1.2 then Flashprog stops after a few seconds and the Active Sync 3.7 stops to run...

A reset can wake up my xda, but no new developers rom .

please can somebody explane help how to rol back to developers v1.2

help :cry: :cry: :cry:

thx decodertje
[MDA, XDA, 1010 Software Upgrading] sheran_g:
Flash it by using an SD Card. Use XDArit and write the SERom 1.2 onto your card and flash it with the Bootloader.

I am writing up some documents regarding this. I will post them later today.
[MDA, XDA, 1010 Software Upgrading] decodertje:
i just do wat u sad

and now my xda = dead :( :( :(

when i put it in the cradle it says unknown usb device

only the light from batterie is orange for the rest nothing

please help xda developers
[MDA, XDA, 1010 Software Upgrading] itsme:
what way did you use to upgrade to 2003?
[MDA, XDA, 1010 Software Upgrading] decodertje:
i put the file 2003 from jef summers on a sd card

hard reset en instalt it

its works fine, but i like the xda developers rom 1.1 very much

then i want to instal v1.2 and i put the exe file from jef summers on the sd card .then i hard reset en instalt the rom,wait then it says compleet cold reset now ,thats wat i did and now its dead
[MDA, XDA, 1010 Software Upgrading] itsme:
and you only put and .nb1 on the card?

and left the 'bootloader' checkbox unchecked?
[MDA, XDA, 1010 Software Upgrading] decodertje:
bootloader i also put a x

i think that was wrong right?

what to do ??
[MDA, XDA, 1010 Software Upgrading] Supergrobie:
Hi!

I did the same but not the bootloader... 8)

But I've also the Problem to go back and

the 1.1 / 1.2 ist only an EXE and i could not burn

it on an SD card, right?

Stefan
[MDA, XDA, 1010 Software Upgrading] itsme:
yes. it is somewhat of a wonder that your 2003 actually works.

to fix a corrupt bootloader when you still have a working 2003. you would have to write a program to flash from ce. ( and figure out how to do flashing )

if your xda does not boot at all, take a look at jtag. maybe you can find someone who also does pda memory upgrades to do this for you.
[MDA, XDA, 1010 Software Upgrading] decodertje:
i think u not understand me because my englisch

last week i upgrade my xda to the 2003 versie

now i wanne go back

I've I tryed to "update" to the new XDA-Def. 1.2 then Flashprog stops after a few seconds and the Active Sync 3.7 stops to run...

A reset can wake up my xda, but no new developers rom .

please can somebody explane help how to rol back to developers v1.2

help

that was the first problem to go back to v2.1

then i did

Flash it by using an SD Card. Use XDArit and write the SERom 1.2 onto sd card and flasht it with the Bootloader

i wait till it was finish.

the xda say compleet , en cold reset u xda . thats what i did.

but the xda dont work anymore.

when i put it in the cradle only the battery led burn.

windows xp say unknown device and dont regonice my xda.

when i put the powerbutton and softreset i dont see wallaby bootloader anymore??

what to do now

help me please xda developers
[MDA, XDA, 1010 Software Upgrading] itsme:
I think I do understand you, and that

is your current problem, and

is your only option left.
[MDA, XDA, 1010 Software Upgrading] decodertje:
@XDA developer Itsme

thx for the help

i am lucky

there is a compagny in maarssen in the netherlands, its only 50km from almere, they upgrade my xda to 64 mb :lol:

do u now how the xda runs whit 128mb????

next week i go there and i let u know how it end

decodertje from the netherlands bye
[MDA, XDA, 1010 Software Upgrading] Aurora13:
Decodertje I'm from the Netherlands also and I changed back from 2003 to SE 1.2. So if you give me a private message I think I can solve your problem. And you can speak in Dutch then. :)

I'll explain in english what I did:

- Extract 'Jeff's SE 1.2 EXE' to an folder. (don't run it!)

- Then burn the NK.nbf found in the folder to an SD card with a SD reader (or MMC card/reader like I did) and put it in the device.

- Hold the power button and press the RESET switch.

- It will go into the Wallaby bootloader and will see the ROM on the SD card. Press the action button (middle position of the 4-way button).

It will load the new ROM and when it is finished (about 5 min.) press the RESET switch. And it will boot with the BEST ROM ever! :)

Hope this helps.
[MDA, XDA, 1010 Software Upgrading] Aurora13:
IMPORTANT

I forget something:

Burn the nk.nbf to an SD card with XDArit, but ONLY the Windows CE, do NOT select the bootloader!!!!
[MDA, XDA, 1010 Software Upgrading] decodertje:
Aurora13

u got pm