[Q] What's wrong with my phone? - General Questions and Answers

So here's the deal. I have A rooted Droid Incredible and i cant get past the splash image. I tried going into recovery and wiping everything and flashing a new rom but I keep getting the following message:
E: Can't mount dev/block/mmcblk0p1
It comes up when i try to flash a rom and says installation aborted about halfway through installing. It also comes up when i try to wipe and do a factory reset.
If anyone knows a way around this It would be immensely helpful, because as of right now i cant use my phone which is a problem. I'm running clockwork recovery v2.5.0.5.

Dr0pSh0t said:
So here's the deal. I have A rooted Droid Incredible and i cant get past the splash image. I tried going into recovery and wiping everything and flashing a new rom but I keep getting the following message:
E: Can't mount dev/block/mmcblk0p1
It comes up when i try to flash a rom and says installation aborted about halfway through installing. It also comes up when i try to wipe and do a factory reset.
If anyone knows a way around this It would be immensely helpful, because as of right now i cant use my phone which is a problem. I'm running clockwork recovery v2.5.0.5.
Click to expand...
Click to collapse
Try to post this in Droid Incredible's ROM development section - you will find better help there!

Related

[Q] Need some help on getting phone out of "stuck on google logo" state

Hey guys my phone is stuck on google logo, i have bought it in this condition. Its i9020T and wrong cwm is installed. I am able to put phone in download mode but odin wont recognize it, tried flashing different rom gives me abort with state 7, also when i try to wipe anything it gives me E: Can't find MISC, and E: Can't find CACHE. I have CWM 2.0... I figured wrong CWM can cause the problem, so my question is: how can i update CWM and get phone back to working state?

[Q]Cant Install Updates from Recovery

Ok, I cant install any update.zip files or NAND stuff to go back to stock. Everytime I try, it says E: signature failure and aborted. Ive wiped all my data and everything too.
Here is the screen info.
Android System Recovery <3e>
reboot system now
apply update from /sdcard << cant install anything using this.
wipe data/factory
wipe cache partition
So everytime I try to install something it says E: signature verification failed.
I run a WIND Nexus S, with a the ICS 4.0.3, which really ate up my memory and started lagging like turtle after an hour or 2. SO I wanna go back to stock and install another version that hopefully rus better and smoother. Please help
Do you have cwm 5.0.2.x or greater?
No, I think Im 3.xx something. BUt Ive tried updating thru rom manager and it says I dont have the privileges. I have superuser installed o I dont know why its not letting me. Do I have to manually apply the 5.8.0 touch update???
I assume you have an unlocked bootloader, so use fastboot to upgrade to v5 or greater. You don't need the touch if you don't want it, you can just use 5.0.2.0 if you prefer.
Recap of command: fastboot flash recovery recovery.img
You can get the latest superuser .zip file from here. You can probably flash that through the older recovery if you're unsure how to use fastboot.
Thanks for the replies Harbb. SO I did fastboot flash recover to the new 5.0.2.0.. but nothing happened. The cmd did say recovery sent in 1.7 secs. But when I reboot nothing changed. Its still the same recovery at 3e and I still cant install updates cuz of the e: signature verification failure.
EDIT: I just got it to work. Thank for the help Harbb, extremely appreciated.
Good to know you got it sorted

If I can get into the Fastboot screen I am not fully bricked??

I can boot with volume up and get to the recovery screen. I am combing threads and doing all I can now. Any help is greatly appreciated. Downloading the SDK on slow work internet now and attempting to get all files I think I might need as we speak.
give members more details [what did u flash etc], so they can help u.
No, if you have recovery mode available nothing is lost.
Just download a ROM you like, and try flashing it. If it doesn't work, try formatting and then flashing again.
I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.
In recovery you can still use adb to transfer files to the device.
Code:
adb push update.zip /sdcard
I am having trouble getting adb to work. I am following these instructions but something seems to be wonky?
http://androidadvices.com/how-to-install-set-up-and-use-adb-for-android-devices/#.UAWbt7Sm_Nk
can you point me in a better direction to get adb access
I just noticed at the bottom of my screen in slightly greyed out copy it reads: FASTBOOT STATUS - FAILINVALID COMMAND
magicwands said:
I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.
Click to expand...
Click to collapse
That small menu as you called it is fastboot.
That recovery is stock recovery.
Connect to phone to computer and use fastboot to flash a custom recovery. Boot into said recovery. Mount usb storage. Transfer rom over to phone. factory reset/format system and flash new rom.
If you don't know how set up and use fastboot. Look it up.
I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?
magicwands said:
I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?
Click to expand...
Click to collapse
Do a full wipe, re-download the rom ( make sure its the correct rom for your device) and try again.
If it still fails. Flash the official stock images and make sure that at least works
I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.
magicwands said:
I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.
Click to expand...
Click to collapse
Download the following files:
7-Zip from http://www.7-zip.org
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
http://android.kcomputerzone.com/stock/sojus-imm76d-factory_windows-scripts.zip
http://android.kcomputerzone.com/extras/crespo-drivers.zip (just in case you need them)
Install 7-Zip
Extract sojus-imm76d from sojus-imm76d-factory-10660f4c.tgz (You will need to go in multiple levels deep to get to folder) to your desktop.
Extract contents of sojus-imm76d-factory_windows-scripts.zip to the sojus-imm76d on your the desktop.
With phone in bootloader mode run flash-all.cmd in the sojus-imm76d folder.
If all worked it should be boot and be working.
That should restore yours to default firmware all using fastboot. Hope this helps.
This site (http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/) got me up and running with TWRP then I been having issues flashing roms, I am able to get a Peter Alfonso stock rom to boot but then if I try to flash I get the same error. I was able to ODIN the stock 4.0.4 but nothing seems willing to flash via clockwork or TWRP.
Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.
magicwands said:
Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.
Click to expand...
Click to collapse
That is the problem with One click root/unroot. I know the simplicity is awesome but the end user is learning nothing. Doing it the ol' fashion way teaches the user how to use SDK, ADB, and other important simple things. I always say use the guide and do it yourself. Problems happen and instead of having to start a new thread you can trouble shoot it yourself. :good:

Just screwed myself. Brick?? Help :((

Hello, I know I am an idiot for this.
But I tried to create my own rom, following a guide carefully.
It was a miui rom and I skipped only one thing, because I couldn't find it. I don't think it was anything important that could have caused my dilemma.
To get to the point.
I have the Nexus S 4G
Using TWRP Recovery
I made a backup of my stock rom
I flashed the Rom(I created) and it failed to flash.
So I tried to restore my Stock rom. Once it said it completed.
I tried to reboot and it just brought me back to bootloader screen.
I'm panicking now.
So I use my root toolkit to flash CWM recovery and tried to install a
new rom on my phone, but it's not working
when I try to boot up into a new rom, all I get is a black screen.
HELP PLEASE. ((
edit: when I went back into TWRP to check the log, it said "can't mount SD"
and I went to MOUNT and Sdcard was mounted..

[Q]Motorola Atrix 2:possible soft brick? Installed altCyanogenMod and now won't boot.

I have been struggling with getting my Motorola Atrix 2 rooted. I finally got it rooted and tried to install a custom ROM. I started with installing CWM and flashing this CM10 port: (wangs) http://www.androidlawn.com/motorola-atrix-2-android-4-2-2-jelly-bean-cyanogenmod-10-1/
I found this to be buggy so I kept looking and I found this: altCyanogenMod http://forum.xda-developers.com/showthread.php?t=2275529
I installed it according to the instruction in that thread and now my phone just hangs on the CM boot screen.
I am able to get in to bootloader via adb.
When i use adb to reboot in to recovery I get the android with the Red triangle "!". If I hold both volume up and down I can get in to "Android System Recovery <3e> Android system recovery utility" from this menu I am able to
reboot the phone
flash a zip from the sd card
wipe data/factory reset
wipe cache
apply update from cache
These are the only options. When I try to flash a NEW ROM in the flash zip option it fails, saying "E:signature verification failed" then it aborts. I have tried this with 2 different ROMs
I don't know what else to try.
I think this happened because I might be an idiot and installed the altCM on the wrong kernel.
Please help this fool fix his phone! Thank you!
bump-I don't mean to pester. I only bump this because I posted in the middle of the night and this post got quickly buried.
Please help.
Thank you

Categories

Resources