Database Users

suddenly occuring start up problem

hey guys, just wanted to ask if somebody has experienced something similar..
i had jacxhero running on my 32a without problems. tonight i had the phone on the charger, and in the morning it turns off everytime after the first splash screen. i can access the bootloader mode etc normally, just loaded cyans rom and it works. but...why this sudden inusability? i havent added any program or changed settings for the last 2 days or something...

I had the same problem but with a different ROM. It was the TIM ROM which can be found in the Sapphire Android Developement section here at Xda-Dev. I'm not quite sure if it's a nandroid backup or if it's an Update.zip, but as I had it installed it seemed to be the exact same ROM my device has been shipped with and it read the same numbers in the About-System dialog thingie and so on, it was like if it was the shipping ROM.
Always after about a day of usage or so it suddenly froze though, then the device reset itself and then endlessly looped at the bootscreen. Very annoying. It didnt happen with any other ROM since then...

Mineee..
That's weird..
But, you had any data connection?.. maybe it tried to update something!
Mine started rebooting after entering on suspend mode(not on the splash screen)! The program settings from the overclock just was pulled after I run out of battery (with the "forced" reboot) and started making conflict with the specs of the myhero rom.

Whats the developmental aspect of this thread??
None.........so please post in General.
Warning given.

seems like i got more problems since this "crash"
after reflashing to cyan after this startup error and then reflashing jacheroski 1.4, im able to load hero roms like jacheroski 1.4 on my magic and they work fine, but im not able anymore to load any roms without hero kernel it seems..
i tried with several roms like different versions (working before versions!!) of cyanmod, hofo,..they all loop at the last splash screen or stay black when it should come to the actual os(one step after the last splash).
am i "doomed" to stick to hero roms forever?^^
im using eng spl .2005...should i try to reflash something? or have you guys got any other ideas?

Problem with friends Galaxy S

Hi.
My friend got her Galaxy no more than two weeks ago, and I installed the newest Darky ROM (10.1) on her phone, since it has been working fine on my own Galaxy S.
The problem is that her phone just stopped working... just like that.
She thought the battery was drained, so she charged it, and when booting it up it would remain in the samsung logo (boot screen).
Well I put it into recovery and formatted it into factory settings and thought it would be fine. Well it kinda worked: it started up to the setup wizard, choose language, insert SIM card etc. and finally when clicked the complete button, the screen stayed black and few seconds later a message came saying that there has been an error with the android setup configuration.
This is exactly the same phone as I have and mine is working perfectly fine. Dont understand why this phone is acting up.
Will re-flashing it with the same Darky ROM fix this?? The phone has got warranty, but I dont think they'll accept it anymore cause of the custom ROM I put in.
I also have a video of this, but since they assume I'm a spammer, I cannot insert any links for now.
EDIT: Problem solved --> reflashed with Darky's ROM, now working fine. Thank you both slaphead20 & MasterJam882

you can try reflash...or darkys ressurection...or ezbase rom

Just flash an official rom from www.samfirmware.com.
If u still have bugs and errors u know it's a faulty phone and u can send it to samsung without the fear that they wont accept because its an official ROM every user gets over KIES.
greetz

[Q] motorola defy does not start

Hi ..
I had updated defy to the latest cnmod nighty version. ( 110410 ). Eveerything was working fine. i played with the phone for the entire day. video acceleration was awesome and played gt racing.
Suddenly there was problem with wifi connection. I decided to restart the phone. Choose the reboot menu . and now the phone is stuck with the moto logo on startup. Nothing happens after that.
When the bluelight blinks after the android menu , when I press the down button , I get android bootmenu v1.0.5 (By cynongen defy team and galaxy) ,
i was not able to do anything from here. It has these menus :
1)Boot : boot is set to 2nd init
2)cpu settings
3)recovery : in the recovery menu , If i choose latest recovery or stable recovery , I get error in /system/bootmenu/script/recovery.sh (Result: no such file or directory) , and when I choose stock recovery , the phone restarts and is stuck with an exclamation mark )
4)tools: I could understand what to do here.
When nothing did work , I pressed both up and down button after changing boot to normal. there i cleared some cache or something , cleared everything that I could.
After all this my phone is in the same place. A moto logo on startup.
Please can someone help me . This is my first android phone and also the first costly phone I bought and I did something nasty on the first day itself.
i am a normal end user who knows nothing more than gui.
thanks in anticipation

hey
flash a stock 2.2.2 with RDS from bootloader
you gonna need latest defy drivers for windows plus a stable froyo i guess
google this "how to unblick a bricked defy"
let us know what you do and what changes

are you sure this is a case of bricked defy. I had read in many places it is very difficult to brick defy.

its not bricked
but that is what you need to search for to get the solution
i did so too

What "Natsikap" said.
Clear Data/Cache.
Flash Official Froyo 2.2.2 using RSDLite, Use your region correct Froyo (If you are from India use SEA15 Stock ROM -Get it here http://forum.xda-developers.com/wiki/index.php?title=Motorola_Defy). Everything will be Stock normal. Read everything in the wiki before you flash anything, esp read the "How to get back to Normal in case things go awry" part you will save yourself the High BP!

thanks all for your support.
i have installed the orginal manufactuer android froyo
and flashed it later with cynogenmod 7.1 for defy. The latest stable one that was released yesterday
One more question:
Should I unroot this cynogenmod .. so that I don't mess something.

congratulations
you sorta came from behind and am sorta left behind
question: does the 7.1 have any wifi issues? working properly?
tell me so i can make the jump too
thanks bro

sorry for the late reply..
no it does not have any issues.. at least i could'nt find any.
wifi was working like a charm. used it for around 2 hours ..
Couple of questions..
1) i don't lke the menus flying into the screen. How can i change this animation to the normal fade animation that came with original os.
2)should i unroot my cynogenmod should that i don't cripple it while playing with settings or someother way.

Do not unroot CM7. Make site you make a backup in recovery, that way if you mess something up you can just restore it. As for animations, go to settings> cyanogen settings> display, you should be able to change the animations. If not try spare parts app.
Swyped from my MIUI Defy

i have defy plus.....i havnt rooted it ...its working on original 2.3.6
my phone is starting but power button not working.....when i put it on charing lock screen comes to life but touch not working..
sometimes it remains on moto logo
please help

910F lags at 5.1.1 and after downgrade

Hey guys,
after flashing the 5..1.1 rom my Note 4 started to lag at the keyboard after typing few letters or reading the website or in menu.
I use the N910FXXU1COH4 software. The worst part is that it happened yesterday. I havent got lags before (never ever).
Now I've got also lags when I downgrade to 5.0.1
Do you have any idea why this happened? My phone is ofc rooted and I've deleted most of the useless (for me) crap out of it like Instagram, NFC etc.
Do you have this kind of problems with your phone?
Thanks for reply.

I had the same issues you've stated after flashing a 5.1.1 Sweden rom with ODIN.
It lagged like crazy while other aspects were buttery smooth.
After a factory reset and a re-install with ODIN (just the way I did it- not saying it's the correct way of doing it) my phone is running as it should- super quick, smooth and as a Note 4 should be.
So I'd recommend full-wiping and then re-installing the 5.1.1 tar via ODIN.
I've also rooted now too with no issues.
Good luck.

I've got also problem in games. Sometimes the animation just freeze for about 0,5 s and then it runs again. It happens everywhere. And I've got it from yesterday. Dunno whats the problem...

I'm having lags and stutter too my friend, but i'm gonna leave it like this for now and wait for a proper release of 5.1.1 for my country instead of frankenstein mix it like i did now.
If that does not fix the lags im going back to 4.4.4 and never upgrade it again.

Guys, this problem is quite strange.
I've downgraded to 5.0.1 and then to 4.4.4 and every time Ive got lags on keyboard and TW. My phone started to freeze for about 0.5 s - 1 s. Its very annoying and I dont know how to deal with this problem. And it scares me ! Cuz knox is [1] and the warranty went for a walk I guess so i dont know what to do now...
Have you ever this kind of problem with your phone? Even the downgrade did nothing. Before flashing the 5.1.1 system it was fine. Now going down and wiping whole system gives me nothing ;(
Please help! I dont know what to do now...
On cyanogenmod 12.1 works fine. The problem is I guess with the touchwiz systems...
On 5.1.1 touchwiz is also overheating now :/ maybe thats the problem?

So the problem looks like this : After flashing the Swedish 5.1.1 system it all started up.
I can see it in:
1) Games - when it randomly freezes for second
2) Keyboard - after hitting multiply in letters typing something like asidiasjdasijdsaid -> it sudennly stucks and then after about 1 s the button ive smashed shows up in the text message with the lag3
3) touch wiz - after swiping from homescreen to another screen just dont answer and after about again 1s it changes
4) the top bar - with wifi, sounds, brightness, clock, battery etc) also goes down with lag - I swipe with my finger and after 1 second - it react.
5) sometimes it shows the grey suqare at the bottom "Phone is in factory mode" - red letters. It shows only for a while and suddenly disappear.
I've changed every rom now - from 4.4 to 5.1.1 and its still broken! On the Cyanogenmod it works just fine. Something might be broken but I dont know what. Also in cyanogenmod the only game i play have this lags. Other things works fine.
Any solution, what can i do? everything was ok before flashing the 5.1.1? Ive got the EFS folder backuped via TWRP
// EDIT
So - after I've found the backup which I've done just after buying Note I've restored full system (EFS, cache, system etc) and it helped. I guess 5.1.1 flashes makes that my Note 4 had a very bad day.
You can close the topic. My advice is to always have backup ! Glad Ive done it before.

Custom ROMs result in black screen

Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon

Hi:
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
I'm in the same situation. I think these screens are not 100% compatible so it seems a hardware issue.
Maybe using vendor partition but i'm so stucked as you.
My phone can't hotboot any official recovery although i can boot flashed recovery only if i boot slot a not slot b.
Stock roms boot always using slot a but tried Lineage (thats uses slot b) and got always black screen.
I'll keep reading and trying to solve it.
Regards.

simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
Have you made any progress?

gsausalito said:
Have you made any progress?
Click to expand...
Click to collapse
Thanks for your interest but I've made no progress and actually given up on it. I'm sure the issue could be resolved by buying a new, more compatible screen but I'm not going to put any more money into the phone.
As far as the software solution goes, I've tried almost every combination of ROM + Kernel i can think of but the only thing that works is the stock ROM.
I'm going to close this thread as I don't think it's much use to anyone.
Regards

Sorry for posting here, but i am in the same and i noticed that flashing canting 4.9 kernel gives display for like 8 seconds after screen turns off. May it be a kernel config issue? if anyone in this forum could answer this i could try and change it. Also flashing stock kernel on custom rom solves the problem but makes other thing fail

Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.

Hello Mi A1 friends.
So yesterday I decided to change my crack LCD screen and to my surprise the phone boots into Xiaomi Logo and then after that its just a black screen. Message and other notifcation sounds still come in which means that the phone mange to boot into home screen, just with nothing to display. At the time of changing screen, I am on stock kernel and Pixel Experience 10.
Gonna flash back to stock pie(9) rom and see how it goes from there.

Deezio said:
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Click to expand...
Click to collapse
Sry for reply to an old post, but how did you do it? How did you flash kernel when you can't enter twrp because of screen issues? I have exact the same problem, where stock rom works but everything else cause blank screen. Also can't boot to twrp - probably the same reason.