Related
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
Can't find a definitive answer for this anywhere.
Where do the 7.1 or newer Roms active the remote control so it can bring the box out of standy and power down?
I know there is the remote.conf file in /system/etc on the 6 Roms which I have edited sucessfully before and you supposidly edit the remote.mouse1.tab in the 7.1 Roms but that doesn't seem to work. It doesn't even let me control the box once booted never mind power up and down which maybe suggests it is activated somewhere else first??
is it written into the kernel or boot loader perhaps.??
Please don't just suggest what I have already tried above. And yes I use a wireless usb keyboard/trackpad once booted but I'm talking about bringing the unit out of standby and powering down.
Any help would be massively appreciated.
I like my 7.1 Rom but having to disconnect/reconnect the power to boot it is just plain annoying.
did you ever figure it out, my remote does not work anymore after flashing poison rom over my boxes original rom, my power button works on the remote but thats it, have to use air mouse, has to be kernel or bootloader
bluefender said:
did you ever figure it out, my remote does not work anymore after flashing poison rom over my boxes original rom, my power button works on the remote but thats it, have to use air mouse, has to be kernel or bootloader
Click to expand...
Click to collapse
Hey. No still not figured it out. I'm still on my 6.01 ROM as it works. Pretty mental how nobody seems to know a fix for this?
Diamond Geezer said:
Hey. No still not figured it out. I'm still on my 6.01 ROM as it works. Pretty mental how nobody seems to know a fix for this?
Click to expand...
Click to collapse
i read but not sure if its true, it could be the kernel or something in boot, nougat rom changed things, so now i just use an air mouse
funny thing is if i flash back with twrp the original rom, the remote works again, but do not like the original rom.
bluefender said:
i read but not sure if its true, it could be the kernel or something in boot, nougat rom changed things, so now i just use an air mouse
funny thing is if i flash back with twrp the original rom, the remote works again, but do not like the original rom.
Click to expand...
Click to collapse
Its definately got something to do with system, check out the installation method of mine and Whiteak's Poison Rom, that only modifies system partition and apparently after applying it the remote doesnt work properly
Ricky Divjakovski said:
Its definately got something to do with system, check out the installation method of mine and Whiteak's Poison Rom, that only modifies system partition and apparently after applying it the remote doesnt work properly
Click to expand...
Click to collapse
actually it's the bootloader and the remote.conf from \system\etc\ , if the bootloader will work, and if the correct remote.conf is put in system\etc\ the remote will work too for Power ON\OFF
oh, and i know how to add more remotes to a firmware (maximum in a firmware can be added 8 remotes) it's all about kernel
drakulaboy said:
actually it's the bootloader and the remote.conf from \system\etc\ , if the bootloader will work, and if the correct remote.conf is put in system\etc\ the remote will work too for Power ON\OFF
oh, and i know how to add more remotes to a firmware (maximum in a firmware can be added 8 remotes) it's all about kernel
Click to expand...
Click to collapse
Would you be able to PM me?
ive done extensive research on this and couldnt find much
Ricky Divjakovski said:
Would you be able to PM me?
ive done extensive research on this and couldnt find much
Click to expand...
Click to collapse
sure, gonna send you a PM
Is it possible I can get this information also. I have been wracking my brain trying to figure how to do this. Please and Thank you in Advance
Hi, here the same problem. Upgraded the Android 6 firmware of my CSA93 (Amlogic S912, 3GB RAM, 32GB Flash) to the Stock T95Z Android 7.1 ROM (the base for the Poison ROM) and the remote has gone. I tried to copy the original remote.conf (from Android 6) into the new /system/etc folder (and also 5 other remote.conf files from the Internet with a restart each time), but no chance. It is probably not so easy as copying a file Any suggestions are highly appreciated. It is really annoying to have to turn on the device with the power switch each time.
Me too! Any news in this?
Soldiaz said:
Me too! Any news in this?
Click to expand...
Click to collapse
It's in the recovery partition under system/etc
Is there any more info re: this issue? A good write up would really help a lot of us who cannot develop ROM but quite happy to tinker here and there.
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!)
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1......
Click to expand...
Click to collapse
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
I'm also looking for that. But if I can get TWRP on it I'd probably try SU.
How did you get to install the TWRP? I found a few posts but was apprehensive about whether I can use SPFT to flash original stock ROM if things go wrong. I suppose that would be the easiest way.
For what I paid for the phone, it's a decent enough device.
Using SD card as internal memory always result in the total capacity being reported wrongly..256GB becomes 512GB with 50% occupied, 200GB becomes 256GB with 64GB occupied. Still waiting for their tech support to reply but unlikely they would.
Cheers!
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Ibuprophen said:
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thanks for the input I will have a read.
Charlie-Boy said:
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Click to expand...
Click to collapse
Thanks for the info.
Cheers!
chooks06 said:
Thanks for the info.
Cheers!
Click to expand...
Click to collapse
No problem.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
abhijeet715 said:
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
Click to expand...
Click to collapse
Code:
https://www.needrom.com/download/twrp-armox-x/
There are other places listed on Google.
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Charlie, could share how you got the TWRP working?
Have been fiddling around until battery showed -1%.. Had to go back to stock.
Thanks mate!
Choo ks
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Follow the guide here. I did it a few times before success as I followed a guide from another site.
https://www.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
Click to expand...
Click to collapse
I think I installed magisk using this method, clearing dalvik and cache.
https://www.stupdroid.com/2018/02/magisk-16.0-download.html
Click to expand...
Click to collapse
Charlie-Boy said:
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Click to expand...
Click to collapse
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Charlie-Boy said:
Follow the guide here. I did it a few times before success as I followed a guide from another site.
I think I installed magisk using this method, clearing dalvik and cache.
Click to expand...
Click to collapse
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
You ignore the password and change the language to English from Russian. Just don't enter a password at all. The recovery won't stick as Android replaces it when you reboot. After you've completed other steps maybe OEM unlocking then it stays, or so I read somewhere.
chooks06 said:
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
Click to expand...
Click to collapse
All of them are encrypted by default now. The password in TWRP should be ignored and just change the language and select storage etc.
abhijeet715 said:
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Click to expand...
Click to collapse
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Charlie-Boy said:
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Click to expand...
Click to collapse
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
abhijeet715 said:
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
Click to expand...
Click to collapse
Mine is the same encryption is enabled. I select external SD storage and I am shown the contents using the same procedure as yourself, I cannot tell you why this is so. I am using the same technique, same phone, same settings, same TWRP, maybe we have different SD card?
That is all I can think of by way of an explanation. It works perfectly for me. I also made a backup which I can select and restore without a problem.
I'm looking for a way to TWRP flash a Pie GSI (Resurrection Remix, to start with), and am getting the TWRP error "E:Cannot flash images to file systems" using @Pretoriano80's TWRP https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
[EDIT] TWRP is actually v3.2.2-1 from @schwabe93
I remember there were at least two different TWRPs that worked on my M5 8.5 (SHT-W09 C567 in my case), and one of them was for a device similar to the M5 8.4, ?P10 Lite maybe?
Anyways, I'm looking for any guidance that will allow me to flash a Pie (and eventually Q) GSI img via TWRP.
THANKS
why TWRP for GSI??
you can simpely flash the gsi rr using fastboot methode
THE MAXIMUM POWER said:
why TWRP for GSI??
you can simpely flash the gsi rr using fastboot methode
Click to expand...
Click to collapse
No computer. ?
TiTiB said:
No computer.
Click to expand...
Click to collapse
Ohh, my bad, btw never install any images instead of erecovery because you will not be able to recover your tablet as you do not have PC
THE MAXIMUM POWER said:
Ohh, my bad, btw never install any images instead of erecovery because you will not be able to recover your tablet as you do not have PC
Click to expand...
Click to collapse
Thanks @THE MAXIMUM POWER
The "no computer" thing is only temporary, thankfully.
I don't fully understand your post. Do you mean the image overwrites erecovery? When I first rooted my tablet (3-4 months ago) I installed a bunch of gsi's but didn't like them, so went with LOS 15.1 and still have erecovery working—it even started it's download (I was curious).
I'm happy with LOS, but, well TiTiB stands for Tweak it Til it Breaks, sooo....I just can't help myself—gotta have something to, uh, tweak. And, as I said, I want to eventually use Android Q.
TiTiB said:
Thanks @THE MAXIMUM POWER
The "no computer" thing is only temporary, thankfully.
I don't fully understand your post. Do you mean the image overwrites erecovery? When I first rooted my tablet (3-4 months ago) I installed a bunch of gsi's but didn't like them, so went with LOS 15.1 and still have erecovery working—it even started it's download (I was curious).
I'm happy with LOS, but, well TiTiB stands for Tweak it Til it Breaks, sooo....I just can't help myself—gotta have something to, uh, tweak. And, as I said, I want to eventually use Android Q.
Click to expand...
Click to collapse
Yes, i meant do not overwrite any images over erecovery, nice name btw, i used Q on my M5 and it was very buggy, i couldn't even connect to wifi, also im verrrrrry addicted to installing gsis on my tablet, i can not stuck one week without playing around with the Tablet, e. G. Yesterday i was on resurrection remix from openkirin because it it customizable, today i reinstalled the original firmware because it is more beautiful than the stock, tomorrow im going to reinstall rr because i like the stock, after two days lineage and so on and so on.
THE MAXIMUM POWER said:
Yes, i meant do not overwrite any images over erecovery, nice name btw, i used Q on my M5 and it was very buggy, i couldn't even connect to wifi, also im verrrrrry addicted to installing gsis on my tablet, i can not stuck one week without playing around with the Tablet, e. G. Yesterday i was on resurrection remix from openkirin because it it customizable, today i reinstalled the original firmware because it is more beautiful than the stock, tomorrow im going to reinstall rr because i like the stock, after two days lineage and so on and so on.
Click to expand...
Click to collapse
Thanks for clarification. It'll be at least a few months b4 I consider Q—still too new.
Still, I want to track down the "E:Cannot flash images to file systems". I figured out that the TWRP I'm using doesn't have "System Image" as one of the options for flashing, so I was trying to flash the GSI to "System", but need to flash it to "System Image".
The quest continues!
TiTiB said:
Thanks for clarification. It'll be at least a few months b4 I consider Q—still too new.
Still, I want to track down the "E:Cannot flash images to file systems". I figured out that the TWRP I'm using doesn't have "System Image" as one of the options for flashing, so I was trying to flash the GSI to "System", but need to flash it to "System Image".
The quest continues!
Click to expand...
Click to collapse
Well, in order to see the "install as system image", you MUST decrypt your device first and then use the latese petroin twrp, but if your device was stolen by somebody, you will regret the decryption as all your data will be available for him
So i advice u touse the fastboot mode
THE MAXIMUM POWER said:
Well, in order to see the "install as system image", you MUST decrypt your device first and then use the latese petroin twrp, but if your device was stolen by somebody, you will regret the decryption as all your data will be available for him
So i advice u touse the fastboot mode
Click to expand...
Click to collapse
Already decrypted—my M5 almost never leaves the house.
I initially used @Pretoriano80's TWRP. Is that the one? I don't remember why, or even if, I didn't like it at the time. Could be that I just wanted to try something different—very typical for me.
TiTiB said:
Already decrypted—my M5 almost never leaves the house.
I initially used @Pretoriano80's TWRP. Is that the one? I don't remember why, or even if, I didn't like it at the time. Could be that I just wanted to try something different—very typical for me.
Click to expand...
Click to collapse
Good, last time i used this twrp i liked it very much, but i also uninstalled it because it did not install the system images as it should, sometimes it worked, sometimes doesnt
Installed @Pretoriano80's TWRP, RR GSI, and had loops at the RR boot screen. I let it cycle 4 times b4 giving up. Think I'll uninstall Magisk and Xposed (might be a requirement anyway) and try again.
THE MAXIMUM POWER said:
Yes, i meant do not overwrite any images over erecovery, nice name btw, i used Q on my M5 and it was very buggy, i couldn't even connect to wifi, also im verrrrrry addicted to installing gsis on my tablet, i can not stuck one week without playing around with the Tablet, e. G. Yesterday i was on resurrection remix from openkirin because it it customizable, today i reinstalled the original firmware because it is more beautiful than the stock, tomorrow im going to reinstall rr because i like the stock, after two days lineage and so on and so on.
Click to expand...
Click to collapse
So what is your verdict on the GSIs? Is there a pie one with the magnetic cover working for wakeup?
I have the SHT-AL09 C636 on Pie and I have been itching on flashing the GSIs, but I really don't have too much time nowadays to tinker :crying:
Thanks!
jgaviota said:
So what is your verdict on the GSIs? Is there a pie one with the magnetic cover working for wakeup?
I have the SHT-AL09 C636 on Pie and I have been itching on flashing the GSIs, but I really don't have too much time nowadays to tinker :crying:
Thanks!
Click to expand...
Click to collapse
The GSIs are basically and in principle good, but you can not compare them to the original firmware is well built for our device and support all features, take this for example, PUBG run on EMUI way smother than the GSI.
unfortunately, i do not have the magnetic keyboard to test it, btw yours shouldn't support it as the SHT version does not have the conection dots at the buttom
jgaviota said:
So what is your verdict on the GSIs? Is there a pie one with the magnetic cover working for wakeup?
I have the SHT-AL09 C636 on Pie and I have been itching on flashing the GSIs, but I really don't have too much time nowadays to tinker :crying:
Thanks!
Click to expand...
Click to collapse
I haven't tried any since they first came out months ago. I've read good things about EMUI 9.1, though.
BTW, still no success flashing GSI via TWRP. ?
THE MAXIMUM POWER said:
The GSIs are basically and in principle good, but you can not compare them to the original firmware is well built for our device and support all features, take this for example, PUBG run on EMUI way smother than the GSI.
unfortunately, i do not have the magnetic keyboard to test it, btw yours shouldn't support it as the SHT version does not have the conection dots at the buttom
Click to expand...
Click to collapse
Thanks for your reply, I'm talking about a magnetic cover (not the keyboard). Any case with the proper magnets will wake up the device when you open it, it is a very convenient feature in any tablet
jgaviota said:
Thanks for your reply, I'm talking about a magnetic cover (not the keyboard). Any case with the proper magnets will wake up the device when you open it, it is a very convenient feature in any tablet
Click to expand...
Click to collapse
My apologize for misunderstanding, i do not have magnetic cover, i think the openkirin.net roms might work, not sure