PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v215 tested by and boots fine.
https://github.com/phhusson/treble_experimentations/releases
Things to consider
WHAT WORKS:
audio -music and speaker phone
camera-front and back (yes pop-up camera works)
video-camera front and back
video playback --(tested youtube in browser) - recorded video playback
Phone calls
messages
auto rotate
brightness
wifi tethering
mtp
flashlight
lift to wake (needed to turn off then on to activate it)
adaptive brightness
dark theme
gps
WHAT DOESN'T:
--Fingerprint
--phone works/ but dialer app has message that device is unsupported
--off-mode charging -- when charging with phone off, bootloader logo screen stays on, instead of battery icon
--screen recording-- after enable dev option // feature flag // settings_screenrecord_long_press .. you can access
screen record from long press power menu, long press screenshot menu, but recording will not save or stop
recording.-- setting option to on does not survive reboot
-- screen shot -- taking screen shot forces a bug report creation. (maybe this is not an issue, only a setting)
.
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Sergeantslaughter said:
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Click to expand...
Click to collapse
our device does not have VBmeta
the directions that say flash VBMETA, say use the stock meta file from stock firmware. so because that file is not used here, this is why you get the error message, ......
actually from your command you did not tell fastboot the location of the file you are trying to flash Unless you have a file called "vbmeta.img" in the current command terminal location. But again back to my original statement, our device does not have this file, so IF you do have the file, it is from other device anyway.
I guess I see how to flash the gsi but how do I get twrp installed?
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
only one permission file needed to be added. This is also expected to be included in the next release anyway.
Need to be fully stock
--boot
--vendor
--recovery
fastboot flash system **GSI.IMG**
fastboot oem reboot recovery
perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
tested version was AOSP 10.0 v201
V203 boots without having to add the extra permission XML file.
Current version v204 not tested yet.
https://github.com/phhusson/treble_experimentations/releases
additional step to get version lower than v203 to boot
Download the additional permission file from
https://github.com/phhusson/device_...0.0/privapp-permissions-me.phh.treble.app.xml
While system is on boot animation screen. (this is as far as it will go on its own)
After the adb push, for me at least, the phone starts to continue its boot operation. Still do the reboot anyway.
Click to expand...
Click to collapse
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Sergeantslaughter said:
I guess I see how to flash the gsi but how do I get twrp installed?
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Click to expand...
Click to collapse
I have not been using twrp with GSI, but if you want to try goto twrp thread. Note that the twrp is currently only working with adb command line interface. No touch screen activity.
start by looking at the threads here. You will find twrp thread there.
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Sergeantslaughter said:
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Click to expand...
Click to collapse
aosp has root built in. If you prefer majisk, you need to first remove the included -su, and then need to use PHH-Majisk, not standard version.
Information on that should be found in gsi thread. It is not device specific.
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Sergeantslaughter said:
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Click to expand...
Click to collapse
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
mrmazak said:
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
will that work? i cant get my phone to power on at all and adb is not recognizing it...
mrmazak said:
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
That repeating sound is sign of bootloop.
Spflash tool is the recommended repair tool.
Download the factory restore package,
Extract the downloaded file.
Open flashtool, select scatter file from the extracted download. Ensure tool is on "download only" mode
Clear all select boxes in the tool window. Put check only in the recovery line.
Press download button, plug USB into phone. The bootloop in the phone is enough to make connection start.
What twrp did you use, where did it come from. Did you verify md5 of the downloaded file.
The only twrp I found was the one I shared, and it did not cause that kind of issue for me. So maybe you did something that you didn't mention?
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Sergeantslaughter said:
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Click to expand...
Click to collapse
Oh, last step is unplug USB. Then long press power button.
10 second should do. But maybe 20
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
Same happened to me, ended up fixing issue by using spflah tool (latest) and updated stock rom (mrmazak posted it) ?
I haven't bought the N1 yet but just might thanks to @mrmazak testing! Anyone tried Q v204 yet? Also curious if PHH regular Pie is bug free.
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v204 not tested by me yet.
https://github.com/phhusson/treble_experimentations/releases
Click to expand...
Click to collapse
Do not tell me in v 203 which version to download? I tried several but all to no avail
elephone p8000
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Sergeantslaughter said:
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Click to expand...
Click to collapse
Elephone p8000 is at least 3 years old. And would not think twrp from it will work on your bold n1.
As for why your PC shows your bold n1 as different phone, I can only guess that your PC drivers are somehow modified.
Or your phone is maybe not stock?
Related
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Download mfastboot and redownload the recovery img
hetor99 said:
Download mfastboot and redownload the recovery img
Click to expand...
Click to collapse
Thanks.
Decided to install it on my desktop. While trying various files, my laptop accidentally got hit with Chromium virus. It looked like all required files were there, but kept having problems with a couple of those sdk files (tools/platform tools).
I'm still getting the following error:
( bootloader) has-slot :recovery: not found
And once again the Android SDK Tools and Android SKD Platform-tools that are under Tools (preview channel) are unchecked. Not sure if they are needed.
Follow the instructions of how to install on the general section
hetor99 said:
Follow the instructions of how to install on the general section
Click to expand...
Click to collapse
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
L8Show said:
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
Click to expand...
Click to collapse
How to Install TWRP Recovery and Root MOTO E
https://www.youtube.com/watch?v=9Jh-O2LGL3Y
OK, it is done.
Took a couple days with several hours of clicking, and checking settings, and reading and researching, and watching videos, and downloading, and installing/uninstalling, and restarting, but it's now rooted! Way too much time wasted even though it was raining and the gf and I were just watching movies for a lot of it. She kept asking me why I'd waste so much time and remind me I had a perfectly fine iphone nearby. Today I finally got to the point where I had given up. I figured something was screwed up with the phone after that reset on my computer.
Some highlights that may or may not be helpful for the next moto e rooter:
USB debugging was somehow switched to off a few times after I turned it on. Might have been after resetting phone, but who knows exactly.
I set screen to stay while connected via USB.
I removed all the apps I could and took out the sd card.
Kingoroot stuck at 66% many, many times, and then phone would restart. Research showed it may be accessing the wrong ADB instance or something. So I uninstalled SDK, fastboot, Minimal, etc. Anywhere it could have been hiding. Even did a system restore to last week the day I reinstalled windows. Didn't help one bit. Which is to also say... there are a half dozen or more legit options. Try different ones if you are relatively confident you followed directions the 1st 10 times.
Ministro didn't have moto e in their data base.
Finally back to XDA after checking a dozen videos (I have to admit I was completely dumbfounded and was mad at the whole process). I found XDA Kingroot and right away it worked, but it needed permission to allow apps that were not certified or some thing. I can see how people would think this is so easy. If I had started with this, I'd never have had to ask for help here. Btw, was this my problem all along? Did I miss that in the instructions or was it something else possibly? I don't remember if I did that before since it was 3 days ago.
So far I am thoroughly impressed with the this moto e. I paid $40 for it on a whim and now that I can remove a bunch of bloatware and customize it a bit, I think it may be a good gateway into android devices.
Thanks for looking and all your suggestions.
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
faheyd said:
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
Click to expand...
Click to collapse
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
L8Show said:
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
Click to expand...
Click to collapse
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
-z3r0- said:
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
Click to expand...
Click to collapse
Thanks for that information. I thought I saw adb devices command working in fastboot mode in one of the videos so I thought that was the problem. I thought adb needed to root the phone.
In order of what I've done with the phone so far:
Sent/got codes and unlocked moto e.
Turned on developer options and USB debugging.
Was then unable to get TWRP or the other cw something to work using the command fastboot flash recovery (file name) or fastboot boot... commands.
Gave up and installed Kingroot and everything worked fine.
Decided to try to install TWRP and superSU since kingroot had worked. I read that the phone needed to be flashed back to stock to do this and watched/read a couple of guides. http://forum.xda-developers.com/showthread.php?t=2759495
I used the following named file:
SURNIA_ACG_LTE_5.1_LPI23.29-30_cid9_subsidy-DEFAULT_CFC
The phone was changed back, but data doesn't work. I can't access wifi because as soon as I switch it on, it switches back off. 4G, etc is not working either. So after trying to figure that out I decided to just proceed and put TWRP/superSU on the phone.
I powered off the phone. Powered into fastboot mode connected the phone to my computer.
I opened Minimal fastboot folder and shift/right click to bring up the command prompt.
In the command promt i typed fastboot devices and it shows my phone.
I then type fastboot flash recovery (file name or renamed to recovery or renamed to TWRP or I click the actual file and drag it to the command prompt) and then hit enter.
It says it's doing stuff in so many seconds, but after nothing happens. The phone doesn't reset like some of the videos. If I reset it, it powers on, but not into the TWRP screen.
After that I did more reading and found out that adb doesn't always play nice with windows 8.1 and that you might need to force other drivers to make it work right. I did this next and was going to try all the available options from universal naked driver later, but there were no motorola drivers.
Then I came here and learned something new. ADB devices command doesn't work when the phone is in fastboot mode so that has no effect on installing twrp...
Right now I am considering trying to install the other stock files I have access to:
SURNIA_ACG_LTE_5.1_LPI23.29-20_cid9_subsidy-DEFAULT_CFC (20 instead of 30).
After that I am out of ideas if it's not the adb problem. Might kingroot again and go from there.
Ok after researching, it seems that LTE file may not work on sprint and there was success using the boost file from
http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
(2 hour dl make that 5+ lol)
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'll try that next to get the wifi working and then figure out why it won't root.
Thx!
L8Show said:
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Click to expand...
Click to collapse
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
rakeshwipr said:
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
Click to expand...
Click to collapse
and open the command prompt with admin rights
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
d
Thanks! The devices shows up when on as ADB and in fastboot too. I had to take a break when the kernel download took 8 hours, but I think I got the file that will work to fix the wifi issue. I can't mess with it til I get home tomorrow, but I will read and follow all advice.
For the previous poster, I did do the admin rights and did rename TWRP file to recovery... I aslo tried many other combinations, but will keep it in mind for all further attempts.
Appreciate the help so far. I almost left it with the kingroot, but it was bugging me that I couldn't get it to go. Hopefully I'll have good new tomorrow.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
Device shows up in both instances.
It's stock now and the wifi works. Flashed it back to stock by following Mdkcheatz guide here:
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'm stuck where I was when I first started this thread. I've set my account up as administrator. Developer is enabled and so is USB debugging. I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
I confirmed the connection:
fastboot devices
I try to flash it with the:
fastboot flash recovery recovery.img
It says:
target reported max download size of 268435456 bytes
sending 'recovery' (6928 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.359s]
finished total time: 0.578s
C: |Program Files (x86)\Minial ADB and Fastboot>
I'm running windows 8.1 (64 bit). I read that some people had had problems with windows 8. Kingroot worked through the app store. It has been flashed with various stock kernels and that usually takes a few minutes so I don't think it's doing much in half a second. I'll research a bit more, but I think it just a bad combination of this version phone and windows 8.1.
I started the phone after this last attempt. Are there any files in internal storage that I should look for?
L8Show said:
I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
Click to expand...
Click to collapse
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
-z3r0- said:
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
Click to expand...
Click to collapse
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
L8Show said:
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
Click to expand...
Click to collapse
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
-z3r0- said:
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
I am on v2.65. Should I use this version? I checked root and it's rooted, but I needed to use no bloat app (instead of free titanium) to remove some apps. Is that normal? I thought once rooted and set up, I would have complete control. Some apps seem very invasive so I haven't grabbed many yet. I have some questions about apps, etc., but will probably research and ask in another forum if needed.
Thx again for all the help and pointing out my mistake.
I did everything that was stated in the how to's but to no avail. additionally i cant get TWRP installed via fatboot, i have checked and crosschecked usb debugging and unlock OEM , but i cant get it to work , with SP Flash my phone pops up and vanishes in the hardware manager withing fractions of a second so it doesnt work with the sp Flash , in fastboot it wont let me download to recovery even if i use the command line oem unlock , because the volume up button that you have to use to accept[yes] doesnt work , only the vol down[no ] button has an effect, anyone any ideas anyone?
?
Kylekassar said:
I did everything that was stated in the how to's but to no avail. additionally i cant get TWRP installed via fatboot, i have checked and crosschecked usb debugging and unlock OEM , but i cant get it to work , with SP Flash my phone pops up and vanishes in the hardware manager withing fractions of a second so it doesnt work with the sp Flash , in fastboot it wont let me download to recovery even if i use the command line oem unlock , because the volume up button that you have to use to accept[yes] doesnt work , only the vol down[no ] button has an effect, anyone any ideas anyone?
?
Click to expand...
Click to collapse
To use SP Flash tools, turn the phone off, press download on the software then plug the phone in. The preloader is only meant to show for a short time (a fraction of a second to a few seconds) so SPFT needs to be sending the signal to download in that time window.
What I've also found works is to press download on SPFT then press and hold power and volume up until the device starts downloading.
thx for the quick answer i will try a.s.a.p.
Kylekassar said:
thx for the quick answer i will try a.s.a.p.
Click to expand...
Click to collapse
Tried but it doesnt work , i starts the dload but then i end up on brom error : STATUS_PRELOADER_INVALID(0xC0030004) no recovery flashed
Kylekassar said:
Tried but it doesnt work , i starts the dload but then i end up on brom error : STATUS_PRELOADER_INVALID(0xC0030004) no recovery flashed
Click to expand...
Click to collapse
That could be a couple of things:
Which SPFT version are you using? If its an older version try using a newer one.
Or
The scatter file you loaded is not good, download a stock firmware and use the scatter file from that.
Try this:
fastboot flash recovery "filename".img
or
fastboot flash boot "filename".img
Do you have the MTK drivers installed? What does your phone appear as in the Device Manager? Like others have said, once you've chosen your scatter file and recovery to flash, hit download and then plug in the phone.
Managed to fix this? I have the exact same problem and not able to fix it till now....
I'm in a similar situation. I CAN get my phone to flash recovery in SPFT and get a lovely big green tick but when I power off and boot into recovery using power and volume up it boots into the stock android recovery rather than TWRP.
Going another way via ADB, I can get the phone detected but when I send the OEM unlock bootloader command I am unable to use volume up to confirm. Only the volume down key works to cancel.
All I want is to put viper4android on. Never had any issues until this phone.
chandlerp said:
I'm in a similar situation. I CAN get my phone to flash recovery in SPFT and get a lovely big green tick but when I power off and boot into recovery using power and volume up it boots into the stock android recovery rather than TWRP.
Going another way via ADB, I can get the phone detected but when I send the OEM unlock bootloader command I am unable to use volume up to confirm. Only the volume down key works to cancel.
All I want is to put viper4android on. Never had any issues until this phone.
Click to expand...
Click to collapse
Are you 100% sure the recovery.img you flashed was TWRP?
Absolutely. Downloaded from this very site. It was this one: recovery_TWRP_3021_P9000.img
---------- Post added at 02:23 PM ---------- Previous post was at 02:17 PM ----------
Did an OTA update this morning and am showing as on build number Elephone_P9000_20160608 now. Haven't tried flashing since the update as I'm at work with locked down computers. Was going to try again over the weekend. Which recovery and version of flash tools would you recommend trying this time?
thanks for any advice.
Actually I have the same problem.
I tried to reinstall the drivers because it seems to be not the correct one. Here is a pic: i.imgur.com/FoUnVyz.png
After I read somewhere that i can try and hold down Volume+ while connecting my phone to the pc where i started the download in sp tools prior.
I got this error code: STATUS_PRELOADER_INVALID(0xC0030004)
And here I am with a not-up-to-date elephone p9000.
Anybody care to help me?
I'm in the same situation, tried everything - flashtool recovery.img separate in download mode, flashtool in update mode full 7.0 with replaced original recovery.img with TWRP one, played with fastboot with no luck as did not find the way to OEM UNLOCK it - vol + not reacting. Bought the phone on Gearbest, looks like it's locked very hard.
Can't install TWRP
Me too! I've updated my p9000 to latest stock v7 rom with spft. I can't install twrp recovery despite getting a geen tick from spft. Tried four times but it won't overwrite the stock rom recovery. A locked bootloader seems to be the popular diagnosis but spft doesn't use the bootloader. What else could it be? Ideas very welcome.
Did you boot into recovery immediately after flashing? A normal system boot will overwrite TWRP with the stock recovery. Once you start TWRP there is an option to prevent this from happening.
Can't install TWRP
Thanks for the suggestion. I flashed twrp again but it won't boot into recovery afterwards without a restart, just hangs. Stiĺl on stock recovery.
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step
lets get to it
place the magisk.apk and the stock boot.img
in the internal memory of your phone (downloads)
if you like to keep stuff organized :good:
3-step
follow the vídeo tutorial and use magisk manager
to patch your stock boot.img it will output a new
boot.img that includes magisk Root (patched_boot.img)
https://www.youtube.com/watch?v=BF4_hnKgjFA
ps: major ty to hovatek team for this great tutorial
step-4 use Google drive or usb OTG to get the patched_
boot.img to your PC and place it in the ADB folder
once you have oem(bootloader) unlocked just
rename the patched_boot.img to boot.img
step-5
unlock oem, these qilive devices wont unlock
the bootloader even if you enable it in DEV options
enable USB debug in dev options
you will need to use ADB commands
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot oem unlock
(MAJOR WARNING the fastboot
oem unlock will wipe/reset/factoryreset/delete your data)
after you give the command small letters will appear
on the phone screen(yes or no) hard to read dont be hasty plz
use VOLUME+ to select and VOLUME - to confirm
note: when my phone ended the unlock it whent back to
that black screen where you choose fastboot-recovery-restart
and was stuck there, side keys did nothing if this happens
just long press the power key for 10 sec it will shutdown
then press power again to turn on
first boot after unlock will take longer then normal dont freakout
after you unlock small letters will appear during boot up saying the device
is not safe unlocked ,you can later use ( fastboot oem lock )
step-6
flash the patched boot.img with ADB
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot flash boot boot.img
finished/ok
command- fastboot reboot
and voila you should now have magisk
installed in the app drawer, open it!!
step-7 run the install one final time from the
magisk manager and install magisk V16 using
recomended option it will verify/patch the boot image
Do NOT select the AVB 2.0 BOX it will bootloop the phone
and your done, enjoy your qilive rooted phone.
from this point on you can use the fastboot
command- fastboot oem lock
to remove the letters in boot up about the
device not safe unlocked
WARNING oem lock
will WIPE/FACTORY RESET again (god damn it!!)
ps: i had to install twice in a row,major pain in the ....
Repeat step 7 after Wipe/Reset
here is the stock boot for 2 qilive models
you can get the stock firmware for any qilive
at this site www.doc-doapi.com/EM/qilive/smartph...te_3m-fdd-cs_mul_20170818-110645_songlixin_PC
and get the recovery or boot from the unpacked firmware file
ps:my phone is the Q8SIN4GP AND ITS WORKING FINE
A VERY SPECIAL TY to topjohnwu (magisk creator), this man is nothing
short of a God damn genius!! , and if you can donate to him.
hope this helps other qilive users to root:highfive:
quick note on the qilive models, they have two model names
the cliente name in my case Q8SIN4GP
and the factory name in my model its 882912
in order to download the right firmware for your model
you need the factory model witch is what appears in the qilive
site above, it will be in the back of the phone or the original
box on a sticker just bellow the bar code, full model exempl
:Q8SIN4GP/882912 my firmware serves several models,
these Q8 models all start with 88xxxx WARNING
dont try this using the wrong firmware/boot file or you will DAMAGE your phone
Help with BOOTLOOP problems, if you find your self stuck in a bootloop
the phone wont go past the qilive logo and just stays there, dont freak out
you will loose your data but there is a way out
just keep pressing power + Volume up until a black screen with 3 options appears
when it does let go, use Volume + to select option and Volume - to confirm
select Fastboot or alternative select recovery and then select reboot to bootloader
both option will place your phone in Fastboot mode, once in fastboot mode
connect your phone to PC and use ADB commands to fix/bootloop
command- fastboot devices
serial appears
command- fastboot oem unlock (skip this if you use phone unlocked)
a confirm action option appears on the phones screen
use Volume up to say YES / or Volume Down to say NO
Warning oem unlock will WIPE/Factory reset your phone
once it finishes the phone will be stuck on the
Recovery/fastboot/restart screen just long press the power key
until the phone shuts down
start the phone again using Power + Volume up when the black
screen with the 3 options come up, let go and use Volume up to
select Fastboot mode and confirm using Volume Down
Once in fastboot connect your phone to PC and use ADB commands
command- fastboot devices
serial apears
Here you will flash the magisk patched_boot.img
the same image you used to root your phone
command- fastboot flash boot boot.img
it will say finished-ok (or similar)
command- fastboot reboot
the boot up time will be longer than normal
but the phone should now complete the boot
and present the inicial setup screen, select language
enter your mail, the usual bla bla...
any way at this point just repeat step 7
to get root running again
sp flash tools v5.1716.
phonedriller said:
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step....
Click to expand...
Click to collapse
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
Awsome work congrats, as for the recovery so far no luck so try not to go 2 crazy until a working recovery is up and working , install stericsons busy box this is always the first root app i install
If possible buy sterics busybox pro and titaniumbackup pro if you want to install apps to sd card apps2sd pro all of these can be tested in free
Version,again nice work congrats enjoy you rooted phone :highfive:
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
phonedriller said:
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
Click to expand...
Click to collapse
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
xdacktheresianum said:
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
Click to expand...
Click to collapse
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
phonedriller said:
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
Click to expand...
Click to collapse
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
xdacktheresianum said:
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
phonedriller said:
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
Click to expand...
Click to collapse
thank you, phonedriller
everything worked perfectly via SPFlash Tool.
and, referring back to our above questions re the possibility of getting TWRP onto the phones, a developer friend of mine writes me this:
>try to flash TWRP:
>Download following files from this link:
>https://mega.nz/#F!qZIgnJRK!5apBfYo1je0ytg-wmA6JMQ
>- Odin3 v3.12.3 (Complete folder)
>- twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>1. Start your Phone into download mode
>2. Start Odin (Odin3 v3.12.3\Odin3.exe)
>3. Click on Options and unmark Auto Reboot
>4. Click AP and select twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>5. Press Start and wait until finished (Reset or OK!)
>6. Restart your phone immediatly to recovery mode
>7. In TWRP Recovery click on mount
>8. Set the checkbox checked at system (that system is mounted)
>9. go back and click on advanced
>10. Open file manager
>11. navigate to system/build.prop and click on build.prop
>12. Click on chmod
>13. type: 0644 and hit the accept button on screen or at the virtual
>keyboard on your phone
>14. restart your phone
i haven't tried this, but am wondering whether it might seem "reasonably possible" when reading through it.
thanks
ckth
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
tommo1982 said:
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
Click to expand...
Click to collapse
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
I had issues with adds being displayed at home screen and I was not able to close them. I had to use NetGuard to find that FOTA talks to 'adsup' and it is a known malware provider. I learned that some of the system apps try to talk with Alibaba servers and AdOppo (whatever it's called). Kaspersky might not be wrong, actually.
I'm trying to download stock firmware, but I don't know the file name. The website with it is locked, so unless I know exactly what I need, I cannot download it.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
phonedriller said:
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
Click to expand...
Click to collapse
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
Ps use root + apps2sd or titaniumbackup to stop/disable the bad apps and replace them with playS app,not possible on all apps of course
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
tommo1982 said:
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
Click to expand...
Click to collapse
Flashing is super easy use spflashtools or. Odin compiling a Rom is not , were you able to get the original firmware? You will need the original firware to get the boot and partition info from what i read so far
Unfortunately not. I will ask at the shop where I bought it how to contact tech. It should be freely available. I don't understand why Qilive restricted access to firmware.
I'll post when I learn anything.
Well, you can download the firmware if you know the file name. The bad news is, it seems the stock firmware has malware preinstalled. If there is anyone who could help confirm it. I have the ROM, and I can upload it to Google Drive if needed.
Hi all,
I'm coming back to a question lingering since the very first post here and mentioned again in post #9:
Is there a successful way to install TWRP on this Qilive model?
Re this topic:
- has anybody tried/has anybody been successful with the procedure described in post #9?
and
- has anybody seen the following TWRP builders' version (do an in-page search on Q8S55IN4G2)
https://twrpbuilder.github.io/fr/downloads/twrp/
with the download belonging to it
https://androidfilehost.com/?fid=890129502657591798
???
any successful installations to report???
Wouldn't THAT be great!!??
thanks
xdack
Hi...
I try to root my FL02 (ALCATEL FLASH PLUS 2) every thing goes perfect and i get ORANGE STATUS but at the last step when trying to flash the rom with TWRP it could not read the SD card and system folder isn't abel to wipe so i try to repeat steps again.
first flasing in the video done and mobile restarting. no logo on screen and it doesnt boot and cannt go in boot mode or fastboot mode.
it connect and disconnect with PC but i still can connect it to flashing programme and i can send flash from PC but it doesnt boot and nothing appear on the screen.
any help....
Phone : FLASH PLUS 2
N D1M N7KE 03 TJZ
ANDROID 6.0
I follow this video to root
youtube.com/watch?v=d8zPGPJ_uZY
EFAYSAL said:
Hi...
I try to root my FL02 (ALCATEL FLASH PLUS 2) every thing goes perfect and i get ORANGE STATUS but at the last step when trying to flash the rom with TWRP it could not read the SD card and system folder isn't abel to wipe so i try to repeat steps again.
first flasing in the video done and mobile restarting. no logo on screen and it doesnt boot and cannt go in boot mode or fastboot mode.
it connect and disconnect with PC but i still can connect it to flashing programme and i can send flash from PC but it doesnt boot and nothing appear on the screen.
any help....
Phone : FLASH PLUS 2
N D1M N7KE 03 TJZ
ANDROID 6.0
I follow this video to root
youtube.com/watch?v=d8zPGPJ_uZY
Click to expand...
Click to collapse
Ok, tell me to can help you;
Do you have TWRP installed?
Do you unlock bootloader succesfully?
In which modes you can enter? fastboot, recovery, download (do detects SPFlash Tool?)
SubwayChamp said:
Ok, tell me to can help you;
Do you have TWRP installed?
Do you unlock bootloader succesfully?
In which modes you can enter? fastboot, recovery, download (do detects SPFlash Tool?)
Click to expand...
Click to collapse
Thank you SubwayChamp for help.
No , TWRP is not installed now .
Yes, I think bootloader has been unlocked. It is done with Orange status.
I think it is in download mode. it detects SPFlash.
EFAYSAL said:
Thank you SubwayChamp for help.
No , TWRP is not installed now .
Yes, I think bootloader has been unlocked. It is done with Orange status.
I think it is in download mode. it detects SPFlash.
Click to expand...
Click to collapse
Ok, I guess that your device is actually in bootloop and don´t booting.
Tutorial that you followed has many steps and don´t need to do all this to just root device and it contains some files like lk.bin that you can´t be sure that should be for your device.
Some users use this file (lk.bin) of an unlocked device and think that flashng in other device then get unlock it but no need, your device can be unlock it just follow some commands in fastboot mode.
Now you can do the next;
Try to flash again your rom stock (I guess that you don´t have a backup), if for some reason your official tool doesn´t work then use only some images like boot, system and userdata with the scatter.txt to flash them through SP Flash Tool.
Here a link to TWRP https://youtu.be/6vj_BY6xJdA, you can root it with supersu v2.78 0r v2.82 and here some files that can be usefull too https://drive.google.com/uc?id=0BwJgeCYTpnEHNlg2VUlieHFTYVU&export=download
Update steps that you are following to can assist. What extension has your rom and if it is recogniced for SP Flash Tool. I didn´t ask you if you can enter to fastboot mode and if you can then you can know if your bootloader is unlocked typing fastboot oem info
Most info that you give and some screenie will help to understand better
Unfortunatly, it can not enter to fastboot or recovery mode. Those files in replay didn't work and i dont have a backup. I try to flash recovery.img, system.img and preloader_shine_plus.bin . All done but it still black screen and does not boot. But now it connect to Pc without disconect .
I cant add link or images to my post.
EFAYSAL said:
Unfortunatly, it can not enter to fastboot or recovery mode. Those files in replay didn't work and i dont have a backup. I try to flash recovery.img, system.img and preloader_shine_plus.bin . All done but it still black screen and does not boot. But now it connect to Pc without disconect .
I cant add link or images to my post.
Click to expand...
Click to collapse
Gmail didn´t warn myself about your post. Did you solve it?
You said that flashed recovery, system and preloader but how, through SPFlashTool?, if yes, are you sure that this tool recogniced your device?
You forgot to flash boot.img too.
Other way to try; flash only preloader.bin and then try flashing boot, system and userdata that are the three most important partitions to can boot.
Like last resort you can do a Format all + flash but only like last.
SubwayChamp said:
Gmail didn´t warn myself about your post. Did you solve it?
You said that flashed recovery, system and preloader but how, through SPFlashTool?, if yes, are you sure that this tool recogniced your device?
You forgot to flash boot.img too.
Other way to try; flash only preloader.bin and then try flashing boot, system and userdata that are the three most important partitions to can boot.
Like last resort you can do a Format all + flash but only like last.
Click to expand...
Click to collapse
first of all thank you for your help. I was busy last week .
Yes it was with SPFlash and it is show MT6775 when mobile connect . but if i try flashing boot it gives an erorr and cant flashing.
I think i have a wrong boot file.
I miss userdata file.
Do you know where can i download necessary files for this model?
I apologize for delaying. It is time for school examin
EFAYSAL said:
first of all thank you for your help. I was busy last week .
Yes it was with SPFlash and it is show MT6775 when mobile connect . but if i try flashing boot it gives an erorr and cant flashing.
I think i have a wrong boot file.
I miss userdata file.
Do you know where can i download necessary files for this model?
I apologize for delaying. It is time for school examin
Click to expand...
Click to collapse
I´m not sure if you are connecting correctly your device at right time and form to can flash it properly. Every device has more or less a specific way to do it. My last alcatel it was connected just with device power off and after to tap on download, but in other device Blu Dash was connected pressing just vol_up and my last mt6757 Bluboo had to press both vol up and down at time to connect to pc and after to tap on download option. To have sure that is well done increase volume in your pc, you will hear a first sound that is cause pc is recognicing but then you have to hear a second sound that is when SPFlashTool is recognicing device and you will see a red line in down side of the tool window, release button inmediately and let tool to work.
This is a good rom for your device according the author is optimized https://droid1311.blogspot.com/2017/08/alcatel-fl02-aka-flash-plus-2-via.html and this is the link directly if you have troubles with pop-up-adds https://drive.google.com/file/d/0BwAGh1drb91SeDZwV1VXbXpjQWM/view
Also you can try with other versions of SP Flash Tool, most stable maybe should be v5,1628 https://androidmtk.com/smart-phone-flash-tool leth me know how you go
If I understant, the status bar has to be red then I will release the mobile button and click download in SPFlashTool.
SPFlashTool 5.1628:
I try all the way with and without pressing any button but no luck . And when it work finishing with error.
SPFlashTool 5.1628:
I try all the way to get that mode but nothing works. So I try to click download button then conect the phone by random buttons and every time i get red color , yellow , green ,purple , yellow (for many times 100%)
then i get this error:
ERR: STATUS-SEC-IMG-TYPE-MISMATCH (0xC002002A)
EFAYSAL said:
If I understant, the status bar has to be red then I will release the mobile button and click download in SPFlashTool.
I try all the way to get that mode but nothing works. So I try to click download button then conect the pkone by random buttons and every time i get red color , yellow , green ,purple , yellow (for many times 100%)
then i get this error:
ERR: STATUS-SEC-IMG-TYPE-MISMATCH (0xC002002A)
Click to expand...
Click to collapse
There is a part that is not variable in the way to use this tool, ever you have to tap on download before to connect device and is recommendable too connect cable usb to pc (not yet to device); from here is when the button that you have to press can vary but like I said you before in my last mt6757 (a very similar to yours) works pressing both vol at same time to connect terminal cable to device and now you will see a red line (could be violet-ish)
Try before just flashing only preloader file to recreate some partitions and then do other flash for the other files.
Of course you have to be sure that all drivers are installed correctly cause this tool needs to put your device in download mode (a special level) and also keep it in this state so find VCOM drivers for Alcatel and adb/fastboot installer and try to uninstalling some older drivers that you don´t use and many times we keep in our pcs and for a short data transmission can helo that all the rom move it in same folder where SPFlashTool is allocated.
After updating drivers and trying all the possibilities buttons the red line doesnt appear.
EFAYSAL said:
After updating drivers and trying all the possibilities buttons the red line doesnt appear.
Click to expand...
Click to collapse
Ok, here there are somethings that we need to know
- First of all don´t forget to charge your battery, after many attempts could consume a lot.
- Your device is recogniced in fastboot mode? mtk has two variables ways to enter to, pressing both vol + pwr till an options menu appear, then you have to select, and the other method most known is vol down+ pwr to go diirectly
- In what android version are you, 6.0?
- What is the exact variant of your device, you can know maybe seeing in the box, this rom is for 5095K version 6.0 MM
- Did you try to flash just preloader, only this file?
If SPFlashTool don´t give signals of recognicing device is probably that your device is not now totally power off, try pressing pwr by 7 seconds, then try to flash again combining both vol with pwr button
Upload some screenshot about the process
SubwayChamp said:
Ok, here there are somethings that we need to know
- First of all don´t forget to charge your battery, after many attempts could consume a lot.
- Your device is recogniced in fastboot mode? mtk has two variables ways to enter to, pressing both vol + pwr till an options menu appear, then you have to select, and the other method most known is vol down+ pwr to go diirectly
Click to expand...
Click to collapse
Which option mode should appear? Screen is always black (off) all that i have on the phone is the LED.
I try more than 4 different drivers for Alcatel Flash Plus 2 (vcom & cdc) but no sound from SPFlash to prove that it recognise the phone. Sounds just release and keep relrease from Windows 10.
SubwayChamp said:
- In what android version are you, 6.0?
Click to expand...
Click to collapse
Yes, last time it was 6.0 before the root
SubwayChamp said:
- What is the exact variant of your device, you can know maybe seeing in the box, this rom is for 5095K version 6.0 MM
Click to expand...
Click to collapse
Unfortunatly, I dont know . There is nothing on the box or manuel.
that is what i found on the box :
FL02
Venus gold H-B
FL02-2HLCEU2
- PWR+VOL(+) : reset the phone
SubwayChamp said:
- Did you try to flash just preloader, only this file?
Click to expand...
Click to collapse
It is done. all that i have to do is to tab on Download and then connect the phone and I dont need to press any button.
SubwayChamp said:
If SPFlashTool don´t give signals of recognicing device is probably that your device is not now totally power off, try pressing pwr by 7 seconds, then try to flash again combining both vol with pwr button
Upload some screenshot about the process
Click to expand...
Click to collapse
I did that but it is same.
Note:
Success fash always done without pressing any button on the phone. and I try it with and without buttons sometimes it is fail when I press a button and otherwise it work.
I have formated whole fash.
EFAYSAL said:
Which option mode should appear? Screen is always black (off) all that i have on the phone is the LED.
I try more than 4 different drivers for Alcatel Flash Plus 2 (vcom & cdc) but no sound from SPFlash to prove that it recognise the phone. Sounds just release and keep relrease from Windows 10.
Yes, last time it was 6.0 before the root
Unfortunatly, I dont know . There is nothing on the box or manuel.
that is what i found on the box :
FL02
Venus gold H-B
FL02-2HLCEU2
- PWR+VOL(+) : reset the phone
It is done. all that i have to do is to tab on Download and then connect the phone and I dont need to press any button.
I did that but it is same.
Note:
Success fash always done without pressing any button on the phone. and I try it with and without buttons sometimes it is fail when I press a button and otherwise it work.
I have formated whole fash.
Click to expand...
Click to collapse
You need to try two different ways to flash files and restore your device.
First method: fastboot mode
You need to get device enter to fastboot in order to flash some files like system, boot and userdata, then there are two main methods to do it:
- Pressing pwr + vol down
- And I mentioned that sometimes work pressing both volume button + pwr and a menu have to appear to can select an option to enter to (fastboot mode), in some devices this method is not working but you have to try several times attempting to.
Second method: SPFlashTool
You have to ever press first of all Download box and connect terminal cable to pc and the buttons thhat you need to press at time to connec cable usb to your device may vary, sometimes vol down, sometimes both vol but never pwr button; if pc recognice then you have to release all buttone an let it pc continue the flash process.
If SPFlashTool recognice device first flash only preloader file and select now lk.bin too. Flash only these two files and after do again a new flash with the rest of the files, Why you need to do this? your partitions are corrupted and you need to restore them with these files in order to can flash all another files.
Before all of this charge your battery, if you have a cover removable then extract it some minutes and put it again.
Also I read that for this model it´s used this tool instead of SPFlash Tool https://androidmtk.com/download-sugar-mtk-sp-flash-tool (inside the zip you will find a password to start the tool) but I´m not sure what kind of rom it needs, you have to connect your device to begin the process, you will find in product models section in the tool this variant for your device "FL02"
Try first the other tool and then this and let me know how you go, mtk devices are almost unbrickeable so it´s just to find the appropriate way to return it to the life.
Hi again!
It was along time,I know . But I tried to know why I can’t return my phone back to life.
I have searched all possible websites for rom of this model and I have formatted my pc and installed win7 with all necessary drivers.
I can’t found any rom for it but now I can flash all the necessary files for boot they flashing and running smoothly but the mobile can’t boot up.
I try to use that app in your replay. It recognizes the device but stuck after that and keep looking for rom without any chance to download it.
I think I have a wrong rom files. I can’t find any other reason but this.
I will write again all information about my phone:
It is called Alcatel Flash Plus 2
I bought it from AliExpress and it came from Indonesia as I remember (not sure)
On battery wrote:
FL02
TCL communication Ltd
FL02-2HLCEU2
EFAYSAL said:
Hi again!
It was along time,I know . But I tried to know why I can’t return my phone back to life.
I have searched all possible websites for rom of this model and I have formatted my pc and installed win7 with all necessary drivers.
I can’t found any rom for it but now I can flash all the necessary files for boot they flashing and running smoothly but the mobile can’t boot up.
I try to use that app in your replay. It recognizes the device but stuck after that and keep looking for rom without any chance to download it.
I think I have a wrong rom files. I can’t find any other reason but this.
I will write again all information about my phone:
It is called Alcatel Flash Plus 2
I bought it from AliExpress and it came from Indonesia as I remember (not sure)
On battery wrote:
FL02
TCL communication Ltd
FL02-2HLCEU2
Click to expand...
Click to collapse
Yes, so many time
When device is booting, it stays in bootlogo or goes atleast to bootanimation?
I understand that you tried with Sugar tool with no lucky.
Did you try again through SP Flash tool? trying to flash in a first attempt only preloader file and in a second attempt the other files? (try with 2 or 3 versions and see the differences).
Is there some custom development, recovery, roms for your device?
I think that now you are flashing correct rom through fastboot but like you did before bad/wrong flashings your bootloader is refusing to boot to system. Flash through fastboot all the partitions that you can follow the syntax for every one of them by i.e. typing fastboot flash cache cache.img and so on one by one (some of them are unflashable through this method)
SubwayChamp said:
Yes, so many time
When device is booting, it stays in bootlogo or goes atleast to bootanimation?
Click to expand...
Click to collapse
Unfortunately, nothing happens. The screen is black no bootlogo appears or anything that shows that device is booting. It is looking like nothing has happened.
SubwayChamp said:
I understand that you tried with Sugar tool with no lucky.
Click to expand...
Click to collapse
Yes. After recognizing it keeps trying to download data but no luck.
SubwayChamp said:
Did you try again through SP Flash tool? trying to flash in a first attempt only preloader file and in a second attempt the other files? (try with 2 or 3 versions and see the differences).
Click to expand...
Click to collapse
I know it is disappointing!. I try this but no luck.
SubwayChamp said:
Is there some custom development, recovery, roms for your device?
Click to expand...
Click to collapse
Unfortunately no, all that I found are TWRP recovery Roms. I don’t know if I can use them with SPFLASH Tool.
SubwayChamp said:
I think that now you are flashing correct rom through fastboot but like you did before bad/wrong flashings your bootloader is refusing to boot to system. Flash through fastboot all the partitions that you can follow the syntax for every one of them by i.e. typing fastboot flash cache cache.img and so on one by one (some of them are unflashable through this method)
Click to expand...
Click to collapse
I began lose hope that the mobile could work again. I live in Sweden and no technicians kan help me to fix this issue. I should do it by myself.
If you kan help me to do that step by step. Please write to me what I have to do from the beginning step by step until I reach the end. To be sure I'm doing it by the right way.
Thanks
EFAYSAL said:
Unfortunately, nothing happens. The screen is black no bootlogo appears or anything that shows that device is booting. It is looking like nothing has happened.
Yes. After recognizing it keeps trying to download data but no luck.
I know it is disappointing!. I try this but no luck.
Unfortunately no, all that I found are TWRP recovery Roms. I don’t know if I can use them with SPFLASH Tool.
I began lose hope that the mobile could work again. I live in Sweden and no technicians kan help me to fix this issue. I should do it by myself.
If you kan help me to do that step by step. Please write to me what I have to do from the beginning step by step until I reach the end. To be sure I'm doing it by the right way.
Thanks
Click to expand...
Click to collapse
I´ll tell you some ideas with no any specific order that you can try or see if works.
Really very strange that display stays in black, you told me that flashing files through fastboot is working but doesn´t appear not even bootlogo, connect to pc as it is and see how pc recognices in devices manager and my pc if appears like a determined drive d/e/f so it looks that some bad flashing burn your kernel and this case is similar to when a Samsung device need to use jtag method to revive, if in your country no-one knows about Alcatel devices this could be a similar case to what I´m saying then it could be a clue for a technician. I tell you this cause many time ago when I flashed by error a Samsung s4 and only this method revived my device.
Try this, flash your stock recovery only through SPFlash tool and flash after through Alcatel Download tool your stock rom cause some firmwares need to detect stock recovery first to can flash other partitions.
At this stage don´t you have stock recovery, no? so you can try to format data cause sometimes when bootloader is altered then avoid to boot and formatting data can solve this.
If this recovery twrp is for your device you can try flashing through SPFlash tool, you have to put recovery.img and scatter-txt in a same folder. then if succesfull format data, system, wipe cache and dalvik and maybe later try to port some custom rom would be a way to solve this.
To flash any partition through fastboot this is the syntax, just follow one by one any of the files that are in your rom folder so just follow these, if some of then can´t be flashed don´t worry then it´s not flashable:
fastboot flash boot bot.img
fastboot flash cache cache.img
fastboot flash lk lk.bin
and so on till the end
...But after try this if you didn´t get boot to recovery and obviously you can´t delete data nor system then delete first the next partitions trough fastboot typing:
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase boot
Try all this and let us see how it goes
I have flashed TWRP Rom but it is same , no luck.
On sugar tool I got this message after success flashing via SPFLASH tool.
I tried all possible buttons to connect device to PC on Fastboot mode but the PC cannot send data to my device.
To be in Fastboot mode , the device has to boot while pressing on (PWR & VOL+) but my device can’t boot.
EFAYSAL said:
I have flashed TWRP Rom but it is same , no luck.
On sugar tool I got this message after success flashing via SPFLASH tool.
View attachment 4518365
I tried all possible buttons to connect device to PC on Fastboot mode but the PC cannot send data to my device.
To be in Fastboot mode , the device has to boot while pressing on (PWR & VOL+) but my device can’t boot.
Click to expand...
Click to collapse
I see that Sugar tool detects your device like rooted and refuses to flash anything, compare imei number which is in the box, I hope that it couldn´t be changed.
Don´t tell me simply no luck, what it says in SPFlash tool when you tried to flash TWRP and I guess that you put scatter-txt and twrp renamed recovery.img simply in the same folder. Just to be clear, to can flash with this tool your device it has to be off not needed fastboot for this. (provide some screenie)
Other combination of keys to enter to fastboot to flash some partitions when something is missing is, try these three ways:
- Pressing only vol down and at same time connecting to charger (connect first one terminal of cable to your device and then to the charger)
- Pressing the three buttons till a menu appears (you must to release inmediately all)
- Pressing vol up + pwr till a menu appears (you must to release pwr button inmediately) then choose fastboot
In the post 4 I provided a link from Google Drive, in this zip there are 8 items;
- From the item 2 use this version of SP Flash tool, put the four files in a folder and flash them
- In the item 3 you will find some scripts for fastboot, maybe they´re working better and also you have here a subfolder with twrp image.
- And if you get sucessfully install twrp in the item 7 there is a backup with some files to restore from this recovery.
Try one by one and update the info, I hope that your motherboard is not damaged.
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
UnequalB said:
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
Click to expand...
Click to collapse
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
UnequalB said:
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Click to expand...
Click to collapse
You can flash the TWRP image through fastboot and then boot to it through commands.
UnequalB said:
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
Click to expand...
Click to collapse
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
SubwayChamp said:
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
You can flash the TWRP image through fastboot and then boot to it through commands.
Click to expand...
Click to collapse
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
SubwayChamp said:
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Click to expand...
Click to collapse
Weirdly enough the error i got was not listed here..
SubwayChamp said:
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
Click to expand...
Click to collapse
This method doesn't work either since the phone won't stay off for more than 7 seconds.
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
UnequalB said:
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
Click to expand...
Click to collapse
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
UnequalB said:
Weirdly enough the error i got was not listed here..
This method doesn't work either since the phone won't stay off for more than 7 seconds.
Click to expand...
Click to collapse
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
UnequalB said:
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
Click to expand...
Click to collapse
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
SubwayChamp said:
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
Click to expand...
Click to collapse
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
UnequalB said:
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
Click to expand...
Click to collapse
Well, if you interrupted the process, that's not good at all. The only you can do is keeping trying it, if your motherboard was not damaged.
hi guys i am DELTIERO from the Philippines did you allready solve the problem?
If not yet done message me on my facebook page https://www.facebook.com/del.villalobos.1/
and i will help you im here veltech san carlos negross occidental phil
Help please! I flashed a gapps zip file using flashify on my infinix smart 5 x657 (Running on lineageos gsi android 12) then the phone just went off. and it not turning on. but it shows the charging indicator light when i connect it to power.
I've tried disconnecting the battery still nothing
what possible solution is there for this?