Related
Hey guys,
I tried getting some help for this over at the Nook Color threads because it all started *after* i rooted my NC, but no one's been able to explain to me what Ive done wrong or whats happened...
So here's the sitch.
o I have ADB installed, but it only activates in device manager when the nook is plugged in, not the G2
o When the NC get usb'd to the PC, it fully registers and gives me access to the SD card on it
o .... where as the G2 just sits there and says "yay im getting power!"
o ,,,, BUT if i plug it into a HUB rather than directly into a usb port on the mobo or front, the PC (win7 x64 ult) seems to see it but doesnt know how to properly assign a driver to it and gives it UNKNOWN
o also i checked the usb-adb ini file, and it lists all my other devices in the hardware cues BUT the G2, which means it hasnt properly registered since then or never had a proper profile to begin with in the PC. It even has my older mt3G listed which I havent plugged in since all this started.
Ive tried multiple driver types, but literately, NOTHING has worked. Its like the G2 isnt even properly registering in the computer when connected. I tried a factory reset, but still no luck. Is there anything beyond a soft fact reset for an unrooted phone? I mean, i need COLD AS STONE back to day 1 reset.
Please help, I really want to root this :'<
and no, the only way now to access my sd card is to turn the thing off and use a reader. Like i said, it literately is NOT seeing it :<
Wrong section. Ask in the Q&A, not the DEV section.
Try installing HTC Sync, even though it doesnt work with the G2 because its sense based, it will install the proper drivers for you. This worked for me.
Heres the link:
http://www.htc.com/www/SupportViewNews.aspx?dl_id=1058&news_id=804
Another method would be install pdanet on you phone fron the Market, then install pdanet for your computer from here and it should install the drivers when you plug your phone in with pdanet app running:
http://www.junefabrics.com/android/
I tried the Sense link, but I couldnt find the download option for it.... anyways, heres a more precise description of the issue
When I go and install PDA Net, it loads up the drivers, but the computer literately is not even registering that a DEVICE has been plugged in via USB. I dont even get the USB connect prompt on the phone!
That's what Im saying, something is up. I need to take the cable with me and try this on another computer now that I think about it to rule out that something isnt damaged on the phone...
What ROM are you using? Gingerbread ROM's act like the (for now), at least from what I understand. I tried CM7 and sure enough - it acted just like what you're describing.
KCRic said:
What ROM are you using? Gingerbread ROM's act like the (for now), at least from what I understand. I tried CM7 and sure enough - it acted just like what you're describing.
Click to expand...
Click to collapse
But thats the whole thing, im not using a ROM, its just the stock OS build. if i was using a ROM, id have tried removing it and reloading it, but this is on a phone that isnt even rooted yet... actually... should I try going temp root again and see if that fixes anything?
Whats the best way to do that now since I keep reading Vision got pulled away because it was damaging phones or something?
Okay, so i tried plugging it into a diff computer.... same result... so whatever it is, its the phone.
Any ideas XDA pplz?
Has it seen the g2 before? if so, get usbdeview, find the drivers in there that would be used for the g2, delete those. Snag PDANet and download that, plug the phone back in and see what ya get. You will get the pop ups again about the new software being loaded since it will have to find and reload drivers for the phone and PDANet will have the drivers you need.
K41N2358 said:
Okay, so i tried plugging it into a diff computer.... same result... so whatever it is, its the phone.
Any ideas XDA pplz?
Click to expand...
Click to collapse
Like the guy above me said, DL or re-DL the drivers (though none should be needed if you're using it as a storage drive, the comp sees it as a usb drive). Is it charging your phone when you plug it in? It's rare, but the USB cable may be bad.
The only other thing I can think of is that something went wrong and the phone isn't releasing the mount to the sdcard, in which case you should try rooting and using a different ROM or a stock rom and it should help.
Well thats the whole thing, the computer doesnt even see the USB part of it. Thats been my whole issue. The computer doesnt see the phone or the usb drive part. It straight does not see the phone at *all*! Doesnt even show up in Dev Manager, but yet it gets power. I even went and got a new micro USB cable, fresh, and still nothing.
im getting to 86 the os and reload Win7, im like super uber pissed over all this because i cant figure it out. I dont even know whats wrong >_<!
Just for kicks (because I had this exact thing happen to another phone of mine - the slide) you're rooted, which means you have clockwork right?
Reboot into recovery and go to the 'mounts' part and select 'mount usb'. Do that with it plugged into your computer and let me know if the phone shows up then. That's the only way I could put it in mass storage mode. I flashed something other than cyanogen's rom and BAM, it worked like it was supposed to (Linux did mount cyanogen though - weird).
If you want to go back to 0 day with your G2, search 'PC10img' and download it. DO NOT FLASH IT YET, you could really screw up your phone since you have s-off. Go to the wiki and scroll to the bottom, it tells you how to get s-on. Once you can verify that you have s-on, proceed to flashing the pc10img.
Wiki
Okay, so, Im way better now. Apparently I managed to get s-off and root ability via
http://forum.xda-developers.com/showthread.php?t=837315
when i reloaded and got rooting ability, somehow, I now have a detectable sd card again.
I dont know how, I dont know why, I just know that Im going to throw CM6.1.1 onto this thing and be rocking it hard
Thanks again for all your help guys, it was awesome to know XDA really helps out its followers
EDIT:
Okay... so now Im mixed. I have a rooted phone, with CM6.1.1, but still doesnt properly recognize when plugged into the PC.
oh well, I already called TMobile and their sending me a new phone under warranty. Its gotta just be a busted port in some way for detection. I dunno. >_<
But still, thanks a lot guys. Means a lot
OK, I posted in the Q&A section, but not finding much love. Hopefully someone here might be more help.
The first thing to put out there is that I did not accept the Gingerbread OTA. Still on 2.2.
Here's the story: A couple of days ago I tried running unrevoked on my Evo. One month old, HW version 0004. I'm pretty sure I did everything as instructed, but the procedure failed. Machine would run for 30 seconds or so then drop into diagnostic mode (5 vibrations & lock).
So I tried re-flashing back to stock. The first stock image I tried screwed the phone up in that: (1) it would no longer see USB connections (2) no longer saw my Micro SD card (3) would no longer charge when the phone was on.
So I tried flashing a newer stock image, the third one on this page:
http://forum.xda-developers.com/showthread.php?t=884060
That only made matters worse, as now I've lost bluetooth, too.
Keeping in mind that I cannot communicate with the phone via USB (unrevoked now just keeps waiting for me to plug the phone in, as does HTC Sync, which I installed after everything else as a last shot) and am not rooted, what are my options here? I really want to get this device back to stock, because I need a phone that works.
If I take it back to a Sprint repair store will they even look at it? Can they flash it back to stock for me or am I SOL there?
I've been thinking that I could let the OTA install and if everything's still broken take it to Sprint and tell them the OTA screwed up my phone, but I'm worried I've left traces that would tell them I'm bullshitting.
Hell at this point I'm willing to pay $$ to get this thing fixed, motherboard swap or whatever, but I'm not sure Sprint will even do that.
Gotta have my phone back guys, any help greatly appreciated.
Let me clarify... So at the moment you have a version of a stock rom on the phone, and it will actually turn on?
However, you can't "connect" per se to the phone?
You could either email yourself the files you need or use "Awesome Drop"
OR
I've read that if you've bricked or screwed your phone around the time of an OTA happening to come out, you can go to Sprint and tell them you tried to accept the OTA update, Make up some BS about blah blah blah, and then you're left here with a phone that's acting really weird and is borked.
Generally the tech will re-flash as they are familiar with the issues OTAs can cause.... Or they may give you a refurb.
TF1984 said:
Let me clarify... So at the moment you have a version of a stock rom on the phone, and it will actually turn on?
However, you can't "connect" per se to the phone?
You could either email yourself the files you need or use "Awesome Drop"
OR
I've read that if you've bricked or screwed your phone around the time of an OTA happening to come out, you can go to Sprint and tell them you tried to accept the OTA update, Make up some BS about blah blah blah, and then you're left here with a phone that's acting really weird and is borked.
Generally the tech will re-flash as they are familiar with the issues OTAs can cause.... Or they may give you a refurb.
Click to expand...
Click to collapse
I'm not rooted, though, so I doubt any files I could e-mail myself would do any good.
I am considering taking the phone back to Sprint, but I don't know whether to accept the OTA then make up some story about losing Bluetooth, SD Card access and USB, or just being honest and telling them what I did.
At this point I just want to get my phone back to stock and working as it should. I'll leave the rooting adventures to others. Rooting my Nook Color is one thing, since it's basically a $250.00 toy, but I can't live without my phone.
Try this:
http://forum.xda-developers.com/showthread.php?t=695243
However, will need root to fix the USB problem. You should look into some temp root options that will allow you to use a terminal emulator to fix the USB issue. I've never tried a temp root method, so you're going to have to do some digging around for that. Maybe someone who knows more about temp root can chime in and help.
You could start one of two ways...
Either email yourself the S-Off and Recovery Image files, move them to proper place
Or take it to Sprint. Just tell them teh OTA messed something up. Don't think up a whole world of stories or truths. Trust me, they're used to it.
TF1984 said:
You could start one of two ways...
Either email yourself the S-Off and Recovery Image files, move them to proper place
Or take it to Sprint. Just tell them teh OTA messed something up. Don't think up a whole world of stories or truths. Trust me, they're used to it.
Click to expand...
Click to collapse
So, accept the GB OTA, then?
My Sprint store is also a repair facility. Do they have hardware and tools that can re-flash the device to stock regardless of what you've done to it? because that's what I'm thinking of doing at this point.
My biggest problem with attempting to fix it myself is that not being rooted and not having USB access I seem to be SOL.
BTW: I just testes WiMax and it works, so at least my WiMax key is good.
Will your phone recognize the SD at all? If you can get another card to work, you could theoretically run a PC36IMG of the RUU through the bootloader. However, you'll need your SD card working. If your computer will recognize it but the phone won't, you can try backing up the contents, then formatting/partitioning the card. Then move just the PC36IMG to the card, boot into the bootloader, and hopefully it'll ask you to update.
If you can't get anything to work, then download the OTA and start installation. The OTA may fix it... but probably not. If it does fix it, hooray!, but you're stuck without root until an exploit is found. If it doesn't fix it, take it into Sprint and tell them you took the update and your phone is acting funny. Technically if you word it that way, you're not lying
If the card can't be recognized, don't worry about the files on it. If it can, just delete any PC36IMGs or other files related to rooting/troubleshooting. Other than the SD card, there shouldn't be any way to tell you attempted to root as long as you're s-on & cannot access recovery.
If you don't have insurance, I'm not sure how Sprint will handle it. If you do, they should either fix it or replace it for free.
(from... Evo/MIUI/Tapatalk)
plainjane said:
Will your phone recognize the SD at all? If you can get another card to work, you could theoretically run a PC36IMG of the RUU through the bootloader. However, you'll need your SD card working. If your computer will recognize it but the phone won't, you can try backing up the contents, then formatting/partitioning the card. Then move just the PC36IMG to the card, boot into the bootloader, and hopefully it'll ask you to update.
If you can't get anything to work, then download the OTA and start installation. The OTA may fix it... but probably not. If it does fix it, hooray!, but you're stuck without root until an exploit is found. If it doesn't fix it, take it into Sprint and tell them you took the update and your phone is acting funny. Technically if you word it that way, you're not lying
If the card can't be recognized, don't worry about the files on it. If it can, just delete any PC36IMGs or other files related to rooting/troubleshooting. Other than the SD card, there shouldn't be any way to tell you attempted to root as long as you're s-on & cannot access recovery.
If you don't have insurance, I'm not sure how Sprint will handle it. If you do, they should either fix it or replace it for free.
(from... Evo/MIUI/Tapatalk)
Click to expand...
Click to collapse
When boot into the bootloader and choose "restore" it does recognize the SD card. That's how I managed to flash this image (third klink on page) and get back to stock:
http://forum.xda-developers.com/showthread.php?t=884060
So it's definitely a software issue with the phone preventing me from seeing the card/USB or connecting to bluetooth.
At this point I don't mind not being rooted. Having a working phone is more important.
And unfortunately I don't have insurance, but I'll pay the repair fee if they ask me to.
dsf3g said:
When boot into the bootloader and choose "restore" it does recognize the SD card. That's how I managed to flash this image (third klink on page) and get back to stock:
http://forum.xda-developers.com/showthread.php?t=884060
So it's definitely a software issue with the phone preventing me from seeing the card/USB or connecting to bluetooth.
At this point I don't mind not being rooted. Having a working phone is more important.
Click to expand...
Click to collapse
Did you try the SD card fix I posted above? I think with the SD card fixed and temp root you'll be able to fix both problems.
rugedraw said:
Did you try the SD card fix I posted above? I think with the SD card fixed and temp root you'll be able to fix both problems.
Click to expand...
Click to collapse
Thanks, I'll try that. I saw that thread earlier, and I just noticed that someone answered my question about fastboot. So I'll see if I can fix USB using that.
What really bugs me now is the lack of Bluetooth!
XDA search is down right now so I can't see if there are any others who have experienced this.
Please note that with the link I gave you, you can fix the SD card not being detected issue, but to fix the USB port using those instructions, you need root. Since Unrevoked won't work without the USB, you would have to either try a temp root method (I've never used it so I can't offer you much help there) or some other manual root method where the USB port isn't needed.
Step 1, Go into Device Manager
Start Device Manager.
Windows 7
Click Start > Control Panel > System and Security > Device Manager. Windows Vista
Click Start > (Settings) Control Panel > (System and Maintenance) > Device Manager. Note If prompted, click Continue. Windows 2000 / XP
Click Start > (Settings) Control Panel > (Performance and Maintenance) > System > Hardware > Device Manager.
Step 2, These Devices are typically installed when you Install HTC Sync or Just connect your Android Device, If their are no conflicts uninstall all of them and restart your PC, Then Reconnect your android Device
The following devices are normally installed:
If a red X, yellow ! or yellow ? is displayed to the left of a listed device, a conflict is present and the drivers must be updated or reinstalled.
Note Driver conflicts may also be indicated by a device entry labeled Other Devices or Unknown.
Android USB Devices
My HTCDisk drives
HTC Android Phone USB DeviceModems
HTC Modem (if using as a tethered modem)Portable Devices
E:/ (Where E represents the assigned drive letter.)Universal Serial Bus controllers
USB Composite Device USB Mass Storage Device
kingakuma said:
Step 1, Go into Device Manager
...
Click to expand...
Click to collapse
Thanks, Kingakuma, I'll try that, but I don't think the problem is on the PC side. My Evo won't recognize the charger when it's plugged in, so I'm pretty sure the issue is on the Evo.
dsf3g said:
Thanks, Kingakuma, I'll try that, but I don't think the problem is on the PC side. My Evo won't recognize the charger when it's plugged in, so I'm pretty sure the issue is on the Evo.
Click to expand...
Click to collapse
are you using the same usb cable for the charger?
if so try a different usb cable
so rom boots but somethings just do not work correct? bluetooth and usb and sdcard correct? follow the above advice to fix sdcard as mentioned then download z4root from here, to try and root since you are still on froyo temp root should work, at which point download rom manager. use rom manager to install either clockwork or amon ra recovery, boot to recovery, flash rom, profit!
link for z4root
http://forum.xda-developers.com/showthread.php?t=833953
DomSim said:
so rom boots but somethings just do not work correct? bluetooth and usb and sdcard correct? follow the above advice to fix sdcard as mentioned then download z4root from here, to try and root since you are still on froyo temp root should work, at which point download rom manager. use rom manager to install either clockwork or amon ra recovery, boot to recovery, flash rom, profit!
link for z4root
http://forum.xda-developers.com/showthread.php?t=833953
Click to expand...
Click to collapse
Thanks, but how can I download or install this without an SD card mounted?
dsf3g said:
Thanks, but how can I download or install this without an SD card mounted?
Click to expand...
Click to collapse
ok, we can't help you if you do not follow directions. read my post, and those of the others who posted. one contains a link to a thread to fix the sdcard. you have been told to do this several times. i told you to do this first then get z4root. im done helping you, good luck.
Use z4root in order to achieve temp root for previous mentioned fixes.
Wohooo! I've fixed the SD Card issue! Thanks all, even DomSim, who's apparently given up on me in frustration. Give a noob a break, DomSim. I'm new to all this and am trying to balance reading this stuff with a family that also needs my attention.
I've got Z4Root installed and verified root, too. I'll probably fix the USB issue at work, since I don't need a computer connection for that and it's getting late (yeah, I usually leave for work just after 5:00 AM).
Once I've got the USB issue sorted I'll have to take a look at the bluetooth issue. I'm hoping its related to the USB situation and will be cured at the same time, but suspect that's just wishful thinking on my part.
Just completed the USB repair portion and.... SUCCESS!!!!! BEYOND MY WILDEST DREAMS, actually, as Bluetooth now works also.
I was hoping that the bluetooth functionality depended on USB (I think I recall that the bluetooth module on my Dell Mini 9 was USB based) and lo and behold, it does!!!!
Thanks again to everyone who helped out. You guys are first class!
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
have you given a look at this thread? http://forum.xda-developers.com/showthread.php?t=2711825 it might give you some ideas to help you out. also did you try flashing a new recovery to see if you could at least get it to boot to that?
dont care about the bounty just trying to toss something out there that may help you
Did you ever try flashing the stock recovery - JUST the stock recovery - through Odin?
If not, grab the recovery.img and make your own tarball for Odin in Linux.
Hopefully that will flash and get you closer.
eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
...
i have access to both windows and ubuntu linux if it makes a difference.
Click to expand...
Click to collapse
Since you mentioned Ubuntu, you can also try using heimdall instead of odin... http://glassechidna.com.au/heimdall/ . Unfortunately, I think it may be a hardware problem?
Since you are willing to pay to have it fixed, if all else fails, you can always send it off to http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-jtag-brick-repair/. It will actually be cheaper than what you are offering to pay ~$40 + shipping
good luck
Thanks all for your help, I've messed around and gotten no closer. I'm beginning to lean on a hardware failure, perhaps from the usb data port either that or the way bootloaders are packaged in kitkat 4.4 is different. which is why initially this thread gave me hope: http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096 but i tried far too many times now to believe I'm going to succeed. In fact, I've gotten confused as to what i tried, in which order, with which rom. I'm basically trying anything and that's a recipe for bricking the phone for good. so i've stopped.
I'll also thank kozmo21 for the link to the repair shop. i was unaware this existed, as a last resort I'll be sending them my phone. If it turns out they are able to repair it, I'll honor my word and give you something for having been part of the solution.
eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
Click to expand...
Click to collapse
Have you tried going to sammobile and download the newest firmware and only flashing that in odin?
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
ShrekOpher said:
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
More than likely its a bootloader issue my phone did that and all i did was flash the bootloader then it worked again but hes done so much idk what he needs now that's y i said to try a firmware to see if that helps
Download toolkit and select option to push file into phone.
Download a ROM of your choosing, push it into your phone, restart in recovery mode and select file.
Update?
Did you get it fixed? Just my two cents, in case you didnt, I had a similar problem and alll I did to fix it was flash the JediMasterX2 ROM with CWM and everything worked out.
Hi,
So I have a rather unheard of problem. I was given a phone from a friend before they moved out of state and have no way of contacting them anymore. I turned it on and it had a pass code so i just figured i would do a factory reset ( or what i assumed to be a factory reset) using the buttons on the phone. I used the recovery menu to get to the screen that gave me the options to wipe data, or install update from apk, or factory reset the phone so i used the volume buttons and clicked reset. I let the phone do its thing and when it turned back on it goes to the google factory reset protection page saying i need to login using a google account that was previously used on the phone before the reset. FML! i used the talk back option to be able to access the settings menu and figured i would just do the reset from the settings menu. This is were all of my problems begin!! I can access the settings menu and get to the back up & reset and then click the the Factory reset option. However, the factory reset screen has a button at the bottom of the screen that says Reset Phone and when I click the Reset phone button, absolutely nothing happens. (It makes a click sound but it doesn't do anything at all)
The Other Problem!!: For some unknown reason i cant seem to access the developer options and enable USB debugging. even after i put the phone in safe mode i still could not get the developer options to appear. I have no clue what i am doing wrong but i feel like i am running into a brick wall and not matter what i click or press the phone just will not do what it is suppose to do! I tried every way I can think of to enable USB debugging but, no matter how many times I try to click Build Number or Build Version ( whatever it is exactly called, hopefully you can understand what I mean) nothing happens! I have tried to install a USB debugging app from a qr code but it won't read the qr code from the camera app. I was able to access the camera app using the same talk back trick that i used to get into the settings. I keep telling myself if only i knew about the talk back trick to get into the settings menu before i stupidly reset the phone when i first saw the pass code. So I am hoping that a google FRP Bypass program will work and help me make the phone usable again!! Does anyone have any suggestions or advice?? I am open to all ideas.
So far i have come up with a few ideas but idk if any of them are even possible to accomplish! Can someone help me out and tell me if any of the following options are even possible and whether or not it will be helpful and make the phone usable so i can have a cell phone again. Please, Please can someone help me!! Ideas:
1.) Use a Google Factory Reset Protection Unlocking program.
2.)Somehow completely delete the entire phone and reinstall the marshmallow android OS, like when you would do a fresh clean install of windows on a PC, (IDK if this is even possible but i am assuming it should be)
3.) Rooting the phone and finding a new custom ROM. ( I haven't even done anything like or close to rooting a phone, but im guessing it cant be that hard, right? Google and YouTube have vast amounts of tutorials........, hopefully,....right?
4.) I have backups of my older phones that i am wondering if it would be possible to use one of the backups i have saved and somehow putting it on the phone as a way to get pasted the FRP lock? I haven't a clue if the backups are only usable to the specific phones that created them or if they can be used on any phone?
5.) Downgrade the Android version to a older version that doesn't have the FRP lock, then once i have access into the phone i can just upgrade the phone after i logging into my google account.
6.) You know how Windows PC have the restore option in the settings so you can go back to a previously made restore point? Like turning back the clock so to speak, Is this option available or does it even exist at all on Android? I was thinking if it does i can just simply store the phone back to before i stupidly reset it and then use the trick to bypass the screen lock code and use the settings to do a hard reset ( I really don't think this option even exists or is possible but im literally at the point of willing to try and do absolutely anything to be able to have a phone again! Please and thanks! It is a ZTE Z837VL and it is Android marshmallow, Android Version 6.0.1 (I'm not sure if the
Android version matters or not?)
Thanks. Also If this is the wrong place for this post then please just let me know where the correct spot is to post and i will quickly fix it!! I am new to the site and I have read alot of posts and truthfully, feel like i have overwhelmed myself with trying to make sure i do things the way its supposed to be done. I know many most likely ALL of the members on this site are advanced and way more knowledgeable about the mobile phone information. I do know alot of computers and I have alot of programming experience but i have only focused on PCs and am just starting to learn what i can about mobile development.
Thanks again for helping me and sharing whatever you can with me to help solve things. I am really hoping not to end up with a paperweight haha!!
Alyson
Hi
I have a problem rooting my phone.
Thing is that it is my company phone which is supervised by snowsoftware.
We are allowed to use it as an private phone aswell but since it is able to track like everything I do... You know...
Anyway, I've tried to do a factory reset but when I restart it afterwards it still wants me to log into snow before moving on...
I have also used Odin with Albvirals firmware and combination files with same result!
Is there anyway to get rid of this annoying software with some kind of deeper operation?
I hopte that some of you expert can help me!
Airborne972 said:
Hi
I have a problem rooting my phone.
Thing is that it is my company phone which is supervised by snowsoftware.
We are allowed to use it as an private phone aswell but since it is able to track like everything I do... You know...
Anyway, I've tried to do a factory reset but when I restart it afterwards it still wants me to log into snow before moving on...
I have also used Odin with Albvirals firmware and combination files with same result!
Is there anyway to get rid of this annoying software with some kind of deeper operation?
I hopte that some of you expert can help me!
Click to expand...
Click to collapse
Anyone??!!