Related
Hi,
I want to go back to 3.0.1 on my IO limited but I am not able to find an image to flash via ODIN.
I want to go back, install CWM, root, and update keeping root.
Thanks for your help
tonovcp said:
Hi,
I want to go back to 3.0.1 on my IO limited but I am not able to find an image to flash via ODIN.
I want to go back, install CWM, root, and update keeping root.
Thanks for your help
Click to expand...
Click to collapse
you dont need odin.
enter fastboot.
(if you have any media):
fastboot boot CWM
adb shell mount /data
pull your media off
adb reboot bootloader
fastboot erase system -w
unpack system.zip from:
http://droidbasement.com/galaxy/sys-backup/
fastboot flash system.img
unpack boot.zip from:
http://droidbasement.com/galaxy/sys-backup/
fastboot erase boot
fastboot flash boot.img
unpack recovery.zip from here:
http://droidbasement.com/galaxy/sys-backup/
fastboot boot recovery.img
factory reset -> reboot
done.
Thanks for the reply, but I have problem with fastboot: computer recognizes and driver is installed, but when type "fastboot devices" nothing happens.
Also, if I try "fastboot whatever", it stays forever: waiting for device.
By the way, I am very very newby on this. I read posts and follow instructions step by step, but I need step by step procedure.
Can you explain it for me?
Thank you
install pdanet to get the fastboot drivers or get the the driver via sdk manager and install it manually against the device. this is in regards to windows os.
I have drivers installed, and detected as NVIDIA android fastboot device, but when I type "fastboot devices" nothing happens. After that try to push CWM and keeps eternally waiting for device.
HELP PLEASE
SOLVED: I had to choose manually drivers from google-sdk and this instructions to get fastboot to work. I only flashed root, no need to go back to 3.0.1... now rooted
"
6. Type "fastboot devices" your device serial should appear!If not:
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
NO Empty line above this set, though galaxy tab 10.1v but works for all variants!(tab detected as adb xxx device)
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
"
Now into boot loop
begin with typing adb start-server enter, than run fastboot commands!
start from beginning of the source post or flash rom with 3.0, from
http://forum.xda-developers.com/showthread.php?t=1119492
than update from the tab to 3.1, or flash the [stock][eur]touchwiz rom! I prefer flashing to 3.0 and updating from settings>about>update to 3.1
Solved this way:
1- edited C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\android_winusb.inf
following the instructions found in a post:
......................................................
Type "fastboot devices" your device serial should appear!If not:
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows). I copied in both
NO Empty line above this set, though galaxy tab 10.1v but works for all variants!(tab detected as adb xxx device)
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
..............................
2- changed Nvidia driver controller manually to the one in C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\android_winusb.inf
3- fastboot now working, but had to restore factory data and wipe in order to work (Had a loop boot)
Which root file did you use ? Been trying to root and I get the same problem as you (with the root instructions on the other post)
My fastboot and nvflash works .. but the adb refuse to detect the device
tonovcp said:
I have drivers installed, and detected as NVIDIA android fastboot device, but when I type "fastboot devices" nothing happens. After that try to push CWM and keeps eternally waiting for device.
HELP PLEASE
SOLVED: I had to choose manually drivers from google-sdk and this instructions to get fastboot to work. I only flashed root, no need to go back to 3.0.1... now rooted
"
6. Type "fastboot devices" your device serial should appear!If not:
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
NO Empty line above this set, though galaxy tab 10.1v but works for all variants!(tab detected as adb xxx device)
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
"
Click to expand...
Click to collapse
Hi pershoot,
I did what you suggested and everything seemed to work fine for my IO tablet.
However, I noticed that my storage shows only 13.7GB total now.
It used to be around 27GB.
Any idea what's going on and how to fix it?
Any help would be appreciated. Thanks!
try to reformat your internal memory from recovery! ELse try reflashing with pit file from [stock][rom][eur]touchwiz after
So how do you root the IO tab now ??
I updated to touchwiz but am unable to root since the PWR + Vol button always puts me to fastboot
And for some reasons .. ADB works .. but fastboot doesn't (NVFLASH works too)
gunzo71 said:
Which root file did you use ? Been trying to root and I get the same problem as you (with the root instructions on the other post)
My fastboot and nvflash works .. but the adb refuse to detect the device
Click to expand...
Click to collapse
Hi,
I used this cwm:
http://droidbasement.com/db-blog/?p=2061
and root from this post:
http://forum.xda-developers.com/showthread.php?t=1171089
Also installed rom manager to reboot to recovery if needed in future, I cannot do it any other way
Ahh .. sorry .. your fastboot works ?? I typed wrongly ..
should be ADB works but fastboot doesn't work for me .. it keeps saying waiting for device .. strange since previously it worked ..
I can't do the fastboot flash img.. for now ..
:EdITTED: - oops seems like I have the exact same issue as you in the earlier post now let me try that 1st ..
tonovcp said:
Hi,
I used this cwm:
http://droidbasement.com/db-blog/?p=2061
and root from this post:
http://forum.xda-developers.com/showthread.php?t=1171089
Also installed rom manager to reboot to recovery if needed in future, I cannot do it any other way
Click to expand...
Click to collapse
ROOT from that post doesn't work ..
I've flashed the CWM in .. but I CAN'T GET into recovery mode to do the install via ZIP option remember
Only way I see now is to do what did previously .. I just want to know what you did that is much shorter than mine ..
FLASH ODIN GT7105.tar img
- Gets you 3.0.1 rooted
INSTALL CWM and REBOOT FROM THERE
-Gets you into Recovery mode
INSTALL Touchwiz update and INSTALL ROOT.zip at the same time ..
- updates to the new touchwiz ROM and gets rooted at the same time
REBOOT DEVICE
- Updates Firmware to touchwiz and you get a rooted I/O tab
Do you have a shorter way ???
Thanks btw .. now I get all the android low and high level comms tools to work
1-Flash 3.0.1 ROM,
2-update to 3.1 from settings>about>update and get it updated from samsung directly on tab (no touchwiz! wait till 3rd august for a stable release).
3-Next install rom manager from market and get clockworkmod recovery from the app!
This is the shortest possible way. remember to clear data after flashing 3.0 to remove the password prompt at startup!
mughalgxt said:
1-Flash 3.0.1 ROM,
2-update to 3.1 from settings>about>update and get it updated from samsung directly on tab (no touchwiz! wait till 3rd august for a stable release).
3-Next install rom manager from market and get clockworkmod recovery from the app!
This is the shortest possible way. remember to clear data after flashing 3.0 to remove the password prompt at startup!
Click to expand...
Click to collapse
Hi .. step 3 require root .. which you can't get on 3.1 with the I/O
Seems like 3.0.1 retrograde to root and work from there is the only option ..
From there .. the choice is yours to go either OC or Bonsai or Touchwiz or stock 3.1
3.0.1 ROM, is rooted and upgrading from about>update on tab doesn't effect the root, it stays! Hence after the update you have a rooted 3.1 stock firmware ready for the next to-be released touch wiz update!
I did not have to go back to 3.0.1, I rebooted to recovery as in picture in post #8
http://forum.xda-developers.com/showpost.php?p=15823121&postcount=8
"
Installation instructions:
It is reccomended you try out the recovery before replacing your stock recovery.
fastboot boot recovery-cwm_4.0.0.4-sam-tab-10.1.img
If you are happy with it, then to replace your recovery:
fastboot flash recovery recovery-cwm_4.0.0.4-sam-tab-10.1.img
"
once there, flash the root.zip
Here you have recovery (two different to try) and root.zip I used
The main problem was get fastboot to work (driver problem) then reboot into recovery and flash root. Once rooted I installed ROM Manager (to work further flash, and reboots etc...)
PS: I am newby at this. I just searched and found different solutions in different posts that helped me out. I just can tell you what I did, and worked for me.
I hope it works for you, if not, it is time to ask the experts in the forums .
mughalgxt said:
3.0.1 ROM, is rooted and upgrading from about>update on tab doesn't effect the root, it stays! Hence after the update you have a rooted 3.1 stock firmware ready for the next to-be released touch wiz update!
Click to expand...
Click to collapse
I screwed up when trying to go back from 3.1TW to 3.0.1.. the launcher application now keeps forceclosing .. so I can't even access CWM
tonovcp said:
I did not have to go back to 3.0.1, I rebooted to recovery as in picture in post #8
http://forum.xda-developers.com/showpost.php?p=15823121&postcount=8
"
Installation instructions:
It is reccomended you try out the recovery before replacing your stock recovery.
fastboot boot recovery-cwm_4.0.0.4-sam-tab-10.1.img
If you are happy with it, then to replace your recovery:
fastboot flash recovery recovery-cwm_4.0.0.4-sam-tab-10.1.img
"
once there, flash the root.zip
Here you have recovery (two different to try) and root.zip I used
The main problem was get fastboot to work (driver problem) then reboot into recovery and flash root. Once rooted I installed ROM Manager (to work further flash, and reboots etc...)
PS: I am newby at this. I just searched and found different solutions in different posts that helped me out. I just can tell you what I did, and worked for me.
I hope it works for you, if not, it is time to ask the experts in the forums .
Click to expand...
Click to collapse
Well .. I tried this CWM recovery.img earlier .. doesn't work .. when I do a reboot .. it reboots to startup again ..
Got 1 tab rooted using my long way round method (should nothave updated to 3.1 so fast before rooting ) ..
Then I softbricked the other trying to revert back 3.0.1
Anyway .. I recovered it by copying over images of the rooted tab using nvflash
Thanks again guys for the help and the sharing !
yesterday i formatted my HONOR 5x via TWRP .
now my device without OS , and every time REBOOT it from recovery mode it says : NO OS , ARE YOU SURE YOU WANT TO REBOOT
guys i need the official ROM for my Phone so i can install it
My phone name : Huawi Honor 5x L-21
Please save me !! :crying::crying:
Trustive said:
yesterday i formatted my HONOR 5x via TWRP .
now my device without OS , and every time REBOOT it from recovery mode it says : NO OS , ARE YOU SURE YOU WANT TO REBOOT
guys i need the official ROM for my Phone so i can install it
My phone name : Huawi Honor 5x L-21
Please save me !! :crying::crying:
Click to expand...
Click to collapse
everything you need is in the Repository in my signature
if you want to reinstall the official rom {emui} you need to also install the stock recovery
Follow these steps to flash Stock ROM:
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
NOTE: If the manual flashing doesn't works or you get any errors, then first try only the force update method, i.e Putting the UPDATE.APP from which you extracted the files in dload folder of your external SDCARD and pressing Vol UP + Vol DOWN + Power button simultaneously after switching off your phone.
Hi all,
Im using honor 7 plkl01 5.0.2.
I just install twrp and my stock recovery image is gone and i wish to get it back. So i flashed the b130 stock recovery.img from TWRP.
But it ends up with error 11 (recovery) and error 2(load).
Is there any way i can get my stock emui recovery back to life so that i can update my firmware locally?
Ps, i tried adb to flash but ends up write recovery error and command not allowed. my phone is unlocked by the way.
fastboot devices
[should reply with a device]
fastboot flash recovery recovery.img
[with recovery.img in the same folder as adb]
You should try starting with B100 files.
Which rom are you using? Open Multi Tool and flash your currrent rom's stock recovery by following instructions. It's so simple.
zinko_pt said:
fastboot devices
[should reply with a device]
fastboot flash recovery recovery.img
[with recovery.img in the same folder as adb]
You should try starting with B100 files.
Click to expand...
Click to collapse
Hi,
And yes it's correct, but i help a little more, to get the recovery of B100 download the B100 firmware, then download HuaweiUpdateExtractor to extract the recovery.img, then you've said all ^^
Put the .IMG in the same folder with adb... Flash, it should work, then maybe a hardreset
Good luck
Edit 1 : By the way, i prefer flash the recovery manually
nicholasong1994 said:
Hi all,
Im using honor 7 plkl01 5.0.2.
I just install twrp and my stock recovery image is gone and i wish to get it back. So i flashed the b130 stock recovery.img from TWRP.
But it ends up with error 11 (recovery) and error 2(load).
Is there any way i can get my stock emui recovery back to life so that i can update my firmware locally?
Ps, i tried adb to flash but ends up write recovery error and command not allowed. my phone is unlocked by the way.
Click to expand...
Click to collapse
You can't flash a recovery if you are booted into recovery, it's like pinning down a person and asking him to get up.
Okay so to flash a recovery you must be in bootloader mode, to boot into bootloader mode you have to first switch off your device then press Vol DOWN+Power Button once booted into bootloader mode, fire this command to flash recovery:
Code:
fastboot flash recovery recovery.img
The recovery.img file should be in the same folder from where you are executing the command.
DigiGoon said:
You can't flash a recovery if you are booted into recovery, it's like pinning down a person and asking him to get up.
Okay so to flash a recovery you must be in bootloader mode, to boot into bootloader mode you have to first switch off your device then press Vol UP + Power Button once booted into bootloader mode, fire this command to flash recovery:
Code:
fastboot flash recovery recovery.img[/b]
The recovery.img file should be in the same folder from where you are executing the command.[/QUOTE]
Hi, i know you know the way ^^ but you made a little error, to perform the command, it's in fastboot mode ( Vol. DOWN + Power )
Vol UP + Power leads to the recovery
Unless this works too ? :eek:
:)
Click to expand...
Click to collapse
Kikito94 said:
Hi, i know you know the way ^^ but you made a little error, to perform the command, it's in fastboot mode ( Vol. DOWN + Power )
Vol UP + Power leads to the recovery
Unless this works too ?
Click to expand...
Click to collapse
Oh yeah, thanks for noticing, that's my mistake. no it's Vol DOWN + Power only for bootloader.
hello
i tried to install twrp but the swipe didn't work
so i tried to install an older version
but now when i reboot twrp do not appear
and i have no more than 800mo memory available
i can't hard reset
what can i do ?
noogpout said:
hello
i tried to install twrp but the swipe didn't work
so i tried to install an older version
but now when i reboot twrp do not appear
and i have no more than 800mo memory available
i can't hard reset
what can i do ?
Click to expand...
Click to collapse
Flash recovery from CMD !
AbhaYsinGH007 said:
Flash recovery from CMD !
Click to expand...
Click to collapse
how can i flash recovery from cmd ?
where can i download the file ?
noogpout said:
how can i flash recovery from cmd ?
where can i download the file ?
Click to expand...
Click to collapse
Xiaomi.eu -> https://xiaomi.eu/community/threads/twrp-for-mi-pad-3.39743/
i follow the thread you mention
i can launch twrp but swipe do not work, i have now an otg cable but mouse is not recognized
so i don't know how to flash the rom
noogpout said:
i follow the thread you mention
i can launch twrp but swipe do not work, i have now an otg cable but mouse is not recognized
so i don't know how to flash the rom
Click to expand...
Click to collapse
That could be a bug !
noogpout said:
i follow the thread you mention
i can launch twrp but swipe do not work, i have now an otg cable but mouse is not recognized
so i don't know how to flash the rom
Click to expand...
Click to collapse
I find that hard to believe. Did you follow post #10? At your own risk, of course.
Guys, I did it!
I had no problems with the touchscreen, so there was nothing to solve for me. My Bootloader was also unlocked already.
Here is everything I did (be careful, this deletes all your data!):
Boot into fastboot (Volume down+ Power on, hold the Volume down-Key until fastboot loads)
Code:
fastboot -w
fastboot erase system
fastboot format system
fastboot flash recovery twrp.img
Boot into TWRP (Volume up + Power on, hold the Volume up-Key until TWRP boots)
WIPE -> Data -> Repair or Change File System -> Resize File System
Flash xiaomi.eu-zip normally (hopefully) enjoy!
Click to expand...
Click to collapse
Read the entire thread
yes i read the entire thread, i executed all the flashboot command but my rom was a global one not chinese, so the touch screen does not work in twrp.
Actually i downloaded a rom here : https://drive.google.com/uc?id=0B023gSzruW0aLV9ZRG1pdHpqd3c&export=download
then in fast boot mode i executed this command : ./flash_all.sh
but at the end i have this error : finished. total time: 10.194s
error: cannot load './images/cust.img'
i cannot boot to miui but now i have MI Recovery instead of TWRP
noogpout said:
yes i read the entire thread, i executed all the flashboot command but my rom was a global one not chinese, so the touch screen does not work in twrp.
Actually i downloaded a rom here : https://drive.google.com/uc?id=0B023gSzruW0aLV9ZRG1pdHpqd3c&export=download
then in fast boot mode i executed this command : ./flash_all.sh
but at the end i have this error : finished. total time: 10.194s
error: cannot load './images/cust.img'
i cannot boot to miui but now i have MI Recovery instead of TWRP
Click to expand...
Click to collapse
Why would you execute "./flash_all.sh". Did you try the methods mentioned on page 2 in the thread?
You need to know your commands.
Do you have ADB drivers installed?
Palm Trees said:
Why would you execute "./flash_all.sh". Did you try the methods mentioned on page 2 in the thread?
You need to know your commands.
Do you have ADB drivers installed?
Click to expand...
Click to collapse
yes i know the command : ./flash_all is a script in the archive : cappu_images_7.5.11_20170514.0000.00_7.0_global_xiaomi.eu.zip
i have already tested the commands in the page 2 :
fastboot -w
fastboot erase system
fastboot format system
fastboot flash recovery twrp.img
twrp is ok but i cannot swipe, because the touch screen is not enabled
so i cannot pass the step :
10. WIPE -> Data -> Repair or Change File System -> Resize File System
it's ok i commented the following lines in the script :
fastboot $* flash cust `dirname $0`/images/cust.img
if [ $? -ne 0 ] ; then echo "Flash cust error"; exit 1; fi
so the script can continue and after the boot is ok, MIUI start
Dear All,
I went through the book "XDA Developers' Android Hacker's Toolkit".
Liked it. But got little confused too since I lack good knowledge in Android voo doo.
Is there any document or post where Rooting and Installation concepts common to all phones are discussed in detail?
Such as...
To my knowledge, we have three major pieces of software in any Android phones.
1. bootloader (mostly locked)
2. recovery
3. Android OS
1. How to replace each software when phone is not hard bricked but Android OS not working?
2. How to replace each software when phone is alive and Android OS is working?
3. If bootloader itself is corrupted?
4. If bootloader is fine but recovery corrupted?
5. If bootloader and recovery is fine but Android OS is corrupted?
6. Do installable binary differs depending on method?
etc etc...
Sincerely,
Srinivas Nayak
1. How to replace each software when phone is not hard bricked but Android OS not working?
- By using fastboot/download mode and flashing stock firmware (system+boot+recovery+bootloader) using PC
- Here either /system, /data or /boot will be corrupted.
2. How to replace each software when phone is alive and Android OS is working?
- By using fastboot or download mode and flashing stock fastboot firmware using PC.
- By using recovery mode and flashing recovery firmware zip using TWRP.
- By using ADB and flashing recovery firmware zip using ADB sideload.
3. If bootloader itself is corrupted?
- Here the fastboot mode wont be accessible
- By using emergency download mode (EDL)and flashing stock fastboot firmware using PC
- Also known as EDL mode for Qualcomm devices and download mode for Samsung and MediaTek devices
4. If bootloader is fine but recovery corrupted?
- Here the recovery mode wont be accessible.
- By using fastboot/download mode and flashing stock fastboot firmware using PC.
5. If bootloader and recovery is fine but Android OS is corrupted?
- Here the /system or /boot will be corrupted.
- By using fastboot/download mode and flashing stock fastboot firmware using PC.
- By using recovery mode and flashing recovery firmware zip using TWRP.
6. Do installable binary differs depending on method?
Didnt get your question. Which installable binary are you referring to?
Dear SharkcpN,
My hearty thanks for your valuable time and kind help.
It is very clear and concise. Simply loved it.
If you get little time, kindly help me in some silly doubts I always get confused about.
SharkcpN said:
1. How to replace each software when phone is not hard bricked but Android OS not working?
- By using fastboot/download mode and flashing stock firmware (system+boot+recovery+bootloader) using PC
- Here either /system, /data or /boot will be corrupted.
Click to expand...
Click to collapse
Here we say, stock firmware = (system+boot+recovery+bootloader)
What is the difference between boot and bootloader?
Is boot = vmlinuz? and bootloader = grub?
Can I draw an analogy of a Linux system with Android where, bootloader = grub, boot = vmlinuz, system = init, and recovery = another small rescue linux? Am I mistaken?
SharkcpN said:
6. Do installable binary differs depending on method?
Didnt get your question. Which installable binary are you referring to?
Click to expand...
Click to collapse
I was referring to this;
SharkcpN said:
2. How to replace each software when phone is alive and Android OS is working?
- By using fastboot or download mode and flashing stock fastboot firmware using PC.
- By using recovery mode and flashing recovery firmware zip using TWRP.
- By using ADB and flashing recovery firmware zip using ADB sideload.
Click to expand...
Click to collapse
in one method we say, "stock fastboot firmware",
in another method we say "recovery firmware zip".
In these two, what are these binaries?
Are they different things for different partition?
I mean, in one method what we flash, goes to /boot, in another method what we flash, goes to /system, in another method what we flash, goes to place of bootloader, in another method what we flash, goes to /recovery, or all the time, we flash only one thing that consistes of contents of all the partitions(bootloader, /boot, /system, /recovery)?
Also sometimes I read *.img file used in fastboot command, and sometimes *.zip used from recovery mode. Are the binaries same but only differently packaged?
SharkcpN said:
3. If bootloader itself is corrupted?
- Here the fastboot mode wont be accessible
- By using emergency download mode (EDL)and flashing stock fastboot firmware using PC
- Also known as EDL mode for Qualcomm devices and download mode for Samsung and MediaTek devices
Click to expand...
Click to collapse
How can we reach download mode in Samsung/MediaTek phones and EDL mode in Qualcomm phone?
I know only VolumnDown+Power to enter into fastboot mode...
Rest all of your lines are very clear since you have used all our words very consistently throughout your answer.
From all my reading of Android world, I come across a lot of inconsistency of words which resulted in a lot my confusion. This may partly have aggravated due to my lack of deep knowledge.
Kindly help.
Sincerely,
Srinivas Nayak
What is the difference between boot and bootloader?
Is boot = vmlinuz? and bootloader = grub?
Yes the /boot partition contains the Linux Kernel and the bootloader /sbl1 contains the code which is executed when the phone is started. Moto, OnePlus devices have a discrete bootloader in which you can select the partition in which you want to boot i.e. /system = Boot normally /recovery = boot into recovery mode or fastboot mode.
Can I draw an analogy of a Linux system with Android where, bootloader = grub, boot = vmlinuz, system = init, and recovery = another small rescue linux? Am I mistaken?
Correct
in one method we say, "stock fastboot firmware",
in another method we say "recovery firmware zip".
In these two, what are these binaries?
Are they different things for different partition?
They are basically the same files packaged differently. The firmware zip refers to the system (OS), boot(kernel), bootloader(grub) and other partitions which came preinstalled on your device.
Fastboot firmware consists of *.img files which are to be directly flashed using the command "fastboot flash <partition_name> <file_name.img" Recovery firmware consists of META-INF folder, system files in the form of system.dat , boot.img and other files. The META-INF folder contains a updater-script which has instructions which tell the recovery to flash file A to partition A, file B to partition B and so on. If the phone is unusable or any partition is corrupted, its better to flash all the partitions of the device in order to ensure the phone is bootable.
How can we reach download mode in Samsung/MediaTek phones and EDL mode in Qualcomm phone?
I know only VolumnDown+Power to enter into fastboot mode
For Samsung devices = Volume Down + Home + Power
MediaTek = shorting contact points on the SoC, Vol Down + Power, each brand implements it differently
Qualcomm = adb reboot edl, fastboot oem edl, Vol Up + Vol Down, shorting contact points on the SoC, Deep Flash Cable if EDL mode is blocked by the brand, again each brand implements it differently
Many thanks SharkcpN.
SharkcpN said:
Can I draw an analogy of a Linux system with Android where, bootloader = grub, boot = vmlinuz, system = init, and recovery = another small rescue linux? Am I mistaken?
Correct
Click to expand...
Click to collapse
Now my doubts got clear.
But it won't be good to disturb you further.
Is there any book, or tutorial, or any document(in any form: whether blog, website etc.) that will give me details in such line? Exactly like you stated things clearly...
I want to learn more about this...
If possible kindly share some good links.
Sincerely,
Srinivas Nayak
Yesterday's research revealed a good document: 2net.co.uk/slides/android-boot-slides-2.0.pdf
Would like to see more.