I'm having trouble restoring apps+data in Titanium Backup after flashing Android 6.0. I'm rooted (Supersu 2.50 plus modified boot.img provided by Chainfire).
When I restore the apps+data, the progess is stuck at 0%. I'm suspecting there's something wrong with my BusyBox, any thoughts?
Thanks
I think you have to manually set up the right folder in "preference".
Sent from my Nexus 6 using XDA Free mobile app
Well, Titanium Backup does pick up the backup folder location and I could verify the backup files successfully. I've also tried installing Hellscore Kernel, still stuck at 0% during restore.
make sure youre using the latest version of titanium back up 7.2.2
its working for me
Goto menu preferences select another app processing mode
Sent from my SM-T800 using Tapatalk
I think I also tried the "indirect" app processing mode in the latest TB (downloaded from Google Play). I can't seem to restore the apps in 6.0, not even flashing update.zip created by TB.
Good thing I had a 5.1.1 nandroid backup, went back to that.
Any solution please? Here is happening the same..
I wrote before it was working for me, but that was when i had ElementalX kernel, now that i flashed modified boot by chainfire and root with 2.50 superuser. Its not working for me either.
Loved to hear if anyone solved this. @ayang02
torecdude said:
I wrote before it was working for me, but that was when i had ElementalX kernel, now that i flashed modified boot by chainfire and root with 2.50 superuser. Its not working for me either.
Loved to hear if anyone solved this. @ayang02
Click to expand...
Click to collapse
So the solution would be to flash the ElementalX kernel instead of the chainfire one? If I want to flash the ElementalX kernel, I have to flash the stock kernel before, or I can do it from the chainfire one? What are the main differences between both kernels?
Thanks
mtebele said:
So the solution would be to flash the ElementalX kernel instead of the chainfire one? If I want to flash the ElementalX kernel, I have to flash the stock kernel before, or I can do it from the chainfire one? What are the main differences between both kernels?
Thanks
Click to expand...
Click to collapse
I had ElementalX with 2.49 SU was working fine but when i tried to flash chainfire's boot image and Su 2.50 i was stuck at boot loop and had to flash factory image all over again.
I dont recommend you to try and do that. Although it might work. i dont know.
Did any of y'all factory reset and wipe internal storage? I read wiping the SD card will make it work
---------- Post added at 05:40 PM ---------- Previous post was at 05:39 PM ----------
I can't find the exact post about it but it worked for me. Just make sure to backup all files to a computer before hand
I got it to work. Chainfire updated his boot.img for Nexus 6 and Titanium Backup also came out with a new version today. So I basically did a dirty flash from my 5.1.1 backup without wipe and everything worked for me. I didn't wipe this time, so the scenario is a bit different from my original post.
What I did:
1) I was using the latest bootloader + radio already, so I didn't flash those
2) Only Flashed system.img, Chainfire's boot.img, and cache.img
3) Install SuperSU 2.50 in TWRP
4) Reboot to System and waited for apps to upgrade
Some thoughts:
1) If your Titanium Backup has trouble finding the backup files, manually change the backup location to the correct one.
Titanium Backup's restore works for me now.
If SELinux is set to permissive Apps restore.
ldkud50 said:
If SELinux is set to permissive Apps restore.
Click to expand...
Click to collapse
i have SuperSU2.50 and elementalX 6.01 and still stuck at 0% a did try a lot of things... any other sulution then wipe SD card guys?
EDIT:
ok this works
su
setenforce 0
Click to expand...
Click to collapse
in terminal emulator
it will not survive reboot but still better solution then nothing
THANKS ldkud50 !
castaway1 said:
i have SuperSU2.50 and elementalX 6.01 and still stuck at 0% a did try a lot of things... any other sulution then wipe SD card guys?
Click to expand...
Click to collapse
What I did was to download all apps manually, and then restore only data. It worked.
TItanium Backup 7.1.2.1
boot.img from chainfire
SuperSU 2.49
pls help
me too having problem with titanium bkp. I had backup all my apps with data on 5.1.1 and flashed 6.0.1 rom. Now titanium bkp doesn't detect my bkp.
Tried many things like
copy bkp files to internal,
just made an app bkp and copy my bkp files to that folder etc.
still my TB doesn't detect my old bkp
cerico76 said:
I think you have to manually set up the right folder in "preference".
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
ldkud50 said:
If SELinux is set to permissive Apps restore.
Click to expand...
Click to collapse
Yes, that worked!
Related
First, this has started happening all of a sudden (at least I think so ).
I have successfully backup/restored many ROMs (GB and ICS) using CWM recovery version 5.0.2.7.
I am currently on ICS TMT1.0. This is just an FYI as I do not think the ROM is a problem here because I could take full backup on the same ROM once.
Now the issue.
When I enter CWMR and do backup, it backs up boot image fine and then system mount. After the same, it just reboots into recovery. When I go and check the CWM folder I do see backup of boot image and system.ext4.tar (going by the size of these files compared with successful backup it seems fine too). It just does not take backup of other mounts like data, cache, .android_secure etc.
I have tried power off and pulling battery out for few minutes but the same issue.
Any idea how do I take full CWMR backup again?
Do you have full root? You can paste any file to /system without issues? You may have partial root only mate
matius44 said:
Do you have full root? You can paste any file to /system without issues? You may have partial root only mate
Click to expand...
Click to collapse
Yes full root. Could copy a file to systems folder.
Sent from my GT-N7000 using Tapatalk 2
matius44 said:
Do you have full root? You can paste any file to /system without issues? You may have partial root only mate
Click to expand...
Click to collapse
Maybe you are right. Seems I can copy files to /system folder sometimes but not always. So I have to flash ROM again? Thanks for your help.
Sent from my GT-N7000 using Tapatalk 2
prasad.adam said:
Maybe you are right. Seems I can copy files to /system folder sometimes but not always. So I have to flash ROM again? Thanks for your help.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Yes a fresh flash is needed if you have lost root
There is a thread in Development about pre rooted stock ROMs, flash one of those with PC Odin and flash CF Root kernel for that ROM from Chainfire's thread
This way you'll have full root again along with working CWM Recovery
matius44 said:
Yes a fresh flash is needed if you have lost root
There is a thread in Development about pre rooted stock ROMs, flash one of those with PC Odin and flash CF Root kernel for that ROM from Chainfire's thread
This way you'll have full root again along with working CWM Recovery
Click to expand...
Click to collapse
Thought so. Will do the same at first available opportunity. Thanks again mate!
prasad.adam said:
Thought so. Will do the same at first available opportunity. Thanks again mate!
Click to expand...
Click to collapse
Went to stock GB. Root. CF ics repack. Till this point I have full root. then I restore my TMT h backup and I lose full root. Think problem is with TMT ROM. It isn't full root.
Sent from my GT-N7000 using Tapatalk 2
If you want the Official TWRP Recovery (now compatible with KK) for your Nexus S just check this link, there will always be the latest TWRP recovery officially out.
For now the latest is: TWRP 2.8.7.0
LINK: https://dl.twrp.me/crespo/
How to flash this? (Recommended way)
- enter in fastboot mode
- plug to your pc
- open a command prompt at the path where fastboot.exe is located
- type: fastboot flash recovery (drag and drop .img file)
- when done, type: fastboot reboot
PS: You now have a custom recovery and you are rooted. Since 2.5.0.0, TWRP roots your phone for you. Just reboot to recovery, and reboot system, if you are not rooted it will prompt you to root, just slide to accept. Let it reboot ,go to the playstore and download SuperSU.
Or if u are rooted:
- download from the playstore: [ROOT]*Rashr - Flash Tool (Playstore) / [ROOT]*Rashr - The mobile Android Flash-Tool (XDA Thread)
- download the latest TWRP.img
- open the app
- select Flash Other Recovery Image
- browse to your downloads folder
- select the TWRP.img file you just downloaded
THANKS to:
Team Win Recovery Project for this awesome custom recovery.
@DsLNeXuS (XDA username) / Ashot Mkrtchyan for the FREE app.
downloading now. thanks
Hi, I have a problem with a nandroid backup done with 2.3.1.0.
One backup done a week ago, works fine
Backup done today (successful restore) not work (stuck on boot, google and the lock)
Two question:
Is there a way to understand way stuck on boot?
If I restore /system from backup one (same rom) and /data from the last one is the same as full restore the last?
thanks
donpippo said:
Hi, I have a problem with a nandroid backup done with 2.3.1.0.
One backup done a week ago, works fine
Backup done today (successful restore) not work (stuck on boot, google and the lock)
Two question:
Is there a way to understand way stuck on boot?
If I restore /system from backup one (same rom) and /data from the last one is the same as full restore the last?
thanks
Click to expand...
Click to collapse
cant know why it gets stuck... maybe a faulty backup
u can try to grab data end system and substitute with the first one
Cascabreu said:
cant know why it gets stuck... maybe a faulty backup
u can try to grab data end system and substitute with the first one
Click to expand...
Click to collapse
i restored system from the first backup, than data from the second one.
For now works fine. All apps restored with their data.
How is done the backup? Is a dd if=/system of=systembackup ?
If so can I mount -oloop systembackup?
thanks
donpippo said:
i restored system from the first backup, than data from the second one.
For now works fine. All apps restored with their data.
How is done the backup? Is a dd if=/system of=systembackup ?
If so can I mount -oloop systembackup?
thanks
Click to expand...
Click to collapse
Dont know... i made tgis thread just to share the best recovery ever
Sent from my TH3M3D NEXUS S
Is there any changelog from 2.2.2?
Zunex95 said:
Is there any changelog from 2.2.2?
Click to expand...
Click to collapse
stability.
goomanager worked perfectly... thanks for the update
This is no good
luv2vexx said:
This is no good
Click to expand...
Click to collapse
Why? I use it in my nexus and works flawlessly
sent from my brand new Nexus 7
problems with twrp
some roms like sense4all,jb4.1.1 stock rom etc doesn't work with twrp.but works fine with cwm.
Cascabreu said:
Why? I use it in my nexus and works flawlessly
Just tried to restore a TWRP backup, said it was successful, reboot to system and all I get is "Fastboot Mode - No boot or recovery img"
I can still boot to recovery (TWRP)....
What should I do??
Here's what I did to fix: After restoring backup I wiped caches and installed ROM over the top. It is booting now. Thank goodness... I really didn't want to have to start over from scratch!!
Sucks that I can't rely on my nandroid backups though. Unless I am missing something.. This bug needs to be fixed!
not worth it, i reverted back to clockwork 5.8.0
Click to expand...
Click to collapse
luv2vexx said:
Cascabreu said:
Why? I use it in my nexus and works flawlessly
Just tried to restore a TWRP backup, said it was successful, reboot to system and all I get is "Fastboot Mode - No boot or recovery img"
I can still boot to recovery (TWRP)....
What should I do??
Here's what I did to fix: After restoring backup I wiped caches and installed ROM over the top. It is booting now. Thank goodness... I really didn't want to have to start over from scratch!!
Sucks that I can't rely on my nandroid backups though. Unless I am missing something.. This bug needs to be fixed!
not worth it, i reverted back to clockwork 5.8.0
Click to expand...
Click to collapse
Had that issue once and i reflashed the backup and it worked... i still prefer trwp, but different folks for different strokes....
sent from my not almost retired Nexus S
Click to expand...
Click to collapse
luv2vexx said:
Just tried to restore a TWRP backup, said it was successful, reboot to system and all I get is "Fastboot Mode - No boot or recovery img"
I can still boot to recovery (TWRP)....
Click to expand...
Click to collapse
I have this problem too.
I workarounded by flashing ROM's zip and then restoring backup without boot partition
yerazero said:
I have this problem too.
I workarounded by flashing ROM's zip and then restoring backup without boot partition
Click to expand...
Click to collapse
I tried again today and i can confirm that issue, but no biggie if u have the rom too... Lets hpe next version fixes it
Or we are not checking the little box on bbackup the boot partition.... Dunno
sent from my brand new Nexus 7
Cascabreu said:
I tried again today and i can confirm that issue, but no biggie if u have the rom too... Lets hpe next version fixes it
Or we are not checking the little box on bbackup the boot partition.... Dunno
sent from my brand new Nexus 7
Click to expand...
Click to collapse
I'm absolutely sure that I checked System, Data and Boot
thanks for your great work anyway
yerazero said:
I'm absolutely sure that I checked System, Data and Boot
thanks for your great work anyway
Click to expand...
Click to collapse
Thanks but i dont make these recoveries im only sharing it cuz i think apart from this issues wich turn out to be not a problem, twrp is more realiable than cwm...
sent from my brand new Nexus 7
Sorry for being late, OP updated to the latest 2.3.3.0
Now totally supports 4.2 roms
Sent from my Nexus 7 using xda app-developers app
Flashed this as instructed but when I try to boot into recovery I get the dead android guy with the red "!" icon. I'm trying to boot recovery from fastboot, is there another way it should be done?
hi everyone, i have recently got a HTC one, its rooted and also has custom recovery(TWRP) installed. its currently running stock android 4.2.2 firmware and today i have download the android 4.3 ota update. when i try to install the update it boots the TWRP recovery and i m unable to update. is there any way to update without losing my data, i know i have to flash the stock recover and again try to install the update but will this erase all my data(everything). i was using samsung galaxy s3, and its case there used to be chances to loose the data.. does same happens in HTC too. i don't wan't to lose my data, its about 23GB's..
suyash1629 said:
hi everyone, i have recently got a HTC one, its rooted and also has custom recovery(TWRP) installed. its currently running stock android 4.2.2 firmware and today i have download the android 4.3 ota update. when i try to install the update it boots the TWRP recovery and i m unable to update. is there any way to update without losing my data, i know i have to flash the stock recover and again try to install the update but will this erase all my data(everything). i was using samsung galaxy s3, and its case there used to be chances to loose the data.. does same happens in HTC too. i don't wan't to lose my data, its about 23GB's..
Click to expand...
Click to collapse
Your data shouldn't get wiped. No harm in making a backup though, just in case anything goes wrong. You'll just have to reflash twrp once you're done. Just out of curiosity, what's the software number of the update you got?
Sent from my iPod touch using Tapatalk
n1234d said:
Your data shouldn't get wiped. No harm in making a backup though, just in case anything goes wrong. You'll just have to reflash twrp once you're done. Just out of curiosity, what's the software number of the update you got?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
maybe the updates are older, because it was not updated from so long so, i thought to update. anyways the software no of update is 3.62.401.1.
do i need to lock bootloader too, to perform the update. and should i make backup from recovery? which backup method would u prefer... i don't want to lose anything..
suyash1629 said:
maybe the updates are older, because it was not updated from so long so, i thought to update. anyways the software no of update is 3.62.401.1.
do i need to lock bootloader too, to perform the update. and should i make backup from recovery? which backup method would u prefer... i don't want to lose anything..
Click to expand...
Click to collapse
just a quick word of caution, last time I flashed back a stock recovery (and accessed it, but didnt do anything in it), I was unpleasantly surprised that it wiped my entire internal storage
be safe, and backup your stuff to your PC
and no, you do not need to lock your bootloader.
nkk71 said:
just a quick word of caution, last time I flashed back a stock recovery (and accessed it, but didnt do anything in it), I was unpleasantly surprised that it wiped my entire internal storage
be safe, and backup your stuff to your PC
and no, you do not need to lock your bootloader.
Click to expand...
Click to collapse
well thanks a lot.. can i backup apps data too?
suyash1629 said:
maybe the updates are older, because it was not updated from so long so, i thought to update. anyways the software no of update is 3.62.401.1.
do i need to lock bootloader too, to perform the update. and should i make backup from recovery? which backup method would u prefer... i don't want to lose anything..
Click to expand...
Click to collapse
All the info needed to update is here http://www.htc1guru.com/2013/10/ota/
First flash the guru reset mentioned, then the OTA•
You could use titanium backup for all your apps and manually copy all the stuff from the internal sdcard to your pc. Making a nandroid won't really help, coz then you'll be restoring an older nandroid to a phone with a newer firmware, which doesn't work well. If you're completely stock right now, you could make a nandroid, and then after updating, if you want stuff to be like before, you could restore only your data partition. Works on Viper, not sure about stock.
Sent from my iPod touch using Tapatalk
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
n1234d said:
All the info needed to update is here http://www.htc1guru.com/2013/10/ota/
First flash the guru reset mentioned, then the OTA•
You could use titanium backup for all your apps and manually copy all the stuff from the internal sdcard to your pc. Making a nandroid won't really help, coz then you'll be restoring an older nandroid to a phone with a newer firmware, which doesn't work well. If you're completely stock right now, you could make a nandroid, and then after updating, if you want stuff to be like before, you could restore only your data partition. Works on Viper, not sure about stock.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
*Stuff*= all your apps, settings etc from the old rom will be transferred to the new rom
Sent from my iPod touch using Tapatalk
suyash1629 said:
well thanks a lot.. can i backup apps data too?
Click to expand...
Click to collapse
I would
I use Titanium Backup Pro for that (there's also a free version), both require root though. if you need a solution without root, check out Helium; i've never tried it but it should also work.
for SMS and call logs, I use "SMS Backup & Restore" and "Call Logs Backup & Restore" by Ritesh Sahu, which work better than Titanium IMHO.
Then I put everything on my PC, and I'm good to go
Okay, maybe I confused you a bit here, lets do this step by step
1. Make a nandroid of your current rom(data partition) with twrp (make sure you copy this to your pc), backup all apps with titanium backup, copy all data from internal storage
2. Flash guru reset.
3. Flash OTA.
4. Flash twrp, get root
5. Make a nandroid of the new rom (just in case), and then restore only the "Data" partition from the nandroid backup. If it works, amazing. If not, restore all apps from titanium backup. Good luck
Sent from my iPod touch using Tapatalk
---------- Post added at 11:40 PM ---------- Previous post was at 11:37 PM ----------
nkk71 said:
just a quick word of caution, last time I flashed back a stock recovery (and accessed it, but didnt do anything in it), I was unpleasantly surprised that it wiped my entire internal storage
be safe, and backup your stuff to your PC
and no, you do not need to lock your bootloader.
Click to expand...
Click to collapse
Never happened to me..
Sent from my iPod touch using Tapatalk
n1234d said:
Okay, maybe I confused you a bit here, lets do this step by step
1. Make a nandroid of your current rom(data partition) with twrp (make sure you copy this to your pc), backup all apps with titanium backup, copy all data from internal storage
2. Flash guru reset.
3. Flash OTA.
4. Flash twrp, get root
5. Make a nandroid of the new rom (just in case), and then restore only the "Data" partition from the nandroid backup. If it works, amazing. If not, restore all apps from titanium backup. Good luck
Sent from my iPod touch using Tapatalk
---------- Post added at 11:40 PM ---------- Previous post was at 11:37 PM ----------
Never happened to me..
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
well can i just flash stock recovery instead of flash guru reset and than flash ota update.. if i can do so why i need to download that huge(1gb) file to just ota update.. also can u give me a download link to stock recovery.
Edit: i have got the link to stock recovery: http://d-h.st/rZj
Do i have to worry about anything else.. Things i will do now:
1. make a backup of all sd-card data
2. make a titanium backup of all apps
3. use Super Backup : SMS & Contacts to backup call logs, sms and contacts
4. make a nandroid backup of system
5. Flash the stock recovery
6. do an OTA update
I thing this much will do the update right? or is there anything to worry about?
suyash1629 said:
Do i have to worry about anything else.. Things i will do now:
1. make a backup of all sd-card data
2. make a titanium backup of all apps
3. use Super Backup : SMS & Contacts to backup call logs, sms and contacts
4. make a nandroid backup of system
5. Flash the stock recovery
6. do an OTA update
I thing this much will do the update right? or is there anything to worry about?
Click to expand...
Click to collapse
Why I'm suggesting that you download the guru reset is that it'll ensure that you're completely stock before the OTA. having a rooted rom with all of those tweaks that anyone will generally install can cause many complications, so just to keep the process straightforward, rather do it. Leave it to download overnight By "nandroid backup of system", do you mean a complete backup or only of the system partition? Because, you need to make a backup of your data partition, not system. A complete backup will also do.
Sent from my iPod touch using Tapatalk
n1234d said:
Why I'm suggesting that you download the guru reset is that it'll ensure that you're completely stock before the OTA. having a rooted rom with all of those tweaks that anyone will generally install can cause many complications, so just to keep the process straightforward, rather do it. Leave it to download overnight By "nandroid backup of system", do you mean a complete backup or only of the system partition? Because, you need to make a backup of your data partition, not system. A complete backup will also do.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
this HTC one is only rooted and also has a custom recovery, others suggested only flashing stock recovery will do everything, without having a mess. and yes i have made a complete nandroid backup..
Sent from my GT-I9300
suyash1629 said:
this HTC one is only rooted and also has a custom recovery, others suggested only flashing stock recovery will do everything, without having a mess. and yes i have made a complete nandroid backup..
Sent from my GT-I9300
Click to expand...
Click to collapse
Cool then, that's all you need, go ahead
Sent from my iPod touch using Tapatalk
n1234d said:
Cool then, that's all you need, go ahead
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
im trying to copy the nandroid backup to pc but while i try to copy whole twrp folder it copies in seconds and when i checked the backup folder, i find only two files copied. if i try to manually copy those files than large files no not get copied, no error notification pops up but also the files do not get copied.. any ideas??
Sent from my GT-I9300
suyash1629 said:
im trying to copy the nandroid backup to pc but while i try to copy whole twrp folder it copies in seconds and when i checked the backup folder, i find only two files copied. if i try to manually copy those files than large files no not get copied, no error notification pops up but also the files do not get copied.. any ideas??
Sent from my GT-I9300
Click to expand...
Click to collapse
Try with version 2.6.3.0 or 2.6.3.3, some of the older ones don't allow copying of backups because of some form of encryption
Sent from my iPod touch using Tapatalk
n1234d said:
Try with version 2.6.3.0 or 2.6.3.3, some of the older ones don't allow copying of backups because of some form of encryption
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
can i flash newer version directly from recovery mode or i should use pc
sorry for asking lots of questions... i just wanted to verify everything so that nothing goes wrong
Sent from my GT-I9300
suyash1629 said:
can i flash newer version directly from recovery mode or i should use pc
sorry for asking lots of questions... i just wanted to verify everything so that nothing goes wrong
Sent from my GT-I9300
Click to expand...
Click to collapse
Flash it via fastboot just like you flashed this one.
Sent from my iPod touch using Tapatalk
n1234d said:
Flash it via fastboot just like you flashed this one.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
hey thanks for your help, everything worked perfect for me.. no loss of data after update, now i need to root it again. but everything worked perfect
n1234d said:
Never happened to me..
Click to expand...
Click to collapse
I know that's what I thought too, here's exactly what I did and where I was:
1- I just wanted to take a screenshot of stock recovery, and was on ARHD 13.3 with CWM
2- flashed stock recovery (the usual way)
3- took pictures (attached)
4- flashed back the same CWM
5- rebooted, and it hit me with the setup wizard, skipped it, and boom, NOTHING on the phone except the ROM
6- i didnt wipe anything except the "fastboot erase cache"
wonder why it happened
suyash1629 said:
hey thanks for your help, everything worked perfect for me.. no loss of data after update, now i need to root it again. but everything worked perfect
Click to expand...
Click to collapse
:good::good:
nkk71 said:
I know that's what I thought too, here's exactly what I did and where I was:
1- I just wanted to take a screenshot of stock recovery, and was on ARHD 13.3 with CWM
2- flashed stock recovery (the usual way)
3- took pictures (attached)
4- flashed back the same CWM
5- rebooted, and it hit me with the setup wizard, skipped it, and boom, NOTHING on the phone except the ROM
6- i didnt wipe anything except the "fastboot erase cache"
wonder why it happened
:good::good:
Click to expand...
Click to collapse
thanks for ur help guys, everything is working fine, i think volume is decreased a bit, getting less sound than previous. Do u guys know how to claim the 25GB free google drive space, i even tried to lock the boot loader but ins not working.. is there any way??
I was attempting to install the SlimKat ROM, and I followed the directions by going into CWM and doing a factory reset, wiping the cache, and formatting /system. When I tried to install the ROM, though, it told me that the file was bad. Now I can't boot back into the OS! It just stops at the T-Mobile splash screen. I can still get to CWM, but I have no idea where to go from there. I tried to recover from a previous backup, but it gives me "Error while restoring /system!"
How can I get my recoveries to work?
Just to confirm:
You do have the model Exhibit T679, correct?
What version of CWM did you flash?
The way I've been flashing ROMs:
Boot into CWM
Go to mounts and storage
format /system
format /cache
format /data
Go back to first CWM screen
Go to advanced
wipe dalvik cache
Go back to first CWM screen
Choose install zip
choose zip from the location you placed the ROM
To restore your backup:
Do steps 1-5 from above
6. Go to backup and restore
7. restore from the location you saved the backup
ZHXS said:
Just to confirm:
You do have the model Exhibit T679, correct?
What version of CWM did you flash?
Click to expand...
Click to collapse
Yes, it is a T679. My version of CWM is 6.0.5.0.
So, I solved the original problem, and now I have a new one... What I found was that I was able to install one of the other ROMs (Mahdi) from my external SD card. Then, I took a look at the SlimKat zip on my computer. As I suspected, the file was corrupted. (The MD5 hash didn't match.) So, I downloaded a new copy, verified the hash, and then tried again. This time, it worked! Everything seems to have installed okay, and I am loving SlimKat so far. Except for one thing... Somehow, I unrooted my device! Titanium Backup doesn't work anymore, and it was telling me it couldn't get root. So I installed Root Checker, and sure enough, I don't have root anymore! I downloaded root-stock.zip and tried flashing it, and that didn't work. Well, I guess it wouldn't, since I don't have a stock ROM anymore?
I'm sure I could flash a stock ROM, and then root that, but then I would want to go back to SlimKat, and I'm afraid I'd just wind up un-rooting it again.
fajrero said:
Everything seems to have installed okay, and I am loving SlimKat so far. Except for one thing... Somehow, I unrooted my device! Titanium Backup doesn't work anymore, and it was telling me it couldn't get root. So I installed Root Checker, and sure enough, I don't have root anymore! I downloaded root-stock.zip and tried flashing it, and that didn't work. Well, I guess it wouldn't, since I don't have a stock ROM anymore?
I'm sure I could flash a stock ROM, and then root that, but then I would want to go back to SlimKat, and I'm afraid I'd just wind up un-rooting it again.
Click to expand...
Click to collapse
As far as I know, most of these custom ROMs already come with root.
If you installed [ROM] [UNOFFICIAL] [4.4.2] SlimKat ROM [WEEK… | Galaxy Exhibit 4G | XDA Forums one of the listed problems is:
...Awesome... said:
What's Not Working!!
2) Some reason i lost root i had to include the Su app and Root is now active again
Click to expand...
Click to collapse
Maybe wait? Or try to flash/install Su?
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
Of if you installed [ROM][KK][4.4.4][KTU84P] SlimKat 6 UNOFFICIA… | Galaxy Exhibit 4G | XDA Forums known issue is:
jfbs said:
Known Issues
Do not enable KSM
If lacking root, enter superuser settings, then tap superuser access and select apps and adb.
Click to expand...
Click to collapse
ZHXS said:
As far as I know, most of these custom ROMs already come with root.
Click to expand...
Click to collapse
That's what I thought, too. This is why it's so confusing for me.
If you installed [ROM] [UNOFFICIAL] [4.4.2] SlimKat ROM [WEEK… | Galaxy Exhibit 4G | XDA Forums one of the listed problems is:
Click to expand...
Click to collapse
No, it's the one a little further down:
[ROM][KK][4.4.4][KTU84P] SlimKat 6 UNOFFICIAL-20140707
Maybe wait? Or try to flash/install Su?
Click to expand...
Click to collapse
That's what I'm going to try next. I haven't been able to find a source for the su binary yet, though. Just a lot of stuff for SuperSu, which requires you to already be rooted. I'm gonna try to get some sleep and look some more tomorrow. Thanks for your help.
fajrero said:
No, it's the one a little further down:
[ROM][KK][4.4.4][KTU84P] SlimKat 6 UNOFFICIAL-20140707
That's what I'm going to try next. I haven't been able to find a source for the su binary yet, though. Just a lot of stuff for SuperSu, which requires you to already be rooted. I'm gonna try to get some sleep and look some more tomorrow. Thanks for your help.
Click to expand...
Click to collapse
Ok, that ROM seems to have Superuser built in already, do you see a menu item for it when you go into Settings? The instructions seem to note that you have to go into Superuser and check a couple boxes.
Maybe it was a bad install, try formatting the necessary partitions and reflash again. Then go into Superuser and select the appropriate options.
Sometimes I also format sdcard0 after all the other formatting just to be extra thorough then install new ROM per instructions:
jfbs said:
Installation
Install at your own risk
- First time flashing CM11 to your Galaxy Exhibit (or coming from another ROM)?
Boot into existing recovery and create a Nandroid Backup!
Install at least ClockworkMod Recovery 6.0.4.5 or TWRP 2.6.3.0
Reboot recovery into at least ClockworkMod Recovery 6.0.4.5 or TWRP 2.6.3.0
CWM: WIPE dalvik-cache, format: data, system, and cache. TWRP: WIPE dalvik-cache, data, system, and cache.
** Optionally back-up sdcard0 before install and format it in recovery if experiencing install issues **
Install the ROM (without gapps)
Reboot system
After system boots, boot back into recovery and install KK Google Apps.
Wipe dalvik-cache and cache. Reboot.
Click to expand...
Click to collapse
TripFX said:
FYI most people here on xda just prefer you either clicking the thanks button if you the post was useful or if it a bug related then logcats and brief description of the problem and wait patiently for someone who knows to either A) if dev - fixes it or asks for more info. B) if other user- tries to help you out if possible.
Click to expand...
Click to collapse
:laugh:
You are welcome!
ZHXS said:
Maybe it was a bad install, try formatting the necessary partitions and reflash again. Then go into Superuser and select the appropriate options.
Click to expand...
Click to collapse
Yeah, that seems to have done it. I have root again, and everything looks okay.
Thanks again!!
I own an Note 5 and i managed to soft brick it while trying to get android pay working for my rooted phone. In the process I was asked to turn off superuser in the SuperSu app and then reboot. After that my phone wouldn't boot.
List of things I tried:
I tried to flash the recovery.tar to my phone
Flashed Twrp and wiped my cache and davlik-cache
Also tried the fix permissions option.
*Update I bought an otg cable and flashed super su but nothing @Droidriven
GraphicMarble said:
I own an Note 5 and i managed to soft brick it while trying to get android pay working for my rooted phone. In the process I was asked to turn off superuser in the SuperSu app and then reboot. After that my phone wouldn't boot.
List of things I tried:
I tried to flash the recovery.tar to my phone
Flashed Twrp and wiped my cache and davlik-cache
Also tried the fix permissions option.
*Update I bought an otg cable and flashed super su but nothing @Droidriven
Click to expand...
Click to collapse
Have you tried flashing your same ROM again if you were on a custom ROM and then superSU.zip then wipe cache and dalvik but don't factory reset(trying to save your data), then reboot.
If that doesn't work we'll take the next step.
Droidriven said:
Have you tried flashing your same ROM again if you were on a custom ROM and then superSU.zip then wipe cache and dalvik but don't factory reset(trying to save your data), then reboot.
If that doesn't work we'll take the next step.
Click to expand...
Click to collapse
\
I don't know the difference between a kernel and a custom but but i have this kernel SM-N920C-kernel-SkyHigh_TW_v3.5--[16-01-10].tar
GraphicMarble said:
\
I don't know the difference between a kernel and a custom but but i have this kernel SM-N920C-kernel-SkyHigh_TW_v3.5--[16-01-10].tar
Click to expand...
Click to collapse
A custom kernel is any kernel that isn't stock.
If you're using custom ROMs you're using custom kernel, find a kernel that works with your ROM.
Where did mention of a kernel come from?
Sent from my SCH-I535 using Tapatalk
Droidriven said:
A custom kernel is any kernel that isn't stock.
If you're using custom ROMs you're using custom kernel, find a kernel that works with your ROM.
Where did mention of a kernel come from?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I'm confused from this "A custom kernel is any kernel that isn't stock.
If you're using custom ROMs you're using custom kernel" does that mean ROM and kernel are the same thing?
GraphicMarble said:
I'm confused from this "A custom kernel is any kernel that isn't stock.
If you're using custom ROMs you're using custom kernel" does that mean ROM and kernel are the same thing?
Click to expand...
Click to collapse
No, custom ROMs can't use stock kernel so they need their own kernel, the kernel is what integrates your hardware with your software, roughly equivalent to drivers on PC. Without the kernel, the device can't use the ROM.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
No, custom ROMs can't use stock kernel so they need their own kernel, the kernel is what integrates your hardware with your software, roughly equivalent to drivers on PC. Without the kernel, the device can't use the ROM.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
So if i have a kernel that i flashed to gain root access it is a custom kernel. Then i guess i don't have a custom ROM
GraphicMarble said:
So if i have a kernel that i flashed to gain root access it is a custom kernel. Then i guess i don't have a custom ROM
Click to expand...
Click to collapse
Yes, that's how some newer Samsung are having to root.
If you're on Stock firmware then you may have to find a custom ROM and flash it or flash your stock firmware via Odin and start over with rooting the device again but you'll lose your data.
You might can do a nandroid backup before you flash anything and then after flashing you can retrieve your data from the nandroid backup by extracting it and putting it back where it belongs.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Yes, that's how some newer Samsung are having to root.
If you're on Stock firmware then you may have to find a custom ROM and flash it or flash your stock firmware via Odin and start over with rooting the device again but you'll lose your data.
You might can do a nandroid backup before you flash anything and then after flashing you can retrieve your data from the nandroid backup by extracting it and putting it back where it belongs.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
1. What advice do you have for this not happening in the future?
2. What data exactly can i recover through a nandroid backup?
GraphicMarble said:
1. What advice do you have for this not happening in the future?
2. What data exactly can i recover through a nandroid backup?
Click to expand...
Click to collapse
Answer 1) to prevent this in the future, when you get straightened out, boot to recovery and make a nandroid backup, that way you have a backup of everything with it working correctly that can easily be restored later if you have problems and will put you back to having everything the way it was when you made the backup. Its like a restore point in Windows.
Answer 2) A nandroid backup backs up everything on your device that is important, all of your settings, your contacts, your ROM, everything. You can pull whatever data from the backup that you need. But the backup I'm telling you to make right now nay not keep everything you had, there's no telling right now how much data you've lost or not so making the backup is to save whatever you can so you can retrieve it after repairing your device.
Always make a backup after every major change you make on your device so you'll always have a backup that includes the new additions so you can restore to that point if you need to. When you make a new backup you can delete the old one unless you just want to keep it but the more backups you make the more room they take.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Answer 1) to prevent this in the future, when you get straightened out, boot to recovery and make a nandroid backup, that way you have a backup of everything with it working correctly that can easily be restored later if you have problems and will put you back to having everything the way it was when you made the backup. Its like a restore point in Windows.
Answer 2) A nandroid backup backs up everything on your device that is important, all of your settings, your contacts, your ROM, everything. You can pull whatever data from the backup that you need. But the backup I'm telling you to make right now nay not keep everything you had, there's no telling right now how much data you've lost or not so making the backup is to save whatever you can so you can retrieve it after repairing your device.
Always make a backup after every major change you make on your device so you'll always have a backup that includes the new additions so you can restore to that point if you need to. When you make a new backup you can delete the old one unless you just want to keep it but the more backups you make the more room they take.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
So if I make a backup now what are the steps in restoring what I can salvage.
GraphicMarble said:
So if I make a backup now what are the steps in restoring what I can salvage.
Click to expand...
Click to collapse
Don't get ahead of yourself, for now just make the backup and then focus on getting the device restored to working again and THEN you can worry about retrieving the data.
One step at a time, stop trying to cross bridges you haven't gotten to yet.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Answer 1) to prevent this in the future, when you get straightened out, boot to recovery and make a nandroid backup, that way you have a backup of everything with it working correctly that can easily be restored later if you have problems and will put you back to having everything the way it was when you made the backup. Its like a restore point in Windows.
Answer 2) A nandroid backup backs up everything on your device that is important, all of your settings, your contacts, your ROM, everything. You can pull whatever data from the backup that you need. But the backup I'm telling you to make right now nay not keep everything you had, there's no telling right now how much data you've lost or not so making the backup is to save whatever you can so you can retrieve it after repairing your device.
Always make a backup after every major change you make on your device so you'll always have a backup that includes the new additions so you can restore to that point if you need to. When you make a new backup you can delete the old one unless you just want to keep it but the more backups you make the more room they take.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
So I did a backup to my computer. What are the speps in restoring what i can salvage?
GraphicMarble said:
So I did a backup to my computer. What are the speps in restoring what i can salvage?
Click to expand...
Click to collapse
No, not a backup to computer, boot to TWRP and choose the backup option, nandroid are created in recovery. Using PC isn't the right way to do what I said.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
No, not a backup to computer, boot to TWRP and choose the backup option, nandroid are created in recovery. Using PC isn't the right way to do what I said.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thats what I did but I put it on my PC for next time
GraphicMarble said:
Thats what I did but I put it on my PC for next time
Click to expand...
Click to collapse
You don't have an extsdcard? If so its best to keep it there.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
You don't have an extsdcard? If so its best to keep it there.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I kinda do with the OTG feature
So I return to my question, What are steps of salvaging
GraphicMarble said:
I kinda do with the OTG feature
Click to expand...
Click to collapse
Never mind then, just keep it on PC
Now, look through your forum and find a custom ROM that works on your model number and a compatible gapps package(the ROM thread will tell you which gapps you need so don't ask) and then flash ROM then superSU then Gapps in TWRP then reboot and see if you're fixed.
If that doesn't do it then you'll need to go to Sammobile.com or samsung-updates.com and type in your model number to find your firmware, download it and then flash it in Odin in the AP slot, the same slot you flashed your kernel to root.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Never mind then, just keep it on PC
Now, look through your forum and find a custom ROM that works on your model number and a compatible gapps package(the ROM thread will tell you which gapps you need so don't ask) and then flash ROM then superSU then Gapps in TWRP then reboot and see if you're fixed.
If that doesn't do it then you'll need to go to Sammobile.com or samsung-updates.com and type in your model number to fins your firmware, download it and then flash it in Odin in the AP slot, the same slot you flashed your kernel to root.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Can I restore a nandroid backup with a stock ROM?