I'm in need of the stock kernal image and the clockwork recovery.zip file thingy.
NOT the zip verson of the kernal installer.
My situation, I was stupid and installed the voodoo thing, then for someone reason I tried to flash Froyo over Bionix with the voodoo kernal thing. It didnt work so I decided to deleted everything in clockwork. Then I was like omg I cant use clock work or boot my device (stuck on vibrant screen but I can get to odin and the stock recovery).
Later I read that voodoo stopped odin on the cm forum so I couldnt use it. Thats what some dude named viralblack said and theyre a mod so I'm guessing its true.
So my last 4 ideas are:
1)Try and flash a new Kernal Image in adb and hope it gets odin to work
2)Push the cw recovery to the phone
3)Run to the library and hope my computer is the problem
4)Pretend vb is wrong and keep trying the download screen thing
Sorry if this is in the wrong section but I guessed it could go here because I need some files....
flash Eugene's froyo that does not brick via Odin. he has instructions in his thread.
...and it's kernel NOT kernal people
Sent from my SGH-T959 using XDA App
kernel, sorry I guess?
Anyhow what if my pc doesnt notice the phone when its in download mode
RPGbig said:
kernel, sorry I guess?
Anyhow what if my pc doesnt notice the phone when its in download mode
Click to expand...
Click to collapse
Download the Samsung drivers, download ODIN, and then just follow the directions in the ODIN thread
Wow
You guys have nothing better to do than flame a newb?
If you spent half the time helping instead of flaming there MIGHT just be some people with a bit more knowledge than they had yesterday.
If you cant say something constructive/helpful --Why bother!
fcbarca17 said:
Download the Samsung drivers, download ODIN, and then just follow the directions in the ODIN thread
Click to expand...
Click to collapse
Push doesnt seem to work. Permission denied or something rather.
As I said in my first odin wont work, yes I did those things like 10 or so times.
You cant expect a newborn to know how to wipe themselves.
RPGbig said:
Push doesnt seem to work. Permission denied or something rather.
As I said in my first odin wont work, yes I did those things like 10 or so times.
You cant expect a newborn to know how to wipe themselves.
Click to expand...
Click to collapse
What do you mean "push doesn't work". Are you trying to push a file via adb? If you are getting permission denied errors, that is because you either do not have root access/permissions to write to the location you are trying to push to, or because the location you are trying to push to is mounted as read-only.
If you indeed have the necessary permissions (i.e., root), then `adb remount` will re-mount the device's partitions as read-write. If adb does not allow you remount the partitions in this manner, it is because you do not have the permissions to perform the duty.
If anyone is going to give any further help, though, you need to give us a bit more information. Can you access the device via adb? Can you boot into either download or recovery? (If you have adb access, you can usually boot into either of those with `adb shell reboot download` or `adb shell reboot recovery`.) Have you attempted to flash anything via Odin? What is the exact wording of the error messages you are receiving?
If you don't provide information, you won't receive any help. Vague responses such as "Permission denied or something rather" are useless because something rather can be any number of things. Also, attempting things without reading all of the information available beforehand is another way to ensure that people will be hesitant to give you help; this forum already has threads about where to locate the stock kernel image.
Also, instead of positing what-ifs such as "Anyhow what if my pc doesnt notice the phone when its in download mode", why don't you try putting your device into download mode and attaching it to a Windows computer with the proper drivers installed and Odin running, and then ask what the next step might be after you have attempted to do something?
People get angry about members flaming newbies for posting mistakes and asking for help, but if newbies looked for answers and read all of the information available before doing something they didn't understand (or only partially understood), then this wouldn't be a problem in the first place.
rpcameron said:
What do you mean "push doesn't work". Are you trying to push a file via adb? If you are getting permission denied errors, that is because you either do not have root access/permissions to write to the location you are trying to push to, or because the location you are trying to push to is mounted as read-only.
If you indeed have the necessary permissions (i.e., root), then `adb remount` will re-mount the device's partitions as read-write. If adb does not allow you remount the partitions in this manner, it is because you do not have the permissions to perform the duty.
Click to expand...
Click to collapse
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
I type 'adb remount' its says ' remount failed: No such file or directory
rpcameron said:
If anyone is going to give any further help, though, you need to give us a bit more information. Can you access the device via adb? Can you boot into either download or recovery? (If you have adb access, you can usually boot into either of those with `adb shell reboot download` or `adb shell reboot recovery`.) Have you attempted to flash anything via Odin? What is the exact wording of the error messages you are receiving?
Click to expand...
Click to collapse
Yes, I can get into both.
I've download Froyo that doesnt brick. Unziped and got had the drivers from sansumg set up.
I usually type 'adb reboot download' to get into download mode for odin. Then when the phone shows the android guy with the shovel. Then my computer says that an unrecognized usb device has been connect.
This time I type 'adb shell reboot recovery' and its said
'-exce `/system/bin/sh` failed: No such file or directory (2) -'
rpcameron said:
If you don't provide information, you won't receive any help. Vague responses such as "Permission denied or something rather" are useless because something rather can be any number of things. Also, attempting things without reading all of the information available beforehand is another way to ensure that people will be hesitant to give you help; this forum already has threads about where to locate the stock kernel image.
Also, instead of positing what-ifs such as "Anyhow what if my pc doesnt notice the phone when its in download mode", why don't you try putting your device into download mode and attaching it to a Windows computer with the proper drivers installed and Odin running, and then ask what the next step might be after you have attempted to do something?
People get angry about members flaming newbies for posting mistakes and asking for help, but if newbies looked for answers and read all of the information available before doing something they didn't understand (or only partially understood), then this wouldn't be a problem in the first place.
Click to expand...
Click to collapse
RPGbig said:
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
Click to expand...
Click to collapse
You have to be rooted.. But why would you even take the hard way to use clockwork? Just download it from the market..?
I have odin with all the files that will get u to stock of ur phone. Also the froyo files does not brick. So now i exactly dont know what u need. go cows
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
RPGbig said:
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
Click to expand...
Click to collapse
If your phone is stuck in a bootloop you need to flash your phone with odin
RPGbig said:
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
I type 'adb remount' its says ' remount failed: No such file or directory
Click to expand...
Click to collapse
OK, if `adb remount` isn't working properly, then you have to manually instruct the system to remount the system partition as read-write. This is a little different from other Android devices, because Samsung insists on using their screwy RFS. On my device, the system partition resides at /dev/block/st19. If you can get an adb shell session, opened, you can verify it by running `mount`, and seeing which /dev node is assigned to /system. Then, manually remount the system partition with `mount -o remount,rw -t rfs /dev/block/st19 /system`; this must be done as root.
It does seem a bit odd that you are getting a permission denied error on /sdcard. Are you sure that /sdcard is mounted? You can verify the same way you check what /dev node holds you system partition. On my Vibrant, /sdcard is the mount point for /dev/block//vold/179:1 (yes, that is two slashes after block). So, the command to mount the internal SD card is `mount -o remount,rw -t vfat /dev/block//vold/179:1 /sdcard`.
Now those commands should ensure that you have both your system partition and SD card mounted as read-write. Now you can copy over the update.zip that contains ClockworkMod recovery to the root of your SD card (/sdcard) with `adb push drive:\path\to\recovery.zip /sdcard/update.zip`. I recommend specifying a destination filename for update.zip. Also, sometimes an adb push command requires the trailing / of a directory.
RPGbig said:
Yes, I can get into both.
I've download Froyo that doesnt brick. Unziped and got had the drivers from sansumg set up.
I usually type 'adb reboot download' to get into download mode for odin. Then when the phone shows the android guy with the shovel. Then my computer says that an unrecognized usb device has been connect.
This time I type 'adb shell reboot recovery' and its said
'-exce `/system/bin/sh` failed: No such file or directory (2) -'
Click to expand...
Click to collapse
This last statement looks like either your system partition is not mounted, or that it does not have a shell installed. From an adb shell session, check the /system/bin directory and see if there is indeed a shell binary there (either sh itself, or sh linked to another shell such as bash). If there is no /system, then it means that your system partition is not mounted, and you can follow the steps I previously mentioned to mount the system partition.
RPGbig said:
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
Click to expand...
Click to collapse
Can you boot into recovery using the VOL_DN and POWER method, or does the adb daemon ever come online during the bootloop? If so, then either boot into recovery from a powered-off state, or use the adb shell to boot it into recovery.
http://forum.xda-developers.com/showthread.php?t=810130
rpcameron said:
OK, if `adb remount` isn't working properly, then you have to manually instruct the system to remount the system partition as read-write. This is a little different from other Android devices, because Samsung insists on using their screwy RFS. On my device, the system partition resides at /dev/block/st19. If you can get an adb shell session, opened, you can verify it by running `mount`, and seeing which /dev node is assigned to /system. Then, manually remount the system partition with `mount -o remount,rw -t rfs /dev/block/st19 /system`; this must be done as root.
It does seem a bit odd that you are getting a permission denied error on /sdcard. Are you sure that /sdcard is mounted? You can verify the same way you check what /dev node holds you system partition. On my Vibrant, /sdcard is the mount point for /dev/block//vold/179:1 (yes, that is two slashes after block). So, the command to mount the internal SD card is `mount -o remount,rw -t vfat /dev/block//vold/179:1 /sdcard`.
Now those commands should ensure that you have both your system partition and SD card mounted as read-write. Now you can copy over the update.zip that contains ClockworkMod recovery to the root of your SD card (/sdcard) with `adb push drive:\path\to\recovery.zip /sdcard/update.zip`. I recommend specifying a destination filename for update.zip. Also, sometimes an adb push command requires the trailing / of a directory.
This last statement looks like either your system partition is not mounted, or that it does not have a shell installed. From an adb shell session, check the /system/bin directory and see if there is indeed a shell binary there (either sh itself, or sh linked to another shell such as bash). If there is no /system, then it means that your system partition is not mounted, and you can follow the steps I previously mentioned to mount the system partition.
Click to expand...
Click to collapse
I tried 'adb root' and then it said 'adbd cannot run as root in production builds'
By shell session do you mean 'adb shell'? No, I dont believe that works because I get 'adbd cannot run as root in production builds'
When you mean 'shell installed' you do I have it installed on the phone? If it isnt is there anyway I could do it now?
`adb push drive:\path\to\recovery.zip /sdcard/update.zip` didnt work and gave me 'c:\update.zip' to '/sdcard/update.zip': Permission denied
Can I flash /system via my pc onto my phone? or Use the external sdcard instead of the internal?
Dude, if your phone is stuck in a bootloop, you HAVE TO FLASH IT VIA ODIN. There's no other work-around.
RPGbig said:
I tried 'adb root' and then it said 'adbd cannot run as root in production builds'
By shell session do you mean 'adb shell'? No, I dont believe that works because I get 'adbd cannot run as root in production builds'
When you mean 'shell installed' you do I have it installed on the phone? If it isnt is there anyway I could do it now?
`adb push drive:\path\to\recovery.zip /sdcard/update.zip` didnt work and gave me 'c:\update.zip' to '/sdcard/update.zip': Permission denied
Can I flash /system via my pc onto my phone? or Use the external sdcard instead of the internal?
Click to expand...
Click to collapse
Why did you try `adb root`? I don't quite understand that.
A shell session would be `adb shell`, yes. On your computer's command line, invoke `adb shell`. You are now in a shell session. What does the prompt look like? Is it "#" or "$". If it is a hash, then you have root access via adb. If it is a dollar sign, then you do not have root access; try running `su` from within the shell session. If the prompt does not change to a hash, then you are stuck for the moment, because you do not have root access via adb, and therefore nearly all of the adb commands will not work.
By "shell installed" I was referring to a shell interpreter installed on your handset. bash is the most commonly installed Linux shell, and sh is usually just a pointer to bash. If your handset does not have either /system/bin/sh or /system/bin/bash (or anything similar), then you have an incomplete system, and it got messed up along the way with something you did.
But, since it seems that you cannot gain root access through adb, and therefore cannot (re)mount your partitions, you are basically limited in your options. All you can really do is put your phone in download mode, and use Odin to reflash a complete system (including a kernel image). I would also recommend that you use the repartition option in Odin to make sure that your partitions are reformatted and you are essentially left with a wiped and clean handest to start with.
(Lack of root access via adb has severely limited your options. You are basically left with Odin as your only avenue of recourse, unless you are willing to disassemble your device to get to the internal SD card.)
Have you opened yours? Is it an actual (micro) sdcard that can be taken out like the external one?
I typed 'adb root because typing 'adb' showed this
adb root - restarts the adbd daemon with root permissions
so I guess that was what you ment by root.
When I type 'adb shell' all it gave was - exec '/system/bin/sh' failed: No such file or directory (2) -
You need to stop trying to do it the hard way and just use Odin. If your phone is not being recognized then you need the correct drivers. Once installed, you should be back up and running within 5 minutes. Stop lollygagging and fix your phone already.
Related
Let me first say that I have read every post I could find on this subject and tried them all with no success. I rooted my Aria using the Ubuntu Live CD so I could use Titanium backup and eventually try different roms. My phone is still using the stock rom. I then installed Titanium backup which reports "your system settings will prevent you from restoring applications. to correct this go to your phone's settings, then in "applications" and tick the "unknown sources" check box."
The unknown sources check box is of course not there because I have not been able to successfully run the code for allowing non-market apps.
From terminal in the Ubuntu Live CD with USB cable connected and set to charge only. I tried and got "remount failed: operation not permitted." at the adb remount step.
Linux Code:
sudo su
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo "update secure set value = 1 where name = 'install_non_market_apps';"|sqlite3 ./settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb reboot
I downloaded the android-sdk_r07 and extracted it to my C drive. From a Windows command prompt, I changed to the sdk\tools folder. Adb devices sees the phone but adb remount fails with "remount failed: operation not permitted."
Windows Code:
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
I found a post from attn1 that I have not tried that said:
"Put your phone in recovery mode. Go to advanced>mount system and mount data. Follow steps in post #13 (using the windows or linux code above) in cmd screen and you'll be fine." I am not comfortable in trying this approach as there are not enough specific step details and I don't want brick my phone.
I would really appreciate the correct detailed steps to enable non-market apps using the supplied code either from Windows or the Ubuntu Live CD. Thank you in advance.
You are rooted, so boot into recovery and create a nandroid backup; if something goes wrong when pushing settings.db and you cannot boot, restore your nandroid backup. Then, as attn1 stated, perform the same steps you mention above, but while the phone is in recovery and you have mounted the system and data folders.
winsettr said:
You are rooted, so boot into recovery and create a nandroid backup; if something goes wrong when pushing settings.db and you cannot boot, restore your nandroid backup. Then, as attn1 stated, perform the same steps you mention above, but while the phone is in recovery and you have mounted the system and data folders.
Click to expand...
Click to collapse
Thank you winsettr for your post. It looks like running the commands from recovery did indeed work. Titanium backup no longer reports the "your system settings will prevent you from restoring applications. To correct this go to your phone's settings, then in "applications" error.
However, I expected to see the settings\applications unknown sources check box check box and it is not there. I guess I will have to try side-loading an app to confirm that it will work.
I think that gui option would be part of the rom, a part that AT&T has removed... So yeah, see if side- loading works now.
Sent from my Liberty using XDA App
FYI, I am indeed able to side load now from an .apk copied to the sd card. However, I am not able to install from an internet link. Trying to do so generates a "your phone is not authorized" error message.
Until you get a custom rom running, I wouldn't worry too much. Sounds like you can get any app you want (just download internet apps to sd then install). There may be an additional setting in settings.db but that's beyond my knowledge...
Sent from my Liberty using XDA App
Hi, I've been trying to move all my game data from my internal SD card to my larger external SD card with no joy.
I have used condi's AIO tool to install init.d support, which reported as successful, but when I follow obicom's instructions as listed in POST #43 of this thread http://forum.xda-developers.com/showthread.php?t=1490116&page=5
I repeatedly receive the message "Operation not permitted."
I have used both ADB Shell and Terminal Emulator with the same result.
I'm obviously doing something wrong as other people appear to have had success with these instructions, I just don't know what.
Here's what I've done: (on rooted ICS from condi's AIO tool)
Installed init'd support "successfully"
Moved all data from sdcard/Android/data over to sdcard2/game_data
In ADB Shell/Terminal Emu. entered the following line;
mount -o bind /sdcard2/game_data /sdcard/Android/data
and this is where I get the "Operation not permitted" message.
Any ideas?
Once you're in shell, before running the mount command, run the command 'su' first (without the quotes). Your prompt should change from $ to # and try running the mount command again.
Explained: In most Linux systems, unless the fstab has been specifically setup to do it with the user option, filesystems can only be mounted by root. In rooted versions of Android, the normal user can elevate into a root prompt with su, then allowing you to mount and unmount any filesystems.
Ahaaa
Awesome! Can't believe it was something so simple, thanks, and thanks for explaining the reason.
I must have somehow totally missed the "su" instruction in the other thread.
Half of my games work, the other just seem to need re-installing which is no big drama.
Again, thanks, it's much appreciated mate.
Script?
agc93 said:
Once you're in shell, before running the mount command, run the command 'su' first (without the quotes). Your prompt should change from $ to # and try running the mount command again.
Explained: In most Linux systems, unless the fstab has been specifically setup to do it with the user option, filesystems can only be mounted by root. In rooted versions of Android, the normal user can elevate into a root prompt with su, then allowing you to mount and unmount any filesystems.
Click to expand...
Click to collapse
Hi, is there a way I can create a script (or the like) that would do this, and other similar directory changes, at boot?
At present I need to enter these manually each time the tablet starts, which isn't too much of a drama for me but when other people use it they end up downloading the data all over again when they start a game.
Thanks
There is an app available on Google Play called Script Manager (which can be used to create scripts to run at boot as su (which mount command require), which should do what you need. You'll need to use a plain text editor (I believe there is one included with Script Manager) to enter each of the mount command you want to run on a separate line. Then set the file to executable (chmod +x scriptname), and add it to Script Manager.
Note that I haven't used it in a while, so follow whatever instructions Script Manager gives you. They're probably more up to date.
agc93 said:
There is an app available on Google Play called Script Manager (which can be used to create scripts to run at boot as su (which mount command require), which should do what you need. You'll need to use a plain text editor (I believe there is one included with Script Manager) to enter each of the mount command you want to run on a separate line. Then set the file to executable (chmod +x scriptname), and add it to Script Manager.
Note that I haven't used it in a while, so follow whatever instructions Script Manager gives you. They're probably more up to date.
Click to expand...
Click to collapse
Okay thanks, yet again, I'll give it a try today.
Operation not permitted
Hi,i wanted to change my mac address on phone and even with that su command i get "operation not permitted" (my phone is rooted)...even apk named overclock for android could not grant root acces...in root checker my phone is rooted(and i have been rerooting it but still same).AND THERE IS NO FIX ON INTERNET
I've got a device and need either root or su for system app development, but want to do this in the least invasive way possbile. The twist... this is likely a pre-release device and came from HTC with S-OFF (HBOOT-1.01.0000).
With S-OFF (but no root) what are the options for getting root and/or SU installed?
pukebag said:
I've got a device and need either root or su for system app development, but want to do this in the least invasive way possbile. The twist... this is likely a pre-release device and came from HTC with S-OFF (HBOOT-1.01.0000).
With S-OFF (but no root) what are the options for getting root and/or SU installed?
Click to expand...
Click to collapse
Least invasive: Install superuser/su from adb, leaving stock recovery in place. LMGTFY: http://www.equisoforum.com/Thread-ADB-Shell-Pro-Root-method
Better route: Flash CWM or TWRP recovery to phone, then flash superuser/su package from recovery.
junkmail9 said:
Least invasive: Install superuser/su from adb, leaving stock recovery in place. LMGTFY: no_urls_from_noobs
Better route: Flash CWM or TWRP recovery to phone, then flash superuser/su package from recovery.
Click to expand...
Click to collapse
(please forgive if anything I have below is nonsense... I'm slowly building my understanding)
I don't believe the 1st method will work. I can't 'adb remount' because I don't have root on the device ('remount failed: Operation not permitted'). If remount worked I'd be good, because as you suggest I could push the su apk/permission/scripts to the device. I also tried remounting the /system partition as RW but no luck ('mount: Operation not permitted').
I'll try the 'traditional' CWM route. I just wasn't sure if having S-OFF opened up any other options for getting root, mounting /system as RW, or...
Thanks much.
pukebag said:
(please forgive if anything I have below is nonsense... I'm slowly building my understanding)
I don't believe the 1st method will work. I can't 'adb remount' because I don't have root on the device ('remount failed: Operation not permitted'). If remount worked I'd be good, because as you suggest I could push the su apk/permission/scripts to the device. I also tried remounting the /system partition as RW but no luck ('mount: Operation not permitted').
I'll try the 'traditional' CWM route. I just wasn't sure if having S-OFF opened up any other options for getting root, mounting /system as RW, or...
Thanks much.
Click to expand...
Click to collapse
I have always used the "Better Route". However, I was under the impression that s-off unlocked the partitions.
Out of curiosity, did you try the following command anyway: (adb push su /system/bin) ?
junkmail9 said:
I have always used the "Better Route". However, I was under the impression that s-off unlocked the partitions.
Out of curiosity, did you try the following command anyway: (adb push su /system/bin) ?
Click to expand...
Click to collapse
At least in this case /system is mounted RO:
- adb shell mount | grep system -> /dev/block/mmcblk0p33 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
- adb push foobar.txt /system/bin -> 'failed to copy foobar.txt to /sytem/bin/foobar.txt : Read-only file system
This isn't a regular consumer device so it's at least a little funky. For example, it doesn't get OTA updates and is stuck with an old RUU (htc sense 4.0... ruu 1.31.605.1 (? not sure where exactly to get RUU version). It also has the 'normal' CID (VZW__001).
It might get a little interesting digging up workable bootloader and supercid method, now out-of-date for basically everyone else.
pukebag said:
At least in this case /system is mounted RO:
- adb shell mount | grep system -> /dev/block/mmcblk0p33 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
- adb push foobar.txt /system/bin -> 'failed to copy foobar.txt to /sytem/bin/foobar.txt : Read-only file system
This isn't a regular consumer device so it's at least a little funky. For example, it doesn't get OTA updates and is stuck with an old RUU (htc sense 4.0... ruu 1.31.605.1 (? not sure where exactly to get RUU version). It also has the 'normal' CID (VZW__001).
It might get a little interesting digging up workable bootloader and supercid method, now out-of-date for basically everyone else.
Click to expand...
Click to collapse
If you're already S-OFF, you shouldn't need to do anything with supercid. Just put the phone into fastboot and flash a custom recovery - either CWM (link) or TWRP (link), depending on your preference. Follow the "manual installation" steps in the thread of your choice. I have been very happy with PhilZ's Touch CWM.
Also - first thing to do after installing the recovery is to make a nandroid backup of the (semi) pristine state of your phone.
Dear users,
I read multiple threads throughout internet and couldn't find working solution. My lg with kitkat 4.4.2 had lagged so I removed battery. After this phone is boot-looping with startup animation forever.
I can explore files with adb shell when phone is in recovery mode but don't have access to dalvik-cache. Command "su rm -rf /system/data/dalvik-cache" gives "permission denied nor "adb backup -all" cause "unlock your device and confirm...".
I cannot root phone by copying SuperSu files into /system/app. The command "su cp.. " gives no answer and later when exploring /app there's no SuperSu program.
I was trying to explore through sudo nautilus on Ubuntu during using one of rooting tutorial but the phone just disappears in the list of mounted devices.
I have important data like phone contacts, messages and some pictures inside phone memory. I didn't backup all of them formerly.
Any ideas?
likkufri said:
Dear users,
I read multiple threads throughout internet and couldn't find working solution. My lg with kitkat 4.4.2 had lagged so I removed battery. After this phone is boot-looping with startup animation forever.
I can explore files with adb shell when phone is in recovery mode but don't have access to dalvik-cache. Command "su rm -rf /system/data/dalvik-cache" gives "permission denied nor "adb backup -all" cause "unlock your device and confirm...".
I cannot root phone by copying SuperSu files into /system/app. The command "su cp.. " gives no answer and later when exploring /app there's no SuperSu program.
I was trying to explore through sudo nautilus on Ubuntu during using one of rooting tutorial but the phone just disappears in the list of mounted devices.
I have important data like phone contacts, messages and some pictures inside phone memory. I didn't backup all of them formerly.
Any ideas?
Click to expand...
Click to collapse
Could you elaborate on "disappears?" Usually if something is present and suddenly disappears in lubuntu, that means the connection was broken (either physically or by software, such as when switching drivers by running a command). Anyway, have you tried letting it sit for a day or something? I figure the reason it "lags" might potentially affect booting time.
It's also helpful to know what data you want out of it. Some things need root, some things don't need root. If all you want is file X in user space, I imagine that'd be infinitely easier than trying to get a random bootloader setting.
I have a soft bricked HDX 8.9 Apollo. I've scoured dozens of threads about unbricking my Apollo device and I feel fairly confident I could unbrick my device if I could just keep my device on long enough to transfer my ~600MB rom, but my device only has ADB (with root) access for about 45 seconds before it reboots, interrupting my file transfer (getting "Connection reset by peer" transfer error when the device resets).
- I can boot to recovery and fastboot modes which stops the boot loop, but I don't have ADB access in either of these modes.
- I've tried "adb -d shell stop" (which is a command I've seen used to stop a boot loop on other devices) but this does not prevent the boot loop.
Surprisingly no one in any of the threads I checked mentioned a similar problem so I guess I'll just ask here. I can give details if you want but really I just need to know if there's any way I can pause the boot loop while maintaining ADB access and I should be able to handle the rest.
Jabbernaut said:
I have a soft bricked HDX 8.9 Apollo. I've scoured dozens of threads about unbricking my Apollo device and I feel fairly confident I could unbrick my device if I could just keep my device on long enough to transfer my ~600MB firmware, but my device only has ADB (with root) access for about 45 seconds before it reboots, interrupting my file transfer (getting "Connection reset by peer" transfer error when the device resets).
- I can boot to recovery and fastboot modes which stops the boot loop, but I don't have ADB access in either of these modes.
- I've tried "adb -d shell stop" (which is a command I've seen used to stop a boot loop on other devices) but this does not prevent the boot loop.
Surprisingly no one in any of the threads I checked mentioned a similar problem so I guess I'll just ask here. I can give details if you want but really I just need to know if there's any way I can pause the boot loop while maintaining ADB access and I should be able to handle the rest.
Click to expand...
Click to collapse
No clue what you're trying to do. I'll throw this out, use the Terminal found in recovery mode.
---------- Post added at 09:30 PM ---------- Previous post was at 08:37 PM ----------
gwardsc65 said:
No clue what you're trying to do. I'll throw this out, use the Terminal found in recovery mode.
Click to expand...
Click to collapse
With all the necessary files along with the commands ready to copy and paste, you could replace recovery (if needed), aboot, and unlock the bootloader in 45 seconds or less. Boot into recovery and flash whatever you wanted to. Other options you could look into are bulk mode and 1-Click.
gwardsc65 said:
With all the necessary files along with the commands ready to copy and paste, you could replace recovery (if needed), aboot, and unlock the bootloader in 45 seconds or less. Boot into recovery and flash whatever you wanted to. Other options you could look into are bulk mode and 1-Click.
Click to expand...
Click to collapse
Absolutely agree. Forget the dated unbrick threads. Use 1-click or manually replace the bootloader and recovery. If pursuing the latter don't worry about immediately unlocking; that can be done later after device is stable.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
https://forum.xda-developers.com/kindle-fire-hdx/general/how-to-root-unlock-hdx-noobies-t3916167
Sorry for the limited info, but I can offer more clarity now that I have more time. Basically I soft-bricked an Apollo back in 2015 by accidentally flashing a rom designed for Safestrap v4 onto Safestrap 3.75. The last thing I had done before flashing the rom was I rolled back to 3.2.8 and towelrooted it. At the time I declared it a loss.
So yeah I guess I need to replace the bootloader and recovery. I don't have access to a linux or mac machine atm, so I guess I'll be doing this manually.
I was able to get my unlock file and and push twrp and aboot to /sdcard/ just fine, and it looks like I was able to get superuser in adb shell.
Code:
C:\ADB>adb shell
[email protected]:/ $ su
255|[email protected]:/ $ I have SU now right?
but when I run
Code:
255|[email protected]:/ $ dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
it returns
Code:
/dev/block/platform/msm_sdcc.1/by-name/recovery: cannot open for write: Permission denied
Do I need to change folder permissions to be able to execute this? If so, how do I do this?
EDIT: Oh I just realized I guess 255 isn't SU? Seems strange that the su command is going through without error if I don't have root access.
It looks like the one-click bootloader unlock method does not require root. Is there a way to accomplish a rootless unlock without one-click?
Jabbernaut said:
Sorry for the limited info, but I can offer more clarity now that I have more time. Basically I soft-bricked an Apollo back in 2015 by accidentally flashing a rom designed for Safestrap v4 onto Safestrap 3.75. The last thing I had done before flashing the rom was I rolled back to 3.2.8 and towelrooted it. At the time I declared it a loss.
So yeah I guess I need to replace the bootloader and recovery. I don't have access to a linux or mac machine atm, so I guess I'll be doing this manually.
I was able to get my unlock file and and push twrp and aboot to /sdcard/ just fine, and it looks like I was able to get superuser in adb shell.
Code:
C:\ADB>adb shell
[email protected]:/ $ su
255|[email protected]:/ $ I have SU now right?
but when I run
Code:
255|[email protected]:/ $ dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
it returns
Code:
/dev/block/platform/msm_sdcc.1/by-name/recovery: cannot open for write: Permission denied
Do I need to change folder permissions to be able to execute this? If so, how do I do this?
EDIT: Oh I just realized I guess 255 isn't SU? Seems strange that the su command is going through without error if I don't have root access.
It looks like the one-click bootloader unlock method does not require root. Is there a way to accomplish a rootless unlock without one-click?
Click to expand...
Click to collapse
Bulk Mode:
https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
Thanks for the tip! Unfortunately I do not have access to the filesystem via windows, I can only copy files over via ADB. So unless there's some way to gain access to the filesystem with an ADB command I'm probably sunk there
So that's it then I presume?
Jabbernaut said:
Thanks for the tip! Unfortunately I do not have access to the filesystem via windows, I can only copy files over via ADB. So unless there's some way to gain access to the filesystem with an ADB command I'm probably sunk there
So that's it then I presume?
Click to expand...
Click to collapse
Nope. There's usually a way if the HDX boots into recovery or bootloader. If recovery is twrp and not stock, it may be possible to issues the commands to replace aboot via the Terminal. It's not ideal, but may work. I think you really need to take another look at Bulk Mode. Follow the instructions very carefully or you will be out of luck. If you have any doubts, don't attempt using Bulk Mode.
gwardsc65 said:
Nope. There's usually a way if the HDX boots into recovery or bootloader. If recovery is twrp and not stock, it may be possible to issues the commands to replace aboot via the Terminal. It's not ideal, but may work. I think you really need to take another look at Bulk Mode. Follow the instructions very carefully or you will be out of luck. If you have any doubts, don't attempt using Bulk Mode.
Click to expand...
Click to collapse
I guess I should have clarified, I don't have twrp, I only have access to stock recovery. If I had twrp running I probably wouldn't be here lol.
Unless there is another thread that explains how to use this "Bulk Mode" without access to the tablet's filesystem in Windows, in the guide linked above, the very first step is to pull the diskindex from the drive as it appears in Windows. Obviously this will fail because it is not mounted, but here is the result with the tablet connected and ADB working anyway:
Code:
C:\ADB>wmic partition where index=22 get diskindex
No Instance(s) Available.
C:\ADB>wmic partition where (index=17 and numberofblocks=20480) get diskindex
No Instance(s) Available.
C:\ADB>wmic partition where (index=5 and numberofblocks=4096) get diskindex
No Instance(s) Available.
Without a diskindex reference to the tablet's drive, I can't proceed to the next step to copy twrp and aboot into the recovery folder. And as far as I can tell I don't have root anymore so I can't do it via ADB.
So I would assume I'm dead in the water here since as far as I can tell I don't have any access to the folders I need to place the files in? Unless I can like directly sideload them or something. I have virtually nothing to lose here so I'll try whatever.
Just to clarify, I definitely don't have root? What exactly does it mean if the "su" command does not throw an error but instead returns "255|[email protected]:/ $" ?
Code:
C:\ADB>adb shell
[email protected]:/ $ su
255|[email protected]:/ $ In what way did my permissions change here?
Jabbernaut said:
I guess I should have clarified, I don't have twrp, I only have access to stock recovery. If I had twrp running I probably wouldn't be here lol.
Unless there is another thread that explains how to use this "Bulk Mode" without access to the tablet's filesystem in Windows, in the guide linked above, the very first step is to pull the diskindex from the drive as it appears in Windows. Obviously this will fail because it is not mounted, but here is the result with the tablet connected and ADB working anyway:
Code:
C:\ADB>wmic partition where index=22 get diskindex
No Instance(s) Available.
C:\ADB>wmic partition where (index=17 and numberofblocks=20480) get diskindex
No Instance(s) Available.
C:\ADB>wmic partition where (index=5 and numberofblocks=4096) get diskindex
No Instance(s) Available.
Without a diskindex reference to the tablet's drive, I can't proceed to the next step to copy twrp and aboot into the recovery folder. And as far as I can tell I don't have root anymore so I can't do it via ADB.
So I would assume I'm dead in the water here since as far as I can tell I don't have any access to the folders I need to place the files in? Unless I can like directly sideload them or something. I have virtually nothing to lose here so I'll try whatever.
Just to clarify, I definitely don't have root? What exactly does it mean if the "su" command does not throw an error but instead returns "255|[email protected]:/ $" ?
Code:
C:\ADB>adb shell
[email protected]:/ $ su
255|[email protected]:/ $ In what way did my permissions change here?
Click to expand...
Click to collapse
Your best bet is to use 1-Click. 1-Click basically does the same thing as Bulk Mode, but does it automatically for you. Bulk Mode hint - bootloader.
gwardsc65 said:
Your best bet is to use 1-Click. 1-Click basically does the same thing as Bulk Mode, but does it automatically for you. Bulk Mode hint - bootloader.
Click to expand...
Click to collapse
Does 1-click not require USB access to the filesystem or root access? I guess I could install and run linux on a flash drive just to test this but it would be nice to know if the interface to the device is likely to work, I don't know anything about VirtualBox. If we're not sure I'll probably try it later.