Hello
So I have a GSM Galaxy Nexus that was running stock 4.3 (maguro)
Having been really frustrated with the low volume on the device, I decided to try the method mentioned on this link - Download Fix for Google Galaxy Nexus I9250 Volume Issue - Android Advices (VolumeFix by MoDaCo)
After I applied the fix and rebooted, my phone got stuck at the Google screen. My phone was unlocked prior to applying this fix so I went ahead and installed the CWM recovery - despite that, I cannot go past the Google screen, I haven't been able to install the CWM-SuperSU on my phone yet because I cannot transfer it to my phone without having it connected as a USB storage device. I tried adb push CWM-SuperSU-v0.87.zip /sdcard/ but it says "device not found"
I have even downloaded the stock 4.2.1 ROM to flash my phone with it, but at this stage I cannot do anything. I have logged into recovery and have wiped cache/ partitions/ dalvik etc but still it doesn't work.
Kindly advise me on how to fix my phone. I bought it a couple of months ago and being in India, Galaxy Nexus has no support here
Many thanks in advance
I believe the galaxy nexus supports fastboot and the stock (if download from Google here
https://developers.google.com/android/nexus/drivers
Or I believe it also supports hiemdal and Odin which you can return to stock this way as well
Also if you have a recovery that supports adb sideload you can flash straight to a custom ROM, probably the best method as we all want something fun right
Happy flashing!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks for your response. I just downloaded the official 4.3 from Google and flashed my phone with it
Related
Hey all, so I have a galaxy s2 (as you may have guessed) and had a friend root it for me a while back with lightning rom ... Not sure if anyone can help me here ...
I am giving the phone to mum, so went and did a factory reset on it, and it apparently ate the OS because it is now just stuck rebooting itself, it wont actually load into the OS at all.
I've gotten it into recovery mode, but nothing i do seems to work, it just says it can't find files, or sits on a screen with a pretty little icon.
Is there any way I can download the OS again, or somehow get it back onto the phone?
Cheers for your help in advance!
- Rhiana
Find a rom that is installed through odin, either a stock ki8 rom or a modded one, there's plenty in the dev sections.
do you have CWM installed if it is then mount usb storage from CWM menu push the ROM in your mobile from your PC. I would recommend this ROM
http://forum.xda-developers.com/showthread.php?t=1290468
then install as the instructions given on the first page
P.S odin works good too, your choice
There is a sticky just at the start page called bootloop. Take advantage of that.
Sent from my GT-I9100 using XDA App
Hello, I'm having trouble resolving issues with my Google Nexus S 4g.
When I first bought it, I was not happy with the features it was offering so I searched and found out about the CM7(Cyanogenmod 7) mod, and decided that I wanted to try out a modded phone. I've been using CM7 for a few years now and have just plain become unhappy with what they're putting out and decided that I finally wanted my phone back to being normal and rooted. I booted into my clockworkmod(after backing up all apps/data with TitaniumBackup pro & taking pics/vids/etc off through USB) and decided to wipe my sdcard and all other options that Clockworkmod offers. After doing that I realized I made a horrible mistake...every time I go to reboot my phone, it ends up back at the boot menu and at the top it says "Fastboot Mode - No boot or recovery IMG" how would I go about resetting my phone back to a normal OS without being able to transfer stuff onto it without it being booted and having a USB option.
I would also take some feedback on which OS is better. ICS, JB, or GB.
Please, and thanks so much,
incog.
re-Root the nexus, using one click root for ease,
Install a ROM through USB
Flash
Unload with titanium backup
Search forums for root nexus s4g
Jrcon said:
re-Root the nexus, using one click root for ease,
Install a ROM through USB
Flash
Unload with titanium backup
Search forums for root nexus s4g
Click to expand...
Click to collapse
I was having trouble getting the drivers for Android 1.0 and searched around and found that PDANet works best for getting Android 1.0 drivers, I then had found a stock Jelly Bean OS and flashed it with fastboot, once I had all of the default img files, I booted up and my system updated to JB 4.1.1 and from there I rooted with a one click rooter and installed SuperSu.
All is fine now, I have my rooted JB 4.1.1.
If anyone is having trouble with reverting from Cyanogenmod, and can't figure it out, drop me a message.
Anyways, thanks for the feedback Jrcon.
So I've usually only dealt with the rooting/romming scene for Motorola, and I need some help.
I bought a Galaxy Tab P7510 WIFI only off Craigslist. It's the Google I/O version. It was sold to me as a Galaxy Tab 2, but now I'm under the impression that the P7510 is a Galaxy Tab 1 (which I have no problem with).
- It came with what I believe was CM10 installed.
- After seeing that the Tab 2 had the JB OTA released I downloaded the applicable firmware (based on P7510) and used Mobil Odin Pro to get back to stock (thinking I would be able to OTA to JB still thinking this was a Tab 2).
- I managed to get that far and get to stock so at this point I looked for the OTA in system updates and finally realized hey this isn't a Tab 2 because ICS says up to date, so now I want to go back to JB, but maybe in the form of SlimBean.
- I downloaded CWM to flash custom recovery, used Odin via PC and flashed. All went well and I got the green "Pass".
- So at this point I know I'm close, I just need to boot into recovery, do my wipes, and flash the SlimBean zip and I'm done. But the problem is the Tab won't boot into recovery. I tried power + volume up, i tried power + volume down, i tried power + both volumes but I get nothing. Is this a common easily dealt with issue? Everything on the Tab is stock, rooted, with CWM supposedly flashed, but I just can't boot into recovery...
I'm surprised I got this far without asking for help, but at this point anything is appreciated. Thanks in advance!
Nola
I'd like to start this thread in establishing that I am not familiar with how all this works, nor do I have any idea how to fix it, which is why I'm here. I only know the system info, such as version, firmware, etc.
In attempting to add cyanogen mod on my already previously rooted Samsung Galaxy Tab 2 7.0 gt-p3113, I watched a video that directed me to install clockwork recovery and root in a single bundle using Odin, (which I successfully did). I then proceeded to install cyanogen mod while in clockwork recovery, which it then told me to factory reset wipe all data before doing so. After going to the "main page" of CWM and resetting the device like it told me, I then went back to install cyanogen mod, only to have it tell me that CWM is out of date. I tried rebooting the device, but it would take me back to CWM, which im assuming means I deleted to OS on accident.
After all that, I finally concluded I'm stuck on an old version of Clockwork Recovery with no OS installed. I can access download mode, however when I'm not in download mode the device automatically boots up to the old version of clockwork mod, and I'm stuck there.
As I have no idea how all this stuff works and did pretty much everything from a YouTube video, I'm hoping a more experienced developer can help fix the problem and somehow help me regain use of my tablet. At this point I don't care whether I can get cyanogen mod installed or not, and I would appreciate all the help I can get.
Thanks
EvilPenguin42 said:
I'd like to start this thread in establishing that I am not familiar with how all this works, nor do I have any idea how to fix it, which is why I'm here. I only know the system info, such as version, firmware, etc.
In attempting to add cyanogen mod on my already previously rooted Samsung Galaxy Tab 2 7.0 gt-p3113, I watched a video that directed me to install clockwork recovery and root in a single bundle using Odin, (which I successfully did). I then proceeded to install cyanogen mod while in clockwork recovery, which it then told me to factory reset wipe all data before doing so. After going to the "main page" of CWM and resetting the device like it told me, I then went back to install cyanogen mod, only to have it tell me that CWM is out of date. I tried rebooting the device, but it would take me back to CWM, which im assuming means I deleted to OS on accident.
After all that, I finally concluded I'm stuck on an old version of Clockwork Recovery with no OS installed. I can access download mode, however when I'm not in download mode the device automatically boots up to the old version of clockwork mod, and I'm stuck there.
As I have no idea how all this stuff works and did pretty much everything from a YouTube video, I'm hoping a more experienced developer can help fix the problem and somehow help me regain use of my tablet. At this point I don't care whether I can get cyanogen mod installed or not, and I would appreciate all the help I can get.
Thanks
Click to expand...
Click to collapse
Well, I would say that may be a bigger problem ! Now what I think better for you would be trying to flash the stock ROM over to the device again I am sure you have your hands over the flashing. So head over to the sammobile/firmware section and try getting the stock ROM downloaded and flash it over your device.
I've been running rooted with Alliance Rom build 32 for about a year with zero problems. The phone battery ran low last night and the phone turned off. When I turn it on it stops at the first logo. I can't get into Philz
recovery. It will go into downloader mode. I tried using Odin to revert to the stock MJ9 I started from when I used Casual. It flashed successfully (stock pit and MJ9) but still gets stuck at the the first logo and won't go into recovery.
SD card is removed. I haven't made any modifications to the phone for the past six months except adding a few well known apps from the store.
Any advice on how to get back to where I can load recovery and proceed to reinstall would be greatly appreciated.
PS.
I would have bought a new phone last year but it seems all the ones I like are bootloader locked. I can live without the stylus (would love a new note though...). Any recommendation on a replacement for the Note 2 would be much appreciated.
dsteinschneider said:
I've been running rooted with Alliance Rom build 32 for about a year with zero problems. The phone battery ran low last night and the phone turned off. When I turn it on it stops at the first logo. I can't get into Philz
recovery. It will go into downloader mode. I tried using Odin to revert to the stock MJ9 I started from when I used Casual. It flashed successfully (stock pit and MJ9) but still gets stuck at the the first logo and won't go into recovery.
SD card is removed. I haven't made any modifications to the phone for the past six months except adding a few well known apps from the store.
Any advice on how to get back to where I can load recovery and proceed to reinstall would be greatly appreciated.
PS.
I would have bought a new phone last year but it seems all the ones I like are bootloader locked. I can live without the stylus (would love a new note though...). Any recommendation on a replacement for the Note 2 would be much appreciated.
Click to expand...
Click to collapse
If you're looking for a newer phone that lets you unlock the bootloader, you might want to check out last year's Nexus 6 or the newer Moto X Pure Edition. The Nexus 6P from Huawei also looks nice and I'm keeping an eye on it as my next potential phone. The Nexus 5x from LG should also have a boo that can be unlocked.
-----------
Hopefully, you didn't flash the stock Verizon MJ9 4.3 firmware back onto your phone. If so, then you have locked your bootloader with no way to unlock it.
I'm thinking that you're probably getting confused with needing to flash Beanstown106’s modified MJ9 firmware (which doesn't return the phone to stock or contain the 4.3 bootloader). See one of my previous posts ( http://forum.xda-developers.com/showthread.php?p=58541771 ), which discusses a similar issue and has a link on how to flash the stock recovery back onto the phone if you'd like to try that rather than restoring the phone back to stock 4.1.2.
You could also just Odin restore the phone back to Verizon factory stock 4.1.2 and run Casual again to start fresh. See Droidstyle's restore guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ) to get instructions on how to flash back to 4.1.2.
Once back on 4.1.2, you need to go into the stock recovery and wipe cache /factory reset to make sure everything is wiped off the device for a fresh start. (Odin doesn't wipe everything in it's flashing process).
If you restore back to stock 4.1.2, then be careful not to let your phone take an OTA because if it gets updated to 4.3+, then you won't be able to unlock the bootloader any longer.
I usually remove my Sim card when restoring to stock 4.1.2... just to ensure I don't accidentally take an OTA update before I get it rooted again. (You can skip the initial phone Setup screen with the method in this YouTube video - https://youtu.be/qekEpn1Bufc ). It says it's for the S3 but works on the Note II as well. Once you get back into the phone and enable USB debugging in Developer options, you should be able to run Casual again. The phone doesn't have to be activated or on wifi to do this.
Once Casual is successful, it's safe to put the Sim card back in because I don't believe an OTA can install successfully with a custom recovery installed.
Good luck.
mattnmag said:
I
Hopefully, you didn't flash the stock Verizon MJ9 4.3 firmware back onto your phone. If so, then you have locked your bootloader with no way to unlock it.
Click to expand...
Click to collapse
All the ROM's and tools are from threads here so pretty sure I'm using Bean's modified MJ9. I was on Beans 4.3 for over a year before I went to the Alliance ROM.
You could also just Odin restore the phone back to Verizon factory stock 4.1.2 and run Casual again to start fresh. See Droidstyle's restore guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ) to get instructions on how to flash back to 4.1.2.
Once back on 4.1.2, you need to go into the stock recovery and wipe cache /factory reset to make sure everything is wiped off the device for a fresh start. (Odin doesn't wipe everything in it's flashing process).
If you restore back to stock 4.1.2, then be careful not to let your phone take an OTA because if it gets updated to 4.3+, then you won't be able to unlock the bootloader any longer.
Click to expand...
Click to collapse
4.1.2 sounds like a better idea - I have that also.
Thanks your advice here is just what I was looking for in my effort to get this phone running again.
Update: I can still go into Download mode but cannot get a computer to recognize the phone now.
Not one of three computers, numerous cables including one out of the Galaxy Note 2 box and all the tricks I could find like pulling the battery while connected helped.
The first day of this problem (stuck at first logo) I was able to connect to the phone with Odin. I flashed the following:
1. sch-i605-16gb.pit
2. CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar
Would something like http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 help?
Should I look into the JTag guys on ebay?
Thanks,
dsteinschneider said:
Update: I can still go into Download mode but cannot get a computer to recognize the phone now.
Not one of three computers, numerous cables including one out of the Galaxy Note 2 box and all the tricks I could find like pulling the battery while connected helped.
The first day of this problem (stuck at first logo) I was able to connect to the phone with Odin. I flashed the following:
1. sch-i605-16gb.pit
2. CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar
Would something like http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 help?
Should I look into the JTag guys on ebay?
Thanks,
Click to expand...
Click to collapse
I don't know if a USB jig would help the computer recognize the phone again.
Since you tried 3 different computers and still couldn't get it recognized... I'm wondering if something got fubared when you Odin flashed the VRLJB stock Rom. So when you go to Device Manager in the computer, the computer doesn't even show anything connected at all?
I don't know that it would be worth the time, but (on the computer that last worked for your phone), you could try uninstalling the Samsung Drivers, and then use a program like DevManView to totally uninstall all Android related drivers. Restart the computer afterwards and then reinstall the Samsung USB Drivers (from here: http://www.samsung.com/us/support/owners/product/SCH-I605) . Then connect your phone back to the computer in Download Mode to see if it will reinstall the drivers and recognize it.
If the computer still doesn't recognize the phone after all that, then I'm out of ideas.
I'll try the devmanview driver cleanup (love nirsoft utils!) and install the driver in your link on the orginal pc which I use for flashing ROMs. If that doesn't work I'm going to look into sending it out to a JTag guy although they claim if you can get into download mode after they perform their magic that they were successful.
Went with the LG G4 which I'm very happy with. As far as getting the Note 2 running again I've been thinking l might buy a used Verizon Galaxy Note 2 motherboard on ebay rather than sinking a lot of time into trying to... should I say "unbrick" it.
If you ran casual first, it will not connect to the samsung driver, until you uninstall the USB services from the device manager, and then run find new hardware.
But maybe this will not help considering you already tried 3 machines?
I may have had the Samsung driver on all 3 machines. Good suggestion - I'll post back if it works.
Related question. I see you are running CM 12.1 - do you have standby battery drain issues? My 4.4.2 Alliance 32 would drain the battery down to 0 if I didn't plug it in at night even though I might still have 1/3 charge.
dsteinschneider said:
I may have had the Samsung driver on all 3 machines. Good suggestion - I'll post back if it works.
Related question. I see you are running CM 12.1 - do you have standby battery drain issues? My 4.4.2 Alliance 32 would drain the battery down to 0 if I didn't plug it in at night even though I might still have 1/3 charge.
Click to expand...
Click to collapse
Right, it was in the Adam Antler video, for casual. Once you use the casual on USB, the samsung driver will not work until you uninstall and reinstall USB system.
I can get almost 3 days out of a phone battery with little or no use. The one I am using could make it a day and 1/2, but I charge that one every night because I do not need and down time just in case.
I am using the nightly build, 12.1-20151222 12/22/15, I am not sure how the other builds are, or even the stable build for that matter?