I just uploaded tiny noot, a very minimal root tool for the NST glowworm. I think it would probably also work for the simple touch, but I've lent mine out and cannot test it to confirm.
I am basically a cobbler here; many thanks to GabrialD, DeanG and the folks with the minimal touch root tools, which this is based on - and of course to mali100 and the CWR team for getting that on the Touch and Glowworm. Everything below is put together with parts from those projects using what I've learned at XDA and from Dean's nook color repartitioning scripts.
They make it possible for someone like me to knock out a package that's a little more convenient to work from than booting noogie and manually copying in files.
I am using the clockwork recovery zip installation mode for copying in the minimal set of files - I'm not trying to support the google apps or the many interesting screen refresh hacks.
I am not including a modified uRamdisk - the stock uRamdisk supports ADB, and you can get root via adb wireless simply by typing su, so I chose to leave well enough alone.
GabrialD has already released a modified uRamdisk for the glowworm (to support root by default as well as the light) but since stock works for my purposes, I'm not using the modified one.
What it does include:
su and busybox
nook color tools in /system, so that nonmarket apps can be installed
adb wireless
ADW launcher
Amazon appstore, so there's at least once source of "easy" apps
Button Savior
Nook Touch Tools
Supermanager and the Busybox updater interface
The install process is three steps. Four if you decide - and you should - to make a backup of your device before you start. (that process is: make the noogie disk. boot from noogie. connect to your computer. dump the NSTG or NST using dd or another disk imaging tool, and is described in more detail with tips for lots of different operating systems at http://forum.xda-developers.com/showthread.php?t=1142983 That backup will let you restore your entire device to a known working configuration.
Download mali100's nook touch CWR disk discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1360994
the file itself is here:
http://forum.xda-developers.com/attachment.php?attachmentid=806433&d=1323121269
unzip the file and then write the .img file to an sdcard with your disk imaging tool of choice (dd in linux or win32 disk imager are two I use)
Once you've imaged the SD card, copy in these two zipfiles - leave them zipped:
http://www.mediafire.com/?ig75l5b9c24e7q6
http://www.mediafire.com/?2tfitzt97qqfaw7
Apply 1 of 2, then reboot, then
Apply 2 of 2
then remove your SD card and reboot. Although I have not gotten all the commands to run out of a single zipfile, Zydraka noticed, I think correctly, that you can run first the one and then the second without needing to reboot in between. I have done it that way successfully.
I tried putting all commands (copying the files, then setting permissions) into one file and the rooting process aborted in an ugly way. I ultimately needed to reimage the device to restore the oddly hosed /rom partition. After reimaging I was able to root successfully by running the two clockwork scripts back to back without a reboot.
A (very brief) guide to the CWR interface, for those who don't know it:
You will know your card is made correctly when you put it in your device and power on, and you see a clockwork gear nibbling at a nook N. Be patient while CWR loads; you will get to a screen with selectable menu choices.
Navigate up and down with the righthand buttons; navigate back with the lefthand upper button; choose an item or run a command using the raised n button.
Navigate down to "install zip file from sdcard" and hit N
Hit N again to "Choose Zip File from SDcard"
Navigate down to the first zip (labeled 1 of 2) and hit the n button
navigate to "yes - install"
hit the N button
once the first script is done, use the N button to navigate to and apply zip 2 of 2.
navigate back to the reboot menu using the lefthand side buttons. Once you are at the reboot menu item, you can pull the card, then reboot.
I used a 256 meg sdcard I had in the house for making the CWR disk. I find that to be a very convenient size for these disks - big enough to put a few files onto, not so big I wish I hadn't set it up as a CWR disk.
Thanks roustabout! It works great and it was super easy to do! I just got done installing a bunch of apps from Amazon.
Update: I just posted a tutorial with a video for noobs on my blog.
One thing to note, I didn't do the reboot that you mention in between the 1 and 2 packages and everything worked fine. I just installed 2 right after 1 and haven't had any problems.
Thanks for this, rooted last night everything is as it should be, the only issue I've run into is that I can't seem to install the Kindle app. It's not in the amazon market place, I tried backing up the APK from another device via EStrong and transferring the apk to the microSD, and I get a parsing file error. Any tips?
I have not been able to get Tasker to install yet, either.
One thing which sometimes works where other approaches fail (if you have the .apk file) is to ssh into your device (I use quicksshd) and log in as root, then cd to the directory the APK was copied to and issue the command
pm install blah-blah.apk
I have not yet tried that with Tasker, but it may also help with the Kindle app? I did need to do it for one of the apps I use, although I can't recall which one.
Edit: the 3.1 kindle app Zydraka points out works for me as well.
By default, the Kindle app is pretty unusable, very slow page turns. But by using the gesture-enabled screen refresh hack, it's very useable. (I found that using the no gesture version led to lots of apps just ignoring the hack's presence. I think Renate has a way around that, but I haven't read up on it.)
http://forum.xda-developers.com/showthread.php?p=22800284#post22800284
I got Tasker to install, but needed first to copy in the Maps jar and xml (to framework and permissions respectively) reboot and install via ssh - it might have worked just to reboot.
Since others may want Tasker available, putting the maps.jar and maps.xml files into the tinynooter is trivial, and I'll probably get to it soon.
I found that the older version of the Kindle app works, version 3.1.0.30. There's a donwload for it at Android Freeware. http://www.freewarelovers.com/android/app/kindle
So, after this, will the glowlight work in all apps? I need to make sure that, moon+ reader and EZpdf will glow in the dark, before I purchase the new nook.
thanks.
The glowlight seems to work in all apps. I'm not clear on how exactly it's turned on and off; it might be possible to have an app that uses a long press on the N button for something else, and that might interfere, but so far it works fine in the launcher, in the Kindle reader, in fbreader, in Newsrob (that I know I've tested.) even if you had an app that was doing something funny with that long press, you ought to be able to turn it on from the settings menu that comes up on a short press.
Once the glowlight is on, it seems to stay on until your screen goes to sleep, regardless of what applications you may also be using.
This is part of why I didn't get into the boot environment at all in this approach - I knew from manual rooting that I didn't have to change out uRamdisk so I decided to leave it all alone.
Thanks for tinynoot! It's working well for me, and glowlight behaves normally.
roustabout said:
I just uploaded tiny noot, a very minimal root tool for the NST glowworm. I think it would probably also work for the simple touch, but I've lent mine out and cannot test it to confirm.
I am basically a cobbler here; many thanks to GabrialD, DeanG and the folks with the minimal touch root tools, which this is based on - and of course to mali100 and the CWR team for getting that on the Touch and Glowworm. Everything below is put together with parts from those projects using what I've learned at XDA and from Dean's nook color repartitioning scripts.
They make it possible for someone like me to knock out a package that's a little more convenient to work from than booting noogie and manually copying in files.
I am using the clockwork recovery zip installation mode for copying in the minimal set of files - I'm not trying to support the google apps or the many interesting screen refresh hacks.
I am not including a modified uRamdisk - the stock uRamdisk supports ADB, and you can get root via adb wireless simply by typing su, so I chose to leave well enough alone.
GabrialD has already released a modified uRamdisk for the glowworm (to support root by default as well as the light) but since stock works for my purposes, I'm not using the modified one.
What it does include:
su and busybox
nook color tools in /system, so that nonmarket apps can be installed
adb wireless
ADW launcher
Amazon appstore, so there's at least once source of "easy" apps
Button Savior
Nook Touch Tools
Supermanager and the Busybox updater interface
The install process is three steps. Four if you decide - and you should - to make a backup of your device before you start. (that process is: make the noogie disk. boot from noogie. connect to your computer. dump the NSTG or NST using dd or another disk imaging tool, and is described in more detail with tips for lots of different operating systems at http://forum.xda-developers.com/showthread.php?t=1142983 That backup will let you restore your entire device to a known working configuration.
Download mali100's nook touch CWR disk discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=1360994
the file itself is here:
http://forum.xda-developers.com/attachment.php?attachmentid=806433&d=1323121269
unzip the file and then write the .img file to an sdcard with your disk imaging tool of choice (dd in linux or win32 disk imager are two I use)
Once you've imaged the SD card, copy in these two zipfiles - leave them zipped:
http://www.mediafire.com/?ig75l5b9c24e7q6
http://www.mediafire.com/?2tfitzt97qqfaw7
Apply 1 of 2, then reboot, then
Apply 2 of 2
then remove your SD card and reboot. Although I have not gotten all the commands to run out of a single zipfile, Zydraka noticed, I think correctly, that you can run first the one and then the second without needing to reboot in between. I have done it that way successfully.
I tried putting all commands (copying the files, then setting permissions) into one file and the rooting process aborted in an ugly way. I ultimately needed to reimage the device to restore the oddly hosed /rom partition. After reimaging I was able to root successfully by running the two clockwork scripts back to back without a reboot.
A (very brief) guide to the CWR interface, for those who don't know it:
You will know your card is made correctly when you put it in your device and power on, and you see a clockwork gear nibbling at a nook N. Be patient while CWR loads; you will get to a screen with selectable menu choices.
Navigate up and down with the righthand buttons; navigate back with the lefthand upper button; choose an item or run a command using the raised n button.
Navigate down to "install zip file from sdcard" and hit N
Hit N again to "Choose Zip File from SDcard"
Navigate down to the first zip (labeled 1 of 2) and hit the n button
navigate to "yes - install"
hit the N button
once the first script is done, use the N button to navigate to and apply zip 2 of 2.
navigate back to the reboot menu using the lefthand side buttons. Once you are at the reboot menu item, you can pull the card, then reboot.
I used a 256 meg sdcard I had in the house for making the CWR disk. I find that to be a very convenient size for these disks - big enough to put a few files onto, not so big I wish I hadn't set it up as a CWR disk.
Click to expand...
Click to collapse
You know, it should be nice if before using the packages other people create, for your own project, you asked them for permission to use them, if not, at least create your own scripts.....
Yes I'm refering to me.... thats not cool.
Anyway, the two step process is not necessary here, thats just for preventing some Gapps database corruption, you edited that code away allready and there are no Gapps installed, so add the code to correct the permissions on the first zip, and everything should work fine, no need to rm dalvik either if you arent modifying framework.jar, etc, it should also speed the first boot time.
I apologize - this was intended to be a quick hack and largely for my own use (as I was testing stuff on both my and my girlfriend's glowworms) but I realized there were a lot of folks trying to root their gw's manually. I thought it worked well enough to share.
I didn't intend to present it as original and if I appeared to I apologize.
Say the word and I will yank the thread outright, and I would have no objection to your asking the mods to do so, either.
roustabout said:
I apologize - this was intended to be a quick hack and largely for my own use (as I was testing stuff on both my and my girlfriend's glowworms) but I realized there were a lot of folks trying to root their gw's manually. I thought it worked well enough to share.
I didn't intend to present it as original and if I appeared to I apologize.
Say the word and I will yank the thread outright, and I would have no objection to your asking the mods to do so, either.
Click to expand...
Click to collapse
Don't worry, just stating that before creating a thread with others people work, you should ask them.
Everything is fine, It didn't even pass my mind the idea of reporting it, we are a small niche community, active members must be praised, so dont worry, and I encorage you to keep deving ^^, just that before using other peoples work and starting a thread with it, ask them for permission, no one is gonna deny it and it's the kind way of doing things .
I'm planning to get my hands on a Glow tonight, so over the weekend I should be able to get together a full Nooter for it.
tiny noot - also works for older NST
Just so folks know, I've confirmed that the tinynoot rooter also works on the NST running 1.1.2 firmware.
It will probably work on earlier firmware also, since it is not replacing uRamdisk or framework files.
Are Supermanager and the Busybox Updater supposed to work? Supermanager crashes back to home, and Busybox won't install.
Did you apply both files, and is there an sd card in your device? I just tested the busybox updater and was able to get it to update the installed busybox. It requires that you have an sdcard inserted to work - I remember being puzzled by that the first time I tried using it on a device.
supermanager is crashing. I hadn't tried running it on the device before, and hadn't noticed that.
Looking at logcat, yes, supermanager's crashing in the background quite a bit. It seems to be looking for things which are not available, for instance, a dialer, and erroring out when it can't find them.
roustabout said:
[...] supermanager is crashing. I hadn't tried running it on the device before, and hadn't noticed that.
Click to expand...
Click to collapse
Supermanager has always been a problem, at least for me, using TouchNooter. I believe it's intended to provide file manager capability, particularly for installing APKs on uSD. Once I get Market (Play Store) access, reinstalling supermanager fixes the problem. At that point, I don't need it anymore.
I've always had to work around this when rooting my Touch devices. I'd suggest a basic file manager be provided instead for Day 1.
I'm rooted with tinynoot. Recently I've been experiencing excessive battery drain. I'm eliminating apps I'd installed to if that helps. Wondering if anyone has experience with apps that are problematic in that regard? Dropbox? Amazon Appstore? Facebook? 1Mobile Market? I assume nothing that was provided by default with tinynoot. Thanks.
Hi Glowco,
I'd suggest installing task management apps to get a view of what is actually running (not all processes relate to an installed app icon that you can uninstall). I use Advanced Task Manager to view running apps, and Autorun Manager to control what processes start up at boot time.
Ian
Thanks, I'll keep that in mind. In the meantime, as an experiment I uninstalled several apps including Amazon Appstore, 1Mobile Market, FB, and Wireless ADB. Good result - my battery charge hasn't decreased in an hour and a half. If I decide I miss them I can try adding them back and use your method.
That's good news!
I'd suggest that Wireless ADB is not to blame, since it does not stay resident once it's closed and in any case does nothing until you click the big red button
Of the others, I have Amazon Marketplace installed and I don't experience any battery issues (I'm Glownooted not Tinynooted but don't think that's relevant in this discussion), but I can't speak for the other two apps. If I were paranoid (and I am! ) I would point at Facebook, since it's purpose is marketing and wants to follow your every move
Ian
I've read through quite a few threads (but forgive me I didn't go through all 976), and searched for some answers on google, so I've done my research as best I could. Please understand that if this question's already been asked and answered, I just didn't know the proper keywords to find it.
so here's my issue. Got a note 2 dec. 12 loved it and eventually wanted to root it, but by the time that happened, my USB port started malfunctioning. to make a long story short, the port charges if i mess with the microUSB side a lot, and even then one small nudge and it loses connection. PC USB connection is completely out of the question. I've tested it on 4 computers with 15 different USB ports (both on machines that had USB drivers/other Samsung software installed, and machines that were Samsung-free) and the best I can get is an alternating on-off connection; you'll see the lightning bolt flash across the battery, then not, then on... etc etc.
Basically here's what I want to do:
I want to use ABD backup to completely image my phone: I have the new one, so I would like to simply copy it over to the new one and avoid setting all the countless system/UI settings.
If this is not possible, I want to use Rerware's MyBackup to backup whatever I can.... problem is, I've tried this and getting the backup files off the device is tricky. direct USB connection is not possible. I tried via Wifi file transfer and somehow the ZIP file (1.85GB) got corrupted, and when I used zip repair tool from recovery toolbox (nifty utility) it found nothing in the zip file after an hour-plus scan. When I tried copying it to the external card using samsung's stock explorer app, it only copied over 255MB and nothing else.
If all this is not possible, I would like to know what options or solutions someone could (please) offer as to how to get some data (at least pictures) off my device. When I get it back from amazon wireless, I'm going to try to sync them all retroactively to dropbox or picasa or something, but I want to know if there's something else I haven't (more than likely) thought of.
Also, I would also like to know if there's an option for root without USB. the problem is that in order to do ADB backup (my #1 hope) I need to be rooted. I saw a CFAuto root that says it works through ODIN download mode, but then I found another thread that said you have to have your phone hooked up via USB in order for that to work.
I've seen there're ADB via wifi apps on the market (if there's a root without USB possibility) and was wondering if these could be used somehow?
Lastly, this phone is getting returned to amazon wireless, so really, I want no evidence of any tinkering that voids warranties. If this is not possible, I just want my damn data.
To recap, since that seemed like a rant:
is there a way to image my entire phone to transfer to my new one? if not....
is there a way to backup most (if not all) settings etc to restore to new phone?
any other creative ideas on how to get data off the old device?
sorry if this seems frivolous, I'm just sick of this crap. I got a pretty advanced smartphone and in less than a month it somehow corrupted 80+ pictures, lost USB data connectivity, and now certain STOCK apps are malfunctioning. any help or advice would be appreciated.
I will continue researching.
My company's IT department set an enterprise-level Exchange 2010 ActiveSync mailbox policy that enables a local device wipe after multiple failed password attempts. My child was playing with my phone and apparently enacted this, creating a factory reset and complete wipe of my phone. I am now looking for any way to recovery the hundreds of pictures (and videos and other data) that were stored locally on the phone's internal memory. Note: I do NOT have an SD card and unfortunately I did not back up the files in the cloud or anywhere else. (shame on me)
I have scoured this board and others and been unable to find a solution or work around. Or, the things I've tried have been thwarted by issues. (example: apparent inability to enable USB Mass Storage (UMS) on an un-rooted device?) I'm fairly savvy with computers (mainly Windows) and am very logical and methodical in troubleshooting but I don't have dev experience, Linux familiarity, file recovery experience or any advanced knowledge in this area. I would be very grateful for any insight. My basic question is this:
Question: How can I recover deleted files from a stock 4.1.2 SGH-I747 after a factory reset?
I will actively monitor this thread and answer any additional questions. Thanks in advance for any help or guidance!
admitch4
Just wanted to bump this thread as I am still desperately trying to find a solution.
Also, here is an update/recap:
I have a Samsung Galaxy S3 (SGH-I747) running Android 4.1.2. My phone is rooted. A factory reset was inadvertently performed on the phone that wiped the entire internal memory (I do not have an external SD card). I had many very important pictures of my children, family, etc. that I would really like to get back if it’s at all possible. I installed DiskDigger and performed a scan for all .jpgs. The tool sees “/data” of 12.24 GiB (and other devices) but the scan does NOT result in any files. Does this mean none of the files are recoverable? Or, would it help to try another tool? I’m happy to purchase DiskDigger Pro or try anything else if it will help at all. Or, I'm also up for trying much more drastic measures if there is a reasonable likelihood of some recovery. Thanks in advance for any information or feedback.
Snipped
Hi, you should try "UnDelete"
https://play.google.com/store/apps/details?id=fahrbot.apps.undelete&hl=en
This may or may not work on the phone as long as you didn't overwrite many files. ( I have not tested hard resets.)
Thanks
EDIT : Sorry! I was wrong! I just tried a different app, and it recovered half of a deleted image on a phone I was repairing. Its called DiskDigger.
Search in /data (that is the internal SDcard)
https://play.google.com/store/apps/details?id=com.defianttech.diskdigger&hl=en
Hey all,
as I was backing up files from my phone (internal storage full, 500MB to go) via USB, and after I'd done a bunch of PDFs and what not, I wanted to start moving videos / photos. That failed instantly and after that, EVERY SINGLE IMAGE / VIDEO file was gone from the phone. I installed three "recovery" apps - they couldn't find a thing. I have a bunch of family stuff I really, really would like to have back.
I downloaded the MIUI unlocking tool and wanted to 'get going' with rooting, but I'm getting a "Unlock will erase user data" notification, for if I continue. This does not seem what I want.
- Can I continue without definitely trashing any hope of recovering files?
- Is there another way to get to files that magically disappeared (no Sync on, no OneDrive auto-backup, no nothing at all) that do not required root, and/or ...
- Is this a "known" problem? I cannot seem to find anything.
Many, many, many thanks......
As MIUI Unlocking tool says, it will delete all the data on the phone.
Whelp, this is happening. I'll give it a go before I can't get the files...
I have to wait 2 weeks for the MIUI tool to allow unlocking the bootloader. So I guess at this point I'd mostly like to know if the Mysterious Case of the Disappearing Files is something that's more common on the Redmi Note 5 - or on Android 8.1 / MIUI? I'd like to assure the reader at this point that, while threads like these are a dime a dozen and it often boils down to user error, I'm not a complete nitwit and assure you I was doing nothing other than Ctrl-X -> Ctrl-V to harddrive, got an error message, 40GB were magically freed up on internal storage and ALL files were gone. All of it. Folders too.
Updating thread title, hope that's okay..
Realistically, considering different "undelete" / "recovery" apps are not finding ANYTHING!!! at all, how likely is it even that something will be found once the device has been rooted? This almost seems like it had a system reset while it was still enabled...... Just everything gone / re-encrypted / whatever. Is that even possible? Again, though, the device DID NOT reboot. The files were there......then 40GB was gone.
It is possible to recover the data but the process will require root permissions. Install Disk digger pro from playstore. And give root permissions it can easily recover the most of the photos ( May recover all but possibilities are less ) Give a try bro it will definitely help you. As it helped me before.
I had something similar back when I had Redmi Note 3. Files just disappeared when I put them inside obb folder. However, they reappeared when I entered the recovery (it was custom) and I copyed them via cable onto my pc. They weren't there when I connected normally turned on phone to the pc, and it was annoying. So whatever you are doing, don't format your phone, otherwise you'll lose the files forever.
If rooting and installing an app to recover the files won't help, I suggest you flashing twrp and trying to find them from there using the cable and a pc, or whatever.
Thanks. It's a shame I'm finally "getting in to" rooting only now, now that I have a problem. When I tried many years ago I felt it was too complicated and most of all risky....
The main problem I have with rooting is that the Mi Unlock Tool wishes to Reset the phone, re-encrypting it in the process, and destroying any hope of recovering data. I intend to flash OrangeFox before it can reset.... Does anyone have a better idea....? It's really very, very much appreciated!