Related
PLEASE MAKE SURE YOUR HAVE FASTBOOT AND RECOVERY FULL UNLOCKED BEFORE USE!!!!
so recently i have had my GT540 stolen, so i though next time ill SEMI-brick my phone over the air. i am currently developing an app that will;
1. listence for a text
E.g. "Brick Me PASSWORD IMEI"
PASSWORD would be your preset password
IMEI would be your IMEI number
2. upon receving this text it will;
extract the "erase_image" binary and erase your boot partition, then run "reboot -p" which will turn off your phone.
this meen that the phone wont be able to boot up the android OS, but it WILL be able to boot into recovery mode and fastboot mode.
So, this mean that a nandroid back up is required before testing. could anybody help me out with testing this app(i would but i wont have a new phone for a wile yet, awating the Nexus 3 release ). Also an emulator doesnt have busybox installed, and wont install.
Download
wowowowowowwowowow nice idea!!!you planning to make this a paid app on the market ????? well i want to help but im too busy studying for my end of year exams so maybe next time.....
thinking about it, but need to make sure it works first.
So, basically.. the software would screw up your phone, leaving it in a state where it's pretty easy to repair, and all your personal information would stay intact.. and just re-flashing a good boot.img would make your phone fully accessible again. Sorry, not a good idea, because any sensitive information you have on your phone would still be accessible(in the right hands anyway). The software's definitely not going to help you get your phone back, so I figure there's no reason for the data on it to stay intact. If you can figure out a way to wipe it AND screw it up, that would be more useful(sdcard too!). Also, having to rely on sending an SMS to yourself is also a bit useless, because no one in their right mind will leave the phone on, and with the SIM card in, so I'm thinking you should rather make the client(phone-side) application await commands not only from messages, but also from the internet(Of couse, I imagine that would require an online service, where the client stays logged in in order to keep an updated IP, and also that would mean more traffic on the monthly bill, but it's a small price to pay).
Just my thoughts on this.. the overall idea is great, but you should at least consider a different method of activation(rather than SMS). Good luck.
P.S. Actually.. when i think about it. You could also pair the client with the current SIM card, so when and IF that's replaced, and the phone is turned on, it sends a message to some other predefined number with the new card's number, and you could operate with that. There was a software for Symbian UIQ(and probably not only) that did exactly this.
Good ideas, will work on erasing all data, and damaging the sdcard. not shore on how well it would work though because my app would be in the data partition.
update: ok, so i managed to wipe the sdcard and data partition, any idea on deleting all the partition with busybox?
ill wait till i get a new phone to test it. thanks ofr your suggestion nutterbg
theres an app out there atm called Seekdroid, it can track your phone to within 30metres, lock it , wipe sd , wide anything as a matter of fact and u can cancel everything the user wants to do. Check it out , all u do is log onto a website to find it
lukemovement1 said:
Good ideas, will work on erasing all data, and damaging the sdcard. not shore on how well it would work though because my app would be in the data partition.
update: ok, so i managed to wipe the sdcard and data partition, any idea on deleting all the partition with busybox?
Click to expand...
Click to collapse
Sorry, not a developer, so I've no idea. I do good as a common-sense-endowed-person though. I doubt it's possible to damage the sd card.. irreperably anyway, and I'm guessing you wouldn't want that(how does one test that?), but yeah, wiping it is more than enough.
ChriisM said:
theres an app out there atm called Seekdroid, it can track your phone to within 30metres, lock it , wipe sd , wide anything as a matter of fact and u can cancel everything the user wants to do. Check it out , all u do is log onto a website to find it
Click to expand...
Click to collapse
Or androidlost app FREE!
http://www.androidlost.com
lukemovement1 said:
Good ideas, will work on erasing all data, and damaging the sdcard. not shore on how well it would work though because my app would be in the data partition.
update: ok, so i managed to wipe the sdcard and data partition, any idea on deleting all the partition with busybox?
Click to expand...
Click to collapse
you could make the app that has a update.zip in it and use recoverys extended commands to reboot into recovery and auto flash the zip that has a .sh and the flash_erase file in it to erase the system/data/boot partitions just an idea
bs828 said:
wowowowowowwowowow nice idea!!!you planning to make this a paid app on the market ????? well i want to help but im too busy studying for my end of year exams so maybe next time.....
Click to expand...
Click to collapse
Hmm. Nice idea. But, it is kind of risky if implemented correctly.
You can modify erase_image to remove recovery, data and cache partitions. This way it will do a remote wipe as well.I believe it would be possible to mess up the boot loader as well rendering the phone completely useless.
nibras_reeza said:
Hmm. Nice idea. But, it is kind of risky if implemented correctly.
You can modify erase_image to remove recovery, data and cache partitions. This way it will do a remote wipe as well.I believe it would be possible to mess up the boot loader as well rendering the phone completely useless.
Click to expand...
Click to collapse
Hm, you got me thinking.. Does a phone with a messed up bootloader(obviously no fastboot, no regular boot, no recovery) still boot into Download Mode(no battery)? I wonder if the bootloader's responsible for that too... otherwise you could render the phone not only completely useless, but irreparable, and I'm not sure we want that... Or how we can test that without losing a phone.
nutterbg said:
Hm, you got me thinking.. Does a phone with a messed up bootloader(obviously no fastboot, no regular boot, no recovery) still boot into Download Mode(no battery)? I wonder if the bootloader's responsible for that too... otherwise you could render the phone not only completely useless, but irreparable, and I'm not sure we want that... Or how we can test that without losing a phone.
Click to expand...
Click to collapse
Depends on how much you damage the boot loader. If you fully wipe it, the phone would become useless. The only way to fix it would be writing directly to the motherboard in super-dev mode using special equipment. I don't know if this is supported by LG Optimus though.
Nonetheless, after reading this, I got a cooler idea. Why shouldn't we write a trojan and inject it to a system core apk? Perhaps to the browser or location service?
This way we could find the location of the phone even after a factory reset provided the system apks were not replaced. ie, when the thief finally sells it and someone else uses it, we would be able to track it and get it back. Also, we can have a feature to wipe user data and a complete destruction mode where we damage the phone beyond repair.
My Droid 4 is bricked, but out seems to me that if I could get safestrap recovery in, I could boot any working "safe" ROM and leave my non-functioning "unsafe" system alone until the day a fastboot image becomes available.
The only wrinkle is that since the current OS is bricked, I can't load the Safestrap recovery via Apk. Is there any way to load it using one of the remaining capabilities in the phone (normal recovery, fastboot, etc.)?
I definitely don't have the full technical ability to answer your question, but to get the ball rolling:
Can you get adb up and running? If you can't, my guess is no... If you can, somebody who knows more than I do might be able to get you going...
Call Motorola or the wireless vendor where you got your phone and play dumb.
How did you brick your phone?
I bricked mine the first time by restoring a saved stock rom that I had made. Little did I know, but I got the webtop save mixed up, and totally soft-bricked my handset.
Safestrap is a good alternative to having nothing, but you should read everything there is to know about it before installing it. Conceptually, it doesn't share a whole lot with the original clockworkmod recovery.
RueTheDayTrebek said:
Call Motorola or the wireless vendor where you got your phone and play dumb.
Click to expand...
Click to collapse
I've thought about it. (1) there's stuff on the internal "sdcard" (/sdcard, as distinct from the removable real SDC) I'd like to recover if I could, so restoring the phone I have right now is preferable, unless restoring from a fastboot recovery wipes /sdcard).. and (2) I hate the idea of "cheating" on a warranty for a self-inflicted product failure, both on the ethics of it and on the remote possibility I could get caught.
How did you brick your phone?
Click to expand...
Click to collapse
I had safely rooted the phone (Droid 4 Utility is awesome) and installed Titanium Backup Pro. I was playing around with freezing bloatware, deleting bloatware, and the like... the last thing I did before rebooting and never coming back was integrating system application dalvik cache into the ROM and then undoing that integration. But I can't be sure that was the killer, since I hadn't rebooted for a while before that... one of the other changes earlier could have been it.
Safestrap is a good alternative to having nothing, but you should read everything there is to know about it before installing it. Conceptually, it doesn't share a whole lot with the original clockworkmod recovery.
Click to expand...
Click to collapse
Yeah, I recognize it's a very different world because of the locked bootstrap, so I'd obviously have to adapt to the differences, but just the ability to get some use out of the phone before the fastboot recovery leaks would be a good start. My needs are not great. Something besides repeated reboots ("Droid..." every 10 seconds until the battery runs flat) would make me happier than a pig in slop.
podspi said:
I definitely don't have the full technical ability to answer your question, but to get the ball rolling:
Can you get adb up and running? If you can't, my guess is no... If you can, somebody who knows more than I do might be able to get you going...
Click to expand...
Click to collapse
Yeah. The times I've tried, the phone never boots to the point that the USB debugging driver on the PC ever sees the phone ("adb devices" lists nothing).
About the only interaction I can get to is to force the phone into fastboot and plugging in with the fastboot USB driver on the PC. RSD Lite does see the phone then. Too bad I don't have a fastboot recovery to use at that point.
I recently received my nexus 6 a couple days ago and I LOVE it. The problem I am having at the moment is that I can't seem to get it to go decrypt. I downloaded the tool kit and my devices build isn't present. As a result, the tool kit it won't allow me to run the decrypt option on the fastboot window.
It's anyone running into this. My build is a LNX***.
First, what toolkit are you talking about?
Second, to decrypt the N6 you need to flash a modified boot image and then wipe your phone.
Thirdly, what's build LNX***?
Didgeridoohan said:
First, what toolkit are you talking about?
Second, to decrypt the N6 you need to flash a modified boot image and then wipe your phone.
Thirdly, what's build LNX***?
Click to expand...
Click to collapse
I'm using the nexus root toolkit . I have the flash on my computer and LNX07M is the build I have on the device. Maybe I should install a custom ROM first?
Nexus 6....man I missed being rooted.
KappaAce2010 said:
I'm using the nexus root toolkit . I have the flash on my computer and LNX07M is the build I have on the device. Maybe I should install a custom ROM first?
Nexus 6....man I missed being rooted.
Click to expand...
Click to collapse
You just need a custom kernel and a wipe.
another prime example of why you shouldn't use toolkits, if you don't understand what they are doing you shouldn't be using them.
To decrypt all you need to do is:
Backup your internal storage to a PC
Either use custom recovery to wipe everything including internal storage, install your rom and install a kernel that doesn't force
or
factory reset your phone, but before it boots up go back into recovery and flash a custom kernel that doesn't enforce
Circaflex said:
another prime example of why you shouldn't use toolkits, if you don't understand what they are doing you shouldn't be using them.
To decrypt all you need to do is:
Backup your internal storage to a PC
Either use custom recovery to wipe everything including internal storage, install your rom and install a kernel that doesn't force
or
factory reset your phone, but before it boots up go back into recovery and flash a custom kernel that doesn't enforce
Click to expand...
Click to collapse
Well if you to come off as a jerk, you have accomplished your goal. All you had to do was state what was needed and none of bs personal ideals you have. It's a Q & A section, so you should expect questions like this to arise.
Thank you for the input though.
Nexus 6....man I missed being rooted.
KappaAce2010 said:
Well if you to come off as a jerk, you have accomplished your goal. All you had to do was state what was needed and none of bs personal ideals you have. It's a Q & A section, so you should expect questions like this to arise.
Thank you for the input though.
Nexus 6....man I missed being rooted.
Click to expand...
Click to collapse
Although you're right, it is a personal ideal of many of us, I don't think he intended to come off as a jerk. But his point is that toolkits often remove the need for knowledge, which can become a problem for some users.
The good thing about nexus devices is that everything is pretty easy to do, so if you get stuck - continue to ask.
+1 to what rootSU said. And you should probably upgrade. That build is ancient and doesn't even have an official factory image (the reason it's not available in NRT).
Didgeridoohan said:
+1 to what rootSU said. And you should probably upgrade. That build is ancient and doesn't even have an official factory image (the reason it's not available in NRT).
Click to expand...
Click to collapse
I already plan on doing this anyway. Just time is conflicting with me at the moment.
rootSU said:
Although you're right, it is a personal ideal of many of us, I don't think he intended to come off as a jerk. But his point is that toolkits often remove the need for knowledge, which can become a problem for some users.
The good thing about nexus devices is that everything is pretty easy to do, so if you get stuck - continue to ask.
Click to expand...
Click to collapse
Well it happened, it's not going anywhere. Either way thanks guys for the advice. I should figure out everything tonight.
Nexus 6....man I missed being rooted.
Everything is a go. Fully decrypted and loving it. Thanks again.
so, just got my nexus a couple of days ago, and loving it!
would like to decrypt, but not 100% sure on the best/safest way to do it at this point..
running pure rom, with lots of tweaks, and I originally unlocked and rooted with Wugs great toolkit.
I know if I decrypt at this point I will lose all my data and stuff, but of course its already backed up in a couple of places, and I have the "fixes" to flash after I decrypt to keep me that way, if I flash a "encrypted" rom by mistake.
Just wondering if someone could make a straightforward post, telling me the 3 or 4 things I need to do/flash to get to that point.
Thanks so much!:good:
you need to flash a custom kernel that allows for decryption, then you have to format your storage. only then will you boot up decrypted. if you dont actively decrypt(format your storage), you wont be decrypted. this will delete everything in your storage.
ok, then do you know of a kernel for Tmobile that allows for that?
do I flash that kernel in twrp, then also format everything else in TWRP?
if I do that, how do I then boot my phone into something useable so I can rebuild it once again?
thanks
wase4711 said:
ok, then do you know of a kernel for Tmobile that allows for that?
do I flash that kernel in twrp, then also format everything else in TWRP?
if I do that, how do I then boot my phone into something useable so I can rebuild it once again?
thanks
Click to expand...
Click to collapse
You can use the Nexus Root Toolkit to decrypt as well. I believe its under advanced utilities-flash boot image. You will have to be on a stock build however, so you could also use flash stock plus unroot. I believe there is an option there for flashing a no encrypt kernel in the process.
Sent from my Nexus 6 using Tapatalk
wase4711 said:
ok, then do you know of a kernel for Tmobile that allows for that?
do I flash that kernel in twrp, then also format everything else in TWRP?
if I do that, how do I then boot my phone into something useable so I can rebuild it once again?
thanks
Click to expand...
Click to collapse
any custom kernel does. and there is no such thing on any nexus device as aa rom or kernel for a specific carrier, they all work on tmobile.
Othoric said:
You can use the Nexus Root Toolkit to decrypt as well. I believe its under advanced utilities-flash boot image. You will have to be on a stock build however, so you could also use flash stock plus unroot. I believe there is an option there for flashing a no encrypt kernel in the process.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
simms22 said:
any custom kernel does. and there is no such thing on any nexus device as aa rom or kernel for a specific carrier, they all work on tmobile.
Click to expand...
Click to collapse
thanks guys, I got it now!
Final question; is there a REAL difference in performace when you are decrypted, or is it mostly placebo?
this phone, on Pure Rom, is super fast and smooth, and I cant imagine it getting much better if decrypted, but as a Nexus N00b, I just dont know.
Thanks again for your help and feedback :good:
Most likely Pure has a decrypt kernel. Haven't looked. Beans usually adds all those tweaks. Just need to format data. May Lose your data and have to start over. Not sure as I run encrypted. If run decrypted might as well welcome Stagefright too.
ah, good point, so running decrypted makes you vulnerable to that krap...
wase4711 said:
ah, good point, so running decrypted makes you vulnerable to that krap...
Click to expand...
Click to collapse
Decrypted makes you vulnerable to any data exploit. Stagefright is different but both are security risks. Probably won't see a performance boost with decrypt. Only can be seen with large data files. Won't see with apps or daily use.
wase4711 said:
thanks guys, I got it now!
Final question; is there a REAL difference in performace when you are decrypted, or is it mostly placebo?
this phone, on Pure Rom, is super fast and smooth, and I cant imagine it getting much better if decrypted, but as a Nexus N00b, I just dont know.
Thanks again for your help and feedback :good:
Click to expand...
Click to collapse
I've ran both. And I actually just decrypted for a second time to see if I noticed any difference. To be perfectly honest, and this is just my personal experience, I haven't seen any noticeable difference between being encrypted or not since the release of 5.1. And since there are some ROMs out there that do have force encryption, I personally am going to go back to being encrypted just so I have one less thing to worry about when flashing ROMs. But there is a flashable zip that you can flash after any ROM that will disable force encryption if you want to go that route.
Sent from my Nexus 6 using Tapatalk
Let's clear things up. There is only one way to do it. You first need a kernel that doesn't force encryption (most don't force) so check the rom thread as its kernel probably doesn't either.
Then, you have to format userdata, which means all your apps, data (including sdcard) and settings will be gone.
Granted, there are a few ways to get these 2 steps done, but "fastboot format userdata" or format /data from TWRP recovery are the best.
As for TMobile, its the exact same phone as every other in north America, so all roms and kernels work. Actually there is.only one other model.(international) .and that works.with all the same.ROMs.and kernels.too.
Thanks for clarification. The format userdata was what I wasn't sure about. Recovery format I know clears all data. Fastboot format userdata restores data after format. Fastboot erase userdata wipes data. Wasn't sure which type format was required.
danarama said:
Let's clear things up. There is only one way to do it. You first need a kernel that doesn't force encryption (most don't force) so check the rom thread as its kernel probably doesn't either.
Then, you have to format userdata, which means all your apps, data (including sdcard) and settings will be gone.
Granted, there are a few ways to get these 2 steps done, but "fastboot format userdata" or format /data from TWRP recovery are the best.
As for TMobile, its the exact same phone as every other in north America, so all roms and kernels work. Actually there is.only one other model.(international) .and that works.with all the same.ROMs.and kernels.too.
Click to expand...
Click to collapse
thanks man, I am out of thanks for the day, but I do appreciate the input!
it sounds like with 5.1, there isn't a real strong reason to decrypt, and with all the stagefright nonsense floating around, and what ever other hidden exploits there are, its probably better at this point to just stay encrypted, since it doesn't sound like there are any major advantages to decrypt right now.
I appreciate everyone who posted in here for their knowledge and insight, and I will make sure I help anyone else going forward with a similar question.:good::good:
prdog1 said:
Thanks for clarification. The format userdata was what I wasn't sure about. Recovery format I know clears all data. Fastboot format userdata restores data after format. Fastboot erase userdata wipes data. Wasn't sure which type format was required.
Click to expand...
Click to collapse
fastboot erase userdata wipes all data but doesn't recreate the file system so the filesystem will retain the encryption flag.
fastboot format userdata will recreate the filesystem losing the encryption flag and since the kernel won't re-add the flag on boot, ,you're good to go.
Neither restore data.
Same in recovery, erase/wipe data won't format, only format will.
danarama said:
fastboot erase userdata wipes all data but doesn't recreate the file system so the filesystem will retain the encryption flag.
fastboot format userdata will recreate the filesystem losing the encryption flag and since the kernel won't re-add the flag on boot, ,you're good to go.
Neither restore data.
Same in recovery, erase/wipe data won't format, only format will.
Click to expand...
Click to collapse
You are correct. Thanks for the clarification. I run modified stock rooted so don't run into a lot of these scenarios that break their devices. All my mods are hard coded.
Mod Edit
Thread Closed - At OP request
ronnie498
Forum Moderator
Hoping I'm not totally screwed here, but here goes. I'm swapping from one Nexus 6 to another. On stock 5.0.1 (still), rooted, and unencrypted. I made my Titanium Backups (always as a precaution) then booted to TWRP and made a nandroid backup. I was too tired to command line myself so I decided to use the Skipsoft Toolkit to pull my data. I got curious about a full backup option on there so I tried it out. First thing it did was boot an unsecured boot.img. Phone then boots back up and begins the encryption process. I knew I didn't want encryption, so I powered off mid-process. (Kicking myself for that now...) Now when I boot back up, I get the "Encryption Unsuccessful" message telling me that my data is unusable and that I must do a phone reset.
I can still get to the bootloader and boot into TWRP, but it can't see any of the data on the device--including the TWRP backup I made earlier today. Seeing as I didn't get any of my backups off before this happened, I need that TWRP or I will lose everything since my last backup on 11/6. Is there ANY way to still pull data from a partial but failed encryption? Please help!
wizard5007 said:
Hoping I'm not totally screwed here, but here goes. I'm swapping from one Nexus 6 to another. On stock 5.0.1 (still), rooted, and unencrypted. I made my Titanium Backups (always as a precaution) then booted to TWRP and made a nandroid backup. I was too tired to command line myself so I decided to use the Skipsoft Toolkit to pull my data. I got curious about a full backup option on there so I tried it out. First thing it did was boot an unsecured boot.img. Phone then boots back up and begins the encryption process. I knew I didn't want encryption, so I powered off mid-process. (Kicking myself for that now...) Now when I boot back up, I get the "Encryption Unsuccessful" message telling me that my data is unusable and that I must do a phone reset.
I can still get to the bootloader and boot into TWRP, but it can't see any of the data on the device--including the TWRP backup I made earlier today. Seeing as I didn't get any of my backups off before this happened, I need that TWRP or I will lose everything since my last backup on 11/6. Is there ANY way to still pull data from a partial but failed encryption? Please help!
Click to expand...
Click to collapse
You most likely corrupted all the data on the device.
Not sure why you thought powering off during encryption would stop it and not cause corruption.
Also dont even think about restoring a nandroid on a new device.
zelendel said:
You most likely corrupted all the data on the device.
Not sure why you thought powering off during encryption would stop it and not cause corruption.
Also dont even think about restoring a nandroid on a new device.
Click to expand...
Click to collapse
Because I wasn't thinking... I know--stupid. Is there no shot at recovering anything?
I'm switching from one Nexus 6 to another. Can I not restore a nandroid to an identical device?
wizard5007 said:
Because I wasn't thinking... I know--stupid. Is there no shot at recovering anything?
I'm switching from one Nexus 6 to another. Can I not restore a nandroid to an identical device?
Click to expand...
Click to collapse
No, no you can not. A nandroid has device spicific files in it like GPS and IMEI info. Restoring it is just asking for trouble. Only restore USER apps and data everything else is off limits.
How did you fix the issue?
zelendel said:
No, no you can not. A nandroid has device spicific files in it like GPS and IMEI info. Restoring it is just asking for trouble. Only restore USER apps and data everything else is off limits.
Click to expand...
Click to collapse
So what specifically is in /system or /data that would be so dangerous?
Have you ever actually done this, or are you just saying stuff you have read but don't fully understand?
If you backed up every single partition its a bad idea to restore to another phone... But simple backups are fine to restore cross device if you aren't including efs
scryan said:
So what specifically is in /system or /data that would be so dangerous?
Have you ever actually done this, or are you just saying stuff you have read but don't fully understand?
If you backed up every single partition its a bad idea to restore to another phone... But simple backups are fine to restore cross device if you aren't including efs
Click to expand...
Click to collapse
You do know who your talking to right? I don't read things. I do them. Been doing this for over 10 years now. So just maybe you might want to know who you are talking to first.
zelendel said:
You do know who your talking to right? I don't read things. I do them. Been doing this for over 10 years now. So just maybe you might want to know who you are talking to first.
Click to expand...
Click to collapse
Nope, no idea who you are.
All I know is how many times I have seen twrp backups restored on a phone it wasn't taken on with out issue?
Maybe you should actual read things and you wouldn't have an issue with it either?
Or... Care to actually explain the danger rather then just puffing your chest out because you have played with android smart phones for ten years (apparently since before it was released?)
lol!
ok, both @zelendel and @scryan are right..
its highly not recommended to restore a nandroid onto a different phone if it contains system apps. that said, theres also a chance that it would be fine as well. its just that the system apps could not be supported(or could be) by the 2nd device. but even if they arent supported, it wont really harm your device, as you can fix whatever issues by just switching out the apps that are causing issues(then reboot).
scryan said:
Nope, no idea who you are.
All I know is how many times I have seen twrp backups restored on a phone it wasn't taken on with out issue?
Maybe you should actual read things and you wouldn't have an issue with it either?
Or... Care to actually explain the danger rather then just puffing your chest out because you have played with android smart phones for ten years (apparently since before it was released?)
Click to expand...
Click to collapse
Well let's start out with the fact that when system apps are loaded the data loaded to is set to one device. By restoring that to another device messes it up and causes all types of issues with the app and system.
Also as stated above not all apps are compatible across devices. Could lead you to an endless bootloop.
See you have me twisted. I don't have to read about it as I do it everyday. As each device is different there is no telling that one thing will work for one but not the other.
As for doing this before android was released? Yes. Who do you think got leaks to run on wm devices before the first nexus was released? Xda and the legendary HD2.
I was modding devices before the first smartphone was even released. Then I became a moderator here. Which is requires a whole lot of learning. Like reading the source and knowing what does what.
Now you are more then welcome to flash someone else's backup, that is up to you but I will tell you that no one that knows what they are doing will do that.
zelendel said:
As for doing this before android was released? Yes. Who do you think got leaks to run on wm devices before the first nexus was released? Xda and the legendary HD2.
Click to expand...
Click to collapse
the Dream(G1) was Googles android developer phone before the Nexus. while a lot of people did use and mod the HD2, the G1/Dream was getting most of the developer support.
simms22 said:
the Dream(G1) was Googles android developer phone before the Nexus. while a lot of people did use and mod the HD2, the G1/Dream was getting most of the developer support.
Click to expand...
Click to collapse
I wouldn't say most. But it was close indeed. I had them both but focused on the hd2 mostly. God I miss truly open bootloader lol.
zelendel said:
....focused on the hd2 mostly.
Click to expand...
Click to collapse
I remember the HD2 as one of the best phone ever made.
zelendel said:
Well let's start out with the fact that when system apps are loaded the data loaded to is set to one device. By restoring that to another device messes it up and causes all types of issues with the app and system.
Also as stated above not all apps are compatible across devices. Could lead you to an endless bootloop.
See you have me twisted. I don't have to read about it as I do it everyday. As each device is different there is no telling that one thing will work for one but not the other.
As for doing this before android was released? Yes. Who do you think got leaks to run on wm devices before the first nexus was released? Xda and the legendary HD2.
I was modding devices before the first smartphone was even released. Then I became a moderator here. Which is requires a whole lot of learning. Like reading the source and knowing what does what.
Now you are more then welcome to flash someone else's backup, that is up to you but I will tell you that no one that knows what they are doing will do that.
Click to expand...
Click to collapse
Just wanted to chime in here and say, I agree 1000% that I would never restore a backup from one phone to another, unless I knew for a fact I could "rescue" the phone if it locked up/got fried/ruined from the restore..
And, I have been playing with cell phones since November 1983, the first day cell service became widely available in Chicagoland, and I have been modding/tweaking/hacking them pretty much since then, so I too have "extensive" experience about what may or may not work when doing something like this..
To each his own, but I would never do this..