Related
hello, i just got my first android phone so I'm new to this sort of stuff, though I love being able to unlock hidden potential of different devices, so naturally I discovered the ability to root smart phones and all that good stuff.
The model I have is the Samsung Galaxy Gio GT-S5660M. It's running 2.3.4. Gingerbread version.
I've been reading a lot of guides and for the most part rooting and adding additional utilities like flash, etc. seems pretty simple. However, I have not yet been able to find out how to create a back of up of my stock firmware when I bought the phone in case I end up bricking it, or decide I want to return to stock.
I've read many guides that claim to show how to create back ups and recovery points, but I'm still having trouble understanding it.
To be more specific, I would like to create as opposed to download, a back up of the phone in it's current state which is, as I said earlier, stock. I did a factory reset since I had some stuff installed while I was fiddling with it for the first time.
thx
You have to root it before you can back up stock rom so, firstly you root it (you can find guides here on xda)
Then install clockworkmod recovery: warning: DON'T EVER USE ROM MANAGER TO INSTALL CLOCKWORKMOD ON YOUR GIO, IT WILL BRICK YOUR PHONE!! use one of the recoveries found in xda, you will also find guides to install them there.
Then third; backup in clockworkmod using "backup and restore"
Sent from my GT-S5660
iok1 said:
You have to root it before you can back up stock rom so, firstly you root it (you can find guides here on xda)
Then install clockworkmod recovery: warning: DON'T EVER USE ROM MANAGER TO INSTALL CLOCKWORKMOD ON YOUR GIO, IT WILL BRICK YOUR PHONE!! use one of the recoveries found in xda, you will also find guides to install them there.
Then third; backup in clockworkmod using "backup and restore"
Sent from my GT-S5660
Click to expand...
Click to collapse
so first of all, what I'm looking for is called a ROM right?
what I don't get though is how come I need to modify the device before creating the backup. Isn't the phone modified at that point? Or is the stock configuration being stored somewhere on the phone that I can't see without clockwork?
You cannot create a backup without the recovery mod CWM Clockwork Recovery Mod. But to install this you need your device rooted (modified so you can modify and view system files)
gfyrdr said:
so first of all, what I'm looking for is called a ROM right?
what I don't get though is how come I need to modify the device before creating the backup. Isn't the phone modified at that point? Or is the stock configuration being stored somewhere on the phone that I can't see without clockwork?
Click to expand...
Click to collapse
1 - you don't need to search for a rom to backup your stock rom
2 - you need to root your phone in order to be able to backup your rom
3 - you need to install a more advanced recovery (program "similar" to pc BIOS) in order to do a nandroid backup
4 - after you flash that more advanced recovery (aka CWM -> ClockWorkMod), you backup your rom in "backup and restore" menu, backup. It will then store your rom in a folder.
5 - you should strongly consider after that, to install a custom rom made by many of the devs here on XDA in order to have a better experience with your phone...
0M3G4_ said:
1 - you don't need to search for a rom to backup your stock rom
2 - you need to root your phone in order to be able to backup your rom
3 - you need to install a more advanced recovery (program "similar" to pc BIOS) in order to do a nandroid backup
4 - after you flash that more advanced recovery (aka CWM -> ClockWorkMod), you backup your rom in "backup and restore" menu, backup. It will then store your rom in a folder.
5 - you should strongly consider after that, to install a custom rom made by many of the devs here on XDA in order to have a better experience with your phone...
Click to expand...
Click to collapse
+1 That was what I wanted to say
I've already uploaded a stock ROM backup last fall of the same Gingerbread ROM you're running, along with instructions on how to make one yourself or flash mine.
The best advice I can give you is: research, research, and more research.
Good luck,
Darkshado
Sent from my Nexus S using XDA
What software do you recommend to clockworkmod Gio with?
s!mon said:
What software do you recommend to clockworkmod Gio with?
Click to expand...
Click to collapse
I use px-cwm-v2.zip recovery.
You flash it using stock recovery.
thx for the replies. I will give it a try.
Darkshadow, whats the thread's name where you posted the ROM and instructions? I'd like to check that out too.
Also, whats a good rom to consider upgrading to? Something that has the ability to play flash videos.
EDIT:
If I understand correctly, roms are basically whole operating systems that have been customized by the developer. So a rom can be already rooted and have clockwork as well as other custom stuff, and I just need to flash it. The alternative to this is to do everything manualy... root the current OS, add clockwork and whatever else. Correct?
Also, I'm not sure yet if a rooted phone has any extra options on it's own, or if it's only a set up that's sole purpose is to allow other applications to be installed who then will give the user better control over his device.
I've run into a little problem.
I'm following this guide: http://forum.xda-developers.com/showpost.php?p=16963172&postcount=1
I've got Odin and the tar downloaded, but when I go into download mode with my phone and connect it to the PC, it says that the device driver was not successfuly installed, and I get no confirmation in Odin that a connection has been made between the phone and the program.
What am I missing?
Thx.
EDIT:
Nevermind, I needed to install Kies. Don't even need to run it. Apparently it has the driver that's needed.
Okay, I've rooted my phone successfully. Now the next step is to install Clockwork and create a back up.
Now that I understand a little bit the way Odin and flashing ROM works, I think it would be better to just download a stock ROM and in case something goes wrong, I can just flash it the way I flashed the rooted one.
(I think I saw a completely stock ROM somewhere for my model but I don't remember where. A link would be appreciated if it exists.)
Correct me if I'm wrong pls.
Also, if I do that, then is there any reason to install Clockwork since I've read that many ppl have issues with installing it and it's riskier than rooting or installing other software.
Right now I think what I'm most interested in is installing Adobe Flash Player 11 or something of the sort that can play flash videos and streams.
^
http://forum.xda-developers.com/showpost.php?p=19623732&postcount=1
taken from the sticky
i'm also thinking of installing cwm
looking at the sticky, http://forum.xda-developers.com/showpost.php?p=20397988&postcount=8
how outdated is this cwm?
I'm using Opera as my browser so from what I've learned, flash doesn't work with it period. Is skyfire a good alternative?
Also, like I said, I don't think I need the clockwork if I can get a clean stock ROM that I can just flash if something goes wrong. As I don't intend to download many apps or add many phone numbers (memorized instead), a backup isn't really needed.
nvmd, i just went ahead and installed the cwm in that link, there's a 5.0.2.7 though if that is even the newest one
now, i cant seem to backup my phone
it says it cannot mount /system
try dolphin browser
anonxlg said:
nvmd, i just went ahead and installed the cwm in that link, there's a 5.0.2.7 though if that is even the newest one
now, i cant seem to backup my phone
it says it cannot mount /system
try dolphin browser
Click to expand...
Click to collapse
Did you pick the ext4 + rfs version?
Sent from my GT-S5660
Clockwork is not riskier than other things you do. Just follow steps and you see no problems.
anonxlg said:
^
http://forum.xda-developers.com/showpost.php?p=19623732&postcount=1
i'm also thinking of installing cwm
looking at the sticky, http://forum.xda-developers.com/showpost.php?p=20397988&postcount=8
how outdated is this cwm?
Click to expand...
Click to collapse
its an older version, its 5.0.2.7, theres also 5.0.2.8 but these give some problems after installing/wiping, so some people still use the older version.
Hello guys,
I'm new here. I have the same problem as anonxlg. It says can't mount system. I also used the version from the big thread for new users. Can anyone enlighten me on what to do? I've been searching the forum and google, but can't make it work. I feel like a compleet noob now, and I don't feel special about it.
RJ88
Edit: I kept searching, and finally found a working 5.0.2.7 version. First I had another 5.0.2.7 version, but when I tried to install it didn't work. I finally found "signed_cwm-5.0.2.7-flashablezip-ext4+rfs.zip (Flash from Recovery)" on http://forum.xda-developers.com/showthread.php?t=1421650 (through google actually. I have to get used to this site), and I'm making my backup now.
thanks RJA88, backup worked
edit/update
i used the cwm linked and backup worked, i tried installing cm9 beta8 (galaxyics), and it would get stuck after samsung bootscreen (it flashes a white pick or soemthing before full back screen)
i tried restoring backup i made, and it didnt work, some mount error again
i reverted back to 5.0.2.6 and did the restore backup again, and this time it goes up the the galaxy gio gt5660m screen and just stop..
note that i do not know what the rfs/ext4 is for for the gio if that is what is causing problems
My vzw nexus has been running mRom version x.x for sometime. I went to install the upgraded 4.2 rom via clockworkmod, (wipe cache and dalvik, flash over current rom) and it appeared to install successfully. However, when I rebooted I saw the lock screen for a split second and it just started to boot loop. I rebooted back into recovery and wiped all data and tried to reinstall the rom via through the new 0 partition, but I get the error symlink: some symlinks failed
E: Error in /sdcard/0/mRom_v3.0_JOP40C.zip (status 7)
I think that this may have something to do with the multiple users in 4.2, but don't quote me on it. I cannot get my computer to recognize my phone, when I go to mounts in cwm I can mount everything except the sdcard, although I think this problem was evident before I flashed. Any suggestions? I could try to restore to stock using galaxynexusrestore-- http://forum.xda-developers.com/showthread.php?t=1743939 but I have not tried it before so I cannot speak to weither it will work or not.
HELP!
Always always wipe data when changing an Android version. Unless it comes via OTA, which is specifically designed to fix all the little problems that will arise.
As to how to fix the problem, flashing a factory image
http://forum.xda-developers.com/showthread.php?t=1626895 will probably work. Just follow the rules for Toro. The toolkit you linked may work, but it's generally a better idea to not use them and actually familiarize yourself with how to fix things yourself, you'll be less likely to make mistakes in the future.
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Misread OP.
ironerd said:
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Click to expand...
Click to collapse
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
same problem, stuck at JB logo
Marisa said:
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
Click to expand...
Click to collapse
I was running stock JRO03O with Clockwork Recovery Mod and decided to flash the JB 4.2 ROM from Grouper (http://forum.xda-developers.com/showthread.php?t=1993545 - I can't post there since I'm too new).
The update must have succeeded, because I can see the new 0/ partition on my phone, but it won't boot past the "X" logo. I can boot into CWM and try various things, but of course because of the data structure changes, I can't actually recover to my last save. When I'm home, I'm hoping I can get the CWM backup off my phone to restore later, but without a terminal in CWM, I can't try to fix the path.
It's nice to hear that CW is working on a fix - I hope it's retroactive (I mean, helpful to those of use who already screwed up). Also, I've never flashed anything but OTA, so I didn't realize I needed to wipe data before flashing something that's supposed to be almost stock. I guess it matters how different from stock the ROM actually is.
What's next? I'll try to interface with my PC at home. If others have this problem, I'd be happy to hear your success (or fail) stories. I'll share mine once I've tried it.
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Koush
When trying to restore CWM backup move previous backups AND blobs folder to /data/media/clockworkmod if the folder does not exist simply create one or if unsure just go to recovery and make new backup, it will create necessary folders for you then move (or copy to be safe) files to location.... The blobs folder is what I was missing and why I kept getting error while trying to restore.
Click to expand...
Click to collapse
This should help your problem solving for the moment, if you're familiar enough with ADB to move the files that way it shouldn't take very long at all
thanks, and update of my status
Marisa said:
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Click to expand...
Click to collapse
Thanks for the extra insight. I wrestled with my phone all night and finally got it back to 4.1.1 (JRO030). Along the way I screwed up my adb or fastboot drivers, and for all my efforts I couldn't get any of my nexus toolkits to recognize the phone as in fastboot mode. Adb was fine, but fastboot was a no-go. I moved to a fresh computer after someone else had success with that, and read up on how to do a manual (adb command line) flash to factory image.
Now that that's done, I'm hoping I can restore from CWM to get back to where I was. If not, then yuck, but I'm optimistic.
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
I initially flashed all the way back to the TWRP build before 2.3.1 but stopped there. I'll report back with results of your recommendation in the morning!
prboy1969 said:
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
Click to expand...
Click to collapse
ROM Manager was something I tried as a last resort as well, it flashed the custom recovery alright, but soft bricked it with a redundant recovery bootloop. I got past that by Odin-ing back to stock.
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
prboy1969 said:
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
Click to expand...
Click to collapse
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
n3td3v said:
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
Click to expand...
Click to collapse
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
prboy1969 said:
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
Click to expand...
Click to collapse
I tried formatting the sdcard as well as without the sdcard and even with a different one to no avail. I'm still on the hunt for pda, csc, etc. Odin files. My last resort will be to figure out how to get it replaced at Sprint as a defective device lol
Sent from my SPH-L710 using xda premium
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
billard412 said:
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Yes, stock recovery allows clearing of cache, depending on whose stock recovery I flash. If I flash the toolkit version of stock, I can clear no problems. There are a couple of other stock recoveries, such as this one, in which everything fails as well.
FYI, I have even flashed the stock builds you have on sxtp with the same results.
Thanks for this -- you solved my problem...at least mostly.
I tried to root a new Sprint SG3 by ODIN'ing CWM and then flashing a root.zip file. That epic failed just like your situation where nothing would mount in recovery whether I used CWM or TWRP. I am assuming that something must've changed on the Sprint S3's and that root method must not work anymore (for whatever reason). So I decided to go back to stock recovery and just wait and see if anything further is discovered about this here (I'm not a dev, so I have to wait for other more talented people to solve my problems). However, the stock recovery image that I downloaded from the same "Easy Root" tutorial here didn't work and I still couldn't mount anything.
Saw your post where you stated that the Toolkit stock recovery image worked, so I just tried that and score! However...my poor little recovery android is on his back with a red triangle and a "!". Everything mounts, I can wipe cache, browse around for an update, etc., but I'm a little concerned that my little Android is sick. Should I be? Is that because I have a flash count of 5 so it thinks I have a custom ROM?
Sorry to hijack your thread a little, but my problems seems to be related.
n3td3v said:
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
Click to expand...
Click to collapse
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
swiggs98 said:
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
Click to expand...
Click to collapse
Same boat. Rooted probably 6 S3 before now and my wife's new S3 I am seeing same thing.
Sent from my SPH-L900 using xda app-developers app
I'm having the same issue. I finally downloaded an image that allowed me to flash it but I still cannot mount anything in recovery? Any help would be nice
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
n3td3v said:
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
Click to expand...
Click to collapse
Folks, A quick search would have led ya here : http://forum.xda-developers.com/showthread.php?t=2183910&page=4 This is a known issue with both TWRP and CWM recoveries on newer S3's. Devs are working on it to find a solution. Just a matter of being patient and waiting. IF you just want root access, you can odin a pre-rooted rom to the phone with no issues. You'll atleast have root at that point. Just unable to change rom/kernels on the fly.
I achieved root with virtually no issues but thank you for the link!
Sent from my SPH-L710 using xda premium
Hi, I will have my hands on this tablet very soon and want to use the Cleanrom that is listed in a thread here. This will be my first time doing this and have been searching around for a guide. I have read a few bits and pieces but would like someone to explain in a few steps so i can get this right the first time.
I found a guide to Root it at rootgalaxynote.com but would like to understand how to install the CleanROM.
Hello,
You have to install TWRP Recovery first, then you need to copy Rom.zip to storage and then flash it using Recovery, dont forget about Wipe.
52224489
WeedyEyes said:
Hello,
You have to install TWRP Recovery first, then you need to copy Rom.zip to storage and then flash it using Recovery, dont forget about Wipe.
Click to expand...
Click to collapse
I havent installed anything yet as i will be receiving it for christmas. Not 100% sure on process so was posting here hoping someone could explain the process a bit more in laymans terms as this will be the first time i will be doing this. i understand you have to root the device so you can change the ROM, wasnt sure on what to do after that.
reetzy said:
I havent installed anything yet as i will be receiving it for christmas. Not 100% sure on process so was posting here hoping someone could explain the process a bit more in laymans terms as this will be the first time i will be doing this. i understand you have to root the device so you can change the ROM, wasnt sure on what to do after that.
Click to expand...
Click to collapse
All you need is to Install Custom Recovery to change ROM, that will allow you to do anything you want with your device (such as System Backup/Restore, installing .zip packages, and etc.) read thread about TWRP so you can find everything you need to know.
But notice the fact you'll lose your warranty installing custom roms, as I know there is no way to change warranty bit back to 0 yet.
All information you need to know about Custom Roms is already there.
WeedyEyes said:
All you need is to Install Custom Recovery to change ROM, that will allow you to do anything you want with your device (such as System Backup/Restore, installing .zip packages, and etc.) read thread about TWRP so you can find everything you need to know.
But notice the fact you'll lose your warranty installing custom roms, as I know there is no way to change warranty bit back to 0 yet.
All information you need to know about Custom Roms is already there.
Click to expand...
Click to collapse
Thanks Weedy :good: Once i get this tablet i will give it a go.
Can you give me a link to the TWRP thread you refereed to thanks.
http://forum.xda-developers.com/showthread.php?t=2515656
Here you can find TWRP. I would recommend flashing the ".0"version because some people are having problems with the newer one
Worked fine for me , just did the same process as you
Sent by my Note 10.1 2014
benni2903 said:
http://forum.xda-developers.com/showthread.php?t=2515656
Here you can find TWRP. I would recommend flashing the ".0"version because some people are having problems with the newer one
Worked fine for me , just did the same process as you
Sent by my Note 10.1 2014
Click to expand...
Click to collapse
Thanks, all i need is Santa to hurry up now lol.
Are you sure you wanna get P600 not P605?
Make sure you get the right version, whether Quality or Exnyos. I had a freeze until I got the right version.
Sent from my SM-P600 using Tapatalk
In this guide what is this file for ?
Step 3. Download and unzip P600_Autoroot.zip:
rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-2014-edition/
Edit: Should i do this first before the TWPR?
Build says CleanRom 1.0 but all apps are still present
My build says CleanRom 1.0 but I still have all of the apps that others say are removed such as Sketchbook. My note was rooted using the AutoRoot file with Odin and then the stock recovery was flashed. I then used the twrp 3.0 file and booted into recovery. I then installed CleanRom (without reset per instructions) and the device rebooted and everything worked except all of the apps were still there. I then tried to re-flash CleanRom and perform the wipe but I then got stuck on the Samsung splash screen to no avail. I booted into recovery and tried re-flashing the CleanRom zip to no avail. All I could do to get this thing booted was to flash the auto-root file again in Odin, re-flash twrp, and install cleanrom again from the recovery but all of the apps are still there. Before I did any of this I had a bunch of the bloatware either frozen or uninstalled in Titanium but now some of those apps show lines through them in TBP. Either way, my device is showing CleanRom 1.0 under the build but I really don't think it is... any ideas on how to fix this?
Hi i'm a newbie on android
i've tried to install this rom a lot of time but unsuccessfully at any time
i've tried all the solutions i found here but none were successfull
i am under TWRP 2.6.3.0
my tablet is rooted but after the rom flash ,when i reboot ,just after the "galaxy note edition 2014" logo there's a black screen
the only way to repair is to flash with the mk1 stock rom after or to restore my old version saved with TWRP
can someone help ?
thanks
shoresteve626 said:
My build says CleanRom 1.0 but I still have all of the apps that others say are removed such as Sketchbook. My note was rooted using the AutoRoot file with Odin and then the stock recovery was flashed. I then used the twrp 3.0 file and booted into recovery. I then installed CleanRom (without reset per instructions) and the device rebooted and everything worked except all of the apps were still there. I then tried to re-flash CleanRom and perform the wipe but I then got stuck on the Samsung splash screen to no avail. I booted into recovery and tried re-flashing the CleanRom zip to no avail. All I could do to get this thing booted was to flash the auto-root file again in Odin, re-flash twrp, and install cleanrom again from the recovery but all of the apps are still there. Before I did any of this I had a bunch of the bloatware either frozen or uninstalled in Titanium but now some of those apps show lines through them in TBP. Either way, my device is showing CleanRom 1.0 under the build but I really don't think it is... any ideas on how to fix this?
Click to expand...
Click to collapse
Before flashing your rom perform a factory reset in twrp and format /data. All your apps will be deleted and you should be fine if you are stuck on the samsung boot logo it might help to boot into recovery and format /cache and dalvik cache
Sent by my Note 10.1 2014
Messed it up even more
benni2903 said:
Before flashing your rom perform a factory reset in twrp and format /data. All your apps will be deleted and you should be fine if you are stuck on the samsung boot logo it might help to boot into recovery and format /cache and dalvik cache
Sent by my Note 10.1 2014
Click to expand...
Click to collapse
So, I did the factory reset in twrp and then formatted the data. Naturally, everything was lost but when I went to install CleanRom it was no longer on the internal memory due to the format... but I did copy it to the Ext SD Card. MY problem is that twrp won't install the zip from the sd card. Each time it says its unable to mount "/data" even though I'm going into "advanced settings" and placing the check mark. I re-flashed twrp and tried using file manager to move the file to the internal storage but came up with the same problem. Also, I can't place the check on mount data for some reason. Now, my tablet starts to boot up but hangs on the samsung screen before the boot animation. Basically, its like there isn't any firmware on it and I tried re-doing the auto-root and stock recovery but thats a no go as well. Is this thing toasted?
shoresteve626 said:
So, I did the factory reset in twrp and then formatted the data. Naturally, everything was lost but when I went to install CleanRom it was no longer on the internal memory due to the format... but I did copy it to the Ext SD Card. MY problem is that twrp won't install the zip from the sd card. Each time it says its unable to mount "/data" even though I'm going into "advanced settings" and placing the check mark. I re-flashed twrp and tried using file manager to move the file to the internal storage but came up with the same problem. Also, I can't place the check on mount data for some reason. Now, my tablet starts to boot up but hangs on the samsung screen before the boot animation. Basically, its like there isn't any firmware on it and I tried re-doing the auto-root and stock recovery but thats a no go as well. Is this thing toasted?
Click to expand...
Click to collapse
Boot into TWRP and click "Restore Back Up" (Cannot remember exact verbiage) . Find where it says internal storage and press it and it will switch to a drop down and you can choose "External SD" Then go back and and it should be going to External SD instead of internal SD when you select install
Make sure you factory re-set. For safety, I advance wipe but I don't think that is necessary.
You may need to re-flash recovery if you're unable to access it.
shoresteve626 said:
So, I did the factory reset in twrp and then formatted the data. Naturally, everything was lost but when I went to install CleanRom it was no longer on the internal memory due to the format... but I did copy it to the Ext SD Card. MY problem is that twrp won't install the zip from the sd card. Each time it says its unable to mount "/data" even though I'm going into "advanced settings" and placing the check mark. I re-flashed twrp and tried using file manager to move the file to the internal storage but came up with the same problem. Also, I can't place the check on mount data for some reason. Now, my tablet starts to boot up but hangs on the samsung screen before the boot animation. Basically, its like there isn't any firmware on it and I tried re-doing the auto-root and stock recovery but thats a no go as well. Is this thing toasted?
Click to expand...
Click to collapse
Your device is not toasted I always have the Rom zip on the root directory of the device so formatting /data will not affect the rom zip. If you cant get it working then you might need to flash a firmware via odin and after that copy the rom on the internal root directory. Resetting your device should not format the whole internal storage so you can install the rom afterwards. Good luck mate
Sent by my Note 10.1 2014
Thanks for all the help!
benni2903 said:
Your device is not toasted I always have the Rom zip on the root directory of the device so formatting /data will not affect the rom zip. If you cant get it working then you might need to flash a firmware via odin and after that copy the rom on the internal root directory. Resetting your device should not format the whole internal storage so you can install the rom afterwards. Good luck mate
Sent by my Note 10.1 2014
Click to expand...
Click to collapse
After the holiday (and many stressful attempts) I was finally able to re-boot the device and get past the splash screen. Opening Kies seemed to "kick" past the splash screen even though it said my device wasn't compatible with Kies. Anyway, I flashed the stock recovery, wiped, reset, flashed original firmware via Odin, flashed TWRP again, and then installed the CleanRom zip. Phew... it's FINALLY over with no issues and running smooth. I think the problem came in with TWRP not wiping correctly even though it said it did. I do appreciate all of the help and advice as you guys are life-savers!
Exnyos?
sdelliott31 said:
Make sure you get the right version, whether Quality or Exnyos. I had a freeze until I got the right version.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
How do you know with version you have?
jkitsmiller said:
How do you know with version you have?
Click to expand...
Click to collapse
Wifi Only Version = P600 = Exynos processor
Lte = P605 = Snapdragon800
Gesendet von meinem SM-P600 mit Tapatalk
When I installed with TWRP 2.6.3.3 & 2.6.3.1 I got the write permission denied and then I tried with 2.6.3.0 it got hung while installing CleanRom 1.5R2. Does anyone know how to resolve this issue? Thanks
Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
ejaf said:
Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
Click to expand...
Click to collapse
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Here is the link to the latest, grab the first tar flash it via odin & you should be good to boot into recovery to flash roms.
https://dl.twrp.me/d2spr/
Lonelyskatter12 said:
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Click to expand...
Click to collapse
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
ejaf said:
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
Click to expand...
Click to collapse
Yes, the official thread is CM13, you don't need Cwm, pretty much twrp supports marshmallow now.
And i believe you would need root.
If there's any way for you to be able to download the files, id be happy to give you step by step instructions :good:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
ejaf said:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
Click to expand...
Click to collapse
Yeah the Unofficial thread was being maintained by a Developer, who stopped as soon as the officials came out.
And yes
1.) Wipe Data, Cache, System, & Internal Storage (So backup anything on there)
2.) Flash Rom, Gapps, SuperSu 2.71 (If you want root)
& should be good to go
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
ejaf said:
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
Click to expand...
Click to collapse
That's the order, now about the apn im not sure, i just use mine for wifi and stuff.
That Cyanogenmod build "04282016" wasn't running so well for me, so I'm on AICP for now.
But i would suggest, OctOs , AICP, or Exodus Roms. Those are the most stable roms for this device.
Same steps just different ROMs.
But i did hear Exodus gives you data right off the bat, so that'd be good to try
Interesting...thanks for the tips. Hopefully I won't have to bother any of you all again, since I really don't have much in the way of knowledge to return
E
FYI...was able to boot up into CM 12.1 over the weekend. Jury's still out on whether to go to a 6.0.1 based ROM, but appreciate all the help.
Eric
I found the APN fix didn't work with the CM13 rom (I've used it previously with 12.1 fine). I also found that the build-in cm update failed on 20160505 nightly. Not sure if this was just that day or a known bug.