Related
Because of my stupid mistakes of making my SD card failed the first time, I found a way to actually downgrade the system using HBoot mode even if you have a new HBoot system (i.e. Official Chinese version, Carrier Locked version, etc).
First thing to do, is to download the 2.73.405.5 official WWE RUU package (the exe);
Then, run that wizard, and while the wizard's program is running, search in your PC's %userprofile% folder, and look for "rom.zip"
Rename that rom.zip to HEROIMG.zip.
Put that file into your MicroSD card's root folder. Do not modify its contents.
put that SD card into your phone.
While the card is in, hboot the device (vol down + power).
it will pop up the HBOOT mode of the device. It will now check for a few files if they exist on your SD card. (HERODIAG.zip, etc)
in the last check, it will look for HEROIMG.zip, and tries to load it. Once the loading bar is complete on the top right side of the device, it will ask you to press home to continue the upgrade, or press other key to escape it. (i am not 100% sure if those are the keys, but you can read english so figure that part out).
Once the flashing is done (remember, this method will wipe everything. including radio, recovery, system, data, cache), you will now have a complete original ROM on your system. From there, use InstantRoot or any other rooting exploit, to root your device, put Cyanogen's recovery there, and start upgrading into custom roms!
Let me know if this method works or not. it worked on 3 of my friend's HTCs.
/* p.s. however i still have my unresolved issue about the SD card slot and USB device not recognized issue. */
Nope, I tried that before and it fails the CID check.
Guiness in a can? BRILLIANT!
yea, everyone has been jumping through their butts trying to figure out how to make goldcards and bypasses... why not just use hboot like htc probally uses it? Duh! Thanks for this!
edit..... oh snap....
does not work for me!
Once the loading bar is complete on the top right side of the device
go back to hboot...
and nothing to do
this won't work because the SPL is still checking the CID of the rom.zip you renamed to HEROIMG
for some people the flash will work, but thats because they have a hero with a CID thats in the range of the cid numbers (open the .zip file and check the android-info.txt to see the list.
changing topic is this is confusing people
nice try though
Otiginal IMG
Confirm ...works for me.After rooting...... and flashing couple images i try reflash back original rom - official ruu not want work ...stop on bootloader .....extracted rom not be a flashable trough sd card and amon ra loader....this way work like charm.Thnx.
Original IMG
Confirm ...works for me.After rooting...... and flashing couple images i try reflash back original rom - official ruu not want work ...stop on bootloader .....extracted rom not be a flashable trough sd card and amon ra loader....this way work like charm.Thnx.
Thank you, you are the man!
Thank you so much, i was about to eat my phone. it is htc hero and it worked. thank you so much...
since we have this thread i can ask as well...
is HEROIMG.ZIP signed, or why wouldn't one just alter the CID values in android-info.txt?
kendong2 said:
since we have this thread i can ask as well...
is HEROIMG.ZIP signed, or why wouldn't one just alter the CID values in android-info.txt?
Click to expand...
Click to collapse
I believe it is signed using HTC's own personal keys, preventing us changing the RUU extract.
anon2122 said:
I believe it is signed using HTC's own personal keys, preventing us changing the RUU extract.
Click to expand...
Click to collapse
Might be worth a test to do self signed ?
Jesterz said:
this won't work because the SPL is still checking the CID of the rom.zip you renamed to HEROIMG
for some people the flash will work, but thats because they have a hero with a CID thats in the range of the cid numbers (open the .zip file and check the android-info.txt to see the list.
changing topic is this is confusing people
nice try though
Click to expand...
Click to collapse
hi, i have the same problem and my cid is in in the list.
what could be the problem?
How the hell did you came up with that?
It worked perfectly! Cannot thank you enough.
You're the man.
been looking for this for nearly a week.
got my wife a new phone and want to store it original, but couldnt get back to stock,all cid fails.
with this version no cid fail and stock htc hero again.
thanks, you tha man.
(Avis aux intéressés, j'ai traduit mon message en français, et reparti une discussion sur Frandroid.)
Hello,
I managed to map the partitions on the Gio 5660M (Bell Canada, 2.3.4, MUGK3) in order to extract an ODIN flashable complete stock backup.
I have also made a stock, rooted ROM backup by working in a hex editor. Other tools that helped the mapping were Winmerge, to do file comparisons with an Euro 5660 ROM, and Notepad++ for string searches.
Those with a 5660M that are experiencing issues after flashing Euro 5660 ROMs that have been posted here now have the possibility of flashing back their original radio and kernel.
ROM development and deployment is going to be safer going forward.
I copied the blocks with the dd command as follows:
dd if=/dev/block/bml1 of=/sdcard/bml1 bs=4096
WARNING!!! DO NOT dd /dev/block/stl5 as there have been multiple reports of bricking following reading it. We already know that this block contains the EFS partition, including the SIM-lock code. You can however dd bml5 without issue from a "live" phone. If you absolutely want stl5, you may get it by using a rooted custom recovery.
From what I've gathered bml is essentially a lower level interface to the same blocks accessed by stl, but the results differ somewhat in resulting file size.
Here are the results:
Code:
/dev/block/bml1 MIBIB
/dev/block/bml2 QCSBL
/dev/block/bml3 OEMSBL
/dev/block/bml4 AMSS
/dev/block/bml6 Essentially empty, with a FSR_STL string at the beginning.
/dev/block/bml7 arm11boot
/dev/block/bml8 boot.img. My initial assumption was based on the .ops file supplied with the Euro ROM I've done my comparisons with. This has since been confirmed with actual flashing.
/dev/block/bml9 recovery.img for the same reasons as above.
/dev/block/bml10 Essentially empty. Mine has a BMC string at the beginning which matches the CSC code on this phone, followed by an ON and an OFF.
/dev/block/bml11 Empty. \xFF all around.
/dev/block/bml12 Seems to contain the same RFS data as stl12, but with an additional 8 megs of data/padding, not readable by MagicISO.
/dev/block/bml13 Like 12 above, but user data
/dev/block/bml14 As above, but the almost empty partition
/dev/block/stl1 cannot open for read
/dev/block/stl2 cannot open for read
/dev/block/stl3 cannot open for read
/dev/block/stl4 cannot open for read
/dev/block/stl6 Empty: contains only \xFF
/dev/block/stl7 cannot open for read
/dev/block/stl8 cannot open for read
/dev/block/stl9 cannot open for read
/dev/block/stl10 cannot open for read
/dev/block/stl11 cannot open for read
/dev/block/stl12 system.rfs - is flashable as-is once tarballed. Also contains the CSC files as we're taking this from a "live" installation, contrary to an OEM provided image. (My image is also rooted for the same reason.)
/dev/block/stl13 data.rfs - User data partition
/dev/block/stl14 cache.rfs - Odin hangs when I try to flash it. Use CWM and dd back into place from the SD card.
From what I see we can't repartition our phones like the GT-I9000 guys do, so there are no PIT files to worry about. Only the OPS files which ODIN uses. We're not able to flash with Heimdall in its current configuration as it requires a PIT file.
GT-S5660M_MUGKG3_stock_rooted_ROM_v2.7z (101.46 MB)
Un7-Zip, flash tarball with Odin using the "One Package" option. Tested working on my phone. I think it goes without saying that flashing this is at your own risk.
(PDA: S5660MUGKG3 PHONE: S5660MUGKG3 CSC: S5660MBMCKG3)
Tutorial on flashing with Odin, with link for the appropriate version for our phone.
I've released my custom 5660M ROM, ArpegGioMod.
Goodbye,
Darkshado
Wow,
Thank you very much. The screen brightness issues and problems connecting to the mobile 3G network were very troublesome.
I will be flashing this ROM back to my s5660m.
THANK YOU!
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!
Cool! Please, pretty please let me know as soon as possible how it turns out. When do you plan on trying this? This afternoon or later tonight?
Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Good luck,
Darkshado
Coolty said:
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!
Click to expand...
Click to collapse
Great! You just made my day!
About the missing CSC file: CSC is an acronym for Carrier/Country Specific Code. The csc.rfs file is a partition image file that, as far as I can tell, is merged with the contents of the system.rfs partition. In our case, the CSC file would contain the APN settings, as well as the Bell proprietary apps like self-serve and remote PVR.
Instead, since I took the system partition from a live phone, the CSC content is already in the system.rfs partition. I think the idea behind this is that Samsung can release new CSC packages without having to update the whole firmware when "new" carriers add the phone to their lineup.
I'll see if I can edit the RFS partitions, (maybe by mounting them on the phone directly?) if so, I would be able to unroot, and make that separate CSC partition as well. That would make the backup completely stock, as if it came right from Samsung.
Another, simpler solution would be to modify the OPS file to skip the CSC partition.
One question: did you re-tar each file individually for ODIN to take them?
CM7 port: I'd love to have one on that phone as well, but I'm not in a position to tackle that project, yet. The good news is that since we now have a way to bring the phone back to stock, we can experiment safely.
Goodbye,
Darkshado
Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Click to expand...
Click to collapse
I will try this as well, will let you know the status of that as soon as I get to that. I am pretty confident with flashing phones by now
One question: did you re-tar each file individually for ODIN to take them?
Click to expand...
Click to collapse
No, I use linux so it was an easy process of copying the factory.rfs to my HDD, renaming it to system.rfs, deleting factory.rfs from TAR, and then adding system.rfs to the TAR file.
Let me know if you want me to try anything else, as I have access to linux and am pretty knowledgeable when it comes to things of that nature.
I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.
Step by Step guide for Noobs?
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.
red02 said:
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.
Click to expand...
Click to collapse
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?
Coolty said:
I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.
Click to expand...
Click to collapse
if you could post it, that would be much appreciated!!
steez003 said:
if you could post it, that would be much appreciated!!
Click to expand...
Click to collapse
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty
Coolty said:
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?
Click to expand...
Click to collapse
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
red02 said:
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
Click to expand...
Click to collapse
Hi,
I'm not one for explaining things in great detail, but the basic breakdown of the things you need (google is your friend) are:
1) Odin_Multi_Downloader_v4.42
2) The USB drivers for your phone (Hint: Samsung Kies)
3) OPS File (for this phone, I recommend GIO_v1.0.OPS)
4) Either a single TAR file or multiple files (eg, appboot, PDA, etc) For the file I am uploading it will be a single TAR file which is a package that includes all the things needed.
Then, you just remove the battery in your phone, unplug it from USB or wall charger, put battery back in, hold vol down + HOME + power until you see a screen (you may have to press a vol key after that, read the screen to see if you need to) Your screen on the phone should say DOWNLOADING... This is when you:
1) connect phone to computer via USB after installing drivers (kies, usb driver)
2) make sure kies is closed
3) run ODIN
4) choose the proper OPS file
5) click single package
6) choose the TAR file you want to flash to your phone
That's it!
EDIT:
I am providing some forum links that may better explain how to do what you need done:
How to unbrick (for samsung ACE, but applies to the 5660m) http://forum.xda-developers.com/showthread.php?t=1071970
How to use ODIN to flash your phone: http://forum.xda-developers.com/showpost.php?p=16979859&postcount=549
And of course, the great bible of GIO 5660 links and information: http://forum.xda-developers.com/showthread.php?t=1209425
I have updated my previous post to include the download link to the fixed rom for use with the s5660m.
(search for "s5660m by coolty" on the forums to find it)
Coolty said:
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty
Click to expand...
Click to collapse
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Will this help at at all with a blank IMEI? I assume this would only help for people flashing back to stock firmware or recovering from a non-bootable or reboot loop phone?
steez003 said:
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Click to expand...
Click to collapse
I'm also running into the same issue
Sent from my Nexus S using XDA App
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Waqasshazad: Maybe wiping the caches will help, but the issues might be due to running a 5660 on a 5660M as well. We know the kernels and modems aren't compatible, it may go a bit further. By the way, it's spelled factory.
MacrossFX: I've seen mentions of people dd'ing their stl5 partition into a file and then back on the phone, but I'm unsure this worked in the end. I'm afraid your only solution might involve a shipment to the service center...
ClockworkMod Recovery for the Samsung Galaxy Gio GT-S5660
http://forum.xda-developers.com/showpost.php?p=16980117&postcount=559
May be this can backup for you , too with s5660m , i have tested on Gt s5660 and it worked perfectly fine..
waqasshahzad1986 said:
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Click to expand...
Click to collapse
I followed your instructional video and did do a factory reset before and after. Maybe i'll try reflashing it again tonight and see what happens.
Hi!!
Some people have been asking this question however, I am unable to fix the problem.
I need to return my phone for warranty because my volume buttons no longer work, so I am trying to bring it back to stock.
I am following The Complete Guide 2 Return Rooted Phone Back 2 Stock for Vodafone Australia Warranty by Yoshi.
I am currently at this step....
INSTALL STOCK VODAFONE (AU) ROM
Follow this link to download Kazuroka's Vodafone Australia Stock Branded ROM 1.32.178.5 http :// depositfiles.com/files/ 3x1c6v6hj
Create a folder on you micro SD card such as "stockrom" as follows: "/clockworkmod/backup/stockrom/" then copy the zip file there. Enter bootloader as described above. Choose recovery, then wipe/factory reset, choose backup/restore, then restore and select the zip file from the folder you just copied to your MicroSD card. After everything is done it will ask you to reboot. If so some reason when you select the option at the end to reboot and you just get a blank screen, wait for a while and be absolutely sure your phone your phone won't turn on then just remove and replace battery and then turn on.
This sounds easy enough, however upon downloading Kazuroka's stock rom and then following the steps above, in recovery it won't restore the zip file because it says 'md5 mistmatch'
These are the solutions I found on the forums and have tried...
1. extracting Kazuroka zip into the stockrom folder on the sd card and in recovery run from there - this did not work
2. Extract the contents of the zip into /clockworkmod/backup/stockrom/.
Then delete the nandroid.md5 file.
Then use md5sum to recreate it like this:
md5sum *img > nandroid.md5
- unfortunately I do not know how to recreate it
3. redownload the file because it may be a transfer error - I have done this and it still says a md5 mismatch
I have been searching for 5 hours for the answer. Please! If anyone can direct me to the thread with the solution, or anything that could help me that would be lovely!
Any help is much appreciated!!
Thank you !!!!
-MATE! I'm am having this exact same problem, as I need to return my phone for the exact same volume rocker issue. I'm not getting any answers unfortunately.
I've followed all the same suggestions as use, and don't know how to recreate the nandroid.md5.
I've tried creating a new file nandroid.md5\ 'value of the md5'*img, just changed to error to 'no md5 .' so I don't really know at this point, but will post the solution if/when I find one. If you do, please post it on this thread of pm me. Thanks for posting this, I was close to doing so myself.
I found this download from a google search http://www.multiupload.com/D42QL68GYX it is a WWE but in the page to that link it had this name HTC Desire HD - Vodafone 1.32.405.3 RUU. Apparently it doesn't have the vodafone splash screen nor bloatware but since RUUs are official releases it should not void your warranty, I sent my inspire 4g to warranty with a WWE RUU and AT&T simply replaced it with theirs after fixing my phone.
I dont know how Vodafone will act but it will probably be ok also check:
Shipped rom collection by FootBall
http://forum.xda-developers.com/showthread.php?p=19101263#post19101263
I've been searching around for a stock RUU, but Goo.im seems to no longer have it in it's archives and all the digging about has lead to dead links or Rooted versions of the Stock. I'm trying to restore it to trade in for repairs to street.
Would anyone have a copy of any Stock RUU's available? Non-rooted of course. <:
Madatsubomi said:
I've been searching around for a stock RUU, but Goo.im seems to no longer have it in it's archives and all the digging about has lead to dead links or Rooted versions of the Stock. I'm trying to restore it to trade in for repairs to street.
Would anyone have a copy of any Stock RUU's available? Non-rooted of course. <:
Click to expand...
Click to collapse
Try here:
http://androidfiles.org/ruu/?developer=Supersonic
Sent from my EVO using xda premium
If you are on Hboot 2.18 and it's S-ON, then the biggest problem that you may run into is that it will not except any RUUs if your misc partition has been updated. You would have to first downgrade the misc partition before attempting to run any RUUs.
If that's the case, you can download my old sdk.zip file found here
https://dl.dropboxusercontent.com/u/38127313/sdk.zip
Unzip the file to a folder on your computer, then copy the mtd-eng.img and flash_image to the root of your sdcard.
Then you can follow part of this guide (forget about the title), but you only need to follow steps 30-39 (the previous steps replaces step 29 and substitutes the PC36IMG file found in step 33) in order to downgrade the misc partition, assuming that your phone is still rooted also. You could also use the PC36IMG file in step 33. Mine is just part of that sdk.zip file.
http://forum.xda-developers.com/showthread.php?t=1473373&highlight=s-off
If you are not on Hboot 2.18, but S-ON, then the PC36IMG file inside my sdk.zip file should work fine. Just be careful to rename it PC36IMG.zip and not PC36IMG.zip.zip.
See my other thread about the upgrade message when I connect to HTC sync manager. (Even though the phone reboots and goes thru several flash screens, nothing is changed)
Phone is HTC Desire 526 Verizon prepaid.
This time, I let it run again, but I opened the program temp folder in explorer and grabbed the files.
It has a 1.2GB file that I'm guessing is system image and a 10MB file labeled boot image.
I uploaded it to my Google drive in the hopes that someone here can find a way to use it to get us a custom ROM, or at least root, going.
Here's the files:
https://drive.google.com/folder/d/0B_Sgf7j8WktiM0pmcDJveVBFWUU/edit
Cheers.
Are those files for the US or the Europe version?
Ynlord said:
Are those files for the US or the Europe version?
Click to expand...
Click to collapse
USA, Verizon prepaid
ericpeacock79 said:
USA, Verizon prepaid
Click to expand...
Click to collapse
Which one is exactly the temp directory of the program?
Ynlord said:
Are those files for the US or the Europe version?
Click to expand...
Click to collapse
Ynlord said:
Which one is exactly the temp directory of the program?
Click to expand...
Click to collapse
I pulled those files from the temporary download location of the HTC program on Windows, just after it downloaded the update, while it was copying the files to the phone.
It was in the Program Files directory of the HTC desktop program, instead of the windows user profile temp folder like most programs.
The files uploaded are the update files.
ericpeacock79 said:
I pulled those files from the temporary download location of the HTC program on Windows, just after it downloaded the update, while it was copying the files to the phone.
It was in the Program Files directory of the HTC desktop program, instead of the windows user profile temp folder like most programs.
The files uploaded are the update files.
Click to expand...
Click to collapse
I was having trouble downloading the one that you posted, i downloaded again with the htc sync manager and got it on this location C:\Users\<your_user_name>\AppData\Local\HTC MediaHub\FOTA.
Should i go to recovery and fast it or should i use adb for it?
Ynlord said:
I was having trouble downloading the one that you posted, i downloaded again with the htc sync manager and got it on this location C:\Users\<your_user_name>\AppData\Local\HTC MediaHub\FOTA.
Should i go to recovery and fast it or should i use adb for it?
Click to expand...
Click to collapse
I do not know if it would work like that. If I had to guess, I would say fastboot, but I really don't know.
I will try it tomorrow and let you know. I still have the phone, but I don't use it and can't seem to sell it on Craigslist...
Is it possible to unpack an image of the non branded version and compare the differences.. see what we can change to possibly allow hot-spot or root?
hemanolio said:
Is it possible to unpack an image of the non branded version and compare the differences.. see what we can change to possibly allow hot-spot or root?
Click to expand...
Click to collapse
That might be difficult, given that the US-market 526 was only sold by Verizon and doesn't seem to be too popular of a phone. I never found a way to order it unlocked straight from HTC.
Does the boot.img have an unlocked bootloader?I need one thats unlocked
there is no unlocked bootloader for the Vreizon prepaid Desire 526.
I posted these files in the hopes that someone could use them to get us unlocked.
Thank You for the files.
I will take a look and let you guys know how to flash it.
It will help the bootloader issue.
I need these files to keep working on this.
Thanks again
---------- Post added at 05:54 PM ---------- Previous post was at 05:46 PM ----------
To flash the rom. Whichever of the 2 downloads it is ???
rename the file to
Code:
0PM3IMG.zip
Copy 0PM3IMG.zip to the external sd card.
Boot the phone into the bootloader / download mode.
It should find the file on the sdcard and ask you if you want to install it.
I will test it out later.
Basically if you mess something up in the phone by deleting files or whatnot this should be useable to flash back to stock.
I know I'm just an amateur with programming but couldn't you/we just "Frankencode" it? Like have two/three of the same file and keep one original, have another be the successful edit, and have another be the experimental editing?
To some extent that is what i'm working on.
The Desire 626s is the same chipset and the boot-loader is unlockable.
These RUU files / ( Factory Rom ) ruu = rom update utility come packed with some goodies.
The bootloader is in the packages for the 526 and the 626.
The question is how to flash the files from the 626 to the 526.
The ruu uses a couple different security measures to make sure the files aren't tampered with.
The main zip file is signed with keys and verified to be signed against the public half of the keypair.
It's a file called keys in the /res folder of the recovery.img ramdisk.
By generating a pair of keys ( Private and Publick ) .pk8 and .pem and dumping the public key with dumppublickeys it is possible to change the key in the /res/key of the ramdisk. This means we can modify the main zip file and sign it with our own keys and it will pass the signature test.
But the zip files inside of the main zip are also signed / encrypted.
We can decrypt the inner zip files with bruuveal. So that can extract the zip files and not get errors.
Or use the HTC Decrypt tool found on this forum.
The interesting thing here is that prior to the ruu flashing the phone it flashes the HOSD.
That's the smaller zip file.
The only reason for HTC to do that i'm thinking is because the hosd / hboot that is on the phone to begin with blocks writing of the necessary partitions by some means.
So the hosd is pre-updated to allow the main ruu to flash.
This is not the case on the 626s. The other interesting thing is that the hosd flashes by itself in the main zip not a sub zip and like I said I can get around the first file signature.
If I can get the 626s firmware to flash to the 526 then we can unlock the boot-loader.
If we can find a way to get around the inner file signing ( If I can figure out where the public half of the key is)
You can flash the software using fastboot...
fastboot flash zip <name 1st zip>
fastboot flash zip <name 2nd zip>
If the second file will not be able to - use htc_fastboot
where to take - when unpacking (executing)standart RUU file
Anyone find a solution to this problem? I have the desire 526 and it froze during upgrading with the htc sync, now it doesn't go past the boot screen and I've searched for a solution to this problem everywhere.
Is it safe to say that none of the forums have a solution to the Desire 526 vzw prepaid problem? I've searched multiple forums, youtube videos, and no one either answer the problem or the answers do not work. However most of us are just looking for the original boot & recovery, but that seems to be an impossible mission. Hopefully, someone in some forum will come up with a solution that actually works, or someone will actually respond to some of our questions.
ericpeacock79 said:
See my other thread about the upgrade message when I connect to HTC sync manager. (Even though the phone reboots and goes thru several flash screens, nothing is changed)
Phone is HTC Desire 526 Verizon prepaid.
This time, I let it run again, but I opened the program temp folder in explorer and grabbed the files.
It has a 1.2GB file that I'm guessing is system image and a 10MB file labeled boot image.
I uploaded it to my Google drive in the hopes that someone here can find a way to use it to get us a custom ROM, or at least root, going.
Here's the files:
https://drive.google.com/folder/d/0B_Sgf7j8WktiM0pmcDJveVBFWUU/edit
Cheers.
Click to expand...
Click to collapse
curious to know what file are we suppose to use?
badHTC526 said:
curious to know what file are we suppose to use?
Click to expand...
Click to collapse
No idea. I just put these up in the hopes that someone would be able to put them to good use. I'm not a dev, sorry.
I was able to find quite a few RUU's for HTCD100LVW after excavaing into the mythical 2nd & later pages of Google search. I can't remember how bad my soft brick was, but I spend somewhere near 40 hours ****ing this phone up before finally pulling the right bootable sd image on BigCountry's BL/root/TWRP method
Sent from my Desire 526 using XDA Labs