Related
I've done quite a few searches and ended up here every time:
forum.xda-developers.com/showthread.php?t=502010
forum.xda-developers.com/showthread.php?t=517874
forum.xda-developers.com/showthread.php?t=543617
I'm starting to drive myself crazy here because I successfully did this once. Here's my issue, I've been playing around with Cyanogen Mod and I was doing some tweaking and for whatever reason I got stuck in a reboot loop. Well, since I couldn't get anything else to work, I wiped my SD:Ext using:
Code:
`mke2fs -j /dev/block/mmcblk0p2`
After that, I installed Enomther`s [ROM] TheOfficial Nexus1 - v1.8.1, Release 1.8.1 and everything seemed to be working fine. For some reason, I got in a reboot loop so I did a nand restore and went back to the stock 2.1 Android OS (ERE27). Unfortunately now I can't get anything to work again. Here's what I'm running into, when I open a shell, mke2fs is no longer a command nor does "mount -o rw /dev/block/mmcblk0p2 /system/sd" work as mount gives me a "usage" error. I don't know what all this talk is about /dev/block/mmcblk0p2" is but that doesn't exist. All I have in /dev/block is mmcblk0 and mmcblk0p1. When using the mount command, I do change mmcblk0p2 to an mmcblk* that exists in /dev/block/.
I'm really at a loss here because all I want to do is wipe my SD card like the guides tell me to so I can reflash my rom but I can't figure it out. These mount and mke2fs commands worked the last time I tried to do this but right now I'm stuck
No one can help? I've posted this up in two different forums and not one person can help?
Have you tried deleting all the partitions & recreating them from scratch? Parted seems to be reliable & is nice & simple to use. Try this guide. If your current ROM doesn't include parted, try doing this from Recovery as there's a fair chance it will. I suggest you stick to the instructions & don't improvise commands unless you're very sure you know what you're doing.
[Q] LG P506 AT&T Thrive Help Request - Post Unroot, Attempt @ 2.2.2 update, ~bricked
Hello,
Newbie. Bought a LG P506 AT&T as learner Android phone. Learn here, make mistakes on cheaper phone than fancy Galaxy SII etc.
Well, Learning how to root, add recovery, backup and such. Started looking at Android App dev, loaded the tools (took forever), haven't done "Hello World" yet.
Read this forum. Too much at time.
Wanted to see if I had a handle on this ROM thing. I didn't. Despite backup labled "before xxx", I'm still stuck.
Rooted Phone .. running 2.2.1
did root things for weeks, backups made, recovery added
made the WiFi work with AD-Hoc WIFI (very nice)
Well life was good.
Wanted to experience update 2.2.2
Unrooted the phone & verified.
Connect up to AT&T for the 2.2.2
Problem with install day 1.
Cleared some storage. Double checked my backup copied to PC.
Day 2 (24hours later BS)
Connect to AT&T for update 2.2.2
It installed and ALL HAPPY ... but reboot and now stuck in recovery
Look around through forum. The Thrive developer pages had ROM. Recovery installs it, but reboot still bring up the recovery menu.
Restoring my backup works, but reboot still brings up recovery menu.
DO not feel I have the ABD and fastboot stuff loaded properly on PC. Seems like some things have moved around. Sorted out some of that. Have fastboot and ABD ... in a folder ready on PC. I can get fastbook running on Thrive.
Would like a little expert help to sort the right URLs I should follow. Or who would be up for little 1:1 chat to speed me along.
Thanks in advance.
What recovery do you have? CWM or amon ra?
Did you try this?
Additional Details to P506 Issue
Hi,
Yes, I found that URL/link and followed, as best I understood.
Since my original post, I learned how to make ADB and fastboot work and come up.
I feel I have followed the 3 steps from the suggest link. No change, phone still boots into recovery or with power+home into fastboot.
The phone boots into ClockworkMod Recovery V3.1.0.0
Flashing a P506 stock ROM .img (link from this forum) actually made the weird color issue go away. It is now a lovely orange.
Phone seems alive enough. I can browse directories on the phone and SD-Card.
What additional data would you like?
Might be newbie oversight.
Thanks raenye for reply
Updated Information P506 POST 2.2.2 (not Bricked)
Reading and searching forums here, So it seems that the LG P506 is not bricked. Too much functionality ... into CWM Recovery, into fastboot, into emergency mode (not sure of uses).
CWM Recovery V3.1.0.0 reboots shows E:Bad boot message "recovery " ... which might be a red herring. May not real issue.
Restoring my backup hasn't helped.
Restoring the CWM3100-p506-recovery.img hasn't helped.
Question: Could the OS or boot or config be corrupt/missing ... something from original rooted 2.2.1 OS conflicting with AT&T 2.2.2 OS Update (succeeded, but booted into recovery ever since).
Is this init.rc workable for normal boot?
Is this the correct contents for init.rc to make a normal boot possible?
--- Init.rc ---
on early-init
start ueventd
on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
symlink /system/etc /etc
mkdir /boot
mkdir /sdcard
mkdir /sd-ext
mkdir /datadata
mkdir /emmc
mkdir /system
mkdir /data
mkdir /cache
mount /tmp /tmp tmpfs
on boot
ifup lo
hostname localhost
domainname localdomain
class_start default
service ueventd /sbin/ueventd
critical
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
disabled
on propertyersist.service.adb.enable=1
start adbd
on propertyersist.service.adb.enable=0
stop adbd
This is the same issue I've been having. Ive flashed multiple roms reporting success, but still makes it back to recovery. Cleared the cache, master reset, all the same. Considering sending it in for a warranty replacement.
Thanks for affirmation of Thrive P506 Problem post 2.2.2 update
Thanks for taking the time to reply. Not alone.
Yep, Phone otherwise seems functional. I have to wonder if the boot process is just running an incomplete script. Missing that magic part that says RUN KERNEL.
Hoped that someone with the know-how would offer up a consult or tool to lend a land.
Newbie struggle perhaps...
Follow UP - P506 mtd verus P500 mtd
Don't feel this P506 is bricked, but perhaps just not configured right.
I read the the mtd (fuzzy are they mounts?) are different between a LG P506 Thrive and regular LG Optimus one.
Could this make a phone not boot? ... but into recovery and still do restores, but not running right?
Currently after successful restore (after restore) with CWM Recovery v3.1.0.0 .... I have the following mtd
cat proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
Which is just like a regular LG optimus which I infer is wrong for a P506 Thrive.
Reference URLs:
http://forum.xda-developers.com/archive/index.php/t-1114472.html
http://forum.xda-developers.com/archive/index.php/t-1114472.html
Report mtd for Stock P506 Thrive
------------------------------------------
( The partitions are in a different order for this phone than for other phones. For example, when I did my image pull of a clean, stock Thrive, I got the following mtd partitions:
mtd0 = boot
mtd1 = system
mtd2 = recovery
mtd3 = lgdrm
mtd4 = splash
mtd5 = FOTABIN
mtd6 = FOTA
mtd7 = misc
mtd8 = cache
mtd9 = userdata The two (unexpected) partitions, as far as order goes, were system and cache; at least, they are unexpectedly located at mtd1 and mtd8, respectively, as compared to their respective locations on the Optimus V (i.e., mtd7 and mtd2, respectively, on Optimus V). )
Question: Would that kind of swap keep the system from booting/running and stuck in recovery?
Bonus: Can these mtds be shifted around? And how?
SOLVED - LG P506 Trive WORKS - was LG P506 AT&T Thrive Help Request - Post Unroot ...
Thanks to the XDA Forum and users. With it I stitched together a solution and have returned my LG P506 (AT&T Thrive) to good working order with 2.2.2
This was my first Android learner phone, since I would soon need to know Android +/- for work.
Started with a backed up (and backed up) Rooted LG Thrive running 2.2.1 with CWM Recovery. Tried to unroot and return to stock (unfreeze AT&T bloatware, unroot, etc). The AT&T 2.2.2 over-the-air (OTA) was successful, but after reboot the P506 was stuck in a CWM boot-to-recovery mode.
All the fastboot commands, all the CWM recovery commands worked fine. New Custom Stock ROM 2.2.2 re-flashed fine, but the phone would still either boot to CWM Recovery to Fastboot-mode depending on Keys/buttons pressed at boot.
So phone wasn't bricked, but was stuck.
From this XDA forum (this and other XDA forum posting here and there). The Solution was found.
From another LG P506 thread here I got 2 files boot.img and system.img for LG P506 (I did use these files, but perhaps a full custom CWM ROM recovery would be good to -- These are the facts, you can refine)
From the LG Fastboot command I
>fastboot flash boot boot.img
>fastboot flash system system.img
Tried to boot but still stuck at CWM Recovery
POST AFTER POST here says wipe phone more or less. I did wipes with CWM Recovery. I was never really sure how to do enough but NOT TOO MUCH of a WIPE. Too timid as a noob, never tried to fastboot to erase.
LEARNED POINT: fastboot erase is/must-be different than CWM Recovery wipes/formats etc.
The LG P506 was a starter Android phone to learn on, build skill and make mistakes without wrecking an $800 phone.
I had seen another XDA Forum posting about the structure of the phone's file system ... it showed 'system' 'cache' 'userdata' 'misc' 'FOTABIN' 'FOTA' ... plus a few more.
HINDSIGHT: I looked for but could not find a good here is how ANDROID boots for this phone. (1) this .. (2) that ... (3) etc .. kernel, GUI, etc. I suspect I would have learned that something I erased below like FOTA or FOTABIN was running and dying throwing me into CWM Recovery.
I felt I had nothing to loose at this point and no matter what I tried I was (up to that point) still always able to get into CWM Recovery. CWM Recovery ROCKS!
The BREAK THROUGH....
In fastboot mode again.
>flastboot erase FOTA
>flastboot erase FOTABIN
>fastboot erase misc
>fastboot erase cache
>fastboot erase userdata
>fastboot reboot
... there was the LG P506 running 2.2.2 sans the AT&T bloatware. Battery needed recharged, so I took my son to House of Air in the Presidio in San Francisco for trampoline dodgeball.
Nearly 24 hours later the LG P506 Thrive is still working fine.
I suspect that (1) either the boot & system img were needed and something needed erased/wiped.
-- OR --
(2) something like FOTA and/or FOTABIN need erased first and foremost.
As newbie, I was not sure quite what to do at each turn. Using google, I struggled to find insightful android documentation for my problem that was current and not about older versions of ANDROID. The Forum experts use acronyms and speak at an expert-level at times, but the gist of what they shared feels/felt sound. But kind of hard to hear Babe-Ruth explain how to hit a HOME RUN and all together different thing to step into the batter's box and hit a HOME RUN.
Anyhow, the XDA FORUM ROCKS. The experts are EXPERT, I'm unworthy. THANK YOU FOR THE HELP.
AT&T Unlock Request
Please can someone help guide me on how to unlock my LG-P506 which is currently the AT&T Network. Thank you in advance.
Hi All,
I have been flashing back and forth a bit from CM9 to CM10 to try things out. Today, I attempted to restore back to CM9 and it hung for over an hour, so I hard restarted it. Now, I can't restore anything, because it hangs on the /cache partition. I also receive the message while in recovery mode
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
I am able to get adb shell in recovery mode and I have gone through the steps to check for a bad emmc, which did not indicate badness. I have attempted to use umount from the shell on /cache, which just hangs. In recovery mode, over adb shell, I can ls and cat any of the files in /cache without apparent issue.
I have attempted Super Wipe, factory reset, manual formatting, and wipe cache, all to no avail (they all just hang).
I am running CWM 6.0.1.1.
dmesg has a message about an ext4 error, that makes me suspicious, but I don't know what to do about it.
<4>[ 8.431030] EXT4-fs warning (device mmcblk0p26): ext4_clear_journal_err:4154: Filesystem error recorded from previous mount: IO failure
<4>[ 8.442413] EXT4-fs warning (device mmcblk0p26): ext4_clear_journal_err:4155: Marking fs in need of filesystem check.
<4>[ 8.462036] EXT4-fs (mmcblk0p26): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 8.475463] EXT4-fs (mmcblk0p26): recovery complete
<6>[ 8.489562] EXT4-fs (mmcblk0p26): mounted filesystem with ordered data mode. Opts:
<6>[ 9.242095] key released
<6>[ 9.243774] key released
<6>[ 9.442749] msmsdcc_runtime_suspend: Enter WIFI suspend
<6>[ 9.542755] fsa9480 5-0025: fsa9480_init_detect
<6>[ 9.547424] fsa9480 5-0025: dev1: 0x0, dev2: 0x0
<2>[ 13.382751] EXT4-fs error (device mmcblk0p26): ext4_init_inode_table:1293: comm ext4lazyinit: Something is wrong with group 0
<2>[ 13.382751] Used itable blocks: 403itable unused count: 0
<2>[ 13.382781]
<3>[ 13.411773] Aborting journal on device mmcblk0p26-8.
<2>[ 13.429321] EXT4-fs (mmcblk0p26): Remounting filesystem read-only
Click to expand...
Click to collapse
Apparently my full dmesg output was too long, so if you need anything else please ask.
Thanks in advance for any help!
I am experiencing the same thing (I think) as the OP.
I had been running alpha2 of TeamChopsticks CM10. I installed the new recovery for the skyrocket (downloaded from teamchopsticks.org). Then rebooted into recovery. formatted /system -> installed alpha3 -> installed gapps -> installed darkside-wipe-cache-only -> rebooted. Then my phone just hung on the boot animation for 10+ minutes.
After rebooting I thought I would try to install alpha2 again. I tried to format /system, and it hung.
So I rebooted again, and tried to restore a backup. That hung on "Restoring .android_secure..."
So, I rebooted again. This time I tried a factory reset. It hung on "Wiping cache..."
After rebooting this time, I selected "show log" in CWM, which shows this (I don't know if this is helpful/related):
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
I have also tried Fixing Permissions in CWM, with no apparent change.
Also, any time I perform an action in CWM (show logs, fix permissions, etc.) and select "go back" in the menu, the menu disappears. I am still in recovery (still see the CWM logo in the background, and see the text from my previous action), but buttons do nothing and there is no menu.
Any help would be appreciated.
Josh
---------- Post added at 10:58 AM ---------- Previous post was at 10:20 AM ----------
Another follow up to my previous post:
I have tried to reinstall cm9 and cm10 alpha2.
With each I format /system, then when I select "Go Back" in the CWM menu the menu disappears (as I mentioned before). So, I reboot, then install zip from SD -> select the cm zip and get this:
Code:
CWM-based Recovery v6.0.1.1
-- Installing: /sdcard/cm-9-20120715-EXPERIMENTAL-skyrocket-beta1.zip
And nothing after that. It will just sit there.
Don't use darkside wipe, reflash sk8ers recovery From his thread
Posted w/xda app w/ i727R
MY STICKIES
| ROMS | KERNELS | FIRMWARE | RADIOS | HOWTO'S | GUIDES | INFo |
NEWB GUIDES TO: RESTORE TO STOCK | USE ODIN | INSTALL CWM | ROOT |
vincom said:
Don't use darkside wipe, reflash sk8ers recovery From his thread
Click to expand...
Click to collapse
Interestingly (and perhaps ironically), looks like sk8er may be adding the Darkside Tools option in a forthcoming Recovery....
http://forum.xda-developers.com/showpost.php?p=30639023&postcount=267
That's pretty hilarious, so Darkside Wipe is apparently the way to go, except it doesn't work in my case.
So, I tried installing that recovery but it won't install (just like everything else).
I get this:
Code:
CWM-based Recovery v6.0.1.1
-- Installing: /sdcard/cwm6012touch_v11.zip
Is there a way to install his recovery that I am not aware of?
Thanks,
Josh
Fantastic! With some help from the TeamChopsticks IRC channel, particularly sk8erwitskil, I installed CWM Touch 6.0.1.2 and was able to restore a backup of CM9 without an issue. Now that I can do that, I'm going to give CM10 alpha 3 another go.
Please see http://forum.xda-developers.com/showthread.php?t=1777970 for any further help with the recovery.
Cheers!
cthrax said:
Fantastic! With some help from the TeamChopsticks IRC channel, particularly sk8erwitskil, I installed CWM Touch 6.0.1.2 and was able to restore a backup of CM9 without an issue. Now that I can do that, I'm going to give CM10 alpha 3 another go.
Please see http://forum.xda-developers.com/showthread.php?t=1777970 for any further help with the recovery.
Cheers!
Click to expand...
Click to collapse
Why could u install the recovery and what was the solution
Posted w/xda app w/ i727R
MY STICKIES
| ROMS | KERNELS | FIRMWARE | RADIOS | HOWTO'S | GUIDES | INFo |
NEWB GUIDES TO: RESTORE TO STOCK | USE ODIN | INSTALL CWM | ROOT |
I didn't do anything special to install recovery. I pushed the zip to my external card and installed it via the recovery. I assume the cache was not needed to be overwritten for the recovery install.
cthrax said:
I didn't do anything special to install recovery. I pushed the zip to my external card and installed it via the recovery. I assume the cache was not needed to be overwritten for the recovery install.
Click to expand...
Click to collapse
thats the way its done, i just dont understand why you couldnt do it the first place, and the cache has nothing todo with recovery just the rom
Ah, that's a confusion of terms. The original issue was that I could not restore from a backup. Or install a new rom. Apparently installing a new recovery was not an issue, I just didn't know that installing that would help at the time.
I just wanted to follow up that I was able to get my phone back thanks to help from Meanstreak242 in the IRC channel.
I ended up using an adb shell to dd the recovery image to the recovery partition (I *think* it was partition 22).
joshjryan said:
I just wanted to follow up that I was able to get my phone back thanks to help from Meanstreak242 in the IRC channel.
I ended up using an adb shell to dd the recovery image to the recovery partition (I *think* it was partition 22).
Click to expand...
Click to collapse
I'm gonna give this a go as well. Vin, seems you were onto something regarding usage in adb. I've been getting really familiar with it since. And now check out his results. Hopefully this'll work out for me too!!
KillaT21 said:
I'm gonna give this a go as well. Vin, seems you were onto something regarding usage in adb. I've been getting really familiar with it since. And now check out his results. Hopefully this'll work out for me too!!
Click to expand...
Click to collapse
Another no go. Cthrax, can you post or pm me exactly what you did?
KillaT21 said:
Another no go. Cthrax, can you post or pm me exactly what you did?
Click to expand...
Click to collapse
1. Mount phone as USB device
2. Copy newer version of ClockWorkMod Touch
3. Go back into recovery and "install zip from flash"
4. Reboot and restore backup.
5. Profit!
cthrax said:
1. Mount phone as USB device
2. Copy newer version of ClockWorkMod Touch
3. Go back into recovery and "install zip from flash"
4. Reboot and restore backup.
5. Profit!
Click to expand...
Click to collapse
well I didnt have the exact circumstance of doing a restore. I just need to format my partitions so that would hopefully allow me to flash something else. My system basically tries its hardest to stay as Read Only. Even when I mount the system, nothing. I was hoping that with a new recovery I could. It "flashes", but once i reboot, its the same o Clockworkmod Recovery v5.8.1.3
KillaT21 said:
well I didnt have the exact circumstance of doing a restore. I just need to format my partitions so that would hopefully allow me to flash something else. My system basically tries its hardest to stay as Read Only. Even when I mount the system, nothing. I was hoping that with a new recovery I could. It "flashes", but once i reboot, its the same o Clockworkmod Recovery v5.8.1.3
Click to expand...
Click to collapse
Maybe your variant of the problem is closer to what joshjryan did then. He had to use adb shell to manually use dd to copy the bits over. Hopefully he's watching and can chime in with some more comments.
Well, joshjryan, I hope youre reading this too.
This caught my attention after a dmesg:
<6>[ 1478.616302] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mod
e. Opts:
So then I
~ # parted /dev/block/mmcblk0p24
parted /dev/block/mmcblk0p24
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p24
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/block/mmcblk0p24: 627MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Could this be the cause??
Number Start End Size File system Flags
1 0.00B 627MB 627MB ext4
(parted)
cthrax said:
Maybe your variant of the problem is closer to what joshjryan did then. He had to use adb shell to manually use dd to copy the bits over. Hopefully he's watching and can chime in with some more comments.
Click to expand...
Click to collapse
This does sound similar to what I was seeing.
I also was not able to actually install the new recovery. So I did this:
I extracted cwm0612touch to get recovery.img
Then I mounted my phones SB by USB and copied recovery.img to my sd card
Then in the adb shell to my phone I used dd to copy the image to the appropriate partition
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
Hopefully that does the trick for you!
joshjryan said:
This does sound similar to what I was seeing.
I also was not able to actually install the new recovery. So I did this:
I extracted cwm0612touch to get recovery.img
Then I mounted my phones SB by USB and copied recovery.img to my sd card
Then in the adb shell to my phone I used dd to copy the image to the appropriate partition
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
Hopefully that does the trick for you!
Click to expand...
Click to collapse
It didnt. It installed to the right partition, but after reboot, cwmtouch5.8.1.3 is there again
Is it something in my reboot/boot that causes that?
Hey guys i have an n8010. When samsung released the leak fw for the 8000 I installed it. It worked pretty well. A few months ago an official update came for the 8010 but im using the 8000 bootloader i cannot install it Is that any solution for recovering the old bootloader? I've tried a lot of thing to solve it but none of them was successful. I've tried this method: http://forum.xda-developers.com/galaxy-note-10-1/help/recovering-n8010-leaked-locked-n8000-t2802516 and a lot of custom roms but i always have a same crash after using it for about 2 days. It says System UIDs Inconsistent, UIDs on the system are inconsistent you need to wipe your data partition or your device will be unstable. And if i press "I'm felling lucky" every app crashes touchwiz ,android everything.
Please help me to solve my problem
kataik95 said:
Hey guys i have an n8010. When samsung released the leak fw for the 8000 I installed it. It worked pretty well. A few months ago an official update came for the 8010 but im using the 8000 bootloader i cannot install it Is that any solution for recovering the old bootloader? I've tried a lot of thing to solve it but none of them was successful. I've tried this method: http://forum.xda-developers.com/galaxy-note-10-1/help/recovering-n8010-leaked-locked-n8000-t2802516 and a lot of custom roms but i always have a same crash after using it for about 2 days. It says System UIDs Inconsistent, UIDs on the system are inconsistent you need to wipe your data partition or your device will be unstable. And if i press "I'm felling lucky" every app crashes touchwiz ,android everything.
Please help me to solve my problem
Click to expand...
Click to collapse
I think your Stuck with the bootloader..
The issue about im feeling lucky thing... I think you have malware on your device... Never heard of or seen nothing like that
hi,
this is my backup of the jb bootloader for the n8013 [n801x]
http://d-h.st/users/moonbutt74/?fld_id=39849#files
cwm flashable
m
moonbutt74 said:
hi,
this is my backup of the jb bootloader for the n8013 [n801x]
http://d-h.st/users/moonbutt74/?fld_id=39849#files
cwm flashable
m
Click to expand...
Click to collapse
Thanks man i havent tried it yet but i hope it will help
Sent from my SM-G900F using XDA Free mobile app
Hi, well I have the n8010 model.
and while you install the version of n8000 leak.
so my bootloader remained in n8000.
and then, after much, I put the rom gnabo v6.
and a few days ago, my note I do not step beyond the samsung logo, stayed stagnant.
try putting on the rom again, but not carrying anything.
I made full format from the recovery of the internal sdcard.
did wipes and try to flash the rom, but not!
I went back to install the 4.4 leak of n8000, but nothing.
and I get the error: failed mount / efs (invalid argument)
that I can do? please help.
sorry for my English, I'm from mexico
FGM 11 said:
Hi, well I have the n8010 model.
and while you install the version of n8000 leak.
so my bootloader remained in n8000.
and then, after much, I put the rom gnabo v6.
and a few days ago, my note I do not step beyond the samsung logo, stayed stagnant.
try putting on the rom again, but not carrying anything.
I made full format from the recovery of the internal sdcard.
did wipes and try to flash the rom, but not!
I went back to install the 4.4 leak of n8000, but nothing.
and I get the error: failed mount / efs (invalid argument)
that I can do? please help.
sorry for my English, I'm from mexico
Click to expand...
Click to collapse
I tried everything but nothing helped. And now i have the same efs problem like you. I hope that somebody can help us
This worked for the galaxy tab 3 10.1
okay,
a while back i helped a user with a similar problem. this was my approach HOWEVER, the following conditions
must be met first.
1 you are able to boot into recovery and maintain normal operation including adb root shell access
2 you are able to charge your tab from a powered off state, mostly to see if you charging animation shows.
that means your kernel is intact-ish
3 you can boot into odin mode.
assuming the partion layouts for your respective devices match the red highlighted sections of this output from parted.
Code:
[email protected]:/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
[COLOR="Red"] 1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 41.9MB 8389kB PARAM[/COLOR]
5 41.9MB 50.3MB 8389kB BOOT
6 50.3MB 58.7MB 8389kB RECOVERY
7 58.7MB 92.3MB 33.6MB RADIO
8 92.3MB 931MB 839MB ext4 CACHE
9 931MB 2399MB 1468MB ext4 SYSTEM
10 2399MB 2923MB 524MB ext4 HIDDEN
11 2923MB 2932MB 8389kB OTA
12 2932MB 15.8GB 12.8GB ext4 USERDATA
(parted)
AND provided you can get someone competent with access to the respective models to open a root shell
on device or through adb and run the following command,
Code:
[COLOR="Red"]dd if=/dev/block/mmcblk0 of=/sdcard/fix.img bs=1 count=35221668[/COLOR]
AND zip the output fix.img and post it, again for the respective devices.
THEN you can through adb,
adb push fix.img /sdcard/
or
adb push fix.img /sdcard
or
adb push fix.img /data/media/0/
or
adb push fix.img /data/media/0
you can then navigate TO the directory you pushed the image to and execute the following
dd if=fix.img of=/dev/block/mmcblk0
the above approach worked for me in helping another user with a like device.
you assume the same risk you took previously to achieve the state your device is in now.
NOTE- count=35221668 is a hair under the actual end of /efs . you may need to adjust through param and into boot maybe
half way , but then you can just reflash kernel or then do a proper odin flash of stock. the fix.img will NOT be odin flashable.
m
partitions
moonbutt74 said:
okay,
a while back i helped a user with a similar problem. this was my approach HOWEVER, the following conditions
must be met first.
1 you are able to boot into recovery and maintain normal operation including adb root shell access
2 you are able to charge your tab from a powered off state, mostly to see if you charging animation shows.
that means your kernel is intact-ish
3 you can boot into odin mode.
assuming the partion layouts for your respective devices match the red highlighted sections of this output from parted.
Code:
[email protected]:/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
[COLOR="Red"] 1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 41.9MB 8389kB PARAM[/COLOR]
5 41.9MB 50.3MB 8389kB BOOT
6 50.3MB 58.7MB 8389kB RECOVERY
7 58.7MB 92.3MB 33.6MB RADIO
8 92.3MB 931MB 839MB ext4 CACHE
9 931MB 2399MB 1468MB ext4 SYSTEM
10 2399MB 2923MB 524MB ext4 HIDDEN
11 2923MB 2932MB 8389kB OTA
12 2932MB 15.8GB 12.8GB ext4 USERDATA
(parted)
AND provided you can get someone competent with access to the respective models to open a root shell
on device or through adb and run the following command,
Code:
[COLOR="Red"]dd if=/dev/block/mmcblk0 of=/sdcard/fix.img bs=1 count=35221668[/COLOR]
AND zip the output fix.img and post it, again for the respective devices.
THEN you can through adb,
adb push fix.img /sdcard/
or
adb push fix.img /sdcard
or
adb push fix.img /data/media/0/
or
adb push fix.img /data/media/0
you can then navigate TO the directory you pushed the image to and execute the following
dd if=fix.img of=/dev/block/mmcblk0
the above approach worked for me in helping another user with a like device.
you assume the same risk you took previously to achieve the state your device is in now.
NOTE- count=35221668 is a hair under the actual end of /efs . you may need to adjust through param and into boot maybe
half way , but then you can just reflash kernel or then do a proper odin flash of stock. the fix.img will NOT be odin flashable.
m
Click to expand...
Click to collapse
Well this is how my partitions look like: http://kepfeltoltes.hu/view/140928/partitions2_www.kepfeltoltes.hu_.png
Instructions Matter
kataik95 said:
Well this is how my partitions look like: http://kepfeltoltes.hu/view/140928/partitions2_www.kepfeltoltes.hu_.png
Click to expand...
Click to collapse
K,
i must stress the need for you to follow instructions, hear me out, I am operating on the assumption that you are
an experienced android user.
1 the archive with the bootloader data i provided was a cwm flashable zip file. to attempt a flashing of that file itself
or the img files contained within in any other fashion has likely made your problem worse. i also stated as per the
name of the file that it is for the n8013. it is good to hear that you have made some progress however instructions
are important because,
2 though you have succeeded in using parted through adb you have provided the wrong information.
instead of
parted /dev/block/mmcblk0p8
please run
parted /dev/block/mmcblk0
then at the (parted) prompt running print all wil return the correct information.
I mean the above in the best way, as well to stress the importance of doing these things correctly
to avoid a true hard-bricking of your device. You will need to go hat in hand and request an experienced/competent
user/developer pull the needed data from their device as stated in my previous post.
it is likely that the data pulled from my device may work, but that your device afterwards will register as an n8013.
please re-execute parted through adb as instructed for the needed information and we can move foward from there.
m
moonbutt74 said:
K,
i must stress the need for you to follow instructions, hear me out, I am operating on the assumption that you are
an experienced android user.
1 the archive with the bootloader data i provided was a cwm flashable zip file. to attempt a flashing of that file itself
or the img files contained within in any other fashion has likely made your problem worse. i also stated as per the
name of the file that it is for the n8013. it is good to hear that you have made some progress however instructions
are important because,
2 though you have succeeded in using parted through adb you have provided the wrong information.
instead of
parted /dev/block/mmcblk0p8
please run
parted /dev/block/mmcblk0
then at the (parted) prompt running print all wil return the correct information.
I mean the above in the best way, as well to stress the importance of doing these things correctly
to avoid a true hard-bricking of your device. You will need to go hat in hand and request an experienced/competent
user/developer pull the needed data from their device as stated in my previous post.
it is likely that the data pulled from my device may work, but that your device afterwards will register as an n8013.
please re-execute parted through adb as instructed for the needed information and we can move foward from there.
m
Click to expand...
Click to collapse
Thanks for all the help you gave me but I decided to take my tab to a service, they probably make it work
kataik95 said:
Thanks for all the help you gave me but I decided to take my tab to a service, they probably make it work
Click to expand...
Click to collapse
Sure, no problem. Hope everything works out. :good:
m
moonbutt74 said:
Sure, no problem. Hope everything works out. :good:
m
Click to expand...
Click to collapse
Imagine after 2 services where the could't fix I took to a 3rd. They could fix it so it works its on 4.0.4 in some kind of factory mode (strange). I can not quit from this mode and odin not works as well. In the recovery it says efs is invaild. What is that fw?
Good day,
I am having a lot of problems with flashing a recovery to my Samsung Galaxy s4 mini GT-I9190 and need help urgently please.
I have tried using odin but neither the computer or odin recognizes the phone when in recovery mode, I have tried all the solutions I could find on how to fix that but have come up empty handed.
Next I tried flashing the recovery using the fastboot method, when I enter adb devices it picks it up and everything goes great until about the last step when I type in: "fastboot flash recovery FILE.IMG" and the it says the following: "writing 'recovery'... failed (remote partition 'recovery' not support flash)". I tried solutions for that ass well but nothing seem to work as the cmd wont go further than that.
Then I tried flashing the recovery using the following cmd codes:
cd\
cd c:\androidsdk\tools
adb push recovery.img /sdcard
adb push flash_image /sdcard
adb shell
su
mount
mount -o remount,exec /dev/block//vold/179:1 /sdcard - first of all here the path is not sdcard but "/data/sdext2 ext2 rw,"(don't remember the last word), then it works and I can go on to the next step which is:
cd /sdcard - I can not get past this step as the cmd keeps saying that the path is not found, I got past this once but then it said the same thing at the following step
./flash_image recovery /sdcard/recovery.img
I have been trying to flash a custom recovery for weeks now because I want to flash a new ROM as the one that is on the phone is infected with adware and I also accidentally uninstalled the contacts storage, I searched how to fix that and all I got was to flash a new ROM.
I am completely out of options of methods to try and everything I search keeps giving the same methods that have failed me.
Please can someone help me with this, I would appreciate it so much!!!! I am completely out of hope and think that this phone is a piece of garbage by now, please help!!!!
XDA Visitor said:
Good day,
I am having a lot of problems with flashing a recovery to my Samsung Galaxy s4 mini GT-I9190 and need help urgently please.
I have tried using odin but neither the computer or odin recognizes the phone when in recovery mode, I have tried all the solutions I could find on how to fix that but have come up empty handed.
Next I tried flashing the recovery using the fastboot method, when I enter adb devices it picks it up and everything goes great until about the last step when I type in: "fastboot flash recovery FILE.IMG" and the it says the following: "writing 'recovery'... failed (remote partition 'recovery' not support flash)". I tried solutions for that ass well but nothing seem to work as the cmd wont go further than that.
Then I tried flashing the recovery using the following cmd codes:
cd\
cd c:\androidsdk\tools
adb push recovery.img /sdcard
adb push flash_image /sdcard
adb shell
su
mount
mount -o remount,exec /dev/block//vold/179:1 /sdcard - first of all here the path is not sdcard but "/data/sdext2 ext2 rw,"(don't remember the last word), then it works and I can go on to the next step which is:
cd /sdcard - I can not get past this step as the cmd keeps saying that the path is not found, I got past this once but then it said the same thing at the following step
./flash_image recovery /sdcard/recovery.img
I have been trying to flash a custom recovery for weeks now because I want to flash a new ROM as the one that is on the phone is infected with adware and I also accidentally uninstalled the contacts storage, I searched how to fix that and all I got was to flash a new ROM.
I am completely out of options of methods to try and everything I search keeps giving the same methods that have failed me.
Please can someone help me with this, I would appreciate it so much!!!! I am completely out of hope and think that this phone is a piece of garbage by now, please help!!!!
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
First, please create an account so you can post in other forums.
Here is your device's main forum area:
(You should bookmark this)
http://forum.xda-developers.com/galaxy-s4-mini
After creating your account, please ask for help here:
http://forum.xda-developers.com/galaxy-s4-mini/help
The experts for your device are located there and will be able to help.
Remember, please wait at least 24 hours for a response before bumping your post.
Good luck!