Hi! Most of the firmware runs on our device GSI, but the fingerprint doesn't work anywhere. What is the problem?
Gsi
Which GSI is more stable ????
dude there is no GSI Yet for the Phone , well there is but Touch isnt working
naman81093 said:
Which GSI is more stable ????
Click to expand...
Click to collapse
crDroid On 10 Android, everything works, only there is no fingerprint. in general, most GSI on 10 Android works well on our phone. except a finger ..
Gsi
Can u send me the link of crdroid gsi and gapps.
figyra said:
crDroid On 10 Android, everything works, only there is no fingerprint. in general, most GSI on 10 Android works well on our phone. except a finger ..
Click to expand...
Click to collapse
where did you see CrDroid ? for the RealMe X2 Pro
natedogg20050 said:
where did you see CrDroid ? for the RealMe X2 Pro
Click to expand...
Click to collapse
there is no firmware for our phone, you can just flash any GSI based on Android 10 and it will work
naman81093 said:
Can u send me the link of crdroid gsi and gapps.
Click to expand...
Click to collapse
https://sourceforge.net/projects/am...200104--v6.1-arm64-ab-vanilla.img.xz/download
gaps can be found after you sew the image .img make the date format via yes. then the system will work
Tried absolutely everything to get GSI's to boot and nothing, yup going from wiping data in stock recovery, to full (yes) wipe in twrp, just won't do nowt, So I'm very much puzzled on how some are managing?
Duncan1982 said:
Tried absolutely everything to get GSI's to boot and nothing, yup going from wiping data in stock recovery, to full (yes) wipe in twrp, just won't do nowt, So I'm very much puzzled on how some are managing?
Click to expand...
Click to collapse
I was having the same problem, no GSIs would boot. Flashing A/B images got as far as the boot animation but no further. I found the below post for the Realme x2 which mentioned flashing a blank vbmeta and making some changes to fstab.qcom in /vendor/etc. After making some changes to the fstab I can now boot GSIs fine. I'm not sure why only some people might need to do this, could be a issue depending on the variant? I have the Malaysian X2 pro which couldn't be unlocked using the normal deeptest app.
https://forum.xda-developers.com/realme-x2/how-to/google-gsi-generic-image-howto-t4013421
Steps for those who don't want to dig through the other post:
1. fastboot --disable-verification flash vbmeta vbmeta.img (Attached the vbmeta)
2. Boot to recovery, mount vendor partition.
3. Edit /vendor/etc/fstab.qcom as follows (I've attached mine for those who just want to adb push) :
Code:
#/dev/block/bootdevice/by-name/metadata /metadata ext4 noatime,nosuid,nodev,async_discard wait,formattable
#/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc,async_discard,errors=panic latemount,wait,check,quota,fileencryption=ice,wrappedkey,keydirectory=/metadata/vold/metadata_encryption,reservedsize=128M,resize
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,noatime,nodev,barrier=1,noauto_da_alloc,async_discard,lazytime,errors=panic latemount,wait,resize,check,quota,reservedsize=128M
4. Flash GSI image to System
5. Format data (Other post mentions rm -rf mode, this failed for me)
I hope that helps some people
datty said:
I was having the same problem, no GSIs would boot. Flashing A/B images got as far as the boot animation but no further. I found the below post for the Realme x2 which mentioned flashing a blank vbmeta and making some changes to fstab.qcom in /vendor/etc. After making some changes to the fstab I can now boot GSIs fine. I'm not sure why only some people might need to do this, could be a issue depending on the variant? I have the Malaysian X2 pro which couldn't be unlocked using the normal deeptest app.
https://forum.xda-developers.com/realme-x2/how-to/google-gsi-generic-image-howto-t4013421
Steps for those who don't want to dig through the other post:
1. fastboot --disable-verification flash vbmeta vbmeta.img (Attached the vbmeta)
2. Boot to recovery, mount vendor partition.
3. Edit /vendor/etc/fstab.qcom as follows (I've attached mine for those who just want to adb push) :
4. Flash GSI image to System
5. Format data (Other post mentions rm -rf mode, this failed for me)
I hope that helps some people
Click to expand...
Click to collapse
Many thanks will give this a try and see if it works ........
datty said:
I was having the same problem, no GSIs would boot. Flashing A/B images got as far as the boot animation but no further. I found the below post for the Realme x2 which mentioned flashing a blank vbmeta and making some changes to fstab.qcom in /vendor/etc. After making some changes to the fstab I can now boot GSIs fine. I'm not sure why only some people might need to do this, could be a issue depending on the variant? I have the Malaysian X2 pro which couldn't be unlocked using the normal deeptest app.
https://forum.xda-developers.com/realme-x2/how-to/google-gsi-generic-image-howto-t4013421
Steps for those who don't want to dig through the other post:
1. fastboot --disable-verification flash vbmeta vbmeta.img (Attached the vbmeta)
2. Boot to recovery, mount vendor partition.
3. Edit /vendor/etc/fstab.qcom as follows (I've attached mine for those who just want to adb push) :
Code:
#/dev/block/bootdevice/by-name/metadata /metadata ext4 noatime,nosuid,nodev,async_discard wait,formattable
#/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc,async_discard,errors=panic latemount,wait,check,quota,fileencryption=ice,wrappedkey,keydirectory=/metadata/vold/metadata_encryption,reservedsize=128M,resize
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,noatime,nodev,barrier=1,noauto_da_alloc,async_discard,lazytime,errors=panic latemount,wait,resize,check,quota,reservedsize=128M
4. Flash GSI image to System
5. Format data (Other post mentions rm -rf mode, this failed for me)
I hope that helps some people
Click to expand...
Click to collapse
can you confirm that fingerprint is still working and if so please make your own thread and include everything so people wont have to search on millions of posts
---------- Post added at 03:55 PM ---------- Previous post was at 03:49 PM ----------
datty said:
I was having the same problem, no GSIs would boot. Flashing A/B images got as far as the boot animation but no further. I found the below post for the Realme x2 which mentioned flashing a blank vbmeta and making some changes to fstab.qcom in /vendor/etc. After making some changes to the fstab I can now boot GSIs fine. I'm not sure why only some people might need to do this, could be a issue depending on the variant? I have the Malaysian X2 pro which couldn't be unlocked using the normal deeptest app.
https://forum.xda-developers.com/realme-x2/how-to/google-gsi-generic-image-howto-t4013421
Steps for those who don't want to dig through the other post:
1. fastboot --disable-verification flash vbmeta vbmeta.img (Attached the vbmeta)
2. Boot to recovery, mount vendor partition.
3. Edit /vendor/etc/fstab.qcom as follows (I've attached mine for those who just want to adb push) :
Code:
#/dev/block/bootdevice/by-name/metadata /metadata ext4 noatime,nosuid,nodev,async_discard wait,formattable
#/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc,async_discard,errors=panic latemount,wait,check,quota,fileencryption=ice,wrappedkey,keydirectory=/metadata/vold/metadata_encryption,reservedsize=128M,resize
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,noatime,nodev,barrier=1,noauto_da_alloc,async_discard,lazytime,errors=panic latemount,wait,resize,check,quota,reservedsize=128M
4. Flash GSI image to System
5. Format data (Other post mentions rm -rf mode, this failed for me)
I hope that helps some people
Click to expand...
Click to collapse
https://www.getdroidtips.com/aosp-android-10-realme-x2-pro/
did you try if that boots also ?
natedogg20050 said:
can you confirm that fingerprint is still working and if so please make your own thread and include everything so people wont have to search on millions of posts
---------- Post added at 03:55 PM ---------- Previous post was at 03:49 PM ----------
https://www.getdroidtips.com/aosp-android-10-realme-x2-pro/
did you try if that boots also ?
Click to expand...
Click to collapse
No fingerprint working at the moment.
I tried the AOSP you linked and the PixelExperience GSI, both worked fine as far as camera/bluetooth/wifi/mobile data but I didn't test much further than that.
datty said:
No fingerprint working at the moment.
I tried the AOSP you linked and the PixelExperience GSI, both worked fine as far as camera/bluetooth/wifi/mobile data but I didn't test much further than that.
Click to expand...
Click to collapse
so if everything is indeed working i might switch to the GSI
datty said:
No fingerprint working at the moment.
Click to expand...
Click to collapse
Did you update to latest firmware and locked/relocked? Shouldn't the fp issue be fixed after the update?
Anyone tried sGSI roms? We might get to boot OxygenOS using these builds . They may need permisser, I think i'll try them out when i have more time, I'm leaving them here if someone wants to try.
https://forum.xda-developers.com/re...gsi-realme-t4036825/post81522239#post81522239
Related
Hey guys, it's me again In the last few months I dont active much on this anymore, now I'm back
Here is the latest rec for our beloved device:
https://drive.google.com/file/d/0B5ePoKNP9UFtM1R5MW1vdjFGOGc/view?usp=sharing
How to use:
Code:
fastboot flash recovery twrp-z1-2860.img
Changelog:
v2.8.6.0:
Nothing much, just add support for Z1 and F2FS
Bugs: The image/icon may look weird because I have to compress all icon to make room for new update....Limited space for us to "hack" it...
You tell me
This thread will be main support for TWRP to use with CM/CM-based rom or maybe stock rom too by me...Stay update
I will update it ASAP when new TWRP version come out....
P/S: "TekCafe" is just the name of my support group...If you guys not like it, I will make another without that name....
Tested on AICP 9.0
Click "Thanks" if you find it useful...
Thanks. Everything is working perfectly we just seem to have 2 home buttons now. The 1 home button functions like the back button so it's just cosmetic
LSD DREAMER said:
Thanks. Everything is working perfectly we just seem to have 2 home buttons now. The 1 home button functions like the back button so it's just cosmetic
Click to expand...
Click to collapse
I compress and reuse all the icon so you may find broken artifact icon, duplicated,...It's just cosmetic, every function work just as fine....
BlackSoulxxx said:
I compress and reuse all the icon so you may find broken artifact icon, duplicated,...It's just cosmetic, every function work just as fine....
Click to expand...
Click to collapse
It all works fine it even looks the same just the 2 home buttons. Not complaining just thought I'll share
Hi!
Will this TWRP work with stock 4.4.4?
I´m on UB.
Best regards
C_Karhu said:
Hi!
Will this TWRP work with stock 4.4.4?
I´m on UB.
Best regards
Click to expand...
Click to collapse
You should install NUT XZDR...:fingers-crossed::fingers-crossed::fingers-crossed:
Sorry, I didn't make myself clear. I'm interested in the F2FS. My kernel has support, but I can't format system to it. Will this TWRP format stock 4.4.4 to full F2FS?
Best regards
Is it compiled from source or repacked from Sirius?
o-l-a-v said:
Is it compiled from source or repacked from Sirius?
Click to expand...
Click to collapse
You already answer that question.....
Does the latest CM12 nightly support F2FS already?
Hi,
I've changed /system and /cache successfully, but I cannot convert /data to f2fs. Formats to ext4 correctly, but even after I formatted ext4, rebooting to recovery and formatting it to f2fs fails.
Code:
Formatting Data using mkfs.f2fs...
E:Unable to wipe '/data'.
E:Unknown MTP message type: 1
E:Error changing file system.
Updating partition details...
I have unlocked bootloader, Xperia Z1 (c6903 honami) running 5.1 with Resurrection Remix 5.4.1 kernel and ROM. I have not encrypted device.
Thoughts?
FIXED! I was able to format it by using terminal from TWRP and typing
Code:
mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
then I rebooted device into recovery to update partition table, then Wipe > Repair/Change Filesystem > Data
Code:
current file system: f2fs
Yay!
kentexcitebot said:
Hi,
I've changed /system and /cache successfully, but I cannot convert /data to f2fs. Formats to ext4 correctly, but even after I formatted ext4, rebooting to recovery and formatting it to f2fs fails.
Code:
Formatting Data using mkfs.f2fs...
E:Unable to wipe '/data'.
E:Unknown MTP message type: 1
E:Error changing file system.
Updating partition details...
I have unlocked bootloader, Xperia Z1 (c6903 honami) running 5.1 with Resurrection Remix 5.4.1 kernel and ROM. I have not encrypted device.
Thoughts?
FIXED! I was able to format it by using terminal from TWRP and typing
Code:
mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
then I rebooted device into recovery to update partition table, then Wipe > Repair/Change Filesystem > Data
Code:
current file system: f2fs
Yay!
Click to expand...
Click to collapse
Tks!:fingers-crossed::fingers-crossed::fingers-crossed:
Up...............
guys help me pls. i flash the recovery by fastboot but when press volume - not enter in recovery why is? obviously i have unlocked the boot
axelgrox said:
guys help me pls. i flash the recovery by fastboot but when press volume - not enter in recovery why is? obviously i have unlocked the boot
Click to expand...
Click to collapse
+1... same problem!
axelgrox said:
guys help me pls. i flash the recovery by fastboot but when press volume - not enter in recovery why is? obviously i have unlocked the boot
Click to expand...
Click to collapse
There could be 2 reasons: one, you are not properly flashing, as you need to do
fastboot flash recovery "name of file": second, if you have kernel with TWRP integrated, the two will collide resulting in no recovery at all...
Hi
Does it work for stock android 5.0.2 build .270 ?!
Thank you
Does this work 14.6.A.0.368
I have been trying to reflash this, however when I try to boot in to TWRP all I get is the fastboot mode on my phone which doesn't allow me to do anything. I recently just uninstalled MultiRom for the same reasons, but now since I have removed MultiRom I cannot get into TWRP at all. Does anyone have any ideas?
File doesn't exist anymore
If you guys help me to go back successfully to stock, I'll make a guide to explain the process, maybe for all 3 models. I just need help on this one
I have an A2017G
So this is my fourth time trying to get back to stock. the first one resulted on a DFU brick. The second one was through MiFlash and the system had random reboots. The third, I flashed tron1's A2017G B04 Bootstack and a DrakenFX flashable zip (for the U, just wanted to try) and TWRP said that there was no system which turned out to be true... i had wiped system, data and caches before, but it seemingly installed okay...
I also tried to use MiFlash again and get B10, but it started to throw an error out of the blue (the specified cast is not valid, or something along the lines). I used it at least 4 times before.
So what zip should I use? I never tried flashing one of those update zips (I have full official B10 on the sdcard) but I believe they won't work. Please tell me if they do work...
again, if i manage to get SAFELY to stock and AVOID DFU I'll make a nice guide so that we stop asking. Most custom roms are flawed, for ex. Lineage has bad compatibility, Pure Nexus (the one I'm using now) has extreme, Galaxy Y grade lag, and RR simply works worse than stock (it's probably the best one of the bunch though).
i am in in the process of going back to stock(A2017), will let you know.
---------- Post added at 04:07 AM ---------- Previous post was at 03:14 AM ----------
I have followed all the tutorials but its failed and now i cant even install any zip in twrp , cant mount internal storage.. deive or resource busy and cant restore my LOS based rom.. same errors..
satish.yarramsetti said:
i am in in the process of going back to stock(A2017), will let you know.
---------- Post added at 04:07 AM ---------- Previous post was at 03:14 AM ----------
I have followed all the tutorials but its failed and now i cant even install any zip in twrp , cant mount internal storage.. deive or resource busy and cant restore my LOS based rom.. same errors..
Click to expand...
Click to collapse
well you can get to EDL and flash a full A2017 EDL package. I can't, not on this computer
Does EDL work?
Choose an username... said:
well you can get to EDL and flash a full A2017 EDL package. I can't, not on this computer
Click to expand...
Click to collapse
TWRP doesnt mount /Data
---------- Post added at 04:19 AM ---------- Previous post was at 04:16 AM ----------
Choose an username... said:
well you can get to EDL and flash a full A2017 EDL package. I can't, not on this computer
Click to expand...
Click to collapse
I tried Format system option in Wipe Menu, and that caused this ' Cnat mount /Data ' issue.
satish.yarramsetti said:
TWRP doesnt mount /Data
---------- Post added at 04:19 AM ---------- Previous post was at 04:16 AM ----------
I tried Format system option in Wipe Menu, and that caused this ' Cnat mount /Data ' issue.
Click to expand...
Click to collapse
well I meant use MiFlash, but I don't know if you should even think about getting out of TWRP in this state. No idea
Hey how to boot EDL mode
Choose an username... said:
well I meant use MiFlash, but I don't know if you should even think about getting out of TWRP in this state. No idea
Click to expand...
Click to collapse
Please help, how to boot EDL mode? please help i forgot
satish.yarramsetti said:
Please help, how to boot EDL mode? please help i forgot
Click to expand...
Click to collapse
I don't think you should when having TWRP loaded on your RAM and your system probably not there...
My DFU brick was just because of that
but if you insist, turn your phone off and hold the two volume keys, then connect the USB cable (it has to be connected to the PC obviously)
Still had TWRP
Choose an username... said:
I don't think you should when having TWRP loaded on your RAM and your system probably not there...
My DFU brick was just because of that
but if you insist, turn your phone off and hold the two volume keys, then connect the USB cable (it has to be connected to the PC obviously)
Click to expand...
Click to collapse
Man, still i had twrp and i can access internal storage. let me see if i can restore my rom
---------- Post added at 04:37 AM ---------- Previous post was at 04:34 AM ----------
satish.yarramsetti said:
Man, still i had twrp and i can access internal storage. let me see if i can restore my rom
Click to expand...
Click to collapse
Thanks God! Restore is in progress and if it works i wont try to get back to stock until someone find a sure shot method for that... waiting.. waiting..
satish.yarramsetti said:
Man, still i had twrp and i can access internal storage. let me see if i can restore my rom
---------- Post added at 04:37 AM ---------- Previous post was at 04:34 AM ----------
Thanks God! Restore is in progress and if it works i wont try to get back to stock until someone find a sure shot method for that... waiting.. waiting..
Click to expand...
Click to collapse
MiFlash is that method. It only has to be in the mood to work...
restore failed
Choose an username... said:
MiFlash is that method. It only has to be in the mood to work...
Click to expand...
Click to collapse
restore failed "extracttarfork() process ended with error=255"
satish.yarramsetti said:
restore failed "extracttarfork() process ended with error=255"
Click to expand...
Click to collapse
i had that error when I was backing up. Try to wipe all the partitions but internal (not necessarily format, go to settings and tick use rm -rf) maybe it works. if not try formatting with ext4
lol deleted
No, doesnt help
Choose an username... said:
lol deleted
Click to expand...
Click to collapse
No its doesnt help wiping all partitions.. same error
Mount -> Unmount /data
Wipe -> Format Data (the actual button next to 'Advanced Wipe')-> type 'yes' -> Reboot Recovery
Wipe -> Advanced Wipe -> Tick 'Data' -> Change File System -> EXT4
Try to mount /data
This has worked for me going from an LOS system back to Stock.
satish.yarramsetti said:
No its doesnt help wiping all partitions.. same error
Click to expand...
Click to collapse
QuantumFluxx said:
Mount -> Unmount /data
Wipe -> Format Data (the actual button next to 'Advanced Wipe')-> type 'yes' -> Reboot Recovery
Wipe -> Advanced Wipe -> Tick 'Data' -> Change File System -> EXT4
Try to mount /data
This has worked for me going from an LOS system back to Stock.
Click to expand...
Click to collapse
It might have worked post restart. I am unable mount internal storage or fash but Post restrat it worked
QuantumFluxx said:
This has worked for me going from an LOS system back to Stock.
Click to expand...
Click to collapse
could you tell us how you did to get to stock? What's your device, A2017G? What did you flash?
That's pretty much everything I want to know
A2017U from LOS to stock using the files on https://forum.xda-developers.com/showpost.php?p=68873482
The only reason I mentioned it when I have the United States model is because I have ran into a problem on multiple devices going from CyanogenMod to any sort of AOSP-based ROM without clicking that format data button. The first time I ran into the problem comma I could not mount my data partition.
I advised @satish.yarramsetti about this here. @satish.yarramsetti, can you confirm that the ZIP I linked you to in the other thread is the one you flashed and is booting?
Choose an username... said:
could you tell us how you did to get to stock? What's your device, A2017G? What did you flash?
That's pretty much everything I want to know
Click to expand...
Click to collapse
QuantumFluxx said:
A2017U from LOS to stock using the files on https://forum.xda-developers.com/showpost.php?p=68873482
The only reason I mentioned it when I have the United States model is because I have ran into a problem on multiple devices going from CyanogenMod to any sort of AOSP-based ROM without clicking that format data button. The first time I ran into the problem comma I could not mount my data partition.
I advised @satish.yarramsetti about this here. @satish.yarramsetti, can you confirm that the ZIP I linked you to in the other thread is the one you flashed and is booting?
Click to expand...
Click to collapse
I am Nuclear Rom(LOS Based) and tried to go back to stock. I have followed all tutorials but when i try to reboot, TWRP warned me that there is no OS. So i didn't reboot as it might remove TWRP ( it might have booted but not sure) ( i also flashed NO verify zip) , so i thought of formatting in wipe menu which caused a lot of problems like cant mount data & device busy errors . I tried to flash N boot loader and mod but every FLASH is getting failed. So i decided to restart and luckily i have TWRP and no os and my nandroid back up niether worked.
Finally i flashed Clean LOS.
Understood. I have received that same warning in the past after flashing stock. At any rate, if there's no OS installed, there's nothing to overwrite TWRP. The phone would just sit at the ZTE logo and you would have to hold Vol Up+Power to get back into TWRP. If you decided to try again, at least you know you can restore LOS if it doesn't work... Good luck.
satish.yarramsetti said:
I am Nuclear Rom(LOS Based) and tried to go back to stock. I have followed all tutorials but when i try to reboot, TWRP warned me that there is no OS. So i didn't reboot as it might remove TWRP ( it might have booted but not sure) ( i also flashed NO verify zip) , so i thought of formatting in wipe menu which caused a lot of problems like cant mount data & device busy errors . I tried to flash N boot loader and mod but every FLASH is getting failed. So i decided to restart and luckily i have TWRP and no os and my nandroid back up niether worked.
Finally i flashed Clean LOS.
Click to expand...
Click to collapse
QuantumFluxx said:
Understood. I have received that same warning in the past after flashing stock. At any rate, if there's no OS installed, there's nothing to overwrite TWRP. The phone would just sit at the ZTE logo and you would have to hold Vol Up+Power to get back into TWRP. If you decided to try again, at least you know you can restore LOS if it doesn't work... Good luck.
Click to expand...
Click to collapse
The restore is also not working i got some error 255 ... Strange thing is i got a warning like no OS after installing LOS but i booted.
So I recently rooted and flashed a custom rom (https://forum.xda-developers.com/yureka/general/rom-bootleggers-rom-v2-1-volte-t3777131) on my device, all was working fine until I realized that I didn't flash gapps. Downloaded gapps tried flashing (on TWRP) it but I got the error "error executing updater binary" . Googled up for a solution and got this:
Step 1:- Go to recovery.
Step 2:- Go to Wipe>>Advanced wipe.
Step 3:- Check data, system, cache & dalvik cache and then swipe to wipe all.
Step 4:- Then go to install zip from SD card and browse the Rom and install it.
Step 5:- Reboot the device
After this, somehow, I lost the rom but had my TWRP recovery still but I was able to flash the rom again using "minimal adb and fastboot". Everything was working fine but I still didn't have gapps and I thought I did something wrong with the steps aforementioned so I took a shot at those steps again. And boom! my device now keeps booting into "FASTBOOT MODE"(can't even go to recovery) and I tried several methods to try and fix and the most frequent "fix" I got for this on Google was to use adb and fastboot and use the command "fastboot oem unlock" but that didn't help either. PLEASE HELP ME OUT. JUST NEED TO GET A RECOVERY (TWRP/CWM) and flash my rom
fastboot -i 0x1ebf erase cache
fastboot -i 0x1ebf erase userdata
Flash twrp 3.2.2
fastboot -i 0x1ebf flash recovery twrp_3.2.2.img
Sent from my AO5510 using Tapatalk
---------- Post added at 06:19 AM ---------- Previous post was at 06:18 AM ----------
brickedmyphone1 said:
So I recently rooted and flashed a custom rom (https://forum.xda-developers.com/yureka/general/rom-bootleggers-rom-v2-1-volte-t3777131) on my device, all was working fine until I realized that I didn't flash gapps. Downloaded gapps tried flashing (on TWRP) it but I got the error "error executing updater binary" . Googled up for a solution and got this:
Step 1:- Go to recovery.
Step 2:- Go to Wipe>>Advanced wipe.
Step 3:- Check data, system, cache & dalvik cache and then swipe to wipe all.
Step 4:- Then go to install zip from SD card and browse the Rom and install it.
Step 5:- Reboot the device
After this, somehow, I lost the rom but had my TWRP recovery still but I was able to flash the rom again using "minimal adb and fastboot". Everything was working fine but I still didn't have gapps and I thought I did something wrong with the steps aforementioned so I took a shot at those steps again. And boom! my device now keeps booting into "FASTBOOT MODE"(can't even go to recovery) and I tried several methods to try and fix and the most frequent "fix" I got for this on Google was to use adb and fastboot and use the command "fastboot oem unlock" but that didn't help either. PLEASE HELP ME OUT. JUST NEED TO GET A RECOVERY (TWRP/CWM) and flash my rom
Click to expand...
Click to collapse
https://dl.twrp.me/tomato/
Sent from my AO5510 using Tapatalk
Thank you very much!! I am so sorry for the late af reply, got a little carried away with some other thing(s). I got the recovery now and I used a micro SD card to flash the rom but the problem now is that I'm getting the error 7 ("Updater process ended with ERROR: 7 Error installing zip file "/external_sd/" followed by filename.zip)
and then it says "Updating partition details... Failed to mount '/cache' (Invalid arguement)
...done"
I do not understand what seems to be the problem....I thought the issue might be with me trying to flash it via the memory card so I tried using the "adb sideload" method which yielded the same results. I have no idea what is to be done now
brickedmyphone1 said:
Thank you very much!! I am so sorry for the late af reply, got a little carried away with some other thing(s). I got the recovery now and I used a micro SD card to flash the rom but the problem now is that I'm getting the error 7 ("Updater process ended with ERROR: 7 Error installing zip file "/external_sd/" followed by filename.zip)
and then it says "Updating partition details... Failed to mount '/cache' (Invalid arguement)
...done"
I do not understand what seems to be the problem....I thought the issue might be with me trying to flash it via the memory card so I tried using the "adb sideload" method which yielded the same results. I have no idea what is to be done now
Click to expand...
Click to collapse
Do factory reset in twrp
Do it twice
Then flash ROM as usual
Sent from my AO5510 using Tapatalk
Rajendran Rasa said:
Do factory reset in twrp
Do it twice
Then flash ROM as usual
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
Thank you very much!!!!! That did it! You da man ) just one last query, I'm about to flash gapps(which was the root of all the problems) and I've downloaded the gapps 64 bit cos yu yureka is ARM with 64 bit cpu architecture right?
Edit: I went ahead and tried flashing it with the 64 bit one and after getting the regular twrp messages I got one as "Insufficient storage space available in system partition. You may want to use a smaller open GApps package or consider removing some apps using gapps-config. See:'/sdcard/open_gapps_log.txt' for complete information"
But right now I did a factory reset(ty again) and there's absolutely nothing in my internal storage. The last passage on twrp looks like this ;
"Error Code: 70
-Unmounting /persist /system
Updater process ended with ERROR: 70
Error installing zip file '/sdcard/open_gapps-arm64-8.1-stock-20180705.zip' "
brickedmyphone1 said:
cos yu yureka is ARM with 64 bit cpu architecture right?
Click to expand...
Click to collapse
Right.:good:
~bump~
Edited the last post with new problems ._.
brickedmyphone1 said:
~bump~
Edited the last post with new problems ._.
Click to expand...
Click to collapse
Internal storage and /system partition are different things.
Either download the Pico Gapps package or increase the /system partition size.
saurav007 said:
Internal storage and /system partition are different things.
Either download the Pico Gapps package or increase the /system partition size.
Click to expand...
Click to collapse
Thank you again!
But pray tell, how do I increase my /system partition size?
brickedmyphone1 said:
Thank you again!
But pray tell, how do I increase my /system partition size?
Click to expand...
Click to collapse
Make sure to read everything and only follow it once you understand everything or you always have a risk of bricking your device. You can also opt for Pico Gapps package if you want where you probably won't have to increase any partition size.
http://forums.yuplaygod.com/threads/39966/
saurav007 said:
Internal storage and /system partition are different things.
Either download the Pico Gapps package or increase the /system partition size.
Click to expand...
Click to collapse
saurav007 said:
Make sure to read everything and only follow it once you understand everything or you always have a risk of bricking your device. You can also opt for Pico Gapps package if you want where you probably won't have to increase any partition size.
http://forums.yuplaygod.com/threads/39966/
Click to expand...
Click to collapse
Thank you once again, I will try the same and revert back.
Hi .
I'm tired with Huawei's encryption. It's ok with Emui Rom but for AOSP (or other based on it) it's annoying :crying:
So use this guide for remove it definitively
WARNING !!
ALL YOUR DATA WILL BE DELETED ,SO BACKUP ALL YOUR PICTURES,VIDEO ETC ... TO YOUR PC OR IN EXT SDCARD
Download and copy in sdcard,not internal ,in attached files my :
- Huawei_remove_encyption_data
- Custom TWRP 3.2.3 recovery
rename my twrp_recovery.img.zip to twrp_recovery.img (remove .zip at the end, it's for upload this files into xda (size files))
or
in Android File Host
Download
HERE
PROGRESS :
Boot into fastboot, and Run
"fastboot -w", to wipe crypto
without rebooting flash included patched TWRP (fastboot flash recovery_ramdisk twrp_recovery.img)
Boot into TWRP, then Wipe internal storage, Wipe > Format Data then write "Yes"
Then flash my Huawei_remove_encyption_data script
reboot into TWRP recovery
Now you could continue to flash AOSP/LOS/CUSTOMS ROMs
And we're Done
Changelogs
2018-11-01
* Add new Android File Host Download link
* Add new MINADBD
* Fix selinux denial with stock kernel
Click to expand...
Click to collapse
Note:
If you want to come back to stock EMUI/Encryption data ,reboot into erecovery and use "download last firmware and recovery" and follow the steps
Enjoy :good:
Creadits:
@AL_IRAQI for the inspiration of this guide
Updated 2018-10-24
* Update script with busybox mount program , more stable as previous script
* Update TWRP with Static Busybox ,last teamwin stuff and some other fix
This is on a good path, thank you brother for your work ...:good:
I tried on my VTR-L29C432 (P10) and it worked!
Now I can flash files from my internal storage.
It works on EMUI and custom roms, even android 9. @micky387 Thank you so much for this tool bro
It just isnt working for me.
it installs twrp, but it fails with the wiping
when i try to format data it says cannot mount storage
acant install any rom either.
also refuses to download latest update in emui recovery
man, does huawei suck!
caniranges said:
It just isnt working for me.
it installs twrp, but it fails with the wiping
when i try to format data it says cannot mount storage
acant install any rom either.
also refuses to download latest update in emui recovery
man, does huawei suck!
Click to expand...
Click to collapse
Which device ,mate 9 ?
download again and try the new files. I have updated my twrp and script for more support
After flashing custom ROM, my data partition was encrypted.
Need some help here.
I have a mate 9 US variant. I was directed here from [Recovery][10-09-2018][3.2.3-0] TWRP for the Huawei Mate 9 (hi3660) (https://forum.xda-developers.com/mate-9/development/recovery-twrp-huawei-mate-9-hi3660-t3834796).
1) Successfully installed TWRP 3.2.3.
2) Backed up my /system partiton using TWRP to my ext SD card.
3) Boot into fastboot and run "fastboot -w". It shows
"
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.078s]
finished. total time: 0.078s
"
Not sure it is successful or not.
4) No rebooting and flash TWRP 3.2.3 again.
5) reboot to TWRP successfully, but not able to format data. It shows "failed to mount '/data'"
---------------------------------------------------------------------------------------------------------------------------------------------
Just found these two post have different TWRP files. The version numbers are the same, but file sizes are not. Is successful with the TWRP posted in this page.
@micky387 Hi!
One Question, the fstab file was taken from Honor View 10 forum or you modded that? Because I the one that I'm using was taken from there.
First I did the wipes on Twrp but my internal storage wasn't recognized when the phone booted, so I had to wipe using stock recovery and it worked, now I can use my internal memory on Twrp.
Hi guys.
OP updated
* Update script with busybox mount program , more stable as previous script
* Update TWRP with Static Busybox ,last teamwin stuff and some other fix
Click to expand...
Click to collapse
soft-touch said:
After flashing custom ROM, my data partition was encrypted.
Click to expand...
Click to collapse
Try with new stuff.
swith to busybox for more device variant support
huhtan said:
Need some help here.
I have a mate 9 US variant. I was directed here from [Recovery][10-09-2018][3.2.3-0] TWRP for the Huawei Mate 9 (hi3660) (https://forum.xda-developers.com/mate-9/development/recovery-twrp-huawei-mate-9-hi3660-t3834796).
1) Successfully installed TWRP 3.2.3.
2) Backed up my /system partiton using TWRP to my ext SD card.
3) Boot into fastboot and run "fastboot -w". It shows
"
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.078s]
finished. total time: 0.078s
"
Not sure it is successful or not.
4) No rebooting and flash TWRP 3.2.3 again.
5) reboot to TWRP successfully, but not able to format data. It shows "failed to mount '/data'"
---------------------------------------------------------------------------------------------------------------------------------------------
Just found these two post have different TWRP files. The version numbers are the same, but file sizes are not. Is successful with the TWRP posted in this page.
Click to expand...
Click to collapse
Same, use new script and twrp in OP and report
sfoot13 said:
@micky387 Hi!
One Question, the fstab file was taken from Honor View 10 forum or you modded that? Because I the one that I'm using was taken from there.
First I did the wipes on Twrp but my internal storage wasn't recognized when the phone booted, so I had to wipe using stock recovery and it worked, now I can use my internal memory on Twrp.
Click to expand...
Click to collapse
Hi,
first, fstab is from Mate 9. The only diff with View 10 is this line.
Code:
/devices/platform/e7f00000.hifi_usb/* auto auto defaults voldmanaged=usbotg:auto
you can add it in my fstab if you want for your device
for the second question ,I have already noted that for me, just restart in recovery mode to fix this
With TWRP do you use ?
micky387 said:
Hi,
first, fstab is from Mate 9. The only diff with View 10 is this line.
you can add it in my fstab if you want for your device
for the second question ,I have already noted that for me, just restart in recovery mode to fix this
With TWRP do you use ?
Click to expand...
Click to collapse
Thanks for the answer
On my last testing, I flashed your fstab without problems and wiped using stock.
To flash your zip, first I need to use this twrp https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 it boots even if the phone is encrypted but you need a sdcard, after the decrypt is done, I replace it with this twrp https://marijuana.ddo.jp/cm/recovery
sfoot13 said:
Thanks for the answer
On my last testing, I flashed your fstab without problems and wiped using stock.
To flash your zip, first I need to use this twrp https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 it boots even if the phone is encrypted but you need a sdcard, after the decrypt is done, I replace it with this twrp https://marijuana.ddo.jp/cm/recovery
Click to expand...
Click to collapse
Thanks do you have a xda link of the second TWRP ?
It's just to see if it use too a symlinks script for our partitions
micky387 said:
Thanks do you have a xda link of the second TWRP ?
It's just to see if it use too a symlinks script for our partitions
Click to expand...
Click to collapse
No, I saw the link on this post https://forum.xda-developers.com/showpost.php?p=77262856&postcount=166 but I think @love_marijuana is the dev, because of the splash screen of the twrp :silly: talk to him bro.
OP Updated
2018-11-01
* Add new Android File Host Download link
* Add new MINADBD
* Fix selinux denial with stock kernel
Click to expand...
Click to collapse
We can use all TWRP feature now in Stock kernel.
Because Huawei has removed setenforce permission into kernel , the recovery script (setenforce 0) dont work , so "use" adb and other stuff was blocked by selinux
Fix all selinux denial by this commits
Return to stock emui/encryption
Hello!
I have a mate 9 c432 b370 with LineageOS 16 by micky (but due to stopped development i want to go back, the other treble roms just aren't working that well as rhis one, and I'm having a bit of bad battery life right now)
My question is:
"If you want to come back to stock EMUI/Encryption data ,reboot into erecovery and use "download last firmware and recovery" and follow the steps"
Is this the only way to go back to stock/encryption?
A wipe data or factory reset on emui stock recovery wouldn't work?
I'm asking because i have decrypted a while ago.
The last time i tried to use erecovery it said "no packages available" with an exclamation mark.
I have flashed stock system, kernel, ramdisk and recovery to boot back several times, but this time i have decrypted the internal storage...
Just need confirmation and/or possible solution to this. @micky387
Thanks in advance
hello @micky387
noob question. is it possible to work on a mate 8 debrand(AL10C00) atm im running openkirin omnirom 5.2,
would like to try other gsi roms. to check the most compatible rom..
your reply is very much appriciated
thank you
P10 Lite / WAS-LX1
Works on P10 Lite (WAS-LX1) with a fitting TWRP (I used Darkjokers 3.3.1). Used the zip over ADB sideload, so no external SD needed. Thanks for showing us da wae pal :good:
Hey dudes will this work on mate 8 Oreo ? If soon could you mod it for it ? Thanks
c|nder said:
Hey dudes will this work on mate 8 Oreo ? If soon could you mod it for it ? Thanks
Click to expand...
Click to collapse
If you check by the dates, it was all discussed at the time of EMUI 8/Oreo.
Earlier with Nougat, there was no such problem (TWRP was able to access internal storage).
To the other side, with current EMUI 9.1, Vendor is read-only and proposed modifications will not work
Hi all!
I've been using the 6T for a while (great phone, veeeery slippery!), I've rooted it without any problem (twrp-3.2.3-x_blu_spark_v9.86_op6).
Now, before doing the OTA updates, I want to do a nandroid backup, but it always fails with the message:
Code:
I:Error adding file '/data/data/tcTMGKoV3DJi2BtFo,DVwA/NdOFCMKtKQfG60hOSGJXIB/utPFuENU2UMyfeNmcGVBFC' to '/usbstorage/TWRP/BACKUPS/506bb395/2018-12-09--12-59-20/data.ext4.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/usbstorage/TWRP/BACKUPS/506bb395/2018-12-09--12-59-20/data.info'
[B]createTarFork() process ended with ERROR: 255[/B]
Backup Failed. Cleaning Backup Folder.
When TWRP starts it doesn't ask for the password (I've a password, no patern).
I've tried to decrypt in the terminal
Code:
~ # twrp decrypt PASSWORD
Attempting to decrypt data partition via command line.
Failed to decrypt data
The log:
Code:
I:Command 'decrypt PASSWORD' received
I:Set page: 'singleaction_page'
I:operation_start: 'TWRP CLI Command'
Attempting to decrypt data partition via command line.
get_crypt_ftr_info crypto key location: ''
Unexpected value for crypto key location
Error getting crypt footer and key
Failed to decrypt data.
Am I the only one having this problem?
How can I solve it?
Thanks!
The only reason I know of to use the BluSpark recovery is if you want to use OP6 roms? Why aren't you using one of the OP6T TWRP?
Right now there are problems with backup and recovery anyways, so you maybe out of luck even if you did have a backup. I've had zero issues updating my phone flashing the full package. Just make you flash the TWRP installer again after you flash the the full ROM, reboot to recovery again, flash Magisk again. Reboot to the system finally. Instructions for TWRP users are in this post.
OhioYJ said:
The only reason I know of to use the BluSpark recovery is if you want to use OP6 roms? Why aren't you using one of the OP6T TWRP?
Click to expand...
Click to collapse
Because I've followed this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ and right now I want to stay on OxygenOS. I've been on LineageOS for years and I love all the settings that it has, but I'm tired of unstable ROMS!
Right now there are problems with backup and recovery anyways, so you maybe out of luck even if you did have a backup. I've had zero issues updating my phone flashing the full package. Just make you flash the TWRP installer again after you flash the the full ROM, reboot to recovery again, flash Magisk again. Reboot to the system finally. Instructions for TWRP users are in this post.
Click to expand...
Click to collapse
Well...I'll try without a backup... :fingers-crossed:
andrea_x said:
Because I've followed this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ and right now I want to stay on OxygenOS. I've been on LineageOS for years and I love all the settings that it has, but I'm tired of unstable ROMS!
Well...I'll try without a backup... :fingers-crossed:
Click to expand...
Click to collapse
The guide you are following is over a month old now and development has progressed since then. The principals are the same, just use one of the newer TWRP, specifically for the OP6T. Though currently unofficial, most of the features now work, including decryption. I believe one of the test versions supports full backup and restore also now, though I haven't tested it myself. Great work from XDA developers as usual.
I can confirm, both of the new, unofficial twrps's are fully functional. As far as the necessities go. Not sure about aroma, as I don't use any of those. But, backup and restore, function perfectly. As well as decryption, obviously
Nandroid backup
andrea_x said:
Hi all!
I've been using the 6T for a while (great phone, veeeery slippery!), I've rooted it without any problem (twrp-3.2.3-x_blu_spark_v9.86_op6).
Now, before doing the OTA updates, I want to do a nandroid backup, but it always fails with the message:
Code:
I:Error adding file '/data/data/tcTMGKoV3DJi2BtFo,DVwA/NdOFCMKtKQfG60hOSGJXIB/utPFuENU2UMyfeNmcGVBFC' to '/usbstorage/TWRP/BACKUPS/506bb395/2018-12-09--12-59-20/data.ext4.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/usbstorage/TWRP/BACKUPS/506bb395/2018-12-09--12-59-20/data.info'
[B]createTarFork() process ended with ERROR: 255[/B]
Backup Failed. Cleaning Backup Folder.
When TWRP starts it doesn't ask for the password (I've a password, no patern).
I've tried to decrypt in the terminal
Code:
~ # twrp decrypt PASSWORD
Attempting to decrypt data partition via command line.
Failed to decrypt data
The log:
Code:
I:Command 'decrypt PASSWORD' received
I:Set page: 'singleaction_page'
I:operation_start: 'TWRP CLI Command'
Attempting to decrypt data partition via command line.
get_crypt_ftr_info crypto key location: ''
Unexpected value for crypto key location
Error getting crypt footer and key
Failed to decrypt data.
Am I the only one having this problem?
How can I solve it?
Thanks!
Click to expand...
Click to collapse
Hey were you able to solve the problem? If yes, please tell how?
I'm using twrp-fajita-3.2.3-8-installer.zip and it works.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
ZeRoZeRoRaZ said:
I'm using twrp-fajita-3.2.3-8-installer.zip and it works.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Click to expand...
Click to collapse
It says backup still having some problem and I already have installed twrp blu spark version. I think this problem is due to encrypted phone.
I'm running into this issue, too. I just flashed the latest OP zip as well as TWRP installer, and after flashing a ROM and TWRP installer, I rebooted to TWRP. I was about to flash Magisk and gapps, however I discovered my filenames were all scrambled.
sabrdawg said:
I'm running into this issue, too. I just flashed the latest OP zip as well as TWRP installer, and after flashing a ROM and TWRP installer, I rebooted to TWRP. I was about to flash Magisk and gapps, however I discovered my filenames were all scrambled.
Click to expand...
Click to collapse
This means your phone is encrypted, decrypt it first.
mansi0312 said:
This means your phone is encrypted, decrypt it first.
Click to expand...
Click to collapse
Do you mean by formatting data via TWRP? I can do that, once I get home and can copy all my files to my computer.
sabrdawg said:
Do you mean by formatting data via TWRP? I can do that, once I get home and can copy all my files to my computer.
Click to expand...
Click to collapse
If you have a oneplus 6t it won't work, decryption is still an issue on oneplus 6t. If you want to decrypt this badly you can follow this thread. I haven't tried it yet but you can give it a go. Do tell how did it go.
https://forum.xda-developers.com/one...overy-t3861482
Meanwhile or if you don't want to decrypt your phone, you can install magisk and gapps via adb sideload or using an otg. It has nothing to do with encryption. Encrypted phone will not let you make nandroid backups on the phone's internal storage and you will have to flash zip files using adb sideload or otg storage.
I have installed zips with this method without decrypting the phone.
sabrdawg said:
I'm running into this issue, too. I just flashed the latest OP zip as well as TWRP installer, and after flashing a ROM and TWRP installer, I rebooted to TWRP. I was about to flash Magisk and gapps, however I discovered my filenames were all scrambled.
Click to expand...
Click to collapse
Latest OnePlus Zip and Gapps? Why would you flash Gapps?
In my experiences this is caused by:
1. TWRP did not ask for a PIN, which can be corrected by another reboot (typically).
2. You are trying to use a OP6 recovery and a OP6T ROM, or vice versa. In that case, use the correct recovery for the ROM you are trying to use and your data will become readable. Even if you only need it to be temporary to pull it.
3. You ran AOSP rom and now your DATA partition is formatted for that. It will have to be formatted before OP6T recovery will read it. A OP6 recovery will read it.
There are no problems with OP6T recovery that I've found decrypting anything if you are aware of the caveats. So far the only issue really seems to be backing up / restoring still. Hopefully this helps.
*edit* I should add that OP6 recoveries would read AOSP data partitions before, I haven't tested this since the release of "dedicated" OP6T AOSP roms. So let us know what you find. *edit*
I ran across the same problem with my OnePlus 6.
Just do this:
- Download official twrp.
- Reboot to fastboot mode
- boot with it (fastboot boot ***.img)
Now it will temporarily boot and ask for decrypt password. Hola!
mansi0312 said:
Hey were you able to solve the problem? If yes, please tell how?
Click to expand...
Click to collapse
I've flashed twrp-fajita-3.2.3-8-installer
andrea_x said:
I've flashed twrp-fajita-3.2.3-8-installer
Click to expand...
Click to collapse
Hey,
Isn't fajita recovery for OP6?
mansi0312 said:
Hey,
Isn't fajita recovery for OP6?
Click to expand...
Click to collapse
No, fajita is the name code of op6t, didn't you notice that there are a lot of fajitas in threads names ?
---------- Post added at 07:13 AM ---------- Previous post was at 07:12 AM ----------
andrea_x said:
I've flashed twrp-fajita-3.2.3-8-installer
Click to expand...
Click to collapse
Try the latest version, -28
Striatum_bdr said:
No, fajita is the name code of op6t, didn't you notice that there are a lot of fajitas in threads names ?
---------- Post added at 07:13 AM ---------- Previous post was at 07:12 AM ----------
Try the latest version, -28
Click to expand...
Click to collapse
Is this a stable version?
mansi0312 said:
Is this a stable version?
Click to expand...
Click to collapse
Yes
I'm having the same issue and flashing the latest TWRP didn't solve it. Can't boot into system either, it just loops me back to TWRP.