Database Users

Nexus S i9020a + CM7

Can someone please direct me to the a step by step guide on how to Root and put CM7 on the Nexus S i9020a variant? Most of the stickies are for the T-mobile version and Its getting to be a bit confusing on which guide to follow. Please help this noobie!!!

use gingerbreak then rom manager it's that simple
http://forum.xda-developers.com/showthread.php?t=1044765

Quick note once you install CM7 do not use the 2g/3g feature it will break your 3g

Break 3g? as in damage it permanently? Thanks for the link for gingerbreak so basically that will root my nexus s then I can install CM 7 with out any special instructions since it has different radio compared to the tmobile version?

i used gingerbreak then rom manager to install clockwork recovery and CM7. Do some reading the 3g bug for I9020A has been discussed a few times. Just stay away from the 2g/3g toggle and everything will be fine. I don't think it permanently breaks it just is a pain in the A to fix. I have a I9020A and this was the simplest way I've found.

don't we have to flash a clockwork compatible kernel first, before flashing cm7?
Also, doesn't clockwork rom manager fail on sns? I have cwr from the main stickies, but rom manager doesn't see it (it works), and can't download roms, unless cwr from rom manager, which I heard fails.
Sent from my Nexus S using XDA App
So I downloaded CM7 7.0.2 - and gapps - flashed in order (nandroid first) and voila! no hastle! This ROM is great!

No, those are the only steps i took

CM7 comes with its own AOSP kernel. Just flash the rom, you'll get the kernel bundled. (Of course you can always use a great kernel from the developers thread) don't forget to flash gapps.
Sent from my Nexus S using XDA Premium App

jruweaver said:
Quick note once you install CM7 do not use the 2g/3g feature it will break your 3g
Click to expand...
Click to collapse
He means don't use the 2g/3g toggle widget as that will cause some problems, it hasn't been fixed yet. If you do want to change it though, do it manually through the settings.
Sent from my Nexus S using XDA App

I tried using gingerbreak on my i9020a but it runs for longer than 15 mins so I guess it doesn't work. What are my other options for rooting?
edit: I guess it's because I installed 2.3.6.. is it possible to downgrade easily?

drleospaceman said:
I tried using gingerbreak on my i9020a but it runs for longer than 15 mins so I guess it doesn't work. What are my other options for rooting?
edit: I guess it's because I installed 2.3.6.. is it possible to downgrade?
Click to expand...
Click to collapse
Follow one of the root guides, all you really need to do is unlock the bootloader and install Clockwork Recovery.
Once that is done, download the zip for cm7 and use CWM to flash it.

Matridom said:
Follow one of the root guides, all you really need to do is unlock the bootloader and install Clockwork Recovery.
Once that is done, download the zip for cm7 and use CWM to flash it.
Click to expand...
Click to collapse
Thanks

Matridom said:
Follow one of the root guides, all you really need to do is unlock the bootloader and install Clockwork Recovery.
Once that is done, download the zip for cm7 and use CWM to flash it.
Click to expand...
Click to collapse
Exactly the steps I took. Took all of 10 minutes
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot recovery
Install .zip from SD
Select CM7
reboot system

Mr Kyle said:
Exactly the steps I took. Took all of 10 minutes
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot recovery
Install .zip from SD
Select CM7
reboot system
Click to expand...
Click to collapse
Agreed, but it's a matter of getting the correct CWM image for our phones. Also, for people who are setting up their phones for the first time, the drivers needed for fastboot need to be installed, fastboot/SDK needs to be downloaded etc...
Hence why i referenced the rooting guides.

Mr Kyle said:
Exactly the steps I took. Took all of 10 minutes
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot recovery
Install .zip from SD
Select CM7
reboot system
Click to expand...
Click to collapse
Which recovery img file should I use from here?
http://forum.xda-developers.com/showthread.php?t=988686&highlight=i9020a
Thanks
edit: nevermind, I guess the color names are just cosmetic?

drleospaceman said:
Which recovery img file should I use from here?
http://forum.xda-developers.com/showthread.php?t=988686&highlight=i9020a
Thanks
edit: nevermind, I guess the color names are just cosmetic?
Click to expand...
Click to collapse
Yep, it's just the color you want your recovery to be. I flashed the cyan a couple of days ago for somebody else and no issues.. typical clockwork recovery

So I flashed the recovery file, but when I boot into recovery now, there's just the triangle with the ! in it and nothing happens.. did I do something wrong?
edit: reflashed it and it works

drleospaceman said:
So I flashed the recovery file, but when I boot into recovery now, there's just the triangle with the ! in it and nothing happens.. did I do something wrong?
Click to expand...
Click to collapse
How did you flash it? That's the stock recovery.. should be 'fastboot flash recovery nameof.img' without quotes obviously.

drleospaceman said:
So I flashed the recovery file, but when I boot into recovery now, there's just the triangle with the ! in it and nothing happens.. did I do something wrong?
edit: reflashed it and it works
Click to expand...
Click to collapse
somebody after reboot no CWR on recovery use this solved your problem
clockworkmodrecovery rom manager find and install
open it and touch flash clockworkmod recovery(first item)
select reboot into recovery manual
mount and storage select
mount USB storage
unmount
++++ go back +++++
install from zip sdcard
find
'' super user.zip'' flash
reboot
find and isntall ''es file explorer'' select setting mark root explorer and mount file system after
select phone in file explorer find ''etc'' folder select and find ''install-recovery.sh'' file and rename file for example ''install-recovery.sheski'' and
open rom manager again touch flash clockworkmod recovery(first item)
check it...
please click thanks button

[GUIDE] Install ClockworkMod Recovery image after updated to 2.3.4 (GRJ22).

Not applicable
Delete this thread

Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!

Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.

Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.

bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?

Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse

andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?

This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App

bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore

zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers

andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist

16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist

Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S

No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk

nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?

I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.

dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?

I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?

hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....

just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)

*problem solved*

hi there, i have a problem with my nexus 7 and i have searched around for some answers i cant seem to find any for my problem.
so the story goes:
i downloaded the nexus 7 toolkit by mskip and i used this to unlock the boot and root my device, this worked fine. I then decided to try another rom, so i copied the zip to the sdcard (or so i thought) and using the toolkit i used option 11 to install the recovery-clockwork-6.0.1.0-grouper.img, (i selected option 1 intall in /boot, i assume this is where i screwed up) this too went fine. but i couldn't install the new rom as it was no longer there, and now i cant get my device to do anything except boot into cwm or i can go into fast boot.
any ideas on what i can do?
i have looked for the default .img to try installing that but i cant seem to find one.
thanks for looking.

SemnteX said:
hi there, i have a problem with my nexus 7 and i have searched around for some answers i cant seem to find any for my problem.
so the story goes:
i downloaded the nexus 7 toolkit by mskip and i used this to unlock the boot and root my device, this worked fine. I then decided to try another rom, so i copied the zip to the sdcard (or so i thought) and using the toolkit i used option 11 to install the recovery-clockwork-6.0.1.0-grouper.img, this too went fine. but i couldn't install the new rom as it was no longer there, and no i cant get my device to do anything except boot into cwm or i can go into fast boot.
any ideas on what i can do?
i have looked for the default .img to try installing that but i cant seem to find one.
thanks for looking.
Click to expand...
Click to collapse
dont use a toolkits. download the rom via your phones browser, go into recovery and flash it. anyways, you should try twrp recovery, its better than cwm and not buggy

simms22 said:
dont use a toolkits. download the rom via your phones browser, go into recovery and flash it. anyways, you should try twrp recovery, its better than cwm and not buggy
Click to expand...
Click to collapse
unfortunately i cant do this as i cant boot into the androis os, i have stupidly overwritten the original boot.img located in the /boot folder, i think i need a copy of the original boot.img to be able to get into android and then get me a new rom

SemnteX said:
unfortunately i cant do this as i cant boot into the androis os, i have stupidly overwritten the original boot.img located in the /boot folder, i think i need a copy of the original boot.img to be able to get into android and then get me a new rom
Click to expand...
Click to collapse
Do you have adb on your computer? Fastboot?
Sent from my Nexus 7 using xda premium

marty331 said:
Do you have adb on your computer? Fastboot?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
yes i do, but i get confused using those, which is why i used the toolkit to unlock and root my device. unfortunately i got a little carried away and installed cwm into the wrong directory and overwrote the boot img.

SemnteX said:
unfortunately i cant do this as i cant boot into the androis os, i have stupidly overwritten the original boot.img located in the /boot folder, i think i need a copy of the original boot.img to be able to get into android and then get me a new rom
Click to expand...
Click to collapse
cant you reach your storage via your cwm recovery? you should be able to transfer files from your computer to device still.

simms22 said:
cant you reach your storage via your cwm recovery? you should be able to transfer files from your computer to device still.
Click to expand...
Click to collapse
i've tried to do this, but it wont let me mount the /scdard, im not sure why, but it maybe has something to do with how i installed cwm on the device, or maybe im have driver issues
UPDATE = i fixed my device, my stupidity knows no bounds, i found an option in the toolkit to download and install the factory standard rom with all the gubbins attached including the boot img so i okay for now untill i find something else to screw up

SemnteX said:
i've tried to do this, but it wont let me mount the /scdard, im not sure why, but it maybe has something to do with how i installed cwm on the device, or maybe im have driver issues
UPDATE = i fixed my device, my stupidity knows no bounds, i found an option in the toolkit to download and install the factory standard rom with all the gubbins attached including the boot img so i okay for now untill i find something else to screw up
Click to expand...
Click to collapse
No sir, how about reading this link!
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
I'm sure there is something similar on xda but I have this link handy.
Sent from my Nexus 7 using xda premium

Changing the title of this post to problem solved doesn't help anybody in the future with a similar problem
Sent from my Nexus 7

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

[Q] Unable to Flash Nexus 7

hello everyone..
In serious need of help here and hope someone can help..
Due to the massive battery drain issue I have been having, I tried to flash the original stock rom on my nexus 7 and
things have gone downhill really bad..
in the past, I flashed using this guide (http://forum.xda-developers.com/showthread.php?t=1907796)
without any problems but last night.. I encountered errors when trying to flash the bootloader
and radio IMG files.. neeedless to say when it comes to flashing the rom in, it came out with errors and my nexus remain OS-less
the errors when trying to flash the bootloader and radio are
"failed (command write failed (Invalid Argument))"
can anyone help me?
p.s :- if anyone can even suggest me a easier way to flash custom roms in and so forth, your suggestion will be most welcomed..
also, I did try wug's rootkit plus the nexus 7 toolkit or something, both came out errors too when too do any flashing in relating to
the bootloader or system.. thanks

Why were you trying to flash the bootloader? Were you trying to update to 4.18?

Username invalid said:
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Click to expand...
Click to collapse
actually, my bootloader boots fine, it shows tilapia 4.18.
so does this mean I dont have to flash it?
if I dont have to flash the bootloader, do I have to flash the radio?
sorry, kind of a noob in these things..

Anyway, is it normal for the bootloader flash attempt to fail?

hamiksu said:
Anyway, is it normal for the bootloader flash attempt to fail?
Click to expand...
Click to collapse
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.

korockinout13 said:
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
Click to expand...
Click to collapse
hmm, ok..
then I will go back home and do the system flashing and try and post out the errors it stated there..
really hope to get my nexus back on line...

This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.

hamiksu said:
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
Click to expand...
Click to collapse
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock

ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
it says my bootloader is already unlocked

hamiksu said:
it says my bootloader is already unlocked
Click to expand...
Click to collapse
Then it sounds like something happened to your system partition that should not have happened.
Are you sure the system image you're trying to flash is valid, do the md5 sums match?
How about flashing another system image?
Or flash a custom recovery, and install a new ROM from there?

ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
ameinild said:
Then it sounds like something happened to your system partition that should not have happened. Sorry, can't help you there...
Click to expand...
Click to collapse
meaning my system partition is screwed?
anyone knows how to go around this problem?
p.s :- anyway ameinild, thanks for trying to help

hamiksu said:
p.s :- anyway ameinild, thanks for trying to help
Click to expand...
Click to collapse
I edited my post with some more suggestions to try first

ameinild said:
I edited my post with some more suggestions to try first
Click to expand...
Click to collapse
yup, the image i tried a few.. even tried stock rom image.
tried both nexus 7 toolkit
as well as wugs nexus root tool kit.
they all seem to encounter problems when trying to "push" the rom images in or something.
is there a way to like format the entire thing and install from scratch>?

hamiksu said:
is there a way to like format the entire thing and install from scratch>?
Click to expand...
Click to collapse
Sorry, I can't really find anything for the N7... Hope someone else can chime in.

ameinild said:
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
Click to expand...
Click to collapse
Yea, I hope someone will pop in and be my guardian angel too..
Thanks again, Ameinild

tried to flash stock rom using wug's rootkit..
this is what happens...

hamiksu said:
tried to flash stock rom using wug's rootkit..
this is what happens...
Click to expand...
Click to collapse
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?

Rirere said:
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Click to expand...
Click to collapse
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis

I'm assuming you haven't tried this yet, if you have tried this just ignore.
1 - Download - http://techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.6.0.0-grouper.img
2 - fastboot flash recovery openrecovery-twrp-2.6.0.0-grouper.img
If flashes fine:
Power off Nexus, Hold Volume down and Power on, keep holding power down until you get to recovery.
Then:
Either - Get a USB OTG and put a ROM on a USB Stick, go to "install" - "Use external storage" find the rom and flash it.
or
Plug in to PC whilst in recovery, - Mount Storage - Now the Nexus should pop up on PC, Drag ROM to Nexus. Unmount and then try to flash.
Let me know how you get on with this.
Regards.

hamiksu said:
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
Click to expand...
Click to collapse
That's because you have stock recovery installed now and it's unable to verify that your device is in working order, hence the red mark. Find TWRP for your device, download the .img and try to flash it with fastboot flash recovery <path-to-recovery.img>. Since you can at least get into a recovery, it's possible you'll be able to use onboard recovery tools to see what state your internal partitions are in.
Until there's a little more info available, there's nothing I can say that's not pure conjecture.