CURRENT STATUS -- PHONE BACK TO STOCK AND WORKING. WILL ROOT AGAIN AND PROBABLY WAIT A FOR THE FINE DEVS AT TO RELEASE THE ROMS I WANT INSTEAD OF MANUAL MODS HA!
PLEASE NOTE, AT THE TIME OF WRITING THIS THREAD, THE ROM MANAGER INSTALLATION OF CLOCKWORKMOD HAS SERIOUS ISSUES. YOU DO NOT HAVE A WORKING RECOVERY EVEN THOUGH IT FLASHES THE RECOVERY SOFTWARE. SEE XDA THREAD showthread.php?t=1695967 CHECK YOUR CLOCKWORKMOD BEFORE YOU DO ANY MODS
SUMMARY OF FIX --> USE FASTBOOT TO RELOAD WORKING RECOVERY --> ATTEMPT ROM INSTALL, FAILED --> RELOCK BOOTLOADER --> RUN APPROPRIATE RUU...PHONE IS NOW BACK TO STOCK CONDITION WORKING GREAT. XDA WILL SAVE YOU FROM YOURSELF
What happened?
-Rooted phone with regawMOD. Everything fine.
-Install rommanager -- decide to flash clockworkmod via rom manager, since I'm used to that recovery in the past.
-Use phone for 2 days.
-See thread about editing build.prop for links related to apple lawsuit.
-used root explorer file manager, backup build.prop, edit build.prop, HIT THE PERMISSIONS BUTTON ON THE FOLDER TO R/W and then back to R/O (DAMN DAMN DAMN)...reboot phone. Phone boots HTC white screen and then just black. Won't boot android.
What I tried to fix?
-Thinking sucks, but no biggie, I reboot and go to recovery clockworkmod 5.8.3.5 DOES NOT WORK...go search, find more forum posts about this version for our phone not working...DAMMIT CLOCKWORKMOD!
-Go to "Factory Reset", who cares at this point, just reset everything? Nope...white HTC screen, boots into clockworkmod v5.8.3.5 -- again, broken worthless recovery, no menus do anthing. Why did I forsake you TWRP?!?!
Now I'm gun shy on just hopping down and trying new things without consulting you guys first. What are my options? Don't want to make this worse.
Fine
TL;DR
EVO 4GLTE, rooted.
Screwed permissions and/or build.prop system folder
clockworkmod recovery version is worthless
Afraid to go forward.
If you can boot into the bootloader, maybe you can use fastboot to flash TWRP.
xxddaaohnoes said:
What happened?
-Rooted phone with regawMOD. Everything fine.
-Install rommanager -- decide to flash clockworkmod via rom manager, since I'm used to that recovery in the past.
-Use phone for 2 days.
-See thread about editing build.prop for links related to apple lawsuit.
-used root explorer file manager, backup build.prop, edit build.prop, HIT THE PERMISSIONS BUTTON ON THE FOLDER TO R/W and then back to R/O (DAMN DAMN DAMN)...reboot phone. Phone boots HTC white screen and then just black. Won't boot android.
What I tried to fix?
-Thinking sucks, but no biggie, I reboot and go to recovery clockworkmod 5.8.3.5 DOES NOT WORK...go search, find more forum posts about this version for our phone not working...DAMMIT CLOCKWORKMOD!
-Go to "Factory Reset", who cares at this point, just reset everything? Nope...white HTC screen, boots into clockworkmod v5.8.3.5 -- again, broken worthless recovery, no menus do anthing. Why did I forsake you TWRP?!?!
Now I'm gun shy on just hopping down and trying new things without consulting you guys first. What are my options? Don't want to make this worse.
Fine
TL;DR
EVO 4GLTE, rooted.
Screwed permissions and/or build.prop system folder
clockworkmod recovery version is worthless
Afraid to go forward.
Click to expand...
Click to collapse
yeah, download twrp and move it to your fastboot folder.
use the command "fastboot flash recovery (recovery name).img"
replace (recovery name) with whatever twrp is called, and remove the quotes.
husker91 said:
yeah, download twrp and move it to your fastboot folder.
use the command "fastboot flash recovery (recovery name).img"
replace (recovery name) with whatever twrp is called, and remove the quotes.
Click to expand...
Click to collapse
THANK YOU BOTH OF YOU!
For posterity, those that are reading this with a similar problem in the future, go here for the EVO LTE:
teamw.in
/project/twrp2/98
1> make sure your HTC drivers are up to date
2> download the TWRP img file
3>find fastboot.exe
4>put TWRP img file with fastboot.exe
5>run commands as on that TWRP page
I now have TWRP recovery! But not a running phone yet
The plan at this time was to wipe everything and just flash a stock ROM and count my blessings. Problems though with sd-ext and new ROM.
Wipe cache -- works.
Wipe Dalvik-cache -- /sd-ext not present, skipping
Factory Reset -- failed to mount /sd-ext (No such file or directory)
I've got the stock ROM img sitting in /sdcard via USB mount on my PC. Just copied it over.
Then I install it and everything acts like it works.
Restart phone, hangs at HTC screen for 20 minutes, never fully booting.
And now I'm here again.
When I go into the TWRP file manager I can see /sd-ext
Any thoughts?
The /sd-ext errors are normal, it's only used if you reformatted your sdcards to add it.
If the ROM you flashed is good and it still won't boot you'll want to run the RUU and bring it back to stock. All you have to do is connect it in fastboot mode and run:
fastboot oem lock
Then, once it's relocked, leave it in fastboot mode and run the RUU that can be found here.
You may need to run it twice if the phone reboots half way through, but that's fine. Just run it a second time and it should finish. When it's done your phone will be completely stock again.
fugard Dollin's
xHausx said:
The /sd-ext errors are normal, it's only used if you reformatted your sdcards to add it.
If the ROM you flashed is good and it still won't boot you'll want to run the RUU and bring it back to stock. All you have to do is connect it in fastboot mode and run:
fastboot oem lock
Then, once it's relocked, leave it in fastboot mode and run the RUU that can be found [
You may need to run it twice if the phone reboots half way through, but that's fine. Just run it a second time and it should finish. When it's done your phone will be completely stock again.
Click to expand...
Click to collapse
Will try that now and report back.
Thank you for the quick answer and vote of confidence. I know what is "supposed" to happen along this path, but this is the first time in 5 years and as many devices that I've made such a bone headed mistake rooting. So now I'm a little overly timid as to what is normal and what I caused in screwing up some permissions.
Thanks again!
WORKING! OP updated. Thanks everyone for your time and help!
xHausx said:
The /sd-ext errors are normal, it's only used if you reformatted your sdcards to add it.
If the ROM you flashed is good and it still won't boot you'll want to run the RUU and bring it back to stock. All you have to do is connect it in fastboot mode and run:
fastboot oem lock
Then, once it's relocked, leave it in fastboot mode and run the RUU that can be found here.
You may need to run it twice if the phone reboots half way through, but that's fine. Just run it a second time and it should finish. When it's done your phone will be completely stock again.
Click to expand...
Click to collapse
Haus are we lucky enough to have you join us here? Or u still rocking the 3D? Hope things are well buddy
Edit...OP glad to hear things worked out.
Sent from my EVO using Tapatalk 2
Not sure why people insist on having CW even when they know its broken. Even if it wasn't broken, just using TWRP one time, one will realize how much better it is compared to CW. Anyways dude, you're not fully bricked. You just need to find a way to get TWRP flashed.
Sent from my EVO using XDA
shook187 said:
Not sure why people insist on having CW even when they know its broken. Even if it wasn't broken, just using TWRP one time, one will realize how much better it is compared to CW. Anyways dude, you're not fully bricked. You just need to find a way to get TWRP flashed.
Sent from my EVO using XDA
Click to expand...
Click to collapse
{
"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"
}
Related
Edit: I'm not pleased with this guide yet. Below I have you going back to stock jfd (2.1) and then I have a 2.2 kernel (overstock) which I didn't use when I installed cm7... I'm probably going to change this and suggest using the alt method in the noob guide, or going to jfd and then installing Trigger... Suggestions?
Installing CyanogenMod 7 on the Vibrant is NOT difficult. The process is different, not hard. There are certain steps you need to follow. Please note, I am trying to help and am in no way responsible for your actions, your phone, etc.... I will try and assist you so please post comments/suggestions/questions below.
Is CM7 perfect? ABSOLUTELY NOT!!
Read up on it HERE and decide if you are ready to try it out.
I am not being as detailed as normal. That is because I assume you have read and KNOW the NOOB GUIDE first.
I will let POST ONE be from start to finish (stock phone > CM7). This is obviously the longest process, but it's also the cleanest install.
POST TWO will be for those who already have root/custom recovery/a custom rom and DO NOT want to go back to stock first.
Regardless which method you choose, you are going to need the files....
FILES
The Update.zip file to root your phone (this roots stock 2.1, not 2.2) > File: View attachment update.zip <
If you have eclair, root per the noob guide linked above or another method of your preference... doesn't matter.
**A kernel with CWR (here is a link to an OverStock you can use): LINK
** I didn't use this method, I believe it should work fine, feedback wanted **
** I BELIEVE the reasoning here for this are two things, could be wrong... one, you cant use stock recovery and two, this gives you the option to go from CWR directly to download mode, which is needed later. THAT SAID, I used the regular CWR that installs from Rom Manager... once I flashed the efsbackup (more on this soon) I just pulled my battery and went into download mode because (a) it was fast (b) I didn't have the option to enter download mode from recovery.
THESE THREE FILES ARE NEEDED
- vibrant-efsbackup.zip
- cm7-vibrant-initial-kernel.tar
- cm7-vibrant-initial-20110304.zip
OPTIONAL: You may want to also grab the latest NIGHTLY version of CM7. The link above is the INITIAL CM7... there is work being done in the form of updates/NIGHTLY versions.... you can find them HERE and read about them on THIS thread. These do NOT wipe your phone so really no reason to not backup/test these out as they are released in my opinion.
I would also download the following:
The latest CM7 kernel from theexel (my preference here, not needed)
The Google Apps (CM7 doesn't come with the Market, Gmail, etc.. a C&D order a few years back is to blame)
STOCK > CM7
First thing I did was move ALL of my personal FILES that were already on my phone (both the internal/external) to my pc so I had a backup of them.
I then went to Menu > SD CARD AND PHONE STORAGE and I unmounted/formatted BOTH the internal and external.
I then used ODIN to get back to stock JFD (if you are stock anything, that's fine, I wasnt so I added this step for those who want to go back to stock).
Once it has finished and rebooted, I mounted my phone to my pc. I then moved the following files (all were listed above, minus the .tar, more on that later... leave it on your PC) from my PC to my INTERNAL memory:
The update.zip file to root my phone
The OverStock kernel (option to enter download mode, not required though, see above)
The vibrant-efsbackup.zip
The cm7-vibrant-initial-20110304.zip
The CM7 most recent NIGHTLY .zip (updated CM7)
The latest CM7 kernel from theexel (my preference here, not needed)
The gapps (google apps) zip.
Hold in BOTH volume buttons and POWER (release when you see the Vibrant logo) to reboot into recovery (phone can be on or off). Select Reinstall Packages.
Your phone will reboot and you will have root.
Go to the market and download ROM MANAGER. Open it, select to flash CWR (top option) and once it's done (you got the Success popup), reboot into clockwork recovery (2nd option).
Go to install zip from sd card, choose zip from sdcard, select the overstock kernel zip if you are going to flash it. If so, once done, reboot the phone...then go BACK to CWR using the 3 button combo (should be a red recovery now)
Go to install zip from sd card, choose zip from sdcard, select the efsbackup.zip. Once it finishes you need to get into download mode. If you used the overstock kernel, there is an option.. maybe under advanced. If you kept the normal CWR via Rom Manager, you can pull your battery and go ahead and load ODIN/Download Mode.
Load ODIN on your PC (I prefer THIS version of ODIN, older versions tend to hang up more)
UNCHECK reboot phone
UNCHECK Re-Partition
Load the cm7-vibrant-initial-kernel.tar (PDA Spot)
Press Start
About 10 seconds later, it should be done.... you need to get back to recovery... no need to turn off the phone or anything, FROM DOWNLOAD MODE, SIMPLY HOLD IN BOTH VOLUME BUTTONS AND POWER UNTIL YOU SEE THE VIBRANT LOGO.
** note, in this pic, my phone is not connected yet.. you can load this up before you connect your phone **
{
"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"
}
Now, in CWR, go down to "mounts and storage" and format the following: System, data, and cache.
Still in CWR, go to install zip from sd card, choose zip from sdcard, select the cm7-vibrant-initial-20110304.zip. Once this has finished do a Factory Wipe and Reboot.
Enjoy watching your new CM7 Bootup!!
Click to expand...
Click to collapse
IMPORTANT: Allow 15 minutes of the phone being turned on for the install to settle.
At this point, I would reboot back to recovery (3 buttons, power menu option will NOT work) and i would flash the following:
The latest Nightly update (don't wipe again, not needed).
The custom kernel from theexel (OPTIONAL)
The gapps zip so you can have the Market, gmail, etc
Then reboot.. let the phone sit... drink a beer.. donate some money to the guys that make this possible IF you like... and then enjoy the latest CM7 on your phone!
On a bootup, you may not have signal until you power off and back on your screen, fyi. *thanks theexel*
CM7 BOOTUP / RUNNING ON THE VIBRANT
Reserved for future use
nice guide!
Sent from my SGH-T959 using XDA App
It's not perfect, hate I was having issues recording to my pc... the drivers for my recorder were royally effing up using ODIN so I do not have nearly the video quality I was hoping to add.
Please offer suggestions for imporoving the guide!
You said you installed overstock kernel to JFD? how was that compatible? it's a 2.2 kernel right?
Sent from my SGH-T959 using XDA App
^ no... I did not, I just used the CWR that came with rom manager.
I may need to edit the guide... good catch.
Since there seems to be great interest in Cyanogen I think this guide should be stickied. Even though this is a work in progress it's already much clearer than the Cyanogen thread's OP.
^ I appreciate it, but this is not good enough yet... and I question of this install method will be required ongoing.
I may make a big change and suggest everyone just ODIN to stock using the ALT METHOD in my noob guide since it comes pre-rooted, comes with Clockwork Recovery AND is a 2.2 rom.
I probably should have done this the first time... may start over from scratch. I need feedback from people using this guide to know how it's working.
Hey when coming from CM7 to stock, do you hit re-partition in odin?
Sent from my SGH-T959 using XDA App
If you are gonig back to stock, from CM7, the file system on CM7 is different so I remember reading that you should....
that said, when I went back to stock to redo the process for making the guide... I honestly do not recall if I checked it, and I am up and running fine...
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
Hey.
I have managed to get a really funny issue with, sadly, my moms Xperia P.
The P is running Nemesis kernel v6.3 and Honami MW v8, and of course unlocked BL, and have been working okay-ish(I cant say I particularly like the P).
Since its my mom's phone, and shes... well, not the youngest nor most tech-savvy person around, Ive done what I can to make it as 'user friendly' as possible.
But this time I mustve fked up badly...
Heres what I did: I was checking if I could get the AOSP incoming call screen in the same manner as the lock screen, so I tried renaming semcPhone.apk to something else, thinking the worst thing that could happen was a boot loop... Boy was I wrong...
Not only did the phone not start(no surprise there), but it even froze before the first "vibrate", making it impossible to enter recovery
Okay, no worries, I can still enter fastboot... So I went into fastboot and reflashed the boot - nope, still froze right away...
After much struggle to no avail, I tried a 'fastboot erase system' and lo' and behold! The stupid thing didnt freeze right away anymore and I could enter recovery!
Once In recovery I restored a backup I made a couple of weeks ago, and finally the phone started again! yay! :victory:
All is good then, right? .... nope...
Did a reboot, and it did the exact. same. thing. again. And I had to erase the system and restore the backup for the phone to boot again... wtf...
Okay, maybe erasing the system wasnt enough, right? So I did a factory reset, formatted system, data and cache, and went ahead of installing a fresh copy of Honami MW.......... Phone froze right away.... back to square 1...
Okay, so I repeated the process, but instead of installing a fresh MW, I restored the backup - phone booted fine Restarted the phone and back to square one again...
I tried installing a fresh copy a few more times, and it refused to boot each time. But restoring the backup boots the phone fine every time... whaaat?
The phone works perfectly fine once its booted, and I cant see anything wrong in the system at all, yet everytime I do a reboot it freezes right away and I have to erase system through fastboot(to get into recovery at all) and restore my ~2 week old backup. Its even enough to just do an "advanced restore" and chose system, leaving data and cache alone.
Ok so.. TL;DR: Phone freezes right away on first reboot, a fresh install of the ROM doesnt work - only restoring a backup do(it makes no sense!!)
I am completely out of ideas as to what can be the issue here... I have never experienced this kind of issue - especially not just by renaming "wrong" file(which gets restored during the reinstallation processes anyway)
{
"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"
}
Try flashing stock ftf completely and see if the issue persists(I guess it shouldn't)
Cheers,
AJ
Mm yes, flashing it back to stock ftf is the only thing I havent tried yet... But it still makes no sense. Why does it behave like this, regardless of complete wipes? And why is only a backup working, and not a clean install :s... My head's gonna explode over this >_<
Same here, have never been able to restore nandroid backup, always boots oince then its dead.
Anyone else have any bright ideas? I havent tried stock ftf yet(dont have access to the phone yet ), but somehow I have my doubts it will work...
I get the feeling the phone fails to mount the various partitions upon boot, but when checking permissions everything is exactly as it should be. Obviously Ive tried running 'fix permissions' in CWM, but that only results in a "/bin/sh: fix_permissions not found" which I also noticed my ZTE Blade says(which works fine despite all the cruel experiments Ive done on it lol).
Ive also tried to do a fresh install of BB and SU, as well as the whole rooting process(even though the ROM is already rooted) to no avail. (edit: also reinstalled recovery several times...)
Anyway, is there any app that can do a fix_permissions? Might be worth a shot...
Goatshocker said:
Anyone else have any bright ideas? I havent tried stock ftf yet(dont have access to the phone yet ), but somehow I have my doubts it will work...
I get the feeling the phone fails to mount the various partitions upon boot, but when checking permissions everything is exactly as it should be. Obviously Ive tried running 'fix permissions' in CWM, but that only results in a "/bin/sh: fix_permissions not found" which I also noticed my ZTE Blade says(which works fine despite all the cruel experiments Ive done on it lol).
Ive also tried to do a fresh install of BB and SU, as well as the whole rooting process(even though the ROM is already rooted) to no avail. (edit: also reinstalled recovery several times...)
Anyway, is there any app that can do a fix_permissions? Might be worth a shot...
Click to expand...
Click to collapse
Boot it wait 5-10 mins and then shut it down,do it again,and again until phone Boots needed to do it three times on Xperia U.
It only related to stock custom roms od 4.1.2.
Sent from my Xperia U using Tapatalk
XperianPro said:
Boot it wait 5-10 mins and then shut it down,do it again,and again until phone Boots needed to do it three times on Xperia U.
It only related to stock custom roms od 4.1.2.
Sent from my Xperia U using Tapatalk
Click to expand...
Click to collapse
You mean boot it to where it freezes(right away) and wait 10mins, or boot into system and wait 10mins? If the first, I think Ive tried that a few times. Doesnt hurt to try again though...
Do you have to do this every boot or just once after a flash?
Still makes no sense why it just started doing this "out of the blue"(If we ignore the fact I renamed a file, cause I seriously doubt that that specific action could cause this issue).
Edit: Dude.... That **** actually worked! I didnt wait 10mins, but maybe 2-3... Forced shutdowned it and started it roughly 5 times, the 6th time it started! Im currently rebooting it all the time(3 times so far... 4 now lol.. ok 5..) and it has started every time!!
Thank you for your tip (I should make some more accounts so I can hit 'thanks' a few more times lol)
I just want to make sure I understand the process before I go and mess up my phone. If someone could help me out a bit, that would be awesome.
#1 - Backup
I used a tool called Simple ADB backup (http://forum.xda-developers.com/showthread.php?p=36499906) to backup my phone. I'm not sure if it created an image or what (it's a .ab file at 6GB), but I also used Moborobo to backup contacts & apps. I already have my music, pictures, contacts backed up through gmail and such, so I'm not too worried about the data, only the fact that I want to be able to revert back to a stock ROM in case I mess up.
#2 - Make sure USB debugging is enabled and drivers are installed.
#3 - Wipe / unlock the bootloader through the htcdev website. This wipes all data from my understanding.
#4 - Install CWM or TMRW (this lets me load a ROM?)
#5 - Download ROM and use TMRW to install / load.
Now I've heard various things about S-off vs S-on. IT seems some ROMs can install with or without it and apparently with s-on is safer in terms of avoiding a bricked phone. S-off allows for deeper functionality for certain apps?
Now do I need a toolkit of some kind to do any of this or is that only with certain phone? Where does the SuperSU come into play?
I'm sure this isn't complicated to a lot of you, but this is the first I've looked into rooting. Did the past couple hours researching and figured I need to talk it out before going through with anything. As for ROM, I think I'm leaning towards the Cyanogen right now. It seems like a base version of Jelly Bean but slightly tweaked. I'm mostly looking to keep it clean and simple as possible and removing the bloatware and improve performance.
Thanks in advance, I'm excited!
rumpus01 said:
I just want to make sure I understand the process before I go and mess up my phone. If someone could help me out a bit, that would be awesome.
#1 - Backup
I used a tool called Simple ADB backup (http://forum.xda-developers.com/showthread.php?p=36499906) to backup my phone. I'm not sure if it created an image or what (it's a .ab file at 6GB), but I also used Moborobo to backup contacts & apps. I already have my music, pictures, contacts backed up through gmail and such, so I'm not too worried about the data, only the fact that I want to be able to revert back to a stock ROM in case I mess up.
#2 - Make sure USB debugging is enabled and drivers are installed.
#3 - Wipe / unlock the bootloader through the htcdev website. This wipes all data from my understanding.
#4 - Install CWM or TMRW (this lets me load a ROM?)
#5 - Download ROM and use TMRW to install / load.
Now I've heard various things about S-off vs S-on. IT seems some ROMs can install with or without it and apparently with s-on is safer in terms of avoiding a bricked phone. S-off allows for deeper functionality for certain apps?
Now do I need a toolkit of some kind to do any of this or is that only with certain phone? Where does the SuperSU come into play?
I'm sure this isn't complicated to a lot of you, but this is the first I've looked into rooting. Did the past couple hours researching and figured I need to talk it out before going through with anything. As for ROM, I think I'm leaning towards the Cyanogen right now. It seems like a base version of Jelly Bean but slightly tweaked. I'm mostly looking to keep it clean and simple as possible and removing the bloatware and improve performance.
Thanks in advance, I'm excited!
Click to expand...
Click to collapse
Okay, first, what machine are you on? Linux,mac,xp,vista,7? You can't unlock on 8.1 drivers aren't compatible. But Yes you unlock via HTC dev, I have a tool to help for that if you want to try it it helps first time root you still have to take the info that it gives you and put it into HTC dev then put the code you get from the email you get into the folder but I don't know if you would want that I need someone to test it But continuing.
Unlock via HTC dev if you want to do it manually with the command first.
1. Open a cmd prompt where your fastboot tool is using shift+right click.
2. Boot into fastboot by pulling the battery, then holding volume down and power, then clicking on the first thing which is fastboot by clicking power.
3. Back to the computer type
Code:
fastboot devices
4. If your device is found your good to get your unlock data, if not you need to reinstall drivers/check your connection/or your on windows 8/8.1
5. Now to get your unlock token.
Code:
fastboot oem get_identifier_token
6. Copy and paste this into HTC dev starting at
Code:
<<<< Identifier Token Start >>>>
And ending with this line:
<<<<< Identifier Token End >>>>>
7. Submit the unlock token it will say if its valid or not and send you a email with it is.
8. When you get the email it will have a item called Unlock_code.bin place this item into the same folder in which your fastboot is in.
9. Initiate the command
Code:
fastboot flash unlocktoken Unlock_code.bin
10. It will then send the Unlock_code.bin to your phone, you will see a prompt saying "Unlock bootloader" Then volume up and click yes. It will wipe ALL of your data back it all up before you do anything...
11. When your phone finally reboots. If you would like a custom recovery boot back into fastboot again, (Pulling battery then volume down+power button and clicking on fastboot
12. Then once into fastboot, back to your computer download either
TWRP: http://techerrata.com/browse/twrp2/vigor
PhilZ: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/vigor <-------you must use this if using a ROM by snuzzo "aka Plain-andy or illusion ROM
CWM: Or go here http://forum.xda-developers.com/showthread.php?t=1914215 Download one of the zips, Extract it with your favorite extractor. You should get a .img in a folder, extract it and put it in your fastboot folder. This is only for CWM.
Take one of the .img's from above that you just downloaded and place it in the folder with your fastboot.
13.Back to your computer to push the recovery. Then while your phone is still in fastboot and connected to the computer make sure your device is still found.
Code:
fastboot devices
then if your device shows up, you are good to then flash the Recovery. Initiate this command.
Code:
fastboot flash recovery <name of recovery>.img
14. It should write the img successfully.
15. If you would like to go into recovery, you can either press "bootloader" In the fastboot option then click recovery and go into it from there. Or do
Code:
fastboot reboot
it will reboot your phone like normal. Then you can put your ROM and correlating GAPPS of choice onto your phone via USB Mass storage, along with SU. Put it on the root of your external SD card. Then you can reboot into recovery. After booting normal and transferring the ROM of choice you can then enable USB debugging and do
Code:
adb reboot recovery
16. It will reboot you to the recovery that you used. You might get a lot of errors on your phone. IGNORE THEM!!
17. Go to install and find SU from your external SD card. Install that. Then after that I would suggest STRONGLY making a backup (NANDroid) By clicking the backup button in any recovery, make sure you back it up to your external SD card.
18. Make sure that you have your ROM of choice on your SD card.
19. Wipe the hell out of everything once your ready to install your ROM.... EXCEPT SD CARD
20. Install the ROM and GAPPS in that order.
21. After a confirmed flash, wipe, cache and dalvik.
22. Boot into fastboot. (Power+Volume down and clicking fastboot)
23. Take your original <Name of ROM>.zip and extract it. Open the folder. In the folder will be a item called boot.img
24. Place this boot.img into the folder with your fastboot.
25. Again initiate the command
Code:
fastboot devices
make sure the device is found.
26. Initiate the command, this will flash the kernal aka "boot.img"
Code:
fastboot flash boot boot.img
27. Once you've confirmed that it has flashed the boot.img do
Code:
fastboot reboot
it will reboot your device. WAIT AT LEAST 20 MINUTES!!! FIRST BOOT CAN TAKE A WHILE!!!
28. Once rebooted set up
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Now talking about s-off, if you like to flash ROM's a lot I would suggest it, if not and your just staying on one ROM then just stay s-on. s-off allows you to write to every partition to the phone. s-off can be dangerous as if say you flash a ROM made for the S3, well your phone will flash it happily and well brick itself going down happily... But with s-on it will abort the flash or anything. That being said theres also the advantage of s-off being you can flash a ROM for your phone, flash and go, no computer. S-off can do some stuff inside the phone such as bootlogo's etc.. BUT its not needed for almost any app in the play store or any ROM... s-off just simply means you can write to every partition freely. No its not required. Now if you were to mess up and something goes corrupt on the phone and you need to return to stock for some reason......Well.... You almost kinda need s-off for that.... unless you do
Code:
fastboot oem lock
relock your bootloader and run a RUU..... But while s-off you can simply run a RUU (ROM upgrade utility I think ) But you can just run it.... This is how your would "return to stock" if anything messes up.... s-off can be EASILY obtained via rumrunner, use the universal 0.5.0 it will s-off your device http://rumrunner.us/downloads-2/
Unlike the old version of s-off which requires linux and a 22ga wire.... Hope this answers any questions!
I will post anything if i missed something, have to go, typed this real quick, please don't do this yet I think its right though....
edit: Just checked over it and made some changes... This should be exactly step by step... Or for what I did and what most others did. If I missed anything, someone else please post...
After more research, I am editing my original response.
The above is too many steps for me; I know it can be simpler. I'm going to go with the Everevolv ROM and just want to verify my findings on the install process.
- Make sure all Rezound drivers installed
- Install & update Android SDK
- Unlock bootloader / wipe phone data
- Install TWRP
- Put Everevolv ROM .zip on SD card (not extracted)
- Boot into TWRP & Flash ROM
Now, I have not rooted my phone and I am S-ON, so I know I need to flash in fastboot with the command: "fastboot flash boot boot.img".
Does this mean I flash with the android SDK instead of TWRP? Or at what point in the install procedure do I flash the boot.img file?
From my understanding, this ROM does not require root access. Is this correct?
rumpus01 said:
After more research, I am editing my original response.
The above is too many steps for me; I know it can be simpler. I'm going to go with the Everevolv ROM and just want to verify my findings on the install process.
- Make sure all Rezound drivers installed
- Install & update Android SDK
- Unlock bootloader / wipe phone data
- Install TWRP
- Put Everevolv ROM .zip on SD card (not extracted)
- Boot into TWRP & Flash ROM
Now, I have not rooted my phone and I am S-ON, so I know I need to flash in fastboot with the command: "fastboot flash boot boot.img".
Does this mean I flash with the android SDK instead of TWRP? Or at what point in the install procedure do I flash the boot.img file?
From my understanding, this ROM does not require root access. Is this correct?
Click to expand...
Click to collapse
1. Unlock via HTC dev.
2. Make sure drivers are installed.
3. Push recovery to phone.
4. Back up stock to SD card.
5. Wipe everything including system.
6. Flash ROM and GAPPS.
7. Flash boot.img in fastboot using
Code:
fastboot flash boot boot.img
8. Reboot phone.
If you have any questions with that. I will explain each step more in depth. But steps 1-11 were unlocking help.
Step 12-19 is pushing the recovery, making a back up, rebooting to it.
Step 20-end actually getting the device to boot after flashing ROM. If I need to explain again. I will. In a ever more simplified version. Plus the reason that there were so many steps is because the longest step literally takes like 2 minutes max. The rest is almost like 30 seconds besides actually flashing the ROM and GAPPS. I tried to do as much detail as POSSIBLE!!! Please consider rereading it, if you don't understand a step, ask and I will gladly explain. But it is a COMPLETE STEP-BY-STEP GUIDE. Hope you get your phone rooted, but if you didn't know what fastboot was....you might need some more reading..... I can write up a complete guide of what EVERYTHING means, what EVERYTHING does. But fastboot is just where you flash recovery/boot.img/etc.....any questions, please ask, I will explain or someone can beat me to it
Awesome man, thanks so much! I'll give it another read... I have a few hours set aside later tonight to investigate the whole process once again, so I'll certainly have more questions.
Once again seriously, thanks for the help!
rumpus01 said:
Awesome man, thanks so much! I'll give it another read... I have a few hours set aside later tonight to investigate the whole process once again, so I'll certainly have more questions.
Once again seriously, thanks for the help!
Click to expand...
Click to collapse
sweet. Just PM me or post here :good:
pball52998 said:
sweet. Just PM me or post here :good:
Click to expand...
Click to collapse
Alright man so after re-reading it, it's starting to make a whole lot more sense now. Initially, I was wondering why the hell there were so many steps in your first post. Now I realize you were just going step by step through the HTC unlock process as well, which I'm guessing HTC walks you through more or less but you clarified it in more detail.
Now in a broader step by step list, you said this:
1. Unlock via HTC dev.
2. Make sure drivers are installed.
3. Push recovery to phone.
4. Back up stock to SD card.
5. Wipe everything including system.
6. Flash ROM and GAPPS.
7. Flash boot.img in fastboot using
Click to expand...
Click to collapse
Now my understanding is that unlocking the bootloader wipes all data, but #4 is a backing up procedure... Is this just creating a backup of the stock ROM on my phone at the moment, without any of my apps or personal data? Then #5 would actually be wiping the stock ROM?
These few steps confuse me a little:
20. Install the ROM and GAPPS in that order.
21. After a confirmed flash, wipe, cache and dalvik.
22. Boot into fastboot. (Power+Volume down and clicking fastboot)
Click to expand...
Click to collapse
Are GAPPS included with the ROM download?
#21 - Are you telling me to "cache and dalvik" or is that part of the flash process that I don't have to do in separate steps? For example, are you saying
a) After a confirmed flash, you need to wipe, cache, and dalvik.
or
b) After a confirmed flash, wipe, cache, and dalvik, you need to boot into fastboot.
WTH is dalvik?
Now I think those are my only questions regarding the process for the moment; I'm going to check out some YouTube videos of some of these processes individually to get a better understanding. It sounds to me like most of this makes sense once you actually start going through the process and seeing it instead of reading about it, but I wanted to do as much homework as possible first.
Think I'll go ahead and give this a try tonight... It sounds like with S-on, I can only screw it up so much but we'll see. I did all my chores tonight so I can focus on this tomorrow all night if I wonk it out and just be without my phone during the day.
Oh one last question - Will I be able to get updates / update without flashing again?
Thanks again man!!!
Okay. So my "full" step by step makes more sense now? Good now do you see why I had so many steps? It was each individual part. Step by step. With clear detail or at least I tried
So moving onto the "unlocking wiping data" yes it will wipe every piece of data. But leaves stock. What I would suggest is putting su on your SD card and that being the first thing you flash before wiping or backing up..I've heard you can't back up bare bone stock. It must have root, or so I've heard... So put su on your sd card and flash it first (aka go to install and find it swipe to flash. Su should now flash. You now have root or should). Not very hard, just flashing it won't do any damage.
But backing up. When you back up it pulls every piece of info you have and puts it into a folder on your SD card. Like I have no stock... I accidentally erased it... But besides that. Do you see in my signature how I have 3 roms on my rezound. PAC, CM, And sense 5. See every one of those has been backed up. If I were to restore it, it would automatically restore to the point where I made the backup.
So now let's say. You have your backup of stock. It's on your EXTERNAL SD CARD. It should be about 1-3 gb backup. So now we have that backup made in twrp. Wipee we now have stock saved just incase something happens
So then we go in to the wipe button. Youre going to
factory reset 3 times
Wipe data, cache, dalvik cache, boot and system 3 times each. Don't ask why 3 I really don't know. But one isn't good enough...it's proven... So this leaves you with no OS oooo noooo. But the thing is you have your backup on your external hard SD card. And also your ROM/gapps on there. (gapps is google apps) but you must download the two separately. Both in a .zip format. Not a folder... Can't flash a folder... But there should be a need gapps button on the evervolv page? Click it and it should take you to a download for gapps. Remember all this is on the root of your external SD. So now we have 3 things on your SD card and no OS. O Lordy.... Time to hit up the install button!!! ;D now were going to choose the evervolv ROM. Bam, click add more zips, find gapps, click it. Bam, now you have two zips queed to flash. Just swipe to flash make sure you choose the rom before the gapps. so time passes (less than 5 minutes) and rom and gapps are now flashed. When it gets done flashing you should have some options. One being wipe cache/dalvik. That is where your question of the #21 is... Sooo.... Dalvik is pretty much like our java almost... It runs our apps...soon android will be changing to ART (android run time).
Blah blah blah, doesn't matter!! Lol xD so then after wiping your cache and dalvik after flashing your rom, return to the main menu of TWRP you should see a button on twrp's main menu, at the very bottom right, "reboot" when you click on that you should get 4 options, reboot system, bootloader, recovery, power off. We want to choose bootloader. This will bring us to fastboot (it will say fastboot usb in bug red letters if your in fastboot) where you flash the boot.img that you extracted earlier from the zip and placed it in the same folder as your adb/fastboot you remember? We need to open a cmd prompt and flash this boot.img "aka kernel" so were going to type in that cmd prompt: fastboot flash boot boot.img
This will flash the boot.img to your phone once confirmed, (only about 6 seconds to write it) were going to reboot the phone and hope for the best.. Do: fastboot reboot
It'll reboot your phone, remember first boot can take a while....
Also what do you mean by your last question??????
Sent from my crappy Jailbroken apple iPad.....
Freedoms just another word for nothing left to do... Nothin' ain't worth nothing but it's free.....
Hey man! I did not read your full post just now because I'm tired of thinking about this stuff, but I went through your step by step instructions and everything seemed to work out. I'm currently waiting for on my first boot; it's at the Evervol screen with the heartbeat animation going on. Everything made perfect sense once following your guide to the actual process; it just seems risky since there's no good way to practice unless you have a spare phone or something.
The only thing that tripped me up was that my SD card had all the data from my previous ROM even after everything was wiped. So I formatted it in Windows prior to copying the SU, ROM, and GAPPS zips on there.
Oh and I noticed after wiping and booting into the "clean" stock ROM, I had no service... Obviously, I didn't try to fiddle around with that since I was about to install a new ROM, but I can see that being a problem if this ROM ever loads (been about 22 mins).
I did find this info on a different thread:
1. Go to the dialer and press *#*#4636#*#*
2. Click on "Phone Information"
3. You should notice almost towards the bottom radio settings, Make sure the radio is on and change the settings from WCDMA to GSM (auto)
4. Exit out of the screen by pressing the back button
5. Reset the phone and you will have service.
Click to expand...
Click to collapse
I'll give that shot if it's no bueno!
Thanks again man, I'll post back tonight if I don't fall asleep before it's done loading, lol. Either way I'll post back tomorrow. Seriously thank you again, can't believe you typed all that out for me, even when the first 11 steps were step by step from HTC too. :good: True internet assistance!
Did you flash the boot.img in fastboot?? That can cause you to stay on the boot screen forever. I've had that problem @rumpus01 and glad it all made sense!!! :good:
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Did you flash the boot.img in fastboot?? That can cause you to stay on the boot screen forever. I've had that problem @rumpus01 and glad it all made sense!!! :good:
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
I did indeed as it was listed in your steps, of course!
It's been about an hour now, so I'm guessing something went askew and it is not going to power up. What course of action should I take from here? I'm guessing go back to stock ROM via recovery (the backup I made), and then do the whole process over again, aside from unlocking and what not. I definitely installed SU before making a backup, so hopefully that works out.
Thanks again! It's never simple...
Okay one question. How much did you wipe before you clean installed the ROM? Did you wipe everything but External SD 3 times? Including system?
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Okay one question. How much did you wipe before you clean installed the ROM? Did you wipe everything but External SD 3 times? Including system?
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
No, I did not... I did everything before your post about that, so I'm guessing that's the problem. I also only wiped cache, dalvik cahce, system, and internal storage. There's an option for android secure and factory reset under the wipe menu as well, but I wasn't sure about those...
I tried pulling battery and rebooting, I'm guessing it's dunzo. I am now booted into recovery mode and going to recover to the backup I made, and try the whole thing again after reading your post about wiping multiple times.
EDIT: To clarify, I am wiping everything 3 times before restoring. Then I'm going to reboot normally to see if the restore worked, and then go through the process again except wiping multiple times before installing the ROM this time.
Crap....sorry I didn't mention that to begin with..... And don't do the recover yet. Try wiping everything.... 3x then try booting. After the boot.img flash in fastboot... Sorry I forgot that man.... First off though, if everolv doesn't work. You can always try another ROM. Go s-off (takes at most like 30 minutes) then flash everolv.... But try wiping everything at least 3 times except the SD card. The reason for the two wipes is because one clears main. Then it goes into emmc and clears I think.. Sorry I completely forgot about it and it went over my head....
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Crap....sorry I didn't mention that to begin with..... And don't do the recover yet. Try wiping everything.... 3x then try booting. After the boot.img flash in fastboot... Sorry I forgot that man.... First off though, if everolv doesn't work. You can always try another ROM. Go s-off (takes at most like 30 minutes) then flash everolv.... But try wiping everything at least 3 times except the SD card. The reason for the two wipes is because one clears main. Then it goes into emmc and clears I think.. Sorry I completely forgot about it and it went over my head....
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
Crap I already wiped everything and tried a restore, which doesn't appear to be working haha. And don't worry man, I can't believe you gave that many instructions to begin with. It's a lot of steps! Nothing happens when I boot after doing my recover install. My computer gives the sound of a USB device but says nothing, and my phone doesn't even light up in any way. I'm going to go wipe everything and try rebooting it normally again.
Well just wipe, wipe, wipe, then install the ROM and gapps. Flash boot.img and you should boot fine.... Btw if you want stock, there's a ROM for that xD
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Well just wipe, wipe, wipe, then install the ROM and gapps. Flash boot.img and you should boot fine.... Btw if you want stock, there's a ROM for that xD
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
So after wiping everything, I go to "install" and all the zip files for the GAPPS and SU and ROM are on my Internal storage device... didn't I just clear that 3 times???
I cleared everything including internal storage and selected reboot, and recovery told me SU was not installed and asked if I wanted to. I chose yes and rebooted. Then wiped cache/dalvik cahce 3 times each, and now installing the ROM and GAPPS again... I think I wiped my internal SD card & system in addition to cache and dalvik cache after installing SU but before installing the ROM and GAPPS initially... I wonder if this was the main source of the problem.
Okay. Everything's wiped. There is no os installed. So that being said. You have your ROM and gapps on your SD card. Correct? Or external SD card. Either will work dear sir. Install those and then flash the boot
Img and see your result. That should be the easiest way to boot.
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Okay. Everything's wiped. There is no os installed. So that being said. You have your ROM and gapps on your SD card. Correct? Or external SD card. Either will work dear sir. Install those and then flash the boot
Img and see your result. That should be the easiest way to boot.
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
WELL WELL, IT IS WORKING. IT blew through that Evervolv boot screen in like 2 minutes this time.
I see that my service is not working, and my computer said MTP USB Device drivers failed to install. I now see that has something to do with transferring media files to PC.
Well, whatever. I am cool with this for now, at least it is installed. Very tired, let's all go to sleep! Thanks again for all the help man, feel like I'm paying someone for remote support lol.
Lol gg man. We got it. Cheers!!! :good:
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF