Related
Hi All,
my first time using a forum and first time attempting to install a custom ROM so be nice . i have done some research around the net but I'm now more confused than before i have read that i need to install software to back up my current ROM but before that it needs to be rooted but before i can root it i should back up the current ROM (confusing...), i have also read that galaxy note 1 users have some serious bugs in the kernel so its very risky rooting it never mind putting a custom ROM on it, that the IEMI in the EFS partition will be wiped so that should be backed up after rooting but before flashing with a new ROM otherwise i wont be able to connect to my network i have searched the forum and found guides but nothing for my phone and nothing in as much layman's terms as i need.
Phone: Samsung galaxy note GT-N7000, last over the air update was 12 months ago for android v 4.1.2
base band version n7000xxlt3 kernel version 3.0.31-1103517 [email protected]#3 smp preempt tue jun 4 20:55:52 KST 2013 build number J2054k.N7000XXLT9
bought 2 years ago on t mobile currently running on giff-gaff
knowledge: some but evidently not enough tried to fix a bug on a tablet and didn't back it up first, bricked it and a year later its still in my draw
i have a lot of stuff on my phone, 2 years worth of stuff and while iv done the odd manual back up knowing im about to flatten it completely i want to back it up completely first, document videos pics contacts apps messages everything i can possibly back up i will
so what i need:
a total walk through precautions on what i should do and in what order i.e. backing up in general, backing up efs, rooting, backing up current rom, flashing a rom ect
what software i should use for the above?
the best 3 ROM's available for GT-N7000 or just peoples opinions will do I'm looking for something with added features and a a fresh look as I'm really bored of the phone now
sorry if this is already somewhere else and please feel free to make fun of the new guy as long as i can perform a successful flash my phone i will be happy!
Many thanks in advance
@ckershaw here is what you need to do. As you have a lot on your phone, connect it to pc and transfer all the data. Then look for Philz kernel and download kernel matching your build number XXLT9. Download the .zip file and put it on your external sd card. Reboot to recovery pressing volume up+power+home button and flash the .zip file there. It will give you custom cwm and root. You can now install titanium backup pro or such application to backup your user apps (don't backup and restore system apps). Once done, you can again reboot to recovery and take a backup of your whole rom (make sure you select EFS folder too to backup). Once you have the backup on your external SD card or trasnferred to pc. Perform full wipe (factory reset from philz recovery). Then go to mounts and storage and also wipe /system /cache /data and internal sd card. Once you are done, flash raw kernel (either r4 or r5) from external sd card and reboot recovery and flash the latest kit kat rom (any of your choice) along with Gapps. Raw kernel is only if you are trying to flash any kit kat rom, else philz kernel should suffice.
treacherous_hawk said:
@ckershaw here is what you need to do. As you have a lot on your phone, connect it to pc and transfer all the data. Then look for Philz kernel and download kernel matching your build number XXLT9. Download the .zip file and put it on your external sd card. Reboot to recovery pressing volume up+power+home button and flash the .zip file there. It will give you custom cwm and root. You can now install titanium backup pro or such application to backup your user apps (don't backup and restore system apps). Once done, you can again reboot to recovery and take a backup of your whole rom (make sure you select EFS folder too to backup). Once you have the backup on your external SD card or trasnferred to pc. Perform full wipe (factory reset from philz recovery). Then go to mounts and storage and also wipe /system /cache /data and internal sd card. Once you are done, flash raw kernel (either r4 or r5) from external sd card and reboot recovery and flash the latest kit kat rom (any of your choice) along with Gapps. Raw kernel is only if you are trying to flash any kit kat rom, else philz kernel should suffice.
Click to expand...
Click to collapse
hi thanks for the info!
when i say uber noob i do have lots of experience with phones and computers as its what i do for a living im also a quick learner so i figured it out myself last night, granted i was at it till 02:30 in the morning but i figured it out and that's almost exactly what i did, the only thing i did differently was i wiped it but i didn't 'Then go to mounts and storage and also wipe /system /cache /data and internal sd card' but all is working very well and it feels like i have a new phone i did have 1 annoying issue that was the Google keyboard crashed every 5 seconds so had to keep clearing the notifications for it but i solved that by disabling it and pushing a different one from the play store.
one thing i do need help with however is i made a manual backup of the phone but not sure if i got everything, i did a full backup with kies.. that was a mistake! as the phone isn't recognized as a Samsung device i cant restore the backup, i would like to try to manually extract the file but i have looked around and been told you can only recover calendar and contacts, i want to recover images, videos, sms, call logs all that sort of stuff.. any ideas? has anything been developed recently for that as all the posts i looked out although relevant are rather outdated its a .sbu file
Thanks
ckershaw said:
hi thanks for the info!
when i say uber noob i do have lots of experience with phones and computers as its what i do for a living im also a quick learner so i figured it out myself last night, granted i was at it till 02:30 in the morning but i figured it out and that's almost exactly what i did, the only thing i did differently was i wiped it but i didn't 'Then go to mounts and storage and also wipe /system /cache /data and internal sd card' but all is working very well and it feels like i have a new phone i did have 1 annoying issue that was the Google keyboard crashed every 5 seconds so had to keep clearing the notifications for it but i solved that by disabling it and pushing a different one from the play store.
one thing i do need help with however is i made a manual backup of the phone but not sure if i got everything, i did a full backup with kies.. that was a mistake! as the phone isn't recognized as a Samsung device i cant restore the backup, i would like to try to manually extract the file but i have looked around and been told you can only recover calendar and contacts, i want to recover images, videos, sms, call logs all that sort of stuff.. any ideas? has anything been developed recently for that as all the posts i looked out although relevant are rather outdated its a .sbu file
Thanks
Click to expand...
Click to collapse
If all your efforts are for naught, maybe I'd suggest that you flash a stock rom, restore all your stuff via Kies again, and this time backup them in your PC instead. Do not worry about deleting your media (Images, video, music) if you do a factory wipe reset from a custom recovery as they are not set to delete those files. to back up sms, call logs and contacts calendar n stuff, you can install superbackup app from playstore. Takes time n effort to restore but I think it's worth it. Good Luck bro:good:
Hi Guys,
thanks for all the help, been working great for a week with no bugs my question is now i have flashed it with the ROM the root access is now gone so i will need to root again the details are now
android version: 4.43
omni version: 4.4.3-20140608-n7000-nightly
Baseband n7000xxlt3
kernel: 3.0.64-OMNI-g5f47648 [email protected] #1 sun jun 8 07:00:23 CEST 2014
built number omni_n7000-userdebug 4.4.3 KTU84M 254 test-keys
what file will i need to do this, i couldnt use odin it dodnt work i found transfering the file to SD and running it that way worked best (cant remember do you have to wipe when you root this way)
Thanks
ckershaw said:
Hi Guys,
thanks for all the help, been working great for a week with no bugs my question is now i have flashed it with the ROM the root access is now gone so i will need to root again the details are now
android version: 4.43
omni version: 4.4.3-20140608-n7000-nightly
Baseband n7000xxlt3
kernel: 3.0.64-OMNI-g5f47648 [email protected] #1 sun jun 8 07:00:23 CEST 2014
built number omni_n7000-userdebug 4.4.3 KTU84M 254 test-keys
what file will i need to do this, i couldnt use odin it dodnt work i found transfering the file to SD and running it that way worked best (cant remember do you have to wipe when you root this way)
Thanks
Click to expand...
Click to collapse
Either find UpdateSuperSUv1.94.zip and flash it through recovery, or just try downloading supersu or superuser from playstore.
Jackwu696 said:
Either find UpdateSuperSUv1.94.zip and flash it through recovery, or just try downloading supersu or superuser from playstore.
Click to expand...
Click to collapse
Thanks,
last one i promise my battery has been draining in an average of 4 hours and my phone is constantly hot since putting this ROM on i have 3 battery's i charge externally via an external charger and that just about lasts me the day i have a power management app called battery doctor that is great and if it wasn't for that I'm sure it would only last half the amount, i have checked and Google+ keeps starting up every time i close it even if i force it to stop and it's used 96% of my battery today i have only actually used the phone for about 3 minutes today. ond its only been off charge for 3 hours is it OK to disable it what else wont work if i do. is there any reason its doing this surely that's not normal?
Thanks
ckershaw said:
Thanks,
last one i promise my battery has been draining in an average of 4 hours and my phone is constantly hot since putting this ROM on i have 3 battery's i charge externally via an external charger and that just about lasts me the day i have a power management app called battery doctor that is great and if it wasn't for that I'm sure it would only last half the amount, i have checked and Google+ keeps starting up every time i close it even if i force it to stop and it's used 96% of my battery today i have only actually used the phone for about 3 minutes today. ond its only been off charge for 3 hours is it OK to disable it what else wont work if i do. is there any reason its doing this surely that's not normal?
Thanks
Click to expand...
Click to collapse
My best suggestion would be to delete google+. Otherwise use Titanium Backup to freeze or greenify it. The best is still to delete it though.
Sent from my GT-N7000
I have a rooted KFHD 7” (gen 1) with TWRP. I have a few questions about rooting in general. I’ve rooted several devices in the past but with extensive hand-holding so I still don’t completely understand the process. I’ve tried looking for general explanations but my search has come up empty so far.
1. The KFHD is running an early CM11 build with some functions missing (cannot install ANY Amazon apps, Netflix via HDMI glitches, etc). I want to flash a more recent CM11 build that supposedly has those issues ironed out.
- Do I have to wipe all data before I flash to the new CM11 build? Do I have to flash new GAPPS? Will TWRP backups from the earlier build still work after I flash a new build? When do I wipe cache and delvik cache, and what are they exactly?
2. These questions are related to TWRP. I made a backup back in April 2014 when I first rooted the KFHD, and then created another one yesterday. Why do I see only the backup I made yesterday when I boot into TWRP? I am asking because the TWRP folder is about 5gb, which is a lot of space on a 16gb KFHD. I want to delete the older backup and perhaps minimize the size of future backups. Please see picture attached for a screen cap. Only the first file "boot.emmc.win" is cut off (it is a 8mb that I assume to be important). Which files can I delete? Like I said, I don't see the April 2014 backup when I booted into TWRP.
3. Also for TWRP: what is the difference if I made a backup with or without “data” checked? I experimented yesterday and made 2 backups – one with “data” and one without “data”. I first recovered with the “with data” backup to check if it works fine, then boot into TWRP and recovered with the “without data” backup. Everything seems to be the same and nothing’s lost – is it because I didn’t wipe the KFHD before I restore with the "without data" backup? If I wiped the KFHD and then restore with the “without data” backup, what kind of difference would I see?
Sorry for the essay. Really want to learn the basic principles of rooting.
1. Go into settings>about tablet>cyanogenmod updates>check for updates. M7 should be on the list, press the button to the right and it should update, as long as you are on cm 11 already this procedure is fine and no gapps update is needed.
2. The backups from earlier don't show because twrp was fixed a while back and now reads our serial number, notice the backups are probably in a folder that random alpha numeric characters and another that is a ton of zero's, when ESN was able to be read it stored our backups in the folder with our correct ESN rather than a fake ESN made of zeros. Either move that backup from the 0's folder or delete it, it will be then old one.
3.with data backs up the userdata partition, basically all of your user installed apps and their appdata.
Sent from my Amazon Tate using Tapatalk
I don't think this is a Moto X (XT1096) specific problem, but more so with TWRP. Phone works fine, just can't backup or restore
I'll try to get a log as soon as I can, just need to figure out how
Problem
I can't backup or restore (and maybe can't delete via TWRP?) from TWRP, getting errors at the start (can't access .../data/cmthemes and can't access .../data/motogallery) and then at the end TarFork() process ended with ERROR=255
Tried Solutions
Reflash TWRP (broke, had to use TWRP app to fix)
Upgrade TWRP (says it failed, but worked)
Enable Compression (no real difference that I can tell)
Cause?
I was on CM13 (2/2 ?), upgraded to most recent (2/6), didn't like it so wiped and flashed to original (1/29 ?) then restored backup (2/2). Probably wasn't the best way to do that, oops. Since then I have wiped and reflashed 2/2 and upgraded to 2/7, haven't done anything since (besides mess with TWRP)
Any help or ideas would be appreciated!
Please lock/delete
Solution: Factory reset, only method that worked for me
Be sure to clear cache
Solution: There is a file on the phone that is preventing the backup. Not sure what is creating it. It could be an artifact of a TWRP backup restoration, which is the first time I had the problem.
Look in the TWRP log ([SDCard]/recovery.log) and scroll near the end - you will find the culprit there, almost always in the [root]/SYSTEM folder but sometimes in multiple folders. It has many names. I've seen it called, simply "999". On my Moto G4, it was "d.addon". Delete the folder and you're good to go.
Hi,
Pls pardon my noob questions...
I just gotten my 3T about a week now and after spending over 3 days setting up everything from scratch (eg installing numerous apps and configuring them one by one, setup emails, sms, contacts, icons packs, settings, etc) and finally gotten the phone to a state where I am very satisfied, a question dawn on me - How can I do a full image backup so that if anything happens, I can do a full image recovery and get back the "perfect" state?
After doing so much reading, it seemed the full image backup is called a "nandroid" backup and I need to first unlock the bootloader and flash TWRP in-order to perform this backup. But my predicament is, if I proceed to unlock bootloader, then all my configurations, setups and data will be wiped. So it became a chicken and egg scenario.
And the 2nd problem is that, worst comes to worst I decide to bite the bullet and proceed with unlocking and flashing TWRP, when booting into TWRP can I select "read only" and not agree with modified system since I have no intention to root. Will this cause boot loop problem if it is "read only"?
Can "read only" state in TWRP allows me to perform nandroid backup and restoration later on?
May I skip the next step of flashing anti dm verity file / root? I don't really want to go root since I am very happy with stock OOS at the moment.
So the big question is, is there anyway out there in the universe where I can do as close as possible to a nandroid backup without going bootloader unlocking route as that is not an option for me as I can't afford to have all the data, settings and configurations wiped. I heard about Helium app which can backup app data but that's about it. Everything else has to be setup from scratch.
Zegnalabel said:
Hi,
Pls pardon my noob questions...
I just gotten my 3T about a week now and after spending over 3 days setting up everything from scratch (eg installing numerous apps and configuring them one by one, setup emails, sms, contacts, icons packs, settings, etc) and finally gotten the phone to a state where I am very satisfied, a question dawn on me - How can I do a full image backup so that if anything happens, I can do a full image recovery and get back the "perfect" state?
After doing so much reading, it seemed the full image backup is called a "nandroid" backup and I need to first unlock the bootloader and flash TWRP in-order to perform this backup. But my predicament is, if I proceed to unlock bootloader, then all my configurations, setups and data will be wiped. So it became a chicken and egg scenario.
Click to expand...
Click to collapse
Yes, a Nandroid backup is what you want, and yes, you need an unlocked bootloader for that, and yes, you need to wipe your data to do that. That's why it's highly recommended that unlocking your bootloader is the first thing you do as soon as you get your phone (though that's obviously too late for you). To help ease the pain, you can do an adb backup as described at http://forum.xda-developers.com/showthread.php?t=1678239. This will preserve most but not all of your stuff, and doesn't need an unlocked bootloader. Once you do that, you can unlock the bootloader, restore the adb backup, then take a nandroid backup.
Zegnalabel said:
And the 2nd problem is that, worst comes to worst I decide to bite the bullet and proceed with unlocking and flashing TWRP, when booting into TWRP can I select "read only" and not agree with modified system since I have no intention to root. Will this cause boot loop problem if it is "read only"?
Can "read only" state in TWRP allows me to perform nandroid backup and restoration later on?
May I skip the next step of flashing anti dm verity file / root? I don't really want to go root since I am very happy with stock OOS at the moment.
So the big question is, is there anyway out there in the universe where I can do as close as possible to a nandroid backup without going bootloader unlocking route as that is not an option for me as I can't afford to have all the data, settings and configurations wiped. I heard about Helium app which can backup app data but that's about it. Everything else has to be setup from scratch.
Click to expand...
Click to collapse
Yes, you should mount /system read-only. You don't need to root or disable dm-verity as long as you do that. (By the way, Helium is pretty much just a nice wrapper around adb backup.)
josephcsible said:
Yes, a Nandroid backup is what you want, and yes, you need an unlocked bootloader for that, and yes, you need to wipe your data to do that. That's why it's highly recommended that unlocking your bootloader is the first thing you do as soon as you get your phone (though that's obviously too late for you). To help ease the pain, you can do an adb backup as described at http://forum.xda-developers.com/showthread.php?t=1678239. This will preserve most but not all of your stuff, and doesn't need an unlocked bootloader. Once you do that, you can unlock the bootloader, restore the adb backup, then take a nandroid backup.
Click to expand...
Click to collapse
Many thanks Joseph for your advice! I really appreciate it! You're totally right, I'll do an adb backup followed by bootloader unlocking and TWRP installation. :good:
Yes, you should mount /system read-only. You don't need to root or disable dm-verity as long as you do that. (By the way, Helium is pretty much just a nice wrapper around adb backup.)
Click to expand...
Click to collapse
May I further check with you what are the limitation bring about when choosing "read only" when first enter TWRP? As in won't be able to flash ROM, flash supersu, etc thereafter?
Once again, thanks for your help, Joseph!
Zegnalabel said:
May I further check with you what are the limitation bring about when choosing "read only" when first enter TWRP? As in won't be able to flash ROM, flash supersu, etc thereafter?
Click to expand...
Click to collapse
All it means is that you won't be able to modify /system with file manager or the shell. Flashable zips almost all contain code that remounts /system read-write (as the TWRP screen warns you about). Also, you can always change your mind and make it read-write later (though the reverse is not true; once you mount it read-write, putting it back to read-only doesn't fix anything unless you reflash the ROM).
Many thanks Joseph for your sound advice.
After taking some time to read through all the links and sub-links getting to know the varied means of backups available, I have decided that my backup strategy will be as follows since non of the methods offer comprehensive backup and a mixed of the lots will be required to get as fool-proof as possible, before embarking on a data wiping journey with bootloader unlocking.
(i) I first perform a backup using google native backup and restore function under setting no matter how limited it is, to be use as a safety net.
(ii) Next, adb backup. The limitation with adb backup is that since Android 6.0, it obeys AndroidManifest.xml and will not backup data of those apps which has android:allowBackup set to false. The challenge is, I will be held in the dark which app falls into this category when performing adb backup and won't know until after I had done the actual restoration. Its like a blackbox you won't know what you gonna face until the aftermath had hit. Therefore to get around this, I'll be using Helium app (a wrapper around adb backup) instead of the actual adb backup since both methods refer to AndroidManifest.xml when deciding which app data it can or cannot backup. And Helium shows exactly which app it can backup vs that which it can't. Good info there for a start.
After installing Helium and activating it via PC client, I found out it does backup:
A) SMS and call logs
B) User dictionary
C) Accounts
D) Bunch of apps and their data
List of apps and data it can't backup:
1) Contacts
2) browser bookmarks
3) Calender
4) System settings
5) APNs
6) Homescreen shortcuts
7) Widgets
8) Alarms
9) Photos
10) Music
11) Videos
12) MMS
13) Google AUTHENTICATOR!!! - I have over 15 profiles that I'll have to re-setup one by one... what a nightmare.
14) Line
15) Whatsapp
16) wechat
17) Signal
18) Nova launcher - luckily its setting can be exported and backup via the app's functionality.
19) QQMusic - all my thousands of songs! - even if I back this up manually using ES explorer the app's internal linkage between playlist to songs will be broken. Will have to re-download all the songs to repair linkage and this means wasting another month of subscription fees for songs re-download. This is one of the most problematic app but it has DTS plagin which makes your music sound fantastic even with cheap earpiece, so I am putting up with it.
20) Skype - not much chat in there so that's fine to start over.
(iii) After backing up the limited stuff using Helium, I shall proceed to use another app to backup (1) to (12). And that app will be "MyBackup" (https://play.google.com/store/apps/details?id=com.rerware.android.MyBackup&hl=en). The app developer confirmed in its app's features that (1) to (12) are supported. Note "MyBackup" does not backup any app data at all when device is not rooted therefore step one using Helium is still necessary.
(iv) Next, to circumvent the limitation with failure to backup app & data for (13) to (20), my initial thought were to patch each app's manifest using this method (https://forum.xda-developers.com/an...g/guide-how-to-enable-adb-backup-app-t3495117). But then, as I studied further, I realized another chicken and egg scenario. That is, the decompiling, editing, recompiling and signing of the patched apk would need to take place first before using the app and not after. So in another word this method with each newly patched app will not seemlessly replace the existing app but rather the existing app will first have to be uninstall before the patched app can be installed, and that very act would mean losing existing data altogether.
To install on android the patched apk, you must first uninstall your previous version, and this is because the key used to sign the apk is different. If you try to install one app itself with a different signing key, you will get this error: [INSTALL_FAILED_ALREADY_EXISTS] [Unquote]
Given this ****ty situation, I guess I am still hesitant and not ready to move forward with bootloader unlocking. Sigh...
Click to expand...
Click to collapse
Hi!
!! This is quite serious! I need to get my data (pictures, videos) out of my phone, which is possibly soft-bricked.
I did the following in hope of more usage opportunities with my new phone:
[Unlocked bootloader + Rooted it]
1. installed TWRP following this guide https://forum.xda-developers.com/p10/development/testers-twrp-t3585256;
2. rooted following this guide https://forum.xda-developers.com/p10/help/root-huawei-p10-p10-t3589946;
3. installed few apps like greenify, wi-fi hacking apps etc, and everything was good.
BUT then 1 app (don't remember which) requested that it needs SuperSU and not the one root permission app that I had. So it asked whether I want to install it. I thought - yes, why not. Then it said that before it can install SuperSU it needs to uninstall previous permission app - I clicked OK. Then it kind of started, but then failed the installation. Ok, I kind of closed it and there were no problems. But after next restart of the phone it was stuck on boot process..
I dont really care about the phone, but data on it is so important. I tried sme fast hend methrods to boot it, like wiping catch, dalvik catch, but it did not work out.
Next I looked for possobilities to rescue data, but I didn't succeed.
Easiest mentioned option - to enter twrp and connect via usb seemed promising, BUT data are shown encrypted.
Please see the picture - I tried to be as precise as I could, so that you can understand the situation.
! I can beckup all data to micro sd card, but would it decrypt after new install of stock rom (e.g. from eRecovery that Huawei provides) and allow access or not?
Please help me. I am willing to have 1-on-1 skype chat and give some donations for this as it is so important.
To mention: Rescue apps like EaseUS seems to be useless, because they state to recover data from bricked device, but then after installing soft it askes to allow usb-debbuging, but c'mon, it's not booting up.. .
So,
1. Is there a chance to recover data?
2. Is it a good sign that 16GB of data are showing even if files are shown encrypted?
3. data are also showing on pc, when connected on twrp, but also encrypted.
Any help will be appreciated!
Additionally quite important question: at this state (possible soft brick + encrypted files), is there a chance that if I make a backup to MicroSd card of all the data and then take it our to reinstall rooted stock version of my android that later puting backup in will show my files that were backuped? Could ir be so that phone luckiliy decrypt them itself because it is the same phone? Hope this is clear what I mean.
OK, hopefully all is not lost.
First things first, be REALLY careful. If you start applying factory images, wiping things and generally messing about, if you don't know what you're doing you're putting your data in a lot of danger - Huawei devices do things in weird ways, so be super sure you know the consequences of what you're doing.
Now that's out of the way... it sounds like you haven't done anything to wipe the data. Also, you've already previously unlocked the bootloader which should put you in a good situation. You need to discount TWRP as a potential solution - there is no working decryption for TWRP yet on the Kirin 960 devices and from conversations I've had, it doesn't sound like that is imminent.
What it sounds like has happened is that messing about with root has messed up something on your system partition. Which should be fixable!
As a first step, this is what I'd do.
- Check which version your phone is on if you don't know already (you should be able to find this in ' /version/special_cust/VTR-L09/hw/eu/prop/local.prop')
- Find a full dload zip for the appropriate version (use FirmwareFinder if needed)
- Download the zip an extract the dload app
- Use splitupdate to split the images out of the dload
- Boot the device to bootloader ('adb reboot bootloader' or power on with cable connected and volume down pressed) then do 'fastboot flash system SYSTEM.img'
- Flash BOOT.img too
- Try booting
Hopefully this will fix it, but at the very least it'll get your system partition back to a stock state.
Let me know how it goes. Good luck!
P