Related
Let it now be hacked by the USA! France, those silly, um, baguette-eaters, via Bloggee, has several videos and some forums (in French) showing (but I don't think explaining) a hacked Archos 70B ereader/tablet. Can we get there??
I'd like to see a guide for hacking this 130 euro Android tablet!
About: I AM A N00B. I AM UNWORTHY! You are all wiser and cooler and better at all of this than me. I cannot write code, except some CSS and HTML, blah blah beginner stuff. I was the guy that jailbroke friends' iPhones when we studied in Italy. I like learning how to do things, but can't get extremely in depth, though I respect the process and the art behind it. Currently, my iPhone died so for a phone I have a quad-band Huawei J2SE POS I couldn't modify much, and a netbook with dual-boot Win7/Linux. Now in Germany, I bought a lovely Archos 70B ereader, and while it does the job of ereader, it's ugly and clunky and I want to hack it into running a cleaner, prettier Android ROM (with marketplace) since this seems to be a new device with a lot of potential.
Questions that haven't been answered by looking through these forums, and that I have encountered trying to customize my tablet:
Trying to get marketplace, I finally found an .apk to download, but trying to install, it said (paraphrase) "Only works with Froyo." SOO, Android's various versions (Eclair, Froyo, Gingerbread, Honeycomb, etc) while all the same OS in a way, prevent apps compatible with one version from being installed onto another version. It's like trying to install Win95 stuff on XP, or Win7 stuff on XP. Correct?
Issue: Finding Eclair-compatible .apk files. Where are they? Or, can Eclair apps be installed on other builds of Android, & vice versa?
Trying to upgrade the hardware to Froyo, well, I can't find anything. If a machine has the minimum hardware specs, why is installing any version an issue? Why can't I just search certain websites for an installer package and then use it, like a Windows or Linux .ISO, etc?
Issue: Upgrading from one Android OS/version to another (Eclair to Froyo, Froyo to Gingerbread, Eclair to Gingerbread)
Trying to upgrade firmware on device, I've found that Archos' website has no downloads for 70B ereader...HMMM. Issue, much? My firmware on the device is 1.0.1. There is no "Update Firmware" option or anything, and the firmware display is grayed out, so you can't touch it for further details or anything.
Issue: How do I update/backup/recover firmware for this device (or any, I guess)
While I have found guides to using Nandroid to backup a system in case of issues, they all seem to require that you have Marketplace so you can get Nandroid...and since this Archos version of Android doesn't have Marketplace...I've tried AppBrain Appmarket but the webpage isn't helpful: it says dl nandroid from marketplace or navigate there on my device's browser, but my device's browser won't download the APK when I visit the site. How does one get nandroid and a solid backup without marketplace? (.apk anywhere??)
Permanent rooting on this device; currently I use Z4Root and do temporary rooting, since 1) that's what guides said worked and 2) I don't know if permanently rooting my device will somehow destroy my data or be unrecoverable without further restore options.
Issue: Permanent root vs. temporary root (and why use one or the other)
Installing a custom ROM. In short, because I just am not clear, can someone clarify for me? Is this like basically wiping the HDD to all 0's, down to the first sector, and installing an entire new OS (called a "ROM") onto the HDD? I know a flash HDD is different than a circular spinning drive with Windows and an MBR, etc, but I'm curious if a custom ROM erases EVERYTHING, including a flash drive equivalent to all recovery/installer partitions. Or is there a tiny partition left and, if the factory reset button is pushed, that reinstalls/recovers everything? If that is not the case, then don't I need stock Archos ROM to reinstall/recover, if I wanted to go back to that?
Issue: Does a custom ROM completely wipe a HDD all to 0's, and if so, how does recovery work if using a device-specific build for Android (like Archos')
Maybe nobody cares about this tablet, and sure it's slow, but having a sub-$200 Android tablet would rock, and figuring out how to root and ROM and customize a device would be great.
Also, I want to say that most important is knowing if/how/why I can return to my stock Archos version of Android if dissatisfied; second most importantly is how to improve this (and any) device with a crappy tweaked Android OS into a pretty and fast (with marketplace) Android OS.
THANKS
Current for Archos 70B
Model Number A7EB
Firmware Version 1.0.1
Kernel Version 2.6.25 [email protected] #14
Build Number v.0.18.ECLAIR.eng.root.20110324.142810
Have successfully rooted (temporarily, until reboot) via Z4root.
Currently trying to use ArcTools...I had the site linked, and lots of other nifty links throughout, but xda handicaps us n00bs until 8 posts. So no links. Sorry.
Currently...
stuck at the same place as these people, pretty much.
http
forum.archosfans.com
viewtopic.php?f=82&t=51066
sorry for breaking it up. insert slashes to go to the link, or just visit the forum and search for Archos 70b.
currently looking into loading the (much nicer-looking) Voltaire firmware onto the 70b, if the parts are the same...hope i don't get a spanish installer program
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
stopdatrue said:
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
Click to expand...
Click to collapse
IMPORTANT QUESTION !!
Can i downgrade when i do this ^^ ?
i have found this:
xxx:xxx.archoslounge.net/forum/showthread.php?t=17642&p=275535&viewfull=1#post275535
^^
firmware_Archos70bereader.zip
xxxx:xxx.multiupload.com/U8MOUTWI5T
Does not work
It crashes at 99%. Luckily I had a recovery image.
I followed all the steps but can't get the image to install properly
We really need a rooted version of the BQ Voltaire software. Mine has now crashed twice since using it. If I could backup it wouldnt be nearly so bad.
The temporary root doesnt seem to work for me.
I have recently brought the Archos 70B ereader. I would like to know how to perform a factory restore. I have already tried to the reset button on the back, but that's just resulting in turning of the device. I also noticed the startup wizard on the setting menu, which after adjusting the startup setting is adding the factory apps back to the device. However, it does not seem to erase the whole internal memory like a real factory restore would do.
Does anyone knows how to perform a real hardreset on the reader?
Thanx.
I have upgraded my 70b succesfully with the BQ firmware.
It runs nicely tho it seems the battery is having a hard time.
So far i haven't managed to get it to last for more then a day.
Currently testing with juice defender to see if it helps.
I noticed some questions about reinstalling the default archos image (factory reset). The procedure to do this is the same as the installation of the BQ firmware. You just need to select the correct image.
So make sure you have both the archos and the bq image before attempting the upgrade. When you brick it, use the installation procedure to get it back to life.
However, when done properly, the BQ firmware should work.
Note: The drivers are not compatible with a 64bit OS. I flashed mine with an old XP-32 running laptop where WIN7-64 would fail.
I have a bq Voltaire running latest firmware (1.0.8) an i was able to temp root with Universal Androot.
will try to perm root and report back
...but is there any rom with software buttons (back, home, menu)?
because the bq does not have them...
cheers
EDIT: was unable to perm root with either Universal Androot or z4root...
I also have the software installed BQ. Works perfectly. I can not say that the batterylif is a problem. BQ software works much better tehn de the Archos Software.
The Archos 70 b eReaders and BQ Voltaire tablet run with the firmware Voltaire_20110699_v2.0.9.-2 _update.img very stable. For some days has been there one for this equipment android 2.2 version. There were some crahs on my device with that and moving the Apps on a SD card also doesn't work.
A rooted version with containedly in the Link2SD (you can move the Apps on SD card) the above-mentioned version in the link. E.g. an optimal mode of operation is possible with a 32 GB SD card class 10.
The Mini tool partition software can with standalone the SD card be formatted into 2 partitions. 1st partition FAT32 (e.g. 28 GB) 2nd partition ext3 (rest) both primary.
The approx. 2 GB suffice for many Apps.
For link see Archosfans forum. (i can't write link here)
Works like a charm with the Voltaire rom!
So THANX guys
how to remove key locks ?
stopdatrue said:
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
Click to expand...
Click to collapse
Hallo all and thank you for this great manual.
I allready prepared all: downloads, installing usb and uncompressing and so on, tryed many times, but my problem is your point 7): remove key-locks. , whichj I didn´read clearly before and thats why I want to install any new system on my/our Archos BQVoltaire: My daughter played with the login until it was locked and I do not have any Google-Password to unlock this. Nor dont know, how to hard reset or anything else. I am just a user, nothing else. Tried everything, but didn´t get it.
Do anybody hav an idea, how I can solve this, I would be really happy. Thx a lot in advance.
Giant THANKS, is easy as instruction say, and works a charm...now i have a tablet instead of a****!
stopdatrue said:
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
Click to expand...
Click to collapse
Point 7) of the instruction ????
Maybe for you woks like a charm. :good: Congratulations, fine for you.
But my problem has not been solved, since july last year!! I understand the entire instruction, already downloaded all indicated files, but as I already mentioned, my problem is point 7 of the instructions: "7. remove locks on keys and install the new device using uncompressed drivers"
.
The thread here is called something like "how to hakk keylocked installation...". Isn´t it?
But in Point 7) says: ".. remove locks on keys..." !!! What a fool is this, it is ridiculous. If I could remove this f... keylock manually, so why should I make a hard-reset.??? This is the REASON for what I´m going to do this !!!
My Archos ereader is not stolen nor part of any fraud. It just were handled foolish form my daughter, which is 10 y old.
Ok, if anybody have another idea, how to remove this keylock, you are welcome, thx
cvesch said:
I have upgraded my 70b succesfully with the BQ firmware.
It runs nicely tho it seems the battery is having a hard time.
So far i haven't managed to get it to last for more then a day.
Currently testing with juice defender to see if it helps.
I noticed some questions about reinstalling the default archos image (factory reset). The procedure to do this is the same as the installation of the BQ firmware. You just need to select the correct image.
So make sure you have both the archos and the bq image before attempting the upgrade. When you brick it, use the installation procedure to get it back to life.
However, when done properly, the BQ firmware should work.
Note: The drivers are not compatible with a 64bit OS. I flashed mine with an old XP-32 running laptop where WIN7-64 would fail.
Click to expand...
Click to collapse
For me it was the same. The drivers are working only on 32-bit win WinToUSB - cool tool, if you don't want to reinstall your win.
---------- Post added at 09:21 AM ---------- Previous post was at 09:07 AM ----------
I AM NOT RESPONSIBLE FOR ANY NEGATIVE IMPACTS OR CONSEQUENCES ON YOUR PHONE IF YOU SO CHOOSE TO USE THIS GUIDE.
I own the ZTE U950 and had realized that there is very little information (in English) on how to do anything beyond stock for this incredible phone. After hours of research and translation I was able to figure out everything needed to get this phone to a "better" state. Since then I - and other XDA members - have been trying to keep the ZTE U950 alive...
ZTE U950 SPECS
NVIDIA TEGRA 3 (1.3MHz)
1GB RAM
4.3" Display (480x800)
5MP Front Camera/0.3MP Back Camera
Android OS 4.0.4
DRIVERS
Here are the "Join Me" drivers so that your PC can recognize the ZTE U950.
KERNEL
Stock - This is the stock kernel's source file.
Custom - This is a custom kernel for stock ROMs that can be OC'd to 2.5GHz.
ROOT
1) Make sure you have USB Debugging Mode and Unknown Sources checked in your phone Settings.
2) Connect your phone to your PC.
3) Download and open Genotools.
4) The program will open, click the 4th tab (last tab on the right).
5) Ensure that your phone is plugged into your PC.
6) Click the 2nd ROOT button.
7) A popup window will appear, press OK.
8) Your phone will then have a popup window, click the "Restore My Data" option.
9) The phone will restart several times, leave it for a few minutes.
10) This is the odd part... The phone will likely not stop restarting, and when you try to click the unlock key for the screen, it will automatically restart. Disconnect the phone. It should continue to restart.
11) Force the phone off.
12) Restart the phone.
13) If you have SuperUser, you are then rooted. If not, repeat these steps.
ROOT - NEW VERSION #1 (UNTESTED!):
1) Download the file here.
2) The instructions read verbatim are, "1 If your phone is not acquired before the ROOT privileges, we choose 1 root [next line] 2 after enter". Which I assume means click root, then enter...
ROOT - NEW VERSION #2 (UNTESTED!):
1) Download the root kit here made for the ZTE U950 (it uses the Chinese recovery), and extract to your desktop.
2) On your phone, go into Settings and enable USB Debugging under Developer options.
3) Connect the phone to your PC (Windows OS should fail to recognize the device).
4) Run either DrvInst_x64.exe or DrvInst_x86.exe. If you are unsure what you have, run both, the wrong one will fail with an error message.
5) After installation, unplug and replug your phone.
6) Go into Device Manager. You should be able to see a "ZTE TD Handset ADB Interface" under the "Android Phone" section. If you don't, reinstall the drivers again.
7). To root, simply run the U950_Root.bat file, and follow the instructions.
RECOVERY (CWM/TWRP)
1) Download the Chinese CWM or English TWRP recovery.img and place it into the root folder of your external SD card.
2) Download a terminal emulator. (If you are unable to download one, use the APP TRICKS described near the bottom to install a terminal emulator onto your phone.)
3) Open the terminal emulator.
4) Type in "su" then hit the return button.
5) Now type in the following:
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
(and press the return button)
6) There should be a few lines beginning with something like 14052 or 14272, if not, then the above input was not typed correctly. If so, the recovery should now be installed.
GET INTO RECOVERY
1) Turn the phone off.
2) Hold the Power button + Volume Down button. When the ZTE logo comes up, count two seconds and then let go of the buttons.
3) The phone will enter into recovery. Use the Volume rockers for up and down and the power button to choose (if on CWM), or simply touch the buttons (if on TWRP).
4) I will describe the standard processes here if using CWM - the menus are top-to-bottom on the phone, which are written left-to-right here:
The Main Menu:
[*] Reboot system now
[*] Select zip to flash/install
[*] Wipe data
[*] Wipe cache
[*] Backup and restore
[*] Flash memory/Format
[*] Advanced setting
[*] Turn off phone
The Zip Menu:
[*] Install from zip
[*] Install from internal
Wipe Date:
[*] Confirm wipe data
[*] Do not wipe data
Wipe Cache:
[*] Confirm wipe cache
[*] Do not wipe cache
Backup and Restore:
[*] Backup
[*] Restore
ROMS (ALWAYS MAKE A BACKUP BEFORE FLASHING ANY ROMS TO THIS PHONE!)
Factory ROMs (in order of release)
U950V1.0.0B02
U950V1.0.0B14
U950V1.0.0B18
U950V1.0.0B22
U950V1.0.0B04
U950V1.0.0B05
Custom ROMs (in no particular order)
6240-jingjian
MIUI3.3.7
CustomRom-B14
DeodexedMIUI3.3.7
EN&CN-MIUI3.3.7-msdfyc4zwg
MIUI3.2.8-ysdfyc4zwg
Signed-121223-MZECN-CookedROM
SignedROM
V2.0.0-Hiapk-XC-iSignFile
12-21ROM
4.2CameraROM
RandROM
MIUI1220
V2-MaunJ
CM10/.1 - HeatSka Edition
This should be listed under ROMS, but I felt that it needed its own section. Ska and I worked on this for quite some time getting all the kinks worked out. We did not create the original version of this unofficial Cyanogenmod port, but the original had many issues and was not maintained after its initial release. All the major problems have been worked out in our HeatSka edition.
The ROM was initially CM10 (4.1.2), but it has been mixed with files that list it as 4.2.2 (CM10.1) under the information section. In either case, it is Jelly Bean! Aside from the fixes we have implemented, there are also numerous tweaks and mods for UI speed, network speed, battery consumption, app installs, and much more. There is almost no theming, just enough to know that this is our enhanced (and better) variation.
The only known issue that may arise is CPU throttling. We have included an app called, "LGP880 Booster". This app will allow a CPU speed boost when turned on, with a temperature threshold to prevent overheating. If you wish to save battery, only enable this app when playing a game or using CPU-intensive apps.
DOWNLOAD: CM10.1/2 - HeatSka
FLASH A ROM
1) Download a ROM.
2) Place the ROM in the root of the phone's SD card.
3) Enter into recovery.
4) Wipe data.
5) Wipe cache.
NOTE: Wipe data and cache are the Factory Reset button in TWRP.
6) Follow the menus to get to the ROM in the SD card.
7) Click the power button to choose the ZIP if on CWM (or just push the designated button on TWRP).
8) The ROM is being flashed.
9) Follow the left arrow (the last selection) on the menus to get back to the main menu.
10) Choose the first option on the main menu to reboot on CWM (or click Reboot followed by System in TWRP).
NOTE I: The ROM will probably be in Chinese. Find the Settings icon and click it. Go down to the Language & Input setting and click it (there is a capital "A" next to it). Click the top setting and choose the desired language.
NOTE II: There may not be an English keyboard available, so download this 4.2 keyboard ZIP file and flash it in recovery.
INSTALL GOOGLE PLAY
1) Download and install a file explorer like ES Explorer (free) or Root Explorer (paid). (If the phone is unable to download a file explorer, use the APP TRICKS described near the bottom to install one onto the phone.)
2) Download and take the three files from the RAR file for Google Play and place them in a folder on the phone that can easily be reached with a file explorer.
3) Open up a file explorer.
4) Move the three files to the "/System/App" folder on the phone.
5) Give the three files each the same permissions (Read for all three groups, and Write for User).
6) Restart the phone and Google Play should now be installed.
Notes: a) There are cases where two Google Play store icons may appear. They should both work and not cause problems.
b) If the store does not show, redo the process above.
c) This trick does seem to work on other Android devices as I have successfully done this on a Galaxy Note N7000.
INSTALL FACTORY ROM
1) Download a Factory ROM from above and place the "update.zip" file in the root of your external SD card.
2) Go to Settings.
3) Go down to About Phone and click that.
4) Click on System Updates.
5) Remove the check mark.
6) Click OK.
7) The phone should restore to whichever factory update file was used.
APN FIX (MOBILE DATA FIX)
If your mobile data is not working then use this method to fix your APN:
1) Revert to stock ROM (or any custom ROM where mobile data does work).
2) Download and open a file explorer like Root Explorer or ES Explorer.
3) Go to /system/etc
4) Copy "apns-conf.xml".
5) Go to /sdcard/
6) Paste "apns-conf.xml".
7) Flash ROM.
8) Download a file explorer and open it.
9) Copy "apns-conf.xml".
10) Go to /system/etc
11) Paste "apns-conf.xml" (overwriting the existing file).
12) Reboot the phone.
13) Mobile data should now work.
GAME SUPPORT FOR ZTE U950 (WORKS ONLY FOR U950V1.0.0B02)
Note: I have not tested this. Apparently the first firmware version of this phone is not recognized by Google Play for certain Tegra games. If this occurs, try the following method.
1) Make a backup of the System folder. (It is easier to make a Backup of the entire ROM in recovery...)
2) Insert the build.prop file from this file.
3) Clear the Data for Google Play store (Settings > Apps > Google Play > Clear Data).
4) Reboot the phone.
5) When opening Google Play it should make give their agreement again. If it doesn't, then Data has not been cleared.
6) The rows modified in the build prop is as follows:
Desire ro.product.model = X
HTC ro.product.brand =
Desire ro.product.name = X
Desire ro.product.device = X
...
HTC ro.product.manufacturer =
AGAIN, I HAVE NOT TESTED THIS SO USE AT YOUR OWN RISK!
APP SUPPORT FOR ZTE U950
Note: Some apps will throw package errors after downloaded and then will not install. This method will help a lot of these errors from occurring. It doesn't work for all, but it will for some [tested with Dead Trigger 2].
1) Download this file.
2) Use a file explorer like ES Explorer (free) or Root Explorer (paid) and put com.google.android.maps.xml in /system/etc/permissions
3) Put com.google.android.maps.jar in /system/framework
4) Reboot the phone and now apps should install without issue.
DEAD TRIGGER 1
1) Enable graphics details to High in Setup/Others.
2) Exit the game.
3) Use a file explorer like ES Explorer (free) or Root Explorer (paid) and go to /data/data/com.madfingergames.deadtrigger/shared_prefs/
4) Edit the com.madfingergames.deadtrigger.xml file.
5) Change <int name=”UnityGraphicsQuality” value=”1″ /> to <int name=”UnityGraphicsQuality” value=”2″ />
6) Change <int name=”OptionsGraphicDetail” value=”2″ /> to <int name=”OptionsGraphicDetail” value=”3″ />
7) Save the com.madfingergames.deadtrigger.xml file.
8) Remove all write permission on User, Group and Other for the com.madfingergames.deadtrigger.xml file.
9) Delete the com.madfingergames.deadtrigger.xml.bak file.
Note: This technique works on any non-Tegra device.
APP TRICKS
If apps cannot be downloaded normally (from Google Play), this guide will show an alternative method on how to install them:
1) Download the necessary apk file online.
2) Open the 4.2LatinIme.zip with 7zip or WinRAR and delete the keyboard APK (or keep it if not installed yet).
3) While the ZIP is open go into "/Sytem/App" and place in it any APK you want installed.
4) Boot into recovery.
5) Flash the ZIP file.
6) Reboot and the app(s) should be installed.
Note: I have noticed that certain apps do not flash properly so an alternative APK needs to be downloaded. However, once you have the right apps to install Google Play, you should be able to download any apps from the store.
HARDWARE FIXES BY SKA
NOTE: Always work without the battery attached to the phone.
SIM Card No Longer Works
INFO: There is a diode which provides voltage to the SIM card. Somehow it has become loose, which disallows current to the SIM. Thus, the baseband cannot recognize the SIM card any longer.
FIX: The easiest way to fix and check something is to "re-flow" the PCB (printed circuit board). The modem soldering must be re-flowed in order to reconnect the loose diode and re-allow voltage back to the SIM card.
Touchscreen Not Displaying
Open up your phone. If you don't know how, then you won't be able to continue...
There are three connectors on the left soc side. Check the upper connector near the audio jack and try to seat with a pair of tweezers very gently.
There is a white line on every connector - apart from the battery connector - pull up straight. It must be exactly at the of the beginning of the brown clip when pulled downwards.
MISC
I have successfully paired this phone with a PS3 controller using Sixaxis. This is not unique to my phone as I have verified that there is support within the Kernel for this.
It does seem that Wii controller support can be turned on according to the kernel...
There are no known custom kernels for this phone, however, the incomplete Cyanogenmod ROM available does seem to use its own kernel.
The phone is "stuck" on ICS 4.0.4 with almost every ROM. The incomplete Cyanogenmod ROM upgrades the OS to JB 4.1.2.
The phone is known to have heating issues on different (all?) firmware versions. While these do not seem to attribute to hardware failure, it is an annoyance.
Different firmware versions apparently produce varying levels of GPU performance: The best in GPU performance is U950V1.0.0B14, but this build may produce issues in some games. The worst in GPU performance is U950V1.0.0B18, but it is stable. The U950V1.0.0B22 is stable as well but has better GPU performance than B18. I have found no information on how well the first and last firmware versions perform in terms of GPU.
To disconnect the battery connector you need to place a spudger beneath and lift up. It is the same method used for the connectors of fans, temperature sensors, and the battery in a MacBook Pro 2006/7/8.
Thank you for this Tutorial.
Do you know a method to change language in CWM ?
Best regards
cmoegele said:
Thank you for this Tutorial.
Do you know a method to change language in CWM ?
Best regards
Click to expand...
Click to collapse
Unfortunately I haven't found anything that would suggest that you can. The best I could do is have one of my friends tell me what each section states, but that may be a long while from now.
The menus I have figured out and listed are the most necessary. The others are just icing I suppose.
Unable to switch it back on
Hi,
first of all, please excuse me if this is not exactly related to this post, but I see there is not much discussion around this device so I figured this would be an okayish place to ask.
I got my ZTE U950 just today, put my SIM and MicroSD cards in it, turned it on, all OK. I played with it for a while, changed the language into English, tried some apps, deleted lots of default installed Chinese apps (such as Baidu, QQ, Baidu maps, etc).
I run Debian on my machine, so this guide wasn't working for me. However, I tried to run Genotools on Wine and followed the first steps, but no pop-up showed in my phone and I decided that probably Wine wasn't forwarding the USB dev properly. The phone kept on working normally for a while, I even recieved a phone call.
Then I turned it off just to switch the SIM back to my old phone and, after that, I haven't been able to switch the ZTE back on again. At first I thought it'd be the battery running out (although it reported 50% left while it was on), but I've had it connected for about 30 minutes now and I still can't turn it on...
Do you guys know if there is something I can try?
Thanks a lot and excuse me again if I posted in the wrong place... (and if I have, could you please point out where should I post it?)
Bernat.
EDIT: Today I woke up, I pressed the power button and... surprise! It just worked!
No Popup on phone
Hello
I have tried to follow the steps as you have mentioned.
Root>2nd Button>Popup>ok
But nothing appeared on my phone.
Can you guide me what should I do.
I have USB debugging and Unknown Source checked but no popup appeared on my phone.
raoyasir said:
Hello
I have tried to follow the steps as you have mentioned.
Root>2nd Button>Popup>ok
But nothing appeared on my phone.
Can you guide me what should I do.
I have USB debugging and Unknown Source checked but no popup appeared on my phone.
Click to expand...
Click to collapse
Do you have the usb-drivers installed ? (doublechek in device manager for windows ) Sometimes Win7-64 or Firewalls block uncertified drivers to install correctly. For 7-64 you can press F8 during early boot and choose "force unsigned drivers" or something simiar. On linux you should go through an Android adb installation howto, to correctly get debuginterface running.
Once you have installed chinese recover you can install some prerooted images from the hungarion or chinese sites.
br
cm
PS: has someone skills for implementing other languages or removing the chinese letters on some menues ?
I just bought ZTE V985 which is also tegra 3 device. Can anyone help how to root it?
Sent from my HTC Desire using xda app-developers app
how to root zte v985
someone please tell us how to root zte v985.
3G
Hi guys,
does anybody know if/how it is possible to connect to a 3G network with this terminal? In the specs it says it can only connect to Chinese 3G networks, so I'd like to know whether this is a software or a hardware restriction.
If it's a hardware one, I guess the solution must be pretty complex...
Cheers!
alz_uk said:
someone please tell us how to root zte v985.
Click to expand...
Click to collapse
I was able to root my ZTE V985 couple days ago. Download root installation package from:
http://pan.baidu.com/share/link?shareid=68344&uk=2753639880
1. Install ZTE USB driver first: Goto Settings -Developer options - enable Driver CDROM. Connect your phone to the computer and install driver package from ZTE. 985root.7z package has also ZTE USB driver but it didn't work on my Win 7, so I installed drivers from phone.
2. Turn off CDROM mode and enable USB debugging mode and Unknown sources
3. Unzip 985root.7z file to any folder
4. Run xxxroot.bat and command window appears. Script will stop and ask you to press any key (in Chinese)
5. Check that your phone is connected and press any key. Script will upload files to your phone
6. There will be popup window on your phone. Click Restore my data
7. Phone will then boot up but keep it connected to PC and wait until it is fully booted
8. if there's nothing going on in command window, press any key and command window closes. If your are rooted, you have SuperUser app
Original instructions from here:
http://bbs.gfan.com/android-5226211-1-1.html
And Google translation:
http://translate.google.com/transla...=http://bbs.gfan.com/android-5226211-1-1.html
suunnittelija said:
I was able to root my ZTE V985 couple days ago. Download root installation package from:
http://pan.baidu.com/share/link?shareid=68344&uk=2753639880
1. Install ZTE USB driver first: Goto Settings -Developer options - enable Driver CDROM. Connect your phone to the computer and install driver package from ZTE. 985root.7z package has also ZTE USB driver but it didn't work on my Win 7, so I installed drivers from phone.
2. Turn off CDROM mode and enable USB debugging mode and Unknown sources
3. Unzip 985root.7z file to any folder
4. Run xxxroot.bat and command window appears. Script will stop and ask you to press any key (in Chinese)
5. Check that your phone is connected and press any key. Script will upload files to your phone
6. There will be popup window on your phone. Click Restore my data
7. Phone will then boot up but keep it connected to PC and wait until it is fully booted
8. if there's nothing going on in command window, press any key and command window closes. If your are rooted, you have SuperUser app
Original instructions from here:
http://bbs.gfan.com/android-5226211-1-1.html
And Google translation:
http://translate.google.com/transla...=http://bbs.gfan.com/android-5226211-1-1.html
Click to expand...
Click to collapse
Thank you very much my freind, you are a kind and intelligent person.
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
nabax said:
Hi guys,
does anybody know if/how it is possible to connect to a 3G network with this terminal? In the specs it says it can only connect to Chinese 3G networks, so I'd like to know whether this is a software or a hardware restriction.
If it's a hardware one, I guess the solution must be pretty complex...
Cheers!
Click to expand...
Click to collapse
Hahaha you silly billy, i know whats happened to you! You got the ZTE U985 instead of the V985. The ZTE U985 only supports TD-SCDMA 3g network which is CHINA only. You should have bought the ZTE V985 which is WCDMA 800/1900/2100 mhz which supports western 3G networks. LMFAO. I feel sorry for you fella.
Where did you buy the v985 ? I only can find offers from 350-400$ and for this pricing I can´t find any real advantages buying a chinese phone , there is also no DualSim,and normally very limited languages ( chinese cwm?),....
cmoegele said:
Where did you buy the v985 ? I only can find offers from 350-400$ and for this pricing I can´t find any real advantages buying a chinese phone , there is also no DualSim,and normally very limited languages ( chinese cwm?),....
Click to expand...
Click to collapse
I bought it from fastcardtech.com, only 275 USD with free delivery.
From hardware specs point of view this is a really good phone, fast as my Asus TF700T tab with Tegra 3. It also supports WCDMA 900/2100MHz which are the most used 3G frequencies in EU. It does have only English and Chinese languages, but I used MoreLocale 2 to get more choices. More Locale does not change system language (like settings, caller app etc) so those will remain in English, but for example now other apps like Google play, Chrome etc. supports the language you have chosen in MoreLocale.
Sent from my ZTE V985 using xda app-developers app
cmoegele said:
Where did you buy the v985 ? I only can find offers from 350-400$ and for this pricing I can´t find any real advantages buying a chinese phone , there is also no DualSim,and normally very limited languages ( chinese cwm?),....
Click to expand...
Click to collapse
Dont get it wrong my mate the zte v985 is a beast of a phone + a smart piece of hardware. Only downfall i see is the limited rom/root/customization support since its new (october 2012)
Reasons why you should purchase the zte v985:
1. really supports APP2SD (install apps to external sd so you never run out of space and you dont have to throw away your phone when internal memory of 4GB gets full like most other android phones)
2. quad core cpu + 12 core NVIDIA gpu (theres websites full of games made only for this cpu + gpu)
3. USB OTG (using your superfast cpu and gpu together with usb otg you can turn your phone into an high class gaming system using two usb game controllers playing arcade roms and 3d games ON YOUR PHONE!). This is an awesome feature that not all phones support even some high performance quad core phones dont have this function.
4. 720P HD screen + 1080P HD Playback/Recording
5. Full MHL support (usb to hdmi)
6. Cheapest all round high performance quad core. Awesome price (£190) for a phone compared to other quad core high performance phones e.g galaxy note 2 @ £500
NOTE: if you would like to buy this phone for the price mentioned leave a message with your email or contact me i know a seller in china.
NOTE: Or you could wait another month or two and buy the new mtk 6589 quad core phones such as the UMI X2 which is quad core, DUAL SIM, usb otg, 2GB RAM, 32GB ROM and dirt cheap (£200!!!)
I get my ZTE V985 today through the post, cant wait till i get it!
Recovery in english language?
Hi
Anyone found Recovery in English language?
Google play
I can install google play, but if i open it, it immediatly shuts down again...
Any idea's ?
cwm zte u950 test 1 (build, 28 nov 2012) by me.
===================================
(cwm-u950-6.0.2.3-permanent)
-------------------------------------------
CRC32 : D2CD4005
MD5 : A1C6B72375B2E79100AA9BE52D0F30C2
SHA-1 : C7B3165D1E1F7463BFF16C0DE7747E6B3EC3F807
xxx.media*fire.com/download.php?0411sb2m1kkyrv4
(cwm-u950-6.0.2.3-temporary)
------------------------------------------
CRC32 : 830121A8
MD5 : 8239E70CB81548FE4427C505A5184749
SHA-1 : 9CF9CED3EC6CA2B79AE174E03A423435BB0FFFAC
xxx.media*fire.com/download.php?m90c896m17u0o9p
sorry.. i still need to learn..
please report cwm zte u950 test 1 (build, 28 nov 2012).
suunnittelija said:
I bought it from fastcardtech.com, only 275 USD with free delivery.
From hardware specs point of view this is a really good phone, fast as my Asus TF700T tab with Tegra 3. It also supports WCDMA 900/2100MHz which are the most used 3G frequencies in EU. It does have only English and Chinese languages, but I used MoreLocale 2 to get more choices. More Locale does not change system language (like settings, caller app etc) so those will remain in English, but for example now other apps like Google play, Chrome etc. supports the language you have chosen in MoreLocale.
Sent from my ZTE V985 using xda app-developers app
Click to expand...
Click to collapse
ZTE Grand Era V985 Recovery (support English)download link: pan.baidu.com/share/link?shareid=372147&uk=973327405
If you have any problems,please sent a email to me ,my email address is '[email protected]' ,i can help root your ZTE Grand Era V985,and install the recovery,the recovery includes English language.At last,the Android 4.2 for V985 will coming soon,maybe in April,if anyone need ,i will send to you.Thank you.
i found twrp for the zte u950 in english in this package, it is in the folder recovery_3 :good:
what do you think? is it possible to make the zt3 u980 to work with european 3g network? i thought to flash the baseband from zte v985 on the zte u950... do you think its possible?
More stuff in English
hey Heatshiver...u can add these in your OP
I found some roms HERE for U950 which support english language..and atleast instructions are in english
2 or 3 of them are based on MIUI ...
I've tried the 1st one...works perfectly so didn't flash others
Extracted img file of twrp recovery (english) from the package provided by superpfpf - attached in the post
Note this is NOT the Blu R1 HD that Amazon sold with advertising built in; it is a separate more expensive model named BLU R1 PLUS. I have searched online for several weeks and not a peek how to Root BLU R1 Plus except the standard promises of paid root services and of course Kingroot. I've used Kingroot before on other phones in desperation but it seems you never get all of their app off your phone even if they are able to root it.
Has anyone any idea how to root this phone? Thank you!
If you have rooted your BLU R1 PLUS (not the Amazon Prime model) if you would share how, I will be more than grateful. Thank you.
Seriously? Still not a single method to root this device?
I think it's a great fone (with a few issues like multi-touch), but still... Wanted to mess with some root tweaks since several months ago.
Any news on this thread?
I have the same problem, i had it since a year ago i dont get how there is not a single root method yet.
I don't know either. The boot loader is locked on this one. I believe all the effort went into cracking the Amazon commercial one. I am guessing there are only a couple of people who can crack them and they either stay busy with more exciting models (the cheapest ones are not always the most popular for some reason, it's the opposite with me). Yes I made the mistake of purchasing the BLU R1 Plus without researching that all the love was being spent on the other models, otherwise this appears to be a really nice phone. I've had it for nearly 6 months and it's still in the box because I am using my old cracked face BLU until I hear how to root this one. I don't use them unless I can root and add secure Xposed environment. Too much, too exposed to the laughable "free" world of apps. I like the BLU phones. This one even has an extra long battery life and doesn't require a bank loan to purchase as most of the popular ones do
Also I tried Kingroot on this one in desperation .... massive list of failures and not sure what condition it left the phone in.
Root TWRP Blu R1 Plus
Unlock Bootloader & Root
BLU R1 Plus
Yes it has been done
Thanks to Antonio Lopes for his help with this and porting TWRP
Thanks to RootJunky for his FRP Unlock img
Thanks to Larry Miller for additional device testing
This method uses adb and fastboot commands and has only been tested on v13
It will wipe your device during install
ADB and Fastboot Minimal is included in zip file
Before any actions: copy all that you need from SDcard internal to PC!
If you want backup calls, messages, contacts (different by goggle contacts or if you can record all the contacts in your google contacts account directly through the contacts application).
For backup, use any application from google play!
Save in your PC! After all the processes you can restore them using the same application that you used.
- Instructions to PROCESS:
1. On phone
Enable Developer Options
Enable USB Debugging too
2. On PC search the folder of adb
fastboot minimal C drive
Unzip TWRPRootR1Plus.zip and Place unlock.img , recoveryTWRP.img and SR3-SuperSU-v2.79SR3-20170114223742.zip in adb folder
Start adb
adb devices ( Ensure connection)
adb reboot bootloader
fastboot flash frp unlock.img
fastboot oem unlock
( Confirm with volume up select )
fastboot flash recovery recoveryTWRP.img
Fastboot will show image flashed but due to BLUs locking of device fastboot reboot will not function
So ….
Unplug device , Hold power off until device turns off
Hold Volume up and Plug device back into PC ,
Continue to hold volume up until TWRP boots fully
Select Wipe , Select Format Data ( don’t worry if any errors show )
Reboot recovery
Select Mount , Select Mount USB Storage
Open Device on PC , Move SR3-SuperSU zip to device external_sd
Unmount
Select Install
Select external_sd
Select SU zip and install
Reboot System
Phone May reboot several time do not interrupt boot
https://www.mediafire.com/download/hjmjpgepfbnjy7h
SOLVED: I figured out the issue. As mentioned in this thread, downgrading to an older version of flashtool successfully got me past the bundle mismatch error, allowing me to flash stock US firmware onto the device. Still not exactly sure why that's the case, but it worked for me.
Hey folks,
Hope you're all doing well! I have a bit of an odd situation. I recently picked up a Z-Pocket Game, a handheld built using the internals from a torn down Z1 Compact.
A few days ago, I decided to see if I could poke around and install a custom ROM onto the device, given how many are available for the source hardware (Z1C). The device already came pre-installed with XZDualRecovery and was running a custom ROM in Chinese built off Lollipop.
I'm a novice when it comes to flashing and custom ROMs, so I tried to learn more about the process before getting started. Evidently, however, I'm in over my head - fully my responsibility, of course, but over my head nonetheless.
Long story short, I tried to install Lineage OS 17.1 onto the device via the version of TWRP already installed on the device. As per the installation instructions detailed here, I did an advanced wipe before attempting the install, selecting "Dalvik," "System," "Cache," and "Data." When I actually attempted the process, however, it errored out almost immediately, leaving me with a wiped system and no ROM (TWRP warned me about this prior to rebooting).
When I now power on the device, it's stuck on the "Sony - XPERIA" screen, and the LEDs don't light up at all. I can't seem to access TWRP or Philz on the device with the normal key presses. I can force the device off by holding Power and Volume Up, and it also seems able to enter fastboot mode (with a solid blue LED) and flash mode (the LED flashes green, then turns off). I've tried a number of different things to try and fix it, but all of them haven't worked in one way or another. Providing a brief overview to the best of my recollection here, but happy to try again and give more detail if needed:
Using fastboot via the command line to flash a new recovery onto the device gives me an error indicating I can't write the file to the device, and things just end there.
Trying to flash a stock US ROM to the device via flashtool gives me an error indicating the device does not match the bundle, and things just end there.
Trying to restore the device using Xperia Companion first gives an error requesting permission to access the device, then when I select "My Device Cannot Be Detected or Started" and follow the instructions, it tells me that "an error occurred while repairing this device," and provides this small blurb of device info:
UEGetPhoneInfoMissingInfo
Z-POCKET GAME 3579 1279-6978 R2D 14.6.A.1.236
2.11.6.0 / Windows 10 64 bit / Win32 / US / /
So I'm a bit stumped. It seems as though enough of the device is working to get everything back into a workable state, but I'm not sure of how to go about that. Any thoughts or leads would be greatly appreciated!
edit_duplicate said:
SOLVED: I figured out the issue. As mentioned in this thread, downgrading to an older version of flashtool successfully got me past the bundle mismatch error, allowing me to flash stock US firmware onto the device. Still not exactly sure why that's the case, but it worked for me.
Hey folks,
Hope you're all doing well! I have a bit of an odd situation. I recently picked up a Z-Pocket Game, a handheld built using the internals from a torn down Z1 Compact.
A few days ago, I decided to see if I could poke around and install a custom ROM onto the device, given how many are available for the source hardware (Z1C). The device already came pre-installed with XZDualRecovery and was running a custom ROM in Chinese built off Lollipop.
I'm a novice when it comes to flashing and custom ROMs, so I tried to learn more about the process before getting started. Evidently, however, I'm in over my head - fully my responsibility, of course, but over my head nonetheless.
Long story short, I tried to install Lineage OS 17.1 onto the device via the version of TWRP already installed on the device. As per the installation instructions detailed here, I did an advanced wipe before attempting the install, selecting "Dalvik," "System," "Cache," and "Data." When I actually attempted the process, however, it errored out almost immediately, leaving me with a wiped system and no ROM (TWRP warned me about this prior to rebooting).
When I now power on the device, it's stuck on the "Sony - XPERIA" screen, and the LEDs don't light up at all. I can't seem to access TWRP or Philz on the device with the normal key presses. I can force the device off by holding Power and Volume Up, and it also seems able to enter fastboot mode (with a solid blue LED) and flash mode (the LED flashes green, then turns off). I've tried a number of different things to try and fix it, but all of them haven't worked in one way or another. Providing a brief overview to the best of my recollection here, but happy to try again and give more detail if needed:
Using fastboot via the command line to flash a new recovery onto the device gives me an error indicating I can't write the file to the device, and things just end there.
Trying to flash a stock US ROM to the device via flashtool gives me an error indicating the device does not match the bundle, and things just end there.
Trying to restore the device using Xperia Companion first gives an error requesting permission to access the device, then when I select "My Device Cannot Be Detected or Started" and follow the instructions, it tells me that "an error occurred while repairing this device," and provides this small blurb of device info:
UEGetPhoneInfoMissingInfo
Z-POCKET GAME 3579 1279-6978 R2D 14.6.A.1.236
2.11.6.0 / Windows 10 64 bit / Win32 / US / /
So I'm a bit stumped. It seems as though enough of the device is working to get everything back into a workable state, but I'm not sure of how to go about that. Any thoughts or leads would be greatly appreciated!
Click to expand...
Click to collapse
Glad that you find out yourself.
And thanks for sharing!
* Prelude
What started this journey was noticing that Tasker had restricted call screening
to android versions 10+. I would be delighted to hear what techniques fellow
forum members use to fight spam calls. I am a complete beginner, and so I
thought I would detail my journey in case it proves useful for others. There is
some outdated information and plenty of online tutorials, it just takes some
time to sort it out.
I have a Huawei P20 lite ANE LX3.
* Unlocking the Bootloader
I believe this is by far the most tedious step. Now that I am free from carrier
contracts, I know that my next phone will not be from a manufacturer with a
locked bootloader. In any case you may have some luck emailing Huawei directly
or through paid third-party services. What worked for me was potatoNV
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
The documentation on the repository is perfectly fine. Specifically in my case,
the device first showed under device manager as 'USP SER' and I had to reinstall
the test point drivers (found in the above README) for it to turn into 'Huawei
USB COM 1.0.' PotatoNV did its job and I managed to get my unlock code.
* Project Treble/GSI? Fastboot? ADB?
Again, being new to all of this, I did notice a lot of noise when searching
online for information. The most informative links I found useful:
- https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)
- https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
- https://developer.android.com/studio/releases/platform-tools
What is worth repeating is to USE THE GOOGLE PLAY APP 'TREBLE INFO' over the
more popular 'Treble Check', which falsely informed my that I needed an A image
rather than being fine with an A/B image. This wasted a lot of my time.
Initially I went down the route of using TWRP to flash the image, but this led
me to a soft brick (could very well be my own fault). The phone was frozen to
the TWRP splash screen, 'adb reboot bootloader' would not work. Power plus
volume down or volume up also had no effect. With no access to e-recovery or the
bootloader, I had really dug myself into a hole.
* Unscrewing a bricked phone
My last chance at fixing this consisted of getting the stock service firmware.
[NO ROOT] [BOOTLOADER LOCK] How to install an update [DLOAD Method]
I'm very happy :D:D After spending a lot of time trying to figure out how to install an original firmware using the dload method, I managed to find a guide that explains how to do it and today I will report the main steps: First of all, we need...
forum.xda-developers.com
This forum thread was useful and on unscrewing the situation. The real useful
part of the above link was the 'Software Upgrade Guidelines' documentation.
So ultimately what unbricked my phone was following the direction to press all
three buttons (power, volume up, volume down) at once to enter "automatic
upgrade mode." I gather this was supposed to utilize the 'dload' folder I copied
over earlier. As an aside, it was a lifesaver that 'adb shell' gave me access to
some unix commands to make poking around easier. The automatic upgrade using the
'dload' folder failed.
BUT RESTARTING FROM THIS "AUTOMATIC UPGRADE MODE" GRANTED ME ACCESS TO RECOVERY
MODE VIA THE POWER BUTTON + VOLUME UP whereas before this was not the case. By
the grace of God this allowed me to download a recovery image from Huawei
servers. How much longer will their servers retain this image? I don't know, but
I'm grateful either way.
* Lineage OS successfully flashed
What instead worked for me was flashing the "GSI image without TWRP" - from the
2nd of the 3 links above. This is the image that I used:
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz
For sake of completeness M Rahman's 2018 article was still mostly accurate, the
'-u' flag may be omitted from 'fastboot -u flash system name_of_system.img'. The
only other thing I would append to his instructions is -AIF-'s recommendation to
4. Run command fastboot reboot, unplug your phone, when appears on screen yellow
warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe
data/factory reset'.Reboot . - From:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
I say this because I had seen the power button + down volume/up volume technique
yield different results depending on whether the phone was connected to the
computer. I suspect this is the fault of HiSuite, but who is going to track down
a bug like this?
* Evaluation
Pros:
- I had solved my initial problem.
- The new phone feeling!
Cons:
The most noticeable deficiency was that adding an external SD card AS SYSTEM
STORAGE would never finish; I gave it about a day before giving up.
I will add further reports as they come up.
In conclusion I give props to Huawei for keeping that server image alive, but
last I heard they were pivoting away from smartphones into clean energy
altogether. If I were to do it all over again, I'm not sure it would be worth
it. This took a good day's worth of time.
Big thanks to the AOSP developers and the XDA community for buying
my old P20 lite a bit more time. I'm also interested in which companies the
community considers friendly to "popping the hood"/tweaker mentality.
Hope this was helpful for someone,