Database Users

Nexus S Issues

ok, first of all, i do not have enough post's to post this in the development section where it belongs...anyways, my nexus s is a complete mess. I had brainmaster's miui with the matr1x kernel running for 6 hours and my phone reboots and get's stuck on the boot up screen with the unlocked symbol.
i've tried many battery pulls and yet it won't manage to boot past that screen nor will it mount my sd card. i've been looking all over xda for a fix for this and i can't seem to get any solution to fix my problem.
i tried adb but im not sure if im doing it right or not because im using a mac.
anyways, any help will be greatly appreciated!!
and yes i tried the method where i download the nandroid backup and mount through cwr, but each time i try to mount my sd card to mount it fails, for some reason it only mounts if i have twrp recovery...

mimobeatz said:
ok, first of all, i do not have enough post's to post this in the development section where it belongs...anyways, my nexus s is a complete mess. I had brainmaster's miui with the matr1x kernel running for 6 hours and my phone reboots and get's stuck on the boot up screen with the unlocked symbol.
i've tried many battery pulls and yet it won't manage to boot past that screen nor will it mount my sd card. i've been looking all over xda for a fix for this and i can't seem to get any solution to fix my problem.
i tried adb but im not sure if im doing it right or not because im using a mac.
anyways, any help will be greatly appreciated!!
and yes i tried the method where i download the nandroid backup and mount through cwr, but each time i try to mount my sd card to mount it fails, for some reason it only mounts if i have twrp recovery...
Click to expand...
Click to collapse
try mount "usb storage" also you may try and re-flash miui and not wipe cache ect. it might boot back up.

ok, but how can i reflash the rom if the sd card won't mount? is it possible through adb?

mimobeatz said:
ok, first of all, i do not have enough post's to post this in the development section where it belongs...anyways, my nexus s is a complete mess. I had brainmaster's miui with the matr1x kernel running for 6 hours and my phone reboots and get's stuck on the boot up screen with the unlocked symbol.
i've tried many battery pulls and yet it won't manage to boot past that screen nor will it mount my sd card. i've been looking all over xda for a fix for this and i can't seem to get any solution to fix my problem.
i tried adb but im not sure if im doing it right or not because im using a mac.
anyways, any help will be greatly appreciated!!
and yes i tried the method where i download the nandroid backup and mount through cwr, but each time i try to mount my sd card to mount it fails, for some reason it only mounts if i have twrp recovery...
Click to expand...
Click to collapse
actually this doesn't belong in development section... it goes in Q&A. So yeah that post count limit is there for a reason
boot into recovery by holding volume up and power button and then selecting recovery and backup then wipe data/cache and start over and see if that fixes the issue.

Tried that as well, i began to research the problem more and it could possible that my nand is corrupt, so i might need to send it in under warranty? If this where the case would i just need to lock the bootloader?

reboot into recovery and wipe dalvik and try to reboot. Had the same problem but on cm7/matr1x and i wiped it and it booted, worth a try.

mimobeatz said:
Tried that as well, i began to research the problem more and it could possible that my nand is corrupt, so i might need to send it in under warranty? If this where the case would i just need to lock the bootloader?
Click to expand...
Click to collapse
What happened when you tried this?
Sent from my Nexus S 4G

also did you try and mount USB STORAGE in CWM?

Cant get Vibrant to start help plz!

Ok i was on ICS passion then all of a sudden my phone said something about encryption an that it had failed an only option was to reset phone so i hit reset then it went to recovery mode an green android came up with chest open then error message happened an so i booted in to recovery then i try to go in sd an it would not allow me to so i then tried to odin an flashed then i powered on it gies to vibrant screen then it just shuts off so i then flashed Eugene froyo that does not brick then it takes me to stock recovery an says an i cant click on anything in recovery can only move -- movi_checking done!...
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI me
nu for format and reboot actions.
Here are instructions i have followed an no luck http://forum.xda-developers.com/showthread.php?t=1043892
Ok I think you got some extra cache or some other piece of data that did not get wiped. either way, do this in this sequence and you should be ok
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Load the JFD rom for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine!
15. Then, root the phone and you can flash your new Rom.
doing this method will get everything back to normal and the phone will work just like it did right out of the box
It is #7 that is important when it reboots into recovery after froyo that does not brick then pull the battery and go back into download mode and flash the JFD, This will clear everything out and put you back into stock
Good luck

Got it started
I got it booted though a very hard process an now i cant get my sd card to mount it says when i go into anything media related it says "Your phone does not have a SD card inserted" an Externel dont mount either

Which sd card isnt working... internal sd, or external sd?

kf7strng said:
Which sd card isnt working... internal sd, or external sd?
Click to expand...
Click to collapse
Both of them aren't working

Jasonhunterx said:
Both of them aren't working
Click to expand...
Click to collapse
Don't use eugene's rom, since you were using an ICS rom follow these steps
flash froyo bootloaders
flash regular jfd and TICK REPARTITION ( ICS/CM7/CM9 change the partition layout and you need to flash correct partition table for stock rom to work )
back in bussiness.
http://forum.xda-developers.com/showthread.php?t=848737

jrafael said:
Don't use eugene's rom, since you were using an ICS rom follow these steps
flash froyo bootloaders
flash regular jfd and TICK REPARTITION ( ICS/CM7/CM9 change the partition layout and you need to flash correct partition table for stock rom to work )
back in bussiness.
http://forum.xda-developers.com/showthread.php?t=848737
Click to expand...
Click to collapse
it never booted on Eugene rom it just went to recovery an gave me an error the one time i got it booted was on 2.1 Stock all the phone does is go to vibrant screen then shut down an no boot loop just off it has done this before an i fixed but Sd was not working an first time apps worked but then 2nd time no apps worked besides browser messenger

Jasonhunterx said:
it never booted on Eugene rom it just went to recovery an gave me an error the one time i got it booted was on 2.1 Stock all the phone does is go to vibrant screen then shut down an no boot loop just off it has done this before an i fixed but Sd was not working an first time apps worked but then 2nd time no apps worked besides browser messenger
Click to expand...
Click to collapse
Hey Jason. I'm in the exact situation you're in. Loaded Passion for about 1 week, got the encryption screen and was forced to reset. Now my SD cards (internal and external) won't load. Have you found a work around for it yet? Cheers Mate.

nope nothing

either of you find a solution? Im having same issue

In the same boat
I am in the same boat. I was using the Euphoria ROM. Yesterday things slowed down on the phone. I rebooted a few times and it crashed. The last couple of times it told me about the encrypted data. That was when I tried to take it back to stock and it won't do anything now other than boot to the vibrant logo and shutdown. Searching for a way to odin a ROM/Kernel that has a CWM recovery so I can go in and manually format the SDcard.

Do what I did, sell it to someone as a wifi hotspot and buy yourself a hercules. You'll never look back
Sent from my SAMSUNG-SGH-T989 using XDA

BUMP
BUMP!
I have had a paper weight for three weeks now because of this partition issue.
there has to be a way to fix this.

webstas said:
BUMP!
I have had a paper weight for three weeks now because of this partition issue.
there has to be a way to fix this.
Click to expand...
Click to collapse
Try this one.
http://forum.xda-developers.com/showthread.php?t=1580902
Sent from my Vibrant using Tapatalk 2

Webstas- Just out of curiousity, were you trying to mount your phone to your computer while on ICs when this happened? I have a theory that I believe I know why this is happening. Just need you to see if you remember a few weeks ago and if you had any problems mounting to your PC and then your next reboot you got the Ecnryption Error.

Woodrube said:
Webstas- Just out of curiousity, were you trying to mount your phone to your computer while on ICs when this happened? I have a theory that I believe I know why this is happening. Just need you to see if you remember a few weeks ago and if you had any problems mounting to your PC and then your next reboot you got the Ecnryption Error.
Click to expand...
Click to collapse
no i got up an took a shower then came back it gave me an encryption error then i odin back an more trouble odined a couple more times an now it boot loop an also wont start with eugenes froyo

I know it has been awhile but think back. Were you mounted to your PC at anytime between your last reboot and the Encryption Error? Doesn't have to be right before, the error gets throw on your "next" reboot. And as you know, reboots can happen manually or for something as simple as wrong UV settings.
Looking back in this thread, I saw that you got it to boot up. See if you can do that again and then mount your External via ADB and you should to push the proper commands then. Pretty much your internal is hosed, but me and a few others are working on that too.

Can't get it to boot it makes it to Vibrant screen an shut off an on Eugene"s froyo it gives me a couple of errors an I just can't get it to start anymore it there anyone who has encountered this an got it fixed like I really need this fix I am using a blackberry please save me

YAY
I got it fixed but now im on step 13 of that guide where you have to use ADB an i cant get the phone to show up on my PC what drivers do i need i already have Vibrant drivers but still nothing an the usb works its a samsung USB so can anyone help me with ADB

I am having a similar problem. Was running ICS 4.0.3 w/Euphoria without issue until this morning. Got a couple of errors after a normal recharge. Pulled battery and rebooted, but is stuck in boot loop. Cannot access either recovery or fastboot screen. Vibrant logo flashes and release buttons, but never enters mode. Then cycles to Android screen and would likely stay there until battery died. This is primary phone and need to put back into service quickly. Any assistance will be greatly appreciated. Thanks.
JIM in FLA

Go back to stock 2.1
Sent from my SGH-T959 using XDA

stuck in recovery

I am not a computer guy--tried to install latest update and am now stuck in recovery--I tried to install a recovery off an sd card but seemed to fail and now cant get anywhere. Can anyone walk me through a fix??
Thanks

press ctrl+alt+del
not suer

Need more info. Were you on a stock or custom ROM? Are you stuck in stock or custom recovery? What method did you try to install another recovery?
Sent from my SGH-I777 using xda premium

stuck
I was custom but rooted--tried to update tonight and it failed--then tried to deroot but now stuck un clockwork recovery--I am downloading ics -us but dont even know how to access external card with this file on as recovery lets me only onto internal sd which i think i cannot access
Thanks for the help

this worked for me...my situation sounds very similar to yours....
http://forum.xda-developers.com/showpost.php?p=23587495&postcount=47

ostism attachable
seems to freeze on cold boot??? says cold booting linux but noting happens
I am stuck in something that says clockworkmod Recovery v5.5.0.4

voodoo_dr said:
seems to freeze on cold boot??? says cold booting linux but noting happens
I am stuck in something that says clockworkmod Recovery v5.5.0.4
Click to expand...
Click to collapse
5.5.0.4 from Koush has a known problem
Follow this:
http://forum.xda-developers.com/showthread.php?t=1530337
There are many ways to get out of this situation. Get all the tools (adb, ROM zip files, etc.). Read posts in the thread. Ask for help there.
Good luck.

Put your transformer in APX mode by hold the power button & volume up.. If it turns back on do it again, make sure you have you sync cable plugged in and drivers installed. Now that your in APX download this stock rom then root it with viper (option 1 in viper)
Stock rom
http://forum.xda-developers.com/showthread.php?t=1334673
Viper root works on transformer & prime for root and unroot!!!
http://forum.xda-developers.com/showthread.php?t=1427125

voodoo_dr said:
I was custom but rooted--tried to update tonight and it failed--then tried to deroot but now stuck un clockwork recovery--I am downloading ics -us but dont even know how to access external card with this file on as recovery lets me only onto internal sd which i think i cannot access
Thanks for the help
Click to expand...
Click to collapse
Why you trying a stock ota on a custom rom?
feisty_noodle said:
5.5.0.4 from Koush has a known problem
Follow this:
http://forum.xda-developers.com/showthread.php?t=1530337
There are many ways to get out of this situation. Get all the tools (adb, ROM zip files, etc.). Read posts in the thread. Ask for help there.
Good luck.
Click to expand...
Click to collapse
Yes there's a fix in there towards the bottom of the first post.
If you want to flash another recovery, turn your device on into recovery, connect it to your computer and use adb to push the file to your internal storage.
It should be something like "adb push filename.zip /data/media" then you can use the borked recovery you're on to flash the one you pushed.
tegezee said:
Put your transformer in APX mode by hold the power button & volume up.. If it turns back on do it again, make sure you have you sync cable plugged in and drivers installed. Now that your in APX download this stock rom then root it with viper (option 1 in viper)
Stock rom
http://forum.xda-developers.com/showthread.php?t=1334673
Viper root works on transformer & prime for root and unroot!!!
http://forum.xda-developers.com/showthread.php?t=1427125
Click to expand...
Click to collapse
No, this is overkill and won't fix his issue.

This will work period
fone_fanatic said:
Why you trying a stock ota on a custom rom?
Yes there's a fix in there towards the bottom of the first post.
If you want to flash another recovery, turn your device on into recovery, connect it to your computer and use adb to push the file to your internal storage.
It should be something like "adb push filename.zip /data/media" then you can use the borked recovery you're on to flash the one you pushed.
No, this is overkill and won't fix his issue.
Click to expand...
Click to collapse
Yes it will what are you talking about? If he wants his tablet to work again and if he's not worried about the data on it (since he can't access it anyway) then this will work... Overkill lol , call it what you want it will work and it's simple!

tegezee said:
Yes it will what are you talking about? If he wants his tablet to work again and if he's not worried about the data on it (since he can't access it anyway) then this will work... Overkill lol , call it what you want it will work and it's simple!
Click to expand...
Click to collapse
His problem is with it getting stuck in recovery, which is a known issue with Koush's 5.5.0.4, simple fix with adb. No need to reflash the whole rom.

voodoo_dr said:
I am not a computer guy
Thanks
Click to expand...
Click to collapse
Well if he's not good with a computer, my method is the easiest especially if he doesn't have it figured out by now...

Thanks for the help everyone--Ended up using NVflash to load a rom called prime 1.6. 3:30 a.m. and I am as good as new. No ICS but at least it is stable

Good to see you got it back working...

Testing eMMC Fix (got bricked, looking for the reason)

Well, I loved this kernel! But I appear to have bricked when flashing another (also aparrently kernel fixed) rom.
I *could* get to CWM, but I can't touch system. The phone freezes if I try to do anything.
Odin will not flash.
I'm an experienced user, I've owned several Android phones in the past and understand how everything works, however, this time, it really appears I am dead.
I can take the phone back so no big deal, but I just wanted to let people know. If I am unable to get this working, it appears the new kernels still have some risk involved.
I was on UK Stock ICS (Not sure what the version was now), flashed Francos using DD, everything was fine but Wifi did not work, so I wanted to try Speedmod. This caused a bootloop. So I reverted, and the bootloop remained. At this point I downloaded a Lite rom that used Franco V4, (sorry, the name has escaped me) this flashed but also gave a bootloop. So I wiped, and re-applied.
When I reinstalled after wiping, the install bar glitched and flew past it's usual 100% right off the side of the screen. Then it froze.
After this I am unable to flash *anything* to the phone. CWM boots but I can't do anything within it. Odin attempts to flash but I see the phone send invalid responses back (non-alphabetical characters) and Odin then fails.
Anything else I could do? I think I've tried everything possible at this point. Gutted!
[edit]
UPDATE: This does currently appear to be a case of bad luck, and NOT The eMMC Bug. The eMMC Bug fix is now under critical testing by myself (as I have access to replacement phones within minutes), though I have flashed 18 times at present with no superbricks or broken eMMCs. So far so good!

I think u wiped from ICS kernel and this may have caused u a brick. At first when you flashed speedmod and had bootloop you could have flashed back to Abyss kernel wiped and reinstalled the whole rom instead of wiping from ICS kernel and installing rom. Its a known fact that while installing or restoring roms from ICS kernels people have faced lot of issues..

I'm aware of that issue. I used Franco's R5 kernel (which is ICS and superbug fixed. The fix was not a guaranteed fix, and sadly I appear to have proven this fix to be non-working at the moment.)
I guess I'll be popping back to the shop at lunchtime!
Cheers.

One last try just pull the battery for 30 seconds and try to get into download mode and try to flash stock GB with 16gb pit file and gb bootloaders
---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------
When i had Galaxy s same thing happened to me only download mode no cwm nothing and Odin was failing to flash stock roms even with a pit file and what i did was flash with bootloaders along with pit file and rom files and voila my phone was back to bussiness

You might be right about the PIT files. It would make sense, Odin almost completes when the phone throws out the invalid text- might be trying to put data out of the partition.
I'll give it a go, thanks. I do still have Download mode. I no longer can access recovery though.

so you cant flash on ODIN?? stuck on factoryimg??

Well, that didn't go to plan. Crashed again, and now I have no download mode, instead the phone appears to be insisting that the battery is not installed. How odd!

musashiro said:
so you cant flash on ODIN?? stuck on factoryimg??
Click to expand...
Click to collapse
This was the case, yes.
Oh, I just got Download mode back, Stupid thing. What odd behavior.
I can get the phone replaced within minutes if required (I'm 5 mins away from the shop) but I'd rather try to keep my internal storage intact

Here's the guide to fix it. I along with many others managed to fix our phones using this guide: http://www.android.gs/easily-fix-bricked-samsung-galaxy-note-n7000/

Thanks for that. I'd just found it before you posted and am reading through it now.
I am half tempted to try it, but I think if there are now "bad blocks" in internal memory, I will just get it swapped for a fresh device.
It's behaving weird, sporadically thinking the battery was removed etc. so I am not 100% sure this is a superbrick /mmc problem, and it could be some other issue that cropped up. Let's hope so (because I'd really like to think Superbrick is fixed as we had suspected!)
Thanks for your input. I'm off down the shops!

Eyup! New phone in hand.
So I have 13 days in which to take advantage of this quick-swap. What I'm going to do now is begin heavy flashing with the R5 "fixed" kernel. If I succeed in breaking it, we know the fix isn't working. If I fail at breaking it, we're all good. Sound like a plan?

damiensturdy said:
Eyup! New phone in hand.
So I have 13 days in which to take advantage of this quick-swap. What I'm going to do now is begin heavy flashing with the R5 "fixed" kernel. If I succeed in breaking it, we know the fix isn't working. If I fail at breaking it, we're all good. Sound like a plan?
Click to expand...
Click to collapse
Yes seems like a good plan to me, looking forward to get results from you soon.
Thanks

Right, OK, I managed to duplicate the crash, but instead of using ODIN which failed the first time round and caused very, very weird behavior, I installed THOR'S CWM. This was able to unmount, format, etc the system partition. This means that despite the other errors, there was no EMMC damage
(I'm aware the damage is not always the same, but I was able to consistently cause the crash with no damage.)
After installing Thor, I was able to reinstall other roms
IMPORTANT!!!
When I tried to install Thor's CWM, It froze - I gave up hope here, but after forcing a reboot the phone had Thor's CWM anyway, so it'd written the important parts over before crashing
Hope this helps. If you find yourself with a recovery unable to flash roms, try flashing Thor's CWM, it may freeze, but give it a minute then pull the battery and re-enter recovery. Fingers crossed

Glad to have someone willing to risk their devices in these dark times. Well appreciated!
Sent from my GT-N7000 using Xparent ICS Tapatalk 2

In order to run the test, you need to actually boot up the device, go through the settings, and install a few apps. Then go to recovery, and perform a wipe.
Simply hitting the Wipe key in succession (like 100 times) does not work. There must be something to format in the respective partitions.
Thank you for doing what you're doing. But if you could, and only if you have the time, could you try wiping from CWM (just wiping, not nandroid restore), for say 20 ~ 30 times? It's very tedious to do it due to the setting up and needing to wait for it to boot and install a few apps from the market.
I'm sure with 20 ~ 30 or more wipes on a single device, we can safely say that the fix is a likely permanent fix.
damiensturdy said:
Right, OK, I managed to duplicate the crash, but instead of using ODIN which failed the first time round and caused very, very weird behavior, I installed THOR'S CWM. This was able to unmount, format, etc the system partition. This means that despite the other errors, there was no EMMC damage
(I'm aware the damage is not always the same, but I was able to consistently cause the crash with no damage.)
After installing Thor, I was able to reinstall other roms
IMPORTANT!!!
When I tried to install Thor's CWM, It froze - I gave up hope here, but after forcing a reboot the phone had Thor's CWM anyway, so it'd written the important parts over before crashing
Hope this helps. If you find yourself with a recovery unable to flash roms, try flashing Thor's CWM, it may freeze, but give it a minute then pull the battery and re-enter recovery. Fingers crossed
Click to expand...
Click to collapse

So, in short, you had /system corrupted at the filesystem level, not the eMMC level. This seems to be a common problem on the Note, and some people falsely describe it as "partial root". CM9's initramfs has had changes made to make it easier to fix these problems by not automatically mounting /system on entry into recovery.
The problem was: If /system was corrupted due to plain-jane filesystem corruption, it would be mounted read-only if mounted at any time. Also, it seems that CWM would be unable to unmount it, preventing CWM from reformatting it.
Solution (which I haven't fully tested as I haven't had this issue in a few weeks, but I have encountered it before) is not to mount /system automatically on boot when entering recovery.
I pointed Franco to the fix for this but I'm not sure if he's included it yet.
Note that this is NOT the eMMC brick bug, it's completely different and is recoverable.
Alternate recovery method:
In CWM, connect via ADB, and in an ADB shell:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
Clobbers the first 1M of system so CWM will completely fail to mount it instead of treating it as corrupt. At this point it can be formatted in CWM's Mounts and Storage menu.

Good input guys. Thanks.
Yes, indeed this didn't appear to be the eMMC Bug. I can't guarantee what it was on the old phone (which did appear bricked.), I just know I started off the same. It's more likely that I knackered it with failed Odin flashes than the eMMC bug at this time.
I'm still flashing, installing, wiping, etc. I'm basically trying everything that we're not supposed to do. So far the worst I've got is a corrupt system partition (indeed, that is not an eMMC bug) but the only CWM able to fix that was Thors.
Basically if I knacker the phone I can get it replaced within minutes, so I might as well take advantage so that we can all relax knowing it's fixed (or continue to look for a fix if it isn't)
Obviously I shouldn't take the piss. If somehow I brick it a couple more times I'll be forced to stop. But I like to help so let's go! :-D

What does "flashed Franco from DD" mean? After that process did you ever verify that you where actually on Franco?
Perhaps the kernel flash didn't take and your subsequent wipes/flashes where from stock ICS kernel.
Sent from my GT-N7000 using xda premium

Entropy512 said:
The problem was: If /system was corrupted due to plain-jane filesystem corruption, it would be mounted read-only if mounted at any time. Also, it seems that CWM would be unable to unmount it, preventing CWM from reformatting it.
Solution (which I haven't fully tested as I haven't had this issue in a few weeks, but I have encountered it before) is not to mount /system automatically on boot when entering recovery.
I pointed Franco to the fix for this but I'm not sure if he's included it yet.
Note that this is NOT the eMMC brick bug, it's completely different and is recoverable.
Alternate recovery method:
In CWM, connect via ADB, and in an ADB shell:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
Clobbers the first 1M of system so CWM will completely fail to mount it instead of treating it as corrupt. At this point it can be formatted in CWM's Mounts and Storage menu.
Click to expand...
Click to collapse
VERY Useful information. Just got myself back into this situation and this did fix it without Thors CWM, although I recommend everyone have a copy of Thor's CWM on their card just in case!
Actually I notice that Thor does NOT Mount System by default, this seems to match your information.
Nice one, Thanks!

damiensturdy said:
VERY Useful information. Just got myself back into this situation and this did fix it without Thors CWM, although I recommend everyone have a copy of Thor's CWM on their card just in case!
Actually I notice that Thor does NOT Mount System by default, this seems to match your information.
Nice one, Thanks!
Click to expand...
Click to collapse
That's because he kangs from CM and then releases warez based on our work.
Linux kernel without source code published = warez.

Stuck at google logo, recovery mode doesn't work?

I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.

calavera-pw said:
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
Click to expand...
Click to collapse
before you do anything, use your recovery to see if the rom zip is located in /data/media/0/. if its there, flash it from that location.

Are you able to boot into recovery?
If yes, it could be as simple as plugging your tablet into the computer and mounting the usb, drag and drop the rom, and flash it without using a toolkit (only recovery). I'm not familiar with jrom flasher, but i will say the more variables there are, the more chance of a problem.
If no, you're best off running the stock factory image through your computer, found here: https://developers.google.com/android/nexus/images#nakasi. I had your problem at one point, and could not even boot into recovery. After trying to install cwm through adb (which failed), and a number of toolkits, the factory image was what brought my nexus back to life.
I remember reading that sometimes a wipe can delete your recovery as well as your system (and whatever else you have on your n7), although i dont know if that was ever fixed, as i got my tab replaced a month or two ago and havent rooted it again yet. There was some type of command or .zip or something that should be used to keep recovery after wipes. When i expirienced problems such as yours, it was also from a bad wipe from a toolkit. Using just the recovery afterwards, i never expirienced any issues, even without the recovery fix.
I would definitely try simms suggestion first if you can access recovery. If that fails, try one of the above processes.
PS, even if you can access recovery, if at this point you just want to go completely stock, the factory image will work regardless.
cheers

Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.

calavera-pw said:
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
Click to expand...
Click to collapse
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:

appoos said:
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
Click to expand...
Click to collapse
ADB
Sent from my Galaxy Nexus

Pirateghost said:
ADB
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This dint work in my windows 8

appoos said:
This dint work in my windows 8
Click to expand...
Click to collapse
You're holding it wrong. ADB works on my Win8 machine

Pirateghost said:
You're holding it wrong. ADB works on my Win8 machine
Click to expand...
Click to collapse
can you tell me the procedure..

appoos said:
can you tell me the procedure..
Click to expand...
Click to collapse
no.
in the other thread that YOU created, you were given links to follow and the instructions are already there. i dont hold hands

I could do it with ADB..thanks guys