In an SBF file, CG35 and CG47 contain the system kernel. The Droid X2 lacks CG35, so CG47 probably contains the kernel.
In this thread, it can be seen that the kernel is simply a ramdisk, and the first 2048 bytes are the signature.
It is also fully possible to create custom SBF firmware using the MotoAndroidDepacker software. Sooo...
Extrapolating from this, shouldn't it be possible to create a custom kernel, and move the signature from the old one to the new one? A new kernel and system could be flashed with an SBF, all under Moto's signatures.
I might be missing something here, and I probably am. But still. Has this been tried before? If so, what were the results?
This is just my way of thinking but its hard to believe that Motorola would overlook something that seems that simple with the SBF files THEY provide us. But if its possible and no one has thought of this before, I would LOVE to see someone try. I would if I knew what I was doing. lol
I don't know the details,but I've seen this question posted many a time and it can't be done.
I'm sure someone will come in give you a list of all the problems with making an SBF.
From my understanding the issue is noone has access to the tegra2 kernel/driver source code.
Sent from my MB870 using xda app-developers app
The problem is it would have to be signed and we don't have the key. The second problem would be there's no way to test it. If you screw up the sbf and flash it and it fails the phone would be a brick with no way to bring it back.
Sent from my MB870 using xda app-developers app
Since this isn't a development release, it should be in the General forum.
Thread moved.
Maximinus I said:
The problem is it would have to be signed and we don't have the key. The second problem would be there's no way to test it. If you screw up the sbf and flash it and it fails the phone would be a brick with no way to bring it back.
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
I disagree. If you leave the bootloader flash intact, it should be fine.
Secondly, the first 2048 bytes in the file is the signature. If this was copied over, and the signature on the SBF was copied over (which can be done through the Motorola Android Firmware Depacker, the SBF should be recognized normally.
You can't just transfer the key. If it was that easy nothing would be locked. You have to re-sign the file if you make changes to it. The key I'd imagine probably uses an MD5 to verify the file is legit. once it's changed it will no longer match. It's a good idea but in reality not going to work due to the lock.
Sent from my MB870 using xda app-developers app
Remember, you have to have the original hash key to generate the new key BASED on the newly compiled kernel/bootloader. Without the original source key, if you replace the bootloader with something new in the SBF, it will NOT match and it will brick your phone.
If it were that easy, don't you think we'd already have this available?
The key that Motorola has is the source and once you have that, THEN you can sign the bootloader and it will match. Since we don't have the source key, forget it. It won't work because the newly compiled bootloader/kernel would generate a different hash code than what is in the current SBF files and therefore will fail miserably.
You can't create your own SBFs that will work when flashed on the X2. If it was that easy, we would have had it working a year ago. The last few posts are correct in saying that it needs to be signed by Motorola in order for it to run on the X2.
dragonzkiller said:
You can't create your own SBFs that will work when flashed on the X2. If it was that easy, we would have had it working a year ago. The last few posts are correct in saying that it needs to be signed by Motorola in order for it to run on the X2.
Click to expand...
Click to collapse
The Man has spoken, that is all!
Related
How can I turn this off so I don't get aborted installations in recovery when flashing a zip
Sent from my Eris using XDA App
iloveandroid said:
How can I turn this off so I don't get aborted installations in recovery when flashing a zip
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Are you trying to flash garbage to your phone?
OK, that was harsh; let me put that a different way.
If you get a verification error, there are only two possibilities:
1) The downloaded file was signed with the test-key and is corrupted (or truncated short)
2) The downloaded .zip file was never signed, or signed with some other key other than the "test-key" (and might, or might not also be corrupted)
ClockworkMod will allow you to turn off signature verification; that probably explains why folks end up with bricks from time to time when using Clockwork.
I don't think there are any devs in the XDA Eris forums that produce anything that is not signed (with test-key); so in that case, it is hard to imagine that signature verification is causing you any harm - if you get a verification error, it would be because your .zip file was corrupted somehow.
But - it's your phone to take risks as you see fit. If you want to flash without protection, use ClockworkMod. I would be very diligent about checking MD5 signatures, or running "jarsigner -verify" over the zips you intend to flash
bftb0
bftb0 said:
Are you trying to flash garbage to your phone?
OK, that was harsh; let me put that a different way.
If you get a verification error, there are only two possibilities:
1) The downloaded file was signed with the test-key and is corrupted (or truncated short)
2) The downloaded .zip file was never signed, or signed with some other key other than the "test-key" (and might, or might not also be corrupted)
ClockworkMod will allow you to turn off signature verification; that probably explains why folks end up with bricks from time to time when using Clockwork.
I don't think there are any devs in the XDA Eris forums that produce anything that is not signed (with test-key); so in that case, it is hard to imagine that signature verification is causing you any harm - if you get a verification error, it would be because your .zip file was corrupted somehow.
But - it's your phone to take risks as you see fit. If you want to flash without protection, use ClockworkMod. I would be very diligent about checking MD5 signatures, or running "jarsigner -verify" over the zips you intend to flash
bftb0
Click to expand...
Click to collapse
I wouldn't use Clockwork at all. Just try downloading the file directly on your phone and move it to the root after unzipping and do a md5 to make sure it's right first. It sounds like a corrupted download.
Please ignore all I love android posts.
Hungry Man said:
Please ignore all I love android posts.
Click to expand...
Click to collapse
It took me several tries but I finally parsed your post. I guess it is late. Then I poked around, and I suppose I see what you mean.
We need a special Eris sub-forum with the title "Put Your Posts in Here and They Will be Ignored".
Hang on, wait a minute... that's this forum! lolz
Or, how about a sub-forum entitled "Can I Try This?". The only rule in that forum will be that the correct, and only answer to every question posed will be the single word "Hellyagoforit!"
bftb0
Hey guys
I'm a bit worried, I have gingerblur on the phone now, and apparently OTAing from it can be bad juju
I read the fastboot way of doing it, but just want to make sure I got this right so I dont mess it up
1. DL fastboot
2. download all the images from the link provided on the thread
**here is where I need to make sure I got this right***
3. I have to put all the images in the same folder as the fastboot.exe I guess
4. use the commands given on the link
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
5. I wipe the data and reboot
moto-fastboot -w
moto-fastboot reboot
6. should be gtg
now my questions are
is it going to be rooted when I do this, or will I have to reroot the phone (is it posisble to root the 2.3.4?)
and can I do this coming from gingerblur? I don't wanna mess anything up
and lastly, what about all the other img files? webtop, radio etc...
thanks!
ps. sorry I'm in a rush, supposed to goto dinner and then see captain america, so I figured I put this up real quick b4 i leave, gf is waiting at the door! lol
razorseal said:
Hey guys
I'm a bit worried, I have gingerblur on the phone now, and apparently OTAing from it can be bad juju
I read the fastboot way of doing it, but just want to make sure I got this right so I dont mess it up
1. DL fastboot
2. download all the images from the link provided on the thread
**here is where I need to make sure I got this right***
3. I have to put all the images in the same folder as the fastboot.exe I guess
4. use the commands given on the link
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
5. I wipe the data and reboot
moto-fastboot -w
moto-fastboot reboot
6. should be gtg
now my questions are
is it going to be rooted when I do this, or will I have to reroot the phone (is it posisble to root the 2.3.4?)
and can I do this coming from gingerblur? I don't wanna mess anything up
and lastly, what about all the other img files? webtop, radio etc...
thanks!
ps. sorry I'm in a rush, supposed to goto dinner and then see captain america, so I figured I put this up real quick b4 i leave, gf is waiting at the door! lol
Click to expand...
Click to collapse
Don't make things so complicating, just flash this if you're on 1.8.3.
http://forum.xda-developers.com/showthread.php?t=1182526
Are you unlocked??
Sent from my MB860 using XDA App
Paschalis said:
Are you unlocked??
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
As long as he's on 1.8.3. that shouldn't matter.
Yes, but if he's locked, I think he won't be able too use fastboot..
Edit: if the images he want to flash using fastboot, are for unlocked device, he will end bricked.
Sent from my MB860 using XDA App
Paschalis said:
Yes, but if he's locked, I think he won't be able too use fastboot..
Edit: if the images he want to flash using fastboot, are for unlocked device, he will end bricked.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Refer to the link I sent him...
Unlocked as in rooted?
I'm running gingerblur, so yes, I'm rooted so i have access to cwm...
Can I just flash that? And yes I'm on 1.8.3
Flashing via sbf?
Sent from my MB860 using XDA App
mpalatsi said:
Don't make things so complicating, just flash this if you're on 1.8.3.
http://forum.xda-developers.com/showthread.php?t=1182526
Click to expand...
Click to collapse
So what are allll these posts about phones hard bricking? Why isn't everyone just doing this?
I realized unlocked as in bootloader unlocked... That part I'm not sure, I did the OTA 1.8.3 update, so I assume not...
I doubt I'll be downgrading though, so is it safe to just use that link? I'd hate to hard brick
Sent from my MB860 using XDA App
razorseal said:
So what are allll these posts about phones hard bricking? Why isn't everyone just doing this?
I realized unlocked as in bootloader unlocked... That part I'm not sure, I did the OTA 1.8.3 update, so I assume not...
I doubt I'll be downgrading though, so is it safe to just use that link? I'd hate to hard brick
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
@razorseal,
You will not hard-brick if you use the link posted by @mpalatsi.
It appears to be the official SBF version of the OTA. Edit: actually, that one is modified with the unlocked bootloader.
However, you will not be able to go back to any other SBF after you flash this thing. It modifies the bootloader in a way that will cause damage if you try to revert. This is ok if you have no plans to revert, but one never knows when they need to take a step back.
So, you can commit to this SBF or you can do the sensible thing: unlock your bootloader (if you haven't already done so) and follow with your procedure (or use the Fruit Cakes which are equivalent to the fastboot flashing, but using the recovery).
I would recommend staying away from SBF's in general, especially from the ones that cause irreversible changes to the bootloader.
Edit: If you need help unlocking your bootloader, look up the Pudding thread in the Dev section. Everything is straightforward and has been done by many users successfully.
Edit2: If it makes you feel any better, I personally used the method you described in the OP to upgrade. Wasn't that hard or "complicated".
feisty_noodle said:
@razorseal,
You will not hard-brick if you use the link posted by @mpalatsi.
It appears to be the official SBF version of the OTA.
However, you will not be able to go back to any other SBF after you flash this thing. It modifies the bootloader in a way that will cause damage if you try to revert. This is ok if you have no plans to revert, but one never knows when they need to take a step back.
So, you can commit to this SBF or you can do the sensible thing: unlock your bootloader (if you haven't already done so) and follow with your procedure (or use the Fruit Cakes which are equivalent to the fastboot flashing, but using the recovery).
I would recommend staying away from SBF's in general, especially from the ones that cause irreversible changes to the bootloader.
Edit: If you need help unlocking your bootloader, look up the Pudding thread in the Dev section. Everything is straightforward and has been done by many users successfully.
Click to expand...
Click to collapse
ok, got it...
I understand no downgrading, but how about upgrading in the future?
so if I want to do it the 'safe' way, how do I do that? the way I mentioned it? (the thread via fastboot)
How can I check if i'm unlocked my bootloader or not?
I'm in the same boat. I'm on ginger blur and 1.83 and I just want to update, unlock and root.I would like to revert back if need be.
Sent from my MB860 using XDA App
razorseal said:
ok, got it...
I understand no downgrading, but how about upgrading in the future?
so if I want to do it the 'safe' way, how do I do that? the way I mentioned it? (the thread via fastboot)
How can I check if i'm unlocked my bootloader or not?
Click to expand...
Click to collapse
This link was exactly what I used.
As far as upgrading in the future, you can use the resources found here, on XDA. People will be dissecting new updates to remove the nasty bits (bootloaders and such).
If you decide that you want to play with custom ROMs, you can do that, too.
You will NOT be able to use OTA's unless you backtrack to a fully stock ROM via official OTA's or SBF's. This can be done, but will require some careful work on your part.
For the bootloader unlocking--go read the Pudding thread here. It is very a straightforward procedure.
Edit: if your first Motorola boot screen has the word "Unlocked" in the upper left corner, then you are unlocked. If not, then ...
Don't you remember if you unlocked your bootloader?
There is a method to check that I think in the pudding thread.
With unlocked bootloader, when moto makes an OTA, the devs here take it, mod it, made it a flashable zip, and you can upgrade your phone.
For downgrading.
Personally I m on gingerblur 4.5. With unlocked bootloader, and tenfars port of cwm recovery installed.
I currently have CWM nandroid backup.
I can install the 2.3.4 cherryblur e.g( with cwm installation also), and whenever I want I can restore this backup..
I can also have 2 backups of 2.2 and 2.3 and switch between the 2 backups.
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Sent from my MB860 using XDA App
Paschalis said:
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Click to expand...
Click to collapse
well then I should stay from that link that was provided here considering it's an sbf file...
Paschalis said:
Don't you remember if you unlocked your bootloader?
There is a method to check that I think in the pudding thread.
With unlocked bootloader, when moto makes an OTA, the devs here take it, mod it, made it a flashable zip, and you can upgrade your phone.
For downgrading.
Personally I m on gingerblur 4.5. With unlocked bootloader, and tenfars port of cwm recovery installed.
I currently have CWM nandroid backup.
I can install the 2.3.4 cherryblur e.g( with cwm installation also), and whenever I want I can restore this backup..
I can also have 2 backups of 2.2 and 2.3 and switch between the 2 backups.
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I agree with almost everything.
The 'almost' part is that using stock system.img can be a good idea. Whenever new firmware updates come out, I am always curious to see what the OEM envisioned to be the 'normal' look for their device.
Flashing these is perfectly safe because you are only touching the system partition. As long as you have functional fastboot (unlocked bootloader) or recovery, you will have two fallback positions in case something goes wrong (like a bad flash).
Trusting OEM's to give you a good product has historically been a losing proposition. They always take waaay too long. And they make stupid mistakes (like the ****ed up battery monitor in the new Gingerbread ROM, the 4.5.91). And to fix those mistakes they take their sweet time again.
Anyway, @razorseal:
After you upgrade, you will likely see poor battery performance. The way to fix this is to flash the new radio 01.77.30P found here; this will be done through recovery. I am not sure if Ken's thread here is the same thing. The image files look different.
Also, to fix the aforementioned screw-up by Motorola, follow the instructions here.
feisty_noodle said:
I agree with almost everything.
The 'almost' part is that using stock system.img can be a good idea. Whenever new firmware updates come out, I am always curious to see what the OEM envisioned to be the 'normal' look for their device.
Flashing these is perfectly safe because you are only touching the system partition. As long as you have functional fastboot (unlocked bootloader) or recovery, you will have two fallback positions in case something goes wrong (like a bad flash).
Trusting OEM's to give you a good product has historically been a losing proposition. They always take waaay too long. And they make stupid mistakes (like the ****ed up battery monitor in the new Gingerbread ROM, the 4.5.91). And to fix those mistakes they take their sweet time again.
Anyway, @razorseal:
After you upgrade, you will likely see poor battery performance. The way to fix this is to flash the new radio 01.77.30P found here; this will be done through recovery. I am not sure if Ken's thread here is the same thing. The image files look different.
Also, to fix the aforementioned screw-up by Motorola, follow the instructions here.
Click to expand...
Click to collapse
Thanks bud
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I looked at that, and that says it will unlock it... isn't the link provided here already unlocked?
razorseal said:
Thanks bud
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I looked at that, and that says it will unlock it... isn't the link provided here already unlocked?
Click to expand...
Click to collapse
Yes, zomgunlock-lite.sbf is the contents of "pudding".
That is your bootloader that has the unlock code. Just follow Ken's instructions from the page you linked to.
Also, here is the link for an easy root method after you are done.
If you are still scared, watch the videos of the process here. I didn't have time to look too carefully, but it clearly shows what the bootloader screen should look like when you've successfully unlocked.
Good luck, I have to sleep now.
ah ****... not working
I have something that says 'failed to boot 4'
starting RSD mode
uh oh
razorseal said:
ah ****... not working
I have something that says 'failed to boot 4'
starting RSD mode
uh oh
Click to expand...
Click to collapse
You are not in a bricking situation! Take a deep breath.
I have not seen this, but others have ...
http://forum.xda-developers.com/showthread.php?t=1062727
Do some homework.
I am really going now.
I just reflashed.... I guess something got corrupted it works now
alright, off to unlocking, and doing the radio tweak along with battery % and att logo removal
Hello,
me and my friend thought of something..
he unlocked his bootloader, and sent me his binary file
he said that once he sent his hex code, he instantly got the email for the binary code, so we think that because its so fast you might receive a general binary file to flash.
is it possible to use his binary file to unlock my bootloader??\
that way i wont have to agree wiht htc on voiding my warranty?
if so how would i flash it??
Bigv69er said:
Hello,
me and my friend thought of something..
he unlocked his bootloader, and sent me his binary file
he said that once he sent his hex code, he instantly got the email for the binary code, so we think that because its so fast you might receive a general binary file to flash.
is it possible to use his binary file to unlock my bootloader??\
that way i wont have to agree wiht htc on voiding my warranty?
if so how would i flash it??
Click to expand...
Click to collapse
Well we can do an md5sum check of the binary files to see if they are all identical but I seriously doubt that they are. I am pretty sure they use that they use the identifier token to process and produce the unlock.bin file.
Binary100100 said:
Well we can do an md5sum check of the binary files to see if they are all identical but I seriously doubt that they are. I am pretty sure they use that they use the identifier token to process and produce the unlock.bin file.
Click to expand...
Click to collapse
i think the identifier is only a way for them to better track what phone you are unlocking?
but yeah someone should check them..
should i upload his??
Bigv69er said:
i think the identifier is only a way for them to better track what phone you are unlocking?
but yeah someone should check them..
should i upload his??
Click to expand...
Click to collapse
If you want. I'm curious to see what will happen. My guess is that it'll return an error of some kind.
I've been working on trying to decompile or decode the .bin file to see if there is something to edit to give us S-OFF instead of Unlock.
Unfortunately I've been on duty for the last four days doing 12 hour shifts and when I get home I still have about three hours of reports to type up.
I'm just lucky I don't have any pending cases going to trial anytime soon so I can look into it a little more the next couple days.
When you upload the file you will probably have to zip it because I don't think you can upload .bin files on the forums.
Binary100100 said:
If you want. I'm curious to see what will happen. My guess is that it'll return an error of some kind.
I've been working on trying to decompile or decode the .bin file to see if there is something to edit to give us S-OFF instead of Unlock.
Unfortunately I've been on duty for the last four days doing 12 hour shifts and when I get home I still have about three hours of reports to type up.
I'm just lucky I don't have any pending cases going to trial anytime soon so I can look into it a little more the next couple days.
When you upload the file you will probably have to zip it because I don't think you can upload .bin files on the forums.
Click to expand...
Click to collapse
ok here it is..
check it out.. let me know
yeah thats what i was going to tell you, if someone could rewrite it or change the way it unlocks it, to give us S-off right now i would think that would be the most logical way, since they are giving us a partial unlock, maybe someone can make it into a full unlock
Bigv69er said:
ok here it is..
check it out.. let me know
yeah thats what i was going to tell you, if someone could rewrite it or change the way it unlocks it, to give us S-off right now i would think that would be the most logical way, since they are giving us a partial unlock, maybe someone can make it into a full unlock
Click to expand...
Click to collapse
Someone out there do a md5 check please?
I'm at work and shouldn't install extra stuff since I share this computer with another employee. I would like to know if they are the same.
Ok did md5 checksums they are diffrent so it will probably saw invaild unlock_code.bin if you flash but give it a try i think
His: 067e76020977d8a8f603c16d3bbf2f86
Mine: 94771323b128fd3d1689bce177f8c2f3
xboarder56 said:
Ok did md5 checksums they are diffrent so it will probably saw invaild unlock_code.bin if you flash but give it a try i think
His: 067e76020977d8a8f603c16d3bbf2f86
Mine: 94771323b128fd3d1689bce177f8c2f3
Click to expand...
Click to collapse
So just add I thought, HTC does use the token that we submit.
Sent from my HTC Amaze 4G using xda premium
xboarder56 said:
Ok did md5 checksums they are diffrent so it will probably saw invaild unlock_code.bin if you flash but give it a try i think
His: 067e76020977d8a8f603c16d3bbf2f86
Mine: 94771323b128fd3d1689bce177f8c2f3
Click to expand...
Click to collapse
Thanks X..
Aww. So should i try it?? Would it be safe?
Sent from my HTC_Amaze_4G_WHITE using xda premium
Bigv69er said:
Thanks X..
Aww. So should i try it?? Would it be safe?
Sent from my HTC_Amaze_4G_WHITE using xda premium
Click to expand...
Click to collapse
I wouldn't bother, when in doubt--there is no doubt.
^^^That has kept my phones safe for years.
TheSneakerWhore said:
I wouldn't bother, when in doubt--there is no doubt.
^^^That has kept my phones safe for years.
Click to expand...
Click to collapse
Lol yea
Sent from my HTC_Amaze_4G_WHITE using xda premium
Title just has it...
What are fastboot files for? everyone keep saying it's a good thing and etc... but I don't really know what's the biga deal
It's the phone os in a file.
Different from the old .sbf, in that it doesn't destroy user settings, accounts, sms etc.
Shadowdancer123 said:
It's the phone os in a file.
Different from the old .sbf, in that it doesn't destroy user settings, accounts, sms etc.
Click to expand...
Click to collapse
To add to that it is for recovering from a soft brick. So it is kind of a big deal. It may also helps devs not be so gun shy.
inheme said:
Title just has it...
What are fastboot files for? everyone keep saying it's a good thing and etc... but I don't really know what's the biga deal
Click to expand...
Click to collapse
If u install a costum rom, fastboot files let you back to moto stock rom
Sent from my XT910 using Tapatalk
Thanks guys!
So is there any fastboot for the GSM version yet? If not, is there any way to extract it?
cheekrox said:
So is there any fastboot for the GSM version yet? If not, is there any way to extract it?
Click to expand...
Click to collapse
Spend about 2minutes and look at developer threads, you can find them
Sent from my RAZR using Tapatalk
Bit confused here; the boot loader is locked so you can't change the kernel (os). Is the fastboot stuff everything but the kernel; just the jvm; not the jvm but the basic files that are executed by the jvm; the ...???
jake21 said:
Bit confused here; the boot loader is locked so you can't change the kernel (os). Is the fastboot stuff everything but the kernel; just the jvm; not the jvm but the basic files that are executed by the jvm; the ...???
Click to expand...
Click to collapse
The kernel can be flashed by these files, since it's encrypted with the correct password.
We'd need that password to bypass the hardlock, but unfortunately noone will ever want to experiment with that since it may blow e-fuses, rendering his or her phone forever dead.
By the little I know of cryptography, the fastboot only has half the key.
Previously no phone actually used an e-fuse (it was proven on earlier moto phones that e-fuse was not enabled). Does the razr actually use an e-fuse ?
Shadowdancer123 said:
The kernel can be flashed by these files, since it's encrypted with the correct password.
We'd need that password to bypass the hardlock, but unfortunately noone will ever want to experiment with that since it may blow e-fuses, rendering his or her phone forever dead.
By the little I know of cryptography, the fastboot only has half the key.
Click to expand...
Click to collapse
Hey, everyone. I know this is probably the last thing you want to read, but I could really use some prompt help.
I tried the method posted in: http://forum.xda-developers.com/showthread.php?t=1686551
I got to step 3, but it didn't let me choose recovery. It just started installing the update. However, when it rebooted, it never got past the white HTC boot screen. I pulled the battery, pulled the MicroSD card, went back into the bootloader and tried running Factory Reset. Same result - stuck at white HTC boot screen.
Some more information:
1. Device is completely stock - no customer bootloader, stock Gingerbread OS. (2.3.4. That's why I wanted to try this in the first place. According to HTC, my IMEI number block hasn't been updated for ICS, yet.)
2. I renamed the file "update" as per the thread.
I'm hoping that the devs and contributors here will have mercy on a lowly noob who's having problems. I'm hoping to either return to stock and wait for the ICS update, or get to the point where I can install a custom ROM found here. (I was thinking SpeedROM). But, as my device has Gingerbread (or, potentially nothing at this point), I'm not sure where to go from here.
Thanks so much for any suggestions. You guys are the best, and I love this site.
Not sure if you've tried this yet, just name your file as PH85IMG.zip and place it on your microSD. Boot into bootloader and let it run the update. If this is what you did, then I have no clue what happened.
Just out of curiosity, why didn't you get the official OTA the official way if you're completely stock?
PS - This question belongs in the Q&A subforum. Remember that next time if you don't want to get flamed =)
kered424 said:
Not sure if you've tried this yet, just name your file as PH85IMG.zip and place it on your microSD. Boot into bootloader and let it run the update. If this is what you did, then I have no clue what happened.
Just out of curiosity, why didn't you get the official OTA the official way if you're completely stock?
PS - This question belongs in the Q&A subforum. Remember that next time if you don't want to get flamed =)
Click to expand...
Click to collapse
Thanks! I'm trying that now.
And, I appreciate the advanced notice. Is there a way I can transition the thread, so as to avoid further confrontation?
takingflight005 said:
Thanks! I'm trying that now.
And, I appreciate the advanced notice. Is there a way I can transition the thread, so as to avoid further confrontation?
Click to expand...
Click to collapse
It happens. No worries, the Mods will move it for you.
kered424 said:
Not sure if you've tried this yet, just name your file as PH85IMG.zip and place it on your microSD. Boot into bootloader and let it run the update. If this is what you did, then I have no clue what happened.
Just out of curiosity, why didn't you get the official OTA the official way if you're completely stock?
PS - This question belongs in the Q&A subforum. Remember that next time if you don't want to get flamed =)
Click to expand...
Click to collapse
The official update just never showed up. I literally lost count of the number of times I went into Settings > About phone > HTC software updates > Check now.
I've been on probably 4 chats and 4-5 calls between T-Mobile customer service and HTC tech support. The general consensus is that my phone's IMEI number is in a block that hasn't been authorized for the ICS update, yet. But, I really wanted to upgrade, and I think it's ridiculous that it's been 2 months since the update and my phone can't.
Ok, so I'm first going to apologize, since I've heard that double-posting is very much not accepted by forum communities.
I've tried several times to fix this. I renamed the file as was suggested, and went back into the bootloader. It (apparently) scans the MicroSD card for files, and says "Loading...[PH85IMG.zip]" (It attempts to load PH85DIAG.zip, says no image, and PH85IMG.nbh, and again says no image)
After this, it says "Checking..[PH85IMG.zip]" (That is the only thing it says)
Then, I get the options:
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
If I go into FASTBOOT, it doesn't really help - just reboots either the bootloader (repeating this process, obviously) or the phone, which goes back to the white HTC boot screen it's hanging on.
If I go into RECOVERY, there's not option to install the .zip like the other page suggests, but if I try "Install update from SD card" it gives me "Illegal operation" and reboots.
If I go to FACTORY RESET, it acts like it's reinstalling, but leads to the same problem.
I'm thinking that I just nuked the phone's internal storage, and completely deleted the original OS. Any ideas on how to resolve that?
Or, if that's not the problem, where should I go from here?
It's funny....I troubleshoot computers for a living....but I'm lost right now on this phone.
Thank you for the continued help, gents! I'd really like to not have to throw away a $350, brand new phone....
I would guess you have one of the 3
the wrong carrier's ruu
A bad download of ruu
Renamed wrong (maybe you added ".zip" when it already had the ext but is just hidden by windows 7)
Sent from my SGH-T999 using xda premium
glacierguy said:
I would guess you have one of the 3
the wrong carrier's ruu
A bad download of ruu
Renamed wrong (maybe you added ".zip" when it already had the ext but is just hidden by windows 7)
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hm....well, it's not the third. I doubt the first, unless the wrong file was linked in the thread I mentioned. I'll try downloading the file again.
So, if this still doesn't work for me, let's attack this from a different angle. Are there any other options? Could I change the bootloader, install the leaked ICS ROM, then install another one after that? Like I said, I had been considering trying out Project Butter Speed ROM. I know that the instructions for all that are in the Amaze Bible thread, but there's such a large volume of data there, it's hard to sift through.
Edit: Re-downloaded the file; no change. Any more suggestions?
I've been away a while, but if my memory serves me correct, to install it using ph85img, you must first relock your bootloader. are you locked or unlocked right now?
aj_2423 said:
I've been away a while, but if my memory serves me correct, to install it using ph85img, you must first relock your bootloader. are you locked or unlocked right now?
Click to expand...
Click to collapse
I never unlocked or modified the bootloader in any way. That's why I thought this would work. My impression was that basically everything had to be stock.
takingflight005 said:
I never unlocked or modified the bootloader in any way. That's why I thought this would work. My impression was that basically everything had to be stock.
Click to expand...
Click to collapse
I think you need to reconsider the name of your file. If it shows up as PH85IMG.zip, more likely than not, it is actually named PH85IMG.zip.zip
This is due to how Windows reads files. If the file is of a known file type, it will not show up the extension (even though it IS there).
Try renaming it to PH85IMG and then put it in the root directory of the SD card and then boot into bootloader. It *should* read it.
Keylogger_0 said:
I think you need to reconsider the name of your file. If it shows up as PH85IMG.zip, more likely than not, it is actually named PH85IMG.zip.zip
This is due to how Windows reads files. If the file is of a known file type, it will not show up the extension (even though it IS there).
Try renaming it to PH85IMG and then put it in the root directory of the SD card and then boot into bootloader. It *should* read it.
Click to expand...
Click to collapse
I'm a computer support tech. Trust me, I did not add an extra file extension, lol. Windows does indeed recognize it as a zip file, so I know the extension is properly set. Name is just set to "PH85IMG"
Not trying to sound like a jerk; just making sure people know where I'm coming from.
takingflight005 said:
I'm a computer support tech. Trust me, I did not add an extra file extension, lol. Windows does indeed recognize it as a zip file, so I know the extension is properly set. Name is just set to "PH85IMG"
Not trying to sound like a jerk; just making sure people know where I'm coming from.
Click to expand...
Click to collapse
I understand that, but if you read through the Q&A section, you'll know why I imperatively make that statement. Can you link me to which file you're trying to flash? I'm thinking it might be a wrong file you're trying to flash.
When you flash or update via a stock ruu, it may seem stuck but it isn't, first boot always takes time, read through this thread properly when I get home, the guys seems to be here, so I'm not needed anyways.
Sent from a Galaxy flowing with Jelly Beans.
Keylogger_0 said:
I understand that, but if you read through the Q&A section, you'll know why I imperatively make that statement. Can you link me to which file you're trying to flash? I'm thinking it might be a wrong file you're trying to flash.
Click to expand...
Click to collapse
http://www.4shared.com/zip/V4cIZsvx/OTA_RUBY_ICS_35_S_TMOUS_214531.html
takingflight005 said:
http://www.4shared.com/zip/V4cIZsvx/OTA_RUBY_ICS_35_S_TMOUS_214531.html
Click to expand...
Click to collapse
Try this one. It's the latest one out there. Link is here
Don't forget to give thanks to krook6023 for providing this.
His original thread is here http://forum.xda-developers.com/showthread.php?t=1617644
Anyways, download that one, then rename it to PH85IMG, put it in the microSD card and then boot into bootloader. It should work. Let us know if it does not.
That one worked! The original file I was trying never propmpted me to update. This one went off without a hitch.
Again, my great thanks to everyone in the thread!
Sent from my HTC_Amaze_4G using xda app-developers app
takingflight005 said:
That one worked! The original file I was trying never propmpted me to update. This one went off without a hitch.
Again, my great thanks to everyone in the thread!
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Glad you're up and going. FileFactory has such ****ty download speeds that its possible something became corrupt in the 4 hours or so that it took to download the original. I had a similar issue. Enjoy your ICS man!!!
Sent from my SGH-T999 using xda premium
glacierguy said:
Glad you're up and going. FileFactory has such ****ty download speeds that its possible something became corrupt in the 4 hours or so that it took to download the original. I had a similar issue. Enjoy your ICS man!!!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks! I am really enjoying the new features. Many things that, after I use them, I think "That should have been the way right from the beginning."
The one thing I would like is the stock ICS notification bar....but then, that's why I rooted, isn't it?
takingflight005 said:
The one thing I would like is the stock ICS notification bar....but then, that's why I rooted, isn't it?
Click to expand...
Click to collapse
There's a mod for that
Check themes and apps section
Sent from my SGH-T999 using xda premium