[Q] Mail app attachment error: File browser stopped unexpectedly - One (M8) Q&A, Help & Troubleshooting

HELP - i'm new at this -
I bought a HTC One M8sw off Ebay - it came from China. I can see based on the settings and using Root Checker Basic that it has been rooted and customised and I have SuperSU app showing up. Thus, I have a File manager installed which probably does not come as stock with the mobile? The file manager works fine. Issue is that, when I'm in the stock MAIL app and i try to attach a file by clicking on File or click on Document/PDF or Office Document - I get the following error:
------------------------------
Sorry!
File Browser has stopped unexpectedly
When I go into the error report:
It says the process which name is com.htc.FilePicker
-----------------------------------
I have gone through all the trouble shooting with HTC phone Support including clearing cache and data, rebooting, safe mode for 24 hours, deleting and re-adding email accounts, but still does not work. They have told me now that i need to a factory reset and see if this fixes it ... but i prefer not to do that as I don't want to remove all the amazing customisation which came with the phone as i wouldn't know how to get it back!
Anyone else experience this? Can you please let me know if there's anything i could do to fix this issue without going back to a factory reset? Any further information required?
Note: I'm not a techie ... so have limited to any knowledge on how to root, check root etc.

Well, are you running customized stock or are you on a custom rom?
Go into Settings > About tablet > Build number and post what you got there.
It could be that the former owner only removed the stock HTC file manager app. Do you have it in your app drawer?
Or check in system/priv-app/ and look for the FilePicker.apk.
If it is not there you could just download the stock firmware (whichever version you are on now), extract it and look in system/priv-app for the apk, copy it to the corresponding folder on your phone, set the permissions to read-only and reboot.
This is just a wild guess since I don't know what rom you are running, but it's a place to start...

berndblb said:
Well, are you running customized stock or are you on a custom rom?
Go into Settings > About tablet > Build number and post what you got there.
It could be that the former owner only removed the stock HTC file manager app. Do you have it in your app drawer?
Or check in system/priv-app/ and look for the FilePicker.apk.
If it is not there you could just download the stock firmware (whichever version you are on now), extract it and look in system/priv-app for the apk, copy it to the corresponding folder on your phone, set the permissions to read-only and reboot.
This is just a wild guess since I don't know what rom you are running, but it's a place to start...
Click to expand...
Click to collapse
In the Log file of Error - I see the following:
Type: crash
Process: com.htc.FilePicker
Time: 1414606270952
Device Active Time: -1
Flags: 0x4088be45
Package: com.htc.FilePicker v639000400 (6.0.767298)
Application Label: File Browser
System App: true
Installed By: null
App Active Time: -1
Build: htc/htc_europe/htc_m8dug:4.4.2/KOT49H/352881.12:user/release-keys
Project Branch: M8_DUGL_K44_SENSE60:379917
Changelist: 352881
Release: 4.4.2
Number of hibernations: 0
Time of resume from hibernation: unknown
Bootloader: 3.18.0.0000
Radio: 1.18.30306251.22G
----- KERNEL -----
Linux version 3.4.0-gcd8e74f ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Jun 10 19:10:59 CST 2014
---------------
In the System/About - I see:
Build: 1.45.401.12.CL352881 release- keys
The File Manager is in the app drawer just like all other apps. I do not how to go to System/ priv to find the file picker.
Hope the above makes sense. Any help appreciated.

htcm8new said:
In the Log file of Error - I see the following:
Type: crash
Process: com.htc.FilePicker
Time: 1414606270952
Device Active Time: -1
Flags: 0x4088be45
Package: com.htc.FilePicker v639000400 (6.0.767298)
Application Label: File Browser
System App: true
Installed By: null
App Active Time: -1
Build: htc/htc_europe/htc_m8dug:4.4.2/KOT49H/352881.12:user/release-keys
Project Branch: M8_DUGL_K44_SENSE60:379917
Changelist: 352881
Release: 4.4.2
Number of hibernations: 0
Time of resume from hibernation: unknown
Bootloader: 3.18.0.0000
Radio: 1.18.30306251.22G
----- KERNEL -----
Linux version 3.4.0-gcd8e74f (ro[email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Jun 10 19:10:59 CST 2014
---------------
In the System/About - I see:
Build: 1.45.401.12.CL352881 release- keys
The File Manager is in the app drawer just like all other apps. I do not how to go to System/ priv to find the file picker.
Hope the above makes sense. Any help appreciated.
Click to expand...
Click to collapse
Any Response from anyone out there in the interwebiverse?

htcm8new said:
Any Response from anyone out there in the interwebiverse?
Click to expand...
Click to collapse
It's really tough to give you any advice without knowing what modifications have been done to the stock system....
The best way would be to flash back to stock or flash a custom rom and start from there...
But then you would have to do find out which modifications have been done and redo them yourself. Sooner or later you probably have to anyway...

It's been suggested that I just delete the current HTC file browser and install another which may do the trick? Thoughts?

Possibly. I suggested something similar myself in an earlier post.
But a bit of learning will be involved....
The file browser is installed as a system app and you need root priviliges to uninstall it. Do you have root?
If not sure downlad RootChecker from the Play Store and run it.
I suspect to provide the functionality you want, the new file browser also needs to be installed as a system app (apps installed by the user are normally installed to data/app, factory loaded apps are in system/priv-app).
The difference between both is all about permissions which apps need within Android to be able to execute certain functions. User apps are way more restricted in what they are allowed to do and access than system apps.
You can accomplish both by using Titanium Backup (if you have root). It can uninstall system apps and it can covert an app installed by the user to a system app.
So to replace the current file browser you need to:
Get Titanium Backup, grant it root rights (which it will ask for when you launch it).
Backup (just a precaution) then uninstall the current file browser in TiBu
A little detour here:
You could give this a shot: Backup, then uninstall the file browser, reboot, then restore it in Titanuim Backup.
Reboot and check if you can attach files now. This would be an easy solution if the apk currently installed is not corrupted.
If that doesn't work:
Download a custom rom for your current rom version (was it 4.4.2?) that has the HTC file browser. I know that scrosler's roms (stock rooted or CleanROM) have it. Not sure about the many other roms for this phone.
Extract the zip file to it's own folder and drill down through them until you find system/priv-app.
Inside should be a file called FilePicker.apk. I believe that is the HTC file browser.
Copy that apk to your phone
In Settings > Security enable "unknown sources"
Using the phone's file browser find the apk, tap to install it.
Open Titanium Backup and find the newly installed app, convert it to a system app.
Reboot.
That would give you a fesh copy of the stock file browser.
Hope this helps.

Thanks for the detailed explanation. Steep learning to ensure i don't mess this up, but will take my time to make sure i understand everything stated in your explanation and then give it a crack over the wknd and let you know.

Related

Rooting non-standard Android

Model number: GM_DSTL1
Firmware version: 1.5
Baseband version: 20/05/09,st32,x2a.m1
Kernel version: 2.6.28-svn1368
Build number: CUPCAKE.eng.long.20090720.210535.r1368
Trying to figure out how this could be rooted because I can't seem to use traditional methods like downgrading and 1-click rooting.
If I understand correctly this is possible for me due to CVE-2009-2692
In an effort to try and cover my butt I have backed up all that "adb shell" permission would let me.
Zinx's "Recovery partition flasher for Android" has not been helpful.
Getting my device to use FastBoot seems to be my first step.
Constructive comments?
still no luck
Ruled out the telnetd hack, bummer:
I run telnetd in terminal and it gives me no errors but a port scan doesn't return anything besides port 110(pop3), 25(smtp), and 21(ftp) - none of which have proved useful thus far. Must have been patched with cupcake... or something I'm missing.
Also ran cat /proc/cpuinfo for fun
--------------------------------
Processor : XScale-V3 based processor rev 2 (v5l)
BogoMIPS : 103.58
Features : swp half thumb fastmult edsp iwmmxt
CPU implementer : 0x69
CPU architecture: 5TE
CPU variant : 0x0
CPU part : 0x689
CPU revision : 2
Hardware : yuhua X2_V4 on Marvell (Littleton)
Revision : 0004
Serial : 0000000000000000
-----------------------------------------------------
103.58 is weak sauce... but apparently that is the minimum for the Marvell PXA310 RISC Microprocessor
I wonder if anyone else on this board is bumpin the DSTL1? I may be the lone fish out here
Following this guide to get Fastboot aka Engineering Bootloader
I skipped flashing the radio because I figured it had to do with the OTA stuff which doesn't affect my model...
So I downloaded spl-signed.zip and renamed it to update.zip, placed it on my sdcard in the folder "update" (these instructions are specific to my model). In recovery mode I tried to update it but it FAIL.
update.log from failed update
Starting recovery on Thu Oct 8 01:22:51 2009
framebuffer: fd 4 (240 x 400)
I:text_cols 24 text_rows 22
E:Can't open /cache/recovery/command
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=CUPCAKE
ro.build.display.id=CUPCAKE.eng.long.20090710.190105.r1322
ro.build.version.incremental=eng.long.20090710.190105.r1322
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Fri Jul 10 19:15:42 CST 2009
ro.build.date.utc=1247224542
ro.build.type=user
ro.build.user=long
ro.build.host=long-desktop
ro.build.tags=ota-rel-keys,test-keys
ro.product.model=GM_DSTL1
ro.product.brand=generic
ro.product.name=gm_x2
ro.product.device=x2
ro.product.board=x2a_v4
ro.product.manufacturer=yh
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=
ro.build.product=x2
ro.build.description=gm_x2-user 1.5 CUPCAKE eng.long.20090710.190105.r1322 ota-rel-keys,test-keys
rild.libpath=/system/lib/libyh-ril.so
rild.libargs=-d /dev/ttyp1
persist.gsm.dual.mode.phone=1
persist.gsm.sim.active.phone=GSM1
sms.supports.national.lang=1
wifi.interface=eth0
ro.config.sm_notification_snd=notf_gm_02.ogg
ro.config.sm_notification_snd_2=notf_gm_02.ogg
ro.config.notification_sound=F1_New_SMS.ogg
ro.config.ringtone=GM_01.ogg
ro.config.ringtone_2=GM_01.ogg
ro.config.sync=yes
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=yuhua
ro.revision=4
init.svc.recovery=running
init.svc.adbd=running
init.svc.yuhua-board-init=stopped
ro.kernel.android.qemud=0
ro.radio.use-ppp=no
ro.com.google.locationfeatures=1
RecVer:Fri Jul 10 19:15:42 CST 2009
Recovery tools:
HOME: Sd-card update
CALL: Board test
BACK: Factory reset
POWER: Reboot system
I:Key 102 pressed, alt 0
Search /sdcard/update/*
I:Find file . in /sdcard/update/
I:Find file .. in /sdcard/update/
I:Find file update.log in /sdcard/update/
I:Find file update.zip in /sdcard/update/
Find update.zip, Home to update
I:Update package /sdcard/update/update.zip
Installing /sdcard/update/update.zip
Installation failed.
Another Fastboot attempt
http://android-dls.com/wiki/index.php?title=Engineering_Bootloader
Downloaded update.xxx, renamed it to update.zip, placed it on my sdcard in the folder "update" (these instructions are specific to my model). In recovery mode I tried to update it but it FAIL... again.
From the log files it seems this stock recovery system SUCKS...
Another FAIL
Revisiting http://forum.xda-developers.com/showthread.php?t=532719 from my earlier post (#3). Tried to do the Radio Update... Downloaded ota-radio-2_22_19_26I.zip and renamed it to update.zip... yada yada yada, you know the rest.
Visit "http://www.generalmobile.com/index.asp?action=Android_Phones/DSTL1_support", and you can find how the update system work(it is not a G1). Also take some time to see the install package and hack it.
1. Unzip the package.
unzip Android_20090826_r1502.zip
2. Copy some missed property app(http://www.sendspace.com/file/dii80c get from adp1.5) to /system/app/ after diff it with the ADP image.
3. zip the new package.
zip Android_20090826_r1502_hack.zip -ry system boot.img
4. update package and wait it bootup.
Very cool!
@wineleven
THANKS!
That was very cool! Finally some progress
So I was not too off from that path, I had already downloaded the update from General Mobile and had been inspecting the zip file they were trying to shove in my face as a quick fix to their buggy ROM. I was asking the support some very hard questions, which is probably why it has taken them more than their 48 hours to reply to me. (its been 5 days now)
General Mobile's update is Android_20090826_r1502.zip
containing the following particularly interesting (to me) files:
/system/build.prop
/system/system-update-post-script
/boot.img
/update-validate-script
Attempt 1
Here I tried to zip up their unmodified package with the suggested -ry arguments and hope that stock recovery takes it and runs with it.
FAIL
I reviewed wineleven's suggestions noticed he omitted the file update-validate-script
This was probably my problem
Attempt 2
Here I omitted update-validate-script
SUCCESS!
Attempt 3
Spirits high I go for the gusto:
I downloaded superuser.zip from this forum and embedded it in the location /system/app
Flash SUCCESS, functionality FAIL
I got too excited and put Superuser.apk and su both in the same directory... silly mistake
Attempt 4
This time I put Superuser.apk in /system/app and su in /system/bin
Flash SUCCESS, functionality FAIL
running su in terminal gave me "permission denied" with the following carriage return:
here1here2here3here4$
obviously I'm missing something here... but have made progress and feel more confident about this.
More attempts to come. Suggestions and advice is welcome!
Question to those knowledgeable
Why are certain files in the /system/bin included as "links" and not actual files? save space in zip?
Can boot.img be modified? Replaced with a better (more useful) one?
Any ideas on obtaining root?
Root idea and shortcommings
After reviewing http://android-dls.com/wiki/index.php?title=Magic_Root_Access
I may have bin (lol) too hasty with slapping su in /system/bin
But logic tells me it shouldn't matter... bin or xbin
And I feel like permissions are my real issue because my current su (residing in /system/bin)
command
ls -l /system/bin/su
returns
-rwxr-xr-x root shell 34612 2008-08-01 08:00 su
command
chmod 6755 /system/bin/su
returns
Unable to chmod su: Read-only file system
^--- in hindsight I see that as a DUH, because I can't remount the /system partition as read/write
More questions
I have always understood chmod to use three digits, why are there four digits now?
Also, what is 's' in terms of permission... is that to see? like hidden files?
Main task accomplished!
After reviewing Cyanogen's experimental ROM I can see where and how he sets permission for su
Trying to emulate his method for myself has been plenty of trial and error, but I have finally done it.
system-update-post-script was the key file that set permissions.
One MUST keep the carriage return at the end of the file - I have a neatfreak habit of cleaning them up.
Also, using the su and Superuser.apk in Cyanogen's latest build kept restarting my device, must be because his kernel is newer than mine.
RapidShare is hosting for 90 days Android_20090826_r1502_rooted.zip - NEW BUILD HERE
MD5: F1DE9A270CDDF01ADEE708B6660B7AFA
PM me if not avail.
NOTE:
I am not responsible for your new paper-weight mode...
This has worked fine on my device, but I guarantee nothing for yours...
My device is General Mobile's DSTL1 - details in post #1
What you get:
Root access via su and Superuser.apk - procured from XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=211569&d=1249225060
To use:
Your sdcard must contain "update" folder, this is where you will place the zip file after you have renamed it to "update.zip"
Happy ROOT
------------------------------------------
My next task will be to get Cyanogen's ROM to work on my device... seeing as how Cyanogen codes for the popular HTC models, I am left out - and I don't like being left out.
Side quests will be to play with the boot.img, flash the SPL, and maybe get a nice recovery
Particularly I would love to try out nandroid.
@wineleven THANK YOU for the nudge in the right direction!
Thank you:
Google for the open source Android OS - without the free SDK wouldn't have been possible for me
General Mobile for the nifty device
Remote Exploit for BackTrack3/4 - I did most of my work on this Live CD distro
XDA-Developers Forum for info and resources: superuser files and Cyanogen's ROM for info
congratulation to you.
Some notice:
As this devices is deeply modified based on Android open source and hardware different to G1. So you can not rebuild any system framework APK from open source unless you can get the DSTL1 source code. As i now, one thing we can do is to add some external APK file (API compatible to device, now SDK 1.5) to system. Like the Superuser.apk you do.
crzyruski said:
After reviewing Cyanogen's experimental ROM I can see where and how he sets permission for su
Trying to emulate his method for myself has been plenty of trial and error, but I have finally done it.
system-update-post-script was the key file that set permissions.
One MUST keep the carriage return at the end of the file - I have a neatfreak habit of cleaning them up.
Also, using the su and Superuser.apk in Cyanogen's latest build kept restarting my device, must be because his kernel is newer than mine.
RapidShare is hosting for 90 days Android_20090826_r1502_rooted.zip
MD5: C3C13F6DC75BF6F86E5C9E41D7FB4C59
PM me if not avail.
NOTE:
I am not responsible for your new paper-weight mode...
This has worked fine on my device, but I guarantee nothing for yours...
My device is General Mobile's DSTL1 - details in post #1
What you get:
Root access via su and Superuser.apk - procured from XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=211569&d=1249225060
To use:
Your sdcard must contain "update" folder, this is where you will place the zip file after you have renamed it to "update.zip"
Happy ROOT
------------------------------------------
My next task will be to get Cyanogen's ROM to work on my device... seeing as how Cyanogen codes for the popular HTC models, I am left out - and I don't like being left out.
Side quests will be to play with the boot.img, flash the SPL, and maybe get a nice recovery
Particularly I would love to try out nandroid.
Click to expand...
Click to collapse
Hi crzyruski
I'm a new android and DSTL1 user and this information is cool
it's easy to do for a newbie as I?
What do you mean easy? What would you like to do?
I took General Mobile's only update: http://www.generalmobile.com/index.asp?action=Android_Phones/DSTL1_support and gave it ROOT. If this is all you want to do, I have compiled the package already for you in my post above. If you want to do it manually then read the whole thread to see how I did it.
If you want to use my compiled package, it is easy.
Then again, I don't know if anyone else has tried it. It worked for me.
You are only the second individual to inquire about it, I am not sure if the other fellow had any luck - he hasn't replied to me.
Hope this helps.
Keep in touch!
I only have 3 days with Android, but I think that I want to get root access. The only thing I have to do is a second "update" with your package, isn't it?
I'm going to look for a backup system program first...
Can I have problems to update from General Mobile support web in a future? (i.e Android 2.0)
It does not need to be second. That is your choice. You can use it in any order. This is not a patch so order is no relevant.
My package is basically the original General Mobile update + 2 files.
These two files are su and Superuser.apk - nothing special (except that you will obtain root access on demand)
I currently only utilize root access to run Advanced Task Manager.
And in the future I want to overclock because I feel the DSTL1 is greatly underclocked though it should max out at ~600Mhz.
Good luck with a backup program as I have not found any free versions and NAndroid is ideal but not not yet possible as you have to flash the SPL and I am not aware how to do this for DSTL1 though I am sure it is possible.
Please let me know what you end up using to backup, if you do.
I would like to note that I am not all knowing and if something goes wrong I am sorry, but can't take responsibility.
There is no reason you should not be able to update from my package to another like: original 1.5 or new 1.6 or future 2.0 (whenever it comes out).
Hopefully when those come out I will be able to modify them similarly and make them available.
But you mentioned you will only have the device for 3 days, do you suppose 2.0 will be released within this time?
-crzyruski
crzyruski said:
Please let me know what you end up using to backup, if you do.
But you mentioned you will only have the device for 3 days, do you suppose 2.0 will be released within this time?
-crzyruski
Click to expand...
Click to collapse
I'm going to try with My Backup Pro
And about 2.0 this all I know...
http://www.boygeniusreport.com/2009/10/16/android-2-0-screenshot-walkthrough/
Good luck to you.
I think I may begin working on some more DSTL1 hacks.
Please keep me updated with your progress
I only have to do ALL this process with your zip, isn't it?
How to Install the Product Update:
Create a folder at the top-level of your memory card called 'update' , and copy file '*.zip' into your phone's memory card.
Make sure your phone is off, and press the Home key together with the Power & End key to enter the recovery mode, do the operations following the UI indication:
1- Press the Home key to search the zip file from your memory card, and press the Home key again to update the software.
2- Press the Call key to do board test.
3- Press the Back key to restore the factory settings.
4- Press the Power & End key to reboot your phone after update finishes.
Click to expand...
Click to collapse
Looks correct to me. Tell me how it works out.
crzyruski said:
Looks correct to me. Tell me how it works out.
Click to expand...
Click to collapse
I've done it! and all seems to be ok...
Thank you crzyruski.
I'll be waitng for your future DSTL1 hacks.

[Q] Reinstall HTC Sense stock apps

Hello,
I've removed the Gallery app (com.htc.album.apk) using the Titanium backup 'cause I wanted to replace it with another one. I do have the backup, but when I do a restore it just does the circle with restore in progress forever. Is there a way to restore the Gallery?
The only reason why I want to restore is that when I use the HTC Sense apps which cooperate with Gallery (for example the Camera), when I want to see the photos the apps crash - I thought it would be possible to choose another app like QuickPic for this photo browsing, but apparently not. Therefore I would be very grateful if somebody knows how to restore the app.
The phone has s-off and is rooted.
Thank you very much.
SOLUTION
OK, I've found a way how to do it, so just want to share with others, in case anybody gets into the same kinda trouble as I did ;-)
The steps:
1. Download the zipped RUU of the stock ROM and extract the APK and ODEX files of the app you want to restore (HTCAlbum.apk and HTCAlbum.odex in my case)
2. Using Root Explorer (or some other tool that can write into /system/app) copy the apk and odex files into it.
3. Again using the same tool set the permissions of the 2 files to rw-r--r-- and set the owner and group to 0 - root (both user and group)
4. What I did now was try to Install the apk in the /system/app, but it failed, so probably this step is not needed - just put it here in order to reproduce exactly all steps.
5. Reboot the phone -> after the reboot the app should appear in the app drawer and all HTC stock apps now work with using the Gallery.
Please if you try this method, write down your comment, whether you succeeded or not.
Cheers and good luck...
Didn't work for me. Tried apk and odex gallery from newest ruu.
I also accidentally removed the Gallery (com.htc.album.apk), and I've found a way out to do it.
First to do :
> Install the latest Java JDK.
> Install HTC Sync & drivers.
> Install the Android SDK.
> Open SDK Manager after installing the Android SDK successfully.
> Install every 'Available Packages' in SDK Manager.
> Edit 'Path' in Environmental Variables and put this behind the line
Code:
;C:\android-sdk-windows\platform-tools
> Enable USB Debugging on your HTC.
And after all this above..
1 -Connect your Wildfire to the PC.
2 -Reboot into CWM Recovery.
3 -Go to Mounts and Storage.
4 -Select Mount /system.
Then use adb :
Oh and make sure the HTCAlbum.apk is in the same map as adb.exe
Code:
adb push HTCAlbum.apk /system/app
-MAKE SURE YOUR DEVICE IS S-OFF- Otherwise it won't work.
Solar_ said:
MAKE SURE YOUR DEVICE IS S-OFF- Otherwise it won't work.
Click to expand...
Click to collapse
This doesn't need S-OFF. Just a Custom Recovery like Clockworkmod.
rocky7x said:
OK, I've found a way how to do it, so just want to share with others, in case anybody gets into the same kinda trouble as I did
The steps:
1. Download the zipped RUU of the stock ROM and extract the APK and ODEX files of the app you want to restore (HTCAlbum.apk and HTCAlbum.odex in my case)
2. Using Root Explorer (or some other tool that can write into /system/app) copy the apk and odex files into it.
3. Again using the same tool set the permissions of the 2 files to rw-r--r-- and set the owner and group to 0 - root (both user and group)
4. What I did now was try to Install the apk in the /system/app, but it failed, so probably this step is not needed - just put it here in order to reproduce exactly all steps.
5. Reboot the phone -> after the reboot the app should appear in the app drawer and all HTC stock apps now work with using the Gallery.
Please if you try this method, write down your comment, whether you succeeded or not.
Cheers and good luck...
Click to expand...
Click to collapse
It worked! Thank you:good:

[N2E][1.1] TouchNooter 2.1.31

This Nooter is officially supported by The Nooter Project for Nook Simple Touch​
I'm not adding certain things because I don't believe they should be available as part of a rooting kit designed to give users more control of their devices. Things such as additional readers or CPU Clocks are up to the user to install themselves and needlessly putting them in Nooter creates app bloat that a user may or may not want. You can always drop Apps you want into \nooter\data\app and they will install automatically when you root the device. This Nooter is designed with the sole purpose of opening up the possibilities of the device by giving users Root, Google Apps, and other Apps which make the device more usable as an android device than just an e-reader.
What it does:
Enables ADB via uRamdisk
Installs adbWireless
Installs Button Savior
Installs NookTouch Tools
Installs Amazon Marketplace
Installs su and Superuser.apk
Installs ADW + E-ink Friendly Theme
Installs Busybox & Busybox Installer/Uninstaller
Installs Gapps (Gmail, Market, Youtube, Others)
Installs NookColor Tools (To Enable Non-Market Installs)
System Files that get Modified:
/system/build.prop - Enabling Google Check In
packages.xml - Allows Gapps to install properly.
framework.jar - Should allow a proper Android ID to generate.
Changes:
January 26, 2012 -
Tested Fix: ADW not installing - Caused by spaces in ADW's Filename in 2.1.26
Added: Amazon Marketplace, Opera Mini
January 26, 2012 -
Added: adbWireless, SuperManager (Root File Manager, APK Manager, other useful tools), Busybox Installer/Uninstaller
Untested Fix: Market 1 Day wait
Updated: busybox, ButtonSavior.apk, su & SuperUser.apk
November 20, 2011 -
Removed: GoLauncher, LiveWallPaper Picker, maybe some other stuff.
Added: New Market, ADW with Black Minimalist Theme, NookTouchTools.
New: Rooting Image
June 24, 2011 -
Removed: Multitouch Permission
Added: Modified framework.jar
June 22, 2011 - Fixed: Script not running at boot.
June 20, 2011 - Initial Release
Before you begin:
You must already have a registered Nook Simple Touch
You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
You must either have dd (Linux) or WinImage (Windows) software.
You must have an external microSDCard reader or this will not work. Using the Nook Simple Touch can result in it becoming unusable (bricked).
You must have enough intelligence to follow instructions.
Let's get started:
Download TouchNooter from here: touchnooter-2-1-31.zip - Uploaded
Linux: Unzip and use dd if=touchnooter-xx-xx-xx.img of=/dev/sdcard (where xx-xx-xx is the version number)
Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
Windows Alternative: https://launchpad.net/win32-image-writer/+download
If you wish to use Underclocking follow these steps
Download Underclock.zip from uploaded attachments
Unzip it and place the data folder in /nooter/
Check that the com.antutu.CpuMasterFree folder is in the /nooter/data/data folder
Check that com.antutu.CpuMasterFree.apk is in /nooter/data/app
Power off your Nook Simple Touch.
Insert TouchNooter SDcard into your Nook Simple Touch.
Power on your Nook Simple Touch.
You should see the new TouchNooter boot screen, follow all instructions.
That was the hard part, now to the simple stuff.
Upon boot unlock your screen.
At the Android Welcome Screen skip Sign In.
Enable Location Services when given the option.
Connect to Wifi and launch Youtube from ADW's App Drawer (Or the App Drawer of your Choice).
Click the Menu button (The right one in the middle of the status bar).
Select "My Channel" and Login using your Gmail Account.
Exit Youtube and Launch Gmail from ADW's App Drawer.
Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
At this time Market fails and you must wait up to a day. Just check it every so often. Future updates should fix this.
Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
Enable Non-Market Installs by running the NookColor Tools App.
If your Youtube fails to launch Uninstall and Reinstall Youtube from /data/app
Go to Settings > Device Info > SdCard > UnMount > Format
Thanks To:
XorZone - NookTouchTools - http://forum.xda-developers.com/showthread.php?t=1289894 - Sorry, been busy, credit where credits due.
Torimu.Joji - For the configurations for CPU Master Free that allows simple automated underclocking
xevious - Kick starting my brain to get this update out
mali100 - modified framework.jar for 1.1
eded333 - Repackaged Gapps, the idea that may fix 1 Day Market Issue.
ros87 - uRamdisk
nemith - helping me figure out getting it to run at boot.
JesusFreke - For getting root.
MrMuffin - For the original Market Hack that we're using.
If I'm using an app in TouchNooter and you would like Credit/Thanks, or to have it removed, please PM me, otherwise I might not see your requests
Currently Working On: School
What's great info but are you going to still develop it to make gapps working?
domi.nos said:
What's great info but are you going to still develop it to make gapps working?
Click to expand...
Click to collapse
If I can find a way to do it without killing the device I will.
Works great
Hi
It works great, thanks.
Beside the full GApps do you know if there's a way today to get the Market working on a firmware 1.1 with TouchNooter 1.11.11 ?
ZeAuReLiEn said:
Hi
It works great, thanks.
Beside the full GApps do you know if there's a way today to get the Market working on a firmware 1.1 with TouchNooter 1.11.11 ?
Click to expand...
Click to collapse
Go through all the steps manually with something like noogie. The reason TouchNooter can't do it is because to get the script to run requires the the system to boot, replacing the files while the system is active will cause the system to crash when you go to reboot it to complete the steps for Market. Because of this to install Gapps you have to use a method that doesn't require the system to be active like Noogie.
Another method which would allow us to add Gapps, is if someone completed a version of CWM for Nook Touch.
Dear Gabriel,
somehow i gained working market on my Nook with 1.1. I used the older touchnooter with subplanted framework.jar and uRamdisk (wifi one). Then i've done all steps as in guide. Market however didn't saw any applications. I removed youtube app, and it started working! Then updated market to that one http://forum.xda-developers.com/showpost.php?p=15084704&postcount=51 using adb.
"adb install -r Vending.apk"
And right now i'm cool.
I've done the root for 1.1 manually, and it was a bit of a pain, so everybody should be thanking Gabrial here for streamlining the process a bit and not having to hunt down all the elements necessary to make a rooted Nook useful. (It's not actually difficult, but nobody has centralized *all* of the info even if much of it can be found in the Knowledge Base thread, including e.g. that you need Busybox even for something as simple as the cp command.)
domi.nos-
Is the -r switch for reinstallations any different than removing the old Vending.apk and then installing the new one? I still have not got market 100%; search won't work. Is it working for you? It's not really that big a deal because I only need a few apps but all the same it'd be nice...
Is it necessary to revert to original Nook ROM (the backup I've made before rooting the Nook Touch)?
No as a see it does not search. ;/ But in my opinion it is more important to find out why did my nook (any everyone elses' as i presume) disappear from pc market website.
But as i remember in the previous 1.01 software market couldn't do true way of searching, it was only showing most used searches.
This may sound dump, but I don't have a lot of knowledge with android yet.
This root is without any google apps, Can I download the google apps apks and install them on my device?
Dark_hawk,
From what I read from Gabrial, the only way to install Gapps if when nook is booting, and there is no safe way as from now. I'm still checking, though.
My experience so far? 1.1, touchnootered with 1.11.11, backup recovered with titanium backup pro (which worked quite well, I might add), and besides market, everything else is working?
I'm looking for info on how to install Gapps, or market at least, but no luck yet. Gabrial mentioned something about using noogie, but I don't even know where to look for Gapps version that may work on Nook STR>
(Hard method)
First, install this:
http://forum.xda-developers.com/showpost.php?p=19201466&postcount=352
Then try this, it should work:
http://nookdevs.com/NookColor:Manual_market_enable
and if search dosn't work, this:
http://forum.xda-developers.com/showpost.php?p=15084704&postcount=51
(Easy method)
Follow this guide:
http://www.mobileread.com/forums/showthread.php?t=156539
Read post 7, it explains how to do it easily.
How can I install Side-loaded APK?
I think, its dumb NB question... but I can not figure out, how I can install side-loaded APKs... I copied APKs to Nook but just not find a way to install them on nook... Is this something simple ? or not that simple as I think?
WORKS WITH 1.1.0 and gapps!
eded333 said:
(Hard method)
First, install this:
http://forum.xda-developers.com/showpost.php?p=19201466&postcount=352
Then try this, it should work:
http://nookdevs.com/NookColor:Manual_market_enable
and if search dosn't work, this:
http://forum.xda-developers.com/showpost.php?p=15084704&postcount=51
(Easy method)
Follow this guide:
http://www.mobileread.com/forums/showthread.php?t=156539
Read post 7, it explains how to do it easily.
Click to expand...
Click to collapse
The Easy method above worked perfectly with my new nook running 1.1.0.
all I would add is that I got search working in the market by toggling "allow non market apps" in Nook Tools app, then installing the vending.apk file from my sd card with ES file explorer as an application. just select yes when it asks you to replace system app.
To get ES file explorer to begin with, I scrolled thru the whole list of top free apps, which took awhile.
Apps that I was able to install and work:
ES file explorer, Facebook, Google reader, Google voice, XDA app, Opera mobile, Opera mini, Google+, Quickpic and Paint easy.
Thanks to everyone for all the hard work that made it easy for a N00b like me to root and customize my NST!
Orz-Orz said:
I think, its dumb NB question... but I can not figure out, how I can install side-loaded APKs... I copied APKs to Nook but just not find a way to install them on nook... Is this something simple ? or not that simple as I think?
Click to expand...
Click to collapse
+1 It seems ES File Explorer is not installed!
Well, I followed the recipe:
- Restored
- Resetted
- Updated to 1.1.0
- Touchnootered with 1.6.24 and framework and uramdisk for 1.1.0
- Three locked boots (at least 5 minutes each)
- When tried without SD, got back to regular nook!!!!
I did register, though, after reset. Would that make a difference???
Gotta try.
I've tried to install ESFile Explorer through browser but with no results. Besides, browser crashes when, for instance, I try to write something on google.
One way to side-load apk's
Orz-Orz said:
I think, its dumb NB question... but I can not figure out, how I can install side-loaded APKs... I copied APKs to Nook but just not find a way to install them on nook... Is this something simple ? or not that simple as I think?
Click to expand...
Click to collapse
The way I did it was to copy apk's to my SD card, then download a file explorer/manager app from the market (my personal favorite is ES file explorer), which allows you to view the contents of your SD card, and select apk's to install.
---------- Post added at 07:48 PM ---------- Previous post was at 07:32 PM ----------
apeine said:
Well, I followed the recipe:
- Restored
- Resetted
- Updated to 1.1.0
- Touchnootered with 1.6.24 and framework and uramdisk for 1.1.0
- Three locked boots (at least 5 minutes each)
- When tried without SD, got back to regular nook!!!!
I did register, though, after reset. Would that make a difference???
Gotta try.
Click to expand...
Click to collapse
It sounds like you did it the exact same way I did. Just to make sure did you delete the old Framework and uramdisk files, then copy/rename their replacements to match the original files? i.e. framework.jar and uRamdisk
---------- Post added at 07:51 PM ---------- Previous post was at 07:48 PM ----------
myself11 said:
I've tried to install ESFile Explorer through browser but with no results. Besides, browser crashes when, for instance, I try to write something on google.
Click to expand...
Click to collapse
I think the easiest way to get it would be from the market. if you haven't updated the vending.apk file to fix searching the market then you would have to use the category buttons at the top of the market to browse for it and install it.
Yes, I deleted the old version, installed uRamdisk usb 1.1 and framework 1.1.jar and renamed them properly (same name as erased files).
Did it all over again, no registering, and same result: after running for 3 times, went back to regular nook STR!!!
Forget about the restart the process three times, do it like this:
1) Use nookRestore to restore /system.
2) Erase and Deregistered to wipe /data
(If it dosnt let you, force it shutting down your nook, then starting it up, and when the screen flickers press right and left bottom buttons, hold for 5+ seconds).
3) Register, or not, as you preffer.
4) Apply 1.1 firmware update.
5) Open the TouchNooter 1.6.24 image and inside the nooter folder, search and substitude the uRamdisk for this one http://www.multiupload.com/CJ981FWPJG
and framework.jar for this one http://forum.xda-developers.com/showpost.php?p=19201466&postcount=352.
6) Use the new TouchNooter 1.6.24 to root your device. Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=1132693
If it dosnt work, try again until it works.
7) Continue with registering: Youtube (401 error) --> GMail --> Market.
8) Download adb, and unzip it:
http://forum.xda-developers.com/showthread.php?t=1124160&page=6
download this vending apk:
http://forum.xda-developers.com/showthread.php?t=1124160&page=6
and sqlite3:
http://www.sqlite.org/sqlite-shell-win32-x86-3070900.zip
copy the apk and sqlite3 tothefolderyouunzippedadb/platform-tools , open cmd and then:
cd tothefolderyouunzippedadb/platform-tools
adb connect yournooktouchip
Now we are going to enable non market apps use my method, or what madmachinist said:
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db "update secure set value=1 where name='install_non_market_apps';"
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb reboot
now when NST reboots:
cd tothefolderyouunzippedadb/platform-tools
adb connect yournooktouchip
adb install Vending.apk
adb reboot
You are done, everything should work now.

[Q] Sky go - pls help

Hi,
I'm hoping somebody can simplify what it is I need to do to get sky go working on my desire.
I've have been reading through the sky go thread and spreadsheet etc but I'm still not clear if it is at is possible to get this app working on my current configuration. I have worked out that I need version 1.5 of gumbalds apk and voodoo ota to hide root but I'm not clear on the kernal bit (if/what I need to do). Hopefully somebody can simplify the steps needed?
My current set up is
Software : Cool Droid v3 gsm
Android version: 2.3.4
Kernal: 2.6.35.14-gingercakes-0.9-avs
Many thanks
ok thanks for your help everybody. Here is what I did to get skygo working on my desire. I think the key is to have a ROM based on an official HTC release and then update the boot.img as per the post at the top of this page
http://forum.xda-developers.com/show...06967&page=174
So the steps I followed:-
1. Make sure my desire is flashed with a Rom based on an official HTC release. I used Cool Droid v3 gsm but it should work with others
2. I then made a nandroid backup of my Rom
3. As per the above link I then downloaded, installed and research how to use the kitchen app.
4. I then connected my phone to pc and copied my system and boot.img files from my clockworkmod backup folder to the relevant kitchen folder on my pc.
5. Using the kitchen app I then made a working copy of my Rom.(this took a while to process) 6. Then from the kitchen advanced menu I unpacked my boot.img this then create a new temporaryfolder on my pc with all the files
7. In Windows explorer I then found the default.prop file and opened it in notepad
8. I updated a line in this file from ro.secure=0 to ro.secure=1 and saved.
9. I went back into the kitchen app and repacked my boot image.
10. In kitchen I then created a rom from the working folder (im was going to flash the Rom but got inpatient)
11. Using explorer I then located the boot.img and copied just this file back to my clockwork backup folder on my phone
12. I then did a restore from recovery in my phone. I got a warning at this point (something about md5um not matching) and I continued with restore.
13. I then hid root using voodoo ota root keeper and checked skygo and whoop whoop all was good
I'm not sure this will work for everyone but it worked for me and I made sure I created copies of my backup files just in case it didn't work...
If anybody requires any further clarity please shout.

TrevStuff - Apps and Stuff to help with Alliance and Other Roms

This is a collection of tools and apps that I have produced to try to help users of Alliance ROM and various Kernels. Some of these apps may work for other ROMs or Kernels but I must stress that these will not have been tested.
Contents
My Apps - Apps or Flashable Zips that I have produced to address specific needs.
Guides - Guides I have produced to take you through fixes or modifications.
Other Stuff - Useful bits from others.
Bespoke Stuff - Custom stuff that is not Rom or Kernel specific.
Rom Share - Links to Mirrors I have set up for Roms I use with slow download speeds from their original host.
Other useful Links:
Alliance Thread
Alliance OTA Submission Thread
Rom Share - Mirror of ROMs and Kernels I use where the main link is very slow.
Adblock Hub - Some adblockers saved from the Play Store cull.
Apps
My Apps - These are Apps or Flashable Zips that I have created for Alliance Rom or a specific Kernel
SymlinkSD - App that runs on boot and Symliks the External SDCard as /mnt/sdcard - Only needed for Kernels that display this behaviour.
Reset Fuel Gauge - Function to rectify weird battery readings, code taken from Dori's kernel and turned into an app.
Tweaker - Allows you to toggle the following options on your phone if the installed Apps support it:
Camera Silent Menu Item
Disable auto convert SMS to MMS
Change the maximum number of contacts that can be joined to another contact
TogMods - Auto enables any Toggle Modifications you have made on reboot instead of having to make a change to enable them.
AccuWeather Widget - Flashable Zip for either Normal (with Background) or Transparent
LS Fix - Repairs Issue on some LS8 ROMs where the Lockscreen does not come up and a long press of the power button restarts the phone.
Stock Messaging no Convert and Sent Time - Stock Messaging app with the Convert to MMS function disabled and displayed times reflect the sent time not received time.
AOSP Themed Messaging no Convert and Sent Time - AOSP Themed Messaging app with the Convert to MMS function disabled and displayed times reflect the sent time not received time.
SilentCam - Camera app with Silent Option
CPU Idle - Allows user to specify the Scheduler used for CPU Idle for screen on and off as long as the Kernel supports it.
Crash Logger - Captures LastKmsg file automatically after an unexpected reboot. File is saved to SD and copied to Clipboard. Kernel must not have disabled Android Logging.
Boot Wifi - Automatically enables WiFi on Boot for ROMs or Kernels that deactivate WiFi on startup.
Auto Wifi - Automatically enables WiFi on Boot for ROMs or Kernels that deactivate WiFi on startup and renenables WiFi if it is enabled by the user and then immediately deactivated by the Kernel or Rom.
Cache Cleaner - Runs the Cache Clean feature from Dorimanx kernel as a stand alone application. Just run and that's it. It will show the Start Free Ram, End Free Ram and then close itself and remove from memory.
Rom Select - App for Dual Boot users to allow them to change Roms without waiting for STweaks to load first. Tested with Dorimanx, should work with Siyah as well.
The following Apps may no longer be required as they should be fixed.
Dori CamFix - Fixes problems with some CM and AOKP ROMS where the camera force closes when using Dorimanx Kernel.
Fake Notify - Fixes issue for users using AllianceROM where the Notification bar does not show up on boot.
Fake Notify Plus - Fixes issue for users using AllianceROM where the Notification bar does not show up on boot and also sometimes disappears during normal use at Random.
Crackle Stop - Automates TRB's method of fixing the problem of a crackling sound being produced along with notifications. Once installed run and you will need to grant SU access. You will then be presented with a Menu for your Normal 'Idle' mode, this should be the same as the awake idle mode set in STweaks, next you will be asked for an Alt Idle mode, this can be anything, just not the same as your normal mode.
Once set you will need to reboot for the fix to activate.
Once rebooted the app does what it needs to do over a 20 second period (not 20 seconds after the phone has booted as the app will probably be the last thing loaded - so to be safe I'd give it 2 or 3 minutes). You then need to let your phone get into Deep Sleep so leave it for a bit and then after that all should be OK.
Note this is not a one off fix, this process will run on each boot but you do not need to rerun the App unless you want to change the Normal Idle mode.
Guides
My Guides - These are useful Guides I have made to help with various ROM and Kernel Issues.
Swype LSx Fix - Problem where the Custom Dictionary stops working and saving new words when using Swype on LSx ROMS.
IMEI Recovery - Step by step guide on how to backup your IMEI and then how to recover should you need to. This an essential guide, as should you not be able to recover your IMEI your phone will become a very expensive Paper Weight.
Change System DPI Settings - Step by step settings to change the system DPI.
YouTube fix - How to fix the error signing in problem in YouTube.
Other Stuff - Useful bits from others
The Red Blur's Cave - The Red Blur's page of helpful hints and knowledge. Don't bother reporting a problem until you have checked here, this guy is the best resource for all things Galaxy S 2!
Dorimanx Kernel Discussion Thread - Discussion Thread for all things Dori, especially things that should not be posted in the Dev Thread.
HawkerPaul's ROM and Kernel Wipe / Nuke scripts - These scripts should be used before flashing new ROMs or Kernels to clear up all of the left behind bits from your old installation.
Stock Video Fix - Flashable fix for issues with the Stock Video Player Force Closing when opened from the App Drawer, usually only present with Dori and Siyah Kernels. Thanks TRB.
Auto Call Record Mod and Disable increasing Volume Mod - Mods for LSx based ROMs to enable Automatic Call Recording and disable Increasing Ringtone volume.
LSx Dual Boot Mod - Manual Mod to allow Dual Booting of Roms when one of them is LSx
Ficeto's Kernel - Flashable Zip of Alliance 6 and 7 stock kernel.
AC!D Audio Installer - For Alliance Rom
Instructions:
Download and flash through Recovery.
After flash Wipe Dalvik Cache and Fix Permissions
Once booted enter the following into a Terminal Prompt to test install:
su
mount -o rw,remount /system
aaengine
You shouldn't need to run the above command, the install should do it but just to be sure
Reserved 1
Alliance Rom FAQ
How do I install 7.02?
You need to uninstall the Rom Customiser that comes with the Rom then install the new one from play store (https://play.google.com/store/apps/details?id=com.ficeto.alliancemanager) once installed go into Rom Customiser and then OTA and select the updates.
OTA does not mean Samsung or System OTA.
How do I install 7.3? I can't find it in OTA.
7.3 is a full Rom and not an update. As such you need to download the full Rom zip from the OP on the Alliance Thread. Once downloaded flash it through Rom Customiser.
How do I flash the Stock Theme for 7.3?
During installation uncheck the box next to "Alliance Theme".
What can be installed through Rom Customiser?
Anything can be flashed through Rom Customiser as long as it is a Flashable zip, an Odin Tar file or an OTA download.
I have Downloaded a mod or update from OTA which I cannot flash through recovery. What am I doing wrong?
You need to flash these files through Rom Customiser which will then automate recovery. You cannot flash these independently.
What is the default blue colour used in the Rom?
Uncheck the Alpha box Colour Hex code #33b5e5
How can I get the Dandelion Lock Screen Wallpaper back?
Download it from here.
Bespoke stuff
These are bits that have been requested by others for a specific requirement not Rom or Kernel specific.
MTU 1300 (tun0) - App to set the MTU value to 1300 for a VPN connection using tun0.
Re: TrevStuff - Apps and Stuff to help with Alliance Rom
Glad to see it finally on xda :thumbup:
SIGNATURE
PHONE : SGSII
Sent via: Tapatalk
Main ROM: AllianceROM v7.01 LSD
KERNEL : PhilZ Touch LSD 4.87 Fixed init version
(DEFAULT PROFILE AND SETTINGS )
MODEM : LS8
BATTERY : Stock 1650mAh
EXTERNAL Sdcard : Samsung Class 10 32gb
LAUNCHER : Apex Pro
Root Manager : SuperSU 1.04
THE CAVE = My Guides list to install NeatRom and other ROMS and kernels on LSJ and LS8 + tools to have a bug free rom and kernel + how to back up and RESTORE ROM OM FULLY = http://forum.xda-developers.com/showthread.php?p=35923600
1.Current list of kernels on LSJ and pros and cons
http://forum.xda-developers.com/showthread.php?p=36698607
2.Rom Nuke / Wipe scripts
http://forum.xda-developers.com/showthread.php?p=36742265
3. GS2KERNELWIPE script
http://forum.xda-developers.com/showthread.php?p=36742198
4.Fast Dormancy :
http://forum.xda-developers.com/showthread.php?p=36396636
5. How to install full wipe with rom nuke on LSJ
http://forum.xda-developers.com/showthread.php?p=36655790
Changing the DPI
Change the Entire System DPI setting.
1. Open Root Explorer
2. Navigate to /System folder
3. Open the build.prop file
4. Scroll down to the 'Additional_build_properties' you are looking for the line
"ro.sf.lcd_density = 240"
The default value for the LCD density is 240, the lower the number the more on
the screen. 200 is a good value to start with.
Save the change.
5. Reboot phone for the change to become effective.
Re: TrevStuff - Apps and Stuff to help with Alliance Rom
trevfee said:
Bespoke stuff
These are bits that have been requested by others for a specific requirement not Rom or Kernel specific.
MTU 1300 (tun0) - App to set the MTU value to 1300 for a VPN connection using tun0.
Click to expand...
Click to collapse
Thanks you so much sir trev for accommodating my request. I will test and if successful I will refer this to my colleagues.
Sent from my GT-N7100 using Tapatalk 2
Re: TrevStuff - Apps and Stuff to help with Alliance Rom
nogo8888 said:
Thanks you so much sir trev for accommodating my request. I will test and if successful I will refer this to my colleagues.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Initial report: just working on note2.
Thank you so much sir.
Without this mod, i cannot access our internal website.
Sir can you post this playstore?
Sent from my GT-N7100 using Tapatalk 2
android ipsec vpn mtu mod
trevfee said:
Bespoke stuff
These are bits that have been requested by others for a specific requirement not Rom or Kernel specific.
MTU 1300 (tun0) - App to set the MTU value to 1300 for a VPN connection using tun0.
Click to expand...
Click to collapse
Since I requested this tweak, I would give a simple explanation on what it does and how to use it.
When your connecting to a ipsec vpn using wifi and having trouble browsing to your internal websites eventhough your connected to it. You can ping your internal network but the trouble is no browsing. The solutions are:
1. Tell your System Administrator to change the ip tcp adjust-mss to a lower value, in my case I used 1000 using 1841 cisco router. This prevents the packet from fragmentation. Packets when fragmented were dropped thus resulting to no browsing. If the Sys Ad refuses to do so because this may cause some issues to Windows users (browsing may slow a little bit), your best solution is to install this tweak.
2. This MTU mod sets the MTU value of your payload to 1300 via tunnel interface of your android device this avoiding packet fragmentation resulting to packet being allowed to pass through the tunnel interface going to ipsec vpn router.
How to use it:
1. Download the vpnc widget from playstore. https://play.google.com/store/apps/details?id=com.gmail.mjm4456.vpncwidget&hl=en
Configure your credentials. Then connect.
2. Once the vpnc widget has been connected open this app. Then you should have browsed your internal network.
Note: This tweak is needed only for wifi connections. If your using carrier data, then this is not needed anymore.
Please give thanks to the creator of this app.
I just gave him the code and he did all the stuff in making this app looks nice and easy to use.
Big credit to OP, trevfee and thanks to my neatrom family (Many40, Mr.Greg, ESD and others who helped me finding the code)
Re: TrevStuff - Apps and Stuff to help with Alliance Rom
nogo8888 said:
Initial report: just working on note2.
Thank you so much sir.
Without this mod, i cannot access our internal website.
Sir can you post this playstore?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Glad it's working for you and thaks for the feedback and explanation for others.
As for Play Store I have yet to purchase a dev account to allow me to upload as I really only make things for people who know how to install from anywhere. Please feel free to trek people to download from this page, I won't be removing the app.
Phone Details and My Apps:
Phone: Samsung Galaxy SII i9100
ROM: AllianceROM i9100 JB v7 beta LSD
Kernel: Jeboo but usually Dorimanx
TrevStuff - My Apps and useful links.
If I answer your question by asking you to search or look somewhere else I'm not being rude. Just encouraging you to use XDA correctly.
Have you backed up your /efs folder? See here.
If I help you, please give me thanks.
Rom Share
Alliance Rom
Version 6.00 MD5 ad9ef7e3f95b746de4bbc938ebf89a9a
Version 6.10 MD5 eab8fc5f40e47bc1a1a2d06b3d9253e1
Version 7.00 MD5 ae964c3a07aeb460c8d21fe3c0f087e9
Version 7.01 MD5 d761e4625b8406eee3b97fd5eec6ea87
IMEI Recovery
IMPORTANT
FOR THIS PROCESS TO WORK YOU MUST HAVE A GOOD COPY OF YOUR /efs DIRECTORY TAKEN PRIOR TO THE PROBLEM HAPPENING. IF YOU DO NOT HAVE THIS YOU WILL NOT BE ABLE TO RECOVER.
DISCLAIMER - THIS IS AN AMALGAMATION OF IDEAS, PROCESSES AND GUIDES FOUND ONLINE ALONG WITH MY OWN MODIFICATIONS AND PROCESSES THAT I HAD TO MAKE TO GET THE PROCESS TO WORK FOR ME.
ALTHOUGH I HAVE PERFORMED THIS PROCESS IN FULL AND IT HAS WORKED FOR ME I AM NOT RESPONSIBLE FOR ANY DAMAGE OR DATA LOSS THAT ARISES FROM FOLLOWING THIS GUIDE. BY USING THIS GUIDE YOU ARE ACCEPTING ANY AND ALL RESPONSIBILITY FOR ALL ACTIONS AND THEIR RESULTS.
IT GOES WITHOUT SAYING THAT PERFORMING THIS PROCESS WILL INVALIDATE YOUR WARRANTY BUT IF YOU ARE ALREADY ROOTED AND RUNNING CUSTOM SOFTWARE THEN YOU HAVE ALREADY INVALIDATED YOUR WARRANTY ANYWAY.
This is a common problem that usually occurs when a problem is encountered flashing a file from Recovery. Please take the precautions listed below, it will save you a lot of trouble should you ever suffer from this problem.
Backup Process
There are 3 ways that I use to back up the /efs directory.
These are:
1 - Manually copy /efs to your SD Card and make another copy somewhere safe (Computer, Dropbox, etc).
2 - Use HC-kTool to make a backup image of your /efs directory.
3 - Use Galaxy S Unlock AND GSII Repair to make backups of your original /efs directory (These are both the same but by doing both you have two copies of /efs available should you need it).
All Apps available from the Google Play Store or can be downloaded in the AppPack from here
At the end of this process you will have 4 copies of your /efs directory on your SD Card as well as any dulicates you created externally in step 1. This might seem like overkill but trust me taking 5 minutes creating these will save you hours and possibly quite a bit of money in repair costs in the long run should you ever need to recover!
Now you have your backups lets hope that you never need them, but should you then...
Recovery Process
Acknowledgements
Based on original post by XDA Member vaskodogamagmail with more detail and modifications to make process work added by me.
Original Post
Symptoms
You may have one, some or all of the following:
No Signal
Emergency Call Only
No Network
IMEI 004999010640000
IMEI 000000000000000
IMEI
(To check your IMEI number either enter *#06# dial into the dialer or check in Settings, Phone Information)
Prerequisites
Rooted Phone
Try the following processes in order until the problem is resolved.
Method 1:
Open HC-kTool and choose "Restore efs from backup (DANGEROUS!)" then choose "Restore IMG". Once completed you will be prompted to reboot. Perform Reboot and if all has gone well you will have a working phone again.
Method 2:
Open Galaxy S Unlock app and select "Restore saved EFS Folder". This will come up with a response saying "Done". Reboot and see if your phone is working again.
Method 3:
Open GSII_Repair and perform Options 2 and 3. Your phone will reboot. Once it has rebooted see if your phone is working.
Method 4:
Open GSII_Repair and select "Restore saved EFS Folder". This will come up with a response saying "Done". Reboot and see if your phone is working again.
Method 5:
This is the last chance (and the one that after tweaking to what you see below worked for me).
You will Need the following:
Stock GB ROM
Insecure Kernel
ODIN
Quick Root
All of these can be downloaded in the IMEIFix.zip which can be downloaded from here.
Android SDK and ADB instaled on your Computer or a Terminal App on your Phone (Personally I prefer ADB from Computer but you choose whichever you are most comfortable with).
We are going to restore your phone to as close to original stock a possible. No data wil be removed from your SD Card(s) but all installed apps, customisations, ROMs and Kernels will be removed. Please backup everyting you need before runnng this process.
If you are able to make a Nandroid Backup of your Rom you will be able to recover this at the end of the process.
Open ODIN
In Options select "Auto Reboot" and "F. Reset Time".
Select the following files from the "OriginalRom" folder on your computer:
Bootloader -> KERNEL_I9100XEKDB_CL161513_REV02_user_low_ship.tar.md5
PDA -> CODE_I9100XEKDB_CL161513_REV02_user_low_ship.tar.md5
Phone -> MODEM_I9100XXKDH_REV_02_CL995882.tar.md5
Reboot your phone into Download Mode (Hold down Home, Volume Down and Power when turnng on).
When in Download Mode connect to Computer via USB.
You will get a Ready message in one of the top boxes in ODIN. When you have this press the Start button.
After a while your phone will reboot and load up into it's Stock setup.
Configure the settings and then Power down the Phone.
Once Powered down go into Download Mode again (same process as above).
In ODIN press Reset.
Set the same options as before.
This time only set the Bootloader box. Select the file from the "InsecureKernel" folder on your computer - NOTE Insecure means that it is able to be rooted, not that there is a security issue with using it. We will be replacing this later anyway.
Check you have the Ready in the top box in ODIN and press Start.
Once finished your phone will reboot to stock again. IMPORTANT - Disconnect the USB cable before proceeding.
Go to Settings, Applications, Developer Options.
Turn ON "USB Debugging".
Connect USB cable to Computer and Phone.
Open "Samsung Quick Root"
Select "Reboot Device When Finished"
Press "Root Device"
Some text will scroll on the screen and then phone will reboot.
This will have installed SuperUser, Busybox and Rooted your phone.
Install a Root capable Explorer app, I used Es File Explorer, either download from the Play Store or you can install if from the Apps folder of IMEIFix downloaded above.
Open a Command Prompt on your Computer
Enter the following commands:
adb shell
su
busybox umount -l /efs
exit
exit
Using your chosen exporer delete the efs folder from the root of your phone.
Reset the phone, after that open your explorer again and browse to the Root, the efs folder should have recreated and will contain files. These are new and are system generated.
Go to the efs folder using your chosen explorer, and delete "nv_data.bin" and "nv_data.bin.md5".
Go to the working back up of your efs folder on your SD Card, copy the "imei" folder to the efs folder at the root of your phone, then again go to the backed up efs folder on your SD Card and copy the "nv_data.bin" file to your efs folder at the root of your phone using your explorer. Once you have copied this file, please rename the new file to "nv_data.bin.bak".
Make another copy of the "nv_data.bin" file in the backed up efs folder on your SD Card and paste this into the efs folder at the root of your phone again.
On your Computer open a command prompt and enter the following commands:
adb shell
su
chown 1001:radio /efs/nv_data.bin
Reset your phone.
You should now have your Original IMEI, check this by dialing *#06# call into the dialer. If you have the correct IMEI then you are done. You can either reinstall your usual ROM, Apps, Kernel etc manually or restore an existing backup.
If you need to install a Recovery with CWM (to restore backups or install new ROMs and Kernels then please follow these steps:
Install Mobile Odin from ChainFire from the Play Store (or if you are an XDA user you can download from here)
If you have used the XDA version you will also need the eu.chainfire.mobileodin.flashkernel.i9100.v2-1 apk file, this is in the IMEIFix download above in the Apps folder.
Copy the Kernel-V7.tar file from the CWMKernel folder in IMEIFix to your SD Card.
Open Mobile Odin and from there open the Kernel-V7.tar file. This will flash Dorimanx 7.45. If you now boot into recovery you can flash what you need to in the usual way.
By following the process above you will likely find that the Triangle Alert is now on your screen when booting yor phone indicating that your bootloader has been modified. Although this makes no functional difference to your phone you can remove this alert by installing TriangleAway from the Play Store (or if you are an XDA user you can download from here. This will reset the flash counters in your phone and remove the warning.
If you still have the wrong or no IMEI then you will need to seek further help.
There is no obligation but if this guide has just saved your phone and you feel you would like to show your appreciation there is a "Donate" button on the left, please feel free to use it.
YouTube fix
The problem is actually with Xlory's Inverted Play Store so far a fix had not been released by Xlory so we have to use the following workaround based on suggestion from Nos_20 and modifications from Andreas75k.
Fully uninstall YouTube, firstly from the Play Store or Settings, Applications and then from Rom Customiser (Manage System Apps).
In Rom Customiser go to OTA then select and flash Stock Play Store.
Goto Settings, Applications and wipe cache, data and any updates for Google Play Services and Google Play Store.
Reboot to recovery.
Wipe Cache and Dalvik Cache.
Reboot.
Once rebooted reinstall YouTube in Rom Customiser and update through the Play Store or just install directly from the Play Store but obviously it wont be a system app.
That's it, all should now work.
Key here is: don't use any modified versions of Google Play Services, Google Play Store or YouTube, only STOCK.
Phone Details and My Apps:
Phone: Samsung Galaxy SII i9100
ROM: AllianceROM i9100 JB v7 beta LSD
Kernel: Jeboo but usually Dorimanx
TrevStuff - My Apps and useful links.
If I answer your question by asking you to search or look somewhere else I'm not being rude. Just encouraging you to use XDA correctly.
Have you backed up your /efs folder? See here.
If I help you, please give me thanks.
Hello mate
Thanks for this very helpful and informative thread
:good::good:
Re: TrevStuff - Apps and Stuff to help with Alliance Rom
t-pip said:
Goto Settings, Applications and wipe cache, data and any updates for Google Play Services and Google Play Store.
Phone Details and My Apps:
Phone: Samsung Galaxy SII i9100
ROM: AllianceROM i9100 JB v7 beta LSD
Kernel: Jeboo but usually Dorimanx
TrevStuff - My Apps and useful links.
If I answer your question by asking you to search or look somewhere else I'm not being rude. Just encouraging you to use XDA correctly.
Have you backed up your /efs folder? See here.
If I help you, please give me thanks.
Click to expand...
Click to collapse
By that ^^ you mean to clear data and cache for google play and google play services and their updates also...
Because I cleared only for the updates and it didnt work... could you please make it clearer for other users
Thanks Alot for the guide and ur 'stuff' very useful
Re: TrevStuff - Apps and Stuff to help with Alliance Rom
Ba7rani123 said:
By that ^^ you mean to clear data and cache for google play and google play services and their updates also...
Because I cleared only for the updates and it didnt work... could you please make it clearer for other users
Thanks Alot for the guide and ur 'stuff' very useful
Click to expand...
Click to collapse
Thanks for that. Yes wipe cache and data after uninstalling updates.
Phone Details and My Apps:
Phone: Samsung Galaxy SII i9100
ROM: AllianceROM i9100 JB v7 beta LSD
Kernel: Jeboo but usually Dorimanx
TrevStuff - My Apps and useful links.
If I answer your question by asking you to search or look somewhere else I'm not being rude. Just encouraging you to use XDA correctly.
Have you backed up your /efs folder? See here.
If I help you, please give me thanks.
Great thread good info. :thumbup:
alliance 7.3
apollo 4.5 regular
I9100

Categories

Resources