Related
Hi everyone,
Just a word of advice: Rooting + Flashing ROMs for the Desire may og may not brick your devices. As you can see in this thread http://android.modaco.com/content-p...-usb-connectivity-etc-and-root-a2sd/page/540/ we are quite a few with bricked devices - and no way to un-brick them so far.
Nobody yet knows what might have caused this - maybe Apps 2 SD.
I would advice for everyone to wait flashing any further until this issue is clarified!!!
Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?
Mastoid said:
Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?
Click to expand...
Click to collapse
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.
It could be any ROM.
Sent from my HTC Desire using Tapatalk
socktug said:
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
Click to expand...
Click to collapse
I take it you have a bricked phone then? I hope this gets resolved soon especially for those who might have turned their phone into nothing more than a paper weight.
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.
Click to expand...
Click to collapse
Since many people have reported this issue, is there not some kind of pattern emerging? Hopefully we can isolate the problem to something in particular, as you stated, whether it be caused by the rooting process, Apps2SD, or a USB driver issue.
For those who are experiencing this, might be an idea to post computer specs, what ROM they attempted to install, and other associated things so we can narrow down the problem.
I've flashed loads so far and have no issues - finally got a ROM I like at the mo so will leave it for now...probably
My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.
It happens that I flash several time in a day, I have MCR r3 A2SD+ now and I never had such a problem...
The problem is APPS2SD related.
DocRambone said:
My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.
Click to expand...
Click to collapse
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Could this be most of the issue happened to be with people with .80 bootloader??
kuailan said:
Could this be most of the issue happened to be with people with .80 bootloader??
Click to expand...
Click to collapse
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.
abc27 said:
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.
Click to expand...
Click to collapse
There are people on modaco who have bricked their phones, and were not using A2SD.
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.
socktug said:
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.
Click to expand...
Click to collapse
I think DocRambone is onto something here... he stated a few posts back that he thinks it may be down to the sensitivity of the connection/cable while the phone is in recovery mode during flash, and you mentioned that you bricked your phone while knocking it while flashing in recovery?
From my experience, whenever I attempted to flash Desire cutoms ROMs, I did not move the USB cable at all and it worked fine. Had the phone placed on the desk and kept it stationary while flashing. I have not had any problems with Apps2SD or USB driver issues either.
I did mine from the laptop and the phone on the sette beside me. lol. I initially thought I'd knocked it and the battery came out, but I'm fairly sure now that the battery wasn't the problem, it fits too tight to come out with a simple knock of the hand.
Anyway, all I can say is if you brick it, and can unroot it, and bought it at the carphonewarehouse, you will be fine! They took it back and gave me a new one, no questions asked. I'm not going near a root process untill there is a fix now
Afaik there are two possible solutions for the issue
1. someone needs to security unlock the spl, so that we are able to use all fastboot commands
2. In the modaco thread someone found some helpfull kernel commands
so, if anyone either is experienced in spl modifications or capable of programming c for the kernel commands, pleade send me a pm
millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
I have read the last few pages of the MoDaCo thread but still I am not clear about the issue.
Is it there are some unknown factors causing the root process to brick the USB? But still you can flash stock RUU in fastboot?
you can flash back to stock cause fastboot is still working and so you can flash the signed stock roms (thoose with release keys or the testrom with testkeys) but due to the fact that adb is nomore working you can't enter the custom recovery to flash cooked roms
millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
Just send a message to one of the mods, he sure will make that post sticky
--edit---
man, theese guys are fast, now it's sticky
Easy and apparently safer method of rooting?
Not sure if anyone's seen this on modaco but using the tiny core linux has worked well for me, with 3 flashes from a stock HTC ROM and currently running eViL De-SiRe after trying paul's initial boot then the Cyanogen Port.
May flash again tonight with the Kernel release the ROMs will get better and better.
i have searched, read and read more. but i am totally stuck on getting a custom theme and dock setup on my rooted phone. is there a how to that is better written than the ones i have come across on start to end on programs, apps, w/e i need to get one of these custom themes working. seems i follow what is there, but get stuck on area's of it, than i search on that to come up with nothing or no info. maybe im just over doing it all in one day on learning all this, lol. im a video person, but havent seen a install video of this. any help or links or something? thanks
tyhodge07 said:
i have searched, read and read more. but i am totally stuck on getting a custom theme and dock setup on my rooted phone. is there a how to that is better written than the ones i have come across on start to end on programs, apps, w/e i need to get one of these custom themes working. seems i follow what is there, but get stuck on area's of it, than i search on that to come up with nothing or no info. maybe im just over doing it all in one day on learning all this, lol. im a video person, but havent seen a install video of this. any help or links or something? thanks
Click to expand...
Click to collapse
Youre asking how to install a theme?? Find once compatible for your rom. Stick it on your sd card. Boot into recovery, and flash it.
Post what problems you are having. Good luck.
Sent from my PC36100 using XDA App
Dredge said:
Youre asking how to install a theme?? Find once compatible for your rom. Stick it on your sd card. Boot into recovery, and flash it.
Click to expand...
Click to collapse
im not even sure which rom to use, i have tried a couple but the adk is where i am stuck at, when i go to command prompt it isnt at the c://adk/etc.. like what all the write ups are at, its at c://user/applications or something of that nature and i type what should be typed in on the /adk part of it and says it can not be found. i tried reinstalling the adk again and same problem, im doing something wrong somewhere i assume or stuck in a spot that i keep doing wrong and not noticing. i just rooted it, so whatever rom i have i am assuming is the stock one since i havent gotten past this yet.
Your in over your head man, seriously, YOU put the sdk where you want it, me, I just put it in C:\sdk to make my life easy when changing directories.
If command line work is not something your familiar with, have patience, enjoy your rom as it is right now and wait until the super easy one click gui programs are created.
Did you buy the phone already rooted, or did you root it yourself?
Dredge said:
Did you buy the phone already rooted, or did you root it yourself?
Click to expand...
Click to collapse
i rooted it myself. also when i right click on tools and im supposed to see open in comand promp or something, that doesnt appear?
tyhodge07 said:
i rooted it myself. also when i right click on tools and im supposed to see open in comand promp or something, that doesnt appear?
Click to expand...
Click to collapse
You say you rooted it yourself, which is great, but the questions you're asking are so far out that it makes it urprising that you did.
UNLESS... you rooted using simpleroot or some ****? If sooooooo, that makes ur questions make a lot more sense.
Anyways you just boot into recovery, and flash the zip from that menu.
It has nothing to do with adb, cmd, or any of that other bull**** you're talking about. Just do what's bolded and stop going 3 miles outside of the box.
TJDuckett said:
You say you rooted it yourself, which is great, but the questions you're asking are so far out that it makes it urprising that you did.
UNLESS... you rooted using simpleroot or some ****? If sooooooo, that makes ur questions make a lot more sense.
Anyways you just boot into recovery, and flash the zip from that menu.
It has nothing to do with adb, cmd, or any of that other bull**** you're talking about. Just do what's bolded and stop going 3 miles outside of the box.
Click to expand...
Click to collapse
I agree, OP, you are way over complicating it dude. What is your build number? Settings> about phone> software information.
If I didn't know better I would almost bet you're trying to troll us. Being a brand new account and all.
Dredge said:
I agree, OP, you are way over complicating it dude. What is your build number? Settings> about phone> software information.
If I didn't know better I would almost bet you're trying to troll us. Being a brand new account and all.
Click to expand...
Click to collapse
build number
1.17.651.1 cl160858
ive tried the reboot and flash thing and nothing happened, said missing filie or something and erased my phone and now vibrate doesnt work? this is after placing them theme on there i want to use and trying to load it in the boot screen. dont know all these names for the android system. prob just so used to messing with the iphones which is what is making this so hard for me, lol.
tyhodge07 said:
build number
1.17.651.1 cl160858
ive tried the reboot and flash thing and nothing happened, said missing filie or something and erased my phone and now vibrate doesnt work? this is after placing them theme on there i want to use and trying to load it in the boot screen. dont know all these names for the android system. prob just so used to messing with the iphones which is what is making this so hard for me, lol.
Click to expand...
Click to collapse
I don't believe you anymore. Even Root tutorials direct you to install a rom after rooting, which would put you at 1.47.65 or whatever even without 2.2 upgrading.
Trying to flash a zip that isn't valid doesn't do anything at all to your phone... it just... doesn't work and sends you on your way. Absolutely nothing you type comes off as a "real" problem.
Anyways, I'm just going to say straight out, that I think you're trolling and that it's sad that you made an account just to waste your time.
I'm done with this thread.
TJDuckett said:
I don't believe you anymore. Even Root tutorials direct you to install a rom after rooting, which would put you at 1.47.65 or whatever even without 2.2 upgrading.
Trying to flash a zip that isn't valid doesn't do anything at all to your phone... it just... doesn't work and sends you on your way. Absolutely nothing you type comes off as a "real" problem.
Anyways, I'm just going to say straight out, that I think you're trolling and that it's sad that you made an account just to waste your time.
I'm done with this thread.
Click to expand...
Click to collapse
think what you would like, im not a kid. ive answered your questions. computers or phones is nothing new to me. family works for sprint, but will not mess with the rooting part of it. so i was left alone on this. ive searched and searched and what u have read is where i am at. basically i am wanting a custom theme. i have tethering and all that crap that works fine. but a theme wont work and a rom to be 1.47 or whatever was never put on, i have what i posted and have everything a rooted phone should have. obviously im stuck on that rom part of it. no reason to be a **** or call someone a troll or say their trolling, when their asking questions. if ur intentions wernt to help, than dont reply. u wasted ur own time.
I just wanted to share the big mistake I made because I didn't realize that there were more then one variants of my phone...
My wife bought me a new HTC One X for Christmas at full retail so we didn't have to extend our contract. I activated it December 26th.
I rooted it the same day and unlocked the bootloader the following day with no problems.... I didn't do anything else to it for 3 weeks.
Night before last I followed instructions I found online here: http://theunlockr.com/2012/04/28/how-to-install-clockworkmod-touch-recovery-on-htc-one-x/ to install Clockwork mod.
Everything seemed to install and everything seemed fine until I got to the end where I was to type in the command prompt to reboot. The phone shut down and will not reboot. No charge indicator anymore nothing! Won't even go into bootloader now with the Vol- and power button.
After all this I realized (thanks to members on here) that I had installed the wrong version of clockwork mod... I installed the version for the endeavoru when I appearently have something else.
So it probably is/was a stupid mistake on my part for not researching more....I just wanted to tell the other noobs doing this stuff to just please read read read!!!!
I have rooted and replaced the ROM's on all my previous phones and tablets with no problem but I do not do this everyday....Just when I get a new phone so I guess I got cocky and just assumed this one would be just as easy....
So I now have a 3 week old $599.99 paper weight.....
Please be careful and avoid the same mistake I made....
I find myself saying this over and over again on this forum: Don't Google around to random websites for phone mods.
This is a perfect example why. Those websites are not well organized, and therefore will easily mislead you into installing mods to your phone that are not meant for your version of the One X.
Plus, almost all of these "unlock" or "root" webites just steal content from XDA. Look at the webpage the OP linked. It just gives credit by giving a link that goes right back here to XDA. These random websites don't create their own content, they just steal from XDA, and add a few sentences of text that any moron can type, and call the work theirs.
Stick to XDA. As long as you are in the forum that says "AT&T", any ROMs, mods, etc. you find will be safe for the AT&T version of the One X, and its other dual core S4 variants.
There are a few other reputable websites with Android mods. But unless you know for a fact they are legit, its better to assume they are not, and stick to XDA.
Its really that simple.
I agree however I didn't just "Google" the recovery install instructions. I got to this page from a link in an XDA post I had read. Problem was I was apparently in the wrong HTC ONE X Forum. The instructions listed on the site are correct for the "Other" version of the phone.
It's an easy mistake to make with the way this site delivers a search. Example: Go up to the top of the page where it has a search box and says "Find your device"
Type in HTC ONE X. Look at which model the search returns. The International model, Not our AT&T version. Granted I should of read a little more closely, I didn't. The picture was my phone so I scrolled down and began reading threads.
If there are more then one variant of the same phone then both should appear when you search for a device so we can pick the correct version. I was unaware there were different versions of the HTC One X until today....
so it is what it is, I can't go back and do it all over and It's been a very expensive lesson learned so my post was to encourage other noobs to read read read so this doesn't happen to somebody else.
I'll eventually go buy another One X and might even go extend my contract and get one sooner.....either way, next time I'll know.
(Going back to my shattered screen Inspire has not been a pleasant experience, makes me really miss the One X)
Take care.
Man that sucks soooooo bad... Which rom did you pick? It sucks you used cwm.. If you would have used twrp there's a 94% chance it would have just failed instead of flashing.... Sorry for your luck bro.
Sent from my One X using Tapatalk 2
InflatedTitan said:
Man that sucks soooooo bad... Which rom did you pick? It sucks you used cwm.. If you would have used twrp there's a 94% chance it would have just failed instead of flashing.... Sorry for your luck bro.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
i think he bricked by flashing wrong cwm, not rom.
Honestly, how ridiculous is it that AT&T called the One XL variant the One X. Poor name choice has lead to problems like OP experienced.
ethantarheels123 said:
i think he bricked by flashing wrong cwm, not rom.
Click to expand...
Click to collapse
The problem isn't with cwm... You can run cwm all day everyday. Problem is its not supported, people been getting their sdcard wiped and what not. The problem with running cwm is that it doesn't restrict what's being flashed IF its not supported. He would have flashed an international rom, and cwm let it happen.
The international Devs worked in their ROMs to fail in twrp for our device..
Sent from my One X using Tapatalk 2
Hmm I wonder if the jet tool could help unbrick it, or is after flashing a wring recovery it to late? I don't have experience unbricking phones, just throwing out there.
scribed on my soon to be sold for note 2 one x!
jessepatty said:
I agree however I didn't just "Google" the recovery install instructions. I got to this page from a link in an XDA post I had read.
Click to expand...
Click to collapse
I find it odd that an XDA post links to the page you posted, since that page just links back to XDA, and doesn't seem to contain any unique or original content. That's why it seemed that you had "Googled" for that webpage, which seems to be what too many people are doing. My apologies since this is not the case, so maybe I should make my font smaller in the post above! ;-P
jessepatty said:
Problem was I was apparently in the wrong HTC ONE X Forum. The instructions listed on the site are correct for the "Other" version of the phone.
Click to expand...
Click to collapse
Yes, its still easy to confuse the variants on XDA, but at least XDA has the forums split apart at all, and makes the distinction between the dual and quad core versions (not the case on most other fly-by-night "root" or "unlock" websites).
Its too late for your current phone. But if you replace it with another AT&T One X, in the future just stick to this forum section and you will be safe from flashing the wrong mods: http://forum.xda-developers.com/forumdisplay.php?f=1538
Use the button "SEARCH THIS FORUM" button instead of the one at the top of the webpage, and you will always stay within the forum for the AT&T version.
And as I mentioned in my previous post, make sure the webpage you are looking at makes mention of "AT&T, Rogers etc." at the top of the page, and you are sure to be in the correct forum section.
You can also take a look at my Index thread, which has most any resource you will ever need: http://forum.xda-developers.com/showthread.php?t=1671237
Everything listed on this Index is specific to the dual core AT&T version and its variants.
jessepatty said:
If there are more then one variant of the same phone then both should appear when you search for a device so we can pick the correct version. I was unaware there were different versions of the HTC One X until today....
Click to expand...
Click to collapse
I've had 5 different smartphones/tablets going back to old Windows Mobile days, and every one of them has had multiple variants, some even having CDMA and GSM variants in the same forum section (but with seperate subforums). In the past you often had to be very careful and verify that you weren't flashing a ROm for the wrong variant (such as flashing a CDMA ROM on a GSM phone). The way XDA is organized for the variants of the One X is actually less confusing than many other devices.
Its good to keep in mind on any smartphone device to research as much as possible, and make sure you are doing mods specific to your version, before doing anything.
ethantarheels123 said:
i think he bricked by flashing wrong cwm, not rom.
Click to expand...
Click to collapse
InflatedTitan said:
The problem isn't with cwm... You can run cwm all day everyday.
Click to expand...
Click to collapse
Actually, if you flash CWM Touch Recovery from inside ROM Manager, you can get a brick. The version in ROM Manager is for endeavour, and it bricks largely for the same reason the endeavour roms do.
iElvis said:
Actually, if you flash CWM Touch Recovery from inside ROM Manager, you can get a brick. The version in ROM Manager is for endeavour, and it bricks largely for the same reason the endeavour roms do.
Click to expand...
Click to collapse
Oh... Ill respectively take my foot out of my mouth lol.
Sent from my One X using Tapatalk 2
To help everyone (Put this in your OP) if you want
Just type : fastboot getvar all
into the Command Prompt before you DO ANYTHING!
This will tell you all your information you need to know about your phone. For ex if its Evita or endevou
InflatedTitan said:
Man that sucks soooooo bad... Which rom did you pick? It sucks you used cwm.. If you would have used twrp there's a 94% chance it would have just failed instead of flashing.... Sorry for your luck bro.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Thanks, it is what it is
ethantarheels123 said:
i think he bricked by flashing wrong cwm, not rom.
Click to expand...
Click to collapse
This is true. I hadn't made it to installing a rom yet.
unitedatom said:
Honestly, how ridiculous is it that AT&T called the One XL variant the One X. Poor name choice has lead to problems like OP experienced.
Click to expand...
Click to collapse
I couldn't agree more (now) LoL
redpoint73 said:
I find it odd that an XDA post links to the page you posted, since that page just links back to XDA, and doesn't seem to contain any unique or original content. That's why it seemed that you had "Googled" for that webpage, which seems to be what too many people are doing. My apologies since this is not the case, so maybe I should make my font smaller in the post above! ;-P
Yes, its still easy to confuse the variants on XDA, but at least XDA has the forums split apart at all, and makes the distinction between the dual and quad core versions (not the case on most other fly-by-night "root" or "unlock" websites).
Its too late for your current phone. But if you replace it with another AT&T One X, in the future just stick to this forum section and you will be safe from flashing the wrong mods: http://forum.xda-developers.com/forumdisplay.php?f=1538
Use the button "SEARCH THIS FORUM" button instead of the one at the top of the webpage, and you will always stay within the forum for the AT&T version.
And as I mentioned in my previous post, make sure the webpage you are looking at makes mention of "AT&T, Rogers etc." at the top of the page, and you are sure to be in the correct forum section.
You can also take a look at my Index thread, which has most any resource you will ever need: http://forum.xda-developers.com/showthread.php?t=1671237
Everything listed on this Index is specific to the dual core AT&T version and its variants.
I've had 5 different smartphones/tablets going back to old Windows Mobile days, and every one of them has had multiple variants, some even having CDMA and GSM variants in the same forum section (but with seperate subforums). In the past you often had to be very careful and verify that you weren't flashing a ROm for the wrong variant (such as flashing a CDMA ROM on a GSM phone). The way XDA is organized for the variants of the One X is actually less confusing than many other devices.
Its good to keep in mind on any smartphone device to research as much as possible, and make sure you are doing mods specific to your version, before doing anything.
Click to expand...
Click to collapse
Thanks....I too have done something, root, unlock bootloaders, install roms, etc over and over going back to win mobile as well and I've never been this careless before. I was in a hurry to get all the AT&T bloatware off it and make it more user friendly so I let my guard down and now have to live with my actions.
ronnyg12 said:
To help everyone (Put this in your OP) if you want
Just type : fastboot getvar all
into the Command Prompt before you DO ANYTHING!
This will tell you all your information you need to know about your phone. For ex if its Evita or endevou
Click to expand...
Click to collapse
THANK YOU!
I will let everyone know that when I got home from work today I found a box at my front door. I opened it up and found a replacement HTC One X. I call and spoke with AT&T questioning why and they said that they went ahead and did a warranty defect on the original phone due to it only being 3 weeks old. So I am excited to say I have a new one in my hand at this time.
Now I just need to start from scratch and figure this out without doing this again. If anyone wants to help walk me through it step by step, I will be forever grateful
Jess
jessepatty said:
I will let everyone know that when I got home from work today I found a box at my front door. I opened it up and found a replacement HTC One X. I call and spoke with AT&T questioning why and they said that they went ahead and did a warranty defect on the original phone due to it only being 3 weeks old. So I am excited to say I have a new one in my hand at this time.
Now I just need to start from scratch and figure this out without doing this again. If anyone wants to help walk me through it step by step, I will be forever grateful
Jess
Click to expand...
Click to collapse
Your new ATT one x probably came with 2.20 software and a new Hboot. I would start reading here:
TOOL KIT NOOB PROOF
Nice all in one tool kit!
eraste said:
Your new ATT one x probably came with 2.20 software and a new Hboot. I would start reading here:
TOOL KIT NOOB PROOF
Nice all in one tool kit!
Click to expand...
Click to collapse
Yes, 2.20...Old one was 1.85
That is what I have, that I used on the first phone.
Thank you
Im having issues with HTCdev.com loading.....keeps timing out. I'm not sure what is up with that.
Gonna try it again tomorrow. Seems like the server is either down or swamped right now.
I did the perm root command in the tool kit which pushed SU to the phone and it says to boot in recovery and run it. I can't seem to get the command line correct to unzip and install SU now. Can somebody post the correct command line to unzip and install SU.
Thanks
jessepatty said:
Im having issues with HTCdev.com loading.....keeps timing out. I'm not sure what is up with that.
Gonna try it again tomorrow. Seems like the server is either down or swamped right now.
I did the perm root command in the tool kit which pushed SU to the phone and it says to boot in recovery and run it. I can't seem to get the command line correct to unzip and install SU now. Can somebody post the correct command line to unzip and install SU.
Thanks
Click to expand...
Click to collapse
The HTCDev.com website is having some serious issues the last few days. Several different users have posted on various posts about the website not working. One user contacted HTC, and they said they are working on getting it back up and running.
You need to unlock the bootloader and install TWRP (custom recovery) before you can flash SU. Once you do those things, just go into recovery, select the install option, and select the SU zip. Its a flashable zip, not something you are supposed to unzip.
redpoint73 said:
The HTCDev.com website is having some serious issues the last few days. Several different users have posted on various posts about the website not working. One user contacted HTC, and they said they are working on getting it back up and running.
You need to unlock the bootloader and install TWRP (custom recovery) before you can flash SU. Once you do those things, just go into recovery, select the install option, and select the SU zip. Its a flashable zip, not something you are supposed to unzip.
Click to expand...
Click to collapse
Thanks....
Yeah I keep submitting my token ID and I get the page that says it was successfully submitted and that I will receive an email with the unlock file attachment but I never get the email... I've submitted it like 4 times now...
I can't do anything else without that file attachment it says I need. I thought I may be able to use the Unlock_code.bin file from my previous phone that died but it says that they are specific to the token ID generated so I guess that is out.
Gonna have to wait until their site is fully functioning before I can proceed.
jessepatty said:
Thanks....
Yeah I keep submitting my token ID and I get the page that says it was successfully submitted and that I will receive an email with the unlock file attachment but I never get the email... I've submitted it like 4 times now...
I can't do anything else without that file attachment it says I need. I thought I may be able to use the Unlock_code.bin file from my previous phone that died but it says that they are specific to the token ID generated so I guess that is out.
Gonna have to wait until their site is fully functioning before I can proceed.
Click to expand...
Click to collapse
Looked in you bulk or spam folders? First time I did it ny email put it there didn't know it twittled my thumbs for almost 2 hours until I noticed it lol. Yea I know I'm an idiot.
Sent from my HTC One XL using Tapatalk 2
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"
Alright, Im going to be completely honest. I am a complete and total noob to the tech behind smartphones. As Ive been learning, I tried rooting my Samsung Galaxy SII SCH-R760X, and after I attempted to flash a kernel that was suggested by this guide: http://forum.xda-developers.com/galaxy-s2/general/how-to-root-galaxy-sii-sch-r760-generic-t1928566, my phone is now stuck at the logo with a warning sign at the bottom. After all this, I realized I made the worst possible mistake anyone could ever make: I didnt backup my system. Luckily, I didnt have much data on it anyway. At this point I am aware it has become a softbrick, and Ive looked at guides such as this one:http://forum.xda-developers.com/galaxy-s2/development/guide-fix-unflashable-soft-bricked-t1619571, but it still tells me to "put the recovery file in its place". Im assuming he's talking about the backup... which i dont have. If anyone could point me to where I can find a backup for it, or upload one for me, I would be incredibly in debt to you. Thank you for reading, I know how most people feel about noobs, but I dont know where else to go.
Please, if I am doing something wrong with this post, please tell me. I dont want to be an annoyance. In fact, this is my first time ever posting to a forum! Id love to get into smartphone tech, however, since I couldnt find a place to start, I made the foolish choice of simply diving in and ruining my phone (hopefully not permanently). Anyway, thank you for reading! Even if you cant help, I really appreciate the attention. Thanks!
RikkyRoe said:
Alright, Im going to be completely honest. I am a complete and total noob to the tech behind smartphones. As Ive been learning, I tried rooting my Samsung Galaxy SII SCH-R760X, and after I attempted to flash a kernel that was suggested by this guide: http://forum.xda-developers.com/galaxy-s2/general/how-to-root-galaxy-sii-sch-r760-generic-t1928566, my phone is now stuck at the logo with a warning sign at the bottom. After all this, I realized I made the worst possible mistake anyone could ever make: I didnt backup my system. Luckily, I didnt have much data on it anyway. At this point I am aware it has become a softbrick, and Ive looked at guides such as this one:http://forum.xda-developers.com/galaxy-s2/development/guide-fix-unflashable-soft-bricked-t1619571, but it still tells me to "put the recovery file in its place". Im assuming he's talking about the backup... which i dont have. If anyone could point me to where I can find a backup for it, or upload one for me, I would be incredibly in debt to you. Thank you for reading, I know how most people feel about noobs, but I dont know where else to go.
Please, if I am doing something wrong with this post, please tell me. I dont want to be an annoyance. In fact, this is my first time ever posting to a forum! Id love to get into smartphone tech, however, since I couldnt find a place to start, I made the foolish choice of simply diving in and ruining my phone (hopefully not permanently). Anyway, thank you for reading! Even if you cant help, I really appreciate the attention. Thanks!
Click to expand...
Click to collapse
You have already found good threads.
To recover a soft-bricked device, you basically have to flash back an official firmware for your device.
The guide you found was for the GT-I9100G, which is a little bit different from your exact device model.
Here is another guide for other variants of the S2: [GUIDE] Fix an unflashable or soft bricked GSII (I9100G/M/P/T VERSION INCLUDED) by Phistachio.
As there is no "ready-to-go" recovery package available for your device model, you have to get an official/stock firmware for your device.
A link to possible firmware sources is in the first post of the guide you posted.
Flashing the stock firmware with Odin should fix the soft-brick.
If not, maybe a wipe data (= factory reset) in recovery mode (long press Volume UP + HOME + POWER) is needed additionally.
And rooting your device seems to be working with this too: [ROOT] Framaroot, a one-click apk to root some devices by alephzain ... I found some users confirming it working fine to root your device model.
If you still have issues and need further help, please ask in the [Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread by It_ler thread.
There we try to give detailed help for all variants of the S2.
Good luck !
Thanks for responding man! I didnt think anyone would reply.
I really appreciate the help. However, I downloaded and flashed the droiddroidz kernel turner78 said to flash, and that was what made my phone go softbricked in the first place... I tried flashing the other two kernels instead, and they proceeded to put my phone in bootloop... So, I tried flashing the "Siyah" stock kernel everyone was talking about, and it made this weird eye thing with a yin-yang flash on my phone... And Im sorry Im a total noob, I just recently learned what flashing and kernels were from the help of google :/... Im still a little lost on what Roms are. But reguardless, Im assuming the kernels I tried flashing were incompatible or corrupted, and thats whats making my phone not work. If Im wrong, correct me please. I know my phone is version 1.4.1, but thats about it. I dont know if its "Gingerbread" or "jellybean" or whatnot. Im sure Ive just made a stupid mistake and Im too dumb to know how to fix it.
RikkyRoe said:
Thanks for responding man! I didnt think anyone would reply.
I really appreciate the help. However, I downloaded and flashed the droiddroidz kernel turner78 said to flash, and that was what made my phone go softbricked in the first place... I tried flashing the other two kernels instead, and they proceeded to put my phone in bootloop... So, I tried flashing the "Siyah" stock kernel everyone was talking about, and it made this weird eye thing with a yin-yang flash on my phone... And Im sorry Im a total noob, I just recently learned what flashing and kernels were from the help of google :/... Im still a little lost on what Roms are. But reguardless, Im assuming the kernels I tried flashing were incompatible or corrupted, and thats whats making my phone not work. If Im wrong, correct me please. I know my phone is version 1.4.1, but thats about it. I dont know if its "Gingerbread" or "jellybean" or whatnot. Im sure Ive just made a stupid mistake and Im too dumb to know how to fix it.
Click to expand...
Click to collapse
As you have already posted in the help thread, this thread can be closed now.
Let's continue in the S2 help thread.
Thanks for your understanding!
Signature:
Device: SGS5 (SM-G900F)
ROM: AllianceROM v9.1
Kernel: Stock XXU1BOE6 kernel
Recovery: TWRP recovery by Ktoonsez
Modem: XXU1POG1