[Q] Having trouble with "RECOVERY IS NOT SEANDROID ENFORCING" message - Sprint Galaxy S 5 Q&A, Help & Troubleshooting

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

Related

[Q] Skyrocket will boot into recovery and download but hang when booting all ROMS

The Phone was working fine. When it stopped sending emails, i rebooted and it showed the "samsung" boot screen, then the screen turns black and there is nothing. Sometimes, it will boot into ROM after sitting there for 30 minutes. It is SGII skyrocket running CM 10.2 with TWRP. Tried flashing stock rom and various backups and roms. A few days earlier I had flashed a rom to experiment but ended up reverting back using a backup. I am able to get into download and recovery mode. Is it possible I corrupted something and what do I need to do to get it to boot correctly? Thanks.
zjsdlr2 said:
The Phone was working fine. When it stopped sending emails, i rebooted and it showed the "samsung" boot screen, then the screen turns black and there is nothing. Sometimes, it will boot into ROM after sitting there for 30 minutes. It is SGII skyrocket running CM 10.2 with TWRP. Tried flashing stock rom and various backups and roms. A few days earlier I had flashed a rom to experiment but ended up reverting back using a backup. I am able to get into download and recovery mode. Is it possible I corrupted something and what do I need to do to get it to boot correctly? Thanks.
Click to expand...
Click to collapse
Flash the proper recovery, then wipe and flash the Rom again. I'm not going to help you past that, since I've already explained this exact problem last week.
Sent from my Nexus 7 using Tapatalk 4
I was given the advice to use odin and flash a stock recovery. Havent tried it yet, but its on my list. That and finishing the christmas tree. My problem was similar and phone would randomly kernal lock during boot.
Sent from my GT-N5110 using xda app-developers app
rpr69 said:
Flash the proper recovery, then wipe and flash the Rom again. I'm not going to help you past that, since I've already explained this exact problem last week.
Click to expand...
Click to collapse
Thats not helpful. What is "the proper recover?" TWRP has been working for months. Not even a link to where you explained the solution? I searched the forum before I posted and I didnt see it. I flashed the stock with odin before posting and it did the same thing.
zjsdlr2 said:
Thats not helpful. What is "the proper recover?" TWRP has been working for months. Not even a link to where you explained the solution? I searched the forum before I posted and I didnt see it. I flashed the stock with odin before posting and it did the same thing.
Click to expand...
Click to collapse
Then get a new phone
Sent from my HTC One using Tapatalk
zjsdlr2 said:
Thats not helpful. What is "the proper recover?" TWRP has been working for months. Not even a link to where you explained the solution? I searched the forum before I posted and I didnt see it. I flashed the stock with odin before posting and it did the same thing.
Click to expand...
Click to collapse
Search 'black screen boot' in this forum and you will find dozens of threads describing the exact same problem. Read some of them.
zjsdlr2,
read ALL of this thread first http://forum.xda-developers.com/showthread.php?t=1773659
You have many options for ROMs so YOU need to decide what you want to use.

[Q] Buying the phone today and rooting?

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.

[Q] random shutdown and bootloop

Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
arsenaljordan said:
Hello First post here so hopefully in the right place! I've got a nexus 5, UK model purchased around January time. I had rooted, running stock with SuperSU installed and a few apps installed with xposed mod.
It was running perfectly fine, until a few days back where I was required to reboot, it then got stuck at the Google screen and wouldn't go past that, I turned the phone off for a while and eventually could get into it.. Great, until it happened again.. I spoke to a friend who said perhaps it was the xposed which was causing it, so I flashed back to factory, ran it for a while and it was fine, so went back to root and tested it, was stable so I reinstalled xposed.. It then got stuck in the bootloop again, so flashed to factory certain that it was xposed causing issues. I'm now running factory, however the phone will still get stuck in bootloop but will also randomly reboot itself now.. Has anyone experienced this? After scanning the forums I can't find anything so hopefully someone can help!! My boot loader is still unlocked.
Thank you, Jordan.
Click to expand...
Click to collapse
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
GUGUITOMTG4 said:
Are you able to flash a custom recovery? like TWRP, PHILZ, CWM? try it.
if successful, flash a custom Rom. just to discard the possibility of emmc failure.
Click to expand...
Click to collapse
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
arsenaljordan said:
I am able to flash a custom recovery and so forth, so wouldn't think it to be emmc failure.
Click to expand...
Click to collapse
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
GUGUITOMTG4 said:
It doesn't really exonerates emmc from being bad yet. now, wipe and flash a Rom, a stock/aosp based one
Click to expand...
Click to collapse
I have already flashed the stock recovery and ROM back to the device

[Q] Help, I deleted my stock rom by accident

This is my first post and I'm not sure where to put it but I hope this is right.
I'm kinda new to flashing ROMs and was trying to flash one using safestrap on my GS3. I couldn't find one that worked and went back to my stock ROM. In the stock ROM cell service completely died and wouldn't work, to combat this problem I removed all ROMs, ROM slots, and wiped the stock ROM cache. Nothing. So then I restored to my nandroid backup I made yesterday and that deleted my OS. Now when I boot it just gets stuck at the second Samsung boot logo (there the first one that just says "Samsung" and "unlocked", then the second on says "Galaxy SIII" or something) now I have no OS and I'm not sure how to fix this, can I get some help please?
Okay, I got the stock firmware installed but I still have no service anywhere. Any ideas?
apcake said:
This is my first post and I'm not sure where to put it but I hope this is right.
I'm kinda new to flashing ROMs and was trying to flash one using safestrap on my GS3. I couldn't find one that worked and went back to my stock ROM. In the stock ROM cell service completely died and wouldn't work, to combat this problem I removed all ROMs, ROM slots, and wiped the stock ROM cache. Nothing. So then I restored to my nandroid backup I made yesterday and that deleted my OS. Now when I boot it just gets stuck at the second Samsung boot logo (there the first one that just says "Samsung" and "unlocked", then the second on says "Galaxy SIII" or something) now I have no OS and I'm not sure how to fix this, can I get some help please?
Okay, I got the stock firmware installed but I still have no service anywhere. Any ideas?
Click to expand...
Click to collapse
Uhhhmmmm would flashing the modems help? (directed towards the more knowledged users)
Sent from my SCH-I535 using XDA Free mobile app
poppers162 said:
Uhhhmmmm would flashing the modems help? (directed towards the more knowledged users)
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
It might. It depends on what modem they are currently on
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
apcake said:
This is my first post and I'm not sure where to put it but I hope this is right.
I'm kinda new to flashing ROMs and was trying to flash one using safestrap on my GS3. I couldn't find one that worked and went back to my stock ROM. In the stock ROM cell service completely died and wouldn't work, to combat this problem I removed all ROMs, ROM slots, and wiped the stock ROM cache. Nothing. So then I restored to my nandroid backup I made yesterday and that deleted my OS. Now when I boot it just gets stuck at the second Samsung boot logo (there the first one that just says "Samsung" and "unlocked", then the second on says "Galaxy SIII" or something) now I have no OS and I'm not sure how to fix this, can I get some help please?
Okay, I got the stock firmware installed but I still have no service anywhere. Any ideas?
Click to expand...
Click to collapse
First thing I would do is make sure your imei is still present in the about phone section. If it is, move on to the next step.
I would go completely back to stock, Odin flash either the stock 4.3 or 4.4 image depending on which you were on. If you're unsure, post what it says in download mode.
If you do that and you still have no service, then go to verizon and get a new sim card. Flashing a new modem wouldn't fix this situation.
BadUsername said:
First thing I would do is make sure your imei is still present in the about phone section. If it is, move on to the next step.
I would go completely back to stock, Odin flash either the stock 4.3 or 4.4 image depending on which you were on. If you're unsure, post what it says in download mode.
If you do that and you still have no service, then go to verizon and get a new sim card. Flashing a new modem wouldn't fix this situation.
Click to expand...
Click to collapse
it appears as though the sim was wiped
apcake said:
it appears as though the sim was wiped
Click to expand...
Click to collapse
Grab a new sim card.

[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

Categories

Resources