[Q] Unable to flash recovery - Click Android Development
Hi all!!!
I have a big problem trying to flash recovery image.
I've tryied to flash recovery-RA-tattoo-v1.6.2, recovery-clockwork-2.5.1.8-tattoo and recovery-clockwork-3.0.0.5-tattoo but i got the following error:
mtd: erase failure at 0x00260000 (Input/output error)
mtd: erase failure at 0x00260000 (Input/output error)
mtd: skipping write block at 0x00260000
I used aldo the 1 click recovery method but the result is always the same.
But if i try to flash original recovery it works fine.
I also tryied to setup RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe and than i repeted the recovery procedure...but the same errors appeared.
it seems original recovery may not use 0x00260000 block while custom recovery do, i think.
How can i solve this problem? Any idea?
thank you!!!
davinem said:
Hi all!!!
I have a big problem trying to flash recovery image.
I've tryied to flash recovery-RA-tattoo-v1.6.2, recovery-clockwork-2.5.1.8-tattoo and recovery-clockwork-3.0.0.5-tattoo but i got the following error:
mtd: erase failure at 0x00260000 (Input/output error)
mtd: erase failure at 0x00260000 (Input/output error)
mtd: skipping write block at 0x00260000
thank you!!!
Click to expand...
Click to collapse
try to flash recovery while in recovery as mentioned in the following post
http://forum.xda-developers.com/showpost.php?p=12066137&postcount=17
also have look at the following thread last 5-6 messages are about similar issue
http://forum.xda-developers.com/showthread.php?t=989182&page=2
I can't use adb when my tattoo is in recovery page. adb device not found...
root your Phone and use rommanager from market. it automatically flash clockwork recovery by first use...
Hi dlazz,
I've already tried with RomManager...it gives me a successfull message, but when i try to restart in recovery, my tattoo is locked on tattoo screen. :-(
It's very strange, i've also flashed original ruu, but the same message appear.
But if i flash the original recovery, it completes successfull...So i think it's the dimension of the custom recovery gives me problems...
Another try:
While i was running the original RUU i copied the file rom.zip from a subfolder in c:\windows\temp. Then, i replaced recovery.img with clockwork 3.0.0.6 and renamed in CLICIMG.zip.
When i reboot Hboot load it but after checking do nothing!
Can i avoid Hboot checking?
It's correct?
Tried also to generate a goldcard...but while flashing recovery...mtd: erase failure at 0x00260000 (Input/output error) comes AGAIN!!!
It gives me so much pain
Now, my question is...Only my tattoo is so....
No one can help me???
davinem said:
Hi all!!!
I have a big problem trying to flash recovery image.
I've tryied to flash recovery-RA-tattoo-v1.6.2, recovery-clockwork-2.5.1.8-tattoo and recovery-clockwork-3.0.0.5-tattoo but i got the following error:
mtd: erase failure at 0x00260000 (Input/output error)
mtd: erase failure at 0x00260000 (Input/output error)
mtd: skipping write block at 0x00260000
I used aldo the 1 click recovery method but the result is always the same.
But if i try to flash original recovery it works fine.
I also tryied to setup RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe and than i repeted the recovery procedure...but the same errors appeared.
it seems original recovery may not use 0x00260000 block while custom recovery do, i think.
How can i solve this problem? Any idea?
thank you!!!
Click to expand...
Click to collapse
Are you sure that your device is rooted?
First root your device using the one-click root method that is there in this forum. Then open adb. Type 'adb shell' to get a shell. Then type 'su'. If you get #, you are successfully rooted. Then type 'lsmod', if you see tattoo_hack in the next line, all is well. Then just download Rom Manager and flash recovery. And enter all the commands without the quotes.
KalimochoAz said:
Are you sure that your device is rooted?
Click to expand...
Click to collapse
His device is rooted. He didnt insert tattoo-hack.ko. If his device wasnt rooted, then would not have been able to run flash_image. It would give permission problems.
Hi and thank you for your support...
Yes, i rooted my tattoo. I've done it both with 1click root method, manual method universal nandroot, etc...
If i use 1 click method with all the known recovery it gives me the same error, but if i place the original recovery, it flashes successfully.
I re-installed also the original RUU to have a clean system and then repeated 1click method...but the result is the same.
This is the output for lsmod:
# lsmod
lsmod
tattoo_hack 1480 0 - Live 0xbf000000
Can i execute any adb commands to help you about my tattoo???
P.S. I've just tried with RomManager and it gives me a successful message installing Clockworkmod 3.0.0.6 recovery. but if i reboot in recovery mode my tattoo is stopped on Tattoo logo...
sunitknandi said:
His device is rooted. He didnt insert tattoo-hack.ko. If his device wasnt rooted, then would not have been able to run flash_image. It would give permission problems.
Click to expand...
Click to collapse
I've inserted the tattoo-hack.ko, so if i repeat the 1 click procedure when i try to insert tattoo-hack.ko it gives me file already exists.
But, how can i test the full functionality of this module?maybe, it doesn't work correctly...
thank you!
Related
Accidentally formatted sdcard prior to flashing
Hey guys, I need some help here I accidentally formatted the sdcard when preparing a clean flash. I also formatted system ect. so now all I can do is boot into recovery but no files to flash. Is there some way I can transfer files to the sdcard og another way to get the device working again? Thanks in advance.
You are softbricked. Restore factory image using wugfresh http://www.wugfresh.com/nrt/
Download the factory images, boot into bootloader (not recovery) by holding power+down, then flash the factory images.
I'm in exactly the same boat here, but every time I try to use fastboot commands, I get a write failed. I'm fairly certain the drivers are installed properly, as fastboot devices shows me the device. What else could be done?
codemonkey85 said: I'm in exactly the same boat here, but every time I try to use fastboot commands, I get a write failed. I'm fairly certain the drivers are installed properly, as fastboot devices shows me the device. What else could be done? Click to expand... Click to collapse Give the exact steps and exact messages, cut and paste is best, otherwise there is not enough info to go on.
I installed the drivers using Nexus Root Toolkit 1.5.5. (I used option #2, which is to install the signed drivers.) I copied the extracted contents of the Nexus 7 4.2 factory image into my adb folder. I ran a command prompt in that folder. I type: fastboot devices I get: 015d25687443fe0f fastboot I type: fastboot flash bootloader bootloader-grouper-4.13.img I get: FAILED (command write failed (Unknown error)) I type: fastboot -w update image-nakasi-jop40c.zip I get: FAILED (command write failed (Unknown error))
Well, I don't know how or why, but I just tried the same thing again using the Nexus Toolkit and it worked this time. I'm booting into a stock ROM right now.
Im unable to turn on USB debugging, cause i have no ROM. What to do?
codemonkey85 said: I installed the drivers using Nexus Root Toolkit 1.5.5. (I used option #2, which is to install the signed drivers.) I copied the extracted contents of the Nexus 7 4.2 factory image into my adb folder. I ran a command prompt in that folder. I type: fastboot devices I get: 015d25687443fe0f fastboot I type: fastboot flash bootloader bootloader-grouper-4.13.img I get: FAILED (command write failed (Unknown error)) I type: fastboot -w update image-nakasi-jop40c.zip I get: FAILED (command write failed (Unknown error)) Click to expand... Click to collapse exactly the same error im getting.. how did you solve it?
Tried again on another USB port and now it worked. Thanks for the help guys.
codemonkey85 said: Well, I don't know how or why, but I just tried the same thing again using the Nexus Toolkit and it worked this time. I'm booting into a stock ROM right now. Click to expand... Click to collapse Out of interest why didn't you just run the small script that comes with the factory image to wipe and reflash everything. It's what I did to make sure I had a nice clean install. Or were you trying to keep some data from /data for example.
[Q] TWRP flash via Fastboot failing
I just took my good ol' Streak 7 to update it as I see some nice JB action here. But as I understand any manipulation to be made needs TWRP to be present on device. As GooManager wasn't instaling recovery the simple way, I decided to download image and flash it via Fastboot. Yet every single time it failed to do so. Code: fastboot flash recovery twrps.img sending 'recovery' (4822 KB)... FAILED (command write failed (Invalid argument)) finished. total time: 0.000s I was flashing the latest (2.6.x) version. Also my device is empty atm (had 3.2, now has nothing). Custom Recovery is CWR 5. Need help to flash the TWRP and begin using JB roms.
YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot. The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value.
giveen said: YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot. The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value. Click to expand... Click to collapse Seems that all download links for nvflash pack for DS7 are now dead both on xda and google.
[Q] Razr I Failed flashing process
Hi - I've started receiving a bunch of errors on my phone indicating a lot of processes are failing. Have tried resetting app preferences after searching through a lot of forums but these problems still persisted. Factory reset didn't help either. I'm bootloader unlocked and rooted so thought I'd flash a new ROM via RSDLite. I am unable to do this either. I receive the error "Failed flashing process. 1/12 flash gpt "gpt_signed" -> Phone returned FAIL.." (see attached screenshot). On the phone itself I see the following: E: Can't read /dev/block/misc (I/O error) E: Failed to get BOX sync msg from MISC Fastboot Reason: Reboot to bootloader fastboot: max download size: 100Mb USB connected Getvar max-download-size Downloading ... Flashing gpt ... E: re-partition failed: Device or resource busy Fastboot command failed I fear this means I have a corrupted internal SD card so no way to fix... however I'm no expert on this. Any idea how to fix please? Thanks,
UPDATE Without any further tinkering on my part the phone is no longer able to boot up. It's now alternating between the "intel inside" logo and motorola logo. Also feels pretty warm. I'm kind of giving up on the device and have ordered a new phone already. If anyone has a quick fix to revive it then feel free to let me know else will use it as a nice paperweight. Thanks.
Razr I stucks on bootloop
Hi - I've started receiving a bunch of errors on my phone indicating a lot of processes are failing. The OS version is Android 4.1.2 Jelly bean. Have tried resetting app preferences after searching through a lot of forums but these problems still persisted. Factory reset didn't help either. I'm bootloader unlocked and rooted so thought I'd flash a new ROM via RSDLite. I am unable to do this either. I receive the error "Failed flashing process. 1/12 flash gpt "gpt_signed" -> Phone returned FAIL..". On the phone itself I see the following: E: Can't read /dev/block/misc (Bad file number) E: Failed to get BOS sync msg from MISC Fastboot Reason: Flash Failure fastboot: max download size: 100Mb USB connected Getvar max-download-size Downloading ... Flashing gpt ... E: re-partition failed: Device or resource busy Fastboot command failed Fastboot menu disabled I fear this means I have a corrupted internal SD card so no way to fix... however I'm no expert on this. Any idea how to fix please? Thanks,
U copy/pasted another forum post , ah well it works. It is indeed that your phones memory is corrupted. I maybe have a solution, but first i need to know what firmware u are using. Hazou
Can't flash a single custom rom. Help Needed.
So I don't know what has happened but I can't flash even a single custom rom. The problem occurs in TWRP as well as CWM. Also I am on the stock partition. Tried the modified partition too. The problem is still occuring no matter what I try. The following case is of SOKP. Every other rom also has the same problem. Even after trying it via adb the problem persists. After I select the zip file in the recovery mode,the installation starts. After that, it says: Patching system image unconditionally... blkdiscard failed: Invalid argument E : Error in/data/media/0/SOKP-L_5.1.1-LMY48B-R3-20150525-cancro.zip (Status 7) Installation aborted.
Have you checked whether your bootloader is locked or not (because of that damned MIUI MM)? Try sending through fastboot: Code: fastboot oem device-info If the "Device unlocked" comes out as false, then unlock it first by sending through fastboot: Code: fastboot oem unlock It'll wipe all the content of your phone though...
shivam0909 said: So I don't know what has happened but I can't flash even a single custom rom. The problem occurs in TWRP as well as CWM. Also I am on the stock partition. Tried the modified partition too. The problem is still occuring no matter what I try. The following case is of SOKP. Every other rom also has the same problem. Even after trying it via adb the problem persists. After I select the zip file in the recovery mode,the installation starts. After that, it says: Patching system image unconditionally... blkdiscard failed: Invalid argument E : Error in/data/media/0/SOKP-L_5.1.1-LMY48B-R3-20150525-cancro.zip (Status 7) Installation aborted. Click to expand... Click to collapse Extend your partition first, you'll be fine then. There is manual tutorial in Mi3 General sub forum.