ok. I finally decided to root my note 2. i have rooted many phones before, so i am familiar with the process. I used the one click verizon method posted here. Rooted fine. Booted into TWRP (first time using this recovery). wiped cache, etc. Installed rom (paranoidandroid 3). froze at boot screen.
went back to recovery tried to reinstall. same thing. deleted everything through twrp and tried to mount internal card. Nothing. PC wont see it. I can adb and see the device and see it in device manager, but cant see the cards in my computer. can not mount through adb using mount /sdcard, mount /data, etc, says device is busy. cant boot into bootloader to reinstall CWM recovery, etc.
Any suggestions?
Phyllip J FRy said:
ok. I finally decided to root my note 2. i have rooted many phones before, so i am familiar with the process. I used the one click verizon method posted here. Rooted fine. Booted into TWRP (first time using this recovery). wiped cache, etc. Installed rom (paranoidandroid 3). froze at boot screen.
went back to recovery tried to reinstall. same thing. deleted everything through twrp and tried to mount internal card. Nothing. PC wont see it. I can adb and see the device and see it in device manager, but cant see the cards in my computer. can not mount through adb using mount /sdcard, mount /data, etc, says device is busy. cant boot into bootloader to reinstall CWM recovery, etc.
Any suggestions?
Click to expand...
Click to collapse
A lot of the time when booting a rom and it freezes during the boot you can do a battery pull and then power the phone back on again and it'll work.
If you can still get into recovery you could flash CWM, I take you meaning you cant boot into bootloader as meaning you can't boot into recovery though....
Why were you trying to mount the internal storage in TWRP? It's automatically mounted for me every time I boot into recovery.
Can you reach Download Mode? If so you may want to use Odin to go back to stock, using droidstyles guide, and start over again. When you get back to stock just root and unlock again and try this again.
Sent from my SCH-I605 using XDA Premium HD app
Phyllip J FRy said:
ok. I finally decided to root my note 2. i have rooted many phones before, so i am familiar with the process. I used the one click verizon method posted here. Rooted fine. Booted into TWRP (first time using this recovery). wiped cache, etc. Installed rom (paranoidandroid 3). froze at boot screen.
went back to recovery tried to reinstall. same thing. deleted everything through twrp and tried to mount internal card. Nothing. PC wont see it. I can adb and see the device and see it in device manager, but cant see the cards in my computer. can not mount through adb using mount /sdcard, mount /data, etc, says device is busy. cant boot into bootloader to reinstall CWM recovery, etc.
Any suggestions?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2196891
Related
i am bricked with the kind of brick where i can boot into recovery and use fastboot, but cant boot into a rom. i tried using fastboot to reinstall twrp, but my internal sd is wiped and i am trying to push a rom to flash using adb push but it gives and error- read only file system even though i am pushing it to /sdcard. i tried going into adb shell and mount -o remount rw /sdcard, which works for small files, but the rom ive tried to push still has the same error any ideas? i really wish i backed up with nvflash, never thought i would get myself into this mess...
i am using this (http://forum.xda-developers.com/showthread.php?t=1773280) and it appears to be working... am installing the stock .28 blob...
am booting now... waiting... please... work... didnt work. ill try a different rom
I had a similar issue where I was stuck in CWM Recovery after selecting "Reboot to Recovery" from EOS ROM. I followed these steps: (http://forum.xda-developers.com/showthread.php?t=1514088) and my prime fully booted once again.
Have you looked into that thread?
i had similar problem after trying to update my prime. instead of updateing it booted recovery and keept doing that. the thread from last post helped me to fix this and flash a fresh rom.
ya i got it fixed in the end from that thread but i had to do extra steps because wiping data alone didnt do the trick. i had to go into fastboot, flash the linux boot img, flash a new recovery, and then because i wanted to go as close to stock as i could i flashed a stock rom for unlocked devices, then i did a data wipe and it booted. thanks for your help
I recently purchased a used atrix. It worked fine but I wanted to try a different ROM.
Fast forward a little bit and I had rooted, unlocked the bootloader, and setup a recovery.
I downloaded the Neutrino CM7 ROM and put it on my external SD card (possible mistake #1, the thread says use internal).
I went into the recovery on the phone, made a backup of the phone and then went about wiping dalvik, cache, factory-reset, etc.
I then flashed the ROM from zip and some of the addons from the thread. When I went to reboot, the phone sits at the "M Dual Core" screen (I gave it plenty of time for any kind of background "first-boot" stuff and even removed the battery and let it try again). I have wiped and reinstalled the ROM about 4 times now.
I then decided to just go back to my original config and tried to restore from the backup (after wiping). Now after restoring the backup I either get a bootloop, or it will just sit at the "M Dual Core" screen again.
My only solace was that I was able to get into fastboot from the phone, but now after many attempts, it displays "Battery is too low to flash" if I try to enter fastboot. The phone doesn't seem to charge because it just sits at the "M Dual Core" screen whether its plugged into the wall or otherwise.
I am stuck on what to do next. I have access to the recovery, so I thought of trying another ROM, but how can I get those files to the device?
tgeo said:
how can I get those files to the device?
Click to expand...
Click to collapse
You could plug your microSD card to a computer and copy the ROM you want to it. Alternatively, I once saw an option in clockworkmod recovery to mount the sdcard or the internal storage with the phone plugged to a computer via USB. If I recall it correctly, this option is located in the 'mounts and storage' section of the recovery.
MaxK47 said:
You could plug your microSD card to a computer and copy the ROM you want to it. Alternatively, I once saw an option in clockworkmod recovery to mount the sdcard or the internal storage with the phone plugged to a computer via USB. If I recall it correctly, this option is located in the 'mounts and storage' section of the recovery.
Click to expand...
Click to collapse
Thanks. This worked perfectly!
tgeo said:
Thanks. This worked perfectly!
Click to expand...
Click to collapse
And also update your recovery to romracer or cwm touch, you will again get stuck at M logo with an outdated recovery.
I was trying to flash CM and made the stupid mistake of only flashing the boot.img and now my dna repeatedly restarts and won't get past the droid light thing. The rom files and gapps are not on my sd card. I can't get a connection to adb and my computer doesn't see the device. ADB will recognize the device at one part during the bootloop but says "offline" right next to it. I'm s-off (moonshine), rooted, and have CWM recovery. I've tried wiping the cache, dalvik cache, and tried a factory reset. None of those worked. If I lose this phone I'm really screwed, is there no way to get out of this?
mistahthron said:
I was trying to flash CM and made the stupid mistake of only flashing the boot.img and now my dna repeatedly restarts and won't get past the droid light thing. The rom files and gapps are not on my sd card. I can't get a connection to adb and my computer doesn't see the device. ADB will recognize the device at one part during the bootloop but says "offline" right next to it. I'm s-off (moonshine), rooted, and have CWM recovery. I've tried wiping the cache, dalvik cache, and tried a factory reset. None of those worked. If I lose this phone I'm really screwed, is there no way to get out of this?
Click to expand...
Click to collapse
Boot in CM recovery and there is an option to connect the phone to the computer as a USB. There you can put the rom files etc and flash it again.
abhi897 said:
Boot in CM recovery and there is an option to connect the phone to the computer as a USB. There you can put the rom files etc and flash it again.
Click to expand...
Click to collapse
I ended up fixing the problem by finding out what sideloading is and sideloading the rom/gapps. Thanks for the help though!
Hello,
I will highly appreciate if somebody can help me.
I wanted to clear my Prime TF201 that's why I used the "Reset device" option in the Menu. After device started again on the screen I see a Clockworkmod recovery v5.8.2.0 menu. And here begins the problem I can't do anything.
When I choose reboot it restarts and I'm back at the main Menu.
When I choose install update from SD card I see only files from the internal memory of the device (although I have deleted them). I've tried to connect to PC but adb said: no device connected.
Generaly I's stuck- no SD card, no USB can be used for recovery file instalation or something like that.
Please help me :crying:
To make this clear: CWM works? Then I suppose you're not fubar.
Have you tried if it shows up in fastboot?
Xerxes-3.0 said:
To make this clear: CWM works? Then I suppose you're not fubar.
Have you tried if it shows up in fastboot?
Click to expand...
Click to collapse
Hi, I don't think it is working since I only see the menu of CWM and none of the options is working. How to try fastboot?
Follow this guide, it worked for me.
Get your downloads and the appropriate ROM and start with the "fastboot devices", then it should show up.
TWRP worked for me and CWM didn't, this is why I recommend it. You can just flash it on top of CWm and it will replace it.
Remember to wipe Dalvik, System, Cache ad Data before installing the other ROM.
/e: I should mention that it did work when I had a non-booting CWM first.
I am trying to install an AOSP rom and stuffed it up. Here's what I did so far. I normally format the internal sdcard when I flash a new daily driver but forgot I haven't put in an external sdcard.
I am currently now in TWRP with no OS. I want to turn the phone off and put in an exernal sdcard to flash a rom. I am just afraid if I turn it off now I won't be able to get back into recovery.
Just wanted to check if this is possible, otherwise I'll leave it on and attempt a sideload and flash a rom that way (still reading up on this if anyone is familiar would appreciate any advice.)
With Windroid
i) Flashed TWRP
ii) Installed SU
With TWRP
formatted dlavik cache etc etc and, very unfortunately, sdcard as well.
Where I am at with sideload
Trying to follow a tutorial (can't link)
Currently I am at the part where I am installing the sdk bundle to get the adb executable.
change to usb storage mode in twrp, and plug to your pc, copy rom to phone, unmount usb storage mode, flash the rom
Pendekar7 said:
change to usb storage mode in twrp, and plug to your pc, copy rom to phone, unmount usb storage mode, flash the rom
Click to expand...
Click to collapse
Sweet much easier than I thought, what a time to be alive...
ROM currently installing, hope all is good.
Thanks again!
Edit: Also, is it weird that when I press reboot system in TWRP (after the ROM installed) nothing happens? It just stays there. This also happened when I installed SU, I had to take my battery out to reset it and SU was there when it booted back on.
I previously used CWM so a bit new to TWRP.
frogduck said:
Sweet much easier than I thought, what a time to be alive...
ROM currently installing, hope all is good.
Thanks again!
Edit: Also, is it weird that when I press reboot system in TWRP (after the ROM installed) nothing happens? It just stays there. This also happened when I installed SU, I had to take my battery out to reset it and SU was there when it booted back on.
I previously used CWM so a bit new to TWRP.
Click to expand...
Click to collapse
yeah that bug, sometime twrp will freeze while select reboot via twrp menu, happened to me too