Related
I flashed Evil Eris 3.0 couple days ago and could out get the A2SD function to working so I decided that I want to go back to a previous version where A2SD works. When I reboot into recovery menu, I found that everything else works fine with the trackball except the downward direction. That really pissed me off because no matter how hard I try to scroll it down, it does not work. Now the recovery menu does not work for me anymore except the reboot function. It seems that it is the problem with trackball itself because when I reboot it into the system the downward direction still does not work. Anyway, I am thinking about flashing the ROM with terminal commands. Anyone who can help me with this? I'm using recovery image 1.6.2. Whats the command line for wiping the four things(I am not even sure if there is four or five because I cannot get into it! aaahhh) under the wipe function? For partitioning SD card? For upgrading from ext 2 to ext 3(if i remember this function right)? And finally whats the command line for flashing a ROM from SD card? Thanks!!!! Now I really wish that I had the Droid cuz theres a physical D-pad on it!
This will solve your issue:
http://www.xda-developers.com/android/trackball-transplant-on-htc-droid-eris/
Don't forget that when Amon_RA recovery is booted up, "adbd" is running on the phone.
That means that you can get your restore operations done by using ADB on the PC, and the
/sbin/nandroid-mobile.sh
script in Amon_RA to perform all the operations that you would have with the menu system.
do a /sbin/nandroid-mobile.sh --help
with Amon_RA recovery booted, and have a look at the
--listbackup
--subname
--restore
options for more information.
Obviously, this won't fix your trackball. But it does give you access to restore and backup operations in the meantime.
bftb0
I am a newbie with terminal and command lines, so I hope you don't mind if I ask some questions here. I checked the help list of nandroid-mobile script, but I think all the functions are to do with nandroid backup file? it is either to back up or to restore a backup file? I have successfully backed up though. But how do I wipe my dalvik cache and other misc. stuff in the recovery menu? How do I partition my sdcard using the script? and flash an img?
My trackball went out on me the other night when I was working on it. Or so I thought. Just before I called Verizon to send me a replacement, I tried one last ditch effort. I used my tshirt to wipe whatever was on the ball and pressed it kind of hard when moving the trackball around and what do you know, it fixed it. I only use my trackball for when flashing, which is a lot. So hopefully this might help you.
lacrisexistentielle said:
I am a newbie with terminal and command lines, so I hope you don't mind if I ask some questions here. I checked the help list of nandroid-mobile script, but I think all the functions are to do with nandroid backup file? it is either to back up or to restore a backup file? I have successfully backed up though. But how do I wipe my dalvik cache and other misc. stuff in the recovery menu? How do I partition my sdcard using the script? and flash an img?
Click to expand...
Click to collapse
That script only does a couple things in addition to nandroid backup and restores - it is not a replacement for the Amon_RA menu.
Your original post indicated that you were trying to restore a previously saved ROM backup, so that I why I suggested it.
Obviously, it would be better if you got your trackball fixed.
As far as wipes go, here is what happens during a wipe:
Code:
mount /system
cd /system
rm -rf /system/* >>/dev/null 2>&1
cd /
umount /system
mount /data
cd /data
rm -rf /data/* >>/dev/null 2>&1
cd /
umount /data
Since - as you said - you are a newcomer to command lines, you probably shouldn't be doing the above. In particular, the "rm" commands above are extremely dangerous if you don't know what you are doing (although I tried to minimize the danger with the superfluous-looking "cd" commands.
If you would like to learn more about using the command line, or scripting, just pull that file to your PC
adb pull /sbin/nandroid-mobile.sh nandroid-mobile.sh
and study it intently (shell scripts are plain text files). You will learn a lot about what goes on "under the hood" that way.
cheers
bftb0
I'm in the same boat as the original poster. Just need the code to push a stock or closer to stock ROM so I can return to Verizon.
-------------------------------------
Sent via the XDA Tapatalk App
thanks so much! I think I will replace my trackball just for safety. I don't want to temper with the command line that I have no idea of yet! I will certainly look into the shell script later. Also, if I want to learn more basic stuff with the terminal language, what should I do? is there any wikis or websites or even books teaching the language? I am intrigued by all these custom ROMs available for android system and I would love to learn how to build one on my own!
WOW, that is awesome! I never thought that I would be able to do that but this looks so simple!
I tried to push it really hard but nothing changed. I start to wonder if this is a common problem seen in Eris owners? I just couldn't imagine why the trackball will be senseless. Thanks for your tip though!
I just wanted to share a story of woe and redemption so that it doesn't happen to you.
As background, I had sim unlocked my phone using helroz's method a while back, and my phone has been working fine from team whiskey's early days till now. Recently, I was flashing my phone as most of us do. I noted that after flashing the dead horse kernel, my market was not working properly, so I decided to odin back to JFD. From there, I flashed Bionix, but afterward, noted that I wasn't getting any cell reception. After some investigation and several odins, I looked at my software info and found that my baseband was unknown. I flashed back to JFD however, and it worked fine. In fact, this was the only rom where the cell worked. The phone otherwise was functioning flawlessly, including wifi.
Further investigation showed that this has happened to others, and anecdotally, people have fixed it by odining over and over or doing some magic with their sim card. I did just that but to no avail. After some thinking, it occurred to me that maybe my /efs data was bad, so I took a look. Hitting *#06# showed the generic samsung IMEI while in JFD (it did not work in other versions as the baseband was not working), not my normal IMEI. That's odd. I still had the backup from trying to sim unlock it months ago. I tried to overwrite the /efs folder w/ my own, but I could not write it due to 'not enough space.'
Further investigation showed that indeed, my efs partition had been borked, and so I could not write data to it (I could copy however). The only way to fix this is by flashing/odin'ing a new partition. This only works if you have a backup, which I didn't. Basically, I had a fancy media player at this point.
I went ahead and looked on craigslist and found a vibrant w/ a broken screen, figuring I could swap out the guts. I immediately backed up the /efs folder and partition of the broken phone, just in case. On a whim, I tried to flash the efs partition from the broken phone to my phone. Lo and behold, the baseband came back. I was now able to write to that partition, so overwrote the /efs folder w/ my backup from before. My IMEI came back afterwards, and so now, I have 2 functioning vibrants. I'm not sure what data is stored in /dev/block/stl3, but I do know I was able to fix my phone using another phone's data. They both work w/ my sim, though I am unsure if they can connect simultaneously using different sims or if they are somehow cloned, but the IMEIs are different for sure.
The moral of the story is that this phone is nigh unbrickable and even when it doesn't boot, you can always try the jig. The only part of the phone you can't fix w/ a routine odin it seems, is the efs partition, so I would encourage everyone to make a backup and keep it safe. This is not done standard as an initiation into rooting and roms and such, but it should be. Normally, odin'ing a rom does not write to this area, but even w/o screwing with this, frequent flashing and odins can apparently corrupt it, leaving you high and dry. With this backup and odin, you could probably fix your phone from any jam.
Here are the relevant threads on how to do this:
http://forum.xda-developers.com/showthread.php?t=882039
http://forum.xda-developers.com/showthread.php?t=859914
Keep those backups safe!
Thank you for sharing ur experience, I recently noticed that my data speeds have gone down after unlocking my vibrant using the method you mentioned above.Damn, I get edge speeds when I am on a HSPA network. Dunno whats the problem,called up simple mobile,am not data throttled.Sigh..
Sent from my SGH-T959 using XDA App
man this is scary, but your phone still works at JFD right?
Sent from my SGH-T959 using XDA App
It didn't for a while. Now, both phones are fully functional. I had a copy of the /efs folder of my old phone, but not an image of the partition. The problem is, when the partition gets screwed, you can't write to it, making the /efs useless.
That's why I'm trying to get people to make the backup. It takes a few minutes, but can be a lifesaver. I do believe you can flash a foreign stl3 partition and overwrite the /efs like I did, but unless you had a friend, no one would share it w/ you as it contains their imei info. Better to just back up your own. And if you lose your /efs, game over.
How exactly do you back up a partition?
Very cool of you to post this up. Is there any reason to back up your efs partition if you have no reason to unlock?
<---backing it up anyway.
It's not the unlocking. It seems that over time, some people (such as myself) screwed up the efs partition by just flashing/odin'ing various roms. It shouldn't happen, but it does. Consider that no roms write to the stl3 layer, yet mine was working one day, then one odin later, it didn't. I'm sure the number of people this happens to is quite small, but when it happens, it happens. It's like a 6 mb backup which isn't that big of a deal.
It's better to be safe than sorry.
I did an experiment on my Galaxy Tab, that I move the /efs folder to memory card.
Soon I found the reception goes way worse (at least 10dBm less) and the serial number changed to 00000000, then I immediately copied (restore) the folder and everything was back to normal.
I tried to examine the files with hex editor but I found nothing spectular.
vnamee said:
It's not the unlocking. It seems that over time, some people (such as myself) screwed up the efs partition by just flashing/odin'ing various roms. It shouldn't happen, but it does. Consider that no roms write to the stl3 layer, yet mine was working one day, then one odin later, it didn't. I'm sure the number of people this happens to is quite small, but when it happens, it happens. It's like a 6 mb backup which isn't that big of a deal.
Click to expand...
Click to collapse
That's really weird. I've never really looked into the occurrence because I always assumed it was isolated only to those that did some weird hacking in an attempt to unlock, or to those that were developing and found themselves doing some nasty, nasty things.
I just created efs_dev-block-st13.img and efs-backup.tar.gz so hopefully I'm all safe and sound now.
Thanks again! Once I get beyond GPS stuff I find myself clueless.
draikz said:
How exactly do you back up a partition?
Click to expand...
Click to collapse
You need to read the two links in the OP and download adb. You also need root and busybox.
all you need is to root your phone, such as w/ superoneclick which will put busybox on there. Then all you need is adb.exe.
Open up a command prompt where adb.exe is located. You can adb su or just go adb shell and then su.
The only commands you need are:
cat /dev/block/stl3 > /sdcard/stl3.bin (backs up sector management layer of partition)
cat /dev/block/bml3 > /sdcard/bml3.bin (backs up block management layer of partition)
tar zcvf /sdcard/efs-backup.tar.gz /efs (tars /efs folder)
cp stl3.bin efs.rfs (just makes copy of stl3.bin to new name efs.rfs)
tar -cf efs.tar efs.rfs (makes an odin flashable tar of partition)
I kept a copy of stl3.bin, bml3.bin, efs-backup.tar, and efs.tar.
vnamee said:
all you need is to root your phone, such as w/ superoneclick which will put busybox on there. Then all you need is adb.exe.
Open up a command prompt where adb.exe is located. You can adb su or just go adb shell and then su.
The only commands you need are:
cat /dev/block/stl3 > /sdcard/stl3.bin (backs up sector management layer of partition)
cat /dev/block/bml3 > /sdcard/bml3.bin (backs up block management layer of partition)
tar zcvf /sdcard/efs-backup.tar.gz /efs (tars /efs folder)
cp stl3.bin efs.rfs (just makes copy of stl3.bin to new name efs.rfs)
tar -cf efs.tar efs.rfs (makes an odin flashable tar of partition)
I kept a copy of stl3.bin, bml3.bin, efs-backup.tar, and efs.tar.
Click to expand...
Click to collapse
I've got backups of stl3.bin, bml3.bin and efs-backup.tar.gz
When I try to make the partition an odin flashable tar it tells me: "No such file or directory".
You have to cd into the directory, or else it should be:
cp /sdcard/stl3.bin /sdcard/efs.rfs (just makes copy of stl3.bin to new name efs.rfs)
tar -cf /sdcard/efs.tar /sdcard/efs.rfs (makes an odin flashable tar of partition)
This is kind of old news, but nevertheless important.
Months ago in the Q&A section there were two threads about the importance of the EFS, and how a corrupted nv_data.bin and EFS can cause many problems including losing the ability to use a different carriers sim, yet nobody paid attention to those threads, but I thought the info was vital.
Would using ROM Manager and backing up your current rom, also backup the /efs?
vnamee said:
You have to cd into the directory, or else it should be:
cp /sdcard/stl3.bin /sdcard/efs.rfs (just makes copy of stl3.bin to new name efs.rfs)
tar -cf /sdcard/efs.tar /sdcard/efs.rfs (makes an odin flashable tar of partition)
Click to expand...
Click to collapse
Yeah, I did. I'll do it again and post up exactly what I type and put in. Maybe it's just operator error.
Here ya go.
It might have been operator error because that time I watched efs.tar get written to /sdcard
It should be efs.rfs, not efs/rfs. It's a file, not a directory.
SamsungVibrant said:
Would using ROM Manager and backing up your current rom, also backup the /efs?
Click to expand...
Click to collapse
Nandroid does not back up the /efs partition, at least not that I can tell. All those files in the backup folder are of the various partitions, and efs partition is not part of it.
The reason I made this thread to begin with is because when I had this problem, I looked high and low, and found scant info. In the future, if someone else has this problem, this will come up in a search and won't have some lame magical fix that may or may not work.
vnamee said:
It should be efs.rfs, not efs/rfs. It's a file, not a directory.
Click to expand...
Click to collapse
Pinky slip!!! For whatever reason, it took 3 tries but I finally got it to backup. Thanks for the help! I would never think to back this stuff up. Everyone does Nandroid's like crazy, which is good, but losing this stuff is losing your phone!
Excellent write-up vnamee thank you..........
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
**Removed - wait for JCSullins official release**
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
For those not in the know, it is recommended to update your recovery and essential if you plan to update to cm10. This fixes s file system corruption bug that shows up when expanding the partition in preparation for cm10.
Sent from my HP TouchPad using Tapatalk 2
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
"Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here."
Click to expand...
Click to collapse
Open terminal
type
su
umount -o remount,rw /boot
then use es file explorer.
chadster1976 said:
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
Click to expand...
Click to collapse
Rom Toolbox lite will allow you to .
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
I flashed it and now I'm soft bricked. Can't boot into sk8's CWR6, CM10 or anything.
Lesson learned, ask developers before posting there work
Sent from my Galaxy Nexus using xda app-developers app
It likely not the CWM6 that did it but the boot partition full. If you have an extra webos kernel, some moboot themes, TWRP, and then this new larger uImage for CWM you will likely run out of space.
Probably should put that warning here it's pretty important people realize it and/or add a script to remove TWRP, to prevent issues with this zip.
@jcsullins +1 Feedback. Installed your CWM uImage manually. Mounted as mass storage in CWM, copied files, Installed latest CM10 12/05(over older CM10 installed with Acme3), Installed Gapps, Installed Camera Preview 3 patch, Installed WEBCM10, cleared both caches in CWM and noticed no issues during all the processes.
I ACMEU wiped and ACME3'd the whole deal back on w/new recovery. It needed the clean up anyways and I had a NAND from yesterday.
Nice, thanks JC.
Roland Makes oopsy
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Thank you for taking the time to create this great new CWM6. I have been really enjoying the new looks and graphics. I have tested flashing different zips and Roms. I have made and restored Nandroid backups and even restored older CWM5 backups with CWM6. I do this to try and help but sometimes I really step in $#@# trying to help, like with the 4.2gapps.
Sorry about being so anxious to get this out to the public. I have had a lot of complaints about Bricked TouchPads and would like to get the word out about the problem and how to fix/prevent it.
I feel very responsible for the people affected due to me making an install video without knowledge of the corruption issue beforehand.
I wanted to make a video explaining that there was an issue but to fix it they can, Backup, uninstall, reinstall and restore. To prevent future issues I want to included this in my install instructions. They would of course need your New CWM6 to do this and I have been eagerly awaiting this fix.
Sorry about all my stupid mistakes, I get a bit over excited about Tech stuff at times. Please accept my sincerest apologies.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
I'm sorry, but I didn't see your post in Rootzwiki or I would have posted there.
This cwm has worked flawlessly. I haven't had a chance to try all the new features, but the ones I did try worked fine.
Thanks so much for this. The old 5.0.2.6 was starting to show its age. I hope this cwm does away with the sporadic partitioning problems I'd been seeing.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
New Backup Options
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
webdroidmt said:
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
Click to expand...
Click to collapse
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
RolandDeschain79 said:
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
Click to expand...
Click to collapse
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
.dup & .tar enlightenment
webdroidmt said:
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
Click to expand...
Click to collapse
Thank you very much for the detailed response. I’m feeling good now that I am starting to understand the new recovery. I also really liked having those individual .tar backups:good:, I made one for each version of CM. I wonder how .dup backups will affect the free space on my device. I also backup a lot but I did find that i was able to restore the older CWM5 backups without a problem. I will probably just keep the older CWM5 .tars for CM7, CM9 and do my CM10 backing up with the newer .dup. Time to transfer some backups:victory:
Can we maybe get rid of the link in op? Jc has stated this was only for testing, you shouldn't host a devs work without permission, and maybe for the fact of it will soft brick a TP? Just saying....
Sent from my HTC VLE_U using xda app-developers app
Sorry for possibly misunderstanding but is it recommended to use this yet due to possible corruption issues with older versions of CWM or only intended for testing atm? I've been meaning to ACME uninstall the TP and reinstall CM10 clean again and if this newer version of recovery is recommended for flashing I'll throw it on there while I'm at it
Thx JCSullins! :fingers-crossed:
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Hello,
Sorry for that :/
I haven't seen your rootzwiki post and so far I was just willing to help users to install it
easily (seems that was my mistake :x) because after I gave it a try it solved the issues
I was having with the previous CWM one. There is just one thing that disturb me, in
Backup and Restore menu, 'choose backup format' should be rename in something like
"choose default backup format".
That's just my 2cents and besides this all functions work well, thanks for your hard work.
I'll remove the link from the OP post and wait for your public release
Sincerely, menthe.
Has anyone tried the adb sideload yet?
When attempting to sideload I get: * failed to write data 'protocol fault (no status)' *
Any other adb commands I issue are met with "error:closed"
I am stuck here because I don't have a power button to do a hard reset... please someone tell me this function is working and I am just doing something wrong. My TP has a full charge and I don't feel like waiting 8hrs for it to die so it can be reset.
Edit: just took the whole thing apart and pulled the battery
How hard would it be to create a script that runs on boot that formats /system if su is detected?
And could it be made into a flashable zip to be used on any phone?
Very happy to throw a nice donation your way if it can be done.
Thank you.
iBowToAndroid said:
How hard would it be to create a script that runs on boot that formats /system if su is detected?
And could it be made into a flashable zip to be used on any phone?
Very happy to throw a nice donation your way if it can be done.
Thank you.
Click to expand...
Click to collapse
It's not hard at all, but why would you want to do this?
abnormalreply said:
It's not hard at all, but why would you want to do this?
Click to expand...
Click to collapse
Ha. I spose that sounds a little suspicious. It's a long story, but basically I just want a script that I can run on a few of my devices so I can test out a few things, mainly via recovery and adb, really just making sure I can recover if something like that happens. Yeah I could wipe from recovery but I'd rather simulate the real thing, or if I have stock recovery, etc. I know a tiny bit about init but not enough to know how to write the script so I just figured it would be easier and quicker for someone to do it who actually has experience. I also realized that there's no need for a zip since I can just copy the script to any device I need. Basically "if /system/bin/su or /system/xbin/su exists, then format /system" - something like that, although I know the formatting is different. Yes I understand what I'm doing and the risks and have the restoration tools ready lol
iBowToAndroid said:
Ha. I spose that sounds a little suspicious. It's a long story, but basically I just want a script that I can run on a few of my devices so I can test out a few things, mainly via recovery and adb, really just making sure I can recover if something like that happens. Yeah I could wipe from recovery but I'd rather simulate the real thing, or if I have stock recovery, etc. I know a tiny bit about init but not enough to know how to write the script so I just figured it would be easier and quicker for someone to do it who actually has experience. I also realized that there's no need for a zip since I can just copy the script to any device I need. Basically "if /system/bin/su or /system/xbin/su exists, then format /system" - something like that, although I know the formatting is different. Yes I understand what I'm doing and the risks and have the restoration tools ready lol
Click to expand...
Click to collapse
I'm surprised you're able to test recovery/ADB scripts on your devices but don't know how to write the script you're describing.
Background
I do not plan on flashing roms, I have a rooted note 3(900t) with knox at 0x0(want to keep it that way). I do not want to backup APKs or personal information.
Desire
I only want to make a backup of all of my critical system files necessary to do a soft reboot. So that in a worst case scenario I never have to worry about not being able to reset my phone.
Reason
I plan on editing files with a root explorer and using Xposed framework.
Hope this is a little more clear, thanks for the help!
7US said:
I have a rooted note 3 with a knox warranty of 0x0. I would like to make a full backup of any system files that could become corrupted so that I may restore them without tripping the knox. I do not care about backing up Apps(Actually prefer to manually install them as I need them), I have all of my APK files manually backed up. Additionally I want to install Xprivacy and Xposed framework but they always warn to do a full backup. I was playing around with ADB as well but that backup seems to be directed at Apps and Contacts which I don't care about. Would it be safe to just install Xposed framework and Xprivacy and rely on the factory reset? Or is there some method I should use of doing a complete system backup. Also how would I restore that backup? (preferably I would like to have a nice backup/recovery method that I know I can always restore from my computer in case somehow one of my system files get deleted) Thank you for your help. I like to edit my system files and I have no problem using the standard phone reset I am more worried about critical failures really just as a failsafe.
Click to expand...
Click to collapse
too long.
if i get right from this longe sentences;
u cannot backup knox counter.
u can make nandroid backup from ur system but knox counter will change its value.
:good:
x102x96x said:
too long.
if i get right from this longe sentences;
u cannot backup knox counter.
u can make nandroid backup from ur system but knox counter will change its value.
:good:
Click to expand...
Click to collapse
I fixed my original post, hope it is more clear for you.
I know I cannot backup my knox counter, which is why I do not plan on installing CWM.
I am new to the Android operating system and read many threads about different methods of backing up and restoring(CWM/Titanium Backup/etc) but they always seem to be centered around backing up APKs+Contacts or backing up Roms for Rom Flashing.
I am trying to understand what I need to backup to be safe to play around with my system files and Xposed and always be able to restore any damage that I may do.
So far I played around with ADB a little bit and saw some tutorials on how to do full backups through ADB but not for the note 3. Thanks for your help! I plan on experimenting and such on my own but first I want to make sure I have necessary backups to not worry about crippling the OS.
Perhaps a question within my question is.. What type of backup do I need? What files need to be preserved for me to be able to do a system reboot to restore the phone? Is it safe for me to be using Xposed without a backup and playing around with system files? Will the soft reboot restore these files? If not what needs to be backed up, that really is my question.
7US said:
I fixed my original post, hope it is more clear for you.
I know I cannot backup my knox counter, which is why I do not plan on installing CWM.
I am new to the Android operating system and read many threads about different methods of backing up and restoring(CWM/Titanium Backup/etc) but they always seem to be centered around backing up APKs+Contacts or backing up Roms for Rom Flashing.
I am trying to understand what I need to backup to be safe to play around with my system files and Xposed and always be able to restore any damage that I may do.
So far I played around with ADB a little bit and saw some tutorials on how to do full backups through ADB but not for the note 3. Thanks for your help! I plan on experimenting and such on my own but first I want to make sure I have necessary backups to not worry about crippling the OS.
Perhaps a question within my question is.. What type of backup do I need? What files need to be preserved for me to be able to do a system reboot to restore the phone? Is it safe for me to be using Xposed without a backup and playing around with system files? Will the soft reboot restore these files? If not what needs to be backed up, that really is my question.
Click to expand...
Click to collapse
instead of making backup of ur system files u can download a firmware of ur region!
if something goes wrong when u try to modifying then flash the stock rom.
however u can easily copy a file to another direction and then paste back to original if issue appears.
for example build.prop and etc.
and for ur firmware as i said u can make nandroid backup (thr s lots of tools in play.store for it that not need custom recovery) (if i say correctly!)
:good:
7US said:
Background
I do not plan on flashing roms, I have a rooted note 3(900t) with knox at 0x0(want to keep it that way). I do not want to backup APKs or personal information.
Desire
I only want to make a backup of all of my critical system files necessary to do a soft reboot. So that in a worst case scenario I never have to worry about not being able to reset my phone.
Click to expand...
Click to collapse
suggestion:
you could use safestrap.
it is based on the twrp custom recovery but it will not trip knox !
read the thread before using it. you have some more benefits using ss, you will see.
backup the system and data partition and you are safe.
please note that this will never backup the content of your internal storage like your music, videos ond so on.
just dont wipe/format your internal storage from recovery or if you feel you need to, copy the whole content to your pc first.
additional things to backup:
you might want to backup your efs and maybe your pit file too.
easy to find info on this forum.
if you want to read more about backing up via adb, directly to the pc then this thread is for you.
i made a backup of the whole memory block one time, just for the worst case...
basicly, you just need the required files, open 2 cygwin windows and copy and paste(right click) the commands from the first 2 codeboxes from the thread into that windows.
hope this helps
A.N.Droid said:
suggestion:
you could use safestrap.
it is based on the twrp custom recovery but it will not trip knox !
read the thread before using it. you have some more benefits using ss, you will see.
backup the system and data partition and you are safe.
please note that this will never backup the content of your internal storage like your music, videos ond so on.
just dont wipe/format your internal storage from recovery or if you feel you need to, copy the whole content to your pc first.
additional things to backup:
you might want to backup your efs and maybe your pit file too.
easy to find info on this forum.
if you want to read more about backing up via adb, directly to the pc then this thread is for you.
i made a backup of the whole memory block one time, just for the worst case...
basicly, you just need the required files, open 2 cygwin windows and copy and paste(right click) the commands from the first 2 codeboxes from the thread into that windows.
hope this helps
Click to expand...
Click to collapse
Very interesting! Reading the 2nd link made me think... could I even recover my files through ADB if I crippled my OS? Don't I need to boot into the device to even get to ADB? Or can I access ADB through the stock boot screen without CWM? Safestrap also looks very tempting. Also do you have a list of the note 3 partitions for me to make ADB backups I have been looking for them on Google and can't find them anywhere the Android file structure is a jungle to me especially how it varies from phone to phone.
7US said:
Very interesting! Reading the 2nd link made me think... could I even recover my files through ADB if I crippled my OS? Don't I need to boot into the device to even get to ADB? Or can I access ADB through the stock boot screen without CWM? Safestrap also looks very tempting. Also do you have a list of the note 3 partitions for me to make ADB backups I have been looking for them on Google and can't find them anywhere the Android file structure is a jungle to me especially how it varies from phone to phone.
Click to expand...
Click to collapse
i´m not sure for the stock recovery but from twrp you can use this adb backup method. i just did it a few days ago.
you must change the path in the commands from /system/xbin to /sbin and no need for su.
it should work from safestrap too but i couldn´t get adb to work, some error message was shown.
for the partitions:
system ,data, efs
and maybe modemst1 and modemst2
theres a full list of partitions and an interesting discussion about this topic on this thread.