and yet still nothing?
Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
TWRP for Amlogic devices.
Collapse
This is a sticky topic.
X
X
-
I must be missing some here, should I be able to boot twrp from an ext SD Card as a test prior to flashing it to my box? I have tried copying the image to SD and renaming to recovery.img yet when I reboot I end at the stock android recovery. I tried to make a bootable SD card using the amlogic bootcard maker , didn't work and I tried following this guide
and yet still nothing?
Originally posted by Nofan Tasi View Post
-
Originally posted by Nofan Tasi View Postsee posts #1103 #1109 #1129
Still at a miss why I can't boot twrp via SD though, I don't want to take a chance flashing without testing because as you know there are many variants of the MXQ Pro 4K.Last edited by tiff_lee; 07 January 2017, 08:35.
Comment
-
[QUOTE=tiff_lee;n620872]I must be missing some here, should I be able to boot twrp from an ext SD Card as a test prior to flashing it to my box? I have tried copying the image to SD and renaming to recovery.img yet when I reboot I end at the stock android recovery. I tried to make a bootable SD card using the amlogic bootcard maker , didn't work and I tried following this guide
and yet still nothing?
/QUOTE]
No one able to offer any pointers on booting twrp from an SD Card?
Comment
-
Originally posted by Nofan Tasi View PostHaving twrp recovery.img on SD Card and toothpick booting might go into twrp. Perhaps dtb.img is needed as well.
Comment
-
Originally posted by tiff_lee View PostOn my unit pressing the button (with toothpick) does absolutely nothing, the only way I can get into recovery is to boot the box and then using reboot app select reboot to recovery, however when rebooting to recovery it just goes to stock android recovery and doesn't boot the twrp image. Not sure what dtb.img is ill need to google.
- check if there is some script in android etc that would reinstall stock recovery upon boot, if so, then rename it
- copy twrp image to recovery partition with dd
Retry.
No need to seearch fot dtb yet.
Comment
-
Originally posted by Nofan Tasi View PostOK if you reboot into recovery fom android or adb or fastboot and boot stock recovery then you did not overwrite recovery partition or (some android do) android overwrote it again. You can:
- check if there is some script in android etc that would reinstall stock recovery upon boot, if so, then rename it
- copy twrp image to recovery partition with dd
Retry.
No need to seearch fot dtb yet.
In the end I booted TWRP via SDCard following instructions in post #9 here
once I was happy the custom twrp recovery worked with my device I then flashed it and now I have twrp permanently for what it's worth. Given that I can only boot into recovery by using app once the device has booted, if I ever soft brick it i'm going to struggle (with the reset button doing nothing leaving me no way to boot recovery).
Comment
-
Originally posted by Unkash View Postabdul_pt has forgot this post i think
I still waiting recovey for my r-box pro 3g
Files (blocks, partitions and recovey stock): https://mega.nz/#!OklnRYwK!786Y9yvF-...0uSZTS2uMFk580Originally posted by sandog View PostCan someone help me out with a link to the beelink GT1 verOriginally posted by Unkash View Post
Just doing a backup to USB as we speak.
When installed as the main recovery.img it does not seem to boot to recovery though. It stays at the boot logo.Last edited by lyricidal; 16 January 2017, 23:13.
Comment
-
Recently i patched the "Sunvell T95Z PLUS - Superceleron V1 Final ROM"
to work with my NEXBOX A1 (@Superceleron suggest me to find help from you for my problem!)
but i'm facing a problem with the TWRP recovery when i make a backup of the system of this rom
and to be more clear the problem is when i try to RESTORE the system!
i'm getting this error again and again :
"Error during restore process.
extractTarFork() process ended with ERROR: 255"
it seems to be "libbluetooth_jni.so" problem!
these are the last lines of the recovery log :
" ==> extracting: /system//app/Bluetooth/ (mode 40755, directory)
==> extracting: /system//app/Bluetooth/Bluetooth.apk (file size 1699022 bytes)
==> extracting: /system//app/Bluetooth/lib/ (mode 40755, directory)
==> extracting: /system//app/Bluetooth/lib/arm/ (mode 40755, directory)
==> extracting: /system//app/Bluetooth/lib/arm/libbluetooth_jni.so (symlink to /system/lib/libbluetooth_jni.so)
==> extracting: /system//app/Bluetooth/lib/arm/libbluetooth_jni.so (link to /system//system/lib/libbluetooth_jni.so)
tar_extract_hardlink(): failed restore of hardlink '/system//app/Bluetooth/lib/arm/libbluetooth_jni.so' but returning as if nothing bad happened
tar_extract_file(): failed to set permissions on /system//app/Bluetooth/lib/arm/libbluetooth_jni.so !!!
I:Unable to extract tar archive '/usb-otg/TWRP/BACKUPS/q200/2014-12-31--18-01-04_NEXBOX-A1-6.0.1-2017/system.ext4.win'
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
I operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'restore_select'
I:Set page: 'restore'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I operation_start: 'Copy Log'
I:Copying file /tmp/recovery.log to /usb-otg/recovery.log "
the name (NEXBOX-A1) is changed from me in the build.prop
and has nothing effect on this because i get the same error again and again, whatever name i put !
i know you you have a lot time out of this thread
but if you read it or anyone else who knows and wants to help please
it will appreciated....
thank you!
Comment
-
Hello,
What is the difference between TWRP_2.8.7.0_N200_emmc.img and TWRP_2.8.7.0_N200.img? I booted with the TWRP_2.8.7.0_N200.img from SD on my M8S (MBX n200) but want to flash it and wondering which one I need and how to do it?
Thanks!Last edited by FerociousAndroid; 24 January 2017, 00:39.
Comment
-
@abdul_pt
TWRP recovery Needed for the Mecool BB2-Pro 3GB DDR4 16GB
HERE is a link to my drive folder containing the Stock recovery dump as well as other useful files such as build.prop and various partition queries
like block.txt, by-num.txt, part.txt, Etc. There are also Partition Dump Scripts for anyone interested they can be edited to work with any device
if there are any problems with the provided link or more is needed please let me know
And I am definitely willing to beta test
Thanks in advance,
PhatboyJ
...
.Last edited by phatboyj420; 07 February 2017, 13:09.
Comment
What's Going On
Collapse
There are currently 4447 users online. 1 members and 4446 guests.
Most users ever online was 37,478 at 04:14 on 26 June 2024.
Comment