Related
WOW! HOLY CRAP THIS PLACE IS DEAD! Its been a while since I read around these Zio places. Yup, my ol Zio still bootlooped (its around here somewhere). I tried all the "guides" n zip's and skd's and all that other.....stuff, its koo gathering and installing stuff and gettin that lil rush of hope, but then one lil thing goes wrong or ain't in the step-by-step guied, BOOM- all bad, and nobody's around all of a sudden. Alot of HERE, TRY THIS POST FROM SO N SO (not for the Zio), GO TO BLAHBLAH.COM install that n profit (evil setup to rom someone's phone AND wipe it clean), BUT ITS ALL MY BAD, NEWBIE like me shouldn't mess with roots n roms. Don't get me wrong, if I can find somebody that would fix it for cash, id go back to my zio and chuck this HALLWIE A2 (whatever its called) to a dev. Well, I'm probly gona get smashed for posting this. DEEEEP BREATH........K, I FEEL BETTER NOW.
Now I'm soo broke I cant even pay attention!
What you need help on? Bootloop fix? I can help you. Pm me on the details. Could you still get into faatboot or recovery? What service sprint or cricket!?
Sent from my Zio using XDA App
My zio is messed up too. I have no home/launcher or whatever you wanna call it. I can't get to settings to enable usb debugging either so none of the adb stuff works for me (so far). New to this and I don't want to buy another phone just yet. More details can be provided as to how this happened if needed. ty.
Not sure where it is but there was a fast boot zip of launcher apk. If you boot your phone into fast boot and cwm copy the zip to the phone and then flash the zip to your Zio it should resolve the issue
Sent from my Zio
Krsmqn said:
My zio is messed up too. I have no home/launcher or whatever you wanna call it. I can't get to settings to enable usb debugging either so none of the adb stuff works for me (so far). New to this and I don't want to buy another phone just yet. More details can be provided as to how this happened if needed. ty.
Click to expand...
Click to collapse
I can make a launcher apk. flashable zip for ya,just let Me know.
Sent from my LG-P509 using xda premium
openZIO Rom issue
Hi, I just installed the openZIO 2.1.2 ROM. Everything worked fine, but after rebooting and going through the initial set up (i.e. the google user setup blahblah) the VTL Launcher continually force closes and I can't do anything but go back and recover my original boot.img has anyone else had this kind of issue? Any possible fixes? Any help would be appreciated, I know not to many people are in using the Zio forums anymore... but yeah.. Thanks in advance
Try Reflashing again
Sent from my LG-P509 using xda premium
I've actually already done that, and it's still doing the same thing. I've deleted and re-downloaded the ROM, and re-flashed it to my phone, and still having the same issue. VTL Launcher just continually force closes, and it sucks cause I've been waiting months to get to install the ROM cause I couldn't afford a new USB cord. I've read so much on this ROM and everything for the Zio and was excited to actually be able to overclock my phone, and get some pretty good performance boosts out of it. Now I got one, and can't get it to work.. what a sad day
Could you explain your steps when flashing?
Sent from my LG-P509 using xda premium
well I first move the .zip to the sd, then power down and boot up CWM, and "install from SD card" and once it's finished flashing, I reboot the phone. when it comes back up my kyocera logo comes back up and it takes me through the first-boot programming (google sign-in) and once I input my un/pw and sign in, it tells me that VTL had an error and must hit force close. and once I hit force close it continues to come up saying the same thing over and over again. so I rebooted my phone, still the same thing. SO I go back through and flash it back to my original boot.img. I have gone through and completely deleted the openZIO 2.1.2.zip file and re-downloaded it, and gone through the same steps to see if maybe it was just a bad file somehow. But to no avail, still having the same issues.
After you boot into cwm : wipe cache partition, then go into mounts and storage, format: system, data, cache :then go into advanced and wipe dalvick cache.
Now flash rom
Sent from my LG-P509 using xda premium
Ok just went through with what you had mentioned, and still getting the same results. "Sorry! The application VTL.Launcher (process android.process.acore) has stopped unexpectedly. Please try again. with the only option to force close. As soon as I force close, the same message pops up
Have you tryed flashing my rom?
I would try that, and see what happens.
You can always push a launcher with adb or Droid commander.
Sent from my LG-P509 using xda premium
doing this now actually.. been reading for the last hour or so and seems like you did some good work on the ROM. it's flashing now, hopefully all works well I'm excited to see how it goes.
Well it flashed and well... seems to be having a strange issue.
When switching screens, it seems to glitch out? Like you see the icons, and when you switch screens, it's like the icons move but it freezes different frames. imma re-flash it in the morning to see if that helps any.
XCmaster said:
doing this now actually.. been reading for the last hour or so and seems like you did some good work on the ROM. it's flashing now, hopefully all works well I'm excited to see how it goes.
Well it flashed and well... seems to be having a strange issue.
When switching screens, it seems to glitch out? Like you see the icons, and when you switch screens, it's like the icons move but it freezes different frames. imma re-flash it in the morning to see if that helps any.
Click to expand...
Click to collapse
Im outta suggestions, I think you might have a hardware problem, but can't be for sure on that.
I've never heard of anybody having that problem, let me know if you get the issue resolved
Sent from my LG-P509 using xda premium
could defiantly be, this phone is well over a year old and has been dropped quite a number of times lol.
XCmaster said:
could defiantly be, this phone is well over a year old and has been dropped quite a number of times lol.
Click to expand...
Click to collapse
Was your phone acting like that before you flashed openzio?
Sent from my LG-P509 using Tapatalk 2
Nope, I've never had these issues before. And I can still flash it back to my original boot.img and it works like before. I've never had any problems with it, so that's why I'm surprised this is happening lol
XCmaster said:
Nope, I've never had these issues before. And I can still flash it back to my original boot.img and it works like before. I've never had any problems with it, so that's why I'm surprised this is happening lol
Click to expand...
Click to collapse
I guess then its probably not a hardware issue.. hmm.. its almost Like the roms your flashing are getting corrupted some how.
Sent from my LG-P509 using Tapatalk 2
hmm.. .well maybe I'll format my sd and do a factory reset on the phone first, then try to flash the rom?
I have been getting a lot of force closes on my AT&T LTE tab over the last couple of weeks. Mainly gmail, Android browser and the google services framework.
Is anyone else seeing this same issue?
I rooted the tab back in December, but haven't had any issues outside this recent spat of fcs.
Sent from my SAMSUNG-SGH-I957 using XDA App
I havent seen this.
Did you install CWM? if so you can try fixing permissions.
I get the same issue. orlando where do you change the permissions at in the file system?
You can fix permissions with CWM recovery.
Are you guys using the regular root kernel, or the OC kernel?
This stumps me, because I cant figure out why it would work fine for a month and then start to have FCs.
If you have CWM try clearing your cache and dalvik.
Since the tablet is so similar to the skyrocket, I would suggest reading this: http://forum.xda-developers.com/showthread.php?t=1386234
*dont do what the OP says though, just read it for info*
This also may be of help, but it would have to be modified. http://forum.xda-developers.com/showthread.php?t=1487706
I don't have a clear answer at this time.
Sent from my SAMSUNG-SGH-I727 using xda premium
I am running the normal root kernel, and no cwm installed.
I will read those threads, try the cwm permissions fix, and report back.
Sent from my SAMSUNG-SGH-I957 using XDA App
My force closes only happened after installing the OC with the LIB's pushed. I did the permissions fix and cleared the cache and dalvik. I'll let you know how it goes.
Hmmm. Started getting FC on YouTube now. Also am on stock. Not sure what happened but has been like this since yesterday. Not getting any other FC's though.
Sent from my GT-P7300 using xda premium
this is weird indeed.
The YouTube issue is widespread across tabs.
Yup I'm experiencing the same issues with Youtube. I didn't pay attention to Youtube because I don't watch videos via Youtube on my tab that often.
Looks like YouTube issue was fixed last night for tablets. This might not resolve OP but thought might be linked hence brought it up.
Sent from my GT-P7300 using xda premium
I have been talking to thederekjay, and he has written a tool for a more complete wipe than CWM can provide.
read here: http://forum.xda-developers.com/showthread.php?t=1487706
I checked out the script and the partitions are the same.
I am thinking that maybe running this after flashing clockworkmod and the custom kernel would aleviate FC's if multiple people are having them.
I dont know though, and the tool needs to be tested. I will let you know what he says.
EDIT: He said this should work. I sent him the output from my adb shell mount with partition layout.
I used the script. it ran fine.
really scary when i flashed the stock rom through odin and it froze at the ATT logo. wouldnt boot past.
i booted into 3e recovery and wiped data factory reset and it worked fine after that. feels slightly faster but that just might be a placebo effect.
K3N1K said:
YouTube app up and running here
Click to expand...
Click to collapse
yea its fixed.
my only suggestion to the other people seeing force closes is to maybe flash stock, and root without using a custom kernel....
OP, are you still seeing FCs?
OP...has your problem been resolved?
Since fixing the permissions I have had any force closes
Sent from my SAMSUNG-SGH-I957 using xda premium
orlandoxpolice said:
I used the script. it ran fine.
really scary when i flashed the stock rom through odin and it froze at the ATT logo. wouldnt boot past.
i booted into 3e recovery and wiped data factory reset and it worked fine after that. feels slightly faster but that just might be a placebo effect.
Click to expand...
Click to collapse
Hi, do you think the script will work on GSM version of this tablet too? (P7300)
Thanks for the answer.
pls delete - wrong tread.
woxydator said:
Hi, do you think the script will work on GSM version of this tablet too? (P7300)
Thanks for the answer.
Click to expand...
Click to collapse
Different partition layout I think
Sent from my SAMSUNG-SGH-I727 using xda premium
I am getting a massive amount of force closes on my i957. Stock kernel with cwm and root only. Fixing permissions in cwm does nothing and neither does rom manager. Incredibly annoying.
Sent from my SAMSUNG-SGH-I957 using xda premium
Hey all,
I just went from ICS to Stock 2.3.6 and the first thing I noticed is that after the flashing process where de phones go to recovery and loads for some time it asked me for a password... I tried many things but without luck, i flashed TWRP and wiped data and everything then it went away and I could normally use my phone...
Now I set up a Pin lock on my phone and I know 100% sure i know the pin because im using it for a year or so now but it keeps telling me the pincode is incorrect, so i cant unlock it.
Wiped everything again and did the same thing but again it keeps telling me its wrong while I know its correct...
How can I fix this?
Thanks in advance!
failly said:
Hey all,
I just went from ICS to Stock 2.3.6 and the first thing I noticed is that after the flashing process where de phones go to recovery and loads for some time it asked me for a password... I tried many things but without luck, i flashed TWRP and wiped data and everything then it went away and I could normally use my phone...
Now I set up a Pin lock on my phone and I know 100% sure i know the pin because im using it for a year or so now but it keeps telling me the pincode is incorrect, so i cant unlock it.
Wiped everything again and did the same thing but again it keeps telling me its wrong while I know its correct...
How can I fix this?
Thanks in advance!
Click to expand...
Click to collapse
Well, according to this: "I wiped data and everything then it went away and I could normally use my phone...", it seems (at least that's what I think) that you have set a software-based pin code (instead of the simcard code itself) from which you thought it was the simcard code all the time. so your simcard code remained unchanged. This is just my speculation, try the original code. (if you can still find it) Because wiping any partition would never delete information (pincode) on your simcard.
broodplank1337 said:
Well, according to this: "I wiped data and everything then it went away and I could normally use my phone...", it seems (at least that's what I think) that you have set a software-based pin code (instead of the simcard code itself) from which you thought it was the simcard code all the time. so your simcard code remained unchanged. This is just my speculation, try the original code. (if you can still find it) Because wiping any partition would never delete information (pincode) on your simcard.
Click to expand...
Click to collapse
No its not the pincode of my simcard that it asks for thats still there and working fine it asks for a password which i assume is the pinlock on my phone, i also tried without a lock on my phone and it still asks for it.
On this thread the OP has posted a phone its exactly like that!
http://forum.xda-developers.com/showthread.php?t=1066943
I just set another lock with the pin 1234 and it still says Fout Wachtwoord ´Incorrect Password´
p.s. my phone is unlocked
failly said:
No its not the pincode of my simcard that it asks for thats still there and working fine it asks for a password which i assume is the pinlock on my phone, i also tried without a lock on my phone and it still asks for it.
On this thread the OP has posted a phone its exactly like that!
http://forum.xda-developers.com/showthread.php?t=1066943
I just set another lock with the pin 1234 and it still says Fout Wachtwoord ´Incorrect Password´
p.s. my phone is unlocked
Click to expand...
Click to collapse
Have you tried to flash a new rom..after formating all your date it shud work is a new system , it showdent ask for the pasword
I flashed a new rom and got that
But it only got it when flashing a stock rom im now on a custom rom but i want to knwo the problem?
Sent from my GT-I9001 using xda app-developers app
May be your phone may be having security software. Installed in past which may have its files in sd
I had same problem in my 5230.....
Reboot to recovery connect to pc copy all imp songs photos etc to pc and wipe your sd and external one and factory reset
Sent from my GT-I9001 using xda premium
failly said:
I flashed a new rom and got that
But it only got it when flashing a stock rom im now on a custom rom but i want to knwo the problem?
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
Only possibly related thing I could found inside build.prop
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995
but im actually 99.99999% sure that that doesn't make any changes at all
Hmm thanks brood, i flashed the same stock before and it worked fine only after ICS i only wiped data and then flashed srock woth odin afterward i did all the wipes maybe that explains it...
Sent from my GT-I9001 using xda app-developers app
Hmm thanks brood, i flashed the same stock before and it worked fine only after ICS i only wiped data and then flashed srock woth odin afterward i did all the wipes maybe that explains it...
Odin only says RESET not Passed...
Sent from my GT-I9001 using xda app-developers app
Hmm thanks brood, i flashed the same stock before and it worked fine only after ICS i only wiped data and then flashed srock woth odin afterward i did all the wipes maybe that explains it...
Odin only says RESET not Passed...
Sent from my GT-I9001 using xda app-developers app
It may sound as im advertising, but what you can try is flashing broodROM RC5 with odin, a bunch of people actually reported that if your stuck in "your" situation, a flash of broodrom goodness can do miracles. I have never experienced such problems but you can always try and flash my rom, if it works again then install stock
broodplank1337 said:
It may sound as im advertising, but what you can try is flashing broodROM RC5 with odin, a bunch of people actually reported that if your stuck in "your" situation, a flash of broodrom goodness can do miracles. I have never experienced such problems but you can always try and flash my rom, if it works again then install stock
Click to expand...
Click to collapse
Okay thanks, im now temp on gigabread+ but i dont really like it.
I want ro flash broodrom but which one is better regarding battery life? Broodrom rc5 or the other edition? Does ot have the same battery life as the stock rom or even better? Because battery is very important to me!
Thanks in advance!
Sent from my GT-I9001 using xda app-developers app
I just installed Broodrom Business edition and the first thing I did was testing if the problem got solved, so I set up a pincode even wrote it down to make sure I dont go paranoid but it still says wrong password and I cant unlock the phone anymore, wiped cache+dalvik cache+data/factory reset and even did a system wipe but still nothing, im using TWRP by the way...
I really hope someone knows how to fix this I really hate the situation im in right now and I really want to know whats causing it...
Flashing ICS ang going back to GB seems a big mistake of me...
Hope you guys can help me!
Sent from my GT-I9001 using xda app-developers app
The best thing you can do is to flash VIA ODIN BroodROM RC5. As brood said, it does miracles.
adrianzowe said:
The best thing you can do is to flash VIA ODIN BroodROM RC5. As brood said, it does miracles.
Click to expand...
Click to collapse
Okay thanks gonna flash it in a hour or so hopefully it does miracles for me
Sent from my GT-I9001 using xda app-developers app
I just flashed Broodrom RC5 and everything went as expected, only Odin didn't say PASSED this time either but it went well luckly.
The phone booted and i set up an lock screen i locked it and it still says pincode wrong! Now i need to wipe date etc to have access again.
This is really pissing me off...
What can i do now?
Where is the lockscreen located? maybe i can access it and change some values or something?
Or can someone thats using Broodrom rc5 give me his framework file or some system files that the lockscreen may be using?
Thanks in advance!
Sorry man. Pin code security comes from you sim card. Changing your system files wont work. You can Buy a new sim card, Try to find puk code or go back to your provider and tell them you lost your puk code.
edit: Oh. I didn't read the OP when i posted this. My bad. Forget what i said
Sent from my GT-I9001 using xda app-developers app
rickvrolings said:
Sorry man. Pin code security comes from you sim card. Changing your system files wont work. You can Buy a new sim card, Try to find puk code or go back to your provider and tell them you lost your puk code.
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
No I mean the lockscreen pin code not my simcard pincode!
failly said:
No I mean the lockscreen pin code not my simcard pincode!
Click to expand...
Click to collapse
Haha. My bad. I read the OP after posting. Sorry. Anyway. I'm not as smart as mister broodplank, But your problem might be solved after installing 2.3.6 via kies... i don't know for sure if this is possible when you allready have 2.3.6. Anyway. Google it and maybe your problem is solved.
Am i right? Could this be a solution brood?
Sent from my GT-I9001 using xda app-developers app
rickvrolings said:
Haha. My bad. I read the OP after posting. Sorry. Anyway. I'm not as smart as mister broodplank, But your problem might be solved after installing 2.3.6 via kies... i don't know for sure if this is possible when you allready have 2.3.6. Anyway. Google it and maybe your problem is solved.
Am i right? Could this be a solution brood?
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
I am now on 2.3.6 and I already wanted to try that but when I connect it to kies is says 'Your device is not supported' or something because I got this firmware file from samfirmware I think.
Is there a way to force update to the firmware Kies was giving?
Btw i noticed when I set a pin screen lock and afterwards I press 'No Screenlock' it doesn't ask for the pin to confirm, and as long as I can remember it did when you wanted to remove the screenlock(back in the days when it was working lol).
Sent from my GT-I9001 using xda app-developers app
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
Hi.
Am using Motorola Milestone (A853) running on Cyanogenmod 7.
Am having a telephony problem since few days and my mobile frequently is having this error and asking for a reboot. Error image is attached below.
I have installed Vulnerable recovery, Open recovery (2nd boot).
When I had this problem, I reinstalled open recovery, wiped dalvic cache, external partition cache but still am getting this error.
Please help me to fix this.
Thank you.
Sent from my Milestone using xda app-developers app
Most of the time it is caused by having the 2.1 BPSW (baseband processor software) instead of the 2.2
I recommend flashing these two files (bpsw and devtree) just to be sure.
Good luck.
I have applied the updates you mentioned. Will check if my mobile if i gives or not the error again. Will post if it is fixed.
Thank you.
Sent from my Milestone using xda app-developers app
Erovia said:
Most of the time it is caused by having the 2.1 BPSW (baseband processor software) instead of the 2.2
I recommend flashing these two files (bpsw and devtree) just to be sure.
Good luck.
Click to expand...
Click to collapse
After flashing those files i didn't had problems for two days. But am again getting the same error. How do I solve it??
Sent from my Milestone using xda app-developers app
Sorry, but I don't have any more information regarding this problem.
( I know this problem occured even with the stock roms, but they rebooted the phone immediately and all unsaved data lost. )
Erovia said:
Sorry, but I don't have any more information regarding this problem.
( I know this problem occured even with the stock roms, but they rebooted the phone immediately and all unsaved data lost. )
Click to expand...
Click to collapse
I think you have installed CM 9.1 in your Milestone!
Can you please give me a feedback about the performance and usage of milestone on CM 9.1!
Thank you
It works great. I'm not saying it is as speedy as on a newer phone, but most of the time its okay. If it slows down, I just restart the phone and the problem is solved.
I recommend you to try it out for yourself. I also recommend to change the stock launcher.
Erovia said:
It works great. I'm not saying it is as speedy as on a newer phone, but most of the time its okay. If it slows down, I just restart the phone and the problem is solved.
I recommend you to try it out for yourself. I also recommend to change the stock launcher.
Click to expand...
Click to collapse
Ya sure I will try once. Thank you for the feedback!