How to repack mini rom? - Android Q&A, Help & Troubleshooting

i repack miui rom by “make_ext4fs”,i got the system.img, then flash it with fastboot mode, The phone is not boot and is restarted to fastboot mode, so i remove the dm-verify from boot.img by magiskboot and flash boot.img. Now the phone can boot, but wifi does not work. Please tell me which step is wrong. los15.1 works fine by this way. thanks!

Related

I can't flash back stock rom :(

Hi everyone I have a big problem I make backup of my stock rom (boot.img, recovery.img, etc.) and now I try to flash it back but it say error and bad size
My device: Colorovo citytab lite 10" (RockChip RK3168)
Sorry for my bad English.
You have to flash the .img files with fastboot.
For the boot its: fastboot flash boot boot.img
For the recovery its: fastboot flash recovery recovery.img
I'm trying to toggle on fastboot but I can't see device in "fastboot devices"
Now I'm on logo screen(not animation) but I can't boot. Only works recovery, adb and bootloader :/

Phone Bricked - Need Hand Holding

I installed the 135 update for my BLA-L29 (C605) Mate 10 Pro and noticed the face lock got really slow after I flashed HyperX Kernel. I then thought I found a stock kernel for the Mate 10 Pro and flashed it. Now I cannot get past the boot screen, I cannot get into TWRP, eREcovery isn't able to wipe my phone, error trying to update, all the fun! I can get to fastboot no problem and my phone shows "Phone Unlocked," and "FRP Unlock." Bootloader is unlocked and I'm pulling my hair on trying to figure out how to get it back to the 135 update which was running just fine until I decided to get cute with Hyper X. I'm at the brink of buying credits through Funky but I don't want to do that. Can someone please walk me through how to unbrick using DC Phoenix. I've got the 135 update file downloaded but could use some more help. Thank you!
can you descripe the step, how you flashed the kernel? Over fastboot in this form: fastboot flash kernel filename.img? or fastboot flash boot filename.img? fastboot flash kernel filename.img is the correct one. But if you have flashed it to the boot partition (fastboot flash boot filename.img) then you need to find the stock boot partition. Follow this thread and unpack kernel.img and boot.img. Then flash kernel.img in this form: fastboot flash kernel kernel.img and boot img in this form fastboot flash boot boot.img

Partition Problem in Redmi Y3

Help me, my phone's boot partition problem.
When i try to flash boot.img file using 'Minimal ADB and Fastboot' then it flash stock boot.img even i changed this file.
Means,
Stock Boot.img file of Redmi Y3 is 64mb
I copy custom Boot.img file(15.20mb) to Minimal ADB folder and flash this but i won't get custom Boot.img, i get stock boot.img of 64mb.
After this,
I Booted to Twrp Recovery and Try to flash Boot.img from here but i get this same problem again.
I Erased Boot Partition using Minimal ADB Tool and After this when i Booted to twrp and go to Backup then i see Boot(64mb).
When i Erased Boot.img It should be seen 0mb in Twrp but i see anytime it is 64mb help me please
you has bootloader unlocked?
Boot Partition Problem Solved
My Boot partition problem is Solved now !!
I flashed original rom miui 10.3.2 rom and after successful reboot, i flashed custom rom and new boot animation is coming in screen ???

[Unofficial][Q]Twrp Recovery for Xperia 1/5 On Android 10

Hello dear people !! ^^
Since we have in a short time Android 10
We don't have recovery for it.. Sadly enough but..
I found this on a chinese forum and make a guide of it.
I don't own the Xperia 1.. Not yet but next week i have one,
So i hope all you people understand this guide because i
explained it as far i can do it.
----------------------
.. Requirements ..
Unlocked bootloader
Xperia 1 Or 5
Android 10
Knowledge howto flash
----------------------
Important !!: rename your patched boot.img what you did
with magisk to kernel.img in put it in this zip Here
1: Remember to back up all your data
2: Make a clean install of the firmware,
!! don't boot after flashing !!
3: Turn the phone into fastboot mode
and connect and type this command in cmd window:
fastboot flash boot twrp-xperia1.img
Here the fastboot twrp file
4: fastboot this command of vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Here the vbmeta file
5: Press and hold the volume down and power at the same time,
release the powerbutton but keep
pressing volume down button till you enter twrp.
6: Copy the 3 zips:
The boot.zip where your own kernel.img is inside
what you did at the beginnig of these steps
twrp-Xperia1-3.3.x.zip: Here
Magisk-v20.1.zip: Here
to the phone storage, and flash in twrp
7: Start it up and done
Note: If you encountered
damaged internal storage, format internal memory in twrp
and all went just fine.
... Credits ...
M-Rom
​
Res
This doesn't lead to success with an Xperia 5. Once you try to boot into TWRP at step 5, you got a note that the device is corrupt and will shut down in 5 seconds.
Thanks ASap people try this I will install and try it! Know bug? Is this still in very testing version? For the moment I don't want to touch my device.
The clean install is necessary? Any incompatibilities with some magisk modules? Im currently using: smali patcher, taichi, youtube vanced
Why isn't there a Thread in the Xperia 5 Forums? Just found this out of Luck...
Instructions are also bit confusing... Where is the vbmeta.img from? Google? And why do i need a boot.img if we have already a TWRP boot.img? Will the one boot.img not replace the other?
Flashing a new Firmware makes also no sense if you just do "fastboot -w" to erase all Userdata. (If coming from a clean Firmware like i do, or You do right after unlocking Your Device)
Edit: So in a nutshell
-We do boot up the twrp boot.img to be able to flash Zips!?
-We do flash vbmeta to unsecure our booting!?
-We do flash our own boot.img with the Zip that the Device can work right!?
-We do flash the TWRP Zip which edits our Ramdisks to add TWRP
-We do flash Magisk (Optional!?) for only Root? Or also needed Kernel changes!?
Would be nice to also make links to XperiFirm and UnSin to get the boot images...
You could also edit the boot.zip script for "magisk_patched.img" so users don't have to rename it
Just want to support that btw. Thanks for Your work anyways!
---------- Post added at 15:47 ---------- Previous post was at 15:07 ----------
Xperia 5 booted well into TWRP but it freezes everytime i start a flash or wipe. Got the storage to work with fastboot -w after flashing the twrp and vbmeta images. Adb Sideload does also not work. Looking forward to a working version!
TWRP unable to flash zips
Well, the title says it all. I can flash the twrp image, but it freezes when flashing zips or starting sideload. I'm using a J9110. I understand you're not supporting here, but just in case you had some tips. Oh and by the way, hoi vanuit Leiden
EDIT: Found the fix: don't change the language to english before opening twrp, and it will flash just fine!
xperia 5 fix plz
I've installed this, it work but boot in chinese and cant load the usb mtp driver on my pc, I cant move the boot.zip to flash, had it put on sd card, cant find the sd card on this crappy twrp, for me is a no. I'd just stick with patched boot until something better will work.
mtp should work if you follow every instruction and boot twrp in chinese.
Having the same issue as others... it appears as though the internal storage is encrypted, but I have no lock screen enabled in the ROM. No Passwords or Fingerprint either. Tried wiping data from within TWRP froze the system. Performed a wipe from within ROM, and now the ROM shows internal data folders as though they're encrypted. Need a pinch of help here.
This method has problem if 55.1.A.3.149 is flashed. The "Start" screen freeze with no touchscreen function on reboot after the procedures completed.
Is there any update to this?
Hopefully with 3.4 will bring a more stable twrp. It includes changes for devices updated to Android 10
I hope can teach how to get your patched boot.img
It's not too much complex to make it work
download firmware from xperiFirm
unsign the boot.sin to get boot.img for your xperia 1
flash the twrp.img to your boot slot_a/b
boot into twrp
install the boot.img, twrp.zip, magisk.zip
now everything works
benben233 said:
I hope can teach how to get your patched boot.img
Click to expand...
Click to collapse
It's not too hard to get one
Get the origin boot.img from xperiFirm, twrp.zip
boot into any twrp on any device
backup your own boot paritition
install the boot.img, twrp one by one
then backup the boot partition, you get the patched-boot.img
Tenhow.XDA said:
download firmware from xperiFirm
unsign the boot.sin to get boot.img for your xperia 1
flash the twrp.img to your boot slot_a/b
boot into twrp
install the boot.img, twrp.zip, magisk.zip
now everything works
Click to expand...
Click to collapse
On latest android 10 and fw .28 it works ? @Tenhow.XDA
Any sign of Android 11 TWRP for Xperia 1?
MrMmmkay said:
Any sign of Android 11 TWRP for Xperia 1?
Click to expand...
Click to collapse
No

Fatsboot boot bug (phone doesn't boot)

Hello!
Now I have a trouble with my Nokia 7.1.
When I try to boot twrp or another kernel (boot.img) it stuck. I do '"fastboot boot twrp.img" or "fastboot boot boot.img" and my phone frozes on Android One logo.
And if problem with twrp can be solved (first enter "fastboot flash recovery twrp.img" and only than "fastboot boot twrp.img"), problem with boot.img is still relevant.
I noticed, that after "fastboot boot ..." phone restarts into download mode.
My phone is unlocked.
Thank
Hi, before any boot command, you'll need to do that flash recovery counterpart. You can do it on a standard boot image as well, not just TWRP. There's no recovery partition, so, nothing gets flashed. But it somehow allows us to boot our bootable img files.
So,
Code:
fastboot flash recovery boot.img
fastboot boot boot.img
singhnsk said:
Hi, before any boot command, you'll need to do that flash recovery counterpart. You can do it on a standard boot image as well, not just TWRP. There's no recovery partition, so, nothing gets flashed. But it somehow allows us to boot our bootable img files.
So,
Code:
fastboot flash recovery boot.img
fastboot boot boot.img
Click to expand...
Click to collapse
Yes! Thank you.
I recently came to this conclusion, but what is it?
Does it bootloader bug or anything else?
i have similar problems and just started a new request

Categories

Resources