Related
Hello everyone, my name is Christina and I am a fellow newb that needs your help...
I really really really need my kindle fire... and I promise I tried to look for help in the previous threads!!! Please find the generosities in your souls to help a newb like me!!!
My story:
About a year ago, I bought a KF and I successfully rooted it to ice cream sandwich (6.3.1 I think.. newest at the time). It had the play store, TWRP, etc.. So basically I believe I followed all of the steps on youtube correctly. But more recently.. my kindle started to shut down all of a sudden. My first thought was.. I think its crashing because im downloading these "new" applications and my KF cant handle it. So I decided to do some research and see if there has been any updates. I found that there was the new Jelly bean OS that I could update to, so I tried it out.
What I did:
First, I followed the video on youtube by TechBoss96 titled "restoring kindle fire..." and it didnt work. My computer (windows 7) didnt detect the "ADB android phone" in the device manager. I made sure I followed every step, and sadly it failed. So I tried to do the entire process again and it failed. So out of frustration, I went to my computer, and clicked on "format" for my KF...
Whats going on now (after a week of frustration):
When I plug in my KF to my computer, it is still charging succesfully.. Phew! But.. in my computer I do NOT see the KINDLE drive anymore (it was there before...) And in device manager, I do not see adb android phone or the kindle fire drive either.
When I try to turn on my KF: I see the original white and blue "kindle fire" logo. It doesnt go to the swirly loading page anymore. I see the logo for about 3-4 seconds then it just turns off -___-
Can anyone help me? It would be VERY VERY much appreciated! If its possible, I would like to at least have a "live chat" with someone that is willing to help me. You have NO IDEA how much it would mean to me if I can get this fixed in a timely manner. I leave for basic military training as of TUESDAY 8/14/2012 so I must get it fixed by then. I miss my kindle fire!!!
Glad it was an easy fix chrisleealee enjoy the modified stock for awhile but when you do decide to move on here is my pick http://forum.xda-developers.com/show....php?t=1778010 don't forget to add system to your scheme of wipes when changing systems good luck and have fun
---------- Post added at 04:38 AM ---------- Previous post was at 04:37 AM ----------
I think that was timely
THANK YOU!
Thepooch said:
Glad it was an easy fix chrisleealee enjoy the modified stock for awhile but when you do decide to move on here is my pick http://forum.xda-developers.com/show....php?t=1778010 don't forget to add system to your scheme of wipes when changing systems good luck and have fun
---------- Post added at 04:38 AM ---------- Previous post was at 04:37 AM ----------
I think that was timely
Click to expand...
Click to collapse
Thanks a million!! You were soo incredibly helpful! I wish I could press the thank you button a million times!!
Your welcome anytime
Hi all
I have one of these cheap ICS tablets.It won't let me post the link because I'm new but if you search amazon for A1CS Fusion5 Economy you can see the specs.
It's a bit slow and unresponsive (what do you expect for the price), so I thought flashing it with CM might help.
I got a CWM working on it and following a thread on these forums about allwinner tablets in general I flashed it with (in this order).
cm10_a10_20120913.zip
gapps-jb-20120726-signed.zip
protab2xxlv2_compatibility_1.2.0.zip
Clearly these were not the correct roms (in hindsight I can see that I have used an allwinner A10 rom when my tablet is an Allwinner A13).
After I shut down from CWM the tablet will not switch back on. It also won't boot into either recovery or download mode. Nothing happens when I plug it into its wall charger, nor will the laptop recognise it when plugged into the usb.
I think I have no way to fix this since it is unresponsive to everything that I might do to get it into a state to fixit, but I am very new to this so posting to see if anyone can help?
Did you ever unbrick your tablet and find a solution?
The same happened to me and I could find no way to recover the tablet and yes mine turned out to be an A13 as well
spoondoom said:
Hi all
I have one of these cheap ICS tablets.It won't let me post the link because I'm new but if you search amazon for A1CS Fusion5 Economy you can see the specs.
It's a bit slow and unresponsive (what do you expect for the price), so I thought flashing it with CM might help.
I got a CWM working on it and following a thread on these forums about allwinner tablets in general I flashed it with (in this order).
cm10_a10_20120913.zip
gapps-jb-20120726-signed.zip
protab2xxlv2_compatibility_1.2.0.zip
Clearly these were not the correct roms (in hindsight I can see that I have used an allwinner A10 rom when my tablet is an Allwinner A13).
After I shut down from CWM the tablet will not switch back on. It also won't boot into either recovery or download mode. Nothing happens when I plug it into its wall charger, nor will the laptop recognise it when plugged into the usb.
I think I have no way to fix this since it is unresponsive to everything that I might do to get it into a state to fixit, but I am very new to this so posting to see if anyone can help?
Click to expand...
Click to collapse
I'm afraid I've joined the club....
Does anyone know how to fix this?!!!!
Update!
I have since discovered that the bricking is almost certainly due to loading an incorrect ROM.
I am trying to find a ROM which will work and to upload it using livesuit (google and download it!). I will update further if I have any success, in the meantime I hope this helps someone!
Oh and if the tablet is not recognised by your PC, press and hold the power button for a little while (until your PC beeps like you connected a usb device)
Good luck and update me if you have any luck !
Update 2
Search for:
A7S_A13_86VEB_M707EBC_130511_V1.2
This rom will, once flashed using livesuite, at least allow you to boot to recovery again.
When that screen fired up again I had a big geeky smile on my face!
---------- Post added at 10:20 PM ---------- Previous post was at 10:07 PM ----------
And this cyanogen rom
cm_a13_20130628
will bring you almost back to where we want to be.....
http://www.slatedroid.com/topic/80689-rom-cyanogenmod-10-for-allwinner-a13/
No touchscreen yet......:silly::silly::silly:
Update 3
Still not quite there with the touchscreen but there are a bundle of driver details here:
http://forum.xda-developers.com/showthread.php?t=2189569
Nonetheless, all that is left to do (in theory!) is to identify the correct driver, enable usb debugging (using a usb mouse since the touchscreen doesn't currently work) and then use basic adb commands (if I can do it, you can too!) to push the driver to the device.
I will update in due course. I guess it's too late for you guys but maybe this will help someone one day.
Little help here?!
Well I've narrowed down the drivers to 1 of 3.
I'm trying to work out how to run these - maybe via adb or terminal emulator? to work out which one works.
Then I believe I need to amend the boot file or the script.bin to run the driver automatically?
Any advice gratefully received!
More!
Getting bored of these updates yet?
Sometimes you have to take a step backwards to take two steps forwards...
Installed a new firmware and ROM (FaaastJB V2) flashed with livesuit. Easy.
Still no TS - when you search for FaaastJB though, you will see a bunch of driver files with adb included in the file so you can just hit run and sit back. I had to reflash a couple of times but very quickly the touchscreen was back.
Still working on the camera but I'm pretty much done.
I hope this helps someone!
PS - I should probably give some props / respect / good karma / shout out to Toxicro, the guy who I believe made faaastJB v2. good work fella!
Final post
Quick last one and that's it from me (at last I hear you cry!)
The new faaastJB - v2.5 includes camera drivers. The same TS drivers work.
Rooted, Rom-ed, working, done!
Godneps out!
I have a T-mobile sgh-t999 that is stuck in boot-loop. I can get into recovery and download modes. The problem started with an unsucccessful root attempt using clockwork mod. After several attempts at fixing, i finally rooted with Chains DD. I enjoyed one day of control and was instructed by "MacTweaker" app to reboot so service could take effect and have not been able to start phone since. There also seems to be a remote-user who is inhibiting my attemps at repair. i dont want to return the phone back to the carrier because of the penalties and charges that may apply. Remote user is a dev with much more knowlegde than myself, and has even infected my home computer through usb from the phone. I was lucky enough to to discover him/her through running trouble-shoot on phone and intercepted a log that had his her "fixes" for my phone that dated Feb. 5, Feb 7, 8, and 9th. These "fixes" included turning up voltage to my kernal, fixing the kernal from "whining about an outdated hack, and states that device will not be able to boot until it receives a reboot signal from a driver a1f2d6. This log also had many referances to clockwork mod with entries like: "Merge clock cm12345 with LED display cm 54321. Run cm 45678 with left handed display...", and many other instances. I believe this dev works for either cwm and is angry i changed to Chains DD, or is employed by Samsung. I tried to save entire log on home computer for further review to have a chance of deciphering and ultimately repairing, but it was "mysteriously" erased from my desktop, AND the FIVE other places I attempted to hide it in: (Folders within folders within folders. Shortcuts to the file within other files, etc.). I am sending this from an internet cafe to try to avoid detection. I've tried to update the drivers but am either not allowed to do so, or the price is more than the the fix. Driver websites also tell me there is an "unknown device" installed on the phone, also. Is there a link that i can download just to reboot the phone? I can download apps to fight once if I could do that. I believe I can fight Big-Brother if i can just get the phone on. PLEASE HELP...
Flash Stock Firmware using Kies.
Huge problem need help urgently
---------- Post added at 12:00 PM ---------- Previous post was at 11:55 AM ----------
[/COLOR]Well I have a Samsung t999 which had a USB problem it charge alright but my MTP wasn't working dunno why.. I figure it was a software problem so tried to flash it with cm11 but I 4got to backup and wiped everything in recovery mode and the cm11 didn't work now my Samsung is stuck in bootloop and I can't use Odin coz my USB cn only charge but not MTP mode... I rli need help... Is there any way I can flash my phone without using Odin... I rli love my phone we been thru alot together... Need help please
Hi all i know someone will not be happy i have asked this question that is probs one of the most asked on here from Nubs like me lol.... Basicly i recently got my rooted htc one m8 S-on back, i was planning to sell it so tried to remove the Root from the phone i have somehow managed to Brick it, its under HTC_001 it didnt have a main fw number so i did what others have and read it from the about software section on my phone wich give me 1.54.401.10....... Well i ended up download that one something went wrong either way now im left with a phone that only goes into Hboot and i can access the recovery what is TWRP i can connect the usb and get onto my Sd card using mount but ive tried and tried to get no joy.... Sorry for the nub questions i did go abit out of my knowledge people say ADB on other forums, im not very clued up with it other than changing the recoverys ive watched youtube vids ect no joy Please can someone give me a Simple Tut or link to help me ive tried following threads and still got no joy http://forum.xda-developers.com/showthread.php?t=2701376 So now i ask the PRO'S please help lol
mikem2273 said:
Basicly i recently got my rooted htc one m8 S-on back
Click to expand...
Click to collapse
Got it back from where???
mikem2273 said:
Sorry for the nub questions
Click to expand...
Click to collapse
No need to apologize for the n00b questions. However, the huge run-on sentences are another story. Take some time to type a post with proper punctuation and sentence structure. It will make it easier for you to get you point across and for us to help.
mikem2273 said:
now im left with a phone that only goes into Hboot and i can access the recovery what is TWRP i can connect the usb and get onto my Sd card using mount but ive tried and tried to get no joy....
Click to expand...
Click to collapse
Tried and tried what? If you aren't specific in what you have done, what are we supposed to do, guess? Be detailed and be specific when asking for help.
You aren't in bad shape at all if you have recovery and can mount SD. Just put a software 1.x based ROM on the SD and flash it in TWRP.
---------- Post added at 01:48 PM ---------- Previous post was at 01:42 PM ----------
mikem2273 said:
people say ADB on other forums, im not very clued up with it other than changing the recoverys
Click to expand...
Click to collapse
Just use the XDA search function, and search "adb beginner" to find a number of good adb/fastboot tutorials aimed at just that, beginners.
But if you've used fastboot to install recovery, the other commands aren't any harder. Its just a matter of just knowing what commands to use for a given situation.
If you can mount SD, I don't even think you need adb. But its a very valuable tool to know, and can help in a lot of situations.
Thanks for the response, well i tried a stock rom im not sure where i went wrong tbh i put it on the internal sd and the file would not show up inTWRP i then had a back up and copied and pasted the files from the Stock rom into the back up and tried to install it and thats where it messed up i am crap at this kind of thing i rooted it no problem i thought unrooting would be easier, adb is a bit confusing with me if there was a way i could put a file onto my sd card in zip format and open it i just tried the original one i downloaded to get loads of red commmads saying
E;unable to stat '/and-sec/;555?.??/m?? and so on a load more random numbers
Sorry i am not very on ball with this should of just left it how it was lol
Right update time...... so i have got the phone back working by flashing a new rom but my phone massively lags on boot up, i think my firmware files are corrupt i cant get wifi either ive red about fixes but all need S-off yet i dont want to pay 25 dollars is this the only way to do this ?? i cant put firmware files on my hone without the s-off such hard work and effort would rather pay someone to fix it lol
unable 2 load my one m8 to fasboot
pls, i av bein unable to access fastboot on my device; i cant unlock bootloader,s-off e.t.c......what can i do; i really need help...
d screen displays black with fastboot mode @ d lower left corner
nnamathy said:
pls, i av bein unable to access fastboot on my device; i cant unlock bootloader,s-off e.t.c......what can i do; i really need help...
d screen displays black with fastboot mode @ d lower left corner
Click to expand...
Click to collapse
Dude ..who are you talking too ?? your post is useless and makes no sense.
Start your own thread ... post an exact description of what you did and whats wrong along with pictures / bootloader / anything that might be of some help
mikem2273 said:
Thanks for the response, well i tried a stock rom im not sure where i went wrong tbh i put it on the internal sd and the file would not show up inTWRP i then had a back up and copied and pasted the files from the Stock rom into the back up and tried to install it and thats where it messed up i am crap at this kind of thing i rooted it no problem i thought unrooting would be easier, adb is a bit confusing with me if there was a way i could put a file onto my sd card in zip format and open it i just tried the original one i downloaded to get loads of red commmads saying
E;unable to stat '/and-sec/;555?.??/m?? and so on a load more random numbers
Sorry i am not very on ball with this should of just left it how it was lol
Click to expand...
Click to collapse
You sentence structure (or lack of it) is still making it hard to understand what you are trying to tell us. If you can't even be bothered to type a proper sentence; how do you expect us to take the time to help you? Honestly, most other requests for help on this forum get much more response. I think many folks are just walking away from this thread without helping, because they can't understand you due to your writing style.
Your lack of specificity also makes it crippling to try to help. What stock ROM, and where did you get it from?
If you got a stock nandroid, you then need to extract the files from the zip and place them in exactly the right folder, otherwise TWRP won't see it. And you do not use the TWRP "INSTALL" function with a stock nandroid, you use the "RESTORE" function.
A flashable ROM zip, in contrast to a nandroid, can be placed anywhere on internal storage or removable SD, and TWRP will see it and flash it using the INSTALL function.
Its very easy to push a ROM zip to the phone with adb. I already told you how to find BEGINNER tutorials on how to use adb. Don't expect to be spoonfed information that is already readily available on XDA. If you have a specific question regarding adb, ask it. Otherwise just saying "adb is confusing" is not going to help you.
---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------
mikem2273 said:
Right update time...... so i have got the phone back working by flashing a new rom but my phone massively lags on boot up, i think my firmware files are corrupt i cant get wifi either ive red about fixes but all need S-off yet i dont want to pay 25 dollars is this the only way to do this ?? i cant put firmware files on my hone without the s-off such hard work and effort would rather pay someone to fix it lol
Click to expand...
Click to collapse
Your firmware files aren't "corrupt". They are just outdated, and don't match the ROM your flashed.
OTAs are available for your version. An option if you don't want to s-off, is to return to stock ROM and recovery, and OTA to update the firmware. It seems you are having problems installing the stock nandroids, but I think you just need to properly follow the instructions from the stock nandroid collection thread.
Otherwise, you are stuck running ROMs that are based on 1.x software. Running anything more recent will result in long boot times and broken WiFI, as you've experienced.
Dammit i know excatly where i went wrong and what you meant by you have to open the file up and adb the right files to the right places............ $%$% i have now fully ruined the phone i think i turn it on i get a White screen the phone then goes full black screen and does nothing...... i have connected the phone via usb to the laptop, the laptop notices the phone and usb i click on the phone in my computer nothing is there when it opens i have also gone onto adb and done the "adb devices" and it does not show on the list, is there anything i can do with this now, i am very gratefull for the help even though i haven't been specific and guessed my way through alot of it like a nob,
adb only works when booted into OS or in recovery.
Alternately, if you have an SD card reader, use it to load a ROM zip onto the SD from your computer. Then place SD in the phone, boot TWRP, and flash the ROM.
redpoint73 said:
You sentence structure (or lack of it) is still making it hard to understand what you are trying to tell us. If you can't even be bothered to type a proper sentence; how do you expect us to take the time to help you? Honestly, most other requests for help on this forum get much more response. I think many folks are just walking away from this thread without helping, because they can't understand you due to your writing style.
Click to expand...
Click to collapse
At this point I have to assume it's an inability to communicate clearly, not an unwillingness. You have a lot more patience than most for even trying.
redpoint73 said:
adb only works when booted into OS or in recovery.
Alternately, if you have an SD card reader, use it to load a ROM zip onto the SD from your computer. Then place SD in the phone, boot TWRP, and flash the ROM.
Click to expand...
Click to collapse
@redpoint73: I'm in his exact same position...hopefully, I can communicate this a little better...at least I'll try. LOL
Background: Rooted, S-Off (via Sunshine), , TWRP 2.8.1.0, was running CleanROM (on the 444 firmware) and tried installing Vanir 444. I did a factory reset and I'm pretty sure I might have went into Advanced and wiped System as well (from the reading I've done, I shouldn't have done that) ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted. When the phone went to reboot, it went to the usual white HTC screen, then went black and never moved past that point.
As you advised in an earlier post, I held down Power/Vol up until the white HTC screen appears. I waited until the screen went black then held Vol down for several minutes but bootloader never came up.
My computer recognizes the phone when I plug it in, Windows explorer shows both "Internal" and "SD card", with Internal basically empty and SD card showing all my files. Since I can't get into bootloader, "adb devices" doesn't bring anything back.
Any suggestions you might have would be hugely appreciated - hoping to avoid having to head to a local Verizon store and see what they can do! If I missed any background or details, let me know and I'll elaborate.
TIA!
sigmaxaa said:
@redpoint73: I'm in his exact same position...hopefully, I can communicate this a little better...at least I'll try. LOL
Click to expand...
Click to collapse
I can't imagine it being any worse than the previous guy!
Seriously though, your post would have been better served in its own thread, or almost any other relevant thread. Couple reasons for this:
1) My experience, when folks say they are "in the exact same position", "I have the same problem", etc. they are in fact virtually never the exact same condition. There are far too many variables (M8 variant, hboot version, software/firmware version, how you got to the current condition, and many more) for your condition to be "exactly the same". And for that matter, when folks say they have the "same problem" it in fact is most often a completely different cause, and different fix. Do yourself a favor, and don't say "me too" when posting a problem.
2) The OP basically chased everyone away with his horrible diction. Help threads in this section normally get considerable traffic and assistance. I'm the only one helping this guy, because apparently I'm the only one patient enough to try to decipher his ramblings. By attaching your post to his, you've pretty much cursed your issue to obscurity as well.
sigmaxaa said:
As you advised in an earlier post, I held down Power/Vol up until the white HTC screen appears. I waited until the screen went black then held Vol down for several minutes but bootloader never came up.
Click to expand...
Click to collapse
If you got this from a post of mine in another thread, its (normally) accompanied with the statement that failure to get into bootloader is virtually always a matter of user error (not getting the timing right). Simply stated, if the screen still comes on, you can get into bootloader. So just repeat the steps until the bootloader screen comes up. You either didn't start pressing vol down fast enough; or let go of it too early (don't let go until the bootloader screen appears).
sigmaxaa said:
My computer recognizes the phone when I plug it in, Windows explorer shows both "Internal" and "SD card", with Internal basically empty and SD card showing all my files. Since I can't get into bootloader, "adb devices" doesn't bring anything back.
Click to expand...
Click to collapse
Once you get the timing right to get into bootloader, and from there recovery, we should be in good shape.
You can likely recover by transferring a known good ROM to the SD card, and just flashing from custom recovery. Or just restore your nandroid.
sigmaxaa said:
Any suggestions you might have would be hugely appreciated - hoping to avoid having to head to a local Verizon store and see what they can do!
Click to expand...
Click to collapse
I doubt Verizon can help. And since the phone was put into this situation by your own actions (mods you performed) its really your responsibility to fix it, not theirs.
redpoint73 said:
I can't imagine it being any worse than the previous guy!
Seriously though, your post would have been better served in its own thread, or almost any other relevant thread. Couple reasons for this:
1) My experience, when folks say they are "in the exact same position", "I have the same problem", etc. they are in fact virtually never the exact same condition. There are far too many variables (M8 variant, hboot version, software/firmware version, how you got to the current condition, and many more) for your condition to be "exactly the same". And for that matter, when folks say they have the "same problem" it in fact is most often a completely different cause, and different fix. Do yourself a favor, and don't say "me too" when posting a problem.
2) The OP basically chased everyone away with his horrible diction. Help threads in this section normally get considerable traffic and assistance. I'm the only one helping this guy, because apparently I'm the only one patient enough to try to decipher his ramblings. By attaching your post to his, you've pretty much cursed your issue to obscurity as well.
If you got this from a post of mine in another thread, its (normally) accompanied with the statement that failure to get into bootloader is virtually always a matter of user error (not getting the timing right). Simply stated, if the screen still comes on, you can get into bootloader. So just repeat the steps until the bootloader screen comes up. You either didn't start pressing vol down fast enough; or let go of it too early (don't let go until the bootloader screen appears).
Once you get the timing right to get into bootloader, and from there recovery, we should be in good shape.
You can likely recover by transferring a known good ROM to the SD card, and just flashing from custom recovery. Or just restore your nandroid.
I doubt Verizon can help. And since the phone was put into this situation by your own actions (mods you performed) its really your responsibility to fix it, not theirs.
Click to expand...
Click to collapse
Thanks for the reply, I do appreciate it. I was able to get it working (after dozens of attempts) and you're absolutely correct...it's all in the timing.
Whenever I try to connect it to my pc, it only charges but the option for mtp/ptp is not showing up. It's also not recognized by adb even though I enabled USB debugging. I tried reconnecting, reinstalling drivers but to no avail. Is this already a hardware failure or can I still do something about it?
notinthemood said:
Whenever I try to connect it to my pc, it only charges but the option for mtp/ptp is not showing up. It's also not recognized by adb even though I enabled USB debugging. I tried reconnecting, reinstalling drivers but to no avail. Is this already a hardware failure or can I still do something about it?
Click to expand...
Click to collapse
Does your phone still charge slowly from PC ? Does the charge light light up ?
Could be data cable became faulty and now only charges if it does.
Could be USB board.
Could be drivers.
Could be a windows update blocking your drivers.
Many things that only you can possibly try to possibly resolve but
1) first try a new data cable and another pc
timbernot said:
Does your phone still charge slowly from PC ? Does the charge light light up ?
Could be data cable became faulty and now only charges if it does.
Could be USB board.
Could be drivers.
Could be a windows update blocking your drivers.
Many things that only you can possibly try to possibly resolve but
1) first try a new data cable and another pc
Click to expand...
Click to collapse
The phone still charges, but really slow. Even though I only have the screen on, the battery level actually goes lower. The charging LED does light up.
I tried several cables already but to no avail. I will try connecting on my laptop and see how it goes.
notinthemood said:
The phone still charges, but really slow. Even though I only have the screen on, the battery level actually goes lower. The charging LED does light up.
I tried several cables already but to no avail. I will try connecting on my laptop and see how it goes.
Click to expand...
Click to collapse
How did it go ?
timbernot said:
How did it go ?
Click to expand...
Click to collapse
Well, it still did not read my phone. Installed the drivers first before connecting, tried other ports, other cables, but still not working. Also, when I try to charge it when open, it doesn't have the LED light on. But if it's turned off, it shows the LED.
@notinthemood
Now would be the ideal time to give details of IFWI version in Bootloader , build , date in settings etc .
Hopefully it is firmware problem now
And not USB board , or USB port attached to it , ugh !
I had this after MM came out and I tried everything to the point where I thought my usb port was broken.
I ended up completely wiping my phone (Internal memory too), then re-flashed MM firmware via ADB and it was fine.
Suspect I had a downloaded a dodgy/corrupt mod and it wiped part of the OS code for USB or just killed USB?
mckc001 said:
I had this after MM came out and I tried everything to the point where I thought my usb port was broken.
I ended up completely wiping my phone (Internal memory too), then re-flashed MM firmware via ADB and it was fine.
Suspect I had a downloaded a dodgy/corrupt mod and it wiped part of the OS code for USB or just killed USB?
Click to expand...
Click to collapse
Best and easiest method for future reference to rule out software , if in full stock M and providing a factory reset didnt suffice , is a simple official downgrade via ext sd , flashing the official downgrade version - NO PC required If problems then persist ,then it would be definately be hardware after.
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
If @notinthemood could follow if in stock M , this would be ideal to rule out software :good:
Here are some of the details of my software in the settings. Tell me if you need more. http://imgur.com/a/Ynl2J
notinthemood said:
Here are some of the details of my software in the settings. Tell me if you need more. http://imgur.com/a/Ynl2J
Click to expand...
Click to collapse
WOW you are in LP over a year old .
Download LP .198 last of the LP firmware to interna memory l> UL-WW LP 2.20.40.198 from asus and reboot :good:
When set up -- factory reset in settings immediately -- see if probs persist:good:
---------- Post added at 02:51 PM ---------- Previous post was at 02:47 PM ----------
@notinthemood >
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.198-user.zip
Have you tried to go in devoloper settings and "Select USB configuration"?
timbernot said:
WOW you are in LP over a year old .
Download LP .198 last of the LP firmware to interna memory l> UL-WW LP 2.20.40.198 from asus and reboot :good:
When set up -- factory reset in settings immediately -- see if probs persist:good:
---------- Post added at 02:51 PM ---------- Previous post was at 02:47 PM ----------
@notinthemood >
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.198-user.zip
Click to expand...
Click to collapse
Oh wait. Does that work on custom ROMs? It isn't really stock but rather a cleaned up rom.
notinthemood said:
Oh wait. Does that work on custom ROMs? It isn't really stock but rather a cleaned up rom.
Click to expand...
Click to collapse
Hence why i asked earlier your IFWI version , it would`ve determined your bootloader status being unlocked , since you never answered i assumed you wasnt unlocked !
When people try to help , its best you answer the questions to your best ability .
So , next questions are... do you have TWRP recovery ? is your IFWI version in bootloader 0094.0173 ?
If the answer is yes then --> try this.....AT your OWN risk ...as always !
https://forum.xda-developers.com/showpost.php?p=70780400&postcount=26
---------- Post added at 06:00 PM ---------- Previous post was at 05:51 PM ----------
Original post reads ;-
Whenever I try to connect it to my pc, it only charges but the option for mtp/ptp is not showing up. It's also not recognized by adb even though I enabled USB debugging. I tried reconnecting, reinstalling drivers but to no avail. Is this already a hardware failure or can I still do something about it?
What it should say is;-
I have these problems with a year old custom rom !
And the answer is quick and simple, >Flash back stock rom back up , Update and see if probs persist !
timbernot said:
Hence why i asked earlier your IFWI version , it would`ve determined your bootloader status being unlocked , since you never answered i assumed you wasnt unlocked !
When people try to help , its best you answer the questions to your best ability .
So , next questions are... do you have TWRP recovery ? is your IFWI version in bootloader 0094.0173 ?
If the answer is yes then --> try this.....AT your OWN risk ...as always !
https://forum.xda-developers.com/showpost.php?p=70780400&postcount=26
---------- Post added at 06:00 PM ---------- Previous post was at 05:51 PM ----------
Original post reads ;-
Whenever I try to connect it to my pc, it only charges but the option for mtp/ptp is not showing up. It's also not recognized by adb even though I enabled USB debugging. I tried reconnecting, reinstalling drivers but to no avail. Is this already a hardware failure or can I still do something about it?
What it should say is;-
I have these problems with a year old custom rom !
And the answer is quick and simple, >Flash back stock rom back up , Update and see if probs persist !
Click to expand...
Click to collapse
Oh my, sorry about that. I don't know how to check the IFWI version so I assumed that it's on the about page in the settings. And yes I do have TWRP.
All OK now ? Fixed ? Reboot to bootloader for IFWI version, you are on a year old custom ROM so IFWI should be what I stated earlier anyhow.
Just had a check at your recent posts
You are a maintainer for another device it seems , strange you have not sorted this out already
timbernot said:
All OK now ? Fixed ? Reboot to bootloader for IFWI version, you are on a year old custom ROM so IFWI should be what I stated earlier anyhow.
Just had a check at your recent posts
You are a maintainer for another device it seems , strange you have not sorted this out already
Click to expand...
Click to collapse
IFWI version is 0094.0177. Would it still be fine to flash that stock rom?
I actually misplaced this phone for almost a year. Just found it again and it's a mess but I still want to use it since it is a powerful device.
@notinthemood
Restore your back up first . A maintainer of another device surely knows the basics ?????
I'm pretty sure .0177 is locked bootloader, maybe my mind is playing tricks on me and .0173 is and 0177 is unlocked ,
If you have root , does it function OK ?
Maybe , with the device being over a year old , use Asus bootloader unlock app to be on the safe side.
Even so , sounds all very strange to me
Goodluck
timbernot said:
@notinthemood
Restore your back up first . A maintainer of another device surely knows the basics ?????
I'm pretty sure .0177 is locked bootloader, maybe my mind is playing tricks on me and .0173 is and 0177 is unlocked ,
If you have root , does it function OK ?
Maybe , with the device being over a year old , use Asus bootloader unlock app to be on the safe side.
Even so , sounds all very strange to me
Goodluck
Click to expand...
Click to collapse
Root functionality is fine. Reinstalled Greenify and it asked for root access and I was able to grant it. Also, I used Asus official bootloader unlocker before. The white background when booting confirms that it is unlocked, right?
Also, I already have restored its backup. I thought that would fix the problem but it didn't.
notinthemood said:
Root functionality is fine. Reinstalled Greenify and it asked for root access and I was able to grant it. Also, I used Asus official bootloader unlocker before. The white background when booting confirms that it is unlocked, right?
Also, I already have restored its backup. I thought that would fix the problem but it didn't.
Click to expand...
Click to collapse
OK follow that link I posted , the reply I put there applies to you here also
timbernot said:
OK follow that link I posted , the reply I put there applies to you here also
Click to expand...
Click to collapse
Alright. Will update you later once I finish the process.