Develop Bugs

[Q] Unable to reset to stock

I've been trying to reset my HOX to stock for OTA JB update, but it keeps going into boot loops in which the only solution is to hold down the vol_down to go into bootloader.
I've been following vladnosferatu's method 2:
Extract the rom.zip from RUU of your CID (google how extract ruu.exe)
-fastboot oem readcid (to know your CID)
Extract boot.img, system.img, signed_recovery.img from rom.zip
Flash
-fastboot flash recovery signed_recovery.img
-fastboot flash boot boot.img
-fastboot flash system system.img
-fastboot erase cache
-fastboot oem lock
Power on the phone
Run the RUU exe file (of your CID) and upgrade your phone
Click to expand...
Click to collapse
the bootloops start after oem lock.
I tried ClydeB1's noob-friendly method first, but it won't work since I'm already on 2.xxxxxxxx, and it refuses to downgrade to 1.xxxxxxxx
and I was on Renovate rom before this.
I have reset to Stock from Renovate once before, but now I can't seem to do it again. I have adb, fastboot and RUU(and extracted rom.zip)
What should I do? I've considered re-flashing CWM, flashing a Renovate again and restart the entire process, but I would like to confirm whether it would work first.
Thanks in advance for all responses!
UPDATE: I have just realised that there are 2.14 and 2.17 RUUs for my .707. I am now downloading those and trying if re-applying the steps using the updated RUUs will work.

Seriously .......WHY DIDN'T YOU TAKE 2 MINUTES TO MAKE A NANDROID BACKUP !!!!

if you upgraded the hboot you can only revert to stock when JB OTA is availabe for download an flash.

donhashem.dh said:
Seriously .......WHY DIDN'T YOU TAKE 2 MINUTES TO MAKE A NANDROID BACKUP !!!!
Click to expand...
Click to collapse
Because I have done this before perfectly fine, so I didn't expect anything to go wrong. I'd be sure to do it next time.
Seelendrache said:
if you upgraded the hboot you can only revert to stock when JB OTA is availabe for download an flash.
Click to expand...
Click to collapse
My hboot is 2.x, but it's not even the JB hboot of 3.x. I have been able to flash ROMs just fine on 2.x, so why can't I revert to stock? The 2.x hboot is obtained from stock OTA in the first place, too.

Just download the 2.17.707.3 RUU, then put your device is fastboot mode, relock the bootloader - fastboot oem lock
Then in fastboot mode too, run the RUU... you will for sure be on stock rom; there is no need to extract this and that and bla bla bla
And there is a JB OTA awaiting for your device
---------- Post added at 11:16 PM ---------- Previous post was at 11:15 PM ----------
donhashem.dh said:
Seriously .......WHY DIDN'T YOU TAKE 2 MINUTES TO MAKE A NANDROID BACKUP !!!!
Click to expand...
Click to collapse
What are you doing here, Don ? Change phone ?

ckpv5 said:
Just download the 2.17.707.3 RUU, then put your device is fastboot mode, relock the bootloader - fastboot oem lock
Then in fastboot mode too, run the RUU... you will for sure be on stock rom; there is no need to extract this and that and bla bla bla
And there is a JB OTA awaiting for your device
Click to expand...
Click to collapse
Hi ckpv5, I have also noticed that the 3.14.707 and 3.17.707 RUU has been uploaded. Can I just RUU the 3.17.707, skipping the manual 2.17.707? Because the only reason why I'm reverting to stock, is to update my hboot to 3.x, so that I can flash JB ROMs. Bypassing the 2.17-3.17 OTA would save quite some time.

Ya... I would do that if I were you... straight away run the 3.14 RUU instead of 2.17; but the RUU comes out after I did the OTA. So not so sure if it works that way but theoretically it should.
Just a note, the JB RUU, you cannot do the extract thingy.. so just relock the bootloader and run the RUU.

-- question deleted cause I saw some numbers wrongly that caused confusion =/ --

Hehe no ....just got bored from the one v forums ...nothing new happening :thumbdown:

ckpv5 said:
Ya... I would do that if I were you... straight away run the 3.14 RUU instead of 2.17; but the RUU comes out after I did the OTA. So not so sure if it works that way but theoretically it should.
Just a note, the JB RUU, you cannot do the extract thingy.. so just relock the bootloader and run the RUU.
Click to expand...
Click to collapse
Unfortunately this doesn't seem to work. The 3.14 gives me an error saying something about finding the right RUU for my device. Now downloading 2.17.707. Man htcruu downloads keep timing out halfway and I have to restart over and over :crying:
UPDATE: Yeah so it seems I had to RUU 2.17, and manually get 3.14 from OTA in order to upgrade. Can't skip that step.

[Q] Q: Firmware Package HTC One X

I'm going to update my htc one x to jelly bean from ICS, using custom ROM (ARHD), it was noted that I need a firmware package, and now that I found the package for my CID because took sometime before I found it, is it really required to flash it? TIA

For JB roms you need a JB hboot those are the 1.31 and higher up. Except for the aosp JB roms, those run also on the lower ics hboots.
So if you are on a lower hboot then 1.31 then yes you need to upgrade the hboot

Now I think everything's messed up and I badly need help here, so stupid with I did.
At one moment, my phone is stuck at One tm screen, after I flash the boot.img and installed the custom ROM. I tried to restore my phone using CWM but it still stucked. It was too late before I realized how to flash the firmware package that I need to rename what I downloaded to firmware.zip. I tried flashing the firmware without knowing that I have to relocked my phone before I flash it. Now I relocked my phone and I'm stucked with hboot and I can't do anything at the moment.

With it relocked. In fastboot do
fastboot oem rebootRUU (note the capitals)
Your phone will then reboot into a black screen with the HTC logo.
Then do fastboot flash zip firmware.zip
Once completed fastboot reboot-bootloader
It will reboot into bootloader
Then unlock and flash recovery again.
Flash boot image and reinstall ROM and you should be good to go
Sent from my HTC One X using xda app-developers app

bagofcrap24 said:
With it relocked. In fastboot do
fastboot oem rebootRUU (note the capitals)
Your phone will then reboot into a black screen with the HTC logo.
Then do fastboot flash zip firmware.zipOnce completed fastboot reboot-bootloader
It will reboot into bootloader
Then unlock and flash recovery again.
Flash boot image and reinstall ROM and you should be good to go
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Cannot load "firmware.zip" always shows up. My CID is HTC_044, and as far as I know I downloaded the correct firmware package for my phone according to ARHD forum. Thanks in advance.

Did you have the firmware.zip in your fastboot folder?

Yes. And I downloaded it 3 times just to make sure it is the right firmware.

Oh and sometimes you need to flash it 3 or 4 times to succeed. I had to do the command 3 times when I flashed my firmware.
So try it multiple times in a row.
Sent from my One X

Sorry but I tried several times and "error: cannot load 'firmware.zip' all the time. What could be the problem?
During at work. I thought if is it possible just to return to stock ROM? But I just can't find the proper RUU yet.
cid: htc_044
version-main: 1.29.707.11

I'm currently charging my phone using the batch file I found here in xda. I saw a lot of posts regarding flashing the current version of CWM so you can charge your battery, I think my CWM is in version 5.8.1.0, and as far as I know you have to unlock your hboot before you can flash recovery, so it's impossible for me to flash 5.8.4.0? Am I correct here or I can just proceed to the other steps?

I can check tonight if i have your RUU !

Mr Hofs said:
I can check tonight if i have your RUU !
Click to expand...
Click to collapse
Thank you Mr Hofs! And, should my battery level is 30% or higher before I can flash the RUU?

Yes ! If you can't get enough power with the batt script you can flash the latest cwm recovery and charge the battery in there to 100% if you want to.
Unlock the bootloader first if it is still locked

Mr Hofs said:
Yes ! If you can't get enough power with the batt script you can flash the latest cwm recovery and charge the battery in there to 100% if you want to.
Unlock the bootloader first if it is still locked
Click to expand...
Click to collapse
I was done in re-unlocking my bootloader, but then I still can't flash cwm recovery because it says low battery, then I tried to use the batt script again and of course it cannot work since I just re-unlocked my bootloader.

I never tried it with a unlocked bootloader, have you tried it ?

Yes, I tried it and it doesn't work.
What I did for the past hours, I tried to restore my phone again using cwm recovery, still nothing changed, still stucked at htc one logo, then I turned it off trying to charge it using the main charger and it does have light in its LED, left it for a while and now it doesn't turn on.

Try it with phone connected to the pc, it seems to make a difference sometimes....and if you are capable again to run the bat script then leave it for 2.hours or so !

Now it's working. The first time I used the batt script, I thought it could charge more than 3681mV but It didn't work as it didn't get higher than 3681mV. I HOPE it's enough just to flash the cwm recovery. Thanks Mr Hofs, will update asap.

[SOLVED] Hboot upgrade attempt failed

I'm trying to help a friend remotely fix his current brick of a HOX and would like some pro advice to ensure im telling him the right thing. Info I have:
Its S-On UK T Mobile CID T-MOB005.
He obtained a 1.39 firmware from somewhere that matched his CID
At some point in the process the firmware flash failed or partially flashed
His Custom Recovery is gone
His HBoot version has not increased (i think 1.12)
He has a security warning under the 'relocked' message in bootloader
Before he tried the firmware upgrade he flashed viper x 3.4.0 + boot.img so the phone wont boot up normally now
He has a nandroid backup from before the process.
Im going to recommend to him to download the 1.36 firmware from Mikes thread here http://forum.xda-developers.com/showthread.php?t=1957376 (i notice there is no 1.39 available for his CID so im suspicious this was a duff file he had for 1.39)
If he cant flash it because of low power then he should use the charging batch script first or re-unlock, flash CWM, restore nandroid and flash the boot.img from it so he can boot phone and charge it normally or from cwm.
I guess after that start to look at an RUU or a stock nandroid backup download to be able to do the firmware OTA ?
My own HOX is S-Off so im not as familiar with the process as i never worried about the correct firmware or had to flash boot.img separately from roms or nandroids.
Any tips appreciated.
Cheers

Re: Hboot upgrade attempt failed
Yeah that's about it.....only flashing the rom is not going to work because of the low hboot.
Just charge the battery and and unlock the bootloader, then reflash a custom recovery and charge the battery up in there.
With enough power he can relock the bootloader and flash the firmware
Fastboot oem lock
Fastboot rebootRUU (watch the capital letters)
Fastboot flash zip firmware.zip
Unlock the bootloader
Fastboot flash unlocktoken unlock_code.bin
Then flash the custom recovery again and install a new rom ! :thumbup:

Cheers, so out of interest what causes the Security Warning in the bootloader ? Is it because the phone knows there is a screwed up firmware flash or knows it cant boot\has low power ? It must have done something as his custom recovery was wiped even though the Hboot ver didnt change.

how does the security warning look like exactly.....i know there is a warning because the bootloader is relocked. don't know if we are talking about the same picture now

Re: Hboot upgrade attempt failed
You have to relock the boot loader to flash an updated firmware which is the point you are at and why you are seeing the security warning.
The first time you flash the updated firmware it flashes everything else.
Stock recovery, boot.IMG and sometimes other partitions.
Then it tries to flash the hboot and fails.
All you usually have to do is tell it to flash a second time and then in succeeds in updating boot.
Obviously he stopped after the first attempt which is why only the recovery changed and not the hboot.
I doubt he has a bogus firmware as the phone will not attempt to flash anything that isn't signed and cid matched.
Sent from my HTC One X using xda app-developers app

bagofcrap24 said:
You have to relock the boot loader to flash an updated firmware which is the point you are at and why you are seeing the security warning.
The first time you flash the updated firmware it flashes everything else.
Stock recovery, boot.IMG and sometimes other partitions.
Then it tries to flash the hboot and fails.
All you usually have to do is tell it to flash a second time and then in succeeds in updating boot.
Obviously he stopped after the first attempt which is why only the recovery changed and not the hboot.
I doubt he has a bogus firmware as the phone will not attempt to flash anything that isn't signed and cid matched.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Great will check, just assumed he had tried it twice as all instructions I've seen state that you must but then again i dont know what instructions he followed - maybe he didnt ! Ive not seen this explanation of whats being flashed and in what order before - cheers.

Mr Hofs said:
how does the security warning look like exactly.....i know there is a warning because the bootloader is relocked. don't know if we are talking about the same picture now
Click to expand...
Click to collapse
Ive not seen it but i assume its something like this
*** RELOCKED ***
*** Security Warning ***
Then all the usual bootloader stuff
based on images ive seen before on web. can find them with a quick google of images.

Re: Hboot upgrade attempt failed
Yeah that's normal :thumbup:

Re: Hboot upgrade attempt failed
Ok it lives ! Was a combination of the firmware file and his battery being too low to flash so he put cwm back on, charged and then followed my instructions. Cheers for help
This is the what I sent him incase anyone else finds them useful. Assumes you know roughly what your doing and that you must get back to fastboot usb for the commands .
-----------------------------
So get phone into fastboot mode by power plus vol and choose it in bootloader., plug usb in so it says fastboot usb, then get command prompt in directory with fastboot in on pc.
1. Lock bootloader with: fastboot oem lock
2. Vol and power down to get into bootloader again
3.fastboot oem rebootRUU
4. Should now get phone with silver HTC in middle on black
5. fastboot flash zip firmware.zip where this is the new firmware for your cid.
6. Might fail first time. Do it again and it works
7. Should now see green bar completed under the htc
8. Power and vol to get to bootloader. The hboot should now be updated.
9. Now to unlock bootloader again
. fastboot flash unlocktoken unlockcode.bin (where unlockcode.bin is the file you got from htcdev)
10. Now on the phone select yes and it reboots.
11. Don't wait just use power and vol to get into bootloader.
12. Flash custom recovery again. fastboot flash recovery recovery.img where recovery.img is the cwm 5.8.4.0
13. You can now flash your chosen Rom boot.img. fastboot flash boot boot.img
14. fastboot erase cache
15. Now use recovery to flash the Rom.
16. Done
Sent from my HTC One X

Very good :thumbup:
CASE CLOSED !

I have to say that the OP did a great job at providing the needed information. I wish everyone would describe their problems as good as the OP of this thread, it would make helping people out hell of a lot easier.
Sent from my HTC One X using xda app-developers app

ViktorN said:
I have to say that the OP did a great job at providing the needed information. I wish everyone would describe their problems as good as the OP of this thread, it would make helping people out hell of a lot easier.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
So true !

Indeed. Not very often you can tell exactly where a problem is without having to ask for more info. In fact. A thanks to the op for providing a very detailed diagnosis without even having the device to hand
Sent from my HTC One X using xda app-developers app

[Q] optus001 RUU>problems flashing

So i was running a 4.0 custom rom (skydragon) and was looking to go to stock 4.1 then custom rom from there. i cant find too much about the optus001 branded one x but found what i thought to be a correct method
Downloaded a nandroid backup - Stock JB Optus Australia 3.14.980.27
boot into bootloader
fastboot erase cache
fastboot flash boot.img
Recovery>nandroid backup current rom
Nandroid restore downloaded backup
fastboot flash recovery (stock recovery)
wipe user data/cache/dalvik cache
after doing all this im given a bootloop and im not sure where to go from here. ive flashed many phones successfully with minimal issues but im kinda lost here and ive been reading through forums trying to work out where i went wrong
So im wondering if i should download the RUU and do it that way but then my problem is the site that people have linked for the standard RUU just doesnt work (http://htcruu.com/?dir=Endeavor) it wont load at all.
any ideas where i went wrong and what i can do to rectify this (other than a nandroid restore of my current custom rom)

bikerboi85 said:
So i was running a 4.0 custom rom (skydragon) and was looking to go to stock 4.1 then custom rom from there. i cant find too much about the optus001 branded one x but found what i thought to be a correct method
Downloaded a nandroid backup - Stock JB Optus Australia 3.14.980.27
boot into bootloader
fastboot erase cache
fastboot flash boot.img
Recovery>nandroid backup current rom
Nandroid restore downloaded backup
fastboot flash recovery (stock recovery)
wipe user data/cache/dalvik cache
after doing all this im given a bootloop and im not sure where to go from here. ive flashed many phones successfully with minimal issues but im kinda lost here and ive been reading through forums trying to work out where i went wrong
So im wondering if i should download the RUU and do it that way but then my problem is the site that people have linked for the standard RUU just doesnt work (http://htcruu.com/?dir=Endeavor) it wont load at all.
any ideas where i went wrong and what i can do to rectify this (other than a nandroid restore of my current custom rom)
Click to expand...
Click to collapse
Hey,
Try this post:
http://forum.xda-developers.com/showthread.php?t=2119610
EDIT: Did you fastboot oem lock?

Thanks for the quick reply but theres nothing in that thread with the optus001 cid RUU or nandroid wise

bikerboi85 said:
Thanks for the quick reply but theres nothing in that thread with the optus001 cid RUU or nandroid wise
Click to expand...
Click to collapse
Optus Australia jellybean 3.14.980.27 nandroid
http://ul.to/bvcpzcgl

was that in that thread? i used ctrl+f to find optus but it didnt find anything on any of the pages. odd

No,
In a different thread

oh ok. yeah thats the same file i used to start with

Also i didnt see u ask til just now, no i didnt oem lock am i supposed to? i didnt see it in the thread i was reading about the nandroid backup to stock. ill check again and start all over from the start as i just nandroid restored to my custom rom

Follow this post :
http://forum.xda-developers.com/showthread.php?t=1609190
Should work for you

Thanks for the help dude. that tutorial got me back to stock fine. +1 to you sir

bikerboi85 said:
Thanks for the help dude. that tutorial got me back to stock fine. +1 to you sir
Click to expand...
Click to collapse
Always happy to help

while ur around, how do i go about flashing from stock 4.1 to custom 4.1. im guessing its not that difficult anymore being that the hboot gets updated with the OTA update. i would figure its like flashing a rom before hand.
unlock bootloader
fastboot flash CWM
fastboot erase cache
fastboot flash custom rom boot.img
fastboot erase cache
Recovery> flash custom rom zip file
Wipe data/cache
reboot?

Re: [Q] optus001 RUU>problems flashing
bikerboi85 said:
while ur around, how do i go about flashing from stock 4.1 to custom 4.1. im guessing its not that difficult anymore being that the hboot gets updated with the OTA update. i would figure its like flashing a rom before hand.
unlock bootloader
fastboot flash CWM
fastboot erase cache
fastboot flash custom rom boot.img
fastboot erase cache
Recovery> flash custom rom zip file
Wipe data/cache
reboot?
Click to expand...
Click to collapse
Unlock bootloader
Flash custom recovery
Flash custom boot.img
Fastboot erase cache
Recovery- full wipe (everything except sdcard)
Install custom rom
Reboot

lol i was close. thanks bud

bikerboi85 said:
while ur around, how do i go about flashing from stock 4.1 to custom 4.1. im guessing its not that difficult anymore being that the hboot gets updated with the OTA update. i would figure its like flashing a rom before hand.
unlock bootloader
fastboot flash CWM
fastboot erase cache
fastboot flash custom rom boot.img
fastboot erase cache
Recovery> flash custom rom zip file
Wipe data/cache
reboot?
Click to expand...
Click to collapse
fastboot flash unlocktoken unlock_code.bin
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
Recovery>BACKUP!!
Recovery>Wipe data/factory reset+cache+advenced>wipe Dalvik cache
Recovery>install rom, gapps (&vendor installer for cm10.1)
Reboot
Enjoy!

Hboot
Ok, so I have spent the last few days messing around with trying to update my version of renovate, I have managed to get everything working rom loaded custom recovery flashed, New Optus OTA installed. But it won't let me update the bootloader no matter what I do, I thought the stock 1.29 RUU should do that, but neither that or the OTA updated Hboot. So I tried the JBFW flasher tool, that gives an error of 42 custom id fail.... Even with a stock recovery,rom and kernel...
I'm lost, I have run out of threads to read, this thread seems the most related to my phone/issue.
What do you guys think?
I'm on 0.95 Hboot, 4.0.3 ICS, 1.29 Optus 001.

Deviat said:
Ok, so I have spent the last few days messing around with trying to update my version of renovate, I have managed to get everything working rom loaded custom recovery flashed, New Optus OTA installed. But it won't let me update the bootloader no matter what I do, I thought the stock 1.29 RUU should do that, but neither that or the OTA updated Hboot. So I tried the JBFW flasher tool, that gives an error of 42 custom id fail.... Even with a stock recovery,rom and kernel...
I'm lost, I have run out of threads to read, this thread seems the most related to my phone/issue.
What do you guys think?
I'm on 0.95 Hboot, 4.0.3 ICS, 1.29 Optus 001.
Click to expand...
Click to collapse
Get the main version number !
Fastboot getvar version-main

Mr Hofs said:
Get the main version number !
Fastboot getvar version-main
Click to expand...
Click to collapse
1.29.980.11

Here is your ruu to go back to stock
http://bugsylawson.com/index.php/fi...11-radio-1120410514-release-260560-signedexe/
Relock the bootloader and execute the ruu with admin rights. Keep the phone in the bootloader when executing the ruu

Mr Hofs said:
Here is your ruu to go back to stock
http://bugsylawson.com/index.php/fi...11-radio-1120410514-release-260560-signedexe/
Relock the bootloader and execute the ruu with admin rights. Keep the phone in the bootloader when executing the ruu
Click to expand...
Click to collapse
I already have that Ruu and have done that like 20 times Is the Silver HTC screen still part of the boot loader, I'm guessing so?

[Q] Need help updating to Hboot 1.72

Hello all,
The name of this post says it all really, I am trying to update to Hboot 1.72 but I have no idea how This may be difficult as I have a new computer, and don't have any of the old folder I used to do this before so I will have to start from scratch again I have the Android SDK, so I can take any files needed from there, but apart from that I literally have nothing. Also, I am a complete novice with all this stuff so you may need to "dumb down" your answers a bit Thanks in advance.
Current:
Hboot: 1.32.0000
CID: HTC_001
CWM: 5.8.4.0

TheBlaaaaah said:
Hello all,
The name of this post says it all really, I am trying to update to Hboot 1.72 but I have no idea how This may be difficult as I have a new computer, and don't have any of the old folder I used to do this before so I will have to start from scratch again I have the Android SDK, so I can take any files needed from there, but apart from that I literally have nothing. Also, I am a complete novice with all this stuff so you may need to "dumb down" your answers a bit Thanks in advance.
Current:
Hboot: 1.32.0000
CID: HTC_001
CWM: 5.8.4.0
Click to expand...
Click to collapse
Read THIS for the simple method.

Since you are HTC__001 you'll get the ota soon you just need to be on stock rom, kernel and recovery and you are good to go

desmond1303 said:
Since you are HTC__001 you'll get the ota soon you just need to be on stock rom, kernel and recovery and you are good to go
Click to expand...
Click to collapse
The reason I'm trying to do this is because I'm on CyanogenMod 10.1 and the 10.2 update (Android 4.3) requires the newer hboot, so how would I go about doing this myself (step by step)?
Also Tigerlight, I'm fairly confident that JB FW doesn't let you use non Sense based ROM's afterwards, and to be honest I prefer doing things like this myself rather than letting software do it for you

Well...
You should be able to have CM 1.2 on 1.39...
But you Will have to wait for the firmware zip to be uploaded here http://forum.xda-developers.com/showthread.php?t=1957376
in order to be able to update it manually... You could download the OTA files and extract that firmware.zip yourself and than find a tutorial on how to flash a firmware.zip... there are plenty of them out here

TheBlaaaaah said:
The reason I'm trying to do this is because I'm on CyanogenMod 10.1 and the 10.2 update (Android 4.3) requires the newer hboot, so how would I go about doing this myself (step by step)?
Also Tigerlight, I'm fairly confident that JB FW doesn't let you use non Sense based ROM's afterwards, and to be honest I prefer doing things like this myself rather than letting software do it for you
Click to expand...
Click to collapse
JBFW flasher upgrades hboot, which has nothing whatsoever to do with what Sense or AOSP ROM you flash afterward so long as that hboot is compatible.
And why on earth type all the instructions manually when the tools exist.
And the 1.72 hboot firmware has been uploaded HERE.

Tigerlight said:
JBFW flasher upgrades hboot, which has nothing whatsoever to do with what Sense or AOSP ROM you flash afterward so long as that hboot is compatible.
And why on earth type all the instructions manually when the tools exist.
And the 1.72 hboot firmware has been uploaded HERE.
Click to expand...
Click to collapse
Ok, may have been a bit wrong there..... :silly: Still, I like to learn how to do this sort of thing so that if anything ever goes wrong I have the knowledge to fix it. Once I have the firmware, what do I need to do?

Just downloaded JBFW out of interest, and when you go to update it says this: After upgrade you will not be able to - Install a fully functional Non-Sense ROM, so I was right that I can't use that software, and anyway wouldn't want to tbph Anyone know how to manually update hboot given that I have no files from when I rooted anymore? :laugh:

Once you have the firmware.zip file you have to
1:relock the bootloader
Fastboot oem lock
2: boot into ruu mode
Fastboot oem rebootRUU
3: flash the firmware.zip
Fastboot flash zip firmware.zip
Maybe needed twice (only if the command returns an error)
Then unlock the bootloader and flash a custom recovery. Preferably repacked twrp, or philz touch recovery.
Then full wipe the phone in recovery and install the rom.zip and fastboot flash the boot.img.
That sums it up pretty much

Mr Hofs said:
Once you have the firmware.zip file you have to
1:relock the bootloader
Fastboot oem lock
2: boot into ruu mode
Fastboot oem rebootRUU
3: flash the firmware.zip
Fastboot flash zip firmware.zip
Maybe needed twice (only if the command returns an error)
Then unlock the bootloader and flash a custom recovery. Preferably repacked twrp, or philz touch recovery.
Then full wipe the phone in recovery and install the rom.zip and fastboot flash the boot.img.
That sums it up pretty much
Click to expand...
Click to collapse
Thanks Mr Hofs,
Already found out about 20 mins ago: you actually responded to someone else a while back and I used those instructions. I may have messed up quite a lot though: forgot to put the CM 10.2 zip on the phone before hand and now the phone is acting really weird..... I'll let you know if I need help but I have a few ideas first
Thanks again, I appreciate the help.