Hi there,
today I started with rooting, downgrading and installing a custom ROM on my HTC Desire Z / Vision (not a t-mobile G2)
Everything went fine, except for one crucial thing:
While I can select recovery mode, it just won't proceed into recovery mode. After selecting recovery mode, the screen turns black while displaying a small image of a phone coupled with a red coloured triangle with exclamation mark.
So far that is the same problem as discussed here:
http://forum.xda-developers.com/showthread.php?p=15771495
The solution described there is to push simultaneously VOL down + Power button. Then indeed a new screen with blue letter appear, but selecting the given option "apply update.zip from sdcard" won't do the trick. Even though I named the CM 7.2 ROM as such.
It keeps on telling me that verification failed.
So in short, recovery mode does not give me the option of installing zip file from sd card.
As suggested here, http://forum.xda-developers.com/showthread.php?t=2130106 I could use an older version. But which one?
Thank you very much in advance! I am out of options and ideas basically.
Some system info
Vision PVT Ship S-OFF
HBOOT-0.85.0005
RADIO-26.03.02.18_M3
eMMC-boot
Re: [Q] Can't select install zip from sd card in recovery mode
Well my guess is you did some silly way to root which did not instruct you to install a custom recovery. You are best to follow the xda wiki to root your phone as you will get true radio soff, a custom recovery, super cid, sim unlocked, an engineering bootloader, and a better understanding of android
The triangle is stock recovery, does you know good, the bootloader you have will not allow for fastboot flashing a new one. If you still have a boot able is you could install the flash image binary, busybox, and su, then use a terminal emulator to flash a custom recovery. But you will be best off downgrading and following the gfree method to exploit your phone
Sent from my Nexus 7 using xda premium
demkantor said:
Well my guess is you did some silly way to root which did not instruct you to install a custom recovery. You are best to follow the xda wiki to root your phone as you will get true radio soff, a custom recovery, super cid, sim unlocked, an engineering bootloader, and a better understanding of android
The triangle is stock recovery, does you know good, the bootloader you have will not allow for fastboot flashing a new one. If you still have a boot able is you could install the flash image binary, busybox, and su, then use a terminal emulator to flash a custom recovery. But you will be best off downgrading and following the gfree method to exploit your phone
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for your reply.
I sure could have done something wrong, at some points the whole procedure confused me. I tried to stick with the XDA wiki guide, but there are several and all of them were useful at some points. Slowly I am getting to know this whole side of Android more, but slowly.
I actually did all the things you mention, using busybox, su and using the gfree method. But as far as I know I have not used a terminal emulator.
well there is only one guide IN THE WIKI maybe best to just start over with this guide, dont skip any step just ask a question if it confuses you
otherwise strawmetal made a great PDF GUIDE that many say is a lot easier
both methods are the same just stick with one, downgrade fully, use gfree to exploit, flash the engineering hboot and recovery of choice.
if you follow all of this completely, read and understand, it is really very easy and the long term benefits are amazing
demkantor said:
if you follow all of this completely, read and understand, it is really very easy and the long term benefits are amazing
Click to expand...
Click to collapse
Well, I did as you suggested and it did work out in the end. I really appreciate the help you gave me!!
Had a bit of trouble with actually selecting the install zip from sdcard option, as the power button wouldn't have any effect. A bit of google learned that the trackball is the proper button.
Anyway, I just had about half an hour of playtime with the CM 7.2 mod until I opted to reboot it just to see how that would go.
Unfortunately, that brought problems. After booting into the home screen it might work for some time (varies) including using apps and wifi, it will reboot randomly.
Obviously I searched for answers, there is some talk about wiping dalvik cache. So I did that (and partition wipe), and now waiting for and if the next random reboot takes place.
Edit: unfortunately, the random reboot did take place. Is it best to reinstall CM7.2 but prior to that data wipe? And after it a dalvik wipe, or should I go to 7.1?
Yeah you should always wipe everything clean prior to flashing a new ROM or update, sometimes youre OK not doing this but until you are very well immersed in android and know when you don't have to I always recommend complete wipes, superwipes, fastboot -w, whatever, just be clean
Rizzoizzo made a great guide on how to flash ROMs for beginners, you'll find it within the first few pages of general section, there you will find instructions as well as links to superwipe scripts etc. Be sure to thank him for his guide
Sent from my Nexus 7 using xda premium
demkantor said:
Yeah you should always wipe everything clean prior to flashing a new ROM or update, sometimes youre OK not doing this but until you are very well immersed in android and know when you don't have to I always recommend complete wipes, superwipes, fastboot -w, whatever, just be clean
Click to expand...
Click to collapse
Again, thank you very much for your suggestion! Without your tips it would have given me the proverbial headache.
It seems to have fixed the random reboot problem. After wiping and new flashing it never spontaneously rebooted again! I am slowly adding additional apps, and then only the ones the masses use like BBC, CNN and Firefox.
I have to say, it really is so much better with a custom rom. Loads of highly useful options you never had in the stock rom. I am really curious about the battery performance though, we'll see.
For any future readers with the same problem, the guide referred to is this one
http://forum.xda-developers.com/showthread.php?p=31249070
Related
Hello
Before i start, just like to say that I spent almost two days to read almost all posts related to my phone, but still feel I need your help.
Ok then:
I own an HTC Desire and recently asked an informatic friend to root my phone, mainly for two reasons:
- In order to install more applications, since it was always with the notification of "low memory space" and still had lots of applications to install and,
- To be able to customize, since I see many colleagues with images and icons very beautiful and I'd like to have that
After the root done, my friend installed the ROM CyanogenMod 7.0.1
I was very happy the phone came to my hands, but even before i start to install the applications i noticed that only had about 70MB free space, and then after installing some, quickly came to 30Mb, even using the App2SD. Frankly it seems to me that this program is working exactly the same way it was before the root. One part goes to the SD but another part is the internal memory. I thought with the root, the entire application would go to the SD.
I also noticed that either the cache or system applications were also in the internal memory and not in SD. So i suspect that something is lacking because something is not right.
Another question I have, and probably can be related, is that applications that came in were the Rom Manager and Superuser. However, if you open the Superuser does not appear nothing, not on the page of the application or the registration page. Do not know if it's normal.
As for the rom manager, any action that I want to do such as Install Rom from SD card, or Download Rom or Check for Rom Updates, or Partition SD Card always shows me the message "You must have ClockworkMod Recovery installed before continuing. Install the Recovery Manager through Rom first " followed by the option Install or Cancel. Has im not an expert, i decided not to install and listen to your help first. What is wrong? what should I do?
I hope you understand me (sorry for my English but im from Portugal) and i wait you can help me.
Thanks
FDinis
1. Search for SD partition guide, a2sd/a2sd+/data2ext guide, Hboot flashing guide, recovery flashing guide, rom flashing guide (in no particular order, get them all), learn and figure out what these are. So before you take a step, you know the risk.
2. Maybe your Desire got RMD Recovery on the recovery partition after rooted. So with your finishing "1." , you should know how to get a ClockworkMod Recovery.
Bad english, hope you know what I try to tell. Learn those and you'll know how to get more ram.
Thank you, but can anyone be more especific?
The rooting process installs Superuser on your phone system partition. Superuser is the app that grants root permissions to other apps. Opening it will just show you which apps have been granted root priveledges which I am guessing are none so far.
Do not use ROM manager with the desire it will cause all kinds of problems. You should already have a custom recovery installed when it was rooted.
To get more space for apps you need to install a ROM that supports A2SD+ (not the same as Froyo A2SD) and partition your sd card. ROMs available here http://forum.xda-developers.com/showthread.php?t=809328 There is a guide here http://forum.xda-developers.com/showthread.php?t=1016084 Follow steps 5 to 7 (you have done 1 to 4 already). There is another good (perhaps better) guide here http://androidforums.com/desire-all-things-root/220627-faq-apps2sd-updated-17-02-11-a.html and some more general information about rooting here http://androidforums.com/desire-all-things-root/503471-desire-all-things-root-guide.html
Alternatively you could change the phone internal partitions in conjunction with an appropriate ROM but that is more complicated.
I hope this helps.
Nick
nicka3200 said:
You should already have a custom recovery installed when it was rooted.
Click to expand...
Click to collapse
How can i know that?!
Shut down phone, then hold vol down and press power - this will take you to bootloader screen. Navigate using vol up/down to Recovery and press power to select - this should take you into custom recovery.
Edit: do you know how your mate rooted your phone? Post the details shown on bootloader screen, and what your original hboot version and software version is if you know.
Sent from my HTC Desire using Tapatalk 2
beachcomber said:
Edit: do you know how your mate rooted your phone? Post the details shown on bootloader screen, and what your original hboot version and software version is if you know.
Click to expand...
Click to collapse
How do i do that?
Sorry but i dont have experience in Android
beachcomber said:
Shut down phone, then hold vol down and press power - this will take you to bootloader screen. Navigate using vol up/down to Recovery and press power to select - this should take you into custom recovery.
Edit: do you know how your mate rooted your phone? Post the details shown on bootloader screen, and what your original hboot version and software version is if you know.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Revolutionary
Bravo PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICRO-031d
TOUCH PANEL - SYNW0101
RADIO-5.17.05.23
aUG 10 2010,17:52:18
And now?
fdinis said:
Revolutionary
Bravo PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICRO-031d
TOUCH PANEL - SYNW0101
RADIO-5.17.05.23
aUG 10 2010,17:52:18
And now?
Click to expand...
Click to collapse
And now you take 15 minutes of your oh so important life which matters to everyone here and actually READ instead of asking to be spoon fed, before I strangle somebody.
And since it was your "friend" that put your phone in that state, it wouldn't be bad to ask him first for help and explain to you what he did.
via xda app
bortak said:
And now you take 15 minutes of your oh so important life which matters to everyone here and actually READ instead of asking to be spoon fed, before I strangle somebody.
Click to expand...
Click to collapse
Bortak, why that attitud?
If you read my 1st sentence i already told that i spent a lot of time reading this forum, but unfortunatly i dont have technical knowledge so im affraid of doing something wrong.
You are not obliged to help but if you spent some of your precious time posting here, wasnt it better if you helped instead of criticizing? Isn't that the objective of forums?
Fortunatly there are some guys that do that.
Hold that fury for something more important
stankyou said:
And since it was your "friend" that put your phone in that state, it wouldn't be bad to ask him first for help and explain to you what he did.
via xda app
Click to expand...
Click to collapse
Stankyou
As i didnt like what he has done, im not asking him to do other things
Oh dear, I'll help you move on from this forum.
You have now S-OFF'd your device, meaning you can now manipulate any data that is saved onto your nand (layman's terms: built in) memory.
If you want to do further change, such as changing the operating system on your device, you need to flash a custom recovery. There is a tutorial on my guide on how to do so. Do not ask me which one to flash, remember a recovery is a recovery is a recovery is a recovery - they ALL do the same thing, some may have different features than others.
Once you have flashed recovery backup your ROM.
There are a few different variations of Android, here are A FEW you can choose from, I just picked the first one that picked the criteria.
Sense 2.0/2.1
Sense 3.0/3.5
Stock AOSP Gingerbread
Customised AOSP Gingerbread
MIUI AOSP Gingerbread
AOSP ICS (UNSTABLE)
Once you've decided what ROM you would like to choose, read the forum thread, and find out what HBOOT you need from www.alpharev.io (make sure to check the md5 before flashing, there's a tool that does this for you in resources on my guide). And flash the hboot (tutorial on my guide).
A lot of ROMs also support A2SD. For this you need to have a EXT3 or 4 partition on your sd-card. Use Gparted to make a 1024mb EXT3 or 4 partition on your sd-card. Make sure to back it up beforehand as it will be wiped.
Put the ROM on your sd-card, boot into recovery.
In recovery do a full wipe of boot, system, data, cache and dalvik cache.
Flash the ROM you wanted to use.
reboot.
That's as much help as you'll get from anyone here.
Bortak
Thanks
I'll try to do that, but i'm affraid of doing something wrong due to my (lack of) knowledge.
Well, best way to gain some knowledge is a) to read and b) to try out different things. So please, stop complaining and just do it! Most of us learned how to do things by doing them. And that's also the reason why most newbies get some troll posts when asking things.
This post is not meant to insult you, but just to give some advice. There are very few states where your phone will be totally unusable, so just give it a try.
fdinis said:
Bortak
Thanks
I'll try to do that, but i'm affraid of doing something wrong due to my (lack of) knowledge.
Click to expand...
Click to collapse
Replied to your Pm, so check your messages
fdinis said:
As for the rom manager, any action that I want to do such as Install Rom from SD card, or Download Rom or Check for Rom Updates, or Partition SD Card always shows me the message "You must have ClockworkMod Recovery installed before continuing. Install the Recovery Manager through Rom first " followed by the option Install or Cancel. Has im not an expert, i decided not to install and listen to your help first.
Thanks
FDinis
Click to expand...
Click to collapse
Looks like you haven't got a custom recovery flashed. If you are going to use ClockWorkRecovery then next time when it asks you to flash CMW recovery say Yes and follow the instructions. Personally, I prefer 4EXT recovery (you can search for it in Google play store). But you need a custom recovery on your rooted phone before you can start tinkering with it.
Sent from my HTC Desire using Tapatalk 2
SANCAH said:
Looks like you haven't got a custom recovery flashed. If you are going to use ClockWorkRecovery then next time when it asks you to flash CMW recovery say Yes and follow the instructions. Personally, I prefer 4EXT recovery (you can search for it in Google play store). But you need a custom recovery on your rooted phone before you can start tinkering with it.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
you're rocketing your way to 10 posts very quickly...spreading a little bad advice along the way
- you need to be s-off before you can start tinkering with recovery
- also, he has already been advised correctly not to use ROM manager at all...
1.Just install 4ext app from Google Play
2.Flash with it 4ext recovery, boot into recovery and do a backup of your current rom
4.download the customrom zip of your choice.
3.download the required hboot and flash it.
5.boot from the 4ext app into recovery do a full wipe
6. go to install zip from sd ( if needes toggle veryfication off before)
7.Reboot
8. finish
7.Have fun
Sent from my HTC Desire using XDA
eddiehk6 said:
- you need to be s-off before you can start tinkering with recovery
Click to expand...
Click to collapse
If i recall correctly, the timeline i followed was
stock rom
got my self root and custom recovery (clockwork) ( unrevoked.com)
custom rom, on stock hboot
s-off, custom hboot, custom rom with more space for data (alpharev.nl)
so a custom recovery without s-off is possible
Installed Andromadus 4.0 beta on my wife's G2. When I got home from work my wife said that the phone had restarted and would now only boot into clockworkmod recovery v5.8.1.0. Tried factory reset and wiping the caches and reflashing. Also tried flashing CM9 unofficial but the phone just shuts off in the middle of the flash and reboots back into clockwork. Tried to flash stockmod but I get a "can't open error". Currently the phone boots into Clockwork mod, stays on for 60 secs, then reboots itself back into clockwork mod. Help please!
maybe try to reflash your recovery, boot into fastboot and try...
When you say 'tried to flash stockmod' do you mean a PC10IMG?
Cause those are made to be flashed in hboot mode, not recovery.
-Nipqer
Nipqer said:
When you say 'tried to flash stockmod' do you mean a PC10IMG?
Cause those are made to be flashed in hboot mode, not recovery.
-Nipqer
Click to expand...
Click to collapse
Well that must be why that option didn't work. I'm pretty new to all this. Have a MyTouch I rooted a couple weeks ago that works great. But I am having fits with this one, and worse, it's my wifes phone Any other suggestions?
wipe everything in recovery, then flash a superwipe.zip (also fastboot -w is good but if your new dont worry) no flash a stable rom in recovery. i suggest elite mod, its a cm7 based rom that i personally like. all files will be found in the development threads along with any instructions needed. if you have troubles ask here again but make sure you
1 wipe all
2 superwipe.zip
3 flash rom (elitemod or whatever)
Sent from my HTC Vision using xda premium
demkantor said:
wipe everything in recovery, then flash a superwipe.zip (also fastboot -w is good but if your new dont worry) no flash a stable rom in recovery. i suggest elite mod, its a cm7 based rom that i personally like. all files will be found in the development threads along with any instructions needed. if you have troubles ask here again but make sure you
1 wipe all
2 superwipe.zip
3 flash rom (elitemod or whatever)
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
It worked! Thank you so much!
great to hear! if you used and like the rom i suggested make sure to thank the developer, it doesnt seem that too many use this rom any more but it is still one of my favorites for the g2 and the dev deserves great credit
Not really working!
demkantor said:
great to hear! if you used and like the rom i suggested make sure to thank the developer, it doesnt seem that too many use this rom any more but it is still one of my favorites for the g2 and the dev deserves great credit
Click to expand...
Click to collapse
I tried installing superwipe, and all sorts of different android operating systems but I cant seem to get my phone to get out of clockworkmod v5.8.1.0 and I can get to fastboot or hboot but it wont go passed the HTC screen. Every time I try installing an updated OS or a different OS or even doing the superwipe.zip it just says installation aborted and i can't get it to work! Any tips?
For future reference, don't go blindly flashing "Stock" images and such via the bootloader you tend to get yourself into more trouble that way (bricking, or making it difficult to get back to rooting).
Also if you're frequently using ICS roms I recommend using 4EXT Touch Recovery instead of ClockworkMod. A lot more useful tools in the recovery itself especially for wiping or formatting specific partitions.
When you get a chance check out which eMMC is used on that phone (click the eMMC name in my signature to see the poll thread which tells you how to check). Good for future reference if something acts up again.
i have a droid x2 that i have rooted and switched roms on numerous times, as well as sbfing becoming one of my close friends. not sure what to do with the 3 different pages on rooting applications and methods. does a link to actual step by step instructions on how to root and intall roms exist? last night i rooted and installed twrp using the utility, but could not get it to boot for anything. held power down and all i get is a normal boot . when i went to install AOKP , i used the utility to get into twrp RIGHT after putting FFF on it. i flashed the rom and gapps after wiping data, and i got a blank screen for an hour. i found a tutorial on mounting sd card through twrp and saved it. my question is what is the proper way to root 6.2.2? and will installing roms through working twrp actualy work? if so how do i get twrp to work? thanks in advance guys.
clarity
just to clarify , i have read all of the guides on here and have a bsic understanding (not much) of fastboot and adb. does this device need adb things done to it to work? <--- third question...lol
I used the kindle fire utility. It is a little more complicated than other devices I have rooted/rommed, but not impossible. http://forum.xda-developers.com/showthread.php?t=1399889 is the thread for KFU. You install it on your computer and follow the instructions. I soft bricked mine because I wasn't paying attention and flashed the wrong bootloader, if something like that happens there is another utility for unbrick.
Sent from my Galaxy Nexus using xda premium
Lorenzo VonMatterhorn said:
just to clarify , i have read all of the guides on here and have a bsic understanding (not much) of fastboot and adb. does this device need adb things done to it to work? <--- third question...lol
Click to expand...
Click to collapse
Yes, you use adb but it instructs you what to type.
Sent from my Galaxy Nexus using xda premium
pyroscott said:
I used the kindle fire utility. It is a little more complicated than other devices I have rooted/rommed, but not impossible. http://forum.xda-developers.com/showthread.php?t=1399889 is the thread for KFU. You install it on your computer and follow the instructions. I soft bricked mine because I wasn't paying attention and flashed the wrong bootloader, if something like that happens there is another utility for unbrick.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
i used the utility for my first blunder on this device. is the first step install permanent root? thats what i did first. then install latest twrp. did that second. said it was installed, unplugged from my computer and tried to boot into twrp. nothing. from off just hitting power sould show the triangle sign correct? if so i dont even get this.
Yes the first step should be root... which in my case also installs twrp...
If you're planning to install a custom ROM, there's no point in rooting. FFF and TWRP are more than enough.
aokp
ok well i rooted. and now twrp works flawlessly. but when i try to flash aokp, i wipe data/factory reset, install aokp and then gapps, i get nothing but a black screen after rebooting. after waiting a minute or two, i rebooted into recovery and restored a backup. am i doing something wrong? i started on 6.2.2 if that helps at all.
You should -always- wipe cache and dalvik-cache when flashing ROMs.
When you're upgrading the same ROM from a lower version to a newer one (for example, going from gede 1.65 to 1.7) you may skip factory reset, so long as there isn't a major change (going from normal to linaro, for example).
However, it is good practice to let Titanium Backup handle all of your /data backups and just factory reset every time as well.
You have the two most important steps done.
1. You have TWRP installed and you can boot into it. That is one of the hardest steps it appears.
2. You did a backup before doing anything else.
As Dasanko said you also need to wipe cache and dalvik-cache. When I do a new rom I wipe data, system, cache and dalvik-cache.
Titanium Backup (TiBu) is also awesome to restore your apps. However, you will need to install TiBu to use it to restore other apps. Some ROMS have it installed already and some don't. If you don't have access to TiBu from the Rom your are flashing you will need the GApps installed to get the Play Store. You can then download TiBu be able to restore your chosen apps.
Lorenzo VonMatterhorn said:
i used the utility for my first blunder on this device. is the first step install permanent root? thats what i did first. then install latest twrp. did that second. said it was installed, unplugged from my computer and tried to boot into twrp. nothing. from off just hitting power sould show the triangle sign correct? if so i dont even get this.
Click to expand...
Click to collapse
Yes, you should get the screen with the triangle. I would try flashing the recovery again
Sent from my Galaxy Nexus using xda premium
also when you are installing a new rom I always wipe system so you dont have any errors because that is where the old rom is located. btw cm9 and aokp are both really nice on this device
Hi All, let me start with a warning…
total Android n00b here, doing his first ROM flash on a newly rooted T-Mobile G2. I’ve read and searched a bit in the forum threads to see if I could solve this on my own, but I do need help.
VISION PVT SHIP S-OFF
HBOOT - 0.82.0000 (PC1010000)
MICROP - 0425
RADIO - 26.02.01.15_M2
eMMC - boot
Aug 20 2010, 16:51:01
This is from using the instructions in Strawmetal’s PDF guide to Downgrading from Gingerbread to Froyo and Root. I am working with a G2 phone that was set to Factory Reset before rooting, so there is no user data to backup or worry about.
1. I downloaded the Andromadus Mimicry 1.1.2 ROM image, and verified the md5 checksum on my sdcard using the AFV Legacy application. The Gapps image also was verified as well.
2. Using ROM Manager 5.0.0.8 from the Google Market, I ran Clockwork Recovery to install the Andromadus image. I left all settings on defaults and the installer ran fine.
3. When it restarted, I was left stuck at the white HTC screen for ages… the longest I left it was 20 mins. After that, I pulled the battery and restarted. Same white HTC screen.
4. I tried using Volume (+) key and Power On to get back to Clockwork Recovery, but the phone vibrated (buzzed) 3x times quickly, and the Power LED lamp pulsed an amber color. Again, yank battery, restart, same white HTC screen.
5. finally I decided to read more of the help for adb, and found the command “adb reboot-bootloader”. This let me get into the default Recovery mode, and it proceeded to find the PC10IMG.zip I still had on the sdcard from doing the Froyo downgrade. Recovery checked it out, ran it and restored the stock Froyo image and my phone did a proper restart. WHEW.
After that, I had to run adb to install the hboot recovery image file, and the busybox checksums were valid according to Strawmetal’s PDF instructions to get permanent root back after restoring the stock Froyo image.
I have done this process about 4 times, and am really good at typing inside adb now
But I’m lost…
-did I pick a ROM that doesn’t work with the G2? Other posters to the forum thread appear to be using the HTC Vision or G2.
-is ROM Manager not a good way to install a ROM?
-when I tried to get back into Recovery, what do the 3x buzzes/amber power LED mean?
-I never got to install the Gapps image; was I supposed to install that first, then the ROM image?
I imagine I did something wrong (duh!), but I can’t spot it. If someone can help me through this, I’d appreciate some advice very much.
thanks!
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Hi Nospin,
Thank you very much for your suggestions!
I will revise my root and remove Clockwork, and switch to 4EXT instead.
I appreciate the idea of "superwipe"; I will look for that as well today.
If I understand everything right...
-replace CWM with 4EXT
-place superwipe.zip, Gapps.zip and the Mimicry ROM.zip on the top level of the sdcard first.
-reboot the phone and run 4EXT recovery
-select superwipe to run first, then the ROM and then Gapps
-then restart the phone
When I used CWM before to install the ROM, it rebooted on its own before I could install Gapps. Will 4EXT let me do each install right after each other or do I have to return to 4EXT for each separate install?
regards,
motionmonk
Nospin said:
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Click to expand...
Click to collapse
Hi blk_jack,
I went back to the Mimicry page and re-read the FAQ section.
I think what I got out of it the first time was that if the ROM flash failed, it could be a corrupt ROM image. I will definitely use 4EXT to repartition before I try again with a ROM flash.
I guess I am still getting used to the terms for everything; can 4EXT do the nandroid backup? or is there a better process for setting that up?
thank you!
motionmonk
blk_jack said:
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Yes, you should be able to flash the rom and then GApps without rebooting. Give me a few and I will send you a PM with a few links....
Shot you a PM.
Thanks! I'll check it out :good:
Nospin said:
Shot you a PM.
Click to expand...
Click to collapse
Update-not working
Ok...
I re-flashed back to stock Froyo, and did a permanent root.
Installed 4ext Recovery (instead of Clockwork), and got a copy of SuperwipeG2+ext4;
I copied new checksum'd copies of Mimicry 1.1.2 ROM and GApps to my sdcard.
Booted into 4ext Recovery and installed from .zip the SuperwipeG2+ext4 file.
System, data and cache are all converted to ext4 partitions.
Wiped the system and data and cache partitions.
Installed from inside Recovery the Mimicry ROM and then the GApps archives.
No errors reported.
Upon reboot, I still get the white HTC screen. UGH.
I've left it on in that state for 30 mins... I had to yank the battery after that in shame...
I have tried to make sure that I read up on background steps, and I feel I do understand the overall process, but something is still getting in the way. I am doing this as I mentioned in an earlier post on a factory reset G2 with a clean erased SD card (has the stock Froyo image, Andromadus Mimicry ROM and GApps only). There is no SIM card installed either, wifi is off (to avoid OTA upgrade requests).
Are there other things I can try, or info I can supply that would help? I think I'm so close to getting this done... I must be overlooking something obvious.
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Hi amogil,
Just to be sure I understand, are you saying you are swapping between Andromadus and CM9 beta on your phone?
Did you flash CM9 first? and then Andromadus?
or just carrying the CM9 beta image and running Andromadus?
Sorry, I'm all sorts of confused here lol
thanks
amogil said:
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
It's definitely a thought, and I believe that's what amogil is telling me too...
Ya, I can try a different ROM and report back.
I guess I should go back to stock Froyo and then start from CM7.2, and if that boots, try Mimicry again?
-from the Andromadus FAQ, it says it if a different ROM is based on ICS9, you shouldn't have to wipe. But with CM7, I'd have to wipe the Dalvik cache, yes?
-since CM7 is obviously not based on ICS9, would being able to launch into that show some details I can't see at present? Just was curious.
Or, do you think it better to go stock Froyo and then the older Mimicry ROM?
Either way, I'll make sure that I use the Superwipe to set things to ext4 first.
thanks guys for the ideas,
motionmonk
Nospin said:
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
Click to expand...
Click to collapse
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
SUCCESS!
Woohoo!
It works!
Since I had an ICS9 ROM already in place and was planning to wipe back to stock anyways, I tried flashing the older Andromadus 1.1.0 ROM.
What a surprise and treat to see the startup animation!
After poking around for an hour inside it, I then tried Recovery to reflash to the newest 1.1.2 ROM.
YAY! It works!
OMG, having a new ROM is like having a new phone-- there are so many improvements to the UI and it's quick and speedy versus GB. Dang, I'm happy now :victory:
Observations:
1. I did notice that inside Recovery, my touchscreen was barely functional when I tried to update from 1.1.0 up to 1.1.2-- I had to use the Volume +/- and the d-pad button to make selections. After the flash, the touchscreen is as responsive as ever.
2. it's got me thinking, that there must be a setting that is expected in the v1.1.2 ROM that the v1.1.0 ROM installed. Or could something else be the issue? I mean absolutely no disrespect to the developers... but on the technical side, I'm just curious what possibilities exist that might lead to this situation.
3. backup question... when I use MyBackup Pro, I know I can make an archive of the apps I've installed, and an archive of the data (documents, music, settings). Is a nandroid backup different from that? when I see the backup/restore options inside of 4ext Recovery, what are those doing that's different from what I get from MyBackup Pro?
thanks for all the help and encouragement. I have a new ROM installed! :good:
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Oooh, a possibility. We will see if he can boot a different rom.
Whenever you switch roms (even if they are using the same Android version as a base) I suggest a full wipe. (Wipe all user data + Dalvik Cache + Cache, or just flash the superwipe zip). When upgrading the rom you are currently on (say upgrading CM Nightlies or going from Mimicry 1.1.1 to 1.1.2) you only need to really wipe cache and dalvik cache. Unless the dev states otherwise of course.
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank You All!
A big shout out to:
Nospin
blk_jack
amogil
strawmetal
for taking the time out to help a total n00b stumble through his first ROM flash.
I really appreciate the points you guys made, and the help provided.
Thank you!
I hope that one day I can help someone else out with a problem and pass the kindness forward.
Yay! I have a working ROM!
motionmonk
motionmonk said:
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
Click to expand...
Click to collapse
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
WOW. i just realized there is SO MUCH I need to catch up on!
I'll have to look up some of these guides later today... but the RUU is the ROM upgrade, right?
Did you ever find a reason why you got the false S-OFF flag? It's clear that the way I was looking at the failed fre3vo exploit as proof of S-OFF isn't always going to be true... but how would you separate a false S-OFF flag from lets say a wrong hboot image?
BTW, your PDF on downgrading and rooting the G2 was a godsend. Very very helpful and clear.
One of the reasons why I took so long to try rooting was that I was confused by the different methods and the replies of X not working, Y is a better way... going through your guide and the info here on xda cleared alot of things up. :good:
strawmetal said:
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
Click to expand...
Click to collapse
Hi,
I'm new here so please go easy on this "noob"
It was my first to unlock and root my phone, followed by flashing a stock ROM (Which is exactly why I rooted it)
I flashed this JB 4.2.2 stock build [ROM] [OTA][GSM] Android 4.2.2 JDQ39: Rooted | Galaxy Nexus > XDA for my Galaxy Nexus
Now...
I can't disable Next-word suggestions in the Language & Input -> Google Keyboard Settings
Also, I noticed a few seconds of lag when pressing the power button to unlock the phone, when viewing recent apps (via the soft-key), and when opening the Camera too
Also, when I choose the "Recent Apps" soft key.. it's as the app that's currently being used is minimised and the homescreen is shown without any icons
The Build came with Busybox pre-installed and now its gone after a day of using my phone... I literally can't find it.
I searched in the play store "BusyBox" and the result is 3 different apps with the same name!
Any Advice?
AMKhatri said:
Hi,
I'm new here so please go easy on this "noob"
It was my first to unlock and root my phone, followed by flashing a stock ROM (Which is exactly why I rooted it)
I flashed this JB 4.2.2 stock build [ROM] [OTA][GSM] Android 4.2.2 JDQ39: Rooted | Galaxy Nexus > XDA for my Galaxy Nexus
Now...
I can't disable Next-word suggestions in the Language & Input -> Google Keyboard Settings
Also, I noticed a few seconds of lag when pressing the power button to unlock the phone, when viewing recent apps (via the soft-key), and when opening the Camera too
Also, when I choose the "Recent Apps" soft key.. it's as the app that's currently being used is minimised and the homescreen is shown without any icons
The Build came with Busybox pre-installed and now its gone after a day of using my phone... I literally can't find it.
I searched in the play store "BusyBox" and the result is 3 different apps with the same name!
Any Advice?
Click to expand...
Click to collapse
go back to recovery, format/wipe /system partition, reflash rom.
For your reference, a good app to install bb is stephen (stericsson)'s busybox installer (play store link). Obviously, it needs root.
Next time, read the stickies.
http://forum.xda-developers.com/showthread.php?t=1812959
How do I get “root”?
If you are booted into a custom recovery (recoveries will be covered later), root is enabled by default. If you want root while booted into Android, you will need to place two files on your system partition: an “su” binary which grants root access, and a superuser app that manages that access. The two that are available are ChainsDD’s Superuser and Chainfire’s SuperSU. Usually these files are packaged up in a zip file that is flashable using a custom recovery, but they can be flashed manually using ADB. Both of these methods will be described below.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=26328017&postcount=123
As you probably noticed by now, you didn't need to flash a full "custom stock ROM" to root.
beekay201 said:
go back to recovery, format/wipe /system partition, reflash rom.
For your reference, a good app to install bb is stephen (stericsson)'s busybox installer (play store link). Obviously, it needs root.
Next time, read the stickies.
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showpost.php?p=26328017&postcount=123
As you probably noticed by now, you didn't need to flash a full "custom stock ROM" to root.
Click to expand...
Click to collapse
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PS: Do you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...
AMKhatri said:
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PSo you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...
Click to expand...
Click to collapse
You can wipe the system partition in a custom recovery (dont know if you can with stock). And yes you could flash via ROM manager but I wouldnt recommend it. I am on XenonHD 11.1 and loving it. But roms are a personal choice so there is no 'best' ROM. Just try out.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can wipe the system partition in a custom recovery (dont know if you can with stock). And yes you could flash via ROM manager but I wouldnt recommend it. I am on XenonHD 11.1 and loving it. But roms are a personal choice so there is no 'best' ROM. Just try out.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
The tutorial I followed didn't mention using the ROM manager, but I had not choice.. becuase whenever I went into fastboot mode manually, it got stuck on the screen displaying Google (I waited for minutes without any luck)
How would you recommend CyanogenMod 10.1.2 against the stock 4.2.2 which I have currently?
I read these threads as well whereby they said that there is no "real" solution to the issues:
http://forum.xda-developers.com/showthread.php?t=2178962
http://forum.xda-developers.com/showthread.php?t=2363872
AMKhatri said:
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PS: Do you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...
Click to expand...
Click to collapse
Mr., please, read the LINK i gave you! THIS ONE ->>>> http://forum.xda-developers.com/showthread.php?t=1812959
If you read it, you'll stop thinking you need to be doing anything at this point in FASTBOOT interface! Like mrgnex says, you need to be on a custom recovery to format /system. (Have you read the link yet? By now you should know that the /system partition and the /sdcard/ (aka userdata) are 2 different things!)
mrgnex said:
You can wipe the system partition in a custom recovery (dont know if you can with stock). (...) roms are a personal choice so there is no 'best' ROM. Just try out.
Click to expand...
Click to collapse
+1
For your reference, you can't erase /system in stock recovery.
AMKhatri said:
The tutorial I followed didn't mention using the ROM manager, but I had not choice.. becuase whenever I went into fastboot mode manually, it got stuck on the screen displaying Google (I waited for minutes without any luck)
How would you recommend CyanogenMod 10.1.2 against the stock 4.2.2 which I have currently?
I read these threads as well whereby they said that there is no "real" solution to the issues:
http://forum.xda-developers.com/showthread.php?t=2178962
http://forum.xda-developers.com/showthread.php?t=2363872
Click to expand...
Click to collapse
Stop! THERE'S NO NEED FOR FASTBOOT HERE!
Thanks Guys for replying.
Yes, I read the info in the link, it was very helpful.
I'm still confused though.. "Fast boot" and "Recovery" are they the same thing?
I tried a "fix" mentioned by someone about using a live wallpaper such as "Water", I tried it and it's been 1/2 hour and it's really smooth compared to before...
Yes, I do have a custom recovery, actually I don't know why, but It seems I've got two according to ROM Manager.
It says I've got Clockwork Mod Recovery & TWRP.
I also tried going into recovery (Volume up + Down + Power) and it worked this time, when I select recovery, it goes into CWRM
I also did a bit of research about CyanogenMod 10.1.2 and from what I could gather it's liked by people a lot.
I'm guessing that definitely some time ahead it'll get all "laggy" again, Is there any reason according to you why I shouldn't install it compared to the stock 4.2.2 I have?
AMKhatri said:
Thanks Guys for replying.
Yes, I read the info in the link, it was very helpful.
I'm still confused though.. "Fast boot" and "Recovery" are they the same thing?
I tried a "fix" mentioned by someone about using a live wallpaper such as "Water", I tried it and it's been 1/2 hour and it's really smooth compared to before...
Yes, I do have a custom recovery, actually I don't know why, but It seems I've got two according to ROM Manager.
It says I've got Clockwork Mod Recovery & TWRP.
I also tried going into recovery (Volume up + Down + Power) and it worked this time, when I select recovery, it goes into CWRM
I also did a bit of research about CyanogenMod 10.1.2 and from what I could gather it's liked by people a lot.
I'm guessing that definitely some time ahead it'll get all "laggy" again, Is there any reason according to you why I shouldn't install it compared to the stock 4.2.2 I have?
Click to expand...
Click to collapse
So to get things clear:
No fastboot and recovery arent the same thing.
Vol up+down+power brings you into fast boot and not recovery.
Apparently you dont have 2 custom recoverys since you booted into cwm.
Cm10 is great. But there are many great roms out there. You can start off with cm and then (if you please) look further.
I dont see any reason to not install cm10.1.2 since a whole team built and optimized it. So basically it is a better stock.
When you think your phone is slow you should look into the custom kernels. Thats a different story which I will not begin before you want to
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
So to get things clear:
No fastboot and recovery arent the same thing.
Vol up+down+power brings you into fast boot and not recovery.
Apparently you dont have 2 custom recoverys since you booted into cwm.
Cm10 is great. But there are many great roms out there. You can start off with cm and then (if you please) look further.
I dont see any reason to not install cm10.1.2 since a whole team built and optimized it. So basically it is a better stock.
When you think your phone is slow you should look into the custom kernels. Thats a different story which I will not begin before you want to
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! Now it's definitely clear!
I'll download CM10.1.2 tomorrow and will decide to install it once Stock JB 4.2.2 starts acting up again.
In the meantime I'll read on about kernels, please keep don't close this thread...yet.
clerk usdEuro
I've decided that I will test out the Rom that I have currently (4.2.2) for a few weeks, and then flash CM.
I wanted to know one more thing, Is it bad to flash ROMs to your phone every now and then?
Because I've seen people flashing different ROMs on their phone, I don't wanna damage my phone as I want it to last as long as I can make it.
(by "Bad" I mean... does it reduce the phone's life or it's hardware's life span)
AMKhatri said:
I've decided that I will test out the Rom that I have currently (4.2.2) for a few weeks, and then flash CM.
I wanted to know one more thing, Is it bad to flash ROMs to your phone every now and then?
Because I've seen people flashing different ROMs on their phone, I don't wanna damage my phone as I want it to last as long as I can make it.
(by "Bad" I mean... does it reduce the phone's life or it's hardware's life span)
Click to expand...
Click to collapse
No it can't. I was a flashaholic (until I discovered XenonHD) and my phone didn't got worse. Only overclocking the CPU and gpu can affect the life of the CPU or gpu (or both XD). Just do a fresh install everytime and read the post of the ROM of your choice to see what to do to get it working optimally. If you have any problems just ask.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
No it can't. I was a flashaholic (until I discovered XenonHD) and my phone didn't got worse. Only overclocking the CPU and gpu can affect the life of the CPU or gpu (or both XD). Just do a fresh install everytime and read the post of the ROM of your choice to see what to do to get it working optimally. If you have any problems just ask.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thanks...
I'll flash CM in a week or two, as I'm on a tight schedule currently, and I also wanna note down the average battery time I get out of 4.2.2
So... since 4.3 is now out, I was thinking it'd be better for me to flash it other than anything else.
I'll most probably download the stock rom from:
https://developers.google.com/android/nexus/images#yakjujwr66v
So far I came across this thread having the steps to flash 4.3
http://forum.xda-developers.com/showthread.php?t=2377307
But I wanna flash it and lose my data, so that it's as fresh as it can be...
Will that work if I use "wugfresh root toolkit"?
AMKhatri said:
So... since 4.3 is now out, I was thinking it'd be better for me to flash it other than anything else.
I'll most probably download the stock rom from:
https://developers.google.com/android/nexus/images#yakjujwr66v
So far I came across this thread having the steps to flash 4.3
http://forum.xda-developers.com/showthread.php?t=2377307
But I wanna flash it and lose my data, so that it's as fresh as it can be...
Will that work if I use "wugfresh root toolkit"?
Click to expand...
Click to collapse
With the stock package there is no need for a toolkit.
Hell, there's no reason for a toolkit any time.
Sent from my Galaxy Nexus
Pirateghost said:
With the stock package there is no need for a toolkit.
Hell, there's no reason for a toolkit any time.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
What was I thinking...
I apologize guys... I guess I wasn't thinking straight as its past midnight here...
So just to clarify stuff so that I don't end up doing something wrong:
-> Head into Recovery Mode (with usb debugging enabled... connect usb cable to phone and pc)
-> Wipe System
-> Wipe Cache
-> Install from SD card (select .zip file)
right?
Also, I performed a backup of the applications I have via Titanium Backup, They'll work on 4.3 when I restore them right? or do you recommend downloading them from the play store again?
Sorry for being such a noob, and Thanks for your responses!
backup everything from your /sdcard to your computer, titanium backups and a nandroid
the google stock package is NOT flashable in CWM/TWRP
if you follow the GOOGLE instructions it WILL wipe your device (remember that backup you made of everything?)
alternatively you can make sure and have adb/fastboot working on your computer properly, extract all the files out of the zip (including the tar.gz located inside), and in recovery, do a factory reset, then boot to fastboot, fastboot flash system and boot ....
as for Titanium Backup, there is a work around to get it working on 4.3, but root is lacking full power.
Pirateghost said:
backup everything from your /sdcard to your computer, titanium backups and a nandroid
the google stock package is NOT flashable in CWM/TWRP
if you follow the GOOGLE instructions it WILL wipe your device (remember that backup you made of everything?)
alternatively you can make sure and have adb/fastboot working on your computer properly, extract all the files out of the zip (including the tar.gz located inside), and in recovery, do a factory reset, then boot to fastboot, fastboot flash system and boot ....
as for Titanium Backup, there is a work around to get it working on 4.3, but root is lacking full power.
Click to expand...
Click to collapse
Thanks!
I'm now on Android 4.3
I'm full of excitement atm :victory:
I took a backup of my apps using titanium backup, I installed it but can't use it, it says I need root (which I already had before).
I read online somewhere that I need to root again, but I don't wanna lose all my data/ apps I installed again...
Any ideas?
If I use Wugfresh Nexus Root Toolkit... will I lose my data?
Thanks for the continued support!
AMKhatri said:
Thanks!
I'm now on Android 4.3
I'm full of excitement atm :victory:
I took a backup of my apps using titanium backup, I installed it but can't use it, it says I need root (which I already had before).
I read online somewhere that I need to root again, but I don't wanna lose all my data/ apps I installed again...
Any ideas?
If I use Wugfresh Nexus Root Toolkit... will I lose my data?
Thanks for the continued support!
Click to expand...
Click to collapse
Seriously, how hard can it be for you people to waste 5, 5!!! minutes to browse the forums.
http://forum.xda-developers.com/showthread.php?t=2377318
Thanks!
According to a friend's recommendation I used Wugfresh Nexus Root Toolkit to Root, and surprisingly didn't lose any of my data!
Once again, Thanks for all the help everyone... You've all been quite helpful.