Hi to all of you, I need the help of anyone on how to extract and restore (adb commands pull and push) the build.prop file in my cell (now bricked) i had the files (modified buil.prop and the original backup build.prop.bak) inside the phone...
The main problem I have: An issue with device recognition in windows PC... driver ADB VCOM MTK 6592 (tried in different PCS windows Xp and 8) (the device manager "see" the vcom preloader but only a little moment (in the first instant when connect the cell (cell off) with usb cable) and then dissapear (disconnect) the vcom preloader...
When I type the command adb devices, result: no devices found...
Tried to upgrade the vcom drivers (when i can catch it in the active state in device manager)... nothing
Tried to "on" the phone... nothing
Tried to flash a new ROM from Recovery (MIUI or Feelingme 078)... ERROR installation aborted
I can see this effect (with usbview): the usb is recognized in the PC (but just for a little moment at the instant when plug it), then disconnect...
I need to recover the original build.prop.bak from coolpad memory, rename it to build.prop and send it to coolpad again...
I think i can flash (from recovery) an original build. prop (packed as update.zip) doing the wipes and apply update from sdcard)... anyone can assist me on this?
This new 9976A item comes to me with 048 version, custom buid version 265 and rooted from factory...
Anyone can please help me?
Probably want to post in here http://forum.xda-developers.com/showthread.php?t=2635445 where there are other members with your device that are rooted and some links to some roms.
es0tericcha0s said:
Probably want to post in here http://forum.xda-developers.com/showthread.php?t=2635445 where there are other members with your device that are rooted and some links to some roms.
Click to expand...
Click to collapse
Thanksss. will do that.
It all depends on your current phone status.
Why did you try to modify it in the first place, how did you try it?
If you're able to
0) put phone in recovery-mode,
1) connect to the phone via adb,
you could
2) rename/delete the wrong build.prop directly on the phone.
So you don't need to push or pull anything.
I'd start MTKDroidTools, connect the powered off phone or while it's powered on being inside the recovery-mode, and hit the ADB-button...then:
"adb shell"
"cd system"
"rm build.prop" deletes current file
"mv build.prop.bak build.prop" renames your backup to original file
"reboot" restarts the device
If you want to use another ROM, you need a proper cwm-recovery to flash (any) kind of that .zip ...that's also the reason,why you couldn't install another ROM on your phone, because your current recovery haven't got the rights to do it. This will also be keeping you from using a update.zip containing the proper build.prop,but that's only a guess.
...on the fly with 9976A
thor2001 said:
It all depends on your current phone status.
Why did you try to modify it in the first place, how did you try it?
If you're able to
0) put phone in recovery-mode,
1) connect to the phone via adb,
you could
2) rename/delete the wrong build.prop directly on the phone.
So you don't need to push or pull anything.
I'd start MTKDroidTools, connect the powered off phone or while it's powered on being inside the recovery-mode, and hit the ADB-button...then:
"adb shell"
"cd system"
"rm build.prop" deletes current file
"mv build.prop.bak build.prop" renames your backup to original file
"reboot" restarts the device
If you want to use another ROM, you need a proper cwm-recovery to flash (any) kind of that .zip ...that's also the reason,why you couldn't install another ROM on your phone, because your current recovery haven't got the rights to do it. This will also be keeping you from using a update.zip containing the proper build.prop,but that's only a guess.
...on the fly with 9976A
Click to expand...
Click to collapse
Hi thor, I modify the buil.prop with root explorer (sound section) because the music not listening through the speakers
Backup created build.prop.bak
Restart the phone... brick...
The phone starts but no pass the main initial logo... get stuck here...
Now, with the phone off, connect it with usb cable, the pc recognizes the phone (but only by a short amount of time) with a couple of seconds disconnetcs...
i have tried a couple of coolpad 9976 vcom drivers finded in the web... (do you have a specific or ensured one?)
mtk 6592 drivers...
this phone comes to me factory rooted, build number: 4.2.048.P2.140127.9976A
custom build version: 265
i will try to do all of you advices...
is this possible to flash an update.zip (with only an original build.prop file inside it) through CWM?
Is this a nice solution?
Hold the line...
I'd try booting in recovery and once you're inside it, connect the phone to the PC, while MTKDroidtools is running. It should be found by Droidtools (MT6592,but without IMEI) and you hit the ADB-button.
After that, use the commands I mentioned earlier ...
The build.prop isn't unique, so if you're unable to use your backup you could use mine (but still need a connection through adb or update.zip).
What is the current recovery on your phone? I know, there's a way building an update.zip...but I've never tried/used that.
The short timespan, in which you can see your device in windows devicemanager, you can right click on it and use "update driver"-function pointing to the VCOM-files. As soon as you click "update driver" you've got time and it will be installed correctly.
ADB-drivers are easy to install, because it can be while the device isn't connected.
Which VCOM-driver did you install, which ADB-driver on which OS?
...on the fly with 9976A
@federimau
Here, try this update.zip...it should contain the correct build.prop
thor2001 said:
@federimau
Here, try this update.zip...it should contain the correct build.prop
Click to expand...
Click to collapse
THANKS GENIUSSSS.
I have the 3a Stock Recovery.
Will try to do this...
If this not work, can i flash what ROM with this Recovery (3a)???
any links to suggested ROMs that work with Recovery 3a???
You need a working system first.
Then use a TWRP or cwm-recovery for installing any custom ROM...
I don't use any custom ROM, so you already asked in the right thread (9976A ROOT).
federimau said:
If this not work, can i flash what ROM with this Recovery (3a)???
any links to suggested ROMs that work with Recovery 3a???
Click to expand...
Click to collapse
thor2001 said:
Hold the line...
I'd try booting in recovery and once you're inside it, connect the phone to the PC, while MTKDroidtools is running. It should be found by Droidtools (MT6592,but without IMEI) and you hit the ADB-button.
After that, use the commands I mentioned earlier ...
The build.prop isn't unique, so if you're unable to use your backup you could use mine (but still need a connection through adb or update.zip).
What is the current recovery on your phone? I know, there's a way building an update.zip...but I've never tried/used that.
The short timespan, in which you can see your device in windows devicemanager, you can right click on it and use "update driver"-function pointing to the VCOM-files. As soon as you click "update driver" you've got time and it will be installed correctly.
ADB-drivers are easy to install, because it can be while the device isn't connected.
Which VCOM-driver did you install, which ADB-driver on which OS?
...on the fly with 9976A
Click to expand...
Click to collapse
Current recovery 3a (from factory)
I think the last vcom drivers are MTKUniversalbrushdriver
Windows XP SP3
i copied AdbWinApi.dll and AdbWinUsbApi.dll and adb.exe in windows/system and windows/system32 folders
thor2001 said:
You need a working system first.
Then use a TWRP or cwm-recovery for installing any custom ROM...
I don't use any custom ROM, so you already asked in the right thread (9976A ROOT).
Click to expand...
Click to collapse
ahhhh ok, ok,... with this you say that i can not solve the problem flashing a new entire ROM through Recovery?
You can try it, I haven't tried that at all.
You should backup your WORKING firmware and IMEI FIRST, just in case!
Regards
federimau said:
ahhhh ok, ok,... with this you say that i can not solve the problem flashing a new entire ROM through Recovery?
Click to expand...
Click to collapse
thor2001 said:
You can try it, I haven't tried that at all.
You should backup your WORKING firmware and IMEI FIRST, just in case!
Regards
Click to expand...
Click to collapse
will do that first... i expect your buil.prop flashed by update.zip works...
thor2001 said:
You can try it, I haven't tried that at all.
You should backup your WORKING firmware and IMEI FIRST, just in case!
Regards
Click to expand...
Click to collapse
By the way... what is your recomendation/suggestion/advice about: best/fast ROM, CWM version, ROOT method
will do all that in the future
I'll stay at Stock v056,because every newer fw uses the small tray icons,which I don't like.
I still use rua1 autoCWM (non-touch), which is automatically created when you're doing the backup.
Rooting could be done after making the backup, with MTKDroidTools. This should root almost any MTK-phone.
It depends on your firmware and if you're using stock-recovery or cwm-recovery.
With a cwm-recovery,you could use a Chinese update.zip to root.
In the newer FWs you need Root Genius to get system-root after you've got shell-root.
...on the fly with 9976A
Even with the messed up build.prop file, wouldn't you still be able to flash a custom recovery via Odin? Just flash one that has a file manager, boot into it, and manually restore the original build.prop.
Or am I missing something here?
thor2001 said:
You can try it, I haven't tried that at all.
You should backup your WORKING firmware and IMEI FIRST, just in case!
Regards
Click to expand...
Click to collapse
Hi thor... tried to flash your update.zip through stock Recovery (3e) unsucessfully...
with this stock recovery i can not flash anything... tried to flash it.. error... tried to flash five different ROMs... error...
can you help with a new update.zip (only build.prop inside) that i can flash with this recovery (3e)??
Phenom2122 said:
Even with the messed up build.prop file, wouldn't you still be able to flash a custom recovery via Odin? Just flash one that has a file manager, boot into it, and manually restore the original build.prop.
Or am I missing something here?
Click to expand...
Click to collapse
Hi Phenom, i used odin with samsung phones, here we are using mtkdroid and spflashtools, i do not know if odin works with this mediateks cells??
Odin is for Samsung phones.
@federimau
Did you try connecting the phone, while it's in recovery and MTKDroidTools is running?
Like I mentioned some time ago?
Doing the trick via adb?
thor2001 said:
Odin is for Samsung phones.
@federimau
Did you try connecting the phone, while it's in recovery and MTKDroidTools is running?
Like I mentioned some time ago?
Doing the trick via adb?
Click to expand...
Click to collapse
yes it tried it... i´m focus now finding a new usb VCOM driver... can you advice me an ensured one?
Related
hello to all...i am new to this developing. i have a rom file in .zip format....inside it there is system folder. i want to convert this .zip into a system img file. is it possible?? actually i hav a phone on which sdcard is not getting detected. so cwm recovery wont work, niether adb is detecting that device, so i want to make a system img file from this rom so that i can flash it using fastboot. Plz help me
niranjand147 said:
hello to all...i am new to this developing. i have a rom file in .zip format....inside it there is system folder. i want to convert this .zip into a system img file. is it possible?? actually i hav a phone on which sdcard is not getting detected. so cwm recovery wont work, niether adb is detecting that device, so i want to make a system img file from this rom so that i can flash it using fastboot. Plz help me
Click to expand...
Click to collapse
For future reference, at the very least, state the device you have and or are having problems with. Makes things easier for people like me
What your asking for doesn't exist to my knowledge. However, you can extract the contents of the zip to your hard disk and use fastboot to flash the file "boot.img' which should be in the root of the zip you have. Everything else needs to be pushed via ADB to the /system partition. If your CWM is built correctly, ADB should detect your device when connected. That's assuming that you have your drivers installed already.
In reality, I don't think that what you are wanting to do can be done, however I don't know everything either. :silly: Best of luck
bill.weckel said:
For future reference, at the very least, state the device you have and or are having problems with. Makes things easier for people like me
What your asking for doesn't exist to my knowledge. However, you can extract the contents of the zip to your hard disk and use fastboot to flash the file "boot.img' which should be in the root of the zip you have. Everything else needs to be pushed via ADB to the /system partition. If your CWM is built correctly, ADB should detect your device when connected. That's assuming that you have your drivers installed already.
In reality, I don't think that what you are wanting to do can be done, however I don't know everything either. :silly: Best of luck
Click to expand...
Click to collapse
i am trying it for huawei u8180
shinobisoft said:
For future reference, at the very least, state the device you have and or are having problems with. Makes things easier for people like me
What your asking for doesn't exist to my knowledge. However, you can extract the contents of the zip to your hard disk and use fastboot to flash the file "boot.img' which should be in the root of the zip you have. Everything else needs to be pushed via ADB to the /system partition. If your CWM is built correctly, ADB should detect your device when connected. That's assuming that you have your drivers installed already.
In reality, I don't think that what you are wanting to do can be done, however I don't know everything either. :silly: Best of luck
Click to expand...
Click to collapse
I tried this using Livesuit 1.11 for a softwinerEvb a13 tablet (no other known device specs) and it said the image file was invalid. Situation is I soft bricked my tablet by flashing the wrong cwm zip. Finally found out how to connect via Livesuit (kinda like fastboot or bootloader mode or something? like Odin?) to flash stuff to it. I decided to use an erase img .img because where I found how to connect it suggested that to the OP (on techknow). So now instead of the tablet just being stuck on the first screen when trying to boot (normal or recovery), it doesn't do anything at all since there's no boot.img. Which I'm not worried about since It connects to my laptop just fine via livesuit still so I can get a boot on it (ADB won't detect it - pretty positive it's not ADB user error [I run cmd "adb root" when the tablet is connect in whatever mode its in - the way livesuit detects it - and adb says no device found]. BUT I can't find a stock firmware/rom/boot.img for it anywhere (mainly since there's a bunch of clones of this tablet). I'm downloading a few roms (in boot.img format? - .7z files) that I found for "this" tablet (meaning the devs don't know which clones which roms work on lol).
ANYWAY haha, my question is, is there a way to do what you said in the above quote that will work in my situation? I'm not advanced enough to know why livesuit says the image is invalid. I tried it with a cm10.1 zip made for this tablet and a cwm zip made for this tablet (for both I extracted the files and then tried flashing the boot.img I found in the directory(extracted folder right?) via livesuit. livesuit said image file invalid for both .img's.
Please help me and THANK YOU in advance.
I'm open to anyone's help and any help is much appreciated! Thanks buttons will be pressed!!!
Same situation
Same Situation but I know the Specs,, It is allwinner A10 .and Stuck in the soft brick
could you solved this problem? i need a help too, the same problem
---------- Post added at 09:21 PM ---------- Previous post was at 09:13 PM ----------
vennkis said:
Same Situation but I know the Specs,, It is allwinner A10 .and Stuck in the soft brick
Click to expand...
Click to collapse
Hi, could you solved that?
i have a Chinese tablet a10, i have repaired different tablets and android phone trough ADB, but this devices is not detected, i have download some software to help me download the tablet drivers, but hasn't possible that.
finally the only source i have, is charge the firmware again, i use phoenix , and i have some rooms in zip format, what can i do for convert to IMG format?
Hello everyone
Finally what can we do?
How to convert .ZIP to .IMG ?
how to convert?
m.morcielago said:
Hello everyone
Finally what can we do?
How to convert .ZIP to .IMG ?
Click to expand...
Click to collapse
m.morcielago said:
Hello everyone
Finally what can we do?
How to convert .ZIP to .IMG ?
Click to expand...
Click to collapse
hahaha...no answer....i am still waiting for this software
doelwit.sunny said:
hahaha...no answer....i am still waiting for this software
Click to expand...
Click to collapse
You know just converting is not enough
I can convert it
But you need "partition table" for making .IMG
So we don't have it
check sdat2img and imgpatchtools
I'm sorry if this isn't the right place.
I rooted my LG G2 D802 around 2 months ago, and completely forgot about it.
I got the Kitkat update about 5 hours ago, and stupidly downloaded it.
The phone got stuck in a team win bootloop and again, in a bit of a panic I wiped the phone (not thinking of just restoring my back up from when i rooted the device)
after that didn't solve anything, i reverted to google. I found a guide on here for my exact problem http://forum.xda-developers.com/showthread.php?t=2451696
I read it carefully and proceeded to follow this by the letter. I think I messed up though, with the 'ADB' thing, the last i remembered about it was using it to root the device, so I followed to guide but using the root folder i had used. now I'm no longer in a team win bootloop, I'm not in a LG splash screen boot loop, I can just about manage to get into recovery and get back to team win, but can't get into download mode.
I really wasn't looking to replace this device until the LG G3 got released, and don't really have the money to spare - so i'm really hoping this is fixable.
a note is, to root the device i followed a guide, and the TWRP (I'm not actually sure) I think i just went with it and managed it so i'm not very good when it comes to the terms, and stuff like that, any help would be greatly appreciated!
I can use a Win7 laptop to do whatever is needed, it is an EE LG G2 D802, UK, 16GB black.
I don't have insurance, I kept pushing myself to wait to do anything like this until I had insurance, but at 2 in the morning, nothing to do, ready to root - It's hard to resist.
(I do have the USB drivers on my laptop)
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
es0tericcha0s said:
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
Click to expand...
Click to collapse
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
I have just had another read through, mainly the comments and that guide seems to get you to the point where you can get into recovery and enter those commands in the guide on my opening post - i can get into recovery and i did both fixes, the one using adb if using the adb in the root folder on my laptop i used to root the device is okay, and then again using the terminal emulator in recovery, after neither worked (actually, the terminal emulator one got me from a TWRP bootloop into an lg splash screen bootloop, after reading into thr comment to about page 7 there was an additional line to the terminal emulator method changing only the /fota to /misc which did nothing for my device. The fix there simply changed the type of bootloop i am in
yoalphadied said:
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
Click to expand...
Click to collapse
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
es0tericcha0s said:
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
Click to expand...
Click to collapse
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
yoalphadied said:
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
Click to expand...
Click to collapse
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: https://mega.co.nz/#!rU0RkSaK!JzUCoZ5emWOsc_Tw6h8a3JZtRNT1-JvGvc8EC_u9rnI
adb and fastboot files: https://mega.co.nz/#!SJ8ijCKY!UKpr4ufVyPq4DVL2i90RI9CD7TX5AETPHrcqMQdpG5w
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Just making sure I understand correctly, the 'rom' i need ks the stock rom, right? Im not looking to root again as the whole reason i rooted was because it was everywhere that ee werent releasing the kitkat update for the g2, since they have now i dont need root anymore.
Ill try this fix later on and tell you if it worked! Thanks
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
yoalphadied said:
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
Click to expand...
Click to collapse
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
http://forum.xda-developers.com/showthread.php?t=2736854
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
es0tericcha0s said:
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
Click to expand...
Click to collapse
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
yoalphadied said:
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
Click to expand...
Click to collapse
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
Okay, I just tried pushing the rom, the line entered, i got no return so far but it won't allow me to type anything else in the CMD, i'm guessing its because it's pushing the file?
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
The recovery is working fine, but after factory resetting, and then trying to install the rom.zip it tries to open it
then e: cant open /data/media/rom.zip
(bad)
installation aborted
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
yoalphadied said:
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
Click to expand...
Click to collapse
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
es0tericcha0s said:
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
Click to expand...
Click to collapse
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
yoalphadied said:
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
Click to expand...
Click to collapse
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
*EDIT*
install Kernal & supersu doesn't resolve the issue, going to try the new rom you posted now
yoalphadied said:
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
Click to expand...
Click to collapse
That's what I would do. Won't make it worse. Might help. If not, it's only a few more minutes altogether to try. Just make sure to wipe cache and dalvik cache.
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Okay, I came across another problem.
with the several versions of the same ROM at /sdcard/ my memory was running low, so i formatted it - then it wouldn't let me push anything to it, anyway i sorted that (can't remember how) and then installed the Kernal and superuser, which didn't seem to sort anything, but I did a little digging and mounted all the directories on Philz.
Then after I restarted the phone, whilst trying to get into recovery I heard the 'LG' splash screen animation noise. and then the phone loaded up the country setting - and then I got an error which made the screen unresponsive, I tried reloading to get yet another error, similar but not the same.
I booted into recovery, did a factory reset and again rebooted the phone and now it works, with the Knock Code! thank you so much you have saved my phone..
Is there anything I can do to say thank you properly, you've just saved me over £250
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Chegger said:
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Click to expand...
Click to collapse
Not the solution, but maybe a cause... did you root your device?
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
harddisk_wp said:
Not the solution, but maybe a cause... did you root your device?
Click to expand...
Click to collapse
Yes I did.
I also thought that was the problem.
delox88 said:
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
Click to expand...
Click to collapse
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Chegger said:
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Click to expand...
Click to collapse
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
harddisk_wp said:
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
Click to expand...
Click to collapse
At least you know this stuff that's half way trough.
I will post this in the original root thread since I already posted the issue there and they are now replying ( I will mention you).
http://forum.xda-developers.com/general/rooting-roms/root-achieved-cat-b15q-t2822015/page11
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've witten you a PM - please send me your original ROM - or could you send me a link where i may download it.
huedlrick said:
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
Click to expand...
Click to collapse
Another one here! Were you able to use link2sd after rooting the phone? Link2sd gave me a mount error when I tried to mount my sd card's 2nd ext3 partition.
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile
1.1019.000 Recovery
Original 1.1019.000 update
Scatter file
To flash the phone you only need the bootimg, recovery,android and scatterfile.
(Edit: I dont have google drive anymore)
bigal1337 said:
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile https : // drive . google . com /file/d/0ByVAMsMZdC8bdEIxWlpBeXBHNUE/view?usp=sharing
1.1019.000 Recovery https : // drive . google . com /file/d/0ByVAMsMZdC8bVXU2RzBGalV0S1U/view?usp=sharing
Original 1.1019.000 update https : // drive . google . com /file/d/0ByVAMsMZdC8bbWQ4dmhSZWVxZVE/view?usp=sharing
Scatter file https : // drive . google . com /file/d/0ByVAMsMZdC8bSkRhREEwakNhUWc/view?usp=sharing
To flash the phone you only need the bootimg, recovery,android and scatterfile.
Click to expand...
Click to collapse
Thank you very much - but how can I determine if my phone is E01/B01 without being able to boot it?
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Great and congrats.
Could you, please, describe the process and which files did you use.
Thanks.
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Can you give some hints how you unbricked it? What tools and commands have to be entered?
Best regards,
Doggy77
Uploads are not done yet. But you can prepare until I'm done... grab the driver package, spFlashTool and the 1.022 RAR from http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774.
You will need a win7 x86 machine for this to work (64-bit systems will need to disable the driver signature enforcement, but this is unreliable), and latest(!) WinRAR for unpacking.
The full backup of your device will take up ~1.5 GB, so you will need at least 3GB free and another 2GB if you also want to backup your userdata (HIGHLY RECOMMENDED).
"PMT changed for the ROM; it must be downloaded"
I'm trying to flash the files of harddisk_wp with his instructions but i keep getting the error "PMT changed for the ROM; it must be downloaded", right after I connect the phone and SP Flash Tool finishes "Download DA". I am trying with the 64bit drivers since I do not have a 32bit system, with digital signature verification disabled.
After some search, I saw in the log files that SP Flash Tool is reading the partition table on the phone and comparing it to the scatter file. There is a mismatch there and throws this exception. Now either the driver is not working correct and does not report the partition table right or there is something else going on. Anybody tried this on a 64bit system? Any ideas?
BTW the scatter file is correct for my phone. I had downloaded it myself also before the bricking and I compared it with harddisk_wp's one. They are identical.
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
walckenaerius said:
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
Click to expand...
Click to collapse
SPFT worked for me good to resurrect the phone with files from 1010 version (first firmware) raw partitions.
Phone came back to last user backup and booted fine.
I applied newer and suggested 1019 update that had bricked the phone even further into the loop of the booting logo stuck and rebooting.
SPFT tool memory scan showed that there is no NAND present. I assume that there is PRELOADER damaged. By trying to flush raw PRELOADER that was a no go area. Connection made red line on 100% and nothing happens after that.
SPFT stopped making connection via USB. Inserting the battery, power on - it didn't came back at all.
Phone is now dead black brick that on Linux shows: as MediaTek Inc. MT6227 phone.
In any case do not try to make the same mistake like me.
I will check if it works on some other Windows machine.
Not being Windows user I cannot tell if it is in USB driver or not.
Used W7 without admin pass, with MTKUsbAll driver.
Eh.
I just got this phone (already rooted) and am trying to flash the new b009 rom with cwm 6.047
; I tried to load the zip file I downloaded by choosing to install it from SD card (internal storage).
But for some reason, the rom does not get installed. Do I have to rename the rom or have to place it somewhere? Or do I need to unzip it?
Please let me know. Help would be much appreciated!!
no need to use CWM recovery. Flashing is native ont this device. See:
http://forum.xda-developers.com/hua...-3-320-dpi-t2923860/post57253214#post57253214
or
https://forum.lowyat.net/index.php?showtopic=3280093&view=findpost&p=69086974
(end of post)
BUT custom recovery may deny this possibility. So you'll have to go back to stock recovery, or maybe find another way to apply the .zip files (maybe via fastboot? Let us know if you find out)
Thanks for your reply.
Djiban said:
no need to use CWM recovery. Flashing is native ont this device. See:
http://forum.xda-developers.com/hua...-3-320-dpi-t2923860/post57253214#post57253214
or
https://forum.lowyat.net/index.php?showtopic=3280093&view=findpost&p=69086974
(end of post)
BUT custom recovery may deny this possibility. So you'll have to go back to stock recovery, or maybe find another way to apply the .zip files (maybe via fastboot? Let us know if you find out)
Click to expand...
Click to collapse
I figured this out myself. Problem solved! Thanks for your reply, though.
But for some reason, I cannot root this device. Even if my phone goes to USB debugging mode, rooting apps - root genius, iroot, kingo root do not recognize it. It says USB debugging mode is turned off. Any advice?
Between, what is the use of cwm if there is no custom rom available?
xsxvvx said:
I figured this out myself. Problem solved! Thanks for your reply, though.
Click to expand...
Click to collapse
Did you Manage to apply .zip update files WITHOUT going back to stock recovery??
But for some reason, I cannot root this device. Even if my phone goes to USB debugging mode, rooting apps - root genius, iroot, kingo root do not recognize it. It says USB debugging mode is turned off. Any advice?
Click to expand...
Click to collapse
for the USB debugging issue:
1) test with different cables and PC USB ports.
2) reinstall drivers on your PC, and test.
3) install adb, and test with the "adb devices" command
to root:
if still no usb debugging mode, try out the iroot app directly on your androphone:
http://www.mgyun.com/m/en
Between, what is the use of cwm if there is no custom rom available?
Click to expand...
Click to collapse
Nandroid backup, at least!!!!
The only custom ROM are official-ROM-based (like KangVIP, look for it in this forum), absolutly not the same custom than a CWM or Omi .
Guide to rooting infocus Epic 1 (for windows) for build 00.
This method is only tested on build 00IN_1_360 only. If you are on the older build, first update your phone to build 00IN_1_360 then proceed. Check Build number in settings->about phone.
Proceed at your own risk, I will not be help responsible if your phone bricks, Your warranty will be void after this. Also all phone data will be lost including data on internal memory like photos, etc after these steps so take necessary backups.
Prepare your system
1. Extract and Install MTK Driver Auto Installer v5.1632 (google it)
2. Install Phone F Driver (from phone CD-emulation/driver folder upon connecting your phone)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
4. Download latest SuperSU flashable zip file from here
5. Download twrp-3.0.3-0-epic1-noveritynoencrypt.zip from here, extract in the folder where you have installed adb and fastboot
6. Download noencryptnoverty_boot.zip from attachments and extract to folder where you have installed adb and fastboot
Steps to root:
1. Enable Developer options in phone settings (goto phone settings -> about phone -> tap build number 7 times)
1a. Enable OEM unlock
1b. Enable USB Debugging
2. Connect phone to computer, wait for hardware to auto install
3. open cmd as administrator
3a. goto the directory where adb and fastboot is installed
4. type command:
4a.
adb reboot bootloader
(Wait for phone to come in fastboot)
4b.
fastboot OEM unlock
(press vol up key on phone)
4c.
fastboot flash boot noveritynoencrypt.img
4d.
fastboot flash recovery recovery.img
4e.
fastboot reboot
You will get an phone orange state prompt, do not worry its normal. Phone may reboot once or twice. Wait for phone to normal bootup.
5. open cmd and type command
5e.
adb reboot recovery
Phone will reboot in recovery i.e. TWRP
6. Tap on Keep system read-only. Do not swipe to allow modifications. If TWRP asks for password, don't enter any press back.
7a. Tap Wipe -> Format Data. Come out to main menu, then click reboot and then recovery to restart recovery.
7b. Tap Wipe -> Advanced Wipe -> Select Dalvik /ART, Cache, Data and Internal Storage. This is important step, as these partitions are encrypted at the moment, so if you flash anything the phone rom may corrupt.
8. Come out and then Tap Reboot -> System
9. Once the phone is back, turn off the phone. Then power on with vol up key pressed to boot into TWRP
10. Tap Backup, select all partitions, select phone storage (SD card preferred) and take backup (optional step but highly recommended )
11. Now tap install, goto the location where you had copied SuperSU zip file, flash it.
Congratulations your Phone is rooted. Reboot, see SuperSU icon in app drawer.
Many thanks to @mujammil786 for providing stock files and @Bornstud for testing twrp builds
Special thanks to our devs @DespairFactor for modifying boot.img to disable Encryption and Verity and @kirito9 for creating TWRP for our device. Without their help, it wouldn’t have been possible.
MODS
(Take backup of your ROM/Data before applying any mods)
Viper4Android (Advanced Sound Enhancement)
Hugely Customizable and better than MaxxAudio or Dolby Atmos IMHO
Now working on our device Infocus Epic 1
Need to flash the 2 attached files via TWRP before installing the official app from HERE. Although latest version v2.5.0.5 also works, but i personally prefer v2.4.0.1 (busybox required)
(Note the attached files are not my work, they are picked from here and here. Say thanks to original contributors.)
Good V4A profile: HERE
Extract it to ViPER4Android Directory in internal Storage
Xposed
Needs no introduction. Every android enthusiast should know what it is. Anyway if you are new, xposed opens limitless ROM customization(s) and useful features via 100s of its modules.
Installation:
1. Flash framework xposed-v87-sdk23-arm64.zip from HERE via TWRP. Reboot after installation will take long time (~10 - 15 minutes)
2. Install app XposedInstaller_3.1.1.apk from HERE
Restoring phone back through SUT
If you are stuck somewhere or want to restore the phone factory state (like for when giving to repair), you can restore the phone back via SUT
Link for build 1280: https://firmwarefile.com/infocus-epic-1
Also dont turn off your phone as suggested in sut readme file. It only works when your phone is on. Check below vid for more instructions
https://m.youtube.com/watch?v=eV_cId5fC9E
Reduce battery consumption & phone temperature
Found an interesting thread, mod works on our device also
https://forum.xda-developers.com/red...tings-t3687897
I have tried both flavor 1 and flavor 2 over the past week. Results with flavor 1 were positive in the beginning but for some reason standby drain shot up after 3-4 days, not sure what the reason was.
On flavor 2, I have just disabled MTK perfservice by setting
ro.mtk_perfservice_support = 0 in build.prop
Yes this limits the a72 core to 1.5ghz, but i have noticed phone is heating less and need for charging the phone has reduced. I haven't noticed much drop in performance either, but that might be as I don't use intensive apps.
Mafioso said:
I've managed to unpack nb0 file through a688 tool, however its only successful in unpacking few files before it crashes with some array size error, but the good thing is I was able to extract the scatter file for this phone before it happened.
Anyway, I was hopeful that I would be able to make backup of Stock ROM and Recovery through it via spflash tools however as it turns out, spflash tool is giving me error while doing readback BROM ERROR: STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003)
Not sure how to fix it, i've updated my drivers as well as i'm using latest version of spflash tool (SP_Flash_Tool_v5.1628_Win)
Attaching scatter file.
Click to expand...
Click to collapse
From where uve downloaded the stock firmware
Romeotamizh said:
From where uve downloaded the stock firmware
Click to expand...
Click to collapse
http://firmwarefile.com/infocus-epic-1
Mafioso said:
http://firmwarefile.com/infocus-epic-1
Click to expand...
Click to collapse
Oh
---------- Post added at 08:17 AM ---------- Previous post was at 08:17 AM ----------
Romeotamizh said:
Oh
Click to expand...
Click to collapse
Look in other sites bro for img files
Romeotamizh said:
Oh
---------- Post added at 08:17 AM ---------- Previous post was at 08:17 AM ----------
Look in other sites bro for img files
Click to expand...
Click to collapse
Hmm yaa, but at the moment no sites with for .img file for this phone. All sites point to this image only. Let's hope somebody posts. Thanks!
Mafioso said:
Hmm yaa, but at the moment no sites with for .img file for this phone. All sites point to this image only. Let's hope somebody posts. Thanks!
Click to expand...
Click to collapse
Ooh bro I'm happy to help but seriously i Duno about these kind of extensions hope u understand
Mafioso said:
I'm trying to root Infocus Epic 1, its a good budget phone with decent specs. Availability is only in India, not sure other regions. Anyway I'm having hard time to root it, since not much support is available. But so far, I have tried below things:
1. Tried to root with Kingroot, doesn't work .Probably because it is very new version of Marshmallow with Oct'16 patch level and kernel dated in dec 16.
2. Tried to generate scatter file via MTK Droid tool v2.5.3, after enable USB debugging in phone. The phone get detected in the tool, however create scatter file option in block map is disabled I've read somewhere, it might be due to MTK6797 (Helios x20) is quite new and is not yet fully supported by tool yet. Not sure if its true though. But if I can generate scatter file, I can extract phone's stock recovery via SPFlash tool readback to try a hand at porting twrp/cwm with some help..
3. Downloaded stock Infocus Epic 1 firmware in hope for recovering stock recovery.img or MTK scatter file, however on unpacking the firmware package, I found it contains unknown image file of nb0 extension which is it to be flashed via SUT Tool. Not sure how to unpack this file
Any more ideas, how can i atleast start with my quest to root/put custom recovery on this phone ? @Romeotamizh Pls help.
Click to expand...
Click to collapse
I can give u stock recovery of epic 1..
mujammil786 said:
I can give u stock recovery of epic 1..
Click to expand...
Click to collapse
how bro, are you able to get it via SPFlash tool readback option or are you able to unpack the nb0 file ?
Anyway you should post it here, somebody else might pick it up and build twrp for it. At the moment, I'm stuck with SPFlash tool unable to readback my phone as stated above , doubt i would be able to flash anything to test
Mafioso said:
how bro, are you able to get it via SPFlash tool readback option or are you able to unpack the nb0 file ?
Anyway you should post it here, somebody else might pick it up and build twrp for it. At the moment, I'm stuck with SPFlash tool unable to readback my phone as stated above , doubt i would be able to flash anything to test
Click to expand...
Click to collapse
I was able to extract it from last update zip
---------- Post added at 04:45 PM ---------- Previous post was at 04:33 PM ----------
Epic 1 stock recovery
https://drive.google.com/file/d/0B4FNo4vddleCNmpwcS1hS3FLam8/view?usp=drivesdk
mujammil786 said:
I was able to extract it from last update zip
Click to expand...
Click to collapse
ok I see, please post it here. I can update it in the first post. Might be useful for anyone willing to develop for this phone.
Also did you try to read-back the phone via SPFlash tool ? I'm running into issues, but maybe i'm not doing something correctly. Might be you will have better luck.
Mafioso said:
ok I see, please post it here. I can update it in the first post. Might be useful for anyone willing to develop for this phone.
Also did you try to read-back the phone via SPFlash tool ? I'm running into issues, but maybe i'm not doing something correctly. Might be you will have better luck.
Click to expand...
Click to collapse
Well i tried but i got ctrl device error ,btw i have uploaded stock recovery
mujammil786 said:
Well i tried but i got ctrl device error ,btw i have uploaded stock recovery
Click to expand...
Click to collapse
thanks, updated first post.
Mafioso said:
thanks, updated first post.
Click to expand...
Click to collapse
Thanks let's hope for best
I like this phone and the only thing lacking is Root, Hope someone will do it
I hope so too. However, it seems its not that straight forward anymore i.e. communicating with SPFlash tool on newer MTK chipsets. I was going through guides for LeTV x620 (also with MT6797), not sure but it seems they require authentication file now for the process, which might not be available for our phone.
I already tried all the other download agents like DA_PL.bin, DA_PL_High.bin, DA_BR.bin in flash tool through which this LeTV is able to communicate, it's same error for us with all.
Also other curious thing, I was unable to run any fastboot commands on this phone. The phone gets detected in fastboot when put in fastboot mode (vol - + power) i.e. I get output on fastboot devices.
However If i try to run any commands like fastboot oem get-bootinfo or fastboot oem device-info I get error message remote command unknown
Mafioso said:
I hope so too. However, it seems its not that straight forward anymore i.e. communicating with SPFlash tool on newer MTK chipsets. I was going through guides for LeTV x620 (also with MT6797), not sure but it seems they require authentication file now for the process, which might not be available for our phone.
I already tried all the other download agents like DA_PL.bin, DA_PL_High.bin, DA_BR.bin in flash tool through which this LeTV is able to communicate, it's same error for us with all.
Also other curious thing, I was unable to run any fastboot commands on this phone. The phone gets detected in fastboot when put in fastboot mode (vol - + power) i.e. I get output on fastboot devices.
However If i try to run any commands like fastboot oem get-bootinfo or fastboot oem device-info I get error message remote command unknown
Click to expand...
Click to collapse
My device does not get detect in fastboot can u show me screen shot of command u are trying....
mujammil786 said:
My device does not get detect in fastboot can u show me screen shot of command u are trying....
Click to expand...
Click to collapse
If it's not detected maybe its related to your drivers. I've installed the following drivers
1. Try installing the Phone F Driver (from phone CD-emulation upon connecting)
2. MTK Driver Auto Installer v5.1632.00 (you can get from needrom)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
Run cmd as administrator:
adb reboot bootloader
When phone reboots in fastboot mode
fastboot devices
You should see your phone being detected from above.
Mafioso said:
If it's not detected maybe its related to your drivers. I've installed the following drivers
1. Try installing the Phone F Driver (from phone CD-emulation upon connecting)
2. MTK Driver Auto Installer v5.1632.00 (you can get from needrom)
3. Minimal ADB and Fastboot installer v.1.4.2 (from xda)
Run cmd as administrator:
adb reboot bootloader
When phone reboots in fastboot mode
fastboot devices
You should see your phone being detected from above.
Click to expand...
Click to collapse
Ok will try thanx
bootloder get unlocked and locked too
ok so phone get detected in fastboot mode:victory: .was able to lock and unlock boot loader but without custom recovery it is no useful for us.
unlocked bootloader.
tried flashing Vernee_Apollo_Lite_P6(same spec. as epic 1) twrp recovery.
flashing done but after flashing phone refused to boot.
flashed stock recovery from update zip.
locked bootloader.
phone booted but erased internal memory after boot.
---------- Post added at 11:47 AM ---------- Previous post was at 11:44 AM ----------
do you know any guide for making twrp and i think phone will not boot if it detect any change in system partition i think