Related
So i decided to go on a Flashing spree today for no reason, i just felt like it..
I started out by flashing 2.2 on my 2.1 phone, that all worked out quite well, but for some reason i could not root it. ( I used http://forum.xda-developers.com/showthread.php?t=845558) It all worked out nicelly but since i could not root it, i just game up on it.
After searching i found http://forum.xda-developers.com/showthread.php?t=734475 to revert my phone back to its original firmware. I have a Galaxy s Vibrant, so i thought it was the correct thing. But since i installed it i have alot of problems.
First of all, when i plug it into my USB the phone auto turns off. And it will not charge when the usb is in.
I have rom manager installed, but when i try to run a rom, i keep getting the error (status = bad ).
Also the phone wont recognise my SimCard so i cant stay with this firmweare anyways.
flash back to a stock Froyo
then boot into the Recovery Mode
then wipe data, and wipe cache
see if that helps
Do you know the best place where i can get a stock froyo rom ?
amnoric said:
So i decided to go on a Flashing spree today for no reason, i just felt like it..
I started out by flashing 2.2 on my 2.1 phone, that all worked out quite well, but for some reason i could not root it. ( I used http://forum.xda-developers.com/showthread.php?t=845558) It all worked out nicelly but since i could not root it, i just game up on it.
After searching i found http://forum.xda-developers.com/showthread.php?t=734475 to revert my phone back to its original firmware. I have a Galaxy s Vibrant, so i thought it was the correct thing. But since i installed it i have alot of problems.
First of all, when i plug it into my USB the phone auto turns off. And it will not charge when the usb is in.
I have rom manager installed, but when i try to run a rom, i keep getting the error (status = bad ).
Also the phone wont recognise my SimCard so i cant stay with this firmweare anyways.
Click to expand...
Click to collapse
It looks like you flashed the actual "Vibrant" (T-Mobile US) type firmware onto your Bell i9000M phone... I dont know if you can flash back as the Download and Recovery modes for the actual Vibrant are different than the i-9000 model phones...
@Allgamer, can you be of any further help?
btw i really hate Samsung right now, why would you release a phone called a i-9000m Vibrant, then release a phone under the brand name vibrant
amnoric said:
btw i really hate Samsung right now, why would you release a phone called a i-9000m Vibrant, then release a phone under the brand name vibrant
Click to expand...
Click to collapse
I agree with you on this man. How confusing could they make it? I guess they did it to sort of distinguish our model of i9000M from the International version but couldnt they at least give a different name from the U.S. model?
They even look identical except for the fact that the U.S. Vibrant has 4 soft keys at the bottom where we have the 2 soft and 1 hard key...
Well now that my panic attack is over and my phone is back to normal after Flashing 2.2 on it ( FOR I-9000m even ).
I have another random question..... what is the best way to root 2.2.. since the whole point of the **** up was because i would not root it
amnoric said:
Well now that my panic attack is over and my phone is back to normal after Flashing 2.2 on it ( FOR I-9000m even ).
I have another random question..... what is the best way to root 2.2.. since the whole point of the **** up was because i would not root it
Click to expand...
Click to collapse
I recommend the app called z4root by RyanZA. You can find it on the Market. It is a one click root that requires no flashing of any kind.
You may have to start the app and if it seems to hang for a while just perform a reboot and run the app again and it will root within 30 seconds. Also be weary in the Market as someone has stolen the icon and everything from RyanZA and the "rip off" app is NOT complete. Make sure the one you download states it is from RyanZA...
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
gtabspring said:
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.
swedishcancerboi said:
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.
Click to expand...
Click to collapse
Thanks for the suggestion. I think your version of galaxy tab is different with mine and I am not sure that it will work. I am really desparate for solution. This disaster started when the tab's battery is low and suddenly off and when it's charged and turned on it bricked
Point being, tabs are tabs. You will need to use the same procedure, but a different ROM that is designed for your tablet. Go there and find a ROM. There is a thread about unbricking your tablet, I think in the Android Development section that should have a link to samfirmware.com and may provide you with a ROM version that should work. something that may help: plug your tab into the charger at least overnight. I used the stock charger and cable and charged it for 12 hours or so. I did not get any indication that it was charging since the screen and softkeys would not respond, but it did charge.
Of course, I look back and I think you have an indicator, but still a good idea. Try it anyway. Can't make it worse, eh? Mine seemed hardbricked, but it wasn't. I was real close to taking it apart before I found something that works. I believe, IMO, what really fixed it is flashing ROM (PDA), Modem, and CSC files all at once. It could have been something else, but that was the last thing I did before it finally booted.
Go to samfirmware.com, create a free account, and sign in. Then go here (I think your tab is a P1010, correct?) http://www.samfirmware.com/WEBPROTECT-p1010.htm
and Download this:
1010XWKC1 ## MULTI - CSC - OXXKC1 P1WIFI 2.2.1 2011 March DOWNLOAD
(click on DOWNLOAD)
Unzip that file you just downloaded
Start ODIN
Hold VOL DOWN and plug in tab to computer
I believe 3 files should be in the .rar (you can use 7-zip to open, Google it)
the MODEM file goes in Phone.
the CSC file goes in, you guessed it, CSC
last one is PDA.
I think I just rewrote instructions that can be found in the Galaxy Tab Bible. lol. This is what I would do. It worked for me.
Password for P1000XWJJ7.rar
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.
I'm having the same problem were you able to fix it?
jairo_pena said:
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.
Click to expand...
Click to collapse
try sampro.pl
see if that works.
I too require the passwords to be able to extract these files if someone would be so kind.
Copied straight from SamFirmware.com. It is right at the top of the download page.
try both of these... seems it could be either one of them
## Password is samfirmware.com
# Password is samsung-firmwares.com
Click to expand...
Click to collapse
where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website
oxbeast1210 said:
where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website
Click to expand...
Click to collapse
do a quick search of the dev thread for EA24 and you should be able to find the original SPH-P100 files. then you can find the EB28 and EF17 updates as well to get all the way to the official GB release.
tried the suggested file still get the error that the OP got in the first screen
oxbeast1210 said:
tried the suggested file still get the error that the OP got in the first screen
Click to expand...
Click to collapse
ok, no one likes a bricked device so let's see what we can do to help you. tell us where you are with your problem. by that i mean what model do you have, what rom were you running, what did you do or try to do that bricked your phone. i'll keep an eye on this thread looking for your response and we'll go from there.
I have the sprint p100 model room was stock rooted gingerbread.
I mailed the Tab to my brother when he got it tab battery was
completely dead and after he charged it and turned it on
he had that error
---------- Post added at 01:30 AM ---------- Previous post was at 01:29 AM ----------
thank you very much for helping me!!
can anyone help?
I have the T-Mobile version of this, but here's a guide and download files to recover your stock ROM. You can follow the entire guide if you want the Overcome ROM as well:
Guide:
http://www.teamovercome.net/p1000/?page_id=17
Downloads:
http://www.teamovercome.net/p1000/?page_id=21
Good luck!
NOTE:
Sprint modem is not listed, but you can fix that later. If you can get it to work with this guide & using the last modem file, we can go from there.
gtabspring said:
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
try the one on teamovercome . net I have soft bricked mine but it worked after i followed their instructions there..
Has anyone EVER confirmed that overcome work for non GSM tab, for unbricking and CwM functions?
Sent from my GT-P1000 using XDA
Hello,
I am a newcomer to the Forum and I would be grateful if I could benefit from the experience and the knowledge of the experts.
I have an unlocked HTC G1 phone. I use the ATT network.
I would like to install Gingerbread.
Could somebody give me the direction where I would find a step by step guide to replace my actual Donut version with Gingerbread.
Here are the specs of the phone:
Model number Android Dev Phone 1
Firmware version 1.6
Baseband version 62.50S.20.17H_2.22.19.261
Kernel version 2.6.29-00479-g3c7df37
[email protected]#19
Build number DRC83
well if its a dev phone it should already be rooted so ignore those steps, check and see your radio/spl (power on holding camera button)
your answer here will determine the next step
chances are you need to follow this link _ http://forum.xda-developers.com/showthread.php?t=831139
once this is complete follow the steps here _ http://forum.xda-developers.com/showthread.php?t=882356
if you need more help let me know!
Thank you very much for your reply.
Unfortunately my knowledge in this field is infinitesimal small.
That is why I am looking for a step by step guide.
Maybe I put myself in the wrong forum for my level and my needs. My apologies.
The only thing I know is that my phone does not need to be rooted.
Thank you again for your advice and your time.
Happy New Year to all of us
if your not finding what you are looking for ill see what i can do
first off i need to know your radio/spl - this will help me determine what you need to do next
just type in everything off the screen that will be rainbow colored or have three androids on skateboards
to check the screen, power off your phone, then hold down the power (red button) and the camera button at the same time. tell me what it says...
after you write all of that down press the green, red and menu buttons all at once and the phone will reboot normally.
gunner1937: There is a link I found in another thread for an older version of ROM Manager which will work on Android 1.6. Since you're rooted with a Google ADP phone this might be all you need. But I would go in the menu and do a factory reset.
I upgraded my T-Mobile G1 from stock Android 1.6 to CyanogenMod 6.1 (Android 2.2.1) three days ago following the instructions on http://wiki.cyanogenmod.com/wiki/HTC_Dream:_Rooting
I will stick with it for now. It came bundled with the ROM Manager app.
In the past week I've researched upgrading to Gingerbread and just recently there may be a bug uncovered where the phone no longer goes into Deep Sleep mode. This means the battery usage is not ideal compared to other earlier ROMs. It turns out virtually all Gingerbread Dream ROMs use some code by ezTerry, so they may all have this issue. So.. I think I will hold off on going to a flavor of Gingerbread until I get more info on this possible bug.
In your case I believe I'd do the factory reset, then load this ROM Manager onto it. You'd need to copy the ROM Manager.apk file to your phone's SD card. I would backup the contents of your SD card onto your PC just so you have any files/songs you want, and then format it with FAT32. You can format the SD card from a Settings menu on the phone if you like. I think there's another setting in the menu to allow installing a program from unknown sources. Find that and check it in order to be able to manually install an app like this. Or I dunno, that may not be in the ADP phone. Next you'd need to get on the Android market and get a file manager to be able to dig into the SD card's file directory and install the APK file. I used a text editor called TxtPad Lite which included a usable file manager. Another one is called Astro File Manager. With something like that you can browse the file system to be able to look at the files on your SD card and install ROM Manager. You'd just find the APK file and tap on it.
So then you're reset, got the ROM Manager app that will work on Android 1.6, then you can use it. You want to let it install the ClockworkMod Recovery first thing. It's required and what the app uses to manage installing your ROMs. I myself have never actually used ROM Manager to install a ROM (I did use it to install the ClockworkMod Recovery). I've gone in and out of the app. It asked me to update it, so I did. And I decided to stick with CyanogenMod 6.1 for now. It looks like it's gone through a ton of vetting to get it really honed.
I kind of wanted a more full introduction to flashing the ROMs and stuff and the CyanogenMod guide was great for me. This looks like a relatively painless and less complicated way to safely upgrade and switch out ROMs for you, and I might've done it more or less this way if I'd discovered it first.
Thank you.
HBOOT: 0.95.0000
Radio: 2.22.19.26I
CPLD4
Personally I would recommend you install froyobylaszlo
But anyways, first of all before you start installing the 2708+ kernel, you're gonna need fastboot and adb on your computer
What OS do you have on your computer?
one laptop is Vista and the other is Win7
JediDwight said:
In the past week I've researched upgrading to Gingerbread and just recently there may be a bug uncovered where the phone no longer goes into Deep Sleep mode. This means the battery usage is not ideal compared to other earlier ROMs. It turns out virtually all Gingerbread Dream ROMs use some code by ezTerry, so they may all have this issue. So.. I think I will hold off on going to a flavor of Gingerbread until I get more info on this possible bug.
Click to expand...
Click to collapse
If you are not testing it this is a bad conclusion:
*) Deep sleep may or may not be working.. this has mixed results but the device is mostly sleeping.. so yes if completely idle (ie no cell network no wifi, screen off, no services running..) you might go from 4days uptime that the system currently gets even with an sdcard to 5 days if the problem if it exists is solved
problem is deep sleep is when the ARM11 CPU is turned completely off (it is going into low speeds correctly, and disabling other hardware into low power modes) This means when you are using the phone this state will not be entered (and thus the phone uses the same power as it is now) when a service is actively running.
Thus most peoples battery enhancements in GB are from the new APIs to allow applications to stay in the background more in Gingerbread; and a much larger problem is many applications these days are running more services than the G1 can support thus the system is constantly swapping in and out applications from memory.
Thus those whose battery on gingerbread roms is draining fast will more likely benefit from checking what is running in the backgound than waiting on a deep sleep fix if its even a problem.. since the services will still run after any fix and the battery life won't improve.
What the op needs is the 2708+ radio/SPL (that others are helping with) than nandroid in recovery can be used to switch between roms; since it provides more ram to CM5/CM6 and gingerbread roms all work with the 2708+ combination then the op can pick what works best for them in a more overall evaluation... and not just what lasts the longest when not used as a phone.
To OP:
the best way to continue is to:
1) Install fastboot (and the sdk) on your computer. you will need to search for this since the since I don't know the details for windows
2) If you already have a custom recovery (clockwork or ra-recovery) continue; otherwise you will need to install one: http://forum.xda-developers.com/showpost.php?p=4647751&postcount=1
3) then since you have HBOOT: 0.95.0000 install 1.33.2003 from: http://forum.xda-developers.com/showpost.php?p=6510019&postcount=76 this will allow fastboot and let you continue with:
4) Then the installation section at: http://forum.xda-developers.com/showthread.php?t=831139 (The files section will have the various files required and older roms that have been ported to work on the new SPL/Radio.. newer roms mostly will work per instructions on the rom's thread) .. read the entire post before doing anything.. as this is a major change to the phone, and the actions to fix something if you run into a problem may be slightly different than they were with more stock roms..
Try to get a feeling for what is needed before you begin .. we know its a bit of an involved process.. but most users have auctioned this in smaller steps originally.
(Note the cmwiki will probably be the best way to install recovery)
forum.xda-developers.com/showthread.php?t=910008
Download the drivers only pack
I think it includes fastboot
I can't check, if not tell me and ill upload my files as soon as I can get to a computer
search in google (or probably even xda) for "easy fastboot" if your having issues using fastboot, its exactly that an easy way to use fastboot for noobs.
also you can flash your new radio/spl as well as your rom via recovery, it isnt recommended but it can be easier if you have issues. ill tell you i have done it this way many times and have yet to brick a phone but as always my experience dosent me you will have the same. so try to follow the suggested route of fastboot is best.
upgrading to Gingerbread
I should have taken a longer rest.
I am starting the New Year with the feeling that everybody gets the right to flame me: my G1 does not work after a very bad step.
I installed on the re-formatted SD card 2 files namely DREAIMG.nbh and cupcake.
In short, I got the message "E: cannot open /sd card /update.zip (no such a file or directory). Installation aborted".
The next step was to sign my google account. It failed.
At this stage I cannot format, read, transfer, and use the SD card because it is not recognized by the computer. And of course the phone is not working.
Right now the G1 shows in the colored bars:
DREA100 PVT 32B
HBOOT- 0.95.0000
CPLD-4
RADIO- 1.22.12.29 (before doing anything to the phone the radio was 2.22.19.26I)
This phone was unlocked and set on the AT&T network.
Thanks to my wife Nexus One I can use, format, transfer files (which I did, to no avail) by inserting my SD card in her phone.
The least to say is that I really need the help, knowledge, and assistance of the Forum members.
What you don't want to hear is we see no error in what you have described. > well apart from the nbh file used it may be the original way to root but its not the easiest.
The message you are seeing in recovery is not am indication of a problem.
Ok, 0.95.0000 has no fastboot and thus you really need a custom recovery, to do that you. Need to flash it from the rom after rooting it, this means you need to try and boot the phone normally and log into Google normally.. if this fails try the following:
A.) go into recovery (home+power) and press alt+L then the combo to wipe the phone
B.) If its still not working try re-flashing the nbh
Oncce logged into google the telnet trick can work..
C.) While it needs a bit more setup, this third option is easier to install the 3rd party roms without a Google login and manual flash of recovery from system: make a goldcard ( you can do this on the n1) then put the orange nbh from the 2708+ thread http://forum.xda-developers.com/showthread.php?t=831139 this can be renamed DREAIMG.nbh and then be flashed with the gold card you made. (There are many guides on making the goldcard for HTC phones) Once flashed you will have a fastboot enabled spl that will let you flash anything by fastboot.
Thank you for helping me to breathe a little bit deeper, better, and slower.
So far I am in the same situation.
Dropping by BestBuy I found an SD micro with an adapter. It makes life easier for everybody.
I did again what I started, trying 2 different downloads of the .nbh file. Still locked at signing my google account.
Following your advice I will try to create a goldcard and follow the procedure you mention this evening.
Wait...locked at signing in to google account?
What do you mean? It shows google sign in but you can't sign in?
Do you not have a data plan?
If so, just google "activate g1 wifi"
Sent from my Gingerbread on Dream using Tapatalk
gunner1937 said:
Thank you very much for your reply.
Unfortunately my knowledge in this field is infinitesimal small.
That is why I am looking for a step by step guide.
Maybe I put myself in the wrong forum for my level and my needs. My apologies.
The only thing I know is that my phone does not need to be rooted.
Thank you again for your advice and your time.
Happy New Year to all of us
Click to expand...
Click to collapse
I'm on my phone so idk what link he posted.. but if you got the G1 development section.. look for a thread titled G1 rooting,unrooting and more or something like that by ldrifta, then look around on that thread for a gingerbread ROM
Sent from my T-Mobile G1 using xda premium
ezterry said:
What you don't want to hear is we see no error in what you have described. > well apart from the nbh file used it may be the original way to root but its not the easiest.
The message you are seeing in recovery is not am indication of a problem.
Ok, 0.95.0000 has no fastboot and thus you really need a custom recovery, to do that you. Need to flash it from the rom after rooting it, this means you need to try and boot the phone normally and log into Google normally.. if this fails try the following:
A.) go into recovery (home+power) and press alt+L then the combo to wipe the phone
B.) If its still not working try re-flashing the nbh
Oncce logged into google the telnet trick can work..
C.) While it needs a bit more setup, this third option is easier to install the 3rd party roms without a Google login and manual flash of recovery from system: make a goldcard ( you can do this on the n1) then put the orange nbh from the 2708+ thread http://forum.xda-developers.com/showthread.php?t=831139 this can be renamed DREAIMG.nbh and then be flashed with the gold card you made. (There are many guides on making the goldcard for HTC phones) Once flashed you will have a fastboot enabled spl that will let you flash anything by fastboot.
Click to expand...
Click to collapse
I am still trying to create a goldcard with the nexus 1. I cannot install a driver for it, I cannot install a driver from HTC sync, I get a message that "the device is not connected" but I can see the microSD on the computer.
This is where I am. And I do not know anymore what I have to do next since I feel I am in front of a wall.
frankdrey said:
Wait...locked at signing in to google account?
What do you mean? It shows google sign in but you can't sign in?
Do you not have a data plan?
If so, just google "activate g1 wifi"
Sent from my Gingerbread on Dream using Tapatalk
Click to expand...
Click to collapse
I did not express myself correctly.
When one reaches the sequence to sign into a Google account one has to enter email address then password.
I did that and few minutes later I got the message it could not reach the google servers.
Also, I have -rather had - a wi-fi connection since I got the G1 in December 2008.
gunner1937 said:
I did not express myself correctly.
When one reaches the sequence to sign into a Google account one has to enter email address then password.
I did that and few minutes later I got the message it could not reach the google servers.
Also, I have -rather had - a wi-fi connection since I got the G1 in December 2008.
Click to expand...
Click to collapse
There's your problem...
Wifi is off when you first turn on the phone
wiki.cyanogenmod.com/wiki/Google_Login_via_a_WiFi_Connection
Use that guide to turn it on and sign in
And if you don't want to download the entire sdk just wait until I get on my computer and ill upload just the files you need
But tell me if you still need the files or not...I don't wanna upload for nothing
And if you can't get the steps right, I can try tell you more stepbystep instructions
Sent from my HTC Dream using Tapatalk
wiki.cyanogenmod.com/wiki/Google_Login_via_a_WiFi_Connection.
Thanks for the link.
I cannot take advantage of it: Device manager shows 7 Intel ICH* universal controller, 1 USB composite device and 7 USB root hub.
Nothing else.
No USB mass storage device.
Android SdK is installed on C: but I do not know if it is properly installed or activated because I could not check "adb devices"
I am so sorry for being so stupid to ask,but m left with no option, but to ask.
I have SGH gt-i9000.
I have it working.
I use t-mobile USA
But I want to update it fully.
Have no clue how to do it.
Need elaborated steps which will tell me how can i make the best use of it.
I am actually looking for the most stable and reliable version for my phone which lets me keep it working smooth free of all bugs. I would really appreciate if some of you genius can help me out.
Thanks in advance.
Look at video on samfirmware. com and youtube, read stickies in xda, stock jvu with andip's theme and semaphore kernel is fast and rock solid.
Sent using TCP/IP
tiknaragg said:
I am so sorry for being so stupid to ask,but m left with no option, but to ask.
I have SGH gt-i9000.
I have it working.
I use t-mobile USA
But I want to update it fully.
Have no clue how to do it.
Need elaborated steps which will tell me how can i make the best use of it.
I am actually looking for the most stable and reliable version for my phone which lets me keep it working smooth free of all bugs. I would really appreciate if some of you genius can help me out.
Thanks in advance.
Click to expand...
Click to collapse
First of all, you need to download and install Kies to have the latest drivers for your phone. (You can get kies from Samsung's official webpage) Then download Odin. The latest version is 1.83 afaik. Then you need to download a proper firmware for your phone, which you can do at sammobile.com under the firmwares tab. (you need to register to be able to download, it takes half a minute). After that, extract the firmware using winrar or something like that. You should have a few files which you have to put in Odin, you can find many guides for that on how to do it and what options to tick. You have to put your device into download mode - first switch off (pull the sim card and external sd, as it might cause some errors while flashing), then hold the home-volume down-power keys for a few seconds. You will enter download mode. Before plugging in your phone to your computer, make sure no part of kies is running on your pc (use task manager). Some drivers might install. After that, Odin should "see" your device, a yellow box will appear with the port used. If all the files are at the right place, start flashing (make sure your device has at least 70 percent battery). Only unplug your phone after it has fully booted. Done!
Now you only need to apply a custom kernel. I recommend Semaphore. Search for it on the forums. Switch off your phone again and put it into download mode. Reset Odin. Put the downloaded semaphore kernel into the pda box. Plug in your phone. Flash. Done!
Please hit thanks if I helped
Sent from my sgs
I spent several DAYS getting this watch to work properly (and by properly, I mean rooted and with a new mod).
You DO NOT need an approved phone for this to work! This will allow your watch to work with virtually any phone.
All you need is a Windows PC (with Odin and the Samsung ADB drivers, although these may not be necessary...), your watch, the charging cradle, USB cord and Wondershare (although there are alternatives to this...).
Because I am a new user and can't submit links, this next part is going to SUCK for you:
Here are things to download:
Samsung ADB Drivers - Google!
The Latest Version of Odin - Google!
Wondershare MobileGo for Andoid - Google it!
V700XXUAMK7 Firmware (Build Date: 13.11.2013 -> Region: BTU (United Kingdom) PDA: V700XXUAMK7 Changelist: 2124806 Android: 4.2.2 ) - Easy to Google
Null TWRP (You can find on this forum)
SuperSU ZIP FILE (Do not open) - (Google for "SuperSU Flashable Zip" )
THE REAL NULL ROM 23!!!! Working as of 1/10/2017 - THANKS TO dbest1010
There are several pitfalls that are introduced because of how OLD most of the information on here is.
First, when you turn on your watch, you may be wondering, how can I get into USB Debugging mode?
If you are stuck on a screen that is looking for a phone to connect to the device (and this may happen more than once during this process), then you need to know this VERY SIMPLE TRICK:
Press your finger over the area where the bottom of the screen is. An orange and black box should appear with some numbers/letters in it. Do this repeatedly. A LOT. Keep pressing it. Sometimes swipe up a little or down a little, it doesn't matter, just keep rubbing it like it was your lover. Before long (sometimes it takes a couple of minutes, seriously, do not give up), the phone will go to semi-normal operation.
This will allow you to go into the settings and hammer near the version area several times (unlocking developer mode), which on the previous screen will allow you to select for USB debugging.
I'm not sure why this trick is not explained very well elsewhere on these forums. Really, if you want pretty much zero functionality from the watch, you can stop here.
You may not have the "stock ROM" loaded on this watch. Fortunately, these are still easy to find. You want the BTU version if you are in the United States.
This step is important, because even if you do not NEED to do this, knowing how to do this may help you recover from a "soft brick", and get back on track.
Put the watch into Download Mode.
To do this, hold the power button until the "Rebooting" menu appears.
Now, press the power button several times (4 or more)
A new menu appears, use the power button to move down to "Download"
Hold power button for 3 seconds, then release it
Download mode will appear
Connect the USB to your PC, then the cradle, then add the watch to the cradle
Open Odin
Leave everything as normal, and click on "AP"
Select the V700XXUAMK7 file/image
Run the process
This should get you the stock firmware rom loaded.
Here are some problems you may encounter during this phase:
When you connect the watch to the cradle, sometimes it shuts off or does something unintended. Make sure the cradle and usb are connected to the PC *before* trying to add the watch, rather than trying to plug the USB into the cradle once the watch is attached.
Odin may not "see" the watch as a device, or the installation process may not complete as desired.
MAKE SURE that Kies, Wondershare, ADB and all that other stuff is NOT RUNNING. By not running, I mean ctrl+alt+del and go to task manager in Windows and kill ALL instances of them, especially Wondershare. Do this before you think you got a bad image or something. This particular step gave me a headache for a while.
The watch should be booted with the regular firmware now. You may need to do that pressing trick on the main screen again to get it to do much else.
For installing the custom recovery ROM (this is NOT the custom ROM, but is needed and recommended to install null on your watch), you follow almost the same exact procedure as before.
EXCEPT,
1.) UNCLICK in the options for Odin "Auto Reboot"
2.) When you get to the part where you add the V700XXUAMK7 image file, instead, when you click "AP", add the Null TWRP file you downloaded previously.
After a successful install ,the watch will still be on the "downloading" screen. It is safe to restart it now, however, and you can hold the power button down and then press it a few times during the "Rebooting" phase to change to recovery mode.
If you did this right, after a brief Samsung Logo, you will see the Null TWRP screen which has several nice options on there for you.
Now, what you should do, since you know that it worked, is you need to ROOT THE DEVICE.
Don't worry about no Impactor stuff or any of that crap. If you're like me, it will not work. Don't worry about ADB or any of that either.
Use your free trial of Wondershare (or your alternative method), and add the SuperSU ZIP file to the ROOT DIRECTORY of your SD card. With Wondershare, you do this by opening Wondershare, and then connecting the device via USB. Remember what I say, put USB to PC, then to cradle, then add the watch.
Why come your Wondershare no see the watch? Make sure you did the trick on the home screen (pressing the stupid box a thousand times) to get into the Settings and enable Developer mode (keep clicking the version) and USB Debugging.
DO NOT BOOT THE WATCH INTO DOWNLOAD MODE! What are you doing?! Just open the watch up and run it regular so you can see the time, make sure USB Debugging mode is turned on, and Wondershare should see the watch. Still having problems? Try for install those drivers I linked at the top for Samsung devices. You may not need to do this.
You are STILL having problems?! Make sure no other process similar is running. No Odin. No ADB. No Kies. No Impactor. Nadda! Ctrl+alt+del and get rid of all those type processes. Then try it again.
Now, to finish the root.
Once the file is transfer over, disconnect the watch again, and reboot into recovery mode.
Go to install and select that SuperSU zip file, it will install right from the zip.
As an extra added measure, go down into the advanced options of TWRP, the recovery mode, and press on the "fix permissions". I don't know, maybe this does not help, but it does not hurt it either.
Restart the watch regular, run the SuperSU program from the "apps" section, and everything should look fine, and your watch is now rooted.
Power back down and go into recover mode again.
NOW, important! Go to TWRP again and go to BACKUP. Create a backup.
This backup is useful from this point so you can recover a fully working stock version that is rooted, because the next step may cause you a lot of frustration.
DO NOT GO TO SOURCEFORGE!!! F0mey has a page on there for the NULL ROM, and it is not even for the same device! It has version all the way to 27. It doesn't matter if you download the oldest version on there is almost 1GB and it is NOT THE CORRECT THING FOR THIS WATCH.
Do not waste your time! I kept flashing all kinds of bogus stuff on my watch trying to get it to work. Some other guy has a Galactus Mod. Don't bother! It will not work!
If you're sitting there trying to install some bogus ROM, and getting stuck in reboot mode and everything, just use that recovery you made and then come back to this thread when you have some sense in your head.
Go back to the top and get the REAL Null Rom 23. This is a mirror somebody found hosted by Kent. it is only about 300MB, not no 900MB file like the stuff on F0mey Sourceforge page.
How to install it?
Well, the same way you moved that SuperSU file over to the SD card with Wondershare, what you can do, is move the null rom over to the SD card using Wondershare. Just move the ZIP, same way as with the SuperSU. Do not open it! Once it is on the watch, this is the easy part, go into the recovery mode again, go to install, and install it.
You'll know it is correct because on the very first screen, it will say the device it is made for before it installs. The other roms say i398 or something, which is NOT THIS WATCH.
It will have all kinds of options you can tap on with your grubby finger. The recommended settings are fine, you may want to tick some of the Google stuff, like the Play Store.
Anyhow, now the whole thing will take a few minutes to install/flash onto your device.
When it starts to boot up, what is this?! It gets stuck in a loop! Galaxy logo, over and over!
No!!! After so much work! This can't be happening!!
Don't worry, this sound stupid, but just connect the watch to the cradle with the USB connected to the PC. Don't do anything else. For some reason, now it will work and boot fine and you'll be able to unplug it later and do what you like with it.
You will have to do the trick of rubbing the main screen again, with the orange and black box. Sorry, it takes forever, I know. Don't give up. Once you are done, you can connect it with your phone or whatever device.
Make sure to turn on Bluetooth on your phone, and you should be able to see the device (if not play with the bluetooth settings on the watch). Pair the devices, which requires tapping something on both screens.
Most likely, your phone also has an option under "hotspots and tethering" to allow bluetooth sharing of the internet with the watch. Once you enable that, go to the watch, and go to the bluetooth settings where the phone is connected to it, there is options in there for internet sharing with the device over bluetooth (just enable it, it is an on/off toggle).
What did I forget? This is only version 0.01 of this tutorial for you. If you need some more advices, you can write me. I may not check often, but that is life. You can find my email probably from my profile, also.
Dude..... I love you !!!! I thought id never see the gear null rom ever again. Thx bro
Awesome write up made my watch very happy!!
Thanks for all that,
Help
Good post, i have a question, this only work in android 4.3? i have 6.0 and the gear say error connection, thanks and sorry for the bad english
the recovery mode text is so small i cant read it. its stuck at the top portion of the screen. any help? i feel like i wasted money buying this. there is zero support here.
Thank you for this! This is very helpful!
Bad news, though... The Null 23 link isn't being hosted again. Anyone know a valid link to the VALID Null 23 rom?
I need the Null_23.zip too!
tamcswain said:
Thank you for this! This is very helpful!
Bad news, though... The Null 23 link isn't being hosted again. Anyone know a valid link to the VALID Null 23 rom?
Click to expand...
Click to collapse
I have same situation!! That link is not working anymore so i'm waiting the Null_23.zip custom rom for Galaxy Gear 1 which i got it 2 days ago!
Anyone have the Null_23.zip Samsung galaxy Gear's custom rom for share it to us?
Jc Lee said:
I have same situation!! That link is not working anymore so i'm waiting the Null_23.zip custom rom for Galaxy Gear 1 which i got it 2 days ago!
Anyone have the Null_23.zip Samsung galaxy Gear's custom rom for share it to us?
Click to expand...
Click to collapse
If you find something, let me know! I will do the same. I message fOmey (the Null 23 rom creator) and he confirmed he doesn't have it anymore or any links. I also asked to confirm the Null 23 roms on sourceforge.net are incorrect since they are almost 1gb in size and states in the rom installation "i9300" which is the galaxy s III phone.
https://drive.google.com/drive/folders/0B_ka0GfEx6wOMmVfb2tQblJmTmc?usp=sharing
KcajBoy said:
I spent several DAYS getting this watch to work properly (and by properly, I mean rooted and with a new mod).
...
Because I am a new user and can't submit links, this next part is going to SUCK for you:.
Click to expand...
Click to collapse
My gen 1 still works on null 23, but I got a nostalgic kick out of reading your write up. Nice job. Took me back to some good - although often frustrating - days. F0mey did nice to infuse new life back into this classic.
I came to see if anything better was out here since I last visited a good while ago; but not really. Maybe it's time to finally buy something new, and retire this one to a time capsule. (Next to the Casio calculator, $1 g-shock, nelsonic pacman/frogger, stainless mickey mouse, blue gobot/transformer, and gray fighter jet. I wish. Those didn't survive.)
Gear 1 won't connect with Samsung S8
I don't know if I am in the right place but I try and hope you wil tell if I am or not.
My watch Gear 1 always worked with my Samsung S7Edge. No problems. Now I have a Samsung S8 and it won't connect. My Sansung S8 finds my Gear1, but when I have to confirm on my Gear1 it tells me to reset the Gear 1 to its factory settings. It resets, but only starts and I cannot confirm anywhere the number that appeared on the phone. Somebody can help me?
Thanks in advance.
Only acknowledge on phone not on watch
Idebutterpiep said:
I don't know if I am in the right place but I try and hope you wil tell if I am or not.
My watch Gear 1 always worked with my Samsung S7Edge. No problems. Now I have a Samsung S8 and it won't connect. My Sansung S8 finds my Gear1, but when I have to confirm on my Gear1 it tells me to reset the Gear 1 to its factory settings. It resets, but only starts and I cannot confirm anywhere the number that appeared on the phone. Somebody can help me?
Thanks in advance.
Click to expand...
Click to collapse
You just have to acknowledge on the phone not on the watch. Just had that issue with an old S3
Battery life is terrible in null did that last year and went back to tizen
Sent from my SM-G950F using Tapatalk
A very Simple Trick - access debug mode without phone
Great guide, feels like im getting somewhere now. Slightly easier way of accessing Samsung Gear without pairing with another phone is to- On the install Samsung Gear screen(on your watch) try tapping 10-15 times on the white gear watch picture on the top left. This will bring up some message at the bottom about 'bluetooth 3 second press' whereafter you long press for 3 seconds on same picture. Watch is unlocked much easier than 'making love' and swiping up and down to get into settings haha
One question though. After installing stock rom should my software version not change in gear information settings?It seems that I am having trouble with 100% correct drivers because wondershare cant connect to my device, although it shows up in my file explorer is official latest samsung drivers fine or should i download fastboot drivers?. (any reliable links to stock rom,recovery,usb drivers and custom rom would be greatly appreciated,feels like im having trouble with the correct zip files)
I had a hard time getting all the files together so I have made a zip up and it has every file you need,even the firmware V700XXUAMK7,I added that cos on the Samsung Firmware website on slow download it took me 2 hours to download it and it like only 411 mb.
Super SU v2.85 in it there and works fine ,use Impactor_0.9.14,run Impactor.exe and click start and wait for it to finish then connect using Wondershare MobileGo and install the supersu-2-82.apk,Google play on Wondershare MobileGo don't work cos it can't find the device cos Google Play is not on the Gear 1 ,click on supersu app on the Gear 1 and it will ask you to update root files,just click on normal and it will update it and done,you have root on Gear1 now..
Here is the files in a zip.. Hope this helps sommeone,it would of helped me.. its on Mega.. here https://mega.nz/#!sAxinCDa!GR47wt4cQ6g74Ya_9An0bfmf2mel1o8dV0sNiqK3A6M
spannernick said:
I had a hard time getting all the files together so I have made a zip up and it has every file you need,even the firmware V700XXUAMK7,I added that cos on the Samsung Firmware website on slow download it took me 2 hours to download it and it like only 411 mb.
Super SU v2.85 in it there and works fine ,use Impactor_0.9.14,run Impactor.exe and click start and wait for it to finish then connect using Wondershare MobileGo and install the supersu-2-82.apk,Google play on Wondershare MobileGo don't work cos it can't find the device cos Google Play is not on the Gear 1 ,click on supersu app on the Gear 1 and it will ask you to update root files,just click on normal and it will update it and done,you have root on Gear1 now..
Here is the files in a zip.. Hope this helps sommeone,it would of helped me.. its on Mega.. here https://mega.nz/#!sAxinCDa!GR47wt4cQ6g74Ya_9An0bfmf2mel1o8dV0sNiqK3A6M
Click to expand...
Click to collapse
Is not available anymore