Related
I own Lenovo Yoga Tablet 2 830L, firmware "upgraded" to 830LC, rooted. I've tested the provided solution only on it, though it should work on other models, and maybe even on other devices.
I've built exFAT and ntfs-3g drivers from the most resent sources, and made a shell script, to auto-mount a microSD at the system start. Root and SuperSU are required. Currently, the installation is manual. The project is here:
https://github.com/Lurker00/Android-fs/releases
Please read the description I've written, at least "How to mount?" section, and, of course, the disclaimer.
Edit: Now it has a CWM/TWRP installation zip for easy use!
Lurker0 said:
I own Lenovo Yoga Tablet 2 830L, firmware "upgraded" to 830LC, rooted. I've tested the provided solution only on it, though it should work on other models, and maybe even on other devices.
I've built exFAT and ntfs-3g drivers from the most resent sources, and made a shell script, to auto-mount a microSD at the system start. Root and SuperSU are required. Currently, the installation is manual. The project is here:
https://github.com/Lurker00/Android-fs/releases
Please read the description I've written, at least "How to mount?" section, and, of course, the disclaimer.
Click to expand...
Click to collapse
Thanks a lot for putting effort into this! I haven't tried it yet, but I'd suggest to create an app/APK which installs the files necessary and which features some buttons for mounting and unmounting. A CWM package is not such a good idea due to the fact that we have only temporary CWM and hence installing would still be a bit painful. This app could be something like a Yoga tablet 2 toolkit, which could maybe even include my sharpness fix
I've created CWM/TWRP installation zip with exFAT and NTFS drivers, and mounting script. It can be downloaded from here:
https://github.com/Lurker00/Android-fs/releases
Now, if you have rooted your Lenovo Yoga Tablet 2 (any screen size), and have SuperSU installed, just download UPDATE-android-fs-1.0.1-install.zip, install the same way, and start using exFAT (strongly recommended!) or NTFS (not recommended!) microSD.
To safely unmount for hot unplug, use Android settings. For mount after hot plug, better to reboot your tablet.
Note: the microSD file system is checked before mounting, and, if errors are found, it is mounted as read-only. So, if you find out that you can't write to the microSD, safely remove it and check (allowing to fix errors) it under Windows. It is strongly recommended to check and fix under Windows, because both exFAT and NTFS are produced by Microsoft, and no open source software is able to correct the file system errors correctly!
I have Yoga Tablet 2 8''. But the installation zip contains binary files for a number of platforms, and may work on other Lenovo Android devices. Being manually installed, the drivers are confirmed to work on:
Lenovo Vibe Z2 Pro
Lenovo Vibe Z2
Lenovo S90
so I see no a reason why they will not work being installed via recovery console.
I almost thought my Yoga 2-850F is broken as it was impossible to mount or format any micro SD card. Even when I tried formatting the card with my android phone using various file systems (i.e. exfat, ext4 etc.), I would always get an error. Finally, just flashing the zip did the trick. Thanks for the script!
I've updated the drivers to version 1.0.2:
1. One more supolicy rule added to the mounting script. Without it, unmount from Android Settings didn't work.
I didn't put per-platform binaries this time, because the recovery zip contains them all.
I'm sorry for so frequent updates, but
exFAT/NTFS fuse drivers binaries for Android v1.0.3
The problem is that the original exFAT driver was designed to update the file system only at unmount events, but the current Android never unmounts microSD mounted not by Android's vold process Meaning, file system corruption may happen on a reboot or power off.
Version 1.0.2 partially addresses that issue, and is stable enough. Only freshly created directories can be damaged by a reboot, and only if there were no any file operations after that, i.e. a rare case. Version 1.0.3 ensures that the file system is kept consistent almost always. It can be damaged only by removing microSD card during write operation.
Nevertheless, I plan to make at least one more release, to keep microSD clean, when there are no pending writes. Also, I'd try to improve the write performance compared to 1.0.3, without a penalty of the file system consistency.
I just have released
exFAT/NTFS fuse drivers binaries for Android v1.0.4
and I can say I'm quite satisfied with both performance and robustness of the resulting exFAT driver (no changes were made to ntfs-3g). So, I believe, it is the final build for a while.
Worked perfect.
Tested and working perfect:
Tablet: Lenovo Yoga Tablet 2 Pro Android 4.4
Micro SD: Lexar 128GB (633x) Formatted to exFAT
I flashed it via temp recovery and did a reboot from recovery. Then shut down the tablet and put the exFAT card in. Booted up and not so much as a whisper. The system recognised and mounted the card without any problems.
Thanks again for your hard work.
Now to find a custom ROM. I think I've got more chance of finding rocking horse s**t than a ROM for my tablet though
Hello,
Thanks fort the work.
I have got a lenovo yoga tab 2 1050F updated tout lollipop and rooted.
Can you tell US if it is works with both KitKat ans lollipop?
Can you détail the installing methode?
Thanks in advance.
Kalachnikos said:
Hello,
Thanks fort the work.
I have got a lenovo yoga tab 2 1050F updated tout lollipop and rooted.
Can you tell US if it is works with both KitKat ans lollipop?
Can you détail the installing methode?
Thanks in advance.
Click to expand...
Click to collapse
I didn't upgrade to Lollipop myself, and I don't want to.
The driver and the mounting script are reported to work under Lollipop, but, for auto-mount on boot, they rely on /system/etc/install-recovery.sh script modified by SuperSU to launch with required privileges on system boot, which is not the case for Lollipop. It works flawlessly under Kitkat though.
You can find the detailed instructions at the github place from the link above. It's as easy as to root.
Hi,
Should this work on the Tab 2 A10-70, which has ARMv8 (Cortex-A53, MT8165 chipset)?
Looking for a sustainable solution to get exFAT working on that Lenovo device, it's a real let down it doesn't by default...
Many thanks !
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Lurker0 said:
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Click to expand...
Click to collapse
I'm still on kit-kat, and rooted. I've yet to install CWM/TWRP though, so that's the first step. I'm pretty limited on tech skills so that might be an issue, but I'll see how it goes ; if it's a simple zip flash then great, otherwise things may get too out of hands
If/when I get around to testing, I'll keep you posted - but in the meantime many thanks for the work on this!
Thank you for your work. It works with exfat microsd 64 go sandisk and my lenovo 1050F tablet under lollipop.
I don't know how android system works, sorry for newbie questions
I try to have my external SD mounted in R/W at launch time.
In superSU, i change the following parameter : activate su on starting to enable but it does not work.
I have read that /system/etc/install-recovery.sh is executed by super-su. I can see at the end of this shell /system/etc/install-recovery-2.sh is called but it does not mount the SD in R/W...
Any help is appreciated! Thank you.
Unfortunately, Lollipop has more protection, and it launches install-recovery.sh in a very restricted environment, not enough for the mounting script to work properly. And I don't know a way to launch my script at the boot time with required privileges under Lollipop. One of the reasons I don't want to "upgrade" my 830LC to 5.0.1!
I have a Lenovo yoga tablet 2 830LC, upgraded to Lollipop 5.0.1 recently. There are no proper root guides for the Lollipop version anywhere on the forum, and since I'm interested in rooting my device and also be able to write to the external sd card, I request you to guide me on this. I'm sorry if this isn't the proper thread for my request but would be appreciated much.
zach181 said:
Worked perfect.
Tested and working perfect:
Tablet: Lenovo Yoga Tablet 2 Pro Android 4.4
Micro SD: Lexar 128GB (633x) Formatted to exFAT
I flashed it via temp recovery and did a reboot from recovery. Then shut down the tablet and put the exFAT card in. Booted up and not so much as a whisper. The system recognised and mounted the card without any problems.
Thanks again for your hard work.
Now to find a custom ROM. I think I've got more chance of finding rocking horse s**t than a ROM for my tablet though
Click to expand...
Click to collapse
Hi.. i hv rooted and in that process flashed supersu thru temp recovery twrp... now iam not sure how to activate again twrp... any advise...thanks
Same way you did it when rooted. It is launched one time only.
mmlbbntr said:
Should this work on the Tab 2 A10-70, which has ARMv8 (Cortex-A53, MT8165 chipset)?
Looking for a sustainable solution to get exFAT working on that Lenovo device, it's a real let down it doesn't by default...
Click to expand...
Click to collapse
Yeah, it's a shame that Lenovo hasn't included exFAT support.
Read on...
Lurker0 said:
You can try yourself...
There are binaries for all kinds of arm, including 64-bit. The mounting script won't work under Lollipop. But people with rooted devices and stright hands manage to make the drivers launched at right time with right options. I heard successful reports for very different devices.
Click to expand...
Click to collapse
I love you, man! :good:
I just got your drivers to work on a Lenovo Tab 2 A10-70F running Android 5.0.1.
Yes, the install-recovery-2.sh mounting script doesn't work there, because it runs in a restrictive security context on Lollipop, if I've understood it correctly.
I flashed your update zip, noticed that it didn't work, then searched for some other options. I thought about init.d, but that isn't supported on this tablet either.
However, SuperSU, which I've already been using, offers a "su.d" mechanism, similar to init.d, and I used that to get it to run!
One needs to have SuperSU and busybox installed, and flash your update zip with a custom recovery (this one works for the Tab 2 A10-70, F & L).
Then create /system/su.d directory and move the /system/etc/install-recovery-2.sh script there. It can be named anything, I renamed it "/system/su.d/00mount_exfat_ntfs.sh".
I'm not too sure about the permissions, I used 755 for both the directory and the script.
In the SuperSU settings (accessible in the SuperSU app), the option "mount namespace separation" must be disabled.
I have a 64GB SanDisk Ultra microSDXC card, but for some reason it wouldn't want to work with exFAT on this tablet at first.
/dev/block/mmcblk1p1 did not show up while the card was inserted, only /dev/block/mmcblk1.
I formatted the card with NTFS, and that worked. I changed it back to exFAT, and then it finally did show up. Weird.
Anyway, would you recommend exFAT or NTFS, Lurker0?
I've used this card with NTFS on an older tablet, and it was rock solid, which I can't say about my experience with exFAT.
One minor caveat: the card isn't automatically mounted on insertion. Mounting requires another execution of the mounting script, either by rebooting or running "su -c /system/su.d/00mount_exfat_ntfs.sh".
Is there any way to make that automatic?
Thanks again.
Tzul said:
However, SuperSU, which I've already been using, offers a "su.d" mechanism, similar to init.d, and I used that to get it to run!
Click to expand...
Click to collapse
Thank you for finding! I'll read more and try to update my package.
Tzul said:
Anyway, would you recommend exFAT or NTFS, Lurker0?
Click to expand...
Click to collapse
NTFS is not flash-friendly, so I believe exFAT is better.
Tzul said:
Is there any way to make that automatic?
Click to expand...
Click to collapse
It requires to write an application to watch for system mount events and run that script. I'm lazy to do it
Well, I have been going through many tab owner problems on this forum who have tried everything on the book to get their tab back running. this experimental process is only for those people who have no option left than to throw away their tab as a dead glorious paperweight or play with it as a Frisbee. hopefully it can recover or at least it can open a new way for getting out of a brick or perhaps be a good learning experience, just for the sake of it. what else would you want to do? if your device is un-repairable? at least this can take a backup for the complete device in a different way though.
So what really is this about?
Well, Samsung tab 2 emmc is pretty much notoriously getting scarier, either it is happening because of flashing a wrong kernel or doing wrong with your tab, or in some cases where people had no clue. A sudden attack and the tab was dead. you may be lucky to get a replacement and get the tab running up again. but not all could be solved and resolved.
but what if we provide the tab a second emmc(your external card emulated and working as an exact image of the internal emmc with all the system files with their partition on it?) sounds good eh? there are 2 sides of this coin. one, our device is not made that way and it's definitely not going to work at all, second, it can work after a little hardware modification provided you have the right files and right tools and a insanely expert brain. Now the chances of this working is like that of flipped coin landing on it's edges. very tricky.
But how we can achieve this then?
Well, there are users on the internet that have some sort of success in this, while it wasn't guaranteed for their device, that this process can work for all and there is definitely nothing like this sort ever found for our device. which is on omap chipset, it's the debrick method. you can't tell unless you are from the development department of Samsung. So, I would say even if it's 0.0000000001 percent of having a chance to work for us. I would like to keep it.
Debrick.img? what does it do? how to get it?
Well, this file is generally taken out from a stock rom from location /dev/block/mmcblk0 which is where pit stores the data for all the partition and from there we can extract all the important parts, including the boot-loader, recovery, cache, hidden, sbl1, sbl2, factoryfs param, modem, EFS, DataEFS to a .img file. (as far as my definition goes for better understanding). please feel free to go through all the post that you can find about the debrick, or if you have more knowledge please share.
I was just going through these posts.
The whole process for sg s3 http://forum.xda-developers.com/showthread.php?t=2660566
http://forum.xda-developers.com/showthread.php?t=1818321 a guide that explains about taking backup of the entire memory block with all partitions or single partition. it's quite old but informative.
fixing a bootloader
http://forum.xda-developers.com/showthread.php?t=2345860
there are different parts to it, first is getting the bootloader written on a external sd card. but we still don't know if our device will be able to treat the external sd card as an internal emmc. it is yet to be found out.
my theory is suppose if we can get out the whole partition along with system written on a external card, can we make the device treat it as a internal emmc? will it then be possible to revive a dead internal emmc tab? there are chances it might. still no practical though and no guarantees for sure.
but it makes you feel better, I managed to get out those partition on a .img file which could be written on a external card as well. basically an image of your emmc. this might be a good backup too for those who would like to be safe in case a emmc bug hits them too.
Now, To get this data we need volunteers to take these files from their working rooted stock rom and upload these files for every model of samsung tab, if they wish to contribute to our community, you are welcome. or at least keep it safe on their disks. although, this process will require atmost care as we are dealing with bootloaders here, and one wrong bootloder and it
won't work, as much as my knowledge goes, there are two- the ics and jb for our tab 2. still there are many other variants and I really have no clue, how to work this out all by myself. so, I would like other great minds share their wisdom upon this and please before sharing files, mention everything you can, right from your
1. Device model number
2. 8gb or 16gb
3. Bootloader(ics or jb)
4. Stock rom, custom rom,
5. firmware
6. Baseband
7. Country and to your name.
Now before pulling out this file, I have a doubt, as I have got few imgs option. there is 128mb, 200mb, 256mb, 512mb and also I have got one img of around 2.17gb as well which is the complete backup I could take out from my device.
I am not sure which one to choose that's going to work. people have mostly used 128mb file to get access to the download mode, I guess in that 128mb, there is enough files needed to boot your device into download mode and recover from hard bricks, but there is no evidence as for now in our device section as to which is suffient for us. So for first try, we take 128mb, and keep doubt aside for one process.
but suppose it's our emmc bug and we want to use the external as a image of the damaged internal, in that case I suppose we need to take out the whole info! is it really possible with the 2.17gb of my device complete data? ah, I would really like to know about the answer myself, in case it hits my device, I would be prepared myself
anyways to try this you must have a sd card reader and use a external card of 16gb or 8gb depending upon your device variant (card class 10 required, on others it has high chance of not working at all)
Now the process to extract the file
The script that you need to enter into terminal emulator(download one from playstore) this will backup a 128mb file on your sdcard.
Code:
#su
#busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
128MB is arbitrary. on some devices 70MB was sufficient, on our device? maybe or maybe not. please test or help me answer this correctly, if I'm wrong. but untill then, use 128mb, if we fail, we will look for other options.
other dd commands
Code:
1. dd if=/dev/block/mmcblk0 of=/sdcard/backup.img
backup whole partitons thus will be large size and takes more time.
Code:
2. dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=70
70mb data from mmcblk0 will be copied to sd card
Code:
3 dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=512
512mb data from mmcblk0 will be copied to sd card
Code:
4. dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=4096
large size more than 4GB and more time consuming
Procedure
1. Connect the external sd card to the card reader move all the files to your pc and format it.
2. find the correct debrick.img image from post 2.
3. Download and extract this software win iso burner
4. Open the software win32diskimager.exe and browse the debrick.img
5. Successfully Write the debrick.img onto it.
6. Put the sdcard in your device
7. Pray, or do the cha cha, praise the droid lord.
8. switch it on or press power button + volume down/up, whatever you can.
9. if you can then get into download mode, you can try to flash stock firmware or dance your way around.
10. report us back what happened.
1. Download Debrick dump imgs. (128mb)
Samsung tab 2 10.1 P5100 16gb
jellybean boot-loader.
was on custom 5.1 rom and twrp recovery from UAE firmware.
Samsung Tab 2 P3100 16gb
shared by @jak978 on post 6 Hit thanks for him.
more will come, when people will share.
for other guides and ways
interesting, unfortunately my broken emmc have replaced with eemc from note 2, tho mine is p3100
jak978 said:
interesting, unfortunately my broken emmc have replaced with eemc from note 2, tho mine is p3100
Click to expand...
Click to collapse
So, you're one of those lucky ones. Getting a replacement is still the best way. So, do you think my theory here could work? Anyways it would be an interesting answer to find out. But people would need to share files here first for any samsung tab 2 model. I hope it becomes helpful rather than just interesting.
billysam said:
So, you're one of those lucky ones. Getting a replacement is still the best way. So, do you think my theory here could work? Anyways it would be an interesting answer to find out. But people would need to share files here first for any samsung tab 2 model. I hope it becomes helpful rather than just interesting.
Click to expand...
Click to collapse
here you go tab2 P3100 16GB
Anybody having any luck with this procedure??
Rag888 said:
Anybody having any luck with this procedure??
Click to expand...
Click to collapse
Well I still haven't faced the emmc bug, so can't really test on my device yet. nobody else who faced this issue had tried this and posted or shared any of the findings here.
Updating the emmc firmware via. ISP gives back life to >80% of affected devices.
16 GB Tab 2 have a known faulty EMMC (MAG2GA). It can happen, that your EMMC get "read only", so you can't perform any write actions (also you can't format) anymore.
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device life time is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
Click to expand...
Click to collapse
On a faulty EMMC firmware it happens a lot faster if the emmc reaches a wrong value.
Sadly Patching the emmc fw isn't possible running the device, at least there's no known kernel on chip power-on Method...
Those from europe can contact @html6405 , he is able to update the emmc firmware and he can also replace the emmc if needed.
Note:
Sharing a whole copy if mmcblk0 isn't good, because it will include efs partition which is sensible data.
~ All my work, news etc. on http://andi34.github.io ~
Found something interesting printing the pit using heimdall:
https://paste.omnirom.org/view/4173cc20
Someone knows what the GANG partition is for?
I wonder if it is the emmc firmware because emmc.bin is stored there...
I am waiting to get the fixed emmc firmware, i might be able to tell you once i have it.
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
Note:
Sharing a whole copy if mmcblk0 isn't good, because it will include efs partition which is sensible data.
Click to expand...
Click to collapse
Yes, better to keep them private. Users do not share, just keep a backup with yourself.
thanks for your thorough research.
Android-Andi said:
Found something interesting printing the pit using heimdall:
https://paste.omnirom.org/view/4173cc20
Someone knows what the GANG partition is for?
I wonder if it is the emmc firmware because emmc.bin is stored there...
Click to expand...
Click to collapse
I did notice the GANG partition since you mentioned it(strange I never realized this before as I have looked at the pit file many times earlier as well.) located at 0x64C.
it does look like the emmc firmware partition. what else it should have?
jak978 said:
interesting, unfortunately my broken emmc have replaced with eemc from note 2, tho mine is p3100
Click to expand...
Click to collapse
hi jak978,
i plan to replace my p3100 emmc with p5100 emmc, can i just flash p3100 firmware using odin after change the emmc?
some more, can u re upload the debrick dump for p3100, it says "file not found" in your link.
regards,
alms
here you go tab2 P3100 16GB UNABLE TO GOT FILE PLEASE SHARE THE FILE PLEASE
---------- Post added at 12:56 PM ---------- Previous post was at 12:49 PM ----------
billysam said:
1. Download debrick dump imgs. (128mb)
samsung tab 2 10.1 p5100 16gb
jellybean boot-loader.
Was on custom 5.1 rom and twrp recovery from uae firmware.
samsung tab 2 p3100 16gb
shared by @jak978 on post 6 hit thanks for him.
More will come, when people will share.
Click to expand...
Click to collapse
please re share p3100 file i need it my tab was not work or trell me any way to get emmc chip from online or else process
my tab only in condition on restart restart.....
No recovery and firmware ll able to write on p3100
please help your reply too much helpful for me please give file p3100 so i can use your method
asiffrluv said:
here you go tab2 P3100 16GB UNABLE TO GOT FILE PLEASE SHARE THE FILE PLEASE
---------- Post added at 12:56 PM ---------- Previous post was at 12:49 PM ----------
please re share p3100 file i need it my tab was not work or trell me any way to get emmc chip from online or else process
my tab only in condition on restart restart.....
No recovery and firmware ll able to write on p3100
please help your reply too much helpful for me please give file p3100 so i can use your method
Click to expand...
Click to collapse
Look at this on eBay http://www.ebay.com/itm/192025936615
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Hi,
I just tried this method. The tab boot on the sdcard, i have the charging logo displayed, and then screen turns black. The driver change from omap4430 to Android, and keep this driver until i unplug the usb cable.
On linux, the tab device is recognized as Android. Same on windows (loaded in virtualbox from linux).
adb device display an unauthorized device.
So from this step, it is still impossible to flash the tab.
Anyway thanks for sharing this; even if its painfull to lose a tab, it is nice to learn how all this work.
if other people have more information to share, i would appreciate any new info on this subject
billysam said:
1. Download Debrick dump imgs. (128mb)
Samsung tab 2 10.1 P5100 16gb
jellybean boot-loader.
was on custom 5.1 rom and twrp recovery from UAE firmware.
Samsung Tab 2 P3100 16gb
shared by @jak978 on post 6 Hit thanks for him.
more will come, when people will share.
Click to expand...
Click to collapse
Links are dead can you update them?
@Android-Andi @billysam @jak978
Sorry for pinging do you still have the p3100 debrick img?
No, never had it.
Ugh dev host dosent work in 2020
Still waiting for the link
For my own use ( see https://forum.xda-developers.com/nook-touch/general/how-to-force-reinstall-nook-simple-t3971367 for details ), I have put the needed updates into a new NookManager1.2.2 package (https://www.dropbox.com/s/kdlabh09txkx3k9/NookManager1.2.2.img?dl=0 ) so that it can be used for Nook Simple Touch 1.2.2 directly with updates described here (https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048), thanks to nmyshkin (https://forum.xda-developers.com/member.php?u=5562185).
Hello -- Not sure if anyone reads this anymore....
I'm trying to root a NST. I believe I've created the micro sd properly, and when I insert it and reboot, I see "Nookmanager Loading...". But then it just hangs there.
I've used a 32gb class 10 card. I have seen elsewhere that I should not use anything higher than class 6. Could this be the problem?
smjohn1 said:
For my own use ( see https://forum.xda-developers.com/nook-touch/general/how-to-force-reinstall-nook-simple-t3971367 for details ), I have put the needed updates into a new NookManager1.2.2 package (https://www.dropbox.com/s/kdlabh09txkx3k9/NookManager1.2.2.img?dl=0 ) so that it can be used for Nook Simple Touch 1.2.2 directly with updates described here (https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048), thanks to nmyshkin (https://forum.xda-developers.com/member.php?u=5562185).
Click to expand...
Click to collapse
Hello -- Not sure if anyone reads this anymore....
I'm trying to root a NST. I believe I've created the micro sd properly, and when I insert it and reboot, I see "Nookmanager Loading...". But then it just hangs there.
I've used a 32gb class 10 card. I have seen elsewhere that I should not use anything higher than class 6. Could this be the problem?
lm2 said:
Hello -- Not sure if anyone reads this anymore....
I'm trying to root a NST. I believe I've created the micro sd properly, and when I insert it and reboot, I see "Nookmanager Loading...". But then it just hangs there.
I've used a 32gb class 10 card. I have seen elsewhere that I should not use anything higher than class 6. Could this be the problem?
Click to expand...
Click to collapse
I don't think the class is the problem but your NST might be struggling with the 32 gb size.
nmyshkin said:
I don't think the class is the problem but your NST might be struggling with the 32 gb size.
Click to expand...
Click to collapse
Thanks for that tip. Is there a *minimum* size I need to use for Nookmanager1.2.2?
lm2 said:
Thanks for that tip. Is there a *minimum* size I need to use for Nookmanager1.2.2?
Click to expand...
Click to collapse
Probably 4 gb. The backups are compressed, but I don't recall offhand the size.
nmyshkin said:
Probably 4 gb. The backups are compressed, but I don't recall offhand the size.
Click to expand...
Click to collapse
I have a 2gb, and then next larger is 32gb. I guess that means I could root, but then not have enough room for a backup. And I'm guessing making a backup is advisable? Is there anyway to get back to stock w/o having made a backup?
lm2 said:
I have a 2gb, and then next larger is 32gb. I guess that means I could root, but then not have enough room for a backup. And I'm guessing making a backup is advisable? Is there anyway to get back to stock w/o having made a backup?
Click to expand...
Click to collapse
OK, I should have checked before my last response. The original thread specifies 512 mb as a minimum, room enough for NookManager and a backup.
nmyshkin said:
Probably 4 gb. The backups are compressed, but I don't recall offhand the size.
Click to expand...
Click to collapse
I just tried with the 2gb, as googling suggested that many others had used that. And I'm still getting the same issue: I see "NookManager Loading...." in font of normal darkness right when I boot up, and then after hanging like that for 20 seconds, that text fades to the point where I can hardly see it, and nothing happens but that.
lm2 said:
I just tried with the 2gb, as googling suggested that many others had used that. And I'm still getting the same issue: I see "NookManager Loading...." in font of normal darkness right when I boot up, and then after hanging like that for 20 seconds, that text fades to the point where I can hardly see it, and nothing happens but that.
Click to expand...
Click to collapse
I guess it's possible that the image is faulty. It's not difficult to update the original NookManager card yourself. You can follow the link referenced in the OP which leads to my update instructions. That may work out better for you.
nmyshkin said:
I guess it's possible that the image is faulty. It's not difficult to update the original NookManager card yourself. You can follow the link referenced in the OP which leads to my update instructions. That may work out better for you.
Click to expand...
Click to collapse
Thanks, I appreciate your helping me through this. The person who first told me about rooting NSTs warned me against using sd cards higher than class 6. This thread seems to hint at the same issue, esp. with class 10. I've been using class 10. It is hard to find anything lower, but I just ordered a class 4 from eBay and I guess I'll wait to see if that works any better.
lm2 said:
Thanks, I appreciate your helping me through this. The person who first told me about rooting NSTs warned me against using sd cards higher than class 6. This thread seems to hint at the same issue, esp. with class 10. I've been using class 10. It is hard to find anything lower, but I just ordered a class 4 from eBay and I guess I'll wait to see if that works any better.
Click to expand...
Click to collapse
Yes, I've seen the warnings about class 10, even with the Nook Tablet, but I've not encountered problems. As you say, other than a special order, its hard to come by anything that's not class 10. The NookManager card I've used for many years is a SanDisk class 10 Ultra. Never had a problem with it. YMMV.
nmyshkin said:
Yes, I've seen the warnings about class 10, even with the Nook Tablet, but I've not encountered problems. As you say, other than a special order, its hard to come by anything that's not class 10. The NookManager card I've used for many years is a SanDisk class 10 Ultra. Never had a problem with it. YMMV.
Click to expand...
Click to collapse
Thanks very much again. I'll give the special order card a try when it arrives, and if it doesn't, I guess I'll try to update the original NookManager, as you first suggested.
Is it possible to downgrade a Nook's firmware to 1.2.1 in order to use the original NookManager? Or maybe that's just more trouble than it could possibly be worth.
lm2 said:
Thanks very much again. I'll give the special order card a try when it arrives, and if it doesn't, I guess I'll try to update the original NookManager, as you first suggested.
Is it possible to downgrade a Nook's firmware to 1.2.1 in order to use the original NookManager? Or maybe that's just more trouble than it could possibly be worth.
Click to expand...
Click to collapse
There's no sense in "downgrading" to FW 1.2.1. While you're waiting for the card to arrive I'd sure give yourself a chance to make your own NookManager update. You might be pleasantly surprised.
nmyshkin said:
There's no sense in "downgrading" to FW 1.2.1. While you're waiting for the card to arrive I'd sure give yourself a chance to make your own NookManager update. You might be pleasantly surprised.
Click to expand...
Click to collapse
Alright, awesome; will do. Thanks!
nmyshkin said:
There's no sense in "downgrading" to FW 1.2.1. While you're waiting for the card to arrive I'd sure give yourself a chance to make your own NookManager update. You might be pleasantly surprised.
Click to expand...
Click to collapse
Well you were right: I was able to successfully root the device with a class 10 sd card by changing the scripts and replacing the jars in the way you instruct here. Thank you!!
Unfortunately I'm not able to establish any successful internet connection with either wifi source I use in my home. Any thoughts on why that might be? (I was having connectivity issues before I rooted it, too.) -- Actually, the device does say I'm successfully connected, it's just that the browser doesn't work and I also cannot connect to the Amazon App Store for Android (which, as you know, is a default app option on the rooted device).
Maybe I should just say what I'm trying to achieve: I'd like to use the NST as an external e-ink screen. So all I really need is a way to work with txt files that can be saved to an sd card. It would be nice, too, if I could email them to myself or otherwise upload them to the cloud from the NST, but that's not essential.
Any tips on how I might achieve that limited functionality even if I can't fix these connectivity issues?
Thanks again!
lm2 said:
Well you were right: I was able to successfully root the device with a class 10 sd card by changing the scripts and replacing the jars in the way you instruct here. Thank you!!
Unfortunately I'm not able to establish any successful internet connection with either wifi source I use in my home. Any thoughts on why that might be? (I was having connectivity issues before I rooted it, too.) -- Actually, the device does say I'm successfully connected, it's just that the browser doesn't work and I also cannot connect to the Amazon App Store for Android (which, as you know, is a default app option on the rooted device).
Maybe I should just say what I'm trying to achieve: I'd like to use the NST as an external e-ink screen. So all I really need is a way to work with txt files that can be saved to an sd card. It would be nice, too, if I could email them to myself or otherwise upload them to the cloud from the NST, but that's not essential.
Any tips on how I might achieve that limited functionality even if I can't fix these connectivity issues?
Thanks again!
Click to expand...
Click to collapse
I was able to install Jota via an apk on sd, so that's a start (for this n00b)!
lm2 said:
Well you were right: I was able to successfully root the device with a class 10 sd card by changing the scripts and replacing the jars in the way you instruct here. Thank you!!
Unfortunately I'm not able to establish any successful internet connection with either wifi source I use in my home. Any thoughts on why that might be? (I was having connectivity issues before I rooted it, too.) -- Actually, the device does say I'm successfully connected, it's just that the browser doesn't work and I also cannot connect to the Amazon App Store for Android (which, as you know, is a default app option on the rooted device)
Click to expand...
Click to collapse
There is likely nothing wrong with your wifi. Reading a little further in the NookManager update thread you will see that the Amazon App Store has been dead for a long time. The same is true for the stock browser. You can uninstall both (for the stock browser that just entails deleting the apk file from /system/app and rebooting.) Also in that same post is a copy of Opera Mobile. That browser will work. You can side-load it if you need a browser.
As for email, either some version of k9 or the stock aosp email client will work. If you follow the link in my signature you will find a list of apps I run. One is the stock email with a link. You can search the forum for k9. I posted it somewhere for somebody long ago but don't remember exactly where.
nmyshkin said:
There is likely nothing wrong with your wifi. Reading a little further in the NookManager update thread you will see that the Amazon App Store has been dead for a long time. The same is true for the stock browser. You can uninstall both (for the stock browser that just entails deleting the apk file from /system/app and rebooting.) Also in that same post is a copy of Opera Mobile. That browser will work. You can side-load it if you need a browser.
As for email, either some version of k9 or the stock aosp email client will work. If you follow the link in my signature you will find a list of apps I run. One is the stock email with a link. You can search the forum for k9. I posted it somewhere for somebody long ago but don't remember exactly where.
Click to expand...
Click to collapse
Thanks so much. For various reasons, I decided to flash back to stock and then re-root. My NST then ended up with many more apps on it than it did the first time. And I also now see more of the Nook's rooted file structure, too. Not sure what was different.
My main task right now is updating the uImage and uRamdisk files with these here. My understanding is that this is required to get host mode working for an external keyboard. But I have no idea how to go about doing this. Any tips on that would be gratefully received!
lm2 said:
Thanks so much. For various reasons, I decided to flash back to stock and then re-root. My NST then ended up with many more apps on it than it did the first time. And I also now see more of the Nook's rooted file structure, too. Not sure what was different.
My main task right now is updating the uImage and uRamdisk files with these here. My understanding is that this is required to get host mode working for an external keyboard. But I have no idea how to go about doing this. Any tips on that would be gratefully received!
Click to expand...
Click to collapse
These are the instructions I have used for changing kernals: https://forum.xda-developers.com/t/...issue-explanation-added.1563645/post-24168019
There is also a CWM kernal update file somewhere on the forum, but that would require preparing yet another card with CWM, etc. If you have ADB working, the earlier solution would be simplest.
Only use my Note 3 to play audio and video files.
Recently noticed some video files missing on a 64GB exFAT mSD card.
1st thought they had been deleted by Note 3.
Just did a chkdsk scan and everything OK. Have a screen capture of this but do not know how to attach.
Additional Info: My Note 3 has stock Android 4.4.2 (KitCat) and never rooted.
Am Open to all suggestions how to correct this problem.
Hey I might can offer some assistance. BUT IM A FRESH NEWBIE TO THIS. I MEAN I JUST STARTED REALLY MESSING WITH MY PHONE 2 DAYS AGO. First what type of note 3 do you have? (ie. Sprint=SM-N900P) do you have service on your phone? Do you have any experience with custom ROMs?
SurageBook said:
? (ie. Sprint=SM-N900P) do you have service on your phone?
I hope not as this is not the Sprint model forum .
OP i would copy data off then full format sd card as a starter .
Damaged files look in the Lost Files folders .
Click to expand...
Click to collapse
SurageBook "what type of note 3 do you have?" Verizon "have service on your phone?" No "Do you have any experience with custom ROMs?" No
JJEgan "...i would copy data off then full format sd card as a starter." Agree did copy the wanted data.
As previously mentioned have used Windows longer than Android so used chkdsk to examine & fix the mSD Card. Everything was OK and all the missing files were shown and Not damaged,
Since posting I backed up all the wanted data and then put the mSD card back in my Note 3. All the missing files were there and undamaged. Can anyone explain this?
From experience most Windows users reload the OS every few years.
Am wondering if I should Factory reset my Android 4.4.2 OS?
Any recommendations?
Man if you just use that phone for a media device just create a backup of your phone, SD card, and copy it to your PC then install custom ROMs until you find one you like and root that bad boy. My note 3 is my primary phone with service and I have about 10 custom ROMs on my SD card that I switch every couple of days. Earlier today I was on Havco OS 2.8 android 9 now I'm on some rom that when it turns on theres a pink unicorn and its on android 7. Its easier than you think. Things you need are 1. TWRP(for your phone model) 2. Odin(on PC to flash things to your phone*optional) 3. Custom ROM 4. magisk(to root your phone) 5. Gapps (for the android version that's on the custom rom*optional) 6. Enjoy
SurageBook Thanks for the tips!
Do you know if any good tutorials concerning how to root the Verizon version of Note 3?
I don't know about Verizon I'm on sprint but if you go to the Verizon section you'll find a guide for your firmware. https://forum.xda-developers.com/verizon-galaxy-note-3/general
Please guys post in the forum for your phones .
Otherwise i see a reply on here not your models leading to a bricked phone .
KermitJ said:
Only use my Note 3 to play audio and video files.
Recently noticed some video files missing on a 64GB exFAT mSD card.
1st thought they had been deleted by Note 3.
Just did a chkdsk scan and everything OK. Have a screen capture of this but do not know how to attach.
Additional Info: My Note 3 has stock Android 4.4.2 (KitCat) and never rooted.
Am Open to all suggestions how to correct this problem.
Click to expand...
Click to collapse
try this, this might help with the missing media files
https://play.google.com/store/apps/details?id=com.house.noranuko.mediarescanner
though i use 128gb sdcard and is formatted in exfat but mediascanner always crashing on me on stock android 5.0, thats why i dont use stock atm
r0mushii Thanks for the tip!
Tried to use the link you provided https://play.google.com/store/apps/d...mediarescanner but got 404 error.
Then used search words "Media Scanner" but got a lot of similar apps.
KermitJ said:
r0mushii Thanks for the tip!
Tried to use the link you provided https://play.google.com/store/apps/d...mediarescanner but got 404 error.
Then used search words "Media Scanner" but got a lot of similar apps.
Click to expand...
Click to collapse
heres an alternative link(from apkpure): https://m.apkpure.com/media-re-scan...n-above-4-0/com.house.noranuko.mediarescanner
r0mushii somehow these links are not working? got a 404 from 2nd link https://m.apkpure.com/media-re-scan-...mediarescanner
Made a screen capture but do not know how to attach?
media.Re.Scan: media scanner, work on above 4.0
That is the link and it is live on both .
JJEgan "media.Re.Scan: media scanner, work on above 4.0 That is the link and it is live on both"
Thanks!
Was the link problem only on my PC? I am using Chrome browser.
Also is it possible to post screen captures?
I have the zipped file atvXperience_v4_S905X_RT_BCM.7z and extracted that and only that to the micro sd card. Not sure when to insert, before or after it boots to android screen. and does the sd card need just basic mbr or guid? End game is trying to get the android side working again so I can utilize the apk loader. It came with superuser and it bricked when I updated superuser. So I think the seller had it locked down? No copyright infringement. I was actully lucky to get the roms off the card that came with the console. So on the emuelec side I think I can add roms no issue.
It took the update to 4.0, so pleased about that. But I want to make the android side like a media center so I can plug an external ssd into it and have whatever movies/shows I want right on my roku tv. Can someone help me out please? I've came this far, so I'm not stopping lol. I guess this is my new tech junky hobbie. LOL 45, and still love ****ing with tech.
Thanks!
Mike