Database Info

Trouble booting into cyanogen -PLEASE HELP-

Okay, so I have installed cm on 3 phones so far, and thought I had it down. Apperently not.
I flashed the .nbh, used upgrademyg1.com/root.apk, and attempted to install the latest cyanogen. Upon doing so, the phone would hang at the g1 logo. I attempted wiping and repeating to no avail. Thinking perhaps I had corrupted files, I redownloaded cm, with the same results. I can enter recovery. This is not my phone, and would be very appreciative of any help.
Thanks!
-
EDIT: Did everything over again and worked fine - thanks guys!

[RESOLVED] D2G/ClockworkMod Issues

I'm quickly finding the D2G is the least supported of the Droid devices and have the feeling I should have just bought the D2. It's been a bear trying to get information on this phone, let alone any decent ROMs that are working. That said I've got some issues with flashing backups, so here's the details.
Droid 2 Global
- CM7.1 (DROID2WE version) installed.
- Droid 2 Bootstrapper 1.0.0.5
- Clockwork Mod 5.0.2.3
First off, all the online documentation, including CM's site that CWM can be loaded by: "Hold the X key on the keyboard & the Power button until the device boots to the recovery." is incorrect. Doing so pulls up the PHONE recovery; the best way to get CWM to boot is to wait until the "M" logo comes up and the backlight on the screen turns off, then pressing and holding the power button for 5-10 seconds.
Now, I've tried both entering into recovery from ROM Manager, then creating a back up and rebooting into CWM recovery, then creating a backup. In both instances, the recovery will not restore; each and every time I've tried, I get this error: "Error while formatting /system". Keep in mind that I did NOT change the name of the backup (which I'm told can cause this error).
Supposedly, according to ROM Manager's page on the Market, the latest update was supposed to resolve the error/restore problem, but I've flashed 5.0.2.3 several times with no avail. I emailed Koush, but haven't received a response. To add to the issue, I haven't been able to get any other ROM to flash to the phone, like Liberty 3, for example, unless I flash SBF back to 2.4.330; it's almost like the phone doesn't like dealing with more than one ROM.
Anyone know what I'm doing wrong? I can't find anyone else with the same issues in a finite post and certainly no wikis to explain the matter. I have an OG Droid that doesn't have any of these problems so I assume this is related to the D2G and not because I'm doing something wrong.
**EDIT** Scroll to last post for the resolution.

D2G has a locked bootloader. The custom ROMs are made for a certain kernel. A GB-based ROM won't load on the 2.4.x base, and vice versa, a Froyo ROM won't start on the 4.5.x base.
To install CWM, you need to use Droid 2 Recovery Bootstrap from the Market. With stock ROMs booting into CWM is only possible by first booting into the OS, and then choosing Reboot Recovery in the Droid 2 Bootstrap Recovery app you installed before.
(I have never used ROM Manager because it's not really supposed to work well with the D2G.)
Also, it's worth noting that the “official” CM7.1 ROM is based on the Froyo kernel from 2.4.x firmware.

I've got the Droid 2 Recovery Bootstrap installed. But that still doesn't explain why all the videos and people I see online can switch in between ROMs on other phones, but it's so hard on the D2G, or that I can't get a backup to install properly.
I've read online that using the Droid 2 Recovery Bootstrap to reboot into recovery isn't advised; can anyone confirm?

It's not advised for CM7 and MIUI; those have their own recovery access methods, and CWM comes preinstalled. In CM7, you have to long press the power button, tap “Reboot”, and choose “Recovery” from the reboot menu.
On the most current (ICS-based) MIUI, you have to use the boot menu (press the Volume Down button during power on when the notification LED turns blue while the red Motorola logo is still displayed).
On stock firmware, however, the only way to access CWM is using koush's Droid 2 Recovery Bootstrap and its Reboot Recovery option.
For most other phones, you just replace the stock recovery with CWM, and that gives you the same version of CWM whenever you boot into it.
On Motorola phones with locked bootloaders, CWM versions might differ between different ROMs, because CWM is installed as just another system component with the ROM itself, not outside the ROM inside the boot/recovery partition.
I am, however, unsure why are there such issues for you with backup and restore; I was able to use backup and restore on multiple occasions, and last time I did it was just 2 days ago when I switched between MIUI and stock about 7 times without resorting to SBF even once.

I thought the first few times it didn't 'restore' was because I installed CM7 incorrectly or that I didn't install the bootstrap correctly, but I've SBFd and installed CM7 at least 4 times now and I've never been able to restore; every time I do, I get the 'Error while formatting /system' message.
I really hope I'm just doing this wrong (though I don't see how) and someone can steer me in the right direction.

Wipe data/ cache?
If u use rom manager, go recovery via rom manager

I've done that every time, including wiping the cache partition AND Dalvik under 'advanced'. I found out it was the CM7 version I had installed, which was the 'stable' version that installs over Froyo. It was messing up all sorts of things. I installed one of the RevNightlies over the Gingerbread OTA and most of my problems resolved. I've still had a few instances of a backup not restoring right though... is that a common issue?

**EDIT**
Problem solved, thanks to the guys over @ Rootzwiki. If you have the D2G, you need to flash CWM for the Droid X (2nd-init). I did and backups/restores are working perfectly.
This is a HUGE issue, IMO. There's zero documentation on CWM online, so hopefully people will see this thread if they encounter the same issues I did.

beepea206 said:
**EDIT**
Problem solved, thanks to the guys over @ Rootzwiki. If you have the D2G, you need to flash CWM for the Droid X (2nd-init). I did and backups/restores are working perfectly.
This is a HUGE issue, IMO. There's zero documentation on CWM online, so hopefully people will see this thread if they encounter the same issues I did.
Click to expand...
Click to collapse
I was also having this issue. Thank you for doing the research!
It's pretty frustrating because in ROM Manager, there's a Droid 2 Global option which you would think would be the obvious choice. Apparently D2G's really need DX-2ndInit.
I'm in DX-2ndInit Recovery on my D2G and it's actually doing functions instead of pretending. It's happily restoring a Nandroid backup that I made under the old original version of CWM that the D2Bootstrapper installed.
Edit: Nandroid Restore worked perfectly! All's going very well now and my phone is now running on AT&T on a GoPhone SIM. Looks like it can even jump on HSDPA!

[Q] NexusS (i9020T) hard bricked, at which step did I go wrong?

Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.

I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk

I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA

Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.

Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.

I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though

I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).

I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.

[Q] MZ604 won't boot after installing Wingray ROM

I have been running CWM recovery and installing Wingray nightlies on my MZ604 without any problem for more than a year. A couple of days ago I flashed what I think was a partially downloaded ROM. This soft bricked my Xoom (somewhat unsurprisingly). I ended up in a boot loop so I used this method http://www.xoomforums.com/forum/motorola-xoom-development/18743-how-flash-sbf-rsd-method.html to get out of it.
That worked fine leaving me with a stock Xoom running 3.1.
I then unlocked the bootloader and flashed CWM Touch using adb. I then booted into recovery and flashed the universal Xoom root from here http://forum.xda-developers.com/showthread.php?t=1242241.
Again, this worked fine so now I had what appeared to be a fully functional Xoom running CWM Touch and 3.1. So far, so good.
The final step was to install a recent ROM so I booted into recovery again, flashed the latest Wingray nighly and the GApps package as I have done on numerous occasions (after doing a factory reset and wiping the cache and the Dalvik cache). This appeared to work just as it has always done but now my Xoom just sits at the M logo and nothing else happens. I can still boot into CWM Touch but my Xoom won't get past the M logo in normal boot.
Since everything seemed to work exactly as I would expect right up to the final boot, I'm somewhat mystified as to what is wrong. Can anyone give me any suggestions as to what to do next?

Now I can actually help you. I saw this a day ago but did not respond yet because I did not test my method.
It's been stated by a few in the eos 4 wingray thread that nightlies 204-205 are TEST builds. Only one person said that but from what everyone else is experiencing this appears to be true. You are not alone mine was bootlooping and never getting past the splash animation either.
You don't need to fix or flash a new recovery. All you have to do is use a lower build such as 203 and you'll be fine. I'm testing some roms right now and they work fine now. I did upgrade to twrp recovery as well.
I'm sorry you went through the whole boot loader process again.
At least it's a simple fix. I'd recommend monitoring the eos4 thread and see when people post about newer builds working. I'm sure 206 will fix everything.
Best of luck.

Thanks for the suggestion but unfortunately it didn't work. I did get past the M logo and the multicoloured splash screen appeared but it just got stuck there.
I tried going back to 203 and that didn't work. I also tried going way back to 155 (with the appropriate Google apps package) and that didn't work either.
I am starting to wonder if there is something about the way I am flashing these that isn't working. I have done it so many times that I am rather baffled as to what is going on this time but I think I shall try flashing using Odin and see if that gets me any further. It's all rather frustrating as I haven't been able to use my Xoom for days now.

I have now fixed this although I am not absolutely sure whether my diagnosis is correct.
By flashing Wingray 203 and a very old GApps package, I got past the splash screen. The Google setup program then crashed but at least it had booted. I then tried 203 and the second most recent GApps package (dating from January I think) and it worked.
My guess is that there is some weird interaction between the most recent versions of Wingray and the most recent GApps package (and possibly other factors) but at least my Xoom now works.

[Q] Stops Booting at Splash Screen in AOSP ROMs

I've been using CM10.1 on this phone pretty much since it's been available and updating nightlies about once a week usually. Typically I use Ktoonsez kernel and also update this regularly. Also I am on the MF1 firmware. So, I'm pretty comfortable with the update process and have done it many times.
The other day I attempted to update to CM10.1 7/8 nightly while also installing a kernel I've never tried before called 'Sultan-kernel-Venturi-r5-USA'. Also completing the update process I rebooted and the phone would not move past the CM loading animation splash screen. After about 10 minutes of this I pulled the battery and rebooted, hoping it was just a hiccup but the same thing happened. After dirty installing various CM10.1 nightly and release versions with various combos of no custom kernel and the KT kernel but nothing would fix the boot issue.
I then attempted to wipe and ended up eventually wiping everything on the phone except the external SD card. Still, I could not get the phone to move past the CM splash screen. I then tried a few other AOSP ROMs with the same issue presenting.
Eventually I installed a TW based ROM and was able to get the phone to boot and and able to at least use my phone now. I've tried a couple time since to do a nandroid backup then try installing CM10.1 again and still nothing changes. I can restore the backup and the TW ROM works fine again.
Any ideas on what could have happened to cause this or anything else I can try to get AOSP ROMs working on my phone again?

I would say Odin back to 4.0.4 stock, do the OTA's, reroot with the one click root in the developer section, and it should work.
Sent from my SCH-I535 using xda app-developers app

I did get this figured out. Somehow my EFS partition was wiped. TW based ROMs would actually boot but displayed a 'Factory Mode' warning on startup. AOSP ROMs would not finish booting at all. After restoring EFS from backup everything started working again.