Develop Bugs

AOSP 2.99 beta5 (five) Reboot loop! bricked

The problem I encountered must be the worst problem ever! For some reason my nexus reboot randomly and its not just a regular reboot but it reboot as a DEEP FREEZE. So basically once it rebooted, it goes back to a same specific point of time. I can't even delete stuff from the phone, for example if I deleted 1GB of music off my phone, after few second the phone will reboot automatically OR if i reboot the phone myself the 1GB of music would be back in my phone. Like WTH? I am completely lost. I have no idea how it happened, but I know it happened after I installed Paranoid Android AOSP 2.99 beta5. I was fine when flashing Paranoid Android 1,3,4. ALSO I cannot do a factory reset or install a factory rom. It just go back to 4.2.1 AOSP 2.99 beta5...
please guys, if anyone can help me that would be great. If you guys need more explaining please email or PM me. I will be glad to write a whole essay on what you guys need to know to help me out. Thank you

Go back to stock and start fresh.
Sent from my i9250

bk201doesntexist said:
Go back to stock and start fresh.
Sent from my i9250
Click to expand...
Click to collapse
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..

Yellowfriedrice said:
Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here

ahmadallica said:
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here
Click to expand...
Click to collapse
You cant brick a nexus! Try making a jig with this link http://www.youtube.com/watch?v=jKRrTZayRxU Then get download odin and an img file of whatever rom you want and flash it through odin. Problem should be solved.

Yellowfriedrice said:
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out

khuzema9 said:
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out
Click to expand...
Click to collapse
Based on the language used in the OP I think he used a toolkit to root/unlock his Nexus and that's why he knows nothing about his device and how to fix it.
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again

altimax98 said:
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again
Click to expand...
Click to collapse
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck

still didn't work
ahmadallica said:
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck
Click to expand...
Click to collapse
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you

Yellowfriedrice said:
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you
Click to expand...
Click to collapse
I really have not done anything to my GNex via Windows becuse I am using Ubuntu Linux so I have not experienced installing these drivers on Windows. I also have neither returned my phone to stock before nor used the Nexus toolkit. I am doing everything manually.
I think you are referring to the drivers in this page. If you are using Windows 8 then there are some steps mentioned on how to get pass the driver signature enforcement.
If you are on Windows 7, then look here.
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?

ahmadallica said:
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?
Click to expand...
Click to collapse
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol

Yellowfriedrice said:
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol
Click to expand...
Click to collapse
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!

ahmadallica said:
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!
Click to expand...
Click to collapse
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.

Yellowfriedrice said:
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.
Click to expand...
Click to collapse
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck

ahmadallica said:
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.

ahmadallica said:
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
Thank Goodness im not the only one who has this issue... Bugs the crap outta me lol..
To the OP:
Try this, 1: make sure your an admin on your PC. From the sounds of it you may not be if it said 'access denied'. 2: Plug your nexus in while in the 'device manager' section of windows. 3: Find the new device and delete it. Delete anything that says Android ADB or Android anything or galaxy Nexus or Galaxy phone. Just delete them. Windows will warn you but do it anyways... 4: reboot the pc. 5: Plug your nexus back in, it should either install the device or fail. At that point find and download the newest samsung naked drivers and use the option on windows to install driver from disk and navigate to your unzipped folder.
That is the sure fire way to get it working again. Sorry to say if you still have driver issues then your doing something wrong. Do alot of reading and the answer will show itself.

1. Can you boot your phone into fastboot mode?
2. If so, once in fastboot mode, what happens when you connect the phone to the computer?
It is very very difficult to brick a nexus, so don't worry... .

Yellowfriedrice said:
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.
Click to expand...
Click to collapse
Sorry for not being able to help you better. I'm sure that others who are familiar with Windows can help you overcome your earlier issues with drivers and so on thus be able to return to stock and start fresh
Good Luck

It is very very difficult to brick a nexus said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse

OKAY i tried everything.. nothing seem to work.. selling my nexus!
Yellowfriedrice said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse

I think I bricked my New Nexus 7

I'm new to the forums and I've been searching and reading all over for help. This was my first time rooting. I was trying to flash a rom in TWRP and somehow erased everything, no OS or anything. Now when I boot up it only says google. It won't load past that. I can get into the fastboot screen but the adb options don't work. And now since trying two different tool kits to flash to stock image, I can't get on TWRP anymore. Any help would be great thanks. I'm not even sure what I did but I can try to add more information. Thanks

You can boot in fastboot and flash it back to stock.
I see Google hasn't posted the factory images out there yet, your tablet is fixable, but you need the image. Maybe someone else can chime in with a image I haven't found yet. BTW, you can fastboot flash the recovery if its a .IMG file to get that back.
Note: you'll need the android SDK because you'll need the fastboot drivers and the fastboot.exe program to flash back.
Sent from my Nexus 7 FHD using Tapatalk 2

trssho91 said:
Can you boot into fastboot mode by holding all three buttons for 5 seconds with the device off? It doesn't need a os or recovery just as long as you didn't kill the bootloader. Once in fastboot just flash it back to stock.
Download your image here: https://developers.google.com/android/nexus/images
Don't freak out yet, its hard to brick a nexus device
Edit, I just saw you said you can get fastboot. Use the link I posted to download your image, if you need the android SDK because you'll need the fastboot drivers and the fastboot.exe program to flash back.
Sent from my Nexus 7 FHD using Tapatalk 2
Click to expand...
Click to collapse
Obviously ADB would not work in fastboot. Erasing your ROM and recovery is no where near being bricked. You get into bootloader by holding Power + Volume down. Google has not released the official image package yet so flash the stock images from these -
http://forum.xda-developers.com/showthread.php?t=2381438
http://forum.xda-developers.com/showthread.php?t=2381582

I'll try this all out in the morning. It's getting late here. Thank you and I'll be back to give you all an update!

You could even skip flashing the stock recovery and reflash TWRP. Rename it "recovery.img" put it in platform-tools... Then:
fastboot flash recovery recovery.img
TWRP should be flashed. Install a stock deodex or odex ROM and wipe data before install. Should be good.
But, everyone else's solutions will also work too (ie you are NOT bricked )
Sent from my Nexus 4 using Tapatalk 4 Beta

I need help also im trying to restore with the images but its hanging when i get to the flash system part it just sits there and i dont have a system to bootup to if i wanted to what can i do ??
Okay i guess i just had to wait a lil bit longer its finally flashing the system
Sent from my Nexus 4 using Tapatalk 4 Beta

I think I'm having some problems trying to download things in the correct folders, seeing as I don't understand most of the lingo. I used a all in one tool to unlock the bootloader and root but when I tried putting things in the folder it wouldn't load properly. I deleted everything off of my pc and I'm going to redownload everything and try again.
Tried http://forum.xda-developers.com/showthread.php?t=2381582 early this morning and it wouldn't load properly. I ran it and it said ?????? fastboot and then said some files were missing. Let me get back at it though.

You're just gonna have to own up and install the SDK. It only takes a few commands once it's downloaded.
http://developer.android.com/sdk/index.html
Sent from my Nexus 4 using Tapatalk 4 Beta

Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.

Geodude074 said:
Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.
Click to expand...
Click to collapse
Yea thats correct zedomax made a zip on here that only has the files u need
Sent from my Nexus 7 using Tapatalk 4 Beta

Geodude074 said:
Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.
Click to expand...
Click to collapse
+1 I didn't know somebody compiled that for the new N7. I was mostly trying to get this fellow to shy away from the toolkits - not that they're bad... But when they mess up, it's a headache to recover.
Sent from my Nexus 4 using Tapatalk 4 Beta

When I post on here I think its better to assume I'm posting to a noob rather assuming they know something they don't and making their situation more stressful. The SDK is a blanket install and you know everything is there. For someone inexperienced its better than: get this driver, and this one, and these files...move them here..you get the idea.
Sent from my SAMSUNG SGH-I747 running CyanogenMod.

Anisak said:
Tried http://forum.xda-developers.com/showthread.php?t=2381582 early this morning and it wouldn't load properly. I ran it and it said ?????? fastboot and then said some files were missing. Let me get back at it though.
Click to expand...
Click to collapse
The guide on that thread should work really well, but I will just point out that for me, ADB wasn't working (yet) while I was still trying to flash TWRP on it, so the 'ADB reboot bootloader' line in the "Recovery_Nexus7.bat" was pointless. In my case, I go to the bootloader/fastboot mode by holding the power button + volume down.
Once in fastboot/bootloader mode, ensure that fastboot can see your N7 2013 by typing 'fastboot devices'. If you see your device there, you are good to proceed with flashing all the files that are in that zip file. It even roots your device. Good luck and let me know if you need any further help.

zeppelin101 said:
The guide on that thread should work really well, but I will just point out that for me, ADB wasn't working (yet) while I was still trying to flash TWRP on it, so the 'ADB reboot bootloader' line in the "Recovery_Nexus7.bat" was pointless. In my case, I go to the bootloader/fastboot mode by holding the power button + volume down.
Once in fastboot/bootloader mode, ensure that fastboot can see your N7 2013 by typing 'fastboot devices'. If you see your device there, you are good to proceed with flashing all the files that are in that zip file. It even roots your device. Good luck and let me know if you need any further help.
Click to expand...
Click to collapse
Oh disregard my last comment. I got it to work! Thank you everyone for the help!

Anisak said:
When I type fastboot devices nothing comes up. And I can't seem to unlock or lock it now. (Was testing that command)
Click to expand...
Click to collapse
Are you logging in from your administrator account and is it windows 8 by any chance ?
Well, Rule is log into from your administrator account and windows 8 will need manual drivers installation for your Nexus 7 (2013). Try downloading USB drivers from SDK.
I am also attaching fastboot drivers which I hope will work
Good luck

Hnk1 said:
Are you logging in from your administrator account and is it windows 8 by any chance ?
Well, Rule is log into from your administrator account and windows 8 will need manual drivers installation for your Nexus 7 (2013). Try downloading USB drivers from SDK.
Good luck
Click to expand...
Click to collapse
I'm on windows 7 but I did read about something about being on admin and that did the trick. Before it wasn't letting me run anything and not warning me to do so either. But I got it! Thanks to everyone for the help and advice. :victory:

[Q] URGENT: Flashed Wrong Kernel To My Nexus 7 (flo)!

Hi guys. I recently flashed the Glitched Kernel (http://forum.xda-developers.com/showthread.php?t=2449919) to my Nexus, but I accidently downloaded the wrong one. Not knowing this, I flashed it via TWRP and now my device crashes completely (my computer won't even recognize it) on the lock screen. I can still boot into the bootloader, TWRP, and MultiROM easily. I just can't boot up Cyanogenmod (Only rom I have on the device as of now). I really don't know what to do. I've tried connecting via USB in the bootloader, my computer won't even pick up the device. I've also tried adb sideload a new rom and a new kernel, but I get the error 'protocol fault (no status)' which is weird, because ADB recognizes my device (I typed the 'adb devices' command in CMD) How can I flash the stock kernel back onto it?
Thanks in advance,
~NascarBoy119

Just clean flash cyanogenmod again if you have the Rom as .zip on your device. If not use ADB to get a Rom for flashing on your device.

Restore your backup (nandroid).

detoxN said:
Just clean flash cyanogenmod again if you have the Rom as .zip on your device. If not use ADB to get a Rom for flashing on your device.
Click to expand...
Click to collapse
I can't download anything to my device. ADB sideload won't work also (I get the error 'protocol fault [no status]), as I stated above.
Also @wantabe
Shortly before this I ran Clean Master on my device. Turned out it deleted my backups... After that, all this drama happened. Probably kinda my fault as I used the TWRP backup feature instead of NanDriod.

NascarBoy119 said:
I can't download anything to my device. ADB sideload won't work also (I get the error 'protocol fault [no status]), as I stated above.
Also @wantabe
Shortly before this I ran Clean Master on my device. Turned out it deleted my backups... After that, all this drama happened. Probably kinda my fault as I used the TWRP backup feature instead of NanDriod.
Click to expand...
Click to collapse
adb is your friend. There is plenty of opportunities. You could download a ROM on your computer and sideload or push it in adb. You could also download stock images and fastboot it in the bootloader. Simple...
Sent from my Nexus 7 using Tapatalk

NascarBoy119;49329133]I can't download anything to my device. ADB sideload won't work also (I get the error 'protocol fault [no status]).
Click to expand...
Click to collapse
nikr123 said:
adb is your friend. There is plenty of opportunities. You could download a ROM on your computer and sideload or push it in adb. You could also download stock images and fastboot it in the bootloader. Simple...
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
As you see the text that I put in bold, ADB sideload/pushing gives me an error. I might try the fastboot thing though but then I'll lose all my data, right?

NascarBoy119 said:
As you see the text what I put in bold, ADB sideload/pushing gives me an error. I might try the fastboot thing though but then I'll lose all my data, right?
Click to expand...
Click to collapse
what android version are your running?
anyways grab the gltiched kernel for your device this time.
then put your device i to recovery: up/down volume plus power when device is off
once in recovery type thus from your computer.
fastboot flash boot boot.img
you will need to extract the image from the glitched-kernel.zip
no this will not wipe your data. it is the manual way of flashing a kernel.
hope that helps.

NascarBoy119 said:
As you see the text what I put in bold, ADB sideload/pushing gives me an error. I might try the fastboot thing though but then I'll lose all my data, right?
Click to expand...
Click to collapse
Fastboot is your friend in this case, as long as you didn't relock your bootloader you can flash without losing your data.
userdelroot said:
no this will not wipe your data. it is the manual way of flashing a kernel.
hope that helps.
Click to expand...
Click to collapse
^this
Not using cleanmaster to delete your backups was a lesson you learned the hard way, but it is not unrecoverable and you can chalk it up as a learning experience.
Let us know how it worked out, everything will be fine as long as you take your time and relax. This is something that happens to most people sooner or later and is a great confidence builder (once you work through it).

To avoid this I keep all my backups, zips and other flashaholic stuff on a USB drive mounted using an USB OTG cable. You can mount it and use it in recovery.

megabatteryman said:
To avoid this I keep all my backups, zips and other flashaholic stuff on a USB drive mounted using an USB OTG cable. You can mount it and use it in recovery.
Click to expand...
Click to collapse
This may very well be the top reason to buy an OTG cable and/or OTG Micro SD reader / hub device
Sent from my Nexus 7 using XDA Premium HD app

userdelroot said:
what android version are your running?
anyways grab the gltiched kernel for your device this time.
then put your device i to recovery: up/down volume plus power when device is off
once in recovery type thus from your computer.
fastboot flash boot boot.img
you will need to extract the image from the glitched-kernel.zip
no this will not wipe your data. it is the manual way of flashing a kernel.
hope that helps.
Click to expand...
Click to collapse
oldsoldier2003 said:
Fastboot is your friend in this case, as long as you didn't relock your bootloader you can flash without losing your data.
Not using cleanmaster to delete your backups was a lesson you learned the hard way, but it is not unrecoverable and you can chalk it up as a learning experience.
Let us know how it worked out, everything will be fine as long as you take your time and relax. This is something that happens to most people sooner or later and is a great confidence builder (once you work through it).
Click to expand...
Click to collapse
I did what you guys said and it work flawlessly. Thank you so much! I was worried I permanently bricked my device. I though about buying an OTG cable, but now I think I'm buying it for sure. I'll try to store some backups on it too.

Awesome, glad we could help

[Q] Accidently Deleted Android and Don't Know How To Reflash It!

I had some problems with sound and couldn't get anything to fix it. So i rebooted the bootloader and was going to hard reset the device. But i accidently hit the wrong one and it deleted my OS. I don't know how to put android back on and my computer won't detect my device. My bootloader is unlocked and i have Team Win Recovery. What should i do?!

GabuscusMason said:
I had some problems with sound and couldn't get anything to fix it. So i rebooted the bootloader and was going to hard reset the device. But i accidently hit the wrong one and it deleted my OS. I don't know how to put android back on and my computer won't detect my device. My bootloader is unlocked and i have Team Win Recovery. What should i do?!
Click to expand...
Click to collapse
You will need to use the ADB sideload feature of TWRP to upload a rom to install. Research ADB on how to use it as well as the sideload feature of TWRP. You will need to connect the tablet to your PC for this,.

What he said ^^
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

NRT has and does everything you need:
http://forum.xda-developers.com/showthread.php?t=2389107
As long as you can get the ADB drivers installed on your PC, you can click Advanced Utilities "Launch," then "Flash Zips" and select a rom zip on your desktop to flash to the tablet.

And as for adb drivers, here is a link to a post by Koush with a driver install that should work without any issues.
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH

DaveRichardson said:
NRT has and does everything you need:
http://forum.xda-developers.com/showthread.php?t=2389107
As long as you can get the ADB drivers installed on your PC, you can click Advanced Utilities "Launch," then "Flash Zips" and select a rom zip on your desktop to flash to the tablet.
Click to expand...
Click to collapse
I've done what the OP has done, and if I recall, getting the device into download mode will allow Wug's Toolbox to pick it up from there. I reinstalled the OEM rom, rerooted and reinstalled TWRP. You can download the OEM rom from the toolbox.

[Q] Device bricked after trying to change ROM

I just bricked my galaxy nexus by trying to install Shiny ROM. I've got a (europe) maguro galaxy nexus which ran PA before, but I wanted to update as it became extremely slow at times.
Using TWRP v2.5.0.0 I did a factory reset(data, cache and dalvik wipe). I then tried to install ShinyROM, but it gave the following error:
Updating partition details...
Formatting Cache using make_ext4fs...
Done.
Wiping data without wiping /data/media ...
Done.
Updating partition details...
Installing '/sdcard/modsnstuff/ShinyROM_maguro_a
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
Installing Shiny ROM build 062114
for maguro
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/modsnstuff/ShinyROM_
Updating partition details...
Click to expand...
Click to collapse
I also put a new PA version on the phone, which gave a similar error.
I tried using the android toolkit to get into adb recovery and flash a new rom somehow. I did not succeed to install the drivers successfully, which is probably because I am not able to boot into android. I do not see how I can use the toolkit now, and since I barely know what it does and I would not know how to install the drivers.
What can I do to correctly install the new ROM, or at least get it to boot in any version of android?

inasm said:
I just bricked my galaxy nexus by trying to install Shiny ROM. I've got a (europe) maguro galaxy nexus which ran PA before, but I wanted to update as it became extremely slow at times.
Using TWRP v2.5.0.0 I did a factory reset(data, cache and dalvik wipe). I then tried to install ShinyROM, but it gave the following error:
I also put a new PA version on the phone, which gave a similar error.
I tried using the android toolkit to get into adb recovery and flash a new rom somehow. I did not succeed to install the drivers successfully, which is probably because I am not able to boot into android. I do not see how I can use the toolkit now, and since I barely know what it does and I would not know how to install the drivers.
What can I do to correctly install the new ROM, or at least get it to boot in any version of android?
Click to expand...
Click to collapse
Search for using fastboot to return to stock Google image(stock ROM). Then install custom recovery again and flash a ROM.
This phone is nearly impossible to brick

DR3W5K1 said:
Search for using fastboot to return to stock Google image(stock ROM). Then install custom recovery again and flash a ROM.
This phone is nearly impossible to brick
Click to expand...
Click to collapse
Thanks a lot for the reply, trying it now. Apologies if I misused the word brick btw.

inasm said:
Thanks a lot for the reply, trying it now. Apologies if I misused the word brick btw.
Click to expand...
Click to collapse
No need to apologize just didn't want you to think that you were stuck.
Also it will be very beneficial to study up on adb along with fastboot.
If you learn these two things you will be able to get out of just about any sticky situation you run into.
PS The most difficult part is getting the drivers installed.

DR3W5K1 said:
No need to apologize just didn't want you to think that you were stuck.
Also it will be very beneficial to study up on adb along with fastboot.
If you learn these two things you will be able to get out of just about any sticky situation you run into.
PS The most difficult part is getting the drivers installed.
Click to expand...
Click to collapse
Would you happen to have a link to a post of some sort? I tried downloading the drivers, then installing them using device manager which didn't work, since windows said they were up to date already. All other guides I found to install the right drivers were with a working android version. Even the soft brick guides assume you have installed the drivers already.

inasm said:
Would you happen to have a link to a post of some sort? I tried downloading the drivers, then installing them using device manager which didn't work, since windows said they were up to date already. All other guides I found to install the right drivers were with a working android version. Even the soft brick guides assume you have installed the drivers already.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1583801. Use this for driver issues.
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895 use this to return to stock.
With these guides you can fix it!

DR3W5K1 said:
http://forum.xda-developers.com/showthread.php?t=1583801. Use this for driver issues.
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895 use this to return to stock.
With these guides you can fix it!
Click to expand...
Click to collapse
The driver still seems to refuse to work. It keeps saying the latest driver is installed. I am using Windows 7 in stead of 8, which is why the guide might not apply 100% to me.
When I use the Android ToolKit and I try to flash the google ROM, it does detect a device in ADB MODE, and it gets the serial number, but it gets stuck on "Waiting for adb Mode". Does this mean the drivers are already correctly installed?
EDIT:
I remembered that I downloaded an old version of PA a long time ago using goo manager, which was still on my phone. ADB drivers are also installed now it seems, now I just have to install the 4.4 version correctly.
Thanks a lot for your help!

inasm said:
The driver still seems to refuse to work. It keeps saying the latest driver is installed. I am using Windows 7 in stead of 8, which is why the guide might not apply 100% to me.
When I use the Android ToolKit and I try to flash the google ROM, it does detect a device in ADB MODE, and it gets the serial number, but it gets stuck on "Waiting for adb Mode". Does this mean the drivers are already correctly installed?
EDIT:
I remembered that I downloaded an old version of PA a long time ago using goo manager, which was still on my phone. ADB drivers are also installed now it seems, now I just have to install the 4.4 version correctly.
Thanks a lot for your help!
Click to expand...
Click to collapse
Your welcome but you should have been using fastboot instead of adb. For future reference they are two different things