Was on Stock 4.1.2 Jellybean.
I Rooted the phone. (Successful)
I flashed the WRONG Clockworkmod Recovery(It was for Galaxy Note II, I think. (cwm6-recovery-i317.tar) instead of this recovery-cwmtouch-6.0.2.7-GTI9300.
Now, everything (it boots, buttons work) works fine except the touchscreen wont respond. So Im stuck on the setup screen (language selection).
Tried a fresh install of stock ROM. I even tried to recover from my old Cyanogen backup and it flashes fine. But the screen is still unresponsive.
Can anyone help? Thanks for any answer. And sorry if this is an old story to you. Im new here. Good day.
My Phone: Samsung Galaxy S3 International Version
Get the flash counter reset and flash the stock ROM. Digitiser on note 2 needs higher voltage so note 2 recovery gives it more. You've blown your digitiser and it needs to be replaced
Sent from my GT-I9300 using Tapatalk 2
Well, i have the same problem
noobjob said:
Was on Stock 4.1.2 Jellybean.
I Rooted the phone. (Successful)
I flashed the WRONG Clockworkmod Recovery(It was for Galaxy Note II, I think. (cwm6-recovery-i317.tar) instead of this recovery-cwmtouch-6.0.2.7-GTI9300.
Now, everything (it boots, buttons work) works fine except the touchscreen wont respond. So Im stuck on the setup screen (language selection).
Tried a fresh install of stock ROM. I even tried to recover from my old Cyanogen backup and it flashes fine. But the screen is still unresponsive.
Can anyone help? Thanks for any answer. And sorry if this is an old story to you. Im new here. Good day.
My Phone: Samsung Galaxy S3 International Version
Click to expand...
Click to collapse
How did you solve it??
trocaderos said:
How did you solve it??
Click to expand...
Click to collapse
Read rootSU post ... note 2 digitizer takes more voltage ... he burn his digitizer.
I advice to get a otg cable conect a mouse reser counter flash stock and take it to service center.
Just say one day youre playing almost an hour straight and it stopped suddenly ...
Maybe it passes.
Take care
Sent From My Galaxy S III Using XDA Premium 4
Do I need to replace the LCD too or just the Digitizer?
Hi. I mistakenly installed a wrong ROM on to my samsung galaxy s3 after that the touch screen was not responsive. I restored the Stock ROM but the problem persists. After googling i found I need to swap the digitizer. Does it need LCD replacement too or not?
Any help would be much appreciated.
Thanks
Regards
Adeel
U overvolted the touch chip controller.
U probably need all screen replaced
Enviado do meu GT-I9300 através de Tapatalk
Related
HELP!!!!
I rooted my Galaxy NOTE and installed clockworkmod. I soft booted into recovery mode once and now NOTHING I do (take the battery out, rebooting the phone from clockworkrecovery, etc) works! I just got this phone TODAY and I am desperate to get it working again. Any help would be greatly appreciated
vintshave said:
HELP!!!!
I rooted my Galaxy Touch and installed clockworkmod. I soft booted into recovery mode once and now NOTHING I do (take the battery out, rebooting the phone from clockworkrecovery, etc) works! I just got this phone TODAY and I am desperate to get it working again. Any help would be greatly appreciated
Click to expand...
Click to collapse
whats a galaxy touch?
vintshave said:
HELP!!!!
I rooted my Galaxy Touch and installed clockworkmod. I soft booted into recovery mode once and now NOTHING I do (take the battery out, rebooting the phone from clockworkrecovery, etc) works! I just got this phone TODAY and I am desperate to get it working again. Any help would be greatly appreciated
Click to expand...
Click to collapse
i hope you didnt come to the wrong model forums.
If u ment galaxy note lol odin back to stock recovery its in the dev section. That should get u booting to system
Sent from my SAMSUNG-SGH-I717 using XDA App
BLOWNCO said:
whats a galaxy touch?
Click to expand...
Click to collapse
mybad....GALAXY NOTE
u921333 said:
If u ment galaxy note lol odin back to stock recovery its in the dev section. That should get u booting to system
Sent from my SAMSUNG-SGH-I717 using XDA App
Click to expand...
Click to collapse
Thanks! I got a nice stock file from Da_G (Da Man!). Now like a lemming jumping off a cliff again, I want to re-root it. What would you suggest as the best way to do it and how would I avoid the same "sh*t" with clcokworkmod?
I just odin'd the rooted overclocked kernel to do root. Booted completely up then went back in download mode and odin'd cwm... Im on beta 2 not 3. .. Havent read if there is any issues on 3 that may have caused it.
Sent from my SAMSUNG-SGH-I717 using XDA App
u921333 said:
I just odin'd the rooted overclocked kernel to do root. Booted completely up then went back in download mode and odin'd cwm... Im on beta 2 not 3. .. Havent read if there is any issues on 3 that may have caused it.
Sent from my SAMSUNG-SGH-I717 using XDA App
Click to expand...
Click to collapse
Do you have a link to the Kernel that you rooted and instructions? I'm on android 2.3.6 kernel 2.6.35.11, build GINGERBREAD.UCLA1.
Damn! How can they justify installing Gingerbread in 2012 with ICS out and working?!
product code?
vintshave said:
Thanks! I got a nice stock file from Da_G (Da Man!). Now like a lemming jumping off a cliff again, I want to re-root it. What would you suggest as the best way to do it and how would I avoid the same "sh*t" with clcokworkmod?
Click to expand...
Click to collapse
Hi vintshave;
I'm having the exact same CWM bootloop issue and it looks like I need to do the same thing you did. I'm trying to download the stock rom (using check FUS) but I'm not sure what the Product Code is? It says to dial a number to get the product code but that's not an option right now obviously. Is it on the back somewhere?
If you got it somewhere else, can you let me know?
Thanks a lot!
---------- Post added at 05:10 PM ---------- Previous post was at 04:39 PM ----------
Whoops; ignore me. I just loaded and flashed the beta 3 CWM and all is well again; tiny text, but all good. Thanks to snovvman for posting the link to the newer recovery:
http://forum.xda-developers.com/showpost.php?p=23207501&postcount=2
CWR3 runs just fine for me , no problems yet ,, i think if you are haveing boot loop problems you did something wrong , do a search in the developers forum and look for att recovery ,
use oden and flash back to facotry and if all is well start over ,, its not hard i am new at this ,, about a week or two now and i have
root
blue battery mod
over clock ker
CWR 3
custom rom
just read every thing first befor you try to flash , read the hole post to see if there are any problems with said mod befor you just flash away
good luck
Hello, I have had a Samsung Galaxy S II LTE from Rogers for three months now and it suddenly stopped working after trying to make a phone call.
The firmware was the Gingerbread 2.3.6 I believe (The most current firmware before ICS for the SGH-I727R)
There has been a history of attemping to install Cyanogenmod 10, but I had Clockwork Recovery installed and I was never able to install Cyanogenmod 10 because it gave me errors.
So I used Odin and an official release from Rogers to restore back to Gingerbread.
A month later, this is where I am at.
Status:
I can boot as far as the Carrier logo before going blank and vibrating every 2 - 3 seconds
I can go into download and recovery mode for 5 seconds before being met with a quick flash of a blue screen.
The phone randomly vibrates when a battery is inserted, when it is being charged, or a combination of the two
The battery needs to be taken out and placed back in before attempting a normal, download or recovery boot.
I also do not know if Samsung can tell, as there is no Clockwork Mod or any left over roms or Superuser permissions.
What should I do? Thanks!
xbladeinc said:
Hello, I have had a Samsung Galaxy S II LTE from Rogers for three months now and it suddenly stopped working after trying to make a phone call.
The firmware was the Gingerbread 2.3.6 I believe (The most current firmware before ICS for the SGH-I727R)
There has been a history of attemping to install Cyanogenmod 10, but I had Clockwork Recovery installed and I was never able to install Cyanogenmod 10 because it gave me errors.
So I used Odin and an official release from Rogers to restore back to Gingerbread.
A month later, this is where I am at.
Status:
I can boot as far as the Carrier logo before going blank and vibrating every 2 - 3 seconds
I can go into download and recovery mode for 5 seconds before being met with a quick flash of a blue screen.
The phone randomly vibrates when a battery is inserted, when it is being charged, or a combination of the two
The battery needs to be taken out and placed back in before attempting a normal, download or recovery boot.
I also do not know if Samsung can tell, as there is no Clockwork Mod or any left over roms or Superuser permissions.
What should I do? Thanks!
Click to expand...
Click to collapse
You can start by going to your own section.
Sent from Team Pirate! Using Tapatalk 2
Nick281051 said:
You can start by going to your own section.
Sent from Team Pirate! Using Tapatalk 2
Click to expand...
Click to collapse
There is no known section for the Samsung Galaxy S II LTE for Rogers, only the Samsung Galaxy S II Skyrocket for AT&T.
If I am wrong, please let me know.
xbladeinc said:
There is no known section for the Samsung Galaxy S II LTE for Rogers, only the Samsung Galaxy S II Skyrocket for AT&T.
If I am wrong, please let me know.
Click to expand...
Click to collapse
Correct, but except for the 'R', maybe everything is the same? In any case, you need to ask in the Skyrocket forum, they may be able to point you in the right direction. You won't get much help here.
xbladeinc said:
There is no known section for the Samsung Galaxy S II LTE for Rogers, only the Samsung Galaxy S II Skyrocket for AT&T.
If I am wrong, please let me know.
Click to expand...
Click to collapse
You are wrong. They are the same phone.
Sent from Team Pirate! Using Tapatalk 2
Thread closed
4 months ago i've rooted my Galaxy S3 international (I-9300). Before rooting i took a nandroid backup of the Samsung's ICS. Then i flashed CM10 and recently (1 month ago) i flashed CM10.1. Everything was working OK (except some issues that come with the CM10-10.1). I also came against the SOD (Screen of Death) but as the devs warned us i was OK with that. From time to time i flashed a newer version of the CM10.1 nightly (recent one was 4th of Jan 2013).
Today as i was sitting in my office i picked up my device and pressed the power button just to check the time. The device did not respond and i presumed that it was another case of SOD. So i removed my battery and put it back inside as i always did when a SOD occured. I long-pressed the power button but nothing happened. I went to the nearest Samsung supplier and i bought a brand new Samsung battery to replace the old one but the device never powered up. Now i am stack with a device that cannot power up. I cannot get into download mode as well.
Is it a case of a bricked device? If it is, is there anything i can do to bring it back to life?
Thanks in advance!
In this case you cannot do much....take it to center and require motherboard replacement, if its case of brickbug it will he warranty covered....right now im interested if you flashed XXELLA or newer bootloader or did you flash kernel compiled from 7th source from samsung?
Sent from my GT-I9300 using xda app-developers app
tsangaris said:
4 months ago i've rooted my Galaxy S3 international (I-9300). Before rooting i took a nandroid backup of the Samsung's ICS. Then i flashed CM10 and recently (1 month ago) i flashed CM10.1. Everything was working OK (except some issues that come with the CM10-10.1). I also came against the SOD (Screen of Death) but as the devs warned us i was OK with that. From time to time i flashed a newer version of the CM10.1 nightly (recent one was 4th of Jan 2013).
Today as i was sitting in my office i picked up my device and pressed the power button just to check the time. The device did not respond and i presumed that it was another case of SOD. So i removed my battery and put it back inside as i always did when a SOD occured. I long-pressed the power button but nothing happened. I went to the nearest Samsung supplier and i bought a brand new Samsung battery to replace the old one but the device never powered up. Now i am stack with a device that cannot power up. I cannot get into download mode as well.
Is it a case of a bricked device? If it is, is there anything i can do to bring it back to life?
Thanks in advance!
Click to expand...
Click to collapse
Sudden death, all you can do is get a motherboard replacement at a service center, however they may never know you flashed CM10.1 because the NAND is dead.
gaspernemec said:
In this case you cannot do much....take it to center and require motherboard replacement, if its case of brickbug it will he warranty covered....right now im interested if you flashed XXELLA or newer bootloader or did you flash kernel compiled from 7th source from samsung?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick reply but i am not sure i can help you with the bootloader! I am not an advanced user. I just used Odin v3.04 to flash CF-Root-SGS3-v6.4. When i finally rooted my device i downloaded the CM10 and afterwards the CM10.1 rom and flashed it along with the GAPPS. And then i used a program to match the modem with the RIL (XXDLID). Ofcourse i fixed permissions.
One thing i need to know? Does the phone stays in the warranty if you root it?
delsus said:
Sudden death, all you can do is get a motherboard replacement at a service center, however they may never know you flashed CM10.1 because the NAND is dead.
Click to expand...
Click to collapse
You mean that i shouldnt say anything about root and CM10.1 right?
Also, is there a way for the technicians to find out that i've rooted the device and flashed CM10.1? I mean on a device that it cant even power on!
ps: i live in Cyprus (small island in the meditteranean sea) , so there isnt any advanced service center to examine my motherboard (at least i hope so).
tsangaris said:
You mean that i shouldnt say anything about root and CM10.1 right?
Also, is there a way for the technicians to find out that i've rooted the device and flashed CM10.1? I mean on a device that it cant even power on!
ps: i live in Cyprus (small island in the meditteranean sea) , so there isnt any advanced service center to examine my motherboard (at least i hope so).
Click to expand...
Click to collapse
Don't mention it, don't say anything about firmware, if they ask play dumb and just say the latest version, it's up to them to prove your warranty is void, also is Cyprus in the EU? If so check this out http://forum.xda-developers.com/showthread.php?t=2092530&highlight=eu
In short for your warranty to be voided by flashing Samsung has to prove that it was CM10.1 that caused the problem.
I don't think this will be needed though because your NAND is completely dead so it will be extremely hard if possible for them to prove you flashed anything.
delsus said:
Don't mention it, don't say anything about firmware, if they ask play dumb and just say the latest version, it's up to them to prove your warranty is void, also is Cyprus in the EU? If so check this out http://forum.xda-developers.com/showthread.php?t=2092530&highlight=eu
In short for your warranty to be voided by flashing Samsung has to prove that it was CM10.1 that caused the problem.
I don't think this will be needed though because your NAND is completely dead so it will be extremely hard if possible for them to prove you flashed anything.
Click to expand...
Click to collapse
Yes Cyprus belongs to EU.
I will not mention a thing about firmware and CM hoping they dont find it out.
In the meantime, if they replace the motherboard, i will be running Android with Touchwiz by default?
tsangaris said:
Yes Cyprus belongs to EU.
I will not mention a thing about firmware and CM hoping they dont find it out.
In the meantime, if they replace the motherboard, i will be running Android with Touchwiz by default?
Click to expand...
Click to collapse
Yes you will be on touchwiz, but you can always change that
I have no idea which version though, it depends what they flash at the factory.
delsus said:
Yes you will be on touchwiz, but you can always change that
I have no idea which version though, it depends what they flash at the factory.
Click to expand...
Click to collapse
Samsung should worry about their skin, because i am a user that rooted his device to flash a custom ROM, then the device is not booting by any means and i am thinking to root it again after the motherboard is replaced!!
By the way, the problem on the motherboard is caused 100% because i root the device??
Thanks so much for your answers!
tsangaris said:
Samsung should worry about their skin, because i am a user that rooted his device to flash a custom ROM, then the device is not booting by any means and i am thinking to root it again after the motherboard is replaced!!
By the way, the problem on the motherboard is caused 100% because i root the device??
Thanks so much for your answers!
Click to expand...
Click to collapse
No it is not caused by rooting your device. Your case is a typical Sudden Death Syndrome one. For more info go here:
http://forum.xda-developers.com/showthread.php?t=2091045
You said that the last CM 10.1 you installed was from 04.01.13? Well in that case the Samsung Update7 source wasn`t applied yet to CM10.1 Kernel, so the Kernel was not secure.
Scarface1991 said:
No it is not caused by rooting your device. Your case is a typical Sudden Death Syndrome one. For more info go here:
http://forum.xda-developers.com/showthread.php?t=2091045
You said that the last CM 10.1 you installed was from 04.01.13? Well in that case the Samsung Update7 source wasn`t applied yet to CM10.1 Kernel, so the Kernel was not secure.
Click to expand...
Click to collapse
I didnt find the time to read the thread you post (i am reading it later on). So the not secure Kernel could cause this?
tsangaris said:
I didnt find the time to read the thread you post (i am reading it later on). So the not secure Kernel could cause this?
Click to expand...
Click to collapse
Yes there is a problem with a specific type of eMMC chips in the SIII. There is plenty of evidence now that Samsung fixed this issue with the Update7 Source release and most S3 Kernels have this fix by now. You can read it in detail by clicking the link I posted a couple of posts ago.
I hope that they will repair your device without any problems but they should and if you couldn`t even access download mode it`s pretty much impossible to find out that you had Root or a custom ROM installed.
tsangaris said:
I didnt find the time to read the thread you post (i am reading it later on). So the not secure Kernel could cause this?
Click to expand...
Click to collapse
Some people are saying that the kernel fixes it some are saying they havent, but the service center should fix it because its a known problem.
Also the latest kernel has only been rolled out in UK and Spain. If there has not been a stock update available in your country there is really nothing they can do.
Sent from my GT-I9300 using xda premium
delsus said:
Some people are saying that the kernel fixes it some are saying they havent, but the service center should fix it because its a known problem.
Also the latest kernel has only been rolled out in UK and Spain. If there has not been a stock update available in your country there is really nothing they can do.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I don`t know of any case where someone had an SD while having a fixed Kernel installed. But you are right that nobody knows 100% if the fix really works.
Thank you all for your responses!! I am taking my GS3 to the place that i bought it for repairing first thing tomorrow!
I will let you know of the outcome!
Again, thanks a lot!!
tsangaris said:
Thank you all for your responses!! I am taking my GS3 to the place that i bought it for repairing first thing tomorrow!
I will let you know of the outcome!
Again, thanks a lot!!
Click to expand...
Click to collapse
Good luck
Hey guys,
I have a similar problem except that my screen turns on and shows the Galaxy S3 logo when I try to power it on but it won't go further (shows logo until I pull the battery). It doesn't boot into recovery either but I can start download mode.
The phone just turned off while I was listening to music. I think I was running Omega v27.
So my question is: Should I try flash a stock ROM since I can boot into download mode? And is this even "sudden death"?
Thanks in advance!
Half of sudden death. You should also get the phone to samsung
avrano1 said:
Hey guys,
I have a similar problem except that my screen turns on and shows the Galaxy S3 logo when I try to power it on but it won't go further (shows logo until I pull the battery). It doesn't boot into recovery either but I can start download mode.
The phone just turned off while I was listening to music. I think I was running Omega v27.
So my question is: Should I try flash a stock ROM since I can boot into download mode? And is this even "sudden death"?
Thanks in advance!
Click to expand...
Click to collapse
I would take that to samsung, toy could try flashing stock but if it wasn't a failure flashing something I'm not sure it would work.
I would imagine it will fail before it tries to flash.
Sent from my GT-I9300 using xda premium
vasp3690 said:
Half of sudden death. You should also get the phone to samsung
Click to expand...
Click to collapse
Tried to flash the + RESCUE FIRMWARE SGSIII I9300 + but it doesn't work. It can't flash the .pit-file and it doesn't work without either.
So I really have to return it but:
since the phone boots into download mode they will see that I used a custom firmware. Any chance to change this?
I flashed my s3 more than 20 times so far and everything was ok since last night when it turns on normaly but when he came to choose country and language I noticed that my touch screen dont work, than I flashed official samsung rom via odin of course and flashing was ok but touchscreen still the same! I flashed several time with official rom but same thing every time! Pleese help I dont have contract so can any1 tell me is this software problem or hadware! If you know how to fix it I would be very thankfull....
so you used a root package for the note 2? you've fried the digitizer
Glebun said:
so you used a root package for the note 2? you've fried the digitizer
Click to expand...
Click to collapse
I used always the same routine like previous times, so no other option besides changing whole screen?
what file did you flash?
Glebun said:
what file did you flash?
Click to expand...
Click to collapse
For about 5 months i´ve got omega jelly bean v40, than i want to check new 4.2.2 and didnt love it so i want to bring back omega and there i got this problem than i flashed stock several times with same results!
but you said it happened after rooting, and now you're saying it happened after flashing omega
No one can help unless you give accurate information. Start from the top. List every step you took and every file you used to get from a working state to the broken state you're in now
Tell us what rom you were on when working and if rooted. Whole thread is confusing
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
No one can help unless you give accurate information. Start from the top. List every step you took and every file you used to get from a working state to the broken state you're in now
Tell us what rom you were on when working and if rooted. Whole thread is confusing
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
My mistake, so:
1. My phone was rooted long time ago
2. I use omega jelly bean v40 from begining, i tryed others but always returned on omega with no problem
3 . this time I started with flashing JB 4.2.2 official from sammobile, and i done it normaly
4. i wanted still to return on omega like many times so far, and i just flashed omega, and on screen startup when there is chosing language and country i noticed my touch screen dont work
5. than i tryed to flash stock ics and everything was ok but same problem touch screen wont work
6. I tryed several time with same results
7. man who fix phones told me that i need to replace touch and screen, it will make burn hole in my pocket :crying:
Did the touchscreen work in the leak?
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
Did the touchscreen work in the leak?
Sent from my GT-I9300 using Tapatalk 2[/
I dont understand what do you mean, it work normally before flashing and after it not responds, volume, off/on, home, back and options buttons works just touchscreen dont!
Click to expand...
Click to collapse
JB 4.2.2 from Samsung is a leak firmware. He's asking if it worked then
Glebun said:
JB 4.2.2 from Samsung is a leak firmware. He's asking if it worked then
Click to expand...
Click to collapse
Yes it worked normally for 5 days!
Edit > nevermind.
Dunno what youve done then. Better send it for repair
I have problems flashing Roms I dont know what could be the reason. Couple days ago my SD card died I bought a new one I tried to flash the new version of Tweaked I forgot to made a back up and for some reason my phone will get stuck on the "Galaxy note 2" screen or return to the TWRP menu I tried to flash at least 5 different roms and same results the only one It was able to boot was Clean rom 3.1. I updated TWRP to the latest version and still having the same issues if any one can tell me what to do I will appreciate it
Sent from my SCH-I605 using xda app-developers app
You do know first boots take a while right? You should wait up to or at least 10 minutes for the first boot of a rom.
AldenIsRad said:
You do know first boots take a while right? You should wait up to or at least 10 minutes for the first boot of a rom.
Click to expand...
Click to collapse
I'll try again when I get home. Thanks
Sent from my SCH-I605 using xda app-developers app
I'm actually having a similar, if more limited, problem. I recently tried flashing P.A.C. rom onto my Note 2, but it would just hang on the galaxy note 2 screen. I left it for more than 10 minutes without change. However, after that I tried flashing Cyanogen; which worked just fine.
I'd greatly appreciate any tips on how to figure out what's going wrong.
Epsilon Rose said:
I'm actually having a similar, if more limited, problem. I recently tried flashing P.A.C. rom onto my Note 2, but it would just hang on the galaxy note 2 screen. I left it for more than 10 minutes without change. However, after that I tried flashing Cyanogen; which worked just fine.
I'd greatly appreciate any tips on how to figure out what's going wrong.
Click to expand...
Click to collapse
I never had these issues flashing roms except for one I might try with CWR
Sent from my SCH-I605 using xda app-developers app
killa408shark said:
I never had these issues flashing roms except for one I might try with CWR
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Huh? Did I misinterpret something?
In the op you said:
for some reason my phone will get stuck on the "Galaxy note 2" screen or return to the TWRP menu I tried to flash at least 5 different roms and same results the only one It was able to boot was Clean rom 3.1.
Click to expand...
Click to collapse
Which seemed pretty similar.
Epsilon Rose said:
Huh? Did I misinterpret something?
In the op you said:
Which seemed pretty similar.
Click to expand...
Click to collapse
Before I never had issues till a couple days ago. Like you i waited for more than 10 minutes and never booted up
Sent from my Transformer TF101 using xda app-developers app
And now it works.
So, I seem to actually have things working now and I figured I should give a quick update.
Before, I was using a nightly of P.A.C. rom, because I didn't see anything more stable at the time. Now I've switched to a milestone rom and it boots just fine. At this point, I think I'd pin the blame on a glitch the rom I was trying to flash; given the fact that Cyanogen and the current iteration work fine
Hello . iam having issues , after flashing a rom for my htc one m7 , s-On , after flashing it . stupid cos i had mybe to change to S-Off, anyway the phone now stuck on the welcome page from the new ROM , and i get on display a message "Unfortunately ,Google Text-to speech Engine has stopped , i cant though press anything . . i try to get in to recovery but cant . now in the left corner says Safe mode . Very frustrated ... any advice=? iam a mac owner but i could use my moms .
i got a few days before i go abroad and i would preffer having the phone with me .. .. i dont know what to do .
i try to find some info here .. maybe if some one knows that there is some info here sent me the link?
marjanna said:
Hello . iam having issues , after flashing a rom for my htc one m7 , s-On , after flashing it . stupid cos i had mybe to change to S-Off, anyway the phone now stuck on the welcome page from the new ROM , and i get on display a message "Unfortunately ,Google Text-to speech Engine has stopped , i cant though press anything . . i try to get in to recovery but cant . now in the left corner says Safe mode . Very frustrated ... any advice=? iam a mac owner but i could use my moms .
i got a few days before i go abroad and i would preffer having the phone with me .. .. i dont know what to do .
i try to find some info here .. maybe if some one knows that there is some info here sent me the link?
Click to expand...
Click to collapse
Sorry to say this is the verizon note ii q&a. I'm not even sure which HTC one m7 variant you have to point you to the correct forum.
MunkinDrunky said:
Sorry to say this is the verizon note ii q&a. I'm not even sure which HTC one m7 variant you have to point you to the correct forum.
Click to expand...
Click to collapse
Edited: Thanks i found it and i fixed the problem .