Related
Guys,
I have had an device impacted by TWRP 2.7.X build that created the problem of not being able to mount /data and sometimes(/cache & /system) partitions.
I have managed to make it run a ROM by using information from
http://forum.xda-developers.com/showthread.php?t=1869673 & http://forum.xda-developers.com/showthread.php?t=1843062.
the problem is that the mounts are not remaining permanent and my modified boot.img does not boot the devices. So i have to mount the partition manually during the boot process over a shell and then the device boots.
Need help from experts to do a kernel which can mount sdext partition and an updated recovery image which also mounts the sdext partition as /data so that roms can be flashed easily.
I will try and do a writeup of how i made it run.
Resurrecting Pyramid
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Jack Daniel's said:
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
rmann said:
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
Click to expand...
Click to collapse
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Jack Daniel's said:
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Which recovery are you using... I have re-tested the script and it works ok for me.
rmann said:
Which recovery are you using... I have re-tested the script and it works ok for me.
Click to expand...
Click to collapse
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
antiziclon said:
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
Click to expand...
Click to collapse
did you try to update the recovery to the latest version?
rzr86 said:
did you try to update the recovery to the latest version?
Click to expand...
Click to collapse
Just tested with v1.0.0.6 RC3 build 8, same error
antiziclon said:
Just tested with v1.0.0.6 RC3 build 8, same error
Click to expand...
Click to collapse
redownload the zip file
after that i am out of ideas
ok, I found out the issue.
The issue is on the encoding of the "updater-script" file.
It needs to be in Unix encoding. If you use Windows (as I do) when unzipping the Zip file or when creating a new file with a text editor, the encoding gets changed and it is not Unix encoding.
To solve it:
- Open the file in Notepad++.
- Go to Edit --> EOL Conversion --> UNIX
It will change the enf of lines to comply with Unix encoding. Then add the file to the Rom zip file and you are ready to go
Enjoy!
Successful Pyramid rescue
I have a sensation with corrupted emmc caused by TWRP, /data cannot be mounted.
I followed your instructions and addition re script encoding and successfully installed Revelation to partitioned sdcard.
Phone boots and works.
That's great, thanks.
I have some questions:
1. Is 512 MB sufficient for swap partition? What would be the optimal size?
2. My sensation is s-on unlocked, and I had to flash boot via fastboot after install, 4ext did not flash it despite smartflash option turned on. Is that normal?
2. Superuser does not seem to work, I have no root. I checked with root validator and I have su binary, superuser and busybox, but no root is given to apps that require it, su binary update fails, and there are no logs left in superuser to check (or I simply don't know where to look).
Thank you.
rmann said:
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Click to expand...
Click to collapse
Ok try to make that in unix
Extreme lag
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Extreme unuseful slow
With my sensation XE i also followed all steps. Revelation 1.0.3 is booting, but not to use at all, it stucks in every step, cant even receive a call, can't go to any menu. Pls someone help me out of here. Do I need a swap partition? Or are the partitions to small? sd-ext has 1024Mib; sd-ext2 1537Mib.
danilandroid said:
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Click to expand...
Click to collapse
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
probably you need a sdcard with high speed of w/r but i am not sure
Lag
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
danilandroid said:
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
Click to expand...
Click to collapse
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
So, I bought a class 10 card, revelation is running now!! At first start it was still very slowly an got stuck allover. But at second start it is running now! Thanks for that perfect thread!!:good:
I wonderd why vipers wont start the same way? When I try to boot it , 4ext recovery is starting rightaway with little delay!
Hi, when I got the same problem with /data, /cache and /system not mounting. I followed the steps from #2 post http://forum.xda-developers.com/showpost.php?p=55157092&postcount=2
and when I try to install from zip it says that the zip isn't meant to be flashed in recovery and it aborts the installation. First I tried renaming the new_boot.img you provided to boot.img but it's the same result.
Tried to flash Sailfish OS on my moto g 1st gen using TWRP but i keep getting this error. E:Error executing updater binary in zip '/sdcard/sailfishos-falcon-release-1.1.7.28-my4.zip'
Error flashing zip '/sdcard/sailfishos-falcon-release-1.1.7.28-my4.zip'
Prymston said:
Tried to flash Sailfish OS on my moto g 1st gen using TWRP but i keep getting this error. E:Error executing updater binary in zip '/sdcard/sailfishos-falcon-release-1.1.7.28-my4.zip'
Error flashing zip '/sdcard/sailfishos-falcon-release-1.1.7.28-my4.zip'
Click to expand...
Click to collapse
No other error messages before these? Try "adb pull /tmp/recovery.log" and post the file.
_that said:
No other error messages before these? Try "adb pull /tmp/recovery.log" and post the file.
Click to expand...
Click to collapse
Sorry for the noobie question but do i post the whole log here or do i upload the file? :silly:
Known issue:
When flashing, I get the following: "E:Error executing updater binary in zip"
This is a custom recovery bug. Try restarting recovery and flashing again. Alternatively you may need to format /data (userdata) in Custom Recovery. Note: This will delete anything on internal storage - photos, music, videos etc.
Prymston said:
Sorry for the noobie question but do i post the whole log here or do i upload the file? :silly:
Click to expand...
Click to collapse
I don't know if Junior members are allowed to attach files to posts. If not, upload it to some paste site and post the link (you'll need to remove things like "http://" to be allowed to post it).
lost101 said:
Known issue:
When flashing, I get the following: "E:Error executing updater binary in zip"
This is a custom recovery bug.
Click to expand...
Click to collapse
Unlikely - if the recovery could not run update binaries at all, someone would have noticed. Why should restarting recovery change anything? What exactly is the bug?
lost101 said:
Known issue:
When flashing, I get the following: "E:Error executing updater binary in zip"
This is a custom recovery bug. Try restarting recovery and flashing again. Alternatively you may need to format /data (userdata) in Custom Recovery. Note: This will delete anything on internal storage - photos, music, videos etc.
Click to expand...
Click to collapse
I tried that didn't work
Prymston said:
I tried that didn't work
Click to expand...
Click to collapse
Make sure to use the following option: TWRP > Wipe > Format Data > Yes
can't post log? probably to much text?
where can i post the log? I can't post it here.
i posted the recovery.log on google drive
Prymston said:
i posted the recovery.log on google drive
Click to expand...
Click to collapse
The script expects the device name to be "falcon":
Code:
script aborted: assert failed: getprop("ro.product.device") == "falcon" || getprop("ro.build.product") == "falcon" || getprop("ro.cm.device") == "falcon"
But your TWRP version calls it "xt1032":
Code:
ro.product.name=XT1032
ro.build.product=xt1032
ro.cm.device=xt1032
Workaround: replace "falcon" with "xt1032" in updater-script inside the zip file.
New Log.
Prymston said:
New Log.
Click to expand...
Click to collapse
Looks fine. The mount error is probably because /data is already mounted, which it must be to read the zip from the emulated sdcard.
_that said:
Looks fine. The mount error is probably because /data is already mounted, which it must be to read the zip from the emulated sdcard.
Click to expand...
Click to collapse
but i get a black screen when booting sailfish os, somethings not right.
Prymston said:
but i get a black screen when booting sailfish os, somethings not right.
Click to expand...
Click to collapse
Did you get it to flash properly now?
If yes, you should try another CM12.1 nightly. I posted a working one in the Sailfish thread
k-kuchen said:
Did you get it to flash properly now?
If yes, you should try another CM12.1 nightly. I posted a working one in the Sailfish thread
Click to expand...
Click to collapse
It worked! Thank you
"This package is for A0001, this device is bacon." Wiped internal storage, cant flash
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
If you can acces TWRP, just by connecting the OPO to your PC should give you acces to storage. I guess that you are trying to install H2OS, download the fixed version with the updater-script fixed. If it gives you this error with another rom, just download another custom rom and put in on the internal storage or flash the stock OS with fastboot
KuranKaname said:
If you can acces TWRP, just by connecting the OPO to your PC should give you acces to storage. I guess that you are trying to install H2OS, download the fixed version with the updater-script fixed. If it gives you this error with another rom, just download another custom rom and put in on the internal storage or flash the stock OS with fastboot
Click to expand...
Click to collapse
Yep, inside the rom zip, there is a file called updater-script.
In this file, there is a line checking the phone name.
While most of the roms are using "bacon", H2OS original zip file uses "A0001" instead.
Can you try with any other rom?
niranjanbhat said:
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
Click to expand...
Click to collapse
Instead of using adb push metod try to flash stock rom (https://forums.oneplus.net/threads/oxygenos-2-1-4-for-the-oneplus-one.425544/) and then flash the rom you want.
Good luck!
Note: You will loose twrp, so you have to flash it via fasboot [fastboot flash recovery (recovery name).img]
I'd suggest you to start over with a clean flash of COS13 fastboot factory image. Sounds like you are on a very old base.
Try to reboot TWRP and flash again. Or remove that check string from the updater-script.
download CM11 factory recover tool from my google drive @ https://drive.google.com/open?id=0ByfGPjP5zNYSTDZZcXZpLU44Q00 and install drivers and go to fastboot and plug in the phone and run recovery tool to push default factory image then install whatever CM version you want directly
No updater-script file that I can see
Can't find that file!
Anghirrim said:
Yep, inside the rom zip, there is a file called updater-script.
In this file, there is a line checking the phone name.
While most of the roms are using "bacon", H2OS original zip file uses "A0001" instead.
Can you try with any other rom?
Click to expand...
Click to collapse
use usb otg, success each time!
setup on ubuntu
Instructions for install on linux (test on ubuntu)
1- install adb :
Code:
$ sudo apt-get install android-tools-adb
2- install fastboot :
Code:
$ sudo apt-get install android-tools-fastboot
3- Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
4- test if the phone is detected with the cmd :
Code:
$ fastboot devices
5- unlock bootloader (/!\ it wipe the phone) :
Code:
$ sudo fastboot oem unlock
6- install TWRP :
- go to the path where is the img
Code:
$ cd path/to/twrp/folder/
- rename the image to twrp.img
Code:
$ mv old_name.img twrp.img
- flash the recovery
Code:
$ sudo fastboot flash recovery twrp.img
/!\ Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually turn it off by pressing and holding power button until it switches off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode. Now that you have a custom recovery, you may continue to the final step. /!\
7- install custom/official ROM with TWRP :
- Wipe > Swipe to Factory Reset
- Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
- Install GApps using same process as ROM, then reboot. (optionnal: the official OnePlus ROM come with GApps pre-installed)
Possible errors with official ROM :
"This package is for device: A0001; this device is bacon" or "This package is for device: OnePlus; this device is A0001" or other similar
==> go into the ROM zip file, in "/META-INF/com/google/android/" there is an "updater-script" file. Open it, locate the expression ' getprop("ro.build.product") == "A0001" ' and replace the "A0001" by the device name you have. Replace the file in the archive. Note : after that, you can't verify the official MD5 !
- example : "This package is for device: A0001; this device is bacon", the ' getprop("ro.build.product") == "A0001" ' become getprop("ro.build.product") == "bacon" '
Sources :
https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
https://forum.xda-developers.com/oneplus-one/help/package-a0001-device-bacon-wiped-t3457766
Oneplus one Oxygen Installation error using TWRP
niranjanbhat said:
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
Click to expand...
Click to collapse
check this post
wirelessindeed.blogspot.com/2017/07/oxygen-installation-error-on-oneplus.html
Update TWRP Recovery
I know this is an old post, so this is here in case anyone finds it in the future and requires help...
My mate asked me to upgrade his OnePlus (original, codename Bacon) and I received this error when upgrading from LineageOS 14.1 to 15.1.
To resolve, its extremely easy - simply upgrade the TWRP recovery. My mate originally had TWRP 3.1.1.0 installed, but the latest weekly LineageOS 15.1 required v3.2.3.0 installed which resolved the error message "This package is for device: bacon, a1001. this device is ."
Either Vol+ and Power to enter bootloader, or from command line:
adb reboot bootloader (with Android USB debugging turned on. You can test for connection using command "adb devices" and if successful it should show your phone's serial number). You will need to trust the computer's connection on your phone. To get to Android USB Debugging, you need to go Settings -> Developer menu options, and if you can't see that: Settings -> About Phone and tap "Build" 7 times for developer mode to appear.
Once phone goes into bootloader mode, type:
fastboot flash recovery "path:\twrp-x.x.x.x-bacon.img" (obviously path is the directory that the recovery is stored in, and x.x.x.x will be replaced with the version you've just downloaded. At time of writing, v3.2.3.0 is the latest. You can always use "fastboot devices" if you used Vol+ and Power to enter bootloader to ensure you have a valid connection, in USB debugging mode on your phone and correct Android adb drivers installed in Windows.
Wait until it's succeeded, and turn off phone. Now go into recovery and try again - and this time you should be good to go!!!
All the above implies your bootloader is unlocked. If you need to unlock your bootloader, there are plenty of instructions telling you how to do this - but HAVE A BACKUP as unlocking your bootloader will do a factory reset on your phone.
Hope this helps someone
......mmmmmm BACON!!!
Hello,
I can update my shield tablet. I get that error:
Code:
Updating partition details …
… done
Full SELinux support is present
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file …
Sskipping MD5 check*: no MD5 file found
Source*: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys
Target: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys
Verifying current system...
Package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys or nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys*; this device has nvidia/sb_na_wf/shieldtablet:6,0:MRA58K/41524_664,1902:user/release-keys.
Update process ended with ERROR*: 7
Error installing installing zip file '@/cache/recovery/block.map'
Done processing script file
MTP Enabled
Can someone help me?
bird12358 said:
Hello,
I can update my shield tablet. I get that error:
Code:
Updating partition details …
… done
Full SELinux support is present
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file …
Sskipping MD5 check*: no MD5 file found
Source*: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys
Target: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys
Verifying current system...
Package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys or nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys*; this device has nvidia/sb_na_wf/shieldtablet:6,0:MRA58K/41524_664,1902:user/release-keys.
Update process ended with ERROR*: 7
Error installing installing zip file '@/cache/recovery/block.map'
Done processing script file
MTP Enabled
Can someone help me?
Click to expand...
Click to collapse
some more information might help people help you mate, are you rooted, do you have a custom recovery installed or are you running a custom rom? things like that help us alot
I user to be as root. But I restore factory setting ans I still have thé error.
Should i made an other thing to suppress thé root settings.?
Yes Mate I thought no so do you have a custom recovery installed
Sent from my HTC One using Tapatalk
I don t think I have that recovery installed. Where could I find this?
bird12358 said:
I don t think I have that recovery installed. Where could I find this?
Click to expand...
Click to collapse
Turn off your tablet then hold volume down and the power button untill you get to the boot loader then use the volume down button to select recovery and press power if you have a custom recovery it will bot to it and it will say team win recovery
Sent from my HTC One using Tapatalk
It seems I don t have a custom recovery. How should I do nos?
I ran into a problem trying flashing LineageOS 16 into my one
I flashed newest twrp 3.3.0 successfully
But when I tried to use adb sideload to flash LineageOS a problem happened
The flashing process just ended immediatly
In the command prompt it says:
serving: 'lineage-16.0-20190422-nightly-bacon-signed.zip' (~0%) adb: failed to read command: No error
On my phone it says:
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'
Waring: No file_contexts
Comparing TZ version TZ.BF.2.0-2.0.0109 to TZ.BF.2.0-2.0.0096
Comparing TZ version TZ.BF.2.0-2.0.0123 to TZ.BF.2.0-2.0.0096
Comparing TZ version TZ.BF.2.0-2.0.0134 to TZ.BF.2.0-2.0.0096
assert failed: oppo.verify_trustzone("TZ.BF.2.0-2.0.0109","TZ.BF.2.0-2.0.0123","TZ.BF.2.0-2.0.0134") == "1"
Updater process ended with ERROR: 7
I don't know what to do now, I googled, no one seems to have the same problem, I tried on a different computer, didn't work, I pushed the install package into my phone's storage and install from there, didn't work
Can anyone help?
I don't think you should be trying to adb sideload, just wipe Data, System, Dalvik, Cache (without internal storage) and flash the zip.
Be warned, lineage 16 currently has an issue where the wifi is unstable if used with gapps (https://gitlab.com/LineageOS/issues/android/issues/392).
You mean flash the zip from internal storage? I tried that, didn't work, same problem
Does it work with an older version of TWRP?
SethGeckoXDA said:
Does it work with an older version of TWRP?
Click to expand...
Click to collapse
Tried that, didn't work, same problem
tkgrand said:
Tried that, didn't work, same problem
Click to expand...
Click to collapse
I think this is because the modem needs to be updated before flashing.
Try flashing this modem zip before flashing rom. ---> https://androidfilehost.com/?fid=24052804347825946
Steps:
1.Open twrp
2.Flash modem
3.Flash lineage
3.Flash gapps
4.Restart
vicky2131 said:
I think this is because the modem needs to be updated before flashing.
Try flashing this modem zip before flashing rom. ---> https://androidfilehost.com/?fid=24052804347825946
Steps:
1.Open twrp
2.Flash modem
3.Flash lineage
3.Flash gapps
4.Restart
Click to expand...
Click to collapse
Yes! It works! Thank You!
twrp-3.6.2_9-0-bacon.img 14.9M 2022-05-30 00:09:30 UTC works as well. Thank you.