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
Related
So I used that other non- CWM recovery image to wipe some stuff on the device, and I also wiped the rom before copying a new one for install.
Now when I try to adb-push a rom, I get a "device not found" error.
I tried flashing stock Google image using Galaxxy Nexus Toolkit but it's stuck on "waiting for device".
I also installed the driver using the toolkit and restarted the PC and replugged the phone.
The phone isn't shown on Windows and Windows automatically tries to install a driver for it and fails.
What do I do? Can I get a manual driver to install or is it something entirely different?
yonyz said:
So I used that other non- CWM recovery image to wipe some stuff on the device, and I also wiped the rom before copying a new one for install.
Now when I try to adb-push a rom, I get a "device not found" error.
I tried flashing stock Google image using Galaxxy Nexus Toolkit but it's stuck on "waiting for device".
I also installed the driver using the toolkit and restarted the PC and replugged the phone.
The phone isn't shown on Windows and Windows automatically tries to install a driver for it and fails.
What do I do? Can I get a manual driver to install or is it something entirely different?
Click to expand...
Click to collapse
[ADB/FB/APX Driver] Universal Naked Driver 0.7
Thank you, I was able to push the rom and am now installing it.
yonyz said:
Thank you, I was able to push the rom and am now installing it.
Click to expand...
Click to collapse
just a tip its for times like these that its recommend you make a nandroid backup before wiping in cwm
k786 said:
just a tip its for times like these that its recommend you make a nandroid backup before wiping in cwm
Click to expand...
Click to collapse
Thank you too.
Hi, I just got a Sprint Galaxy Nexus off ebay. It came rooted with team win recovery and a custom rom based on jelly bean 4.1.1. It worked fine. It had goo manager, so I downloaded two different roms to flash before I activated the phone. I wiped the system, factory reset, casce and Dalvik Cache, then flashed the rom. It failed. I hit wipe cache/dalvik, it said successful. Like a dumbass, I rebooted even though it said there was no os installed. Now, neither rom will flash, it will only boot into win recovery and it won't mount to my pc. Is there anyway I can fix this?
Nadreo said:
Hi, I just got a Sprint Galaxy Nexus off ebay. It came rooted with team win recovery and a custom rom based on jelly bean 4.1.1. It worked fine. It had goo manager, so I downloaded two different roms to flash before I activated the phone. I wiped the system, factory reset, casce and Dalvik Cache, then flashed the rom. It failed. I hit wipe cache/dalvik, it said successful. Like a dumbass, I rebooted even though it said there was no os installed. Now, neither rom will flash, it will only boot into win recovery and it won't mount to my pc. Is there anyway I can fix this?
Click to expand...
Click to collapse
Did you do a backup before you flashed? If so, have you tried using the backup? If you did not, maybe the person before you who rooted the phone did a backup.
[email protected] said:
Did you do a backup before you flashed? If so, have you tried using the backup? If you did not, maybe the person before you who rooted the phone did a backup.
Click to expand...
Click to collapse
no, I did not make a backup. I unwisely assumed the person before me did. they did not.
I'm not sure where the guide is but you should search on how to push files to the phone via ADB, once you have the file on your phone I think you should be able to flash a new rom and be back to normal.
Since you now own a nexus, you should learn how to use fastboot and adb. I'd restore every thing to stock by flashing the factory images for your phone. See my post below:
http://forum.xda-developers.com/showthread.php?p=35247414
Sent from my Galaxy Nexus using xda premium
mwalt2 said:
Since you more own a nexus, you should learn how to use fastboot and adb. I'd restore every thing to stock by flashing the factory images for your phone. See my post below:
http://forum.xda-developers.com/showthread.php?p=35247414
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I almost wish the toolkit didn't exist so everyone would do this and never need help ever again. Teach a man to fish...
mwalt2 said:
Since you now own a nexus, you should learn how to use fastboot and adb. I'd restore every thing to stock by flashing the factory images for your phone. See my post below:
http://forum.xda-developers.com/showthread.php?p=35247414
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I downloaded the factory image, unzipped in the same directory as fastboot and adb, restarted phone into bootloader, ran the commands, got <waiting for device> like the other guy in that post, already had the drivers but reinstalled anyway, updated driver in device manager--it sees it as Android 1, but has the correct driver and says is working properly--tried several different ways to flash the system.img, still get the <waiting for device> any suggestions?
thanks for your help by the way, really appreciate it.
Nadreo said:
I downloaded the factory image, unzipped in the same directory as fastboot and adb, restarted phone into bootloader, ran the commands, got <waiting for device> like the other guy in that post, already had the drivers but reinstalled anyway, updated driver in device manager--it sees it as Android 1, but has the correct driver and says is working properly--tried several different ways to flash the system.img, still get the <waiting for device> any suggestions?
thanks for your help by the way, really appreciate it.
Click to expand...
Click to collapse
It should say Android ADB Interface under ADB Interface in Device Manager. Mine says Samsung Android ADB Interface. The waiting for device is a driver issue. I've usually had to install drivers for it to recognize the phone in fastboot, even if it is already recognized by adb.
mwalt2 said:
It should say Android ADB Interface under ADB Interface in Device Manager. Mine says Samsung Android ADB Interface. The waiting for device is a driver issue. I've usually had to install drivers for it to recognize the phone in fastboot, even if it is already recognized by adb.
Click to expand...
Click to collapse
Praise baby jesus and yourself kind sir! I finally got the ****ing thing to work. It was the drivers all along. Had to go into the registry and edit the string for portable devices and fix the port numbers. After that everything worked just fine, Thanks again for your help!
Nadreo said:
Praise baby jesus and yourself kind sir! I finally got the ****ing thing to work. It was the drivers all along. Had to go into the registry and edit the string for portable devices and fix the port numbers. After that everything worked just fine, Thanks again for your help!
Click to expand...
Click to collapse
Haha, glad you got it working. It's really nice having an open device like the nexus and now you learned how to use some of the tools (no need for a 'toolkit'!).
Sent from my Nexus 7 using xda premium
Hello
I have purchased a second hand Nexus. It is rooted and has got custom rom. Also Teamwinner or so is installed. When i boot into recovery to install some other rom it exits with error 7. Same when i try to update the teamwinner to the newest version.
Any idea what to try?
dosada said:
Hello
I have purchased a second hand Nexus. It is rooted and has got custom rom. Also Teamwinner or so is installed. When i boot into recovery to install some other rom it exits with error 7. Same when i try to update the teamwinner to the newest version.
Any idea what to try?
Click to expand...
Click to collapse
i remember seeing error 7 before on a rom i tried to flash.. i was using CWM so its not the recovery's fault. turns out there was a problem with the rom...
so find another rom to flash would be my answer for now.
The problem is that i get this error whatever i tried to flah. Even cwm or some other rom result in same error
dosada said:
The problem is that i get this error whatever i tried to flah. Even cwm or some other rom result in same error
Click to expand...
Click to collapse
What procedure are you using to flash? What file are you trying to flash and where did you get it from?
I start up the phone using volume down and power. Then in teamwinner i chose install zip and then the file
so far have tried, all downloaded from here or linked from here, those files
CWM-Touch-6.0.2.5-DJ
Hellybean-20130405-crespo
TWRP-2.4.4.0-DJ
jellyshot_crespo-v3.3
nothing works. all of them exist with error 7
dosada said:
I start up the phone using volume down and power. Then in teamwinner i chose install zip and then the file
so far have tried, all downloaded from here or linked from here, those files
CWM-Touch-6.0.2.5-DJ
Hellybean-20130405-crespo
TWRP-2.4.4.0-DJ
jellyshot_crespo-v3.3
nothing works. all of them exist with error 7
Click to expand...
Click to collapse
.....
This is the Galaxy Nexus forums, that firmware aka ROM is for crespo aka Nexus S
Sent from my Nexus
Fair enough about the roms, but why cant i even install cwm? This shows me just the error 7 too
I wouldn't be surprised if your recovery is either not for your device or not even a flash able zip.
dosada said:
Fair enough about the roms, but why cant i even install cwm? This shows me just the error 7 too
Click to expand...
Click to collapse
Where did you get that CWM? http://www.clockworkmod.com/rommanager? If so those are img files, for flashing from fastboot. But I have no idea what "DJ" is for. To flash from recovery it needs to be packaged in a flashable zip.
Or you can install CWM from the ROM Manager app. Or TWRP from GooManager.
quite frankly i wouldnt use CWM. The UI is annoying as hell, and it tends ot be a lot slower, at least from my own experience.
I recommand TWRP, http://www.teamw.in/project/twrp2/90 latest version here for maguro.
if you have adb set up, installing twrp is cake, simply open adb and type:
1) adb reboot bootloader
2) fastboot flash recovery TWRP.img <-----assuming you are in the directory of that img file you just downloaded, and TWRP is just the name of the img file, its usually attached with version, so i would rename it for easier access.
3) after you flashed it just boot into recovery and start flashing your new rom.
If all else fail.....use the toolkit and flash factory image for a fresh start, i havnt failed with factory image yet
Earlier today I was running CM 10.2 on Android 4.3.2. I checked the nightlies for the first time in awhile saw CM 11 with Android 4.4 was out so I decided to flash it. However I ran into a problem I've never faced before, the install kept failing in recovery. I did some research and it appears the problem is that I have an outdated version of TWRP that doesn't work with 4.4 for some reason.
Here's the real problem. I don't have any backups or any other zips on my sd card I can install. Only CM 11 and the 4.4 gapps, so I'm stuck in recovery. I've looked into ways of putting files (such as another ROM so I could flash and get out)on your phone when you're stuck in recovery and the only methods I've found involve adb. Adb solutions don't work for me because I don't have the HTC one drivers installed so the device can't be found.
Anything I can do here? I've run out of ideas.
shamrocks010 said:
Earlier today I was running CM 10.2 on Android 4.3.2. I checked the nightlies for the first time in awhile saw CM 11 with Android 4.4 was out so I decided to flash it. However I ran into a problem I've never faced before, the install kept failing in recovery. I did some research and it appears the problem is that I have an outdated version of TWRP that doesn't work with 4.4 for some reason.
Here's the real problem. I don't have any backups or any other zips on my sd card I can install. Only CM 11 and the 4.4 gapps, so I'm stuck in recovery. I've looked into ways of putting files (such as another ROM so I could flash and get out)on your phone when you're stuck in recovery and the only methods I've found involve adb. Adb solutions don't work for me because I don't have the HTC one drivers installed so the device can't be found.
Anything I can do here? I've run out of ideas.
Click to expand...
Click to collapse
You have to install the drivers.
Chilidog said:
You have to install the drivers.
Click to expand...
Click to collapse
How? It's just showing up in device manager as "MTP USB Device." HTC sync isn't detecting it and updating the drivers.
shamrocks010 said:
How? It's just showing up in device manager as "MTP USB Device." HTC sync isn't detecting it and updating the drivers.
Click to expand...
Click to collapse
How did you flash the recovery on your phone? I'm pretty sure they're installed. Did you try ADB Sideload yet?
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Did you follow the instructions to flash TWRP using Odin?
olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear
bump
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?
N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.
N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post
aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.