Hey there everybody, tried to find a solution all day long for my problem, but wasn't successful jet.
Brought uk version of ics on my tab (using P7510XXLPH) without any problems. I came from cm9 with cwm 5.5.0.4, because of the rolling recovery issue i flashed a different bootloader using isimobile's method.
To get ics working i flashed Stock HC, wiped cache and made a factory reset, both 3x. Finally flashed UK 7510 Version (everything with odin 1.85). Works great now, better then ever....
But and here is the problem, if i want to flash the zip for easy-root from internal sd card using stock recovery mode, it can't be mounted (see attached pictures).
I looked all day long on xda without finding a solution fitting for me. Maybe i'm searching with the wrong words, don't know. There are many solutions for a external sd card, also for different devices, but how can i solve my problem with a gt-p7511/7510?
Hope that someone can help me, don't want to kill the tab by using a try-and-error-method.
And please don't kill me directly, if i did something wrong, just getting started and want to learn now activ, after just reading xda for years.
Thanks for your help!
Just to avoid anybody to think i'm blind, yes i read also these two threads without beeing convinced that they would help me:
forum.xda-developers.com/showthread.php?t=1804824
forum.xda-developers.com/showthread.php?t=1808560
edit 2:
Just to prevent anyone to stick at the same trapp as i did, all stock recovery from ics and up where patched to prevent access to sdcard from there. This might be clear to many here, but it wasn't to me. Thanks to msedek, who lighted me up, my "problem" is absolutely normal and wished by devs. Just didn't delet my post becaus about 100 people seemed to be interested so there could be need to state that clear.
Sorry to post bs. If someone thinks my post isn't helpful at all it can be deleted also.
I return now back to read-only-state in the forum, there is still much more to learn...
Hi, I have the same problem on my GT-P7500 (Galaxy Tab 10.1).
If I flash with Odin the stock HoneyComb firmware, all returns working as usual.
If I flash with Odin the stock ICS firmware, I get this issue and can't install anything on recovery because it says
E:unknown volume for path [/sdcard]
by the way I'm happy that you confirm this isn't my fault on something :angel:
Anyway, now the only method to get a working root seems to be:
1) Flash HC
2) Root as usual
3) Do the OTA update to ICS
The first time I updated to ICS, I've done this way because I had original Rooted HC and after the update, Root was still present.
By
gfreeman86 said:
Hi, I have the same problem on my GT-P7500 (Galaxy Tab 10.1).
If I flash with Odin the stock HoneyComb firmware, all returns working as usual.
If I flash with Odin the stock ICS firmware, I get this issue and can't install anything on recovery because it says
E:unknown volume for path [/sdcard]
by the way I'm happy that you confirm this isn't my fault on something :angel:
Anyway, now the only method to get a working root seems to be:
1) Flash HC
2) Root as usual
3) Do the OTA update to ICS
The first time I updated to ICS, I've done this way because I had original Rooted HC and after the update, Root was still present.
By
Click to expand...
Click to collapse
Only method?? Once youve installed ICS, use Odin to flash CWM and then install the root zip
http://forum.xda-developers.com/showthread.php?p=14020091
Sent from my GT-P7510
gfreeman86 said:
Hi, I have the same problem on my GT-P7500 (Galaxy Tab 10.1).
If I flash with Odin the stock HoneyComb firmware, all returns working as usual.
If I flash with Odin the stock ICS firmware, I get this issue and can't install anything on recovery because it says
E:unknown volume for path [/sdcard]
by the way I'm happy that you confirm this isn't my fault on something :angel:
Anyway, now the only method to get a working root seems to be:
1) Flash HC
2) Root as usual
3) Do the OTA update to ICS
The first time I updated to ICS, I've done this way because I had original Rooted HC and after the update, Root was still present.
By
Click to expand...
Click to collapse
I flashed with mobile Odin and had the same problem. I think Samsung blocked it so we are not able to root easily. This was the case in 7510 in honeycomb also. Anyway, I used Odin to install team win recovery and rooted it!
Sent from my amazing 10.1 galaxy tab
Yes, thats what i was informed about to by msedek. It's a issue to might prevent us from flashing without custom recovery.
Obviousely it worked, thought i did something wrong and my tab didn't act normal
lesson learned
Related
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Joeyjr25 said:
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Click to expand...
Click to collapse
Start with getting back to stock using this guide. Check for ICS bootloaders too, you probably flashed them and you have to get stock ones back (careful, flashing bootloaders can cause hardbricking). Once you're back to stock and rooted, you shouldn't need to ever use PC Odin again.
Then use this guide for rooting/flashing.
One other note: when you tried to install CWM, it sounds like you loaded an update.zip onto your phone then tried to install it using stock recovery. Stock recovery won't let you install unsigned update.zips, which is why that method for getting CWM on your phone will never work (hence the authentication error and installation abort). For our phone, CWM is only included in custom kernels, that's the only way to get it on there, and don't even think about updating or changing it via other means. Just flash a custom kernel, it'll include CWM, use it until you want to switch kernels.
Hit my thanks button, I was really nice this time. And post in Q/A next time as well.
EDIT: Skip the second guide if all you want is stock. You should be able to update OTA after following the first guide. Though even if stock is what you want, I highly recommend flashing a custom GB kernel because a) they're more stable and faster and b) you'll have CWM in case you need it.
You started off mentioning about "leak ics" which I have absolutely zero experience.
My suggestion:
1. Try to get it back to stock. Make sure it works correctly.
2. If hasn't rooted yet, do so.
3. Getting CMW into the device by flashing custom kernel.
4. From there, install any ICS ROM you want.
Hi all - the weirdest thing is happening to me and it is definitely something I've done but I haven't the slightest what it is.
I've got CMX right now, and I've tried to go to a couple of ICS ROMs (Task, Sonic). They flash just fine, but on the new system if the screen goes to sleep the video flickers on screen wakeup. I have tried to remedy this by flashing an ICS kernel but haven't had any luck whatsoever. So today I thought I'd go back to my Nandroid backup that I took on CWM 5.0.2.7 way back on the 1st before I rooted my tab. I was on (and prefer) TWRP so I used Odin to re-flash the original recovery, wiped everything (including format /system from the Mounts menu to wipe the ROM) and restored the backup. Everything seemed fine. But to my horror, I locked the screen and woke it up to find the same flickering!!!!
I rebooted back into recovery and flashed TWRP back on so I could restore my CMX backup and I'm back to normal again. But now I feel like I'm stuck here, and the only way I'm going to be able to fix this issue is by using Odin to flash a stock firmware package. I really don't want to have to do that if I don't have to but will if I need to of course...
The one thing I haven't been able to get an answer on is before blowing everything away is what I'm asking now...in thinking about it, I had taken the backup before flashing a bootloader to fix my "rolling recovery screen" issue. Could the cause of this type of problem be a bootloader that the ROM doesn't like, or is this a crazy assumption?
OK I'm going to bump this thread with a simple to-the-point question - hoping for an answer as I work out my theories.
For those of you who have flashed ICS and custom recovery with no "rolling/flickering" issues - are you using an unlocked bootloader?
For the bootloader you just hit the point my friend,the bootloader that we use to fix rolling recovery problem has issues with most kernels except Pershoot's HC or CM9...
For your problem you should think of grabbing the official ICS or HC(just for getting rid of screen flicker),and in addition to flashing it you should extract it's stock bootloader,make a. tar.md5 out of it and keep it for future similar problems...
Note that the bootloader can only be flashed using Odin in PC and CWM or even stock flashing using MobileOdin can't make changes to it(or recover it)
For now there is not a proper fix for that but I think the best way is to have the stock bootloader and use ROMmanager or MobileOdin for flashing(since the recovery rolls with stock bootloader)...
Yeah I flashed stock ICS and rooted yesterday. I am just going to fight through the rolling recovery for now and stick with ICS until we can do more.
Thanks for the response!
some trick:you can rename the zip files you're going to flash so that their name starts with "Z",it's then easy to navigate to them(just press vol down twice)
Yep! That works, and you can also rename files as update.zip and use that option I believe. It's time to think outside of the box a bit with regard to flashing some ROMs...thats the bottom line. i am sure there are a few devs on this site that would appreciate it if we did more of that lol!
guys im really getting the same problem now... and i dont know what to do
would you be able to help me please?
Hi,
I am trying to root a second T959 phone, my wife's, but am not having much luck. It is currently running Froyo 2.2 w/ KB5.
I tried using AIO Toolbox to root, but that did not work. The first problem I encountered is that it complained that 'verification failed' when I tried to reinstall package.
I searched through the forums, and found that I have recovery 3e. Noticed that on the recovery menu too. So I did what this thread indicated:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=root+3e
Ran the install.bat, and it did its work. I was still not able to apply the update.zip, but I was able to run 'SuperOneClick' to root the phone, or I thought. SuperOneClick reports that I have rooted the phone, but none of the apps think so. So right now, I am still stuck, with a phone that I cannot root.
I found this other thread talking about using ODIN to flash in a CWM instead of using recovery. I am a bit hesitant about this, as I am worried about flashing anything at this point without a backup.
I realize that I could ODIN to stock and I would be able to root and upgrade ROMs without problems, but I would really like to backup using Titanium before doing so.
Maybe I missed something somewhere, but is there a way that I can root this phone on the current fw?
Solved
Ok, found this thread with further searching, and it solved my problem.
Phone rooted and upgraded to JB! Woohoo!
http://forum.xda-developers.com/showthread.php?t=925400
thank you for posting where you found how to root. helped me alot i was running kb5 and now have it rooted and can access CWM. My question to you is did you just download and install the rom? im still on kb5 and am rooted and looking for any OS upgrade GB at least but dont have access to a pc all the time. Do i have to have one or are there any roms that i can flash from my rooted stock froyo?
shizno said:
thank you for posting where you found how to root. helped me alot i was running kb5 and now have it rooted and can access CWM. My question to you is did you just download and install the rom? im still on kb5 and am rooted and looking for any OS upgrade GB at least but dont have access to a pc all the time. Do i have to have one or are there any roms that i can flash from my rooted stock froyo?
Click to expand...
Click to collapse
You don't need a computer to flash a ROM. Find a ROM you like, I recommend a JB ROM as they are supported, anything prior will not be. Download the ROM zip and gapps zip if required. Use a root file app, I use root browser, and move the zips from
sdcard/download to sdcard. Boot to recovery, wipe cache, advanced>wipe dalvik cache, wipe data/factory reset, install zip from SD, install ROM then install gapps, reboot and profit!
*you might have to flash the ROM more than once as it has to update recoveries and partitions.
Sent from my SCH-I535 using xda premium
ty for your reply it was very helpful. i got impatient and flashed a ram before i saw it and everything went perfect. But i do appreciate not only the reply but the steps as well. i am now running iczen with subzero on my vibrant and its the most beautiful thing ive ever seen. lol. i dont even recognize my phone anymore and it feels like i just got a 800 dollar phone for free. i have even recommended every person i know with an android phone to join the site as well as read all steps carefully. thank you again sorry for the long post but i have just been so thrilled about the results i have got.
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
muffintastic said:
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
Click to expand...
Click to collapse
To avoid brickbug is by flashing JB 4.1.2. (good alternative!)
But if you really like ICS then i suggest you move back to 4.0.3. There is no avoiding brickbug on 4.0.4.
If you have rooted it, you can check with 'Brickbug check' app on google play, to see if you have sane (or insane) chip (brickbug or not), cause most custom kernels and roms have found a solution to this bug, and use it on their roms/kernels. Which means on those you can safely wipe and restore etc.. (but check brickbug app first on google play)
Yep. Don't wipe a rooted phone running 4.0.4. And if you're really paranoid, don't even wipe a non-rooted phone running 4.0.4 (Entropy mentioned at least one case he knew of where someone borked their phone doing a wipe on a phone running 4.0.4 via stock Android recovery, tho it seems to be very rare).
The TL;DR is don't run rooted stock 4.0.4 if you mess with your phone in any way.
I know that's not a fix, but that's because there isn't one. Some chips aren't susceptible to the bug; there's an app floating around here somewhere/Google Play where you can check which chip you have (seems to be more that are susceptible).
Your 1st paragraph is a load of crap.Bootloop has nothing to do with "brickbug".More like by you not running kernel cleaning script,or not factory resetting before/after flashing a new rom.
As mentioned by others,just dont have 4.0.4 running on your phone.So you are still left with over 100 custom/stock roms to choose from........lol
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Hopper8 said:
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Im not sure Hopper.I am leaning towards the restore would be "cancelled" due to not being complete,rather than it succeeding leading to bootloop.
But hes not said.
And he cant get "factory" rom with a restore as it didnt come with cwm lol.
Sorry to clear things up.. I updated it to 4.1.2 via Kies many months ago. I used PhilZ method to root, no problem. Few months down the line since then I put LiquidSmooth 2.4 (few days ago) then restored a backup from PhilZ recovery and put 4.1.2 and everything back on no problem. Then restarted the phone and it when into a boot loop of the Orange and Samsung logo.
I'm not stupid as I've rooted my own SGS3 and Samsung Galaxy ACEs etc, Just forgotten to put that info in lol and yes I always use the Factory Reset to install a new rom.
And yes when I managed to get it restored from this so called boot loop (by putting 4.1.2 Orange UK firmeware back on via Odin) the EMMC brick bug is present as i've checked via an app via Google Play. My overall goal is to eliminate this problem or temp fix so I can put different roms on and if I don't like them recovery back to the latest restore without issues.
Are we on the same line now ?
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
help me out here please
MistahBungle said:
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
Click to expand...
Click to collapse
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
andreshbozo said:
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
Click to expand...
Click to collapse
Here is my situation.
I had 4.1.2 JB. Installed CM11 M8 and CWM_6.0.4.7(coming previously from Siyah) at the end of July. In the beginning of October my phone just shut down. That happened before on the same and previous rom so I wasn't worried. I turned it on and phone was in bootloop. That was strange because the last time that happened I installed Chainfire. So bootloop without any cause..that was strange. I tried making a backup before flashing the ROM. But I got an error. I can't remember but I can dig it somewhere if you want it. I tried then flashing recovery(bad idea) and Odin again reported an error. When I restarted phone I noticed that my Recovery mode was gone. Just gone and with no solution on how to restore it. I tried numerous methods OMAP drivers, heimdall, .pit file method but nothing. So I brought my sgs2 to the store where I bought it and they concluded that it was bad eMMC chip.
Now, your problem reminds me of mine because Odin wouldn't want to flash anything without an error(well, not exactly anything, I managed to flash some partition using Heimdall but it was not sufficient) but it doesn't have to be.
What version of cwm were you using?
I´m on S3 International and have flashed Philz Recovery with ODIN and flashed Wanam latest 4.3. Works great! I have even flashed the S4 launcher and weatherwidget and all is still well.
However, now I want to try to run MIUI on my S3. After backing up my S3 and started to flash I got Error Status 7. I have read some threads about it and the first I wanted to try was to install another recovery. But even when I flash another recovery I get Error Status 7. I suddenly can´t flash anything at all. Does this have to do with the fact that I ticked the "disable recovery flash" when exiting the Philz recovery after starting this journey when beginning to root and so on? If so... how do I get it "unticked"?
First up...
Will flashing another recovery (CWM for example) help me get past this Status 7 problem?
Second...
If I descide to flash CWM Recovery via ODIN will it reset my current ROM in any way or will everything stay the same?
Third...
I read somewhere that I can modify the updater-script in the META-folder. Is that really a afe way to go about it? It feels kind of wierd when the *.zip´s are made for the right phone, model, version and so on...
Thanx for the help, guys!
Manneman32 said:
I´m on S3 International and have flashed Philz Recovery with ODIN and flashed Wanam latest 4.3. Works great! I have even flashed the S4 launcher and weatherwidget and all is still well.
However, now I want to try to run MIUI on my S3. After backing up my S3 and started to flash I got Error Status 7. I have read some threads about it and the first I wanted to try was to install another recovery. But even when I flash another recovery I get Error Status 7. I suddenly can´t flash anything at all. Does this have to do with the fact that I ticked the "disable recovery flash" when exiting the Philz recovery after starting this journey when beginning to root and so on? If so... how do I get it "unticked"?
First up...
Will flashing another recovery (CWM for example) help me get past this Status 7 problem?
Second...
If I descide to flash CWM Recovery via ODIN will it reset my current ROM in any way or will everything stay the same?
Third...
I read somewhere that I can modify the updater-script in the META-folder. Is that really a afe way to go about it? It feels kind of wierd when the *.zip´s are made for the right phone, model, version and so on...
Thanx for the help, guys!
Click to expand...
Click to collapse
You didn't mention the version of Philz you were using. Anyway, the error 7 can be caused from 2 main reasons:
1- Older recovery version. Flash the lastest recovery available (6.15.4) and try again: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300
2- Corrupted rom download.
To your 2nd question- if it doesn't work with Philz, it will not work with any other recovery.
Well... when I asked about how to go about rooting just a week ago I got links to what I needed. And with that I got a link to Philz Recovery. But now I see that it was an old version (6.07.9)
I´ll try with the latest one and see where that takes me.
Edit:
Flashed the latest Philz and took a new backup just in case. It didn´t work. Still Status 7. So I re-downloaded the ROM just in case it was corrupted but still the same... aborted Status 7.
So... now what? Am I screwed?
I read somewhere that it could have something to do with the fact that I use an external SD-card. Will it really make a difference if I flash it from the internal memory and even if i take the SD out of the phone?
Manneman32 said:
I read somewhere that it could have something to do with the fact that I use an external SD-card. Will it really make a difference if I flash it from the internal memory and even if i take the SD out of the phone?
Click to expand...
Click to collapse
Worth the try
Here 2 relevant threads I found:
http://en.miui.com/thread-6429-1-1.html
Follow galnet post (page 7):
http://forum.xda-developers.com/showthread.php?t=1749392&page=7
Sent from my GT-I9300 using Tapatalk
So... the links refer to downgrading to a really old recovery used for rooting with CF or unticking the "disable signature check" ... feels strange.
Is there anyway to explain why this error occurs?
Last question before giving this up...
If I should downgrade my recovery, is that safe? And how will it work with downgrading from a 4.3 ROM to a 4.1.1 ROM. Is this nothing to be concerned about?
// Manneman
Manneman32 said:
Last question before giving this up...
If I should downgrade my recovery, is that safe? And how will it work with downgrading from a 4.3 ROM to a 4.1.1 ROM. Is this nothing to be concerned about?
// Manneman
Click to expand...
Click to collapse
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221