Related
I just unrooted my nexus s (9020t) and returned it to stock. It came up with 2.3.1 originally and wanted to update it back to 2.3.3. I found the update drivers and tried to update it, and came up with the status 7 errors. If found the solutions, and tried to go from 2.3.1 to 2.3.2, than install the radio thing to 2.3.3. Up to 2.3.2, it came up with the same error and tried the last resort of updating it to the full 2.3.3 os.
After the update, the nexus s turns on to the google splash screen and hangs up there. I can still access the recovery by holding the volume up and power. I also tried to do factory reset, and wipe data. Nothing seems to help.
Any help?
I'm no expert by any means but you may have to use odin to get it going again. You will probably need to make a jig or buy one to get into download mode.
I hope this helps you and your able to get up and running again.
Sent from my Nexus S using XDA Premium App
I'm totally new into the android community and have no idea what Odin or jig is.
Since the fastboot is working, is there something that I'm missing with resetting orders or something else? I found that some one did a wipe dalvik (I think) with factory reset and cache, but I cannot find the dalvik.
donharden2002 said:
I'm no expert by any means but you may have to use odin to get it going again. You will probably need to make a jig or buy one to get into download mode.
I hope this helps you and your able to get up and running again.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
You dont need a jig to get into download mode
Aslong as the bootloader is unlocked
Power down phone hold volume up/down then plug in USB from computer ....in download mode
Sent from my Nexus S using XDA App
im thinking if you could still access the bootloader then you can still flash clockworkmod. when you get that running, flash any rom u want in clockwork including stock 2.3.3. no odin necessary.
As long as you can still use fastboot there's no need to use Odin or JIG to flash the ROM.
I assume that:
you already have clockworkmod recovery installed and it's working properly.
your phone model is I9020T (SAMOLED)
If those are correct, I'd suggest you to download the 2.3.3 OTA package and flash it via clockworkmod (use the menu "Install zip from sdcard")
After flashing you'll have 2.3.3 on GRI40 running. And if you want to continue updating to 2.3.4, there's a thread dedicated to the topic.
PROBLEM SOLVED! Big appreciation to sonnysekhon who helped me over the phone at 11 in the night!
I was guided to just unlock fastboot, load the cwr and go into usb storage, add the cyanogen mod 7 and voila, problem solved. Now my only problem is, I've got 2.3.3 and want to update it to 2.3.4. Is there any easy way to do this?
Again, I want to thank you guys for the help!
SovereigN7 said:
PROBLEM SOLVED! Big appreciation to sonnysekhon who helped me over the phone at 11 in the night!
I was guided to just unlock fastboot, load the cwr and go into usb storage, add the cyanogen mod 7 and voila, problem solved. Now my only problem is, I've got 2.3.3 and want to update it to 2.3.4. Is there any easy way to do this?
Again, I want to thank you guys for the help!
Click to expand...
Click to collapse
Are you on cm7 or stock?
Sent from my Nexus S using XDA Premium App
I'm on cm7. It shows the cyanogen mod splash screen during bootup and has rom manager, file manager preinstalled.
I'm not really savvy when it comes to android mechanics because I just moved from itouch and iphones to androids couple days ago.
First of all. Congratulations on making the best decision! Iphone sucks. Lol.
Anyway, you can't update to 2.3.4 yet since its only available on stock right now. We're gonna have to wait until devs incorporate it into their custom roms. I believe there is a nightly version of cm7 that is already 2.3.4 but its not as stable as the 2.3.3 yet. hope that helps.
Sent from my Nexus S using XDA Premium App
yea you made the right move switching
Give it time you will get use to messing with Roms ..ect
Well everyone here is the moment we have all been waiting for a little GB love for our SGS4G http://hotfile.com/dl/121009639/fc3e54d/T595VUVKF1.rar.html down load file run through odin Gingerbread Goodness credit to birgertime for the find.
Password For the file is samfirmware.com
This Rom is not Rooted
Currently no way to get back to our own roms right now with that GB rom! I cannot for the life of me restore my backups.
Eric-1987 said:
Currently no way to get back to our own roms right now with that GB rom! I cannot for the life of me restore my backups.
Click to expand...
Click to collapse
Sorry for your woes. Hope u get things worked out. If you do get things worked out wait until one of the devs fixes this issue. I'm sure well see a deodexed version soon, I hope.
Sent from my SGH-T959V using XDA Premium App
I love it, downloading right now. Lets see how our phone files
This is huge. Has anyone rooted this yet? That's the question. Superoneclick doesn't seem to do the trick.
Sent from my SGH-T959V using XDA Premium App
Eric-1987 said:
Currently no way to get back to our own roms right now with that GB rom! I cannot for the life of me restore my backups.
Click to expand...
Click to collapse
pretty sure you need a root before you can do that buddy
Eric-1987 said:
Currently no way to get back to our own roms right now with that GB rom! I cannot for the life of me restore my backups.
Click to expand...
Click to collapse
You can odin a ROM that's gotten rooted so you can use quickreboot or adb to get into recovery mode, then you can use CWM from there if you had it installed already. I just had to flash an old rooted ROM to be able to get to recover my CWM backup.
EDIT:
OP, by the way the password for the file at that link is
samfirmware.com
FBis251 said:
You can odin a ROM that's gotten rooted so you can use quickreboot or adb to get into recovery mode, then you can use CWM from there if you had it installed already. I just had to flash an old rooted ROM to be able to get to recover my CWM backup.
EDIT:
OP, by the way the password for the file at that link is
samfirmware.com
Click to expand...
Click to collapse
Thanks will update original post
Ah man I just got my phone to my liking lol.
I think I'll wait a bit though as this is almost like a KC1 for froyo. Leaked build, so there will probably be a final build avail via OTA and Kies.
nothing better to do might as well flash and play lol worse comes to worse can always odin back and recover with clockwork
super!
flashing rite now. let you guys know how it goes later.
Just curious ....Anyone else not able to get into download mode or stock recovery via ANY METHOD ?
Bl4ckpheniX said:
Just curious ....Anyone else not able to get into download mode or stock recovery via ANY METHOD ?
Click to expand...
Click to collapse
That would be no bueno. Definitely interested to hear if you can get into Download mode, recovery not as much. DL at least you have ODIN.
^^uh oh
10chara
I tried to flash without the bootloader using Heimdall so I can flash back. it finished flashing but wont boot to the OS. so I Odined back to KD1.
try the home button should allow u to flash back via odin
fknfocused said:
^^uh oh
10chara
Click to expand...
Click to collapse
I think on the galaxy s phones they couldn't get into recovery or dl mode unless they flashed the gingerbread boot loader
Sent from my HTC Glacier using XDA Premium App
Just flashed with no problem. Everything seems to work fine. I dont see much changes just some of the menu settings. Phone seems to run smooth. Gonna use it for a bit and let you guys know.
Thanksssssssssssssssss!!!
To going to download mode first you must open ODIN. Assume your phone is off. Then press and hold the volume + and - then plug the USB to your PC. You should see a BIG yellow triangle on the phone said Download mode. Hope this helps.
Keymapping is changed in GB. Not familiar with your phone nut on the original Vibrant GB bootloaders now require one volume key instead of two.
I sent chanfire a 'dump ' of my tab+ a few hours ago and he has already added support for us just now!
https://market.android.com/details?id=eu.chainfire.mobileodin.pro&hl=en
Mobile ODIN - Full firmware flashing straight from the device itself!Mobile ODIN is the on-device firmware flasher of choice. Just throw those firmware files on your (internal or external) SD card, start Mobile ODIN and flash away.!!! Your device must be rooted to be able to use Mobile ODIN. Check the list below to see if your device is supported !!!If you use the EverRoot option, Mobile ODIN will root the firmware while you flash it. Checking out that new leaked firmware? No reason to lose root!
Sent from my GT-P6210 using xda premium
Is this a "safe" method to do Odin install?
Just curious, because installing firmware via an app is not recommended, in my experience. I.e. Installing ROM via ROM manager.
Just tried it. Worked flawlessly.
Sent from my SAMSUNG-SGH-I997 using XDA App
jasonemorrow said:
Just tried it. Worked flawlessly.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Hey. I've been trying to flash ICS (official UK rom) to no avail. I have used Mobile Odin exactly like shown in all videos/guides I have come across but whenever I hit flash everything goes well except that when my GT-P6210 gets restarted it goes into Recovery Mode but that's it. It doesn't install anything. It just stays there.
I am still able to use the tablet like before. Basically, nothing is happening.
Any ideas?
Thanks.
jasonemorrow said:
Just tried it. Worked flawlessly.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
I flashed ICS with mobile Odin. No issues.
Sent from my GT-P6210 using Tapatalk 2
pandasonic said:
Hey. I've been trying to flash ICS (official UK rom) to no avail. I have used Mobile Odin exactly like shown in all videos/guides I have come across but whenever I hit flash everything goes well except that when my GT-P6210 gets restarted it goes into Recovery Mode but that's it. It doesn't install anything. It just stays there.
I am still able to use the tablet like before. Basically, nothing is happening.
Any ideas?
Thanks.
Click to expand...
Click to collapse
One guide I saw said to clear system and I got the same result you are getting. Don't clear system, and flash will go through. You will loose CWM but retain root. This is a fantastic upgrade to the Tab Plus.
pawdog said:
One guide I saw said to clear system and I got the same result you are getting. Don't clear system, and flash will go through. You will loose CWM but retain root. This is a fantastic upgrade to the Tab Plus.
Click to expand...
Click to collapse
Thanks! I moved the tar.md5 file to the internal SD card and it finally worked.
I'm loving the speed and responsiveness of ICS but I'm really disappointed by the aesthetics of it. I really don't like the way the tablet looks anymore. Can't wait to find a working Jelly Bean 4.1.1 ROM without TouchWiz.
anyone know how to flash CWM using mobile odin? can give instruction?
Ok so I've been rooted and unlocked for a while now, but stayed with the stock rom as when I tried out Synergy Nightlies it gave me some errors. So I went to try out CleanRom 2.1, people liked it and I didn't notice any flashing errors. So I flashed it through CWM 6.0.1 and it gave me the yellow exclamation mark saying I had unauthorized data on my phone. So I followed the sticky on how to unbrick my phone using the 2 boot loaders and the root66 stock image. My issue is that when running the root66 stock image through Odin it fails at _XmitData_Read, which seems to be somewhere in system.img.ext4. I've tried rebooting the computer, the phone, Odin, it just doesn't work. So when I reboot my phone after the failure I get Odin auto loading saying:
Odin Mode
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Then an image of a phone, 2 dots, a yellow exclamation, 2 dots and a computer are shown with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Anyone able to help me?
can you still get to odin mode? also if you have kies installed on the computer erase it.
kidhudi said:
can you still get to odin mode? also if you have kies installed on the computer erase it.
Click to expand...
Click to collapse
Kies isn't installed on the computer and yes I am still able to get into Odin Mode.
I'm under the impression that "unauthorized software" message comes from the locked bootloader (if I'm wrong about that someone plese correct me.)
Sounds like you're functional enough to be able to Odin back to stock and go from there - that's what I'd try. See the stickied thread in the Q&A forum.
I would run the FULL VRALF stock image through ODIN to return to stock. That is always the safest way out of a sticky situation.
Thanks guys, according to another post the version of EZ-Unlock I used most likely gave a false report and never actually unlocked my phone. The problem with going back to stock, which if what I'm trying to do, is that it fails.
Could be an USB issue - an intermittent connection would be most likely to cause problems while sending the system partition since that's the biggest. I've had problems using adb from time to time if I plug into one of the front-panel ports on my PC but no trouble with one on the back.
Maybe try switching ports or try a different cable ...
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Strange.... i was able to flash syergy on thefirst try. Never used odin during the whole process....
If youre rooted you need to make sure you have a custom recovery in place like cwm or twrp. Make sure you make a nand-backup.
I used casual to flash unsecure bootloader, with that and recovery in place you should be able to flash roms without any hitches....
I could never find a comprehensive guide on using odin so i never got around to testing it
kintwofan said:
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So far I've tried 3 different USB cables and both a desktop, both front and back ports and a laptop, each one fails on the write of XmitData under system.img.ext4
I had a custom recovery installed and Odin is only being used to get me back to a stock rom, otherwise I did all my flashing under CWM 6.0.1 or twrp. I think the whole fake unlocked bootloader just hard bricked the software.
EDIT: Come to think of it I remember waking up to my phone in download mode. I think Verizon tried to install the update to my phone while I was sleeping. Granted it failed at the end, but I'm wondering if that did something to brick me now.
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yea, I'm currently downloading at the speed of slug the newest update from the forums, will probably just redownload at home, since it's going to take over an hour >.<
EDIT:
Does anyone have a link for an older EZ-Unlocker, that is known to work, so that I don't get this problem yet again.
FIXED!
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
LlirasChosen said:
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
Click to expand...
Click to collapse
I personally suggest not using the app if you already had trouble. Just root your phone using the Debug Root method in Development, download the aboot.img from Adam Outlers thread HERE to your phone, and run the commands at the very bottom in Terminal Emulater app (from the market).
That way you know for sure your bootloader is unlocked. This is what I have done and never had an issue.
Edit: Glad you got your issue resolved!
So after seeing KitKat in action, I hunted down an Android phone eligible for a KitKat ROM. I traded my iPhone for a Verizon Samsung Galaxy S3 (i535) I got it rooted and CWM on it just fine, and the boot loader unlocked. (or so I thought) Went into recovery and did all the steps to install the ROM, got it installed, along with G-Apps and rebooted. My phone came to a screen saying
"system software not authorized by Verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
As far as I can tell, the boot loader was not successfully unlocked. So, it's back to stock ROM via Odin, right? :laugh:
NO! All the guides I find say to download an app to reset the binary counter. How do I do that if I have no OS to boot to?
Any Ideas? Did my enticement for KitKat get the best of me?
You shouldn't need triangle away to Odin back to stock. Triangle away would be for if you were trying to take your phone back to Verizon or Samsung for warranty work and didn't want them to know it was previously rooted.
Sent from my SCH-I535 using xda app-developers app
dustin_b said:
You shouldn't need triangle away to Odin back to stock. Triangle away would be for if you were trying to take your phone back to Verizon or Samsung for warranty work and didn't want them to know it was previously rooted.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
jcaauwe said:
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
Click to expand...
Click to collapse
Follow the instructions in section 5 of this guide: http://forum.xda-developers.com/showthread.php?t=1762709. This will get you back to stock and unrooted. Then you will have to do the root unlock processs again.
Sent from my SCH-I535 using xda app-developers app
dustin_b said:
Follow the instructions in section 5 of this guide: http://forum.xda-developers.com/showthread.php?t=1762709. This will get you back to stock and unrooted. Then you will have to do the root unlock processs again.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
and or use the casual all in one tool and follow root, and flash insecure aboot then download Rom manager from google play and install latest CWM
I just had my s3 replaced under warranty. The new one, I used casual to root/unlock, etc. Worked great! I think I let casual install everything then flashed CM from recovery.
Sent from my SCH-I535 using xda app-developers app
jcaauwe said:
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
Click to expand...
Click to collapse
Not sure what you are trying to achieve, but once you get it back to functional and rooted, I would recommend you try out some of the wonderful custom TouchWIz ROMs on the forum here. They have most of if not more features than are in Kit Kat and there are no fully functional Kit Kat ROMSs for the S3 yet. Plus thse ROMs are stable and all your Samsung features will work properly . MORA, Hyperdrive, Synergy, and Jelly "beans" are good examples of excellent ROMs.
So I figured out what went wrong, and I'm still kicking myself for how stupid of problem it was. The reason Odin didn't want to work was because I was using the front USB ports on my system, which are not USB 2.0... I spent 6 hours trying to figure it out. So I hooked it up to a rear USB port, flashed it back to stock ROM, redid the Root, unlocked bootloader (which I didn't do in the first place) and now I'm getting Cyanogenmod on it.
Thanks everyone for the help! I hope anyone else who comes across this who where in the same boat I was can figure it out.
Sometimes it's a user-error.
Fix
jcaauwe said:
So after seeing KitKat in action, I hunted down an Android phone eligible for a KitKat ROM. I traded my iPhone for a Verizon Samsung Galaxy S3 (i535) I got it rooted and CWM on it just fine, and the boot loader unlocked. (or so I thought) Went into recovery and did all the steps to install the ROM, got it installed, along with G-Apps and rebooted. My phone came to a screen saying
"system software not authorized by Verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
As far as I can tell, the boot loader was not successfully unlocked. So, it's back to stock ROM via Odin, right? :laugh:
NO! All the guides I find say to download an app to reset the binary counter. How do I do that if I have no OS to boot to?
Any Ideas? Did my enticement for KitKat get the best of me?
Click to expand...
Click to collapse
i know you say you are ROOT but why dont you check using ROOT CHECKER download it from the play store its gonna tell you if you are root or not. im using sspencer10 KITKAT 4.4 CM11 and is running pretty smooth why don't you try it out just download the .zip reboot into RECOVERY i preffer you use TWRP (last version) go to whipe>advanced wipe and clear, Dalvik Cache>System>Data>Cache (optional i alwayz check mark Internal storage looking for space and alwayz make a clean flash same as Format Data) make sure you backup everything first using Titatinium Backup go back, then go to Install search for your .zip file on ur SDCard or Internal Storage first select the ROM ADD MORE FILE and add the GAPPS click REBOOT SYSTEM AND ENJOY YOUR NEW KITKAT 4.4 CM11 ON YOUR SGS3.
Don't be scared of Kit Kat! Once u get ur issues figured out and get 4.4 up and running you will see its all worth it!