If I'm getting a new note. Can I restore a Nandroid of the rom from my old note to the new one to keep everything in tact or us that gonna mess stuff up?
Sent from my SAMSUNG-SGH-I717 using xda premium
ctraywick1 said:
If I'm getting a new note. Can I restore a Nandroid of the rom from my old note to the new one to keep everything in tact or us that gonna mess stuff up?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I would say right off the bat...Yes...your gonna mess stuff up....
why not use titanium backup paid...which is great, you can save all your setting/data/apps....then if your going to run the same ROM, on your new Note...just copy the titanium backup folder from your old Note to your new Note... and put tibu on your new Note...hit restore...btw the paid is great due to you capabilities of run batch backup and restorations...among lots of other items ...Tibu is a very powerful tool for any android smartphone...
check it out...
I think his goal is to clone his phone. Not for samsung even if it is the same exact model.
Samsung phones have an encrypted file that generates the phone IEMI. If you nandroid, that folder and file go to the second phone and your phone ends with no (or a generic) IEMI.
There are better ways to restore a new phone.
Edit: I did this with an AOSP ROM without issue. Even though everything seemed fine, I wouldn't suggest doing it. I know setting up the phone is a PITA, but the extra time it takes is well worth it considering the problems that may arise from restoring a nandroid to the same model phone.
bigjoe2675 said:
I would say right off the bat...Yes...your gonna mess stuff up....
why not use titanium backup paid...which is great, you can save all your setting/data/apps....then if your going to run the same ROM, on your new Note...just copy the titanium backup folder from your old Note to your new Note... and put tibu on your new Note...hit restore...btw the paid is great due to you capabilities of run batch backup and restorations...among lots of other items ...Tibu is a very powerful tool for any android smartphone...
check it out...
Click to expand...
Click to collapse
Yea i have the paid version so i could just do it like that and treat it like a new rom. Just restore my apps from tibu, sms/ call logs with mybackup pro, and just use my launcher/messaging theme and setup . So all i have to manually restore are my system settings. Thanks
rangercaptain said:
I think his goal is to clone his phone. Not for samsung even if it is the same exact model.
Samsung phones have an encrypted file that generates the phone IEMI. If you nandroid, that folder and file go to the second phone and your phone ends with no (or a generic) IEMI.
There are better ways to restore a new phone.
Click to expand...
Click to collapse
Didnt know that about the encrypted files,thanks for the warning. You were right I just wanted to be lazy and "clone my phone"
froidroid said:
Edit: I did this with an AOSP ROM without issue. Even though everything seemed fine, I wouldn't suggest doing it. I know setting up the phone is a PITA, but the extra time it takes is well worth it considering the problems that may arise from restoring a nandroid to the same model phone.
Click to expand...
Click to collapse
Point well taken
Sent from my SAMSUNG-SGH-I717 using xda premium
rangercaptain said:
I think his goal is to clone his phone. Not for samsung even if it is the same exact model.
Samsung phones have an encrypted file that generates the phone IEMI. If you nandroid, that folder and file go to the second phone and your phone ends with no (or a generic) IEMI.
There are better ways to restore a new phone.
Click to expand...
Click to collapse
i am certain nandroids DO NOT contain the /efs folder... back in the captivate days you had to do a manual backup of that folder in case your IMEI (M comes before the E btw) got messed up you could restore it with that backup... if a nandroid contained that, then that backup step would have been superfluous.
On top of that... nandroids don't even contain the fuggin modem...why would they have the phone specific information that you should NEVER even touch in the first place?
studacris said:
i am certain nandroids DO NOT contain the /efs folder... back in the captivate days you had to do a manual backup of that folder in case your IMEI (M comes before the E btw) got messed up you could restore it with that backup... if a nandroid contained that, then that backup step would have been superfluous.
Click to expand...
Click to collapse
Are you certain enough to let what you say brick someone's phone? I don't think you or I are enough of an expert to make that assertion.
From Rootswiki forum:
This question comes up in a lot of forums because some people think we should be able to just copy the whole package from one phone to another like we can on computers. Unfortunately almost every piece of software on phones is installed in such a way that it is inextricably tied to that particular piece of hardware. Nandroid and other backups only work on the phone they were made.
At code.google.com the consensus was don't do it.
I got the /efs folder detail from Samsung support. Its within the /system folder -- why would you think it gets skipped during backup? And the messed up IEMI number is a very common outcome. Just look around in other galaxy s class phone forums.
From TiBU FAQ's:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And your concern about the frakkin modem -- that code isn't in the modem, its in the nvdata file (the encrypted one I mentioned) in the /efs folder.
@ctraywick1:
Don't follow advice that could ruin your phone when there are only opinions not facts available.
Just develop a good backup strategy so migrating to a new rom or phone is less painful.
My point about the modern was not that IT contained the IMEI, i know perfectly well where it is, in fact better than you (see below lol). it was the fact that you flash modems all the time and yet they are not contained in s nandroid, so...why would non volatile data like that be included...
And the efs folder is most certainly NOT IN the /system directory...that would be retarded as that directory gets COMPLETELY FORMATTED with every Rom flash.
IT'S IN THE ROOT DIRECTORY
studacris said:
My point about the modern was not that IT contained the IMEI, i know perfectly well where it is, in fact better than you (see below lol). it was the fact that you flash modems all the time and yet they are not contained in s nandroid, so...why would non volatile data like that be included...
And the efs folder is most certainly NOT IN the /system directory...that would be retarded as that directory gets COMPLETELY FORMATTED with every Rom flash.
Click to expand...
Click to collapse
Why are you making such a big deal about this? The OP just wanted advice and I can find 100 posts that say don't copy your nandroid to another phone. Because we are dealing with a $600 device the wisest thing to do is say "don't do it" and help him develop a usedul backup strategy. What are you doing to further that goal? I gave several experts and you only offer your opinion. Thats just not good enough even if you are the smartest guy in the room.
And your own picture says you're mistaken about the flashing and rewriting. Look at the date of your /efs folder. I'm sure your phone is more than two days old. My stock phone has May 6 2012 date created.
Yes, I was wrong about the location, but the advice is still his best course. Experiment on your own phone.
Lol you come back with false information...i correct it.. Not "making a big deal", but i will not be corrected with information that is not accurate.
A nandroid is not the "whole phone"
As i said, it does not contain a modem, also doesn't contain your bootloaders, your sdcards/emmc, or the /efs folder.
And since it doesn't contain bootloaders there is no chance of hard bricking anything.
I didn't condone nor endorse anything either...Just saying the IMEI is not in a nandroid, that 's all
Yeah, I'm no expert just an enthusiast. Thats why I got the TiBu screenshot that said "whole phone". I guess they are giving incorrect information.
Your screenshot contradicts you -- look at the /efs folder date.
Oh.. That's cause i was experimenting with some stuff inside there, just goofing around and looking through it really, and even though it was a copy i was messing with... i copied back a known untouched version just out of ocd.
Well anyway I don't think it matters to you but I enjoy your posts and repect your opinions.
You add a lot of value to xda.
studacris said:
Oh.. That's cause i was ... i copied back a known untouched version just out of ocd.
Click to expand...
Click to collapse
Related
I keep seeing talk about "DON'T USE ROM MANAGER" it is causing issues right now in MANY DIFFERENT THREADS. Just wanted to show anyone that has issues with rom manager and how it worked for me. I have used rom manager to download roms (CM7), and also run BACKUPS from rom manager. So Rom Manager does work without issue for CM7, and still works well with any other rom for our ATT SGS2's with one little catch which is very easy to do. I know the video is not the greatest quality as I used my old cappy to record running rom manager as a backup. So if this helps you out great. If not know big deal, just thought I would try to help.
https://www.youtube.com/watch?v=o9JwYtDC4rA&feature=youtube_gdata_player
Sent From My KICKASS CM7 AT&T SGS2
Can you post what that one little catch is, instead of making us watch a 6 minute video?
re: rom manager
RockRatt said:
I keep seeing talk about "DON'T USE ROM MANAGER" it is causing issues right now in MANY DIFFERENT THREADS. Just wanted to show anyone that has issues with rom manager and how it worked for me. I have used rom manager to download roms (CM7), and also run BACKUPS from rom manager. So Rom Manager does work without issue for CM7, and still works well with any other rom for our ATT SGS2's with one little catch which is very easy to do. I know the video is not the greatest quality as I used my old cappy to record running rom manager as a backup. So if this helps you out great. If not know big deal, just thought I would try to help.
https://www.youtube.com/watch?v=o9JwYtDC4rA&feature=youtube_gdata_player
Sent From My KICKASS CM7 AT&T SGS2
Click to expand...
Click to collapse
Why mess with something which can only cause grief to most people.
Best to wait for a new update of it which is fully compatible with our
phones and all the custom roms.
Until then here is a very good substitude which include many of the
same features and options as rom manager and is 100% compatible.
Check it out!
CWM Manager can be downloaded here: http://megaupload.com/?d=TGXMLL1G
It's very easy to use because its fully self-explanitory.
jetarpon said:
Can you post what that one little catch is, instead of making us watch a 6 minute video?
Click to expand...
Click to collapse
It is when the phone first goes to reboot to recovery that it will go to a black screen with a symbol on it, when you see that screen you just hold down the three button salute until screen goes black, then let go of the buttons, the backup process will begin where it should be and create your backups.
Rom manager is NO GRIEF at all and MOST know of it and how it works. This is a VERY EASY workaround rather than having another app to install to do the same exact things. But I guess there are people that cannot read instructions and follow so I SHOWED how it is done. But when you see people saying it didn't work for them on different post because they are not familiar enough to use it. I am not pointing you out MrJunky but I ha e seen you post this over and over again. I am just trying to help those out that may need it.
Hopefully others can see HOW EASY it is with a video to backup their roms (ANY ROM), then how to go about switching between backed up roms very easily. This way they can test out DGs roms, Unnamed rom, CM7, or any other rom without the fear of screwing up anything. So that is why the video shows How To BACKUP and how to SWITCH between different roms via your backups.
Sent From My KICKASS CM7 AT&T SGS2
So, your "ROM Manager" workaround was to trigger entry into the standard non-broken non-ROM-Manager recovery?
You use the three-finger, you are no longer using ROM Manager.
This is why we tell people not to use ROM Manager. Your method is harder than simply using the three-finger from poweroff, or if you've got a custom ROM, the Recovery option from reboot menu.
Yes the workaround is slightly different as once your phone starts to boot up and goes to the screen you hold down the three buttons. I only did this because I saw others that were pulling the battery since they thought they were stuck. The plus is when using rom manager to backup the current rom you can easily name it via rom manager and.once it is backed up and rebooted you can see the name you picked stuck. I know how to JUST use the three button salute and backup right from cwm, this is.just a workaround for someone wanting to use rom manager. And it.is not any harder than JUST using the three button. It is basically the same except it allows you to use rom manager and name the backed up rom before actually backing it up. This has helped.me.in the past when I made a backup from cwm within the same day for two different roms. I wasn't sure which one was which. So I didn't want to JUST try to rename them after the fact. Yes it is NOT a big deal here but it does work. I know you do great.things for this community, and I am no dev so I am not trying to argue any points with you. I am just showing that.it can work with ease. Plus RM works perfect with CM7 without having to do the three button workaround to get rom manager to work. So what.is it that would allow CM7 use.rom manager correctly yet the stock based Samsung roms not work without a workaround?
Sent From My KICKASS CM7 AT&T SGS2
re: rom manager
RockRatt said:
Yes the workaround is slightly different as once your phone starts to boot up and goes to the screen you hold down the three buttons. I only did this because I saw others that were pulling the battery since they thought they were stuck. The plus is when using rom manager to backup the current rom you can easily name it via rom manager and.once it is backed up and rebooted you can see the name you picked stuck. I know how to JUST use the three button salute and backup right from cwm, this is.just a workaround for someone wanting to use rom manager. And it.is not any harder than JUST using the three button. It is basically the same except it allows you to use rom manager and name the backed up rom before actually backing it up. This has helped.me.in the past when I made a backup from cwm within the same day for two different roms. I wasn't sure which one was which. So I didn't want to JUST try to rename them after the fact. Yes it is NOT a big deal here but it does work. I know you do great.things for this community, and I am no dev so I am not trying to argue any points with you. I am just showing that.it can work with ease. Plus RM works perfect with CM7 without having to do the three button workaround to get rom manager to work. So what.is it that would allow CM7 use.rom manager correctly yet the stock based Samsung roms not work without a workaround?
Sent From My KICKASS CM7 AT&T SGS2
Click to expand...
Click to collapse
Why not just avoid all the hassles in the first place?
Rom Manager is not the only app which can do nandroid backup/restore,
rename, delete, flash roms and kernels and much more.
(and yes it asks for filename BEFORE backing up existing rom)
For example here is an app called CWM Manager which can do all that stuff
and more without 3 finger salute or any hassle at all.
cwm manager: http://megaupload.com/?d=TGXMLL1G
About the only thing it's lacking when compared to rom manager is that
it cannot download roms or anything else.
Personally I think that for the majority of users its a lot less complicated to use than Rom Manager.
Check it out yourself.
Are there any other apps that are similar to this? My issue is that I can't backup to my ext SD which is significantly larger, 32class10.? Or is the a mod so I can mount my ext SD as the main storage? That way all apparently recognize my sdext?
Sent from my SAMSUNG-SGH-I777 using xda premium
I don't understand why so many people are tied to Rom Manager. It's not that great of a tool and honestly I'm happier without it. What's the point of trying to make it work to such a degree? Maybe I'm missing something but if it never works properly, I'll be perfectly fine with it.
jgrimberg1979 said:
Are there any other apps that are similar to this? My issue is that I can't backup to my ext SD which is significantly larger, 32class10.? Or is the a mod so I can mount my ext SD as the main storage? That way all apparently recognize my sdext?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Just do the backup and then move it from the internal over to your ext. Or are you out of space as it is to where you can't even do a backup to begin with?
Kadin said:
I don't understand why so many people are tied to Rom Manager. It's not that great of a tool and honestly I'm happier without it. What's the point of trying to make it work to such a degree? Maybe I'm missing something but if it never works properly, I'll be perfectly fine with it.
Dude I am not tied to it, its just that much easier! Ex. a. there is a grocery store 1 miles down the street and very easy to walk to b. on the other hand i have a car in my drive way ready to be use and i could get back so much quicker.. What choice would 99.9% of people use? Obviously b. Rom managers makes it easy to make nandroids and restore, everthing is automated. I can just "set it and forget it". Installing zips is nice because i paid for the premium version so i can flash as many zips as i wont in one swop. You would be lying if you said you prefer booting into to recovery and manually flashing or backups or restores, rather than just hitting backup or restore etc. Also it is nice because you can name your backups before you backup it up.
I am not out of space but i will be soon. I just got the phone and i have 5 gigs left (that is 2 days of use) . Moving the backups manually to the ext is such a pain and the ass. Is there alternatives out there to rom manager besides CWM Manager?
Click to expand...
Click to collapse
jgrimberg1979 said:
Dude I am not tied to it, its just that much easier! Ex. a. there is a grocery store 1 miles down the street and very easy to walk to b. on the other hand i have a car in my drive way ready to be use and i could get back so much quicker.. What choice would 99.9% of people use? Obviously b. Rom managers makes it easy to make nandroids and restore, everthing is automated. I can just "set it and forget it". Installing zips is nice because i paid for the premium version so i can flash as many zips as i wont in one swop. You would be lying if you said you prefer booting into to recovery and manually flashing or backups or restores, rather than just hitting backup or restore etc. Also it is nice because you can name your backups before you backup it up.
I am not out of space but i will be soon. I just got the phone and i have 5 gigs left (that is 2 days of use) . Moving the backups manually to the ext is such a pain and the ass. Is there alternatives out there to rom manager besides CWM Manager?
Click to expand...
Click to collapse
I wasn't referring to you actually, was more with regards to the thread itself and so many that are like it. That's why I stated it before I then quoted you and gave my input.
I find it simple to copy them over and renaming them is easy as well. Obviously it would be ideal for many people but personally it's not a big deal - that's all I'm saying.
SIMULAR to Rom Manager
jgrimberg1979 said:
Are there any other apps that are similar to this? My issue is that I can't backup to my ext SD which is significantly larger, 32class10.? Or is the a mod so I can mount my ext SD as the main storage? That way all apparently recognize my sdext?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Why not just avoid all the hassles in the first place?
Rom Manager is not the only app which can do nandroid backup/restore,
rename, delete, flash roms and kernels and much more.
(and yes it asks for filename BEFORE backing up existing rom)
For example here is an app called CWM Manager which can do all that stuff
and more without 3 finger salute or any hassle at all.
cwm manager: http://megaupload.com/?d=TGXMLL1G
About the only thing it's lacking when compared to rom manager is that
it cannot download roms or anything else.
Personally I think that for the majority of users its a lot less complicated
to use than Rom Manager. (because it's self-explanitory)
This app is 100% compatible with CWM Recovery too.
Check it out yourself.
Misterjunky said:
Why not just avoid all the hassles in the first place?
Rom Manager is not the only app which can do nandroid backup/restore,
rename, delete, flash roms and kernels and much more.
(and yes it asks for filename BEFORE backing up existing rom)
For example here is an app called CWM Manager which can do all that stuff
and more without 3 finger salute or any hassle at all.
cwm manager: http://megaupload.com/?d=TGXMLL1G
About the only thing it's lacking when compared to rom manager is that
it cannot download roms or anything else.
Personally I think that for the majority of users its a lot less complicated to use than Rom Manager.
Check it out yourself.
Click to expand...
Click to collapse
When I rename a ROM BACKUP in CWM Manager before backing it up then try to restore it, it can't find it. It just shows a blank restore screen. For some reason renaming it doesn't work for me. Just using the default name (date and time) works but custom names do not. That is a major issue, at least for me.
OTOH I don't like having to do the 3 finger salute .... both have their problems.
You realize you have posted the exact same message 3 times in this thread. that has only 13 messages. Are you on their payroll?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MisterEdF said:
When I rename a ROM BACKUP in CWM Manager before backing it up then try to restore it, it can't find it. It just shows a blank restore screen. For some reason renaming it doesn't work for me. Just using the default name (date and time) works but custom names do not. That is a major issue, at least for me.
OTOH I don't like having to do the 3 finger salute .... both have their problems.
Click to expand...
Click to collapse
You simply have to rename it without any spaces. You can use periods and dashes but if you put in any spaces, it won't find them.
Kadin said:
You simply have to rename it without any spaces. You can use periods and dashes but if you put in any spaces, it won't find them.
Click to expand...
Click to collapse
Ahhh, a simple (but not obvious) solution! Thanks.
MisterEdF said:
When I rename a ROM BACKUP in CWM Manager before backing it up then try to restore it, it can't find it. It just shows a blank restore screen. For some reason renaming it doesn't work for me. Just using the default name (date and time) works but custom names do not. That is a major issue, at least for me.
OTOH I don't like having to do the 3 finger salute .... both have their problems.
Click to expand...
Click to collapse
That's because when you change the default date/time name you
must have given it some name which contains some charactor(s)
which cwm manager cannot reconize or you changed the location
of the backed up rom to a different location than where it was saved to.
Proper location for backup is: ( sdcard/clockworkmod/backup ).
Then inside the backup folder is where the default or user named
backup folders containing the backup set of files needs to reside.
MisterEdF said:
When I rename a ROM BACKUP in CWM Manager before backing it up then try to restore it, it can't find it. It just shows a blank restore screen. For some reason renaming it doesn't work for me. Just using the default name (date and time) works but custom names do not. That is a major issue, at least for me.
OTOH I don't like having to do the 3 finger salute .... both have their problems.
You realize you have posted the exact same message 3 times in this thread. that has only 13 messages. Are you on their payroll?
Click to expand...
Click to collapse
LOL, no ****
So even though I have been s-off since the Panda hit the scene, I think those that have yet to unlock/root might REALLY like to know this.
Basically you can create a back up using ADB on your NON-ROOTED device. Unlock/Root (which we all know will require a factory reset when using HTCDev Unlock) and then with your freshly rooted device, you can restore from the ADB backup you create.
I haven't tried this out yet (just got the update and attached change log) but might try it out just to see. Lucky for me all the devices I support have been Panda *certified but this will be real handy if I have to deal with a un-s-off-able device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my EVO using xda premium
I was gonna post this, beat me to it haha. It's a nice feature for those s-on
Sent from my EVO using Tapatalk 2
That's one of the very first apps I ever bought, almost 3 years ago. The dev is great. He always responds to emails quickly. I'm glad this was added. I don't need it (yet), but this is definitely a nice feature.
Cool - I wish this had been in the program a few months ago when I did the unlock.
I did the ADB backup/restore manually but this would be a lot easier.
metalfan78 said:
That's one of the very first apps I ever bought, almost 3 years ago. The dev is great. He always responds to emails quickly. I'm glad this was added. I don't need it (yet), but this is definitely a nice feature.
Click to expand...
Click to collapse
Yeah man, the FIRST and only app I "require" someone purchase if I'm working on a phone is TB. If you never buy another app, TB is the single best investment you can make if you are rooting your phone and this just add more "goodness" to the pile. :good::good:
metalfan78 said:
That's one of the very first apps I ever bought, almost 3 years ago. The dev is great. He always responds to emails quickly. I'm glad this was added. I don't need it (yet), but this is definitely a nice feature.
Click to expand...
Click to collapse
I was gonna say the same. I noticed one day that TiBu wasn't being granted SU just out of nowhere. I emailed Joel, he emailed me back in less than an hour with exactly the fix. (I think it was 'force system busybox' from TI settings). Guy is awesome.
I'm not sure how you perform adb backup. Would be curious to know.
from my flying AOKP'd Evo LTE and xda premium
scottspa74 said:
I was gonna say the same. I noticed one day that TiBu wasn't being granted SU just out of nowhere. I emailed Joel, he emailed me back in less than an hour with exactly the fix. (I think it was 'force system busybox' from TI settings). Guy is awesome.
I'm not sure how you perform adb backup. Would be curious to know.
from my flying AOKP'd Evo LTE and xda premium
Click to expand...
Click to collapse
Good and Evo did a write up on how to do it. I haven't tried it BUT you can find the instructions here >>>>> http://goo.gl/9rr8N
Sent from my EVO using xda premium
I recently bought the pro version of this app strictly for this feature. Thus far, I have been unable to get it to work. I've tried two different .ab files both of which have been successfully restored from using UBT. Any suggestions or ideas why TB pro would say the .ab files are invalid?
Thanks!
Ryan
Hi Ryan,
Is your backup file password protected (encrypted) or not?
Also please do (on the device or in a unix shell):
busybox head -n4 MyBackupFile.ab
and please post the result...
hmm. didnt see that. I'll have to give it a try
joel.bourquard said:
Hi Ryan,
Is your backup file password protected (encrypted) or not?
Also please do (on the device or in a unix shell):
busybox head -n4 MyBackupFile.ab
and please post the result...
Click to expand...
Click to collapse
Another reason this app is the $hit! The dev of this essential app checking boards and popping in to help directly.
I'm about to try this out on a new white EVO LTE so we'll see how easy this goes.
Great news. Would be even greater if we could do it direct to a computer?
Maybe possible by mounting a network share? Would need to find a way to check the backup has worked though.
Or maybe this can be done with adb pull?
My phone went into boot-loop a week or so ago and this feature of TiB saved the day. I could not boot the normal OS to make a backup and had no recent backup. Reflashing my rom and wiping cache & dalvik made no difference. But I made a nandroid from TWRP, factory reset, then was able to restore my txt's from the nandroid using TiB (dialer storage) all right on the device while out to dinner. Damned nice.
Sent from my EVO using xda premium
Ironically, I'd been using the free version of TB for quite a while... but recently bought Pro because I found it to be so useful...
Did anyone fix the AB issue in titanium backup?
When trying to use this feature, tianium backup is not letting me select the .ab file. The file appears greyed out.
The backup file is encrypted.
I ran "busybox head -n4" on my .ab file and got the following -
ANDROID BACKUP
4
1
AES-256
Any ideas?
Edit: I managed to force select the file using another file manager only to be greeted by a message from titanium backup stating the backup file is either invalid or unsupported.
@joel.bourquard
ms.goofy said:
When trying to use this feature, tianium backup is not letting me select the .ab file. The file appears greyed out.
The backup file is encrypted.
I ran "busybox head -n4" on my .ab file and got the following -
ANDROID BACKUP
4
1
AES-256
Any ideas?
Edit: I managed to force select the file using another file manager only to be greeted by a message from titanium backup stating the backup file is either invalid or unsupported.
@joel.bourquard
Click to expand...
Click to collapse
Hi,
Feel free to try with TB 7.6.1, it should work
joel.bourquard said:
Hi,
Feel free to try with TB 7.6.1, it should work
Click to expand...
Click to collapse
Thanks for fixing it. It works now. Though I need to use a third party file manager app to select the .ab file.
Does this mean it's somehow possible to backup directly to a PC via USB, instead of backing up to an SD? I have destroyed 2-3 SD so far by heating them up to much while doing long backup/restore
I have had it I have deleted all my photos AGAIN!!! I can't seem to see why KitKat made the Ext-SD Read Only : (ie photos in the internal memory) : WHY can't we access the internal memory from any of the recoveries and with all the other problems associated with the LB that we are all familiar with this is a really bad phone to root.
How did this happen ?
I downloaded a new ROM, made sure my phone had them both the ROM and the Dual Recovery flashable file on the SD and rebooted to TWRP. I then wiped out my everything but external and internal SD. After doing this I went to flash the ROM but couldn't find it (I know it was there but buried in one of the million sub directories.) Next I was interrupted at the door by my boss, we got to talking and I realized that my screen was off. When I returned the phone was in fact dead. #$#@ I screamed out loud because I knew what this meant. Despite my knowledge of how this operates I knew from experience loosing all my wedding photos that this wasn't going to go over well (read my previous thread of lost wedding photos).
Why even recommend rooting to anyone with a locked boot loader after all this is a phone people buy to use the camera. The photos are forced by default to internal memory and internal memory is extremely volatile on this phone
HAS ANYONE OUT THERE been able to get the data back I simply have no system/recovery partition now ?! Surely SOMEONE out there knows of a way to .ftf a system partition only so I can access my internal memory as the data partition is still fully intact..
If not I wont be surprised as this LB phone (camera) is a total disaster for me and I am regretting getting it in the first place... It's a real mess with these glitches ..
futiless said:
I have had it I have deleted all my photos AGAIN!!! I can't seem to see why KitKat made the Ext-SD Read Only : (ie photos in the internal memory) : WHY can't we access the internal memory from any of the recoveries and with all the other problems associated with the LB that we are all familiar with this is a really bad phone to root.
How did this happen ?
I downloaded a new ROM, made sure my phone had them both the ROM and the Dual Recovery flashable file on the SD and rebooted to TWRP. I then wiped out my everything but external and internal SD. After doing this I went to flash the ROM but couldn't find it (I know it was there but buried in one of the million sub directories.) Next I was interrupted at the door by my boss, we got to talking and I realized that my screen was off. When I returned the phone was in fact dead. #$#@ I screamed out loud because I knew what this meant. Despite my knowledge of how this operates I knew from experience loosing all my wedding photos that this wasn't going to go over well (read my previous thread of lost wedding photos).
Why even recommend rooting to anyone with a locked boot loader after all this is a phone people buy to use the camera. The photos are forced by default to internal memory and internal memory is extremely volatile on this phone
HAS ANYONE OUT THERE been able to get the data back I simply have no system/recovery partition now ?! Surely SOMEONE out there knows of a way to .ftf a system partition only so I can access my internal memory as the data partition is still fully intact..
If not I wont be surprised as this LB phone (camera) is a total disaster for me and I am regretting getting it in the first place... It's a real mess with these glitches ..
Click to expand...
Click to collapse
If you got proper root you're always able to backup. It's just your fault you lost your data.
If it's just system that's gone you haven't lost any actual data yet, get the ftf for the firmware you were using, flash it in flashtool with everything but system /kernel checked. That way it doesn't wipe data etc. I'm not at my computer so can't be exact but you get the picture just restoring system via flashtool should do the trick
Also if you use xposed there's a module to enable handling of external storage, that and setting pics to save to external memory card should avoid you ever having this issue again. There's also an app called folder mount that can be used to ghost internal directories to the external card too hth
Oh also, I may be wrong but if you were using philz if you let the screen go dark while your running something it stays dark till it's finished then a quick press of the power button wakes it back up, you should of waited a little longer if that was the issue
Mr.R™ said:
If it's just system that's gone you haven't lost any actual data yet, get the ftf for the firmware you were using, flash it in flashtool with everything but system /kernel checked. That way it doesn't wipe data etc. I'm not at my computer so can't be exact but you get the picture just restoring system via flashtool should do the trick
Also if you use xposed there's a module to enable handling of external storage, that and setting pics to save to external memory card should avoid you ever having this issue again. There's also an app called folder mount that can be used to ghost internal directories to the external card too hth
Oh also, I may be wrong but if you were using philz if you let the screen go dark while your running something it stays dark till it's finished then a quick press of the power button wakes it back up, you should of waited a little longer if that was the issue
Click to expand...
Click to collapse
Your a GENIUS this totally saved me thank you so much sir : THIS WORKED... it was something I considered but found daunting because I have a 6906, the 6903 FTF worked for anyone reading this !!!! Maybe I can fix my attitude on this one thanks again...
futiless said:
Your a GENIUS this totally saved me thank you so much sir : THIS WORKED... it was something I considered but found daunting because I have a 6906, the 6903 FTF worked for anyone reading this !!!! Maybe I can fix my attitude on this one thanks again...
Click to expand...
Click to collapse
Can I suggest you edit title to include [SOLVED] - might help other folks out
No worries pal, glad you got it sorted I'd be just the same if I thought I'd lost data that was important to me
Plus, why the hell are you not using google+ to backup your photos ?
Personally I use My PhoneExplorer to back my phone up and synchronise with my pc. It wil also back up all your photos to a folder in the My Pictures directory, sync your calendar and even make basic data backups. Been using it for years now, ever since I had a Sony Ericsson K700 phone
This is just a suggestion if you are also a bit paranoid in storing all your stuff on google.
http://www.fjsoft.at/en/
Sent from my D6503 using XDA Free mobile app
But you know that even without any rooting there is an option inside the camera app where to store pictures? You can choose ext. SD Card there. In my opinion it's not hard to find and due to your last disaster it's your fault not checking this. Since there are options to keep pictures on SD Card in fact you shouldn't blame the phone nor Sony.
furrypotato said:
Plus, why the hell are you not using google+ to backup your photos ?
Click to expand...
Click to collapse
Privacy reasons, not wanting a third party to be responsible for your data etc etc
gurningchimp said:
Can I suggest you edit title to include [SOLVED] - might help other folks out
Click to expand...
Click to collapse
Would like to do this but don't know how exactly ...
futiless said:
Would like to do this but don't know how exactly ...
Click to expand...
Click to collapse
click on edit/delete
click on go advanced
see the title box Below Reason for editing... change that one
Example Picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
furrypotato said:
Plus, why the hell are you not using google+ to backup your photos ?
Click to expand...
Click to collapse
Kind of short sighted and pretentious to think we would all see things exactly the same. Personally Google isn't the "answer" to all my problems. Secondly I have had numerous smart phones as most of us have and this Xperia although I love it I have to dance around the volatile situation it poses to have 4.4 limitations which requires root to be able to in order to write to SD (?!). Kinda weird if you ask me and this is just one more thing to setup and calibrate so between roms it is easily overlooked. As I don't actually use social networking all that much and I have such large photos among many other things. I am thinking of other ways to automate this in the future. I am looking for a more set it and forget it method and if I could persist this between roms so be it.
I would like to know who keeps everything they own online aswell today... I mean why do companies use a VPN for data archive ... when they can just sync EVERYTHING to the cloud ?
I ponder politics
Envious_Data said:
click on edit/delete
click on go advanced
see the title box Below Reason for editing... change that one
Example Picture
Click to expand...
Click to collapse
Where is the field to edit the Thread and not just the first post ?
You should not flash ROMs in locked BL even if you have a recovery and root that doesn't mean it will flash a ROM.
so I have made a twrp backup of the new lollipop OC5 for the sprint note3 stock and it should be rooted if anybody is interested on using this backup here is the link https://www.mediafire.com/?959vjs98swqrdf5 just unzip the folder put it in the twrp backup folder reboot to recovery restore the backup and enjoy. (if this helps you don't forget to hit the thanks button!) PS the file is called (2015-04-11--13-33-08 LRX21V.N900PVPUEOC5)
You know your personal info will be in that lol. Google account and such
Sent from my 0x1 Note 3...... I love tep
kaos420 said:
You know your personal info will be in that lol. Google account and such
Sent from my 0x1 Note 3...... I love tep
Click to expand...
Click to collapse
great i got a stupid question after that....
jus like he did wouldnt i be able to get the update do a factory reset and then do a backup to share or would it still have the info listed too?
The phone is a image of your phone. To do what you want to do. You will have your info stored. Also will get a invalid user Id warning on boot. Will prove a lot of. Issues. I did just flash nk4 wipe from stock recovery. Boot up and it will update fine. But your msl all your sprint id **** in in the backup.
Sent from my 0x1 Note 3...... I love tep
So this is what i did...took the ota whent through the set up and some other things booted to custom recovery wipe data did the backup flash different rom for a day then whent back to recovery flash the backup and had to go through the setup again and there's no personal data...so if anybody wants to give it a shot just let me know if it works for you guys.
If it's activated there's data. Let someone flash. Bet there is ghost files.
Sent from my 0x1 Note 3...... I love tep
kaos420 said:
If it's activated there's data. Let someone flash. Bet there is ghost files.
Sent from my 0x1 Note 3...... I love tep
Click to expand...
Click to collapse
ROM is in SYSTEM partition. If you back up only SYSTEM partition you will get ROM. personal data is in DATA partition. MSL and stuff is in EFS. Full nandroid backup can contain all of those, but if you only back up SYSTEM it should be ok.
Make sure you install this tool: http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325 and backup your EFS in a safe location before trying.
leond said:
ROM is in SYSTEM partition. If you back up only SYSTEM partition you will get ROM. personal data is in DATA partition. MSL and stuff is in EFS. Full nandroid backup can contain all of those, but if you only back up SYSTEM it should be ok.
Make sure you install this tool: http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325 and backup your EFS in a safe location before trying.
Click to expand...
Click to collapse
Go use a root Explorer and look under system Etc system csc browsing 3 files in csc I see my phone serial my msl and my sprint email. Sooooo how is that not data. It's in the system. Lollipop is a difference thing altogether. Just trying g to help the mkv not share his info. Or another user mess up there device. But hey to each their own.
Sent from my 0x1 Note 3...... I love tep
lollipop is not different partition-wise, ROM still goes in to System partition. I downloaded zip extracted and looked inside. it has boot, data and system partitions. Data partition is practically empty, the way it should be. EFS backup is not present. System partition has no personal info. It should be ok to flash.
BTW, /system/etc/csc or /system/etc/system/csc does not exists neither in this nor in kitkat ROMs
I see /system/csc/ but nothing personal there and there shouldn't be
leond said:
lollipop is not different partition-wise, ROM still goes in to System partition. I downloaded zip extracted and looked inside. it has boot, data and system partitions. Data partition is practically empty, the way it should be. EFS backup is not present. System partition has no personal info. It should be ok to flash.
BTW, /system/etc/csc or /system/etc/system/csc does not exists neither in this nor in kitkat ROMs
I see /system/csc/ but nothing personal there and there shouldn't be
Click to expand...
Click to collapse
Actually both exist. Lmfao I'm good give what info you think is right. It's not but hey your 44 post count was earned some how. But hey you got it. I'm done unsuscribing from thread.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my 0x1 Note 3...... I love tep
Just finished doing restore using this backup - everything looks good - i have phone and data working (with my and not OP's phone number )
The only thing I see is that baseband is still at NK4. It seems to work fine so I can probably wait until OC5 modem is officially posted, unless you know how to backup firmware/modem
kaos420 said:
Actually both exist. Lmfao I'm good give what info you think is right. It's not but hey your 44 post count was earned some how. But hey you got it. I'm done unsuscribing from thread.
Sent from my 0x1 Note 3...... I love tep
Click to expand...
Click to collapse
No personal info in system partition in general or in those folders in particular. Don't understand your insult about 44 posts. backup seems to work well so far.
So for those who got this backup and are using it do you guys have all the lollipop features but not baseband...then if you guys like it I'm glad to helped !!!!
Amazing.
havent had the time to try this yet, but hearing that it worked for some has convinced me to flash this over the weekend. I agree that it's probable that there are some personal data in there somewhere. I'll have a look at the file table and see whether system has anything interesting. But either way, thanks OP
Jairsantana said:
So for those who got this backup and are using it do you guys have all the lollipop features but not baseband...then if you guys like it I'm glad to helped !!!!
Click to expand...
Click to collapse
yes, running this as of yesterday. I had seen few Touchwith crashes, but I am not using Touchwiz so I don't care. Got Native hotspot working using :
GalaxyTools v3.1.2 http://forum.xda-developers.com/not.../app-one-click-hotspot-enabler-menus-t2816159
got external uSD writable from all apps using this app: FolderMount https://play.google.com/store/apps/details?id=com.devasque.fmount&hl=en
changed ro.securestorage.support=true to false in /system/build.prop to make sure it keeps wifi passwords unencrypted and does not forget them after reboot.
I'm pretty sure I can use this just to disect it builprop, csc etc to try to port some Roms so thanks @Jairsantana
Josephigloe said:
I'm pretty sure I can use this just to disect it builprop, csc etc to try to port some Roms so thanks @Jairsantana
Click to expand...
Click to collapse
good let us know when you have the ported rom so we ca give it a shot!!!:good:
Jairsantana said:
good let us know when you have the ported rom so we ca give it a shot!!!:good:
Click to expand...
Click to collapse
Wouldn't you just prefer deodex lol
On to my newly purchased s6 edge..
ram9200 said:
Wouldn't you just prefer deodex lol View attachment 3267532View attachment 3267533
On to my newly purchased s6 edge..
Click to expand...
Click to collapse
yeap it looks good just post the link when you have it ready!!!
Nice!
hi so i rooted my phone with Twrp V3 messi one it deleted my operating system :\\ and i need a backup rom restore file could someone make one and be able to give me it so i can restore my phone thank you so much i really thank you for it if you do it.
Backup also needed
I have the same situation and was wondering if you ever received a backup and if so could you give me a link to the file? Thank you.
Link to new recovery
https://forum.xda-developers.com/android/development/twrp-lg-aristo-aka-lv3-t3656019
And then you can flash the iPioneer stock rom.
https://forum.xda-developers.com/android/development/rom-ipioneer-stock-10i-v1-t3637393
Hope this helps.
@[email protected] has got you covered.
What I'd like to understand is what both of you did to wipe your system. There is literally no way for twrp to wipe your system partition unless you chose to wipe system.
It could happen. It happened to me while I was compiling the recovery. Misc partition not commented out in the fstab causes the recovery to wipe the system using the physical keys.
[email protected] said:
It could happen. It happened to me while I was compiling the recovery. Misc partition not commented out in the fstab causes the recovery to wipe the system using the physical keys.
Click to expand...
Click to collapse
But the fstab commit was for the stock lg recovery, which when using the hard key boot for recovery only performed a factory reset which also slid into the v1 twrp.
ninjasinabag said:
But the fstab commit was for the stock lg recovery, which when using the hard key boot for recovery only performed a factory reset which also slid into the v1 twrp.
Click to expand...
Click to collapse
No fstab is the file system table it tells the recovery what partitions are on the device. Without the twrp.fstab or recovery.fstab twrp would not boot up.
Read this :
https://source.android.com/devices/tech/ota/device_code
ninjasinabag said:
@[email protected] has got you covered.
What I'd like to understand is what both of you did to wipe your system. There is literally no way for twrp to wipe your system partition unless you chose to wipe system.
Click to expand...
Click to collapse
I must have checked the system partition in twrp on accident and for some reason did not create a Nandroid on my sd card but instead had it backed up to internal storage of which I wiped as well. Anyway, I am with T-Mobile and I flashed ipioneer and it works fine aside from having to make a few modifications because the dev decided he was the only one of whom should have administrative privileges to the ROM. I have to admit it was a pretty simple fix. All I had to do was pull the boot.img from the kdz file and flash it in fastboot mode. Oh, I had to remove the super user files as well which was not a problem with twrp recovery. I'm not making any judgment calls but it seems a little fishy to me that the developer would not have ulterior motives of having root privileges to my device.Hmmm, just something to think about before you flash this ROM or if you do... ipioneer? NO, I PIONEER MY OWN DEVICE!!! Aside from that, big shout out to the developer it was a lifesaver aside from that one small glitch.
Sent from my LG-TP450 using Tapatalk
sdflowers32 said:
I must have checked the system partition in twrp on accident and for some reason did not create a Nandroid on my sd card but instead had it backed up to internal storage of which I wiped as well. Anyway, I am with T-Mobile and I flashed ipioneer and it works fine aside from having to make a few modifications because the dev decided he was the only one of whom should have administrative privileges to the ROM. I have to admit it was a pretty simple fix. All I had to do was pull the boot.img from the kdz file and flash it in fastboot mode. Oh, I had to remove the super user files as well which was not a problem with twrp recovery. I'm not making any judgment calls but it seems a little fishy to me that the developer would not have ulterior motives of having root privileges to my device.Hmmm, just something to think about before you flash this ROM or if you do... ipioneer? NO, I PIONEER MY OWN DEVICE!!! Aside from that, big shout out to the developer it was a lifesaver aside from that one small glitch.
Sent from my LG-TP450 using Tapatalk
Click to expand...
Click to collapse
Ummmmmm.
SuperSU was installed in the room to save you time. Not for anything fishy, a large majority of custom roms based on CyanogenMod and lineage os both have insystem root privileges from the start.
If you really are worried about someone doing something with your device that you feel isn't kosher, just look at outgoing data or in your list of apps.
Either way, I can promise you that the root access is only for you and nobody else to use.
Also, it's mildly insulting to make a claim like this because if it ends up being taken seriously, the developer could end up being barred from posting and that would cost us in the long run.
No offense to you, but that's just the facts on these kind of things.
ninjasinabag said:
Ummmmmm.
SuperSU was installed in the room to save you time. Not for anything fishy, a large majority of custom roms based on CyanogenMod and lineage os both have insystem root privileges from the start.
If you really are worried about someone doing something with your device that you feel isn't kosher, just look at outgoing data or in your list of apps.
Either way, I can promise you that the root access is only for you and nobody else to use.
Also, it's mildly insulting to make a claim like this because if it ends up being taken seriously, the developer could end up being barred from posting and that would cost us in the long run.
No offense to you, but that's just the facts on these kind of things.
Click to expand...
Click to collapse
You have a point and I do apologize. I don't use SuperSU because of the fact that it modifies the system partition and doesn't pass Google's safety net. I tried flashing a systemless root and it wouldn't allow me. Really the reason I said what I said was because when you flash the ROM he makes some remarks about being the only one with root privileges to the ROM so it had me a little confused I guess. Thanks for making the point though because I'm not trying to do anyone any harm I just hope that others have that same notion in mind. Believe me there are a lot of people that develop custom roms for hacking purposes so it's not unheard of. Anyways thanks again!
Sent from my LG-TP450 using Tapatalk
sdflowers32 said:
You have a point and I do apologize. I don't use SuperSU because of the fact that it modifies the system partition and doesn't pass Google's safety net. I tried flashing a systemless root and it wouldn't allow me. Really the reason I said what I said was because when you flash the ROM he makes some remarks about being the only one with root privileges to the ROM so it had me a little confused I guess. Thanks for making the point though because I'm not trying to do anyone any harm I just hope that others have that same notion in mind. Believe me there are a lot of people that develop custom roms for hacking purposes so it's not unheard of. Anyways thanks again!
Sent from my LG-TP450 using Tapatalk
Click to expand...
Click to collapse
No, I understand. No harm, no foul.
Normally If there is something fishy going on with your device, you can check your output. Data isn't censored from the monitor. So if your device is sending, you'll be able to see it.
If it was using the LG data gathering system (by way of rerouting the server for which the data gets sent to) your device wouldn't be able to connect to the LG app repository.
Anyway, there's no issue in being careful with what you do with your device. Especially if you have a valid worry like this, but it helps to get any relevant data on the subject of worry before you make any claims. (Sorry about the lecture, but I'd rather be outright instead of babying you on this since it helps in the long run to know as much as possible)
If there's anything you're curious about, or if you have a thought about something or another, just message @[email protected] @xtremelora or myself.
I can't speak for the others, but I'm almost always on and willing to share what little I do know.
Okay, and once again thank you for the information. One of the reasons I root my devices to begin with is because of all the permissions and just invasive ways of the world in general. And I'm not just talking about people, I'm talking about the cell phone carriers and manufacturers and so on and so forth. Seems like everyone's trying to gather your information all the time and it's a NeverEnding Story so it does have me on edge at times. And yes if I have any questions you seem to be quite knowledgeable about things of this nature so I wouldn't be hesitant to message you or the others you mentioned. Once again, I'm really glad you said something because by no means do I want to hurt anyone or make anyone look bad who is actually doing many people like myself favors because I'm not exactly a noob but I've only been at this for a couple of years now and have a lot to learn. Thanks again.
Sent from my LG-TP450 using Tapatalk
Like I said, it's nothing to worry about. We all start from the bottom and make our way up the ladder, but we only go so far without everyone else pending a hand when we get stuck.
Or in my case, being stubborn enough to break everything and back track until you fix what you broke. Lmao
sdflowers32 said:
I must have checked the system partition in twrp on accident and for some reason did not create a Nandroid on my sd card but instead had it backed up to internal storage of which I wiped as well. Anyway, I am with T-Mobile and I flashed ipioneer and it works fine aside from having to make a few modifications because the dev decided he was the only one of whom should have administrative privileges to the ROM. I have to admit it was a pretty simple fix. All I had to do was pull the boot.img from the kdz file and flash it in fastboot mode. Oh, I had to remove the super user files as well which was not a problem with twrp recovery. I'm not making any judgment calls but it seems a little fishy to me that the developer would not have ulterior motives of having root privileges to my device.Hmmm, just something to think about before you flash this ROM or if you do... ipioneer? NO, I PIONEER MY OWN DEVICE!!! Aside from that, big shout out to the developer it was a lifesaver aside from that one small glitch.
Click to expand...
Click to collapse
Dude....
First, hello buddy.
Second, the stock iPioneer rom doesn't have SuperSu installed on (unless SuperR. kitchen didn't eliminate all traces from adb wich would not be my fault).
Third, the stament "Let's set the permissions..... Well, super power are only mine..." IT IS FOR METADATA PERMISSIONS not for ROOT privileges (wich is not present in that rom)
Fourth, if you pay attention to the updater-script inside the rom and chech every statement I wrote you can notice they are FUNNY or SARCASTIC
Finally, there is not an statement for SuperSu on any of my roms (stock, slim, core) because SuperSu it has its own statement that you can see when is installing on twrp.
But you are right, we all need to proceed with caution when we modify our phones. Did you laugh with the: "Let's extract the boot image... Boot image, the pictures of boots?..." statement?
BTW: I would like to do a neutral rom for Tmo and Mtro.
Thank you @ninjasinabag for mention my username, I usually don't read other post about this device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
xtremelora said:
Dude....
First, hello buddy.
Second, the stock iPioneer rom doesn't have SuperSu installed on (unless SuperR. kitchen didn't eliminate all traces from adb wich would not be my fault).
Third, the stament "Let's set the permissions..... Well, super power are only mine..." IT IS FOR METADATA PERMISSIONS not for ROOT privileges (wich is not present in that rom)
Fourth, if you pay attention to the updater-script inside the rom and chech every statement I wrote you can notice they are FUNNY or SARCASTIC
Finally, there is not an statement for SuperSu on any of my roms (stock, slim, core) because SuperSu it has its own statement that you can see when is installing on twrp.
But you are right, we all need to proceed with caution when we modify our phones. Did you laugh with the: "Let's extract the boot image... Boot image, the pictures of boots?..." statement?
BTW: I would like to do a neutral rom for Tmo and Mtro.
Thank you @ninjasinabag for mention my username, I usually don't read other post about this device.
Click to expand...
Click to collapse
I wanted to make sure you could clarify in your defense since you are the developer, but this is also a moment for introduction so we can avoid scenarios like this.
How can I get a zip file of the t mobile variant of the stock Rom to flash in twrp? I flashed the ipioneer Rom but I have t mobile and im having problems....
Sent from my LG-TP450 using Tapatalk
If you want to get ram dump, hellllllp?
help fix m210
[/IMG]
https://mega.nz/#!ULwBjLoa!F2WVAGX6XdbwCp0KWDLPYnnlRz7vjBtn23L7mACpctQ