Hello there. I was wonder about about Darkys ROM so I have installed 9.5 successfully (thanks to noobish giude).
1) I have upgraded from official Samsung I9000 galaxy S (2.2) to 9.5 ROM + Dark core 1.4.
It gave perfect result - fast and stable.
2) then I did upgrade to ROM 10.1 with help of noob guide (recovery mode, no clean, update via zip file as before, disabled lag etc.). It was successfull too, BUT after install I restarted as in last instruction of upgrade and it has come:
Look at this screen in ATTACH please.
If I let it be it will boot up fine but:
1) it appears randomly inside of system (mostly when sliding notification bar up and down).
2) I cannot see recovery mode (its in there but it looks like it cannot work with display until initialization of system)
Anyone can help me please?
Then
So its solved thanks to user ceriko on official darkyrom.com.
//sorry for unfinished name of post (I am unable to edit it)
Bootloader problem. I had the same thing when I first flashed GB.
Hi!
I just bought a Nexus 4 with broken touch screen which I replaced myself.
After I replaced it, I decided to start fresh and updated the device directly to stock 4.4 using fastboot commands and got stuck in bootloop (4 circles going on for hours).
Then I tried different factory images and managed to boot under official Android 4.2.2 and it worked flawlessly until I tried to update with 4.3 OTA (with radio .83)
I found out that downgrading radio from .83 to .48 (or .53) allows the device to boot under Android 4.3.
I'm now stuck at this stage because the same trick does not work after 4.4 OTA (from 4.3).
The issue seems to be acknowledged by Google but they don't seem to have an official software fix for it since they only go for a replacement.
I'm considering an RMA but since I replaced the screen myself, I'm facing the risk to be charged 200€ if my warranty gets void (if they really control the device as they say).
Anyone managed to fix this issue? It seems to be linked to the radio (can't go further than radio .48 / .53)?
Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.
neoantho said:
Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.
Click to expand...
Click to collapse
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!
varun037 said:
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!
Click to expand...
Click to collapse
Did you find a solution?
Not yet. I will definitely post if I am able to find one. Researching on the topic currently.
I've got the same problem with 4.3 bootloop. Could this be fixed with custom rom?
Try flashing 4.2.2 rom - custom or stock
I'm with 4.2.2... and that's not what I asked. I want 4.4.2. Is it possible to load custom kit kat with this kind of sensor problems?
Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.
varun037 said:
Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.
Click to expand...
Click to collapse
I'm on 4.3 and the sensors dont work ... the proximity, gyro... nothing works... any solution?
Hello friends, i have a similar problem.
I went to replace the glass and warmed him a lot and damaged the lcd. I bought a complete lcd with touch, but when installing it the cel came in infinite boot, Flashed the 4.2.2 and booted but sensor is working by testing q I did for an app, the problem is they do not find my network and baseband ta as unknown, been through the radio's 4.2.2 (the version I am now). the motherboard was not with the screen when I get heated to the glass, were in housing with the display flex earpiece with proximity sensor and flex usb that has the microphone and led, everything is normal, the LED only that does not work. One would like some light please. I thought about buying the flex usb to see if it resolves, but does not want to risk spending for nothing. Thank you very much!
Sorry for my english, I'm using google translator
Sorry to Disturb
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Gloftking said:
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Click to expand...
Click to collapse
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.
FEW
varun037 said:
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.
Click to expand...
Click to collapse
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif
Gloftking said:
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif
Click to expand...
Click to collapse
Follow this. It has the reset flag removed and will not wipe your data
http://forum.xda-developers.com/showthread.php?p=53176897
Sent from my Nexus 5 using XDA Free mobile app
Hi,
I am facing the same issue .. Nexus 4 is stuck at boot loader after screen replacement .. is there any solution that I can follow to resolve this .
Regards,
Ripu Daman
The same problem with me, i did replaced my phone screen. I didn't notice that could damaged the phone. :crying:
so, theres no way to solve ??
Only way is to downgrade the os version to 4.2.2 and stay there.
nexus 4 stuck at boot loop.
Hi guys i have the same problem as you are describing, o got a nexus 4 android 4.2.2 JQRW build I've flashed it from all different ways and i just got flash cm10.2 and carbon rom but only stuff jeallybean and as someone said here i used adb sideload to push the update 4.3 and got stuck at the boot but i flash the radio 84 to 48 and my phone boot Fine but i am stuck at jeallybean yet and i want chroma rom android 7
---------- Post added at 03:00 AM ---------- Previous post was at 02:56 AM ----------
Please we need a wise man to fix this problem. I am tired of flashing stock img and custom ron for nothing.
Hi, i have the i9301i and i've installed CM12 unofficial rom latest version with everything done by the book:
I had original modified samsung 4.3 rom,
Using latest TWRP i've done complete format, data and cache wipes, install the rom 'cm-12-20150422-UNOFFICIAL-s3ve3g' and pico gapps.
After successful boot, I'm getting a contest background notification "“Firmware upgrade encountered issue” and it's locked to the background. I've tried to take a screenshot of it but i cannot: while taking a screenshot it captures only the actual screen but not the message. If you want to imagine, think about the non OEM message that microsoft is putting to non genuine windows background. The rom is operating normally without problem but this issue is extremely annoying.
I've tried to put the device in download mode - the same hidden message on the background is appeared even there!
Any idea for solution? Has anyone got the same issue before?
dannee2016 said:
Hi, i have the i9301i and i've installed CM12 unofficial rom latest version with everything done by the book:
I had original modified samsung 4.3 rom,
Using latest TWRP i've done complete format, data and cache wipes, install the rom 'cm-12-20150422-UNOFFICIAL-s3ve3g' and pico gapps.
After successful boot, I'm getting a contest background notification "“Firmware upgrade encountered issue” and it's locked to the background. I've tried to take a screenshot of it but i cannot: while taking a screenshot it captures only the actual screen but not the message. If you want to imagine, think about the non OEM message that microsoft is putting to non genuine windows background. The rom is operating normally without problem but this issue is extremely annoying.
I've tried to put the device in download mode - the same hidden message on the background is appeared even there!
Any idea for solution? Has anyone got the same issue before?
Click to expand...
Click to collapse
Try re-flash the Latest stock rom via odin or use the emergency firmware recovery via kies
Then flash the latest TWRP 2.8.5.0 by Rox
http://forum.xda-developers.com/gal...overy-t-r-p-samsung-galaxy-s3-neo-gt-t2906840
Finally flash the Cm 12.1 20151111 latest build by rox
http://forum.xda-developers.com/galaxy-s3-neo/orig-development/rom-cyanogenmod-12-1-s3-neo-t3099384
Press the thanks button if i helped you
Was given back my Nexus 7 tablet and was thinking about updating it. Currently rooted running on a 4.4.4 rom (purity). Is there any new basebands/modems that I need to flash/update before flashing a 7.0 rom? Would appreciate any pointers, thanks in advance!
You probably should first update your device to the latest factory image from Google (5.1.1 - LMY47V, including 4.23 - bootloader, etc.), then installing the latest TWRP 3.1.1 and you should be fine for a 7.x Nougat ROM.
Please be sure to select correct factory image (nakasi / nakasig) depending on your model and probably verify that the bootloader included within the factory image is a "good one" because there existed factory images from Google with a non working bootloader ... You probably might want to have a look here
AndDiSa said:
You probably should first update your device to the latest factory image from Google (5.1.1 - LMY47V, including 4.23 - bootloader, etc.), then installing the latest TWRP 3.1.1 and you should be fine for a 7.x Nougat ROM.
Please be sure to select correct factory image (nakasi / nakasig) depending on your model and probably verify that the bootloader included within the factory image is a "good one" because there existed factory images from Google with a non working bootloader ... You probably might want to have a look here
Click to expand...
Click to collapse
is the rom in your signature stable enough for me giving this tablet to my mom and for it to not feel slower than life?
right now im on 4.4 and its very very very laggy
i have an update to 5.1 but i have been there and it was Unusable...
do you have any rom recomendation so it performs nice with some not demanding games ? and browsing
mine its the WIFI ONLY version
tablet is so old that i dont know where to look for a good rom anymore..
thanks for the help
edit:
im updating to 5.1.1 latest so im am on latest bootloader and stuff (but as my tablet is not updating im doing a factory image install, then TWRP then this rom https://forum.xda-developers.com/nexus-7/development/rom-android-7-aosp-grouper-t3467514 )
so the steps to follow would be
install TWRP
boot into recovery
**Factory reset tablet (wipe DATA and cache)
**install OTA for groupr wifi only tablet
**reboot into recovery
**install GAPPS (bean something)
**wipe dalvik/cache _
**then reboot???
@gierso should be fine ... if you run into setup issues, skip the google account setup, switch on WiFi and then add a user account to your tablet
AndDiSa said:
@gierso should be fine ... if you run into setup issues, skip the google account setup, switch on WiFi and then add a user account to your tablet
Click to expand...
Click to collapse
nevermind tablet is not updateable .. usb port does not respond to PC ( i think is broken as it sounds as connected disconected many times) so i ended up giving up trying to make it connect ..
i might open it to try to solder the pins.. or to try to change the connector but for the time being i just formatted it and installed the sole game i need it for (it still charges but the data connection is never acomplished) ...
i will try to update my nexus 7 2013 with a similar rom (but ifrom the 2013 forum of course)
Hi guys, hope someone will be able to help with this.
I have been trying to downgrade the andoid version to 7.1.1 so that I can install nethunter. The downgrade works fine and I am able to boot into 7.1.1, set up developer mode and enable usb debugging, but everytime I reboot the phone it gets stuck on the boot logo. Strangely when I carry out system updates to update to 8.0 the system works fine and I can restart over and over again without any problem
Hope someone has had the same problem and found a solution for this.
mickey o said:
Hi guys, hope someone will be able to help with this.
I have been trying to downgrade the andoid version to 7.1.1 so that I can install nethunter. The downgrade works fine and I am able to boot into 7.1.1, set up developer mode and enable usb debugging, but everytime I reboot the phone it gets stuck on the boot logo. Strangely when I carry out system updates to update to 8.0 the system works fine and I can restart over and over again without any problem
Hope someone has had the same problem and found a solution for this.
Click to expand...
Click to collapse
Did you look over at the nethunter thread and tried the very detailed description of a working Nethunter setup and look up the necessary files you need at the end are a couple.
https://forum.xda-developers.com/showpost.php?p=79695958&postcount=175
If the issue persists can I take look at the log..
Gl!
PS
It is even more convenient with the revisit kernel by re4son, which you can use with LineageOS, if you want..
Here are most of the files you need
https://build.nethunter.com/contributors/re4son/angler/
https://www.androidfilehost.com/?w=files&flid=299779
https://mega.nz/#!QZxTwQ7D!477llbKVUEW9l1_y4mYqFWKJOA1Ya1rHDrDxH1scNrQ