Here's a true tethering unlock for AT&T 1.85 based ROMs(should work on 1.73 also). This mod makes a change in the framework so the OS doesn't think it's a AT&T ROM anymore, so there are no checks for tethering like non AT&T versions and this will also revert your network icons to 3G & H instead of always having 4G displayed(side effect of the mod). I included odex'd and deodex'd version with revert versions just in case anymore wants to remove this mod.
Thanks. Do you know how I can tell if my ROM is deodexed or not?
Calkulin said:
Here's a true tethering unlock for AT&T 1.85 based ROMs(should work on 1.73 also). This mod makes a change in the framework so the OS doesn't think it's a AT&T ROM anymore, so there are no checks for tethering like non AT&T versions and this will also revert your network icons to 3G & H instead of always having 4G displayed(side effect of the mod). I included odex'd and deodex'd version with revert versions just in case anymore wants to remove this mod.
Click to expand...
Click to collapse
Good to see your name caulk. Any roms coming soon? Haha.
Hell yea bro, thanks for this
Calkulin said:
Here's a true tethering unlock for AT&T 1.85 based ROMs(should work on 1.73 also). This mod makes a change in the framework so the OS doesn't think it's a AT&T ROM anymore, so there are no checks for tethering like non AT&T versions and this will also revert your network icons to 3G & H instead of always having 4G displayed(side effect of the mod). I included odex'd and deodex'd version with revert versions just in case anymore wants to remove this mod.
Click to expand...
Click to collapse
I'm assuming we flash this via CWM? Also, you mention 1.85 and 1.73, any reason why these wouldn't work on other versions?
Can you also do one for 1.88? Thanks!
NguyenHuu said:
Can you also do one for 1.88? Thanks!
Click to expand...
Click to collapse
1.88 isn't an ATT rom, tether and hotspot should work.
nugzo said:
1.88 isn't an ATT rom, tether and hotspot should work.
Click to expand...
Click to collapse
Nope, still get the provisioning error and to call AT&T.
Sent from my HTC One X using xda premium
Flashed the 1.85 Unlock hack to my stock ATT one X on 1.85 and I had to RUU to get it working again. Wrong file?
I don't have cwm or the other thing to flash the unlock. I know where to put the ext.odex but where do I put the other folder (meta-inf) contents?
Ok, so i unlocked my BL and then I installed CWM, then flashed the hotspot unlock, then reboot, now my phone wont start up and is stuck on the HTC screen. Unfortunatly I did not have any roms on my sdcard and now i'm stuck. I tried using the 1.85 ruu but i get an error and it wont work. I don't know how to use adb. Can anyone please help me out? it's the weekend for goodness sake! I can't be stuck without a phone!
Relock your bootloader with fastboot oem lock. Then you can flash the ruu.
gunnyman said:
Relock your bootloader with fastboot oem lock. Then you can flash the ruu.
Click to expand...
Click to collapse
Don't forget he has to reinstall stock recovery first. Wipe data and cache is a good think to try before resorting to all of that.
Sent from my HTC One X using XDA
Thanks guys, I got it.
I've never had to install stock recovery before running ruu. Make sure htc sync is disabled. 170 is usb error. V
gunnyman said:
I've never had to install stock recovery before running ruu. Make sure htc sync is disabled. 170 is usb error. V
Click to expand...
Click to collapse
That's interesting...and which custom recovery you had when used RUU?
gunnyman said:
I've never had to install stock recovery before running ruu. Make sure htc sync is disabled. 170 is usb error. V
Click to expand...
Click to collapse
vin255764 said:
That's interesting...and which custom recovery you had when used RUU?
Click to expand...
Click to collapse
Me neither and I've done it 5 or 6 times already. I had cwm but I really don't think it matters. The RUU puts the stock recovery back on. All you need to do to be able to run the RUU is re-lock your bootloader.
I managed to install the stock 1.85 ruu but now i don't have root
I tried the one click method that's in the dev section but i was not able to successfully get the su installed i tried 4 times. Maybe because I'm not using an at&t SIM? Oh well, i guess I'll have to stick without root until there's an easier one click. I really wanted to try cleanrom.
Sent from my HTC One X
veliksam said:
I managed to install the stock 1.85 ruu but now i don't have root
I tried the one click method that's in the dev section but i was not able to successfully get the su installed i tried 4 times. Maybe because I'm not using an at&t SIM? Oh well, i guess I'll have to stick without root until there's an easier one click. I really wanted to try cleanrom.
Sent from my HTC One X
Click to expand...
Click to collapse
Just unlock your bootloader again through adb, flash CWM or TWRP and then flash CleanROM. No need to root 1.85.
_MetalHead_ said:
Just unlock your bootloader again through adb, flash CWM or TWRP and then flash CleanROM. No need to root 1.85.
Click to expand...
Click to collapse
It's there an easy way of doing the bl unlock like the supercid, something like a one click? I'm still a new comer when it comes to adb and all that hex stuff. I saw the thread about unlocking thru htcdev but it seems too complicated and I'm scared i might brick something.
Should i try this: http://forum.xda-developers.com/showthread.php?t=1675312 ?
Sent from my HTC One X
Related
I've gotten totally accustomed to flashing on Samsung devices..
Currently have AT&T One X
- Rooted
- Bootloader Unlocked
- Running CleanRom 1.0
- Build Number 1.88.707.2
I'd like to get it back to just a rooted AT&T stock version so that I can make my own adjustments. I'm a bit confused as to the easiest way to do this.
05GT said:
I've gotten totally accustomed to flashing on Samsung devices..
Currently have AT&T One X
- Rooted
- Bootloader Unlocked
- Running CleanRom 1.0
- Build Number 1.88.707.2
I'd like to get it back to just a rooted AT&T stock version so that I can make my own adjustments. I'm a bit confused as to the easiest way to do this.
Click to expand...
Click to collapse
Someone would have to make a rooted stock from. Unless you want to go back to 1.73 which you would get the bugs it had. If you did that would require a firmware downgrade. There is a thread in dev section. Have you tried updating to cleanrom 2.5.5 the most recent version with tons of fixes and such.
Sent from my HTC One X using xda premium
if you haven't flashed something else or found this already, this link is to a stock, CWM ready version of the 1.85.502.3 RUU. read the OP first, because this version is NOT rooted.
You presumably already have SuperCID if you have bootloader unlocked. All you have to do is:
1) Relock bootloader
2) Run whatever RUU you want
3) Unlock bootloader again
4) Install CWM
5) Root via One click for 1.73 or 1.82, or install SuperSU via CWM for 1.85.
The pre-rooted deodexed 1.85 version posted in the response above is also a good approach (install via CWM). But its not fully stock, as in its deodexed. But if you want to install mods, this is a good thing anyway, since many of them require deodex. You also don't need to mess with relocking and unlocking the BL again. But its not clear what you want to do, if you want to return to the original shipped 1.73 firmware or not.
cortez.i said:
if you haven't flashed something else or found this already, this link is to a stock, CWM ready version of the 1.85.502.3 RUU. read the OP first, because this version is NOT rooted.
Click to expand...
Click to collapse
Thanks for the link.
redpoint73 said:
You presumably already have SuperCID if you have bootloader unlocked. All you have to do is:
1) Relock bootloader
2) Run whatever RUU you want
3) Unlock bootloader again
4) Install CWM
5) Root via One click for 1.73 or 1.82, or install SuperSU via CWM for 1.85.
The pre-rooted deodexed 1.85 version posted in the response above is also a good approach (install via CWM). But its not fully stock, as in its deodexed. But if you want to install mods, this is a good thing anyway, since many of them require deodex. You also don't need to mess with relocking and unlocking the BL again. But its not clear what you want to do, if you want to return to the original shipped 1.73 firmware or not.
Click to expand...
Click to collapse
Thanks,
Went this route and everything worked great. Now just need to flash the deodexed rom so I can make tweaks.
Sent from my HTC One X using xda premium
Hi Guys.
I wanted to confrim if I can install any RUU on my HTC One XL with out unlocking the Bootloader or rooting or supercid.
Because in most forums i have had a look at they dont mention if its needed.
In this case i wanted to install the RUU EVITA hTC Asia WWE 2.23.707.2 and wanted to know if its required to perform the above to install the RUU.
Regards
Ruus have 3 simple rules.
1. Bootloader must be locked.
2. Cid must match. Eg WWE is not the same cid as Telstra. You need to supercid or atleast change to Telstra cid.
3. You can not downgrade hboot. The ruu must be equal or newer than your current version.
Point 2 is where you will need root.
gondwn said:
Hi Guys.
I wanted to confrim if I can install any RUU on my HTC One XL with out unlocking the Bootloader or rooting or supercid.
Because in most forums i have had a look at they dont mention if its needed.
In this case i wanted to install the RUU EVITA hTC Asia WWE 2.23.707.2 and wanted to know if its required to perform the above to install the RUU.
Regards
Click to expand...
Click to collapse
The Telstra One XL is currently Bootloader unlockable through htcdev unlike the AT&T One X. This means that we don't have to mess around to get a ROM onto our device. Why you would go to all the trouble of rooting and changing your cid (Which sometimes I've read can wipe out your IMEI and Serial Number?) when you just just unlock your bootloader, flash a recovery and then install any ROM you want.
Thanks guys for your help
I am stuck in a cm10 boot loop. Never got çm sucessufulky flashed. Was on stock deodexed rom prior to attempting cm.
I can get to twrp 2.2.0 recovery and to recovery as well but don't have a backup to flash from twrp.
I was thinking of going back to ruu 1.8.5 but my bootloader is unlocked using HTC Dev.
Any suggestions?
[QUOTE=twistedddx;30840704]Ruus have 3 simple rules.
1. Bootloader must be locked.
2. Cid must match. Eg WWE is not the same cid as Telstra. You need to supercid or atleast change to Telstra cid.
3. You can not downgrade hboot. The ruu must be equal or newer than your current version.
Point 2 is where you will need root.[/QUOTE]
Grab another rom and flash it. Try nocturnals telstra rom and see what you think.
It will be a lot easier than heading back to stock via ruu
Sent from my HTC One XL using xda app-developers app
w0tha said:
Grab another rom and flash it. Try nocturnals telstra rom and see what you think.
It will be a lot easier than heading back to stock via ruu
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
how do you flash another rom though without being able to put it on your sd card first? is there a command you can put in command prompt so that the zip shows up in recovery?
from twrp recovery, you can connect the USB and mount SDCard
then connect to computer and copy over the rom
otherwise, you could use adb commands
adb devices (make sure device exists)
adb shell
mount sdcard
Then either
adb push ROM.zip \sdcard\
or copy
AT&T ONE X
Hi,
I have an AT&T one X and i see that i cant use tethered WiFi, I dont use the phone in the USA but here in NZL, is there some way to get around this ? I cant stand the ATT rubbish they put on the phone so im looking for a unbraded rom, but Id prefer a rom which is factory rather than a custom built.
Could someone please point me in the right direction
Thanks in advance
G
gymmy said:
Hi,
I have an AT&T one X and i see that i cant use tethered WiFi, I dont use the phone in the USA but here in NZL, is there some way to get around this ? I cant stand the ATT rubbish they put on the phone so im looking for a unbraded rom, but Id prefer a rom which is factory rather than a custom built.
Could someone please point me in the right direction
Thanks in advance
G
Click to expand...
Click to collapse
Any of the stock rooted ROMs in Development except AT&T ones have WiFi tethering enabled. You of course need to be bootloader unlocked and custom recovery.
redpoint73 said:
Any of the stock rooted ROMs in Development except AT&T ones have WiFi tethering enabled. You of course need to be bootloader unlocked and custom recovery.
Click to expand...
Click to collapse
I was trying to avoid loading a custom recovery, its not that i dont trust the kind folk on here, but lets face it , it wouldnt take much to have my phone upload its contents to a dev, just call me paranoid hahahaa, so do i have to use an ATT rom ? i really would like to unbrand it also
G
I decided to downgrade to 1.85 for a fresh start after downgrading hboot to 1.09.000. 1.85, 1.73 RUUs failed and im trying 2.20 as we speak :// if this fails what are mmy options?
thanks
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
area51avenger said:
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
yes
twistedddx said:
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
Click to expand...
Click to collapse
I did this and I keep getting error 140- per this I am stuck in bl and I cant get adb
anyone? im in need of desperate help..
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
superchilpil said:
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Kole_Ackerson said:
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Click to expand...
Click to collapse
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
superchilpil said:
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
ok, I got the unlock token but its hanging on sending (0kb)
Kole_Ackerson said:
ok, I got the unlock token but its hanging on sending (0kb)
Click to expand...
Click to collapse
Make sure you're in fastboot not hboot
If that doesn't work reset your computer to make sure not programs are interfering with it
Sent from my One X using Tapatalk 2
it is in fastboot usb so ill reset my comp.
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
superchilpil said:
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Kole_Ackerson said:
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Click to expand...
Click to collapse
Nah don't worry about it!
Just helping out where I can
Sent from my One X using Tapatalk 2
Can only boot to bootloader and all RUU failed
I am in a bit of trouble at the moment. I will try to describe what I have done to end up where I am now.
I have a Telstra HTC One XL. Recently upgraded an already unlocked, rooted HOXL to JB using the OTA update (big mistake I know now). This upgraded the hboot to 2.14 and software to 3.17.8xxx.
Spent a lot of time trying to re-root. TWRP didn't work (no touch response). So I eventually found the Interim CWM Recovery (no touch) by Modaco. This seemed to work well and I managed to root the phone.
Then i followed the instructions to flash to KingBeatZ 1.2.0 ROM. Booted fine but had no touch response too.
So I wiped KingBeatZ 1.2.0 and went for the nightly CM10. Again, booted fine but no touch response.
OK, so I figured I should just go back to my restored data. Tried that but apparently no restore data (didn't realise a wipe wiped the restore data as well, what is the point of that?)
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
I do not know what I should do now to restore any functionality to my HOXL. Any help would be greatly appreciated.
o0okiato0o said:
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
Click to expand...
Click to collapse
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
redpoint73 said:
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
Click to expand...
Click to collapse
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
superchilpil said:
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
o0okiato0o said:
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
Click to expand...
Click to collapse
Take a stock ROM and pull out the boot.img
And fastboot flash boot boot.img just to make sure it flashes
Then flash the ROM in recovery
Sent from my One X using Tapatalk 2
This is probably a long shot but does anyone have a STOCK T-mobile 2.3.6 NAND back I can flash? I tried to update my HTC Sensation 4G to ICS via RUU since I rooted and such. Keeps failing due to some error, doesn't say which. I had some ROM on it but it couldn't connect to Wi-Fi and my mum was furious about that, so I attempted RUU, no beans.
I unlocked bootloader, S-ON, 4EXT TOUCH recovery.
creepinm3 said:
This is probably a long shot but does anyone have a STOCK T-mobile 2.3.6 NAND back I can flash? I tried to update my HTC Sensation 4G to ICS via RUU since I rooted and such. Keeps failing due to some error, doesn't say which. I had some ROM on it but it couldn't connect to Wi-Fi and my mum was furious about that, so I attempted RUU, no beans.
I unlocked bootloader, S-ON, 4EXT TOUCH recovery.
Click to expand...
Click to collapse
i see that you still in gingerbread android
then you must use revolutionary.io method to S-OFF the device
it was unecessary to unlock the bootloader
rzr86 said:
i see that you still in gingerbread android
then you must use revolutionary.io method to S-OFF the device
it was unecessary to unlock the bootloader
Click to expand...
Click to collapse
I don't even want to bother with that anymore, I am just looking for a way to get back to stock T-mobile Gingerbread ROM.
EDIT: I constantly get error 155 no matter what version of the RUU I try.
creepinm3 said:
I don't even want to bother with that anymore, I am just looking for a way to get back to stock T-mobile Gingerbread ROM.
EDIT: I constantly get error 155 no matter what version of the RUU I try.
Click to expand...
Click to collapse
ddi you relock the bootloader first?
rzr86 said:
ddi you relock the bootloader first?
Click to expand...
Click to collapse
Yes, I did
Sent from my SAMSUNG-SGH-T989 using xda premium
Hi, I have a HTC ONE XL for AT&T with S-OFF and unlocked bootloader. I have the nocturnal ROM based on ICS. Also HBOOT 1.01.0000.
I want to install a rom based on JB (This particular CleanROM 6.5 - ★ | Jellybean 4.1.1! |).
My question is with this hboot, can i flash a jb rom from ICS? Because I'm not sure if flash from recovery the zip of this rom bricked me.
It won't brick you. I'm not sure if you'll experience issues using such an old firmware with a ROM based on the latest softwate
Sent from my One X using xda app-developers app
Thanks. Is there any way to update the software?
Rafanjani said:
Thanks. Is there any way to update the software?
Click to expand...
Click to collapse
Yes install the Ruu, then push twrp, then install CR. This will give you the latest firmware. CR by itself does not so it, and some gave experienced random reboots with older wifi firmware. Just be aware that a small subset of HOXL phones do not work well with Maps/nav under JB
between ynelsol
GroovyGeek said:
Yes install the Ruu, then push twrp, then install CR. This will give you the latest firmware. CR by itself does not so it, and some gave experienced random reboots with older wifi firmware. Just be aware that a small subset of HOXL phones do not work well with Maps/nav under JB
Click to expand...
Click to collapse
thanks for reply! I did brick my phone when i try to install an official ruu 2 months ago, but i did fix this ($$$$). The problem is that I can not install because I have CID 111111 and CR root, bootloader unlocked etc
With s-off you won't brick running an ruu. Though my phone will no longer ruu properly but that's another story. I may post a thread about it in case others experience it so they know how to recover.
Sent from my HTC One X using xda app-developers app
exad said:
Though my phone will no longer ruu properly but that's another story. I may post a thread about it in case others experience it so they know how to recover.
Click to expand...
Click to collapse
I'm curious about this. What happened?
Sent from my HTC One
ECEXCURSION said:
I'm curious about this. What happened?
Sent from my HTC One
Click to expand...
Click to collapse
Something went wrong while RUUing and my hboot partition cannot be written over without clearing the cache first. So the RUU will get to the end and then fail. Everything flashed except the hboot. It's kind of funny because it looks like a brick when it happens but it remains in RUU mode so I can just fastboot flash the hboot seperately after and everything works but RUUs will no longer complete successfully Always half bricks.
How did it happen? Well I think it's because I was RUUing in a VM as I was running linux exclusively at the time. But during RUU the phone looses connection and I have to manually reconnect to my phone and I didn't realize so it interrupted the RUU. I'm just lucky I didn't end up with a full brick! ^_^
exad said:
Something went wrong while RUUing and my hboot partition cannot be written over without clearing the cache first. So the RUU will get to the end and then fail. Everything flashed except the hboot. It's kind of funny because it looks like a brick when it happens but it remains in RUU mode so I can just fastboot flash the hboot seperately after and everything works but RUUs will no longer complete successfully Always half bricks.
How did it happen? Well I think it's because I was RUUing in a VM as I was running linux exclusively at the time. But during RUU the phone looses connection and I have to manually reconnect to my phone and I didn't realize so it interrupted the RUU. I'm just lucky I didn't end up with a full brick! ^_^
Click to expand...
Click to collapse
how i can flash hboot using fastboot? I wish to have jb
Rafanjani said:
how i can flash hboot using fastboot? I wish to have jb
Click to expand...
Click to collapse
flashing hboot with fastboot won't give you JB......
Is your phone S-ON or S-OFF?
SuperCID? Yes or no?
Bootloader locked or unlocked?
exad said:
flashing hboot with fastboot won't give you JB......
Is your phone S-ON or S-OFF?
SuperCID? Yes or no?
Bootloader locked or unlocked?
Click to expand...
Click to collapse
I know! but it's the first step to upgrade to jb
Rafanjani said:
I know! but it's the first step to upgrade to jb
Click to expand...
Click to collapse
No it isn't