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.
Related
ph84 said that dual boot is possible and he will write how to.
When???(don't hurry, I only ask)
Maybe your question can be answered if you look for the Topogigi's post in this thread [HOW TO] Linux on Folio.
I've not try this, because i don't understand some things... if someone makes a how to step by step, would be amazing !!
Here is how to get it without steps:
Topogigi said:
[ONLY FOR DEVELOPERS AND SKILLED PEOPLE: NOT FOR NEWBIES!!!]
My 2 cents:
I installed ubuntu and it works quite well. I'd like to point out that it you can boot android or ubuntu flashing the boot.img containing the linux kernel in place of recovery kernel (fastboot flash recovery boot.img). You can even try a kernel before flashing it to the device (fastboot boot boot.img). To enter fastboot mode in your device, simply press the power button three times when the Toshiba logo appears on the screen at powerup, then press volume up one time. Voila, you are in fastboot mode...
To boot linux, you have to press "power+volume up", then follow the instruction on screen to wipe the device (don't worry, it will boot linux and it will not wipe anything). You'll miss the recovery partition that way, but you'll gain a dual-boot tablet with android and ubuntu in change. Not a bad trade.
If you really need recovery, you can always reflash it with fastboot, so the process is perfectly reversible.
Now, back to business:
1) Touchscreen works (sort of). If you apt-get evtest, you'll notice that /dev/input/event3 is bound to the touchscreen and it reports to be alive and kicking. The test reports the coordinate changing and the pressure on the screen (multitouch works too). But......in Xorg, the device only reports the pressure and coordinates are not changing. You can test with xinput as I did. It seems a software-related issue: the drivers does not report correctly what the hardware is telling him. I'll investigate and report back if news will come out.
2) Wifi could eventually work. The card is bound via SDIO bus, and a ar6000 driver supporting SDIO is available. I'll try to compile the driver ASAP.
3) Suspend, cpufreq do not work and I doubt they will work without driver sources
4) Battery is working, framebuffer is working good and the system seems quite snappy also with an EXT4 partition on a MMC. Openoffice works great, quicker than expected.
5) If you compile the kernel with nilfs2 support, you can easily mount all the android partitions within ubuntu with ease. Not bad...
That's all for the moment: I hope that someone will help me to make this little devil fly.
Click to expand...
Click to collapse
sergi711 said:
Maybe your question can be answered if you look for the Topogigi's post in this thread [HOW TO] Linux on Folio.
I've not try this, because i don't understand some things... if someone makes a how to step by step, would be amazing !!
Here is how to get it without steps:
Click to expand...
Click to collapse
That's quite easy in fact :
In fastboot, just flash the boot.img instead of recovery :
fastboot flash recovery boot.img
That's it... you will loose "auto" recovery, but you will gain Linux Ubuntu
Akta
Akta77 said:
That's quite easy in fact :
In fastboot, just flash the boot.img instead of recovery :
fastboot flash recovery boot.img
That's it... you will loose "auto" recovery, but you will gain Linux Ubuntu
Akta
Click to expand...
Click to collapse
It sounds easy... but i have never enter in fastboot mode... I don't know what commands use...
Another question, I have flashed the update.zip from ph84 to boot only ubuntu, when i flash this boot.img on fastboot mode how I flash the foliomod ???
fastboot, SDK, UPDATE.ZIP, DRIVERS etc.
Sergi711
1.I know for that(try), but I can't use fastboot. I installed all drivers, but I can't send commands to Folio 100. I made thread for help, but no one help me. If you can help, please, help me!!!!!!
Can we make update.zip with that kernel and don't use fastboot?
2.a)First, download and install SDK.
http://developer.android.com/sdk/index.html
Second, go here http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets and install drivers.
Third, enter fastboot mode(3X Power UP+Volume UP) IF YOU PRESS POWER UP 4X, YOU'LL BRICK TABLET AND FOR THAT YOU CAN'T FIND HELP!!!!!
Moreover, connect Folio with PC,Laptop, NetBook, Tablet PC or NoteBook via USB and open terminal(Start>Run>cmd) and go to C:/android-sdk/platform-tools (in my
case)
Terminal: cd C:/android-sdk/platform-tools
Fifth, now run fastboot.exe and type anything you want
Terminal: fastboot _______________( fastboot flash recovery boot.img)
b) If you flash boot.img from ph84 to boot Ubuntu ARM on Folio 100, in future, you'll can only boot from SD Card or USB(sdmmc-update.zip or usb-update.zip). You'll not use Folio's internal storage and you'll can't boot to FolioMod, but from recovery you can easily reflash FolioMod or another rom or custom kernel(you need to reflash kernel and you can made your own update.zip with your custom kernel and don't touch FolioMod )
Akta77
Can we we copy recovery to /date or /date/date folder and boot it like MCLP said for installing FolioMod or another rom?
Step 1. Install Root Explorer on Folio 100(can't post app, because rules, but with googling find it easily or download it from android market)
Step 2. Copy the recovery image from FolioMod(if you want original recovery) or from CyanogenMod7.0.0(if you want unofficial ClockworkMod recovery) to SD Card or Internal storage
Step 3.With Root Explorer copy recovery.img to /date or if you find another date directory inside copy there(copy recovery.img to both directory just in case)
Step 4. Exit from Root Explorer, got to Settings>Applications>Development and enable USB Debugging
Step 5. Connect Folio 100 to PC or etc. via USB and open Terminal(cmd) and go to SDK directory C:/android-sdk/platform-tools(in my case)
Terminal: cd C:/android-sdk/platform-tools
adb shell (use this if you have installed SDK drivers for Tegra devices)
cat /data/recovery.img >/dev/block/mmcblk0p7
or
Install any Terminal app on Folio 100 and type
Android Terminal: cat /data/recovery.img >/dev/block/mmcblk0p7
After this, you should have recovery
Jon2555 said:
Sergi711
1.I know for that(try), but I can't use fastboot. I installed all drivers, but I can't send commands to Folio 100. I made thread for help, but no one help me. If you can help, please, help me!!!!!!
Click to expand...
Click to collapse
Maybe this helps: http://forum.xda-developers.com/showthread.php?t=1055754
Most other fastboot binaries out there don't recognize tegra devices.
I just use the SDK's Fastboot under Linux (built from Cyanogen's 7 repo) without any problem.
If you are using Windows, have you modified the inf has stated by google?
Entering fastboot is simple : just press x3 power and then volume up at boot screen.
You will be in fastboot mode.
I am not sure we can boot the kernel from somewhere else than boot partition or recovery partition. But we could maybe build a relocable kernel and load Linux or Android using kexec from boot partition like "petiboot" on PS3
Akta
Thank's guys!!! I'm going to try it whan I back from France.
Sent from my folio 100 using Tapatalk
could someone that have a dual boot ubutntu/android make a how to for us... ??? because i read the lastest post that you reply i don't know how to have a dual boot yet.. i can't understand... please a how to is needed, step by step...
thanks in advance !!!
Hi,
Just wrote you how to do it
Boot the tab in fastboot (3xPower + 1 Vol Up)
Then connect your tablet on your PC and do :
fastboot flash recovery boot.img (boot.img is extracted from update.zip according to your wish (SDCARD or USB PENDRIVE)).
Akta
ok i flash the boot.img on fastboot, and then ??? i only have now ubuntu, how i install android after fastboot flash boot boot.img ????
I know, i must enter fastboot mode, and flash boot.img instead of recovery.
After that, i will only be able to boot from sdcard... isn't it ?
Ok, i must have 2 sdcards to boot android, and the other sdcard to boot ubuntu ???
if this is right... how the sdcard must be ??? update.zip on the root ???, the update zip extracted on the root of sdcard ??
i have lot of doubts after the fastboot flash recovery boot.img step, sorry.... can anyone help me ??
I think when you flash boot.img(sd or usb) for dualboot, when sd card with Ubuntu is in Folio you'll boot ubuntu(sd or usb) and if you haven't got Ubuntu sdcard or you have it (but not Ubuntu sd) or if you haven't any you will boot to android.
What's up with my question?
Sent from my folio 100 using Tapatalk
Ok i understand that after flash boot.img instead of recovery on fastboot mode... folio will boot from sdcard, in that case, if you push a sdcard with an ubuntu filesystem, folio will boot ubuntu, and if you remove sd after boot moment, folio will recognise internal sd and boot android ??? thats it ???
edit: but what boot.img must i flash ???
When i will have some time, i will rebuild a boot.img able too boot linux from a second partition on the sdcard. You will have fat32 on first partition and ext3 or ext4 on second. For now, you can live your sdcard in the folio but android is not able to access it (lack of ext3 / ext4 support, but easy to install ).
Akta
Thank's Akta for your help!!! Can you sometime post your progress? I want to help, but I don't have dev skills. Can you post some good link(searched, but no luck) or your howto about making kernels? I found for themes and I'll try to make some in my free time.
Sent from my folio 100 using Tapatalk
Quite interested by the dual boot on Folio 100.
I will keep an eye on this thread.
Akta77 said:
That's quite easy in fact :
In fastboot, just flash the boot.img instead of recovery :
fastboot flash recovery boot.img
That's it... you will loose "auto" recovery, but you will gain Linux Ubuntu
Akta
Click to expand...
Click to collapse
I there, I have few questions:
First, why are you flashing boot into recovery? Is not supposed that boot is the image that cares about booting procedure?
Second, once first question is solved, which boot image are we supposed to flash? I mean, we will need one that searches into sd for a boot/grub, isnt it?
Third, what about the procedure, I explain myself, the logical order of doing all this is: flash an android rom, CM for example, then do the procedure to install ubuntu into the sd and finally flash the boot img so system looks for sd-ubuntu and if it's not found, then boot internal android rom, am i right?
Thanks!
1. Yes.
2. Yes.
3. Yes.
Sent from my GT-I5700 using Tapatalk
Well, then:
Which image should we flash? Where can I can get it?
And finally, this image where must be flashed to dualboot?
Thanks!
Look in the second post on first page. You will see someone talking about dual boot. Find that post in first threde of Ubuntu for Folio 100 that wrote DerArtem(I think)
I don't have time to post link, but if you don't find it tell me and I'll post link.
Below I'm mentioning a few points that I have tried to understand in the past 2 days.....Please note these are just assumptions of my understanding...I might be wrong....Plz cement my understanding by just saying either true or false....You may correct the wrong assumptions...no force
1. Users with unlocked bootloaders and the ability to boot into the bootloader (HTC) can do without a custom recovery...as they can do all that we do through CWM using the fastboot commands through cmd. (This point is clarified a bit from ur above post. Bootloader/fastboot mode can only replace a few features of CWM not all....CWM gives more advanced features. )
2. Samsung users have unlocked bootloaders but cannot boot into it so cannot use fastboot commands. They need to flash CWM through ODIN by entering download mode.
3. Download mode exclusive to samsung.
4. fastboot commands can be used with locked bootloaders.
5. The boot.img is an image of the boot partition and same goes for recovery.img.
6. boot.img contains the kernel and the ramdisk..so the bootloader location first loads this partition into main memory and the kernel then loads the OS and other stuff.
7. HTC devices have access to bootloader (HBOOT) ie they can boot into the bootloader. From there they can use fastboot commands to direct the bootloader to boot into recovery mode....what this does is directs the bootloader to load the recovery partition into memory instead of the boot partition.
8. Samsung users cannot directly address the bootloader as they cannot boot into the bootloader and hence cannot use fastboot commands. The key combinations (Volume up + ok + Power) that sammy users use to get into recovery are directions to the bootloader to load the recovery partition instead of the boot partition.
9. On rooted phones, we can use apps to do the same thing from within the phone ie we are using apps with root access to instruct the bootloader to take us into recovery instead of using key combinations at boot.
10. Even htc users can do so apart from the ability to directly instruct the bootloader by booting into it.
Your help will be greatly appreciated
Note : Samsung here refers to mostly S2 as I know that nexus users can boot into the bootloader.
I'm using an Empire ElectroniX D709 tablet, running Android 4.0.4. It's an old low-spec device, and I'm planning to use this device to improve my Android hacking skills.
I've asked the manufacturers to send me the stock ROM, which they did. Pretty cool!
The problem is that there's no flashing tool or instructions included, and the staff I spoke with did not know how to flash it either.
So now I'm on my own, with a big image file I don't know how to flash.
I tried to start a development thread at the Miscelleaneous Android Development section, but because I have almost no posts, I can't post there. So maybe this is a good place to ask. How can I flash or unpack this image?
You can find the ROM here: http://www.needrom.com/download/empire-electronics-d709/
Exeleration-G said:
I'm using an Empire ElectroniX D709 tablet, running Android 4.0.4. It's an old low-spec device, and I'm planning to use this device to improve my Android hacking skills.
I've asked the manufacturers to send me the stock ROM, which they did. Pretty cool!
The problem is that there's no flashing tool or instructions included, and the staff I spoke with did not know how to flash it either.
So now I'm on my own, with a big image file I don't know how to flash.
I tried to start a development thread at the Miscelleaneous Android Development section, but because I have almost no posts, I can't post there. So maybe this is a good place to ask. How can I flash or unpack this image?
You can find the ROM here: http://www.needrom.com/download/empire-electronics-d709/
Click to expand...
Click to collapse
You have to manually flash them using fastboot. Look up how to get fastboot and move the image(s) to the folder were fastboot.exe is located. Boot into your bootloader either via adb reboot bootloader or by physically doing it from the device. Now here is where most people fail. At the end of the file name, before the .img, it should be either boot, fastboot, recovery or system. If it is system, then do fastboot flash system nameofthesystemimg.img and if it is boot, you get the idea.
Thank you. Fastboot is a good idea. Problem is that I don't know which partition this .img file belongs to. I have the feeling that this file contains every partition, yet I'm not sure how to split it up so that I can flash each partition.
Exeleration-G said:
Thank you. Fastboot is a good idea. Problem is that I don't know which partition this .img file belongs to. I have the feeling that this file contains every partition, yet I'm not sure how to split it up so that I can flash each partition.
Click to expand...
Click to collapse
Will you mind sharing the whole file name? If it is an all partition img you can do fastboot flash all (I think). Just type fastboot and see the all option in the help menu.
Sent using a ks01lte (gt-i9506) running cm 13
RAZERZDAHACKER said:
Will you mind sharing the whole file name? If it is an all partition img you can do fastboot flash all (I think). Just type fastboot and see the all option in the help menu.
Sent using a ks01lte (gt-i9506) running cm 13
Click to expand...
Click to collapse
The full file name is D709_n.img. Theres an option fastboot flashall indeed.
Right now, I'm trying to get the device into fastboot, without success. Things I've tried until now:
Code:
adb reboot-bootloader
adb reboot bootloader
adb reboot fastboot
Every time, the device restarts and just enters the normal mode. I can get into stock recovery, but there's no option to restart to bootloader there.
Exeleration-G said:
The full file name is D709_n.img. Theres an option fastboot flashall indeed.
Right now, I'm trying to get the device into fastboot, without success. Things I've tried until now:
Code:
adb reboot-bootloader
adb reboot bootloader
adb reboot fastboot
Every time, the device restarts and just enters the normal mode. I can get into stock recovery, but there's no option to restart to bootloader there.
Click to expand...
Click to collapse
Hmmm, if you type adb devices, do you see your device there? If not, search online for drivers. If that does not work, google your device and how to get it to fastboot.
RAZERZDAHACKER said:
Hmmm, if you type adb devices, do you see your device there? If not, search online for drivers. If that does not work, google your device and how to get it to fastboot.
Click to expand...
Click to collapse
Yes, it's fully recognized, and I can adb in it just fine. I also get an adb prompt in recovery mode that lets me control the device. The only problem right now is getting this thing to fastboot.
Update
After googling its model number (crane-evb), I found out that this device can be flashed using LiveSuite (described here). It's nice to see the device back in its factory condition. Now I need to find a way to extract the partitions.
[QRCODE][/QRCODE]
Exeleration-G said:
Update
After googling its model number (crane-evb), I found out that this device can be flashed using LiveSuite (described here). It's nice to see the device back in its factory condition. Now I need to find a way to extract the partitions.
Click to expand...
Click to collapse
YaY! I was going to say that in stock recovery there is this option called update via adb or something but now that it is working, there is no need for that.
MANUALLY INSTALLING FULL NOUGAT 7.11 FIRMWARE 2018/03/15(security_patch 2018-02-05) (RECOVERY, BOOT, SYSTEM) Even If Its Soft Bricked Because You Messed Up Somewhere. Files Here Are For Asus Zenfone 3 Zoom ZE553KL Z01HD WW Sku .
Its The Last Nougat Update Before Oreo Was Released.
MORE FIRWARES HERE
Story Time:
As I Remember It.....Condensed Version, This Was Over A Few Days Of Trial And Error, Mainly Because Adb SideLoad Refused To Flash Asus's Stock Firmware Zip Files.
I Messed Up My Friends Asus Zenfone 3 Zoom, ZE553KL.
He Bought Used, He Quickly Updated To Oreo From Within The Phones Update But Was Having Missed Texts And Slow Lte(4g) Speeds, He Wasnt Sure If It Happened On Nougat Which The Phone Was On Originally.
Downgraded To 6.01, Installed Twrp, Magisk, Still Having Same Issues, Flashing An Update Zip W/a Modded Updater Script Via Twrp Caused A Soft Bricked Phone, It Never Completed The Flash, Twrp Backup Didnt Work, Factory Reset A No Go, Couldn't Manually Flash Stock Rom As Adb Sideload Always Gave Errors, Fastboot System images Didnt Help For One Reason Or Another, Phone Was Just Bootlooping Back To The Unlocked Bootloader Menu.
Down Loaded Alot Of Stuff, Read Countless Pages, And Somehow Got The Right Firmware Files(recovery, boot, system img files) That Was Flashable Via Fastboot Extracted From A Zip, My Fix Is Below. These Are Not My Files But I Cant Remember Where I Got Them From As I Dl-ed Alot Of Stuff Trying To Get This Phone To A Running State. No I Havent Tried Oreo Yet, He Has His Phone Back Now And Not Sure When He'll Let Me Play With It Again, Lol.
UPDATE TO THIS STORY
HOWTO FLASH
PREREQUISITES:
Make A Nandroid Backup
If Bootable Remove/Signout Of Google Account
(Might Work With Locked Bootloader, IDK)
Ze553kl(Zenfone3 Zoom) Phone With Unlocked Bootloader(used unlocker apk from asus website when phone was in running state)
Unlocking Bootloader App Available From Asus - was for upto nougat 7.11
Usb Asus Drivers
Usb Debugging Enabled On Phone, Maybe Not But Wont Hurt To Try
Adb Fastboot Program(Included)
Recovery, Boot, And System Img Files Of Nougat 7.11(Included)
Computer Running Windows
Usb Data Cable For Phone
ON PHONE-
If Bootable Enable Usb Debugging, Uncheck Verify Apps Via Usb, Install From Unknown Sources, Remove Google Account
Backup Internal Sdcard - Most Def
Remove Sdcard, Just In Case
Put Phone Into Fast Boot Mode- Unplugged, Phone Powered Off - Vol Up + Power Button Pressed, Hold Both Until Screen Comes On.
Plug Usb In Cable To Phone From Pc.
ON COMPUTER-
From The Download Section Below Dl ADB_FASTBOOT_1.4.1.ZIP File And Extract It Into A New Empty Folder.
Download And Copy The Three .Img Files From The Download Section Below Into This New Adb Folder
HOW TO RUN ADB VIA COMMAND PROMPT? -
From Within Adb-fastboot Folder You Created, Nothing Selected, Hold Down The Shift Key Then Use The Right Mouse Button To Click In Empty Space In The Adb-fastboot Folder, Select "Open Command Window Here" From The Menu That Pops Up.
From Within Command Prompt Type-
Adb Devices
It Should Output A Device With A String Of Letters And Numbers, Thats Your Phone.
Next Steps Will Install Nougat 7.11 And Consequently Wipe Your Phone
Run These 5 "fastboot" Commands One At A Time.
When Each Step Is Completed Run The Next Command, You Can Copy And Paste These Five (5) Fastboot Commands Into The Command Prompt Window
----------------------------------------------------------------------
1.
Code:
fastboot flash recovery recovery-zoom-7.11.img
2.
Code:
fastboot flash boot boot-zoom-7.11.img
3.
this one @ ~4gb will take awhile to initialize and complete, patience needed
CAN REDO THIS SYSTEM FLASH NOW TO MAKE SURE IT "STICKS"
Code:
fastboot flash system system-zoom-7.11.img
4.
wipes internal sdcard
Code:
fastboot format userdata
5.
Code:
fastboot reboot
-------------------------------------------------------------------------------------------
if you were successfull it will boot into 7.11, takes about 3-5 mins to boot.
IF DID NOT FLASH PROPERLY OR ODD BEHAVIOR AFTER REBOOT THEN REDO STEPS AGAIN....ELSE KEEP READING!
------------------------------------------------------------------------
IF STILL BRICKED OR ODD BEHAVIOR BUT CAN BOOT TO BOOTLOADER/FASTBOOT THEN DO THESE COMMANDS WHEN IN FASTBOOT MODE
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
THEN RE-BOOT BACK INTO BOOTLOADER AND DO THE FLASH FOR 7.11 FIRMWARE
STILL HAVING ISSUES, RESTORE USING TECH FW THAT REFLASHES ALL MDMS, RADIOS, DRIVERS ETC FROM HERE
[FW] 7.1.1 & 6.0.1 Service Tech Firmwares - Debrick - Upgrade - Downgrade
- -------------------------------------------------------------------------------------
disclaimer im not responsible for yours or anyone elses devices, do at your own risk
DOWNLOADS
PHONE FILES ARE FROM A Asus Zenfone 3 Zoom ZE553KL WW SKU FIRMWARE Version WW-71.60.139.30 2018/03/15
RECOVERY-ZOOM-7.11.IMG
md5 03d8358e1341a73b5a492c12e3dbe39e
BOOT-ZOOM-7.11.IMG
md5 1ad55f9852d56b79a95654173af5649a
SYSTEM-ZOOM-7.11.IMG
md5 7217f778701c988271739ab18fb0fb30
ADB_FASTBOOT_1.4.1.ZIP
..
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Deleted. Double post
Naman Vashishth said:
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Click to expand...
Click to collapse
What do u mean by raw. In what format is it in.
I've converted oreo stock firmware .dat files to .img files but I can't test them as I don't have the phone. My friend seems happy on nougat and I don't think he'll let me flash it on his phone.
I haven't tried dl-ing official stock and seeing if phone will see it as an update to manually self install via nougat recovery or maybe to try adb sideload again.
Naman Vashishth said:
I can provide you latest system,boot, recovery.img files if you want...
Click to expand...
Click to collapse
Please do - I could sure use them.
Work very well !
ciao
God bless you! You made my quite dead phone, live again!
Thank you
I can't update to Oreo via ota... do you know why?
the op here. lol, my friend dropped the phone and now its dead screen, no display/no touch but phone still works.
he doesnt want to get a screen for it as it will cost almost as much as he paid for it.......so its mine now.
been flashing stuff to it, gave it a very hard soft brick, still dealing with that.
my goal was to run it remotely but get adb/usb debugging enabled and get pc trusted by phone. i thought he wanted to sell it as is but decided to give to me to do whatever i want to it
got out of the hard soft brick, installed twrp, use twrp cli, twrp backups and restore, rooted w/magisk, installed 6.0.1 (fluked it), 7.11 using my method above with the extra erase commands, removed frp, got adb /usb debugging enabled and device adb authorized by hacking , got vysor, a remote control mirroring app running, all without a working screen.
i'll write up a tut for any1 else that needs help. fyi, weak screen if dropped even short distance, but he had no cover, but pretty to hard to brick it, imo, ymmv
So can i downgrade my phone from android 8 to 7.1.1 following this process.
kingairtel08 said:
So can i downgrade my phone from android 8 to 7.1.1 following this process.
Click to expand...
Click to collapse
yes, i went from 8.0 to 7.11 then to 6.01
more fw here https://forum.xda-developers.com/ze...fw-7-11-6-0-1-service-tech-firmwares-t3850000
Bro i am on 8.0 and want to unlock bootloader and root it n enable cam2api in it, as unlocker nt working in android 8.0 so i want to back to 7.1.1. thank u bro,i will try it tonight.
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
kingairtel08 said:
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
Click to expand...
Click to collapse
after flashing did u, in stock recovery, do a factory reset and wipe caches aka wipe user data in fastboot.
else do a complete wipe as outlined in op
yes bro i m on stock recovery ,did wipe cache etc.
kingairtel08 said:
yes bro i m on stock recovery ,did wipe cache etc.
Click to expand...
Click to collapse
does etc mean factory reset?
did u do the extra procedure to completely erase everything as posted in op in the section of when still having issues
yes bro. i followed all steps .
kingairtel08 said:
yes bro.
Click to expand...
Click to collapse
yes to which
this?
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
if yes then do a full restore of radio, mdm etc from here using method 1 or 2
https://forum.xda-developers.com/att-s7-edge/how-to/fw-7-11-6-0-1-service-tech-firmwares-t3850000
i did all this steps then flash firmware img.
kingairtel08 said:
i did all this steps then flash firmware img.
Click to expand...
Click to collapse
which method did u use from the link i posted
bro i dnt have the 7.1..1 zip file ,i used ur 7.1.1.img file,used method 2.
i will try once again ,wil reply within 2hours.
bro i want to unlock my phone whats why i downgrade,but after downgrading checked official unlock tool gives the same network error that gives on android 8.0.is there any way to unlock it on this 7.1.1 firmware?
Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205