Related
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Dr. Light said:
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Click to expand...
Click to collapse
first of all you can't flash anything on a stock recovery hence the need of a custom recovery. Second you don't accept the OTA when rooted as it can cause the exact issue that you have. Last there isn't a way to fix your problem via another android device that I know of.
U are going to need a pc and then u will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery. Then you can access your backups.
Always_Jonezen said:
U will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery.
Click to expand...
Click to collapse
He doesn't have access to his PC PLUS he already knows what to do on that end.
jmxc23 said:
He doesn't have access to his PC PLUS he already knows what to do on that end.
Click to expand...
Click to collapse
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Thanks for all of advice guys. I'll prob just wait it out till Monday. Thanks again.
Always_Jonezen said:
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Click to expand...
Click to collapse
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
jmxc23 said:
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
Click to expand...
Click to collapse
hey all, I've been reading , downloading etc for hours trying to get back into my GS3.. i was as usual roaming around and saw a post that said something to this effect "do ya need to get back to stock?" and figured yes i need to so i jumped in with both feet ..i had my boot loader unlocked and for some reason locked the darned thing remembering it was locked before i rooted and then i get the screen that says ie: "System software not authorized ~~~~~~~~~~~~" with a yellow triangle over it with an "!" mark in it..
all would have been ok except the line up of the way to do things was kinda outta line.. after i had locked bootloader "which is the way the GS3 came" i thought. at any rate i am now where i said i was and if i can be helped it would be appreciated.. and no repeated.. next time i'll read their whole line up first.. so help me if ya can and i am game right now for about anything ..
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
Yep so I tried to install CM11
and the last thing was to:
fastboot flash boot boot.img
and that was it. Cannot restore my Nandroid backup - it doesn't boot back up.
Just gets stuck at the HTC page with "This build is for development purposes".
I think I need the stock boot.img but it is no where to be found.
Any help??
Just paid someone to get the RUU and restore then phone. I have no idea how he found the RUU since no one else here has it. If they have it they are not sharing it.
Who did you find to restore your phone?
808phone said:
Just paid someone to get the RUU and restore then phone. I have no idea how he found the RUU since no one else here has it. If they have it they are not sharing it.
Click to expand...
Click to collapse
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
so basically you paid a guy to google the right RUU???
all you had to do is check your CID (its written on fastboot) and search for that, they really arent that hard to find!!
http://forum.xda-developers.com/showthread.php?t=2140967
also if you're going to keep flashing different roms its also a good idea to keep that RUU on your pc somewhere!!
There was no matching ruu. What no one told me was that you could use a newer ruu than the one you have. Another thing, before you judge, there were no replies to help me so I had no choice. Since then look how many times I have helped others.
chrons6 said:
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
Click to expand...
Click to collapse
As I previously posted, you can use a newer ruu than the version you have installed. That's what the guy did.
In not judging at all man, i just couldnt understand as to why you couldnt fine the info... They guy you paid is no different to you or me, che just searched harder... As for the ruu the name itself tells you its an update... No biggie im glad you got it worked out in the end
Sent from my One S using xda app-developers app
zubeedubs said:
In not judging at all man, i just couldnt understand as to why you couldnt fine the info... They guy you paid is no different to you or me, che just searched harder... As for the ruu the name itself tells you its an update... No biggie im glad you got it worked out in the end
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Did you not read what I said? THERE WAS NO MATCHING RUU! Read OK????
No one told me you could use a NEWER RUU.
If someone - perhaps you had told me, yeah fine, I could have done it. No one helped ok?
BTW: I did a nandroid backup, I had installed custom recovery, rooted with superSU etc... I had adb, fastboot working too. Because I couldn't get an answer I paid someone.
If you have a JTAG machine and you were running a business then maybe you are just like him.
808phone said:
Did you not read what I said? THERE WAS NO MATCHING RUU! Read OK????
No one told me you could use a NEWER RUU.
If someone - perhaps you had told me, yeah fine, I could have done it. No one helped ok?
BTW: I did a nandroid backup, I had installed custom recovery, rooted with superSU etc... I had adb, fastboot working too. Because I couldn't get an answer I paid someone.
If you have a JTAG machine and you were running a business then maybe you are just like him.
Click to expand...
Click to collapse
dude theres no need to get fassy about anything... unless your one s is knock off means that there is a RUU for your device and that you simply couldnt find one in the small amount of time that you searched for one...
and just to gnaw a little more at your flawed logic and sour attitude RUU means "ROM UPDATE UTILITY" so i guess your right in not being able to use a newer one... :good:
AND BTW.. i dont have a jtag but i do run a business and in my line of work we see folk like you everyday, ever so quick to get pi**ed at someone for THEIR OWN mistakes!!!
and maybe if youre that impatient and wound up for your own calamities it serves you right to have paid for a simple task..
---------- Post added at 08:21 PM ---------- Previous post was at 08:14 PM ----------
chrons6 said:
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
Click to expand...
Click to collapse
have a peek at the RUU thread in the dev section and follow the instructions... it really isnt that difficult!!!
? and in my line of work we see folk like you everyday
Right and that's why I have more thanks and posts than you for helping people.
Yes, I know that a RUU has a version number too. I know what it means. If you even took the time to realize that after having to pay, I helped out other people after that so they wouldn't have to pay.
I guess you don't read. I said you COULD use a newer version of the RUU but no one told me.
Where were you when I asked for help? Never mind, you go about yourself and I will continue helping.
In my line of work I know people like you too. You are the type of person people avoid so create your own thread and stop jumping in with unhelpful info.
808phone said:
? and in my line of work we see folk like you everyday
Right and that's why I have more thanks and posts than you for helping people.
Yes, I know that a RUU has a version number too. I know what it means. If you even took the time to realize that after having to pay, I helped out other people after that so they wouldn't have to pay.
I guess you don't read. I said you COULD use a newer version of the RUU but no one told me.
Where were you when I asked for help? Never mind, you go about yourself and I will continue helping.
In my line of work I know people like you too. You are the type of person people avoid so create your own thread and stop jumping in with unhelpful info.
Click to expand...
Click to collapse
about your deluded logic: paying a guy to fix your mistakes is the right info??? seriously?? and thats supposed to help the next guy more than directing him towards the right RUU??? boy you really are a contribution to the comunity...
about your thanks rating: i signed up last month and youve been here since january if youve ever contributed anything on here then you should have more thanks than me, its basic math, also i think i should point out that its a forum and not "thank marathon" nobody wins a prize for them...
as far as helping people: i suppose you have, i dont really care that much either..
lastly: i came on your thread infact to lend a hand, until i saw that youre actually lazy and ready to fire off your mouth at strangers for nothing apart from stating the obvious truth...
so as of now you can take your all your thanks and try and cash them in for the next phone you softbrick and "need" to pay someone else to fix...or maybe not!!!
as for me this discussion is closed as i can only feed a troll so much!!!
808phone said:
As I previously posted, you can use a newer ruu than the version you have installed. That's what the guy did.
Click to expand...
Click to collapse
I understand how the RUU works and how to use it. My problem, though I hope not, may be slightly more unique?
I had previously rooted by ONE S T-Mobile version and it had been working fine. I then decided to try out another rom. I likely flashed an incorrect boot img because it would only reboot into fastboot, but would still allow me to go into recovery. I went to recovery and restored my nandroid backup; however, now the phone will get stuck on the opening HTC screen the red language on the bottom, "this build is for development purposes only." It will hang on this screen for about 20 seconds and then turn off. No loop. When I attempt to power up again, I get a quick horizontal flash of light across my screen and then the orange LED comes on in the top left corner indicating the phone is charging. I then hold down power and again the phone gets stuck on the opening HTC screen with the red language.
My problem is that I cannot get the phone into fastboot
I've received advice on how to enter the bootloader: power off the phone manually by pressing power for 10+ seconds. Then I' should be able to enter the bootloader and fastboot. (Vol down + power)
Unfortunately, no matter how many times I try, using the above method and a variety of other methods, I still can't get past "HTC developmental purposes only" screen. I'm not new to android and have experience with a number of phones, but this is my first HTC. Pretty frustrating thus far. Rather than spend many more hours pulling out my hair and continually going in circles with no progress to show for my efforts, I'd rather pay someone to make the necessary fixes for me.
Any additional advice would be much appreciated.
same problem
zubeedubs said:
about your deluded logic: paying a guy to fix your mistakes is the right info??? seriously?? and thats supposed to help the next guy more than directing him towards the right RUU??? boy you really are a contribution to the comunity...
about your thanks rating: i signed up last month and youve been here since january if youve ever contributed anything on here then you should have more thanks than me, its basic math, also i think i should point out that its a forum and not "thank marathon" nobody wins a prize for them...
as far as helping people: i suppose you have, i dont really care that much either..
lastly: i came on your thread infact to lend a hand, until i saw that youre actually lazy and ready to fire off your mouth at strangers for nothing apart from stating the obvious truth...
so as of now you can take your all your thanks and try and cash them in for the next phone you softbrick and "need" to pay someone else to fix...or maybe not!!!
as for me this discussion is closed as i can only feed a troll so much!!!
Click to expand...
Click to collapse
Just to say that I
chrons6 said:
I understand how the RUU works and how to use it. My problem, though I hope not, may be slightly more unique?
I had previously rooted by ONE S T-Mobile version and it had been working fine. I then decided to try out another rom. I likely flashed an incorrect boot img because it would only reboot into fastboot, but would still allow me to go into recovery. I went to recovery and restored my nandroid backup; however, now the phone will get stuck on the opening HTC screen the red language on the bottom, "this build is for development purposes only." It will hang on this screen for about 20 seconds and then turn off. No loop. When I attempt to power up again, I get a quick horizontal flash of light across my screen and then the orange LED comes on in the top left corner indicating the phone is charging. I then hold down power and again the phone gets stuck on the opening HTC screen with the red language.
My problem is that I cannot get the phone into fastboot
I've received advice on how to enter the bootloader: power off the phone manually by pressing power for 10+ seconds. Then I' should be able to enter the bootloader and fastboot. (Vol down + power)
Unfortunately, no matter how many times I try, using the above method and a variety of other methods, I still can't get past "HTC developmental purposes only" screen. I'm not new to android and have experience with a number of phones, but this is my first HTC. Pretty frustrating thus far. Rather than spend many more hours pulling out my hair and continually going in circles with no progress to show for my efforts, I'd rather pay someone to make the necessary fixes for me.
Any additional advice would be much appreciated.
Click to expand...
Click to collapse
Thankfully I finally figured out how to consistently get my phone to enter into Fastboot; however, no the trouble I'm having is finding the proper RUU. I've tried the 3 T-mobile varients available in the RUU depository found here
http://forum.xda-developers.com/showthread.php?t=2094414
But alas, while I am able to run the RUU program, which enters my phone into a mode where the screen is all black expect for the HTC logo in the middle, I keep on getting error codes. Are there more than 3 RUU varients identified in the depository?
Oh, I should note that I was also able to get into recovery, but my SD was unable to mount so I can't find my Nandroid
Youre at least half Way there, what recovery are you using?? If you can get your PC to see the device try and format the memory to fat32 from PC...
Sent from my One S using xda app-developers app
zubeedubs said:
Youre at least half Way there, what recovery are you using?? If you can get your PC to see the device try and format the memory to fat32 from PC...
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I believe I'm using TWRP 6.3.0...I'm at work right now and without the phone, but I'm fairly confident that's the recovery. I'll to get the phone into USB mode and see if I'm offered the opportunity to format the memory.
By the way, thanks for the help...it's much appreciated.
chrons6 said:
I believe I'm using TWRP 6.3.0...I'm at work right now and without the phone, but I'm fairly confident that's the recovery. I'll to get the phone into USB mode and see if I'm offered the opportunity to format the memory.
By the way, thanks for the help...it's much appreciated.
Click to expand...
Click to collapse
That won't help. You can fix the sdcrad bug by flashing stock recovery via fastbot and preform "factory reset + clear storage"
Hi guys, I'm pretty new to rooting so tell me if i need to give more info etc cause I know i can be a bit vague.
So I rooted my phone no problem via the all in one kit thing and installed cyanogen, but this was right before the big android update so I wanted to switch back and update to that, but somewhere along the line i got rid of all the Roms (I think)
The stage it's at now: I can boot normally but the startup wizard fails, I assume this is because the stock operating system isnt hooked up to run, regardless I can't find a copy or figure out how to run it. (before my TWRP seemed to stop running on startup)
Bootloader: I don't know how it ended up relocked after I'd unlocked it but am guessing that is why i cant access the custom recovery at the moment (twrp)
If anyone is able could you walk me through, or point me to a guide to show:
How to unlock a relocked phone,
How to get a Stock version of Android (anything after 4.0 I guess because it will auto update?) running on there
Tell me if I'm being dumb in any part of this (apart from pissing about with things I don't understand, haha)
OK, So i'm unlocked and back onto TWRP, that was easy though, What I do need help with is working out how to install the factory Operating system again, last time I tried that is what caused the relocking etc so any help would be amazing.
Thanks, Simon
Redijedeye said:
OK, So i'm unlocked and back onto TWRP, that was easy though, What I do need help with is working out how to install the factory Operating system again, last time I tried that is what caused the relocking etc so any help would be amazing.
Thanks, Simon
Click to expand...
Click to collapse
Is this the same device as the one you are asking about in? [Q] How do I know what RUU to use, and more by Redijedeye
sd_shadow said:
Is this the same device as the one you are asking about in? [Q] How do I know what RUU to use, and more by Redijedeye
Click to expand...
Click to collapse
Sorry yes, meant to close this post now that this particular problem was kinda sorted but didnt get round to it last night. Unless you know a way to get the correct firmware for the wifi? Just seems strange it'd update wrong.
Redijedeye said:
Sorry yes, meant to close this post now that this particular problem was kinda sorted but didnt get round to it last night. Unless you know a way to get the correct firmware for the wifi? Just seems strange it'd update wrong.
Click to expand...
Click to collapse
No, I don't.
I consider this [Completed] and have thread closed.
Hello. Today I tried to downgrade my phone I don't know what was I thinking, but I installed lost of custom ROMs before and stock firmwares too with Odin, so i kinda know how flashing works so I never thought it will be a problem. But after odin successfully flashed my 4.4.4 firmware onto my A5 i restarted the phone, and it wont power up, go into recovery or download mode, or EVEN CHARGE!! it's practically completely dead. Can someone tell me what should I do considering the fact that this is a unibody phone so very hard to cut the power off AND not very much development for it, i can't find debrick images or anything. Somebody knows what should I do? Thank you very much. Oh, and I can't get it to service because of the fact that the screen glass it's a bit shattered its out of warranty so I can't tell them its not my fault and tell them to replace the device. Thanks again.
Mrelenschi said:
Hello. Today I tried to downgrade my phone I don't know what was I thinking, but I installed lost of custom ROMs before and stock firmwares too with Odin, so i kinda know how flashing works so I never thought it will be a problem. But after odin successfully flashed my 4.4.4 firmware onto my A5 i restarted the phone, and it wont power up, go into recovery or download mode, or EVEN CHARGE!! it's practically completely dead. Can someone tell me what should I do considering the fact that this is a unibody phone so very hard to cut the power off AND not very much development for it, i can't find debrick images or anything. Somebody knows what should I do? Thank you very much. Oh, and I can't get it to service because of the fact that the screen glass it's a bit shattered its out of warranty so I can't tell them its not my fault and tell them to replace the device. Thanks again.
Click to expand...
Click to collapse
Hi
thank you for using XDA assist
Im really sorry to hear that OP,
Cant see any relevant for your device here at XDA but i can route you over here for your questions about your device..
http://forum.xda-developers.com/android/help