Related
Hi guys and girls.
New to XDA but not to Android.
I need some help big time as I'm totally stuck and I'm about to send my phone to "will it blend".
Long story short my memory card will not read when inside the phone all I get under phone storage is "unavailable" with mount being greyed out.
HTC DESIRE HD 2.3.3 (Not Rooted)
Things I have tried:
Factory reset soft/hard both through phone and through power + vol down.
Tried two different mem cards both coming up in storage as "unavailable" the general fix seems to be formatting in fat32 on desktop pc I have done that for both cards (which are both readable on PC) and have even tried formatting through command prompt still no luck.
read alot in ADB/fastboot as it is something I'm abit unfamiliar with saw that users where able to restore sd card function by installing adb then running command prompt: "fastboot oem enableqxdm 0" I get a message saying it was successful I reboot guess what...same problem. One thing I have noticed is if I type "adb shell" I get "Daemon started on port 5079". (I have enable debugging) followed by device not found. have tried two diff usb cables both work with my S2 on either media faceplate or backplate usb ports still no luck. Trust me on this one guys I have searched far and wide and I'm just about read to quit on this. I'm at a dead end any advice would be awesome.
I've tried to resolve the adb method by installing various drivers (running windows 7pro 64bit) the issue I seem to get is that windows doesnt like the drivers Im trying to assign so im forced into have to update them manually through "let me choose a driver from location" blah blah blah...
There is a system update available which may possibly fix my issue however suprise suprise I can't download the update without having an sd card. I have even tried downloading a HTC sdmount widget whether Im downloading the wrong one I dont know? I have got HTC sync installed as others claimed this helped windows detect the correct drivers but then technically speaking its not an ADB interface?? just like to point out that both of the sd cards work flawlessly in my s2. anyone who can help me will get paypal'd a beer!
Thanks
Seb.
OK, I had same problem with my Desire S. I'm running Win7 64bit as well. I un-installed HTC sync, including the drivers. Control Panel>Programs & Features. I then download the latest HTC sync. Went back to Programs & Features and un-installed HTC sync but, left the drivers. Rebooted PC and Win7 picked up Desire S.
Hope this helps
How old is your phone? Depending in which country you are in you may still be under warranty.
Try cleaning the contacts?
Not too sure if you can mount the sd card on phones that are not rooted, or if you have the hboot option/recovery. Fastboot turned off, phone off, then press and hold the down volume button and while pressing it down, press the power button.
If you are not sure what you are looking at do not play around with those options, and it may not work. Not sure if you get those options if you are not rooted.
Do not root your phone, it is improbable it will help, and chances are, it may cause more problems than help.
First option, find out about the warranty.
Edit: just noticed you can boot into hboot. Not too sure if you have the option for recovery and even less if you get the option to mount sd card through there.
2nd edit: I'm not responsible for bad advice. I still haven't had my second cup of coffee
3rd edit: to find out if the adb is working properly and you got the htc sync installed type in whatever the command is in adb to see if it detects your device.
However, try cleaning the contacts and find out about the warranty.
Sent from a dream.
eloquence intshe
Thanks for the reply.
Hehe dont worry you can have some of mine I'm on the 4th cup thats how stressed I am getting with this. Just trying Taysider's method for trying to re-enable the sd card function. I have disabled fastboot using your method so is there a way of mouting sd in recovery? because Im sure I may have tried that already and all I got was an icon of a phone with a red exclamation mark infront of it?
thanks
3rd edit: to find out if the adb is working properly and you got the htc sync installed type in whatever the command is in adb to see if it detects your device.
However, try cleaning the contacts and find out about the warranty.
Sent from a dream.[/QUOTE]
How do I clean the contacts on the sd reader? it doesnt look very accessible unless I remove part of the housing? also what command prompt do you recommend I try first? like I said I tried "adb shell" and got no device found I'll update in a second as soon as I have tried this I have just uninstalled htc sync now all I need to do is assign driver to "android 1.0" in device manager then I'll take it for a spin.
Thanks dude
Ironman MarkV said:
Thanks for the reply.
Hehe dont worry you can have some of mine I'm on the 4th cup thats how stressed I am getting with this. Just trying Taysider's method for trying to re-enable the sd card function. I have disabled fastboot using your method so is there a way of mouting sd in recovery? because Im sure I may have tried that already and all I got was an icon of a phone with a red exclamation mark infront of it?
thanks
Click to expand...
Click to collapse
Re-read my previous post, there' another edit.
Thing is, Im not too sure what options you get nor l, well, anything related to non rooted phones. Do not root your phone as I mentioned previously. Mainly because first you ought to find out if you are still under warranty. If you are, send it to them.
Exclamation mark? Do a search, there were a few threads talking about that a few weeks back, but I believe it was about something else entirely, people effen up their phones trying to root.
From here on, the best advice I can give you is step back, take a break, continue later. There is probably too much info in your head right now.
1- see if adb can detect your phone.
2- try cleaning the contacts, do a search cause I can't remember if the cleaning of contacts was also for the sd card or only the wifi antenna.
3- Check your warranty, I can't stress this enough.
4- Coffee is kicking in
5- Check if you can detect the sd card through recovery. My assumption is that recovery works something like safe mode in windows, only an assumption.
6- Wait till someone more knowledgable than myself joins in. Chances are it would either be darunion, gleviatan or some chap who's nick I cant remember but starts with an M.
@guyinthecorner: you can skip this one - and I'm still waiting for that flashable zip.
Sent from a dream.
Teichopsia said:
Re-read my previous post, there' another edit.
Thing is, Im not too sure what options you get nor l, well, anything related to non rooted phones. Do not root your phone as I mentioned previously. Mainly because first you ought to find out if you are still under warranty. If you are, send it to them.
Exclamation mark? Do a search, there were a few threads talking about that a few weeks back, but I believe it was about something else entirely, people effen up their phones trying to root.
From here on, the best advice I can give you is step back, take a break, continue later. There is probably too much info in your head right now.
1- see if adb can detect your phone.
2- try cleaning the contacts, do a search cause I can't remember if the cleaning of contacts was also for the sd card or only the wifi antenna.
3- Check your warranty, I can't stress this enough.
4- Coffee is kicking in
5- Check if you can detect the sd card through recovery. My assumption is that recovery works something like safe mode in windows, only an assumption.
6- Wait till someone more knowledgable than myself joins in. Chances are it would either be darunion, gleviatan or some chap who's nick I cant remember but starts with an M.
@guyinthecorner: you can skip this one - and I'm still waiting for that flashable zip.
Sent from a dream.
Click to expand...
Click to collapse
Lol, already saw your username and was like 'Yup, problem solved ;-)'
Flashable zip is being a pain in the rear, should have it soon (reading a crap-ton of tutorials to help me)
Sent from my Desire HD using Swype beta for Android!
I've been working on this for the past week. Every exploit I've tried just hangs after a while. I've gotten much further manually. I've got unbuntu and been working using various manual methods. The thing I've noticed is that there is no system folder in root. There is a system partition in which app and bin folders exist. Later today I'm going to have time to try some more. If it weren't for these silly rules id reply to somebody elses post, but I guess reading in forums for 3 years as a registered user doesn't count. Never a need to post as I've always found something using a search. And now I've got a phones that's been out for a week and there's no info out on it so I guess I get to develop myself. Not a hard thing...just time consuming and I've got better things to do, but these pink apps gotta go and I need wired or wireless tehter again. Hopefully I have succcess later today and can post how I accomplished it.
I'll be waiting anxiously. please post updates in this thread with your progress!
Any progress on this? I have been attempting but no luck.
update on progress
jb0ne said:
I'll be waiting anxiously. please post updates in this thread with your progress!
Click to expand...
Click to collapse
ok so here's what i've learned so far from trying every method that i can find...
when you boot the phone into the pink screen (volume up and volume down plus power) there is a partition containing 1 folder with 5 files. That folder is called image and the file inside are amss.mbn, boot.img, cust.img, emmcboot.mbn, and recovery.img
The Ascend G300 is a similar phone to the G312 and there is a filed called superrecovery which changes the recovery to set ADB with root priveliges and installs SU in system. If we use the recovery from that batch file made by PauloBrien and push it to the device while in pink screen mode and then reboot into recovery the phone won't power on. You can return to the pink screen and change back to the original recovery, but you can not boot the device into recovery nor regularly. Now this gave me an idea as i'm typing. what if i change it and issue the command in ADB as ADB works during the pink screen. I'm going to try that now.
But this can't be done when in bootloader, only in pinkscreen which makes me think it's fastboot USB mode, but fastboot commands dont work uless you are in the bootloader with the huawei logo which you can only get into by issuing the reboot-bootloader command through adb. once you enter bootloader mode via ADB reboot command then you are able to issue some fastboot commands.
ok so that didn't work...basically when the files in the imge folder are changed the device won't boot into anything but the pink screen mode.
the original recovery file size is 6340KB and the one from PauloBrien is smaller at 5074KB. I'm wondering if file size has something to do with why it won't boot, however, i'm not familiar with what's inside of these files. So...as i reasearch how to build our own clockworkmod recovery i'm wondering if there's a way to change the ADB command inside from not root to root. if it's a on off selecton i'm not sure how i'd affect file size. this is where we get into the realm of knowledge that i don't possess.
so if anybody can offer up some knowledge from where i stand now... please do so.
on a side note, when running exploits, (gingerbreak, zergrush, doomsomething, psneuter, etc)...they all hang.
in linux when trying to drop a file into /system/bin the terminal read out says something about failing to cycle power, not certain what this means.
as i learn a bit more, i'll go ahead and add more...
I am hopeful to hear back from you with a successful root method for this device. I myself just purchased this phone for myself and would really love to see more development on it. Seems like a solid phone with a low entry price. Look forward to seeing what you come up with.
I'm also waiting anxiously for someone to figure this out. I just got this phone and while I really like it, there is just so much packed on this thing that I want to get rid of before I can really enjoy the phone.
I'll be watching this thread as well hopefully OP or someone else will figure out the trick to rooting this phone, like others I have used the usual methods but no luck. I've counted no less than 13 programs I'd uninstall right off the bat.
For what its worth the phone seems to not be considered part of the Ascend models of phones although they are quite similar our model is called the Unite U8680 and the Unite Q U8730 (the slider version). I've sent a email to Huawei lets see if they respond at all.
It's pretty much useless but this is all I can find on the G312 on the Huawei website:
http://www.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=4086&tb=0
I'll be watching this thread as well. According to a post on another forum regarding a different Huawei model, dialling *#*# 2846579 #*#* and making some changes in the log file settings suddenly made their phones rootable for some reason. However while the same # gets you into the service mode on this phone, the log file changes made no difference.
I wonder, though, there are quite a few other options in that service mode. Maybe something in there that could be useful.
Edit: There's one menu that looks interesting, the USB one. You can change it to all sorts of modes including "Manufacture mode" whatever that is. Afraid to try it, don't want to brick my wife''s new phone
I've been playing with this menu as well and some of the USB modes do seem interesting. I was hoping this would let me find the product ID for the phone cause I found a link on the Huawei homepage to register to get an unlock code for the boot loader on this phone. If anyone is interested here is a link to the page and sadly the method they say to find the product ID doesn't work on our phone.
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=toApplyUnlock
huawei says the product ID is an 8 digit number. I've been trying to dump the log files so i can scan them for some kind of 8 digit number. i've also tried all the different USB modes as well as a few other changes in the project menu that we're able to access. These haven't given me any success in changing the ownership of the folders needed to gain root access. i've not had any time to tear apart the recovery image to figure out what it's doing. but all in due time somebody will figure this out. still haven't been able to get fastboot to work properly either. am running through the usb modes on that now.
Yes please help i cannot figure out out either
builder.clockworkmod.com
so i've been working on building a recovery image for this devices using koush's site and have been able to build it, but the device won't boot into recovery yet. not sure how to fix this, gonna mess around and keep on trying. i can get it to boot back up and can get it to respond to adb commands when in the mode that just shows the android 4g logo. but i can't get into recovery. not through adb and not through using the power and volume buttons.
still working on it... any body else have anything yet?
No info on rooting this phone but Huawei just posted on their website the open source gingerbread kernel for the G312 U8680 here is a link to it:
http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDY3MzU=
It's been rooted!
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!
jb0ne said:
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!
Click to expand...
Click to collapse
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.
jamonthis said:
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.
Click to expand...
Click to collapse
If you figure it out and find anything out I would love to know about it. Where should I watch for an update in case someone does get that sorted out?
Recovery mode
There is an accessible recovery mode, at least on my querty version of the phone. You have to completely pull the battery first. Put the battery back in, hold Volume up, and then hit power. I held the power button for a couple seconds, and volume up for maybe 6-8 seconds, then started hitting volume up repeatedly. The key is to pull the battery each time you try, I think. It looks like powering off from the phone's power menu just puts it in a suspend sort of mode. (Compare boot times when rebooting, and when pulling battery)
Apparently the bootloader is locked, so not sure how useful it is yet.
For anyone with a T-Mobile MyTouch Q (Huawei U8730), I created a wiki page for it, and we should post in the New Device Forum Requests thread so we have a specific place to post info.
I just purchased a U8730 today and will definitely be figuring out how to root it at some point.
For anyone that cares here's a link in case you haven't registered at the other site.
http://j.gs/1U5q
I'm hoping we can get some development going for this phone. I just picked one up for my daughter a month ago and it's giving her memory filled messages already. It'd be great if we can get it permanently rooted and remove bloat to start... then possibly move onto Cyanogen... considering she had the horrible Comet (also by Huawei) previously and it had development for CM7. I may be taking a leap from my contract soon, but can't go to Straight Talk with her phone unless it's unlocked
So I have upgraded my i927 captivate glide using the ROM from , but I only Androidupdate com called I927UCLH2_I927ATTLH2_I927UCLH2_Home tar md5 but I get a black screen with a slide down menu saying the date ‘Ongoing’ and an option to change the way that the device connects to another computer.
The update stated pass, it booted and proceeded to tell me that it was updating apps or something like that, then a black screen with the pull down menu from the top of the screen near the usb symbol came up but nothing else. I got a message a few hours later stating that the update application or something like that was not responding and an option to wait or quit. I chose wait, but nothing came of it eventually.
I then proceeded to try reflashing the process with no success even after factory reset and rebooting.
I then tried the pre-release ICS update as per XDA developers and other websites. Same thing
I tried a few other ODIN programs and ROMs but no success. Same issues including the hang up on the Samsung logo. I tried rooting it once and for some reason it started up into what looked like the same pull down menu, but it was requesting that I needed an to input a lock code for the network. I assume that is because my sim card was in it by now, but maybe not. I got so frustrated that I tried the bootloader and update bootloader options using the official ICS update ROM for some stupid reason but nothing. The thing is that at least it booted into the pull down menu that i got with a black screen again.
I then flashed with an updated ICS, CWM6 but cannot do the:
Third: Reboot into CWM6 (Volume- and power) install from sdcard (superuser)
Link to superuser: Superuser-3.2-RC2-arm-signed zip
Forth: Repeat third step above but install keyboard fix.
Link to keyboard fix: CWM_keyboard_backlight_fix zip
since I do not have an SD card that is working. I did get the SD Card in the device but I have always had problems with the format of it and I cannot put the zips onto the card due to the computer Win7 not recognizing it. I tried reformatting the device is HPUSB format program and windows. I inserted the card into the device to hopefully have it recognized on windows, and i gave me an option to format the SD card. So I proceeded and success. I was able to put the Zips onto the card. However, I returned to the CWM6 screen by pressing the VOL- and power keys but the files were no where to be found on the SD Card.
I moved on after a few other tries at it, so I tried to go backwards to the Gingerbread ROM. No success, same hanging issue at the Samsung logo.
I then tried to reflash with the devices original ROM as provided by DroidAngel on androidupdate com. Both without success.
I wanted to try the process involved on the 'stuck on boot screen' thread, but I cannot access the zip files on the sdcard in order to be able to do that.
I also bought my phone unlocked from the US (ATT version) and had it sent to me in Canada unlocked so I cannot just return it to the seller to get a new one, so my new phone is pretty useless.
I have spent two days reading through and trying different fixes and updated ROMs on multiple sites but I just cannot figure out what the heck to do now. I know that this site is not to spoon feed people and I am a noob to all of this but I am out of ideas and cannot find anything else to help out.
Where do I go from here. Is there a possibility of reformatting EVERYTHING on the device including all partitions etc etc.? I mean the hardware is fine, it is just a software issue. I do this to my laptop whenever I get into a bind.
Have you tried booting into CWM and restoring factory?
sent from my captivate glide running ICS (NardROM 0.3 Rooted)
Just a note, the SD card you're seeing in CWMR isn't actually your physical SD card, its the internal phone memory. I don't think we have a version of CWMR that reads the real external SD unless modified. So anything you put on it won't show up there. The folder structure will look like ... /sdcard/external_sd/ where /sdcard/ is where you want to put your files for CMWR to see, /external_sd/ is your physical card you can take in/out.
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
EaglesIII said:
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
Click to expand...
Click to collapse
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Evil Alex said:
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Click to expand...
Click to collapse
Okay, so right now I can still get into the download mode to flash, the CWM6 to factory reset and reboot which I have tried already as stated, and I have not been asked for the network key again since the one time quite a long time ago. The network key is only asked when I load one of the other custom ROMS though, but I have not tried any of those in a while.
I am stuck at the black screen with white Samsung logo.
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Got it running on Bio360 but 'Not Registered on Network' now
Evil Alex said:
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Click to expand...
Click to collapse
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
EaglesIII said:
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
Click to expand...
Click to collapse
You're very welcome! Glad to hear the phone is usable again. In order to get data back you will have to set your APN manually. Stock ROMs come with the APN settings for all providers it is expected to be sold with. But custom ROMs usually come without those settings. You can find the APN settings for your provider online, just do a search. There is even an app for it, but the name eludes me at the moment. You'll need wifi to get the app, though! Once the settings are in place (You put them in under wireless & Networks), you'll have data again.
As for the limited functionality, I had the same thing, at first. The upgrade was broken for me, I guess some settings/apps were causing problems. So, after flashing the upgrade, I did a factory reset in CWM. I also wiped the cache, and the Dalvik cache, for good measure(Under advanced in CWM). It rebooted, said it was upgrading and installing, and I let it sit for a few minutes. Then I was greeted by an initial setup screen, and the phone has been on a working ICS ever since! I did lose all my settings and such, but I had a back-up of those with Titanium Backup, and got those back that way.
Hope this will help as well.
the phone is a sprint gnex.
i had twrp as recovery, and i was playing around with it, got distracted, and my 2 year old grabbed it and wiped everything. no OS, no recovery, no nothing.
i'm not even sure where to start. my newbie self is thinking maybe odin? i used adb once, is that where i should be looking?
i guess my question is where does one start when he has no OS. and i could sure use a link for wherever factory images, or tar files, or whatever, are reposed.
please help a brother out, and keep in mind i am in fact over my head. just trying to salvage this if possible. it is not an urgent thing, as i the device is merely used as a media device for my 2 year old.
my laptop is a windows 7 device. i've downloaded usb drivers for samsung, odin, and adb fastboot. they are sitting in my download folder as zip files. that is where i stand.
boathead said:
the phone is a sprint gnex.
i had twrp as recovery, and i was playing around with it, got distracted, and my 2 year old grabbed it and wiped everything. no OS, no recovery, no nothing.
i'm not even sure where to start. my newbie self is thinking maybe odin? i used adb once, is that where i should be looking?
i guess my question is where does one start when he has no OS. and i could sure use a link for wherever factory images, or tar files, or whatever, are reposed.
please help a brother out, and keep in mind i am in fact over my head. just trying to salvage this if possible. it is not an urgent thing, as i the device is merely used as a media device for my 2 year old.
my laptop is a windows 7 device. i've downloaded usb drivers for samsung, odin, and adb fastboot. they are sitting in my download folder as zip files. that is where i stand.
Click to expand...
Click to collapse
Don't worry you'll be fine.
If you can get into twrp, try just downloading a ROM and gapps zip on computer and using adb to push or sideload to device (Google "adb sideload ROM galaxy nexus...exact steps easy to find)
If you can't get into recovery, or just want to go back to complete stock and start from there, go here https://developers.google.com/android/nexus/images
Grab a package for sprint gnex(mysidspr, aka toroplus) and if u have adb&fastboot installed on computer(if not then Google "installing android SDK" and it will be top result, fastboot and adb come WITH the SDK when u install it)
Then you just unzip that factory img file, plug device into computer while in boot loader mode (hold power and both volume keys), open the folder created when u uncompressed factory IMG file, hold down shift and right click and choose "open command prompt". Enter "fastboot devices"(no quotes) in the command window to make sure device is recognized. Then just run "flash-all.exe" or "flash-all.bat" in command prompt and BE PATIENT AND LET IT FINISH EVERYTHING. After that device will be like brand new out of box.
ashclepdia said:
Don't worry you'll be fine.
If you can get into twrp, try just downloading a ROM and gapps zip on computer and using adb to push or sideload to device (Google "adb sideload ROM galaxy nexus...exact steps easy to find)
If you can't get into recovery, or just want to go back to complete stock and start from there, go here https://developers.google.com/android/nexus/images
Grab a package for sprint gnex(mysidspr, aka toroplus) and if u have adb&fastboot installed on computer(if not then Google "installing android SDK" and it will be top result, fastboot and adb come WITH the SDK when u install it)
Then you just unzip that factory img file, plug device into computer while in boot loader mode (hold power and both volume keys), open the folder created when u uncompressed factory IMG file, hold down shift and right click and choose "open command prompt". Enter "fastboot devices"(no quotes) in the command window to make sure device is recognized. Then just run "flash-all.exe" or "flash-all.bat" in command prompt and BE PATIENT AND LET IT FINISH EVERYTHING. After that device will be like brand new out of box.
Click to expand...
Click to collapse
thank you so much for responding. i will play around with this later, but it is a bit comforting to know that maybe i'm not doomed.
i cannot get into recovery, so yeah, i don't know what i'm doing.
boathead said:
thank you so much for responding. i will play around with this later, but it is a bit comforting to know that maybe i'm not doomed.
i cannot get into recovery, so yeah, i don't know what i'm doing.
Click to expand...
Click to collapse
Why can't you get into recovery?
Are you choosing recovery mode via the bootloader menu? I didn't think it was POSSIBLE to wipe recovery from within recovery.
Even if you can't, trust me, Doing a factory img restore, or using fastboot to flash custom recovery again is VERY easy. To get the SDK that has needed fastboot tools, go here http://developer.android.com/sdk/index.html#ExistingIDE
And grab the needed exe for your setup(windows 64 or 32bit). Make sure you are getting the "ADT bundle" it's what has needed platform tools. Then just run the exe and follow instructions.
Now u COULD also just Google search for Wugfresg toolkit, and download and use that. Its very easy to use as well. I just prefer to have adb and fastboot installed to my computer so that I can always be good to go. Plus I use Linux so Im not able to use Wugfresh, but knowing how to just use fastboot and adb also makes ya feel like a boss(even though is pretty simple lol)
Don't worry, there is hope, and it's not gonna be difficult. You'll be up again in no time.
because you said you didn't think it was possible to wipe recovery from recovery, i went into bootloader. you are correct. in my panic i overlooked it. i DO in fact still have twrp.
but there is nothing to restore or install. so once my phone charges, i'll give it a shot as you suggested. would you kindly check in later in case i need some more help?
thanks my friend for steering me in the correct direction.
boathead said:
because you said you didn't think it was possible to wipe recovery from recovery, i went into bootloader. you are correct. in my panic i overlooked it. i DO in fact still have twrp.
but there is nothing to restore or install. so once my phone charges, i'll give it a shot as you suggested. would you kindly check in later in case i need some more help?
thanks my friend for steering me in the correct direction.
Click to expand...
Click to collapse
Of course!
I'm always checking in these forums, and I use Tapatalk, and have actually grown fond of Tapatalk notifications, so I SHOULD get a notif if you post back or PM(though I prefer to keep in thread, that way someone else searching for answer to similar issue can find a helpful thread as well)
Yea it sounds like your little one got into twrp and most likely wiped all of /data and /system. Instead of just a regular factory reset which would have left your stuff like flashable zips and all still in /sdcard. That sucks! I've actually done that on accideHahaha
hile back(a mistake you only make once to wipe all of /data AND /system lol, even though can pretty easily be fixed)
Sounds like you could use adb sideload or push to get ROM/gapps zips back on the device, or just go with a total device factory restore, whichever you choose at this point should work just fine.
I'm not sure if there is a way to do this yet, but I've always wanted to put a pin code lock for TWRP. That way if my nephew ever did find his way into there when using my phone, he wouldn't be able to do any damage. If it's not a part of custom recovery yet (I haven't looked actually lol) it would be awesome if someone found a way to add that feature in. Could save a lot of us the hassle in cases like this! Hahaha
I'll check back in the morning and randomly tomorrow (some of the day I won't have a connection, I use Gnex strictly on WiFi) to see if you need any help/tips/clarifying of any steps needed. Once you do this restore process once, you'll be amazed at how easy it can be, and as long as you keep the files on your laptop, you'll be ready to go if you ever need to do it again.
success!
i had a great deal of trouble sorting the drivers....took quite a while to get the pc to recognize the device. then i got confused about a few things...stunner, i know, but was able to reflash a factory image with the wug toolkit. so i guess i took the cowardly way and didn't do the adb route.
anyway, i'm good to go. i am left with the initial problem that had me in recovery in the first place. i figured flashing a rom would solve it, but no. so i'm left thinking it is on the server side. at least i have something to work with now.
so thanks again. without your calming words i never would have gotten this going. i don't have the temperament to play around with my devices, i've learned.
boathead said:
success!
i had a great deal of trouble sorting the drivers....took quite a while to get the pc to recognize the device. then i got confused about a few things...stunner, i know, but was able to reflash a factory image with the wug toolkit. so i guess i took the cowardly way and didn't do the adb route.
anyway, i'm good to go. i am left with the initial problem that had me in recovery in the first place. i figured flashing a rom would solve it, but no. so i'm left thinking it is on the server side. at least i have something to work with now.
so thanks again. without your calming words i never would have gotten this going. i don't have the temperament to play around with my devices, i've learned.
Click to expand...
Click to collapse
That temperament is something that is gained. MOST of us have been in that "oh holy crap what do I do now?!?! Im not prepared for this!!" Moments (my first one was on my birthday back when I had DroidX2, and didn't have my own computer to restore it using RSDlite sbf flash.. I accidentally flashed something that didn't work, and was left with no OS stuck in bootloop with no way to get into the bootstrap recovery we had...was without device for 3 days until I could get to a coworkers laptop!! Lol!!!) But the stress goes WAY down after you've restored device once or twice and have the tools at the ready with basic understanding of the steps at least
And as for drivers, I apologize for not warning/informing about that. I forgot that you mentioned you had multiple driver packages downloaded and i was going to clarify which to use(on a Linux setup you don't need drivers and it been a while since I used windows for my device so drivers aren't usually on my mind lol) I think a lot of people use the PDAnet drivers. But if you are connected to internet and just put device in fastboot mode and connect to computer, I think it will automatically find and install the correct drivers needed for fastboot/adb access.(the toolkit can also be used to install correct drivers I believe)
And don't worry, I wouldn't call using toolkit the "cowardly way". SOME people detest/despise use of toolkit since they think it takes away from learning and understanding how to do it without a toolkit. But when you use a toolkit you usually see command prompt correct? (Or at least a setting so you can SEE what it is running as far as commands) so you get to see what its doing, which helps beginners start to grasp the concepts of what it is doing.
Trust me, if you can use the toolkit correctly, you can easily transfer that knowledge to just using fastboot or adb commands.
by the way, fastboot is what's used for factory image restore. ADB is for pushing/pulling files, taking logs, sideloading a ROM/gapps zip that isn't on device, taking/restoring adb backups of system and or data, things like that. Think of adb as the "taker and giver". And fastboot as the "img installer/booter"...imgs being anything from system img files, to data partition img files, boot.img(aka kernel), recovery.img, bootloader update img, radio imgs. Things like that
The reason the knowledge from using toolkit easily transfers over to using just straight up fastboot for example is because of how they word the choices and menus. You will see it says something like "use fastboot to flash new recovery img", which the fastboot command for that in command line equates to "fastboot flash recovery "NameOfRecoveryImage.img" "
(With no quotes of course, and replace "NameOf...." With the actual file name of the recovery.img you have downloaded, and you can rename the downloaded recovery img file to something easier to type out if you want to also)
Basic structure of using fastboot command would be as follows:
fastboot[space]command[space]partitioname[space]filetobeused
Which after used once or twice is very easy to grasp basic usage
So are you able to at least boot into OS now? Also, make sure if you are trying to flash a KitKat ROM, that you install the 2.7TWRP recovery, anything earlier won't work correctly for 4.4based ROMs.
Again, any trouble feel free to ask.
(And apologies for the long rambling posts lol)
yes. i am in the OS now.
what gave rise to my troubles in the first place is that i've moved my residence. all my devices recognize my new wifi, and proceed along their merry way.
my gnex is another story. it recognized my wifi, shows me as connected, but nothing at all can actually access the server. i tried factory reset, nothing. then i was going to install a new rom, figuring something was corrupted. then my 2 year old took over!
so i am in the OS, but still cannot access the server. so it must be on the server side i figure. not sure how to fix this, but when i have some time, i'll do some looking around. i am going to try to access a different wifi network later on to see if at least it is not my device.
again, thanks for your help my friend.
boathead said:
yes. i am in the OS now.
what gave rise to my troubles in the first place is that i've moved my residence. all my devices recognize my new wifi, and proceed along their merry way.
my gnex is another story. it recognized my wifi, shows me as connected, but nothing at all can actually access the server. i tried factory reset, nothing. then i was going to install a new rom, figuring something was corrupted. then my 2 year old took over!
so i am in the OS, but still cannot access the server. so it must be on the server side i figure. not sure how to fix this, but when i have some time, i'll do some looking around. i am going to try to access a different wifi network later on to see if at least it is not my device.
again, thanks for your help my friend.
Click to expand...
Click to collapse
what security do you use on your router? if WEP try changing it. the gnex has issues sometimes with using WEP secured WiFi AP's
also, if using a 5ghz network, I can only get mine to connect to that on channel 153. there are only a certain number of 5ghz channels supported.
might also want to just try forgetting WiFi network and re add?(if it restored the access points by any means including Google backup/restore)
and make sure your router isn't rejecting the Mac address for some reason(and some people will suggest reboot of the router to see if that helps fix it, which I've seen fix many connection issues)
well, my device works beautifully....everywhere except in my house.:crying:
as much as drivers befuddle me, routers do even more so. it must be a router issue, right? my device connects to google elsewhere. and all my other devices connect to google here at home. maybe tomorrow i'll try the router's live chat to see if i can get some help.
boathead said:
well, my device works beautifully....everywhere except in my house.:crying:
as much as drivers befuddle me, routers do even more so. it must be a router issue, right? my device connects to google elsewhere. and all my other devices connect to google here at home. maybe tomorrow i'll try the router's live chat to see if i can get some help.
Click to expand...
Click to collapse
what type of security are you using in the router setting? WPA? wep? none?
what model router are you using?
is device connecting to internet and just not Google servers?
is device connecting to router at all and just no internet access?(meaning when you are in WiFi settings, and choose network does it show obtaining IP address and then connected? or just never fully connect?)
I've had similar issues in past and might be able to help with some more details
ashclepdia said:
what type of security are you using in the router setting? WPA? wep? none?
what model router are you using?
is device connecting to internet and just not Google servers?
is device connecting to router at all and just no internet access?(meaning when you are in WiFi settings, and choose network does it show obtaining IP address and then connected? or just never fully connect?)
I've had similar issues in past and might be able to help with some more details
Click to expand...
Click to collapse
wpa2...but i've even disable all security to see....i've disable firewalls...nothing. it is an arris router that time warner cable provided when i moved to my new place.
and i my phone does show me as connected to my network...just can't get into google. and the phone works just fine at my work. as you know, i've been through several roms and an entirely new OS...so it cannot be the phone...can it?
been through this entire threads, and no joy.
http://forum.xda-developers.com/showthread.php?t=2110225
if you have any ideas, post away. i will be away from access to the internet for a few days, so i won't even have a chance to check in here, but any info in the meantime would be most thanked.
boathead said:
thank you so much for responding. i will play around with this later, but it is a bit comforting to know that maybe i'm not doomed.
i cannot get into recovery, so yeah, i don't know what i'm doing.
Click to expand...
Click to collapse
my samsung s5 had the same problem. i wiped out everything and it says i have no os no nothing. i hope if anyone can help, i will be pleased.
the only question is that "how can i get an os and get my phone working"
ashclepdia said:
Don't worry you'll be fine.
If you can get into twrp, try just downloading a ROM and gapps zip on computer and using adb to push or sideload to device (Google "adb sideload ROM galaxy nexus...exact steps easy to find)
If you can't get into recovery, or just want to go back to complete stock and start from there, go here https://developers.google.com/android/nexus/images
Grab a package for sprint gnex(mysidspr, aka toroplus) and if u have adb&fastboot installed on computer(if not then Google "installing android SDK" and it will be top result, fastboot and adb come WITH the SDK when u install it)
Then you just unzip that factory img file, plug device into computer while in boot loader mode (hold power and both volume keys), open the folder created when u uncompressed factory IMG file, hold down shift and right click and choose "open command prompt". Enter "fastboot devices"(no quotes) in the command window to make sure device is recognized. Then just run "flash-all.exe" or "flash-all.bat" in command prompt and BE PATIENT AND LET IT FINISH EVERYTHING. After that device will be like brand new out of box.
Click to expand...
Click to collapse
The same thing happened to me right now, while I was installing CM13 in my Lenovo Zuk Z1. I took a backup from TWRP and copied the same to my pc. Then I wiped all the data from my phone using TWRP. Then I plugged in the Usb back to copy the downloaded files of CM13 to my phone but my pc is not showing the Internal Memory of my phone. I am so freaked out right now. I dont have an OS in my phone and I am unable to restore what I backed up. I am just stucked in TWRP. Guide me through to install CM 13 or atleast revert back to where I started. Any help is appreciated.
I have hit dead end after dead end, after many hours, just want to get copy of text messages off this phone somehow, and then erase all data. I have spent many hours on this, my level of experience with all this is beginner/intermediate, as I'm sure you will be able to tell by the ramble below. Skip to the last paragraph **** with the asterisks to get to the important part of my inquiry. if you don't want to read about what I have tried already.
Before you suggest the obvious, replace lcd, let me say that the motherboard lcd connector is damaged beyond repair. water damage, but the phone boots normally and seems to run fine. phone calls ring and other sounds indicate the phone is able to function but no display or touch function obviously. the usb port works. Also there is no samsung account on the phone so that option to bypass screen lock does not help. Kies, smart switch, etc don't help due to the "screen lock"
ie... There is a basic swipe to unlock "lock" on the phone, so otg cable options also hit a dead end. There are workarounds to bypass other lockscreens, but no way to do the swipe over otg that I can find. And even if/once I am able to swipe to unlock over otg, there are other obstacles to get around that may not be possible (click ok, navigate to enable usb debugging). If I am wrong here and there is an obvious solution I am missing, let me know (explain in detail if you can) and I will get the hub & cable back out and try again!
Dr.phone android recovery (data recovery/damaged device option) looks like the most promising, and here I have also run into trouble. Dr phone will put the phone into download mode but then always seems to fail "flash recovery package failed" at some percentage. dr.phone downloads the recovery package (I am selecting the correct model n910v) successfully, but the percentage before flash recovery package fails changes. It hasn't made it past 85%. the dr.phone log files don't reveal anything to my untrained eye.
Before running dr.phone, adb "permission denied"...after using dr phone, however, while the phone is still powered on and in download mode, once I close dr phone, I am able to start to get somewhere with adb! adb devices shows the phone as an emulated device, and (some) adb commands start to work! I think if I just am able to find the exact location of the stock messaging log, I will be very close.
If anyone can suggest some commands to try in adb to grab just the sms log I would be very grateful!
I can run "adb backup", and have tried a few other adb commands, but none of the standard backup commands actually contain a sms log.
***Anyway, I think the best option might be to flash a custom recovery after getting the phone in download mode & adb working successfully (showing as an emulated device) with dr.phone as described above... However I have no way to tell what firmware version the phone is running (don't want to brick it or loose data), and I am really looking for specific directions on which clockworkmod or twrp recovery file to try for n910v, that will allow me to get a sms backup, and/or a recovery that will have usb debugging enabled.
Thanks for the input! sorry for the rambling post, I hope it's possible to make sense of it.. ANY help greatly appreciated!
beefriendly said:
I have hit dead end after dead end, after many hours, just want to get copy of text messages off this phone somehow, and then erase all data. I have spent many hours on this, my level of experience with all this is beginner/intermediate, as I'm sure you will be able to tell by the ramble below. Skip to the last paragraph **** with the asterisks to get to the important part of my inquiry. if you don't want to read about what I have tried already.
Before you suggest the obvious, replace lcd, let me say that the motherboard lcd connector is damaged beyond repair. water damage, but the phone boots normally and seems to run fine. phone calls ring and other sounds indicate the phone is able to function but no display or touch function obviously. the usb port works. Also there is no samsung account on the phone so that option to bypass screen lock does not help. Kies, smart switch, etc don't help due to the "screen lock"
ie... There is a basic swipe to unlock "lock" on the phone, so otg cable options also hit a dead end. There are workarounds to bypass other lockscreens, but no way to do the swipe over otg that I can find. And even if/once I am able to swipe to unlock over otg, there are other obstacles to get around that may not be possible (click ok, navigate to enable usb debugging). If I am wrong here and there is an obvious solution I am missing, let me know (explain in detail if you can) and I will get the hub & cable back out and try again!
Dr.phone android recovery (data recovery/damaged device option) looks like the most promising, and here I have also run into trouble. Dr phone will put the phone into download mode but then always seems to fail "flash recovery package failed" at some percentage. dr.phone downloads the recovery package (I am selecting the correct model n910v) successfully, but the percentage before flash recovery package fails changes. It hasn't made it past 85%. the dr.phone log files don't reveal anything to my untrained eye.
Before running dr.phone, adb "permission denied"...after using dr phone, however, while the phone is still powered on and in download mode, once I close dr phone, I am able to start to get somewhere with adb! adb devices shows the phone as an emulated device, and (some) adb commands start to work! I think if I just am able to find the exact location of the stock messaging log, I will be very close.
If anyone can suggest some commands to try in adb to grab just the sms log I would be very grateful!
I can run "adb backup", and have tried a few other adb commands, but none of the standard backup commands actually contain a sms log.
***Anyway, I think the best option might be to flash a custom recovery after getting the phone in download mode & adb working successfully (showing as an emulated device) with dr.phone as described above... However I have no way to tell what firmware version the phone is running (don't want to brick it or loose data), and I am really looking for specific directions on which clockworkmod or twrp recovery file to try for n910v, that will allow me to get a sms backup, and/or a recovery that will have usb debugging enabled.
Thanks for the input! sorry for the rambling post, I hope it's possible to make sense of it.. ANY help greatly appreciated!
Click to expand...
Click to collapse
This tool might work for you. Ive never used it myself but it looks promising. It supposed to be able to control your phone on your pc.
For the custom recovery, it should tell you what model you have when you boot into download mode but the TWRP for the note 4 has been unified so it should work either way. This link is for the most recent version. Get the .tar file if you're looking to use ODIN to install it.
Thanks for the reply! The tool you inked to requires USB debugging switched on. I was looking at it previously but didn't consider it because of this. I have USB debugging off, and the process I described with the dr phone windows application /download mode, doesn't turn usb debugging on.
Is there a way that I can flash a recovery for the note 4 that has USB debugging enabled from the start? If anyone knows please describe the process or post the link.
I think I need step by step instructions or screen shots for what to do with the Note 4 twrp recovery. I am trying to acquire a second phone so I can view the screen and know what buttons to press, but so far it is not looking like I have enough information to do sms backup from the twrp menus..on the device when I can't see the screen.
I see reference to being able to use adb commands to control the twrp recovery / backup process, but so far I haven't found anything that will help for my particular situation. If anyone knows what adb commands to use to pull the note 4 sms files , or a backup that includes them, PLEASE let me know.
thanks again