Hi
Having some issues with HOX
My mainver is: 3.78.61.6 HIGER THAN ANY EXISTING MAINVER POSSIBLE
I can ONLY install stock software via CustomRUU as i need to match mainver to = 3.78.61.6 WHICH IS HIGHER THAN JB!!!
ONCE INSTALLED I CAN NOT OTA UPGRADE because MainVer is HIGHER than JB update.
So it just crashes after installed (At Lock Ring). Because stock is installed i MUST do OTA update as phone insists i update.
JB RUU DOES NOT EXIST for my CID BUT OTA JB UPDATE DOES
Cid: TELNZ001
hboot 1.12.000 (BUT UPDATE IS INCLUDED IN OTA)
I have the ota zip file, which has FOLDERS not IMG so is not flashable.
HOWEVER DOES contain Firmware.zip with HBOOT 1.39 FOR TELNZ001 in it but is not flashable.
I have two questions:
Can anyone help me to downgrade / fool mainver, so i can revert back to stock and OTA to JB
OR
IS there a way to flash the hboot.img from OTA update.
I CANNOT flash firmware.zip from OTA as its CORRUPT and has been CORRUPT from every download site.
Thanks
How many threads are you gonna open for this
Mr Hofs said:
How many threads are you gonna open for this
Click to expand...
Click to collapse
Lol no matter what i post i get completly different answers than im actually looking for.
I know there is a way to charge mainver on some htc phones.
no one seems no one has a telnz001 JB backup.
and im having trouble flashing the hboot img
if i can flash the boot img i can run a jb rom...
What's the problem with flashing then ?
problem with flashing hboot?
There is NOTHING telling me how to flash the hboot.img file itself except for ruu / firmware.zip WHICH come back with errors, through fastboot i get error 99 unknown.
i cant flash it via the firmware.zip as mainver in the OTA JB ZIP is too low. either that or i need to find a way to sign the zip which is impossible.
and if i rebuild it ( make the mainver higher in the text file higher to match my mainver which is 2.76.xx.xx ) it refuses to flash.
the problem is .... i cant flash the hboot as it appears the only way is via ruu / ruu mode with firmware.zip
which is because my mainver is 3.76.xx.xx
next problem is even IF i could flash firmware.zip or ruu to an OLDER version is it updates the stock software to 2.17 but mainver still remains 3.76.xx.xx so its impossible to do the jb update which is 3.17.xx.xx
does a zip exist to make my mainver 1.00.00.00 as i would just be able to flash ruu and OTA and it will work
ive tried the mainver fixes and nothing has worked so far.
An older firmware.zip is never gonna work, you need S-OFF for that. The best is to get a nandroid backup ..... it doesn't matter if that is older or not. When you get hands on a nandroid you can restore it and update with official ota. Even if its an old one. The hboot will stay the same during updstes. The only thing that get updated is the software.
as far as I read about this, you can never downgrade with S-ON
if you want to keep using Sense , You need to look for a backup for your CID.
and I think you're probably figured that out by now
I think rephrasing the question might help you get someone to aid
and maybe you can upload the Firmware.zip for advanced developers to look at, you might get lucky and someone find an answer to you problem
anyway, you can read This , it's about Unlocking CID TELNZ001, might help?
Mr Hofs said:
An older firmware.zip is never gonna work, you need S-OFF for that. The best is to get a nandroid backup ..... it doesn't matter if that is older or not. When you get hands on a nandroid you can restore it and update with official ota. Even if its an old one. The hboot will stay the same during updstes. The only thing that get updated is the software.
Click to expand...
Click to collapse
I ony have one little problem with restoring from nandroid...
that is:
it does a couple of updates before the jb update is available
so it hits the 2.17 update maybe the update just after that and gets stuck on the lock screen and constantly reboots.
Very fustrating phone now in boot loop after OTA update.
does this EVERY time
relocked
stock boot and stock recovery.
misterr.mann said:
Very fustrating phone now in boot loop after OTA update.
does this EVERY time
relocked
stock boot and stock recovery.
Click to expand...
Click to collapse
please read this : http://forum.xda-developers.com/showpost.php?p=36977974&postcount=1
Related
I have unlocked my OneX, root it using PaulBrien's method, and then stripped off all the sense stuff. I didn't install any custom rom all these while.
Then I decide to revert back to stock. I do the following
1. flash back stock recovery
2. lock back the one-x using fastboot oem lock
3. run the ruu executable.
It worked as I managed to complete the ruu flashing process, and proceed with the system upgrade OTA to 1.28
then, I had problem with the rooted 1.28 (again stock 1.28 rooted using Paul's version) so I did a CWM recovery back to my rooted 1.26 ROM.
Now, I decide to flash stock rom back to my OneX, I repeated the steps above, and instead I got this error from the RUU app.
Any reason what has happen? I even tried flash the 1.26 signed boot.img prior to step 3, but it still yield the same problem.
Thanks...
Since you updated to 1.28 you need the 1.28 RUU. When you updated it changed you hboot
Sent from my HTC One X using Tapatalk 2
I didn't know it change the hboot.
can I flash 1.26 hboot over?
strangely, I didn't have the problem the first time round, maybe something went wrong in between.
zenkinz said:
I didn't know it change the hboot.
can I flash 1.26 hboot over?
strangely, I didn't have the problem the first time round, maybe something went wrong in between.
Click to expand...
Click to collapse
i dont think so until we get S-OFF
this problem happen for me
you are only download other ruu
only other ruu download and enjoy
You need the 1.28 RUU as you've done the OTA 1.28 update.
If your version is 1.28.707.10, here is the RUU : http://bit.ly/IjzQwM
Else, please let us know your software version no. and someone will point you to the right RUU.
I have an HTC one x that i bought has been rooted, on aftermarket software. Mainver is 4.78.61.6.. i am trying to return to stock.
I cant install RUU as the RUU available is ICS and can not downgrade as mainver is too high, nor can i obtain a JB RUU as a telecom nz JB ruu does not exist.
I have tried everything and searched fourms for months.
flashing ruu / firmware.zip or rom.zip always comes back with an error, signature error or mainver error. from what i can tell this mainver does not exist anywhere in the world it is FAR too high to even upgrade to any existing JB stock software.
i tried extracting rom.zip from telecom nz ics firmware and matching the mainver to be the same is the only way to return to stock using customRUU or ruu flash tool... BUT when it updates to the 4th or 5th update (system update just bofore the JB update) it freezes on boot, and does lots of weird things suck as booting into recovery / ruu / fastboot.
i have tried flashing telnz001 nandroid backup of ICS (JB not available)
everything is returned to factory spec when i do this, relocked, stock recovery etc
its on an older version of hboot (the one included in stock telnz001)
Cant upgrade hboot.
tried misc tool to change mainver to 1.00.00.0 BUT IT DOESNT WORK.
ALL that will run on it is a aftermarket rom.
IS there any other way to change the mainver?
would a nandroid backup of JB on telnz001 work?
why would it fail or play up on upgrades OTA ( mainver is NEWER than the OTA updates )
really need to return to stock and upgrade to JB
thanks
I don't seem to recognize that main version, can you check and tell me what your bootloader says. The top 3-4 lines .....
it
Mr Hofs said:
I don't seem to recognize that main version, can you check and tell me what your bootloader says. The top 3-4 lines .....
Click to expand...
Click to collapse
It says
***Unlocked***
ENDEAVORU PVT SHIP S-ON RL
HBOOD-1.12.0000
CPLD-None
MICROP-None
RADIO 0-5. 1204. 163r. 30
(is that what you wanted ?
Hmm i don't see a ruu with that number anywhere, and also no "new" stock nandroid backup
What's your exact cid
Fastboot oem readcid
Mr Hofs said:
Hmm i don't see a ruu with that number anywhere, and also no "new" stock nandroid backup
What's your exact cid
Fastboot oem readcid
Click to expand...
Click to collapse
TELNZ001
I think you are out of luck.....i can't find any useful info on your main version. Sorry mate..... Like you said, no ruu no matching firmware....
Mr Hofs said:
I think you are out of luck.....i can't find any useful info on your main version. Sorry mate..... Like you said, no ruu no matching firmware....
Click to expand...
Click to collapse
The Main version is reading 3.27.000.0 now after installing latest carbon 4.2.2 if this helps any
You need the main version that comes out with fastboot command.
Fastboot getvar version-main
The main number on a custom rom doesn't say anything. When you flash a wwe rom it will change to something like 3.14.401 or 2.17.401 for example.
You need the main version that is embedded in the hboot version.
Do the fastboot command and check if its the same number as stated in the opening post. If its different it might be useful
Mr Hofs said:
You need the main version that comes out with fastboot command.
Fastboot getvar version-main
The main number on a custom rom doesn't say anything. When you flash a wwe rom it will change to something like 3.14.401 or 2.17.401 for example.
You need the main version that is embedded in the hboot version.
Do the fastboot command and check if its the same number as stated in the opening post. If its different it might be useful
Click to expand...
Click to collapse
Have and Mainversion now reads 3.27.000.0 and HBOOT is still 1.12.0000
So its not the one from the OP. But still i haven't seen this number around either
Mr Hofs said:
So its not the one from the OP. But still i haven't seen this number around either
Click to expand...
Click to collapse
Yeh I have looked and cannot find anything either any ruu I use gets to around 80% then crashes with wrong boot error , they are the Telecom ones.Frustrating as well .
Mainver is higher than any mainver that exists for htc one.
I found out the androidinfo.txt in a zip file was updated in attempt to roll back software to ICS.
so basically i have two questions,
Is there ANY possible way to downgrade mainver. I have tried misc tool and cannot get it to work.
My other question is does anyone have a nandroid backup of JB for CID TELNZ001
and if i can get the backup all i need to do is upgrade the hboot. which i have also tried and have not been able to achieve.
Could someone please upload a backup image for cwm of JB TELNZ001 with updates included. and hboot file.
Or a firmware.zip with JB system, hboot, boot and recovery for TELNZ001.
thanks =]
im afraid there is nothing you can do...
if your hboot doesn't support JB you're out of luck
except hope that when sense 5 arrives it, comes with a higher main ver
misterr.mann said:
Mainver is higher than any mainver that exists for htc one.
I found out the androidinfo.txt in a zip file was updated in attempt to roll back software to ICS.
so basically i have two questions,
Is there ANY possible way to downgrade mainver. I have tried misc tool and cannot get it to work.
My other question is does anyone have a nandroid backup of JB for CID TELNZ001
and if i can get the backup all i need to do is upgrade the hboot. which i have also tried and have not been able to achieve.
Could someone please upload a backup image for cwm of JB TELNZ001 with updates included. and hboot file.
Or a firmware.zip with JB system, hboot, boot and recovery for TELNZ001.
thanks =]
Click to expand...
Click to collapse
thing is Telecom have brought out JB 4.1.2 and I cannot even get that to load back , stock was 4.1.1 any suggestions would help
Thing is. . I can update hboot.i have telnz001 hboot 1.39 i think. from memory. i just need to flash it. but i need the nandroid backup
You have hboot 1.12 that's a ics hboot, not a JB hboot.
---------- Post added at 05:55 AM ---------- Previous post was at 05:54 AM ----------
aluria2012 said:
It says
***Unlocked***
ENDEAVORU PVT SHIP S-ON RL
HBOOD-1.12.0000
CPLD-None
MICROP-None
RADIO 0-5. 1204. 163r. 30
(is that what you wanted ?
Click to expand...
Click to collapse
Look this is what you wrote
Mr Hofs said:
You have hboot 1.12 that's a ics hboot, not a JB hboot.
---------- Post added at 05:55 AM ---------- Previous post was at 05:54 AM ----------
Look this is what you wrote
Click to expand...
Click to collapse
i like how thats from a different username.. i didnt write that lol
my username is misterr.mann
I wrote that i had a ics hboot im not denying that, the part you missed was i have the 1.39 hboot for jb, which i can flash and am flashing right this second, although its not going to help me as it fails on OTA update, so what im saying is once im on hboot 1.39 ill still have that EXACT same issue, as my main ver is higher than any one that exists it wont ota update. so once hboot 1.39 is on all i will need is nandroid backup of JB telnz001, literally all i asked for was this nandroid backup rom.zip or firmware.zip
My mistake :thumbdown:
Okay so my HTC one is reverted completly back to stock (used custom ruu with system.img boot.img androiinfo.text etc)
I had to edit android txt file to MATCH my existing mainver.
After 2.17 update phone boots, gets to o lock ring, and reboots. does this constantly... non stop. my main ver is still higher then cicomming update mainver is still 3.78
i have a file for OTA update zip
file name:
OTA_ENDEAVOR_U_JB_45_S_Telecom_NZ_WWE_3.17.781.2-2.17.781.3_release_304681lsq8o9k2p8n4minf.zip
now there is no RUU for JB
My question is how can i install this update, i still have hboot for ics 1.12.0000
contents in OTA_ENDEAVOR_U_JB_45_S_Telecom_NZ_WWE_3.17.781.2-2.17.781.3_release_304681lsq8o9k2p8n4minf
contains firmware.zip with hboot 1.39
so i can extract hboot file
i can fully extract the entire firmware.zip contained in the OTA update.
But am having issues flashing through fastboot, and in RUU mode it comes back 99 unknown error
Im stuck between a rock and a hard place as both options for update fail
i tried creating a firmware.zip containing android txt file with my current mainver hboot 1.39 boot.img and recovery.img
yet this update fails.
any help would be appreicated thanks
Help please urgently needed.
I need a stock backup of JB on telecom nz. CID TELNZ001. with s on
or a firmware.zip with JB and hboot included.
Reason: MAINVER IS HIGHER THAN ANY MAINVER THAT EXISTS IN THE WORLD.
it was updated in the androidinfo.txt.... so it permently updated the mainver. unable to roll back to stock ICS as mainver is newer.
and there is no RUU for JB on telnz001.
even if there was a RUU, it would result in an error as mainver is newer than ANY JB firmware in the world 3.76.xx.
many attempts of trying firmware.zip, rom.zip ruu, flashing through fastboot, ruu mode etc all do not work.
i can restore to stock ICS software by changing androidinfo.txt to match my mainver..... but with OTA updates it results in constant rebooting or rebooting into fastboot as mainver is newer than OTA update.
and yes when i tried all this i relocked bootloader, reflashed stock boot and recovery, tried many different boot.img, recovery.img files. nothing seems to work
and 9/10 times a zip is ALWAYS corrupt.
IF ANYONE HAS JB TELNZ001 nandroid or firmware.zip could they please upload, also needed hboot so JB works thanks
You need a ICS nandroid backup or a lower version than that. Your bootloader says 1.12 hboot, that's not a JB hboot.
Mr Hofs said:
You need a ICS nandroid backup or a lower version than that. Your bootloader says 1.12 hboot, that's not a JB hboot.
Click to expand...
Click to collapse
No i dont, i need a JB firmware.zip / rom.zip or a nandroid backup, i have hboot1.39 for telnz001 which i can flash IF i get the nandroid backup.
IF i put ICS on it WILL crash on OTA updates, it reaches the 2.17 update and CRASHES it boots and reaches the ring lock screen and restarts, i have tried this dozens of times, with my own ics backup, other ics backups, extracting the rom from telecom nz ruu (ics) and everytime it crashes after the OTA.
By flashing hboot 1.39 for my own carrier i will be able to use JB TELNZ001 this is why i am asking for it, as a last resort i created a username and password specifically for this question as i have been trying to revert back to stock ( and have it FULLY UPDATE WITHOUT FAIL ) to JB and have not been able to as it fails,
after doing this i have updated kernals and other img files, and have not been able to get it to fully boot after the OTA update.
You say you have the firmware for the 1.39 hboot, yet you ask for a JB nandroid and a JB firmware. I read it very clear in your OP
No i have the hboot 1.39 FILE, NOT THE FIRMWARE, the firmware i said i had was ICS stock, which when i update it FAILS ALL the time. i made that clear, if i had the firmware for JB i wouldnt be asking for nandroid backup... all i am asking for is the nandroid backup of jb telnz001 as all i have is the ICS nandroid, ruu , firmware.zip and rom.zip, which all of the above when installed refuse to flash properly or boot, its not even the JB update it crashes on, its the update just before the JB update. However i did say i have the JB firmware OTA zip, which is USELESS as it CANNOT be flashed
Edit : nevermind !
I wish you al the best and good luck to find a nandroid.
Mr Hofs said:
Then you might have used the wrong words. The file to update the hboot to 1.39 is the firmware. And the firmware you speak of as ics stock is the nandroid backup ics !
I know what im talking about mate.
I wish you al the best and good luck to find a nandroid.
Click to expand...
Click to collapse
So do i , i obtained the hboot 1.39 from an OTA JB zip file, whch in a way i supose is firmware. but there is no way to install the zip file onto ics. or is there? its not flashable and contains recovery.img hboot 1.39 boot.img and a system folder and a few other things, if the folders were img files i would just flash these and wouldnt have a problem.
i guarantee if i can obtain a nandroid backup of JB it will work, i have been susessfull on another htc one with a very similar problem, but the problem is i cant use their nandroid they are no longer in the same town , so i am unable to use it untill one is available to download
misterr.mann said:
So do i , i obtained the hboot 1.39 from an OTA JB zip file, whch in a way i supose is firmware. but there is no way to install the zip file onto ics. or is there? its not flashable and contains recovery.img hboot 1.39 boot.img and a system folder and a few other things, if the folders were img files i would just flash these and wouldnt have a problem.
i guarantee if i can obtain a nandroid backup of JB it will work, i have been susessfull on another htc one with a very similar problem, but the problem is i cant use their nandroid they are no longer in the same town , so i am unable to use it untill one is available to download
Click to expand...
Click to collapse
Paste the firmware.zip in your fastboot folder.
THen
1. fastboot oem lock
2. fastboot oem rebootRUU
3.fastboot flash zip firmware,zip
The hboot is upgraded.But you cant boot up cause tou are locked.
Again unlock with fastboot and your unlock_tocken.bin
A standalone firmare.zip is flashable. But i don't know if it can be extracted directly from the ota. Search in the collection of firmare updates. Maybe there is news about that
The firmare can be flashed with
Fastboot oem rebootRUU
Fastboot flash zip firmare.zip
These commands and the right firmware will update the hboot to 1.39.
The only question is if you can flash the firmware.zip without it needing to be modified or not ?
i can flash a modified or unmodified firmware.zip easly with adb / fastboot with phone in RUU mode, the only problem is the contents in the OTA update are folders so its not flashable, i zip boot.img hboot file recovery.img and system.img and androidinfo.txt name it firmware.zip and flash it... the problem is i can not find the system img which has JB contents, as the zip contains apks, folders and files and its not flashable lol. hence why im asking for someone to upload nandroid backup , or a firmware.zip containing JB as i can put my TELNZ001 hboot file in the zip and susessfully flash JB onto my hox
Maybe you can ask here too about a firmware ?
http://forum.xda-developers.com/showthread.php?t=1957376
{< r o N o $ said:
Paste the firmware.zip in your fastboot folder.
THen
1. fastboot oem lock
2. fastboot oem rebootRUU
3.fastboot flash zip firmware,zip
The hboot is upgraded.But you cant boot up cause tou are locked.
Again unlock with fastboot and your unlock_tocken.bin
Click to expand...
Click to collapse
contained in the ota update is many files folders and img, except system img its just a dir folder, there is a firmware.zip but its corrupt. actually almost every zip i extract from or download (flashable ones) are ALWAYS corrupt, and i have noticed MANY peol;e have this issue.
also if i put ics on and ota it boot loops regardless of weather im locked or unlocked, regardless of boot img, recovery or even flashing kernal no matter what still boot loops
I think the firmware.zip is encrypted and not corrupt.....
Mr Hofs said:
Maybe you can ask here too about a firmware ?
http://forum.xda-developers.com/showthread.php?t=1957376
Click to expand...
Click to collapse
thanks dude, i asked there and they updated the link.. but its still 1.29 (ics)
i have a file named
OTA_ENDEAVOR_U_JB_45_S_Telecom_NZ_WWE_3.17.781.2-2.17.781.3_release_304681lsq8o9k2p8n4minf.zip
it contains firmware.zip with hboot.139 in it, i cant flash as it comes back unknown error 99
regardless of locked or unlocked bootloader.
i tried extracting files, and editing androidinfo.txt to match my mainver, but still comes back with an error.
is there any other way to flash the hboot? i have the img itself, and still have the original ota update zip but its not flashable
OK so i can only run one rom.
stock ics
any other rom will not boot, even after flashing boot.img i really just want to get this phone working
Hi, not sure if you have managed to find a nandroid backup for TELNZ001 stock firmware yet, but if you're still searching for it, here it is:
http://forum.xda-developers.com/showpost.php?p=37519317&postcount=39
Hi i have been given a HOX to look at and it's had me stumped for the last 24 hours so now i'm asking for help. Here we go.
The phone has no IMEI/Baseband. The fasboot getvar all command returns the correct IMEI to the box but it just doesn't show in android so no signal at all stuck on airplane mode etc. It's a TMOB005 cid.
Tried loads of custom roms and methods no signal.
Tried to return to stock to flash stock RUU. My main 3.16.110.4 so try RUU RUU_ENDEAVOR_U_ICS_40_S_TMO_UK_2.17.110.5_Radio_2.1204.137U.21_release_284360_signed.exe it fails with script error and all other RUU fail at bootloader version.
I downloaded recommended nandroid for my main. 2012-10-29.07.35.43 from thread on here. Flashed boot img in fastboot. Flashed stock 1.29 recovery. Got the small 1.25mb OTA but then nothing after that and still no signal.
Tearing my hair out now. HBOOT is 1.39. Let me know if i've missed any info please any ideas now will help.
Oke i will give it a go !
You restored a 2.17 nandroid backup ? And flashed back a 1.29 stock recovery ?
In this case your rom won't respond to touch on screen ! You say your main version is 3.16 then you need a nandroid backup with at least that number....and a stock 3.16 recovery and not a 1.29 one
So.....enlighten me ?
Now you have me all confused?! The touch screen works fine with the stock recovery i flashed. It's one you recommended to someone else in a TMOB005 thread i saw. I'm not sure recovery is the real issue here anyway. The issue is not being able to flash an RUU, stock not doing the OTA it only reports the small one 1.25MB. Never asked for Jellybean OTa it just doesn't want to work.
The nandroid should be correct too as it's a TMOB005 one too.
If you can help let's start from my main as we know that's 100% right.
So what nandroid stock rom do i need, what recovery and anything else required?
Thanks for reply so far.
Oke you need a stock nandroid backup 3.16 if you have it (or already restored it) that's good then. Now we need your stock 3.16 recovery and not the 1.29 one.....
Is your 3.16 number matching this command ?
Fastboot getvar version-main
Ok I'll check when I'm at home next, I'll still appreciate any help/ideas/input from anyone. I'm sure my version matches the one with the version main command.
Does the recovery version have to match too? Where would I find the relevant one?
Try this one
http://db.tt/mp3v3KrP
Mr Hofs said:
Try this one
http://db.tt/mp3v3KrP
Click to expand...
Click to collapse
Thanks and is the nan droid I mentioned the correct one at all? Like I say it offers the small OTA does that have any significance?
Is there no possible way to flash ANY RUU?!
If the nandroid matches the main version number 3.16.110 then you have indeed the correct one. And no a ruu is not available so that's not possible atm.
I saw something about an RUU hack where it makes it think you have an older version or is that not possible any more? The custom RUU file isn't available for download any more.
Well its probably possible for some, but if the phone has updated touch drivers then its of no use. Ics and lower roms don't work because touchscreen doesn't respond !
And the OP is on 3.16 so that's a no go.
From 3.14 and lower it could work.
"fastboot getvar version-main" returns that my main is definitely 3.16.110.4. So what nandroid for definite matches and what recovery? Can anyone provide links please? Is 3.16.110.4 supposed to be Jellybean?!
Yes 3.16 is Jellybean. And the recovery will be in the nandroid backup, as well as the boot.img.
Will the nandroid backup not have clockwork mod recovery in it as that is required to make the backup?!
Hold on....
you have the 3.16.110 nandroid backup ?
No i have a main of 3.16.110.4. I have the 2.17.110.5 nandroid as i understand this should work for OTA as i read in another thread. As long as the red part matches. I have installed a 3.16 stock recovery too yet STILL not being offered the proper OTA (still get the 1.25MB one) plus the phone is still stuck without IMEI or baseband.
EDIT:
This guy you helped here... http://forum.xda-developers.com/showthread.php?t=2204955 was offered the OTA after using the same nandroid as me so what's going on?!
Well give it a go then !!!
Here is the 2.17 stock recovery......trying to recall what i missed/forgot.
http://db.tt/OtcxVXh5
Mr Hofs said:
Well give it a go then !!!
Here is the 2.17 stock recovery......trying to recall what i missed/forgot.
http://db.tt/OtcxVXh5
Click to expand...
Click to collapse
Still no offer of the OTA hmm. It's such a shame we can't change CID or flash any RUU as I'm sure that would help me. I'm just stuck and this phone is useless.
What ota are you talking about anyway ? Restore the 2.17 nandroid and the 2.17 stock recovery and then ota up to JB !
Mr Hofs said:
What ota are you talking about anyway ? Restore the 2.17 nandroid and the 2.17 stock recovery and then ota up to JB !
Click to expand...
Click to collapse
That's exactly my aim but it's not happening.i've restored the correct nandroid (100% certain) unless there is a 3.16 nandroid? Then i've tried with stock recovery 3.16 and 2.17 both times. The only OTA i get offered is the first 1.25MB one and that's it nothing after it. Tried with bootloader locked and unlocked although this shouldn't matter.
Do you need GSM signal to be offered the OTA? As if you do i'll never get offered it as i don't have an IMEI or baseband etc.
I appreciate all the help you are offering Mr Hofs i see you have helped a LOT of people on here.
Just tried the recovery 2.17 that you uploaded as it's a diferent size to the ones i've previously tried but still no luck. No OTA at all.
Is stock recovery supposed to just show a red triangle? It's shows green first then changes to a red triangle ni'm not sure this is right even with bootloader locked.
Does recovery have to match as in 2.17.110?
No this stock 2.17 recovery works on branded phones too, its weird but indeed it could be related to no baseband and imei !
My Hboot is 1.39
and i wanted to know what is the latest Hboot for this CID
as i saw some guys here having the same CID and have Hboot v1.73
So can someone help before i screw up my phone ?
BTW i am currently with ARHD 31.3
Also , My stock backup is gone , so thats an issue and i didn't find a ruu for my phone.
Some hints :
Fastboot getvar version-main
That command gives you the nand number you need. Check in the general section for the nandroid backup collection. And restore the one you need if it's available for download. After restore you need to flash back the stock recovery and update. How to is described there too.
And yes there are updates waiting for you.
Cheers.
Ruu is not available indeed. And if there is no nand available just keep on using a sense 5 rom if you want. All current roms work on your 1.39 hboot.
oRmA2 said:
My Hboot is 1.39
and i wanted to know what is the latest Hboot for this CID
as i saw some guys here having the same CID and have Hboot v1.73
So can someone help before i screw up my phone ?
BTW i am currently with ARHD 31.3
Also , My stock backup is gone , so thats an issue and i didn't find a ruu for my phone.
Click to expand...
Click to collapse
If you wish to update the hboot, all u need to do is do a nandroid restore to 4.0.4 (which is available in this forum)..fastboot flash stock boot.img, and fastboot flash stock recovery.img and lastly relock the bootloader..then update your phone normally via OTA to get the latest rom and hboot..unlock and install custom roms...that's it...
And do NOT loose another stock backup again !
Edit :
Relocking the bootloader is not needed. The 1.29 and the 3.16 are available. The 1.29 is probably of no use because i don't think you find official ota with that anymore. The 3.16 may be of use but therefore we need your main. If your main is lower you cant use it either !
You can find them here
http://forum.xda-developers.com/showthread.php?t=1975140
@amirage where is the 4.0.4 ? I can't see it at this moment.....another thread ?
1.29 = 4.0.3
3.16 = 4.1.1