Hi there first let me say sorry for any spelling mistakes i have dyslexia and its hard for me to spot everything when i look over it so sorry
now down to buissness i have an Alcatel 4 (6) 4g from argos in the uk i think the model on the phone shows as 9001X but also shows as 9001D when you connect wondershare or other tools
i broke the screen on the device and took it to one of thoes little shops in the mall to get it fixed when there the guy told me he could root the device for you for me at the same time i thought yeh cool save me from doing it my self
when i went back to get the phone later that day it worked good in fact perfect he had rooted the device using king root and all was working good the device was working but then it suddenly rebooted out of the blue when it was led on a table
when the device started back up king root was still installed as a system app but it showed the device as not having any root access witch i thought was weird but i just left it like that while i made a few phone calls but again half way through a phone call the device restarted it self again
this time when the phone started back up it showed the pixi 4 logo and then the alcatel logo and refused to move any further its just stuck on this screen. I looked on XDA for a fix but couldnt fine anything for my model the 9001X/D i found one page that said you can format using recovery mode
i held down the power and volume up buttons and got access to the reovery menu and done a factory install and then restarted the phone but again got stuck on the alcatel screen
i sent alcatel an email asking for a stock image to flash from recovery or something but i got no email from them i then tried to use the upgrade tool from the alcatel website witch i thought would do it the phone was found and the upgrade tool started but at 2% but then i get a red error saying failed to read some ingformation check phone status but the phone is turned off as per the instuctions and nothing is on the screen
i cant find a stock image anywhere cant get the tool to work when i goto recovery and tell the phone to reboot into bootloader mode to run fastboot its never worked even when the phone was working it would simply say waiting for devices on cmd also in recovery if i enable adb still finds nothing i have no idea what i can do to get anything working or reset the phone at all
does anyone know what i can do or have an image that would work anything at all my phone only like 2 months old and i dont know what todo as the stall is no longer in the mall to go back to
Related
Hello. I Was wondering if someone can help me with a dilemma......... i recently got my mega a month ago. I then decided to root my mega (As i do with all my android devices)The rooting process worked out great. The phone booted.....Everything's all peachy! root was successful! After about 3 weeks i wanted to record my screen. By the way i was running kitkat on my mega. So i installed a screen recording program. i wanted to record the screen so i started the recording..... but it wasnt recording. it kept saying an error message i think it when like gpu is not supported and change to cpu something like that! i thought nothing of it... so i changed the settings to gpu then to cpu (Not knowing what i was doing) after it failed to record again i threw the towel in and quit. i then played one of my mobile games(FNAF2) after i lost the game i went back to the homescreen and the homescreen was acting up... it was in landscape mode when i had the phone upright. it was bugging me to the point where i just rebooted my device. i tried rebooting my device BUT IT WAS IN A BOOTLOOP! i had no idea what was going on. So i tried to restore the backup and it was restored but it was still in a bootloop. at this point i was freaking out! when i went home that day i put the device in download mode and flashed the stock firmware but it failed and didnt work. but when the phone rebooted it booted up and my phone was on activation screen and it was in a different language. then i soon found out that my touchscreen wasnt responding! neither was the home button or back button. i really dont know whats going on. kies does not work i tried emergency firmware initializing and kies didnt read it i tried reinstalling kies and my phones drivers 4 times and it was a no go...... but i finally found a english firmware and i flashed it but it failed and said something like dev_not supported or something so that didnt work either..... i booted up my phone and the language was back to english and my touchscreen wasnt working neither was my home buttons or anything. i also tried installing custom roms but everytime i try to install them it says it completed installing but when i boot up my phone its the same activation screen. i really need help anything that can help will be greatly appreciated. also everytime i boot up it always says set warranty bit:Kernal
Ok so, I've been researching for about 2 days now. Trying to figure out a way to fix my soft bricked phone, now the problem with the phone is that, before it was bricked I had rooted it with this program called Kongo Root, after it ended and what not, it seemed like the phone was rooted successfully, so I went on and went to the play store and decided to download Superuser(even though I already had one from the Kongo Root program) anyhow I installed this superuser, and it asked for root permission, I allowed it, and after it asked me to go to the recovery install, I said yes, and my phone restarted, now it is stuck in the screen where it is supposed to download something or update idk, but it just shows an android with the sphere or whatever it is on its stomach, and there's a percentage bar at the bottom, and it just shows a 0% and it does not go any further than that, I cannot access bootloader, and it seems like my PC won't recognise the phone either. Help please. Sorry if my explanation is not good enough, I typed this really fast, im just really desperate.
Let me start by addressing I know this isn't the sprint thread but there's a lot more development here which equals more help. Plus this issue seems to be able to happen to any variant.
Second, this isn't my device I'm trying to see if it can be fixed for a friend. I'm not that familiar with Samsung devices but I have been able to get them working in the past via Odin or kies but this time I need some help.
So this is what's going on, my friend recently rooted his S6(SM-920P) not sure which method he used (don't think it matters at this stage) and was on stock rom (LP5.0.2) with xposed framework installed. He hadn't changed the kernel AFAIK oh but I did install TWRP for him and everything was working. Long story short he woke up a couple days ago to his phone being unable to turn back on. I told him how to get to download mode and I asked him what did it say on the top left corner it said something like "system binary not SEandroid locked" underneath that it said fac lock
So I had him give me the phone thinking somehow it did a OTA update while he was asleep or something either way I was confident using Odin to flash the firmware would solve the issue. Had the firmware finished flashing I'm confident it would have but halfway through Odin simply froze on installing system. I figured its just gonna take a while 45 mins later it was still stuck at the same spot.
Not really thinking about it I figured I will just reboot the phone back into download mode restart the process it should be fine. Not a good idea. Now all I get is a green screen saying to access the smart switch emergency recovery system. But it gets better.
My computer isn't recognizing the device now. I installed smart switch software and it's not recognizing it. I even installed Kies and it's not recognizing either.
Is his phone toast or what? I tried emergency system recovery but I need the S/N of his phone to possibly get this thing working again, but it boot into anything anymore except the screen that says Samsung switch...
PLEASE HELP ME if it's bricked it's bricked I get that but if there's a way to figure out what to do I'm all ears. Thanks in advance
guys i need serious help. i have had this device (name in title) for a while and i had it rooted. when resetting it from its menu it got stuck on android is upgrading screen for a couple of days. so i decided to restore it using sp flash tool. i went on needrom and got the latest rom from there BIG MISTAKE . i then flashed it correctly and it had booted but it would not let me use the screen because it had froze. so then forcing it to power off by removing the battery. unfortunately it never booted up again. now when trying to flash the first rom available it only shows the red bar and then i get an error ''BROM:S_ft_enable_dram_failed(4032).
i have noticed that when it booted up after flashing the rom it booted up with a htc bootanimation so the rom was a custom rom.
the setup screen also looked messed up.
i was told to right click on the preloader when it shows up and install the correct drivers manually. i did but i also noticed it had a yellow triangle and was named mt65xxx preloader. once updating it it is now called something like mediateck vcom preloader or close to that but when connecting the phone it oonly stays there for 2 seconds and disappears and never comes back unless i dissconnect and connect the phone again.
someone please help and if you need more info just message me.
Hey guys, I've got a Kyocera Brigadier and I decided to change the runtime from Dalvik to ART. Now the phone is stuck on loadscreen and I don't know how to fix it. The phone is rooted using the KingRoot app, but I don't know if that would help in any way.
Please help me guys!
Similar Issue
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Ornias Abezethibou said:
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Click to expand...
Click to collapse
I have the same problem. I bought a new a Brigadier that was on 4.4.2. I rooted with Kingroot ran update and now my phone will not boot past Kyocera screen. It goes black with the back light on. Did factory wipe and still nothing. I am shocked that KK has killed yet another phone of mine. I very much dislike KK ROM. What did you find out?