I've flashed TWRP onto an Allwinner A33 tablet (on recovery partition), and now it's stuck. No matter what I do, holding any combination of buttons, it always boots back into TWRP again. I can't get into fastboot to try to fix it. I also can't do anything in TWRP, because the touchscreen doesn't respond.
The only thing I can do is access a shell through adb, but it's not much use either. All the "twrp" commands don't work, there is no twrp executable anywhere. I can do "poweroff" and guess what, right back to TWRP again. I can't even see the NAND devices, only SD card.
Which A33 tablet do you have? I have the v11 10.1" unbranded and found a firmware PH or PHGQA33GA10H0312N102v11 that works for tablet it's a china rom but everything works, using the new Phoenix usb pro 4.0, I hope this helps
The device is Logicom M BOT TAB 100.
After a lot of research I finally discovered a way to get out of recovery mode:
Get a microSD sniffer breakout board and a 3.3V USB UART adapter
Connect the UART adapter: TX=CD/DAT3, RX=CLK, GND=GND, VCC=not connected
Plug the adapter into the PC and open the serial console (eg
Code:
screen /dev/ttyUSB0 115200
on Linux)
Hold "s" in the terminal and power on the device; you should see boot messages and enter a shell
Run command:
Code:
setenv bootcmd "run setargs_nand boot_normal"
- this resets the boot mode so it won't boot into recovery
Run command:
Code:
boot
(or just turn off and on again) and it should boot up normally!
Still I'm using the stock ROM without root, so if you know of a ROM that will work, that'd be great.
EDIT: actually that command didn't fix it (I can't seem to save the change with any command), but I was able to enter Fastboot, flash the original recovery.img, and boot normally.
Related
Please HELP!
Yesterday I flashed my Odys Xelio (Allwinner A10) with CWM. After booting in a working state, I restarted in Recovery too full whipe and whipe dalvik, I installed gapps ans the compatibility.zip also from CWM.
After that I got stuck in a whitescreen. I can not access anything, not even CWM recovery anymore. In win 8 I only could see 1 to 2 undefined devices (should be a problem with the device AND a driver issue).
In Linux I could see a device in adb yesterday and could put it into "adb reboot recovery". Still whitescreen on the tablet, but I could push a recovery file with adb to the /sdcard/. Rebooting didn't bring me to another state.
Today I am not able to connect via adb. It always tells me "List of devices attached" and an empty list.
Display should be okay, no cable issue or sth. else. I really hope someone can help. Perhaps theres a way to JTAG the devices or there is a trick with pressing some buttons and using the USB cable...
BTW: While booting into CarbonRom the first time, the button-behaviour was strange or even totally not working. Perhaps that's a point?
THX in advance
EDIT: Now, after playing around with a needle into a "reset-hole" I finally found a way to see the device in adb. How do I go on!?
Hello Ive got a bit of a problem actualy a few with my pipo U1 Pro
I installed CWM V6.o.3.1 and rebooted fine, pipo boot image was normal, then i installed from ext SD card Decontaminat V3.1
after install the screen was Split at 2/3 and touch orintation was off with buttons in wrong corners
so i read alot found change in build.prop (ro.sf.hwrotation=270) from 270 to 0 and reinstalled form ext sd card
all it fixed was position of touch screen the image of ui was still split 2/3 and out of rotation.
i reinstalled CWM fron ext sd card reboot ant the cwm recovery is straigt on the vertical and the android shows in center of screen, but ther is a fine line showing where the screen was split in the os.
after reboot the os is still split 2/3 image i have to us the show touch function to navigat the touch field to make thins work
i had TNT pipo u1 pro.img installed before and was rooted worked fine but latly had a few minor problems with it so i desided to chand up a bit.
second problem is i cant get ADB , android studio or rkbatch tools to find my tablet, usb debugging is on, tried the load from adb sideload function in cwm
im running linux mint 17 added udev.rules rebooted every thing many time s swapped usb plugs cords you name it.
as it is the tablet works but the ui is buggered up and touch is off
any help would be verry appricated
mike
May be bricked now ?
I have the pipo stuck in what might be a boot loop?
just says decontaminate with a split screen on bootup shows pipo image then goes to decontaminate screen and nothing.
lsusb shows device { Bus 002 Device 009: ID 2207:0006 }
shows Android device in file manager But Error unable to mount android unable to open mtp device
pushing the buttons '' esc, +vol then power gets nothing.
pushing +vol, power gets nothing
incerting usb and pushing +vol gets nothing
only thing gets anything is push and hold power, CWM is not working cant boot to cwm
tried a bootable sdcard still no boot
was a nice Tablet till decontaminat screwd the screen up
got recovery yeah !!!!
found a way into the cwm recovery through adb.
i added a line into the file here.
/yourusername/.android/adb_usb.ini
its a hidden file added a simple line as root user
0x2207
saved file and rebooted computer.
will post again if i can recover the pipo.
buggered
had total access to the pipo.
i used flash_image to install freaktbs ryley rom for the pipo u1 pro.
now im stuck in a worse position. the kernal.img was not for the pipo.
he was playing with a another tablet and left its kernel.img as kernel.img and had pipo kernel as 1kernel.img
so im stuck with no touch support on the screen and its not defaulted to usb debug mode.
i can see the button acking to allow debug when i connect to usb on linux but no access to touch.
also the rom didnt have any tools for adb installed in recovery /system/bin.
no adb shell support.
only access is adb ls /
to read files and push pull commands.
any ideas on how to edit the default.prob make it stick through reboot and get it to debugg after reboot ?
this sucks MR.RYLEY built a bad rom I was almost into my pipo again.
my guess is the decontaminat rom was using a similar kernel to ryley to get the screen all buggered up.
Dear everyone,
I have an ASUS MeMoPad 10 (ME103K) here which I vowed to fix. The user wanted to revert to Factory Defaults, lost power or something like this, and ended up with a bricked device.
I can only start it with power button + volume up, into Fastboot. Secure Boot is enabled.
I have Android SDK and minimal FastBoot installed. Have the Google USB Drivers on my desktop.
I tried flashing SuperBoot (ADB), but ADB simply lists "Waiting for Device". No devices can be listed. It does show up in Windows Device Manager: ASUS Android Bootloader Interface.
I have the following files available:
- SuperBoot r5
- Kernel: l-8064-r1_V12.16.1.12-201508071139-foss.tar
- UL-K01E-WW-12.16.1.12-user
- recovery-original-me103k
There is apparently no recovery.img for this device. The boot.img is in the UL-K01E-WW-12.16.1.12-user file
Power = ASUS logo then goes black
Power + Volume up = Fastboot
Power + Volume down = /
Power + Volume up+down = /
Is this the place I should be looking? I'm honestly not sure if I can catch up with the details: android.stackexchange.com/questions/124344/trying-to-flash-a-system-img-i-took-with-dd-failing
Any help would be much appreciated!
- Al
EDIT:
fastboot devices now detects #serialnumber
Alright, fastboot now detects my device. I installed PDANet which didn't do anything, and then downloaded another adbfastboot package which hit it.
I'm able to start writing boot.img, but that's what it stays at. It's an 8MB file, so it shouldn't take half an hour, I suppose?
I'm not getting any error message either, though.
EDIT: It seems that regardless of what commands I send, they stall and don't get executed. ADB doesn't seem to find any devices, only Fastboot does.
EDIT 2: Tried the same on my laptop. Different ports. Nothing goes further than for example "Writing 'boot' - that's it.
Bump (won't bump until tomorrow late)
B0mp
kab0mp
boink
Bwamp
Recover Asus Me103k (k01e)
1) Stock recovery:
View attachment k01e_stock_recovery.zip
3) Run it without flash:
Code:
fastboot boot k01e_stock_recovery.img
3) In recovery select to install UL-K01E-WW-12.16.1.12-user.zip (early placed on microsd)
4) Also can check boot ability:
Extract boot.img from update firmware zip UL-K01E-WW-12.16.1.12-user
And run it from fastboot:
Code:
fastboot boot boot.img
If Android loaded normaly after it, but after reboot you see FASTBOOT MODE, than execute this commands:
Code:
fastboot oem reset-dev_info
fastboot reboot
Asus MeMo pad ME103K/K01E bootloader unlock
sheinbo said:
Hi,
after all these years I remembered my asus memo... Such a fine displsay but ... . I discovered an unofficial rom for another old device ( samsung gt 5830) and so I'd like to ask you whether you know any possibility to "upgrade" the MeMo or any other way to pitch / patch it. Your reply here let me think that you are very attached to asus memo, maybe you are still interested.
Click to expand...
Click to collapse
Same here, running the device on Lollipop is awfully slow, KitKat is somewhat better though but those are the only two official ROM's which can be found and installed.
Tried to unlock the bootloader to try different ROM's but bootloader is locked, despite all info here on XDA, nothing seems to work and the bootloader remains locked. Unlock APK's also give no result.
Running out of options here, any suggestions will be appreciated.
Hi All - I was trying to install a new image on my zenpad and ended up bricking my tablet. I think I ended up formatting everything outside of droidboot.
It only goes straight to the droidboot provision OS now.
i.imgur.com/tnzb5YT.jpg
I've tried the following:
1) Fastboot - It connects, but i don't have privilege to boot from an image. I can only do readonly type of tasks
2) ADB - my computer doesn't detect the tablet when using ADB shell, i think because it would only work if usb debugging is on... which i can't even get to anyway
3) ASUS FLash tool - there's no raw image available for this tablet
It seems like my only hope is the SD Download... but i think I need an image for that too? Any ideas and guidance please?
http://forum.xda-developers.com/u/repair/hard-brick-asus-zenpad-s8-z580ca-z580c-t3465203
I've got an Android box with limitations that allows a terminal emulator to send it commands, so I can for instance reboot to recovery.
Is there a command or set of commands that will allow me to reboot into a recovery image on an SD-card?
_________________________
Background, if needed:
I have a copy of TWRP that I'd like to test to see if it is functional on this box and a tutorial I read indicated that if I
1. have an SD card with the recovery.img,
2. press the reset button (it's in the AV jack), and
3. plug in the power at the same time,
I should be able to run TWRP in memory, no flashing required, to test the functionality of the version of TWRP.
It didn't work. No TWRP, it just started stock recovery. Perhaps I screwed up the process, but I tried several times. The operation doesn't seem to need a PhD.
[A95X MAX TV box, s905x2 chipset. The TWRP version is supposedly for a generic s905x2 box.]