Model: ASUS_Z00AD(ZE551ML)
RAM: 4G
Firmware/APP Version: Latest
Frequency: All the time
Rooted/Unlocked: No
APP Name: None/All/System
Hello, all!
I'm pretty sure I'm gonna have to send it back for an exchange, but I tried to wipe the cache partition on my brand new ASUS ZenFone and got impatient. On top of that I forgot to allow USB debugging. So here's what I did, and the problems I'm facing now:
I installed the latest OTA update that was sent
After three hours of trying to find a fix for the notification glitch, I arose to the solution that it was a permanent bug, however seen many reports of clearing the cache to help
Assuming it was the system cache, I powered the phone down and booted into fastboot, then into recovery using a tutorial found on YouTube
I got into the F:/Cache partition by moving the cursor down and selecting "Wipe Cache Partition"
The process was taking longer than expected, so I powered off the phone in what I feel is a catastrophic failure
Problems:
Bootloader is corrupt with only showing the "dead" android with it flashing slow and constantly
Unable to access recovery mode anymore (see above problem)
Able to access fastboot, but no USB Debugging is turned on
ADB can't access the device (most likely because of the USB Debug. turned off.)
I am NOT rooted and DO NOT have a custom ROM like CyanogenMOD
is there any helping the poor thing or do I have to send it back? Thank you for reading if you got this far.
sincerely,
J
Hello
I did the same thing and fixed it by plugging the phone in fastboot mode and typing the following command : fastboot erase cache
I was then able to go back to recovery and flash a full stock rom with adb sideload
Hope it does the trick for you
dapezzz said:
Hello
I did the same thing and fixed it by plugging the phone in fastboot mode and typing the following command : fastboot erase cache
I was then able to go back to recovery and flash a full stock rom with adb sideload
Hope it does the trick for you
Click to expand...
Click to collapse
Thank you for your reply.. TBH, I have no idea how it works, but it does all of a sudden. The first thing I did, tho, was enable USB Debugging. Goddess this was a long and tedious possess that I hope I don't have to go through again.. This is a great case and point where Apple wins in simplicity. But, yes, to that hater who's reading this: I did know what I was doing, I've rooted many androids before, I just got careless.
wolfboytech said:
This is a great case and point where Apple wins in simplicity.
Click to expand...
Click to collapse
Only when Apple works, had my little brother pulling out his hair trying to get an iphone to downgfrade after the upgrade pretty much pissed all over the actual using of the phone for calls... To make matters worse, it was his work phone and he'd just got through updating everyone's phone at the company...
Simple way to go bald and loose a job....
wolfboytech said:
Thank you for your reply.. TBH, I have no idea how it works, but it does all of a sudden. The first thing I did, tho, was enable USB Debugging. Goddess this was a long and tedious possess that I hope I don't have to go through again.. This is a great case and point where Apple wins in simplicity. But, yes, to that hater who's reading this: I did know what I was doing, I've rooted many androids before, I just got careless.
Click to expand...
Click to collapse
Actually it depends on how much you want to get out of your phone. The more you get the trickier it gets. Most people won't run into those troubles because they just got what manufacturers give to them.
wolfboytech said:
Model: ASUS_Z00AD(ZE551ML)
RAM: 4G
Firmware/APP Version: Latest
Frequency: All the time
Rooted/Unlocked: No
APP Name: None/All/System
Hello, all!
I'm pretty sure I'm gonna have to send it back for an exchange, but I tried to wipe the cache partition on my brand new ASUS ZenFone and got impatient. On top of that I forgot to allow USB debugging. So here's what I did, and the problems I'm facing now:
I installed the latest OTA update that was sent
After three hours of trying to find a fix for the notification glitch, I arose to the solution that it was a permanent bug, however seen many reports of clearing the cache to help
Assuming it was the system cache, I powered the phone down and booted into fastboot, then into recovery using a tutorial found on YouTube
I got into the F:/Cache partition by moving the cursor down and selecting "Wipe Cache Partition"
The process was taking longer than expected, so I powered off the phone in what I feel is a catastrophic failure
Problems:
Bootloader is corrupt with only showing the "dead" android with it flashing slow and constantly
Unable to access recovery mode anymore (see above problem)
Able to access fastboot, but no USB Debugging is turned on
ADB can't access the device (most likely because of the USB Debug. turned off.)
I am NOT rooted and DO NOT have a custom ROM like CyanogenMOD
is there any helping the poor thing or do I have to send it back? Thank you for reading if you got this far.
sincerely,
J
Click to expand...
Click to collapse
there is nothing like stupidity in this bro... this is all about curiosity..these problems makes you more aware of ur device and what andriod development actually is.. getting into these problems and solving it gives a great pleasure and confidence in urself.. which APPLE can never give. m sure every android geek is gone through this problem.. so be happy and proud bro.. happy new year.
c_/\/\_k said:
there is nothing like stupidity in this bro... this is all about curiosity..these problems makes you more aware of ur device and what andriod development actually is.. getting into these problems and solving it gives a great pleasure and confidence in urself.. which APPLE can never give. m sure every android geek is gone through this problem.. so be happy and proud bro.. happy new year.
Click to expand...
Click to collapse
Exactly bro! In learning about androids full potential, its all about trial & errors. By the way, speaking of Apple. IPhones are too simple for advanced users/geeks like us [emoji12]
Sent from my ASUS_Z00AD using Tapatalk
Related
Hey,
I have a huge problem, people.
I've had some issues with one of the ROMs that I tested, so decided to restore my Nandroid Backup. I've wiped everything and runned the Nandroid Restore of my previous - working ROM (EzHero 1.2.1) - everything looked as if it worked fine, the operation was completed succesfully. So, given that I've chosen reboot phone option in the Recovery (AmonRa 1.6.2) and it turned on with a regular booting screen and just stuck on it. It's been like 2hrs and I'm constantly stuck on this "loading" screen and cannot turn the mobile off either by holding Power or Power Home or Power Home Back. Nothing. I don't wanna take the battery out as I heard that it can be devastating.
So, to clarify all of that, I have a phone connected via cable (yet no connection through ADB) to PC, so the battery would not discharge and the phone itself is stuck on booting logo/animation, the one just before it goes into the usual desktop screen.
How can I go about it to restore it?
Thanks!
Do you have App2SD ?? If yes it may took ages to boot when you do a first boot... But that only works if you had done a Nandroid + Ext...
Its fine to take your battery out,... Reset and give it another try at booting. If it fails again, try booting without SD in. If it fails again, try doing another restore of your nandroid. Fail again,... Full wipe then reflash ROM.
There is only risk of bricking when flashing a new radio and interrupting the process.
sebxd said:
Do you have App2SD ?? If yes it may took ages to boot when you do a first boot... But that only works if you had done a Nandroid + Ext...
Click to expand...
Click to collapse
I do have apps2sd but haven't done +Ext.
When I soft-reseted the device it obviously went into boot loop again BUT I have managed to connect it to my PC through ADB now and wonder if I could use it to my advantage?
ddotpatel said:
Its fine to take your battery out,... Reset and give it another try at booting. If it fails again, try booting without SD in. If it fails again, try doing another restore of your nandroid. Fail again,... Full wipe then reflash ROM.
There is only risk of bricking when flashing a new radio and interrupting the process.
Click to expand...
Click to collapse
The problem is my phone IS stuck at boot loop and even if I soft reset it I don't have enough time to press POWER and HOME to go into Recovery so I cannot check if I could do restore. Would connection through ADB help as I currently after soft reset have it?
I have to clear something up my phone is in the boot loop but not as in that it reboots itself time after time - NO! It just sticks on the booting animation and that's it.
Oh, and running this "fastboot boot recovery-RA-hero-v1.6.2.img" through ADB just sits stuck at "< waiting for the device >" though I _can_ list the contents of my Hero through shell.
Also when I press vol up or vol down in the state with startup screen beeing stuck I can hear it same way as if I heard it in the working phone - as in beeping when pressing up and beeping lower when down.
I'm not so clued up on fastboot commands to be honest.
Take your battery out,... Hold HOME and put your battery back in..... KEEPING HOME HELD IN
OK! Finally after finding enough courage to do so I pulled the battery out as ddotpatel advised me to - I have to say it was scary 30s, real scary. Anyway, it seemed that his advice was correct and he is in fact a very wise man - THANK YOU! Afterwards I've done all the wipes again as I did initially and instead of trying to recover it from my Nandroid backup I just gave up and reflashed it again. It didn't work, so I reformated and repartitioned the SD card and it's all good now... And I'm a happy puppy! Actually, I'm no puppy at all but I am happy nonetheless.
@ddotpatel Thank you sir! You are a Gentleman and a Scholar and I shall praise your name forever on this and other Android forums alike. ^__^ Just a quick question though: removing a battery is prohibited only when flashing radio and when the phone's on the "phone & a box/arrow" picture, right? So if I ever have an booting/issue error whilst flashing custom ROMs that do nothing to the radio I should be fine poping the battery?
I know I sad it trice already but - ddotpatel, sir, THANK YOU!
kad3t said:
....Just a quick question though: removing a battery is prohibited only when flashing radio and when the phone's on the "phone & a box/arrow" picture, right? So if I ever have an booting/issue error whilst flashing custom ROMs that do nothing to the radio I should be fine poping the battery?...
Click to expand...
Click to collapse
Yes indeed, you are correct....
and as for all the praise,.... Oh stop it, your making me blush!
I'm Jealous I firstly tried to help you
ddotpatel said:
Yes indeed, you are correct....
and as for all the praise,.... Oh stop it, your making me blush!
Click to expand...
Click to collapse
I have to say I would not made the move if it was not for you though I did check few of your earlier posts and those made me follow your advice as you seem very knowledgeble. ^__^
sebxd said:
I'm Jealous I firstly tried to help you
Click to expand...
Click to collapse
Thank you too! I'm sorry but it was his advice that helped/pushed me in the right direction. However your try is also equally appreciated. ^__^
kad3t said:
I have to say I would not made the move if it was not for you though I did check few of your earlier posts and those made me follow your advice as you seem very knowledgeble. ^__^
Click to expand...
Click to collapse
Ah its no problem,... I honestly didn't know a single thing until I started lurking on here. Just keep your eyes open, try to read other peoples problems even if you don't know a solution yourself. There are alot of helpful guys and gals on here.
Pay it forward. Peace.
ddotpatel said:
Ah its no problem,... I honestly didn't know a single thing until I started lurking on here. Just keep your eyes open, try to read other peoples problems even if you don't know a solution yourself. There are alot of helpful guys and gals on here.
Pay it forward. Peace.
Click to expand...
Click to collapse
No worries, mate! My post count did not go up to 73 in like 5 days for no reason. I try to help as much as I can and also would not run into those problems if I wouldn't flash and benchmark many ROMs (posting all the stats for the same configurations & settings) here for others to decide on their own which they liked best either. ^__^
Peace!
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
sfrat said:
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
Click to expand...
Click to collapse
if you can get into download mode im guessing there is some hope for you.
go here: http://droidangel.blogspot.com/2011/05/samsung-galaxy-ace-s5830-original-stock.html
look for: S5830XXKP9
and make sure you have odin 4.38 and flash with that.
try to install cwm and install a customrom
Sent from my GT-S5830 using xda premium
sfrat said:
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
Click to expand...
Click to collapse
with the cellphone off, put out ur baterry for a minute, then maintain ur finger into the volume down button and the power button tell a friend or if u can alone insert the batery while quickly pressing volume down and power button to get into download mode, and flash.
Hehehe,bootloop is horrible,you just have to get in download mode & flash with 2.3.4 firmware with Odin,just that steps and you save your SGA.
I got bootloop many times and Odin saved me.
Sent from my SGA
robinandroid said:
try to install cwm and install a customrom
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
he cant go back in recovery mod............
If you can go to recovery mode than you can just wipe the data and cache. This saved me many times. Otherwise on what ever OS you may be , just create new user name after removing samsung android drivers. Login from new user name and than re install drivers again and now flash your phone from firmware which was installed on your phone before you bricked it. This helped me a few times.
dr_vishal said:
If you can go to recovery mode than you can just wipe the data and cache. This saved me many times. Otherwise on what ever OS you may be , just create new user name after removing samsung android drivers. Login from new user name and than re install drivers again and now flash your phone from firmware which was installed on your phone before you bricked it. This helped me a few times.
Click to expand...
Click to collapse
hey guys thanks for the answers, but unfortunately i am not able to reach the recovery mode, my phone just reach the download mode.....i will try with the xxkp9, even if i have already tried it...I guess i have tried at least 15 firmwares without any success
Helping to make your Christmas Merry
It seems that you've already received a lot of help for unbricking your device. So I'll try to help out in unlocking your phone after you finished unbricking it.
This is the method I personally used on my locked Ace:
http://forum.xda-developers.com/showthread.php?t=1335548
It's perfectly safe. 100%.
King Kaze said:
if you can get into download mode im guessing there is some hope for you.
look for: S5830XXKP9
and make sure you have odin 4.38 and flash with that.
Click to expand...
Click to collapse
I have tried the XXKP9 again, it is not working, as usual Odin ends to load the firmware and then it goes back in the endless loop mode....there is no chance to get it back?
franzks said:
It seems that you've already received a lot of help for unbricking your device. So I'll try to help out in unlocking your phone after you finished unbricking it.
This is the method I personally used on my locked Ace:
http://forum.xda-developers.com/showthread.php?t=1335548
It's perfectly safe. 100%.
Click to expand...
Click to collapse
thank you very much I will follow your advice...IF I will be able to get my phone back which seems impossible =(
@dr_vishal
Thank you first of all, I have tried to uninstall and reinstall the android device driver, but it doesn't seems to be the problem, Odin ends with a "PASS" at the end, I guess there still is comunication in the between the two devices...
Hopefully it will be a Merry Christmas =)
It's not impossible. I'm relatively new here but I have noticed quite a few "bricked" threads already. Most of them (if not all) have been able to fix their device. I haven't seen a single person permanently brick their device, so I would guess that your chances of fixing it are really high. Just be patient and keep describing your situation and more experienced help will certainly arrive. I'd really like to help out but I have no idea how to fix it as I have not experienced bricking my phone yet.
Anyway, if the method for unlocking I suggested works for you kindly press the Thanks Button. Merry Christmas!
franzks said:
It's not impossible. I'm relatively new here but I have noticed quite a few "bricked" threads already. Most of them (if not all) have been able to fix their device. I haven't seen a single person permanently brick their device, so I would guess that your chances of fixing it are really high. Just be patient and keep describing your situation and more experienced help will certainly arrive. I'd really like to help out but I have no idea how to fix it as I have not experienced bricking my phone yet.
Anyway, if the method for unlocking I suggested works for you kindly press the Thanks Button. Merry Christmas!
Click to expand...
Click to collapse
Thank you franzks!
I promise I will try your method and I am positive it will works, but I need to get my phone back...so I will add few new information I have found out talking to a friend of mine which has my same device and the same carrier as well.
The version built-in is:
GINGERBREAD.BVKQ9
S5830BVKQB
[email protected]#1
Any suggestion about the firmware I am suppose to flash in?
I am actually passing through all the version contained in the address droidangel you gave me...at the moment no one is working...I will keep trying...
sfrat said:
Thank you franzks!
I promise I will try your method and I am positive it will works, but I need to get my phone back...so I will add few new information I have found out talking to a friend of mine which has my same device and the same carrier as well.
The version built-in is:
GINGERBREAD.BVKQ9
S5830BVKQB
[email protected]#1
Any suggestion about the firmware I am suppose to flash in?
I am actually passing through all the version contained in the address droidangel you gave me...at the moment no one is working...I will keep trying...
Click to expand...
Click to collapse
Guys,
I am out of ideas, I have tried each single firmware I have seen around internet, no one is working, any tip or advice or suggestion?
I messed up with the efs, and I guess that's all, the phone is gone....now it needs a JTAG or whatever is its name....
maybe to get the warranty still valid I should broke totally the phone over charging it....??
sfrat said:
Guys,
I am out of ideas, I have tried each single firmware I have seen around internet, no one is working, any tip or advice or suggestion?
I messed up with the efs, and I guess that's all, the phone is gone....now it needs a JTAG or whatever is its name....
maybe to get the warranty still valid I should broke totally the phone over charging it....??
Click to expand...
Click to collapse
Did you try that?
http://forum.xda-developers.com/showthread.php?t=1153310
just a thought
a lot of people have talked about reflashing it and all but have you managed to get into the recovery mode at all once you have reinstalled the rom with odin? if you can get to that you just need to hit factory reset, wipe cache and wipe dalvik and normaly after that it will work fine... so far ive been stuck in soft brink 3 times and each time doing the wipes from the recovery mode has worked...
Pinting said:
Did you try that?
http://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
I've tried to use the oneclick, but it seems it doesn't recognize the phone, since, i guess, it's made for a galaxy s.
The others are not my case, since I am able to get download mode, and all these are made to can get it back.
Anyway I found out a post in which the people were talking about the s5500, which apparentely is similiar to my device, and the owners of that model experienced a similar problem doing the same process....anyway in that post the people needed to use a Jtag, which is the only way to get it back....so I though it could be the same solution for my problem...but I don't know anybody with Jtag, so the only way is contacting the service center.
thanks anyway, when I will be back at home after Christmas I will try to find the ticket and I will probably try to get it back in warranty, since is preatty new...
@torchwolfery
I am not able to reach recovery mode, there is no way to get it back, even flashing the phone with different firmwares, all I got is download mode, and apparently that is completely pointless...since the only change in the phone behavior is that if i install a certain firmwares it doesn't even have the back-light working when it is stuck in bootloop.
Warranty is your only hope (as it was mine once and it worked).
I didn't think it was possible to brick these phones. There I have tried so much to try and brick it but I have not been able to as it still always goes into 'download' mode. The only advice I can give you is double check that you are using the correct version of Odin which is v4.38 and that you use cooper v1.0 as your OPS. If dont mind me asking, but exactly what did you do or do you remember the steps you took to brick it? What buttons are you using for 'recovery' mode.
Also please clarify if Odin is going in a loop or does the phone come on and then keeps rebooting? If it is the phone that keeps rebooting, then wiping cache and data partition should do the trick. This can be done by going into recovery mode (which I am aware you cannot get into) or if you can manage to get into the dialler quick enough before the reboot, by dialling *7267*3855# and that should format the relevant partitions (data and cahce) and bring it back to factory settings. Without further info, I cannot really tell exactly what the situation is.
The fact that you are getting 'download' mode, I dont think that it is bricked because it will still allow you to write the relevant directory/files to the relevant blocks. Either way, would be interested to know.
Hello people, I really hope you can help me out on this one. I own the Sony Xperia U, which I had succesfully bootloader unlocked and rooted months ago. It had been runing ICS smoothly and everything was working great, until two days ago, when the screen started ocasionally missing/ignoring taps/sweeps. It was a real pain to type since it would miss a letter or more in every word I typed. I decided to do a factory reset, and so did I. The problem was not fixed. Now, I'm dealing with more: My computer does absolutely nothing when I connect the XU, and the phone itself only recognizes a charger. The same in debugging mode. Superuser does not work (can't get root access despite it says it has granted the rights), I can't even uninstall Superuser. What are my options? Can I somehow flash some things and do a full reset of the phone? I have CWM Recovery installed!
Thanks in advance!
PS: The main ambition is to get rid of everything but the screen problem. I'll probably replace the digitizer after that.
Anyone? Sorry for second post!
Proberly hardware problem. But you unlocked your bootloader and your pc is now as good as nothing. Just pay for the repair :-\
Sent from my LT22i using xda app-developers app
Dimas.94 said:
Hello people, I really hope you can help me out on this one. I own the Sony Xperia U, which I had succesfully bootloader unlocked and rooted months ago. It had been runing ICS smoothly and everything was working great, until two days ago, when the screen started ocasionally missing/ignoring taps/sweeps. It was a real pain to type since it would miss a letter or more in every word I typed. I decided to do a factory reset, and so did I. The problem was not fixed. Now, I'm dealing with more: My computer does absolutely nothing when I connect the XU, and the phone itself only recognizes a charger. The same in debugging mode. Superuser does not work (can't get root access despite it says it has granted the rights), I can't even uninstall Superuser. What are my options? Can I somehow flash some things and do a full reset of the phone? I have CWM Recovery installed!
Thanks in advance!
PS: The main ambition is to get rid of everything but the screen problem. I'll probably replace the digitizer after that.
Click to expand...
Click to collapse
Well, I would recommend to flash stock again to remove root and relocking the bootloader and if the problem gets solved, root it again.
moli2398 said:
Well, I would recommend to flash stock again to remove root and relocking the bootloader and if the problem gets solved, root it again.
Click to expand...
Click to collapse
Fixed it by flashing stock ftf! Thanks!
hey all, as you know i was trying to port full sense for desire x dual sim community. ive already searched for custom ROM for desire x dual sim on that Chinese market community web site..no luck there wasn't any full jb sense ROM for dual sim dx.
so i ported it myself and to test it i borrowed dx dual sim from my friend.
so it goes like this. my friends dx dual sim was perfectly stock and n wasn't rooted. this morning i unlocked its boot-loader and it all went so well. within 5 min i unlocked the boot-loader and after that i flashed recovery which i founded in previous threads, it said that the recovery was specially made for desire x dual sim and was posted here on xda from that Chinese forums. anyways i flashed the recovery, it was miui using fast-boot and then i flashed superuser package and rooted the desire x dual sim. it was factory rested and it rebooted i saw superuser in the menu and i was quite happy. but then in order to flash the rom i ported, i had to change the recovery as the miui recovery wasn't taking backups. so i changed my recovery to twrp, made by nexus_prime in a few threads back. i flashed that recovery and everything was good till then. after that when i try taking backups from twrp recovery it says failed. i was sick of trying again and again but no luck, then twrp recovery suggested that i should install super su in order to gain root. i said ok install it and then my device rebooted. i saw super su app there and also not to forget i was already having super user installed cause i was rooted. the super su app wasn't working it said updating binary and then it said failed. i uninstalled it thinking its not gonna work for me. after i uninstalled it, i rebooted my deice to fast-boot in order to change my recovery back to miui.
i powered desire x dual sim off and then boom, **** my damn device is not turning on now, ive already tried looking for solution online and ive already tried changing battery and pulling them off and on but no luck damn it. when connected it shows orange led and then cpu vibrates like 5 times every 3 hours later. it doesn't boot neither it gets into boot-loader.
some body please tell me soon what wrong i did and what am i suppose to do now? and some one (@xpirit) said that desire x dual sim cannot be bricked if its s -on.
what should i do now. ill be in big trouble if my friends find out what happned to his device.
someone pls help me out ASAP.
thank you
Let it charge peacefully for an hour
Sent from my HTC Desire X using xda app-developers app
not a battery issue
please i respect youre help but ive already said i aint a battery or charging problem, its annoying to see that kind of solutions - pull battery out, let it charge or unplug and plug it ..etc . all these are really not helping, i think my boot loader or something like that is erased and thats why its happening. i want a fix to the solution, any help is always appreciated, except the stupid battery or charging things.
thanks
lol, you dont even know half of what you are talking about.... you tried to port roms, before even learning rooting and flashing basics, and you tell him his solution is stupid?
Its true, you cant mess up the boot-loader so easily.... its just that you have tried to flash SU binary from TWRP, which is not good.... just boot to recovery, flash a superuser-arm-xyz.zip avaialable on androidsu.com or something, then you will get it booting. Otherwise, if you have mistakenly wiped system partition, then you are out of luck and you will have to take another desire x, root it, take backup, copy it to sdcard and then use it restore system on this phone.
Next time, read read and read more before this kind of experiments.
Regards
Yasir
PLEASE, TRY.. to read carefully sir.
i said desire x t328w is completely dead, DEAD. i cant get into recovery not even into boatloadER. nothing happens when i press power button or try to go to the boot loader. its like it has no life. only sign of life it shows is when it is connected to the charger, the orange led lits up and hence and that only thing which changes in this device.
please, if i could go to the recovery id solved this issue by my self rather than troubling you all. ive been searchinh for this kind of problem over the internet some says it cant be repaired by flashing or etc.. some says cpu is faulty etc. i dont know what wrong i did.
also i didnt flash super user via twrp
i flashed it via miui recovery
IN NO WAY I DIS RESPECT ANY DEVELOPER OR ANY USER. I'M ALREADY IN A MESS WANT A GOOD SOLUTION WHICH SHOULD WORK, RATHER THAN CHARGE YOUR DEVICE OR REPLACE THE BATTERY OR ETC.
THANKS
Blue3125 said:
PLEASE, TRY.. to read carefully sir.
i said desire x t328w is completely dead, DEAD. i cant get into recovery not even into boatloadER. nothing happens when i press power button or try to go to the boot loader. its like it has no life. only sign of life it shows is when it is connected to the charger, the orange led lits up and hence and that only thing which changes in this device.
please, if i could go to the recovery id solved this issue by my self rather than troubling you all. ive been searchinh for this kind of problem over the internet some says it cant be repaired by flashing or etc.. some says cpu is faulty etc. i dont know what wrong i did.
also i didnt flash super user via twrp
i flashed it via miui recovery
IN NO WAY I DIS RESPECT ANY DEVELOPER OR ANY USER. I'M ALREADY IN A MESS WANT A GOOD SOLUTION WHICH SHOULD WORK, RATHER THAN CHARGE YOUR DEVICE OR REPLACE THE BATTERY OR ETC.
THANKS
Click to expand...
Click to collapse
Did you even try the solution Infinity gave you, porting to another device is very risky and this could be the outcome.
Blue3125 said:
PLEASE, TRY.. to read carefully sir.
i said desire x t328w is completely dead, DEAD. i cant get into recovery not even into boatloadER. nothing happens when i press power button or try to go to the boot loader. its like it has no life. only sign of life it shows is when it is connected to the charger, the orange led lits up and hence and that only thing which changes in this device.
please, if i could go to the recovery id solved this issue by my self rather than troubling you all. ive been searchinh for this kind of problem over the internet some says it cant be repaired by flashing or etc.. some says cpu is faulty etc. i dont know what wrong i did.
also i didnt flash super user via twrp
i flashed it via miui recovery
IN NO WAY I DIS RESPECT ANY DEVELOPER OR ANY USER. I'M ALREADY IN A MESS WANT A GOOD SOLUTION WHICH SHOULD WORK, RATHER THAN CHARGE YOUR DEVICE OR REPLACE THE BATTERY OR ETC.
THANKS
Click to expand...
Click to collapse
Hmm Yep your Screwed... Looks like it's time to Buy Your Mate a New DesireX
yes, BUY A NEW PHONE (See, i didn't advise to charge battery or something.)
OnTopic:
I happened to have the same issue once on my desire bravo.... and guess what solution fixed it???? (CHARGING IT) coz its battery was SO LOW, whenever i tried to power up, it flashed leds.
Calm down and think, also can you post what you have tried ? Did you let it finish charging ? Tried plugging into pc ? Etc etc, might have to lend your mate your phone ps wtf you testing stuff on your mates phone for ? Best to use your own, if yours is the same take a backup 1st, also dont bother trying recovery go for bootloader 1st once you can get into that rest will be easier, worst case senario you will have to pay someone to fix
Sent from my HTC Desire X using xda app-developers app
azraelcelt said:
Calm down and think, also can you post what you have tried ? Did you let it finish charging ? Tried plugging into pc ? Etc etc, might have to lend your mate your phone ps wtf you testing stuff on your mates phone for ? Best to use your own, if yours is the same take a backup 1st, also dont bother trying recovery go for bootloader 1st once you can get into that rest will be easier, worst case senario you will have to pay someone to fix
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Thanks for your sensible answer mate. But I'm afraid you don't know maybe that i cannot access boot loader nor does my phone says a single word. Also I've being charging it for more then 10 hours. Nothing happens when connected to PC. worthless. I'm screwed and i learned a lesson that never to mess around with someone else device even if other says it 'cannot be bricked'.
Thank you all who help and also who really put me this situation.
btw now his desire x is resting at HTC, i don't know what will they say as for now i told them nothing about rooting and all other stuff i tired..
Blue3125 said:
Thanks for your sensible answer mate. But I'm afraid you don't know maybe that i cannot access boot loader nor does my phone says a single word. Also I've being charging it for more then 10 hours. Nothing happens when connected to PC. worthless. I'm screwed and i learned a lesson that never to mess around with someone else device even if other says it 'cannot be bricked'.
Click to expand...
Click to collapse
It is common problem with this phone.
Simple cure - pull out the battery and let the phone stay without charger and battery during an hour or two.
Then it will be OK again, but until next power off.
I think the problem is in custom recovery. I have the same problem with friend's phone. But it's working well without power off, so I don't want to mess with it again
Disconnect Phone from charger.
Press the Power button.
Connect the Charger while the button is pressed. Phone should start.
I've done it several times now, main reason being, battery was not having any charge.
Never mind guys it was the motherboard which was really screwed. I don't know what really caused it but the only thing I'm aware of right now is that it'll cost a lot
Blue3125 said:
Never mind guys it was the motherboard which was really screwed. I don't know what really caused it but the only thing I'm aware of right now is that it'll cost a lot
Click to expand...
Click to collapse
Yeah they're extortionate prices for HTC's, in the past I've just scrapped phones instead of getting them repaired when they have motherboard or problem relating to charger port.
Sent from my HTC Desire X using Tapatalk
I'm interested in running a custom Rom on my mpcs LG f6 (ms500). I'm a part timer at this, my understanding of code is devastatingly deficient.
I have a an l9 and another f6 that won't even turn on and I'm wondering where, even, to begin.
All are mpcs.
All three, including the one I'm writing this on presently, were/are rooted.
An update took out the non-working f6, and the l9 was my bad.
I'm now on a rooted f6 running battery booster pro, overclocked with freedom kernal, with roehsoft ram expander doubling my ram to 1608.
I realize my circumstances are all over the place, but, if anyone has the genuine benevolence to help me where they can; my gratitude will be unquantifiable.
findrome said:
I'm interested in running a custom Rom on my mpcs LG f6 (ms500). I'm a part timer at this, my understanding of code is devastatingly deficient.
I have a an l9 and another f6 that won't even turn on and I'm wondering where, even, to begin.
All are mpcs.
All three, including the one I'm writing this on presently, were/are rooted.
An update took out the non-working f6, and the l9 was my bad.
I'm now on a rooted f6 running battery booster pro, overclocked with freedom kernal, with roehsoft ram expander doubling my ram to 1608.
I realize my circumstances are all over the place, but, if anyone has the genuine benevolence to help me where they can; my gratitude will be unquantifiable.
Click to expand...
Click to collapse
I'll give a shot at trying to help you with the L9 but I'm going to need some details about what happened. :/
Thank you AshIndigo
L9 rooted and running system tuner pro. I turned on the oem battery function, kernal, doo-hicky (highly technical terminology). The unit ceased recognizing the battery after reboot. It stated, at boot, to insert oem battery and will not take a charge.
I'm considering a wipe and a new bootlaoder with a custom Rom if possible, but I'll settle with just getting it working.
findrome said:
Thank you AshIndigo
L9 rooted and running system tuner pro. I turned on the oem battery function, kernal, doo-hicky (highly technical terminology). The unit ceased recognizing the battery after reboot. It stated, at boot, to insert oem battery and will not take a charge.
I'm considering a wipe and a new bootlaoder with a custom Rom if possible, but I'll settle with just getting it working.
Click to expand...
Click to collapse
Thats a new one. But what modes can you get into. S/W, fastboot, recovery, the wipe combination? If you can get into s/w mode just use the lg mobile tool and that should fix it. Otherwise we may need to reflash the phone. and is your bootloader unlocked?
It doesn't power up in the slightest. And it won't charge.
Bootloader was not unlocked, I'm still trying to wrap my skull jelly around that. I'm thinking flash might be the best option, but I'd prefer to preserve the data (not likely if flashed). I've downloaded LG flash tool, but the manual data entry is a mystery, excluding imei and serial.
findrome said:
Bootloader was not unlocked, I'm still trying to wrap my skull jelly around that. I'm thinking flash might be the best option, but I'd prefer to preserve the data (not likely if flashed). I've downloaded LG flash tool, but the manual data entry is a mystery, excluding imei and serial.
Click to expand...
Click to collapse
Alright I'm presuming s/w mode doesnt work but if it does then that would be nice. Next thing is to try fastboot. Here is a link to a fastboot for the l9
http://forum.xda-developers.com/showthread.php?t=2292828
If you manage to get into fastboot. We can reflash things. Truth to be told I dont know if we reflash we might have to wipe the device. :/
I've resolved myself to things being what they are.
What's s/w mode?
AshIndigo said:
Alright I'm presuming s/w mode doesnt work but if it does then that would be nice. Next thing is to try fastboot. Here is a link to a fastboot for the l9
http://forum.xda-developers.com/showthread.php?t=2292828
If you manage to get into fastboot. We can reflash things. Truth to be told I dont know if we reflash we might have to wipe the device. :/
Click to expand...
Click to collapse
Downloaded, followed instructions. Device booted once and quit while playing around with it, consistent with initial failure as I recall (if only vaguely), now on s/w update screen. Says please wait while upgrading.
Update:
Can enter s/w update. Now takes charge, will likely be 100% by the time you read this.
Lastly, can power on but powers off after entering screen unlock code.
Thank you again AshIndigo.
After some more dabbling, I've made it past the lock screen. The result is a message " please use genuine LG battery" before the unit shuts down and goes into what might might questionably be a bootloop. It's the system tuner pro app, set to start on start-up, that's the thorn in my side.
What are your orders captain?
findrome said:
After some more dabbling, I've made it past the lock screen. The result is a message " please use genuine LG battery" before the unit shuts down and goes into what might might questionably be a bootloop. It's the system tuner pro app, set to start on start-up, that's the thorn in my side.
What are your orders captain?
Click to expand...
Click to collapse
Sorry for replying late but if you have adb enabled we can uninstall the app easily. This should be the command to remove it.
adb uninstall ccc71.pmw.pro
AshIndigo said:
Sorry for replying late but if you have adb enabled we can uninstall the app easily. This should be the command to remove it.
adb uninstall ccc71.pmw.pro
Click to expand...
Click to collapse
No apologies needed, your time is greatly appreciated.
I ran the command, with what appears to be success. It seems though, the kernal remains intact.
A wipe seems imminent.
findrome said:
No apologies needed, your time is greatly appreciated.
I ran the command, with what appears to be success. It seems though, the kernal remains intact.
A wipe seems imminent.
Click to expand...
Click to collapse
(I just deleted everything I wrote and have to write it again )
Ok so before we try to re-flash the kernel. Lets just try the lg mobile support tool. If that doesn't work then heres instructions
1. If you have the p760 then heres the stock kernel
http://www.mediafire.com/download/87i322233ev36k8/stock-kernel.zip
3. Download it
4. extract the boot.img from the zips and put it into the "yours" folder in the fastboot folder
5. Get into fastboot
6. Make sure the device is connected by typing "fastboot devices"
(It should look like this) http://cdn.teamandroid.com/wp-content/uploads/2012/07/fastboot-devices-600x302.jpg
6a. Pray to Google
7. type "fastboot flash boot boot.img"
8. Pray again.
If you don't have the p760 then tell me which device you have so I can get the kernel
@ AshIndigo
P769BK
AshIndigo said:
(I just deleted everything I wrote and have to write it again )
6a. Pray to Google
8. Pray again.
If you don't have the p760 then tell me which device you have so I can get the kernel
Click to expand...
Click to collapse
Golden, you missed your calling.
It's a P769(bk). Not that the color makes a difference. It's also a T-mo, not mpcs. If that matters.
findrome said:
Golden, you missed your calling.
It's a P769(bk). Not that the color makes a difference. It's also a T-mo, not mpcs. If that matters.
Click to expand...
Click to collapse
I dont think I've missed it yet
Alright so there are 2 options right now.
1. You resign the kernel or wait for me to get on a windows computer so I can resign it.
2. You unlock your bootloader.
If you choose option 1 then and you want to try then here's the link.
http://forum.xda-developers.com/optimus-l9/general/guide-install-custom-roms-locked-t3249828
And here's the link to the kernel
http://d-h.st/pdM
1. Follow the manual instructions in the post except just do it for the boot.img and flash that instead.
"fastboot flash boot boot_bumped.img"
If you choose option 2 then here's a link with instructions. (My phone is perma-locked so I never got to try this)
http://forum.xda-developers.com/showthread.php?t=2601480 (Wish you luck if you try this)
If anything is unclear let me know.