Hi,
I have flash system.img file by using
Code:
D:\ADB\Android>fastboot flash system d:\backup\flash\system.img
sending 'system' (116302 KB)...
OKAY [114.524s]
writing 'system'...
OKAY [ 47.582s]
finished. total time: 162.108s
It seems normal to me, but the problem arise when I restart the the phone. The phone unable to boot, and when I try
Code:
ADB Shell
It says somethings like "sh" is not found. So I do reboot recovery go to the shell and mount /system. Shockingly there is nothing in there.
I have checked the contents of system.img, and there is a lot of things in there, including the "sh". But it seems fastboot failed to flash the system partition.
Anyone can help me ?
maybe you should tell more info about your device, brand,chipset, etc ?
so people can be more easy to help.
just newbie suggestion, ignore this if its no help xD
Looks like your system image file is corrupted cause its not mounted after loading kernel. What kind of filesystem the image is using?
lolet said:
Looks like your system image file is corrupted cause its not mounted after loading kernel. What kind of filesystem the image is using?
Click to expand...
Click to collapse
The system image is not corrupted, because I can safely flash it using Clockworkmod. The filesystem is yaff2, and I have tried opening it using some software and my file is there. I think the problem lies on fastboot who failed flashing properly.
simple
yokowasis said:
Hi,
I have flash system.img file by using
Code:
D:\ADB\Android>fastboot flash system d:\backup\flash\system.img
sending 'system' (116302 KB)...
OKAY [114.524s]
writing 'system'...
OKAY [ 47.582s]
finished. total time: 162.108s
It seems normal to me, but the problem arise when I restart the the phone. The phone unable to boot, and when I try
Code:
ADB Shell
It says somethings like "sh" is not found. So I do reboot recovery go to the shell and mount /system. Shockingly there is nothing in there.
I have checked the contents of system.img, and there is a lot of things in there, including the "sh". But it seems fastboot failed to flash the system partition.
Anyone can help me ?
Click to expand...
Click to collapse
ur work is simple...just plug in ur phone in fastboot mode...keep a boot.img file in the same folder that that of the fastboot folder....boot.img can be taken from ur STOCK ROM
and type ==
fastboot devices
then ur device will be shown.....
then type
fastboot flash boot boot.img
n its done!
I stuck with my Mate 9 Error mode numbers 11 and 2
MEGHSHAH said:
ur work is simple...just plug in ur phone in fastboot mode...keep a boot.img file in the same folder that that of the fastboot folder....boot.img can be taken from ur STOCK ROM
and type ==
fastboot devices
then ur device will be shown.....
then type
fastboot flash boot boot.img
n its done!
Click to expand...
Click to collapse
I would like to tell you my problem, I have a Mate 9 MHA-L09C605B111 which I did a rebrand a while ago and I'm with CUST 432 and installed the version of Oreo 8.0.0.368, a few weeks ago I received the update 369 via OTA. It was interesting to try; the problem is that I had open bootloader, TWRP Pretorian 3.2.0 and Root, take a terrible decision to do a relock of the bootloader.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in a tutorial
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.
Related
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
raystef66 said:
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
Click to expand...
Click to collapse
I have try also boot , try everything, not matter if youhave FRP lock fastboot oem unlock is only to unlock bootloader, which i have, that is not a problem.
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
joyrida12 said:
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
michalss said:
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
Click to expand...
Click to collapse
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
stiggu said:
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
Click to expand...
Click to collapse
same problem on my mate s
good to know that adb is not working for others
i thaught it was just me
I've the same problem , any idea ??
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Hey , the problem is the device won't boot , so how can we enable developer option?!!!!
Sent from my iPhone using Tapatalk
There was a time when xda where the place to get the right answer and quick!
nowadays most topics are full of people with same problem and no dev to come to help, pity.
on topic: I have the same problem, ( mine is a Y6 pro) and before bricking it I had debugging and oem unlock enabled but now can't flash boot etc using fastboot ( error , denied ..) and can't use spflashtools either : preloader vcom appears for 1 second and then disappears and phone turns on.
tried many drivers, 3 Os'es (7, 8.1 ,10) still no luck.
porcha18 said:
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Click to expand...
Click to collapse
Danke!!!!!!!!!!!!! Nach ewigem Suchen diese einfache Lösung. Vielen Dank!! Tag gerettet
the same issue
Good day, i have the same issue on my p9 EVA-L19.
FRP lock. And i can't do anything...
My warranty says that they cannot recover data from the phone, but the information is very important. I need to unlock FRP and somehow boot into TWRP or something to recover my data.
Please help someone if you had a same issue and results.
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Runner85sx said:
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Click to expand...
Click to collapse
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
anditan said:
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
Click to expand...
Click to collapse
your recovery location in adb is wrong probably. try changing it to the correct path. atleast thats what worked for me
man u can'T do anything because FRP is ACTIVATED !!!
No solution till now
Use the Huawei Swype bypass Method
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
Try to do:
fastboot boot recovery.img
This will boot up the device with the given image. With that you can put a custom rom to your sd-card and flash it.
I will upload a Nandroid (stock system, recovery, boot) from my Y6 SCL-L01 soon.
With that you can restore boot and recovery with twrp. For this way you don't need to have a frp unlock.
Procedure:
fastboot boot recovery-twrp.img
Put your stock firmware (dload folder) to the sdcard.
Put my Nandroid to your sdcard.
Restore my Nandroid, reboot your device with Vol+ and Vol- pressed.
This way only works for SCL-L01 up to SCL-L04.
I need to create an extra recovery.img that includes a dt image that fits for all SCL variants.
Work in progress...
I have just removed frp today, but its not free method, unfortunately
Hello,
I soft-bricked my Padfone A86 when I tried to flash my own kernel using TWRP 2.7.1.1. Before that I was running a rooted Android 5.0.2 (fw version WW-12.4.0.59) with TWRP recovery that I installed like described in an article at padfoneclub.com.
Installing the custom ROM damaged (at least) the boot and recovery partitions. That means I only have access to fastboot which I can not use to flash to those partitions:
Code:
fastboot flash recovery twrp-2.7.1.1-unofficial.img
target reported max download size of 1879048192 bytes
sending 'recovery' (10124 KB)...
OKAY [ 0.321s]
writing 'recovery'...
FAILED (remote: Security is Enable, close 'flash' function !!)
finished. total time: 0.338s
The remote: Security is Enable, close 'flash' function !! error must have been introduced by a patch to the bootloader because I don't recall having this issue when I first flashed TWRP back then when I was running some previous firmware version.
What I can do though is to boot the boot.img (only from fw versions 10.12.3.116 and 10.12.3.130) like this: fastboot boot boot.img
Using saferoot I managed to get root access which enables me to write to the recovery and boot partitions like this:
Code:
dd if=/sdcard/twrp-2.7.1.1-unofficial.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=4096; sync;
Although I can confirm that the memory gets changed using the dd command the bootloader neither loads recovery nor the system on the boot partition.
I looked at a hexdump of the recovery partition and it seems like the only thing stored in it is the TWRP image followed by zeroes. Trying different block sizes didn't help neither.
Confusingly that method seemed to work for some people. Maybe TWRP requires to be written over some stock recovery and can't boot on its own?
I was only able to try to flash the stock recovery for fw versions above 10.12.3.13 as ASUS only included patch-files for the recovery partition before. That didn't work neither. I was assuming that the recovery is running on its own and does not depend on being the same version as the system (or the bootloader). Or might there be something on a different partition that prevents the recovery from working properly?
Booting into recovery results in getting into fastboot mode (fastboot continue doesn't help).
Booting the system stops at the bootloader which shows the error message: ERROR: Can not load Invalid boot image!!
The frustrating thing is that although I seem to have full access to the device memory I still don't manage to fix the recovery partition.
Any help or ideas would be greatly appreciated.
Thunder Storm said:
Hello,
I soft-bricked my Padfone A86 when I tried to flash my own kernel using TWRP 2.7.1.1. Before that I was running a rooted Android 5.0.2 (fw version WW-12.4.0.59) with TWRP recovery that I installed like described in an article at padfoneclub.com.
Installing the custom ROM damaged (at least) the boot and recovery partitions. That means I only have access to fastboot which I can not use to flash to those partitions:
Code:
fastboot flash recovery twrp-2.7.1.1-unofficial.img
target reported max download size of 1879048192 bytes
sending 'recovery' (10124 KB)...
OKAY [ 0.321s]
writing 'recovery'...
FAILED (remote: Security is Enable, close 'flash' function !!)
finished. total time: 0.338s
The remote: Security is Enable, close 'flash' function !! error must have been introduced by a patch to the bootloader because I don't recall having this issue when I first flashed TWRP back then when I was running some previous firmware version.
What I can do though is to boot the boot.img (only from fw versions 10.12.3.116 and 10.12.3.130) like this: fastboot boot boot.img
Using saferoot I managed to get root access which enables me to write to the recovery and boot partitions like this:
Code:
dd if=/sdcard/twrp-2.7.1.1-unofficial.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=4096; sync;
Although I can confirm that the memory gets changed using the dd command the bootloader neither loads recovery nor the system on the boot partition.
I looked at a hexdump of the recovery partition and it seems like the only thing stored in it is the TWRP image followed by zeroes.
Confusingly that method seemed to work for some people. Maybe TWRP requires to be written over some stock recovery and can't boot on its own?
I was only able to try to flash the stock recovery for fw versions above 10.12.3.13 as ASUS only included patch-files for the recovery partition before. That didn't work neither. I was assuming that the recovery is running on its own and does not depend on being the same version as the system (or the bootloader). Or might there be something on a different partition that prevents the recovery from working properly?
Booting into recovery results in getting into fastboot mode (fastboot continue doesn't help).
Booting the system stops at the bootloader which shows the error message: ERROR: Can not load Invalid boot image!!
The frustrating thing is that although I seem to have full access to the device memory I still don't manage to fix the recovery partition.
Any help or ideas would be greatly appreciated.
Click to expand...
Click to collapse
Try getting rid of the bs part. Flash the image at it's normal size.
Sent from my XT1609 using Tapatalk
Thanks for your reply.
I flashed both TWRP and stock recovery without the bs parameter. Same results as before: it doesn't boot into recovery.
I extended the given TWRP from s3tupw1zard ported by Thinhx2.
You can now use the adb root access while the TWRP booted and access your phone with mtp when it is not encrypted.
It is a self booting image now, means, this boot file only boot direct to TWRP.
NEVER flash this image direct to flash with fastboot flash boot, you cannot start android then, only TWRP.
Boot it, while your smartphone is in fastboot mode, with the command:
fastboot boot self_bootingTWRP323.img
Then you can do everything like in the flashable version of TWRP, only with the advantage that you are not security patch dependent and you don't need to modify your original system.
You can install all ZIP files, like Magisk or open-Gapps.
After reboot the smartphone starts normal from the boot partition inside the smartphone and twrp is gone.
Tested in 00EEA platform only but i guess it will also run on 00WW!
Lol, what's the difference between each of these 4 parts. No statement about it. Lack of info may confuse users.
Its one rar image divided into 4 parts because upload size is limited!
page1875 said:
Its one rar image divided into 4 parts because upload size is limited!
Click to expand...
Click to collapse
How could I combine it all?
Download them all, put them to the same folder and extract the first image.
Then the rar extractor will take the following images automatically!
How to decrypt Nokia 3.2 using TWRP.
page1875 said:
Download them all, put them to the same folder and extract the first image.
Then the rar extractor will take the following images automatically!
Click to expand...
Click to collapse
Works perfectly. If you want to decrypt your Nokia 3.2 you will be needing to format your data partition using TWRP. But your device will be encrypted again (if you didn't do (perhaps) any backup or used commands like "adb push") once it booted up.
I tried it after unlocking bootloader but it just goes to black screen and nothing is happening, only solution is holding power button and it reboots normally. here's the command output:
[email protected]:~# fastboot boot /mnt/q/twrp/self_bootingTWRP.img
downloading 'boot.img'...
OKAY [ 0.962s]
booting...
FAILED (status read failed (No such device))
finished. total time: 6.614s
I'm on android 9 (no updates applied), phone is TA-1164. build number: 00WW_1_08D.
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
Hey all,
I have a new z5c running 32.4.A.1.54 stock.
I flash TWRP (I have tried a few different versions) using Fastboot on Ubuntu20.04, it all runs fine no errors, and appears to flash as it should.
But the phone will not load TWRP, from the phone itself, I have tried a million different ways.
The only way it loads is by
fastboot boot twrp.img
But when I do this .. android will not then start .. hangs on Sony logo
I have to reflash the stock rom to get it to work again
If I run
fastboot reboot recovery
I get:
fastboot: usage: unknown reboot target recovery
even tho:
fastboot devices
correctly identifies the device
I would like to root and use custom rom, but have not yet been able to get past this TWRP hurdle
Has anyone experience of this, or any ideas?
You've flashed TWRP in a wrong way! Please search for help in my several ROM threads.
Well, thanks for your answer, really, I appreciate it
But I have flashed it again and again and followed your threads and other threads
I'm not a newbie, i have flashed TWRP and roms to a few phones, inc Z1C and a couple of Z3Cs
I have adb, and fastboot installed
Bootloader unlocked
USB debugging
Recommended stock
I have downloaded multiple .img files, including your 3.6.1 version
I run fastboot
and
fastboot flash recovery twrp.img
The phone will not reboot into TWRP, using buttons nor fastboot, only into android, unless I then run
fastboot boot twrp.img
Then TWRP runs, but when I then reboot, I just hit the SONY logo if I have not flashed a ROM or a bootloop if I have.
And from there will not return to TWRP at all.
What am I missing?
I'm very confused as everything you're talking about is working here and for other users flawlessly.
Really, I don't know what's wrong at your side.
Berni-0815 said:
I'm very confused as everything you're talking about is working here and for other users flawlessly.
Really, I don't know what's wrong at your side.
Click to expand...
Click to collapse
Yes, that makes 2 of us!
Ugh.
Did you try what I told you in this post?
With that, LineageOS 19.1 MUST boot up!
If not, I don't know further...
Berni-0815 said:
Did you try what I told you in this post?
With that, LineageOS 19.1 MUST boot up!
If not, I don't know further...
Click to expand...
Click to collapse
I did try that as recommended, thanks
I am flashtool-ing back to the stock again, after being again stuck on boot with TWRP inaccessible
I will give it one last go
Thanks, man
How do I buy you a coffee?
That's all really weird; since it works here since years.
From a fresh fully-functional stock install
Following this simple process exactly
Devices with only TWRP.IMG
If your device only has the IMG file, then execute the below command: fastboot flash recovery twrp.img
Now execute the below command to boot your device to the TWRP recovery. fastboot boot twrp.img
Once it boots to TWRP, you could then boot it to the OS, via the Reboot > System option in TWRP.
From here;
https://www.getdroidtips.com/flash-twrp-recovery-android/
After 3. it gets to SONY logo and hangs
Same every time
Obviously not a problem with your or any other custom ROM
The only way out from here is to Flashtool the stock again
Geez
I'm giving up on TWRP and custom ROM
I'll go for the rooted, debloated, degoogled stock as best as I can get it
Thanks v much for the support!
I've NEVER used the command
Code:
fastboot boot twrp.img
I've always flashed TWRP like this:
Shutting down device
Waiting some time
Pressing volume up and plugging usb cable
Enter this command in a terminal window:
Code:
fastboot flash recovery TWRP_3.6.1_9-0-recovery_suzuran_2022-03-09.img
After unplugging the usb cable and waiting some time I rebooted into TWRP by pressing power and volume down simultaneously.
That worked since years flawlessly!
Berni-0815 said:
I've NEVER used the command
Code:
fastboot boot twrp.img
I've always flashed TWRP like this:
Shutting down device
Waiting some time
Pressing volume up and plugging usb cable
Enter this command in a terminal window:
Code:
fastboot flash recovery TWRP_3.6.1_9-0-recovery_suzuran_2022-03-09.img
After unplugging the usb cable and waiting some time I rebooted into TWRP by pressing power and volume down simultaneously.
That worked since years flawlessly!
Click to expand...
Click to collapse
That command is the only way that twrp has loaded for me
Right .. deep breath ... one last go at this using yr suggestion,
thanks
Nope
Same again
All goes as it should
Power and volume down simultaneously
Boots into Android
adb reboot recovery
Also boots into android
If I was now to run
fastboot boot twrp.img
It would run TWRP the one time, but just hang on SONY logo when rebooted
Ho hum.
kaivalyam said:
Power and volume down simultaneously
Boots into Android
Click to expand...
Click to collapse
That SHOULD NOT happen if you've flashed TWRP in the only right way.
I'm sorry, but I don't believe that...
Berni-0815 said:
That SHOULD NOT happen if you've flashed TWRP in the only right way.
I'm sorry, but I don't believe that...
Click to expand...
Click to collapse
Well, its not a particularly complicated process
I have described exactly what I have done
I have done it multiple times
And that is what happens
As I said: I've never seen that and that's not reported very often by other users.
And if, then it has been an error in flashing.
Highly unlikely that you're devices so called FOTA partition is damaged so that the command
Code:
fastboot flash recovery <name of the recovery image>
fails.
Code:
fastboot flash boot <name of the boot image>
flashes the boot partition and that's not the same as the FOTA partition.
I have to believe you but somehow I can't.
I understand
fastboot flash recovery <name of the recovery image>
Doesn't fail exactly ... it runs fine .. no errors
Code:
~/Dev/Z5/twrp/3.6.1$ fastboot flash recovery TWRP_3.6.1_9-0-recovery_suzuran_2022-03-09.img
target reported max download size of 536870912 bytes
sending 'recovery' (22668 KB)...
OKAY [ 0.570s]
writing 'recovery'...
OKAY [ 0.395s]
finished. total time: 0.965s
But then the phone will only boot android
~~~
Unless
I run;
fastboot flash boot <name of the boot image>
Again, runs fine .. no errors
Code:
~/Dev/Z5/twrp/3.6.1$ fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.552s]
booting...
OKAY [ 0.561s]
finished. total time: 1.113s
This boots TWRP but then after that the phone hangs at boot and will neither start Android or TWRP
It is indeed very strange.
Look at your own code:
Code:
~/Dev/Z5/twrp/3.6.1$ fastboot boot twrp.img
downloading 'boot.img'...
From where is boot.img downloaded? And where is it stored internally?
Have you flashed system.img too?
There goes something terribly wrong at your side.
Thanks for your patience
Yes I'm sure you're right, probably user error, although I am having trouble seeing what that is exactly ...
So, using Ubuntu, I am in the directory that contains the twrp.img file (most times I have renamed it this)
Is that correct so far?
From there I run
fastboot flash recovery twrp.img
All good, as above, but TWRP does not load, ever, using buttons or adb, unless I then run
fastboot boot twrp.img
TWRP then runs
But the phone will not boot into anything from there
Yes, I thought that was a little odd ...
"downloading" : I assumed it meant it was transferring the file across, or accessing it, from my pc to the device
"'boot.img" : I assumed fastboot had changed the filename to what it needed it to be ...
Is the problem around this?
You can name the recovery image file as you like it to be named.
Have you disconnected the USB cable after flashing?
Have you waited some time before trying to boot anything?
If you can boot TWRP, you can fetch a LOG file at the "Advanced" menu. Please send me this LOG file via PM (it may contain personell data!).