Related
ok so i loaded MotoFrenzyv05a so my milestone would have android 2.2 an its working great. So what i wanted to do next was to load the update : MotoFrenzy-v0.5c-update-nosign.
As the instructions say:
(download the latest attached zip , and inside you find a MotoFrenzy-vx.xx-update-nosign zip , which you copy to your sdcard into the folder /OpenRecovery/updates and recover from OpenRecovery menu.
Patches only match the release which it is made for. so 0.1 release has patches 0.1(a-z) and so on. you cannot use 0.1a on a 0.2 release.)
i dont have a folder named openrecovery on my sd card, so i tried a bunch of stuff pretty much an i just dont know if i have it on or not, if someone could jus tell me how step by step how to install this update (MotoFrenzy-v0.5c-update-nosign) i would really appreciate it.
And also after install the new MotoFrenzyv05a . i cant seem to find any networks to connect to on my phone, ive searched for my network telus countless of times and nothing, please help, thanks
Hello, I don't own a Milestone yet, but am planning on buying one and have done lot's of research, so I guess I could take a shot at helping you out.
Since you've been able to "install" (which is actually restore) MotoFrenzy, You probably already have root and some sort of recovery environment. Since the term 'openrecovery' doesn't ring a bell, let me ask this, do you know of the term 'adbrecovery'? Or do you remember how you installed MotoFrenzy?
In case you don't, I'll walk you through to installing Openrecovery.
I recommend using the OpenRecovery Mod by G.O.T. since that one has more features and is just my personal preference.
You can download it from: http://groupoften.wordpress.com/g-o-t-s-openrecovery/ look for "click to download (V1.04a)"
Once you downloaded the file, extract it and copy the "OpenRecovery" and "update.zip" to the root (top most folder) of your sd card.
Now you put the update in the /OpenRecovery/Updates folder.
Once you've done that, reboot your phone into the OpenRecovery menu by pressing power+X (for recovery 90.78) or power+Camera (for recovery 90.74)
Note that the recovery's of 90.78 and .74 don't have anything to do with what you've just done. Just try out both key combinations.
Once you've done that you should see a triangle. Now you have to press camera+volume UP and select install update.zip
Now you should be at the OpenRecovery Menu and that's as far as I can help, but it should be pretty self-explanatory (or something)
Hope that helped!
whenever i try to go back into recovery, it goes to the normal one instead of openrecovery. i have to apply update.zip every time. anyone else have that problem? otherwise it works fine. installed the theme, root, memhack, jit...
you have to apply the update.zip everytime it sucks but its not that bad ....
Motofrenzy is 2.1 not 2.2
Sent from my Milestone using XDA App
mousiope said:
you have to apply the update.zip everytime it sucks but its not that bad ....
Click to expand...
Click to collapse
thanks
thought i did something wrong. oh well. updates pretty quick anyway
Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.
Follow the instructions in the alternate gtab firmware post. It worked great for me. I would suggest installing cwm so you can back up your existing firmware.
My update would force close during download on the stock firmware. I finally got it to work by minimizing the pop up that displayed the progress. For some reason the screen would crash the download.
Your files should be there but you will lose all user settings and installed apps when you do the factory reset.
This is a common issue with stock, and TnT Lite. The user data seems to be very unstable once you upgrade to different firmware.
The "easiest" thing to do is just wipe the user data. However, if there is certain data you need to keep, I would recommend the excellent Titanium Backup. The only caveat is that the device has to be rooted, to use it.
roebeet said:
The only caveat is that the device has to be rooted, to use it.
Click to expand...
Click to collapse
And Z4root does this easily. Just install and click "root".
RyuFDAC01 said:
Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.
Click to expand...
Click to collapse
Tntlite is that easy I was surprised. Too since rooting my HTC hero a year and a half ago was so much more hands on
Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
I thank you guys VERY VERY MUCH appreciate this
Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
Click to expand...
Click to collapse
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recovery\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recovery/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
Dude thank you so much for your effort in this !!!!! gonna try this as soon as i put my baby to sleep.... will let you know if this worked for me
dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!
roebeet said:
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!
Click to expand...
Click to collapse
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!
dcom222 said:
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!
Click to expand...
Click to collapse
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed
RyuFDAC01 said:
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed
Click to expand...
Click to collapse
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!
dcom222 said:
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!
Click to expand...
Click to collapse
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!
RyuFDAC01 said:
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!
Click to expand...
Click to collapse
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
I just flashed the TnT 2.02 again. So far it seems OK, however it did the first 2 times I did it as well. I followed all of the instructions at "forum.androidcentral.com/showthread.php?p=442691#post442691" except I substituted using roeboot's TnT. Once I did it I had everything working (flash, market, etc...). Both times the boot loop happened when I tried to install or uninstall something, and both times were after a few hours of use. I tried a third time and almost instantly got into a boot loop, but I think I got ahead of myself in that try and did some things out of order. The good thing is that I was able to recover each time.
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.
The EULA shows up with a new stock firmware - and yeah 4.1 / 4.2 kinda bugged me too. I never selected "I Agree" - fark that.
As for the boot loops, it seems that we still can't pin it down - maybe it's just random, I don't know.
Hi,
I was stuck after bootlooping using Cyanmod, then flashing NVflash still didnt fix the issue, this fix did it for me. Thanks for getting me back up & running. I will give another shot at using cyanmod now that I have all the files needed to get me back.
BTW< I have a green cloth. What does that mean?
Thanks,
Rich
dcom222 said:
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.
Click to expand...
Click to collapse
My tab came with a grey cloth... funny thing though I got mine on the second wave of shipments to sears... I NEVER had any issues with the time i just set it and it kept the time... I remembered that when these first came out that was a problem... i thought mine was diff because i never had any issues with time reseting itself... anyway Thanks again dude for your help hope i could play this forward to someone more noobier than me
Roebeet looking forward to your TnT lites...
dcom222 said:
After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Click to expand...
Click to collapse
I now have clockwork recovery installed... How do i copy the update.zip from external microsd to internal microsd... mounting sd-ext gives an error..
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
Frustration levels are high with this device!!
Thanks!
a "me too" reboot problem
I was able to install TNT Lite 2.0, then 2.11. I got Clockwork Recovery installed as well.
The market would start, but if I did a search for obvious things like "Kindle", the market would give an error that it didn't exist in the market. Thinking it was the error situation described here:
http://forum.xda-developers.com/showthread.php?t=845175
I applied those instructions, and rebooted.
Upon reboot, it ended up in a continual reboot loop.
Trying to do the start with volume+power, it brings up Clockwork Recovery, and when told to wipe data/factory reset, it stays in the reboot loop. When told to apply sdcard's update.zip, it looks only at the one on the internal sdcard, which is for CWR, and goes back into the loop.
At that point I setup a microSD with the information from this post:
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
including changing the line from sdcard to sdcard2. Again it doesn't recognize that the internal sdcard2 is plugged in, and attempts to mount it with CWR (mount /sd-ext) yields the error:
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
So, unfortunately I'm at an impasse, like the previous poster. I just bought the tablet a couple of days ago, so I'm far from expert at tweaking it into working.
Any suggestions on what to do, are greatly appreciated.
PS - Bought the gtablet from Office Depot, and received a green cloth.
Boot into clockwork recovery and go to advanced and format SD, use the 2gb and 512mb I believe, then flash TNT or another rom. That fixed my boot loop.
THIS GUIDE IS SPECIFICALLY FOR THE MESMERIZE
Steps To Customize Your Mesmerize (For upgrading from any version to FROYO 2.2 EC10)
1.) Upgrade from any setup to 2.2 EC10 (Official Froyo) - If you have not already done so, you will need to upgrade your phone to EC10 2.2. If you have already, skip to the next step. (You can check this in "settings->about phone" under "firmware version" (should be 2.2.1 if you've already done this) NOTE: There is a custom rom listed in this post, I will detail that down below.
NOTE: The roms for this version come pre-rooted, so no need to root. However, if you have issues with superuser permissions (or are staying stock with root), you can use the SuperOneClick Root tool located here
If in the previous step you installed the leak that had the CWM upgrade pre-loaded or you have already manually updated CWM, skip step 2.- You know you have the updated recovery if when you boot to recovery it takes you to the red recovery with voodoo, backup and other options.
2.) Upgrade CWM manually (if needed) downloading this., (this next step by step will upgrade your recovery so that you are able to flash custom rom's/theme's/kernels.)
1.Shut phone off, pull battery out and leave it out.
2.Run odin (assuming you have it installed)
3.Load the cwm-recovery-all.tar file into the PDA spot
4.Plug usb into computer, then into your phone.
5.Hold the volume down key until phone goes into download mode, there will be a yellow android picture.
6.In odin, one of your com: spots should light up yellow - this means your phone is seen by odin (if not you may need drivers)
7.If above step is true, press start and odin will flash the recovery file to your phone. If all goes well the yellow box will turn green and your phone will power off.
8.Now you're able to boot into CWM recovery using the three button method (see glossary here)
3.)Upgrade Kernel With EC10 brought a new turn of events which thanks to jt has allowed fasicnate users to develop kernels which are compatible on the entire line of this model, so be sure to read phidelt's post on kernel's located here and choose one that is compatible with your rom. AOSP and MIUI require a different kernel, so keep this in mind as if you're restoring you may need to flash the appropriate kernel as the restore does not do this for you.
4.) Flash a custom ROM Choose from one of the Custom Rom's that we have out right now;
EC10 Pick and Pack DOWNLOAD HERE -- This is our stock deodexed rom with bloatware moved to a seperate .zip containing flashable packages with those removed apps. - < created by: phidelt82 >
EC10 Custom RomDOWNLOAD HERE - This is a custom rom built by phidelt82 which incorporates some aspects of AOSP into the EC10 rom - launcher and calendar are to name a few.
AOSP -DOWNLOAD HERE - This is a custom ROM/Kernel built with the android open source project code (by lmartin), one of the most "vanilla" rom's meaning no manufacturer's additions such as touchwiz. It's very lean and runs well, but is in BETA stage so beware it may not be for your daily use. NOTE: If you use this rom/kernel and are wanting to return to EC10 you will need to reflash the appropriate kernel for the ROM you are restoring to (for example touchwiz)
MIUI -DOWNLOAD HERE - This is a custom ROM running on the AOSP kernel, you can learn more about it in the thread linked here.NOTE: If you use this rom/kernel and are wanting to return to EC10 you will need to reflash the appropriate kernel for the ROM you are restoring to (for example touchwiz)
GAS EC10 PNP based rom -DOWNLOAD HERE - This is a custom ROM that runs with the touchwiz kernel. Learn more about it in the linked thread.
HEINZ 57 EC10 (PNP/ED01/EC10 based rom) -DOWNLOAD HERE - This is a custom ROM that runs with the touchwiz kernel. Thanks to Sbrissen, it has a lot of extra settings in the TM parts settings menu, allowing you even more customizing. Learn more about it in the linked thread.
5.)Flash a custom THEME Pick one that's compatible with the ROM you are running, from this list.
HELP MY PHONE IS SCREWED (GO TO STOCK 2.2)!!!: If you weren't attentive and made a mistake or haphazardly missed a step and now you're stuck at a boot screen or one of many other failure points, stop what you're doing. Take a deep breath, wu-sa, grus-fraba, whatever you need to do to calm yourself and simply go to this thread and get your phone back to stock. You may not need to go all the way stock, but it seems to be the easiest, and requires the least amount of help from the developers (who have better things to do than answer questions of careless/unlucky people!! - no offense intended) This is also how you would handle getting your phone back to stock before trying to turn it in for repair.NOTE: Being as going to stock means it's expecting your phone to be formatted to RFS instead of EXT4 (lagfix enabled) you should disable lagfix before doing so or you will have errors and md5 mismatches which will disallow you from flashing from recovery. If for some reason you can't access recovery you will just have to disable lagfix manually which is detailed in this thread here.
---------------------------------------------------------------------------------------------------------
==================================================
---------------------------------------------------------------------------------------------------------
THIS IS THE OLD GUIDE FOR CUSTOMIZING 2.1
When I began this process, I had zero experience flashing any sort of software to any sort of devices, and a very minor understanding of "rooting". After much research and crawling I was able to work my way through these steps with little headache, and learned a lot along the way.
Keep in mind there are many variations to each step, this is what worked for me the easiest as a newb.
And last but not least. There is always the disclaimer that attempting any of this can and will make your phone dysfunctional and or possibly bricked beyond repair (but most likely just dysfunctional which is a pain in the arse to deal with) if you do not follow steps completely (and of a trustworthy source such as xda - ehm and in the appropriate forum ).
So make sure you're in a comfortable environment (not a good idea to be trying to accomplish this while slamming beers at the bar), take your time, read each step that these people have taken the time to carefully write up (then follow it), and you'll be just fine. Be patient as things don't always move fast and you never want to freak out as you may screw things up bad, when it's actually just taking longer than you would expect. Always give it at least 5 minutes before you determine it's looping or crashing or whatevering, there is alot going on behind the scenes, trust me!
Steps To Customize Your Stock Mesmerize (For eclair 2.1)
1) Root your phone. - Basically all this means is gaining the ability to give programs/apps and yourself SuperUser access (equivalent of being admin in windows) and also the ability to flash roms via recovery, detailed below.
The easiest way to root is through the z4root.apk. (an application that will run right on your phone)
Download Here
After download, put z4root.apk on your SD card root directory
Then make sure in Settings->Applications that the "Unknown sources" box is checked.
If you don't have a file manager, download a free one from the market, using the file manager navigate to the z4root.apk and select to install it. Note: If you need help at this step, no offense I would suggest getting someone with more experience to help you continue on. I'm serious here
Reboot your phone
After it boots, open the z4root app and press root. At this point it is going to hang, give it 2 minutes and pull the battery. Count to 10, put it back in and turn it on. - This is normal, trust me .
After your phone boots open z4root again and click root, this time it will run no problems and phone will reboot.
NOTE**IF YOU HAVE PROBLEMS WITH z4root: "give Super One Click a try. It's a package you have to download to your computer, but you get to see more of what's actually going on so you know where it's at in the process. I have only used up to version 1.5.5, and I know that version is very capable for the Mesmerize on 2.1. It is located here."-This Information provided by phidelt82**
Once you are rooted (you will see the superuser icon in your apps, it will show apps you've given that permission to... eventually) you will need to make sure you have a file manager that can request root permissions (read/write) before you will be able to complete the next step. Search the market for "root file manager" and pick one to download and install.
Also at this step I would download and install RomManager and TerminalEmulator as you will need these later.
2) Install RomManager and the ClockworkMod Recovery. These will basically just give you the ability to boot into recovery where you can more easily flash kernel's/rom's and anything else you wish to push to your phone. (Recovery is basically a bios like interface - but it's different than the stock version)
I was able to install the Clockwork Mod Recovery very easily just by simply using the root file manager app I had downloaded, along with following with the instructions.
(In your file manager, MAKE SURE YOU ARE Read/Write not Read/Only, for RootExplorer there is a toggle at the top, other ones you may have to enable this through settings, others may just be R/W by default, you will just have to determine this or google the app)
Download the two zip files located in the first post here
Place both files on your SD card root if you were using a computer to download them or you could always download them through your phone's browser
Using the root file explorer app, move the Redbend_ua file from the SD card to /system/xbin/
Long press on the Redbend_ua file and click permissions, there should be one check missing, check that so that all are marked. Save and exit.
Now open TerminalEmulator (Come with me if you want to live )
NOTE:The spaces below are actual spaces and in bml8 there is a lowercase "L" not a "1" there is also a space after cd, after redbend_ua, after restore, and after recovery.bin
TYPE THIS ALL EXACTLY AS SHOWN BETWEEN THE QUOTES
at the command line ($) type "su" (then hit enter)
Type "cd /system/xbin" (then hit enter, which changes directory)
Type "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" (then hit enter, It will now scroll a bunch of text and reboot.)
After phone boots, open RomManager
Click on Flash ClockworkMod Recovery
Select the Samsung Fascinate your phone will still be the mesmerize. By now - you better damn well trust me , this is just what works with our model
At this point you're all stock and ready for new kernel/rom. (but now you are able to do so very easily)
3) KERNEL: Install Voodoo lagfix kernel and new 5.0 sound
If you want speed and good battery life (and high standard marks) +unlocking the headphone amp and eq controls (it makes even the samsung headset sound killer) go here and follow those steps for using your now functional recovery mode to flash the new Voodoo 5.0 kernel.
You could always install the old Voodoo kernel located here, if for some reason you do not want to take advantage of the new, sound improved one.
Note: Just an FYI, after installing custom kernel's you will always have an issue on start up of seeing a flashing black box in the middle of the samsung logo. This can be corrected by installing a custom boot screen (only requires root access) and you can find out how here.
Note: There are a few ways of getting into this recovery mode, the best way if all else fails is to hold phone from the back with left hand (thumb on volume button, in the middle holding both down and pointer on power button) hold these down until the mesmerize logo pops up then slide your thumb down a bit to volume down only (if you slip don't worry it might blink but it'll still go to recovery) Sometimes this is easier with the back case off. However the best way, is to download and use the QuickBoot app, it allows boot to recovery/reboot/poweroff options from the app.
4) Custom ROM : Download and install the ROM of your choice.
Just pick one from this list Here-They are all there along with other very useful links, read through the first post of each before you decide, some are plug and play some take a few steps first. These are currently only 2.1 eclair builds however right now they have an (somewhat unstable) 2.2 froyo rom/kernel that being worked on but is not quite yet ready for day to day use (some features are not working quite yet). But be patient because these guys will have something long before Samsung let's us have theirs, but who cares - "ours" will be so much better
HELP MY PHONE IS SCREWED!!! (GO TO STOCK 2.1): If you weren't attentive and made a mistake or haphazardly missed a step and now you're stuck at a boot screen or one of many other failure points, stop what you're doing. Take a deep breath, wu-sa, grus-fraba, whatever you need to do to calm yourself and simply go to this thread and get your phone back to stock. You may not need to go all the way stock, but it seems to be the easiest, and requires the least amount of help from the developers (who have better things to do than answer questions of careless/unlucky people!! - no offense intended) This is also how you would handle getting your phone back to stock before trying to turn it in for repair.
MASSIVE AMOUNTS OF Credit go to all of the OP's and many others (some included in my sig), these people are awesome, show them some love! Without them we would be stuck in stock US cell/Samsung HELL!
Final NoteIf you have any suggestions, additions, corrections, subtractions, or multiplications; PLEASE LET ME KNOW! I'm very open to all of the above and since this is now more of a community article let's stick to the android motto and keep it...open source
I gotta say, you did a really good job explaining yourself there. Now I'll just have to send people to one post and not a bunch when I get messages at all hours of the night.
Good work!
phidelt82 said:
I gotta say, you did a really good job explaining yourself there. Now I'll just have to send people to one post and not a bunch when I get messages at all hours of the night.
Good work!
Click to expand...
Click to collapse
Hey thanks, and believe it or not this is the exact reason I decided to put this together with this much detail (aside from answering someone's question). I figure, I'm no android developer but I can follow instruction and explain myself pretty well so I put this together to take some of that off of you guys. (A small token of my appreciation)
Nice work! Stickied for others to follow
Oh and love that comment:
Now open TerminalEmulator (Come with me if you want to live )
Click to expand...
Click to collapse
Gave me a good laugh!
the_scotsman said:
Nice work! Stickied for others to follow
Oh and love that comment:
Gave me a good laugh!
Click to expand...
Click to collapse
Haha well good and thanks, I almost put /badjoke at the end of that comment
EDIT: Edit to main post.
Good Job! This pretty much covers everything. Hopefully soon we can add to it :S
Is there a rough idea of the amount of time it will take to complete? I have pulled the battery a couple of times, and it just sits at the "running exploit in order to obtain root access" spinning the icon for several minutes. I have re-started it for a third time, now just letting it spin to see if it will come around.
LaTuFu said:
Is there a rough idea of the amount of time it will take to complete? I have pulled the battery a couple of times, and it just sits at the "running exploit in order to obtain root access" spinning the icon for several minutes. I have re-started it for a third time, now just letting it spin to see if it will come around.
Click to expand...
Click to collapse
Usually it only takes about a minute or so to complete. If it gives you problems, give Super One Click a try. It's a package you have to download to your computer, but you get to see more of what's actually going on so you know where it's at in the process. I have only used up to version 1.5.5, and I know that version is very capable for the Mesmerize on 2.1. It is located here.
Just wanted to say thanks for all the hard work and for the write ups for those of us new around here. You guys make the scene available for the rest of us.
Sent from my SCH-I500 using Tapatalk
Thanks for the easy walkthrough.
I am getting stuck at the end of step 2. The "redbend_ua restore" part was completed successfully, and after the phone rebooted I launched Rom Manager and clicked "flash ClockworkMod Recovery", selected the Fascinate, and keep getting an error message stating "An error occured while downloading your recovery."
Am I doing something wrong? Is there another way to get clockwork recovery onto my phone? I am on WiFi with a strong signal (I'm about 3 feet from the router) and the connection is working fine in other apps (browser and whatnot) so I don't think it's my internet connection.
Any help for this total newb to the android community would be greatly appreciated.
Mesmerizeuser said:
Thanks for the easy walkthrough.
I am getting stuck at the end of step 2. The "redbend_ua restore" part was completed successfully, and after the phone rebooted I launched Rom Manager and clicked "flash ClockworkMod Recovery", selected the Fascinate, and keep getting an error message stating "An error occured while downloading your recovery."
Am I doing something wrong? Is there another way to get clockwork recovery onto my phone? I am on WiFi with a strong signal (I'm about 3 feet from the router) and the connection is working fine in other apps (browser and whatnot) so I don't think it's my internet connection.
Any help for this total newb to the android community would be greatly appreciated.
Click to expand...
Click to collapse
It's not you. I believe Koush's repo is down right now. Hopefully it will be back up soon and you will be able to finish up.
Thanks for the heads up. Is there any way to get the recovery on the phone without using rom manager, or will I have to wait for the repo's to come back up?
never mind
It's back up. Just flashed to a voodoo kernel. Thanks again for the great instructions.
Very good write up.. You actually made it kind of fun to read if that makes sense.. lol
I seem to be running into problems. Whenever I go into recovery mode my phone doesn't verify the update.zip file. I was wondering how do I fix it or get another one? Also what part does this file play in changing roms?
Error:
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Install aborted
Also very good write up A++ would hack again
Edit: got it working. I had to rerun redbend_ua and make sure it went through a full reboot and didn't stall. I think I wasn't giving it super user permissions. Great writeup thanks again!
thanks this is worked great for me on the Froyo step by step
jmtenny said:
thanks this is worked great for me on the Froyo step by step
Click to expand...
Click to collapse
Great, glad to hear it! This is a new addition and I've just made some more changes and also reformatted the OP so i'ts more obvious that there are two processes.
Thanks so much for taking the time to do this!
I'd like to think that now I have a better understanding of what I'm doing.
I'm having some problems and was wondering if someone could help me please.....
I successfully installed the EA11 leak and updated from 2.1 to 2.2. However, when I boot into the blue recovery and try to hit update.zip from there it just shows me an exlamation icon and never goes into the red recovery instantly like it should according to everyone's directions.
At thiis screen it will stay showing this icon, and the only way off of it is to hit the menu key which takes you back to the blue recovery screen. It then has a description below the blue text that says:
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:Failed to verify whole file signature
E:signature verification failed
Installation aborted.
Am I doing something wrong? Any feedback would be so appreciated.
Fool proof way to install 4349:
The reason there are so many steps is that they are broken down so that each step is basically one menu action. Follow EVERY step. Yes there are easier ways, this way ensures that your tablet is absolutly stock and wiped of all traces of other roms.
What you need:
1. A g Tablet with CWM 0.8 recovery (doesn't matter what ROM)
2. A stock 3588 image renamed to 'stock3588update.zip' (http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip)
3. A stock 4349 image renamed to 'update.zip' (http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-4349-user.zip)
4. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
4. Calkulin's Format_all.zip (attached here: http://forum.xda-developers.com/showpost.php?p=11946224&postcount=1)
Step 1: Ensure there is nothing on your g tablet you want. NOTHING!
Step 2: Boot to CWM recovery with Pwr and Vol+
Step 3: Go to the "mounts and storage" menu
Step 4: Choose "mount USB storage"
Step 5: Confirm there is nothing you want to save on your SD card. If there is anything you want, save it now.
Step 6: "Unmount" and go back to the main CWM Recover Menu
Step 7: Choose "advanced"
Step 8: Choose "Partition SD Card"
Step 9: Choose 2048M for Ext size
Step 10: Choose 0M for swap size
Step 11: Watch it Partioning SD Card, then when complete once again mount USB storage as in steps 3/4
Step 12: Load onto the SD Card: Calkulin's_FORMAT_ALL.zip, stock3588update.zip, update.zip (this is the 4349 file), the recovery folder with the command file inside it. Your Sdcard should look like the attached screen grab.
Step 13: Unmount and return to main menu of CWM.
Step 14: Choose "install zip from sdcard" then "choose zip from sdcard" and select "Calkulin's_FORMAT_ALL.zip"
Step 15: Proceed with the install, once finish select "choose zip from sdcard" and select "stock3588update.zip"
Step 16: Once it completes, go to the CWM recovery main menu then power off with the power button.
Step 17: Boot up into recovery with PWR and Vol+. This will initiate the 4349 install using the stock recovery.
Step 18: Watch your tablet boot into a bone stock 4349 rom.
An optional starting point for this is to use nvflash (back to stock recovery or CWM recovery) to repartition everything first to make fully sure all partitions are as they should be.
Nice! Well laid out with clear steps. I 100% agree that the cleaner your device is, the more likely that the 4349 upgrade will succeed. On clean 3588 stock, I've had about a 90% success rate, at least (but I have had a few soft-bricks too).
Going to work on 3588 nvflash today - need to test it out as I think we all really need it, at this point.
Just one question for clairifacation.. on the command line of text. Should it have the have the apostrophy and the beginning and end or not?
LisaBham said:
Just one question for clairifacation.. on the command line of text. Should it have the have the apostrophy and the beginning and end or not?
Click to expand...
Click to collapse
No, corrected. Thanks.
Just to post a bit of an update:
It is pretty easy to get rooted with z4root. The permanent option works. Also, installing the amazon marketplace was no problem. I actually like this setup better than google market because it stores all the free apps you download as well as the paid ones.
Additionally, the google apps (download from here: http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps get the ones for tegra on CM6) from CM6 were easy to install with the standard recovery. Looks like this latest stock version is pretty decent overall.
ramerco said:
installing the amazon marketplace was no problem. I actually like this setup better than google market because it stores all the free apps you download as well as the paid ones.
Click to expand...
Click to collapse
The biggest problem with the Amazon Appstore for Android is that it has far, far fewer apps than the Google Android Market. A large majority of the applications that I require (indeed, what I bought the tablet to run in the first place) are only available through the Google Android Market.
Followed step by step and everything seemed to go well until I tried to restart after the upgrade....nothing but a black back-lit screen. Tried resetting/factory reset, tried clearing cache, nothing. Had to NVFlash back to 3588 and tried to see if there was an OTA update but it says I am up to date with 3588. Then tried to manually install the 4349 update.zip which appeared to go through but again, same black screen afterwards. Very frustrating.
tsg2513 said:
Followed step by step and everything seemed to go well until I tried to restart after the upgrade....nothing but a black back-lit screen. Tried resetting/factory reset, tried clearing cache, nothing. Had to NVFlash back to 3588 and tried to see if there was an OTA update but it says I am up to date with 3588. Then tried to manually install the 4349 update.zip which appeared to go through but again, same black screen afterwards. Very frustrating.
Click to expand...
Click to collapse
Sounds like you were stuck in apx mode. Lucky you were able to boot at all!
jason1332 said:
Sounds like you were stuck in apx mode. Lucky you were able to boot at all!
Click to expand...
Click to collapse
Could be, but I don't think so. I got through the 3 birds screen then the g-tablet screen before it went black so I don't think I was in apx. I guess I will just wait until VS pushes the OTA Update again.
Is there any way to change the boot animation in 4349?
ideaman said:
Is there any way to change the boot animation in 4349?
Click to expand...
Click to collapse
Boot animation is still stored in the same place (system/media) so existing methods for changing it should work fine.
Hi Gents,
Questions,
- Is this flash will void my warranty?
- If I'm running from stock 3855 Rom form VS, from what step I should begin with?
Thanks,
Charles
I'd like to make a formal request that this guide be stickied?
Many people have been wanting to flash the HC rom, and this is the best guide I've found (used it myself) to safely, and efficiently get to the 1.2 bootloader and stock recovery in update 4349.
It does not instruct anyone, or link to Roms on other forums, just provides them with the information to reach a foundation to where they can use 1.2 based bootloader roms. We can't ignore that it's an important catagory of users.
TJEvans said:
I'd like to make a formal request that this guide be stickied?
Many people have been wanting to flash the HC rom, and this is the best guide I've found (used it myself) to safely, and efficiently get to the 1.2 bootloader and stock recovery in update 4349
Click to expand...
Click to collapse
At that time this was a good way to do it. Now, you can NVFLASH 4349 in a few minutes. Then when you reboot wipe data/cache.
jcflman said:
At that time this was a good way to do it. Now, you can NVFLASH 4349 in a few minutes. Then when you reboot wipe data/cache.
Click to expand...
Click to collapse
regardless, there isn't a stickied guide on safely getting to 1.2 from out of the box setup...this is the most comprehensive one I've found for a brand new user that doesn't have any experience with nvflash (I still don't) or even flashing a rom. I've answered 2 questions today from people that basically just opened the box and were wondering how to get to 1.2 from stock. or wanted a link to a stock rom/recovery image. I haven't found any other posts that have a stock 3588 or stock 4349 files link in it. This post does, without even going into the roms available for the 1.2 bootloader.
Thanks ramerco. This is exactly what I've been looking for. I am still relatively new to the G-Tab and ROMS and need more details, which you have provided. I've been looking for "detailed" steps to get to 4349 along with 1.2 boot loader since I want to try roebeet's HC.
jcflman said:
At that time this was a good way to do it. Now, you can NVFLASH 4349 in a few minutes. Then when you reboot wipe data/cache.
Click to expand...
Click to collapse
I'd like ot bump this, and request again, that this post be stickied. More and more people are having issues when flashign from 1.1 to 1.2 roms, and THIS GUIDE is the SAFEST and MOST COMPREHENSIVE guide on how to go from 1.1 to 1.2.
Yes, it may be quicker to NVFlash as much as you possibly want, but I'll bet that if you found every post about a softbricked G-Tablet, the user was trying to NVFlash something...
It seems to me at this point, that developers are NVFlashing everything nowadays..that's fine, becuase most of them know how ot recover from it. Typical USERS, though, do not, and end up making their situation worse. WE NEED TO PREVENT PROBLEMS, so using standard recoveries, or CWM over NVFlash is the safest way to do it. I have no problem learning NVFlash to recover from a softbrick, but I'll be damned if learning it and using it CAUSES a softbrick becuase I have no idea what I'm doing.
PLEASE Sticky this thread, and clean up some other stickies that are no longer needed. For instance, Jerdog's "One and only Honeycomb" thread...not necessary anymore, since the reality he predicted wouldn't happen, has.
Wi-Fi
Who knows how to set up Wi-Fi on Linux.
Shall describe the step by step please.
how do you create file
I am really new at this. So how to you do this step?
4. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
What is the step-by-step process for this? I know how to create a folder, but I dont know how to create the file with the code. Can someone help me with this. Thanks I have Windows 7 if that matters.
novicexda said:
I am really new at this. So how to you do this step?
4. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
What is the step-by-step process for this? I know how to create a folder, but I dont know how to create the file with the code. Can someone help me with this. Thanks I have Windows 7 if that matters.
Click to expand...
Click to collapse
You might have a copy of the recovery folder with command file on your pc where you unzipped the cwmod_internal.zip unless you moved it to your G Tablet instead of copying. You could always unzip the cwmod_internal.zip file again to pull the recovery folder from it. Anyway, to answer your question...
To create a file just open the recovery folder you just created then right-click > new > text document. Put the code "--update_package=SDCARD:/update.zip" without the quotes & save the document as command. It shouldn't have a file extension like command.txt just command only.
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
baareem said:
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
Click to expand...
Click to collapse
what color is your cwm screen?
this may be a simpler way of gettin cwm:
http://forum.xda-developers.com/showthread.php?t=1220090
specifically, the CWM instructions set.
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
baareem said:
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
Click to expand...
Click to collapse
if you still have root, download from market
sgs kernel flasher and the flash the gingerbread kernel to give you RED recovery and flash the rom of your choice after a factory reset and usual wipes
Cool... i'm now running CM7 !
Here is what i missed for anyone who would have the same problem in the future (you can find the download links here: http://forum.xda-developers.com/showthread.php?t=1220090 ):
CWM Installation Instructions:
1) You must be rooted.
2) If you have a /Voodoo folder on your internal SD card, delete it and reboot.
3) If you're already running a custom ROM with Voodoo lagfix FULLY enabled, you can skip to step 7.
4) Download CWM-community-kernel-v8.zip if you're on Froyo or CWM-infused-v2.0.1-kernel.zip if you're on Gingerbread and place it on your internal SD card.
5) Install SGS Kernel Flasher from the Market.
6) Open SGS Kernel Flasher, select choose kernel, select the file you downloaded, and select flash kernel. Your phone will reboot and begin to enable Voodoo lagfix. Let it do that and boot all the way up. It will take a while (5-10 minutes) because it's converting all partitions to ext4.
7) Download update-infused-v2.X.X-full.zip and place it on your internal SD card.
8) Power off your phone.
9) With the phone powered off, hold both volume keys and the power button for about 10 seconds and then release. This should boot you into RED CWM.
10) Select "install zip from sdcard" and select update-infused-v2.X.X-full.zip.
11) Once that finishes, select "wipe data/factory reset".
12) Select "reboot system now".
13) Do NOT restore system data with Titanium Backup. Do NOT restore ALL apps with data. If you absolutely must restore something with Titanium Backup, only restore MISSING apps with data.
Click to expand...
Click to collapse
Now just another question: i noticed different errors when running the market and other old built-in apps... I just need to reinstall gapps right?
yeah, that is why it's stickeyed.
you just had to read/search them.
market wise, there's a market fix
or you can also factory reset and wipe cache and dalvik in cwm
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread (NOT) SOLVED.
--------
(Edited after realizing gapps still don't show up as installation didn't really worked)
baareem said:
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread SOLVED.
Click to expand...
Click to collapse
np. take it easy, bro.
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
E: Can't open /emmc/gapps-gb-xxxxxxx-signed.zip
(bad)
Installation aborted.
Click to expand...
Click to collapse
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
baareem said:
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
Click to expand...
Click to collapse
what version of ROM were you running when you tried this?
Stock FRoyo?
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
baareem said:
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
Click to expand...
Click to collapse
I haven't played with CM7, it's not an infuse based rom.
I recall some installation issues with it.
I remember an unsuccess reboot intially and pull battery thing..not sure.
If you're looking to install another rom, odin back to stock and start over.
check out my sig line for some useful links