Hi Everyone!
I'm new here so I'm sorry if this has already been answered.
On my Nexus 7 which I rooted and unlocked, I still have the default/stock OS but put CWM recovery. Now I realise I want to put back the default one Google had on there but when I try to re-flash the recovery using fastboot flash recovery recovery.img , it seems to work
Code:
/fastboot flash recovery recovery.img
sending 'recovery' (5234 KB)...
OKAY [ 0.704s]
writing 'recovery'...
OKAY [ 1.200s]
finished. total time: 1.904s
Except when re-booting into recovery, it shows this weird image that seems to be an error. See the attachment "screenshot" image.
So, is there any way to put back default recovery, while keeping root?
Thanks!
Michael
This isn't a q and a forum, this is development. For ROMs, kernels, or other mods. Not for help.
Sent from my Google Nexus 7 using Tapatalk 2
Questions go in the q & a forum........
Sent from my Nexus 7 using xda app-developers app
My apologies, I thought this would have to do with ROMs. Re-posting in Q&A now...
Related
Hi all,
I have a samsung nexus s GT-I9020 ( no rooted , no custom recovery ) and 1 week ago I received the OTA update for Ice Cream Sandwich. I updated but, after 1 week usage, I noticed serious issues with the battery. So I decided to revert back to gingerbread, by downloading a stock firmware 2.3.2-GRH78C nandroid backup and trying to do
fastboot flash boot boot.img
fastboot flash system system.img
and so on.
But I do have a problem here. When, in fastboot, I first ran fastboot flash boot boot.img I got an error on the terminal
sending 'boot' (8192 KB)...
OKAY [ 1.185s]
writing 'boot'...
FAILED (remote: Write Fail)
finished. total time: 1.191s
Click to expand...
Click to collapse
and on the phone screen I can see
FAILED exceed blocks 0x0000001e > 0x0000001c
Click to expand...
Click to collapse
Similar error happens if I try the system partition, with the following error on the terminal
sending 'system' (151476 KB)...
OKAY [ 22.184s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 22.189s
Click to expand...
Click to collapse
and on the phone screen
Invalid Magic Code 0x00000003
The phone now has a recovery image ( clockwork ) which I have been able to install, but this is not able to browse any of the filesystems available. So I was looking at some stock img files I could flash via fastboot, At the moment the phone just hangs at fastboot mode saying no boot image is available.
I am using a ubuntu oneiric 32 bit and I have the latest android sdk tools.
This is not the first time I flash images using fastboot and I really have no idea why this is happening. It might be because my android version was icecream ? I have never had issues when flashing different versions of gingerbread. Also I used the encryption feature of icecream sandwich, if this is useful for you to know.
Thank you very much, hope someone can help me with that.
Click to expand...
Click to collapse
Maybe u got bad downloads try redownloading the files and make sure u have the boot loader unlocked first.
Sent from my Nexus S 4G using xda premium
I would suggest trying to fastboot boot cwr and flashing a zip.
Sent from my Nexus S using xda premium
I cannot use CWR to flash it.
The reason is: I can start CWR but the nandroid backup I got from xda developers is not on the nexus s itself. Moreover CWR cannot browse the contentes of the sd, it says cannot open device.
Regardig the files, I have issued md5sum and they seem all right.
I am really struggling with it.
Hi,
I recently got a nexus 10, and started working on rooting. I have unlocked it, installed CWM recovery and booted it twice. I have not rooted it yet. Now I realized, that everytime I entered the CWM recovery mode, it automatically reboots back into recovery or normal boot in about 30 seconds or so. (this is not the main problem!)
But one booting up second time, I got a notification of sytem update for 4.2 jellybean (please note initially the device was on 4.2 JB JVP15P), I clicked on install, it booted into CWM recovery, but then it failed to continue with installation, as it complained about authentication failure for the zip fle or something of that sort. So I chose to boot the device without installing the update, now it entered a boot loop. I have tried erasing cache and userdata (both using fastboot commandline, and options in the CWM - in the 30 secs I get). It did not work.
After trying it for a few times, I tried restoring some backups I had made. Initially it complained about MD5 mismatch, and then later on it complained about unable to mount cache/* and unable to mount sdcard.
I have read around and the universal solution seems to be to restore stock images. Is that the solution for me as well?
Any help would be greatly appreciated, and I am noob in this area, so pardon me if I act like one.
cheers,
brickin
I'd like to know part of the answer to this as well. The tab is running fine and TWRP works fine, but CWM constantly reboots and I have the same mounting problems within both CWM and TWRP. I've tried flashing stock image and recovery but it's made no difference.
IIRC, the newest CWM has an issue with devices that allow multiple users (aka: N7 and N10). Flash TWRP and don't look back.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 06:07 AM ---------- Previous post was at 06:05 AM ----------
Also, TWRP supports USB OTG while CWM doesn't.
Sent from my Galaxy Nexus using Tapatalk 2
I was having a similar issue with cwm. This explains everything.
Blueback22 said:
IIRC, the newest CWM has an issue with devices that allow multiple users (aka: N7 and N10). Flash TWRP and don't look back.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 06:07 AM ---------- Previous post was at 06:05 AM ----------
Also, TWRP supports USB OTG while CWM doesn't.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi Blueback22,
Thanks a lot for your reply.
Would flashing TWRP solve everything? And also is it ok to flash TWRP now, would it be able to restore the backups I have made using CWM?
Do I need to uninstall or remove the CWM recovery image that has alreday been flashed? or will TWRP image overwrite it?
How do I solve the bootloop issue?
I am unable to get a stock image for JB version: JVP15P. Do you know where I can find the factory image for that?
OR is it ok for me to flash the JOP40C image? Would it cause any problems - (like would it cry saying checksum mismatch or something like that)?
Also, what is the solution for unable to mount sdcard problem?
Sorry for asking so many questions, but I do not wish to brick my device, hence I wish to understand what I am going to do, and ensure that it is not going to harm my device.
Your replies to this post is and will be deeply appreciated.
Thanks,
brickin
brickin said:
Hi Blueback22,
Thanks a lot for your reply.
Would flashing TWRP solve everything? And also is it ok to flash TWRP now, would it be able to restore the backups I have made using CWM?
Do I need to uninstall or remove the CWM recovery image that has alreday been flashed? or will TWRP image overwrite it?
How do I solve the bootloop issue?
I am unable to get a stock image for JB version: JVP15P. Do you know where I can find the factory image for that?
OR is it ok for me to flash the JOP40C image? Would it cause any problems - (like would it cry saying checksum mismatch or something like that)?
Also, what is the solution for unable to mount sdcard problem?
Sorry for asking so many questions, but I do not wish to brick my device, hence I wish to understand what I am going to do, and ensure that it is not going to harm my device.
Your replies to this post is and will be deeply appreciated.
Thanks,
brickin
Click to expand...
Click to collapse
If I were you, I would use WugFresh's toolkit to flash back to stock. Then I'd flash TWRP and start from scratch.
I don't know if TWRP will fix your issue all together, but I do remember hearing that there's an issue with CWM on the N10 right now.
Your CWM backups won't work on TWRP IIRC.
Here is where you can get stock images:
https://developers.google.com/android/nexus/images
Sent from my Galaxy Nexus using Tapatalk 2
Hi Blueback22,
Thanks for the help. I was able to fix the problem.
Here are the questions I had and the answers I found, please correct me if I am wrong.
1. My JB version is JVP15P, is it ok to flash JOP40C stock recovery image?
ans: yes
2. Does TWRP work perfectly with nexus 10?
ans: Atleast in my case it did, I was able to root my device, and was also able to take backups.
3. a. CWM complains E: Can't mound /sdcard !
b. CWM Keeps restarting within 30 secs or so !
c. My device is stuck in bootloop !
ans: First, try to wipe your cache, and userdata and reboot. If it does not solve, then flash stock factory image for your device and flash TWRP recovery image.
4. CWM complains E: can't mount /cache/*
ans: Wipe your cache, userdata and reboot.
Reiterating blueback22's point:
DO NOT USE CWM WITH NEXUS 10. USE TWRP INSTEAD.
Cheers,
brickin
BRICKED: OLd bootloader version wont update
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.168s]
writing 'bootloader'...
OKAY [ 0.143s]
finished. total time: 0.318s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.009s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
OKAY [ 0.145s]
finished. total time: 0.323s
C:\android-sdk\platform-tools>fastboot -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ09
Baseband Version.....: no modem
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MANTALJ09'.
Update requires 'MANTALJ12'.
finished. total time: 0.063s
I tried one click root and wug's root kits, but there wasn't any luck in returning to stock and stuck in older bootloader without the possibility of returning to stock. I am stuck in Clockworkmod v6.0.1.9 loops. Tried to search the forum but I couldnt find anything.
ginsboon said:
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.168s]
writing 'bootloader'...
OKAY [ 0.143s]
finished. total time: 0.318s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.009s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
OKAY [ 0.145s]
finished. total time: 0.323s
C:\android-sdk\platform-tools>fastboot -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ09
Baseband Version.....: no modem
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MANTALJ09'.
Update requires 'MANTALJ12'.
finished. total time: 0.063s
I tried one click root and wug's root kits, but there wasn't any luck in returning to stock and stuck in older bootloader without the possibility of returning to stock. I am stuck in Clockworkmod v6.0.1.9 loops. Tried to search the forum but I couldnt find anything.
Click to expand...
Click to collapse
Can you get into the boot loader and flash TWRP to see if that fixes it?
Sent from my Galaxy Nexus using Tapatalk 2
ginsboon said:
returning to stock. I am stuck in Clockworkmod v6.0.1.9 loops. Tried to search the forum but I couldnt find anything.
Click to expand...
Click to collapse
Why don't you try cwm 6.0.2.3? I also loaded 6.0.1.9 and it would reboot in about 30sec time. After going to the latest, cwm has been stable. No more random reboots.
Link to download the latest version...
http://www.clockworkmod.com/rommanager
cowabunga said:
Why don't you try cwm 6.0.2.3? I also loaded 6.0.1.9 and it would reboot in about 30sec time.
I tried to flash cwm 6.0.2.3 and twrp but failed. Still searching for some clues.
Click to expand...
Click to collapse
For OP and other N10 users with stock 4.2 JB Build JVP15P experience:
Is it possible to use the available toolkits (Wug's or mskip's) to unlock the bootloader and root a N10 with the configuration above? Both toolkits ask for Build JOP40C. I've searched the developer forum for this build and found nothing. Thanks!
So I just flash the factory image through fastboot, and the boot?
Flashing latest TWRP after that, which method is best to root afterwards? Thanks.
binaryfalcon said:
So I just flash the factory image through fastboot, and the boot?
Flashing latest TWRP after that, which method is best to root afterwards? Thanks.
Click to expand...
Click to collapse
You flash the images, then you flash TWRP, then you do a factory reset in TWRP, and install SuperSU (http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip), and then boot. You'll now have 4.4 Rooted.
binaryfalcon said:
So I just flash the factory image through fastboot, and the boot?
Flashing latest TWRP after that, which method is best to root afterwards? Thanks.
Click to expand...
Click to collapse
How long does it take to flash the image-occam-krt16o.zip? I have been waiting for 20 minutes now. This is my output from the command window
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.076s]
writing 'bootloader'...
OKAY [ 0.298s]
finished. total time: 0.375s
wickdc said:
How long does it take to flash the image-occam-krt16o.zip? I have been waiting for 20 minutes now. This is my output from the command window
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.076s]
writing 'bootloader'...
OKAY [ 0.298s]
finished. total time: 0.375s
Click to expand...
Click to collapse
You can run the flash all command, or you flash everything separately. Go to efrant's guide on how to do that here on xda. You have now flashed the bootloader succesfully, now you will have to flash the other images as well.
Sent from my Nexus 4 using xda app-developers app
why don't you install cwm/twrp first? it's a lot easier to flash in my opinion (not if you want to install the image from your computer)
but normally it just takes a few moments/minutes
I am depressing now. I have been doing a lot of googling in the past few days, but all I found doesn't work for me.
I have formatted everything in my nexus 7 using clockworkmod recovery by accident, and I don't have access to it by using USB or OTG cable. I have tried Adb, found drivers from different tutorials (they are the same driver), but when I try the command adb devices, it seems my computer is not recognizing it. then I tried again with another computer, Don't work either. The problem maybe is that I can't Enable usb debugging on my device, since the android system has been formatted by me.
What else can I try at this point? thank you in advance!!!
so I can't get into ADB because I can't change my bricked device to USB debugging mode. is this mean, I can't do anything else to fix it??
thank you for the fast reply.....
I saw someone mentioned Nexus Root Toolkit, and tried it, can't get into adb..but fastboot shows my device....but I can't flash anything into my device without adb
C:\an>fastboot.exe devices
015d24bc5c0ff218 fastboot
C:\an>fastboot.exe flash recovery cm-10.1.2-grouper.zip
sending 'recovery' (159175 KB)...
OKAY [ 21.062s]
writing 'recovery'...
FAILED (remote: (InvalidSize))
finished. total time: 21.111s
fastboot flash recovery recovery.img (where recovery.img is the name of the recovery file that you have downloaded, either TWRP or CWM).
That last command was invalid.
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
You can also try downloading the factory image and flash it via fastboot.
sgt. meow said:
fastboot flash recovery recovery.img (where recovery.img is the name of the recovery file that you have downloaded, either TWRP or CWM).
That last command was invalid.
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
You can also try downloading the factory image and flash it via fastboot.
Click to expand...
Click to collapse
thank you.. I have CWM before....after do that, CWM is gone. I have that figured out....but even with CWM, I can't do much.
C:\an>fastboot.exe flash recovery openrecovery-twrp-2.4.1.0-jewel.img
sending 'recovery' (7936 KB)...
OKAY [ 1.068s]
writing 'recovery'...
OKAY [ 0.502s]
finished. total time: 1.574s
C:\an>fastboot.exe devices
015d24bc5c0ff218 fastboot
C:\an>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.106s]
finished. total time: 0.108s
C:\an>fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
sending 'recovery' (7964 KB)...
OKAY [ 1.069s]
writing 'recovery'...
OKAY [ 0.506s]
finished. total time: 1.578s
C:\an>fastboot.exe devices
C:\an>fastboot.exe devices
015d24bc5c0ff218 fastboot
C:\an>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.106s]
finished. total time: 0.108s
C:\an>fastboot.exe flash recovery openrecovery-twrp-2.6.3.1-grouper.img
sending 'recovery' (7766 KB)...
OKAY [ 1.034s]
writing 'recovery'...
OKAY [ 0.514s]
finished. total time: 1.551s
I did it. I got TWRP installed, and is able to see my using OTG USB, and saw my backup file, but my backup file is made using CWM. will it works??
megapig said:
thank you.. I have CWM before....after do that, CWM is gone. I have that figured out....but even with CWM, I can't do much.
Click to expand...
Click to collapse
In cwm you should be able to use adb. Otherwise flash the factory image.
Sent from my Nexus 7 using Tapatalk
sgt. meow said:
In cwm you should be able to use adb. Otherwise flash the factory image.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I can't use adb in cwm. I have tried, and CWM can't mount OTG USB drive. So now I am trying to copy my CWM backup file to sdcard using TWRP's file manager , and later delete TWRP and reinstall CWM and try to see if I can restore my device..thank you so much
sgt. meow said:
In cwm you should be able to use adb. Otherwise flash the factory image.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
there is an usb mounting option in 6.0.4.1 version of CWM. I was using 6.0.3.1, and.. I am restoring ...
Unbrick!!! restored using OTG USB!!!!
i have one received from customer , when i power on just hang on start-up log
to fix that i need just unlock boot loader flash the phone (using Nexus Root Toolkit1.8.6 )
but this one , root is done phone habe unlocked boot loader , when i try to flash i get this error
archive does not contain 'boot.sig'
PHP:
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2203 KB)...
OKAY [ 0.077s]
writing 'bootloader'...
OKAY [ 0.318s]
finished. total time: 0.398s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
sending 'radio' (45537 KB)...
OKAY [ 1.503s]
writing 'radio'...
OKAY [ 2.578s]
finished. total time: 4.083s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
archive does not contain 'boot.sig'
error: out of memory
any help ^
Probably is not the problem about that "sign" error but next line, out of memory error. Check if there is any storage left. If there is,... What rom do you flash with?
Addition: i had a similar problem and i couldnt instal 4.4.4, i did first install 4.2 amd after that on 4.4.4 and it was successful.
I did it by this manual:
https://developers.google.com/android/nexus/images
Sent from my Nexus 4 using XDA Free mobile app
bojanz said:
Probably is not the problem about that "sign" error but next line, out of memory error. Check if there is any storage left. If there is,... What rom do you flash with?
Addition: i had a similar problem and i couldnt instal 4.4.4, i did first install 4.2 amd after that on 4.4.4 and it was successful.
I did it by this manual:
https://developers.google.com/android/nexus/images
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
This ^ boot sig error is normal
Sent from my Nexus 5 using XDA Free mobile app
yes phone work with 4.2 as you say thx for help
but i have base band version unknown
hitibiti said:
yes phone work with 4.2 as you say thx for help
but i have base band version unknown
Click to expand...
Click to collapse
Fastboot flash the 4.2 cache image
Sent from my Nexus 5 using XDA Free mobile app
how can i do that ?
thx
hitibiti said:
how can i do that ?
thx
Click to expand...
Click to collapse
Download the factory image. Extract it. Inside is a zip, extract that too. In there you'll find the cache.img. boot into the bootloader and in a cmd window on the pc use
fastboot flash cache cache.img
If you don't have fastboot set up on the pc Google 15 second adb install xda
Sent from my Nexus 5 using XDA Free mobile app