Hey, guys.
I own a Samsung Galaxy Grand Quattro (Grand Win) I-8552. I am trying to update it to 4.4. I found a valid (looking) zip that needs to be flashed.
But now I can't use CWM, which the ROM needs (my phone is unsupported). Can't use Odin, 'cause it needs a *.tar extension or something like that, and converting a zip into a tar file doesn't work when it has a META-INF folder and *.img extension file.
Every page I have visited about installing CWM on unsupported devices requires a model-specific file from the website. So basically they are saying, "How to run CWM on unsupported devices, but requires a supported device."
Please !
EDIT: Never mind, I derped. How do I kill the thread?
Related
Hey Guys,
I'm in need of some really n00b friendly advice.
When you flash a new ROM (i.e. CM9) in CWM the tutorials tell you to flash the file named Update.zip. My problem is that I can't seem to find one in the zip file I downloaded for my xperia mini.
I downloaded FXP131, and found the zip file to contain a boot.img, which will be the kernel. And 2 other folders named META-INF and System.
I know how to flash the kernel and expect it was just left in there for easy transportation.
But where in the world is 'update.zip'?
Am I meant to unpackage the kernel then re-zip the META-INF and System folder and then call that 'Update.zip'?
I've flashed roms for some of my other devices before, but they've always used flashtool or samsungs flashtool.
Please help me guys, I don't like sounding this inexperienced
update.zip
I'm wondering if the ROM I am trying to flash needs to be renamed as update.zip in order to work. It is krook's v.6 of JB for the Lenovo K1 tablet. Since the download site has to distinguish between wifi and 3G versions, as well as nvflash versions there are a number of different filenames, however does it need to be renamed after putting it on my SD card?
Generally speaking "update.zip" is used as a generic name. For example the update.zip I just flashed is actually named "rascarlo_maguro_ota_2012-11-01.zip". When you flash a custom ROM in a custom recovery you should be able to browse & flash whichever file you need.
The FXP131.zip file that contains the boot.img and 2 other folders named META-INF and System is the "update.zip"
solved
My problem was an incomplete download. I compared file sizes, and checked md5sums and determined the correct ROM and it is now in the middle of finishing the upgrade/optimization process.
Thx
Hello,
I tried to do a simple task which raise several problem and it start to drive me crazy, so here I am, asking for help. The subject may have been already mentioned, but can't find an issue with the galaxy s3.
I work with ubuntu 12.04 and Odin on win7. My GS3 has XXELL4 baseband, and 3.0.31-742798 kernel version.
I need to load and run a custom module (let's say a "hello world" one for begin) on the galaxy S3.
I compiled it through a Makefile with the toolchain from the ndk package (
Code:
path_to_ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-
and the source code from the samsung web site (GT-I9300_JB_Opensource_Update8.zip).
Obviously, when i tried to insmod my module, I've got some compatibility error like
Code:
Exec format error
.
The fact is that the kernel from website is not the same as the phone one.
So I tried to put the kernel from the website on the phone
I compiled it with the same toolchain and I received a zImage file in result. But what to do with this file ? I extracted a boot.img from the phone with Odin and split it (with perl script stuff) to use the extracted files with my compiled zImage for reconstruct a new boot.img. But since fastboot is not available on GS3 (or I miss something) I can't simply
Code:
$ fastboot flash boot boot.img
, and need to use Odin again. So I replace the boot.img from odin's backup folder on my PC with my boot.img. But the nandroid.md5 file raise an error. Am I doing it wrong or too complicated ? If I can correct the md5 error, is that my module will work ?
I also tried to compil my module directly with the kernel from the phone but didn't manage to extract the kernel files to do it. Stuck with a boot.img. Same with the stock kernel from http://forum.xda-developers.com/showthread.php?t=1646610
I made a lot of research but don't find any concrete solutions to my simple task. Maybe I miss something or looking too deep.
Is there a more simple way to run a custom module on the GS3 ?
sorry for my english
Hello and welcome to xda!
You do not have to use odin to flash your kernel, you can do it via custom recovery too.
Just get an simple cwm package of another kernel for s3 and replace the boot.img in the zip.
I attached a simple empty cwm package, just drag your boot.img to the root of the zip with winrar or something.
hsrars-d said:
Hello and welcome to xda!
You do not have to use odin to flash your kernel, you can do it via custom recovery too.
Just get an simple cwm package of another kernel for s3 and replace the boot.img in the zip.
I attached a simple empty cwm package, just drag your boot.img to the root of the zip with winrar or something.
Click to expand...
Click to collapse
Thanks
I've got also a md5 error when i tried to restore with cwm, since I have no md5 file in my folder. Do I need to generate one ? how ?
EDIT: so a generate a md5 file with md5sum, but still have the Exec format error when i try to insmod my module.
ok, im not good with kernel stuff/modules so i cant help you any further...
try to find someone that has experience with kernel modules
edit: found something with google, not exactly for s3 but the error is pretty common:
http://www.linuxquestions.org/questions/linux-kernel-70/insmod-error-version-magic-4175424366/
http://forum.xda-developers.com/showthread.php?t=444338&page=1
http://stackoverflow.com/questions/...for-android-unknown-relocation-27-when-insmod
Why are you posting in this section?
Glebun said:
Why are you posting in this section?
Click to expand...
Click to collapse
well ... I don't yet have access to other section. But If someone could move the thread in a more appropriate one I'll thanks him.
Yes, you do. Questions go in the Q&A section, obviously
firstly i request all moderators of xda in grand 2 forum,
as i am unable to post on developement section,
i am posting the thread here..
plz move it to developement section.
ok now back to topic,
try at your own risk!
i will not be responsible if anything happens to your phone
To all the users who have succesfully rooted grand 2,
there can be a way to install (flash) recovery on your phone!
i was exploring the system and i found a file in "/system" folder
called "recovery-from-boot.p"
i THINK this is the file that causes problem!
you may delete it or rename it...(renaming is safer)
once you delete it, you may flash custom recovery via ODIN
and even if the recovery gets currupted or if you cant boot into recovery, you can simply boot normally and restore the renamed or deleted file!!!
and then once again you may try to flash custom recovery from ODIN (as stock gets deleted as soon as you modify recovery-from-boot.p file)
press thanks if this post helped!
dindt find any file like u wrote.... plss provide specific path.. so we can try
Rakesh251 said:
dindt find any file like u wrote.... plss provide specific path.. so we can try
Click to expand...
Click to collapse
Its located here:
bro no such file is available.. this wont help to solve .and still custom recovery not available for grand2
how would u know that it won't help..
i only post threads as i know what i am doing.
the file which i uploaded up there is taken from MY PHONE ITSELF i.e galaxy GRAND 2..
and That FILE (recovery-from-boot.p) IS present on my phone and i m using Stock rom and not any other rom..
Same with me... none of them named exactly like you mention above.
Sent from my SM-G7102 using XDA Premium 4 mobile app
it only appears on a Stock UN-ROOTED firmware..
In order to inject custom CWM there isnt a necessity to root device.
so firstly we need to remove file that I mentioned in my previous post and inject recovery.
and via that recovery,
we can flash a custom kernel that automatically roots device!
vrushabh sutar said:
it only appears on a Stock UN-ROOTED firmware..
In order to inject custom CWM there isnt a necessity to root device.
so firstly we need to remove file that I mentioned in my previous post and inject recovery.
and via that recovery,
we can flash a custom kernel that automatically roots device!
Click to expand...
Click to collapse
Dude, if the FILE just appears in STOCK UNROOTED FIRMWARE , so how can we delete that.
Coz, to delete a /system file, we need ROOT access.
NOT POSSIBLE.
And in rooted version, the FILE is not available :victory:
00hacktheworld00 said:
Dude, if the FILE just appears in STOCK UNROOTED FIRMWARE , so how can we delete that.
Coz, to delete a /system file, we need ROOT access.
NOT POSSIBLE.
And in rooted version, the FILE is not available :victory:
Click to expand...
Click to collapse
Thank you for replying.
I know that it can't be deleted,
but one may understand the importance of that ".p" file and understand its working, as it plays a vital role in booting up recovery...
the only thing I wanna let users understand is that,
stock recovery includes that file and
it got deleted when rooted because the rooting package (eg. CF root) didnt contain the .p file
when I studied that strange file,
it consisted of mapping and accurate memory address as well as accurate size of stock recovery image in bytes,
so that whn new recovery gets flashed, it verifies with the .p file!
and talking abt modifying the .p file,
we must create a custom linux binary with zerglings and packed into .tar file which gets flashed to phone via Odin!
for build creation you can use this tool..
http://www.xda-developers.com/android/comprehensive-guide-to-the-android-build-process/?__utma=60652090.747738090.1398670920.1400078979.1400132113.21&__utmb=60652090.0.10.1400132113&__utmc=60652090&__utmx=-&__utmz=60652090.1400132113.21.12.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=163283131
So I found the reason behind this
It is a file used by Software Update Application to flash updates.
If you want proof go-to the data folder of the SOFTWARE UPDATER and there will be a 3mb file. Copy it to pc and open using winrar. You can see many files including boot.img.
So the author of this thread was about to update his/her phone when he found the file :thumbdown:
SO MYSTERY SOLVED
SCOOBY DOOBY DOOO
Sent from my SM-G7102
i didnt't get what you are on to...
i noticed that the Update Package (i.e the OTA) easily jumps over all the restrictions imposed by Bootloader(locked one) and gets easily flashed to the phone...
therefore the whole matter is now pointing out to the 'ro.build.fingerprint' as well as Verification of MD5 hashes linked directly to Flashing InstructionSet
Hi. I am a newbie in flashing phones. I am having a Lenovo A850. I was planning to flash it to Android Marshmallow (CynogenMod) . It was really hard to find the ROM. Somehow I managed to find one here: https://forum.xda-developers.com/le...rom-unofficial-cyanogenmod-13-lenovo-t3724018 . Once I downloaded it, I noticed that it is in RAR format. I tried entering CWM in my phone, and the RAR file doesn't show up. CWM probably does not support flashing RAR files.
What should I do now?
Maevinarsh said:
Hi. I am a newbie in flashing phones. I am having a Lenovo A850. I was planning to flash it to Android Marshmallow (CynogenMod) . It was really hard to find the ROM. Somehow I managed to find one here: https://forum.xda-developers.com/le...rom-unofficial-cyanogenmod-13-lenovo-t3724018 . Once I downloaded it, I noticed that it is in RAR format. I tried entering CWM in my phone, and the RAR file doesn't show up. CWM probably does not support flashing RAR files.
What should I do now?
Click to expand...
Click to collapse
What you do for a quick fix is to open the .rar file on your computer using a software like winrar, or 7zip. Then compress it using the software as a .Zip file then you can flash it easy as that.
Doing this is changing the file format all correctly with correct conversions so it should be alright. But be aware that this is a quick fix which I use and have success with. Not sure if it would work for you But it should, if it doesn't don't hit me ~ QAQ
Note that this is possible as well on phones using file manager with inbuilt rar,win support
How to flash only stock recovery? how to convert "recovery.img.lz4" to "recovery.tar"
Hi all,
I am fairly newb in installing custom ROMs, so apologies if Im misusing any terms. Some time ago I wanted to move a priv-app to system-app, without rooting. I managed to flash TWRP on my Samsung S8 G-950F, and from there moved private app to system app.
Now I would like to go back to the stock recovery img, but I don't know how or if it's even possible. The reason behind this is that my company is deploying Android Work Profile and it is detecting the custom ROM (I assume it is specifically detecting the custom recovery partition)
I tried to find the respective recovery.img for my current stock ROM, but was unable to find it. I can only find for older versions, and from what I read, you can't install older recovery with newer ROM
I can only find the full stock ROM, in .tar.md5 format. opening this with 7zip, I can see the recovery.img.lz4
How do I flash this without altering the OS partition?
Thank you in advance,
Rhaswar
@Rhaswar
Look inside here.
thank you @jwoegerbauer, I have seen this article and it mentions a file called recovery.tar
I don't have that, what I have is the recovery.img.lz4
Is there a conversion that can be done?
Thank you
@Rhaswar
Watch this video: https://www.youtube.com/watch?v=OfrMo1_Rgxc