Related
I tried to root through the odin method and I can get into CWM but when I install zip then reboot it stops at the SAMSUNG screen...any help will do I need my phone by tomorrow at the latest also Im with Best buy warranty so should I just break my phone and get another ?
Boot into recovety try data/cache wipe 3 times each then reboot.
---------- Post added at 03:50 PM ---------- Previous post was at 03:50 PM ----------
Also which rom are you trying to install?
What u running 2.3.5? Or 2.3.6?
IF 2.3.5 than i would unroot it and run 1click root.
GeezyF.Ladies said:
I tried to root through the odin method and I can get into CWM but when I install zip then reboot it stops at the SAMSUNG screen...any help will do I need my phone by tomorrow at the latest also Im with Best buy warranty so should I just break my phone and get another ?
Click to expand...
Click to collapse
stock one from http://forum.xda-developers.com/showthread.php?t=1340526
appdroid said:
What u running 2.3.5? Or 2.3.6?
IF 2.3.5 than i would unroot it and run 1click root.
Click to expand...
Click to collapse
2.3.6 yeah I've heard one click is awesome
Your able to get into recovery? So as i said boot into recovery wipe data/cache 3 times then reboot. If still no go flash the stock tar with odin again and reroot. You could also try just flashing the stock recovery.tar and boot into it. Then wipe data, and cache. Then reboot
silver03wrx said:
Your able to get into recovery? So as i said boot into recovery wipe data/cache 3 times then reboot. If still no go flash the stock tar with odin again and reroot. You could also try just flashing the stock recovery.tar and boot into it. Then wipe data, and cache. Then reboot
Click to expand...
Click to collapse
k tried the data/cache 3 times each and rebooted and nothing. well how do I put stock tar on my sd card if I cant get my phone on to connect with my pc storage ?
The stock tar you need to put on your pc. And you need to get your phone into download mode. You use odin on you pc with your phone in download mode. To flash the stock recovery tar. To be honest you need to just use odin to reflash the stock tar. Again. Go to the thread woth the stock tar and follow the instructions again
haha duh on my part I was just so scared that I panicked but its downloading now and im going to try and flash back to stock when it is done. thanks for your patience/help slvwrx.....upon more research I think I got a bad recovery tar bc I cant open it its just a white page with a folded corner and I think I saw someone with this problem in the thread and said you have to extract zip
any other ideas ?
anyone get tar files from another site because when I try to open mine they all say cannot open file does not seem to be a valid archive.
You cannot be serious with these questions? You don't open the tar file you put it in Odin. You really need to put some effort into researching what you are trying to do with your phone. Your lack of prior research is why you are having problems. Not trying to be an ahole but you really need to READ everything in these forums before you try to do anything to your phone or you seriously risk bricking it and not being able to recover it. It is nearly impossible to brick these phones but if you have not done the requisite research here then you will end up in essence with a brick because you have no clue how to recover it from your own mistakes. I read these forums for a solid week before I even connected my phone to my laptop and I am an IT Engineer but that doesn't make me an Android expert so I learned from the awesome people here that know more than I and are freely willing to share their knowledge. Take my word for it any/all information you would ever need to fix your phone is all right here for the reading courtesy of the great devs and enthusiasts here on the site.
Sent from my SAMSUNG-SGH-I957 using XDA App
Blackberrynomore said:
You cannot be serious with these questions? You don't open the tar file you put it in Odin. You really need to put some effort into researching what you are trying to do with your phone. Your lack of prior research is why you are having problems. Not trying to be an ahole but you really need to READ everything in these forums before you try to do anything to your phone or you seriously risk bricking it and not being able to recover it. It is nearly impossible to brick these phones but if you have not done the requisite research here then you will end up in essence with a brick because you have no clue how to recover it from your own mistakes. I read these forums for a solid week before I even connected my phone to my laptop and I am an IT Engineer but that doesn't make me an Android expert so I learned from the awesome people here that know more than I and are freely willing to share their knowledge. Take my word for it any/all information you would ever need to fix your phone is all wright here for the reading courtesy of the great devs and enthusiasts here on the site.
Sent from my SAMSUNG-SGH-I957 using XDA App
Click to expand...
Click to collapse
any criticism is good criticism to me thanks for giving me the cold hard facts and to be truthful I did jump into this early coming from an iphone 4 and all the ones before that and jailbreaking them I thought it'd be easy and it was I just 2nd guess myself all the time. my mistake was following the vid a ruebarb posted in the thread and I followed it to a T .it wasnt till he updated his video and said that his method was for ''already'' rooted users so after getting konane's stock tar flashed in odin I was back to stock re-did the 2.3.6 method got it done stayed stock rooted for 2 days then just about 30 mins ago I went head and jumped on RED SONIA!
again thanks for your input and to care enough to set a noob stright
also Cdshep pretty much found the problem after having a personal chat with me he saw what I was trying to say I'm just not really good with wording or spelling I just recently winged myself of of concerta(ADHD pills) and so my mind moves faster than I can type or right and I confuse myself but its better than the life of a zombie!
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. You MUST use this interim CWM version for the moment, as the others do not work properly. Some things like USB mount dont work in this interim version, but the important functions like wipe and flash, backup and restore, and restart do work. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
bump... i see US users still asking.
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Worked great for me
Sent from my HTC VLE_U using xda premium
So if we root and flash a custom ROM is there any way to get the phone back to factory state, and get rid of the *TAMPERED* and *UNLOCKED* notification??
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
cyberchuck9000 said:
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
Click to expand...
Click to collapse
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
nickmv said:
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Click to expand...
Click to collapse
+1
androidcues said:
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
Click to expand...
Click to collapse
If you need to perform a hard reset on the One S, you hold down the power button for about 7-10 secs.
First of all, thanks for this thread...I used the HTC One S All in one tool kit to unlock my phone, unfortunately I miss understood one of the directions(#5) and stopped using the tool kit and followed another thread, much to my surprise, my bootloader is unlocked, hooray My question is, how do I get back to the original state if that is possible? The reason I ask, is I would like to go back and do it correctly...I used better terminal emulator to see if I had root, but all I got was the $ sign instead of the # sign So I would like to start over...
Thanks in advance for the help
I'm honestly not sure what the procedure is for relocking an HTC bootloader. Perhaps do some Google research on some of the latest models, and I bet you'll find something.
That being said, once you unlock the bootloader a single time, the best you can do is go to **RELOCKED** state. You'll never get back **LOCKED**. Once it's gone it's gone. I'm curious about the **TAMPERED** message though. That's an ugly word.
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
suhailtheboss said:
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
Click to expand...
Click to collapse
Uh oh that doesn't sound good
Sent from my HTC VLE_U using xda premium
yeah, tried reflashing both CWM & stock recovery. phone still boots to CWM everytime.
Luckily i can still access the phone via ADB, (while in recovery) so i'm sure i'll be able to sort it out. just need to take a fresh crack at it tomorrow. gonna switch back to my galaxy nexus tonight. (oh wait, i dont have any other phones that use microsim)
haha.
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
nickmv said:
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. Some things like USB mount dont work, but the important functions like wipe and flash and restart do. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart. I cant speak for the non-interim solutions, but from what I can gather, they are problematic, so avoid them for now.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
Click to expand...
Click to collapse
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Thongvilay said:
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Click to expand...
Click to collapse
That step is only if you want to flash ROMs, or need to wipe cache, dalvik, etc. CWM is used for flashing and recovery/backup purposes. If you're not using ROMs yet, then you have no need for it.
nickmv said:
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
Click to expand...
Click to collapse
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
suhailtheboss said:
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
Click to expand...
Click to collapse
Wow, I have no idea dude. That sounds kinda crazy. Hopefully all will be well in the future and you won't come across it again.
the only variable i can think of is that i did have the phone about a week before launch. HTC mailed it to me directly.
I thought maybe that had somethign to do with it, but as far as i can tell the phone was the final shipping version.
I sent you a PM, trying to find a solution.
Hey everyone.
Im generally pretty savvy with androids. I rooted and S-offed my HTC Desire, I had a nexus S for a bit until it got ran over... Now im stuck with this Galaxy S 4G, which has been nothing but headaches because for some reason... this thing is impossible to root to me. Ive tried Hemidall, Super1clicks, Odin etc..
Can someone please just point me in the direction of rooting this POS? Im hoping that once its rooted and running stock, I wont hate this thing as much... because so far, Its a horrible purchase.
I just need someone to post a link to where I need to be. Ive searched.. and im absolutely lost. Even the Rootz wiki was useless to me.
Thanks.
Model Number - SGH-T959W
Android Version 2.3.6
You might not have any luck this is the T-959V and your phone might not be supported
Sent from my SGH-T959V using xda app-developers app
http://forum.xda-developers.com/showpost.php?p=28566711&postcount=15
Read that then understand what bhundven means by DONT FLASH BOOTLOADERS!!
You can use the heimdall one clicks he created to get root access and then flash any rom that DOESNT HAVE BOOTLOADERS INCLUDED. That means do not use gremlin remover period. Once you get rooted make a backup and keep it stored in as many places as possible. If you flash the ics variants you will have to use the stock kj6 HOC and then need to flash the HOC for antonx kernel to get root back. At that point you can flash your nandroid or whatever rom you want. AGAIN AS LONG AS IT DOESNT HAVE BOOTLOADERS included.
eollie said:
http://forum.xda-developers.com/showpost.php?p=28566711&postcount=15
Read that then understand what bhundven means by DONT FLASH BOOTLOADERS!!
You can use the heimdall one clicks he created to get root access and then flash any rom that DOESNT HAVE BOOTLOADERS INCLUDED. That means do not use gremlin remover period. Once you get rooted make a backup and keep it stored in as many places as possible. If you flash the ics variants you will have to use the stock kj6 HOC and then need to flash the HOC for antonx kernel to get root back. At that point you can flash your nandroid or whatever rom you want. AGAIN AS LONG AS IT DOESNT HAVE BOOTLOADERS included.
Click to expand...
Click to collapse
I have no idea what youre talking about. Sorry
I used the Hemidall, and only got an unrooted Tmobile rom.. Im not sure where exactly i get root from this
Meh, forget it... im selling this phone. There is no convincing me to ever buy anything from Sammy again unless its a Nexus line.
HTC or Nexus forever.
Thanks guys
Reading is hard
"Can I get step by step directions please?"
Sure, here you are!
"What?! Your not going to remotely root my phone for me? F this place"
Good luck sir, you have the patience of a saint and the drive of a tiger!
OK let's be honest you gave up kinda quick.......
The forum that eollie linked you to was a forum talking about the phone that you bought, which is an apparent offshoot of the t-959v and according to what Masonite found out, "our" roms work on the t-959w but you cannot flash the bootloaders.
Here is the one click link http://forum.xda-developers.com/showthread.php?t=1358498 just boot into download mode and use this but absolutely don't flash bootloaders and it should be OK, no promises.
Eollie was right for linking you there, all the info you needed about your model phone was on that forum, that one click is in the dev sticky which everybody should read.
There has been a flood of people not researching a little bit first before posting and that's why people flamed you but you should not give up, its a good phone and our devs are dedicated and have put in a lot of time on this model, you should be happy your phone can even support all the great roms that are available.
I'm not being mean but seriously, come on, all the info is there, no need to get mad.
Sent from my cm_tenderloin using xda premium
Edit: or Google search how to use heimdall if your confused, I learn off a damn YouTube video..........
Our devs didn't create heimdall and don't support it but it is a great program and the dev has to build the individual one click for the phone, we should be happy to have it that easily available.
Reading the whole thread you got linked to is really hard. Phone-bricking hard
FBis251 said:
Reading the whole thread you got linked to is really hard. Phone-bricking hard
Click to expand...
Click to collapse
Hahaha I know but but I believe in you lmao
Sent from my cm_tenderloin using xda premium
You'll need to flash one of the back to stock files that you got linked to in that thread which will put you on stock GB with no root. DO NOT FLASH THE BOOTLOADERS. You'll very likely brick if you do.
After this download the AntonX kernel from bhundven's one click thread and flash that. That will give you a custom kernel with CWM built in and root.
Needless to say, this is all for the SGH-T959V which theoretically should work on the SGH-T959W. As you'll read any disclaimer on this forum, you're resposible for anything you flash and the damage that may occur to your device.
Thanks for that fb I forgot a few steps if he wants to be on mtd roms, I assumed he could read from that point............ but your right for knowing better
Sent from my cm_tenderloin using xda premium
Thank you very much, and I'm sorry for getting angry. I've had this phone for almost 4 months now, and haven't been able to do anything with it. Quite frustrating.
So, I currently have the Tmobile ROM on my phone, so I'm halfway there it appears!
I'm going to download the other ROM as soon as I get home.
Thanks so much! Next up.. Learning to flash with Odin, and not ROM manager.
It seemed like everything I tried wasn't working with 2.3.6. Superoneclick etc.
I was waiting for a new exploit, but it never came. I tried YouTube tutorials, text directions.. Everything would fail, or give me "read only" errors. I feared bricking, so I stopped.. But I searched the forum and came across the thread he linked me to, but it said no bootloaders, and all the ones I saw had bootloaders. Wasn't until tonight that I noticed it's a 2 part flash process, with the second being the bootloaders.
I think I started this thread at 3am.
Lesson learned.
In heimdall, you can click a little box that says "flash bootloaders" to toggle flashing them on and off! .... or maybe it was odin? I can't remember... been a while since I used them!
After being away for the weekend, I came home, and BAM... fully rooted. Amazing! and FINALLY!!!
Thanks everyone for your help...
I just have another issue.
I wanna flash this ROM http://forum.xda-developers.com/showthread.php?t=1305145
It says its CWM.. but there is a huge disclaimer that we shouldn't use ROM Manager on the development page, which is a bit confusing. Since this ROM isnt Odin flashable... what do i do?
Thanks again.
So I was confused about this when I first started. I'm not at my computer but I can help. In order to flash Roms via cmw you have to turn off your phone hold both volume rockers on the phone then hold the power button and hold till you get into cwm recovery. That will get you into cmw recovery mode. Then wipe data factory rest, from there go back to the main menu and select the install zip from sd card and find the zip file you want to flash and select it and install. Should be good to go.
Sent from my SGH-T959V using xda app-developers app
Nevermind... im a complete goon. I got it, lol.
Thanks
hey everyone!
yesterday, I got really tired of froyo so I said ''f$%? it, lets try to root my phone and install jelly bean, that look really slick!''
. well looks like everyone as to start somwhere..
so my problem right now, I am stuck at the custom LG logo, I cant hard reset and even my recovery boot but the menu wont pop up and simply restart my phone..
basicaly, I feel screwed right now does anybody can help me on this?
it is probably something super stupid and simple but I can'T find any solution so I decided to join this forum for a bit of support..
EDIT: my mistake, it went in the wrong section
thx a bunch!
Usually run this when I cluster f my phone
http://forum.xda-developers.com/showthread.php?t=1590523
thanks for the cue, I will also try this. and keep you posted if it worked or not..
better way to learn is to make mistakes!
http://forum.xda-developers.com/showthread.php?t=1180331
ok, most of the link to download the needed files are dead... I might have to rely on your support guys.
the http://forum.xda-developers.com/showthread.php?t=1180331 thread didnt helped enough..
Did you install the adampk rom?
Sent from my LG-P999 using xda app-developers app
no I haven't...
so far , what I did is
root the pone with the one clicker (wich was a success)
did the recovery with the clockworkmod recovery thing,
restarted and exectued this website's tutorial to jellybean (start with WWW stuff.androidauthority.com/g2x-p999-t-mobile-cyanogenmod-10-cm10-unofficial-115536)
and then, look like it failed..
this morning, I managed to get back to the recovery boot screen and found that if I press the house icon it show up a menu.. but this menu giving me access to reboot, wipe cache, data or install update.zip (which was supposed to fix my problem) but this menu is blued out and unaccessible..
dunno if it helped..
right now, I am trying to get acces to my phone doing the no battery boot thing but my pc doesnt seem to recognize my phone + I am at work hehe so I am pretty much limited in acces due tu the it protection and firewall stuff
I am gonna try to redo that stuff tonight at home but meanwhile, if any of what I described may give you a clue on how to help me, I really appreciate the effort!
thanks again for the support guys, I know it can be a pain sometimes to help people screwing some beginner stuff like I probably do right now
dubmah said:
WWW stuff.androidauthority.com/g2x-p999-t-mobile-cyanogenmod-10-cm10-unofficial-115536)
and then, look like it failed
Click to expand...
Click to collapse
I say you needed to use the g2x android development forums on this site to find a suitable jb rom, not this other site. The one click method isn't very stable, so nvflash is most definitely what you need to try to get working. There are very thorough tutorials on how to get that to work. Do you know which clockwork recovery version you have installed? Should be 5.0.2.0. Once you get home, I suggest you read read read. Do as much research you can to make sure you can follow nvflash instructions to the letter. I know I personally spent about a week researching to make sure I had a solid understanding of the procedure.
I recommend getting nvflash going to get clockwork properly installed, then download a rom from xda, nowhere else. I would even say use a gb rom before trying a jb ...the jb roms are hackfest versions, so they have (from my experience) much poorer battery life, and lack hardware acceleration. Netflix and many 3d games won't work. You can use adampk or mazout's roms but they don't have working radio, i.e. no phone/SMS functionality.
Sent from my LG-P999 using xda app-developers app
dubmah said:
no I haven't...
so far , what I did is
root the pone with the one clicker (wich was a success)
did the recovery with the clockworkmod recovery thing,
restarted and exectued this website's tutorial to jellybean (start with WWW stuff.androidauthority.com/g2x-p999-t-mobile-cyanogenmod-10-cm10-unofficial-115536)
and then, look like it failed..
this morning, I managed to get back to the recovery boot screen and found that if I press the house icon it show up a menu.. but this menu giving me access to reboot, wipe cache, data or install update.zip (which was supposed to fix my problem) but this menu is blued out and unaccessible..
dunno if it helped..
right now, I am trying to get acces to my phone doing the no battery boot thing but my pc doesnt seem to recognize my phone + I am at work hehe so I am pretty much limited in acces due tu the it protection and firewall stuff
I am gonna try to redo that stuff tonight at home but meanwhile, if any of what I described may give you a clue on how to help me, I really appreciate the effort!
thanks again for the support guys, I know it can be a pain sometimes to help people screwing some beginner stuff like I probably do right now
Click to expand...
Click to collapse
Boot into recovery, there should be an option to format or wipe system. Do that then flash the ROM. It won't boot if you flash it over stock.
Also, use the paranoid android rom found in the development section, same cyanogenmod base but works better.
Sent from my Nexus 7 using Tapatalk HD
great ! thx for the advices ! yeah I Will read some more first, making sure I do thing properly, for now, I will try to revert at least to my backup and wait til I know what I'm doing!
thx again, I keep you up about the progress !
progress!! .. I tried to start my phone without the battery.. my pc recognized the phone for about 10sec and then the icon disapeared and until then, nothing I plug I start there is no way I can make my pc to recognize the phone...
does this happened to anyone before?
allright! I have bean reading about the NVFlash! that help A LOT! actually it almost fixed my thing! the phone is now unbriked YAY
I just keep replying to myself incase there is another guy who dont know crap about the obvious, if it can help the thread worth it
I used this tutorial to fix things,
http://forum.xda-developers.com/showthread.php?t=1248644&highlight=nvflash+steps
My main issue was the APX driver wich wasnt installed.. now I know bit more, I still have issue but luckily things goes forward so it gave me the boost to keep working on
but I face a new problem so maybe some of you might be able to help on that new issue
I am from montreal and here in quebec we have videotron instead of t-mobile and since I used a t-mobile boot it looks like my sim card is not recognized anymore..
is there a way to fix that? am I supposed to find a videotron thing?
hope it helps
dubmah said:
I used a t-mobile boot it looks like my sim card is not recognized anymore..
is there a way to fix that? am I supposed to find a videotron thing?
Click to expand...
Click to collapse
What do you mean by "T-Mobile boot" and "videotron thing?"
Sent from my LG-P999
---------- Post added at 10:09 PM ---------- Previous post was at 10:02 PM ----------
Ok, wait I think I understand what you're saying now. If you can, pm the op of that thread you used to unbrick. Ask that person if you need some kind of different file in that .zip file to work on your carrier.
I remember having to use that guide to get back to stock. Glad to see you're making progress. I know it can be frustrating when devices get wacky. Good luck!
Sent from my LG-P999
hehehe sorry, I am not fully used to the right terms so I rather stay in the gray zone by using words like ''thing''
but I can now oficially say I was talking about ROMs
finally, I managed to bring back my phone to the stock mode everything seem to work!
now I can brick it again!
thx for the help!
I began to wonder if it was just a matter of changing APN settings?
Sent from my LG-P999
this, or... putting the simcard in the properly? !!
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"