Database Users

CWM and CM7 problems

I hope that this is in the right place, but I've run into a strange problem with my Desire Z.
I have rooted and achieved S-Off by following the process at Cyanogen's Wiki.
I had Cyanogen 7.0.3 working just fine for a few months. Last night, I was trying to install some apps (Zenonia 2 and 3 to be precise), and the system hung during the install. So, I set it down for a few mins, then pulled the battery after I figured it wasn't coming back.
In trying boot after the hang, the system stuck on the Cyanogen mod load screen, left for 5+ mins and still no progress.
Rebooting again stuck it on the HTC screen.
I can still get into Hboot and ClockworkMod, but when trying to flash the CM7 boot.img through fastboot I receive the following error
Code:
writing 'boot' ... FAILED (remote:not allowed)
which is the same result when trying to flash the stock rom boot
CWM 3.0.2.4 generates errors as well.
Code:
E:\Can't mount /cache/recovery/command
E:\Can't mount /cache/recovery/log
E:\Can't open /cache/recovery/log
E:\Can't mount /cache/recovery/last_log
E:\Can't open /cache/recovery/last_log
When I try and flash CM7 back through "install zip from sdcard", I get the following
Code:
Finding update package...
Opening updae package...
Installing update...
E:Error in /sdcard/update-cm-7.0.3-vision-signed.zip (Status 1)
Installation aborted.
Now I'm pretty (ie 99%) sure that this is the same CM that I installed before without a hitch.
I am pretty new to android, and any help you might be able to provide would be greatly appreciated!

Sounds like you don't have eng hboot installed. that's why you can't flash anything from the bootloader. I am pretty sure you have already done that .but have you done a full wipe from recovery?
Sent from my HTC Vision using XDA App

I have wiped both the data and cache in CWM. And the bootloader that shows up is the engboot (three boarding droids, hboot command, etc)

Connect your phone to your pc, put your phone on fastboot and try this command: fastboot erase system -w
That should solve the problem .I am assuming you have the fastboot binary in your adb folder as well.
Sent from my HTC Vision using XDA App

You can also try to flash another rom just to make sure the cm7 zip that you have is not the problem
Sent from my HTC Vision using XDA App

Tried fastboot erase system -w
threw the following message
Code:
erasing 'system'... FAILED (remote:not allowed)
Just to confirm, the header in hboot is
Code:
VISION PVT SHIP S-OFF
HBOOT-0.85.0005
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010,20:10:38

snowman211 said:
I hope that this is in the right place, but I've run into a strange problem with my Desire Z.
I have rooted and achieved S-Off by following the process at Cyanogen's Wiki.
I had Cyanogen 7.0.3 working just fine for a few months. Last night, I was trying to install some apps (Zenonia 2 and 3 to be precise), and the system hung during the install. So, I set it down for a few mins, then pulled the battery after I figured it wasn't coming back.
In trying boot after the hang, the system stuck on the Cyanogen mod load screen, left for 5+ mins and still no progress.
Rebooting again stuck it on the HTC screen.
I can still get into Hboot and ClockworkMod, but when trying to flash the CM7 boot.img through fastboot I receive the following error
Code:
writing 'boot' ... FAILED (remote:not allowed)
which is the same result when trying to flash the stock rom boot
CWM 3.0.2.4 generates errors as well.
Code:
E:\Can't mount /cache/recovery/command
E:\Can't mount /cache/recovery/log
E:\Can't open /cache/recovery/log
E:\Can't mount /cache/recovery/last_log
E:\Can't open /cache/recovery/last_log
When I try and flash CM7 back through "install zip from sdcard", I get the following
Code:
Finding update package...
Opening updae package...
Installing update...
E:Error in /sdcard/update-cm-7.0.3-vision-signed.zip (Status 1)
Installation aborted.
Now I'm pretty (ie 99%) sure that this is the same CM that I installed before without a hitch.
I am pretty new to android, and any help you might be able to provide would be greatly appreciated!
Click to expand...
Click to collapse
I had this exact problem, I'm afraid to say it seems your emmc chip went bad... This happened to my previous G2 and left it a brick. What you need to do is hop on the IRC channel #g2root on a IRC client (on irc.freenode.com) and talk to a guy named Guhl. He can help you determine if your eemc chip is truly broken or fixable!

Thanks Kevin. I'll try that when I get a chance.

snowman211 said:
Tried fastboot erase system -w
threw the following message
Code:
erasing 'system'... FAILED (remote:not allowed)
Just to confirm, the header in hboot is
Code:
VISION PVT SHIP S-OFF
HBOOT-0.85.0005
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010,20:10:38
Click to expand...
Click to collapse
Well that's what I though ,you havnt got eng hboot installed what's is why you can't use fastboot commands . I don't think it is anything hardware related though. Youmight be Able to fix it by flashing a pc10img
Sent from my HTC Vision using XDA App

Emmc is shot. Nothing to do if that's the case
Sent from my HTC Vision using XDA Premium App

Emmc being shot a common problem? Or just really bad luck on my part? I loved the phone thus far.

snowman211 said:
Emmc being shot a common problem? Or just really bad luck on my part? I loved the phone thus far.
Click to expand...
Click to collapse
Its weird cause I never used to see anything about it. Now all of a sudden over the past few months it seems to be happening to someone every other day. Either way its not your fault. Bad luck. I read a real good explanation of why/what happens but not sure where its at now
Sent from my HTC Vision using XDA Premium App

Oh well. Time for a new phone I guess. Thanks all for your help.

nexus 7 wont react while flashing in fastboot

hello,
today i downloaded the Android 5.0 Image from Google and wanted to flash it.
i extraced the tgz file and flashed the boot.img and system.img via fastboot.
so far so good. i reboot the tabelt and it has a bootloop.
so i used the flash-all.bat included in the tgz file but it wont flash it (didnt copied the error message)
so i tried flashing 4.4.4. but when i flash anything it wont work (fastboot flash recovery recovery.img for example)
i tried differend usb ports and with fastboot devices it shows my device.i tried rebooting the laptop and the tablet. no changes
example
Code:
C:\Users\xxx\Desktop\nakasi-lrx21p>fastboot flash recovery recovery.img
sending 'recovery' (5682 KB)...
after 20 min of waiting nothing changes.
my setup:
a laptop with windows 8.1
all drivers installt
original nexus 7 usb cable
drivers are working fine. i often flashed something on the n7 and my m7 bevor on this laptop

Code:
C:\Users\xxx\Desktop\nakasi-lrx21p>fastboot flash boot boot.img
sending 'boot' (5146 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
thats a error message i get when something more happens then "sending 'xxx' (xxx kb)

Code:
FAILED (data transfer failure (Too many links))
finished. total time: 85.114s

now i managed to flash recovery (TWRP)
but i cant do anything there. in the pc its not listet (adb devices) and in the log of TWRP it says
Code:
E:Unable to mount '/data'
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'

now i got in TWRP (changing to Clockworkmod Recovery doesnt change anything) and got to Wipe-> Advanced
there i tried to repair the partions . doesnt works. but if i format it that works and could be mounted again. (in system i have to format it in an different file format and back to ext4)
so now i flashed the rom (stock 5.0 from google) and it boots... waiting whats coming next....

etsch said:
now i got in TWRP (changing to Clockworkmod Recovery doesnt change anything) and got to Wipe-> Advanced
there i tried to repair the partions . doesnt works. but if i format it that works and could be mounted again. (in system i have to format it in an different file format and back to ext4)
so now i flashed the rom (stock 5.0 from google) and it boots... waiting whats coming next....
Click to expand...
Click to collapse
i have the same problem how did you format it and did it fix the problem

do you have TWRP ?
you go to wipe-> advanced
there you can choose which repair and format.
ive formated one by one and then it shows the size after formating.
now my tablet booted into android (i think its ugly) but iam afraid going in the recovery

[Q] Nexus 7 (2013) unlock bootloader and the Power button (yes) Failed.

Hi,
I try to boot my Nexus 7 (2013/wifi). I have access to :
a white google logo
a fastboot access
and a recovery mode (with a sideload option)
I was reading my email when the tablet suddenly reboot and stuck on the Google logo. Now, I don't know what can I do.
Code:
Fastboot oem unlock
doesn't work (FAILED <unknow error>).
I can flash a new bootloader (FLO-04.04) but can't unlock it.

Are you getting any specific error message ?

After recovery mode I have something like :
Code:
-- Wiping cache...
Formatting /cache..
Cache wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_locale
I make a `fastboot oem unlock` right now and waiting after a error :angel:
Code:
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
edit : After 23000 s
FAILED (unknown status code)

May be my best choice is to waiting for 5.1 OTA (nexus 7 2013 wifi) and make a sideload ?

Any suggestion ?

jaiunxda said:
Any suggestion ?
Click to expand...
Click to collapse
Last chance : https://www.change.org/p/google-lg-...aign=share_twitter_responsive#petition-letter

Nexus only runs with Jelly bean 4.2.2 (downgrade from 5.1.1)

Hi,
I have a Nexus 4 which was flashed with Lollipop 5.1.1.
My problem started when, after letting the battery completely drain and then trying to turn the phone on again, I got stuck on the message "Android is starting... optimizing apps" for days. I tried rebooting and factory format with no success.
I also tried formatting it through TWRP, but I got the message "Unable to mount /cache". After that, I tried flashing older factory images but only got my phone to work with the oldest version of jelly bean available by google developers page (4.2.2). After I got it to work, I tried to OTA update it to 4.3, but the same message "Android is starting ... optimizing apps" came back.
I had no other choice but to fastboot format it and flash it again with 4.2.2.
Any ideas on what could possibly be causing this? I thought it might be some problem in the cache partition but haven't found a way to fix it or if it's even possible to. Apparently everything's working with 4.2.2 but I'd love to go back to 5.1.1!
Thanks in advance!

dont dirty flash the factory image. make a clean factory image flash

After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?

audit13 said:
After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?
Click to expand...
Click to collapse
Haven't tried that, I'll give it a go and post the results here!
I've also noticed the phone isn't receiving any signal and it doesn't display the IMEI anymore..

The lack of an imei is a definite problem. Try flashing the stock LP or KK ROM and check for the imei.

audit13 said:
The lack of an imei is a definite problem. Try flashing the stock LP or KK ROM and check for the imei.
Click to expand...
Click to collapse
Did a clean factory image flash of Lollipop 5.1.1, booted into twrp recovery (I'm not sure how to go back to stock recovery) to wipe the data and got the following message:
E: UnMount: Unable to find partition for path '/sdcard'
E: Mount: Unable to find partition for path '/sdcard'
Updating partition details...
E: Unable to mount '/cache'
...done
E: Unable to mount '/cache'
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Formatting Data using make_ext4fs function.
Ypu may need to reboot recovery to be able to use /data again.
Updating partition details...
E: Unable to mount '/cache'
...done
After that I rebooted the phone and it's been stuck on bootloop again since then.

When you flash a stock ROM, did you flash the recovery.img? Sometimes, I find that only stock recovery can properly format the cache. When flashing my Nexus 5 to stock from a custom ROM, I get an error message when I boot into stock recovery that the cache has an invalid format. Once I perform a factory wipe, the cache is properly formatted and wiped.

audit13 said:
When you flash a stock ROM, did you flash the recovery.img? Sometimes, I find that only stock recovery can properly format the cache. When flashing my Nexus 5 to stock from a custom ROM, I get an error message when I boot into stock recovery that the cache has an invalid format. Once I perform a factory wipe, the cache is properly formatted and wiped.
Click to expand...
Click to collapse
Yeah, I flashed the images for boot, recovery, system, userdata and cache separately. I'll look up how to get back into stock recovery now and I'll try what you've said!

If recovery.img was flashed, the phone should not have TWRP, it should be a stock recovery. If stock recovery cannot be flashed, this leads to me believe that something is wrong with the memory chip.

audit13 said:
If recovery.img was flashed, the phone should not have TWRP, it should be a stock recovery. If stock recovery cannot be flashed, this leads to me believe that something is wrong with the memory chip.
Click to expand...
Click to collapse
I tried it again, flashed everything including recovery, went into stock recovery mode and wiped the data. Apparently its back to being stuck on bootloop

Use fastbot commands to erase cache and userdata. Then use fastboot to flash the userdata.img file, boot directly to recovery, and wipe again.

audit13 said:
Use fastbot commands to erase cache and userdata. Then use fastboot to flash the userdata.img file, boot directly to recovery, and wipe again.
Click to expand...
Click to collapse
Did it, still stuck on bootloop... Not sure if it can be somehow related but I got this message when I booted into recovery

The recovery screen looks correct because, after flashing userdata.img, you must format in stock recovery.
I am at a loss as to why 4.2.2 works while kk and LP do not.

audit13 said:
The recovery screen looks correct because, after flashing userdata.img, you must format in stock recovery.
I am at a loss as to why 4.2.2 works while kk and LP do not.
Click to expand...
Click to collapse
Ah, thanks for the help, anyway!
If someone else knows what to do.. The phone is now back to the initial message "android is starting... optimizing apps". Kinda of losing hope now

I've done this to my Nexus 5 once, too.
You basically screwed your cache partition.
Boot into the bootloader. Hook the phone up to your pc and open the command prompt.
Enter these commands:
fastboot erase cache
fastboot format cache
fastboot reboot-bootloader
When successful boot into recovery and the errors should be gone.
You should be able to flash a new rom now.

playitlouder said:
I've done this to my Nexus 5 once, too.
You basically screwed your cache partition.
Boot into the bootloader. Hook the phone up to your pc and open the command prompt.
Enter these commands:
fastboot erase cache
fastboot format cache
fastboot reboot-bootloader
When successful boot into recovery and the errors should be gone.
You should be able to flash a new rom now.
Click to expand...
Click to collapse
This got rid of the unable to mount cache error, flashed the rom again but it's still stuck on bootloop :/

thafuchs said:
This got rid of the unable to mount cache error, flashed the rom again but it's still stuck on bootloop :/
Click to expand...
Click to collapse
Okay. Progress
You have probably already nuked all your data. So I would suggest erasing and formatting everything again and then flash the newest factory image.
Enter bootloader again, on your pc do the following:
fastboot erase system
fastboot format system
fastboot erase data
fastboot format data
fastboot reboot-bootloader
Then grab the factory image, open the flash_all.bat file in an text editor (either use windows notepad, or grab notepad++).
You have to "cd" to the directory of your factory image. I would suggest to type "c:" *press enter* then cd *pull the folder that contains the factory image into the command prompt* *press enter*.
If you type "dir" now you should get your factory image directory.
Now just type in every command from the flash_all.bat one by one. Report, if there are any errors.

playitlouder said:
Okay. Progress
You have probably already nuked all your data. So I would suggest erasing and formatting everything again and then flash the newest factory image.
Enter bootloader again, on your pc do the following:
fastboot erase system
fastboot format system
fastboot erase data
fastboot format data
fastboot reboot-bootloader
Then grab the factory image, open the flash_all.bat file in an text editor (either use windows notepad, or grab notepad++).
You have to "cd" to the directory of your factory image. I would suggest to type "c:" *press enter* then cd *pull the folder that contains the factory image into the command prompt* *press enter*.
If you type "dir" now you should get your factory image directory.
Now just type in every command from the flash_all.bat one by one. Report, if there are any errors.
Click to expand...
Click to collapse
Okay, got some errors on the way... trying to erase data failed (Remote: partition table doesnt exist), format data failed too (formatting is not supported for filesystem with type ' '.)
Also, on the last command:
.\fastboot -w update .\image-occam-lmy48t.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
[...]
checking version-bootloader
FAILED
Device version-bootloader is 'MAKOZ10o'
Update requires 'MAKOZ30f'
Rebooted and its now stuck on google logo

Sorry, you should have typed: (it obviously cannot format something that is not there )
fastboot erase userdata
fastboot format userdata
Have you flashed the bootloader?
Have you rebooted after flashing the bootloader?
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
Don't forget to also flash the radio.
These "does not contain" errors are normal.

playitlouder said:
Sorry, you should have typed: (it obviously cannot format something that is not there )
fastboot erase userdata
fastboot format userdata
Have you flashed the bootloader?
Have you rebooted after flashing the bootloader?
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
Don't forget to also flash the radio.
These "does not contain" errors are normal.
Click to expand...
Click to collapse
Okay, I've flashed bootloader, rebooted, flashed radio, rebooted, typed the update command but the checking of bootloader version failed again.. rebooted and its back to being stuck on google logo

huawei p8 brick

Hello
i have huawei p8 and it is brick
Code:
rescue mode
error func No : 10 (boot image)
error No : 2 (load failded!)
There is trwp but when i go wipe i have 0 MB storage
E: Unbale to mount /system
E: Unbale to mount cache
E: Unbale to mount /data
do you have any idea to fix it ???

holekns said:
Hello
i have huawei p8 and it is brick
There is trwp but when i go wipe i have 0 MB storage
E: Unbale to mount /system
E: Unbale to mount cache
E: Unbale to mount /data
do you have any idea to fix it ???
Click to expand...
Click to collapse
I think that you have to flash the normal recovery and flash the stock version of emui.
Sent from my Huawei P8 using XDA Labs

It happened to me once, you have to download the latest stock ROM for your device, unpack it and flash boot.img, recovery.img and system.img through adb. Then when you boot up, you have to transfer the update.app that you downloaded on your PC to your P8 and install it via SD card method. That's how I fixed it. Or you can save yourself the headache, if you remember the build you were on, you can just download it again on your PC, unpack it and and flash boot.img through adb.

Ok
I make
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
then phone stop on huawei logo and only vol- fastbootand rescue mode
its look like the boot is fake

holekns said:
Ok
I make
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
then phone stop on huawei logo and only vol- fastbootand rescue mode
its look like the boot is fake
Click to expand...
Click to collapse
Flash the boot, recovery and system.img of the rom you had when you brick the mobile.
Sent from my GRACE using XDA Labs

lespaul79 said:
Flash the boot, recovery and system.img of the rom you had when you brick the mobile.
Sent from my GRACE using XDA Labs
Click to expand...
Click to collapse
but i don't known what boot was any idea or test all boot yes ???
is anyware place where are all the boot recovery and system to p8
This will be ok https://www.androidfilehost.com/?w=files&flid=140689

holekns said:
but i don't known what boot was any idea or test all boot yes ???
Click to expand...
Click to collapse
Install twrp and flash a custom ROM, keep in mind that operating system you had mm or llollipop there is custom ROM for both tecalote and blackball
Sent from my GRACE using XDA Labs