Very strange. My phone was working perfectly yesterday. But this morning when I powered it on, it's stuck in a boot loop (going over and over to the first splash screen).
I can't get it into recovery either, which also seems odd.
I'm sure I can get it out of it by flashing a ROM or perhaps factory reset (goes into hboot fine). Will experiment a bit later (no time this morning) to see if I can get it out of the loop without flashing a ROM though - e.g. I will probably try just flashing Clockwork via fastboot.
Just putting this up there for info. I flashed a new radio yesterday, but as I said the phone was working perfectly, so I don't see why that should have anything to do with it.
I had issues flashing CWM recovery via fastboot... I was able to "fastboot boot recovery.img" From there, you can flash a ROM with ROM Manager and reflash your recovery.
Let me know if you run into the same issues.
steviewevie said:
Very strange. My phone was working perfectly yesterday. But this morning when I powered it on, it's stuck in a boot loop (going over and over to the first splash screen).
I can't get it into recovery either, which also seems odd.
I'm sure I can get it out of it by flashing a ROM or perhaps factory reset (goes into hboot fine). Will experiment a bit later (no time this morning) to see if I can get it out of the loop without flashing a ROM though - e.g. I will probably try just flashing Clockwork via fastboot.
Just putting this up there for info. I flashed a new radio yesterday, but as I said the phone was working perfectly, so I don't see why that should have anything to do with it.
Click to expand...
Click to collapse
You might have to flash a rom via bootloader/fastboot. Just remember you can't flash one with a older hardboot version. If you have the eng bootloader, you shouldn't have a problem. What a pain though, I hope it isn't the radio either as I flashed a different one earlier tonight also, lol!
Crap, I flashed the same damned radio as you did too. Ha! Although, I do find this ironic after our little debate about the forum merge yesterday I'm sure you can try reflashing recovery via fastboot and if that fails reflash stock rom through fastboot. Its not bricked for sure...
Did you reboot (properly) after you flashed the new radio? (i.e. after it powered on once).
I did worry that anyone with radio s-off will have issues like this when they tried to flash a new radio.
Lennyuk said:
Did you reboot (properly) after you flashed the new radio? (i.e. after it powered on once).
I did worry that anyone with radio s-off will have issues like this when they tried to flash a new radio.
Click to expand...
Click to collapse
He must have had a bad flash... I flashed the same radio with no problems and several powering off attempts and reboots, checking compatiblity, and backups. No issues and have already reflashed a few roms and kernels. The radios are safe... at least the lastest desire z one from Eygpt and the two stock tmobile usa ones are too.
I never did a second reboot after flashing the new radio, but it did reboot after flashing it from fastboot of course, and it worked perfectly for the rest of the day (I'm positive I was getting a better signal).
I just tried fastboot to flash CW recovery - same problem (stuck in boot loop).
I then tried fasboot boot with the CW recovery image - same problem.
Then I used fastboot to reflash the radio. It worked ! The phone is back up and running.
So that's odd. Could just be a bad flash, as has been suggested ?
steviewevie said:
I never did a second reboot after flashing the new radio, but it did reboot after flashing it from fastboot of course, and it worked perfectly for the rest of the day (I'm positive I was getting a better signal).
I just tried fastboot to flash CW recovery - same problem (stuck in boot loop).
I then tried fasboot boot with the CW recovery image - same problem.
Then I used fastboot to reflash the radio. It worked ! The phone is back up and running.
So that's odd. Could just be a bad flash, as has been suggested ?
Click to expand...
Click to collapse
Sounds like it... I've seen this happen on some old WM phones before.
Well my phone has exactly the same problem this morning after being left powered off overnight.
I tried flashing the recovery image and radio image again, via fastboot, like last time, but it didn't help.
Going to reflash the stock ROM. I'm starting to think there is something wrong with my phone and it's going to have to go back
Shizzer! Again? You went back to stock after using Visionary didn't you?.. Done Rage from clean yeah?
ddotpatel said:
Shizzer! Again? You went back to stock after using Visionary didn't you?.. Done Rage from clean yeah?
Click to expand...
Click to collapse
No I didn't use Visionary lol.
Yesterday, after first having the problem, all I did was flash CW recovery and flash the new (Egypt) radio again. Then the phone was back to life, I rebooted it several times and all was 100%.
This morning though it was stuck again but flashing CW recovery and the radio (both via Fastboot) didn't help at all.
So I've just flashed the stock UK/Europe ROM. Will root again via rage, install ROM Manager, flash Clockwork and restore the nandroid backup I did last night.
I will stay back on the stock ROM/radio combination for a bit because I'm starting to wonder if my phone has a problem. No-one else has reported an issue with this radio.
Edit - back up and running fine now after doing the above.
I'm still newbie in these phone things but really sounds like something is corrupting your files.
Device working perfectly after a flash and getting into boot loop later sounds like a hard ware problem to me. (also I have understood that /system is r-only if you don't remount it?)
AnyDone said:
I'm still newbie in these phone things but really sounds like something is corrupting your files.
Device working perfectly after a flash and getting into boot loop later sounds like a hard ware problem to me. (also I have understood that /system is r-only if you don't remount it?)
Click to expand...
Click to collapse
Yeah I know what you mean. I'm going to stick with the stock radio (even though it's worse than the newer one) for a while to check that the problem goes away. Then I will probably try flashing it again to see if the problem comes straight back again.
I also did wonder about whether I can just "dd" the new radio to the correct partition instead of using fastboot to flash it, though I'm not going to do that unless someone can confirm that's ok.
Related
While once again needlessly flashing stuff on my phone I lost SMS with the Cyanogen6 Snap kernel with Snap Turbo. From what I read I decided I had to reflash a stock rom to regain my ability to receive SMS. A flash of the update file has left me stuck in the bootloader. I had thought I good having used Unrevoked a few weeks ago. My Hboot was updated and is -S. When I turn the phone on it gets stuck on the white htc screen. Same when I try to boot into recovery. So I need to know how to reflash my phone with a stock rooted rom so I can start over. Shell commands work for fastboot but I am getting remote:not allowed responses when I try and flash recovery.
Please can you help me? I am going to sleep and letting the Evo get a full charge. Please do not delete this and link me to a solution.
Came here for the same, Did you fix this? my problem got worse, since adb doesn't seem to recognize the device, and none of Caulkin's methods here: seemed to work either. Somehow, along the way, Clockworkmod recovery got lost too, and I can't even flash a different rom.
shogun26 said:
Came here for the same, Did you fix this? my problem got worse, since adb doesn't seem to recognize the device, and none of Caulkin's methods here: seemed to work either. Somehow, along the way, Clockworkmod recovery got lost too, and I can't even flash a different rom.
Click to expand...
Click to collapse
I'd like to add a "me too" here.
I'm stuck with only fastboot available for getting the phone to work again.
I have a nandroid backup on my PC, that I could put on it. But I don't know the
fastboot command to use, or if there's even one available to use for a nandroid.
I also have a complete PC36IMG.zip. But again, I don't know the fastboot command
to use, or whether it's even possible.
Please help.
Thank you.
--Chris
I have the SAME PROBLEM! What's going on guys? Any fix?
So you probably see these types of threads all the time, but this one is different--
So the phone is a T-Mobile G2, Yes, It is Rooted, and S-OFF.
Long story short, I rooted the phone fine, but I cannot reboot into recovery.
I have the newest CWM flashed. It is version 3.0.0.5. When I try to boot the phone into recovery, it simply gets stuck on the HTC Logo screen. But, it is not bricked, but if I remove the battery, and put it back in, the phone boots and its fine. One more time. The phone is S-OFF and rooted.
The only thing I can do is flash CM 2.5.1.3...... 2.5.1.4+ do not work.
I just want to know WHY its doing this. Its my friends G2 and I have rooted mine the SAME exact way, and its fine. I have tried factory resetting it, but it doesn't work.
PLEASE TELL MY WHY.
EDIT*
I'm trying to do this process in ROM Manager- I also have tried flashing it more than once.
Brazildiogo732 said:
So you probably see these types of threads all the time, but this one is different--
So the phone is a T-Mobile G2, Yes, It is Rooted, and S-OFF.
Long story short, I rooted the phone fine, but I cannot reboot into recovery.
I have the newest CWM flashed. It is version 3.0.0.5. When I try to boot the phone into recovery, it simply gets stuck on the HTC Logo screen. But, it is not bricked, but if I remove the battery, and put it back in, the phone boots and its fine. One more time. The phone is S-OFF and rooted.
The only thing I can do is flash CM 2.5.1.3...... 2.5.1.4+ do not work.
I just want to know WHY its doing this. Its my friends G2 and I have rooted mine the SAME exact way, and its fine. I have tried factory resetting it, but it doesn't work.
PLEASE TELL MY WHY.
Click to expand...
Click to collapse
If you can boot up normally, load rom manager (download from market), and go to install alternate recovery, and install any alternate recovery. Then when that is complete, go back and install the Clockwork recovery version you want on top of the alternate.
What happens is SOMETIMES recovery will get messed up while installing, and you'll get exactly that, loop at the HTC screen.
If you cannot reflash an old, then the proper recovery through Rom Manager, you can do it via fastboot with your computer and USB, there are a few guides on the developer forum on how to do that. If you need i can try to dig up the fastboot recovery method guide later... but really, if you can boot up, Rom Manager is your best/easiest bet.
Yeah, I'm trying to do it using ROM Manager. and It still doesnt work. Ive rooted- unrooted and did everything, idk what I'm doing wrong. I tried flashing the new recovery like 4 times, it doesn't work for me. Thanks for the reply!
Hi everyone, I've come into a strange problem with my G2 and I bet someone here can help me out! I just got a refurbished G2 because my last one had display problems. I tried to root with one with gfree (05) and I ran into a couple of errors so I rebooted my phone and used the rage method. Anyway, I downloaded rom manager and flashed CWM 3.0.2.4 so I could flash that leaked gingerbread build. It wouldn't work for me, so I flashed xborders' version and it's all good. I went to flash the stock rom (to go back) and when it reboots it stays stuck on the HTC splash screen. The same thing happens with CM7, or any other rom I've tried recently. I let CM7 flash when I went to sleep, when I woke up it was still stuck on the HTC screen.
I'll explain what I do:
1. Flash superwipe g2
2. Flash the rom in recovery
I accidently deleted my froyo nandroid but I have one from xborders rom so I at least have a usable phone. Could my sd card be messed up? I've tried it on the two I have.
I had this problem with my other phone too, no matter what I tried I couldn't get CM7 to work. Now it seems like no roms are working.
After I do flash a rom, it doesn't say reboot system like I think it should? I have to hit back to go back into the recovery menu.
Ended up fixing the problem, thanks to anyone who looked at this!
Care to tell us how you fixed in case someone else comes to this thread for reference?
He probably didn't root the phone properly or the partition table has been messed up. To fix something like that just flash a stock ROM that you know works on the phone and from there you can use any root method to get SuperCID, Permanent ROOT, an unlocked HBOOT and ClockWorkMod. Then any rom designed for the G2/DZ should be flashed just fine as long as the requirements are met.
Hey guys,
Long time lurker, ROM user since the Galaxy S days.
Weird, intractable bootloop problem here. Gets to boot animation sometimes gets to the "upgrading android" screen, then bootloops in a few seconds after upgrading a few apps. Usually bootloops during the boot animation (doesn't matter what ROM or Stock ROM I try). Ocassionally gets to my "SIM PIN" screen, then reboots before I have a chance to enter anything.
Normal State have Cyanogenmod and Franco Kernel running buttery smooth. (CM10.1M3 Snapshot + Franco 376 when problem started)
Problem Started When I tried to update CM to the new RC1 from the Cyanogenmod upgrade button in "settings". I had SuperSU installed overtop the built-in superuser. Everything was working fine.
What I have tried:
Have latest CWM: Have flashed, reflashed, wiped and re-wiped everything imaginable through CWM. All Caches, system sdcard, you name it, if it's an option in CWM I have tried formatting or wiping it and reflashing a ROM.
ROMs I have tried - CM10.1M3 Snapshot, CM10.1RC1 CM10.1RC2, ParanoidAndroid 3.5+ (Latest), Bigxie Maguro Latest.
Finally I got fed up and decided to go back to STOCK, unrooted, unlocked using fastboot.
I did:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader magurobootloader.img
> fastboot reboot-bootloader
> fastboot flash radio radioxxlj1.img
> fastboot reboot-bootloader
> fastboot -w update image-maguro-jdq39.zip
And after booting back into the STOCK google recovery (man I haven't seen that screen in AGES) and resetting factory clearing cache. Low and behold -
STILL BOOT LOOPS!!!! What the hell!?!
I'm at my wits end. Any suggestions would be great. What am I forgetting here?! I am absolutely desperate.
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
bodh said:
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
Click to expand...
Click to collapse
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Vihsadas said:
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Click to expand...
Click to collapse
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Vihsadas said:
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Click to expand...
Click to collapse
So decided to try TWRP just to see...well I dunno.
Interstingly enough when I got to hit "reboot" in TWRP it says "OS not installed!!" which is weird because I basically flashed the stock everything 4.2.2 (bootloader recovery, system, boot, everything) from fastboot. Then JUST flashed the TWRP recovery.
I really don't know what to make of this. I just tried keeping the battery out for like 2 minutes, then going back into fastboot and manually flashing:
bootloader
boot
radio
recovery
system
userdata
relocked bootloader
of the STOCK google maguro 4.2.2 (MD5 sum is good. It checked out)
And I still get a continuous reboot loop that doesn't even get past the "X" animation screen. Very ocassionally (1/10) it does get past that screen and I get to the screen where you choose your language, but right when I choose my language, the phone reboots and then continues the loop.
Honestly...Unless someone has another idea, I think I'm going to get another phone tomorrow and pray I'm under warranty. I hate to do it, because I've never had to do that before through all my flashing/ROM adventures...but I don't know what else to do. I've been using sideload for everything (except of course the fastboot flashing back to stock), but I doubt that has anything to do with it...I dunno crap.
anyone have any words of advice?
One thing I thought i might work was redoing the partition table in Odin. So I tried this method:
http://forum.xda-developers.com/showthread.php?t=2065470 (Thanks to Samersh72)
ODIN worked perfectly, download mode worked well, installed fine, and...
still bootloops!
Sometimes gets to "updating android" does a few apps, then bootloops. Once got to the screen where I select language, and before I could select anything - bootloop!
Do you guys think this is hardware? Right now I've installed stock 4.2.2 through ODIN and locked the bootloader in anticipation of returning the phone...
give a try to omap flash
Good Luck
samersh72 said:
give a try to omap flash
Good Luck
Click to expand...
Click to collapse
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Vihsadas said:
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Click to expand...
Click to collapse
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
samersh72 said:
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
Click to expand...
Click to collapse
Yeah you're right. OK done.
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
bk201doesntexist said:
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
Click to expand...
Click to collapse
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Vihsadas said:
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Click to expand...
Click to collapse
Yes, but There's a build.prop property that enables ADB debugging.. Since you have access to a custom recovery, you can mount /system rw and make your changes there.
Sent from my Nexus
Similar issue
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
lsal25 said:
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
Click to expand...
Click to collapse
I dont know if you already did but try to wipe /system also and then flash a ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.
stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
I agree. I got it used tho which is an issue.
Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.
Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.
Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:
stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.
smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.