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.]
Related
device : Dupad K1
android version: 4.2.2
baseband version: MOLY.WR8.W1315.MD.WG.MP.V1.P7,2013/09/10 17:18
built number: SPMTK6572M431WP02V07
CPU MOdel: ARMv7 Processor rev 3 (v71)
I had install boot animation app after rooted my device and installed a boot screen... after restart device got stuck in boot screen that i installed....
have online nandroid backup but dont know how to restore it
dont have cwm...
please someone help me to regain my device
Recovery mode
Go to recovery mode.
Do you have Android SDK installed in your machine or any Linux substitute in case you are a Linux user? You'll need it.
Read before attempting.
-Find the key combinations that applies to your phone.
-Get into recovery mode pressing the specific keys.
-Connect your device through USB port.
-Write in terminal or cmd:
Code:
adb devices
-if a device is connected proceed, if not, find what's going on.
-Write in terminal or cmd:
Code:
adb reboot recovery
-Find the desired ROM (The one made for your device or a previous system backup that you have made when the phone still worked), ensure it's safe and specific made for your phone.
-There must appear some options showing in your phone screen or maybe the Android robot laying on its back, you'll need to see the options, click buttons until you see them.
-Choose the line that says "apply update from ADB".
-Use the command in Terminal or cmd:
Code:
adb sideload yourzipfile.zip
-It must be a zip file, sometimes you need to unzip the zip file just to find another zip file (usually named update.zip)
-It must show the robot in a different position and some yellow lines showing you the progress, if something goes wrong you'll know, if everything goes fine, good.
-Restart the phone and you're done.
If you can't load the file with adb sideload command, copy the zip file in the SD card and choose apply update from SDcard from the recovery menu, locate the zip file and apply it.
You should be fine if you use the right Android version or backup.
Good luck. If this doesn't works or goes easy as I say, let me know.
Prerequisites:
Can boot into recovery
A working bootanimation.zip
Adb....if you dont have it download minimalistic adb and fastboot for windows.
Okay lets get down to business....
1.First boot into recovery and then select apply update from adb and type -'adb devices'
This will open up the comms port and start adb comms with the device.
2.Now type adb push <bootanimationfile>.zip system/media/
3.and voila you will have revived youtlr device.
Hit thanks if this helped.
Hey Everybody!
I am new to this forum, looking for a way to root my trekstor Surftab breeze 9.6 Quad. I already tried out the recommended tools, unfortunately none of them worked out. Is anyone of you aware of a method rooting the tab? Or did anyone already rooted it?
First ofall I am looking for a way to move files and apps to the external sd and delete pre-installed apps. Farther, if possible and available, a custom rom would be pretty amazing.
I'm only familiar to nexus root toolkit on my old nexus 4, otherwise I'm a newbie in rooting.
Maybe there's some of you able to help me. If necessary, I will look up more information on the tablet.
Lucas
Maybe as an Update:
Trying to build a working adb connection using the andorid sdk tools, the surftab is not listed as a device in "adb devices"
Anyone out there who can help me with the tablet?
Alright, new update for today.
I was able to get a driver running and the root-toolkits like KingoRoot, KingRoot, One Click root etc. noticed the device, I even was able to start the rooting, but all of those tools said "Root failed" or "Your device is soild to root".
Looks like those one click solution aren't able to root the surftab. I also tried towelroot and framaroot, both without any success.
I am still looking for help
If you are still interested, I successfully dumped whole eMMC memory from this tablet, so I can send you, for example, the boot partition. You can try patch it with Magisk
The magic
Yes, if it's not difficult for you, you can share the firmware. I will be grateful
Hi!
I attached xz-compressed stock boot.img for you!
Also, I have full eMMC dump, but:
recovery partition data are not usable (overwritten by uncompatible recovery image during mine tests)
no data partition
no platform bootloader partitions mmc0boot0 and mmc0boot1
Trekstor-Surftab-Breeze-9.6-ST96416-1-emmc-dump.dd.xz [1.12 GB]
Decompress and use kpartx tool (need force to ignore omitted data partition)
I have this tablet rooted now, so you can ask me for anything about it.
With love for all open source,
petabeda
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
petabeda said:
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
Click to expand...
Click to collapse
I have two surftab tablets. One version of the SIM card is fully functional. Another wifi version will not load. When loading, the orange logo at the moment of "collection" freezes. If there is, you can go into recovery even factory reset.
But nothing changes. I believe that the EMMC resource has been exhausted and therefore this behavior.
and to be honest, I don’t know how to write the partition. Since only the adb sideload command is available in recovery mode. Apparently, it is impossible to overwrite the firmware except through the programmer.
Until that time, I could not even pull out the firmware. Since there was no root access
Thank you for your help. As a thank you, I will give you a link to a tool to repair the Nexus 7 bootloader. Through a vulnerability in the tegra cpu. As I understand it, I use this method to hack the nintendo switch. I personally bought 4 nexus 2012 on the secondary market and one of them was able to restore in this way. They of them had a damaged eMMC other power controller. And even with a soldering station, I could not replace it because there is no suitable frame for the reball. In general, nexus are not bad, but there is very little disk space for installing google services and GAPPS are useless. And it is difficult to change partition. And it makes no sense because of the available firmware.
I see, you can''t unlock bootloader, because your device is not bootable at all. So, there is no way to get into fastboot mode?
We are anti e-waste fighters giving second chances!
The first photo is the available recovery menu. Where after choosing a factory reset, nothing changes. And through the adb update, only sideload mode is available.
The factory partition is not corrupted as the restore completes successfully. But the download fails. And not just does not occur, but freezes as in the screenshot above. Most likely a hardware problem eMMC.
Earlier, I saw something similar, for example, in Asus Zenpad, if turn off or connect the camera incorrectly, then the download stops. But here animation is stuck.
I don't know how to check eMMC exactly.
logs files is empty
And with recovery, no commands are available (like adb or fasboot)
There is a one way how to diagnose/repair/have fun with that Trekstor tablet - If you could and want to disassemble it:
have your tablet powered off
disassemble the tablet
carefully disconnect FFC cables (display and digitizer)
remove mainboard screws
at back side in the center of the board, there are three testpoints.......yes you are thinking right, these are actually 1.8V UART signals and GND
Connect these signals to your serial converter (in my case, Raspberry Pi), be careful and talk with the same loundnesses
Don''t power on the tablet, only plug usb cable, tablet will try boot and run healthd (charging mode with battery animation)
Your console will show you the magic (PBL/SBL) bootloader messages and Linux log and event, maybe, the console (though no root), lalalal (/dev/ttyFIQ0)
Wish you luck
After that, if everything goes well, you should be able to use reboot fastboot command to get fastboot mode !
I have a problem connecting to Blutooth. I bought a car 2DIN radio for android. My phone turns on blutooth and connects to a call without a phone call. My radio with other smartphones connects seamlessly, has a problem with my phone only. My phone connects properly with the handsfree, with the speaker and other devices, just does not want to connect with my radio. I had an original Image, now I changed to MUI, but it is the same.
Is it really so difficult to repair if no one else has encountered such a problem?
Help
I'm fighting for 3 days and I do not know where I'm making a mistake. I was looking for a solution for bluetooth connection with 2DIN radio. I found the image in EUI 5.8 15S still works well. I had TWRP installed so there was no problem, I found the image I installed. Unfortunately bluetooth does not work. I wanted to install MIUI so I downloaded the image and here my problem starts. I am in TWRP unfortunately I can not access the phone memory. I will start everything from scratch. I will do everything as described:
I have ADB installed on my PC
on the phone I enter the system developer set
in the directory where I have downloaded twrp with shift PPM and the command window opens
adb devices command - correct answer
adb reboot command bootloader - telefin into bootloader mode
fastboot oem unlock command - correct answer
fastboot flash twrp twrp.img - install twrp
button + volume and power - twrp mode
in the twrp install button - and again the same I can not access the memory.
If I choose the memory, I have 0 mg memory and OTG memory
What I do is not where the error is.
wojt_wc said:
Help
I'm fighting for 3 days and I do not know where I'm making a mistake. I was looking for a solution for bluetooth connection with 2DIN radio. I found the image in EUI 5.8 15S still works well. I had TWRP installed so there was no problem, I found the image I installed. Unfortunately bluetooth does not work. I wanted to install MIUI so I downloaded the image and here my problem starts. I am in TWRP unfortunately I can not access the phone memory. I will start everything from scratch. I will do everything as described:
I have ADB installed on my PC
on the phone I enter the system developer set
in the directory where I have downloaded twrp with shift PPM and the command window opens
adb devices command - correct answer
adb reboot command bootloader - telefin into bootloader mode
fastboot oem unlock command - correct answer
fastboot flash twrp twrp.img - install twrp
button + volume and power - twrp mode
in the twrp install button - and again the same I can not access the memory.
If I choose the memory, I have 0 mg memory and OTG memory
What I do is not where the error is.
Click to expand...
Click to collapse
When you start it, is TWRP asking for a password? If it does, that means your phone is encrypted, which, for example, is the default for Indian firmwares. It's a bug, but not the end of the world. You have to hit cancel at the password prompt and restart recovery. It will eventually start without asking for a password and then you'll have access to the internal memory. Once, I had to restart TWRP about 10 times until this worked, so you have to be patient.
Thanks a lot. Actually I had to start again and it was OK. But now I have a bigger problem. I downloaded the picture MIUI 9. The installation ran smoothly. MIUI 9 has been installed but I can not take over the configuration. Even though the SIM card is inserted it does not see it. Can not find no IMEI. Can not set up MI Acccount. The phone is hot all the time and it's still on Mi Account. Can you stop it? Can I upload another image?
Yesterday at a late hour I managed to run everything on a regular basis on SmailSUI. I reinstalled the memory cleaner and it works fine. All the time I'm waiting for MIUI 9. As you work on this image you can check if BT is working properly. At me mixed with different images from this began. So far I have not found a system that works properly BT. When connected to another Android BT connects without a phone. You can not receive or call BT.
Thanks again for your help.
I have a FriendlyArm Nano PC T3 Plus board with a custom Android build and occasionally I would like to be able to update the Android build. At present I have not figured out how to do an OTA build for this board but a full update is good enough as all of the system configuration can be backed up to SD card prior to doing this and it's only used for a single application use anyway so easy to reinstall as part of the update.
The issue I have is that to update the OS from SD card, you need to power up the board with the BOOT button held on and then release this. That becomes difficult if the board is installed in the enclosure. I'd like to be able to do this from ADB via some form of command line input. Is this even possible?
The other option is to use recovery but this board doesn't seem to have this option in the build. Doing a reboot recovery cmd line simply reboots as normal.
v8dave said:
I have a FriendlyArm Nano PC T3 Plus board with a custom Android build and occasionally I would like to be able to update the Android build. At present I have not figured out how to do an OTA build for this board but a full update is good enough as all of the system configuration can be backed up to SD card prior to doing this and it's only used for a single application use anyway so easy to reinstall as part of the update.
The issue I have is that to update the OS from SD card, you need to power up the board with the BOOT button held on and then release this. That becomes difficult if the board is installed in the enclosure. I'd like to be able to do this from ADB via some form of command line input. Is this even possible?
The other option is to use recovery but this board doesn't seem to have this option in the build. Doing a reboot recovery cmd line simply reboots as normal.
Click to expand...
Click to collapse
Try "adb reboot bootloader"
toolhas4degrees said:
Try "adb reboot bootloader"
Click to expand...
Click to collapse
Tried that. Same effect, normal boot.
BUT, I wonder if I could make changes to the bootloader source to do what I need seeing as I have access to that too as source. I'll look into that today. Thanks.
Do you have TWRP or something installed on it? It might be a bit of a jerry rig solution, but I'd usually try and backup the boot partition as an IMG, transfer the file to the pc and run "fastboot boot boot.img" of the twrp image. that will technically push the boot.img to RAM and NOT flash it to the storage media, kind of a safe solution.
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.