As the title suggests my Galaxy Nexus is stuck in bootloop. Heres what i did:
I rooted my phone long ago 1 year after it came out so i cant give much detail on this.
In the spirit of pokemonGo i tried to get it to 4.4. 5 Hours extensive reading later, I:
- installed latest superuser for 4.3 *
- made backups on my pc and phone *
* via SkipSoft Toolkit
- downloaded latest kitkat version (4.4), superuser, gapps from this forum
- installed them all in the given order above in the recovery screen
Got it working, but lots of bugs (graphic bugs, acceptable and to be expected; not the issue, browser crashing on starting download, usb from pc not connecting, google store not working, all media displaying services not working). In a feeble attempt to fix this i erased my user data and since then have been stuck in bootloop. Backups from sdcard not working, unable to connect to pc, or rather all usb drivers do not recognise my phone/cannot write to it.
Phone specs:
galaxy nexus I9250XXL31, build JWR66Y (version 4.3)
Help is greatly appreciated, for i am a noob and the /nexus is full of terrors.
Thank you in advance
nevermind fixed it, formatted all data and files, did the job
Related
As an introduction: When it comes to mobile platforms I'm more or less as green as they come - so forgive my ignorance regarding... Everything
I recently misplaced my beloved Nexus 4's flipcase. The day it went missing, I managed to stumble and drop my phone a distance onto tiles . It landed at such an awkward angle that the screen not only cracked but pretty much shattered - killing what I believe is known as the digitizer with it. It won't respond to touch.
Distraught I took up my dad's old Galaxy S3 - which was only cracked and a bit eaten (puppies). I went straight into using it and due to a demanding schedule I didn't have time to recover any of the data of the N4 - which I don't know how to do anyway. I quickly learn that I hate Touchwiz and the lack of personal details wakens me to how reliant I am on my phone.
So I set aside some time to get root - load a custom ROM (pa) - and transfer all my data from the N4 to the S3. The first difficulties appear when the S3 rejects towelroot. I install the towelroot apk from the official website and run it. Towelroot tells me it's currently an unsupported device. I google the model number (i9300) and apparently it works with Towelroot. Weird - I guess I'll do it manually.
So I install odin and download what I need and get the drivers for the S3 working and get root. It works without a hitch (I think until later ). Next I look into how to get a ROM on my phone. This happens: http://forum.xda-developers.com/par...s-7-error-installing-pa-t2844044/post54744770 (that's my post btw so it's the exact scenario). I will say that while I was going through this issue I tried many things to try and get rid of the error - I played with CWM a lot - tried to update it - updating failed with unknown errors. - I tried to flash my recovery - it couldn't flash my recovery. Earlier I had tried to install the CWM recovery on it's own from the play store (again - total noob) I only got related versions of CWM from 2011-2012. All of these problems were pretty confusing - and eventually due to the generic error about not being able to flash my recovery I had no idea how to proceed so I did as advised in the thread above and installed Flashify.
Flashify told me I had root, but that it couldn't get access to SuperSU - and to delete SuperSUs memory of Flashify. I went to SuperSU and SuperSU told me that it needed to update my binaries (I don't even know what my binaries are?!). I tell it it can go ahead and it just says "installation failed" so I install SuperUser to try and replace SuperSU - and delete SuperSU. And Flashify is clinging to the remains of SuperSU. Between my odd model identification (TowelRoot - Status 7 error) and my devices seeming lack of compatibility with.. Anything really (I imagine the two are related). I decide to clean slate it with a factory reset. Which I do from the CWM BIOS (?? Volume up + Home + Power?).
So of course unlike any phone I've ever worked with - a factory reset now means wipe my SIM. (Okay that was laziness and stupidity I should have taken it out first but allow me to grieve). As I should have predicted but didn't it wiped all my backups (foolishly saved onto the internal SD card) and leaves me in the fetal position on the ground making howling noises shedding tears onto the floor.
I can't afford a new phone - or to repair my old one. I need the data off my N4 - who's touchscreen doesn't work - which is problem number 1. And I would really rather not live with touchwiz, or have to do half the process again when I otherwise find the time to get rid of it, so I want to do that now but there are so many errors and I have no idea what I'm dealing with - which is problem number 2.
So please, if anyone can help me out with a)Getting the data off my N4 (it is properly set up as a mass media device) and b)Fixing this seemingly banjaxed S3 and getting pa onto it.
Any help would be really gratefully received. It's been an awful weekend - I also lost a hard drive with all my work and a lot of personal data on it to natural causes.
Thanks - I eagerly await my knight in shining armor.
Hi everyone... this explanation may be long but I'll try to put my problem in context, please patience!
First, I have years of experience coding stand alone applications and programs but close to none in Android or web development experience... so ... been confident that I could do something as simple ("Yeh right!") as rooting, why should I backup anything from my phone? Big mistake...
My S2 was getting old, space was getting limited and at first I downloaded some cleaning apps (Clean Master) was good for a time but then I had to start uninstalling some of my favorite applications to keep the phone fully operational. After a while I had nothing else to install, as programmed obsolecense was getting my ass, so I decided to find out some ways to get some room in and I found External2Internal app to use my SD as InternalMem, it did the trick except that there still was the "not enough space" message and some apps still refused to install due to the lack of room. So, basically this only modified the reported space in the Storage section of settings.
How I did this? Well, installed KingRoot and then APK Uninstaller with root and External2Internal to finish the trick.
As the problems continued I decided to research more, found out that there was a "better" way, more 1337 way to ROOT and that was installing a Kernel/ROM that was rooted and that would even improve my OS. So I took a tutorial on youtube and Installed "Siyah-s2-v6.0b5" using ODIN and "I9100 XWLSN .NeatROM.Lite.v4.6.1" with Recovery Mode -> Install ZIP from SD. At the end the CMW kept saying that I needed a upgraded version of it and SU needed to be updated but it failed everytime.
After each attempt I wiped to factory settings, cache, battery and even some delvik...
Nothing worked, I downloaded a console simulator to be certain about the rooting and surprise! It wasn't rooted at all...
Then I downloaded CMW update... SU Update... Syrah update... then tried with 4.6 NeatRom Apollo Kernel....:crying:
Now... the phone won't start... it can go into download mode and recovery mode but after ... nothing... I doesn't show anything pass the Samsung Galaxy S ii start screen with the admiration sign < ! > with the triangle.
I Factory reset, wiped everything and still nothing... doesn't start properly.
PLEASE HELP!!!
[bump] please help!
Hey,
I'm using a Samsung Galaxy S3 LTE (i9305) at the moment, on which I tried to install TWRP and CM13.
At first the installation of TWRP did not work - after that, the SIM card didn't work as the cellphone made a restart into the system.
After a little bit of research (and a few videos on YouTube) I managed to install TWRP and installed CM 1 3 (unofficial) on my phone.
After a restart my phone was stuck in bootloop - the CM logo was only shown at the start and did move.
I made a factory reset after that and tried to install TWRP again, this time with CM 11 (official) - with the same problems as before.
After I installed CM 11, Windows shortly recognized the phone when it booted - but I don't know, if my PC would have recognized the others too (Windows just played the sound it does, when a new device is connected)
The TWRP version is 3.0.2-1.
Any idea what I could try now?
Thanks in advance!
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.
Hi There,
My Main Issue:
I have a Samsung Galaxy S6 Edge SM-G925F, with a cracked screen, at 15% battery life the display is not usable, although anything after 25% it becomes usable and brightness levels from 60%~100% the device and screen is usable.
BIG issues:
Recovery Mode [Display Dead - But Active in Recovery Mode]
Download Mode [Display Dead - But Active]
Boot Screen and logo [Nothing but one flash on cracked side] - indicates OS boot
Work a rounds:
Watched YT videos of people in recovery and basically counted my way to wiping cache and dalvic etc [which worked once]
FIRMWARE Issues:
Samsung_SM-G925F_(G925FXXU6ESA1_G925FOJV6ESB1_South_Africa_v7.0)_by_(FirmwareOS.com) - Size: 1.9GB | Works But unable to boot
SM-G925F_1_20180530094301_nsue7o1m55_fac - Size: 4.9GB | Works but when installed only 16Gb assigned feels like the wrong firmware or dual sim or possible double os with backdoor
XFV-G925FXXU5EQL2-20180111184000 - Does not work without alterations.
Odin Version Used: 3.10, 3.10.6, 3.10.7, 13.14
1. When installing Samsung_SM-G925F_(G925FXXU6ESA1_G925FOJV6ESB1_South_Africa_v7.0)_by_(FirmwareOS.com) using odin, it completes with success although its unable to boot into the startup screen. (Most likely stuck on boot logo but unable to see).
2. When installing SM-G925F_1_20180530094301_nsue7o1m55_fac using odin, it completes and is able to boot and setup the device. My main issue is that this OS is double the size weird in app apps and the OS Storage is at 16GB and not 32GB.
Work Around:
I installed SM-G925F_1_20180530094301_nsue7o1m55_fac then at bootscreen entered download mode again and installed Samsung_SM-G925F_(G925FXXU6ESA1_G925FOJV6ESB1_South_Africa_v7.0)_by_(FirmwareOS.com), That installs with success and boots it sorts out the weird apps and works smoothly, only problem is now that storage is at 16GB and not 32GB still.
I have got XFV-G925FXXU5EQL2-20180111184000 working and installable although it is not worth the effort as the OS itself is missing major .com files.
I messed around to the point where i got it to 32GB although i flashed it to get to the working non sketchy size firmware Samsung_SM-G925F_(G925FXXU6ESA1_G925FOJV6ESB1_South_Africa_v7.0)_by_(FirmwareOS.com).
My Final Points:
Started googling how to build my own android rom, turns out that route is going to including a steep learning curve and a fast data connection.
Remembered XDA back when i used android 5 years ago and i must say this is a darn cool upgrade to XDA , tried to find a firmware failed
Found Linage OS, realized i cannot install that due to no sd card and no screen visibility in recovery mode.
Is there anyone with free time and the available tools required to create a proper bootable image for the SM-G925F perhaps stock 7.1 rom, or help me piece together a working one using multiple other firmwares.
Been mixing around with the images, then simply recreating the md5 files and the final combined.md5 would be used as the trial and error img.
Mission:
Trying to get this baby back up and running so that i could actually utlise it by installing linux etc as i do not need a screen to VNC or SSH
Thanks in advance
UPDATE:
New Firmware found:
ISSUES: Able to install although displays 16GB of storage still.
I was unable to install in stand alone from download as Odin got stuck at meta-data/foto.zip
After removing the meta-data i then remade the .tar.md5 and installed it using Odin
It was a success up until i checked the storage and it was incorrect. I then went to Settings and found those weird looking settings "Apps" setting doubled .
Link : SM-G925F_XFV_G925FXXS6ETK3_G925FXFV6ESE1_G925FXXU6ESE3_G925FXXS6ETK3
EDIT:
Currently Going to give this one a try
G925FXXS6ETJ4_G925FOJV6ETJ1_PAK-Droidhelper.com.zip
Will update with results
UPDATE: Did not work.
Going to fiddle with number 2 as that one happened to pick up 32GB on one install.
Found a New Firmware:
XSG-G925FXXU6ERD3-20180515181713
Going to give this one a try.
Will post an update
UPDATE: Did not work