This is a question thread for people who have Clone Phones by HDC, Goophone, Tengda, iHD, and other manufacturers' phones that are based upon an existing phone by a major manufacturer.
The design of this thread is equal to this
Make sure to read the Forum Rules before posting
Anyone can answer.
All questions are welcome!
Hardware: MT6572 (MTK6595 IS FAKE) MODEL :S960c
Hi Xda,
I have a fake Lenovo S960c (didn't knew before i purchased it) , after i rooted it with kingo user, because there was a malware which was located only by rooting . the malware was removed , but after few months the same type of malware came again but this time there was two or three malware which was causing my battery to drain and i couldn't charge my phone battery to 100% . My Antivirus Showed my Mediatek file had a malware , i didnt know so i uninstalled that file after my phone restarted it is caught in bootloop and won't go beyond the lenovo logo.
Please advise how can i solve this problem as i have been scammed when i bought this phone from Aliexpress,
thinking this was a real MTK6595 MODEL original Lenovo phone. I have written below my phone's real spec which
i got using Mtk droid tools for your reference. please advise how can i fix my phone again.
Hardware: Mtk6572 (Mtk6595 is fake)
Model: S960c
Build Number : S5_JB3_3G_EMMC_QHD_32_4_XLD_Z12_LENO
Build Date : 20150417-064045
Andriod v: 4.4.3
Baseband: ____
Kernel v: 3.4.5([email protected])(gcc version 4.6x-google 20120106 (prerelease)(GCC)#1 SMP Fri Apr 17
18:02:31 CST 2015
sufyan nuhammad said:
Hi Xda,
I have a fake Lenovo S960c (didn't knew before i purchased it) , after i rooted it with kingo user, because there was a malware which was located only by rooting . the malware was removed , but after few months the same type of malware came again but this time there was two or three malware which was causing my battery to drain and i couldn't charge my phone battery to 100% . My Antivirus Showed my Mediatek file had a malware , i didnt know so i uninstalled that file after my phone restarted it is caught in bootloop and won't go beyond the lenovo logo.
Please advise how can i solve this problem as i have been scammed when i bought this phone from Aliexpress,
thinking this was a real MTK6595 MODEL original Lenovo phone. I have written below my phone's real spec which
i got using Mtk droid tools for your reference. please advise how can i fix my phone again.
Hardware: Mtk6572 (Mtk6595 is fake)
Model: S960c
Build Number : S5_JB3_3G_EMMC_QHD_32_4_XLD_Z12_LENO
Build Date : 20150417-064045
Andriod v: 4.4.3
Baseband: ____
Kernel v: 3.4.5([email protected])(gcc version 4.6x-google 20120106 (prerelease)(GCC)#1 SMP Fri Apr 17
18:02:31 CST 2015
Click to expand...
Click to collapse
Most likely, the malware was caused by a required system app. Maybe the dialer, MMS, or search app? Whenever the app sweeps your phone to check and sees there is no malware app, it connects to a server and, unbeknownst to you, installs it as a system app.
Do you know the actual manufacturer? In antutu it would show Zen, Alps, Wen, Next, or another OEM name. If so, that helps a lot in recovering your OEM mtk phone.
Your phone is recognized by mtk droid tools right? If so, you should be able to go into recovery as well. Even make cwm which should help
Sent from my SGH-M919 using XDA Free mobile app
Hardware: MT6572 (MTK6595 IS FAKE) MODEL :S960c
Qiangong2 said:
Most likely, the malware was caused by a required system app. Maybe the dialer, MMS, or search app? Whenever the app sweeps your phone to check and sees there is no malware app, it connects to a server and, unbeknownst to you, installs it as a system app.
Do you know the actual manufacturer? In antutu it would show Zen, Alps, Wen, Next, or another OEM name. If so, that helps a lot in recovering your OEM mtk phone.
Your phone is recognized by mtk droid tools right? If so, you should be able to go into recovery as well. Even make cwm which should help
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
First of all thanks for your kind Reply , really appreciated , when its comes to android, I am a toddler , not much experience in installing or flashing roms or making recoveries either. Please guide me step by step way , like a child
how to fix my phone again , as my hard earned money will go down the drain. if try to flash or do something else,
already i made it stuck on boot loop.
:good::good:
Regards
Sufyan
sufyan nuhammad said:
First of all thanks for your kind Reply , really appreciated , when its comes to android, I am a toddler , not much experience in installing or flashing roms or making recoveries either. Please guide me step by step way , like a child
how to fix my phone again , as my hard earned money will go down the drain. if try to flash or do something else,
already i made it stuck on boot loop.
:good::good:
Regards
Sufyan
Click to expand...
Click to collapse
No problem, I'm happy to help.
1. Is your phone still recognized when you plug it in to mtk droid tools?
2. Do you know what the actual manufacturer of your phone? If so, what?
3. What was the name of the file you deleted? (not needed, but it might help)
Qiangong2
Hardware: MT6572 (MTK6595 IS FAKE) MODEL :S960c
Qiangong2 said:
No problem, I'm happy to help.
1. Is your phone still recognized when you plug it in to mtk droid tools?
2. Do you know what the actual manufacturer of your phone? If so, what?
3. What was the name of the file you deleted? (not needed, but it might help)
Qiangong2
Click to expand...
Click to collapse
Yes , its does when i connect it to the droid tools it says in the message window,
Attention fake hardware in kernel or firmware doesn't correspond to phone
Attention File/system/Recovery-from-boot-p which restore factory recovery in case of phone
switching on in a normal mode is found.
also in left side menu the beside yellow light there is a message which says ,
S960c system/bin/su is found! Via root button it is possible to get root shell.
then when i press root button this message appears ,
to try to receive root shell through already established su .
I press yes to the button, after a while this error pop's up ,
Loss of communication with the device! the program will be closed.
I press OK then the software window is gone.
I am sorry, really don't know the actual manufacturer of the phone , i even did an tutu test but really , i only remember is the fake specs that mesmerized me a lot nothing else ,
The Files I deleted where Mediatek file , i bingo as the Anti Virus showed serious Malware in them.
sufyan nuhammad said:
Yes , its does when i connect it to the droid tools it says in the message window,
Attention fake hardware in kernel or firmware doesn't correspond to phone
Attention File/system/Recovery-from-boot-p which restore factory recovery in case of phone
switching on in a normal mode is found.
Click to expand...
Click to collapse
The first "Attention" shouldn't matter, it's just reading the build.prop which claims that it is an MT6595 instead of an MT6572. The second "Attention" is more interesting. I've actually never seen that one before, but it seems like there was some error in the ROM, and (when there is) it defaults to booting to factory/stock recovery.
also in left side menu the beside yellow light there is a message which says ,
S960c system/bin/su is found! Via root button it is possible to get root shell.
then when i press root button this message appears ,
to try to receive root shell through already established su .
I press yes to the button, after a while this error pop's up ,
Loss of communication with the device! the program will be closed.
I press OK then the software window is gone.
Click to expand...
Click to collapse
You may already have root, or it may not be there anymore. Try opening adb (from the adb button) and type:
Code:
adb devices
If your phone is recognized, type:
Code:
adb shell
Then (if it works) type:
Code:
su
if you see a # sign right next to where you type, then you have root.
I am sorry, really don't know the actual manufacturer of the phone , i even did an tutu test but really , i only remember is the fake specs that mesmerized me a lot nothing else ,
Click to expand...
Click to collapse
That's okay, it will just be harder to find information about your device firmware, not impossible though.
The Files I deleted where Mediatek file , i bingo as the Anti Virus showed serious Malware in them.
Click to expand...
Click to collapse
That should be fine... Mediatek files can be required or useless. Most of the time they only activate if you enter factory test mode. Since they had malware in them, they shouldn't be needed.
Qiangong2 said:
The first "Attention" shouldn't matter, it's just reading the build.prop which claims that it is an MT6595 instead of an MT6572. The second "Attention" is more interesting. I've actually never seen that one before, but it seems like there was some error in the ROM, and (when there is) it defaults to booting to factory/stock recovery.
You may already have root, or it may not be there anymore. Try opening adb (from the adb button) and type:
Code:
adb devices
If your phone is recognized, type:
Code:
adb shell
Then (if it works) type:
Code:
su
if you see a # sign right next to where you type, then you have root.
That's okay, it will just be harder to find information about your device firmware, not impossible though.
That should be fine... Mediatek files can be required or useless. Most of the time they only activate if you enter factory test mode. Since they had malware in them, they shouldn't be needed.
Click to expand...
Click to collapse
Sorry i forgot to tell you that when my phone was in OK condition , i did root it with kingo root , so do you think , it
is still rooted while caught in boot loop. sorry for not telling you the complete details. So should i follow the above mentioned details , also where would i find the adb button , is it when i connect the phone through droid tools it will appear there or you are talking about phone recovery menu.
---------- Post added at 11:29 AM ---------- Previous post was at 11:22 AM ----------
sufyan nuhammad said:
Sorry i forgot to tell you that when my phone was in OK condition , i did root it with kingo root , so do you think , it
is still rooted while caught in boot loop. sorry for not telling you the complete details. So should i follow the above mentioned details , also where would i find the adb button , is it when i connect the phone through droid tools it will appear there or you are talking about phone recovery menu.
Click to expand...
Click to collapse
i tried all your commands mentioned above while pressing Adb Terminal Buttton, in the end the command line showed # as you have mentioned , now what should i do please advise. once again thanks for your efforts brother.
sufyan nuhammad said:
Sorry i forgot to tell you that when my phone was in OK condition , i did root it with kingo root , so do you think , it
is still rooted while caught in boot loop. sorry for not telling you the complete details. So should i follow the above mentioned details , also where would i find the adb button , is it when i connect the phone through droid tools it will appear there or you are talking about phone recovery menu.
---------- Post added at 11:29 AM ---------- Previous post was at 11:22 AM ----------
i tried all your commands mentioned above while pressing Adb Terminal Buttton, in the end the command line showed # as you have mentioned , now what should i do please advise. once again thanks for your efforts brother.
Click to expand...
Click to collapse
You have root so you are stuck in bootloop. The bootloop seems to be caused by mediatek file now...
Have you removed any other files? Also, where was the file placed that you removed?
Qiangong2 said:
You have root so you are stuck in bootloop. The bootloop seems to be caused by mediatek file now...
Have you removed any other files? Also, where was the file placed that you removed?
Click to expand...
Click to collapse
As i mentioned before i only removed the file from settings, then click app, then all files , from there i uninstalled mediatek file and iBingo file nothing else. . Please advise what to do now.
sufyan nuhammad said:
As i mentioned before i only removed the file from settings, then click app, then all files , from there i uninstalled mediatek file and iBingo file nothing else. . Please advise what to do now.
Click to expand...
Click to collapse
The mediatek file is the problem then. We need to figure out what exactly the file is and also whether it is a customised file or a generic. If it is generic, then we can just copy it from another MT6572 phone with the same screen aspect ratio. If it is customised, then we need to somehow recover the file, or just get a copy of the stock firmware from the manufacturer.
On a side note: have you tried pulling a copy of your stock ROM out using adb? It may be able to shine some light onto what exactly the file affected. If you can't, that's fine. We'll just move on
Qiangong2 said:
The mediatek file is the problem then. We need to figure out what exactly the file is and also whether it is a customised file or a generic. If it is generic, then we can just copy it from another MT6572 phone with the same screen aspect ratio. If it is customised, then we need to somehow recover the file, or just get a copy of the stock firmware from the manufacturer.
On a side note: have you tried pulling a copy of your stock ROM out using adb? It may be able to shine some light onto what exactly the file affected. If you can't, that's fine. We'll just move on
Click to expand...
Click to collapse
Sorry, Brother i don't really know if the file is generic or Customised one, i only remember when i uninstalled mediatek and i bingo , the first error which came up was some google gaaps type error , it asked me to repair it i clicked OK , then my phone restarted and when into boot loop. I wish i new how to do adb backup and copy my stock ROM , as i said earlier not a pro , not even a rookie , just a dumb toddler who doesn't know much about android apps and system mechanics . sorry to put you in a mess brother. thanks for your cooperation
sufyan nuhammad said:
Sorry, Brother i don't really know if the file is generic or Customised one, i only remember when i uninstalled mediatek and i bingo , the first error which came up was some google gaaps type error , it asked me to repair it i clicked OK , then my phone restarted and when into boot loop. I wish i new how to do adb backup and copy my stock ROM , as i said earlier not a pro , not even a rookie , just a dumb toddler who doesn't know much about android apps and system mechanics . sorry to put you in a mess brother. thanks for your cooperation
Click to expand...
Click to collapse
Okay, go into adb from mtk droid tools, and type:
Code:
adb shell
Then (once it connects) type:
Code:
su
Now you have root. Next type this:
Code:
cat /proc/partitions
To find out which partition contains your system.img, your boot.img, and your data.img.
If none of the partitions say system or boot. Then make a copy of the partition list and upload it. We'll go from there.
Qiangong2 said:
Okay, go into adb from mtk droid tools, and type:
Code:
adb shell
Then (once it connects) type:
Code:
su
Now you have root. Next type this:
Code:
cat /proc/partitions
To find out which partition contains your system.img, your boot.img, and your data.img.
If none of the partitions say system or boot. Then make a copy of the partition list and upload it. We'll go from there.
Click to expand...
Click to collapse
i followed the instructions and type the command adb shell , from there , the com and line became like this
[email protected]:/$ when i typed su beside this this error came {-} connection to ui timed out , i still went with the last command and when i wrote cat /proc/partitions , this is whats happened afterwards,
major minor #blocks name
7 0 1254 loop0
179 0 3795968 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 665600 mmcblk0p4
179 5 385024 mmcblk0p5
179 6 1355776 mmcblk0p6
179 7 1332992 mmcblk0p7
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 96 3933184 mmcblk1
179 97 3929088 mmcblk1p1
[email protected]:/ $ mmc
Did i do something wrong or is this what you are looking for , please advise me .
sufyan nuhammad said:
i followed the instructions and type the command adb shell , from there , the com and line became like this
[email protected]:/$ when i typed su beside this this error came {-} connection to ui timed out , i still went with the last command and when i wrote cat /proc/partitions , this is whats happened afterwards,
major minor #blocks name
7 0 1254 loop0
179 0 3795968 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 665600 mmcblk0p4
179 5 385024 mmcblk0p5
179 6 1355776 mmcblk0p6
179 7 1332992 mmcblk0p7
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 96 3933184 mmcblk1
179 97 3929088 mmcblk1p1
[email protected]:/ $ mmc
Did i do something wrong or is this what you are looking for , please advise me .
Click to expand...
Click to collapse
This is what we're looking for. mmcblk0 is the entire device. it seems like mmcblk0p4 is the system.img as it is the largest partition within device mmcblk0.
use this:
Code:
cat dev/block/mmcblk0p4 /sdcard/system.img
Which should save your system partition as a .img file on your sdcard which, once transferred to your computer, you can open with the applications ext2read and ext2explore (both on sourceforge)
Repeat previous code, replacing mmcblk0p4 with: mmcblk0p6, mmcblk0p7, and mmcblk0p5. those should bring out your boot.img and your recovery.img at least. use the perl scripts I've attached to unpack those. the instructions are in the readme file.
You are gonna be hard pressed to learn android on a knock off device. No real developer will even touch it.
Qiangong2 said:
This is what we're looking for. mmcblk0 is the entire device. it seems like mmcblk0p4 is the system.img as it is the largest partition within device mmcblk0.
use this:
Code:
cat dev/block/mmcblk0p4 /sdcard/system.img
Which should save your system partition as a .img file on your sdcard which, once transferred to your computer, you can open with the applications ext2read and ext2explore (both on sourceforge)
Repeat previous code, replacing mmcblk0p4 with: mmcblk0p6, mmcblk0p7, and mmcblk0p5. those should bring out your boot.img and your recovery.img at least. use the perl scripts I've attached to unpack those. the instructions are in the readme file.
Click to expand...
Click to collapse
i started in adb, then command line by typing cat dev/block/mmcblk0p4 /sdcard/system.img but it said
'cat' is not a recognized as an internal or external command, operable program or batch file.
then i retyped adb shell , then su then i typed this cat dev/block/mmcblk0p4 /sdcard/system.img
this error show up
/system/bin/sh: cat: dev/block/mmcblk0p4 / permission denied
/system/bin/sh: cat: /sdcard/system.img / no such file or directory
1 :[email protected]:/ $
now what should i do , please advise.
sufyan nuhammad said:
i started in adb, then command line by typing cat dev/block/mmcblk0p4 /sdcard/system.img but it said
'cat' is not a recognized as an internal or external command, operable program or batch file.
then i retyped adb shell , then su then i typed this cat dev/block/mmcblk0p4 /sdcard/system.img
this error show up
/system/bin/sh: cat: dev/block/mmcblk0p4 / permission denied
/system/bin/sh: cat: /sdcard/system.img / no such file or directory
1 :[email protected]:/ $
now what should i do , please advise.
Click to expand...
Click to collapse
You could always just do a backup in mtk droid tools.
To do this,
1) connect your phone to the computer
2) open mtk droid tools
3) when the information shows up, click root button to get root shell (if you don't already have root shell). Then, click the root, backup, and recovery tab.
4) click backup. It is now starting to backup your phone. It doesn't matter if you pack it or not at the end.
All of the files should be in the mtk droid tools backup folder.
Qiangong2 said:
You could always just do a backup in mtk droid tools.
To do this,
1) connect your phone to the computer
2) open mtk droid tools
3) when the information shows up, click root button to get root shell (if you don't already have root shell). Then, click the root, backup, and recovery tab.
4) click backup. It is now starting to backup your phone. It doesn't matter if you pack it or not at the end.
All of the files should be in the mtk droid tools backup folder.
Click to expand...
Click to collapse
when i click root in droidtools . this message then this message shows up
to try to receive root shel through already established su? i clicked yes , after a while in the left side message screen it shows : error su inaccessible . i retried again this time i click no , but this time in the message screen there was a different message :
Through CWM it is possible to get root on this phone! Look URLs :
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
please tell what to do .
---------- Post added at 05:50 PM ---------- Previous post was at 05:49 PM ----------
sufyan nuhammad said:
when i click root in droidtools . this message then this message shows up
to try to receive root shel through already established su? i clicked yes , after a while in the left side message screen it shows : error su inaccessible . i retried again this time i click no , but this time in the message screen there was a different message :
Through CWM it is possible to get root on this phone! Look URLs :
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
please tell what to do .
Click to expand...
Click to collapse
also this message was included
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
sufyan nuhammad said:
when i click root in droidtools . this message then this message shows up
to try to receive root shel through already established su? i clicked yes , after a while in the left side message screen it shows : error su inaccessible . i retried again this time i click no , but this time in the message screen there was a different message :
Through CWM it is possible to get root on this phone! Look URLs :
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
please tell what to do .
---------- Post added at 05:50 PM ---------- Previous post was at 05:49 PM ----------
also this message was included
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Click to expand...
Click to collapse
please help me if you are not busy, waiting for your reply.
Related
Hello:
I'm a buyer of an Iview 760TPC (chinese 1.3Mpx camera version).
The reason I'm writing is because its some days reading and trying things to get everything unlocked, and seems that is really impossible to flash a new firmware or to get root. I'm getting really mad.
- I have managed to get adb recognize the tablet on linux and on windows. Despite of that, I get "adbd cannot run on production builds".
- If I do an 'adb shell', I get a prompt (with no superuser privileges). If I try to 'su', I get a "Passwd:" prompt , so I cannot get a superuser prompt to remount the filesystems, neither push any file to /system.
Browsing, I see there's no 'su' on /system/bin but there's on /system/xbin. Is a read-only filesystem and I cannot push anything.
- I installed root explorer but cannot mount R/W the filesystems.
- Installed Busybox installer. Says that the tablet is rooted, but when I try to install busybox, says that I have not permissions. Same if I try one of the upgrade menus of superuser. There are not privileges.
- I tried many times, to flash a firmware with the livesuit method, but the tablet is not being recognized. When I do the combination to enter the flashing mode, it boots a like a recovery with 4 options:
1) erase user data partition
2) enter adfu
3) upgrade firmware from sdcard
4) exit menu
I'm interested in the 3er option, but I can't find any information of the process itself (where to put the firmware, if its the same img as with the livesuit method, and what name needs to have the file)
There's also an ADFU mode, that I don't understand, but windows recognizes a new device when I enter there (but there's no driver or information I can found). The screen gets like a bit of white color, and the only way to exit from there is to press home+power buttons without the usb cable.
I've tried superoneclick but it doesn't work because there's not 'su' binary. Same happens with the installers of the CWM, not working because there's no 'su' (so I could flash a file with any kind of name)
Any help would be aprecciated. Sorry for my engrish and for asking so much, but I don't know how to proceed ;-)
Thanks
What version of Android is the device running? You could try manually pushing an exploit binary (e.g. zergrush) onto the device and executing to get temp root, at which point you should be able to mount /system as R/W and then push the su binary to /system/bin
The exploit binary to use would depend on the version of Android though. zergrush is for 2.3 I think (maybe 2.3.something). For early versions of ICS (4.0), there is mempodroid (might have spelt that wrong).
EDIT: Also, everything you can do over ADB, you could do by installing SSHDroid on the device and connecting via SSH from a computer.
Thanks a lot for your answer SifJar:
The tablet comes with ICS 4.0.3 and 3.0.8 kernel.
Superoneclick has the psneuter and zergRush exploits(neither of those seem to work for me).
Found this thread:
http://forum.xda-developers.com/showthread.php?t=1461736
Edit: It does not work for me:
./adb shell
[email protected]:/ $ chmod 777 /data/local/mempodroid
[email protected]:/ $ /data/local/mempodroid 0xd9ec 0xaf47 sh
/system/bin/sh: /data/local/mempodroid: not executable: magic 7F45
Thanks
Installed SSHDroid from the Play Store, but does not work either.
I get:
Can't generate RSA keys: sh <stdin>[1]: /data/data/berserker.android.apps.sshdroid/dropbear/dropbearkey: not executable: magic 7F45
Don't really know what else can I do.
Thanks
mempodroid requires a different offset for each device. "0xd9ec 0xaf47 sh" is for the Eee Pad Transformer Prime. You need to get the right offset for your device. You can try this to do that: http://forum.xda-developers.com/showthread.php?t=1612591
EDIT: But it looks like your device may not be able to run standard Android binaries, which would be quite an inconvenience for trying to root it.
SifJar said:
mempodroid requires a different offset for each device. "0xd9ec 0xaf47 sh" is for the Eee Pad Transformer Prime. You need to get the right offset for your device. You can try this to do that: http://forum.xda-developers.com/showthread.php?t=1612591
EDIT: But it looks like your device may not be able to run standard Android binaries, which would be quite an inconvenience for trying to root it.
Click to expand...
Click to collapse
I think I should reflash a new firmware from that recovery that has from factory, but there's no way I can do it. I mean, it is supposed to have an special mode that you enter with a button combination and to flash then with livesuit, but in this chinese clone, does not seem to work that combination of buttons.
From the recovery, ADFU seems to mean Actions Device Firmware Update. There's some information here http://wiki.s1mp3.org/USB_modes
- If I put the device in ADFU mode, windows ask for an USB driver (that I don't have or does not exist either)
- Another thing. There's a flashing from sdcard, that seems to support, but there's no information or manual of where is supposed to put the firmware, the name of the file or if it needs to be zipped (and what file/s inside and names),...
Thanks
It's possible the flashing from sd card supports standard update .ZIPs. You could try this one, it's a ZIP that should work for rooting most Android devices I believe. Superuser.zip
(This is from a topic on the HTC Explorer phone, but there is nothing specific to that phone in the ZIP as far as I know)
EDIT: This ZIP doesn't overwrite the firmware or anything, all it does is add su, busybox and Superuser to the existing /system partition.
EDIT: If selecting the "Update firmware from SD card" option doesn't give the option to browse for a ZIP, rename it to "update.zip" and place it in the root of the card and try again.
SifJar said:
It's possible the flashing from sd card supports standard update .ZIPs. You could try this one, it's a ZIP that should work for rooting most Android devices I believe. Superuser.zip
(This is from a topic on the HTC Explorer phone, but there is nothing specific to that phone in the ZIP as far as I know)
EDIT: This ZIP doesn't overwrite the firmware or anything, all it does is add su, busybox and Superuser to the existing /system partition.
EDIT: If selecting the "Update firmware from SD card" option doesn't give the option to browse for a ZIP, rename it to "update.zip" and place it in the root of the card and try again.
Click to expand...
Click to collapse
Thanks a lot. Does not have a browsing option so I need to know the needed name. Does not seem to work with the update.zip method
Does it try to install update.zip and give an error or does it say there is no update on the SD card?
Also, can you try and extract the su binary you said is in /system/xbin and post it here? There's something I would like to check.
EDIT: From adb shell, type the following, without quotes, "cat /proc/cpuinfo" and post the output here please
EDIT: Another silly suggestion - you could try guessing the password su asks you for. Maybe it's something obvious like "root" or "admin".
SifJar said:
Does it try to install update.zip and give an error or does it say there is no update on the SD card?
Also, can you try and extract the su binary you said is in /system/xbin and post it here? There's something I would like to check.
EDIT: From adb shell, type the following, without quotes, "cat /proc/cpuinfo" and post the output here please
Click to expand...
Click to collapse
Seems that it does not even try to update, no error message, nothing. I tried putting the update.zip in both /sdcard (internal sdcard) and /sd-ext (microsd)
Code:
[email protected]:/ $ cat /proc/cpuinfo
system type : actions-atv5201
processor : 0
cpu model : MIPS 74Kc V5.0 FPU V0.0
BogoMIPS : 719.25
wait instruction : yes
microsecond timers : yes
tlb_entries : 32
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0000, 0x0000, 0x0460, 0x0868]
ASEs implemented : mips16 dsp
shadow register sets : 1
core : 0
VCED exceptions : not available
VCEI exceptions : not available
I have attached the 'su' binary from /system/xbin
Also:
Code:
$file su
su: ELF 32-bit LSB executable, MIPS, MIPS32 rel2 version 1 (SYSV), dynamically linked (uses shared libs), with unknown capability 0xf41 = 0x756e6700, with unknown capability 0x70100 = 0x1040000, stripped
But the table description of the manufacturer, says that has an Allwinner A10 (Cortex A8). Does not seem to be true, right?
Thanks
Looks like a MIPS processor then, not an ARM as most android devices have. That explains why exploit don't run and SSH didn't work, both use code compiled for ARM processors. It also means a standard su binary won't work on that device. You'll need one compiled for MIPS.
Does the update from sd card give any sort of error?
No. It does not say anything. I'll try to find the right update.zip for the MIPS architecture. Perhaps it could work.
Edit: Found this https://rapidshare.com/files/2288417520/Superuser-3.0.7-mips32r2-ics_signed.zip , but does not seem that I can flash it from the recovery with the update.zip method
Thanks a lot Sifjar
I'm afraid I'm now out of suggestions. The last piece of advice I can give is try and find an official update for the tablet from the manufacturer and investigate the format of that update, to try and identify how an update should be formatted/named for your device.
Thank you SifJar. You helped me a lot to find what happens with this tablet ;-)
I've read from more people, buying Allwiner A10 tablets on efox, and receiving different ones (lower specs and usually MIPS based). I'd not recommend to buy to this seller because it does not even answer your questions or does give you support.
I'm pretty sure, that could be one of the clones of the Ainol Novo7 Paladin/Basic. I'll try to find it
dreamer_ said:
Thank you SifJar. You helped me a lot to find what happens with this tablet ;-)
I've read from more people, buying Allwiner A10 tablets on efox, and receiving different ones (lower specs and usually MIPS based). I'd not recommend to buy to this seller because it does not even answer your questions or does give you support.
I'm pretty sure, that could be one of the clones of the Ainol Novo7 Paladin/Basic. I'll try to find it
Click to expand...
Click to collapse
Well I believe from a bit of reading about the Ainol tablet you should be able to type "adb remount" and then "adb root" to get root access from adb on that tablet. Then you can push a MIPS su binary to the device and be done with it. But it depends how close a clone it is whether the same will be true for your tablet I guess.
EDIT: Have you found any way to access a fastboot mode? (Possibly the command "adb reboot bootloader" would work) If the bootloader isn't locked, you may be able to extract the system.img, root the img and then flash it back with fastboot. Although that is something I have only heard about, I have no experience in how one would go about rooting the system.img. (Extracting it from the phone and flashing back isn't overly hard).
I have tried both things with no success. The remount, fails and I don't have root access then (and R/O Filesystems)
adb reboot bootloader, just reboots the device
I have found a post from a guy http://tabletrepublic.com/forum/other-tablets/actions-cpu-android-tablet-actions-atm7013-1-3ghz-cpu-2087.html#post20776, that seems to have my same tablet (or both tablets seem to be the same MIPS based).
I still think that could be a novo 7 basic/paladin clone and it does have the same recovery and the DFU mode. I'm downloading the tools and FW from the paladin, but seems to be impossible to find anything more about my tablet.
Thanks
dreamer_ said:
I have tried both things with no success. The remount, fails and I don't have root access then (and R/O Filesystems)
adb reboot bootloader, just reboots the device
I have found a post from a guy http://tabletrepublic.com/forum/oth...ctions-atm7013-1-3ghz-cpu-2087.html#post20776, that seems to have my same tablet (or both tablets seem to be the same MIPS based).
I still think that could be a novo 7 basic/paladin clone and it does have the same recovery and the DFU mode. I'm downloading the tools and FW from the paladin, but seems to be impossible to find anything more about my tablet.
Thanks
Click to expand...
Click to collapse
This is one of the big issues with China based devices. Not only is it have really limited development they tend to use none standard hardware so none of the current things work on it. Then toss in the fact that the hardware is not always what it is said to be.
Sent from my SGH-I897 using Tapatalk 2
The USB drivers for the novo paladin, didn't work for me....If I only could flash a CWM recovery for my tablet, perhaps I could then flash the superuser.zip with the 'su' binary that SifJar said.
zelendel said:
This is one of the big issues with China based devices. Not only is it have really limited development they tend to use none standard hardware so none of the current things work on it. Then toss in the fact that the hardware is not always what it is said to be.
Click to expand...
Click to collapse
Yes...my problem has been mainly that in the efox website, they are basically lying you in the product description, and selling a thing that is not true.
Casually, there's also an IVIEW tablet on the market, exactly like mine, made only for the chinese market (without the IVIEW letters and 1.3mpx camera)...and that was what I thought I bought, a chinese IVEW (and my mistake)
You really need to see the cpuinfo to see that, and not everybody will do it....
Thanks
If you download this: usbview.zip
You can use it to find the vendor ID (app shows it as IdVendor) for your device (put it in the DFU mode thing first), and then you could try using fastboot and specifying the vendor ID with -i argument, it might work without drivers then (not sure if this is right, but I think something similar was done with the Kindle Fire)
just try something like
Code:
fastboot -i 0xFFFF devices
replacing 0xFFFF with the vendor ID from that app, to see if it detects it at all
Thanks. Does not seem to return anything (a return). It works with '-i device' at the end of the line.
Code:
fastboot.exe devices -i 0x10D6
ADB does give me this:
Code:
c:\sonec>ADB\adb.exe devices
List of devices attached
Actions Semi. 23711DF4 device
Hello all,I had bought a local tablet from calcutta called ICE Xtreme on which I had nightmares,but it also helped me learn n now here is it,a short yet complete guide for ur allwinner devices.
Like me,some of u might have been bored enough abt the stock rom that we decide to experiment.since allwinner CPUs can boot over USB(livesuit mode) n SD cards (phoenixcard) we think nothing will b wrong n flash without a full rom backup (i hav a script uploaded here,find it n hav a look), after the flash we find the stock ROM gone,camera,touch,wi-fi etc gone haywires n cache is mounted as SDCARD!!! Yes,those who used livesuit hav been in stuff lik this. Now I was also in one n upon reading alot I hav seen ppl editing bootloaders,using keyboard mouse,plugging HDMI(lcd broken). After a month of fiddling wit my device its time i share a shortcut that can save many hours of ur life.
Also do backup the boot n bootloader on ur pc as sumtimes flashing destroys the SD.
1st step. Backup ur bootloader n boot images. Use "cat dev/block/nandc > sdcard/dump/boot.img" to backup boot..nw backup bootloader the same way,by replacing nandc wit nanda.
Now u use adb pull method to backup ur system,etc,data(its optional,only do it if u want ur apps).n any other folder from the root of ur device.my script can help u do it instantly. Anyways,u must get the etc n system folder.
After that ur free to flash any ROM image through any method (actually,livesuits the best if u can find the img). Now after flash ur device is on right?? Does the SDCARD mount??if no then turn on USB debug,in adb shell type cd dev/block <enter> then type ls n ull see a list of nand partitions,the last one is the SDCARD in raw format.so format is by: su busybox mkfs.vfat dev/block/nand[drive letter,i.e. nandj] n then type vold.ur sdcard will mount.
Now send those boot n bootloader files to SDCARD/dump. U can use mkdir or mannually make the dir n copy. Thn simply type "cat sdcard/dump/boot.img > dev/block/nandc" n same way type nanda n bootloader to restore the bootloader. Now use adb to push the files of ur stock ROM system/vendor/modules(which u backed up earlier) to tablets system/vendor/modules. N the contents of etc folder to etc on the tablet.nw reboot.
Hey!!! Its working.the LCD shift is gone,cam n wi-fi doing good,touch is not reversed or stuff. Congratulations u restored ur tablet,n now running a completely diffrent ROM on it.enjoy.
Heres another shortcut ive learned. U can get any update.zip n convert it to licesuit image. Just extract the system dir. Thn copy it to ur SDCARD. Make modification if needed,copy the modules u backed up.In adb shell type make_ext4fs -s -l 300M -a system <filename.img> (dir of ur system,i.e mnt/sdcard/system) it will make u a .img file which is same as the system.fex file u get when u break a livesuit image. Copy n replace the ROMs boot n bootloader.fex files wit ur backed up boot n bootloader.img (rename .img to .fex) pack the image again to livesuit format n burn it. It will install like a normal ROM. BUT MAKE SURE FILE PERMISSIONS OF READ WRITE N EXECUTE IS INTACT. ELSE ULL ENJOY HOURS OF BOOTANIMATION. but if ur stuck use the method above n flash any other ROM n fix the RON fr ur device. Guys ROM developing n editing fr allwinner devices are not easy...BTW id lik to thank user [iamabadduck] fr his actual A10 backup script. On which i made mine. Im still doing experiments. Hope this info i shared makes the readers modest enough to make the hit thanks. Bye. [ ill b around,so if any quests,ill ans them].
I was very excited to see someone finally post a guide for these mysterious tablets! Thank you!
However, I ran into some difficulties trying to make use of them, but I think this has more to do with my hardware and trying to match it with the appropriate ROM and compatibility zip.
You see, I have a Kocaso M1060W. It's a very nice little tablet but trying to identify it has been difficult. As far I can tell, it's a clone of the Protab2XXL (I don't know what version) or something called the BC1077. It seems easier identifying other Allwinner A10's, apparently. I know some identifying information can be found in the build.prop file and that's how I figured out the tablets of which it is a clone. I even tried finding a database of different ImageSuit images I could try to use, but either there is none or my Google skills are suffering. Does it matter that Kocaso chose to go with PhoenixCard for flashing their tablets? Some documentation suggests the images for both are the same.
Can you help me find documentation that would help me identify the board and the hardware? Let me know what information you need from the tablet, and I will get it to you. Identification would go a long way towards me making use of your steps.
Also, a question. After the rom is flashed and you "adb shell" in, you have me trying to mount the sdcard directory via the nand block devices, and then entering "vold". It doesn't error but nothing seems to happen. Even stranger, running "mount" tells me that it's done something. Is it because most of the ROM flashes require the data wipe that I should assume I have the capability to read/write within the SDCARD directory?
Allwinner A10 ghost touch (Icoo D70W, goodix chip)
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Compatability
konyazsolt said:
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Click to expand...
Click to collapse
If you could Post an lsmod from both the Working Firmware and the Non-Working I will take a swing at answering your question...The problem is likely one compat file is installing drivers for one of Your pieces of hardware and not the other and the other compat file is istalling the driver for the other piece but not the One... confusing sounding...
But Bottom Line is If I had the Lsmod from the working Hardware and the 2 compatability files you tried I could likely alter one of the compatability files to cover All of your hardware.
Or better yet pull the Bootloader.img and the Boot.img out of your Tab and send them to me...
you can do this by opening a cmd window from a directory where you wish to store the .img files then type the following :
adb shell su -c "cat /dev/block/nandc > /mnt/sdcard/nandc-root.img" (Press enter Key)
adb pull /mnt/sdcard/nandc-root.img (Press enter Key)
That will give you the Boot.img (named nandc-root.img)
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img" (Press enter Key)
adb pull /mnt/sdcard/nanda-bootloader.img (Press enter Key)
That will give the bootloader.img (named nanda-bootloader.img)
send those from both your OEM Rom that is working and the Target Rom you wish to make work .... from that I can either write a compat patch for it or send back the edited ones from your Target Rom (the one you wish to work)
Srry i cudnt keep my promise of being around. Had been pretty busy looking for stock JB ROMs in livesuit format. Found some. Some worked n some didnt. Will abt the touchscreen issue if that Rom has a focaltech ftx_5x touchscreen its broken. U hav to compile it again leaving out the multitouch part in a header file. Do a google search. There r alot of articles. N abt da nand part well not all roms break the internal SD partition. The busybox thing u do only when ur internal cards dont mount. It will NOT WORK FOR A MICROSD IF U HAV ONE. Its generally mounted as extsd.
Try reading from here:
konyazsolt said:
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1520943
It's a thread about the allwinner A10 or EKEN T01A.. it shows how to reflash to original and updated EKEN firmwares via livesuit. And also i think they mentioned something about touchscreen issues. Hope it helps
Hi please help me! I have nightmares too with my tablet:
Hi, i have a mid tabler model HBD-Mid-708G like that http://marcopolocompany.fucsio.com/e...oducts/MC-708G . This is a Boxchip a10 with 11 partitions, i get this info throw ADB.
My problem was try to install CWM getting the error Can´t Mount / Read!!!!!
I have been used this roms:
F1-4.1.1-20130319.2.0.6-A721_v4.2
pdf_android4.0.10_ctp7_public_en_0319
Q7_512M+flash+Gmail
rom_woo_comet_404_291112_0cd4d
RSH-A10-C2
speed.1.1.1
sun4i_crane_t01a-linsay-20120411
and only rom_woo_comet where some Ok! .
Solved this CWM problem flashing a rom_woo_comet using LiveSuit but the result is an screen resolution problem: (the image attach) .
So please any can say me a correct rom?
Thanks
accessing nand
hi there,
this is interesting stuff you are talking about here. Unfortunately, I get stuck to the beginning. How do you access the nand???
you say sart with cat dev/block/nandc > sdcard/dump/boot.img
I'd love to but where do you enter these commands? When I connect my tablet to my computer, I see certains parts as usb storage, and I have no way of entering commands to the tablet. From within android, everything is blocked...
thanks for your help
nacxo said:
Hi please help me! I have nightmares too with my tablet:
Hi, i have a mid tabler model HBD-Mid-708G like that http://marcopolocompany.fucsio.com/e...oducts/MC-708G . This is a Boxchip a10 with 11 partitions, i get this info throw ADB.
My problem was try to install CWM getting the error Can´t Mount / Read!!!!!
I have been used this roms:
F1-4.1.1-20130319.2.0.6-A721_v4.2
pdf_android4.0.10_ctp7_public_en_0319
Q7_512M+flash+Gmail
rom_woo_comet_404_291112_0cd4d
RSH-A10-C2
speed.1.1.1
sun4i_crane_t01a-linsay-20120411
and only rom_woo_comet where some Ok! .
Solved this CWM problem flashing a rom_woo_comet using LiveSuit but the result is an screen resolution problem: (the image attach) .
So please any can say me a correct rom?
Thanks
Click to expand...
Click to collapse
You need to edit your script.bin inside the bootloader.img... there is a utility to do this on techknow.me...
to do it manually you need to extract the script.bin file from the bootloader.img ... easiest way is from adb shell
Open a windows command window (this assumes you have adb.exe in your Path .. if not you must do this from the
same folder where adb.exe is located)
type the following
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img"
adb pull /mnt/sdcard/nanda-bootloader.img
this will place a file called nanda-bootloader.img in the folder where you ran the windows command window.
Now copy the file to your Linux Machine or VM
and from a terminal do the following:
mkdir bootloader
sudo mount -t vfat ./nanda-bootloader.img bootloader
This mounts the bootloader image to the bootloader folder.... in the bootloader folder copy the script.bin file to another location for editing.
to edit it must be converted to fex... you will need the fex tools for this I have them posted here: http://www.4shared.com/zip/Nzn6PV-b/tools.html
your Linux machine has to be x64 for those to work.
from the folder containing the tools folder and script.bin file open a terminal and do the following:
./tools/bin2fex script.bin > script.fex
this will create the script.fex file which is editable in a linux text editor, open the file and edit the [lcd0_para] section
to correct your screen shift ... the exact settings needed are impossible for me to determine as I do not
have your tab nor the rom you originally had on it.. if you have the original rom available (with screen position correct)
you can pull the script.bin from that rom and replace the entire [lcd0_para] section with the same section from your working rom
to solve the issue.
once edited convert back to .bin from a terminal with the following commands:
./tool/fex2bin script.fex > script.bin
now open the bootloader folder as superuser and delete the script.bin and script0.bin located inside...
copy the new script.bin file in and also copy it and rename the copy to script0.bin and place that there as well.
then from folder containing bootloader folder open a terminal and do the following:
sudo umount bootloader
now copy nanda-bootloader.img to windows machine.
open a Command window in the folder containing your new nanda-bootloader.img file and do the following
adb push nanda-bootloader.img /mnt/sdcard
adb shell su -c "cat /mnt/sdcard/nanda-bootloader.img > /dev/block/nanda"
adb shell rm /mnt/sdcard/nanda-bootloader.img
adb shell su -c "sync"
adb shell su -c "reboot"
if all was done properly your tab should now reboot with the correct screen geometry. The utility I mentioned does
pretty much all of this for you, but i cannot link it here as it is on techknow.me which requires registration to
download ... and the rules forbid links to such sites here.
I hope that all helps you.
---------- Post added at 12:24 PM ---------- Previous post was at 12:16 PM ----------
djahma said:
hi there,
this is interesting stuff you are talking about here. Unfortunately, I get stuck to the beginning. How do you access the nand???
you say sart with cat dev/block/nandc > sdcard/dump/boot.img
I'd love to but where do you enter these commands? When I connect my tablet to my computer, I see certains parts as usb storage, and I have no way of entering commands to the tablet. From within android, everything is blocked...
thanks for your help
Click to expand...
Click to collapse
You must have the ADB drivers installed and know where they are located, placing them in your Path statement is a good idea if you intend to do much ROM editing or direct Tablet commands from and adb shell.
NOTE: To open a command window from any folder on your computer in Explorer browse to the folder you want to open command window from
then in an area of the folder window that is empty right click mouse while holding shift then select open command window here
Once you have ADB INstalled, if the adb.exe is in your path open a command window from any folder you like on windows and type the commands in the command window. If ADB.exe is not in your path you must open a command window in the folder containing adb.exe
(Usually the android SDK Platform tools folder)
I Hope that helps
Thanks fsebentley, I've now copied all nandX partitions.
what I'm trying to do now, is to create a bootable sd card. I believe I must tailor u-boot.bin to boot a specific kernel with my specific hardware setup.
I've found a lot of resource for arm boards, but almost none for tablets, except for direct flashing but I'm not ready to go this far.
So, do you know about a nice tool to read what's in u-boot.bin and eventually modify it?
Touchpad driver
Hi!
I need some help!! I want to include touchpad driver an cm9 installer because when I instal the system with CWM but the touchpad not working!!!
Here is the topic where you can find the ROM: http://forum.xda-developers.com/show....php?t=1861445
Sorry I write here because I can't write in the original topic.
Thank for help!!!
Apad 711 stuck at boot logo
Hi Guys,
I need help. one of my friend has a Apad711 tablet and his stock android recovery was changed by cwm 5.08 incorrect version and hence the power + - or power button was not responding.
I took over and had flashed 6.0.2 8 cwm by following this forum http://forum.xda-developers.com/showthread.php?t=2189640
and recovery was working properly, but then i though of upgrading it to cyanogen mod 9 and downloaded the files using this forum
http://forum.xda-developers.com/showthread.php?t=1760929
however after the update was completed the touchscreen didnt work and I had to connect a usb OTG cable along with usb mouse to get into recovery. I then did a little research and tried flashing a couple of compatibility zip
711i_compatibility_1.1.0.zip, lyf1_compatibility_1.1.0.zip, 711i_compatibility_1.2.0.zip, lyf1_compatibility_1.2.0.zip which had similar specs from this website http://old.androidfilehost.com/main/Allwinner_A10_Developers/christiantroy/misc/
but even after doing so touchscreen,camers etc didnt work.
since i had made a backup of stock rom using cwm before flashing cyanogenmod 9 i thought of restoring it back using cwm 6.0.2.8
i was able to restore the back up but to my surprise i am now stuck at apad boot logo and cannot boot to recovery using the volume - and power key. i tried to connect the tablet to pc so that i can get into adb interface and reboot to recovery but the computer detects the tab as unknown device
I now need help to get into recovery and flash a rom that would make it work or complete tutorial to install/flash a new /stock rom or cyanogenmod to get the device back to life.
please refer to the manufacturers website link listed below for specs:--
http://www.apadtab.com/711_spec.php
Any help would be greatly appreciated.
allwinner a10., broken bootloader
Hi i've got a eneoze tablet with an allwinner A10., now i've flashed my bootloader with berryboot en it was working., later i wanted to change some things in de configs of the berryboot bootloader and i messed up. Now my tablet is completely dead.
It doesn't doe anything when i try to turn it on., de screen doesn't even light up., it isn't recognised when i connect it to the pc so fastboot., adb aren't working eather.
Do you have any ideas on how to resolve this.?
Greets Sam
sammekevremde said:
Hi i've got a eneoze tablet with an allwinner A10., now i've flashed my bootloader with berryboot en it was working., later i wanted to change some things in de configs of the berryboot bootloader and i messed up. Now my tablet is completely dead.
It doesn't doe anything when i try to turn it on., de screen doesn't even light up., it isn't recognised when i connect it to the pc so fastboot., adb aren't working eather.
Do you have any ideas on how to resolve this.?
Greets Sam
Click to expand...
Click to collapse
If you can't flash it from your pc, create a bootable sd card. For example, you could copy your berryboot image to the sd card and boot from it.
Supposedly, you saved your tablet nand into an image before messing up with that nand. Once you boot from sd, flash the nand again with that saved image. Good luck to you
need a little help
i wnt to increase resolution of my a10 tab from 800x480 to 1024x600....to do so i need to edit the bootloader(bootloader.fex)
but,the problem is i can't edit the bootloader.fex correctly......how to edit properly
Guys i have bricked my phone by restoring MK1 efs backup created with efs professional tool. Few days ago i upgraded it with android 4.4 version with ota. I restored all partitions with efs pro tool except user data and system. Now it's in qhsusb_dload mode. I tried i9205 debrick image from this forum and it's not working. I do not know how to make debrick image form stock rom or any other way. Can anyone help me to fix this?
Thanks
Finally unbricked it with DarkAngel's help. Many thanks to him.
For unbrick your phone please read all post's by DarkAngel.
ashikrobi said:
Guys i have bricked my phone by restoring MK1 efs backup created with efs professional tool. Few days ago i upgraded it with android 4.4 version with ota. I restored all partitions with efs pro tool except user data and system. Now it's in qhsusb_dload mode. I tried i9205 debrick image from this forum and it's not working. I do not know how to make debrick image form stock rom or any other way. Can anyone help me to fix this?
Thanks
Click to expand...
Click to collapse
Have you tried to Odin the Official Firmware available for the L600? It can be done via Kies as well.
L600VPUBNE4
I tried odin and kies
DarkAngel said:
Have you tried to Odin the Official Firmware available for the L600? It can be done via Kies as well.
L600VPUBNE4
Click to expand...
Click to collapse
Yes i tried but in qhsusb_dload mode odin cannot find the phone. It cannot be powered up bro so how can kies detect it? Do you know how to fix this issue? Please help.
ashikrobi said:
Yes i tried but in qhsusb_dload mode odin cannot find the phone. It cannot be powered up bro so how can kies detect it? Do you know how to fix this issue? Please help.
Click to expand...
Click to collapse
Which version of Odin are you using?
odin 3.09 and 3.04
DarkAngel said:
Which version of Odin are you using?
Click to expand...
Click to collapse
I tried with these versions. They do not detect the device. If you have a working phone, you can make a debrick image for me. Please install busybox and a terminal emulator. Then issue this command from the terminal and you will get the debrick image in your sd card.
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
Make sure you have SPH-L600 and android version 4.4 or the image will not work for me.
Please upload
Thanks
installed automatic upgrade stuck in boot loop
I have a Galaxy Mega SPH-L600 and i replaced the screen about a week ago and it was running fine opened it up 2 days ago and there was an update said needed to be done so hit ok and installed update it went to 100% and shut off and turned back on went to Samsung splash screen and shut off and turned back on did this for about a half hour so i tried to do the hard boot with power button,volume up and home button droid comes up and it says installing upgrade and goes back ito boot loop tried to hook up to laptop but can not get it to show up on my Windows 7 unit tried alot of stuff nothing works need some help from anyone that can point me in the right direction and thank you in advance
ashikrobi said:
I tried with these versions. They do not detect the device. If you have a working phone, you can make a debrick image for me. Please install busybox and a terminal emulator. Then issue this command from the terminal and you will get the debrick image in your sd card.
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
Make sure you have SPH-L600 and android version 4.4 or the image will not work for me.
Please upload
Thanks
Click to expand...
Click to collapse
The only problem I have with the debrick image is if the 128mb will include my EFS information. I have to mount it to an extra SDcard I have and check it's content before I give it out or post it up for grabs.
Thank you for the how too but I am familiar with making a debrick image using TE. I have one made for all my devices although I haven't bothered checking to see what was exactly on this one being it is at 128mb ( as my SGS3 needs only just about half of the requested to work ) so I can provide the needed files.
Just to make things clear not all images being from other carriers will work on other devices of the same model. They may be partitioned a different way than the L600. Also you PM'd me that you tried to recover your EFS info using the created backup from one of a MK1. I wouldn't have tried that. You already upgraded to 4.4 and have the newest Knox bootloader which will not allow you to downgrade the Bootloader at all.
Thanks for the reply
DarkAngel said:
The only problem I have with the debrick image is if the 128mb will include my EFS information. I have to mount it to an extra SDcard I have and check it's content before I give it out or post it up for grabs.
Thank you for the how too but I am familiar with making a debrick image using TE. I have one made for all my devices although I haven't bothered checking to see what was exactly on this one being it is at 128mb ( as my SGS3 needs only just about half of the requested to work ) so I can provide the needed files.
Just to make things clear not all images being from other carriers will work on other devices of the same model. They may be partitioned a different way than the L600. Also you PM'd me that you tried to recover your EFS info using the created backup from one of a MK1. I wouldn't have tried that. You already upgraded to 4.4 and have the newest Knox bootloader which will not allow you to downgrade the Bootloader at all.
Click to expand...
Click to collapse
Thanks DarkAngel for your reply. My sprint mega was reprogrammed by myself with dfs tool. I didn't provisioned it with any commercial way. I just changed it to use uim to get operator information and it was working. But after i changed the rom to slimkat i lost esn from efs. That's why i tried to restore efs backup after 4.4 ota update.
I knew you are an expert or an android developer so i requested help from you. Because you have some threads that maybe possible by a developer. I am in a horrible situation. I took my phone the other day to my local jtag repair center an they failed to repair it. They said there is no support for this phone still now. Brother please help me to fix my phone. Thanks.
ashikrobi said:
Thanks DarkAngel for your reply. My sprint mega was reprogrammed by myself with dfs tool. I didn't provisioned it with any commercial way. I just changed it to use uim to get operator information and it was working. But after i changed the rom to slimkat i lost esn from efs. That's why i tried to restore efs backup after 4.4 ota update.
I knew you are an expert or an android developer so i requested help from you. Because you have some threads that maybe possible by a developer. I am in a horrible situation. I took my phone the other day to my local jtag repair center an they failed to repair it. They said there is no support for this phone still now. Brother please help me to fix my phone. Thanks.
Click to expand...
Click to collapse
Well not an expert but I read a lot on here and do what I can when I can.
This is what I got from my Mega:
Code:
L600 Output
====================
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
[U]
Number Start End Size File system Name Flags[/U]
[B] 1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 71.2MB 524kB tz
8 71.2MB 84.3MB 13.1MB pad
9 84.3MB 92.7MB 8389kB param[/B]
[COLOR=Red][B]10 92.7MB 107MB 14.3MB ext4 efs[/B][/COLOR]
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 124MB 10.5MB boot
14 124MB 134MB 10.5MB recovery
15 134MB 145MB 10.5MB fota
16 145MB 152MB 7332kB backup
17 152MB 155MB 3146kB fsg
18 155MB 155MB 8192B ssd
19 155MB 164MB 8389kB ext4 persist
20 164MB 176MB 12.6MB ext4 persdata
21 176MB 2324MB 2147MB ext4 system
22 2324MB 3058MB 734MB ext4 cache
23 3058MB 3079MB 21.0MB ext4 carrier
24 3079MB 15.8GB 12.7GB ext4 userdata
pit file of my mega
DarkAngel said:
Well not an expert but I read a lot on here and do what I can when I can.
This is what I got from my Mega:
Code:
L600 Output
====================
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
[U]
Number Start End Size File system Name Flags[/U]
[B] 1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 71.2MB 524kB tz
8 71.2MB 84.3MB 13.1MB pad
9 84.3MB 92.7MB 8389kB param[/B]
[COLOR=Red][B]10 92.7MB 107MB 14.3MB ext4 efs[/B][/COLOR]
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 124MB 10.5MB boot
14 124MB 134MB 10.5MB recovery
15 134MB 145MB 10.5MB fota
16 145MB 152MB 7332kB backup
17 152MB 155MB 3146kB fsg
18 155MB 155MB 8192B ssd
19 155MB 164MB 8389kB ext4 persist
20 164MB 176MB 12.6MB ext4 persdata
21 176MB 2324MB 2147MB ext4 system
22 2324MB 3058MB 734MB ext4 cache
23 3058MB 3079MB 21.0MB ext4 carrier
24 3079MB 15.8GB 12.7GB ext4 userdata
Click to expand...
Click to collapse
Take a loot at my pit file previously created with efs professional tool. Same like yours. I hope your debrick image will work for my mega. Please upload when possible. Do not worry about efs partition. I have my efs backup. I will restore mine. I have a question, if my phone becomes useable after using your debrick image and i restore only efs partition from efs backup will it brick again?
Thanks.
SPH-L600 sprint mega bad ESN
so as not to make a new topic, I decided to write here
I recently bought SPH-L600 sprint mega with a bad ESN, he came to me activated on Sprint and Sprint have sim I played settings and activation dropped sprint
but I live in another country and I can not activate it!
help somehow activate it! I bought an unlock code network, but said that he needed seller activation sprint!
any help would be much appreciated!
ashikrobi said:
Take a loot at my pit file previously created with efs professional tool. Same like yours. I hope your debrick image will work for my mega. Please upload when possible. Do not worry about efs partition. I have my efs backup. I will restore mine. I have a question, if my phone becomes useable after using your debrick image and i restore only efs partition from efs backup will it brick again?
Thanks.
Click to expand...
Click to collapse
Yes, they should be the same thing as we both have L600's. I didn't have a chance to look it over but I will try and get it to you later on today.
All you need is for your Mega to be able to get to Download Mode. Then and only then you will have to Odin a copy of the Official Firmware L600VPUBNE4 for it not to stay bricked but you probably already know that. As far as becoming usable that would be up to you, being able to restore your EFS data. In theory it should not brick but you need to only restore the EFS portion of the data.
Here is all the info I gathered from using Terminal Emulator in case you need it for file locations:
EFS is located: /dev/block/mmcblkop10
As you can see msm_sdcc.1 is specific to our device ( I noticed that it was the same on my SGS3 but not my SGN2 on KitKat ) so one can locate the by-name file to get the list below.
The second picture shows GNU Parted being run in my Terminal Emulator. You would need the Parted Binary file located here at the end of the Original Post.
Just extract the parted binary manually and then copy and paste it to the /system/bin folder with any File Explorer with Root access. After you paste the binary you will need to set the permissions to the parted binary you pasted to rwxr-xr-x or (0755). You can do this to any device you have and run it either in Terminal Emulator and even via ADB on your computer. Really handy to have sometimes.
Once you get the debrick image, below are two guides that I saved in my subscriptions that may help you. You may have them already.
deBricker
gTan64
---------- Post added at 05:31 AM ---------- Previous post was at 05:29 AM ----------
Ura535 said:
so as not to make a new topic, I decided to write here
I recently bought SPH-L600 sprint mega with a bad ESN, he came to me activated on Sprint and Sprint have sim I played settings and activation dropped sprint
but I live in another country and I can not activate it!
help somehow activate it! I bought an unlock code network, but said that he needed seller activation sprint!
any help would be much appreciated!
Click to expand...
Click to collapse
Actually this is an entirely different topic from Debricking a phone. You have a phone with a bad ESN. With that I can not help. If the previous owner ( or seller in your case ) "maybe" did not pay his bill, then your phone is locked out until it is released from his/her account by Sprint. If there is a way around this, I may not know.
I had this happen to me once before with my wife's Sprint SGS4. It was a pain but eventually two days later the seller finally came through and the phone was released for activation.
You should start a separate thread to see if you can get the right help and not get your question lost in this thread. I am sorry I couldn't help you any further.
Sorry you misunderstood
DarkAngel said:
Yes, they should be the same thing as we both have L600's. I didn't have a chance to look it over but I will try and get it to you later on today.
All you need is for your Mega to be able to get to Download Mode. Then and only then you will have to Odin a copy of the Official Firmware L600VPUBNE4 for it not to stay bricked but you probably already know that. As far as becoming usable that would be up to you, being able to restore your EFS data. In theory it should not brick but you need to only restore the EFS portion of the data.
Here is all the info I gathered from using Terminal Emulator in case you need it for file locations:
EFS is located: /dev/block/mmcblkop10
As you can see msm_sdcc.1 is specific to our device ( I noticed that it was the same on my SGS3 but not my SGN2 on KitKat ) so one can locate the by-name file to get the list below.
The second picture shows GNU Parted being run in my Terminal Emulator. You would need the Parted Binary file located here at the end of the Original Post.
Just extract the parted binary manually and then copy and paste it to the /system/bin folder with any File Explorer with Root access. After you paste the binary you will need to set the permissions to the parted binary you pasted to rwxr-xr-x or (0755). You can do this to any device you have and run it either in Terminal Emulator and even via ADB on your computer. Really handy to have sometimes.
Once you get the debrick image, below are two guides that I saved in my subscriptions that may help you. You may have them already.
deBricker
gTan64
---------- Post added at 05:31 AM ---------- Previous post was at 05:29 AM ----------
Actually this is an entirely different topic from Debricking a phone and on yours, you have a bad ESN. With that I can not help. If the previous owner ( or seller in your case ) "maybe" did not pay his bill, then your phone is locked out until it is released from his/her account by Sprint. If there is a way around this, I may not know.
I had this happen to me once before with my wife's Sprint SGS4. It was a pain but eventually two days later the seller finally came through and the phone was released for activation.
You should start a separate thread to see if you can get the right help and not get your question lost in this thread. I am sorry I couldn't help you any further.
Click to expand...
Click to collapse
Dark Angel you misunderstood my message i don't have bad esn. I lost esn number or corrupt it with dfs cdma tool. Dfs shows my esn but status from efs shows cps_na error. I didn't bought this phone second hand. My cousin send it from USA and she bought it new.
Thanks and i am waiting for your reply.
Off Topic Post / Misunderstanding .....
ashikrobi said:
Dark Angel you misunderstood my message i don't have bad esn. I lost esn number or corrupt it with dfs cdma tool. Dfs shows my esn but status from efs shows cps_na error. I didn't bought this phone second hand. My cousin send it from USA and she bought it new.
Thanks and i am waiting for your reply.
Click to expand...
Click to collapse
Yes I know, please disregard the quote and answer from the previous person responding above my post, right after the pictures I posted ( you will see the quote ). It was an off topic post and the forum combined them for some reason in the response for you ( probably because they were so close in time frame when I posted ) ..... I tried separating them in different posts but it still combined them together.
That is why off topic posts should be posted in a new thread/topic to avoid confusion......
DarkAngel said:
Yes I know, please disregard the quote and answer from the previous person responding above my post, right after the pictures I posted ( you will see the quote ). It was an off topic post and the forum combined them for some reason in the response for you ( probably because they were so close in time frame when I posted ) ..... I tried separating them in different posts but it still combined them together.
That is why off topic posts should be posted in a new thread/topic to avoid confusion......
Click to expand...
Click to collapse
Wow!!! Dark Angel, you are the man i was looking for. You know linux like a pro. Linux is my favorite operating system. I didn't know parted was available for android also. How do you learn these things?
By the way sorry, i though your message about bad esn was for me.
Thanks
ashikrobi said:
Wow!!! Dark Angel, you are the man i was looking for. You know linux like a pro. Linux is my favorite operating system. I didn't know parted was available for android also. How do you learn these things?
By the way sorry, i though your message about bad esn was for me.
Thanks
Click to expand...
Click to collapse
Well not a Pro..... I still have much more to learn but Linux is my favorite OS to use for anything Android related. A lot I still do on Windows.
Debrick Image......
Okay try this image.......
I burnt this image several time over on a class 4, 8 gig card and it wrote the image on it perfect. I don't know if you will have to use a 16gig card for your Mega or not but try what you have 16 gig or less. Trial and error at this point.
You can probably add more to it if need be from the Official Firmware by dragging and dropping ( if I am not mistaken ) by just opening ( and not extracting ) the tar.md5 with WinRAR or 7zip. I can't remember if one was able to do this.......
L600 Debrick Image
Not working
DarkAngel said:
Okay try this image.......
I burnt this image several time over on a class 4, 8 gig card and it wrote the image on it perfect. I don't know if you will have to use a 16gig card for your Mega or not but try what you have 16 gig or less. Trial and error at this point.
You can probably add more to it if need be from the Official Firmware by dragging and dropping ( if I am not mistaken ) by just opening the tar.md5 with WinRAR or 7zip. I can't remember.
L600 Debrick Image
Click to expand...
Click to collapse
DarkAngel I wrote the img file to a 16gb sdcard and tried to boot my phone but it's not working. I waited 5 min and tried several times. I also used a usbjig to boot into download mode but failed.
Have a look these terminal output:
sudo dd if=/home/tails/Downloads/debrick.img of=/dev/sdc
174080+0 records in
174080+0 records out
89128960 bytes (89 MB) copied, 75.5075 s, 1.2 MB/s
[email protected]:~/Downloads$ sudo parted /dev/sdc print
Error: Invalid argument during seek for read on /dev/sdc
Retry/Ignore/Cancel? Ignore
Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
OK/Cancel? ok
Backtrace has 8 calls on stack:
8: /lib/i386-linux-gnu/libparted.so.0(ped_assert+0x29) [0xb773ad19]
7: /lib/i386-linux-gnu/libparted.so.0(+0x4649c) [0xb777749c]
6: /lib/i386-linux-gnu/libparted.so.0(ped_disk_new+0x55) [0xb7742275]
5: parted() [0x804ea2b]
4: parted(non_interactive_mode+0x8c) [0x8055c4c]
3: parted(main+0x1970) [0x804d5b0]
2: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0xb753aa83]
1: parted() [0x804d6e2]
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
http://ftp.gnu.org/gnu/parted/
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
http://www.gnu.org/software/parted
for further information.
Your report should contain the version of this release (2.3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Assertion (last_usable <= disk->dev->length) at ../../../libparted/labels/gpt.c:994 in function _parse_header() failed.
By the way is there any other way to recover from this state? I found qpst finds my phone after installing qhsusb_dload driver. Please help me.
Thanks
You are using an installed version of Linux correct? Are you on 13.04? Well I know the GNU Parted is just the program from Linux but the image still wrote on the SD card.
After the image was written to the SDcard, were you able to see the image content inside? For me it showed about 60MB of actual space written from the 85mb image. After it wrote, I just wrote over it and wrote over it and wrote over it again. Funny thing is I could not see the image at first so I then removed the card from my computer and re-inserted it and was then able to see it. I even inserted it on a Windows 8 tablet I have from a co-worker and it read it fine.
I did this while just using the "Install CD" and trying Ubuntu ( don't have it re-installed yet on my Notebook yet ). I did it using 14.04 LTS though. Try updating your GNU Parted ( your at 2.3 ), if it hasn't already been done, to the most current and re-write the image again.
DarkAngel said:
You are using an installed version of Linux correct? Are you on 13.04? Well I know the GNU Parted is just the program from Linux but the image still wrote on the SD card.
After the image was written to the SDcard, were you able to see the image content inside? For me it showed about 60MB of actual space written from the 85mb image. After it wrote, I just wrote over it and wrote over it and wrote over it again. Funny thing is I could not see the image at first so I then removed the card from my computer and re-inserted it and was then able to see it. I even inserted it on a Windows 8 tablet I have from a co-worker and it read it fine.
I did this while just using the "Install CD" and trying Ubuntu ( don't have it re-installed yet on my Notebook yet ). I did it using 14.04 LTS though. Try updating your GNU Parted ( your at 2.3 ), if it hasn't already been done, to the most current and re-write the image again.
Click to expand...
Click to collapse
Yes i am using an installed version of ubuntu 14.04. I was also not able to view partitions after i wrote the image to sdcard. But after i reinsert the card it showed all partitions and maybe mounted modem partition contents. I could view partitions with windows 7 also.
But when i try to boot the phone with this sdcard nothing happened. I tried several times but failed. What can i do now? DarkAngel please tell me a way to unbrick my phone.
Thanks
I understand that there is a seperate thread for the LG G Vista, but I was hoping that it was okay to post this. I noticed that there is not any guide on how to install CWM on the D-631 so here is a guide on how to do just that.
First of all..... you will need to enable USB Debugging.
To do this
\go to 'Settings' then 'About Phone' then 'Software Information' then click 'Build number' 7 times or so until it says 'You are now a developer!'
go back to 'Settings' and scroll down to the new box Developer Options
turn it on, and enable USB Debugging. ( I also check stay awake)
I rooted my phone with iRoot, and it installed Kinguser as my super user apk. Whether or not it is the best, I don't know. It just is the only one I could get working.
1. Install The LG Unified drivers from here ( I used LG USB Drivers 3.11)
http://www.mylgphones.com/lg-android-usb-device-drivers
2. Install ADB & fastboot (follow the xda thread here)
http://forum.xda-developers.com/showthread.php?t=2588979
3. now you have to use tese adb commands to zero out the laf partition on your D-631
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(I also ran this command to zero out the actual block partition)
dd if=/dev/zero of=/dev/block/mmcblk0p15
after I eliminated the LG Download so that fastboot takes priority (just as the G3) I could now boot into fastboot.
*Source from here* http://www.theandroidsoul.com/lg-g3-fastboot-mode-61660/
4. boot to fastboot. To do this.. Power down your phone. Hold vol+ and plug your phone into your pc.
It will still say DOWNLOAD MODE at the top, but it should now say 'fastboot processing commands'
5. unlock bootloader with this fastboot command
fastboot oem unlock
*this did not delete anything off my phone*
6. download and flash CWM recovery
Here is the recovery file
https://drive.google.com/file/d/0B-GvkM12QEbMbWxSV2RHcWRMOWs/view?usp=sharing
also on my main google drive
https://drive.google.com/folderview?id=0B-GvkM12QEbMeFFxRThfMlRvMWc&usp=sharing
fastboot flash recovery xxxxxxxxx
"xxxxxxx" is your directory of the recovery.img
bam all done.........
but this is what sucks..... fastboot reboot commands dont work. and idk how to fix that, but. I need help with the rest, PLEASE. and also some tweaks on the recovery file will need to be done. I just made it possible for us
so to reboot you must pull your battery.
I still dont know the hard key combo to enter into recovery so I had to install Xposed Framework from here
http://repo.xposed.info/module/de.robv.android.xposed.installer
then from googlen play I downloaded these
Xposed Additions
G3 Tweakbox <------------= This can enable the option for REboot REcovery
Busybox
SD Maid
(I used SDMaid to uninstall Carrier IQ tracking software, but I had to toggle the carrier IQ autostart component that starts with Android System)
So yeah, long nights, long days, but no bricks and now here it is
+XDA (as posted on your thread) and I am not responsible for any damage that may be caused.
=Do not steal this, give credit where it is due, link it here to this thread please.
Sorry I did not see the area for the guides and I apologize about that.
Also I forgot to thank everyone who gave their time on the LG G3 fast-boot project, as without your information I would not have been able to do this.
Also thanks to Google translate lol.... I couldnt have read Korean
great work friend
I delete some system files and now I cannot install anything from Google Play
I follow you method and I have CWM installed on my device can you help me to say how flash recovery to IMG FILES from you google drive all files are IMG not .tar ...
What files did you delete? I may be able to pull them with titabium backup and send you them all in a .zip file or something like that.
I used the fastboot commands to flash partitions.
fastboot flash xxxx <dir>
Where dir is the directory of said file to be flashed.
However installing apk's and what not i am not sure on how to do that.
Ill create some files in the .tar format as well. Im attempting to compile an un-official .bin, ,.tot, .dz or .kdz file for the d631. I have dzcreate and what nots. Its just that i drove away with my phone on the bumper and have to wait for my new screen from amazon.
djacks222 said:
What files did you delete? I may be able to pull them with titabium backup and send you them all in a .zip file or something like that.
I used the fastboot commands to flash partitions.
fastboot flash xxxx <dir>
Where dir is the directory of said file to be flashed.
However installing apk's and what not i am not sure on how to do that.
Ill create some files in the .tar format as well. Im attempting to compile an un-official .bin, ,.tot, .dz or .kdz file for the d631. I have dzcreate and what nots. Its just that i drove away with my phone on the bumper and have to wait for my new screen from amazon.
Click to expand...
Click to collapse
when I flashing the file system.img ( 2 GB size) obtain a error from fastboot for the size of system.img over 512 mb my partition system i
/system 1.97G 1.71G 260.18M 4096
/data 3.96G 1011.82M 2.97G 4096
/persist 31.46M 4.03M 27.43M 4096
/cache 884.61M 14.61M 870.00M 4096
/persist-lg 7.83M 4.33M 3.50M 4096
/sns 7.83M 4.03M 3.80M 4096
/firmware 63.95M 56.39M 7.56M 16384
/mpt 31.46M 13.36M 18.10M 4096
/mnt/shell/emulated 3.96G 1011.82M 2.97G 4096
/storage/emulated/legacy 3.96G 1011.82M 2.97G 4096
/storage/emulated 677.76M 0.00K 677.76M 4096
/mnt/media_rw/external_SD 3.72G 395.72M 3.33G 32768
/mnt/secure/asec 3.72G 395.72M 3.33G 32768
/storage/external_SD 3.72G 395.72M 3.33G 32768
/storage/emulated/0 3.96G 1011.82M 2.97G 4096
/storage/emulated/0/Android/obb 3.96G 1011.82M 2.97G 4096
/storage/emulated/legacy 3.96G 1011.82M 2.97G 4096
/storage/emulated/legacy/Android/obb 3.96G 1011.82M 2.97G
4096
Thank you! I just pulled your recovery image for the D631 and used flashify to flash it. Now custom CWM recovery is working fully!! Thank you for your work. I am looking into porting a rom to our device so that all of us G Vista owners have some options! Now that we have root and custom recovery we are almost there!
Sent from my LG-D631 using XDA Free mobile app
Man dude that would be awesome. I will even help in aid of development. I dont know exactly what to do but im sure that i could figure something out with all the guides here on xda.
I am in need of other devs to help out...but it looks like none are able..so i dunno where to go from here. Looks like we are stuck.
Sent from my LG-D631 using XDA Free mobile app
Msm8226 is the board for the d631. It is also the board for the v410 lte tablet. Is there any compatibility between the two
Sent from my LG-V410 using Tapatalk
Once rooted with one click, you can install the quick boot app from the Play store and use it to reboot into recovery.
oranget said:
Thank you! I just pulled your recovery image for the D631 and used flashify to flash it. Now custom CWM recovery is working fully!! Thank you for your work. I am looking into porting a rom to our device so that all of us G Vista owners have some options! Now that we have root and custom recovery we are almost there!
Sent from my LG-D631 using XDA Free mobile app
Click to expand...
Click to collapse
what is this is it hope
it's not a brick it's a wonderful egg i'm going to hatch into a beautiful budget-friendly princess
Issues step 6
djacks222 said:
I understand that there is a seperate thread for the LG G Vista, but I was hoping that it was okay to post this. I noticed that there is not any guide on how to install CWM on the D-631 so here is a guide on how to do just that.
First of all..... you will need to enable USB Debugging.
To do this
\go to 'Settings' then 'About Phone' then 'Software Information' then click 'Build number' 7 times or so until it says 'You are now a developer!'
go back to 'Settings' and scroll down to the new box Developer Options
turn it on, and enable USB Debugging. ( I also check stay awake)
I rooted my phone with iRoot, and it installed Kinguser as my super user apk. Whether or not it is the best, I don't know. It just is the only one I could get working.
1. Install The LG Unified drivers from here ( I used LG USB Drivers 3.11)
http://www.mylgphones.com/lg-android-usb-device-drivers
2. Install ADB & fastboot (follow the xda thread here)
http://forum.xda-developers.com/showthread.php?t=2588979
3. now you have to use tese adb commands to zero out the laf partition on your D-631
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(I also ran this command to zero out the actual block partition)
dd if=/dev/zero of=/dev/block/mmcblk0p15
after I eliminated the LG Download so that fastboot takes priority (just as the G3) I could now boot into fastboot.
*Source from here* http://www.theandroidsoul.com/lg-g3-fastboot-mode-61660/
4. boot to fastboot. To do this.. Power down your phone. Hold vol+ and plug your phone into your pc.
It will still say DOWNLOAD MODE at the top, but it should now say 'fastboot processing commands'
5. unlock bootloader with this fastboot command
fastboot oem unlock
*this did not delete anything off my phone*
6. download and flash CWM recovery
Here is the recovery file
https://drive.google.com/file/d/0B-GvkM12QEbMbWxSV2RHcWRMOWs/view?usp=sharing
also on my main google drive
https://drive.google.com/folderview?id=0B-GvkM12QEbMeFFxRThfMlRvMWc&usp=sharing
fastboot flash recovery xxxxxxxxx
"xxxxxxx" is your directory of the recovery.img
bam all done.........
but this is what sucks..... fastboot reboot commands dont work. and idk how to fix that, but. I need help with the rest, PLEASE. and also some tweaks on the recovery file will need to be done. I just made it possible for us
so to reboot you must pull your battery.
I still dont know the hard key combo to enter into recovery so I had to install Xposed Framework from here
http://repo.xposed.info/module/de.robv.android.xposed.installer
then from googlen play I downloaded these
Xposed Additions
G3 Tweakbox <------------= This can enable the option for REboot REcovery
Busybox
SD Maid
(I used SDMaid to uninstall Carrier IQ tracking software, but I had to toggle the carrier IQ autostart component that starts with Android System)
So yeah, long nights, long days, but no bricks and now here it is
+XDA (as posted on your thread) and I am not responsible for any damage that may be caused.
=Do not steal this, give credit where it is due, link it here to this thread please.
Click to expand...
Click to collapse
Wonderful work btw. Needed this thread. I only had one problem!!1
I made int all the way down to Step 6 and got hung up. I have renamed the the file to "recovery.img" and I entered "fastboot flash recovery c:\users\jason\desktop\recovery.img" (file location\file) and Command window says,
target reported max download size of 536670912 bytes
sending 'recovery' (10465 KB)......
okay [ 0.406s]
writing 'recovery'....
FAILED (remote unknown command)
Finished. total time: 0.422s
No CWM recovery... where have i gone wrong?
Thanks in advance.
Drake865 said:
Wonderful work btw. Needed this thread. I only had one problem!!1
I made int all the way down to Step 6 and got hung up. I have renamed the the file to "recovery.img" and I entered "fastboot flash recovery c:\users\jason\desktop\recovery.img" (file location\file) and Command window says,
target reported max download size of 536670912 bytes
sending 'recovery' (10465 KB)......
okay [ 0.406s]
writing 'recovery'....
FAILED (remote unknown command)
Finished. total time: 0.422s
No CWM recovery... where have i gone wrong?
Thanks in advance.
Click to expand...
Click to collapse
If you are rooted, you could try using flashify. It worked for me. It'll load cwm first and reboot, but after the second try you should be up and running.
Questions???Anything on the update for this device thanks
System Dump
I currently have a full system dump of the lg g vista d631 on android version 4.4.2 for the purpose of roms. The one issue I have is I'm not able to get a hold of 2 files, "WCNSS_qcom_cfg.ini" and "WCNSS_qcom_wlan_nv.bin". They are located in the directory etc/firmware/wlan/prima. They are important for wifi connectivity and I don't want to build a rom without them. Can anyone retrieve them?
Edit: I've gotten everything now. I'll work on building a rom for testing.
How would I go about retrieving those two files
---------- Post added at 06:44 PM ---------- Previous post was at 06:39 PM ----------
I have the 2 files that you need but I need a email address to send it to you
Any kdz file or anything how to update to 5.0
at&t d631 rom
Isaiah.E.Scott said:
I currently have a full system dump of the lg g vista d631 on android version 4.4.2 for the purpose of roms. The one issue I have is I'm not able to get a hold of 2 files, "WCNSS_qcom_cfg.ini" and "WCNSS_qcom_wlan_nv.bin". They are located in the directory etc/firmware/wlan/prima. They are important for wifi connectivity and I don't want to build a rom without them. Can anyone retrieve them?
Edit: I've gotten everything now. I'll work on building a rom for testing.
Click to expand...
Click to collapse
Where you able to get a rom put together? I have the d631 5.0.2 rooted and removed the wrong contacts apk and now can't save any contacts. Do you have a way to retrieve the apks from this version?
piptravels said:
Where you able to get a rom put together? I have the d631 5.0.2 rooted and removed the wrong contacts apk and now can't save any contacts. Do you have a way to retrieve the apks from this version?
Click to expand...
Click to collapse
Can't you upload the update zip
Rican39 said:
Can't you upload the update zip
Click to expand...
Click to collapse
Where is the update zip? I have seen a lot of stuff about kdz and tot files but I don't see anything identifying if they're for the AT&T version of the LG G Vista or the Verizon version.
Today, I finally have found where to post for newbies, so I post, thought 4 hours ago I posted on androidforums.
Here is very difficult to operate with this site, and to use this site for with android devices is quite impossible. Only in windows, and not every comfortable. Anyway, I see, that is the first university on the net
Click to expand...
Click to collapse
.
just enter in google: tablet h007 and you shall see the specification, cos I can`t post link now. If anyone has the backup for this model, it shall be about 560 MB. Let me know, not to trouble anyone.
The tablet was rooted by kingoroot, but as you know or not, kingoroot, offers root acces, as the 1 service started, when the device is on, but it does not provide general full root settings, as for example when we are in the recovery menu.
I used some kernel tuner application, and I did not make any backups at all. I edited the file with this application, called build.prop, where I change the attribute of user for superuser. In that way, I though, I could get permissions of full root, I did that, because, I could not see my system partition generally, only from total commander, I could see and do whatever I want. After, I rebooted, and the problem started.
I attach here, my device specifications: Which I watched, while I could use the device:
Android system recovery 3e with sw version: alps.kk1.mp1.v2.11. It is on the photo though but with the different name.
MS board: d95b
Mt6582 (Chip)
All the rest is on the photo
foto.lovestudio.biz/image.uploads/30-07-2015/original-9ec17e355b096718359535e5af42aa4c.png
I have windows vista 32bit 2 service pack.
MTKdroidTools, the application I tried, 4 different versions, 1, last, and 2 in the years, when my phone was produced. It does not read my phone, saying, it is not present. Though all 4 kind of drivers are installed, even adb device driver is installed and all is perfect, all is connected.
The only thing I can use in this mtkdroidtools is adb terminal. I enter there the following command: adv devices, which shows some number of device connected with sideload.
Something like that:
List of devices attached
01234565ABCDEFG recovery
but at the place of recovery, I have
List of devices attached
01234565ABCDEFG sideload
Then, after reading stack-exchange site, I understand, that now I can enter the system partition to get my build.prop file, to change superuser for user as it was before and to return in back to the device, and get my phone worked. But I can`t do that. Cos as I stated before, the device is rooted only by kingoroot, and I works only as the 1 st. service inside android operating system, but not in recovery menu.
So I cant use the following command to get it right. Cos when I enter any of them, but first of all, I enter: adb usb - it says: error: closed
You can then copy the file off the phone:
adb pull /system/build.prop c:\build.prop
You can now edit it in any text editor (recommend Notepad++ because it will preserve the Unix style line endings,) and then copy it back to the phone:
adb push c:\build.prop /system/build.prop
To work with adb terminal, of course I am in the recovery menu and I enter inside ADB SIdeload Application.
I know how to deal as you see, with this problem, but I can`t get to the file, to the system partition in the whole, cos as I understand, the phone is not rooted.
So guys, let`s see what happens next, I am looking forward to your suggestions.
lovestudio said:
.
just enter in google: tablet h007 and you shall see the specification, cos I can`t post link now. If anyone has the backup for this model, it shall be about 560 MB. Let me know, not to trouble anyone.
The tablet was rooted by kingoroot, but as you know or not, kingoroot, offers root acces, as the 1 service started, when the device is on, but it does not provide general full root settings, as for example when we are in the recovery menu.
I used some kernel tuner application, and I did not make any backups at all. I edited the file with this application, called build.prop, where I change the attribute of user for superuser. In that way, I though, I could get permissions of full root, I did that, because, I could not see my system partition generally, only from total commander, I could see and do whatever I want. After, I rebooted, and the problem started.
I attach here, my device specifications: Which I watched, while I could use the device:
Android system recovery 3e with sw version: alps.kk1.mp1.v2.11. It is on the photo though but with the different name.
MS board: d95b
Mt6582 (Chip)
All the rest is on the photo
foto.lovestudio.biz/image.uploads/30-07-2015/original-9ec17e355b096718359535e5af42aa4c.png
I have windows vista 32bit 2 service pack.
MTKdroidTools, the application I tried, 4 different versions, 1, last, and 2 in the years, when my phone was produced. It does not read my phone, saying, it is not present. Though all 4 kind of drivers are installed, even adb device driver is installed and all is perfect, all is connected.
The only thing I can use in this mtkdroidtools is adb terminal. I enter there the following command: adv devices, which shows some number of device connected with sideload.
Something like that:
List of devices attached
01234565ABCDEFG recovery
but at the place of recovery, I have
List of devices attached
01234565ABCDEFG sideload
Then, after reading stack-exchange site, I understand, that now I can enter the system partition to get my build.prop file, to change superuser for user as it was before and to return in back to the device, and get my phone worked. But I can`t do that. Cos as I stated before, the device is rooted only by kingoroot, and I works only as the 1 st. service inside android operating system, but not in recovery menu.
So I cant use the following command to get it right. Cos when I enter any of them, but first of all, I enter: adb usb - it says: error: closed
You can then copy the file off the phone:
adb pull /system/build.prop c:\build.prop
You can now edit it in any text editor (recommend Notepad++ because it will preserve the Unix style line endings,) and then copy it back to the phone:
adb push c:\build.prop /system/build.prop
To work with adb terminal, of course I am in the recovery menu and I enter inside ADB SIdeload Application.
I know how to deal as you see, with this problem, but I can`t get to the file, to the system partition in the whole, cos as I understand, the phone is not rooted.
So guys, let`s see what happens next, I am looking forward to your suggestions.
Click to expand...
Click to collapse
I am sorry, so no one knows, on 3 sites, no one knows. let me know, then I shall not check every hour this post. I t`s better to know, that nothing possible, that believe that smth. is possible. thanks.