Related
Hallo,
I've been trying to install the updated to update-cm-4.2.7.1-signed.zip.
I've been able to install first the signed-dream_devphone_userdebug-ota-14721.zip and imediatly after that, without reboot, the update-cm-4.2.7.1-signed.zip. Only I was unable to sign in to google right after that so I rebooted and then I was unable to boot it any longer...
Ok so then I retried the whole process but now after flashing the first signed-dream_devphone_userdebug-ota-14721.zip, wich goes ok, the second update-cm-4.2.7.1-signed.zip aborts the installation...
Next to it the installation of signed-dream_devphone_userdebug-ota-14721.zip isn't stable at all... after max one minute the phone crashes, so I'm unable to do anything....
I'm feeling extremely NOOOOOOBY!!!...
Which is probably how I'm supposed to feel...
Uuuugh....
Anyways is there anyone with hints about what I'm doing wrong here?
Thanks!
Greetings,
Geert
did u do a full wipe from CM recovery before putting on the google updates then cyanogen??? i had this issue and it fixes it?
Sorry for the late reply...
I tried to flash the recovery image of cyanogen but itś not possible anymore....
There is no flash_image tool on signed-dream_devphone_userdebug-ota-14721.zip...
Also using fastboot, it says < waiting for device > till eternity...
my advice would be to start from scratch, get dreaming.nbh on ur sdcard. follow the instructions @ cyanogens wiki
i was having a world of **** on my G1 and just went back to RC29/RC7 and started again. if you have the files already on the SD card (CM recovery, official google, latest cyanogen mod) its simply a case of a few key presses.
dont forget to do the telnetd stage. i did and then wondered why i didnt have root access lol
ive never bothered with fastboot, usually just use ADB!
r|ktk|ng
As the thread title states, I'm looking for info on the steps to root my stock MT4g, and install the new ROM that's floating around. I'm pretty technically capable, but the info I've found looks slightly dated. When I was active in the iPhone jailbreak scene, using old directions could brick a phone pretty easy, or prevent future jailbreaking. I haven't kept up with this scene enough to be able to know what's dated and what isn't.
This is my current plan, please correct it if I'm missing anything or have it wrong.
(based on wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide)
I've got ADB going
I need a backup solution for app data right? What's my best option here?
Once backed up, I plan to install busybox, Superuser package & Temporary Root package via ADB
Use gfree to make that root permanent
Install ClockworkMod recovery
Reboot into recovery, and install faux123's ROM
Does that sound correct, and did I skip anything? Any input at all is welcome, I'd like to stand tall on the backs of giants.
There are two popular methods floating around
You can either use the Root.sh method [ Found Here ]
Or the ./gfree method [ Found here ]
Either method will work perfectly. I've used both and can say with confidence they work.
The Cyanogen method can be goofy at times. I've see alot of people say they cannot get it working for them. I'd rock one of the two above. You shouldn't have a problem either way.
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
For backing up apps and data, use titanium backup. for backing up your whole phone, use the backup feature in clockworkmod recovery after you've flashed it via rom manager after permarooting.
lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
The best way to back up your Data and Applications is like mentioned above is Titanium Backup. The free version will work well but i recommend the paid one.
as far as a snap shot of the entire ROM incase you want to go back to it. reboot into recovery > backup/restore > backup. And it will do the rest.
Well I made it halfway there, but didn't nail the whole thing. I've got permanent root access (yay) now, and was able to make backups via Titanium. I then rebooted the phone into "recovery" using the ROM Manager from Clockwork. First boot had a red exclamation mark, I unplugged the handset from the USB and tried a second time. After that, I was greeted with the Orange and black interface, and selected "restore to factory". I then started searching for the cache clearing, which changed verbage between 3.x and 4.x releases of Clockwork. After exploring the menus a little, the phone reboots itself from this screen. My blood-pressure goes up, and I worry my toy just became a b-word. Not all was lost though, and the phone happily booted into the stock t-mobile welcome wizard.
I still have superUser installed, and still have root (S=OFF I guess?). I install ROM Manager again, and do the "Flash ClockworkMod Recovery" (which now shows both current and latest recovery as ClockworkMod 3.0.2.4). When I choose Reboot into Recovery however, it reboots back to the MyTouch 4G logo screen (non-animated one), and hangs. After some reading I tried to force recovery boot via ADB, which produced the same result as the soft reset from ROM Manager. After that I tried doing it the manual way with holding the volume button, which launched me into what I believe is a stock recovery console (white with colored options, uses vol +/- and power to navigate). Choosing "recovery" from that screen *also* produces the white logo screen hang.
So my question now is, in it's current state; how can I get to the Clockwork recovery again? From there I bet installing the image will be easy street, but I believe I'm stuck for now.
Side-note: the phone functions fine on regular boots and pure vanilla mode; I just don't want to stop here when I'm pretty close to my 2.3 goal
Well good news and bad news. I was able to get Clockwork going by reverting it to 3.0.0.5 and just using that version. Was able to install ROMs, tested a few. Phone started freezing after/during installing packages. Started the clear cache/install ROM process, ran into this:
Code:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
http://forum.xda-developers.com/showthread.php?p=14389074
Totally stuck at boot screen, but able to get into Clockwork. All ROM zips off the sdcard produce this or an invalid zip error.
Other guy smight tell you what a status 7 might be, but with the flurry of flashing youre doing, you may have gotten some corruption on your sd
try formatting your sd card in the pc, or use another one so you dont have to back everything up on this one. put one rom zip on the root and see if that helps
also, i would make super sure you wiped/factory resetted every possible data/cache in CWM before flashing the zip
lastly, i would md5 test the download to make sure it matches the web page. Plus, after it's transferred to the cleanly-formetted sd, check it again either thru adb, or do the trans on the pc using an sdcard reader and check it once it's on the sdcard, then pop it into back your phone.
good luck
Thanks a ton for the uber fast reply. When I format on the PC, what format do I use, or is there a specific tool to properly format it for the phone?
When I'm wiping /data it's taking forever and I get the following message back:
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log/last_log
E:Can't open /cache/recovery/log/last_log
Don't have an adapter at the office today for the sdcard, but I guess I can just grab a new one at lunch? All it would need is a fresh format then the .zip of the ROM in question at the root?
Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.
Jack_R1 said:
Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.
Click to expand...
Click to collapse
So I use the same PD15IMG.zip i did to start, flash it using Clockwork, then start the root > rom process over? I think that it currently tells me it can't find that zip anymore on the white screen pre console, is that expected? I just xfer it to the sdcard prior to fixing?
Yes, that's the right procedure. Move it to the card and start from scratch. Beware not to use the newer Panache/MT4G Gingerbread RUU, otherwise you'll be left with no way to root, or at least harder way.
Ok, so I didn't have a PD15IMG.zip to begin with, I see this thread:
http://forum.xda-developers.com/showthread.php?t=1059347
and that's proper that I'm flashing the radio itself for this process? Which of those images do I want to grab? I always like to double check when I read warnings that are pretty specific about bricking the device
No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.
acsi007 said:
No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.
Click to expand...
Click to collapse
Jesus, glad I asked before getting in there.
So I was going to offer you a beer sometime, I think I owe you a few rounds at this point...
Edit: this one right http://forum.xda-developers.com/showthread.php?t=924923 ?
Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...
acsi007 said:
Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...
Click to expand...
Click to collapse
I rooted gfree originally, and think I may be in the bad place
Fail-PU errors running the update from pd15img. Do I have any options at this point? I bought the phone from Wirefly.com, and since I can't get a recovery image going, I may be fuct here on a return eh?
looks like i'm moving to: http://forum.xda-developers.com/showthread.php?p=14487111#post14487111
Good luck Lars. Let us know that they did and if you had to pay.
To keep it relatively short, for whatever reason, my recovery is corrupted or broken. I had flashed clockwork, did a full backup, and have my UID and all of that stuff. Today, sometime after I started downloading files from Google Music, my tablet restarted, and now programs and applications constantly crash, presumibly since the tablet seems to be locked in Read Only mode. Chmod seems to work, but then nothing actually changes. Ive been able to seemingly uninstall root, and reinstall it, but its a hassle, and I dont think that works correctly.
Obviously, without recovery, I cannot flash anything, and without being able to write correctly, I cant get it to update. Acer Recovery says that it is successful, but it is not, and simply reboots the tablet.
One user described it as "GroundHog Day" as the tablet returns to the state it was in previously.
So yeah, I need help getting recovery back and working again, so I can either wipe this rom or do something entirely different. Thanks!
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Borman18 said:
To keep it relatively short, for whatever reason, my recovery is corrupted or broken. I had flashed clockwork, did a full nandroid backup, and have my UID and all of that stuff. Today, sometime after I started downloading files from Google Music, my tablet restarted, and now programs and applications constantly crash, presumibly since the tablet seems to be locked in Read Only mode. Chmod seems to work, but then nothing actually changes. Ive been able to seemingly uninstall root, and reinstall it, but its a hassle, and I dont think that works correctly.
Obviously, without recovery, I cannot flash anything, and without being able to write correctly, I cant get it to update. Acer Recovery says that it is successful, but it is not, and simply reboots the tablet.
One user described it as "GroundHog Day" as the tablet returns to the state it was in previously.
So yeah, I need help getting recovery back and working again, so I can either wipe this rom or do something entirely different. Thanks!
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Click to expand...
Click to collapse
Are you using Iconia Root to root and unroot? Let's start there?
Off to bed, I'm sure one of the other "late nighters" will be able to help you.
My only question is that you stated you installed CWM, if so, why didn't you create a full backup with it instead of nandroid?
Yes, I used Iconia Root to do the deed, which has worked since I got the unit a week ago until today.
And thats what I mean in terms of backing up, my apologies (im just use to calling it Nandroid for whatever reason).
I have no idea how the recovery got wiped though.
Borman18 said:
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Click to expand...
Click to collapse
I STRONGLY recommend you read the following thread.
http://forum.xda-developers.com/showthread.php?t=1129873
Looks like you flashed something and didn't run "itsmagic".
Ive tried that, and no go. As far as I can remember, I havent flashed anything in days, since updating to the latest update a few days ago. And its been fine since then, until today. I started downloading google music stuff, went to the bathroom, came back and my tablet was off. I can give it another go though.
If it wasn't clear, I can definitely boot, its just with all those errors
But you get a checksum error, right? Have you gone through the steps in that thread that detail how to fix the checksum error?
If so, I suggest you contact sc2k.
Correct, if I hold the volume - and power, it gives that error. Just ran through the steps for the "<CASE 1> SOS checksum error" again to be safe, and its the same. I PM'ed him earlier (maybe twice..), but I can only assume he's sleeping, so I was just trying to see if anyone has any ideas.
Edit: from my ADB Shell session, just to show that it seems to want to work anyway? But of course, the same old..
# /data/local/itsmagic
Some magic trick by @sc2k on xda
it tricks the bootloader to run any kernel you want.
Thx @Acer for making this so easy.. why did you say the BL is locked if it isn't?
USE AT YOUR OWN RISK!
Done. Have fun!
# exit
Your best option is to wait until sc2k gets back to you, then. Don't worry. He's a fairly nice guy and has helped plenty of folks sort out similar issues on their tabs. Just remember to beer him afterwards!
Of course Thanks for your help regardless, I figured it was worth a shot. Of course, it does this right before I am to go camping for a few days (I had some maps and stuff on here to use as backup).
Borman18 said:
Of course Thanks for your help regardless, I figured it was worth a shot. Of course, it does this right before I am to go camping for a few days (I had some maps and stuff on here to use as backup).
Click to expand...
Click to collapse
AH, y'see, now you know what caused it in the first place! You tempted the fates! Never tempt the fates, for they are mean and sadistic beings that just LOVE to screw with folks right before they go camping.
I hope sc2k is able to help you out.
Hey everyone,
I'm having trouble getting my Nexus 7 to update to 4.2.2. My device is rooted, I recently performed a factory reset.
The update has never appeared in my "System updates" menu, so I looked around and saw that if you force stop "Google Services Framework" and clear its data, the update will appear in "System updates."
It did, but when it finishes downloading, it says "Verification failed."
I tried another factory reset, and I had to again force stop and clear data on "Google Services Framework" to get the update to appear, but again it downloads and say "Verification failed."
I'm stumped now. Do I have to unroot and reroot? Do I have to keep waiting for this update? Do anything with the bootloader? (I really hope not...)
Thanks everyone!
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Leonhan said:
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Click to expand...
Click to collapse
Is flashing the stock 4.2.1 rom the same thing as doing a factory reset to 4.2.1?
If it isn't, would flashing the 4.2.1 rom wipe my tablet?
Leonhan said:
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Click to expand...
Click to collapse
If he is trying to do an OTA to 4.2.2, would it not be more straightforward to just flash the 4.2.2 factory image? The OP has already done a factory reset, so it doesn't look like he/she is particularly attached to his current setup.
Also - the language he used was vague - it sort of sounded like the OP observed "verification failed" in the main OS rather than in the recovery. Not sure.
But it doesn't matter - newbs should not be trying to use OTAs on modified /system images or tabs with altered boot images. It's just too detailed a process to describe compactly.
@Horadrius
Before you do anything further, you should back up everything on the "SD Card" to your PC. Yes, all of it. You can throw it away later if you find you didn't need it. But if you follow the instructions for the Google (factory) images install, everything gets wiped off of /data including your pseudo - SD card.
At a minimum, that will allow you to follow the SBS instructions for installing the 4.2.2 factory images, or - you can simply install a 4.2.2 Stock ROM from over in the dev forum.
Whatever you do, start getting in the habit of making backups - and at least occasionally also getting copies of those off of the tablet.
Oh boy, lot of information to digest here....and a lot of questions
it sort of sounded like the OP observed "verification failed" in the main OS rather than in the recovery. Not sure.
Click to expand...
Click to collapse
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
newbs should not be trying to use OTAs on modified /system images or tabs with altered boot images.
Click to expand...
Click to collapse
So, no updating the device from System Menu because I'm rooted/unlocked bootloader? I'll have to flash everything as it comes out?
@Horadrius
Before you do anything further, you should back up everything on the "SD Card" to your PC.
Click to expand...
Click to collapse
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Horadrius said:
Oh boy, lot of information to digest here....and a lot of questions
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
So, no updating the device from System Menu because I'm rooted/unlocked bootloader? I'll have to flash everything as it comes out?
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Click to expand...
Click to collapse
Sounds like your download is bad if it fails at this stage. I believe it is saying the checksum of the download file doesn't match whatever is downloaded.
PS. not related to N7, why XDA use the re-captcha which I need to refresh several times to get something I can read
Horadrius said:
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
Click to expand...
Click to collapse
No. It means that for some strange reason, running a checksum program on the downloaded OTA file failed to produce the expected checksum. The most likely way this can happen is that the file is truncated - the download stopped short of the full file. Don't know why this is happening, but there you go. There could be other failure causes that are more rare, but it doesn't mean you are not "supposed" to have the OTA. It means that the download process is failing.
The *stock* recovery does a number of even more sophisticated checking than this; but it appears from your description that the recovery never even gets booted.
Horadrius said:
So, no updating the device from System Menu because I'm rooted/unlocked bootloader?
Click to expand...
Click to collapse
Yes and No. An unlocked bootloader causes no problems at all. ANY of the following CAN or WILL cause problems:
- attempting to run an OTA with a custom recovery installed instead of the stock recovery.
- having a modified boot partition (e.g. non-stock kernel, or slightly modified boot partition)
- having altered (or removed!) files in the /system partition that are targeted for patching.
- permissions changes performed by the installer script can cause root functionality to disappear
Horadrius said:
I'll have to flash everything as it comes out?
Click to expand...
Click to collapse
Not sure what you are asking here, but the basic answer is that if you stay on stock you can certainly apply OTAs easily. If you start altering things, you might or might not be able to apply an OTA; there are simply no guarantees.
[size=+1]OTAs are meant for stock installations - including a stock recovery. PERIOD. While it is possible that an OTA could succeed, it is unreasonable to have the expectation that it will do so.[/size]
Horadrius said:
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
Click to expand...
Click to collapse
I presume you are talking about the future here, as you said that you already did a factory reset at least twice. If you have subsequently added stuff back in, then I suppose you might be talking about the present tense.
But, yes - either TiBu or the Carbon app can be used along with a strategy where you simply back up the apps & data you are interested in, (plus any "flashable zips" that you used to customize your device in the first place), and you simply start from scratch with a factory install followed by re-rooting, and then restore your apps & data (using TiBu or Carbon).
One other thing you can do which is EASY is this: simply wait until a developer/ROM cook publishes a "Stock" flashable ROM based on the release that the OTA is upgrading to. Don't worry about the OTA, just wait a little bit. (These ROMs are already out for the WiFi-only model, BTW).
1) Take a backup as the first thing you do. It's easy and gives you some insurance.
2) Don't wipe (no "factory reset") - just install the Stock ROM over the top of your existing ROM.
that's it. If you were using a custom kernel, re-install it.
Horadrius said:
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Click to expand...
Click to collapse
[size=+1]OTAs are meant for stock installations - including a stock recovery. PERIOD.[/size]
Interpret that as you desire. It is unreasonable for you to expect that you can diddle with your phone any way you please, and a patch install upgrade methodology will be robust in the faces of arbitrary changes on your part. You are the person creating the maze, not Google.
Moreover, it is your choice to take an upgrade - it's not mandatory. My guess is your tablet was quite pleasing to you before any OTAs started rolling out. Nobody is forcing you to do anything.
OK, one last thing. It is still possible that a manual OTA can succeed on your phone if it is lightly rooted - but there are no guarantees. The procedure does not require you to wait around until an OTA arrives on your phone, but it is not for the faint-hearted:
1) Download the appropriate Stock OTA File.
2) Re-install the stock recovery onto your tablet. You will have to dig it out of the Google full factory image for the version of the OS you are currently running. (available here)
Code:
fastboot flash recovery factory-4.2.1-recovery.img
3) Soft-boot into a custom recovery, e.g.
Code:
fastboot boot openrecovery-twrp-2.4.1.0-grouper.img
5) Using the command line and adb to communicate with the soft-booted recovery, create a recovery command file:
Code:
C:\myPCsux> adb push 6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip /cache/update.zip
C:\myPCsux> adb shell
# cd /cache/recovery
# cat > command
--update_package=/cache/update.zip
^D # ( that is a Control-D character )
# sync
# reboot recovery
This will either succeed or fail. Based on your comments though, you might just want to overflash a Stock-derived ROM over the top of your existing ROM (a "no-wipe" install).
[ROM][Factory Image][4.2.2] Nakasi -::- Odex, Deodex, Rooted -::- teshxx (02/14/13) <-- NOTE for WiFi (nakasi/grouper) ONLY
good luck with your tab.
Someone once said "Rooting is a lifestyle". There's some truth to that; it eats up your time. Perhaps it is not for you.
Thanks, bftb0.
Looking through your list of reasons for why my OTA might not work, none of them applied to me.
I didn't install any custom recovery (didn't install Clockwork Mod recovery specifically to avoid dealing with flashing roms) or kernels or modify any partitions, nor to my knowledge changed any files in the /system section.
I think I'm going to give this update a week or so to pop up on my update menu before I start tinkering again.
Don't get me wrong - I enjoy this kind of tinkering, and all the perks of rooting, but my knowledge is extremely limited, which is what makes it frustrating trying to find information. The only thing I've done before this is install Cyanogen on my HP Touchpad.
Anyway, do I need to install CWM recovery to flash (overflash?) that 4.2.2 rom you linked?
if you haven't done anything other than rooting(i.e. copying a file su to it), OTA would go through. Your problem is about the download process. It can go wrong for many reasons from the download is bad to what saved to the temp area(where the download is) is bad(rare but still possible).
chimpanzeexda said:
if you haven't done anything other than rooting(i.e. copying a file su to it), OTA would go through. Your problem is about the download process. It can go wrong for many reasons from the download is bad to what saved to the temp area(where the download is) is bad(rare but still possible).
Click to expand...
Click to collapse
That's all I've done, root and unlock bootloader. The download only showed up when I cleared data and force stopped the "Google Services Framework" process. I reboot the system, and check for the update and nothing is there.
well, sounds like you have to flash it manually using fastboot then.
That said, I myself have no intention of doing the update any time soon as I don't find any specific problem with 4.2.1 and there isn't any specific feature i want in 4.2.2
Horadrius said:
Anyway, do I need to install CWM recovery to flash (overflash?) that 4.2.2 rom you linked?
Click to expand...
Click to collapse
TL;DR Yes and No.
People that use toolkits seem to use hard-flashed installs of custom recoveries, as they don't really understand what goes on under the hood, even if the toolkit offers them a means to soft-boot any image the toolkit operator downloads. (I assume that the toolkits probably allow this; as I don't use them I don't know for sure.)
What I am saying is that the answer depends on your knowledge. So long as you have an unlocked bootloader, you can soft-boot any boot image you like - including custom recoveries.. (This also pre-supposes correctly-functioning device drivers, but that is a Windows/user training issue, it has nothing to do with Android).
When I say soft-boot, I mean that the image is transferred to the tablet, which then hands over control and starts executing that image - but it is not "flashed" to Flash memory, so the next time a boot occurs, the same boot images are still stored in either "boot" or "recovery".
In this configuration, the phone should be much more likely to complete an OTA as it will have the stock recovery present most of the time, and only temporarily present when you attach to your PC and kick things off with a custom recovery.
The OTA could still fail, but it probably would succeed for a very lightly rooted stock configuration (other than problems with losing root).
The only downside to this arrangement is that you can't be flashing roms or making nandroid backups or other forms of rooter activities when you are away from the PC.
For the IT-OCD or obsessive ROM hopper, that could be a good thing.
good luck... the rest is up to you.
Ok, I installed Clockwork Mod from a toolkit because going into fastboot and choosing "Recovery mode" led me to a picture of the Android guy with a red triangle on his back saying "No Command."
I'm just going to install 4.2.2 myself now. Question regarding that link - odex/deodexed - I looked up the difference but can't tell which one is appropriate for me - I'm guessing it's odex because that seems to be closer to stock.
Edit: It worked! Thanks for your assistance, everyone!
IMO, google should not ship odex image now that we have fast enough hardware. odex is just a form of 'pre-compilation' which only benefit first time load(or when the cache is cleared). Too little gain for such a complicated setup.
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Kenchi* said:
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Click to expand...
Click to collapse
Im having the same issue too
Kenchi* said:
I am unable at the moment with TWRP to mount my /system partition, which therefore has lead me not to have the ability to flash a custom ROM, but also at the same time I am ROMless, I have access to Recovery, at the moment, I'm attempting to sideload a Stock Rooted zip of my AT&T G2 ROM. However, I believe it won't have any progress, but I'm attempting anything at the moment in order to get my phone running.
Currently stuck on TWRP flashing a ROM and stuck on "Formatting" once again.
Any help would be appreciated. Quite frankly, I am scared out of my wit that I have bricked my phone, however there is some hope left in me with the fact that I have Recovery still running.
Click to expand...
Click to collapse
Try this? http://forum.xda-developers.com/showthread.php?t=2451696
I finally solved the issue, miraculously, nothing was working so I just left the phone to continuing formatting for an hour so, came back, and it seemed to have done it, I installed Custom ROM, and it booted up normally, I'm not sure what triggered the phone to accept the system mount, but I am sure as hell happy it did. I was worried I was going to have a bricked device on my hands.
Hold strong, just allow the phone to continue doing what it needs to do I guess. Leave TWRP in all STOCK settings, I tried to modify multiple settings based on Devs saying to get a faster formatting to enable RM-F but I have no clue why and what didn't work.
Anyhow, problem resolved!
On another note, I would never use the recommended method from Droid_<3er as they would completely brick your phone unless you're specifically in the situation listed in that thread. As you would put your phone into a state where you lose both access to Recovery and ROM access, rendering your phone to a piece of plastic and metal. But it's definitely worth mentioning, I just had to do some research on the method cause I had the same thinking as well.
I can confirm by using normal make_ext4fs while formatting /system is the best way to avoid this. Was afraid of having a 5.2 inch brick, but thankfully, disabling the quick way to format has fixed it and allowed /system to be remounted.
I think (<-- that's the disclaimer) that it's OK to use the fast formatting method for Dalvik Cache and Cache, but not for System.
in my opinion it's best to use rm -rf /system aka delete_recursive("/system"); than formatting
I'm having the same issue, and I'd be willing to try this one. How would I do this?
I have the same issue with CWM and now got over to twrp with the same outcome.
Right here I see solutions that worked so far, but it seems like this was rather accidentially.
I want to try some of these, but in the thread posted above
"Try this? http://forum.xda-developers.com/show....php?t=2451696"
it says "Do it the wrong way and your phone might get nuked"
unfortunately it doesn't say what the commands in there mean...
Can anybody be of assistence which method will properly work without nuking the phone?
I have the MOTO G 2014 (2nd Gen)
It is an updated bootloader
i got the latest twrp
and some titan roms.
only stock rom will work so far,
custom roms will result in a bootloop.