Database Info

Root and Custom CWM recovery for VSD220

I got the device which is really nice, I rooted the first night, I then updated to version 1.1, lost root as usual but luckily my copy of CWM works fine for both versions 1.0 and 1.1.
If you are familiar doing this with android phones, just follow the same steps.
Use at own Risk
Download both files. Make sure they are complete and the file sizes match.
Save recovery.img to computer, and su.zip to VSD220,
Gain access to adb for your device,
go to terminal or command prompt and type "adb reboot bootloader",
and then enter.
The screen will turn solid black,
in the same terminal type "Fastboot flash recovery recovery.img",
and enter, make sure you are in the same directory as your recovery.img.
The recovery will flash quickly, when complete type "fastboot reboot", enter.
Your device will boot up,
make sure you have Su.zip saved on the VSD220 in the directory /mnt/external_sd/su.zip,
you must have an external sd card inserted,
you can confirm this with root explorer even without root.
In terminal type adb reboot recovery,
you should have a working CWM that will allow you to flash su.zip, and perform a nandroid backup, etc.
If CWM offers to block the stock recovery, accept it.
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
Enjoy Root.
This works for both version 1.0 and 1.1.

Cool, thanks!

Can't seem to get "adb devices" to come up with anything. Using Android Composite ADB Interface for driver, no luck at all.
Any help on which ADB driver to use and where to download appreciated.
sk8tingusmc said:
I got the device which is really nice, I rooted the first night, I then updated to version 1.1, lost root as usual but luckily my copy of CWM works fine for both versions 1.0 and 1.1.
If you are familiar doing this with android phones, just follow the same steps.
Use at own Risk
Download both files. Make sure they are complete and the file sizes match.
Save recovery.img to computer, and su.zip to VSD220,
Gain access to adb for your device,
go to terminal or command prompt and type "adb reboot bootloader",
and then enter.
The screen will turn solid black,
in the same terminal type "Fastboot flash recovery recovery.img",
and enter, make sure you are in the same directory as your recovery.img.
The recovery will flash quickly, when complete type "fastboot reboot", enter.
Your device will boot up,
make sure you have Su.zip saved on the VSD220 in the directory /mnt/external_sd/su.zip,
you must have an external sd card inserted,
you can confirm this with root explorer even without root.
In terminal type adb reboot recovery,
you should have a working CWM that will allow you to flash su.zip, and perform a nandroid backup, etc.
If CWM offers to block the stock recovery, accept it.
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
Enjoy Root.
This works for both version 1.0 and 1.1.
Click to expand...
Click to collapse

admisi said:
Can't seem to get "adb devices" to come up with anything. Using Android Composite ADB Interface for driver, no luck at all.
Any help on which ADB driver to use and where to download appreciated.
Click to expand...
Click to collapse
Sorry, was using outdated adb.
So got adb, flashed recovery.img, recovery flashed ok, rebooted...but now when I adb reboot recovery, it reboots and then stuck on green android with red triangle.
Any advice?

admisi said:
Sorry, was using outdated adb.
So got adb, flashed recovery.img, recovery flashed ok, rebooted...but now when I adb reboot recovery, it reboots and then stuck on green android with red triangle.
Any advice?
Click to expand...
Click to collapse
Ok, I worked it out now. But for others, the problem was that recovery image was being replaced with the original on the command "fasboot reboot".
So instead, immediately after typing "Fastboot flash recovery recovery.img" I typed the following command "fastboot boot recovery.img".....AND only then did I get CWM which allowed me to flash su.zip from SD card.
Thanks for all help. Now that I have root, what changes/tweaks did you make using root?
Is there an optimum dpi to apply and are you overclocking?
Thanks.

Here is a script to reboot recovery mode; from your Android VSD220.
sk8tingusmc said:
I got the device which is really nice, I rooted the first night, I then updated to version 1.1, lost root as usual but luckily my copy of CWM works fine for both versions 1.0 and 1.1.
If you are familiar doing this with android phones, just follow the same steps.
Use at own Risk
Download both files. Make sure they are complete and the file sizes match.
Save recovery.img to computer, and su.zip to VSD220,
Gain access to adb for your device,
go to terminal or command prompt and type "adb reboot bootloader",
and then enter.
The screen will turn solid black,
in the same terminal type "Fastboot flash recovery recovery.img",
and enter, make sure you are in the same directory as your recovery.img.
The recovery will flash quickly, when complete type "fastboot reboot", enter.
Your device will boot up,
make sure you have Su.zip saved on the VSD220 in the directory /mnt/external_sd/su.zip,
you must have an external sd card inserted,
you can confirm this with root explorer even without root.
In terminal type adb reboot recovery,
you should have a working CWM that will allow you to flash su.zip, and perform a nandroid backup, etc.
If CWM offers to block the stock recovery, accept it.
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
Enjoy Root.
This works for both version 1.0 and 1.1.
Click to expand...
Click to collapse
Here is a script to reboot recovery mode; from your Android VSD220.
********* script starts here
#!/system/bin/sh
su
echo -n recovery | busybox dd of= /dev/block/emmc count=1 conv=sync; sync; reboot recovery
********* script ends here
I used Scripter Ver. 1.8 It work find. Don't forget to flash the right recovery.img and install su.zip. If you don't the script won't work.

has anyone gotten this to work lately? The device I'm playing with has 1.3 firmware on it. For some reason, I haven't gotten adb to work on this device in windows, and in ubuntu, I can adb reboot bootloader, and it goes to the black screen, but any fastboot commands, just sits there waiting for device. Any suggestions would be appreciated.

n1gh7m4r3 said:
has anyone gotten this to work lately? The device I'm playing with has 1.3 firmware on it. For some reason, I haven't gotten adb to work on this device in windows, and in ubuntu, I can adb reboot bootloader, and it goes to the black screen, but any fastboot commands, just sits there waiting for device. Any suggestions would be appreciated.
Click to expand...
Click to collapse
I didn't know 1.3 was available. Is this a recent firmware? I checked a couple weeks ago.

Not sure, it's not my monitor, just looking at it for a friend. when I go to about, system update I see vsd220 system update 1.3 device system version : IMM76D.UI23ED02_VSC and same info under server version

Got it sorted out after hunting on google. it does work

problem with adb
Ok so i got the device being recognized on my XP machine. Really did not have to do much. Just pluged it in and everything worked.
On my Windows 7 machine when i plug in the device i only see the MTP installed and then see VSD220 in MY COMPUTER and can browse the files. I do not see it when i "adb devices".
1) USB debugging is on/enabled
2) Both laptops have Eclipse with latest ADB and ADT tools installed
Any suggestions as to what i can do? Anyone can copy over drivers that are working with your win7 machine?

Confirmed Working for Acer DA220HQL (atleast for me)
Thanks to sk8tingusmc for posting the instructions. I followed them as well as the comments below and rewrote the instructions to reflect what worked for me on my Acer DA220HQL Smart Display. Which seems to be about the same device as the Viewsonic VSD220
Use at your own Risk - Acer DA220HQL
1. Download both files from the first Post (Thanks to sk8tingusmc).
Make sure they are complete and the file sizes match.​2. Save "recovery.img" to your computer, and copy su.zip to the Acer DA220HQL to "/mnt/external_sd/su.zip"
3. Press Windows Key + R to open the Command Prompt or Start > Run > cmd > Enter
4. At the Command Prompt change to the Directory with adb.exe in my case "C:\Temp\sdk\platform-tools"
Download SDK from here: http://developer.android.com/sdk/index.html#download and extract in my case to C:\Temp (C:\Temp\sdk, C:\Temp\eclipse, and C:\Temp\SDK Manager.exe)​5. At the Command Prompt type "adb reboot bootloader" and hit enter.
The screen will turn solid black​6. At the Command Prompt Type "Fastboot flash recovery recovery.img" and hit enter.
Make sure you are in the same directory as your recovery.img.
The recovery will flash quickly
C:\Temp\sdk\platform-tools>Fastboot flash recovery recovery.img
sending 'recovery' (5688 KB)...
OKAY [ 0.176s]
writing 'recovery'...
OKAY [ 0.983s]
finished. total time: 1.163s
​7. At the Command Prompt Type "fastboot boot recovery.img" and hit enter.
C:\Temp\sdk\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.173s]
booting...
OKAY [ 0.001s]
finished. total time: 0.178s
Your device will boot up​8. At the Command Prompt Type "adb reboot recovery"
It will enter ClockworkMod Recovery v6.0.2.8 with Touch Support. ​9. Choose ZIP File from SDCard navigate to su.zip and select it by pressing on it.
Scroll all the way down to find ++++Go Back++++ on the SDCard if you entered the wrong Directory.
You may also choose to create a Nandroid Backup if you care to do so.​10. Go Back and select Reboot
11. ROM may Flash stock recovery on boot. Fix? - Yes - Disable recovery Flash
Otherwise you will need to delete or rename /install-recovery.sh and/or /system/recovery-from-boot.p.
​12. View attachment 2062751

Rom Version and work in Linux?
swiss420 said:
Thanks to sk8tingusmc for posting the instructions. I followed them as well as the comments below and rewrote the instructions to reflect what worked for me on my Acer DA220HQL Smart Display. Which seems to be about the same device as the Viewsonic VSD220
Click to expand...
Click to collapse
I was wondering what ROM Version is your DA220HQL on (ES I think?) and will the instructions work in Linux or other *nix like systems?
The main problem I have is that I do not have any drivers so adb in Windows XP will recognize it. It is recognized under Ubuntu 12.04 for me.
Thanks for the info! I am very excited to get this working better than out of the box!

LoveMyAndroid2010 said:
I was wondering what ROM Version is your DA220HQL on (ES I think?) and will the instructions work in Linux or other *nix like systems?
The main problem I have is that I do not have any drivers so adb in Windows XP will recognize it. It is recognized under Ubuntu 12.04 for me.
Thanks for the info! I am very excited to get this working better than out of the box!
Click to expand...
Click to collapse
There are a universal ADB Drivers for Windows.
Universal Naked Driver for example.
http://forum.xda-developers.com/showthread.php?t=1161769
Or the following link which I have no clue about who maintains this site and how secure it is running that Exe. So please check first for yourself before yelling at me. http://adbdriver.com/
Regarding the ROM Version I was on, check the other Thread where I listed them all.

swiss420 said:
There are a universal ADB Drivers for Windows.
Universal Naked Driver for example.
http://forum.xda-developers.com/showthread.php?t=1161769
Or the following link which I have no clue about who maintains this site and how secure it is running that Exe. So please check first for yourself before yelling at me. http://adbdriver.com/
Regarding the ROM Version I was on, check the other Thread where I listed them all.
Click to expand...
Click to collapse
Well I got the ADB driver installed and I can use it! However I tried the root procedure and it failed to root.
When I was in the CW, the one thing it kept giving an error such as cannot mount sdcard. I checked the sdcard and su.zip IS on it, but the recovery could not locate it. I did try using the sideload method and it seemed to work, but when I rebooted and checked for root, it was not successful.
I tried this in both Ubuntu and Windows with the same result. I even performed a factory reset and tried again. And the same thing: no root.
Is there a timing issue with when to enter the commands?
The info on my DA220HQL from about is as follows:
Model number
DA220HQL
Android version
4.0.4
Kernel version
3.0.21-00003-OMAP-Android+
[email protected] #1
SMP PREEMPT Mon May 13 10:06:22 CST 2013
Scaler version
BA0.2A en_PA
Touch driver version
1.1.0509.1
Build number
IMM76D.UI23ED22_ACE​
Thanks for the help!

LoveMyAndroid2010 said:
Well I got the ADB driver installed and I can use it! However I tried the root procedure and it failed to root.
When I was in the CW, the one thing it kept giving an error such as cannot mount sdcard. I checked the sdcard and su.zip IS on it, but the recovery could not locate it. I did try using the sideload method and it seemed to work, but when I rebooted and checked for root, it was not successful.
I tried this in both Ubuntu and Windows with the same result. I even performed a factory reset and tried again. And the same thing: no root.
Is there a timing issue with when to enter the commands?
The info on my DA220HQL from about is as follows:
Model number
DA220HQL
Android version
4.0.4
Kernel version
3.0.21-00003-OMAP-Android+
[email protected] #1
SMP PREEMPT Mon May 13 10:06:22 CST 2013
Scaler version
BA0.2A en_PA
Touch driver version
1.1.0509.1
Build number
IMM76D.UI23ED22_ACE​Thanks for the help!
Click to expand...
Click to collapse
So you were able to load CW but when you select "Choose from SDCard" it could not find su.zip? Or did you try to Mount your SDCard? Regarding the ADB Commands you can take as much time as you want. Have you used CW before?

swiss420 said:
So you were able to load CW but when you select "Choose from SDCard" it could not find su.zip? Or did you try to Mount your SDCard? Regarding the ADB Commands you can take as much time as you want. Have you used CW before?
Click to expand...
Click to collapse
I did try to mount the sdcard, but I got an error that said it could not mount the sdcard. That is when I tried the sideload method. When I boot up normally, the sdcard is there along with su.zip. I posted the info on my DA220HQL noting the kernel version. I went back to the post where you stated your kernel version. They are different. Mine is later than yours.
After going through everything several times, I though maybe I was doing something wrong. We went out of town so this is the first time I could sit down and check out the posts.
Thanks for your help in advance.

Thanks for all the help. I could not get this to root so we are sending it back to HSN. As a last ditch effort, I did a factory reset and tried again. And I got the same result. I do not think that the recovery while booted was able to "see" the device's partition at all, which is why I got the mount errors. In any case, I also have found that we can find it online for much less than what HSN charged us for it. I am still curious if anyone else was able to root this little gem.
Keep posting updates!

im getting the same issue
cwm is not mounting my sdcard
android is recognizing it, but not in recovery
I'm thinking I shouldn't have installed that update
there are a bunch of errors in recovery when starting
E:Can't open /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (No such file or directory)
E:Can't mount /cache/recovery/command
E:Can't open /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't open /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (No such file or directory)
my best guess is we need a different recovery img, even though acer is the same as viewsonic
also there is no prompt to disable stock recovery being reinstalled
recovery touch is also kind of wack, have to tap below whatever I want to pick (which is also not consistent horizontally)
edit: going back to recovery, under mounts and storage, it doesn't appear to have permission to mount anything

looks like viewsonic released a rooted ROM on their support site
http://www.viewsoniceurope.com/uk/support/downloads/drivers/?prod_name=vsd220
But yeah...Acer hasnt
Perhaps this should get the ball rolling? It's funny how the US site doesn't have that
edit: wow looks like they even provided flashing tools and instructions...I just hope that this doesn't brick my unit (since its Acer not Viewsonic)...anyone else willing to give it a try?

stuck with bootloop and no alternative rom

i have a slight problem. i grabbed the ubuntu touch alpha and went in to recovery, loaded it (according to thread instructions) but ended up with a bootloop.
in the end i thought "lets just put another rom back on for now" and then realised i had deleted the other rom from the sdcard! so i'm stuck with it not booting in to ubuntu, and not able to get another rom on as it doesn't boot in.
can i connect to the internal sdcard area myself by plugging the usb in to the pc or something?
i have twrp loaded as recovery
thanks

ah, TWRP adb sideload to the rescue!

problem
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found

partti86 said:
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found
Click to expand...
Click to collapse
The issue, Superwipe wipes the internal /sdcard/ and also this is where it flashes from.
You need to boot to recovery and then use ADB to push files to the sdcard.
If you have never used ADB, it can be a bit daunting.
First, you need adb from the Android SDK. It is a big file for the few you need. I have a copy of the relevant ADB files here: https://db.tt/b9dQ6xzp
Unzip this to c:\adb folder on windows. If you are using Linux, it should already have adb in the /usr/bin/ folder.
Next, you need the Universal Naked Drivers: http://forum.xda-developers.com/attachment.php?attachmentid=1934814&d=1367674531
Unzip these to c:\universal_naked_drivers
Boot to CWM and then plug in your USB cable. It should show a new device found. It may find 2, an MTP and then there should be another either Unknown device or an Android ADB device. Right click and update the driver. Be sure to search for driver, then tell it you want to pick from a list. Hit the Have Disk button and then hit the browse button and browse to c:\universal_naked_drivers and hit OK. It should show you a driver to select and hit OK. If you are using Win 8, there is an additional step that is required to used non-signed drivers.
Once the driver is updated, download the zip file you want to flash on your PC. I assume it is a ROM.zip file for this example. Place this file in the c:\adb folder and call it ROM.zip (can be named something else, but this is what we will use for this example).
Now, open a command prompt and execute the following:
Code:
> [B]c:[/B]
c:\> [B]cd c:\adb[/B]
c:\adb> [B]adb devices[/B]
It will probably say some messages about the daemon is not running, restarting adb.
Then it should show a list. There should be some numbers followed by "recovery"
If no devices are shown, check that your ADB device is showing in the Device Manager.
Once you see it in the adb devices list, continue:
Code:
c:\adb> [B]adb push ROM.zip /sdcard/[/B]
successfully pushed xxx bytes
c:\adb>
At this point you should now see the ROM.zip file on the internal storage in CWM to allow you to install it.
Choose to install the file then reboot (not to recovery). You have to let it flash the file (progress bar will show). Once the screen goes black and the progress bar disappears, it should now boot to your ROM..
If your ROM requires a custom kernel and/or GAPPS to be flashed, use the same procedure to push your kernel.zip and GAPPS.zip to the /sdcard/ directory.

mk2media said:
ah, TWRP adb sideload to the rescue!
Click to expand...
Click to collapse
Can you explain what you did please? what is adb sideload?

[Request] EMMC backup of G6-U10 (tutorials included)

Hi, my G6-U10 is hard bricked and has gone to QDLoader 9008 mode so i cant go to recovery, fastboot,adb mode .
i need EMMC image of a similare device (G6-U10) so i can fix it following instructions in this thread .
i dont need whole EMMC image, just first 100-200 MB .
to extract EMMC, you need to be on stock rom with root access.
to do so:
1. Enable "USB debugging" in "Developer Options". then connect your device to Windows PC.
2. download and extract ADB. then run the following command through CMD:
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/EMMC.img bs=100m count=1
note that you must enter each row separately and confirm the dialogs appeared on your device screen to grant root and adb access for pc. the option bs=100m mean that the dd command will only extract first 100MB of EMMC. and FYI, this file is only backup from system partition, not from any private files, no need to worry.
the extracted file will be in internal SD, named EMMC.img , compress it in ZIP or RAR so it will have much less size, then send it here to solve many people's problems. anybody does that, i'll appreciate.
Thanks for reading.
Credits and references:
@majdinj http://forum.xda-developers.com/showthread.php?t=2450045
@Jimmyz0r http://forum.xda-developers.com/yureka/help/guide-unbrick-hard-bricked-yureka-t3303112
@tirta.agung http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
http://linoxide.com/linux-command/linux-dd-command-create-1gb-file/
http://unix.stackexchange.com/questions/134299/dd-bs-count-seek

https://yadi.sk/d/wtaBNFaUraZyg

washichi said:
https://yadi.sk/d/wtaBNFaUraZyg
Click to expand...
Click to collapse
Thanks bro, but it's just 100bytes, not 100Mbytes. i think you used bs=100 instead of bs=100m
please consider reuploading , you are my saviour

info on the progress:
I got EMMC image thanks to @washichi :good: (download it from attachments).
then i could finally wake my device up, in the fastboot and recovery, following instructions in this thread(first post).
i can go into Fastboot mode but though i had unlocked bootloader (before), but i can only flash recovery, system(partly) and boot partitions. other partitions give me error ((Remote: Not Allowed)).
the only recovery that i could go into, was the latest TWRP 3 . in recovery i can even connect my device in MTP mode to pc and see files on the internal SD! but i was not successful with flashing roms, it always gives me error mounting cache, system, data. ADB mode is also accessible, used adb sideload to flash rom, but it didnt worked too!
i think part of internal SD is damaged and need to be fixed somehow. still havent found out how.
so, for guys who are having problems similar to me or "Internal Storage Damaged blah blah" i recommend trying to follow these steps to see if their internal SD is still flashable or not:
1. Download an official Rom for your device and unpack it using HuaweiUpdateExtractor.
2. download and extract latest (at least 1.0.32) fastboot in the same folder as extracted huawei IMG files are (Gush bless me! there's too much grammatical erros in my texts )
3. connect your device in fastboot mode (instructions above).
4. go to the directory where all extracted files place. Hold shift and right click on empty space, chose "Open command window here".
Note: you must have an unlocked bootloader to be able to continue, type this command to see if its unlocked:
Code:
fastboot oem get-bootinfo
if you're unlocked, then continue reading, if not, i dont think there is a way to find unlock key for your device.even DC unlocker cant recognize your device in fastboot and adb.
5. now that you know you have an unlocked BL, type these commands one bye one:
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash aboot aboot.img
fastboot flash tz tz.img
fastboot flash userdata userdata.img
fastboot flash [COLOR="RoyalBlue"]XXX [/COLOR][COLOR="SeaGreen"]XXX[/COLOR].img
as i said before, i could only flash 3 partitions with success. but if you where able to flash all parts with success, your extremely have a chance to revive your device. at last, type fastboot reboot to see if you boot up successfully, if not, you will go again in fastboot mode or recovery mode.
for me, default recovery mode just freezes, so i flashed TWRP 3 instead of default recovery. you can try that too.
one more thing: you might not be successful to reboot into recovery, you must restart until you succeed. if you stuck in freezed recovery, open the device back, unscrew the little steel plate (it has 2 screws) and dettach the battery cord, wait 3 secs, re-attach it. i have done it more than 300 times now i dont even know where is the steel plate
FYI, EMMC image in the attachment is for G6-U10 only and probably will not work for other G6 models. if you want G6-L11 emmc, i can share it for you.
if anything was not clear for you, ask me.

@bugggmenot Everytime i insert the sd card and try to enter fastboot mode by holding the Volume+, the PC keeps beeping and refreshing the device manager, tho i can't see any hardware detected. The phone isn't recognizable as fastboot device and the LED is lighting in a blue color.
Any ideas?

Sashko98 said:
@bugggmenot Everytime i insert the sd card and try to enter fastboot mode by holding the Volume+, the PC keeps beeping and refreshing the device manager, tho i can't see any hardware detected. The phone isn't recognizable as fastboot device and the LED is lighting in a blue color.
Any ideas?
Click to expand...
Click to collapse
Do as follows:
1. detach the battery and retach it again.
2. connect the device to pc WITHOUT holding any buttons.
3. if you go into fastboot mode, you will see a blue "Fastboot mode" in middle of texts (and Blue LED).
4. type in cmd: fastboot devices
if your device is listed, you are good to go for flashing procedure.
oh and one more important thing: install fastboot and adb drivers. it's a global driver not device specific, so install any you van find ( sorry I can't Google it for you right now).

bugggmenot said:
Do as follows:
1. detach the battery and retach it again.
2. connect the device to pc WITHOUT holding any buttons.
3. if you go into fastboot mode, you will see a blue "Fastboot mode" in middle of texts (and Blue LED).
4. type in cmd: fastboot devices
if your device is listed, you are good to go for flashing procedure.
oh and one more important thing: install fastboot and adb drivers. it's a global driver not device specific, so install any you van find ( sorry I can't Google it for you right now).
Click to expand...
Click to collapse
Did everything still doesn't want to boot in fastboot mode.
Edit: I made it to the fastboot, thank you very much.

Sashko98 said:
Did everything still doesn't want to boot in fastboot mode.
Edit: I made it to the fastboot, thank you very much.
Click to expand...
Click to collapse
Happy to hear that. would be great if you share your way of success and your current progress on reviving the device. it might help many people.

bugggmenot said:
Happy to hear that. would be great if you share your way of success and your current progress on reviving the device. it might help many people.
Click to expand...
Click to collapse
I got it to the progress you did. Was able to flash only boot.img recovery.img and like 950MB of system.img. Yet smth makes me to think that everything i do flash is being flashed in the SDcard memory not in the internal one, is it supposed to be like that?
Edit1: Tried to flash an update.zip which i made by using huawei tools extractor from the stock recovery but the verification aborted the update. Tried with CWM by using adb sideload but there was some error while sending, also tried with TWRP which seems to erase its memory everytime when i restart the phone, the adb sideload doesnt work and couldn't found the flashable zip after i pushed it in by using adb

Sashko98 said:
I got it to the progress you did. Was able to flash only boot.img recovery.img and like 950MB of system.img. Yet smth makes me to think that everything i do flash is being flashed in the SDcard memory not in the internal one, is it supposed to be like that?
Click to expand...
Click to collapse
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...

bugggmenot said:
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
Click to expand...
Click to collapse
Well i did try flashing img files via TWRP but it allows me to modify just recovery or boot partition. Tried also making flashable zip of the partition to run it from CWM but i get stuck.
I also tried
Code:
fastboot flashing unlock_critical
and
Code:
flashing unlock
but i recieve 3 dots, maybe i should be more patient next time to see what will happen.
===========================================================================
@bugggmenot i've found the file for G6-C00 for qualcomm bootloader platform. Will they work on G6-U10???

Sashko98 said:
Well i did try flashing img files via TWRP but it allows me to modify just recovery or boot partition. Tried also making flashable zip of the partition to run it from CWM but i get stuck.
I also tried
Code:
fastboot flashing unlock_critical
and
Code:
flashing unlock
but i recieve 3 dots, maybe i should be more patient next time to see what will happen.
===========================================================================
@bugggmenot i've found the file for G6-C00 for qualcomm bootloader platform. Will they work on G6-U10???
Click to expand...
Click to collapse
Greate! i dont know if they are similar or not but who cares, i'll give it a shot! please share files here i'll try and report back.

bugggmenot said:
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
Click to expand...
Click to collapse
Why not try to repartition your device?
You can you the parted binary (google will find it) and put it on your /sdcard or / (the root folder). NOT your internald memory or any other partition thats your EMMC.
Now umount ALL partitions in recovery, except for the external sdcard. Go to the commandline in the recovery and cd to the parted binary. Now typ 'parted /dev/block/mmcblk0'.
Type 'print' to see your partition table.
You can now modify your partition table (only ext2 and fat32 partitions support, BUT you can format it whit your recovery soo it will be ext4. (Dont check RM format in settings!).
Hope this will fix the flashing problem.

Hard Brick
Hello guys, i don't know if this is the right place, but do you know how to unbrick Huawei Y550 - L03 from hard brick? My pc recognizes it in the device manager just as Android adapter PCUI (COM10) but the device itself doesn't show.
Thank you in advance if you can help me please. :crying:

Here i put EMMC for G6-L11 for people who need it:

Hello, can you explain how you made it from dead phone QDLoader 9008 to recovery?

bugggmenot said:
Here i put EMMC for G6-L11 for people who need it:
Click to expand...
Click to collapse
We should use the Yureka tutorial with this file to bring the G6-L11 to life right?

henrucci said:
We should use the Yureka tutorial with this file to bring the G6-L11 to life right?
Click to expand...
Click to collapse
only if your phone is G6-L11, then the answer is yes.

Win32disk killed for good all sdcards with g6-l11 image

delete don't work

Thread Closed Per OP Request
Don't work,
I give up
Thanks in advanced. All comments can help!

I have a tablet I can depure via USB and where I can root the tablet. But if I connect to the internet, the "registration and password" of university program enters and is saved (even after formatting it is stuck on this screen) blocking the tablet, I believe that after the internet loads, it installs this locking program ... What would be the name of this type of application? I'd like to know, how remove this app, to If connect in internet, we can block (and try install TWRP via internet with TWRP Management)...

C.Modica said:
Hello everyone !
I've been trying to resolve this issue for weeks. I have a tablet that I can't unlock (it's super hard, it's like Dark Souls of tablets). Well let's start.
He has a program that blocks asking for password and user (this a old from a university), where you request access via wireless or 2G/3G. without it you can't access it, so I believe I have to change his firmware instaled in, but I'm having a hard time to make it.
• Let's go to basic product information:
The chip is a RK3066 (same from TV BOX based on rockchip).
The model is YPY L1050 from POSITIVO (it's from Brazil).
- Software and Items
I have the drivers installed (correctly);
I have adb installed;
I have SD_Card;
I have acess from PC;
The tablet is unroot;
• Back to the items:
So, the good news is that I have the same tablet model, unlocked (with another type of ROM that I am unaware of). That works normally, without problems. Well, I saw a procedure that basically it is possible to extract this image from the good tablet, to the locked tablet. I did that, I ended up extracting a series of .img files from the unlocked tablet: boot, cache, kernel, system, etc... ok.
• Trying a extract from unlock same tablet:
I try transfer the copied files from "good unlock tablet" (extrated with AndroidTool), and put in (with the same tool) in the lock tablet... There is a problem, even before starting the operation, I have the error "Test Device Fail ", in the last is not possible to transfer files via USB (I can only do commands like" ResetDevice ", or export the images from the blocked tablet via AndroidTool... and yes I have the drivers instaled, commands like adb sideloader in the fastboot works).
• Trying a firmware found in internet:
Well, I tryed to download the firmware found on the internet corresponding to the device model, but unfortunately I have the same error as above. I download the .img firware original and using the RKBatchTool and have the same error (the operation don't start, give "Test Device Fail" in "Upgrade" and "Restore").
I believe that both operations do not accept transferring via USB.
PS: The tablet unlocked the command of "TestDevice" works fine.
• What I was thinking of doing:
1 - I think I need to take the all .img(s) files extracted from the unlocked device, put it in a single image (.img), put it in a SD_Card and in the "fastboot" take the option "update rkimage from external storage". But I don't know how to do this. (I try search for it);
2 - Somehow being able to do "apply update from external storage", maybe doing the same procedure above with an "update.img", but I also don't know how to do that (put all img. files together in the form of a one update.img).
3 - Have anothers options, like "apply update from ADB", the PC response this conection with tablet, (I can see the device with ''adb device'' cmds in sideload mode in PC). The problem is that I don't know how I'm going to send the .img file, if I send it inside a .zip (I even tried that, send all the .img files inside a .zip to see if it works. The tablet arrives to read the files but in the end the operation aborts). So my knowledge is lacking in this part.
4 - Another would be such a "ROM Dump." I'd like to do a "ROM dump" with an SD card, I even researched it on the internet but I didn't find this procedure to rockchip (only for Amlogic).
With SD Card:
There was a youtube that managed to unlock a tablet like that, but it was a previous model that I'd like to unlock (and different version of firmware, android etc). His method was to put a bootable sd_card, but he doesn't explain how he does it (he only gives the file done) and looking at the files internally, I just think they were converted to linux formats (system.tar.gz, userdata.tar.gz, some .sh .so files, and a bootenv.img, uImage etc) and with completely different names from .img... It is a pity that it is not for my Tablet model .
Well, that's it in the end, I need to change the firmware and I don't know how to do it.
PS: I tried other operations/methods as well, but I will not comment so that this post doesn't get big.
Thanks in advanced. All comments can help!
Click to expand...
Click to collapse
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.

C.Modica said:
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
Click to expand...
Click to collapse
It isn't going to work via adb unless the device is rooted and then it won't be via adb sideload, it would be done by using dd commands to dd the .img files directly to their partitions.
Sent from my SM-S767VL using Tapatalk

I just found a solution. It requires some tinkering, though.
I had to use a machine running windows 7, because that's the only OS that the drivers worked.
Download the firmware for the Ypy L1050F here: https://www.stockrom.net/2018/07/l1050.html
It comes with the drivers, the ROM, and a tool called RKBatchtool 1.8
You'll have to decompress everything, open RKBatchtool and choose the firmware that is in the ROM folder (Not the DEMO one).
Now comes the tricky part: You gotta undo the 3 screws aroud the tablet, then pry it open with your fingers(remember to remove microSD and SIM first, to avoid breaking stuff!). I recommend startind by the side with the usb, hdmi and power ports to get some leverage. The back cover should pop right off. Then you have to locate the NAND chip in it. Should be a Micron one with 48 pins. The small circle at one of the corners of the chip represents pin 1. Plug your usb cable to the tablet. With the tablet TURNED OFF, use a SIM removal tool or very fine tip metallic screwdriver to short pins 17 and 18 on the NAND chip and plug the power jack into the tablet. RKBatchtool should show that a device was connected. You can release the screwdriver now and just click the "Upgrade" button in RKBatchtool. Now this is very important: DO NOT UNPLUG your tablet until everything is done. It'll tell you when it's done uploading the firmware and checking it. Enjoy your new usable tablet!
I scoured the internet and found this procedure being used for TV Boxes with the same RK3066 SoC. AFAIK, nobody else managed to do it so far, so spread the word.

You are awesome. Broke the internet! I will follow your procedures to try to unlock it. Many thanks again xmas for you.
[edit] don't work

"Cannot load Android system" after failed update - HELP!

My Android phone (Motorola Edge) can no longer start properly after a failed system update. The message I get is: "Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device."
I've tried restarting it in recovery mode which didn't work. I've read that I may be able to install some software via USB and rescue the system but I have no idea how that's done. I've looked at some different rescue software such as Rescue and Smart Assistant (which would only let me rescue the phone which will erase all data) and Dr.Fone but the reviews aren't convincing and the unofficial software programs generally don't support Motorola phones. Does anyone know how to fix my phone without losing my data?? Any help is much appreciated.
Also; I'm in no way a developer so I need everything explained to me like I'm 12 years old.

hi, kid welcome to xda.
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.

[email protected] said:
hi, kid welcome to xda.
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
Click to expand...
Click to collapse
Thank you so much for your input. Unfortunately I can't make it work. When I type 'adb devices', I get this text:
List of devices attached
ZY227HQ2BX sideload
I've attached more info. Not sure if this has something to do with "USB debugging"?

all things right,
that sideload appears because you have stock recovery {no need to worry}
you don't need to erase system, (it is like optional)
and the error ANDROID_PRODUCT_OUT....... is because as i said earlier you have to copy the path of the file not file name.
how to copy path of the file ?
well, simple on windows, open the folder in which system file is present. and again open command prompt type (remember to be in fastboot mode in mobile phone)
fastboot flash {drag and drop system file from folder to command prompt}.
it should look like (but not the same, it is an example)
fastboot flash E:/newfolder/nexus/files/system.img
tell me if you face any problem (also include screenshots like you did, great right?)

What file is the system file in this folder?

[email protected] said:
all things right,
that sideload appears because you have stock recovery {no need to worry}
you don't need to erase system, (it is like optional)
and the error ANDROID_PRODUCT_OUT....... is because as i said earlier you have to copy the path of the file not file name.
how to copy path of the file ?
well, simple on windows, open the folder in which system file is present. and again open command prompt type (remember to be in fastboot mode in mobile phone)
fastboot flash {drag and drop system file from folder to command prompt}.
it should look like (but not the same, it is an example)
fastboot flash E:/newfolder/nexus/files/system.img
tell me if you face any problem (also include screenshots like you did, great right?)
Click to expand...
Click to collapse
Hi again, I've spent all weekend trying to figure it out but so far no luck.
I don't know where to find the system file in the folder I downloader (see attached photo in my reply above this). I also tried making a service-batfile with guidance from YouTube but it seems my phone is locked so it doesn't work.

well sorry i was quite busy so i was not able to reply.
first thing first do you need your data
if so boot into twrp. find twrp image for your phone then use command in fastbootmode
fastboot boot and drag and drop twrp file.
after successfully booting into twrp use option to backup and backup your data in any external storage like sd card.
after that run flash all.bat inside your downloaded folder.
i will completely wipe and reinstall your firmware.
then after it again in fastboot mode boot into twrp and restore your backup that's it.

[email protected] said:
well sorry i was quite busy so i was not able to reply.
first thing first do you need your data
if so boot into twrp. find twrp image for your phone then use command in fastbootmode
fastboot boot and drag and drop twrp file.
after successfully booting into twrp use option to backup and backup your data in any external storage like sd card.
after that run flash all.bat inside your downloaded folder.
i will completely wipe and reinstall your firmware.
then after it again in fastboot mode boot into twrp and restore your backup that's it.
Click to expand...
Click to collapse
I tried doing it but no success (I really want to keep my data). See attached photo

bro first try fastboot oem unlock then try this command
note. if some pop up ask to click ok in phone click to conform unlocking phone to flash other files (twrp)

[email protected] said:
bro first try fastboot oem unlock then try this command
note. if some pop up ask to click ok in phone click to conform unlocking phone to flash other files (twrp)
Click to expand...
Click to collapse
I get this message:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
finished. total time: 0.061s
Will unlocking the device delete my data?

SirOinksalot said:
I get this message:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
finished. total time: 0.061s
Will unlocking the device delete my data?
Click to expand...
Click to collapse
try some windows app to recover it.
sorry unocking will delete data

[email protected] said:
try some windows app to recover it.
sorry unocking will delete data
Click to expand...
Click to collapse
What about your original suggestions - will they not work on a locked device? Fx this:
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.

SirOinksalot said:
What about your original suggestions - will they not work on a locked device? Fx this:
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
Click to expand...
Click to collapse
it will work but need to be modified as your frimware is different i mean hybrid which does not contain system image.
try to clear caches using fastboot : fastboot clear cache
and try to reboot hope it will work. acctuly i have exams so i am a quite busy now a days sorry

SirOinksalot said:
What about your original suggestions - will they not work on a locked device? Fx this:
now about your problem, it is very simple.
1) download latest firmware according to your country.
2) boot the phone into recovery mode.
3) if you have windows on pc then install minimal adb and fast boot from this Link
4) connect your phone to pc using adb cable ( the cable in charger )
5)open command prompt type adb devices
6) if you see any thing like 213547448882 recovery ( recovery should be displayed)
7) type adb reboot bootloader
secondly unzip the downloaded firmware you will see many files with .img extension
8) type fastboot erase system
9) type fastboot flash system <----- here don't type system rather drag and drop file in cmd for location of file
10) if result is success then you must boot normally without data lose.
Click to expand...
Click to collapse
How did you resolve your issue ?

[email protected] said:
it will work but need to be modified as your frimware is different i mean hybrid which does not contain system image.
try to clear caches using fastboot : fastboot clear cache
and try to reboot hope it will work. acctuly i have exams so i am a quite busy now a days sorry
Click to expand...
Click to collapse
Hello buddy,hope your exams are over and you passed them all with wonderful grades!
I am facving the similar problem and unable to find a solution.Would you mind having a look at this ? Thank you!