Database Users

[Q] Root newbie, can you change between roms?

Hi i am looking to root for the 1st time i have seen how to do it, i have already unlocked bootloader for updating reasons.
My question is if i put a rom on for instance JellyBAM can i if i choose to switch between that and the stock android or would i have to re install the stock android.
I enjoy the features of the stock android on my nexus 7 (2013) but am looking to just tweak it a little but i dont want to put the factory image back on if i dont like JellyBAM as it will wipe my device again.
Thanks for any help
Joe

http://www.indiegogo.com/projects/multirom-for-nexus-7-2013
Flashing a new ROM would only overwrite your current system, system data and cache. Your internal storage where your files, pictures, videos, etc are would be intact.

Username invalid said:
http://www.indiegogo.com/projects/multirom-for-nexus-7-2013
Flashing a new ROM would only overwrite your current system, system data and cache. Your internal storage where your files, pictures, videos, etc are would be intact.
Click to expand...
Click to collapse
thanks for the reply and answer
to get the stock android system back do you remove the rom you have flashed or do you just flash the stock rom back on?
Thanks for any help again
Also if you flash the stock rom back on where can i download the rom from?

joeyt90 said:
thanks for the reply and answer
to get the stock android system back do you remove the rom you have flashed or do you just flash the stock rom back on?
Thanks for any help again
Also if you flash the stock rom back on where can i download the rom from?
Click to expand...
Click to collapse
The custom recovery automatically wipes the old ROM when you flash a new one.
Stock ROM - https://developers.google.com/android/nexus/images

Username invalid said:
The custom recovery automatically wipes the old ROM when you flash a new one.
Stock ROM - https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
If i flashed a stock rom would it wipe my tablet to new?
I recently had to fastboot the new android os 4.3 (jss15q) and would that be the same way to get it back on after flashing a custom rom? using flash-all.bat?
Thanks for the great help so far!!

joeyt90 said:
If i flashed a stock rom would it wipe my tablet to new?
I recently had to fastboot the new android os 4.3 (jss15q) and would that be the same way to get it back on after flashing a custom rom? using flash-all.bat?
Thanks for the great help so far!!
Click to expand...
Click to collapse
If just flashed the stock ROM images (system, userdata, cache), your internal storage, custom recovery and kernel would remain.

Username invalid said:
If just flashed the stock ROM images (system, userdata, cache), your internal storage, custom recovery and kernel would remain.
Click to expand...
Click to collapse
I think i am starting to undertand it all now, so using flash-bat.all just uploads the rom its the unlocking of the bootloader that wipes your memory (which i have already done)
now for a personal opinion what is a good rom to start with for someone who wants to learn but not get chucked in at the deep end (in terms of the changes you can do to the device not the flashing which i know makes no difference which rom you put on its always the same method)
Thanks

joeyt90 said:
I think i am starting to undertand it all now, so using flash-bat.all just uploads the rom its the unlocking of the bootloader that wipes your memory (which i have already done)
now for a personal opinion what is a good rom to start with for someone who wants to learn but not get chucked in at the deep end (in terms of the changes you can do to the device not the flashing which i know makes no difference which rom you put on its always the same method)
Thanks
Click to expand...
Click to collapse
When you first unlocked the bootloader, it wiped the userdata, cache and internal storage. Flash a new ROM in the recovery replaces the stock system, userdata and cache without wiping your internal storage. You can start off with Minimus or CleanROM which is the closest to stock with minimal changes.

Username invalid said:
When you first unlocked the bootloader, it wiped the userdata, cache and internal storage. Flash a new ROM in the recovery replaces the stock system, userdata and cache without wiping your internal storage. You can start off with Minimus or CleanROM which is the closest to stock with minimal changes.
Click to expand...
Click to collapse
Thanks again i have flashed cleanROM and its worked great, but now that i have rooted and installed the rom can i delete the files of my nexus 7 internal storage?
Thanks
Joe

joeyt90 said:
Thanks again i have flashed cleanROM and its worked great, but now that i have rooted and installed the rom can i delete the files of my nexus 7 internal storage?
Thanks
Joe
Click to expand...
Click to collapse
Yes, you can wipe your internal storage or format your device in the recovery which would accomplish the same thing.
{
"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:
Yes, you can wipe your internal storage or format your device in the recovery which would accomplish the same thing.
Click to expand...
Click to collapse
worked a treat although i now cannot stop changing things
Thanks

[Q] lost my storage after update to 4.4.3

Hi, I have a Nexus 7 2012 32 GB. Today I updated to 4.4.3 but after update only 6.02 GB of 32 GB is shown on storage.
What should I do?
{
"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"
}

mkhp70 said:
Hi, I have a Nexus 7 2012 32 GB. Today I updated to 4.4.3 but after update only 6.02 GB of 32 GB is shown on storage. What should I do? ,,,
Click to expand...
Click to collapse
First, a bit more details - is yours rooted/unlocked, what was running before & using custom recovery (latest CWM or TWRP) ? Did you do a Factory Reset after backing up user files & data? Wipe Dalvik Cache, Cache and Factory Reset/Wipe?
Reboot into Custom Recovery, wipe dalvik cache & cache first, then reset & check your storage again?
Post your steps, results & we will go from there.

rooted/unlock/TWRP 2.6 / I did factory reset after backing up user files & data but I didnt Wipe Dalvik Cache, Cache
updating through the factory image with nexus toolkit
now i do wipe dalvik cache and cache and full wipe but not fix

Something is seriously messed up if all it's telling you you have is 6gb of internal storage. If you have a 32gb like me, then it should show around 27 to 28 gb storage (mine is the 2012 WiFi version of N7).
Something got seriously borked during the upgrade.
My question is, did you get an OTA and do it that way or did you download the full image from Google and then flashed it that way?

Something isn't right? I'm afraid that you need to start al over - learn ADB and forget about those Toolkit(s) unless that are specific & updated for 4.4.3 compliance. Mine is a 2012 WiFi model with 32 GB, internal storage/total space is 27.58 GB and even with apps & pix, video, etc. on the SDcard, and Apps taking up space, I have 19.1GB available.
First, might I suggest that you upgrade/try the newest recovery - either CWM or TWRP (using 6.0.4.5 on mine) to install - doing a full wipe & factory reset is best way/recommended AND yes, time-consuming, but you get it "right" almost every time - wipe three (3) times each - dalvik cache, cache and factory reset/full wipe. Then, re-flash your factory rom/image file - be patient, as it will take 5 to 10 minutes for it to finish, take a break or whatever. When it's done & without error/abort message, reboot the device & let it settle for a little while after configuring WiFi as those download Apps and update could take a while if your mobile data plan is limited. Personally, I'm "biased" toward TWRP and I don't have to deal with MD5 check/error message that pop out of nowhere with CWM. :cyclops:
If everything works as planned, you will be shown the Setup Menu to configure - profit & enjoy, check the storage size (you can see what's taking up the space) then, restore your Google Account with the Apps, and reboot when finished.
Good luck & let us know your progress or results.

mkhp70 said:
rooted/unlock/TWRP 2.6 / I did factory reset after backing up user files & data but I didnt Wipe Dalvik Cache, Cache
updating through the factory image with nexus toolkit
now i do wipe dalvik cache and cache and full wipe but not fix
Click to expand...
Click to collapse
At the last step the toolkit shows you a message that talks about this issue. I can't remember what it exactly says. But it tells you what to do incase of lost storage. Either reflash using toolkit and read the prompt about lost storage or search the Web about this message from toolkit.
Sent from my Nexus 7 using XDA Free mobile app

Anyone have a XT1575 7/19/2016 update TWRP package?

Anyone have a XT1575 7/19/2016 update TWRP package?
{
"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"
}

Please post if you do, my rooted phone now enters boot-loop because I accidentally hit "Yes, I am in"....
Thanks in advance!!!

I had the boot loop too. Went to twrp and wiped dalvik and cache and no more boot loop.

captainmalcolm said:
I had the boot loop too. Went to twrp and wiped dalvik and cache and no more boot loop.
Click to expand...
Click to collapse
Do you still have root, etc.?

captainmalcolm said:
I had the boot loop too. Went to twrp and wiped dalvik and cache and no more boot loop.
Click to expand...
Click to collapse
HeatR216 said:
Do you still have root, etc.?
Click to expand...
Click to collapse
Yes i would like to know! I would love to be able to run the OTA update without causing issues, and if all i have to do is wipe dalvik n cache on boot after the OTA update that would be awesome!

Sorry should have been more clear, the update does not work. Wrong signing keys. It sends the system into a boot loop. You boot back into the O's but after about 30 seconds it begins applying the update again and send you into twrp and updates fails, reboot, wait 30 apply again twrp, etc. Etc. The way I got out of the loop was wiping dalvik and cache and now I can use the phone again without boot loop. We need to wait until someone creates a twrp zip for the update.

Mine is full wipe >> flash stock 24.49-18-3 >> update 24.49-18-4 via OTA then flash Su 2.62-3 >> Done.

captainmalcolm said:
Sorry should have been more clear, the update does not work. Wrong signing keys. It sends the system into a boot loop. You boot back into the O's but after about 30 seconds it begins applying the update again and send you into twrp and updates fails, reboot, wait 30 apply again twrp, etc. Etc. The way I got out of the loop was wiping dalvik and cache and now I can use the phone again without boot loop. We need to wait until someone creates a twrp zip for the update.
Click to expand...
Click to collapse
I still dont get you, first you say the update does not work, then you said it worked after you cleared dalvik and cache in twrp after it had been applied making it work?

Not TWRP flashable, but someone posted the full firmware here.
I could not get the OTA to go on my phone, kept failing.
I just fastboot flashed everything in that zip according to the flash script that came with the zip except recovery and didn't wipe userdata. Booted into new system to confirm everything was ok, then TWRP flashed systemless supersu and Frankenclark. All is good. Not as simple as TWRP flashable, but way less disruptive than restoring to bare bones stock to take an OTA.

How long does it usually take on a new twrp zip?

oh someone please get this going! i hate this annoying update notification every day! twrp zip would be awesome!

nd4spdbh said:
oh someone please get this going! i hate this annoying update notification every day! twrp zip would be awesome!
Click to expand...
Click to collapse
yep. just waiting for twrp zip.

Samsung Galaxy S7 bootloop

I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)

k1ng0fqu33n5 said:
I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)
Click to expand...
Click to collapse
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.

TheSproker said:
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.
Click to expand...
Click to collapse
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.

k1ng0fqu33n5 said:
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.
Click to expand...
Click to collapse
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)

TheSproker said:
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)
Click to expand...
Click to collapse
If i do a factory reset with TWRP, will it wipe any of the internal data? (pictures, messages etc.)
because the factory reset screen says that it's not included:
{
"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"
}

Well, i just tried a factory reset and that fails too. Unable to mount /data.

k1ng0fqu33n5 said:
Well, i just tried a factory reset and that fails too. Unable to mount /data.
Click to expand...
Click to collapse
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?

EasyAndroidPro said:
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?
Click to expand...
Click to collapse
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.

k1ng0fqu33n5 said:
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.
Click to expand...
Click to collapse
I see.. if that file did not fix the bootlooping then I'm afraid the only fix is like the previous poster said
Either flash stock again with Odin
Or format data in twrp

Ok, i somehow made it so the phone booted up and initialized. Now i got the problem that the google play store keeps crashing.
Edit: I also can't download my whatsapp backup data (says insufficient storage, which is not the case)

I also can't download files with the chrome browser (it says no sd-card found). If i use the stock samsung browser it works though.

I can't back up after restoring a backup- please help

Hello all,
I recently bought a brand-new ZE552KL and have since unlocked the bootloader, flashed TWRP 3.2.1, flashed ViperOS 7.1.2, flashed Magisk 15.3, flashed Xposed v89r5-v90b2, and made several backups. However, each time I restore one, I lose all progress in the most evil manner I've encountered to date: Any time I try to back up my install after restoring from a backup, it fails, claiming my system partition is only 7MB in size.
Now, at first I thought this was simply a bug in the latest TWRP- 3.2.1 is so new, after all- so I flashed back to 3.1.1, reflashed ROM/GApps, went through first boot, and began making backups as normal. Only, when I tested one of them by restoring, booting to system, changing things, booting back into recovery, and attempting to back up, well, you guessed it... 7MB system partition. I have no idea what's causing this, but it kinda invalidates the point of having backups in the first place. Any help would be appreciated.

Hi, i never find a solution for backup / restore with TWRP. Always doing all from begining.

I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?

wang1chung said:
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
Click to expand...
Click to collapse
Sorry for the late reply. It's been a rough, long day at work.
I have no issues restoring either. As I mentioned in my post, the trouble comes from trying to back up what I've restored- say, restoring at a previous point and changing things from how I'd previously set it up. As soon as I try to back up a restored system, it tells me my system partition is only 7MB in size.
However, to answer your question, no, I back up everything. I always have, ever since I first got TWRP on my Motorola Xoom. (CWM on that thing was just awful.) Is there some reason a full backup is wrong on this device?

auroraPLG said:
Sorry for the late reply. It's been a rough, long day at work.
I have no issues restoring either. As I mentioned in my post, the trouble comes from trying to back up what I've restored- say, restoring at a previous point and changing things from how I'd previously set it up. As soon as I try to back up a restored system, it tells me my system partition is only 7MB in size.
However, to answer your question, no, I back up everything. I always have, ever since I first got TWRP on my Motorola Xoom. (CWM on that thing was just awful.) Is there some reason a full backup is wrong on this device?
Click to expand...
Click to collapse
Try to flash twrp 3.1.1 (20171023) from here https://mega.nz/#F!kl8lmKRL!ZbLvz1b4YgLMr_n09vRrTA

[email protected]@ said:
Try to flash twrp 3.1.1 (20171023) from here
Click to expand...
Click to collapse
Okay, got it downloaded. Wish me luck.
EDIT: Old TWRP flashed and backup made. Gonna bite the bullet.
EDIT 2: So... now an error restoring. First time for everything, eh? (Not saying I've never had a failed restore, just not with this device- until now, of course....)
Code:
Restoring Data (excl. storage)...
extractTarFork() process ended with ERROR: 255
Gonna reflash 3.2.1 for now just to get a system running. Any ideas for in the meantime?

auroraPLG said:
Okay, got it downloaded. Wish me luck.
EDIT: Old TWRP flashed and backup made. Gonna bite the bullet.
EDIT 2: So... now an error restoring. First time for everything, eh? (Not saying I've never had a failed restore, just not with this device- until now, of course....)
Gonna reflash 3.2.1 for now just to get a system running. Any ideas for in the meantime?
Click to expand...
Click to collapse
1. Old twrp make your device bootloop?
2. The data you backup is from nougat stock and you want to restore it in viperos?

[email protected]@ said:
1. Old twrp make your device bootloop?
2. The data you backup is from nougat stock and you want to restore it in viperos?
Click to expand...
Click to collapse
1. No. No bootloop. I don't understand where you got this idea. As I said, old TWRP failed to restore Data. However, I'm pretty sure it was the Data partitions in my latest backups, due to making files immutable- not the recovery itself.
2. No, I want to restore ViperOS.

wang1chung said:
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
Click to expand...
Click to collapse
Hi, this is the right configuration for a backup ?
Please confirm me
{
"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"
}
Picture from howtogeek.com

@dekson9
Yes, that is the correct. System partition is the OS, and the data partition is your apps and config data.
So, when you make a backup, can you confirm the size of the backup files, should be something like system.ext4.win000, 001, 002.
Maybe try unmounting and remounting the system partition while in twrp before the restore? You can toggle the button at the bottom right (4 horizontal lines) to see if there were any errors.

wang1chung said:
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
Click to expand...
Click to collapse
Well, I tried it your way. Not gonna lie, I don't understand why a full backup would cause that problem. But it turns out you're right. I've gotten that kink worked out thanks to you. Now if I could just fix the hardware clock... but that's another adventure for another party, I'm sure. I'm off to press that thanks button.

@auroraPLG
Glad you got it sorted, happy flashing!

@wang1chung
Thank you! I think I'm gonna play around with backups and pull logs and see if I can't figure out what causes this particular bug.