Update: I have just created a V2. Why, because i plugged back my awox striimstick and found it very slow and outdated. So I created a V2 with a new launcher, and remove a lot of crap and freed up memory.
To sum up, if you need to get close to stock ROM use V1, (there is some draw back and some modification to do to get back the internal SDcard (Modify /etc/vold.fstab and find the line: "dev_mount sdcard /mnt/sdcard auto /devices/virtual/block/nandk" replace nandk or whatever by nandj then do a mkfs.vfat /dev/block/nandj to format, then reboot)
OR, use the V2, access to everything and very fast rom (fast considering the very old CPU and the 512 Mb of ram). This rom V2 is very usable;
Hi all,.
This is an awox striimstick, hdmi stick.
Please see the recovery method below after download link...
Long story short, a fw restore using allwinnera10 tools went wrong and now i have no way to recover it.
I have no power button or volume key, only a reset button on the back (like the mk802)
If i keep pressing this button while pluggin the usb cable to my computer i should be able to go to the bootloader, but it never works... It only reset all my settings.
For restoring the striimstick:
Link for Firmware V1 (file 460mb) and Firmware V2 (file 607 mb) and tools (Livesuite and phoenix carad writer)
Link: https://drive.google.com/drive/folders/0BwJDxBRQ92xcbU5RWkQ2WXV1UFE?usp=sharing
and the instruction:
- Download and use phoenix card writer to write the output.img or outputv2.img to a micro sd (1Gb microsd should be enough)
- plug micro SD card to the stiimstick (do not plug HDMI, just a Usb cable to your computer)
- Power on (You should see a green light blinking close to the red light)
- Wait 1 real minute
- 1- Remove microSD, 2- unplug the usb cable from your computer
- Plug it back into your computer (Make sure your computer's sound is on so you will here windows saying it is detecting new hardware)
- The stick Should now be in bootloader mode, Windows will detect the hardware and will ask for driver, use the driver from live suite folder\Usb driver
- Use livesuite to flash the file output.img or outputv2.img file (If flashing says 0% and do not start after 1 minute, unplug and plug back the stick one more time, do not touch anything on the computer, the flashing should start automatically in the next 30 seconds)
Unplug the stick and plug the HDMI cable to your TV, Plug back power cable, it should be working
Again this is not super easy, if you do it anyway, do it at your own risk
Fyi (On v1), on this image there is the playstore already installed and it is rooted. This is not the official image as nobody has it. I made this image from a nandroid backup i did previously
Fyi (On v2), on this image there is no google services installed but the rom is rooted and has aptoid lite, facebook lite, cleanMaster and ES File explorer already installed out of the box.
Please hit the thanks button if you donwload the file.
Cheers
Note for V2:
Use the same Recovery method using the SDCARD then Livesuite.
After reboot, use ES file explorer, activate "root"option in it THEN to go to /system/app and reinstall android terminal by clicking on jackpal.androidterm-1.apk (Yon can also use adb shell and type "su" and go to next step).
then Open Android term type su, wait for superSu to popup and autorise it. then type: mkfs.vfat /dev/block/nandj (It will format the internal SDCARD not the MicroSD call EXT-SD) then type reboot.
You will now have the internal SD card accessible in /SDCARD. Your MicroSD card is accessible through /mnt/extsd
Also, as this stick have a little amount of ram, I recommand to use the android Widget "CleanMaster (White theme)" already installed from the laucher (This is the widget below my kid's picture on the launcher). Everytime before starting an app I'm cleaning the RAM using this button from the launcher (See the launcher screenshot below)
I removed everything included google services and google market (Was present in V1) because it uses too much ram and CPU. I replaced it with Aptoid lite, replaced chrome by opera mini, and facebook by facebook lite..
Regarding remote control, if you dont like the hardware remote provided by awox, you can download from google play store on your phone the Awox remote app (striimstick Remote) and use it to remote control your android stick (emulating mouse and keyboard).
The stick is also able to receive DLNA request and it is working pretty well (I send DLNA from my galaxy S6 using bubbleUpnP and it is working well with movies and series.
{
"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"
}
Here another screenshot with the application I used and works well with this stick:
pierrottls31 said:
Hi all, i need help with my device.
This is an awox striimstick, hdmi stick.
Long story short, a fw restore using allwinnera10 tools went wrong and now i have no way to recover it.
I have no power button or volume key, only a reset button on the back (like the mk802)
If i keep pressing this button while pluggin the usb cable to my computer i should be able to go to the bootloader, but it never works... It only reset all my settings.
Im suspecting vendor had setup a different way for recovering this device, like using the usb port or the micro sd port. Any idea of a procédure and the type of file i should use?
To sum up whatever i do, nothing is detected by usb so. I cannot use livesuite or other software to reflash the firmware
Any help/pointers will be greatly appreciated
Cheers
Click to expand...
Click to collapse
All I was able to get back the Livesuite USB device, but any firmware Im flashing is failling and the stick will not boot up.
I made a backup using all winnertool but i have only boot.img, bootloader.img, recovery.img and system.img
but livesuite want only one big firmware image. Any idea how I can gather all those files together in order to fully restore the device?
thank you
pierrottls31 said:
All I was able to get back the Livesuite USB device, but any firmware Im flashing is failling and the stick will not boot up.
I made a backup using all winnertool but i have only boot.img, bootloader.img, recovery.img and system.img
but livesuite want only one big firmware image. Any idea how I can gather all those files together in order to fully restore the device?
thank you
Click to expand...
Click to collapse
1st, I had to do all this because Awox will not release original firmware, so if your device is fu..ed then you need to get the firmware to reflash the device. (You cannot even test alternate firmware as if the stick is not booting, you will not be able to put the stick in bootloader mode, there is no USB connection detected)
Finally found a way to restore the original firmware I did backed up the device using Uberizer and a Phoenix card writer.
Use uberizer to unpack any A13 device image 4.0.1 you can donwload and wait untill it finish.
Take the backup you have made using allwinner tools.exe when the device was still working.
copy the 3 img file to uberizer rom input folder, rename your .img file to .fex file, the from uberizer menu "i" use Repack image.
Then take any 2gb min Microsd card, and using Phoenix card writer, write the uberizer output.img on the sdcard.
Turn off your striimstick, plug the MicroSD Card and plug the power cable on the device.
You should see a blinkin green light close to the red light. When it stop blinking, remove sdcard and Unplug, plug back in the power cable. It should be restored.
If you need I can create and send you a recovery image, just send me a private message.
Hope this will help.
Cheers
Hi Guys,
Is there someone kind enough to send me the original firmware please? I'm having issue with a Flickering HDMi, I would like to reinstall original firmware to make sure this is not software related.
Also if I get the original firmware I will be able to cook a better rom (My rom backup is already messed up). I want to try to go for 4.2 rom , in this case, the stick should be faster.
You can use the application Nandroid backup or any other tool you want.
Your help will be greatly appreciated.
Thanks you
Related
The MoDaCo Mod for MOJO, which adds root and increased Play Store app availability to the MadCatz MOJO, is now available!
The mod takes the form of a Superboot image (as used on many devices previously), with additional features to resolve the Play Store lack-of-apps issue.
What is this?
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
What are the pre-requisites?
You need a MOJO (duh) and a USB Male A-A cable to carry out this process. And a computer I suppose (Windows, Mac or Linux).
Any caveats?
You should note that while rooting may affect your ability to receive future OTAs, reverting back to stock is easy enough. We'll cross that bridge when we come to it.
Download
APPLY THIS AT YOUR OWN RISK!
Superboot MMM³ - DOWNLOAD - MD5: 835de32dd795d2825ade1ed1be422abf
How to use Superboot - Windows, Linux and OSX
Download the Superboot zip file above and extract to a directory
Put your device in bootloader mode - Unplug the power cable and any USB cables (the dongle can stay in), insert the USB Male A-A cable in the port labelled '2.0', then insert the power cable. 'Key driver not found.. Booting OS' will appear on screen.
WINDOWS - install the device drivers from the directory you extracted above if required, then run 'superboot-windows.bat' as Administrator
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by 'sudo ./superboot-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by 'sudo ./superboot-linux.sh'
You will see 'Booting downloaded image' and a black screen, then the screen will return to 'Key driver not found.. Booting OS'. At this point, unplug the USB cable and the power cable, wait a few moments, then reconnect the power cable to boot as normal.
For all the missing apps to show up on the Play Store, you may need to clear data on the Play Store in 'Settings -> Applications' and reboot, then run the Play Store again.
Enjoy!
P
{
"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"
}
Thank you!
Thank you for kicking off true development for the Mojo to move forward. I'll try this as soon as I can and respond.
you rock!
Now I'm off to get dog food! Oh...I mean I'm using that as an excuse to run and get myself a USB cable. You're awesome, paulobrien. I'll root this evening!
There we go!!! What we've all been waiting for!!!
BTW, what are the changes to the Play Store that enable all the apps?
Thanks for this! Now I need an A-A cable...
Ok it's finaly come so happy thanks Paul O'Brien
I don't understand why my pc won't see my mojo there is no sound when i plug into it i try usb 2 and 3 with a usb 3 male male cable
So after i type reboot bootloader the mojo reboot normaly even if i unplug the power etc... and the pc do nothing
Thanks for what you did this is awesome
Mojo goes into fastboot mode and installed drivers fine. However currently running into issue where when I run the superboot-windows.bat file in admin mode it opens cmd for a second then immediately closes. The mojo doesn't seem to respond whatsoever. Any thoughts?
Ya same here mojo say key driver not found... Booting OS but when I run the .bat file doesnt close just sitting waiting for device
buggin0915 said:
Ya same here mojo say key driver not found... Booting OS but when I run the .bat file doesnt close just sitting waiting for device
Click to expand...
Click to collapse
Are running the bat file as an admin? right click>run as admin
ya ran in admin also tried to run adb just to see if i can connect device but nothing. computer is connecting just not the device with adb/fastboot
2 things to try:
1) Run the bat file in an actual command window to see the output, or edit it and add pause at the end (likely device not found or fastboot isn't in the path)
2) Manually force a driver (I believe the fastboot driver from the Android SDK should be able to be forced, since this is just a Tegra 4 chipset)
To ensure its ready to go, you should be able to write:
"fastboot devices"
And see that there is a device there. I will try when I get my cable
Thanks I'll try out more tomorrow.
For me i have to add absolute filepath to script if i run it as admin
if the folder is under C:\ it is: C:\r1-mojo-superboot-mmm\fastboot-windows.exe boot boot.superboot.img
But just telling me "waiting for device". driver is installed properly and device is recognized as usb device.
saenta said:
For me i have to add absolute filepath to script if i run it as admin
if the folder is under C:\ it is: C:\r1-mojo-superboot-mmm\fastboot-windows.exe boot boot.superboot.img
But just telling me "waiting for device". driver is installed properly and device is recognized as usb device.
Click to expand...
Click to collapse
Could you try editing the batch file, replacing 'fastboot boot' with 'fastboot -i 0x0738 boot'? I don't think that should be necessary on Windows (I use a Mac) but it's worth a try!
P
paulobrien said:
Could you try editing the batch file, replacing 'fastboot boot' with 'fastboot -i 0x0738 boot'? I don't think that should be necessary on Windows (I use a Mac) but it's worth a try!
P
Click to expand...
Click to collapse
Perfect thanks that worked!
saenta said:
Perfect thanks that worked!
Click to expand...
Click to collapse
Ah, awesome, i'll update the script in the zip.
P
Hi i'm facing a problem and i see i'm the only one for the moment
i use a usb 3 male male cable but when i plug into the mojo and pc nothing hapens no sound of windows who say there is an usb plug so maybe it's because i use a usb 3 cable ( the cable is pluged into the usb 2 port )
and the other thing it's when i reboot into bootloader the device reboot normaly i don't see "Key driver not found.. Booting OS"
Download updated to r2 (Windows fix).
P
Dead-neM said:
Hi i'm facing a problem and i see i'm the only one for the moment
i use a usb 3 male male cable but when i plug into the mojo and pc nothing hapens no sound of windows who say there is an usb plug so maybe it's because i use a usb 3 cable ( the cable is pluged into the usb 2 port )
and the other thing it's when i reboot into bootloader the device reboot normaly i don't see "Key driver not found.. Booting OS"
Click to expand...
Click to collapse
Have you followed the instructions precisely or are you trying to do it a different way?
P
paulobrien said:
Have you followed the instructions precisely or are you trying to do it a different way?
P
Click to expand...
Click to collapse
Thanks for reply
Yes i think i'm doing it exactly like it's described
I have no problem with my phone and driver but the mojo looks dead with usb slave
Dead-neM said:
Thanks for reply
Yes i think i'm doing it exactly like it's described
I have no problem with my phone and driver but the mojo looks dead with usb slave
Click to expand...
Click to collapse
You won't see it when you plug it in, open device manager you will see fastboot device without driver.
To install the Mojo driver on Windows 8 you need to disable driver signature checking, else install will fail.
Your USB3 cable is backward compatible to USB2.
Have you taken mojo from power? if you only reboot bootloader you won't see anything.
How To Root Galaxy Win or Galaxy Grand Quattro (GT-I8552)
Best viewed in a Web browser. The pictures won't appear as intended in the XDA app.
One of the bit.ly/shortened URLs linked in this guide which directly leads to the download page of the file may be blocked by a security feature. They're all safe. Once you click a link you may be warned by your browser for accessing the URLs, but fortunately, the Warning page has a part where there's an option to proceed with accessing the page, just proceed and click the link. See example below.
bitly suggests that you
Change the original link, and re-shorten with bitly
Close your browser window
Notify the sender of the URL
Or, continue at your own risk to: http://download.clockworkmod.com/drivers/SAMSUNG_USB_Driver_for_Mobile_Phones.exe[/COLOR]
If you get no warnings, much better. Let's proceed.
The Preparation : Before you start, make sure that . . .1) You have a PC / Laptop running Windows Platform
2) Samsung USB Driver for Mobile Phones (click to DL from clockworkmod.com) is installed
3) Phone battery power is at least 70%. That's good enough to not run out of power during this whole process.
4) Its USB Debugging is enabled (Settings > Developer Options > USB Debugging)
5) You have a USB Cable to establish a connection between the phone & your computer
6) You have the files needed. Keep three files in one folder.
- twrp_2.8_material - 9185 KB (click to DL directly from its dev's (Gody) MediaFire drive)
- Odin3-v3.09.zip - 972 KB (click to DL from sammobile.com's MEGA shared cloud storage) This software runs only on Windows platform.
- SuperSU_v1.94.zip - 1,703 KB (click to DL direclty from chainfire website)7) A copy of that flashable zip file "SuperSU" must be saved in your phone's memory, internal or external .
1st Step : Flashing TWRP Recovery Via OdinWhat is Recovery? | The Two Android Recovery Agents (CWM & TWRP)
Here, we will use TWRP Recovery. We will install it on the device using the Odin software.
Required: your phone, Windows PC, USB cable, Odin, and TWRP (.tar file)
1) Boot phone to "Odin Mode, a.k.a. Download Mode" by pressing the buttons at the same time: Volume Down, Power, & Home. When the device vibrates, immediately release the Power button while still pressing the other two until the Download Mode's warning screen appears.
{
"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"
}
2) Press the "Volume Up" button to continue to Odin Mode
3) In your computer, using WinRar or 7-zip, extract the Odin zip file, then run Odin3 v3.09.exe as Administrator
4) Connect your phone to your PC via USB. It should say "Added" on Odin.
5) On Odin, click the "AP" button, find and select the "twrp_2.8_material.tar"
6) Click "Start" to proceed in flashing the TWRP Recovery. *This takes about a minute.
7) It's partially finished when it says RESET! with these three lines in the message box.
RQT_CLOSE !!
RES OK !!
Removed!!
Then, phone will reboot automatically to OS.
8) Sometimes it takes a few more seconds after the phone has rebooted for you to be able to completely close Odin. Just wait for Odin to change its status from RESET! to PASS! and say All threads completed. (succeed 1 / failed 0), as shown in the picture below.
Then, you may click Exit and disconnect cable.
TWRP 2.8.5.0 Recovery is now installed.
And this is how to boot to "Recovery Mode". Press the buttons at the same time: Volume Up, Power, & Home. When the device vibrates, immediately release the Power button while still pressing the other two until the SAMSUNG boot-screen appears. See photo instructions below.
By the way, see the pictures below for the difference between the Galaxy Win's stock recovery and TWRP's recovery.
Important : NANDroid Backup
At this point, with TWRP Recovery installed, you can now create a NANDroid backup. It's a backup of literally everything in your phone - System, Cache, Data, EFS, and Boot. It is considered to be the top priority of things to do before messing with your phone i.e. flashing ROMs, kernels, or apps. After you create a backup, the backup file would be located in "sdcard0/TWRP/BACKUPS/" for internally saved backup, and "extSdCard/TWRP/BACKUPS/" if it's saved to the external memory. This file can also be transferred to a different storage, say a hard-disk, if you need to have more space on your phone for something else. You may skip to the actual rooting part. But, in case you do want to create a backup just follow the simple steps below. 1) Boot phone to Recovery Mode
2) Select Backup
3) This part lets you name the backup file with whatever name you want, choose whether to save it internally or externally, and pick which stuff you'd like to backup. And when you're ready, swipe to backup.
*This may take 5-10 minutes depending on how big your whole current installation is.
4) Once done, you may proceed with the 2nd part of this rooting guide.
2nd & Final Step: Flashing SuperSUSuperSU allows for advanced management of Superuser access rights for all the apps on your device that need root.
Required: your phone, and SuperSU (.zip file)
1) Boot phone to Recovery Mode
2) Select Install
2) Locate the zip file SuperSU
3) Go ahead and swipe to install SuperSU *This takes just 5-10 seconds.
4) Reboot System
You now have root access. Good luck!
Important Reads After Rooting An Android Device:
What Is A Nandroid Backup and How Exactly Does It Work?
TriangleAway – Reset Flash Counter Tool
11 Things To Do After Rooting Your Android Smartphone | RootMyAndroid.Org
Suggested ROM:
COSMIC 2.0 ROM (released 4/27/15) (CM10). Rated to be the most stable custom ROM for the device.
Originally developed for Galaxy Core Duos by dev abhi922, then ported by dev gody420 to work on Grand Quattro.
Hey mate, thanks a lot! Your guide is very clean and objective. Links shown properly. You did a good job!
But I'm still facing a problem on my I-8552B. Whichever Recovery I try to flash, I keep getting a black screen.
I tried the one you posted and the 6.0.3.7 version, but nothing different. :/
Thanks! I'm as glad that this guide is helpful to us who need it.
When does this black screen appear?
What have you done so far?
Sent from my GT-I8552
The phone is working properly, I can boot into the system normally. But after I flash any custom recovery via Odin (all I tried, so far), and boot into recovery (phone off, VOL +, Home and PWR boot), I get a black screen.
I've read that people are getting this issue on devices bought after July/14...
Please refer to this thread for more ideas.
http://forum.xda-developers.com/showthread.php?t=2977978
Best of luck!
Sent from my GT-I8552
Hi. .when my galaxy win was rooted, the task manager was deleted. Is there a way to recover it plz. .tnx
Sent from my GT-I8552 using XDA Free mobile app
[Root ,Easy ,Fast No Pc! ]
:angel:Visit the link: http://forum.xda-developers.com/grand-quattro/general/root-grand-quattro-win-duos-t3091676
Good Share
Thanks for clear share;
1- Odin3-v3.09.zip link dead
2- I download the v3.07 and It works only AP = PDA
3-I like the TWRP screen
Thanks again
i'm too having the same problem..after flashing custom recovery, the screen goes black when i try to enter recovery mode
Samsung Galaxy Win GT-I8552B
Excellent tutorial, but I could not install SuperSU, my phone model is
Samsung Galaxy Win GT-I8552B
Version: 4.1.2
Can you help me?
Best regards
Roosevelt Paz Garcia
I am stuck at 'starting adb sideload features' in adb sideload. Please suggest what to do?
I am not getting the install option on the recovery boot
someone help plz
No need to unlock bootloader for samsung ???
Is it??
Hey All
Its been a while since I got to play with anything these days but I recently found one of these POS 10in touchscreen units in the dumpster and it fires up into a menu running android. So I was hoping I could reflash this and use it like a tablet given it's also got a small thermal printer in it, so maybe try and save it from e-waste
I searched online for more details and came across this HERE which is identical to what I have so hoping I can root it and flash it with a clean android?
I would love to repurposed this to use as a touch screen tablet or similar, since it's got a GSM module and can take an SDCard too as I opened it up and took some pictures and I managed to get it in a recovery mode as well - from the PIX its using a rockchip RK3368
{
"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"
}
I am not sure if the mini usb port is a OTG port to try and use ADB but I have not been able to do much with it and hoping someone can guide me through to possibly a reflash or ways to unlook root and add in another bootloader/rom
I've downloaded the files from citaq website but so far not been successful to do much with it, has anyone played with these and turned them into something more practical for the home?
Here's hoping for some tips - Apology if this is in the wrong section, move as needed :good:
Cheers
Kosti
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
jwoegerbauer said:
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
Click to expand...
Click to collapse
Hey, Thanks for chiming in!
So in order to get ADB and or Fastboot its suggested to enable USB debugging in the device system settings, but I am not sure on how to do this, would it be safe to assume this is already USB debug is already enabled?
Could I back up the original stock recovery
I'm a little green on the whole process hence looking thought I'd ask here, I don't think I even have an OTG cable handy
I will see if I can load ADB on a windows box and try and talk to this unit
Cheers
Kosti
@Kostiz
An OTG-cable isn't needed, because the recovery menu
doesn't give you the opportunity to load something from an USB-device
OK, some success!
I went back and connected a mini USB straight to the PC and ADB driver installed detected the android device.
Ran ADB in windows powershell
So whats the best method to backup the entire ROM, and recovery files in the event I stuff this up?
Do I use just ADB for this or someother tools?
I did try one tool here from the vendors website but stuck as not sure what the Chinese characters mean..
Is the fact that this is only 1G i couldn't run Android at all and needs to be stripped down?
Cheers
Kosti
@Kostiz
Android Oreo Go Edition is a lightweight distribution of Android that runs better than normal Android on devices with <= 1 GB of RAM
How to backup device's Stock ROM is eplained here.
Thanks again mate!
Seem I have to do a lot of reading and thankfully everything is here, just got to spend time to read and have a go!
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
BTW, the current ROM installed boots into a special menu, all other settings are hidden, would there be a way to enable seeing all the items and when getting the the settings (gear icon) that pops up in the corner, only takes me to the standard wifi menu to choose a wifi, so it seems everything else is hidden, if by enabling these I could potentially not need to do anything other than stop the default application from starting up - if that makes any sense
Could I just get back into a adb shell and try
adb shell
su
pm enable applicationname
I have to read up on rooting first I assume before I do much more, this is getting exciting, LOL :good:
Kostiz said:
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
Click to expand...
Click to collapse
You use Android's HOME button to navigate within the Recovery menu, use POWER button to select option.
Hi, fellas! Please help me with one of these Citaq H10 POS. All we have is bootloop with some custom ROM showing vendor's logo.
Forcing it into recovery gives me some dead android screen with "No command" text.
Please guide me through this challenge, cause I have no other option but to ressurect it somehow.
Good news is that I have another one that is working fine, so we could try cloning it or something. Please help!
Yet I can't attach pics, cause of few posts, but if needed I can PM some.
citaq h10-2
I am also stuck with this machine citaq h10-2 , i did use a wireless kb to move up/down and not the 2 buttons on the motherboard , i can talk with it with ADB but all you can do is put it in sideload to upload new firmware and put it in fastboot but in fastboot you only get a black screen , what I have don is > opened up developer mode but you have no OEM UNLOCK tick box in side so running any bootloader unlock dose not work and i have run them all, if you google this machine for flashing new firmware you only get XDA this forum, unless any body knows another place to get the info from please let us know as i do think this would make a nice tablet with printer, the firmware is 5.1.1 and would love to put 6.0 or above on it but. i did download some firmware and used sideload to install it but it come up with error , i did try and make a backup but cannot do it ?, I think the firmware was from a galaxy s5 , I am not into all this firmware flashing so I am learning as I go along and if I brick it up well it was for free any way as the takeaway was shutting down and he gave it to me so no loss, if any body knows how we can get 6.0 or above on this machine please let us know.
A big thank you to all that can help put android 6.0 or above on this tablet.
Did you guys take a look at the solution here ? It worked for me ! All with a 2k ohm resistor...
Hola, alguien tiene la Rom de este dispositivo?
Disclaimer
I am not responsible for any damage you made to your device and responsibe for anything else. Do this only if you know what are you doing.
You have been warned
Click to expand...
Click to collapse
Screenshots/Video:
{
"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"
}
Don't be afraid: The latency you see is caused by the non optimization of the refresh rate of the e-ink panel, which I'd like to port from stock cinese rom. (here if you'd like to help to make the e-ink works on android even faster than stock!!).
System UI is very much smoother than on stock rom (try with scrcpy).
Files:
Spoiler
Main Folder https://mega.nz/folder/QkVXUDLS#LWYIHVvuiOFxxeZpWruTlg
Download those files:
- https://mega.nz/file/bR5g0I5I#2kwOj8vpsrOUfu-Fpdj1Yboppx9-ZzTk7t3IS-dpT5E
- https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view
- Hisense_A5_LA592C(HLTE202N)_L1657.6.09.06.00_TFDownload_202004090105_user.zip
- https://drive.google.com/file/d/1WKhek-8iDULzjXKxBtVivhnbUeh8Fw89/view
- https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/27_Jan_2020/system_arm64_ab.zip/download
- https://github.com/topjohnwu/Magisk/releases/download/v22.1/Magisk-v22.1.apk
- https://github.com/KinglyWayne/simg2img_win/archive/refs/heads/master.zip
Instructions:
Spoiler
Bootloader still locked (unfortunately). (or tell me if you managed to unlock )
Android 9 works good.
Android 10 lags.
Before starting: Backup all the data, partitions and most importantly the EFS/QCN file! (Read BACKUP QCN section.)
If you'd like to share a vanilla EFS/QCN file, erasing your IMEI with a blank one before doing it, that would be useful in case someone corrupted his one. You can read more about on the guide.
Make sure to read the Disclaimer above.
- Install QPST and Qualcomm Drivers from Hisense_a5_Flashpaket_6.10.04.00.zip
- Format a microSD into FAT32, then unzip Hisense_A5_LA592C(HLTE202N)_L1657.6.09.06.00_TFDownload_202004090105_user.zip to a folder named HLTE202N_TF and copy it to the microSD. Insert the microSD inside the smartphone.
- Unzip HLTE202N_HLTE202N.R1_L1657.6.03.02.00.7z and replace recovery.img, vbmeta.img, boot.img with those you find inside zip file boot_recovery_vbmeta_6.03.02.zip.
- Enter in EDL MODE by [/I]adb reboot edl[I] or this and connect the device with usb cable to PC.
- open QFIL and select Flat Build, then select Programmer and choose prog_emmc_firehose_8937_ddr_000bf0e1, load XML rawprogram_000bf0e1 and patch patch patch0 from HLTE202N folder.
- Click Download to flash stock ROM 6.03
- Once finished, detach usb cable and reboot the smartphone this way: hold vol up and vol down and power at the same time and as soon as it boot, release only power button until you see vision logo flashing TF
- Wait the smartphone to boot the 6.09 firmware, and once booted, enable USB debugging and OEM unlocking.
- You should see developer options inside the submenu other settings after tapping 7 times on kernel version inside about phone.
- Now check system updates, and OTA update to 6.10.04.00 and no more, just only to build 6.10.04.00.
- After update complete, unzip Hisense_a5_Flashpaket_6.10.04.00.zip
- Open QFIL and select flat build, then select programmer prog_emmc_firehose_8937_ddr_000bf0e1, load XML rawprogram_000bf0e1_joygram and patch patch0 from Hisense_a5_Flashpaket_6.10.04.00/rootkit_6.10.04 folder.
- Enter in EDL MODE and click Download to flash root for ROM 6.10.04.
- Once finished, detach usb cable and to reboot, press power button for at least 20 seconds, or more, to exit EDL mode.
- Once booted up, install Magisk 22.1 and give all permissions, then open it, and click ok if it asks to install additional setup. Phone will reboot.
- Once rebooted, connect the phone via adb to pc and type adb shell
- Once in the adb shell, type su and a popup should appear on the smartphone. Grant permission from smartphone.
Checkpoint
- Once here, you could be ready to flash your desired GSI ROM (I've tested many, and look like only compatibility is with Android 9 and 10. 11/12/13 didn't work on my tests, and android 9 is the smoothest performance wise, while android 10 is not really supported and it lags on system.)
At this point, if you'd like to try out different roms, You need to return to Checkpoint, and follow again the steps below.
Your GSI rom should be arm64 and ab partion. Here you can find a list https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list (look for android 9 and 10 roms)
- Unzip your GSI rom, then rename the unzipped .img file to system.img
- copy system.img file to simg2img directory and double click convert.bat to start the unparsing process. It should make another system file inside same folder, but with .ext4 extension.
- copy the system.ext4 file to another directory.
- Open QFIL and select flat build, then select programmer prog_emmc_firehose_8937_ddr_000bf0e1 from Hisense_a5_Flashpaket_6.10.04.00/rootkit_6.10.04 folder.
- Enter in EDL MODE
- Now go on Tools and Partition Manager
- Popup will open, now right click system partition and select manage partition, then erase, then load image.
- Select the system.ext4 file, and it will start flashing.
- Once done, click close, then close again, and then ok.
- wait 10s and detach cable usb from the pc.
- press power button + volume down for 20s to enter recovery. You might want to try some times. Mine worked like this: as soon you feel the reboot vibration, release the power button but keep holding the volume down button until you see recovery logo. or. if it's still stuck on hisense logo (power on), press power and volume down button for 5 seconds, then release power button while still holding volume down, it should enter recovery.
- Inside recovery, erase all the data.
- Reboot, and wait at least 20 minutes, the phone should boot your GSI rom!
Possible error: If you still see Hisense logo with backlight on, probably your ROM has booted, but somehow it won't show you the main display.
Fix: with https://github.com/Genymobile/scrcpy by pressing the screen, after cable is connected and adb devices command launched, where the adb authorization popup would appear, just try to click "ok", and then scrcpy would allow you to see what's happening. Finish the wizard and you should be able to continue on the smartphone now. Keep in mind you may need to use scrcpy at each reboot, because for some ways, the smartphone boots up showing only Hisense logo, but underlying the system is working.
Projects:- Hisense A5 Port eink display refresh rate modes from chinese to AOSP rom https://forum.xda-developers.com/t/hisense-a5-e-ink-display-modes-port-for-aosp.4497903/
- Hisense A5 adjustable backlight color temperature (Warm to Cold) https://forum.xda-developers.com/t/...lor-temperature-backlight-frontlight.4495045/
- Hisense A5 original EFS/QNC vanilla backup file
https://forum.xda-developers.com/t/hisense-a5-efs-qcn-original-file-backup.4497447/#post-87484995
Hey thanks for getting this far! I wonder if you got any further along? I have an a5 and I would very much like to put a stock rom on
which one recovery do you use ~~where can download it
THANKs
can be taught step by step
Hello,
My phone felt down from the 6th floor through the elevator shaft, ending up really damaged: broken screen (fully black, top left corner partly chipped off) !
Yet, the phone is not completly dead:
- The alarm keeps ringing at each time I have scheduled (several each morning )
- I'm able to switch off the alarm by by swiping left through the bottom of the screen, or by pressing the on/off button
- when I plug phone to my PC (win10) I can hear the bip-bip typical of a device connection, but nothing else happens
- On a PC on which the phone had never been connected, Windows recognised the phone and installed the drivers, but again Windows doesn't ask me what to do with the phone
- bluetooth seems to be working as the phone is seen as available by other devices
I'm trying to find a solution to access some of the data in my phone. Primarily the DCIM folder.
I would like to reboot in fastboot mode, as I believe I may have USB debugging on.
However I don't seem to be able to switch off the phone or reboot it.
Any idea how I could switch off the phone? Enter fastboot.
Do you think I could access the phone screen using an OTG device plugged to my computer screen via HDMI. If yes, which OTG device should I purchase?
Any other idea?
As a last resort, do you think it is possible to fully ripp-off the phone, get the flash drive and mount it somewhere in a tool that could be pluggin via USB?
Surfinette said:
Hello,
My phone felt down from the 6th floor through the elevator shaft, ending up really damaged: broken screen (fully black, top left corner partly chipped off) !
Yet, the phone is not completly dead:
- The alarm keeps ringing at each time I have scheduled (several each morning )
- I'm able to switch off the alarm by by swiping left through the bottom of the screen, or by pressing the on/off button
- when I plug phone to my PC (win10) I can hear the bip-bip typical of a device connection, but nothing else happens
- On a PC on which the phone had never been connected, Windows recognised the phone and installed the drivers, but again Windows doesn't ask me what to do with the phone
- bluetooth seems to be working as the phone is seen as available by other devices
I'm trying to find a solution to access some of the data in my phone. Primarily the DCIM folder.
I would like to reboot in fastboot mode, as I believe I may have USB debugging on.
However I don't seem to be able to switch off the phone or reboot it.
Any idea how I could switch off the phone? Enter fastboot.
Do you think I could access the phone screen using an OTG device plugged to my computer screen via HDMI. If yes, which OTG device should I purchase?
Any other idea?
As a last resort, do you think it is possible to fully ripp-off the phone, get the flash drive and mount it somewhere in a tool that could be pluggin via USB?
Click to expand...
Click to collapse
Look for force reboot butto combination for your phone usually vol up/down + power button
The mounting option works but its quite advanced and you mmay need schematics or guess work lmao
You really don't want fastboot, you want ADB. Did you have ADB enabled before?
When it's connected to your Windows machines what is it showing? MTP (in File Explorer) or ADB?
Don't wait for Windows to ask questions!
Thank you for your help
When I connect my phone to the PC, there is just the connecting sound ("bip bip"), no ADB, no MTP
Since the phone screen is stuck to black, I don't know what's going on on the phone.
When first using the phone one year ago, I had activated ADB and used it to debloat the phone. I never removed ADB myself on the phone, but maybe it was deactivated (i don't know) after a system update. I would love to be able to check whether adb is still activated
When I type > adb devices in power shell with my OP plugged in, there is no device found.
So I believe this ADB option is off for me
Somehow USB debbugging must have been deactived
Also
Force-reboot doesn't seem to work
It may be that you don't have a Windows driver loaded.
Get UsbView.exe
The left pane should change as you disconnect/reconnect the USB cable.
Find the device that appears and disappears, select it, copy the contents of the right pane and post it here.
Renate said:
It may be that you don't have a Windows driver loaded.
Get UsbView.exe
The left pane should change as you disconnect/reconnect the USB cable.
Find the device that appears and disappears, select it, copy the contents of the right pane and post it here.
Click to expand...
Click to collapse
Thanks
Here is the screenshot (sorry my Windows OS is in French).
The new item when I plug my phone is :
[Loc23] DeviceConnected : Composite USB Device
{
"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"
}
Ça ne me dit rien. (It doesn't tell me anything.)
I need the information on the right side when you click on Loc23.
Renate said:
Ça ne me dit rien. (It doesn't tell me anything.)
I need the information on the right side when you click on Loc23.
Click to expand...
Click to collapse
Ha so sorry, still mixing up right and left
OMG, your device is showing as a MIDI interface.
Er, that's not good.
Did you root your device with Magisk? Do you have anything useful on your desktop, boot.img or the Magisk'ed version?
Did you have TWRP recovery or some other?
Renate said:
OMG, your device is showing as a MIDI interface.
Er, that's not good.
Did you root your device with Magisk? Do you have anything useful on your desktop, boot.img or the Magisk'ed version?
Did you have TWRP recovery or some other?
Click to expand...
Click to collapse
No, I've never rooted this device. Never even attempted (with this one), so no Magisk, etc. The only "tweak" I did with it was removing some bloatwares using adb (I did this one year ago, right after purchasing it).
A MIDI interface.... I don't know.... But an alarm clock, for sure
If we're talking about the OnePlus Nord 2, that's a MediaTek.
You could go to a cell phone repair place and let them put in a new screen.
You could buy a screen. You don't need to actually install it. You can just connect it to the old cable and leave it flopping.
I don't think that your device has video out (USB Type C alt mode of DP or HDMI or MHL)
You could pull a copy of your boot image using MTK Client.
You could get someone to give you a boot image or a Magisk'ed image.
A small tweak to the boot image would have it come up as ADB or MTP.
Renate said:
If we're talking about the OnePlus Nord 2, that's a MediaTek.
You could go to a cell phone repair place and let them put in a new screen.
You could buy a screen. You don't need to actually install it. You can just connect it to the old cable and leave it flopping.
I don't think that your device has video out (USB Type C alt mode of DP or HDMI or MHL)
You could pull a copy of your boot image using MTK Client.
You could get someone to give you a boot image or a Magisk'ed image.
A small tweak to the boot image would have it come up as ADB or MTP.
Click to expand...
Click to collapse
Thank you so much for your help.
Changing the screen is not an option, given my phone's current state of destruction... it looks like a miracle the alarm clock still works, and the phone is still responsive to wiping the screen to turn it off
I will have a look at MTK Client, but it may be beyond my skill. Would you have a link to a good tutorial? Also, what would be the "small" tweak needed to the boot image?
They call that format of a phone "candy bar", but that doesn't mean that you should nibble on the corner!
This is the open source (Python) MTK client: https://github.com/bkerler/mtkclient
Hey! Any of you OnePlus Nord2 owners have a boot image to share? A Magisk'ed boot image would be even better.