Avoiding MicroSD when loading Custoom ROM - myTouch 3G, Magic Android Development

I'll admit, I'm no expert on this in the least, but I'll try to explain my dilemma.
I have a T-Mobile MyTouch, and I'd like to install Cyanogen for it's speed and other general benefits. I've followed this tutorial to the successful rooting of my phone, but when I got to section 3, it requires that I remove my micro-SD card and use the "provided" adapter to connect it to my PC to transfer the files.
I don't have any sort of micro-SD adapter, and it'd be a serious pain to go and find one to use. Is there any way I can load a custom ROM without needing to either format the SD card before doing so (so that I can put on the update.zip before I wipe the device), or some other way in general?
Another complication is that I plan to use the device without cellular service (wifi only). Would the cyanogen ROM do the "tutorial" screen in the beginning if I wanted to update to a new version? The tutorial screen on the basic OS requires cellular service, and it cannot be activated with Wifi.
Thanks. If there's anything I can explain better, tell me.

You don't need the adapter. If you have the MicroSD reader or adapter, it saves you a reboot. Just mount the SD card and copy the data to the phone like normal.

Really?
I followed the tutorial to the step where I factory reset. Then it requires that I format the SD. When that finishes, if I reboot the phone, then it brings up the Android Setup tutorial screen, and after that I'm back to the basic OS home screen. Can I load the ROM from there somehow, or would I have to re-root the phone and get back into the boot menu?
Or do you not need root to get into the boot menu?
Edit: Looks like I can. Ok, I'm a bit confused. What exactly does rooting the phone do? If performing a factory reset still allows you to access the system recovery, why did I need to root it in the first place? Or does the rooting process carry over through a factory reset?
Edit2: Also, how can I tell whether I have a 32A or 32B? I've heard that you should hold back and power when turning it on, but that seems to do nothing. I'd hate to put the wrong one on and totally screw it up.

Volume down + power key.
Hold that key combination for upwards of 5-6 seconds and it WILL display the information requested.
It should read as follows:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0006
CPLD - 10
RADIO - 2.22.19.26I
MAY 27TH 2009 19:06:41

Perfect!
I'm still wondering though, what does the factory wipe accomplish? If you can boot it up, transfer the files to the SD, and then go back into recovery mode, why must you factory reset? Or do you not have to?
If I follow what I just said, going into the base OS, putting on update.zip, powering down, booting in recovery, and loading the ROM, will it work?

Don't do that!
TheBigCheese0 said:
Perfect!
I'm still wondering though, what does the factory wipe accomplish? If you can boot it up, transfer the files to the SD, and then go back into recovery mode, why must you factory reset? Or do you not have to?
If I follow what I just said, going into the base OS, putting on update.zip, powering down, booting in recovery, and loading the ROM, will it work?
Click to expand...
Click to collapse
Absolutely NOT!
Do not ever try to apply and "update" file while the standard (T-Mobile) Cupcake build 1.5 is installed. You must "factory reset" or wipe your phone of any remaining data, which includes cache from various applications and user information. That's where Cyanogen's recovery image version 1.4 comes in handy. I suggest you research the One-Click Root Method to flash his recovery image onto your device. After you have done that; read up on numerous tutorials, finding one that you can fully understand...then go from there! Trust me, if you find some proper sources on this topic, it's quite simple - and well worth it.
BUT DON'T WORRY...when you flash that recovery image to your phone, there is a built-in feature that allows you to utilize a program referred to as "Nandroid" that will manually backup the current build on your phone. So, please believe the first thing you will be instructed to do upon flashing his recovery image is to backup your current ROM using Nandroid.
Good luck.

Thanks. The recovery flash program comes with the 1.4 version I believe. So I'll try that.
If I want to put a new version on it, I should download the img to the SD card and load it from the recovery flash application, right?
If it's that easy what is all this stuff in the tutorial about wiping the phone and SD, and needing the recovery mode?
Thanks for the help. The tutorial I was using actually suggested against flashing the cyanogen from the recovery flash program, so I skipped it.

Originally Posted by TheBigCheese0
Edit: Looks like I can. Ok, I'm a bit confused. What exactly does rooting the phone do? If performing a factory reset still allows you to access the system recovery, why did I need to root it in the first place? Or does the rooting process carry over through a factory reset?
Click to expand...
Click to collapse
I am unsure why you didn't need root to flash the RC29 image, but you definitely need root to flash a custom rom as most require you to download and install different radios and SPL's.

Arg. So I wiped the system and booted the Cyanogen 4.1 ROM. Now it's stuck at the boot screen.
Luckily I backed up. So I'm going to try the latest stable release instead with the same process.

Why even apply 4.1 build?
TheBigCheese0 said:
Arg. So I wiped the system and booted the Cyanogen 4.1 ROM. Now it's stuck at the boot screen.
Luckily I backed up. So I'm going to try the latest stable release instead with the same process.
Click to expand...
Click to collapse
4.1.2.1 is the most recent experimental build. There's no need to backtrack unless you're switching from STABLE to EXPERIMENTAL - vice versa.
WIPE, RE-FLASH, and REBOOT. Again, keep in mind that regardless of an upgrade or full-on WIPE then installing a ROM...that FIRST BOOT is going to take a while. The splash screen image should sit there for about 2-3 minutes, then your booting image, which will obviously be Cyanogen's little custom image - WILL take upwards of 10 minutes. You're only STUCK in a "boot loop" when the reflective imagery FREEZES momentarily, then starts up that same image again. That's a boot loop issue. Just keep your fingers crossed and be patient.
Good luck.

i thought you cant flash 32a builds to the tmobile mytouch?

mahfuzurkhan said:
i thought you cant flash 32a builds to the tmobile mytouch?
Click to expand...
Click to collapse
It's a 32B.
The splash screen image should sit there for about 2-3 minutes, then your booting image, which will obviously be Cyanogen's little custom image - WILL take upwards of 10 minutes.
Click to expand...
Click to collapse
Ah. That's my problem then. I let it sit for maybe about 5-7 minutes before pulling the battery.
I'll try it again.

Great! It works!
I just have one more question, but it's much more involved.
Is there any way I can get rid of the startup "android setup" tutorial screen? It seems to be tied to the device, unless Cyanogen also included it in their distribution. The problem being that if I plan to use it on wifi only, I cannot connect to the cell towers to setup the phone if I update Cyanogen.

Related

[SOLVED] HELP Installing CM 4.2 on Mytouch3G

Hey guys so I'm pretty tech savvy and i know my way around this phone but something weird's been happening. I had CM 4.2 on my Mytouch3G. I tried applying a theme which made it not boot up anymore(bootloop).
I did make a nandroid backup before but when i tried restoring with it, it keeps getting stuck at the green mt3g screen or at the second loading screen. I've tried flashing the rom again but gets stuck at the same place. If I just install the htc 1.6 update it works fine. But when I go to apply the CM 4.2 update it gets stuck again. I have wiped a million times, and fixed ext system also a bunch of times. I have also unrooted also by applying sappimg.nbh and starting over. Rooted, tried again, but nothing, still getting stuck at the loading screen. I have gotten it a couple times to go all the way to the home screen but i get com.android.phone force close.
Also i've tried going from stock htc 1.6 to CM 4.1.99 and up, not just straight to CM 4.2 so i don't know what to do.
Any help appreciated!
I seem to be having this problem as well.
Phone just freezes at MT3g loading screen.
4.1.9.2 seems to load fine, however 4.2.1 flashes properly, but phone just sits at green loading screen.
charkosh said:
I seem to be having this problem as well.
Phone just freezes at MT3g loading screen.
4.1.9.2 seems to load fine, however 4.2.1 flashes properly, but phone just sits at green loading screen.
Click to expand...
Click to collapse
Maybe a mytouch issue? Hopefully we can get some help.
lupascu.marius said:
Maybe a mytouch issue? Hopefully we can get some help.
Click to expand...
Click to collapse
You didnt say the steps you took to flash it. Did you do the step by step instructions on Cyan's OP? You cant just flash it like a normal ROM you have to do what he says on his post. I followed the steps and my MT3G works fine with it.
bluecluenj said:
You didnt say the steps you took to flash it. Did you do the step by step instructions on Cyan's OP? You cant just flash it like a normal ROM you have to do what he says on his post. I followed the steps and my MT3G works fine with it.
Click to expand...
Click to collapse
But i did say the steps...i first flashed the htc recovery image like it CM said to do. I even said in the post that i already had cm 4.2 on my phone but had to reflash after a theme froze my phone at the boot screen. I know its a different install process compared to any other rom.
Make sure you wipe before applying rom
Mr Bill Florida said:
Make sure you wipe before applying rom
Click to expand...
Click to collapse
Do people even take time to read the original post, or do they just blurt out things that sound helpful? I said towards the middle of the post that i've wiped a million times and also tried fixing ext filesystem. I appreciate anyone trying to help but please read my post carefully!
I have the same problem guys, but oly with 4.2.3.1
http://forum.xda-developers.com/showpost.php?p=4851283&postcount=3677
i HAD a similar problem when i went to 4.1.999 the first time but i fixed it.
i prefer amon ra's recovery 1.2.3g. i wiped the file system AND cache. then i did the 1.6 update followed immediately with the CM update. i rebooted and let it load up completely, then rebooted into recovery again and applied the new theme.
i actually went through the process a couple times before it worked flawlessly. it may have been a different problem though, since i was getting past the mytouch splash and about 10 seconds into the android splash before it would freeze.
jayzusfk said:
i HAD a similar problem when i went to 4.1.999 the first time but i fixed it.
i prefer amon ra's recovery 1.2.3g. i wiped the file system AND cache. then i did the 1.6 update followed immediately with the CM update. i rebooted and let it load up completely, then rebooted into recovery again and applied the new theme.
i actually went through the process a couple times before it worked flawlessly. it may have been a different problem though, since i was getting past the mytouch splash and about 10 seconds into the android splash before it would freeze.
Click to expand...
Click to collapse
Thats a good idea...i'll try amon ra's recovery image and see if there's different results. Will post back soon.
lupascu.marius said:
Thats a good idea...i'll try amon ra's recovery image and see if there's different results. Will post back soon.
Click to expand...
Click to collapse
So i tried everything from scratch but with amon ra's rec image this time. It gets passed the first boot screen and right after the second android screen it goes straight to a black screen. Have tried a few variations of installing and same thing happens everytime...This blows, i'm so stuck.
lupascu.marius said:
So i tried everything from scratch but with amon ra's rec image this time. It gets passed the first boot screen and right after the second android screen it goes straight to a black screen. Have tried a few variations of installing and same thing happens everytime...This blows, i'm so stuck.
Click to expand...
Click to collapse
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks
lupascu.marius said:
But i did say the steps...i first flashed the htc recovery image like it CM said to do. I even said in the post that i already had cm 4.2 on my phone but had to reflash after a theme froze my phone at the boot screen. I know its a different install process compared to any other rom.
Click to expand...
Click to collapse
Actually if you have an MT3G I believe you don't flash the 1.6 recovery image, but flash the 1.6 ADP rom. That is what I did since I was already rooted but with AmonRa's donut rom, but wanted to give Cy a shot, and I had no problems flashing this HTC ADP 1.6 DRC83 , then reboot manually but while rebooting I pushed home fast while it was rebooting to get me to the recovery screen, then I just flashed Cy's 4.2.2 then I went to the market and downloaded his Cyanogen updater and checked for an update, then found the update 4.2.3.1 and downloaded that straight to my phone and then choose to reboot and it automatically installed 4.2.3.1 straight to my MT3G with no problems at all.
From Cyanogen:
Download: Android 1.6 Recovery Image. (This isn’t like a typical "recovery" image we know -- it’s simply HTCs version of an update.zip.)
* Magic32A and Magic32B users only: Download this HTC_ADP_1.6_DRC83_rooted_base.zip
lupascu.marius said:
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks
Click to expand...
Click to collapse
I would go ahead and put Cy's latest back on your sd card, and also download the HTC_1.6_ADP rom if you have a MT3G (Magic 32B) or a Magic 32A and put that on your sd card. WIPE WIPE WIPE - I always wipe three times, and wipe cache also, then flash the 1.6 ADP rom then reboot but while it is rebooting hold down home to get back to recovery screen then apply Cy's on top of the 1.6 ADP rom.
I went ahead and just put Cy's 4.2.2 (instead of 4.2.3.1) on my sd card along with the HTC 1.6 ADP Rom and flashed the HTC 1.6 ADP rom first, then rebooted manually from the recovery screen, then quickly hold down home while rebooting to get back to recovery screen and applied any zip Cy4.2.2. Then when I signed in went to market to download Cyanogen Updater and set that up and then checked for updates and it found 4.2.3.1. I dowloaded that from my phone and then it was automatic from there, just asked if I wanted to reboot and apply and I said yes. Up and running with no problems so far....
mavsfan said:
I would go ahead and put Cy's latest back on your sd card, and also download the HTC_1.6_ADP rom if you have a MT3G (Magic 32B) or a Magic 32A and put that on your sd card. WIPE WIPE WIPE - I always wipe three times, and wipe cache also, then flash the 1.6 ADP rom then reboot but while it is rebooting hold down home to get back to recovery screen then apply Cy's on top of the 1.6 ADP rom.
I went ahead and just put Cy's 4.2.2 (instead of 4.2.3.1) on my sd card along with the HTC 1.6 ADP Rom and flashed the HTC 1.6 ADP rom first, then rebooted manually from the recovery screen, then quickly hold down home while rebooting to get back to recovery screen and applied any zip Cy4.2.2. Then when I signed in went to market to download Cyanogen Updater and set that up and then checked for updates and it found 4.2.3.1. I dowloaded that from my phone and then it was automatic from there, just asked if I wanted to reboot and apply and I said yes. Up and running with no problems so far....
Click to expand...
Click to collapse
That is the exact process i run thru. Sorry for the confusion, the reason i said htc recovery 1.6 is because thats what htc calls it. So i do have the htc 1.6 adp.....and i do wipe a lot also
This is probably a dumb question as I assume you would have mentioned it, but are there themes involved in any of your troubles or are you staying with stock 4.2.3.1? I only ask because I was having the same issue with the SECOND android splash crashing because I had tried to install a theme before booting into Cyanogen at least once.
I also don't think you should reboot after installing the 1.6 base like mavsfan was suggesting, though I'm not sure if it's related to your issues.
Try booting it up without an sdcard inserted. If it works that means it's your card. Card issues are very hard to diagnose and even harder to solve (other than reformat).
jayzusfk said:
This is probably a dumb question as I assume you would have mentioned it, but are there themes involved in any of your troubles or are you staying with stock 4.2.3.1? I only ask because I was having the same issue with the SECOND android splash crashing because I had tried to install a theme before booting into Cyanogen at least once.
I also don't think you should reboot after installing the 1.6 base like mavsfan was suggesting, though I'm not sure if it's related to your issues.
Click to expand...
Click to collapse
The problem i have is with the stock 4.2.3.1 not the themes...and i've also tried without rebooting after installing the 1.6 base and just go straight to applying the CM update
pascanu said:
Try booting it up without an sdcard inserted. If it works that means it's your card. Card issues are very hard to diagnose and even harder to solve (other than reformat).
Click to expand...
Click to collapse
Hey thanks for your suggestion, i have tried that, I've reformatted, I've tried different SD cards and nothing changed. I'm pretty sure the sd cards are good...
[SOLVED]Finally...
So for anyone having similar issues, here's what i did to finally get this working.
Apparently with Cyanogen's newest ROM's you HAVE to partition your sdcard, so the Rom will run on certain phones. I don't know if its all phones because there's only a few people that i've heard to have this problem. So here's the steps:
Things you will need(all these can be found in this forum)
1. Phone+sdcard
2. sappimg.nbh
3. FlashRecovery.apk
5. AmonRa's recovery image(has more options than CM's RecImg)
6. Htc ADP 1.6 stock donut rom
7. CM 4.2.3+
8. A theme(optional)(check out the Eclair 2.0 theme)
Starting from scratch
1. a. Put sappimg.nbh on sd card and turn the phone off.
b. Turn phone on by holding VOLUME DOWN+POWER
c. Apply the stock sapphire image and boot up to home screen.
2. a. Now put FlashRec.apk and AmonRa's recovery image on sdcard.
b. Install a file manager like Astro and install FlashRec.apk
c. Now open it and click Backup Recovery Image.
d. Now erase whats in the box and type /sdcard/name.of.recoveryimage.img
e. Yes you do have to type .img after the recovery image name.
f. Then click flash.
3. a. Now put the HTC ADP 1.6 Rom and CM 4.2.3+ Rom on the sdcard.
b. Reboot into recovery by holding HOME+POWER.
c. Now partition your sdcard by selecting it from the menu(the one that says +swap)
d. Now convert ext2 to ext3. After that I did:
4. a. Wipe, format ext3, wipe
b. Flash HTC ADP 1.6
c. Wipe, format ext3, wipe again.
d. Flash CM 4.2.3+
e. Wipe, format ext3, wipe one more time
f. Reboot, now it should work, give it some time to boot up.
Adding the theme
1. Make a nandroid backup before starting to save you the hassle.
2. Put your theme.zip on sdcard and reboot in recovery again.
3. Choose apply any zip and choose the theme from the list.
4. Reboot once its done and enjoy.
If anyone has any questions about anything here go ahead and reply or PM me. Have a good one guys, hope this helps anyone.
Oh and if you guys see any mistakes let me know so i can fix it, its pretty late right now

[Q] Best Nexus S GSM Rom.

Hi, I'm new to the forum, so please excuse any stupidity on my behalf.
I have a Australian, vodafone GSM Nexus S, currently running 4.0.3.
I am currently feeling stock android to be very limited, and want to move a custom rom, but I have never done any rooting/modding before. So just a couple of questions.
1) How do you root and install a custom rom? Does anybody have any video (I prefer video as I am less prone to making mistakes) tutorials for rooting and installing a custom rom for Nexus S GSM ICS 4.0.3?
2) What is the best rom, kernal etc, as I want to get my phone as smooth as ios or pretty dam close to it. Also I like changing customizing home screens, etc and would also like on screen buttons. Also I would like it to be very very stable.
3) Would it be possible to reverse all this in case my nexus screws up as the sides of my nexus are kinda creaky, and though this doesn't really effect my usability, I might end up rma'ing my phone in the future, so I would like to be able to reverse all this so it doesn't void my warranty.
4) Is there any point is overclocking and undervolting a phone. My PC is overclocked, but I have a huge fan, so overclocking would mean more heat + more battery use, and on the other hand you are lowering the voltage. Wouldn't this be very unstable?
This is my first post, so I apologize for anything I did wrong, and I did try searching, but all the roms look very good, there are some very talented devs here, and I say thanks for the help in advance.
Cheers,
Continuum
EDIT: INSTRUCTIONS ON HOW TO UNLOCK BOOTLOADER + INSTALL CLOCKWORK RECOVERY TOUCH
1. Download the CyberGR-MOD|NS.NGN ICS v8 HYBRID
http://clockworkmod.com/rommanager/d...le Nexus S
Why Cyber, seems fast, stable, and is not a beta.
2. Download and install the windows drivers for my phone (I'm on windows 7)
http://downloadandroidrom.com/file/N...ussrootICS.zip
3. Follow these until step 7
http://nexusshacks.com/nexus-s-root/...r-gingerbread/
n.b: don't worry about the cd \nexussrootthing. Just go to that folder, shift + right click, and click start command prompt instead.
4. Download clockwork recovery touch
(Link: http://downloadandroidrom.com/file/N...overytouch.zip )
and follow these instructions:
http://nexusshacks.com/nexus-s-hacks...or-nexus-s-4g/
5. Go into clockwork recovery (while still plugged into pc) and perform a nandroid back up
and click the following after:
data/factory reset
under mount and boot
format /boot
format /system
Next mount usb, and copy CyberGR-MOD|NS.NGN ICS v8 HYBRID over to sdcard, and unmount USB.
6. Plug out cable, and flash rom by going into clockwork recovery and clicking install zip from sdcard, to flash rom
7. Reboot phone and enjoy
1. NexusSHacks.com has a video tutorial on how to unlock your bootloader and Root the phone. Rooting won't be necessary to go to a custom ROM, but unlocking the bootloader is highly recommended for doing so. You will lose all personal data (including from internal SD card) once you unlock.
2. Best ROM and Kernel are the ones that fit your needs. Try a few of them, you'll find a sweet spot somewhere. The Nexus S has some of the (if not THE) best ROMs and kernels of any android, in quality, features, speed and stability.
3. All reversible from a software side. Hardware issues are covered for 1 year under warranty even if you've rooted it, technically. You can lock the bootloader and flash a stock ROM very easily.
4. Overclocking can give a significant performance increase at the cost of battery life and possibly stability. Undervolting uses very slightly less power, but generally not significant enough to notice, especially with the instability risk (rebooting will use far more power than undervolting will save you). Some chips are made more perfect than others, so some can handle high OC and extreme UV, some gag at the thought of 25mV less.
Also, remember to do a backup via recovery (NANDROID backup) when you want to try something new and when you are happy and stable with a ROM/Kernel/Settings combo. This can save lots of wasted time
Hi Harbb, thanks for the reply.
1. Sorry new to xda so couldn't link url, but I think I got it thanks, and I found one for unrooting. But how do you install a custom rom without rooting?
2. Well I was looking into roms, and codename looks good but does not come with Gapps. CM9 also looks good, but still in beta, I think I'll wait for the final release of CM9. Got any specific ones you like? Also what is the point in changing kernel?
3. Since there is a vodafone flag under your name I presume you work for voda aus? So do I have to flash it back to stock to rma it, or can I just give it in, rooted + custom rom, and expect them to replace it for me granted the phone is still <1yr, and if it is not, I guess it costs a bit to fix it.
4. But wouldn't overclocking cause your phone to overheat. Sometimes my stock nexus is sunning really hot, and other times the screen is not responsive, and I presume overclocking will just add to that. I see undervolting as a benefit, but you could just configure your phone to go into aeroplane mode/turn of 3g/etc using timerifficor tasker if battery is an issue.
Thanks for the help, but whats a NANDROID backup. Also, isn't there another one called titanium or something?
Cheers,
continuum
Nandroid is a backup you make in ClockworkMod Recovery.
Titanium Backup is a backup of all your apps (+ data).
1. Once you have an unlocked bootloader, you are given permission to use "fastboot" to flash a custom recovery. The custom recovery has, practically, full access to the rest of the system (which is essentially what root/su is). From the new custom recovery you can flash the .zip file which is the ROM, or kernel, or backup all of your files that you couldn't even access before, or format several partitions to your liking. Rooting is just copying over the su command so you can have access to the entire system, which you can't have without it.
2. CodeName Android has a seperate gapps .zip file, it's linked in the thread somewhere. Just wipe (a full wipe includes data/factory reset, format /system and format /boot, i recommend doing this between different ROMs), flash the ROM .zip first, then gapps.zip second, then reboot into your new ROM. I really liked stock. Recently i moved to Slim ICS. It's all about preference, features, etc. All of the devs here are great and there is no harm in trying out a handful of ROMs, say for about 2 days each. See which one you feel at home with. Same with kernels. Pick a handful with the features you want and try them for a couple of days.
3. No, I don't work for Vodafone. That just says which carrier I'm with. With regard to warranty, put it this way. Unless you get some serious hardware failure or storage failure, you will be able to put the phone back into the locked and stock state. If the phone just up and dies one day, feel free to send it in as-is and they should sort it out for you as it is a hardware problem. This -could- be due to overclocking, and they can argue it, but i can't recall anyone having issues like that so nothing to stress about, just don't abuse your phone. Otherwise, you can usually be able to bring it back to a locked state and in this case i would do that just in case. You can find the warranty policy here. It's quite broad, but so long as it's a manufacturing problem it is clearly covered.
4. Possibly, yes. As i said before, different CPUs are better in general than others due to variances in manufacturing. Lowering voltage may lower temperatures too, so if it is stable this could be an upside to UVing. It's all about being stable though, if your phone can't handle 1200mhz, don't OC it. If it is and you are happy with the battery life and possible lessened lifetime of the phone while stable, go right ahead. Generally no harm in trying, just go up (or down) incrementally. I'll note that while not in use, the phone should be in "Deep Sleep", which completely shuts off nearly all components of the phone aside from the radio (for cellular reception). Undervolting or Overclocking has no effect whatsoever here.
Icecoldmeat said:
Nandroid is a backup you make in ClockworkMod Recovery.
Titanium Backup is a backup of all your apps (+ data).
Click to expand...
Click to collapse
Cheers, so basically its like a windows recovery image. But for the nexus s 19203 (I think, its the slcd one), nexus hacks is saying to use TWRP. Can you still do nandroid backup with that?
Harbb said:
1. Once you have an unlocked bootloader, you are given permission to use "fastboot" to flash a custom recovery. The custom recovery has, practically, full access to the rest of the system (which is essentially what root/su is). From the new custom recovery you can flash the .zip file which is the ROM, or kernel, or backup all of your files that you couldn't even access before, or format several partitions to your liking. Rooting is just copying over the su command so you can have access to the entire system, which you can't have without it.
Click to expand...
Click to collapse
So for a beginner, your suggesting it would be easier to unlock the bootloader, and load a custom rom with root already incuded, such as CM9, right?
Harbb said:
2. CodeName Android has a seperate gapps .zip file, it's linked in the thread somewhere. Just wipe (a full wipe includes data/factory reset, format /system and format /boot, i recommend doing this between different ROMs), flash the ROM .zip first, then gapps.zip second, then reboot into your new ROM. I really liked stock. Recently i moved to Slim ICS. It's all about preference, features, etc. All of the devs here are great and there is no harm in trying out a handful of ROMs, say for about 2 days each. See which one you feel at home with. Same with kernels. Pick a handful with the features you want and try them for a couple of days.
Click to expand...
Click to collapse
So essentially:
1. Find a rom, and the drivers for my device, store these on my pc
2. Wipe phone (I presume by going into settings and pressing factory reset? and then wiping everything)
3. Turn off phone
4. Follow the nexusshacks to fastboot oem unlock and TWRP recovery
5. Nandroid backup??
6. Flash the rom
7. Flash Gapps
8. Reboot, disconnect from pc, and then let everything initialize.
9. Enjoy
Harbb said:
3. No, I don't work for Vodafone. That just says which carrier I'm with. With regard to warranty, put it this way. Unless you get some serious hardware failure or storage failure, you will be able to put the phone back into the locked and stock state. If the phone just up and dies one day, feel free to send it in as-is and they should sort it out for you as it is a hardware problem. This -could- be due to overclocking, and they can argue it, but i can't recall anyone having issues like that so nothing to stress about, just don't abuse your phone. Otherwise, you can usually be able to bring it back to a locked state and in this case i would do that just in case. You can find the warranty policy. It's quite broad, but so long as it's a manufacturing problem it is clearly covered.
Click to expand...
Click to collapse
Ahh, my bad, new to this forum, and though you were a voda rep
So I guess as long as your not extreme overvolting, you'll be fine.
Harbb said:
4. Possibly, yes. As i said before, different CPUs are better in general than others due to variances in manufacturing. Lowering voltage may lower temperatures too, so if it is stable this could be an upside to UVing. It's all about being stable though, if your phone can't handle 1200mhz, don't OC it. If it is and you are happy with the battery life and possible lessened lifetime of the phone while stable, go right ahead. Generally no harm in trying, just go up (or down) incrementally. I'll note that while not in use, the phone should be in "Deep Sleep", which completely shuts off nearly all components of the phone aside from the radio (for cellular reception). Undervolting or Overclocking has no effect whatsoever here.
Click to expand...
Click to collapse
I'll try mucking about eventually, but am a bit scared about heat build up.
Also, any word on when the full CM9 will come out?
I believe the initial estimation was around march, and by how early CM9 ROMs are going i tend to believe them. Likely more toward the end, though, before a stable is released.
A NANDROID backup basically copies: /system, /boot, /data, /cache, the recovery, kernel and .android_secure (on the sdcard). Pretty much everything android on your phone is backed up and you can go back to that exact state anytime you want by restoring, or restore each one individually. I personally recommend the ClockWorkMod, TWRP isn't in development anymore and CWM now has a touch version too, though i still prefer the non-touch myself. Just make sure to get the latest version from here.
You can feel when the phone gets hot as long as you don't have a full cover, and some apps can tell you what the battery temperature is too. Stick to what is comfortable for you. Don't be worried though, you can always just clock it back to stock speeds and volts.
Harbb said:
I personally recommend the ClockWorkMod, TWRP isn't in development anymore and CWM now has a touch version too, though i still prefer the non-touch myself. Just make sure to get the latest version from here[/URL].
Click to expand...
Click to collapse
Ok, so this is what I am going to do:
1. Download the CyberGR-MOD|NS.NGN ICS v8 HYBRID, from the link you gave me, I presume this works for i9023
2. Download and install the windows drivers for my phone
3. Root my phone, with TWRP, according to that method shown by nexusshacks
4. Then install clockwork recovery touch using fastboot flash recovery ,also shown by nexus s hacks
5. Preform a nandroid back up ?? not sure how to do this
6. Flash rom ?? not sure how to do this either
7. Reboot phone and enjoy
I am presuming Gapps in included with the rom.
Please correct anything wrong, and also, how do I get onscreen buttons? The code name rom looks like it comes with them.
!!!
I recommend you to use the latest CyanogenMod Nightlie (it's already smooth and stable enough) and some great custom kernel: AirKernel of Matrix kernel
novic_dev said:
I recommend you to use the latest CyanogenMod Nightlie (it's already smooth and stable enough) and some great custom kernel: AirKernel of Matrix kernel
Click to expand...
Click to collapse
Cool, but would I have to do the whole process all over again, once the final CM9 comes out, and does it update automatically, or must you update manually?
No need for twrp, you can flash cwm straight away. Before unlocking remember to backup all your data that you can (you will lose save games and app settings). Make sure to do the wipes I told you about or your phone may not boot or be very unstable. Copy the from .zip to sdcard and while in recovery choose to install a .zip and choose which one. It's quite simple, I'm sure you'll figure it out. Backing up is done by clicking backup of course.
There is a thread in development dedicated to onscreen buttons, that might be of use. I haven't tried it before.
Harbb said:
No need for twrp, you can flash cwm straight away. Before unlocking remember to backup all your data that you can (you will lose save games and app settings). Make sure to do the wipes I told you about or your phone may not boot or be very unstable. Copy the from .zip to sdcard and while in recovery choose to install a .zip and choose which one. It's quite simple, I'm sure you'll figure it out. Backing up is done by clicking backup of course.
Click to expand...
Click to collapse
Well I don't have much data on there, so I'm just going to copy a couple of photo's, and then factory reset, but I thought to flash cwm you have to have root first? My nexus is just pure, stock.
Harbb said:
There is a thread in development dedicated to onscreen buttons, that might be of use. I haven't tried it before.
Click to expand...
Click to collapse
Thanks, but I can't post there yet.
http://[www].androidegis.com/how-to/now-root-your-nexus-s-in-one-click-root-method/ Is this any good?
Unsure if that one still works for ICS, possibly not. There are other methods to root 4.0.3 though without unlocking the bootloader, but it often makes it much harder to do some things. Since we don't get scalded for unlocking the bootloader (and it can be undone, AND it's easy), it is the best and preferred way by most accounts. It saves alot of hassle and we are free to use fastboot if anything goes awry. Much better than needing to do that rooting procedure again, then flashing recovery within android, etc. Since you have nothing on your phone, definitely just unlock the bootloader. Nothing like freedom
Unlocking the bootloader allows you to use fastboot, as i said. fastboot allows you to flash a custom recovery (and boot with a custom kernel, and some other less-used things). TWRP and CWM are both custom recoveries, so as long as you can use fastboot (via "fastboot flash recovery recovery.img") you can replace recovery.img with twrp.img, cwm.img and so on. Same process, different file.
I'll give you another hint since you'll probably run into this eventually: Stock recovery has an android and exclamation (!) mark as a splash screen. You have to press a volume key and power button to go through that splash screen. The main time you'll see this is if you flash an official Stock ROM. There is a script that reinstalls the stock recovery on boot in Stock ROMs. To get rid of it, you'll need to rename the file /system/etc/install-recovery.sh to something else (like install-recovery.sh.bak), or just delete it. You need su to do this, of course.
Harbb,
is it "OK" before reverting to a previous NANDROID backup in CWM recovery to do format system/boot/data/cache/dalvik and factory defaults ? or not or harmful ?
What is the word on that ?
Alright, thanks guys, I will try this soon.
mahanddeem said:
Harbb,
is it "OK" before reverting to a previous NANDROID backup in CWM recovery to do format system/boot/data/cache/dalvik and factory defaults ? or not or harmful ?
What is the word on that ?
Click to expand...
Click to collapse
No need to, it is done automatically before restoring. Essentially it doesn't make a difference either way.
continuum51 said:
Alright, thanks guys, I will try this soon.
Click to expand...
Click to collapse
You're welcome, it'll all make alot more sense once you're doing it.
Ok guy, about to do it now. These are the steps I'm taking,
1. Download the CyberGR-MOD|NS.NGN ICS v8 HYBRID
http://clockworkmod.com/rommanager/...CyberGR-MOD|NS-NGN.&deviceName=Google Nexus S
Why Cyber, seems fast, stable, and is not a beta. Only question is how are updates going to work?
2. Download and install the windows drivers for my phone (I'm on windows 7)
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootICS.zip
3. Follow these until step 7
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
4. Then install clockwork recovery touch (Link: http://downloadandroidrom.com/file/NexusS/cwm/nexussrecoverytouch.zip)
and follow these instructions:
http://nexusshacks.com/nexus-s-hack...orkmod-touch-on-rooted-nexus-s-or-nexus-s-4g/
5. Preform a nandroid back up, I'm guessing this is a part of clockwork recovery, and click the following after:
data/factory reset
format /boot
format /system
From advanced, click reboot recovery, and wipe data/factory reset & cache again.
Next, storage select, format /system /data /cache /boot & format /sdcard, mount usb, and copy CyberGR-MOD|NS.NGN ICS v8 HYBRID over to sdcard.
6. Plug out cable, and lash rom by going into clockwork recovery and clicking install zip from sdcard, top flash rom
7. Reboot phone and enjoy
Before I go ahead, if something screws up, and the phone completely dies (software side), is there a way to force it back to stock? And are these steps correct?
continuum51 said:
Ok guy, about to do it now. These are the steps I'm taking,
1. Download the CyberGR-MOD|NS.NGN ICS v8 HYBRID
http://clockworkmod.com/rommanager/...CyberGR-MOD|NS-NGN.&deviceName=Google Nexus S
Why Cyber, seems fast, stable, and is not a beta. Only question is how are updates going to work?
2. Download and install the windows drivers for my phone (I'm on windows 7)
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootICS.zip
3. Follow these until step 7
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
4. Then install clockwork recovery touch (Link: http://downloadandroidrom.com/file/NexusS/cwm/nexussrecoverytouch.zip)
and follow these instructions:
http://nexusshacks.com/nexus-s-hack...orkmod-touch-on-rooted-nexus-s-or-nexus-s-4g/
5. Preform a nandroid back up, I'm guessing this is a part of clockwork recovery, and click the following after:
wipe data/factory reset
wipe/cache partition
And download the following Dalvik-wiper.zip, and wipe Cache. ?? for this, do I put it on phone sd card?
From advanced, click reboot recovery, and wipe data/factory reset & cache again.
Next, storage select, format /system /data /cache /boot & format /sdcard, mount usb, and copy CyberGR-MOD|NS.NGN ICS v8 HYBRID over to sdcard.
6. Plug out cable, and lash rom by going into clockwork recovery and clicking install zip from sdcard, top flash rom
7. Reboot phone and enjoy
Before I go ahead, if something screws up, and the phone completely dies (software side), is there a way to force it back to stock? And are these steps correct?
Click to expand...
Click to collapse
Data/factory reset also formats /cache. For a full wipe: data/factory reset, format /boot, format /system. No need to worry about any wiping .zips. No reason to do it twice either, but if you really want peace of mind do as you wish. This is ALL you need to do for wiping.
They are correct, but also somewhat redundant. Follow my wiping directions and you will be perfectly fine. If you ever want to flash a new kernel, you only need to wipe dalvik cache prior to flashing it.
Thanks mate. I've edited step 5, and am doing it now.
As i said too, no need to do the wiping again as you have at the bottom of step 5. Also note that data/factory reset formats /data, /cache and .android_secure (on sdcard), so doing the separate formats is essentially the same as doing the data/factory reset.
There is a sticky at the top of the general section with all of the stock OTA ROMs (Full and Update ones). Just wipe and flash one of the Full ROMs and you'll be back to stock in no time.

[Q] Guess I've bricked my phone, again

I was running CM10, downloaded the nightly released on 1/13.
Installed it, it rebooted, then got stuck looping again. I couldn't get it to do anything. Eventually my boot screen would go away, it would go to a blank black screen. I could see backlight, but I had absolutely nothing.
I managed to get into my bootloader, could get into recovery as well. I'm using TWRP.
I couldn't get it to do anything at all.
I eventually wiped my SD card, reformatted it, downloaded AOKP, flashed the ROM. It's started, got to the AOKP Loading screen, which it is now looping. I can't get it to do anything. I'm lost and frustrated as can be.
Any fresh ideas from anyone?
If the screen is on, its not bricked. Not knowing what to do is not a brick.
Did you factory reset, wipe data and wipe cache (all from TWRP, do not factory reset from hboot, whatever you do) before flashing?
If on hboot 1.14 or higher, did you flash boot.img via fastboot?
I restarted the entire process. I actually ended up having to do it a few times. No change in the process.
Wipe SD card. Factory Rest. Removed OS through recovery. Flashed boot. Flashed ROM. I just kept getting looping boot screens.
On another attempt it worked just fine. No change in the way I did things. I'm unsure of what the difference was or why, but its working, for now. I may end up getting a different phone instead of my Onex to see if things run smoother on my process. I have an old captivate I may try to use as a trial/error experiment.
Sent from my One X using xda app-developers app
i factory reset from hboot is there anything i can do? had the same issue with cm10
mfc1288 said:
Wipe SD card. Factory Rest. Removed OS through recovery. Flashed boot. Flashed ROM. I just kept getting looping boot screens.
Click to expand...
Click to collapse
Why do people keep wiping their SD card when flashing? I understand there are some people that do it deliberately because they like to make a "fresh" start. But it seems that the majority of people doing it are n00bs that for some reason think its "required" when flashing a new ROM, which it is not. Factory reset, wipe Dalvik, wipe cache. Nothing else "needs" to be wiped when flashing.
Remember on most devices the SD is removable, and doesn't really have much of anything to do with the flashing process, aside from the fact that you put the new ROM zip file on there (and backups go there). Its like saying you "have to" format your external hard drive every time you want to change or upgrade your PC operating system.
mfc1288 said:
I have an old captivate I may try to use as a trial/error experiment.
Click to expand...
Click to collapse
Completely different hardware, so I'm not sure what you would trying to accomplish with that experiment. I think you just had some bad luck, and bad flashes just happen occasionally. I've flashed many different ROMs on the One X, and have never had issues booting up.
CM10 seems to be giving more headaches than other ROMs, so that may have something to do with it. Not to insult that ROM or its devs. But when things change nightly, there can be glitches. And it just seems there are a lot more complaints about not being able to boot after flashing CM10 than other ROMs (despite having correctly flashed boot.img and wiped). Or maybe the number of people posting this issue is just a testament to how popular CM10 is?
---------- Post added at 10:03 AM ---------- Previous post was at 10:01 AM ----------
sinzish said:
i factory reset from hboot is there anything i can do?
Click to expand...
Click to collapse
This has been discussed on many threads already. Plug the phone to a PC, and it should show up as new hardware. Select it, and choose the option to format FAT32. After that, you should be able to mount as a USB drive.

[Q] Phone never boots after flashing new ROM

Hi!
I am currently running CM12-20150314-NIGHTLY. I am still using this old version because every time i flash a new rom the phone won't boot. It will ALWAYS get stuck on the splash screen. It will still be possible to access recovery mode, but it won't help wiping, reflashing the new version or reflashing the old version. To solve the problem i have to re run the guide for "root, ulocking bootloader and flashing recovery" to get the phone to boot again.
Do someone have an idea why the phone won't boot after upgrading to a newer rom? I have performed the process three times with different versions of the rom so i know it will happen if i flash a new rom again.
//diddi
Bump
Couple of questions. What roms are you trying to flash and where are you getting them? How long do you let it sit at the splash screen before giving up? When you say wipe, do you mean a complete data wipe? Or just a cache wipe? My thought is that it could be any of the following:
1. You just need to let it sit longer. The first boot after a new flash can take a really long time.
2. The rom may not be complete, or it could have been a bad download.
3. You aren't wiping everything and there is something conflicting.
If it's not any of those, let us know. But we need more details.
Thanks for your response!
This time i have not tried to flash a new rom, since it have not worked the past three times. Last time i think i came from CM12 20150210 to about 20150215. But that did not work, neither the previous flash between to ROMS.
1. I have let the phone load for at least 20 minutes one time, shouldn't that be enough?
2. No, really don't think that's the case, since i can't even get the phone to bot with the rom that i was previously using.
3. i have tried to wipe cache and a complete wipe, no difference
/diddi
It seems like you know what you are doing. For good measure, I would try instead of installing a nightly, just do a nandroid backup, and try a completely different rom designed for the the OPO. If that won't flash, then it may be something wrong with the recovery or bootloader.
Thank you! Will try that tomorrow when i got some spare time! I'll come back with the results!
//diddi

F***ed up badly, now downloading factory rom, need help to continue

Hi guys, I just registered @ xda because it looks like it's the only serious and feedback active community available. In 10 minutes I found most of the info I was looking for, but I still want to make sure what Im planning to do is fine before I mess up again. Here's the issue:
I was fooling around with the tablet and had just rooted it so I could get rid of some bloatware, and decided to go further and install cyanogen, just for the looks. So I got this thing cm-10.1-20130411-EXPERIMENTAL-p3110-M3 from the official site, which was I put on a folder inside the tablets storage (not on the 16gb SDcard it had in it). I downloaded Rom Manager and skipped through the "search and download rom" and went for the option of looking for it inside the SD card. I had the Backup options and the wipe cache and data ON.
So I proceeded and it booted, started to do the backup and at some final point it had an error, something like "could not backup Data!". I had the options of rebooting, some other stuff and the option of installing a rom from the SD Card. I went for it and searched for the .zip inside the storage, and installed it. It did it withouth trouble, and when it finishd it prompted me to install an update, which I didn't (don't know why).
Then, I went for the reeboot option and when it started I get the normal samsung's black screen with the device's name on it, but then I get a fast glitching image that sweeps through the screen and the cyanogen startup logo which gets stuck for ever.
Click to expand...
Click to collapse
Now Im past it, I can get to download or recovery mode, so I moved onto getting the original firmware so I can clean-install again. I got it from sammobile, chose the one belonging to Chile (that's where I got the tablet), and it's 729mb of data. The tablet is a Samsung Galaxy Tab 2 7.0 P3110
If I flash it with Odin will everything be fine? All I have to do is that thing in downloadmode when I rooted it, but with that 729mb file? Should I put it in the external SD or is it more convenient to place it in the internal storage?
I appreciate your help in advance, I know this is as basic as it gets but messing up again would cost me dearly, since I have to do other stuff.
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
billysam said:
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
Click to expand...
Click to collapse
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
aguscanzani said:
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
Click to expand...
Click to collapse
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
billysam said:
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
Click to expand...
Click to collapse
You guys have helped me a lot. I've worked everything out and now i've got to reinstalling android on it, AOSP's 5.1.1 Lollipop. It's beautiful. There's just one problem: Since it came with no apps at all, I wanted to install everything on it again. Problem is, when I go to google play, it shows that i've already got my apps installed, so it wont let me download them, and it doesn't matter if I place the APK's inside the tablet as there's no manager to open them. Even if I download apk's through the tablet's own web browser, it says it can't open the file. Any ideas on this?

Categories

Resources