Ok so last night when i flashed ace42's hero everything was going ok wasnt a slow hero but i wanted to go back to super D. My dumbasz forgot to nandroid and when i try to flash an rom it stays on the 1st splash screen i could acces recovery and bootloader so its not a hard brick. Ive tried every thing form reflashing the radio and spl to the bootloader and back. Shoooot i even tried using DREAIMG.Nbh and the stock cupcake but still nothing nada. Any ideas what could be wrong? Im using amons recovery 1.6.2 btw
did you try wiping? Usually after you do a nandroid/switchrom/bart it's best to wipe before you flash.
Try This:
Code:
Wipe Data/Factory Reset
Wipe Dalvik Cache
Wipe Ext Partition
Repair EXT
Flash New Rom
See if that doesn't help.
....
nolimit78 said:
did you try wiping? Usually after you do a nandroid/switchrom/bart it's best to wipe before you flash.
Try This:
Code:
Wipe Data/Factory Reset
Wipe Dalvik Cache
Wipe Ext Partition
Repair EXT
Flash New Rom
See if that doesn't help.
Click to expand...
Click to collapse
Yes ive tried all that sadly no success=/ it says error wipe ext via console or repair ext via console im looost
Go to recovery
Console, format your sdcard and repartition
then put the update file
and flash the rom.
Ugh
peshal said:
Go to recovery
Console, format your sdcard and repartition
then put the update file
and flash the rom.
Click to expand...
Click to collapse
Ive tried all of that itll hang on the g1 screen for hours
Alex530 said:
Ive tried all of that itll hang on the g1 screen for hours
Click to expand...
Click to collapse
Can you fastboot the phone? If you can do that then I recommend flashing through fastboot a boot and system image of what was previously working.
Just a thought, but did you try flashing the HTC recovery first?
I just had this same problem. I did a complete wipe. then flashed DRC83_base_defanged.zip (found here: http://www.mediafire.com/?nymkxjmndzd)when it was done flashing I flashed cyanogens latest with no reboot in between. I am now back up and running.
Backup the contents of your FAT partition on your SDCARD to your computer.
Reformat you SDCARD.
Repartition the SDCARD using Amon_RA's recovery (ext3 or ext4 partiton).
Reboot back into recovery.
Wipe your data/dalvik-cache.
Restore all of your FAT content originally saved from your SDCARD.
flash the DRC83_base_defanged.zip and then CM rom immediately following.
plug your device into your computer (if it's not there already) and use ddms or adb shell logcat to get a logcat and see if it appears to be repeating if your phone doesn't boot then copy the logcat and post it here.
Good luck.
I have installed semaphore cwm on a stock Galayxy S 2.3 phone. I can get into recovery mode and also download mode. However, when I try and boot the phone it just flashes up the usual Glxy S boot screen and goes no further. I cannot work out how to get Cyanogenmod 10.1.2 zip on to the /sd card when I can't boot the phone. I have put the zip on to the external sd, but that is no good as CWM doesn't see the external SD.
I am getting desperate as it is my daughter's phone and she will not be happy if I have bricked it. I am running linux mint 14.
Ozdemon said:
I have installed semaphore cwm on a stock Galayxy S 2.3 phone. I can get into recovery mode and also download mode. However, when I try and boot the phone it just flashes up the usual Glxy S boot screen and goes no further. I cannot work out how to get Cyanogenmod 10.1.2 zip on to the /sd card when I can't boot the phone. I have put the zip on to the external sd, but that is no good as CWM doesn't see the external SD.
I am getting desperate as it is my daughter's phone and she will not be happy if I have bricked it. I am running linux mint 14.
Click to expand...
Click to collapse
To put files into sd card when you are in recovery mode, just go:
Mounts & Storage -> mount usb storage
Then put your zip file and flash it.
1 step forward and 2 steps back.
TenKoX said:
To put files into sd card when you are in recovery mode, just go:
Mounts & Storage -> mount usb storage
Then put your zip file and flash it.
Click to expand...
Click to collapse
Thank you so much for this advice. It worked. I got the phone going again and then, to my eternal shame, I did a restore on CWM. I should have done an advanced restore and only selected what I needed. So now I am back where I started, but in a worse position. CWM is displaying error messages such as failed to open /etc/recovery.fstab, can't mount /cache/recovery....I can't install from the internal sd as it can't be seen. I feel like screaming. I have tried re-installing CWM, doing a factory re-set, wiping the cache and dalvik cache, all to no avail.
I wouldn't blame you for giving up on me!
Ozdemon said:
So now I am back where I started, but in a worse position. CWM is displaying error messages such as failed to open !
Click to expand...
Click to collapse
You can use a Rescue Kit from My Android Collections to solve your problem or look in http://forum.xda-developers.com/showthread.php?p=30415128#post30415128 for a solution
You can use a Nandroid Manager app ( from google) to recover data from your backups
Up and running
xsenman said:
You can use a Rescue Kit from My Android Collections to solve your problem or look in http://forum.xda-developers.com/showthread.php?p=30415128#post30415128 for a solution
You can use a Nandroid Manager app ( from google) to recover data from your backups
Click to expand...
Click to collapse
Thanks very much. I am now up and running. You have a mighty impressive set of android software.
i have team win recover project v2.5.0.0 i went to wipe advance wipe and selected dalvik cache, cache, data and system and swipe to wipe
then i went to reboot and it mark no os installed. help?
seanpx said:
i have team win recover project v2.5.0.0 i went to wipe advance wipe and selected dalvik cache, cache, data and system and swipe to wipe
then i went to reboot and it mark no os installed. help?
Click to expand...
Click to collapse
OH MAN!!
What you think could wiping system partition mean? Exactly: you wiped your system partition and because of that, there is no more system to boot from anymore...
So go back to recovery and flash a rom of your choice. If you have no flashable rom on your sdcard, you have to sideload a downloaded zip from your pc. There are howto´s how to do that with TWRP here on XDA. Before you do that, you should update your recovery to the latest version of TWRP (2.6.3.0)http://forum.xda-developers.com/showthread.php?t=2173870&highlight=twrp
I wish you luck
SpeedyCarv said:
OH MAN!!
What you think could wiping system partition mean? Exactly: you wiped your system partition and because of that, there is no more system to boot from anymore...
So go back to recovery and flash a rom of your choice. If you have no flashable rom on your sdcard, you have to sideload a downloaded zip from your pc. There are howto´s how to do that with TWRP here on XDA. Before you do that, you should update your recovery to the latest version of TWRP (2.6.3.0)http://forum.xda-developers.com/showthread.php?t=2173870&highlight=twrp
I wish you luck
Click to expand...
Click to collapse
i do have a backup would that work if i have a usb otg cable but i dont have one is there any other way
i can not access my internal storage from pc
Look up ADB push or ADB sideload, either will get you where you want.
Don't worry, you haven't messed up your phone
Sent from my Nexus 4 using xda app-developers app
seanpx said:
i do have a backup would that work if i have a usb otg cable but i dont have one is there any other way
i can not access my internal storage from pc
Click to expand...
Click to collapse
You don't need to access internal storage. Just have ADB installed on your cpu and make sure it reads your device. Reboot into recovery go into adb sideload and push a Rom from the terminal of your computer. YouTube it for step by step process
Sent from my HTC One using XDA Premium 4 mobile app
thank u all i was able to used Quick-ADB-Pusher_v0.5 to put Android_Revolution_HD-One_30.0 and install it
I was formatting my HTC One to give it to a family member. I was going to sideload or push a rom and flash it, but twrp keeps saying it cant mount /data/ or internal storage. I got to sideload android revolution HD GPE but when it boots its asks for a password to decrypt the storage which i have never done. In twrp it still says it can't mount internal storage or data and I need help getting out of this mess. :/
xXxG0dzRAgexXx said:
I was formatting my HTC One to give it to a family member. I was going to sideload or push a rom and flash it, but twrp keeps saying it cant mount /data/ or internal storage. I got to sideload android revolution HD GPE but when it boots its asks for a password to decrypt the storage which i have never done. In twrp it still says it can't mount internal storage or data and I need help getting out of this mess. :/
Click to expand...
Click to collapse
inside TWRP select wipe and then select format data, this will however completely wipe your phone and you will need to push or sideload a new rom then flash it, try and use TWRP 2.6.3.3, it makes all the difference.
Seanie280672 said:
inside TWRP select wipe and then select format data, this will however completely wipe your phone and you will need to push or sideload a new rom then flash it, try and use TWRP 2.6.3.3, it makes all the difference.
Click to expand...
Click to collapse
I flashed CWM to see if it worked instead but still said cant mount /data and can't mount /sdcard. I formatted /data and now trying to sideload android revolution again to see if that will work. If not I will try to use TWRP 2.6.3.3. I was using 2.7.1.1 beforehand.
Also the whole reason im here is because I wiped my phone completely with TWRP. Just planned on wiping it all then sideloading a rom to give it that "new phone" sort of feel. No empty random folders and all that. No left over files.
xXxG0dzRAgexXx said:
I flashed CWM to see if it worked instead but still said cant mount /data and can't mount /sdcard. I formatted /data and now trying to sideload android revolution again to see if that will work. If not I will try to use TWRP 2.6.3.3. I was using 2.7.1.1 beforehand.
Also the whole reason im here is because I wiped my phone completely with TWRP. Just planned on wiping it all then sideloading a rom to give it that "new phone" sort of feel. No empty random folders and all that. No left over files.
Click to expand...
Click to collapse
The TWRP 2.7.x.x series all seem to have one or another problem going on with them, most users here swear by 2.6.3.3 or 2.6.3.4, however you will also find that most custom rom's require TWRP recovery over CWM.
also, don't forget to erase the cache after flashing each recovery.
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Seanie280672 said:
The TWRP 2.7.x.x series all seem to have one or another problem going on with them, most users here swear by 2.6.3.3 or 2.6.3.4, however you will also find that most custom rom's require TWRP recovery over CWM.
also, don't forget to erase the cache after flashing each recovery.
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Ended up reflashing twrp with fastboot and then flashed Android revolution HD71.1 on it. The format of data in CWM worked to fix the mounting problem I had. Twrp probably could have fixed it too if I tried wiping data again. Will remember that next time for the other HTC One I'll be doing this to in the next few days.
Hey guys!
I'm have a Nook HD+ running AOSP Nougat from amaces along with TWRP 3.0.2-0 as recovery.
(http://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269)
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?). Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Any idea how I could rescue my tablet? Thank you very much!
N0he said:
Hey guys!
I'm have a Nook HD+ running AOSP Nougat from amaces along with TWRP 3.0.2-0 as recovery.
(http://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269)
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?). Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Any idea how I could rescue my tablet? Thank you very much!
Click to expand...
Click to collapse
+1 on this, I am seeing the exact same behavior. After running a while there seems to start cascading failures of apps. Browser stopped, google play most common, MTP host stops...
TWRP hangs on the splash screen , Ive tried all (3) 3.0.2. variants.... I am running the NDE63P 7.1 build...
in my case, however, if I boot from a card into OLD Cwm, don't do anything, and then reboot from the tablet, I am then able to boot from emmc normally.
N0he said:
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?).
Click to expand...
Click to collapse
Sounds like your userdata partitions got corrupted; F2FS? Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
N0he said:
Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Click to expand...
Click to collapse
When recovery cannot mount its partitions (by default, including /data and /cache), it will hang, so you have to either build a TWRP image that doesn't attempt to use /data, or use the old CWM from the external card, which doesn't understand F2FS. The external recoveries should always boot, if nothing else is broken.
mikeataol said:
in my case, however, if I boot from a card into OLD Cwm, don't do anything, and then reboot from the tablet, I am then able to boot from emmc normally.
Click to expand...
Click to collapse
Yes, all these recoveries clear the boot count, but only after they finish booting. When TWRP doesn't finish a full boot, the system is still marked for recovery.
As a side note, I really don't understand why people insist on using (highly) experimental builds without a good understanding of how to rescue from soft-bricks…
amaces said:
Sounds like your userdata partitions got corrupted; F2FS? Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
The external recoveries should always boot, if nothing else is broken.
Click to expand...
Click to collapse
The TWRP recoveries on the SD card ddont boot, they hang as well. Only the CWM boots
I was trying to ascertain if the file system was corrupted, or if just TWRP was broken.
The rom boots and runs normally from emmc, no signs anywhere that there is corruption, except subtle hints... (change settings on an app, clear data and cache on an app, and on the successful reboot into the rom those changes don't seem to have stuck.
mikeataol said:
The TWRP recoveries on the SD card ddont boot, they hang as well. Only the CWM boots
I was trying to ascertain if the file system was corrupted, or if just TWRP was broken.
Click to expand...
Click to collapse
Right, CWM is one of the recoveries on the SD card. No recovery that supports F2FS and wants to access /data will work at this point; it just happens that CWM can skip that step.
@amaces and as you suggested, booting cwm from the card
reformatting userdata (make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata )
allowed TWRP to work again just ducky.....
Thank you for taking your time to help me!
amaces said:
When recovery cannot mount its partitions (by default, including /data and /cache), it will hang, so you have to either build a TWRP image that doesn't attempt to use /data, or use the old CWM from the external card, which doesn't understand F2FS. The external recoveries should always boot, if nothing else is broken.
Click to expand...
Click to collapse
In my case, I am unable to boot from the microSD card at all, the device always boots into the emmc recovery no matter what I do.
amaces said:
Sounds like your userdata partitions got corrupted; F2FS?
Click to expand...
Click to collapse
I did not know what F2FS is, but from googling, I assume it is something the user would have to manually set, which did not happen in my case.
amaces said:
Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
Click to expand...
Click to collapse
Is it possible to do so without access to recovery? Can you give me some directions to where I can get the info to be able to do so? Any good posts on that, or any keyword I could research around? Would fastboot work? I'm not too sure where to start.
amaces said:
As a side note, I really don't understand why people insist on using (highly) experimental builds without a good understanding of how to rescue from soft-bricks…
Click to expand...
Click to collapse
From what I have seen in the forums, I assumed having a "rescue microSD card" would make flashing ROMs fairly save, but I guess I'll stick to stable builds from now on then. But then again, doing stupid stuff does make me learn new things, and I was willing to risk bricking my tablet.
Anyways, thank you for helping me and for all your work to keep the Nooks alive!
N0he said:
In my case, I am unable to boot from the microSD card at all, the device always boots into the emmc recovery no matter what I do.
Click to expand...
Click to collapse
Hi
You should make another card using a different MicroSD. Not all cards work for booting NOOKS.
A class 4 brand name card usually works
the disk image amace has here :https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778/59738502081/1
has a CWM recovery and 2 TWRP recoveries to choose from on boot.
mikeataol said:
Hi
You should make another card using a different MicroSD. Not all cards work for booting NOOKS.
A class 4 brand name card usually works
the disk image amace has here :https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778/59738502081/1
has a CWM recovery and 2 TWRP recoveries to choose from on boot.
Click to expand...
Click to collapse
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
N0he said:
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
Click to expand...
Click to collapse
Have you checked whether adb is working while you are sitting at the splash screen for TWRP?
If yes, then you can execute the make_ext4fs command
"make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata"
to format your /userdata partition.
I was able to do this while stuck on a TWRP splash screen
this will reset your file system back to ext4, (and wipe it) . if you are going to reload one of the newer roms , you'd of course want to convert it back to f2fs before installing.
the NBD90Z 161019 build is working very well for me....
N0he said:
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
Click to expand...
Click to collapse
So, it never presents the external recovery menu, where you could select CWM before? You might need to format and re-build that SD card if that's the case.
mikeataol said:
Have you checked whether adb is working while you are sitting at the splash screen for TWRP?
If yes, then you can execute the make_ext4fs command
"make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata"
to format your /userdata partition.
Click to expand...
Click to collapse
Yes, do try this even with the eMMC recovery; ADB should be working, and you might be able format userdata if it was ext4 before. With some F2FS corruption, it's less likely to work, since it'll say /data is in use, and you can't unmount it.
mikeataol said:
if you are going to reload one of the newer roms , you'd of course want to convert it back to f2fs before installing.
Click to expand...
Click to collapse
I think you should stick to ext4 while testing these issues. I did notice more corruption with F2FS on the new kernel, but didn't have time to investigate yet.
My tablet randomly booted into the microSD card overnight while charging for some reason, and since then, I'm able to boot into the card cwm.
Trying to format the device, I get following error: /sbin/sh: make_ext4fs: not found
I looked into /sbin/sh and found mke2fs and mkfs.ext2, how should I proceed?
N0he said:
My tablet randomly booted into the microSD card overnight while charging for some reason, and since then, I'm able to boot into the card cwm.
Trying to format the device, I get following error: /sbin/sh: make_ext4fs: not found
I looked into /sbin/sh and found mke2fs and mkfs.ext2, how should I proceed?
Click to expand...
Click to collapse
I think you should format it mkfs.ext2 then, ....
that should allow you to boot into the internal recovery and then convert it to ext4
Thank you both for taking your time to help me!
I'm going to summarize what I did to get my tablet back to working:
1. Having the tablet shut down because of low battery seems to have been the reason why I could boot from the microSD card again. So what can be done in that situation is to boot into the emmc recovery (which gets stuck at the splash screen) and then just leave it on until it shuts itself off. Then charge it up again and try to boot into the microSD card. Worked for me.
2. To then actually fix the problem, make sure to have CWM on the microSD card. There are at least two ways to get the tablet to work again:
- Boot into CWM, then connect to a pc with adb, reformat with adb shell using "make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata" (didn't work for me, as it couldn't find make_ext4fs)
- Boot into CWM, install stock recovery, use it to factory reset the tablet, boot into stock ROM once to make sure, boot into CWM, flash all your stuff.