Related
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
Hi!
I've been going mad searching the web for a solution.
As you understand I was stupid enough to wipe the whole internal storage when I was about to flash OxygenOS.
So now I have no OS to boot up to.
I've have tried basically everything I've found of the web.
- Sideloading a stock flash worked partially, it transferred but then nothing more.
- Fastboot using this cmd: fastboot -w update [insert zip here].zip worked partially but stuck on writing system.img
- Fastboot using all the individual commands is the same thing, gets stuck on writing system.img or erasing userdata.
It feels as whatever I do something small is messing it up.
Can you please help me troubleshoot this super annoying mess I've done.
I have gotten a basic knowledge of sideloading and fastboot commands from this though, but not enough I feel.
Thanks in advance!
mayby this help... google for "OPO_Toolbox" and click first link
choose 16 or 64 gb !
reinstall cm 11
hgeert said:
mayby this help... google for "OPO_Toolbox" and click first link
choose 16 or 64 gb !
reinstall cm 11
Click to expand...
Click to collapse
I have used the toolkit (the one by inthiaano) and when installing the cm11 it gets stuck on erasing userdata..
target reported max download size of 536870912 bytes
sending 'boot' (5580 KB)...
OKAY [ 0.177s]
writing 'boot'...
OKAY [ 0.109s]
finished. total time: 0.286s
target reported max download size of 536870912 bytes
erasing 'userdata'...
Ok,i found a Way back to Stock for Mediapad X2 703L
i test this and works fine.
If your Mediapad X2 Rooted and have install Custom Recovery and will go back to Stock.(Also your Pad is Rooted,Unlocked Bootloader and Twrp installed)
Backup your Data Before Flash this Firmeware!!!
Download the Huawei Extractor App unpack and install it (Download from Attachment).
Download the Huawei Firmware from here and unpack it.
Installing Mediapad X2 Driver (Hi Suite) and must have fastboot ADB installed.
Copy the Update.app in dload Folder in Internal or external Storage.(For later)
Open the Huawei Extractor and extract Recovery and or System and copy Recovery and or System in your ABB Folder.
Reboot your Mediapad in Fastboot/Bootloader Power Off - Connect to Pc and Press and hold Power and Volume Down to boot in Fastboot Mode or CMD Command adb reboot bootloader.(USB Debugging must be enabled)
Open CMD and Navigate to your ADB Folder (cd C:\ADB)
For Recovery to Update for Local Update
fastboot flash recovery RECOVERY.img
For System (If you have delete Apps from System and not wipe your Data))
fastboot flash System SYSTEM.img
wait to finish this Procedur.
The X2 Reboot and go in Setting to Update Program-Menu-Local Update and Flash your Original Firmware for GEM 703L
Wait to Reboot and you have Original Stockrom/Firmware without Root and Twrp.This wipe your Data,please Backup your Data before you make this Procedur!
I am not responsible for damage to the unit or other!!!
Sorry for my bad English.
thank you. now my phone gets bootloop.I will try this method !
I can't flash system.img.Error messaging : can't load system.img
Bootloader unlocked
I have 702L, will the 703L firmware work for my Mediapad? I couldn't find the specific firmware for it on Huawei's web-site.
It worked! Oh my god, thank you! I was close to tears, being up all night trying to fix my failed root attempt. Time to start again from scratch hahahaha!
what if in fastboot when flashing it says : " write : command not allowed " ...
How do I get USB debugging if I have no ROM installed and TWRP won't flash D: (only thing I can get is erecovery)
EDIT: Well TWRP wouldn't flash because I had to reunlock my bootloader, yes....reunlock.
letschky said:
For System (If you have delete Apps from System and not wipe your Data))
fastboot flash System SYSTEM.img
Click to expand...
Click to collapse
Code:
platform-tools>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (32354 KB)...
OKAY [ 1.010s]
writing 'recovery'...
OKAY [ 1.050s]
finished. total time: 2.060s
platform-tools>fastboot flash System SYSTEM.img
[COLOR="Red"]error: cannot load 'SYSTEM.img'[/COLOR]
xdxdxd33 said:
Code:
platform-tools>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (32354 KB)...
OKAY [ 1.010s]
writing 'recovery'...
OKAY [ 1.050s]
finished. total time: 2.060s
platform-tools>fastboot flash System SYSTEM.img
[COLOR="Red"]error: cannot load 'SYSTEM.img'[/COLOR]
Click to expand...
Click to collapse
Extract the SYSTEM.img again,i had the same Problem,then it worked
letschky said:
Extract the SYSTEM.img again,i had the same Problem,then it worked
Click to expand...
Click to collapse
Nope still does not work, I tried with GEM-703L_EMUI3.0.5_Android5.0_V100R001C233B015 and GEM-703L_EMUI3.1_Android5.1_V100R001C233B112
What is the sha1 or md5 hash for your SYSTEM.img?
My fastboot / platform-tools were outdated, so I downloaded newer ones that fixed the issue.
I'm pulling out my hair trying to get this to work.
When I try to run the local update using the UPDATE.APP file, I get an incompatible error.... I definitely downloaded the 703L stock ROM FOR MY 703L...... so wtf is the problem?
I've followed your instructions and the local update always fails with this error message i.imgur.com/Gb7P9Ks.jpg
So what could I be doing wrong...?
I've tried all these ROMs
Code:
GEM-703L_EMUI3.0.5_Android5.0_V100R001C233B015
GEM-703L_EMUI3.1_Android5.1_V100R001C233B112
GEM-703L_EMUI3.1_Android5.1_V100
GEM-703LT_EMUI3.1_Android5.1_V10
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)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Notice1:
U Pro has A/B partitions. to prevent issues its good to flash it in both slot, because i/we can not know on which partition you are
Notice 2:
This version only working on Eragon roms
Maybe soon I'll manage it to work on stock rom
Notice 3: Sdcard now working
DOWNLOAD
TWRP for 20180227 Base via Qfil Flashtools:
Go here : https://drive.google.com/file/d/1JZ59mO07Zc1a9kdA6j7LJvrgc9g2kf5d/view?usp=sharing
TWRP for 20180511 Base and newer:
Go here: https://drive.google.com/file/d/1RrWuncXsH8GtCTbaEgGpDffRUDK9fMVv/view?usp=sharing
INSTALLATION
if you use the old 20180227 Base you have to use Qfil Flashtools , because fastboot commands dont work in that Build.
we have a good guide of how to use FLashtools already
look here: https://forum.xda-developers.com/android/development/guide-elephone-pro-user-manual-t3775895
if you are on 20180511 Base and newer you can use fastboot commands
required : ADB and fastboot
enable usb debugging in developer settings.
do this:
Code:
adb shell
Code:
reboot bootloader
now we flash it in slot a
Code:
fastboot flash boot_a twrp.img
after that we flash it also in slot b
Code:
fastboot flash boot_b twrp.img
Special thanks to
teamwin for this awesome custom recovery
And @skeleton1911 for his help
Reserved 1
I loaded up all my usual apps and settings and was going to do twrp backup and strange thing happened: the recovery doesn't see my external SD. I can see sd card's files from the phone but it's invisible in twrp. Funny, because someone couldn't flash ROM from sd yesterday and I did, I still have the ROM files there on SD. I tried to pick the sd storage for the backup and that's how I found out it's missing. The trwp was flashed per instruction: fastboot, 'a' & 'b' then I did a total wipe in twrp and flashed the ROM twice - that was it. Probably some conflict between a an b again? It can wait, am not in the hurry, this Rom otherwise looks really good, it boots faster then the stock, nice.
mzsquared said:
I loaded up all my usual apps and settings and was going to do twrp backup and strange thing happened: the recovery doesn't see my external SD. I can see sd card's files from the phone but it's invisible in twrp. Funny, because someone couldn't flash ROM from sd yesterday and I did, I still have the ROM files there on SD. I tried to pick the sd storage for the backup and that's how I found out it's missing. The trwp was flashed per instruction: fastboot, 'a' & 'b' then I did a total wipe in twrp and flashed the ROM twice - that was it. Probably some conflict between a an b again? It can wait, am not in the hurry, this Rom otherwise looks really good, it boots faster then the stock, nice.
Click to expand...
Click to collapse
It's fixed now i uploaded the new twrp now everything working very well
Maherabed1986 said:
It's fixed now i uploaded the new twrp now everything working very well
Click to expand...
Click to collapse
sorry for bringing bad news, I flashed that new ver. it shows SDcard(it wasn't there before) and that's it, it won't go 'up level', also in File Manager or Backup storage choices it shows externalSD with 0MB space.
Hey Guys, we have two parallel Upro Universes here, two seperate threads on "Unofficial twrp for Elephone u pro v3.2.1.0", would that be _a and _b?
mzsquared said:
sorry for bringing bad news, I flashed that new ver. it shows SDcard(it wasn't there before) and that's it, it won't go 'up level', also in File Manager or Backup storage choices it shows externalSD with 0MB space.
Hey Guys, we have two parallel Upro Universes here, two seperate threads on "Unofficial twrp for Elephone u pro v3.2.1.0", would that be _a and _b?
Click to expand...
Click to collapse
Can you join us on Telegram group plz
https://t.me/joinchat/GxIBOhKXi5I6bsNWOm6LFg
Maherabed1986 said:
Can you join us on Telegram group plz
https://t.me/joinchat/GxIBOhKXi5I6bsNWOm6LFg
Click to expand...
Click to collapse
opened my acct in telegram, so, what next?
mzsquared said:
opened my acct in telegram, so, what next?
Click to expand...
Click to collapse
Tab the link again then join the group
mzsquared said:
sorry for bringing bad news, I flashed that new ver. it shows SDcard(it wasn't there before) and that's it, it won't go 'up level', also in File Manager or Backup storage choices it shows externalSD with 0MB space
Click to expand...
Click to collapse
same problem here
jimibxl said:
same problem here
Click to expand...
Click to collapse
reinstalled, reflashed, flashed and reinstalled and still no show for extSD in TWRP. But am all set for now, placed Eragon v.5 and Magisk Mgr on microSD/USB C OTG dongle and installed the ROM(zip) + Magisk(zip) from there via TWRP. Everything's good 'xept that 0 extSD. I was also able to do TWRP nandroid sys backup which went on that OTG dongle, some 3.8GB, that'll save me some time in the future I'd think :laugh: So, with the Springtime weather outside am gonna leave my computer stuff now and go out to ejnoy some of that Spring! See you later!
Hi Skeleton my problem is:
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
and
PS C:\adb> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
Can you help me??
Thanks
Enrique602012 said:
Hi Skeleton my problem is:
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
and
PS C:\adb> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
Can you help me??
Thanks
Click to expand...
Click to collapse
You are on build 20180227 so the flash commands not available you must use Qfil flashing tools to flash twrp
mzsquared said:
reinstalled, reflashed, flashed and reinstalled and still no show for extSD in TWRP. But am all set for now, placed Eragon v.5 and Magisk Mgr on microSD/USB C OTG dongle and installed the ROM(zip) + Magisk(zip) from there via TWRP. Everything's good 'xept that 0 extSD. I was also able to do TWRP nandroid sys backup which went on that OTG dongle, some 3.8GB, that'll save me some time in the future I'd think :laugh: So, with the Springtime weather outside am gonna leave my computer stuff now and go out to ejnoy some of that Spring! See you later!
Click to expand...
Click to collapse
On last build of twrp everything is working perfectly
Thanks but I run now Eragon V6. Each time start the Rom appear yellow !.
Enrique602012 said:
Thanks but I run now Eragon V6. Each time start the Rom appear yellow !.
Click to expand...
Click to collapse
It's because the unlocked bootloader it's normal
The problem is when I try to install TWRP now run V6:
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567s
and
PS C:\adb> fastboot flash boot_b twrp.img
target reported max download size of 536870912 bytes
sending 'boot_b' (55180 KB)...
OKAY [ 1.564s]
writing 'boot_b'...
FAILED (remote: unknown command)
finished. total time: 1.567
Thanks again
Hi Skeleton now I try to install TWRP and first no problem with boot_a and boot_b.
I run V6.
When restart the phone initial appear ! yellow........next appear TWRP and nothing hapen. Each time restart phone appear the same thing. Many times.
I try to install TWRP with QPST and nothing happend
I reinstall V5 by zip file and reinstall V6 by QPST and all ok.
What can I do to install TWRP without problem.
Thanks so much
Maherabed1986 said:
fix this command from
Code:
fastboot falsh boot_b twrp.img
to
Code:
fastboot flash boot_b twrp.img
Click to expand...
Click to collapse
And thanks dude. :good:
powergo said:
And thanks dude. :good:
Click to expand...
Click to collapse
Thanks dude but there's no difference between the two codes ?
Maherabed1986 said:
Thanks dude but there's no difference between the two codes
Click to expand...
Click to collapse
i mean falsh to flash
:good: