Hello everybody,
I have rooted Doogee DG800 and i tried to use fastboot to boot custom ramdisk. But it didn't work. Fastboot downloaded kernel image and ramdisk but didn't boot the system. I also tried kernel and ramdisk from my current ROM but it also didn't work. Fastboot only says "booting..." and that's all.
PS : I'm doing this because I want to buy a cheap tablet with Allwinner A13 and install Debian on it. But I want to try it first on my phone.
Thanks for answers
Related
Hi. I'm new in compling cyanogenmod and
I successfully compile cwm for my device
1. I mean, If I test the custom boot.img and it won't boot or stuck in bootloop. (The boot part is broken).
Can I still boot into recovery after that?
I fear to test my compiled boot.
2. Can I test boot.img by 'fastboot boot boot.img' command? Will it work?
Last, My device is only sold in my country and no one made any custom rom or kernel for the device.
My device is ZTE-V817 that using CPU Qualcomm msm8225q.
The CPU is same as Blade V. I trying to use Blade V kernel for my rom.
Sorry for my bad english skill.
lenkyun said:
Hi. I'm new in compling cyanogenmod and
I successfully compile cwm for my device
1. I mean, If I test the custom boot.img and it won't boot or stuck in bootloop. (The boot part is broken).
Can I still boot into recovery after that?
I fear to test my compiled boot.
2. Can I test boot.img by 'fastboot boot boot.img' command? Will it work?
Last, My device is only sold in my country and no one made any custom rom or kernel for the device.
My device is ZTE-V817 that using CPU Qualcomm msm8225q.
The CPU is same as Blade V. I trying to use Blade V kernel for my rom.
Sorry for my bad english skill.
Click to expand...
Click to collapse
there is recovery.img for recovery mode
Vaibhav Chauhan said:
there is recovery.img for recovery mode
Click to expand...
Click to collapse
Thanks for reply.
I mean, It not require boot before recovery right?
lenkyun said:
Thanks for reply.
I mean, It not require boot before recovery right?
Click to expand...
Click to collapse
right
The boot.img (i think you are talking about a kernel image) is independent from recovery.img (your image). If you flash a bad kernel for your device it will stuck on bootloop but you can access download mode/emergency/recovery etc. There is no problem is you mess up your kernel the flashing command from fastboot is usually : fastboot flash boot boot.img (you must have the boot.img in the same folder as fastboot). Good luck my friend.
christi9503 said:
The boot.img (i think you are talking about a kernel image) is independent from recovery.img (your image). If you flash a bad kernel for your device it will stuck on bootloop but you can access download mode/emergency/recovery etc. There is no problem is you mess up your kernel the flashing command from fastboot is usually : fastboot flash boot boot.img (you must have the boot.img in the same folder as fastboot). Good luck my friend.
Click to expand...
Click to collapse
i'm also saying that
zte v817
lenkyun said:
Hi. I'm new in compling cyanogenmod and
I successfully compile cwm for my device
1. I mean, If I test the custom boot.img and it won't boot or stuck in bootloop. (The boot part is broken).
Can I still boot into recovery after that?
I fear to test my compiled boot.
2. Can I test boot.img by 'fastboot boot boot.img' command? Will it work?
Last, My device is only sold in my country and no one made any custom rom or kernel for the device.
My device is ZTE-V817 that using CPU Qualcomm msm8225q.
The CPU is same as Blade V. I trying to use Blade V kernel for my rom.
Sorry for my bad english skill.
Click to expand...
Click to collapse
hey,do you still have the original Rom of zte v817 i want your help really man...save me ;s:angel:
Hi there,
i am newbie at xda-developers and posting this thread to get you android engineere help to unbrick my cdma android phone.
last yesterday, i've tried to to install custom rom in my phone by using adb sdk.
my hardware is QRD
brand model is MTS MTAG353 Coolpad 5210
Android version 2.3.5
Iast week i planed to change its rom and download a cwm7.1 Custom rom compatible with android 2.3.5.
i'd took backup of my original rom before flashing files of cwm custom rom. and start flashing files of cwm.
i'd first flash recovery by adb command "flastboot flash recovery recovery.img" and then flash "fastboot flash boot boot.img"
And after that use command "fastboot reboot" (mistake i did).
then my phone reboot, mts logo image appear and then black screen. My phone connected with pc but no usb port show that my android device is connected.
now i am confuse what to do. As adb don't show my device connected with pc. I've backup of my last used boot and recovery file. But i don't know, how to re-flash them.
so guys, if there is any solution reply me as-soon-as possible.
Hello. Please i need help.
I have a Mediatek device with a secured boot.img i have been trying to make it unsecured by changing ro.secure in default.prop
when i repack the boot.img and flash it with SP Flash tools the device does not boot at all. (reboots at first splash)
Can anyone help me do it properly? i'll really appreciate your help.
Also Auto TWRP and CWM installers do not work for the device so if anyone can assist me with building TWRP or CWM for it i'll be grateful
this is a link to the boot.img and recovery.img:
https://drive.google.com/open?id=0B39xYnt0Q7O0YktFaXE0NnVRSkk
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 :/
I'm trying to port TWRP to my Ulefone Armor x10 on the way to de-googling it.
I have extracted the boot.img from the official zip from the website, and then used https://github.com/twrpdtgen/twrpdtgen to generate a basic device tree.
I then downloaded the device tree for the Armor X5 from here, https://github.com/SPRATAY/android_device_ulefone_x5_armor
and compared the two,
i then built TWRP using the minimal manifest guide: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
I get the build to finish OK, but when I try to boot via
fastboot boot mytwrp.img
i get
FAILED (Status read failed (Too many links))
and if i flash with
fastboot flash boot mytwrp.img
the device just bootloops endlessly with nothing on the screen.
How can I debug TWRP builds to see why its failing?
My phone has bootloader unlocked and flashed null vbmeta
Am I on the right path here? there seems to be not many Mediatek 6762 devices running android 11+ with recovery in boot ramdisk.
Is there a great guide on porting TWRP?
Thanks!
OK, i will reply here incase anyone else picks this up online.
I followed lots of guides suggesting USB drivers, bad ports, old ADB versions, it seems its a generic error.
I tried fastboot boot with the stock image I dumped from the phone and that also failed, so I realised its just a generic problem.
It was also the problem given by the broken TWRP i ported when I flashed it onto the phone.
I knew flashing the stock boot image with fastboot flash boot stockboot.img worked, so I then unpacked stockboot with Carliv image kitechen, added a single text file as a text, rebuilt it, and flashed it to boot and the phone booted fine.
I then found a closer match of TWRP and followed the porting guide https://techsbyte.com/how-to-port-twrp-to-a-b-partitioned-devices-mediatek/ and got a version to boot.
The storage partition still doesn't work, I will reply if I get a working TWRP for this phone with a link.
Leaving this incase someone else is trying to port TWRP and gets a similar error.