Database Users

[Samsung Moment] Root Instructions

EDIT: This information is out dated now but visit the link below for updated info.
taken from here http://www.samsungmomentforum.com/rooting/root-access-(finally-achieved!)/
1) Partition your SD Card to have first partition as fat16 and second ext3 [this tutorial assumes you have this setup exactly as stated]
2) Boot in Test Mode with Call+Center+Power
3) copy root into your tools directory of the sdk
4) adb push root /system
5) adb shell chmod 0755 /system/root
6) adb shell /system/root
7) unplug usb, remove battery, reboot into test mode when instructed
8) adb shell
9) /system/bin/btld_testmode
10) /system/root

Excellent. It work!. Just do exatly the steps above. Thanks for putting all this info together.
FYI... Samsung post the source code of the samsung moment.

Is this temp or persistent root? For temp root I don't think partitioning the sd card is necessary or at least I didn't partition it when I temp rooted my Moment.

Was a long time WinMo user, I was stuck with a Moto Q9c on sprint for way to long. I'm still stuck with sprint, but got the Moment in hopes of having a badass Android to start with.
Night and Day compared to my Q, the root is key though, custom rom's were so easy on the Q.
soooo im a newb to android, same question as johnbarry3434.
does it stick?
I've got two Moment's(thanks sprint for shipping me 2 and charging me for neither) ?maybe one for test purposes?
Anything I can do to help the rooting process, please let me know

Sorry guys but I'm very new to this android. Only had my phone for a week now. Is rooting like flashing a custom ROM for the Touch Pro?

Does this require seperate adb drivers for the Samsung phone?? If so where can I get them and are there any avaliable for Ubuntu???

Hi guys,
I have just gotten myself a Samsung Spica. Can I use this guide as well? Is there a ROM-update tool for the Spica?
I'm really n00b, so any help is appreciated

I need someone with this rooted phone to contact me, I need to get some data from it so I can work on something for it.
Please contact me at [email protected]
Thanks

hey look i am brand new to this whole root thing i just got my moment two days ago i am used to the simple jailbreak iphone stuff but this is a whole new level
i am on windows vista and i do not understand any of this at all please someone email me some simpler instructions or make a video or something just to help me out in some way please and thank you
my email: [email protected]

use the search Service people

Now that moment is rooted?
Will there be any chance of us getting a custom rom of andorid using sense ui?
i dont really see any point in rooting my phone if there is no MAJOR thing you can do with it..

I cannot get my samsung to root
I have the updated cupcake cl14 and when I boot my phone with talk+center+power, I boot into a test mode that lets me test the screen, keyboard, and so on. I did copy the root file (supplied from the instructions ) to the main part of my card on both partitions, and partitioned it just as it stated in the 1st step. I don't understand what the "adb" is and how to use it. Can this only be down with windows because I'm am using Ubuntu. I know adb is advance debugging bridge but after some google searches I still don't know how to use it. I now a little about chmod 0755 because of Ubuntu but any "hand-holding" instructions would be great thankyou to everyone who is willing to help me and others out with this problem.

Is there still no "real" benefit for root access for the Moment? As in no good reason to root the phone? My girlfriend has one and I was hoping that it was at least close behind my Hero by now in terms of root access benefits....TIA

bbv203 said:
Is there still no "real" benefit for root access for the Moment? As in no good reason to root the phone? My girlfriend has one and I was hoping that it was at least close behind my Hero by now in terms of root access benefits....TIA
Click to expand...
Click to collapse
try this
http://forum.samdroid.net/threads/13-How-to-get-Root-on-Samsung-i5700-EN-02-10-v-LK10

just got my phone and can't increase the size of the fonts was told rooting is the only way even with using spare parts.
first of what program can I use to partition the sd card I am running windows XP. and everything I have downloaded today would only see the internal drive.

For those of you still looking for how to root your Samsung Moment (you don't have to use your SDCard either) there are two HOW TOs posted at PPCGeeks under the NON-WM DEVICES>ANDRIOD>SAMSUNG MOMENT
One explains how to root phone with CJ05
The other explains how to root phones that have CL14 out-the-box or officially updated to CL14
I would post a link except I'm not permitted to post an outside link... just go to PPCGeeks(dot)com and click on their forum

So what Now!!!!
Okay I see you have this placed here.. I like... I have a Nexus and 2 Droids, wife and mine.. Nexus ALL mine.. HAHAHA..
My sister, wifes sister, she has the Moment.. I have always wanted to root this just cause of the 800mhz processor... This was the first device to almost meet up with the Nexus before it was even thought up..
Is there Roms, Themes, Kernels, etc.. I see nothing, but a root, useless, without an accommodation, thanks anyway, always good to have the key to the door first..
Somebody, PM me if not on, or reply here, I'll come back around...

cool that i made the front page but the info is out dated now.

yes this info is way outdated. just flash the kernel with speedyrabbit's or joeykrim's kernel and you'll have persistent root, plus a much faster phone.

also, speedyrabbit's kernel has wifi tether and flash_image support. you can download from www(dot)sdx-developers(dot)com.

eMMC fix?

i think i might have found a possible fix for the eMMC corruption.
credits go to 3p4145 for discovering this:
Well I am in no way an expert or have enough knowledge to find an answer.. but I have some basic idea... so here it goes...
If I understand correctly, the problem is that the eMMC driver chip gets corrupt...
This chip controls the MMC0 which is (part of the chip) the actual flash upon which the phone relies to store its stuff...
No Since the issue is seen with rooted phones more often, I would imagine something that was written to the mmc0 is causing issues.. Using root explorer, i found this file on my /proc/emmc
This file seems to have the some sort of memory locations for various directories on the mmc... a corruption of this file could be a bad thing... I am not saying that this is the cause.. but if anyone with a bricked phone could get into their FS (i have no clue how) and check this file.. we could look into coming up with a generic file with memory address that are common....
Mine seems to have locations address for:
misc
recovery
boot
system
cache
userdata
devlog
pdata
Click to expand...
Click to collapse
as he stated, the eMMC files that might be corrupted in the failed eMMC chips are located in /proc/emmc.
i have been able to get to this location using adb
Code:
cat /proc/emmc
so, would it be possible to copy the correct files from a good chip to this location, and fix the failed eMMC problem?
the failed chip's filesystem got corrupted i think (correct me if i'm wrong)
i have the emmc file, pm me if you want it.

seems like a good theory. let's say you do copy the files from a good chip over to the bad emmc...how could you simulate or know when/how the M4G2DE 2.10GiB units would fail?

suchavibrantthang said:
seems like a good theory. let's say you do copy the files from a good chip over to the bad emmc...how could you simulate or know when/how the M4G2DE 2.10GiB units would fail?
Click to expand...
Click to collapse
it's impossible to tell when the chip will fail. but when they do.. could someone try this?

So it's a software failure and not an actual hardware failure? I'm not sure how likely this is to solve the issue, but any movement towards a solution is a good thing.

TeeJay3800 said:
So it's a software failure and not an actual hardware failure? I'm not sure how likely this is to solve the issue, but any movement towards a solution is a good thing.
Click to expand...
Click to collapse
it's more of a firmware issue. inside a computer, there are many different chips. some chips are consisted of firmwares, these are the ones that you can write to and change (like the eMMC chip). other chips, are completely hardware, you can't write to them, you can't change them.
so since the eMMC chip is consisted of "software", then maybe we can replace the corrupted files with good ones.
but i need some testers, since my dead eMMC chip is somewhere in tmobile's dead phones junkyard.

If it's the chip itself that fails - then you can't fix it by writing something to it, since it won't write whatever you're trying to write to it. Trying that would be equal to trying to fix a failed hard disk by using it.
"Firmware" is just another term for software. No chip consists of firmware, firmware is written on memory (permanent or rewritable), which is read by some hardware (usually some type of CPU) that executes this firmware. eMMC is just a rewritable memory chip, and if the controller of the chip fails, or big chunks of the memory in this chip fail - it's not usable anymore.
And of course, there is no such thing as "driver chip". Driver is a program, software, that runs on CPU and is stored in - again - memory. eMMC controller, on the other hand, is hardware, a part of the chip itself. The failure is on a whole another level.

Jack_R1 said:
If it's the chip itself that fails - then you can't fix it by writing something to it, since it won't write whatever you're trying to write to it. Trying that would be equal to trying to fix a failed hard disk by using it.
"Firmware" is just another term for software. No chip consists of firmware, firmware is written on memory (permanent or rewritable), which is read by some hardware (usually some type of CPU) that executes this firmware. eMMC is just a rewritable memory chip, and if the controller of the chip fails, or big chunks of the memory in this chip fail - it's not usable anymore.
And of course, there is no such thing as "driver chip". Driver is a program, software, that runs on CPU and is stored in - again - memory. eMMC controller, on the other hand, is hardware, a part of the chip itself. The failure is on a whole another level.
Click to expand...
Click to collapse
You summed up my thoughts on the issue perfectly, especially the first paragraph. That's why I didn't understand why the OP's theory would work. I'm not knocking his efforts at all...anyone trying to fix the eMMC issue is doing a good thing, it just didn't make sense to me.

oh...
sorry.. i thought the chip was just corrupted when it said "failed"...
well then nevermind, this wouldn't work.

Thanks for talking abt this guys..
I understand what you guys are saying.. but quite often the HW itself is not bad but the address locations are corrupt.. Like I mentioned in my initial post... I am not sure what causes the fault.. but Once caused, IF there is a way to just re-write the addresses for these locations so that the driver chip/Controller chip can try to use the addresses provided is what I am trying to see..
This statement is right on the amrk: "eMMC is just a rewritable memory chip, and if the controller of the chip fails, or big chunks of the memory in this chip fail - it's not usable anymore."
now considering this, IF the controller is physical fault (as in fabrication fault, overheated transistors etc).. the nothing more can be done.. BUT if the fault is just in the addressing fail.. this providing the addresses should work wouldn't you think?
If someone has a brick on their desk they can try this.. Nothing really to loose right?
I would never suggest replacing the emmc file of a working chip.. now thats just crazy talk.. well if you have $500 to spare.. sure.. but I was thinking of fixing a broken one...
One more last thing: The only problem with this approach on a dead phone is getting access to the FS AFTER the phone is dead.. any ideas?

3p4145 said:
Thanks for talking abt this guys..
I understand what you guys are saying.. but quite often the HW itself is not bad but the address locations are corrupt.. Like I mentioned in my initial post... I am not sure what causes the fault.. but Once caused, IF there is a way to just re-write the addresses for these locations so that the driver chip/Controller chip can try to use the addresses provided is what I am trying to see..
This statement is right on the amrk: "eMMC is just a rewritable memory chip, and if the controller of the chip fails, or big chunks of the memory in this chip fail - it's not usable anymore."
now considering this, IF the controller is physical fault (as in fabrication fault, overheated transistors etc).. the nothing more can be done.. BUT if the fault is just in the addressing fail.. this providing the addresses should work wouldn't you think?
If someone has a brick on their desk they can try this.. Nothing really to loose right?
I would never suggest replacing the emmc file of a working chip.. now thats just crazy talk.. well if you have $500 to spare.. sure.. but I was thinking of fixing a broken one...
One more last thing: The only problem with this approach on a dead phone is getting access to the FS AFTER the phone is dead.. any ideas?
Click to expand...
Click to collapse
using adb you are able to get into the filesystem...

A failed partition update would mean the emmc file was corrupted??
Or failed partition update means it wasn't able to update partitions because the chip failed to re-initialize??
If the theory is correct, the EMMC file not the chip is actually screwed up and it can be fixed, but if the emmc chip is what failed then it is irrecoverable.

tKoHaXoR said:
A failed partition update would mean the emmc file was corrupted??
Or failed partition update means it wasn't able to update partitions because the chip failed to re-initialize??
If the theory is correct, the EMMC file not the chip is actually screwed up and it can be fixed, but if the emmc chip is what failed then it is irrecoverable.
Click to expand...
Click to collapse
i'm pretty sure it the eMMC's filesystem got corrupted, but of course, i could be very wrong.
that's why we need a bricked MT4G with dead eMMC.

Has this been posted in the g2 forums? I know they have had some guys lookin into this as well...
Sent from my HTC Glacier using XDA Premium App

irrelephant said:
Has this been posted in the g2 forums? I know they have had some guys lookin into this as well...
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
should i also post this in the g2 forums?

saranhai said:
should i also post this in the g2 forums?
Click to expand...
Click to collapse
I believe there are a few ppl there with the failed emmc that still have their phones...
Sent from my HTC Glacier using XDA Premium App

irrelephant said:
I believe there are a few ppl there with the failed emmc that still have their phones...
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
yes thank you

irrelephant said:
I believe there are a few ppl there with the failed emmc that still have their phones...
Click to expand...
Click to collapse
Do any other models have this issue, or is it just T-Mobile phones?

TeeJay3800 said:
Do any other models have this issue, or is it just T-Mobile phones?
Click to expand...
Click to collapse
I have heard about 4 or 5 phones have had the bad emmc... Just Google phones with bad emmc and I'm sure there will be a list
Sent from my HTC Glacier using XDA Premium App

question: would the stock rom/pd image have this so called "good" file imbedded in it?
i ask because my current phone has gotten the cache errors while on rooted non-stock roms such as ice glacier and CM7..i was able to recover from them...but never once saw any issues after flashing completely back to stock...ive also not seen this issue arise after flashing from stock into Virtuous Unity and ive been on VU for almost 2 weeks and ive flashed a few radios and restarted my phone at least 2 dozen times to see if i get the cache error and so far nothing
all of which kinda leads me to believe that this very well could be a software or file issue thats being written maybe too many times or written with incorrect information due to flashing multiple roms or radios or something...i know not everyone with the "bad" emmc has had issues but maybe they arent doing something to trigger the bad errors

here's the emmc file located in proc:

[Q] SOLVED- Process to map out bad sectors on a500? Replace MOBO

SOLVED the best way.. See post #5
Hello
I have asked this in other threads, but have not gotten an answer that I can manage to make work yet. I'm also hoping that this thread may help the many others out there with this same problem.
I have an Iconia A500 that has the bad sector problem. I cannot get it to format partitions through any of the EUU's out there,or even the Babsector .bat's . Same thing every time-read/write failure. I have seen mention in a thread or two about guys who have used the "rawdeviceread" and "rawdevicewrite" commands in NvFlash to "map out" any bad sectors on the EMMC chip, and create "dummy" partitions over them so that the tablet will function again, at least until more sectors die anyhow.
Can someone please explain this process, including describing the files needed, exact commands, and the rest of the process to make this happen? I have seen member "Yaworski" describe the basis of it, but again his commands are no-go for me. It would also be great if a partition could be created, but not formatted, completely bypassing any possibility of NvFlash failure.
Thanks in advance By helping me I'm sure you wil also help many others. It seems many a500's are starting to suffer form this same exact issue.

Anyone? I have read thru this post: http://forum.xda-developers.com/showthread.php?t=1691729&page=3 , and seen a couple recommendations to it in other threads, but no dice on making it work .. or even being able to map out the bad sector/s. I know this'lll fix me up at least temporarily...

I need help with this as well. There doesn't seem to be a step by step guide anywhere :\
Sent from my SGH-T769 using xda premium

dynospectrum said:
I need help with this as well. There doesn't seem to be a step by step guide anywhere :\
Sent from my SGH-T769 using xda premium
Click to expand...
Click to collapse
I've been asking around about a possible process of mapping out bad sectors, and not just members in here, but engineers and technicians I know as well. First, the NAND has this sort of embedded firmware that directs it to remap or bypass bad sectors “spontaneously,” if you can call it that. When you're stuck with “write errors” or where the NVflash even fails to create and format a partition, it suggests that this part of that firmware is not working. Why the loose fit, or lack thereof, I don't know.
Second, The FCK guys mention that you can write a dummy file and make the device read back so you can see where the data is missing and circumvent it altogether. But they also state that if Sector 0 – which NVFlash is slated to access – is kaputt, then it would hang, as probably in your case and certainly in mine.
Given that the Boot Configuration Table is 4Kb tiny while the NAND is 16Gb large, I can't imagine the latter being damaged so badly as not to have a continuous space of 4Kb to accommodate such partition. As a matter of fact, I did have someone with special equipment probe my NAND “physically” and the initial report indicated that the first half (50%) of it had less than 3% of its sectors that was bad. NVFlash, however, could neither create nor format, let alone write on it.
So, either one must have the appropriate hardware to do a very low level format to restore the NAND in full or in part, or NVFlash has to be hacked to command writing at a Sector different than 0. Until that happens, I doubt it that a step-by-step guide grounded in current programs would be viable.
I know that neither the custom ROMs nor the custom Bootloaders and Recoveries are remotely the cause, because this occurred way before any of it came onto the scene. But in light of the frequency at which this happens to some of us, it seems ironic to term this device bullet-proof. I'd like to think it's not incurable, but what the FCK do I know? (Sigh) Anyone with the essential hardware know-how to tackle this?

SOLVED..well the "easy" way....
I sourced out a broken A500(strangely the screen is fine though lol), re-soldered the power button on it(PITA), and put it into my A500.
I plan on taking it easy with the flashing on this one. A500s seem to have a growing history of EEMC chip failure from over-flashing. My old board had been flashed MANY times by the previous owner, and a few by me before it died. The "new" tab was only flashed enough to get it to Stock ICS. Now it has the V8 bootloader and Civato's Re-Flexx ROM(Best out there IMHO).
So there you have it.. this seems to be the best way to fix this problem on the A500---Replace the Darn motherboard. I'd imagine mapping/skipping sectors is only a temporary fix that will probably lead to the tablet dying when its needed most.

[WIP] [DEV] Any dev know where BT config is stored within i9505G?

Trying to fix my Bluetooth issue, as chronicled in detail here.
Wanted to ask you devs where Bluetooth configuration or a related error log is stored on the i9505G so I can take a look at it; something is stopping my BT from being able to turn on; it used to work fine pre-root (heck, even post-root for a day or so).
I figured the developers would be the best people to ask since you'd be familiar with the folder structure and config files.

KrossX said:
Trying to fix my Bluetooth issue, as chronicled in detail here.
Wanted to ask you devs where Bluetooth configuration or a related error log is stored on the i9505G so I can take a look at it; something is stopping my BT from being able to turn on; it used to work fine pre-root (heck, even post-root for a day or so).
I figured the developers would be the best people to ask since you'd be familiar with the folder structure and config files.
Click to expand...
Click to collapse
Sent from my GT-I9505G using Tapatalk 2
KrossX this is the second time you have posted questions in the development forum. As I stated before these are for Q&A NOT here. Please refrain from posting your questions here and READ the XDA users guide and forum rules again. There is a reason for this. I am glad your part of the community and your questions and comments are noteworthy you just need to put them in the right place. We read those threads as well! MJ
This is for Development ONLY

Yes PLEASE no name calling we all make mistakes and this thread will be moved soon to the proper place
And to answer your question Kriss you could do a logcat but if your not familiar with that do a search and provide more info on what your trying to do ( configuration?)
Sent from my GT-I9505G using Tapatalk 2

MJHawaii said:
Yes PLEASE no name calling we all make mistakes and this thread will be moved soon to the proper place
And to answer your question Kriss you could do a logcat but if your not familiar with that do a search and provide more info on what your trying to do ( configuration?)
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I thought that since I was aiming this more at the devs it would've been in the Dev forums. Sorry for having you move yet another thread of mine.
Didn't mean to cause a ruckus; never really got a chance to read the post by deaffob above before it was edited by the mod so no offense from whatever name-calling was done, haha.
Thanks MJHawaii; I will search for logcat and see what I can pull up.

Any ideas (referring to attached pic)? I filtered at the Error level in the logs for the term "Bluetooth"
Sent from my GT-I9505G using Tapatalk 4

KrossX said:
Any ideas (referring to attached pic)? I filtered at the Error level in the logs for the term "Bluetooth"
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
The first error there looks like it may be relevant, but you'll need to get a more thorough logcat in order to trouble shoot it more. Please grab one with adb and post it to pastebin or here in a [ code][ /code] box.

xHausx said:
The first error there looks like it may be relevant, but you'll need to get a more thorough logcat in order to trouble shoot it more. Please grab one with adb and post it to pastebin or here in a [ code][ /code] box.
Click to expand...
Click to collapse
Good news and bad news.
Bad news: I am unable to run logcat; I am unable to access my device via USB ever since the root and when I tried doing the logcat steps, yet again it couldn't connect to my device.
Good news: I believe the solution to this issue (being unable to access my device via USB) may also lie in the logs along with the bluetooth issue. The reason why is because of this error message I received while trying to reinstall the USB driver (attached pic); it points to not being able to "start" a device. I think this will all eventually tie-in with some services not running correctly on my phone.
So, is there another way for me to post a log for you kind folks to review on here via my phone directly?
If I can do that via catlog app on my device, let me know what sort of log (which options) I'd need to run and post. Thanks!

Well, did a restore to stock + root. That didn't help. It changed the Baseband, Kernel, and Build versions but did nothing to fix my issues with BT and USB connectivity.
I think I am going to start researching ways to start from scratch. Like a factory reset/wipe back to first-use condition. If anyone can point me towards some reading material on how to do that safely and wisely, it would be much appreciated!

I just ended up doing a factory reset (Menu-->Settings-->Backup & Reset-->Factory Data Reset) and that resolved the issue (while wiping my phone).
Bluetooth issue is resolved; tested it just now and it works just fine again. As is the USB issue; as soon as the phone was connected to the same exact PC as before, it was recognized and showed up as a device that I could open and explore.
My Kernal/Baseband/Build versions are all back to the ones I had when I got the phone from the Google Store, so that's comforting too.
Thanks to all those who attempted to help!

Super beginner, never even used one of these before. Please help...

Ive just recently aquired one of these and I'm trying to factory reset it. I'm afraid to use the erase and deregister cuz I don't want to get locked out if I don't have some certain info or whatever... Is that the best way to make it like you just turned it on for the first time?
Maybe someone can point me to a specific thread that explains how custom recovery boot loaders work on this thing and what not. I'm just not sure where to begin. I'm searching, but I'm seeing stuff like burn cm7 to an sdcard? I could just blindly follow those steps, but I don't wanna brick this thing. Is there a thread that gives a crash course on how things work with this device?
It would be nice to have cm7 on here though. Is it Android to begin with? I've got a rooted modded s4 currently, but this nook looks like it might work a bit differently. Any help would be greatly appreciated.
You've been Tapatold ♧♢dbombROMv3.4♤♡

The erase and deregister is the best way to get back to the way it came in the box. Make sure you are connected to wifi when you do it. It will remove it from the prior owners registration. Then you can register it in your name. (You did not say, but I am assuming you got this second hand).
Go to my NC Tips thread linked in my signature to learn a little more about this device. It does not all have to be read, but some sections will help you a lot.
And stock is Android (Froyo, Android 2.2), but heavily modified by B&N.
Look for eyeballer's thread on how to put CM7 on internal memory replacing stock. See here:
http://forum.xda-developers.com/showthread.php?t=1030227
Sent from my BN NookHD+ using XDA Premium HD app

Thanks a lot man. I'll check this out. And yes I did get this second hand.
Does anyone know a good place to get magazines and books that are compatible with this?
Are torrents updated frequently with new titles and monthly copies of a lot of magazines? I don't even know what file format the books should be in. But I'll read the info you suggested, above me... Thanks again
You've been Tapatold ♧♢dbombROMv3.4♤♡