I have been having issues with my phone not charging and being recognized in my PC. I have tried everything I can think of to fix it without success. At this point I need to send it back to Verizon, but I am currently running AOKP. So I need to revert it back to stock before I can send it.
Since the phone is not being recognized, ADB is not an option. I have tried using Mobile Odin Pro, but with v3.45 and 3.50, I get this error when I try to flash the factory image from Google: "An error occurred extracting the update script"
Any ideas how I can revert back to stock?
There ARE other ways to do it. Read the stickies.
For odin, you need compatible images with ODIN, which is not supported by Google/Samsung (just be reminded of that); the ones we get from Google are to be flashed with fastboot.
Quick tip: i believe you need to relock bootloader with the app before going back to stock completely (since you'll loose root).
Sent from my i9250
I looked at all the stickies, and I can't find anything. Am i just missing it?
this may be a shot in the dark but I had a problem with my usb port not working on my gsm gnex, and thought i needed to send it in to sammy. Then i found a thread where a guy talked about pushing the tip of a razer blade(carefully) in between the tab in the middle of the usb port and the rear of phone. I tried it and since have had no charging problems. As a matter of fact I had forgotten about it until reading this thread.
Or mabye someone with a verizon gnex can upload a stock nandroid for you. As for bootloader unlocked..
3oudreaux said:
this may be a shot in the dark but I had a problem with my usb port not working on my gsm gnex, and thought i needed to send it in to sammy. Then i found a thread where a guy talked about pushing the tip of a razer blade(carefully) in between the tab in the middle of the usb port and the rear of phone. I tried it and since have had no charging problems. As a matter of fact I had forgotten about it until reading this thread.
Or mabye someone with a verizon gnex can upload a stock nandroid for you. As for bootloader unlocked..
Click to expand...
Click to collapse
This could be. Worth a shot, IMO.
zeppelin_one said:
I looked at all the stickies, and I can't find anything. Am i just missing it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1731993
Really, all you need is flashable radio image, flashable bootloader image, stock zip file from Google, and custom recovery (such as Clockworkmod or twrp)
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
kyokeun1234 said:
Really, all you need is flashable radio image, flashable bootloader image, stock zip file from Google, and custom recovery (such as Clockworkmod or twrp)
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
Click to expand...
Click to collapse
Have you read the thread...? Op is trying to return the device, bad usb port.
Sent from my i9250
Restore factory (unroot, stock recovery) without USB connection
I've read through all the threads that I can find on this an other forums regarding this challenge. Basically I have an locked bootloader rooted Galaxy Nexux Toro that has a slightly tweeked rooted JRO03O system and the Jelly Bean bootloader.
I want to restore stock recovery and stock system but the USB port is totally fried. (It actually smoked last time I plugged it in).
I have Odin Mobile Pro downloaded and a tarball for 4.0.4 (VzW-PDA-ODIN-I515EL03_ICL53F_signed.tar) ready to inject using ODIN. However I'm afraid to go ahead with this because I've read that ICS can't handle the Jelly Bean bootloader that is on my phone. As far as I see it I have 4 options:
1. Go ahead and flash the ICS tarball and hope that it works with the JB bootloader but potentially be screwed if it messes up the recovery partition with no way to reflash it as I have no USB.
2. Use the tarball that was in the google release mysid-jro03o-factory-f17426e6.tgz that the toolkit extracted when it unpacked the tgz (it's called mysid-jro03o-factory-f17426e6.tar and the toolkit pulled it from the tgz along with the zip and all the other bits and pieces)
4. Flash the tarball that I created using the GNex toolkit (Wug's) that I made using the img files for system, recovery, kernel and userdata that I pulled out of mysid-jro03o-factory-f17426e6.tgz after allowing the toolkit to unpack the TGZ
4. Try and reflash the ICS bootloader and hope the phone reboots ok into my current ROM and allows me to flash the ICF53F tarball using ODIN.
Any advice on which of these options (or another not listed) stands the best chance of success from those more knowledgeable would be greatly appreciated.
Thanks!
juscoll said:
that ICS can't handle the Jelly Bean bootloader that is on my phone.
Click to expand...
Click to collapse
True, only earlier versions support older bootloaders, not the other way round. Some of it could work, maybe doesnt boot at all (it may be a bit extreme for the device not to, but maybe there's the chance.)
juscoll said:
4. Try and reflash the ICS bootloader and hope the phone reboots ok into my current ROM and allows me to flash the ICF53F tarball using ODIN.
Click to expand...
Click to collapse
Not sure how to flash ICS bootloader on the phone... I assume you're relying on Odin Mobile for this task? Anyways, if you manage to do it, then go ahead and use odin again to restore to factory.
juscoll said:
Any advice on which of these options (or another not listed) stands the best chance of success from those more knowledgeable would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Yes, just return the device. Its got a freaking bad usb port. Even if they can see you modded the rom/updated system etc, and they give you trouble, just ask them to restore the device to its factory state, without USB!! "It's a developers phone people!!!" Personally, i think they will only look at unlocked/locked boot screen.
Sent from my i9250
Related
Here is the stripped version of ICL53F.
FLASH AT YOUR OWN RISK
Changelogs are not fully known yet, but I do know this is Android 4.0.2 and USB host is now working
Stripped meaning no bootloaders, no recovery (so you keep your current CWM), and no wipe (so you keep your data).
IMPORTANT: No wipe is only if your device has been previously OEM unlocked. If your device is NOT OEM unlocked, this WILL wipe your data !
It does include kernel, system and modem, and it's an ODIN tar because ... just because !
YAKJU (GSM): http://www.multiupload.com/7C78MDUQG9
MYSID (LTE): http://www.multiupload.com/3ZZ79I7057
In doubt which one you want ? ADB the following commands:
adb shell getprop ro.product.name
adb shell getprop ro.build.description
adb shell getprop ro.build.fingerprint
The full original Google images can be found here:
http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84
ODIN ?!
The (Windows) software is attached. USE THE ATTACHED VERSION. DO NOT USE AN OLDER VERSION. A lot of you will be familiar with ODIN from other Samsung devices... well, it works exactly the same on this device.
Turn off your device, turn it on again by holding volume-down and power to enter ODIN download mode.
Launch the ODIN software, press the PDA button and select the .tar file you extracted from the .zip file you downloaded.
Make sure in the ODIN program "Re-Partition", "Phone EFS Clear", and "Phone Bootloader Update" are NOT checked.
Connect the Android device with your computer and you should see a yellow box in the ODIN program. Press the "Start" button, wait a minute or so, and your device will be booted with this firmware.
Also see the attached image, which has every box you need to look at circled in red
For both GSM and LTE compatibility ? ?
Nice !
Could you please tell me how to use it with Odin (used to use Odin with SII or Ace but not with Nexus version..)
Thanks for your explanations
imfloflo said:
For both GSM and LTE compatibility ? ?
Click to expand...
Click to collapse
Yeah there are two separate links in OP. One for GSM, and one for LTE.
@zephiK after OP edited #1 i found my answer thanks
@Chainfire can you add the mac OSX step by step too plz.
Thanks for sharing this
Hi Chain fire
First of all its nice to see you on the Nexus section. Don't know what I would have down without your fantastic rooted kernels on the SGS2.
Do you loose root and boot loader is locked again if you flash this 53F?
Sent from my Galaxy Nexus using xda premium
OP update now with Odin & how to answers my request,
Thank you
Hey Chainfire good to see you here!
I heard that the new bootloader might solve the charging issue...can you confirm?
Also really would like to see cf-root kernels...used them alot on my sgs1 and sgs2...always the best kernels for me.
Good to see Odin is back too...its the best thing to use to flash youre phone
Sent from my Galaxy Nexus using xda premium
Any chance that I can flash it on to yakjuux and have no problems?
imfloflo said:
@zephiK after OP edited #1 i found my answer thanks
@Chainfire can you add the mac OSX step by step too plz.
Thanks for sharing this
Click to expand...
Click to collapse
I have no idea what the steps are on Mac OSX.
schrickm5 said:
Hi Chain fire
First of all its nice to see you on the Nexus section. Don't know what I would have down without your fantastic rooted kernels on the SGS2.
Do you loose root and boot loader is locked again if you flash this 53F?
Click to expand...
Click to collapse
You will lose root. If you have CWM recovery installed you can just flash a Superuser package through recovery, as CWM is not overwritten by this flash.
This flash does not include bootloaders, and will not re-lock your bootloaders.
(It even appears ODIN will unlock your bootloader if it was locked)
D_Magic said:
Hey Chainfire good to see you here!
I heard that the new bootloader might solve the charging issue...can you confirm?
Also really would like to see cf-root kernels...used them alot on my sgs1 and sgs2...always the best kernels for me
Click to expand...
Click to collapse
Can't confirm because I don't know. I have only had the charging issue when using custom kernels, the stock kernel had no issue for me.
Not sure if I will release a CF-Root... as this device has a separate recovery partition, there is not that much need for CF-Root... It's still handy though, of course.
Should the bootloaders prove needed and/or helpful, I will release a separate bootloader package so you can flash those later.
AfzalivE said:
Any chance that I can flash it on to yakjuux and have no problems?
Click to expand...
Click to collapse
Nobody knows.
To be fair, I don't even know which model I have. I flashed the Google provided stock image of ITL41F within an hour of getting my Nexus last week, due to soft-bricking it (yeah, that quick).
It may work, it may not.
Chainfire said:
Nobody knows.
To be fair, I don't even know which model I have. I flashed the Google provided stock image of ITL41F within an hour of getting my Nexus last week, due to soft-bricking it (yeah, that quick).
It may work, it may not.
Click to expand...
Click to collapse
Alright then, I'll just flash the provided ICL53F images then...just to switch over to yakju.
Nice to see you here Chainfire. Thanks for this, I will flash it now as I'm looking for a stock ROM, or just stock in its own. I find custom ROM's cause too much battery drain with all the features that are adding.
Chainfire said:
Should the bootloaders prove needed and/or helpful, I will release a separate bootloader package so you can flash those later.
Click to expand...
Click to collapse
Thanks but it turns out the new bootloader doesn't fix the issue
So if i flash this with odin then i keep the unlocked bootloader and cwm but i loose root....what do you mean with flash a superuser package? ( i wanna go back to stock for now cause on every custom rom/kernel i get a really bad battery drain )
Sent from my Galaxy Nexus using xda premium
D_Magic said:
Thanks but it turns out the new bootloader doesn't fix the issue
So if i flash this with odin then i keep the unlocked bootloader and cwm but i loose root....what do you mean with flash a superuser package? ( i wanna go back to stock for now cause on every custom rom/kernel i get a really bad battery drain )
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Maybe the new bootloader fixes the RF interference (debounce time) on the volume buttons (that was only patched in the kernel in the last update)?
I guess someone who lives in a region that had that problem would have to check.
Here are the changes from 4.0.1 --> 4.0.2
Device features
Optimized Mobile Hotspot when used with VPN
Optimized 3G/4G data sessions for faster response times
Fixed an incorrect notification that “data was disconnected due to roaming”
WiFi now automatically reconnects when returning to a known Access Point
Improvements to special visual effects feature when using front-facing camcorder
Visual improvements to the lock screen
Email and Messaging
Fixed an issue where some email attachments would not open correctly
Apps and Widgets
DivX support has been removed and will be supported in a future upgrade
Improved audio volume in Google navigation turn-by-turn directions
Anyone know if I can use this tar file with Heimdall?
madj42 said:
Anyone know if I can use this tar file with Heimdall?
Click to expand...
Click to collapse
Don't know for sure, but I don't see why not ...
Chainfire said:
mysid variant has not been tested by me. Please let me know if the radio flashes properly... if not I'll update the package.
Click to expand...
Click to collapse
Radio flashed flawlessly here
Did anyone of you get the Update ota? On the gsm nexus?
Long time lurker, first (maybe second) time poster.
I'd really like to mess around with my phone's potential, but every time I flash a custom ROM I lose all data connectivity. 2g/voice works fine, but 3G and LTE are out the window.
Here are a few things I've tried AFTER flashing to a customer ROM. I come from years of using HTC phones and software, so I'm definitely fumbling around in the dark here. Please, excuse me if I sound ridiculous.
- I'm on Sprint
- Flashed radio zips in recovery (various ones from reading other threads)
- Used Odin to flash radio files (various ones from reading other threads)
- Repeatedly attempted to update Profile and PRL with error messages saying I couldn't update them and to call customer service
I'm not really sure what else to put up here or to try. I'm hoping the great XDA can help out! Again, I only loose data connectivity after flashing a new ROM. Unlock and root do not effect radios, and I'm able to use the phone just fine on stock software.
Attached is a screenshot of my stock build.
Thanks,
Brandon
I am a little baffled that after 150 views, no one else on this board has shared a similar experience. While its remotely possible, there is just no way I am the only one to have had this issue.
Also... shamless self-bump,.
you are flashing a sprint rom correct?
Zepius said:
you are flashing a sprint rom correct?
Click to expand...
Click to collapse
I'd hope so. I've gotten them all from the Sprint section of the GN forum here on XDA.
i would try flashing the factory images for sprint with fastboot and not odin. this may help more in making sure you have the exact radio/etc you need.
https://developers.google.com/android/nexus/images#mysidspr
Zepius said:
i would try flashing the factory images for sprint with fastboot and not odin. this may help more in making sure you have the exact radio/etc you need.
Click to expand...
Click to collapse
So, here's my order of operations here...
1) flash factory image with fastboot
2) install custom ROM
3) ???
4) Profit?
I mean, if there are other steps, I'm sure I can figure them out. So, I'm assuming that there is typically no need to do anything to the radios after installing a ROM?
after flashing the stock images (all of them, dont leave any out just to be sure) youd need to flash the custom recovery and then you can install the custom rom.
Zepius said:
after flashing the stock images (all of them, dont leave any out just to be sure) youd need to flash the custom recovery and then you can install the custom rom.
Click to expand...
Click to collapse
Sorry, but when you say all of the stock images, what do you mean? What other stock images are there?
And wait, sorry, there's something I didn't mention. I've been using the GN ToolKit for a lot of this. How do I push the stock image you linked me to using fastboot? I'm familiar with using ADB and all that, but I have no idea what to do without a guide. I certainly am not a programmer, just an enthusiast.
Thanks
itsasmallboat said:
Sorry, but when you say all of the stock images, what do you mean? What other stock images are there?
And wait, sorry, there's something I didn't mention. I've been using the GN ToolKit for a lot of this. How do I push the stock image you linked me to using fastboot? I'm familiar with using ADB and all that, but I have no idea what to do without a guide. I certainly am not a programmer, just an enthusiast.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895 - follow the steps similar to the verizon version, except make sure you download the mysidspr image from the google website.
flash every image. bootloader, radios (note there are 2 with the CDMA versions), system, userdata (copy your SD card off before you do this as it will wipe the phone) boot. do not skip anything.
Zepius said:
- follow the steps similar to the verizon version, except make sure you download the mysidspr image from the google website.
flash every image. bootloader, radios (note there are 2 with the CDMA versions), system, userdata (copy your SD card off before you do this as it will wipe the phone) boot. do not skip anything.
Click to expand...
Click to collapse
Alright. Two hours later and after all that... same result. No matter what I do, booting to any custom ROM does not allow me to access 3G/LTE. Should I just give up? lol
Alright, I've been doing some research and apparently I need my phones unique MSL codes to enter in after I flash a new ROM. Any suggestions on how to find my MSL and how to type these codes in after flashing?
Update:
Found a way to get my MSL using a script in terminal w/ root. I can access the data settings menu, but STILL cannot get my MSL for this.
Please help! We've gotten this far!
Hello xda,
I tried rooting my SGH-T999 and it took a while so I unplugged the USB and restarted the phone. Phone keeps saying it has encountered a problem with the current firmware, connect to KIES and select recovery. Kies does not connect to the device. I read on xda to reflash using ODIN. I have ODIN v1.85 from trying to root, is this the right version to use because I also found the ODIN3_v3.07? As far as USB driver, is there separate drivers for ODIN or are people referring to the Samsung Kies drivers (I just installed KIES). I read to do it on this screen and I also read to try to go into the recovery mode (holding vol down, home, power) and then reflashing; which should I do?
Also, I found this link on xda for the T-mobile firmware ( http://forum.xda-developers.com/showthread.php?t=1949687 ). No idea which one to choose, why are there so many, I am currently downloading the latest one
"UVDLJA
PDA: T999UVDLJA
CSC: T999TMBDLJA
Version: 4.1.1 JB
Date: Nov. 14, 2012
Sammobile Link
Samsung-Updates Link"
If I want to use the pre rooted file do I need to fix my problem first and try flashing with stock firmware or can I try to fix the issue directly with the pre rooted firmware?
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Aerowinder said:
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Click to expand...
Click to collapse
I used this guide to root.
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Before I try to flash with mrRobinson's stock rooted rom which I just finished downloading, I will uninstall Kies and install the USB drivers first?
Thanks for your response Aerowinder.
I got USB drivers earlier today that was a newer version but I will be using the files from your sig since it works :good:
Another question I had was, does the phone need to be in download mode or can I do it in the screen where it says "encountered problem with current firmware. Connect to KIES and select recovery" screen when I flash with Odin? I know normally I would have to be in the download mode but I'm wondering if it is the same when I am getting this error.
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Aerowinder said:
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Click to expand...
Click to collapse
Awesome thanks!
So I am watching the root video on your sig, so in my case I would choose the rom I want for the PDA instead of the cwm-touch-6.0.2.3-d2tmo right? Should I extract the rooted firmware or just load the zipped file onto ODIN PDA?
Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Aerowinder said:
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Click to expand...
Click to collapse
Okay I don't care about the counter, I just want my phone to work and I'll be happy.
But now I'm getting a little confused about the cwm recovery.
So just to be clear, you are saying I need to flash a recovery (cwm-touch-6.0.2.3-d2tmo in my case since I don't care about the counter), BUT do I flash the recovery before or after I flash with Root66 firmware? That part I am confused about. And do I flash one right after another or do I need to restart my phone or ODIN first?
Thank you so much for helping me out. I was freaking out this morning and I am very grateful for your help and knowledge. I hope I am not being too much of a pain or hassle with these questions. Sorry that I am quite new to this
Woody said:
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Click to expand...
Click to collapse
Woody, I went to the link you posted. What are the 4 files for?
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
buzzking00 said:
Woody, I went to the link you posted. What are the 4 files for?
Click to expand...
Click to collapse
Top one is TWRP version 2.3.0.0
Second is 6.0.1.2 CWR touch version
Third is TWRP version 2.3.1.0
Fourth is Stock recovery.
Do not flash all of them. Are you a TWRP or CWR kind of person? Instead of re-typing it out, go here and I come in on post #20 on the 2nd page. Read that to the end and let us know if you understand it. Pretty easy to follow but I understand your Panic Mode, so take your time.
Aerowinder said:
If still having problems, only thing left to do is flash a full stock image, link also in my signature.
Click to expand...
Click to collapse
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
Awesome. Thanks Aerowinder!
I will try this when I get home (assuming I can go into download mode...) and post what happened
Woody said:
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Click to expand...
Click to collapse
I will take a look at the link Woody.
I am really hoping this will work on the first try!
Okay so from reading your post Woody I can use EITHER the TWRP and CWR, but I want to use the one that is easiest to use. Which one do you guys think is easier to use?
Also, SU3.3 or SU1.04 which one should I use? Aerowinder, your sig shows both now but earlier I didn't notice the SU1.04. I just realized I only need the SU file IF the prerooted file doesn't work but just in case it doesn't I guess it is better to know.
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Aerowinder said:
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Click to expand...
Click to collapse
I am going to try it in an hour.
Wish me luck!
1. Download mode
2. Flash CWM
3. Flash Root66
4. Hopefully no problems
:good:
Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
OMFG OMFG OMFG
OMFG OMFG OMFG
OOOOOOH MYYYYYY FOOOOOOOOKIN GOOOOOOOOOOOOSH
AEROWINDER AND WOODY
I LOVE YOU SO MUCH
IT WORKED AND NOTHING GOT ERASED. I THOUGHT PUTTING THE NEW FIRMWARE WOULD'VE ERASED EVERYTHING WITH THE NEW ROM BUT NOPE.
Uninstalled KIES and USB drivers.
Installed USB drivers from Aerowinders sig
So the Odin 3.07 didn't work either so I ended up using ODIN 1.85
Turned off auto reboot and left f reset on (no idea what f reset does lol)
Flashed CWM
Flashed root66 rom
Restarted phone and it was back to normal with all the data saved, but no SU (wasn't unlocked)
So reflashed CWM
Then restarted in clockwork recovery and ran super user and now the phone is rooted
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
:good::good::good: 3 thumbs up to the knowledge members above Aerowinder and Woody!
THANK YOU!
Panic mode TRANSFORMMMMM! *Panic mode has now transformed into excitement mode*
buzzking00 said:
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
Click to expand...
Click to collapse
So, ahh, are you excited? Haha. Great. Glad you got it up and running.
I hope that you do learn more about Android and share it with someone who needs help someday. When I first came, that is what someone did for me and I have tried to do it ever since. We are all still learning, including Aero and myself, so there will never be an end but rather more.
Good job and now you should make a Nandroid backup just in case you ever get in a bind again.
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
buzzking00 said:
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
Click to expand...
Click to collapse
That's the attitude, with Android you have to be a sponge and try to learn as much as you can. A single Google search will give you the answers you seek and making a backup is pretty much universal no matter what Rom, phone you have. Good luck
Sent from my SGH-T999 using xda app-developers app
Alright, so I'm trying to reflash the stock kernel for my stock, rooted, Sprint 4.2.1 Galaxy Nexus(the GA02 kernel). I managed to get the .tar file from Samsung's site but ODIN keeps on closing on my PC when it gets to 'file analysis'. I have my phone connected, and everything is recognized and ready to go, but the program keeps freezing at that point. So, does anyone have a link for a flashable zip for the kernel? Or can anyone tell me what I'm doing wrong with ODIN? Thanks in advance.
Here you are: http://forum.xda-developers.com/showthread.php?t=1992483&highlight=stock+kernel
noname580 said:
Here you are: http://forum.xda-developers.com/showthread.php?t=1992483&highlight=stock+kernel
Click to expand...
Click to collapse
I tried this kernel and it drains my battery so badly it won't charge.
Ramocity said:
I tried this kernel and it drains my battery so badly it won't charge.
Click to expand...
Click to collapse
I just so happened to be looking for a stock kernel as I was going to start playing around with them. I haven't yet tested it. Thanks for the heads up. The only thing left to do is wipe and backup for stock kernel.
Why don't you extract boot.img from the corresponding factory image (available here https://developers.google.com/android/nexus/images#mysidspr; variant 'toroplus'), and flash that through fastboot? I don't understand why some make no effort to use the tools GOOGLE gave us. For most purposes, you're the proud owner of a Nexus device.
a maguro wrote this.
Good Evening all,
I have a T-mobile Galaxy S3 that was rooted. That I took back to stock and unrooted using Odin and T999UVALEM_T999TMBALEM_T999UVALEM_HOME.tar......I let the phone sit for about 25-30 min and it never really made it past the pulsing SAMSUNG screen. Now I rebooted into Flashing Mode (Odin) and Flashed CF-Auto-Root-d2tmo-d2tmo-sght999.tar, thinking that would help.......however.....I still seem to be stuck.....How do I get myself unstuck? Thanks so much for any help .....
Mic
Have you tried using stock recovery and perform a factory reset? I also took mine back to stock via Odin, performed the factory reset and worked fine
Sent from my SGH-T999 using Tapatalk
Hellfireworks said:
Have you tried using stock recovery and perform a factory reset? I also took mine back to stock via Odin, performed the factory reset and worked fine
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I did do that.....and was able to update to 4.3 through t-mobile, however, now I have a black block which appears over all screens giving or listing what seems to be the information about my phone, and a warning that the phone is in "Factory Mode" and I need to reset it back to user.....or something like that...it comes and goes kinda fast....I wanted to flash a different ROM but I went back to stock to kinda clean up my internal SD....it was getting kinda bulked down with all the roms I was trying.........but now I am stuck with this......any ideas??
jinx0117 said:
I did do that.....and was able to update to 4.3 through t-mobile, however, now I have a black block which appears over all screens giving or listing what seems to be the information about my phone, and a warning that the phone is in "Factory Mode" and I need to reset it back to user.....or something like that...it comes and goes kinda fast....I wanted to flash a different ROM but I went back to stock to kinda clean up my internal SD....it was getting kinda bulked down with all the roms I was trying.........but now I am stuck with this......any ideas??
Click to expand...
Click to collapse
Did you update to 4.3 while you were in stock? If you did that, maybe Knox is causing you these issues, if you havent been in 4.3 in stock, you shouldn't have that issue.
I would suggest flashing 4.1.2 version via odin, after that enter recovery and do a factory reset, after that reboot and it should start properly
Sent from my SGH-T999 using Tapatalk
Hellfireworks said:
Did you update to 4.3 while you were in stock? If you did that, maybe Knox is causing you these issues, if you havent been in 4.3 in stock, you shouldn't have that issue.
I would suggest flashing 4.1.2 version via odin, after that enter recovery and do a factory reset, after that reboot and it should start properly
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I originally went to Stock 4.1.2....then got tried to root the phone thinking that flashing different Rom would fix the issue.....no dice...So I flashed back to the 4.1.2 Stock. Made my way around the block that pops up telling me I need to set it back to user mode and did the OTA update. After the update it was still saying that I was in Factory Mode....and needed to reset it to User Mode.....In did a hard reset and wipe....and it is still there.....I may be able to change it through root explorer but I need to root my phone again.....and I have no idea where a safe place to start would be for that....
@jinx0117
Sounds like your EFS folder might have been erased. You can root the phone and check with a file explore. If you don't have a backup of it, there is no way to recover it.
If you have updated to official 4.3 don't try to downgrade with odin or you will end up with a full brick.
sswb27 said:
@jinx0117
Sounds like your EFS folder might have been erased. You can root the phone and check with a file explore. If you don't have a backup of it, there is no way to recover it.
If you have updated to official 4.3 don't try to downgrade with odin or you will end up with a full brick.
Click to expand...
Click to collapse
Thank you so much for telling me that.....I was able to root and reset my phones Factory Mode by use of a Emulator. Now I did follow some steps I found here on XDA to get around the Knox Security that T mobile put on the 4.3 update......I am able to flash Roms now with no issues.....thanks so much everyone for all your help!!!!
I will assume that if I want to take it back to stock again I would need to flash a 4.3 stock with Odin???? That way I don't brick my phone? Is that correct?:good:
jinx0117 said:
Thank you so much for telling me that.....I was able to root and reset my phones Factory Mode by use of a Emulator. Now I did follow some steps I found here on XDA to get around the Knox Security that T mobile put on the 4.3 update......I am able to flash Roms now with no issues.....thanks so much everyone for all your help!!!!
I will assume that if I want to take it back to stock again I would need to flash a 4.3 stock with Odin???? That way I don't brick my phone? Is that correct?:good:
Click to expand...
Click to collapse
Yea, Stick with 4.3 odin for now on. The 4.3 Bootloader wont let you downgrade.
sswb27 said:
Yea, Stick with 4.3 odin for now on. The 4.3 Bootloader wont let you downgrade.
Click to expand...
Click to collapse
Thank you so much for that....I have tried to flash a few custom roms but I see there are some issues with certain parts of the phone if they are not 4.3 and above. Do you know of a good ROM that would work on my phone that has alot of customizing.....I'm a chick....so....In like to theme.....lol
I can't use anything from Team Dirt.....my phone won't load it....I have Dandroid on there now....but that is pretty much stock.....Tried StockRom custom.....but it never loaded the Aroma installer......it just sat there saying it was loading it...... Thanks again for all the help. :laugh:
jinx0117 said:
Thank you so much for that....I have tried to flash a few custom roms but I see there are some issues with certain parts of the phone if they are not 4.3 and above. Do you know of a good ROM that would work on my phone that has alot of customizing.....I'm a chick....so....In like to theme.....lol
I can't use anything from Team Dirt.....my phone won't load it....I have Dandroid on there now....but that is pretty much stock.....Tried StockRom custom.....but it never loaded the Aroma installer......it just sat there saying it was loading it...... Thanks again for all the help. :laugh:
Click to expand...
Click to collapse
Aroma is buggy, you just have to keep rebooting into recovery and keep trying, it will go. Some say it seems to work better without the usb plugged in.
As for team dirt I believe it is a aosp rom. If it is you will have to edit the updater script in the zip file so it know's your new 4.3 bootloader. META-INF>com>google>android>updater-script. If your on windows I suggest downloading notepad++ to edit the file. Just delete every thing down to where it
say's mount then save the file.
Update: I edited the updater for you https://www.dropbox.com/s/xucl47rh1wxg9rt/updater-script
Just put it in the zip file where I told you above, save and copy it to the zip and flash away.
sswb27 said:
Aroma is buggy, you just have to keep rebooting into recovery and keep trying, it will go. Some say it seems to work better without the usb plugged in.
As for team dirt I believe it is a aosp rom. If it is you will have to edit the updater script in the zip file so it know's your new 4.3 bootloader. META-INF>com>google>android>updater-script. If your on windows I suggest downloading notepad++ to edit the file. Just delete every thing down to where it
say's mount then save the file.
Update: I edited the updater for you https://www.dropbox.com/s/xucl47rh1wxg9rt/updater-script
Just put it in the zip file where I told you above, save and copy it to the zip and flash away.
Click to expand...
Click to collapse
Wow!!!! Thank you sooooo much....I admit I don't know it all just enough to be dangerous....but I am always willing to learn.....thank you so much for doing that for me....that was really awesome of you......
jinx0117 said:
Wow!!!! Thank you sooooo much....I admit I don't know it all just enough to be dangerous....but I am always willing to learn.....thank you so much for doing that for me....that was really awesome of you......
Click to expand...
Click to collapse
Well, this is the place to learn. We are all here to help each other, that's why i love android.:highfive:
Just use that thanks button to people that help you is all we ask in return.