Related
This is the latest hboot from HTC for the DINC that allows the bootloader to be OEM unlocked.
HBOOT 1.02.0000
1. Enable usb debugging
2. Run RUU(make sure to use the HTC drivers or RUU wont work)
3. Use htc dev process to oem unlock bootloader
4. Enjoy pwnage of ur DINC
P.S. I have attached the PB31IMG.zip for those who dont kno how to RUU
Question (anyone)?
If you are already S-off, rooted, and using the .92 bootloader, will flashing the zip cause a loss of S-off, or any other disasters?
Considering giving it a shot, but don't want to spend the evening rerooting or getting into something I can't get back out of.
Input welcome...
sorry...I was on the phone
omniatic said:
Question (anyone)?
If you are already S-off, rooted, and using the .92 bootloader, will flashing the zip cause a loss of S-off, or any other disasters?
Considering giving it a shot, but don't want to spend the evening rerooting or getting into something I can't get back out of.
Input welcome...
sorry...I was on the phone
Click to expand...
Click to collapse
No. I did that and was fine. I used the PB31IMG.zip
Sent from my Galaxy Nexus using Tapatalk 2
OK flashed it fine. Now, I see that the unlocking process wipes the phone clean. Will I still be able to boot into CWM recovery and restore a nand backup? Or will I have to reflash CWM 5.0.2.0?
Edit: I'll still be S-off, right?
omniatic said:
OK flashed it fine. Now, I see that the unlocking process wipes the phone clean. Will I still be able to boot into CWM recovery and restore a nand backup? Or will I have to reflash CWM 5.0.2.0?
Edit: I'll still be S-off, right?
Click to expand...
Click to collapse
Actually I think the wipe process with unlocking fails if you're on CWM. I didn't lose CWM or data when I did it.
Yes. I still am S-OFF when I did it rooted.
But you may not need this unlocked bootloader as you can already flash radios and recoveries from the bootloader (HBOOT) and kernels, ROMs and recoveries from CWM with s-off alone.
I got it just so I could use fastboot to flash kernels which if you flash with fastboot on this device you may need to still manually push the corresponding wifi module if the version string changes - not necessarily each time you switch kernels either. For my gingersense kernels that would only be if you switch between gingertiny 2.6.35.10, gingertiny-v2 2.6.35.13 and gingertiny-2.6.35.14. For incredikernel that may be quite different.
Sorry, I'm rambiling and should be asleep but just so hyper.
Yeah, I know it wasn't needed. But I felt it had to be done. Anyhow, something got wiped, cause it hung on the boot screen forever. Finally pulled the battery, booted into recovery, and restored my fresh backup. 1.02 bootloader, unlocked, and up and running again.
Thanks for all the help. I see you edited your post about the same time I was banging away in command prompt. All my SDK tools were scattered around and needed updating, which stretched it out. Once again, that feeling you get when something works despite your best efforts.
Thanks+
After a gut-wrencher like that, some sleep sounds good.
Sorry if this is the wrong thread in which to post but I'm getting pretty confused. I have an HTC incredible I just received with S-Off
It says:
HBOOT-0.92.9999
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
I am in fastboot usb, but I cannot flash the cwm 5.0.2.0 img,
I try fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img and receive the error:
C:\Android\android-sdk\platf
sending 'recovery' (3064 KB)
OKAY [ 0.494s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.498s
Does this mean that I don't have root access, even though I am S-off?
Not sure about flashing a newer recovery through fastboot.....but you can also download rom manager from the market and update your cwm that way....
The Bootloader
can you update the hboot while running a custom rom without bricking.
Asylum1621 said:
Sorry if this is the wrong thread in which to post but I'm getting pretty confused. I have an HTC incredible I just received with S-Off
It says:
HBOOT-0.92.9999
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
I am in fastboot usb, but I cannot flash the cwm 5.0.2.0 img,
I try fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img and receive the error:
C:\Android\android-sdk\platf
sending 'recovery' (3064 KB)
OKAY [ 0.494s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.498s
Does this mean that I don't have root access, even though I am S-off?
Click to expand...
Click to collapse
How are you trying to flash it? You just take this file http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip, and place it on your sdcard in no folders. Then boot to hboot and wait a few secs. It should automaticly find the file and prompt you to press vol up to update.
Fastboot flashing images wont work unless your bootloader in unlocked.
Edit: Didnt realize this post was so old.
---------- Post added at 10:31 PM ---------- Previous post was at 10:27 PM ----------
zachf714 said:
can you update the hboot while running a custom rom without bricking.
Click to expand...
Click to collapse
Yes you can as long as your s-off. This thread is actually old and a newer version hboot 1.07
DOWNLOAD: http://dinc.does-it.net/Hboots/Hboot_1.07/PB31IMG.zip
MD5: http://dinc.does-it.net/Hboots/Hboot_1.07/PB31IMG.zip.md5 has been released. However if your s-off there is no need to update, as you can already flash thru hboot. The only advantage is being able to fastboot flash imgs.
If you s-on the only way to update is to do an ruu, which will wipe the phone and require you to reroot and flash a backup.
cmlusco said:
Yes you can as long as your s-off.
Click to expand...
Click to collapse
Oh really? s-off users can simply flash the new HBOOT in HBOOT then do the unlocking process on HTC-Dev?
That unlocks and keeps s-off?
ardax said:
Oh really? s-off users can simply flash the new HBOOT in HBOOT then do the unlocking process on HTC-Dev?
That unlocks and keeps s-off?
Click to expand...
Click to collapse
Correct.
Are you guys flashing HBOOT without checking the md5?
Sounds gutsy...
Sent from my Droid Incredible using xda app-developers app
ccbiker said:
Are you guys flashing HBOOT without checking the md5?
Sounds gutsy...
Sent from my Droid Incredible using xda app-developers app
Click to expand...
Click to collapse
You can get the md5 by adding .md5 to the download url. ( http://dinc.does-it.net/Hboots/Hboot_1.07/PB31IMG.zip.md5 ) All files on dinc.does-it.net have an md5.
ccbiker said:
Are you guys flashing HBOOT without checking the md5?
Click to expand...
Click to collapse
Are you nutters? I'll both verify md5 and check zip file integrity before attempting to flash something like an hboot or radio!
cmlusco said:
You can get the md5 by adding .md5 to the download url. ( http://dinc.does-it.net/Hboots/Hboot_1.07/PB31IMG.zip.md5 ) All files on dinc.does-it.net have an md5.
Click to expand...
Click to collapse
Oh nice. I just saw the PB31IMG zip in the attachment in the OP and was like, "what?! these people are crazy!" Good to know!
ardax said:
Are you nutters? I'll both verify md5 and check zip file integrity before attempting to flash something like an hboot or radio!
Click to expand...
Click to collapse
Yeah.. I feel the same way! I was just confused since I didn't see the md5 posted. I wondered what I was missing.
So I kno its so late but I'd rather be sure than sorry lol...I can flash hboot 1.07(or what ever it is) and have both s-off and be unlocked? I thought you could only have one at a time? Someone help plz
Sent from my rooted GameBoy Advance! ^¬^
Yeah. Get S-OFF first if you haven't already. Then flash the latest HBOOT. You'll still have S-OFF after that. Then just unlock the bootloader on htcdev.com according to their directions.
Viola! S-OFF and unlocked bootloader.
Thanks will do!
Sent from my rooted GameBoy Advance! ^¬^
Why do you guys do this? Are you already rooted and running custom roms
Sent from my ADR6300 using xda app-developers app
Hello All,
Here's my dilemma. I successfully rooted my HTC One (AT&T), and was recently attempting to unroot it. I followed this one here http://forum.xda-developers.com/showthread.php?t=2182823. Since I have the AT&T version, I downloaded the first one the list found there, however it wouldn't verify. Next I downloaded the AT&T AIO here http://forum.xda-developers.com/showthread.php?t=2242635. I was able to use that to figure out according to the info it displayed that I actually needed the Google Edition one from the previous link. I thought that was weird since I dont have the google edition one. But when I fast booted that one, everything appeared to go through with a hitch.....Until it restarted.
After it restarted, I only have a black screen. No start up. I restarted the phone and went into the bootloader and to my surprise, the bootloader was black instead of the normal white.
I've tried several RUUs found here http://www.androidruu.com/index.php?developer=M7
I've tried both the exe and flashing the zip.
I have no clue what to try next. Please XDA, your my only hope.
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
iElvis said:
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
Click to expand...
Click to collapse
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Tylegn said:
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Click to expand...
Click to collapse
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
iElvis said:
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
Click to expand...
Click to collapse
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Tylegn said:
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Click to expand...
Click to collapse
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
iElvis said:
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
Click to expand...
Click to collapse
I received the phone directly from HTC through a sell to earn contest.
Not sure if it matters much but I unlocked the bootloader through HTC Dev.
To unroot,
1) Put phone in bootloader with fastboot
2) Relocked bootloader
3) fastboot oem rebootRUU
4) fastboot flash zip 2.24.401.1.zip (failed)
Used one of the AIOs that stated I had modelid: PN0712000 and cidnum: CWS__001. That when I grabbed the GE version.
5) fastboot flash zip 3.06.1700.10.zip
6) Phone finished, rebooted to a black screen
7) Rebooted into bootloader (Which is now black instead of white)
8) Sad ever since....
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
ageldea consider
iElvis said:
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
Click to expand...
Click to collapse
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Tylegn said:
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Click to expand...
Click to collapse
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
Found the stock recovery. Attempted to flash it and got this:
sending 'recovery' <16303 KB>...
OKAY [ 1.786s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote: 12 signature verify fail>
finished. total time: 3.178s
Is there a different way I should be doing it.
HTC One has the Gray HTC logo chilling on the screen...
Also tried in normal fastboot mode...
Tylegn said:
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
Click to expand...
Click to collapse
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
iElvis said:
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
Click to expand...
Click to collapse
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
ADD: I just successfully flashed the stock recovery.... Too scared to muck something up so I'll waif for your superior guidance!
Thanks again
Tylegn said:
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
Click to expand...
Click to collapse
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
iElvis said:
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
Click to expand...
Click to collapse
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Tylegn said:
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Click to expand...
Click to collapse
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
iElvis said:
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
Click to expand...
Click to collapse
Thank you so much! I believe I can take it from here.....Until I brick my phone when the signed 4.3 comes out. LOL
Until next time. Thanks iElivis you are a BADA$$!:good::good::good:
So I'm trying to flash a new RUU for GPE HTC One Jelly Bean 4.3. The RUU is suppose to work for unlocked devices; the person who posted the download links had two, with one for unlocked devices and the other for locked devices. I think I messed up somewhere because I had a custom kernel installed via .zip, then booted back to the stock GPE kernel with "fastboot flash boot boot.img"; the system booted up fine but the 3 dot menu was missing so I went back to the customer kernel. The system wouldn't get past the Google screen and now I'm trying to flash the RUU but it won't work. If I do it on my computer via commands, I get "<bootloader> zip info parsing," then "FAILED <remote: 99 unknown fail>". So now I'm in TWRP recovery with the RUU on my SD card; tried flashing it on my phone and it says "Updating partition details...", "E: unable to mount ' /data'", "E: unable to mount internal storage", E: unable to mount ' /data," then lastly "Error flashing zip." I wiped the cache, data, and system; it won't wipe the Dalvik cache and gives me the same error when I do it. Can someone help me?
Edit: When I also try to wipe via "fastboot -w" it comes up with an error saying "FAILED <remote: not allowed>.
You need S-off to ruu to another firmware that's not made for your particular model/carrier.
Once you s-off enter fastboot oem rebootRUU
fastboot flash zip firmware.zip
(Firmware.zip being the actually name of the ruu zip)
It will begin to flash, then fail and say to flush image immediately. Simply press the "up" arrow on keyboard to repeat the exact same command. It will work the second time.
For some reason fastbooting a ruu in that mode always fails the first time, so you have to do it twice without exiting.
Good luck and enjoy
Sent from my HTC One using Tapatalk 2
InflatedTitan said:
You need S-off to ruu to another firmware that's not made for your particular model/carrier.
Once you s-off enter fastboot oem rebootRUU
fastboot flash zip firmware.zip
(Firmware.zip being the actually name of the ruu zip)
It will begin to flash, then fail and say to flush image immediately. Simply press the "up" arrow on keyboard to repeat the exact same command. It will work the second time.
For some reason fastbooting a ruu in that mode always fails the first time, so you have to do it twice without exiting.
Good luck and enjoy
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I think the GPE RUU supports MID: PN0713000 and CID: T-MOB010. http://forum.xda-developers.com/showthread.php?t=2358781
Edit: Oh, never mind; it says S-Off needed...
Any advice on what to do now since my HBoot is 1.54? The HBoot for the latest T-Mobile Sense 5 RUU is 1.44... I'm stuck now...
May be the alcohol but I'm having trouble keeping up lol. You're having questions with the hboot trying to s-off? If you can't s-off, nor ruu BC the firmware doesn't match with the most recent ruu then you may be stuck or hopefully someone with more advanced knowledge can help you a little better
Sent from my HTC One using Tapatalk 2
yorkies88888 said:
I think the GPE RUU supports MID: PN0713000 and CID: T-MOB010. http://forum.xda-developers.com/showthread.php?t=2358781
Edit: Oh, never mind; it says S-Off needed...
Any advice on what to do now since my HBoot is 1.54? The HBoot for the latest T-Mobile Sense 5 RUU is 1.44... I'm stuck now...
Click to expand...
Click to collapse
For some reason Google firmware will flash on certain s-on phones when it shouldn't. First we need to know if this happened.
When booted into the boot loader, is the screen black or white?
Now if there's an RUU available for your cid and mid (an official ruu.exe not an unsigned zip) that is greater than the firmware version currently on the phone, flashing that will fix everything.
If not, head over to original android development and grab a GPE ROM ( you could also use sense or AOSP, but I'm assuming you want GPe) and attempt to flash the ROM in recovery just like you normally would.
AT&T HTC M7ul
Baad Newz's InsertCoin 3.4-2
Flar2's Bulletproof 6.2
CoryTallman said:
For some reason Google firmware will flash on certain s-on phones when it shouldn't. First we need to know if this happened.
When booted into the boot loader, is the screen black or white?
Now if there's an RUU available for your cid and mid (an official ruu.exe not an unsigned zip) that is greater than the firmware version currently on the phone, flashing that will fix everything.
If not, head over to original android development and grab a GPE ROM ( you could also use sense or AOSP, but I'm assuming you want GPe) and attempt to flash the ROM in recovery just like you normally would.
AT&T HTC M7ul
Baad Newz's InsertCoin 3.4-2
Flar2's Bulletproof 6.2
Click to expand...
Click to collapse
So basically I accidentally put security back on BEFORE flashing back to stock so now I'm stuck here. The bootloader screen is black and since I upgraded to HBoot 1.54 via OTA update for stock Jelly Bean when I was S-Off, there is no compatible HBoot for me since the one for T-Mobile is 1.44 currently. My biggest worries right now is that I screwed something up with the partitions or if there's a bigger issue here because it's saying it can't mount the data and SD card, and I can't even wipe the phone via commands. If it's just the CID, MID, and HBoot not matching, then I'm not worried since I can still flash a custom ROM right?
yorkies88888 said:
So basically I accidentally put security back on BEFORE flashing back to stock so now I'm stuck here. The bootloader screen is black and since I upgraded to HBoot 1.54 via OTA update for stock Jelly Bean when I was S-Off, there is no compatible HBoot for me since the one for T-Mobile is 1.44 currently. My biggest worries right now is that I screwed something up with the partitions or if there's a bigger issue here because it's saying it can't mount the data and SD card, and I can't even wipe the phone via commands. If it's just the CID, MID, and HBoot not matching, then I'm not worried since I can still flash a custom ROM right?
Click to expand...
Click to collapse
This is why going back to s-on is almost always a bad idea. You can't flash any unsigned RUUs or firmware packages now, so you can't return your phone to stock.
It sounds like you may have corrupted your sdcard during all this. Try reformatting it from your PC. This will wipe all your data, but if it's corrupted, it's gone anyway. Then you can push a new rom and kernel and flash.
here is the latest signed RUU for TMOB.
http://forum.xda-developers.com/showthread.php?t=2427325
wwjdd44 said:
here is the latest signed RUU for TMOB.
http://forum.xda-developers.com/showthread.php?t=2427325
Click to expand...
Click to collapse
It's of no use to him; he can't run it because he's on 1.54 and s-on.
iElvis said:
This is why going back to s-on is almost always a bad idea. You can't flash any unsigned RUUs or firmware packages now, so you can't return your phone to stock.
It sounds like you may have corrupted your sdcard during all this. Try reformatting it from your PC. This will wipe all your data, but if it's corrupted, it's gone anyway. Then you can push a new rom and kernel and flash.
Click to expand...
Click to collapse
So even if T-Mobile releases an RUU with HBoot 1.54, I can't go back to stock? And how do I reformat it on my PC? CMD? And can you recommend me a ROM that's closest to stock Sense 5? And do I flash the ROM first or the kernel? Sorry about all the questions; I'm just freaking out right now.
yorkies88888 said:
So even if T-Mobile releases an RUU with HBoot 1.54, I can't go back to stock? And how do I reformat it on my PC? CMD? And can you recommend me a ROM that's closest to stock Sense 5? And do I flash the ROM first or the kernel? Sorry about all the questions; I'm just freaking out right now.
Click to expand...
Click to collapse
You still have an unlocked bootloader right?
Then I would just flash a custom recovery and "format sdcard" from there.
Then "adb push Rom.zip /sdcard/" (or sideload) and flash the Rom.
I personally use ARHD 13.x which is very close to stock Sense 5.
ROMs already include a kernel, so no need to flash separately.
Sent from my HTC One using xda app-developers app
nkk71 said:
You still have an unlocked bootloader right?
Then I would just flash a custom recovery and "format sdcard" from there.
Then "adb push Rom.zip /sdcard/" (or sideload) and flash the Rom.
I personally use ARHD 13.x which is very close to stock Sense 5.
ROMs already include a kernel, so no need to flash separately.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I have an unlocked bootloader but TWRP doesn't seem to have a "format SD card" option.
Edit: And do you know if it's still possible to use the T-Mobile RUU when they come out with Jelly Bean 4.3 update with HBoot 1.54? Or am I just stuck with custom ROMS now?
yorkies88888 said:
Yes, I have an unlocked bootloader but TWRP doesn't seem to have a "format SD card" option.
Click to expand...
Click to collapse
I haven't used TWRP, but I'm sure it's there somewhere. Usually under advanced.
Might be called something else? What format options does TWRP have? Maybe /data/media
Sent from my HTC One using xda app-developers app
nkk71 said:
I haven't used TWRP, but I'm sure it's there somewhere. Usually under advanced.
Might be called something else? What format options does TWRP have? Maybe /data/media
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh, I found it! Thanks! Woot! Do you recommend ARHD 13.x or 21.x?
yorkies88888 said:
Oh, I found it! Thanks! Woot! Do you recommend ARHD 13.x or 21.x?
Click to expand...
Click to collapse
Personal preference. Why don't you try both. 13.x is based on official 4.2.2 and 21.x is based on leaked 4.3 (but still very good)
Just note on 21.0 you have to enter APN settings manually to get mobile data & mms, and there's a bug which won't let you access SIM card contacts.
Sent from my HTC One using xda app-developers app
nkk71 said:
Personal preference. Why don't you try both. 13.x is based on official 4.2.2 and 21.x is based on leaked 4.3 (but still very good)
Just note on 21.0 you have to enter APN settings manually to get mobile data & mms, and there's a bug which won't let you access SIM card contacts.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
yorkies88888 said:
Edit: And do you know if it's still possible to use the T-Mobile RUU when they come out with Jelly Bean 4.3 update with HBoot 1.54? Or am I just stuck with custom ROMS now?
Click to expand...
Click to collapse
You can't use unsigned RUUs. If T-Mo releases a RUU with 1.54 or later hboot, then yes, you should be able to use it (unless you changed your MID or CID).
yorkies88888 said:
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
Click to expand...
Click to collapse
Yes it is, but you're stuck with the Google bootloader for now, until there is an s-off exploit for 1.54 or T-Mo releases that RUU.
yorkies88888 said:
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
Click to expand...
Click to collapse
It is compatible with 1.54, but I've never tried GPe, so I can't answer that. Don't know if it is firmware, ROM related, or if GPe hboot is different.
Can someone pitch in?
Sent from my HTC One using xda app-developers app
iElvis said:
You can't use unsigned RUUs. If T-Mo releases a RUU with 1.54 or later hboot, then yes, you should be able to use it (unless you changed your MID or CID).
Yes it is, but you're stuck with the Google bootloader for now, until there is an s-off exploit for 1.54 or T-Mo releases that RUU.
Click to expand...
Click to collapse
nkk71 said:
It is compatible with 1.54, but I've never tried GPe, so I can't answer that. Don't know if it is firmware, ROM related, or if GPe hboot is different.
Can someone pitch in?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well it's a good thing I changed my CID back to T-MOB010 before I put security back on then... I had SuperCID so not like it would've mattered... But thanks for the good news! And the GPE ARHD is compatible because it's Jelly Bean 4.3, but would flashing the ARHD 13.x ROM change the bootloader and start-up screen to HTC instead of Google?
yorkies88888 said:
Well it's a good thing I changed my CID back to T-MOB010 before I put security back on then... I had SuperCID so not like it would've mattered... But thanks for the good news! And the GPE ARHD is compatible because it's Jelly Bean 4.3, but would flashing the ARHD 13.x ROM change the bootloader and start-up screen to HTC instead of Google?
Click to expand...
Click to collapse
No. No rom will change your bootloader or splash screen. You need s-off to do that.
[Q&A] [RUU] Google Edition Conversion. 4.4.2 RUU Zip pre-rooted/non-rooted + Firmwar
Q&A for [RUU] Google Edition Conversion. 4.4.2 RUU Zip pre-rooted/non-rooted + Firmware
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RUU] Google Edition Conversion. 4.4.2 RUU Zip pre-rooted/non-rooted + Firmware. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
s_off question
liam_davenport said:
I had no problem with receiving update with the stock recovery installed
---------- Post added at 10:49 AM ---------- Previous post was at 10:47 AM ----------
Don't go from 4.x.xxx.xx to 5.xx.xxx.xx I've had the firmware bug that bricks you're device, it's a pain have to set up linux and run some commands
Click to expand...
Click to collapse
will the process retain s off? Thanks in advance
crazyandroid said:
will the process retain s off? Thanks in advance
Click to expand...
Click to collapse
the only way your phone can turn back to s-on is if you enter the right command manually "fastboot writesecureflag 3"
S-OFF will never turn back to S-ON by itself
alray said:
the only way your phone can turn back to s-on is if you enter the right command manually "fastboot writesecureflag 3"
S-OFF will never turn back to S-ON by itself
Click to expand...
Click to collapse
Thank you for the quick reply.
running into a problem
First time back with an HTC since the nexus one. so bear with my on the of the HTC exclusive setting, options and what not.
I keep getting an error code "FAILED (remote: 99 unknown fail)" when i try and flash the ROM, I get the error code in the same spot i would get an error the first time I ran the code. this is a different code than what he said I would get. any direction on what i need to change is greatly appreciated!
Here is the code i get --------------------------------
Tanners-MacBook-Pro:Mac Tanner$ ./fastboot flash zip RUU-HTC_One_GE-4.4.2-3.62.1700.1_Rooted.zip
sending 'zip' (514596 KB)...
OKAY [ 20.864s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 21.109s
Tanners-MacBook-Pro:Mac Tanner$
--------------------------------------------------------------
sOther Information:
Build Number 4.18.502.7 CL302626
Baseband Version "Unknown"
HBOOT 1.44
Radio 4A.17.3250.20
That might be a corrupted download. Did you try redownloading it?
I may have actually found the problem. This phone is all sorts of messed up, when i got it, it had a custom ROM, (Which was stuck on the HTC Logo), a CWM recovery, but still S-ON.
I have ran firewater and Revone methods to turn S-Off. The first time i ran it is said successful, but I never bothered to confirm.
I got it working and i was able to grant root access to applications but their were reboots ever 1-2 minutes. so i flashed a new ROM.
now, i have a working ROM (still have the random reboots), SuperSU tells me i need to update my binaries, and i still have S-ON.
I am sure they are all related, and my main goal is to get S-OFF, but i don't know how. i should quit messing around with HTC and just stick with what i know, the Nexus phones.
teport said:
I may have actually found the problem. This phone is all sorts of messed up, when i got it, it had a custom ROM, (Which was stuck on the HTC Logo), a CWM recovery, but still S-ON.
I have ran firewater and Revone methods to turn S-Off. The first time i ran it is said successful, but I never bothered to confirm.
I got it working and i was able to grant root access to applications but their were reboots ever 1-2 minutes. so i flashed a new ROM.
now, i have a working ROM (still have the random reboots), SuperSU tells me i need to update my binaries, and i still have S-ON.
I am sure they are all related, and my main goal is to get S-OFF, but i don't know how. i should quit messing around with HTC and just stick with what i know, the Nexus phones.
Click to expand...
Click to collapse
you indeed need s-off to flash this ruu and you'll (maybe) have to change your cid/mid to match the android-info.txt file packed in that ruu.
Achieving s-off on hboot 1.44 is simple:
flash ARHD 31.6 (this rom is pre-rooted and have the correct unsecured kernel for the s-off exploit to work)
Then follow instructions from Revone thread.
when s-off is acheived, confirm that your cid and mid match the android-info.txt file of the ruu (or change CID/MID so they match)
Flash the ruu in RUU mode:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_file.zip
fastboot flash zip name_of_file.zip
fastboot reboot
Never s-on and relock bootloader when using GPE
Can I just flash the newest firmware? Or there is a different firmware for gpe?
htc one m7 convert GPE questions.
htc one m7
model pn07100
android 4.3
htc sense 5.0
hboot 1.55
unlocked
I want to convert my m7 to a GPE. before i do anything to my phone ,I have a few questions to ask...
i want to install the RUU-HTC_One_GE-4.4-3.62.1700.1.zip rom (non rooted) http://forum.xda-developers.com/showthread.php?t=2358781
- does that mean i dont need to root my phone if im flashing the non rooted rom?
- my device is unlocked but in the bootloader is says that its locked in the menu. does that mean i still have to unlock the bootloader? is there a difference between having an unlocked phone and having an unlocked bootloader?
- do i need to install sync manager and install drivers for my phone?
- will i be able to receive updates from google OTA? do i need to flash stock recovery in order to receive OTA updates from google?
- how would i back up my stock rom (android 4.1.2 w/ htc sense 5.0) if i decide to go back.
- after the flash will i have to re-install all my apps?
thanks.
S-off mandatory
Hello, is absolutely essential s-off? If the device is only unlocked bootloader via HTCdev? The procedure will fail completely?
duzera said:
Hello, is absolutely essential s-off? If the device is only unlocked bootloader via HTCdev? The procedure will fail completely?
Click to expand...
Click to collapse
are you asking seriously or....?
Prerequisites
S-Off, <--------
ADB knowledge
Fastboot knowledge
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=43459658&postcount=1
i installed the google play edition for htc one m7 4.4.2 rom. how do i add/remove panels? i dont see any personalize settings in the menu? i've tried a search and no results.
graphic glitches
I have successfully converted my phone to GPE4.4.2 using the exact methods. There is no problem with that. Problem started once I did an OTA to update it with 4.4.3 where there are graphic glitches on the status bar and the bottom part of the screen. Also the power off panel won't appear after pressing (holding) the power button. Anyone suffered this? any solutions?
Edited : Problem solved by changing phone's CID. I can't change the RUU android-info's CID because the glitch would be there as the OTA's CID is GOOGL001.
Sprint?
Hey guys, does this RUU work with Sprint yet?
when upgrade to lollipop
have this problem: mount failed to mount /dev/block/mmcblk0p037 at /data device or resource busy
how to solve it ?
in 4.4.4, stuck recovery, unrooted
It doesn't affect anything. Just let it keep going. The update takes a while because it is using the older patch method.
recovery
where can I find stock recovery for gpe rom 4.4.4/4.9.1700.1 thanks in advance
I get this too but I get FAILED (remote: 42 custom id check fail) when I reboot it just reboots back into cyanogenmod11
Cillian.K said:
I get this too but I get FAILED (remote: 42 custom id check fail) when I reboot it just reboots back into cyanogenmod11
Click to expand...
Click to collapse
wrong cid make sure your cid is compatible with the ruu
Hi all,
I've tried to install WWE stock rom on this device, but now is bricked. I can get into fastboot and bootloader, but I can't install anything now. I've tried from fastboot to install the one's dedicated to my device from here:
http://forum.xda-developers.com/showthread.php?t=2617159
device info (before trying to re-install) were:
tampered/unlocked
m7 cdug pvt ship s-on rh
hboot: 2.23.000
radio: u2.05.3501.18
open dsp-v28.120.274.0328
qsc-1237.18.19.0528
os-2.25.1402.1
e-mmc-boot 2048mb
cid/mid: HTCCN703
now CID is gone, but it's still unlocked and S-ON, and
hboot is 2.27.0000
radio u3.08.35.07.17
open dsp-v31.120.274.0617
qsc-1237.25.32.0717
os-2.25.1402.1
eMMC-boot 2048mb
PN0771000
How can I restore it in a way, then to install a WWE version?
ady_uaic said:
Hi all,
I've tried to install WWE stock rom on this device, but now is bricked. I can get into fastboot and bootloader, but I can't install anything now. I've tried from fastboot to install the one's dedicated to my device from here:
http://forum.xda-developers.com/showthread.php?t=2617159
device info (before trying to re-install) were:
tampered/unlocked
m7 cdug pvt ship s-on rh
hboot: 2.23.000
radio: u2.05.3501.18
open dsp-v28.120.274.0328
qsc-1237.18.19.0528
os-2.25.1402.1
e-mmc-boot 2048mb
cid/mid: HTCCN703
now CID is gone, but it's still unlocked and S-ON, and
hboot is 2.27.0000
radio u3.08.35.07.17
open dsp-v31.120.274.0617
qsc-1237.25.32.0717
os-2.25.1402.1
eMMC-boot 2048mb
PN0771000
How can I restore it in a way, then to install a WWE version?
Click to expand...
Click to collapse
post here for windows HTC phone mate, you'll get a quicker response, beside, alot of us here are anti-windows phones lol even if you do just live down the road from me: http://forum.xda-developers.com/htc-8x
Seanie280672 said:
post here for windows HTC phone mate, you'll get a quicker response, beside, alot of us here are anti-windows phones lol even if you do just live down the road from me: http://forum.xda-developers.com/htc-8x
Click to expand...
Click to collapse
I'm not sure I follow you. This is 802W, not windows phone.
The error: remote not allowed.
ady_uaic said:
I'm not sure I follow you. This is 802W, not windows phone.
Click to expand...
Click to collapse
Sorry, your cid related to a windows phone when I googled it, ive never seen those details before, I think you've already found everything to do with the 802w, but i'll have a look around too.
Seanie280672 said:
Sorry, your cid related to a windows phone when I googled it, ive never seen those details before, I think you've already found everything to do with the 802w, but i'll have a look around too.
Click to expand...
Click to collapse
thanks a lot mate!
I think the only thing I need is to flash a stock RUU (doesn't matter which version, as long as it works, then to do again all the processes: unlock bootloader, s-off, custom recovery, root, stock WWE RUU).
ady_uaic said:
thanks a lot mate!
I think the only thing I need is to flash a stock RUU (doesn't matter which version, as long as it works, then to do again all the processes: unlock bootloader, s-off, custom recovery, root, stock WWE RUU).
Click to expand...
Click to collapse
trouble is, your current OS is 2.25.1402.1 and thats an OTA not an RUU, you need a full RUU, this one may work:
PN07IMG_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.30.1402.1_ Radio_1237.25.32.0717_release_332510_signed_2_4.zip http://d-h.st/NAf which is the next full RUU up from yours.
Seanie280672 said:
trouble is, your current OS is 2.25.1402.1 and thats an OTA not an RUU, you need a full RUU, this one may work:
PN07IMG_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.30.1402.1_ Radio_1237.25.32.0717_release_332510_signed_2_4.zip http://d-h.st/NAf which is the next full RUU up from yours.
Click to expand...
Click to collapse
I already tried that mate, thanks!
it returns after signature checking...:
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
ady_uaic said:
I already tried that mate, thanks!
it returns after signature checking...:
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
Click to expand...
Click to collapse
Umm, im a bit confused, its a zip file not an official RUU, im just downloading it to take a closer look, how are you trying to flash it ?
EDIT: ok its an RUU zip, it need to be flashed in fastbootRUU mode, using fastboot commands, bootloader needs to be locked as you are s-on, Its should work as this OTA states that RUU was your next update if you got it via OTA, OTA_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_TO THIS ROM VERSION 2.30.1402.1 --------------------- FROM THIS ROM VERSION-2.25.1402.1 SAME AS YOURS_release_332539.zip - 50.49 MB
Seanie280672 said:
Umm, im a bit confused, its a zip file not an official RUU, im just downloading it to take a closer look, how are you trying to flash it ?
EDIT: ok its an RUU zip, it need to be flashed in fastbootRUU mode, using fastboot commands, bootloader needs to be locked as you are s-on, Its should work as this OTA states that RUU was your next update if you got it via OTA, OTA_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_TO THIS ROM VERSION 2.30.1402.1 --------------------- FROM THIS ROM VERSION-2.25.1402.1 SAME AS YOURS_release_332539.zip - 50.49 MB
Click to expand...
Click to collapse
from fastboot, using the command line:
fastboot flash zip ....zip
I've locked back the bootloader, and still doesn't work:
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
and no, it was an UNICOM version, and my friend tried to update to WWE.
ady_uaic said:
from fastboot, using the command line:
fastboot flash zip ....zip
I've locked back the bootloader, and still doesn't work:
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILnot allowed
FAILED (remote: not allowed)
and no, it was an UNICOM version, and my friend tried to update to WWE.
Click to expand...
Click to collapse
You cant change to WWE without s-off, tell your friend to leave it alone lol, it requires you to change cid and mid etc first, then flash the corrisponding firmware and then the RUU.
Rename your RUU to rom.zip for ease, then issue these commands :
make sure its this RUU, not the WWE one PN07IMG_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.30.1402.1_ Radio_1237.25.32.0717_release_332510_signed_2_4.zi p
fastboot oem rebootRUU (case sensetive, type it exactly like that)
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder
fastboot flash zip Rom.zip
This takes a couple minutes and you will most likely get a error
(pre-hboot update: please flush immediately) HTC typo, should be please flash immediately
Make sure device is still in ruu mode(black HTC screen)
now simply reflash the rom.zip, fastboot flash zip Rom.zip
Let it run and it should finish this time, make sure it says successfull at the end, if it does then fastboot reboot, you'll be full stock, if failed, report back here before doing anything else, dont reboot out of RUU mode.
The first flash is just a preupdate, the 2nd flash flashes the rom and firmware files.
Yes mate, I know that. Now I'm trying to put back any ROM then I will do the right procedure to install WWE.
But, now doesn't work at all. not even with that command (and it's not necessary to rename the zip file, as long as it's only one in the adb folder). I already tried that, and it doesn't work .
L.E. oh, wait mate! I think it works now! I'm waiting for the installation to be finished. do you have a good tutorial to upgrade to WWE version?
ady_uaic said:
Yes mate, I know that. Now I'm trying to put back any ROM then I will do the right procedure to install WWE.
But, now doesn't work at all. not even with that command (and it's not necessary to rename the zip file, as long as it's only one in the adb folder). I already tried that, and it doesn't work .
L.E. oh, wait mate! I think it works now! I'm waiting for the installation to be finished. do you have a good tutorial to upgrade to WWE version?
Click to expand...
Click to collapse
Im not really familiar with the dual sim versions, dont know how to s-off them, all the knowlege im giving you is just based on my M7, but to convert you will need to get s-off first, change your cid and mid to match the WWE RUU and then you'll need to flash the WWE full RUU as close to as possible to the version number you have now so that the firmware swap over goes smoothly.
Seanie280672 said:
Im not really familiar with the dual sim versions, dont know how to s-off them, all the knowlege im giving you is just based on my M7, but to convert you will need to get s-off first, change your cid and mid to match the WWE RUU and then you'll need to flash the WWE full RUU as close to as possible to the version number you have now so that the firmware swap over goes smoothly.
Click to expand...
Click to collapse
will do, thanks!
ady_uaic said:
will do, thanks!
Click to expand...
Click to collapse
When the flash has finished, let me know if it boots ok please and was successful.
Seanie280672 said:
When the flash has finished, let me know if it boots ok please and was successful.
Click to expand...
Click to collapse
with the chinese version yes, it boots ok. now I'm trying to use this tutorial for WWE: http://forum.xda-developers.com/showthread.php?t=2559891
ady_uaic said:
with the chinese version yes, it boots ok. now I'm trying to use this tutorial for WWE: http://forum.xda-developers.com/showthread.php?t=2559891
Click to expand...
Click to collapse
just had a quick read through it, I would be cautious flashing HBOOT before getting s-off, if I was you I would use the moonshine s-off method for your HBOOT and device version first before flashing the HBOOT, make sure these have not changed after flashing an updated RUU.
A bad HBOOT flash will hard brick your device.
Seanie280672 said:
just had a quick read through it, I would be cautious flashing HBOOT before getting s-off, if I was you I would use the moonshine s-off method for your HBOOT and device version first before flashing the HBOOT, make sure these have not changed after flashing an updated RUU.
A bad HBOOT flash will hard brick your device.
Click to expand...
Click to collapse
I will have a look right now. what do you mean by device version?
ady_uaic said:
what do you mean by device version?
Click to expand...
Click to collapse
sorry, forget that, they are all for the 802w, threw me out a bit as he labelled the moonshine one as (for the 802w version)
ps, firewater no longer works, its been discontinued, lets hope your not on that HBOOT. :fingers-crossed:
Seanie280672 said:
sorry, forget that, they are all for the 802w, threw me out a bit as he labelled the moonshine one as (for the 802w version)
ps, firewater no longer works, its been discontinued, lets hope your not on that HBOOT. :fingers-crossed:
Click to expand...
Click to collapse
problem solved. now it has wwe. thanks mate!