Related
I tried the "IDIOT-PROOF Root Guide! NAND Unlock and ADB Update!!".... to no avail.
I had fallowed the instructions to a tee and around step 55 it all went down hill, it was supposed to automatically flash a ROM and it did nothing, and now i have probably screwed it up worse. Phone is still 100% functional but i would like to reset back to factory settings, no root, no nand, no custom rooted ROMS, nothing.
Does anyone know of a way to get my phone back to the way it was when i walked out of Best Buy earlier today?
Thanks for the help and all the great resources here at XDA.
Daugusta.
Search for and run the RUU
Step 55? Thats the idiot proof guide? I followed the original guides and there were like 10 steps max..
Haha, could i snag a link to the guide you used? also, where can i find this RUU?
Thanks.
Daugusta12 said:
Haha, could i snag a link to the guide you used? also, where can i find this RUU?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=685835&highlight=RUU
This is not flashed, its an exe so its run while your phone is plugged in. Should go smoothly, but as always know the risks of flashing anything
I've heard toasts method is pretty solid for rooting.
Quick question wouldn't this be in Q & A? Not trying to come off as a jerk. Just my 2 cents
Sent via the Sprint HTC EVO
RUU Is not working, i get it to start, it restarts my phone and then sits their at a black screen that says "HTC" Then the program says "Waiting for boot loader" and counts to like 75 and then errors saying that it cannot connect to the phone. I then tried to start the process, pull the battery, then manually put it into the boot loader and the program never recognizes it.
Anyone else have another idea, or a way to get this working?
Thanks,
Daugusta
I believe you have to use HTC sync when you run it, though I could be mistaken. Search YouTube, there's a video of it somewhere. I wouldn't give up on rooting just yet though.
Trust me im not giving up
Try the 1-click Root Method
I looked at the fifty-five step root method and peed my pants, then I hit up jiqqaman's one-click root method. Stable root, and you can flash the stock (rooted) rom.
[forum.xda-developers.com/showthread.php?t=706411
Diesektor said:
I believe you have to use HTC sync when you run it, though I could be mistaken. Search YouTube, there's a video of it somewhere. I wouldn't give up on rooting just yet though.
Click to expand...
Click to collapse
When I have ran an rru from previous HTC phones I have had to have sync up. But then again its never been at a black screen
Sent via the Sprint HTC EVO
Ya, i had the HTC sync running as well, synced up fine with my comp but the RUU still gave me the same error.
Im running this on Win 7 64 Bit, im guessing the 64 bit may be the problem. ill try it on a different comp and see how it goes.
Just tried it on a 32 bit Windows 7 comp, still same issues.
Sucks man, coming from the iphone world this rooting stuff seems a hell of a lot more complicated. The last jailbreak I did on my 3GS I downloaded 1 program, plugged by phone into the PC, clicked 1 button and bam!
This andriod root stuff is waaaaay more difficult, NAND this, bootloader that, recovery this, RUU that, adb this, zip and flashing all kinds of stuff. Wish there was a simpler method. Im obviously a noob so Im sure it will get easier with time.
Daugusta12 said:
RUU Is not working, i get it to start, it restarts my phone and then sits their at a black screen that says "HTC" Then the program says "Waiting for boot loader" and counts to like 75 and then errors saying that it cannot connect to the phone. I then tried to start the process, pull the battery, then manually put it into the boot loader and the program never recognizes it.
Anyone else have another idea, or a way to get this working?
Thanks,
Daugusta
Click to expand...
Click to collapse
It should work. After the program doesn't recognize it, while your phone is at the HTC logo. Close the program on your pc and start it again.
Daugusta12 said:
Just tried it on a 32 bit Windows 7 comp, still same issues.
Click to expand...
Click to collapse
There shouldn't be any problems caused by 64-bit OS. I used Win7 Ult 64-bit and it worked fine. Do you have the HTC Sync drivers? That may fix the problems you have.
EVO'D_OUT said:
Sucks man, coming from the iphone world this rooting stuff seems a hell of a lot more complicated. The last jailbreak I did on my 3GS I downloaded 1 program, plugged by phone into the PC, clicked 1 button and bam!
This andriod root stuff is waaaaay more difficult, NAND this, bootloader that, recovery this, RUU that, adb this, zip and flashing all kinds of stuff. Wish there was a simpler method. Im obviously a noob so Im sure it will get easier with time.
Click to expand...
Click to collapse
I noted this too, only I didn't have an iPhone, just an iPod Touch. Despite this, I am having a lot more fun with Android and how it works. I.E. *.9.pngs which made made jaw drop when I understood how it works. SO AMAZING.
I don't think I will ever be much of a dev, but who knows. I have been digging through a TON of documentation over the past 2-3 weeks.
Thread moved to Q&A.
well I'm pretty much over this rooting business. Ill wait for the official froyo update from Sprint/HTC and not worry about this crap, no camera, instability, bricking, etc. Guess I'm not much of an android hacker and the phone works pretty well bone stock.
Here are my questions...and please explain this to me like I am mentally retarded haha...
For returning my phone to bone stock, Like Day 1, same as it was when I walked out of Sprint store...
1) download .exe file from post #1 onto my PC
2) plug EVO into USB on PC (run in USB debug mode?)
3) Run .exe file while EVO is in Andriod
4) Select yes, yes, blah, blah and it will do its thing automatically?
Is this correct? Some have mentioned I need to download HTC sync onto PC. Yes - No? Any help would be appreciated. Hopefully someone can comment THAT HAS ACTUALLY DONE THIS and not just guessing/speculation can assist.
EVO'D_OUT said:
well I'm pretty much over this rooting business. Ill wait for the official froyo update from Sprint/HTC and not worry about this crap, no camera, instability, bricking, etc. Guess I'm not much of an android hacker and the phone works pretty well bone stock.
Here are my questions...and please explain this to me like I am mentally retarded haha...
For returning my phone to bone stock, Like Day 1, same as it was when I walked out of Sprint store...
1) download .exe file from post #1 onto my PC
2) plug EVO into USB on PC (run in USB debug mode?)
3) Run .exe file while EVO is in Andriod
4) Select yes, yes, blah, blah and it will do its thing automatically?
Is this correct? Some have mentioned I need to download HTC sync onto PC. Yes - No? Any help would be appreciated. Hopefully someone can comment THAT HAS ACTUALLY DONE THIS and not just guessing/speculation can assist.
Click to expand...
Click to collapse
Great question.. Some of these long winded threads need trimming and a definite answer listed out. Clutter = confusion
Anyone that can help me with this one, can be my new bestfriend
After getting really really depressed over being on the Official HTC Sense ROM with my Desire, I decided to change to the Starburst ROM. As the new Unrevoked doesn't work with the latest official build of Froyo from HTC I always, always use this when I want to downgrade and root, to install new roms.
Normally, I will use the utility as indicated, everything will go smoothly, Eclair 2.1 will install, however normally my phone will be locked, and I will have to remove my SIM, update to 2.2, my phone will become Unlocked after updating, and I will root. However this time, when the utility copied a misc_partition or something like that to my SD Card, it came up with a load of write errors, saying there wasn't enough room on my SD Card, which I know is wrong as there is well above 6GB on there, and it's a Goldcard. One advantage of the utility is, if anything goes wrong you can press CRTL-C and the utility will stop with no changes made to your phone, however in my case this wasn't so. I stopped the utility, thinking if I continued due to the write error I would encounter some more errors, and I decided to do a complete wipe of my phone using the on-board Factory Reset in the Setting's menu. After doing this, I started to encounter some problems.
First of all, when the phone enters the setup wizard, it says I have 4 bars of signal, and a 3G connection. After around 15 seconds of being in the Wizard, I will suddenly loose all mobile connection. After completing the setup wizard, I will be prompted by a notice telling me I need to Insert an SD Card. Well my card is in there, and I know its working because after these problems I put it into my brothers phone, and formatted it, and it showed up as working just fine. If an LG POP can mount my phone, surely a frigging HTC Desire can?
I have noticed that if I remove my SD Card, then the problems with the Network will go away and I will be able to connect, however sometimes when I boot it my phone will connect to the Network for about 5 minutes with the SD inserted, then return back to Limited Service. *I have attached a picture of what I am seeing.* This is really annoying me, I am going to download the Froyo 2.2 ROM from Shipped-Roms as the SD Card seems to mount fine in HBoot. Please though, can anyone help me. Thanks.
*This is starting to become very annoying now, I have been working on this for several hours now, and I still have no fix or nothing. I can't exactly be patient and I don't mean to sound like a tech addict, but my world revolves around my phone, I use it for business ect. When I connect my phone to my computer, I get a message saying 'Install Drivers For Qualcomm CDMA Technologies MSM' I have heard of CDMA before, but I don't think my phone is CDMA? My phone was originally branded Orange in the UK? Anyone that can help, just please please help me!
Hi, sorry I can't help with your problem as it seems too complicated to me (noob here) but reading what you wrote sort of alarmed me as I've been reading/watching videos on rooting and I thought that unrevoked (latest version) worked on any desire. It says so on the unrevoked site but you wrote you can't do it on yours because of new build of froyo.
Don't understand that, I'm on vodafone and asked advice to a few people about rooting and nobody told that I couldn't use unrevoked. Are you sure you can't use it. How about you do a factory reset and reflash rom and see how it goes. I do hope you're wrong about unrevoked though as I'm about to use it any day now (building up the courage...) Hope you get your problem solved.
well try to reinstall whole software via pc ...............
but check download latest version of official rom
back up your data as ur whole system sofware will be replaced
and do format ur sd in pc ( not a quick format )
hopefully it might resolve ur issues ( otherwise it seems a hardware issue >>>>>)
and i am not responsible for any sim locking or data loss sort of problems
wilborama said:
Hi, sorry I can't help with your problem as it seems too complicated to me (noob here) but reading what you wrote sort of alarmed me as I've been reading/watching videos on rooting and I thought that unrevoked (latest version) worked on any desire. It says so on the unrevoked site but you wrote you can't do it on yours because of new build of froyo.
Don't understand that, I'm on vodafone and asked advice to a few people about rooting and nobody told that I couldn't use unrevoked. Are you sure you can't use it. How about you do a factory reset and reflash rom and see how it goes. I do hope you're wrong about unrevoked though as I'm about to use it any day now (building up the courage...) Hope you get your problem solved.
Click to expand...
Click to collapse
Basically on the latest Froyo build from HTC (2.29.405.5) if you use Unrevoked, everything will go fine until it boots out of the bootloader to the actual software. On reboot Unrevoked will say 'Waiting for system to Settle'. This will never dissappear and it will wait for the system to settle forever and ever. However becuase you are branded on Vodafone, the chances are you're not running Froyo build 2.29.405.5, but a slightly older one. This is because when HTC release an update the phone companies have to put their software onto it, the the 2.29.405.5 update was only 5Mb, barely enough for the companies to be even bothered messing around with, so chances are you WOULD be able to root anyway, thanks for commenting.
commando0 said:
well try to reinstall whole software via pc ...............
but check download latest version of official rom
back up your data as ur whole system sofware will be replaced
and do format ur sd in pc ( not a quick format )
hopefully it might resolve ur issues ( otherwise it seems a hardware issue >>>>>)
and i am not responsible for any sim locking or data loss sort of problems
Click to expand...
Click to collapse
Oh I know about data loss, Sim Locking and all that, been there, done that, got the T-Shirt, I've got a Utility on my computer that will unlock my phone and as for Data Loss, Google servers have it all
I've got a bit of an update though, I know your saying it's a hardware error but I think there are two key components here that aren't working.
- The SD Card
- The SIM Card
I have come to believe this, because I managed to use the PB99IMG file to update to the latest Froyo, and now my phone is saying there is an SD in there, but stats about the SD are unavailable in my phone, and also when trying to connect to the network, my phone will not connect to Orange. If I click on Manually Select, and I click on Orange, I get a message saying SIM won't allow connection to this network, if I do it with Automatic however, it just says unable to connect to the network at this time. I'm gutted I haven't been able to fix this yet, it's really annoying me because normally I would be able to sort this, been up all night trying to do it, any help is greatly appreciated.
2.29.405.5 roots absolute fine with unrEVOked - if it didn't I wouldn't be rooted!!
EddyOS said:
2.29.405.5 roots absolute fine with unrEVOked - if it didn't I wouldn't be rooted!!
Click to expand...
Click to collapse
Possibly a problem with my Device or HBoot? Could anyone point me to the correct RRU for me to reset my phone with? I am running the latest software version with a goldcard, the card won't mount when the phone is turned on, thanks.
This is for the 2.29.405.5 RUU
http://www.multiupload.com/LEJCW182AH
EddyOS said:
This is for the 2.29.405.5 RUU
http://www.multiupload.com/LEJCW182AH
Click to expand...
Click to collapse
Really appreciate it mate, thankyou
*Update, I flashed this RRU, it's not working though :/
When you say not working what do you mean? More info needed!
Also, edit the 'Qualcom CDAM' thingy, that means its trying to install modem drivers - sounds you USB-bricked the phone
EddyOS said:
When you say not working what do you mean? More info needed!
Also, edit the 'Qualcom CDAM' thingy, that means its trying to install modem drivers - sounds you USB-bricked the phone
Click to expand...
Click to collapse
Yeah it won't connect in any way USB wise, and when IS ay not working, the OS works fine, connects to the network for the first 5 minutes, SD card won't mount, then after 5 minutes I get locked out of the network, and if I try and connect I get a message saying my sim won't allow connection to Orange :/ Think you can help?
Hy,
today I tried rooting my HTC Desire Z. Until today I didn't modify anything, it was like shipped three years ago when I bought it (no root, S-ON, but officially updated to stock Gingerbread).
So why I decided to root? I had a problem after updating all apps at once: the update process got stuck, I had to pull the battery. After turning it back on, it resulted in bootloop - no good. Tried a lot of things - nothing worked. Finnally I had to do a hard reset. Worked, but all data was lost.
So I decided to now root the phone in order to have the possibility to backup everything with nandroid - to be prepared for the next time
OK, so I searched the net found a lot of infos and the wonderful downgrading guide by strawmetal as described on this post: http://forum.xda-developers.com/showthread.php?t=1178912
I followed all the steps, download all the files. Everything worked fine like described in the guide (I skipped the backup thing, as it is optional and I had nothing to backup). The problem occured in the last step: downgrading (page 10). I chosed method B: "fastboot downgrade". but finally I got stuck when flashing the StockRom.zip: everything seemed to work, but the process stopped with the line: " INFO[RUU]WP,radio,95 " (output of my cmd-window here: http://pastebin.com/7n11dXJx). My HTC Screen showed a grey HTC Logo and green process bar which was about 95% I guess.
I waited about an hour or so, nothing happend. I had to interrupt the command-window by "ctrl+c", pulled the lead and finally had to pull the battery too as the power button did not work either.
Tried to switch it on afterwards - but nothing, really nothing happens. Screen stays black, no LEDs, no vibrations, no bootscreen. Argh!
Did I kill it? Is there anything I can do? What did I do wrong? I don't get it...
I'm using Windows Pro 64bit and used the StockRom linked in the thread above (see post from 1st March 2014): http://cmw.cmfs.me/vision/stock/1.34.707.3/PC10IMG.zip. It was upped again after the original links did not work anymore. It says it is for Desire Z, but now I see it's another version (and has other checksum too): it's 1.34.707.3 instead of 1.34.405.5 which is linked in strawmetals guide. Maybe this is the problem? Unfortunately I can not post to developement section as I'm new to XDA...
Any help appreciated! Thanks!
Maybe a stupid question, but is your battery charged?
And after you insert USB into computer and phone, does your computer detects a device? For me device manager shows: http://i.imgur.com/7HDDPzo.png
Unfortunately it is very possible that your phone is bricked. When flashing firmware, particularly the bootloader or radio, you need to be sure they successfully and completely flash or your phone will not boot. This is why the warnings are there as there is risk, the fastboot method is the safest but a battery pull is a sure way to never have your phone wake again, that is if there was an error or any form of incomplete flash you cannot do a battery pull
So I'm sorry to say that if your phone shows no sign of life you likely will not be able to resurrect it without JTAG
Sent from my Nexus 7 using XDA Premium 4 mobile app
G2 / Desire Z bricked - wrong ROM !?!?!?
Thanks a lot for your answers and sorry for answering so late. OK, I bricked it - that's for sure. :crying:
As everything worked fine until the flashing process stopped I suppose that it was kind of a conflict with the ROM I used. In the original thread it says: "use 1.34.405.5_PC10IMG.zip". The Version which was provided by a user after the original link died was "1.34.707.3_PC10IMG.zip" (MD5 is different!). Maybe this is the issue? I cannot post to developer section until now - so if you think this could have caused the bricking issue, please warn users in the original thread and help saving some G2/Desire Z from bricking. Thanks!
I will buy a new phone now. But this time no HTC !!!
veiwoo said:
Thanks a lot for your answers and sorry for answering so late. OK, I bricked it - that's for sure. :crying:
As everything worked fine until the flashing process stopped I suppose that it was kind of a conflict with the ROM I used. In the original thread it says: "use 1.34.405.5_PC10IMG.zip". The Version which was provided by a user after the original link died was "1.34.707.3_PC10IMG.zip" (MD5 is different!). Maybe this is the issue? I cannot post to developer section until now - so if you think this could have caused the bricking issue, please warn users in the original thread and help saving some G2/Desire Z from bricking. Thanks!
I will buy a new phone now. But this time no HTC !!!
Click to expand...
Click to collapse
.
It should work with both 1.34 ROMs.
But maybe, it was a step before that which make it fail...
It wasn't so much the stock ROM that bricked the device it was the battery pull of an incomplete radio flash. Bootloader needs to run a radio check in order to boot, no radio - no boot.
If something like this happens to you in the future just run the fastboot commands again, do not reboot, there are many reasons it can get stuck but no damage will occur until reboot
The good news is desire z has become cheap, you can buy an old broken one of eBay for probably less than $40 and just swap logic boards
Either way, best of luck in the future!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks for your answers. I think I won't have any HTC devices because the original problem (updating caused bootloop) is not acceptable for me. Had to do a hard reset to get this solved and had a lot of problems after this issue. Anyway:
thanks and closed!
Hi all i know someone will not be happy i have asked this question that is probs one of the most asked on here from Nubs like me lol.... Basicly i recently got my rooted htc one m8 S-on back, i was planning to sell it so tried to remove the Root from the phone i have somehow managed to Brick it, its under HTC_001 it didnt have a main fw number so i did what others have and read it from the about software section on my phone wich give me 1.54.401.10....... Well i ended up download that one something went wrong either way now im left with a phone that only goes into Hboot and i can access the recovery what is TWRP i can connect the usb and get onto my Sd card using mount but ive tried and tried to get no joy.... Sorry for the nub questions i did go abit out of my knowledge people say ADB on other forums, im not very clued up with it other than changing the recoverys ive watched youtube vids ect no joy Please can someone give me a Simple Tut or link to help me ive tried following threads and still got no joy http://forum.xda-developers.com/showthread.php?t=2701376 So now i ask the PRO'S please help lol
mikem2273 said:
Basicly i recently got my rooted htc one m8 S-on back
Click to expand...
Click to collapse
Got it back from where???
mikem2273 said:
Sorry for the nub questions
Click to expand...
Click to collapse
No need to apologize for the n00b questions. However, the huge run-on sentences are another story. Take some time to type a post with proper punctuation and sentence structure. It will make it easier for you to get you point across and for us to help.
mikem2273 said:
now im left with a phone that only goes into Hboot and i can access the recovery what is TWRP i can connect the usb and get onto my Sd card using mount but ive tried and tried to get no joy....
Click to expand...
Click to collapse
Tried and tried what? If you aren't specific in what you have done, what are we supposed to do, guess? Be detailed and be specific when asking for help.
You aren't in bad shape at all if you have recovery and can mount SD. Just put a software 1.x based ROM on the SD and flash it in TWRP.
---------- Post added at 01:48 PM ---------- Previous post was at 01:42 PM ----------
mikem2273 said:
people say ADB on other forums, im not very clued up with it other than changing the recoverys
Click to expand...
Click to collapse
Just use the XDA search function, and search "adb beginner" to find a number of good adb/fastboot tutorials aimed at just that, beginners.
But if you've used fastboot to install recovery, the other commands aren't any harder. Its just a matter of just knowing what commands to use for a given situation.
If you can mount SD, I don't even think you need adb. But its a very valuable tool to know, and can help in a lot of situations.
Thanks for the response, well i tried a stock rom im not sure where i went wrong tbh i put it on the internal sd and the file would not show up inTWRP i then had a back up and copied and pasted the files from the Stock rom into the back up and tried to install it and thats where it messed up i am crap at this kind of thing i rooted it no problem i thought unrooting would be easier, adb is a bit confusing with me if there was a way i could put a file onto my sd card in zip format and open it i just tried the original one i downloaded to get loads of red commmads saying
E;unable to stat '/and-sec/;555?.??/m?? and so on a load more random numbers
Sorry i am not very on ball with this should of just left it how it was lol
Right update time...... so i have got the phone back working by flashing a new rom but my phone massively lags on boot up, i think my firmware files are corrupt i cant get wifi either ive red about fixes but all need S-off yet i dont want to pay 25 dollars is this the only way to do this ?? i cant put firmware files on my hone without the s-off such hard work and effort would rather pay someone to fix it lol
unable 2 load my one m8 to fasboot
pls, i av bein unable to access fastboot on my device; i cant unlock bootloader,s-off e.t.c......what can i do; i really need help...
d screen displays black with fastboot mode @ d lower left corner
nnamathy said:
pls, i av bein unable to access fastboot on my device; i cant unlock bootloader,s-off e.t.c......what can i do; i really need help...
d screen displays black with fastboot mode @ d lower left corner
Click to expand...
Click to collapse
Dude ..who are you talking too ?? your post is useless and makes no sense.
Start your own thread ... post an exact description of what you did and whats wrong along with pictures / bootloader / anything that might be of some help
mikem2273 said:
Thanks for the response, well i tried a stock rom im not sure where i went wrong tbh i put it on the internal sd and the file would not show up inTWRP i then had a back up and copied and pasted the files from the Stock rom into the back up and tried to install it and thats where it messed up i am crap at this kind of thing i rooted it no problem i thought unrooting would be easier, adb is a bit confusing with me if there was a way i could put a file onto my sd card in zip format and open it i just tried the original one i downloaded to get loads of red commmads saying
E;unable to stat '/and-sec/;555?.??/m?? and so on a load more random numbers
Sorry i am not very on ball with this should of just left it how it was lol
Click to expand...
Click to collapse
You sentence structure (or lack of it) is still making it hard to understand what you are trying to tell us. If you can't even be bothered to type a proper sentence; how do you expect us to take the time to help you? Honestly, most other requests for help on this forum get much more response. I think many folks are just walking away from this thread without helping, because they can't understand you due to your writing style.
Your lack of specificity also makes it crippling to try to help. What stock ROM, and where did you get it from?
If you got a stock nandroid, you then need to extract the files from the zip and place them in exactly the right folder, otherwise TWRP won't see it. And you do not use the TWRP "INSTALL" function with a stock nandroid, you use the "RESTORE" function.
A flashable ROM zip, in contrast to a nandroid, can be placed anywhere on internal storage or removable SD, and TWRP will see it and flash it using the INSTALL function.
Its very easy to push a ROM zip to the phone with adb. I already told you how to find BEGINNER tutorials on how to use adb. Don't expect to be spoonfed information that is already readily available on XDA. If you have a specific question regarding adb, ask it. Otherwise just saying "adb is confusing" is not going to help you.
---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------
mikem2273 said:
Right update time...... so i have got the phone back working by flashing a new rom but my phone massively lags on boot up, i think my firmware files are corrupt i cant get wifi either ive red about fixes but all need S-off yet i dont want to pay 25 dollars is this the only way to do this ?? i cant put firmware files on my hone without the s-off such hard work and effort would rather pay someone to fix it lol
Click to expand...
Click to collapse
Your firmware files aren't "corrupt". They are just outdated, and don't match the ROM your flashed.
OTAs are available for your version. An option if you don't want to s-off, is to return to stock ROM and recovery, and OTA to update the firmware. It seems you are having problems installing the stock nandroids, but I think you just need to properly follow the instructions from the stock nandroid collection thread.
Otherwise, you are stuck running ROMs that are based on 1.x software. Running anything more recent will result in long boot times and broken WiFI, as you've experienced.
Dammit i know excatly where i went wrong and what you meant by you have to open the file up and adb the right files to the right places............ $%$% i have now fully ruined the phone i think i turn it on i get a White screen the phone then goes full black screen and does nothing...... i have connected the phone via usb to the laptop, the laptop notices the phone and usb i click on the phone in my computer nothing is there when it opens i have also gone onto adb and done the "adb devices" and it does not show on the list, is there anything i can do with this now, i am very gratefull for the help even though i haven't been specific and guessed my way through alot of it like a nob,
adb only works when booted into OS or in recovery.
Alternately, if you have an SD card reader, use it to load a ROM zip onto the SD from your computer. Then place SD in the phone, boot TWRP, and flash the ROM.
redpoint73 said:
You sentence structure (or lack of it) is still making it hard to understand what you are trying to tell us. If you can't even be bothered to type a proper sentence; how do you expect us to take the time to help you? Honestly, most other requests for help on this forum get much more response. I think many folks are just walking away from this thread without helping, because they can't understand you due to your writing style.
Click to expand...
Click to collapse
At this point I have to assume it's an inability to communicate clearly, not an unwillingness. You have a lot more patience than most for even trying.
redpoint73 said:
adb only works when booted into OS or in recovery.
Alternately, if you have an SD card reader, use it to load a ROM zip onto the SD from your computer. Then place SD in the phone, boot TWRP, and flash the ROM.
Click to expand...
Click to collapse
@redpoint73: I'm in his exact same position...hopefully, I can communicate this a little better...at least I'll try. LOL
Background: Rooted, S-Off (via Sunshine), , TWRP 2.8.1.0, was running CleanROM (on the 444 firmware) and tried installing Vanir 444. I did a factory reset and I'm pretty sure I might have went into Advanced and wiped System as well (from the reading I've done, I shouldn't have done that) ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted. When the phone went to reboot, it went to the usual white HTC screen, then went black and never moved past that point.
As you advised in an earlier post, I held down Power/Vol up until the white HTC screen appears. I waited until the screen went black then held Vol down for several minutes but bootloader never came up.
My computer recognizes the phone when I plug it in, Windows explorer shows both "Internal" and "SD card", with Internal basically empty and SD card showing all my files. Since I can't get into bootloader, "adb devices" doesn't bring anything back.
Any suggestions you might have would be hugely appreciated - hoping to avoid having to head to a local Verizon store and see what they can do! If I missed any background or details, let me know and I'll elaborate.
TIA!
sigmaxaa said:
@redpoint73: I'm in his exact same position...hopefully, I can communicate this a little better...at least I'll try. LOL
Click to expand...
Click to collapse
I can't imagine it being any worse than the previous guy!
Seriously though, your post would have been better served in its own thread, or almost any other relevant thread. Couple reasons for this:
1) My experience, when folks say they are "in the exact same position", "I have the same problem", etc. they are in fact virtually never the exact same condition. There are far too many variables (M8 variant, hboot version, software/firmware version, how you got to the current condition, and many more) for your condition to be "exactly the same". And for that matter, when folks say they have the "same problem" it in fact is most often a completely different cause, and different fix. Do yourself a favor, and don't say "me too" when posting a problem.
2) The OP basically chased everyone away with his horrible diction. Help threads in this section normally get considerable traffic and assistance. I'm the only one helping this guy, because apparently I'm the only one patient enough to try to decipher his ramblings. By attaching your post to his, you've pretty much cursed your issue to obscurity as well.
sigmaxaa said:
As you advised in an earlier post, I held down Power/Vol up until the white HTC screen appears. I waited until the screen went black then held Vol down for several minutes but bootloader never came up.
Click to expand...
Click to collapse
If you got this from a post of mine in another thread, its (normally) accompanied with the statement that failure to get into bootloader is virtually always a matter of user error (not getting the timing right). Simply stated, if the screen still comes on, you can get into bootloader. So just repeat the steps until the bootloader screen comes up. You either didn't start pressing vol down fast enough; or let go of it too early (don't let go until the bootloader screen appears).
sigmaxaa said:
My computer recognizes the phone when I plug it in, Windows explorer shows both "Internal" and "SD card", with Internal basically empty and SD card showing all my files. Since I can't get into bootloader, "adb devices" doesn't bring anything back.
Click to expand...
Click to collapse
Once you get the timing right to get into bootloader, and from there recovery, we should be in good shape.
You can likely recover by transferring a known good ROM to the SD card, and just flashing from custom recovery. Or just restore your nandroid.
sigmaxaa said:
Any suggestions you might have would be hugely appreciated - hoping to avoid having to head to a local Verizon store and see what they can do!
Click to expand...
Click to collapse
I doubt Verizon can help. And since the phone was put into this situation by your own actions (mods you performed) its really your responsibility to fix it, not theirs.
redpoint73 said:
I can't imagine it being any worse than the previous guy!
Seriously though, your post would have been better served in its own thread, or almost any other relevant thread. Couple reasons for this:
1) My experience, when folks say they are "in the exact same position", "I have the same problem", etc. they are in fact virtually never the exact same condition. There are far too many variables (M8 variant, hboot version, software/firmware version, how you got to the current condition, and many more) for your condition to be "exactly the same". And for that matter, when folks say they have the "same problem" it in fact is most often a completely different cause, and different fix. Do yourself a favor, and don't say "me too" when posting a problem.
2) The OP basically chased everyone away with his horrible diction. Help threads in this section normally get considerable traffic and assistance. I'm the only one helping this guy, because apparently I'm the only one patient enough to try to decipher his ramblings. By attaching your post to his, you've pretty much cursed your issue to obscurity as well.
If you got this from a post of mine in another thread, its (normally) accompanied with the statement that failure to get into bootloader is virtually always a matter of user error (not getting the timing right). Simply stated, if the screen still comes on, you can get into bootloader. So just repeat the steps until the bootloader screen comes up. You either didn't start pressing vol down fast enough; or let go of it too early (don't let go until the bootloader screen appears).
Once you get the timing right to get into bootloader, and from there recovery, we should be in good shape.
You can likely recover by transferring a known good ROM to the SD card, and just flashing from custom recovery. Or just restore your nandroid.
I doubt Verizon can help. And since the phone was put into this situation by your own actions (mods you performed) its really your responsibility to fix it, not theirs.
Click to expand...
Click to collapse
Thanks for the reply, I do appreciate it. I was able to get it working (after dozens of attempts) and you're absolutely correct...it's all in the timing.
The following is a description of the events that lead to the brick. I am writing here in utter desperation and have tried almost everything available on the forums and around the web. Requesting assistance from any person in India or anywhere who knows the device well and can help me.
1) I had been using HTC One X for around two years. It went dead slow and I went looking out for options. Found cleaners and other software but nothing helped much.
2) I decided to flash a ROM like I have done on my Micromax A116(Indian mobile brand, available on XDA forums as well).
3) After a bit of research I found that I have to unlock the bootloader and install recovery(installing the recovery isnt new to me)
4) I then unlocked the bootloader and tried installing the ROM.. http://forum.xda-developers.com/showthread.php?t=2753450
5) The installation was a failure due to some partition error.
6) I looked around XDA and found a solution.
7) This is where I goofed up.
I was unable to install the ROM and so I wiped everything using philz touch recovery. It even wiped the backup(I forgot I do not have the option of memory card on this Indian model of HTC One X).
Now after the restart, nothing comes up. I tried flashing other recovery like TWRP 2.8 which is flashing fine however, am unable to do anything except go in bootloader(fastboot, Hboot etc) or inside the recovery.
I read about RUUs, and how to make my phone detectable in PC and use ADB to copy ROM and re-flash it but nothing works at the moment. After a week of trying myself, I am here if anyone can help me out. Would deeply appreciate if anyone can find some time and check out on my issue.
I have HTC One X: CID HTC__038
Hboot: 1.73+
S-on
BhatiaPulkit said:
The following is a description of the events that lead to the brick. I am writing here in utter desperation and have tried almost everything available on the forums and around the web. Requesting assistance from any person in India or anywhere who knows the device well and can help me.
1) I had been using HTC One X for around two years. It went dead slow and I went looking out for options. Found cleaners and other software but nothing helped much.
2) I decided to flash a ROM like I have done on my Micromax A116(Indian mobile brand, available on XDA forums as well).
3) After a bit of research I found that I have to unlock the bootloader and install recovery(installing the recovery isnt new to me)
4) I then unlocked the bootloader and tried installing the ROM.. http://forum.xda-developers.com/showthread.php?t=2753450
5) The installation was a failure due to some partition error.
6) I looked around XDA and found a solution.
7) This is where I goofed up.
I was unable to install the ROM and so I wiped everything using philz touch recovery. It even wiped the backup(I forgot I do not have the option of memory card on this Indian model of HTC One X).
Now after the restart, nothing comes up. I tried flashing other recovery like TWRP 2.8 which is flashing fine however, am unable to do anything except go in bootloader(fastboot, Hboot etc) or inside the recovery.
I read about RUUs, and how to make my phone detectable in PC and use ADB to copy ROM and re-flash it but nothing works at the moment. After a week of trying myself, I am here if anyone can help me out. Would deeply appreciate if anyone can find some time and check out on my issue.
I have HTC One X: CID HTC__038
Hboot: 1.73+
S-on
Click to expand...
Click to collapse
Download this read very carefully and follow each and every step in that file ...
after switching to new layout flash the rom you had downloaded ..and ur HOX will come back to life
to get a hang of new layout read here
HTX One X Stuck in Bootloop
onex master said:
Download this read very carefully and follow each and every step in that file ...
after switching to new layout flash the rom you had downloaded ..and ur HOX will come back to life
to get a hang of new layout read here
Click to expand...
Click to collapse
I Tried the steps listed in the PDF but no go..
I am still stuck at the boot screen and the CM 12 logo is all I get. I never get past that. I have tried multiple flashes and installs but no go.
I followed the instructions step by step and word by word as per http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru but still no go.
Any help will be highly appreciated.
Dragon_Knight said:
I Tried the steps listed in the PDF but no go..
I am still stuck at the boot screen and the CM 12 logo is all I get. I never get past that. I have tried multiple flashes and installs but no go.
I followed the instructions step by step and word by word as per http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru but still no go.
Any help will be highly appreciated.
Click to expand...
Click to collapse
after flashing rom have u flashed the boot.img
if not then flash it using fastboot flash boot boot.img
Cannot thank you enough onex master
onex master said:
after flashing rom have u flashed the boot.img
if not then flash it using fastboot flash boot boot.img
Click to expand...
Click to collapse
Dear onex master,
I had given my phone to service center and got the phone today after they failed to bring it back and said nothing can be done now.
And that is when I came back here to find your post and thought of giving it a try before I go ahead and buy a new phone. Your guidance is so perfect and accurate that my issue is finally resolved now. I got my phone back. Many thanks to you. Much much appreciated. May God bless you dear..
BhatiaPulkit said:
Dear onex master,
I had given my phone to service center and got the phone today after they failed to bring it back and said nothing can be done now.
And that is when I came back here to find your post and thought of giving it a try before I go ahead and buy a new phone. Your guidance is so perfect and accurate that my issue is finally resolved now. I got my phone back. Many thanks to you. Much much appreciated. May God bless you dear..
Click to expand...
Click to collapse
Hi man, im also in the same situation so can please you please elaborate the steps to get back working phone.
Thanks.
Please refer to the pdf link by one x master/Tanuj. You will get your phone back..just follow step by step. Use same software and recovery as mentioned by him in pdf..
Sent from my Micromax A116 using XDA Free mobile app