Develop Bugs

USB Debugging not accessible

Hi
I was flashing back to Stock from task650 to fix my gps. Well something blew up and when the phone reboots the screen goes black but I hear the AT&T start-up tune. Essentially I can't get to enable USB debugging to reflash. I can get to download or recovery, but there are no files to recover<?> and busybox never got installed.
What do I do now?

Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.

CZ Eddie said:
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
Click to expand...
Click to collapse
Yes I have stock recovery. Odin is of no use because it hangs waiting for the USB debug to respond. And i can't turn it on because the screen is black and I can't navigate

Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release

xBeerdroiDx said:
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
Click to expand...
Click to collapse
Thanks. I created an emergency tool kit on an SD, I wiped data, wiped cache and Davlik and formated system. Flashed the stock rom. When I rebooted it now hung at the Samsung Galaxy S III screen.
How do I get out of this mess?

Try wiping data and cache again in recovery

xBeerdroiDx said:
Try wiping data and cache again in recovery
Click to expand...
Click to collapse
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.

BertMor said:
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
Click to expand...
Click to collapse
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.

xBeerdroiDx said:
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
Click to expand...
Click to collapse
When it rains it pours. Now I can't get into recovery. I get the empty battery graphic cycling on and off, and its very warm to the touch. I think the battery is not charging.
I tried using Odin and flashed a stock rom but I kept getting verification errors and status 7 errors. Things just are not taking. I fear I've got a hard brick and I don't know what to do to fix it.
I appreciate your help

aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?

xBeerdroiDx said:
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
Click to expand...
Click to collapse
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery

it might indeed be drained. leave it plugged in for a while and report back.
you were getting the error/status 7 messages after you flashed cwm back on it likely because the cwm wasnt up-to-date.
what was the last thing you tried before it stopped working altogether?

It gets really hot if I leave it plugged in. But it seems like I can get into recovery again. The last thing I flashed was CMW 6.0.3.1. But what is on it now is CMW 5.5.0.4

actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.

BertMor said:
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
Click to expand...
Click to collapse
xBeerdroiDx said:
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
Click to expand...
Click to collapse
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide

BertMor said:
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
Click to expand...
Click to collapse
Well I think I managed it!. First I tried to install an update d/l'ed from Dropbox and that did nothing. Then I flashed an old .tar that was a rooted stock and it rebooted!
I tried editing the updater-script but I couldn't getit to save the changes properly.
Well I will now re flash the RM and CWM and hope for the best
Thanks for all your help, greatly appreciated

Stuck in bootloop

I had decided to upgrade my cm10 to the latest version so I went into twrp recovery backup it up wiped data, system, cache, dalvik cache, then I installed the rom and gapps and whiped cach and dalvik. Now im rebooting and im stuck in the first cm10 bootscreen with the samung galaxy s3 text an the cm10 alien dude. I tried restoring my twrp backup and it failed.
What do i do with formatting data? I tried installing older cm10 rom version I got on my phone and none worked and for some reason i cant see my sd card when i mount it through twrp
Help!

re: bootloop
genardas said:
I had decided to upgrade my cm10 to the latest version so I went into twrp recovery backup it up wiped data, system, cache, dalvik cache, then I installed the rom and gapps and whiped cach and dalvik. Now im rebooting and im stuck in the first cm10 bootscreen with the samung galaxy s3 text an the cm10 alien dude. I tried restoring my twrp backup and it failed.
What do i do with formatting data? I tried installing older cm10 rom version I got on my phone and none worked and for some reason i cant see my sd card when i mount it through twrp
Help!
Click to expand...
Click to collapse
Have you tried this? - It should work every time.
Here is the step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you have purchased it except with the benifit of being rooted.
Download the stock-rooted T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Here is a link for ODIN which is required for flashing the stock rooted firmware (a windows app) http://d-h.st/Q14
Download and extract Odin into the same folder you made containing the TAR file.
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!

Sometimes it can take a while to get past that screen the first time you turn it on with a new ROM (like, 5+ minutes) - how long did you wait ?

Wow. What a crazy 24 hrs. My S3 kicked out a couple hiccups yesterday. Gave me a gapps error and then one other I don't remember. I decided to just reboot to restore everything. Phone would not boot past boot screen. Crazy. I could get into recovery. Tried to restore from backup. Nope. Stuck at boot screen. Odin back to stock w/root. Nope. Odin back to stock. Nope. Ended up Odin to stock. Boot into recovery. *Wipe data and factory reset 3 times*. It then completed a boot. FINALLY!!! OMG. Such a bizarre fluke. I am back on rooted Wicked 9.1 thanks to a backup. I searched various forums and threads on here. I tried the above procedure. (It was actually the first thing I did and what I used as a guide.) It wasn't until I did the Odin, boot into recovery and wipe data 3 times that my phone would completely boot up fully.

radar9 said:
Wow. What a crazy 24 hrs. My S3 kicked out a couple hiccups yesterday. Gave me a gapps error and then one other I don't remember. I decided to just reboot to restore everything. Phone would not boot past boot screen. Crazy. I could get into recovery. Tried to restore from backup. Nope. Stuck at boot screen. Odin back to stock w/root. Nope. Odin back to stock. Nope. Ended up Odin to stock. Boot into recovery. *Wipe data and factory reset 3 times*. It then completed a boot. FINALLY!!! OMG. Such a bizarre fluke. I am back on rooted Wicked 9.1 thanks to a backup. I searched various forums and threads on here. I tried the above procedure. (It was actually the first thing I did and what I used as a guide.) It wasn't until I did the Odin, boot into recovery and wipe data 3 times that my phone would completely boot up fully.
Click to expand...
Click to collapse
Could have saved yourself hours by doing a factory reset.

Yeah guys I restored it thorugh odin and then went into the stock recovery like an idiot and being used to the twrp recovery clicked wipe data/factory reset thinking it would reset the rom and I lost everything. Well really only lost music buts its k. Now im back on stock but I might have to root again DDD

genardas said:
Yeah guys I restored it thorugh odin and then went into the stock recovery like an idiot and being used to the twrp recovery clicked wipe data/factory reset thinking it would reset the rom and I lost everything. Well really only lost music buts its k. Now im back on stock but I might have to root again DDD
Click to expand...
Click to collapse
Next time you should keep stock rom and kernel on your sdcard so that if anything goes wrong you could flash that, usually it might fix the bootloop. When installing a JB rom, be sure that you have a kernel that is compatible with JB. If not, you could enter a bootloop. Also, BACKUP EFS.

[Q] wiping cache and dalvik caused boot loop?

my s2 was being glitchy so i went into recovery to wipe cache and dalvik and then rebooted from recovery. i waited and then it just boooot loops and shuts off. im currently using cwm recovery 5.2.7 or something like that. will i be able to flash the newer roms like CyanogenMod 10.2 with that current recovery? and why did the wiping of cache and dalvik booot looped my phone? i thought wiping those just makes my phone less glitchy

You probably had some other issues to cause phone to be glitchy in the first place.
When flashing a new ROM it's recommend you wipe data, system cache and dalvik cache.(cache and dalvik can be wipe after the ROM install before rebooting)

nooob 4 ever said:
im currently using cwm recovery 5.2.7 or something like that. will i be able to flash the newer roms like CyanogenMod 10.2 with that current recovery?
Click to expand...
Click to collapse
No, you are going to have to update to either the newest TWRP or CWM to flash 4.3 ROMs.

I'm gonna jump in and hope this isn't a hijack. I had a similar experience but I wanted to update to the latest TWRP so I could flash a 4.3 ROM (Simbean) .
I Odined in and flashed TWRP 2.6.3. Was able to flash the Slimbean ROM but on first reboot I can't make it past the Samsung screen.
I can get back into TWRP but everything fails. - typical process. "Fix permissions- Success", then "Full wipe - Success" then "Fix permissions (cause I'm trying anything at this point)- Failed"
In TWRP Restoring backups "Failed" Flashing new image "Failed" In between I've tried Erasing everything but the MicroSD card and starting fresh but Noting will install.
I've reflashed TWRP through ODIN but same issue. A couple of times I've got a restore to work but if the phone sleeps it won't wake up. I can only get back to TWRP.
What is the Nuclear Option? Or have I done that already? I've been flashing for years. I've never seen anything like this.
Help.

pairustwo said:
In TWRP Restoring backups "Failed" Flashing new image "Failed" In between I've tried Erasing everything but the MicroSD card and starting fresh but Noting will install.
I've reflashed TWRP through ODIN but same issue. A couple of times I've got a restore to work but if the phone sleeps it won't wake up. I can only get back to TWRP.
What is the Nuclear Option? Or have I done that already? I've been flashing for years. I've never seen anything like this.
Help.
Click to expand...
Click to collapse
Some people have problems with 2.6.3.0. Try to Odin 2.6.1.0 and see if it helps.
http://techerrata.com/browse/twrp2/hercules

help
so what are my options to fix my phone with the current cwm 5.0.27?

nooob 4 ever said:
so what are my options to fix my phone with the current cwm 5.0.27?
Click to expand...
Click to collapse
i can get into cwm and thats it

nooob 4 ever said:
i can get into cwm and thats it
Click to expand...
Click to collapse
Nothing, that recovery is good for 4.1.2 and lower, of u want newer roms u can go to my beanstalk thread or @ThdDude's hellybean thread and the new recoveries are posted...
Sent from a soup'd up Herc while climbing a giant beanstalk to crazy heights.....

what I did is to hold the power button/ remove the battery of your phone. Open it again and wait for it to start. no bootloop.

[Resolved!] Update to 4.3+ ROM freezes on boot

I am on Liquid Smooth 2.9 (4.2.2) and using TWRP 2.6.3.0 phone is an i747m 32GB model. I tried upgrading to LS2.10 which is 4.3. Installed ROM OK but after first reboot phone froze on the Samsung logo. It wouldn't even get the the boot animation. I tried several methods of flashing as requested but to no avail. Today I tried the latest nightly of Carbon ROM which is 4.3.1 and encountered the same issue. I tried rebooting after flashing GAPPS and it just froze at the Samsung logo without going to boot animation. I did flash the latest bootloader in between while trying to diagnose as well.
Does anyone have any suggestions or similar situations? I would really like to upgrade to a 4.3 ROM but seem to have hit a hurdle...
Thanks in advance.

So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.

Galloway said:
So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.
Click to expand...
Click to collapse
When you flash the ROM, are you wiping dalvik cache as well as wiping all data/ factory reset and cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?

gluk1470 said:
I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?
Click to expand...
Click to collapse
At least it's not just me....unfortunately I don't have much time lately so I haven't been able to try experimenting. I noticed you are using TWRP as well....I may try flashing CWM if I get a sec and see if the results are the same. Also if the same happens and I have enough time I'll try and grab a logcat. If I don't have time it's called wipe and restore from a backup.
And yes Dalvik + cache are always wiped anytime I flash anything as a minimum. With this issue I have been doing an entire internal format. I have tried just wiping cache and Dalvik when it occurs as well as fixing permissions but still doesn't boot. Wish I had more time latrely to narrow it down.

Yes, its work. I flashed stock ROM 4.1.2, then root device, flash CWM 6.0.2.3 (no touch) and flash Quantum 2.20. But I think, problem not in recovery or device. Problem in Titanium Backup, I used it to restore some system apps and accounts, now I restored only call log and SMS.

I have now tried flashing with TWRP and pulling SD card before initial boot to eliminate an SD card issue. I've set to not install backups from Google as precaution. Still the same result of frozen at Samsung logo.
I've then flashed the newest CWM non-touch and wiped all with flash. The result was even worse. This time it wouldn't even boot the first time for initial setup it just hangs at the Samsung logo.
This is starting to get frustrating just due to the fact of me not having a huge amount of time to dedicate to isolating the issue. I need to get a logcat but I am not usually near a computer to ADB to it when it is not booting. If I have time this weekend I'll try and get a logcat to post up.

CWM broke it real good! LOL! Anyways I couldn't even get my backups to restore. I tried taking a logcat while it was frozen but was not able to get an ADB connection in order to even get a logcat. I managed to push a fresh copy of Liquidsmooth 2.9 to the SD card and install it. Then flashed TWRP back. Then restored my back up. What a tedious task to still be scratching my head as to why multiple 4.3 ROM's won't boot on the second boot after flashing...

It's been resolved! As per an awesome person on Carbon's G+ thread don't flash the ROM from external SD .Only flash it from internal storage!

[Q] Stuck in recovery mode bootloop!

Hello everyone,
This is what is happening to me. I was trying to flash Miroslav's Cyanogenmod 11 RC2 with Philz Touch 6.07.9, but none of the recomended methods worked for me, I just got stuck on lg logo bootloop - I really want this rom but it is hard as f**k to flash -. So I tried to go back to CM 10.2.1 and got the "Status 7" error. Very frustrated, I finally used my stock recovery image and it worked fine.
From this point, i was recovering my apps and data using titanium back up and when it finished, a notification asked if I wanted the official system update. I refused it and proceded to reboot. Now the phone boots instantly to recovery mode and show the purple screen of Philz touch. First I wiped cache and dalvik and got the same bootloop. Then I wiped cache, dalvik and factory reset and got the same bootloop. Finally, I formated system, factory reset, wiped cache, wiped dalvik and flashed again my recovery image, and got again the recovery mode bootloop.
Any Ideas? Thank you for your help.
Best regards.
EDIT: I must clarify that when I flash my recovery image, it ALWAYS get suck on a part that says something like "installing android security". I have to press power button 10 seconds to restart but it boots normaly in the stock rom.

chortiman said:
Hello everyone,
This is what is happening to me. I was trying to flash Miroslav's Cyanogenmod 11 RC2 with Philz Touch 6.07.9, but none of the recomended methods worked for me, I just got stuck on lg logo bootloop - I really want this rom but it is hard as f**k to flash -. So I tried to go back to CM 10.2.1 and got the "Status 7" error. Very frustrated, I finally used my stock recovery image and it worked fine.
From this point, i was recovering my apps and data using titanium back up and when it finished, a notification asked if I wanted the official system update. I refused it and proceded to reboot. Now the phone boots instantly to recovery mode and show the purple screen of Philz touch. First I wiped cache and dalvik and got the same bootloop. Then I wiped cache, dalvik and factory reset and got the same bootloop. Finally, I formated system, factory reset, wiped cache, wiped dalvik and flashed again my recovery image, and got again the recovery mode bootloop.
Any Ideas? Thank you for your help.
Best regards.
EDIT: I must clarify that when I flash my recovery image, it ALWAYS get suck on a part that says something like "installing android security". I have to press power button 10 seconds to restart but it boots normaly in the stock rom.
Click to expand...
Click to collapse
When in vain , unbrick your phone again using unbricking guide and use CWM , not all guide is working for the same type of phone . No need to wipe system clean cache watevr **** you were told unless recommended by developer and just factory reset then flash the rom

Mr.201 said:
When in vain , unbrick your phone again using unbricking guide and use CWM , not all guide is working for the same type of phone . No need to wipe system clean cache watevr **** you were told unless recommended by developer and just factory reset then flash the rom
Click to expand...
Click to collapse
Thanks for the answer and the advice about factory reset. Yes, I had to unbrick my phone and by the way, still could not install miroslav's cm11 RC3 using Philz touch 6.19.3.
But I have another issue: I successfully got back to CM 10.2.1 but after I restored my apps using Titanium Backup, I rebooted the phone and got stuck on CM logo for half hour. I wiped dalvik and got the same result. Then wiped cache and dalvik and still stuck. What should I do? Flash again the rom? The restored data is from CM 10.2.1 so I don't see any problem....

chortiman said:
Thanks for the answer and the advice about factory reset. Yes, I had to unbrick my phone and by the way, still could not install miroslav's cm11 RC3 using Philz touch 6.19.3.
But I have another issue: I successfully got back to CM 10.2.1 but after I restored my apps using Titanium Backup, I rebooted the phone and got stuck on CM logo for half hour. I wiped dalvik and got the same result. Then wiped cache and dalvik and still stuck. What should I do? Flash again the rom? The restored data is from CM 10.2.1 so I don't see any problem....
Click to expand...
Click to collapse
check again what you restore, user apps will have no problem to restore but system apps will cause incompatibility to the rom and crash it

Mr.201 said:
check again what you restore, user apps will have no problem to restore but system apps will cause incompatibility to the rom and crash it
Click to expand...
Click to collapse
The phone is good now, I restored the stock rom and from there I flashed CM 10.2.1 just making a factory reset. Plus I flashed adreno drivers and gapps. Once it booted, I restored my apps without sistem data and now the phone works properly.
Thank you Mr.201

chortiman said:
The phone is good now, I restored the stock rom and from there I flashed CM 10.2.1 just making a factory reset. Plus I flashed adreno drivers and gapps. Once it booted, I restored my apps without sistem data and now the phone works properly.
Thank you Mr.201
Click to expand...
Click to collapse
Glad it worked, make sure you untick 'system' in filter in titanium backup so that you can only see your user apps .