[Q] i747m (Bell) - Requesting Assistance - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Alright, Apologies if this thread has been started in the wrong area - Just to get that off my chest lol.
I've recently made a serious mistake - noob mistake -
I had flashed the (DMG2) (I747 (AT&T)) from http://forum.xda-developers.com/showthread.php?t=2321310
Now, my phone is dead as a doorknob - Almost.
I thank you in advance for reading through this and ANY help is greatly appreciated
I've recently discovered that the device is recognized as:
Qualcomm HS-USB QDLoader 9008 (COM2;Can be changed)
Model: QHSUSB_DLOAD
I've been lurking the threads and found a very promising lead into wat may be a solution to my issue without JTAG'ing the device - Since the JTAG RIFF box, after research, my not support my model, the only option would be to replace the Mobo, though I coul be wrong on that.
I'm opt'ing to not send the device off to get JTAG'ed since I'm determined to find a solution...for now
OS - Windows 8
Firmware (Prior to Brick) - I747MVLDMF1
ROM: SlimRom - build.1.8-WEEKLY-1260 (Ver. 4.3)
My work so far:
- Phone will not boot into DL Mode/Recovery mode, red light (consistant) when plugged in without the battery; drops connection (w/out battery) after minute or so - with battery, the device stays connected through COM2
- USB Jig found not to work with this particular brick
- Odin does not detect (though it's using COM2) the device - I suspect this to be something to do with the DLOAD device recognition.
- Heimdall does not detect the device
- EFS: Recognizes device, cannot connect to it...
- 2nas does not detect the device
- Unified Root Tools is unable to connect to the device
- ADB (SDK Manager) - Nothing found relevant, so far - ADB doesn't connect.
- Roadkil SD Image Creater (SD boot Option) - Ironically, no i747m (Bell) Dumps located in this fourm
- UART drivers installed
- USBXpress: Still searching for potential leads
- QPST: The only viable option would be "Use Emerg. Host D/L" option under Multi-Image section in the Software Download Client - And after reading this http://www.anyclub.org/2012/05/qpst-emergency-download-support.html it burst that little bubble of mine.
I'm still searching http://www.anyclub.org/ but I wanted to see if anyone else might have located a ix for the issue - I was thingink on doing the Unbrickable mod from http://forum.xda-developers.com/showthread.php?t=1206216 but I'm kinda leary as to if that's such a good idea with my phone being in the state it's in - My question is whether or not the mod will create the opposite effect, the "non-unbrickable device"
The other idea, which I'm not to keen on either, is the possibility of forcing the phone to boot by soldering the boot leads on the Mobo -Using the MSM8960 BGA pin map showing the BOOT_CONFIG_x pads.- Source: http://forum.xda-developers.com/showthread.php?p=30781353
Again, Thank you for reading through this - Any help is GREATLY appreciated I've been up all night the past few nights trying to implement a fix for it - at this point I'm game for any testing software that may be out there to resurrect this dead body.

Related

Z1C won't start - advice please

I've got myself into quite a muddle with my rooted Z1 Compact. I was prompted to update the firmware to 14.4.A.0.157, which I did over the air. Since the update, the device had been freezing, restarting and generally being unwell. What I didn't realise, based on a piece I read somewhere, was that this was likely or probable if the phone had been rooted. My memory is a bit sketchy on all the steps I took - but briefly - it suggested checking the status of the phone, from which I followed instructions using flashtool to flash a preceding firmware (xxxx.108), which it appeared to do successfully but now the phone does not boot at all. I'm now lost what to do next and I couldn't say if I've soft or hard bricked the phone. Another article (at android.gs / unbrick-sony-xperia-z1 ) says that if it's hard bricked then I need to flash the full firmware (not just kernel only). I've downloaded and installed Emma from Sony's site. I can get the software to recognise the phone but it says it is locked and I am in the process of downloading the Android SDK to [see if I can] continue this process.
I should have stopped and asked for advice before I did any of this. Now finally I am pausing to seek advice. Can anyone point me in the right direction?
The phone will charge when plugged in, at least it is showing a green LED to imply fully charged.
Brief update: I couldn't enable USB debugging on device, as device doesn't start up. I enter fastboot mode when connecting the device (Windows) and I run "fastboot devices" in the platform-tools folder without an error however when I enter the command with my unlock key, I just get "waiting for device" (several minutes). I am assuming that this might be because I couldn't enable USB debugging on the device? Any suggestions on where to go from here?
I might as well log the antics of my adventurous mind. Given that I hit a dead end, I continued on the original path and used FlashTool to flash 14.2.A.1.114_Customized firmware (why this - because it was the only full firmware that I found). Anyway, thankfully, I now have a working device running that firmware with Android 4.3. I'll try and proceed to get back up to date.
devo1d said:
(why this - because it was the only full firmware that I found).
Click to expand...
Click to collapse
Not sure how when this thread is stickied at the top of the General Section. Z1 Compact Resource Thread -|-Rooting-BL Unlocking-Firmware & More..
Oh my goodness......... It is pantomime season after all
Magic. I confess to being another dizzy head when things don't go right and reading from a multiple sources and getting a bit overwhelmed & lost. Anyway, found the way out and thank you for the pointer to the sticky right-in-front-of-the-eyes info. Bookmarked.

LG F460 Cat 6 (H A R D B R I C K E D) Help!!!

Greetings Everyone,
I need help regarding my hardbricked LG F460L. As of right now it is in DEADBOOT (The screen won't turn on even if I plug it in) So, I can't boot into RECOVERY, DOWNLOAD MODE, or FASTBOOT. However, when I connect my phone to my Win 7 64-bit PC, it is detected as QHSUSB_BULK.
This nightmare happened because I flashed a D855 modem.iso to my F460L, I accidentally flashed the incorrect modem.iso in TWRP and i've been screwed since then.
After reading and scouring through every LG F460L/K/S Cat 6 Unbricking threads in XDA, I have found three methods:
https://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853
- I have installed the QUALCOMM driver, my phone is now detected as Qualcomm QDLoader 9008. This is in accordance to the BoardDiag method. Using willcracker's boarddiag program, I connected my phone to my pc and clicked start HOWEVER I always get the device not found in dload trying flash programmer error after 2 minutes. The AP Chipset I chose is B2 since there is no MSM8084 or APQ8084 chipset for the Cat 6 in the program
If anyone has a working BoardDiag program that supports the Cat 6, please do post a link in the comments or PM me if you so prefer.
= ~FAILED~
https://forum.xda-developers.com/lg-g3/general/unbrick-debrick-f460-boot-security-t3352382
- I tried to boot through an external Micro SD card by flashing a "debrick.img" to the SD card. There were 5 debrick images listed in the guide, however, all of its download links are down (220, 200, 180, 160, and 140 are all down)
Thanks to the efforts of other users, I was able to download a debrick image file for the F460. Upon mounting the flashed Micro SD card, my screen turns on and I can enter download mode BUT it was of no use since I was stuck in an eternal "Secure Booting Error!" bootloop.
If anyone has a working link to the 5 debrick images for the F460, please share.
= ~FAILED~
https://forum.xda-developers.com/verizon-lg-g3/general/fix-unbrick-hard-bricked-lg-g3-vs985-t3467067
-Finally, there is the Wire Trick (Test Point/Shorting Points) method, this method carries a risk of DAMAGING HARDWARE since you can fry your mobo if you're careless.
Since my phone was already detected as Quallcomm QDLoader 9008, I skipped this method, but beacuse the first method is not working for me, I wanted to get back to this.
I was actually desperate enough to attempt this, however, upon reading the warnings and disclaimers, I had to think twice about it. The trick was to short a point near/beside the processor and short it to ground. It is relatively simple and easy (For the International versions) but since I have an F460 Cat 6, my board is SIGNIFICANTLY different from the mobos of the International/European versions.. Images and diagrams online, looks different to an F460L mobo. Can't risk frying my phone!
Since there is no information/images/guides regarding how to short an F460 Cat 6, I put out this method for later study.
If anyone can point me where to short these pins or help me find the correct pins, I would appreciate it.
= ~FAILED~
http://cafe.naver.com/develoid/562849
:crying: I am desperate because support for the Cat 6 seems to be very poor, and the Develoid Cat 6 forum in Cafe.Naver is apparently region-locked, only allowing Koreans. I can't seem to register an account since it requires an I-PIN or a Korean phone number.
Please Help Me!!!!!!!!!!!!!!!!!!!!!!
If anyone can provide me with other methods (except paying for overpriced JTAG repairs ) I will really appreciate it!
and Thanks everyone!
If you have a working link to the 5 debrick images for the F460, please share.
Thanks you so much
Boot verification fail!cause : mismatch_sig_len please help me asap pleaseee

AC8227L - Mediatek components + unknown MCU - Bricked device help from PCB pictures

Hi all,
So I managed to successfully root and dump various bits of firmware etc over the past few weeks and generally had no issues(apart from the LED front panel lights not working(did at first), which is the main reason I was trying to rectify) - I have flashed from USB using a .bin also dumped preloader and rom etc via a scatter file using SP Tools after finding a rom entitled 8277L in the filenames, this worked perfectly(but still without the LEDS's) - Link to bought device(a cheap chinese one) - https://www.ebay.co.uk/itm/Single-On...53.m2749.l2649
Main issue: Now I have bricked it - I selected the format all part in SP-Tools thinking it would allow me to flash from fresh to stop the stock and TWRP recovery from timing out(I successfully ported TWRP over, but after about 30-40 seconds it was rebooting the device, bizarre!) - When the head unit is powered on it turns on the display but that is all, just a light black screen. I've tried recovering again via USB and SP tools but I think I'm almost out of luck. SP Tools doesn't read from the device or detect it, and yes I have the correct drivers installed under Windows. No screen swiped or button presses help in getting into any bootloader or update mode.
I am really hoping, anyone could help identify the UART pins on the board - yes I've now taken it all apart - in the hope I can flash a bootloader image which I guess is what is now wrong and has been erased??
I've really been digging into this and researching on Russian websites and getting lot's of interesting information including from XDA thankfully, but not this issue. I have included some pretty much hi res images, some are dark but I have redone some, everything is readable but I've googled and googled for model/part/serial numbers etc and have had no results that helped to indentify where I could potentially find the UART connection.
If anyone has the same unit or similar it would be great to share the knowledge so perhaps we can help bring the info together and help other debrick this device if there are any!
Many thanks, for anyone who cares take a look!
https://imgur.com/a/8Qz8ESP - all high res images
AC8227L - Mediatek components + unknown MCU - Bricked device help from PCB pictures
info
hi,
i have the same problem , i don't know how to fix it
info
please check this
4pda.ru/forum/index.php?showtopic=930058&st=160#entry81152859
forteon said:
please check this
4pda.ru/forum/index.php?showtopic=930058&st=160#entry81152859
Click to expand...
Click to collapse
Thank you, will try this out.

Early debug output

Is it possible to get some kind of UART or Serial port over USB at the start of the phone?
I want to dig into a issue where a ROM - under a specific circumstances - hard bricks my device (that means, no system, no recovery). However, it happens during a early boot stage. I only have a chance of finding the culprit when I have access to the (kernel) log. If Qualcomm devices have even more detailed logs (before the kernel is started?) I would like to read those to.
Mind that saving the log and reading it out doesn't work here... at the point I need to access it my device is already hard-bricked.
I read somewhere that QCSC devices have a USB UART / Serial mode, but I can't find any concrete information about it.
Would love to hear your thoughts about this.

ZenFone 2 Z00A(d) ZE551ML - can't boot - black/white screen, no bootloader, want Windows (KVM kernel/OS)

I recently bought Asus Zenfone, because here in Ukraine is war, so I want small device with Windows (electricity often is off here because rockets fall on our electrric infrastructure etc).
So I've bought Asus Zenfone 2 used (it costed 16,25$). It came without accumulator, and 1/3 screen working. So I went to radio-market to buy new battery, it costed + ~10.25$ + 2,5$ to install battery. Then I've bought new touchscreen for it for ~22,5$, plus payed ~6,25$ to install it. Then around 7,5$ to restore battery connectors (on device and accumulator). So finally it worked, and wanted to see how to install Windows on Zenfone. Sure, if I had possibility to buy anywhere Zenfone better, new, not used, - I'ld do it, but it is not that easily available, just like any other Intel smartphone.
So, I started reading - how to make my device rooted. I don't understand how to get root. I found on wikipedia, that rooting is different from unlocking bootloader, and realized - yes. I need to unlock bootloader, and to boot from external flash-disk and install windows, or at least - new kernel with KVM support. I used pn my Android (non intel) Limbo x86 emulator, it can run some old windows 98 etc, maybe even xp, never win 2000, and if it runs win-7 or win-8 - it is so terribly slow. So I decided to buy Asus Zenfone. As in KVM mode I can send commands to CPU directly, and hope this Windows works much faster than in emulator. I hope just at least to run Windows XP on it, I need to code some C# code, so that Andorid phone is not only for mp3-playing, internet on the go and make calls, but to learn, study and to work. I don't know why Microsot, Intel and other companies don't like Intel CPUs in mobiles. They could do it if they wanted. I like WIndows because most programs are for Windows. And I want desktop x86 windows also on every mobile, intead of all Androids.
Anyway, What I tried to with my Zenfone. I found one amazing experience - that our hero and inspirer (ley God blesses him, maybe he will work in Intel/AMD/Asus/Microsoft etc to make more newer KVM kernels for future x86 phones with windows) - so Ycavan made KVM for Asus Zenfone 2. Great, I've read his thread - https://forum.xda-developers.com/t/...0-with-kvm-bridge-compiled-need-help.3145055/ - completely, with pen and paper writing down important information, downloaded all the files, and decided to start flashing.
I copied them to root of my Zenfone, unpacked tars and converted them into ZIPs. I also unpacked .img files to root of phone (I mean its folder which is visible if I connect it thorught USB, I know it is not "/" root of file system of Andoird, but anyway it is visible even inside CWM... sorry, was visible)...
So, I made some mistakes. I downloaded the kernel, tried to flash it using commands like :
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150710.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150714.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150717.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
fastboot flash boot boot_2.19_kvm_bridge.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
but non of them produced bootable Zenfone. So I had to revert to previous bootloader using the CWM tool.
In fact I liked this CWM most. I found this thread - https://forum.xda-developers.com/t/...root-ze500-ze550-ze551-temporary-cwm.3114063/
or similar here on forum, and it worked amazingly. I attached Zen-phone to USB, turned it off, then on while pressing, keeping pressed volume-up key, and after Asus logo appeared and some "zzz" vibration, again it blinked and I saw bootloader with Android robot, and possibility to scroll through menu using volume up-down, to choose normal boot, or reboot/power off, or to run restore etc.
For some reason, Restore there not worked. So anyway, I understood that I can use tool like ADB (Android debug bridge) and fastboot to copy new firmwares/kernels/bootloaders etc to it, so I guessed I can do it myself, and was ready for risks... And this what bad can happen - it happened.
So, I runned in CWM - file cai_dat_CWM.bat - which asked to type ACCEPT and then T4, and phone started to go into amazing mode, some "clouds" started appearing on phone, and it loaded into special secret menu, from which I could select what to do next. To me it looked like default boot manager which I wanted to see like in Dos/Windows machines - so I can choose to run into safe mode windows, or set some settings before booting, or even use "reanimator dvd" etc to load Windows and other tools to do partitioning, passwrods recovery etc. So it looked like on desktops, and very nice. I went inside the menu, and found good option to make backup. I did it all. Then in same CWM tool (I think it is called SuperSU for Android), I finally choose to restore bootloader/kernel/boot (custom recovery), and this saved my from bricking the first time after I followed the manual from Ycavan. Well, I know I can read a lot more threads how to do this and that, but there is always risk that something wrong can happen. So I tried to read as much as I could, and follow manuals as precisely as I could understand. But my phone is kind of "bricked".
Now it shows some scfreen like TV which can't catch any tv program. So it is some random colors - see attached picture. It is good that it shows at least this. But in worse situation - it doesn't show anything. So let me tell how I achieved this, and if you can tell me how to avoid this mistake and to recover it. I hope to get help from anyone here who installed KVM kernel(s) and acheieved running Windows on their zenfone 2 (or maybe anyone who has XPerience with other x86 phones may help, or if it is general issue how to unbrick - then also non x86 users please help).
So, CWM made backup, I became more non-scared to make more experiments with firmware. But main problem is that I don't know which firmware to use. I ideally suggested that when I change kernel to KVM-supported from Ycavan - that it will work with my Andorid 5.0 (it was installed when I bought it). So, but unfortunately, after installing any of KVM kernels of Ycavan - I was unable to understand which OS to install, which version. So even I tried to try to flash whole 1GB+ image (I have downloaded UL-Z00A-WW-2.20.40.59-user.zip from official asus.com - https://www.asus.com/ua-ua/supportonly/asus zenfone 2 (ze551ml)/helpdesk_bios/ - but. I was unable to upload it to zenfone (flash it), as it said it is older than installed version.
Anyway, now it doesn't matter as I cannot run into ANdroid at all. Worse - I cannot even get Bootloader working in Android, as I see after turning phone on - only "white screen" with non-working TV-like image (see attached picture of my Zenfone 2).
So, to make this happen, I did this: I found some information about TWRP. I tried to install as recovery tool. Even though it was flashed into mobile, and I installed it from apk from Google-Play, still, I was unable to run it... So then I found even cooler tool - which was too risky to install. I was good, but Andorid stopped running at all.
This tool is called - preroot601. I runned in it preroot.bat, and then it did something similar to CWM, but several times it restartd the phone _ i have added screenshots of how it looked like on PC / Windows. So after several restarts, it did a lot of changes - Android didn't start after it. Phone always was able to start into recovery mode - into TWRP (I downloaded its .img and flased it as recovery for phone). But in TWRP I think I did something wrong. I made backup of all files (syste,, bootloader, everything). I saw it is cool - to see there terminal, ability so set attributes for files, mount partitions ... even USB -hey, can I run from flash-disk? or from external DVD/Bluray which I have in this mode? I have USB-hub, and can connect to it keyboard, mouse, flash-usb, ssd/hdd - all through Microusb-usb adapter and to usb-hub. So what I wanted to do is to try to see flash-disk, mount it on my android zenfone. And then after restart - I had black screen or this 'non-working analog-TV screen when no program/channel/wave is caught for signal"...
So, I don't even understand what I did, and why this all happened, and why I have to do to restore bootloader at least.
My aim is to have KVM enabled in the kernel. I don't mind if it is old Windows like XP working on this Zenfone, but I like windows to be my main OS on every phone which I may use in future (and hope they all be x86-64 and not ARM). So as I don't have Steamdect now (it has also AMD x86 CPU, like Zenfone), I want to do this, achieve it - having Windows on mobile - Zenfone.
I can carry it in pocket everywhere, so why not people like having desktop Windows x86-64 in each and every mobile? Even Lenovo are collaborating with IBM - then why not make also IBM-Mobile / IBM-smartphone, which will also be as good as PC - to unassemble it, change any part like on desktop, why not do it? I think everyone will enjoy it, and it will boost everything to better hights, levels.
So, please. If anyone here has similar experience of going to same screen like I have (see screenshot), or like that - black screen - indeed my device also may not even show any thing - even no ASUS logo, no bootloader (even if I press Volume-UP after powering and after flash it usually showed bootloader with robot - no... not now)...
So I don't see anything on screen of Android Zenfone now. no text, no bootloader, no recovery even - no TWRP menu. I think I am ready to format whole zenfone, and install there maybe some partition manager (like you know there is Partition magic on PCs, when I can split HDD/SSD nto two parts, one for Windows, and say other for Unix - Ubuntu or Android x 86 - all on same physical drive)... So I want some re-partitioning for intern SD memory, and be able to install there some ISOs, say with DOS, Win3.11, win 95, 98, 2000, xp, 7, 8,1 and maybe even 10. But guess last will be slow. I think Windows XP would be ideal OS for my Zenfone, if it can run fast. Win 7/8 maybe will be slow. But for some sceintific aims - like I just write some algorythm in Visual studio, and can do it even in WinXP, so why don't do it on my Zenfone? I don't like many Andorids, as they are not for work much - they are used by many people to play games, watch videos on phones, surf social networks, but not for real work. Real work is usually on WIndows, and no laptop can replace "Windows x86 in pocket" (on mobile). And I wonder why Microsoft develops "Windows for ARM" instead of investing millions into efforts like which Ycavan did - to make Windows run in KVM mode fast on x86 smartphones.
Ok, So, any ideas? What should I do now? I need some special tool to fix my phone first. Fix its loader. I think I need to bypass fastboot.exe restriction, which shows "waiting for device". Command in cmd like this: ADB.exe devices -L --- shows device from time to time - it shows:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
So, I cannot even flash some recovery device in this way. In devices manager I see "ADB interface" in "USB devices" category in devices treeview. And sometimes Moorefield appears, but with exclaimation mark - I have no idea how to make it disappear. I found here some info that I can install tool - xFSTK_Downloader_v1.7.0.zip - I downloaded it, installe,d but it doesn't run (I have win10 x64bit). hm... And driver required - iSOC_USB_Driver_Setup_v1.2.0.zip - I installed - but nothing.
So, what to do? How to make bootloader appear again? And how to write there prob=per bootloader with KVM kernel, and which firmware to flash so I can use KVM fast there with fast Windows...? Is it possible at all to make it run WIndows natively on Zenfone? or it will always be only in virtual machine inside some ArchLinux or in Limbo x86 on Android?
I read that Ycavan used this ArchLinux, but I don't understand why. Is he installing it over Android? Then also which version he uses? I need to know each and every version whcih he uses to make everything works. I 'ld require all the firmwares which he uses to make it work also - to make some Windows iso run on my Zenfone 2.
Did anyone achieved this successfully, except for Ycavan - to run Windows on Zenfone? Or except for him noone was able to install KVM kernel, and it was similar to mine situation? And maybe this is the reason why manufacturers of phons don't like x86 phones? I don't know. Any ideas?
See screenshots. What to do in this state?
IF anyone can please upload to somewhere whole pack of files ("WIndows on Zenfone starter kit") to make anyone able to just follow instaructions which will work in all cases to install WIndows there like Ycavan has - it would be great. There is lack of more detailed information - which .img files, .zips, firmwares etc, which OSes are supported by Ycavan's KVM kernels?
I have no idea. if anyone passed this path, and achieved Windows on Zenfone, please share your experiences, Ireally need it. Here in Ukraine when electricity disappears almost daily, we need devices like x86 phones almost for everyone. And mo matter if Windows is a bit old. KVM mode I guess must be much faster, almost native speed, so (like on tablet PCs), so please help...
Thank you all in advance, whoever will answer me.
indubhushan said:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
Click to expand...
Click to collapse
wrong mode. adb is only working in
- normal/boot mode
- recovery mode
fastboot is only working in
- bootloader mode
- fastboot mode
You can see 0123456789ABCDEF device in adb devices, therefore you are either in TWRP or in Android (Win?)
type adb shell and check the prompt is either $ (shell) or # (root shell)
in root shell you can flash partitions from cmd line. you can also reboot into bootloader/fastboot mode from cmd line.
Code:
adb reboot bootloader
I had success in restoring my bootloader (logo with android robot) - I intalled xFSTK, so somehow I had success to make it run, and I added threee files (1, 2, and 4th) and tried to flash it. Phone was visible as Moorefield. Then I tried to use Asus flash tool to flash big RAW image, but for some reason I don't know why - I had even whole day left it to flash, it didn't do the task - Android stopped booting - no logo showing at all - have to use xFSTK to recover. Maybe I use wrong RAW image (from official site it is .zip, so have no idea where to get those raw files).
When try to flash using flashboot - I get error: - flash cmd error.
As for devices list. My device rarely appear there. It may appear for some seconds, and then xfstk can have success to flash it, and maybe even make it runnable into Android robot scren (bootloader).
I am thinking that I need to install maybe ArchLinux, which Ycavan is using, but have no idea where to get RAW file for it, and how to flash it. Maybe some problem with my USB port on old laptop, or maybe even with USB cable (though have few good almost new cables, even new 4Amperes one). So maybe even problem in port of Zenfone itself (to change it). No idea. Because even when I tried to flash it (that huge 1GB file), phone disconnected, or showed "ready for commands", instead of showing process of ownloading RAW image/Android into phone's memory.
Flashboot/adb almost unusable. Well, I'll try, maybe it'll work.
My hope is try to go into CWM, run from it into "secret menu" on phone, and from it - to access internal memory of phone, and restore phone from backup. But when I tried to load into it once - it hanged on "clouds". I don't know...
And I don't think I'm ready now to format internal memory of phone or to repartition. At least I don't have backup on some external card (sd-card) etc.
as for adb. maybe it can't see my device, even if it is "recovery mode" (when see in devices manager in Windows - Moorefield). Now I'm stuck on xFSTK and can't go anywhere further like adding TWRP into phone, or foing into backup/restore menu on phone, and of course there is no Android. Even when I see Android robot (boot menu) - I feel happy, that at least phone shows anything, so at least bootloader workds. Maybe difference is in drivers - when I have Moorefield driver, then maybe it contradicts with Zenfone driver, and I have to reinstall them? Or use other OS? I have dual-boot (two Windowses on my laptop), so maybe I need to use one Windows - to work with Moorefield (xfstk) - when phone is in "worst" situation when no logo shows / no bootloader. And the other Windows I have to run on laptop - with Zenfone driver installed (I think it shows something like Asus device in device manager). But they seem to use contradicting drivers, I am not sure. And maybe it's some problem with my usb ports, but hope no. They seem to be ok... Maybe I'll have to go some day to give phone for diagnostics to repairing center again ;-(

Categories

Resources