Hey all,
So awhile back, I flashed ClassicNerd, which was fantastic, but I wanted to switch back to CM9 last night. I went into CWM and wiped everything and flashed CM9, but when I booted up my Touchpad, it seems like ClassicNerd remained there. It's a bit hard to explain, so I've attached a pic of the issue I'm having. How exactly do I get rid of ClassicNerd? Do I just leave it there? Thanks for your help guys!
sportsinger75 said:
Hey all,
So awhile back, I flashed ClassicNerd, which was fantastic, but I wanted to switch back to CM9 last night. I went into CWM and wiped everything and flashed CM9, but when I booted up my Touchpad, it seems like ClassicNerd remained there. It's a bit hard to explain, so I've attached a pic of the issue I'm having. How exactly do I get rid of ClassicNerd? Do I just leave it there? Thanks for your help guys!
Click to expand...
Click to collapse
download root exblorer or es file manager go boot folder and delete the classicnerd ulmage
Here you go. Full instructions in the OPs post.
http://forum.xda-developers.com/showthread.php?t=1705627
Sent from my cm_tenderloin using xda app-developers app
Thanks guys, I appreciate it
Just download tga.uImage cleaner from the Classicnerd website and flash in CWM before flashing a new rom and it will completely clean moboot and return it to default settings
Sent from my CyanogenMod9 TouchPad using TapaTalk 2
Related
So i got cm7 on my phone last week and ever since i got it when i leave the phone on for more that 2 min the phone will just turn itself off and restart and show the cyanogenmod logo with the little android guy on the skateboard (same as once you turn on the device) and all the apps and everything is shut off. What is happening, is this normal?
Still looking for a solution
Flash back to stock to see if it does it there. Then reflash CM7.
Eyeronik said:
Still looking for a solution
Click to expand...
Click to collapse
Maybe you restored system data from a different ROM and it broke something. Flash back to stock and then follow the direction to a T on flashing CM7. Do not restore anything and see if you have the issue.
I used cm7 for 2 weeks to see what all the fuss is about. I had the problem you where describing. in my case it was caused by restoring too much stuff from titanium back up. follow the instructions and you shuld be fine.
After getting it working I did not like cm7 so I uninstalled it and went to the i9000 gingerbread based ROMs(I am using continuum) and dident look back.
Us cappy owners are fortunate to have such a rich developer community with so much to choose from.
Sent from my GT-I9000 using XDA Premium App
Yea this is the first rom i have put on it. I just got it a couple weeks ago. Im going to attempt to figure out how to flash back to stock. Thanks guys.
Move some apps to external and see if it still happens.
Sent from my SGH-I897 using XDA Premium App
Hey guys, I rooted my NC using the instructions on NookDevs several months ago. I recently started using MIUI on my Fascinate and loved it so much that I had to have it on my NC. I put the ROM on my NC uSD, flashed CWM thru ROM Manager, then rebooted into CWM. From there, I assumed the steps would be the same as w my phone, so I wiped data/cache/Dalvik then TRIED to reboot into recovery so I could install the ROM. I never got back to CWM, it just goes straight into the "Log into Google" process.
My problem is that I can't sign in to Google. It just keeps telling me that a connection w the Google servers couldn't be established. I'm connected to wifi and able to get on the internet w the NC browser. On top of all that, when I press the "N" button at the bottom, nothing happens. It's like I have no home screen at all. I've tried turning the NC on and off, disconnecting and reconnecting fm and to my wifi network, and forgetting the network altogether. Can anyone help me out?
Sounds a lot like what I just went thru. I found the MIUI interface interesting so thought I would try it.
Jumped right to Phiremod's V.2 MIUI ROM. After several failed attempts (including using ROM Manager) figured I backup and start from the get-go.
Factory Reset via CWM (wipe data/cache/dalvik). Fresh bootable uSD and flashed Phiremod's ROM directly thru CWM. Took a while to restart (about 5 minutes) but it worked.
Give it a shot.
If you need the Phiremod link: http://rootzwiki.com/showthread.php?3995-Phiremod-MIUI-for-Nook-Color
Thanks for the info! I can't get into CWM tho. Idk why, but since I can't log in to Market, I can't dl ROM Manager, so I can't boot into CWM.
My guess is that I'll have to do the whole boot interrupt 8 times to go back to stock, then re-root, then dl ROM Manager and go fm there. Was just hoping I didn't have to go thru the re-rooting process. Any other thoughts?, or am I just outta luck?
Sent from my SCH-I500 using XDA App
Start by creating a new bootable uSD with CWM. Factory reset and wipe from there.
http://androidforums.com/nookcolor-...workmod-version-3-2-0-1-recovery-sd-card.html
And format your uSD with this: https://www.sdcard.org/consumers/formatter_3/
Awesome! I'll start this tmrw. Thanks so much for ur help!
Do u recommend not going w the MIUI 1.8.5 fm their website?, in favor of the version u flashed?
Sent from my SCH-I500 using XDA App
I really admire Phiremod's work with past ROMs. I liked his mods to the original MIUI interface.
Rather a matter of preference really.
Hope all this helps!
I'm really greatful. I was totally hamstrung. Thanks again!
Sent from my SCH-I500 using XDA App
All went well I presume?
Hahaha, thx for the follow-up. Sadly, that still has yet to be seen. I've been slammed this weekend and haven't had a chance to sit down w it. I'll definitely let you know tho.
Thx again for checking up on me!
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Maybe he dont follow the instructions correctly
Sent from my GT-N7000 using xda premium
meminiau said:
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Click to expand...
Click to collapse
What method is he using to flash? If using pc Odin does the flash get stuck at factoryfs. Img?
Was he on ics stock and did he perform any factory resets on it?
If answers are yes, it's likely he's got traces of damage on his emmc chip, but we need to know where the flash is failing to understand further.
Sent from my GT-N7000 using xda premium
No and no.
His phone came with GB. He downloads the ROMs using his computer then transfers the zip to then flash using CWM recovery.
He has tried lots of different ROMs. He tried to install a new ROM the other day but before doing so he deleted a few ROMs he still had on the SD card. He flashed the new ROM and it didn't work. He freaked coz he didn't do a backup first, but he tried installed the ROMs that were still on the SD card and found them all but one to work, and the one that worked was a ROM that he had tried before but didn't work then, but this time it did work...
What is happening? Is there something he can do?
Swiped on my Gnex
meminiau said:
No and no.
His phone came with GB. He downloads the ROMs using his computer then transfers the zip to then flash using CWM recovery.
He has tried lots of different ROMs. He tried to install a new ROM the other day but before doing so he deleted a few ROMs he still had on the SD card. He flashed the new ROM and it didn't work. He freaked coz he didn't do a backup first, but he tried installed the ROMs that were still on the SD card and found them all but one to work, and the one that worked was a ROM that he had tried before but didn't work then, but this time it did work...
What is happening? Is there something he can do?
Swiped on my Gnex
Click to expand...
Click to collapse
Try flashing rom with pc odin instead of cwm.
Check out Dr ketan sticky thread in rom development for directions on how to use pc odin. It's simple.
Let us know how you progress.
Sent from my GT-N7000 using xda premium
meminiau said:
Hey,
I have a nexus, but my mate has the note. He is having all sorts of problems with it when it comes to flashing ROMs. I was hoping u smart people here might be able to help
What the problem is, is that only about one in 10 ROMs will install. He flashes the usual way... wipe everything, etc but either gets in a boot loop, or just Samsung comes up on the screen, it disappears and then comes back and this repeats. He has to then pull the battery. Another weird thing is that a ROM that may not have worked a few weeks ago, he tries it again and for some weird reason it works. So far he has never been able to flash an ICS ROM.
Any ideas? I've suggested to him to start completely afresh and use fast boot, etc again, but I'm no expert myself. I've never had any dramas myself with the nexus so this has me completely stumped....
Thanks
Dean
Swiped on my Gnex
Edit: sorry guys, he used Odin, not fast boot.
Click to expand...
Click to collapse
No problem at all.
Sent from my GT-N7000 using xda premium
What?????
Swiped on my Gnex
Sounds very odd - only though is he's not following instructions correctly..
I uninstalled the old version of safestrap, then installed the new version. I can do everything just fine (install, wipe, etc) but when I try to boot from the ROM slots, the phone just sits at a black screen.. I tried flashing Eclipse 3.0 and nothing happens.. help???
Sent from my DROID3 using xda app-developers app
Well eclipse 3.0 hasn't worked for me. The latest cm10,aokp,and aosp boot for me as well as mavrom 4.5 and axiomcs 1.0. Have u tried any other roms aside from eclipse?
Sent from my XT862 using xda app-developers app
Don't think eclipse works with new Safestrap. I have tested CM10, AOKP, AOSP, and Steel Droid. Those 4 all are "working".
Steel Droid is the most stable one i have tried so far, CM10, AOKP and AOSP all lag for me.
Hey guys,
New to Droid 3/ Milestone 3 World here.
I just bought one, actually with the 5.2.390.XT860.Brasil.en.BR version.
I'm not exacly new to flashing roms, and recoveries, but in this case I'm a little confused. Is it possible to use SafeStrap on this one? Or better go for an older version of it?
Thanks in advance.
@Munckster, as long as it is rooted you can install safestrap 3.04 and try if custom roms work for you?? but make sure you have the correct SS3 version!!
bArAbAts said:
@Munckster, as long as it is rooted you can install safestrap 3.04 and try if custom roms work for you?? but make sure you have the correct SS3 version!!
Click to expand...
Click to collapse
I was thinking about trying... Maybe during the weekend..
Thanks for the advice, man!
I took my phone back to stock (from an oldish CM9 that had been working reasonably well for me for some time) so I could install SS3. Made the mistake of letting the phone OTA update itself and then had to find a new root hack before I could get SS3 installed.
Unfortunately the OTA update has messed with the radio, as reinstalling the CM9 I've used for months gets a system where the phone app just crashes.
The kexec cm9 on hash code's download site results in a black screen for me. I have to pull the battery to get the phone back. Funnly enough the old CM9 does boot - and every thing works except the phone.
The latest CM10 does every thing I want (I can live with out the camera) BUT I can't receive calls, the phone app crashes. (But I can MAKE calls!).
This is on GSM BTW, not CDMA where I live.
So i'm busted back down to the 'stock' OS so I can use my phone as a phone
And as a new XDA user I can't post my bug report in the developer thread.
Well,
I installed the 3.0.5 version. Works like a charm! The easiest to use recovery that I ever use.
But the question is: Is it safe to downgrade it?
Sorry about the dumb question.
SS3 can be un-installed pretty easily. Boot your 'stock' OS, then use the SS3 app to remove the 'hijack' and then reboot again. No SS3. Just remember to do it from the 'stock' OS and not one of the others.
Don't do what I did with SS2 - from a non stock OS, remove SS and reboot. Ended up with a phone that never finished booting before it rebooted. Fortunately the emergency recovery mode built into the phone worked to recover it.
matthewgeier said:
The kexec cm9 on hash code's download site results in a black screen for me. I have to pull the battery to get the phone back. Funnly enough the old CM9 does boot - and every thing works except the phone.
The latest CM10 does every thing I want (I can live with out the camera) BUT I can't receive calls, the phone app crashes. (But I can MAKE calls!).
This is on GSM BTW, not CDMA where I live.
So i'm busted back down to the 'stock' OS so I can use my phone as a phone
And as a new XDA user I can't post my bug report in the developer thread.
Click to expand...
Click to collapse
Is the issue you're having that when you're speaking to people on the phone you can't hear anything and they can't hear you? Cause on CM9 there should be no issues with using it as a phone as long as you don't enable bluetooth ever or use buttons on a headset connected to your phone. I haven't tried CM10 yet so I wouldn't know too much about that. Just for some extra info to save your time do not flash Liberty or Eclipse, they don't seem to work. The newest Maverick works fine.
matthewgeier said:
SS3 can be un-installed pretty easily. Boot your 'stock' OS, then use the SS3 app to remove the 'hijack' and then reboot again. No SS3. Just remember to do it from the 'stock' OS and not one of the others.
Don't do what I did with SS2 - from a non stock OS, remove SS and reboot. Ended up with a phone that never finished booting before it rebooted. Fortunately the emergency recovery mode built into the phone worked to recover it.
Click to expand...
Click to collapse
I was going to try from the stock.
I am much more familiar with clockworkmod.
Anyway, thank you for the advice
Sent from my XT860 using xda app-developers app
I have been running Android on the TouchPad since the cm7 days and have gone through plenty of ROMS. Unfortunately though, I tried to update TWRP to 2.3 and also change over to a new CM9 ROM. Now if I try to get into TWRP or Android I get a boot loop. I can still get into WebOS just fine though.
Is there a simple fix for this? In my reading/searching I've heard horror stories of just running WebOS Doctor. Can I just do an Acmeuninstall and do acmeinstall?
newbk said:
I have been running Android on the TouchPad since the cm7 days and have gone through plenty of ROMS. Unfortunately though, I tried to update TWRP to 2.3 and also change over to a new CM9 ROM. Now if I try to get into TWRP or Android I get a boot loop. I can still get into WebOS just fine though.
Is there a simple fix for this? In my reading/searching I've heard horror stories of just running WebOS Doctor. Can I just do an Acmeuninstall and do acmeinstall?
Click to expand...
Click to collapse
You'll have to do an ACMEUninstall, then reinstall. I did the same thing when the fault TWRP update came out. And thanks to wwjoshdew, I got it all fixed.
I guess that's okay if you have a recent nandroid backup. Which I didn't *sad face*
Anyways, that's all you need to do.
Sent from Mr Z's HP Touchpad
Thanks for the reply. Acmeuninstall it is.
*UPDATE* Alright, dang thing isn't being recognized in webOS recovery. I guess I am going to have to really start over again.
Sent from my One X using xda app-developers app