:cyclops: hello. (I have been searching for quite some time. and have not found a thread that has helped me along. disclaimer.)
I have recently installed the custom LinaroCM10 ROM for the Samsung Galaxy Exhibit II 4G (t679), and upon restoring my apps and data via Titanium backup, the messaging (i could open the app, but not individual threads), exchange, (and email?) services ceased to function. that it does not come with wifi calling, (which is necessary while I am at home), I searched for another ROM. Excited by the possibility of wifi calling, i immediately endeavored to install jedimindtricks x3, only to find that it is not for my phone in the least. Now, between multiple Clockworkmod (v6.0.1.2) wipes of everything, I am left with a phone that will only boot into recovery or download mode.
I am currently trying to flash the stock file - uvlg3.flash2stock.zip via ADB (platform-tools), but to no avail. I have made many silly mistakes, but I would very much like to bring my phone back to normal, so that I may...root it again. I greatly appreciate any and all assistance kindly bequeathed upon my novice eyes and ears. Thank you.
robbiegeiss said:
:cyclops: hello. (I have been searching for quite some time. and have not found a thread that has helped me along. disclaimer.)
I have recently installed the custom LinaroCM10 ROM for the Samsung Galaxy Exhibit II 4G (t679), and upon restoring my apps and data via Titanium backup, the messaging (i could open the app, but not individual threads), exchange, (and email?) services ceased to function. that it does not come with wifi calling, (which is necessary while I am at home), I searched for another ROM. Excited by the possibility of wifi calling, i immediately endeavored to install jedimindtricks x3, only to find that it is not for my phone in the least. Now, between multiple Clockworkmod (v6.0.1.2) wipes of everything, I am left with a phone that will only boot into recovery or download mode.
I am currently trying to flash the stock file - uvlg3.flash2stock.zip via ADB (platform-tools), but to no avail. I have made many silly mistakes, but I would very much like to bring my phone back to normal, so that I may...root it again. I greatly appreciate any and all assistance kindly bequeathed upon my novice eyes and ears. Thank you.
Click to expand...
Click to collapse
Everything you need is here http://forum.xda-developers.com/showthread.php?t=1686384 in post #2. Have you tried dropping the uvlg3.flash2stock.zip on your external sd card and flashing?
NomadSpin said:
Everything you need is here http://forum.xda-developers.com/showthread.php?t=1686384 in post #2. Have you tried dropping the uvlg3.flash2stock.zip on your external sd card and flashing?
Click to expand...
Click to collapse
Yes. I have the necessary zip files, But my problem is actually getting them through via cmd/ADB
i type
"cd desktop/platform-tools"
brings me to the correct folder
then I don't know what to type to correctly push the file with ADB
file path is:"C:\Users\Robbie\Desktop\platform-tools\uvlg3.flash2stock.zip"
Step 6: http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
Edit: try adb push C:\Users\Robbie\Desktop\platform-tools\uvlg3.flash2stock.zip /storage/sdcard0
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Good luck. Flashing a ROM through adb was only ever really achieved on HTC phones. I would just flash through recovery since you can access it. Or since this is a Samsung phone the other option is Odin. If you attempt an adb flash you may risk bricking your phone.
P.S. first result in Google searching " flash android rom adb."
Sent from my SGH-T679 using xda app-developers app
---------- Post added at 03:33 PM ---------- Previous post was at 03:28 PM ----------
Also the problem you had with your previous rom could have been avoided if you hadn't have restored data with Titanium. This has caused issues over and over, and has been stated in several threads. Many times it is incompatible data from another rom. Restoring apps is fine data is tricky and usually causes problems. Hope you get things sorted out.
Sent from my SGH-T679 using xda app-developers app
Dvarl said:
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Good luck. Flashing a ROM through adb was only ever really achieved on HTC phones. I would just flash through recovery since you can access it. Or since this is a Samsung phone the other option is Odin. If you attempt an adb flash you may risk bricking your phone.
P.S. first result in Google searching " flash android rom adb."
Sent from my SGH-T679 using xda app-developers app
---------- Post added at 03:33 PM ---------- Previous post was at 03:28 PM ----------
Also the problem you had with your previous rom could have been avoided if you hadn't have restored data with Titanium. This has caused issues over and over, and has been stated in several threads. Many times it is incompatible data from another rom. Restoring apps is fine data is tricky and usually causes problems. Hope you get things sorted out.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Thank very much you Dvarl. I looked into using ODIN and it does indeed seem I have fixed my phone (using: http://androidforums.com/exhibit-2-...bit-ii-4g-back-its-factory-out-box-state.html). Thank you so much, and everyone else, as well, for the advice!!!
Glad you got it straightened out. Just would hate to see someone brick their phone. Out of of the 8 devices I have rooted I have only ever bricked one. That was my fault alone as I overclocked too high and fried my phone.
Sent from my SGH-T679 using xda app-developers app
Dvarl said:
Glad you got it straightened out. Just would hate to see someone brick their phone. Out of of the 8 devices I have rooted I have only ever bricked one. That was my fault alone as I overclocked too high and fried my phone.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Haha. Indeed. Hardware destruction seems pretty irrevocable on this scale. Does overclocking usually fry?
If it is kept at safe values no. I made the mistake of going 1.8 for too long safest value for this phone is no higher than 1.4. But it should be noted that these phones vary greatly and some people can only go 1.2, some not at all.
Sent from my SGH-T679 using xda app-developers app
Dvarl said:
If it is kept at safe values no. I made the mistake of going 1.8 for too long safest value for this phone is no higher than 1.4. But it should be noted that these phones vary greatly and some people can only go 1.2, some not at all.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
of course. It depends on the original processing rate, yes?
For the most part. There is a safe level for each processor. On this phone all were stable at 1GZ but some can be safely overclocked, Smartguy found that anything over 1.4 can seriously damage the phone. So that is only a guide, some of these processors can't be over clocked at all. It really depends on your phone. I you want more information about this I suggest reading the kernel threads. There are more experienced answers there.
Sent from my SGH-T679 using xda app-developers app
Related
Hello,
Hoping that someone can take a few minutes to answer my questions. I have the at&t branded "SGH-I957" and have finally given up hope that Samsung is ever going to upgrade this thing to ICS. I am tired of how clunky and bad the U/I is, all the crashes, etc. etc. and after much back and forth decided to give XDA a try in finding a custom ROM. I had several pre-Windows 7 phones and flashed like crazy on those things years ago but have never done this on an Android device. I get too addicted to flashing so I didn't want to start with Android, but here we go!!
I flashed my 8.9 tablet with just about everything I could find. The different ROM's consistently load up and run but they lag so bad they are pretty much unusable. So after a week of lots and lots of learning and flashing I went back to the old crappy Gingerbread stock ROM. What am I doing wrong?. I figure no-one would be doing this if everyone had these results. So I'd like to humbly ask if someone could review my steps to possibly point out what I am missing.
1. I rooted my device and installed TWRP as my recovery tool.
2. I found a few ROM's to try and downloaded them and then placed them on my device's internal storage in the download folder.
3. I booted into TWRP, went to the Wipe menu and did a system reset, ROM reset, cache reset and dvork cache reset.
4. Still in TWRP I went to the install menu, found the zip file for the ROM I wanted to load and installed it.
5. Ran another Dvork cache wipe.
6. Booted into the system.
In every case my system loads up fine, I can connect to the at&t LTE network, I can connect to my Wireless connection. I can connect to Google and reload my profile....everything looks good.
7. Next I am using either the ROM tool or TWRP to reset permissions on my Apps.
Now I try to use the tab and find that everything just lags terribly. I hit settings and it sits and sits....after about 30 - 45 seconds I get a prompt that setting is not responding, do you want to kill it? I tap "wait"..........more lag and after about 60 seconds it loads. Then every subsequent tap behaves the same way.
This happens with every single flash and with each of the 3 different ROM's I've tried to I am convinced I must be doing something wrong in the process and hope that someone here that has more experience and expertise than I do might have some advice.
Thanks in advance for the help.
You should not have to reset permissions. For a ROM, try the JB ROM in the cm 10 how to in the developer section. If been running this for two weeks with no major issues.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
---------- Post added at 09:12 AM ---------- Previous post was at 08:53 AM ----------
PS,not sure what you meant with the resets, ROM, cache, etc. I use TRWP and just wipe the system and the caches. I don't do the dalvic wipe after the install, but I don't think it makes a difference one way or the other.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
---------- Post added at 09:31 AM ---------- Previous post was at 09:12 AM ----------
PPS, out of curiosity I fixed permissions in TRWP with ROM I mentioned above and had no problems so it might be the ROM you're using. I've found it difficult to find good ROM's for the i957. I've tried many ROMs also with limited success, this one does almost everything I would wish for.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Tried the suggested ROM. I experience the same lag for all the roms I've tried.
I think I used the wrong terminology. Reset=Wipe. I wiped everything. Cache, System and delvik
Sent from my SAMSUNG-SGH-I957 using XDA Premium HD app
Originally, I started with just wanting to update the firmware on my phone because I read updating it to a newer version fixes the dreadful "low memory" bug, where the phone constantly thinks it has no internal memory left despite having plenty.
I tried updating the phone with Kies - says unsupported for updates. Tried updating the CSC, still couldn't get updates.
Then I thought, I always wanted to mod the phone but didn't have the time. I sat down to do it today, spent HOURS and HOURS on here following the guides and reading and I can't seem to get anywhere. Any ROM gives me a Status 7 failure when I try flash it and I notice that CWM doesn't boot up (just the default Android one). I can't even seem to get my phone to go into download mode for use Odin and put a new stock rom on it. And yes, I rooted the phone, deleted all the caches and data, tried unrooting it...nothing.
I read that maybe it's because I have a Koodo Samsung Galaxy Ace...and that it has a different ROM that can't be meddled with. I mean, the update software option under the Settings is even greyed out. It's hard for me to even follow the youtube guides when my phone isn't responding like the ones in the videos.
I'm literally going nuts. I've tried everything. Someone please help me.
nookthecat said:
Originally, I started with just wanting to update the firmware on my phone because I read updating it to a newer version fixes the dreadful "low memory" bug, where the phone constantly thinks it has no internal memory left despite having plenty.
I tried updating the phone with Kies - says unsupported for updates. Tried updating the CSC, still couldn't get updates.
Then I thought, I always wanted to mod the phone but didn't have the time. I sat down to do it today, spent HOURS and HOURS on here following the guides and reading and I can't seem to get anywhere. Any ROM gives me a Status 7 failure when I try flash it and I notice that CWM doesn't boot up (just the default Android one). I can't even seem to get my phone to go into download mode for use Odin and put a new stock rom on it. And yes, I rooted the phone, deleted all the caches and data, tried unrooting it...nothing.
I read that maybe it's because I have a Koodo Samsung Galaxy Ace...and that it has a different ROM that can't be meddled with. I mean, the update software option under the Settings is even greyed out. It's hard for me to even follow the youtube guides when my phone isn't responding like the ones in the videos.
I'm literally going nuts. I've tried everything. Someone please help me.
Click to expand...
Click to collapse
What do you want to do ? Flash stock via odin or root for a custom one ?
I used to have beautiful life before. Now I'm in engineering...!
Venomous Viper 119 said:
What do you want to do ? Flash stock via odin or root for a custom one ?
I used to have beautiful life before. Now I'm in engineering...!
Click to expand...
Click to collapse
Now that I've gone through the effort - custom rom.
nookthecat said:
Now that I've gone through the effort - custom rom.
Click to expand...
Click to collapse
You aren't able to boot in to downloading mode. So flashing stock via odin isn't possible that easily. You'll have to try Jtag or oneclickunbrick. But before that, are you atleast able to boot into recovery ? What version of cwm are you using ?
I used to have beautiful life before. Now I'm in engineering...!
---------- Post added at 09:38 PM ---------- Previous post was at 09:37 PM ----------
Venomous Viper 119 said:
You aren't able to boot in to downloading mode. So flashing stock via odin isn't possible that easily. You'll have to try Jtag or oneclickunbrick. But before that, are you able to atleast able to boot into recovery ? What version of cwm are you using ? And what does the phone show when you just switch it on ?
I used to have beautiful life before. Now I'm in engineering...!
Click to expand...
Click to collapse
I used to have beautiful life before. Now I'm in engineering...!
Venomous Viper 119 said:
You aren't able to boot in to downloading mode. So flashing stock via odin isn't possible that easily. You'll have to try Jtag or oneclickunbrick. But before that, are you atleast able to boot into recovery ? What version of cwm are you using ?
I used to have beautiful life before. Now I'm in engineering...!
I actually managed to get the phone to go into Download mode this morning. I have Odin v. 3 on my computer, and right now I'm trying to flash CWM onto the phone. It keeps saying Setup Connection... for a long time then fails. I reinstalled my drivers... and the computer recognizes my phone.
I installed CMW through the google play app..I had the latest version (6) and tried using 5.2. The phone keeps booting back into Android recovery manager instead, even when I ask it to install a rom through the app.
Click to expand...
Click to collapse
It says in my phone (behind battery) the phone model is GTS5830D. Is this somehow different from any other GTS5830? People are saying to flash it with 2.3.6 firmware first, but the thing is, I can't flash it with anything. Everything I've tried to flash gives the Status 7 failure message.
nookthecat said:
It says in my phone (behind battery) the phone model is GTS5830D. Is this somehow different from any other GTS5830? People are saying to flash it with 2.3.6 firmware first, but the thing is, I can't flash it with anything. Everything I've tried to flash gives the Status 7 failure message.
Click to expand...
Click to collapse
Yes... S5830D does differ from S5830. In what way...? It doesn't matter now. Just go to the samsung service center & they'll fix it for you. But play dumb. Don't talk about roms, rooting, etc. Just say that it happened while updating via kies...
I used to have beautiful life before. Now I'm in engineering...!
Yeah, everything is pointing to this being impossible. It's not even a C/M/i model, just D which seems to have nothing behind it.
Guess that's why Koodo phones in Canada are so dirt cheap - some kind of weird, low-end international version of the regular phone. There isn't even updates on Kies for this model. The original ROM is still on the phone, so it works fine...but I know after a short time it will start getting really laggy and get the same 'low memory' message. I was hoping to improve the phone.
Odd. Mine is the 5830D and I had no problem rooting and flashing. I'm on my second custom ROM (maybe 3rd can't remember) .
Sent from my GT-S5830 using xda app-developers app
---------- Post added at 02:36 PM ---------- Previous post was at 02:30 PM ----------
I noticed you said you downloaded CWM thru the play store. Was it ROM manager by any chance?
Sent from my GT-S5830 using xda app-developers app
hooked_on_droid said:
Odd. Mine is the 5830D and I had no problem rooting and flashing. I'm on my second custom ROM (maybe 3rd can't remember) .
Sent from my GT-S5830 using xda app-developers app
---------- Post added at 02:36 PM ---------- Previous post was at 02:30 PM ----------
I noticed you said you downloaded CWM thru the play store. Was it ROM manager by any chance?
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
Which roms did you use? Can you give me some links...
Hopefully someone with some insight on this Status 7 error shows up because I'm finding nothing useful on the forum or in google.
Update: I got CWM 5.2 to work, but I had to use the one for the 5830i model. Still get the installation errors though.
I have used Apocolypse and am currently on Democracy. The link for Democracy is normally in my signature, but since I'm on my cell I will have to see if I can find it. Both are excellent roms. I used unlock root to root mine, its pretty easy to use.
Sent from my GT-S5830 using xda app-developers app
Just ignore my post. I missed the part about using a recovery from the "I". Sorry
Sent from my GT-S5830 using xda app-developers app
hooked_on_droid said:
http://forum.xda-developers.com/showthread.php?t=1712654
Link for Democracy
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
Did you just read his update ? He's using the recovery of s5830i. Hope it doesn't put him in trouble. I know that the s5830i,d,l,m, etc; are almost the same though...
I used to have beautiful life before. Now I'm in engineering...!
nookthecat said:
Yeah, everything is pointing to this being impossible. It's not even a C/M/i model, just D which seems to have nothing behind it.
Guess that's why Koodo phones in Canada are so dirt cheap - some kind of weird, low-end international version of the regular phone. There isn't even updates on Kies for this model. The original ROM is still on the phone, so it works fine...but I know after a short time it will start getting really laggy and get the same 'low memory' message. I was hoping to improve the phone.
Click to expand...
Click to collapse
I'm with Koodo, have a straight old S5830. Bought it from them at the kiosk in my local mall. Currently running CM9.1 RC4.1 by Wayland_ACE. How were you flashing your stuff before you had issues? Via recovery or Odin?
How did you install CWM? I hope you flashed it from recovery.
DON'T TOUCH ROM MANAGER.
UPDATE: I'm sorry, I do have the GT-S5830D from Koodo. My ROM is for the S5830 though. It works fine.
http://forum.xda-developers.com/showthread.php?t=1868121
Venomous Viper 119 said:
Did you just read his update ? He's using the recovery of s5830i. Hope it doesn't put him in trouble. I know that the s5830i,d,l,m, etc; are almost the same though...
I used to have beautiful life before. Now I'm in engineering...!
Click to expand...
Click to collapse
Lolno. The d,l,m,b are similar because they are just nationality variants. i is an entirely different model. Nothing for the S5830i works with the S5830 properly. There is a reason that it has separate threads from the other variants.
Hi Guys,
I'm a noob so please send me in the right direction if I seem out of place. I have an Exhibit 4G that I managed to root. It was 2.3.6 I believe. All was great until I decided I wanted to change the operating system to a Peach Sunrise (I think) then it became stuck in a boot screen loop. I have tried resetting to factory but that doesn't help. I'm not too savvy with these phones so I'm stuck at a dead end. I'm looking for someone in the Atlanta area to fix it for me. I'm willing to pay. It was a brand new phone bought from an individual. It was only used about two week by me. Please let me know if you can help or have a relatively easy solution. Thanks in advance, Les
Is it the galaxy exhibit 4G T679? It the original exhibit? There are multiple phones with the same name. Also wiping cache/dalvik cache and fix permissions will usually fix a problem like this.
Sent from my SGH-T679 using xda app-developers app
patches0616 said:
Hi Guys,
I'm a noob so please send me in the right direction if I seem out of place. I have an Exhibit 4G that I managed to root. It was 2.3.6 I believe. All was great until I decided I wanted to change the operating system to a Peach Sunrise (I think) then it became stuck in a boot screen loop. I have tried resetting to factory but that doesn't help. I'm not too savvy with these phones so I'm stuck at a dead end. I'm looking for someone in the Atlanta area to fix it for me. I'm willing to pay. It was a brand new phone bought from an individual. It was only used about two week by me. Please let me know if you can help or have a relatively easy solution. Thanks in advance, Les
Click to expand...
Click to collapse
What do you mean by reset to factory? Wiping data does not change the operating system. However do you have cwm installed and yea is it even the t679
Sent from my Nexus 7 using xda app-developers app
i bricked my phone
:i cant get in recovery mode i have bricked my phone i was puting a costum rom on my phone stuck in boot logo and odin is not working please help :crying
allenw420 said:
:i cant get in recovery mode i have bricked my phone i was puting a costum rom on my phone stuck in boot logo and odin is not working please help :crying
Click to expand...
Click to collapse
Do you have the right drivers? Just download Samsung kies and it should be fixed
Sent from my Nexus 7 using xda app-developers app
Dvarl said:
Is it the galaxy exhibit 4G T679? It the original exhibit? There are multiple phones with the same name. Also wiping cache/dalvik cache and fix permissions will usually fix a problem like this.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Hi Dvarl,
I'm extremely sorry but I forgot to bookmark the sight and finally decided to search my laptop history to find the thread. The phone is the newer model SGH-T679 galaxy exhibit, not the exhibit II. I have tried wiping the cache but i'm not sure exactly how to proceed to do all the procedures that you are talking about. It does not have cwm installed. I did manage to root it before I got myself in this mess.
I can assure you I will be checking the replies frequently and any help is appreciated.
theAPANT said:
What do you mean by reset to factory? Wiping data does not change the operating system. However do you have cwm installed and yea is it even the t679
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I would like to put it back to way it came out of the box or really I would like to have the newest OS on it. After that I think I could root it myself (after performing a backup). It does not have cwm installed on it. It is the newer 4G Exhibit not the exhibit II. Thanks for the reply and sorry I lost the forum and finally searched my history to find it.
Regards,
Les
patches0616 said:
I would like to put it back to way it came out of the box or really I would like to have the newest OS on it. After that I think I could root it myself (after performing a backup). It does not have cwm installed on it. It is the newer 4G Exhibit not the exhibit II. Thanks for the reply and sorry I lost the forum and finally searched my history to find it.
Regards,
Les
Click to expand...
Click to collapse
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
theAPANT said:
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Wow that was a fast response! I have saved your link so I can try it. You are right, it is the renamed exhibit II. The startup screen used to say exhibit NOT exhibit II. I just wished I had backed it up before I made the big mistake. I have learned my lesson. I'll give it a shot tomorrow and let you know the results. Thanks again for your help, Les
I'm having the same problem. I tried odin but it's not working.. what am I missing?
What I do because it is much much faster IMHO, I would use Odin to put cwm back on the phone then download any ROM I want or the flash to stock, or even better if you followed the rules restore a nandroid
Sent from my SGH-T679 using xda app-developers app
theAPANT said:
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I do have the renamed t679. I must be doing something wrong. First I put it into restore mode and clear the cache then restart in download mode. Then I start the Odin Multi Downloader (Ancora) and insert into the OPS field the Ancora.ops then insert into the One Package field the T679LG3.tar file then hit start until all automatically finishes.
I am still left with a phone in the boot logo loop. I noticed when I wiped the cache and restarted the phone script said something about " unable to mount \system .... I didn't take a snapshot so I'm not exactly sure of what it was but I know the phone will not start up if it can't mount the system partition, at least I think I saw that somewhere in a thread.
Any suggestions? I wish I knew someone around Atlanta that I could join up with and get this thing working. I loved this phone and only used it for about a week. I'm thinking before all this is over I will be a phone geek instead of a newbie. All the information that I have gotten here is super helpful, I just don't know enough to effectively utilize it.
patches0616 said:
I do have the renamed t679. I must be doing something wrong. First I put it into restore mode and clear the cache then restart in download mode. Then I start the Odin Multi Downloader (Ancora) and insert into the OPS field the Ancora.ops then insert into the One Package field the T679LG3.tar file then hit start until all automatically finishes.
I am still left with a phone in the boot logo loop. I noticed when I wiped the cache and restarted the phone script said something about " unable to mount \system .... I didn't take a snapshot so I'm not exactly sure of what it was but I know the phone will not start up if it can't mount the system partition, at least I think I saw that somewhere in a thread.
Any suggestions? I wish I knew someone around Atlanta that I could join up with and get this thing working. I loved this phone and only used it for about a week. I'm thinking before all this is over I will be a phone geek instead of a newbie. All the information that I have gotten here is super helpful, I just don't know enough to effectively utilize it.
Click to expand...
Click to collapse
OK now use the volume up and power to get to a screen with a box and then hit menu that will bring you to a recovery and just click wipe data factory reset and you should be fine.
Sent from my Nexus 7 using xda app-developers app
theAPANT said:
OK now use the volume up and power to get to a screen with a box and then hit menu that will bring you to a recovery and just click wipe data factory reset and you should be fine.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've tried that more than ten times to no avail. I get the feeling that the original OS may be corrupt or missing or maybe that "unable to mount" message that I saw.
patches0616 said:
I've tried that more than ten times to no avail. I get the feeling that the original OS may be corrupt or missing or maybe that "unable to mount" message that I saw.
Click to expand...
Click to collapse
OK well if it boots to the android icon with green fire or whatever then you have an os. My only advice is to make sure you check the right things when using Odin.
Edit: there is a very slim possibility that you have a fried emmc chip but I doubt it. Also make sure it says pass before you unplug
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:44 PM ---------- Previous post was at 09:20 PM ----------
How far do you boot to? How long does it take for Odin to finish?
Sent from my Nexus 7 using xda app-developers app
Odon does the same thing to me, it says pass but still boot loops, that's why I recommend just doing cwm through Odin and flash the b2s or any ROM you desire
Sent from my SGH-T679 using xda app-developers app
theAPANT said:
OK well if it boots to the android icon with green fire or whatever then you have an os. My only advice is to make sure you check the right things when using Odin.
Edit: there is a very slim possibility that you have a fried emmc chip but I doubt it. Also make sure it says pass before you unplug
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:44 PM ---------- Previous post was at 09:20 PM ----------
How far do you boot to? How long does it take for Odin to finish?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
When I run the Odin Multi Downloader program it takes 5 mins and 38 secs to finish. The phone restore Odin is fairly fast when I reset to factory settings but I've never timed it. The phone boots to the t-mobile exhibit screen just beyond the plain white Samsung start up screen.
patches0616 said:
When I run the Odin Multi Downloader program it takes 5 mins and 38 secs to finish. The phone restore Odin is fairly fast when I reset to factory settings but I've never timed it. The phone boots to the t-mobile exhibit screen just beyond the plain white Samsung start up screen.
Click to expand...
Click to collapse
Hmm when I've done it it took about 10min, so perhaps the 300 sec reset option is not set. Try what tazmanion said by using Odin to flash cwm and then you can Mount system in revovery
If it doesn't get to boot animation then yea you have no os
Sent from my Nexus 7 using xda app-developers app
I'm also still having bootloop issues, I wiped cache/dalvik, fixed permissions, wiped battery stats, etc. but best it did was sit on the SAMSUNG for like 2 minutes then go back into a bootloop.
I'd like to keep the original rom/system in tact to not loose any data (didn't backup beforehand, I know...) anyone have suggestions?
Thanks in advance.
(yes this is crossposted, need answer asap, sorry)
You do not have a ROM if it sits in Samsung
Sent from my SGH-T679 using xda app-developers app
Hello everyone, this will be my first post here, so I'm pretty much a newbie as I was only recently introduced to the world of Android (and only been using IOS for a few months before that!). So to keep it brief, this is my situation;
- Recently rooted my phone - No problems there
- Used root access apps such as Superuser, Titanium back up to name some from the top of my head.
- Got interested in ROMs and Kernels (mostly kernels, wasn't really going to install a new ROM)
- During my research, came upon Pimp my ROM, downloaded it and checked it out (This is where the problems come in)
- Looked through the options it gave me, much of it I didn't understand, so I left most of the options untouched.
- What I did change was the Density option and the tweak options (to decrease data loading times, faster performance etc).
- After making all my selections, I rebooted via the reboot option, but not before creating a rescue package supposedly.
- After the reboot, it went into a slight bootloop that lasted around 30 seconds before booting in. I found the density change to my disliking, so changed it to another setting.
- After rebooting it a second time, it was now permanently stuck trying to boot.
So that's my current situation. I've tried researching the issue on google and xda forums, but there doesn't seem to be a lot of information on the SP. The only thread directly stating a bootloop problem on xda I could find, I couldn't make heads or tails from the posts.
I've tried playing around with Sony PC companion, flashtool, sdk manager (adb). But the main issue seems to stem from the fact that these programs don't recognize my phone at all. I understand I'm supposed to fastboot it or boot into recovery, however it seems my method of trying the combo keys doesn't seem to work.
This is my phone's information;
Xperia SP (C5306)
Bought through fido (Canada)
Bootloader unlock: no (checked after rooting)
Rooting method from Doomlord's Easy Rooting Toolkit
Please let me know if you require more info and I'll be sure to provide it.
Any help would be greatly appreciated and even more so if you could take the time to explain to me any methods you suggest in simple terms (like I'm 5) as I'm rather new to Android/IOS. Thank you again!
How long did you try to boot your phone?
Do you have CWM? Maybe I can upload a rescue package for you...
Sent from my C5303 using xda premium
sonyxperiaplayer said:
How long did you try to boot your phone?
Do you have CWM? Maybe I can upload a rescue package for you...
Sent from my C5303 using xda premium
Click to expand...
Click to collapse
This problem occurred last night and after recalling something about maybe draining it's battery would somehow fix the issue, I left it on the bootloop until it ran out. Alas it proved no use and I am currently still stuck on the bootloop screen. I had never heard of CWM until you mentioned it now. I'm currently skimming over it's info at the moment, but I assume I must somehow have it installed onto my phone? Though it does sound extremely helpful I would definitely use it if I recover my SP.
Wraid said:
This problem occurred last night and after recalling something about maybe draining it's battery would somehow fix the issue, I left it on the bootloop until it ran out. Alas it proved no use and I am currently still stuck on the bootloop screen. I had never heard of CWM until you mentioned it now. I'm currently skimming over it's info at the moment, but I assume I must somehow have it installed onto my phone? Though it does sound extremely helpful I would definitely use it if I recover my SP.
Click to expand...
Click to collapse
If you don't have CWM, the recovery package will be of no use. You should read up on it, its really important in risky situations.
The only way now is to flash an FTF, I will find a guide on how to do it. Surely you don't mind to lose all your data?
There is still some hope though, that you can recover your phone without losing anything.
Sent from my C5303 using xda premium
---------- Post added at 05:55 PM ---------- Previous post was at 05:50 PM ----------
Here are the instructions, view the Flashtool section : http://forum.xda-developers.com/showthread.php?t=2354704
You can try unticking the 'Wipe Data' option on the configuration page, then it will not wipe your data and internal SD Card.
Try that and booting it to see if it was fixed. If not, then go for a full flash (just follow ALL the instructions there)
***ATTENTION! IT WILL WIPE YOUR INTERNAL SD CARD!*** not the SD card that you can remove
Sony phones are UNBRICKABLE for normal users! Don't worry! The worst thing that could happen will be losing all your stuff, but that's not bad compared to bricking your phone.
Sent from my C5303 using xda premium
sonyxperiaplayer said:
If you don't have CWM, the recovery package will be of no use. You should read up on it, its really important in risky situations.
The only way now is to flash an FTF, I will find a guide on how to do it. Surely you don't mind to lose all your data?
There is still some hope though, that you can recover your phone without losing anything.
Sent from my C5303 using xda premium
---------- Post added at 05:55 PM ---------- Previous post was at 05:50 PM ----------
Here are the instructions, view the Flashtool section : http://forum.xda-developers.com/showthread.php?t=2354704
You can try unticking the 'Wipe Data' option on the configuration page, then it will not wipe your data and internal SD Card.
Try that and booting it to see if it was fixed. If not, then go for a full flash (just follow ALL the instructions there)
***ATTENTION! IT WILL WIPE YOUR INTERNAL SD CARD!*** not the SD card that you can remove
Sony phones are UNBRICKABLE for normal users! Don't worry! The worst thing that could happen will be losing all your stuff, but that's not bad compared to bricking your phone.
Sent from my C5303 using xda premium
Click to expand...
Click to collapse
Thanks! I will try your solution and give a update. I don't mind losing the data on the phone since it's new and I barely have anything on it. It does give me some reassurance when you say Sony Phones are hard to brick!
Update: Phone was flashed and successfully booted! Thanks for your help! I've fixed my phone and gained new understanding on flashing! Kudos!
Wraid said:
Update: Phone was flashed and successfully booted! Thanks for your help! I've fixed my phone and gained new understanding on flashing! Kudos!
Click to expand...
Click to collapse
No prob. When you face a bootloop or anything that bricks your phone, use this.
This is why Sony phones are unbrickable!
Sent from my C5303 using xda premium
Hi I recently got a Note 3 for AT&T off Ebay. It was stuck in a bootloop so I wound up reflashing through Odin and got it to work. The problem I'm having is that the touch screen does not work but the S-pen does does that mean the digitizer is gone. I looked and read everywhere and found no solution other than contacting Samsung and trying to have it under warranty.
What do I do?? Any help would be greatly appreciated.
Odd. Did you use kies or Odin? Is it possible this device was opened once and part of the digitizer not plugged in?
Sent from my XT907 using XDA Free mobile app
mrkhigh said:
Odd. Did you use kies or Odin? Is it possible this device was opened once and part of the digitizer not plugged in?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
I have no clue, the guy i got it from told me it was a work phone, he said the touch screen worked and sometimes he would use the pen. The phone is in excellent condition. I used Odin to reflash the phone also installed Kies3. Do you think maybe flashing a custom rom will help it cause I can do that. I just need the tar file to root the phone, I looked but don't know where to find it.
It's just weird that the s-pen will work but not the touchscreen. Any help would be great.
I have no idea... I would honestly start with redownloading the files and flashing it again. Making sure it is a full Odin flash not a partial one.
Sent from my XT907 using XDA Free mobile app
Well when I flashed it I used the 4 files in the OP and flashed all those. What file do I need to root it. Maybe I will try that
Root isn't your current issue.... And is sorta complicated these days (more than doable just not à quick answer) . I honestly don't know what to tell you.
Sent from my XT907 using XDA Free mobile app
---------- Post added at 12:32 AM ---------- Previous post was at 12:26 AM ----------
I swear up and down I've seen this issue once though. I thought it had something to do with a dirty flash or a bad flash which is why I was wondering if you used all four files....
Sent from my XT907 using XDA Free mobile app
Well when I got the phone I noticed that it gave a system process error. When I tried to clear it with the touch screen it wouldn't. But the pen works which makes me believe it might be the digitizer. Not sure I heard there was an app to check the touch screen is this true
There is but it is for calibration.... I found a post that talked about a Samsung app breaking digitizer.... I still think I would do another factory reset, wipe it clean then try Odin again.... Then perhaps even updating all the apps.
Sent from my XT907 using XDA Free mobile app
What Samsung app is that? Maybe I can uninstall it. I will also try to rewipe and reinstall
Well I wound up getting root, installing safestrap, installed FireKat, and still the same no touch screen. I think it had to be a bad digitizer. Any other suggestions