Hello all,
Apologies if this is not the right section to post - though it might be if I'm able to lift the ROM off this engineering device
I've been trying to root/change the ROM of this sample Streak device I have access to, but to no avail. It's SIM unlocked, but clearly is an earlier SW (possbily HW) version. There's no access to fastboot (pressing the camera on boot gets me to the engineering test menu, no fastboot option).
Here's some additional information:
Modem (Baseband) Version: AUS_************51
Model Number: M01M
OEM Version: Unknown
Build number: 77910
Any ideas?
Thanks
jkbuha
I'd ask Paul at modaco. He seems to know his way around rooting..
Sent from my Dell Streak using Tapatalk
Thanks for the tip fards - I didn't really want to trouble Paul, but seeing as no one here has any ideas I'll drop him an email and see what his thoughts are.
cheers
jkbuha
photo of the engineering menu please
this sucks
Heres the boatloader !!! My touchscreen wont calibrate either nor will it go into fastboot!!!!!!!!!!!!!
Try using the androot.apk since it doesnt require fastboot.
well 1% progress...
im rooted but i cant downgrade or flash any rom im afraid to flash clockwork....I just found out how to get fastboot even on that screen tho!!!!!!!!!
thats interesting, australian version?
in any case, you can either root it via the universal root tool and do a nandroid backup, or you can yaffs2 it.
you need linux os on your computer, yaffs2, and the system folder from your device
Code:
# cd /where/your/dumped/system/folder/is
# ./mkfs.yaffs2 system /system.img
# exit
i have an engineering device too, the one with a sticker under the battery cover. just wondering, is there a FCC number for that one?
Hi I'm back - apos for the delay
So here's an update...
I've managed to semi-brick my engineering (aus?) dell by issuing a fastboot -w and/or a fastboot flash boot/recovery without backing up my system first! Flashing any recovery image so far is unsuccessful.
Here's what I know so far:
Pressing volume down ONLY (not UP) on powerup goes directly to the fastboot menu. Right now that's the only thing that works - no recovery, booting.
I tried to flash the backup nandroid image kindly provided by one of the posters on this forum, but no luck. Boot/Recovery/System works but when flashing userdata with the data.img provided I get an error saying remote: too large.
Not sure if I have an FCC id - I'll check later
Any help appreciated!
if you can get into fastboot, i wonder if you can get into recovery?
its volume up+down+power on boot.
if you cant, try flashing to 2.1 using the american guide and see if it works. your device is already half bricked, so might as well give it a shot.
http://android.modaco.com/content-p...-devices-download-here/page/180/#entry1376331
theres also a few recoveries you can try, but the stock one wont do you any good since you dont have the baseband 51 rom.
Thanks for the link - but same results unfortunately
Pressing up+down on power on takes me to a menu which says:
1) factory reset
2) update from .zip (NOTE: not pkg)
3) reboot
When pressing the second option the screen goes blank (I'm assuming it's trying to launch recovery) and depending on what recovery I've flashed it either goes to fastboot mode or the two icons start flashing on/off then stop altogether. It's never gone to a proper recovery menu, irrespective of the imgs I've flashed.
Anyone has a link to
(i) a humongous backlog of recovery roms
(ii) a set of nandroid img backups for the streak
Or any other ideas?
Thanks
jkbuha
Related
Hi all
first of all I apologize if this is not the right place to put my inquiry in, but I could not find the specific forum for this device.
I have serious problem with this android mobile phone. it is pretty good phone very useful with dual sim function one of them is 3G with WiFi Hotspot but the problem that I have rooted the phone with superoneclick and I have installed a lot of apps in it modifying some language files then when I restart the phone to let the changes take effect then the mobile keep restarting for infinite. Tried to get in to the recovery mode by using Call Button+Volume up+Power but the screen became blank. I spent the whole day searching the the internet to find the solution but with no clue. the problem the device is new and not supported that much in the public forums. could not find Stock Rom. Huawei website and bulletin was not useful.
is there any way to do it through USB or sdcard and How?
thanks in Advance
I am still trying to find a solution...
if you need it, I attached the original recovery dump to this post.
then you just need to get "fastboot" and then (after preparing your device for fastboot):
"fastboot flash recovery recovery.img" (on a command line opened on the same folder where "fastboot" is)
or you can probably do it too on Linux if you prefer. if it is possible, you'll find the way for it on Google.
also, to access fastboot mode is POWER+VOL_DOWN (not volume up or a 3 key combination) and recovery is POWER+HOME (which you probably already know).
the system dump I can't send because I never made a dump.img of it and I am currently having a bootloop problem (I'll probably have to flash the original rom from a friend).
bl88drg said:
if you need it, I attached the original recovery dump to this post.
then you just need to get "fastboot" and then (after preparing your device for fastboot):
"fastboot flash recovery recovery.img" (on a command line opened on the same folder where "fastboot" is)
or you can probably do it too on Linux if you prefer. if it is possible, you'll find the way for it on Google.
also, to access fastboot mode is POWER+VOL_DOWN (not volume up or a 3 key combination) and recovery is POWER+HOME (which you probably already know).
the system dump I can't send because I never made a dump.img of it and I am currently having a bootloop problem (I'll probably have to flash the original rom from a friend).
Click to expand...
Click to collapse
Hi, Can you help me and upload the boot img. I accidentally erase the boot partition.
Many Thanks.
So yes, I tried to flash a different system.img, and am currently bricked, but would like to share some helpful info:
Google's Nexus telephone support will not supply factory image locations
They will also not comment on whether some sort of "internet recovery" (using Ethernet) exists such.
Fastboot can be manually entered by powering up with a palm ove the device, waiting for the red flashing to begin, and once it does, immediately removing your palm. I struggled with this for a little while (as I couldn't connect over adb/fastboot) and am at least in a state now where I could restore the device.
I hope this info's helpful... and if it is, please help me out with some factory image sources over in my "Factory Images?" thread!
Oh, and it'll run ICS
...or at least boot it! (can't yet post links)
youtube.com/watch?v=dUmuQULyrAk
You can Fastboot the device and only botched the system image correct? Well, in theory all you need to do is boot ClockworkMod Recovery through Fastboot and restore a dump someone has already done. I think their is one in the Dev Forum already.
ThisIsDave said:
So yes, I tried to flash a different system.img, and am currently bricked, but would like to share some helpful info:
Google's Nexus telephone support will not supply factory image locations
They will also not comment on whether some sort of "internet recovery" (using Ethernet) exists such.
Fastboot can be manually entered by powering up with a palm ove the device, waiting for the red flashing to begin, and once it does, immediately removing your palm. I struggled with this for a little while (as I couldn't connect over adb/fastboot) and am at least in a state now where I could restore the device.
I hope this info's helpful... and if it is, please help me out with some factory image sources over in my "Factory Images?" thread!
Click to expand...
Click to collapse
Thanks for the info, saved me at least 3 or 4 times after soft bricking my Q. One thing that I found to help is while the device is bricked type in command prompt: adb reboot-bootloader ... this will generate a waiting for device tag then once you see that unplug the Nexus Q and plug it in, within one second as soon as you see a hint of blue on the mute button put your palm over it and it typically boots right into fastboot mode. If not just unplug and repete until it goes.
FYI: Also if you try to launch clockwork from an apk and instal a rom you will almost most definitely soft brick it (tried to sideload AOSP JB ROM and some others with no luck).
Hello everyone!
I would like to know if it's possible to rewrite the bootloader, mine is damn crashed
The sim doesn't work, and it cant be connected to any available operators [But the device is able to find them]
Also Phone can not run any other rom but DSC
And also I wonder why it writes error near "Network Lock"
Is it possible to fix?
You may need the QDL Tool for this, but I'm inclined to believe yours is a hardware issue rather than software. Usually, "Default NV Checked #3" refers to the internal MicroSD. It may have failed or it may be stuck on write protect. Run the following test and post the results.
1. Turn off your Streak
2. Hold down the camera button all the way, as you turn on your Streak
3. At the white screen, dial in the code *#301# – This will open the engineering mode that allows you to run individual tests.
4. Dial in 10 then press Enter to run the SD & SIM test
5. The Internal SD test should pass, and it should show “permanent write-nonprotect”.
I have already tryed qdl tool, nothing changed
And the test is showing “permanent write-nonprotect”.
Try installing a stock ROM and recovery, 360 for example, and see if that helps restore the bootloader. Then install the custom ROM of your choice.
The device hangs on Dell logo, it can run ONLY DSC rom, thats strange
Sent from my HTC One™
You may want to try running fastboot and pushing a replacement boot.img from 407 to the Streak, and see if that takes. The hardware diagnostics you did seem to rule out a hardware failure, which means the boot.img must have been corrupted somehow.
so do I have to use the following code to flash the boot.img ?
Code:
fastboot -i 0x413c flash boot boot.img
but i don't know where can I get the boot.img, can't find it on this site
Do i have to take it out from the stock .PKG file?
Each of the ROMs should be available on dev host in zip format as well. Download one of those and you can get the boot.img from the zip.
Hello, Guys. So I did a stupid thing today - I was poking around in the build.prop in my v20d P769. I changed the value of a line concerning the battery, something like "battery_genuine" - My thought was that it was going to enable some sort of alternate battery notification or icon or whatever, I'm not sure what I was thinking.
Anyway, long story short, I rebooted after editing build.prop and now when the phone turns on it just says "use genuine battery - powering off" and shuts off. I had previously uninstalled CWM (getting ready to manually apply v20f) so I can't get to recovery to mount /system. I have been trying all day to get the offline flash method to work and the damn thing won't work half the time. I went through the thread instructions to install small server and edit hosts file - then reboot - when the loopback ip's are in the hosts file the test link on the thread (127.0.0.1:9002) doesn't work and neither LG application will work. If I comment out the loopback lines and restart both of them will open but neither of them will do anything useful. LG Updater tool just says I have the latest software and the UptestEX_mod2_marwin application won't flash anything.
Hoping someone can help me out here so I can recover this phone.
boot the phone in fastboot mode, don't know how to do that with your model though
use fastboot to boot into any custom recovery by typing 'path_to_adb_toolkit_files\fastboot.exe boot your_recovery_image.img'
if fastboot hangs on <waiting for device> install usb drivers
then pull off build.prop, change that field to original value and push it back into the phone
sorry mate, can't explain more detailed
Either flash ICS uboot and xloader in fastboot mode and unbrick it after, or if you can access adb, try sometjing like the following:
cd to your adb directory on your PC
adb pull /system/build.prop (in a command prompt on your PC)
Modify the file (it will be in the adb folder)
adb push pathto/thefile/build.prop > /system/build.prop (again in the cmd)
Hope it helps
Sent from my LG-P760 using xda app-developers app
N00BY0815 said:
Either flash ICS uboot and xloader in fastboot mode and unbrick it after, or if you can access adb, try sometjing like the following:
cd to your adb directory on your PC
adb pull /system/build.prop (in a command prompt on your PC)
Modify the file (it will be in the adb folder)
adb push pathto/thefile/build.prop > /system/build.prop (again in the cmd)
Hope it helps
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply man - yeah I can't get to adb, that was my first though so i'm going to try fastboot, only problem is, I don't know how to boot fastboot. Is s/w upgrade mode the fastboot screen (volume up + plug in cable)?
Also, would anyone mind explaining why the small server only outputs "file not found" when attempting to start up the flash tool? The only way I can get the flash tool to even launch is to comment out the loopback lines in hosts. lol man it's times like this when I miss motorola!
*Edit - In case anyone wants to help on this front, here is the output I receive from small server when trying to open B2CappClient or UpTest or even hit the test link in the offline flash thread:
Accept-Language: en-US,en;q=0.8
^!!
!->02/08 23:54:39 [127.0.0.1:2173>9002] (t1 4) >\favicon.ico(Undefined/default)
Error. File not found.
!->02/08 23:54:39 [127.0.0.1:2173>9002] (t1 5) >HTTP in:279 out:1993 Time:31
!->02/08 23:54:41 [127.0.0.1:2177>9002] (t1 6)
GET /favicon.ico HTTP/1.1
Host: 127.0.0.1:9002
Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
^!!
!->02/08 23:54:41 [127.0.0.1:2177>9002] (t1 7) >\favicon.ico(Undefined/default)
Error. File not found.
!->02/08 23:54:41 [127.0.0.1:2177>9002] (t1 8) >HTTP in:279 out:1995 Time:94
!->02/08 23:55:43 [127.0.0.1:2184>9002] (t1 9)
GET /client/app/live_update.jsp HTTP/1.1
Host: csmg.lgmobile.com:9002
Cache-Control: no-cache
^!!
!->02/08 23:55:43 [127.0.0.1:2184>9002] (t1 10) >\client\app\live_update.jsp(Undefined/default)
Error. File not found.
!->02/08 23:55:43 [127.0.0.1:2184>9002] (t1 11) >HTTP in:99 out:2012 Time:62
I recommended removing all lg drivers and etc. Redownload all files, disable firewall and antivirus. But first you need to install fastboot and flash the u-boot for ice cream.
Inside the fastboot zip by lelus is more instructions on how to set it up. And checkout the original thread about fastbooting the l9
And you might want to try on another PC,
You need a good and clean windows environment for all to work well. This is the problem with many people. Plus a lot of antivirus programs don't like the small server.
Sent from my LG-P769 using xda app-developers app
well, if you boot into a screen that is neither android nor recovery, it should be fastboot at least this applies to my phone
since the combination is one button + plug in cable i guess it's the right one
does it say fastboot mode in the top of the screen?
SuicideFlasher said:
well, if you boot into a screen that is neither android nor recovery, it should be fastboot at least this applies to my phone
since the combination is one button + plug in cable i guess it's the right one
does it say fastboot mode in the top of the screen?
Click to expand...
Click to collapse
Well I managed to get to fastboot with the p940 script. The screen that comes up with "S/W Upgrade Please wait while upgrading...". this may be some sort of fastboot derivative but there's no response to "fastboot devices" at the prompt. Can I flash cwm through fastboot if my bootloader is locked? I had it installed with the bootstrap method.
peoplegetpeople said:
Well I managed to get to fastboot with the p940 script. The screen that comes up with "S/W Upgrade Please wait while upgrading...". this may be some sort of fastboot derivative but there's no response to "fastboot devices" at the prompt. Can I flash cwm through fastboot if my bootloader is locked? I had it installed with the bootstrap method.
Click to expand...
Click to collapse
Fastboot is an inverted lg logo.
This will offer some more help,
http://forum.xda-developers.com/showthread.php?p=43703982
Hey don't flash ice cream and ect.
All you have to do is flash (in fastboot) the boot.IMG for the kdz you are on, and you're good to go.
Extract the boot.img from the kdz
Look at my guide. Or just wait until later tonight for me to upload it.
To tell you the truth, Lol, I did the same thing you did with the battery. I was fast enough to edit it before it shutoff. I had toolbox lite app installed.
CM 10.1 P769
Finally got it! :laugh: Turns out, the default path for small server is c:\shttps\www - the problem I gave myself is that when I didn't extract to the c root, I copied from my L9 directory - when I copied none of the contents of \www copied with it, once I moved those files to the correct position it all went through as it should!
Thanks for your help guys!!
kuma82 said:
Fastboot is an inverted lg logo.
This will offer some more help,
http://forum.xda-developers.com/showthread.php?p=43703982
Hey don't flash ice cream and ect.
All you have to do is flash (in fastboot) the boot.IMG for the kdz you are on, and you're good to go.
Extract the boot.img from the kdz
Look at my guide. Or just wait until later tonight for me to upload it.
To tell you the truth, Lol, I did the same thing you did with the battery. I was fast enough to edit it before it shutoff. I had toolbox lite app installed.
CM 10.1 P769
Click to expand...
Click to collapse
hahaha I saw this about 10 mins after I got it to boot! lol - oh well, I'm running 20f now, getting ready to root and see about unlocking the bootloader. Now that the flash tool is working correctly, the only thing I have to do is get a feel for the mirrored, wonky screen. I've been researching the bootloader method but could never get that flash tool to work correctly. I'm in the game now! WOOT!
Thanks for all your help man!
peoplegetpeople said:
hahaha I saw this about 10 mins after I got it to boot! lol - oh well, I'm running 20f now, getting ready to root and see about unlocking the bootloader. Now that the flash tool is working correctly, the only thing I have to do is get a feel for the mirrored, wonky screen. I've been researching the bootloader method but could never get that flash tool to work correctly. I'm in the game now! WOOT!
Thanks for all your help man!
Click to expand...
Click to collapse
Just be sure you are ready for everything,
I recommended flashing 20d then 20b.
Hold up I'll give you all the help I gave to someone in a p.m.
kuma82 said:
I didn't have a hard time, but then again I've studied my a** off, and I knew how to fix all problems that popped up. My advice to you is read all the threads about unlocking the bootloader. The video is good but it doesn't break it down enough.
Let me tell you about everything that can go wrong and how to fix it
Problems
1. After flashing the euro kdz your phone won't boot past the logo.
Okay, this problem will make things harder(but do able), because you have to hard reset the device by pressing/holding the vol (-) + home + power (let go of power button when the lg logo comes up)
Plus after a hard reset all data will be wiped and you will have to enable USB debugging on the wonky touch screen.
The chance of this happening is rare because you are not coming from a custom ROM.
2. After flashing you get a security error (or an error during the flashing process).
Now this one sucks because you will need to fastboot and flash the ice cream u-boot. Then put the phone in the s/w upgrade mode and perform the offline flash again.
I had this happen to me once, while flashing the wind kdz. Messing with fastboot is not hard but it takes time to understand it. Get familiar with it first before trying to unlock. I'll send you a link with some more info.
3.After flashing the euro kdz you find out you don't have root.
Sometimes rooting fails (dam computers)
Now I had this happen to me after flashing euro kdz (so no cwm) but I wasn't really worried about that because I had a signal and I could make/receive calls. I had a signal because when I was flashing I swapped out the euro radio (p760.fls) with the metropcs one (lgms769.fls)
Note: you have to extract the radio from the metro kdz and rename it to p760.fls
When flashing replace the 11th bin (with hex edited 11th bin for 20b) & the radio (from metro renamed).
Another thing don't rush the unlock. I waited about 3 to 4 hours before trying, plus I took a couple of calls on the 20b kdz. And I was on wifi.
I flashed the euro kdz at work and when I got home I turned on WiFi and waited another hour.
I'm not to sure about what the video says about turning off and flashing the radio.
When the unlock first came out, the instructions were to not turn off the device before unlocking.
When I flashed the euro kdz I was on the metropcs ROM.
This is what I recommend and did.
Enable USB debugging, show all touches, & allow install from unknown sources.
Leave your phone on normally(don't put it in s/w mode) and flash the euro kdz and hopefully no problems.
After waiting a couple of hours try the unlock command with Adb on your PC.
If all goes good the phone will take you to an inverted unlock screen, just press the volume up (make sure you press the Up button!)
This will take you to the official fastboot (but it's inverted), now in fastboot flash the cwm recovery image.
In cwm flash the touch screen fix and restore a backup.
Another thing make your own backup with the locked bl cwm (just in case you have to erase all data) make backup on external SD. Another thing, Lol ,make sure the backup is good, try to restore it. I have had several corrupted backups with cwm.
I know it's a lot to learn, but then again you want to be prepared.
Think of it like a final exam, Lol and you won't go wrong.
If you get lost just holla at me.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
CM 10.1 P769
kuma82 said:
Just be sure you are ready for everything,
I recommended flashing 20d then 20b.
Hold up I'll give you all the help I gave to someone in a p.m.
CM 10.1 P769
Click to expand...
Click to collapse
Wow man! Awesome response, really appreciate your input and explanations. It really takes some of the unknown out of it. Thanks!
Sent from my LG-P769 using xda app-developers app
httGeneric Procedure - Turn on " Fake Battery Mode " ( Bypass Genuine Battery Test ).
Boot Error ( " Use Genuine Battery " -power off- )
Entered here since procedure seems to be generic " Turn on Fake Battery Mode " (Bypass Genuine Battery Test).
>> Also called Service Menu: Type in: ##LGSERVICEMENU send (##5473784296368) on the dialpad.
>>enter the security code: 000000, locate: SW/HW Tests or HW test or SW/HW Versions
>> find "bypass booting" in menu locate "fake battery mode" select it and choose on.
--- My phone LG Optimus G Pro E980 (note: the 980 in code refers to model)
when approx 90-95%, with new gold 4200mAh battery Boot up Error ( " Use Genuine Battery " -power off- )
so, i went into hidden menu 3845#*980# ->Settings->Battery->Battery Fake Mode (Turned it ON), seems to be fixed.
By the way, the gold battery tested WORSE THAN 3140mAh OEM, Save yourself time, buy the Quality LG OEM.
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