Hello all - kind of heavy first post - Android Q&A, Help & Troubleshooting

Hello,
So I need help with completely wiping a linux partition on my android SM-a137f (and computer) that has been there for privacy invasion reason/spying etc by someone at my work.
------------Skip to the bottom part for phone only part, the rest is about the computer issue , both related however as they infect each other and i see the same linux filesystem and patterns on both---------
I never used Linux before and I tried fighting this "trojan" in windows on my computerand fatigued myself after the 50th low level formatting, not understanding how it can just come back, plus self learning, if i use an antivirus that works decent, like install it within 2 minutes after formatting before it activates, it gave me a lifespan of +20 minutes perhaps, next time i did that, it had injected it and just spawned like 10 processors of it to lag me down. Plus installing these fake drivers, meaning it infected my kernel.
So as i dived in to the world of Linux i got my hands on rescuezilla, which is based on ubuntu, things started to clear up, very sophisiticated work, and insane. Looping stuff, a squash filesystems that is impossible to remove, and i mean impossible in my book, thats why i come here, because if you are going to suggest any permission changing command or unmount command, don't - i tried every single one in the book and it won't budge.
It's not even an I (i forgot what I stood for) in the permission, it's only like cr- r ---- r-- or something, two or three 3's
The overlay starts with a /cow and holds everything.
Since this will perhaps be a police matter unless he agrees to replace the devices this has killed (phone, im on my third now, computer and a very secure router) and I have more than enough evidence including a perfect clone of the whole harddrive of my work computer and laptop.
Anyway - i dont care about any data, wipe all, and more if possible. Its my 85th time formatting anyway so, i just can't get rid of it. It's "base" is the X: partition which would be the recovery one I believe, in windows. And it mounts itself as a ddrom and/or ram, virtual, but not virtual. Every program i've said has stated it's a virtual, and when i try anti-virtual removal stuff, it says its not a virtual disk. Read only that nothing can remove in windows at least, forget diskpart etc.
-----------------------------------------------------------Phone---------------------------------
I am willing to pay for proper help on this.
I just rooted it and I want to wipe that whole kernel on this phone. Not a factory reset - a clean wipe. Not a single file left. Is that possible? Or how else do I get rid of all of that stuff, I mean, there is a problem whe 280 system apps has on average 60 permissions each, up to 400.
Thanks a lot for any input in advance. I can't stress how much of a mental toll this has taken on me as i've been on this for 1 month straight not doing anything else. Since it's about my privacy, and It seems I've had one for the past 2 years with my every footstep, thing ive written or said, even a sleepshedule has been monitored.
Just a few screeshot examples

In Odin flash the firmware with a 4-file zip file.

ze7zez said:
In Odin flash the firmware with a 4-file zip file.
Click to expand...
Click to collapse
How do you mean? I done that several times, filled out the AP CP BL CSC etc, doesn't touch that partition

Mikez77 said:
How do you mean? I done that several times, filled out the AP CP BL CSC etc, doesn't touch that partition
Click to expand...
Click to collapse
Show a screenshot of the Odin window after the flashing is complete.

According to the OP, their computer is attacked within seconds of them logging in. Any antivirus only lasts a few minutes. Can't low level format the disk, because the attacker puts BIOS and virtual wifi spots into the UEFI partition, hacked their router and cell phones numerous times as well.
And they claim to know who this is, have a mountain of evidence but somehow won't go to the police with it. Search for the op's name and the keyword linux. They're carpet-bombing forums with paranoia.

Related

Searched and NOTHING!

Hey guys, so I searched and search, using the search function as described in the forum rules, and couldn't come across anything with this nature, so if anyone has an urge to help out a noob I would really appreciate it!
So I downloaded the new Android Desire V4 rom, someone told me there were instructions in the download, which there were...they read as follows...
set mtype 2524
set ramaddr 0x20000000
set ramsize 0x0fc00000
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline ""
boot
So my question is, again, um how do I do any of that! LOL Those look like a list of things I am supposed to do as opposed to actual instructions on how to do them LOL
If I run HaRet, it boots, but from my understanding I need to do the above list to make it functioning to it's (current) fullest potential?
Thanks for any assists!
i haven't tried android, not interested in kids play things, but that to me lookslike a list of setup commands, , sure they aren't supposed to go in an initialization file of some kind?
thats the startup txt details, and all you hav to do is copy it all to ur sd root and thats it its honestly not worth it at the min unless u just gonna play about for a bit
hmm
samsamuel said:
i haven't tried android, not interested in kids play things, but that to me lookslike a list of setup commands, , sure they aren't supposed to go in an initialization file of some kind?
Click to expand...
Click to collapse
Probably, but I don't even know what that means! LOL
I am like a super noob..haha.
I guess I am asking specifically what you would do, every step, to do the list of setup commands.
1. How do I change to those values, like which part of the phone I go into.
2. If they need to be installed, how exactly, specifically do I install them.
I am basically looking for full instructions. For example if I were teaching someone to watch a DVD who has never used a DVD/movie playing device before, I wouldn't just say "put it in and watch it." I would say. "This is the power button. Click that to turn the device on. This is the open tray button, click this, and place the DVD shiny/mirror side down flat. Click the open tray button again to close the tray. Once closed it should automatically play, if not click the button with the sideways triangle on it to start the movie."
Like that is how nooby I am with this stuff LOL..but not stupid enough to change something I shouldn't, screw something up. If the instructions are there, I got it.
Demon_man said:
thats the startup txt details, and all you hav to do is copy it all to ur sd root and thats it its honestly not worth it at the min unless u just gonna play about for a bit
Click to expand...
Click to collapse
So I don't have to do anything? I have booted Android Desire V4 rom about 22 times so far, and every single time it is stuck in fast forward mode, does not give me the sim option like in the instructions on the website to download the file, and is generally the exact opposite of what everyone is claiming it is/doing.
So I would assume I am missing some key crucial steps no? Also My radio rom is fine, I reformatted my SD Card, it's fresh and all files are on the root of the card. From the sounds of it, you have to do something with the zImage (from what I have read), and something else... this is why I am confused.
as far as i'm aware there are still a few issues where certain models cant run it properly? and isn't there something about there being a few different digitizers, and it only works on some? (that might not be an issue anymore, i've not been keeping up)
i tried android quite a few times on my previous device (htc kaiser). i believe nearly the same concepts apply to the HD2 at the current stage of android development for the HD2.
facts:
1. you should know that android's files are to be kept on the sd card according to the instructions (more details here: http://forum.xda-developers.com/showthread.php?t=719646)
2. you should know that your windows and any settings made under windows will remain INTACT. this is because android, being in the storage card, is like an independent operating system.
3. point 2 above implies that any settings specific to windows or specifically made in the windows system settings (etc) have NO IMPACT on android. so no need to ask:
1. How do I change to those values, like which part of the phone I go into.
Click to expand...
Click to collapse
4. the only things important to android are the radio ROM version and MAYBE the (Hard)SPL version.
5. android is spun into action using "haret". haret is a little program that is started from windows but it essentially kicks out windows (temporarily) and tricks the phone into booting android from the sd card.
so from all of the above points, we can conclude that any and all configurations for android must be made in some text files. this text file must be placed according to the instructions somewhere along side haret and the rest of the android files on the sd card. this should answer:
2. If they need to be installed, how exactly, specifically do I install them.
Click to expand...
Click to collapse
this text file, as suggested by demon_man in post 3 in this thread is the "startup.txt". another name for startup.txt is "default.txt". these files are the same, except that haret pre-selects "default.txt" as your startup script when you launch haret. this saves you the step of manually selecting a particular startup file (you can have a bunch of startup files with different settings in each to experiment and you can name them ANYTHING). so after experimenting, you should arrive at a startup file containing configurations that work well for you. you can then name this file as "default.txt" and you can also optionally delete all the other startup files you created while you were experimenting.
i hope the above gives you some idea of what to do. if i had tried android on the HD2 for myself and if i had personally done more research of android on the HD2, i would have certainly given you some links of material that i am CERTAIN already exists, if you fancy searching just a little bit. being a noob is no excuse, because "search" is the FIRST forum rule. and just saying that you searched without posting some example keywords of what you searched for sounds "fishy", so not sure you searched well
i have written the above to help you build your concept, but we would all applaud for you (yay!) if you post in the appropriate threads for android and android tutorials from now on. i doubt you will need to post more because what i have tried to detail for you above should be a very solid foundation for you to understand how the wonderful people here at xda have gotten android to work on devices it was never released for.

Enable multi user / guest account feature on Lollipop

The multi user and guest account feature is not available on either of the two recent releases of Lollipop for the Z3v. I did some research and it appears this is the case, not only on other Verizon handsets like the Droid Turbo and the Galaxy S5 / S6, but a few other non-VZW devices as well. I'm not sure why it was removed but apparently it's just hidden. It can be enabled and I followed the instructions for doing this for the various other devices and can report that it works for our Z3v (see attached screenshots).
I've kind of cleaned up the instructions and put them below. Usual disclaimer - I'm not responsible for anything that may happen to you or your cat if you choose to do the following. You DO need root access to edit and write to the system file.
** To be safe, please make a backup of your phone and/or a copy of the build.prop file that you are going to edit.
Get ES File Explorer. Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)
With ES File Explorer, go to device/system/ and find the file: build.prop
Choose to edit it with ES Note Editor.
Scroll to the end of the file and type in the following:
fw.max_users=5
fw.show_multiuserui=1
Save the file.
I'm not sure if the next step is required but it was in half the instructions I saw, and I did it myself: Click and hold the file, go to Properties, and then change the permissions to Read, Write & Execute. [all three]
Reboot your phone.
When you're up and running, access multi user mode by pulling down your notification shade and then clicking on your user icon at the top right corner.
Notes so far:
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Therefore, an app such as Movie Creator can and will create a "highlight" movie that is composed from photos that are saved on the external SD Card. Just keep this in mind as far as privacy.
There is a per user option that lets you decide whether or not the additional users can use the phone and access the text messages. If you disable this ability, while they cannot open the phone app to make a call, the CAN receive an incoming call.
You can find out more about the nuances of additional users with your Google Fu.
Enjoy!
Wow! Great work!
AddictedToGlass said:
Wow! Great work!
Click to expand...
Click to collapse
Thanks! I really wanted this feature and it seemed like not many people care too much about it. It's my way of circumventing the awful permissions control we currently have in Android. That is, there are apps I want to use but refuse to install because of their overreaching permission requirements (contacts, etc) and so I can now create a second user with a new "dummy" Gmail account that has no sensitive information and install these apps without worrying.
By the way, something neat I figured out about this. Additional user accounts are not allowed to side load apps (the toggle to install from unknown sources is grayed out). I figured out that if the main user / owner restores an app through Titanium Backup, any other currently existing user will have it installed for some reason. I don't know why this happens but it's a neat glitch that gets you around that restriction.
Well I think most people simply don't let others touch their phones and so don't have a use for multiple user accounts. I find that my phone, as big as the screen is, is becoming more and more of a computer / tablet replacement. I like the idea of a multiuser functionality, but mostly to hide my own stuff. I'll silk never let anyone else touch my phone!
The use for multi-user that I've seen that makes the most sense is people with children. They will create a user profile for the child so they can't get into any of the parent's stuff or settings. That or the guest profile which will let them do whatever the heck they want without screwing up the phone.
Aside from that I have read that devs find the feature very useful for testing. Heck, that's not a bad idea to install and test apps, in general.
uh oh.
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
rpelljr said:
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
Click to expand...
Click to collapse
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Tigerhoods said:
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Click to expand...
Click to collapse
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
rpelljr said:
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
Click to expand...
Click to collapse
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
it is guys if done right your system needs to be switched to r/w then go back to r/o after modifying the build prop if you modify in r/o you will get bootloop to a hard brick it depends.
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
Well I kinda fixed it. I went and bought a HTC M9. Lol but not yet, I'm still working on it. I have found scripts to run, even a specific build.prop fix to push, but I have windows 10 and couldn't get adb to find the device. Plus I'm a little rusty. So I broke out my old windows 7 laptop I have used just for rooting an modding phones and tablets. I did get adb and fastboot to find it once. Then some reason lost it. I didn't have it ready to go. But I'm almost 100 percent sure I can get it. Just need to play around with it a little bit more. Having trouble with drivers etc. I will let you know when I have it.
And didn't really hurt my feelings getting the phone I truly want. I never had problems with HTC since I was flashing roms on my old window phones. I just want my pictures I cannot replace.
"Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)"
Alas- I am not rooted, and therefore can not enable "Root Explorer" option. Unless someone has some other suggestions- I think I can't do this unless I'm rooted.
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
AddictedToGlass said:
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
Click to expand...
Click to collapse
a backup usually means going into your twrp and hit the back up button and make a copy of your system including data and all that. This is mandatory before messing with the build prop. If you want Pm me your build prop and I will send it back to you. With multi user enabled.
Yup, I know what a back-up is and how to do it, and I know it's a must before messing with the build.prop. I just really thought I had done it recently...
-and I had! But I forgot that a few days ago I bought myself a Christmas present; a 200 Gb micro SD, and copied most of the contents to the new card from my old one. I chose not to copy the backup because I had planned to make some changes and create a more recent backup. Never happened though because I got side tracked loading music and such. Lol!
So I'm all back together, but would still like to play with this feature. So I'm going to give it another shot.
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Click to expand...
Click to collapse
Perhaps the wrong thread but: enabled multi user on a Cube T8 only to find that guest and other user can access INTERNAL sd but not external sd. I'd rather have it the other way round. So the kids (other users) can use the whole of 32 GB sd card rather than me having to share the small internal sd with them.
Any ideas how to fix this? Phablet is not rooted btw.
got bootloop..... but i'm safe as i've backup.... through recovery..
I've inserted two lines and fell in bootloop
Thanks bro.. working....!!!! but second step is not needed...

Need help to backup my pictures and video from my keeping restart kindle fire HDX 8.9

My device is Amazon Kindle Fire HDX GU045RW 64GB Black 8.9" Wifi 3rd Generation Tablet, and it has had a keeping restart issue since last week, the device is not rooted, and firmware version is 4.5.5.2. I think a factory reset might bring it back to work, but I forgot to back up my pictures and videos in the DCIM folder.
so far the device can start the fire OS for around 10 seconds and restarts again when it is powered by a PC, which recognizes it as a portable device and I can explore the internal storage for a very short time, but when it is powered by a charger, it rarely enter into the main menu, looks like the USB storage enumeration would pend the restart a little bit longer, I am not sure if such info is helpful to narrow the possible causes, just hope anyone who met similar issue would give me some hint about it. Thanks in advance for any comment!
I have managed to install the kindle adb driver on my laptop, and could run "adb devices" and serial number showed , is there any adb command I could use to diagnose my device? Thanks in advance for any suggestion
godhand_sh said:
My device is Amazon Kindle Fire HDX GU045RW 64GB Black 8.9" Wifi 3rd Generation Tablet, and it has had a keeping restart issue since last week, the device is not rooted, and firmware version is 4.5.5.2. I think a factory reset might bring it back to work, but I forgot to back up my pictures and videos in the DCIM folder.
so far the device can start the fire OS for around 10 seconds and restarts again when it is powered by a PC, which recognizes it as a portable device and I can explore the internal storage for a very short time, but when it is powered by a charger, it rarely enter into the main menu, looks like the USB storage enumeration would pend the restart a little bit longer, I am not sure if such info is helpful to narrow the possible causes, just hope anyone who met similar issue would give me some hint about it. Thanks in advance for any comment!
I have managed to install the kindle adb driver on my laptop, and could run "adb devices" and serial number showed , is there any adb command I could use to diagnose my device? Thanks in advance for any suggestion
Click to expand...
Click to collapse
Tough nut to crack. There is no adb magic that will assist in diagnosing/remedying the situation without root access. You can not utilize adb nor see the DCIM folder unless FireOS is running and USB debugging enabled; I believe the latter resets on every reboot. Given the stability window (10-15 sec) there is barely sufficient time to navigate to the option under settings before the device restarts. You could root and unlock but the limited FireOS run time presents an insurmountable obstacle as the procedure takes some time.
I don't think a factory reset will resolve the issue but is likely the only recourse. Sorry to share the bad news ...
Davey126 said:
Tough nut to crack. There is no adb magic that will assist in diagnosing/remedying the situation without root access. You can not utilize adb nor see the DCIM folder unless FireOS is running and USB debugging enabled; I believe the latter resets on every reboot. Given the stability window (10-15 sec) there is barely sufficient time to navigate to the option under settings before the device restarts. You could root and unlock but the limited FireOS run time presents an insurmountable obstacle as the procedure takes some time.
I don't think a factory reset will resolve the issue but is likely the only recourse. Sorry to share the bad news ...
Click to expand...
Click to collapse
Thanks for the information! I have connected my device with adb shell command, and also measured the time from adb server on to device reset, it was around 30 seconds, is it enough to perform the root with adb assistance? I think 30 seconds is enough for moving the jpg files out one by one, but might be insufficient for the mp4 files because some of them are over 1GB.
I can make the device enter FireOS original recovery and it never restarts, so I am thinking maybe it is possible to replace it with some custom recovery like TWRP which supports mount function and adb connection as well, but per my research from the forum, the custom recovery needs a unlocked bootloader, which needs the device to be rooted at first.
BTW, I found the jpg and mp4 files in /sdcard/DCIM/Camera, would it be affected by the factory reset? Or just data and cache would be affected? I know TWRP can perform a factory reset without affecting the internal storage, but not sure what the original recovery would do. Please kindly refer to the attached snapshot for more details.
Thanks in advance for any help
godhand_sh said:
Thanks for the information! I have connected my device with adb shell command, and also measured the time from adb server on to device reset, it was around 30 seconds, is it enough to perform the root with adb assistance? I think 30 seconds is enough for moving the jpg files out one by one, but might be insufficient for the mp4 files because some of them are over 1GB.
I can make the device enter FireOS original recovery and it never restarts, so I am thinking maybe it is possible to replace it with some custom recovery like TWRP which supports mount function and adb connection as well, but per my research from the forum, the custom recovery needs a unlocked bootloader, which needs the device to be rooted at first.
BTW, I found the jpg and mp4 files in /sdcard/DCIM/Camera, would it be affected by the factory reset? Or just data and cache would be affected? I know TWRP can perform a factory reset without affecting the internal storage, but not sure what the original recovery would do. Please kindly refer to the attached snapshot for more details.
Thanks in advance for any help
Click to expand...
Click to collapse
Unfortunately, your research is accurate. Device must be rooted (and usually unlocked) to install a custom recovery. Rooting requires a functioning ROM and typically takes some time (more than 10-30 sec) to complete.
As I recall a stock factory reset is comprehensive including contents of the DCIM folder. So you'll want to move out whatever you can before going that route. I also think the chances are small a reset (basically a user app/data wipe) will resolve the looping problem as it does not touch the system partition.
As a test turn off your AP before powering up the HDX. Outside chance establishing a WiFi connection is somehow contributing to the boot loop. Graphing at straws - not much else you can do in the absence of root.
I would also reach out to Amazon given the value of the device ($400+ USD). While likely out of warranty they may provide some accommodation if you play your cards right and get a compassionate agent. Highly unlikely you'll get anything close to full value but perhaps something.
Davey126 said:
Unfortunately, your research is accurate. Device must be rooted (and usually unlocked) to install a custom recovery. Rooting requires a functioning ROM and typically takes some time (more than 10-30 sec) to complete.
As I recall a stock factory reset is comprehensive including contents of the DCIM folder. So you'll want to move out whatever you can before going that route. I also think the chances are small a reset (basically a user app/data wipe) will resolve the looping problem as it does not touch the system partition.
As a test turn off your AP before powering up the HDX. Outside chance establishing a WiFi connection is somehow contributing to the boot loop. Graphing at straws - not much else you can do in the absence of root.
I would also reach out to Amazon given the value of the device ($400+ USD). While likely out of warranty they may provide some accommodation if you play your cards right and get a compassionate agent. Highly unlikely you'll get anything close to full value but perhaps something.
Click to expand...
Click to collapse
Thanks for the suggestion! I have moved all the pictures and part of mp4 files out of that device by adb pull command, and I found the time from adb connection built to device restarting allows around 300MB data transfer, so the mp4 files more than 300MB are still left in the device. I am thinking if it is possible to copy busybox into my device, and use split command to divide large files into files less than 300MB. Is it ok to use the one from https://busybox.net/downloads/binaries/1.21.1/ directly? Thanks in advance for any comment
godhand_sh said:
Thanks for the suggestion! I have moved all the pictures and part of mp4 files out of that device by adb pull command, and I found the time from adb connection built to device restarting allows around 300MB data transfer, so the mp4 files more than 300MB are still left in the device. I am thinking if it is possible to copy busybox into my device, and use split command to divide large files into files less than 300MB. Is it ok to use the one from https://busybox.net/downloads/binaries/1.21.1/ directly? Thanks in advance for any comment
Click to expand...
Click to collapse
Shouldn't be a problem download from that source. Splitting large files is a good idea.
Regardless of what eventually happens with your device I suspect there will be a take away regarding performing regular backups against personal files. Even something simple like drag/drop of important files/folders on occasion.
Davey126 said:
Shouldn't be a problem download from that source. Splitting large files is a good idea.
Regardless of what eventually happens with your device I suspect there will be a take away regarding performing regular backups against personal files. Even something simple like drag/drop of important files/folders on occasion.
Click to expand...
Click to collapse
Yeah! I did it! Thanks for the powerful busybox, which can continue to split large files even when it is interrupted by device restarting. With this feature I could pull any file out of a keeping restart device given there is enough disk space for storing the split files. The following shares my process & scripts used in the backup. Hope that helps others might meet the similar case.
1. move busybox in the device
adb push busybox /data/local/tmp/
adb shell chmod 755 /data/local/tmp/busybox
2. split the large file
adb shell /data/local/tmp/busybox split -b 300m /sdcard/DCIM/Camera/%%i /sdcard/tmp/split /*used in a DOS bat file*/
3.pull the files out
for /f %%i in (%1) do if not exist .\kindle\tmp\%%i adb pull /sdcard/tmp/%%i .\kindle\tmp\ /*used in a DOS bat file*/
4.combine the split files into what it should be.
cat splita* > a.mp4

[GUIDE][TOOL] Dreamtab increase internal storage

Summary​
Uses an external micro sd as "internal storage". Accomplished by a ramdisk edit to the boot image. The bootloader must be unlocked to use this tool and unlocking the bootloader will erase all personal data, game saves, etc on your device. For devices that already have their bootloader unlocked there is an option to transfer the current data to the external microsd card.
Considerations​
-The bootloader needs to be unlocked. The unlocking procedure erases all data on the device. If games saves, etc, are important use a tool that can back them up first.
-If you already have an unlocked bootloader the script allows you to transfer the data over and it should be like nothing ever happened but an increase in space. However, scripts are not perfect, nor can I take in to account every situation that might arise. If you have an unlocked bootloader and your data is important, please, please, please make a backup before trying this script.
-Micro SD card quality. All data will be read and written to the micro sd card. Not all cards are created the same. Many have very poor write performance, especially 4K writes. I tested about 6 or 7 cards and found the Samsung EVO+ as the best performing card. I didn't test the SanDisk extreme but it will likely be good as well. Increasing the size available is of no use if the speed is terrible and the tablet is laggy.
-Drivers. You must have fastboot and ADB drivers already set up and ready to go. The drivers are always a pain because so many different computers have different setups, previous drivers installed, conflicting drivers, etc. I attached the NabiLab2017 drivers to the post, even they can be buggy but provided an option if you choose. More about driver setup can be found here https://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Procedure​
ONLY FOR NVIDIA NV08B
Video: https://www.youtube.com/watch?v=aka8nUu7qQY
Video with data transfer: https://www.youtube.com/watch?v=ZbxqtzV33jI
ADB and fastboot drivers setup and tested
Micro SD card you want to use installed
Device connected and booted to Android
Unzip and run convert.bat
________________________
Thanks (again) @aicjofs for all the work you continue to do on these Nabi Dreamtab HD8s. TWRP, fsck fixes, stock 137 TWRP backups, and now this (which cures my biggest gripe about these tablets).
My kids are rough on them, but, because of the work you do, I've been able to keep them going & they grow with my kids. I just picked up 2 more refurbs from eBay today for $50 each. I'll be applying this internal storage fix as soon as they arrive.
I'm a Linux guy, not Windows. Would it help if I contributed a bash script that mimics your convert.bat? I'd have to assume that adb & fastboot are already installed & running, but I could probably script most of if from that point.
jvonhoff said:
Thanks (again) @aicjofs for all the work you continue to do on these Nabi Dreamtab HD8s. TWRP, fsck fixes, stock 137 TWRP backups, and now this (which cures my biggest gripe about these tablets).
My kids are rough on them, but, because of the work you do, I've been able to keep them going & they grow with my kids. I just picked up 2 more refurbs from eBay today for $50 each. I'll be applying this internal storage fix as soon as they arrive.
I'm a Linux guy, not Windows. Would it help if I contributed a bash script that mimics your convert.bat? I'd have to assume that adb & fastboot are already installed & running, but I could probably script most of if from that point.
Click to expand...
Click to collapse
Absolutely contribute, I don't do this for fame or money, just try to help others. Any and all additions are always welcome.
It should be easy enough to convert as most of the magic happens on the tablet itself, I think I only pushed a couple files to the tablet and made the ramdisk changes on the tablet too to keep the file size down. Weird how TWRP, the kernel, the tablet itself is all done in Linux but I only make windows scripts/apps.
I have quite a few of these tablets too, 5 maybe?. Kind of weird because Fuhu/Nabi screwed up that fsck thing so many people dump the tablet for next to nothing because they seem like garbage and crash all the time with loss of all the kids data but they are really a solid tablet. Try and find a screen of the HD8 quality on a modern kids tablet for $50. Shame about the crappy source code, if I could have got the camera to work right in the kernel I think I would have pressed on with the lollipop ROM and instead lost interest. This mod though breathes a lot of life into it still though. I have 3 of these running the mod and the kids still use it all the time with 64GB cards as their main storage and have had no issues.
aicjofs said:
Any and all additions are always welcome.
Click to expand...
Click to collapse
I've attached my attempt at a bash script for the swap. I got time to run one of my tablets through the gauntlet with this version, and only hit a snag at the check for fsck. Since I was that far, I just fixed the bug & applied the rest by hand. So, beware.
aicjofs said:
if I could have got the camera to work right in the kernel I think I would have pressed on with the lollipop ROM and instead lost interest.
Click to expand...
Click to collapse
I hear you there. I was hoping to see you get Lollipop going (even w/o a camera), just to have the battery saver. But, Greenify does a pretty good job keeping the battery going a while. So, again, thank you, and let me know if this script needs fixing.
Thanks for the work on this tablet. I am trying to salvage our dreamtab with your method. Unfortunately, I have a card inserted but the convert.bat never gave me any information about the sdcard like it did for you in the youtube video. Any idea what I might be doing wrong?
Thanks again!

Ulefone Armor x5 boot-debug.img

Ok, I get that boot-debug has been around for years... since android 10 for me, before that, it was variant=user, or variant=eng(ineer).
Strange how after I show boot-debug.img, magisk chooses this very path, but only after. Keeping in mind many people come here asking questions, and all those that know sit back and say nothing. Until they dont like what they see.
If you know better, and cant help, please keep your comments to yourself. This thread is intended to HELP, and is targetted toward those who CHOOSE to HELP because they CAN.
How I got su to work. Is this root? Now this is a good question. I dont want ANY overlaid system in my fone. I want to write to system like many others want to.
Not some google way of forcing us to use their mirrored online version of a locked filesystem already on my f'n.
Priority 1: I want to root my f'n without internet. Period. I do NOT want magisk using my credit. This proves we pay for magisk. I sometimes live so far from the world wide web, that offline is the only way to work. So I need to be able to root without google or THEIR employees offerings.
Priority 2: RW-able system.
So, I discover boot-debug.img for my f'n. Had it for a year, before I discovered it. Yeah, I discovered it after a year here asking, and getting NO replies that worked. Only after I'm vindicated to the naysayers 'thats been around forever...' yeah, try helping instead of useless comments.
In the end, I learned so much in such a short time. Constructive critiscism is NOT insulting. Magisk kills root in MY f'n. PERIOD. Camera does not work, location does not work, and I cant make/receive calls. But hey, it's an overlaid file system, of course it wont ALL work, I mean, I'd expect to lose a lil functionality, but disabling the GSI ability in dev options? I dont think so.. Worse, lack of adb or fastboot is produced in my f'n when using magisk, so tata magisk.
My logs actually explain all, so no more crappy adb logs. Yeah, I like simple adb, it works, or I'll MAKE it work.
Like this:
Attempt every possible method of flashing magisk according to tut's, nada. 3 different paths lead me to...?
1: The note9 recovery I found, that lopstom was kind enough to twrp for me (well appreciated) is the KEY to gaining root on my ulefone armor x5 mt6765. It turns out that the note9 recovery is actually an android 9 os, with a 'super' .img - and being android 9, the bootloader I used is an OLD bootloader, in particular, the variant=eng type. Note this, this is key.
2: With the note9 flashed to recovery I can RW system in android 10 properly, but only in twrp.
3: Discover boot-debug.img - yup, it's not quite a variant=eng build, but it does work for the following:
Flash boot-debug.img. By doing so, you get the adb root command, and the disable-verity options, way better than wiping vbmeta, which contains the 'is it rw, or ro' of every file in every partition to be mounted in their own partitions, but what most dont know, is each file mounted in it's own mountpoint also has the information contained by vbmeta, but for each seperate file. So unless you add the /null (one for system, the other for vendor) after the disable-verity...
Nah, wipe most of your directory structure, then wonder why in a RW-able system, it still dont work. Because each file in it's own mountpoint knows if the system directory SHOULD be ro or rw. That's EACH and EVERY stock file in it's OWN mountpoint, has the RW or RO inf for the system & vendor directory, ie, is system RW?
Example: Camera wont work, get it?
In the end, this is how I went about installing su.
Flashed boot-debug.img did NOT flash recovery. Flashed meefik busybox-arm64 to f'n, but did NOT install it, instead, I opened it to install it, top left, saved the busybox-arm64 and then flashed twrp, and while there, flashed the system_rw, to defeat the system_RW saying not enough space, I chose 1024, did the copy over of super_fixed, then rebooted, enabled system, THEN flashed the busybox-arm64 from twrp, and rebooted.
Results: I copied the busybox-arm64 su, from xbin to system. In order to defeat the system_RW saying not enough space, I chose 1024. Round numbers matter with system_RW, same senario as memory, so use sizes equal to how memory works. ie, 32, 64, 128, and multiples of.
Look at the adb posts in my closed thread.
With Su installed, I have to type exit TWICE to exit. without su in system, exit only needs typed once.
Now here is why I continue. I found root, but dont have the experience, but it's like this:
See all those lovely new file that end in .cel? Mine says platinum. That means I AM ROOT. By swapping out .cel files, I have all the access magisk denies me. .cel files... get on it devs... swap them out, try try try... find what I found.
I dont actually need su, but i need it for some apps. What I have proven, is that SU does NOT kill android 10_Q.
variant=user or variant=eng, is NOW dependant on .cel files, like, say, boot-debug.cel.
Have a nice discovery... I hacked googles latest offering my-cel-f
Edit: Cel files are found in the bootloader, a zero byte file, the file NAME decides what the loader can or cant do, PERIOD.
New root tools only require swapping these out, as well as a few system edits when done.
Ok, slight mistake in spelling so I'll add the following for you to 'see'..
userdebug_plat_sepolicy.cil
So it's not cel as I wrote in the first post, my point being just as valid.
Platinum clearly states there are more who's names I have yet to obtain...
Theoretically in my mind, if I swap the .cil file in the bootloader for say hypothetically:
engdebug_plat_sepolicy.cil... with the few edits seen in the android 10 notes I posted from china, the one where people say 'too much hassle' - I say, for them. Those notes show the rest of the cil files, so yeah, I got root OPTIONS to play with
Stay tuned for more scottish inventor style NOTES.
Edit: for the record: https://source.android.com/compatibility/vts/vts-on-gsi

Categories

Resources