Related
I've searched and read FAQs a lot already. I read the threads that XDA suggested before posting this.
I've been doing a lot of reading and I'm a little fuzzy. Want to root my gf's AT&T Captivate (JH7) and install Froyo for her but still a little unclear on exactly how everything fits together.
From what I've gathered so far I can use the update.zip method to install Clockwork Recovery and make a nandroid backup of her current configuration without even rooting it, right?
Then can I just flash whichever ROM I want? Will the ROM.zip update her to the correct modem/kernel at that time?
About using ODIN to restore - do I restore to the version she is on NOW or the version the phone originally shipped with, if different? And do I REALLY need to ODIN restore between ROMs or is a full wipe with CWM recovery enough?
Also read that CWM recovery doesn't work with Froyo at this time so can't do nandroid backups of Froyo ROMs?
Somebody catch me up... with my mt3g and mt4g I'm totally comfortable but this stuff is confusing me. I'm fairly comfortable with adb and already used it to sideload an app for her without rooting.
Thanks for your help guys.
I'm pretty new at this too so I'll try to answer what I can.
Before you try anything, just make sure you can get into recovery and download mode.
Recovery:
- Hold Vol Up + Vol Down + Power button.
- from adb type reboot recovery
- from Rom Manager, select the Reboot to Recovery option.
Download
- Hold Vol Up + Vol Down and insert the usb cable. This works for me. Getting Odin to detect it can be a bit tricky. I usually start Odin first, then connect phone.
- from adb type reboot download (I think)
From what I've gathered so far I can use the update.zip method to install Clockwork Recovery and make a nandroid backup of her current configuration without even rooting it, right?
Click to expand...
Click to collapse
Not sure to be honest. The way I do it is that I install Rom Manager from the market first. It will ask you for root though. I like this way better as you can download and install the appropriate update.zip from the app. Rooting is very very easy. You can use this tool:
http://forum.xda-developers.com/showthread.php?t=739304
Then can I just flash whichever ROM I want? Will the ROM.zip update her to the correct modem/kernel at that time?
Click to expand...
Click to collapse
To be safe, I only try ROMs that I find in the Captivate Development sub forum. Most of them can be installed with CWM. Place the *.zip in the root of your internal SD card, reboot into CWM and select the install .zip from card option. Don't freak out.
There is also a way to flash roms from Odin but I've never tried it to be honest.
About using ODIN to restore - do I restore to the version she is on NOW or the version the phone originally shipped with, if different? And do I REALLY need to ODIN restore between ROMs or is a full wipe with CWM recovery enough?
Click to expand...
Click to collapse
I believe it will restore to Samsung's stock version (I897UCJF6). Check this thread: http://forum.xda-developers.com/showthread.php?t=731989
Remember that this is only for the Captivate. It is safer to do a full restore whenever you are trying a new rom. The only exception, I think, is when you are upgrading versions (say, Darky's 7.8 to 8.0)
Also read that CWM recovery doesn't work with Froyo at this time so can't do nandroid backups of Froyo ROMs?
Click to expand...
Click to collapse
I always install it using ROM manager and it works fine.
Now, from what I've been reading and doing this week, I learned that apart from the ROM, you can also flash the kernel and model separately, in case you have specific needs. For instance, I flashed glitterball's kernel to overclock the phone. Just remember that 2.1 Roms need 2.1 kernels and modems, the same applies for 2.2. Here is a list of modems: http://forum.xda-developers.com/showthread.php?t=835272
I'm currently trying out the TLJL3.
Remember that there are many ways to get to Rome. Also, use Titanium Backup to save your apps.
tl;dr:
1. Root.
2. Install CWM.
3. Verify that you can access recovery and download mode.
4. Download ROM (CWM .zip installable).
5. Read read read.
Much more detailed guide:
http://forum.xda-developers.com/showthread.php?t=884364
LOADING CUSTOM ROMs
Phateless said:
I've searched and read FAQs a lot already. I read the threads that XDA suggested before posting this.
I've been doing a lot of reading and I'm a little fuzzy. Want to root my gf's AT&T Captivate (JH7) and install Froyo for her but still a little unclear on exactly how everything fits together.
From what I've gathered so far I can use the update.zip method to install Clockwork Recovery and make a nandroid backup of her current configuration without even rooting it, right?
Then can I just flash whichever ROM I want? Will the ROM.zip update her to the correct modem/kernel at that time?
About using ODIN to restore - do I restore to the version she is on NOW or the version the phone originally shipped with, if different? And do I REALLY need to ODIN restore between ROMs or is a full wipe with CWM recovery enough?
Also read that CWM recovery doesn't work with Froyo at this time so can't do nandroid backups of Froyo ROMs?
Somebody catch me up... with my mt3g and mt4g I'm totally comfortable but this stuff is confusing me. I'm fairly comfortable with adb and already used it to sideload an app for her without rooting.
Thanks for your help guys.
Click to expand...
Click to collapse
Hmm... Most of your answers can be found in
http://forum.xda-developers.com/showthread.php?t=884364
The ROM file would contain a kernel and a modem that will update her current kernel and modem. She can flash the kernel and modem of her choice after installing a custom ROM without breaking anything.
For Backing up use Titanium Backup, u need to ROOT your phone using directions in the earlier link provided.
When using custom ROMs it is always better to do a full wipe and flash to stock and master clear, i.e JF6 (using Odin one-click, or Odin with 3-button) or JH7 using the DG version.
You can follow
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Update.zip file once installed would load CWM from which you can install custom ROMs. Once you install custom ROMs, they are always rooted, and you needn't root again. It's a one time thing.
Hope this resolves everything..
Thanks for your replies, guys, I'm actually very familiar with rooting and flashing. To clarify, I already know HOW to install a custom ROM, that's not the issue. I'm more concerned about compatibility once I start installing custom stuff, and about UNROOTING if I need to. It sounds like if all I'm doing is installing a custom recovery and then a custom ROM, I don't really need to worry about it.
I always opt for manual method through recovery as opposed to Rom Manager.
I would use SuperOneClick for the stock ROM as I've used it before without issues. Most likely I would use the update.zip method to install clockwork recovery so I can make a nandroid backup of her completely unrooted stock setup before proceeding.
I can get into stock recovery just fine but haven't tried download mode yet.
And yes I would ONLY flash ROMs for the Captivate specifically, unless someone manages to complete a port for Sense.
Sounds like your good to go then.
... and Odin is just the cheap and easy method to return the phone back to stock.
So if you ever need to give it back and need it restored this is the easiest method to do it. But I would suggest formatting the internal SD Card to make sure there are no remnants of you playing around with the phone.
avgjoegeek said:
Sounds like your good to go then.
... and Odin is just the cheap and easy method to return the phone back to stock.
So if you ever need to give it back and need it restored this is the easiest method to do it. But I would suggest formatting the internal SD Card to make sure there are no remnants of you playing around with the phone.
Click to expand...
Click to collapse
Agreed, will definitely do that.
I also heard that when using ODIN to restore to JF6 the OTA update to JH7 won't come back on its own?
lol yea.. but it doesn't matter unless you were wanting to keep it on "stock".
If your flashing or returning the phone your ok with keeping it on JF6.
If your phone came with JH7 and you have issues with Odin one-click, you might want to look at this guide, it has worked great for me and many others:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
How do I know what build number her phone is? I see references to build number 1010, but I don't know if this phone CAME WITH jh7 or if that was an update. I bought it used. If I try to restore to JF6 will that brick it??
EDIT - found it. She's a 1007. So if I used ODIN-3 to restore to JF6, how do I get back to JH7? Reading elsewhere it seems that a nandroid restore won't include the baseband?
Phateless said:
So if I used ODIN-3 to restore to JF6, how do I get back to JH7? Reading elsewhere it seems that a nandroid restore won't include the baseband?
Click to expand...
Click to collapse
Download the Mini Kies from here Download Center for SEG-I897ZKAATT.
Make sure the phone asks for USB on connection and select Kies mode when you plug into pc. Then open Mini Kies, it should recognize your phone and tell you an update is available. Follow the instructions from there.
cappysw10 said:
Download the Mini Kies from here Download Center for SEG-I897ZKAATT.
Make sure the phone asks for USB on connection and select Kies mode when you plug into pc. Then open Mini Kies, it should recognize your phone and tell you an update is available. Follow the instructions from there.
Click to expand...
Click to collapse
Ok cool, thanks for your help! Already downloaded Kies from the Samsung website.
About to flash her phone but saw something somewhere about backing up some *.nv file to preserve her IMEI# and stuff? Can you link me to a guide on that? Can not for the life of me remember where I saw that.
Hi guys,
I have a non-rooted Galaxy S running Froyo 2.2, Baseband version is I9000BOJP3, Build No is FROYO.BOJPB (note this is the official Froyo T-Mobile ROM)
I am able to use the '3 button recovery mode' however it is the 3e recovery mode rather better 2e version.
Can I still use the 3e recovery mode to flash a custom rom onto this phone, would I be able to go back & recover my phone in the event of something going wrong?
Thanks in advance
You need 2e to install unsigned zip files.
peachpuff said:
You need 2e to install unsigned zip files.
Click to expand...
Click to collapse
Cheers for that - don't suppose you know of a good handy guide to downgrade my 3e to 2e
gavk-xda said:
Cheers for that - don't suppose you know of a good handy guide to downgrade my 3e to 2e
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/showthread.php?t=788108
gavk-xda said:
Cheers for that - don't suppose you know of a good handy guide to downgrade my 3e to 2e
Click to expand...
Click to collapse
Well no idea about your ROM. So its on you . WARNING if something goes wrong I take no responsibility. READ IF ITS FOR YOU BEFORE YOU FLASH SOMETHING But you can flash a custom kernel.
I used Speedmod Kernel READ THE WARNINGS IN THE THREAD. To go back I backed up mine. If its only kernel you change should be easy to go back. But whole rom after you flash something custom not sure . Anyway this is how I did it.
1. Root is a must
2. Download SGS kernel flasher from Neldar
3. Backup your current kernel with the SGS kernel flasher (upload to email)
4. Optional Just in case backup your efs folder (SGS toolbox is nice for that) upload the back to your email
5. Flash the CWM version (with the SGS kernel flasher) you get on speedmod kernels thread.
6. Optional, now you can boot to the 2e recovery (Again SGS toolbox comes in handy with a shortcut and apply the goodies from speedmod or backup everything or flash what you wanted
the "upload to email" I added cuz there can always, even without this flashing go something wrong with your SD (internal or external) and is always good to have a backup. you can change email to PC etc
I completely agree with Pagot's instructions. SGS Kernel Flasher and SGS Toolbox give you all you need to swap kernels with confidence, then add CWM for Mods and you are now good to go.
I would suggest that if you don;t with to email the efs folder to yourself, upload it to Dropbox. I keep all vital backups for all of my devices there, so I can get to them at anytime, from any device.
Just want to start by saying this is a great forum, lots of information, and I've read alot of it, as there are so many twists and turns depending on your device.
Here is where I am at with my first time rooting/installing a custom rom
Started with stock Model GT-I9000M, Firmware version 2.2, Baseband version I9000UGJL2, Kernel 2.6.32.9 ([email protected] #3), Build number FROYO.UGJL2.
Step 1, I rooted my device using SuperOneClick
Step 2, backed up /efs and /st13 folders via ADB and BusyBox
Step 3, Backed up apps, sytem data via Titanium Backup
Step 4, Installed CWM from Android Market, Flashed ClockworkMod Recovery, selected 'Galaxy S i9000' when prompted
(Honestly this was confusing as I tried to select 'GalaxyS i9000 (MTD)' as I have the i9000M, but was prompted with the 'GalaxyS i9000 (MTD) does not have an officially supported ClockworkMod Recovery yet.')
Now have 'ClockworkMod 2.5.1.2' installed, but was unable to boot into it, as I found out I have 3e reovery, which doesn't allow the installation of zip files without signature verification. So after much reading I learned I can get around this my installing a custom kernel, searching this link I realized there is no CF-Root kernel for my UGJL2 build, after more reading I came across this link which said if on stock Froyo with 3e recovery to use the latest Super Optimized kernel. I now have Kernel version 2.6.32.9 [email protected]_8_3#1725, and am able to boot into CWM recovery.
Step 5, I am following the instructions below to complete the installation of my choosen Deodexed Gingerbread ROM, and I get to the second last step which tells to upgrade to the GingerBread bootloader, but after doing so I'm reverted back to 3e reovery, with no access to CWM recovery.
Installation Instructions
1. Make sure you’ve backed up any apps / data you need to keep
I would recommend using Titanium Backup. Also, it is best when upgrading to a new version of Android to only backup your user apps and not to include any system data.
2. Copy the XXJVP_Deodexed_I9000M.zip ROM file to your phone.
3. Upgrade to the Gingerbread bootloader
You need to do this only if you’re currently running the original ROM (or any Android 2.2 ROM). Read and follow the instructions here carefully. (http://forum.xda-developers.com/showpost.php?p=14013450&postcount=1)
4. Flash the XXJVP_Deodexed_I9000M.zip update using CWM.
So I have reinstalled the Super Optimized kernel, and am able to access CWM recovery, is it safe to upgrade this ROM without the GingerBread bootloader? I obviously won't be able to use the GingerBread Bootloader, as it blocks CWM. Any advice would be appreciated.
Two side questions,
1. When I was doing this post, I accidentally clicked the wrong phone in the 'Flash ClockworkMod Recovery', and had to redo the flash again picking the 'Galaxy S i9000', however, now when I reboot, there is no option for the Super Optimized Kernels 'advanced ulk features' so that I can ensure that the lagfix is disabled when I get to actually flashing the ROM. If I reinstall the Super Optimized Kernel again, will that option show up again?
2. When booting the phone now, I noticed the graphic that shows the model number of the phone starts out with 'I9000M' and then switches to 'I9000', dropping the 'M', is this an issue, or do I just ignore?
Thanks again.
I've successfully rooted my phone thanks to SuperOneClick, but am not able to figure out how to flash the recovery so that I can use ROM Manager.
I have a stock KB1 image, on an I897 Captivate from AT&T. I'm trying to get the recovery image (currently 3e) set so that I can bypass the signature check, which is what I keep running into.
I installed ROM Manager (the free one, at least until pay day) and tried to use that to flash CWM recovery. Every time I boot into recovery, I run into the confounded signature check.
I have a Superuser app installed from the Market, version 3.0.6(40) and su binary ver 2.3.1-ef.
I'm not typically a dunce, since I've been able to install and run a Linux server at home more than once. But this has got me stumped.
Please let me know what additional information I might need to provide to target guidance.
Read this. Please look at stickies and/or use the search function.
On a personal note, don't waste time on Rom Manager. Its trash for SGS line.
I hadn't seen that list previously. I spent 4 hours last night and three hours today reading stickies and stumbling through search results. That guide for fixing recovery might just be the answer I was looking for.
Is there a different "ROM manager" app that you recommend, or just bare-backing it (which I'm not afraid to do, either)?
Don't bother with it. IMO if you like stock froyo, I recommend just flashing Cognition 4.x.x. Based on KB2 stock looking, but tweaked for speed. CWM is easiest achieved by flashing a kernel with it baked in it.
to skip the recovery crap and rooting and everything else....
take phone out of box. (done)
download and run odin3 flashing util 1.8x Odin3v1.85.zip
boot phone into download mode
flash ginberbread bootloaders http://www.multiupload.com/QQ3LFSRBMD
reboot into download mode
flash custom kernel with CWM built-in pick one in dev section. ANY NOT miui/cm7 kernel in dev section.
reboot into recovery (cwm now!!)
mounts / usb/ copy rom to phone (if not on sdcard already can be done any time before)
cwm flash rom.
** cwm2 kernel for eclair/froyo roms & cwm3/4/5 kernel for gingerbread up
If you goal is to flash a new rom then TRusselo is right. Easier to just flash a kernel with CWM.
Rooted via super 1click and was unable to get clockwork recovery to load said it flashed but would only boot default recovery, soft bricked it 3 times then straight busted it getting the forced upload key press thing had to use USB jig to get download then used Odin to repair firmware some how 3g got switched off. Anyone got any ideas on how to switch back on my guess is key pad access but don't know the code amorphous smart apn from market but don't have the phone yet to try it my friend is gonna bring it this weekend just wanted to find out the best way to switch it back on before I get it back because grs gonna be there this time and I don't want to make him nervous or have him think I'm gonba mess up his phone
Sent from my Evo Running CM7
Stop flashing and read the stickies. If you tried using rom manager or update.zip it wont work unless you fix the 3e recovery issue. Its easier to flash a kernel with CWM baked in to it. For example if you are on froyo Cognition 4.x.x (search for it) kernel should work just fine.
Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,
Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,
Click to expand...
Click to collapse
Other way to change roms is custom recovery. On GB TWRP, on JB CWM.
Sent from Galaxy S Advance
Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?
YMatrix said:
Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?
Click to expand...
Click to collapse
I think it is not working. It is not supported. Way we install custom ROMs: download ROM zip, transfer to SD, then go to recovery and install it from there.
I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...
YMatrix said:
I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...
Click to expand...
Click to collapse
You have GB? Look here.
On I9070 recovery is on the same partition as kernel. So it can't be installed separatly. It is ported. You need to install this kernel, or CoCore. If you install with Odin - you will increase binary counter. For installation with ADB shell, or Terminal emulator (app from market) you need root - and it will not increase bc.
So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?
YMatrix said:
So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?
Click to expand...
Click to collapse
No, only JetMOD have embendend kernel too. And it have TWRP.
Hm, another thing. You better use non binary counter increaing root method. But it need you to flash whole firmware with Odin. And maybe you loose data. But if you do not do factory reset - it will be ok.
Sorry, I didn't understand your last post.
YMatrix said:
Sorry, I didn't understand your last post.
Click to expand...
Click to collapse
If you want to get TWRP with dd command you need to root your phone first.
There are 2 root methods. One that increase binary counter, and one that do not..
With one that do not increase - you need to flash whole firmware with Odin. And by doing that you might need to do factory reset. That will cause your data and app delete. You can try to boot, maybe it will be ok.
Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?
Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?
Click to expand...
Click to collapse
Didn't pay attention.
You have backup option in TWRP, and you can restore it.
Custom roms do not have connection with kernel, just JetMod who do have kernel with TWRP too.
P.S. lol you confuse me. TWRP is kernel related, nothing to do with ROM.
When you want stock kernel back, just flash your firmware from sammobile.com.
So you need to change kernel to get TWRP. And with TWRP you do backup of system.
Sent from Galaxy S Advance
Bos manForu
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?
YMatrix said:
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?
Click to expand...
Click to collapse
You can do that only with TWRP.
And did you read ROM manager description?
* Flash your recovery to the latest and greatest ClockworkMod recovery.
Click to expand...
Click to collapse
For ROM manager you need custom recovery. And for I9070 that is embended in kernel. Full stop.
And it is connected to CWM, not to TWRP. We do not have CWM for Android 2.3.6. ported.
P.S. So to close this:
- You can't do any backup, installation of ROMs without custom recovery (in our case TWRP) on our phone.
- Custom recovery couldn't be installed separatly - it is embended inside kernel file - and has nothing to do with ROM.
It is clear now?
I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?
YMatrix said:
I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?
Click to expand...
Click to collapse
CWM = TWRP
Both are custom recoveryes. Not the same, but same purpose.
1) Our phone have same partition for kernel and recovery. So we can't install it separatly
2) You can backup kernel, but you will need Terminal emulator, and similiar command like instalation of other kernel
Code:
$ su
# dd if=/dev/block/mmcblk0p15 of=/sdcard/boot.bin
# reboot
This will backup your stock kernel on your sdcard. You can install it later this way (ofcourse if boot.bin file is on your sd)
Code:
$ su
# dd if=/sdcard/boot.bin of=/dev/block/mmcblk0p15
# reboot
You always can flash your stock kernel, Download mode do not have anything to do with kernel and recovery partition.
If this is little hard for you, just install custom kernel with TWRP. Or do not do anything. :laugh:
P.S. Trust me, you can't hard brick device with installing kernel. I am tester, and I flashed at least 10 non booting kernels, and 50+ booting ones.
I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?
YMatrix said:
I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?
Click to expand...
Click to collapse
Most likely you will have to flash whole firmware if something goes wrong. I told you what I know.
And if you can go in TWRP recovery, it can restore krenel with other things you backed up. And you can flash new kernel in TWRP too.
Somewhere is written what partition is for what. I do not know that. And developers told us what partition is for kernel and recovery.
I do not think that that thing with restoring downlaod mode will work. Newer tried or heard of it.
I tried to explain you, but maybe I was little confusing. :angel: My english is not great, and I didn't provide 1, 2, 3... steps explanation. Like I throw everything to you. :laugh::laugh::laugh:
:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?
YMatrix said:
:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?
Click to expand...
Click to collapse
That is ok.
And you backup old kernel that you can easy go back to stock one. Without flashing whole firmware, when you want stock. Like you want to go to service for warranty or something like that...