Database Info

A self inflicted wound

Loaded my BL 1.1 with [ROM - 1.2] BETA ICS 4.0.X - Team DRH, worked like a charm. I got greedy and attempted to load [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery. It didn't go well.
I knew that if I can get into the APX mode, I would eventually Flash myself back to the original BL 1.1 3588. After many hours I did succeed and got the invitation to take the 3588 OTA. That went well. I was trying to get CWM to switch on (power plus Volume+) because even though I was able to see the internal SD card, side load the ICS 4.0.X & the Gapps, I knew there was no way to partition (2048/0) as well as unpack the new ROM.
During one of my attempts to get CWM to switch on, I was invited to take a BL 1.2 update, #5379 I think. That reboot really locked me out. I have the cover off to access the reset button. I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is essentially it doesn't see the tablet.
May I ask for some suggestions? I'm ready to Flash away but....
“Please follow the steps in the OP. If you follow those, you will actually be flashing the newest CWM touch recovery and our rom.
HOW TO INSTALL
• Boot into current version of CWM and "Wipe data/factory reset"
Dear fosser2,
“I have the cover off to access the reset button, I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is it essentially the Flash doesn't see the tablet.”
Thank you for your excellent work. Your steps are very explicit for a flawless installation.
The situation I have failed to make clear is that I am unable to reach the APX mode. There is no audible tone (high to indicate APX mode, low to indicate Not in APX mode).
My attempt to reflash to stock blindly, in the audible sense, has the response “USB device not found.
I’m going to repost this in the General section. I would be grateful for any suggestions.

hushpup131 said:
Loaded my BL 1.1 with [ROM - 1.2] BETA ICS 4.0.X - Team DRH, worked like a charm. I got greedy and attempted to load [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery. It didn't go well.
I knew that if I can get into the APX mode, I would eventually Flash myself back to the original BL 1.1 3588. After many hours I did succeed and got the invitation to take the 3588 OTA. That went well. I was trying to get CWM to switch on (power plus Volume+) because even though I was able to see the internal SD card, side load the ICS 4.0.X & the Gapps, I knew there was no way to partition (2048/0) as well as unpack the new ROM.
During one of my attempts to get CWM to switch on, I was invited to take a BL 1.2 update, #5379 I think. That reboot really locked me out. I have the cover off to access the reset button. I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is essentially it doesn't see the tablet.
May I ask for some suggestions? I'm ready to Flash away but....
“Please follow the steps in the OP. If you follow those, you will actually be flashing the newest CWM touch recovery and our rom.
HOW TO INSTALL
• Boot into current version of CWM and "Wipe data/factory reset"
Dear fosser2,
“I have the cover off to access the reset button, I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is it essentially the Flash doesn't see the tablet.”
Thank you for your excellent work. Your steps are very explicit for a flawless installation.
The situation I have failed to make clear is that I am unable to reach the APX mode. There is no audible tone (high to indicate APX mode, low to indicate Not in APX mode).
My attempt to reflash to stock blindly, in the audible sense, has the response “USB device not found.
I’m going to repost this in the General section. I would be grateful for any suggestions.
Click to expand...
Click to collapse
can you get into APX mode?
---------- Post added at 05:19 PM ---------- Previous post was at 05:12 PM ----------
if so just use my BL update
http://forum.xda-developers.com/showthread.php?p=20410053#post20410053

jamcar said:
can you get into APX mode?
---------- Post added at 05:19 PM ---------- Previous post was at 05:12 PM ----------
if so just use my BL update
http://forum.xda-developers.com/showthread.php?p=20410053#post20410053
Click to expand...
Click to collapse
I am not able to get into the APX mode. The basis of my belief is there is no audible signal (USB to PC) and there is no new window opening inviting me to explore a new drive.

I have disconnected the battery both short term as well as over night, no response from the power only and power plus volume – buttons.
The charge light has turned green; no response from the buttons.
Measuring the voltage at the charger tip read 12+ volts. I am using a new USB to PC cable. Out of curiosity I unplugged the battery connector and re-connected to see the charge light switch off and on while the charger was connected. As a novice here, I suspect that test eliminated the charging circuit as a fault.
I'm in UBUNTU
loaded and extracted gtab.nvflash.1.1.branch.20110422 with cwmv8.zip
the response says:
"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --go
@set /p batuserinput=Press enter to continue:
- what does this mean?

1. Is there any sort of display brightening (even briefly?) after you power on? In APX mode, for example, the screen will brighten slightly, then go dead again.
2. Try this test on Ubuntu to see if the tablet has gone into APX mode:
Code:
[I]Power off gTab.
Power on gTab using Power & Vol [-].[/I]
$ [B]sudo dmesg -c >/dev/null[/B] [I] Clear old kernel logs.[/I]
[I]Now connect the USB cable to gTab.[/I]
$ [B]dmesg[/B] [I] Get latest log message.[/I]
[18045.279886] usb 1-1.2: new full speed USB device number 6 using ohci_hcd
[18045.384823] usb 1-1.2: New USB device found, idVendor=0955, idProduct=[B]7820[/B]
[18045.384830] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[18045.384835] usb 1-1.2: Product: APX
[18045.384839] usb 1-1.2: Manufacturer: NVIDIA Corp.
$
A USB product id of 7820 indicates APX mode on the gTab.
Post the exact output (if any) of your run here.
For reference this is the output when the gTab is running either CWM or the ROM:
Code:
$ [B]sudo dmesg -c >/dev/null[/B] [I] Clear old kernel logs.[/I]
[I]Now connect the USB cable to the gTab.[/I]
$ [B]dmesg[/B] [I] Get latest log message.[/I]
[17516.799429] usb 1-1.2: new full speed USB device number 5 using ohci_hcd
[17516.911353] usb 1-1.2: New USB device found, idVendor=0955, idProduct=[B]7100[/B]
[17516.911361] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[17516.911366] usb 1-1.2: Product: NVIDIA Harmony
[17516.911370] usb 1-1.2: Manufacturer: NVIDIA
[17516.911374] usb 1-1.2: SerialNumber: 0270308341006257
$
The product id will be 7100.

[email protected]:~$ coonected USB to Gtab, power button plus vol minus 2 minutes
coonected: command not found
[email protected]:~$ sudo dmesg -c >/dev/nul
bash: /dev/nul: Permission denied
[email protected]:~$ pwd
/home/ubuntu
[email protected]:~$ cd ..
[email protected]:/home$ cd ..
[email protected]:/$ pwd
/
[email protected]:/$ sudo dmesg -c >/dev/null
[email protected]:/$ dmesg
[email protected]:/$
[email protected]:/$

It's not surprising that you got no output--I screwed up. The sequence of steps was incorrect: the cable has to be connected between the 2 dmesg commands. Please repeat.
(If you want to insert inline comments on the command line do it like this:
Code:
$ [B]# This is just a comment.[/B]
The shell will ignore everything from the `#' character to the end of the line.)
And, this video is what I recommend to people whose bootloader seems to be trashed--which is what I think your problem is: How to unbrick your Viewsonic G-Tablet

[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ # power plus volue - for 3 seconds, USB inserted
[email protected]:~$ dmesg
[email protected]:~$

The first 2 commands are not needed:
hushpup131 said:
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ # power plus volue - for 3 seconds, USB inserted
[email protected]:~$ dmesg
[email protected]:~$
Click to expand...
Click to collapse
Yeah, as I suspected, its a bad bootloader and/or other critical partition problem.
If you are certain that the USB cable and ports are OK (check using another device--try a "sudo adb devices" command with a phone, for instance) and you ran the second dmesg command after connecting the USB cable (otherwise, power off and do the sequence again), then your only option now is to follow the K1 pad-shorting procedure shown in the video.
BTW, you didn't answer question #1 in post #5, above. Is there any change in the display brighness after powering on?

[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[13557.584148] usb 4-1: USB disconnect, device number 3
[13557.908045] usb 4-1: new low-speed USB device number 4 using uhci_hcd
[13558.145227] input: Microsoft Microsoft Wireless Optical Mouse\xffffffc2\xffffffae\xffffffae 1.00 as /devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/input/input17
[13558.145525] generic-usb 0003:045E:00E1.0003: input,hidraw0: USB HID v1.11 Mouse [Microsoft Microsoft Wireless Optical Mouse\xffffffc2\xffffffae\xffffffae 1.00] on usb-0000:00:1a.1-1/input0
[13558.256080] usb 1-4: new high-speed USB device number 6 using ehci_hcd
[13558.397196] scsi9 : usb-storage 1-4:1.0
[13559.397403] scsi 9:0:0:0: Direct-Access Motorola A855 0001 PQ: 0 ANSI: 2
[13559.398816] sd 9:0:0:0: Attached scsi generic sg3 type 0
[13559.403602] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[email protected]:~$
question one, post five... there was no change in the display
There was no change in the display after shorting K1

hushpup131 said:
[email protected]:~$ dmesg
[13557.584148] usb 4-1: USB disconnect, device number 3
Click to expand...
Click to collapse
Your USB cable seems OK, but, I don't like that line above. Can you describe exactly what you did when you captured that output?
And, run through that dmesg sequence once again exactly as described and post the output. Also, connect the gTab directly to a USB port, and not through a hub.

Unlock Nexus Player

This is how you unlock the bootloader (warning!!!! This will erase everything you have on your device!)
1. adb reboot fastboot
2. fastboot oem unlock(x2. It will prompt you to enter it again to confirm)

Awesome. First thing I'm going to do out of the box.
Sent from my Oneplus One with Tapatalk Pro.

peppy6582 said:
This is how you unlock the bootloader (warning!!!! This will erase everything you have on your device!)
1. adb reboot fastboot
2. fastboot oem unlock(x2. It will prompt you to enter it again to confirm)
Click to expand...
Click to collapse
And don't forget, to put device in fastboot, press and hold button that is located on the bottom of the player, plug in the power cord and hold until led light flashes repeatedly.

Fastboot
On Ubuntu, ADB is not ever seeing my NP. I can get it in fastboot mode with the button, and my USB devices enumerate (2 different ones), but ADB never shows it connected.
Code:
[376711.228958] usb 3-2.4: new high-speed USB device number 12 using xhci_hcd
[376711.246426] usb 3-2.4: New USB device found, idVendor=18d1, idProduct=4ee0
[376711.246436] usb 3-2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[376711.246441] usb 3-2.4: Product: fugu
[376711.246445] usb 3-2.4: Manufacturer: Android
[376711.246450] usb 3-2.4: SerialNumber: 13737740
[376772.269599] usb 3-2.4: USB disconnect, device number 12
[376773.252023] usb 3-2.4: new high-speed USB device number 13 using xhci_hcd
[376773.282912] usb 3-2.4: New USB device found, idVendor=8086, idProduct=0a2c
[376773.282919] usb 3-2.4: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[376773.282923] usb 3-2.4: Product: MOOREFIELD
[376773.282926] usb 3-2.4: Manufacturer: INTEL
[376773.282943] usb 3-2.4: SerialNumber: <redacted>

Ahh, I forgot I had to enable USB debugging in the developer menu. The dev menu is enabled by clicking "Build" a handful of times from the "About" menu.

figured it out : windows , device manager , let me choose driver , selected ADB TESTING INTErFACE , all is good. hope this helps others,.
================================================================================================================
using windows 8 , holding down bottom button i get to fastboot , when i run "fastboot devices" i get nothing , when run adb devices i get " emulator-5554 device " ( that was bluestacks ) i had to end task . but still no luck. when i run "fastboot devices" i get nothing , when run adb devices i get nothing
i double checked developer mode , all good , windows 8 calls it FUGU , , in control panel . if i run 'fastboot oem unlock" all i get is "waiting for device "
what step did i miss? any help appreciated./.

I have the same problems running Linux Mint 17.
"adb shell" works OK when booting normally.
"sudo fastboot devices" shows nothing in bootloader/fastboot mode, and no other fastboot commands work. Also see:
<6>[84128.968111] usb 1-5: new high-speed USB device number 55 using ehci-pci
<6>[84129.106293] usb 1-5: New USB device found, idVendor=18d1, idProduct=4ee0
<6>[84129.106305] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
<6>[84129.106313] usb 1-5: Product: fugu
<6>[84129.106319] usb 1-5: Manufacturer: Android
<6>[84129.106324] usb 1-5: SerialNumber: DA4D....
I'm itching for root to explore more.

fastboot problem is due to need for new fastboot.
I've attached the Linux version in my updated SDK. Windows version is in SDK on Google site somewhere I guess.

Just thought that I'd point out that holding down the button on the bottom of the device while plugging in will load the bootloader...just another way to get there is all.

bsara said:
Just thought that I'd point out that holding down the button on the bottom of the device while plugging in will load the bootloader...just another way to get there is all.
Click to expand...
Click to collapse
And one that doesn't require a working adb connection first.

Device not found
Trying to unlock Nexus Player but getting error, device not found. I enable USB debugging in the Developer menu and turn on developer by hitting Build in About menu.
I am using a windows 7 computer and i get the following when i try to unlock,
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>

dreadprinz said:
Trying to unlock Nexus Player but getting error, device not found. I enable USB debugging in the Developer menu and turn on developer by hitting Build in About menu.
I am using a windows 7 computer and i get the following when i try to unlock,
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
The command is "adb reboot-bootloader" not "fastboot"
Also, double check that you have the latest platform tools installed from the SDK manager.

Just go straight into the bootlloader by holding the button as you plug it in, then wait for the light as BSaras post states . No driver needed

volwrath said:
Just go straight into the bootlloader by holding the button as you plug it in, then wait for the light as BSaras post states . No driver needed
Click to expand...
Click to collapse
Very good point...though you will still need the latest version of the android SDK platform tools for fastboot to detect the player.

bsara said:
Very good point...though you will still need the latest version of the android SDK platform tools for fastboot to detect the player.
Click to expand...
Click to collapse
I don't think so.
I haven't upgraded mine in quite a while and fastboot had no problem seeing the player. I am updating my sdk platform tools as we speak.
But then again I guess they are fairly new since I updated them to play with my google watch

Device not found
I tried the command "adb reboot-bootloader" still got error device not found .
I think i have the latest platform tools Revision 23.0.5.

Try this:
After you unlock Developer options,
Go into Developer options
You will see "Enable OEM unlock" make sure that is checked then you should be able to proceed

vitald2 said:
Try this:
After you unlock Developer options,
Go into Developer options
You will see "Enable OEM unlock" make sure that is checked then you should be able to proceed
Click to expand...
Click to collapse
Hmm I don't see Enable oem unlock anywhere.

vitald2 said:
Try this:
After you unlock Developer options,
Go into Developer options
You will see "Enable OEM unlock" make sure that is checked then you should be able to proceed
Click to expand...
Click to collapse
Maybe i am missing something here, but i don't see "Enable OEM unlock" anywhere.

dreadprinz said:
I tried the command "adb reboot-bootloader" still got error device not found .
I think i have the latest platform tools Revision 23.0.5.
Click to expand...
Click to collapse
You've listed the version of you "Android SDK Tools" not the "Android SDK Platform-tools" (which is found right below it in the SDK manager). At any rate, you probably are having a driver issue (I'm assuming that you're using Windows). I personally can't help you much there since I use Ubuntu, but this tool for Nexus devices might help: http://www.wugfresh.com/nrt. I know that the Player isn't listed there...but with that tool you can install the generic drivers...perhaps it will fix things for you.
Also, as stated before, you can (for the time being) just hold down the button on the bottom of the device while you plug in the device and it will boot into the bootloader (I.E. fastboot mode). Then run "fastboot devices" to see if anything shows up, if not...I would keep looking into the driver instructions on the tool I listed above. Also, to ensure that adb is seeing your device, you can also run "adb devices". Also, make sure that no other android devices that have USB debugging enabled are plugged in while you run your command, otherwise it won't succeed because it won't know which device to pick...or just run "adb -s [DEVICE_ID] reboot-bootloader" where [DEVICE_ID] is the id listed when running adb devices. Good luck.
And that "Enable OEM unlock" stuff is not true...just ignore it. Once in fastboot, you'll just need to run "fastboot oem unlock" twice in a row for the unlock to occur.

tf300t fastboot vs usb cable

My problem is my tablet is visible in normal mode on my pc. Bootloader 4.2.1, The Device is unlocked ok. adb devices: #serie ok, and adb reboot-bootloader function works. The tablet will reboot into fastboot mode, but I am unable to find a driver that works on my pc. I installed 1.97 pc asus sync, google sdk, minimal adb fasboot driver, all indicates error code 10
"fastboot devices" does not work. Rck is on and the icon does not flashes, the fastboot reboot feature is '' Waiting for device ". So if I disconnect and reconnect the USB cable, the tablet will restart on the OS...
Even tried with a live linux cd and still the same problem...
Note my usb cable has been replaced by a generic for my original cable had become unstable.
It can be the cause of my problem. Of course I tested with 2 cables? Factory reset and unlocke with v7 and v8 apk, and also an OEM recovery to latest firmware 10.6.1.27.5-20130902
I would like to set up a recovery to try others Roms,
Thanks for your help.

cyborg3691 said:
I would like to set up a recovery to try others Roms,
Click to expand...
Click to collapse
First of all, your boot loader must end with 27.5. Check it out when you are unsure before you do anything more.
Then try to flash Kang TWRP from your SD Card with Terminal Emulator using the following code:
dd if=/sdcard/ twrp_tf300t_kang_2.8.7.2.img of=/dev/block/mmcblk0p4
For more information have a look at Josh’s thread http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479

For this soluce the tablet need to be root...
I have make this but not working, the terminal not see the file on sd card....
On terminal i see
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/foo.img of=/dev/block/mmcblk0p4
/sdcard/foo.img cannot open for read: no such file or directory
1 [email protected]:/ #
help me

SOLUCE With another computer...
My problem was my computer z87 motherboard with incompatible usb port? I try front and rear usb ports,
with a generic usb cable, I have solutioned this problem, with a other old computer and minimal adb fastboot v. 1.3.1 with a netbook msi wind u100 runing xp and now, tf300t was detected in adb and fastboot mode the command devices works fine. I intall twrp and intall and try another rom.
Thanks for your help.

Updating ADT-3 to Android 11 with OTA bricks it

I had official Android 11 Beta on it (there was the guide how to update it).
Got OTA with Android 11 today.
And now it does not boot - staying on "androidtv" splash screen.
Does anyone have it? How to get to recover or something on it? Any way to perform reset on it or manual update while PC (adb) does not see it.
Reported this issue to google's tracker: https://issuetracker.google.com/issues/169172450
Linux machine sees USB device connected but obviously no ADB at this point:
Code:
[ +8,588816] usb 3-5: new high-speed USB device number 24 using xhci_hcd
[ +0,150146] usb 3-5: New USB device found, idVendor=1b8e, idProduct=c003, bcdDevice= 0.07
[ +0,000002] usb 3-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Code:
$ adb kill-server
$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached

Issue solved: Most probably booting sequence was blocked by USB connection to my linux host machine (yeah, development device is connected to linux machine for development). Unplugging USB (keeping power line from Y-shaped usb cable) make it bootable.

How do I downgrade VollaOS?

I'm looking for advice on downgrading the OS on my phone, as the performance used to be better. I've been struggling for days here, knowing very little about Android phones a week ago.
I have a Volla, which is a modified Gigaset GS290 (MediaTek chipset). I've been trying out a number of flash tools but am always getting stuck.
Last one I tried was MTKClient. I can get it to detect the phone, but it stops part way in the command line:
Preloader - CPU: MT6763(Helio P23)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0x7f
Preloader - Disabling Watchdog...
Preloader - HW code: 0x690
Preloader - Target config: 0x0
Preloader - SBC enabled: False
Preloader - SLA enabled: False
Preloader - DAA enabled: False
Preloader - SWJTAG enabled: False
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: False
Preloader - Mem write auth: False
Preloader - Cmd 0xC8 blocked: False
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca01
Preloader - SW Ver: 0x1
Preloader - ME_ID: A472FAA544E08CAF5B46DBB8xxxxxxxxx
Preloader - SOC_ID: AD6EA35C43EBBF6EA20446713F9B9EEEB3CF6409F1CF667F11E1287xxxxxxxxx
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
I'm at a loss at this point.

I was able to downgrade from VollaOS 11 to 10 successfully, but it was quite difficult with the tools available. I gave up on MTKClient. For the benefit of others who want to do this, I’ll outline the steps I used. Special thanks for Volla Developer Community on Telegram for offering some suggestions.
I connected my Volla phone via USB to a Windows 10 PC and went through these steps.
1) Install Android SDK
2) Install MediaTek VCOM USB drivers
3) Download VollaOS 10
4) Allow USB debugging
5) Try ADB sideloading
6) Unlock bootloader
7) Allow USB debugging again
8) Install custom TWRP recovery
9) Remove device check from ZIP
10) Sideload OS from TWRP
11) Reboot the system from TWRP
1) Install Android SDK
You need two Command Line programs on your PC called ADB and Fastboot to make changes on your phone. These are included in the official Android SDK ‘Android Studio’ and are in the ‘platform-tools’ folder, which installed at this location by default:
Code:
C:\Users\user\AppData\Local\Android\Sdk\platform-tools
2) Install MediaTek VCOM USB drivers
The Volla phone’s CPU (a modified Gigabit GS290) is a MT6763V (aka Helio P23). Windows needs the right drivers to interact with a MediaTek based device. I found a set called "Windows 10 x64 MTK USB Drivers.inf”. Some sites will include installers with the drivers, but I installed “MTK USB Port” manually by selecting “Add legacy hardware” in the Device Manager. Lots of good YouTube tutorials how to do that step by step.
3) Download VollaOS 10
Get it from this repository here
Now that there’s 3 different Volla phones, be mindful of project names in the filenames that match your phone.
Code:
Volla = yggdrasil
Volla X = yggdrasilx
Volla 22 = mimameid
4) Allow USB debugging
First, unhide the Developer Menu on your phone. Navigate here and tap it 7 times:
Code:
Settings > About phone > Build number
A new menu will appear here:
Code:
Settings > System > Developer options
In this menu, turn on "USB debugging”. You may be prompted to allow it and trust the connected computer.
Now run the Command Line from the ‘platform-tools’ folder and check your devices are communicating
Code:
>adb devices
You should see a devices serial number
5) Try ADB sideloading
This is worth trying next, because the proceeding step wipes your phone completely. It didn’t work for me because of 2 errors:
Code:
Error 21: “Failed to verify whole signature”
E3004: "This package is for "[device]" devices; this is a “GS290”
Reboot the phone into maintenance mode by holding power + vol up
Select ‘recovery’ from the menu by pressing vol up, and confirm it with vol down
Select Advanced>Apply Update> from ADB
From the command line run:
Code:
>adb sideload volla-10.0-20220430-release-k63v2_64_bsp-signed.zip
This is where I got error 21. To get around this I needed to use the custom recovery TWRP, and to install that I had to unlock the bootloader, which wipes the entire phone.
6) Unlock bootloader
With the phone’s system running normally, reboot into fastboot from the command line on your PC:
Code:
>adb reboot bootloader
Then
Code:
>fastboot flashing unlock
Press volume up on your phone to confirm
7) Allow USB debugging again
Since your phone has done a factory reset you have to run through step 4 again to continue to run the debugging tools
8) Install custom TWRP recovery
Download a version of TWRP that works with Android 10, and put a copy in your platform-tools folder. I used twrp-3.5.0-10.0.img. Reboot into fastboot from the Command Line:
Code:
>adb reboot bootloader
Once the screen turns on with ‘Fastboot mode’ at the bottom, run:
Code:
>fastboot flash recovery twrp-3.5.0-10.0-GS290.img
If your PC reports all OK, then:
Code:
>fastboot reboot recovery
Your phone should reboot into TWRP.
9) Remove device check from ZIP
This is to get around Error 3004. Unzip your VollaOS package on your PC and find this file:
Code:
volla-10.0\META-INF\com\google\android\updater-script
Remove the following line and resave the file:
Code:
(!less_than_int(1651017058, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Tue Apr 26 23:50:58 UTC 2022) over newer build (" + getprop("ro.build.date") + ").");
Re-zip and then copy altered file onto a FAT32 formatted USB-C drive
10) Sideload OS from TWRP
Connect your USB Drive to your phone. Press ‘Install’ and choose your ZIP file on your USB.
11) Reboot the system from TWRP
When you reboot your phone it will prompt you to wipe your phone again because of corrupted files, but it should behave normally after that.
Note about TWRP: I tried for days to get TWRP to stay installed on the phone permanently, but it was always overridden by the Android 10 stock recovery when the system rebooted. I believe the way to circumvent this is to remove or rename the file /system/recovery-from-boot.p, but I couldn’t figure out how to get root permissions to alter this. One should be able to do this from TWRP, but the file remained hidden, nor did TWRP alter the ROM files as it was supposed to keep it installed. It’s annoying I can’t get it to stick, but I can load it again using step 8. Also, ‘fastboot boot twrp.img’ doesn’t work as it should either.