Related
so i went through the instructions on instaklling the tranquility rom, well after installing all i got was the motorola boot, nothing else, so i restarted the phone after about 10 min, and still nothing, so i reboot into recovery, and wiped the phone, well its still only showing the motorola logo, any suggestions?
Same thing happend to me
Sent from my DROIDX using XDA App
oxidant11 said:
so i went through the instructions on instaklling the tranquility rom, well after installing all i got was the motorola boot, nothing else, so i restarted the phone after about 10 min, and still nothing, so i reboot into recovery, and wiped the phone, well its still only showing the motorola logo, any suggestions?
Click to expand...
Click to collapse
Boot into recovery and load one of your backups. If you don't have backups, then you just learned why you need them. Of course, there are people who have uploaded nandroid backups to this site and others, find one of them, move it to your sdcard, boot into recovery, and install it.
If all this fails, then just .sbf. It doesn't take forever, and you can make a nice clean stock 2.2 backup after you root and then upgrade.
What OS are you running? Have you tried to SBF your phone back to factory?
Im guessing its 2.2 only
Sent from my DROIDX using XDA App
Yeah i got it back by doing spf. And then reloaded a backup, but i could never get into clockwork, what do u do yo get into clockwork because the only recovery i was able to get into was the recovery that comes with the phone, just would like to know.
Sent from my DROIDX using XDA App
The same thing happened to me trying to update using the update.zip. Installs everything normally but when it comes to booting it simply stops at the motorola logo, then if you reboot it several times taking the battery out it boots into the system.
Doesn't sound like your rooted? Have to be rooted to use Clockwork.
If you are rooted might try reinstalling the Bootstrap Recovery.
Would definitely suggest doing an SBF on the phone. The guides here are a little unorganized, so I wrote up a nice one below. Includes everything including the SBF file needed for flashing.
http://destdroid.com/showthread.php?18-How-to-Flash-2.1-(SBF)
Need help! My phone was rooted using the Easy Root process, all was peachy until I decided to try the latest leak of 2.2. Didn't work, got stuck at the M logo and could only get the bootloader screen up. I thought it was bricked but after searching high and low through the blogosphere got to this post. Now I've done the sbf as suggested, but when I try to do the Easy Root again, nothing happens. Any suggestions? I would like to root again so I can access the backup from my sd card and get my phone back to where I had it b/f. HELP!
I tried to use SuperOneClick to root my phone and it seemed to work. The program came back saying I successfully rooted my phone.
I then went to ClockworkMod to install cyanogen and clicked on the appropriate boxes to begin the download process for cyanogen 6.0 stable mod and ran it.
My phone rebooted and started to run some scripts.
Now, the phone just reboots to the green mytouch screen and continues to loop like that and I have no idea what to do.
I can get into fastboot on the mt3g and when I do, my pc makes the sound that states that the phone is connected but when I try to get into the mytouch, using adb, my pc cant access it but when I plug up my G2, I can see the serial number and such showing that it is connected.
I tried to follow the fastboot driver installation page but it didn't seem to work.
Bottom line is I would really enjoy a functional MT3G in either the regular form or cyanogen (which is why im in this predicament now )
For the the record,
I was running 1.6 but got the OTA update for 2.2 before I ended up blowing up my phone.
Thanks for reading this and any aid would be greatly appreciated.
UPDATED:
I found something called SAPPIMG.NBH that allowed me load Android 1.5 onto my phone. I now am back to a functioning device but still, I am super stuck on trying to get cyanogen onto my device. Any helpful hints? From what you read above, did I miss something?
Thanks again.
... Sadness... I have been bashing my face against this mt3g and haven't been able to get cyanogenmod on this phone for the life of me. I have tried all of the builds from 5.08 up to RC1 of 6.10 and I just get the infinite loop at the cyanogen boot up screen. I even tried to flash 2.23.XXXX radio to see if it gets past the boot loop and it does not. Anybody have any insights into my issue?
Thanks,
You must go into recovery mode(boot up by holding down home + power). That will get you to Clockworkmod recovery(I am assuming since you said you downloaded using Clockwork app). From there you need to wipe cache, and anything else you can wipe. Then try installing Cyanogenmod after that. Without wiping the there is not enough space to install and it causes a bootloop.
I'm in the same boat, I'm stuck in a boot loop and I cannot get any ROM to fully load in. I'm using clockwork recovery Radio 2.22 32B.
I tried wiping everything but that still doesnt seem to work. I noticed when I try wiping Davlik cache I dont see any message on the bottom. I thought it would normally give me some sort of message stating that it is wiping davlik or something so maybe it isnt actually wiping it?
Is there some other way to make sure davlik is wiped? Or something else I can do. I just want the phone to boot up at this point. I can get into recovery but thats it.
I know I shouldve done a backup but dumb me was such in a rush I completely forgot, I know im a idiot...
Het I found that same .img file and also reverted back to 1.5 then just went up to 2.2 not sure what was wrong but Rom I put on just went into a boot loop. Maybe it was clockwork recovery.
Sent from my ADR6300 using XDA App
the padawan becomes the master... Sort of...
The problem is that you cannot go directly to 2.2 from 1.5. You have to do the incremental upgrades that take you from 1.5 to 1.6 then 1.6 to 2.2
Hey guys, first time poster long time lurker here lol, Anyways, today I rooted my EVO via the new Unrevoked version, everything went smooth, flashed Cyanogen from Rom Manager, all was good but I noticed maps/market were missing. I started messing with the phone to the point where is now sitting on the white htc evo 4g loader screen, and it wont go past that.
I have access to the hboot screen but aside from that that's it. I've tried pretty much all the options in recovery mode to no avail. I believe my problem is that I deleted the OS and my phone has nothing to boot to.
Any help will be greatly appreciated
Some info about the phone:
Hardware version 0003
2.15.00.11.19
3.70.651.1
Have you tried re-flashing the ROM? Or a different one? Or re-downloading the same one to make sure it didn't get corrupted? Have you done a full wipe (cache and data)?
If you can get into recovery, it usually is possible to get back in business somehow.
Try getting into recovery from the hboot screen. Then wipe everything twice and then reflash your rom.
Default
wiped everything and rom keeps giving me "intallation aborted"
here's what it says:
Copying files...
E:Can't symlink /system/xbin/zcip
E: Failure at line 64
symlink busybox SYSTEM:xbin/zcip
Installation aborted.
Lolwut... You shoukd be doing it in recovery...
I was doing it in the ClockwordMod Recovery, but now it wont even let me go into recovery, I just get a phone with a red triangle
im also an android noob and was in your same boat...this is what i did. i downloaded an ruu that was stock but left the root open. its a program that u can run on your pc that will program a stock rom to ur fone...i went into recovery on the fone, hit the fast boot option, connected the fone to the pc and the pc picked it up as "my htc". at that point i ran the ruu and that booted my fone into a stock rom. after that i reinstalled clockworkmod and uploaded a backup i had made w it...now im good..hope this helps
i think this is what i have to do.. im on the same problem and also a noob at this.. i have been banging my head to my desk all night lost out on major sleep.. lol this has to help.. any 1 have the link to the RUU stock?? thx in advance.. and are there any diff tips for linux ubuntu users??
Ok, so I updated from stock, using official update phone rebooted and stayed at samsung screen forever it kept blinking and vibrating. Pulled battery, tried restarting it goes samsung loading bar -> VM welcome -> flashing/vibrating samsung screen.....I can get into recovery AND download mode. Tried clearing cache, factory reset, and updating again, but still gets stuck at samsung screen. I am desperate guys I really need help, I am going on a LONG road trip this weekend and need my phone so ANY help would really be appreciated. THANKS!
When u say update do u mean u went from ex. 2.1 to 2.2.... android that is? U should elaborate a hit more, if what I mentioned is the case then revert back to the ROM prior to the update. If u give more info I may be able to help from my personal experiences
Sent from my HTC HD2 using XDA App
Yes used official update went from 2.1 (stock) to 2.2 as the update finished, it got stuck in a sort of boot cycle, stuck at a samsung screen keeps flashing samsung logo, and vibrating. wont fully boot
OK, I saw on my facebook page samsung intercept page. Mediafire link to download update.zip file,has anyone tried this. Will this work,if it bricks my phone i will be pissed...
There's always the chance that a phone can get bricked, no mater what ...even from an 'official' update from your service provider. With that said, however, I've downloaded the Virgin Mobile 2.2 Froyo update file that's floating around and it installed no problem on my phone.
For the first poster ....I believe that the stock recovery is necessary for the VM 2.2 update to work. I won't swear on that though.
Here's what I did. Downloaded the 2.2 VM Froyo update to my laptop. Renamed it 'update.zip'. Copied it to the root of my sdcard on my Intercept via bluetooth. Booted into recovery mode and applied the update. Twiddled my thumbs while it updated itself from recovery and then rebooted....and the reboot takes a while, maybe 5 minutes. Presto ...2.2 Froyo.
creativenate88 said:
Ok, so I updated from stock, using official update phone rebooted and stayed at samsung screen forever it kept blinking and vibrating. Pulled battery, tried restarting it goes samsung loading bar -> VM welcome -> flashing/vibrating samsung screen.....I can get into recovery AND download mode. Tried clearing cache, factory reset, and updating again, but still gets stuck at samsung screen. I am desperate guys I really need help, I am going on a LONG road trip this weekend and need my phone so ANY help would really be appreciated. THANKS!
Click to expand...
Click to collapse
I think that you didn't wait long enough...as the reboot takes a looooong time, maybe 5 minutes or more at least. Patience is a virtue.
Okay guys,im new here. I installed VM Froyo 2.2 update.zip,it seems to work fine. A bit slow but its still booting up. I installed stock rom,stock kernal, and update.zip,in that order. And backup works too,wiped dalvik cashe to. I like this forum its more informative,will let yall know more later. Thanks.
ajones23 said:
Okay guys,im new here. I installed VM Froyo 2.2 update.zip,it seems to work fine. A bit slow but its still booting up. I installed stock rom,stock kernal, and update.zip,in that order. And backup works too,wiped dalvik cashe to. I like this forum its more informative,will let yall know more later. Thanks.
Click to expand...
Click to collapse
You're making this way to convoluted. All that one needs to do when updating from stock 2.1 on the VM Intercept is to download the (official unofficial) update file, rename it to 'update.zip' on the root of the sdcard, boot into recovery, and apply the update. That's it. It installs Froyo and the new radio, etc, itself...all from the update.zip. No need to mess with kernels and recovery or wipe anything ....except one's own azz if they go take a chit while waiting for it to reboot. In fact, when I updated it even kept all of my 2.1 widgets and icons and imported them into Froyo ...I didn't need to do a thing.
Oh, I see ....you had to convert your Intercept back to 'stock' first. Nevermind...
Yes, i did i downloaded stock rom,stock kernal and stock recovery all .zip. Put stock.zips in sdx/zip folder and update.zip 2.2 in root on sdcard. Installed all three wiped dalvik cashe rebooted each time in custom recvery. When i got to stk rec. rebooted to stock rec. Ran update.zip 2.2 may take a while but it booted no problems.
Can u get the phone into download more with any button sequences, YouTube it if u don't know what i mean(mobiletechvideos) then y will need to use odin to use tp download an official Samsung Rom.... PM if u need help
Sent from my SGH-T959 using XDA App
hey people first post longtime reader any way i got my samsung intercept update
just fine saved all adw stuff and everything but i cant root anymore {big up to z4root} anyone can help?
sorry trying to delete my posts.
Love XDA but but for interecpt help Go to SDX forums
So I've been running MIUI 1.8.whatever for a few weeks and finally realized there hadn't been an update in a while. After discovering MIUI move into the 1.9.Xs I downloaded 1.9.16 and proceeded to update via CWM. While updating it told me 1.9.16 runs off the Gingerbread kernel. At that point I got worried since I had been running the Froyo kernel since I rooted my DX.
After the update I told it to reboot and now it gets stuck at the white M logo. I can boot into regular recovery but I CANNOT get my phone to boot into CWM recovery so I can run the backup!
I've tried every button combination with no luck. i've booted into regular recovery and selected reboot having read that it will boot back into CWM recovery. Needless to say that didn't work either. And lastly I tried running RSDLite to SBF the phone to .602 but since the phone can't fully boot up RSDLite doesn't see the phone.
That is where I am at and I seek the help and guidance of you much smarter folks to help me get my phone at minimum to CWM recovery.
PLEASE HELP!!!
Boot the phone into bootloader mode, then SBF.
Sent from my DROIDX using XDA App
I got it into bootloader mode now, but my computer isn't finding the OMAP drivers and the installation keeps failing. How can I get these drivers onto my computer? RSD isn't seeing the phone even in bootloader so these drivers seem to be the key.
You can find the drivers in this thread:
http://forum.xda-developers.com/showthread.php?t=1258599
Sent from my DROIDX using XDA App
I got RSDLite to see the phone. Now when I try to flash it, it makes it all the way to checking the checksums (which all pass) then tries to switch the phone to BP passthrough. It keeps failing to switch the phone to BP passthrough and now my phone will only boot to the Bootloader screen and says Code Corrupt. It'll let me run the flash again but RSDLite keeps failing at that BP passthrough switch.
Thats where i'm at now.
Try a different SBF file. I had problems like this when i tried to SBF once, but once I found the SBF file that works for me, its always worked since. (I've had to SBF like 6 times now haha)
will find an older sbf file and try that. Wil let you know.
Alright we've made progress! I was able to finally get the phone SBF'd to .602. Then I rocked the Pete's Droid Rooting program and all seemed to have gone smoothly... Except I cannot boot into CWM recovery at all! I've ensured ROM Manager has the correct flash for CWM installed, but when I click Reboot into CWM Recovery, it'll reboot normally. So I turned the phone off and held the Home + Power button to boot into regular recovery. I get the ! logo with the green android, but when I hit hte Search button nothing happens.
So now I'm rooted, but can't get to CWM Recovery to install ROMS.
What do you guys think?
Yeah, Reboot into Recovery from ROM Manager doesn't work for me usually either...in fact, I had to go into the Bootstrapper app, install the recovery again, and then hit Reboot Recovery. This is on Apex though, but can't hurt to try it.
Yea I finally got it figured out. Its been so long since I originally rooted my phone I forgot all about D2Bootstrapper. And I didn't read the how-to guide for updating to MIUI 1.9.16 so that was all on me.