[Q] Buying the phone today and rooting? - Verizon Samsung Galaxy S III

If I buy the S3 from a verizon store today brand new, will I be able to root it and unlock the boot loader still or will it come with a firmware too new?
Sorry if this was answered before. Tried searching but couldn't find results. If they are out there then I blame iOS 7 and my iPhone that needs replacing

I'm not sure what, if any, updates they've had in the last few months but I just got my s3 in August. I did take an update on it and had no issues with using casual to root & unlock. Perhaps someone may have a more recent experience.
Sent from my Slim GS3

Yes you will still be able to root, our 4.3 update hasn't happens yet
Sent from my SCH-I535 using xda app-developers app

Rooting is a great idea- I'm loving 4.4 on the s3.

clembrowning said:
Yes you will still be able to root, our 4.3 update hasn't happens yet
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That's great to know. I take it I can use custom recovery, and replace the ROM entirely? I don't want to deal with an OTA removing root on me.
Thanks

fbiryujin said:
That's great to know. I take it I can use custom recovery, and replace the ROM entirely? I don't want to deal with an OTA removing root on me.
Thanks
Click to expand...
Click to collapse
You should have absolutely ZERO issues with rooting/using a custom recovery, etc... Casual couldn't be any easier.

MisterSprinkles said:
You should have absolutely ZERO issues with rooting/using a custom recovery, etc... Casual couldn't be any easier.
Click to expand...
Click to collapse
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.

KutuluMike said:
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.
Click to expand...
Click to collapse
Ah crap. Thanks for the warning. I decided to order a Verizon Moto X Dev Edition. Can't wait for that to arrive.
Thanks to everyone for the info/advice.

KutuluMike said:
Not necessarily. If he gets a phone that was manufactured after ~July 2013, he'll have problems. There was apparently a silent change to the firmware/hardware/boot process that prevents any of the currently-available custom recovery packages from working. (Not clear on what the change was other than they apparently back-ported it from the GS4 and it requires a change to the recovery's kernel before anything will mount.) I've been fighting to get my brand new GS3 rooted and a custom ROM on it for almost two weeks now.
Trying to do so with Casual caused an endless boot-into-recovery loop because the recovery couldn't clear the cache and reset the 'boot into recovery' flag that ADB set; I was forced to flash back to stock recovery to fix that.
I did manage to get both TWRP and CWM loaded via ODIN, but every version I tried (dozens in all) refused to mount any partitions - it couldn't mount/read from /system or /data or /sdcard or /cache, so there's no way to flash anything. The closest I've come is by using the hacked-up versions of TWRP and CWM from this thread, but they're built for to Sprint phones, so now when booted into Recovery my phone thinks it's a Sprint and won't flash the VZW versions of anything.
So far, every person who's having this problem appears to have gotten their phone in the second half of this year, so I strongly suspect that buying one now will have the same result.
Click to expand...
Click to collapse
Not necessarily true on that... I got mine last month... I did have issues with using the latest casual Root method, but the all-in-one casual Root works perfectly! But I would suggest downloading rom manager and letting that app install recovery for you (TWRP and cwm touch both caused issues for me). If you need a step by step, pm me and I'll write it up for you...
Sent from my SCH-I535 using xda premium

Macrodroid said:
Not necessarily true on that... I got mine last month... I did have issues with using the latest casual Root method, but the all-in-one casual Root works perfectly! But I would suggest downloading rom manager and letting that app install recovery for you (TWRP and cwm touch both caused issues for me). If you need a step by step, pm me and I'll write it up for you...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I have no problem getting the recovery installed. The custom recoveries are just *non-functional* because they can't mount any partitions. The error logs' are pretty clear, and every custom recovery I've tried behaves exactly the same.

Related

[Q] Help with recovery after failed ROM installation

So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Can you check your file system and see if your CWM folder has a backup? It should be Sdcard/CWM or extsdcard/CWM. If not, do you mind flashing another rom or that same rom?
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Click to expand...
Click to collapse
2 questions: Which factory image did you use to restore (link to thread)? Did you change the default backup location in CWM (ie, did you backup to the external sd or the internal - internal is default)?
There is a file in both extsdcard and sdcard with clock work mod back up. I did manage to factory reset and re root, so phone is functional again, just with none of my apps or settings. I have a feeling I'm going to need to un root in order to re receive my JB update too?
Sent from my SCH-I535 using xda app-developers app
Didn't unlock bootloader?
I don't know for sure. I unzipped SU plus bootloader file exactly as specified in forums/video. Had no problems until I tried installing that ROM through ROM manager. And forgive me for trying that. I hadn't rooted in over a year. But main problem now is just that I want to recover how my phone was ie settings and set up if possible.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
There is a file in both extsdcard and sdcard with clock work mod back up. I did manage to factory reset and re root, so phone is functional again, just with none of my apps or settings. I have a feeling I'm going to need to un root in order to re receive my JB update too?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How big are those 2 folders?
One is 4.82 gb...so I'd think there has to be a file in there.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
One is 4.82 gb...so I'd think there has to be a file in there.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That sounds about the right size for a backup. When you go into CWM and do the restore (or restore from external - which ever has that folder, you didn't say) it doesn't show a backup?
What version of CWM are you running?
It's version CWM6023touchvzw.tar.md5. And it's on the external. But no matter which option of restore I choose in the recovery boot, it says file not found.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
It's version CWM6023touchvzw.tar.md5. And it's on the external. But no matter which option of restore I choose in the recovery boot, it says file not found.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Maybe after all that flashing and Odin-ing your recovery install got wanked, somehow.
Let's try this: it will re-install the latest CWM, clean and then let's see if it'll recognize your backups.
http://www.clockworkmod.com/rommanager/
download the touch image for the d2vzw (or just click here)
put that in the root of your internal sd card.
Open up terminal emulator on your phone and type the following:
Code:
su
dd if=/sdcard/recovery-clockwork-touch-6.0.2.3-d2vzw.img of=/dev/block/mmcblk0p18
reboot recovery
(partition 18 is your recovery partition)
That'll push the known good CWM to your recovery partition and boot you into it. It won't mess with any sort of data anywhere else on the phone.
Alright, thanks. I'll give this a try after I get back home from work.
Sent from my SCH-I535 using xda app-developers app
recovery
JoeS8705 said:
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Click to expand...
Click to collapse
COuld you possibly link the file you used to get back to stock? i resently tried to root my device and it won't start.
No problem. Once again, I'm at work. I'll post it when I get home though.
Sent from my SCH-I535 using xda app-developers app

[Q] A complete backup?

My phone has root using MotoChopper but I am still using the stock ROM. I really don't want to go through the effort of custom ROM.
The nice thing about the Galaxy S3 was the Kies software that backed up everything important. Is there something like that for Motorola? I have an SD car installed with plenty of space.
Is there something in the Motorola recovery menu that would allow me to perform a backup, or an app? I have titanium backup installed by the way.
Search for recoveries
As you know TB doesn't do a full backup. But as long as you are rooted there are options open to you other than getting another rom installed to do a full Nandroid Backup. Do a search for "Recoveries". I have preferred CWM http://www.clockworkmod.com/ with my past phones but there are a few more you may want to peruse before flashing one.
The great thing about recoveries is that you can Nandroid backup your current rom before flashing a new one. And if you don't like the new one, or it has issues you don't like, just use the recovery to flash back.
I hope this helps you in some way.
gps4213 said:
As you know TB doesn't do a full backup..
Click to expand...
Click to collapse
I've used CWM with previous Android phones. Yes I liked it. A few follow ups ....
1. If all I care about was retoring apps and their settings to the Stock Moto ROM -- could I trust TB for that purpose?
2. Supposing I had the bootloader unlocked -- could I install CWM and just keep the ROM that I have or would I be forced to install a custom ROM?
strike3 said:
1. If all I care about was restoring apps and their settings to the Stock Moto ROM -- could I trust TB for that purpose?
Click to expand...
Click to collapse
Yes, but if all you want is app backups with the ability to restore (Not data just apps) I prefer appsaver. But if you want data as well then TB is superb.
strike3 said:
2. Supposing I had the bootloader unlocked -- could I install CWM and just keep the ROM that I have or would I be forced to install a custom ROM?
Click to expand...
Click to collapse
Having root and or an unlocked boot loader (As phones used to come with) does not mean you have to use any other rom. I plan on keeping the stock rom on my phone as I like it over the present roms.
Remember, you will never be forced to use any rom. With the unlocked boot loader you can use any you choose including stock.
---Edit---
CWM does not yet have a stock recovery for the XT926, give it time and they will. You did not state your exact phone version but I would guess it is the 925/926.
As I just rooted my self I am also looking for a recovery to do a Nandroid backup.
I did find this thread that has some answers IF your boot loader is unlocked...
http://forum.xda-developers.com/showthread.php?t=1973904
gps4213 said:
Yes, but if all you want is app backups with the ability to restore (Not data just apps) I prefer appsaver. But if you want data as well then TB is superb.
Having root and or an unlocked boot loader (As phones used to come with) does not mean you have to use any other rom. I plan on keeping the stock rom on my phone as I like it over the present roms.
Remember, you will never be forced to use any rom. With the unlocked boot loader you can use any you choose including stock.
---Edit---
CWM does not yet have a stock recovery for the XT926, give it time and they will. You did not state your exact phone version but I would guess it is the 925/926.
As I just rooted my self I am also looking for a recovery to do a Nandroid backup.
I did find this thread that has some answers IF your boot loader is unlocked...
http://forum.xda-developers.com/showthread.php?t=1973904
Click to expand...
Click to collapse
I have the 926. I used the recently posted MotoChopper - April 2013 edition -- from DJR bliss to root. I don't know if that unlocks the bootloader as well. Perhaps someone could clue me in.
strike3 said:
I have the 926. I used the recently posted MotoChopper - April 2013 edition -- from DJR bliss to root. I don't know if that unlocks the bootloader as well. Perhaps someone could clue me in.
Click to expand...
Click to collapse
Nope, that JUST allows root access. To unlock the boot loader you need a tad more. Search this forum for droid razr HD utility by Mattlgroff. It has every thing you need to root (And that can be undone) and unlock the boot loader (THIS CAN NOT be undone). Linky
--FYI--
I do not recommend flashing the 4.1.2, but as I said if you are unlocked you can do what ever you want. Being just rooted (Or even not rooted) you can flash 4.0.4 and 4.1.1, when you flash to 4.1.2 you can NOT go back to 4.0.4 or 4.1.1 with out an unlocked boot loader.
And the droid razr HD utility has the CWM custom recovery included!
Bonus!
Any more questions that I can answer before I go to sleep tonight?
Thanks for everything you did -- you deserve sleep. I already had 4.1.2 when i ran MotoChopper. I don't plan on going back or doing a custom recovery or custom ROM. I know I am not using the droid to its full potential however -- i'm just thankful to end the 2 months of banging my head against a wall. As I mentioned on another thread I bought the iPhone 5 on verizon 4 times and returned it all 4 times. I bought the S3 for Verizon once and returned it. 3 of the iPhones and the S3 had chronic wifi issues. I was beginning to think it was me. It was not. With no other variables in my work flow changing -- the Razr HD had none of these problems. I'm sure the M and the Maxx HD would have been fine also. However, I wanted something slightly better than the M and I would have had a hard time squeezing the Maxx HD with a case into my shirt pockets.
strike3 said:
Thanks for everything you did -- you deserve sleep. I already had 4.1.2 when i ran MotoChopper. I don't plan on going back or doing a custom recovery or custom ROM. I know I am not using the droid to its full potential however -- i'm just thankful to end the 2 months of banging my head against a wall. As I mentioned on another thread I bought the iPhone 5 on verizon 4 times and returned it all 4 times. I bought the S3 for Verizon once and returned it. 3 of the iPhones and the S3 had chronic wifi issues. I was beginning to think it was me. It was not. With no other variables in my work flow changing -- the Razr HD had none of these problems. I'm sure the M and the Maxx HD would have been fine also. However, I wanted something slightly better than the M and I would have had a hard time squeezing the Maxx HD with a case into my shirt pockets.
Click to expand...
Click to collapse
Just install twrp as your recovery and make a full backup that way. unlocked bootloader required.
Yes you can trust tibu for app backup and recovery. I flash several times per week and it's the app I use and trust.
Sent from my XT926 using Tapatalk 2
koftheworld said:
Just install twrp as your recovery and make a full backup that way. unlocked bootloader required.
Yes you can trust tibu for app backup and recovery. I flash several times per week and it's the app I use and trust.
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
Thank you Kofthworld, I will give that a whirl as well. CWM is still my pref until I find better though.
gps4213 said:
Thank you Kofthworld, I will give that a whirl as well. CWM is still my pref until I find better though.
Click to expand...
Click to collapse
I understand where you're coming from. I used to use cmw since the og droid. Twrp has supplanted it fully imo. all of the devs prefer it and it's easy to use. Nonetheless both exist for the xt926. Use this utility for the recovery of your choice.
http://www.droidrzr.com/index.php?/...Ver.3 {UPDATED-4/16/13} More Options Manually
Sent from my XT926 using Tapatalk 2
I think I should have screwed this one up -- and should have done the custom recovery to make a FULL backup. I backed up all my apps using TB. did a complete wipe -- not just a system reset from Settings but -- a motorola AP fastboot style wipe -- with the stock 4.1.2. I re-rooted. Then logged in to Play installed TB.
I think the problem i created occurred when I tried to reinstall system stuff -- not just user apps. I have stock recovery, root at this point. After restarting once i restored those apps and their data I am perpetually stuck on the Droid eye.
strike3 said:
I think I should have screwed this one up -- and should have done the custom recovery to make a FULL backup. I backed up all my apps using TB. did a complete wipe -- not just a system reset from Settings but -- a motorola AP fastboot style wipe -- with the stock 4.1.2. I re-rooted. Then logged in to Play installed TB.
I think the problem i created occurred when I tried to reinstall system stuff -- not just user apps. I have stock recovery, root at this point. After restarting once i restored those apps and their data I am perpetually stuck on the Droid eye.
Click to expand...
Click to collapse
Ok -- I reflashed a stock recovery under AP Fastboot, re-rooted, and then installed TB, doing a 'restore missing apps' - meaning the user installed apps. hopefully ill be ok now.

[Q] Flashing no longer possible: Flash successful but system does not change

Hello!
I can no longer flash anything to my GT-P5110, even factory reset has no effect. The internal storage seems to be read-only.
I think this is a longer story: About one year ago the stock firmware became incredibly slow, to the point that processes started to force close, then my user data was lost, and after factory reset the tablet went into endless boot loop.
So I decided to give CM10 a try and it worked flawlessly. The tablet was fast again. I even could upgrade to CM11 later. But around 2 month ago, only sometimes processes started to force-close or the tablet randomly rebooted itself - mostly during charging. I left it that way in the charger for some days because I had no time to bother with that issue. Then, I tried to factory reset my device only to find out that this has absolutely no effect. Installing app updates: No effect. Changing system settings: No effect. And apps start to force-close at an insane rate short after boot. The device is unusable. My could only shut down and reboot into recovery. I left the tablet lying around, turned off, out of charger, for 2 months. Now I tried to investigate:
When I "adb shell" into recovery and call dmesg, I see lots of these lines:
Code:
mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
I think something is really broken with the internal storage. I tried to flash a newer recovery but it has no effect, even when done from download mode.
Factory reset sometimes fails with an error. Reinstalling CM fails with an error. Wiping cache seemingly succeeds but I'm sure it has no effect. I tried installing SlimRom instead which seemingly succeeds, too - but after reboot I'm greeted with the CM boot logo again.
I tried to flash stock firmware with Odin. It is very very slow, runs for about 15 minutes, then fails at around 50%. Of course: That "half flashed firmware" does in no way affect the device: It still boots CM11 "without problems", then a few seconds after finishing boot (showing home screen), force-closes start to pop-up.
What should I do? I suppose the device is out of warranty for a few weeks or months, now. And even when not: It has been flashed with CM, the triangle counter is not zero. I suppose that combination of problems (read-only/failing storage, non-stock firmware) voids warranty in a way that Samsung will deny any repair. If at least I could return the device to stock firmware things would be different maybe.
Any ideas what I could try? Is it possible that the internal storage is simply fried? fsck'ing the partitions shows no errors, just the data partition is unclean with unwritten journal data but all data is readable. So the internal storage has probably not died. It just sticks to read-only mode for whatever reason.
I've found some posts with similar problems but those seem to be about older Galaxy Tab 1 devices built 2011 or before.
Just reading over this and it sounds very similar to what I'm currently facing, which is doubly annoying as no one else has chipped in a solution
I had reboot issues with my Tab2 10.1 (GT-P5110) on stock so after realizing I'd need to factory reset bite the bullet and rooted so I could use CM10.
Had occasional reboots but nothing I couldn't live with however from yesterday evening the tablet is seemingly stuck in a boot loop. It comes on, some apps fire up and an update starts. Sometimes apps force close then BOOM I get the boot splash screen.
I've tried factory reset in recovery (CWM 6.0.2.7) to no avail and wiping just about everything which also had no noticeable effect as all my settings and the rom are still the same when I get back in (albeit briefly!).
I've tried flashing new recovery via ODIN which reported a success however that also didn't appear to take. I'm beginning to think it some serious file system or storage corruption ;(
Same problem here...
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.
bigg fella said:
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.
Click to expand...
Click to collapse
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).
hurikhan77 said:
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).
Click to expand...
Click to collapse
exactly, can't even uninstall an app. It's as if it boots from a permanent back up because even deleting pictures or files isn't permanently successful. You can uninstall and delete to your hearts content, get false hope, and get crushed after it reboots and everything is unchanged
Not looking very optimistic for this I was getting a similar inkling that it's gone into a permanent RO mode as not even the wipes from recovery have an effect. I'd also tried un-installing apps as I noticed one updating and thought it was crashing it however even when it did fire up and I disabled WLAN to stop Play Store auto-updating and removed the app on the next reboot cycle the app was back:crying::crying:
I fear I may have a big white paperweight....
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Would this method be any different to the way it attempts to reformat the internal partitions when you select to format the various mounts from CWM? If so I'm more then willing to give it a go as I really have nothing to lose as the damn thing is useless atm!
shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Good call......Smart move?
help!!
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?
PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app
im also having this issue with my galaxy tab2 7".. help is badly needed
Well, the proposed fix I had didn't help. Was worth a shot...
Sent from my Nexus 4 using XDA Premium HD app
hope someone finds a solution for this.
No Access to ADB
shakatu said:
PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Hi Shakatu,thanks for the PM, however, my device in ADB is unauthorised, so wont let me get into shell. Is there a way around this please?
sunnytimes said:
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?
Click to expand...
Click to collapse
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread
same problem please help me... :crying:
seagman said:
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread
Click to expand...
Click to collapse
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..
sunnytimes said:
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..
Click to expand...
Click to collapse
same here too, i have same issue.. unable to flash or do anything to my phone....
Probably this is the end for our tab. As off now the tab is useless.
Sent from my GT-N7000 using XDA Free mobile app

[Q] Recovery Disappears After Reboot

Hello!
Im not really new to rooting and custom roms. Had the Nexus 4 until about a year ago, so been away from Android for about a year! Got the Nexus 5 a couple weeks ago, but been too busy to get around to doing anything with it. So, well, now its time! Ive unlocked the bootloader, and installed ClockworkMod Recovery (Only cuz thats what I used to use, and I like it! The installation goes fine, and the recovery works fine! So, I restart my phone so I can see if the phone is working fine before I install a rom. Everythings fine! So, I resart and go into recovery and that's where the problem is! When I go into recovery, it shows a picture of a Android under service. Well, I did some research, and from what I can tell it looks like there is no custom recovery on the phone. I repeated this a couple times, same problem! can anyone help me out? Someone here mustve faced this problem too... or maybe Im just screwing up somewhere and I dont realize it.
-AGZ
It happens with stock lollipop and maybe some aosp ones too. Flash latest SuperSU from recovery or delete recovery-from-boot.p (I think in system folder)
Sent from my Nexus 5 using XDA Free mobile app
AGZ98 said:
Hello!
Im not really new to rooting and custom roms. Had the Nexus 4 until about a year ago, so been away from Android for about a year! Got the Nexus 5 a couple weeks ago, but been too busy to get around to doing anything with it. So, well, now its time! Ive unlocked the bootloader, and installed ClockworkMod Recovery (Only cuz thats what I used to use, and I like it! The installation goes fine, and the recovery works fine! So, I restart my phone so I can see if the phone is working fine before I install a rom. Everythings fine! So, I resart and go into recovery and that's where the problem is! When I go into recovery, it shows a picture of a Android under service. Well, I did some research, and from what I can tell it looks like there is no custom recovery on the phone. I repeated this a couple times, same problem! can anyone help me out? Someone here mustve faced this problem too... or maybe Im just screwing up somewhere and I dont realize it.
-AGZ
Click to expand...
Click to collapse
Fastboot boot cwmrecovery.img
Flash supersu in recovery
Then
Fastboot flash recovery cwmrecovery.img
Btw, I recommend you use twrp
Sent from my Nexus 9 using XDA Free mobile app
+1 for TWRP, CWM is practically ancient.
Live boot TWRP, flash SuperSU, then use Flashify (root) to install TWRP.
bm19981217 said:
delete recovery-from-boot.p (I think in system folder)
Click to expand...
Click to collapse
This. This is the key for maintaining your custom recovery after a reboot.
a maguro wrote this.

[Q] Having trouble with "RECOVERY IS NOT SEANDROID ENFORCING" message

Alright, I'm at my wit's end and I've searched the web far and wide. Tonight I thought I'd root, recover and MOD my S5 (have done so before with the S3 and Epic many times).
Ran into a series of problems, but here is where I'm at presently:
I got Philz touch recovery working fine. I used it to install [MOAR][NE5] v2.2 / The Next Level / Wicked Sick / Endless Customization which noted a couple errors (didn't say which) but overall seemed to call the installation a success.
Then I go to restart and I get the Samsung S5 splash, followed by dark screen and reset vibration, the following message:
(blue) RECOVERY BOOTING
(red) RECOVERY IS NOT SEANDROID ENFORCING
(yellow) SET WARRANTY BIT: recovery
which then kicks me back to Philz touch.
Any idea what I can do? I'm glad I can at least get to recovery (and download mode). Hopefully at worst putting stock on the SD and installing that from Philz would solve the problem... but I'm a little pessimistic since the ROM I just installed doesn't seem to work. Thanks for any help, I really appreciate it.
put the stock rom this why i dont mess with my 599.99 phone
You can always Odin back on stock and start over, or flash a different rom.
sersdf said:
Alright, I'm at my wit's end and I've searched the web far and wide. Tonight I thought I'd root, recover and MOD my S5 (have done so before with the S3 and Epic many times).
Ran into a series of problems, but here is where I'm at presently:
I got Philz touch recovery working fine. I used it to install [MOAR][NE5] v2.2 / The Next Level / Wicked Sick / Endless Customization which noted a couple errors (didn't say which) but overall seemed to call the installation a success.
Then I go to restart and I get the Samsung S5 splash, followed by dark screen and reset vibration, the following message:
(blue) RECOVERY BOOTING
(red) RECOVERY IS NOT SEANDROID ENFORCING
(yellow) SET WARRANTY BIT: recovery
which then kicks me back to Philz touch.
Any idea what I can do? I'm glad I can at least get to recovery (and download mode). Hopefully at worst putting stock on the SD and installing that from Philz would solve the problem... but I'm a little pessimistic since the ROM I just installed doesn't seem to work. Thanks for any help, I really appreciate it.
Click to expand...
Click to collapse
I have heard that philz doesn't work right with all base bands and ROMs, that may just be hearsay. Did you do a full wipe before you flashed the ROM?
Sent from my SM-G900P using XDA Free mobile app
Yea, TWRP has been the most reliable for me, not for everyone though and vice versa.
emanuelrv said:
put the stock rom this why i dont mess with my 599.99 phone
Click to expand...
Click to collapse
Fair enough. I actually was happy with just root to remove the bloat but I think I deleted something critically by accident while removing Sprintzone crap.
metalfan78 said:
You can always Odin back on stock and start over, or flash a different rom.
Click to expand...
Click to collapse
Alright, I might try a different recovery (TWRP) first, but if that doesn't work you're right. Thanks.
metalfan78 said:
Yea, TWRP has been the most reliable for me, not for everyone though and vice versa.
Click to expand...
Click to collapse
Yeah, no luck there either (can get into TWRP and flash the ROM but same boot problem). Got a bad feeling I'm bricked, but will try to flash stock through Odin :-/ Thanks
If you can get into recovery or download mode you are not bricked. Odin is your best bet.
What firmware was your phone running? It is possible you don't have the correct firmware installed for the ROM. You could also try reflashing the ROM. Don't worry about the warning you are getting, that shows up because your recovery is not stock.
Sent from my SM-G900P using XDA Free mobile app
drteeths said:
What firmware was your phone running? It is possible you don't have the correct firmware installed for the ROM. You could also try reflashing the ROM. Don't worry about the warning you are getting, that shows up because your recovery is not stock.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
NE5. Hmm, that makes sense, perhaps that was the problem. Ultimately, I Odin-ed to NK4 which solved matters (well, unbricked anyways).
Well good news for you is that MOAR 5.0 has been released.
Sent from my SM-G900P using XDA Free mobile app

Categories

Resources