Problem:
Can't seems to be able to restore my phone using clockwork 3.0.2.4 or when trying to do a fastboot restore through the android SDK.
Error:
When I try to restore the system or the data via clockwork on the phone i get "error formatting /system!" or "error formatting /data!"
I also tried to do this:
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
I get the following error:
sending 'userdata'
FAILED (remote: data lenght is too large)
I also tried this via the adb shell
flash_image system system.img
Can't read device: "/dev/block/mmcblk0"
Error in reading mbr!
failed with error: -1
Question
Is it because there is a problem with the MBR that i can not write the system or data files? Is there a way to fix the MBR?
Any suggestions or information would be greatly appreciated!
What I have
Mytouch 4g
T-Mobile
Clockwork 3.0.24
After doing a little more digging I found that some people had luck with putting the PD15IMG.zip in the root directory of the SDcard. This will restore the phone back to factory default when holding the volume down and power button at the same time.
I went ahead and tried this and when trying to restore it I get a FAIL-PU, FAIL-PU FAIL-PU when loading for bootloader down to system.
Anyone have any other recommendations of what I can try? Seems like I might have a expensive paper weight on my hands
I've found only one instance of this so far in the development forum by user malickie but they seem to have just returned the phone and I don't believe it's unfixable.
It all started by my trying to update while retaining root without flashing a stock 2.3.5. I tried the "three lines of code method", editing from within the phone using either FX or ES explorer (one initially wouldn't paste back into /system/bin after I made a backup on the sd card).
When I tried to update it got as far as the recovery image, the android with the folder and arrow, and eventually crashed telling me I had invalid this and that; CDROM, SYSTEM, WEBTOP. Sorry, I don't remember the specifics. I shut it down and it bootlooped as far as the AT&T logo droplet thing.
I launched into forum scrounging mode, got RSD Lite 5.6, the FXZ, the update.zip, and flashed back to 2.3.5. The first time I shut down after this it bootlooped again. So I flashed it again, so far so good, so I figured I'd go ahead and update to 2.3.6. More bad luck as it tells me "insufficient memory please factory reset". I try this, and it goes into fastboot telling me "Invalid CG (cg: recovery)".
So, I've been scrounging all day trying to figure out if this issue has been solved to no avail Does anyone have any suggestions?
ri4naire said:
I've found only one instance of this so far in the development forum by user malickie but they seem to have just returned the phone and I don't believe it's unfixable.
It all started by my trying to update while retaining root without flashing a stock 2.3.5. I tried the "three lines of code method", editing from within the phone using either FX or ES explorer (one initially wouldn't paste back into /system/bin after I made a backup on the sd card).
When I tried to update it got as far as the recovery image, the android with the folder and arrow, and eventually crashed telling me I had invalid this and that; CDROM, SYSTEM, WEBTOP. Sorry, I don't remember the specifics. I shut it down and it bootlooped as far as the AT&T logo droplet thing.
I launched into forum scrounging mode, got RSD Lite 5.6, the FXZ, the update.zip, and flashed back to 2.3.5. The first time I shut down after this it bootlooped again. So I flashed it again, so far so good, so I figured I'd go ahead and update to 2.3.6. More bad luck as it tells me "insufficient memory please factory reset". I try this, and it goes into fastboot telling me "Invalid CG (cg: recovery)".
So, I've been scrounging all day trying to figure out if this issue has been solved to no avail Does anyone have any suggestions?
Click to expand...
Click to collapse
I hate to say it, but it sounds like you might have a bad phone.
But you can try using the beginner thread and use the directions there to flash the fxz, but try unzipping the fxz and then go into RSD lite and click on the "..." button, and then select the xml file and start flashing.
If that does not work, there is another way, but you have to be VERY careful, because this can hard-brick your phone.
Last ditch, but ONLY if the others don't work, do this:
Make sure your have the android sdk installed:
http://developer.android.com/sdk/index.html
Then go grab this, and put in the same directory as the SDK installed to, under platform-tools:
http://forum.xda-developers.com/attachment.php?attachmentid=890596
Then open a command line in the directory that you saved and unzipped the fxz in, then;
put your phone in fastboot mode, connect the USB cable, and:
Code:
[FONT=monospace]
[/FONT]fastboot erase userdata
fastboot erase cache
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash preinstall preinstall.img
fastboot reboot
No guarantees this will work
The first two work fine, returning "OKAY". However, if I try any type of flashing from the cmd prompt I get a "FAILED".
Code:
C:\*\InlineFlashing_etc>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.355s]
finished. total time: 0.356s
C:***>fastboot erase cache
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.020s
C:***>fastboot flash system system.img
sending 'system' (491264 KB)...
OKAY [ 17.982s]
writing 'system'...
(bootloader) Preflash validation failure
FAILED (remote: )
finished. total time: 18.212s
I realize we have a locked bootloader so is there a step I might have missed? I flashed back the updated fxz (that's now 18 steps instead of 20, and PS. this renders me with a functional phone, just not one that can update) and luckily I can seem to get back to at least this state consistently.
Ok, so I tried rooting in this state and used the ADB method from the Beginners' Guide to attempt to retain root through the update. This time there was nothing about insufficient memory, it just downloaded the update and then tried to reboot for the install but instead of going to unzip the package it goes straight back to fastboot flash mode with another failure.
Code:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.65
Battery OK
OK to Program
Connect USB
Data Cable
On the bright side it's not taunting me with invalid partitions but then again it won't boot normally either. I'm stuck on this screen.
Try pulling the battery and then booting into boot selection mode. (Press+hold volume buttons, then power button) and select "normal boot".
If that doesn't work then flash the fxz... again.
Did you do manual or one-click root?
Sent from my MB865 using Tapatalk
Ok, I had to plug it in overnight, making sure not to press the power button because it would go into "AP Fastboot", because my battery ran low. I'm flashing the updated FXZ again right now.
I've only ever done the One-Click Root. The first time I tried to retain root, what started all this, was using only the phone. This last time I used the ADB method and it didn't demand I factory reset.
Interestingly, when I tried that factory reset that's when it told me my recovery image wasn't good. I've noticed that the FXZ doesn't flash recovery.img but it does flash system, boot, and preinstall. So, is it possible I could manipulate that file to perform the steps you, Jim, suggested? I should just need to create an MD5 sum and follow the template of the rest of the time, right?
Hi.
I had problems with adb connect in twrp ics so i flashed cwm via fastboot to see if it made any difference. I didn't. It was just driver issue but thats not the trouble. When I was done I wanted to delete cwm cause I dont want to have them both installed. So dumb as I was I went to parted mmcblk0 in adb shell and removed number 6 as it is the recovery partition. Then i wanted to flash twrp via fastboot but ofcourse it gives me the error that the remote partition does not exist. And also now, the phone shows lg logo for a second and then shuts off.
I know I can flash ICS xbsa.bin from flashtool to write all partitions again but then I will loose my data that I havent saved.
So my question is. How can I make a new recovery partition on the mmcblk0 if I can only acces fastboot or download mode?
Edit: when i run
fastboot oem part-list
in fastboot it gives me the error:
...
FAILED(remote failure)
finished. total time 0.00s
Why cant I see my partitions?
Flashed stock ICS. Got tired of waiting lol
Booting now.
Will never do the same mistake again
I used the toolkit to flash the stock CM image as phone is stuck at one plus one logo . Flashing the stock worked without any errors after phone rebooted it's still stuck in bootloop. Is that means phone needs RMA, I can get into fastboot and recovery ..
I think you should come take a peak at my thread. Your issue sounds familiar
http://forum.xda-developers.com/showthread.php?p=55488755
So by issuing these commands
fastboot erase persist
fastboot flash persist persist.img
and flashing OS will fix the bootloop issue ??
I am getting this error " finished. total time: 0.009s
error: failed to load 'cm-11.0-XNPH30O-bacon-signed-fastboot.zip': No such file
or directory" but the file is in the location ..
sguy156 said:
I am getting this error " finished. total time: 0.009s
error: failed to load 'cm-11.0-XNPH30O-bacon-signed-fastboot.zip': No such file
or directory" but the file is in the location ..
Click to expand...
Click to collapse
Did you try rebooting after flashing the persist?
If yes and you still have no is download 38r and flash it instead
https://forums.oneplus.net/threads/38r-factory-images-now-available.147875/
Having major issues. The bootloader on this device is locked and I accidentally flashed The wrong firmware. Now I just get a " failed to validate boot img failed" message. Cannot flash anything except for bootloader.img and a few other files in the stock firmware.