Hi guys I've tried everything but I am not able to achieve it. So I will explain step by step what I've tried pleas help me for gods sake.
- I want to pull my clockworkmod backups from /data/media/clockworkmod/backup/ (in the root - not the emulated sd card)
1)
C:\Android SDK\platform-tools>adb pull /data/media/clockworkmod/backup /backup
remote object '/data/media/clockworkmod/backup' does not exist - - Stange. The directory is this one i've checked with root explorer
C:\Android SDK\platform-tools>adb pull /charger /charger
failed to copy '/charger' to '/charger': Permission denied This is a random file in the root and it finds it this time - even stranger but I have no Permissions so I try to fix that.
2) to fix permissions I've tried this:
>> adb shell
>> su
>> mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
and after that trough shell:
>>adb pull /data/clockworkmod/backup -> and I get device not found
If I exit to adb again the same from point 1) happens
With this still the same as 1)
adb> adb shell su mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Any ideas? I am curious from technical point of view and I want to achieve it also. Please don''t recommend alternatives like copy ot SD card and then to PC. I wanna achieve this one
Let's start simple. Does your device show up if you adb devices?
Sent from my Nexus 5
jd1639 said:
Let's start simple. Does your device show up if you adb devices?
Sent from my Nexus 5
Click to expand...
Click to collapse
Yes I don't have problems with ADB/Fastboot it I can use them, the problem is only with the mounting/accessing the system partition.
Well the device doesnt show up when in shell:
Code:
C:\Android SDK\platform-tools>adb devices
List of devices attached
024e02[I]XXXXXX[/I] device
C:\Android SDK\platform-tools>adb shell
[email protected]:/ $ adb devices
adb devices
List of devices attached
[email protected]:/ $ su
su
[email protected]:/ # adb devices
adb devices
List of devices attached
[email protected]:/ #
Don't worry about the shell. I think the problem is cwm doesn't use the file structure correctly. It's actually in some weird place which I don't remember. Even though you see it in root explorer, or whatever you're using.
In your charger example,I believe charger is a file and not a directory. Adb is trying to pull a directory called charger which doesn't exist.
I'll look around a little to see if I can find where cwm stores the backups
Sent from my Nexus 5
---------- Post added at 03:09 PM ---------- Previous post was at 02:56 PM ----------
jd1639 said:
Don't worry about the shell. I think the problem is cwm doesn't use the file structure correctly. It's actually in some weird place which I don't remember. Even though you see it in root explorer, or whatever you're using.
In your charger example,I believe charger is a file and not a directory. Adb is trying to pull a directory called charger which doesn't exist.
I'll look around a little to see if I can find where cwm stores the backups
Sent from my Nexus 5
Click to expand...
Click to collapse
Now you really got me curious. I use twrp but put cwm on and made a backup. I'm getting the same error you are trying to pull the backup. It's not finding the directories. It finds them up to the point I add clockworkmod, i.e. pull /data/media works, /data/media/clockworkmod says it doesn't exist
Sent from my Nexus 5
Have you tried pulling the backup from /mnt/shell/emulated/clockworkmod/backup ??
In my device cwm always stores the backups there.
Sent from my Nexus 4 using xda app-developers app
Morbe said:
Have you tried pulling the backup from /mnt/shell/emulated/clockworkmod/backup ??
In my device cwm always stores the backups there.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I couldn't remember where cwm stored them. Thanks for that info.
Sent from my Nexus 5
You're welcome, if you can't find the cwm backups you can check rom manager app. Under "backup current ROM" on main menu it should show the backup path.
Sent from my Nexus 4 using xda app-developers app
Related
I need to uninstall swype and reinstall it. Ive tried over writing it with the default apk but its not removing a theme I installed with metamorph. If I can uninstall it, a fresh install should fix it.
I just dont know how to remove it
I don't know if you want to go to this extreme, but I did. I fudged up the phone real good by removing and installing stuff. I finally got fed up and flashed it back to stock and applied root again. This time I'll keep my fingers out of it. I hated touchwiz in the beginning, but now it's kinda growing on me. I've never had an iphone but the home and drawer remind me of iphone wannabe. It's okay for now.
Sent from my SPH-D700 using XDA App
There a tool over at sdx-developers that can remove that when root explorer can't. I forget the name of it. There's also a pay app in the market that I think is called root manager that can successfully remove crap too. I didn't have much luck putting the general swype 1.61 in. It refused to install. That's when I think I just flashed it back to factory image. A full reset/wipe wouldn't fix it either.
Sent from my SPH-D700 using XDA App
I had to do this a few days ago for similar reasons. This is what I did:
First, you have to open your browser or other app with a text field. Select the text field then long press the text field again and switch the input method to the stock android kb.
Next, you have to make sure /system is mounted as r/w. The early versions of the the rooting scripts did not remount correctly but the newer ones supposedly fix it. I just looked in the initial rooting .bat file (on the PC) for the remount command and used adb to remount /system.
You can test if it's remounted correctly by renaming Swype.apk to Swype.bak with Root Explorer then going up a level and back to /system/app. If it's not mounted correctly it will show as Swype.apk again. If it shows as Swype.bak still, then you just have to copy the original Swype.apk to /system/app and then switch input method back to Swype!
Sent from my Epic 4G using XDA App
yea its mounting in r-r, thats def my problem, cant change swype.apk with root explorer
so i need to re-root?
I don't know what's causing it but root explorer doesn't seem to work properly on the phone (not sdcard) filesystem in the system app folder. It's stuck in rw mode. People have said different things why but I forgot. I did noobnl's latest flash and it's still not working right. His script is removing the old root and my phone doesn't have that on there. I don't know what to tell ya. Maybe I should look for another root file manager.
kennethlongshaw said:
yea its mounting in r-r, thats def my problem, cant change swype.apk with root explorer
so i need to re-root?
Click to expand...
Click to collapse
I don't know if re-rooting will fix it or not. You could try. Here's the exact steps I took using adb from the PC:
Code:
adb shell
su
ls /system/app/S* (just shows Swype.apk is in fact in /system/app)
mount -t rfs -o remount,rw /dev/block/stl9 /system
mv /system/app/Swype.apk /system/app/Swype.bak
ls /system/app/S* (just to confirm Swype.apk is now Swype.bak)
cp /sdcard/download/Swype.apk /system/app/Swype.apk (or replace first argument with path of the good Swype.apk on your phone)
ls /system/app/S* (just to confirm Swype.apk and Swype.bak are both there)
reboot (reboots the phone, dunno if its really necessary)
dwyw42 said:
I don't know if re-rooting will fix it or not. You could try. Here's the exact steps I took using adb from the PC:
Code:
adb shell
su
ls /system/app/S* (just shows Swype.apk is in fact in /system/app)
mount -t rfs -o remount,rw /dev/block/stl9 /system
mv /system/app/Swype.apk /system/app/Swype.bak
ls /system/app/S* (just to confirm Swype.apk is now Swype.bak)
cp /sdcard/download/Swype.apk /system/app/Swype.apk (or replace first argument with path of the good Swype.apk on your phone)
ls /system/app/S* (just to confirm Swype.apk and Swype.bak are both there)
reboot (reboots the phone, dunno if its really necessary)
Click to expand...
Click to collapse
mmmm. That fixed. it. I owe you a beer
kennethlongshaw said:
mmmm. That fixed. it. I owe you a beer
Click to expand...
Click to collapse
Hi guyz.
I cant delete swype.apt file from /system/app/*
i am using SUFBS program (reed/write option enabled)
i tried use command in terminal:
Code:
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
but i get only;
Code:
permission denied
z4root show info that my phone is rooted
PDA i5800XXJI2
any ideas how to del that file? :]
Sorry if this has been mentioned before (I did search before posting), but there are a few widgets from the other Galaxy S phones that are rather nice, the weather clock in particular. I know there is a Fascinate dump out there, but can I just extract the apk and install it, or is there something else that I need to do. Any help is appreciated.
Sent from my SAMSUNG-SGH-I897 using XDA App
I would like to know this as well. Have subscribed to this thread.
Sent from my SAMSUNG-SGH-I897 using XDA App
Download the firmware that has those widgets and pull the apks and install them on your firmware of choice
If anyone does this post it please, if you link a how to ill do it.
Well, i pulled the APK's out of the ROM, but I'm not able to install them. I'm really new at this, so forgive me for the ignorance. there are ODEX files that accompany the apks...do i have to do something with those on order to install the widgets?
you'll need to use adb shell once you copy the files to a location on your internal sd card
you'll need to mount system as r/w first so do this, so:
adb shell
su (your device needs to be awake and unlocked so you can verify the SU request)
mount -o remount rw /system
cp /sdcard/xxxx.odex /system/app
cp /sdcard/xxxx.apk /system/app
reboot
the reboot is just for good measure. i've used this technique to get apps onto the phone, but as usual YMMV. If you post up the apk and odex files as a zip i'll give them a shot.
uiskibum said:
you'll need to use adb shell once you copy the files to a location on your internal sd card
you'll need to mount system as r/w first so do this, so:
adb shell
su (your device needs to be awake and unlocked so you can verify the SU request)
mount -o remount rw /system
cp /sdcard/xxxx.odex /system/app
cp /sdcard/xxxx.apk /system/app
reboot
the reboot is just for good measure. i've used this technique to get apps onto the phone, but as usual YMMV. If you post up the apk and odex files as a zip i'll give them a shot.
Click to expand...
Click to collapse
Do you have o remount /system as read only or will the reboot do that?
alphadog00 said:
Do you have o remount /system as read only or will the reboot do that?
Click to expand...
Click to collapse
the reboot will do that
What kind of cool stuff do they have?
Do tell!!
I had asked about putting the Samsung Touchwiz widgets on if using Launcher Pro. Was told no.
Would this method allow that for them?
Well, I've uploaded the files to Rapidshare, but thanks to the restrictions on my noob account, I can't link to the files.
rapidshare files 421816817 Samsung_Fascinate_Widgets zip
OK, major problem.
I copied the ODEX and APK's to the System/App folder and rebooted...now my phone will get stuck at the "Galaxy S" logo page and the display stops working. connecting via USB to the computer allows me to access the system via ADB, but I can't get the display running. What's the command in ADB to remove the files I just copied over?
adb shell
su
mount -o rw,remount /dev/block/st19 /system
rm /system/app/[name of widget file].*
Sgt_Bilbo said:
OK, major problem.
I copied the ODEX and APK's to the System/App folder and rebooted...now my phone will get stuck at the "Galaxy S" logo page and the display stops working. connecting via USB to the computer allows me to access the system via ADB, but I can't get the display running. What's the command in ADB to remove the files I just copied over?
Click to expand...
Click to collapse
Thanks for that info. Phone is back to normal. Now, back to the topic at hand. Anyone had success at getting these widgets working on the Captivate?
Sent from my SAMSUNG-SGH-I897 using XDA App
Hello, I rooted with unrevoked and then flashed the rom liberated_aria_FR006_signed.
I booted through clockwork and mounted /system /data /sdcard and then connected to my pc via usb, through the command prompt and adb I tried:
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
when I do rm /system/etc/hosts it says:
rm: can't remove '/system/etc/hosts': Directory not empty
What's wrong? Is /system not full perms through clockwork or is it a unrevoked root problem.
Thanks!
G226 said:
Hello, I rooted with unrevoked and then flashed the rom liberated_aria_FR006_signed.
I booted through clockwork and mounted /system /data /sdcard and then connected to my pc via usb, through the command prompt and adb I tried:
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
when I do rm /system/etc/hosts it says:
rm: can't remove '/system/etc/hosts': Directory not empty
What's wrong? Is /system not full perms through clockwork or is it a unrevoked root problem.
Thanks!
Click to expand...
Click to collapse
Lol...the error tells you exactly what's wrong...but kinda weird since the hosts is a file not a directory...so I can only assume that there are some permission issues...navigate to the /system/etc directory and do a "ls -al" and see what the permissions are for the hosts file...it'll be on the left side of the results of the ls.
Sent From My HTC Aria Using XDA App
Oh fyi...I'm dumb...are you already rooted? I dunno much about adb but you MIGHT have to run the above command through a terminal program on your phone...
Sent From My HTC Aria Using XDA App
I'm rooted but it's through unrevoked as mentioned, does that give me the proper permissions if I adb through clockwork recovery?
If not what would? I'll do a "ls -al" in a little.
G226 said:
I'm rooted but it's through unrevoked as mentioned, does that give me the proper permissions if I adb through clockwork recovery?
If not what would? I'll do a "ls -al" in a little.
Click to expand...
Click to collapse
I'm not sure...as I said im not too familiar with adb...I do know if you have a terminal program on your phone just open it, type the following:
su
cd /system/etc
ls -al
Once you so the ls, if you aren't familiar with *nix, you'll see the following:
-rw-r--r-- 1 root root 25 Aug 1 2008 hosts
Along with a bunch of other lines similar to this, this is the line I'd like to see though
Sent From My HTC Aria Using XDA App
Thanks for the help so far, I did what you said and after doing "ls -al" it said :
-al: No such file or directory
If I do a plain "ls" command it'll list all the files/folders in the system dir.
G226 said:
Thanks for the help so far, I did what you said and after doing "ls -al" it said :
-al: No such file or directory
If I do a plain "ls" command it'll list all the files/folders in the system dir.
Click to expand...
Click to collapse
1 are you doing this in adb or terminal?
2 are you typing "ls -al" with a space? And "al" as in alpha lima?
3 are you in the etc directory?
Sent From My HTC Aria Using XDA App
I did as you instructed, used the terminal program app and tried these commands through there, I'll try adb.
Thanks.
Well the only reason I asked was because ls -al is a legit command lol...I dunno of another way to view the permissions of files...I also don't know if there is a way or not through adb, Google may be your friend in regards to that...
Sent From My HTC Aria Using XDA App
This may be related to busybox on the phone. Can you do an "echo $PATH" from the adb shell and paste the results here?
So from the command prompt you would enter "adb shell" this should give you a new prompt like this #. At this prompt type "echo $PATH" without the quotes. Maybe you do not need all these instructions, sorry.
I see this all the time, from all the noobs (myself included)
First off the ARIA still has S-ON security, so if you are writing to /system/ you _NEED_ to be properly booted into recovery - otherwise you will not have write permissions. its in the FAQ but still completely overlooked. There is a post about this every day i swear.
STEP 1) UNPLUG THE USB <----- CRITICAL
STEP 2) POWER DOWN THE PHONE <----- AFTER STEP 1!!!!!!
STEP 3) HOLD VOLUME DOWN + PRESS POWER to load hboot
STEP 4) SELECT recovery to start clockwork
STEP 5) partitions --> mount --> /system/
STEP 6) connect USB
STEP 7) adb shell
edit: if you shortcut into recovery by just leaving the USB plugged in while you power down - you will not have full permissions.
dexmix said:
I see this all the time, from all the noobs (myself included)
First off the ARIA still has S-ON security, so if you are writing to /system/ you _NEED_ to be properly booted into recovery - otherwise you will not have write permissions. its in the FAQ but still completely overlooked. There is a post about this every day i swear.
STEP 1) UNPLUG THE USB <----- CRITICAL
STEP 2) POWER DOWN THE PHONE <----- AFTER STEP 1!!!!!!
STEP 3) HOLD VOLUME DOWN + PRESS POWER to load hboot
STEP 4) SELECT recovery to start clockwork
STEP 5) partitions --> mount --> /system/
STEP 6) connect USB
STEP 7) adb shell
edit: if you shortcut into recovery by just leaving the USB plugged in while you power down - you will not have full permissions.
Click to expand...
Click to collapse
3 sleepless nights later and dexmix comes to the rescue. This drove me crazy man, I just could not find the answer. Thanks!! Bed time!
Hope this is the right place to post this.
My Atrix is rooted stock 1.83 .
I'm trying to "adb push" some OGG files to "/system/media/audio/" to add-to and replace some of the existing system sounds, especially that bloody annoying keypress (typewriter) sound, but I'm getting the following error (which makes sense):
Read-only file system
Tried using Root Explorer, same issue...again makes sense since its mounted as Read only on boot.
I tried booting into recovery mode, but I can't access the phone via ADB at all, even with USB Debug enabled. I also tried "adb remount" command, no luck either. I get an error "operation not permitted".
So, does anyone know the correct sequence of commands I need in ADB to remount the Atrix /system folder as RW??
What I have been doing is using adb push to the /sdcard then using adb shell then su then
mount -t rfs -o remount,rw /dev/stl5 /system
Then cp /sdcard/whatever /system/media
Sent from my MB860 using XDA App
EDIT: im at my computer now so I can write this easier to understand, lol
Lets say the file you want to change is called whatever.ogg
Code:
adb push whatever.ogg /sdcard/whatever.ogg
adb shell
su
mount -t rfs -o remount,rw /dev/stl5 /system
cp /sdcard/whatever.ogg /system/media/audio/notifications
when you access root explorer, does it let you know that it has been granted supervisor privilages? Does it give you the option to change from read to write? what did you use to root? I had to run the original Aroot three times before if finally gave me root.
You're the best, worked perfectly Can't believe that hideous typewriter sound is gone, it only took me 1.5 years as an Android user to finaly say enough is enough. Whomever thought it was a good idea to mimic the sound of an 1800's typewriter on a 21st century device needs to be fired.
Thanks again.
aver2one said:
What I have been doing is using adb push to the /sdcard then using adb shell then su then
mount -t rfs -o remount,rw /dev/stl5 /system
Then cp /sdcard/whatever /system/media
Sent from my MB860 using XDA App
EDIT: im at my computer now so I can write this easier to understand, lol
Lets say the file you want to change is called whatever.ogg
Code:
adb push whatever.ogg /sdcard/whatever.ogg
adb shell
su
mount -t rfs -o remount,rw /dev/stl5 /system
cp /sdcard/whatever.ogg /system/media/audio/notifications
Click to expand...
Click to collapse
i need help
im using a clone samsung galaxy tab2.tried to change the system font with root browser and it bricked.the phone dont have cwm so i didnt back up my rom.any command in adb that can be used to change the font folder
Obiechina said:
im using a clone samsung galaxy tab2.tried to change the system font with root browser and it bricked.the phone dont have cwm so i didnt back up my rom.any command in adb that can be used to change the font folder
Click to expand...
Click to collapse
Well congrats! that was the dumbest thing ever. NEVER attempt something like that unless you have CWM or equivalent installed, have a backup, and know what you are doing.
Have you tried to read your device's xda forum?
Please Help
Hahaha, can you help me?
i want to change my /system/framework folder by using the POWER and UP volume keys
i had a backup of my system/framework in my SD..
What should i do?
I'm out of ideas. I've asked before but got no where. I figured a picture may help. I can root and get all the way to cm 7.0.3 but anything 1.2 update related fails. I've tried using the cwm flashable update but that fails too.
The pic is from a fresh 1.0. (I've tried 1.1 also.)
Sent from my DROIDX using XDA Premium App
USE THIS http://forum.xda-developers.com/showthread.php?t=1000957 with a sandisk 8 gb class 4 chip.....
Call it a day.... use CM7.1 RC, its very stable.... if you need to update to nightlies, its simple as just copy the downloaded file onto the external memory card.
Yeah that is a last resort. I plan on giving that nook to my brother who is android illiterate. How did everything get borked anyway?
I bypassed the registration and my nook info looks like this
Sent from my DROIDX using XDA Premium App
OH CRAP.... looks like some sort of internal corruption....
Do a complete wipe......
THEN Do the SDCard install...
It's seemless to the user... THere is no bootup screen or anything... The nook will automatically boot to the sd first.... so he won't need to know anything...
if he is REALLY not too literate, then he can just pull the sd, and it boots into the nook.
Ok....I'm not sure what kind of SD card I have... it just says micro SD hc 4gb with a circle with a 4 in it.
So I'm assuming its a class 4 SD card...not sure the brand though
Sent from my DROIDX using XDA Premium App
oman0123 said:
Ok....I'm not sure what kind of SD card I have... it just says micro SD hc 4gb with a circle with a 4 in it.
So I'm assuming its a class 4 SD card...not sure the brand though
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
It will work fine..... class 4 is good enough
Also if anybody knows a fix for whatever happened I would much rather do that than running off of sd
Also Thanks for the help slider. At least I know he will at least have the current cm if I can't find a fix
Sent from my DROIDX using XDA Premium App
oman0123 said:
Also if anybody knows a fix for whatever happened I would much rather do that than running off of sd
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
Did you try to wipe it? under settings?
slider2828 said:
Did you try to wipe it? under settings?
Click to expand...
Click to collapse
Yup wont let me. Says: deregister device failed with error: user not registered (E_NOT_REGISTERED)
Sent from my DROIDX using XDA Premium App
Looks like your "ROM" got corrupted... it is a partition (/dev/mmcblk0p2) that is mounted r/w as /rom
Check and see if you have partition mmcblk0p3 and if rombackup.zip is in there...
Boot off CWM bootable uSD... then try the following:
adb shell mkdir /tmp
adb shell mount /dev/block/mmcblk0p3 /tmp
adb shell ls /tmp
if rombackup.zip is there... you're fine... we can fix it.
Wow I've been rooting for about 3 years and have never ever used adb. Crazy right? Can anybody point me in the right direction ?
Sent from my DROIDX using XDA Premium App
can that be done in terminal emulator or do I gotta go and install adb and whatever else on my computer?
term emulator would work.
DizzyDen said:
Looks like your "ROM" got corrupted... it is a partition (/dev/mmcblk0p2) that is mounted r/w as /rom
Check and see if you have partition mmcblk0p3 and if rombackup.zip is in there...
Boot off CWM bootable uSD... then try the following:
adb shell mkdir /tmp
adb shell mount /dev/block/mmcblk0p3 /tmp
adb shell ls /tmp
if rombackup.zip is there... you're fine... we can fix it.
Click to expand...
Click to collapse
Ok I tried adb shell mkdir /tmp and i get mkdir: cant create directory /tmp: read only file system.
Tried adb shell mount /dev/block/mmcblk0p3 /tmp, it fails and says no such file or directory.
does this mean if I want the newest versions of cm7 I gotta do it off sd?
Arrrgh been trying all night. I hope there's still a way and its not completely borked
Sent from my DROIDX using XDA Premium App
oman0123 said:
Ok I tried adb shell mkdir /tmp and i get mkdir: cant create directory /tmp: read only file system.
Tried adb shell mount /dev/block/mmcblk0p3 /tmp, it fails and says no such file or directory.
does this mean if I want the newest versions of cm7 I gotta do it off sd?
Click to expand...
Click to collapse
You could still run CM7 off of EMMC... we're just trying to salvage your device specific information if there's any hope... which I truly think there is.
oman0123 said:
Arrrgh been trying all night. I hope there's still a way and its not completely borked
Click to expand...
Click to collapse
Sorry... was at work... didn't have a chance to reply...
try adb remount
before the other steps above... if you get an error then you will need to
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
One of those two should work from CWM bootable uSD... then the steps I listed above will work... IF you have the rombackup.zip file... we'll help you through fixing your issues.
DizzyDen said:
You could still run CM7 off of EMMC... we're just trying to salvage your device specific information if there's any hope... which I truly think there is.
Sorry... was at work... didn't have a chance to reply...
try adb remount
before the other steps above... if you get an error then you will need to
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
One of those two should work from CWM bootable uSD... then the steps I listed above will work... IF you have the rombackup.zip file... we'll help you through fixing your issues.
Click to expand...
Click to collapse
I got the same error messages after the remount but the "adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system" seemed liked it work. it didnt say anything though
It won't give you a message saying it was successful... just try the other commands to see if you have backuprom.zip on partition 3. If its there... we can fix the issues... if not.. we have to make stuff up to fix it
You can do the same thing for partition 2 (where the device specific stuff is stored unzipped) by creating directory called tmp2 and mounting /dev/block/mmcblk0p2 to it... in that one 3 specific files you're looking for are:
DeviceID
MACAddress
SerialNumber
Those are plain text type files (but not DOS or windows formatted.. so you can view them, but don't edit them in notepad)
DizzyDen said:
It won't give you a message saying it was successful... just try the other commands to see if you have backuprom.zip on partition 3. If its there... we can fix the issues... if not.. we have to make stuff up to fix it
You can do the same thing for partition 2 (where the device specific stuff is stored unzipped) by creating directory called tmp2 and mounting /dev/block/mmcblk0p2 to it... in that one 3 specific files you're looking for are:
DeviceID
MACAddress
SerialNumber
Those are plain text type files (but not DOS or windows formatted.. so you can view them, but don't edit them in notepad)
Click to expand...
Click to collapse
Ok you are gonna have to help me with that. I wouldnt even know where to begin. We all gotta push our limits right? haha
Check your PM... give me a call if you want.
I gave you some bad commands.... this should work:
adb shell mount -O remount /remount, rw /dev/block/mmcblk0p5 /system
adb shell mkdir /system/tmp
adb shell mount /dev/block/mmcblk0p3 /system/tmp
adb shell ls -l /system/tmp
then
adb shell mkdir /system/tmp2
adb shell mount /dev/block/mmcblk0p2 /system/tmp2
adb shell ls -l /system/tmp2
OR
adb shell
mkdir /system/tmp
etc.
etc.
Since you have the rombackup.zip on mmcblk0p3 try this...
extract attached file... then run the resettofactory.cmd file... it will copy the BootCnt file to /rom and make it think its on 8th failed boot.