Ok, I have a phone that I purchased used. When my S3 got the Jellybean update in December, I found out it had Clockwork Recovery Mod installed on it. It scared the hell out of me, but I went ahead with the update and it was fine. I am a complete newb to rooting and would never root my phone (I lack the skills). When the update went through in December, I was relieved. For more details on all that, see this thread: http://forum.xda-developers.com/showthread.php?t=2048805
Today's update was a different story. This update appears to have broken my phone.This time, it won't even boot up. It just say "System software not authorized by Verizon Wireless has been found on your phone and go to the nearest Verizon Wireless Store for help." Any suggestions on how to fix this? Am I completely screwed? I have almost no knowledge of rooting, ODIN, etc.
R: [Q] Help - I bricked my phone with latest VZW update
It's not bricked.. you should be able to get in download mode and flash a stock firmware with Odin..
edit: I'll link you the url's to the howto's as soon as I get to my pc
Sent from my GT-I9300 using xda premium
zeroblu3 said:
It's not bricked.. you should be able to get in download mode and flash a stock firmware with Odin..
edit: I'll link you the url's to the howto's as soon as I get to my pc
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
The weirdest thing just happened. Ok, I put in ODIN mode and pressed cancel. Then like 3 minutes later, it just started up all on its own. The update failed of course but the phone is working again. Weird. Was able to turn it off and restart.
I think I may trade this phone back into the same folks who sold it to me. I am clearly not cut out for this.
i'm glad the problem solved by itself
anyway if you still want to attempt to reset the phone to stock here is everything you should need to know :
http://forum.xda-developers.com/showthread.php?t=1762709 (take a look at section 5)
it's really not as hard as it looks...just be aware there is always a chance that something could go wrong....just take your time, read, and only go ahead if you are fully confident and willing to accept the risks...
let us know how it went and don't hesitate to ask for help if you are still in doubt after reading the forum
I hate how I am average Joe with my root knowledge and I could fix your phone without thinking twice.
It surprises me you have an xda account and can not even root and unlock boot loader.
You ask for help then say. Never mind.
Haha whatever works for you at the end of the day.
Sent from club Clean Rom
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse
My Atrix 2 is currently having some serious issues. Last night I rooted it. I changed the boot animation to what was supposed to be a human eye turned droid eye or something. When I rooted it and attempted to install Safestrap it didn't install correctly. As I am inexperienced with rooting android phones, I didn't think it'd hurt. I don't know if it did. When I rebooted to see the animation it just said android in silver letters with light flashing across it and it never got past that. I did several hard resets to see if that would fix it, after trying multiple battery pulls of course, and nothing. The phone is now dead and won't charge, when I plug it in it just shows the Motorola logo and doesn't do anything, but if I unplug it the logo doesn't go away. Help, please!
CreativeSin said:
My Atrix 2 is currently having some serious issues. Last night I rooted it. I changed the boot animation to what was supposed to be a human eye turned droid eye or something. When I rooted it and attempted to install Safestrap it didn't install correctly. As I am inexperienced with rooting android phones, I didn't think it'd hurt. I don't know if it did. When I rebooted to see the animation it just said android in silver letters with light flashing across it and it never got past that. I did several hard resets to see if that would fix it, after trying multiple battery pulls of course, and nothing. The phone is now dead and won't charge, when I plug it in it just shows the Motorola logo and doesn't do anything, but if I unplug it the logo doesn't go away. Help, please!
Click to expand...
Click to collapse
Phew, that was close. Hello and welcome to the help section of the A2 forum, for starters the trouble you're facing right now is called soft bricking. It's a very common problem, but is usually solved by flashing the correct ICS sbf for your region.
So firstly, is your phone branded AT&T or is it from another region? Please specify which. Next you need to recharge your battery externally either by an external battery charger or the Mcgyver method. (search the forum for more details).
After you've charged your battery up enough, put it back in your phone and put your phone into fastboot mode by holding the volume down button + power button and make sure it says 'Battery OK'.
After making it this far, you'll need RSD lite order to flash/install the sbf files. If everything goes fine without failure, then your phone will be back to stock and you've saved it! Here's a thread that has content that should guide you with further details: http://forum.xda-developers.com/showthread.php?t=2245825 Good luck!
Sent from the Ace's MB865 using xda-developers app
Aceofzeroz said:
Phew, that was close. Hello and welcome to the help section of the A2 forum, for starters the trouble you're facing right now is called soft bricking. It's a very common problem, but is usually solved by flashing the correct ICS sbf for your region.
So firstly, is your phone branded AT&T or is it from another region? Please specify which. Next you need to recharge your battery externally either by an external battery charger or the Mcgyver method. (search the forum for more details).
After you've charged your battery up enough, put it back in your phone and put your phone into fastboot mode by holding the volume down button + power button and make sure it says 'Battery OK'.
After making it this far, you'll need RSD lite order to flash/install the sbf files. If everything goes fine without failure, then your phone will be back to stock and you've saved it! Here's a thread that has content that should guide you with further details: http://forum.xda-developers.com/showthread.php?t=2245825 Good luck!
Sent from the Ace's MB865 using xda-developers app
Click to expand...
Click to collapse
As RSDLite was rebooting my phone I checked the forums and saw this! Hahah but thank you very much! This is pretty much exactly what I ended up doing. I posted this and then read up on the forums rules and some stuff and realized I should really learn to help myself if I want to . Took some time and a lot of mistakes but I put it together. Thank you very much for the reply.
CreativeSin said:
As RSDLite was rebooting my phone I checked the forums and saw this! Hahah but thank you very much! This is pretty much exactly what I ended up doing. I posted this and then read up on the forums rules and some stuff and realized I should really learn to help myself if I want to .
Took some time and a lot of mistakes but I put it together. Thank you very much for the reply.
Click to expand...
Click to collapse
You're welcome :thumbup: I'm glad it all worked out for you in the end. I still remember the time earlier this year when I just got my phone, went crazy with mods and ended up softbricking it for a whole week. It was hell just to get it working again cuz RSD Lite decided to hate me from the get-go. -_-
So I'm glad to help others out with this, but enough rambling lol, take greater care for the next flashes you do until you get used to it!
Sent from the Ace's MB865 using xda-developers app
Aceofzeroz said:
You're welcome :thumbup: I'm glad it all worked out for you in the end. I still remember the time earlier this year when I just got my phone, went crazy with mods and ended up softbricking it for a whole week. It was hell just to get it working again cuz RSD Lite decided to hate me from the get-go. -_-
So I'm glad to help others out with this, but enough rambling lol, take greater care for the next flashes you do until you get used to it!
Sent from the Ace's MB865 using xda-developers app
Click to expand...
Click to collapse
Thanks! Just got it all rooted again no problem. I'm trying to learn all this, any tips on something I could start working on?
CreativeSin said:
Thanks! Just got it all rooted again no problem. I'm trying to learn all this, any tips on something I could start working on?
Click to expand...
Click to collapse
Well now that you're back and rooted, if you're planning on doing any more flashing any time soon then I recommend you install boot menu manager. If you've previously installed safestrap or bootstrap, clear their data and uninstall them before installing bmm.
With that done, you've just made your phone a little safer from bricking because bmm allows multi rom booting, which are somewhat independent of the primary system. Refer to this thread for more info on how to make systems, etc.: http://forum.xda-developers.com/showthread.php?t=2115715
The first thing you'd want to do is make sure your apps/data is always backed up at all times with apps like titanium backup. Create 2 or more systems so that you can try the bmm compatible custom ROMs which are in the dev section if you want to try any of them. But please, read all instructions, warnings, requirements, etc. carefully before attempting any flashing in general.
The thread I posted in my earlier post above will have links to the specific custom ROMs. If you're doing any other kind of flashing, make sure to again, read instructions carefully and take your time with learning all of this.
Hi, I soft bricked my phone recently.
I was running stock ICS from Moto on a rooted Atrix 2. I wanted to upgrade it to JB so I installed Atrix 2 bootstrap and clicked Bootstrap Recovery (gave superuser permission) and then Reboot Recovery. It went into CWM and I wiped factory data and cache. Before I installed the JB zip I backed up my old ICS via CWM and then installed CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com zip.
It was upgraded successfully to 4.2.2 but I couldnt get my updated contacts from the Super Recovery app, so I thought to restore the old ICS and backup the contacts once again. I installed Atrix 2 bootstarp apk again and went thought the same process ( Bootstrap recovery > gave Superuser permission > Reboot recovery). As soon as it rebooted the Motorola logo came on and after that the phone gave dark grey screen. I tried rebooting and going into CWM on startup but it didnt give the option of install zip from sd card as it did on my earlier attempt.
I am stuck with a bricked phone and all my work is stuck up.
I read about RSDlite but I have heard it causes hard bricking on several occasion. So, I am a bit cautious about using it and I dont know the exact procedure to use it also. Can you please guide me on how to regain my phone from this soft brick and where i went wrong during my installations.
Any help would be very much appreciated. Thanks a lot in advance.
kunal2711 said:
Hi, I soft bricked my phone recently.
I was running stock ICS from Moto on a rooted Atrix 2. I wanted to upgrade it to JB so I installed Atrix 2 bootstrap and clicked Bootstrap Recovery (gave superuser permission) and then Reboot Recovery. It went into CWM and I wiped factory data and cache. Before I installed the JB zip I backed up my old ICS via CWM and then installed CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com zip.
It was upgraded successfully to 4.2.2 but I couldnt get my updated contacts from the Super Recovery app, so I thought to restore the old ICS and backup the contacts once again. I installed Atrix 2 bootstarp apk again and went thought the same process ( Bootstrap recovery > gave Superuser permission > Reboot recovery). As soon as it rebooted the Motorola logo came on and after that the phone gave dark grey screen. I tried rebooting and going into CWM on startup but it didnt give the option of install zip from sd card as it did on my earlier attempt.
I am stuck with a bricked phone and all my work is stuck up.
I read about RSDlite but I have heard it causes hard bricking on several occasion. So, I am a bit cautious about using it and I dont know the exact procedure to use it also. Can you please guide me on how to regain my phone from this soft brick and where i went wrong during my installations.
Any help would be very much appreciated. Thanks a lot in advance.
Click to expand...
Click to collapse
Use boot menu manager instead of bootstrap recovery
Sent from my MB865 using XDA Premium 4 mobile app
Hi XDA. I'm having a really stressful problem right now. Yesterday I rooted my Nexus 6 to Cyanogenmod 12, adding up to installing TWRP. I had fun rooting it all the way and messing around with full control of my device. Until I noticed that, T-Mobile has found out that my Nexus was rooted! As I was having issues with the IMEI of my phone, I couldn't receive and make phone calls. So I went to The Unlockr website and they taught me how to unroot my Nexus 6 and how to flash it back to stock mode. And so I did. I flashed it back to Stock... I thought this was the day the phone would shine bright and reset as stock... But no... TWRP recovery (Teamwin) keeps bootlooping endlessly, leaving me paranoid, into thinking "WTF SHOULD I DO NOW" I want to know what is wrong and what should I do to solve this enormous annoying issue... Please answer back, I'll be in deep trouble if my family knows that my phone is going haywire, and I wouldn't want to spend a lot of money to replace my phone for another one... I need help guys.
Hi
Thanks for writing to us at XDA Assist. I think the best place for your question would be the Nexus 6 help thread here:
Noob Friendly Q and A Help Thread
Thread closed, thanks.
Hey everyone,
Up until recently, I've had no issues with my Zenfone 6. However last night the camera started acting up when I was trying to take a picture and the app suggested I restart my device inorder to rectify the problem. I followed the prompt and ever since last night my phone has been stuck in a boot loop. I have stock everything on this phone, I have experimented with roms and kernels in the past but didn't feel the need on this phone. I followed deadman96385 guide on how to unbrick your Zenfone but still have the same problem. I can't enter my recovery instead it just kicks me back to the boot screen. Unforchuntly, it is not unlocked so I have no way to flash twrp and install a fresh version of Android. I contacted Asus and their support suggested I find a local technician but I'm hoping git won't have to come to that. Any help would be greatly appreciated!
xgrifflegruffx said:
...
Click to expand...
Click to collapse
@xgrifflegruffx THREAD CLOSED as duplicate of https://forum.xda-developers.com/t/help-with-bootloop.4194625/, which had been moved from "Guides etc." to Q&A.
Please review rule no. 5 of the XDA Forum Rules and do not multiply post!