So, I figured with all my time off from classes during spring break that it would be a good idea to update my HTC One. It was running a rather old version of the HD rom and i assume some old version of TWRP or Clockwork.
Using Windows 7 and fastboot, I erased the cache and pushed over TWRP 2.7 then used "fastboot reboot". At the time, I was unaware of what trouble that last command would get me into. Upon further investigation, I found out that I needed to erase the cache again and use "fastboot reboot-loader". Once i sent "fastboot reboot" the phone shutdown, then made it to the boot screen and shut off I think.
At the moment all my phone will do is turn the red light off and on. If the red light is off, holding down the power button for ten seconds turns the light on. Holding down the button for three seconds turns off the light. Holding down the power button and volume down button at the same time for any amount of time does nothing.
Does anyone have ideas on how I get it to work again?
Try holding it to a bright light while holding the power key for 15 seconds, also, it's "fastboot reboot-bootloader"
Sent from my HTC One using XDA Premium 4 mobile app
Whoareyou said:
Try holding it to a bright light while holding the power key for 15 seconds, also, it's "fastboot reboot-bootloader"
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Held it close to my lamp while holding the button for 15 seconds. Tried it multiple times and nothing happened but the red light by the speaker going off and on every 15 seconds or so.
I did so more digging around and found this thread: http://forum.xda-developers.com/showthread.php?t=2301007
I tried option one and it worked. I love how well these phones are setup to avoid perma bricks.
I should be good at attempting to put TWRP on it correctly, right?
Update: I turned the phone off after booting up the first time since the issue. The phone would not start up without using one of the button tricks. I was able to properly flash TWRP 2.7. I still have to use one of the two tricks to get it to do a cold boot.
TWRP 2.7 is confirmed to be on the phone. When I got to install with .zip, none of my .zip file are shown by TWRP. Any ideas why this is happening?
Update: Idk if this is normal, but there is a folder named "0" in the internal storage area that Windows can see. TWRP can only see the "0" folder and not the area that Windows sees.
Madog7 said:
IUpdate: I turned the phone off after booting up the first time since the issue. The phone would not start up without using one of the button tricks. I was able to properly flash TWRP 2.7. I still have to use one of the two tricks to get it to do a cold boot.
TWRP 2.7 is confirmed to be on the phone. When I got to install with .zip, none of my .zip file are shown by TWRP. Any ideas why this is happening?
Update: Idk if this is normal, but there is a folder named "0" in the internal storage area that Windows can see. TWRP can only see the "0" folder and not the area that Windows sees.
Click to expand...
Click to collapse
Yes, this is probably normal. Earlier android versions stored data in /data/media, while newer ones use /data/media/0. The TWRP UI is smarter than the part that shows the files via USB.
But what do you mean when you say none of the files are shown by TWRP? Cant the computer find the files, but TWRP cannot? Is the contents of the "0" folder empty?
The first thing I would check is to unmount /system, /sdcard, and /data, then run these commands to check whether there's filesystem corruption:
Code:
e2fsck -n -f /dev/block/mmcblk0p35
e2fsck -n -f /dev/block/mmcblk0p37
(You can use the built-in shell to run the commends, or use the ADB shell.)
Related
Okay I don't know if this will help anyone, but I figured out how to stop Windows from detecting the phone as two USB drives when the phone goes into Recovery mode, and to make it show up as Android Composite ADB device.
I do NOT have HTC installed, rather, I'm using the USB 3 drivers that come down through the SDK, so I'm not sure how to do this if you are using the HTC Sync drivers intead.
At any rate, start with the phone off and disconnected. Open the Device Manager. Boot with your prefered method into Recovery mode, then connect the phone. It should detect as USB Mass Storage Device under Universal Serial Bus Controllers. Right click on USB Mass Storage Device and click Uninstall and then OK. Once this is done, disconnect the phone (you can leave it running in Recovery).
Open My Computer and navigate to C:\Windows\inf. Copy the files usbstor.inf and usbstor.pnf to your desktop or wherever, it doesn't matter, just make sure you put them somewhere you can get them later. Then delete them from the C:\Windows\inf folder. These are the drivers that Windows automatically uses for USB storage devices.
Ok, now bring Device Manager back to the foreground and plug the phone back in in Recovery. It should show up as Android Phone with an exclamation mark. If Device Wizard pops up cancel out of it. Now right click on the Android Phone and click update driver. Click Browse my computer for driver software. Click Let me pick from a list... Click Android Phone and Next. Click Have Disk. Browse to your SDK folder into the USB Drivers folder and you should see android_winusb.inf, select that then click OK. You should now have a list of three items to select, this part I am not sure if there is a 'right' or a 'wrong' but I go with Android Composite ADB Interface.
Select that or whichever one you think and this is what it will install as. Bingo, now whenever you connect the phone into Recovery or boot into Recovery with it already connect it correctly detects as the Composite ADB Interface or whichever you selected, but does NOT show up as any USB drives.
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
At any rate, to get everything back to normal as far as your computer being able to use USB storage devices just copy those two files back to the inf folder before you connect them and you should be fine.
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
.
Click to expand...
Click to collapse
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Or you could try what I've done 7 times and achieved ADB Shell 7 times...
1. Turn the phone off.
2. Start running Loop.bat
3. Unplug USB cable.
4. Turn device on in Fastboot by holding in the optical joystick and power.
5. Plug USB in.
6. Hit power button once to get to HBOOT.
7. Wait two seconds for it to do it's thing.
8. Pull off the back of the phone.
9. Hit Vol - to Recovery then hit power.
10. Immediately after doing this continuously push the sd card in and out (about every .5 - .75 seconds)
11. ?????
12. Profit
@DigitalDementia--
How is what you said relevant in this thread?
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
Click to expand...
Click to collapse
drtrmiller said:
@DigitalDementia--
How is what you said relevant in this thread?
Click to expand...
Click to collapse
Pretty positive it had everything to do with that section of the first post, he said he still couldn't achieve root I attempted to help him. Why don't you explain to me exactly what it doesn't have to do with this thread?
rynosaur said:
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Click to expand...
Click to collapse
The real bummer here - and I should have known better, really - is that this wipes your phone.
I suppose it should be obvious, but take it from someone who's pretty new to Android phones and just wiped their entire phone after following your steps: Please add a warning to your original post.
It's late, I'm tired and irritated, but I'm sort of bummed to know I went from hero to zero in trying to enter shell (again) during recovery all in an effort to get proper perm. root. Sort of ****ty to know that I just lost everything.
still no root
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
USB drives are ok in recovery
When I am in recovery with adb and working correctly it still shows the 2 USB drives so this is normal and ok, what you have done is fool yourself into thinking that your phone is in correct mode but it really is not, this is why it still does not work, sorry.
rynosaur said:
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Now that I've scorched the earth, I'm hitting this thing hard with every trick I can think of to get the shell in recovery again.
Thankfully, I at least have my app list on appbrain.
After researching around the different forums, I think this maybe my issue. I will have to make this attempt when I get home.
This is what I posted on a different forum. I am not sure if this is a similar experience you were having:
So, for a little a bit I was having issues with finding and modding the usb.inf file. I got that finally resolved... Now as I go to one of the first parts of the procedure, executing the adb shell command. Well at first it said the 2 lines, about the daemon and whatever the second line was. Anyways, the third line did not say "no device found" it went straight to a shell prompt "$" . The instructions made a point in the instructions for it to say " no device found" .
I went ahead with the rest of the instructions. No Luck. And I did both methods. A co-worker of mine told to run adb devices to see if my phone is recognized. I will also make that attempt tonight.
I wanted to know if any of you had some insight. I made sure I was in the right directory.
I will make another attempt on a different machine tonight.
Thanks. Oh yeah, I do have some UNIX experience if that makes a difference.
I had the same problem, used this method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
kentoe said:
I had the same problem, used this method here
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
Click to expand...
Click to collapse
I rooted in Windows, rather than linux, simply because I like the look of MejDam's procedure better than the linux script posted here on XDA--and his windows procedure is accompanied by his YouTube video
Long story short: I had ADB Composite Device AND the two storage volumes mounted together, as I got shell, and did the other steps in recovery. NB: they were mounted as Generic Storage Volumes, not writeable partitions. The stock recovery on DI does not allow host to mount either partions, although I'd like to see if
Code:
mount /dev/block/mmcblk0p1
worked for the SDcard on the sdcard, cuz then it would be a cinch to mount sdcard/emnc partition into host OS--windows, linux, Atari 2600, etc Worth a try.
Anyhow, my conclusion: a bad driver setup could be a barrier to catching adb shell, but it is certain not the prevailing problem for most, IMHO.
Was wondering if bast525(the creator of the thread) was ever able to adb shell while in recovery, and if so what did you do thanks.
Heh, I wish.... I've tried just about every method posted on these forums, and five different SD cards from Sandisk, PNY, and Kingston. The only thing I haven't tried is rolling back to the pre OTA update, because I don't want to wipe the phone at this point.
I have had my Nook Color rooted for about 3 weeks and have been enjoying it.
But today things started to mess up.... A LOT.
I use my Nook Color in school for reading books and playing Angry Birds when the teacher's not looking, and throughout the day the UI was getting more and more sluggish.
And so, a few hours ago I decided to turn it off and then back on.
After it cut off I let it sit for about 10 mins before trying to boot it back up.
Now, for some reason it just wouldnt.
After fiddling with it a bit I discovered that if I took the SD card out then it would power up, but then freeze at the "touch the future of reading" screen.
But if I put the SD card in and hooked the machine up to my computer it froze at the "n" screen.
Knowing that I probably needed to do the factory reset I plugged it in and turned it off 8 times and that got me to be able to open Clockworld Recovery v3.0.0.5
I scrolled down to the "wipe data/factory reset" option.
Here is what i got:
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/ .android_secure...
E:failed to mount /sdcard (No such file or directory)
Error mounting /sdcard/ .android_secure!
Skipping format...
Data wipe complete.
E:Can't mount /cache/recovery/log
E:Cant open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Even after the factory reset or whatever that was it still wont boot all the way up.
So yeah... Is there anything I can do to save my Nook Color? Or is it ruined?
Back up the data on your SD and format it.
If you can still get into CWR, that means you can use adb. Try my method to restore to stock without adb by flashing a zip or snowfox's method with dd and boot img. Both threads are in dev.
Sent from my HTC Desire using XDA App
samuelhalff said:
If you can still get into CWR, that means you can use adb. Try my method to restore to stock without adb by flashing a zip or snowfox's method with dd and boot img. Both threads are in dev.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Can You give me a set of instructions or something? I am VERY new and I'll probably end up making it worse.
Find snowfox's thread in dev, top 15. You will need adb..there are instructions there..
Sent from my HTC Desire using XDA App
Oddly enough a similar thing happened to me while searching and watching Youtube videos.
The longer I searched and watched videos the slower the whole thing got.
Eventually I got a black unresponsive screen.
After I was able to get back to task killer and killed everything, it still made no difference, the entire tablet was so slow it was unusable.
Did a restart and then the touch screen no longer worked.
Did another restart and everything is working fine again so far.
Not as bad as your situation, but it seems like there is a memory leak somewhere..
I powered it up this morning and left in on while I was at school all day, and it still says "Touch the Future of reading"
I'm getting depressed.
***UPDATE***
Thanks at all of you who are trying to help, but now it wont even boot up past the "Touch the Future of Reading" screen.
Also, when I hook it up to my PC it does this:
When SD is removed:
It says "new hardware found" and Then it says "Found new hardware" "RDNIS/Ethernet Gadget"
If I go to My Computer it shows no new drives.
Can anyone explain this?
I have discovered that if I plug it in without the SD card in, let the computer say "found new hardware", then hold power and the n button for about 15-20 seconds it boots to the n logo screen but then just sits there. My PC also recognizes 2 new drives "Removable Disk I:" and "Removeable Disk J:" but when I try to open them it says "Please insert a disk into drive I: or J:" At least now I have access to some drives, anyone know where to go from here??
Ign3nt said:
I powered it up this morning and left in on while I was at school all day, and it still says "Touch the Future of reading"
I'm getting depressed.
Click to expand...
Click to collapse
I'm not exactly 100 percent positive on this but It's supposed to wipe itself back to stock on the 8th failed boot. Have you tried it eight times yet?
vap0rxt said:
I'm not exactly 100 percent positive on this but It's supposed to wipe itself back to stock on the 8th failed boot. Have you tried it eight times yet?
Click to expand...
Click to collapse
It won't with Clockwork installed. I would try the restore image from the developers forum
This happened to me and this is what I did.
My NC was also getting stuck on the touch the future or reading screen. I tried rebooting it several times and it still didn't work. However, I did do this and it worked so give it a try:
1. Make sure your NC is off.
2. Plug it into a computer.
3. Hold down the n and the power button for about 20 seconds.
4. When the ghetto menu shows up, select the first option to reboot.
5. Wait a while for it to boot. It will stay at the touch the future of reading screen for a while, but don't give up; it will boot up fully.
6. Try again if it stays at the touch the future screen for more than 1 minute.
7. If it still doesn't work. try something else
I did this before doing anything more dramatic and it booted right up.
Thanks zen5200 - those steps worked perfectly for me.
Time for some words of wisdom:
If you can't fix something your messing with, then don't mess with it.
Ive got an issue with my CWM installation on my thrill.
Im got SDK downloaded with ADB.
I downloaded the Recovery.img file.
cmd prompt
adb push recovery.img /data
is says data sent
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
rm /data/recovery.img
reboot
Everything goes through likes its working, i get data sent after the commands. but CWM isnt on there.
I have tried prolly 100 times to reboot to recovery.
ive held vol- and 3d then power. until the lg logo pops on then off and i release the power, but hold the other 2. nothing. except i get a vibrate at the beginning of holding all 3.
ive tried releasing power when i see the LG sign. nothing.
ive tried both combos with just vol - adn with vol+ and with vol-+ and vol+-3d
nothing puts this thing into recovery mode. I have Rom manager on the phone but im not using it for this.
i rooted with super one click. and i have the drivers. as i can see device listed and talk with it etc. any hints? helps?
Hook it up to your computer and manually put it on your phone by drag and drop it
Then use terminal on phone for rest
To get into recovery I hold volume down. .. then push and hold power until it turns on.. takes 3 to 5 seconds
thetanurucka said:
Ive got an issue with my CWM installation on my thrill.
Im got SDK downloaded with ADB.
I downloaded the Recovery.img file.
cmd prompt
adb push recovery.img /data
is says data sent
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
rm /data/recovery.img
reboot
Everything goes through likes its working, i get data sent after the commands. but CWM isnt on there.
I have tried prolly 100 times to reboot to recovery.
ive held vol- and 3d then power. until the lg logo pops on then off and i release the power, but hold the other 2. nothing. except i get a vibrate at the beginning of holding all 3.
ive tried releasing power when i see the LG sign. nothing.
ive tried both combos with just vol - adn with vol+ and with vol-+ and vol+-3d
nothing puts this thing into recovery mode. I have Rom manager on the phone but im not using it for this.
i rooted with super one click. and i have the drivers. as i can see device listed and talk with it etc. any hints? helps?
Click to expand...
Click to collapse
Sent from my LG-P925 using XDA App
Try using root explorer and setting data permissions to all checked for read and write. And when going into cwm I release all buttons one the phone vibrates.
Sent from my LG-P925 using xda premium
just wait... a guy made a one click cwr installer he just has to post it.
Sent from my LG Thrill OC'd
ive tried manually dropping the file, same thing. the recovery file is transfered i have seen it. I have used rom manager and set the permissions all on.
really waiting for that one click lol
ok so it does go to your data folder? you have seen it in the /data folder? do you have the mmcblk0p6.backup file in /sdcard? if those two things are happening then it should be working. when you try to get into recovery it just goes to stock recovery or nothing at all? can you post a screenshot or copy paste the output in cmd here so we can take a look at it.
...fighting ninjas at night, talkin' about this and that.
I am having a similar issue like you too, thetanurucka.. It is very frustrated. Hope there is a easier way.
Look for my thread in dev section... easieast way to install clockwork mod recovery... takes two minites
Sent from my LG-P925 using XDA App
I installed cwm using ROM manager.
Sent from my LG-P920 using xda premium
This release has been out in the wild for several days now for the Rezound. Everyone who has gotten it to work reports root lasting much longer than previous methods. I am glad that it is working out for others. This should also work on other devices, such as the Vivid and that is why I am posting it here. There is nothing about it that makes it work specifically for the Rezound.
It still uses zergrush and absolutely does not provide any other capability than other temp roots. (Although some people have reported root apps see root better so it might actually be better). The only difference is I have the things relating to root (ie su,busybox, etc) stored in a ramdisk that lasts alot longer (I have not seen of a report of it being lost before a reboot yet) than things "written" or linked to /system. This is because we still have /system write locked so when we write things to it (like the original zergrush implementation) it gets forgotten after while.
Your mileage may vary. I am obviously not responsible for bricks, data loss, etc if you use this. I and others have used it for about a week and it has been fine.
To use:
0) Make sure superuser isn't installed
1) Reboot phone (full reboot), make sure usb debugging is on.
2) Plug in phone in charge only mode to PC.
3) Kill everything in the built in task manager, then go back to the rosie home screen.
4) Extract zip and doubleclick temproot.bat
5) There is a 20 second time out at the beginning just in case you forgot to plug in your phone, etc so you have time to cancel the process before it starts. To skip it just hit enter on the keyboard or wait the 20 seconds.
6) Hit the thanks button (bottom left of this post) if you like it!
Let me know if you like it better or if something bad happens so I can take it down. Lets hope we get S-Off soon and don't have to deal with this temp root **** anymore.
Troubleshooting:
1) Bootlooping? Pull the battery. If you still are boot looping, an RUU restore may be necessary. I believe this has only happened to one user and it was likely a result of something that was done AFTER root and not directly caused by this program.
2) Just not working? Reboot both your PC and Phone. If ADB cannot see your phone, it is not a fault of the program. If you haven't gotten other temp root methods to work, it is likely this one won't either.
con247 said:
This release has been out in the wild for several days now for the Rezound. Everyone who has gotten it to work reports root lasting much longer than previous methods. I am glad that it is working out for others. This should also work on other devices, such as the Vivid and that is why I am posting it here. There is nothing about it that makes it work specifically for the Rezound.
It still uses zergrush and absolutely does not provide any other capability than other temp roots. (Although some people have reported root apps see root better so it might actually be better). The only difference is I have the things relating to root (ie su,busybox, etc) stored in a ramdisk that lasts alot longer (I have not seen of a report of it being lost before a reboot yet) than things "written" or linked to /system. This is because we still have /system write locked so when we write things to it (like the original zergrush implementation) it gets forgotten after while.
Your mileage may vary. I am obviously not responsible for bricks, data loss, etc if you use this. I and others have used it for about a week and it has been fine.
To use:
0) Make sure superuser isn't installed
1) Reboot phone (full reboot), make sure usb debugging is on.
2) Plug in phone in charge only mode to PC.
3) Kill everything in the built in task manager, then go back to the rosie home screen.
4) Extract zip and doubleclick temproot.bat
5) There is a 20 second time out at the beginning just in case you forgot to plug in your phone, etc so you have time to cancel the process before it starts. To skip it just hit enter on the keyboard or wait the 20 seconds.
6) Hit the thanks button (bottom left of this post) if you like it!
Let me know if you like it better or if something bad happens so I can take it down. Lets hope we get S-Off soon and don't have to deal with this temp root **** anymore.
Troubleshooting:
1) Bootlooping? Pull the battery. If you still are boot looping, an RUU restore may be necessary. I believe this has only happened to one user and it was likely a result of something that was done AFTER root and not directly caused by this program.
2) Just not working? Reboot both your PC and Phone. If ADB cannot see your phone, it is not a fault of the program. If you haven't gotten other temp root methods to work, it is likely this one won't either.
Click to expand...
Click to collapse
Just don't execute the program again after you have done it once, or it will boot loop the vivid to high hell. And you'll have to do a factory reset.
Sent from my HTC PH39100 using xda premium
Did that just happen to you? There is a 20 second timeout for a reason...
Is there a possibility in making a Mac or Linux friendly version?
Thank
Drew
Sent from my HTC PH39100 using xda premium
drewdatrip said:
Is there a possibility in making a Mac or Linux friendly version?
Thank
Drew
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
If you know how to use adb on Mac or Linux you can just run the equivalent command one by one
Sent from my ADR6425LVW using XDA App
Code:
timeout /T 20
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
adb push zergRush /data/local/
adb shell chmod 755 /data/local/zergRush
adb shell /data/local/zergRush
adb wait-for-device
adb shell sleep 1
adb remount
adb shell mkdir /system/xbin
adb shell mount -t tmpfs none /system/xbin
adb push busybox /system/xbin
adb shell chmod 4755 /system/xbin/busybox
adb push su /system/xbin/su
adb shell chmod 4755 /system/xbin/su
adb shell cd /system/xbin
adb shell /system/xbin/busybox --install -s /system/xbin
adb install Superuser.apk
Does nothing different from the original scripts that were posted here a month ago.
Read my OP bud. I have downloaded all of the ones posted in your Vivid section and made sure. This one stores the root to a ramdisk that lasts until a reboot instead of /system rw mount going away after a short time.
I had a problem pushing this to the phone at first. Then I made sure the screen didnt time out and everything worked fine for me....just a little FYI incase someone runs into this problem as well.
Thanks
Didn't work for me.
I followed the instructions to the letter, and when I ran the batch file, there was no 20-second wait; it started immediately. It found the phone, went through the "sending speedbots" or whatever, and then rebooted the phone. It then re-ran ADB with "wait-for-phone" and the phone got stuck in a bootloop. I kept it connected to the PC and did a battery pull, and as the Beats Audio logo came up during boot, the command window on my PC flashed some more text and then closed. I let the phone completely boot and tried to run Titanium Backup and I get an error indicating it doesn't have root access. Any thoughts?
BTW - running Windows XP on a Dell Optiplex 755 with 4GB of RAM.
UPDATE - I tried performing the whole process again, and it ran for about 10 seocnds then just closed. So, I tried again, and it went through the process, up to rebooting my phone and indicating "wait-for-device," but the phone never completely shut down; it hung at that shutdown point where the entire screen is black but you can see a bit of lighting. So I did another battery pull and turned the phone on again, and after about 15 seconds, the command window scrolled a bunch more stuff and then closed and the phone continued to boot. It did manage to boot this time without a battery pull and no loops, and SU is there, but when I run Titanium Backup, I still get a "phone not rooted" error.
Looks like I'm waiting for perm root. Thanks for your work though. I'm glad it worked for others. Viva la Android!!!!
FYI: I did disable bloatware using a script, within the same command prompt window right after achieving temporary root.
The bloatware APPS and widgets remain disabled even after full reboots, including a battery pull.
I'm very grateful to temporary root, since it allows to disable most of the pre-installed bloatware.
Went from bad to worse.
I ran this on my phone last night, and even though it didn't temp root my phone, it still ran fine for the rest of the night and all day today. I decided to reboot the phone before I went to bed and now I am stuck in some kind of loop. The phone actually boots to the lock screen, and I can unlock it, but some of the icons on my homescreen don't load and the phone becomes unresponsive after about 10 seconds and then reboots. It's done this about 10 times and a battery pull does not resolve the issue. Help?
Have you tried a factory reset ? After that it may allow you to run the temp root. At least that is what happened once when I tried it.
Well through trial and error, I have found out several things...
1. The temp root that comes with the Rezound Clean Tool is the only temp root tool I can get to work.
2. Even if you have BT turned on before using the Rezound Clean Tool, turning it off permanently disables it until a reboot is done.
3. It is common for the Rezound to suddenly start boot looping, even if you haven't done any rooting or anything. This is caused by the connection type in Phone Properties randomly changing to a type that is incompatible with the Verizon SIM. (Google search "rezound boot loop" and you'll find the fix quite easily.) Also, removing the battery cover may disable the antenna but only a SIM-less boot will stop the boot looping so that the communication type can be set back to what it should be.
4. I still love this phone. It is the best phone on the market today; it has the fastest processor available from any carrier and has the most internal memory of phones that allows for removeable storage.
Thanks to all the devs for their hard work - I can't wait for perm root and custom ROMs!!!!
My wife was using her moto x4 to take pictures yesterday and apparently used up almost all her storage space. she got a message saying such and that some apps won't work properly until storage is freed up. She was able to take a couple more pictures but when she tried to text them to someone she couldn't open up hangouts. She rebooted her phone and now its stuck in a bootloop. Won't go past the Android One logo, and restarts after a few seconds. I've been able to get to recovery mode where I thought there used to be a delete cache option, but the only thing I saw was data/factory reset and I wanted that to be the last option since my wife doesn't want to lose her pictures of our kids. They weren't backed up to photos yet because we weren't on wifi. I have used ABD in the past and found a command to delete cache "fastboot erase cache" but that didn't help. I did also tried Mount /system and after doing that the first try it blipped a Motorola logo after the Android One but then went immediately back to bootloop and not getting past Android One.
Is it possible to pull the pictures off her device without being able to boot?
Any ideas to make it boot without doing a factory reset? I assume this is a storage issue but maybe just big coincidence?
I have the Motorola USB utility on my computer, and the device is stock Android 8.1, stock recovery and not rooted or anything.
Thanks,
Richard
boot back into recovery and adb pull the pictures.
so, you boot into recovery..then do adb shell.
then cd /sdcard/DCIM
do ls
you should see another folder or the pictures and videos.
then do exit to come out of adb shell and follow this to pull the folder
https://stackoverflow.com/questions...pull-all-files-of-a-folder-present-in-sd-card
munchy_cool said:
boot back into recovery and adb pull the pictures.
so, you boot into recovery..then do adb shell.
then cd /sdcard/DCIM
do ls
you should see another folder or the pictures and videos.
then do exit to come out of adb shell and follow this to pull the folder
Thanks for the quick reply. I get an error: no devices/emulators found. I don't think my wife has USB debugging enabled. Any other options?
Thanks,
Richard
Click to expand...
Click to collapse
when did you get the error?
Sorry, it occurs at the first step, the adb shell command.
Granted, my experience with using adb is limited but my understanding was that you can't use it unless USB debugging is enabled. Playing around a bit more, my computer doesn't seem to recognize the usb connection unless I chose apply update from ADB but I think that only allows sideloading. The adb shell didn't work and adb devices empty there as well.
Thanks,
Richard
rjschwar said:
My wife was using her moto x4 to take pictures yesterday and apparently used up almost all her storage space. she got a message saying such and that some apps won't work properly until storage is freed up. She was able to take a couple more pictures but when she tried to text them to someone she couldn't open up hangouts. She rebooted her phone and now its stuck in a bootloop. Won't go past the Android One logo, and restarts after a few seconds. I've been able to get to recovery mode where I thought there used to be a delete cache option, but the only thing I saw was data/factory reset and I wanted that to be the last option since my wife doesn't want to lose her pictures of our kids. They weren't backed up to photos yet because we weren't on wifi. I have used ABD in the past and found a command to delete cache "fastboot erase cache" but that didn't help. I did also tried Mount /system and after doing that the first try it blipped a Motorola logo after the Android One but then went immediately back to bootloop and not getting past Android One.
Is it possible to pull the pictures off her device without being able to boot?
Any ideas to make it boot without doing a factory reset? I assume this is a storage issue but maybe just big coincidence?
I have the Motorola USB utility on my computer, and the device is stock Android 8.1, stock recovery and not rooted or anything.
Thanks,
Richard
Click to expand...
Click to collapse
I feel horrible for you. The one pro of iOS is that bootloops are less often but can happen (happened on iPad 6 but reinstalled iOS without data loss). I will always root my phone and install TWRP out of these horror stories. Do you still have the issue?