Hello folks,
Need help with my X96 2GB/16GB version. It's a S905x(p212) device with a Q5X v2.1 board. The Wi-fi chip version is RTL8189.
Here is what happened:
- Initially, it was running 6.0.1 stock which I upgraded to 7.1.2 using TX7 upgrade package( SD Card method - Erase bootloader option was selected) posted on another forum. The ROM upgrade was successful and I had a fully-functional ROM, in that even the IR remote’s power buttons were mapped correctly, so no mods were needed after flash.
- I flashed TWRP posted by @Ricky Divjakovski on xda-developers for S905x devices and later installed his Poison ROM. The Poison ROM couldn’t boot for me like others who reported this issue as well on Poison thread.
- I now went a bit adventurous and flashed MagicSee Iron 7.1.2 firmware(SD Card Method- Erase Bootloader selected). The upgrade went fine this time too, but the ROM had many hiccups and software would hang quite often. So, I decided to roll-back to TX7 firmware again.
- But my reset button stopped working. The ROM would still boot and I could load TWRP recovery too.
- I tried some other stuff to install stock recovery and install OTA packages. And now, it’s totally messed up. I have lost TWRP too.
Current status:
- No matter I do, I can’t get into recovery. It shows the boot logo and then moves to Magicsee logo animation, but get’s stuck there.
- I tried shorting some pins(not sure if they are the right pins), the device restarts but follows the same sequence as above(boot logo -> Magisee animation) but Amlogic USB burning tool never detects the device.
- I also, tried with the X96 stock firmware flashed on a SD Card, but still couldn’t get into recovery to trigger the update.
Any advice to recover this soft-brick will be a great help.
Cheers,
rishi2504 said:
Hello folks,
Need help with my X96 2GB/16GB version. It's a S905x(p212) device with a Q5X v2.1 board. The Wi-fi chip version is RTL8189.
Cheers,
Click to expand...
Click to collapse
Short pin method will fix this, unplug your device from everything, short 2 pins then while shorting the pins plug in the USB-USB cable with burning tool open, if it does work unplug and repeat the process until you short the correct pins
rishi2504 said:
Hello folks,
Need help with my X96 2GB/16GB version. It's a S905x(p212) device with a Q5X v2.1 board. The Wi-fi chip version is RTL8189.
Here is what happened:
- Initially, it was running 6.0.1 stock which I upgraded to 7.1.2 using TX7 upgrade package( SD Card method - Erase bootloader option was selected) posted on another forum. The ROM upgrade was successful and I had a fully-functional ROM, in that even the IR remote’s power buttons were mapped correctly, so no mods were needed after flash.
Click to expand...
Click to collapse
I hope the previous post will fix it for you! I don't want to highjack your thread, but the flash you did with the TX7 acually means that we could get a nougat rom on the X96? I've been searching for it a couple of months but didn't find any that would fit and I'm not that adventurous like you so haven't tried s905x roms for other boxes
BTW is this the one you used? https://4pda.ru/forum/index.php?showtopic=767468&view=findpost&p=71357306
Ricky Divjakovski said:
Short pin method will fix this, unplug your device from everything, short 2 pins then while shorting the pins plug in the USB-USB cable with burning tool open, if it does work unplug and repeat the process until you short the correct pins
Click to expand...
Click to collapse
Thanks Ricky for responding!
I had tried all the pins and shorting some does result in a reboot(and some sparks as well ), but nothing makes USB burning tool detect the device.
Have attached the eMMC's image. Any idea where I should try shorting the pins?
Cheers,
Update: I managed to locate the pins finally and revert to stock firmware. Thanks
antonholmstedt said:
I hope the previous post will fix it for you! I don't want to highjack your thread, but the flash you did with the TX7 acually means that we could get a nougat rom on the X96? I've been searching for it a couple of months but didn't find any that would fit and I'm not that adventurous like you so haven't tried s905x roms for other boxes
BTW is this the one you used? https://4pda.ru/forum/index.php?showtopic=767468&view=findpost&p=71357306
Click to expand...
Click to collapse
Im the one who tested the tx7 firmware on the x96, can confirm it works perfectly. using usb burning tool. be sure to tick the "erase bootloader" option when updating
tx7 firmware - HQYG-TX7-nikodi-20180104 .img
https://mega.nz/#!8VxwyDLK!swvvVOEe-ozT6UlNgSKp97mdjhtRPDBpJH64ky1f-Po
newest stock firmware if needed (dont think its english by default but i only used it to save myself from a soft brick and then installed the tx7 firmware)
aml_upgrade_package1_1_3.img
https://cloud.mail.ru/public/86o5/2PFx8P94Q
huffmybrd said:
Im the one who tested the tx7 firmware on the x96, can confirm it works perfectly. using usb burning tool. be sure to tick the "erase bootloader" option when updating
tx7 firmware - HQYG-TX7-nikodi-20180104 .img
https://mega.nz/#!8VxwyDLK!swvvVOEe-ozT6UlNgSKp97mdjhtRPDBpJH64ky1f-Po
newest stock firmware if needed (dont think its english by default but i only used it to save myself from a soft brick and then installed the tx7 firmware)
aml_upgrade_package1_1_3.img
https://cloud.mail.ru/public/86o5/2PFx8P94Q
Click to expand...
Click to collapse
Thanks! So the second file is x96 stock firmware? Just want to make sure I got it right I'm using a custom rom now so I will use that one first.
antonholmstedt said:
Thanks! So the second file is x96 stock firmware? Just want to make sure I got it right I'm using a custom rom now so I will use that one first.
Click to expand...
Click to collapse
yepp, the second link (aml_upgrade_package1_1_3.img ) is the stock firmware (still 6.0 though).
and your right, it probibly is wise to flash stock and then 7.1.2 (since your updating the bootloader when moving to 7.1.2)
huffmybrd said:
yepp, the second link (aml_upgrade_package1_1_3.img ) is the stock firmware (still 6.0 though).
and your right, it probibly is wise to flash stock and then 7.1.2 (since your updating the bootloader when moving to 7.1.2)
Click to expand...
Click to collapse
Thanks, will do! Should I choose Erase bootloader with the stock fw as well?
antonholmstedt said:
Thanks, will do! Should I choose Erase bootloader with the stock fw as well?
Click to expand...
Click to collapse
Thats how i did it.
huffmybrd said:
yepp, the second link (aml_upgrade_package1_1_3.img ) is the stock firmware (still 6.0 though).
and your right, it probibly is wise to flash stock and then 7.1.2 (since your updating the bootloader when moving to 7.1.2)
Click to expand...
Click to collapse
So flash aml_upgrade via usb burner, then the other IMG ? Then I can just watch for atvxperience?
brooker88 said:
So flash aml_upgrade via usb burner, then the other IMG ? Then I can just watch for atvxperience?
Click to expand...
Click to collapse
Correct!
rishi2504 said:
Thanks Ricky for responding!
I had tried all the pins and shorting some does result in a reboot(and some sparks as well ), but nothing makes USB burning tool detect the device.
Have attached the eMMC's image. Any idea where I should try shorting the pins?
Cheers,
Update: I managed to locate the pins finally and revert to stock firmware. Thanks
Click to expand...
Click to collapse
care to share the pins you used?
Unbrick x96mini:
Have a look @ my #4 Post!
https://forum.xda-developers.com/showpost.php?p=74831391&postcount=4
coyotecal said:
care to share the pins you used?
Click to expand...
Click to collapse
Those pins did not work for me. It sounded like they didn't work for him either and he found different pins, thus why I asked him to show what pins he used.
zusatzmetall said:
Unbrick x96mini:
Have a look @ my #4 Post!
https://forum.xda-developers.com/showpost.php?p=74831391&postcount=4
Click to expand...
Click to collapse
you shall try the pin on none arrow side of the eMMC, around pin 5 and 6 count from outside of board towards inside of board. it works on my old X96 2+16g version. eMMC: KLMAG1JENB-B041 from samsung
the first two pin at arrow side never work for me.
huffmybrd said:
Im the one who tested the tx7 firmware on the x96, can confirm it works perfectly. using usb burning tool. be sure to tick the "erase bootloader" option when updating
tx7 firmware - HQYG-TX7-nikodi-20180104 .img
https://mega.nz/#!8VxwyDLK!swvvVOEe-ozT6UlNgSKp97mdjhtRPDBpJH64ky1f-Po
newest stock firmware if needed (dont think its english by default but i only used it to save myself from a soft brick and then installed the tx7 firmware)
aml_upgrade_package1_1_3.img
https://cloud.mail.ru/public/86o5/2PFx8P94Q
Click to expand...
Click to collapse
don't know why ppl still trying pin short, if this works without opening the box.
you saved my box that got bricked after poisonatv rom. it got stuck at that rom and that rom was a boo boo for me.
back to ever reliable atvxperience rom now.
rishi2504 said:
Hello folks,
Need help with my X96 2GB/16GB version. It's a S905x(p212) device with a Q5X v2.1 board. The Wi-fi chip version is RTL8189.
Here is what happened:
- Initially, it was running 6.0.1 stock which I upgraded to 7.1.2 using TX7 upgrade package( SD Card method - Erase bootloader option was selected) posted on another forum. The ROM upgrade was successful and I had a fully-functional ROM, in that even the IR remote’s power buttons were mapped correctly, so no mods were needed after flash.
- I flashed TWRP posted by @Ricky Divjakovski on xda-developers for S905x devices and later installed his Poison ROM. The Poison ROM couldn’t boot for me like others who reported this issue as well on Poison thread.
- I now went a bit adventurous and flashed MagicSee Iron 7.1.2 firmware(SD Card Method- Erase Bootloader selected). The upgrade went fine this time too, but the ROM had many hiccups and software would hang quite often. So, I decided to roll-back to TX7 firmware again.
- But my reset button stopped working. The ROM would still boot and I could load TWRP recovery too.
- I tried some other stuff to install stock recovery and install OTA packages. And now, it’s totally messed up. I have lost TWRP too.
Current status:
- No matter I do, I can’t get into recovery. It shows the boot logo and then moves to Magicsee logo animation, but get’s stuck there.
- I tried shorting some pins(not sure if they are the right pins), the device restarts but follows the same sequence as above(boot logo -> Magisee animation) but Amlogic USB burning tool never detects the device.
- I also, tried with the X96 stock firmware flashed on a SD Card, but still couldn’t get into recovery to trigger the update.
Any advice to recover this soft-brick will be a great help.
Cheers,
Click to expand...
Click to collapse
you can try make booting sd card first, use amlogic boot card maker with the right u-boot.bin for your device, then copy stock recovery to your booting sd card, then try to reflashing stock firmware with usb burning tools when your device detected.
rishi2504 said:
Thanks Ricky for responding!
I had tried all the pins and shorting some does result in a reboot(and some sparks as well ), but nothing makes USB burning tool detect the device.
Have attached the eMMC's image. Any idea where I should try shorting the pins?
Cheers,
Update: I managed to locate the pins finally and revert to stock firmware. Thanks
Click to expand...
Click to collapse
hi, can you say wich pins?
51ice said:
debe probar el pin en el lado sin flecha del eMMC, alrededor del pin 5 y 6 contando desde el exterior de la placa hacia el interior de la placa. funciona en mi antigua versión X96 2+16g. eMMC: KLMAG1JENB-B041 de samsung
los dos primeros pines en el lado de la flecha nunca me funcionan.
Click to expand...
Click to collapse
hi! I have the same eMMC, could you say me wich pins? is in the red or green zone of pins? (sorry for my english!)
Related
I TAKE NO CREDIT FOR CORE METHOD. I APPLIED IT FOR OUR DEVICE !
To make long story short, I've hard bricked my device while trying to patch/unlock the bootloader after successfully flashing a custom kernel (this tripped knox counter). After reading all guides that addresses the problem for other devices, I'm posting a 100% working solution for the most hated disaster in the Android rooting/flashing world. Moreover, this is very promising info for testing bootloader exploits.
What is Hard Brick?
Hard brick is the state of android device that occurs when your device won’t boot/respond/charge at all. This is mainly caused by flashing corrupted firmware, damaged bootloader, incomplete flashing in Odin/Download mode, or interrupted OTA upgrade. You can't recover from hard brick by traditional methods since your phone is ~dead & you can't enter any Recovery or Download Modes; You'll need to use JTAG (expensive service), USB JIG (cheap, but no gurantee), or this free guide/files to get it repaired.
What do you need?
- Hard Bricked Device: Samsung Galaxy Note 3 (N900V)
- Micro SD Card: 4/8/16/32 GB micro SD card
- Unbrick Image: working dump with the same bootloader/version
- Image Writer: native commands on Linux/MacOSx or Win32 Disk Imager on Windows
How to recover?
1- Download Unbrick Image for your bootloader (MJE, NC2 or NC4) from here
2- If you're using Windows, download Win32 Disk Imager
3- Backup all files in the micro SD card you 'll use
4- Write the Unbrick Image to your micro SD card using Win32 Disk Imager or Linux/MacOSX commands
5- Remove battery, Insert micro SD card & then the battery
6- Hold Power + Home + Volume Down to enter Download Mode by bootloader on SD card
7- Flash Stock firmware via Odin & Enjoy
YOU MAY NEED TO TEST MICRO SD CARDS WITH DIFFERENT TYPES/SIZES & FORMAT AS EXFAT BEFORE WRITING AN UNBRICK IMAGE ACCORDING TO YOUR BOOTLOADER!
This method should work for most Hard Brick cases, especially those with flashing failures. However, some cases might need a repair service or a hardware treatment to recover. One thing you may try if you can't get a replacement (warranty claim) is from Samsung guide for N900 device that includes disassembly & making short of R4075 resistance (which isn't tested & for another device + I don't recommend it) as described here.
Click to expand...
Click to collapse
For Developer Edition, you need to create your own Unbrick Image since I can't share it for the device-specific bootloader. Just run this Unbrick Image Creator in recovery & it'll create "/sdcard/Unbrick_Files" in your internal SD card.
For more details, read the guides provided bellow in the credits section.
Downloads:
All files you may need are available in this folder.
Credits:
- designgears - for this guide
- Shabbypenguin - for this guide
- theramsey3 - for this guide
- dstruct2k - for this guide
- -Mr. X- - for this guide
Thanks to:
- @soundrizm - for creating the MJE image from his device
- @jrbxx7 - for creating the NC2 image from his device
- @K03WL3R - for creating the NC4 image from his device
XDA:DevDB Information
How to recover from a HARD BRICK, Tool/Utility for the Verizon Samsung Galaxy Note 3
Contributors
hsbadr
Version Information
Status: Stable
Created 2014-08-01
Last Updated 2015-02-15
Nice work! Thanks
Tapped from an annihilated N10.1
This is amazing progress for our devices @hsbadr. I, for one, can't thank you enough for all you're doing to keep our beautiful albeit locked down Note 3's on the forefront! Donation coming asap!
Sent from my SM-G900V using Tapatalk
Wait, how can this help with unlocking bootloader? I have no developing background so this would be nice to know
This won't reset knox to 0 though, correct? So there's no way to reset to 0 yet?
I see there is a nc2 and nc4 unbrick image... If i am on the unified kk Jasmine rom firmware which image do i use... I thought i read on the Jasmine thread that it contained components of both...
Samsung Note 3 - VZW
Jasmine 2.0 v4
XDA Pro
ihavenewnike said:
Wait, how can this help with unlocking bootloader? I have no developing background so this would be nice to know
Click to expand...
Click to collapse
Testing bootloader exploits could easily HARD BRICK the device; now, we've a tested fully working fix for this disaster. So, devs can feel better with their tests.
kvnhmmd said:
This won't reset knox to 0 though, correct? So there's no way to reset to 0 yet?
Click to expand...
Click to collapse
This just enables booting the device from SD card so that you can enter Download Mode & revive it from HARD BRICK state. The knox counter won't change unless you've already tripped it while messing with your device at/before HARD BRICK.
Night_Watcher said:
I see there is a nc2 and nc4 unbrick image... If i am on the unified kk Jasmine rom firmware which image do i use... I thought i read on the Jasmine thread that it contained components of both...
Click to expand...
Click to collapse
It only depends on the bootloader version. The unified KK firmware doesn't include any bootloader; so, you'll need to use the Unbrick Image based on your bootloader (NC4 for OTA update or full NC4 tar via Odin & NC2 otherwise). You may try the NC2 image 1st which won't boot if you're on a newer NC4 bootlooder; if so, use the NC4 image.
hsbadr said:
Testing bootloader exploits could easily HARD BRICK the device; now, we've a tested fully working fix for this disaster. So, devs can feel better with their tests.
This just enables booting the device from SD card so that you can enter Download Mode & revive it from HARD BRICK state. The knox counter won't change unless you've already tripped it while messing with your device at/before HARD BRICK.
It only depends on the bootloader version. The unified KK firmware doesn't include any bootloader; so, you'll need to use the Unbrick Image based on your bootloader (NC4 for OTA update or full NC4 tar via Odin & NC2 otherwise). You may try the NC2 image 1st which won't boot if you're on a newer NC4 bootlooder; if so, use the NC4 image.
Click to expand...
Click to collapse
So now we can just randomly try bootloaders, like maybe the DE bootloader modified for a device?
ihavenewnike said:
So now we can just randomly try bootloaders, like maybe the DE bootloader modified for a device?
Click to expand...
Click to collapse
NO, don't! This is only for devs or users who know exactly what they're doing. If you flashed another device's bootloader, you may kill your device forever. However, you can use it to recover when you ACCIDENTALLY made your device hard bricked.
Ok. Thanks. Curious, how do you learn about these things. I would love to try some stuff. Hey I got the device for 50 off contract.
Thank you, Thank you, Thank you! Makes me feel better about trying different roms &mods.
had a Droid HD unlocked bootloader, bricked it many times.
Could the unbrick files be made flashable. The DE 4.4 bootloader is now on new devices and many DE guys (me too) are interested in upgrading from 4.3? I bow low to @hsbadr really great work!
ol`DXer said:
Thank you, Thank you, Thank you! Makes me feel better about trying different roms &mods.
had a Droid HD unlocked bootloader, bricked it many times.
Click to expand...
Click to collapse
You're welcome! Glad I could help.
LillieBennett said:
Could the unbrick files be made flashable. The DE 4.4 bootloader is now on new devices and many DE guys (me too) are interested in upgrading from 4.3? I bow low to @hsbadr really great work!
Click to expand...
Click to collapse
The purpose of Unbrick Image(s) is to revive a ~dead (hard bricked) device by booting from external SD card to enter Dwonload Mode & flash firmware to recover. You can pull all images from your device & on DevED, all of them can be flashable.
Is the process similiar for a phone that was on MJE?
Scenario:
Phone was stock MJE.
Rooted w/ TowelRoot, installed SS 3.7.1
Rebooted to DL mode, Odin'd "unified firmware" from Jasmine thread (*I think this is where things went sideways b/c no NC2/4 rom was installed to stock slot, just the leftover MJE+TR+SS install).
Phone shutdown at the end of that Odin, and now will not power up / vibrate / enter DL mode / nothing ...
I put the NC2 debrick image on a 32GB Class4 MicroSD - no joy.
I was wondering if it's because the MJE bootloader is still there? Wouldn't I then need an MJE unbrick microSD img?
I figured as much so I made one by Odin'ing another phone back to Stock MJE, and doing a "dd if=/dev/block/mmcblk0 of=/sdcard/unbrickMJE.img count=524288" and used that .img to make the MicroSD card (with Win32DiskImager)...
Still no joy... No power-up/buzz/dl-mode off of power button OR voldn+home+pwr, with and w/out USB cable...
(Yes, the card is fine, the battery is at 100%...)
I'm wondering if I made the .img incorrectly? OR, is this phone just completely eff-screwed now?? :crying:
Thoughts?
NetworkPIMP said:
Still no joy... No power-up/buzz/dl-mode off of power button OR voldn+home+pwr, with and w/out USB cable...
(Yes, the card is fine, the battery is at 100%...)
I'm wondering if I made the .img incorrectly? OR, is this phone just completely eff-screwed now?? :crying:
Thoughts?
Click to expand...
Click to collapse
Does your phone vibrate when you attempt to turn it on? With the battery or without the battery but plugged into the charger? In my experience with hard bricks, the phone should at least vibe when you go to power it up. Also, not sure if it will make a difference but, try a class 10 card with the same amount of memory as the phone.
Other than that everything you did sounds correct.
Sent from my SM-G900V using XDA Premium HD app
NetworkPIMP said:
Is the process similiar for a phone that was on MJE?
Scenario:
Phone was stock MJE.
Rooted w/ TowelRoot, installed SS 3.7.1
Rebooted to DL mode, Odin'd "unified firmware" from Jasmine thread (*I think this is where things went sideways b/c no NC2/4 rom was installed to stock slot, just the leftover MJE+TR+SS install).
Phone shutdown at the end of that Odin, and now will not power up / vibrate / enter DL mode / nothing ...
I put the NC2 debrick image on a 32GB Class4 MicroSD - no joy.
I was wondering if it's because the MJE bootloader is still there? Wouldn't I then need an MJE unbrick microSD img?
I figured as much so I made one by Odin'ing another phone back to Stock MJE, and doing a "dd if=/dev/block/mmcblk0 of=/sdcard/unbrickMJE.img count=524288" and used that .img to make the MicroSD card (with Win32DiskImager)...
Still no joy... No power-up/buzz/dl-mode off of power button OR voldn+home+pwr, with and w/out USB cable...
(Yes, the card is fine, the battery is at 100%...)
I'm wondering if I made the .img incorrectly? OR, is this phone just completely eff-screwed now?? :crying:
Thoughts?
Click to expand...
Click to collapse
1st: you should have flashed full firmware to upgrade from JB; the unified firmware is for KK only !!!
2nd: If you can enter Download Mode, flash the firmware linked above to recover.
3rd: You should use Unbrick Image for the same bootloader & device (N900V MJE in your case)
Update: you may also try a USB JIG to enter Download Mode & flash the required firmware; you can create one or order it from Amazon.com (it's very cheap).
Can someone do a video tutorial on this.
An unbrick image may only be viable on a 32GB+ MicroSD. It must be at least the size of the eMMC chip on-board.
Kudos to all the folks that are involved in this, a life saver for those in need for sure!:good:
Any luck with mj7 debrick.img
Hi guys...quick question. I have a Huawei P8 that "used" to have Marshmallow Beta Rom installed. Long story short. Since there was no root I tried to revert back to stock with fastboot. Problem is when I tried to flash the B200 stock rom it got stuck on the last "sending" file for about half an hour (which normally takes about 3 minutes for full rom flash). Thought that I just unplug and try to reflash rom again(big mistake it seems but my last 2 phones were nexuses so I thought that it's impossible to actually brick your phone). Anyway...now I'm stuck on a bootloop with no way of entering recovery or the bootloader or fastboot, or anything else for that matter. The Vol+ - and Power combinations don't seem to be working. Any help would be greatly appreciated. Thanks
Check this thread:
http://forum.xda-developers.com/showthread.php?t=3260704
You will find a fix
30adi said:
Check this thread:
http://forum.xda-developers.com/showthread.php?t=3260704
You will find a fix
Click to expand...
Click to collapse
Yeah...already tried that. Eventually this morning, after countless tries I managed to flash the first firmware for our P8 which is a beta B030 version. Now technically the phone works..but I no longer have audio and device isn't getting recognised by the PC (though Fastboot works fine), therefore it must be a software issue. An hour ago I managed to flash B170 and even B200 but the audio issue and usb connection issue is still there. Kinda running on fumes here. Anyone has any other ideea if I should flash anything else. Mind you...I can only update via fastboot...Normal update methods do not work. Thanks
If you had marshmallow beta rom, there is a downgrade package. Have you used it? It's version B300
30adi said:
If you had marshmallow beta rom, there is a downgrade package. Have you used it? It's version B300
Click to expand...
Click to collapse
No...haven't used it. Got a link by any chance? I did a google search but the links were all dead. Thanks
UPDATE: Ok....found it...but I'm gonna need to extract it since local update isn't working. Will update. Bottom line...I messed up because I didn't do the research before trying to rollback to B200. Stupid me
You should go back to marshmallow and do a proper downgrade: B313 -> B300 -> B200
Check the thread, you have to downgrade via 3 button combination for B300, and 2 button combination for B200
B300 is the only proper downgrade package
Good luck!
30adi said:
If you had marshmallow beta rom, there is a downgrade package. Have you used it? It's version B300
Click to expand...
Click to collapse
Man...you're a life saver. That was totally it. Everything back in order now.. Hai sa traiesti
Doamne ajuta!!! Well done
Hello guys!
Recently, i've got this phone mentioned above. It is a great phone, everything is okay, but i do not like EMUI a lot, i prefer AOSP to EMUI.
Are there any custom ROMs (CM, AOSP, etc) to this phone?
I've looked around on 4pda.ru about this, i found a recovery, but thats it, nothing more.
There you go, i installed this TWRP 3.0.2.0, and it works like a charm.
1: Unlock your bootloader. IT IS INDISPENSABLE! If you brick your device locked, you lost.
2: Go into fastboot (Easiest: Turn off your device, and Hold down POWER DOWN + POWER WHILE you attach the USB from the computer. The phone will go instantly into fastboot mode, it works for me)
3: Type: fastboot flash recovery twrp.img
4: The phone now should download the recovery. Pull the battery out, and restart in recovery.
Download
The file is from 4PDA.ru, i have to reupload it, because 4PDA's sign up is a PAIN. A friend of mine helped me, and it took like 2 hours.
Altough, i do not know why you need the recovery other than backing up, since there are no custom rom avaiable for this phone. (Can anyone maybe port to it?)
I think, that porting Allwiev E4 Lite custom roms would be the best option, but I have weak knowledge about roms porting :crying:
There are no custom roms yet for this device.
For first you may trie to install nova launcher? It gives some feeling near to aosp.
Loller 123 said:
I think, that porting Allwiev E4 Lite custom roms would be the best option, but I have weak knowledge about roms porting :crying:
Click to expand...
Click to collapse
No. The best option is to port the ROM with the same chipset (MT6735).
My best result is a Doogee X5 Pro
Runner85sx said:
There are no custom roms yet for this device.
For first you may trie to install nova launcher? It gives some feeling near to aosp.
Click to expand...
Click to collapse
Thanks. I'll probably try it.
snikerfreak said:
No. The best option is to port the ROM with the same chipset (MT6735).
My best result is a Doogee X5 Pro
Click to expand...
Click to collapse
This is THE SAME chipset...
Loller 123 said:
This is THE SAME chipset...
Click to expand...
Click to collapse
Maybe I did read a wrong article. Could you please link a cyanogenmod to that device?
snikerfreak said:
Maybe I did read a wrong article. Could you please link a cyanogenmod to that device?
Click to expand...
Click to collapse
IDK, if there is cm for allview, but I'm trying to port IOS rom.
snikerfreak said:
There you go, i installed this TWRP 3.0.2.0, and it works like a charm.
1: Unlock your bootloader. IT IS INDISPENSABLE! If you brick your device locked, you lost.
2: Go into fastboot (Easiest: Turn off your device, and Hold down POWER DOWN + POWER WHILE you attach the USB from the computer. The phone will go instantly into fastboot mode, it works for me)
3: Type: fastboot flash recovery twrp.img
4: The phone now should download the recovery. Pull the battery out, and restart in recovery.
Download
The file is from 4PDA.ru, i have to reupload it, because 4PDA's sign up is a PAIN. A friend of mine helped me, and it took like 2 hours.
Altough, i do not know why you need the recovery other than backing up, since there are no custom rom avaiable for this phone. (Can anyone maybe port to it?)
Click to expand...
Click to collapse
@snikerfreak did you find any rom for this device.
My son instaled TWRP and wiped everything trying to flash an honor 5A rom, installation failed so now phone is dead.
Do you know where to get a firmware? Can't find anything right!
All attempts to find firmware for my Dual Sim Huawei Y6 II Compact (LYO-L21) failed so I want to ask a BIG support to anyone in this thread with a TWRP recovery installed. By inexperience my teenager son wiped every partition on the phone and now we are unable to boot. It would be of great help if some one could share a twpr backup (including all partitions) to be used not only for me but for anyone as a flashable firmware.
I'm aware it would take some time, skills and dedication.
Here is how to perform it:
Backup your current phone firts with all your personal data
Do a Factory Reset
Do a second backup to be shared as a stock rom or standard firmware
Restore personal backup
Upload firmware (stock rom) backup to the cloud and share donwload link here
Is there anyone wanting to provide this?
I'll be very grateful for that
Thanks
zumnao said:
All attempts to find firmware for my Dual Sim Huawei Y6 II Compact (LYO-L21) failed so I want to ask a BIG support to anyone in this thread with a TWRP recovery installed. By inexperience my teenager son wiped every partition on the phone and now we are unable to boot. It would be of great help if some one could share a twpr backup (including all partitions) to be used not only for me but for anyone as a flashable firmware.
I'm aware it would take some time, skills and dedication.
Here is how to perform it:
Backup your current phone firts with all your personal data
Do a Factory Reset
Do a second backup to be shared as a stock rom or standard firmware
Restore personal backup
Upload firmware (stock rom) backup to the cloud and share donwload link here
Is there anyone wanting to provide this?
I'll be very grateful for that
Thanks
Click to expand...
Click to collapse
OK I did the trick myself on a new phone I've got
Upload is done.
I've decided to create a new thread for it
Please check for the link here https://forum.xda-developers.com/general/rooting-roms/huawei-y6ii-compact-lyo-l21-dual-sim-t3577874
snikerfreak said:
Hello guys!
Recently, i've got this phone mentioned above. It is a great phone, everything is okay, but i do not like EMUI a lot, i prefer AOSP to EMUI.
Are there any custom ROMs (CM, AOSP, etc) to this phone?
I've looked around on 4pda.ru about this, i found a recovery, but thats it, nothing more.
Click to expand...
Click to collapse
Are there any custom ROMs?
Russian have custom ROMs in 4pda forum. It is Resurrection Remix OS 7.1.1 (unstable beta) and CyanogenMod 14.1_Android 7.1.1 (beta, camera not working). They stop work with RR_OS, but CM 14.1 is still porting.
You can help em.
links:
RR_Os port - 4pda.ru/forum/index.php?showtopic=792704&st=560#entry60137872
CM 14.1 port - 4pda.ru/forum/index.php?showtopic=792704&st=780#entry60547208
Also u can install ota-updates from custom recovery. Just del some strings in updater-script file into update.app \META-INF\com\google\android\ and repack its like .zip (w/o compression)
4xample strings:
assert(file_getprop(" -- it is checks firmware version and region
assert(apply_patch_check(" --- it is checks the hash sums of files the updates
Ok, so i'm stuck at an impass and am hoping someone can help me.
I have two types of Q-Box (S905). The 2/8 and the 2/16.
The 2/16 seems like a better version of the two, has 5Ghz wifi, etc. It boots to TWRP from an sdcard without issue.
The 2/8 is giving me nothing.
I'm thinking its something to do with the bootloader, but I'm just guessing as I've never had this issue before.
Any ideas guys?
simonchunk said:
Ok, so i'm stuck at an impass and am hoping someone can help me.
I have two types of Q-Box (S905). The 2/8 and the 2/16.
The 2/16 seems like a better version of the two, has 5Ghz wifi, etc. It boots to TWRP from an sdcard without issue.
The 2/8 is giving me nothing.
I'm thinking its something to do with the bootloader, but I'm just guessing as I've never had this issue before.
Any ideas guys?
Click to expand...
Click to collapse
I don't think there is a TWRP version for the 2/8gb version
So maybe you flashed the 2/16Gb recovery, however you able to.fix this with USB burning tool
I should rephrase.
The box works fine, but I can't get twrp.
So you may have answered my question ?
They'll have to stay as is then ?
Fix this with USB Burning Tool??? I don't get it.
Recovery is recovery as long as it is compatible. It isn't very big - 12mb-ish. It should be fine on 10GB or 1GB RAM model. I used 2GB x96 version on 1GB model I bought just to test before spending more on a better model - Txx or something.
I didn't like the look of those HDMI Android stick's when looking around... Looked too dodgy.
simonchunk said:
I should rephrase.
The box works fine, but I can't get twrp.
So you may have answered my question
They'll have to stay as is then
Click to expand...
Click to collapse
send me the recovery.img of the non woring one
Just to be clear, I have both a stock box and I have one that I tried loading TWRP onto.
What exactly do you need?
simonchunk said:
Just to be clear, I have both a stock box and I have one that I tried loading TWRP onto.
What exactly do you need?
Click to expand...
Click to collapse
My AMlogic flash tool now includes the ability to port a recovery, enjoy
Ricky Divjakovski said:
My AMlogic flash tool now includes the ability to port a recovery, enjoy
Click to expand...
Click to collapse
"port a recovery", someone can explain it? mean custom recovery?
Hi. I just purchased the new flex 11 from BB NS-P11A100. It appears to have the exact same processor, chip, and GPU as another tablet I have used before. The Lenovo Tab3 8. The only difference I can see is the emmc size (Lenovo 16Gb & Insignia 32Gb respectively) and the screen sizes. The processor is the same however limited to 1Ghz on the Lenovo whereas I believe the 1.3Ghz is the base CPU speed (I think the European version of the Lenovo came with a 1.3Ghz speed). So out of curiosity would the finished Lenovo's TWRP recovery work on the Insignia? Just a thought. Also, in case of brick could you use the Lenovo's firmware to flash it (after modding the scatter file of course). I'm just a noob to development but have no problem getting my hands dirty (I have 2 Lenovo's both broken but modified heavily) It's good to see another tablet with the 64bit processor setup. Makes it so the 1Gb of RAM don't look so bad. Thanks in advance for any info provided.
i'm guessing this hasn't peaked interest yet? i just got this bad boy root would be awesome
So did any of you who have this tablet figure anything out?
I was walking down the street with my tablet and accidentally stumbled into fastboot. Stay tuned
Fastboot Achieved Need Custom Recovery
IDontKnowMang said:
I was walking down the street with my tablet and accidentally stumbled into fastboot. Stay tuned
Click to expand...
Click to collapse
Ya I was able to unlock the bootloader using the Fastboot Oem Unlock comand. I just havent gotten up the courage to try the twrp recovery I have that I used for my Lenovo. Seeing as i also cannot find a download to get the stock firmware or flash file to fix it if I encounter any bricks... If someone can rewrite the twrp for the lenovo tab3 8 to use the insignia's model number it should work seeing as they both use the same board and chipset. Any ideas from anyone?
Tofor said:
Ya I was able to unlock the bootloader using the Fastboot Oem Unlock comand. I just havent gotten up the courage to try the twrp recovery I have that I used for my Lenovo. Seeing as i also cannot find a download to get the stock firmware or flash file to fix it if I encounter any bricks... If someone can rewrite the twrp for the lenovo tab3 8 to use the insignia's model number it should work seeing as they both use the same board and chipset. Any ideas from anyone?
Click to expand...
Click to collapse
link me up ill give it a shot
Anyone know how to get this thing in download mode? As soon as i get a boot.img i can build us twrp
Any progress on this yet?
any progress, this tablet makes me want to just blow it up. any ideas on rooting it?
Ok. I apologize for not being too active on this... Before when I tried to boot to the twrp recovery that belonged to the Lenovo Tab 4 8 (fastboot boot recovery twrp.img) it would always tell me there was no file by that name. The same thing happened to me when I attempted a different twrp than what was for my new Lenovo Tab 4 10. I found out that the bootloader simply does not allow the ability to boot to twrp. I got balsy and attempted to flash my new Lenovo (fastboot flash recovery tewp.img) instead of trying to boot to it. It worked. However would not boot to recovery but back to fastboot, and when I attempted a regular boot to the OS it replaced the bad twrp with the stock recovery. Tried maybe 5 diff twrp recoveries and it always fixed it. I haven't tried this with the insignia flexx 11 yet and I still have it up and going strong on stock. Maybey it will work and we can have twrp and root on the insignia. BTW. Has anyone seen or found a stock firmware for this device yet? Twrp would be cake it I can get a stock boot and recovery from it.
Alguien puede decirme si es posible hacer algo con las licencias estas?modificarla para root?o solo es una simple info?
Tofor said:
Hi. I just purchased the new flex 11 from BB NS-P11A100. It appears to have the exact same processor, chip, and GPU as another tablet I have used before. The Lenovo Tab3 8. The only difference I can see is the emmc size (Lenovo 16Gb & Insignia 32Gb respectively) and the screen sizes. The processor is the same however limited to 1Ghz on the Lenovo whereas I believe the 1.3Ghz is the base CPU speed (I think the European version of the Lenovo came with a 1.3Ghz speed). So out of curiosity would the finished Lenovo's TWRP recovery work on the Insignia? Just a thought. Also, in case of brick could you use the Lenovo's firmware to flash it (after modding the scatter file of course). I'm just a noob to development but have no problem getting my hands dirty (I have 2 Lenovo's both broken but modified heavily) It's good to see another tablet with the 64bit processor setup. Makes it so the 1Gb of RAM doesn't look so bad. Thanks in advance for any info provided.
Click to expand...
Click to collapse
I have a temporary solution till I find a better way magisk 7.1 and MTK easy root I'm going to assume you have android nugat like mine and it has mtk processor like mine. Anyway you can find both of those downloads here on this site under apps if not let me know
First install mtk easy root then install magisk go back to easy root and install the app or manager what ever it prompts you to do then go to magisk it will prompt you for extra set up then reboot and go to mtk easy root click the boot button on the bottom of the screen after root success go to magisk and set it up poof you have root it takes a minute for mtk to root on its own so I hit the button instead of waiting but it
works till i can really root it
IDontKnowMang said:
Anyone know how to get this thing in download mode? As soon as i get a boot.img i can build us twrp
Click to expand...
Click to collapse
Tofor said:
Fastboot Achieved Need Custom Recovery
Ya I was able to unlock the bootloader using the Fastboot Oem Unlock comand. I just havent gotten up the courage to try the twrp recovery I have that I used for my Lenovo. Seeing as i also cannot find a download to get the stock firmware or flash file to fix it if I encounter any bricks... If someone can rewrite the twrp for the lenovo tab3 8 to use the insignia's model number it should work seeing as they both use the same board and chipset. Any ideas from anyone?
Click to expand...
Click to collapse
If you want to put that thing in download mode it power and volume down then you need a phone handy to translate the Chinese think it's the 3rd one down but I forgot I just use mtk fast root and majisk it works great on mine!
I am looking for a twrp for this tho any suggestions would be awesome!
MT8163__Insignia__NS-P10A8100__mid1023_ma__7.0__alps-mp-n0.mp102-V1.6_hcn8163.tb.wvl1.n_P14
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
I finally found stock firmware
If I insert an SD card, I'm given a dialog box asking to confirm the switch between storage location from internal RAM to SD card, opening up all sorts of access. It gives me a full screen dialog that seems to bypass all of its walled in protections. With a Chrome apk on the SD card I can install it, run it, and download anything.
IDontKnowMang said:
Anyone know how to get this thing in download mode? As soon as i get a boot.img i can build us twrp
Click to expand...
Click to collapse
<Raising my hand> I do. Please see my previous answer.
Power and volume down