I'm trying to install ROM from this thread: [ROM][UNOFFICIAL] CyanogenMod 11 [Android 4.4.4]
And I'm always getting errors.
I've tried to istall two packages:
cm-11-20140715-NIGHTLY-liberty.zip
cm-11-20140614-EXPERIMENTAL-liberty.zip
And both resulted with the same error:
Code:
-- Installing: SDCARD:clockworkmod/rom/cm11/cm-11-20140715-NIGHTLY-liberty.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/clockworkmod/rom/cm11/cm-11-20140715-NIGHTLY-liberty.zip
(Status 0)
Installation aborted
What could be the problem?
Phone was "factory reset" before updating from ZIP package.
Here is HTC Aria, Clockworkmod Recovery 2.5.0.7.
P.S. Unfortunately I have no rights to post the question directly in that thread (see link above). I'm posing with a hope, that the developer (WinSuk) will read this thread...
if you want the developer to see it, you need to mention him like this @xd0
look at your mentions, you should have one from me and this post.
bweN diorD said:
if you want the developer to see it, you need to mention him like this @xd0
look at your mentions, you should have one from me and this post.
Click to expand...
Click to collapse
Thank you, @bweN diorD
It looks like with the current forum's rules, I can't even sent IM to @WinSuk. After I tried to sent my message to him (pointing to this thread), I can't see that sent messages in my profile ("Sent Items contains 0 messages.")...
BTW, how to mention names, containing more then one word (e.g. like yours)? Should I use "" (or something else) around the whole name?
xd0 said:
Thank you, @bweN diorD
It looks like with the current forum's rules, I can't even sent IM to @WinSuk. After I tried to sent my message to him (pointing to this thread), I can't see that sent messages in my profile ("Sent Items contains 0 messages.")...
BTW, how to mention names, containing more then one word (e.g. like yours)? Should I use "" (or something else) around the whole name?
Click to expand...
Click to collapse
you did it right, i got the mention
Install the recommended recovery linked in the thread OP (this one)
I'll update it to say required instead so there's less problems in the future.
I've tried two different ways to update recovery image to v6.0.2.8.
1. Used "Unrevoked3 v3.32" ("reflash_package_3.32.exe" v1.2.0.715, CRC32: 1062F0D9):
1.1. Disconnect phone form PC
1.2. Launch the program
1.3. Point to "custom" recovery image (recovery_6.0.2.8.img, CRC32: 1A7669DF).
1.4. Connect phone to PC (via USB cable) and it starts flashing immediately
After several phone reboots, Unrevoked3 reported - "Failed to flash recovery image"
2. Used fastboot from Android tools. Result is the same. See log:
Code:
D:\Dev\Phone\Android\Tools>fastboot flash recovery recovery_6.0.2.8.img
sending 'recovery' (4212 KB)... OKAY [ 5.870s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 7.212s
At this point there is no recovery installed on the phone, meaning I can't restore any nandroid backup made earlier with corresponding revovery image...
Is there any other way to flash that recovery_6.0.2.8.img?
I've recovered old Recovery v2.5.0.7 using fastboot tool. Then I've tried to update Recovery from v2.5.0.7 to recommended v6.0.2.8 using ... Recovery itself.
1. Copy cwm-6.0.2.8-UNOFFICIAL-liberty.zip into SD card
2. Put phone into Recovery and ask it to "install zip from sdcard"
After a brief log in its console phone went to boot... and hang. I was not able to go to Recovery after that.
Finally I've restored the old Recovery v2.5.0.7 back using fastboot tool again...
The new Recovery image is noticeably bigger, than what I use now. In order to install that bigger image, do I need to do something special here? E.g. change recovery partition size or may be do something else?
Just in case the phone has HBOOT-6.02.1002.
Flashing through fastboot should work fine if it says HBOOT-6.02.1002 :-\
Unrevoked is for the older bootloader(s), so that won't work..
Just to confirm, it says "-Revolutionary-" in pink at the top of the bootloader/fastboot?
Bootloader page:
Code:
-Revolutionary- {white font on pink background}
LIBERTY PVT SHIP S-OFF
HBOOT-6.02.1002
MICROP-031b
TOUCH PANEL-STN21_03
RADIO-7.16.35.11
Nov 4 2010,23:12:58
Here is exact log from CMD window:
Code:
D:\Dev\Phone\Android\Tools>fastboot flash recovery recovery_6.0.2.8.img
sending 'recovery' (4212 KB)... OKAY [ 5.599s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 6.931s
After that error, any attempt to go to recovery from boot screen, causes phone to hang. It gets white screen with HTC and nothing more. Then I have to remove battery to boot it again.
Everything on your bootloader is exactly the same as mine, so it should be working... I even downloaded and tried it again to make sure
I can think of three things:
You have a bad download - try downloading it again
The fastboot you're using (on Windows) is really old - you can flash other things, so nevermind
Your device is somehow different, and it's too big (same error message as images that are) - try flashing the version without offmode charging (it's a little smaller)
If nothing else works, there's other ways of getting the ROM running I can probably help with, but OTA updates won't work without the recovery...
@WinSuk, thanks a lot for your help. I've tried to install Revolutionary v6.0.2.8 without off-mode charging and it succeeded! Indeed, it looks like the problem is with package size. Here is the log from CMD:
Code:
D:\Dev\Phone\Android\Tools>fastboot flash recovery "D:\Storage\Phone\HTC Aria\Recovery\cwm-6.0.2.8.img"
< waiting for device >
sending 'recovery' (4212 KB)... OKAY [ 5.849s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 7.161s
D:\Dev\Phone\Android\Tools>fastboot flash recovery "D:\Storage\Phone\HTC Aria\Recovery\cwm-6.0.2.8-wc.img"
sending 'recovery' (3998 KB)... OKAY [ 5.348s]
writing 'recovery'... OKAY [ 1.342s]
finished. total time: 6.690s
Then I was able to install new ROM, built 14-07-15. I couldn't believe that Android v4.4.4 could work on this device I start to play with it. So far so good...
Now, back to Recovery. I always have problems with battery (actually at this point of time I already have 5 batteries). All of them can't be charged to 100% and time-to-time I try to charge them when phone is off. Thus ability to charge phone while it's off is important to me.
Could you please take a look at the Recovery package supporting off-mode charging and try to reduce its size. So it could be installed on my device (I'd be glad to test it). From my experience of running the new Revolutionary v6.0.2.8 I (no charging support version) I see that it has a big image (nice and colorful one) of Android on the background, (which, BTW, makes it harder to see the menu items due to the bright green color of the image). I think in order to reduce package size it'd be helpful to completely remove that image from the package. I know it's nice and pretty. But the Aria has its big limitations on Recovery size and functionality is way more important, than the nice background image... What do you think? Will it help to fit the new Recovery with off-mode charging on my device?
Thanks again!
Sure... the off-mode charging isn't perfect though - the recovery behind it can still be used.
I changed the stitched background to black (it stuck on the HTC logo when I removed it), and fastboot says it's 4066 KB
That should be enough.. let me know if it isn't
https://drive.google.com/file/d/0B6gvebRGyJuKU21sa1lNZXpKUGc/edit?usp=sharing
It is indeed, enough. I've installed it without any problems. Now I've turned off the phone and connected it to charger - to see if it will be charged or not. The notification LED is red when it;s connected to charger and it's off in 4 sec after I disconnect it. Other than that there is no any indication that it's charging or not. It's OK, we'll see some results later After a while I'll let you know.
Can't wait to see how CM11 will run on this device... I'm trying to run it without Gaps (installing .APK packages directly from SD card) and using Link2SD to link new installed apps to second ext2 partition on SD. So far so good Thanks again!
@WinSuk, I've made first backup with new Recovery v6.0.2.8 and noticed, that it makes some extra empty files. I don't know how it will restore it later (have not tried it yet), but I think you may want to take a look at it a bit closely...
Here is all files created by Recovery v6.0.2.8:
Code:
140719 03:38 0 .android_secure.vfat.tar
140719 03:38 1,536 .android_secure.vfat.tar.a
140719 03:36 2,883,584 boot.img
140719 03:38 31,680 cache.yaffs2.img
140719 03:37 104,594,688 data.yaffs2.img
140719 03:38 465 nandroid.md5
140719 03:36 4,194,304 recovery.img
140719 03:38 0 sd-ext.ext2.tar
140719 03:38 72,626,176 sd-ext.ext2.tar.a
140719 03:37 233,980,032 system.yaffs2.img
Please note two extra files with 0 bytes size:
.android_secure.vfat.tar
sd-ext.ext2.tar
Is it normal? Or we may need do something to remove them?
Regarding the size of the Recovery image itself. I've checked all my old backups and it looks like Recovery partition on my Aria device is 4,194,304 bytes exactly. I don't think that I ever changed it from its default value (may be OTA did it some day?) It explains why I could not install your "v6.0.2.8 with off-mode charging" image (MD5:ed5ae3fa92c4facdc4e9f04b40e2afb5, size: 4,313,088), but was able to install "v6.0.2.8 without off-mode charging" image (MD5:abc699b0069d0b1505830ae93175fd61, size:4,093,952) and the latest "cwm-6.0.2.8-nobg-UNOFFICIAL-liberty.img" (MD5:1653261DFAD56B3C657B088822D63BBB, size:4,163,584).
Bottom line: recovery image limit for my device is - 4,194,304 bytes. If there is a bigger Recovery image, it will require to somehow change the size of that partition and I don't know if that even is possible...
xd0 said:
@WinSuk, I've made first backup with new Recovery v6.0.2.8 and noticed, that it makes some extra empty files. I don't know how it will restore it later (have not tried it yet), but I think you may want to take a look at it a bit closely...
Here is all files created by Recovery v6.0.2.8:
Code:
140719 03:38 0 .android_secure.vfat.tar
140719 03:38 1,536 .android_secure.vfat.tar.a
140719 03:36 2,883,584 boot.img
140719 03:38 31,680 cache.yaffs2.img
140719 03:37 104,594,688 data.yaffs2.img
140719 03:38 465 nandroid.md5
140719 03:36 4,194,304 recovery.img
140719 03:38 0 sd-ext.ext2.tar
140719 03:38 72,626,176 sd-ext.ext2.tar.a
140719 03:37 233,980,032 system.yaffs2.img
Please note two extra files with 0 bytes size:
.android_secure.vfat.tar
sd-ext.ext2.tar
Is it normal? Or we may need do something to remove them?
Regarding the size of the Recovery image itself. I've checked all my old backups and it looks like Recovery partition on my Aria device is 4,194,304 bytes exactly. I don't think that I ever changed it from its default value (may be OTA did it some day?) It explains why I could not install your "v6.0.2.8 with off-mode charging" image (MD5:ed5ae3fa92c4facdc4e9f04b40e2afb5, size: 4,313,088), but was able to install "v6.0.2.8 without off-mode charging" image (MD5:abc699b0069d0b1505830ae93175fd61, size:4,093,952) and the latest "cwm-6.0.2.8-nobg-UNOFFICIAL-liberty.img" (MD5:1653261DFAD56B3C657B088822D63BBB, size:4,163,584).
Bottom line: recovery image limit for my device is - 4,194,304 bytes. If there is a bigger Recovery image, it will require to somehow change the size of that partition and I don't know if that even is possible...
Click to expand...
Click to collapse
I'm not sure why they do the empty ones, but that's normal... the files ending in .a is where your data is.
If any of them get over a certain size, it breaks out into b, c, etc... but you can't open them by themselves until they are joined back together, so I think the empty file is supposed to be hinting at that.
Newer recoveries also do this for system and data
Related
Happy Easter to everybody!
Since a couple of days (when I tried several times to install WLegend 0.3), when I go to recovery and try to wipe dalvik-cache, i get an error message saying
Code:
run "wipe dalvik" via adb
I would like to overcome the problem reflashing the rav 1.5.2 on my magic, but when I try to do it via adb, the following message appears:
Code:
mtd: read error at 0x00020000 (Out of memory)
Can someone help me re-flashing the recovery?
Many thanks!!!
no one who wants to help me?
i've read somewhere that that error message that you get is bug in recovery and although it said that it didn't erased dalvik, it did.
so actually...you can flash your new rom without reflashing recovery or what so ever...
ya its a bug in the 1.5.2 recovery, upgrade to the latest 1.6 something
Sent from my HTC Magic using the XDA mobile application powered by Tapatalk
digitaljeff said:
ya its a bug in the 1.5.2 recovery, upgrade to the latest 1.6 something
Sent from my HTC Magic using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
The strange thing is that it started not immediatly, but after some correct wipes
Here is what I obtain trying to re-flah the recovery...
Code:
Microsoft Windows [Versione 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. Tutti i diritti riservati.
D:\sdk\tools>
D:\sdk\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
/ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or direc
tory
/ # flash_image recovery /sdcard/recovery-RA-sapphire-v1.5.2H.img
flash_image recovery /sdcard/recovery-RA-sapphire-v1.5.2H.img
header is the same, not flashing recovery
/ #
D:\sdk\tools>fastboot devices
HT95PKF06370 fastboot
D:\sdk\tools>fastboot flash recovery recovery-RA-sapphire-v1.5.2H.img
sending 'recovery' (4074 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
D:\sdk\tools>
The first time I flashed the custom recovery, all this sh!t didn't appeared!
I used flashrec and it worked like a charm. Anyway, why are you trying fo flash an old version of the recovery? Use the latest for your Magic (I'm guessing it's a 32A, since you're using the H recovery image), but be sure to verify the md5 checksum before.
A nice thing I did to quickly get my RA image back was save it to my SD, rename it to "recovery-backup", open up flashrec, and click "restore backup". That will flash your Amun RI, because the flashrec recognizes it as teh backup image because that what it saves the original image as.
keinengel said:
I used flashrec and it worked like a charm. Anyway, why are you trying fo flash an old version of the recovery? Use the latest for your Magic (I'm guessing it's a 32A, since you're using the H recovery image), but be sure to verify the md5 checksum before.
Click to expand...
Click to collapse
I'm trying to understand if the errors I get are due to the fact that I re-flash the same recovery or to some other problems...
knny1491 said:
A nice thing I did to quickly get my RA image back was save it to my SD, rename it to "recovery-backup", open up flashrec, and click "restore backup". That will flash your Amun RI, because the flashrec recognizes it as teh backup image because that what it saves the original image as.
Click to expand...
Click to collapse
Thanks, I'll try flashrec
/ # flash_image recovery /sdcard/recovery-RA-sapphire-v1.5.2H.img
flash_image recovery /sdcard/recovery-RA-sapphire-v1.5.2H.img
header is the same, not flashing recovery
/ #
Click to expand...
Click to collapse
Means that you already have the recovery that you are trying to flash...
D:\sdk\tools>fastboot flash recovery recovery-RA-sapphire-v1.5.2H.img
sending 'recovery' (4074 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
Means you dont have an engineering SPL.
P.S i suggest you use ROM manager from the market, it can flash a nice Clockwork recovery or amon_ra 1.6.2
Which MAgic do you have? a new 32a with 3.5mm headphone jack?
Also your erros just mean
1. Your flashing an older recovery then you have (or same)
2. your SPL is not "unlocked"
If you have a new mytouch 1.2 or fender you must use 1.6.2H
Also, you can do all this in terminal or buy putting the recovery ont he sd card and using adb shell.
But get a new recovery, your main problem is your using the one with taht exact known problem which is why it was updated.
Thank you all for the responses!
@ eyegor: if I understand, it is not possible to flash the same recovery (eg 1.5.2 on 1.5.2), am I right?
I don't need an engineering SPL in order to flash new roms, right?
@ crypysmoker: I have a standard 32A magic (no 3.5mm jack)
It is but not from terminal.
No, you do not.
I did the update to 1.6.2, now it's all ok! no errors updating, no errors wiping...
Thank you all for the support!
A little background, I am trying to flash a Honeycomb rom to my Archos 7HTv2. This is a custom rom that I put together. I know that Honeycomb requires much more power than my Archos can give me. I know that it would probably be unusable, but I was curious, and it brought up a problem.
The system.img for the HC rom is ~112mbs, the total update.img is ~123mbs
The system.img for the stock rom is ~51mbs the total update.img is ~54mbs
I first tried to flash it and got a "not enough space" error when flashing the system. I assumed that the stock rom barely fit in the system partition, so I went looking for how to make it bigger.
Flashing on the Archos is by putting an update.img in the SDcard, or by using the "BatchUpgrade" utility from the computer, which copies it to some temp on the device. Then the recovery takes over and installs the rom.
Code:
Writing KERNEL:...
Checking KERNEL:...
Writing BOOT:...
Checking BOOT:...
Writing SYSTEM:...
E:Write failed(No space left on device)
E:Failure at line 16:
write_image PACKAGE:system SYSTEM:
Update failed, please reboot and update again!
Line 16 refers to the update-script file which has the list of Writing & Checking.
When I flash the rom from the computer using "BatchUpgrade" it fails before it can attempt unpacking. It just tells me "FAILURE" and no specifics as to why. Because the img never begins unpacking makes me believe it might be the temp area is not big enough for the .img and the extracted components.
I found this mtd information in the HWDEF file (part of update.img)
Code:
#Format: part_name offset:size
parameter 0x00000000:0x00002000:fh
misc 0x00002000:0x00002000:f
kernel 0x00004000:0x00004000:f
boot 0x00008000:0x00002000:f
recovery 0x0000A000:0x00004000:f
system 0x0000E000:0x00030000:f
backup 0x0003E000:0x0003A000:
cache 0x00078000:0x0003A000:
userdata 0x000B2000:0x00100000:
user 0x001B2000:0xFFFFFFFF:
END
I changed the system and backup partitions to be bigger (the above is stock) but nothing happened. I then found the PARAMETER file which had a similar string of mtd definitions, I updated them as above. Still no luck.
Anyone have any ideas?
Thanks
Do you had any luck?
Hello I have the latest version of this rom http://forum.xda-developers.com/oneplus-one/development/rom-cm-12-builds-t3045053
and it was working great! I had no problems and then one day while playing an audio file (smart voice recorder), my phone froze for lke 30 seconds and then just rebooted by itself and started looping the android logo. Worried I booted into TWRP (3.0.2-0) and found out that in the logs I get these messages:
Could not mount /data and unable to find crypto footer.
Failed to mount /data (invalid argument)
Failed to mount /cache (invalid argument)
Unable to mount storage
What the hell, does this happen to anyone? Using their phone all ok and then bam reboot and now my internal storage is gone! Was it because I was using a 25 watt apple charger because I was recording video at the time and needed the juice. Oh man I really need those videos they mean everything to me!
system shows a size but very small like 1.3 gigs or something
data shows 0 mb for all stats
cache shows 0 mb for all stats
Internal Storage shows "invalid partition selection"
I have no idea what happened, I have such important data on this phone! How can I recover this? Please!!! I tried using the repairing data option and i got this error message
/sbin/efsck -fp /dev/block/mmcblk0p28 process ended with ERROR: 4
Unable to repair data
Will offer a bounty if someone can help me recover my data! I am knocking my own ass for not having a backup ugh
I will offer a bounty if someone with experience can help me through this. The memories of my mother's passing means a lot to me and I would hate to lose it because some stupid app crashed on me and the phone rebooted.
vap3 said:
Hello I have the latest version of this rom http://forum.xda-developers.com/oneplus-one/development/rom-cm-12-builds-t3045053
and it was working great! I had no problems and then one day while playing an audio file (smart voice recorder), my phone froze for lke 30 seconds and then just rebooted by itself and started looping the android logo. Worried I booted into TWRP (3.0.2-0) and found out that in the logs I get these messages:
Could not mount /data and unable to find crypto footer.
Failed to mount /data (invalid argument)
Failed to mount /cache (invalid argument)
Unable to mount storage
What the hell, does this happen to anyone? Using their phone all ok and then bam reboot and now my internal storage is gone! Was it because I was using a 25 watt apple charger because I was recording video at the time and needed the juice. Oh man I really need those videos they mean everything to me!
system shows a size but very small like 1.3 gigs or something
data shows 0 mb for all stats
cache shows 0 mb for all stats
Internal Storage shows "invalid partition selection"
I have no idea what happened, I have such important data on this phone! How can I recover this? Please!!! I tried using the repairing data option and i got this error message
/sbin/efsck -fp /dev/block/mmcblk0p28 process ended with ERROR: 4
Unable to repair data
Will offer a bounty if someone can help me recover my data! I am knocking my own ass for not having a backup ugh
Click to expand...
Click to collapse
In twrp if you go to advance then file manager click on sdcard can you see your files?
If not did you try to mount in twrp?
If so then you can pull the whole sdcard or select files via adb.
Durso81 said:
In twrp if you go to advance then file manager click on sdcard can you see your files?
If not did you try to mount in twrp?
If so then you can pull the whole sdcard or select files via adb.
Click to expand...
Click to collapse
for question #1 yes I do see my files. But certain folders like DCIM (pictures) or other apps such as whatapp is not showing.
when i try to mount in TWRP only firmware and system is checkable.... data/cache/usb-otg is not selectable (meaning check marks won't show up if I try to click it)
when I hit "select storage" i see the select storage options and both options (internal storage and usb-otg) says 0 MB
for your last suggestion im going to try it and see if I can access my files
Thank you for your help! Let me know how else I can continue the diagnostic and I will keep my word
vap3 said:
for question #1 yes I do see my files. But certain folders like DCIM (pictures) or other apps such as whatapp is not showing.
when i try to mount in TWRP only firmware and system is checkable.... data/cache/usb-otg is not selectable (meaning check marks won't show up if I try to click it)
when I hit "select storage" i see the select storage options and both options (internal storage and usb-otg) says 0 MB
for your last suggestion im going to try it and see if I can access my files
Thank you for your help! Let me know how else I can continue the diagnostic and I will keep my word
Click to expand...
Click to collapse
Yeah I would try pulling the whole sdcard to your computer via adb and see if it pulls the files you want.
If that doesn't work all I got is you can dirty flash that same ROM you had installed before. When you dirty flash you don't wipe data or anything since its the same ROM you had before. Its the same thing you do when you update to a new version of that developers ROM and you don't loose your data.
Just curious did you change over to f2fs the developer recommended it for installing his ROM, not sure if that's what caused the initial problem if you did not change to f2fs.
Durso81 said:
Yeah I would try pulling the whole sdcard to your computer via adb and see if it pulls the files you want.
If that doesn't work all I got is you can dirty flash that same ROM you had installed before. When you dirty flash you don't wipe data or anything since its the same ROM you had before. Its the same thing you do when you update to a new version of that developers ROM and you don't loose your data.
Just curious did you change over to f2fs the developer recommended it for installing his ROM, not sure if that's what caused the initial problem if you did not change to f2fs.
Click to expand...
Click to collapse
interesting i will try the adb method and see if that i can pull the files despite not seeing everything in the file manager
unfortunately i have never changed to the f2fs file system due to me being a noob at the time. But i never had a problem with his early builds and dirty flashing all the way to September. Ironically every time I dirty flashed i did a nandroid backup on the phone. lol... i can't even access that file right now because i don't see it in the file manager as the data cannot be accessed at the moment.
vap3 said:
interesting i will try the adb method and see if that i can pull the files despite not seeing everything in the file manager
unfortunately i have never changed to the f2fs file system due to me being a noob at the time. But i never had a problem with his early builds and dirty flashing all the way to September. Ironically every time I dirty flashed i did a nandroid backup on the phone. lol... i can't even access that file right now because i don't see it in the file manager as the data cannot be accessed at the moment.
Click to expand...
Click to collapse
Just to interject, not being on f2fs is wise, I don't believe it to be as stable, and is not very useful..
I'd like to also recommend using TWRP 2.8.6 (there's a link in my signature).. I've read more recovery related issues since it was updated..
Good luck
I know you said you are new if your having issues figuring out how to pull files via adb there is a all in one toolkit that has a pull/push file fearure. http://www.wugfresh.com/brt/
It will be under advance utilities.
should i downgrade to twrp 2.8.6 before proceeding to try the adb dirty flash upgrade?
Durso81 you are so awesome! Gonna try this tonight (PRAYING) and Setting.Out thank you!
damn I got this error message triying to flash twrp 2.8.6.0
C:\android-sdk-windows>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10882 KB)...
OKAY [ 0.351s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.399s
uh oh... is the thing totally bricked? i also tried to flash the oct 15th build of jpgapps and it didn't work got this screenshot for you! That Bacon tool is cool though!
vap3 said:
damn I got this error message triying to flash twrp 2.8.6.0
C:\android-sdk-windows>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10882 KB)...
OKAY [ 0.351s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.399s
uh oh... is the thing totally bricked? i also tried to flash the oct 15th build of jpgapps and it didn't work got this screenshot for you! That Bacon tool is cool though!
Click to expand...
Click to collapse
Looks like your firmware isn't correct, finish switching to 2.8.6 before fixing this.. As per recovery, flash the image in TWRP.. Select 'instal' and there's an option for 'IMG' select it and find the recovery image and then select the option for recovery, swipe to flash and upon success reboot the recovery.. Now update the firmware as per the ROM's OP and the ROM will flash..
Setting.Out said:
Looks like your firmware isn't correct, finish switching to 2.8.6 before fixing this.. As per recovery, flash the image in TWRP.. Select 'instal' and there's an option for 'IMG' select it and find the recovery image and then select the option for recovery, swipe to flash and upon success reboot the recovery.. Now update the firmware as per the ROM's OP and the ROM will flash..
Click to expand...
Click to collapse
I tried that and when i rebooted the TWRP is still 3.02.0 what's the next step?
vap3 said:
I tried that and when i rebooted the TWRP is still 3.02.0 what's the next step?
Click to expand...
Click to collapse
You still had 3.02 after flashing the 2.8.6 recovery.img and rebooting twrp? And fastboot flashing recovery failed?..
Try flashing this normally..
https://www.androidfilehost.com/?fid=95916177934548751
Setting.Out said:
You still had 3.02 after flashing the 2.8.6 recovery.img and rebooting twrp? And fastboot flashing recovery failed?..
Try flashing this normally..
https://www.androidfilehost.com/?fid=95916177934548751
Click to expand...
Click to collapse
exactly! Its like nothing wants to work I got the same error message trying to flash that url you gave me too
C:\android-sdk-windows>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10882 KB)...
OKAY [ 0.347s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.406s
man now I know its one of those things I can't recover no matter how much money I throw at it T_T not even about the value of the phone but the data I appreicate your help though so if you have any other ideas please let me know i'm all ears
vap3 said:
exactly! Its like nothing wants to work I got the same error message trying to flash that url you gave me too
C:\android-sdk-windows>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10882 KB)...
OKAY [ 0.347s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.406s
man now I know its one of those things I can't recover no matter how much money I throw at it T_T not even about the value of the phone but the data I appreicate your help though so if you have any other ideas please let me know i'm all ears
Click to expand...
Click to collapse
Don't fastboot flash a .zip... Flash it through recovery using twrp..
Fastboot is for recovery.IMG
Let's see if that helps..
Setting.Out said:
Don't fastboot flash a .zip... Flash it through recovery using twrp..
Fastboot is for recovery.IMG
Let's see if that helps..
Click to expand...
Click to collapse
what i would do is unzip the twrp and the default file name is recovery.img so I would unzip it to my SDK android folder that contains the adb.exe
so I tried flashing in TWRP again but this time selecting the zip file instead of the img file and I got the same error and it after rebooting it still boots into TWRP 3.0.2.0
vap3 said:
what i would do is unzip the twrp and the default file name is recovery.img so I would unzip it to my SDK android folder that contains the adb.exe
so I tried flashing in TWRP again but this time selecting the zip file instead of the img file and I got the same error and it after rebooting it still boots into TWRP 3.0.2.0
Click to expand...
Click to collapse
Are you encrypted?
Setting.Out said:
Are you encrypted?
Click to expand...
Click to collapse
like through TWRP or through android? I don't remember... if I am how do I unencrypt? But I'm wondering how I got here in the first place.
vap3 said:
like through TWRP or through android? I don't remember... if I am how do I unencrypt? But I'm wondering how I got here in the first place.
Click to expand...
Click to collapse
You'd know, it requires many steps to encrypt, so I'll guess no.. Have you ever been able to flash anything through that recovery?
I'd copy your SD to your computer and return to stock, then try again with customs from there...
Setting.Out said:
You'd know, it requires many steps to encrypt, so I'll guess no.. Have you ever been able to flash anything through that recovery?
I'd copy your SD to your computer and return to stock, then try again with customs from there...
Click to expand...
Click to collapse
nope when I try to flash the oct 15th of the rom I get simliar error messages like trying to flash the twrp 2.8.6
im wondering how am I suppose to recover certain files like my bitcoin app, google authenticator passcodes, smart audio recorder files, photos and videos as when i peek into the file structure nowhere is to be found!
can the bacon tool do all the backup for me? what's the easiest way to do this? damn im super sleepy so i'll try again tomorrow thanks for the help
Lenovo Tab 3 8/TB3-850F -
Android 6.0 Stock Firmware Images
DISCLAIMER: As always, flashing your device - with either stock or custom firmware - involves an inherent risk of bricking or otherwise rendering your device inoperable. I am not responsible for any good or bad resulting from your use of these firmware images or this thread.
DEVICE SPECIFICATIONS:
Model: Lenovo Tab 3 8"(TB3-850F)
Android Version: 6.0 Marshmallow
Kernel Version: 3.18.19
Board Platform: MediaTek MT6735m (1.0 GHz)
Build No: TB3-850F_S100031_171010_ROW
Software Version: TB3-850F_160412
SDK Version: 23
Build ID: MRA58K
Android Security Patch Level: 9/05/2017
Build Date: 10/10/2017
NOTE:
First & foremost, these partition images will not restore your device completely back to factory/stock condition. They will restore your Android OS, boot logo, boot image & recovery to stock condition. Other vital partitions of your device, such as /lk (the primary bootloader) are not restored by flashing these images. To revert to an unmodified factory state, you will need to visit @r&xp's thread mentioned below and flash your device with stock firmware using the SP Flash Tool, which will also re-lock your bootloader.
This firmware thread is not intended as a tutorial or guide for flashing or restoring your Lenovo Tab 3 back to stock condition. Rather, this is intended as a resource for stock images, device drivers, etc. However, some rudimentary instructions are provided, which will enable you to install these images and restore your device back to mostly stock condition. NOTE: IF YOUR DEVICE IS BRICKED (UNABLE TO BOOT INTO EITHER RECOVERY OR FASTBOOT MODE), THESE FIRMWARE IMAGES WILL BE OF NO BENEFIT. INSTEAD, PLEASE VISIT THE FOLLOWING THREAD BY XDA MEMBER @r&xp , WHICH WILL GIVE YOU THE NECESSARY FILES AND PRECISE INSTRUCTIONS FOR UNBRICKING & RESTORING YOUR DEVICE. https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
There are any number of available procedures to flash these stock partition images to your device. The simplest option is to use a custom recovery like TWRP to flash them. Store these images to your external micro SD (or internal storage if you do not intend to wipe internal storage or format /userdata). In TWRP's main menu, select "WIPE", "ADVANCED WIPE", and select Dalvik Cache, Cache, System, & Data. (For a clean install, it is recommended to format Data as well, by selecting "WIPE", then "Format Data.") Reboot Recovery (often necessary for proper mounting of the data partition). Now, select "INSTALL", then select "INSTALL IMAGE" in the bottom right of the menu, navigate to the storage location of the firmware images, and flash them in any order you choose. If you do not have TWRP installed on your device, XDA Senior Member @Hemphiz has a simple & comprehensive thread here: https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786/page1. In any event, whichever option you choose, please do your homework and research the threads here on XDA relating to your choice. These images may also be installed via fastboot mode. You will need to install Minimal ADB & Fastboot (v1.4 or later) on your PC, ensure the proper Lenovo device drivers & ADB drivers are installed on your PC, and connect your device to your PC via the stock (or quality equivalent) micro USB to USB data sync cable. Once in fastboot mode, open a command prompt in the adb/fastboot directory, and execute the following command lines:
fastboot devices (if you are properly synced, your device serial # will be shown)
fastboot oem fb_mode_set
fastboot flash logo logo.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img (this will overwrite any custom recovery)
fastboot flash system system.img (fastboot will automatically sparsechunk this image)
fastboot erase userdata
fastboot erase cache
fastboot oem fb_mode_clear
fastboot reboot
STOCK PARTITION IMAGES:
The link below provides the following stock firmware images:
/system.........................Size 3.0 GB
/boot..............................Size 16 MB
/recovery........................Size 16 MB
/logo...............................Size 8 MB
Also included in the link are some helpful files like Minimal ADB & Fastboot v1.4.3, the official Lenovo USB Drivers for the TB3-850F (v1.1.21), a general partition index of the tablet, the ADB driver installer for Windows, and the latest PC version of LenovoSuite Mobile Assistant v1.4.1.14199.
I have made a full & complete partition dump of this device, including sensitive firmware partitions such as /oemkeystore, /nvdata, /seccfg, /lk, etc. In the event any members have corrupted these partitions, just request and I will upload these as well. (/nvdata contains device identifiers such as MAC Address, ESN, etc. The device from which these images were taken has since been hardware damaged & salvaged for parts. Therefore, I have no issue with sharing these images. However, as a disclaimer, you are fully responsible for the manner in which you use device ID partitions. Modifying a device's identifiers delves into matters of legality and ethical guidelines, all for which you are solely responsible.)
CREDITS:
Thanks to XDA Senior Member @Hemphiz for his hard work & development on this device, and his thread on TWRP & rooting. Also, huge thanks to @r&xp for his lifesaving tutorial on recovering this device from a soft or hard brick. His guide has revived many devices from the Android cemetery. You guys visiting either of these threads mentioned, be sure and hit the "THANKS" button for their hard work.
DOWNLOAD LINK:
TB3-850F_S100031_171010_ROW
Stock Firmware Partition Images: https://drive.google.com/folderview?id=1vRLwQ2mCD3CwYQZKGHyykDvBd2yGHisT
Sent from my Lenovo Tab 3 8/TB3-850F using XDA Forums Pro Edition.
Hi:
I have a Tab3 8 TB3-850F which bough in China. It's a 2G+16G version.
I have successfully install TWRP and root.
I'm wondering can I install this ROM to my TAB3?
Thanks!
tsaibru said:
Hi:
I have a Tab3 8 TB3-850F which bough in China. It's a 2G+16G version.
I have successfully install TWRP and root.
I'm wondering can I install this ROM to my TAB3?
Thanks!
Click to expand...
Click to collapse
I don't see why you couldn't. But, to clarify some info, what is your Build No and Software Version? Look under Settings, About Device
Build number:
TB3-850F_S100026_161221_PRC
Software version:
TB3-850F-160425
Thank you very much!
tsaibru said:
Build number:
TB3-850F_S100026_161221_PRC
Software version:
TB3-850F-160425
Thank you very much!
Click to expand...
Click to collapse
Based on your Build & Software Version info, I can see no compatibility issues with this Stock ROM & your device. You seem to simply have a Chinese variant of the TB3-850F that is not available for retail in the United States.
In any event, use TWRP to backup all partitions of your tablet before proceeding henceforth with flashing this ROM. Also, do not flash the stock recovery from my link...keep your TWRP fully intact & accessible in case anything goes south as a result of the flash. Accordingly, you should be able to fully restore your partition backups via TWRP in the event my Stock ROM doesn't boot up. But, like I said, I can see no adverse consequences to flashing it. Should you decide to give it a go, please update us on this thread as to the results.
Thank you...
The reason why I would like to flash this ROM is to get full Google service which Chinese Rom does not offer.
Even though I have root and install Google service on it. Some of apps I downloaded from play just won't install.
So I dowbloaded this ROM and flash system-002.img, it works.
Now I have all Google service I needed, and all apps I download are able to install.
But after I reset the tab I've build number S100026_160923_ROW, software version TB3-850F_160412.
It will try to download the update to 161209 but after reboot it just go in TWRP not doing anything.
I'm very satisfied with this, and I will keep searching and wait for a way for me to update to S100030_161209_ROW.
I do really appreciate your work to help me solve my problem and save this tab from goes to trash can.
tsaibru said:
The reason why I would like to flash this ROM is to get full Google service which Chinese Rom does not offer.
Even though I have root and install Google service on it. Some of apps I downloaded from play just won't install.
So I dowbloaded this ROM and flash system-002.img, it works.
Now I have all Google service I needed, and all apps I download are able to install.
But after I reset the tab I've build number S100026_160923_ROW, software version TB3-850F_160412.
It will try to download the update to 161209 but after reboot it just go in TWRP not doing anything.
I'm very satisfied with this, and I will keep searching and wait for a way for me to update to S100030_161209_ROW.
I do really appreciate your work to help me solve my problem and save this tab from goes to trash can.
Click to expand...
Click to collapse
Trying a system update will not work with a custom recovery installed. In spft you can select only to flash the stock recovery then you should be able to update it, when you have done the system update just flash TWRP again.
@MotoJunkie01 I did send you a PM the other day, maybe like for you it did not send or was it my noobishness? :laugh:
stonedpsycho said:
Trying a system update will not work with a custom recovery installed. In spft you can select only to flash the stock recovery then you should be able to update it, when you have done the system update just flash TWRP again.
@MotoJunkie01 I did send you a PM the other day, maybe like for you it did not send or was it my noobishness? :laugh:
Click to expand...
Click to collapse
Try sending another PM please. I could have deleted your PM by mistake.
boot. logo and recovery.img worked but system.img did not .the system.img downloads with the explorer or e symbol not a disc like the others do.don't know if that has anything to do with it not working? need the system.img to work pls.
chico2016 said:
boot. logo and recovery.img worked but system.img did not .the system.img downloads with the explorer or e symbol not a disc like the others do.don't know if that has anything to do with it not working? need the system.img to work pls.
Click to expand...
Click to collapse
Not sure. The /system image is an unmodified dump taken from a brand new TB3-850F. It works for me and other members. Be sure you are running version 1.4 or later on minimal adb & fastboot. That could be your issue.
MotoJunkie01 said:
Not sure. The /system image is an unmodified dump taken from a brand new TB3-850F. It works for me and other members. Be sure you are running version 1.4 or later on minimal adb & fastboot. That could be your issue.
Click to expand...
Click to collapse
ok will try again thank you.
---------- Post added at 01:19 AM ---------- Previous post was at 01:15 AM ----------
is it possible to use the platform tool ,like it says for the twrp for the system image?
chico2016 said:
ok will try again thank you.
---------- Post added at 01:19 AM ---------- Previous post was at 01:15 AM ----------
is it possible to use the platform tool ,like it says for the twrp for the system image?
Click to expand...
Click to collapse
Sure. Minimal ADB & Fastboot is merely a bare essentials utility in contrast to the Android SDK & other platform tools packages. You may also flash the /system image using TWRP.
MotoJunkie01 said:
Sure. Minimal ADB & Fastboot is merely a bare essentials utility in contrast to the Android SDK & other platform tools packages. You may also flash the /system image using TWRP.
Click to expand...
Click to collapse
target reported max download size of 134217728 bytes.
invalid sparse file format at header magi ? Not enough room.
need help with tb3-850f flashing system.img.
Thanks!!! Saved my soft bricked Tab3 8 850F
chico2016 said:
target reported max download size of 134217728 bytes.
invalid sparse file format at header magi ? Not enough room.
need help with tb3-850f flashing system.img.
Click to expand...
Click to collapse
If you use minimal adb & fastboot v1.4, the /system image will automatically be converted into a series of smaller sparsechunk image files, which will be flashed to your device one at a time until complete.
wow dont know what i am doing wrong.
invalid sparse file format at header Magi
erasing 'system'...
okay[0.032s]
sending sparse 'system' 1/21...(129476kb) okay[14.824s] writing 'system'1/21...
failed(remote: uknown chunck type)
finished. total time: 14.904s
need some help adb fastboot file says 'system.img is to long?
wow dont know what i am doing wrong.
invalid sparse file format at header Magi
erasing 'system'...
okay[0.032s]
sending sparse 'system' 1/21...
failed(remote: uknown chunck type)
finished. total time: 14.904s
need some help adb fastboot file says 'system.img is to long?
chico2016 said:
wow dont know what i am doing wrong.
invalid sparse file format at header Magi
erasing 'system'...
okay[0.032s]
sending sparse 'system' 1/21...
failed(remote: uknown chunck type)
finished. total time: 14.904s
need some help adb fastboot file says 'system.img is to long?
Click to expand...
Click to collapse
What version of Minimal ADB & Fastboot are you using?
i am using the 1.4 version adb fastboot from the same link i got the images on this very helpful post
boot img -logo.img-recovery.img say flash on ,and the tablet marks ok that they have flashed---but no luck with the system.img even though i have re downloaded twice same thing .do you have a link that would go through a step by step instalation process you could help me with.
chico2016 said:
i am using the 1.4 version adb fastboot from the same link i got the images on this very helpful post
boot img -logo.img-recovery.img say flash on ,and the tablet marks ok that they have flashed---but no luck with the system.img even though i have re downloaded twice same thing .do you have a link that would go through a step by step instalation process you could help me with.
Click to expand...
Click to collapse
I don't have a tutorial posted per se on installation. Here's a thought. Boot your tablet into TWRP (fastboot boot TWRP.img) and flash my system.img via TWRP. In TWRP main menu select INSTALL, then select the .img file option in bottom right hand corner of screen. (You will need to put the system.img on an ext micro SD)
Just wanted to write a report on the successful flashing Oukitel WP5 (version 4/32 Gb) with Mediatek MT6761 + PowerVR Rogue GE8300
I have used instructions in this thread with some modification.
disclaimer (short version): Do not do any of the following unless you are prepared to lose your warranty or brick your phone. Everything that you do with your phone is at your own risk, and no one but you is responsible for it.
For flashing i used adb and fastboot. In Debian 10 it's easy to install:
sudo apt install adb fastboot
How to do that in other systems you my read on this forum or do some googling.
System image from phh's you can download here. I have used system-quack-arm64-ab-floss.img.xz image.
The steps of the procedure are almost the same as for WP6, except for one important point:
1. Battery must be charged. Unlock the bootloader as usual (developer options - enable USB debugging and OEM unlock). Connect phone to computer with USB cable
2. Type:
adb devices
ADB should now detect your device, and a request for access will pop up on your phone asking to allow permission. Allow it.
Next type:
adb reboot bootloader
The phone will reboot into fastboot mode, wait a few seconds until "fastboot mode" is shown on the bottom left of your phone's screen.
Next type:
fastboot devices
Fastboot should detect your device
Next type:
fastboot flashing unlock
Fastboot and your phone will ask you to confirm that you want to unlock your bootloader, confirm it using the volume buttons on your phone according to the instructions on your phones screen.
After the bootloader has unlocked successfully you need to format your device, type:
fastboot erase userdata
You'll receive a confirmation that data has been formatted.
Type:
fastboot erase system
You'll receive a confirmation that system has been formatted.
3. Next, you need to disable protection from booting non-factory firmware or whatever it is called - let the experts correct me. For that i flashed vbmeta partition with blank one (see attached file):
fastboot flash vbmeta vbmeta-blank.img
This is important step! If you do not do that - you will get phone infinity cycle trying to boot and rebooting
4. Final step, flashing the system image, that you have previously download and unpack:
fastboot flash system system-quack-arm64-ab-floss.img
and reboot after process is finished:
fastboot reboot
P.S. After booting everything works like a Swiss watch
I note that there is an AOSP 11 available since a few days. Any reason to avoid trying that on my WP5?
https://github.com/phhusson/treble_experimentations/releases/download/v302/system-roar-arm64-ab-floss.img.xz
I have tried AOSP 11 on Oukitel WP6 - it was slow (compared to AOSP 10) and, as i remember, on AOSP 11 does not worked some applications, that i need.
But you can try it yourself. Since there was several new releases - may be something was improved.
I went ahead and installed phh's AOSP 11 ndklite vanilla on my WP5 and it all seems to work ok. I'm confused at having superuser preinstalled and unsure how that affects trying to install magisk. but anyhow, for anyone wondering, it worked.
I'm kind of confused by the AOSP install. I wanted to change /system/etc/hosts but it is RO and can't be mounted RW despite superuser root. Online searches suggest I need magisk with systemless enabled. however unlike playing with the stock rom, i can't figure out how to get my boot.img to patch. i thought i'd find it in the AOSP image file but I can't locate it. I thought I could perhaps us SP flashtool to readback, but I don't have the scatter file, unless it's the same as stock. Perhaps the boot.img is the same as stock. I'm out of my depth.
gringobenuk said:
I'm kind of confused by the AOSP install. I wanted to change /system/etc/hosts but it is RO and can't be mounted RW despite superuser root. Online searches suggest I need magisk with systemless enabled. however unlike playing with the stock rom, i can't figure out how to get my boot.img to patch. i thought i'd find it in the AOSP image file but I can't locate it. I thought I could perhaps us SP flashtool to readback, but I don't have the scatter file, unless it's the same as stock. Perhaps the boot.img is the same as stock. I'm out of my depth.
Click to expand...
Click to collapse
.
The thumb rule of applies to all operating systems. DON'T use them, if you can't control them. Meaning, if you have no root control and firewall for what goes in and out. How do you know what's going on in the background?. My point is... Using a system you are rooted in and can control, rather than using the latest Bling Bling systems, for the sake of trend ore popularity. You should use an older proven and rooted system....
I guess your curiosity and search for knowledge is the reason why you hang out here with us at XDA.
XDA is the epicenter of public knolitsh for smartphones and technology...
Millions of brains combined into a singularity for problem solving and solutions...
.
Took me the better part of a day to figure all this out, but I've finally got phh's A11 GSI running on my 3GB model. I've added a brief guide at https://github.com/adil192/OukitelWP5TrebleTips/ if anyone with this phone stumbles across this in the future.
Risbele94 said:
I've added a brief guide at https://github.com/adil192/OukitelWP5TrebleTips/ if anyone with this phone stumbles across this in the future.
Click to expand...
Click to collapse
I have WP5 3 GiB RAM model and flashing ARM32 images ( like mentioned on this site: system-roar-arm32_binder64-ab-vndklite-gapps.img ) results in a boot stuck.
ARM64 images (AOSP9, AOSP10, ...) works.
I can confirm - with Android 10 stock firmware from https://oukitel.com/pages/download-center phone constantly restarts itself. (I wrote about this to Oukitel but appears that they don't give a sh*t...)
Why sometimes *.img uploading speed is ~20 MB/s :
>fastboot flash system system-roar-arm32_binder64-ab-vndklite-gapps.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/15 (131060 KB) OKAY [ 6.349s]
Writing 'system' OKAY [ 1.811s]
Sending sparse 'system' 2/15 (131048 KB) OKAY [ 6.309s]
Writing 'system' OKAY [ 1.794s]
Sending sparse 'system' 3/15 (131068 KB) OKAY [ 6.299s]
Writing 'system' OKAY [ 1.788s]
[...]
and another time only ~3 MB/s ?
>fastboot flash system system-roar-arm64-ab-gapps.img
Sending sparse 'system' 1/18 (131068 KB) OKAY [ 42.548s]
Writing 'system' OKAY [ 1.799s]
Sending sparse 'system' 2/18 (131068 KB) OKAY [ 42.618s]
Writing 'system' OKAY [ 1.821s]
Sending sparse 'system' 3/18 (131068 KB) OKAY [ 42.647s]
Writing 'system' OKAY [ 1.824s]
[...]