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?
Related
I basically was attempting to make my custom rom, or flavor it and what not. but basically what happens now is it goes into a boot loop.
It just says HTC, sits for a second, screen goes black and repeats. it doesn't even get to the boot animation, so logcat doesn't even detect the device for some reason.
I unplug it, start cmd in my SDK dir.
type 'adb logcat' and it just says -waiting for device-
never detects it. heres the recovery.log from the flash
http://pastebin.com/fjzEt7F2
absolutelygrim said:
I basically was attempting to make my custom rom, or flavor it and what not. but basically what happens now is it goes into a boot loop.
It just says HTC, sits for a second, screen goes black and repeats. it doesn't even get to the boot animation, so logcat doesn't even detect the device for some reason.
I unplug it, start cmd in my SDK dir.
type 'adb logcat' and it just says -waiting for device-
never detects it. heres the recovery.log from the flash
http://pastebin.com/fjzEt7F2
Click to expand...
Click to collapse
Quick look at log implies a corrupt zip file. Suggest removing existing file and replace. Go into recovery and try to re-install.
yea ive tried that. tried rebuilding it and what not. same things keep happening.
any idea what this means?
mtd: not erasing bad block at 0x01700000
bad block, if anything like a HDD, something going bad?
absolutelygrim said:
yea ive tried that. tried rebuilding it and what not. same things keep happening.
any idea what this means?
mtd: not erasing bad block at 0x01700000
bad block, if anything like a HDD, something going bad?
Click to expand...
Click to collapse
Might suggest renaming the files - if a bad block is involved - it will be covered up with the current file.
Recompile and then move to sd card. Remember to rename the file on the sd card as well so if a bad block is there, you have it covered as well.
Good luck.
Hi all,
I rooted and installed CM 10.1.x RC2 on my S3 for a bit more than 6 months ago and all went fine. The rom worked just fine, and it was like I got a new phone But bit by bit it started to reboot a random times and then the last day it rebooted and all my text messages was gone. No biggie I thought! But the next day it rebooted again but didn't get past the boot screen, where it says "Samsung Galaxy .....". No matter how long I waited I coundn't get it to start up. I managed to get it to CWM recovery mode but no matter what I did it kept saying:
E: Can't mount /cache/ recovery/ command
Warning: No file_contexts
E: Can't mount /cache/ recovery/ log
E: Can't open --------------=------------
...
...
...
...
E: Can't mount /sdcard/
So no matter what I did it wouldn't do anything!!!
So I tried to wipe everything (cache partition, calvick, facotry) but nothing happened.. I can't restore it or anything..
Then I tried with Odin by using EH03_full_odin.tar with atlas_v2.2.pit but it's stuck at "Set partition". Tried with both "Repartition" checked and unchecked. When unchecked it stuck at "NAND Write Start". So that didn't worked.
Then I tried this one: http://forum.xda-developers.com/showthread.php?t=2391616 and flash in Odin but that failed.
Then I find a International-GT-i9300-StockRecovery.tar but again failed..
So now I'm really lost, I dont know what to do!
Does anybody have an idea?
Thanks
Does anyone has a clue what do do?
Your emmc chip is damaged and partition structure lost. Either warranty repair or new motherboard required.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Your emmc chip is damaged and partition structure lost. Either warranty repair or new motherboard required.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Hmm not really what I wanted to hear But thanks for the reply
when ever i try to flash any image to the device rom fastboot says remote: flash write failure also when i lock bootloader then reboot the device it get back to it's origen lock status "unlocked"
I have tried so many tools and methods to have that image succeed with no luck !
I have tried to log into temporary twirp session then tried to wipe the data it says :field to mount storage ...data...etc
so many threads related to this issue are misleading and I will not give up by replacing motherboard since this is a softbrick issue related to corrupted partitioning i think so please XDA NERDS HELP!
device : nexus 5
cause : bootloop
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.