Hi there,
yesterday succesfully rooted my device using the insecure boot image.
Today booted and also flashed the new CWM recovery image but now, when booting into recovery only get an android logo and the text "no command" ?
Any ideas ? Flashed back to original recovery image but no change either ?
Root remains though and working fine.
Thanks
CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app
n7of9 said:
CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Not true read here again :
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
Click to expand...
Click to collapse
has anyone reported it working?
Sent from my Nexus 7 using xda app-developers app
It seems tonight clockwork will release a new version with bugfixes which should make recovery working when flashed also.
Sent from my Nexus 4 using xda app-developers app
New clockworkmod recovery 6.0.1.8 had been released and I can confirm myself that it is working perfectly and stays when flashed !
You can download it here and follow the instructions as written here.
Good luck !
excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)
n7of9 said:
excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)
Click to expand...
Click to collapse
Meanwhile a newer 6.0.1.9 is released as well, which will hopefully also fix the backup being in the wrong location and not usable
CWM is fixed. Read this thread: http://forum.xda-developers.com/showthread.php?t=1995440
6.0.1.9 is the one i flashed and I'm still looking for my backup :s
n7'd from my n7
Disregard this post! It was meant for LBE which is a Virus or acts like one (Newest version that was translated)
I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?
k3nav7 said:
I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?
Click to expand...
Click to collapse
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD
El Daddy said:
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.
k3nav7 said:
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.
Click to expand...
Click to collapse
No problem! Glad to help!
Sent from my Nexus 7 using Tapatalk HD
No Command recovery problem
Hello im using a Canvas Magnus A117 its an amazing phone i rooted it but wanted to install chainfire 3D on it but it didnt work and now my phone is bricked. I tried flashing a custom rom but in recovery when i click on apply update from sdcard it says No command. with a dead android and a red triangle with !. So i cant use any feature in the Recovery mode and my phone is bricked. What do i do?
Related
Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message
IAmNice said:
usb debugging on? Have you checked that?
Click to expand...
Click to collapse
Hi. Yes mam (usb debugging on) have a look to the attachment.
Toolkit me boot into fastboot then reboot then for something to fastboot loaded and back to android and trying to upload the files but nothing superuser is not recorded because of (read-only file system).
have a look on the attachment is there to see everything ...
yep same issue here - problem with the forum regs is unless you have enough posts you can't actually address the issue to the appropriate person can you? Anyway, able to unlock but then is unable to root and rest due to a permissions problem. have tried as administrator but of coure this doesn't make any difference.
NexusTropers said:
Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message
Click to expand...
Click to collapse
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.
try:
http://forum.xda-developers.com/showthread.php?t=1796109
comminus said:
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.
Click to expand...
Click to collapse
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.
bazabaza said:
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.
Click to expand...
Click to collapse
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.
comminus said:
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.
Click to expand...
Click to collapse
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.
NexusTropers said:
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
Click to expand...
Click to collapse
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
NexusTropers said:
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.
Click to expand...
Click to collapse
I'm not really sure what you're trying to say...
I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.
comminus said:
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
I'm not really sure what you're trying to say...
Click to expand...
Click to collapse
1. THX u i try it.
2. AH sorry translator make crazy text.
homerbrew said:
I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.
Click to expand...
Click to collapse
Oki THX u i try this tool...
I'm also having this same problem but here's my story:
Using the Nexus 1.5.4 Toolkit, I Unrooted + Flashed jzo54k, success. I locked OEM, success. I unlocked again, success. Then I ran the root process again, and it keeps freezing at the android recovery screen. Following the prompt in the toolkit, I walked away for a few hours hoping time would resolve the issue.
If you're wondering why I unlocked + rooted, and decided to unroot, lock, unlock, and root again, its because I'm super-noob to anything android related after version 1.5, I wanted to learn the processes after I found out I was having troubles with certian things after my Nexus 7 updated from 4.1 to 4.1.2
I am having the same issue as you. 4.1.2 is not rooting for me. I can't install CWM or TWRP because it needs to rename recovery files, and to do that you need to be rooted. If I boot in recovery I always get stock
Having the same issue with a stock 4.1.2. I can unlock no problem but I cannot get it rooted. Everything appears to have worked, but it is not rooted. If I revert back to 4.1.1 I can unlock, root, etc. without issue. I was able to root 4.1.1 and use the root keeper app to then update to 4.1.2 and I was rooted still. However, it would not let me install CWM or anything. ROM Manager says it was installed, but booting to recovery always too me to stock.
Any ideas?
Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app
MetalMadness said:
Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I used Nexus Root Toolkit v1.5.4 and selected the "Flash Stock + Unroot" option. When prompted I choose the default 4.1.1 option and away it went.
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!
hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Indy1204 said:
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!
Click to expand...
Click to collapse
Thanks. I did this earlier and it didnt work, but I checked boot instead of flash
FLASH THE OLDER BOOTLOADER DON'T BOOT IT!!!
Can you please help me answer how to install OTA updated with CWM installed. I get this error saying the installation aborted .. it boots into CWM
is there any step by step method to get the new update on nexus 4
Thanks
you need stock rom, no modifications made, and stock kernel for it to work
Download and extract the original 4.2 and fastboot flash system system.img and it'll restore all missing apps.. I had to do it earlier to allow the system to install the update
Sent from my Nexus 4 using xda app-developers app
I reflashed stock recovery but now the update isn't available. Any ideas?
billybennett said:
I reflashed stock recovery but now the update isn't available. Any ideas?
Click to expand...
Click to collapse
update manually.
So I got my update but it keeps failing during install. I'm rooted and every time the update starts it kicks over to CWM recovery and stops with a message something like, "do you want to install this untrusted zip file" I say yes but it still fails. I have even tried to manually install the update through CWM but that fails too. My N7 is rooted but otherwise stock, I have not removed any stock apps or flashed roms or kernels so WTF must I do???
Did you not read the posts above yours? CWM recovery is not stock.
Sent from Arkham
zelendel said:
Did you not read the posts above yours? CWM recovery is not stock.
Sent from Arkham
Click to expand...
Click to collapse
I don't know where, but I saw a few posts about working updates to 4.2.1 with CWM recovery.
However, I'm not getting it to work.
How do I get rid of the recovery without loosing the root?
If you are on Windows I find the Nexus 4 Toolkit to be super easy to use. I flashed a stock recovery so I could get the update. Unfortunately, I forgot I had made changes to the stock weather widget so I can't apply the update anymore because of a missing geniewidget.odex file.
You will need to be fully stock to get the update to take as posted earlier in this thread. This is a well known requirement when doing OTA
Sent from Arkham
4.2.1 update getting installation aborted
Hey, can some please post the stock Nexus 4 v4.2 build.prop file? I can't seem to install the v4.2.1 update without it...
Thanks...
zelendel said:
You will need to be fully stock to get the update to take as posted earlier in this thread. This is a well known requirement when doing OTA
Sent from Arkham
Click to expand...
Click to collapse
Successfully installed OTA here while rooted with CWM recovery, though everything else is stock.
billybennett said:
If you are on Windows I find the Nexus 4 Toolkit to be super easy to use. I flashed a stock recovery so I could get the update. Unfortunately, I forgot I had made changes to the stock weather widget so I can't apply the update anymore because of a missing geniewidget.odex file.
Click to expand...
Click to collapse
Hey,
got an Error over here with stock recovery and root.
However, tengen says he made it with CWM and root - maybe it's because I'm using stuff like Busybox or the Pimp my Rom APK?
EDIT: I think its because of the %-BatteryMod I'm using. I'll try to flash the custom rom.
Greetings
I get stucked showing an android laying on its back with the triangle thing on its tummy.
I have to randomly press my hardware buttons to get to CWM
is there anyway I can fix this that when I choose recovery mode it will go directly CWM?
That is the stock recovery. Not clockwork recovery.
I'm guessing you used the command "fastboot boot" instead of "fastboot flash" when trying to flash recovery.
Sent from my Nexus 7 using Tapatalk HD
El Daddy said:
That is the stock recovery. Not clockwork recovery.
I'm guessing you used the command "fastboot boot" instead of "fastboot flash" when trying to flash recovery.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I was able to flash the CWM already tho.
I'll just reflash the CWM.
This could be your problem too.
From efrant's N4 101 guide:
" I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick."
Sent from my Nexus 4 using xda premium
reflashed CWM. its still not sticking.
El Daddy said:
This could be your problem too.
From efrant's N4 101 guide:
" I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick."
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
okay I'll try this. but a got a quick question if I rename both of them (install-recovery.bak & recovery-from-boot.bak) will this possibly brick my device? or nothing major will be affected?
It won't brick your device.
Sent from my Nexus 4 using xda premium
El Daddy said:
It won't brick your device.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
thanks man. got it working. it doesn't show the stock recovery anymore. (renamed both files).
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!
hettige677 said:
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!
Click to expand...
Click to collapse
Hello there!
What about a little search? is a search bar in every part of the forum!!!
Anyway there you go:
http://forum.xda-developers.com/showthread.php?t=1745781
Just don't get used to it :good:
Read the forum rules!
So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app
n/m
hettige677 said:
So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
That's because you are using a custom recovery. You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
Leonhan said:
That's because you are using a custom recovery.
Click to expand...
Click to collapse
Possibly, but probably not. In most of the reports that have been coming in - when the users actually report the full error message rather than saying something ambiguous like "I got a Status 7 error" - the problems revolve around altered/removed files in /system, or having a custom kernel (boot or LNX partition) installed. That suggests that the recovery version is not causing assert() failures.
The other thing to rememder is that the program that is interpreting the edify updater-script is the "updater-binary" program which is shipped inside the OTA - so it is virtually identical independent of the choice of recovery (other than perhaps kernel behavior differences).
Leonhan said:
You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
Click to expand...
Click to collapse
Even though what you are saying here does only require being able to operate a plain-text editor and a zip tool, it's way above the heads of most folks who think that OTAs should work on non-stock ROMs. And I'm not sure how these folks would be better off with partially-patched ROMs. In any event, if this course is taken indeed a custom recovery would need to be used for this, as modifying the zip contents will break the OTA package signing, so the stock recovery couldn't be used.
The OP should just
- make a full nandroid backup of what they have now
- download the factory 4.2.2 images from Google
- extract the system.img file and boot.img images
( hint for windoze users: 7-zip understands .tgz files)
fastboot flash boot boot.img
fastboot flash system system.img
- reflash a basic SuperSU or Superuser root kit
Sort of crude, but it's a decent hack for the lazy or poorly informed. It won't "erase my data", but presumably it will break whatever it was that altered the stock system and/or boot partitions - the very things that are causing the OTA to fail on them with their rooted & modified ROMs.
If they don't like the result, they can simply restore their nandroid backup.
So I got the OTA update, but after downloading it, the install failed (dead android says: error), then the Nexus 7 reboots to 4.2.2.
I already did a factory reset, but it didn't help either...
Anyone with the same issue?
Video:
Same problem here. I haven't fixed it yet either.
Why is the right door always locked?
hasbrobot said:
Same problem here. I haven't fixed it yet either.
Why is the right door always locked?
Click to expand...
Click to collapse
I got this problem...
I download this OTA...Then it say reboot to install but it enter TWRP.
Then I put the zip to internal storage and flash but I got error.
Sent from my Sony Xperia™ sola using XDA Premium
Ben Ling said:
I got this problem...
I download this OTA...Then it say reboot to install but it enter TWRP.
Then I put the zip to internal storage and flash but I got error.
Sent from my Sony Xperia™ sola using XDA Premium
Click to expand...
Click to collapse
looks like your SystemUI.apk has been modified not in original. I would recommend to get copy of systemUI.apk from stock 4.2.2 and copy it to your tablet and using file explorer, replace it. and give a try.
jazzespresso said:
looks like your SystemUI.apk has been modified not in original. I would recommend to get copy of systemUI.apk from stock 4.2.2 and copy it to your tablet and using file explorer, replace it. and give a try.
Click to expand...
Click to collapse
yeah i have modified my SystemUI before.and also framework-res...
but i didn't save my old SystemUI,can you upload?
Sent from my Google Nexus 7 using XDA Premium App
Ashenphoenix said:
So I got the OTA update, but after downloading it, the install failed (dead android says: error), then the Nexus 7 reboots to 4.2.2.
I already did a factory reset, but it didn't help either...
Anyone with the same issue?
Video:
Click to expand...
Click to collapse
my OTA failed too, different error. this usually always the case if /system/ folder integrity check failure (error 7), means files in /system/ folder are not original or modified. Yours does not give any details, but I bet it is. to see what error, try to flash it thru CWM or any other custom recovery you use.
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Ben Ling said:
yeah i have modified my SystemUI before.and also framework-res...
but i didn't save my old SystemUI,can you upload?
Sent from my Google Nexus 7 using XDA Premium App
Click to expand...
Click to collapse
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
jazzespresso said:
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
Click to expand...
Click to collapse
okay...will my data be erase when installing?
Sent from my Google Nexus 7 using XDA Premium App
---------- Post added at 09:07 PM ---------- Previous post was at 08:48 PM ----------
jazzespresso said:
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
Click to expand...
Click to collapse
Tried your SystemUI,don't work...keep on stopped...so I replace back...
Sent from my Sony Xperia™ sola using XDA Premium
I guess I'll download the Nexus Toolkit, click on the flash stock + unroot button, so it flashes the stock 4.2.2 and then I'll try to OTA update again.
I already unrooted, but I think it's not a problem.
Seems like it is not fixable!
I used fast boot to push my missing file.
I used es file explorer.
I used titanium back up to make the app, system...
No way, nothing. Not the slightest luck.
(My missing app is xt9ime.apk)
I haaaaaate this situation.
the worst thing is that xt9ime.apk is asus keyboard, and it is disabled by google on nexus 7.
why should not having an app that they don't want to use be a problem. X(
Sent from my Nexus 7 using XDA Premium HD app
Are you guys with errors using SuperSU? If so what version?
It seems like that the last couple versions touch a file used by OTAs. The Dev recommends using the "Full Unroot" option in the SuperSU app prior to accepting the OTA.
jaysus145 said:
Are you guys with errors using SuperSU? If so what version?
It seems like that the last couple versions touch a file used by OTAs. The Dev recommends using the "Full Unroot" option in the SuperSU app prior to accepting the OTA.
Click to expand...
Click to collapse
I did full unroot, and I also did a factory reset, but it still fails to install.
Using Wug's Toolkit to flash stock 4.2.2 is a good idea?
Then try to OTA update 4.3 again?
Same problem
Hi,
I think I have the same problem:
What to do?
You cannot install the full image from Google using fastboot? Just back up your data(if you can) then try a fresh install.
Sent from my Galaxy Nexus using Tapatalk 2
chrisinsocalif said:
You cannot install the full image from Google using fastboot? Just back up your data(if you can) then try a fresh install.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
What is Fastboot?
Theuntje said:
What is Fastboot?
Click to expand...
Click to collapse
Sadness.
Fastboot is a utility used to control the base fastboot firmware on many Android devices. It lets you do low-level actions such as flashing a custom recovery, ROM, or kernel. Toolkits run fastboot behind the scene, but automate the commands for newer users.
I had exactly the same problem and after trying a few things, I just found a working solution for my Nexus 7.
I used the same tool I used to unlock and root a few months ago: Nexus Root Toolkit 1.6.3.
I made a backup of my files first, my idea being to reflash the 4.2.2 rom
I downloaded the system file here: https://developers.google.com/android/nexus/images#occamjwr66v
Then, in the Nexus Root Kit, launch " flash stock + unroot" and select the downloaded system file.
The flash lasts 5 minutes, and the system will reboot.
Then you need to reactivate the usb debugging .
The next action is to relock the Nexus, with the "OEM Lock" in Nexus Root Toolkit.
The system will reboot after flash.
Then, the 4.3 update will be available automaticaly but this time the installation won't crash.
I hope this could help.
el chibro said:
I had exactly the same problem and after trying a few things, I just found a working solution for my Nexus 7.
I used the same tool I used to unlock and root a few months ago: Nexus Root Toolkit 1.6.3.
I made a backup of my files first, my idea being to reflash the 4.2.2 rom
...
I hope this could help.
Click to expand...
Click to collapse
Thanks for the idea. I used a similar approach with different steps and got 4.3 and root back.
I had stock 4.2.2, stock recovery, rooted (SuperSU).
Backup data.
From the Toolkit at http://forum.xda-developers.com/showthread.php?t=1809195
- "9. Download, Extract + Flash Google Factory Stock Rom"
- Download Stock Image
- "15. Android 4.2.2 (Build JDQ39)
... followed directions to download and flash WITHOUT wiping USERDATA
I did NOT do the "relock the Nexus, with the OEM Lock".
After flashing, did the OTA update to 4.3
After OTA and rebooting, got SuperSU update and put it on my N7
SuperSU thread: http://forum.xda-developers.com/showthread.php?t=1538053
CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
I went back in to the Toolkit:
- "10. Boot to Custom/Stock Recovery without Permanently Flashing it"
In CWM, I flashed the installable SuperSU ZIP, rebooted, and got rooted.
RocketOptics said:
Thanks for the idea. I used a similar approach with different steps and got 4.3 and root back.
I had stock 4.2.2, stock recovery, rooted (SuperSU).
Backup data.
From the Toolkit at http://forum.xda-developers.com/showthread.php?t=1809195
- "9. Download, Extract + Flash Google Factory Stock Rom"
- Download Stock Image
- "15. Android 4.2.2 (Build JDQ39)
... followed directions to download and flash WITHOUT wiping USERDATA
I did NOT do the "relock the Nexus, with the OEM Lock".
After flashing, did the OTA update to 4.3
After OTA and rebooting, got SuperSU update and put it on my N7
SuperSU thread: http://forum.xda-developers.com/showthread.php?t=1538053
CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
I went back in to the Toolkit:
- "10. Boot to Custom/Stock Recovery without Permanently Flashing it"
In CWM, I flashed the installable SuperSU ZIP, rebooted, and got rooted.
Click to expand...
Click to collapse
Hmm, why didn't you flash directly the 4.3 factory image and the SuperSU.zip on top of it ...
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Hmm, why didn't you flash directly the 4.3 factory image and the SuperSU.zip on top of it ...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I wanted to save my data and wasn't sure if going directly to 4.3 would be safe. Was just being cautious and letting the OTA do the update.