Backup Apps? - Galaxy S 5 Q&A, Help & Troubleshooting

So, I have the S5(Obviously) and I like to play around with which of the ROMS I like best, but my only problem is having to redownload all my Apps. I can backup my contacts and messages easily and restore them, but when I try to backup/restoring my apps, i'm at a loss.
I've tried titanium backup but when I do I move the backups to my External SD Card so they don't get wiped when I flash it with a new ROM, but when I move them back or anything, it just shows nothing. So basically is there something i'm missing or is there another way to backup my apps+appdata so i'm not spending forever trying to redownload some of my apps?
Veru much appreciated and thanks in advance.

Why are you moving your backups? Why not just back them up to your external card?

You are half way there by using titanium backup........
TiBu can make a zip of your backup that can be restored through CWM.......
Done it myself many times.....
http://i.imgur.com/rVnFwJM.jpg

{
"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"
}
BUT.......If you choose to include app data in the backup zip, make sure the version of Android you are restoring it to, is the same as the version that was on your device when you made the backup.....
App data is *usually* OS version SPECIFIC......so it could be the case that the restored data won't 'play nice' with your new ROM if it's based on a different OS version......
Sent from my SM-G900F using Tapatalk

keithross39 said:
BUT.......If you choose to include app data in the backup zip, make sure the version of Android you are restoring it to, is the same as the version that was on your device when you made the backup.....
App data is *usually* OS version SPECIFIC......so it could be the case that the restored data won't 'play nice' with your new ROM if it's based on a different OS version......
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
This could work for me, but I don't have the donate version at the moment unfortunately. So is there another way to achieve this?
I didn't know this about android version but that's nice to know. i plan on sticking with Lolipop but i'll be sure to keep this in mind.

Sorry fella......
TiBu is the only app like this I've ever used....it's all I know.....
It was the first root level access app I purchased after rooting my first ever smartphone somewhere way back in the frozen past.....lol
For what it costs it is *the* single most useful app you'll ever buy......
http://i.imgur.com/rVnFwJM.jpg

Agreed, I bought it like 6 years ago, invaluable.

Check this Web page. .....
http://m.alternativeto.net/software/titanium-backup/
Might be something worth trying......
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
Sorry fella......
TiBu is the only app like this I've ever used....it's all I know.....
It was the first root level access app I purchased after rooting my first ever smartphone somewhere way back in the frozen past.....lol
For what it costs it is *the* single most useful app you'll ever buy......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
I don't doubt that, and I can probably buy it here next week or so after I gain some funds. SInce it the holidays I kinda went a little overboard on getting gifts. Haha
Ill probably do that though. Thanks for the help.
Just to make sure I got this right, so basically just open TiBu, backup al my aps and such, then run the "Create "update.zip", move it to me external SD card, flash the ROM, and afterwards just re-dl TiBu, and recover it usng the update.zip, correct?
EDIT: Thanks, i'll check out the site.

You don't use TiBu to 'flash' the zip......you use a custom recovery....
I've always used one version or another of CWM, I should think that you can use TWRP instead, but having not used that recovery, I can't say for certain.
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
You don't use TiBu to 'flash' the zip......you use a custom recovery....
I've always used one version or another of CWM, I should think that you can use TWRP instead, but having not used that recovery, I can't say for certain.
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Oh no, sorry I knew that you didn't use TiBu to flash the zip. xD Sorry, I use FlashFire for that. Shoulda used more detail or explain better last time.
1. Create the Backup
2. Create the Update.zip
3. Backup whatever else I feel I need to on my phone
4. Move it all to my external SD Card
5. Flash the ROM with FlashFire
6. After new ROM is installed and etc, re-download TiBu
7. Then under one of the recovery options, get all the apps from the Update.zip
8. Restore whatever else I backedup onto my External SD card.
9. ??
10. Profit
(9 and 10, couldn't help myself. xD)

Lol.....
In essence, correct......
Point 7 though......
You don't touch the zip.....no extracting or anything like that necessary.....
Simply boot into (custom CWM or TWRP) recovery (this won't work with stock recovery.....or even CM recovery), locate the update zip and flash like you would a ROM zip......nothing else needed......
Edit.....TiBu will be included in the update zip....
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
Lol.....
In essence, correct......
Point 7 though......
You don't touch the zip.....no extracting or anything like that necessary.....
Simply boot into (custom CWM or TWRP) recovery (this won't work with stock recovery.....or even CM recovery), locate the update zip and flash like you would a ROM zip......nothing else needed......
Edit.....TiBu will be included in the update zip....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Ooh ok, perfect, makes sense then. Thank you so much for the help.
Sent from my SM-G900V using Tapatalk

Exmix said:
Ooh ok, perfect, makes sense then. Thank you so much for the help.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
In my experience the update.zip hasn't worked for me in flashfire, might be better to just back up your apps to external, and then when you reflash it'll all still be there eon your external so long as you don't wipe it, then you boot and restore them in TiBu, that's what I do on my G900A since there's no recovery...
Sent from my SAMSUNG-SM-G900A using Tapatalk

Rakuu said:
In my experience the update.zip hasn't worked for me in flashfire, might be better to just back up your apps to external, and then when you reflash it'll all still be there eon your external so long as you don't wipe it, then you boot and restore them in TiBu, that's what I do on my G900A since there's no recovery...
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
At the moment FlashFire is my only option since I don't have a recovery either(Atleast I don't think so? If someone could tell me how to check to see if I do or not would be great)
But i'm gonna try on FlashFire at somepoint when I can get the Pro version of TiBu

Exmix said:
At the moment FlashFire is my only option since I don't have a recovery either(Atleast I don't think so? If someone could tell me how to check to see if I do or not would be great)
But i'm gonna try on FlashFire at somepoint when I can get the Pro version of TiBu
Click to expand...
Click to collapse
If you are currently running a custom ROM, then at the very least you have CM custom recovery....it is relatively easy to flash CWM or TWRP over the top of this, then you can use the newly installed recovery to flash the update zip......no need for Flashfire at all......
http://i.imgur.com/rVnFwJM.jpg
---------- Post added at 03:21 AM ---------- Previous post was at 03:12 AM ----------
To check which recovery you have, simply power the device off, then press and hold power, volume up and home buttons simultaneously until the phone begins to boot. Release all the keys and you'll be in recovery......
The text at the top of the screen will tell you which recovery you have.....
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
If you are currently running a custom ROM, then at the very least you have CM custom recovery....it is relatively easy to flash CWM or TWRP over the top of this, then you can use the newly installed recovery to flash the update zip......no need for Flashfire at all......
http://i.imgur.com/rVnFwJM.jpg
---------- Post added at 03:21 AM ---------- Previous post was at 03:12 AM ----------
To check which recovery you have, simply power the device off, then press and hold power, volume up and home buttons simultaneously until the phone begins to boot. Release all the keys and you'll be in recovery......
The text at the top of the screen will tell you which recovery you have.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Ah ok. I only ever had to do this on my Nexus 7 tablet and that was Power+Vol Down and when I tried it on this it didn't work and I never really had to need to check, so when I do this I get this:
Code:
Android system recovery <3e>
LRX2IT.G900VVRU2BOG5
Volume up/down to move highlight;
power button to select
reboot system now
apply update from ADP
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CDC-code : VZW
Successfully applied multi-CSC.
So I should be able to apply the update.zip from this menu from what im understanding, but which option would I choose? :X I assume the "Apply update from external storage".
Also, thank you again so much for the help, you've made this a tremendous learning experience.

Exmix said:
Ah ok. I only ever had to do this on my Nexus 7 tablet and that was Power+Vol Down and when I tried it on this it didn't work and I never really had to need to check, so when I do this I get this:
Code:
Android system recovery <3e>
LRX2IT.G900VVRU2BOG5
Volume up/down to move highlight;
power button to select
reboot system now
apply update from ADP
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CDC-code : VZW
Successfully applied multi-CSC.
So I should be able to apply the update.zip from this menu from what im understanding, but which option would I choose? :X I assume the "Apply update from external storage".
Also, thank you again so much for the help, you've made this a tremendous learning experience.
Click to expand...
Click to collapse
Hey no problem fella......
The text at the top says 3e which means stock recovery.....i'm guessing you are currently running a Samsung firmware....
Unfortunately you cannot flash the update zip from stock recovery.....
It *has* to be a custom recovery which would normally come as part of a custom rom......
Although, a standalone custom recovery can also be flashed on top of a stock firmware......just got to make sure the recovery you flash is compatible with the firmware.....
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
Hey no problem fella......
The text at the top says 3e which means stock recovery.....i'm guessing you are currently running a Samsung firmware....
Unfortunately you cannot flash the update zip from stock recovery.....
It *has* to be a custom recovery which would normally come as part of a custom rom......
Although, a standalone custom recovery can also be flashed on top of a stock firmware......just got to make sure the recovery you flash is compatible with the firmware.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Well i'm running the Phoenix ROM. So do you have any links or Tips on how to get a custom recovery onto mine so I can make this possible?
Like I had mentioned I really enjoy trying out new ROMs and wanna try more I just hate having to re-install all my APPs and such. =\
EDIT: I found this link here and it this seems liek it may work since i'm on the G900V version, but I just want a little confirmation on if this can work before I just jump right in. =P

I have a variant of the device that doesn't have a locked bootloader.....so (fortunately for me) I don't have to jump through the same loops as you do in order to modify my device.....
as a result, I'm not familiar with the processes needed for locked bootloader devices, I also cannot state what will or will not work with any certainty......
Having said that, I've been a member on here for some time, and whenever I've seen mention of Safe strap, it's generally been a positive comment.....speaking as someone who hasn't had to work around a locked bootloader, it would seem to be a good option, but if it were me, I'd be looking for some informed confirmation before I used it.......
Sorry I can't be any more help than that, but I really don't want to hand out advice that bricks somebody else's device.......
http://i.imgur.com/rVnFwJM.jpg

Related

[HOW TO] install CyanogenMod/MIUI to your phone

[CyanogenMod/MIUI]
This assumes that you are running stock froyo or gingerbread ROM:
1.first make sure your phone is rooted.If not,come here for detail.Specially for GB rooting,come here for tutorial.
2.download and install droid2bootstrap(attachment)
3.open droid2bootstrap and select install recovery
4.Install bootmenu v0.8.6. For more detail,come here
5.download CM7 All in one update.zip from here and then put it in your sdcard
6.reboot to bootmenu and then goto custom recoery
7.apply All in one update.zip(ROM package)
8.reboot to bootmenu again!
10.wipe data/cache
11.apply update again
12.reboot and everything should be OK
Specially,if you already get bootmenu v1.x.x working in your phone,you can skip step1~7.
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
[CyanogenMod]
This assumes that you are running MIUI:
1.reboot to bootmenu and then goto recovery
2.wipe data/cache
3.apply All in one update.zip(ROM package)
4.reboot and everything should be OK
Click to expand...
Click to collapse
This assumes that you are running CM7:
1.reboot to bootmenu and then goto recovery
2.wipe cache and dalvik cache in advance menu
3.apply All in one update.zip(ROM package)
4.reboot and everything should be OK
Specially,if you got some apps FC issues,first try to clear data for that app.And if you still get serious FCs,consider to make a full data wipe.
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
[MIUI]
This assumes that you are running CM7:
1.reboot to bootmenu and then goto recovery
2.wipe data/cache
3.apply All in one update.zip(ROM package)
4.reboot and everything should be OK
Click to expand...
Click to collapse
This assumes that you are running MIUI:
1.reboot to bootmenu and then goto recovery
2.wipe cache and dalvik cache in advance menu
3.apply All in one update.zip(ROM package)
4.reboot and everything should be OK
Specially,if you got some apps FC issues,first try to clear data for that app.And if you still get serious FCs,consider to make a full data wipe.
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
Questions
I have some questions ...
Firstly, with regard to the cm7 20111018-nightly v1.0, you mention that DEVTREE changed to UK2.2.2 and use CH2.6.0 kernel. Will the change in kernel appear in my phone ? (ie under kernel version)
Secondly, there is changes for the battd from uk2.2.2 (no battery jumping) Does it mean that the battery will not drop from 65% to 50 %?
Lastly, if I'm using the phone for mass storage and after i safely remove it, which is suppose to appear? ME722 or A953? (I'm from Asia region)
(I'm sorry, I cant post in the android development due to limited posts)
Thanks.
puiboy said:
I have some questions ...
Firstly, with regard to the cm7 20111018-nightly v1.0, you mention that DEVTREE changed to UK2.2.2 and use CH2.6.0 kernel. Will the change in kernel appear in my phone ? (ie under kernel version)
Secondly, there is changes for the battd from uk2.2.2 (no battery jumping) Does it mean that the battery will not drop from 65% to 50 %?
Lastly, if I'm using the phone for mass storage and after i safely remove it, which is suppose to appear? ME722 or A953? (I'm from Asia region)
(I'm sorry, I cant post in the android development due to limited posts)
Thanks.
Click to expand...
Click to collapse
1.devtree will not show.
2.Yep,it should be.At least in my daily use.
3.When you use UK devtree, it shows A953.Otherwise ME722.
Thanks to this repost I'm now using the CM7 port, thank you very much.
Sent from my MotoA953 using XDA App
Endless7 said:
1.devtree will not show.
2.Yep,it should be.At least in my daily use.
3.When you use UK devtree, it shows A953.Otherwise ME722.
Click to expand...
Click to collapse
Thanks Endless7, really appreciate it.
If there is battery jump, what advice can you give me?
Thanks
puiboy said:
Thanks Endless7, really appreciate it.
If there is battery jump, what advice can you give me?
Thanks
Click to expand...
Click to collapse
Use battery calibration to calibrate or wipe battery status in CWM.
Endless7 said:
Use battery calibration to calibrate or wipe battery status in CWM.
Click to expand...
Click to collapse
Use battery calibration to calibrate it for cm7-20111018, but battery still drop from 65% to 50% . Have flashed to the latest rom.
I'm having a problem. CM nightly does install fine and reboots but when I install droid2bootstrap and tries to boot into recovery, it does hangs on boot screen. Is there any specific directions I'm missing??
You cant use Droid2Bootstrap in CM7 or MIUI. They have integrated Bootmenu, which have included custom recovery.
ok then how to enter in recovery or Bootmenu? I'm giving a last go again :-(
Edit: I'm idiot!!!!! Cheers UFO for pointing.
After installing MIUI my Milestone2 is restarting constantly. Once installed, it worked normally. After installing several apps, it began to restart. I went back to voltage and frequency for stock. He kept restarting. I decided to start over. This time, I installed a few apps, restart stopped. After installing all the apps, To restart again. I was uninstalling apps, and it stopped rebooting. Is he related to the amount of apps, or even the amount of homescreens? I used the room (2.2.2 Argentina). MIUI 1.10.21V2. I believe that many users experienced this. Thank you.
Sorry, but I'm going to need some help to do this...
I couldn't find te CM7 All in one update.zip to download it, can anyone help me?
Sorry, I really don't know nothing about this... but I really want to try CM7
Found it?
guilhermemz said:
Sorry, but I'm going to need some help to do this...
I couldn't find te CM7 All in one update.zip to download it, can anyone help me?
Sorry, I really don't know nothing about this... but I really want to try CM7
Click to expand...
Click to collapse
I'm not 100% sure and just finished reading through this whole stuff for the Milestone 2, but I think it's (as of today) the file called: "cm7-20111027-NIGHTLY-Milestone2-ICS-Stable-v2.zip". The link is always at the end of the last changelog in the code box (just scroll a little bit down).
---------- Post added at 04:40 AM ---------- Previous post was at 03:51 AM ----------
After this procedure the bootloader is still locked, isn't it?
What is now different before the leaked ROM came to us, why can we now install custom a ROM? We have a suitable kernel?
Big thanks for the hard work getting this done
noticed a few people have a problem with the USB not mounting and I'm having the same problem, quick digging around I found out when I mount as "memory card access" it connects find to the pc but unmounts the SD card and I haven't found out how to remount it yet
---------- Post added at 09:42 PM ---------- Previous post was at 09:20 PM ----------
forgot to mention going to setting>storage mount sd card is greyed out
20111027-NIGHTLY-ICS-Stable-v2
when I open Droid 2 BootStraper, only two choice can be chose,how i can install the recovery ?
I will upload a photo !
please help to fix it !
{
"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"
}
LittleKu said:
when I open Droid 2 BootStraper, only two choice can be chose,how i can install the recovery ?
Click to expand...
Click to collapse
click on bootstrap recovery and when it asks for root permissions give it, after that click on reboot recovery and it will take you to the recovery.
Good how to, i dont know how enter the recovery...
Enviado desde mi MotoA953 usando Tapatalk
BlackF09
Did you installed CM7? How was it?
Sent from my A953 using XDA App
Is there a way to backup the widgets (their positions in the screen)?
Can titanium do that? I've tried but unsucessfully.
By the way, I'm using cyanogenmod and it's awsome. Congrats endless7.
Sent from my MotoA953 using XDA App
Hello,
I'm following the steps to install CM7 on my phone - currently using "mostly blurless gingerbread" rom - but I'm getting an error message "Invalid MD5" when trying to apply the update (step 7).
Also, another question - do I need to unzip the update on the destination folder, or leave it unzipped?
Thanks in advance.

[Guide]Samsung Galaxy S3[GT-I9300]Complete Basic Guide -One Stop Location

Hi Everyone, I had made some guides for Galaxy S3 on my blog and thought it would be enough. But after seeing the same questions being repeated again and again I felt I will post them here as well in a single thread.
If the mods find this useful they can put it up in the Stickies.
So here you go.
All about Android-Series
Samsung Galaxy S3 - GT-I9300
Part 1-
How to install a Custom ROM
This is a generic guide. Sometimes it may vary according to the ROM. So read the OP very carefully.
The main feature which distinguishes Android from all other operating system is the ability to tweak and customize the OS as per your liking.
If you are good at Linux commands and Java you can do this yourselves or you can install a Custom ROM prepared by other developers.
Before I start this, I would like to elaborate on what a Custom ROM or a ROM means. ROM in computer terms is Read Only Memory. It is specifically designed to be only accessible for reading and is not accessible to users for modifications. But in Android you can get access to this partition (if you are rooted)and make any changes you want to make.
For all practical purposes, a ROM is your Operating System or OS.
Now that it is out of the way, lets start.
Requirements:
For installing any custom ROM you will need to root your phone and have ClockworkMod (CWM) recovery installed.
A recovery is a partition on your internal memory which is used to install Software Upgrades or act as a last line of defense against a bricked device.
For Rooting and Installing CWM you will have to follow the procedures mentioned Below:
For rooting use Chainfire's CF AutoRoot. Your recovery will remain stock. Click.
Now you need to install a custom recovery. For that you have 2 options; either use ClockworkMod (CWM) Recovery Click or Team Win Recovery Project (TWRP) recovery Click.
Once you have that you can come back here.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
How to:
Okay now that you have CWM recovery and root.
Go here and search for a Custom ROM you like. Keep in mind that read the first post of the thread very carefully. It will have all the features of that ROM in detail. Download the ROM from that thread.
Once you have downloaded the ROM, follow these steps:
Put the ROM in the root directory of your Internal/External SDcard
Reboot into recovery: Press and Hold Power+Home+Volume Up buttons together and release it only when you see the recovery menu come up.
Now, Choose Wipe data.Factory Reset from here
Then, Wipe Cache and, goto Advanced and choose Wipe Dalvik Cache
You are now ready to Flash your Custom Rom
Choose, Install From Sdcard option in the Main Menu of the Recovery
Choose the ROM which you had earlier put on your SDcard
It will ask you whether you want to install or not, navigate to "Yes" and choose it.
Voila, You ROM will be installed, now Reboot.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Your Custom ROM is ready to be used.
Enjoy the Android Goodness!!
backing up your Device and Data
All about Android-Series
Samsung Galaxy S3 - GT-I9300
Part 2 -
How to Backup your device
Now that we have gotten fairly good at flashing Custom ROM, the biggest challenge we face is to restore all the application and application data we had earlier on our phone before going flash happy. It is often a very cumbersome task to download all you apps again from the PlayStore and the irritation goes to another level if we are in the midst of playing a big game and had completed 20 levels out of 22.
Once we do a Factory Reset/Data Wipe from the recovery menu all our saved data is lost and hence the Games and Apps.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
In this post I will update you on how to backup your device, your data and your apps effectively.
Backing up your device
To effectively backup your device before flashing any custom ROM, you will need to have ClockworkMod Recovery installed. If you don't have it or don't know what it is, read my guide in Part 1.
Once you have CWM installed, reboot into Recovery by pressing and holding Volume Up+Power+Home buttons together, release the buttons only when you see the Recovery Menu come on the screen.
Navigate to Backup and Recovery, Choose Backup from here.
This option will then backup all the system files, apps, app data and settings which you have on your device. There are two things which are not backed up here:
Your data on Internal/External Sdcard
Your Modem or Radio
Once the backup has completed, it will ask you to reboot the device. Reboot and you are backed up against any flashing misfortunes.
To Restore this backup just navigate again to backup and restore option in CWM recovery. Choose Restore option from here and Select the Backup you want to restore.
This is also known as Nandroid Backup.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your Applications and Application Data
Performing a Nandroid backup will not be useful if you want to try out a new ROM, as all the applications will be in the Nandroid backup and restore it you will have to restore the complete backup or Use Advance Restore from the options which is slightly cumbersome.
The best option here is to use Titanium Backup Application from the PlayStore. Get this app from here.
You will need to be rooted to use this application.
Now to backup your apps, fire up this application and grant it Superuser permissions.
It will show you all the apps which are not backed up. Choose the option of backing up all the apps with data.
It backs up all the apps and data on your internal sdcard.
Now after flashing a Custom ROM/New ROM you can restore all your applications to the same state by again going in TB and clicking restore all apps with data.
It is advisable that you don't restore System Apps and System Data if you have moved onto a different ROM, otherwise you will end up in Force Closes and unresponsive system.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing your SMSes
Another important data which we don't want to loose are our SMSes. To backup the SMSes we will use another application knows as SMS Backup and Restore. Get it from the PlayStore from here.
Open up the Application and click Backup. It will ask you for a name, give the backup a name preferably with a date. Now, you also have an option to save this backup in your dropbox account along with the SDcard. For it you will have to download an additional add-on for this app from here.
Once you have to add-on installed, navigate to Preferences>Backup Settings and Configure your Dropbox account here. Check that the Upload to Dropbox option is ticked. You can also configure a schedule for it to do the backups automatically and at the same time uploading it to Dropbox.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backup Contacts
This is already done by Google and all your contacts get backed in your Google account automatically.
Just ensure that you have added a Google account in your phone and the sync option is turned On.
Sometimes it so happens that you store all your contacts in your phone instead of your Google account and many times people are not aware of this. In this case even if the phone is synced with Google the contacts are not backed up in the Google account. So as a precautionary measure always backup your contacts to your SDcard and move it to the PC before wiping. For it go to Contacts -> Settings -> Backup contacts to SDcard.
Alternatively, you can also backup your Contacts, Call Logs, Messages, WiFi APs using Titanium Backup Pro.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing Up Your EFS Partition
The EFS folder in the root directory of your phone contains the most sensitive data peculiar to your device. Sometimes it so happens that while flashing a Custom ROM, this folder gets messed up. So, It is imperative that you back this folder up. I will explain this procedure using kTool application.
Download the kTool App from Playstore.
Now open the app and grant Superuser permissions (you should be rooted to use this applications)
Choose the "Backup EFS to Sdcard/EFS.img" option
Verify the Backup by clicking Yes on the Popup
Run Check in the resulting Screen
If the output says 100%(0 bytes differ) then your backup has been performed successfully.(when you later check this backup again there might be a difference so don't worry it is meant to be that way)
Now, using any file explorer upload this to your storage account and PC for safe keeping you might need it later for restoration.
Your EFS folder is now backed up..rest in peace.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I hope after following all these steps your are fairly protected against any misfortunes and can go and flash as many ROMs as you want.
Enjoy the Android Goodnes !!
Installing Latest Jelly Bean ROM
Using Odin:
Odin is the all purpose tool for Samsung devices which has completely replaced Kies on many PCs. It is light, fast, fluid and reliable.
You will need to first set up Odin in your PC (Hemidall in case of Mac users, don't ask me how to do it as I don't have a mac). Get Odin from here.
Once you have downloaded the zip file. Extract it somewhere you will remember.
Open the extracted folder and then open Odin3_v3.04.exe. It will ask you for administrator privileges, grant it.
Now download the latest ROM from:
www.samfirmware.com
Checkfus
XDA Page
Extract the tar from this zip to your PC.
Boot your phone into download mode, you can do this by pressing and holding Volume Down+Power+Home buttons together. Release the buttons when you see a robot with yellow triangle. Now press volume up button to enter into download mode.
Connect your phone to your PC. You will see Odin will recognize your phone and will show a message "Connected". The first box in the third row from the top will turn blue and say ID:COM7.
Now, the fun starts, click on PDA button and choose the tar file you had just extracted. Only Auto Reboot and F.Reset.Time options should be checked in the boxes above. If the Re-Partition box is checked Un-check it.
Click on Start, Odin will start installing your ROM. It will take some time so be patient. Once the installation is complete, your phone will reboot and you will have Jelly Bean on your phone.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Using ClockworkMod Recovery:
To get CWM recovery on your phone check my earlier post.
Download the ROM from here or here.
Put the zip file on your SDcard. Reboot into CWM recovery by pressing and holding Volume Up+Power+Home buttons together.
Choose "Install from SDcard", Navigate to the zip file and choose "Yes" when asked for confirmation.
Once installed reboot your phone and enjoy the Jellybean goodness.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
These Firmwares can be used by any International Galaxy S3 phones. You don't have to worry about which firmware you are currently at.
Enjoy the Android Goodness !!
Moving Back to Stock ROM
How to return back to Stock ROM: After you have played with Custom ROMs
In the Android world it is often said that "If you have not played with it, you have not used it". Most people who are familiar with the Android development play with Custom ROMs (Operating Systems). These are made by developers who know their way around the Android File system and programming language. The purpose is to get more out of each and every device.
Many android users use these custom roms to personalize their device to their liking. However, sometimes it so happens that you need to take the device back to the original state, the state it was in when you took it out of the box. The reasons for doing so may vary from:
Sending it for warranty repair
Starting afresh
Sorting out some bugs etc.
In this part I will guide you through the steps required for doing so.
Step 1: Download the Original Firmware (Complete OS, includes Boot image, Recovery image, sboot, partition information etc.).
The Original Firmware for your region may be downloaded from various sources:
samfirmware.com
Checkfus
XDA
In either of the above sources you will have to specify your OS name, Device Name, OS version and Region. After that you will be presented with a list of the latest firmwares. Download the firmware.
Step2: Reset the Binary Counter
If you have been into Custom Roms and have rooted your phone, most likely your binary counter is not 0.
You can check your binary counter by booting into Download Mode.
It can be done by pressing and holding Volume Down + Power + Home buttons together. You will get to screen which will ask you if you want to enter into download mode. Now press volume up button.
Here you will get all the information about your device status:
Odin Mode Product Name: GT-I9300
Custom Binary Download: a number
Current Binary: Samsung Official/Custom
System Status: Official/Custom
Our purpose is to change the "Custom Binary Download" to 0.
For this we will require a special application know as "Triangle Away" made by XDA Elite Recognized Developer Chainfire. You can buy this app from the Playstore or download it free from XDA Developers website.
Once installed, fire up the app and follow the instructions given there. Don't worry it should not damage your device.
After it has done the trick, check the download mode again to see whether the binary counter has changed to zero or not.
Step 3: Flash the Official Firmware
Now you will need to flash the official firmware you had downloaded in the first step.
Open, Odin application on your pc and connect your phone (For detailed instructions check out this blog post)
After you have flashed the firmware, you have now reverted your phone back to the status it was in when you had bought it.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Please feel free to post your comments and questions.
Enjoy the Android Goodness!!
Trouble shooting [FAQs]
Trouble Shooting Guide
Q. I have used Odin to flash stock ROM, now my phone is stuck in Bootloops. What should I do?
A. You have 2 options:
Boot in to Stock Recovery. Press and hold Volume up + Power + Home buttons together. Factory reset from there. However, if you do this you will loose all your data on the internal Sdcard
Flash CWM Recovery from here. Boot into recovery using the same button combo and Wipe Data/Factory Reset from there. You will not loose your data on internal SDcard this way.
Q. Can I flash JellyBean leak over the Stock ICS ROM?
A. Yes, you can. Just wipe Data, Cache and Dalvik Cache if flashing using ClockworkMod Recovery.
Q. How do I flash a kernel?
A. A kernel is flashed in the same way as a Custom ROM. So place the zip file on your Sdcard. Boot into recovery. Wipe Cache and Dalvik Cache. Flash the kernel.zip file.
Q. Can I flash XXXX modem over XXXX ROM?
A. Yes, Modem generally works independent of the ROM. So, You can flash whichever modem works best for your carrier/region.
Q. I have flashed XXXX ROM and now my CSC is unknown?
A. Generally Speaking CSC does not make much of a difference. If you are really facing a problem which is related to CSC such as some specific apps not working, some language not there etc. Either:
Use
Type *#272*Device IMEI# at Phone dial pad.
Select the CSC that you want.
Click Install.
or Install CSC changer app from the Market and change the CSC
Both ways yopur device will be factory resetted.
Q. I have installed a new ROM, but I am getting a strange notification in my status bar?
{
"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"
}
A. This icon means that your notifications are turned off. Drag your finger from the top of the screen down and you should see a bunch of buttons and the notification area, tap on the big button with the "i" so it turns green.
Q. What is the difference between a Theme and a ROM?
A. A ROM is a complete operating system whereas a Theme is a visual change made to some parts of a ROM.
Q. I have excessive battery drains?
A. More often than not it is your own fault. You have installed some app which is keeping your device awake. First of all before coming to any conclusions monitor your battery for atleast 2-3 charge discharge cycle. If you still feel the battery drain is high, install better battery stats from the market.
Now charge your mobile fully and let it discharge to 10%. Check the output of BBS and see which apps are causing the most wakelocks (i.e. keeping your device awake for the longest periods).
If it a non-system app, force stop/freeze the app and again monitor the battery drain for 1 complete cycle.
If the drain has improved, you have found the culprit, uninstall the offending app.
Additionaly, enable only those services out of
Location Services
GPS
WiFi
Sync etc
Which you use and disable those after you have used them.
Q. I have installed a new ROM, now my device does not see my photos/music?
A. This is a issue of the Media Scanner. The things which you should do in the decreasing order of priority are:
Reboot
Clear Cache/Data of the Gallery/Music Player app and Reboot
Clear Cache/Data of Media Storage and Reboot
Download Media Scanner app from Play Store and force rescan Media
Check in the media folders using a root enabled app for a .nomedia file, if found delete it
Re - Install the ROM after a full wipe.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Q. Where do I find XXXXXX?
A. Use the search option in the Thread Tools or Forum Tools. Use an many keywords as possible.
Q. I do not find the solution to my problem in this thread, should I start a new thread?
A. Strictly No, post your problem in this thread, more often than not you will find someone with an answer. Useless threads spam the forum which makes person looking for information do twice/thrice the work.
And Most important:
Always Thank the person who has helped you!!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I will be updating these guide regularly. SO feel free to comment and point out if I have missed/misrepresented anything.
Also, Please comment if any particular guide needs to be added.
Ask a mod to move the guide to a sticky .
On second thoughts users who would benefit from this guide refuse to read Stickies \FAQS and Guides .
jje
Zoot1, you are an absolute legend! Well done, should hopefully stop some of the stupid questions.... or at least give us an easy answer, by directing people here.
Should defo be stickied.
I would suggest adding a bit about backing up EFS (I only say it cos I buggered mine a couple of weeks ago, and had a mild heart attack until I remembered I had backed it up!).
BTW, there is a spelling mistake in post 2 - How to backup YOU device.... should say YOUR device.
krs360 said:
Zoot1, you are an absolute legend! Well done, should hopefully stop some of the stupid questions.... or at least give us an easy answer, by directing people here.
Should defo be stickied.
I would suggest adding a bit about backing up EFS (I only say it cos I buggered mine a couple of weeks ago, and had a mild heart attack until I remembered I had backed it up!).
BTW, there is a spelling mistake in post 2 - How to backup YOU device.... should say YOUR device.
Click to expand...
Click to collapse
Edited the post thanks for pointing it out.
Added a guide on backing up EFS folder.
Don't know if I'm posting this in the right place (I hope I am).
Rooted my galaxy s3 using odin. CWM and su were installed. After booting up I got process.android.gapp has stopped working. Also playstore force closes and restarts when I try initiating downloads initially. Now it doesn't open at all. It just closes immediately it opens. What could be wrong? And what can I do?
Sent from my GT-N7100 using xda app-developers app
ciphoenix said:
Don't know if I'm posting this in the right place (I hope I am).
Rooted my galaxy s3 using odin. CWM and su were installed. After booting up I got process.android.gapp has stopped working. Also playstore force closes and restarts when I try initiating downloads initially. Now it doesn't open at all. It just closes immediately it opens. What could be wrong? And what can I do?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Step 1 would be to remove your google account..the clear data and cache from google framework services and play store...reboot...
If that does not work then ..backup your apps and data..boot into CWM recovery..wipe data and cache from there...hopefully this will resolve your issue..
Sent from my iPad using Forum Runner
Originally Posted by ciphoenix
Don't know if I'm posting this in the right place (I hope I am).
Rooted my galaxy s3 using odin. CWM and su were installed. After booting up I got process.android.gapp has stopped working. Also playstore force closes and restarts when I try initiating downloads initially. Now it doesn't open at all. It just closes immediately it opens. What could be wrong? And what can I do?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Step 1 would be to remove your google account..the clear data and cache from google framework services and play store...reboot...
If that does not work then ..backup your apps and data..boot into CWM recovery..wipe data and cache from there...hopefully this will resolve your issue..
Sent from my iPad using Forum Runner
Click to expand...
Click to collapse
Thanks. The first step did it. Can now download from the playstore.
Sent from my GT-N7100 using xda app-developers app
waiting time after flashing stock
how long does the samsung logo stay on (animating) after flashing back to stock.
i have just followed your instructions on going back to stock (I9300XXEMB5) but now my phone wont boot up. i waited half an hour for it then i pulled the battery. and tried again but still it gets nowhere
mahall1988 said:
how long does the samsung logo stay on (animating) after flashing back to stock.
i have just followed your instructions on going back to stock (I9300XXEMB5) but now my phone wont boot up. i waited half an hour for it then i pulled the battery. and tried again but still it gets nowhere
Click to expand...
Click to collapse
Boot into stock recovery.. Wipe data/factory reset from there and try again..
Sent from my GT-I9300 using Tapatalk 2
zoot1 said:
Boot into stock recovery.. Wipe data/factory reset from there and try again..
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
your amazing thank you
very very inforrmative thank yo. jsut one more thing, what about images and vids etc? how do i back them up?
abukad said:
very very inforrmative thank yo. jsut one more thing, what about images and vids etc? how do i back them up?
Click to expand...
Click to collapse
Images can be backed up on Dropbox.. Similarly for videos as well.. However it is better to move all your important data on the internal sdcard to a pc before formatting..
Sent from my GT-I9300 using Tapatalk 2
Thank you. Now I know!
Sent from my GT-I9300 using xda premium
Thot I had synced contacts to Google... turns out dey were all saved to phone.. so ended up losing all contacts... so restored my nandroid n exported contacts to SD card... think u shud mention that
Sent from my GT-I9300
Rets88 said:
Thot I had synced contacts to Google... turns out dey were all saved to phone.. so ended up losing all contacts... so restored my nandroid n exported contacts to SD card... think u shud mention that
Sent from my GT-I9300
Click to expand...
Click to collapse
Thanks I will add it to the guide..
Sent from my GT-I9300 using Tapatalk 2

[ROM][PORT] Cyanogenmod 7 (Unofficial) for the Motorola XPRT

Cyanogenmod 7 for Motorola XPRT
Disclaimer: Do not flash this ROM if you do not know what you are doing and I take no responsibility if you do so, etc.
This is not an official ROM nor a final ROM. This ROM is still in testing stage and there will be some issues and problems. If some errors are encountered and somethings dont work then please post those issues in this thread.
Things that are tested and working:
Call and Data in GSM
Camera
Audio/Video
Call Recorder
etc.
Things that don't work:
Home button,
Voice search button
Side button.
Requirements:
1. Flash Gingerbread 2.3.5
2. Root
3. Install Custom Recovery
Boot into recovery and flash the ROM below:
http://www.4shared.com/zip/X8rTOj2P/cm-720-kronos.html
Next do a data/factory reset from your recovery.
After installing this ROM, Flash gapps for gingerbread to get Google Play Store ( Android Market) from http://goo.im/gapps/gapps-gb-20110828-signed.zip
After flashing this ROM it is not recommended to install recovery like Droid2 bootstrapper.
You can get to the bootmenu by rebooting your phone and when it starts up the LED will turn blue. When it turns blue press the volume down button. From the bootmenu you can choose the Recovery option.
thank you
rongsang said:
Cyanogenmod 7 for Motorola XPRT
Disclaimer: Do not flash this ROM if you do not know what you are doing and I take no responsibility if you do so, etc.
This is not an official ROM nor a final ROM. This ROM is still in testing stage and there will be some issues and problems. If some errors are encountered and somethings dont work then please post those issues in this thread.
Things that are tested and working:
Call and Data in GSM
Camera
Audio/Video
Call Recorder
etc.
Requirements:
1. Flash Gingerbread 2.3.5
2. Root
3. Install Custom Recovery
Boot into recovery and flash the ROM below:
http://www.4shared.com/zip/X8rTOj2P/cm-720-kronos.html
After flashing this ROM it is not recommended to install recovery like Droid2 bootstrapper.
You can get to the bootmenu by rebooting your phone and when it starts up the LED will turn blue. When it turns blue press the volume down button. From the bootmenu you can choose the Recovery option
Click to expand...
Click to collapse
Thank you very much ! you are a superman!:laugh:
Dear rongsang!
Merry Christmas and happy New Year!
Thank you for your work!
Pls attach the file Bootmenu_v0.8.6-v2_2_2 to the post)
Because, i think, many people trying to find it =)
Some instruction for noobs(i am noob too =) ):
1,Flash original 2.3.5 moto rom.
2.Root it.
3.Install droid Droid2Bootstrap recovery.
4.Run droid2 recovery, click on install recovery.
5.Reboot to recovery from program roid2 recovery.
6.Flash update Bootmenu_v0.8.6-v2_2_2 from recovery.
7.after flash reboot the phone.
8.Phone reboot into boot menu.
9.boot-enter-set default(second init)-go back
10.Choose recovery and press on custom recovery.
11.Backup and restore-backup(you need free space on your sd card).
12.flash update from sd card cm-7.2.0-kronos.zip
13.reboot the phone.
Enjoys =)
P.S. If you want to restore your backup, then you must restore and change in the boot set default normal!
sniper304 said:
Dear rongsang!
Merry Christmas and happy New Year!
Thank you for your work!
Pls attach the file Bootmenu_v0.8.6-v2_2_2 to the post)
Because, i think, many people trying to find it =)
Some instruction for noobs(i am noob too =) ):
1,Flash original 2.3.5 moto rom.
2.Root it.
3.Install droid Droid2Bootstrap recovery.
4.Run droid2 recovery, click on install recovery.
5.Reboot to recovery from program roid2 recovery.
6.Flash update Bootmenu_v0.8.6-v2_2_2 from recovery.
7.after flash reboot the phone.
8.Phone reboot into boot menu.
9.boot-enter-set default(second init)-go back
10.Choose recovery and press on custom recovery.
11.Backup and restore-backup(you need free space on your sd card).
12.flash update from sd card cm-7.2.0-kronos.zip
13.reboot the phone.
Enjoys =)
P.S. If you want to restore your backup, then you must restore and change in the boot set default normal!
Click to expand...
Click to collapse
It is not necessary to install the bootmenu as in step 6. You can install the droid2 bootstrapper and flash the ROM directly as the ROM already contains the bootmenu in it.
rongsang said:
It is not necessary to install the bootmenu as in step 6. You can install the droid2 bootstrapper and flash the ROM directly as the ROM already contains the bootmenu in it.
Click to expand...
Click to collapse
Ok,thanks!But i used bootmenu and recovery for a953 =)
Work good, now testet, wifi work ok!
Home button don't work(
When push it, it only vibrate.
When disable all keyboard settings(suach as auto replace;auto-cap;auto-punctuate)
keyboard don't visible on the screen
upd.
lockscreen dont work when i turn off display.why?we can change settings of lockscreen?
{
"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"
}
p.s. plz add to first message than, if you want adnroid market you must installe gapps for gb =)
So far I've only noticed the problem with the home menu button as the user above had stated. And and this on to your list rongsang. Calls and data work straight off the bat CDMA Boost Mobile! Amazing job.
Great Job Rongsang! Nearly perfect! I had the home button problem too, but I reflashed the rom, and it still didn't work. So then I deleted the dalvik-cache when I was installing gapps, and now the home button works. Not sure what fixed it though, lol.
Sent from my MB612 using xda app-developers app
tzuba12 said:
Great Job Rongsang! Nearly perfect! I had the home button problem too, but I reflashed the rom, and it still didn't work. So then I deleted the dalvik-cache when I was installing gapps, and now the home button works. Not sure what fixed it though, lol.
Sent from my MB612 using xda app-developers app
Click to expand...
Click to collapse
clean dalvik cache, but still no working(
upd.
In setting there is a dock settings.What is this?It's used in moto xprt?
P.S. Soory for my big list of question!
Upd 2.
When i trying to call on my mobile, call didn't go, because my mobile automatically ending call(
So far I've only noticed the problem with the home menu button as the user above had stated. And and this on to your list rongsang. Calls and data work straight off the bat CDMA Boost Mobile! Amazing job.
Click to expand...
Click to collapse
Yeah i forgot to add those... My first priority was just to upload the rom and post it so I didnt remember to write most of the things and I don't remember most of those things right now so kindly remind me and I will keep adding it to my post. Thank you guys..
tzuba12 said:
Great Job Rongsang! Nearly perfect! I had the home button problem too, but I reflashed the rom, and it still didn't work. So then I deleted the dalvik-cache when I was installing gapps, and now the home button works. Not sure what fixed it though, lol.
Sent from my MB612 using xda app-developers app
Click to expand...
Click to collapse
Same here. Just installing gapps fixes the home menu button. Heres the one you guys need.
BlackFire27 said:
Same here. Just installing gapps fixes the home menu button. Heres the one you guys need.
Click to expand...
Click to collapse
Flash it frome Recover?
zhongwu said:
Flash it frome Recover?
Click to expand...
Click to collapse
Yes.
Reboot the phone, and now call going to my phone.
sniper304 said:
Reboot the phone, and now call going to my phone.
Click to expand...
Click to collapse
Do try installing Google Apps. The phone app is updated sometimes through it I believe.
BlackFire27 said:
Do try installing Google Apps. The phone app is updated sometimes through it I believe.
Click to expand...
Click to collapse
call don't goint to me, after i installed gapps.But after reboot all work.
Approximation sensor didn't work correctly(when you calling, if you take mobile phone from ear, after that sensor don't work correctly)!
sniper304 said:
call don't goint to me, after i installed gapps.But after reboot all work.
Approximation sensor didn't work correctly(when you calling, if you take mobile phone from ear, after that sensor don't work correctly)!
Click to expand...
Click to collapse
I'm having no problems with the proximity sensor at all :/
sniper304 said:
Approximation sensor didn't work correctly(when you calling, if you take mobile phone from ear, after that sensor don't work correctly)!
Click to expand...
Click to collapse
Sorry, sensor work correctly!(this is my feature, i trying to put a finger on it , but i think sensor don't understand finger xD)
upd.
Bluetooth received files good,don't test bt audio.
sniper304 said:
Sorry, sensor work correctly!(this is my feature, i trying to put a finger on it , but i think sensor don't understand finger xD)
Click to expand...
Click to collapse
:laugh: happy new year ,everyone:highfive:
sniper304 said:
Sorry, sensor work correctly!(this is my feature, i trying to put a finger on it , but i think sensor don't understand finger xD)
upd.
Bluetooth received files good,don't test bt audio.
Click to expand...
Click to collapse
Lol. Well do keep in mind it also uses the accelerometer too to find out if its not by your ear. Because youll bring it down to look at the screen.
zhongwu said:
:laugh: happy new year ,everyone:highfive:
Click to expand...
Click to collapse
Happy new year):highfive:

OS command delay

Hi,
I recently bought a refurbished Nexus 7 and after creating 4 users and installing some apps on them the tablet started to act strange... e.g. when I open settings and tap any of the category it doesn't open... I need to press back and wait 30 sec or more. The same happens with Google Play when I tap install. Also with all other apps (EXCEPT games). Note: The tablet isn't laggy. I don't know what to do Please help
Sent from my Nexus 7 using xda app-developers app
Up.
Please help !!!!! :crying: This thing is getting worse
Try wiping cache. In recovery preferably.
Okay. And that will erase the temporary files and cache files NOT user data, correct? :fingers-crossed:
You've tried rebooting?
Sent from my Nexus 7 using Tapatalk HD
Yes. The same thing happens. I tried to enter recovery mode to erase the cache but i got the message "no command" and the green Android laying on its back with a red triangle over it. Any opinions?
BTW, on boot a white open padlock appears. That means is rooted? I also installed Root Checker and said that i don't have root acces. If it's rooted then can I unroot? (bcz i'm thinking of a warranty replacement)
The open lock means the boot loader has been unlocked. You still need to install super user, there's instructions posted search for it. Recovery wasn't installed properly. I missed a step my first time and had the same dead android, again is posted in the instructions on rooting and installing cwm.
http://forum.xda-developers.com/showthread.php?t=2150661
Sent from my Nexus 7 using Tapatalk 4 Beta
It probably means recovery wasn't installed at all.
SlowCobra96 said:
The open lock means the boot loader has been unlocked. You still need to install super user, there's instructions posted search for it. Recovery wasn't installed properly. I missed a step my first time and had the same dead android, again is posted in the instructions on rooting and installing cwm.
http://forum.xda-developers.com/showthread.php?t=2150661
Click to expand...
Click to collapse
Umm, ok.. But, I don't need CMW and Root on my N7. So, there is a way to come back to the original, pure JB 4.2.2 ? To be like a brand new unit? (with NO mods at all)
If you want it completely stock like factory new there is a thread sticky on how to do that as well.
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using Tapatalk 4 Beta
Thanks! And what about the recovery mode/'no command' error? ---- The link you gave me will solve this problem as well?
Sorry for n00b questions
bv31top said:
Thanks! And what about the recovery mode/'no command' error? ---- The link you gave me will solve this problem as well?
Sorry for n00b questions
Click to expand...
Click to collapse
The problem is that it appears there is no recovery installed thus the no command error. So you need to start with using the knowledge from the first thread I posted to get a recovery installed. From there you can try to wipe cache and dalvik cache then fix permissions. Or just follow the second thread to start completely fresh with a new install of jb 4.2.2.
EDIT: here is a guide for using adb and fast boot. http://forum.xda-developers.com/showthread.php?t=2225405
Sent from my Nexus 7 using Tapatalk 4 Beta
bv31top said:
Umm, ok.. But, I don't need CMW and Root on my N7. So, there is a way to come back to the original, pure JB 4.2.2 ? To be like a brand new unit? (with NO mods at all)
Click to expand...
Click to collapse
Gonna lag for sure then.
Rooting's best side effect is being able to tweak and streamline your device to make it as zippy as possible. Never will be as smooth running unrooted stock with no tweaks.
Sent from my SGH-T989D using xda app-developers app
I did a factory reset and now I made two users and installed around 5 apps. Now it's ok (no more delay). I think the problem is that the RAM/CPU becomes very slow with 4 users and many apps on them. I can only hope 4.3 will be better in managing multi-user devices. Anyway, the open padlock is still there.
Or just follow the second thread to start completely fresh with a new install of jb 4.2.2.
Click to expand...
Click to collapse
So, a fresh install with the method you gave me in the 2nd link can fix recovery mode (no command) and lock the bootloader?
Yes or No?
bv31top said:
I did a factory reset and now I made two users and installed around 5 apps. Now it's ok (no more delay). I think the problem is that the RAM/CPU becomes very slow with 4 users and many apps on them. I can only hope 4.3 will be better in managing multi-user devices. Anyway, the open padlock is still there.
So, a fresh install with the method you gave me in the 2nd link can fix recovery mode (no command) and lock the bootloader?
Yes or No?
Click to expand...
Click to collapse
Highly recommend you look into MultiROM. Like having multiple operating systems on a PC, you can install how ever many ROMs you want on your device that you will be able to pick which to boot from. There is less lag running different ROMs on there then stock 4.2.2.
{
"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"
}
Username invalid said:
Highly recommend you look into MultiROM. Like having multiple operating systems on a PC, you can install how ever many ROMs you want on your device that you will be able to pick which to boot from. There is less lag running different ROMs on there then stock 4.2.2.
Click to expand...
Click to collapse
Interesting...But, I'm not interested in setting up multiple OSs on my N7. At least not now.
Thanks, anyway.
bv31top said:
Interesting...But, I'm not interested in setting up multiple OSs on my N7. At least not now.
Thanks, anyway.
Click to expand...
Click to collapse
Why do you prefer to have 4 accounts on 1 ROM? Especially when it is causing you increasingly more trouble? And I am doubtful 4.3 would be a significantly better at "multi-usering".
Username invalid said:
Why do you prefer to have 4 accounts on 1 ROM? Especially when it is causing you increasingly more trouble? And I am doubtful 4.3 would be a significantly better at "multi-usering".
Click to expand...
Click to collapse
Just hoping U know... I know that it's 90% sure that will run ultra-smooth and problem-free, but I don't want to mess around with rooting, ROMs etc.
Now I'm waiting for @SlowCobra96 to respond to my question cuz his explanation was kinda odd.
One more question: When I tried to clear cache (from the UI because the recovery is f***ed up) I ended up with ~500MB cache from 600MB
Did anybody experience this problem?
bv31top said:
Just hoping U know... I know that it's 90% sure that will run ultra-smooth and problem-free, but I don't want to mess around with rooting, ROMs etc.
Now I'm waiting for @SlowCobra96 to respond to my question cuz his explanation was kinda odd.
One more question: When I tried to clear cache (from the UI because the recovery is f***ed up) I ended up with ~500MB cache from 600MB
Did anybody experience this problem?
Click to expand...
Click to collapse
Read the links I included they tell you what they do and how to do it. One is to install cwm and then a new rom if you so choose the other is to make the tablet like the day it came out of the box.
Sent from my Nexus 7 using Tapatalk 4 Beta
SlowCobra96 said:
Read the links I included they tell you what they do and how to do it. One is to install cwm and then a new rom if you so choose the other is to make the tablet like the day it came out of the box.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok... I think I will give it a try with the 2nd link.
And the cache problem?

FlashFire for locked bootloader G4's

Hey guys, I just want to start a general discussion about using FlashFire on G4's with locked bootloaders. We have confirmation that we can install the latest Xposed with it. I've also created a standard backup using it (I have not tried restoring yet). I don't see what would prevent us from installing stock based roms with it.
Here's a screen shot of the backup it created. System, data, and boot all appear to the the correct sizes.
{
"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 VS986 using Tapatalk
joshw0000 said:
Hey guys, I just want to start a general discussion about using FlashFire on G4's with locked bootloaders. We have confirmation that we can install the latest Xposed with it. I've also created a standard backup using it (I have not tried restoring yet). I don't see what would prevent us from installing stock based roms with it.
Here's a screen shot of the backup it created. System, data, and boot all appear to the the correct sizes.
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
Well I think the problem will be this, the app needs to be ran while android is running. If you are restoring the image and it is trying to replace system files it will probably crash at some point resulting in a boot loop. I haven't looked to see how this app works and maybe they have a way but I remember an app a few devs were working on to do the same and he was never able to get it working properly, it would just end up crashing and bootlooping/bricking. If they found a way around that this would be an incredible app!
You can try it out if you want but understand that you will probably softbrick. I highly recommend backing up your current system.img using the guide in the root method we have. That way you can put it in download mode and restore.
Apps like this wont allow flashing system but we should be able to flash a custom recovery, which would allow rom flashing. It depends on software.
I would guess that the stock rom has verification checks for partitions on the phone. We would probably have to do a custom recovery, boot into TWRP, and immediately flash a custom rom without said checks. I think we'll get there eventually but I am waiting on the devs to do their thing.
We have KDZ stock files to flash if things go bad. I am not saying to try it but if anyone feels confident in testing, it should be recoverable if things screw up, but most likely you will brick your phone.
Flashfire boot in a minimalistic os to work there.
You can also use partition flasher to flash system.img, boot.img and so on. To flash system img is no problem with locked boot loader at all. But the device can not boot with twrp installed with an locked Bootloader. The signature is not correct, so softbrick.
player911 said:
Apps like this wont allow flashing system but we should be able to flash a custom recovery, which would allow rom flashing. It depends on software.
I would guess that the stock rom has verification checks for partitions on the phone. We would probably have to do a custom recovery, boot into TWRP, and immediately flash a custom rom without said checks. I think we'll get there eventually but I am waiting on the devs to do their thing.
We have KDZ stock files to flash if things go bad. I am not saying to try it but if anyone feels confident in testing, it should be recoverable if things screw up, but most likely you will brick your phone.
Click to expand...
Click to collapse
You're a dev. lol. Anyways, we can flash stock roms with this. As long as it's running a stock kernel, it shouldn't be a problem. A modified kernel would most likely trigger secure boot error.
player911 said:
Apps like this wont allow flashing system but we should be able to flash a custom recovery, which would allow rom flashing. It depends on software.
I would guess that the stock rom has verification checks for partitions on the phone. We would probably have to do a custom recovery, boot into TWRP, and immediately flash a custom rom without said checks. I think we'll get there eventually but I am waiting on the devs to do their thing.
We have KDZ stock files to flash if things go bad. I am not saying to try it but if anyone feels confident in testing, it should be recoverable if things screw up, but most likely you will brick your phone.
Click to expand...
Click to collapse
On the contrary. Coming from Samsung, this is how roms are installed on those devices with locked bootloaders. It flashes the system images perfectly working around the Locked boot loader. Just don't try to flash a bootloaders.
I was wondering how the s6 was running Roms. Was it an easy process? And why aren't they doing this on the G4?
Sent from my iPhone using Tapatalk
dlscott1111 said:
I was wondering how the s6 was running Roms. Was it an easy process? And why aren't they doing this on the G4?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
You probably need a dev to build a package accordingly. Remove kernel and stuff like that. No one wants to be the tester lol. It would be nice to have a tot file just in case instead of that PR that is breaking cameras. (talking aT&T version of course)
I would LOVE to try out an international rom if they can get it to work with our devices but I have a feeling we will only be able to run rom on the same update we have? Maybe not as long as it works with the kernel
Just as an update...I used FlashFire to successfully restore my stock kernel. Granted, there were no modifications, but it worked.
Sent from my LGLS991 using XDA Free mobile app
The more I hear about flashfire the more I like.
Sent from my iPhone using Tapatalk
anyone with a stock at&t system want to pull a backup? that would be a good test for the guys running the pr rom. I'll guinee pig it
I did try restoring the 815 system and boot zip last night but I got nothing but force closes and didnt have time to mess with it because I needed my phone today
diedemus said:
anyone with a stock at&t system want to pull a backup? that would be a good test for the guys running the pr rom. I'll guinee pig it
I did try restoring the 815 system and boot zip last night but I got nothing but force closes and didnt have time to mess with it because I needed my phone today
Click to expand...
Click to collapse
I would totally do it but I don't want to have to factory wipe my device :-/ Just a pain to set it up again lol, I'm sure someone with more time on their hands can do it. Exciting, hope you can get the 815 working, there may be some changes needed to get everything to work
---------- Post added at 08:36 AM ---------- Previous post was at 07:42 AM ----------
diedemus said:
anyone with a stock at&t system want to pull a backup? that would be a good test for the guys running the pr rom. I'll guinee pig it
I did try restoring the 815 system and boot zip last night but I got nothing but force closes and didnt have time to mess with it because I needed my phone today
Click to expand...
Click to collapse
looks like you need to try to get this 10f update that fixes touch issues, if we could get that going we will be in paradise unless the fix was in the kernel
diedemus said:
anyone with a stock at&t system want to pull a backup? that would be a good test for the guys running the pr rom. I'll guinee pig it
I did try restoring the 815 system and boot zip last night but I got nothing but force closes and didnt have time to mess with it because I needed my phone today
Click to expand...
Click to collapse
Wait, would this image file work? http://forum.xda-developers.com/att-g4/development/root-images-h81010b-h81010e-t3168427 worth a shot. I'm not sure if that is the full system or not
joshuadjohnson22 said:
I would totally do it but I don't want to have to factory wipe my device :-/ Just a pain to set it up again lol, I'm sure someone with more time on their hands can do it. Exciting, hope you can get the 815 working, there may be some changes needed to get everything to work
Click to expand...
Click to collapse
No factory reset needed. Just don't include the data and cache partitions in the backup. . Since the system partition is not editable without root it is never changed. When a factory reset is performed all that happens is the data and cache partitions are wiped.
Edit: This is why root survives a factory reset.
CAG-man said:
No factory reset needed. Just don't include the data and cache partitions in the backup. . Since the system partition is not editable without root it is never changed. When a factory reset is performed all that happens is the data and cache partitions are wiped.
Edit: This is why root survives a factory reset.
Click to expand...
Click to collapse
ok... I'll trust you. I have xposed installed so you will have to live with it if it made changes to system and the system.prop edit. I will want to send it directly to you first before I post it in case something stays lol PM me (it is backing up now btw)
---------- Post added at 05:39 PM ---------- Previous post was at 05:36 PM ----------
CAG-man said:
No factory reset needed. Just don't include the data and cache partitions in the backup. . Since the system partition is not editable without root it is never changed. When a factory reset is performed all that happens is the data and cache partitions are wiped.
Edit: This is why root survives a factory reset.
Click to expand...
Click to collapse
also I backed up my system.img file before I rooted it using the adb commands maybe this will be useful too? Let me know.
EDIT: if you do not have the data partition exact won't it just have force closes and boot loops? I just have horrible memories on my G3 where I accidentally wiped data and even after flashing new roms i had force closes.
EDIT AGAIN: Currently uploading, I will PM you and the other requester @diedemus the file here in a minute. keep me posted
EDIT LAST: PM Sent
grabbing it now, we'll see how it goes
*edit 1* First attempt gave me the security error..... on to round 2
diedemus said:
grabbing it now, we'll see how it goes
*edit 1* First attempt gave me the security error..... on to round 2
Click to expand...
Click to collapse
Hmm interesting, Fingers crossed, what can you do differently the second time?
Sent from my LG-H810 using XDA Forums Pro.
just an update to flashfire... i was able to do a full backup for now. the black screen is a bit scary at first, u dont know if it hangs or not u just have to be patient. now i want to try if xposed will really work. *crossfingers*
edit.. xposed framework works!! finally!
Sent from my LG-H815 using Tapatalk 2
diedemus said:
grabbing it now, we'll see how it goes
*edit 1* First attempt gave me the security error..... on to round 2
Click to expand...
Click to collapse
You're restoring this with FlashFire?
Sent from my VS986 using Tapatalk
joshw0000 said:
You're restoring this with FlashFire?
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
yeah, it seems to work but we don't know if we can manage flashing a different version of stock yet. He is testing that out. Would love to get someone with 10F to install the app and back up system, data (with a factory wipe) and boot using FlashFire and see if we can get the touchscreen fix.

Resources