Related
[SOLVED, see below].
I've also attached the Su flashable zip to this post, as linked below
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I recently rooted my Desire using unrevoked 3.2.1 Basically, no problems so far.
However, when I have tried to run a few Apps that require ROOT access, the Superuser pop-up screen shows, EVERY TIME.
I have clicked Allow, and made sure to check "Remember", but it comes back every time for the same Apps.
I have double-checked that the Apps requesting Superuser permissions are indeed in the Superuser.apk list for Allow. They are, little green dot and all, but it doesn't seem to matter.
I tried a Batch routine in Titanium Backup, and I had to click that damn Allow button like 150 times!
Does anyone have any idea what's going here? Anyone experienced the same thing?
I wonder if it is related to what mortenmhp mentioned over in this post (post 3, "Cant remove Stock apps? Root Explorer and Unrevoked3"; sorry, I can't link yet)...
the fact that unrevoked3 still does not achieve S-OFF HBOOT and thus doesn't r/w to /system.
Btw. the thread mentioned:
http://forum.xda-developers.com/showthread.php?p=8324672#post8324672
Your problem should not have to do with this though.
The superuser app stores it's list on the data partition, and it should be able to grant su access to anything apart from rw to the protected partitions.
First off:
- Does it happen to all apps requesting su?
- Which version of superuser are you currently using?
- How did you get it? Like was it included in a rom or did you install it by flashing superuser only?
- If included in a rom, which?
And finally. You should start by trying to clear the data associated with the superuser app:
"settings -> applications -> application list* -> Superuser -> clear data button"
*I dont remember the exact name, and the charger for my desire is gone for now
If it does not work, you should also try to do a nandroid backup and a factory reset by wiping the data partition to see, if it doesn't fix it.
Thanks for your response, let me see if I can fill in some of the details:
Yes, it happens AFAIK for ALL Apps requesting Superuser access
Version: Superuser v2.3.6.1 - Added c...
Database version 5
(From the info at the bottom of the Superuser>Settings menu)
IIRC, I may have installed the App myself from the Market...? Is that even possible? Honestly, I may have jumped ahead of my knowledge in this one area. But I'm certain it wasn't from any flashing, unless unrevoked adds the App itself.
ROM, Froyo w/ HTC OTA Sept. update
I rooted with unrevoked3.2.1, but haven't flashed anything
(other than the Clockwork Mod as part of unrevoked, and, the ?re-flash? of Clockwork via ROM Manager)
The most noticeable example of this problem is Titanium Backup; I have to click Allow 14 times each time I open the App. And it is clearly listed in the Superuser List, with a green dot.
UPDATE: It is definitely possible to install this App directly from the Market, as I just re-did it. Then I Rebooted, but it all made no difference, still have 14 Allows in order to launch Titanium Backup
Results
Alright, I tried to "Clear Data", and then I did a reboot for good measure. It did NOT work.
The Superuser list was blank, but as soon as I started Titanium, I had to do the same 14 Allows. The Titanium>Log clearly shows each of them, but it's like the fact that the setting is "Remembered" doesn't have any effect.
I guess I can try the Nandroid back-up/wipe, but that just seems to be in the "format and reinstall Windows" family of solutions (no offense).
Other observation
Here's something else I noticed, may or may not be related.
I have Spare Parts installed, and I was testing the different settings.
First, Reboot/Recovery options ask for Superuser access, but then nothing happens, it just returns to the Spare Parts menu.
I'm interested in "upgrading" my boot animation (I have another thread about that), so I also tried the LeoFroyo Addon of Bootanimation>LeoFroYo BIOS
It Requested Superuser access, delayed while "Working...", and then asked to Reboot. When I clicked Yes, nothing. Just went back to the Spare Parts menu. When I rebooted manually, the stock HTC animation is still what I got.
Relaunching Spare Parts confirmed that the bootanimation setting was still on the upgrade, it apparently just didn't work.
The reason I mention these things is because I wonder if possibly I haven't achieved all the ROOT access that maybe I should have???
Any other thoughts? I'm not sure what else to try, but I can provide any other details that would be useful.
Maybe I'm just fighting a pointless losing battle on this, since I plan to flash to Cyanogen anyway. But it just find it irksome that I can't find a solution to a relatively straightforward issue.
It is because you cannot just install the superuser app from the market, because it needs root in the first place. This might just be your problem. I cant find the update.zip only including superuser right now, so if you want cm anyway, I would just go for it. Otherwise you will have to search for a zip file only including the superuser files or another rom with it included.
edit: and sorry for not replying but i have school as well
edit 2: This should be the zip file to flash to get superuser only hope you can get it to work.
Success
Yessir! That did it.
I think you're right. Don't know what I read to carelessly make me think I could just download Superuser from the Market. Actually, I'm not even too sure why its on there, since it CANNOT work if you install it that way.
I guess when I installed Superuser to grant ROOT permissions, I didn't have ROOT permissions. So, Superuser could grant other Apps ROOT (which did work), but it didn't have ROOT itself to store the Allow list. How ironic.
When I get to a computer, I'll add that linked zip as an attachment to this thread, along with some flashing Instructions in case anyone else is less familiar.
It must be pretty uncommon to do the work to get ROOT and then not flash a custom ROM with Superuser built in.
Thanks for your help. All glory to mortenmhp
okay, i was stupid. this fixed the problem for me too! thanks a lot.
Thank god for this thread
Had same problem
solved for me
And for now, i just want su, no custom rom, they seem to be sometimes unstable
Guide for dummies
just in case(copied),
Transfer this zip file file to your SD card. Remember where you saved it.
Reboot the phone into Recovery
(Boot the phone by holding down either the circle button or Volume Down button, then press the Power button. Select Recovery from the menu. (You can navigate the menus with the volume button, and make selections with the round button thingy).)
Select Install zip from SD card and navigate to where you copied the zip file and install. Watch out: Do NOT select the similar-looking apply sdcard:update.zip menu item. You have to confirm by selecting the correct ZIP file from a list.
reboot phone.
This woked for me too. Thanks a lot it was very annoying.
Oh and thanks for the dummies guide. I have not done anything but a nandbackup do it helped me feel a little more comfortable.
Great . It worked for me as well.
Thanks scott and all
FIRST THINGS FIRST:
This represents very little work that I've done on my own. It is mostly appropriating the work of others. The important thing to note is that the file works and it works well.
All I did to create this file was incorporate a modified version of stachre's updater-script into the official WiFi 3.1 update from Google (this is not the file you should flash).
I then added the kernel & all of the files from bigrushdog's HC3.1 .zip EXCEPT the system.img file (which is the vast majority of the update). BRD's HC3.1 installs the 3G version of 3.1 with Hotspot/Tethering options in the settings menu under Wireless & Networks, and I personally want to have the WiFi-only software on my WiFi XOOM. His version seems to work just fine and the only difference I noticed was in the Settings menu, but that was enough of a difference for me to prefer the WiFi only software. I'm sure more of you may feel the same. If there are any other differences between the WiFi & 3G software I'd be curious to know what, if any, there are.
I then added the code from BRD's updater-script (minus the parts relevant to flashing the system.img) on to the end of the updater-script from stachre's updater-script.
One of the benefits of this approach is that it does not require you to perform a factory data reset, as BRD's method currently does. And yes, you will have access to your external SD Card in the /sdcard/external folder.
It is super late and I am exhausted, but I wanted to share this with you before I fall asleep. If you seem to notice that these instructions are more or less copy and pasted verbatim from stachre's thread, that is because they are. This is a simplified version of his method with the addition of BRD's modified version of the stock 3.1 kernel for SD Card storage. There are fewer steps (now only 2) because more files are included in the zip.
[size=+1]DOWNLOAD HERE - FLASH IN CLOCKWORK RECOVERY:[/size]
MZ604_3.1_ROOT_update.zip
WARNING: Following this procedure may damage or permamently destroy your device. This procedure is provided with NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Perform this procedure at your own risk.
COMPATIBILITY NOTE: I have personally tested this procedure ONLY ON THE US XOOM WIFI MZ604. If other devices (i.e., Euro Xoom WiFi) implement the same Android 3.1 update file, then this procedure *should* work; some users have reported success with UK and Canadian models (see this post for more info). Know, however, that you proceed at your own risk. If you're stuck in a boot cycle, try a factory data reset in recovery.
[size=+1]SUMMARY[/size]
Here's a run-down on the current procedure:
Updates the Xoom WiFi to Android 3.1 using ClockworkMod Recovery (MZ604_3.1_ROOT_update.zip)
Resolves issue in updater-script: get_prop ro.product.device wingray
Pushes Superuser and su, sets correct permissions to enable functioning root
Flashes the system partitions to stock (required at this time)
Flashes bigrushdog modified stock boot.img (kernel) to enable external storage
Updates bootloader to include Recovery in the boot menu
Leaves user data intact
Leaves recovery intact
Outstanding Issues:
The new
Videos.apk does not appear in app drawer after update, according to Motorola this was done intentionally. Videos still play in Gallery. For some reason Motorola doesn't want us to use this app yet on the WiFi Xoom, but it's available on the 3G Xoom.
Now, without further ado...
[size=+1]ASSUMPTIONS[/size]
You've downloaded the update here: MZ604_3.1_ROOT_update.zip
You've downloaded and unzipped the stock Xoom WiFi MZ604 HWI69 images from Motorola also available via torrent
You've flashed a recent version of ClockworkMod Recovery (thanks, bigrushdog, koush, et al)
You've installed a physical SDCard in your Xoom (required for ClockworkMod Recovery updates) and have it functioning properly
You've configured the Android SDK on your PC, with adb functioning properly
You've downloaded fastboot and have it functioning properly (usually alongside adb in platform-tools)
[size=+1]PROCEDURE[/size]
Flash stock system.img & boot.img
Prior to performing the actual update, the update script checks a number of files (including bcm4329.ko, which is usually built with the kernel) in /system. If any file doesn't match what's expected, the update halts. Flashing the stock system.img ensures a smooth update.
The pre-update checks also include the boot partition. The actual update flashes this partition with a new kernel that implements the new 3.1 features.
If you are unlocked and running unrooted stock Android 3.0.1, you can skip step 1. If you are already on 3.1 and just need root and/or external SD card storage, see this thread.
Code:
adb reboot bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
Perform update
Code:
adb reboot recovery
You may need to re-enable USB debugging in the Application settings menu before you can send the above adb command. Alternately after sending 'fastboot reboot' in step 1, wait a few seconds after you see the Motorola logo and tap the Volume Down button. If you see "Android Recovery" at the top of the screen, tap the Volume Up button to boot into recovery and install from there.
Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select.
In ClockworkMod Recovery, select "mounts and storage"
Ensure your Xoom is connected to your PC via USB, then select "mount USB storage"
On your PC, copy MZ604_3.1_ROOT_update.zip to the root of the Xoom's SDCard ("Removable Disk" in Windows)
In ClockworkModRecovery (still on the "USB Mass Storage device" screen) select "Unmount"
In the "Mounts and Storage Menu" screen, if the option "unmount /sdcard" is present, continue to the next step; if "mount /sdcard" is present, select it then continue
Select "+++++Go Back+++++"
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "MZ604_3.1_ROOT_update.zip"
Select "Yes - Install MZ604_3.1_ROOT_update.zip"
"Install from sdcard complete." will indicate that the update is completed.
.
Select "reboot system now"
New bootloader will install. The message, "Congratulations! Your bootloader was successfully upgraded" will be immediately followed by an automatic reboot.
Enjoy your rooted Xoom WiFi, running on Android 3.1!
CUSTOM KERNELS:
I told you guys it wouldn't be long. TDR has already released an overclock kernel for WiFi Xooms on 3.1.
Tips & Tricks for quick-booting into Fastboot & Recovery:
Booting into Fastboot:
Hold down both the power button and the Volume Down button. Fastboot support will boot and you can flash system/recovery/userdata images.
Booting into Recovery:
I haven't seen anyone else mention this. If you power up, wait a few seconds after the Motorola logo appears, then hit the Volume Down button you will see "Recovery" appear at the top of the screen. Hit the Volume Up key to boot into recovery!
Great instructions, the simplest I could see so far! The above process worked for my WIFI only XOOM which I had rooted and installed the Tiamat Xoom Kernel. I am in Australia so was impatient to wait for OTA which probably wouldn't have worked anyways from what I have read.
How does this differ from bigrushdogs procedure? I have a wifi only xoom and am not sure which method to follow. Is this for stockusers?
it is different because no wipe is needed, if you are stock (unrooted) you will have to wipe when you unlock the bootloader
This is exactly the method I used, though I did thinks manually and it took a while, but works great
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Sent from my Xoom using Tapatalk
Dubar said:
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Click to expand...
Click to collapse
I think this problem is a bit two-faced, as a few of us on the 3G/VZW XOOM have updated fine and have a working video player, but rentals purchased do not play instead throw an Error 49 license error, while local content plays fine.
The Wifi users are reporting that the videos app doesn't even show up, let alone open. General suckage, not even being able to play local content.
I've been tinkering around with logs and trying to narrow down my error 49 issue but thus far have been unsuccessful.
xoppaw said:
How does this differ from bigrushdogs procedure? I have a wifi only xoom and am not sure which method to follow. Is this for stockusers?
Click to expand...
Click to collapse
Yeah, the two main differences between this and BRD's procedure is that you don't have to perform a factory reset to get this one to work, and this method requires adb/fastboot. I don't think you should have to erase all your data just to install an official update. It's also only one file to flash.
The other difference is that this version doesn't have artifacts from the 3G version in the Wireless & Networks Settings menu (if that bothers you).
I don't know if this update would apply on an unlocked and unrooted Xoom, but if your Xoom is unlocked this version of the update should give you root. Both would be worth testing
Dubar said:
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Click to expand...
Click to collapse
tekuru said:
I think this problem is a bit two-faced, as a few of us on the 3G/VZW XOOM have updated fine and have a working video player, but rentals purchased do not play instead throw an Error 49 license error, while local content plays fine.
The Wifi users are reporting that the videos app doesn't even show up, let alone open. General suckage, not even being able to play local content.
I've been tinkering around with logs and trying to narrow down my error 49 issue but thus far have been unsuccessful.
Click to expand...
Click to collapse
You can still play videos/local content fine through the gallery app, so we are safe in that respect. I can still watch all my movies or videos filmed on the Xoom just fine.
Here are some observations that I made. The WiFi update only included the Videos.apk file while the 3G update also included a Videos.odex file as well. I chose to add the Videos.odex to the update file in the OP, but it didn't make a difference (Videos apk still doesn't show in the app drawer).
Thanks.. Worked great.
Note: I had to re-enable USB debugging on the Xoom after flashing the Stock System and Boot Images.
Land Master said:
Thanks.. Worked great.
Note: I had to re-enable USB debugging on the Xoom after flashing the Stock System and Boot Images.
Click to expand...
Click to collapse
Thanks, I updated the OP to take account of that. Ever since I figured out how to boot into recovery from the Motorola logo I haven't really needed to send the 'adb reboot recovery' command.
I used BRD update method for my wifi zoom (don't care about the extra settings) and I have a working videos.apk that plays local content. I have not yet tried to rent a video.
kev0153 said:
I used BRD update method for my wifi zoom (don't care about the extra settings) and I have a working videos.apk that plays local content. I have not yet tried to rent a video.
Click to expand...
Click to collapse
Yes, I'm pretty sure for whatever reason the Videos.apk is enabled for the 3G version of 3.1 but not for the WiFi version of 3.1. I agree that the extra settings isn't a big deal, I made this file mostly because I wanted a way around wiping all of my user data.
Rumor has it that Google has said that the Videos.apk will be working on the WiFi Xoom in a few days.
I used the method posted by stachre from yesterday, and I don't have access to my sdcard in sdcard/external. Any way I can change that? The two methods seem to be very similar...and I want my SD!
IXIKelsonIXI said:
I used the method posted by stachre from yesterday, and I don't have access to my sdcard in sdcard/external. Any way I can change that? The two methods seem to be very similar...and I want my SD!
Click to expand...
Click to collapse
Download and flash this file:
http://www.mediafire.com/download.php?2bj5taicy3buc5c
Basically do what I said to do in the OP but skip step 1.
You are beautiful, and I love you.
I installed brd's 3.1 update yesterday, and i tried to install this zip over his method because i have a wifi xoom and wanted to get rid of the hotspot settings, but when i try to flash this in cwm i get an error:
Assert failed: file_getprop("system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.0.1/hwi69/110420:user/release-keys" || file_getprop("system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/hmj37/124251:user/release-keys"
E: error in /sdcard/mz604_3.1_ROOT_update.zip
(status 7)
installation aborted
What is the problem? Is it not possible to flash this over his method? Do i have to change the build.prop?
Thanks
Edit:
Solved by going back to stock 3.0.1 and installing the cwm to get updated to 3.1.
WARNING Boot Loop!
Warning. This method set me in to a boot loop. The tip at the bottom of the instructions eventually saved me as I booted in to recovery (adb stopped working after awhile) and upgraded via bigrushdog's clockwork thread. Not sure if it was my custom boot theme or something else. I reflashed twice while adb was still working. All looked good each time but then when I rebooted to do the final cwm step, this is where I looped each time. I was careful. Not sure why it messed up.
Thanks a lot for putting this together, worked like a charm.
So what about overclocking. I don't have option above 1ghz. Is this because we are back on a stock kernal. Will we have to wait for Tia to make a new one?
Sent from my Xoom using XDA Premium App
kntdookoo said:
So what about overclocking. I don't have option above 1ghz. Is this because we are back on a stock kernal. Will we have to wait for Tia to make a new one?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Bigrushdog has said that they are working on an overclock tiamat kernel for Android 3.1. So yes it is expected that you can not overclock your xoom in 3.1 currently.
A few questions since I have not updated my xoom to 3.1 yet:
1) Is everyone experiencing the Videos.apk error where they can't install the videos app?
2) How are the 3.1 updated features? Can anyone share if the overall user experience is better in 3.1 (better scrolling, smoother, etc).
I am kinda holding off updating 3.1 until I hear more of the drawbacks of 3.1.
ericdabbs said:
Bigrushdog has said that they are working on an overclock tiamat kernel for Android 3.1. So yes it is expected that you can not overclock your xoom in 3.1 currently.
A few questions since I have not updated my xoom to 3.1 yet:
1) Is everyone experiencing the Videos.apk error where they can't install the videos app?
2) How are the 3.1 updated features? Can anyone share if the overall user experience is better in 3.1 (better scrolling, smoother, etc).
I am kinda holding off updating 3.1 until I hear more of the drawbacks of 3.1.
Click to expand...
Click to collapse
1. It's weird. My understanding is that even, unrooted stock WiFi Xoom owners can't access the new Videos apk on 3.1. The Videos.apk is there it just doesn't show up in the app drawer so there isn't any way to access it. If you look for it in a file manager like Root Explorer you can see it. There are other "ghost" apps like that in Android like the SoundRecorder.apk, so that's not completely unheard of. What's puzzling is why the 3G Xoomers got one that works and we didn't. If/when this is solved I will update the OP. It does work if you use bigrushdog's update method (but you gotta wipe all your data).
The Videos apk is mostly a showcase for their Video rental service that they announced Tuesday, you can still play videos in Gallery, so you're not really missing out on any major functionality at the moment.
2. The new features are cool! It's hard to compare performance since I was overclocked before and now I'm not. I love the resizable widgets. Overall it does feel like a more polished OS, they fixed a whole bunch of little itty bitty issues here and there. I can't really think of any downsides to the upgrade, it just feels like a step in the right direction. I'm definitely looking forward to see where Honeycomb development goes in the future.
I have installed this update over my rooted wifi only 3.0. It worked great, i did get a boot loop and was forced to wipe in recovery (luckily i did a titanium backup first), apart from that it went through no problem.
I haven't used the browser extensively yet, but it does seem more stable, hasn't crashed yet and the overall browser seems much better, especially the thumb menu from labs.
Good work!!
(I have the wifi only UK version BTW)
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.
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
Hey all!
As you all know, Wileyfox has started rolling out Nougat for their devices, starting with the codenamed marmite family (Swift 2, 2 Plus and 2X models). With this new update, Wileyfox has also included a bunch of BLOATWARE I personally NEVER expected from them. I mean, I didn't request ads in my launcher, and why do I need to forcefully use Truecaller dialer instead of the cleaner, AOSP-based one? That's why I've created this Wileyfox Debloater tool, to keep the system apps as clean and stockish as possible.
App removals included:
- AndroidPay
- BasicDreams
- BookmarkProvider
- Google Books
- Chrome
- CMFileManager
- Drive
- Duo
- Gmail
- GooglePrintRecommendationService
- GoogleTTS
- Hangouts
- Keep
- Maps
- Google Music
- News and Weather
- PhotoTable
- talkback
- Google Videos
- WFChromeCustomization
- Youtube
- Contacts
- FoxHole
- Mms
- SnapdragonGallery
- TrueCaller
- All bundled-apps from /system/vendor/bundled-app
- Possibly more in the future.
(Note: All the moved Google Apps were removed for the sole reason that they can also be downloaded from the Play Store.)
App additons / other features included:
- Google Contacts, in replacement of the half-dummy, prebundled Contacts app (which was missing link with the Dialer).
- Google Dialer, in replacement of TrueCaller.
- Google Messages, in replacement of Wileyfox Mms app.
- AOSP's Launcher3, in replacement of FoxHole (Wileyfox's Launcher).
- Framework and permission files for Google Dialer to work.
- Small tweaks in the build.prop, including drop of min processors to work from 2 to 1, and rise of maximum processors to work from 4 to 8, as well as increasing the Android compiler default amount of processors from 4 to 6.
- Possibly more in the future, too.
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
(To learn how to properly upgrade your device, kindly check post [URL="https://forum.xda-developers.com/swift-2/development/debloat-wileyfox-debloater-quickly-t3587536/post72258926#post72258926"]#25[/URL])
2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Downloads:
- For the latest Wileyfox Swift 2, Swift 2 Plus and Swift 2X firmware: Wileyfox-TOS118C-Debloater--11-05-17.zip
(For version TOS089 check Wileyfox-TOS089-Debloater--10-04-17.zip)
- For more Wileyfox devices, coming soon
Installation instructions:
1. Update your device to Nougat
2. Unlock your bootloader and flash TWRP
3. Download the latest version zip
4. Boot into TWRP, make a backup if you wish (although is highly recommended), choose Install and locate and flash the ZIP.
5. Reboot and enjoy!
6. Are you missing missed calls notifications? Is the caller ID always showed as a number instead of a contact name during phone calls? Check post #16!
Uninstall instructions:
Check post #6
Enjoy, and don't forget to leave a Thanks if you loved it!
I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
rivierakid said:
I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
Click to expand...
Click to collapse
That is also a possibility but:
1. Launcher3 conflicts with the already installed launcher, so it's impossible to get that out of the way
2. I got latest version working here using the required libraries (extracted from a Pixel), so yeah, probably both possibilities are just fine
And for the third one, just wanted to say there's no need to reactivate them (if you manage to deactivate them, ofc), and, all of the packages the script moves are stored in a safe place (/system/__bloat), so they can be restored from there
I don't remember if I had a problem with a previous OTA update for Wileyfox, but I was not able to install an update without reactivation a disabled app.
I'm not sure...
You could select a default launcher and the phone has really enough RAM, so I think it is not necessary to remove the FoxHole from the system.
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
The final solution for this is LineageOS, if they provide the source
Excellent! Thanks for providing this...such a stupid shame that Wileyfox decided to do this. I'm just hoping that they now release their sources so that we can start working on a proper release of Lineage!
*Edit: Nice! https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937/commits/all*
JT
rivierakid said:
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
Click to expand...
Click to collapse
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.
Hello,
thanks for your effort to the community.
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.
linuxct said:
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.
Click to expand...
Click to collapse
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT
MCPoppa said:
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.
Click to expand...
Click to collapse
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
jdtanner said:
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT
Click to expand...
Click to collapse
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions
linuxct said:
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions
Click to expand...
Click to collapse
Everytime i installed twrp i got stuck in a bootloop :/
MCPoppa said:
Everytime i installed twrp i got stuck in a bootloop :/
Click to expand...
Click to collapse
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
linuxct said:
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
Click to expand...
Click to collapse
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?
MCPoppa said:
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?
Click to expand...
Click to collapse
I explained it last night here, but I also stated it in the OP:
linuxct said:
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
[B]2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.[/B]
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Click to expand...
Click to collapse
linuxct said:
I explained it last night here, but I also stated it in the OP:
Click to expand...
Click to collapse
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?
MCPoppa said:
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?
Click to expand...
Click to collapse
Try flashing it to your recovery partition, my guess is that now that DM-verity is disabled everything should work fine
Cheers!
Quick update post after two days of usage, yesterday I noticed I didn't receive any notifications on missed calls, and that the caller ID always showed as a number although I had it added as a contact.
I realised that I didn't have any "Phone" app chosen as default in Android settings, so I was missing those notifications until I opened the Google Dialer app.
In case it happens to you, to sort it out go into Settings > Apps, then hit the gear in the top right corner and make sure you've a config similar to this one (Launcher3, Google's "Phone" and Google's "Messages" chosen as default Home, Phone and Messaging apps).
I hope this is clear for everyone, since it's not something I can fix on my side/requires the user to do the change
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
Ianharding said:
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
Click to expand...
Click to collapse
Firsts things first: After heavily modding the system like you did on Marshmallow, make sure not to update your device through the regular OTA but using a recovery image like the ones posted in this device's forum.
For magisk: are you sure you flashed it correctly? Magisk disables that dmverity message you are mentioning, so maybe you installed an old version or wasn't properly flashed.
My advice is: download everything: the recovery image, the debloater and Magisk. Boot into TWRP, wipe EVERYTHING if possible, including Data cache dalvik cache and system partitions. Once done, flash the recovery image zip, and right after that, without rebooting, flash the debloater and magisk. Reboot and everything should work perfectly
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
digidude512 said:
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
Click to expand...
Click to collapse
As soon as you root any Marshmallow/Nougat phone Android Pay will not work, according to this article
I have never used Android Pay so it doesn't make any difference to me. My phone is much better now that I have debloated it. I also installed Evie Launcher and Halo Browser, both small minimalist apps and everything is really smooth.
Instead of a Debloater, could the Stock ROM not be debloated and rezipped as a custom 'Lite' version?