Hey everyone,
I'm sending my Verizon Galaxy Nexus back under warranty because the USB connector broke. I'm running JellyBelly 11.0, with the stock kernel (it's 4.2.1 if that's relevant), and followed the instructions here: http://rootzwiki.com/topic/19864-vz...ockrootflash-romsfaq/page__st__40#entry759280 to use MobileODIN and revert to stock. I used the correct PDA file, used MobileODIN without everroot, having it wipe data and cache. It rebooted, came up with the screen where it had each of the categories (kernel, system, etc.) and under each it said wiping and flashing, and after about 10 seconds it just rebooted back into JellyBelly. I tried it multiple times, and it does that every time.
Does anybody happen to have an idea why? I could reflash CWM and install a different mod if that would cause a problem - I have the replacement already and can charge the battery with that. I just have to send it back within a few days.
Related
Hi All, I come begging for help after exhausting all of my options and searches for similar issues.
I have a CDMA Galaxy Nexus Stock 4.0.2 but rooted (I installed CWM).
I woke up to my phone stuck in the boot loading screen; it just kept looping over and over. I shut off the phone restarted it and the phone was practically unuseable, it ran very very slow. Now I haven't done anything recently or installed any apps. The only app I installed was a modified MMS app (one of the Inverted Black ones), but that was 2 weeks ago and everything was running fine since then. (However since I'm not on a deodexed Rom, I knew there could be issues).
Well I of course switched back to the stock MMS app that I had manually backed up and that did not help. Now my phone would load, it would get to my homescreen, but it would then say something along, "service is not working, wait, close, or ok?" I'd hit wait and within 2 minutes my phone would automatically reboot and then go into a a sort-of bootloop (it would just show the boot.img and loop).
I then tried to restore two Nandroid back-ups (which were basically bone stock and made months ago) and both worked, except it would say secure.img not found or something like that. I was still able to boot up and use these back ups, but then within 5 minutes I would get the same error and then the phone would reboot.
After retrying them I decided to to just go bone stock and wipe and do a factory reset. This worked and everything seemed fine until I went to turn on wi-fi.
I would wait for wi-fi to turn on and eventually it would just quit and then reboot the phone. I did this 3 times in a row to confirm that it was indeed wi-fi causing these rebooting issues.
Now here's the thing, right now my phone is working as I have purposely tried not to touch the wi-fi (I need to use my phone) . Data, voice, mms/sms all work. But I literally have no idea why wi-fi would be causing my OS to go crazy?
My last resort is to flash the stock toro.img but I was hoping you guys could help me before I get to that point.
As of right now even though I did a data wipe/factory restore my phone is still rooted (rooted apps all work) and my bootloader is still unlocked. (I renamed the secure.bootloader file as per the instructions when using fastboot to load CWM).
Please help me troubleshoot this, Thanks guys.
I don't know if you have tried but maybe try flashing a rom after a data wipe
angelino0919 said:
I don't know if you have tried but maybe try flashing a rom after a data wipe
Click to expand...
Click to collapse
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
JayBeezy802 said:
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
Click to expand...
Click to collapse
Well you can always relock the bootloader. I doubt you will have to go back to stock though
This morning I found my battery dead. When I got it to boot, it was bootlooping. I tried flashing, wiping, everything. Bottom line is if I sync to google, my phone goes into bootloop. Full data wipe in recovery does nothing, all my apps are there and work fine, flashing works fine. Tried installing twrp, same thing.
Any ideas?
Anyone got any ideas? Could this be a hardware problem?
Guess I'll try going back to stock when I get home. Unfortunately I could never get mtp to work properly.
Sounds like a bad ROM you are using.
Does it use the CM GAPPS file?
You can try flashing CyanogenMOD's latest GAPPS and i bet that would fix it.
Galaxy Nexus GSM
Tried many different ROMs, that was not the problem. Wipe didn't work, even the native factory reset. Went fully back to stock and rerooted and it seems to be fixed. Still working on restoring things.
I've been trying to get a Rom on a S3 that the wife likes, so I've recently flashed the latest versions of Hyperdrive, Synergy and Wicked. I always follow the proper procedures of data wiping/factory reset, clear cache, clear dalvik, format system, and format data between each flash. I tried Hyperdrive first but had google sync errors, so went to Synergy. Synergy wouldn't connect to the nectwork so I went to flash Wicked v10 but the device wouldn't wipe/format data. I let it set for 20+ minutes and it never progressed. Pulled the battery and tried again but same result. I was able to install Wicked w/out the data wipe and it seemed to boot up ok but I was determined to get that wipe. So next I tried to restore to a backup from a week ago and it also stopped progress at the formatting data step. I re-flash Wicked v10 w/out the wipe. Once it did its thing and booted up I used went to the Factory Reset option under Settings but now the phone is stuck on the screen with the Android figure and a progress bar. Pulling the battery and trying to boot into recovery or even a normal boot all results back on the progress screen. I've managed to thoroughly piss off the wife by disabling her phone. Can anyone tell me how to fix this? I don't care if its reset back to factory rom or just anything to will allow the phone to work. Any help is appreciated.
Have you tried using Odin to flash a new original factory ROM?
IDK if you can get into Download Mode, but, if you can, it's worth a shot.
i agree with that statement. try flashing stock and unroot with odin. i have use hyperdrive since march, and i have not had that issue, so maybe its just a bad download or something. just try odin,
So I've recently been having an issue with my phone that I haven't been able to fix through various standard fix methods. I've tried searching for this exact issue but the only thing that seems to work for other people (albeit they were on different devices when they had this problem) hasn't fixed my issue.
Long story short, I went from SlimROM 2.2 (and many other 4.3 based ROMS) to ForkMyLife 4.4.2 to try out KitKat, and I eventually wanted to go back to SlimROM.
I always full wipe (System/Data/Cache/Delvik) and then flash my ROM (in this case it was Slim), a reboot netted me a bootloop/boothang on the bootanimation. Wiping Cache+Delvik cache will get me to Optimizing Apps, but then it hangs at Starting Apps. At which point I can battery pull, restart, and it will restart just fine (typically, I did have one time where this didn't work). But I'd have to do this series of events every single time I reboot. I've tried multiple ROMs, multiple kernels, but everything ends up doing the same thing after a reboot. I've even done a full Stock 4.2.2 Image flashing (full SDCARD/DATA wipe an everything) using mskip's Toolkit, re-rooted and re-did my entire phone to Liquid 2.37 booted up the first time no problems, but the boothang was back on the very first reboot.
What is somewhat odd to me, is that I can run a 4.4 based ROM with no boot issues though. I ran FML 4.4.2 for a few days and numerous reboots, and the same for OmniMetal 4.4.2 to see if it would lead to any boothangs and I had no problems with either.
Any ideas or thoughts from anyone on why reverting back to 4.3 after a 4.4 ROM would cause so many issues?
Hi everyone, this is somewhat complicated and il try my best to describe what happened.
My device is a i747m (rogers).
I was running CM10.1 (running gapps-jb-20130812 and CWM recovery 6.0.4.3) for a long time, tried to update to 10.2.
(i messed up on 2 things.I don't think i cleared neither of the cache or data and also didn't have proper gapps which would be 20130813).
After installing 10.2 through recovery, it would just stay in the boot Cynogen booting logo.
i restarted into recovery, since my old CM10.1 zip was still there, i installed that instead, but same thing happened, it would just stay at booting logo.
I had made a nandroid back up from before all of this, and so i wiped data, dalvik cache, cache, formatted system, and i recovered into that, which was a stock 4.1.2 rooted (rogers).
However, nothing worked, only WiFi. I couldn't make any phone calls, send/receive messages, or get data.
I then used ODIN 3.07 to flash the new stock 4.3 rooted (rogers). WiFi worked as before, but i still couldn't make any phone calls, send/receive messages, or get data.
i then re-installed the latest recover 6.0.4.5, and installed paranoid android 4.4.2 and gapps for this version. But still nothing, so i went back to the stock 4.3 rooted.
4 months ago, when i made the nandroid back up, i also made an IMEI back up as well (i did not do a full imei/NV/EFS/IMSI/data backup) , i only had my IMEI backup, so i wrote using "NV items reader writer" the IMEI back onto my phone, and now i can recieve/send messages, and get phone calls and make phone calls. wifi also works.
But my data is stuck in Edge, its extremely slow, takes 10min to download a 15mb file.
so far:
-The APN settings are correct
-my IMEI number in settings menu, matches the one on the back of my phone.
-network mode is GSM/HSPA/LTE
-i have installed the latest modem for i747m through CWM recovery and also tried slightly older versions.
i am pretty much lost and i dont know what i should do.
-rogers has told me to use kies and perform backup and then recovery, apparently that will factory reset my phone.
-should i simply use kies to install the latest 4.3?
-does anyone have the imei/NV/EFS/IMSI/data files? or the full NV file?
-should i install CWM recovery and wipe everything that i can? and re-install stock rooted 4.3?
-should i use QPST to fix my IMEI? <-- dont know anything about this, noticed a few threads.
i have used these threads in all my rooting and so forth.
http://forum.xda-developers.com/showthread.php?t=2179330
http://forum.xda-developers.com/showthread.php?t=1831898
http://forum.xda-developers.com/showthread.php?t=2129993
please someone help me out, I dont know how to fix this.
thank you for reading this long and complicated problem.
same problem, ive spent every minute working on it for a week