Ok so I got the GSM version today, I was using this http://www.youtube.com/watch?v=oSmd9ZbUH50&feature=player_embedded to help me unlock the bootloader, flash CWM, and flash the SU files. I unlocked the bootloader without a problem, just It did not delete all my data like the video said.
Once I try flashing CWM and looks like its fine, but after reboot when trying to boot into recovery, I get the Red Triangle with exclamation mark. I have tried flashing it a couple times, it still does the same thing. Can anyone help me please?
I just got mine today also, did you rename the stock recovery image before flashing cwm? I renamed it after and had the same issue so I reflashed cwm and all is good.
Sent from my SGH-T959V using xda premium
try using this tool http://forum.xda-developers.com/showthread.php?t=1400871
1) Play Store devices do NOT wipe when unlocking the bootloader. (We are still trying to figure out why.)
2) The Android with the red "!" IS the stock recovery. There are two files in you /system that reflash the stock recovery on every boot. If you want you custom recovery to stick, you need to delete/rename one or both:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Galaxy Nexus using Tapatalk 2
I didn't rename anything, just exactly how the guy in youtube has it. :crying: Do you have to flash a custom recovery after every reboot? even with the toolkit after i reboot, i get the red triangle.
manuelsavino said:
I didn't rename anything, just exactly how the guy in youtube has it. :crying: Do you have to flash a custom recovery after every reboot? even with the toolkit after i reboot, i get the red triangle.
Click to expand...
Click to collapse
Did you not read what I wrote? You NEED to rename one of those files for CWM to stay installed.
Sent from my Galaxy Nexus using Tapatalk 2
So pretty much without rebooting, I flash custom recovery, root, then rename those two files. correct?
manuelsavino said:
So pretty much without rebooting, I flash custom recovery, root, then rename those two files. correct?
Click to expand...
Click to collapse
Yup. Or if you reboot before renaming the files, just reflash cwm again once you delete then. No big deal.
Sent from my Galaxy Nexus using Tapatalk 2
Ok. Thank you all! I will report back once I do it!
manuelsavino said:
Ok. Thank you all! I will report back once I do it!
Click to expand...
Click to collapse
This would have taken less than 5 minutes with the V7 Toolkit- boot loader unlock, root, rename recovery file, and install CWM/TWRP.
It is good that your trying other methods, though.
Sent from my Galaxy Nexus
bhowanidin said:
This would have taken less than 5 minutes with the V7 Toolkit
Click to expand...
Click to collapse
If he did it using a toolkit as you suggested, we would have learned nothing.
Sent from my Galaxy Nexus using Tapatalk 2
Mate I had the same problem. I got my device yesterday and unlocked my device with the tool Galaxy Nexus Root Toolkit v1.4. But it didn't allow me to root it. As I had ADB installed I tried to flash recovery trough it. But still no success. Here's how I did it.
Download Galaxy Nexus Root Toolkit v1.4. Enter the advanced settings.
Transfer su.zip to your internal memory and then "Boot into Temp CWM" trough that tool. Then you can root your device. Once it's rooted, download "ROM Manager" from the market. Accept the permissions it's asking for. And flash CWM recovery from it.
And voila. It worked for me.
Why did you use version 1.4 when you could use V7 which does all that for you in one click.
Ran into this version in a video I watched. So I just downloaded it.
Oh right you should check the development section for the newer version it is far more simple & self explanatory.
I'm done with rooting and unlocking. I did it already. Just explained how above.
No need for a tool no more.
Its useful if you want to relock your phone and go back to stock
replied..
ste1164 said:
Why did you use version 1.4 when you could use V7 which does all that for you in one click.
Click to expand...
Click to collapse
I'm guessing it just worked for him..:good:
If it anit broke why try to fix it
Ended up using the toolkit. One question, the two files that need to be renamed/deleted so it wont go back to stock recovery, on the toolkit it says rename, though once i go on root explorer to see if the two files are still there, they disappeared. So if I ever wanted to go back to stock recovery for any reason, are those two files available anywhere? Or is there a stock recovery image?
Related
I was on the latest codename and everything was working fine, but wanted to see how 4.0.4 was running as is. I downloaded the stock AOSP build that was flashable by nikademus, downloaded gapps/root files as well. Followed instructions so far so good. Booted up and noticed that the ICS animation was gone and was replaced by just the "android" with the lighting going through it animation. Didn't really care about that so i let the phone do its thing, once it was done and i completed the account setup i rebooted like i normally do when flashing roms. when the phone came back I went into the settings to verify i was on the current version. I noticed that it said 4.0.4 0 4.0.4, thought that was odd and then something else that was odd was that my market was completely blacked out and the only way to see anything was the select something and then it would become visable. By then I knew something was wrong so i tried to boot into recovery via rom manager but it would not do anything. I tried to flash a custom recovery image again and it didnt let me because of su commands ? or something like that. At this point im freaking out because I have no SU permissions apparently, no CWM recovery, and the rom that im using is clearly messed up(not saying its the rom, it was probably something i did wrong) so i tried to use the galaxy nexus root toolkit program by WugFresh. I was going to try to go back to stock+unroot and then root after. I downloaded 4.0.2 and followed the command prompts and everything seemed to be working fine but when the phone was supposedly booting up it just got stuck on the Google screen with the unlocked padlock for a long time. I didnt see no boot animation or anything for about 10 min.
So I have no clue how to recover from this =(
Is my phone a paper weight now ? or can it be fixed ?
someone help me please lol
Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806
Enhanced said:
Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
but i cant even get adb to see my device?
in order for me to use fastboot dont i need adb setup ?
I had adb setup but after this issue i cant go no further then the google screen
Enhanced said:
Flash the stock images from Google with fastboot.
http://forum.xda-developers.com/showthread.php?t=1366806
Click to expand...
Click to collapse
^^^ what he said.
I have yet to see a bricked Galaxy Nexus.
Sent from the future.
okay so I was able to flash the google images using fastboot (thank god) =)
but by me doing this did i loose root permissions ?
AnthonyAldrete said:
okay so I was able to flash the google images using fastboot (thank god) =)
but by me doing this did i loose root permissions ?
Click to expand...
Click to collapse
Yes you're completely stock.
No more wugs for you sir.
You need to learn how to do this manually.
Check my sig.
All you need to do is unroot the nexus back to stock, gnex toolbox. Then reroot
Sent from my Galaxy Nexus using XDA
halifaxjesse said:
All you need to do is unroot the nexus back to stock, gnex toolbox. Then reroot
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
10 chars.
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
marcusabu said:
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
Click to expand...
Click to collapse
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
jv2543 said:
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
Click to expand...
Click to collapse
Where can I find this option and what does it do exactly? I have the Nexus Toolkit too, should I do anything there?
1.Don't panic
2. Try to go on bootloader then reset factory or fastboot then from pc flash recovery
3. Try to get back recovery then factory reset and flash backup
Sent from my HTC One V using Tapatalk 2
OP, here. Learn before you do some damage with tools you don't understand.
I mean, it's the easiest thing to fix damnit if you cared to learn in the first place...
Beamed from Maguro
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I wouldn't recommend Odin to beginners. OP is better off with the fastboot guide mentioned by bk201doesntexist.
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
was it a nexus? maybe/probably not, but if it was, you should have used fastboot. it's officially supported by GOOGLE. if you want to flash a factory image, they tell you to use fastboot. why would we use anything else? a leak? that the community barely really knows anything about?
i'd rather use Heimdall!! (not sure i9250 is supported though.)
Sent from my i9250
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
mr1080p said:
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
SysAdmNj said:
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
Click to expand...
Click to collapse
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
U have to make sure u are rooted first.
Sent from the TermiNOTEr!
mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
SysAdmNj said:
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
Click to expand...
Click to collapse
Yes. CWM and ported ROM. Everything works well I just want TWRP. But I guess I'll do with CWM. If it aint broke then why fix it. It works I guess. Thanks.
Sent from my SAMSUNG-SGH-I317 using xda premium
Check your build prop for device name. Maybe its not correct because of the Rom you're on. Whats the error you're getting?
Did you ever get TWRP on your phone?
I've had goofy issues with TWRP but much prefer it to CWM. Originally rooted using CWM and SuperSu and switched to TWRP when I flashed CleanRom several times via Romtoolbox pro I've flashed updated Twrp it said it was successful but when it rebooted was soft bricked! Had to use Odin and original CWM to get back in and re-install everything (nandroids were twrp backups) found file downloaded to sdcard that worked fine! Odd...
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
wargear said:
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
Click to expand...
Click to collapse
If by "installed" you are referring to the recovery program itself (and not your backups), you can only have one recovery 'installed' at one time as there is only 1 "Recovery" partition on the device (/dev/block/mmcblk0p9). So if you want to install CWM instead of your current TWRP (or visa-versa), either flash the appropriate new recovery zip via your current recovery... or Odin3 flash your desired new recovery tar. Either way, it will write to the same recovery partition. If you are referring to your backups... these are stored in the designated path you selected (either internal sd or external sd)... in the TWRP/BACKUPS folder. In that folder, you will have a device id #... in that folder are your backups.
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
wargear said:
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
Click to expand...
Click to collapse
Which version of Odin3 are you using? When I used Odin3 v1.85 I would get the "PASSED" but with Odin3 v3.07, I also only got "RESET" (on an WindowsXP box)... but both flashed it correctly (and auto rebooted after flash)
Galaxy Note2 TOOLKIT V3.0.0 ATT]
I tried the [Galaxy Note2 TOOLKIT V3.0.0 ATT] http://forum.xda-developers.com/showthread.php?t=2052779 out of curiosity sake. Worked for me installing TWRP 2.3.2.3 without a hitch. Great tool from what I can see, and that's just one of it's many features. Great for simplifying things for new Android users just entering the customizing scene and regulars alike. Big ups to mskip for making this available. I can foresee myself grabbing the donate version here real soon.
And to get yourself SIM unlocked, get yourself back to 4.1.1 and give this a whirl.http://forum.xda-developers.com/showthread.php?t=2014982 Bought my device used, was supposedly unlocked, wasn't. Even came with an unlock code that the previous owner purchased. Firstly it's a no go on 4.1.2, secondly still didn't work when I dropped back to 4.1.1. But this http://forum.xda-developers.com/showthread.php?t=2014982 will set you free. Big thanks owl74 for posting. Once again XDA forums saves my hair from being pulled out.
Well, I used a factory reset tool to reset my rom back to stock. However, when I try to do a system update, it goes all the way to the end and says Error. Note that I can get into my tablet before I launch the update, but afterwards it just boots into recovery and I have to hard reset and reset my device using the aforementioned factory reset tool. Basically all I want to know is if it has anything to do with me recovering from the tool, or are OTA's iffy? I bought the device yesterday and I love it. I rooted it, unlocked the bootloader, etc. So yes it is modified. However It is not in anyway bricked. I just want to know if it's possible to do an official OTA from System Update, or do I have to use the one provided on the Index of the Nexus 7 Flo forum? Thanks for any help. Like I said, It's not bricked, I'm not complaining. Just a few questions
SwiftLeeO said:
Well, I used a factory reset tool to reset my rom back to stock. However, when I try to do a system update, it goes all the way to the end and says Error. Note that I can get into my tablet before I launch the update, but afterwards it just boots into recovery and I have to hard reset and reset my device using the aforementioned factory reset tool. Basically all I want to know is if it has anything to do with me recovering from the tool, or are OTA's iffy? I bought the device yesterday and I love it. I rooted it, unlocked the bootloader, etc. So yes it is modified. However It is not in anyway bricked. I just want to know if it's possible to do an official OTA from System Update, or do I have to use the one provided on the Index of the Nexus 7 Flo forum? Thanks for any help. Like I said, It's not bricked, I'm not complaining. Just a few questions
Click to expand...
Click to collapse
Well, without much detail about the error, it's hard to help. Are you just stock rooted with stock recovery? If so, you should be able to take an OTA no problem, although you'd lose root. But you can always flash supersu to get it back. Did you install a custom recovery to root? Or did you use a toolkit? Lots of questions. If you have a custom recovery, you'd have to fastboot flash the stock recovery from the factory image. If you still have the stock recovery and are just stock rooted, you've probably modified the system in some way. In that case, you can just fastboot flash the stock system image.
charesa39 said:
Well, without much detail about the error, it's hard to help. Are you just stock rooted with stock recovery? If so, you should be able to take an OTA no problem, although you'd lose root. But you can always flash supersu to get it back. Did you install a custom recovery to root? Or did you use a toolkit? Lots of questions. If you have a custom recovery, you'd have to fastboot flash the stock recovery from the factory image. If you still have the stock recovery and are just stock rooted, you've probably modified the system in some way. In that case, you can just fastboot flash the stock system image.
Click to expand...
Click to collapse
Stock Rooted with Stock Recovery. It downloads the OTA no issue, but when in download mode, it gets to the very end and says Error!. I used CFAutoRoot for rooting. I used fastboot to unlock the bootloader and install custom recovery.
SwiftLeeO said:
Stock Rooted with Stock Recovery. It downloads the OTA no issue, but when in download mode, it gets to the very end and says Error!. I used CFAutoRoot for rooting. I used fastboot to unlock the bootloader and install custom recovery.
Click to expand...
Click to collapse
Wait. So do you currently have stock recovery or a custom recovery?
Sent from my Nexus 5 using xda app-developers app
charesa39 said:
Wait. So do you currently have stock recovery or a custom recovery?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Exactly what I was wondering!
charesa39 said:
Wait. So do you currently have stock recovery or a custom recovery?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Stock.
SwiftLeeO said:
Stock.
Click to expand...
Click to collapse
Since you have stock recovery, there's probably an app that modified your system that's not allowing it to install the update because it detects a change in one of your system files. Fastboot flash the system image from the stock factory image. Then, it should update.
Sent from my Nexus 7 using xda app-developers app
charesa39 said:
Since you have stock recovery, there's probably an app that modified your system that's not allowing it to install the update because it detects a change in one of your system files. Fastboot flash the system image from the stock factory image. Then, it should update.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You wouldn't happen to have one of those lying around would you? The img file I mean.
SwiftLeeO said:
You wouldn't happen to have one of those lying around would you? The img file I mean.
Click to expand...
Click to collapse
I'm assuming you're on 4.3 since you're trying to update? Either way, you can find the factory images here: https://developers.google.com/android/nexus/images.
Just download the the one for the version you're currently running on your N7. MAKE SURE YOU DOWNLOAD THE CORRECT ONE. Then, just extract the files from the tar.gz file. There's another zip file in that tar.gz file. Extract that one, and there's a system.img file. Fastboot flash it in the bootloader.
Sent from my Nexus 7 using xda app-developers app
charesa39 said:
I'm assuming you're on 4.3 since you're trying to update? Either way, you can find the factory images here: https://developers.google.com/android/nexus/images.
Just download the the one for the version you're currently running on your N7. MAKE SURE YOU DOWNLOAD THE CORRECT ONE. Then, just extract the files from the tar.gz file. There's another zip file in that tar.gz file. Extract that one, and there's a system.img file. Fastboot flash it in the bootloader.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help
SwiftLeeO said:
Thanks for the help
Click to expand...
Click to collapse
Anytime. :thumbup:
Sent from my Nexus 7 using xda app-developers app
Hello everyone, I've had and rooted a plethora of Android devices but none have given me as much trouble as the S3, I have tried every sprint method that there is all to no avail. I tried CF-Auto-Root, nothing, tried downloading SuperSU after using that, says no SU binary. I tried every option in the Android toolkit, and nada. I looked all over for a Rooted Restore cause thats what always saved me forever ago on the S2 but there's none for that. I'm running out of options, I'm on 4.3 MK3 and I could deff use some help please!
NOTE: On the Android toolkit, the process doesn't work because when it flashes TWRP and it boots to recovery the toolkit says "Recovery mode not detected", and when I check device manager it shows SPH-L710 with a yellow ! mark, I've already installed the Samsung USB drivers, I tried Kies, and even the PDANet drivers, none work for the device when its in recovery mode.
Flash the latest philz recovery via Desktop Odin, it will ask you if you want to root the phone when you reboot it, tell it yes, then update superuser through the play store
Sent from my SPH-L710 using Tapatalk 2
mattzeller said:
Flash the latest philz recovery via Desktop Odin, it will ask you if you want to root the phone when you reboot it, tell it yes, then update superuser through the play store
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Oh my god thank you so much, it worked like a gem! That should be the main root method, not CF-Auto-Root, that was a breeze AND gives you custom recovery!
If you could answer one more question for me that'd be great, I hate sounding so picky, and it's honestly no problem if there's no fix, I just have major OCD, when I boot to recovery and it shows the Cyanogenmod guy, is there anyway I can change/remove that? It bugs me cause I don't have CM or CWM so it seems very out of place.
Giston141 said:
when I boot to recovery and it shows the Cyanogenmod guy, is there anyway I can change/remove that? It bugs me cause I don't have CM or CWM so it seems very out of place.
Click to expand...
Click to collapse
I don't think you can change it, unless you were compiling a version of it yourself, but you would need to ask the dev for philz about how to go about that.
Sent from my SPH-L710 using Tapatalk 2
mattzeller said:
I don't think you can change it, unless you were compiling a version of it yourself, but you would need to ask the dev for philz about how to go about that.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
It's not a Philz thing tho, no matter what custom recovery you have, CWM, Philz, TWRP, it's always got the CM guy, Cid I think his name is? If you could change the boot screen you should be able to change that right?
Giston141 said:
It's not a Philz thing tho, no matter what custom recovery you have, CWM, Philz, TWRP, it's always got the CM guy, Cid I think his name is? If you could change the boot screen you should be able to change that right?
Click to expand...
Click to collapse
No clue, I only see it when I boot into recovery, so I rarely see it
Sent from my SPH-L710 using Tapatalk 2