First to all: Hi, im kinda new on Xda and also im new on this phone stuff, but i have i problem i dont know what to do now without going to a shop to fix it.
My problem is this: 2 months ago i got a new phone with 512 ram, it was soo slow but with a good proccesor, i could not use The ram expander because a license issue so i start to root it.
I was experienced before with this.
I tried to root it with many apps... none of them worked, until i found magisk manager, then i found another problem, the stock rom of my phone its not aanywhere, and where is it, its a password protected Zip.
I thing it was over to me, but then i discover an app called "Miracle Box", after 1 week of research of how to do a backup of my rom i finally could do it, i could root it and everything was fine. (By the way thanks to the creators of MagisK)
Then i discover than those Phones came with a malware, my mom has another phone 1Gb ram version and has the same malware.
I discover the malware is inside System ui, or is camuflated like that.
I look it with game guardian, on the proccess list, appear system ui apk, and system ui (assis) when i close by force the system ui apk, Graphic interface reload, but when i kill system ui (Assis) the virus stops inmediatly.
The malware is something called Game Box, popups with ads, weird notificacions, and i discover it uses a lot of internet, A lot.
My plan was of 2Gb, the malware uses 1Gb, when you have no internet the malware is open ut with no ads and notifications.
I discover cleaning data of system ui with lucky patcher and force detention stops the malware for a while.
Then i dont remember what did i do, but one day the phone boot and theres a black screen. No Nova Launcher, no system ui, there were nothing.
So i tried to write the system with miracle box, and after discover always i have to click preloader i finally unbrick it.
Now i have another problem, i tried to Odex system ui with lucky patcher, and there was not classes.dex and because of that the process got stop, and system ui started to stop too.
later on stock recovery of system (Yes, Mtk Droid tools dont recognize my phone, if i have cwm none of this happens.) i realize system ui.odex got deleted, and i am on another Country.
And my dad dont know how to send it because he think miracle box has a trojan because its a paid program.
So my backup its on another Country... and my phone its bricked on a black screen with a message "Unfortunely because you are stupid, system ui stopped and u have a nice brick", i tried to factory reset and that was my worst mistake.
Later i discover miracle box has an option to delete viruses on system folders, so i delete system ui.apk and the phone finally got unstock of that black screen, and it was factory, tere was another problem.
I deleted a lot of apps (most of google) and the phone just says:
Just a sec. And i can pass there, if i dont factory reset maybe i could have a phone without system.ui while my dad comes here.
Then i started for search again for a Twrp reccovery for my phone, and i found 5.
I flash it everyone but none of them worked, and then phone cloud start, but the recovery does not work, then i found a recovery maded to flash on miracle box.
It says Twrp 3.02 for Lava iris, so i tried to flash it with my preloader and my scatter file, it dont work, then i tried to flash it with the scatter and preloader on the folder, and my phone got on a Hard brick.
It dont boot, dont start on recovery, dont charge the battery, is dead, but i think im not ****ed up.
When i connect my phone to computer and press the boot key and then connect the usb cable, the computer recognize it, miracle box does not, but the computer recognize it as a android modem and i think its my last hope, look:
drive.google.com/file/d/1L4Kzac2boQ2fxNW4rYZVEPhFXuvHnqbT/view?usp=sharing
If i change the driver to Mtk Usb device (which is the only compatible) first i have to press the boot key long time (20 secs)
And the computer says the usb is not recognized because the firmware do not gave the requerided resources.
If i keep pressing the boot key the phone started to be recognized for 10 seconds and then its like disconnected, i stop pressing boot key and every 10 seconds the phone (MTK USB DEVICE) appears, if i start writing the flash on miracle box it stops disappearing every 10 seconds and the miracle box start downloading boot, the the app hangs and says this boot its not suported or cpu bad, select another boot, and i dont know what to do, if i manually change the driver again to preloader or mediatek usb, miracle says: Connecting to phone and dont happpens anything.
So these are my problems, because if i get the healthy backup of the phone when my dad comes here, or if i finally get the stock rom, how i flash it?
Another question: if i get official Stock rom, it does not matter if my phone is 512 ram? Because i realize the 1Gb version is same phone, the only diferences i look its the boot animation its a little different and hspa frequency are different, also the other has 1gb ram, its that a problem?
Sorry if my message was too long, but i really need help, im 15 years old, and if my dad look that i dont know how to flash it with my backup... you understand, i dont want to disappoint him, and dont want he to pay a technician.
If you have the Stock rom, or if you have any form to help me how to proceed, please say it to me.
By the way, my phone is An Energizer Energy S500E
Android 6.0
Mtk 6580.
Rooted with MagisK
Bootloader unlocked.
Sorry for my bad english, i hope you give me an answer to procced:laugh:
Related
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
Hello, XDA forumites!
I've been lurking and reading a lot of threads in here for years, using all your knowledge to fix various phones. Today though is the day I first post and it is for good reason. I'm a guy who loves challenges but this one is making me go insane. I've spend the last two days looking for ways to fix this phone but NOTHING works.
So, the deal is that this phone turns on fine. It boots, it gets to the lockscreen and... it restarts itself. Again and again and again until the battery is removed. To fix it, I've tried the following:
- recovering/updating it through the Huawei official "firmware" supplied by the site: you put the file they supply on an SD card, inside a folder named "dload" and then hold vol up and down along with the power button to make the phone install the contents of that file, named UPDATE.APP. Needless to say it doesn't work. A menu appears with the options reboot system now, apply update from sdcard, apply update from cache, wipe/data factory reset, wipe cache partition and calibrate touch screen. Trying to apply update from sdcard only lets me browse the SD looking for the file but doesn't actually see the file itself, it just shows the dload folder empty (I've tried with 4 different versions of the file compatible with phones from Central America which is where I am ATM). Also, the factory reset does nothing (although it shows it wipes data), everything's there when I start the phone up.
- flashing it with SD Flash Tool: apparently partially works with the last version 3 of the tool (although nothing changes) while version 5 of SDFT doesn't even see the phone (drivers are correctly installed, adb detects it, more on this later). A problem that arises is that I can't flash the SEC_RO package on it (don't know why) nor the PRELOADER (not that one is supposed to normally, but I feel like it would fix my problem in this case).
- cleaning it in safe mode: booting it in safe mode made me notice that it was an app pretending to be Whatsapp causing the restarts (or, perhaps, the one that loads immediately after? The phone has several malware apps). In safe mode those apps didn't load so the phone stayed on. So I cleaned everything, activated USB debugging (for later use in adb mode) and restarted only to find everything as it was before I did the cleanup. I tried rooting it in safemode, cleaning again, still reverts to full "normality" after the restart. Same results when using the phone's proprietary SW HiSuite.
- installing CWM's recovery img through adb+fastboot: I installed all the possible - necessary or unnecessary - drivers (Google's, phone's official ones, PDANet ones) and the phone is correctly detected by the PC (visible in Device Manager) and is visible through the adb devices command. But as soon as I adb reboot bootloader it to fastload the CWM image, the phone stops being seen correctly and doesn't show up in fastboot devices, only showing "NEW: SAFE OLD:RISK" on a black background on its screen.
So, to recap: the phone restarts because of a malware at startup, reverts any and all changes made to it in safemode, doesn't wipe from the recovery menu, apparently has a corrupted bootloader and is impervious to normal flashing SW... Anyone got any more ideas on how to deal with it? The only option left that comes to mind is to fix it directly by flashing the internal memory using JTAG/RIFF but I don't have the equipment (nor do I intend to buy it).
Bump, hoping for some help...
One more bump, still stuck
First, don't get happy: I have no answer to your problem. Sorry. But I have a similar one. I was running a very efficient, rooted, stock ROM G730-U251, until I decided to switch from 'Ninjamorph Free' to 'Pro'. I've been made a lot of changes with Free version for a long time without any issues at all. Then, one day, when making a small, useless change with 'Pro', something went wrong; phone just rebooted and refused to get past bootanimation. With no custom recovery on hand, only solution for this is to flash ROM. Though I had no problem finding the official, stock UPDATE.APP, which flashed smoothly from the SD card to be fair. Mess came when, once flashed, I decided to install OTA update available, which I overlooked since phone was new. Big, BIG mistake. It just came with more restrictions than ever, letting me root, yes, but this time with 'Kingroot' only (as stock, I had no problem rooting with Framaroot) but soon discovered I wasn't able to use 'Super-Sume', 'Adaway' and 'Link2SD', because some system parts now CAN'T be mounted rw, even using ES File Explorer. To avoid any complication, decided to reflash UPDATE.APP just as I did before. No way I can do it this time. Don't know exactly why, but assuming it's not possible to update with a previous version of the 'same' ROM. So now I'm looking for a flashable stock ROM in order to try SP flash tool. Phone is in working state right now (not as yours), but I just don't feel comfortable with it as it is right now, because those apps are always the main reason why I actually root every single of my devices and simply because I like to have my stuff as my own way as possible. You know, truth is there's not much of an advanced support for this phone, not even here at XDA and I think that's because this is a Latin America version. We owners of G730-U251 devices are pretty much on our own, to say the least. Whatever, if the whole deal gets more complicated than it is, there's a strong possibility for me to end up getting rid of this phone. Sad. Really. It's actually a good phone. Though it WAS better...
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
iamnekro said:
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
Click to expand...
Click to collapse
What you read in the internet means re-flashing your stock rom (system), that is the fix for your problem, the way to do it is to download and install Samsung USB drivers if you hadn't done that already, and Download stock rom from here or here search your model number in the search box and choose the stock rom based on your country, and flash with Odin, it's pretty much the same way you tried to root using CF-ROOT method:
1-you boot into download mode (volume down + home button + power button)
2-and then connect your phone to PC.
3-open Odin and uncheck everything except "auto reboot" and "F. Reset Time" (you should find it like that already), make sure your phone is recognized by Odin, you will see a blue box with a message saying "0:[COMX]" where X is a number.
4-press AP (or PDA in some versions) locate your stock rom which should be in .md5 format, and choose it, then 5-press start.
6-wait for the process to finish (takes a while) and then the phone should reboot itself and you will get a message in Odin saying "Reset!"
PS: you must register on the sites to download..bad thing i know but it's obligation.
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
iamnekro said:
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
Click to expand...
Click to collapse
Give me your model number.
Sorry found it in the thread title
@iamnekro
That is the link from the first site:
SM-T337T latest firmware android 5.1.1
That is the link from the second site:
SM-T337T latest firmware android 5.1.1
Obviously you didn't search at all...LOL
PS: It's called Stock Firmware or Stock ROM.... not Drivers
Register on any of the sites first to download.
And press the thanks button please
Regards Migo
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
iamnekro said:
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
Click to expand...
Click to collapse
It doesn't need any advanced computer and only the size of the stock rom and Odin, it's no big deal.
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.
I've tried so many times here to get at least a response... Perhaps devs at xda have finally realised, goole are defo creating problems.
I know my stuff, I've flashed hundreds of android phones and tablets, but never have I seen solving a problem, and providing solutions disappear so fast.. Android 10 sux. Random macs destroy firewall security... but hey..
Tried so many times to flash the Armour x5, and know how to use all flash tools. Restored to origional provided rom, but imei was wrong, and got the GoogleKeyState: Fail, used sn write tool to do imei, worked.
So in testing, Imei went back to incorrect one, reflash origional firmware again, only this time, TEE PL error -3, now, I cant use serial writer to do anything, it wont write, yet all in testing is 'normal'
At no point have I messed with anything other than trying to put twrp on this phone, and always extracted a fresh firmware to flash when not happy with tests. To date I have yet to place a sim in this brand new phone.
seems we can do what we want until they get a wiff of our hacks, then they block them.
So yup I'm asking help to root my android 10 Armour x5, I'm testing, but no-one else seems to wanna input anymore, anyone wanna help me help them?
Well, finally managed to get rid of the GoogleKeyState: Fail, as well as correcting the imei's, a rather long drawn out process when no-one knows what they're doing anymore, I guess ya just got to love the old time hackers huh?
To be rid of big red GoogleKeySTate: Fail
Load up SNWrier_1828-4.0.0-vturkey select attestation file, found in extracted firmware, the google folder, select google attest key, make sure all else is unchecked then write, succesfull, gets rid of the big red ****.
Changing imei:
Tried with bootloader locked, then bootloader unlocked...
Using SNWrier_1828-4.0.0-vturkey: Looked like it wrote, got the green tick, upon rebooting phone, wrong imei's were still there, it did not write succesfully. Same with serial numbers.
Used Maui Meta build 9.1724.0.00, on left, select imei download, read from device, (1st box on left) only input the first 14 digits of your 15 digit imei, the last digit of each imei is the checksum, and loads automatically (if you dont increment macs) hit write, shut down the app gracefully, it turns fone off, upon restart, imei was fixed.
Thanks for the lack of help all you experienced folks waiting on us less qualified to wreck our fones so you can profit by reading how we did what..
I got more help from lesser site's..
Not bumping old threads, just keeping at least one up to date with my ever so slow progress..
Still no joy finding any twrp for this fone, but I did find out how to remove all the forced bloatware on the fone, by doing:
pm uninstall --user 0 com.google.android.apps.wellbeing
...and on and on till i got rid of it all, showing you dont need root to remove the apps that are locked to all apk's... surely this 'PM' can be used to grant access to su somehow? I know it can grant, but I know nothing of this layout in 10_Q, even after reading so much crap from others who clearly have as much a clue as I do... and they write apps lol...
I also managed to change the firmware, I swapped Android_10_Q and managed to load the firmware for the x5 PRO, a different fone, different firmware, yet it loaded, and worked 100%, but I went back to the 10_q in order to figure out more, as the pro had way more partitions, and there was NO system viewable compared to the 10_q, which at least can be grep'd.
As for the big red googlekeystate:fail, dont flash preloader when flashing anything! When I flashed the pro android over 10_q, I flashed the preloader of pro and it bricked the fone... I had to wait until fone was out of power before I could load up the writer to reflash 10_q, had to redo the macs and serial, which incidently, for those not knowing, BARCODE is the serial number if you need to revert to stock mac n serial using attestation key. Flashed Pro again and then back to 10_q without causing big red crap by not flashing preloader!!
Now as for those numpties that cant decide if we are using A/B or A only partitions, dont write apps if you cant get it right, your sacked?! One look at the preloader when loaded in SP Flash Tool clearly shows 2 boot sections!!!!!!! Treble checker does what? Lie and cause so many headaches...
Now if i had a twrp for either 10_Q or Pro variant of the ulefone armour x5....