Develop Bugs

[HOW TO][LTE] Revert to original 4.0.1 STOCK on Windows

Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!

Thanks, this worked for me. However, it does not re-lock the bootloader. You can tell by when the Google logo is on the screen while booting up, if there is an unlocked lock on the bottom then it is unlocked. To fix this, type in:
flashboot oem lock
Click to expand...
Click to collapse
After that you should be good to go again and be stock.

Why not use the 4.0.2 image? Makes more sense to use the latest version:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz

I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?

Zzim said:
I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?
Click to expand...
Click to collapse
If you've got the SDK installed put the fastboot files in the sdk\tools or sdk\platform folder where adb is located. The adbwinapi.dll should be located in there.
Or just copy adbwinapi.dll into the same folder where you have the "restore kit" files downloaded from the OP.

confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus

error
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz

djeddieone said:
confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus
Click to expand...
Click to collapse
cerotes have galaxy nexuses? hrm

mikedfromaz said:
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz
Click to expand...
Click to collapse
Winzip.. unzip it twice...
Sent from my Galaxy Nexus using XDA App

edit: got it thanks

Thank you for the script..i know it will come in handy one day or another!
Sent from my Galaxy Nexus using xda premium

whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?

bigeric828 said:
whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?
Click to expand...
Click to collapse
It was zipped with WinRAR as a standard zip file. Should be able to be opened on just about anything... Have you tried redownloading?

oops already posted this but i put it in the wrong thread but here it is again sorry.
does anyone know how i can get this working? whenever i run it i just get an error: device not found
waiting for bootloader...
flashing bootloader...
error cannot load "bootloader-toro-primek10.img"
<waiting fo device>
anyone suggestion? ive tried reinstalling the drivers and its still not working
any help is appreciated thanks

so.....how do we run the script? with fastboot? with what commmands? it's late, i'm tired and i just want to start from scratch on my GNex...had Wallet running, then loaded BB, lost Wallet, now wallet won't run on ANY rom i have, even rebuilt to 4.0.2, but need to get back to 4.0.1...i posted a question in the Q&A section if there was an ODIN of 4.0.1 lying around somewhere....hopefully i'll get some help either way...
thanks.
EDIT...got it, double click the bat file...the original post did not say that.....thanks for the last post for mentioning it

|Jason8| said:
Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!
Click to expand...
Click to collapse
Having seen the Nexus S sticky for factory firmware etc., I think its time we see this or another post evolve into the same sort of thing including full restores for 4.0.1, 4.0.2 and the eventual 4.0.3(lte) radio's etc.,

Here's a modified script that will allow you to choose between 4.0.1 and 4.0.2. (as long as you have either image or both) It also has the option to re-lock the bootloader.
I'll also update it when the official 4.0.3 images are released.
I don't take no credit for what was already done, I just modified it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions:
=========
1- Extract folder with contents of this package.
2- You will need the Google Factory image for the version you want to restore, or both if you want.
3- Extract the image files to the same folder in step one. Image files should not be in a seperate folder!
So you should have, in one folder, the above files contained in this package plus:
image-mysid-xxxxxx.zip (xxxxxx= pertains to what version)
radio-tor-i515.xxxx.img
radio-cdma-tor-i515.xxxx.img
flash-all.sh
bootloader-tor-primexxxx.img
4- Dbl click on GNexRestore.bat and follow the prompts.
Optionally, if you do have the Android SDK installed, just copy the image files and GNexRestore.bat to the platform-tools folder.
fastboot.exe will also be needed, if you don't have it already, just copy the one in this package to the same location.
Then run GNexRestore.bat

when you extraxt the factory image i get one file and the icon looks like a blank piece of paper. is that how it is suppose to be

When you extract the image, you should see a folder with the files you need.
e.g. this is from 4.0.2

[S-OFF & HBOOT 1.09.0099] We need your unmapped memory dump

Hello !
For those who are already S-OFF (XTC-Clipped or stock S-OFF) and who didn't read the big thread about finding a software S-OFF, you can greatly help us by doing these steps !
If you are willing to help and if your phone is working without any problem with the European stock firmware, you're ready to go !
/!\ Be aware that all your data will certainly be lost in the procedure, so don't forget to do some backups before. /!\
What we need : a dump of the unmapped memory of a S-OFF phone with HBOOT 1.09.0099
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The unmapped memory of the phone is about 8% of the 512MB available on our device. That's where the secu_flag is hiding.
We already compared two dumps of two S-ON phones. The differences were after 0x024c0010 (36,75MB). That means only the last 2MB of the file (which is 38,75MB) is different for the S-ON phones.
We guessed that the secu_flag is certainly in the first 36,75MB part of the dump. So we could easily find it by comparing S-ON/S-OFF dumps !
The procedure is written for Windows users.
0- Backup all your data.
1- Launch RUU_Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed.exe
http://www.shipped-roms.com/index.php?category=android&model=Marvel
2- Launch PG7610000_Marvel_hboot_1.09.0099_2.13.401.3_0210_R.exe
http://www.htcdev.com/ruu/PG7610000_Marvel_hboot_1.09.0099_2.13.401.3_0210_R.exe
Then, you should have HBOOT-1.09.0099 + RADIO-7.54.39.28M.
However, I don't know if you have to go through the HTCDev procedure.
3- Download this archive and unzip it in a folder on your desktop :
http://www.mediafire.com/?jn7c1p8zbqwplni
Launch the Windows Command Prompt (Win+R => cmd) and use the 'cd' command to go in the folder created before.
Start your phone in "Fastboot USB" mode (Power + Vol Down).
Then, use this fastboot command :
Code:
fastboot -c "mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata),[email protected](devlog),[email protected](radio)" boot recovery-clockwork-5.0.2.8-marvel.img
4- Mount your SD card using the Vol Down & Power buttons ("mounts and storage" --> "mount /sdcard").
Then in the Windows Command Prompt :
Code:
adb shell
cat /dev/mtd/mtd7 > /sdcard/radio-soff-hboot1_09_0099.img
5- Zip your dump (the file is at the root of your SD-Card) and send it on mediafire.com. You should use a password and give it to some trusted people who can get something of your dump (no.human.being, theq86, BeciMester).
A lot of thanks for these last three guys for what they are doing to the Wildfire S scene right now !

pihug12 said:
Hello !
For those who are already S-OFF (XTC-Clipped or stock S-OFF) and who didn't read the big thread about finding a software S-OFF, you can greatly help us by doing these steps !
If you are willing to help and if your phone is working without any problem with the European stock firmware, you're ready to go !
/!\ Be aware that all your data will certainly be lost in the procedure, so don't forget to do some backups before. /!\
What we need : a dump of the unmapped memory of a S-OFF phone with HBOOT 1.09.0099
The unmapped memory of the phone is about 8% of the 512MB available on our device. That's where the secu_flag is hiding.
We already compared two dumps of two S-ON phones. The differences were after 0x024c0010 (36,75MB). That means only the last 2MB of the file (which is 38,75MB) is different for the S-ON phones.
We guessed that the secu_flag is certainly in the first 36,75MB part of the dump. So we could easily find it by comparing S-ON/S-OFF dumps !
The procedure is written for Windows users.
0- Backup all your data.
1- Launch RUU_Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed.exe
http://www.shipped-roms.com/index.php?category=android&model=Marvel
2- Launch PG7610000_Marvel_hboot_1.09.0099_2.13.401.3_0210_R.exe
http://www.htcdev.com/ruu/PG7610000_Marvel_hboot_1.09.0099_2.13.401.3_0210_R.exe
Then, you should have HBOOT-1.09.0099 + RADIO-7.54.39.28M.
However, I don't know if you have to go through the HTCDev procedure.
3- Download this archive and unzip it in a folder on your desktop :
http://www.mediafire.com/?jn7c1p8zbqwplni
Launch the Windows Command Prompt (Win+R => cmd) and use the 'cd' command to go in the folder created before.
Start your phone in "Fastboot USB" mode (Power + Vol Down).
Then, use this fastboot command :
Code:
fastboot -c "mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata),[email protected](devlog),[email protected](radio)" boot recovery-clockwork-5.0.2.8-marvel.img
4- Mount your SD card using the Vol Down & Power buttons ("mounts and storage" --> "mount /sdcard").
Then in the Windows Command Prompt :
Code:
adb shell
cat /dev/mtd/mtd7 > /sdcard/radio-soff-hboot1_09_0099.img
5- Zip your dump (the file is at the root of your SD-Card) and send it on mediafire.com. You should use a password and give it to some trusted people who can get something of your dump (no.human.being, theq86, BeciMester).
A lot of thanks for these last three guys for what they are doing to the Wildfire S scene right now !
Click to expand...
Click to collapse
good call man

Flashing Gio from ODIN with .tar.md5

I dowloaded my stock firmware from samfirmware.com and now i would like to flash it. It is a single tar.md5 package. I would like to known how to flash it. I searched, but it was not much help to me. Do i use the single package option in ODIN?
- i have never used odin, but i have flashed alot of roms so im not completely stupid when it comes to this stuff.

Yes, one package

Once you have Odin
To do so
The file "GIO_v0.1.ops"
You will find in the package of Odin
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You put the file you downloaded md5
How do you see "PASS!" disconnect and if appears
"Close serial port and wait until rebooting" a disconnect, and wait until the phone turns on, of course, disconnect the cable.
It says Samsung on the phone remove the battery and enter the Recovery Menu
select "wipe"
select reboot
READY
I already have the new rom

Is it possible to unzip the rom with 7zip and remove the recovery image so i can still have my custom recovery?

AlwaysDroid said:
Is it possible to unzip the rom with 7zip and remove the recovery image so i can still have my custom recovery?
Click to expand...
Click to collapse
Ypu can but must be able to do a md5sum or flash as .tar without md5 check
Sent from my GT-S5660 using xda premium

Cant find?
voetbalremco said:
Ypu can but must be able to do a md5sum or flash as .tar without md5 check
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
Im trying to flash a file called S5660MUGKG3_S5660MBMCKG3_BMC. When ever i try to one package i cant seem to find it? Can anyone help me with this?

Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.

Darkshado said:
Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.
Click to expand...
Click to collapse
How do I unzip it? Can I use winrar and extract?

Darkshado said:
Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.
Click to expand...
Click to collapse
Yay I got it!
Thanks for your help!
Is it fine if it says 1 (COM10) ? and also its keeps on showing the boot animations over over... wont go further and on odin it says pass. should i keep on waiting or is somthing wrong? is it bricked?

1 (COM10) is simply to indicate the serial port number assigned to your phone by Windows and the Samsung USB driver in Odin.
Your phone is boot looping, some might consider this a soft brick. My best guess is that you previously installed a ROM that formatted your /data and /cache partitions from the stock RFS format to ext4 instead. The stock 5660M ROM doesn't support ext4.
Reboot in the stock recovery, either with "adb reboot recovery" or by using the home and power keys simultaneously.
From there, wipe user data and cache, or something similar I don't recall the exact wording, but I do remember they were two separate commands.
Reboot, should work now. Use ddms (part of the Android SDK) to see what's going on under the hood if you feel like it.
I take it computers are a relatively new thing for you to ask how to unzip files. My best advice: make very regular backups and read instructions carefully. Losing data is not cool. Losing someone else's data is worse. (I'm guessing you're on the family computer here...)

can someone help me with H815 misc partition img file

I have mistakenly erased misc partition and have no backup for it so my WIFI dosen't work for me
I've copied the way to make misc.img file from https://forum.xda-developers.com/tmobile-g4/help/request-h811-misc-partition-image-t3516353 and it's below
===============================================Misc.img=====================================================================
Process to generate a image of misc is as follows:
Reboot into TWRP recovery.
Run "adb shell" or open a recovery terminal.
Run "ls /dev/block/platform/*/by-name/misc" to identify the path to your misc partition.
Mine is "/dev/block/platform/f9824900.sdhci/by-name/misc"
Run "dd if=/dev/block/platform/f9824900.sdhci/by-name/misc of=/sdcard/misc.img"
Replace "f9824900.sdhci" if appropriate for your device, using the value found in step 3.
You now have a file misc.img in your storage directory. You can either use "adb pull /sdcard/misc.img" to download it onto your PC, or you can upload it directly using XDA mobile.
If anyone here can follow the above steps and upload the resulting image, I'd be deeply grateful.
===============================================Misc.img=====================================================================

OriginLua said:
I have mistakenly erased misc partition and have no backup for it so my WIFI dosen't work for me
I've copied the way to make misc.img file from https://forum.xda-developers.com/tmobile-g4/help/request-h811-misc-partition-image-t3516353 and it's below
===============================================Misc.img=====================================================================
Process to generate a image of misc is as follows:
Reboot into TWRP recovery.
Run "adb shell" or open a recovery terminal.
Run "ls /dev/block/platform/*/by-name/misc" to identify the path to your misc partition.
Mine is "/dev/block/platform/f9824900.sdhci/by-name/misc"
Run "dd if=/dev/block/platform/f9824900.sdhci/by-name/misc of=/sdcard/misc.img"
Replace "f9824900.sdhci" if appropriate for your device, using the value found in step 3.
You now have a file misc.img in your storage directory. You can either use "adb pull /sdcard/misc.img" to download it onto your PC, or you can upload it directly using XDA mobile.
If anyone here can follow the above steps and upload the resulting image, I'd be deeply grateful.
===============================================Misc.img=====================================================================
Click to expand...
Click to collapse
If you have a copy of your kdz for your model and software version for your specific carrier or can obtain one, you could use SALT to extract all your .image partition files yourself ... it could prove more handy doing it this way in the long run when issues arise.

sdembiske said:
If you have a copy of your kdz for your model and software version for your specific carrier or can obtain one, you could use SALT to extract all your .image partition files yourself ... it could prove more handy doing it this way in the long run when issues arise.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried what you said but kdz doesn't hold misc image

OriginLua said:
I've tried what you said but kdz doesn't hold misc image
Click to expand...
Click to collapse
Copy your post with the screen shot over to the SALT thread.

fastboot.exe doesn't work

I want to flash a boot.img to Xiaomi 6, but fastboot does not work anymore.Device unlocked
fastboot.exe can recognize my device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I type the command, it gets stuck here
Then i unplug the cable
I am using windows 10
help please...
fastboot.exe version
driver version

Does your "boot.img" inside the target folder? in your case inside "platform-tools" folder?
I recommend install ADB installer from this forum https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Or just download it here;
ADB Installer : ADB Installer V1.4.3
After done installing
Create new folder in your Desktop
Copy and paste your boot.img inside the folder
Inside the new folder press and hold "Shift" in your keyboard, Right click and choose "Open command prompt windows here"
Reboot your Phone into the bootloader
Connect your phone
And flash your boot.img as you do it before :good:

Shimizux said:
Does your "boot.img" inside the target folder? in your case inside "platform-tools" folder?
I recommend install ADB installer from this forum https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Or just download it here;
ADB Installer : ADB Installer V1.4.3
After done installing
Create new folder in your Desktop
Copy and paste your boot.img inside the folder
Inside the new folder press and hold "Shift" in your keyboard, Right click and choose "Open command prompt windows here"
Reboot your Phone into the bootloader
Connect your phone
And flash your boot.img as you do it before :good:
Click to expand...
Click to collapse
Thank you for your reply!
I used adb installer and uninstalled the original driver.
It's stuck here.I unplugged the cable and it did not respond.
I'm sure boot.img is in the current directory.

Tubby Custard said:
Thank you for your reply!
I used adb installer and uninstalled the original driver.
It's stuck here.I unplugged the cable and it did not respond.
I'm sure boot.img is in the current directory.
Click to expand...
Click to collapse
Sorry i dont understand, where do you stuck?
By the way, do you have custom recovery (TWRP) install on your phone?
You can flash boot.img with TWRP instead of using fastboot method

Also had this issue. At one PC worked well, but at another no. Changing USB ports or cables does no matter.
Try to use old pure USB2.0 Hub. In my case D-Link DUB-H7 (in metal case) completely solved the problem.