Thats it... A simple (but I want to do it without bricking my $600 phone) ROM flash.
This is the ROM I would like to install:
Stock Sense - 1.13.605.7 Basic DeBloat
Thank you. I give up trying to get help in IRC. Waste of time (except for Dr_Drache, he was very helpful)).
what part do you need help on? are you rooted?
yes, I am already rooted. I had a major malfunction in BAMF 1.6.3 this a.m. when a battery went dead. I replaced the battery and the phone went nuts... So I unrooted the phone and then re-rooted. I couldnt get help in the IRC channel to install this ROM I am asking about so I thought I would try to get some help here.
Thanks for replying.
I am not seeing the question here... Do you have rom manager installed? You could install simply from there. That's how I did my initial rom install.
Sent from my ADR6400L using XDA App
Just download .zip place on sd card and flash using rom manager or manually on clockwork recovery.
tk192 said:
Simply download the rom place on sdcard and flash using rom manager. Just make sure u have the gingerbread radio installed as well, otherwise you won't have a data connection. Also be careful with this rom and other gingerbread roms because of the possibility of bricking your $600 phone. It's been reported the leaked radio was causing hard bricked phone (just an FYI)
Click to expand...
Click to collapse
Stock sense basic debloat ROM does not use the GB radio. And to install I would recommend not using rom manager to install it tends to cause problems.
Sent from my HTC Thunderbolt BAMF ROM OF DEATH
Don't use Rom manager. Download the Rom. Reboot into recovery using Rom manager. Make a backup if you want. Wipe data. Wipe cache. Go to advanced. Wipe davlik cache and battery stats. Go to install zip from SD and select your Rom. When its done reboot.
Sent from my ADR6400L using XDA App
And ya that's not a gingerbread Rom. Is it based off latest froyo ruu?
Sent from my ADR6400L using XDA App
I'm still not sure what the question is here...but i'll lay some steps out for you.
FIRST AND FOREMOST: HAVE AMPLE BATTERY CHARGE!! I don't flash with anything less than 50%. If you do, then continue at your own risk.
1. Go to this thread http://forum.xda-developers.com/showthread.php?t=1081930 and pick out a ROM you think that you would like. I WOULD NOT RECOMMEND ANY GINGERBREAD ROMS. These are still in ALPHA.
2. After you have the ROM downloaded, plug your phone into you computer and put the ROM anywhere on your sd-card. I made a new folder called ROMs and put all my ROMs in there. This keeps things tidy.
3. THIS IS OPTIONAL, but saves you a lot of time in the future. Download Titanium Backup. I would HIGHLY recommend the PRO option. Costs money now, but will save you hours in the future. This program needs root. It will backup all your apps with their data so when you switch ROMs, everything is restored easily and fairly quickly. If you go with this approach, then open TB and backup all USER APPS with DATA. DO NOT BACK UP SYSTEM APPS!!!
4. If you do not have Rom Manager, Download it now. Free is fine. Open up Rom Manager and make sure you have the latest Clockwork Recovery installed. If you don't, then install it. If everything is fine, click the option to boot into recovery. While some people use RM to install the ROMs, I find its better to do it manually.
5. When in Clockwork, go to backup and restore(hit power or home button to choose highlighted option). Choose Backup and let it do its thing.
6. When done, press the menu key until it goes to the main menu.
7. Choose Wipe data/factory reset and let it wipe the data. Do not worry, this will not touch your sd-card. All your pictures, movies, music, ROMs, and everything else on the sdcard will still be there.
8. Go into install zip from sdcard and choose "choose zip from sdcard"
9. Navigate to where you put your ROM from STEP 2
10. Choose the ROM and let it do its thing
11. Press Menu button to go back to main screen and REBOOT
12. ALLOW LOTS OF TIME TO LOAD UP. First boot always takes a long time, dont worry about it.
13. When booted up, ALLOW EVERYTHING TO LOAD. Now enjoy your ROM.
14. If you used Titanium Backup, get it from the market(if it isn't pre-installed). If you payed for it, you won't have to pay for it again as long as you use the same GMAIL account that you used before. All paid apps are saved to your gmail account. Restore all USER APPS with DATA. NOT SYSTEM APPS!
I am by no means a dev or claim to be a genius. I've been around since when the OG droid first came out and I'm just helping out. I am not responsible if something goes wrong. If anyone see's a mistake in this, please point it out or add a step if you want.
gujupmp88 said:
I'm still not sure what the question is here...but i'll lay some steps out for you.
FIRST AND FOREMOST: HAVE AMPLE BATTERY CHARGE!! I don't flash with anything less than 50%. If you do, then continue at your own risk.
1. Go to this thread http://forum.xda-developers.com/showthread.php?t=1081930 and pick out a ROM you think that you would like. I WOULD NOT RECOMMEND ANY GINGERBREAD ROMS. These are still in ALPHA.
2. After you have the ROM downloaded, plug your phone into you computer and put the ROM anywhere on your sd-card. I made a new folder called ROMs and put all my ROMs in there. This keeps things tidy.
3. THIS IS OPTIONAL, but saves you a lot of time in the future. Download Titanium Backup. I would HIGHLY recommend the PRO option. Costs money now, but will save you hours in the future. This program needs root. It will backup all your apps with their data so when you switch ROMs, everything is restored easily and fairly quickly. If you go with this approach, then open TB and backup all USER APPS with DATA. DO NOT BACK UP SYSTEM APPS!!!
4. If you do not have Rom Manager, Download it now. Free is fine. Open up Rom Manager and make sure you have the latest Clockwork Recovery installed. If you don't, then install it. If everything is fine, click the option to boot into recovery. While some people use RM to install the ROMs, I find its better to do it manually.
5. When in Clockwork, go to backup and restore(hit power or home button to choose highlighted option). Choose Backup and let it do its thing.
6. When done, press the menu key until it goes to the main menu.
7. Choose Wipe data/factory reset and let it wipe the data. Do not worry, this will not touch your sd-card. All your pictures, movies, music, ROMs, and everything else on the sdcard will still be there.
8. Go into install zip from sdcard and choose "choose zip from sdcard"
9. Navigate to where you put your ROM from STEP 2
10. Choose the ROM and let it do its thing
11. Press Menu button to go back to main screen and REBOOT
12. ALLOW LOTS OF TIME TO LOAD UP. First boot always takes a long time, dont worry about it.
13. When booted up, ALLOW EVERYTHING TO LOAD. Now enjoy your ROM.
14. If you used Titanium Backup, get it from the market(if it isn't pre-installed). If you payed for it, you won't have to pay for it again as long as you use the same GMAIL account that you used before. All paid apps are saved to your gmail account. Restore all USER APPS with DATA. NOT SYSTEM APPS!
I am by no means a dev or claim to be a genius. I've been around since when the OG droid first came out and I'm just helping out. I am not responsible if something goes wrong. If anyone see's a mistake in this, please point it out or add a step if you want.
Click to expand...
Click to collapse
The rom can't be in a folder on your SD card when flashing it has to be on the root of the SD card.
Sent from my HTC Thunderbolt BAMF ROM OF DEATH
Yes the rom can be in a folder. Only radios cannot be flashed from folders.
Sent from my ADR6400L using XDA App
jaysckap said:
The rom can't be in a folder on your SD card when flashing it has to be on the root of the SD card.
Sent from my HTC Thunderbolt BAMF ROM OF DEATH
Click to expand...
Click to collapse
Actually it can......FYI
Sent from my PC36100 using XDA App
thoerr said:
Yes the rom can be in a folder. Only radios cannot be flashed from folders.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Agreed... ROM does CAN be in a folder... Radios or baseball updates cannot...
Persiandeity said:
Agreed... ROM does CAN be in a folder... Radios or baseball updates cannot...
Click to expand...
Click to collapse
Sorry bout that I stand corrected. I have never done it that way. I guess you do learn something new everyday
Sent from my HTC Thunderbolt BAMF ROM OF DEATH
Thanks for the replies. For not knowing what the question was, it sure was answered pretty thoroughly.
I did buy Ti Pro a while back and use it a lot. That should be no problem once I figure out why I am not rooted now. I did the whole routine yesterday and Ti cant get su for some reason now.... yay for that. I guess I will try the whole thing again. (It may be that I need to get the proper busybox for Ti Pro to work and be allowed su)
So if I have read this correctly, I will be alright with the debloat ROM I mentioned earlier right? Since it is not gingerbread based right?
oastl: You said don't use ROM Manager then after one sentence you then say to use ROM Manager.... Using ROM Manager to boot into recovery must be a different thing altogether I suppose...
Thanks again for the help... Very much appreciated!
danktankk said:
Thanks for the replies. For not knowing what the question was, it sure was answered pretty thoroughly.
I did buy Ti Pro a while back and use it a lot. That should be no problem once I figure out why I am not rooted now. I did the whole routine yesterday and Ti cant get su for some reason now.... yay for that. I guess I will try the whole thing again. (It may be that I need to get the proper busybox for Ti Pro to work and be allowed su)
So if I have read this correctly, I will be alright with the debloat ROM I mentioned earlier right? Since it is not gingerbread based right?
oastl: You said don't use ROM Manager then after one sentence you then say to use ROM Manager.... Using ROM Manager to boot into recovery must be a different thing altogether I suppose...
Thanks again for the help... Very much appreciated!
Click to expand...
Click to collapse
That ROM is safe. And yes use rom manager just to boot into recovery
Sent from my HTC Thunderbolt BAMF ROM OF DEATH
jaysckap said:
The rom can't be in a folder on your SD card when flashing it has to be on the root of the SD card.
Sent from my HTC Thunderbolt BAMF ROM OF DEATH
Click to expand...
Click to collapse
My ROMS are always in folders when I flash them on my devices and it has worked just fine!
jaysckap said:
The rom can't be in a folder on your SD card when flashing it has to be on the root of the SD card.
Sent from my HTC Thunderbolt BAMF ROM OF DEATH
Click to expand...
Click to collapse
If you're using CWR (which i think is the only option these days?) you totally can. Just choose "install from SD card" and it'll let you navigate your folders. I have a neatly organized "RUU" folder on my SD card. Certain things like radios need to pushed as pg05img.zip on the root of the SD card.
Yufice said:
If you're using CWR (which i think is the only option these days?) you totally can. Just choose "install from SD card" and it'll let you navigate your folders. I have a neatly organized "RUU" folder on my SD card. Certain things like radios need to pushed as pg05img.zip on the root of the SD card.
Click to expand...
Click to collapse
I guess I'm old school and never used that method
Sent from my HTC Thunderbolt BAMF ROM OF DEATH
Well, with all the help, I did manage to get everything back as it should be. Thanks a lot for that too!
I got super tired of trying to get someone to answer me in IRC. I think I will just come here with my questions from now on and leave that place to those who have the patience for it.
I also got too used to BAMF I think because I ended up flashing to 1.7 anyway... 2.0 looks really good. I think that is still in Beta or I read the post wrong altogether...
Im curious as to which recovery is working the best with the Galaxy Note 10.1. Im not asking which is the best, but I see darkman has come out with a touch version of cwm and I have the latest TWRP...Only issue i have is that it doesnt see my cwm backups....I havent had any issues with it yet though...Im just curious thats all
I always preferred cwm.. it is more stable.. use to love with twrp when I had asus tf101 but sometimes I couldnt see my internal sd card and sometimes I couldnt mount system.. but just use what works for you..
Sent from my GT-N8013 using XDA Premium HD app
txtmikhail said:
I always preferred cwm.. it is more stable.. use to love with twrp when I had asus tf101 but sometimes I couldnt see my internal sd card and sometimes I couldnt mount system.. but just use what works for you..
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the input.... I do have to constantly tap the external sd option because it takes me back to the main screen. Im assuming its a sensitivity issue
txtmikhail said:
I always preferred cwm.. it is more stable.. use to love with twrp when I had asus tf101 but sometimes I couldnt see my internal sd card and sometimes I couldnt mount system.. but just use what works for you..
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
Agreed. I've found CWM to be very stable. I loved to move to the touch version, though you have to be careful sometimes about accidentally touching an unwanted option. But since a confirmation menu comes up for each option that makes changes, you can easily correct it.
I have used CWM on all my devices and have worked without an itch so prefer CWM
Tried install TWRP on my device once it refused to install contacted the developers did not get the response so ditched it.
Twerp don't seem to get on with note .
But i would say their is very little difference between using TWRP or CWM for most users .
I use TWRP on SGS3 and CWM on Note .
jje
I moved to TWRP awhile ago for my phones and currently use it on my Note. As far as stability goes CWM is much more stable, though I have it tried the touch version(thinking of checking it out though.) TWRP is a little wonky sometimes,but I think that's a sensitivity issue.
As another poster already said, there's no real big difference between the two and they both get the job done.
My big problem with CWM is the backups. Maybe I didn't spend enough time with it or missed an option somewhere. But since they moved to the BLOB model for backups I found it impossible to delete an old backup. I like to do backups often, but I usually only want to keep 2 iterations due to the space they take up. With TWRP it's easy, each backup has it's own folder. Want to delete one, just delete the whole folder.
If someone can tell me how to manage backups properly in CWM I'd be glad to switch back.
midas69 said:
My big problem with CWM is the backups. Maybe I didn't spend enough time with it or missed an option somewhere. But since they moved to the BLOB model for backups I found it impossible to delete an old backup. I like to do backups often, but I usually only want to keep 2 iterations due to the space they take up. With TWRP it's easy, each backup has it's own folder. Want to delete one, just delete the whole folder.
If someone can tell me how to manage backups properly in CWM I'd be glad to switch back.
Click to expand...
Click to collapse
That's one of the reasons I stay with TWRP on my Note despite the super sensitive touch. In all it's wonkiness I've just become more of a fan due to the ease of the touch UI and the ability to just delete the backup folder.
insanecrane said:
That's one of the reasons I stay with TWRP on my Note despite the super sensitive touch. In all it's wonkiness I've just become more of a fan due to the ease of the touch UI and the ability to just delete the backup folder.
Click to expand...
Click to collapse
same thinking for me too..
midas69 said:
My big problem with CWM is the backups. Maybe I didn't spend enough time with it or missed an option somewhere. But since they moved to the BLOB model for backups I found it impossible to delete an old backup. I like to do backups often, but I usually only want to keep 2 iterations due to the space they take up. With TWRP it's easy, each backup has it's own folder. Want to delete one, just delete the whole folder.
If someone can tell me how to manage backups properly in CWM I'd be glad to switch back.
Click to expand...
Click to collapse
Easiest way I've found to manage backups with CWM is to use ROM Manager. It's integrated with CWM such that in the app you ask it to do a backup, you name the backup anything you want, then it automatically reboots into recovery and does it. ROM Manager also allows you to download your backups to you computer via WiFi, and has an easy option to delete backups. Further, CWM has the option to restore data only from a backup for easily getting settings back when doing a ROM upgrade. Geez I'm more sold on CWM than I thought. I almost sound likes a salesperson haha.
glopact said:
Geez I'm more sold on CWM than I thought. I almost sound likes a salesperson haha.
Click to expand...
Click to collapse
Don't apologize, you provided good information. On my HP Touchpad I used TWRP exclusively because it integrated with Goo Manager. But I really don't plan to use anything other than Mobile Odin to flash anything so not much reason to keep it. I may switch back to CWM and try the ROM Manager interface for the backups.
EDIT:
Well that didn't work well at all. Installed and tried to do a backup. Told me (obviously) that I needed CWM installed. Said there wasn't an official version for it so it then asked me if I already had one installed. I answered yes. It then asked if I had version 2 or version 3. But what I have installed has a version number of 6 something. Oh well, back to TWRP I guess.
I thought we could manager the CWM backup from a file manager I have been doing that on my optimus 2x never did it on note though
samir_a said:
I thought we could manager the CWM backup from a file manager I have been doing that on my optimus 2x never did it on note though
Click to expand...
Click to collapse
With older versions I was able to do that. But this newer version I have installed doesn't really work that way. It creates 2 folders for a backup. One has the backup name with just a small file inside. The other folder is called BLOBS. In that fold are multiple other folders that are alphabetical, I assume by file name. The problem is, when you create a 2nd backup, it used the same BLOBS folder. So there is no way to just delete one folder to delete a complete backup.
yes I remember that when I was trying to delete CWM backup files and did not find them. Thanks for the update
---------- Post added at 09:00 PM ---------- Previous post was at 08:59 PM ----------
A noob method try to sort by date/time should tell you which files were updated during your last backup and will give you an idea how the update works. Let me do some R&D on it
I just don't want to have to manually delete files from 20+ directories when, with TWRP, I can just delete one folder.
samir_a said:
I thought we could manage the CWM backup from a file manager ...?
Click to expand...
Click to collapse
midas69 said:
With older versions I was able to do that. But this newer version I have installed doesn't really work that way. It creates 2 folders for a backup. One has the backup name with just a small file inside. The other folder is called BLOBS ...
Click to expand...
Click to collapse
Change the backup format to "tar" and you'll get the old directory structure back.
I just installed the newest version of TWRP and seem to be having some issues with creating backups. My last backup was on the internal memory so I wanted to put something on my SD Card before I tried flashing a new ROM. The first thing that I tried was to just copy it over to the SD Card but it says that I can't copy it. So then I tried to just do another backup in TWRP and have it save right to the SD Card. It completes successfully, but it saves it as some weird folder name (it adds cm_d2vzw-userdebug 4.2.2 and some other stuff to the end of the folder name). I can only see it in ES Explorer on my phone for some reason, if I hook it up to the computer it won't even show the TWRP folder that gets created.
What is wrong? Is it an issue with the latest TWRP?
EDIT: I just tried backing up to internal storage too and it is still doing that funny thing with the folder name. I am thinking it is a recovery issue. Does anyone have the latest version working right?
Im on the latest version 2.6.0.31 some weird number like that. U might have a bad install of twrp try reinstalling it. The only prom i had was wen i moved a backup file using astro manager to my extsdcard i couldn't flash it. So what i did wen u go into twrp backup click on top change it to extcard storage... Hope u get it fix
twistedillutions said:
Im on the latest version 2.6.0.31 some weird number like that. U might have a bad install of twrp try reinstalling it. The only prom i had was wen i moved a backup file using astro manager to my extsdcard i couldn't flash it. So what i did wen u go into twrp backup click on top change it to extcard storage... Hope u get it fix
Click to expand...
Click to collapse
I used GooManager to update to the latest, should I do it another way?
xceebeex said:
I used GooManager to update to the latest, should I do it another way?
Click to expand...
Click to collapse
Try ezunlock i think thats wat is called from Google play. If not go to cyanmode recovery
I tried installing again through goomanager and it still doesn't work. I wonder if I should just go back to 2.6.0.1 or whatever I was on.
Sent from my SCH-I535 using Tapatalk
xceebeex said:
I tried installing again through goomanager and it still doesn't work. I wonder if I should just go back to 2.6.0.1 or whatever I was on.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Verify that root is still working (download root checker), then uninstall goomanager, reboot, reinstall goomgr then give it another try.
buhohitr said:
Verify that root is still working (download root checker), then uninstall goomanager, reboot, reinstall goomgr then give it another try.
Click to expand...
Click to collapse
Why wouldn't root still be working? Doesn't goomanager have to check root first before installing a recovery? Plus, ES Explorer still had root access and titanium backup still works.
Sent from my SCH-I535 using Tapatalk
xceebeex said:
Why wouldn't root still be working? Doesn't goomanager have to check root first before installing a recovery? Plus, ES Explorer still had root access and titanium backup still works.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Try this :
http://forum.xda-developers.com/showthread.php?t=2492496
If none of that works, then try to use a flashable zip from here and flash it in recovery:
http://forum.xda-developers.com/showthread.php?t=2153408
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Try this :
http://forum.xda-developers.com/showthread.php?t=2492496
If none of that works, then try to use a flashable zip from here and flash it in recovery:
http://forum.xda-developers.com/showthread.php?t=2153408
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried flashing the .img file and tried the zip and I am still having the same issue. Is it possible permissions got screwed up somewhere? I just installed the 2.6.3.0 (instead of the 2.6.3.1) and am trying a backup to see if that works.
I might just go back to by backup from a day or two ago when everything was working before I tried going to the latest version of TWRP.
EDIT: Well 2.6.3.0 didn't work either. It is weird that I can't see the folder that it creates on my laptop. I can only see it on my phone with ES Explorer and it is still naming the folder really weird things.
EDIT2: I reinstalled 2.6.0.1 and now it names the folder right (just using the date/time), but I still can't see it when I plug in to my computer. I am afraid to try and restore to it to see if it works. I don't understand why I can't see it when I plug in to my laptop.
xceebeex said:
EDIT: Well 2.6.3.0 didn't work either. It is weird that I can't see the folder that it creates on my laptop. I can only see it on my phone with ES Explorer and it is still naming the folder really weird things.
EDIT2: I reinstalled 2.6.0.1 and now it names the folder right (just using the date/time), but I still can't see it when I plug in to my computer. I am afraid to try and restore to it to see if it works. I don't understand why I can't see it when I plug in to my laptop.
Click to expand...
Click to collapse
I haven't really followed this thread's progression so forgive me, but you can just tap the bar where it reads "Backup Name: (Auto Generate)" to manually change your TWRP backup names. It's not immediately obvious but its there.
SlimSnoopOS said:
I haven't really followed this thread's progression so forgive me, but you can just tap the bar where it reads "Backup Name: (Auto Generate)" to manually change your TWRP backup names. It's not immediately obvious but its there.
Click to expand...
Click to collapse
Yea, I understand that, but I don't understand why it is adding stuff like userdebug and a bunch of other stuff automatically when the older version didn't. Then on top of that, while it appears like it worked and I could see the files using ES Explorer, when I hooked it up to my laptop, it wasn't even seeing the TWRP top level folder on the SD Card.
xceebeex said:
Yea, I understand that, but I don't understand why it is adding stuff like userdebug and a bunch of other stuff automatically when the older version didn't.
Click to expand...
Click to collapse
I guess this is a difference of opinion then cuz I don't see it as an issue.
Then on top of that, while it appears like it worked and I could see the files using ES Explorer, when I hooked it up to my laptop, it wasn't even seeing the TWRP top level folder on the SD Card.
Click to expand...
Click to collapse
Can you view the rest of your internal storage on your laptop? I mean the exact same directory as to where your TWRP storage is located? You are running a KitKat rom which changes the internal storage directories from /sdcard to /0/sdcard (JB 4.3 does as well) so I'd guess that might have something to do with it. I always use Airdroid to transfer files to/from my laptop and I see my newly constructed internal storage fine. I have a MBP so I don't really have a native way to connect my S3 to my laptop to test it out which is why I use AirDroid.
Hey guys, I'm rather new to the world of customising Android devices. I just have SO MANY QUESTIONS right now. And I'm sure I'm not the only one, which is why I created this thread to help myself and other people.
Basically, I'll be asking a bunch of questions related to the topic, and this can help other people who are new to all this too.
So, I've got a rooted device. It's on lollipop 5.0, has an unlocked bootloader, TWRP recovery, and Xposed framework.
A few questions to start off with:
1) Can I flash multiple .zip/.img files one after another? Or do I need to always wipe my phone's cache after each flash?
2) Say I wanna update TWRP recovery. Do I have do something before flashing it? CAN I flash a newer version over the previous one?
3) Same question as 2) but for Xposed framework instead.
4) I have Xposed framework installed with some modules running on my phone. Should I disable these modules before updating my Xposed?
5) The latest version of Xposed is v86 as given here: http://forum.xda-developers.com/showthread.php?t=3034811
Can v86 work for lollipop?
6) Similarly, can one download any TWRP version and flash it for their device? Or do each build have a different, specific version of TWRP?
7) Are the latest recovery mods and Xposed frameworks always guaranteed to be stable? Or is it safer to stay on the older ones? Which ones would you recommend?
8) Now, the custom ROMS. What are the necessary things to do before flashing one of these?
9) After flashing a custom ROM, can you flash another on top of it? Or do you have to restore back to your original stock ROM?
10) Does flashing and switching between custom ROMs cause any damage to the phone? Or is there any such potential?
11) Since backing up is a must, I'll ask some about that too. Which would you suggest to be the best backing up method?
12) Does creating a NANDroid backup or a backup from within custom recovery(TWRP in my case) equal to creating a backup of stock ROM?
13) Do I need to copy that backup into PC(to restore later), or will it be safe in my phone's memory after flashing a custom ROM?
I guess that's about it for now. Everyone, please answer if you have done these before. And of course, add your own questions too. This can save a lot of time for a lot of people. I could add more questions in if people request it.
**Answer mentioning the question number for simplicity of searching.
Answers!
1) Can I flash multiple .zip/.img files one after another? Or do I need to always wipe my phone's cache after each flash?
Click to expand...
Click to collapse
You can, but it is more recommended to wipe cache and dalvik cache with each flash.
2) Say I wanna update TWRP recovery. Do I have do something before flashing it? CAN I flash a newer version over the previous one?
Click to expand...
Click to collapse
You'll have to wipe dalvik cache and cache and just flash it normally. It might be stuck at 90% but a force reboot fixes it. It is because you are already in recovery. If it is stuck, leave it for 15 mins and come back. This is just to ensure that it really is stuck.
3) Same question as 2) but for Xposed framework instead.
Click to expand...
Click to collapse
Yep, works, except you wont be stuck.
4) I have Xposed framework installed with some modules running on my phone. Should I disable these modules before updating my Xposed?
Click to expand...
Click to collapse
No need
5) The latest version of Xposed is v86 as given here: http://forum.xda-developers.com/showthread.php?t=3034811
Can v86 work for lollipop?
Click to expand...
Click to collapse
Yup, just flash it via recovery
6) Similarly, can one download any TWRP version and flash it for their device? Or do each build have a different, specific version of TWRP?
Click to expand...
Click to collapse
Each build is different for each device, so for example, I can't flash a TWRP for s7 edge on my s4.
7) Are the latest recovery mods and Xposed frameworks always guaranteed to be stable? Or is it safer to stay on the older ones? Which ones would you recommend?
Click to expand...
Click to collapse
In example, xposed and supersu framework and binary lets you choose if you want a stable file or a test one for developers. TWRP and other stuff have (what I know) different versions and as stated, these versions behave different on different device. During testing with my S4, I found that TWRP 2.8.7.0 is the most stable build for my device.
8) Now, the custom ROMS. What are the necessary things to do before flashing one of these?
Click to expand...
Click to collapse
Make a nandroid backup of your whole device and back it up on you computer. Then wipe everything except your external sdcard and either store it on an sdcard or "adb sideload" it.
9) After flashing a custom ROM, can you flash another on top of it? Or do you have to restore back to your original stock ROM?
Click to expand...
Click to collapse
Not on top of it, you'll have to do as the answer to question 8, make a backup, wipe everything and then flash. No need to go back to stock ROM and then flash it
10) Does flashing and switching between custom ROMs cause any damage to the phone? Or is there any such potential?
Click to expand...
Click to collapse
There is always the risk of bricking but as far as software, it is always revertable. As long as you have a backup of course.
11) Since backing up is a must, I'll ask some about that too. Which would you suggest to be the best backing up method?
Click to expand...
Click to collapse
Nandroid backup is the best one.
12) Does creating a NANDroid backup or a backup from within custom recovery(TWRP in my case) equal to creating a backup of stock ROM?
Click to expand...
Click to collapse
It creates a backup of your current state, lets say, you are in Cyanogenmod 13, making a Nandroid backup will backup everything on cyanogenmod so that if you flash another ROM and still want to go back, you'll have everything restored, including app data and apps.
13) Do I need to copy that backup into PC(to restore later), or will it be safe in my phone's memory after flashing a custom ROM?
Click to expand...
Click to collapse
It will take up a lot of space on your device (since it is a backup of your whole device) so it is recommended to copy it to your computer and remove it from the phone. But, as always, make sure you copy the whole "BACKUPS" folder because the folder inside that folder has your device ID and it is required by TWRP to have the folder the exact ID of your phone to prevent anything bad from happening (bricks).
Hope, I answered all the questions as you wanted and if you have a new question, post it here and I'll reply as soon as possible
Hey, thanks a lot for answering. It helps a lot.
A few other questions I have:
14) So if I were to get CM13, and then create a backup of it, and then get another rom, say ASOP, create a backup of that too, and then switch to yet another rom, say Resurrection Remix, create a backup of that too.
Now, is it possible for me to be able to SWITCH between multiple roms, with ALL my data saved individually on each rom perfectly the way I wanted?(of course, wipe cache and data before restoring the backup)
If so, then I could just keep Nandroids of my favorite roms, can keep switching between them, never having to flash and start from scratch ever again!
Sent from my ASUS_T00J using XDA-Developers mobile app
15) Since I don't have otg cable, nor an sd card reader, I'm gonna have to keep the nandroid on my sd. Which means a lot of space is needed.
Can this workaround be possible:
- I use TWRP to backup only system and boot data. I save this on sd card.
- I use Titanium backup to save only user app and data. I save this on PC.
So now, when my device crashes while flashing something, I can restore backup from TWRP(do I clear cache and data before this as well?), and once my system rom is back, I can copy titanium backup via USB and restore it.
Sent from my ASUS_T00J using XDA-Developers mobile app
16) Suppose I flashed CM13, and it's really buggy. Can I switch back to the previous rom whose nandroid I had just by restoring it? Is it really that simple?
Sent from my ASUS_T00J using XDA-Developers mobile app
ShinraTensei04 said:
Hey, thanks a lot for answering. It helps a lot.
A few other questions I have:
14) So if I were to get CM13, and then create a backup of it, and then get another rom, say ASOP, create a backup of that too, and then switch to yet another rom, say Resurrection Remix, create a backup of that too.
Now, is it possible for me to be able to SWITCH between multiple roms, with ALL my data saved individually on each rom perfectly the way I wanted?(of course, wipe cache and data before restoring the backup)
If so, then I could just keep Nandroids of my favorite roms, can keep switching between them, never having to flash and start from scratch ever again!
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
14) You can, but you would need tons of space.
Sent using a ks01lte (gt-i9506) running cm 13
---------- Post added at 05:59 AM ---------- Previous post was at 05:56 AM ----------
ShinraTensei04 said:
15) Since I don't have otg cable, nor an sd card reader, I'm gonna have to keep the nandroid on my sd. Which means a lot of space is needed.
Can this workaround be possible:
- I use TWRP to backup only system and boot data. I save this on sd card.
- I use Titanium backup to save only user app and data. I save this on PC.
So now, when my device crashes while flashing something, I can restore backup from TWRP(do I clear cache and data before this as well?), and once my system rom is back, I can copy titanium backup via USB and restore it.
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
You do not have to have an sdcard reader to view your sdcard on your PC. You know how when you make a backup it is stored in /sdcard/TWRP/BACKUPS/CERIALNM/nameofbackup? Well, connect your phone to your pc and move the "backups" folder, then, when you need to restore it, add it to the twrp folder and restore it.
Sent using a ks01lte (gt-i9506) running cm 13
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
ShinraTensei04 said:
15) Since I don't have otg cable, nor an sd card reader, I'm gonna have to keep the nandroid on my sd. Which means a lot of space is needed.
Can this workaround be possible:
- I use TWRP to backup only system and boot data. I save this on sd card.
- I use Titanium backup to save only user app and data. I save this on PC.
So now, when my device crashes while flashing something, I can restore backup from TWRP(do I clear cache and data before this as well?), and once my system rom is back, I can copy titanium backup via USB and restore it.
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
Also, on the titanium backup part, not a bad idea... You can then copy the data and system or boot to your pc and bam.
Sent using a ks01lte (gt-i9506) running cm 13
What I meant was: Let's say I bricked my phone. Now, according to you, I place backup on pc. Okay. But now, how do I place this backup onto the sd on my phone when my pc can't even detect the phone(cuz it's dead yo). Doesn't this impose on me to keep the backup in sd(as I don't have reader or otg).
About the titanium, so you're saying I can do that? Backup only user apps+data and restore after restoring only system+boot.
Another question:
16) Can the backup of user apps+data made on, say, 'X' rom, be restored on 'Y' rom via titanium, on condition they are same Android version(suppose 5.0), without ANY chance of incompatibility. More importantly, can it have any chances of leading to a brick/bootloop.
* I read somewhere that if you backed up system apps of 'X' rom, then changed to 'Y' rom, and restored the system apps of 'X' rom onto 'Y' rom, it bricks the phone.(which is why I ask this question)
17) "Backing up 'system' in TWRP is completely different from backing up 'system' on titanium. This is because TWRP backs up entire system with system apps, while titanium only backs up the apps." This is true, right?
Sent from my ASUS_T00J using XDA-Developers mobile app
ShinraTensei04 said:
What I meant was: Let's say I bricked my phone. Now, according to you, I place backup on pc. Okay. But now, how do I place this backup onto the sd on my phone when my pc can't even detect the phone(cuz it's dead yo). Doesn't this impose on me to keep the backup in sd(as I don't have reader or otg).
About the titanium, so you're saying I can do that? Backup only user apps+data and restore after restoring only system+boot.
Another question:
16) Can the backup of user apps+data made on, say, 'X' rom, be restored on 'Y' rom via titanium, on condition they are same Android version(suppose 5.0), without ANY chance of incompatibility. More importantly, can it have any chances of leading to a brick/bootloop.
* I read somewhere that if you backed up system apps of 'X' rom, then changed to 'Y' rom, and restored the system apps of 'X' rom onto 'Y' rom, it bricks the phone.(which is why I ask this question)
17) "Backing up 'system' in TWRP is completely different from backing up 'system' on titanium. This is because TWRP backs up entire system with system apps, while titanium only backs up the apps." This is true, right?
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
You adb sideload a functioning ROM and once you boot you copy the backup you can flash it via twrp. As for the second question, I have not tested it but it sounds possible.
16) You should not be in a bootloop if you backup like that, the fact that it is even the same android version is making it more likely to work and what I know, you can even switch the backup via phones. I don't use titanium because I always do nandroid backups.
17) Yup, that's true, twrp sees "system as the partition system while titanium sees it as the whole phones software, hence why it is called " system".
Thanks for asking these question and hopefully some day, you can teach others.
RAZERZDAHACKER said:
You adb sideload a functioning ROM and once you boot you copy the backup you can flash it via twrp. As for the second question, I have not tested it but it sounds possible.
16) You should not be in a bootloop if you backup like that, the fact that it is even the same android version is making it more likely to work and what I know, you can even switch the backup via phones. I don't use titanium because I always do nandroid backups.
17) Yup, that's true, twrp sees "system as the partition system while titanium sees it as the whole phones software, hence why it is called " system".
Thanks for asking these question and hopefully some day, you can teach others.
Click to expand...
Click to collapse
Hm... so whenever I brick my phone, I MUST adb sideload to a working rom first, and only then restore the backup I made? Even if I already have a backup saved onto the sd card of my bricked phone? Can I not restore that via TWRP instead? I ask this because if I were to adb sideload first, I'd lose root, unlocked bootloader, and yes, TWRP. So, I'd have to get ALL that done again, and only then restore my backup.
18) Does restoring a backup I made(when I had root access, unlocked BL, custom recovery, xposed) RETAIN all that? Meaning after I restore to that backup, I will still have all that.
Thanks for answering, I'm learning quite a bit. And yeah, I'll make sure to help others with this information too.
ShinraTensei04 said:
Hm... so whenever I brick my phone, I MUST adb sideload to a working rom first, and only then restore the backup I made? Even if I already have a backup saved onto the sd card of my bricked phone? Can I not restore that via TWRP instead? I ask this because if I were to adb sideload first, I'd lose root, unlocked bootloader, and yes, TWRP. So, I'd have to get ALL that done again, and only then restore my backup.
Click to expand...
Click to collapse
You won't lose TWRP or unlocked bootloader, but I will try today by making backup of "cache" and flash it via my sdcard as soon as possible.
18) Does restoring a backup I made(when I had root access, unlocked BL, custom recovery, xposed) RETAIN all that? Meaning after I restore to that backup, I will still have all that.
Click to expand...
Click to collapse
Yup, it makes a backup of every little part of the system (if you include cache and dalvik, I don't, but some do).
Thanks for answering, I'm learning quite a bit. And yeah, I'll make sure to help others with this information too.
Click to expand...
Click to collapse
Okay, made a backup of "cache and the flashing went fine, my hypothesis is that you have to make the backup on the sdcard and not on the phone and move it to the sdcard.
RAZERZDAHACKER said:
You won't lose TWRP or unlocked bootloader, but I will try today by making backup of "cache" and flash it via my sdcard as soon as possible.
Click to expand...
Click to collapse
Actually, when you adb sideload, you need to flash stock fastboot and recovery .img files(at least for my phone), and the bootloader does in fact get locked again, along with losing root. I know cuz I already have done adb sideloading before. So, doesn't that make flashing backup via sd card and TWRP without sideload the only thing I can do? I'm just trying to keep a backup without losing root, unlocked BL, TWRP, even if I gotta give up some space... Just wanna make sure it's safe to do it like that.
RAZERZDAHACKER said:
Yup, it makes a backup of every little part of the system (if you include cache and dalvik, I don't, but some do).
Click to expand...
Click to collapse
I only have "System(1125 mb)", "Data(3480 mb)", and "Cache(0 mb)" listed in TWRP. My cache is 0 mb.... nothing to backup on there?
19) Do I have to unlink my linked apps before creating a Nandroid, or will creating one while linked allow me to retain the link even after wiping data and then restoring the Nandroid?
ShinraTensei04 said:
Actually, when you adb sideload, you need to flash stock fastboot and recovery .img files(at least for my phone), and the bootloader does in fact get locked again, along with losing root. I know cuz I already have done adb sideloading before. So, doesn't that make flashing backup via sd card and TWRP without sideload the only thing I can do? I'm just trying to keep a backup without losing root, unlocked BL, TWRP, even if I gotta give up some space... Just wanna make sure it's safe to do it like that.
Click to expand...
Click to collapse
You wont lose anything during a complete nandroid backup, and, apparently, some devices loose stuff during adb sideload.
I only have "System(1125 mb)", "Data(3480 mb)", and "Cache(0 mb)" listed in TWRP. My cache is 0 mb.... nothing to backup on there?
Click to expand...
Click to collapse
Nothing....... Yet.
19) Do I have to unlink my linked apps before creating a Nandroid, or will creating one while linked allow me to retain the link even after wiping data and then restoring the Nandroid?
Click to expand...
Click to collapse
Unlink? What do you mean? (Not quoting Justin Bieber)
RAZERZDAHACKER said:
Unlink? What do you mean? (Not quoting Justin Bieber)
Click to expand...
Click to collapse
There's this thing you can do where you move your apps from internal storage to sd card COMPLETElY, thereby saving a lot of space on internal memory. It works because a 'link' is created between the app+data(now in sd) back to it's internal location counterpart(where it would have been otherwise). This way, the apps and system think your apps are in internal, but in fact are in sd(you can see that more internal is free by checking space used up via any file manager though).
In order to do this, a second partition on the sd card is to be made with an ext2/ext4 format, and use a linking app( like Apps2sd).
ShinraTensei04 said:
There's this thing you can do where you move your apps from internal storage to sd card COMPLETElY, thereby saving a lot of space on internal memory. It works because a 'link' is created between the app+data(now in sd) back to it's internal location counterpart(where it would have been otherwise). This way, the apps and system think your apps are in internal, but in fact are in sd(you can see that more internal is free by checking space used up via any file manager though).
In order to do this, a second partition on the sd card is to be made with an ext2/ext4 format, and use a linking app( like Apps2sd).
Click to expand...
Click to collapse
Yea I've used one of those, I first thought the app used the "MV" Unix command but yea you need a sec. Partition to do that on the sdcard, but you don't have to do that on your nandroid backup.
RAZERZDAHACKER said:
Yea I've used one of those, I first thought the app used the "MV" Unix command but yea you need a sec. Partition to do that on the sdcard, but you don't have to do that on your nandroid backup.
Click to expand...
Click to collapse
So can I backup linked apps with their links' data saved, so when I install the linking app again, they can be relinked automatically?
Sent from my ASUS_T00J using XDA-Developers mobile app
Thanks for those questions and answers. I posted this before but appearantly in the wrong place. It seems to be quite right here. Thanks to helping people!
Hi XDA experts
I am newly registered in the forum, but experienced in modding (more or less). But I am (for now) strictly a user, not developer.
So far I got along very well, with my beloved Galaxy S4 jfltexx. I got from stock to rooted stock, from there to cm, instantly back to stock, used it for a long time and am just now on cm13 nightly, which is truly awesome!
It is so awesome that I would really like to help other people out, even if they have no idea about this. Meaning I wish to modify other peoples phones for them. However, when it comes to other peoples property I can't really fight my way through technical terms I don't understand anymore, hoping that the outcome will be as I wished. I pretty much know what most of all these technical terms mean, but I don't always understand how they are related to each other. I know, explaining this will take a while, but I would REALLY appreciate it if someone would take the time...
1) The bootloader, can it be replaced? What would be the purpose of that? UNLOCKING does not mean REPLACING, does it??
What do custom ROMs typically consist of? An entire working system? Parts of a working system? Sometimes this sometimes that?
I'm asking the question because I got the impression that some custom ROMs require the user to have a certain (usually stock) ROM in order to flash it. For example, if I had a Galaxy S6 edge running 5.1.1, could I upgrade to noble ROM Marshmallow?
I also have the feeling that the ROM or system or whatever is somewhat seperate from the kernel. What is this relation? Do custom ROMs not always come with a compatible kernel? Is there only one kernel compatible to the rest of the system, or is there a chance to run a system with a kernel not particularly designed for it? How to get a 'wrong' kernel?
Where to get stock ROMs and who provides them? If I wanted to upgrade from Lollipop to Marshmallow, but am rooted and don't get OTA updates, what do I do? Assuming that Nandroids are bound to a single device (e.g. MY phone) who can provide a stock ROM that runs on my device and how does he get it?
Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Is there ANY phone SOLD with open bootloader and root? A phone that actually wants its users to play with the system?
Thanks guys
NoBullsh1t said:
Thanks for those questions and answers. I posted this before but appearantly in the wrong place. It seems to be quite right here. Thanks to helping people!
Click to expand...
Click to collapse
It happnes alot that people post in wrong section
Hi XDA experts
I am newly registered in the forum, but experienced in modding (more or less). But I am (for now) strictly a user, not developer.
So far I got along very well, with my beloved Galaxy S4 jfltexx. I got from stock to rooted stock, from there to cm, instantly back to stock, used it for a long time and am just now on cm13 nightly, which is truly awesome!
Click to expand...
Click to collapse
Yup, kinda same, excpet im ks01lte but I moved from stock to rooted stock (5.1.1) then cm13, then stock + xposed 4.4.2 then cm11 and now back to cm13 nightly
It is so awesome that I would really like to help other people out, even if they have no idea about this. Meaning I wish to modify other peoples phones for them. However, when it comes to other peoples property I can't really fight my way through technical terms I don't understand anymore, hoping that the outcome will be as I wished. I pretty much know what most of all these technical terms mean, but I don't always understand how they are related to each other. I know, explaining this will take a while, but I would REALLY appreciate it if someone would take the time...
Click to expand...
Click to collapse
1) The bootloader, can it be replaced? What would be the purpose of that? UNLOCKING does not mean REPLACING, does it??
Click to expand...
Click to collapse
The bootloader can be replace, however, if you fail here, there is no comming back (you'll need a complete board replacement because the bootloader acts as a BIOS), the purpose of replacing it is various reasons, change of splash screen during boot etc. Some bootloaders are locked to only be able to flash certain ROMs (OEMs do this to not allow people to tinker with their devices) but it is nearly always un-lockable (except for some devices, I own an Acer tablet that has a locked bootloader that cant be un-locked) and no, unlocking it does not mean changing it.
What do custom ROMs typically consist of? An entire working system? Parts of a working system? Sometimes this sometimes that?
Click to expand...
Click to collapse
Yea, sometimes this sometimes that, in example, ported marshamllow touchwiz ROMs rely on some files in the stock ROM so the "update" doesn't take up much space.
I'm asking the question because I got the impression that some custom ROMs require the user to have a certain (usually stock) ROM in order to flash it. For example, if I had a Galaxy S6 edge running 5.1.1, could I upgrade to noble ROM Marshmallow?
Click to expand...
Click to collapse
That is because of the bootloader (again lol), from my experience with the s4, before flashing cm13, I had to go to 5.1.1 because of the bootloader was changed during the OTA, so as stated before, it only allowed a certain type of ROMs to be flashed.
I also have the feeling that the ROM or system or whatever is somewhat seperate from the kernel. What is this relation? Do custom ROMs not always come with a compatible kernel? Is there only one kernel compatible to the rest of the system, or is there a chance to run a system with a kernel not particularly designed for it? How to get a 'wrong' kernel?
Click to expand...
Click to collapse
The kernel tells the system what to do, some kernels are specified for battery optimization, so the kernel tells the cpu to slow down and save juice, while some other kernels offer the ability to overclock the device (mostly used on older devices to make it faster, but it drains more juice and can result into app crashing), the kernel, is not separated from the system, in fact, you can't even compile a ROM without a kernel. There is not only one kernel for lets say cm, you can flash another kernel, just make sure it is compatible with your android version. To get a wrong kernel, flash one that isn't for your device or android version.
Where to get stock ROMs and who provides them? If I wanted to upgrade from Lollipop to Marshmallow, but am rooted and don't get OTA updates, what do I do? Assuming that Nandroids are bound to a single device (e.g. MY phone) who can provide a stock ROM that runs on my device and how does he get it?
Click to expand...
Click to collapse
Your OEM provides them, samsung has a website called sammobile and uploads all the stock ROMs there. If you want to upgrade, just flash it via recovery or in your case, odin (for samsung phones). To give your backup to someone else, the other person must have the exact same phones, in example, you (jfltexx) can't give it to me (ks01lte), I must have jfltexx and then (assuming you did the backup on twrp) I'd have to change the serial number to my device.
Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Click to expand...
Click to collapse
Your hardware buttons will work on pure android (aosp), I don't see why not, you said you are running cm13, that is altered pure android and it works fine, see pure android as cm withou all the features.
Is there ANY phone SOLD with open bootloader and root? A phone that actually wants its users to play with the system?
Thanks guys
Click to expand...
Click to collapse
There are a few devices like that, one plus was a company that wanted to do that, it came with root, unlocked bootloader and cyanogenmod running, they separated unfortunatly and evolved to using "oxygen os" and does nor provide a un-locked bootloader but provides a simple tool to root and unlock. I don't know any companies that have unlocket bootloaders because they don't want the average consumer to mess up their device and blame it on the OEM.
"Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Your hardware buttons will work on pure android (aosp), I don't see why not, you said you are running cm13, that is altered pure android and it works fine, see pure android as cm withou all the features."
I mean is there like a website from google where I can dowoad a non device specific aosp and flash that to my S4 to make it run? Wouldn't there be for example drivers missing? Isn't that what I have to be greateful to Cyanogenmod for, making up to date android compatible with older devices?
---------- Post added at 07:49 PM ---------- Previous post was at 07:42 PM ----------
So I can actually make a jfltexx Nandroid and install it on another jfltexx by easily changing the serial number???
NoBullsh1t said:
"Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Your hardware buttons will work on pure android (aosp), I don't see why not, you said you are running cm13, that is altered pure android and it works fine, see pure android as cm withou all the features."
I mean is there like a website from google where I can dowoad a non device specific aosp and flash that to my S4 to make it run? Wouldn't there be for example drivers missing? Isn't that what I have to be greateful to Cyanogenmod for, making up to date android compatible with older devices?
Click to expand...
Click to collapse
Yes, be greatful, it is free, open source and full of active devs and memebers. I'm still not sure what you mean, do you mean on-screen navigation bar? Because you can change that in cyanogenmod settings.
---------- Post added at 07:49 PM ---------- Previous post was at 07:42 PM ----------
So I can actually make a jfltexx Nandroid and install it on another jfltexx by easily changing the serial number???
Click to expand...
Click to collapse
Yea, you know how your backup is located in /sdcard/TWRP/BACKUPS/SERIALNO? The device you want to flash it to should make a backup of the tiniest partition (usually cache, it's 5mb) and youll get acces to the serial number, then you just swap it and delete the tiniest partition.