I 've had a Nook HD+ for years. I don't use it often, but it does come in handy from time to time. Early on I replaced the stock rom with CM 10, later upgraded to CM 11 and finally to CM 13. Recently the tablet started rebooting itself from time to time, an annoyance but not a show stopper. Thinking it wise (I'm not so sure any more), I decided I should reintall the OS using TWRP 3.1.1-0. Typically, I would have launched it from the Android restart menu, but that function was no longer working. So I launched TWRP the old fashioned way using the power an n keys. Then I reinstalled CM 13 in the normal manner. That seems to have made things worse.
Now, from a cold start the tablet sometimes launches Android very briefly, but often it never gets that far. Before the blue marshmallow can stop pulsing on the display, the cyanogen universal bootloader kicks in all over again ... and again ... and again.
I can still access TWRP without a problem. Howerer, I don't have a system backup generated from TWRP, and I can't seem to restore those using the TWRP restore function. I do have a backup of the stock rom made years ago with CMW, so I'm thinking I may have to replace TWRP to restore the stock rom, then upgrade the OS from there. I also have access to another Nook HD+ running CM 10. Maybe I could use that device to create a system backup for my Nook HD+?
If none of these ideas make sense, what are my other options? I'm open to anything and everything. Thanks!
I’ve been unable to solve my boot loop problem, which makes me more determined than every to find a solution.
My Nook HD+ will not launch android. The device launches the Cyangenmod Universal Bootloader, which quickly crashes and relaunches the boottloader, and around and around it goes. I’ve saved backups created using an android app, but those are of no use since I can’t launch android to access the required app. I also have the stock rom backup that I made when first installing CM, but I would need to launch CWM to restore it. So I tried flashing CWM using TWRP. That doesn’t work because it requires a reboot using TWRP to replace the TWRP recovery, and the reboot menu only offers System and Power Off. The Recovery option is missing, a known bug from what I can tell. No matter how many times I flash CWM, when I power off and boot into recovery I still get TWRP.
I also tried booting into CWM from an SD card. But no matter how many times I powered down and then restarted the device, it would not boot into CWM (because TWRP is installed maybe?).
My next idea was to use ADB and Fastboot to flash CWM. I installed everything needed (I think), and tried to install this way, and here’s what I get:
[email protected]:~$ adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
3024900030504303 recovery
[email protected]:~$ adb reboot bootloader
[email protected]:~$ fastboot flash recovery recovery.img
< waiting for any device >
It doesn’t matter how long I wait. Even though daemon sees and correctly identifies my device, the terminal hangs up and never flashes the CWM recovery image. Is it possible that this is because android debugging is not enabled and if so, is there any way to fix this when I can’t launch android?
One other possibility occurred to me (when you read this you will see just how desperate I’ve become). Looking at the internal files displayed when the Nook is connected to my PC (note that my Nook HD+ has not been rooted) I can see an 8.9 MB file named twrp-3.1.1-0-ovation.img. What if I removed that file, put a CWM image file in it’s place, and gave the CWM file the twrp name? Might that allow me to run CWM recovery and restore the stock OS?
I welcome any and all ideas!
Thanks!!
Related
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
obarthelemy said:
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
Click to expand...
Click to collapse
If you can still use ADB your tablets bootloader is likely not messed up, it sounds like you booted the tablet into fastboot mode not recovery. To get into recovery you can enter it by holding a key combination the most common combination is holding volume up plus the power button at the same time. If that doesn't work from ADB you should be able to get into recovery by running the command:
Code:
adb reboot recovery
Also ROM manger doesn't always work right with every device so I would recommend just uninstalling ROM Manager for now. If it is booting fine into bare ICS then your tablet should be ok, if your looking for Google Apps for ICS they can be found here http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip. Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
obarthelemy said:
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
Click to expand...
Click to collapse
obarthelemy said:
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
Click to expand...
Click to collapse
obarthelemy said:
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
Click to expand...
Click to collapse
The recovery you are referring to is to the standard Android 3e recovery it is included in every version of Android, and will always be like that unless you install a custom recovery such as CWMR and or TWRP. As a general rule you should never install a custom ROM without having a custom recovery image installed first, essentially all the stock 3e recovery is good for is installing OTA updates and preforming a basic factory reset of your phone. You should try and fix your recovery before going any-further, you can sign the un-signed zip by using this tool. Overall, I would focus on trying to fix the recovery to prevent any further damage to your tablet and so that way you have a simple way to recover from anything that might go wrong when flashing ROMs, mods, and other zip files.
issue with the uImage linked
The uImage linked on the download pages for the CM10 and CM9 version ends in ".*"
I have no clue what the normal extension should be; replacing that *.zip doesn't work. Is the file bad, or am I just too clueless about what to do with it ?
Ok so the question is:
1- which "recovery mode" file should I install on my tablet, especially since the mod author's ones seem flaky
2- how do I do that via ADB since my tablet no longer seems to have a working "recovery mode".
I'm sorry to hassle you with those questions... I've looked around, I can't find info nor files I'm confident about ?
So, I've stupidly let my son try and flash a custom rom on his generic chinese tablet (Cambridge Sciences StarPAD 9 SE) and he found a few very similar spec tablet roms on the internet which said they require TWRP to be installed before flashing. So he's installed that, rebooted into recovery but the TWRP doesn't fit the screen in terms of resolution size. Now, that's not the main problem. The main problem is that the touch screen doesn't work at all within TWRP so I can't select any of the options. Whenever I power off the device and power it back up, it reboots to TWRP and doesn't boot to the main ROM. He said that it did originally reboot to the ROM whenever he first installed the TWRP because he said that it was the only way of getting to the recovery. So I thought that I could just use ADB and just force a reboot from there but off course, there is no ADB device driver to be found on the internet.. well not that I can find anyway.
I'll attach a photo for you guys and hopefully someone can help me with this as I've spent the best part of 2 days trying to figure out a fix but am now stuck.
I'm now able to access the device by adb however I don't know what to do from there.
Any help?
Does anyone have any firmware for this device? I can't find anything on the internet at all. If I could get a firmware img then the device will be fixed.
The build number from the firmware is: fiber_evb-eng 4.1.1 master 20130530
the command is "adb reboot" AFAIK
Did he take a nandroid backup before flashing? It looks like a version of twrp that is not compatible with the tablet was installed. Not every device supports touch screen recovery mode. Can you use the volume rocker to navigate?
I can almost guarantee you won't find the firmware for a Chinese tablet. I've just been trying to help someone in a similar situation but the best we could manage was a ROM that had lots of glitches.
Edit how did he flash TWRP if it was incorrectly flashed ie: fastboot flash boot recovery.img instead of fastboot flash recovery recovery.img then that may produce a device that would boot straight into TWRP. I've heard of that happening on a nexus 7
Sent from my C5303 using xda app-developers app
I've gone through numerous threads about "unbricking" but I have not been able to find any specific instructions for what to do in my situation. I have installed Ubuntu on a USB drive in order to access ADB/Fastboot and have allowed myself to spend a few days troubleshooting the problem myself, but must admit that I am in over my head and require some sort of guidance if possible. Any insight or help is appreciated.
How I got to where I am:
I believe when I installed TWRP I had to use the build prop exploit, but I can't remember clearly
At some point after installing TWRP, I believe I removed SafeStrap
I installed the CM-11 ROM and used it for a period of time without issue
CM-12 for Thor was released, so I installed it over the CM-11 installation I believe
I realized that by installing CM-12, I had made my gf's save files for Final Fantasy inaccessible
I tried to restore to a backup I had made of CM-11 and was met with a bootloop
By trying to "start from scratch", I wiped all options allowed without realizing the consequences
Any reboots of the device brings it to a black screen after the gray Kindle Fire logo
Here are some observations I have made while trying to figure out a solution:
In TWRP, ADB shows the device as being in "recovery"
In "adb shell" with the device booted into TWRP, the command "su" produces "/sbin/sh: su: not found"
I am allowed to drag .zip files into "Internal Storage" for the device, but flashing "13.3.1.0.zip" or "cm-12 ... .zip", for example, leads to the device booting into a black screen (I have tried mounting /system in TWRP)
Fastboot commands tend to hang on the linux terminal with the device not responding to commands
EDIT: After a little dicking around, I found out how to make the device show up under Windows 8.1 by using a guide outlined here: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81-10/
I am now familiarizing myself with ADB/Fastboot commands a bit more to see if I can figure anything out on my own.
I haven't been able to figure this out on my own - is there anyone who could give me some advice about my situation?
Basically TLDR is that I did a factory reset on TWRP, I can boot into TWRP but can't seem to flash anything, though I can put zips on my internal storage.
aimlessanomaly said:
I haven't been able to figure this out on my own - is there anyone who could give me some advice about my situation?
Basically TLDR is that I did a factory reset on TWRP, I can boot into TWRP but can't seem to flash anything, though I can put zips on my internal storage.
Click to expand...
Click to collapse
Sound like you either lost write permissions on the system partition or the partition contents are corrupt. I have also heard problems within the data partition can create flashing problems. Have you tried the advanced wipe functions in twrp? You'll need to do a little poking around to determine which items are safe to wipe. Obviously you don't want to touch boot and recovery but (intelligently) neither is an option in twrp.
Davey126 said:
Sound like you either lost write permissions on the system partition or the partition contents are corrupt. I have also heard problems within the data partition can create flashing problems. Have you tried the advanced wipe functions in twrp? You'll need to do a little poking around to determine which items are safe to wipe. Obviously you don't want to touch boot and recovery but (intelligently) neither is an option in twrp.
Click to expand...
Click to collapse
I get a lot of errors involving /system when I try to mount and then repair or flash anything. Also, when I reboot it often says "Your device does not appear to be rooted - Install SuperSU now?" When I swipe to install it just restarts normally to my white kindle fire logo.
EDIT: I somehow was able to flash the cm11 ROM onto my kindle, rebooted, and my tablet is working again! I tried a bunch of different repair options and even used the option that makes you type out "yes" ( can't remember the name, need to sleep atm), but somehow got it working. Thanks for the help so far.
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
ganiman said:
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
Click to expand...
Click to collapse
Your understanding of TWRP is right. Basically, we dd the twrp image with OS 4.5.3 bootloaders (the only bootloaders that will boot unsigned recovery) and then before leaving TWRP flash back (almost) current bootloaders and recovery.
You should be able to adb-sideload the OS 5.1.2 update to fix the freeze. Was device rooted before it updated? Do you know what OS it was on? If you have adb access while device is frozen, run these commands for current OS info:
adb shell getprop ro.build.version.fireos
adb shell getprop ro.build.version.number
No CM12 available. Mostly-working CM11 is here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138
BTW, I assume you tried wiping cache and/or factory reset in recovery. If not, I'd do that first.
Hi everyone!
I'm using a Samsung gt-n8010. It could be done for due to the age, but maybe there is still hope.
My problem is that the tablet boots always to TWRP recovery and I can switch to download mode as well. Everything seems all right, internal storage and sd card shows exactly how they should, BUT... I can't do anything in TWRP. If I have the Keep system partition read only unticked, it still says the storage is read only and /data/media is not accessable. I can see it and access it with TWRP File manager. I tried flashing ROM and Recovery, also stockROM with Odin, but Failed. Clearing Cache, Data, Dalvik... also ends up with error. Format Data works, and also changing the partition types, but when I reboot device, it all comes back the same as before, no changes take effect. In Download mode I tried to use Adb from computer terminal, but it was stuck saying 'Waiting for device'. If Tab is in Recovery my PC shows both internal storage and sd card, but the internal storage is empty when I open it.
For details: I use Lineage OS 18.1 with TWRP 3.6.1_9-0. On my computer I use Linux Mint 20.3, but I tried with a laptop using Win10 as well, no success.
I've read many solutions on 'Unmodified system partition' or some had 0MB internal storage problem, but in my case that is different, as I have them all, but it seems all is read only and not accessable. I even tried to have the last Backup (2 month old) set using Restore of TWRP, but during the process, the tablet reboots and TWRP comes up again. I can't even turn it off, as TWRP comes up after some minutes.
Please help me somehow to be able to use the Tablet. If you need any further details, just tell me.
TWRP is not out yet on android 12, if you have it as of writing it wont be able to unencrypt your device. So all you can do is use it to install roms (YOU MUST FIRST FACTORY RESET THE DEVICE).
I also have never used odin as I have prefered adb
Code:
adb shell
/sbin/recovery --wipe_data
/sbin/recovery --update_package=SDCARD:romname.zip
adb should work in twrp?
I see your point. I intended to change/downgrade LineageOS version, but I was not successful. Now I am not able to do a factory reset either with success from TWRP, but I give a try to your adb codes. Give me some time
leathan said:
TWRP is not out yet on android 12, if you have it as of writing it wont be able to unencrypt your device. So all you can do is use it to install roms (YOU MUST FIRST FACTORY RESET THE DEVICE).
I also have never used odin as I have prefered adb
Code:
adb shell
/sbin/recovery --wipe_data
/sbin/recovery --update_package=SDCARD:romname.zip
adb should work in twrp?
Click to expand...
Click to collapse
Hi, I gave a try to that code both on TWRP and Linux terminal (from PC). But no effect First I did a FactoryWipe (successful) and went back to the Terminal each time. I tried with ROM zip and TWRP img as well, but after rebooting, TWRP 3.6.1 comes back again. I downloaded Lineage OS 17.1 (with GAPPS pico) and TWRP 3.5.0-9. It seems somehow I got stuck with that TWRP 3.6 and all I get on every attempt of flashing or wiping is it can't see '/data/media (No such file or directory)' or 'Unable to make /cache/recovery: Read-only file system'. I hope there would be a solution to get my system out of Read-only state
Nektarin87 said:
Hi, I gave a try to that code both on TWRP and Linux terminal (from PC).
Click to expand...
Click to collapse
Do you have adb installed and do you see your phone when you type "
Code:
adb devices
"
Usually its as simple as just booting into TWRP -> Factory reset then install the rom and done.
Maybe you do need odin but im pretty sure you can use adb instead like I outlined above, I hated using odin but if you find the right file it should also fix your issue.
What is the codename for your tablet? I cant find it on lineageos's site, what guide did you use its an official lineageos im assuming?
leathan said:
Do you have adb installed and do you see your phone when you type "
Code:
adb devices
"
Usually its as simple as just booting into TWRP -> Factory reset then install the rom and done.
Maybe you do need odin but im pretty sure you can use adb instead like I outlined above, I hated using odin but if you find the right file it should also fix your issue.
What is the codename for your tablet? I cant find it on lineageos's site, what guide did you use its an official lineageos im assuming?
Click to expand...
Click to collapse
Well, I have adb installed, but as my Tablet can only load in recovery it says like these:
adb devices
List of devices attached
4107cd04a2b611b5 recovery
When I load Odin or fastload mode (Download mode as tablet says) I can not list it with 'Fastboot device" command. It says 'waiting for device'.
My tablet is Samsung gt-n8010 (10.1) and I follow this thread to make changes:
LineageOS 16.0 Android 9 for GT-N8000 GT-N8010 GT-N8013 GT-N8020 FINAL VERSION EOL
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com
I had Lineage OS 18.1 installed and maybe what caused the issue is that I did not update the TWRP, or we do not have a TWRP ready for it yet, but currently I have TWRP 3.6.1_9-0 installed and stuck with. As I mentioned, on rebooting tablet always starts with TWRP, asking if I want system read only or not with an Unmodified system partition heading. I can not boot OS at all, I can go to Download mode, but Odin always failed indicating my system is read-only.
Ok yes your device is listed as recovery because it has not booted anything. I'm not sure if the commands I gave work without the system actually booting however.
After you entered adb commands there was no error text?
Also if you cant get odin to recognize your phone (RUN IT AS ADMINISTRATOR) you should figure out that first as thats a last resort fix when you really mess things up which I dont think you have yet. I think you must have something off in your configuration if its not reading anything make sure u can access another phone to rule out your pc, but get this working asap.
Usually if your device boot loops you can wipe the cache, and now days remove magisk modules.
If your device still boots straight to recovery It should be as easy as I outlined above, try not isntalling the apps/plugins after the initial rom, and again make sure you wipe cache/data before hand.
If your device boots straight to the bootloader then your left with Odin.
Man I hate video guides. But it looks good (unless he forgot to wipe) should have been as simple as that. He does not however provide you with the firmware (not rom) file that I believe you are going to need if you improperly downgraded the android a full version number. Post on his youtube and find that firmware file and fix your odin connection and flash it. If odin is also dead I have no idea but I have never in nearly 20 years had a phone fully brick even when I try to brick them. But I know it can be possible but your most likely going to recover from this.
If he doesn't respond just read more and learn, you may need some specific large file though to flash over what I believe may now be missing partitions entirely.
Maybe someone else here can help too. Good luck!
leathan said:
Man I hate video guides. But it looks good (unless he forgot to wipe) should have been as simple as that. He does not however provide you with the firmware (not rom) file that I believe you are going to need if you improperly downgraded the android a full version number. Post on his youtube and find that firmware file and fix your odin connection and flash it. If odin is also dead I have no idea but I have never in nearly 20 years had a phone fully brick even when I try to brick them. But I know it can be possible but your most likely going to recover from this.
If he doesn't respond just read more and learn, you may need some specific large file though to flash over what I believe may now be missing partitions entirely.
Maybe someone else here can help too. Good luck!
Click to expand...
Click to collapse
Hi there, I actually find some videos or instructions useful and some helped me out a lot. But as always, things can only be proper if anyone is qualified to do it or when you have the exact same issue on the device. Now back to my case...
I tried many ways, many aspects, but none helped me out. There was this good and working Samsung 10.1 gt-n8010 and one afternoon I found it turned off. When I charged it for a while I turned it on and all it could load is TWRP and I could not do anything. It seems to be working, but I could not see internal storage, while it showed all the 12 GB amount I had, so the issue is not that it shows 0 GB like in many videos. I tried to wipe cache, data, system, even change partition types, all ended with a fail saying my 'system is read only'. I also tried to use Odin and Heimdall to flash new recovery and ROM, also gave a chance to stockRom with android 4.1 or 4.4, but in all cases it said FAILED. To conclude all: I think it could be a hardware issue and as the machine is more the 10 yrs of age, it would not be a surprise, but it's a same it can't be flashed.
If anyone had a similar issue or may have suggestions I'm all ears and the thread remaines, but I am out of ideas at the moment and put my Samsung tab on the shelves.