* SOLVED * Unable to Backup NST GL (Rooting) - Nook Touch General

Every copy of noogie.img.gz I get I am unable to extract as all the instructions I have read require. I have tried Winrar and 7zip, but each say the file is broken. I have downloaded the file from three different locations and it's the same story every time. Noogie.img.gz is a 3MB file that I can only view in 7zip. It shows 11 files (boot.scr, boot.script, cfg.bin etc etc). Is this noogie.img.gz the img or do I need to extract the .gz first to acquire an img?
Edit: I finally found a copy that appears to work. Nook-Root-Kit addictivetips . com . The file is 2.2MB and yields a 77MB (noogie.img) file that is associated with WinImage. When viewed in 7zip it shows the same 11 files. I became impatient, I used it, and it worked. The only issue was the "Root Forever" screen was halfway cut off, and it took several attempts to restart the Nook, but all was well.

Related

To those who have Error msg when upgrading to froyo.

Yesterday I got a repeated problem when I try to install the Froyo. The phone keep give me error msg, File not exist, aborted.....
I figured that it was because I did everything in the phone (downloading, copy/paste, and renaming the file to update.zip). After several failures, i downloaded and renamed the file in a PC, and directly copied the file to the Sdcard root dir. Then it is updated smoothly. I don't know what happened with that phone downloaded file. It seems exactly the same as the one from PC. Maybe the phone downloaded one was attributed with some property that did not allow the bootloader to read it.
Hope this helps.

Trying to root via unrEVOked..."reflash.exe is not a valid Win32 application."

Trying to root via unrEVOked..."reflash.exe is not a valid Win32 application."
I seem to be the only one to ever have this problem. I followed the unrEVOked instructions - I installed HBOOT drivers and installed modified USB drivers. When I get to the point where I turn the phone back on, plug it in, and open "reflash.exe", the "reflash.exe" file won't open. I get the error message "reflash.exe is not a valid Win32 application." I've tried downloading the unrEVOked package again and again. I've tried extracting the files again and again. I've tried opening the file as an administrator. I also get an error message whenever I extract the files, but they seem to be successfully extracted anyway.
JTravisRolko said:
I seem to be the only one to ever have this problem. I followed the unrEVOked instructions - I installed HBOOT drivers and installed modified USB drivers. When I get to the point where I turn the phone back on, plug it in, and open "reflash.exe", the "reflash.exe" file won't open. I get the error message "reflash.exe is not a valid Win32 application." I've tried downloading the unrEVOked package again and again. I've tried extracting the files again and again. I've tried opening the file as an administrator. I also get an error message whenever I extract the files, but they seem to be successfully extracted anyway.
Click to expand...
Click to collapse
Corrupt download. Clear your cache (on the PC) and download again. The reason why you keep getting the same error even after downloads is because IE/FF is using the locally stored copy of the file instead of redownloading again.
I'm not exactly sure what you mean by "clear the PC cache", but I had CCleaner clean up a lot of stuff and then redownloaded the unrEVOked package. I extracted the files from the package, and again, it said that reflash.exe (and only reflash.exe) was corrupt, and again, I get the same error message when trying to open reflash.exe.
Enrevoked is an EXE, there is nothing to extract or remove?
Just start the program, it pushes the file to the phone, reboots it, phone finds image, roots itself basically and bobs your uncle, you have root.
It is fully automated, there is nothing to open or extract.
Problem solved. I downloaded the file to a different hard drive. I don't why, but files that I download via my browser frequently get corrupted.

AGPS Patch

For everyone having problems with gps even after editing the gps.conf i want to mention this thread:
http://forum.xda-developers.com/showthread.php?t=1252011
This worked on my device copying the two files gps.conf and SuplRootCert to /system/etc and i was able to get a gps-fix the first time since buying the tpt
Did you make a backup of the ROM using Recovery as suggested in the AGPS Patch thread, or did you just try it and get lucky. Also, which method did you successfully use on your TPT?
Thanks
That would be method 2, i did everything manually. I don't know if the automatic versions would be compatible with the tpt.
If you need help with the manual steps, i can write you a more detailed instruction.
P.S. Didn't make a backup, but its always a good idea.
It appears method 2 worked for me as well.
-I chose the standard GOOGLE BUILD recommended by the dev.
-Downloaded to device
-Made a backup copy of my original gps.conf file by copy and pasting it with File Manager HD.
-Using ES File Manager with Root access and /system mounted, I copied the two files (gps.conf & SuplRootCert) and pasted them into the /system/etc folder (overwriting the original gps.conf file).
I get a gps accuracy of 30 meters so far in google maps, but the arrow is within 6-10 feet of where I was standing, if not closer.
Does this patch work for anyone else? I've replaced the gps.conf file but still cannot lock on to satellites.
I'm on the newest 0089_ROW.
Did not work for me.

[HELP] Retrieving TWRP data [SOLVED]

Hello, I would like to know how I could extract backed up TWRP data on my computer? maybe because the data was large TWRP split it into two files : data.ext4.win000 and data.ext4.win001 (sizes 1.5 and 1.2 GB)
How I got there:
I've been using XenonHD rom for quite a while, and this rom uses koush's superuser app.
I noticed there was a newer version on the market so I installed it; however it appears the one used by the rom developer was modified and therefore had a different package name: I ended up with two superuser apps, one of them asking to update the binaries, which I did.
After that the phone got stuck and rebooted two or three times before being stuck indefinitely at 'updating app' message right after the bootanimation. I tried:
- to wipe dalvik cache but it was still stuck;
- I reflashed the rom + gapps but it was still stuck;
- then I went to the /data/app/ folder (via TWRP) and deleted the superuser app i installed from market, as well as the corresponding data in /data/data, wiped cache and dalvik again: still the same...
-the I decided to make a backup via TWRP : one of the whole system, and one of Data partition only;
- then I realised I couldn't transfer it to my computer in TWRP, so I finally made a factory reset, re-flashed the rom+gapps, and then (it worked) copied my backup to the computer
now; how can I retrieve the data of my apps only, as I guess it is the system data that is messed up?
Of course I tried to restore the Data backup in twrp and it got stuck again the same way....
any help greatly appreciated!
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
forvrknight said:
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
Click to expand...
Click to collapse
It actually helped me, thanks a lot!
Two Questions
asim0 said:
On this file I used AccessData FTK Imager,
Click to expand...
Click to collapse
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
asim0 said:
All you have to do now is to merge the two data folders and voilà
Click to expand...
Click to collapse
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
pi_yush said:
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
Click to expand...
Click to collapse
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
number_thirty_two said:
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
Click to expand...
Click to collapse
Thanks number_thirty_two, I copyed thes to a folder I named untar in my home folder of CYGWIN, and extracted my system files perfectly
C:\cygwin\home\carl\untar\
system.ext4.win000
system.ext4.win001
tar xvfz system.ext4.win000
tar xvfz system.ext4.win001
Apologies for resurrecting this, but does anyone know how to extract them if they were compressed as .comp files?
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voil
Click to expand...
Click to collapse

[Q] Rename Misshaps, File can't be found.

I was cleaning up my SDcard and renaming some files in the process. during this, I forgot that "&" is a no-no when naming files (using Doobloo file manager) and try to rename a video using it.
the problem is that, since then, I can't find the file anywhere. I tried using ES explorer pro and plugging the device on a PC, but no go.
now, I know that the file is there, just unreacheable (adding a & to the name would not delete the file, right?). How can I find it and rename it properly (since it is probably just taking up space this way).
My Device is a Galaxy S4 from Vivo, Brazil (GT-I9505)

Categories

Resources