Related
Problem resolved
Just swap it out from where you purchased it don't tell them what you did just say its not booting anymore they will swap it out
Sent from my LG-P925 using XDA App
Or see if you can boot into Recovery Mode, you may be able to do something there.
Yea see if you can boot into recovery and do a hard reset from there bud
Sent from my LG-P925 using Tapatalk
I did a factory reset from recovery but it didn't work.
Where did you get it? You should have 30 days to switch phones
1. To pick a different phone
2. Or to swap from a thrill 4 a thrill
I've alrealy used 2 different phones from bestbuy I'm not sure how many times they allow you to do so I think once so I may be stuck with the thrill which is okay I really want the galaxy 2 tho..
Sent from my LG-P925 using Tapatalk
dincdoes.me said:
Yea see if you can boot into recovery and do a hard reset from there bud
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
this didnt recover mine either.
No big deal. Swapped mine out today. I will hold on to the phone til the GS2 comes out, and then im switching.
ADB isn't recognizing the phone either. I believe I left it in USB Debugging mode before this all happened, but maybe that got reset when I did the factory reset and therefore it isn't enabled anymore.
Isn't the SG2 RELEASING ON SEP 16?
Sent from my LG-P925 using Tapatalk
manske90 said:
ADB isn't recognizing the phone either. I believe I left it in USB Debugging mode before this all happened, but maybe that got reset when I did the factory reset and therefore it isn't enabled anymore.
Click to expand...
Click to collapse
you are correct... any setting you may have altered in your phone is saved in the phone's data partition... the build.prop which im assuming you edited is saved in the system partition.. a factory reset only wipes the data partition, this means the setting you enabled for usb debug is set back to default and the build.prop you edited is left the way you edited it in the system partition completely unaffected... best chance is to wait for a manual CWM
dincdoes.me said:
Isn't the SG2 RELEASING ON SEP 16?
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
There are some rumors that it will be releasing that weekend. A friend at samsung claims that is impossible, the phone is in testing.. but some claim that retailers have told them it will release that weekend
How is it resolved?
Sent from my LG Thrill 4G
I have two bricked thrills and cannot get them in download mode.. I watched the video and am doing everything correct.. Just installs the darn texas instruments USB driver. This suuuucks.
what videos are you talking about. I bricked my thrill as well and it wont cut on at all. I have been looking for some sort of help and cant get any.
How was this solved?What were you doing to brick it?Would like to know incase I get there but it seemed easy enough to flash to few roms Ive tried so far.Thanks
Do you have any info on bricked thrills?
hey
manske90 said:
Problem resolved
Click to expand...
Click to collapse
How did you Brick it? what did you do to fix it? my thrill 4g is bricked, it happend to get bricked while trying to restore a stock rom..
Had some LeWa rom.. the CWM i had was supposed to do an automated Backup of the original OS, But it didn't, and i followed dixtra's flash and it bricked my cell phone.. so im out of a cell phone right now.. which annoys me,
the errors i got.. while trying to do a master reset. were
E; cannot open recovery/log cache,
E; cannot mount recovery/log cache,
i can get to the master recovery menu.. but it just gets a boot loop.
Anyone able to help? Either via Tviewer, or pointing me to a guide that will un brick the piece of crud?
Cyaneyed said:
How did you Brick it? what did you do to fix it? my thrill 4g is bricked, it happend to get bricked while trying to restore a stock rom..
Had some LeWa rom.. the CWM i had was supposed to do an automated Backup of the original OS, But it didn't, and i followed dixtra's flash and it bricked my cell phone.. so im out of a cell phone right now.. which annoys me,
the errors i got.. while trying to do a master reset. were
E; cannot open recovery/log cache,
E; cannot mount recovery/log cache,
i can get to the master recovery menu.. but it just gets a boot loop.
Anyone able to help? Either via Tviewer, or pointing me to a guide that will un brick the piece of crud?
Click to expand...
Click to collapse
Reflash kdz then do factory reset it will fix it
Sent from my LG-P925 using xda app-developers app
Hello,
I have gotten the stock ICS rom from samfirmware.com, Installed using ODIN and it all went green.
However, after restart the touch screen is not working !
I have tried the following:
1. First the Default (XXX) ICS rom
2. Second, the Actual ATT ICS rom
3. Flashed CWM and it is working
4. Then tried AOKP unofficial rom, not starting
No luck so far, any help is much appreciated please.
The touch screen was working after step 3?
Sent from my SAMSUNG-SGH-I727 using xda premium
wamaOnline said:
Hello,
I have gotten the stock ICS rom from samfirmware.com, Installed using ODIN and it all went green.
However, after restart the touch screen is not working !
I have tried the following:
1. First the Default (XXX) ICS rom
2. Second, the Actual ATT ICS rom
3. Flashed CWM and it is working
4. Then tried AOKP unofficial rom, not starting
No luck so far, any help is much appreciated please.
Click to expand...
Click to collapse
Do you know what rom you flashed from Sam mobile?
Sent from my SAMSUNG-SGH-I957
jd1639 said:
Do you know what rom you flashed from Sam mobile?
Sent from my SAMSUNG-SGH-I957
Click to expand...
Click to collapse
First was this one sammobile (dot) com /firmware/?page=3&model=SGH-I957&pcode=XXX&os=1&type=3#firmware[/url]
Then when it didn't work, tried this one
sammobile (dot) com /firmware/?page=3&model=SGH-I957&pcode=ATT&os=1&type=3#firmware
Sorry for the strange URL format, but seems as anew member I don't get to add URLs yet
orlandoxpolice said:
The touch screen was working after step 3?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Sorry, I meant the cwm recovery was flashed correctly and functioning
Btwi tried the fix permissions suggestion from the similar thread but no luck
What version of odin did you use? The roms look ok. If you didn't use ver 1.85 download that and re flash the Rom.
Sent from my SAMSUNG-SGH-I957
jd1639 said:
What version of odin did you use? The roms look ok. If you didn't use ver 1.85 download that and re flash the Rom.
Sent from my SAMSUNG-SGH-I957
Click to expand...
Click to collapse
It is the Odin version I have used,
One more note now, am not sure if that is normal if not.but after the latest flash ( preceded by a data wipe and format ) I can now see zip file I have placed on sdcard but can't access them for flashing and/or ad new zip files from pc
In cwm do a factory reset, wipe and format system and data and then boot. I'm hoping that will solve the problem.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
In cwm do a factory reset, wipe and format system and data and then boot. I'm hoping that will solve the problem.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Tried,booted, "SAMASUNG"screen only ( as expected sicne i formatted the system ), then re-flushed the ATT ICS and same output
Am trying to get a new ROM flashed, but when the device powers up [ without me going through the wizard ], i can't write anything to SD from my PC.
Any info around here about flashing CM or AOKP using ODIN for this I957 ?
Not with Odin that I'm aware of. All are zip files and would go thru cwm. If you get only to the Samsung logo, my experience has been a factory reset usually gets you past that and if that doesn't work flashing the stock rom with Odin does. And I'd flash the honeycomb rom and bring it back to they way I bought it, then upgrade to ics
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Not with Odin that I'm aware of. All are zip files and would go thru cwm. If you get only to the Samsung logo, my experience has been a factory reset usually gets you past that and if that doesn't work flashing the stock rom with Odin does. And I'd flash the honeycomb rom and bring it back to they way I bought it, then upgrade to ics
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Tried the honeycomb step, still same problem
As for Booting to samsung screen .. i did format /system as suggested, so there will be no system to boot to i think
I'm at a loss, you've tried everything that has gotten me beyond the boot screen.
Anyone else have any ideas?
Sent from my SGH-I727
wamaOnline said:
Tried the honeycomb step, still same problem
As for Booting to samsung screen .. i did format /system as suggested, so there will be no system to boot to i think
Click to expand...
Click to collapse
I should mention something that has gotten me worried, i flashed a TWRP recovery to check if the touch would work there, but it didn't.
Not sure if i should be worried about HW now, or try another TWRP for instance? Or perhaps TWRP shares another flawed tab wide configuration with the Android image ?
It's not twrp, I use it on my tab and it Works fine. If you were the only one who has this problem I'd say hardware for sure. But at least one other person has the same problem after updating to ics. It seems like there something with the firmware interfacing with the touch screen.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
It's not twrp, I use it on my tab and it Works fine. If you were the only one who has this problem I'd say hardware for sure. But at least one other person has the same problem after updating to ics. It seems like there something with the firmware interfacing with the touch screen.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Then why is it still borked when reverting to hc?
Sent from my SAMSUNG-SGH-I727 using xda premium
Good question. One of the guys couldn't get the touch screen to work in twrp either. It sounds like a hardware issue but to have a few guys have the same problem after installing ics? I don't know? Something's doing it which I can't figure out
jd1639 said:
Good question. One of the guys couldn't get the touch screen to work in twrp either. It sounds like a hardware issue but to have a few guys have the same problem after installing ics? I don't know? Something's doing it which I can't figure out
Click to expand...
Click to collapse
yea i dont get how a rom flash could cause a hardware issue
orlandoxpolice said:
yea i dont get how a rom flash could cause a hardware issue
Click to expand...
Click to collapse
Think the other colleague did say he found someone elsewhere who resolved the problem by reverting to an older backup he had, which gives me hope that this is no hw issue
And this was my first time to flash any ROM without a backup first, thought a stock update would be fine !!
Can I use adb for instance to verify if it was a hardware issue,if so then any help is appreciated
wamaOnline said:
Think the other colleague did say he found someone elsewhere who resolved the problem by reverting to an older backup he had, which gives me hope that this is no hw issue
And this was my first time to flash any ROM without a backup first, thought a stock update would be fine !!
Can I use adb for instance to verify if it was a hardware issue,if so then any help is appreciated
Click to expand...
Click to collapse
Got it Reassembled and cleaned it and it worked
same prob, touchscreen not responding
wamaOnline said:
Got it Reassembled and cleaned it and it worked
Click to expand...
Click to collapse
I'm having this issue of the touchscreen not responding on my s2 now
You say you got it reassembled? What did you have to do to repair it
any help greatly appreciated
I have JB 4.1.2 and cwm 9.1 flashed
after reboot screen comes on but won't respond to touch, I can only access download and recobvery screens
I also have the phone not showing on computer when usb attached but am loading rom etc to ext sd card first and installing them from cwm
Got the maintenance center to disassemble it, clean the pins and reconnect the screen and then it worked
Sent from my LT26ii using xda app-developers app
I recently purchased a boinic because of a cracked screen, when i picked it up it would only go into ap fastboot. i replaced screen and i have tried all fxz files with rsd and all fail at step 6 except .246 ics. that loads all the way up except the radio install fails when it is recovery. phone still boots up but it wont read my sim and reboots after 5 mins or so. any help would be greatly appreciated. i even tried updating via stock recovery with the blur files and they go until installing bp and then fail. i dont know any other history on the phone, i have installed rsd 5.7 motorola device manager 2.3.4.. any suggestions on where to go from here. ive been thru most forums, and googled it for the last 2 days. evry thing that ive tried has not worked.
or where can i find the radio files that i can flash fron stock recovery
reg442 said:
I recently purchased a boinic because of a cracked screen, when i picked it up it would only go into ap fastboot. i replaced screen and i have tried all fxz files with rsd and all fail at step 6 except .246 ics. that loads all the way up except the radio install fails when it is recovery. phone still boots up but it wont read my sim and reboots after 5 mins or so. any help would be greatly appreciated. i even tried updating via stock recovery with the blur files and they go until installing bp and then fail. i dont know any other history on the phone, i have installed rsd 5.7 motorola device manager 2.3.4.. any suggestions on where to go from here. ive been thru most forums, and googled it for the last 2 days. evry thing that ive tried has not worked.
or where can i find the radio files that i can flash fron stock recovery
Click to expand...
Click to collapse
Have you tried the House of Bionic method?http://www.droidrzr.com/index.php/topic/5764-samurihls-house-of-bionic/
Yes I did and I tried the radio fix as well still no go..
Sent from my ADR6425LVW using xda app-developers app
The same exact issue
reg442 said:
Yes I did and I tried the radio fix as well still no go..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I have the exact same issue. Any help from anyone out there in the forum would be great.
I have the problem where it uncompressed and then when it starts flashing it fails in like 10 seconds. Help!
Sent from my DROID BIONIC 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!