[REQUEST] Nandroid backup

[shuvarts]

Hi, can someone upload their nandroid backup files? I don't know how; but, the system on my phone is shown as 0MB. I used 4ext recovery to format all partition and decided to try Slim Bean (coming from Jelly Baby). The phone stuck on the slim bean loading page for about 10 minutes and I decided to take out the battery and restart. That's when the problem started.... I can still boot into 4ext recovery; but, it says the recovery is in safe mode and I need to format the system. When I tried to re format all my partition I got "make_extf4fs failed on dev/block/mmcblk0p25" message.

I have tried to just ignore the message, flash a ROM; but, it won't boot. When I go to "info" on 4ext recovery it says that system, data, and cache size are all --MiB (which I think means that there is no data there).

I have tried to push the system.img from http://forum.xda-developers.com/showthread.php?t=1085624 to the /dev/block based on some google search and it still failed.

I also tried to do an RUU using the T-Mobile Froyo stock rom found in this thread: http://forum.xda-developers.com/showthread.php?t=1178912. When I tried to do update it, it just says it failed in my phone and the only option left is to reboot.

I am able to access the recovery; so, my last option is to try a nandroid backup. I thoughtI got a nandroid backup when I tried to do this whole thing and turned out I don't have one.... So, any help on uploading the file is truly appreciated. This is pretty much the last thing I hope will work....

 

[demkantor]

I doubt a nandroid would do anything, can you post all info from bootloader screen?
Also see here

http://forum.xda-developers.com/showthread.php?p=43195539
You will find links to a bunch of info including toward the bottom of the first post there is a link to important brick info, I suggest reading through this as well
Sent from my Nexus 4 using xda premium

 

[shuvarts]

Here are some information about my bootloader recovery, etc

S-off
HBOOT - 0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot

4ext recovery touch v1.0.0.5 RC5


Thanks for the link. I read some other similar thread and so far, I think I tried most of them.... For whatever reason even after flashing a fresh rom, pushing system.img that I previously mentioned does not help.

When I check on "info" in 4ext recovery, it shows that system, data, and cache size are all "--MiB"

 

[demkantor]

Does the bootloader say ship soff or eng soff?
Also can you confirm you used gfree to root?

Sent from my Nexus 4 using xda premium

 

[shuvarts]

Does the bootloader say ship soff or eng soff?
Also can you confirm you used gfree to root?

Sent from my Nexus 4 using xda premium

It says Vision pvt eng S-off.

I don't remember which method I used to root since it has been more than a year ago. But, I think it was gfree because I remembered reading somewhere that root using visionary has a chance to brick the device...

 

[demkantor]

Feel free to try one of the custom PC10IMG.zips I made, youll find a link in the brick thread (post thirty I believe) also has instruction on how to test if you used gfree to exploit (although others have used it and reported it works without true s-off, I'm just overly cautious at times)

Sent from my Nexus 4 using xda premium

 

[shuvarts]

Feel free to try one of the custom PC10IMG.zips I made, youll find a link in the brick thread (post thirty I believe) also has instruction on how to test if you used gfree to exploit (although others have used it and reported it works without true s-off, I'm just overly cautious at times)

Sent from my Nexus 4 using xda premium

So, I got the same result with your PC10IMG.zip with the other PC10IMG.zip that I've tried.
When I choose to update, it just says -Fail-PU on the first one (which is the bootlader). This is how it looks:


Parsing... [SD ZIP]
[1] BOOTLOADER - Fail-PU
[2] RADIO_V2
[3] RADIO_CUST
[4] RECOVERY
[5] SPLASH1
[6] TP
[7] TP

 

[demkantor]

So there is an hboot error, there is a link on how to use fastboot in the first link I sent you. Tell me what happens when you use fastboot to flash either the engineering bootloader for the g2 or dz (links and md5dums are there as well)

Sent from my Nexus 4 using xda premium

 

[shuvarts]

So there is an hboot error, there is a link on how to use fastboot in the first link I sent you. Tell me what happens when you use fastboot to flash either the engineering bootloader for the g2 or dz (links and md5dums are there as well)

Sent from my Nexus 4 using xda premium

Hmm, I haven't tried flashing the engineering hboot yet. I will try to flash that through fastboot later today when I got home. Hope this works :good:

 

[shuvarts]

So there is an hboot error, there is a link on how to use fastboot in the first link I sent you. Tell me what happens when you use fastboot to flash either the engineering bootloader for the g2 or dz (links and md5dums are there as well)

Sent from my Nexus 4 using xda premium

When I tried to flash the hboot, I used command "fastboot flash hboot g2hboot.img"

The result is:
sending 'hboot' (1024 KB)... OKAY
writing 'hboot'... FAILED (remote: image update error)

Any clue on what else I should do that might help this old phone?

 

[demkantor]

Check and see which emmc you have, instructions are in the link I provided earlier

Sent from my Nexus 4 using xda premium

 

[shuvarts]

Check and see which emmc you have, instructions are in the link I provided earlier

Sent from my Nexus 4 using xda premium

All I got is
'grep' is not recognized as an internal or external command,
operable program or batch file.

All the other adb command works so far; but, I don't know what happened with this grep is not recognized.... Do I need to update my android sdk? Or is it something else?


Edit:
Nevermind... I just re-tried it by separating the adb shell command following this thread that I found: http://forum.xda-developers.com/showthread.php?t=1854558
I followed both of the commands and for the first one which is:
adb shell
dmesg | grep mmc0

I got good result (as in the internal is not fried, I think); but using the second command (which seems to be the same with your thread), this is what I got:

C:\android-sdk-windows\platform-tools>adb shell
~ # cat /proc/kmsg | grep 'mmc0:0001'
cat /proc/kmsg | grep 'mmc0:0001'
<6>[ 6.152069] mmcblk0: mmc0:0001 M4G2DE 2.04 GiB

Does that mean I just got a bad luck with that chip and there is no salvation for this phone?

 

[demkantor]

That chip has a very high brick rate, with the issues your having my guess is its fried, sorry

Sent from my Nexus 4 using xda premium

 

[shuvarts]

That chip has a very high brick rate, with the issues your having my guess is its fried, sorry

Sent from my Nexus 4 using xda premium

Well... I guess that's just my luck.... Thanks for the help!
Is there anything else that might worth a shot?

 

[demkantor]

you could try to boot off sd card, There is info on how to in the first link i sent, which may not work if your bootloader partition is whats fried, but worth a shot anyway
best of luck!