So I've got a wifi-only Samsung Galaxy Tab 10.1" and I have gone through the rooting guide. The guide includes ClockworkMod (CWM) v4.0.0.4, which for the most part, works just fine. I'm able to flash custom ROMs, make backups, and restore backups.
I'm having a problem mounting USB storage from CWM however. I go to the "Mounts and Storage Menu" and then select "mount USB storage." When I do this, I get a message saying:
E:Unable to open ums lunfile (No such file or directory)
Any ideas what this means, and how to fix it? Is anyone else able to mount USB storage from their CWM recovery image?
Anyone can correct me if I'm mistaken...but I believe the reason we see this error is because the Tab is not like phones and the internal storage works differently, there is no sd card so it has nothing to mount. I believe it works more like a hard drive. (MTP is different although I know nothing about it) so CWM produces this error but it is nothing to worry about.
More knowledgeable persons please expound on this, I would like to know more too...
Appreciate the insight -- I hope someone else can expand. To expound on that though, how do you transfer a ROM to the SDcard if you wipe /data and don't already have a ROM available on the SDcard?
I'm worried that I'll accidentally wipe data & cache, but will forget to double-check that I have a ROM on the SDcard partition.
Not to worry, wipe data/factory reset in CWM does nothing to the sd card partition everything will still be there including the ROM file you transferred over.
However factory reset from stock recovery DOES wipe sd card data. So back up your stuff if you do this.
Oh and always make a backup in CWM so you have something to flash in case things get crazy
I'm just trying to plan for a worst case scenario -- let's say all the storage volumes are completely wiped, and all you can do is boot into CWM. On my T-Mobile G2 (Desire Z / Vision), you can mount USB storage, copy over a ROM, and install it.
Looking for some sort of equivalent ability on the Galaxy Tab.
Hmm, let me boot into CWM and see if the computer still can read the tabs storage if I plug it in from there...
Also there is always an ODIN flash.
Nope no dice, i suppose if you were in that scenario ODIN would be your option. I'm not sure if there is an ODIN flashable of stock 3.1, I know there is a .zip i always keep it for emergencies.
Sorry I miss read, there is no ODIN flash.
Would the worst scenario is when you don't even have CWM on the tab?
ODIN flash would probably be your last resort. I am wondering if anyone has run into the worst scenario and got the tab back to the factory stock ROM.
your are right FilltheVoid. if things go completely wrong and you have no backup or rom to flash. Odin will be your savior. You can flash stock roms with Odin bro.
task650 said:
your are right FilltheVoid. if things go completely wrong and you have no backup or rom to flash. Odin will be your savior. You can flash stock roms with Odin bro.
Click to expand...
Click to collapse
Hey Task, do you know where I can find a stock ROM for pt7510 that is ODIN flashable? Ya know, just in case.
Well anywho, I think the point of this is, If you read and follow directions carefully, make backups, and read some more, you will not ever be in this scenario. And there are good, knowledgeable people in this forum that are willing to help you in a bind.
FillTheVoid said:
Hey Task, do you know where I can find a stock ROM for pt7510 that is ODIN flashable? Ya know, just in case.
Well anywho, I think the point of this is, If you read and follow directions carefully, make backups, and read some more, you will not ever be in this scenario. And there are good, knowledgeable people in this forum that are willing to help you in a bind.
Click to expand...
Click to collapse
Even though the question is to Task, i will answer it with whatever i know.
1. http://droidbasement.com/galaxy/sys-backup/hc_31/ - But i read somewhere that this is the ODIN flashable stock of I/O tab
2. ROM | 001002-P7510_KME_Restock.zip - ODIN flashable Stock UEKME ROM
Or you could do:
Boot cwm, then
adb shell
mount /data
mkdir /data/media
adb push stock.zip /data/media/
and flash with cwm
Voila !!!
thank you!
you just saved my tablet! thank you.
i managed to brick my tablet (or so i thought) by an interesting combination of things.
first, i installed Alegro graphing calculator. then, i encrypted my tablet. then, i tried to backup my apps, using titanium backup, and whenever it got to alegro, it crashed superuser, market, myapps, googleapps, calendar, acore...a ton of stuff. so i told titanium to ignore it and backup everyything else, and then i went to the market to try to uninstall. no dice..it force closed everything again. so i went to the settings and tried to factory reset. i went through the steps three times, and nothing happened...the tablet rebooted and was the same as i left it.
so as a last resort i went into clockwork and wiped data and cache. tried to boot, and it was stuck on the Samsung Galaxy Tab 10.1 screen.
rebooted..same...waiting hours...same.
i could still boot to odin and recovery, but i didn't have a zip on my tablet, so i couldn't flash anything. i never thought of using adb to push the zip! but this worked perfectly! (after installing the drivers again on my computer).
thank you thank you thank you!
ansonantonym said:
Even though the question is to Task, i will answer it with whatever i know.
1. http://droidbasement.com/galaxy/sys-backup/hc_31/ - But i read somewhere that this is the ODIN flashable stock of I/O tab
2. ROM | 001002-P7510_KME_Restock.zip - ODIN flashable Stock UEKME ROM
Click to expand...
Click to collapse
Hey 2 questions about the restock ROM:
1) Can it be flashed over In Paris V5?
2) Can it be flashed with CWM?
Update: answered this myself: Yes it can be flashed over in Paris, and no, it has to be flashed with Odin.
I still have a question though: This is not CWM, but is it the stock recovery or do I need to flash that too? Sending the tab in for service (newton's rings)....
This is what I was looking for. I have a slow internet connection, and Clockwork was still working, but nothing else was. Flashed Task's ROM v8... it's looking good so far... You rock, dude.
This worked for me this afternoon! Was stuck in a constant reboot after thinking that the samsung update would be a good thing. Gave thanks!!! Ordered the 30 pin adapter and now dont even need it. Will come in handy though I am sure.
FillTheVoid said:
Anyone can correct me if I'm mistaken...but I believe the reason we see this error is because the Tab is not like phones and the internal storage works differently, there is no sd card so it has nothing to mount. I believe it works more like a hard drive. (MTP is different although I know nothing about it) so CWM produces this error but it is nothing to worry about.
More knowledgeable persons please expound on this, I would like to know more too...
Click to expand...
Click to collapse
This maybe complete rubbish, but I can report a similar issue with the Galaxy S2.
When I install a new ROM, I usually do this:
1/ factory reset
2/ wipe cache
3/ wipe dalvik
4/ Mount ALL the folders, then format each one
When I do this and try to mount USB storage, it says the same error message.
If you then fire up ODIN and push another kernel to the phone, everything works fine. I know its something I am doing wrong, but no idea what!
For you, the solution is to use odin to push another kernel across.
Phil
Related
I've been stuck in a weird place for some time with my phone. After I installed clockwork mod, backed up, installed some flavour of FroYo, and made the mistake of trying to flash back my old back up without properly wiping things have been getting weird. I can use ODIN to flash fresh ROMs, but I always get a bunch of FCs at startup, and most apps don't work. I tried to do all kinds of tricks to completely wipe the internal SD, but there is always some remnants of old fun hanging about causing cascading errors and FCs. No matter what I try to do, MyBackupPro and Rommanager is always present, but not working.
How I can completely rid myself of anything not stock ROM?
I've finally gotten back to root ADB, after a long and hard battle. I believe this may hold the key to salvation for my Vibrant.
Any and all suggestions are much appreciated!
Things I've already tried:
EUGENE373_SamsungS_Froyo_PDA -> Stock 2.1 T959UVJFD
EUGENE373_SamsungS_Froyo_PDA -> battery pull -> Stock 2.1 T959UVJFD
Stock 2.1 T959UVJFD -> EUGENE373_SamsungS_Froyo_PDA
Bionix1.9.zip - would not install due to some error I can't recall right now. Will update.
Factory wipe - from Settings menu
Wipe in Clockworkmod menu
Wipe all in adb shell
The weird *2767*3855#* factory wipe
UPDATE:
Strangest thing happened: I flashed an old ROM back onto the phone with Odin 1.52, then the Updated Stock 2.1 also via Odin the usual FC-ing was still there. Then I rebooted into recovery, reinstalled the Clockworkmod recovery menu, installed the root-update.zip in order to have root shell access. Then I pushed VibrantDeodexed1_2.zip and Vibrantfroyo_R3.zip on to the sd card. I tried to apply the VibrantDeodexed1_2.zip, but it aborted due to some catalog not present. However, I did notice that the installation erased /system and deleted some files, and I had the notion to try and install the VibrantFroyo_R3.zip. The installation succeeded, and Lo and Behold!
the phone has returned to the land of the living! Wohoo!!
I do not fully understand how this can be, but there is no Force Closing of programs any longer. What a relief!
Thanks to everybody who contributed ideas!
If you're having problems, back up whatever data you want to keep to your computer. Go download eugenes 2.2 that doesn't brick. Flash that, do a battery pull once it's done (don't reboot). Then go get a stock eclair file, flash that with odin and check repartition. This solved every problem I had from flashing way too many roms.
Yea, when in doubt I thank the deities for Eugene and flash his "Froyo that doesn't brick" followed by the stock JFD firmware.
Sent from my SGH-T959 using XDA App
brnagndan said:
If you're having problems, back up whatever data you want to keep to your computer. Go download eugenes 2.2 that doesn't brick. Flash that, do a battery pull once it's done (don't reboot). Then go get a stock eclair file, flash that with odin and check repartition. This solved every problem I had from flashing way too many roms.
Click to expand...
Click to collapse
Sorry to say, that trying this solved nothing. Just the same as before.
ullrotta said:
Sorry to say, that trying this solved nothing. Just the same as before.
Click to expand...
Click to collapse
You clicked the "repartition" option? That should format your internal sd...
I7oobie said:
You clicked the "repartition" option? That should format your internal sd...
Click to expand...
Click to collapse
Yeah, that's the weird part.. It doesn't really delete anything. Files are still there, and so are the un-wanted system files, too.
Does anyone know if I can manually partition the sdcard?
Had a similar issue, and couldn't fully erase my files. Figured out how to completely erase everything, before you proceed, backup your files and be ready to Odin. In rom manager, enable advanced mode in settings, then use the flash alternate recovery option. That set my current cwm version to 2.5.1.2, now when I reboot to cwm i have a menu that says something similar to "sd and storage" and within that menu are options to completely format all of the internal storage. Be careful in there, you can delete everything, incl the sd ext, but I think this is what you are looking for.
Edited - I rebooted and checked the menus, mounts and storage in cwm is what you are looking for after flashing the alternate recovery, I can confirm this removes remnants that an Odin repartition or factory format still leaves behind, let me reiterate, backup your personal files, cause this does remove everything
After formatting, Odin away
Sent from my T959 running Bionix1.91 with Jacs OC/UV and Voodoo
same thing happened to me >.> I just formatted the SD card on the phone. then flashed whatever rom I wanted.
Br1cK'd said:
Had a similar issue, and couldn't fully erase my files. Figured out how to completely erase everything, before you proceed, backup your files and be ready to Odin. In rom manager, enable advanced mode in settings, then use the flash alternate recovery option. That set my current cwm version to 2.5.1.2, now when I reboot to cwm i have a menu that says something similar to "sd and storage" and within that menu are options to completely format all of the internal storage. Be careful in there, you can delete everything, incl the sd ext, but I think this is what you are looking for.
Edited - I rebooted and checked the menus, mounts and storage in cwm is what you are looking for after flashing the alternate recovery, I can confirm this removes remnants that an Odin repartition or factory format still leaves behind, let me reiterate, backup your personal files, cause this does remove everything
After formatting, Odin away
Sent from my T959 running Bionix1.91 with Jacs OC/UV and Voodoo
Click to expand...
Click to collapse
When I boot into recovery, I always have to reinstall packages to get to the CWM recovery menu. I tried to clear everything from the mounts and storage submenu; I cleared system, cache and data, then flashed stock eclair. STILL the same applications and files sit on the internal SD.
When performing the wiping, all looks normal. It does take a little time, and the system reports that all is going according to plan, yet no files are deleted.
What can possibly make the phone act this way? Are there no super secret samsung-technician codes that allow me to completely wipe clean the face of the sdcard?
When you get into the storage and mounts menu, I would format everything given what you're experiencing. Format boot, data, system, cache, and sdcard. Dont format the sd ext, thats the physical card. After formatting all of those your phone should be an odin ready blank slate, mine was. Hope this helps.
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
this has to be one of the most useful threads. just last night i was messing with rom manager and enabled advanced settings, BEEFORE reading this thread. I've done so much monkeying, but didn't keep a journal or log, so ive got **** from so many hacks and tweaks (mods and themes)...
thanks, im gonna wipe this ****er clean.
Good Info..but moved to Q&A
Br1cK'd said:
When you get into the storage and mounts menu, I would format everything given what you're experiencing. Format boot, data, system, cache, and sdcard. Dont format the sd ext, thats the physical card. After formatting all of those your phone should be an odin ready blank slate, mine was. Hope this helps.
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
Click to expand...
Click to collapse
This is exactly what I tried yesterday. I'll try it again a few times to see if I can find a way.
ullrotta said:
This is exactly what I tried yesterday. I'll try it again a few times to see if I can find a way.
Click to expand...
Click to collapse
I was hoping that would help you friend, that process wiped mine clean of all remnants. Good luck in getting her back into a functional state.
After reading som more, contacting Samsung Service, I've decided to send the phone in for service. [sigh]
I've learnt a lot about ADB, pushing and pulling files, rooting, unrooting, swapping ROMS and whatnot. Still, the phone is stuck in that weird place where I cannot delete files.
Hopefully the service team can fix this poor, misguided phone
I was in Clockwork Recovery after backing up my stock system (this is my first time) it gave me the options in green text: Reboot, reinstall update.zip, etc.
I chose reboot and everything loaded up fine and after checking in Rom Manager I have a backup of my system. I just want to know if that was the right choice. or should I have reinstalled update.zip
I guess my question revolves around update.zip.
What is that file? I know I originally used it to gain root access but do I need to reinstall it from clockwork recovery everytime before rebooting? and when should I delete it? and are there any negative consequences for not doing either?
As you can tell I'm a noob....but hey I can't believe I'm rooted and backed up at the moment. I'm gonna stop here before flashing any custonm roms and get this question answered first.
I think you are fine. I would not worry so much, i have deleted the update.zip, but since you booted up into ClockWork Recovery you are most likely fine.
I am booted back up completely and the stock os is running and I'm still rooted. I just want to know what that option inside of clockwork recovery means. What is the reason to reinstall update.zip from clockwork recovery and what is the reason to reboot? And once I'm booted back up and running when/why do I go into my files and delete update.zip?
It's not that I'm worried...I just want to know why I'm doing what I'm doing.
I would keep the file. Less chance of failure.
You are only going to use cwr for this:
Backup/restore system
Wipe cache, factory wipe, etc
Flashing rom's (install from sd card)
Don't worry about the other stuff.
I'm confused by the op, not sure how you made a backup from how it reads.
I think I made the backup by flashing into clockwork recovery from rom manager. It started with the purple text recovery mode and I hit reinstall packets. Then it went into the green text clockwork recovery....I think. I've only done it once.
So in clockwork recovery I choose the backup/restore option and then the backup option. So then the phone I assume began the backup process and displayed many lines of white text. At the very end it said something about not being able to mount my ext sd card (which) had me worried.....but then it brought up the menu again. The top option was reboot, the second was reinstall update.zip and I didn't pay attention to the rest because I was pretty sure I needed one of the first two....I just didn't know which one. I selected reboot and the phone then booted into the stock os and was still rooted. Is the fact that it wasn't able to mount my ext sd card at the end of the backup process an issue? I'm able to find a backup in rom manager. Also, if the backup process works correctly should the phone reboot by itself?
What I'm asking is what am I booting from when I choose "reboot" from clockwork recovery and what does it mean to choose "reinstall (packet?) update.zip"? I thought update.zip was what I needed to root.
This last step wasn't in your tutorial (purple text menu) so maybe something didn't go as it should have.
I'm not sure.
Thanks s15274n for the tutorial btw. Its by far the most helpful concise instructions I've found and is really appreciated.
Sent from my SGH-T959 using XDA App
The update.zip in the root of the internal SD card is clockwork recovery (CR). When you install CR it does not overwrite your phone's recovery. What it does is install that update.zip in the root of the SD card. When you want to use CR, you need to "update packages" which will flash that update.zip which contains the CR package. That will load CR into memory only and still does not overwrite the original recovery on the phone. When you reboot into recovery from ROM Manager, it automatically reboots and applies the update.zip and places you into CR. If you enter recovery manually (via buttons on boot), you will need to "re-install packages" from the stock recovery to get CR.
So if you want to use CR, keep that update.zip in the root of the SD card. If you erase it, you will need to re-install it (using ROM Manager) before you can use CR instead of the stock recovery. I hope that makes sense. If not, here is the explanation straight from Koush on how it works.
http://forum.xda-developers.com/showthread.php?t=734164&highlight=clockwork
^^ You are all good then.
The SD-EXT is not going to backup, because you do not have a partiotion on your external SD card (no need for one, like some other phones require). This is normal from what you described.
You will never use the apply update.zip option in CWR... just dont pay any mind to it.
When you select reboot system now, that is all it is.... you are basically saying "Cool, I did everything I needed to do (backup/flash a rom/wipe, etc)... and now I am ready to reboot my phone... ie, you are basically cutting your phone on.
Positive you did, but you can open rom manager, click on manage backups and you should see a file there that has a format kinda like YYYYMMDDTIME, that is the backup you made... no action needed, just an easy way to verify you made a backup of your system.
s15274n said:
I would keep the file. Less chance of failure.
You are only going to use cwr for this:
Backup/restore system
Wipe cache, factory wipe, etc
Flashing rom's (install from sd card)
Don't worry about the other stuff.
I'm confused by the op, not sure how you made a backup from how it reads.
Click to expand...
Click to collapse
Thanks s15274n
i have been wondering the same thing about the update.zip file whether to keep it or not.
Thanks s15274n for the tutorial btw. Its by far the most helpful concise instructions I've found and is really appreciated.
Click to expand...
Click to collapse
Also wanted to say i feel the same way. Appreciate the guide so much!
Thanks guys. I'm glad to have that cleared up so I understand it. Gives me more confidence to do the other things I want to do.
I got confused with the fact that I need to delete the update.zip file after rooting and the fact thats its there again after flashing cw and backing up.
Sometimes I need things spelled out for me. Makes complete sense now.
Sent from my SGH-T959 using XDA App
I'm sorry if this info is already posted, I found similar info in my searches but not exactly what I'm looking for.
I just bought a G and its coming tomorrow. I plan to install clockwork and try out some ROMs (probably VEGAN first). I've seen a lot of information that partitioning the internal memory to 2048/0 is a good idea, but that it will wipe out the internal memory. My questions:
1) Is this accurate? Should I do this before installing custom ROMs?
2) When people say it wipes out EVERYTHING, does that mean the stock OS is gone at that point? Will I still be able to boot into Clockwork at that point to install a ROM?
3) Is it possible / what is the best way to backup the internal memory prior to doing this? Or should I not even worry about that as I will be installing a custom ROM after anyways. EDIT: I should say I'm semi-familiar with clockword with my Droid, I know you can do backups via clockword, is doing a clockwork backup prior to partitioning going to get everything I need in case I brick it? This one may have answered itself hehe.
Thanks!
mattbooty said:
I'm sorry if this info is already posted, I found similar info in my searches but not exactly what I'm looking for.
I just bought a G and its coming tomorrow. I plan to install clockwork and try out some ROMs (probably VEGAN first). I've seen a lot of information that partitioning the internal memory to 2048/0 is a good idea, but that it will wipe out the internal memory. My questions:
1) Is this accurate? Should I do this before installing custom ROMs?
2) When people say it wipes out EVERYTHING, does that mean the stock OS is gone at that point? Will I still be able to boot into Clockwork at that point to install a ROM?
3) Is it possible / what is the best way to backup the internal memory prior to doing this? Or should I not even worry about that as I will be installing a custom ROM after anyways. EDIT: I should say I'm semi-familiar with clockword with my Droid, I know you can do backups via clockword, is doing a clockwork backup prior to partitioning going to get everything I need in case I brick it? This one may have answered itself hehe.
Thanks!
Click to expand...
Click to collapse
1- You can use my batch file to backup an image of your tablet, this is not for day to day restore but it may be useful one day...
2- Yes and possibly more...
3- NVFLASH BACKUP then FULL CLOCKWORK Backup
4- then do whatever your are covered...
http://forum.xda-developers.com/showthread.php?p=12434269#post12434269
Ok, so first thing after I get the G Tab, is install nvflash on my PC, hook up via USB and run your batch file? Should I do this before or after installing clockwork? Do I turn the g Tab on after plugging in the USB?
I really appreciate your help.
Partitioning 2048/0 from CWM recovery doesn't wipe the ROM space. I have booted into the tablet right after doing this and nothing else, so clearly it still has the OS. It just wipes /SDCARD (the built in memory).
mattbooty said:
Ok, so first thing after I get the G Tab, is install nvflash on my PC, hook up via USB and run your batch file? Should I do this before or after installing clockwork? Do I turn the g Tab on after plugging in the USB?
I really appreciate your help.
Click to expand...
Click to collapse
Read the batch remark, it explain, but yes you install the APX drivers, then plug usb, power on with volume - and run the batch files.
Ramerco is also right when he say partition of the 2048GB only erase the 2G/16G part
but it's still a good idea to keep a full image from the early tablet, there's a NVFLASH recovery from bekit availlable as well
Also there's a shell script called inandop.sh that is taking care of this if there's no sdcard it will create it...
Thanks again guys!
Hi,
I am trying to restore a couple of nandroid backups, but a Device Administrator app gone "quirky" seems to materialize no matter what I do. I did a CWM Wipe, restored the nandroid backup before the app went bad. However that did not work, the app was still misbehaving. So I wiped again, restored a nandroid backup from before I had installed the app. Still the app shows up again. It has in effect locked me out of the device.
Can anyone tell what can I do to get rid of the app?
Are these Device Admin app supposed to persist like this? Or am I doing something wrong?
Do I need to choose a different wipe mode (I chose the normal one, which wipes /data/, /cache etc). I did not try to wipe /cache separately, as the first wipe does that by itself. Neither did I wipe the dalvik cache, as I thought they are not relevant here. I don't see any relevant files in the sdcard either, though how the app reappears in the nandroid restore before it was installed is a mystery.
Should I mount more partitions before wiping, like the data/cache etc.
Since the wipes don't seem to make it go away, I am not even sure flashing a different ROM would get rid of this app either, however I can try that (since I was planning to anyway, before this mishap). If that doesn't work either, I might just have the most unusual case of bricking ever.
The XDA forum does not seem to be much info about device-admin apps and my search-fu is not good enough today to find anything directly relevant about the other stuff.
PS. btw the app actually modifies the lockscreen. So I don't actually see the files it has with the pre-app restore, however the lockscreen still comes up, perhaps because of some remanant of the app or because of a setting it left in there somewhere.
efs?
Just to add more info, I see some files in /efs, which look relevant to the lockscren/ They have file names like this "/efs/cryptoprop_lockscreen".
Would these files store the data this app stored. I fortunately have an EFS backup, should I consider restoring these files.
If someone doesn't know the answer, can they suggest which devs would be good to ask about this.
AnDruid said:
Hi,
I am trying to restore a couple of nandroid backups, but a Device Administrator app gone "quirky" seems to materialize no matter what I do. I did a CWM Wipe, restored the nandroid backup before the app went bad. However that did not work, the app was still misbehaving. So I wiped again, restored a nandroid backup from before I had installed the app. Still the app shows up again. It has in effect locked me out of the device.
Can anyone tell what can I do to get rid of the app?
Are these Device Admin app supposed to persist like this? Or am I doing something wrong?
Do I need to choose a different wipe mode (I chose the normal one, which wipes /data/, /cache etc). I did not try to wipe /cache separately, as the first wipe does that by itself. Neither did I wipe the dalvik cache, as I thought they are not relevant here. I don't see any relevant files in the sdcard either, though how the app reappears in the nandroid restore before it was installed is a mystery.
Should I mount more partitions before wiping, like the data/cache etc.
Since the wipes don't seem to make it go away, I am not even sure flashing a different ROM would get rid of this app either, however I can try that (since I was planning to anyway, before this mishap). If that doesn't work either, I might just have the most unusual case of bricking ever.
The XDA forum does not seem to be much info about device-admin apps and my search-fu is not good enough today to find anything directly relevant about the other stuff.
PS. btw the app actually modifies the lockscreen. So I don't actually see the files it has with the pre-app restore, however the lockscreen still comes up, perhaps because of some remanant of the app or because of a setting it left in there somewhere.
Click to expand...
Click to collapse
Do a CWM wipe, and turn off the phone when done by selecting "Power Off"
Now enter download mode, and ODIN flash a stock ROM.
Then re-root with CF-Root and install custom ROM if desired.
pulser_g2 said:
Do a CWM wipe, and turn off the phone when done by selecting "Power Off"
Now enter download mode, and ODIN flash a stock ROM.
Then re-root with CF-Root and install custom ROM if desired.
Click to expand...
Click to collapse
Thanks for the help pulser_g2. I am still concerned about the files i saw in /efs related to the lockscreen (see my second post). Would the stock ROM overwrite settings/configuration inside /efs (I guess since the IMEI etc are all in there, that might not be the case)?
Got through finally.
pulser_g2 said:
Do a CWM wipe, and turn off the phone when done by selecting "Power Off"
Now enter download mode, and ODIN flash a stock ROM.
Then re-root with CF-Root and install custom ROM if desired.
Click to expand...
Click to collapse
OK this worked.
However after I Odin flashed the stock rom and rebooted, I got this
1. First got a different kind of lockscreen.
2. I entered the wrong password five times (after trying the Device Admin alternate password, my Google password, a new 2-step auth password from google) .
3. it said something about wiping sd card. I couldn't catch it (I should probably have videoed this using my point and shoot camera, but this did not strike me then as it was 2am).
4. I was hoping that the stock ROM will boot, cause it stayed on the Samsung logo for too long. (I had already ordered my USB Jig on ebay anyway, but it could have taken time because of my being far off from the seller.). Finally I got the Android Welcome screen and I let out my breath.
In any case, things seem to ok right now. I feel a slight slowness in the rooted stock ROM from my earlier rooted stock ROM, but I am gonna flash a custom ROM later anyway. Thanks a lot for your help pulser.
Hi, i'm new at the forums, but this have been my first option for android related solutions and info for a long time ago, but i finally decided to join it.
Well, this is embarrasing, but my first post it's about a problem in my pretty new SGS3 GT-i9300 i got a couple of weeks ago.
The problem is..., well, i've been testing some roms as 2nd roms with the help of the Siyah kernel. I've done the basics things..., root my phone, install my first kernel (siyah...), killed the stock rom so i learned how to flash a new stock rom for my country without all the operator's junk, then i overclocked (just a bit only), then i started with the 2nd roms....
My first try was UltimaROM, pretty good but i wanted to test MIUI, no problem, i worked but i didn't like it completely since it deleted all the samsung goodies, so i tried to flash ihackers, no luck..., it wouldn't just boot. So i tried with FoxHound, the same thing. So just dissapointed, i came back to UltimaROM and installed it again as 2nd rom (all in just 2 days). Well, it worked ok but then i noticed a serious problem...
Since the last time, when i flashed UltimaROM with the 2nd Rom Utils from Siyah, i came back to the stock rom (1st rom) because i wanted to record the fireworks outside my home (because of new year ), but, the camera said "Error al grabar" and just closed..., then i remember a couple of random massages saying that i was running out of space in the internal memory, so i dicided to temporarily delete the 2nd rom (i've been so gross these two days...), and..., according to the 2nd rom utils from siyah, the 2nd rom was succesfely removed, but just to be sure, i fixed permissions (i did this everytime i tried to flash a new 2nd rom).
Now back to the stock rom, the camera problem not being able to record to the internal memory still there, but now, i looked into the internal memory with root explorer and there is a big folder named "ADM" with a...¡¿copy?! of the UltimaROM zip, which weights 1.5Gb, and i can't delete it, EVEN WORSE!, now a lot of random files and folders in the internal memory are "locked", i can't delete any of these, or even change permissions (my DCIM folder for example). I then tried the CWM option to "fix permissions", on the main CWM recovery as well as in the siyah 2nd rom utils recovery..., but all the same
Thinking that the internal memory file system got corrupted, i though that my best option was to flash the stock rom from samsung again, but this time with the option "Re-partition" checked. I tried it in Odin but...damn it..., it won't make it!, however, i can soft-flash the stock rom without "re-partition" check..., but this doesn't fix the internal memory...
In short, i CAN boot into my main stock rom, i can FLASH the stock rom trough Odin but i can't if i check the Re-partition option, and until i get i fix for the internal memory, i'll have to use my 2Gb External SD Card.....
So..., what can i do? Is there anything i can do to safely format the internal emmc completely and then flash the stock rom again? Or maybe do i have to...assume...that the locked internal memory problem...is a hardware problem? That's what i'm afraid of...
Anyway, i'll leave the details here.
OS: Stock Rom Samsung JB 4.1.2 (I9300UBEMH2_I9300UVOEMH1_ARO)
Kernel: Siyah Kernel 1.9.1
Recovery: CWM-based Recovery v5.5.0.4 CF-v1.5
I would leave a dump file of the failing Odin process now, but i don't know if that is possible and neither how to do it. But he most i can give is a screenshot attached.
Thanks in advance!
P.D.: let me know if this post is on the wrong place inside the forum
alpha-ro said:
Hi, i'm new at the forums, but this have been my first option for android related solutions and info for a long time ago, but i finally decided to join it.
Well, this is embarrasing, but my first post it's about a problem in my pretty new SGS3 GT-i9300 i got a couple of weeks ago.
The problem is..., well, i've been testing some roms as 2nd roms with the help of the Siyah kernel. I've done the basics things..., root my phone, install my first kernel (siyah...), killed the stock rom so i learned how to flash a new stock rom for my country without all the operator's junk, then i overclocked (just a bit only), then i started with the 2nd roms....
My first try was UltimaROM, pretty good but i wanted to test MIUI, no problem, i worked but i didn't like it completely since it deleted all the samsung goodies, so i tried to flash ihackers, no luck..., it wouldn't just boot. So i tried with FoxHound, the same thing. So just dissapointed, i came back to UltimaROM and installed it again as 2nd rom (all in just 2 days). Well, it worked ok but then i noticed a serious problem...
Since the last time, when i flashed UltimaROM with the 2nd Rom Utils from Siyah, i came back to the stock rom (1st rom) because i wanted to record the fireworks outside my home (because of new year ), but, the camera said "Error al grabar" and just closed..., then i remember a couple of random massages saying that i was running out of space in the internal memory, so i dicided to temporarily delete the 2nd rom (i've been so gross these two days...), and..., according to the 2nd rom utils from siyah, the 2nd rom was succesfely removed, but just to be sure, i fixed permissions (i did this everytime i tried to flash a new 2nd rom).
Now back to the stock rom, the camera problem not being able to record to the internal memory still there, but now, i looked into the internal memory with root explorer and there is a big folder named "ADM" with a...¡¿copy?! of the UltimaROM zip, which weights 1.5Gb, and i can't delete it, EVEN WORSE!, now a lot of random files and folders in the internal memory are "locked", i can't delete any of these, or even change permissions (my DCIM folder for example). I then tried the CWM option to "fix permissions", on the main CWM recovery as well as in the siyah 2nd rom utils recovery..., but all the same
Thinking that the internal memory file system got corrupted, i though that my best option was to flash the stock rom from samsung again, but this time with the option "Re-partition" checked. I tried it in Odin but...damn it..., it won't make it!, however, i can soft-flash the stock rom without "re-partition" check..., but this doesn't fix the internal memory...
In short, i CAN boot into my main stock rom, i can FLASH the stock rom trough Odin but i can't if i check the Re-partition option, and until i get i fix for the internal memory, i'll have to use my 2Gb External SD Card.....
So..., what can i do? Is there anything i can do to safely format the internal emmc completely and then flash the stock rom again? Or maybe do i have to...assume...that the locked internal memory problem...is a hardware problem? That's what i'm afraid of...
Anyway, i'll leave the details here.
OS: Stock Rom Samsung JB 4.1.2 (I9300UBEMH2_I9300UVOEMH1_ARO)
Kernel: Siyah Kernel 1.9.1
Recovery: CWM-based Recovery v5.5.0.4 CF-v1.5
I would leave a dump file of the failing Odin process now, but i don't know if that is possible and neither how to do it. But he most i can give is a screenshot attached.
Thanks in advance!
P.D.: let me know if this post is on the wrong place inside the forum
Click to expand...
Click to collapse
Use es file explorer and click on root manager. And click mount r/w. Make sure both is rw.
Sent from my GT-I9300 using xda app-developers app
Give a thank if I helped you
JellyYogurt said:
Use es file explorer and click on root manager. And click mount r/w. Make sure both is rw.
Sent from my GT-I9300 using xda app-developers app
Give a thank if I helped you
Click to expand...
Click to collapse
Thanks JellyYogurt, Yeah, i tried it as one of my first options, even with root permissions
Now, i'm really REALLY consufed...maybe, can Android get stuck for periods and lock access to some files? because after a while, i came back to take a screenshot in windows showing me a "Read-Only" mode error when trying to delete those damn files, at least, that's what said to me before, because now i connected in MTP as usual and the things i tried to delete with error earlier are...gone? I don't get it yet, and i'm hope it won't happen again, maybe tomorrow i'll try reflashing again
If the problem happens to vanish, i'll let you know so u can delete this post, just give a couple of days, i want to make sure i can make a full reflash with repartitioning in case of future emergencies
Thanks again! Really
Well, it looks like the MTP lied to me, i checked inside /sdcard/ again and the locked files still there and locked :/, i tried again mounting as R/W with no luck. When i try to take a screenshot with power + home, it says that the usb storage could be ON...this is weird, i double check my usb mass storage app and swtich to usb mass storage mode and then back to mtp (i know it's only for the extSdCard...but i don't know what else can i do)
Any ideas plz? Thanks again
Sent from my GT-I9300 using xda app-developers app
alpha-ro said:
Well, it looks like the MTP lied to me, i checked inside /sdcard/ again and the locked files still there and locked :/, i tried again mounting as R/W with no luck. When i try to take a screenshot with power + home, it says that the usb storage could be ON...this is weird, i double check my usb mass storage app and swtich to usb mass storage mode and then back to mtp (i know it's only for the extSdCard...but i don't know what else can i do)
Any ideas plz? Thanks again
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Have u tried a factory reset? Copy paste all ur pics and data to the computer first as u seem to be able to do so.
Well, i tried and tried and let me say this an awful way to begin the year :crying:
I tried using doing the factory reset from within CWM and apparently all was succesful, but again in android, the internal /sdcard/ still the same, it didn't delete anything that my settings!
Now i can't avoid being a bit desperate, is there any way to format the internal /sdcard/ (or /sdcard0/, whatever) so i can start from scratch again? In fact i don't have anything useful in there, 'cause i made a full backup 4 days ago before this problem even appeared. Now i would just be fine if i could format the internal /sdcard/, just that..., i tried the "format /sdcard" option from within CWM...but it formatted the external sdcard, what a mess
I'll be waiting, thanks again!
Use philz recovery instead, format internal sd card, wipe for new rom.
Sent from my GT-I9300 using Tapatalk
You are just a master! I tried flashing a Philz recovery via Odin and, like you told me, i formatted the internal /sdcard/, then without exitting the recovery, i check inside the sdcard with the "install zip" option, and it says "No files found", i would never have imagined how beautiful would those words look .
Now, just to make sure, i would like to repartition with odin, and (at least for now) come back to my stock rom, but the problem i mentioned earlier about "can't open file" when i tried to repartition, was because i missed the .pit file hehe
So i searched for the .pit file for the S3 16GB edition and i found it, in the corresponding forum, they said that the .pit file ending in 329 worked good for all of them.
Now with all in hand, i powered on in Download mode, opened Odin v3 once more, selected Re-partition, choosed the .pit file (ending in 329) and the stock rom .md5, flashed, waited 10min and..., no errors, until i saw the "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" problem, so i flashed again the Philz Touch recovery over the stock one (because when i tried to access the stock recovery the error always appeared), so fine! I booted into Philz and wiped cache, data and...it's so beautiful...:crying:, Android finally started! As if it were just when i bought the S3
So, i fixed it finally! I think the only thing that remains is to reset the counter with TriangleAway and get back my last backup
Thank you so much friend! At the end, i'll stay with Philz Recovery, i didn't know it before but is far better than CWM. Thanks again!
P.D.: now that i know how to unbrick completely, i'll tell my journey to my friend Dany