Hey,
Yesterday I got a sort-of-refurbished Nexus S (I9023) which was apparently not in such a good shape...
Had problems flashing the system and userdata partitions (kept saying they were flashed fine but after reboot went back to their previous state).
Stupidly, I followed some tip without actually reading up on it and ended up formatting my bootloader partition.
Now, what I get is just a black screen no response or anything but using a tool called UnBrickable Mod I can get it back to fastboot mode and then boot into a recovery image and have adb access.
All in all, I am currently stuck cuz I want to flash a new bootloader image but what i get when i do that is:
Code:
~ # nandwrite /dev/mtd/mtd0 /bootloader.img
Skipping bad block at 0x00000000
Skipping bad block at 0x00040000
Skipping bad block at 0x00080000
Skipping bad block at 0x000c0000
Writing at 0x00100000
Writing at 0x00140000
Writing at 0x00180000
Writing at 0x001c0000
nandwrite: not enough space in MTD device
I have read that NAND blocks tend to go bad when continuously being flashed, but 50% bad blocks on the bootloader partition? Seems pretty unlucky...
Anyone know any solution for this?
Is it possible to resize the partitions without any JTAGing or writing custom bootloaders?
Thanks for trying to help!
BUMP
Help?
I had MultiROM on my phone, 2 roms, AOSP+RRO and SkyDragon GPE. I was booted into my AOSP+RRO ROM on MultiROM. I was calling someone. I missdialed and tried to hang up. The screen was black and there was still audio coming out, assmuning it was a small detection bug, I tapped the screen a few times, then I hard reset it after it didn't turn the screen back on, when I hardreset, it booted straight into SkyDragon and not MultiROM, When SkyDragon booted it said my phone was encrypted. I typed in random gibber(I didn't have the phone encrypted in the first place) and it said the password was correct however my data was corrupt. It booted into TWRP to try and factory reset, TWRP could not mount /data or /data/media. I tried erasing from fastboot, however I got the error FAILED (command write failed (Bad file descriptor)).
I have tried everything I know I can do to fix this, I think it may be a hardware issue, however, before I give up hope on the device, can anyone here, anyone, help me in the recovery process, or atleast find a way to salvage what is now an expensive paperweight?
I just dealt with some weirdness with my M8 last week. Let the battery go completely dead, I mean completely. Then connect the phone to computer and wait about half an hour. If it's a Windows machine it will probably do the chime thing when it actually resets itself.
In my case it took about thirty minutes of it being connected then ding, I looked over at the phone and it said charging 1% in the off screen.
Mine just died out of the blue. It was doing weird stuff the night before and I figured I'd just so a clean flash in the morning. I woke up and it was completely dead I wasn't able to do anything with it. I bought a cheap phone since I was waiting for the new phones coming out in a month anyway.
A couple days later I was working on a couple of phones and I pulled my sim out the m8 since I was sitting at one of my computers I figured what the hell I'll plug it in just in case...
When all this happened I let it get to 15% then attempted to boot it which it did. It acting like I had wiped all the caches doing the android apps update thing at first but now it's working fine.
I really don't know if this will help you, but I hope it does...
dank101 said:
It booted into TWRP to try and factory reset, TWRP could not mount /data or /data/media. I tried erasing from fastboot, however I got the error FAILED (command write failed (Bad file descriptor)).
Click to expand...
Click to collapse
Try booting into TWRP, pick the Wipe option, select Advanced, and try the option to format internal storage; and see if that helps.
redpoint73 said:
Try booting into TWRP, pick the Wipe option, select Advanced, and try the option to format internal storage; and see if that helps.
Click to expand...
Click to collapse
/data/media IS the internal storage.
dank101 said:
/data/media IS the internal storage.
Click to expand...
Click to collapse
I know. The format I suggested is a known fix for not being able to mount (corrupted) internal storage; at least in some cases.
redpoint73 said:
I know. The format I suggested is a known fix for not being able to mount (corrupted) internal storage; at least in some cases.
Click to expand...
Click to collapse
Did nothing.
I have a replacement One M8 on it's way!
Dear members,
Got this device which belongs to a friend. It's got stock at erasing. The exact procedure performed to get this far is not clear for me by now. I can't tell if it was during attempt to hard reset or flashing new rom. It can be shutdown but second after it kick back on, first om the Gigaset logo for few seconds( during which the PC identifies it as MT65xx preloader). Then directly to erasing screen, and thus lose connection to PC. Any way/ work around this issue or just put it on shelf for part.
I let it sit on erasing screen now for almost 4 days ( yes 4 days ) with no result as of some others mentioned it took them somewhere up to 22 hours to get passed the erasing.
Anyway to kick it out of this, and get a fresh install?
Hi all
For the last 5 days I have been struggling with my tf103c (which I am very much regretting having purchased in the first place!)
Basically I tried installing Xposed on it so I could try and tweak some of the very lacklustre performance.
However this was incompatible with my email client so I set about removing it.
Long story short I can do is get to a bootloader screen, however without the ability to reflash from SD card or wipe data or anything useful.
I can also get into the recovery screen (or the "Recovery starting..." screen) and can execute fastboot commands sent from my pc via usb from there.
Unfortunately all my attempts to reflash or update, at best lead me to the FAILED (remote: flash_cmds error! )
Which is where I'm now stuck.
I've tried various fimwares and techniques but without any further luck.
I was on the official 5.0 lollipop WW version from the Asus support page but trying to load this from fatboot leads to the same error.
Any suggestions please?
No one have any advice?
Come on - can somebody please help?
Alright guys,
Over the past couple days I've been consistently trying to root my Pixel 2 XL. Everything seems to be going fine until I reach the very last step of the root; flashing the patched boot image. Upon entering the command "*./fastboot flash boot patched\_boot.img*" into Windows Powershell, I am greeted with the following error messages (they seem to vary every attempt):
***fastboot: error: Failed to identify current slot***
***Sending 'boot' FAILED (remote: unknown command)***
Along with those, there's another error that says something about reaching the maximum file size. **My bootloader is both unlocked and critical unlocked.**
I've done some research and a few people seemed to have luck playing around with their USB ports (switching out cables and such) - unfortunately this method did not work for me.
I would *extremely* appreciate any help on this as I would love to get the problem solved.