[Solved]Moving back to Stock LTE - Someone give me a hand please? - Samsung Galaxy Nexus

So google released this file called : mysid-icl53f-factory-65895fa8.tar
Inside of it is a file with no extension called mysid-icl53f-factory-65895fa8
Can someone (for the love of God) tell me what I need to do with this thing? I want to revert completely back to stock so I can get rid of the OTA nag that is popping up every 10 minutes on my phone. (Yes I am rooted and running Revolution HD w/the latest custom kernel he has posted in that listing, it is still popping up).
Could someone tell me how I can revert back to Stock on Verizon Wireless LTE Please?
Thank you!!
P.S. I did do a search, I did see the how to for the GSM version. he's talking about all kinds of files for radios and whatnot that are not in the package I posted up top of this post. The files he has are not compatible with LTE version.
Do I just go in and fastboot the file that doesn't have an extension in the tar file? Do I fastboot -w the tar file? Do I shoot myself in my foot twice, hop around in a circle yelling ow ow, then do it?
***EDIT*** SOLVED
Ok so what I did was go to rootzwiki Some of the guys over there shed some light.
The deal is this, if you download the file from google's website you get a tar file. If you are running windows 7 64 bit and using Winrar (I'm not sure which is the culprit) when you open the .tar file it contains a file with no extension.
What you do is extract that file, rename it whatever and ADD the extension .ZIP to it.
Then you can unzip that file and inside you have all the .img files you need to fastboot.
So to revert back to stock LTE you do this:
fastboot flash boot boot.img
Fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
this will bring you back to full stock with the latest version of the OS.

shameless bump

This is a good question. Have you tried posting in the Developer's thread where you downloaded the ROM?

Related

Where can I download the original recovery image?

Please don't shoot me down, I have tried extensively searching and am not able to find this.
I need to find the original HTC/Sprint recovery image for the Evo. I can find an original PC36IMG.zip, but it won't allow me to unzip it or view the contents, and I'm not looking for all the other stuff in that ... JUST the original recovery image.
Can anyone point me in the right direction?
Thank you!
Just a guess, but I think you can take a 2.2 based PC36IMG.zip, use 7zip to extract it (Windows doesn't seem to want to open it with built in zip support, but 7zip works great). Then extract the txt document and the recovery.img and zip them in a new PC36IMG.zip. You'll want to get confirmation from someone more experienced then I, but I think that's all you have to do.

How to extract system.img

Hi all,
I am trying to develop a rom but I came along this difficulty: I can't find the sysyem.img. I tried to download a .zip file, only the folder named "system" came in it. And I tried it with a .exe and looked in "%TEMP%" no luck either...
Can anyone explain how I should extract the system.img?
Thanks in advance.
I guess your referring to a nandroid backup really. When you download a rom, it comes in a zip file which you can flash and has only a boot.img file (I think, can't remember off top of my head) so it can boot. It doesn't have anything else. You only see a system.img file when you do a nandroid backup. Everything that is in the system.img file is still the same as the system folder in a zip file.. more or less.
If you do have a system folder, it is possible to convert it using the HTC Kitchen
http://forum.xda-developers.com/showthread.php?t=633246
That should help heaps with ROM development
Can you please explain to me how I can convert the system folder, I don't have a clue.
Convert it how? How do you want to convert the system folder? And why? Might help us out more you know.
On "Theunlockr" (My guide for making a rom) It says
"If you have a .zip file, you can unpack the system.img and boot.img"
I only have the boot.img and a system folder!
And it also says: "If you have a .exe, run it until the first screen and then go to run and type %TEMP% and a rom.zip should be here"
in both cases it is not the case.
So, can anyone help me out please?

[Q] [Help] Missing bloatwareapps for OTA

Hello,
I recently uninstalled some (system / T-Mobile) apps with Titanium Backup. And I did not make a backup first. The phone still runs fine but the OTA fails.
I tried so far:
- RUU 1.28 -> does not work, because system is already 1.29
- find rom.zip and unpack -> Ok, but cannot unpack system.img, unyafs fails.
The file which the OTA misses, according to logfile is named: 4661_TMODE_Music_One.odex
If someone could sent me this file or upload it somewhere I would be thankful.
There is a good chance that there are more files missing, but the log stops after the first fail.
I see in the system.img that there are at least 4 files with similar names:
4661_TMODE_Music_One.odex
4661_TMODE_Music_One.apk
4662_TMDE_Games_One.odex
4662_TMDE_Games_One.apk
If anyone knows how to unpack these, this would also helpful.
deleted
I think the best way to get all your bloatware back is to lock the bootloader and then flash the 129 RUU. Here is the link for the RUU if its T-mobile uk.
http://www.filefactory.com/file/6y1...Radio_1.1204.105.14_release_260731_signed.exe
Once your back to stock you can unlock again with your unlock token, flash cwm and make a stock nandroid backup.
If you need a file factory password pm me.
No, it's T-Mobile Germany, so I guess this will not help.
At the moment I'm trying to unpack the files from the system.img, but none of the methods described in the forums are working.
It is almost crazy, I can see the filenames and contents (lots of "PK" headers for instance) within the system.img but I've no idea how to extract them.
Get in touch with football. He might be able to get the RUU for you.
ghori1989 said:
Get in touch with football. He might be able to get the RUU for you.
Click to expand...
Click to collapse
Ok, tried that, waiting for the reply.
Meanwhile I'm able to mount the system image with some modifications as ext4 image and copy the contents. If there is an interest for this, I propably could write some tool to make this automatic.
Anyway, it did not help me, because the versions of the files in the image do not match the ones expected from the OTA.

[Q] Extract Boot.img from Stock ROM

Hi guys, I would like to extract boot.img from a Stock ROM without the need of installing it on my (Galaxy Note 2 T-mobile). All I found on the internet is how to extract it from an installed ROM.
So I would like to:
1. Extract the boot.img
2. Then flash it through ODIN to my custom ROM (Jedi Master 14)
Thanks in advance and please help me :crying:
Why would you do that?
Hastily spouted for your befuddlement
I don't know how you going to use boot.img to fix your problem. But the .md5 rom files are just zipped files. unzip and you will find the boot.img file. Are you sure that this will fix your problem?
Are you trying to change your boot image?
Use a tar archive program (7-Zip, Winzip, Winrar, PKZip, this format is pretty universal) to extract what you need from the official Samsung ROM images. (Check out sammobile.com if you haven't already, you will need to register.)
You might get some error message about the end of the archive, that's normal and due to the presence of the MD5 hash at the end of the file, which most programs will be able to work around nonetheless.
Repack the relevant file with a *nix tar binary, or under Cygwin on a Windows machine. (YMMV, but those are the two only ways I've managed to have the files work with Odin.)
Reboot phone to download mode and flash with Odin as usual.
Done.
Thanks a lot. Thats exactly what I am looking for.
Sent from my SGH-T889 using xda app-developers app
Darkshado said:
Use a tar archive program (7-Zip, Winzip, Winrar, PKZip, this format is pretty universal) to extract what you need from the official Samsung ROM images. (Check out sammobile.com if you haven't already, you will need to register.)
You might get some error message about the end of the archive, that's normal and due to the presence of the MD5 hash at the end of the file, which most programs will be able to work around nonetheless.
Repack the relevant file with a *nix tar binary, or under Cygwin on a Windows machine. (YMMV, but those are the two only ways I've managed to have the files work with Odin.)
Reboot phone to download mode and flash with Odin as usual.
Done.
Click to expand...
Click to collapse
and how do we do?
i flash the file without pepacking it so i can t bot, kernel error!
I'm really annoyed if you can explained to me how do we do it
thx

firmware

so i finally decide today to try and update firmware so I can run kk,so this is what i am doing.using adb I type fastboot oem reboot RUU which says it was ok then htc screen pops up.then I dl the newest firmware and with out unzipping I drop into my adb file then I type fastboot flash zip firmware.zip{i did rename file when i put into adb] then adb says it couldnt load file.Ive tried unzipping it and still coming up with eras.So im not sure what i am doing wrong
Send it twice as per santod's instructions. Hopefully that's just your case.
Sent from my HTC6500LVW using Tapatalk
Could also be if you renamed it firmware.zip windows hides extensions so it could actually be named firmware.zip.zip
Don't unzip it and if you did. Go ahead and delete the unzipped one because you broke it. Download the zip again and then run the commands again. This time make sure not to unzip it and if you need to remove the boot.img simply open the archive and delete it that way. Do not unzip it.
Sent from my One using Tapatalk
I actually updated the second post in my thread with a firmware zip minus the boot.IMG a day or two ago.
Try that if you need one without it.
What are the errors?
Make sure USB debugging is enabled in developer options in settings.
Sent from my One using Tapatalk
I will give your guys suggestions when I get back home..thanks guys for the info.I must say the HTC forum on xda you guys are very respect full and quick to respond compared to other people on this site for different phones
so the problem for me was that i was renaming the firmware.zip which i should have just saved it to just firmware just like bd619 said.Thanks again

Categories

Resources