Related
I had a friend root my phone and I know if I want to flash a new build I rename the file update and drag it to my android folder then restart the phone a certain way and press alt s to load the build.
I love my g1 and the 1.5 build Im using but I cant get any further because Ive scoured the internet and these threads and I just cant figure out what all of this computer jargon means and I dont understand how anybody does know without taking classes in it.
I think I should make a nandroid backup and partition my sd card to run apps but good lord what does this mean (regarding nandroid)???---
"anyone who has root on their G1 and has the engineering/dev spl bootloader [1] (or has a dev phone) + a recovery image with busybox and adbd running as root [2"
and this (regarding sd partition)???---
pre-requisite "You created the FAT32 / EXT2 combo partitions" I mean this is a PRE-REQUISITE! I found a thread regarding the fat/ext deal and didnt understand it either.
I know nobody is here to babysit but is there some website somebody can direct me to to begin understanding what Im reading, I mean I read through the sd partition for dummies thread and I literally understood MAYBE 10% of the words, if thats for "dummies" im clearly the "dumbest"
I have the will I just dont have the way, ive typed the language i dont understand into every search engine I know of and Ive learned nothing. You guys are born geniuses
and what the hell's a "script"
No offense intended, but I don't think you should root your phone or carry out any of the procedures outlined in the developer forum. Following instructions to the letter is important when you are performing unauthorized and unsupported hacks, and most of those instructions assume an intermediate-to-advanced level of computing understanding.
As far as "where you learn it", I assume it varies from person to person. Although in nearly all cases, you learn it slowly by absorption when you are immersed in computing culture. Eventually if you lurk enough and see a word enough times in a particular context, you gain an understanding of what it means without being explicitly told.
You learn as you read through forums and threads and asking questions. If you're lucky, someone will explain it to you.
A script is like a programming language that controls a software application.
Nandroid is a tool or script you can use to backup your phone. It takes a bit of knowledge to restore from the backup though and requires a separate thread
You can read all about SPL's here: http://forum.xda-developers.com/showthread.php?t=455860
Can't help you with busybox/adb/recovery image right now.
FAT32 and EXT2 are just file type partitions. Think of a hard drive as a box. You put a divider cutting the box down the middle to split it into 2 compartments so each compartment can store something different. That's essentially what you do to a SD card when you create a FAT32 and EXT2 partition.
I learned all this by totally screwing things up, then reading, and reading some more. Then using the search function of the forum and of course more reading.
Now I understand a good deal about ADB, terminal, and the many, many other things that come with a rooted phone,,
I don't agree with the post that said if you don't get it don't try it.....
But that is cause I learn by doing...
As mentioned, doing this is a little complicated. The wrong step can temporarily brick your phone and then you'd have to know how to fix it, which in a way also requires a certain level of knowledge. It's best to learn and absorb the information first and to NOT be in a hurry to implement what you learn.
DMaverick50 said:
I had a friend root my phone and I know if I want to flash a new build I rename the file update and drag it to my android folder then restart the phone a certain way and press alt s to load the build.
DMaverick50 said:
This will be invaluable to fixing a botched up hack. Although, many times you'll also have to wipe (alt-w) to clear out your personal settings and personal data.
DMaverick50 said:
I love my g1 and the 1.5 build Im using but I cant get any further because Ive scoured the internet and these threads and I just cant figure out what all of this computer jargon means and I dont understand how anybody does know without taking classes in it.
Click to expand...
Click to collapse
As mentioned, we all just love the stuff, and pick it up as we go. Most of us read extensively and have well set backgrounds on computers. If you want to get your degree in brain surgery, it helps to have basic knowledge of human anatomy, first.
DMaverick50 said:
I think I should make a nandroid backup and partition my sd card to run apps but good lord what does this mean (regarding nandroid)???---
"anyone who has root on their G1 and has the engineering/dev spl bootloader [1] (or has a dev phone) + a recovery image with busybox and adbd running as root [2"
Click to expand...
Click to collapse
Nandroid is a backup program build into the... "recovery mode" for lack of a better description. It's where you do the alt-s at. Alt-b creates a backup of your system. To restore it, you must read the thread sticky that walks you through it.
DMaverick50 said:
and this (regarding sd partition)???---
pre-requisite "You created the FAT32 / EXT2 combo partitions" I mean this is a PRE-REQUISITE! I found a thread regarding the fat/ext deal and didnt understand it either.
Click to expand...
Click to collapse
As mentioned, FAT32 and EXT2 are types of filesystems. Think of it as being told to store a box in a wearhouse. The filesystem, in a sense, would be like the isles, shelves, etc. that help you not just have a giant pile of stuff.
This is asking you to have an SD card that has been partitioned off into two partitions (a giant wall in the middle of the wearhouse) where on one side you have one way of storing things that is easily understandable by the average joe (windows, linux, apple) and one side that is much more complicated but much more efficient to store things that only the wearhouse manager understand (linux.)
DMaverick50 said:
I know nobody is here to babysit but is there some website somebody can direct me to to begin understanding what Im reading, I mean I read through the sd partition for dummies thread and I literally understood MAYBE 10% of the words, if thats for "dummies" im clearly the "dumbest"
Click to expand...
Click to collapse
No. We all started somewhere. Nobody here came here and understood everything over night. Most of us have YEARS of experience in the computer field, if not decades. As far as knowledge here, it takes months of READING to really start to understand things. Once you do, THEN things will make sense and then you're less likely to break your phone.
DMaverick50 said:
I have the will I just dont have the way, ive typed the language i dont understand into every search engine I know of and Ive learned nothing. You guys are born geniuses
and what the hell's a "script"
Click to expand...
Click to collapse
Read, read, read. That's my way.
And like mentioned, a script is just what it is in real life. Something you follow. If I gave you a movie script, you follow what it tells you to do while in the movie. In the computer world, it's the same. You write a script that tells the computer what to do.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I see you joined few days ago. I suggest you start from the begining. i.e. read all stickies. Every questions that you've asked here was asked before by someone else and answered multiple times.
To offer a glimpse of hope here: it's a lot easier for n00bs now as more and more people get comfortable with Android and Android tools and it's not just 2-3 guys who can answer a question. Also, at this point we have apps that will run a script for you, move your apps and caches to SD, overclock you CPU, etc etc etc.
Welcome to XDA and good luck
For the APPS2SD do this....
http://forum.xda-developers.com/showthread.php?t=500387
OH, first backup EVERYTHING on your SD card to your desktop.
Open the terminal program... I always do this **** in adb cause you wont catch me dead trying to type and read a small screen when adb is copy and paste.
type
su
cd /data
wget http://64.105.21.209/bin/lib/droid/sdsplit
chmod 555 sdsplit
/data/sdsplit -nd -fs 7500M (thats for an 8 gig card. so adjust it depending on what side card you have 4 gig = 3500M etc...)
Now you need to make sure you have an APPS2SD rom... That makes /system/sd available. Now you have to copy and make "aliases" from the old spot to the new... Million threads on that one. Just wanted to give props to "MartinFick"s script (bunch of commands in a file I guess you can say. You can run any partitioning sw on windows 7 or I would of gone that route...
i appreciate the replies. Ive been on this forum for about month checking throughout the day (instead of paying attention to my professors) but only signed up recently to post.
I do understand the concept of nandroid and the sd partition, I just get lost in the processes very quickly. In my life Ive only learned by screwing things up so im ready for almost anything. I dont want to get stuck without a phone though so Ill definitely try to get a better understanding before trying anything dramatic. I guess Ill keep looking for some website that has a search where I can just type in all of the language I dont understand, surely this type of site exists I just havent found it yet...
southsko said:
For the APPS2SD do this....
http://forum.xda-developers.com/showthread.php?t=500387
OH, first backup EVERYTHING on your SD card to your desktop.
Open the terminal program... I always do this **** in adb cause you wont catch me dead trying to type and read a small screen when adb is copy and paste.
type
su
cd /data
wget http://64.105.21.209/bin/lib/droid/sdsplit
chmod 555 sdsplit
/data/sdsplit -nd -fs 7500M (thats for an 8 gig card. so adjust it depending on what side card you have 4 gig = 3500M etc...)
Now you need to make sure you have an APPS2SD rom... That makes /system/sd available. Now you have to copy and make "aliases" from the old spot to the new... Million threads on that one. Just wanted to give props to "MartinFick"s script (bunch of commands in a file I guess you can say. You can run any partitioning sw on windows 7 or I would of gone that route...
Click to expand...
Click to collapse
The steps seem doable but it says to use jesusfreak's build, i am on dude's will this be a problem? thanks
Simple...we are the borg! The apparent knowledge is actually just one giant shared conscience, connecting our minds together from the time we log onto XDA...and we think you should join us. *Evil Laugh*
knight4linux said:
Simple...we are the borg! The apparent knowledge is actually just one giant shared conscience, connecting our minds together from the time we log onto XDA...and we think you should join us. *Evil Laugh*
Click to expand...
Click to collapse
ROFL.
DMaverick50 said:
I guess Ill keep looking for some website that has a search where I can just type in all of the language I dont understand, surely this type of site exists I just havent found it yet...
Click to expand...
Click to collapse
I'm not sure if that exists. You see, almost all of those terms were invented by people in THIS forum.
DMaverick50 said:
The steps seem doable but it says to use jesusfreak's build, i am on dude's will this be a problem? thanks
Click to expand...
Click to collapse
I did it on the dudes. Any (i think) build that enables the ext partition to be mounted to /system/sd will work...
So can I partition while on this regular build and then flash the apps2sd build or do I need to first download an apps2sd build and then do the actual partition?
some help
When it says to use the jf build that's just the one he used and is familiar with the steps the root hack the phone are the same no matter what. Now the thing you want to do is learn one proccess and stick with it weather it be abd, fastboot, or the sdcard method for beginners or noobs I do not suggest adb or fastboot cause it require knowing how to use a comand line and if you don't know what that is then don't try it. But like everyone says read about it first before you take the plunge also since you have a friend who can do it have him show you how he does it sometime seeing it done on the fly or being told while doing it with someone there to take over if things go wrong is always good. Have fun flashing and once you figure it out do it a few time to get used to it
DMaverick50 said:
I had a friend root my phone and I know if I want to flash a new build I rename the file update and drag it to my android folder then restart the phone a certain way and press alt s to load the build.
I love my g1 and the 1.5 build Im using but I cant get any further because Ive scoured the internet and these threads and I just cant figure out what all of this computer jargon means and I dont understand how anybody does know without taking classes in it.
I think I should make a nandroid backup and partition my sd card to run apps but good lord what does this mean (regarding nandroid)???---
"anyone who has root on their G1 and has the engineering/dev spl bootloader [1] (or has a dev phone) + a recovery image with busybox and adbd running as root [2"
and this (regarding sd partition)???---
pre-requisite "You created the FAT32 / EXT2 combo partitions" I mean this is a PRE-REQUISITE! I found a thread regarding the fat/ext deal and didnt understand it either.
I know nobody is here to babysit but is there some website somebody can direct me to to begin understanding what Im reading, I mean I read through the sd partition for dummies thread and I literally understood MAYBE 10% of the words, if thats for "dummies" im clearly the "dumbest"
I have the will I just dont have the way, ive typed the language i dont understand into every search engine I know of and Ive learned nothing. You guys are born geniuses
and what the hell's a "script"
Click to expand...
Click to collapse
heheh .. didn't we mention we're all a bunch of geeks - LOL - genius cannot be found here (pointing at self) .. i have been known to have a couple bright ideas now and again tho
"script" is just a funny way of saying "we did the work for you" .. all those lines of text that nobody wants to type over and over and over are all neatly packed into one little file .. type the name of the file and VOILA!! all those lines of text are spit into the little pocket sized computer and you have no blisters on your thumbs to show for it
now .. if we could only find a script that got us thru rush hour traffic
DMaverick50 said:
So can I partition while on this regular build and then flash the apps2sd build or do I need to first download an apps2sd build and then do the actual partition?
Click to expand...
Click to collapse
I did what I posted then flashed the APPS2SD rom and then transferred everything over, but when I flashed it it still had all my apps so I would say you can do it before also.
Remember to nandroid backup before you try and move all your files.
OT
Once you get adb running sending all these commands are so easy as you copy and paste and you can restore your phone back the way it was in 2 minutes...
southsko said:
I did what I posted then flashed the APPS2SD rom and then transferred everything over, but when I flashed it it still had all my apps so I would say you can do it before also.
Remember to nandroid backup before you try and move all your files.
OT
Once you get adb running sending all these commands are so easy as you copy and paste and you can restore your phone back the way it was in 2 minutes...
Click to expand...
Click to collapse
i see. im so much more confident attempting the partition after these posts im tempted to ask for the same help with nandroid since ive looked through the threads. But I guess i should head to one of them and start asking questions i know they run a pretty tight ship around here with duplicate threads and off-topic ones and what not...
nandroid was so much harder to read in the thread than it actually is
I'm hoping this thread may help other people.... and will try and help till I run out of beer.. anyway
restoring a backup when you are can connect with fastboot is so simple. Once you get adb working then dl and put fastboot in the tool dir. Then you go to your sd card /nadroid/randomcrap/whatever date/ and copy the 3 files below into the same tools directory.
from the command line on your computer type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
I flashed to one of the first cupcake roms and was like **** this! flashed right back to my old backup. ahhhhh!!!
southsko said:
nandroid was so much harder to read in the thread than it actually is
I'm hoping this thread may help other people.... and will try and help till I run out of beer.. anyway
restoring a backup when you are can connect with fastboot is so simple. Once you get adb working then dl and put fastboot in the tool dir. Then you go to your sd card /nadroid/randomcrap/whatever date/ and copy the 3 files below into the same tools directory.
from the command line on your computer type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
I flashed to one of the first cupcake roms and was like **** this! flashed right back to my old backup. ahhhhh!!!
Click to expand...
Click to collapse
Get ready to laugh..............adb? Fastboot? Everything else looks straight forward ( I assume I'm copying the 3 things to sd thru cpu)...
lmao...
About a day ago I didn't know anything about rooting and what it was but now I know to a degree from many hours of reading.
These are the steps I did.
You have to make sure that you choose the correct one click root method for the DI07 patch. Obviously you need to put the epic in debugging mode and click on the appropriate run.bat command and let the batch run. That part wasn't to hard for me, pretty much self explanatory.
Also to check for "root", to make sure your epic is rooted, download titanium backup from the android market and if it launches your epic is rooted and plus it will say root status "ok"..
The part I had issues with was with the one click clockwork recovery. Especially when people started talking about typing in commands in the dos prompt. I'm ok with doing that but it wasn't explained in full detail regarding what to do.
So first thing that I had to figure out was what they meant by c:/android-sdk-windows/tools and where was this located. I didn't have this file on my cpu on the c: drive and i was lost at this point being that I didn't know where to get it. I later found out and if im wrong please tell me you had to create your own folder on your c: drive so you can point to it from the c: prompt in dos. So I went ahead and did that.
In the tools folder from android-sdk-windows folder you would go ahead and place the contents of the clockwork recovery files in the tools folder. So wahla I now have a folder I can point to in the dos prompt. At this point I still didn't know if this is going to work or not but I felt like I was close.
Next step was to follow "open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code."
adb devices
adb shell
su
remount rw
exit
exit
first you need to type cd C:/android-sdk-windows/tools and press enter to point to that folder. And run subsequent commands from there.
If when you type in adb devices and a device does not pull up that means that the usb drivers are not installed properly for the epic phone and you need to look into that first.
After you run those commands now you can go ahead and run the run.bat file for the clock works recovery. But also make sure your still in debugging mode.
This might take a few tries but it will eventually work and if it does not work after trying to flash the recovery and the epic reboots pull the battery (reinstall battery) and then try to go into recovery by pressing the vol down--camera--and power button at the same time and you should see a green recovery screen.
I wish someone had typed something like this sooner so I wouldn't of had issues.
I hope this helps at-least one person.
Good idea except it's already been done :-\
http://forum.xda-developers.com/showthread.php?t=786305
Whosdaman said:
Good idea except it's already been done :-\
http://forum.xda-developers.com/showthread.php?t=786305
Click to expand...
Click to collapse
I know I was trying to follow that but there was parts missing that I didn't understand for ex. the part where I had to create the actual folder it never stated to create a folder but it wanted you to point to it in the dos prompt. And yes that tutorial did help out tremendously but i was still a little lost. My explanation fills in the missing gaps or parts. But thank you for pointing that out.
Maybe with noobnl latest version of the clockwork installer (version 32 with mount rw included in the script) you no longer need to go into adb?
jimmyz said:
Maybe with noobnl latest version of the clockwork installer (version 32 with mount rw included in the script) you no longer need to go into adb?
Click to expand...
Click to collapse
That is correct. Version 32 is truly one-click.
mattallica76 said:
That is correct. Version 32 is truly one-click.
Click to expand...
Click to collapse
Thats true
I'm not quite as noobish as the OP but I'm a complete noob to Android and -nix os's in general (besides a tiny bit of unix experience and a non-fear of command-line interfaces). Still, I have enough fear of the process to wait until Epic ROMs are a little further along and more refined to the degree that that's possible. If I weren't quite so noobish I'd dive right in.
hello xda!!! been doing alot of reading here and desided that i wanted to be part of the action...with that said...
did some reading on how to get clockworkmod on the mesmerize and have no clue how in gods name to use adb...is there a how to that could help me better understand how to use it and get this on my phone after i have it rooted...soory for the noob question but as you can see. im a noob at this. only phone i have really modded is the samsung acclaim (which btw is a weak phone but good for the noobie droid user) so any help is greatly appreciated. thanks in advance guys and i look forword to helping devs by testing and such
adb, or android debug bridge, is a tool distributed with the android sdk. In current versions of the sdk, it is located in the platform-tools folder, which only appears after you download the sdk tools after downloading the sdk zip itself.
It should be noted that usb debugging needs to be enabled on your device in order for adb to work properly. This can be turned on under: Applications > Development
To use adb, you open up a command window if on windows or a terminal emulator if on linux or mac. Type:
adb <command> [options]
Where command is any one of the commands listed when typing "adb help" and options are things like file names, paths, or other flags.
Common commands include:
pull
push
shell
pull copies a file on your device to your current working directory (or the optional specified location)
push copies a file from your computer onto the device
shell invokes a simple shell on your device allowing you work in a linux like environment on your device
There is a reboot command that is sometimes helpful but that can always be done using the power button on the device.
You will probably only use push and shell.
Examples:
adb shell
adb push update.zip /sdcard/update.zip
Hope that clairifies things a bit.
yes it does sir...so with those commands i can "push" the clockworkmod onto my mesmerize and have that beautiful recovery? the only directions i found where using the adb. if there any way i can screw this up ei: mistyping or will it just say invalid command or something? and again ty for the fast response!!!
you got the thanks for that...lol...im grateful for any and all help
Typos shouldn't hurt. If it's a bad command it just won't execute. If it's a bad filename you may have to clean up a bit (like remove the file that is improperly named or in the wrong directory) but nothing fatal should happen.
alright...i feel a bit more confident that i can make clockworkmod happen when i get my mesmerize and get it rooted...any other suggested mods for spped?
You should install a custom ROM, (I use Super Clean, some people prefer the pick n pack) then a theme you like from the themes and apps section, then install the voodoo lagfix kernel. Everything mentioned can be found in the Mesmerize forum.
yea i seen voodoo but wasnt quite sure what exactly it does. as far as the pick n pack or super clean...could you tell me the difference or does it say it on the page where it was posted and im just blind and didnt see it?
BakedTator said:
yea i seen voodoo but wasnt quite sure what exactly it does. as far as the pick n pack or super clean...could you tell me the difference or does it say it on the page where it was posted and im just blind and didnt see it?
Click to expand...
Click to collapse
Its obvious you didn't read the threads.
Sent from my SCH-I500 using XDA App
ADB is nice and all ..
But there other ways to install and do everything needed to Flash a ROM or Kernel.
How to get ADB up and running.
And a couple other great links for learning more.
http://forum.xda-developers.com/showthread.php?t=502010
http://forum.xda-developers.com/showthread.php?t=872128
If you look in the Clockwork Mod thread here in the Mez forums there are walkthroughs on BOTH ADB method to get CWM working and sans ADB methods.
And again. Always Read.. Read again.. if all else fails.. Read once more.. And ask.. Everyone here is very informative and glad to help when we can.
I knew nothing of Android before I came here and a month later I know enough now to be dangerous.. LOL
skitzo_inc said:
Its obvious you didn't read the threads.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
i did read just havnt read over it several times to see if i have missed anything...just a lil scared of adb because i have never used it before..i have an acclaim and could do everything from the swupgrade flasher for the moment and that made life easy(aint tryin to brick a 600$ phone)
to Sighcosis
thanks for the link...will read over them tonight seeing as my phone will be here no later than Wednesday and i wanna have everything downloaded and ready to roll cause the second i get this phone imma start fashing it and getting everything i want on it...again thanks for all the help guys...now more reading
...you need to make sure you can make it through this checklist.
This isn't a "how to" -- there are plenty of threads about that and stickies and search work pretty well, as does the SGS4G Wiki.
1) How long have you owned your phone? If it is brand-spanking new and your carrier will exchange it if it turns out to be defective, stop here.
2) Why are you contemplating installing whatever it is? Are you confident that the developer knows what they are doing? There is a wide range of skill and an even wider range of testing of things you might find on XDA.
2) Do you understand that virtually all ROMs, tweaks, kernels, what have you that you find on XDA, are all experimental, without warranty, and may turn your phone permanently into an expensive paperweight? Yes you can literally fry the innards of a phone with bad software, or even inappropriate user settings.
3) Are you prepared to be without your phone being functional for hours, days, or longer? Expect it. You're thinking of flashing experimental software.
4) Is your computer stable and reliable? Do you have or have you ever had any issues with USB or Internet connectivity? Fix those first.
5) Have you already installed and know how to use adb? Have you confirmed that it works with your computer, cable, and phone? This means understanding and having used at least:
adb push
adb pull
adb shell
adb logcat
adb remount
as well as shell commands including at least
# logcat
# dmesg
# cat /proc/kmsg
# mount -o rw,remount /system
# mount -o ro,remount /system
Shell redirection to a file, for example, # dmesg > /sdcard/dmesg.today.txt
Using crtl-C to terminate the foreground process in a shell
Yes, "this ain't no iPhone" when you start installing custom ROMs, tweaks, or whatever. You should be prepared to deal with the Linux part of the phone; you're often installing a new operating system and may have to deal with its underpinnings.
No, your GUI-driven "root explorer" really isn't the right tool. You have to be very careful with Windows text editors too. You're lucky I'm not asking you to learn vi.
6) Have you installed and know how to use
Better Battery Stats
aLogcat
aLogrec
7) Have you installed Heimdall, and confirmed that the drivers work for your system (very important for Windows)?
8) Have you already downloaded the "back-to-stock" package for your phone?
9) Have you installed Titanium Backup, preferably Pro, and have complete backups of your system?
10) Have you backed up your Contacts (you can use the phone's Contact app to do this)?
11) Have you backed up your phone logs and SMS/MMS (you can use Backup SMS & Restore and Call Logs Backup & Restore)?
12) Do you have a copy of all of these on something other than the phone and the microSD?
13) Have you read both the thread in Development and the thread in Q&A for the back-to-stock package as well as what you are about to flash? Really, I mean it. Yes, the whole thing. If you don't have time to read the threads, you probably shouldn't be flashing your phone.
If you weren't able to check off all the above. STOP NOW.
OK -- backups in hand, power down your phone. Pull the SIM. Boot into recovery. Do a full backup of everything there as well. This is a "nandroid" backup. (If you're on "stock" without a kernel with custom recovery already flashed, you won't be able to create a nandroid backup.)
Flash the back-to-stock package according to the instructions. Were you able to do that successfully? Did your phone boot? Failure? Read the thread on the back-to-stock package carefully. They really are pretty bullet-proof. You're going to get terse responses if you have problems with the back-to-stock. If you fail here, restore that nandroid backup in your recovery. Go back and make sure you understand how flashing works and re-read the instructions.
Once you can go back-to-stock, make sure you can restore from your backups from steps 9-11. Yes, your SIM is still out, that way you won't be changing anything important on your phone. If you can't, restore the "nandriod" backup. Yes, go back and re-read things again until you understand and can do this reliably.
Made it to here? Go ahead and follow the flashing instructions for your ROM that are in its Development thread, generally in the first couple posts. You did read the entire thread, yes?
Restore your data from backups, if needed. Once you're confident it is running properly, power it down, and now insert your SIM again. Power it up and enjoy your new software.
Have a problem with a ROM or a piece of software? Remember that the problem basically doesn't exist until a dev can reproduce it, or see logs of it happening. Need a hint? See steps 5 & 6 here.
Sticky please.
Thread stickied... but let me run through my answers...
jeffsf said:
...you need to make sure you can make it through this checklist.
1) How long have you owned your phone? If it is brand-spanking new and your carrier will exchange it if it turns out to be defective, stop here. SGSIII - less than an hour...
2) Why are you contemplating installing whatever it is? Are you confident that the developer knows what they are doing? There is a wide range of skill and an even wider range of testing of things you might find on XDA. I want to play!...
2) Do you understand that virtually all ROMs, tweaks, kernels, what have you that you find on XDA, are all experimental, without warranty, and may turn your phone permanently into an expensive paperweight? Yes you can literally fry the innards of a phone with bad software, or even inappropriate user settings. YUP
3) Are you prepared to be without your phone being functional for hours, days, or longer? Expect it. You're thinking of flashing experimental software. Hope not!, but sure... read user comments (thread) before flashing...
4) Is your computer stable and reliable? Do you have or have you ever had any issues with USB or Internet connectivity? Fix those first. Motherboard bluescreens once a month randomly... gotta replace that soon....
5) Have you already installed and know how to use adb? Have you confirmed that it works with your computer, cable, and phone? This means understanding and having used at least: Never used ADB personally... for my captivate or SGSIII
adb push
adb pull
adb shell
adb logcat
adb remount
as well as shell commands including at least
# logcat
# dmesg
# cat /proc/kmsg
# mount -o rw,remount /system
# mount -o ro,remount /system
Shell redirection to a file, for example, # dmesg > /sdcard/dmesg.today.txt
Using crtl-C to terminate the foreground process in a shell
Yes, "this ain't no iPhone" when you start installing custom ROMs, tweaks, or whatever. You should be prepared to deal with the Linux part of the phone; you're often installing a new operating system and may have to deal with its underpinnings. Not a Linux fan....
No, your GUI-driven "root explorer" really isn't the right tool. You have to be very careful with Windows text editors too. You're lucky I'm not asking you to learn vi.
"Root explorer" app works great. But i would hardly call it GUI driven... lol
6) Have you installed and know how to use
Better Battery Stats Never heard of it
aLogcat NOPE
aLogrec NOPE
7) Have you installed Heimdall, and confirmed that the drivers work for your system (very important for Windows)? Hate Heimdall, odin works just fine. Its samsungs offical software, i think it should work. (It does). Chickens.
8) Have you already downloaded the "back-to-stock" package for your phone? Yes before i bought the phone.
9) Have you installed Titanium Backup, preferably Pro, and have complete backups of your system? Yes but after flashing first phone few times...
10) Have you backed up your Contacts (you can use the phone's Contact app to do this)? Sync to google account. no back up needed. figured that out before i found xda.
11) Have you backed up your phone logs and SMS/MMS (you can use Backup SMS & Restore and Call Logs Backup & Restore)? Titanium backup does this as well
12) Do you have a copy of all of these on something other than the phone and the microSD? Some... AND Titanium backup can sync to dropbox account or box account.
13) Have you read both the thread in Development and the thread in Q&A for the back-to-stock package as well as what you are about to flash? Really, I mean it. Yes, the whole thing. If you don't have time to read the threads, you probably shouldn't be flashing your phone. Yup
If you weren't able to check off all the above. STOP NOW.
Click to expand...
Click to collapse
8 out of 13... damn. i should stop flashing and give my recognized developer status back... LOL
TRusselo said:
Thread stickied... but let me run through my answers...
8 out of 13... damn. i should stop flashing and give my recognized developer status back... LOL
Click to expand...
Click to collapse
Heh, we gotta get you an sgs4g and have you show me how to get this crap working without using logcat or reading dmesg.
Trying to install jelly bean on my sgs4g
so far i did everything that's on this page for post 1 http://forum.xda-developers.com/showpost.php?p=21953587&postcount=1
now i want jelly bean what do i do please helpp
salutparis said:
so far i did everything that's on this page for post 1 http://forum.xda-developers.com/showpost.php?p=21953587&postcount=1
now i want jelly bean what do i do please helpp
Click to expand...
Click to collapse
This really isn't a support thread. It's more of a PSA.
If you want help, I'd suggest searching in the Q&A forum.
Hi Everyone,
I'm using a Samsung GT-N7105. It has 16GB of internal memory. It has no external SD card.
A few days ago my phone's screen went black. Everything else works fine, including touch, just that the screen is always completely black.
I took it to a repair centre. After the repair centre ran some tests, (they kept my phone for 2 days,) they confirmed it was the LCD screen problem (i.e. a hardware issue). Since that LCD screen is expensive to repair, I chose not to repair it.
So now I want to install Android Screencast on my phone. I connect my phone to my desktop, and to my surprise I discover that USB debugging isn't enabled anymore!
So I call the repair centre and ask them what software changes they made to my phone. Their response is:
1) The partition table has definitely NOT been altered.
2) "Your Android version has not been upgraded."
3) "We used a special software to format your phone." They declined to tell me what software they used, and they don't seem to know which partitions have been "formatted"! But they did say that "format" was not the same as "factory reset".
(Btw the people at the repair centre are non-native English speakers, whereas my first language is English, so it was hard to ask about technical details.)
Therefore my best guess about the software state of my phone is:
1) It's running stock Android 4.1.2, which it's been running since the first day I bought it
2) The bootloader should have no KNOX nonsense
3) Recovery should be stock recovery
4) A few partitions have been "formatted" to unknown states
5) There are no longer any pattern, PIN, or password locks on my phone. If my phone is on and it's been sitting idle, I just have to tap the home button, then swipe the screen, and it unlocks.
I can reconstruct the partition table of my internal memory if you guys need it. I did an entire dump of mmcblk0 about two months ago.
(Btw the size of that dump of mmcblk0 is 15,758,000,128 bytes, which is significantly less than 16GB, even if you count by 1000s instead of 1024s. Unimportant side question, but does anyone know why?)
**************
My main question is: How do I enable USB debugging ON ANDROID with the black screen restriction?
I've searched the forums, and in thread 2395047 (can't post links yet) the recommendation is to flash CWM recovery to get adb access. But keep in mind that my ultimate goal is to be able to install Android Screencast on my phone, so that I can regain full phone functionality (with the help of an attached computer screen). I don't quite see how adb access via CWM recovery can help me to achieve this goal.
Also, I've never actually used CWM recovery before and don't know how it works. One of my concerns is: Once I have flashed CWM recovery, and after I boot into recovery, do I immediately get adb access just by hooking up to USB cable to the desktop? Or do I first have to select some setting, which would be tough to do with a black screen?
Thanks in advance for all your help!
Ernest
(Note to mods: I accidentally posted this question earlier to xda assist when I wasn't logged in. You can delete the earlier duplicate.)
Hello,
I've been dealing with android for a while and have been a member of XDA for a while. In my time here I've searched for a solution to this issue many times all over the web and XDA but never came up with anything useful.
Of the possible solutions I've found, the most likely possibility is to use an OTG cable and mouse to interface your device but this requires you to see the screen which is not an option for you. adb in this situation is only useful if you want to retrieve data from your device. I do remember finding something on the web that could potentially help you turn on USB debugging but I'm having trouble finding it now. I'll keep looking but can't promise anything. In the meantime, try posting your question in the forum linked below.
http://forum.xda-developers.com/galaxy-note-2/help
If that doesn't help you find answers then try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
I hope this helps, good luck.
Hi Droidriven!
Thank you so much for taking the time to read and reply to my question.
Guess what, with the help of workdowg, I managed to work out a solution! My saving grace is that I'm running Android 4.1.2 and not one of the newer versions. My understanding is that if I was running one of the newer versions of Android, then I wouldn't even be able to get adb access via CWM recovery, because of the extra security measures. (Although I might be wrong about this point; I am still noob.)
I solved my problem in the following way:
1) Flash CWM recovery via ODIN Download mode
2) Boot into recovery, connect phone to desktop computer, open a command line terminal
3) Type "adb shell" to get a root shell in CWM recovery
4) In that root shell, type all the commands in the last code box at the end of the following post:
http://forum.xda-developers.com/showpost.php?p=63829295&postcount=27
(Much thanks to workdowg for this step)
5) Type "exit 0" to exit the shell in CWM recovery, then type "adb reboot"
6) Wait for my phone to reboot to Android
7) Type "adb devices", and now I see that I have adb connection to Android
After this, I was also able to successfully run Android Screencast with my phone. I can see my screen again!
So now, everyone please help me think of some useful search tags for this post / thread.
ErnestChia said:
Hi Droidriven!
Thank you so much for taking the time to read and reply to my question.
Guess what, with the help of workdowg, I managed to work out a solution! My saving grace is that I'm running Android 4.1.2 and not one of the newer versions. My understanding is that if I was running one of the newer versions of Android, then I wouldn't even be able to get adb access via CWM recovery, because of the extra security measures. (Although I might be wrong about this point; I am still noob.)
I solved my problem in the following way:
1) Flash CWM recovery via ODIN Download mode
2) Boot into recovery, connect phone to desktop computer, open a command line terminal
3) Type "adb shell" to get a root shell in CWM recovery
4) In that root shell, type all the commands in the last code box at the end of the following post:
http://forum.xda-developers.com/showpost.php?p=63829295&postcount=27
(Much thanks to workdowg for this step)
5) Type "exit 0" to exit the shell in CWM recovery, then type "adb reboot"
6) Wait for my phone to reboot to Android
7) Type "adb devices", and now I see that I have adb connection to Android
After this, I was also able to successfully run Android Screencast with my phone. I can see my screen again!
So now, everyone please help me think of some useful search tags for this post / thread.
Click to expand...
Click to collapse
I'll have to remember that, I wasn't aware of the difference in 4.1.2, I've not had to deal with 4.1.2, that's good to know.
Glad you got it going, now see if you can find one of your devices on eBay that is no longer working in one or another but still has a good digitizer and glass, you may find one cheap, then you can use the digitizer+glass from the used one to fix the one you are using.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Glad you got it going, now see if you can find one of your devices on eBay that is no longer working in one or another but still has a good digitizer and glass, you may find one cheap, then you can use the digitizer+glass from the used one to fix the one you are using.
Click to expand...
Click to collapse
That's a really good idea, which I didn't even consider. (Maybe because I've never meddled with hardware before.)
Thanks!