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
Related
Not sure when or what happened but I'm unable to mount now. I'm able to use adb and everything but unable to mount AT ALL via adb nor drop down on the notification bar. Any ideas? Yes i've searched and had other members try n figure out why.
imbonez9 said:
Not sure when or what happened but I'm unable to mount now. I'm able to use adb and everything but unable to mount AT ALL via adb nor drop down on the notification bar. Any ideas? Yes i've searched and had other members try n figure out why.
Click to expand...
Click to collapse
If you have Cyan's 1.4 recovery, reboot into recovery, go to console and type
Code:
ums_enable
if it doesnt work, its hardware problem. Make sure its in right, pull it out, blow out any dust, put it back in.
If it does, its something wrong with your ROM install. Make sure its not your computer OS either
you have given absolutely no information on your set-up and its hard to diagnose anything if we don't know what you have
i have
jacXhero1.2
vista 32bit.
My thing is i can use adb with no problems at all, will register every time.
if you can use adb then it shouldn't matter if you can mount the phone, just adb push stuff to your phone if you need it, or pull it. you said you couldn't mount via adb so i guess that means you did "adb shell sdutil ums enable" and you still have ums enabled in your settings?
My whole thing is i want to be able to mount so i can put things on my SD Card and take things off like: music,pictures,videos.
did you try flashing your ROM again? when did it start happening
Go to Settings>Applications>Development and disable USB debugging, you can now mount on your computer to access files. Reenable when done.
SolemnWishing said:
Go to Settings>Applications>Development and disable USB debugging, you can now mount on your computer to access files. Reenable when done.
Click to expand...
Click to collapse
No i still can't thank you though.
imbonez9 said:
No i still can't thank you though.
Click to expand...
Click to collapse
Did you try it with a different card?
you don't NEED to mount to put things on your SD card, you can just do
Code:
adb push \users\me\music\file.mp3 \sdcard\music\file.mp3
or do the same thing to pull from the sdcard, as long as the phone is reading the sdcard then you can push/pull through adb to/from the sdcard
I was trying to update the status bar on my i9000m/JH2. I must have done something wrong when zipping, signing, or zipaligning the file. I was able to apply the update.zip without any errors through recovery mode. But when i rebooted, I was met with continuous force close windows. I had my original backed up and wanted to place that into /sdcard and then simply run it from recovery mode to 'undo' the damage i did.
/sdcard appears empty when I run abd to my phone while in recovery mode. If i attempt to push a file to it, i get 'permission denied'. Do i need to manually mount /sdcard in recovery mode to be able to overwrite /sdcard/update.zip (can this be done)?
*snip*
On sec...
nudge nudge
Reflash is only option now. Recommend in future you leave recovery update.zip on SD card and use root explorer to copy over new f/w. That way if no good you can recover easier.
Sent from my GT-I9000M using XDA App
If u get adb running why not just push it then ?
adb shell stop
adb push framework-res.apk /system/framework/framework-res.apk
adb shell start
lgkahn said:
Reflash is only option now. Recommend in future you leave recovery update.zip on SD card and use root explorer to copy over new f/w. That way if no good you can recover easier.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
I ended up reflashing shortly after it happened. I'll look into root explorers.
Daneshm90 said:
If u get adb running why not just push it then ?
adb shell stop
adb push framework-res.apk /system/framework/framework-res.apk
adb shell start
Click to expand...
Click to collapse
I was able to get adb running, but I didn't see /system when listing. Did i need to mount it?
onaquest said:
I was able to get adb running, but I didn't see /system when listing. Do i need to mount it?
Click to expand...
Click to collapse
/system should still be already mounted. Otherwise u wudnt see a homescreen.
Just try the commands.
Daneshm90 said:
/system should still be already mounted. Otherwise u wudnt see a homescreen.
Just try the commands.
Click to expand...
Click to collapse
One other detail is that the phone wasn't rooted At the time I thought that might have been preventing me from seein /system.
This is all educational for me, I was wondering what other options I had before reflashing. Thanks for all the input guys. I ended reflashing with Odin a few days ago.
I have sucessfully rooted my nook and I can load apks from dropbox, installers or via adb so I am a happy camper, all is good....
But I got greedy. The ComicViewer doesn't work well without menu keys so I decided to install softkeys.apk and that is where the trouble started, something is amiss.
I am not an expert here, just a novice, so forgive my patchwork explanation.
Here's what I know and what I did, maybe someone can spot my error?
I can fully access adb.
I remember installing SuperUser and SU using the commands:
# adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
And all was fine, SuperUser shows up in the drawer. Then I tried installing SoftKeys and it never showed up or worked.
So I figured I fubared the SuperUser install somehow or have an old version of SU or SuperUser. So I downloaded the most recent versions and went to uninstall the original with uninstall utilities and it's not listed in any of them, so I tried using adb (adb shell ls /data/app) and it's still not in the list.
I even reset the Nook to factory and rooted again with nooter and when I tried to install SuperUser again (downloaded the latest version here on the forum) it said "Install Failed already exists!"
So I cannot uninstall the SuperUser or overwrite it with a newer version, and a factory reset doesn't fix it??
I cannot use any root utilities like SuperUser or z4root, SuperUser has all blank screens and I cannot update it and 4zroot just doesn't seem to do anything but reboot the nook.
Titanium Backup says I don't have root access and other utilities say the same thing,
I can mount system partition as read-write
> adb shell
# mount -o remount rw /system
# exit
That works...
So I tried the commands again to install SuperUser and SU and when I try to install SU
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
are OK but when I do:
# cat /data/local/su > su
I get:
Cannot create su: remote access failed
I have also tried a few other things that seem to be available to root users and all come back with write or access errors.
What could I be doing wrong?
Note: I also tried to do a full wipe by using that Power and Volume Down and nothing happens...
Power the nook on and off immediately 8 times until it does a full factory reset. When I've done the Power+VolUp+Nook button reset it doesn't always seem to do a FULL reset. When the nook fails to boot 8 times it does a different reset that takes a good deal longer and (at least in my experience) seems to be the real deal.
z4root will work and install superuser for you.
mhoepfin said:
z4root will work and install superuser for you.
Click to expand...
Click to collapse
I have already mentioned that that did not work, but thanks for the suggestion anyway.
Ok, something VERY weird is going on.
I have reset it to factory twice
Each time I did it by powering on and off 8 times in a row
The first time after it indicated it was updating th software, it went into a stuck at NookColor Logo boot loop again.
The second time I left in the nooter microSD card and it booted properly.
But it booted to a "clean" system with all my programs.
All my settings and data was gone, but all my apks were still installed.
So what exactly did it reset? Just data?
I tried to get it to flash both ways, the quick (power/home/volume) and now twice with the 8 power cycles. Neither reset the Nook entirely.
Am I screwed?
I want to go back to factory to fix this thing
EDIT:
Looks like I am locked out of the system entirely, none of my apps work, some of them come back and say no write access.
I cannot do an app listing like:
adb shell ls /data/app
I get:
opendir failed, Permission denied
I can't do a simple mount
mount -o remount rw /system
I get:
mount: operation not permitted
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
axe2 said:
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
Click to expand...
Click to collapse
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
gormly said:
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
Click to expand...
Click to collapse
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. I would suggest PMing pokey9000 and see if he can walk you through a recovery. You might be the first near brick that requires running some of the recovery commands by hand. I think Pokey9000 knows the most about that.
axe2 said:
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. .
Click to expand...
Click to collapse
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
gormly said:
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
Click to expand...
Click to collapse
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
norkoastal said:
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
Click to expand...
Click to collapse
Yep tried all those things...very frustrating afternoon so far
However...I did get it to boot.. here is how:
Press and hold the power button while inserting the USB charger connected to a computer, continue to hold (I think it was 10 seconds or so).
I remember doing this to reset a device a long time ago, not sure what.
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
gormly said:
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
Click to expand...
Click to collapse
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
johnopsec said:
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
Click to expand...
Click to collapse
I did 1,2,3,6,7,8 and in place of 4/5 I used the most recent version of SU and SuperUser and all is good on my Nook! Not sure what happened before but it must have been a bad version of su or superuser. In any case, all seems fine, only Titanium doesn't work, all the rest of the root requesting apps work fine.
Thanks!
A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
Wait for ADB to enable, run "Shell Root" from SuperOneClick, wait until it says you have root.
Enter adb shell from command line, You should have root(#) access:
adb shell
Mount the system directory as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Make a new directory on /data for your recovery files: (sdcard wont be mounted yet)
mkdir /data/recover
Exit adb shell:
exit
Push your known working files to the new directory:
adb push /path/to/local/file.ext /data/recovery
Enter adb shell from command line:
adb shell
Copy your newly pushed recovery files to their proper location:
cp /data/recover/services.jar /system/framework
cp /data/recover/framework.jar /system/framework
cp /data/recover/famework-res.apk /system/framework
Reboot:
reboot now
Thanks! Extremely happy you are deving for this phone
What's the best way to backup my stock partitions before I keep playing with those files?
Titan Backup works for that?
Or just a tar cf /mnt/sdcard/systembackup.tar /system , works?
Thanks in advance.
uskr said:
What's the best way to backup my stock partitions before I keep playing with those files?
Titan Backup works for that?
Or just a tar cf /mnt/sdcard/systembackup.tar /system , works?
Thanks in advance.
Click to expand...
Click to collapse
I would just use the tar solution, much easier to deal with.
You can also use ADB, adb pull /system system
Also, the retail dump I did matched my phone dump bit for bit, as long as you have that you should be fine.
Thanks! I am messing around with the APKs and scripts to get the webtop to work without the dock. So I wanted to make sure I was covered.
designgears said:
I would just use the tar solution, much easier to deal with.
You can also use ADB, adb pull /system system
Also, the retail dump I did matched my phone dump bit for bit, as long as you have that you should be fine.
Click to expand...
Click to collapse
I already did both adb pull of system and tar, but how did you do the retail dump?
lpsi2000 said:
I already did both adb pull of system and tar, but how did you do the retail dump?
Click to expand...
Click to collapse
tar dump as root of system
One last question.
Once I deodex my /system/app, should I just do a adb push app /system/app and then rm /system/app/*.odex ?
I am used to use the update.zip trick on the captivate. But I am not sure how to proceed on this phone.
uskr said:
One last question.
Once I deodex my /system/app, should I just do a adb push app /system/app and then rm /system/app/*.odex ?
I am used to use the update.zip trick on the captivate. But I am not sure how to proceed on this phone.
Click to expand...
Click to collapse
push apps, then push framework, reboot, then delete all the odex files, reboot
from system do something like; find . -name "*.odex" -exec rm {} \;
designgears said:
push apps, then push framework, reboot, then delete all the odex files, reboot
from system do something like; find . -name "*.odex" -exec rm {} \;
Click to expand...
Click to collapse
Unrelated to this, I could sware yesterday I got to the recovery screen where I was able to wipe stuff and also be able to use update.zip. Although I did not use and update files but saw the option there. Today I am looking everywhere but the recovery screen does not come up with the options. I only see exclamation point and the droid. May be I am going nuts but can anyone confirm this.
lpsi2000 said:
Unrelated to this, I could sware yesterday I got to the recovery screen where I was able to wipe stuff and also be able to use update.zip. Although I did not use and update files but saw the option there. Today I am looking everywhere but the recovery screen does not come up with the options. I only see exclamation point and the droid. May be I am going nuts but can anyone confirm this.
Click to expand...
Click to collapse
tap at the bottom right of the screen right above the search button
designgears said:
tap at the bottom right of the screen right above the search button
Click to expand...
Click to collapse
ahha, thank you. Now I know I am going crazy. I used it yesterday to wipe when the system was unstable on me after playing around with the framework. I am must have stumble on that by accident. I am wondering if this documented yet somewhere around here.
Also too bad we cannot get root from there yet.
Well thank you for this. So when it boots to run, does it do a sys check to verify files are the same size or what? Anyway went to my local AT&T store and they swapped it out for me.
realawill said:
Well thank you for this. So when it boots to run, does it do a sys check to verify files are the same size or what? Anyway went to my local AT&T store and they swapped it out for me.
Click to expand...
Click to collapse
No, I just made a bad edit and it was FC hell
IT DOES NOT WORK WITH ME
I have been trying this trick for many times. The device restart and SuperOneClick hanging without any result.
designgears said:
No, I just made a bad edit and it was FC hell
Click to expand...
Click to collapse
Crazy....mine just would not reboot. But good to know that there is a way to recover. Love the phone but hate Motorola. Wish that it was easy as the Cappy.
Cool stuff. I may snatch the framework off the phone in stock form and make a batch package for this so folks can easily just double click to restore their framework and system app folder.
Good work DG...
I never get past that initial... Starting RSD protocol support screen. Is that fast boot? If so I'm a retard...
EDIT: I need the face palm sticky. It's not Volume UP...it's Volume Down. Reading comprehension for the loss...
azy8000 said:
IT DOES NOT WORK WITH ME
I have been trying this trick for many times. The device restart and SuperOneClick hanging without any result.
Click to expand...
Click to collapse
I have done this several times now, it works
I soft bricked my Atrix earlier this morning, and used this to recover. The time limit is a serious pain!
I ended up needing to separate /system into 5 separate pushes of 30MB each in order to get them done in time.
Oddly, after restoring everything, the phone is no longer associated with my motoblur account, and I can't add it.
Also, I think there my be some files in /system that are unaccounted for by the filesystem, as there is 70MB more than what is present.
Edit:
Restoring the system fixed both above problems.
Hey,
seems I bricked my tablet, though i don't know how.
It shutdown because it had no power anymore and when I tried to boot while loading it wouldn't stop booting.
I can connect via adb but it seems /sdcard and /data are read-only mounted and I don't know how to fix it.
adb remount will fail...
Please help me
Nereuz said:
Hey,
seems I bricked my tablet, though i don't know how.
It shutdown because it had no power anymore and when I tried to boot while loading it wouldn't stop booting.
I can connect via adb but it seems /sdcard and /data are read-only mounted and I don't know how to fix it.
adb remount will fail...
Please help me
Click to expand...
Click to collapse
If you you're 2013 KFHD is in a bootloop then you need to get an exchange through Amazon. Either that or wait until their is a recovery process for it.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
I don't mind sending it in, but is there a way to remount sdcard as rw, so I can delete personal data first?
Nereuz said:
I don't mind sending it in, but is there a way to remount sdcard as rw, so I can delete personal data first?
Click to expand...
Click to collapse
No, not without access to the bootloader.
After trying to remount /data and/or /sdcard as rw for a while I gave up and used 'adb reboot recovery' to reset the device, no need to send it in.
Though I still don't know how that happened...