Related
Sup guys, im really desesperate, today i rooted mi motorola xt316 spice key, so i deleted some apps for a better performance, but now the screen is black, i can view the notificaction bar and the lock screen but its all, what can i do? i searched for one rom and i found nothing, do u guys have a rom or something? ohh and i already do a hard reset.. still the same, please help
What apps had you deleted?
Sent from my Nexus S using xda premium
well i dont remember exactly, but i deleted ones of motorola, u know the widget time, and others. i dont remeber exacly, damn:s
Black screen.. I think you have deleted the launcher
Sent from my Nexus S using xda premium
any suggestion?:S
Is your phone set up with an android market account? I've actually had this problem before and what you do is just install a launcher from the android market and it automatically installs on your phone and it should work perfectly. I still recommend you should reinstall the apps you lost because if you factory reset your phone it will be just as you described. hope it helps!
No , i cant login in with my account, i reset the phone with the factory reset, and when i turn it on, i cant connect with the google servers.
Have someone text you a link to the apk of a launcher, when you get the notification click the download link and when it finished downloading select the download from the notification bar. It'll prompt you to install. If you don't have unknown sources checked then it'll ask you to turn that option on. Once you have a launcher installed then your phone will function properly (depending on what you removed) until you can get the stock rom flashed.
Our you can go straight to the flashing part. Find a rom - stock if you'd like - and flash it. There should be some kind of stock flasher available if there aren't any roms, like an RUU or something... I think RUUs are only for HTC devices, but there should be something similar for your device.
If your phone has a subforum here on XDA, check there for stock or custom roms.
Supersonic Evo 4G | MIUI | Tapatalk
thanks for the response, i have a question; the launcher can be installed via adb?, im gonna try your solution first.
Well I tried the message metod and I apparently delete the default browser, so I tried to install pro launcher via adb but the cmd command says offline device, i think is because the usb debugging is off?, i cant activate it because the screen is black:S
Just flash your rom via Odin. It safer and easy
Odin? what is that? its compatible with the motolola spice key xt316? thanks for the response.
The problem is i cant put my phone in usb debugging because the screen is black, is there another method?
boot ur phone in recovery mode,
this does not need usb-debugging to be On,
and u can use adb...
worth to try
thanks dude im gonna try now.
I put my phone in recovery mode, and i plug the phone to my pc,but when i type adb devices, it doesnt appear.
in the recovery mode there is this options:
reboot system now
apply update from sd card
wipe data/factory reset
wipe cache
download nb0 from sd card
when i tried to install using the adb install comand it says error: device not found
henry225 said:
I put my phone in recovery mode, and i plug the phone to my pc,but when i type adb devices, it doesnt appear.
in the recovery mode there is this options:
reboot system now
apply update from sd card
wipe data/factory reset
wipe cache
download nb0 from sd card
when i tried to install using the adb install comand it says error: device not found
Click to expand...
Click to collapse
ya i think i know why
its the USB drivers for hboot
u need to install drivers for the phone (hboot drivers)
so the machine recognize the phone when plugged
--- or ---
u can get the apk and pack it as an update.zip file (google this to find out how)
then use the option (apply update from sd card)
i think this will install the apk
stinger1 said:
ya i think i know why
its the USB drivers for hboot
u need to install drivers for the phone (hboot drivers)
so the machine recognize the phone when plugged
--- or ---
u can get the apk and pack it as an update.zip file (google this to find out how)
then use the option (apply update from sd card)
i think this will install the apk
Click to expand...
Click to collapse
When i plug my phone on normal mode the comand adb devices recognize the phone but it say offline, but when i plug the phone on recovery mode dont. There is drivers for the recovery mode?, sorrty ima huge noob.
Ok i gogole it and i found a video,http://www.youtube.com/watch?v=FXDszE0Ytn8, but my question is the hboot drivers are the same for all androids? or i need find for my spce xt316.
henry225 said:
Ok i gogole it and i found a video,http://www.youtube.com/watch?v=FXDszE0Ytn8, but my question is the hboot drivers are the same for all androids? or i need find for my spce xt316.
Click to expand...
Click to collapse
i think there is some kind of types/drivers
not 100% related to manufacturer
i mean a driver may work even if its for another manufacturer
anyways try the drivers in ur hand (if u have any)
or try to find "google usb drivers" online somewhere
if failed...
check this list and try to get the proper drivers
http://developer.android.com/sdk/oem-usb.html
i cant boot my huawei u8180 into recovery
i rooted it by super one click
when i tried to flash recovery with rom manager premium it restarts then freeze in boot screen
tried to reset my phone from settings ,privacy it also reboot but freeze on boot
i dont know wt to do
PLZ HELP ME WITH THIS ISSUE
plz any one tell me anything i can do with this problem
i cant even reset my phone
plz reply
thanks guys , i solved my problem alone ,, and insalled cyanogenmod 7.2
everything is ok now
how do you solved your problem with huawei u8180? i have the same isue.
Sorry to bump an old thread
I'm having the exact same problem.
Rooted the 8180 with SuperOneClick, installed Rom Manager, from Rom Manager installed CWM 8160 version with sucess, and whenever trying to boot into recovery mod the phone just hangs while showing the hourglass icon.
I tried reflashing the CWM and it still hangs
Im still running the stock firmware/rom
Can you share how you solved this problem?
Hi, I had a similar issue and did a reboot in to the CWM by holding power, volume up and the "search button" (?) the right one any way. Then did a wipe/factory reset.
Norpan70 said:
Hi, I had a similar issue and did a reboot in to the CWM by holding power, volume up and the "search button" (?) the right one any way. Then did a wipe/factory reset.
Click to expand...
Click to collapse
So you could only boot into CWM by pressing power+volume+search? The regular way (power+volume) would lock up like it does to me, is that it?
Anyway I tried your key combination and it still freezes...
Codeman666 said:
Sorry to bump an old thread
I'm having the exact same problem.
Rooted the 8180 with SuperOneClick, installed Rom Manager, from Rom Manager installed CWM 8160 version with sucess, and whenever trying to boot into recovery mod the phone just hangs while showing the hourglass icon.
I tried reflashing the CWM and it still hangs
Im still running the stock firmware/rom
Can you share how you solved this problem?
Click to expand...
Click to collapse
Bug with rom manager, you should try flashing atleast 3 times and then try and go into recovery, happened to me also, just flash again through rom amanager.
Maeur1 said:
Bug with rom manager, you should try flashing atleast 3 times and then try and go into recovery, happened to me also, just flash again through rom amanager.
Click to expand...
Click to collapse
I already flashed about 5 times and still freezes
Hi,as for the fastboot instructions - I've found this to be a great help in getting adb and fastboot to work on my Win7 x64 installs,so you might want to give it a try. Also,I'm gonna upload in a bit the earlier recovery + recovery manager (if you want to try that before you play around with adb/fastboot) to flash it to your device + the device drivers.
Edit - The link for the file - http://ubuntuone.com/14mi7lUkJelsrNBr4z5Uy2 - 12.5 MB - contains the older recovery (you can still try to flash the newer one first if you want), 2 different driver packs and the aforementioned recovery manager.
bk109 said:
Hi,as for the fastboot instructions - I've found this to be a great help in getting adb and fastboot to work on my Win7 x64 installs,so you might want to give it a try. Also,I'm gonna upload in a bit the earlier recovery + recovery manager (if you want to try that before you play around with adb/fastboot) to flash it to your device + the device drivers.
Edit - The link for the file - http://ubuntuone.com/14mi7lUkJelsrNBr4z5Uy2 - 12.5 MB - contains the older recovery (you can still try to flash the newer one first if you want), 2 different driver packs and the aforementioned recovery manager.
Click to expand...
Click to collapse
Thank you! Im trying recovery manager as I type this, I find it curious it says "Currently installed recovery: unrecognized"
As for the driver, I already had it installed from when I rooted the phone.
EDIT: So I installed the up to date recovery (recovery-clockwork-5.0.2.8-u8160) with Recovery Manager, still unrecognized and still freezes after booting into recovery.
Installed the one you supplied (ClockworkMod-u8160-v0.1) and got the exact same results, unrecognized and freeze
Codeman666 said:
Thank you! Im trying recovery manager as I type this, I find it curious it says "Currently installed recovery: unrecognized"
As for the driver, I already had it installed from when I rooted the phone.
EDIT: So I installed the up to date recovery (recovery-clockwork-5.0.2.8-u8160) with Recovery Manager, still unrecognized and still freezes after booting into recovery.
Installed the one you supplied (ClockworkMod-u8160-v0.1) and got the exact same results, unrecognized and freeze
Click to expand...
Click to collapse
In that case you might want to try the doomsday option - fastboot (not really,hell - it's actually rather useful + if you follow that website you also get adb up and working too). As for the 'unrecognized' alert,I remember getting it too once upon a time,but I have to admit - I haven't used the app myself since when I made the jump from the stock 2.2.1 ROM to a custom froyo build,so I can't recall for the moment what I did to fix that error
bk109 said:
In that case you might want to try the doomsday option - fastboot (not really,hell - it's actually rather useful + if you follow that website you also get adb up and working too). As for the 'unrecognized' alert,I remember getting it too once upon a time,but I have to admit - I haven't used the app myself since when I made the jump from the stock 2.2.1 ROM to a custom froyo build,so I can't recall for the moment what I did to fix that error
Click to expand...
Click to collapse
Will do. Besides the fastboot recovery command what else do I need to do from the phone side?
Does fastboot display any feedback or log about the flashing/installation?
Codeman666 said:
Will do. Besides the fastboot recovery command what else do I need to do from the phone side?
Does fastboot display any feedback or log about the flashing/installation?
Click to expand...
Click to collapse
Nothing specific -you just have to reboot in fastboot mode (just restart the phone while pressing Power and Volume Down. Windows should chirp and install the drivers automagically - afterwards just use that command discussed earlier and it should flash your recovery without any additional prompts (it should only print out a confirmation of a successful flash) and you should have the CWM ready to go
Edit: I put my device into fastboot mode on a clean Windows install (a Win8 Consumer Preview) and it did autodetect and install the relevant driver without restarting itself
No luck... Now it's driver issues
When booting the phone with either the vol up or down pressed and pluging in the USB my PC isn't recognizing the driver, I used both drivers you sent me.
Initially it's detected as Android 1.0 device, upon fetching the drivers it gets named "Android Sooner Single ADB Interface".
As I refresh device manager it goes back to Android 1.0 with an exclamation mark.
I think it's a driver signature issue, I'll try again in a couple of hours in a different PC
edit:in debug mode I have no driver issues and I can even detect my phone with ADB
Finally!
Tried it in another computer, auto downloaded some ASUS adb driver and installed fine.
Flashed latest CWM recovery with fastboot and now I'm able to boot into CWM!
Thank you so much for your help!
Sry for bumping.
So, i had the same trouble with the drivers. But i just downloaded HiSuite directly from the Huawei Site and these fix my problem with drivers to use adb without troubles . Hope this help someone.
BTW, Thanks bk109!
It did helped me thx man
Sent from my U8180 using xda app-developers app
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
*im not developer, neither noob i just like to share what I know*
Maybe this is a noob guide, but i did my best to share something helpful
before you go deeper, be sure to check your phone able to get into fastboot mode. If you cant, use REAL unbrick method instead
If your phone soft or hard bricked, bootloop, stuck on logo etc you know you are f***ed unless you know what should to do.
Some time ago bootlooped my phone, but i cant go to recovery, cant ADB because I forgot to enable USB debugging, my computer wont recognize my phone poperly because my phone mad at me, and my phone flickering like hell *party hard*. Maybe this is a brick not bootloop but whatever
Good friend of mine tell me what should to do
What you need:
Working PC with minimal ADB and fastboot installed //see the thread here, your phone's USB and ADB driver installed //download here if you dont have it
Working USB DATA cable
Custom recovery everything will do, as long as its compatible with your current android version. Rename the img to recovery.img
ROM you prefer everything will do, as long as its compatible with your current android version. Move to your SD Card
The power of will
Step:
1. Make sure your phone is turned off
2. Boot into fastboot mode, you will see some chinese message
3. Plug your phone to to your PC
4. Check if your PC at least know that you are pluged in your phone (check via device manager by 'plug and un-plug' your phone and check for 'appear and disappear' device , mine listed as it is was a modem.)
5. Move the recovery.img inside minimal adb and recovery folder root usually under c:/programfiles directory
6. Run the minimal adb and fastboot, check your device by using /adb devices/ command without backslash
7. If your device is not listed, dont worry. We still able to use the fastboot
8. Boot your phone into recovery mode by using /fastboot boot recovery.img/ command without backslash
9. Wait for few secs, and your phone should touched down to recovery mode.
10. Do wipe (data, dalvik, cache, system, internal)
11. Flash your prefered ROM
12. ..........???
13. Profit
Troubleshooting:
If your PC unable to recognize your phone completely, try using another usb cable, usb ports, uninstall-reinstall, plug-unplug, and make sure your phone in fastboot mode before you plug your phone to the PC.
Feel free to critics, I hope this helped you :fingers-crossed:
Thank you for all who helped me making this post.
McBubu_1337 said:
*im not developer, neither noob i just like to share what I know*
Maybe this is a noob guide, but i did my best to share something helpful
before you go deeper, be sure to check your phone able to get into fastboot mode. If you cant, use REAL unbrick method instead
If your phone soft or hard bricked, bootloop, stuck on logo etc you know you are f***ed unless you know what should to do.
Some time ago bootlooped my phone, but i cant go to recovery, cant ADB because I forgot to enable USB debugging, my computer wont recognize my phone poperly because my phone mad at me, and my phone flickering like hell *party hard*. Maybe this is a brick not bootloop but whatever
Good friend of mine tell me what should to do
What you need:
Working PC with minimal ADB and fastboot installed //see the thread here, your phone's USB and ADB driver installed //download here if you dont have it
Working USB DATA cable
Custom recovery everything will do, as long as its compatible with your current android version. Rename the img to recovery.img
ROM you prefer everything will do, as long as its compatible with your current android version. Move to your SD Card
The power of will
Step:
1. Make sure your phone is turned off
2. Boot into fastboot mode, you will see some chinese message
3. Plug your phone to to your PC
4. Check if your PC at least know that you are pluged in your phone (check via device manager by 'plug and un-plug' your phone and check for 'appear and disappear' device , mine listed as it is was a modem.)
5. Move the recovery.img inside minimal adb and recovery folder root usually under c:/programfiles directory
6. Run the minimal adb and fastboot, check your device by using /adb devices/ command without backslash
7. If your device is not listed, dont worry. We still able to use the fastboot
8. Boot your phone into recovery mode by using /fastboot boot recovery.img/ command without backslash
9. Wait for few secs, and your phone should touched down to recovery mode.
10. Do wipe (data, dalvik, cache, system, internal)
11. Flash your prefered ROM
12. ..........???
13. Profit
Troubleshooting:
If your PC unable to recognize your phone completely[B/], try using another usb cable, usb ports, uninstall-reinstall, plug-unplug, and make sure your phone in fastboot mode before you plug your phone to the PC.
Feel free to critics, I hope this helped you :fingers-crossed:
Thank you for all who helped me making this post.
Click to expand...
Click to collapse
Good work bro
The Hard Gamer said:
Good work bro
Click to expand...
Click to collapse
Thanks, its noob post so i dont expect anything special
McBubu_1337 said:
Thanks, its noob post so i dont expect anything special
Click to expand...
Click to collapse
It is a good help to those who are new to getting bricked
It shows waiting for device
Tommen1998 said:
It shows waiting for device
Click to expand...
Click to collapse
You may need to check some things:
Your PC actually know that you have inserted your phone. It doesn't have to know it's a phone (so it can be detected as unknown device or something similar, mine is detected as a modem)
Your phone is indeed in fastboot mode, you can tell yours is in fastboot mode by a Chinese message at the bottom of the screen
Change your cable data, make sure it is a cable data, not a normal charging cable
let me know if you need some help
McBubu_1337 said:
You may need to check some things:
Your PC actually know that you have inserted your phone. It doesn't have to know it's a phone (so it can be detected as unknown device or something similar, mine is detected as a modem)
Your phone is indeed in fastboot mode, you can tell yours is in fastboot mode by a Chinese message at the bottom of the screen
Change your cable data, make sure it is a cable data, not a normal charging cable
let me know if you need some help
Click to expand...
Click to collapse
Hello. I Tried a lot, but my PC doesn't recognise my phone. The phone is in fastboot mode. I've tried by changing cables too
same issue
Tommen1998 said:
Hello. I Tried a lot, but my PC doesn't recognise my phone. The phone is in fastboot mode. I've tried by changing cables too
Click to expand...
Click to collapse
I am also getting the same issue tried different cables but not working. Anyone please help me
The same issue. I think it's about getting it recognized in Fastboot mode. It's recognized in Android but not in Fastboot. All new devices are installed including those you get in Diagnostic 9091 mode (Power+V+). What do I need for Fastboot mode?
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