Hey guys!
This is my first post so, first of all sorry for my english errors and newbie questions.
I'm trying to find a way to set the device to boot up when plugged into the charger until see the charging animation. I know that have a lot of posts that talk about this but no one can give me a solution for Rockchip based devices.
I've bought an Alcatel One touch Evo 7 a few days ago, and other tablets based on the rockchip and all of them have the same problem.
I've bought an Allwinner A13 based tablet too and by downloading the script.bin, converting to fex and change the [target] power_start = 1 everything went simply perfect!
But i can't find how can i get or if i can get the script.bin from rockchip based device because doesn't exist the /dev/block/nanda, instead of this my boot mountpoint is /dev/block/mtdblock2. I've tried to mount the mtdblock2 as i've done with the nanda on allwinner but without success.
Another idea was add the "/system/bin/reboot" on the init.rc on charger area but i've downloaded the boot.img, unpacked, changed the init.rc and repacked, flashed via Batch Tools successfully but without any change. Simple like i never did any changes on the boot.img, don't change anything.
I've tried to put into fastboot mode and then will send the command "fastboot oem off-mode-charge 0", but i can't get into this mode. The tablet reboot's into bootloader mode but when i type fastboot devices on linux, mac and windows (even installing all the drivers) simply doesn't return anything.
Please if anyone can give me any idea or clue i'm very grateful.
Thanks!
Please check if the tablet say all time, that he was charging, also by not conected charger
Related
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
dazza9075 said:
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
Click to expand...
Click to collapse
I know this is old, but how did you flash the original recovery? I think I need to do this so that I can install the update ZIP for the Kobo 10. CWM is failing to install the file.
At first guys, excuse me if the topic isnt at right place but i cant find the right section.
So i have a Prestigio Multipad 8.0 HD (PMP5588C).I think i have bricked it.I erased NAND with Amlogic Image Burning Tool and now the device wont boot.The screen is black even when im charging it.I wont boot at all.I tried to boot in recovery but no succsess.Ive tried to boot it normally and in recovery (even when i charged it 10 hours usually it charges for 4 hours) but the screen is black.When i connect it with Power and Vol- buttons it shows up in the device manager as M6-CHIP and ive installed the drivers so now is World Cup Device.Ive tried to use Amlogic Image Burning Tool again but it fails on load spl.Any ideas?
Thanks in advance!
Best regards, Stoio.
Im sorry for my English but im from Bulgaria.
Unbrick amlogic tablets
Hello stoio
I have almost the same Tablet. It's a Prestigio PMP5580C, for me it is labeld as Intenso Tab 814, but they are completely the same. I have tried to find the u-boot.bin in the stock firmware, but I didn't sucess yet. I've downloaded several tools which allows me to make my 16 GB MicroSD card recognized as a 512 MB SD card, there I have to put the files on it to unbrick my tablet, it's amlogic (like my username) (someone told me that this is the chipset). It has a TOSHIBA TC58TEG6DCJTA00 NAND flash chip of 8 GB capazity. I also need help by getting my tablet unbricked.
In the future Inwant to learn with this amlogic based tablet how to create custom ROM's, recoveries and custom boot splash screens.
Thanks for any help, I reall appreciate your help,
Please note that I'm from Germany and my English is not good as it should used to be, but I have a dictionary (as a normal book) where I can get good communication with you. I like the idea of using english only.
Every Image (.img) were made with the dd command, I need to look inside in the images and open the content, I used a hex editor and tried to strip off the 2k of data, but I can't success. I'm using this tutorial:
I'm using this hex editor under linux: Okteta
I don't know how to delete the 2k of data. I need to know what content the partitions have to unbrick my amlogic based tablet, cause I'm seeing still the white android robot, and the charging battery or charged plugin picture, but this tablet doesn't have a bootloader or recovery so I'm out of ideas, the only way for me is to use a microsd card like an live cd to automatically let this tablet flash stock firmware, but where is it? Please help me out, I meight be wrong, it's possible that different repairing ways exist, too.
Hello,
I was asked to forward my problem here so here it goes:
Not a long time ago I bought Asus ME302C FHD 10 and tried to root it. I followed a guide but I can't paste link just now.
Anyhow, the guide told me to flash rooted system image. I did every step correctly except that after i rebooted it, my device got stuck on logo screen, sometimes saying "no command".
I would like to undo that by getting unrooted system image for my device or rather get a working rooted system image. I am not sure about other possibilities as I am not experienced in android rooting or anything related. I do have fastboot up and working.
Thank you a lot in advance.
Edit: I figured out that Asus website has factory system images, however I don't really know which one to use because they all are for different countries and I am not sure what device is mine. Is there a way to check parameters of your device without booting it?
Edit2: I messed with the device more and found out that adb doesn't recognize device, as in, running 'adb devices' nothing gets listed. However, 'fastboot devices' does output my device, not sure where the problem is. Also, firmwares listed on asus website are zipped files and I don't know how to flash them. I tried 'fastboot flash system zippedfile.zip' but it would give me an error.
Solved
After few sleepless nights and loads of browser tabs opened I finally managed to fix my device.
All I needed was to use a different SKU firmware from Asus website. Now I can finally boot it thanks to XDA developers team and their useful information on the forums.
Hello. I'll try to explain my problem because I really need some help.
A few days ago, I was normally using my Tablet ECS TR10RS1 Intel®.... I turned it off, went to sleep and the next day when I was going to use it again, the OS didn't start, so I tried and tried until I found a forum where they led me to restore a backup file because the original firmware/rom wasn't still available.... publicly. I tried that, but in the process, I accessed the EFI Shell... That wasn't trouble at all, I just plugged the keyboard and typed "exit", and then it let me to the BIOS... And that's when my real problem began: I restored the factory setting default... and it involves "disabling USB ports".... Now, AGAIN, I'm stuck on EFI Shell. But this time, I can not type "exit" since the keyboard is not recognized by the Tablet.
Then I pressed Vol UP + Power ON and I get access to another menu "DNX".... And that's what brings me here to your forum:
I was briefly reading that one of your members managed to flash the BIOS via DNX, so I was wondering if you guys could help me do that to my tablet because I'm not planning to have a really expensive paper holder.
Thanks in advance.
Jinky.
Not sure about your case. But as your tablet use clovertrail chip like my zenfone 5 n fonepad7 170CG, then there's some methods to unbrick like via fastboot, flashtool, or intel factory flash tool... all of above are required a valid firmware, at least a IFWI package then intel FFT can unbrick anyway. So try to find your need, as i tried to help u to find it, but most of webpages use spanish, then i didn't understand anything
Sent from my ASUS_Z00AD using Tapatalk
Ok, I know this isn't exactly an Android related problem, but I have no one else to help, so here goes nothing...
2 days ago I received a Teclast Tbook that had nothing on it. All I could do was access the BIOS.
I tried making a bootable flash drive and installing windows, but it didn't work, so I searched for a usb cable (the tablet only has usb-a ports) and finally found a usb-a to usb-a, so I downloaded everything I needed and was able to flash Android. It's buggy as hell, but it works. After that I decided to give Windows another go and made another bootable flash. This time it worked... Kinda.
I get a cmd windows and the installation starts, but it never gets to a 100%. I tried different setting in the bios and eventually broke everything... I turned fastboot on and tried to install again and that was it.
I can still access Android, but I can't get to the BIOS. I get a OEM1 ACPI Table Parse Error and it goes into bootloop until I press every key possible and get it to boot to Android.
There isn't a whole lot of information about this device online and I've searched and followed every guide I was able to find, but I'm still stuck. I hope someone here has experience with it and can assist me in some way.