Related
Español
Se me apago mi tablet y al prenderlo se quedo en la pagina de inicio Samsung Galaxy Note 10.1, entre a modo recovery y instale una rom que tenia, espere y de nuevo se quedo en la pagina de inicio, volvi a entrar a modo recovery y abajo salio:
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/last-log
E: Can't open /cache/recovery/last-log
Y la ayuda seria como lo puedo volve a dejarlo a la normalidad
English
I will I turn my tablet and turn it stayed on the homepage Samsung Galaxy Note 10.1, enter recovery mode and install a rom I had wait and again stayed in the homepage, turned to enter recovery mode and I went down:
E: Can not open / cache / recovery / log
E: Can not open / cache / recovery / log
E: Can not open / cache / recovery / last-log
E: Can not open / cache / recovery / last-log
And I would help as volve to leave to normal
Sorry fail to understand the problem ,Try a factory reset first .
Try reading the stickied FAQS
Yes like says the above guy , try do wipe data and wipe cache before flash the rom
Xperia M2 Dual, D2302., Lollipop 5.1.1 - ( Firmware 18.6.A.0.182)
----------------------------------------------------------------------------------------------
This is how it accidentally happened: USA Band selected.
Dial *#*#4636#*#* > Testing menu > Phone information > Select Radio Band > USA Band (No other option in the list).
Lost network, SIM network stopped working now.
----------------------------------------------------------------------------------------------
All below action already performed:
- Bootloader is unlocked
- Successfully connects to ADB and fastboot
- Applied below Fastboot commands:
Fastboot erase modemst1 > Returns with failed (Command not allowed)
Fastboot erase modemst2 > Returns with Failed (Command not allowed)
Fastboot erase cache > Ok
- Also connected to Sony Emma > flash mode – can’t see option to flash modem.img /radio.img
------------------------------------------------------------------------------------------------
How to get to the solution to reset back now?
Please comment help!
Thank you!
solucion español adb
Abrí una ventana DOS y comencé el ADB SHELL con el teléfono conectado, hice *#*#4636#*#* y presione Información del teléfono. Después hice la siguiente instrucción con el adb:
adb shell
$ su
# stop ril-daemon
Después de hacer Enter ves que tu conexión esta perdida, presiona el menú del teléfono y escoges Seleccionar banda de red y las opciones Establecer banda GSM y UMTS aparece en la pantalla. Aquí es donde hay que repartir el ril-daemon:
# start ril-daemon
Despues de hacer Enter, ves que tienes conexión otra vez, presiona Automatic y obtienes el mensaje siguiente:
Establecer Automatic Correcto.
espero que te sirva
I love venezuela
TechGuys said:
Xperia M2 Dual, D2302., Lollipop 5.1.1 - ( Firmware 18.6.A.0.182)
----------------------------------------------------------------------------------------------
This is how it accidentally happened: USA Band selected.
Dial *#*#4636#*#* > Testing menu > Phone information > Select Radio Band > USA Band (No other option in the list).
Lost network, SIM network stopped working now.
----------------------------------------------------------------------------------------------
All below action already performed:
- Bootloader is unlocked
- Successfully connects to ADB and fastboot
- Applied below Fastboot commands:
Fastboot erase modemst1 > Returns with failed (Command not allowed)
Fastboot erase modemst2 > Returns with Failed (Command not allowed)
Fastboot erase cache > Ok
- Also connected to Sony Emma > flash mode – can’t see option to flash modem.img /radio.img
------------------------------------------------------------------------------------------------
How to get to the solution to reset back now?
Please comment help!
Thank you!
Click to expand...
Click to collapse
How we solve
gabriel1209 said:
Abrí una ventana DOS y comencé el ADB SHELL con el teléfono conectado, hice *#*#4636#*#* y presione Información del teléfono. Después hice la siguiente instrucción con el adb:
adb shell
$ su
# stop ril-daemon
Después de hacer Enter ves que tu conexión esta perdida, presiona el menú del teléfono y escoges Seleccionar banda de red y las opciones Establecer banda GSM y UMTS aparece en la pantalla. Aquí es donde hay que repartir el ril-daemon:
# start ril-daemon
Despues de hacer Enter, ves que tienes conexión otra vez, presiona Automatic y obtienes el mensaje siguiente:
Establecer Automatic Correcto.
espero que te sirva
I love venezuela
Click to expand...
Click to collapse
You should know the 4th rule of XDA forums:
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
Click to expand...
Click to collapse
BlueStacks 2.2.17.6203 is introducing "VirtualBox VMs".
The filesystems have been changed to "vdi format" (VirtualBox).
For linux experts: if you know how to mount and modify .vdi without VirtualBox, skip to step 9.
Well, let's get started!
First of all, to root BlueStacks this way you need VirtualBox and you have a Linux OS installed. If you just got started, I'll recommended Ubuntu, you can follow the guide installing Ubuntu on BirtualBox. http://www.wikihow.com/Install-Ubuntu-on-VirtualBox
Also, you will need some linux knowledge. It's not necessessary, but I won't provide any support about the part dealing with linux commands. Just follow the instructions and probably you will be able to root it, but it might not be that simple.
The second mandatory stuff you will need is the Android App called SuperSU. At this time, you should be able to find the latest SuperSU. The instructions should be the same with other SuperSU versions.
Here is a direct link http://www.supersu.com/download
This tutorial assumes you already have an installed BlueStacks you wish to root, but make sure Bluestacks and Ubuntu isn't running isn't running. So, let's get started.
In this tutorial i'm using Ubuntu.
1. MAKE A BACKUP OF ROOT.VDI FILE FIRST!
2. To modify Root.vdi, you need to mount it in Ubuntu virtual machine. Select Ubuntu and click Settings -> Storage. Select Controller: SATA and click on the HDD with green plus symbol.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. A dialog box will appear. Select Choose existing disk
4. Navigate to Bluestacks directory where you installed. Select Root.vdi and Open
ProTip: You can mount Data.vdi and SDcard.vdi to transfer files between guest and VDI.
5. Root.vdi should be added in Storage. Click OK
6. Start Ubuntu on VirtualBox
7. Ubuntu: On your desktop, you should see the grey Hard Drive icon on the right taskbar. Yep, that's root.vdi image file that has been mounted and the disk name should be named 8,6 GB Volume
8. Extract x86 Folder from .zip (Recovery Flashable.zip) archive file and /common/SuperSU.apk somewhere on Ubuntu. Bluestacks is based on Android x86.
8.1. If you already downloaded it on your host computer, Click Devices -> Drag and Drop, Select Bidirectional and you can transfer the file to guest
If you haven't download it yet, download it from http://www.supersu.com/download and click Recovery Flashable.zip
9. Copy the following SuperSU files into your mounted root.vdi
Add file: /x86/su -> (8,6 GB Volume)/android/system/xbin/su
Rename file: /x86/su ---> (8,6 GB Volume)/x86/daemonsu
Add file: /x86/daemonsu ---> (8,6 GB Volume)/android/system/xbin/daemonsu
Add file: /x86/supolicy ---> (8,6 GB Volume)/android/system/xbin/supolicy
Add file: /x86/libsupol.so ---> (8,6 GB Volume)/android/system/lib/libsupol.so
Add file: /common/Superuser.apk ---> (8,6 GB Volume)/android/system/app/Superuser.apk
10. You need to change file permissions in order for SuperSU to work correctly. Open terminal and type the following commands. Type your password when asked
Note: The disk name might be different. You can check it by right click on 8,6 GB Volume and select Properties
ProTip: Type sudo chmod xxx in terminal and drag a file to get the full path like below. Press UP ARROW on your keyboard to show the last command you used.
sudo chmod 755 '/media/test/<disk udid>/android/system/xbin/su'
sudo chmod 755 '/media/test/<disk udid>/android/system/xbin/daemonsu'
sudo chmod 755 '/media/test/<disk udid>/android/system/xbin/supolicy'
sudo chmod 644 '/media/test/<disk udid>/android/system/lib/libsupol.so'
sudo chmod 644 '/media/test/<disk udid>/android/system/app/Superuser.apk'
Files should be owned by root:root. No need to change it on Ubuntu.
11. Now we need to start "daemonsu" on every reboot. BlueStacks init procedure is quite simple. Seems like there is only android/system/etc/init.sh. So, open android/system/etc/init.sh in your preferred linux text-editor, go at the bottom of the file and search for:
Code:
init|"")
do_init
;;
esac
Add this
Code:
init|"")
do_init
/system/xbin/daemonsu --auto-daemon &
;;
esac
I'd say we're done now! Shutdown your Virtualbox
12. Now you can start your BlueStacks. When it's booted, launch SuperSU via Play Store.
You will be prompted about a SuperSU update. Choose the "normal" way and after the update, restart your BlueStacks.
13. That should be it. Now your BlueStacks is rooted.
To be certain you should open your PlayStore and install your preferred RootChecker.
An additional task you might want to do would be using some apps like "/system/app Mover" and "System App Uninstall" and change the SystemDefaultAppLauncher and SystemDefaultAppBrowser.
I usually install Nova Launcher.
Also, as Root FileExplorer, I install X-Plore.
You might want to install a CatLog too!
Hope you enjoyed this tutorial
Hope you will enjoy you newly rooted BlueStacks.
Tweak your Bluestacks and share your .vdi files to everyone.
Credit goes to rumbla (mybot.run) for the original tutorial how to modify root.fs
And me for this new tutorial
Here are the links that helped me a lot to copy/paste text and also files between guest operating system (Ubuntu) and host computer (Windows 10)
"How do I tell if virtualbox guest additions is installed and working correctly" on Ubuntu Forums
"Virtualbox and shared folders - permissions problem" also on Ubuntu Forums
Also I had to chown root:root "files"
Working ................. so far, so good
Thanks a lot
I comfirmed that it still working on bluestack 4 (mac os) thanks a lot! <3
Note that if BS is "x86_64" then you need using files in "x64" folder!
evildog1 said:
BlueStacks 2.2.17.6203 is introducing "VirtualBox VMs".
The filesystems have been changed to "vdi format" (VirtualBox).
For linux experts: if you know how to mount and modify .vdi without VirtualBox, skip to step 9.
Well, let's get started!
First of all, to root BlueStacks this way you need VirtualBox and you have a Linux OS installed. If you just got started, I'll recommended Ubuntu, you can follow the guide installing Ubuntu on BirtualBox. http://www.wikihow.com/Install-Ubuntu-on-VirtualBox
Also, you will need some linux knowledge. It's not necessessary, but I won't provide any support about the part dealing with linux commands. Just follow the instructions and probably you will be able to root it, but it might not be that simple.
The second mandatory stuff you will need is the Android App called SuperSU. At this time, you should be able to find the latest SuperSU. The instructions should be the same with other SuperSU versions.
Here is a direct link http://www.supersu.com/download
This tutorial assumes you already have an installed BlueStacks you wish to root, but make sure Bluestacks and Ubuntu isn't running isn't running. So, let's get started.
In this tutorial i'm using Ubuntu.
1. MAKE A BACKUP OF ROOT.VDI FILE FIRST!
2. To modify Root.vdi, you need to mount it in Ubuntu virtual machine. Select Ubuntu and click Settings -> Storage. Select Controller: SATA and click on the HDD with green plus symbol.
3. A dialog box will appear. Select Choose existing disk
4. Navigate to Bluestacks directory where you installed. Select Root.vdi and Open
ProTip: você pode montar Data.vdi e SDcard.vdi para transferir arquivos entre o convidado e o VDI.
5. Root.vdi deve ser adicionado ao Storage. Clique OK
6. Inicie o Ubuntu no VirtualBox
7. Ubuntu: em sua área de trabalho, você deve ver o ícone cinza do disco rígido na barra de tarefas direita. Sim, esse é o arquivo de imagem root.vdi que foi montado e o nome do disco deve se chamar Volume de 8,6 GB
8. Extraia a pasta x86 do arquivo .zip (Recovery Flashable.zip) e /common/SuperSU.apk em algum lugar do Ubuntu. Bluestacks é baseado no Android x86.
8,1 Se você já fez o download em seu computador host, clique em Dispositivos -> Arrastar e soltar, selecione bidirecional e você pode transferir o arquivo para o convidado
Se você ainda não fez o download, faça o download em http://www.supersu.com/download e clique em Recovery Flashable.zip
9. Copie os seguintes arquivos SuperSU para o root.vdi montado
Adicionar arquivo: / x86 / su -> (Volume de 8,6 GB) / android / system / xbin / su
Renomear arquivo: / x86 / su ---> (Volume de 8,6 GB) / x86 / daemonsu
Adicionar arquivo: / x86 / daemonsu ---> (Volume de 8,6 GB) / android / system / xbin / daemonsu
Adicionar arquivo: / x86 / supolicy ---> (Volume de 8,6 GB) / android / system / xbin / supolicy
Adicionar arquivo: /x86/libsupol.so ---> (Volume de 8,6 GB) /android/system/lib/libsupol.so
Adicionar arquivo: /common/Superuser.apk ---> (Volume de 8,6 GB) /android/system/app/Superuser.apk
10. Você precisa alterar as permissões do arquivo para que o SuperSU funcione corretamente. Abra o terminal e digite os seguintes comandos. Digite sua senha quando solicitado
Nota: o nome do disco pode ser diferente. Você pode verificar clicando com o botão direito em Volume de 8,6 GB e selecione Propriedades
ProTip: Digite sudo chmod xxx no terminal e arraste um arquivo para obter o caminho completo como abaixo. Pressione a SETA PARA CIMA no teclado para mostrar o último comando usado.
sudo chmod 755 '/ media / test / <disk udid> / android / system / xbin / su'
sudo chmod 755 '/ media / test / <disk udid> / android / system / xbin / daemonsu'
sudo chmod 755 '/ media / test / <disk udid> / android / system / xbin / supolicy'
sudo chmod 644 '/ media / test / <disk udid> /android/system/lib/libsupol.so'
sudo chmod 644 '/ media / test / <disk udid> /android/system/app/Superuser.apk'
Os arquivos devem pertencer a root: root. Não há necessidade de alterá-lo no Ubuntu.
11. Agora precisamos iniciar o "daemonsu" a cada reinicialização. O procedimento de inicialização do BlueStacks é bastante simples. Parece que só existe android / system /etc/init.sh. Portanto, abra android / system / etc / init.sh em seu editor de texto Linux preferido, vá até o final do arquivo e pesquise por:
[CÓDIGO] init | "")
fazendo
;;
esac [/ CODE]
Adicione isso
[CÓDIGO] init | "")
fazendo
/ system / xbin / daemonsu --auto-daemon &
;;
esac [/ CODE]
Eu diria que terminamos agora! Desligue seu Virtualbox
12. Agora você pode iniciar seus BlueStacks. Quando ele for inicializado, inicie o SuperSU via Play Store.
Você será avisado sobre uma atualização do SuperSU. Escolha o caminho "normal" e após a atualização reinicie seus BlueStacks.
13. Deve ser isso. Agora seu BlueStacks está enraizado.
Para ter certeza, você deve abrir sua PlayStore e instalar o RootChecker de sua preferência.
Uma tarefa adicional que você pode querer fazer seria usar alguns aplicativos como "/ system / app Mover" e "System App Uninstall" e alterar SystemDefaultAppLauncher e SystemDefaultAppBrowser.
Eu geralmente instalo o Nova Launcher.
Além disso, como Root FileExplorer, eu instalo o X-Plore.
Você pode querer instalar um CatLog também!
Espero que tenha gostado desse tutorial
Espero que você goste de seu BlueStacks recém-enraizado.
Ajuste seus Bluestacks e compartilhe seus arquivos .vdi com todos.
O crédito vai para rumbla (mybot.run) pelo tutorial original sobre como modificar root.fs
E eu para este novo tutorial
Click to expand...
Click to collapse
Não dá
Hi guys, I have a DL 3411 Tablet with Android 5.1, and looks like impossible make root in them, please, if you can help, help me please
Some information about it:
Genuine Intel(R) CPU 1,04 GHz
Cores: 4
Architecture: x86
CPUID: 6.5d.1
Codename: SoFIA 3GR
Process: 28 nm
L1 D-Cache: 4 x 24 KB
L1 I-Cache: 4 x 32 KB
L2 Cache 2: x 512 KB
Clock Speed: 208 MHZ - 1,04 GHZ
GPU Vendor: ARM
GPU Renderer: Mali-450 MP4
Model: Tablet_DL_3411 (TabKids_Plus)
Manufacturer: DL
Board: rk3osdk
Hardware: soflaboard
Screen Size: 5,55 inches
Screen Resolution: 600 x 1024 pixels
Screen Density: 214 dpi
Total RAM: 933 MB
InternaIStorage: 4,41 GB
Android Version: 5.1.1
API Level: 22
Bootloader: 1605.1 00_M1 S1
Build ID: LMY49F release-keys
Java VM: ART 2.1.0
OpenGL ES: 2.0
Kernel Architecture: i686
Kernel Version: 3.14.0 (eng.pb105.20160808.112201)
Olá, consegui fazer o root com o Magisk manager.
Ativei o modo depuração usb, e ativei permitir desbloquear o bootloader no modo desenvolvedor.
Depois usei os comandos para desbloquear o bootloader:
./adb reboot fastboot
-ele reinicia no modo fastboot e fica com a tela preta.
./fastboot oem unlock
./fastboot oem unlock confirm
assim consegui desbloquear o bootloader
Baixei no site DL a fimware e extrai os arquivos da firmware deste tablet com o "flstool.exe" programa que fica na pasta de instalacao do "intel flash tool" e separei o boot.fls.
./FlsTool -x "nome do aquivo firmware.fls"
./FlsTool --extract-prg "nome do arquivo firmware.fls"
ele vai extrair todos os aquivos da firmware, e separei o arquivo que tem o nome boot.fls e o copiei para o tablet.
Instalei o apk magiskmanager atualizado, apos aberto cliquei em instalar e quando pediu o arquivo boot.img para corrigir, indiquei o arquivo boot.fls que extrai da firmware. Ele vai gerar outro arquivo boot.img, copiei este arquivo do tablet para pasta onde esta o adb/fastboot no pc.
Enviar o boot.img gerado pelo magiskmanager via fastboot:
./adb reboot fastboot
espere o tablet reiniciar
./fastboot flash boot "nome do boot.img gerado pelo magisk"
./fastboot reboot
depois disso ja vai estar com root.
pode confirmar instalando o root checker.
Hi, I managed to root with the Magisk manager. I activated the USB debugging mode, and I enabled to allow the bootloader to be unlocked in developer mode. Then I used the commands to unlock the bootloader: ./adb reboot fastboot -he restarts in fastboot mode and stays with the black screen. ./fastboot oem unlock ./fastboot oem unlock confirm so I managed to unlock the bootloader I downloaded the DL site to fimware and extracted the firmware files for this tablet with the "flstool.exe" program located in the installation folder of the "intel flash tool" and separated the boot.fls. ./FlsTool -x "file name firmware.fls" ./FlsTool --extract-prg "filename firmware.fls" it will extract all files from the firmware, and I separated the file that has the name boot.fls and copied it to the tablet. I installed the updated magiskmanager apk, after opening it I clicked install and when asked for the boot.img file to fix it, I indicated the boot.fls file that it extracts from the firmware. It will generate another boot.img file, I copied this file from the tablet to the folder where the adb / fastboot is on the pc. Submit the boot.img generated by magiskmanager via fastboot: ./adb reboot fastboot wait for the tablet to restart ./fastboot flash boot "name of the boot.img generated by magisk" ./fastboot reboot after that it will be rooted. you can confirm by installing the rot checker. all this information was extracted here from the xda forum
Hint: Replace in this thread's title term tablet by your tablet's brand & model thus mainly owners of such a tablet get addressed.
AFAIK at least 3 Android tablets with Intel CPU exist.
Hello,
I have managed to brick my Mediapad T5 by accidentally flashing to wrong board software. Currently, the screen is black and does not turn on at all. The power and volume buttons do nothing. I can, however, connect to the device via fastboot and test point. I think a need to use IDT to flash the board software to at least get the screen back. I have found the attached xml file for the board software but I cannot find the actual firmware itself. Looks like it's called AGS2-L03-rogers-ca after viewing xml file.
Does anyone know where I can find board software for AGS2-L03(C654)?
Thanks
I also have the same problem.
in my case, I don't know what caused this problem. Well, I unlocked the bootloader and then booted to fastboot. From the fastboot level, I did
Fastboot erase fastboot
fastboot erase kernel
Fastboot erase ramdisk
fastboot erase recovery_ramdisk
fastboot erase recovery_vendor
fastboot erase vbmeta
Fastboot erase system
fastboot erase cache
fastboot erase userdata
Fastboot erase vendor
Fastboot erase product
Fastboot erase vbmeta
fastboot erase cust
then I downoaded software 8.0.0.151 AGS2-W09 and with the Huawei extractor I extracted files mentioned above. after that I did the installation software:
Fastboot flash fastboot fastboot.img
fastboot flash kernel kernel.img
Fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash vbmeta vbmeta.img
Fastboot flash system system.img
in while installation system img, dos returned me failure sparse (something) and after that my tablet is black and buttons do nothing.
I makes me wonder that installation image lineage 18 os (fastboot flash system lineage.img) is successful. But tablet still do nothing and has black screen.
userned said:
I also have the same problem.
in my case, I don't know what caused this problem. Well, I unlocked the bootloader and then booted to fastboot. From the fastboot level, I did
Fastboot erase fastboot
fastboot erase kernel
Fastboot erase ramdisk
fastboot erase recovery_ramdisk
fastboot erase recovery_vendor
fastboot erase vbmeta
Fastboot erase system
fastboot erase cache
fastboot erase userdata
Fastboot erase vendor
Fastboot erase product
Fastboot erase vbmeta
fastboot erase cust
then I downoaded software 8.0.0.151 AGS2-W09 and with the Huawei extractor I extracted files mentioned above. after that I did the installation software:
Fastboot flash fastboot fastboot.img
fastboot flash kernel kernel.img
Fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash vbmeta vbmeta.img
Fastboot flash system system.img
in while installation system img, dos returned me failure sparse (something) and after that my tablet is black and buttons do nothing.
I makes me wonder that installation image lineage 18 os (fastboot flash system lineage.img) is successful. But tablet still do nothing and has black screen.
Click to expand...
Click to collapse
Please give me a link fo download: 8.0.0.151 AGS2-W09 thanks
Me sumo a vosotros, pantalla negra y botones no hacen nada, solo al enchufarla al pc la reconoce en estado de fastboot. En mi caso estaba bloqueado por frp de google y segui los siguientes pasos:
1) desbloquee el gestor de arranque con potatoNV que me dio un nuevo codigo
2) ejecute fastboot oem unluck (codigo de potatoNV)
3) ejecutar fastboot flash recovery_ramdisk twrp.img (para instalar twrp)
A partir de aqui el dispositivo solo inciaba en twrp y no podia salir de ahi
4) intente instalar una rom oficial desde twrp pero el zip me dio error
5) accedi a la carpeta dload y dentro habia otro zip , este si me lo instalo y me produjo el brick (pantalla negra)
He probado unas cuantas cosas, incluso flashear igual que el compañero varios archivos de imagen uno por uno de la rom oficial pero nada, no encuentro solucion.
Podira ser porque no tiene archivo boot.img ? y este no lo encuentro en ninguna rom extrayendo del update.pp no sale ni recovery.img ni boot.img ......
ayuda por favor
GOOGLE DE TRADUCCIÓN AL INGLÉS:
Me uno a ti, la pantalla negra y los botones no hacen nada, solo que al enchufarlo a la PC lo reconoce en estado fastboot. En mi caso fue bloqueado por google frp y seguí los siguientes pasos:
1) desbloquear el cargador de arranque con PotatoNV que me dio un nuevo código
2) ejecutar fastboot oem unluck (código de potatoNV)
3) ejecute fastboot flash recovery_ramdisk twrp.img (para instalar twrp)
A partir de aquí el dispositivo solo arrancó en twrp y no pudo salir de ahí
4) intento instalar una rom oficial de twrp pero el zip me da error
5) Accedí a la carpeta de descarga y dentro había otro zip, este lo instaló por mí y produjo el ladrillo (pantalla negra)
He intentado algunas cosas, incluido flashear varios archivos de imagen uno por uno de la rom oficial uno por uno, pero nada, no puedo encontrar una solución.
¿Podría ser porque no tiene un archivo boot.img? y no encuentro esto en ninguna rom extrayendo de update.pp no sale ni recovery.img ni boot.img......
Help me please
I do not have T5 any longer, but when I had some problems in the past I used : Multi-Tool for HUAWEI & HONOR to unbrick. You can find it here:
Multi-Tool for HUAWEI & HONOR ⋆ TEAM MT Developers
The app is based on working with fastboot and adb modes of Huawei and Honor smartphones. Allows you to perform many actions with your device
pro-teammt.ru
Good luck.
garconblair said:
Ya no tengo T5, pero cuando tuve algunos problemas en el pasado, usé: Multi-Tool for HUAWEI & HONOR para desbloqueo. Lo puedes encontrar aquí:
Multi-Tool for HUAWEI & HONOR ⋆ TEAM MT Developers
The app is based on working with fastboot and adb modes of Huawei and Honor smartphones. Allows you to perform many actions with your device
pro-teammt.ru
Buena suerte.
Click to expand...
Click to collapse
Muchas gracias por tu ayuda, estoy probando el programa y en el apartado de unbrick me pide 5 archivos de imagen, 2 son el boot.img y el recovery.img. deduzco que el programa hace lo mismo que estuve haciendo manualmente pero al no encontrar estos archivos al extraer el uppdate de ninguna rom oficial pues sigo con el mismo problema. Si alguien sabe dónde puedo conseguir estos dos archivos de imagen del modelo huawei mediapad t5 ags2-w09 se lo agradecería eternamente.
TRADUCCION GOOGLE
Muchas gracias por su ayuda, estoy probando el programa y en la sección de unbrick me pide 5 archivos de imagen, 2 son boot.img y recovery.img. Deduzco que el programa hace lo mismo que yo estaba haciendo manualmente, pero como no encuentra estos archivos al extraer la actualización de cualquier rom oficial, entonces sigo con el mismo problema. Si alguien sabe donde puedo conseguir estos dos archivos de imagen del modelo huawei mediapad t5 ags2-w09 se lo agradeceria eternamente.
TRADUCCIÓN DE GOOGLE
Have you found a solution ? The AGS2-W09 firmware doesn't have boot.img and recovery.img. The equivalent to them are RAMDISK.img and RECOVERY_RAMDIS.IMG. Have you flashed them (fastboot flash ramdisk RAMDISK.IMG, and fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG) ?
garconblair said:
Has encontrado una solución ? El firmware AGS2-W09 no tiene boot.img ni recovery.img. Los equivalentes a ellos son RAMDISK.img y RECOVERY_RAMDIS.IMG. ¿Los ha flasheado (fastboot flash ramdisk RAMDISK.IMG y fastboot flash recovery_ramdisk RECOVERY_RAMDIS.I
Click to expand...
Click to collapse
Thanks again for your help, I've tried and it doesn't work. As a last attempt I have flashed one by one all the files extracted from the update.app (31 files....uff) and nothing continues on a black screen and in fastboot mode.
same one able to de bricked the tablet?
It cold be a hardware problem, check this out.
But during the upgrade to HarmonyOS I've once lost touch input in all recoveries so it could be also a software problem.
Has anyone found stock firmware .. I'm search for c654 .. bricked and can't get into fastboot