Related
Yes..i searched..all over but got no answers....as I live to learn these kinds of answers from the incredible people who bust there butts so the "Dev in training" like myself can hopefully help contribute to new projects sooner then later!!
I am running EVO with CM7 7.0.3.1 which is Amazing....so thank you sincerely for offering this to less skilled people like myself who are still reading, trying, failing, fixing, and learning and passing on to others.
I will apologize in advance for this post if it is nothing but....I had a permission request pop up:
Titanium Backup 10064
Package: com.keramidas.TitaniumBackup
Requested UID: root (0)
Command: /system/bin/sh
Status: Allow
Created on: 5/24/11 06:01:03
Last Accessed: 5/24/11 06:01:03
Deny......Forget.......Cancel
I believe that 5/25 is when I flashed Cm 7.0.3.1 with the included CM 7 kernal.
Should I be worried??? I have a nandroid from 5/21 that is my goto for fixes in a stock ROM. I have another nandroid that was done on 5/24 at 8;57am but took it off my SD and saved to my desktop to make more space and 5/21 I know is solid.
Evo - Hardware 0004
CM 7.0.3.1 with included kernal
Radio_2.15.00.11.19
Pri 1.90_003
unrevoked forever S-off
Hboot 2.10.0001 (Not 100% sure and dont want to touch phone to find out)
Gapps 20110307
Thank you in advance for anyone who can help me understand if this is bad or no big deal.
FYI - I just downloaded kernel manager that toast suggests but haven't even run yet and also downloaded phone tester that I ran 5 minutes prior to the TB request.
Again, thank you....and as I am looking for more knowledge, if anyone needs help with a project that a semi-noob like myself that learns quick can assist with please let me know. I work cheap...FREE!!!!
velocity300 said:
Yes..i searched..all over but got no answers....as I live to learn these kinds of answers from the incredible people who bust there butts so the "Dev in training" like myself can hopefully help contribute to new projects sooner then later!!
I am running EVO with CM7 7.0.3.1 which is Amazing....so thank you sincerely for offering this to less skilled people like myself who are still reading, trying, failing, fixing, and learning and passing on to others.
I will apologize in advance for this post if it is nothing but....I had a permission request pop up:
Titanium Backup 10064
Package: com.keramidas.TitaniumBackup
Requested UID: root (0)
Command: /system/bin/sh
Status: Allow
Created on: 5/24/11 06:01:03
Last Accessed: 5/24/11 06:01:03
Deny......Forget.......Cancel
I believe that 5/25 is when I flashed Cm 7.0.3.1 with the included CM 7 kernal.
Should I be worried??? I have a nandroid from 5/21 that is my goto for fixes in a stock ROM. I have another nandroid that was done on 5/24 at 8;57am but took it off my SD and saved to my desktop to make more space and 5/21 I know is solid.
Evo - Hardware 0004
CM 7.0.3.1 with included kernal
Radio_2.15.00.11.19
Pri 1.90_003
unrevoked forever S-off
Hboot 2.10.0001 (Not 100% sure and dont want to touch phone to find out)
Gapps 20110307
Thank you in advance for anyone who can help me understand if this is bad or no big deal.
FYI - I just downloaded kernel manager that toast suggests but haven't even run yet and also downloaded phone tester that I ran 5 minutes prior to the TB request.
Again, thank you....and as I am looking for more knowledge, if anyone needs help with a project that a semi-noob like myself that learns quick can assist with please let me know. I work cheap...FREE!!!!
Click to expand...
Click to collapse
Let me explain kindly, as I doubt anyone will...
When a program is asking for root it is basically asking for the administrative priviledges. By allowing it, the program (or user) can modify files within the systems locked directories. Titanium Backup should be allowed root access in order to access any installed applications (to backup) or to restore any backed up applications.
Good luck.
Yeah, we're assuming you downloaded Titanium Backup and are trying to run it. If so, what you're seeing is normal, and you need to say yes for it to work.
Basically when you see that, you want to say yes if:
- You know why it popped up (say, you ran it), and,
- You trust the app to have full access to your system.
So in other words its asking for permission to read/write in the system data, like settings, bookmarks, user dictionary, also backing up data for the stock apps like gmail, camera, peep, messaging, etc.
If its some random app that you don't use for these functions /reasons is asking for root access, then its possible malware.
Yeah, pretty much. Titanium needs root access because Android's security model doesn't allow one app to access another app's data (except through the other app's defined interfaces, if any). A backup app, of course, needs to get around this.
You definitely want to know something about the app that's requesting root access before you say yes. Most apps are harmless -- they want root to do something legitimate, and something you asked it to do. But if you ever see the popup and you don't know what the app is and why it needs root to do what it's trying to do, then you probably want to say no and at least research it first.
It's the same idea behind the much maligned User Access Control in Windows Vista and 7. The idea is that if an app tries to do something with elevated privileges, you should have veto power.
First of all I want to thank all you for the kind informative responses. Secondly, I want to apologize for the time delay as I was deployed and just returned a few weeks ago and could not remember my login information until just now. I have been rooted and flashing roms etc., for over a year and I have used titanium since day one so I believe from what you have told me it was most likely malware do to the unusual way the message came up. You can just tell that it wasn't the normal request and something seemed not quite right about it. As it turns out, titanium was asking for permission to run titanium which in fact this request was coming from a different app that had maware and was trying to manipulate titanium. Fortunately, I did deny the request which I would say it was more luck then skill as I generaly allow most things on my phone where as running windows on my PC's I deny everything and research first. I know now where malware is an issue, but is it becoming a large issue on android based devices and I should be running some type of malware protection? Once again I thank each of you for your time, assistance, and providing educated help, not childish remarks and negative comments that has become almost expected on xda lately which is pretty sad for an open source based forum to help allow your device to do mostly specialty things. Again, the thank you......
If you don't mind me asking, what app was trying to use that method?
~ I'm a fungi
I have a Nook Simple Touch Glowlight with software verion 1.1.5. All the information that I've been able to Google is for 1.1.2, in fact that is the version that I still see on the B&N website.
I _think_ that I have found a suitable way to root the device with Nooter but I would like to know how to confirm that in fact this is the right project for my software version. I'm sorry that I cannot post a link to the Nooter project, but I have less than 10 posts.
Thanks.
There are at least two methods that work with the Glowworm.
You should not use any method until after you have
- made a noogie disk
- booted from it
- backed up your device
- restored that backup to a test disk (a 2 gig or larger microSD card, for instance) and confirmed that the test results in a disk that has 8 partitions.
Many people have made the backup but not tested it; when they tried to restore, they did bad to fatal things to their devices. A very common failure on restore seems to be only getting one partition restored and blowing out the other partitions.
I don't know if the stuff that eded is working on has come to fruition yet - he was looking at building a tool that could detect whether it was run on an NST or NSTG and root appropriately to the device.
The two routes I know work are:
- glownooter, the nooter project tool, includes Google apps and market support
- tinynoot, pasted together from various tools, gives you minimal root without google apps and with amazon appstore. Will work with either NST or NSTG because it's approach is so minimalist.
Thanks, roustabout! I will be sure to test the backups before I install anything else, then. Good to know!
In any case, what I am most concerned about is getting the right version of the rooting software for my device. I see that Nook devices have different firmware and that certain tools only work with certain firmware versions. I see no mention of my firmware version in any tools' websites, hence my apprehension.
hence the value of a backup
I saw your request on that and I think one of the issues here is that so many folks use Windows exclusively, and the backup process is so easy on linux that trying to tell people how to do it in Windows is like jabbing yourself in the eye with a stick, given that linux is free, vmware player is free, and linux can be installed and used for this job entirely in vmware player. On the other side of the coin, if you know nothing of linux, even using dd correctly will be a challenge since there's a pretty steep learning curve behind setting up a new OS successfully just to be able to get backups off an 80-130 dollar device.
In your case: as of now, there is only one firmware release for the glowlight. This is why the folks with the tools aren't mentioning it, aside from 'this is for a glowlight.'
I didn't mention it, but I also use Linux at home (Kubuntu, like Ubuntu but with a better UI). So many people are now using Ubuntu that I find it surprising that the instructions even bother mentioning the OSes for which the operation is as difficult as you say. I remember when doing things in Linux was hard and Windows was easy, and at that time Linux was hardly ever mentioned!
In your case: as of now, there is only one firmware release for the glowlight. This is why the folks with the tools aren't mentioning it, aside from 'this is for a glowlight.'
Click to expand...
Click to collapse
I did not realize that the 1.1.5 release is glowlight-only. Great, thanks, I'm on to hacking this thing!
ok, so for you the backup process is:
- make the noogie disk
- put it into your device
- power cycle your device
- when it boots to "rooted forever," connect the USB cable to your linux box
- once the linux box mounts the NSTG as storage, pay attention to which device it is mounting it at. Assuming it's sdX:
- backup with dd if=/dev/sdX of=backup.img bs=1M
When that's done, disconnect your NSTG, throw media of some sort, larger than 2G, onto your box and test your restore with
dd if=backup.img of=/dev/sdY bs=1M
Once that's done, do an
fdisk /dev/sdY
and a
p to print the partition table.
You should have 8 partitions (and your backup.img file should be just under 2 gig.)
Hack away; if you ever need to restore, you can just drop the virgin image back on.
I take a snapshot like this of my device every so often since remembering how I got to whatever config I liked is harder than just backing it up.
Thanks for the backup instructions, the idea of testing it on a DVD-ROM looks to save quite a bit of trouble with the actual device..
I rooted with this terrific guide:
http://forum.xda-developers.com/showthread.php?t=1675706
The process was simple. I do have an issue where I need to install a Hebrew font but ES File Manager doesn't seem to see the root folders. I'm having a hard time googling my way out of this one, bu all the other little issues were fairly simple.
One issue that I will mention that was hard to solve was the inability to perform searches in the Market. This page helped me resolve that issue:
blog.the-ebook-reader . com/2011/07/15/rooted-nook-touch-fixing-market-search-and-other-tips-and-tricks-video/
I just figured out that the file manager has to have Root permissions enabled. I've enabled it and added some fonts to /system/fonts but I still cannot get Hebrew text to display on this device. All I get are the typical rectangles instead of characters. Any ideas about how to proceed?
Thanks.
Restore Nook 1.1.2
roustabout said:
Many people have made the backup but not tested it; when they tried to restore, they did bad to fatal things to their devices. A very common failure on restore .
Click to expand...
Click to collapse
1. I made this exact same mistake yesterday and I ended up with a bad backup.
2. My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempted to restore the backup (which I didnt know was bad at the time)
3. Please help me restore the Nook back to factory or any working state. Are there any restorable backup images that can be downloaded online?
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)
bubblewrapper said:
1. I made this exact same mistake yesterday and I ended up with a bad backup.
2. My Nook Simple Touch (1.1.2) is now not working because I wiped ALL the partitions before attempted to restore the backup (which I didnt know was bad at the time)
3. Please help me restore the Nook back to factory or any working state. Are there any restorable backup images that can be downloaded online?
p.s. I have tried touchnooter and installed touchformatv2 but all I get now is a Read Forever load screen.
Please Please Help Me Im so sad (I know this is down to carelessness on my part but I really need help)
Click to expand...
Click to collapse
Few people who will be knowledgeable will find your post buried here under this thread. i suggest that you simply start a new thread with a good descriptive title so that the gurus will find it.
Not sure how to get hebrew working. One assumes that in addition to the characters, you need it to right to left? If it's the latter, I know there was a thread discussing doing this with Arabic, and I'm not sure how that turned out. You can also google around for folks looking at this on, I think, mobilereads.
roustabout said:
Not sure how to get hebrew working. One assumes that in addition to the characters, you need it to right to left? If it's the latter, I know there was a thread discussing doing this with Arabic, and I'm not sure how that turned out. You can also google around for folks looking at this on, I think, mobilereads.
Click to expand...
Click to collapse
Actually, I think that I just need the fonts (or at least that would be a great first step). I put fonts with Hebrew glyphs in /system/fonts (using ES File Explorer in Root mode) but even after a restart it does not find the fonts (i.e. Hebrew text still shows as rectangles). I will fight with it some more in the coming days, if I don't succeed I will start a new, concise thread on the topic. There are plenty of Google posts on the subject, but all of the ones that I have seen (not Nook-specific) suggest that dropping the fonts is /system/fonts should be enough. Perhaps it is a permissions issue, I'll see if I can SSH into the device to see permissions.
dotancohen said:
I have a Nook Simple Touch Glowlight with software verion 1.1.5. All the information that I've been able to Google is for 1.1.2, in fact that is the version that I still see on the B&N website.
I _think_ that I have found a suitable way to root the device with Nooter but I would like to know how to confirm that in fact this is the right project for my software version. I'm sorry that I cannot post a link to the Nooter project, but I have less than 10 posts.
Thanks.
Click to expand...
Click to collapse
Sorry that I am so slow to respond, but I think this is the information you need to root a Nook with Glow on version 1.1.5
It uses Glownooter
http://blog.the-ebook-reader.com/20...using-glownooter-includes-googles-app-market/
and this is the backup routine
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
ladykayaker said:
Sorry that I am so slow to respond,
Click to expand...
Click to collapse
Thank you! You don't need to apologize for taking time to respond, you are under no obligation! But I very much do appreciate your assistance and am happy to wait patiently! You will notice that I usually google issues first to try to save us both the time!
I think this is the information you need to root a Nook with Glow on version 1.1.5
It uses Glownooter
http://blog.the-ebook-reader.com/20...using-glownooter-includes-googles-app-market/
and this is the backup routine
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
Click to expand...
Click to collapse
Thank you. It seems that those posts are Windows-centric summerizations of information found here at XDA-developers. The root is pretty much the process that I used, but from the guide right here which has Linux directions as well.
By the way, the-ebook-reader site is often not responding for me. Is it just for me, or does everyone have trouble with that site?
Thanks!
version 1.2.0
UK glowlight ships with 1.2.0. Use tinynooter to root this. You may have issues installing apps atm though but you will get the browser at least.
http://forum.xda-developers.com/showthread.php?t=1961835
Thanks, Loney. In fact, I got this Glowlight in the US, and it reports that it has software verion 1.1.5. But the information will be good for others who might google this thread!
i am very sorry to ask this silly question
i found that i cannot use some apps on 4.2 , but the apps can be used on 4.1
thank you very much
Sent from my GT-I9300 using xda app-developers app
rooted or not?
not rooted
Sent from my GT-I9300 using xda app-developers app
then you're in a bit of a problem.....I was rooted and reverted back to 4.1 after I felt blowing my n7 with 4.2 up.
I don't know any other way apart from wiping it clean, which you could do by rooting it, which would save your apps + data
IF ANYBODY HAS BETTER KNOWLEDGE......PLEASE CHIME IN
This is what I did after I had the problem....root it, then backup all apps + data using titanium back up.....then copy the whole titanium backup folder to computer to save it all.....then reset back to 4.1.2, restore titanium backup, restore apps.....enjoy (and memo to self: if it ain't broken, don't fix it)
apart from rooting it I don't have any suggestions, sorry. wait for others if you want. Please note that this isn't a full proof method so I wouldn't like to be blamed for anything that goes wrong
ace9988 said:
then you're in a bit of a problem.....I was rooted and reverted back to 4.1 after I felt blowing my n7 with 4.2 up.
I don't know any other way apart from wiping it clean, which you could do by rooting it, which would save your apps + data
IF ANYBODY HAS BETTER KNOWLEDGE......PLEASE CHIME IN
This is what I did after I had the problem....root it, then backup all apps + data using titanium back up.....then copy the whole titanium backup folder to computer to save it all.....then reset back to 4.1.2, restore titanium backup, restore apps.....enjoy (and memo to self: if it ain't broken, don't fix it)
apart from rooting it I don't have any suggestions, sorry. wait for others if you want. Please note that this isn't a full proof method so I wouldn't like to be blamed for anything that goes wrong
Click to expand...
Click to collapse
thank you for answing
But the problem is that i do not know how to downgrade to 4.1.2
Sent from my GT-I9300 using xda app-developers app
4.2 hosed my N7 (FC's all over), I couldnt nandroid back, had to use the root kit and flash the 4.1.1 stock image (easy 10- minute fix). My SD was wiped so I suggest do a full back up of all your media before doing so.
phatmanxxl said:
4.2 hosed my N7 (FC's all over), I couldnt nandroid back, had to use the root kit and flash the 4.1.1 stock image (easy 10- minute fix). My SD was wiped so I suggest do a full back up of all your media before doing so.
Click to expand...
Click to collapse
Yea that tool kit really saved my butt a couple of times when I needed to back to stock android. I made sure to give a donation for the work he did.
phatmanxxl said:
4.2 hosed my N7 (FC's all over), I couldnt nandroid back, had to use the root kit and flash the 4.1.1 stock image (easy 10- minute fix). My SD was wiped so I suggest do a full back up of all your media before doing so.
Click to expand...
Click to collapse
Hi,
tell me if i understood correctly..... now that i have still 4.1.1 is better i do root, backup and nandbackup and after upgrade to 4.2, so in case of proobs i can come back.. is it right?
PS: actually my Nexus is completely empty
Which software u suggest, consider im no expert
Many thanks and sorry for my english
Ale
Take a look here
http://forum.xda-developers.com/showthread.php?p=34389960#post34389960
How to downgrade to 4.1.2 - very simple!
charlie135246 said:
i am very sorry to ask this silly question
i found that i cannot use some apps on 4.2 , but the apps can be used on 4.1
thank you very much
Sent from my Samsung GT-I9300 Galaxy SIIIusing xda app-developers app
Click to expand...
Click to collapse
I am a 11 Year old Girl and now i'll give you an instructions how to downgrade very easily.
I do already know the scams and battery problems with 4.2!
Question:Which OS do you have got on your Galaxy S3?
If you've got Android 4.0.4 IceCreamSandwich, then it sucks.
Ok, here is it=:
You need to have your device connected to the PC with a cable to follow this GUIDE.
For this you'll need a Cable which is still working without loose connection or so...
One end is a USB-Input like on USB-Stickers and the other end is MicroUSB and schould fit in your device.
Such a so-called „Micro-USB-Cable"
It is recommended to use an USB 2.0 input in order to avoid compatibility problems such as compatibillity problems with USB-3·0 or so. .... .
1.Download the best and most easy to use Nexus Toolkit (-- )made by a symphatic programmer- WugFresh.
WugFreshs Tooklit is even better than SkipSofts and has more features and even better!
Download it here [ „ http://www.WugFresh.Com/Nrt "], new version 1.8.7 released today. 9'o clock (09:22:51) in GMT+1
I had 1.8.4 and yesterday the 5th September, i did upgrade at 15:56:59 GMT+1 to 1.8.6..
Click to expand...
Click to collapse
2. Install this Program.
3.Download the Factory-Image of the Nexus 7 2012.
You cannot actually have the 2013-Version because the 2013-Version came out with 4.3 [Only-WiFi] and 4.3.1 on the Mobile 4G LTE-Version
IF you have got the only-WiFi-Version then take this link:https://developers.google.com/android/nexus/images?hl=de#nakasijzo54k (Choose JZO54K 4.1.2, too bad, Google did exclude 4.1.0;4.1.1;4.20;4.2.1;4.4.1Kot49e E)
IF you've got the Cellular Nexus 7, then it is not possible because unfortionally the cellular version was launched with 4.2.0!
Information:
FileName=nakasi-jzo54k-factory-973f190e.tgz"
Version: 4.1.2
Build:„JZO54K"
MD5·Checksum:„d906b505ccae0d439839d3c5fafb137a"
SHA·1-Chécksum:973F190e25cbafc29d9739fbe0ffb64ed8946946
[.]9b.Chéérs! Cheers?
http://forum.xda-developers.com/showthread.php?t=176647
http://forum.xda-developers.com/showthread.php?t=1766475
See my posts and WugFresh's answers on the last few pages by pressing the [>>] button on the page selection for more information.
4. You need to launch this program and press Auto·Detect Device+Build OS or so...
If this does not detect your device, then try choosing Device (Nexus 7 2012 WLAN or WiFi so-called...) and your Android-Version Manually.
5.[Backup]
To do a Backup with a device with not unlocked bootloader, then choose „Android Backup"
Do not select the both tickable options (Shared data and SysApps+Data backup) or it won't work.
Choose a location to save the ADB-File and wait until the device is unlocked, then unlock the screen and optionally you can type a password to crypt your backup.
Then start and wait.
Here it's recommended to use newer versions of this program. 1.8.4 was stuck at 92.495 MB or so. 1.8.6 worked fine for me so 1.8.7 will work fine too!
If the progress has finished, then the program will show you a Window with detailled Information. I did even upload a screenshot of this and it is on the official Wug thread on Page 440. Link is ^^^^ûp!^^^^^wards.
If your device has got an Unlocked Bootloader then just choose „[Full NºAndroid°Backup /W/]" and done. Just root in the main menu and... done!
Click to expand...
Click to collapse
6.Go to the devices settings menu and tap on „Storage", then tap on ⁞ and choose the USB-Option. Enable MTP and go to the Devices storage with your Computer on Windows Explorer.
Choose all files and if it says that the time lenght is being „Calculated" then it'sa just counting files, stay patient and wait!
7.
When even this finished then... well, you're ready, now you can Unlock the Bootloader!
I and my heart hate the factory data reset!
The only things that you can't actually be able of backing up are the Systen Settings, the Home Screen LayOut and the internal data of the System Apps.
Example:
Chrome History
Download History
YouTube Search History (if you've got an account, then online on your YouTube Account NOTHING will be changd!)
G·PlayStor Search History
(Google Drive Files will not be deleted from online!)
GMail Offline Sync (don't worry, anything still available online!
and etc.
Except of this, you'll actually loose Nothing!
Click to expand...
Click to collapse
After unlocking the bootloader you can finally root your device but this is not required for downgrading.
Now go to the Programs Home Screen and Load your Costum-ROM.
Use your about 256 MB big downloaded file for this.
The Original Name:„nakasi-jzo54k-factory-973f190e.tgz"
Size:268.416.146 Bytes
Size on Disk Drive(r):268.419.072b.
Windows Explorer shows the file as 255MB; FireFox as 256 MB.
And now you're..... Done!!!!!!!! ( )C o n g r a t u l a t i o n s ! ! ! ! ! [/FONT]
If you want to Relock your bootloader:
A.OEM Stock
B.Follow stéps
C.Done.
If the Backup is smaller than the App Data would be, then i don't know if the file contents are compressed or not... WugFresh won't answer (anymore) because he's probably tired of my (loooooooooooooooooooooooooooooooooooooooooong ( )) questions. I asked too much, my mistake. I asked if compressed or not... but still no answer there!
In this case read the official Nexus WugThrèad for more Important information.
I am doing the same steps but i downgrade from 4.4.2! This Colour for the Status-Bar Icon loox better than this!!!!!
:=Helpabilitty
:=
I hope that my yesterday's Post actually could help.
If it was too hard to understand for you or anybody else,
you (or everyone else) can ask me whenever you want.
Then i'm going to help you agian.
If my Information could not help again, then ask me.
But i hope i could help you.
And i hope that even non-professionals are able to understand what i worte in the last post of yesterday.
I wrote a long text in the last post and it did take 20 Minutes but well... no problem, if WugFresh is tired of answering questions (from my own experience) then what you can do is:
Simply ask me as many questions you want and i'll try to answer them all.
If i don't know the answer, then i simply search on the Internet!
But thanks for Reading my posts on this site, Danke.
Hoffentlich konnte ich dir behilflich sein!
Hannah Stern said:
:=
I hope that my yesterday's Post actually could help.
If it was too hard to understand for you or anybody else,
you (or everyone else) can ask me whenever you want.
Then i'm going to help you agian.
If my Information could not help again, then ask me.
But i hope i could help you.
And i hope that even non-professionals are able to understand what i worte in the last post of yesterday.
I wrote a long text in the last post and it did take 20 Minutes but well... no problem, if WugFresh is tired of answering questions (from my own experience) then what you can do is:
Simply ask me as many questions you want and i'll try to answer them all.
If i don't know the answer, then i simply search on the Internet!
But thanks for Reading my posts on this site, Danke.
Hoffentlich konnte ich dir behilflich sein!
Click to expand...
Click to collapse
The method is clear but.. the post is from 2012.. i think the OP has solved the problem or maybe he don't even has the n7...
Hey.
I have a question that is about sharing ROM's for our Galaxy S4 (GT-I9505). We all knows that the normal way of sharing a new ROM is to wait for a ROM maker / developer to release a new ROM with new modifications and stuffs.
But what i'm thinking on is another way of sharing current ROMs. What this is about is to install the ROM of your choice and theme / modify it like you want it and then take a whole Nandroid (TWRP) backup of the whole ROM and then compress the nandroid backup files you have on the SD card or internal memory into a RAR file and then upload it to a sharing webpage like MEGA, Google Drive or any other good sharing pages.
Now i'm not sure if this is possible / legal to do and if this kind of question is asked before. But would this work to share a ROM this way and then download the nandroid RAR file from others with the same phone as me and unzip it and put it on the SD card or whatever and then run a restore from the TWRP recovery on our phones?
Or is there other things that will make this impossible to do?
I'm sure this have been asked before, but i can't find anything about this by searching, so that's why i'm just making this topic where i'm asking about this.
And i hope this section was the right place to put this kind of question in?
Greetings from Tom-Helge.
Thing is, how do you leave the personal stuff/apps/app settings out & just keep the stuff you want ? (what stuff exactly are you wanting to share in this way? ?) I can't see how you'd do that. I mean, it wouldn't be a huge stretch for someone to put malicious apps in the nandroid. A lot of people don't even look @ Su toasts, they just hit grant without giving it a thought.
I think you need to explain what you're hoping to achieve out of all this a bit better, and why your way would be better/easier/whatever than the current way people do things.
Edit - Also, I think what I'm getting at is, the way things are at the moment, people have complete control over what goes on their phone. You have to flash a rom/kernel/mod/whatever, and you decide what theme you want, what apps/app settings you want. I can't really see the appeal of what you've proposed in the way you've initially explained it at least (though that may change if you explain it a bit more fully).
MistahBungle said:
Thing is, how do you leave the personal stuff/apps/app settings out & just keep the stuff you want ? (what stuff exactly are you wanting to share in this way? ?) I can't see how you'd do that. I mean, it wouldn't be a huge stretch for someone to put malicious apps in the nandroid. A lot of people don't even look @ Su toasts, they just hit grant without giving it a thought.
I think you need to explain what you're hoping to achieve out of all this a bit better, and why your way would be better/easier/whatever than the current way people do things.
Edit - Also, I think what I'm getting at is, the way things are at the moment, people have complete control over what goes on their phone. You have to flash a rom/kernel/mod/whatever, and you decide what theme you want, what apps/app settings you want. I can't really see the appeal of what you've proposed in the way you've initially explained it at least (though that may change if you explain it a bit more fully).
Click to expand...
Click to collapse
Well, it's a more easier way of getting a themed / modified ROM that already exist that might suit you better and might save you alot of time to configure the ROM.
It's pretty much the same way of making a ROM of your choice as the ROM developers do. The ROM developers choose what they want to have in their ROMs and how they want to theme it. While this is sharing a modified ROM after you have installed that existing ROM on your phone.
The concept would be in the same way as the Themer Beta app is. There you can download preconfigured themes and use them the way they are or change them a little after you have downloaded them.
And as for putting malicious apps into the nandroid backups, it would be easy to find out if someone does that and if this type of sharing would be possible and allowed to do here, then the devs always have the banhammer to bust those who have bad intentions towards others here.
I hope this clears a bit more up on what i'm asking after .
EDIT: As for the personal stuffs on your ROM. The way i'm thinking is to install a ROM of your choice and then only modify / theme it the way you want it and leave out the personal stuffs until later when you have created the nandroid backup. Or you could simply remove the accounts and the personal stuffs from the ROM before you creates a backup to.
Ahhh OK, I'm with you now. Still seems like a really convoluted way of doing things to me though. Some people might like it, but if you're the sort of person who roots/mods your phone for the control you have over it, I'm not seeing how a person would be interested in what you're proposing. The people most interested would be people who are time poor or, more likely, people who are too lazy to set their phone up themselves.
MistahBungle said:
Ahhh OK, I'm with you now. Still seems like a really convoluted way of doing things to me though. Some people might like it, but if you're the sort of person who roots/mods your phone for the control you have over it, I'm not seeing how a person would be interested in what you're proposing. The people most interested would be people who are time poor or, more likely, people who are too lazy to set their phone up themselves.
Click to expand...
Click to collapse
Well, it will work. The only thing we have to make sure is to not include any apps that cost money to buy. That's very important.
Like now, i can just take a whole nandroid backup of my current OS as it is now. After that i could just remove any apps that's not needed to be included and then remove all of the accounts and stuffs.
When the ROM is like i want it to be, then i can make a new nandroid backup of the ROM i want to share and then just upload it and share it. Then peoples can download that and run a restore from TWRP recovery and install it. After that i can just return to my main ROM that i took a backup of before i started to modify the ROM to be shared.
So if peoples likes the way i have set up my ROM and want to use that, then they will download my nandroid backup.
Ofc, the peoples that downloads my nandroid backup needs to install the other applications they like that's not included in the nandroid backup.
But yeah, it will work, but it really depends on how much interesting this will be to others.
If peoples are intrested in this, then we can make a topic about this and when we share a nandroid backup, then we have to specify what ROM we use, what apps that are included and have several screenshots from how the ROM is looking and so on.
Sooo
Android Go is made for low-end devices with 1 gig or less of RAM right ?
Could/Would someone please port it when possible ? It would be really cool if our beloved 2009 phone could run new software.
It probably required newest google play services which could kill all resources. Hopefully someone will confirm that I'm not right.
Meanwhile I have installed oldest possible facebok lite and skype lite, etc... from apkmirror.
It works some way.
I know someone who ported Oreo to hd2, but almost nothing workded. He doesnt have the rom now
Dominduchami said:
I know someone who ported Oreo to hd2, but almost nothing workded. He doesnt have the rom now
Click to expand...
Click to collapse
And how come the only person able to boot Oreo on this magically lost the rom in limbo?
C'mon now. A zip is never lost, unless you write over it.
He should have had to re-write whole GBs to write over the place the rom was stored in.
You can simply use Recuva, Easeus, etc. and dig up the file after you've deleted it accidentally.
This whole community would be more than happy to have it, even completelly broken. If it boots, there is hope it could be fixed.
So, tell that person to use those programs and try to recover it.
It might have not been overwritten yet.
Myrmeko said:
And how come the only person able to boot Oreo on this magically lost the rom in limbo?
C'mon now. A zip is never lost, unless you write over it.
He should have had to re-write whole GBs to write over the place the rom was stored in.
You can simply use Recuva, Easeus, etc. and dig up the file after you've deleted it accidentally.
This whole community would be more than happy to have it, even completelly broken. If it boots, there is hope it could be fixed.
So, tell that person to use those programs and try to recover it.
It might have not been overwritten yet.
Click to expand...
Click to collapse
He said he will do that later. I will try to compile the rom myself from source in few days. But i cannot promise anything.
Dominduchami said:
He said he will do that later. I will try to compile the rom myself from source in few days. But i cannot promise anything.
Click to expand...
Click to collapse
Ok, that's dope. Thanks.
Hopefully it works.
If it boots, even if nothing else works, just post it in this forum anyway. People will start fixing stuff.