Hello friends a salute to this great community, I am writing to make a query Y200 acquired a Huawei Ascend (U8655-51) here in Venezuela the problem is that one of the bad features of this is that it has very little internal space I have this app installed because memory is full and it is saying it has little disk space now the question is how this team rooteo to put the linksd2 and to activate the partition and others in order to have more space there is a Statute for a site German but nothing does not work on my computer I have done several times and does not work in advance thanks for any help greetings hope one response
Tutorial
albertwesker17 said:
Hello friends a salute to this great community, I am writing to make a query Y200 acquired a Huawei Ascend (U8655-51) here in Venezuela the problem is that one of the bad features of this is that it has very little internal space I have this app installed because memory is full and it is saying it has little disk space now the question is how this team rooteo to put the linksd2 and to activate the partition and others in order to have more space there is a Statute for a site German but nothing does not work on my computer I have done several times and does not work in advance thanks for any help greetings hope one response
Click to expand...
Click to collapse
Hi, Albert, I think you are the one who did this tutorial. THANKS :highfive: . It worked for me; XDA is the most known comunity so I think you should post it here too...
Mensaje original:
"(…) Download the application "Y200ToolBox".
Then, configure the device
> Settings -> Applications -> Quick Restart (uncheck)
> Settings -> Applications -> Development -> USB debugging (enable)
Adb drivers installed connect the device and given the option to finish installing the phone disconnected).
Turn off the device, remove the battery a few seconds then put back. Get the device in Fastboot with the combination of the [Volume-/ Power] during 15sec until it stay stuck in the logo
Connect the device to the PC and run the software
Select the Root + CMW
It takes a few seconds to work, do not touch anything.
It takes a while because the software will be doing some work, but it tells you when the process is finished completely and boot.
And you'll be already root users”
It work perfect for me for rooting, CMW I’m still trying, and when I get it I’ll post it. I hope it will work for everybody.
All credits to the friends in MyHuawei.net for the creation of the tool”
“Root Huawei Y200 Modelo U8655-51
Para los que no han podido ser Root en este modelo con otros métodos (no discrimino ni digo que no funcionan solo es otra alternativa)
Descargamos la aplicación Y200ToolBox al final dejo el link
Luego configuran el dispositivo
Configuración -> Aplicaciones -> Reinicio rápido (desmarcar)
Configuración -> Aplicaciones -> Desarrollo -> Depuración USB (activar)
Instalan los drivers adb, conectan el dispositivo y les dará la opción de instalarlos al terminar desconectan el teléfono
Apagan el dispositivo sacan la batería unos segundos luego la colocan de nuevo encienden el dispositivo en Fastboot con la combinación de las teclas [Volumen- / Poder] durante 15seg se quedara estancado en el logo
Conectan el dispositivo a la PC y ejecutan el software
Selecciona la opción Root + CMW
Dejan que trabaje se tardara unos segundos NO TOQUEN NADA
Lo dejan un rato ya que el soft. Estará haciendo unas tareas más el avisara cuando todo el proceso haya terminado completamente se apagara y encenderá nuevamente
Y listo ya serán usuarios Root"
A mí me funciono perfectamente para el Root, aunque el CMW todavía no me funciona. Si lo consigo lo pongo bueno espero que les sirva a los que tienen este equipo que a mi parecer es muy bueno
Todos los créditos por la creación de la herramienta a los amigos de MyHuawei.Net”
Click to expand...
Click to collapse
IMPORTANT/IMPORTANTE:
When I used the tool it didn’t work, so I navigated to the install directory Programs Files/MyHuawei.Net and I found a BAT file: “root.bat” that I ran and did the job, it took like 5 minutes. Follow the steps in the Albert tutorial, and run “root.bat” instead of the “Y200ToolBox.exe” if this happens to you. Wait a while, then the phone will boot unrooted, wait a little more and it will boot again by itself and do the Root. :victory:
The error message was like: It’s not a win32 valid application.
Cuando usé la herramienta no funcionó, así que abrí el directorio de instalación Archivos de Programa/MyHuawei.Net y encontré un archivo BAT: “root.bat”, que corrí e hizo el trabajo, tomó como 5 min. Sigan las instrucciones de Albert en su tutorial y corran “root.bat” en vez de “Y200Toolbox.exe” si les ocurre. Esperen un poco, el teléfono se reiniciará sin privilegios Root y luego se reiniciará de nuevo y finalizará el rooteado.
El mensaje de mi error fue algo como No es una aplicación win32 valida.
XDA doen't let me post the link. Search "Y200ToolBox" in google.
XDA no me deja postear el link. Busquen "Y200ToolBox" en google.
tutorial made by albertwesker at Htcmania
tutorial hecho por albertwesker en Htcmania
I discovered the solution to the error by myself, any questions please ask.
La solución a el error de la aplicación lo descubrí por mi cuenta, cualquier cosa pregúntenme.
thanks
it achieves exactly is mine and quice compratir as I did for this team they have not remembered thanks for bringing xda but I had no problem but brought greetings friend
l7wahn said:
IMPORTANT/IMPORTANTE:
When I used the tool it didn’t work, so I navigated to the install directory Programs Files/MyHuawei.Net and I found a BAT file: “root.bat” that I ran and did the job, it took like 5 minutes. Follow the steps in the Albert tutorial, and run “root.bat” instead of the “Y200ToolBox.exe” if this happens to you. Wait a while, then the phone will boot unrooted, wait a little more and it will boot again by itself and do the Root. :victory:
The error message was like: It’s not a win32 valid application.
Click to expand...
Click to collapse
i follow the instruction.
> usb debug
> uncheck fast boot
> successfully install and connect adb driver
> Turning off the device, remove the battery a few seconds then put back. Get the device in Fastboot with the combination of the [Volume-/ Power] during 15sec until it stay stuck in the logo
Connect the device to the PC and run the software
here, i follow your instruction in running "root.bat" in the myhuawei.net because i found "It’s not a win32 valid application."
after that it ran the bat file, about 1 minute my pc restarted
> i wait until it works again but it doesn't.
> there's windows error message
where and what are my mistakes?
thanks
Answers
bakuradits said:
i follow the instruction.
> usb debug
> uncheck fast boot
> successfully install and connect adb driver
> Turning off the device, remove the battery a few seconds then put back. Get the device in Fastboot with the combination of the [Volume-/ Power] during 15sec until it stay stuck in the logo
Connect the device to the PC and run the software
here, i follow your instruction in running "root.bat" in the myhuawei.net because i found "It’s not a win32 valid application."
after that it ran the bat file, about 1 minute my pc restarted
> i wait until it works again but it doesn't.
> there's windows error message
where and what are my mistakes?
thanks
Click to expand...
Click to collapse
Why did your pc restarted? or do you mean your Device?
This is what the root.bat do:
first it erase the recovery image and flash an image with cwm (step that will make your device to not get into the recovery any more... There's a solution)
second it flash the y200recovery.img that is in the y200toolbox directory
third it boots
then when the device boots into the android software and you see the loader, or the lock (depending on your configuration) it will run a shell in adb that will get the superuser.apk in the /system directory. If you're using an Huawei u8655-51, there will be not a chance to damage anything if your pacient.
last it sends the adb reboot command to the phone and the phone boots rooted.
Know, make all things again, but wait until the command promt shuts itself.
Alfredohs esto es para ti:
si dañaste el proceso de inicio es porque tal vez usaste otro ".bat" en el directorio. Esto va a dañar el boot.img de tu teléfono, debes usar el stockkernel.bat en modo fastbot para restaurarlo.
If you damaged the booting process in the phone it might be because you used another ".bat" in the directory. Which will change the boot.img so you should use the stockkernel.bat whit the device in fastboot mode to restore it.
Hi... I have used "Y200ToolBox" to root my phone, but it seems something went wrong. I tried to do it again, but while I restart the phone it restarts to CWM recovery. I don't know when this happened. So I think I disconnected the phone before the rest of the process completed the first time I tried, I mean the rooting part... Can you help me to solve this?
--------------------------------------------------------------------
Hola, he usado "Y200ToolBox" para rootear mi fone, pero parece que algo salió mal. Intenté hacerlo de nuevo, pero mientras reinicio el fone este se va al CWM recovery. No sé cuando pasó, así que pienso que lo desconecté antes de que cumpliera el resto del proceso la primera vez que lo hice, me refiero a la parte del rooting... Me podrían ayudar a resolver esto?
Huawei ascend y200 FM apk required
Hi
I rooted my Huawei ascend y200 and accidentally removed the FM application. If you have the apk please share it
Related
English (Google Translator): Hi, Sorry but first of all. Do not speak English. : ( But I need the help of this great community of developers.
My problem is this, I have an Optimus One P500, brought android originally wanted to upgrade to 2.2.1 and 2.3.3. Check all the options of the forum and I decided to root using the method GingerBreak the rooteo runs without any apparent error, but to my surprise when you restart your phone is Emergency Mode (yellow screen), I thought instantly that I had bricked, remove the battery and left it like 10min, then place it back and turned on the computer, strangely lit correctly, did not show emergency mode. Again I thought it had already been solved, but when
you turn off the computer again returned to the screen yellow emergency mode, the strange thing is that by removing the battery 10min and starts back up if the right way.
But because it's annoying that every time you turn it off need to do
this (remove the battery and such) because I decided to follow the methods desbrickeo who are here in the forum, flashing a ROM format 2.3.3. Kdz smoothly , then do factory reset (wipe) the data necessary to eliminate the previous ROM and the phone lit correctly, but off and on again to find the screen yellow emergency mode again, no change, wait 10 minutes and starts normally.
The situation is tired and annoyed me, so I turn to you, help you regain normal operation.
Any suggestions or help will be welcome, please do not delete the post because it is in Spanish which really NOT write or speak English.
Best regards.
Buenas, primero que nada DISCULPAS pero. DON'T speak english.
Sin embargo estoy necesitando la ayuda de esta gran comunidad de desarrolladores.
Mi problema es el siguiente, tengo un Optimus One P500, originalmente traia android 2.2.1 y queria actualizarlo a 2.3.3. Revise todas las opciones del foro y me decidi a rootear usando el metodo GingerBreak, el rooteo se ejecuto sin ningun error aparente, pero para mi sorpresa cuando reinicie el telefono quedo en MODO EMERGENCIA (pantalla amarilla), pense instantaneamente que lo habia brickeado, quite la bateria y lo deje asi como 10min, luego la coloque de nuevo y encendi el equipo, cosa rara encendio de manera correcta, NO mostro el modo emergencia.
De nuevo pense que ya se habia solucionado, pero al apagar de nuevo el equipo volvio a mostrar la pantalla amarilla en modo emergencia, lo raro es que quitando la bateria 10min y volviendolo a encender SI arranca de manera correcta.
Pero debido a que es MOLESTO que cada vez que lo apague deba hacer esto (quitar la bateria y tal) pues me decidi a seguir los metodos de desbrickeo que estan aqui en el foro, flashee una ROM 2.3.3 en formato .kdz sin inconvenientes, luego realice el reseteo de fabrica (wipe) necesario para eliminar los datos de la ROM anterior y el telefono encendio de manera correcta, pero nuevamente al apagarlo y encenderlo encontre la pantalla amarilla del modo emergencia de nuevo, sin cambios, espere 10min e inicia normalmente.
La situacion me tiene cansado y molesto, por eso acudo a ustedes, ayudenme a recuperar el funcionamiento NORMAL del equipo.
Cualquier sugerencia o ayuda sera MUY bien recibida, por favor no borren el post por estar en español que de verdad NO se escribir ni hablar ingles.
Saludos cordiales.
Forum rules
Speak English, or use Google Translate.
Google Translate :
Hi, Sorry but first of all. Do not speak English.
But I need the help of this great community of developers.
My problem is this, I have an Optimus One P500, brought android originally wanted to upgrade to 2.2.1 and 2.3.3. Check all the options of the forum and I decided to root using the method GingerBreak the rooteo runs without any apparent error, but to my surprise when you restart your phone is Emergency Mode (yellow screen), I thought instantly that I had bricked, remove the battery and left it like 10min, then place it back and turned on the computer, strangely lit correctly, did not show emergency mode.
Again I thought it had already been solved, but when you turn off the computer again returned to the screen yellow emergency mode, the strange thing is that by removing the battery 10min and starts back up if the right way.
But because it's annoying that every time you turn it off need to do this (remove the battery and such) because I decided to follow the methods desbrickeo who are here in the forum, flashing a ROM format 2.3.3. Kdz smoothly , then do factory reset (wipe) the data necessary to eliminate the previous ROM and the phone lit correctly, but off and on again to find the screen yellow emergency mode again, no change, wait 10 minutes and starts normally.
The situation is tired and annoyed me, so I turn to you, help you regain normal operation.
Any suggestions or help will be welcome, please do not delete the post because it is in Spanish which really NOT write or speak English.
Best regards.
Edit. Google Translator Post. Sorry. :S
try installing custom recovery?
Thundeg or ClockworkMod (from Rom Manager)? I already had installed from ROM ClockworkMod rootee manager when using GingerBreak, but the problem persisted, trying to thunderg? now I have the ROM 2.3.3 (Romanian) flashed as I said from kdz.
i think u have some problem in hardware....
make sure your phone dont have custom recovery and not rooted
go to lg service center.
juanitomigraña said:
English (Google Translator): Hi, Sorry but first of all. Do not speak English. : ( But I need the help of this great community of developers.
My problem is this, I have an Optimus One P500, brought android originally wanted to upgrade to 2.2.1 and 2.3.3. Check all the options of the forum and I decided to root using the method GingerBreak the rooteo runs without any apparent error, but to my surprise when you restart your phone is Emergency Mode (yellow screen), I thought instantly that I had bricked, remove the battery and left it like 10min, then place it back and turned on the computer, strangely lit correctly, did not show emergency mode. Again I thought it had already been solved, but when
you turn off the computer again returned to the screen yellow emergency mode, the strange thing is that by removing the battery 10min and starts back up if the right way.
But because it's annoying that every time you turn it off need to do
this (remove the battery and such) because I decided to follow the methods desbrickeo who are here in the forum, flashing a ROM format 2.3.3. Kdz smoothly , then do factory reset (wipe) the data necessary to eliminate the previous ROM and the phone lit correctly, but off and on again to find the screen yellow emergency mode again, no change, wait 10 minutes and starts normally.
The situation is tired and annoyed me, so I turn to you, help you regain normal operation.
Any suggestions or help will be welcome, please do not delete the post because it is in Spanish which really NOT write or speak English.
Best regards.
Buenas, primero que nada DISCULPAS pero. DON'T speak english.
Sin embargo estoy necesitando la ayuda de esta gran comunidad de desarrolladores.
Mi problema es el siguiente, tengo un Optimus One P500, originalmente traia android 2.2.1 y queria actualizarlo a 2.3.3. Revise todas las opciones del foro y me decidi a rootear usando el metodo GingerBreak, el rooteo se ejecuto sin ningun error aparente, pero para mi sorpresa cuando reinicie el telefono quedo en MODO EMERGENCIA (pantalla amarilla), pense instantaneamente que lo habia brickeado, quite la bateria y lo deje asi como 10min, luego la coloque de nuevo y encendi el equipo, cosa rara encendio de manera correcta, NO mostro el modo emergencia.
De nuevo pense que ya se habia solucionado, pero al apagar de nuevo el equipo volvio a mostrar la pantalla amarilla en modo emergencia, lo raro es que quitando la bateria 10min y volviendolo a encender SI arranca de manera correcta.
Pero debido a que es MOLESTO que cada vez que lo apague deba hacer esto (quitar la bateria y tal) pues me decidi a seguir los metodos de desbrickeo que estan aqui en el foro, flashee una ROM 2.3.3 en formato .kdz sin inconvenientes, luego realice el reseteo de fabrica (wipe) necesario para eliminar los datos de la ROM anterior y el telefono encendio de manera correcta, pero nuevamente al apagarlo y encenderlo encontre la pantalla amarilla del modo emergencia de nuevo, sin cambios, espere 10min e inicia normalmente.
La situacion me tiene cansado y molesto, por eso acudo a ustedes, ayudenme a recuperar el funcionamiento NORMAL del equipo.
Cualquier sugerencia o ayuda sera MUY bien recibida, por favor no borren el post por estar en español que de verdad NO se escribir ni hablar ingles.
Saludos cordiales.
Click to expand...
Click to collapse
Hi ,writing in simple English as possible for you to understand ..
I had/have this same problem ..meaning the phone when restarted would go into emergency mode ..like always after it being earlier connected to pc.
well after doing all sorts of bells and whistles ,I found out that the culprit is sd-card due to improper partitioning etc.. and just replacing the sd-card solves this highly irritating problem .. Hope this helps ya !
Thanks for your answers. The solution to bring it to technical service is the one used, I have flashed from "kdz" the official ROM from my operator, without root and no custom recovery. Tomorrow I'm taking, how sad is having these problems with a team of good behavior like this. A greeting.
FIRST: Thanks to jose.guillen1302 (User of HTCManía)
==========================
English version:
==========================
*NOTE* Im uruguayan, and my english its TOO BAD but better than google translator.
Yesterday, i updated my phone, with LGUpdateTool and blah blah blah, with kdz from lg-firmware-rom.com and more blah blah blah
Some hours after the update, i tried to re-flash to downgrade, because the last build its unrooteable with towelroot v1 (freezes)
The problem was: No download mode. (It continues normally)
*reaction* :crying: :crying: :crying: :crying:
At 03:00am i found the solution! (Another time thanks to user of htcmania)
1. Enable Usb Debugging
2. Install adb+fastboot app & driver (i used the installer of the user @Snoop05 /showthread.php?t=2588979)
3. Open a cmd, connect the phone, and do adb restart bootloader
4. The phone will restart and stay on a black screen.
5. Now go to Device Manager and search the unknown device: fastboot
6. Right click > Update driver manually > Search on pc > see full list
7. Search Google, Inc. in the list and install HTC Bootloader, overriding windows message.
8. Now close the device manager, disconnect phone from usb, remove the battery
9. Turn it on, with vol + and THAT'S IT! Now download mode works magically.
Hope it helps.
Source: HTCMania thread - Message #18
==========================
Spanish version / Versión en español:
==========================
*NOTA* Si alguien sabe inglés perfectamente, agradecería enormemente que me corrigiesen.
Ayer, actualicé mi teléfono, con LGUpdateTool y bla bla bla, con el kdz de lg-firmware-rom y mas bla bla bla...
Unas horas despues, intenté re-flashear para hacer downgrade, porque la ultima build no es rooteable con towelroot v1 (se tilda)
El problema era: No tenía modo Download (No podía flashear.)
*mi reacción* :crying: :crying: :crying: :crying:
A eso de las 03:00am encontré la solucion (Otra vez gracias al usuario de HTCManía)
1. Activar modo Depuración Usb
2. Instalar adb+fastboot, la aplicación y el driver. (usé el instalador del usuario @Snoop05 /showthread.php?t=2588979)
3. Abrir una consola (cmd), conectar el teléfono, y hacer: adb restart bootloader
4. El telefono se reiniciará y se quedará en una pantalla negra
5. Ahora ve al administrador de dispositivos y busca el dispositivo desconocido: fastboot
6. Haz click derecho > Actualizar driver manualmente > Buscar en el equipo > ver lista completa
7. Busca " Google, Inc. " en la lista y de ella instala HTC Bootloader, sobrepasando el mensaje de advertencia de windows.
8. Cierra el administrador de dispositivos, desconecta el telefono del usb, remueve la batería
9. Enciendelo, con la tecla vol + y FUNCIONA! Modo download a la vida MAGICAMENTE (Bueno, no tan magicamente)
Espero que ayude.
Fuente: Hilo de HTCManía - Mensaje #18
This is for the D625, right?
Sent from my D620r [Stock 4.4.2]
Vagelis1608 said:
This is for the D625, right?
Sent from my D620r [Stock 4.4.2]
Click to expand...
Click to collapse
Yeah, i tested it on a D625, but i think may work on other g2 mini's who haves this problem.
Nice.
In case you dont manage to install as OP said, choose to instal ADB Interface, select google inc, then in the sub options youll find the htc bootloader.
Also confirming it worked.
Thanks.
Hello.
I have a device that runs a Mediatek MT8563 it seems to be running android, but it has a locked launcher and I cannot seem to get another launcher or any other app to install,
I have connected the UART and I was able to get to the boot loader, but I can't seem to be able to access anything else.
anyone here with more experience with these devices?
If I can at least install another launcher it would be amazing!
The device says "Coship N9085i" but I can't find any info other that a few photos.
I also emailed Coship support to ask for a generic firmware, and they said "No"
This is what the bootloaded shows:
Code:
mt8658_base # help
? - alias for 'help'
base - print or set address offset
bdinfo - print Board Info structure
bootm - boot application image from memory
bootm_zImg- bootm_zImg - boot with zImage in memory
bootp - boot image via network using BOOTP/TFTP protocol
chpart - change active partition
cmp - memory compare
cp - memory copy
crc32 - checksum calculation
dis_log - log_enable
ext2load- load binary file from a Ext2 filesystem
ext2ls - list files in a directory (default /)
ext4load- load binary file from a Ext2 filesystem
ext4ls - list files in a directory (default /)
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatloadex- load binary file from a dos filesystem
fatls - list files in a directory (default /)
go - start application at address 'addr'
help - print online help
loop - infinite loop on address range
matchfile- match a file in a directory
md - memory display
mm - memory modify (auto-incrementing address)
mmc - MMC sub system
mmcinfo - mmcinfo <dev num>-- display MMC info
msdc - msdc -msdc performance testing
mt85xx_boot- mt85xx_boot - boot command for mt85xx platform
mtdparts- define flash/nand partitions
mtest - simple RAM read/write test
mw - memory write (fill)
nm - memory modify (constant address)
ota - Reboot and enter recovery mode
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
rarpboot- boot image via network using RARP/TFTP protocol
reset - Perform RESET of the CPU
setenv - set environment variables
tftpboot- boot image via network using TFTP protocol
ubi - ubi commands
ubifsload- load file from an UBIFS filesystem
ubifsls - list files in a directory
ubifsmount- mount UBIFS volume
upg - upg - Upgrade image sub-system
usb - usb - BDP USB sub-system
usbboot - usbboot - boot from USB device
version - print monitor version
i have the same box.. can u share the pins tx rx for use uart?? speak spanish??
estanenmi said:
i have the same box.. can u share the pins tx rx for use uart?? speak spanish??
Click to expand...
Click to collapse
Yes I do, I am, from Mexico
send me a PM and I can give you the info
buenas me puedes pasar la informacion mi correo es [email protected] te lo agradecería mucho espero respuesta
UART HELP
Hello partner, could you comment on that application and parameters you used to communicate with the device. I tried to log in, but do not receive the information correctly in the terminal. I hope your support.
Greetings from Mexico.
If i do all the proces but i put another image file can work?
informacion
ya hice todo el procedimiento aparees el imagen de android acostado abajo dice que falle la instalación y no se carga la imagen
ya hice todo el procedimiento aparees el imagen de android acostado abajo dice que falle la instalación y no se carga la imagen
no me permite arrancarlo
ayuda coship
:good:
niabi said:
esta dificil poder ayudarte desde aca, pero te sale alguna informacion en el terraterm? o solo es pantalla negra?
Click to expand...
Click to collapse
pues si hermano me aparece esto en pantalla ya configura todo segun el tutorial y de esta pantalla no puedo sacarlo
ya hice todo el procedimiento aparees el imagen de android acostado abajo dice que falle la instalación y no se carga la imagen
no me permite arrancarlo
no se si la ruta o el nombre del archivo no coinciden . como o donde puedo ver que archivo tiene que jalar para su restauracion tanto la ruta como el nombre
AYUDA
Ayuda por favor
como lo desbloqueo
niabi said:
yes i do, i am, from mexico
send me a pm and i can give you the info
Click to expand...
Click to collapse
Hola amigo Segui tu tutorial pero tengo una pregunta cuanto tarda en hacer la actualizacion?
RENATOZAZUETA said:
Ayuda por favor
como lo desbloqueo
Click to expand...
Click to collapse
Toda la información esta en el post.
acidmazner said:
Hola amigo Segui tu tutorial pero tengo una pregunta cuanto tarda en hacer la actualizacion?
Click to expand...
Click to collapse
no debe de tardar mas de 10 minutos.
armandoz58 said:
ya hice todo el procedimiento aparees el imagen de android acostado abajo dice que falle la instalación y no se carga la imagen
Click to expand...
Click to collapse
n0m0 said:
ya hice todo el procedimiento aparees el imagen de android acostado abajo dice que falle la instalación y no se carga la imagen
no me permite arrancarlo
Click to expand...
Click to collapse
n0m0_r said:
ya hice todo el procedimiento aparees el imagen de android acostado abajo dice que falle la instalación y no se carga la imagen
no me permite arrancarlo
no se si la ruta o el nombre del archivo no coinciden . como o donde puedo ver que archivo tiene que jalar para su restauracion tanto la ruta como el nombre
Click to expand...
Click to collapse
"Lo tienen que descomprimir y renombrar el archivo a 8658_linux_demo_dbg.bin y lo ponen en una tarjeta SD, dentro de un folder llamado UPG."
a mi me sale esto:
mt8658_base # ota
change the upg_status to OTA TODO
[EMMC][mtk_emmc_read] start=0x0, len=0x800000, buf=0x22f8c88
[EMMC][i4NFBPartitionWrite] Parameter out of capacity
[UPG_ERROR]upg_flash.c i4NFBPartitionWrite failed
[i_set_upg_status_by_upg] nand write FAIL.
Usage:
Reboot and enter recovery mode
por favor me podrian enviar la informacion a [email protected] ya que no he podido hacer nada porque me bota un error con el mmc
Coship n9090
Hola a todos en especial a niabi!
He logrado conectar la nueva box que usa claro la n9090 y puedo ver en el tera term los datos al encender la caja pero no puedo escribir nada!, no se si me este faltando algo o este bloqueada para no poder hacerlo modificaciones ayuda!
rome3ro said:
Hola a todos en especial a niabi!
He logrado conectar la nueva box que usa claro la n9090 y puedo ver en el tera term los datos al encender la caja pero no puedo escribir nada!, no se si me este faltando algo o este bloqueada para no poder hacerlo modificaciones ayuda!
Click to expand...
Click to collapse
I have the same model. will it be possible to do something via update.zip on recovery? i can access recovery mode just pressing power + left button while booting up, its all in chinese.
Antieco said:
I have the same model. will it be possible to do something via update.zip on recovery? i can access recovery mode just pressing power + left button while booting up, its all in chinese.
Click to expand...
Click to collapse
Ok so do you have tne coship n9090? where did you get it? it could be helpful acces on boot mode like you did but we would need to have a copy of the original firmware/rom or have te way to access to the system to dump a copy, right now I'm able to get the boot data connected with aa usb/ttl adapter attached to the pcb but I can't enter on u-boot
rome3ro said:
Ok so do you have tne coship n9090? where did you get it? it could be helpful acces on boot mode like you did but we would need to have a copy of the original firmware/rom or have te way to access to the system to dump a copy, right now I'm able to get the boot data connected with aa usb/ttl adapter attached to the pcb but I can't enter on u-boot
Click to expand...
Click to collapse
Got two units from Claro, I'm keen on sacrifice one of them.. Should we look for firmwares on similar specifications device?
Enviado desde mi A0001 mediante Tapatalk
Good. My cellular one had remained plaster in the logo of beginning and due to this unload the Rom Stock/Firmware and the folder dload copy it in the Card SD. Press Power, Vol + and Vol - and it began the installation. On having initiated to the telephone he asked me " Update of Software " on having disburdened I skip the option to install and restart the equipment. Restart it and it went away to the terminus emui. But 5 hours happened and the cel followed in 0 % so I decided to take the battery from him and to do the same procedure of the update.app For my surprise on having made it immediately was jumping the mistake. " Software Install failed " And eh here where I come to you, does it design someone of since this solves?
-----------------------------------------------------------------------
Buenas. mi celular se había quedado pegado en el logo de inicio y debido a esto le descargue la Rom Stock/Firmware y la carpeta dload la copie en la Tarjeta SD.
Presione Power, Vol+ y Vol- y comenzó la instalación.
Al iniciar al teléfono me pidio "Actualización de Software" al descargarse me salto la opción de instalar y reiniciar el equipo.
Lo reinicie y se fue a la terminal emui. Pero pasaron 5 horas y el cel seguia en 0% así que decidí quitarle la bateria y hacer el mismo procedimiento del update.app
Para mi sorpresa al hacerlo inmediatamente me saltaba el error. "Software Install failed"
Y eh aqui donde acudo a ustedes, alguna idea de como solucionar esto?
Hello I need your help !!!!
Huawei Ags-w09 tablet
Does not start stays in erecovery shows the option to connect to wifi and gives the error wifi failed! I access another screen of the erecovery where it gives me the hard reset option and it never reaches 100%, it turns off or freezes.
With hsuite in recover system tells me that the device does not support this.
Try with sd memory creating the dload folder with the update file doesn't work either.
In fastboot mode with commands in cmd it indicates bootloader blocked.
Any solution!
Thank you
Hola necesito su ayuda!!!!
Tablet Huawei Ags-w09
No inicia se queda en erecovery muestra la opción conectarse en wifi y da el error wifi failed! Accedo a otra pantalla del erecovery donde me da la opción hard reset y nunca llega al 100% se apaga o queda congelada.
Con hsuite en recuperar sistema me dice q el dispositivo no es compatible con esto.
Intente con memoria sd creando la carpeta dload con el archivo update tampoco funciona.
En modo fastboot con comandos en cmd me indica bootloader bloqueado.
Alguna solución!
Muchas gracias
Help!!!!!
Please help!!!
flopez_dj said:
Hello I need your help !!!!
Huawei Ags-w09 tablet
Does not start stays in erecovery shows the option to connect to wifi and gives the error wifi failed! I access another screen of the erecovery where it gives me the hard reset option and it never reaches 100%, it turns off or freezes.
With hsuite in recover system tells me that the device does not support this.
Try with sd memory creating the dload folder with the update file doesn't work either.
In fastboot mode with commands in cmd it indicates bootloader blocked.
Any solution!
Thank you
Hola necesito su ayuda!!!!
Tablet Huawei Ags-w09
No inicia se queda en erecovery muestra la opción conectarse en wifi y da el error wifi failed! Accedo a otra pantalla del erecovery donde me da la opción hard reset y nunca llega al 100% se apaga o queda congelada.
Con hsuite en recuperar sistema me dice q el dispositivo no es compatible con esto.
Intente con memoria sd creando la carpeta dload con el archivo update tampoco funciona.
En modo fastboot con comandos en cmd me indica bootloader bloqueado.
Alguna solución!
Muchas gracias
Click to expand...
Click to collapse