Related
Hi,
I have been rooting for a while with my evo 4g which is basically just recoveries & zip files.
Currently I have updated to Calk's ICS Beta 3 rom with modem FC05. I have read some stuff here & there that talk about having issues going from a ICS rom back to a GB nandroid.
I have installed Kies opened Odin, looked at the Wiki here:
http://forum.xda-developers.com/showthread.php?t=1274337
I just dont quite get in terms of flashing zips through odin. I keep reading people say to odin back to stock & then flash from there.
How do I do that? I looked at QB777's video on youtube, but it seems like PIT files arent used much at this point.
Any advice would be great.
Thanks,
Rich
Ok, basically when you Odin back to stock, it involves flashing a .tar ROM from the pda slot in desktop Odin and not zip file like you would in CWM. Once you restore back to stock, you can find a .tar recovery, I personally use rogue which will allow you to have cwm-based recovery for flashing zips. All the links should be in development. Let me know if you still need help
Edit-what Odin does is it allows you to flash Roms, kernels, moderns, etc even if you don't have a custom recovery, provided that they are in the correct format, like .tar extension
Sent from my SPH-D710 using xda premium
so when i flash a tar, I go into download mode, open odin, point it to a stock rooted tar file that has CWR & I am back to stock ready to flash to something else?
Can you help me find those files? A stock rooted, CWR should do the trick.
RichTJ99 said:
so when i flash a tar, I go into download mode, open odin, point it to a stock rooted tar file that has CWR & I am back to stock ready to flash to something else?
Can you help me find those files? A stock rooted, CWR should do the trick.
Click to expand...
Click to collapse
Ok, so you go into a download mode on your phone, open Odin, plug in your USB cord, ODIN should recognize your phone provided you installed the right drivers. You're good if you get the yellow box that says 0 com, something something. The only box that should be checked is Auto Reboot in Odin.
The easiest way that I've been going back and forth between GB and ICS is to install the rooted EL29 .tar version here
http://little-melon.com/sfhub/SPH-D710.EL29_CL852097_ROOTED-sfx.exe
You would need to extract the file until you get a folder with tar.md5 name. Example of the file I provided would be SPH-D710.EL29_CL852097_ROOTED_PDA.tar.md5 once you unzip it. This is the file you would put on the PDA slot of your desktop Odin.
Once you do this, Odin will start flashing and be done in like 1-2 minutes and auto reboot. Do not do anything to shut down, unplug, or mess with the device while Odin is flashing or you may end up bricking it. Once your phone reboots you will be rooted and stock based with EL 29 modem and kernel, which is the latest official Sprint OTA. If you want to get a recovery after this,you would need to go back into Odin and flash a kernel that has a recovery baked in. Like I said I use Rogue and the link would be here for Rogue Stock EL29-
http://goo-inside.me/kernels/TeamRo.../rogue_ET-recoveryonly-1.1.4-rc0-odin.tar.md5
Flashing this in Odin you will get CWM-based recovery and can start backing up, flashing different ROMS.
Hope this helps.
This is very helpful. I am stuck at the SGS2 boot screen after flashing MIJJs Goodness 1.8, can't boot in to recovery, only download mode. How do I fix this?
thefoss said:
This is very helpful. I am stuck at the SGS2 boot screen after flashing MIJJs Goodness 1.8, can't boot in to recovery, only download mode. How do I fix this?
Click to expand...
Click to collapse
Flash a recovery in download mode that I linked. It's rogue recovery
Sent from my SPH-D710 using xda premium
Just to confirm, using the files you had here, I open odin in download mode, choose PDA (check the check box) point it to the tar.md5 file, hit start & wait a few minutes until it auto reboots?
How do I flash the recovery? Is it also the PDA?
I have been flashing modems in CWR, not odin & I just want to make sure that recovery or rom itself, just PDA & nothing else checked (but PDA)?
stargaterules said:
Ok, so you go into a download mode on your phone, open Odin, plug in your USB cord, ODIN should recognize your phone provided you installed the right drivers. You're good if you get the yellow box that says 0 com, something something. The only box that should be checked is Auto Reboot in Odin.
The easiest way that I've been going back and forth between GB and ICS is to install the rooted EL29 .tar version here
http://little-melon.com/sfhub/SPH-D710.EL29_CL852097_ROOTED-sfx.exe
You would need to extract the file until you get a folder with tar.md5 name. Example of the file I provided would be SPH-D710.EL29_CL852097_ROOTED_PDA.tar.md5 once you unzip it. This is the file you would put on the PDA slot of your desktop Odin.
Once you do this, Odin will start flashing and be done in like 1-2 minutes and auto reboot. Do not do anything to shut down, unplug, or mess with the device while Odin is flashing or you may end up bricking it. Once your phone reboots you will be rooted and stock based with EL 29 modem and kernel, which is the latest official Sprint OTA. If you want to get a recovery after this,you would need to go back into Odin and flash a kernel that has a recovery baked in. Like I said I use Rogue and the link would be here for Rogue Stock EL29-
http://goo-inside.me/kernels/TeamRo.../rogue_ET-recoveryonly-1.1.4-rc0-odin.tar.md5
Flashing this in Odin you will get CWM-based recovery and can start backing up, flashing different ROMS.
Hope this helps.
Click to expand...
Click to collapse
Reverting back to GB ROM
I recently switched back from ICS to GB and did not have any problems with the change back. I simply went into my SD card manually took everything off except my chaulkins format all and my wifi tether hack. I then went into recovery mode and did a wipe all. Then went to zip files, ran the format all, then did an install of the new ROM and it works great!
I'm just making sure I'm doing this right. I have starburst ROM and android 2.3.4 with the EK02 modem.
I'm trying to flash CM9 from this thread. However, it asks to flash to StockCWM EL26. Can anyone give a step by step direction for flashing this through Odin, cuz I'm a pretty big newb. I tried flashing it earlier but then when I checked my phone the version still says 2.3.4 and baseband version is still S710.10 S.EK02 not EL26.
After that are the steps similar for flashing CM9 and gapps?
Thanks for the help!
PS. I'm a huge nub. I don't know anything...
Open ODIN, then load the CWM EL26 tar file under the !!!PDA!!! slot. Set your phone to ODIN download mode by first shutting it off, then holding the volume down button together with the power button. Once in ODIN download mode, connect your phone to the PC, and start the flash process. After the flash gives a green PASS, disconnect the phone. It will probably be off at this point, so hold the volume UP button together with power to boot into ClockworkMod. Follow the menus to install the CM9 zip. Once it installs, wipe cache and reboot. Enjoy CM9.
Be forewarned that this increments your odin count, and will give the yellow triangle on the load-screen. This can be reversed by using Triangle-Away 1.25 (search the forums for the apk). I was just told in another thread I started that you can also try using mobile ODIN to flash the CWM-EL26 tar, which will not cause the above annoyances.
EDIT: So I just used mobile ODIN, and it worked like a charm! Use mobile ODIN instead, to flash EL26-CWM.
So I came from ICS FC07, and was trying to update my rom to FC15, went into recovery, wiped all, flashed the rom, then the moden, and now I am stuck at the Galaxy S II screen.... I backed everything up in CMW before flashing though so how can I restore it? When I got into recovery ( stock ) I see all my back ups
Is DL mode available? Then only solution would be installing the recovery kernel thru odin.
At this time, EL29 is known as safe to use. So, download the tar file from
http://forum.xda-developers.com/showthread.php?t=1540158
Rogue Stock EL29 (Odin Tar)
-Open Odin and make sure only auto reboot is selected in the option list
-Click PDA and select the Rogue tar, then select start
Odin the tar file (be sure put the file to the right place) and during the reboot, press vol up + power. If the recovery mode comes, then restart the whole process again but don't do the modem again at the same session. If modem cause the problem, then try odin the modem after the reboot.
*important* Be sure that you use the usb cable that had no issues before. Bad usb cable is causing your odin process stopped and your phone bricked....
If you had FC07 with CWM repack did you try any wipe operations before flashing by ODIN OC?
If you should have problems flashing by ODIN after similar cases - in particular, data.img - please mention so as it *may* indicate a brick. But being optimistic and hoping that isn't the case here...
garwynn said:
If you had FC07 with CWM repack did you try any wipe operations before flashing by ODIN OC?
If you should have problems flashing by ODIN after similar cases - in particular, data.img - please mention so as it *may* indicate a brick. But being optimistic and hoping that isn't the case here...
Click to expand...
Click to collapse
no its not bricked, i went ahead and restored it with the post above. thanks though.
Jess813 said:
no its not bricked, i went ahead and restored it with the post above. thanks though.
Click to expand...
Click to collapse
A happy ending We need more of those around here!
kobridge said:
Is DL mode available? Then only solution would be installing the recovery kernel thru odin.
At this time, EL29 is known as safe to use. So, download the tar file from
http://forum.xda-developers.com/showthread.php?t=1540158
Rogue Stock EL29 (Odin Tar)
-Open Odin and make sure only auto reboot is selected in the option list
-Click PDA and select the Rogue tar, then select start
Odin the tar file (be sure put the file to the right place) and during the reboot, press vol up + power. If the recovery mode comes, then restart the whole process again but don't do the modem again at the same session. If modem cause the problem, then try odin the modem after the reboot.
*important* Be sure that you use the usb cable that had no issues before. Bad usb cable is causing your odin process stopped and your phone bricked....
Click to expand...
Click to collapse
Thats what I keep doing and odin works all the way through but then it gets stuck at the boot screen after odin does its thing. I can still boot into team recovery and downloading mode.
armandosal said:
Thats what I keep doing and odin works all the way through but then it gets stuck at the boot screen after odin does its thing. I can still boot into team recovery and downloading mode.
Click to expand...
Click to collapse
seems like we have to choose the long-ride path.
From the same download page, there are separate rom(+root)/kernel/modems files are available. Starting from the first (format all), can you try odin one by one? (reboot after each installation)
The sequence would be -
1. from the recovery, wipe everything, execute Calk's format all
2. odin Rom
3. reboot and check if system starts
4. odin kernel (repacked recovery)
5. reboot
6. odin modem
7. reboot.
8. go settings > about phone > system update > update profile & PRL
Check this out - http://forum.xda-developers.com/showthread.php?t=1557317
Well here is what I did, went into download mode, and installed the EG30 Tar, and everything is up and running. My only problem is that now I have EG30 with FC15 modem LoL, although I am considering leaving it as is because my phone seems to be working super fast, if I wanted to change the modem I would need to do this through Odin correct?
Jess813 said:
Well here is what I did, went into download mode, and installed the EG30 Tar, and everything is up and running. My only problem is that now I have EG30 with FC15 modem LoL, although I am considering leaving it as is because my phone seems to be working super fast, if I wanted to change the modem I would need to do this through Odin correct?
Click to expand...
Click to collapse
because you've already figured out lots of things already, why don't you move to FC18 rom. There would be lots of benefits on it.
Currently Calk's tweaked FC18 rom is available along with Rogue FC18 recovery kernel.
kobridge said:
because you've already figured out lots of things already, why don't you move to FC18 rom. There would be lots of benefits on it.
Currently Calk's tweaked FC18 rom is available along with Rogue FC18 recovery kernel.
Click to expand...
Click to collapse
Not to go out of subject but I decided to go back to stock due to all the little bugs with the new ICS leaks, ex: notification sound, GPS, Camera takes a looong time to boot up ( sometimes) so I said "eh Im going back to stock "
Has these things been worked out in FC18?
I did not notice any issues on FC18. It seems like lots of people are now satisfied with this rom. Again, up to you.
First, never use GooManager to flash TWRP, to soft brick your phone is very likely, if soft bricked your phone, you need to use odin to flash TWRP.
Second, don't use TWRP 2.6.3.0 on our T989/T989D, I have found the following problems:
1: in recovery mode - after advanced wipe is done, the "return" button (right bottom corner) it's not sensitive, you need to press a few times to get back to previous screen
2: after flash new ROM, it usually takes at least 30 seconds to reboot the device, you may think your device is powered off, but it is not, just take too long.
3: No usb mount button in mount screen, not sure why, so you cannot mount your phone in recovery mode, you have to use adb to push file.
4: after you flash the ROM successfully, the newly flashed ROM may enter "bootloop" mode, it happened to me many times, same ROM, I have to flash at least 4-5 times to by pass the bootloop.
5: if you are lucky, and your newly flashed ROM booted, you may experience various problems, e.g. reboot, hangs, lag.... etc. Happened to me.
So, you better stick with TWRP 2.6.1.0, however 2.6.1.0 is prefect, it cannot wipe /preload, but at least, it doesn't have the above problems.
brisk5181 said:
First, never use GooManager to flash TWRP, to soft brick your phone is very likely, if soft bricked your phone, you need to use odin to flash TWRP.
Second, don't use TWRP 2.6.3.0 on our T989/T989D, I have found the following problems:
1: in recovery mode - after advanced wipe is done, the "return" button (right bottom corner) it's not sensitive, you need to press a few times to get back to previous screen
2: after flash new ROM, it usually takes at least 30 seconds to reboot the device, you may think your device is powered off, but it is not, just take too long.
3: No usb mount button in mount screen, not sure why, so you cannot mount your phone in recovery mode, you have to use adb to push file.
4: after you flash the ROM successfully, the newly flashed ROM may enter "bootloop" mode, it happened to me many times, same ROM, I have to flash at least 4-5 times to by pass the bootloop.
5: if you are lucky, and your newly flashed ROM booted, you may experience various problems, e.g. reboot, hangs, lag.... etc. Happened to me.
So, you better stick with TWRP 2.6.1.0, however 2.6.1.0 is prefect, it cannot wipe /preload, but at least, it doesn't have the above problems.
Click to expand...
Click to collapse
You can wipe preload in 2.6.1.0 by going to settings and ticking use rm -rf instead of formatting.
The no USB mount is the worst problem for me. I wonder if @Dees_Troy can shed some light on that.
I wonder if there are such issues then why there are more than 1800 hits on 2.6.3? And also if it has issue then why TWRP released it without properly checking it? Im oberserving TWRP is doing this from a long time and infact i have to search on internet to check if latest version is perfect or not
brisk5181 said:
First, never use GooManager to flash TWRP, to soft brick your phone is very likely, if soft bricked your phone, you need to use odin to flash TWRP.
Second, don't use TWRP 2.6.3.0 on our T989/T989D, I have found the following problems:
1: in recovery mode - after advanced wipe is done, the "return" button (right bottom corner) it's not sensitive, you need to press a few times to get back to previous screen
2: after flash new ROM, it usually takes at least 30 seconds to reboot the device, you may think your device is powered off, but it is not, just take too long.
3: No usb mount button in mount screen, not sure why, so you cannot mount your phone in recovery mode, you have to use adb to push file.
4: after you flash the ROM successfully, the newly flashed ROM may enter "bootloop" mode, it happened to me many times, same ROM, I have to flash at least 4-5 times to by pass the bootloop.
5: if you are lucky, and your newly flashed ROM booted, you may experience various problems, e.g. reboot, hangs, lag.... etc. Happened to me.
So, you better stick with TWRP 2.6.1.0, however 2.6.1.0 is prefect, it cannot wipe /preload, but at least, it doesn't have the above problems.
Click to expand...
Click to collapse
When you re-flashed several times for the new ROM, did you do a wipe everytime? or did you just re install??
HQuser said:
I wonder if there are such issues then why there are more than 1800 hits on 2.6.3? And also if it has issue then why TWRP released it without properly checking it? Im oberserving TWRP is doing this from a long time and infact i have to search on internet to check if latest version is perfect or not
Click to expand...
Click to collapse
There's plenty of documented issues with it....maybe for some devices its fine, but not all devices seem to be created equal.
Why is twrp doing nothing about it....probably because our aging device is under their radar, or they just aren't concerned with a few people with issues. Again....it may be flawless on every other device, so they aren't concerned with our old phone.
That's my guess.
Battery problems? No matter the rom or android version.... >>>> http://forum.xda-developers.com/showthread.php?t=2461864
I have had these same problems, but thy only started when I flashed 4.3. That is slim bean and paranoid android. It will boot after the flash, bit any attempt to reboot after that is met with a boot loop.
Thing is, I don't remember which version of TWRP I am using, and I would like to avoid rebooting since I don't want to reflash just yet. Is there a way to check on the version without a reboot? I know a reflash is inevitable if I want to install another version of TWRP.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Johndoe9990 said:
I have had these same problems, but thy only started when I flashed 4.3. That is slim bean and paranoid android. It will boot after the flash, bit any attempt to reboot after that is met with a boot loop.
Thing is, I don't remember which version of TWRP I am using, and I would like to avoid rebooting since I don't want to reflash just yet. Is there a way to check on the version without a reboot? I know a reflash is inevitable if I want to install another version of TWRP.
Click to expand...
Click to collapse
I can confirm that TWRP 2.6.1.0 causes no bootloop after flashing a ROM.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Where do I find a ODIN flashable file of the 2.6.1.0? I'm new to the Samsung side of things. I have looked all over and all I find at Goo and TWRP sites as .img and .tar files. I know .img files have to use dd to use now is the .tar files can be used with Odin? If so please let me know don't want to brick my new / used S2.
michaelcrossland said:
Where do I find a ODIN flashable file of the 2.6.1.0? I'm new to the Samsung side of things. I have looked all over and all I find at Goo and TWRP sites as .img and .tar files. I know .img files have to use dd to use now is the .tar files can be used with Odin? If so please let me know don't want to brick my new / used S2.
Click to expand...
Click to collapse
Yes, the tar files are for Odin.
So I flashed cm 10.2 on my Galaxy S3 AT&T, and forgot to flash the right gapps, so I did that, except I forgot to do a factory reset when I flashed them. When I went to reboot, my phone would not turn on, nor get into recovery mode. It keeps showing the Samsung logo with the little CyanogenMod figure underneath it, and keeps vibrating repeatedly while trying to turn on. This is not a boot loop (I think) because my phone doesnt even get as far as the arrow animation that keeps going in circles. All I can do is access download mode. Can anyone help me? I have tried taking the battery out multple times and waiting for the battery to charge and then trying to turn it on, to no success.
rohanr014 said:
So I flashed cm 10.2 on my Galaxy S3 AT&T, and forgot to flash the right gapps, so I did that, except I forgot to do a factory reset when I flashed them. When I went to reboot, my phone would not turn on, nor get into recovery mode. It keeps showing the Samsung logo with the little CyanogenMod figure underneath it, and keeps vibrating repeatedly while trying to turn on. This is not a boot loop (I think) because my phone doesnt even get as far as the arrow animation that keeps going in circles. All I can do is access download mode. Can anyone help me? I have tried taking the battery out multple times and waiting for the battery to charge and then trying to turn it on, to no success.
Click to expand...
Click to collapse
If you can get to download mode, try flashing a stock file via Odin to reset your phone to working conditions. Thereafter, you can go back to a custom ROM. Would you recall what firmware version you were on prior to flashing CM? If it was anything older than 4.3 (e.g. 4.1.2, 4.1.1), you can Odin back to 4.1.1. If you already had 4.3, you would need to Odin back to 4.3 following the instructions posted in the thread below ..
http://forum.xda-developers.com/showthread.php?t=2722660&page=3. Scroll through carefully for the file you need for 4.3. Otherwise, you can find the Odin flash-able 4.1.1 stock file on sammobile.com
Larry2999 said:
If you can get to download mode, try flashing a stock file via Odin to reset your phone to working conditions. Thereafter, you can go back to a custom ROM. Would you recall what firmware version you were on prior to flashing CM? If it was anything older than 4.3 (e.g. 4.1.2, 4.1.1), you can Odin back to 4.1.1. If you already had 4.3, you would need to Odin back to 4.3 following the instructions posted in the thread below ..
http://forum.xda-developers.com/showthread.php?t=2722660&page=3. Scroll through carefully for the file you need for 4.3. Otherwise, you can find the Odin flash-able 4.1.1 stock file on sammobile.com
Click to expand...
Click to collapse
I have looked at the thread but I am new to all this stuff, how do I flash using Odin?
rohanr014 said:
I have looked at the thread but I am new to all this stuff, how do I flash using Odin?
Click to expand...
Click to collapse
First you will need to download and extract the Odin tool. Odin is Samsung's tool for flashing (installing) firmware. You can download Odin v3.07 via the link below ...
http://www.mediafire.com/download/772dlmuaxfgm0x2/Odin307.zip
Once you have downloaded it, extract the files and look for the executable file (*.exe). That's the one you will need to run to open Odin.
We also need to identify the appropriate firmware to flash. You did not answer the earlier question on what Android version your device was on prior to flashing the custom firmware. This is important to let us know which official version you can safely revert to (4.1.1 or 4.3). If you were an older version than 4.3, you should flash 4.1.1 but if you were already on 4.3, then you should stick to this. Either way, you can download the 4.1.1 file via this link .. http://rapidgator.net/file/681a28a5...ATT_I747UCDLK3_I747ATTDLK3_Original.zip.html?
Download the files to your PC and extract.
To flash via Odin, open Odin.exe on your PC
Click on the PDA tab and navigate to the file you just extracted. Select the file ending in *.tar.md5 (For 4.1.1, this would be I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5). Make sure this file is showing in the PDA tab.
Boot your phone into download mode and connect to your computer with a good quality micro-USB cable. Make sure your phone is recognized by Odin. You should see the message Added in the left pane.
Do not check or uncheck any boxes other than the defaults.
Click on start and waiting for firmware flashing to end and you see Pass. Your phone will reboot at this stage. You can disconnect from your PC
However, for 4.3, it looks like the Odin flash-able file has been taken offline so you would need to this via custom recovery. That's a different process so please revert on your Android version first so we'll know whether this is required or not
I was running JB 4.3, and I am planning to flash 4.1.1 as you've said. I am downloading that rom from the SamMobile site, however it is taking quite a while...
I understand that it shouldnt be a two minute download, however its been 2 hours and only 210 MB has been downloaded.
Also, I have Odin v3.09, which in the place of a PDA tab, there is an AP tab... should I place the file in the AP tab?
rohanr014 said:
I was running JB 4.3, and I am planning to flash 4.1.1 as you've said. I am downloading that rom from the SamMobile site, however it is taking quite a while...
I understand that it shouldnt be a two minute download, however its been 2 hours and only 210 MB has been downloaded.
Also, I have Odin v3.09, which in the place of a PDA tab, there is an AP tab... should I place the file in the AP tab?
Click to expand...
Click to collapse
Please do not try to flash 4.1.1 if you were on JB 4.3 otherwise you could hard brick your phone due to the secure bootloader in 4.3. You need to revert to stock 4.3 via custom recovery. You may go to the thread below for instructions...
http://forum.xda-developers.com/showthread.php?t=2658486
1) Flash custom recovery (I would suggest TWRP because of the GUI). In Odin v3.09 use the AP tab in place of PDA. You can download TWRP for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore zip file in the thread above and copy to your (micro) SD card. The (TWRP) stock restore zip is also available via the following link .... http://www.mediafire.com/download/30idxwhg2hidxx2/ATT_I747_UCUEMJB_StockRestore_2282014.zip
3) Flash the custom recovery file via Odin. Remove battery immediately the flashing is complete to stop reboot.
4) Place the SD card with the recovery file in your phone
5) Reboot into recovery mode by simultaneously holding down the Volume Up, Home and Power buttons. Hold all buttons until you see the blue flash across your screen, then release power button but keep holding the volume up and home buttons until the Android image appears.
6) Select install and navigate to the stock restore file. Swipe across screen to flash and wait for installation to be complete.
7) Clear cache/dalvik and reboot to system
If you are unable to boot to recovery, then you may still try flashing using Odin v3.09. You may follow the instructions in the thread below and load all the respective partitions. You would need to use the version that has separate flashable files as the single *.tar file has been taken down.
Larry2999 said:
Please do not try to flash 4.1.1 if you were on JB 4.3 otherwise you could hard brick your phone due to the secure bootloader in 4.3. You need to revert to stock 4.3 via custom recovery. You may go to the thread below for instructions...
http://forum.xda-developers.com/showthread.php?t=2658486
1) Flash custom recovery (I would suggest TWRP because of the GUI). In Odin v3.09 use the AP tab in place of PDA. You can download TWRP for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore zip file in the thread above and copy to your (micro) SD card. The (TWRP) stock restore zip is also available via the following link .... http://www.mediafire.com/download/30idxwhg2hidxx2/ATT_I747_UCUEMJB_StockRestore_2282014.zip
3) Flash the custom recovery file via Odin. Remove battery immediately the flashing is complete to stop reboot.
4) Place the SD card with the recovery file in your phone
5) Reboot into recovery mode by simultaneously holding down the Volume Up, Home and Power buttons. Hold all buttons until you see the blue flash across your screen, then release power button but keep holding the volume up and home buttons until the Android image appears.
6) Select install and navigate to the stock restore file. Swipe across screen to flash and wait for installation to be complete.
7) Clear cache/dalvik and reboot to system
If you are unable to boot to recovery, then you may still try flashing using Odin v3.09. You may follow the instructions in the thread below and load all the respective partitions. You would need to use the version that has separate flashable files as the single *.tar file has been taken down.
Click to expand...
Click to collapse
Just to reaffirm since I am not very experienced and do not wish to break my phone:
1) Download the twrp 2.6.3.1 d2att.tar file and flash it to my phone in download mode via Odin.
2)Download zip file on my computer, and take out the microSD from my phone, and copy the file to my microSD.
3) I am confused here because you stated to flash the custom recovery in step 1... anyways when flash is complete I immediately take my battery out to stop the reboot.
4) I insert the microSD with the zip file containing the stock rom
5) Now I should be able to reboot into recovery mode on my phone, though I could not beforehand.
6) Once in Recovery, go to Install and flash the custom stock.
7)Wipe dalvik cache and cache, and reboot to system.
Please clear up any confusion, I am very cautious and inexperienced. Sorry.
rohanr014 said:
Just to reaffirm since I am not very experienced and do not wish to break my phone:
1) Download the twrp 2.6.3.1 d2att.tar file and flash it to my phone in download mode via Odin.
2)Download zip file on my computer, and take out the microSD from my phone, and copy the file to my microSD.
3) I am confused here because you stated to flash the custom recovery in step 1... anyways when flash is complete I immediately take my battery out to stop the reboot.
4) I insert the microSD with the zip file containing the stock rom
5) Now I should be able to reboot into recovery mode on my phone, though I could not beforehand.
6) Once in Recovery, go to Install and flash the custom stock.
7)Wipe dalvik cache and cache, and reboot to system.
Please clear up any confusion, I am very cautious and inexperienced. Sorry.
Click to expand...
Click to collapse
Yes, you are correct. What you are doing in step 1) is flashing custom recovery to your phone. Custom recovery allows you install zip files to your phone and is more functional and versatile than stock recovery.
The zip file referred to in 2) is the stock restore zip. This is the file you will be flashing from (custom) recovery and is the one from the following link (http://www.mediafire.com/download/30...re_2282014.zip). Once you have downloaded it to your computer, save to an SD card so you can insert it into your phone to flash.
The battery pull is after flashing the TWRP file. You then have to boot into (custom) recovery mode to flash the stock restore zip from the SD card.
You are OK on the other steps. Trust this clarifies. Let me know if you encounter any issues.
I have done everything you said, I flashed the TWRP file via Odin, and then i copied the stock zip file to my microSD and put it back into my phone.
I am able to boot into recovery, and everytime I go to flash the stock rom, midway through the flash my phone starts rebooting. Even if I try to clear dalvik cache and cache first, once they are cleared my phone automatically starts rebooting. What do I do now? The zip file is there and I can reach TWRP recovery, but the flash wont complete because my phone starts rebooting. I am at a 100% battery right now so I do not know what the cause of this could be. Please help, I cannot tell what I did wrong if I did do anything wrong.
Try installing the latest version of Philz Touch for the d2lte. Some people have good results with TWRP. I found Philz Touch, which is based on CWM, better for my purposes. Philz can be installed via Odin as long as you down the tar version.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Larry2999 said:
Yes, you are correct. What you are doing in step 1) is flashing custom recovery to your phone. Custom recovery allows you install zip files to your phone and is more functional and versatile than stock recovery.
The zip file referred to in 2) is the stock restore zip. This is the file you will be flashing from (custom) recovery and is the one from the following link (http://www.mediafire.com/download/30...re_2282014.zip). Once you have downloaded it to your computer, save to an SD card so you can insert it into your phone to flash.
The battery pull is after flashing the TWRP file. You then have to boot into (custom) recovery mode to flash the stock restore zip from the SD card.
You are OK on the other steps. Trust this clarifies. Let me know if you encounter any issues.
Click to expand...
Click to collapse
Ok, something very strange has occured.
Since my phone would not flash the original stock rom, I decided to go ahead and flash CM10.2 and its gapps to see if it the problem was with my phone or with the file. Everything worked fine and my phone booted and ran CM10.2, but then I had absolutely no signal anywhere. I could confirm something was wrong because there were multiple AT&T users near me that had good signal. So then I went to flash the stock rom, and it worked. I cleared dalvik and cache like normal after all these flashes and performed factory resets, however when I flashed this stock rom, it worked but 1) I could not connect to Wifi 2) I could not use apps with root requirements, and Root Checker said I did not have root access, even though I had definitely rooted my phone earlier when I first ran CM11 and CM10.2
Should I root again? Please help, my phone is working and I can go into download, stock recovery, and normal mode.
audit13 said:
Try installing the latest version of Philz Touch for the d2lte. Some people have good results with TWRP. I found Philz Touch, which is based on CWM, better for my purposes. Philz can be installed via Odin as long as you down the tar version.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Click to expand...
Click to collapse
The whole idea was to get your phone back to working state. Thereafter, you can build up on the food chain. The stock file you flashed restores the phone to near factory settings including a complete stock (official) firmware, stock recovery, resetting the flash counter. Unfortunately, it also removes root as well. You can, however, re-root in a number of ways. You may also do as Audit advised and reflash Philz Touch custom recovery which would allow you flash any custom ROM of your choice. You do not necessarily need to root to flash custom ROMs if you have custom recovery. However, if you need to use apps which require root, I would recommend you try SafeRoot (http://forum.xda-developers.com/showthread.php?t=2565758). Very easy to use and worked quite well for me.
Finally, you should be able to restore your Wi-Fi from settings. Wi-Fi setup should have happened during the set-up process upon reboot after the firmware installation but sometimes this step is skipped. If you go to Settings, you should be able to enable and set up Wi-Fi.