I was bored and I tried to adapt an Android 8.1 firmware rom from the same chipset to my device and as I see it System is working just fine but boot is completely wrong since I don't know how in world they adapt the boot img when there's no already existing boot for that android sdk in a device
Related
hello everyone i need help with my mediapad 7 lite , i been searching for months and have not been able to install a single recovery like cwm twrp etc. would someone tell me what is going on , most guides stuck at fastboot and waiting for device . why is there so much shadyness would anyone post a good solution with tools etc? mediapad 7 lite s7-932u. well i hope i get a solution , i want install android lollipop , and by anymeans is there a rom for the bios to make the processor quad or dual . as simple as formating windows 98 or xp please.
I am sorry if you don't like my answer as I know your device is not the same as this TWRP but you may like to port it? or compile it?
I think you need to root your device as well otherwise you may struggle.
http://forum.xda-developers.com/showthread.php?t=2693100
Note this is tested on S7-931W while your post shows you are keen to get s7-932u.
If you use Linux you can download that TWRP, unpack it with imgRePackerRK
http://forum.xda-developers.com/showthread.php?t=2257331
then use Android to get info on where your recovery is and take a backup image of it
copy your stock recovery to Linux, unpack it with same tool as above, then swap in your kernel into TWRP and adjust the fstab and a few text files to match your ids
repack modified TWRP with imgRePackerRK and flash it.
making sure you have kept a backup on your removable sdcard.
good luck
Re:Stock or Custom ROM flashing with TWRP...
Let me preface this to say that I am a "noob" when it comes to all things Android,that being said I need some helpful replies re:flashing (with Windows 7 64 bit PC or Smartphone...)a custom or stock ROM (if TWRP is to flash the image,will need a zipped ROM)to an Alcatel One Touch Fierce XP-5054N smatphone that has mysteriously lost Android 5.1.1 Lollipop after downloading,installing TWRP recovery app /) ; after installing TWRP recovery , i noticed that "TWRP" had erased my Android OS so I will need a download link (or ?) for a good Stock Alcatel 5054N ROM or custom ROM copy that is compatible with the aforementioned smartphone...
I will also need to know the best way to reflash/install Android 5.1.1 (or later android OS version)...to my Alcatel(i prefer to install via the smartphone since the smartphone has issues being recognized by any windows adb drivers(well,the smartphone shows up in windows explorer when connected to a USB 2.0 port,but any PC based flashware i've tried cannot find my smartphone!?!?)
Thanks in advance for a pertinent reply!!
In the developer options I have started uploading the GSI ARM64 dynamic system.
I was quite surprised by the possibility.
I'm on Miui Global 12.5.2.0 and AOSP Android 12 was loaded into the second slot automatically and without selection.
Starting the function started the upload and after the upload the prompt to reboot into the other system remained in the top bar.
The reboot went without problems and loaded the AOSP ROM Android 12 in a clean basic environment.
The top bar continued to hold a link to reboot back into Miui.
I returned to a pristine and fully functional Miui system (including settings and data).
The top bar still held a link to reboot into AOSP or remove it. I removed it.
This means that our phone can run two independent systems, one in slot "A" and one in slot "B". These are not virtual slots, but physical slots.
This could be relevant to building recovery.
I can confirm that. figured that's before.
Steps on booting the Android 12 on DSU? I'm using pixel experience and I tried to load the PB4 on DSU but it boots me into an android 11 environment. Does it only work on stock rom?
It could be related to the 12.5.2.0 update.
Presumably the vendor and others will be ready for Android 12.
The firmware package does not include the vendor file, it is obtained by installing the entire Miui ROM or by extraction. Firmware is therefore not enough for change.
StaryMuz said:
It could be related to the 12.5.2.0 update.
Presumably the vendor and others will be ready for Android 12.
The firmware package does not include the vendor file, it is obtained by installing the entire Miui ROM or by extraction. Firmware is therefore not enough for change.
Click to expand...
Click to collapse
i think it only works on stock rom. I installed 12.0.11 and used the DSU loader there. worked fine but the side mounted fingerprint sensor gets treated as a touch input. Could be the custom rom doesn't have the proper dsu config and stuff? Havent tried yet on xiaomi.eu
A little experiment:
I switched in Miui 12.5.2.0 using DSU Loader to GSI ROM. From developer.android.com I downloaded the Android 11 GSI ZIP and took the vbmeta.img from it. Then he downloaded IMG for Lineage OS 18.1 GSI from XDA. I switched the phone to fastboot and flash files (fastboot flash vbmeta vbmeta.img); (fastboot -w flash system system.img); fastbootD is required for system.img. Without deleting anything, I booted the system and Lineage OS 18.1 Treble works.
It's GSI so it's not fine-tuned for our phone, but it works for the vast majority of what's possible. Including fast charging, which detects after a while. For now, the camera is working as well.
A bit complicated, but Lineage OS 18.1 GSI was possible to install. The flash system.img (GSI) itself is not functional. I suppose any GSI system could be run this way.
Generic System Image releases | Platform | Android Developers
developer.android.com
Reverting to the default Miui is no longer available. It would have to be re-flashed.
inn000 said:
Steps on booting the Android 12 on DSU? I'm using pixel experience and I tried to load the PB4 on DSU but it boots me into an android 11 environment. Does it only work on stock rom?
Click to expand...
Click to collapse
Going now to crDroid and I tried running the DSU Loader.
After downloading and selecting reboot to GSI, I reloaded crDroid in the version with android 11.
But the GSI download was version SPB4.210715.014, which is Android 12.
As I found out, it's a GSI version of Android supplied by the Android developer to test and validate new apps.
The fact that Android 12 was not loaded, but again only crDroid Android 11 is related to the fact that our custom ROMs cannot work with the activation of the second slot (A/B).
This is also why OTA updates (running on the system) do not work properly.
For this update you need to automatically switch the active slot, which will not happen! This will cause the OTA update to fail.
Resolving the ability of custom boot.img to work with fastbootD commands can probably fix the problem with the broken OTA.
So far, switching to GSI only works on Miui.
StaryMuz said:
Going now to crDroid and I tried running the DSU Loader.
After downloading and selecting reboot to GSI, I reloaded crDroid in the version with android 11.
But the GSI download was version SPB4.210715.014, which is Android 12.
As I found out, it's a GSI version of Android supplied by the Android developer to test and validate new apps.
The fact that Android 12 was not loaded, but again only crDroid Android 11 is related to the fact that our custom ROMs cannot work with the activation of the second slot (A/B).
This is also why OTA updates (running on the system) do not work properly.
For this update you need to automatically switch the active slot, which will not happen! This will cause the OTA update to fail.
Resolving the ability of custom boot.img to work with fastbootD commands can probably fix the problem with the broken OTA.
So far, switching to GSI only works on Miui.
Click to expand...
Click to collapse
yep only works on stock miui loader. sgsi systems works too, I used pixel 5 pb4 sgsi and it works better than the one on stock miui dsu. the same problems still exists. Audio, power button, etc.
inn000 said:
yep only works on stock miui loader. sgsi systems works too, I used pixel 5 pb4 sgsi and it works better than the one on stock miui dsu. the same problems still exists. Audio, power button, etc.
Click to expand...
Click to collapse
Sorry to bring this up again, but what is SGSI ? What does the "S" stand for
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