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
Related
The AlphaRev team has successfully unlocked NAND on several devices in just the last few days using the same technique. Some of the devices are very similar spec-wise to the Espresso and some of the devices are the same devices that Dumfuq's kernels work for universally with our phone. Has anyone played with this for the Espresso yet? (Devs). I wouldn't play with it unless you are sure what you are doing due to the page having a disclaimer about it being possible to brick your device.
http://alpharev.shadowchild.nl/
http://forum.xda-developers.com/showthread.php?t=794314
nikol4s said:
The AlphaRev team has successfully unlocked NAND on several devices in just the last few days using the same technique. Some of the devices are very similar spec-wise to the Espresso and some of the devices are the same devices that Dumfuq's kernels work for universally with our phone. Has anyone played with this for the Espresso yet? (Devs). I wouldn't play with it unless you are sure what you are doing due to the page having a disclaimer about it being possible to brick your device.
http://alpharev.shadowchild.nl/
http://forum.xda-developers.com/showthread.php?t=794314
Click to expand...
Click to collapse
Initial testing shows that it's very likely it will work.
Now I need to put some stuff together for a full manual test.
ieftm said:
Initial testing shows that it's very likely it will work.
Now I need to put some stuff together for a full manual test.
Click to expand...
Click to collapse
Get in touch with ChiefzReloaded, he's working on it as well.
I smell unlocked NAND incoming soon.
Hmmm i smell s-off sooner then later..
at 935 pm est on chiefsreloaded twitter page he states he has clockwork reinstalled with no need for the update.zip bs. =>
Damn i am syked !!
I am working with AlphaRev to help port this over to Espresso. As IEF said, initial testing shows promise. We'll keep you in the loop when we know more.
I hope this works. Finally some great progress,
Sent from my T-Mobile myTouch 3G Slide using XDA App
Good job guys this is amazing! Thank you
Thanks for your help everyone. I don't need anymore model ID's! See my photo of S-OFF in this thread!
[FONT="]
[/FONT]
[FONT="]If I can all ask you a favor - I need a lot of sample data in order to help IEF automate the process in AlphaRev, specifically your model ID numbers for your Slides. This is not phone-specific like the serial number, but I want to make sure different revisions of our phone aren't out there or that they didn't give them different model IDs depending on manufacturing conditions.
Here's how to help:[/FONT]
[FONT="]Run: adb pull /proc/cmdline.[/FONT]
[FONT="]Open (using Notepad, etc) the 'cmdline' file that you just downloaded using adb pull /proc/cmdline (it defaults downloading to the directory where you ran adb from).[/FONT]
[FONT="]I need the letters and numbers after the equals sign of "androidboot.mid=".[/FONT]
[FONT="]Post those letters and numbers here, in a reply to this thread (please do not quote this post).[/FONT]
[FONT="]Please do NOT reply with your androidboot.cid or androidboot.serialno![/FONT][FONT="]
Please understand that this post does not imply that we have S-OFF yet. I will let you know if/when that happens.
Thanks everyone![/FONT]
Deleted. As totally off topic.
Here You Go Man....
androidboot.mid=PB6510000
Deleted...
I've got the same:
androidboot.mid=PB6510000
MrThePlague said:
I've got the same:
androidboot.mid=PB6510000
Click to expand...
Click to collapse
Same here to
androidboot.mid=PB6510000
androidboot.mid=PB6510000
nbetcher said:
If I can all ask you a favor - I need a lot of sample data in order to help IEF automate the process in AlphaRev, specifically your model ID numbers for your Slides. This is not phone-specific like the serial number, but I want to make sure different revisions of our phone aren't out there or that they didn't give them different model IDs depending on manufacturing conditions.
Here's how to help:
Run: adb pull /proc/cmdline.
Open (using Notepad, etc) the 'cmdline' file that you just downloaded using adb pull /proc/cmdline (it defaults downloading to the directory where you ran adb from).
I need the letters and numbers after the equals sign of "androidboot.mid=".
Post those letters and numbers here, in a reply to this thread (please do not quote this post).
Please do NOT reply with your androidboot.cid or androidboot.serialno!
Please understand that this post does not imply that we have S-OFF yet. I will let you know if/when that happens.
Thanks everyone!
Click to expand...
Click to collapse
Not to sound stupid i read the.. link but wtf is.. S-OFF and what does this do exactly? can someone dumb it down for me
Virus1x said:
Not to sound stupid i read the.. link but wtf is.. S-OFF and what does this do exactly? can someone dumb it down for me
Click to expand...
Click to collapse
S-off makes your phone fully rooted. The S stands for security which locks your NAND, HBOOT, system, and recovery. Right now we our phones are soft modded so we have to get into recovery from the update.zip. With S-off all we have to do is flash the recovery once then it boots up without the update.zip. You can read about it more at this link http://alpharev.shadowchild.nl/
Sent from my T-Mobile myTouch 3G Slide
lstevens86 said:
S-off makes your phone fully rooted. The S stands for security which locks your NAND, HBOOT, system, and recovery. Right now we our phones are soft modded so we have to get into recovery from the update.zip. With S-off all we have to do is flash the recovery once then it boots up without the update.zip. You can read about it more at this link http://alpharev.shadowchild.nl/
Sent from my T-Mobile myTouch 3G Slide
Click to expand...
Click to collapse
Anyone pull this off yet
Sent from my T-Mobile myTouch 3G Slide using XDA App
Virus1x said:
Anyone pull this off yet
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
There are people working on it
Sent from my T-Mobile myTouch 3G Slide
same as well
.mid=PB6510000
I am taking no credit in the release of the OTA files these were from lightningdude and credit goes to him for his efforts to bring these files out. Files size is around 43mb, but I am guessing that it is compressed and when it flashes it uncompresses to 63mb.
Link to original post from lightningdude,
http://forum.xda-developers.com/showthread.php?t=1621431&page=35
DB link from lightningdude
http://dl.dropbox.com/u/21955004/fota.zip
What we know so far it looks like flashing the OTA removes all possibility for root and early signs suggest that the methods for unlocking our bootloaders has been patched. So anyone who OTA's is not able to root and or unlock your BL.
I dont know much about developement of these files and am merely bringing them out to the masses in hopes of some good stuff to come from it, and again dont thank me, thank lightningdude.
DON'T THANK ME, Hit THANKS for lightningdude
Dang, j-greg, I didn't think it needed such bold font.
On-point: Is there any way to actually open this thing? I mean, there's got to be, if our phones update from it, right? There must be a way!
lightningdude said:
Dang, j-greg, I didn't think it needed such bold font.
On-point: Is there any way to actually open this thing? I mean, there's got to be, if our phones update from it, right? There must be a way!
Click to expand...
Click to collapse
I am messing with the files now trying to see if it can uncompressed if it is. And the font is so big because someone already thanked me for the post, and I dont think its right I get the thanks as you were the one who brought them out... I'm just a messenger. So big font to get peoples attention to thank you not me
I think these are compressed with some sort of compression method, maybe proprietary.
I'm guessing this patches the bootloader.
If so, time we overthrow Verizon. With a lawsuit.
KeiranFTW said:
I think these are compressed with some sort of compression method, maybe proprietary.
I'm guessing this patches the bootloader.
If so, time we overthrow Verizon. With a lawsuit.
Click to expand...
Click to collapse
My Mom was just saying today how she wants to sue Verizon in a class action for raising fees and what not. Maybe we should all get together and start that badn wagon. Haha.
KeiranFTW said:
I think these are compressed with some sort of compression method, maybe proprietary.
I'm guessing this patches the bootloader.
If so, time we overthrow Verizon. With a lawsuit.
Click to expand...
Click to collapse
I dislike VZjust as much as the next guy, but VZ feels that if you are a subsidized phone with a plan then the phone is not yours until the contract is up. For me i bought my phone off ebay to replace the total crap that is Motorola Droid 2 Global (loved the keyboard, hated the Motorblur and locked BL)
But I agree, VZ is raping everyone who has a wirelss plan with them, but no news here all Carriers do that.
My phone was free so they have no right to say what we can and can't do with our phones
Sent from my R800x using XDA
droidjunkie said:
My phone was free so they have no right to say what we can and can't do with our phones
Sent from my R800x using XDA
Click to expand...
Click to collapse
Free with a 2 year contract or free from someone you knew? If its free from a contract of 2 years to them they own the device for the length of the contract. I am not trying to support VZ, just saying that I have seen attempts (not firsthand) of people trying to sue VZ or other carriers for the same thing and they are always squashed
jgregoryj1 said:
I am taking no credit in the release of the OTA files these were from lightningdude and credit goes to him for his efforts to bring these files out. Files size is around 43mb, but I am guessing that it is compressed and when it flashes it uncompresses to 63mb.
Link to original post from lightningdude,
http://forum.xda-developers.com/showthread.php?t=1621431&page=35
DB link from lightningdude
http://dl.dropbox.com/u/21955004/fota.zip
What we know so far it looks like flashing the OTA removes all possibility for root and early signs suggest that the methods for unlocking our bootloaders has been patched. So anyone who OTA's is not able to root and or unlock your BL.
I dont know much about developement of these files and am merely bringing them out to the masses in hopes of some good stuff to come from it, and again dont thank me, thank lightningdude.
DON'T THANK ME, Hit THANKS for lightningdude
Click to expand...
Click to collapse
Hey, maybe it's because my BL was unlocked with the testpoint method, but I still have full root. I returned to stock with the .88 ftf file and then rooted it. I ran tha OTA Rootkeeper also. Once the FOTA was finished, I checked and I still have root without even touching the OTA Rootkeeper program. I ran Root Checker, and it verified I have full root access as well.
netizenmt said:
Hey, maybe it's because my BL was unlocked with the testpoint method, but I still have full root. I returned to stock with the .88 ftf file and then rooted it. I ran tha OTA Rootkeeper also. Once the FOTA was finished, I checked and I still have root without even touching the OTA Rootkeeper program. I ran Root Checker, and it verified I have full root access as well.
Click to expand...
Click to collapse
Can you PM me a Nandroid backup of this?
Did a baseband update come with this?
Leraeniesh said:
Can you PM me a Nandroid backup of this?
Click to expand...
Click to collapse
oohh, that would be awesome...... net.... got lucky. But in a good way.
netizenmt said:
Hey, maybe it's because my BL was unlocked with the testpoint method, but I still have full root. I returned to stock with the .88 ftf file and then rooted it. I ran tha OTA Rootkeeper also. Once the FOTA was finished, I checked and I still have root without even touching the OTA Rootkeeper program. I ran Root Checker, and it verified I have full root access as well.
Click to expand...
Click to collapse
I'm also rooted on 2.3.4 but with locked bootloader. Same method of flashing as you minus the ota rootkeeper.
Sent from my R800x using xda premium
kelvenha55 said:
I'm also rooted on 2.3.4 but with locked bootloader. Same method of flashing as you minus the ota rootkeeper.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
Any chance you can make a nandroid backup? And if so post a download link for it here so Devs can browse its files?
You can try and fastboot recoveryplay.img and do a nandroid, dont need an unlocked BL for that.....
jgregoryj1 said:
Any chance you can make a nandroid backup? And if so post a download link for it here so Devs can browse its files?
You can try and fastboot recoveryplay.img and do a nandroid, dont need an unlocked BL for that.....
Click to expand...
Click to collapse
Seriouslly?!?
I thought you needed to be unlocked to hotboot recovery.
Leraeniesh said:
Seriouslly?!?
I thought you needed to be unlocked to hotboot recovery.
Click to expand...
Click to collapse
I might be wrong, been on an unlocked BL since last Aug so maybe my memory is boinked but I thought anyone can do a recoveryplay.img boot and do a nandroid that way? If I am wrong someone please correct me
jgregoryj1 said:
I might be wrong, been on an unlocked BL since last Aug so maybe my memory is boinked but I thought anyone can do a recoveryplay.img boot and do a nandroid that way? If I am wrong someone please correct me
Click to expand...
Click to collapse
Ill re-lock and try it using both Keiran's recovery and FXP's recovery.
Lets hope for luck
Edit: Dident work. Just as expected
jgregoryj1 said:
I might be wrong, been on an unlocked BL since last Aug so maybe my memory is boinked but I thought anyone can do a recoveryplay.img boot and do a nandroid that way? If I am wrong someone please correct me
Click to expand...
Click to collapse
Don't think you can hotboot without unlocked boot. But if has kept root he can install the recovery installer app or the manual way to install it (thread in this section of the forum).
Leraeniesh said:
Ill re-lock and try it using both Keiran's recovery and FXP's recovery.
Lets hope for luck
Click to expand...
Click to collapse
Just a reminder, now that I am thinking on it I am not so sure it will work.... not 100% sure, so you might relcok and find you cannot unlock.....
poo-tang said:
Don't think you can hotboot without unlocked boot. But if has kept root he can install the recovery installer app or the manual way to install it (thread in this section of the forum).
Click to expand...
Click to collapse
Oh yeah that right! We have the custom recovery app from google play store.... sweet, that will help..
https://play.google.com/store/apps/details?id=com.pvy.CWMinstaler&hl=en
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
The latest update enables backing up of the system settings now. This enables the exploit using the following link http://forum.xda-developers.com/showthread.php?t=1894717. The exploit gives shell root access with local.prop emulator setting.
Since the RUU is out there now, there should be no harm in this being public before everyone receives the update.
Edit:
It has been reported that this method is causing devices to change their HBOOT status to "*** TAMPERED ***". That can potentially void your warranty. Once an S-OFF exploit is released that can be corrected.
if this is true im gonna freak!
This is the best news I've had all day!
Please keep us posted on the progress
Sent from my Fireball using Xparent Blue Tapatalk 2
i am testing now, but i am getting confused at step 6..
click restore on your device
i am assuming that something pops up on the nexus? Or am i totally wrong..
Sorry, had to run to an appt so didn't have time to write anything up.
When you run adb restore you should get a prompt on your phone to restore.
Sent from my ADR6410LVW using xda app-developers app
superdave said:
Since the RUU is out there now, there should be no harm in this being public before everyone receives the update.
,Dave
Click to expand...
Click to collapse
Where is the RUU besides the pay link?
squeezyb said:
i am testing now, but i am getting confused at step 6..
click restore on your device
i am assuming that something pops up on the nexus? Or am i totally wrong..
Click to expand...
Click to collapse
Yes, you will get a pop up when trying to restore. You'll have to turn the screen back on before you can accept it if the screen is off.
nvm i have the restore screen now
Best. News. Ever.
Good luck to those giving this a shot. Please keep us updated on the progress. I'd give it a try now but I won't have time to try until this weekend.
Sent from my ADR6410LVW using xda app-developers app
i successfully get to step 8, but i cannot get a root shell... If anyone else has success, please share Cant wait to see progress on this
i'm almost afraid to be excited yet...
squeezyb said:
i successfully get to step 8, but i cannot get a root shell... If anyone else has success, please share Cant wait to see progress on this
Click to expand...
Click to collapse
Have you guys tried the automated scripts in Bin4ary's thread? (I still haven't downloaded the new RUU, so obviously I haven't)
I'm already rooted and I'm praying this is true! Good luck!
Sent from my ADR6410LVW using Tapatalk 2
I will give this a try when I get home tonight, Keeping my fingers crossed.
mdmower said:
Have you guys tried the automated scripts in Bin4ary's thread? (I still haven't downloaded the new RUU, so obviously I haven't)
Click to expand...
Click to collapse
i was only attempting without the new RUU. Hopefully the OTA arrives soon, and the exploit works. fingers crossed
EDIT:
I just received OTA.. downloading now
squeezyb said:
i was only attempting without the new RUU. Hopefully the OTA arrives soon, and the exploit works. fingers crossed
Click to expand...
Click to collapse
i recieved my notification for the update about 10 mins ago. but i don't know what to do. i rejected it for now.
i dont mind trying the update and attempting the exploit. I'll keep you guys updated
nice find OP!
Can't wait to see if this works!!
i am attempting the exploit now from
http://forum.xda-developers.com/showpost.php?p=31545627&postcount=1
it completed successfully, but i do not see Superuser. Has anyone else attempted?
It will appear to complete successfully, but, the changes to system are always reverted. Same thing happens doing it manually. You can get emulator mode root, just cant change system yet without it reverting.
squeezyb said:
i am attempting the exploit now from
http://forum.xda-developers.com/showpost.php?p=31545627&postcount=1
it completed successfully, but i do not see Superuser. Has anyone else attempted?
Click to expand...
Click to collapse
I have a vzw max and i recently reverted everything back to stock and unrooted; or so i believed. The kernel still says 3.4.10 etc. and the phone has no signal nor can it find my location. It keeps rebooting every 30 secs or so and no matter what mode I put the device into, it isn't recognized by my PC. the bootloader is locked and I am S-Off. This all happened after I tried to flash CWM's HTC M7 recovery because the Max isn't listed and I couldn't figure out how to flash TWRP. Help please because this is getting crazy and I can't figure out what to do...
bump
nobody at all eh...
LocBox said:
nobody at all eh...
Click to expand...
Click to collapse
So if you boot to bootloader keeps rebooting there too?
Sent from my Nexus 7 using Tapatalk
dude i feel for you.
why did you put m7 cwm on there. clearly not for this device.
can you still get to bootloader? if you can flash the correct recovery! then find a backup someone has done and restore. or flash the correct boot.img
dude here's the correct recovery
http://forum.xda-developers.com/showthread.php?t=2498749
Well the only problem is my any pc won't even detect that it's connected when I plug it into it. So I can't use any fastboot or adb methods and even when I put the phone into fastboot mode it doesn't connect either. I'm able to put it into bootloader mode and it doesn't reset but still no connection; just charges. I've tried flashing through stock recovery manually and it aborts every attempt I'm assuming because my BL is locked..
No it doesn't
dottat said:
So if you boot to bootloader keeps rebooting there too?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
no it doesnt'
LocBox said:
no it doesnt'
Click to expand...
Click to collapse
Ok. I know how we can fix then. Let me pm you
Sent from my HTC6600LVW using Tapatalk
Thanks
Dottat has helped me and not a moment too soon, I was seconds from printing out the return label for HTC and sending it in for a refurb exchange. smbh. thanks man.:good:
dottat said:
Ok. I know how we can fix then. Let me pm you
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
hey mate, whats the secret sauce
Flashing the zip from bootloader ?
pradeepvizz said:
hey mate, whats the secret sauce
Flashing the zip from bootloader ?
Click to expand...
Click to collapse
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
JBS976 said:
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
Click to expand...
Click to collapse
haha, okay chill mate. i was kidding there.
i am guessing it was full flash of rom / kernel using the zip in the bootloader.
pradeepvizz said:
haha, okay chill mate. i was kidding there.
i am guessing it was full flash of rom / kernel using the zip in the bootloader.
Click to expand...
Click to collapse
That is correct, full flash from bootloader. 0P3PIMG.zip on root of sd. and boom with some pow.
JBS976 said:
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
Click to expand...
Click to collapse
I wasn't trying to hide anything. I typically will walk a user through using the encrypted RUU (my person preference as i know it's intact) to restore their phone as long as it can boot to bootloader. I take it offline because the mods didn't take kindly to the encrypted RUU being posted in the past. I don't have an answer as to why that was case so I just keep that part off the main threads. If its someone in need (like the OP) i have no problem helping one on one.
dottat said:
I wasn't trying to hide anything. I typically will walk a user through using the encrypted RUU (my person preference as i know it's intact) to restore their phone as long as it can boot to bootloader. I take it offline because the mods didn't take kindly to the encrypted RUU being posted in the past. I don't have an answer as to why that was case so I just keep that part off the main threads. If its someone in need (like the OP) i have no problem helping one on one.
Click to expand...
Click to collapse
It's cool, I didn't mean it to sound like anything was being hidden, I just like to read all this stuff and take it in for future reference as I don't want to bother you guys unless I just cannot figure it out on my own. Believe me i really appreciate all you guys do on here as this is an invaluable resource if people take the time to read through things. I was unaware that they didn't want the RUU's on here which really sucks because they are nice to have like I had them for the rezound and it came in real handy at times. Not having them for this device yet has been one of the reasons I have been hesitant to do much else than to S-OFF and root. At this point I guess I am waiting for the OTA Kit Kat update then I will probably dive in.
Bryon
JBS976 said:
It's cool, I didn't mean it to sound like anything was being hidden, I just like to read all this stuff and take it in for future reference as I don't want to bother you guys unless I just cannot figure it out on my own. Believe me i really appreciate all you guys do on here as this is an invaluable resource if people take the time to read through things. I was unaware that they didn't want the RUU's on here which really sucks because they are nice to have like I had them for the rezound and it came in real handy at times. Not having them for this device yet has been one of the reasons I have been hesitant to do much else than to S-OFF and root. At this point I guess I am waiting for the OTA Kit Kat update then I will probably dive in.
Bryon
Click to expand...
Click to collapse
Check your pm shortly. S-off later today ?
Sent from my HTC6600LVW using Tapatalk