Database Info

lost CWM, now CWM 3.0.0.8 is broke?

so, last night my phone was acting wierd... slow, battery was getting destroyed literally in an hour or two so i cleaned it up..
somehow i lost clockwork recovery... no flippin idea what happened, i never flashed or installed anything, but i went to do a backup and all i got was samsung recovery.
i did not lose root...
tried to install via rom manager and it said it worked... yeah whatever, that program is rubbish and ALWAYS says it worked...
anyways rebooted to a black screen but the capacitive buttons would light up if i touched them.
finally it installed but nothing worked and the phone locked up.
by the way rom manager installed CWM 3.0.0.8 (orange)
so now i had to completely blow out the phone, reroot, reinstall CWM (which worked the first time) but nothing is working in clockwork again.
back up.. nope says error backing up.. thats it
restore... nope, something about only having 8gb of space on my SDcard
i can wipe cache,, or so it seems.
but
if i wipe dalvik it locks the phone and i completely lose CWM again.
its acting like CWM is only temporary or something.
so what the heck.. i have never seen this before... ever.

I cant do anything with regards to bqcking up or restoring.
I cant.flash anything either even though rom manager boots to a portion of cwm which tries to flash a eom. But the phone just reboots.
Sent from my SCH-I500 using Tapatalk

Can't lie - Karma's a *****

Try going back to stock and starting over.

foxfire450 said:
Try going back to stock and starting over.
Click to expand...
Click to collapse
please be sure you read my post in its entirety and not bits and pieces.
i did finally get the latest CM7 installed and its running ok.
havent tried to do other things in CWM yet

akellar said:
Can't lie - Karma's a *****
Click to expand...
Click to collapse
you aint kidding...
but
its a phone, my life doesnt end if my phone goes to hell
just wierd, i have never lost clockwork before.

v_lestat said:
please be sure you read my post in its entirety and not bits and pieces.
Click to expand...
Click to collapse
In fairness, it's not immediately clear what you did after getting CWM Orange 3 installed---and really, ROM Manager should only ever be used on our phones if you're using the latest (CWM 4) on an MTD ROM.
That said: IF you think you need to do this (it sounds like if you got CM7 installed, you don't, but offering the advice all the same): take foxfire450's advice. Then do the entire process all over again. I've heard of people having issues with a lagfux or MTD removal unless they did the process twice. You might even consider the RFS Formatter if you're still having trouble.
Again though, that's all largely academic if you're running fine now. *shrug* Up to you to try if you think it's worth bothering at this point.

Flashing error!!!

I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network

pitmanr2003 said:
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
Click to expand...
Click to collapse
where did you get cm10 for the vzw phone? I thought it was for all of the other phones but vzw? Try going back to stock non root. try flashing the modems in the thread about this one.

phillyphill39 said:
where did you get cm10 for the vzw phone? I thought it was for all of the other phones but vzw? Try going back to stock non root. try flashing the modems in the thread about this one.
Click to expand...
Click to collapse
if you go to goo app its in his folders of roms i beleive. i have tried that. i switched to my wifes sim card and got same results, so must be something on the phone

pitmanr2003 said:
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
Click to expand...
Click to collapse
Flash the stock tar.md5 from here: http://samsung-updates.com/device/?id=scH-i535
Whatever you flashed put a custom kernel on there, and that's why you get that message.

pitmanr2003 said:
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
Click to expand...
Click to collapse
I don't mean to be rude, but development is not for questions

timothydonohue said:
I don't mean to be rude, but development is not for questions
Click to expand...
Click to collapse
no offense taken, but with only one question and answer section and that for all cell services could make this question a little different

pitmanr2003 said:
no offense taken, but with only one question and answer section and that for all cell services could make this question a little different
Click to expand...
Click to collapse
I have d2hackers cm10 up and running on my device...click link in sig!

i have tried new modem and fully stock rom. no luck. I was running dual boot before that if that could of caused issue. I am lost now.

pitmanr2003 said:
i have tried new modem and fully stock rom. no luck. I was running dual boot before that if that could of caused issue. I am lost now.
Click to expand...
Click to collapse
I am lost. i have tried everything and i am now where a beginner when it comes to android. Im afraid that if i take it back they will see it has been rooted.

pitmanr2003 said:
I am lost. i have tried everything and i am now where a beginner when it comes to android. Im afraid that if i take it back they will see it has been rooted.
Click to expand...
Click to collapse
wipe data then odin a factory stock image

droidstyle said:
wipe data then odin a factory stock image
Click to expand...
Click to collapse
tried that still wants to roam.

pitmanr2003 said:
tried that still wants to roam.
Click to expand...
Click to collapse
I have tried to odin stock and then wipe. still showing no data connection, and same thing when I put my wifes sim in. IM thinkiing it has something to do with the dual boot i had set up before. is there a way to repartion the internal sd card or emmc?

This seems to be happening to a lot of people flashing AOSP ROMs....this is why they warn you they are not responsible for what happens to your phone...especially with Betas.
There are many threads on this and several on how to get a workaround until someone figures out how to fix this.
Try doing a search on losing IMEI or roaming after flashing CM10...it is happening a lot...that is why I am just using rooted stock with VZW apps and TW frozen.

this problem I was having with no data or radio in CM10.
I used ODIN to go back to stock rooted (root 66).
When I did that I was boot looping in the puking rainbows 4GLTE boot animation.
I eventually figured out how to fix that by booting into recovery (press volume up, home button, and power button at the same time till phone boots). I then did a wipe data/factory reset.
My phone then booted fine into stock root.
I then proceeded to punch in *2767*3855# into my dialer immediately when I got stock root working. That did some sort of a factory reset / format. It all happened so quick I could barely read what it told me. The phone rebooted after a while.
I then downloaded EZ-Recovery for VZW Galaxy S3 app from the Play store.
I installed the custom recovery from Dhacker's CM10 post over on the droidhive forums using EZ recovery.
I also downloaded the CM10 file to flash and the Jelly Bean Google Apps file.
Rebooted into recovery, Wiped data/cache/dalvik.
Installed the CM10 file.
Installed the Jelly Bean apps.
Reboot.
Profit.
I now have a largely functional CM10 (as far as I can tell there are some camera issues). Data 3G/4G is working, so are calls and text and everything is dandy.

Did the *27 bla bla thing posted above and back to normal. Thanks everyone
Sent from my SCH-I535 using XDA App

[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] Bricked xt925 - read-only eMMC ?

Hello,
Since yesterday my phone is crashing about 20-30 seconds after properly booting. I can unlock the phone with my lockscreen pattern, I land on my homescreen but process like Google Play Services goes like "x has stopped working".
On CWM I've erased /system and /data and then reflash a rom (Slimkat or CM), Erasing and flashing process on CWM seems to work as planned but when the phone reboot it's still on Slimkat with all my datas, like if nothing have been done in CWM.
So I've rebooted on the bootloader and tried a "fastboot -w", again the process seems to be ok on my pc but when the phone reboot it is still on this f**ked rom with all my datas, like if fastboot have done nothing.
I've tried to flash an up-to-date CWM, same thing again.
I think the eMMC chip are deeply corrupted, they say any writing on it is ok but in fact they are read-only, which may explain why all the process are crashing after the boot and why flashing seams ok but are useless.
What do you think XDA, andy idea about my problem ? Do you think it's an Hardware issue or what can I do to solve it ?

Why not flashing a stock firmware to go back to STOCK?

joel_sinbad said:
Why not flashing a stock firmware to go back to STOCK?
Click to expand...
Click to collapse
I've tried it with RSDLite but same thing again, everyhing seams ok in RSDLite, the 22 blocks are writed but at the reboot it's still the same Slimkat with my datas.

Ezekiel3 said:
I've tried it with RSDLite but same thing again, everyhing seams ok in RSDLite, the 22 blocks are writed but at the reboot it's still the same Slimkat with my datas.
Click to expand...
Click to collapse
if infact it has gone read only as has happened to some other users, there is no known fix. all known angles have been explored, even with input from a developer.
if you find a fix, post it, it may help others.
most likely, you will need a new phone.

I agree with bwen diord...aint never see anyone recover from that, least not yet.

cmh714 said:
I agree with bwen diord...aint never see anyone recover from that, least not yet.
Click to expand...
Click to collapse
I've just see it's possible to boot from the SD card in that case but I'm to lazy to try it.
Goodbye little RAZR HD, we have covered a lot of mileage together, it's time to leave. :angel:
Anyway thanks for the help XDA

Cyanogenmod 12.1 Upgrade from Slimkat 4.4.4 - Bootloop after optimization

So I've been trying to go from Slimkat (Slim-4.4.4.build.7.0-Official-5979) to Cyanogenmod 12.1 (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw) for a few weeks now. I've tried like 4 different guides, which were all pretty similar, but every time I get to the same point. I'm able to get to my recovery (CWM), clear all my cache, etc, install CM12.1 and Gapp5.11, reboot, it optimizes all my apps, finishes the boot, and then goes into what seems like a boot loop. I've let it sit there and reboot for like 5-10 minutes before and it just keeps rebooting. I even redid the flashing of the aboot and bootloader as shown in the official CM install guide to get the recovery on there and also tried the latest TWRP recovery with the same results. Also, once it enters this bootloop, from the time I turn it on, it shows the Samsung logo with the blue Android man below it, then goes to the screen with the pulsing Android head, it vibrates then goes do a dark screen with a blue pulsing indicator light and then starts the sequence over after a few seconds.
I tried to remove my MicroSD card and boot without that with no success. Is it possible I need to format my internal storage as well? The guides usually don't mention what you're coming from, so I have no idea what starting point they expect me to be at.
Files used:
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw
gapps-511-base-20151205-1-signed
I did NOT use the below CM Recovery, however. I was afraid to do that and lose my ability to recover my old image.
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw-recovery
I'm able to recover back to my original ROM, but any help to upgrade is greatly appreciated. I'm tired of messing with this....

hypercoyote said:
So I've been trying to go from Slimkat (Slim-4.4.4.build.7.0-Official-5979) to Cyanogenmod 12.1 (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw) for a few weeks now. I've tried like 4 different guides, which were all pretty similar, but every time I get to the same point. I'm able to get to my recovery (CWM), clear all my cache, etc, install CM12.1 and Gapp5.11, reboot, it optimizes all my apps, finishes the boot, and then goes into what seems like a boot loop. I've let it sit there and reboot for like 5-10 minutes before and it just keeps rebooting. I even redid the flashing of the aboot and bootloader as shown in the official CM install guide to get the recovery on there and also tried the latest TWRP recovery with the same results. Also, once it enters this bootloop, from the time I turn it on, it shows the Samsung logo with the blue Android man below it, then goes to the screen with the pulsing Android head, it vibrates then goes do a dark screen with a blue pulsing indicator light and then starts the sequence over after a few seconds.
I tried to remove my MicroSD card and boot without that with no success. Is it possible I need to format my internal storage as well? The guides usually don't mention what you're coming from, so I have no idea what starting point they expect me to be at.
Files used:
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw
gapps-511-base-20151205-1-signed
I did NOT use the below CM Recovery, however. I was afraid to do that and lose my ability to recover my old image.
cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2vzw-recovery
I'm able to recover back to my original ROM, but any help to upgrade is greatly appreciated. I'm tired of messing with this....
Click to expand...
Click to collapse
I'd suggest maybe switching your recovery. I'm also running the same version of slimkat on my old S3.
Nexus 6 via SSHD/Cataclysm

ShapesBlue said:
I'd suggest maybe switching your recovery. I'm also running the same version of slimkat on my old S3.
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
yea, I tried using Clockwork Mod recovery as well. CM12.1 includes a recovery as well, but I'm hesitant to use it....
Also, how did you patch the Stagefright exploit on that?

hypercoyote said:
yea, I tried using Clockwork Mod recovery as well. CM12.1 includes a recovery as well, but I'm hesitant to use it....
Also, how did you patch the Stagefright exploit on that?
Click to expand...
Click to collapse
I mean change the recovery to something else like twrp. Honestly I didn't. I personally think the stagefright exploit wasn't anything to worry about
Nexus 6 via SSHD/Cataclysm

ShapesBlue said:
I mean change the recovery to something else like twrp. Honestly I didn't. I personally think the stagefright exploit wasn't anything to worry about
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
Yea, you might've missed that part or I worded it weird, but I tried both TWRP and ClockworkMod and they both produced the same result.

hypercoyote said:
Yea, you might've missed that part or I worded it weird, but I tried both TWRP and ClockworkMod and they both produced the same result.
Click to expand...
Click to collapse
That's weird. I've been using twrp on nearly all my devices and the only issue I've ever had is to update it
Nexus 6 via SSHD/Cataclysm

ShapesBlue said:
That's weird. I've been using twrp on nearly all my devices and the only issue I've ever had is to update it
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
Well, I don't think it's a recovery issue. My guess is it's got something to do with the Bootloader, some files on my phone. I really don't know. Doing the whole custom ROM thing isn't really that hard or complicated once you know what you're doing, but I've run out of things to check on. I don't recall doing anything odd before when I upgraded to Slimkat, but even if I did, it should've been undone in the install process of CM12.1.

hypercoyote said:
Well, I don't think it's a recovery issue. My guess is it's got something to do with the Bootloader, some files on my phone. I really don't know. Doing the whole custom ROM thing isn't really that hard or complicated once you know what you're doing, but I've run out of things to check on. I don't recall doing anything odd before when I upgraded to Slimkat, but even if I did, it should've been undone in the install process of CM12.1.
Click to expand...
Click to collapse
Very possible. I wish I knew what to do or how to help with this issue
Nexus 6 via SSHD/Cataclysm

ShapesBlue said:
Very possible. I wish I knew what to do or how to help with this issue
Nexus 6 via SSHD/Cataclysm
Click to expand...
Click to collapse
Me too! lol

Hehehe