Hey guys, this is my first Thread in xdadevelopers
I am pretty new to coding and all this "behind the UI" stuff, but i am eager to learn more, since its really fun.
So i have got a new Phone : the ulefone power 2 with MTK6750T Prozessor. It has quite the battery with 6000mah, but i still wanted to root the device to archieve like one week battery time or so xD
I rooted, installed TWRP recovery and some apps, everything just went fine. I didnt install a custom rom, since i didnt find any for this phone. Well, i wont buy mtk phones anymore, since they dont offer open source code with all its community possibilities
Anyway, today the touchscreen suddenly stopped working. I thought its a common bug, restarted it. Now it wont start the OS anymore, its only booting in TWRP. I dont remember well, but it said something like "phone is not safe, gotta factory reset".
Since i have TWRP, i just did the reset. Without success though. Its still booting into recovery and cant shut down either, whatever i chose in TWRP options.
My next thought was flashing a new ROM with TWRP, which doesnt work due to "zip file is corrupt" error, even though its the stock file from ulefone.com
Since TWRP has a command terminal, it might be possible to use to stop the recovery bootloop when connecting to pc? in this case i might be able to use adb, but atm i cant, and the battery is non removable
I dont care that much about having a phone, i could just buy a new one (xiaomi redmi note 4x it would be), but i would really like to fix this and enlarge my knowledge for situations to come.
Hopefully someone of the professionals here can help. There is a similar Thread already by drkeey, but in my case i can still use TWRP with my mouse, so there might be hope.
Related
Hi Guys! I usually lurk around here, but now I really need some help.
Basically I have a Rebranded Chinese Tablet called "Tabulet Mech" and it's a redesign of a M701 tablet.
With a bit confidence of rom flashing, I tried flash a rom from a forum which talks about this type of tablet. With careful action I tried flash the rom using FWDN, and miserably failed T.T
while flashing on FWDN I used "Low format whole memory before download", so I guess the FWDN is formatting the whole tablet.
I dunno if I did something bad while flashing it, but since I didn't see any Recovery Mode available for the tablet, I can't exactly recover my tablet at all.
And now, I don't know if my tablet is already turned off or not, since the tablet is still heated up, and when I plug my USB on it, my PC still detect it (even my Moborobo), but since there's nothing on the screen, well you know I can't figure what's happening.
So my question is, is there any way I can install any rom to just make the tablet back working again?
Hiya
I have an Alcatel Onetouch Pop C1 4015D (and for the record, I'm never buying this brand or similar junk again). I just got it un-bricked after a few months thanks to the online USB firmware updater. It's currently in pretty much its factory-default state again, preinstalled crapware and all.
What I'd like to do is install a custom ROM on it, to have a clean system I can actually enjoy owning, e.g. AOSP (if that is what I think it is: the basic, clean Android system). The problem is that I'm getting a little overwhelmed with information, tutorials linking to more tutorials, tutorials linking to downloads for which I have to "complete a survey" and such (abort abort abort), 2 different tutorials for the same thing stating different ADB commands, a few outright scams, etc etc etc. There's tons of information out there, but 90% of it seems wrong, irrelevant, device-specific or otherwise unusable. I've already spent hours on this and still haven't gotten anywhere.
I'd be very grateful if someone actually reliable could walk me through the entire, correct process, please. :fingers-crossed:
I'm just going to write down the bits and pieces of info I already have:
I've already rooted it with Framaroot; no problems there, superuser works.
I've found this site that lists several ROMs, presumably specifically for the C1, including the standard ROM and a cleaned version: tinyurl dot com/o24wqoe. The AOSP one strikes my fancy and is on my SD card already.
The same site says I can just put the provided ROMs on my SD and install them as updates via stock recovery, but I highly doubt that because I read everywhere you specifically can't do that. Sounds like fake advice to me.
I'm told I'd need to unlock my bootloader, but once in fastboot/bootloader mode none of the offered fastboot unlock commands really do anything. The "..." appears in my console and then nothing.
I've tried installing TWRP and CWM recoveries, but you know, "your device is not supported". There's this video of a C1 with a custom recovery (watch?v=_TGgXIp3fWM) and the comments claim it's CTRecovery, but I can't even find anything about that. I already submitted requests for a fix for my device to twrp and cwm half a year ago before I bricked this thing, and one person promised he was gonna make a build for me, but nothing came from any of that.
I think that's just about all the useful things I can extract from this whole mess of information I have...
Please help me make sense of this overload of info and device-specific shenanigans, and walk me through what seems to be such a simple process for everyone with a mainstream device?
For the record, I'm back down to barely being up-to-date on what is what anymore. I'm more than familiar enough with the theoretical side (bootloaders, partitions, bios, etc) because of my heavy computer usage (professional programmer), but once I get into Android I'm just lost. All that fancy terminology nobody seems to bother to explain, things that are taken for granted but aren't really obvious (like a guy demonstrating the installation of a custom ROM, and only mentioning 10 minutes into the excessively long video that you need to install a custom this and custom that first), so many alternative methods for the same thing that have different dependencies (unlocking bootloader vs custom recovery), etc... I don't know anymore what's device-specific and what isn't, who is telling the truth, what a given tutorial is actually making me achieve in the end, etc. TL;DR I'm lost, I'm not stupid but I'm not gonna pretend to know anything about Android's subsystems anymore at this point.
wow u wrote a full post and u speaked for me as have the same problem
Custom recover
i have made a recovery for the 4015x
and got one of the roms to work
(and a fixed stock recovery)
there are 6 versions of this phone and at least two different partition tables that ive seen
but getting it back from softbrick id use the "mobile upgrade s 4.1.1" from the alcatel site
alcatel,mobiles,all mobiles, pop c1, support and on the right hand side down load the program and follow
this forces a stock rom back on the phone (no root and all data wiped)
im waighting on the mods to let me post links so i can host the roms and recoverys
but if you want to mess with the roms your self you can edit the partition tables and get the roms to install.
id use the app "diskinfo" to check what partitions your system and data etc etc are useing and chainge this in the roms.
hope this helped
p.s. if not i could poss look at editing the aosp rom for you and host if for a bit
just waighting on beeing able to post links :s
Alcatel onetouch c1 pop
MY PHONES flash light or led light comes on but it wont come on at all jus remains black wont start ....i tried restoring rom but ,it was useless ,well i used the upgrade tool and there wasnt the right models for my phone what should i do now .oh and also my phone has no stock rom from nowhere on google im so in need of getting back my phone .how can i fix a bricked or whatever phone its a alcatel one touch pop c1 4015a
What is the online USB firmware updater? Mine is also bricked
hi,
"maybe you saw this post elsewhere but i was forwarded here so the rest is the same"
have elephone p2000 with some custom rom on it and working stock recovery. than i flash new rom called resrom 1.5, rooted BUT internal storage is access denied and 0kb. Just to say that my usb port is broken and will be hard to replace it because someone was trying to make it work and totally screwed up.
So anyway I cannot connect to a pc and fix things. Next, cant access recovery, tried to flash new one but to no avail. I am still rooted but even when using some apk to flash new rom or recovery i get msgs like "not enough space" or nothing is happening.
info on the phone:
ELEPHONE P2000 MT 5692
4.4.2
MOLY.WR8.W1315.MD.WG.MP.V35.P8.2014/11/03
KERNEL 3.4.67 [email protected] #1
BUILD P2000_20150228_RESTORN
Play store ok, calls and the rest is fine, apk i am using: mobileuncle, rashr, auto flasher but nothing gets job done, flashyfy doesn't work and many others. I was looking into init files saw some guide but don t want to mess things even more so i gave up, also wanting to flash boot.img but no proper or functional apk for it.
sometimes on phone start stuck in a loop of screen turn on for 20 sec and then off and its like that until i remove battery, all before rom logo, same thing if i try use buttons combination for recovery or whatever i press in any combination nothing changes.
This is not my first smartphone but is of this kind and funny companies, had problems before with Sony, Samsung but in this extent never, always find YOU guys everybody clever in some fields and as a community more than THE BEST, as you can see i dont post or seek answers by asking, i rather research until now. I fell hopeless, useless and never more stupid, or i m just tired of looking for the answer. In some other case i would give it to my child to play the games an to hell with this phone but its my wife's and she dont want to by a new phone for some reason. Help me to be the man of the house again, kidding, loosing it....
I think I gave you overall picture of the phone state and someone might show me the way to have fully working phone. I forgot, if you are wondering how do i charge battery, well I take it out twice a day and charging on the base of other broken phone, that part i did cover, help me with the rest.
p.s my SD card is working most of the time so this is my only connection to a pc....
Deleted
Hey lovely ladies and gents,
So here is the situation: I have an LG Optimus l70 MS323, which until yesterday was with a stock ROM. I banged my head against the wall, trying desperately to follow a guide and root it, along with trying to unlock the bootloader until I watched a video (in Spanish. Thank you high school spanish!) which used flashify to flash a CWM and boot to the custom recovery. I loved it, since that meant that I would be able to finally flash an official Cyanogenmod OS. The first ROM that I flashed was cm-13.0-20160121-NIGHTLY-w5.zip, which worked and made me feel SO HAPPY (I almost yelled Eurika for the sake of historical comedy). I then went ahead and installed an Superuser-SU binary update through the CWM recovery because I wanted to keep on having root. Then I installed a nano gapps package for ARM, Android 6.0 with some minor complications (mostly the "Setup Wizard" crashing every 2 seconds). I rewiped and reinstalled Cyanogenmod through CWM, flashed gapps on the same go, and made a little backup through the recovery menu. I booted up successfully to be met with that buttery-smooth GUI of Marshmallow (ugh, so good.) I decided to go ahead and fetch some apps from the Play Store, such as Messenger and ROM manager. I saw that the Cyanogenmod Update Center had pushed out a notification that the newest nightly snapshot is already downloaded and decided "Meh. What new features have been added? Let's reboot and reinstall." At that point it was 4:40am (keep in mind that I've been trying to get the goddamn phone to cooperate since ~10pm) and I noticed that the boot sequence takes up a lot longer and told myself "It's probably taking a bit longer than usual, it's normal." I put the phone next to my head, hoping that it's going to be ready to use in the morning.
Fast forward to 8:07 am. Bootloader is still going, phone is so hot it can cook an egg.
GNAAAAAAAAAAAAAAAAAAAHHHH. WHY YOU GOTTA DO DIS TO ME PHONE?!??! WHY!?!
SO, the CURRENT situation:
1. Whenever I press the power button, it starts off normally. According to my definition of bootloop, it's stuck in a bootloop.
After hours of staring that goddamn cyanogenmod mascot do you realize that it's going to boot itself into the booting oblivion.
2. I don't have access to CWM. I have tried holding down the power buttons with godknowswhat combinations (I like to call them the Naruto Jutsu of pure despair). Maybe I should hold the buttons for 2 milliseconds longer and it might work. *Sigh*
3. I don't think that I can use fastbood or adb. My computer doesn't see the phone. (GNAAHHAHASDJFLSKDHFSLJHLKJ.)
4. I am totally clueless about what I should do or try. I've basically softbricked my phone and don't know how to unbrick it.
So, now that you see that saying that I'm frustrated is truly an understatement, what do you suggest I do?
In advance, I'd like to thank you SO MUCH for even giving a sh!t about my problem.
Other misc info: I have a 32GB SD card on which I have all the different tools I have used throughout this journey.
I am willing to have it back on stock ROM. My biggest goal is to somehow boot into CWM recovery. From there on, I will be able to deal with it. Until I come back to this forum, begging for mercy.
Have u tried using LG suite or LGUP u need to go to LG 's firmware page I'm not sure about this phone but it worked w my k7 about 100 times also helped unlock it. Check out the LG k7 forum lots of guys on there that use the lgup program and can help
Hi All,
I have a Huawei Enjoy 7 - Model SLA-LA00 (running Nougat 7.0, EMUI 5.1, Boot is unlocked).
I'd like to root it, but I've tried Kingoroot, King Root, iRoot etc and it repeatedly fails. On checking it seems that my device isn't compatible with those apps. I would like to use the ADB method, but there's no custom recovery image for the SLA-LA00, I've also checked and it seems, there isn't but please correct me if I'm wrong.
Is there a custom recovery available for my model?? Also, I've tried looking but, is there an International firmware for this model??
Any assistance would be appreciated, thanks.
Regards,
marquez010
Hello, was going to create a new thread, but think yours fits what I need to ask aswell.
Same phone here, bought it in Shanghai and now in Brasil, was trying just to make it google able. Salesman at the official Huawei store tricked me to think it would just need access to a open network for it to work. Silly me.
Well, as you, unlocked it with ADB and with no answers from nobody, tried to flash it with a random TWRP. Obviously didn't work. Now the phone wont boot into system, but i still can manage to put it in fastboot mode and it still replies to ADB.
Question is if someone that knows better than me can tell me what to do to at least get back where I was, before I finish killing this damm stupid phone, wich also doesn't seem such bad idea.
lucasresende said:
Hello, was going to create a new thread, but think yours fits what I need to ask aswell.
Same phone here, bought it in Shanghai and now in Brasil, was trying just to make it google able. Salesman at the official Huawei store tricked me to think it would just need access to a open network for it to work. Silly me.
Well, as you, unlocked it with ADB and with no answers from nobody, tried to flash it with a random TWRP. Obviously didn't work. Now the phone wont boot into system, but i still can manage to put it in fastboot mode and it still replies to ADB.
Question is if someone that knows better than me can tell me what to do to at least get back where I was, before I finish killing this damm stupid phone, wich also doesn't seem such bad idea.
Click to expand...
Click to collapse
Hi , all you have here :
https://www.getdroidtips.com/huawei-enjoy-7-b161-nougat/
Hey, thanks a bunch. Found that post before, but it looks like its for an older version of this phone. Mine was running b190 nougat. Don't know if should try to flash this one, but if no other ideas, will try it.
Well, was able to boot it again. Flashed it with yet another twrp that i found for a similar (or so i think) huawei and even tough it didn't work, when I connected the phone to the charger and it responded the power up volume combination and allowed me to reboot normaly.
Guess I'm back to where I started. Think now is better to wait, maybe there wiil be a moe suitable release of a gms core package that it requires for google play to work (have it, but installation fails on rebbot) or twrp updates with a version that works for me and then I can try to install gapps thru it.
Back to my old crappy lg now.