Related
hi all...
...I hope that you can help. Some years ago, I have flashed my polaris from o2. i then got myself an iphone and some new computers (using vista now instead of xp), so that I do not have any of the old files that I used back then to flash the phone. my father was using the xda for quite a while now. however, suddenly the device is not working any more: if you turn it on, the boot screen will appear, but then it is stuck and nothing is happening (even no rom info in the lower right corner). also a hard reset doesn't help to overcome this problem.
what I am trying now is to flash it, because I guess (and hope) that this might help. But, to be honest, I completely forgot how this works. I downloaded an original rom from this website today, but I cannot flash it to the device (stuck at 0%, getting an communication problem error). If I turn on the phone with camera button pressed down, the tricolor-screen appears reading POLA200, SPL-3.13.0000, CPLD-2. what am I doing wrong? your help is greatly appreciated.
Try flashing the rom from the tricolour-screen just make sure at the bottom of the tricolour-screen it say's usb not serial.
You will only be able to flash official roms as you don't have a stock spl not hard-spl.
thanks. I tried this one from this forum: RUU_Polaris_o2_GER_1.24.207.2_withSplash_noRadio_schaggo_[fixed]
but it did not work.
however, I now downloaded the rom from the original o2-site and it is at the moment in the process of flashing it - let's cross fingers.
damn, it did not work. I mean, the flashing succeeded, but the problem still persists: if I start the device, the start-screen appears, but that's it - nothing happens afterwards, and after some seconds, the device turns itself off again.
what could that be?
Could be the battery if the device turns itself off,try booting with the charger or usb still in.Or flash hard spl and try a different rom.
hi all friends if you are stuck on 0% and u cant install spl then do this ,,,
You can try this:
1. Stop ActiveSync
2. Open Task Manager (press Ctrl + Alt + Delete) on your PC and
stop these two processes rapimgr.exe and wcescomm.exe
3. Plug in your device via USB. Your computer should be asking install a driver. Install and continue.
4. Now Run mtty and choose USB in 'PORT'
4. type "set 16 0" without the quotes to tell bootloader to boot the OS after reset.
5. type "task 8" to get your device formatted.
6. Now unplug your device and manually reset it.
i hope you will be happy after .. thanks
Hi to all,
Been here for a while and every time i log here in XDA (O3D forum), I always see new people bricking their newly bought O3D (stuck on LG Screen..., rebooting only to cwm recovery.., etc..etc..). If you got into a situation just do the search thing before posting a new topic which is already been posted because our forum (O3D Community) is still small so searching wouldn’t be a problem and there’s no need for a dig yet when reading all the topics posted here. All i can say is for all the people who just bought O3D always remember this "If it aint broke then don’t fix it" you will just end up voiding your warranty,
if there’s an update don’t try to push it on your warranted device, try to check first if the update is applicable to your device (country or region) because we all know that LG only released O3D in Europe so if you are in that place and check that your devices have an update, go grab it, but when it fails always call LG Europe (because you have a warranted device and they will assist you) and explain to them that you are experiencing difficulties in updating your unit, and for everyone else who is not in Europe (like me were my unit is not warranted)be very careful if you want to forcefully push that update to your unit (v10b, v10d or even cwm 4.0.0.9) because me i already bricked my device 3 times were i end up booting only in LG and nothing follows, the other is booting only to CWM again and again, and the last one is after unbricking the device and setting everything then when rebooting the unit it will end up stuck at the LG original android recovery system <3e>menu.
Note: Do this procedure at your own risk, i repeat "AT YOUR OWN RISK", its your unit so its your responsibility, you've been warned, i myself grab that risk and now I’m happy with my unbricked O3D (v10d July, 8, 2011 with fully working CWM 4.0.0.9), all the tools we need are here at XDA so there will be no problem getting those tools.
Ok enough about nonsense(hahaha), lets go down to business. As what the Title says, here we go.
Requirements:
This method will only work in WINDOWS XP MACHINE, i have tried it in Vista and Windows 7 but it will just hung.
I assume that all the necessary drivers are already installed from your machine because without them you can’t bricked your O3D. If by any means you don’t have it, just grab it from http://www.lg.com/uk/support/mc-support/mobile-phone-support.jsp and click the download link save it then run it after installing, it will run automatically, then do the following:
1. Go to Customer Support ---> Application, Manual & USB Driver Download.
2. Enter you IMEI then click the Search button.
3. After Searching, it will list two files form the File List, double click any of those file (me, i choose the file with divX converter)
4. After downloading, it will extract its content to C:\LGP920
5. Go to this directory C:\LGP920\USB_Driver, and double click LGUnitedMobileDriver_S4981MAN33AP22_ML_WHQL_Ver_3.3
6. Let it finish then if it ask to restart your pc, do it.
7. Optionally you can install the LGPCSuite, it can be found in c:\LGP920\LGPCSuite\, just double click the LG_PCSuiteIV_Setup.exe and follow the instruction.
Now that we have installed the drivers for O3D, we can move on to the next instruction.
Make sure to follow the instruction carefully and proceed if you know what your doing.
I have edited nikhil4186 and victortangocharlie post (Original thread: http://forum.xda-developers.com/showthread.php?t=1060121)
1. Detach all other peripherals from your PC. Exit all running applications on your PC especially other PC suites if any. Also exit running programs from the notification bar on the desktop. (Also uninstall Nokia or other phone drivers & microsoft visual ++ runtime environments - not an essential step.)
2. [IMPORTANT] Disable 'LGE Virtual Modem' in PC's Device Manager. (In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.).
3. Remove the Micro SD from your O3D.
4. Download the KDZ rom v10b_00 posted by Fab985 : http://forum.xda-developers.com/showthread.php?t=1155874
(v10d_00 is already available but this method is only tested with the v10b_00 rom, so if you wanna try your luck, its up to you)
5. Download the KDZ updater - http://forum.xda-developers.com/showpost.php?p=8651505&postcount=1
6. Extract it, then run the msxml.msi
7. Now the next step will be crucial because you need a full battery (for safety of course if you don’t want your unit to die while in the middle of the unbricking process) and you will put your unit in emergency mode (by pressing the power button and the volume up button), here’s how you will do it.
Case A. (This is my Case)
If your O3D can boot but only in CWM, charge it (me, i charge mine for 3hours in cwm), you wont see a charging status but you will feel your battery getting warmer.
Case B. (Never happen to me)
If your unit is just stuck at LG logo, try to charge it too and see if your battery is getting warmer, if not, better find another way to charge your battery or a friend who has O3D and borrow the battery.
Once everything is ok proceed to step 8.
8. Open Device Manager and under Modems check if you really disable the LGE Virtual Modem, if it is already disabled don’t close Device Manager, we will need it on the next step. Make sure you can see your Device Manager window and your modems devices are expanded (were you can see the disabled LGE Virtual Modem)
(THIS IS THE TRICKY PART AND YOUR O3D WILL JUST STAY BLACK SCREEN)
9. Plug your USB cable to your pc and then plug it to your phone then enter Emergency MODE (power button plus volume up button) This step is very tricky (me, i tried it several times before it detect my O3D as LG USB modem).
First when your pc detects your O3D, it will detect as OMAP4 then it will look for its drivers, just cancel it, then another device will be detected, if you successfully entered Emergency mode, your O3D will be detected as LG USB Modem, this modem should stay, if it disappear then you failed to enter the emergency mode correctly, try it again before continuing to the next step.
10. Run KDZ_FW_UPD.exe from the extracted folder.
11. Put the following settings:
Type : 3GQCT PhoneMode : DIAG
12. Under the KDZ File, choose the KDZ file you've downloaded from Fab985 post (v10b_00)
13. Press the Launch software update. (this part will take time because it will extract the kdz file into cab file, it took me 15 to 20 mins before it proceed to the updating process)
14. Once updating has started you will encounter this message:
CDMA: wPrama = 2004, IParam = 1
Model Dll Msg Not Found(2004, 1)
This message will come out from 1 to 100 counts:
CDMA: wPrama = 2004, IParam = 1
Model Dll Msg Not Found(2004, 1)
CDMA: wPrama = 2004, IParam = 2
Model Dll Msg Not Found(2004, 2)
And so on till:
CDMA: wPrama = 2004, IParam = 100
Model Dll Msg Not Found(2004, 100)
(Note: This message is case to case because i experienced diff counts then the LG USB MODEM disappear from the device manager list, first attempt count 64 then LG USB Modem disappear from the list, the kdz flasher stops from count 64, waited up to 10 minutes but nothing happens so tried it again from the enter emergency mode step, second attempt count 76 LG USB modem disappear but after a while kdz flasher still continues up to 100 counts then it stop there, waited for 5 minutes nothing happens so decided to remove my device and turn it on and viola it booted to LG original Android system recovery <3e>)
15. After you reach the 100 counts, the process is done, the LG USB modem from the Device manager will be gone, but don’t remove yet your phone to reboot it, try to wait up to 5 minutes before disconnecting your phone.
16. Turn on your O3D, if it boots in LG original android recovery, just choose the wipe data/factory reset, then reboot system now. Then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not proceed to step 17.
17. If it comes back again to recovery after booting then wipe data/factory reset, wipe cache partition then reboot system now.
18. Turn on your O3D, then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not proceed to step 19.
19. If it comes back again to recovery after booting then wipe data/factory reset, wipe cache partition, and lastly wipe nv dynamic partition then reboot system now. (this part resolve my rebooting issue)
20. Turn on your O3D, then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not I guess it’s the end of the line for now.
Sorry for this very long instruction. If it helps you I don’t have a beer fund because I’m not a dev. but a simple hit with thanks will do.....
TIPS NOT RELATED TO UNBRICKING:
Rooting:
Run SuperOneClick as Administrator, before clicking Root, click first the Driver Check and if no problem has been detected, no more settings is required just click the Root button then wait until it says done or finish.
ClockWorkMod:
After rooting, download rom manager from the market, after the install run it and tap Flash ClockworkMod Recovery (4.0.0.9), once successful you may now backup your current rom before you mess again with it, since I installed cwm in my O3D I never use the buttons to boot with it(power button plus volume down button), I always use the menu's with the rom manager to boot into or backup or restore or flash in CWM.
Upgrading:
For safety purposes, if you have a warranted device and then an update pops out, always do a fresh start, what I mean is if you already rooted your device and installed CWM, better removed it first before updating your O3D so when things goes wrong from your update process you can always call LG for it to be fix eliminating the needs to post something like “Help I brick my O3D and I can’t bring it to LG because I installed CWM blah blah blah etc.. etc…”, got the point so be responsible.
For the Mod: Sir if my post will violate something feel free to removed this post. more power XDA!!!!!
Many thanks to the following:
Aremcee
Renegade_Rules
Fab985
ik911
nikhil4186
victortangocharlie
and everyone here at XDA....
thanks for the info but does not work with clockwork installed and update over phone and stuck at firmware updating screen people.. waiting for a solution still
wuper said:
thanks for the info but does not work with clockwork installed and update over phone and stuck at firmware updating screen people.. waiting for a solution still
Click to expand...
Click to collapse
Did you follow the whole step, I know its a long process and it work with me, just follow everything and when you are in step 9 were you need to enter emergency mode,its a tricky step,make sure LG Mobile update is not running completely,open your pc device manager and expand the modems,try to remove the battery then press volume up and power button, put the usb cable then put back the battery,it will vibrate then your xp machine will detect it as omap4 device just cancel it but don't de-press the volume up and power button,then after a while it will vibrate again check if you see LG usb modem in the device manager,once you saw it and it stays,it means you successfully entered emergency mode then that will be the time you will run the kdz flasher and follow the succeeding steps.
Sent from my unbricked LG-P920 using XDA Premium App
bro I tried it with lg mobile modem disabled lg virtual modem disabled both are not disabled both are disabled but none of them make sense. Model Dll Msg Not Found(2001, 0)
is written and lg mobile driver gone but the phone does not reboot both 10d and 10b tried I restarted manually and it opens with fw update screen
I also get a "Get Chip Type error" when kdz reads phone information
Renegade_Rulez, you have the same problem did u try these methods?
wuper said:
I also get a "Get Chip Type error" when kdz reads phone information
Renegade_Rulez, you have the same problem did u try these methods?
Click to expand...
Click to collapse
I have bricked my phone numerous times, and in many imaginative ways. The above instructions are pretty much what I do whenever it gets stuck in some non-functional mode.
I tried this way like 30 times during the last week, I just got back from holiday and I just tried it on a Win XP machine and it's always the same it flashes and it never reboots, V10B/D doesn't matter... After flashing I manually power it on, and only get the Firmware update screen and it hangs there forever... I called LG today waiting for a replacement.
@aremcee
Sir thanks for confirming that this method really works.
@wuper @renegade_rulez
Are you doing it in xp machine, if you run it in Windows 7 the process will just fail. Only disable the LG virtual modem from your pc device manager and completely exit LG PcSuite and LG Mobile update. Make sure your xp machine detects your O3D as LG USB MODEM and not omap4 device, the detected LG usb modem should stay in your device manager under modem and it should be enable then you can now start kdz flasher. Will try to investigate what causing your O3D not to flash using the kdz flasher and if I have time will upload a video on how to properly enter emergency mode.
@all
Thanks for reading this, if you have a question just post it here and will try to answer it back as knowledgeable as I can.
Sent from my unbricked LG-P920 using XDA Premium App
if you can try this and make the phone work that means we are doing sth wrong:
1) install clockwork via rom manager
2) install update via settings telephone software update
3) after installing this update the phone stuck at clockwork recovery and all reboot is turning to this screen
4) flash 10b or 10d through kdz or lg mobile, it will stuck at firmware update screen as picture shown as attached
we try as u said on xp machine several times and device manager opened lg usb modem was there till the process finished after that it get lost and I waited 5 minutes and exit kdz and start manually, nothing..
(the attachment picture is turkish, it is written firmware is updating above and the phone will restart after finishing firmware update below)
PS_U_A_John stated in other topic he can flash a phone that is clockwork installed, that shows clockwork is not the problem, I think clockwork and our installed phone update and after flashed kdz rom are colliding each other and phone could not restart.
wuper said:
if you can try this and make the phone work that means we are doing sth wrong:
1) install clockwork via rom manager
2) install update via settings telephone software update
3) after installing this update the phone stuck at clockwork recovery and all reboot is turning to this screen
4) flash 10b or 10d through kdz or lg mobile, it will stuck at firmware update screen as picture shown as attached
we try as u said on xp machine several times and device manager opened lg usb modem was there till the process finished after that it get lost and I waited 5 minutes and exit kdz and start manually, nothing..
(the attachment picture is turkish, it is written firmware is updating above and the phone will restart after finishing firmware update below)
PS_U_A_John stated in other topic he can flash a phone that is clockwork installed, that shows clockwork is not the problem, I think clockwork and our installed phone update and after flashed kdz rom are colliding each other and phone could not restart.
Click to expand...
Click to collapse
Hi wuper,
Can you try after flashing then turn on your device to recovery by pressing volume down + power button, or remove your battery then put it back while pressing those buttons, will it go to android recovery system <3e>?, if yes try to wipe everything then reboot. let me know. thanks.
Like wuper just told, mine is the same... It's not fixable in that way. Again this morning I tried on my XP pc and it's always the same. Just called LG again they will replace it within 24h we will see
update:
You cannot get into the recovery system, holding power + volume down the phone will power on and off again, releasing power when it boots and keeping volume down pressed gets the Firmware update screen.
same for me cannot enter recovery
Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.
Zirowe said:
Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.
Click to expand...
Click to collapse
Hi Zirowe,
Hmm thats strange, you and dnardz have the same problem, wiping the nv dynamic partition solved my rebooting issues and didnt experience this battery not charging problem, try to root your phone and install clockwork recovery 4.0.0.9 then reboot to cwm and full wipe your O3D including the battery stats, then charge your phone again and see if it is charging(maybe two hours), if it still doesn't work, download the v101d cmw rom by PUAJohn and restore it. Let me know
Zirowe said:
Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.
Click to expand...
Click to collapse
try deleting batterystats.bin then rebooting.
Thank you, I will try it.
Will try it too..thanks Johnance17.
hefonthefjords said:
try deleting batterystats.bin then rebooting.
Click to expand...
Click to collapse
I've tried, but no luck, unfortunately, everything is the same..
hi,
It's strange what happens to you.
Have you tried this?
-Turn device off
-Take out batery
-Wait 5 min
-Re-insert battery
-do a hard-reset
-boot up device completly
-Turn device off
-plug-in charger (NOT USB-PC)
-Wait 1 hour
sorry I do not see much solution
It didn't work on mine also...restoring 10d and erasing battery stats..
Hello, I'm about to giving up,
Something happened to the phone and now it won't boot, it barely show the "ANDROID" logo when it restart itself. I can enter to the recovery menu, it doesn't have clockwork recovery nor twrp, just the basic recovery. So far I tried:
wipe data/factory - didn't work.
wipe cache partition - didn't work
apply update from adb: Adb just work with sideload and that's it, for everything else it shows closed. I tried sending the rom with sideload and it fails every time:
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
So I took my sdcard and copied the room there, so I tried
apply update from sdcard, it starts and in no time it says:
Installation aborted (APPLY_EXT).
I'm very frustrated right now, nothing works, it seems that the manufacturer did great effort on being the only one who can recover this phone, who appears to be from China, the MTK6582.
Fastboot? it doesn't show the device, it would be my last hope but no, since there is no adb, I cannot call fastboot, and the apply update from adb only work with sideload (yeah, f**k me).
The best course of action would be to throw it to the trash?
Thanks!
Hey, I'm in a similar position to you. However, I went about it with a slightly different route. The chip used in this phone is the MediaTek 6582 (I think?). I downloaded some tools from a thread on here that includes the 320 rom and the necessary software for flashing. I've flashed MediaTek devices before, the Huawei Ascend G610 and G700, both successfully. This one is giving me headaches, the damn device keeps disconnecting. HOWEVER, if you're lucky and you don't have the same problem with disconnecting hardware, you should be able to flash a new rom via the software. It'll take a while though. Also, I don't know what'll happen to your IMEI afterwards, so that's another possible headache (both the G610 and the G700 lost their IMEI info, but I'd taken steps to back them up beforehand so I could just restore them; here, there's no option to backup).
Here's the thread: http://forum.xda-developers.com/android/general/htc-mtk-cpu-flash-files-flashtool-t3114271
Let me know if you need help. I'm screwed in that the damn phone keeps disconnecting. Similar to you, no fastboot either. Plus, no RUU for this HTC. Hell, the internet barely knows this flipping phone.
Cheers, and good luck.
blitz9826
0Camus0 said:
Hello, I'm about to giving up,
Something happened to the phone and now it won't boot, it barely show the "ANDROID" logo when it restart itself. I can enter to the recovery menu, it doesn't have clockwork recovery nor twrp, just the basic recovery. So far I tried:
wipe data/factory - didn't work.
wipe cache partition - didn't work
apply update from adb: Adb just work with sideload and that's it, for everything else it shows closed. I tried sending the rom with sideload and it fails every time:
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
So I took my sdcard and copied the room there, so I tried
apply update from sdcard, it starts and in no time it says:
Installation aborted (APPLY_EXT).
I'm very frustrated right now, nothing works, it seems that the manufacturer did great effort on being the only one who can recover this phone, who appears to be from China, the MTK6582.
Fastboot? it doesn't show the device, it would be my last hope but no, since there is no adb, I cannot call fastboot, and the apply update from adb only work with sideload (yeah, f**k me).
The best course of action would be to throw it to the trash?
Thanks!
Click to expand...
Click to collapse
Ditto!!!
Hey guys I am having the exact same issue, luckily for me it is my Mrs who done her phone in and not mine . She has the HTC Desire 320, I believe she tried to root it on her own without even asking for advice, I think she used the app Kingo Root, she said she went to remove the root but when she uninstalled the app it didn't remove it. (LOL I told her well perhaps that's because there will be some way of removing it, aside from just uninstalling the app), anyway she proceeded not to care and carried on using her phone as normal for maybe a week or two at most, then about midnight one night, came down and said to me,
"my phone had an update and on restarting I just get a dead android, if you press the power button you get some options so I clicked erase"
Click to expand...
Click to collapse
I was like nice so basically you F***ed it!!!!, and for about 2 weeks now I have been endlessly reading post after post, forum after forum, trying rom after rom, RUU, all kinds of things.
Here is the situation, the phone will boot as far as the HTC logo, it will get stuck in a short loop and reset itself 4/5 times repeating the HTC logo, eventually it will end up at the dead android pic (the android on his back with the red exclaimation mark triangle) with the words 'no command'. From here I can press the power button once to get a list/menu of items (What I assume to be the recovery menu). I can backup data, I can restore the backed up data (both of which do nothing as I guess there is nothing really to back up), There is an option to restore from sd card (which I have tried numerous roms and to no avail have any been successful), I can erase the cache and I can also erase everything and recover, the erase side works fine, I did notice in each of these menu that if you press volume up to activate them and then press the power button once, then the writing dissapears and the android proceeds to have his moving atom type thing in his belly, saying 'erasing..', however even with them completed successfully, it still does not restore.
NOTE!!! If you choose the erase and restore method, once activated with volume up, press the power button to get the spinning atom and erasing... message, when this finishes the phone will reboot, it goes to the htc logo, resets itself, goes to the logo again and then just stays at a black screen (almost like a frozen state, I left it for quite some time and it never changed).
I should also note, which I didn't to begin with, but no matter how long I hold the volume down and power button, there is no such hboot/fast boot menu at all, if you hold the volume down and power button even after it displays the htc logo, the phone just proceeds to endlessly reset and loop through the same process forever.
The only thing I can seem to access with little success, is the ADB CMD prompt through the Android SDK,
Code:
adb devices
will indeed return the device (a set of numbers with the word sideload beside it)
Code:
adb usb
Apart from the odd fluke, this has seemed to fail everytime with either an error about a protocol or an error stating 'closed'
Code:
adb sideload "ROM_FILENAME.ZIP OR .IMG
Occasionally this will throw the protocol error, but generally succeeds and displays the 100% most of the time, however the phone doesn't even try, it just almost instantaniously returns the error message :
Code:
[B][I]Installation Aborted (APPLY_ADB_SIDELOAD)[/I][/B]
NOTE!!! That the android lays on his back with this error, but it only says error below not no command.
I am pretty sure that I already came across a solution very similar to the one you posted above, and I just couldn't get it to recognise the phone, the only way the RUU would work, was by completely removing the battery and plugging in the usb, however without the battery in the phone, it just constantly beeps via usb, so I guess it turns on, then off, then on, then off, forever!!! So the RUU fails everytime, if I leave the battery in and try, the RUU program does nothing whatsoever! So I am at a complete loss with it now.
Cheers
GunnerJnr
Any luck with unbriking the HTC?
Maybe this is the solution, good luck.
Search: How to Unbrick every MTK China Phone ! Preloader / SP Flashtool Fix [HD] on Youtube
Responds please.
http://forum.xda-developers.com/showpost.php?p=64659997&postcount=16
I think that you no tell true because I tried this method with volume keys and nothing. Flash tool still show error. Its impossible to write android without battery. I think really put your phone to rubbish or sell as lcd+digitizer parts I think just we must waiting for new custom rom flashable via stock recovery. 320 is still new model and developers no moke any custom rom. So maybe only HTC service may help, only in HTC Factory peoples know how install android and bootloader on hard bricked device.
So here is what happened, I installed TWRP on my device and completely wiped my phone so I can install bootleggers OS and Gapps on my Pixel 2 Walleye. But I accidentally booted into Boot slot B on twrp and now the only thing the device can boot into is the bootloader mode, recovery and download mode is completely useless, It gives me either operation denied error or Error slot unbootable. The worst part is no computer will recognize my pixel in device manager at all. Mac computer will not detect it either. Ant tips on how to fix this? And again my I have all drivers installed and platform tools are up to date. And devices bootloader is unlocked.
Anything helps!
RomBetaTester said:
So here is what happened, I installed TWRP on my device and completely wiped my phone so I can install bootleggers OS and Gapps on my Pixel 2 Walleye. But I accidentally booted into Boot slot B on twrp and now the only thing the device can boot into is the bootloader mode, recovery and download mode is completely useless, It gives me either operation denied error or Error slot unbootable. The worst part is no computer will recognize my pixel in device manager at all. Mac computer will not detect it either. Ant tips on how to fix this? And again my I have all drivers installed and platform tools are up to date. And devices bootloader is unlocked.
Anything helps!
Click to expand...
Click to collapse
Did you use the same USB cable each time? If yes try different ones, even if it seems to work with other devices. On your PC go to device manager, then view and then hidden devices. Remove anything that has to do with Android. Then try connecting your device. Does an andriod driver show up after you've connected your device?
I have tried 3 different cables. But will try another one
RomBetaTester said:
I have tried 3 different cables. But will try another one
Click to expand...
Click to collapse
Did you go to view, hidden files in device manager and delete all Android drivers? And if you did, did anything show up after connecting your device?
I am having a similar issue after trying to flash the March update. During the script, the System image failed to transfer completely. I tried again using deuce flash all script, and it got a little further (4/5) with the System image but ultimately failed. Things got worse when my computer stopped recognizing the phone. Now I can't even try anything else because there is no communication, similar to OP. I have tried three different computers, three different cables, and have tried deleting Android related drivers in the device manager. No luck, unfortunately. I tried installing USB drivers from Google which also did not help. I welcome any other ideas of what to try next and appreciate any help.
EDIT: I solved the problem by draining the battery completely. In order to drain the battery, I first left the barcode screen on until eventually just the battery image is displayed on-screen when pressing power. Then eventually there will not be enough power to light up the screen at all, but the LED indicator will blink red while holding the power button. Now, I set up my phone such that the power button was held pressed down and left it there until the LED stopped blinking. Now that the power is completely drained, I could successfully get my computer to recognize it! I followed the steps in this post:
https://forum.xda-developers.com/showpost.php?p=78726736&postcount=13
EDIT2: I should also note that the system image didn't flash successfully the first time and I had repeat step 12 which is flashing the update. Luckily it worked the second time!
I had something similar happen. Held down power for about 10 seconds or so until the phone vibrated, then it was recognised by the computer. Then flash stock image
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31
ricky56789 said:
I had something similar happen. Held down power for about 10 seconds or so until the phone vibrated, then it was recognised by the computer. Then flash stock image
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31
Click to expand...
Click to collapse
Man you just saved me =)
Anyone have this problem and solved it? I have an ASUS Zenfone Max Plus M1 (ZB570TL ) - (X018D) and i have tried every Rom you can think of from WW to CTC to CN, also tried dump firmware but nothing will stick and let this device actually fully boot up after flashing it, it just goes to the POWERED BY ANDROID screen and after 30 secs it will reboot itself back to the POWERED BY ANDROID screen and then reboot again and so on..
HOLDING VOL+ and POWER buttons in gets me to the:
- RECOVERY MODE - Just reboots back to Powered by Android screen and back to bootloop, no android guy recovery...
- FASTBOOT - Lets me have Fastboot but i cant flash anything or unlock bootloader as it errors and shows its Locked...
- NORMAL BOOT - Just reboots back to the Powered by Android and then reboots after 30 secs right back there....
There is no RECOVERY MODE that i can Factory Reset, Update.zip, clear cache...
I Flashed with SP Flashtool over 20 Firmwares and all finish with the popup Finished and green checkmark and i watch the flash process all the way without error, unplug the device and turn it on and back to Powered by Android screen and reboots itself after 30 secs... THIS IS CRAZY its like its a GAG Phone or something just messing with me like ( Jokes on you big guy ) ive never seen anything like it, its like the locked bootloader is telling the device not to allow any Firmware to install by tricking the SP Flashtool that yes it did install but didnt allow it to write to the actual system or let you get into recovery mode to factory reset the device or update from sdcard... im just wondering if its a waste of time to bother finding a UFI Box flasher that doesnt need the dongle so i could try flashing the EMMC files if that would help or not... its not a hardware problem or it wouldnt accept flashing or let it power on and enter fastboot mode....
Is this a GAG Device or has anyone actually had this exact problem and has solved it? If i could just get it to boot up into the system i could use Magisk and make a patched-boot.img thats unlocked bootloader and root but theres no ZenUI or anything but the Powered by Android screen....
Any Help would be awesome as i just put new screen, battery, back cover and buttons on this device thinking it would be a good little phone for my daughter... i cant even get any info on the device as theres no box or sticker with IMEI or Serial Number or info on the last working Firmware its all a shot in the dark... Anyways if anyone has the way to get this device working or has backup rom or links to an actual way thats not ASUS as they are just waste of time for 30 mins then you need to take it in to our service center and pay more money and im done putting money in this and could have bought her a new phone for what ive got into this Gag Phone....
Thankz...... Kixx
Judging from the whole situation, you screwed up several things honestly.
The fact it goes stuck on the splash screen and refuses to neither boot on recovery nor the system itself seems to tell 2 things:
the boot.img and recovery.img got screwed up way too much- or literally got flashed for the wrong device, hence the whole rejection to boot;
i assume SP Flashtool, even if got tricked, got a bit of a mess on the internal partitions to be flashed thru. Sounds like a big red flag because ADB can be highly of help (i don't own an X01BD but an X00HD- still an asus device- but i used simple ADB instead of things like QFIL or SP Flashtool to get things going);
On second point, if you wanna try to unlock the bootloader (since fastboot is the only one to be alive and usable- this means your device will be salvageable...atleast by a significant chunk):
you can give it an attempt by checking over my own collection post.
There you will find at the bottom some tiny guide on how to unlock the bootloader-
if you don't have a secondary rooted device, you can always rely using a laptop or pc.
What really matters is that you'll have ADB downloaded on your machine, because it could be of help to progress thru with the stuff.
After unlocked the bootloader, you can slowly approach to flash TWRP for your own device- even tho, it seems nobody so far has done anything for this specific model...
Atleast, on the bright side, unlocking the bootloader will give you the chance to flash manually the partitions via ADB, and maybe the official zendesk site for it can help if unpacking one of the update zips and see the contents inside- or generally pushing the following .zip update file via ADB and wait for the magic to happen.
I'm not sure on how to help with the region tho.
I guess, if you have the box of the device, it could give you a clue if it is a WW (WorldWide), CN (China), JP (Japan), etc. model- afterall, these letters do not lay around without a reason.
Of course, if you flash the wrong region to the wrong regional model:
then the recovery and system partitions get to screw up big time, just like the scenario you're having right now.
As a last thing, the patched boot.img file only gets to work after you got android to work-
otherwise, patching the pre-rooted boot.img file will be of no use since a functioning ROM isn't there at all.
Sadly, i don't own the device nor never had such screw-ups of this kind, but i hope it will help you up.
Ya i can flash the firmware correctly in SP Flashtool it comes back with green checkmark, all the firmware is for the correct device, its just when i had it given to me it had broken screen and bad battery, so i buy new screen, battery, backcover for it and when i booted it up it just sticks on the first screen shown ( Powered by Android ) then after like 30 secs it reboots back to that screen.. I can hold the vol + and power and get the menu to pick RECOVERY or FASTBOOT or REBOOT, recovery just reboots to powered by android screen then reboots after 30 secs, fastboot lets me use adb and fastboot but cant flash it says failed locked, and fastboot oen unlock or any of the commands to do with unlocking or flashing just gets me failed locked, but fastboot does work. Only way to root or unlock bootloader the device needs full boot into system so i can enable adb debugging or usb debug in developer settings so the computer will let the device get past the failed error locked part....
Do you know how to get the usb debugging turned on so the computer can grant full access to the device then il be able to actually crack into it and flash through fastboot..
Or where the usb debugging file is in the system.img if i extract it, use text editor and give the bool a yes that its been accepted then repack the system,img and flash it usinh sp flashtools, then i might ge able yo get it up and running....
After flashing all kinds of firmware for this device they all pass the flashing except for a few of them, ones that dont work wont even let the device boot to show system thing, then flashing correct firmware it allows the first screen again and the menu to pick fastboot but wont fully boot up..
Im thinking there must be somekind of lock the device put on from letting you oem unlock bootloader or booting into recovery mode because the firmware is working or it wouldnt take it using SP Flash Tools or even let it boot up as it would either reboot instantly or not even turn on, if the boot partition or recovery partition was courupt or broken or damaged it wouldnt take it during the flashing process it would fail....
If you know how i can activate the usb in developer settings from a file in system.img file after ectracting it then thats prob my BEST OPTION OR BUY A USED MOTHERBOATD OFF EBAY...
Lol
KixxTheManz said:
Ya i can flash the firmware correctly in SP Flashtool it comes back with green checkmark, all the firmware is for the correct device, its just when i had it given to me it had broken screen and bad battery, so i buy new screen, battery, backcover for it and when i booted it up it just sticks on the first screen shown ( Powered by Android ) then after like 30 secs it reboots back to that screen.. I can hold the vol + and power and get the menu to pick RECOVERY or FASTBOOT or REBOOT, recovery just reboots to powered by android screen then reboots after 30 secs, fastboot lets me use adb and fastboot but cant flash it says failed locked, and fastboot oen unlock or any of the commands to do with unlocking or flashing just gets me failed locked, but fastboot does work. Only way to root or unlock bootloader the device needs full boot into system so i can enable adb debugging or usb debug in developer settings so the computer will let the device get past the failed error locked part....
Do you know how to get the usb debugging turned on so the computer can grant full access to the device then il be able to actually crack into it and flash through fastboot..
Or where the usb debugging file is in the system.img if i extract it, use text editor and give the bool a yes that its been accepted then repack the system,img and flash it usinh sp flashtools, then i might ge able yo get it up and running....
After flashing all kinds of firmware for this device they all pass the flashing except for a few of them, ones that dont work wont even let the device boot to show system thing, then flashing correct firmware it allows the first screen again and the menu to pick fastboot but wont fully boot up..
Im thinking there must be somekind of lock the device put on from letting you oem unlock bootloader or booting into recovery mode because the firmware is working or it wouldnt take it using SP Flash Tools or even let it boot up as it would either reboot instantly or not even turn on, if the boot partition or recovery partition was courupt or broken or damaged it wouldnt take it during the flashing process it would fail....
If you know how i can activate the usb in developer settings from a file in system.img file after ectracting it then thats prob my BEST OPTION OR BUY A USED MOTHERBOATD OFF EBAY...
Lol
Click to expand...
Click to collapse
Well, as far as i can tell and did unlock 2 asus devices of the same model (still, X00HD):
i didn't needed to go thru android, since Asus never had an "OEM Unlock" thing to enable once unlocked dev settings-
yet, i'm speaking about the X00HD since, again, i never owned an X01BD, but i am trying to apply the same reasoning even if it is an entire different model but still same brand.
Dunno, in my case i was able to get the bootloader unlocked by going getvar all and got the secret key to unlock it just as easily by experimenting and finding cmds to use over this device's forum in here while being in Fastboot mode.
Before stepping my feet to Fastboot, tho, i even tried to get my hands at an OEM Unlocker apk made by Asus:
but to no avail it only worked on devices with really old firmware and since my device was updated to the latest Oreo FW, it was impossible to perform since things got patched overtime.
Sadly, i really don't know how to modify values over system.img files myself and tick up variables by inspecting over hex editors and such.
Least i know is getting the Brotli binaries and some other specific tool on GitHub to extract stuff from Android .img files, but that's all my skills really get limited to since i'm no dev myself nor either someone who can reverse engineer things just as well.
I think you could be out of luck on that regard.
Only thing that remains is going to a particular mode where it is required putting the phone apart and touch 2 specific pins on the board to enter it.
I currently forgot the name of this mode, but i do know by fact it's a common thing between Huawei devices.
If even this thingie won't help, then i really dunno myself.
Maybe someone else could be of help instead of me lol.
Ya ill try touching the two pins but what two oins and touch them with whst? Give me a roll out on what to do, i just dont understand why it accepts firmware but wont let me boot up into it or recovery mode or flash anything because at first it flashes then when it completes it fails and says remote unknown locked
Also im going to try find a way to format or partition the main system partitions maybe the system.img is landing on a different section of the harddrive... just need tge partitions for thus device
KixxTheManz said:
Ya ill try touching the two pins but what two oins and touch them with whst? Give me a roll out on what to do, i just dont understand why it accepts firmware but wont let me boot up into it or recovery mode or flash anything because at first it flashes then when it completes it fails and says remote unknown locked
Click to expand...
Click to collapse
Aight, to start with: i'll share out a couple of links.
First, here's a picture on where the testpoints of the device are.
As of second, you need some tweezers or something that is able to touch such testpoints inside the board (unrelated, but the GH page to PotatoNV has a guide what to do with the testpoints- even tho, the page redirects you to a tool that only works with Huawei devices. Don't test it on that asus device.).
Not sure about the flashing tool, honestly, but i do know for a fact i couldn't share software in here due to rules of this forum.
Since this is, i suppose, a device with a Qualcomm SoC:
maybe you could use stuff like QFIL Flash Tool for the job (dunno about partitions, for that you should get some linux knowledge- since android uses the linux kernel to communicate with everything inside the device).
Also, i've got something intriguing right now:
apparently the forum for the X01BD effectively exists over XDA lol (turns out the X01BD is a Zenfone Max Plus M2 and not an M1).
Maybe you can check out here for further custom ROMs and recoveries, plus more proper help on the matter- as of firmware dumps, you could try hopping over Android FileHost, firmware.mobi, or steep your feet into some unknown forum that has the firmware dumps of this specific device and restore it logically (or simply doing a google search by doing [insert model number here] firmware dump - if google only gets you to shady sites, stick to the XDA forum on the device).