I am new to xda developers community. I bought a brand new HCL ME X1 Android 2.3.3 gracious Gingerbread Tablet.
I rooted my Android 2.3.3 Tablet, and I have installed ClockWorkMod Recovery 5. I want to be prepared to flash my own built images via Fastboot. But I do not know how. How to dump Fastboot format ( .img ) images and by using which tools, so that I could use these images to restore/upgrade via Fastboot especially. Currently I am afraid to replace the OS because I do not have enough safe backup images. Please, guide me regarding this serious problem as I want to prepare my Tablet to use both the tools in case of emergency, and I also want to upgrade my 2.3.3 to at least 2.3.6 or even 3.0. Those who would help me, I appreciate in advance. Also please tell me, if nanddump raw nand images can be used to restore my paritions and OS from FastBoot?
Tushar
I need your help
I have a Phicomm K390X and updating the systema has been locked.
I understand it is an old model and possibly discontinued this, but as I used to develop an app, need to recover full function ..
I was able to get the original update_all.zip but as starting Dload I can not work it off.
Need a rom to dump the system img from Winhex, but I find the way de locate.
you would be so kind as to give me a system image to restore img format?
or otherwise tell me how to repair it.
Thank you very much for your attention
image to see access to mobile from pc-linux
Dear specialists on the XDA,
Normally I ask no questions in order to save the precious time of people, however this time I have a problem which I fail to understand and cannot resolve using the documentation available on the internet.
I have committed extensive reading and know how to build software but am simply missing a link here.
Trying to boot a home build kernel on a oneplus7 pro device with no luck so far.
Here is the situation so far: I have after hours of headaches successfully built myself a kernel straight from the stock sources. No alterations just using the msm8150-perf.defconfig file and build successfully with clang 9.0.5. There are only a few warnings nothing serious and the dtb has many warnings but I get what I need. I have done this before for my oneplus 3 and indeed the kernel was working.
Assuming the kernel is in a functional state. I used the latest version of android image kitchen to unpack the boot image which I extracted (from the right active slot) and replaced the kernel file and repacked the boot.img successfully into a new image file.
No luck after trying to boot into the image using fastboot. Screen hangs forever. Bootloader is unlocked btw
So far I have tried:
1. Signing the boot image using boot signer
2. Unpack/repack using android image editor (which signs the image)
3. Repack using different kernel image files from xda which I expect to be good and working
4. Flash signed image straight into active slot.
5. Completely read through the anykernel1, 2 and 3 scripts to find answers.
No matter what I try. Kernel does not boot. Either the fastboot screen hangs forever or the system reboots back into its currently working active slot.
I have to add that this bootimage contains magisk.
I am out of ideas. Please help me out. I hope that you can point me into a good direction.
I have been trying to build a custom aosp based ROM for pixel 4a, I have made changes to few xml files that goes into vendor/etc/ folder. I built a script to extract vendor blobs from the official vendor image provided by google and also generated build instructions for corresponding files.
I'm able to build the vendor image successfully. All the vendor files are present in the custom built vendor img, when I checked.
After flashing the images, the phone gets stuck in google logo.
I have made sure that bootloader is unlocked., osp version and vendor build version match.
1. Is there a way to build vendor image? Is my approach correct?
2. How can boot loop be debugged? -- ADB is not available at this point of time in boot process.. I'm also not able to boot into recovery, I keep getting bootloader screen.
Any help, links, refs, guides would be helpful
If you are rooting after or during the build process both boot.img and vendor_boot.img files need to be patched. If you are at bootloader(fastboot) you can fastboot flash vendor.img etc
toolhas4degrees said:
If you are rooting after or during the build process both boot.img and vendor_boot.img files need to be patched. If you are at bootloader(fastboot) you can fastboot flash vendor.img etc
Click to expand...
Click to collapse
I'm able to flash the vendor image. I don't want to root the phone. When I use the official vendor image, the phone boots but not when I use vendor image that I built. Is there a way to build vendor image? or How can I debug boot loop?
toolhas4degrees said:
If you are rooting after or during the build process both boot.img and vendor_boot.img files need to be patched. If you are at bootloader(fastboot) you can fastboot flash vendor.img etc
Click to expand...
Click to collapse
Yes, he can use magisk manager to patch the image then flash them in fastboot mode using adb like you said
poppopret_ said:
I have been trying to build a custom aosp based ROM for pixel 4a, I have made changes to few xml files that goes into vendor/etc/ folder. I built a script to extract vendor blobs from the official vendor image provided by google and also generated build instructions for corresponding files.
I'm able to build the vendor image successfully. All the vendor files are present in the custom built vendor img, when I checked.
After flashing the images, the phone gets stuck in google logo.
I have made sure that bootloader is unlocked., osp version and vendor build version match.
1. Is there a way to build vendor image? Is my approach correct?
2. How can boot loop be debugged? -- ADB is not available at this point of time in boot process.. I'm also not able to boot into recovery, I keep getting bootloader screen.
Any help, links, refs, guides would be helpful
Click to expand...
Click to collapse
Did you already check the tutorials or how-to's available on XDA e.g. the tutorials of @AlaskaLinuxUser like
[Guide][Video Tutorial] How to build Custom ROMs and Kernels![10,P,O,N,M,L]
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it was helpful to you in your Android career! Praise...
forum.xda-developers.com
or
[Guide][Video Tutorial] Intermediate to Advanced Custom Rom and Kernel Building
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it is helpful to you in your Android career! Praise God...
forum.xda-developers.com
The XDA University might also be of good help:
XDA-University
Tutorials, How-To Guides and More. Learn about mobile phone development, hacking, flashing, rooting and many other topics!
forum.xda-developers.com
Just search a bit and you'll find much more.
I'm on a quest to root my Hisense A9 e-ink phone. There isn't a stock ROM available online, and my attempts at extracting the recovery.img or boot.img with an EDL client or through ABD have failed. So the next thing I can think of trying is bundling a TWRP build, or possibly borrowing the TWRP from a similarly architected device and seeing if I can boot into it (without flashing).
So is there a way to build TWRP for an unsupported device, when there's no recovery.img available?
Also, is it safe to ./fastboot boot recovery.img without risk of bricking the phone (ie., booting instead of flashing)? If so, then I can try existing TWRP builds for similar devices.
Alternatively, are there any other avenues for rooting a new device which has no available stock ROM? Or other possible workarounds to get Google Services working correctly? I've tried MicroG, but the Hisense A9's ROM doesn't support signature spoofing, and to enable support I need TWRP.
Here's a thread which details some of my failed attempts at getting the boot.img via the EDL client.
And some more details about the phone:
Hisense A9 / HLTE556N
Processor: Qualcomm Snapdragon 662
Android 11
Software version: L2037.6.03.11.00
Kernel: 4.19.157
A/B partitions
Thanks everyone!
Did you tried those experiments…..
I have same question…kinda….
As their is no twrp recovery for my device (vivo 1802 mtk device) I was thinking of booting into twrp recovery not made for my device specifically Without flashing it.
To get the job done maybe some backups or flashing using twrp. But I don’t know what will be the consequences of it…… If anyone got idea or hands on experience on it, I would like to know