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)

[Q] Nexus 7 (4.1.2) can't root

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!!!

[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!

Nexus 10 stuck at Fastboot Mode....I think

I have a Samsung Google Nexus 10 (Wi-Fi) GT-P8110HAAPHE Which was running Android 4.4.3 (I think but it is definitely the latest version) and I simply wished to root it.
I started following a video on Youtube and now I am stuck at what I think is called the Fastboot mode where My options are to scroll through START/RECOVERY MODE/RESTART BOOTLOADER/POWER OFF. I was using the Wugs Nexus Root Toolkit v1.8.3.
No matter which I select it returns me to the screen with the START option. When I select POWER OFF it does indeed power off but when I switch it on again it returns to the fastboot mode START option. I can get into download mode if that helps.
I did create a backup but cannot restore it.
I have done some research and downloaded the Android SDK Suite and fastboot/ADB and drivers etc ready to try and recover but I don't know where to start.
I have a Samsung Galaxy S3 which I have rooted and installed a number of different ROMS on so I am familiar with rooting but not sure if I can use Odin or something similar.
I think I have included all the information I have and hope someon can assist.
Thanks.

matrixmainframe said:
I have a Samsung Google Nexus 10 (Wi-Fi) GT-P8110HAAPHE Which was running Android 4.4.3 (I think but it is definitely the latest version) and I simply wished to root it.
I started following a video on Youtube and now I am stuck at what I think is called the Fastboot mode where My options are to scroll through START/RECOVERY MODE/RESTART BOOTLOADER/POWER OFF. I was using the Wugs Nexus Root Toolkit v1.8.3.
No matter which I select it returns me to the screen with the START option. When I select POWER OFF it does indeed power off but when I switch it on again it returns to the fastboot mode START option. I can get into download mode if that helps.
I did create a backup but cannot restore it.
I have done some research and downloaded the Android SDK Suite and fastboot/ADB and drivers etc ready to try and recover but I don't know where to start.
I have a Samsung Galaxy S3 which I have rooted and installed a number of different ROMS on so I am familiar with rooting but not sure if I can use Odin or something similar.
I think I have included all the information I have and hope someon can assist.
Thanks.
Click to expand...
Click to collapse
This is why I tell people not to use toolkits. Since everything is automated, it's hard to tell what went wrong and where. When it comes to Nexus devices, toolkits are entirely unnecessary IMO. These Nexus devices are so super simple to flash manually it's ridiculous. /END RANT
Okay. Sorry about that. Now, back to the issue at hand. The menu you are describing is, in fact, the Bootloader (aka Fastboot mode). Prior to using the NRT, were you completely stock? Was your bootloader already unlocked? To me, it sounds like you may have wiped your OS. Have you tried flashing the 4.4.3 factory image?

I was completely stock. Whilst using NRT I believe I had just succeeded in unlocking the Bootloader and the video then stated that with 4.4.3 a Factory reset was required which is what I did but I did not realise that deleted the O2. I thought that was on a protected partition like my S3 phone.
I can't flash the factory image as I can't get into recovery or is there another way of doing it?
I suppose where tablets are concerned I'm a book but if you could point me to any instructions on how to flash manually I'm hoping I can recover my tablet. Thanks.
Sent from my GT-I9300 using Tapatalk

Sorry, predictive text is rubbish. O2 should read OS and last paragraph I'm a book should read I'm a noob
Sent from my GT-I9300 using Tapatalk

matrixmainframe said:
I was completely stock. Whilst using NRT I believe I had just succeeded in unlocking the Bootloader and the video then stated that with 4.4.3 a Factory reset was required which is what I did but I did not realise that deleted the O2. I thought that was on a protected partition like my S3 phone.
I can't flash the factory image as I can't get into recovery or is there another way of doing it?
I suppose where tablets are concerned I'm a book but if you could point me to any instructions on how to flash manually I'm hoping I can recover my tablet. Thanks.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Dont know how you got your os erased. But im using a custom recovery since I got mine so maybe the stock recovery erses the os when doing a factory reset. A factory image cant be flashed via recovery and must be flashed via fastboot. Its really easy. But it will wipe the entire device. If you dont want to wipe everything you need to edit it..
Sent from my Galaxy Nexus using XDA Free mobile app

Cannot access Recovery Mode. Can Access Download Mode!
mrgnex said:
Dont know how you got your os erased. But im using a custom recovery since I got mine so maybe the stock recovery erses the os when doing a factory reset. A factory image cant be flashed via recovery and must be flashed via fastboot. Its really easy. But it will wipe the entire device. If you dont want to wipe everything you need to edit it..
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
I don't mind wiping the device but I cannot access Recovery Mode. When I select RECOVERY MODE and press the Power button to take me there it just returns me to the START screen.
I don't know if the fiollowing is relevent but it displays the word START vertically in the top left of the screen and next to it
Device Information
Product Name: manta
Variant: wifi
H/W Version: 8
Bottloader Version: MANTAMF01
Carrier Info: None
Serial Number: Don't think I should show that
Lock State: Unlocked
Reboot Mode Flag: None.
I have tried RESTART BOOTLOADER and that brings me back to the Start screen but still cannot access RECOVERY MODE.
Holding down the Power Button and Volume Up/Down brings me back to the Start screen again
I can get into DOWNLOAD MODE
Is there ANY way I can flash anything onto my Nexus 10 without using RECOVERY MODE like using Odin or Heimdall with a Samsung phone?

SORTED
Great news everyone..........well for me that is :laugh:
Thanks to Androidbeat.com I now have a fully operational Nexus 10.
Just in case anyone else was following this I did it by downloading all the necessary files into on folder on my Windows Desktop, opening a Command Prompt from there and followed the instructions.
Thank you to those who offered advice here and although my Nexus 10 is showing itself to be unlocked I think I'll give a miss to rooting it and just suffer the limitations rather than risk bricking it again.

matrixmainframe said:
Great news everyone..........well for me that is :laugh:
Thanks to Androidbeat.com I now have a fully operational Nexus 10.
Just in case anyone else was following this I did it by downloading all the necessary files into on folder on my Windows Desktop, opening a Command Prompt from there and followed the instructions.
Thank you to those who offered advice here and although my Nexus 10 is showing itself to be unlocked I think I'll give a miss to rooting it and just suffer the limitations rather than risk bricking it again.
Click to expand...
Click to collapse
Glad everything worked out for you. Just an FYI for future reference, the stock recovery factory reset does not wipe the OS (at least it shouldn't). By default, AFAIK there are no custom recoveries that will wipe your OS either while doing a factory reset. It must've been something with the toolkit.
Regarding root, it's super easy to get root on this device. All you have to do is download the custom recovery image file of your choice. I prefer Philz, but you can use CWM or TWRP as well. Then, download the latest SuperSU zip file (I believe it's v1.99r4 now). Simply fastboot flash the recovery image, boot into recovery, and install the SuperSU zip, and you're good to go. The whole process takes two minutes, and no toolkit required.

charesa39 said:
Glad everything worked out for you. Just an FYI for future reference, the stock recovery factory reset does not wipe the OS (at least it shouldn't). By default, AFAIK there are no custom recoveries that will wipe your OS either while doing a factory reset. It must've been something with the toolkit.
Regarding root, it's super easy to get root on this device. All you have to do is download the custom recovery image file of your choice. I prefer Philz, but you can use CWM or TWRP as well. Then, download the latest SuperSU zip file (I believe it's v1.99r4 now). Simply fastboot flash the recovery image, boot into recovery, and install the SuperSU zip, and you're good to go. The whole process takes two minutes, and no toolkit required.
Click to expand...
Click to collapse
charesa39 thanks for that. All done so thanks again.