Database Develop

Bricked, Need ADB push to recover, how mount?

Title says it all. While trying to learn some theme tricks, I must have screwed something up in the framework, because I'm stuck in a boot-loop after rebooting.
Thanks to Aria's post, which describes an easy way to make an easy ADB shortcut, I'm all set to go with ADB... but how can I force my cell to mount my computer when it's turned off? I just need to push my backup onto my phone, because I copied my CWM backup onto my pc and deleted it from my cell to make more room for videos. Stupid, I know
Any ideas? Thanks!

Nevermind, I fixed it through CWM by flashing a .zip of part of the framework that I changed, and it rebooted fine after that. From there I could mount my device.
Still, I'd be curious to know how to mount a device that cannot boot properly, if anyone knows a way.

how did you fix it i am stuck on lg logo when i boot i would really appreciate any help you could give

Komodo Rogue said:
Nevermind, I fixed it through CWM by flashing a .zip of part of the framework that I changed, and it rebooted fine after that. From there I could mount my device.
Still, I'd be curious to know how to mount a device that cannot boot properly, if anyone knows a way.
Click to expand...
Click to collapse
You can mount the system like this. If it's in a bootloop and ADB is enabled, this'll work.
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
Sent from my LG Thrill 4G

[Q] XXLSA Android 4.1.2 and Low Battery: Stuck at Boot. Data Recovery?

Recently my phone had a low battery status. It booted up but apparently lost power somewhere when restoring the Apex Launcher screens.
Since then it just shows the Samsung logo and gets rather hot. I left it in this state for over an hour with no progress.
Boot and recovery mode work fine. Unfortunately adb is not in root by default, as such pulling is useless as nothing is mounted.
issuing
Code:
adb root
will result in:
Code:
adbd cannot run as root in production builds
I can issue for instance:
Code:
adb shell
su
e2fsck -pv /dev/block/mmcblk0p10
mount -t ext4 /dev/block/mmcblk0p10 /data
Unfortunately I cannot tar gzip and copy to the externalSD nor pull the data folder.
Starting dalvikvm fails:
Code:
127|[email protected]:/ # dalvikvm
dalvikvm
Dalvik VM init failed (check log file)
What options do I have to backup my data? Please provide me with concrete ideas and steps.
Many people are having similar problems, and I sincerely thank you if you can help me figure out a way to backup my data at this stage.

After reading the first two sentences and the title:
Buy a new battery.
Install something else, you are still on an early leak and not an official release.

I found a quick solution. All kudos and thanks go out to Philz as well as
TAHER128
Instructions and files are here:
http://www.youtube.com/watch?v=1TinSwsehZ8
After the new recovery mode and kernel is installed, reboot into recovery mode and go to the mount menu in order to select "mount USB storage". Backup everything to your PC.
From hereon out you are safe.
Install busybox if you want. Reflash a stock or custom rom if you want and/or dig your way through logs and fixes within a now powerful bash shell.

blairmiller said:
This problem is difficult to solve by your phone itself. Maybe you need to install some software to help you.
Click to expand...
Click to collapse
This thread is 2 months old

root
The reasons for getting a bootloop on your Android device might be anything. If you wish to know the reason why your Android phone is stuck on the bootloop, you need not type your problem on the Google search box. Just calm yourself for a while and think what you did just before. It could be anything! Here are some major reasons why your Android device is caught in a bootloop.

[Q] mounting HTC mini 2's partition

Hello,
I want to remove Vodafone's boot animation but don't want to root my device. To do that, I must either edit /system/customize/CID/VODAP**.xml or push proper VF_bootanimation.zip into /system/customize/resource. I am not able to do it neither from adb nor from adb shell - there is read-only warning or "permission denied".
Is there a way I can access this XML file, like:
a) registering on HTCDev as a developer
b) mount phone internal memory (/dev/block/mmcblk0p43) to a PC as a mounted drive while phone is switched off and then change its content (is this called 'fastboot'?)
BR
Plodozhor

plodozhor said:
Hello,
I want to remove Vodafone's boot animation but don't want to root my device. To do that, I must either edit /system/customize/CID/VODAP**.xml or push proper VF_bootanimation.zip into /system/customize/resource. I am not able to do it neither from adb nor from adb shell - there is read-only warning or "permission denied".
Is there a way I can access this XML file, like:
a) registering on HTCDev as a developer
b) mount phone internal memory (/dev/block/mmcblk0p43) to a PC as a mounted drive while phone is switched off and then change its content (is this called 'fastboot'?)
BR
Plodozhor
Click to expand...
Click to collapse
I think you need S-OFF to edit system files. At the moment not possible

plodozhor said:
Hello,
I want to remove Vodafone's boot animation but don't want to root my device. To do that, I must either edit /system/customize/CID/VODAP**.xml or push proper VF_bootanimation.zip into /system/customize/resource. I am not able to do it neither from adb nor from adb shell - there is read-only warning or "permission denied".
Is there a way I can access this XML file, like:
a) registering on HTCDev as a developer
b) mount phone internal memory (/dev/block/mmcblk0p43) to a PC as a mounted drive while phone is switched off and then change its content (is this called 'fastboot'?)
BR
Plodozhor
Click to expand...
Click to collapse
kativiti said:
I think you need S-OFF to edit system files. At the moment not possible
Click to expand...
Click to collapse
You will have to flash a custom kernel on your phone that removes the write protection. So only unlocking the bootloader and flashing the kernel is sufficient. If you haven't unlocked you bootloader yet, backup all the data from the internal memory because it gets wiped

Thanks for answers everybody. I am little bit afraid of flashing foreign ROM because it replaces phone's existing ROM and warranty might be void. What I want to do is to keep the existing ROM, and alter one XML file in the customize folder.
I would like to rather have a scenario of mounting the phone memory as 'external removable drive' to some other system. For example, couple of years ago I played around with my home router - I was able to mount my home router's memory to PC running Linux and change some tweaks in the resulting /mount directory. Can I do something similar with mini 2? What is fastboot tool from ADB suite?
Maybe there is another, easier way for eradicating ad bootanimation? Currently I see 3 options: change CID so VODAP102.xml is not triggered; post fixed VF_bootanimation.zip; or change VODAR102.xml.
I am a programmer, however I never worked with writing apps for Android. Is there a way HTCDev-enabled developer can access /customize folder? Like remounting /mmcblk0p43 with RW permission etc.
Thanks in advance and sorry for 'noobism'

plodozhor said:
Thanks for answers everybody. I am little bit afraid of flashing foreign ROM because it replaces phone's existing ROM and warranty might be void. What I want to do is to keep the existing ROM, and alter one XML file in the customize folder.
I would like to rather have a scenario of mounting the phone memory as 'external removable drive' to some other system. For example, couple of years ago I played around with my home router - I was able to mount my home router's memory to PC running Linux and change some tweaks in the resulting /mount directory. Can I do something similar with mini 2? What is fastboot tool from ADB suite?
Maybe there is another, easier way for eradicating ad bootanimation? Currently I see 3 options: change CID so VODAP102.xml is not triggered; post fixed VF_bootanimation.zip; or change VODAR102.xml.
I am a programmer, however I never worked with writing apps for Android. Is there a way HTCDev-enabled developer can access /customize folder? Like remounting /mmcblk0p43 with RW permission etc.
Thanks in advance and sorry for 'noobism'
Click to expand...
Click to collapse
I'm not talking about flash a rom, but only just a kernel. Flash the Liberty Sense kernel and then got can customise the boot animation

csoulr666 said:
I'm not talking about flash a rom, but only just a kernel. Flash the Liberty Sense kernel and then got can customise the boot animation
Click to expand...
Click to collapse
Will I be able to flash original kernel back?
Also, the phone will lose warranty?

plodozhor said:
Will I be able to flash original kernel back?
Also, the phone will lose warranty?
Click to expand...
Click to collapse
If you make a backup of your rom via a custom recovery, then yes. And unfortunately unlocking the bootloader and flashing a custom kernel will void the warranty

[Q] Trouble with R/W access

Hey all
I'm having some trouble getting r/w access back on system on my 5803 on .726 firmware.
I have root and working recovery, just no r/w on system. Every time I check system access in terminal it sits at "ro" and not "rw"
I had full access in Kitkat, but when I flashed Lollipop I seemed to have lost r/w access. I have tried updating my recovery, RICDefeat, and byeselinux, all to no avail.
I feel like I'm busy missing something completely obvious, but I can't for the life of me figure out where I'm going wrong. Can any of you fine souls help?

Can you enable r/w acces using adb?
Open command line window, type adb shell (with device connected in debugging mode), then su, then mount -o remount,rw /system.
Don't know if this works for Lollipop, but I do see other users struggling to get full r/w permissions with the latest LP firmware.
Cheers.

chris5s said:
Can you enable r/w acces using adb?
Open command line window, type adb shell (with device connected in debugging mode), then su, then mount -o remount,rw /system.
Don't know if this works for Lollipop, but I do see other users struggling to get full r/w permissions with the latest LP firmware.
Cheers.
Click to expand...
Click to collapse
It seems that I can enable that way, but it doesn't persist after a reboot. And mounting system in recovery doesn't seem to do anything either. If I try run certain things in recovery it seems like they don't really work. I can change recoveries and ROM, but things like debloating scripts don't seem to work. It's quite strange.

Can you use Script Manager from Play Store to run a script at boot to enable root access? Not the best solution but may work?
Peace

chris5s said:
Can you use Script Manager from Play Store to run a script at boot to enable root access? Not the best solution but may work?
Peace
Click to expand...
Click to collapse
I suppose I could, but that's not gonna solve my problem with flashing things in recovery

Still struggling with this :/

Download this file, run .bat and ready. No need to restart.
https://mega.co.nz/#!tcEDFD4I!hrpQZxmq2Af8BFUS-ciCYBGVpEJ1LvVn_nLb2SYqAWc

pedro5148 said:
Download this file, run .bat and ready. No need to restart.
https://mega.co.nz/#!tcEDFD4I!hrpQZxmq2Af8BFUS-ciCYBGVpEJ1LvVn_nLb2SYqAWc
Click to expand...
Click to collapse
Thanks for the suggestion, but it doesn't work.

[SOLVED]Need assistance!

Ok so this is the rundown. Ran Fix Contexts in TWRP recovery no longer could get phone to connect to pc to read SD card period. Ran several apps that didn't fix SD card permissions. wiped phone completely including DATA, SYSTEM, and SDCARD. had a custom rom on the phone didnt think it would wipe its wiped.
Im in TWRP no adb sideload, no fastboot from bootloader. something with file permissions is preventing phone from even being seen by PC. and no its not USB issues i tried to run RUU. it cant even see my phone. No one can even provide a suggestion i can still do terminal from TWRP but it has something to do with me using the fix contexts that screwed it up.

really no one has a suggestion? i have access to TWRP recovery and can run terminal commands i just need something to fix what ever fix contexts did so i can get access to usb functionality. please? if looked all over google and there is no one with this issue. every topic points to adb sideload and fastboot working but usb doesnt work in my case due to use of fix contexts.

M4rin3r said:
really no one has a suggestion? i have access to TWRP recovery and can run terminal commands i just need something to fix what ever fix contexts did so i can get access to usb functionality. please? if looked all over google and there is no one with this issue. every topic points to adb sideload and fastboot working but usb doesnt work in my case due to use of fix contexts.
Click to expand...
Click to collapse
i solved it mysself no thanks to a forum that supposed to help and yet im a noob at this ****.
for those of you who have done as i did and bricked the phone.
go into twrp recovery and go to terminal
Code:
busybox
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
Reboot phone to see if it worked. then try to see if you can use adb on pc to sideload a rom.

M4rin3r said:
i solved it mysself no thanks to a forum that supposed to help and yet im a noob at this ****.
for those of you who have done as i did and bricked the phone.
go into twrp recovery and go to terminal
Code:
busybox
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
Reboot phone to see if it worked. then try to see if you can use adb on pc to sideload a rom.
Click to expand...
Click to collapse
Well, I could have come in here and pretended I've seen this before, but honestly, I've never run Fix Contexts in TWRP (in fact, I've never heard of it). You've got to remember that most of us know what we know either through our own bad experiences or by following how others fixed their bad experiences. So, I appreciate that you marked it solved and put how you solved it in this thread. Next time someone has the same issue, I'll know where to look for a solution.

coal686 said:
Well, I could have come in here and pretended I've seen this before, but honestly, I've never run Fix Contexts in TWRP (in fact, I've never heard of it). You've got to remember that most of us know what we know either through our own bad experiences or by following how others fixed their bad experiences. So, I appreciate that you marked it solved and put how you solved it in this thread. Next time someone has the same issue, I'll know where to look for a solution.
Click to expand...
Click to collapse
Its also known as fix permissions.

@ M4rin3r
Can you PM me with more details on how to do this, I'm facing the same problem....