sorry if this may be dup.. I could not find a similar posting.
Does anyone know how to modify the default boot order for mboot? Right now it defaults to CM7. I would prefer it default to webos. Thanks
edit /boot/moboot.default. Put "webOS" without the quotes. Save and reboot.
kmdub said:
edit /boot/moboot.default. Put "webOS" without the quotes. Save and reboot.
Click to expand...
Click to collapse
Way to be unhelpful.
Open moboot.zip > read the README.
From a webOS terminal
Code:
mount -o remount,rw /boot
cd /boot
echo "webOS" >moboot.default
sync
or could also try
Code:
mount -o remount,rw /boot
echo "webOS" >/boot/moboot.default
sync
Or you can install an app to change it from webOS. http://rootzwiki.com/topic/8273-rc1-an-app-to-manage-moboot-settings-from-inside-webos/
Way to be unhelpful.
Click to expand...
Click to collapse
So, telling him/her to edit moboot.default, then save it (essentially what you did), is unhelpful? Excuse me if I didn't explicitly state that the file system need to be mounted RW. I may have assumed too much. If you just type "reboot" after writing the file instead of "sync", you not only see the fruits of your labor, but you also remount the file system RO, instead of leaving it RW. Do you know that there are other ways to sync other than typing "sync"? For example, a reboot. You do understand that those are not "magic" Linux commands for editing the mysterious moboot.default text file, right?
I dislike parroting douchebags who call others unhelpful because he/she perceives an opportunity to display his/her technical prowess, even if it may not be required.
I apologize to the original poster for not being clearer and giving step-by-step instructions.
kmdub said:
So, telling him/her to edit moboot.default, then save it (essentially what you did), is unhelpful? Excuse me if I didn't explicitly state that the file system need to be mounted RW. I may have assumed too much. If you just type "reboot" after writing the file instead of "sync", you not only see the fruits of your labor, but you also remount the file system RO, instead of leaving it RW. Do you know that there are other ways to sync other than typing "sync"? For example, a reboot. You do understand that those are not "magic" Linux commands for editing the mysterious moboot.default text file, right?
I dislike parroting douchebags who call others unhelpful because he/she perceives an opportunity to display his/her technical prowess, even if it may not be required.
I apologize to the original poster for not being clearer and giving step-by-step instructions.
Click to expand...
Click to collapse
How would they know the commands to actually edit said moboot.default files without you being technical....so well, my technical douchbaggery was required.
Also didn't type the whole reboot thing because I figured the OP would reboot to check if it worked anyway...
For a quick answer there's an app in preware that will do this. Just boot into webos.
Thanks!
Thanks all... I really appreciate the quick turnaround of responses.
Related
Confirmed by droopypillow -Thanks
This fix is NOT just for the market not downloading apps issue, it actually was bugging me quite a lot that none of my apps were attached to the market so I had to use alternative methods, like app brain or an app updater app to know when I could update my apps
HebrewToYou was kind enough to tell us how to fix only the part where the market won't download apps if you have 1.5 cache set in your custom MTD partitions. So either do this or resize your cache to like 60 as recommended by the helpful fellow aaldiar
HebrewToYou said:
So here's an *actual* fix that doesn't involve replacing the Market app...
...it appears this issue may be localized to people with custom MTD partitions.
Thanks go out to JTownBrewer and FredBo (on #mytouchslide @ freenode IRC) for figuring this out:
Open up your favorite terminal emulator -- I like Better Terminal Emulator Pro -- and enter...
Code:
su
cp -a /dev/cache/download /data/cache
Market apps will once again be downloading properly. This *may* not work after rebooting, so just keep that in mind.
Click to expand...
Click to collapse
What this fixes
Apps not being attached to the market
(Make sense since I have Custom MTD partitions) HebrewToYou tells me that only for users with custom MTD partitions: Not being able to download apps (since build 20)
The Only Requirement
Must have ADB.exe and must know how to get to it through command prompt, my steps are simple enough that that is the only thing you need to know.
Windows Instructions I guess, not so sure how different on Mac or Linux
Download the Vending.apk I attached at the bottem
Put Vending.apk in the folder where adb.exe is located
Go to folder where adb.exe is located with command prompt
This may or may not be unnecessary, but force close and clear you cache on the Market app. It's what I did so just in case, k?
On your phone either go into recovery, or if you have S-Off I think you can type
Code:
adb shell
mount -o rw,remount /system
exit
and you should be able to push to /system without a problem, may be unnecessary but I always do it so I had to add that part
Then in your command prompt type
Code:
adb push Vending.apk /system/app
Open your Marketplace now and see if it's working.
What I did is I took the Vending.apk from the cm6 g-apps, I assure you it works perfect except it is an older version of the marketplace, so maybe it even has the 24 hours for a refund still? I'm not sure and I don't really feel like checking. My phone hasn't tried to update the marketplace so it I've been using this fine for the past 2 days when I first noticed my market wasn't working but at the time I thought it was just me because of a few issues I caused myself
RESERVED to include additional info about what build this error is fixed on when Cyanogen fixes this issue for all devices
All I did for my market to work was download the same file 5 times.. it wouldn't install.. then reboot the phone, try to download apps again like 2 more tries and now market works for me.
Gj on the app too
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
xaodxkevin said:
If you're good with ADB: For anyone who's got a bit of expertise with adb and whatnot, please post if there are any errors in this post and what should be different for I am sick and there may be errors. Seriously though I really need some sleep, good night.
I cannot stress this enough!Please read comments before doing this, there may be an error in my post =\ and hopefully someone's posted the correction or confirmed that this works 100%
I'm really sick, but I felt this could help many people so I'm posting this anyways hoping I don't make any errors and I really don't feel like making this look very nice right now but heres a temp fix
The Only Requirement
Must have ADB.exe and must know how to get to it through command prompt, my steps are simple enough that that is the only thing you need to know.
What this fixes
Not being able to download apps (since build 20?)
And apps not being attached to the market
Windows Instructions I guess, not so sure how different on Mac or Linux
Download the Vending.apk I attached at the bottem
Put Vending.apk in the folder where adb.exe is located
Go to folder where adb.exe is located with command prompt
This may or may not be unnecessary, but force close and clear you cache on the Market app. It's what I did so just in case, k?
On your phone either go into recovery, or if you have S-Off I think you can type
Code:
adb shell
mount -o rw,remount /system
exit
and you should be able to push to /system without a problem, may be unnecessary but I always do it so I had to add that part
Then in your command prompt type
Code:
adb push Vending.apk /system/app
Open your Marketplace now and see if it's working.
What I did is I took the Vending.apk from the cm6 g-apps, I assure you it works perfect except it is an older version of the marketplace, so maybe it even has the 24 hours for a refund still? I'm not sure and I don't really feel like checking. My phone hasn't tried to update the marketplace so it I've been using this fine for the past 2 days when I first noticed my market wasn't working but at the time I thought it was just me because of a few issues I caused myself
p.s.
If this is in the wrong location, move it please? I wasn't too sure where to put this
+
if there are any errors here please post? seriously I'm really sick and this took every ounce of energy and concentration I had so there may be a mistake somewhere and yes I've proof read it about 100x now >:|
Click to expand...
Click to collapse
ive market downloading issues since build 20..i did everything step by step except step 4..and now my market works...thanks for the temporary fix
So here's an *actual* fix that doesn't involve replacing the Market app...
...it appears this issue may be localized to people with custom MTD partitions.
Thanks go out to JTownBrewer and FredBo (on #mytouchslide @ freenode IRC) for figuring this out:
Open up your favorite terminal emulator -- I like Better Terminal Emulator Pro -- and enter...
Code:
su
cp -a /dev/cache/download /data/cache
Market apps will once again be downloading properly. This *may* not work after rebooting, so just keep that in mind.
Thanks for confirming droopypillow
And
Thanks HebrewToYou for the fix once I get home I'll add note of it and credit you, but I still prefer this one because it keeps my apps attached to the market. I'm not sure exactly who/why people are getting that issue but I'll definitely be happy with the old market until I hear that's fixed.
I flashed build 26 market is working again on this build for me..
Sent from my T-Mobile myTouch 3G Slide using XDA App
I have the custom MTD partitions and simply changed the cache from 1.5 to 60 and that solved my Market and GPS problems instantly. Just an FYI for you guys.
aaldiar said:
I have the custom MTD partitions and simply changed the cache from 1.5 to 60 and that solved my Market and GPS problems instantly. Just an FYI for you guys.
Click to expand...
Click to collapse
so the cache was also causing the GPS problems? Thanks, I'll make sure to change the cache size immediately
I'll continue using this though until the apps being attached to market issue is fixed
xaodxkevin said:
so the cache was also causing the GPS problems? Thanks, I'll make sure to change the cache size immediately
I'll continue using this though until the apps being attached to market issue is fixed
Click to expand...
Click to collapse
I have a 1.5meg cache and have no issues with gps...I had market problems from. Build 20-25..but I did nothing wxcept flash build 26 and it is fixed..
Sent from my T-Mobile myTouch 3G Slide using XDA App
Yeah, I don't think the cache partition size has anything to do with GPS issues. This was purely a fix for the market.
Lol, I know it is a fix for the market. But I still had GPS issues with 26 along with market problems. Might just be some hardware dealio with my particular slide series or something. All I know is once I did the partition my GPS and market worked instantly.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I'm on nightly #27, no market issues. Custom mtd with cache @ 1.5 as well.
How do I see what the cache size is and change it?
(Sorry for the noob question).
Please see this thread: http://forum.xda-developers.com/showthread.php?t=893706
i am running custom mtd and notice for some reason something keeps remounting my /sd-ext and /cache partition to RO which causes the failure. Rebooting and updating/installing the apps right away usually works but it's only a matter of time before it gets remount as RO. Also adb shell will not allow me to remount it back to RW, it doesn't give me any errors using mount but it just stays at RO.
right after a reboot:
Code:
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on /sd-ext type ext3 (rw,noatime,nodiratime,errors=continue,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext3 (rw,noatime,nodiratime,errors=continue,barrier=1,data=ordered)
/dev/block/mtdblock4 on /dev/cache type yaffs2 (rw,nosuid,nodev)
after running:
Code:
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on /sd-ext type ext3 (ro,noatime,nodiratime,errors=continue,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext3 (ro,noatime,nodiratime,errors=continue,barrier=1,data=ordered)
/dev/block/mtdblock4 on /dev/cache type yaffs2 (rw,nosuid,nodev)
*edit* failed again
*Mods, please move if in wrong thread*
I am developing a ROM for a major company, but I have a few questions, probably for very advanced developers...
1. Is it possible to develop an app, and incorporate it directly into a rom, almost as if it were a setting? So, instead of the user clicking on the app, can I make it as a built in function of the ROM?
2. Since I'm developing for a company, is there any way to disable installing any other app, even from the market?
3. Also, is there any way possible, to have a centralized "server" for the rom, to see where all of the devices are (gps), and be able to update the rom from the server?? Kind of my own OTA updates..
How would I go about this? Where to begin?
Any help would be appreciated, Thank you in advance
Yes, it's all possible, but with the caveat that a user who knows what he's doing will be able to reverse you changes. If you can get a root shell via adb, you can remove the package installer and install your own applications by remounting the system filesystem read/write with
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
at that point it's just a matter of moving the APK to /system/app/ . Reboot immediately afterwards to avoid any trouble.
#3 is a bit harder since remounting isn't something you want to do while the user is handling the device (it can cause all kinds of weird behavior).... but it's possible. At the very least you should only remount when an update is actually applied and restart immediately afterwards.
Of course, if your users know how to handle ADB, it will all fall to pieces as they will be able to do exactly what you're doing. Setting a password for root might work... but it's as likely to trash the device since Android assumes that it's run by root and if the underlying Linux system should suddenly ask for a root password during boot there won't be any UI to actually enter the password.
Hello Android Devs,
I am a linux admin, looking to help out. Is there a good place to do a quick comparison of commands btw linux and android ? Or where various scripts / special android locations of files.
I have been typing into my touchpad's Terminal Emulator and getting pretty irritated with no tab completion. I think I am going to buy a bluetooth keyboard. The other issue I was hoping Devs could help me find is, where is the fsck.vfat ? or e2fsck -o vfat? I have been having heck of time trying to find this and other normal linux commands without locate or tab completion. man e2fsck (no man pages found lol).
My "sdcard" in dmesg says needs to fsck'd, and I would like to help out because I see forum posts here and rootkitz.forums about just deleting the partition lol.
Thanks for advice
SorrowsTyr
Install Hacker's Keyboard from Market, this one has buttons like Ctrl and Tab.
Sweet I will try that thanks!
-Gary
On my Droid3 e2fsck is located in /system/bin. I am also seeing a fsck.msdos, but no fsck.vfat.
I also remember seeing someone was compiling a BASH shell for Android. This would give you the tab completion that Busybox doesn't have.
Sent from my Nexus S using XDA App
yes there is bash in android , just type it, if you want bash with root privies the most reliable way to do that is su -c "bash"
also dont fsck in android that will get you bad results just look at what happened in a1, better way to that is using webos either using tailor in preware which is a nice front end that unmounts and fscks your media partition or install xecutah and using the command line fsck it (remember to unmount first)
ps: path to the media partition is dev/store/media
sorrowstyr said:
Hello Android Devs,
I am a linux admin, looking to help out. Is there a good place to do a quick comparison of commands btw linux and android ? Or where various scripts / special android locations of files.
I have been typing into my touchpad's Terminal Emulator and getting pretty irritated with no tab completion. I think I am going to buy a bluetooth keyboard. The other issue I was hoping Devs could help me find is, where is the fsck.vfat ? or e2fsck -o vfat? I have been having heck of time trying to find this and other normal linux commands without locate or tab completion. man e2fsck (no man pages found lol).
My "sdcard" in dmesg says needs to fsck'd, and I would like to help out because I see forum posts here and rootkitz.forums about just deleting the partition lol.
Thanks for advice
SorrowsTyr
Click to expand...
Click to collapse
You should try this:
http://www.mediafire.com/file/g52q4...1.0-tenderloin-sdcard_check_fix_r4-signed.zip
It installs a fixed fsck_msdos ...
NOTE: This should be included in Alpha3.6, but until then ...
Hello all,
I have been trying to gain root on a Android 4.0.4 device and was able to, but I can't seem to keep system rw long term.
I run the following command
mount -o remount,rw /system
or
adb remount (from a PC)
the mount command will then show that system is in rw mode. However, if I attempt to copy any data into /system, the first file copy fails and the system then reports read only. To make things even more odd, commands like chmod on a file in /system work just fine.
It seems to me that there is something that detects something writing to /system, and then forces the mount back to ro.
Does anyone have any ideas about this? Is this a common technique manufactures use?
The closest thing I could find on XDA is a reference to Sony Xperia devices having a watchdog service that doesn't something like this, but this device is a Kenwood Head unit and not a Sony device.
Thanks!
chris.davis925 said:
Hello all,
I have been trying to gain root on a Android 4.0.4 device and was able to, but I can't seem to keep system rw long term.
I run the following command
mount -o remount,rw /system
or
adb remount (from a PC)
the mount command will then show that system is in rw mode. However, if I attempt to copy any data into /system, the first file copy fails and the system then reports read only. To make things even more odd, commands like chmod on a file in /system work just fine.
It seems to me that there is something that detects something writing to /system, and then forces the mount back to ro.
Does anyone have any ideas about this? Is this a common technique manufactures use?
The closest thing I could find on XDA is a reference to Sony Xperia devices having a watchdog service that doesn't something like this, but this device is a Kenwood Head unit and not a Sony device.
Thanks!
Click to expand...
Click to collapse
I would think that you might need to run a script to remount on boot perhaps, such as one along this idea http://www.3c71.com/android/?q=node/466. Like via init.d or if that isn't possible on this then maybe something like this could do it http://forum.xda-developers.com/showthread.php?t=2378274 ?
Just spit balling ideas.
Correct me if I am wrong, but it seems to me that I wouldn't be able to do those options since system doesn't actually stay rw?
Really depends on the phone. Sometimes you can slip a script in during boot that will keep the system open. Sometimes you need to have a special module too such as this: http://forum.xda-developers.com/showthread.php?t=2230341 Sometimes the kernel doesn't allow it. I would think on 4.0.4 it shouldn't be near as hard as some of the newer JB and KK things. What do you have?
It is the Kenwood DNN990HD running Android 4.0.4.
I will try and run the binary tool you linked.
Thanks!
After breaking the screen on my phone I spent the following months reading about how to extract data. It all comes down to enabling ADB debugging and having your computer authorised. Usually this can be done from recovery and you're good to go. However, if you have a broken phone that is fully stock, with ADB disabled and with no custom recovery support then your data is as good as bricked. Such was the case with me when I broke my rare Samsung G360G. However, my phone was supported by CF-AutoRoot by Chainfire, and this gave just the opening I needed to go full wide.
Prerequisites:
Your phone needs to be supported by CF-AutoRoot. Check on there and the new site linked for support of your phone. If it's not there then you will need to download a stock ROM and use the CF-AutoRoot site tool to generate a root package for you. But that is outside the scope of this tutorial. This procedure has only been tested on Samsung. Your phone should have a minimal working charge.
https://autoroot.chainfire.eu/
This tutorial is also based on Linux. It should be translatable to Windows and Cygwin. But for simplicity I'll just use the method I used on Linux. However, if using Odin like I do, you'll need Windows to finish it off.
Aside from this it assumes files in are named in a particular format with a certain file format.
Tutorial:
1. First you need to download a CF-AutoRoot package for your phone. Won't get far without it.
2. Open up a terminal in Linux. We need to download some depends so enter this command:
Code:
sudo apt-get install android-tools-adb android-tools-fsutils
3. We need to extract the archive contents out. Create a suitable folder inside your home folder to build the patch in and cd to it. This uses an example file named CF-AutoRoot-example.tar.md5. Substitute with your actual archive name. Like so.
Code:
mkdir cfar-adb
cd cfar-adb
tar -xf CF-AutoRoot-example.tar.md5
4. There should be a recovery.img and a cache.img.ext4 extracted out. We just need to modify the cache.img.ext4. But first we need to convert it to a workable format. From a sparse to a raw image.
Code:
simg2img cache.img.ext4 cache.raw.ext4
5. We need to mount the cache image
Code:
mkdir cache
sudo mount -t ext4 -o loop cache.raw.ext4 cache
6. The big one. Doing the mod. So now we need to modify the cfar cleanup script. We need to insert commands on the end to enable ADB and add the key to authorise the computer. The following will do just that in this fashion.
a)
You will need to load in the cfar-cleanup.sh file inside the cfroot folder from the cache point mounted. Locate the end and paste the following lines before the reboot and exit commands on the end. Don't save yet.
Code:
echo -n 'mtp,adb' > /data/property/persist.sys.usb.config
mount -o remount,rw /system
echo '' >> /system/build.prop
echo 'persist.service.adb.enable=1' >> /system/build.prop
echo 'persist.service.debuggable=1' >> /system/build.prop
echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop
chmod 644 /system/build.prop
mount -o remount,ro /system
mkdir -p /data/misc/adb/
echo '' >/data/misc/adb/adb_keys
chmod 640 /data/misc/adb/adb_keys
b)
Load up the ~/.android/adbkey.pub file in a text editor and copy the entire contents in the clipboard. Now back at the script locate that last echo command you pasted into it and set the cursor just after the first single quotation mark. Now paste the clipboard in! This will add your key in. Make sure it's only between the single quotes with no extra characters or line feeds. The lines will naturally split if they don't fit on screen. Otherwise it should be good to go.
c)
Okay now save the file. The above will enable ADB and authorise your computer on the main Android system after the rooting script has done it's work. Before it reboots normally.
7. We need to unmount the cache so it's ready for use.
Code:
sudo umount cache
8. We need to convert the raw image back into a sparse image.
Code:
img2simg cache.raw.ext4 cache.img.ext4
9. Okay were almost done. Now we repack the files into a new Odin archive. Choose a suitable new filename. Like I have done here with my example file.
Code:
tar -H ustar -c recovery.img cache.img.ext4 > cfar-adb.tar
md5sum -t cfar-adb.tar >> cfar-adb.tar
mv cfar-adb.tar cfar-adb.tar.md5
10. The final step! So now the new package is ready for use. We just to use Odin and flash it to the phone. Save the package to a USB stick if needed.
a)
Reboot into Windows. Or you can run it virtualised from Linux. But I prefer to use the real things when dealing with things of a delicate manner and working blindly. Unplug your phone from the computer if connected. Now load up Odin in admin mode.
b)
Just to make sure pull the battery from your phone. Give it a few seconds then put the battery back in and click the back cover on. Now hold down volume down, then home key, and finally hold down power. Wait for the vibration. Then release power after a few moments. Finally release the other keys. At this point press volume up briefly. You should have just put your phone blindly into download mode. I've done this numerous times.
c)
Plug your phone into your computer. After a moment you should see Odin respond with a device added. Usually the phone can vibrate also when it connects giving more positive signs. If nothing happens disconnect the phone from the computer and retry the last step again to put it into download mode. Took me a few tries before I could do it blindly. It helps if you have a working Samsung to test it out on so you can see what happens before you can only feel it.
d)
Now in Odin press the PDA (or AP) button. Select the cfar-adb.tar.md5 package you made up. If the package is fine it will pass the md5 test. Now press the Start button and watch it go! If all goes well it will upload recovery, cache, give you a pass and then the phone will reset. At this point it will be in the process of being rooted, enable ADB, then reboot. If something goes wrong then you may need to go back and check all the patched files. Then rebuild the package again. But be careful, if the ADB has been enabled in the build.prop file one time, you don't want to add it in again and create duplicates, no matter how keen. Once I had it added the only other major problem I encountered was using the correct adb key.
e)
Hopefully now your phone is rooted, has ADB enabled and is booting up normally. Give it a few minutes. You can even see signs of life in Odin with adds and removes on USB activity. Your phone should also vibrate at times. And making noises is also a good sign.
1.1. So I just cranked it up to eleven. Open a Linux terminal again and give it a test. With your phone plugged in.
Code:
adb devices
If all goes well then adb will find your phone as well as list your device as authorised. You can now open shell to the inside. USB debugging is now enabled.
Conclusion:
Well I hope this helps those who have their app data stuck under a broken screen. As long as it was to type in this tutorial It still took me less time to write this tutorial than to learn all that was needed and apply it to my phone. This ends here but for you it may be only the beginning. A next step would be a screen mirroring app which I think is a must have for visual feedback. And USB debugging opens up these possibilities. One thing to be careful of, in a related issue, is that just because you can use adb and the phone is also rooted doesn't mean it will all work at once. If you are tempted to "su" it in an adb shell and get right in there then SuperSU will ask for permission on a blank screen. As will also happen if you try to do an adb backup, it will ask for confirmation on screen. So just expect to work with USB debugging blindly unless you already have a screen mirroring app installed. If you don't have one installed that is your next step.
And on that note. Good luck!
Hi there,
Your tutorial on how to achieve this on Linux looks real neat and complete. Unfortunately, i'm on Windows and i would like to know if you would be able to rewrite this totorial for a Windows user?
I've been reading online for about a week and i've never saw such a complete guide to help newbies to ADB to be able to retrieve data on their locked broken devices.
Cheers!
Hi RaiM1986 and thanks for your kind words. Yes I wrote it so it would be useful to newbies and seasoned hackers alike. Plus I needed to write down some instructions in case I need to do it all again.
Looking at the tutorial it is a bit Linux-centric. I don't know how well it would translate to Windows. Though there would be Windows version of the tools used the main problem would be mounting the filesystem image and making modifications without corrupting it. Because of things like Linux file modes.
However the following tools may be of assistance.
ADB tools:
https://wiki.lineageos.org/adb_fastboot_guide.html
Cygwin provides Linux tools if needed:
http://www.cygwin.com
simg2img:
https://github.com/KinglyWayne/simg2img_win
For mounting the ext4 image:
https://www.osforensics.com/tools/mount-disk-images.html
img2simg and other tools:
https://forum.xda-developers.com/showpost.php?p=49235638&postcount=5
For the ADB key it should be in %USERPOFILE%\.android and other spots I've read of are C:\Windows\System32\config\systemprofile\.android
In case any of the above fails, since I haven't tested them, the easiest alternative might be to just download a Linux live CD, boot it and do the steps inside. Of course any work is lost when you shut it down. You could also boot it in VM program running on Windows.
Amazing guide, Hypexed! The amount of work you put in to figure this out is incredible.
However, I'm stuck on step 6c, where I'm supposed to save the cfar-cleanup.sh file. It's not letting me save it at all, either within the mount point or to another location, it says that I don't have permissions to save the file. I tried the 'sudo chown' to change ownership to try to edit the permissions, but that didn't work either with it still saying I can't have access to the file. Any ideas? There is probably a simple solution, but this is my first time really using Linux so I'm a noob. I'm using Ubuntu 18.04.1LTS installed, not live, dual-booted with Windows, if that's important to know
SpinningQyarks said:
Amazing guide, Hypexed! The amount of work you put in to figure this out is incredible.
Click to expand...
Click to collapse
Thank you for noticing. It really was the culmination of months of hacking and cracking. Not to mention research. I decided I had to write a guide so I could document what I did in case I needed to do it again. And of course if it helped anyone else.
However, I'm stuck on step 6c, where I'm supposed to save the cfar-cleanup.sh file. It's not letting me save it at all, either within the mount point or to another location, it says that I don't have permissions to save the file. I tried the 'sudo chown' to change ownership to try to edit the permissions, but that didn't work either with it still saying I can't have access to the file. Any ideas? There is probably a simple solution, but this is my first time really using Linux so I'm a noob. I'm using Ubuntu 18.04.1LTS installed, not live, dual-booted with Windows, if that's important to know
Click to expand...
Click to collapse
Sorry you got stuck. I can see some issues in my guide. Especially after trying to do 6c again. First I notice I didn't specify where to store all the folders. Somewhere in the home folder obviously but it looks like you sorted that out fine.
I have tested a working solution to the permissions problem. In fact two:
1. Locate cf folder in the cache mount point on the desktop and go into it. Now right click in the window to bring up the context menu and select "Open as Root". Open up the editor as before.
2.. In the terminal run the editor as root. For example:
sudo gedit cfar-cleanup.sh
I've tested this on Mint which is a "relation" of Ubuntu so should work the same.
Now the original permissions should be left intact. I checked and they didn't have the execute bit set which is unusual. It may help here to save your work on the file to a place you can save to in the meantime. So you don't get stuck again. And then unmount your cache mount point, extract the raw image again as per step 4 and remount as per step 5, if the permissions need restoring. They really should be as they are originally set in the image.
Then continue through to step 6 and beyond as you were.
Good luck!