Yesterday I received ICOO D50 Lite, it was loaded up to the 2nd image on the display (first green android in the next picture the name of the device). Livesuit not reflash, clamp the back button, insert the cord and few times press the power button, the system will see the device, put the driver and all - there are no familiar pop-ups, livesuit not see him, as if I chose the firmware for another tablet.
Next Im setup CWM recovery for Alwinner A10 devices, one of the courteous users of this device (d50) is also setup recovery and made a firmware backup.
I thought that the problem is solved, but device refused to restore the firmware (on another tablet recovery work well).
First, it is cursed in exec '/ system / bin / sh' failed: No such file or directory (2), I unpacked the folder system and downloaded to the tablet via adb.Then he did not like the sum of md5 hashes, which I also cleared. The next time checking md5 sums is successful, then erasing boot before restore, restoring boot image, restoring system... and then an error error while restoring system!
Changed the adb driver to bootloader (too late realized that, this is my first experience with adb), but now the device does not boot up to the 2nd image and bootloader, and freezes on the first picture with android and in the system at this time is not defined as the adb \ bootloader . That is my sad story.
Send it back or possible do something? I hope for the bright minds of this forum. Thank you all in advance. Sorry for my english.
Everything was decided uploading the latest firmware, livesuit successfully identified the device. Earlier this could not do because their site did not work.
/thread
Related
Hi everyone
I got the AC100 and tried to root it and install the Gapps (i needed Gmail and Calendar).
I messed around with the adb from Google SDK and i erased the files from "system/apps" by accident
so the device now got stuck on the startup screen (the android logo keeps flashing once per second)
I searched the web alot and found instructions on how to enter recovery mode
so know i have the ac100 conected via USB to my XP machine, and i have installed the nVidia USB recovery driver
(it showed up as APX in the Device Manager once i turned on the recovery mode).
I can get to the restore screen (holding HOME while powering up) and i've tried a few "update.zip" files on a SD card, but i get the exclamation mark in the triangle as soon as i hit "1 - update" and then the device resets.
I have NVFlash downloaded and it sees the device (nvflash --sync displays info the way it should)
Can anyone please help with instructions on how to get my notebook working again?
I'll be pleased with the stock Android, i'd be happy with Cyanogen Mod.
Please help.
Thank you.
PS. sorry if it's the wrong thread, but as i've read the Folio and AC100 are pretty similar.
best option is to just push the relevant partition images using nvflash, no need to use recovery. If you have an update.zip, that should have the files you need. Have a look at the wet-paint wiki or ask on #ac100
Thanks for the reply
I do have an update.zip, but i'm not quite sure how to push it with nvflash.
I've search alot around the forums but haven't found anyone with a problem like this or i couldn't really understant the steps (in some cases, one of the steps was "push the file to the device with nvflash" but i'm quite a beginner and i would need more detailed info.
I'll try the IRC # as well but if anyone can post here a method, i'd be really glad.
Thanks
UPDATE:
Ok, with the help of some people over on #ac100, i managed to download part8.img to partition 8 (which was the apps partition) but now the devices freezes on the TOSHIBA logo screen.
Any advice?
Good news
I finally got it to run. I used the backup partition imgs i found (along with the partition table txt) and rewrote all the partitions with NVFLASH using the rawdevicewrite method described here:
tosh-ac100.wetpaint.com/page/Backup+and+Restore
It's back to stock android right now.
I'll look into installing Gmail and Gtalk later on and MUCH MORE careful
If anyone can point me in the right direction, that would be great.
Happened to me too
Hi there, I had the same problem that yours and I have solved it this way:
Prerequisites:
Tegra2 Drivers 2 abailable
Android SDK in your system
A working ROM (folio mod for example)
How to:
Extract update.zip to a known folder
Power on the folio.
When see toshiba's logo push power button 3 times and then Volume UP
Connect to the computer
Move to android sdk tools (using CMD)
type:
fastboot flash recovery recovery.img (maybe a route is requiered for last one)
fastboot flash boot boot.img
fastboot flash system system.img
put the full update.zip file into SD and do a normal update
I hope this helps.
thanks metuskale
i got my to work as well
cheers
Hi everyone, I have a problem. I recently got a Huawei y220 and rooted it and enabled USB debugging, tweaked the SystemUI.apk and it all went good, I had no problem rebooting. I also changed my bootscren with BootScreen from the Play Store.
But today, my phone got stucked in bootloop, and i know why, I changed the /system/fonts permissions to 666, and also when I was trying to change the default font (DroidSans.tttf and DroidSansBold.ttf) copied a font file, so in that folder there was some permissions changed and an extra font. I had to to do something so i locked my phone. When I returned a couple of minutes later the phone was like off, so i removed the battery and rebooted it. It got stucked on my bootscreen, and didn't showed me my ADW launcher.
I can't install CWM as there is no file for this model (because it's very new), I can't flash anything as far as I know. Tried downloading the official "upgrade" from Huawei, copied the file, but I can't seem to enter the "Software Upgrade Mode", (VOL UP + VOL DOWN + POWER KEY), I press those keys for about a minute and nothing happens.
I know my phone isn't fully bricked, for now, so, how can I change those file permissions through my PC or Linux?
I can enter the bootloader screen BTW.
I also tried AromaFM, but i get a signature error.
I've already wiped/factory reset and wiped cache.
Thanks for your time!
--
TheEdwardRC
I thought the way you update / restore the stock firmware was by the update.app method? The update should be in an archive and once you unpack it should be a folder named : dload with the update.app in it. That whole folder should go on the root of the SD card so it should read /sdcard/dload. Unless it is a different y220...
Otherwise, you're kinda screwed because unless you have adb access when it is bootlooping (rare), there won't be much to do. You won't have adb in recovery either since it is still stock.
I guess it is the normal y220. The problem is that I can't get into the Software Upgrade Mode. Also, my other choice was AromaFM but i don't know how to stop it to verify the signature verification. If i could do that, i could have root acces to the files. Or maybe could install a POSSIBLE backup that i found online...
Well, when i am in recovery the device is detected on windows, but ot mounted...
Thank you
My point was, according to the info that I found, you don't update that one via the Software Update mode, you do it via the method I was talking about with the update.app in the dload folder on the SD card.
Huawei Ascend Y220 U00
After installing a theme pack, my huawei Y220 has been stuck in bootloop. I found a toolkit on some forum, it requires my device mounted on a Computer, I got all necessary drivers, but the pc could not install my device. It shows the device on device manager on the PC but after 3sec it ejects. Pls I need help.
look here, this will help you unbrick your device
http://en.club.vmall.com/forum.php?mod=viewthread&tid=13433&highlight=unbrick+huawei
This was a thing from 2 years ago. On one night, my screen suddenly went dark during the use of the phone (I remember the last button I touched was about “image”.And the phone should have root permission). I tried to start it but It did not respond. After waiting for an hour, it was still the same. I can't wait anymore,so I removed the battery. Then the phone restarted automatically entered the recovery mode. then I restarted the phone, but it stopped at the first boot screen ... And then I decided to try to flash the machine, here is a list of all the things I've done:
1.Double wipe (/ data, / cache)
2. Use adb sidelode or update from sdcard to try to restore the entire os (always fails, explained below)
3. Use "fastboot boot boot.img" to test the boot.img in each OS released from the official website (also unable to boot, stuck in fastboot mode)
4. Use fastboot flash to Flash with all the OS , failed,too
4.5. Try to wipe all partitions I know with fastboot (boot,...)
5.Press all possible combination for more than 10 seconds. In factory mode, only clear test result and shutdown are available.
In list 2, I got the os from the official website of acer, and checked the model, but every time it said "assert failed" (I have tested every os on the official website, I even deleted all first line in the update-script [assert()], and the result still are failed.
Plz help if anyone know anyway to make my phone rework again, thanks
Note 1: Before the problem occurred, the TOOL DL Image fail! The problem sometimes appeared, but it was resolved after rebooting (yes, I haven't tried the sp flash tool, and I swear I didn't modify anything at the time ... Because I did n’t understand the system at the time)
Note 2: Below are my device information
Model Name: Z130
Part Number: HM.HD4ST.001
CPU(Maybe): MediaTek MT6572M 1 GHz - Dual Band
Storage: 4 GB
Memory: 0.5 GB
Connectivity:Wi-Fi IEEE 802.11b/g/n,Bluetooth 3.0,GPS,Micro SD slot, 3.5mm audio jack
Android version: Android 4.2
Btw English is not my native language... so there's might be some grammar fault, sorry here:silly:
Hello everybody,
first of all I'm, sorry for my newbie's awkwardness and for my bad english too...
I'm a linux (Debian) enthusiast and I'd liked to install it on my Lenovo Tab M10 Plus; my choice felt on "Linux Deploy" but it needs a rooted device so, after an internet search for tutorials and tips and a system backup (.adb file saved on PC) I bravely tried with Magisk... and I failed (or I think so).
The tablet start in a never-end booting loop and on the splash screen appears the message
"
Orange State
Your device has been unlocked and can't be trusted
You device will boot in 5 seconds
"
I can access in fastboot mode so I tried to flash a no-rooted (downloaded) boot.img but it didn't works (the flashing process reports OKAY but the device reboot anyway in Orange Status), I tried with the flashall command that reports
"
error: ANDROID_PRODUCT_OUT not set
"
I tried to wipe and flash but it didn't works, I granted the access in some recovery mode and tried to install the .adb backup file from the SD card but the system says :
"
E: signature verification failed
E: error: 21
Installation aborted.
"
I thought to open the backup .adb file for extract the original files (I don't know if it could be done and if it could be useful) but how?
I think someday someone more skilled than me will solve the problem but, waiting for that day... any advice ?
Thanks, anyway.
Cheers, Ste.
Use official Lenovo Rescue and Smart Assistant
Same problem...lenovo tab x606F firmware is not present in Lenovo Rescue Smart Assistant and you can't add it manually!
Yes hello, sadly I am having the same issue as well. Anyone have any ideas? Here's what I've tried:
[edit]
Hi all,
Well, operator error is definitely at fault here... I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and obviously ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.
Hi, would anyone like to weigh in on this issue?