So i got my hands on a Galaxy Nexus and naturally went for a root. Should be an easy task, i thought, considering those one-click tools posted on forums. So i went on and unlocked the bootloader. No problems there.
Next step booting/flashing CWM. This is where things gotten strange. For the notice, i've tried doing this manually, through adb/fastboot, as well as using GNEX Toolkit and GNEX Root Toolkit by WugFresh, several times.
So the flashing (of CWM) process itself went well in all of the cases. The problem is that when i try entering recovery the phone seems to reboot itself (i get a typical PC sound notification that the device is unplugged) and i'm getting stuck on the Google screen with unlocked pad on. Simple battery remove solves the freeze, and the phone boots normally and is fully functional. Trying to re-enter recovery after reboot results in same freeze screen. Surprisingly, the stock recovery works after a re-flash.
I'm using Universal drivers, adb and fastboot shows the device correctly. Any ideas?
BTW, i'm on IMM76D, baseband version I9023XXKI1. Would really appreciate any ideas.
nzmvs said:
BTW, i'm on IMM76D, baseband version I9023XXKI1. Would really appreciate any ideas.
Click to expand...
Click to collapse
That is not a GNex radio...
As for you issue, I would reflash everything manually. You don't know how and what the toolkits do, so how can you figure out what went wrong?
"stock recovery works after reflash"
what reflash?
learn how to do the whole process manually. you're not even flashing a i9250 radio..
Sent from my Transformer Prime TF201
nzmvs said:
BTW, i'm on IMM76D, baseband version I9023XXKI1. Would really appreciate any ideas.
Click to expand...
Click to collapse
efrant said:
That is not a GNex radio...
As for you issue, I would reflash everything manually. You don't know how and what the toolkits do, so how can you figure out what went wrong?
Click to expand...
Click to collapse
thats right, thats a slcd version nexus s,
are you sure that you bought a galaxy nexus? flashing the galaxy nexus cwm recovery onto the nexus s would cause that issue http://www.gsmarena.com/samsung_google_nexus_s_i9023-3910.php
Omg, epic fail. efrants post made me thinking and i turned out that i mixed up nexus with nexus s :O i guess i was too eager to play with my new toy Anyway, i've successfully rooted and CWM'd the phone, so i'm happy thanks guys for replies, efrant i owe you a beer
Make sure you flash the right files (Verizon/Sprint or GSM), if that doesn't work, re-flash the bootloader, then try again.
Related
Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Another Update:
I just re-flashed with odin, this time it says it successfully completed but once again it's stuck at the flashing Samsung logo with the indicator led on.... I am starting to really freak out lol. I have another file downloading that is supposedly just stock, no root or anything...
rakhov said:
Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Click to expand...
Click to collapse
Actually have the exact same situation going on right now, I will post if I can find a fix. Downloading an alternate stock build I found now and will let you know how it goes.
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
rakhov said:
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
Click to expand...
Click to collapse
Thats exactly what Odin is working on loading now, Download had just finished.
avarize said:
Thats exactly what Odin is working on loading now, Download had just finished.
Click to expand...
Click to collapse
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
rakhov said:
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
Click to expand...
Click to collapse
I've always noticed the LED being on during boot (or some of the boot) and it was also on when I had a bootloop during cm9 so I don't think it means anything.
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
rakhov said:
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
Click to expand...
Click to collapse
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
Click to expand...
Click to collapse
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 for reboot options to force it into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 to force into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
Click to expand...
Click to collapse
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
rakhov said:
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
Click to expand...
Click to collapse
Should have explained a bit better. Yes that toolkit
While it was stuck at samsung screen.
1 For AT&T (Obviously)
20 For reboot options
1 For recovery.
Then wipe data/cache
Then wiped cache (no idea why)
then rebooted.
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
That is exelent. I am downloading the toolkit right now and will report back shortly.
Once you got it to boot, did you still have root? I am wondering if you flashing the "stock rom" that I posted, if that had any impact. I have only pushed the root66 file, so I am expecting root when(if XD) I get this thing going again. I appreciate you being more thorough with your instructions, and will report back with my results as soon as I get some
Also, are we loners on this? I am not seeing any other posts about going back to stock/stock rooted from modded roms using odin? I am trying to figure out the best method to go back to stock. I made a nandroid and I am sure that would work, but all of this word about having to flash different kernels and bluetooth/wifi drivers to get stock working properly makes me wonder if just using odin is the easiest method, as it restores everything on the phone (to my knowledge).
crash822 said:
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
That is great, this may sound a little silly, but how do I boot to recovery? Thanks!
UPDATE:Nvm, google hehe. I just did the factory reset...Things are looking good so far, the haptic lights turned on at least...BOOM! We are good gentlemen. It looks like all it took was the recovery wipe. This is great news! I will try to figure out how to mark this as solved, and you crash822, you get a thanks
NP sir. We all have to start somewhere. Luckily for me I was already planning on doing a full wipe so I backed up everything I wanted to keep from my phone onto my computer before using odin.
I seem to be having the same issue. I've downloaded the toolkit as you guys have suggested. are you guys in download mode on the phone while you use this? it seems to want me to be in debugging mode and i can't get to that. I've tried a factory reset with no luck.
[TOOL] Revert To Stock ICS for the VZW Galaxy Nexus
OVERVIEW
I have created an all-in-one script that will revert your Verizon Galaxy Nexus to stock ICS (Build IMM76K). I have found some of the 'toolkits' to be awesome resources, but a bit flaky when trying to return to stock. This tool is a self-contained EXE and can be run offline as it does not need the internet during the process to download any supplemental files.
!WARNING!
This process WILL WIPE ALL DATA on your phone! You must manually backup all user data, documents and media before performing this process. I take no responsibility for any loss of data to your phone. This script is clean and has been tested, but as with all online guides, this is done at your own risk. Make sure your phone has at least 75% battery before continuing.
WHAT THIS WILL DO
Reset radio, bootloader, and software to factory versions. Unroot your phone. Remove all settings and accounts. Delete all data/apps and replace system apps with old original ones.
WHAT THIS WILL NOT DO
Relock your bootloader or make you coffee.
INSTRUCTIONS
STEP 1: Make sure your phone is UNPLUGGED from your computer, then download and install the Samsung Galaxy Nexus drivers (VZW)
STEP 2: Download/extract my Revert To Stock Tool for the VZW Galaxy Nexus
STEP 3: Power off your phone, then boot into 'Fastboot mode' by holding down both volume buttons and then the power button until you see the screen with the green "Start" arrow (shown below).
NOTE: If your phone boots up normally into your Android OS, then you did not press the buttons correctly. Power off your phone again, and repeat the process until you see the correct screen.
STEP 4: Plug your phone into your computer and let Windows install any necessary device drivers that it detects.
STEP 5: Once it is finished, run the tool (filename: VZW-GNex-RevertToStock.exe), and follow the on-screen prompts to revert your phone to stock ICS (Build IMM76K)
CONCLUSION
Let me know if you have any questions or run into any hiccups along the way. I am always willing to modify the script or the guide to make it more user-friendly.
NOTE: If you receive any virus alert notifications when extracting or running my tool, then know that they are false positives. My executable is clean.
Thread Updates:
2012-02-23:
Added verbiage describing what this script will/will not do.
crobs808 said:
**reserved for thread updates**
Click to expand...
Click to collapse
Hi. I hope this doesn't sound too noobish. I just rooted for the first time the other day using the GNex Tookit Ver. 7.8. to the AOKP JB Rom. I have a Verizon Galaxy Nexus.
Basically I need to go back to stock. It was a CLNR phone and thought it was running great for a day until I started noticing a bunch of dead pixels. So I need it back to Stock.
Is it really as simple as running your tool? Also, will it revert back to the original googe apps? b/c im having some issues with apps now on this rom?
1 last question, I understand it'll go back to stock does that mean I lose root and the bootloader becomes unlocked?
Thanks well in advance!
CorkyRogers said:
Hi. I hope this doesn't sound too noobish. I just rooted for the first time the other day using the GNex Tookit Ver. 7.8. to the AOKP JB Rom. I have a Verizon Galaxy Nexus.
Basically I need to go back to stock. It was a CLNR phone and thought it was running great for a day until I started noticing a bunch of dead pixels. So I need it back to Stock.
Is it really as simple as running your tool? Also, will it revert back to the original googe apps? b/c im having some issues with apps now on this rom?
1 last question, I understand it'll go back to stock does that mean I lose root and the bootloader becomes unlocked?
Thanks well in advance!
Click to expand...
Click to collapse
Yes, this will take you back to the original ROM which includes the original Google Apps (Gapps). Yes, you will LOSE root, but this will NOT re-lock your bootloader. Very good questions - I have updated some of the verbiage in the original post to clarify these points.
crobs808 said:
Yes, this will take you back to the original ROM which includes the original Google Apps (Gapps). Yes, you will LOSE root, but this will NOT re-lock your bootloader. Very good questions - I have updated some of the verbiage in the original post to clarify these points.
Click to expand...
Click to collapse
Ok cool. If I wanted to lock the bootloader, could I use the toolkit after I've used ur script?
CorkyRogers said:
Ok cool. If I wanted to lock the bootloader, could I use the toolkit after I've used ur script?
Click to expand...
Click to collapse
If you wanted to lock the bootloader, just boot into the bootloader and run fastboot oem lock. Don't rely on toolkits.
Edit: HA! I just realized what thread I'm in.
Cilraaz said:
Edit: HA! I just realized what thread I'm in.
Click to expand...
Click to collapse
oops?
Zepius said:
oops?
Click to expand...
Click to collapse
Hopefully this is the last question. When I unlocked/rooted I was on build IMM76Q. Would that affect returning to stock?
Zepius said:
oops?
Click to expand...
Click to collapse
No oops, but it is like walking into an Obama rally and shouting how great Romney is (or vice versa).
Cilraaz said:
No oops, but it is like walking into an Obama rally and shouting how great Romney is (or vice versa).
Click to expand...
Click to collapse
Good thing this isn't a ToolKIT then, just a tool
Not sure why someone arbitrarily rated this thread with "1" star. Kinda uncool, since this will help people.
not working
It keeps saying echo off, plug in your device. I installed the drivers and still nothing,.
harshybar said:
It keeps saying echo off, plug in your device. I installed the drivers and still nothing,.
Click to expand...
Click to collapse
Try a different port, or a different computer. Or spin up a VM if you've got one.
Not restarting
Hi! I found this thread linked in the GNex Toolkit 7.8 thread when I was looking for a solution because it failed to flash the stock image & unroot. I followed all the instructions, and pressed enter after fastboot restarted twice, and got to where it says "Flashing stock rom/system". I have now waited 20mins (the tool estimates 5mins), and my phone isn't restarting out of fastboot mode. It has a blue highlighted line on the bottom that says "Fastboot Status - Okay1515.FA02".
Should I keep waiting? re-run the tool? just try restarting my phone manually?
Please help!
Thanks!
Oh! Was running LiquidSmooth 1.5MR1 prior to starting this...no idea if that would still be working or not if I restart now...
EDIT: I got brave - restarting from fastboot manually just restarted Liquid, so it didn't rewrite the system. Some more searching, and I found a different dl link to try for the system image, put it in the right folder, and the GNex Toolkit worked like it was supposed to. I have to say, though, this tool is much less intimidating haha! Thanks!
So, I am in quite the predicament:
First of all, my phone stopped fully booting into the OS. I can get into fastboot and recovery but when I reboot the system it gets to the android screen and then goes black. Second of all, my usb port is broken.
I am pretty sure that there is nothing to be done, but if anyone has any suggestions that would be AMAZING!
mwreeves said:
So, I am in quite the predicament:
First of all, my phone stopped fully booting into the OS. I can get into fastboot and recovery but when I reboot the system it gets to the android screen and then goes black. Second of all, my usb port is broken.
I am pretty sure that there is nothing to be done, but if anyone has any suggestions that would be AMAZING!
Click to expand...
Click to collapse
Try a different USB cable and a different USB port. It takes a lot to break those ports on your phone, you may just have a bad cable.
crobs808 said:
Try a different USB cable and a different USB port. It takes a lot to break those ports on your phone, you may just have a bad cable.
Click to expand...
Click to collapse
I thought that too. I tried 3 computers and 6 cables: nothing worked. It hasn't been able to connect to a computer for a month now and it stopped charging 2 weeks ago. I have looked at replacing the port with a new mic/usb module but the phone still won't boot so it wouldn't really be worth it.
i just did this and it saved my phone!!!! thank you so much
DadamsJR said:
i just did this and it saved my phone!!!! thank you so much
Click to expand...
Click to collapse
You're welcome
crobs808 said:
You're welcome
Click to expand...
Click to collapse
I wish it were easier to find this thread!
You saved my phone after I stupidly pulled the battery during the root process from the toolkit and got stuck in a reboot loop with the Google logo showing and the little unlock icon.
charlie.sears said:
I wish it were easier to find this thread!
You saved my phone after I stupidly pulled the battery during the root process from the toolkit and got stuck in a reboot loop with the Google logo showing and the little unlock icon.
Click to expand...
Click to collapse
Asks mods to sticky it
I've had this phone for about a week now.
First few days, phone was great! Very quick and awesome. 4G was all over my work area.
Then I used ToolKit program to unlock/root my device.
Since then, no more 4G at work. And It goes IN and OUT of the places where I used to have 15+ MB downloads.
I even used ODIN to Unroot everything. Still didn't help.
Anyone else experience anything similar?
This is exactly what is happening to me, I even ODIN'ed back to stock and got 4G working again... Idk what's wrong with my phone. I updated prl, profile and everything and have never got a good 4G signal since I rooted and been on customs roms.
melo1819 said:
This is exactly what is happening to me, I even ODIN'ed back to stock and got 4G working again... Idk what's wrong with my phone. I updated prl, profile and everything and have never got a good 4G signal since I rooted and been on customs roms.
Click to expand...
Click to collapse
Yeah man. It's sh*tty,
I wish it was mentioned before I did it.
I miss having 4G when I finally got it.
Rooting will do NOTHING to mess with your phones signal/4G! If you updated or switched radios that could cause a problem, but rooting WILL NOT.
I know it has nothing to do with signal but still, the only difference between now and before is that I'm on a custom rom and rooted, I use to get 4g in most of the areas I visit and now I never get it. :/
Sent from my Galaxy Nexus using Tapatalk 2
z06mike said:
Rooting will do NOTHING to mess with your phones signal/4G! If you updated or switched radios that could cause a problem, but rooting WILL NOT.
Click to expand...
Click to collapse
actually what he said is right...ROOTING WILL NOT MESS WITH YOUR RADIO SIGNALS
double check if you had flashed the wrong radio (flash the right one if this is the case) ...or the current ROM you have in has issues (check their thread if anyone else having it)...if all all else fails revert to stock
i'm starting to see why people warn against tool kits. you probably inadvertently flashed an incompatible radio somewhere down the line.
download the fd02 cwm zip here and flash in recovery. it will probably fix your issue. if not, try using fastboot to flash the radio .img's
also, learn fastboot. it's easy, awesome and fun! i always shied away from it because installing the android sdk seemed like a gargantuan task but there are .zip's floating around with the files required to run fastboot. all you do is place them on the root of your harddrive. pm and i'll be glad to assist further.
it could be something as simple as your apn settings...
v3rk said:
i'm starting to see why people warn against tool kits. you probably inadvertently flashed an incompatible radio somewhere down the line.
download the fd02 cwm zip here and flash in recovery. it will probably fix your issue. if not, try using fastboot to flash the radio .img's
also, learn fastboot. it's easy, awesome and fun! i always shied away from it because installing the android sdk seemed like a gargantuan task but there are .zip's floating around with the files required to run fastboot. all you do is place them on the root of your harddrive. pm and i'll be glad to assist further.
Click to expand...
Click to collapse
There's nothing wrong with tool kits. They are very helpful and useful tools, but...
YOU really need to know what you are doing just in case something goes wrong.
If you can "inadvertently" flash a wrong radio, you probably shouldn't be rooting in the first place.
v3rk said:
i'm starting to see why people warn against tool kits. you probably inadvertently flashed an incompatible radio somewhere down the line.
download the fd02 cwm zip here and flash in recovery. it will probably fix your issue. if not, try using fastboot to flash the radio .img's
also, learn fastboot. it's easy, awesome and fun! i always shied away from it because installing the android sdk seemed like a gargantuan task but there are .zip's floating around with the files required to run fastboot. all you do is place them on the root of your harddrive. pm and i'll be glad to assist further.
Click to expand...
Click to collapse
I know how to use ADB and fastboot.
I just used the toolkit because that's what it's made for. I've used plenty of toolkits before and they all worked fine.
Anyway, I will try flashing the FD02 and see if it works. Thank you.
yeah just try flasing another radio and it doesnt hurt to check the md5 either
I've been using my Galaxy Nexus for a month or so, with the official JB ROM (JR30C or whatever, deodexed and rooted) and today I opened Gmail.
That's it. I opened GMail, switched accounts, and my phone has been bootlooping ever since.
I wiped everything in CWM multiple times and reflashed it, and I can't get the phone to do anything else.
Any clues?
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Xfanatic said:
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Click to expand...
Click to collapse
I do not have a working NANDROID. I wasn't sure about the Internet policies at work, but it looks like I can at least make it on here, I'm not sure I'll be able to download another ROM.
I'm confused though, I mean I know it would help to try as many options as possible (to fix it) - but this ROM has been working for weeks. And the phone died randomly, not due to a recent file change or a botched program. The only boot loops I've experienced before were on the Nexus One, and it was always due to a buggy/bad flash or a corrupted ROM download - this one just developed epilepsy on its own...
Here's my plan, since these are the only things I can manage to download due to restrictions on Internet usage at work.
Factory 4.1.1 takju image from here : https://developers.google.com/android/nexus/images#takju
Modified ODIN software here: http://forum.xda-developers.com/showthread.php?t=1586807
ODIN won't rewrite my bootloader, recovery, or userdata, since I already OEM unlocked, but will reflash a stock image.
EDIT: ODIN won't do anything with my device. Trying this ROM instead:
http://forum.xda-developers.com/showthread.php?t=1801664 was using bigxie OTA before.
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
simms22 said:
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Click to expand...
Click to collapse
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
infazzdar said:
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm at work, and I only have my work computer. Group/secpolicy won't allow me to install anything, no admin rights, etc.
Would it even do anything? The phone barely makes it through one second of the boot animation before it loops.
sheik124 said:
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
Click to expand...
Click to collapse
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
Oy. Then how do I get another ROM on here? fastboot/adb?
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Adb push.
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Got more than one additional ROM on there via adb/recovery - my clue that CWM hasn't actually been able to do anything since the phone start looping is I'm still getting my custom boot animation.
I'm using the toolkit to reflash a stock image now. What a mess.
Even reflashing a stock image via fastboot did nothing. WTF happened to my phone? Won't stay on long enough to get a logcat
I'm having the same problem as this guy:
http://forum.xda-developers.com/showthread.php?t=1827685&page=2
I just got finished trying to flash 4.1.1 using ODIN. It still shows me the custom animation from bigxie's ROM (which has supposedly since been overwritten 2-4x times).
Screw you Samsung...this phone is a month old, I flashed -once- to rooted Jelly Bean, and the phone dies when I open the GMail app.
EDIT: WTF - I write screw you Samsung, it boots to the Welcome screen! Just long enough for me to see that my files aren't on it anymore, then it bootloops again. And again. Now it's re-stuck in a bootloop.
And now I'm at the homescreen. I can't rely on this thing like this...is my flash dying or something?
Nobody?
It worked long enough for me to re-enter all of my different Google account information and now it's dead again. Now it only flashes the boot animation for a split second for bootlooping.
I'm thinking of a hardware defect.
Beamed from my Grouper
Mach3.2 said:
I'm thinking of a hardware defect.
Beamed from my Grouper
Click to expand...
Click to collapse
Mee too. As you can see from my signature, I gave up and bought a One S yesterday night from Craigslist. Feels like a true successor to the Desire / N1. It's nice to finally have an AMOLED screen that actually seems color calibrated after the ugly mess that was my RAZR and my less than perfect GNex. It's a damn shame how much more painless flashing a recovery was on this thing.
Sent from my HTC VLE_U using xda app-developers app
was trying to get a ROM and vendor IMG installed and it all went down hill VERY fast. Im not able to get into TWPR and getting the red triangle.
Anyone have any tuts or tips to flash this back!
update:
Was able to get into fastboot mode and use wugs to reinstall. I REALLY need to get back into using ADB!
Everything you could ever want to know about the 5X in one thread including setting up the android SDK and using ADB/fastboot.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
PiousInquisitor said:
Everything you could ever want to know about the 5X in one thread including setting up the android SDK and using ADB/fastboot.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
you are a king of new england sir!
Im up and running now but I really need a refresher, been getting lazier with every phone that comes out
tevil said:
you are a king of new england sir!
Im up and running now but I really need a refresher, been getting lazier with every phone that comes out
Click to expand...
Click to collapse
What specifically are you looking for? That thread is pretty complete.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
What specifically are you looking for? That thread is pretty complete.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
yeah ill read through that. I honestly stopped using adb a while ago so I forget everything with that. The last phone I bricked was my nexus S! I used FB and ADB to restore it and then root everything up till a bit ago when I just tried and started using the wug tool box.
Its gotten me out of some jams. I was able to get it to stay on the FB bootloader screen long enough (cause it was looping too) to grab it and start flashing. Im back up, rooted, updated and already put in my edit for tethering!
Was scared for a minute though
was having a weird issue anyway prior where it kept telling me my phone was full. Now Im to normal with like 4 gigs used out of 24, until I titanium and TWRP backup