{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just pre-ordered this one as a gift for my cousin (gave her a cutout of it since her birthday was yesterday ).
Roughly the same specs as DG310 (which I'm very happy with), but it's 4.5" inch (which kinda makes more sense for the FWVGA screen resolution).
It's apparently built with durability in mind.
CPU: Mediatek 6582 Quad-core 1.3 Ghz
Android: KitKat 4.4
Size (mm): 133.5*68.3*8.8（L×W×H）
Camera: 5.0 MP (back) / 1.3 MP (front)
RAM: 1GB
ROM: 8GB
Dual-sim, 3G, WIFI, BT4.0, GPS, 1800mAh battery by BAK.
Rest of the specs here: http://www.doogee.cc/products_detail/&productId=106.html
It's currently 80$ on Dealextreme + 2 phone cases, from tomorrow to 10/1 82.99$ + an 8GB SD-card.
How much?
leenwen said:
How much?
Click to expand...
Click to collapse
only $84.99 at coolicool.com
Is there a way how to root DG280 ?
cepi666 said:
Is there a way how to root DG280 ?
Click to expand...
Click to collapse
There is a way of rooting dg280. I've done it twice, yet i am not sure how it worked the first time. The second time root genius made it possible.
See attached file.
Good luck.
---------- Post added at 09:30 AM ---------- Previous post was at 08:55 AM ----------
Also i have made a third attempt at rooting the phone and you should know that in order for any of the above root exploits to work you must not install the r10 update released on february 10th. If this update is already installed you manually flash the full r7 rom image from doogee website. Also after getting root you cannot install the r10 update as this one bricks the phone and to recover you must also flash the full r7 rom image.
The r7 image flashing procedure is also pretty complicated because there is no real guide anywhere. There are some files that need editing, because you will need to disable the checksum verification in the flasher because you will get errors from one of the files, errors which are wrong. Also don't try to put the phone in download mode. To flash it just start the flasher select options (i used format+download) and hit the start button. It is just going to wait for a phone. After this just pull the battery from the phone, put it back (don't touch any buttons on the phone, keep it off) and just connect the usb cable to it. After a few second the flasher will show phone info and progress of format and rom upload.
There is also an issue with the usb phone drivers. You need good ones before any of the above procedures. I really cannot help with this because i already had a good number of compatible drivers installed and i just couldn't tell which is the best for this.
Very poor 2g/3g signal reception ??? any one else has experienced the same?
The phone has very very poor 2g/3g signal reception from the mobile networks. The call voice quality is too bad. Call dropping is frequent all the time and voice is transmitted distorted to the other party in call. I tried the phone with all networks that operate in my country, and the result was the same. The phone shows only 1-2 bars at signal cluster, while the other phones show full bars at the same location. So is anyone experiencing the same? Any fix available? Thank you.
leenwen said:
How much?
Click to expand...
Click to collapse
only $19.90 at http://www.pompmall.com/doogee-dg280.html
@lorenc75
I bought the Doogee Leo für my daughter, and she's totally satisfied.
Signal reception is as good as with my Samsung S3, GPS and WiFi is also working good.
I rooted the phone to get a CWM recovery and to deinstall some of the China-Apps.
After 3 Weeks of usage her little brother broke the Micro-USB-Socket while playing Games on the Phone (Charger was plugged in) but that was also no problem, just opened the phone (9 screws) and resoldered the USB-Socket, so it's working again.
All in one I must say, for 80Euros including Shipment from Germany (No Taxes) a good Phone.
Ok, the Flashlight is not the brightest one, but hey.. it was a cheap phone
TimoHL said:
@lorenc75
I bought the Doogee Leo für my daughter, and she's totally satisfied.
Signal reception is as good as with my Samsung S3, GPS and WiFi is also working good.
I rooted the phone to get a CWM recovery and to deinstall some of the China-Apps.
After 3 Weeks of usage her little brother broke the Micro-USB-Socket while playing Games on the Phone (Charger was plugged in) but that was also no problem, just opened the phone (9 screws) and resoldered the USB-Socket, so it's working again.
All in one I must say, for 80Euros including Shipment from Germany (No Taxes) a good Phone.
Ok, the Flashlight is not the brightest one, but hey.. it was a cheap phone
Click to expand...
Click to collapse
i need help, the same thing happend to me, i opened the phone, but i do not know what to look for, can you please help? (i am not often on this site so please contact me on my facebook (Itamar Baum - (username is itwouldgoboom)) thank you.
How to Fix the USB-Connector
Hi everyone. Since I had a few requests on how to do the repair of the USB-Connector, I describe it here although it has nothing to do with Android development. Hope it's OK for you.
I just opened the phone (take out everything, loosen 9 screws).
Then I carefully turned over the USB-Board (1 more screw secured with some kind of adhesive tape) after pulling out the antenna connector, microphone and vibration motor.
Then there are the 5 micro-USB-Pins from the connector to the PCB. In order to have the right alignment of the socket, I insterted a MicroUSB plug into the socket. Then i soldered everything new with ENOUGH tin to get it a little more stable. All you need is a calm hand and a fine soldering-tip. Reassembly in opposite order. But double-Check for shortcuts. And if you are not experienced in soldering small parts, I'd suggest you let it do by someone who knows about this to prevent more damage.
Timo
TimoHL said:
Hi everyone. Since I had a few requests on how to do the repair of the USB-Connector, I describe it here although it has nothing to do with Android development. Hope it's OK for you.
I just opened the phone, then I carefully turned over the USB-Board (1 more screw I think and secured with some kind of adhesive tape) after pulling out the microphone and vibration motor. Then there are the 5 micro-USB-Pins from the Connector to the PCB. In Order to have the right alignment of the Socket, I insterted a MicroUSB Plug in the socket. Then i soldered everything new with ENOUGH tin to get it a little more stable. All you need is a calm hand and a fine soldering-tip. Reassembly in opposite order. But double-Check for shortcuts. And if you are not experienced in soldering small parts, I'd suggest you let it do by someone who knows about this to prevent more damage.
Timo
Click to expand...
Click to collapse
thank you! i was afraid to remove the usb board. it seemed that there are quite a few things connected there at the moment i do not have a fine tip though... guess i may just send it to be fixed :crying:
Where can I recovery ?
DG280 custom recovery
Hi there,
is anyone willing to share with us where to find / download a custom recovery CWM/TWRP for DG280 running lollipop 5.0 version?
I tried the only one recovery available for dg280 on needroom, but it is not working.
Thank you.
hazar1907 said:
Where can I recovery ?
Click to expand...
Click to collapse
lorenc75 said:
Hi there,
is anyone willing to share with us where to find / download a custom recovery CWM/TWRP for DG280 running lollipop 5.0 version?
I tried the only one recovery available for dg280 on needroom, but it is not working.
Click to expand...
Click to collapse
Here's a CWM recovery for the DG280. Haven't tested it yet.
I tried to build Carliv Touch Recovery (CTR) and TWRP for the DG280... they kind of worked, but the touch screen is unusable! Maybe those recoveries are lacking the proper drivers.
Tzul said:
Here's a CWM recovery for the DG280. Haven't tested it yet.
I tried to build Carliv Touch Recovery (CTR) and TWRP for the DG280... they kind of worked, but the touch screen is unusable! Maybe those recoveries are lacking the proper drivers.
Click to expand...
Click to collapse
I flashed it with flash tool in lollipop, doesn't work. Just shows the recovery image and no menu.
Also, i cant root lollipop!
---------- Post added at 01:11 AM ---------- Previous post was at 12:24 AM ----------
lorenc75 said:
The phone has very very poor 2g/3g signal reception from the mobile networks. The call voice quality is too bad. Call dropping is frequent all the time and voice is transmitted distorted to the other party in call. I tried the phone with all networks that operate in my country, and the result was the same. The phone shows only 1-2 bars at signal cluster, while the other phones show full bars at the same location. So is anyone experiencing the same? Any fix available? Thank you.
Click to expand...
Click to collapse
My dg280 has better 2g/3g signal reception than any other mobile i have tested here, even nokia/samsung/lg/motorolla
Has anyone managed to root lollipop? I am trying for hours from yesterday, i created custom system.img, custom recoveries, unsecured boot.img but even if i root it, it doesn't boot again..
gerstavros said:
Has anyone managed to root lollipop? I am trying for hours from yesterday, i created custom system.img, custom recoveries, unsecured boot.img but even if i root it, it doesn't boot again..
Click to expand...
Click to collapse
Found a method on 4PDA, use Google to translate it from Russian.
http://4pda.ru/forum/index.php?showtopic=627006&st=300#entry39327684
I have the Lollipop version and managed to get root very easy using this app - http://androidxda.com/download-kingroot-application. 4.5.0.803 is what I used.
update - can't get ES File Explorer to write to system/app. I always get a not enough space warning. I found out that using this Kingroot app to uninstall system apps opens the door until restart. But you need to remove one system app in order for this to work. Will continue to look for a workaround.
Flashing
Hi,
I failed to root DG280, I regret not reading for example viperasp's hint that from software version r10 it can brick the phone.
I used Kingroot, after second use, it told me everything's fine&rooted. I used then some script that removes Kinguser and puts SuperSU in place of it, it also went OK, SuperSU told it wants to update itself, but it was not possible without restart. But after restart I don't have phone running, so...
Would be really great if someone who went over flashing something to DG280 via some kind of SPFlash tool could share how he/she did that. I got only one tutorial from doogee.cc written in some chinese-english. I downloaded r6 image (the only available at manufacturers website, I don't care about version, just want to have this phone running) and can't flash it... I wonder what version of preloader driver can make this phone visible in SPFlash. Attached "Smartphone multi-port download tool" doesn't see the phone.
Depending on how I'm connecting it - with/without battery, with some/without any keys pressed, it is seen in task manager under ports. Sometimes as "Mediatek DA USB VCOM Port", sometimes it gives continuous appearing/disappearing for ~2sec. of "Mediatek Preloader USB VCOM Port", sometimes USB VCOM Port or MTK USB Port, and Flash tool won't find anything in these cases. Sometimes "MTK USB Port" is left (not disappearing) and this is promising, because Flash tool finds one Com port and displays "COM49 + N/A, scan failed".
If I only got it to display both Preloader COM and MTK USB Port so I think I could do flashing. But how to achieve this?
I tried this on Win XP 386x and win10 x64, same results.
Maybe someone has some knowledge now and is kind enough to share/give some tips? Would be great
qwerty63 said:
Hi,
I failed to root DG280, I regret not reading for example viperasp's hint that from software version r10 it can brick the phone.
I used Kingroot, after second use, it told me everything's fine&rooted. I used then some script that removes Kinguser and puts SuperSU in place of it, it also went OK, SuperSU told it wants to update itself, but it was not possible without restart. But after restart I don't have phone running, so...
Would be really great if someone who went over flashing something to DG280 via some kind of SPFlash tool could share how he/she did that. I got only one tutorial from doogee.cc written in some chinese-english. I downloaded r6 image (the only available at manufacturers website, I don't care about version, just want to have this phone running) and can't flash it... I wonder what version of preloader driver can make this phone visible in SPFlash. Attached "Smartphone multi-port download tool" doesn't see the phone.
Depending on how I'm connecting it - with/without battery, with some/without any keys pressed, it is seen in task manager under ports. Sometimes as "Mediatek DA USB VCOM Port", sometimes it gives continuous appearing/disappearing for ~2sec. of "Mediatek Preloader USB VCOM Port", sometimes USB VCOM Port or MTK USB Port, and Flash tool won't find anything in these cases. Sometimes "MTK USB Port" is left (not disappearing) and this is promising, because Flash tool finds one Com port and displays "COM49 + N/A, scan failed".
If I only got it to display both Preloader COM and MTK USB Port so I think I could do flashing. But how to achieve this?
I tried this on Win XP 386x and win10 x64, same results.
Maybe someone has some knowledge now and is kind enough to share/give some tips? Would be great
Click to expand...
Click to collapse
Check my guide here: https://translate.google.com/transl....gr/forum/showthread.php?p=4883180&edit-text=
Use the drivers from the link there with the autoinstaller. You 'll not have any problem. Flash the latest Croatia Lollipop firmware (find it at needrom.com). And next time, after rooting with kingroot, dont replace it with supersu or other app. Keep kinguser
Related
Since I didn't find much information in English about this phone, I'm posting this guide for this great device.
There are 3 versions of device:
CN - Chinese version (4 GB)
ROW - International (European?) version (4 GB)
ROW 8G - International (European?) version with 8 GB internal memory
If you bought it online from Chinese website (like I did - from to2c.com) then you for sure have "CN" version. If you have a device which came stock with ROW firmware, there is no need to flash new firmware because you are already on international version of the phone and you get the updates over-the-air.
Those phones that came from Chinese sites usually have rooted and multilanguage firmware, but basically it is slightly modified Chinese firmware with Chinese apps still included, Chinese GPS settings, OTA disabled (so you don't loose root and multilanguage ((MoreLocale2)) by OTA update) and old firmware. In this guide I'll post how to change the CN firmware to ROW but keeping the CN modem.img because it isn't compatible across different versions of device. Most of the information I've got from site lenovo-forums.ru.
Why doing this? To get...
latest version of non-Chinese firmware (v S120 ROW)
latest modem from Lenovo VIBE ROM (V52)
CWM recovery
root
GUIDE
Disclaimer: you are doing this at your own risk. Some knowledge and previous experience with flashing MTK devices is highly recommended. If you find something confusing in this guide, then you should probably first learn more about MTK flashing and Android phones in general (hint: google ).
1. TOOLS
- SP_Flash_Tool_v3.1332.0.187, https://www.mediafire.com/?l26qvmalu6m73lw
- MTK preloader drivers, http://forum.xda-developers.com/showthread.php?t=2180436
2. ROM - version S119 ROW full
- download S820_ROW_S119_130922, (LINK) (login information from http://www.bugmenot.com/view/lenovo-forums.ru)
- flash using SP_Flash_Tool_v3.1332.0.187, make sure that all the files are checked, use firmware upgrade mode as shown in pictures bellow...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Flash custom recovery
- get recovery CWM_v6.0.3.4_S820_ROW, download link: https://www.mediafire.com/?82bb42qg55o3ob4 (credits: lenovo-forums.ru)
- flash with SP Flash Tools using Download mode like shown bellow...
4. Flash S120 ROW update (CWM)
- get into recovery by pressing vol down + vol up + power.
- flash this incremental update (S119 -> S120), download: https://www.mediafire.com/?3e11hd2erutsz3k (source lenovo-forums.ru, modified by me because of asert errors in their file)
5. Root device
- enable usb debugging by opening developer menu: Settings -> About -> Versions -> pres 7 times on baseband version
- follow root guide from this link: http://forum.xda-developers.com/showthread.php?t=2247537
6. Change MODEM.IMG to V52 from VIBE ROM
- download this modem.img (V52 from VIBE ROM): https://www.mediafire.com/?au982otib7lkka4
- you flashed international version of firmware (ROW) but modem still have to be from the Chinese ROM to function properly - following guide from this LINK you can swap the MODEM.IMG from ROW version to Chinese (procedure for different phone but works analogously). In short: transfer modem.img to your sdcard, mount /etc/firmware as rw (read/write - you need root rights to do this), copy over existing modem.img, change permissions to 644, reboot phone (pull battery out)
Enjoy the international/EU version of Lenovo S820!
thanks for this very useful thread my friend,
I tried flashing VibeROM,
but it seems no network/signal comming even there is sim card after flashing the ROM.
what seems to be the problem?
Lenovo S820 ROW
repartition
hi great guide. do you have some info how to repartition internal memory on this phone. i have ROW model with 4GB
bakuLaw said:
thanks for this very useful thread my friend,
I tried flashing VibeROM,
but it seems no network/signal comming even there is sim card after flashing the ROM.
what seems to be the problem?
Lenovo S820 ROW
Click to expand...
Click to collapse
It may help if you change the modem.img; try the modem.img from ROW version of the firmware...
Pr0xiMUS said:
It may help if you change the modem.img; try the modem.img from ROW version of the firmware...
Click to expand...
Click to collapse
the problem is when you this procedure,
ur device must be rooted,
its very hard to root viberom,
i try framaroot and the link above,
all failed.
do u have the modem.img from stock ROM,
so that i can flash it with Viberom?
Hi! Does the european Rom (4G) has greek language? Or else, is there anywhere to download the ROM provided by chinese websites (for example to2c.com) which includes aprox. 52 languages?
SIMPLEFBB said:
Hi! Does the european Rom (4G) has greek language? Or else, is there anywhere to download the ROM provided by chinese websites (for example to2c.com) which includes aprox. 52 languages?
Click to expand...
Click to collapse
Try installing MoreLocale2 from Play Store... Those ROMs are not fully translated, you can achieve almost the same with MoreLocale on any other ROM.
Pr0xiMUS said:
Try installing MoreLocale2 from Play Store... Those ROMs are not fully translated, you can achieve almost the same with MoreLocale on any other ROM.
Click to expand...
Click to collapse
Hey, thanks for your answer, but I finally figureed it out on my own :cyclops:..!!
Pr0xiMUS, thanks for this great tutorial,
could you please just give a more noob explanation of step 6 ? (swapping the modem)
im stuck with it and i cannot find my way at lenovo-forums.ru translated.
Hi, I've just tried to flash a rom on my s820. All the procedure went fine (I thought) with a green circle on the screen at the end...
but after disconnecting it from PC, my phone doesn't boot anymore! No way to turn it on, also with powerbutton and vol+, it doesn't show anything on the screen, nor vibrate. Also connected with the charger will not show the charging led signal.
If I connect again to PC it is recognised differently in it has or not the battery, but with flashtools I can't download anything.
Do you have any idea of what I can do?
Thanks
Pago
_Pago_ said:
Hi, I've just tried to flash a rom on my s820. All the procedure went fine (I thought) with a green circle on the screen at the end...
but after disconnecting it from PC, my phone doesn't boot anymore! No way to turn it on, also with powerbutton and vol+, it doesn't show anything on the screen, nor vibrate. Also connected with the charger will not show the charging led signal.
If I connect again to PC it is recognised differently in it has or not the battery, but with flashtools I can't download anything.
Do you have any idea of what I can do?
Thanks
Pago
Click to expand...
Click to collapse
I have also the same problem ! I tried flashing the 119 firm. but then when I try to flash the recovery it gives me an error about the DRAM ! Also phone can;t get past the Lanovo boot screen !
FIXED : Anyone who has the same issue here's the solution :
1) Flash JUST the 119 Firmware
2) Boot into the phone (it will take some time)
3) Connect to WiFi
4) Go to Settings and do an update to get the 120 Firmware through OTA
5) Follow the rest of the Guide !
JimieTheFox said:
I have also the same problem ! I tried flashing the 119 firm. but then when I try to flash the recovery it gives me an error about the DRAM ! Also phone can;t get past the Lanovo boot screen !
FIXED : Anyone who has the same issue here's the solution :
1) Flash JUST the 119 Firmware
2) Boot into the phone (it will take some time)
3) Connect to WiFi
4) Go to Settings and do an update to get the 120 Firmware through OTA
5) Follow the rest of the Guide !
Click to expand...
Click to collapse
First of all, thank you for your time and help!
I tried to keep the button pressed for a long time and to wait for a looooong boot, but nothing happens...
Sadly, I can't download the 119 firmware (or any other..) because as soon as I connect the USB, SP Flash Tool doesn't allow to download anything on the phone and windows start to make the "USB plug" and "USB unplug" sound loop repeated.
Do you have a different way to flash the firmware to the phone?
Bye
Pago
Try this
_Pago_ said:
First of all, thank you for your time and help!
I tried to keep the button pressed for a long time and to wait for a looooong boot, but nothing happens...
Sadly, I can't download the 119 firmware (or any other..) because as soon as I connect the USB, SP Flash Tool doesn't allow to download anything on the phone and windows start to make the "USB plug" and "USB unplug" sound loop repeated.
Do you have a different way to flash the firmware to the phone?
Bye
Pago
Click to expand...
Click to collapse
Ok here're the specific instructions I followed and I have it on 120 ROW + CWM Recovery now :
1) Power off thee phone
2) Follow the Guide on choosing the files
3) Press Firmare Upgrade button and wait for the pink bars to finish
4) Take off the battery
5) While pressing volume up connect the usb cable
6) When the red bar starts let go of volume button
7) Wait for flashing to finish
8) Boot into 119 Firmware
9) Get the 120 via OTA
10) Flash CWM as shown by Guide
If it doesn't wok then :
( Do NOT plug in the usb cable until the pink loading bars have finished and make sure to click ALL the options the tutorial points in the images !!!! ( Don't forget DA DL All with Checksum, preload.img )
a ) Make sure you have installed the MTK drivers for Windows !!! VERY IMPORTANT !!!!
b ) Try with battery in !
c ) Try without pressing volume key !
It's weird but it may work with ANY of the above, I don't know why but it seems each phone requires a different combination of the above !!!
Click to expand...
Click to collapse
P.S. I used Framaroot to root it and it worked fine, got the latest SuperSU now on it and everything works perfect !!!
Tried almost everything.... no success!
Drivers are installed, I have downloaded the wrong preload on the phone with SP Flash with those driver.
When I plug in the USB in the peripheral list appear "Alcatel Single RNDIS Interface", and it suddenly disappears, and then it appears again with a yellow exlamation mark, then again disappears, and so on...
I tried all the possible combinations for enter the META mode (as I can remember it worked when I flashed the incorrect rom some days ago), but the correct device never appears!
I think I have to go with test point way, perhaps it works.
If even this does not, then I'll sadly quit the battle...
Thanks for your help!
Pago
NEVER SAY NEVER!!!!
After reading a LOT of posts... I tried to understand why the phone was recognized as "Alcatel Single RNDIS Interface", and then I tried to reinstall the drivers.
Drivers were already installed, BUT with the phone already connected, during the driver installation, for a while the correct driver was shown... and then disappeared again and there was only "Alcatel Single RNDIS Interface"... again!
So I tried, with SP Flash ready, to reinstall drivers once again, and in the correct moment, I did "software upgrade" and it WORKED!!!
Now I've already booted the phone and is working!
Thanks to all the guys that wrote so many interesting and helping posts and to the guys that answered me!
Hope this can help some other.
Bye
Pago
_Pago_ said:
Tried almost everything.... no success!
Drivers are installed, I have downloaded the wrong preload on the phone with SP Flash with those driver.
When I plug in the USB in the peripheral list appear "Alcatel Single RNDIS Interface", and it suddenly disappears, and then it appears again with a yellow exlamation mark, then again disappears, and so on...
I tried all the possible combinations for enter the META mode (as I can remember it worked when I flashed the incorrect rom some days ago), but the correct device never appears!
I think I have to go with test point way, perhaps it works.
If even this does not, then I'll sadly quit the battle...
Thanks for your help!
Pago
NEVER SAY NEVER!!!!
After reading a LOT of posts... I tried to understand why the phone was recognized as "Alcatel Single RNDIS Interface", and then I tried to reinstall the drivers.
Drivers were already installed, BUT with the phone already connected, during the driver installation, for a while the correct driver was shown... and then disappeared again and there was only "Alcatel Single RNDIS Interface"... again!
So I tried, with SP Flash ready, to reinstall drivers once again, and in the correct moment, I did "software upgrade" and it WORKED!!!
Now I've already booted the phone and is working!
Thanks to all the guys that wrote so many interesting and helping posts and to the guys that answered me!
Hope this can help some other.
Bye
Pago
Click to expand...
Click to collapse
Nice Great job buddy !! It would be nice to know there is a way to get our phones back if we screw up :silly:
JimieTheFox said:
Nice Great job buddy !! It would be nice to know there is a way to get our phones back if we screw up :silly:
Click to expand...
Click to collapse
it would be good if someone successfully installed Viberom with gsm signal working + root tutorial
Grate guide, thank you.
I have a problem with my Bluetooth car set. the other side can't hear me well.
what can I do?
thank you
Hello,
This is really great I've been waiting for Lenovo S820 thread.
...and of course I do have some questions as follow:
Pr0xiMUS said:
Why doing this? To get...
latest version of non-Chinese firmware (v S120 ROW)
latest modem from Lenovo VIBE ROM (V52)
CWM recovery
root
Click to expand...
Click to collapse
FYI: My version infos are:
Lenovo S820_ROW
Android Version 4.2.1
Baseband S820.V21
Build number S820_ROW_8G_S121_131128
My question is: How do I know if I already have the latest modem? How do I checked it?
Pr0xiMUS said:
3. Flash custom recovery
- get recovery CWM_v6.0.3.4_S820_ROW, download link: https://www.mediafire.com/?82bb42qg55o3ob4 (credits: lenovo-forums.ru)
- flash with SP Flash Tools using Download mode like shown bellow...
Click to expand...
Click to collapse
Does the CWM File is for the ROW - International (European?) version 4 GB or 8 GB internal memory? Cause I heard the CWM file will be different.
Does the CWM file will be working on my S820_ROW_8G_S121?
Thank you
This doesn't work, even with the chinese modem, my phone has awfull 3G 2100MHz signal
Latest firmware !
Hi everyone ! I got the latest firmware on my phone ! Not many changes, just a few UI improvements and 1-2 performance improvements ! Also I got koush's superuser in there and latest CWM !!
All i did was :
1) flash the ROW version from the first post
2) get ALL other updates through OTA and NOT flash any CWM or SU !
3) And when I was on the 124 version I flashed the CWM recovery and through recovery I flashed koush's superuser ( much better on my opinion )
(optional)4) I used MTKDroid Tools 2.5.3 to backup my NVRAM and IMEI and delete ALL useless Chinese apps and Lenovo apps and change my locale to eu instead of cn ( Europe instead of Chinese )
I DID NOT REPLACE THE modem.img file and I am getting perfect signal ( Greece ) and perfect 3G speed !!!!!
Hi, folks
I want show you a tutorial how to easy do ROOT and install RECOVERY and then gapps , with a simple tool.
The tool is in Chinese, but you need only to click few times.
Let’s start:
1. Plug your phone to your PC and on the phone choose the option Install driver:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Then install the drivers to your PC.
3. Now on your phone go to setting/ developer options and choose the option USB debugging on.
4.Download the ROOT TOOL from here: http://d-h.st/8Ma
5.Unpack it and run it with administrator rights.
6.Make sure your phone is connected and you have at least 20% battery, Click on the first option on the right site.
you will see this massage don’t click on anything
7. Now wait , your phone will restart and you should see the SUper user app in your apps.
In the tool click on OK
8.Lets continue with the RECOVERY installation. Click on the second option:
9. The same massages will appear ,do the same like on the earlier steps , just wait...
10. Your phone should now boot into recovery , click on the first option - this will reboot your phone
11. If you want google apps continue. Download gapps from here: http://goo.im/gapps/gapps-jb-20130813-signed.zip
12. Put the zip into the root of internal memory.
13. Turn your phone off and enter the recovery by holding volume up + power button until the phone vibrates , then release the power button.
14. You are in recovery now , go to the second option , than choose the first option , select your file , than choose the first option, this will install the google apps.
15. Now leave the recovery.
16. ALL done
I wish you luck
all credist go to myzte.cn
EDIT: REUPLOADED SCREENSHOTS
good,thanks
Sent from my ZTE Grand S II LTE using XDA Free mobile app
5KKKKK said:
good,thanks
Sent from my ZTE Grand S II LTE using XDA Free mobile app
Click to expand...
Click to collapse
You are welcome
BTW , when the next update is out version B07/B08 (i hope it is the big 4.4 update) , i will modify the ROM- with deleting the chinese apps , replacing chinese email , gallery, camera apps to original google one. So mostly stock
I like this phone,but the main problem is it has few ROMs,it seems that zte is not very popular
Sent from my ZTE Grand S II LTE using XDA Free mobile app
Danger ahead
Hello everybody,
I wanted to warn you, I followed this guide and after doing the root procedure my phone is bricked DEAD.
Won't turn on, won't do anything, not even charghing when power plug is connected, I just killed my phone after about 30 minutes of ownership. :/
PLEASE WAIT A LITTLE BIT BEFORE DOING THIS.
My phone is a grey ZTE Grand S II (NBA Edition, from what I see on the box...).
Does anybody here have an idea HOW I could get this back from the dead? :angel:
*** UPDATE ***
I was able to make it work!! Sorry for sounding so alarmed before... I was in panic mode.
If this doesn't work at first please try it on another PC, or switch USB port, and make yourself a big favor by using this:
http://visualgdb.com/UsbDriverTool/
to install your Android ADB driver.
The ZTE Grand S II (S291) is a GREAT handset and I hope the devs get interested because it's one of the BEST prcie/value ratio around...
Got it for 280 € on Aliexpress...
Thank You.
S.
Simmessa said:
Hello everybody,
I wanted to warn you, I followed this guide and after doing the root procedure my phone is bricked DEAD.
Won't turn on, won't do anything, not even charghing when power plug is connected, I just killed my phone after about 30 minutes of ownership. :/
PLEASE WAIT A LITTLE BIT BEFORE DOING THIS.
My phone is a grey ZTE Grand S II (NBA Edition, from what I see on the box...).
Does anybody here have an idea HOW I could get this back from the dead? :angel:
Thank You.
S.
Click to expand...
Click to collapse
Oh , that's not good , but no one bricked the phone to time...
But please look at the titile, have you the ZTE GRAND SII (s251) or the ZTE GRAND SII LTE (s291) because they're completely different phones.
Difference?
Hello Jozco,
I don't know, but I finally managed to get it back from the dead, by removing the battery and re-connecting it to the power plug, I can now turn it on again...
In About phone under model number it says ZTE S291.
I found something strange, when I issue a "adb reboot bootloader" command the phone goes off and dead, I have to detach the battery to be able to turn it on again... any ideas?
The phone has a NBA logo on the box, a gray cover, and I got it here:
http://www.aliexpress.com/snapshot/6097854185.html
Do you have any clues, I'm going crazy...
THANKS!
S.
jozco313 said:
Oh , that's not good , but no one bricked the phone to time...
But please look at the titile, have you the ZTE GRAND SII (s251) or the ZTE GRAND SII LTE (s291) because they're completely different phones.
Click to expand...
Click to collapse
Simmessa said:
Hello Jozco,
I don't know, but I finally managed to get it back from the dead, by removing the battery and re-connecting it to the power plug, I can now turn it on again...
In About phone under model number it says ZTE S291.
I found something strange, when I issue a "adb reboot bootloader" command the phone goes off and dead, I have to detach the battery to be able to turn it on again... any ideas?
The phone has a NBA logo on the box, a gray cover, and I got it here:
http://www.aliexpress.com/snapshot/6097854185.html
Do you have any clues, I'm going crazy...
THANKS!
S.
Click to expand...
Click to collapse
Oh so , that’s seems to be only a ADB driver problem, had it also , because i had a lot of phones to flash , my drivers were mixed up...
just download this: http://visualgdb.com/UsbDriverTool/
install it , open it , plug your phone to the pc , you will see ZTE Handset ADB Interface click on it and under Android ADB driver click install , this will install the universal ADB driver it should work.
I hope we get your phone rooted
I did the steps you suggested but that didn't change anything
The driver situation is ok, as you can see from the screenshot, yet, it WON'T reboot in the bootloader.
Whenever I issue a "adb reboot bootloader" it simply dies... and I have to remove battery.
Obviously I can't make fastboot work this way, therefore I can't move further, any tips?
Thank You!
S.
---
jozco313 said:
Oh so , that’s seems to be only a ADB driver problem, had it also , because i had a lot of phones to flash , my drivers were mixed up...
just download this: http://visualgdb.com/UsbDriverTool/
install it , open it , plug your phone to the pc , you will see ZTE Handset ADB Interface click on it and under Android ADB driver click install , this will install the universal ADB driver it should work.
I hope we get your phone rooted
Click to expand...
Click to collapse
Simmessa said:
I did the steps you suggested but that didn't change anything
The driver situation is ok, as you can see from the screenshot, yet, it WON'T reboot in the bootloader.
Whenever I issue a "adb reboot bootloader" it simply dies... and I have to remove battery.
Obviously I can't make fastboot work this way, therefore I can't move further, any tips?
Thank You!
S.
---
Click to expand...
Click to collapse
I mean this:
BTW did you checked USB debbuging , when you have connected your phone in the connection type have you checked Connect to PC software
?
jozco313 said:
I mean this:
BTW did you checked USB debbuging , when you have connected your phone in the connection type have you checked Connect to PC software
?
Click to expand...
Click to collapse
Yes, that's what I did! Then the software asked me to replace adb_usb.ini and perform adb kill-server, which I did...
C:\Windows\system32>adb kill-server
C:\Windows\system32>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
d70ec4e0 device
I can confirm USB debugging is enabled and my connection mode is "Connect to PC software".
I checked and re-did everything twice and still, adb reboot bootloader makes my phone die: screen black, no lights and won't even turn on unless I remove the battery...
If I'm doing something wrong, I really don't know what it is
Ideas?
S.
Simmessa said:
Yes, that's what I did! Then the software asked me to replace adb_usb.ini and perform adb kill-server, which I did...
C:\Windows\system32>adb kill-server
C:\Windows\system32>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
d70ec4e0 device
I can confirm USB debugging is enabled and my connection mode is "Connect to PC software".
I checked and re-did everything twice and still, adb reboot bootloader makes my phone die: screen black, no lights and won't even turn on unless I remove the battery...
If I'm doing something wrong, I really don't know what it is
Ideas?
S.
Click to expand...
Click to collapse
I really don´t know :/ , when you can try it on another PC...
jozco313 said:
I really don´t know :/ , when you can try it on another PC...
Click to expand...
Click to collapse
Later today I'll do another attempt with another PC I have at home, but I tend to believe this is related to the ZTE device itself, it's actually very strange that the bootloader is not responding, could it be faulty or simply that the bootloader has been wiped in some way?
I know it doesn't make a lot of sense since the phone itself is booting into ZTE Android just fine... but I'm left wondering, if things continue this way I'm gonna return it and ask my money back...
I'll let you know as soon as I can do some more testing, Thanks a lot for now!
S.
no way...
Simmessa said:
Later today I'll do another attempt with another PC I have at home, but I tend to believe this is related to the ZTE device itself, it's actually very strange that the bootloader is not responding, could it be faulty or simply that the bootloader has been wiped in some way?
I know it doesn't make a lot of sense since the phone itself is booting into ZTE Android just fine... but I'm left wondering, if things continue this way I'm gonna return it and ask my money back...
I'll let you know as soon as I can do some more testing, Thanks a lot for now!
S.
Click to expand...
Click to collapse
I tried again, from another PC with windows 7 32bit but same story again... after reboot it's dead and I must do the battery trick.
Here's my plan:
On my phone there's OS v B04 (please see screenshot)
So I'm planning to install v B06 which I got from ZTE support website...
What do you think? I'm hoping this will fix my broken bootloader!
Thanks!
S.
Simmessa said:
I tried again, from another PC with windows 7 32bit but same story again... after reboot it's dead and I must do the battery trick.
Here's my plan:
On my phone there's OS v B04 (please see screenshot)
So I'm planning to install v B06 which I got from ZTE support website...
What do you think? I'm hoping this will fix my broken bootloader!
Thanks!
S.
Click to expand...
Click to collapse
This is the exact file (ROM) I plan to flash on my device, should I do it?
(please see attach).
Thanks!
S.
Simmessa said:
This is the exact file (ROM) I plan to flash on my device, should I do it?
(please see attach).
Thanks!
S.
Click to expand...
Click to collapse
LATEST update:
I don't know why but I re-did the whole procedure with the second PC and WITHOUT explanation this time it worked like a charme... SORRY for wasting your time, but I'm not even sure WHY this time it worked... the only thing I did was switching a couple of usb ports and using the driver supplied by USBdrivertool (The link can found above in this thread)
So, if you have problems with this procedure PLEASE KEEP THE FAITH and you'll eventually do it!
THANK YOU everybody and especially jozco313 for the help and assistance!
S.
Simmessa said:
LATEST update:
I don't know why but I re-did the whole procedure with the second PC and WITHOUT explanation this time it worked like a charme... SORRY for wasting your time, but I'm not even sure WHY this time it worked... the only thing I did was switching a couple of usb ports and using the driver supplied by USBdrivertool (The link can found above in this thread)
So, if you have problems with this procedure PLEASE KEEP THE FAITH and you'll eventually do it!
THANK YOU everybody and especially jozco313 for the help and assistance!
S.
Click to expand...
Click to collapse
You are welcome I help when i can.
But i told you it can’t be the bootloader , because without it would be the device totally broken , you wouldn’t be able to turn on your phone.
BTW you can Update/Edit your first post in this thread , you know some people maybe get scared of buying this phone , and remember when the number of users will raise the development will be also better.
jozco313 said:
You are welcome I help when i can.
But i told you it can’t be the bootloader , because without it would be the device totally broken , you wouldn’t be able to turn on your phone.
BTW you can Update/Edit your first post in this thread , you know some people maybe get scared of buying this phone , and remember when the number of users will raise the development will be also better.
Click to expand...
Click to collapse
Hi Jozco,
sure you're right, I edited my post 'cause all is doing good now, this phone blows my mind!
The only issue I'm having is that Google Sync isn't updating my contacts... so I had to migrate them manually from my old phone, is it like that for you?
Thanks!
S.
Simmessa said:
Hi Jozco,
sure you're right, I edited my post 'cause all is doing good now, this phone blows my mind!
The only issue I'm having is that Google Sync isn't updating my contacts... so I had to migrate them manually from my old phone, is it like that for you?
Thanks!
S.
Click to expand...
Click to collapse
I really don´t know but i think yes i had duplicite contacts , because i updated from .vcf file from my old phone.
BTW you are right the phone is just great
ROOT
Hi, can help me anyone? I can´t provide root because the file for rooting seems to be damaged. I download ok, but unpacking is not possible. It appears note about corrupt or damaged file. Is it possible to download from different link? Thanks for help and answer
It´s ok now. Root was success
Hello there friends. I have accidentally corrupted the bootlader of the phone.
I have trying to flash the phone using Odin and in the bootloader I selected AP file. I did not read it carefully.
Now the phone's bootloader is corrupted. It Show this on the screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I connect it with PC it detects and COM port detects too. Can I repair the bootloader of this phone. Please help me. I will be very grateful.
Thank you
saaqirajput said:
Hello there friends. I have accidentally corrupted the bootlader of the phone.
I have trying to flash the phone using Odin and in the bootloader I selected AP file. I did not read it carefully.
Now the phone's bootloader is corrupted. It Show this on the screen
When I connect it with PC it detects and COM port detects too. Can I repair the bootloader of this phone. Please help me. I will be very grateful.
Thank you
Click to expand...
Click to collapse
If you can still go into download mode, all is not lost
Try the AT&T unbrick using he following mirror page:
http://forum.xda-developers.com/infuse-4g/general/mirror-development-files-t3011627
Hope this helps.
joel.maxuel said:
If you can still go into download mode, all is not lost
Try the AT&T unbrick using he following mirror page:
http://forum.xda-developers.com/infuse-4g/general/mirror-development-files-t3011627
Hope this helps.
Click to expand...
Click to collapse
Last night it was being detected and Com Port was also showing but now it is not. I haven't done anything to the phone between this time.
When I plug in the cable phone detects but com port does not show up. Please guide me. Thanks for your answer
saaqirajput said:
Last night it was being detected and Com Port was also showing but now it is not. I haven't done anything to the phone between this time.
When I plug in the cable phone detects but com port does not show up. Please guide me. Thanks for your answer
Click to expand...
Click to collapse
Silly question...are you in Download Mode now? Easy way to achieve is to pull and reinsert battery, then hold down both volume buttons while plugging in the USB cable.
If you are there and no COM port connection, then are you using a different USB port (or PC) since last time? It is said that Download Mode does not like USB 3.0.
Hope this helps.
joel.maxuel said:
Silly question...are you in Download Mode now? Easy way to achieve is to pull and reinsert battery, then hold down both volume buttons while plugging in the USB cable.
If you are there and no COM port connection, then are you using a different USB port (or PC) since last time? It is said that Download Mode does not like USB 3.0.
Hope this helps.
Click to expand...
Click to collapse
No sir phone it is not getting in download mode.
Like I said last night it was going into download mode today it is not.
Some hardware is detected but com port is not being detected. No samsung port in device manager.
I think the bootloader is corrupted. As I said I opened the PDA file in bootloader section and then very very stupidly pressed the start button.
It flashed 17 percent and then stopped. I then again even more stupidly (like it is even possible to be this much if an idiot, but evidently I am) disconnected pulled the battery out and tried to get into download mode.
It did screen was messed up showing rainbows but Odin detected the phone.
Then I made this post after the first reply I tried to go into download mode so something is detected but not the com port.
So I think it is safe to say that the bootloader is corrupted. Now is there a way to repair the bootloader without the ort jag?
Thank you very much for your answer and your time.
saaqirajput said:
No sir phone it is not getting in download mode.
Like I said last night it was going into download mode today it is not.
Some hardware is detected but com port is not being detected. No samsung port in device manager.
I think the bootloader is corrupted. As I said I opened the PDA file in bootloader section and then very very stupidly pressed the start button.
It flashed 17 percent and then stopped. I then again even more stupidly (like it is even possible to be this much if an idiot, but evidently I am) disconnected pulled the battery out and tried to get into download mode.
It did screen was messed up showing rainbows but Odin detected the phone.
Then I made this post after the first reply I tried to go into download mode so something is detected but not the com port.
So I think it is safe to say that the bootloader is corrupted. Now is there a way to repair the bootloader without the ort jag?
Thank you very much for your answer and your time.
Click to expand...
Click to collapse
Download mode is supposed to be independent of the bootloader, so if you still cannot get into Download Mode, you should luck out with a jig.
joel.maxuel said:
Download mode is supposed to be independent of the bootloader, so if you still cannot get into Download Mode, you should luck out with a jig.
Click to expand...
Click to collapse
Wait you mean even if I have messed up the bootloader I can still get into download mode. Wow this is great news. Thank you very much.
Can you please tell me if I can create this jig thingie, do you know a guide because I am pretty sure I am never going to find one here in my country.
Thank you very much for your help
I have seen some videos looks pretty simple just put a 300 k ohm resistor between the 4th and 5th leg.
I will try and make the jig and post the result tomorrow.
@joel.maxuel thank you very much for your time.
joel.maxuel said:
If you can still go into download mode, all is not lost
Try the AT&T unbrick using he following mirror page:
http://forum.xda-developers.com/infuse-4g/general/mirror-development-files-t3011627
Hope this helps.
Click to expand...
Click to collapse
Hello sir, if I am able to get into download mode will flashing the Phone and PDA files from your package be enough or do I need to find the bootloader too from somewhere?
saaqirajput said:
Hello sir, if I am able to get into download mode will flashing the Phone and PDA files from your package be enough or do I need to find the bootloader too from somewhere?
Click to expand...
Click to collapse
The Unbrick package rescues half-trashed bootloaders (among other things) from what I read in other parts of the forum, so you should be fine. You may, however, need to flash a back to root package (my mirror has option C, albeit in an extracted mess) in order to get system working properly again. When I had my Infuse, it was the Rogers version, so I could never use the AT&T packages (so I never knew first-hand the difference between the unbrick and back-to-stock).
Can cross that bridge when you come to it. Hope this helps.
Okay I am having trouble making a jig. I could not find a proper 301 k resistor to I stiched 3 100k resistors. Somehow it is not working. Maybe the USB connector us faulty. It had four connectors on the main side and 1 on the other.
I will change the USB connector and try again.
Thank you very very much
saaqirajput said:
Okay I am having trouble making a jig. I could not find a proper 301 k resistor to I stiched 3 100k resistors. Somehow it is not working. Maybe the USB connector us faulty. It had four connectors on the main side and 1 on the other.
I will change the USB connector and try again.
Thank you very very much
Click to expand...
Click to collapse
Hmmm, that should work... 301K is pretty specific but there are a lot of variance with resistors, and unless the variance is being amplified by daisy-chaining three 100K's, there shouldn't be a problem. If you have a multimeter, you should check the resistance readout to see if it is off by much.
If not, then it comes back to my original theory. Jacked bootloaders can be modified/restored via ODIN or Heimdall, although the problem screen you have (in the end, a really jacked bootloader) isn't the same as what I was going on (which was the wrong, partially functioning bootloader).
I thought the Download/Odin mode was called off at the Modem level (before the bootloader), but I may be wrong. If so (that is, if your jig does not work), you may need a JTAG service after all.
Sorry for any wasted effort.
I could not find a 5 pin USB connector, I tore apart at least 7 USB cables and all of them ONLY had 4 pins.
I think I am going to have to tear apart the original cable of my S3 and I really really don't want to do that.
I will post the final results on Friday evening
Okay I found a 5 pin connector and made a jig but it did not work. Looks like I a going to have to pay for a jtag service.
Thank you again for all your help
Fixed my Phone
All right I have finally fixed it. The problem was I had some newer or I don't know older driver versions installed. I installed i997 Kies mini and installed the driver that came with that software.
And as soon as I connected the phone while pressing Vol Up + Vol Down computer detected it and odin detected it too. Then I installed your provided firmware.
It is okay now. It is working, there is a rainbow effect every time I turn it on but that is okay. Only recovery is not working. I can't go into recovery.
Everything else is working fine. Thank you very much for all your help.
Okay here's where all this started https://www.facebook.com/groups/130...61465&ref=notif¬if_t=group_comment_mention
Windows and Android Drivers are always a bothersome attempt at trying to get to work properly. Always with a hiccup.
I formated a new laptop with Windows 7 64 Bit Sp1
It still acts as though I don't have a bootloader, recovery menu or chinese mediatek diagnostics menu.
Phone is just constantly looping off and on, in SP Flash Tool it'll timeout. I let the battery drain yesterday and did get a full battery and the green circle.
Me and Nomi (the developer of the rom) tried everything yesterday and he even said he hasn't seen anything like it before, but had driver issues before too.
I'd believe it's still got USB Debugging and looks to still be OEM Bootloader Unlocked as I have the text on the bootscreen.
Just trying to think of anything else I can do, as unihertz hasn't answered my email since yesterday afternoon at 2.
But this seems to be a common problem as you'll see in this reddit:
https://www.reddit.com/r/UnihertzTitan/comments/i33me3
Help the poor UniHurtz TitanFALL!
DorkyDev said:
Okay here's where all this started https://www.facebook.com/groups/130...61465&ref=notif¬if_t=group_comment_mention
Windows and Android Drivers are always a bothersome attempt at trying to get to work properly. Always with a hiccup.
I formated a new laptop with Windows 7 64 Bit Sp1
It still acts as though I don't have a bootloader, recovery menu or chinese mediatek diagnostics menu.
Phone is just constantly looping off and on, in SP Flash Tool it'll timeout. I let the battery drain yesterday and did get a full battery and the green circle.
Me and Nomi (the developer of the rom) tried everything yesterday and he even said he hasn't seen anything like it before, but had driver issues before too.
I'd believe it's still got USB Debugging and looks to still be OEM Bootloader Unlocked as I have the text on the bootscreen.
Just trying to think of anything else I can do, as unihertz hasn't answered my email since yesterday afternoon at 2.
But this seems to be a common problem as you'll see in this reddit:
https://www.reddit.com/r/UnihertzTitan/comments/i33me3
Help the poor UniHurtz TitanFALL!
Click to expand...
Click to collapse
Are you needing help or you solved the bootloop?
I'll find out when I get home from work this morning Unihertz did finally reply to my email at 3am
I'm going to try in both Ubuntu and Windows as they have me tute's and files for both.
On that and the windows note can anyone recommend which driver version works best doesn't matter if it's 7 or 10, so long as it's 64Bit supported.
DorkyDev said:
I'll find out when I get home from work this morning Unihertz did finally reply to my email at 3am
I'm going to try in both Ubuntu and Windows as they have me tute's and files for both.
On that and the windows note can anyone recommend which driver version works best doesn't matter if it's 7 or 10, so long as it's 64Bit supported.
Click to expand...
Click to collapse
platform-tools-latest | drivers USB OEM | MTK USB driver
Obviusly you only need flash stock recovery.img as your device has A9.
For Custom Recovery like TWRP maybe I can ask my friend to help you. If - you still TWRP want?!
Where's the link for that I'll try and see as even with a reply from Unihertz and new files I'm still running into the same error. Where constant looping and when plugged in attempting to flash the factory firmware it times out with a red Download DA bar loading at 100% in seconds and then two minutes later timing out and giving me error code 0xXC0010005.
RN I don't think it'd be possible to get it to stay in bootloader or on long enough to fully do the ADB or Powershell twrp.img flash, interestingly enough I did find MTK Droid Tools v2.5.3B has a rewrite boot and recovery option and askes for the img before proceeding and I didn't do anything else after that though cause it wants a .prm as for a scatter file. Oh and it has ADB builtin to the program.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DorkyDev said:
Where's the link for that I'll try and see as even with a reply from Unihertz and new files I'm still running into the same error. Where constant looping and when plugged in attempting to flash the factory firmware it times out with a red Download DA bar loading at 100% in seconds and then two minutes later timing out and giving me error code 0xXC0010005.
RN I don't think it'd be possible to get it to stay in bootloader or on long enough to fully do the ADB or Powershell twrp.img flash, interestingly enough I did find MTK Droid Tools v2.5.3B has a rewrite boot and recovery option and askes for the img before proceeding and I didn't do anything else after that though cause it wants a .prm as for a scatter file. Oh and it has ADB builtin to the program.View attachment 5518101
Click to expand...
Click to collapse
Search in the internet How install MTK drivers, specially in the Win7. Better in Win10 and if you as that so the drivers [link] is much better, You can try installing that file but need reboot your computer. After try flash with SPFT.
Don't choose FORMAT+ALL or any option with FORMAT+........
Win7 need more effort to start drivers for Mediatek devices!
You can try pressing constantly the VOL - button when put USB for SPFT work.
The issue I keep running into here is no matter how charged the battery is, it won't stay power up long enough to even attempt to correctly install the drivers. (I think at least, still don't ever see a unknown device in other devices), if I could get that far I'd probably stand a chance of recovering it.
DorkyDev said:
The issue I keep running into here is no matter how charged the battery is, it won't stay power up long enough to even attempt to correctly install the drivers. (I think at least, still don't ever see a unknown device in other devices), if I could get that far I'd probably stand a chance of recovering it.
Click to expand...
Click to collapse
We often don't realize that certain errors are normal on our machine. So the question is to test in others computers.
But there are possibilities of company blocks or even something that has happened on the phone without it really should happen.
Some interesting cases:
1- I noticed with the image you showed about trying to flash all the firmware.
** So even if you have tried the Download only or Firmware Upgrade options, the question remains if you tried to flash only the recovery.img file? Obviously you can have the same error in SPFT?!
2- Cases of hardware vs software that match the use and characteristics found such as restarting the PC and trying to flash in a different USB port. Same problem?!: Drivers are resolved?!
The biggest case of suggesting something or thinking that this or that is a problem wastes precious time. Confirm the main steps!:
1- Driver correctly installed and working;
2- Driver works: Different USB PORT tested;
3- SPFT version must be tested. Mainly previous versions to confirm the error message that persists or may disappear;
4- Phone particularities: pressing the VOL buttons for a while can trigger the preloader that is responsible for the connection between the SPFT and your phone on the computer. Switching to VOL+ or Power or VOL- with VOL+ or VOL+ VOL - and Power may solve or confirm the non-solution.
Best way: Win10 with driver updates. Find the way to disable unsigned driver installations. But you can use this driver and you must restart your computer for it to take effect.
Make sure the USB port has a speed feature for the flashing process. Example: All USB ports are 2.0 only and SPFT asks for a USB 3.0 port to make the connection.
With everything confirmed the rest is something to question in relation to having the correct firmware file or the device itself having blocked the installation process due to a drastic change in the preloader or something that has changed and is blocking it.
Look previous posts about that so all depends on what you have and how you use it.
Unfortunately everyone (including me) who went through bad times like the one you have now, has a headache because it's a simple process and doesn't know what to do. But on the other hand, it's a huge learning experience when we solve it.
But there is still a choice without a headache: take it to a technical assistance and pay for it!
No on drivers when it goes to do the typical windows installation with the installation boxes in the upper left corner, I keep getting red x's.
I'm letting it charge some more and tomorrow trying again on my windows 7 laptop, as I think I'm also getting hung up on disabling driver signatures on windows 10 laptop. IDK if it's cause I'm dual booting JingOS 0.9 and that cancels out F7 or what the hang up is on that part.
In all honesty I think you'll end up finding that the only way to recover it is by removing and reprogramming the nand in a proper programmer.
shivadow said:
In all honesty I think you'll end up finding that the only way to recover it is by removing and reprogramming the nand in a proper programmer.
Click to expand...
Click to collapse
Would that also be done in SP Flash Tool or another software? I've also got these MTK tools.
Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
I discovered this by finding Miracle Flash Tool and clicked on Android tab, loaded the scatter file and it took and accepted it and then said boot.img missing please load and pulled up a selection window.
IDK SP Flash Tool never said that. I got drivers to work once and then rebooted now can't get them to work again keeps saying unrecognized usb device. At least it's a bit of progress.
DorkyDev said:
Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
I discovered this by finding Miracle Flash Tool and clicked on Android tab, loaded the scatter file and it took and accepted it and then said boot.img missing please load and pulled up a selection window.
IDK SP Flash Tool never said that. I got drivers to work once and then rebooted now can't get them to work again keeps saying unrecognized usb device. At least it's a bit of progress.
Click to expand...
Click to collapse
If you have more drivers for others phones like samsumg, motorola, lg, etc so remove that's and reboot computer. Install again MTK Drivers, UAC permissions and reboot computer. Test SPFT.
But here a good video to see and may be can fix - confirm driver issue in Win7:
Drivers: https://drive.google.com/file/d/1V2FducGB4pNpbkJWVmk2sfRJpf4Q5Bth/view
DorkyDev said:
Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
Click to expand...
Click to collapse
Maybe corrupted zip file?
I wanted to update Lenovo TAB 2 A7-20F trough SP Flash tool since Android 4.4.2 is really old and kind of useless. I started flashing Lollipop update but after some time flash tool showed error that I can't remember. The device got bootloop. I have seen that I have putted to "Download Only" mode in flash tool instead of "Firmware Update" or "Download Only + Format All", so I tought that's the reason why my device got bricked . Now Instead of just flashing ROM again I used Format Tab in SP flash tool and formated Tablet. And now it's hard bricked. It's not charging or turning on. Not detected by PC when pluged . I tried opening it and removing battery and trying different key combo to put it in META mode since I think preloader is formated as well. If anyone has any idea how can I fix it please replay. I watched youtube tutorials that didn't help . I probably missed something so send help . I guess I have to learn hard way.
IF you want specs here they are:
Lenovo Tab 2 A7-20 - Full tablet specifications
www.gsmarena.com
try to open and search for kcolo or colo + gnd in motherborad and make a jumper and its gonna back to life after that try to flash this rom
like in the image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lenovo_Tab_2_A7-20F_MT8127_S000011_160318
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Ugh...
I think I have problem. I know for kcolo and gnd method but just take a look at this picture.
This is motherboard of my tablet. Most of points aren't labeled and bruteforcing them could damage motherboard. And there is this big heatsink I guess so , maybe it's under there...
I did find stock ROM, only problem is that it's not detected in device manager at all.
Here is the image the closeup image without heatsink.
These are all contact point I could find. There are 9 total. 4 of them near USB port , 3 near battery plug at bottom that you can't rly see but they are unlabeled , and 2 more that I am not sure about what they do. One of them is near camera and other near sd card reader. Not even sure if these are possible test points.
I was able to find and join kcolo ( volume + and volume - points in my case). Now the problem is that after installing driver and trying to flash I get error 4032 in sp flash tool. I tried older versions but they don't support it;
I tried different drivers but didn't help. If anyone can help pls replay.
Nem1x said:
I was able to find and join kcolo ( volume + and volume - points in my case). Now the problem is that after installing driver and trying to flash I get error 4032 in sp flash tool. I tried older versions but they don't support it;View attachment 5557329
I tried different drivers but didn't help. If anyone can help pls replay.
Click to expand...
Click to collapse
Can you provide a picture or explain what you did? I cant seem to find the kcolo/colo and ground pins i need to connect. I would aprechiate it a lot if you gave me an explanation on the process!
You kinda destroyed the whole software by using the format tab. If you didn't, you could've still reinstalled the stock ROM. I have a Lenovo Tab 2 A7-10F that was bricked itself, but I have no idea what's going on
ImmortalChanger said:
You kinda destroyed the whole software by using the format tab. If you didn't, you could've still reinstalled the stock ROM. I have a Lenovo Tab 2 A7-10F that was bricked itself, but I have no idea what's going on
Click to expand...
Click to collapse
Im in a similar situation, i flashed a Lenovo Tab 2 A7-10F rom at Lenovo Tab A7-20F. Tablet wont get recognized by a computer, nor boot nor show any signs of life. Its like this for 1,5 year. Is it possible to bring it back to life?
zisinikos said:
Im in a similar situation, i flashed a Lenovo Tab 2 A7-10F rom at Lenovo Tab A7-20F. Tablet wont get recognized by a computer, nor boot nor show any signs of life. Its like this for 1,5 year. Is it possible to bring it back to life?
Click to expand...
Click to collapse
It’s complicated. The Lenovo Tab 2 A7-10F and 20F are different tablets, so the ROMs compatible with either won’t be compatible with the other. First, make sure the battery is somewhat charged. The energy transfer should depend on the hardware, not the software. I did unbrick my 10F recently but I was able to power it on and the PC recognised it, although it took some time to find the right drivers. Assuming you’re using Windows, have you checked in Device Manager to see if the device is present? I had the same issue where I couldn’t interact with the tablet from the PC but that was because of the absence of drivers. I don’t know precisely what can be done if it doesn’t even turn on, but it could just be a dead battery (that is, if you haven’t tried to hook it up to the charger).
I was able to completely fix and update tablet to Android 5. The golden points are located at back of the motherboard:
The two points at the bottom when connected should make your device recognized in device manager.
After that you install mediatek drivers onto that device and flash stock rom with SP Flash tool.
I unbricked it more than 2 months ago but I was lazy to write this so sorry for waiting.
ImmortalChanger said:
It’s complicated. The Lenovo Tab 2 A7-10F and 20F are different tablets, so the ROMs compatible with either won’t be compatible with the other. First, make sure the battery is somewhat charged. The energy transfer should depend on the hardware, not the software. I did unbrick my 10F recently but I was able to power it on and the PC recognised it, although it took some time to find the right drivers. Assuming you’re using Windows, have you checked in Device Manager to see if the device is present? I had the same issue where I couldn’t interact with the tablet from the PC but that was because of the absence of drivers. I don’t know precisely what can be done if it doesn’t even turn on, but it could just be a dead battery (that is, if you haven’t tried to hook it up to the charger).
Click to expand...
Click to collapse
Thanks for the help but unfortunately I've already lost all hope. Ive tried everything. I don't really care about the device that much so it doesn't bother me.
zisinikos said:
Thanks for the help but unfortunately I've already lost all hope. Ive tried everything. I don't really care about the device that much so it doesn't bother me.
Click to expand...
Click to collapse
Have you tried the method I showed above? Maybe your drivers are not installed correctly. Windows should detect device even without drivers and you will hear the connected sound, just like you pluged your USB in.
Nem1x said:
Have you tried the method I showed above? Maybe your drivers are not installed correctly. Windows should detect device even without drivers and you will hear the connected sound, just like you pluged your USB in.
Click to expand...
Click to collapse
I am the guy that contacted you on telegram a while back. I have indeed tried your method but no luck in there.
zisinikos said:
I am the guy that contacted you on telegram a while back. I have indeed tried your method but no luck in there.
Click to expand...
Click to collapse
Ohh.. yeah. I don't really look who replied to thread.