Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

DigiLand 10.1 DL1010Q MT8127

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    DigiLand 10.1 DL1010Q MT8127

    [Quote = zmagami; 284317] Hola a todos, estoy en la necesidad de mucha ayuda de algunas personas que saben lo que están haciendo .. Tengo dos tabletas DL1010Q. Rompí una por mi propia culpa, el otro está bien. He estado recorriendo y leyendo y pruebas y no puedo arreglar lo rompí. He eliminado todos los archivos .ODEX de la población rom y ahora no puedo arrancar. Después de leer algunos de los puestos en otros lugares, parece que esto es lo que me rompió la tableta, pero no estoy 100%. Uso de las herramientas MTK he respaldado mi dispositivo de trabajo, tengo boot.img, recovery.img, etc He intentado intermitente el system.img usando fastboot pero creo que el gestor de arranque está bloqueado por lo que nunca hace nada, sólo se sienta en el indicador, nunca muestra ningún progreso ni nada. Han intentado al menos 5 veces con el mismo resultado. Herramientas MTK no apoya el MT8127 así que no puedo tirar de un archivo de dispersión, sin embargo, desde el vertedero rom hay un firmware.info que se ve casi exactamente igual a lo que el archivo de dispersión debe ser similar, pero SPFT no le gusta, por lo que es falta algún formato o algo .. No tengo ni idea. Me trató de utilizar herramientas MTK para hacer una recuperación personalizada pero vale errores hacia fuera. Una vez más, probablemente debido a que el MT8127 no es compatible. Mi siguiente intento fue la creación de una firmaron .zip que sería reemplazar los archivos .ODEX utilizando Sideload adb través de recuperación de las poblaciones ... esta carga y comienza a correr y la da "Error de instalación" y se cierra . Vi eres deseos y la esperanza de que alguien de aquí podría asumir el reto porque esto está más allá de mis habilidades .. Tengo un trabajo, enraizada tableta, así como un volcado completo usando Herramientas MTK y estoy encantado de proporcionar todo lo necesario de estos archivos, o si necesita algo más, hágamelo saber y voy a tratar de conseguirlo! Todos los archivos están en mi Google Drive https://drive.google.com/folderview?...Uk&usp=sharing [/ COTIZACIÓN]

    hola henry me llamó y yo tengo el mismo problema con la misma mesa y quieren saver si a reparar la tabla que seria me de mucha ayuda si usted repara como la suya

    Comment


      #17
      ​hello henry called me and I have the same problem with the same table and want saver if you repair the table you serious me much help if you repair like yours

      Comment


        #18
        HELP!!!

        I have a Digiland DL1010Q. I had rooted it using KingRoot. It recently had a wireless update, NOT system update. I did the update and when it rebooted into recovery mode it got stuck. I can see Android system recovery screen with the options for
        1. reboot system
        2. update from ADB
        3. update from sdcard
        4. apply update from cache
        5. wipe data/factory reset
        6. wipe cache partition
        7. backup user data
        8. restore user data

        I have attempted every method. I can see info and recovery folder on drive and get a NO Command error when applying it. I've wiped cache/data/factory reset to no avail and still can see data on the tablet. It is obviously bricked, but soft bricked I believe. How can I push or get a stock or modified ROM back on this tablet so it will boot?

        Comment


          #19
          Go to website download software.

          Comment


            #20
            Awesome, thanks for the link. I had almost given up on DigiLand. Downloading now. I'll post my findings for anyone following or with the same issue.

            Comment


              #21
              Originally posted by djregehr View Post
              HELP!!!

              I have a Digiland DL1010Q. I had rooted it using KingRoot. It recently had a wireless update, NOT system update. I did the update and when it rebooted into recovery mode it got stuck. I can see Android system recovery screen with the options for
              1. reboot system
              2. update from ADB
              3. update from sdcard
              4. apply update from cache
              5. wipe data/factory reset
              6. wipe cache partition
              7. backup user data
              8. restore user data

              I have attempted every method. I can see info and recovery folder on drive and get a NO Command error when applying it. I've wiped cache/data/factory reset to no avail and still can see data on the tablet. It is obviously bricked, but soft bricked I believe. How can I push or get a stock or modified ROM back on this tablet so it will boot?

              So far in my searching since i bricked my tab there are no stock roms or otherwise. Hopefully this is it!

              Comment


                #22
                Even if this is the ROM, (I'm downloading it at the moment) How do I use it when the bootloader appears "closed" and fastboot and adb isn't flashing files??????

                Comment


                  #23
                  I can confirm that this worked for me, I just flashed my tablet and it works now!! *happy dance*
                  Unpack all the archives, there is a copy of SP Flash Tool included. There is an excel with instructions. If you need help, let me know!

                  Comment


                    #24
                    The system image provided by DigiLand appears to be the original stock image, out of the box. After flash, it reports that a wireless update is available. I captured a copy of this update so I can play with the updater-script so I can get the correct settings needed to create a custom ROM. I created a TWRP Recovery for the device but it fails to boot, I imagine that as vampirefo originally mentioned TWRP makes the recovery too large, and even though it flashes without error, its not compatible. Original recovery image is roughly 5MB and the TWRP is just under 15MB, so there is a huge increase there. Though it would be nice to have touch recovery

                    Next I'll try and make a PhilZ Recovery because last I checked the CWM build server was broken. You can submit jobs and upload your files but when you go to retrieve your finished recovery it just gives a broken link and an error message. I'll keep checking to see if they ever get it running again, CWM would probably be the most stable since it is the smallest.

                    In the meantime, it seems entirely possible to create a custom ROM for this device using the files provided by DigiLand. If I can't get custom recovery working, the custom ROM will only be flashable via SP Flash Tool... which I guess is just fine. Just a little more hands on then using a custom recovery and a flashable zip...

                    As a side project, I would love to be able to alter the partitions of the device.. Instead of 2GB of /data and 11GB of emulated external storage I would much rather prefer something like 4GB /data or maybe split it half and half. That's on the back burner though. First we need custom recovery, and a custom ROM. I'll update tomorrow with my progress.

                    Comment


                      #25
                      So, TWRP Recovery comes out to 14.3MB and does not boot. Philz Recovery comes out to 12MB and does not boot. Looks like it's SP Flash Tool for all custom ROMs for this device, for now at least. Also as a note, MTK Droid Tools does not properly support the MT8127 SoC of this device, so it is limited. It cannot create us a CWM Recovery. I uploaded the recovery.img to the CWM Build Server (again...) but it is still broken.

                      Comment


                        #26
                        Originally posted by vampirefo View Post


                        Well I was one of those who got in touch with them to publish the flasher program and the firmware, well anyway thanks to all
                        Last edited by HENRY CARLOS; 08 April 2015, 06:26. Reason: I worked great

                        Comment


                          #27
                          Hi! I just found this thread. Have you been able to move forward with the custom rom¿ that would be great.
                          Thanks

                          Comment


                            #28
                            I am also curious about any custom roms or kernals

                            Comment


                              #29
                              Originally posted by zmagami View Post
                              The system image provided by DigiLand appears to be the original stock image, out of the box. After flash, it reports that a wireless update is available. I captured a copy of this update so I can play with the updater-script so I can get the correct settings needed to create a custom ROM. I created a TWRP Recovery for the device but it fails to boot, I imagine that as vampirefo originally mentioned TWRP makes the recovery too large, and even though it flashes without error, its not compatible. Original recovery image is roughly 5MB and the TWRP is just under 15MB, so there is a huge increase there. Though it would be nice to have touch recovery

                              Next I'll try and make a PhilZ Recovery because last I checked the CWM build server was broken. You can submit jobs and upload your files but when you go to retrieve your finished recovery it just gives a broken link and an error message. I'll keep checking to see if they ever get it running again, CWM would probably be the most stable since it is the smallest.

                              In the meantime, it seems entirely possible to create a custom ROM for this device using the files provided by DigiLand. If I can't get custom recovery working, the custom ROM will only be flashable via SP Flash Tool... which I guess is just fine. Just a little more hands on then using a custom recovery and a flashable zip...

                              As a side project, I would love to be able to alter the partitions of the device.. Instead of 2GB of /data and 11GB of emulated external storage I would much rather prefer something like 4GB /data or maybe split it half and half. That's on the back burner though. First we need custom recovery, and a custom ROM. I'll update tomorrow with my progress.
                              Do you happen to still have the system image from digiland they took it off their site and I am in the constant reboot =P
                              thanks

                              Comment


                                #30

                                Comment

                                Working...
                                X