Is anybody having problems getting clockwordmod to work. After I flashed it, it loads, but none of the options take me anywhere. All the options on the recovery take me to a black screen with a hat. Let me know if you've gotten clockmod recover to work, and how you did it? Thanks
i am stuck too, cannot get out of black screen with hat
Not sure which version you're using. But the one on the development section had issues.
Sent from my EVO using XDA
shook187 said:
Not sure which version you're using. But the one on the development section had issues.
Sent from my EVO using XDA
Click to expand...
Click to collapse
I simply downloaded rom manager and told it to flash clockworkmod. So I'm not sure why I'm experiencing this problem. I even re-flashed it several times.
Use the Camera Button!!
mark22179 said:
Use the Camera Button!!
Click to expand...
Click to collapse
Lmao, took me five minutes to figure thus out. Now I don't feel so dumb
Sent from my ltEVO using Tapatalk 2
last i heared CWM was still broken. make sure it has been fixed before you use it. it would corrupt the /misc partition and it takes a few steps to get it fixed when you flash out of CWM into TWRP
Spyderekz said:
last i heared CWM was still broken. make sure it has been fixed before you use it. it would corrupt the /misc partition and it takes a few steps to get it fixed when you flash out of CWM into TWRP
Click to expand...
Click to collapse
Sorry I never came back to the thread, but I believe you are correct. I don't believe CWM works on the EVO LTE yet of what I've heard. As a result I'm just using TWRP which works great.
if you guys get stuck in clockwordmod, simply go to the main menu of it but hitting power button, then HOLD power button... capac lights will blink a couple times, and the device will reboot.
had this same issue.
also, use twrp for now. instruction to flashing it via terminal emulator is on their site! very useful and straight forward method! good luck
Use TWRP and for gods sake done use ROM manager.
Learn how to do things in recovery. Its painfully easy and work 100% of the time. Unlike ROM Manager.
Rom Manager cant save you when it causes a problem and the phone bootloops.
You can also install it via the goo inside app
sent from my EVO LTE
all you guys that are trying to use clockwork are not doing enough research or something because i have seen it over and over a thousand times that its not working for this phone. you have to use TWRP!!! dont ya think something is wrong when everyone thats trying to use it is having problems? lol
I've been running CM as my recovery for a couple weeks now. Sometimes in ClockworkMod, repeated use of the volume up/down buttons can trigger a 'back button disabled' message. When this happens, it becomes unable to select any of the menu options, leaving you with just the logo until you hit power again. For the CM version on the LTEvo, for some reason, the 'back button disabled' mode is the default starting point.
To overcome this, simply repeatedly press volume up &/or down in rapid succession; it usually takes me less than 10 seconds of pressing them. You will know that it worked when you see a message at the bottom stating 'back button enabled'. At this time, you can navigate and select menu items as normal.
Its still not 100% functional as a recovery, however, as USB storage does not work yet.
I've also been using ROM Manager to facilitate my back ups and restores with no problem.
So why would you use a non functional recovery over one that works 100%
Rxpert said:
So why would you use a non functional recovery over one that works 100%
Click to expand...
Click to collapse
For me, its just a matter of personal preference. TWRP is cool, and I used it initially when brought my LTEvo home and rooted it. However, I've used CM since my OG Evo, and I like it. Its simple, fast, and does what I need (except for the storage part, but then I only use that when I forget something).
geniustheanimal said:
I've used CM since my OG Evo, and I like it.
Click to expand...
Click to collapse
Strike 2
I understand that you want choice, but recoveries are probably the most important part of the phone for a rooted user.
Rxpert said:
Strike 2
I understand that you want choice, but recoveries are probably the most important part of the phone for a rooted user.
Click to expand...
Click to collapse
I don't disagree with you here. Nevertheless, I've been able to use CM for all the essentials I've required of it (namely wiping, flashing, backup, & restore) with zero issue. I may revert back to TWRP for the USB mounting, as it saves me restoring, loading, adding something, and then re-wiping again if I forget something when flashing, but I have no qualms hanging with CM for the time being.
Sent from my EVO using xda app-developers app
geniustheanimal said:
For me, its just a matter of personal preference. TWRP is cool, and I used it initially when brought my LTEvo home and rooted it. However, I've used CM since my OG Evo, and I like it. Its simple, fast, and does what I need (except for the storage part, but then I only use that when I forget something).
Click to expand...
Click to collapse
Yeah, I've been using CM for the same reason, I already know it and trust it. But I already switched to TWRP, and I figured it all out now, so it works.
Not trying to troll or anything, but the majority is correct. Clockwork is down and there is no telling when it will get fixed to work with our Evos. TWRP has been around for quite some time now and is trusted, so why not just stick with what's working? Especially when it comes to the important functionality like recovery.
XDA Premium
TWRP is superior: you can queue up files to flash. Plus, its touch interface is about a million times better than CWM's.
I recommend switching. If you're familiar with CWM, you might be wary (I was at first too), but you'll never look back.
Related
Hey all,
Just a couple days ago, my track ball stopped working when I use it to scroll down. In recovery, you need to be able to scroll down to do anything. Is there a way to flash things and do nands without the track ball? I know there is Clockwork, but I don't trust it with the stories of bricking. If anything, all I need to do is be able to flash the flashback ROM so I can send it in and get a new phone.
Any remedies?
Thanks
Have a read here.
chris22_2 said:
Hey all,
Just a couple days ago, my track ball stopped working when I use it to scroll down. In recovery, you need to be able to scroll down to do anything. Is there a way to flash things and do nands without the track ball? I know there is Clockwork, but I don't trust it with the stories of bricking. If anything, all I need to do is be able to flash the flashback ROM so I can send it in and get a new phone.
Any remedies?
Thanks
Click to expand...
Click to collapse
It happened to me. I was trying to flashback to send it back...no trackball. I found that pushing on the phone with my thumb above the trackball enabled the trackball enough to flash the zip. Keep in mind I was sending the phone back to Verizon for the broken trackball, though, so I wasn't worried about breaking it further.
Chevelle1768 said:
Have a read here.
Click to expand...
Click to collapse
DoubleByte said:
It happened to me. I was trying to flashback to send it back...no trackball. I found that pushing on the phone with my thumb above the trackball enabled the trackball enough to flash the zip. Keep in mind I was sending the phone back to Verizon for the broken trackball, though, so I wasn't worried about breaking it further.
Click to expand...
Click to collapse
Thank you and thank you!
By the way, you probably should grab the recovery-RA-eris-v1.6.2-trackball-optional.img 1.7.1 version (it has all of the functionality of the "original" 1.6.2 Amon_RA; the first "trackball-not-required" version I built was based on the 1.6.2 source that actually omitted some of the menu options).
Cheers!
i have the trackball not working during recovery issue as well
I have found, and I am almost certain this will work for you, plugging your phone into your charger will get your trackball to work
If I don't have my cord to plug into the usb, I've used a paper clip to press against the top of the usb port towards the trackball and have found this to work as well
if you have any questions on the process please don't hesitate to contact me
NPH- said:
i have the trackball not working during recovery issue as well
I have found, and I am almost certain this will work for you, plugging your phone into your charger will get your trackball to work
If I don't have my cord to plug into the usb, I've used a paper clip to press against the top of the usb port towards the trackball and have found this to work as well
if you have any questions on the process please don't hesitate to contact me
Click to expand...
Click to collapse
Actually, most people find out about the problem, or it's more severe when a cord/charger is plugged in.
roirraW "edor" ehT said:
Actually, most people find out about the problem, or it's more severe when a cord/charger is plugged in.
Click to expand...
Click to collapse
Does the problem worsen over time to the point at when it does it if it's not on the charger? Cuz mine's pretty bad on the charger.
I went through this as well. The various tricks to get it to work succeed on some phones and not others, but they're worth a try. In most cases the trackball will continue to deteriorate over time and mine got to the same point where I couldn't scroll down and therefore couldn't use RA to flash. But I needed to flash it back to stock so I could get a refurb from Verizon via my warranty. At that time, I don't think this RA that doesn't require a trackball was available. I asked about if there was and I couldn't find anything about it. Thought about trying to use the RA source and build a version myself but I just didn't have the time and lord knows, screwing that up might have really borked my phone for good, so I get it go. Now that RA without the trackball is out there, I'd use it if you can get that on your phone.
But there's another very easy solution. You can download ROM Manager from the market: ROM manager will let you flash ROMs without the trackball. It uses Clockwork Recovery for flashing and I was concerned at first about the stories of CR possibly bricking phones (in fact this not really a serious risk) or maybe making it harder to return the phone to unrooted stock or something else. But in fact, ROM manager uses Clockwork by only temporarily loading CR in memory, where you can use it to flash a ROM, and it does NOT replace RA! It leaves RA intact on your phone. If you reboot, RA is there. You can use ROM manager to flash any ROM and in my case I used it to flash the easy, return to stock zip that you can find here on the Eris forum. I brought it to the Verizon store and all I had to say was the trackball died and they traded me for a refurb.
BTW, this was a few months ago and there were several threads here with stories about people calling Verizon (not the stores) with tales of woe about their Eris and getting a free upgrade to Incredibles, Moto Droids, etc. if they were very nice about asking. This might have been a time when the inventory on the Eris was low. Anyway, I tried twice times and couldn't swing it - they only offered a refurb Eris. Found a local store with the Eris in stock and did it on the spot.
Now, if an Eris is out of warranty, then the best route is to replace the trackball. There are threads on XDA with all the step by step instructions you need. These are the same trackballs that are used in many of the Blackberrys and apparently those fail frequently and there are a LOT of options available on line for about $3-$5 via Amazon, etc. And hey, you can get them in kinds of whizzy colors ;-p
Hope this helps!
Good luck!
CPCookieMan said:
Does the problem worsen over time to the point at when it does it if it's not on the charger? Cuz mine's pretty bad on the charger.
Click to expand...
Click to collapse
That's my observation and experience.
Sent from my Eris using XDA App
Oh Man!
roirraW "edor" ehT said:
That's my observation and experience.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
crap! that is what I thought and this just confirmed the fate and almost certain death
I think I'm being stalked but maybe I'm not the only one.
So after my battery ran out today I realized that Clockworkmod does not allow charging while the phone is off... This left me in a tricky situation where I could not charge my phone at all. I had seen others mention using another battery but I did not have one on hand. Here's how I replaced Clockworkmod with Amon-Ra to fix it (this also works for all recovery images that I know):
REQUIREMENTS:
-Computer with ADB
-Rezound with Clockworkmod or other faulty recovery
-Amon-Ra's recovery image (attached)
1) Unplug USB and remove battery
2) Put battery in
3) Plug USB into computer (with ADB installed)
4) Enter "adb devices" until you see your Rezound show up as recovery. During this time, the orange LED may either blink shortly first or be solid for a few seconds and then turn off. Once it turns off, it should be accessible over ADB.
5) Grab your amonra recovery img and use adb to copy to phone.
Example: adb push amon-ra-3.15.img /tmp/amon-ra-3.15.img
6) Flash the image to recovery.
Example: adb shell flash_image recovery /tmp/amon-ra-3.15.img
7) Reboot your phone (adb reboot) and repeat steps 1-3 (but this time using wall outlet)
8) Sit back and let Amon-Ra save your Rezound. Once your orange LED has been solid for over a minute, you should be good
Nice guide
Koush really needs to fix that problem or discontinue it for our phone
Sent from my Galaxy Nexus using Tapatalk 2
superchilpil said:
Nice guide
Koush really needs to fix that problem or discontinue it for our phone
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It is discontinued. I don't even really know where to get it anymore lol.
Granted, I don't use CWM, but nice job.
con247 said:
It is discontinued. I don't even really know where to get it anymore lol.
Click to expand...
Click to collapse
Rom manager. Also he offers touch for pay (which is what I mistakenly purchased thinking it could mount the internal sd. Either way though I agree, it is not safe for the average root user even to have a recovery that doesn't allow charging even through a wall outlet. It should only list Amon-Ra's under alternate recovery.
Chyrux said:
Granted, I don't use CWM, but nice job.
Click to expand...
Click to collapse
Thanks, I know the average user is using Amon-Ra or TWRP but figured I'd put this here so we have a clear guide for getting out of this situation where some users may end up returning their phone to HTC (possibly getting charged after the fact)
con247 said:
It is discontinued. I don't even really know where to get it anymore lol.
Click to expand...
Click to collapse
Its odd, those same people who can't search to find out how to fix the problem, can find CWM
Sent from my Galaxy Nexus using Tapatalk 2
I'm fairly new to the Rezound. Came from the Nexus side because I wanted a more multimedia-friendly device (better external speaker/camera/same res). I bought mine pre-rooted and flashed to Clean, which was pretty nice - until I ran into this issue. I bought another battery from Verizon and hooked the other one up to an external charger. I figure it won't hurt to have two batteries anyway.
I know a ton of people have bad things to say about CWM but is this really the only issue? It flashes just fine, right? I ran a nandroid on what I have now and tried to install the latest leak, but I got a ton of reboots. Eventually reverted back to Clean. Either way, thanks for the writeup. Would have saved me a ton of stress over the weekend, hahaha.
Nice work djh816. this was the thing i have always feared lol. matter of fact, this is a HUGE weight lifted out of my mind. Thanks so much for this. keep up the good work
nice guide but i dont think anyone uses cwm anymore. still, thanks
I do. Haven't had issues. I just, if you can believe it, charge my battery before I do anything.
Sent from my ADR6425LVW using Tapatalk 2
Btw, I would change, just to be safe, but haven't seen instructions for doing so, and don't really want the drama that USUALLY comes from asking a question (can't always find what you are searching for).
Sent from my ADR6425LVW using Tapatalk 2
RED ZMAN said:
Btw, I would change, just to be safe, but haven't seen instructions for doing so, and don't really want the drama that USUALLY comes from asking a question (can't always find what you are searching for).
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
The OP of this thread are the instructions... Just do Steps 2-6.
Edit: or use hasoon2000's first AIO toolkit, which has AmonRa as a flash option (also another lingering source of CWM):
http://forum.xda-developers.com/showthread.php?p=22696442
RED ZMAN said:
Btw, I would change, just to be safe, but haven't seen instructions for doing so, and don't really want the drama that USUALLY comes from asking a question (can't always find what you are searching for).
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Haha I was fine as well with Clockworkmod Touch and had no clue it even had that problem until my battery finally drained all the way. Then I was SOL. But yea as he said, following those instructions simply replaces the recovery image. All your data will still be in tact (aside from your clockworkmod backups if you have them but Amon-Ra can read those too I think)
Yeah, I figured those instructions would work. You should advertise this as a how to swap between them also. There are others using CWM, and just not talking about it.
Thanks.
Sent from my ADR6425LVW using Tapatalk 2
I have an easier solution, while phone has been dead for 5-10 minutes, hold power button and as soon as screen flashes plug in the device. Works every time. I also have 3 batteries, 1 original, 2nd from my replacement from warranty, 3rd is extended. I don't ever even change batteries though.
Funny that people are still having/talking about this issue.
I remember when the issue first popped up on the Rezound and people were clueless. All kinds of theories as to the cause and solution.
I knew of the cause from a few phones back... CWM has a history of issues with charging while powered off. I learned of it from an initial release of CWM for a different phone would that when trying to charge with it powered off, would turn on the screen.
Easiest way is to run the command
adb reboot download
boom phone restarts...
I have had this modded version of CWM touch by someone else (I will let him say who he is just in case he does not want to take credit).
It is a modded version of CWM 5.8.1.4-Touch that solves the charging when off problem.
I can not support it but can assure you it works since I have been using it since the beginning of April. I do switch between this and AmonRa for testing my ROM but all my backups are with this.
Still need to copy the .hidenandroidprogress file from internal to external clockworkmod folder to solve the freeze problem when backing up or restoring.
Just install it just like any other recovery.
NOTE: If anyone want to take this and start another thread with it that is fine by me. I just don't have time which is why I never posted it before.
I ended up doing it through fastboot, as I'm a bit more familiar with that, but thanks for the notes and link. I'm now on Amon Ra.
Anything I need to know as a CWM user since, oh, the G1?
And do I need to worry about moving that file so backups work, like you did in CWM?
Thanks again.
Thanks man, this this is totally pimp, sent you a donation - get yourself some good beer!
So... I have FJ Mod on my note. Things have been running great for a long time. Then a few days a go, out of the blue, google voice was constantly crashing. Then the gapps process. Then it got ridiculous and everything would crash. Then I noticed that when I restart, it saves nothing that I had done. For instance, my call log, text messages, moved icons on my homepage.
I did a wipe in CWM, and everything came back the exact same. Still the same problem, icons still in the wrong place... no idea whats going on.
Has anyone got any advice for me? I was going to try and put a new ROM on later if worse comes to worse, but as is, this is very frustrating. I often have to restart my phone just to use the browser, or message, or anything really. I am just hoping that my internal SD isn't screwed some how and now allowing me to write to it. I haven't done any changes. I don't even believe I have downloaded any apps since a week or so prior to this issue.
Flashing with ODIN did not good either. I tried to revert back to stock. It uploaded with no issues apparently, and then when it rebooted I was back in ICS with everything as it was... argh.
Find one of the the ics leaka one click Odin packages and run that. Should wipe everything, and then you just have to flash cwm and root again.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
welchertc said:
Find one of the the ics leaka one click Odin packages and run that. Should wipe everything, and then you just have to flash cwm and root again.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Well, I tried something similar with a rogers stock rom. Booted up Odin, connected to issues. Uploaded/transferred no issues. Figured I'd be on stock Gingerbread upon bootup, but it was ICS! I've done this and similar on multiple phones, not sure whats happening. I will try again with a different rom as you suggested tonight.
I know where the leaks are...this loser has them here....
http://forum.xda-developers.com/showthread.php?t=1740367
welchertc said:
Find one of the the ics leaka one click Odin packages and run that. Should wipe everything, and then you just have to flash cwm and root again.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
johnnyb82 said:
Well, I tried something similar with a rogers stock rom. Booted up Odin, connected to issues. Uploaded/transferred no issues. Figured I'd be on stock Gingerbread upon bootup, but it was ICS! I've done this and similar on multiple phones, not sure whats happening. I will try again with a different rom as you suggested tonight.
Click to expand...
Click to collapse
bigjoe2675 said:
I know where the leaks are...this loser has them here....
http://forum.xda-developers.com/showthread.php?t=1740367
Click to expand...
Click to collapse
Greatly appreciated! Thanks for posting the link. I will try it tonight and let you know how it works out.
johnnyb82 said:
So... I have FJ Mod on my note. Things have been running great for a long time. Then a few days a go, out of the blue, google voice was constantly crashing. Then the gapps process. Then it got ridiculous and everything would crash.
Click to expand...
Click to collapse
I had the EXACT problem, out of the blue as well. I didn't have the other stated problems in your OP but I did have the one quoted above. First voice , then a few google apps(gmail, drive, etc). The apps would hang for a few 1-2 minutes (felt like hours) and the phone including capacitive buttons became unresponsive and couldn't do anything with the phone. The "wait" or "ok" buttons on the force close popup were not clickable.. It sorted itself out in a few days and boy did it drive me NUTS. I was afraid to post up here in fear people would think I was nuts and did something myself to make things go so awry. I was convinced I myself was nuts.. im by no means daft when it comes to android dev/tinkering lol. Very strange
Sent from my SAMSUNG-SGH-I717 using xda premium
Well I was impatient and tried 2 different roms right away. Neither worked. Odin showed "pass", no errors. Then it does its auto-restart and bam, back where I was. Not having the best of luck with this right now.
Any other ideas would be appreciated!
simbill said:
I had the EXACT problem, out of the blue as well. I didn't have the other stated problems in your OP but I did have the one quoted above. First voice , then a few google apps(gmail, drive, etc). The apps would hang for a few 1-2 minutes (felt like hours) and the phone including capacitive buttons became unresponsive and couldn't do anything with the phone. The "wait" or "ok" buttons on the force close popup were not clickable.. It sorted itself out in a few days and boy did it drive me NUTS. I was afraid to post up here in fear people would think I was nuts and did something myself to make things go so awry. I was convinced I myself was nuts.. im by no means daft when it comes to android dev/tinkering lol. Very strange
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
LOL I actually waited a few days before posting here too. I was hoping that maybe uninstalling and reinstalling some, or updated, or clearing cache and all that would help. As you can see, it did nothing. Heck, after I restart my updates didnt even stick and Google Play is trying to download them again!
Well... still no luck.
Here is another thing I noticed. When I hook up the note to my PC, and look at it, I cannot access my external SD. Furthermore, I had a file on my internal SD that I deleted. When I restarted my phone the file was back. Yet in windows it removed without error. I have no idea what is happening at all.
And now its reading it again........ Ive literally been sitting here trying a bunch of different ways to fix this. Playing around in CWM, trying ODIN including a couple 1 click solutions. The one starts writing to NAND, then stops and gives me an error.
Try taking out your sd card and running it for a while. First note i got was acting that way from the get go. Took it back and got a new one. It started doing the same thing. Finally took out sd card and ran great. Card was going bad. I had replaced the 8 gb stock card with the 16 gb one i had in another phone and apparently the mote didn't like it.
Sent from my SAMSUNG-SGH-I717 using xda premium
johnnyb82 said:
Well... still no luck.
Here is another thing I noticed. When I hook up the note to my PC, and look at it, I cannot access my external SD. Furthermore, I had a file on my internal SD that I deleted. When I restarted my phone the file was back. Yet in windows it removed without error. I have no idea what is happening at all.
And now its reading it again........ Ive literally been sitting here trying a bunch of different ways to fix this. Playing around in CWM, trying ODIN including a couple 1 click solutions. The one starts writing to NAND, then stops and gives me an error.
Click to expand...
Click to collapse
Did you, by any chance, install a custom kernal? IIRC, one of them messed with the mount points. By far, the only way to fix your issue immediately will involve restoring to stock through ODIN, then rerooting and reflashing CWM. This will 100% mark your Note as either defective, or prove that it's a problem in another area. However, I don't believe your problem is with your SD Card, unless you've been using an app like apps2sd.
If you're weary about doing this, try to reflash CWM, or TWRP to figure out if it's something going on with the recovery partition and/or settings. I'm no expert, but the only thing I'm aware of that sticks around through a wipe, and multiple flashes are our recovery, our internal SD files (possible), and sometimes the modem. Also, the one click leaks include a not loader, which could prevent you from restoring a GB Nandroid.
By flashing CWM, then TWRP, then CWM again, or sticking with TWRP, you at least knock out one variable...and by reformatting your internal SD, you ensure no resources are sticking around.
Edit:are you using TiBu to backup and restore/migrate after a flash? Verify your backups under the batch lost.
What could be happening, is you're restoring data in CWM, or TiBu, or w/e ap you're using, and then the Google account sync restore is restoring your settings, and replacing the desired ones, or vice versa.
Edit again: Which launcher are you using? Which utilities do you use? What are your main root apps?
The backup verify is a must...but some launchers will scoot icons out of the way. If you're having a touch screen issue, or an S Pen issue, you could be draggn items around when you're not aware of it.
I'll see this through. You've caught my interest.
Sent from my Transformer TF101 using XDA Premium HD app
johnnyb82 said:
So... I have FJ Mod on my note. Things have been running great for a long time. Then a few days a go, out of the blue, google voice was constantly crashing. Then the gapps process. Then it got ridiculous and everything would crash. Then I noticed that when I restart, it saves nothing that I had done. For instance, my call log, text messages, moved icons on my homepage.
I did a wipe in CWM, and everything came back the exact same. Still the same problem, icons still in the wrong place... no idea whats going on.
Has anyone got any advice for me? I was going to try and put a new ROM on later if worse comes to worse, but as is, this is very frustrating. I often have to restart my phone just to use the browser, or message, or anything really. I am just hoping that my internal SD isn't screwed some how and now allowing me to write to it. I haven't done any changes. I don't even believe I have downloaded any apps since a week or so prior to this issue.
Click to expand...
Click to collapse
Also, tap USB utilities in settings, by the other FJ mods, and tap the selection there, then check to see if you can find your SD card through your PC.
In addition to the above, you can also enter the "Tools" section of FJmods, and disable ad blocking, remove touchwiz UI, s voice, etcetera, and return ALL settings too default, and remove all extras. You can reflash recovery there too.
How are you trying to reformat your SD card?
Sent from my Transformer TF101 using XDA Premium HD app
Jamesyboy said:
Also, tap USB utilities in settings, by the other FJ mods, and tap the selection there, then check to see if you can find your SD card through your PC.
In addition to the above, you can also enter the "Tools" section of FJmods, and disable ad blocking, remove touchwiz UI, s voice, etcetera, and return ALL settings too default, and remove all extras. You can reflash recovery there too.
How are you trying to reformat your SD card?
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
I had installed a custom kernel on Gingerbread before, but obviously that was replaced with the one I used with FJmod. It had been operating fine for over a month.
Also, I removed my SD Card, and tried everything without it. I have tried restoring gingerbread stock and ICS stock through both ODIN and CWM. Even formatting through CWM does nothing as when I restart I am back to normal.
As for root, I only had 2-3 programs with access. ES File Manager/Task manager, and I tried one called Lucky Patcher (I will verify this evening). All of these had been on for at least a week prior to all this beginning.
I havent been using TiBu for anything at all actually.
The launcher I am using at the moment is Nova.
Other than that, I am going to try a few of your suggestions once I am done work. I will post my results tonight!
Thanks for the suggestions and info, greatly appreciated.
EDIT: Just to be clear. I am formatting then restarting and all my apps, icon placements and wallpaper return. Even my call history is stuck up to the 13th and erases recent calls. I am also trying to revert to stock ICS and Gingerbread through both ODIN and CWM. After it is done installing through ODIN and reboots, I return to the way my phone was before. Same with CWM. After flashing through CWM I return right back to the way it was. I am not doing any restoring or anything. I have done this plenty of times in the past before. The only thing I can possibly imagine at this point is that my SD is somehow stuck on read only. Yet it is weird because again, I can delete files and apps (and even windows shows them as gone), but after a restart they are all back! I can remove apps, but they are still in the app menu too.... I can even run them lol (even after deleting their folder). The phone is stuck in stasis.
All of this just happened one day out of the blue. No new apps (for at least a week) too.
I have a GTab that had the EXACT same symptoms.. turns out it's internal flash memory was bad, not the microSD. going for broke I opened it up and desoldered the flash memory IC and it uses the microSD now as its primary storage. If even after a stock reflash you have problems I hope you have warranty.
Black6spdZ said:
I have a GTab that had the EXACT same symptoms.. turns out it's internal flash memory was bad, not the microSD. going for broke I opened it up and desoldered the flash memory IC and it uses the microSD now as its primary storage. If even after a stock reflash you have problems I hope you have warranty.
Click to expand...
Click to collapse
Great... lol! I have a warranty, but no one will work with it due to the fact I have a custom rom. Am I maybe contacting the wrong people? I contacted Rogers and they said they couldn't help me. Well I am going to purchase the s3 as I get a small discount on it. I am positive I will end up with the next note unless some sort of crazy deal passes in front of me for another note.
johnnyb82 said:
Great... lol! I have a warranty, but no one will work with it due to the fact I have a custom rom. Am I maybe contacting the wrong people? I contacted Rogers and they said they couldn't help me. Well I am going to purchase the s3 as I get a small discount on it. I am positive I will end up with the next note unless some sort of crazy deal passes in front of me for another note.
Click to expand...
Click to collapse
No stock Odin for your phone? I would attempt this to be absolutely sure the problem isn't software related.. they should warranty hardware faults.
Black6spdZ said:
No stock Odin for your phone? I would attempt this to be absolutely sure the problem isn't software related.. they should warranty hardware faults.
Click to expand...
Click to collapse
No sir. I tried stock gingerbread and ics. I've tried custom roms. I've tried just erasing it too! Tried Odin and CWM. I am going to try and change recovery today again too.
Rogers said they won't help. They used the word "launcher" but I knew what he meant. They think I may have overclocked it any burnt it out I bet. Maybe I will try calling samsung.
Thing is, all my private info is on there! At least no private pics though
johnnyb82 said:
No sir. I tried stock gingerbread and ics. I've tried custom roms. I've tried just erasing it too! Tried Odin and CWM. I am going to try and change recovery today again too.
Rogers said they won't help. They used the word "launcher" but I knew what he meant. They think I may have overclocked it any burnt it out I bet. Maybe I will try calling samsung.
Thing is, all my private info is on there! At least no private pics though
Click to expand...
Click to collapse
If your have insurance, and it turns out the phone was physically damaged , you could try making a claim....but that's only if it was physically damaged. So you restored stock through odin? Did this happen on the stock unrooted rom?
Sent from my Transformer TF101 using XDA Premium HD app
Jamesyboy said:
If your have insurance, and it turns out the phone was physically damaged , you could try making a claim....but that's only if it was physically damaged. So you restored stock through odin? Did this happen on the stock unrooted rom?
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
Well its currently stuck on FJ Mod (which I think is a great rom), and then it just started acting up. I cannot restore Gingerbread stock, or ICS stock, or anything else. ODIN and CWM both show completed on my attempts, but upon reboot my device is back exactly where it left off on the 13th.
I picked up the S3 and I like it, but I miss my note badly
So, I stupidly allowed ROM Manager to install an update for me, including updating my TWRP recovery...and now MoBoot is borked. Nothing will boot except WebOS Recovery (just a USB icon) and everything else fails to boot.
Is there a quick way to fix this? I mean, I could wipe the TP and try a fresh MoBoot etc. but I'd rather not if I can save all my data etc.
Thanks all.
Sent from my Desire HD using xda app-developers app
tedrogers61 said:
So, I stupidly allowed ROM Manager to install an update for me, including updating my TWRP recovery...and now MoBoot is borked. Nothing will boot except WebOS Recovery (just a USB icon) and everything else fails to boot.
Is there a quick way to fix this? I mean, I could wipe the TP and try a fresh MoBoot etc. but I'd rather not if I can save all my data etc.
Thanks all.
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
You could try running ACMEInstaller3 without running ACMEUninstaller. I believe I did that once and nothing got wiped.
That's a good suggestion. Well, it's a suggestion and I like options that make sense, so thank you.
But, before I go for this...any other possibilities?
Sent from my Desire HD using xda app-developers app
If you cant boot anything, I would think AcmeInstaller is your best bet. And if that doesnt work. Use the webOS doctor and start all over.
jsgraphicart said:
If you cant boot anything, I would think AcmeInstaller is your best bet. And if that doesnt work. Use the webOS doctor and start all over.
Click to expand...
Click to collapse
I'm going through ACMEInstaller3 now...did the old "novacom boot mem:// < ACMEInstaller3" line in CMD, and I'm getting scary amounts of linux verbose output pouring down the screen. It's been over 10 minutes now of what looks like error messages. I'm not hopeful!!
Frankly I'll be amased if this works! Right now I'm thinking WebOS Doctor is the way to go.
===
Update: It didn't work. I'm just back at the same point. Nothing will boot beyond MoBoot. Just hangs. I could reinstall a different recovery, but I can't mount the SD in the TP. Maybe I can adb push it???? Any ideas?
I would use Acmeuninstaller first then ACMEInstaller 3 with a regular nightly. Then if that goes to plan use one of your CWM/TWRP backups to restore your settings as they won't be deleted.
Yeah I've got plenty of backups in Ti and CM/TWRP. Hassle though eh!
Still, I'm bored unless I can fiddle.
Sent from my Desire HD using xda app-developers app
tedrogers61 said:
I'm going through ACMEInstaller3 now...did the old "novacom boot mem:// < ACMEInstaller3" line in CMD, and I'm getting scary amounts of linux verbose output pouring down the screen. It's been over 10 minutes now of what looks like error messages. I'm not hopeful!!
Frankly I'll be amased if this works! Right now I'm thinking WebOS Doctor is the way to go.
===
Update: It didn't work. I'm just back at the same point. Nothing will boot beyond MoBoot. Just hangs. I could reinstall a different recovery, but I can't mount the SD in the TP. Maybe I can adb push it???? Any ideas?
Click to expand...
Click to collapse
Can you get into webOS recovery? If it was my TouchPad, I would just go with the webOS doctor. You dont want to lose webOS or its recovery or else you have really bricked your Touchpad.
jsgraphicart said:
Can you get into webOS recovery? If it was my TouchPad, I would just go with the webOS doctor. You dont want to lose webOS or its recovery or else you have really bricked your Touchpad.
Click to expand...
Click to collapse
I can get into recovery from MOBOOT. I get the usual USB icon on the screen. I can't get into anything else though...not recovery, webos or android.
Sent from my Desire HD using xda app-developers app
tedrogers61 said:
I can get into recovery from MOBOOT. I get the usual USB icon on the screen. I can't get into anything else though...not recovery, webos or android.
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
I would use the webOS Doctor then. As long as you have backups of everything, you don't have to worry about losing your stuff.
jsgraphicart said:
I would use the webOS Doctor then. As long as you have backups of everything, you don't have to worry about losing your stuff.
Click to expand...
Click to collapse
So I decided that WebOS Doctor is my only option now...but when I come to try this tonight, the TP is dead (battery) and charging doesn't seem to be happening.
I've got the large battery icon with red bar across the bottom, so it seems to be getting power. I've checked the twist off part on the charger assembly, that's all okay, but it's just taking an age to charge up. I would have thought that after an hour it would be near complete, and well easily over 30% which WebOs Doctor needs to run.
I've reset it loads of times too (Centre Button and power for 15 seconds)...I read this is supposed to help in CM forums, but I don't think it's making any difference at all.
I can't see how swapping the USB lead will help...I've never had a broken USB lead in my life! This seems like a really daft (clutching at straws) option that is banded about the forums.
Any ideas? How long should this take to charge? Will it ever charge? Does it need a working WebOS to gain access to it's own battery stats? This seems crazy if it's not built into firmware!!
Thanks for your help so far guys.
==
EDIT / UPDATE: So, eventually after near 2 hours the TP sprung into life. The battery must have been severly drained. After that I was able to run WebOS Doctor. The TP has just finished it's reboot sequence, which also took a disturbingly long amount of time, but looks like I'm home free! Now just to re-do the Android install procedure.
I've read people saying they had to leave it charging overnight before seeing signs of life. Just leave it charging for a long while.
jsgraphicart said:
I've read people saying they had to leave it charging overnight before seeing signs of life. Just leave it charging for a long while.
Click to expand...
Click to collapse
it also helps to use the charger/wire that came with it...and to not use that wire for other devices. Messed up my one s port.
Sent from my HTC VLE_U using xda app-developers app
havikx said:
it also helps to use the charger/wire that came with it...and to not use that wire for other devices. Messed up my one s port.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Well, swapping the cables made no difference for me...and anyway, I'm happy to report that I'm back up and running.
I'm putting FatnCreamy on right now.
Thanks for all your help peeps!
tedrogers61 said:
Well, swapping the cables made no difference for me...and anyway, I'm happy to report that I'm back up and running.
I'm putting FatnCreamy on right now.
Thanks for all your help peeps!
Click to expand...
Click to collapse
I have come across another really odd issue. For some reason I can't put TWRP on now (latest version 2.3.10). It installs fine through Goo.im Manager, but when you try and run it you get an "invalid magic" message and it fails to boot. That then makes it impossible to boot any other mode except recovery without doing a reset first (centre button and power).
I had to go back to non touch CWM 1012 via ACMEInstaller and it works fine.
Any ideas why TWRP would be not working all of a sudden? It all worked fine before this caper when I allower the ROM Manager to do some updates for me. *slaps own forehead*.
Okay guys so I have a DX2 and I have a problem with it pick up signal it gets one bar at a time until it has full service and then it immediately goes back to no service also if I leave it sitting and don't touch it it will reboot. Please help me out. And the phone is not rooted.
HTCTerrorist said:
Okay guys so I have a DX2 and I have a problem with it pick up signal it gets one bar at a time until it has full service and then it immediately goes back to no service also if I leave it sitting and don't touch it it will reboot. Please help me out. And the phone is not rooted.
Click to expand...
Click to collapse
this phone is pretty wonky even under the best conditions. i would say it sounds like you have a bad app installed, although i dont think that would mess with signal. try doing a factory reset. hold volume down and power for about 5 seconds, then using volume down, scroll to android recovery. hit volume up to select it. once you see the android with the triangle exclamation point, hit both volume up and down at the same time. select factory reset.
(this will erase all apps and wipe the system, photos and music should be ok, but you might want to transfer them to a computer for safety) only solution i can think of. the stock ROM usually runs pretty well, but with 500mb of RAM all it takes is to be running a couple/few apps and it goes absolutley nuts. this is the whole reason i found XDA developers. hope this helps.
Lorenzo VonMatterhorn said:
this phone is pretty wonky even under the best conditions. i would say it sounds like you have a bad app installed, although i dont think that would mess with signal. try doing a factory reset. hold volume down and power for about 5 seconds, then using volume down, scroll to android recovery. hit volume up to select it. once you see the android with the triangle exclamation point, hit both volume up and down at the same time. select factory reset.
(this will erase all apps and wipe the system, photos and music should be ok, but you might want to transfer them to a computer for safety) only solution i can think of. the stock ROM usually runs pretty well, but with 500mb of RAM all it takes is to be running a couple/few apps and it goes absolutley nuts. this is the whole reason i found XDA developers. hope this helps.
Click to expand...
Click to collapse
I have factory reset twice, the only other solution I can think of is rooting it and flashing a stock de-bloated rom.
HTCTerrorist said:
I have factory reset twice, the only other solution I can think of is rooting it and flashing a stock de-bloated rom.
Click to expand...
Click to collapse
i would go for it sir. rooting and romming on this phone (since the locked bootloader) is pretty fool proof. i tried my hardest over the course of two years and could not brick this thing. take the plunge! i suggest eclipse. at least for fully functional.
Lorenzo VonMatterhorn said:
i would go for it sir. rooting and romming on this phone (since the locked bootloader) is pretty fool proof. i tried my hardest over the course of two years and could not brick this thing. take the plunge! i suggest eclipse. at least for fully functional.
Click to expand...
Click to collapse
The only way to brick it is to flash the ntelos sbf to a Verizon phone
Sent from my SCH-I535 using xda premium
Just make sure you have a fully charged battery before you start and NEVER unplug your phone when it is connected to your computer flashing an sbf file.
Eclipse 2.3 is a good stable debloated blur-based rom. Cm7 is AOSP which is still stable, but not as much as eclipse. I've tried pretty much all of the roms for the X2 and these are my two favorites, mainly because they are the most stable. Any rom is going to have minor problems but the cause isn't the rom, but the phone.
Sent from my MB870 using Tapatalk 2
Lorenzo VonMatterhorn said:
i would go for it sir. rooting and romming on this phone (since the locked bootloader) is pretty fool proof. i tried my hardest over the course of two years and could not brick this thing. take the plunge! i suggest eclipse. at least for fully functional.
Click to expand...
Click to collapse
I doubt anyone else could pull this off, but I bricked 3 of them in the first month after release....
Lrs121 said:
The only way to brick it is to flash the ntelos sbf to a Verizon phone
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
No I did not do that...
Now I am attempting a mod, but i expect to brick #4
EDIT
Bricked #4