Related
Hello all,
I'm trying to remove the bootsound for my Desire and so followed the instructions in thread 675580, page 3 (can't post direct URL because I'm a new user)
I replied there saying it does not work but after rereading carefully, I think it's because I tried the command while not being in recovery mode.
I then went around and read a few threads to figure out how to enter this mode. I thus followed the instructions in thread 6710092, reply number 4 in the part about "How to flash ROM".
I can get up to step 6 just fine. I even have the black screen with red triangle showing up. I then try the next step, that is running "recovery-windows.bat"
Unfortunately, adb-nilezon says it did not find any device and so errors out in the three steps inside the batch file.
The only option that I was able to find to get back the phone in a workable state was to remove the battery.
I noticed a behavior of the phone that is not mentioned in the above thread, so maybe I did not do something right.
In Step 5, right after I plug the desire to the PC, Windows says it has found a new device and complains it could not find the driver. I tried to have it search for drivers, but it could not find anything and thus aborted the install.
Along with this, in step 6, right after I press the power button to select Recovery, the phone seems to "reboot" as it shows the white HTC boot screen and it vibrates.
Is it possible that I am missing a part of the correct install?
I read all replies to the mentioned tutorial thread, some users have the same problem so I created a Gold card, which I believe I did right. But this did not change my situation.
When not in recovery mode, I'm able to use USB Debugging to connect to the phone and send my test applications via adb just fine.
Many thanks for your time and patience
Olivier
obones said:
Hello all,
I'm trying to remove the bootsound for my Desire and so followed the instructions in thread 675580, page 3 (can't post direct URL because I'm a new user)
I replied there saying it does not work but after rereading carefully, I think it's because I tried the command while not being in recovery mode.
I then went around and read a few threads to figure out how to enter this mode. I thus followed the instructions in thread 6710092, reply number 4 in the part about "How to flash ROM".
I can get up to step 6 just fine. I even have the black screen with red triangle showing up. I then try the next step, that is running "recovery-windows.bat"
Unfortunately, adb-nilezon says it did not find any device and so errors out in the three steps inside the batch file.
The only option that I was able to find to get back the phone in a workable state was to remove the battery.
I noticed a behavior of the phone that is not mentioned in the above thread, so maybe I did not do something right.
In Step 5, right after I plug the desire to the PC, Windows says it has found a new device and complains it could not find the driver. I tried to have it search for drivers, but it could not find anything and thus aborted the install.
Along with this, in step 6, right after I press the power button to select Recovery, the phone seems to "reboot" as it shows the white HTC boot screen and it vibrates.
Is it possible that I am missing a part of the correct install?
I read all replies to the mentioned tutorial thread, some users have the same problem so I created a Gold card, which I believe I did right. But this did not change my situation.
When not in recovery mode, I'm able to use USB Debugging to connect to the phone and send my test applications via adb just fine.
Many thanks for your time and patience
Olivier
Click to expand...
Click to collapse
Not sure if you do or not but do you need to have Htc Sync installed for the drivers?
I do have HTC Sync installed
Are you rooted? You need root to do this. If you are then why not use fake flash or unrevoked to enter recovery.
No I'm not, but the message in thread 675580 says there is no need for it, hence my tries here.
I'd rather not root my device if I don't have to, for the time being that is.
obones said:
No I'm not, but the message in thread 675580 says there is no need for it, hence my tries here.
I'd rather not root my device if I don't have to, for the time being that is.
Click to expand...
Click to collapse
Recovery-windows.bat won't work unless you are rooted. The screen with the red triangle isn't actually recovery mode. The .bat file you would run pushes the recovery to the phone.
If you are not going to root, then you can get an app from the market that puts your phone on silent as you switch it off, and then back to normal when it's booted. This disables the boot sound. It's called silent boot I think.
Well then, I'm missing something from the other thread (675580) as I can't get the command to work.
I'll wait over here for any comments.
Thanks
obones said:
Well then, I'm missing something from the other thread (675580) as I can't get the command to work.
I'll wait over here for any comments.
Thanks
Click to expand...
Click to collapse
try fake flash? ive never used it so i duno if u need to be rooted
Fake flash needs root. No custom recovery will work without root. Quite simply, if you are not rooted you will not have write access to /system
please help.
i try to install froyo rom.
after flash FroYo_inkreDroid (14.07.2010) rom (throught standart flashrom procedures by update.zip) the device will not boot into os. i try update modem and after this the device win not booting to recovery mode.
i try press both combination (back key + power and volume down + power). the result of both combination is: 7 short vibro signals and black screen.
please help me, how me recovery my device.
thnx and sorry for my english.
your going to have to root it.
Would appreciate your help on the following issue (amoled display):
- phone doesnt boot up, it is stuck to a screen showing htc in the middle and 4 small triangles in the corners; if I unplug the pc cable it goes to a RUU menu
- no access to recovery or bootloader menus (by holding power + vol down/back)
- installing stock RUUs dont work; there is a 110 error saying that the RUU is not complete (tried 5-6 RUUs, both 2.1 and 2.2). there is a progress bar on the phone's screen that is normally green, but turns red when the radio is being written (as per the install wizard on the pc) and there is another triangle showing up at the end of the progress bar
- fastboot oem boot restarts the phone, but then it gets stuck to the white screen having htc in the middle (like when you start up the phone and after this quietly brilliant shows under htc, for me it doesnt go beyond this initial point)
- fastboot reboot-bootloader restarts the phone into the same 4triangles screen with htc in the middle
- adb doesnt work as it doesnt show my device
- any power + vol down/back combination brings the phone to the 4triangles screen
- if I run the stock RUU after fastboot oem boot (white screen with htc in the middle) there is a menu showing up on top of the white screen showing up the progress (1-bootloader, 2-radio_v2, 3-radio, then system, recovery, user data, etc.); bootloader is updated ok but then it gets stuck when updating radio_v2 and doesnt move further from that point)
- after the RUU install fails, I plug out the pc cable and see the RUU menu; depending on the RUU that I try to flash the hboot version changes up and even goes down after, but the firmware (what the RUU installer "sees" on the phone) and radio (seen on the RUU menu) remains the same: 1.21.405.1 and 4.06xx; the date on the RUU menu also changes depending on the RUU that I try to flash
Any suggestions to get my desire unbricked?
Bit of a background to the problem:
- rooted (unlockr) and was having Paul's r3 rom (2.1)
- updated the radio to 5.10xx
- got into silly restarts when using gps and thought to reflash a new rom and went for Paul's r8
- restarts were there also when using the phone normally
- thought to re-do all the rooting, wiping out everything from the phone, etc; so having r8 as the rom (pre-baked version) I started the rooting process with creating again the goldcard, etc etc
- error message at some point saying partition update fail (following the steps from theunlockr as I did the first time when rooting) and then the phone got to this triangles screen with htc in the middle
- strange though that this screen is different than the one when I first rooted when there was just one big triangle in the middle
Thanks a ton guys!
I've seen a few posts about this screen with the 4 triangles, but never seen the result of any potential fixes, or if it was ever actually fixed.
Just an idea, but it was maybe a bad radio flash if you are saying it started playing up after that? Unfortunately a bad radio flash is fairly terminal so I hope that's not your problem.
Good luck with this one and if you get it fixed then post the result here if you don't mind!
Will definitely post the solution when found; so far though nobody has any thoughts around what might be the reason behind this problem and how to get around it. I dropped a few PMs to the people that had this problem in the past and contacted Paul at Modaco, but so far no replies...
You can fix this with an RUU, I've had the same issue when I unplugged too early after flashing, but you are asking for help in the wrong section.
thought that the dev's section is where the best knowledge exists...
about the RUU process, I am trying to flash stock RUU.exe files, but there is a problem when the radio is being written and then I get a 110 error from the RUU install wizard saying that the RUU is incomplete.
for you the RUU install worked smoothly?
If you get a write error during an RUU flash (i.e. while the flashing is taking place, not before) it probably means there's a hardware fault.
Could be hardware, but I find it hard to believe as the phone is new and it is network locked, hence I didnt even use it for real, apart from some wifi and gps activities. Besides, the phone worked very well when I first rooted with Paul's r3 and the whole mess with restarts when using gps started after I upgraded the radio to 5.10xx having a 2.1 OS.
I feel that the problem started when I tried to root the phone being on Paul's r8 2.2 OS (tried to root with a 2.1 system and then it got messed up in the process).
I am not saying that it is not hardware as it is a possibility, but still think that it might be a messy software aspect, as if the radio is messed up from a hardware perspective, then at least the system should boot up and then wifi, gps, gsm and the things that are controlled by the radio shouldnt work...but somehow the OS should start-up.
Basically I dont get a write error, it's just that the error comes up when the radio is being written, hence I think that there is something wrong with the radio set-up that I have now on the phone...
Maybe somebody knows how to flash the system from scratch using only fastboot in cmd (having the right zip or img files properly signed), or maybe just the radio to start with.
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
acolwill said:
This is not a Development question and thus should not be posted in the Development forum.
Thread reported.
Click to expand...
Click to collapse
Well, I thought that as various solutions to root the phone, to get past different restrictions in the OS, etc. were discussed here, it might be a good thing to develop a way to bring back to life a OS being in this situation like mine...come on...
mariosraptor said:
have a look here. i do not know if it helps though. and i know it is not a Desire
http://forum.ppcgeeks.com/htc-hero/118035-error-110-ruu.html
i also found this. sounds familiar? not for desire but might do the trick http://forum.androidcentral.com/htc-hero-roms-hacks/13171-110-error-ruu-1-56-fix-100-unroot-too.html
sorry if i wasted your time.
Click to expand...
Click to collapse
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
but to get adb you need to download and install android sdk. look here http://developer.android.com/sdk/index.html system dependands download.
install it here are instructions on how to use if you aren't familiar with.
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
for anything else just use google.
i'm pretty sure that your device is fixable and you can fix it without any service center. cheers and post what ever happens.
popepope said:
Thanks anyways man, I looked at that already, but cant get it done as I dont have adb commands available in cmd, only fastboot. Dont worry about waisting my time, I really want that these days
Click to expand...
Click to collapse
I know how to use adb commands...pretty new to android and everything, but lately I roamed a lot through various things about it and learned a lot.
The problem is that adb doesnt list my phone when I run adb devices, it shows only when I run fastboot devices, I am sure you know what I mean...hence I cannot push any files to the phone, etc., at least not using adb in cmd.
That's actually the problem, that I cannot get adb to work, I only have fastboot commands. At least the way I see it now the question is how can I work with the phone to fix it just by having fastboot access in cmd.
I searched quite a lot various forums, etc, but I never came across a solution that will get things going just by having fastboot in cmd (without adb working). Maybe somebody here will come up with some magic trick...
Nerten said:
I had the same problem. Passed the device in service center. Changed the motherboard under warranty. It took one month's time.
Click to expand...
Click to collapse
How did you end up having this problem, just like that or after some update, flash, etc?
Thanks!
have a look here mate http://forum.androidcentral.com/htc...9-bricked-my-evo-but-there-away-un-brick.html
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
sorry idf i don't underdstand, but if you have fastboot working in your device and sdcard also then you should be able to push files to device via fastboot making as clean installs as possible.so if your device is picked up by command line type fastboot to see command list. i'am a bit comfused. pretty sure you should fix it through fastboot though.
popepope said:
same story unfortunately, doesnt apply to my problem. in the link they use a terminal emulator, but I cant use that as it doesnt work...it's basically an alternative to using adb directly in cmd, and this doesnt work for me.
if I am to get adb functionality back, then I'm done with the problem in 5 mins probably...
thanks anyways, keeping the hope alive!
Click to expand...
Click to collapse
right, I can run 2 things with fastboot in cmd: (name of the files just an example)
1. fastboot update update.zip
here I get that the archive doesnt contain android-info.txt or android-product.txt
2. fastboot flash update.img
here i get signature verify fail
for example, fastboot erase radio says FAILED, remote: not allowed
there are some fastboot commands related to the kernel and some others, but dont know how to make use of them for my problem.
sd card is accesible for sure and it is a goldcard.
I saw some linux/ubuntu methods to simulate adb usage in cmd, but I dont think it will work...will try to find an ubuntu image and mount it under windows, but dont have time now...
anyways, thanks to everybody for the suggestions and interest, maybe we'll crack it some day
You need to use an official RUU zip image - i.e. a PB99IMG.zip. Not an update.zip.
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
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