My girlfriend's Rezound has a bizarre problem that started a couple days ago; a couple times a day it will randomly reboot into recovery. I was wondering if anyone has seen this happen, and knows of any fixes. Switched to Amon Ra 3.15 from Clockwork Touch.
Second, I'm looking for a stock, de-odexed, rooted GB ROM to flash. She basically wants all the same functionality of stock(including Sense), but I want the ability to install certain mods(power menu, additional settings, etc.). What are your suggestions? She's running rooted, odexed, bone-stock 1.02.605.6. Need to know what's going to be most stable/compatible as I also see a 2.01.605.11 version but have no idea if it's official or a leak.
Sounds like It's trying to install the first ota but keeps failing due to not having the stock recovery
Sent from my ADR6425LVW using Tapatalk 2
Not sure if it's de-odexed but it's the latest GB stock OTA with root - http://www.scottsroms.com/downloads.php?do=file&id=76
Thank Scott for hosting it.
I don't think the stock roms are deodexed but I'm pretty sure Cleanrom 1.7.5 is. It is a cleaned up version of the stock gingerbread rom and is very stable. I used it as my daily driver until I moved to the newer ICS roms. Hope this helps.
p.s. many people seem to be having problems with clockwork so are using amon ra recovery.
+1 on getting rid of CWM. Was causing all kinds of grief for me. Just flashed Amon Ra over it, no problems since then.
Thanks for the responses. I switched to Amon Ra around 2330 last night. At 0045 the phone rebooted into recovery. So I'm thinking it's either the ROM trying to do an OTA update, or a problem with the phone itself. Cleanrom looks nice, but is it Sense or Desense? She loves that stupid weather lockscreen and background(although can't blame her, it's dang purdy) and likes most of what sense has to offer. Tonight I'll switch to the official OTA and boot.img when I'm home and no longer sober. (Because really, who actually does this stuff sober?!)
I on the other hand enjoy the minimal approach of ICS on my Nexus Prime.
UTMorpheus said:
Thanks for the responses. I switched to Amon Ra around 2330 last night. At 0045 the phone rebooted into recovery. So I'm thinking it's either the ROM trying to do an OTA update, or a problem with the phone itself. Cleanrom looks nice, but is it Sense or Desense? She loves that stupid weather lockscreen and background(although can't blame her, it's dang purdy) and likes most of what sense has to offer. Tonight I'll switch to the official OTA and boot.img when I'm home and no longer sober. (Because really, who actually does this stuff sober?!)
I on the other hand enjoy the minimal approach of ICS on my Nexus Prime.
Click to expand...
Click to collapse
CleanRom GB 1.7.5 is Sense 3.5 like stock.
UTMorpheus said:
Thanks for the responses. I switched to Amon Ra around 2330 last night. At 0045 the phone rebooted into recovery. So I'm thinking it's either the ROM trying to do an OTA update, or a problem with the phone itself. Cleanrom looks nice, but is it Sense or Desense? She loves that stupid weather lockscreen and background(although can't blame her, it's dang purdy) and likes most of what sense has to offer. Tonight I'll switch to the official OTA and boot.img when I'm home and no longer sober. (Because really, who actually does this stuff sober?!)
I on the other hand enjoy the minimal approach of ICS on my Nexus Prime.
Click to expand...
Click to collapse
From experience, I don't recommend drunk flashing lol.
This is what I would suggest:
1. Relock the device
2. Run the official OTA 2.xx RUU via your computer. This will guarantee the cleanest possible install of the rom and firmware.
3. Re-Unlock (you can use the same token file)
4. Install AmonRa again
5. Then install the newest cleanrom GBE. It is gingerbread, newest OS version, Sense, clean, stable, fast, has advanced power menu and such.
The RUU I talked about can be found here: http://forum.xda-developers.com/showpost.php?p=22045045&postcount=58
I wouldn't recommend rooting or tinkering with your girlfriends device. If you have a problem, no big deal... fix it. If she has a problem it is a big deal, because its your fault.
what's the easiest way to flash amon-ra over cwm? .. I have the zip on my computer and I'm guessing I just put amon-ra on SD? (then i dont know)
SHIDOOBY said:
what's the easiest way to flash amon-ra over cwm? .. I have the zip on my computer and I'm guessing I just put amon-ra on SD? (then i dont know)
Click to expand...
Click to collapse
You don't flash in recovery. Take the Recovery.IMG and put it in your fastboot folder and when you have your phone connected in fastbootusb pull up your command prompt. Change directory to the folder containing fastboot and the amon ra recovery image and type fastboot flash recovery recovery-ra-vigor-3.15-gnm.img then reboot !
obviously if its zipped unzip and just use the .img, but I really think when you download the zip it is not really zipped it is in .img format already.
Okay, I did those things.. now it says < waiting for device > .. how long does this take or have i done something wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 05:23 PM ---------- Previous post was at 05:08 PM ----------
yeah it didn't work... HEEEEEEEEEEEEEEEEEEELPPP
SHIDOOBY said:
Okay, I did those things.. now it says < waiting for device > .. how long does this take or have i done something wrong?
---------- Post added at 05:23 PM ---------- Previous post was at 05:08 PM ----------
yeah it didn't work... HEEEEEEEEEEEEEEEEEEELPPP
Click to expand...
Click to collapse
If it says waiting for device I don't think you have the HTC drivers installed or your phone isn't in fastboot. It should say fastbootusb in white letters and red background.
Remember your phone needs to be in bootloader then select fastboot.
Sent from my ADR6425LVW using xda premium
It sounds like the advice in the previous post should solve the problem. If not try using CleanFlash. It is a tool developed by the developer of CleanRom that I've used several times when I was too lazy or was having some kind of problem pushing an image. You can search for it here on XDA or find it on Scott's website (scottsroms.com).
Related
Lite'ning ROM v6.1
12/20/2011 - ROM hasn't been updated, but due to some users not having much luck with the included stock modem I've added a CWM flashable UCKK6 modem. I've also added the stock for those that need/want it for some reason. The download links are available at the bottom of this post.
11/27/2011 - Updated with haptic fix (credit to amtrakcn) and Entropy512's latest kernel (11/23/2011). Download link at the bottom has been updated to this one. Enjoy!
11/12/2011 - Updated image with fixed root!
The previous image was almost impossible to get root working. On the surface it was installed, but wouldn't / couldn't gain root access. After many attempts I finally decided to build the port from scratch again. Fixed a couple of file issues, build.prop edits, script tweaks, csc, etc. The result is better WIFI establishment and root that works from install.
This time I didn't use Hellraiser files, but definitely continue to use Entropy512's awesome kernel. No issues with Hellraiser as I've used it to Hellraise other I9100 ROM's without issue, I just didn't need its files in this go around. You should check Hellraiser out. It is an awesome tool.
This ROM is a port of Lite'ning Rom v6.1 XXKH3 found here made for the SGSII I9100. This is a single CWM install of the ROM.
New download link is at the bottom of this post.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credit and thanks to LitePro for his image source, and to Entropy512 for his awesome kernel!
Donations are appreciated, but not required. Thanks is good enough
Save the Zip to your internal SD Card
Boot into CWM
Highly recommended doing a format /data in Mounts and Storage
Do a install zip from sdcard
Point to the downloaded Zip file
Install the Zip package
This CWM package will wipe your cache, system and Davlik-cache for you
Download link: (11/27/2011)
http://www.multiupload.com/74QB78HAI3
Modem downloads (12/20/2011)
UCKK6 Modem
UCKH7 Modem stock
What good is a CWM package if you don't have CWM?
CWM = ClockWork Mod
Note: Your phone needs to be rooted for a non-Odin install. There are many threads in this forum on how to root so I won't get into it here.
Now you need to obtain a kernel that has CWM included. I recommend the latest kernel from Entropy512's thread located here.
You'll want to extract the zImage file out of the Zip and save it on your computer.
If you have the Android SDK installed and working on your computer then save the zImage in its tools directory and then type the following command from this location:
Code:
adb push zImage /sdcard/zImage
Otherwise you'll want to plugin your phone to your computers USB connection and paste the zImage file in the root of your internal SD Card.
Next you need to flash the kernel.
Via ADB (press Enter after each line):
Code:
adb shell
su
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Via a Terminal Emulator installed on your phone (If you don't have one download "Android Terminal Emulator" from the Market and install it. It's free):
Code:
su
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Reboot.
Note that in the above two code examples when you type su you'll get a prompt to allow the "Superuser Request" if its the first time you invoke it from either program.
To boot into CWM in ADB type:
Code:
adb reboot recovery
Or, unplug your USB cable if plugged in, and press and hold vol UP + vol DOWN + Power buttons. Wait until it reboots and you see the Samsung Galaxy S II boot screen and release all 3 buttons. This should place you in your CWM menu.
Doing it this way should keep you from getting an exclamation point on your boot screen which is the main reason why I explained how to do this in this manner. If, by chance, you still get an exclamation point or already had one to begin with the only option I can think of is to use a jig. Not that a jig isn't a good thing to have anyways. Any ROM you flash from within CWM will not be added to your Custom Image count and will not produce the annoying exclamation point on the boot screen.
Absolutely first thing you want to do is boot into CWM.
As of this writing, press the Home button to choose an entry and press your Power button or the back button to go back to the previous screen.
Go to: backup and restore
Choose Backup
This will take a few minutes, but is well worth it. Now if you ever mess up your install you can always boot into CWM and restore the image you backed up. This, however, doesn't protect you from flashing bad bootloaders so word to the wise... DO NOT FLASH BOOTLOADERS!!! At this point and time there is no need to.
Reserved for awesomeness
_______________________
Fresh Install:
Home button has a bit more of a delay to it. - Fixed
Quite a few services running.
Broke my Root. - Fixed
I would recommend someone putting more than the 10 minutes I did into this ROM.
Going back to UnNamed, dont have to the time to mess around too much. Getting late, and Skyrim is coming...
I wont be using this rom but wanted to give serious props for getting this working! Awesome job to everyone involved!!
Sent from my SAMSUNG-SGH-I777 using XDA App
Sweet... wouldn't mind giving it a shot. Thanks for sharing
Is this a sign that we'll be seeing more OGSGS2 ROMs coming over? How hard was it to port?
Sent from my SAMSUNG-SGH-I777 using XDA App
i was thinking about installing this but ive read that the dev who started this, LITEPRO, hasnt updated the rom for a while now. abandoned? will we get new updates?
simpl3lang said:
i was thinking about installing this but ive read that the dev who started this, LITEPRO, hasnt updated the rom for a while now. abandoned? will we get new updates?
Click to expand...
Click to collapse
While I cannot speak for LITEPRO, his last post on XDA being this past August... it's possible that he got burnt out (easy to do) and taking an extended break. I believe we'll see him again. Wherever he is now I hope he's doing well.
As far as updates I will do what I can to add updates as they come about and they provide a benefit to the ROM.
Thanks !!!
Cozmo1 said:
While I cannot speak for LITEPRO, his last post on XDA being this past August... it's possible that he got burnt out (easy to do) and taking an extended break. I believe we'll see him again. Wherever he is now I hope he's doing well.
As far as updates I will do what I can to add updates as they come about and they provide a benefit to the ROM.
Click to expand...
Click to collapse
backing up right now to have a go at it.
when you get the time have a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1334124
it seems someone has continued to tweak and update the litening rom. what do you think?
downloading now. Reporting back soon.
I was waiting for something like this to come along
Sent from my SAMSUNG-SGH-I777 using XDA App
cwc3 said:
Fresh Install:
Home button has a bit more of a delay to it.
Quite a few services running.
Broke my Root.
Click to expand...
Click to collapse
While initially the home button does have a little lag to it didn't seem to persist after using it a little bit. However, I do recall reading that there was a fix for the issue. I will look into it.
It does have many processes listed in the background, but I didn't see it being different than a standard ROM install with a basic selection of apps. Mine currently has 59 in the background, but only 4 in actual use. It's how Linux based systems handle processes and it tends to do a real good job which is why task killers are frowned upon. So I tend to not be concerned with background processes, but more with how the battery consumption is on the ROM. It was rather good in that.
I installed this ROM several times in my testings of it and never had my root broken. I could've just been lucky. It comes with Entropy's daily driver kernel which includes root injected in initramfs as well as CWM. Still, strange things can happen. Did you wipe /data before installing, by chance?
Yea, wiped data first. Its all good. I probably should of flashed twice to be sure. If Skyrim wasn't coming out tomorrow, I would tweak this ROM to my liking then give it a proper test.
For the brief 10 minutes I used it, seemed fairly nice. Only thing that went wrong was the root, which would of been a quick fix I'm sure. I will come back at it in a couple years when I am bored of Skyrim.
cwc3 said:
Yea, wiped data first. Its all good. I probably should of flashed twice to be sure. If Skyrim wasn't coming out tomorrow, I would tweak this ROM to my liking then give it a proper test.
For the brief 10 minutes I used it, seemed fairly nice. Only thing that went wrong was the root, which would of been a quick fix I'm sure. I will come back at it in a couple years when I am bored of Skyrim.
Click to expand...
Click to collapse
LoL - I hear you. I can guarantee you that once Diablo 3 comes out my time on XDA will be severely cut
root not working here. great rom though. fast and smooth.
about to test. if you lost root, wouldn't installing entropy512 kernel fix it? let me try that for you
you think you could fix the home button haptic? its not a big deal but itd be nice lol
Also wifi wasn't working for me so I decided to nandroid back to UnNamed for now
confirming update of kernel bb and su did not give root. I was wrong, but will check back!
This is interesting. On the surface it looks to be rooted, but when you actually try using root capabilities it doesn't work. Not even when flashing a new rooted kernel. This will need some investigation to provide a fix. Will work on it tomorrow after work.
First off, I wanted to say that the XDA developers "Video for Noobs" was absolutely hillarious and informative at the same time. Great idea. NOW, on to the source of my infinite frustration.
I decided today that I wanted to root my Galaxy Vibrant that I got yesterday, and install a ICS ROM on it. I had no clue how to do anything as regards this, but I'm fluent with computers and I have a very good knowledge of Android in general. I don't know details on the coding side, but I have a good base of background knowledge. So, I started work around 3:00EST today. I've been working constantly SINCE THAT TIME (now 9:30 EST) trying to get root and install ClockWork Mod. But it will not work.
So, the details. I'm running Windows 8, 64-bit by the way. The first thing I tried, after looking up many guides and tutorials, was to install the Samsung USB Drivers and to get root and ROM manager. After some trial and error using SuperOneClick (2.3.3.0), I achieved root access, but I didn't have SU so I installed the app from the Play store. Then, I tried installing ClockWork Recovery from the ROM Manager, and I tried rebooting into CWR through the ROM manager. No dice, I got the standard "Android System Recovery" software. e3 variant (I've read up a bit on the different types, but I'm not too fluent in them yet). I tried the "Reinstall Packages" option so I could flash CWR, but that led to a certification error. No clue how to get around it.
I then figured out that I needed to have the DDM (Dalvik Debug Monitor) running to get proper root access. So I did that, and tried EVERYTHING again. I have wiped my phone about 5 times by this time. I went through a bunch of crap and eventually got it so that I CWR would TRY to flash once I got into the recovery screen. Basically, when I hit the "Reinstall Packages" button it goes through a few steps, a progress bar appears, and it says something along the lines of "Replacing stock recovery manager with ClockWork recovery". After just over a second of this, the phone restarts into the plain old recovery screen with no progress whatsoever.
I have ClockWorkMod 2.5.1.2 downloaded through ROM manager.
I have left it alone at this point.
I've tried using ADB, but there are no real guides that are up-to-date with the latest software and manually flashing an image from ClockWork Mod doesn't seem to work as they don't have image files anymore, just .zips with a bunch of single files and folders. I have no clue about Odin.
The ROM I'm trying to flash is Ice Cream Zenwich, which looks to be pretty promising. But I haven't even been able to get any kind of recovery manager working, so that doesn't help much.
Link: (add www) rootzwiki.com/topic/21742-romimm76i-iczen-rc18-the-hammer-of-buddha-5-26-12-deficient-development
I have tried manually flashing, but I haven't really made any progress in that area. I've tried ABD, I've tried CWR, and nothing I've been able to think of seems to work. SO I NEED HELP!
Just to state my system specs and software:
PC:
Windows 8 Consumer Preview, 64-bit
Android SDK and tools
Java JDK 6u29 ]______will this cause problems? Version 6 and 7 Java?
JRE Version 7 ]
Ice Cream Zenwich ROM (RC 1.8)
Phone:
Samsung Galaxy Vibrant, running Android 2.2
ROM Manager, ClockWork Mod Recovery 2.5.1.2 Downloaded
SuperUser
Titanium Backup
Root Tester
Absolutely ANY help would be insanely appreciated, I just can't work at this anymore.
Thanks in advance!
I know this is a bit early to bump, but I really need help with this still. Haven't made any progress.
Sent from my Vibrant using XDA
what instructions were you following? I believe Woodrube's instructions go over this, I'll check though. Here!
Also, get the AIO toolbox. Everything you need in one program. Very convenient. It's also linked in the instructions above. Flashing to stock, rooting, CWR, all just by clicking a button on your computer. AIO
If you get stuck again then just odin lindroid from http://forum.xda-developers.com/showthread.php?t=1057187&highlight=lindroid
It will give you everything ready for flashing ICS roms
dpaul007 said:
what instructions were you following? I believe Woodrube's instructions go over this, I'll check though. Here!
Also, get the AIO toolbox. Everything you need in one program. Very convenient. It's also linked in the instructions above. Flashing to stock, rooting, CWR, all just by clicking a button on your computer. AIO
Click to expand...
Click to collapse
Yep. I do believe all this is covered in there. Hardest part is finding the files (but they are out there). My guide's OP is short but comprehensive, so you should be able to go back to Eclair to ICS in under an hour (and that is a heavy handed time estimate). I can usually get it from 2.1 to ICZen in about 20 minutes and most of that time is waiting for the ROMs to settle down before I flash over them. Oh and since I have used GB bootloaders for some time, I am reminded of my Noob-i-ness when I have to get into Recovery on a Froyo bootloader. Last time it took me about 8 times to get there.
I understand it is frustrating, believe me I do, but it is all out there for the taking. Your OP is a good example of trying to dagnose a problem, not getting the answer and putting out as much info as you can to get help. Nice job on that.
Thanks for all the help
dpaul007 said:
what instructions were you following? I believe Woodrube's instructions go over this, I'll check though. Here!
Also, get the AIO toolbox. Everything you need in one program. Very convenient. It's also linked in the instructions above. Flashing to stock, rooting, CWR, all just by clicking a button on your computer. AIO
Click to expand...
Click to collapse
Thanks for that, I'll definitely take a look at this. I was pretty sure I was overthinking things, I think this might be a simpler solution.
I was following general instructions from various places (the ICZen page, etc), and at first I was following guides from all over the place. After I got my legs, this was the main rooting guide that I followed:
(add www) forum.xda-developers.com/showthread.php?t=1438478
And I was loosely following this guide for the ROM manager, CWR, etc:
(add www) androidauthority.com/vibrant-t959-ice-cream-sandwich-install-56729/
Woodrube said:
Yep. I do believe all this is covered in there. Hardest part is finding the files (but they are out there). My guide's OP is short but comprehensive, so you should be able to go back to Eclair to ICS in under an hour (and that is a heavy handed time estimate). I can usually get it from 2.1 to ICZen in about 20 minutes and most of that time is waiting for the ROMs to settle down before I flash over them. Oh and since I have used GB bootloaders for some time, I am reminded of my Noob-i-ness when I have to get into Recovery on a Froyo bootloader. Last time it took me about 8 times to get there.
I understand it is frustrating, believe me I do, but it is all out there for the taking. Your OP is a good example of trying to dagnose a problem, not getting the answer and putting out as much info as you can to get help. Nice job on that.
Click to expand...
Click to collapse
Thanks a lot for that, it does help a lot. I'm taking a look at that guide right now. Hopefully I can get through it without as much trouble as I had this time around (and without as much frustration). Also, I appreciate it that the author of the guide in question took the time to post here. Thanks again.
And in response to your comment on my OP, yes - I don't like it myself when people leave out information that may be critical to diagnosing their issue. It just prolongs things, makes the situation difficult, and its simply annoying. So I didn't want to be that guy. It looks like it worked!
mohitmoudgil said:
If you get stuck again then just odin lindroid from http://forum.xda-developers.com/showthread.php?t=1057187&highlight=lindroid
It will give you everything ready for flashing ICS roms
Click to expand...
Click to collapse
Thanks, if I do get stuck again I'll give this a try.
I appreciate all the help. I'll report on my progress soon. Hopefully, my next post will be about how happy I am to have ICS (or ICZen, rather) on my Vibrant!
Im probably late to the party but the way i get CWM is simply that i run the recovery 3e to 2e batch file (google 3e to 2e recovery) from my computer and then flash the CWM update.zip (its inside the clockworkmod folder ththat should be in the root of your sd) using reinstall packages, sometimes twice.. this should take you to CWM mod, after which i can flash the root package pretty easily
sent from the xda app on my android smartphone.
CWalkop said:
Also, I appreciate it that the author of the guide in question took the time to post here. Thanks again.
...Snip...
Hopefully, my next post will be about how happy I am to have ICS (or ICZen, rather) on my Vibrant!
Click to expand...
Click to collapse
No problems man. I am usually scanning the General and Q&A sections during the days to see if anyone needs help. At night I turn it over to others to troubleshoot.
I do have to tell you about a certain caveat in the ICZen flashing that is different than the others and almost everyone misses it on the first time they try.
Steps
-Download ICZen and place it on your internal sd
-Reboot to Clockwork Recovery
-Perform a wipedata/factory reset <---You must do this
-Go to mounts and storage and format the system partition
-Flash your downloaded ICZ rom file
-From the main menu of recovery, perform a wipedata/factory reset again <---AND this
-Reboot
-On bootup, give it a few minutes to settle in, reboot and use as normal.
-Enjoy your ICZen!
Click to expand...
Click to collapse
Most of the other ICS ROMs only have you Factory Reset once but you'll need to do it twice in ICZen, otherwise you'll get stuck in a bootloop.
W00T
Good timing with that post. I just came back here to report that I had got Odin, CyanogenMod, a Gingerbread Bootloader, and flashed back to 2.1, flashed Cyanogen mod and was JUST starting my ICZen flash. Interesting how booting into Recovery is built right into Cyanogenmod, I like that.
Anyway, I just performed a factory reset from the prompt that popped up right after I tried to flash ICZen (Deficient Touch Recovery, 5.5.0.4). I remember from the ICZen page that they told you to make SURE you had a CLEAN phone to start from, but I missed the second wipe step. Thanks for reminding me. I'm rebooting now, hopefully this'll work!
Edit: strange, I had to flash the ICZen ROM twice before I could get it to boot! I'm on the ICZen boot page as we speak, here we go...
Thanks for all your help. I'll post screenshots afterwards
CWalkop said:
Good timing with that post. I just came back here to report that I had got Odin, CyanogenMod, a Gingerbread Bootloader, and flashed back to 2.1, flashed Cyanogen mod and was JUST starting my ICZen flash.
Edit: strange, I had to flash the ICZen ROM twice before I could get it to boot! I'm on the ICZen boot page as we speak, here we go...
Click to expand...
Click to collapse
Noticed that you list GB bl's but not that you flashed them. If you did then no worries.
Re: your edit. If you got to the ICZen bootanimation and it still doesn't boot up, try wiping and factory reset again. Should work out after that. Good luck.
Woodrube said:
Noticed that you list GB bl's but not that you flashed them. If you did then no worries.
Click to expand...
Click to collapse
Ah, sorry for the confusion. I did in fact flash the GB bootloader, and it worked fine. I was confused for a bit because I thought I needed to choose a specific bootloader from the page you provided, but then I just chose one and it went through fine.
Re: your edit. If you got to the ICZen bootanimation and it still doesn't boot up, try wiping and factory reset again. Should work out after that. Good luck.
Click to expand...
Click to collapse
That's not exactly what happened; it just rebooted into the recovery manager again after I told it to reboot normally.
But...as you probably garnered from this post, everything worked perfectly after that! I booted into ICZen, setup the phone (no bloatware is nice), and started using it! Its even compatible with some apps that it wasn't before, which is great!
I attached some screenshots. It felt like the right thing to do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*cheers*
Thanks for all the help! You were great. I have over locked a bit; now I'm trying to set up Chainfire 3D so I can run the Tegra apps I bought for my previous tablet (ASUS Transformer, sold to save for the Infinity). I can probably find a guide of some kind online.
Sent from my SGH-T959 using XDA
Kind of random, but I find it really interesting that you can adjust the display color balance on ICZen. That's an absolutely incredible feature; I was actually hoping to find an app that would accomplish this but the built-in control seems to work great! Tweaked to my hearts desire.
Sent from my SGH-T959 using XDA
I noticed that my brother had ICS for his droid razr maxx and so I went about updating my phone so that I could have ICS as well. During the first attempt it downloaded fine, rebooted and started the installation. During the installation though it stopped around 30-40%? ish and rebooted saying the update failed. I have had this problem before and so I thought it was because my phone didn't have some of the applications that It came with from Motorola. I recovered it to my last recovery which I saved with everything still installed but the phone still rooted. The installation didn't work so I figured that I would just factory reset and try it again, thinking the phone would update then.
Phone: Droid razr X912, stock ROM, no root, Superuser is installed but does not work, installed OTA root keeper to check if I had root but didn't work. Bootstrap doesn't work.
Where I am now:
1. Stock ROM
2. factory reset
3. Gingerbread 2.3.6
4. No root and unable to re root
5. Cannot update ICS
Where I am trying to get:
1. Either I would like to get back to one of my recoveries that I made using CMrecovery or
2. Get to ICS.
What I have read so far:
Something about locking the bootloader. Said to use some adb reboot recovery command in a command prompt? I am really new at this so I don't know what this means(should provide somewhat of a idea of how much I know) I can read articles if someone can point me in the right direction
I am unsure what to do in this situation. Thanks.
Edit: Tried Doomlords unrooting script and that didn't work, Says that the phone is in R/O mode most likely (that is my conclusion) from reading a few articles.
Ok...I'm no expert but I can tell you what I would would do and hopefully we can you all fixed up. So you're on stock Gingerbread right? Do you have the stock recovery too or a different one? Anyways try booting into recovery, wipe the cache, do a factory reset/data wipe, clear cache again. Then restart the phone to see if it boots up all good.
Now, do you have the official ICS .211 .zip update file? I'm assuming you do, make sure it's on the "external" SD card. Shut the phone down, and boot back into recovery. Select update.zip from SD card and run the update. Give it plenty of time to run. Sometimes it seems like it is hanging but it's just thinking. Might take in upwards of 10-15 minutes to run through completely so make sure you have a full battery before beginning.
Mine did hang and installation failed. This is actually common when doing a forced update in recovery. Don't worry, all you have to do is force shut it down and repeat the above steps and run the install again. It "should" install fine on the second try, mine did and many others on here too. After it's finished and you're all booted up you should be on the official .211 ICS version.
If you want to root, search for matt's utility for the .211 version (I believe it's the 1.7 version) and simply follow those instructions, works great and don't forget to donate. He's saved lots of us RAZR users. Also, if you want the .215 leaked update, get Voodoo OTA rootkeeper, run that, get the .215 .zip update file from you're external SD card in recovery.
When all is said and done. You should be on the most recent stock .215 ICS version, and rooted. Hope this helps
Edit.. .If this doesn't work, and I don't know if it will, I hope it does, you'll probably have to use RSD to flash a stock image. I think they are .fxz files, not sure. I've never used RSD on my RAZR, only my OG Droid1.
Thanks for the Reply, I do not have the .211 ICS .zip, Though if you or anyone else know where to find it? I do know how to do the force install that you recommended that I do.
http://eclipserom.com/vforum/showth...cial-4-0-4-(211-OTA)-Fastboot-Files-for-XT912
There you go
Thank you. Will try it and let you know if that worked!
Matt's utility (found in the Dev forum) is really all you need. I'm guessing that having bootstrap installed is one of the issues as well.
Oh, I will check that right now while I wait for the ics rom to download, thanks for more options, may try it first if it is all that I need.
You can get the utility at same link I posted earlier..^^^
I just wanted to let you know that I did get it working again with your help! I ended up having to use RDSLite to restore it but its back up and got it working again! Thanks so much guys!
Tried the ics t-mobile leak and worked awesomely for me! (goo.gl/aQuKS) its German but Google translates it brilliantly!
another opportunity is (like I did) installing miui which is officially supported and use Nova launcher if u like.
Nevertheless, T-Mobile leak works like a charm!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT910 Miui V4 using xda premium
kadosEidetic said:
I just wanted to let you know that I did get it working again with your help! I ended up having to use RDSLite to restore it but its back up and got it working again! Thanks so much guys!
Click to expand...
Click to collapse
did you get it re-rooted again?
I was having an issue with the update also. Had to go through an arduous process but finally figured it out.
I have clockwork recovery installed.
my question is
is there *anything special* i need to do to go from this to the new ICS or JB Roms??
thanks in advance!
Yes. Make sure you flash Gingerbread bootloader. There is an easy to follow guide available. Search for Vibrant Custom GB Bootloader on Google and it should take you directly to the thread here.
It's a simple guide to follow, just follow it carefully. *a misstep can hard brick you*
After you have that you can find a suitable 4.0.4 ICS to flash. Just follow the directions in the OP and you should be fine.
Or, you could flash a JB ROM. In that case I would recommend (because I had to) flash cm9 nightly FIRST, then go to JB from there. Would probably make your life easier
As my buddy Woodrube says: read, read, read. When you've read enough, read more.
I still sit back and read about an hours worth of old solved threads and new ones alike on an everyday basis.
Note: if you for choose an ICS ROM, please read the threads titled EU bug, and Encryption Unsuccessful. It may not ever affect you, but you should become familiar with it.
You don't need to flash Gingerbread bootloaders.
theexel said:
You know, everyone always says to go to CM7 then CM10.
I ODIN'ed back to stock today, no idea why, I got bored. xD
Note: Skip steps 1, 3, 4 if you already have a custom recovery, which you do, you're running Bionix and don't want to ODIN back to stock for a complete clean install.
These are the steps I use to go to CM10 coming from stock:
1. ODIN to stock, wipe everything, you know.. clean install.
2. Download all the zips you need. (CM10, JB GAPPS, CM10 FFC support zip, update.zip that has clockworkmod recovery.) and put them on your phone.
3. Reboot into recovery, install 'update.zip' it'll reboot, do it again.
4. It should boot into CWM now, the old version.
5. Flash CM10, it should reboot or get stuck.
6. Boot into recovery (Should be new recovery from now on.), wipe data/factory reset.
7. Boot into recovery, flash twice before rebooting.
8. Reboot system and wait for it to boot up, if it doesn't boot up, flash again.
9. Once it boots, flash GAAPS.
10. Flash CM10 FFC support.
Enjoy?
Click to expand...
Click to collapse
No you don't need GBbl's anymore. Lets just say they are not "required" anymore, but are still "recommended".
OP, I have a ICS install guide in my signature if you need it. Has details about EU bug too.
Woodrube said:
No you don't need GBbl's anymore. Lets just say they are not "required" anymore, but are still "recommended".
OP, I have a ICS install guide in my signature if you need it. Has details about EU bug too.
Click to expand...
Click to collapse
so i need to install CM7 before installing these roms(ICS)? (the guide says skip to the CM7 part). is CM7 required??
if so, how to go about installing the CM7 in place of the Froyo bionix build??
and is there a custom CWR for ICS roms that I need to install?
sorry for the dumb questions. ive been knee deep in my sgs4g and havent kept up with vibrant...
You do not need to flash CM7, people just say it's safer. (Not sure on that one.)
Follow the steps I gave up and skip the ones that I said to, you should be just fine.
theexel said:
You do not need to flash CM7, people just say it's safer. (Not sure on that one.)
Follow the steps I gave up and skip the ones that I said to, you should be just fine.
Click to expand...
Click to collapse
Ive been looking for the JB GAAPS file to dl for vibrant and I cant find it any where
http://goo.im/gapps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
theexel said:
http://goo.im/gapps
Click to expand...
Click to collapse
No wonder I couldnt find it, I was spelling it wrong ffs I feel like a a dip**** now lol
---------- Post added at 11:55 PM ---------- Previous post was at 11:40 PM ----------
Just trying to be thorough here. On step 7 it says "7. Boot into recovery, flash twice before rebooting." What exactly should I be flashing 2x here? Never mind I figured it out
The ROM, but you figured it out.
I suggest you just flash CM7 because it doesn't take that long and you get some practice before going onto another ROM.
FC3SRedSuns said:
I suggest you just flash CM7 because it doesn't take that long and you get some practice before going onto another ROM.
Click to expand...
Click to collapse
I had already flashed 2 other ROMs before going to CM10, 1 successful on not so successful. This time it went flawlessly. Im loving CM10 so far. I see why this is so addicting now haha
Now you guys see what I mean about steps before leaps?
If you have a bad flash on 2.2 or 2.3.x, they are fairly easy to recover from and start over. Sometimes a bad flash on ICS can cause irreparable damage, al'a EU bug. I've also seen motherboards borked, USB/PC unconnectivity and the worst of all a bootloader bad flash, hardbrick.
But yes, I as well as almost everyone here will agree, it is very addicting.
I decided to root my phone last night. I followed a guide that was on XDA. I flashed the CWM thing, and then tried to boot into CMRecovery, but it went into Android Recovery. I tried this multiple times with no success. After that, I re-flashed what I was supposed to, and I booted into it in order to install SU.
The root seemed successful, and I ran various apps that said my phone was rooted. I don't know a whole lot about things, but I wanted to flash a custom kernel in order to install a custom boot animation. In order to do that, I wanted to make a backup so I tried to boot into CMRecovery but it only went into the Android Recovery Mode. It continues to do so. Any and all help would be appreciated!
I was going to install CM Recovery with the ROM Manager but it said the ICH 500 is not available.
If I have to re-flash something on my phone, I'd appreciate some specifics as there are a lot of variations for files.
grantekert said:
I decided to root my phone last night. I followed a guide that was on XDA. I flashed the CWM thing, and then tried to boot into CMRecovery, but it went into Android Recovery. I tried this multiple times with no success. After that, I re-flashed what I was supposed to, and I booted into it in order to install SU.
The root seemed successful, and I ran various apps that said my phone was rooted. I don't know a whole lot about things, but I wanted to flash a custom kernel in order to install a custom boot animation. In order to do that, I wanted to make a backup so I tried to boot into CMRecovery but it only went into the Android Recovery Mode. It continues to do so. Any and all help would be appreciated!
I was going to install CM Recovery with the ROM Manager but it said the ICH 500 is not available.
If I have to re-flash something on my phone, I'd appreciate some specifics as there are a lot of variations for files.
Click to expand...
Click to collapse
What ROM are you on? What kernel did you try to flash? I am new to the tech side of things here but I have flashed my phone and rooted 6 different fascinates over time.. This week I've flashed into three different ROMs and if you want to run a custom boot animation I may be able to help as I changed mine on the jellybeer ROM a few different times ..
dee3 said:
What ROM are you on? What kernel did you try to flash? I am new to the tech side of things here but I have flashed my phone and rooted 6 different fascinates over time.. This week I've flashed into three different ROMs and if you want to run a custom boot animation I may be able to help as I changed mine on the jellybeer ROM a few different times ..
Click to expand...
Click to collapse
I downloaded the following files:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know what ROM I'm on, and what kernel I flashed. I only followed the instructions here http://forum.xda-developers.com/showthread.php?t=1238070. (Rooting stock Froyo/Gingerbread)
Ok I followed a diferent method but its pretty much the same in a way... You will want Odin on your computer And you need the Samsung driver as well as atlas.zip And stock eh03 downloaded on your computer. I will message you the link I used to see if it helps.
---------- Post added at 05:38 PM ---------- Previous post was at 05:24 PM ----------
I followed section 4 and that rooted to where I flash diferent roms regularly from recovery now. The link is in a message I sent you. Good luck And ill help anyway I can as I asked for help here but never got any I had to figure it out on my own.. Doug
dee3 said:
Ok I followed a diferent method but its pretty much the same in a way... You will want Odin on your computer And you need the Samsung driver as well as atlas.zip And stock eh03 downloaded on your computer. I will message you the link I used to see if it helps.
---------- Post added at 05:38 PM ---------- Previous post was at 05:24 PM ----------
I followed section 4 and that rooted to where I flash diferent roms regularly from recovery now. The link is in a message I sent you. Good luck And ill help anyway I can as I asked for help here but never got any I had to figure it out on my own.. Doug
Click to expand...
Click to collapse
Thanks for replying, I got your private message. I don't believe I used an atlas.zip when I did it. Regarding the link you sent, could you specifically explain how step 4 is different then flashing regularly? Also I believe I have (or had) Gingerbread, not the other one.
I can't actually explain it other than that is what I've used on all the fascinates I've rooted. I flash them all back to stock eh03 , Odin them in download mode via USB with the atlas.zip and the stock eh03, flash CWM clockworkmod recovery after and than I download what ROM I want onto SD card. Than I flash it via CWM recovery with appropriate Gapps. Like I said I am dumb to the tech side and when I asked devs for help here I never got any usually. I have multiple fascinates on different ROMs and a lot of it I just googled my questions for answers . hope someone else can explain what I'm having a hard time explaining.. I am on the last KK build though on this device. Had the last Dirty uni ROM before this and it was unstable compared to the KK ROM.
Sent from my SCH-I500 using XDA Premium 4 mobile app
---------- Post added at 10:24 PM ---------- Previous post was at 10:19 PM ----------
And the boot animation thread should be able to tell you how to go into your files and rename and replace your bootanimation file .. Its been about a month since I changed an animation to a red helix animation on one of my other fascinates
Sent from my SCH-I500 using XDA Premium 4 mobile app