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
Related
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
DThimself said:
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
Click to expand...
Click to collapse
Just to be clear:
1. You successfully booted into CM7 after installing it? Then you went to install gapps and couldn't get past the boot logo?
2. Or were you trying to install gapps right after flashing CM7 (i.e. stayed in recovery and did not boot into OS)?
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
DThimself said:
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
Click to expand...
Click to collapse
Hmm, well that definitely rules out an outdated recovery, which is what usually causes people to get stuck at the bootlogo. If you can't even re-install after wiping, then I would just restore a backup and start over.
Maybe try getting a fresh download of the gapps package. You may have possibly had a corrupted download?
Are you running CWM recovery or Rom Racer's? I had a problem where I was stuck at the boot logo while using CWM (latest one) but when I switched to Rom Racer's recovery and flashed everything worked.
I ended up having to use an older CWM recovery and wiping the phone and SD card with a lot of help from a friend of mine whos knows more about this than i do
DThimself said:
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
Click to expand...
Click to collapse
How did you prep for the CM7 and GAPPS flash? If you did not wipe correctly, there was a first indication you might have problems.
How long did you wait after the phone first booted into CM7? If you rebooted as soon as the OS was up, that's more than likely your issue. You need to wait 10 minutes to let the phone build system files after flashing.
Also, an older CWM would have, if anything, caused more problems. If you had the latest ROM Manager or Romracer CWM then that was definitely not your problem, so your friend using an "older" CWM wasn't helping any.
DThimself said:
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
Click to expand...
Click to collapse
I have run into this issue before when flashing any apps that update an app that is already there. I have found that a Dalvik wipe is needed before the flash. It is good practice to wipe Dalvik at least when flashing anything that changes the System Files. I also wipe the cache Partition before any flashes just to help mitigate issues like this.
Hi all, I have tried to flash all of the roms available and none aside from aokp 6.11 will boot. TWRP seems to flast the rom but I get a boot loop. Tried the new version of aopk 11.16 and same issue, I get a boot loop. Within TWRP I cannot factory reset as TWRP cannot mount /cache however erasing all partitions using fastboot does not seem to make any difference (I am not sure if erasing using fastboot is the same as the factory reset through TWRP). I have tried to flash back to stock and I get the green robot but then the device just reboots. To get back to stock I've extracted the recovery.img from the update zip and flashed using fastboot, then put the dload folder on the sdcard etc and as said I just ge a reboot.
The only rom that works is aokp 6.11 and even then wifi does not work and the power button just reboots the device.
I am about to give up. I've spent hours messing with the thing but to no avail! Does anyone have any ideas/solutions?
So... I got my HTC One today and it's been a very difficult experiance. I am quite a newbie when it comes to rooting and such but I managed to unlock my bootloader (with the exception that it shows TAMPERED at the top) then proceded to flash TWRP through fastboot. TWRP wouldn't mount /data, /sdcard, etc... it wouldn't work. A little bit of searching led me to flash CWM instead and that seemed to work.
In CWM I wiped data/factory reset, then flashed SuperSU, then flashed CleanROM, then flashed BulletKernel, and finally reboot. Now I'm stuck in a bootloop and when I go to my bootloader and try to enter recovery it reboots, shows the CWM logo then reboots my phone. I tried re-flashing CWM via fastboot to no avail.
TL;DR: Phone is in bootloop and won't even boot into recovery
Any help would be much appreciated,
Thank you!
EDIT: Had a feeling it was due to the fact I didn't clear cache/dalvik cache before rebooting. I erased my cache via fastboot and voila it booted into recovery!
OrangeFever said:
So... I got my HTC One today and it's been a very difficult experiance. I am quite a newbie when it comes to rooting and such but I managed to unlock my bootloader (with the exception that it shows TAMPERED at the top) then proceded to flash TWRP through fastboot. TWRP wouldn't mount /data, /sdcard, etc... it wouldn't work. A little bit of searching led me to flash CWM instead and that seemed to work.
In CWM I wiped data/factory reset, then flashed SuperSU, then flashed CleanROM, then flashed BulletKernel, and finally reboot. Now I'm stuck in a bootloop and when I go to my bootloader and try to enter recovery it reboots, shows the CWM logo then reboots my phone. I tried re-flashing CWM via fastboot to no avail.
TL;DR: Phone is in bootloop and won't even boot into recovery
Any help would be much appreciated,
Thank you!
Click to expand...
Click to collapse
Boot into bootloader. Then do fastboot erase cache. Then try rebooting. If you can get into recovery but not ROM, reflash the ROM. If you can't even get into recovery still, try reflashing recovery. Fastboot flash recovery recovery.img. Then try getting into recovery and reflashing.
Sent from my HTC One
phositadc said:
Boot into bootloader. Then do fastboot erase cache. Then try rebooting. If you can get into recovery but not ROM, reflash the ROM. If you can't even get into recovery still, try reflashing recovery. Fastboot flash recovery recovery.img. Then try getting into recovery and reflashing.
Sent from my HTC One
Click to expand...
Click to collapse
Thank you!
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
Hello,
I have a Kobo 10HD and rooted and installed CWM v6.0.5.1. I made a backup before and then installed Titanium Backup update.zip. Installation of that zip caused a bootloop (back to CWM). No problem, I thought, I can just restore the backup I made. No dice. I tried to restore the backup and still bootlooping. I even tried to installed the stock ROM ZIP and it fails with the message: (from recovery.log):
nv_copy_blob_file: couldn't get the device path
script aborted (no error message)
script aborted (no error message)I:Legacy property environment disabled.
E:Error in /data/media/0/macallan-ota-932.zip
(Status 7)
Installation aborted.
I have read that some people have had success installing this zip using stock recovery, but I have no idea how to get stock recovery.
Also, I noticed using adb shell that CWM does actually put all the files back into system and other areas during the restore. Upon reboot, and subsequent bootloop, the system files are gone. It must have something to do with an automatic script that is running after restore.
SOLVED!
zhzhou said:
Hello,
I have a Kobo 10HD and rooted and installed CWM v6.0.5.1. I made a backup before and then installed Titanium Backup update.zip. Installation of that zip caused a bootloop (back to CWM). No problem, I thought, I can just restore the backup I made. No dice. I tried to restore the backup and still bootlooping. I even tried to installed the stock ROM ZIP and it fails with the message: (from recovery.log):
nv_copy_blob_file: couldn't get the device path
script aborted (no error message)
script aborted (no error message)I:Legacy property environment disabled.
E:Error in /data/media/0/macallan-ota-932.zip
(Status 7)
Installation aborted.
I have read that some people have had success installing this zip using stock recovery, but I have no idea how to get stock recovery.
Also, I noticed using adb shell that CWM does actually put all the files back into system and other areas during the restore. Upon reboot, and subsequent bootloop, the system files are gone. It must have something to do with an automatic script that is running after restore.
Click to expand...
Click to collapse
After a few more hours of fiddling, I was able to get the device back up. I wiped absolutely everything manually with CWM (format /X) instead of Wipe/Factory Reset. The factory reset was not clearing the SD card, but format/data and /data/media cleared it. I then applied the stock zip that is available via adb sideload. Installation failed with the same error, but I rebooted with the adb reboot command. The device booted back into Kobo stock requiring several updates. It actually got stuck repeating one update several times until I booted back into stock recovery and cleared data and did a factory reset. The update applied correctly and then another upgrade came (a total of three upgrades). I rooted again and we are back in business.
For some reason, I think the key step was manually wiping /data/media. I'm not exactly sure why this would cause a bootloop for CWM restore. Anyway, I hope this helps someone else who may run into a similar issue.
Hi zhzhou!
Just a quick question:
do you happen to remember if stock recovery for Kobo was CWM? I'm in process of restoring stock ROM +recovery and little bet surprised to see CWM after flashing stock recovery
Thanks a lot!
zhzhou said:
After a few more hours of fiddling, I was able to get the device back up. I wiped absolutely everything manually with CWM (format /X) instead of Wipe/Factory Reset. The factory reset was not clearing the SD card, but format/data and /data/media cleared it. I then applied the stock zip that is available via adb sideload. Installation failed with the same error, but I rebooted with the adb reboot command. The device booted back into Kobo stock requiring several updates. It actually got stuck repeating one update several times until I booted back into stock recovery and cleared data and did a factory reset. The update applied correctly and then another upgrade came (a total of three upgrades). I rooted again and we are back in business.
For some reason, I think the key step was manually wiping /data/media. I'm not exactly sure why this would cause a bootloop for CWM restore. Anyway, I hope this helps someone else who may run into a similar issue.
Click to expand...
Click to collapse
Stock was definitely not CWM. It was a long time ago and I no longer have the device, but I think CWM was still present after restoring stock. I think you'll need fastboot if you want to flash the stock recovery image back on. But why do that? TWRP is now available for the device.
Thanks for quick reply! I had CM on it but had some artifact issues so wanted to revert to full stock, even recovery
zhzhou said:
Stock was definitely not CWM. It was a long time ago and I no longer have the device, but I think CWM was still present after restoring stock. I think you'll need fastboot if you want to flash the stock recovery image back on. But why do that? TWRP is now available for the device.
Click to expand...
Click to collapse