I like to think I've got a pretty good grasp of how things work, even if I don't know the specifics. I'm hoping someone can give me an answer on this one - I'm sure it's straightforward once you know!
With my previous phone, an HTC Desire, when I wanted to flash CM, all I had to do was unlock the bootloader (S-OFF), root and flash the .zip file. However, with this phone it seems that it's not so simple - looking at the dev threads for CM-based ROMs they pretty much all require the boot.img to be extracted and flashed via ADB, and then the rest of the ROM flashed from the .zip file.
And, probably related - why are all the stock-based ROMs packaged as .ftf files needing the use of Flashtool? What's the reason they can't be packaged as a .zip and flashed through recovery?
What's different between the phones? I'm not trolling, I'm keen to learn
I'm no expert, but I think the ftf package contains additional informations such as phone model number, branding, etc which is not possible to include in zip archives.
The only difference is that this phone doesn't have a dedicated partition for the recovery. That's why all recoveries are included in kernels(ramdisk).
Sent from my C6603 using xda premium
Related
Hey friends.
I have some questions which i can't seem to find the answer to.
1. what's all that deal with SPL? what exactly is that and why do i need to flash it before flashing the radio version? what do i have to watch out from in order to not bricking my phone?
2. I wanted to flash a radio version from ERE36B that was posted on modaco site.
I downloaded the zip, copied to the sdcard, flashed it using the amonra 1.7 recovery. it said that it was successfully flashed but the radio version hadn't changed. what did i do wrong? I wanted to flash using fastboot but there were no .img files posted. only after extracting the zip files there is an img file inside along with some other files that may be important.
3. why are there different versions of superboot for each build? I mean, after I used superboot once and rooted my phone - I won't have to use it ever again.
no?
many thanks and sorry for the long post.
1. SPL stands for Second Program Loader. but you wont have to worry about it on the Nexus One. Its a different story for the G1.
2. If flashing the radio is successful then your baseband should be 4.04.00.03_2. And you might already had that radio if you just recently bought your phone.
3. Superboot version is not different. As long as you flash a rooted version of the rom then you will still retain root. But if you flash back to a stock rom, then you'll lose root. So always use nandroid to backup.
Thanks for the answer
So what exactly are the risks ?
is it possible to brick the nexus one or it's completely impossible?
10x!
ive been tryin to flash theses roms i can do the one click but i tried the other ones and im using rom manager and i install it and boot in recovery mode and it comes up with errors
What errors?
Flash this
http://forum.xda-developers.com/showthread.php?t=818439
Then flash this
http://www.ponack.net/designgears/Cognitionv2.2BETA9_ODIN.zip
You should be good.
well the cognition roms work but the other ones dont they dont have the one click
adamcoop22 said:
well the cognition roms work but the other ones dont they dont have the one click
Click to expand...
Click to collapse
What one click are you referring to? If you are talking about odin one click, the only thing you should be using that for is going back to stock before flashing a rom. If a rom is flashable through clockwork than you would just put it on your internal sd card and follow the instructions for flashing through Rom Manager. If it is a rom that is supposed to be flashed with odin you would have to open up the zip file you downloaded and enter the appropriate files into odin.
CLgcsi said:
What one click are you referring to? If you are talking about odin one click, the only thing you should be using that for is going back to stock before flashing a rom. If a rom is flashable through clockwork than you would just put it on your internal sd card and follow the instructions for flashing through Rom Manager. If it is a rom that is supposed to be flashed with odin you would have to open up the zip file you downloaded and enter the appropriate files into odin.
Click to expand...
Click to collapse
WELL **** I flashed a rom now im stuck on congnition rom and i cant flash another one can u help
You need to be more descriptive if you want people to figure out a solution to your specific problem. Your post amounts to "I flashed a rom, I'm having problems, vague reference to rom manager, help guys".
Here's what we need:
1. What version of Android are you trying to flash?
2. What version are you currently running?
3. What modifications have you done?
4. What is the specific error you are getting?
5. What is the EXACT process you are using to try to flash the new rom?
READ READ READ READ READ, THEN READ SOME MORE!
you obviously have not read enough. there are 2 versions of ODIN we use for our phones:
One click ODIN which is simply a prepackaged version of the regular ODIN configured with the appropriate files that ODIN needs to flash our phones with it....they are packaged up by a developer named DesignGears. not every rom is going to have a one click odin....
there is also regular ODIN which requires you to have the appropriate files associated with your rom (kernel, pit file, modem, csc file, and rom), sometimes devs will package as much of that as possible into one or 2 files to flash in ODIN
you need to spend some time learning how to use these or just use the one click and go back to stock, then leave your phone alone. seriously, freaking out on a forum is not the right way to go about getting help for your phone.
calm down and give up the info that modest_mandroid has requested. none of us magically know what the heck you are talking about when you spout out random things like help, i flashed something and now i cant do anything else
I have not flashed a ROM yet, but when I do how would I go back to stock? I made a CWM backup of being stock rooted, but I want to know of another way to go back. When I had the AT&T Galaxy S2, all I had to do was flash the tar file in Odin. I searched the development section and only found modified KJ4(2.3.5) and KKA(2.3.6) ROMs. I have the Polish Note if that matters.
Edit: I think I may have found the right way to go back to stock KKA. Just by placing the stock zimage using Chanfires method ^_^
Edit2: Meh figured it out
Sent from my GT-N7000 using xda premium
Edit3: Need confirmation on correct way to return to stock, as others have the same question.
Get the stock rom and reflash it.
ericyang said:
Get the stock rom and reflash it.
Click to expand...
Click to collapse
Yeah I definitely know that part, I'm more concerned about the way of doing it.
I heard that flashing through Odin would cause the yellow triangle as it would set off the flash counter... Can please you link me to the stock ROM that is flashable through Odin if this isn't the case? OR an alternative method besides the one I posted above.
I do in fact have tha same questions. I even went off topic in a ROM release thread about it.
I'm a longtime HTC user and with long time i mean since like 2002ish. I have no fear to mess around with HTC stuff since I know my way around and know exactly how to brick it, if I really want to ;-)
Things look different with the Note thought. The recovery doesnt stick but is kernel dependant, Odin seems to be similar to HBOOT but shouldn't be used since it tells Sammy what one did to its device. Flashing can be done by this that or another way, it all looks so weird and chaotic to a HTC camper... lol.
Sent from my GT-N7000
schaggo said:
I do in fact have tha same questions. I even went off topic in a ROM release thread about it.
I'm a longtime HTC user and with long time i mean since like 2002ish. I have no fear to mess around with HTC stuff since I know my way around and know exactly how to brick it, if I really want to ;-)
Things look different with the Note thought. The recovery doesnt stick but is kernel dependant, Odin seems to be similar to HBOOT but shouldn't be used since it tells Sammy what one did to its device. Flashing can be done by this that or another way, it all looks so weird and chaotic to a HTC camper... lol.
Sent from my GT-N7000
Click to expand...
Click to collapse
Hopefully we can get some clarification on the right method.
Sent from my GT-N7000 using xda premium
Goodm7sn said:
Cheers guys for the great info .
ive been following this thread for a while now , and i would like to suggest to the experts , if possible , to make a full step by step guide for how to revert to stock (including the whole stock kernel re-flashing process for different note models) bcos to be honest , i think many of us have this same question and are hesitated as the whole process sounds confusing.
i could be one of them as this is my first samsung device , coming from HTC Desire HD ,where flashing and development for samsung devices (as far as i know) is quite different from that on HTC devices.
Thank you again for the efforts , would be highly appreciated to get that guide post up.
Click to expand...
Click to collapse
dr.ketan said:
will post it soon
Click to expand...
Click to collapse
i think this thing is being worked on , all above is from this thread http://forum.xda-developers.com/showthread.php?t=1329360
Goodm7sn said:
i think this thing is being worked on , all above is from this thread http://forum.xda-developers.com/showthread.php?t=1329360
Click to expand...
Click to collapse
Yeah he did update it. That's where I got the idea about just using Chainfire's Initial Root Flasher and placing the zImage in that folder. On the bottom of the OP, he put
Now How I can revert back to Stock ROM/Unroot (In case of replacemet may i need)
I you have Just rooted only but not added CWM - Just Download this Extract - Execute - Rum Me unroot.bat
If You have Root + CWM - then first find out original stock kernel (zImage file)
Now place this file in zImage folder, n repeat procedure(Initial CFRoot Flasher), which you have done at time of pushing CWM by selecting I am rooted already
Now unroot with above said unrooting tool.
HTC Chris said:
Yeah he did update it. That's where I got the idea about just using Chainfire's Initial Root Flasher and placing the zImage in that folder. On the bottom of the OP, he put
Now How I can revert back to Stock ROM/Unroot (In case of replacemet may i need)
I you have Just rooted only but not added CWM - Just Download this Extract - Execute - Rum Me unroot.bat
If You have Root + CWM - then first find out original stock kernel (zImage file)
Now place this file in zImage folder, n repeat procedure(Initial CFRoot Flasher), which you have done at time of pushing CWM by selecting I am rooted already
Now unroot with above said unrooting tool.
Click to expand...
Click to collapse
i have afew questions about that ,
where and how can i find the specific zimage for my device ? i understood that its in a compressed file extracted with 7-zip , but how can i get that compressed file ?
also , what if i had another type of ROM installed (NON stock) , how can i flash the original stock rom back (since i will not be be rooted, wont be able to restore NAND backups)??!
in HTC devices (i had Desire HD) , reverting to stock rom is simplified by flashing the "RUU" files , which were found in a dedicated thread.
This whole samsung diferences is really confusing me
thanks alot for any help.
cheers.
Goodm7sn said:
i have afew questions about that ,
where and how can i find the specific zimage for my device ? i understood that its in a compressed file extracted with 7-zip , but how can i get that compressed file ?
also , what if i had another type of ROM installed (NON stock) , how can i flash the original stock rom back (since i will not be be rooted, wont be able to restore NAND backups)??!
in HTC devices (i had Desire HD) , reverting to stock rom is simplified by flashing the "RUU" files , which were found in a dedicated thread.
This whole samsung diferences is really confusing me
thanks alot for any help.
cheers.
Click to expand...
Click to collapse
This is my ass-umption as I am still waiting for other responses as well.
In order to revert to stock you have to download the Initial Flasher.zip from Chainfire.
Then download your Kernel from the first page. http://forum.xda-developers.com/showthread.php?t=1331784 The zImage is taken from extracting your Kernel, whether it be KK1, KJ4, KKA, etc...
You place that zImage in the files folder and click "already-rooted.bat" *if you are coming from another ROM.*
Once that is done, you run the unrooting tool from Doomlord.
This method may work if you are able to access your device. As in your Android OS is up and running. What about a bootloop on a ROM/Kernel without a custom recovery built in confused. How would you go on from here?
On a part-bricked or bootlooping or otherwise fukkered HTC I would fire up my (bien sure as first thing) flashed ENG HBOOT, put it in FASTBOOT mode and simply a) fastboot boot c:\path\to\file\recovery.img or b) fastboot flash recovery c:\path\to\file\recovery.img and done. No brick from here, bc I a) always can restore a nandroid from here or b) always have a ROM ready on the SD or I could put it there using the mount usb option in the recovery, or heck, even by ADB PUSH. But on a Samsung...
Hi, everyone. I believe these questions are not covered in this forum yet.
Is it possible to just flash kernel from FTF file?
Is it possible to convert or package kernel (IMG / ELF) file to FTF file?
If above 2 are possible, does that mean that kernel can be flashed from flashmode instead of Fastboot mode & thus eliminating the need to unlock bootloader?
Are the firmware & kernel of Xperia T / TX / TL / V interchangeable?
Is there any risk trying to flash other firmware or kernel or anything that is not compatible?
Is there any risk trying to flash kernel (IMG /ELF) file & custom ROM with locked bootloader?
Is flashing stock advanced kernel equivalent to flashing stock kernel?
I believe these questions are worthwhile to be added into the All In One thread as well.
Appreciate for the knowledgeable input from u all. Thx in advance! =)
SCC2002 said:
Hi, everyone. I believe these questions are not covered in this forum yet.
Is it possible to just flash kernel from FTF file?
Is it possible to convert or package kernel (IMG / ELF) file to FTF file?
If above 2 are possible, does that mean that kernel can be flashed from flashmode instead of Fastboot mode & thus eliminating the need to unlock bootloader?
Are the firmware & kernel of Xperia T / TX / TL / V interchangeable?
Is there any risk trying to flash other firmware or kernel or anything that is not compatible?
Is there any risk trying to flash kernel (IMG /ELF) file & custom ROM with locked bootloader?
Is flashing stock advanced kernel equivalent to flashing stock kernel?
Click to expand...
Click to collapse
These questions have been answered
1) yes, stock only
2) No
3) No, to flash custom kernel you need fastboot, hence you need unlocked bootloader
4) No, but you can try and see
5) There is always a risk when you flash something to your phone.
6) No risk, because without an unlocked bootloader it wont work*
7) No, Stock advanced kernel is a custom kernel based on stock with cmw and a few other things incorpprated, whilst stock kernels are stock kernels.
EDIT
* from number 6) you may soft brick the phone, but just flash a stock based rom back and it will work again. The problem will be with flashing a rom that needs a custom kernel that our phone will not support because you have a locked bootloader.
SCC2002 said:
I believe these questions are worthwhile to be added into the All In One thread as well.
Appreciate for the knowledgeable input from u all. Thx in advance! =)
Click to expand...
Click to collapse
Why didnt you ask in that thread then? I have spent the time to add them to the FAQ there...
gregbradley said:
These questions have been answered
1) yes, stock only
2) No
3) No, to flash custom kernel you need fastboot, hence you need unlocked bootloader
4) No, but you can try and see
5) There is always a risk when you flash something to your phone.
6) No risk, because without an unlocked bootloader it wont work*
7) No, Stock advanced kernel is a custom kernel based on stock with cmw and a few other things incorpprated, whilst stock kernels are stock kernels.
EDIT
* from number 6) you may soft brick the phone, but just flash a stock based rom back and it will work again. The problem will be with flashing a rom that needs a custom kernel that our phone will not support because you have a locked bootloader.
Click to expand...
Click to collapse
Thank u so much for ur answers. Sorry for didn't manage to find them. =)
1 - 4. My questions arose are bcoz that in order to root firmware later than 7.0.A.3.195 needs to downgrade to 7.0.A.1.303. However, I'm owning a Xperia TX, which having the firmware of 7.0.A.3.197 & the earliest firmware I found for Xperia TX is 7.0.A.1.307. That's why I am not sure whether Xperia T's 7.0.A.1.303 firmware works on Xperia TX.
5. Well, what I mean is additional risk from usual flashing. =)
7. If that's the case, does installing CWM recovery with the phone rooted but locked bootloader resulting in a custom kernel?
Why didnt you ask in that thread then? I have spent the time to add them to the FAQ there...
Click to expand...
Click to collapse
Well, I was thinking that these questions are better asked on a separate thread then. Anyway, thx a lot for compiling the All In One thread. It's very useful. More details can be added though. =)
SCC2002 said:
Thank u so much for ur answers. Sorry for didn't manage to find them. =)
1 - 4. My questions arose are bcoz that in order to root firmware later than 7.0.A.3.195 needs to downgrade to 7.0.A.1.303. However, I'm owning a Xperia TX, which having the firmware of 7.0.A.3.197 & the earliest firmware I found for Xperia TX is 7.0.A.1.307. That's why I am not sure whether Xperia T's 7.0.A.1.303 firmware works on Xperia TX.
5. Well, what I mean is additional risk from usual flashing. =)
7. If that's the case, does installing CWM recovery with the phone rooted but locked bootloader resulting in a custom kernel?
Click to expand...
Click to collapse
1-4) The 303 and 307 firmware are basically the same FW. 303 for the T and 307 for the TX. also 195 is for the T and 197 is for the TX.
5) If you flash something that is not compatable then you can either get various results ranging from no apparent bugs, to slightly buggy formware, to soft bricks or inthe worst case a hard bricked phone.
7) No, installing recovery is seperate to having a custom kernel with recovery incorported within it.
gregbradley said:
1-4) The 303 and 307 firmware are basically the same FW. 303 for the T and 307 for the TX. also 195 is for the T and 197 is for the TX.
5) If you flash something that is not compatable then you can either get various results ranging from no apparent bugs, to slightly buggy formware, to soft bricks or inthe worst case a hard bricked phone.
7) No, installing recovery is seperate to having a custom kernel with recovery incorported within it.
Click to expand...
Click to collapse
5. Hard-brick. Does that mean the phone is irrecoverable any more? In what case would result in this condition?
Oh yea, another question. In this case, downgrading the firmware is required to root the phone. So, does downgrading the kernel only, but not the firmware possible to give the same effect?
SCC2002 said:
5. Hard-brick. Does that mean the phone is irrecoverable any more? In what case would result in this condition?
Click to expand...
Click to collapse
Hard brick means your phone is properly FUBAR'd
SCC2002 said:
Oh yea, another question. In this case, downgrading the firmware is required to root the phone. So, does downgrading the kernel only, but not the firmware possible to give the same effect?
Click to expand...
Click to collapse
Maybe, try it and see. But i think a whole flash of the firmware is needed.
SCC2002 said:
Oh yea, another question. In this case, downgrading the firmware is required to root the phone. So, does downgrading the kernel only, but not the firmware possible to give the same effect?
Click to expand...
Click to collapse
I had read that for some other devices (I think Xperia P) flashing just the old kernel, then rooting then flashing the new kernel works to keep root without flashing system folder or anything else. Give it a try, worse case you just flash again full ftf and start over.
gregbradley said:
Hard brick means your phone is properly FUBAR'd
Maybe, try it and see. But i think a whole flash of the firmware is needed.
Click to expand...
Click to collapse
Spectre51 said:
I had read that for some other devices (I think Xperia P) flashing just the old kernel, then rooting then flashing the new kernel works to keep root without flashing system folder or anything else. Give it a try, worse case you just flash again full ftf and start over.
Click to expand...
Click to collapse
Happy New Year, guys! Thx for the answer. I've tried just flashing the kernel. Doesn't work. Succeeded rooting after flashing the whole firmware. =)
Anyway, now I'm stuck in the process of upgrading the firmware. I can't seem to find a stock ROM for Xperia TX (LT29i) 7.0.A.3.197 firmware. I just gone through all the hard ways to create a stock ROM myself & successfully flashed it. Perhaps bcuz of the improper build, my WiFi can't be turned on & there might be other problems coming up later.
Now I am also worrying that would it cause any prob to my phone. I followed this guide to create the ROM.
http://forum.xda-developers.com/showthread.php?t=1931189
& I took the META-INF folder from this custom ROM.
http://forum.xda-developers.com/showthread.php?t=2040989
Plz kindly help that if there's any resource to the stock ROM or any way to fix this, as well as have a look if there is any side effect from flashing that ROM. Many thanks! ><
Wifi not working is because you have to copy and rename the /system/lib/modules/prima/prima_wlan.ko file to just /system/lib/modules/wlan.ko
I use this for making my own versions: http://forum.xda-developers.com/showthread.php?t=633246
Spectre51 said:
Wifi not working is because you have to copy and rename the /system/lib/modules/prima/prima_wlan.ko file to just /system/lib/modules/wlan.ko
I use this for making my own versions: http://forum.xda-developers.com/showthread.php?t=633246
Click to expand...
Click to collapse
Really? That's all? There's no other side effect from the way that I built the ROM? Am I building ROM with a proper way?
Do I've to keep the original file at the original location? Why is it that we need to modify this, just wondering?
Btw, I heard that there's a prob with MAC address with this method from another forumer. Is this true?
SCC2002 said:
Really? That's all? There's no other side effect from the way that I built the ROM? Am I building ROM with a proper way?
Do I've to keep the original file at the original location? Why is it that we need to modify this, just wondering?
Btw, I heard that there's a prob with MAC address with this method from another forumer. Is this true?
Click to expand...
Click to collapse
I kept the other file in the original location. Not sure about any Mac address issue. Worked fine for my device. Not sure about the way you use to build the rom. I just use the android kitchen since its pretty quick and easy.
Sent from my Sony Xperia™ TL
I have a Canadian N4(910W8)and I want to change the baseband so I can try different Roms. How do I go about this? I'm guessing through Odin right? Where can I find a stock NJ7 ROM to do this? Thanks guys!
re: baseband.
yeroc1982 said:
I have a Canadian N4(910W8)and I want to change the baseband so I can try different Roms. How do I go about this? I'm guessing through Odin right? Where can I find a stock NJ7 ROM to do this? Thanks guys!
Click to expand...
Click to collapse
Firstly, if you change baseband your phone will not work with Canadian or
USA roms.
None of the twrp flashable zip file roms contains the baseband or bootloaders.
You need to keep the Canadian baseband which you already have.
What you will need to do is to save your kernel file so you can use it with the
USA zip file roms.
The kernel is located in the /System/ folder and the filename is "boot.img".
Copy that file to your internal sdcard before you do anything else.
Then after you download a usa zip file rom open it up with winrar/winzip
or other archiver and remove the boot.img in the zip file and replace it with
the boot.img you have saved in your internal sdcard before flashing.
Once you do that you can safely flash the usa zip file rom of your choice.
I never advise anyone to use a different carriers rom, there are many con's
against doing so and not many pro's. But go ahead and give it a try.
Good luck!
Thanks for the helpful info! On my note3, I always flashed tmob roms with no issues, but the note 4 is new so I didn't know exactly what would work or not. Might give this a go later on! Thanks again!
I find sys>kernel>boot_adsp> the file called "boot" which is only 4kb in size. Is that what I'm looking for? Does not have "IMG" behind the "boot"
Hi.... I was wondering the same about the NJ7.... I've flashed 2 TMobile roms so far... Darthstocker & Hyperdrive.... As long as you flash the Starkissed Kernel it boots up fine... Without it you just Bootloop....