Does anyone know how to restore mtd to bml through adb?
i bricked a phone and cant get into DL mode and it just loops to cwm. now before everyone starts sending me links to tools and odin images to fix this, just stop. cause i know its a formatting error.
it seems when i mount the device in adb it says the /cache partition is ext4
here is the recovery log(i know its not this phone but the best devs i know are in here)
http://pastebin.com/wVtxEqw4
is there a way i could adb push the boot.img systemrfs and others? or am i sol?
I recall a thread somewhere in the abyss of this forum that gave the complete partition layout for our device, and shows how to use adb and whatnot for pushing files to said partitions.
You might want to start getting crafty with your search queries to try and locate that info.
Related
USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....
So far i got ahold of the previous Clockwork before the touch came out but it doesnt have options for external and internal im still allowed to mount externalSD card but whats the for if you cannot ADB with clockwork nor install from exernal SD?
Thanks for your time guys
xgp0006 said:
USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....
Click to expand...
Click to collapse
You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?
I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
B-Naughty said:
You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?
Click to expand...
Click to collapse
xgp0006 said:
I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
Click to expand...
Click to collapse
If you're already running CWM, try the wiping and fix permissions before ODIN flash to stock with the TMobile image
Hey guys,
My password isn't working (never did) and I can't get much done in my phone. What to do?
So I was running CM11 on my LS980 and things were working great. I had a nandroid of the rooted stock software on my PC, and decided to encrypt my phone.
So I tried to encrypt my phone, the encryption went well (I think), but when I got to the screen where I type a number in, my code wouldn't work. I wrote it down, I made absolute sure I had it right. I selected the Pin option, as well as the option to automatically unlock the phone when the pin is entered correctly.
I typed the proper code in, and it just kept saying "try again." I have a nandroid backup of the rooted stock Rom saved to my computer, so I can fix this I think, but how do I get back in? I originally heard that wiping data/factory reset would get rid of encryption, but when I try this with my CWM 6.0.4.7 I get:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android.secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
Someone told me this has to do with the way CWM tries to format things (by mounting them first), and that I can go into mounts and storage. but which ones do I format there? I really don't want to mess anything up. Here are my options:
/boot
system
data
cache
persist
firmware
sns
persist-lg
mpt
/data and /data/media (/sdcard
Thanks!
Mods, please move
1. You are in the wrong section, this is not help and troubleshooting (I know more people will see it here) However, we learn from others mistakes and when you post in there people with the same problem might search and see a solution of how you solved your problem.
2. Not sure if adb works in recovery or if it will in your situation but I would try adb reboot recovery or try adb sideload and sideload a rom onto it.
This does not belong in the Development Section, read the Forum Rules on posting....Moved here, thanks.
jhr5474 said:
1. You are in the wrong section, this is not help and troubleshooting (I know more people will see it here) However, we learn from others mistakes and when you post in there people with the same problem might search and see a solution of how you solved your problem.
2. Not sure if adb works in recovery or if it will in your situation but I would try adb reboot recovery or try adb sideload and sideload a rom onto it.
Click to expand...
Click to collapse
Ok ****. So far I've always avoided having to use adb while rooting (rooted evo 4g, gs2, and lg g2). Guess it's time to learn. Any advice on where to start reading?
Judge Joseph Dredd said:
This does not belong in the Development Section, read the Forum Rules on posting....Moved here, thanks.
Click to expand...
Click to collapse
Hey thanks man
While you're here mind telling me why my profile pic doesn't show up on my posts?
I just got a note 2 (i317m - canadian carrier model) that got messed up some how. When attempted to boot the phone it said unable to mount efs partition. My research tells me that partition that contains module info such as IMEI, bluetooth, wifi are stored in that partition. Now I realize why the repair guy wanted $350 to fix it.
Is there a way I can tackle this problem on my own and try and fix it? Apparently there is a tool here in XDA that can wipe the partition but I am not sure if that would rebuild it and allow me to mount it so I can create a new data file with the IMEI number in it.
Where should I start to attempt to fix the problem.
Please note, I can still access recovery (currently TWRP installed) and download mode and use ODIN if necessary to flash back a stock rom BUT can't mount to the computer for any file transfers nor can I boot the android device (stays at samsung logo). I have no issue using ADB is neccessary if I am lead in the right direction. This phone is already trashed in the eyes of the owner so its basically a little project for me to tackle when i have time to kill.
Bloodyskullz said:
I just got a note 2 (i317m - canadian carrier model) that got messed up some how. When attempted to boot the phone it said unable to mount efs partition. My research tells me that partition that contains module info such as IMEI, bluetooth, wifi are stored in that partition. Now I realize why the repair guy wanted $350 to fix it.
Is there a way I can tackle this problem on my own and try and fix it? Apparently there is a tool here in XDA that can wipe the partition but I am not sure if that would rebuild it and allow me to mount it so I can create a new data file with the IMEI number in it.
Where should I start to attempt to fix the problem.
Please note, I can still access recovery (currently TWRP installed) and download mode and use ODIN if necessary to flash back a stock rom BUT can't mount to the computer for any file transfers nor can I boot the android device (stays at samsung logo). I have no issue using ADB is neccessary if I am lead in the right direction. This phone is already trashed in the eyes of the owner so its basically a little project for me to tackle when i have time to kill.
Click to expand...
Click to collapse
Have you tried flashing your official rom? Flash your official firmware by downloading it from sampro.pl or sammobile.com, flash it with PC Odin under PDA tab.
After you done, don't let reboot your phone, goto recovery by pressing vol up+ menu key then power key(continuously hold it until your phone restarts might be 4~8 secs.) Then check 'Wipe Cache Partition', and then reboot phone.
Yup and nothing worked.
Anyone?
So the only solution is a $300 fix?
I bought a new never used Tab 3 for the intended purpose of using it as a universal remote. I wanted to strip it down and started right away with installing custom recovery, or at least I tried. No matter what I did I was not able to get Odin to properly load TWRP. It went through all the steps but I was not able to get into recovery other than stock.
Fast forward to the next day, I finally get it to work and somewhere in this process I somehow deleted or unmounted (I really am not sure) my efs folder/partition. If I try to reset deleting all cache and wiping everything including pulling the battery for a few minutes and flashing the stock ROM again I get hung up at the "SAMSUNG' logo. I have tried several ROMs and even tried using Odin to flash a new pit file with I found HERE. When I load both the pit file and my ROM into Odin it eventually says 'FAIL'. I can flash ROMs all day with no issue.
I can only assume that the error I am getting in recovery that says E:failed to mount /efs (Invalid argument) is my issue.
Adb is not really an option for me since I have little to none, more like none at all knowledge of using it. I assume since I have flashed several tries that USB Debugging is not enabled anyway and isn't enabling it key to using ADB anyway?
I have been at this for 2 full days searching everywhere and trying everything I see. I am at a loss and hate to think this new Tab is already junk.
Any help would be greatly appreciated!
The EMCC or something like that requires replacement
andynroid said:
The EMCC or something like that requires replacement
Click to expand...
Click to collapse
So I should junk it then? I only paid $80 for this Tab.
One trial you may try to flash a Cyanogenmod based ROM see if it can write out the partitions else if no luck time to replace that item as mentioned
I have tried flashing CM and still the same issues.
I have since found out what my issue is (or at least 99% sure), I somehow wiped out my efs partition completely. So running a new pit file with Odin does nothing because the partition is gone.
This is fixable and easy for someone who knows shell, but I don't. So now I am trying to figure it out. It's a matter of pushing the 6 following files to the phone using the adb push [file] /sbin/ command using adb which I have done, now I need to figure out the rest.
e2fsck
mke2fs
parted
resize2fs
sdparted
tune2fs
T
you can't do that in the way you think, it requires disassembling the recovery image, making modifications and repacking then reflashing the image.
If you are using an older recovery, namely twrp, install a newer recovery , check @nels83 's thread for a "modern" twrp build.
You can also try one of my philz builds.
Being as you have been abusing Odin, you may actually have damaged your tab.
BUT if you are connecting to wifi without a problem then it's unlikely that you have damaged your efs partition. It's more likely an error with the recovery build you are using, probably in the fstab.
m
First of all to admins..., I hope I'm posting this in the right section. If I'm not, please move it or direct me.
I have a Verizon S5 - G900V that is soft bricked and I have been pulling my hair out trying to restore stock rom to it via Odin. It fails every time. I have tried so many versions - some fail with aboot, which I understand means that th version I'm flashing is older and I can't downgrade. Fair enough. The only one that seems to work is G900VVRU2DPD1 (which shows up as the version in recovery mode) but it fails at loading the SYSTEM stage. In Odin on Windows it shows fail (AUTH) an on t device it shows secure check fail: system
Reactivation lock on the device in download mode shows OFF And I can't boot into the OS to verify that.
I have all the necessary device drivers installed in windows.
The device, I believe, is not rooted.
Using kies doesn't work because I asks for for device serial which I d know and does n show under the battery (only shows IMEI an model) and using the Verizon repair Assistant doesn't even see the device
I have wiped cache partition and did factory reset from recovery mode.
I have done exhaustive Google searches an been on many xda dev posts for weeks and not finding anything that works.
I've also tried pushing with adb sideload....didnt work.
The only thing I can think of, and think I might have read somewhere, is that my problems are caused by a locked bootloader. I anyone here able to attest to that?
One other thing...in recovery mode, if I select mount system, it gives errors in red e:Failed to mount /system (invalid argument).
Any experts here able to help me get passed this to successfully flash stock rom (or any rom even modified) back into this device and end my madness?
Any help would be appreciated.
Thanks in advance
Bump
any experts out there able to help me on this one?