Related
Hello,
I was wondering if some could help me please. I wanted to flash RR Rom 6.0 on my BLA-L09(I think that what's it is) phone.
I was able to unlock my boot loader, and flash TWRP my device but my dumb s*** flashed TWRP to my file system use FLASH SYSTEM instead of FLASH RECOVERY. Now, I can't fix it ?. I know I can use sideload so I'm not panicking just yet however I know I messed up the file system.
Could someone tell me what file system system I should be using (fat, exfat, ext4, etc...) and what to do to get this think to boot backup.?
I've tried and side loading "update_full_BLA-L29_hw_la.zip" stock ROM but no luck... I keep getting this error message:
"check_write_data_to_partition,write data error
Update_huawei_pkg_from_ota_zip: update package from zip failed
Updated process ended with error: 9"
HELP.!!!
me too..... following searching for a solution
Shandroid_94 said:
me too..... following searching for a solution
Click to expand...
Click to collapse
If you find anything, let me know.!
Just boot to fastboot, flash RR to system and TWRP to recovery_ramdisk?
Hey guys.. having issues rooting my BV9900 Pro. Not much on the net about this device. I gained Root access for one boot using magisk app to patch my boot image and fastboot flashing it. I used a couple Root apps and deleted a couple of system apps, magisk granted access. When I restarted, it went into a boot loop until I flashed the original boot.img. Now whenever I flash the patched boot, it tries once and goes into bootloader. I have an Orange State message on regular boot.img startup.
I tried this with a generic blank vbmeta, it went into a boot loop.
Someone with a non-pro BV9900 with the exact same chipset managed to get twrp on his. I tried flashing that. Bootloader says data transfered but whenever I go into recovery, the original recovery.img loads and it boots normally with the Orange State message.
The root deleted system apps are still gone.
Any insights or tips would be greatly appreciated.
pbsavages said:
Someone with a non-pro BV9900 with the exact same chipset managed to get twrp on his. I tried flashing that. Bootloader says data transfered but whenever I go into recovery, the original recovery.img loads and it boots normally with the Orange State message.
Click to expand...
Click to collapse
Only a side remark:
Even if one finds a TWRP image that at 100% matches his/her device, it's not a good idea to flash it: instead boot into it
Code:
fastboot boot twrp.img
jwoegerbauer said:
Only a side remark:
Even if one finds a TWRP image that at 100% matches his/her device, it's not a good idea to flash it: instead boot into it
Code:
fastboot boot twrp.img
Click to expand...
Click to collapse
Ah. I didn't realize magisk was systemless root. The BV9900 Pro crashes when you edit the system image. I suppose I should research more, things have changed in the last few years.
Does anyone know if it is possible to get an android 10/11 GSI installed and working on this phone? I have tried numerous times, with GSIs found online, from the official site. Have checked to make sure I'm using one for the correct architecture. I've had varying results.
The different results I've had:
Stuck in bootloop. When in recovery, can't mount system partition.
Stuck on boot screen. Unrecoginized by PC. Can't mount System in Recovery.
Stuck on boot screen. Recognized by PC (makes ding). Can't access the phone. Can't mount System in recovery.
Stuck on boot screen. Unrecognized by PC. CAN mount System in recovery.
I have tried various methods, steps, and combinations of steps. Using TWRP and attempting to flash system with fastboot as well. When I was able to mount System after flashing the GSI, I also tried installing Magisk. It installed, but did not fix the problem. I can't remember everything I tried, but it was over the course of a few days, with multiple attempts per day. Around 5-10 each day. I can not figure out what I'm doing wrong, if it is even my error. It may just not be possible? Or may require steps that I have no knowledge of. If anyone has any advice, or knows if it's not possible with this phone, I would greatly appreciate it.
Edit: Also, I was using SP Flash Tool with the firmware from Cubot website to reinstall stock.
Elrandra said:
Does anyone know if it is possible to get an android 10/11 GSI installed and working on this phone? I have tried numerous times, with GSIs found online, from the official site. Have checked to make sure I'm using one for the correct architecture. I've had varying results.
The different results I've had:
Stuck in bootloop. When in recovery, can't mount system partition.
Stuck on boot screen. Unrecoginized by PC. Can't mount System in Recovery.
Stuck on boot screen. Recognized by PC (makes ding). Can't access the phone. Can't mount System in recovery.
Stuck on boot screen. Unrecognized by PC. CAN mount System in recovery.
I have tried various methods, steps, and combinations of steps. Using TWRP and attempting to flash system with fastboot as well. When I was able to mount System after flashing the GSI, I also tried installing Magisk. It installed, but did not fix the problem. I can't remember everything I tried, but it was over the course of a few days, with multiple attempts per day. Around 5-10 each day. I can not figure out what I'm doing wrong, if it is even my error. It may just not be possible? Or may require steps that I have no knowledge of. If anyone has any advice, or knows if it's not possible with this phone, I would greatly appreciate it.
Edit: Also, I was using SP Flash Tool with the firmware from Cubot website to reinstall stock.
Click to expand...
Click to collapse
TWRP 3.3.1 + Root CUBOT X19
[ROM][CUBOT X19][UNOFFICIAL] Havoc OS 3.11 [10.0][2020-11-30]
Wipe System, Data, Dalvik, Cache OR advanced Wipe without internal storage/micro sd card
Reboot TO TWRP
Wipe System, Data, Dalvik, Cache OR advanced Wipe without internal storage/micro sd card
Reboot TO TWRP
Flash the ROM
Willing to help if you still have an interest in the topic
same, doesnt work for me aswell
A GSI ROM can only get flashed if device supports TREBLE.
To check this you may use that app
Treble Check - Apps on Google Play
Check your device for Project Treble support and more
play.google.com
jwoegerbauer said:
A GSI ROM can only get flashed if device supports TREBLE.
To check this you may use that app
Treble Check - Apps on Google Play
Check your device for Project Treble support and more
play.google.com
Click to expand...
Click to collapse
yes it is treble supported
hi,
if i flash "Havoc-OS-v3.12-20201230-Official-arm64-ab.img" to my cubot x19 it runs fine without any problems.
however if i try to flash the images directly from google (either "https://ci.android.com/builds/branches/aosp-android10-gsi/grid?" or "https://developer.android.com/topic/generic-system-image/releases") the phone gets stuck after displaying the boot screen.
does anyone know how to solve this problem?
kind regards,
xt1622-blue27
xt1622-blue27 said:
hi,
if i flash "Havoc-OS-v3.12-20201230-Official-arm64-ab.img" to my cubot x19 it runs fine without any problems.
however if i try to flash the images directly from google (either "https://ci.android.com/builds/branches/aosp-android10-gsi/grid?" or "https://developer.android.com/topic/generic-system-image/releases") the phone gets stuck after displaying the boot screen.
does anyone know how to solve this problem?
kind regards,
xt1622-blue27
Click to expand...
Click to collapse
These are raw copies
If you want to try Android 11 : https://forum.xda-developers.com/t/...si-flashen-ohne-bootlop.4333513/post-85711061
I unlocked the device bootloader thanks to Narender, and tried to flash Lineage OS 18.1. After flashing the ROM and vendor zip files, I switched the current slot and restarted to fastboot mode. Then I flashed the vbmeta image. Then I rebooted to recovery to check the current slot. Slot was as expected, so I rebooted the system.
Then, TWRP gave me an alert saying "No OS is installed" before rebooting. I was unsure what was the reason for it because the ROM was just installed, so I rebooted the system.
After that, device went straight into fastboot mode after "Android One" screen. No matter which option I choose from there, it keeps restarting the bootloader. I tried using "fastboot reboot recovery" but that did not work either. Then I tried to change the active slot of the device using fastboot commands. That did not help either.
Now I'm stuck with a Nokia 7.2 that can only be turned off or start in fastboot mode. Is it bricked beyond saving? I just want to install TWRP in any of the slots and install any usable ROM. Any help is deeply appreciated.
Installed NFT and flashed the stock ROM using that. All good now. I still need to figure out how to install ROMs on A/B systems using TWRP.
Chevindu said:
Installed NFT and flashed the stock ROM using that. All good now. I still need to figure out how to install ROMs on A/B systems using TWRP.
Click to expand...
Click to collapse
Follow this and DM if you have doubts
Edit: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Ujwal2000 said:
Follow this and DM if you have doubts
Click to expand...
Click to collapse
I actually installed few ROMs after my previous reply. But none of them had working WiFi, which is a deal breaker. Went back to stock ROM.
If you are interested I could help you
Ujwal2000 said:
If you are interested I could help you
Click to expand...
Click to collapse
Hey, thanks. But I thought it's not possible due how the signatures in security patches work. So I gave up. Maybe I misunderstood. Linking to Raghu's reply below.
Post in thread '[OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7.2 | Daredevil |'
No, wi-fi with twrp still doesn't work. But what I did was, I extracted the boot image of the ROM I was using, flashed twrp, flashed gapps and then flashed the boot file I extracted earlier. So, wi-fi does work in the end. But, you can't have twrp perpetually installed
Some tutorials I saw online used fastboot boot twrp.img
What this is supposed to do is boot into twrp temporarily and is gone after restart.
But, on this phone, instead of booting to recovery after the command, it boots to the OS. And when you restart the boot image is gone and you restart into the stock recovery. So, that method doesn't work
Ujwal2000 said:
No, wi-fi with twrp still doesn't work. But what I did was, I extracted the boot image of the ROM I was using, flashed twrp, flashed gapps and then flashed the boot file I extracted earlier. So, wi-fi does work in the end. But, you can't have twrp perpetually installed
Some tutorials I saw online used fastboot boot twrp.img
What this is supposed to do is boot into twrp temporarily and is gone after restart.
But, on this phone, instead of booting to recovery after the command, it boots to the OS. And when you restart the boot image is gone and you restart into the stock recovery. So, that method doesn't work
Click to expand...
Click to collapse
Yup, pretty much what I experienced too.
I haven't tried extracting boot image and flashing it manually. At this point to be honest, I'm reluctant to put my hands on it again without having a clear step-by-step guide about it.
I did write a step by step guide. But i'll leave it to you to decide if it is clear. Ok I realize I haven't linked the post.
Here it is: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Ujwal2000 said:
I did write a step by step guide. But i'll leave it to you to decide if it is clear. Ok I relaise I haven't linked the post.
Here it is: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Click to expand...
Click to collapse
Thanks Ujwal, appreciate it. I'll have a look.
Hi everyone. I recently bought an Alcatel 1t 7 (8067) tablet, 1Gb ram, 16Gb rom, just wifi (no 4G), mt6580 processor, android oreo go edition; a very simple and cheap tablet, but it seemed me a very nice one, because is slim and lightweight; worhty of root access, but also a custom recovery. I prefer TWRP recovery because it's more organized... ¡Anyway!... So I got down to work, but at first, as I didn't know how to backup all firmware, and when I learned how to do it and did it (esentially I could "tame" sp flash tools, hehe), I had already lost my original recovery file. Is needless to say that TWRP recovery, as far as I know, isn't available for this model, so I needed to port it, but as at first, I didn't know how to back it up, I overwritten it with other recoveries that didn't work. I mean, at this time, the tablet is working but is without recovery tool. I'm not going to talk about root access, because I already could get it, by using magisk manager, but I need my recovery image file, back; both to reinstall it and port it to TWRP.
So finally, if anyone has this stock recovery file, the full stock rom for it, or even better the ported TWRP for this tablet, please share it to me.
Thanks in advance for your attention.
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
aIecxs said:
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
Click to expand...
Click to collapse
Thank you for reply. Ok, I booted android. I have enabled usb debugging so, when android booted, I connected it to adb, and opened "adb reboot recovery" command, to be sure that android would reboot into that mode; but it didn't, it just rebooted several times on boot screen, and when it "got tired" of rebooting, it booted into android. Didn't boot into recovery, so I guess, It didn't repair it.
PS: I was looking for that file "recovery-from-boot.p" on that path, and there isn't such file, i can't find it.
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
you can port TWRP with kernel from boot. you can use this TWRP as base
aIecxs said:
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
Click to expand...
Click to collapse
¿Must that file have the same size that the original recovery image? Because the only file named recovery that i can find on that path is named "recovery-resource.dat" and its size is 807kb, and as I have seen before, is that recovery images have several Mb of size.
aIecxs said:
you can port TWRP with kernel from boot. you can use this TWRP as base
Click to expand...
Click to collapse
Two questions about it; as far as I can remember twrp image must be compatible not only for the same chipset, but the same screen resolution ¿Am I right? Also, this tablet is 600x1024 px, or 1024x 600 on landscape mode. All TWRP that I have installed on former machines, worked on portrait mode, so I wonder miself ¿Could TWRP also work on landscape mode?
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
aIecxs said:
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
Click to expand...
Click to collapse
Ok... I can find that file on my tablet, but I'm not so skilled android user, as for rebuild recovery from that file or even port TRWP from that file, so ¿Is there an easy way to do it ( or at least, comprehensible for middle skilled android users) ? ¿How? (and supposedly this machine is easy to port and root, they say on internet. I also have a huawei y7 2018 for rooting, that seems harder to root. But that's a another (my next) struggle in here, hehe)
aIecxs said:
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
Click to expand...
Click to collapse
Another question. ¿Are those programs who claim to help to port TWRP with just some clicks, reliable? (for instance TWRP porter for mediatek)
aIecxs said:
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
Click to expand...
Click to collapse
All the TWRP recoveries that i have ported before, have had a working touchscreen, but as I understand, resolution requirement is not only for touch calibration, but for correct displaying of TWRP GUI (that all buttons and options fit on the screen), Now I've read that new versions of TWRP adjust automatically to any screen resolution, ¿Is that right?
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
HCU-client needs 4 credits for Huawei.
I may reply in new thread.
aIecxs said:
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
Click to expand...
Click to collapse
¡No, man! If TWRP porting is kinda hard having the stock recovery image, without it, is a brain smashing task (or at least for me). I mean, I really don't understand well, how to port twrp starting only with boot.img, I mean, without recovery img. I've saw tutorials about the use of carliv kitchen (windows version), and seems easy, but all tutorials are made with stock recovery.img available, not with boot.img. So, what can I do there?
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
aIecxs said:
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
Click to expand...
Click to collapse
I saw a tutorial about. It said that I must to unpack stock recovery and twrp recovery, and replace some files of unpacked twrp recovery, with respective unpacked stock recovery files, and edit some files on twrp unpacked folder, and finally repack it.
Until that point, I assume that it should work, I mean, having stock recovery. But I did that, but using boot.img, I renamed all boot resources, to recovery, for instance, boot.imgkernel to recovery.imgkernel; and replaced it, repacked it, and reflashed it, but nothing happened, I mean, it didn`t want to boot into recovery. It`s interesting to "experiment", but I`m gonna try to find its original stock recovery, to at least get it back.
Hello!
I would like some help, alcatel 1T7" 8086 no4g I likely bricked it. There's nothing else than a black screen. The tablet doesn't react to anything. The computer finds it as unknown USB tool. No visibilty is shown. What can i do with it,for it to work? Or should i just put it in the trash?
Thank you for the reply.