Related
hello everyone
how unlock bootloader on a tablet when it is not booting up. restarting again & again after displaying android logo??
anyone has know the method, plz help
thanx
raj1raj said:
hello everyone
how unlock bootloader on a tablet when it is not booting up. restarting again & again after displaying android logo??
anyone has know the method, plz help
thanx
Click to expand...
Click to collapse
You might get more luck if you at least tell people what tablet it is and what you did to get it in such a bad state.
tablet not booting
SimonTS said:
You might get more luck if you at least tell people what tablet it is and what you did to get it in such a bad state.
Click to expand...
Click to collapse
thanks for reply
my device is china MT6572 with android 4.2.2
I have use a very very very superb tool named "MtkDroidTools v2.48" and bricked my newly purchage tablet.
1. I click on root and happy thing is that tablet got rooted. wow
2. I have created backup from this tool and after few minutes, many *.img backup files are created on my pc and my tab's sdcard. wow again
3. After restarting the tab it restarting again & again and not booting. really a "heart attacking wow".
I have tried following steps
1. In default "android stock recovery 3e" trying to restore backup files and got message "installation aborted" everytime. same message from using "adb sideload command"
2. creating a scatter file from this tool and load backup in "SP_Flash_Tool_v5.1343.01" tool. but no any tool connect my tab. it says no device.
3. only "adb sideload" from stock recovery has the way to connect to the pc. but I don't know which kind of files are used at there??
During the backup process a log file created by MtkDroidTools has attached for details information.
then plz tell me. what I do for get again a "relaxed wow"??
Load scatter file and back up files in SP Flash tool. Power your tablet off, hit download button in SP Flash tool then connect tab to pc.
If you have the preloader driver installed SP flash tool should connect and start flashing firmware to phone. Do you hear the connecting sound when you connect powered off tablet to pc? If not, you may need to press and hold Vol Down, Vol up, or menu button while connecting tab to pc.
Hope this helps and good luck!
Sent from my SGH-I337 using xda app-developers app
tablet not booting
SimonTS said:
You might get more luck if you at least tell people what tablet it is and what you did to get it in such a bad state.
Click to expand...
Click to collapse
Klown80 said:
Load scatter file and back up files in SP Flash tool. Power your tablet off, hit download button in SP Flash tool then connect tab to pc.
If you have the preloader driver installed SP flash tool should connect and start flashing firmware to phone. Do you hear the connecting sound when you connect powered off tablet to pc? If not, you may need to press and hold Vol Down, Vol up, or menu button while connecting tab to pc.
Hope this helps and good luck!
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot sir
but my tab has no menu button, only have three hard buttons.
pressing
power + volup = stock recovery
power + voldown= nothing happen
power + volup + voldown = poweroff tab
when I connect the tab to pc in power off mode. The tab automatically startup after a charging logo.
I have preloader drivers on my pc but when turn on the tab. it is appearing in device manager (preloader composite) for only 2-3 seconds. and disconnected. because tablet rebooting again. I can't install preloader drivers in this short time.
plz suggest.
raj1raj said:
Thanks a lot sir
but my tab has no menu button, only have three hard buttons.
pressing
power + volup = stock recovery
power + voldown= nothing happen
power + volup + voldown = poweroff tab
when I connect the tab to pc in power off mode. The tab automatically startup after a charging logo.
I have preloader drivers on my pc but when turn on the tab. it is appearing in device manager (preloader composite) for only 2-3 seconds. and disconnected. because tablet rebooting again. I can't install preloader drivers in this short time.
plz suggest.
Click to expand...
Click to collapse
Ok, no need to hit a combo of buttons, only 1 button you need to press while connecting tab to PC. Please retry following the directions from my last post again
Yes, preloader will only show for a few seconds in device manager before it turns off. Preloader is only for reflashing firmware. When it enables itself, it is looking for the SP FT (or other firmware flashing programs) to be there to catch it, if not preloader shuts itself off.. Your download of SP Flash Tool should have included the needed preloader drivers. Then you load files in SP FT and hit download button then connect tab to PC.
tablet not booting ----solved
Klown80 said:
Ok, no need to hit a combo of buttons, only 1 button you need to press while connecting tab to PC. Please retry following the directions from my last post again
Yes, preloader will only show for a few seconds in device manager before it turns off. Preloader is only for reflashing firmware. When it enables itself, it is looking for the SP FT (or other firmware flashing programs) to be there to catch it, if not preloader shuts itself off.. Your download of SP Flash Tool should have included the needed preloader drivers. Then you load files in SP FT and hit download button then connect tab to PC.
Click to expand...
Click to collapse
Thank you very very very very much. Finally I have got a wow.
After many efforts, I resolved the tablet booting issue. It is possible due to only your valuable suggestion.
steps are here:
1. connect tab to pc & installing preloader usb drivers.
2. getting VID & PID of tablet usb connection.
3. modifying "SP FT settings files" with new values of my tab.
4. creating a scatter file from droid tool & load in SP FT.
5. Flashing backup to the tab successfully.
You are such a genius. I have been wasted a lot of time since a week for getting the right answer. During this period I had connected to many android experts at many sites. but no satisfaction answer.
And u are really amazing. You have got the real problem in only three conversation. really great.
Well I m a windows expert. If u feel any technical problem regarding servers or windows, ask me, I will try my best.
I am launching a website soon named "GeniusPepoleofWorld.com". Many technical experts & genius people will listed there in different categories like Android experts, Windows experts, Linux Experts, Robotics Experts, Electronics xtra xtra. I want to add you at top there in Android Expert list. Now site is under constructions. I want to know your name & personal mail-id like gmail etc. When I will finish my site, I will inform you.
One more thing I want to know that "what is the use of stock recovery & adb sideload, which files types are used with it?"
Plz plz reply this with your name and mail-id.
Thanks a lot again
-----------
Regard
Raj
Sr. Server Engineer
Delhi, India
raj1raj said:
Thank you very very very very much. Finally I have got a wow.
After many efforts, I resolved the tablet booting issue. It is possible due to only your valuable suggestion.
steps are here:
1. connect tab to pc & installing preloader usb drivers.
2. getting VID & PID of tablet usb connection.
3. modifying "SP FT settings files" with new values of my tab.
4. creating a scatter file from droid tool & load in SP FT.
5. Flashing backup to the tab successfully.
You are such a genius. I have been wasted a lot of time since a week for getting the right answer. During this period I had connected to many android experts at many sites. but no satisfaction answer.
And u are really amazing. You have got the real problem in only three conversation. really great.
Well I m a windows expert. If u feel any technical problem regarding servers or windows, ask me, I will try my best.
I am launching a website soon named "GeniusPepoleofWorld.com". Many technical experts & genius people will listed there in different categories like Android experts, Windows experts, Linux Experts, Robotics Experts, Electronics xtra xtra. I want to add you at top there in Android Expert list. Now site is under constructions. I want to know your name & personal mail-id like gmail etc. When I will finish my site, I will inform you.
One more thing I want to know that "what is the use of stock recovery & adb sideload, which files types are used with it?"
Plz plz reply this with your name and mail-id.
Thanks a lot again
-----------
Regard
Raj
Sr. Server Engineer
Delhi, India
Click to expand...
Click to collapse
I am happy to hear it worked for you. Nice job Raj! I am just passing on the knowledge I learned here on XDA (Thank @rua1 he made MTK DroidTools and without that tool alot of folks with MTK devices wouldn't have root, stock firmware back up files, or working recovery
Anyhow, as for your last 2 questions. Stock recovery is used for flashing officially signed update files from your device manufacturer (If they were to make an update that is lol) This is how all android devices are able to accept ota updates, they download the file to phone/tablet then reboot into recovery and then it flashes the downloaded file to the device.
Adb sideload allows you to connect the device to a PC and then upload a firmware file to device to be flashed via recovery instead of downloading it directly to the phone. This is useful if you had an officially signed stock firmware file for your device stored on your pc. Some custom recoveries also allow you to use adb sideload but since you have stock recovery you would be restricted to using only officially signed files.
Say for instance you were not able to get your device to boot properly, you would just need to boot tablet into recovery mode and then choose adb sideload. At this point you would connect tab to PC and then put your firmware file in the same folder you have adb.exe in. (Let's call the firmware file "firmware.zip" in this example) Then open command prompt in same folder that adb.exe is in and type "adb sideload firmware.zip" this would push the firmware.zip file to the device then flash it for you.
Since you were able to use MTK Droidtools to get root then make a back up, you should be able to also use it to make a custom recovery for your device too. When you made the back up, it will usually make 2 back ups, one on your pc that you use SP FT to flash files and restore your device then it also makes a back up on your devices sd card that is flashed through custom recovery to restore your device. This would make restoring your device pretty easy if you need to do so again and it will also allow you to restore without needing a PC to do it.
Hope this helps!
Kevin
raj1raj said:
Thank you very very very very much. Finally I have got a wow.
After many efforts, I resolved the tablet booting issue. It is possible due to only your valuable suggestion.
steps are here:
1. connect tab to pc & installing preloader usb drivers.
2. getting VID & PID of tablet usb connection.
3. modifying "SP FT settings files" with new values of my tab.
4. creating a scatter file from droid tool & load in SP FT.
5. Flashing backup to the tab successfully.
You are such a genius. I have been wasted a lot of time since a week for getting the right answer. During this period I had connected to many android experts at many sites. but no satisfaction answer.
And u are really amazing. You have got the real problem in only three conversation. really great.
Well I m a windows expert. If u feel any technical problem regarding servers or windows, ask me, I will try my best.
I am launching a website soon named "GeniusPepoleofWorld.com". Many technical experts & genius people will listed there in different categories like Android experts, Windows experts, Linux Experts, Robotics Experts, Electronics xtra xtra. I want to add you at top there in Android Expert list. Now site is under constructions. I want to know your name & personal mail-id like gmail etc. When I will finish my site, I will inform you.
One more thing I want to know that "what is the use of stock recovery & adb sideload, which files types are used with it?"
Plz plz reply this with your name and mail-id.
Thanks a lot again
-----------
Regard
Raj
Sr. Server Engineer
Delhi, India
Click to expand...
Click to collapse
I've got the exact same problem with my phone... My phone, Celkon A15 (Indian brand) also has the same chipset number and while trying to root using MTKdroids tool, I have managed to get it in the boot looping stage.
I'm just curious on how you managed to get the pre-loader installed for this? I CAN NOT get the SP Flash tools to detect my phone for the life of me. Also, when I load my scatter file, it has the "PRELOADER" section in RED... and when I try to upload the preloader.bin from my backup files, it says... "Load file "*path name*" fail!"
I am still struggling to understand how the SP Flash tool works and if it would be able to get my phone alive again (well it did help you out, so I am bit optimistic).
Please HELP!
device not booting
kbrahma said:
I've got the exact same problem with my phone... My phone, Celkon A15 (Indian brand) also has the same chipset number and while trying to root using MTKdroids tool, I have managed to get it in the boot looping stage.
I'm just curious on how you managed to get the pre-loader installed for this? I CAN NOT get the SP Flash tools to detect my phone for the life of me. Also, when I load my scatter file, it has the "PRELOADER" section in RED... and when I try to upload the preloader.bin from my backup files, it says... "Load file "*path name*" fail!"
I am still struggling to understand how the SP Flash tool works and if it would be able to get my phone alive again (well it did help you out, so I am bit optimistic).
Please HELP!
Click to expand...
Click to collapse
Hi
1. First you have connect your device to pc.
2. you have to open the device manager and keep your eyes on a new hardware found at device manager, when you start up your device.
3. Preloader will only show for a few seconds in device manager before it turns off.
3. install preloader drivers.
4. open SP Flash tool and load scatter file and set path for your backup files.
5. Click download button and reboot your device.
6. Software will catch your device and finally backup will be restored to your device.
I too have got same problem, i have infocus m2 with mt6582, i rooted with kingroot n used mtk droid tools for backup.after backup i tried to modify boot img and install cwm using mtk tools but now it wont boot up, nor it enters recovery mode, i tried to flash stock boot and recovery img through sp flashtool but its giving error (2004), plz help me plzzzz....
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:
So i wanted to flash a new firmware on my MTK Device (UleFone Power 2), but i ran into some Errors while doing so, thus , my phone died in the process.
Following Errors occurred, depending on which (SP Flash Tool;SPMultidownloadflashtool;etc) you use:
Errors:
Internal Buffer
STATUS_SEC_IMGHDR_TYPE_MISMATCH
Through digging and asking on the web, two wonderful and very very helpful people: alterogi and finally Sunray888
This solution popped up. Thank you so much to both of them!!
Solution:
But first: You are now warned, try this at your own risk.
Quoted from Sunray888, alterogi. Credits to them.
My German Guide (more detailed with Pictures): Outside of XDA
Side Note: For the UP2 Rom you use SPMultiPortFlashDownloadProject , for the UK6P ROm you use SPFlashTool.
(Links & Attachments below!) (Adb-Fastboot.zip & Checksum.zip)
Part1:
1. Download all the files. (Below are the links and attached files.
2. Extract each zip to its own folder. Then Put the files of the Checksum.zip into the ROM Folder of the Ulefone Power 2.
3. Run the Checksum.exe and wait until it is done. It will show up in the black CMD when it's finished. A new Checksum.ini should be in the folder now.
Part2:
1. Make a backup of your NVRAM and NVDATA, a full ROM backup if you can.
2. Get the Oukitel K6000 Plus ROm Version 2.0 Ready. Extract it to its own folder somewhere on your desktop.
3. Open the SPFlashtool and select the android scatter file of the Oukitel Rom.
4. Connect your phone, hold Volume down and press on "Download" in the SPFlashTool. Now you wait for the process to end, WHILE still holding the button down.
5. After it is done flashing your new Firmware unto your phone, start it like you would normally do. Disconnect your phone now. You can now also skip the Setup Details, since we still have to flash the original Firmware.
6. Go to Device Infos on the bottom of your phone settings, tap a few times on Build Number until the Developer Options activate. Go back and tap on Developer Options.
7. In here you activate OEM Unlock and USB Debugging. Back to the pc: Now you open a CMD Windows and navigate to your extracted ADB-Fastboot Folder. (Some Pictures of this are on my German Tutorial Thread, Link above).
8.Connect your phone, tick the avaible spot of the upcoming new popup notification. Shutdown your phone now. Hold Volume Up and Power Button at the SAME Time until the Fastboot Menu pops up.
Make sure your phone is still connected to the pc.
9. In the cmd window you will now have to type the following thing: fastboot oem unlock
9.5 Another Method to get into fastboot mode: (OR enabled usb debug, accept connection between your PC and Ulephone and send command fastboot reboot bootloader after that "fastboot oem unlock")
10. After the process is done. You are still in fastboot mode.
And let the phone connected to the Pc.
11. Now you have to flash the original ROM/Firmware. In this case only Version 17 will work.
On this step i had a lot issues with "insufficient buffer"-Errors under SP Flash tool, but there is a solution for this.
Be careful :
Try to use #SPMultiPortFlashDownloadProject Version 3.1620 - only this software worked for me,earlier Versions i tried ( v.3.1636 ) always showed an Error.
Current Status: Phone is still connected to pc, fastboot mode, oem has just been unlocked by yourself.
What to do now:
12 Open the SPMultiPortFlashDownloadProject, load scatter file of the Ulefone Power 2 Firmware, then press scan. Nothing will happen now, so be quick: Don't disconnect your phone.
Press Volume Up + Power Button at the same time to simulate a new connection to the pc. While the phone is still connected via cable! We have to do this. You will now hear a sound which you normally would here when connecting a new device to your Pc. Now you just have to keep holding the Volume Up Key.
IMPORTANT:
Don't let go of the button until the Programm shows up a Green Tick which signals the end of the Process. Now you can let go of the button.
13. After the scan has finished, press start and flash firmware. But how? It's easy. Just do the same again. ->>
13.1 Press Start in the Flash Programm.
13.2 We have to simulate a new connection. Hold Vol+ and Power Button. Until you hear the sound again, now only keep holding the Vol+ Button.
14. Wait for the green Tick Notification. Until then: Don't you dare let go of the Vol+ Button. When it shows up, you're pretty much done. Congrats!
15. Restore NVRAM and NVDATA.[/I] through mtk engineering mode: open dialer and call *#*#3646633#*#* , scroll down to GRPS and type in your IMEI (can be found in the box, in which your phone came shipped with). If it says something like that it's successfully written.-> Activate Airplanemode, wait a few seconds, deactivate it, activate Mobile Data Connection and wait. It should show a mobile data active.
Download Links: (I didn't upload those files,i simply shared the links, all credits to their respective owners. Use at your own risk.!)
UP2 Rom: Google Drive
Flashtool for UP2 Rom: One Drive
UK6P 2.0 + Flashtool: Click me
Checksum Gen Zip: --Below--
ADB Components: --Below--
UPDATING:
After flashing V15 Ulefone Firmware, use the SP FLASH TOOL to flash the newest firmware via "Firmware Upgrade" mode. remember to keep pushing vol up before connecting phone!
How to:
Press Download in Tool
Push and hold vol up
Connect cable to pc.
wait until green tick shows up.
Profit.
Same situation here. I've tried flashing with and without battery, no success. I can confirm that I did NOT lock the bootloader. Not that it helps me much.
I've tried using different versions of SPFT in addition to the multiport tool, but they either don't work with Power 2 scatter file, or show the same error.
This can potentially be a driver / USB issue, so I will probably try that next (different computer, fiddle with the drivers). I've also seen claims that SPFT v3 can happily flash over this, and then newer versions start working too, so try that if you can. It did not work for me - the download never starts on my computer with v3.
I can also add that I can flash preloader as well, although I try and leave that off when possible. The modem and lk* partitions show the same error you have, though, and the phone is dead.
I have managed to resolve this with a lot of help from Vivanyok on 4pda.
1. Make a backup of your NVRAM and NVDATA, a full ROM backup if you can.
2. Download Oukitel K6000 Plus ROM v2.0. Only this version will work.
3. Flash it. It will actually work just fine, no errors. I've used the latest SPFT.
4. Boot the phone into Android. In Developer Options, enable OEM Unlock.
5. Reboot into fastboot, do fastboot oem unlock.
6. After this, you can simply flash any Ulefone ROM for Power 2. Win!
7. Restore NVRAM and NVDATA.
Hope this helps somebody.
Thanks for your reply!! I will try that and report back ! I'm so glad there are people out here who help !
EDIT: OMG, You are my hero!!! The Flash Process went just fine, no errors. It boots up. Thank you so much! Now i can flash like a devil again, haha
EDIT2: So i could use the phone with the oukitel rom but i want the original rom, firmware.
So here is the other Problem. I can't flash them. I either get insufficient buffer error or the imghdr error.
Could you link me what you are using? I really need the phone. Thanks for your help in advance.! :S
Hi sm00th4f3
I add some advices to Vivanyok instruction by red letters --->
I have managed to resolve this with a lot of help from Vivanyok on 4pda.
1. Make a backup of your NVRAM and NVDATA, a full ROM backup if you can.
2. Download Oukitel K6000 Plus ROM v2.0. Only this version will work.
3. Flash it. It will actually work just fine, no errors. I've used the latest SPFT.
4. Boot the phone into Android. In Developer Options, enable OEM Unlock.
5. Reboot into fastboot, do fastboot oem unlock.
OR enabled usb debug, accept connection between your PC and Ulephone and send command
fastboot reboot bootloader
after that
fastboot oem unlock
6. After this, you can simply flash any Ulefone ROM for Power 2. Win!
on this step i had a lot issue with insuffitient buffer under SP Flash tool, but yesterday i win too.
be careful :
after oem unlocking you should NOT reboot ulephone to Android,let phone stay connected to PC
try use #SPMultiPortFlashDownloadProject version 3.1620 - only this soft help me,earlier i tried v.3.1636 but always error appear.
and when i started flashing i stayed ulephone connected to usb (i dont disconnect phone after oem unlocking) and i simulated connection by long press volume UP + Power buttons. You can control connection by default PC sound.
due in SPMultiPortFlashDownloadProject other interface i did not change flashing type, it was firware update by default.
After that my ulefone become alive.
7. Restore NVRAM and NVDATA.
good luck, if any questions ask me on 4pda.ru
So, i tried your nice guide, and it finally worked!! Side Note is: After fastboot oem unlock you have to scan with the #SPMultiPortFlashDownloadProject version 3.1620 your phone first, and then like you have already said, use the volume up+power button combo to simulate a connection. and then it will be flashed. Holy crap. Thank you so much!!.
You are welcome, last three day i also tried flash my up2
Still same problem
..
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
Hi there,
Thanks for the instructions. I have succeeded to install the Oukitel V2.0 ROM on my Ulefone Power 2 and change OEM in Android and fastboot but still no success to flash the final Ulefone Power 2 phone ROM from the Ulefone web site. The flash process starts but after two or three download steps the flash tool (3.1620 in administrator mode) stops still with the STATUS_SEC_IMGHDR_TYPE_MISMATCH error.
I have also tried with another ROM coming from another site, but still same error.
Could perhaps provide me a download link to a ROM that you successfully flashed to the Ulefone Power 2?
Thanks for your help
bletru said:
..
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
Hi there,
Thanks for the instructions. I have succeeded to install the Oukitel V2.0 ROM on my Ulefone Power 2 and change OEM in Android and fastboot but still no success to flash the final Ulefone Power 2 phone ROM from the Ulefone web site. The flash process starts but after two or three download steps the flash tool (3.1620 in administrator mode) stops still with the STATUS_SEC_IMGHDR_TYPE_MISMATCH error.
I have also tried with another ROM coming from another site, but still same error.
Could perhaps provide me a download link to a ROM that you successfully flashed to the Ulefone Power 2?
Thanks for your help
Click to expand...
Click to collapse
Look in your inbox, i wrote you a private message.
bletru said:
..
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
Hi there,
Thanks for the instructions. I have succeeded to install the Oukitel V2.0 ROM on my Ulefone Power 2 and change OEM in Android and fastboot but still no success to flash the final Ulefone Power 2 phone ROM from the Ulefone web site. The flash process starts but after two or three download steps the flash tool (3.1620 in administrator mode) stops still with the STATUS_SEC_IMGHDR_TYPE_MISMATCH error.
I have also tried with another ROM coming from another site, but still same error.
Could perhaps provide me a download link to a ROM that you successfully flashed to the Ulefone Power 2?
Thanks for your help
Click to expand...
Click to collapse
That will help many others like me.please post the ule stock rom you flashed and the flash tool.
SUNRAY888 said:
Hi sm00th4f3
I add some advices to Vivanyok instruction by red letters --->
I have managed to resolve this with a lot of help from Vivanyok on 4pda.
1. Make a backup of your NVRAM and NVDATA, a full ROM backup if you can.
2. Download Oukitel K6000 Plus ROM v2.0. Only this version will work.
3. Flash it. It will actually work just fine, no errors. I've used the latest SPFT.
4. Boot the phone into Android. In Developer Options, enable OEM Unlock.
5. Reboot into fastboot, do fastboot oem unlock.
OR enabled usb debug, accept connection between your PC and Ulephone and send command
fastboot reboot bootloader
after that
fastboot oem unlock
6. After this, you can simply flash any Ulefone ROM for Power 2. Win!
on this step i had a lot issue with insuffitient buffer under SP Flash tool, but yesterday i win too.
be careful :
after oem unlocking you should NOT reboot ulephone to Android,let phone stay connected to PC
try use #SPMultiPortFlashDownloadProject version 3.1620 - only this soft help me,earlier i tried v.3.1636 but always error appear.
and when i started flashing i stayed ulephone connected to usb (i dont disconnect phone after oem unlocking) and i simulated connection by long press volume UP + Power buttons. You can control connection by default PC sound.
due in SPMultiPortFlashDownloadProject other interface i did not change flashing type, it was firware update by default.
After that my ulefone become alive.
7. Restore NVRAM and NVDATA.
good luck, if any questions ask me on 4pda.ru
Click to expand...
Click to collapse
cannot find the up2 rom which can be flashed after flashing Oukitel K6000 Plus ROM. Please help...
Download Links added. There shouldn't be any problems using my method as long as you think as well.
Be aware that you have to use the Flashtool i linked, the exact same Flashtool Version as mentioned. Otherwise go to my german thread outside of xda to get more detailed pics.
solved my problem
this was the solution for me, thanks a lot....
recovered!
Hello guys! Thanks for the instructions, it worked great! Only thing, the fastboot you supplied has an password, so I used another I found online.
I finally got time to take care of my bricked Power 2 phone, and I got it back to life using the Oukitel method.
The phone works great, I only had to input IMEI numbers manualy.
Is there a need to lock back the bootloader, because now my device says "orange state", your device cannot be trusted?
hm hm.... fastboot allows me to lock the bootloader, but then the phone would reset itself to factory state for security reasons, so I will leave my bootloader unlocked, as I don't want to go trough the phone app installation and getting the settings to my taste
i just updated the zip..there shouldn't be a password anymore. ^^
For us, there isn't really a need to lock the bootloader. Since we can simply install every ota update by downloading the new rom from external sites. Just a reminder: don't use the ota update app since it will brick or just not work, since your bootloader is unlocked.
Ulefon power 2
ULEPHON POWER 2
Oukitel k6000 Plus Roma- ok
SPMultiPortFlashDownloadProject verziju 3.1620 FL-OK, DL FAIL ???? HELP HELP
[email protected]
brumen1 said:
ULEPHON POWER 2
Oukitel k6000 Plus Roma- ok
SPMultiPortFlashDownloadProject verziju 3.1620 FL-OK, DL FAIL ???? HELP HELP
[email protected]
Click to expand...
Click to collapse
don't forget to enable oem unlock (bootloader isn't unlocked yet after you do this)
then fast boot the phone with oukitel rom, unlock the bootloader with adb fast boot unlock
don't let go of the vol button while flashing the phone with multiport flash tools
don't use ulepfhone original cable, mine was not working ok although there was no visual damage to the cable. I used another one that fit the usb port on the phone more firmly
bad_ri said:
don't forget to enable oem unlock (bootloader isn't unlocked yet after you do this)
then fast boot the phone with oukitel rom, unlock the bootloader with adb fast boot unlock
don't let go of the vol button while flashing the phone with multiport flash tools
don't use ulepfhone original cable, mine was not working ok although there was no visual damage to the cable. I used another one that fit the usb port on the phone more firmly
Click to expand...
Click to collapse
The Original Cable is fine...the problem might only be with yours.
brumen1 said:
ULEPHON POWER 2
Oukitel k6000 Plus Roma- ok
SPMultiPortFlashDownloadProject verziju 3.1620 FL-OK, DL FAIL ???? HELP HELP
[email protected]
Click to expand...
Click to collapse
Read the thread, it's not that difficult.
sm00th4f3 said:
The Original Cable is fine...the problem might only be with yours.
Click to expand...
Click to collapse
maybe, just told what happened in my case, the original cable was bad from the first day
good luck with the flash
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
Yesterday I did UNLOCK BOOTLOADER and then ROOT everything was fine I wanted to install V4A but after installation the device was in BOOTLOOP so I did it FULL WIPE and everything worked so I said I will return it to LOCK BOOTLOADER and since the device works it is stuck on the current image have been destroyed and can not boot realme can not enter bootloader and recovery
Today a good guy came into my computer and did MSMTOOL with me twice but without success I do not know what to do The device was bought exactly a week ago Thanks for the help
PS MSMTOOL requires username and password so that's why the guy helped me if something has a username and password I would love to try again
MY DEVICE - rmx2086
Amitayy said:
up plis help my phone briked!!
Click to expand...
Click to collapse
EDL mode is available but I have no clue if Flashone - "Qualcomm - flash dead phone" will work. Besides Flashone looks for zip file not ozip. You may need to convert ozip to zip and please check here for that - https://forum.xda-developers.com/realme-2-pro/how-to/convert-ozip-to-zip-installing-stock-t4065277.
I have X3, not Super Zoom but I could get the phone to edl mode and could see the COM port on Windows too. Power off the unit. Connect your USB cable to PC - this is important. wait for the screen to go blank. Press Vol Down + Power button together to get to recovery mode - takes few seconds. Select language and then press ver 1.2 (as shown on X3) about 3 times to get to edl mode. If you do not connect the cable as mentioned tapping ver x.x does not do anything.
Hope that helps and good luck.
PS: I know that you've mentioned that no recovery. Hopefully assume the screen remains blank and tap on bottom middle to see if Windows recognises any COM port under device manager.
up plis help my phone briked!!
bro did you get the solution . because i need it. my phone is bricked . it shows current image has been destroyed.....that stuff. its bootloader is not unlocked . i dont know what to do . some please help
hi , i have a realme x3 , after downgrading my phone is bricked , its says current image has been destroyed ........... , please help me someone in this lockdown without phone i will be in great trouble please help me . i am not able to boot to fastboot menu . its detected by the computer when both volume and power button is pressed
Bro msm tool works or not
Help me bro