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
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
Here is twrp for HUAWEI MATE 10 LITE.
Who want?
Comment Here.
i need Android 8 for mate 10 lite !
yes i need thanks
100% tested every thing work just mtp does not work..
Still working on it.
Link is Here
Extract to Pc in Adb Fastboot Folder and
Install through fastboot Command
fastbbot flash recovery_ramdisk twrp8.img
https://drive.google.com/file/d/1_dfpSOCD23Oz_LexYMn1JNRVfrlvKU-x/view?usp=drivesdk
Azan Mughal said:
Link is Here
Extract to Pc in Adb Fastboot Folder and
Install through fastboot Command
fastbbot flash recovery_ramdisk twrp8.img
https://drive.google.com/file/d/1_dfpSOCD23Oz_LexYMn1JNRVfrlvKU-x/view?usp=drivesdk
Click to expand...
Click to collapse
Officall oreo emui8 This is working twrp?
Taha0194 said:
Officall oreo emui8 This is working twrp?
Click to expand...
Click to collapse
Yep
I am using but not officiall.
Not compatible with Official Oreo
Taha0194 said:
Officall oreo emui8 This is working twrp?
Click to expand...
Click to collapse
I tried it on official Oreo.
It does not work.
Error received -
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (18199 KB)...
OKAY [ 0.479s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.493s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.028s
prasanthkb said:
I tried it on official Oreo.
It does not work.
Error received -
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (18199 KB)...
OKAY [ 0.479s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.493s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.028s
Click to expand...
Click to collapse
Bro. Offical oreo emui 8 working
adb command
fastboot flash recovery_ramdisk RECOVERY-V2.img
https://mega.nz/#!GxsAUQaS!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Taha0194 said:
Bro. Offical oreo emui 8 working
adb command
fastboot flash recovery_ramdisk RECOVERY-V2.img
https://mega.nz/#!GxsAUQaS!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Click to expand...
Click to collapse
Hi,
Many thanks. Flashed it finally
I want to take the TWRP backup of my Oreo.
Is it fine if i take the backup of all partitions and restore when needed ?
Some forums said not to restore OEMInfo and Product partitions with TWRP since its not 100% functional !!
I tried to backup to external SD and received error message saying "Cannot create folder, permission denied".
The same error when i used internal SD.
Can you please provide some information on this ?
prasanthkb said:
Hi,
Many thanks. Flashed it finally
I want to take the TWRP backup of my Oreo.
Is it fine if i take the backup of all partitions and restore when needed ?
Some forums said not to restore OEMInfo and Product partitions with TWRP since its not 100% functional !!
I tried to backup to external SD and received error message saying "Cannot create folder, permission denied".
The same error when i used internal SD.
Can you please provide some information on this ?
Click to expand...
Click to collapse
He's not backing up the data partition
It gives an error because of it
Remove sign from data when backing up
Also memory card format must be NTFS
*4GB does not support fat32
achievements
Azan Mughal said:
Link is Here
Extract to Pc in Adb Fastboot Folder and
Install through fastboot Command
fastbbot flash recovery_ramdisk twrp8.img
https://drive.google.com/file/d/1_dfpSOCD23Oz_LexYMn1JNRVfrlvKU-x/view?usp=drivesdk
Click to expand...
Click to collapse
so, this twrp can all save except data.
But we can restore data from emui 5.1 in emui 8.0?
merci
New Version is coming of twrp.
Azan Mughal said:
New Version is coming of twrp.
Click to expand...
Click to collapse
Great, and cant wait, when it is coming ?
Coming Soon
Coming Soon Every thing work and Now tell about it after view whats we need more.
You can unlock frp with this recovery and backup of frp
And backup every partition.
Chisetdel31260 said:
so, this twrp can all save except data.
But we can restore data from emui 5.1 in emui 8.0?
merci
Click to expand...
Click to collapse
I have not tried yet to retrieve data from emui 5 to emui 8 but you know about Android versions emui 5 is 6.0, 7.0 and emui 8 is 8.0 so its possible to retrieve but i think apps were creating problem so its your choice what to do.
Azan Mughal said:
I have not tried yet to retrieve data from emui 5 to emui 8 but you know about Android versions emui 5 is 6.0, 7.0 and emui 8 is 8.0 so its possible to retrieve but i think apps were creating problem so its your choice what to do.
Click to expand...
Click to collapse
OK, thanks
I will test it and tell you if all is well.
thank you for your work.
Azan Mughal said:
Coming Soon Every thing work and Now tell about it after view whats we need more.
You can unlock frp with this recovery and backup of frp
And backup every partition.
Click to expand...
Click to collapse
When you are releasing the new version? I am waiting to install because I tried the V2 but it is not working phone and FAILS to install.
LINK is Here.
Download the file extract the Folder and Go to fastboot mode and double click on TWRP.bat file and you have successfully installed TWRP.
https://drive.google.com/file/d/1DkU-2c4qCm_cGzr-aaDFoFEn0YlLl6fh/view?usp=drivesdk
If anyone like my work can donate. :good:
Azan Mughal said:
Download the file extract the Folder and Go to fastboot mode and double click on TWRP.bat file and you have successfully installed TWRP.
https://drive.google.com/file/d/1DkU-2c4qCm_cGzr-aaDFoFEn0YlLl6fh/view?usp=drivesdk
If anyone like my work can donate. :good:
Click to expand...
Click to collapse
The link is only accessible by your own account. Kindly share a proper link or provide access individually bcoz I already sent you a permission request.
Download Message:
Sorry, this file is infected with a virus
Only the owner is allowed to download infected files.
Somehow managed to download it...
Thank you
{
"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:
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]
[...]