hi everyone, im new to these forums. i want to love my n1, but cant. my service is horrible here in miami florida. so bad that tmobile keeps giving me free months of service instead of a solution.
i was told about holding the phone a certain way, but its so unnatural. but i understand that a few firmware updates helped out the signal issues. me and my sons nexus ones are fluctuating 20-50 dB's at a time.
so i try to root using the cyanogen wiki's instructions. the second i type in adb devices into my windows 7 cmd window, i get the following. "adb is not recognized as an internal or external command"
i repeated the steps in the wiki and have no idea what i am doing wrong.
can anyone assist please?
Mod, if i posted in the wrong section i am sorry; feel free to move thread.
thanks all!
Here bro, this might help... "How to set up adb"
http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Did you run the adb command from the sdk directory?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
You need to download the SDK and use the adb from the SDK directory....
MaximReapage said:
Did you run the adb command from the sdk directory?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
No I used the windows cmd window. I saw the android cmd window but it wouldn't let me type in it. Was I supposed to type in the android window?
Before you go and unlock the phone and install cyanogen, are you sure you want to go down that road? I don't think there are any reception improvements in any of the custom ROMs, so if that's what you are hoping for you might be disappointed.
You may lose your warranty if you do it, and you are going to permanently lose the over-the-air upgrade system that Google uses to push upgrades out with.
sheek360 said:
No I used the windows cmd window. I saw the android cmd window but it wouldn't let me type in it. Was I supposed to type in the android window?
Click to expand...
Click to collapse
You need to read up a lot more on how your computer works, and directory structures, and cmd windows and all that. If you are already confused you could just end up breaking your phone. First thing is to install the SDK. Get that done, then read some more, etc. Do it slowly.
Clarkster said:
You need to read up a lot more on how your computer works, and directory structures, and cmd windows and all that. If you are already confused you could just end up breaking your phone. First thing is to install the SDK. Get that done, then read some more, etc. Do it slowly.
Click to expand...
Click to collapse
Thanks for the heads up. The sdk is definately installed.
I heard that the other radios perform better. I need a miracle, I drop 60% of my calls according to tmo. So does my sons n1's. My daughters cliq and wife's bold9700 are always on 3g
What Baseband version do you have installed on your phone? It's under Settings -> About phone.
You should be running the newest radio firmware already I would think.
PrawnPoBoy said:
What Baseband version do you have installed on your phone? It's under Settings -> About phone.
You should be running the newest radio firmware already I would think.
Click to expand...
Click to collapse
I don't know it off the top of my head. But its definately current.
Well if you want to check it out, I believe "32.26.00.24U_4.04.00.03_2" is the newest. If that's what your phone has then I don't think there is any value in unlocking.
An update from Google should be coming or announced before the end of the month, so maybe it'll have some fixes for you. If not, than at that point I would go ahead and unlock it.
i went ahead and successfully unlocked the boot loader. im trying to load the recovery.img via a terminal app on my phone but i get a message saying permission denied. i heard that there was a way of loading the recovery.img through rom manager, so i tried it.i got a message saying an error occurred while attempting to run privileged commands.
any ideas?
thanks!
seems like i dont have superuser.....
Yup, when I type su in terminal I get a message telling me that I don't have those privaleges. Any ideas? I'm Googling but can't find results.
i find the instructions in here relatively newb friendly. But read all carefully before rushing into action.
Stock to Root:
http://forum.xda-developers.com/showthread.php?t=636795
Recovery Image:
http://forum.xda-developers.com/showthread.php?t=611829
CM ROM (if that is what you would like to have)
http://forum.xda-developers.com/showthread.php?t=623496
and... do all the above first, before you mess with the radio image. all over the above is relatively safe/cannot brick your phone but wrongly flashing radio image can brick your phone permanently (especially if you run out of power or pull the battery during the radio update process)
Thanks. I'm er27. Do I flash with or without himen?
to make it very simple, i'd just recommend first:
1) flash Amon_Ra's recovery image 1.70 (i sent you the link earlier)
2) flash Cyanogen CM5.0.6 (I sent you the link earlier)
3) flash CM's google-addon (on the same page)
CM5.0.6 includes Himem, no need to flash separately.
See how it goes.... THEN you can try flashing radio to EPE54B, but please read all related to that careful. the command is simple, but if you pull your battery during the update, or the phone runs out of power, or you otherwise try to interrupt the process, your phone WILL BE permanently broken. Sometimes the radio update takes a long while (15 min or so), and it seems unresponsive, then you have 2 automatic reboots - those moments can be frightening. best would be to leave the phone plugged into the power socket while you doing it
shmigao said:
to make it very simple, i'd just recommend first:
1) flash Amon_Ra's recovery image 1.70 (i sent you the link earlier)
2) flash Cyanogen CM5.0.6 (I sent you the link earlier)
3) flash CM's google-addon (on the same page)
CM5.0.6 includes Himem, no need to flash separately.
See how it goes.... THEN you can try flashing radio to EPE54B, but please read all related to that careful. the command is simple, but if you pull your battery during the update, or the phone runs out of power, or you otherwise try to interrupt the process, your phone WILL BE permanently broken. Sometimes the radio update takes a long while (15 min or so), and it seems unresponsive, then you have 2 automatic reboots - those moments can be frightening. best would be to leave the phone plugged into the power socket while you doing it
Click to expand...
Click to collapse
damn you just scared me straight. is it possible that future cm roms include new radios?
sheek360 said:
damn you just scared me straight. is it possible that future cm roms include new radios?
Click to expand...
Click to collapse
just achieved root! but my google apps arent in the phone. gotta get epe54b in
All done. Thank you all for your help!8
Related
So for the past year I've had a grand ol' time playing with assorted ROMs and now I've run into a problem I can't fix. First, I'm 95% certain the microUSB on the bottom of my N1 is shot. It will still charge the phone, but cannot connect via Windows/ADB/Superboot or anything. I've tried different cables, different computers, different USB ports and different OSs... still cannot get any computer to recognize device. I'm not paying $200 for HTC to fix this (broken USB ports are not covered)... so here's where I stand:
I installed the Clockwork RomManager to try to DL and install ROMs more easily. It didn't work, it was unable to install anything, and it screwed up my original Amon_RA recovery. So then both means of flashing new ROMs were totally dead. Reluctantly, with no other choice (that I knew of) I reverted back to stock recovery and stock FRG83.
With the Stock ROM I lost Root privileges. And with the stock recovery program (the one with blue writing) I am entirely unable to flash ANY of the common rooted ROMs. I renamed a whole bunch (Cyanogen, Enomther, Rodriguez etc.) to the correct update.zip, but the stock recovery image refuses to flash any of them. It always fails on the Verification stage.
So I can't flash a rooted ROM via the stock recovery program, and I can't use ADB/Superboot/Fastboot to root the device via USB. How can I regain root? Are there any rooted ROMs that are certain to work with the stock recovery image program? Any other ways?
Since all my data is backed up with Titanium, I really need Root to get my life back! Thanks for any ideas!
If you're still on FRG83 (and not FRG83D), you may still be able to root on-device using Visionary, but I'm not sure which version of Visionary to counsel you to try.
If your USB port is broken, how are you charging it?
Which HBOOT version do you have? If none of the on-device methods are working, could you try the PASSIMG for FRF91 and roll back? Universal AndRoot and z4root should work on that build. From there if you want to re-upgrade and keep root, you'll need to take the pre-rooted update.zip format for custom recovery rather than the OTA.
Doesn't sound like it's broken... Weird. And you're 100% sure you have the drivers and everything installed on the computer?
Hi cmstlistand thanks for your advice.
I am now on FRG83D. I looked for Visionary in the market but didn't see it there.
The strange thing about the broken USB is that I'm still able to charge through it without any problems. This is why I'm only 95% sure it's broken... seems very odd that the wires for charging would still be making contact while the others wouldn't. (Please see in my OP all the things I've tried to get it to connect to a computer... certainly open to new ideas if I've missed any.)
I just checked and my HBOOT is version 0.35.0017. I'd be willing to "try the PASSIMG for FRF91" as you suggest. Would I just find the stock FRF91 and rename it PASSIMG and hold down volume down while powering on? Does that sound like my best option?
Thanks again!
KAwAtA said:
Doesn't sound like it's broken... Weird. And you're 100% sure you have the drivers and everything installed on the computer?
Click to expand...
Click to collapse
Sadly, no. I'd say I'm 95% certain...
The thing is I've tried to connect on my desktop PC with W7 64-bit, my XP laptop and another PC with Linux (Ubuntu and Kubuntu) all to no avail.
Here's what I've done on my main PC (Win7 64bit) to try and connect the N1 (which, btw, connected just fine a few months ago, albeit to a different W7 install). The problem might still be in here, and not in the hardware, so I'm open to any ideas.
1. Whenever I connect I get the "USB Device not Recognized" alert in the taskbar.Clicking on that alert yields no actionable information.
2. The Device Manager shows the exclamation mark by unidentified USB device. Uninstalling, Disabling and attempting to manually update the driver from within the Device Manager all have no effect. Windows says I already have the most current drivers.
3. Tried the USBDeview program. It's supposed to "show all hidden and previously installed usb drivers on your computer." It shows nothing related to HTC or Nexus or Google.
4. I tried manually installing the USB drivers from here.
5. I installed & uninstalled & reinstalled the Android SDK thinking that might fix the USB issue. It didn't.
6. Tried running W7 in Safe Mode and without firewall/anti-virus.
7. Tried three different cables on all of the USB ports on my PC.
All throughout... it's always "USB Device not Recognized"
There should be some PASSIMG files you can try at Shipped ROMs. Usually it's a ZIP inside of another ZIP, so you have to extract the inner file first and rename it PASSIMG.zip.
Visionary is not on the Market anymore, nor are most other rooting apps. You'll have to search for them on the web. So far I don't know of any apps that root FRG83D on-device.
Install pdanet on your pc, and try again. It's an easy way to update the drivers.
The sdk has changed with the gingerbread release, and you have to reload the drivers, etc...
Sent from my Nexus One using XDA App
danger-rat said:
Install pdanet on your pc, and try again. It's an easy way to update the drivers.
The sdk has changed with the gingerbread release, and you have to reload the drivers, etc...
Click to expand...
Click to collapse
I'd actually tried that before and forgot to mention it. So I just tried it again and no dice. At the point where you plug in your phone, I get the Device Not Recognized immediately in the taskbar. In Device Manager, there is no "Android Devices" category.
cmstlist said:
There should be some PASSIMG files you can try at Shipped ROMs. Usually it's a ZIP inside of another ZIP, so you have to extract the inner file first and rename it PASSIMG.zip.
Visionary is not on the Market anymore, nor are most other rooting apps. You'll have to search for them on the web. So far I don't know of any apps that root FRG83D on-device.
Click to expand...
Click to collapse
I tried the FRF81 from that site and yes it was a zip inside a zip. Renamed it to PASSIMG... but the installation failed at the verification stage.
Thanks for everyone's help so far. I'm totally at a loss with this thing. I don't even know if this is a software or hardware issue. All I know is that I'm dangerously close to driving a railroad spike through the screen.
Any other suggestions greatly appreciated!
JohnHenrySDM said:
I'd actually tried that before and forgot to mention it. So I just tried it again and no dice. At the point where you plug in your phone, I get the Device Not Recognized immediately in the taskbar. In Device Manager, there is no "Android Devices" category.
I tried the FRF81 from that site and yes it was a zip inside a zip. Renamed it to PASSIMG... but the installation failed at the verification stage.
Thanks for everyone's help so far. I'm totally at a loss with this thing. I don't even know if this is a software or hardware issue. All I know is that I'm dangerously close to driving a railroad spike through the screen.
Any other suggestions greatly appreciated!
Click to expand...
Click to collapse
If a passimg isn't working it's possible your on FRG33 or something else that doesn't like them. Just use visionary to root like suggested it's been taken down from the market so you'll have to find it here
Ozymandias88 said:
If a passimg isn't working it's possible your on FRG33 or something else that doesn't like them. Just use visionary to root like suggested it's been taken down from the market so you'll have to find it here
Click to expand...
Click to collapse
Visionary does not work on FRG83D, which is what the OP has. Thus my suggestion to try downgrading.
If you're on the newer HBOOT, try the KT_KR release of FRF91 (rootable with Universal Androot or z4root), or try FRG33 (rootable with Visionary). Both are available as PASSIMG files.
That's correct I have FRG83D so Visionary will not work.
Thanks for the suggestions Cmstlist.
Any advice on where to find the KT_KR release of FRF91? I'm searching as we speak, but not finding much...
EDIT: Never mind, just found it here Link. Downloading it now, I'll report back soon.
Thanks Again.
Ok I just DLd KT_KR release of FRF91, renamed it to PASSIMG, copied to root of SD card, rebooted holding volume down. Phone finds and starts to load PASSIMG but then I get the "Main Version is Older! Update fail!" error.
I'll look for and try the FRG33 PASSIMG next, but I'm pretty certain I'll get the same error.
Ok just tried FRG33 I found HERE.
It didn't work, but it didn't work in a different way.
HBOOT finds PASSIMG.zip and loads it (blue bar at top right). After loading it says (Checking... PASSIMG.zip) Then it stays there for a few seconds, and then just jumps back to the original HBOOT screen. There's no error message.
I guess where I'm confused now is that I currently have the newest version (FRG83D) installed. So won't all other PASSIMG files be older and therefore result in one of the above errors?
EDIT: Just thought of something else. For both of the above files I needed to rename them myself to PASSIMG. They were originally named Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip and PASSIMG_Passion_KT_KR_2.15.1010.2_FRF91_release_signed.zip. I was correct in needing to rename them, right? Just want to make sure...
Yes you'd be correct to extract and rename them.
Usually the main version error relates to HBOOT and not the OS version itself, which is why I was hoping FRG33 would work for you.
Sent from my Nexus One using XDA App
I see. Thanks for the info.
Still looking for any new ideas to try if anyone has them.
Is there any way I could just revert the phone back to a much earlier build, like ERExx ? Or any way to erase everything, but retain the unlocked state, and then load up a differrent build, one that's software rootable?
Or is it likely that I'm just grasping at straws here?
Rolling back to a much older built requires a modification to the misc partition to trick the HBOOT check... which you can only accomplish either with root, or over USB via fastboot.
Rooting FRG83D requires adb USB over USB. UNLESS... can you adapt the rageagainstthecage instructions to run them by typing or pasting meticulously into Terminal Emulator? Maybe that could root it.
Sent from my Nexus One using XDA App
Hmmm, good idea but I don't think anything involving a terminal emulator is likely to work, at least not with my skill set. I've already tried one other method that relied on terminal, and it failed because I couldn't get SU. Without root, I couldn't get super user permissions, without those, terminal was useless.
I just got off the phone with the insurance company (Asurion). I filed the claim and am now waiting to hear back what my options will be. The guy thought that since the N1 is no longer available, I'd be given a choice between a G2, a Vibrant or a Mytouch (not sure if 3g or4g model). And if I don't want any of those, then I'll just keep my N1.
So, the clock is ticking down! ANY ideas whatsoever are greatly appreciated! I'd much rather keep my N1...
JohnHenrySDM said:
Hmmm, good idea but I don't think anything involving a terminal emulator is likely to work, at least not with my skill set. I've already tried one other method that relied on terminal, and it failed because I couldn't get SU. Without root, I couldn't get super user permissions, without those, terminal was useless.
I just got off the phone with the insurance company (Asurion). I filed the claim and am now waiting to hear back what my options will be. The guy thought that since the N1 is no longer available, I'd be given a choice between a G2, a Vibrant or a Mytouch (not sure if 3g or4g model). And if I don't want any of those, then I'll just keep my N1.
So, the clock is ticking down! ANY ideas whatsoever are greatly appreciated! I'd much rather keep my N1...
Click to expand...
Click to collapse
Oops I pressed thanks instead of quote =)
What I was suggesting is that you try looking at the manual instructions for rageagainstthecage and adapting them to Terminal Emulator. Those instructions don't require you to already have root - they *give* you root. But now that I read them over, it seems there's also some adb start/stop/etc commands that I'm not sure you can replicate in Terminal emulator. Back to the drawing board...
If Asurion is willing to give you an MT4G or G2, I say go for it.
Just on a total whim... try booting up your phone without the SD card, or with a different one... does it still fail to recognize over USB?
cmstlist said:
Just on a total whim... try booting up your phone without the SD card, or with a different one... does it still fail to recognize over USB?
Click to expand...
Click to collapse
Ha ha you had me all excited there... first chance to try something new! Alas, no luck. Used the original SD card and tried again without one; still got the exact same Device Not Recognized.
I talked to another rep and they alluded that the MT4G was not going to be an option, but that the 3G probably would. The3G seems inferior, though.
You think the G2 would be a fair trade? How about the HD2 or the Vibrant? Any others come to mind?
Since I'll need to pay a $130 deductible (not to mention the $5 I've been spending every month for the last year) I want to make very, very certain that my new phone is not inferior to my beloved N1.
Thanks again; you've been very generous with the ideas!
I'm been searching the Nexus One Q&A section for an answer to my problems, but I couldn't find a solution. I'm running a stock version of 2.3.3 on my phone. It's never been rooted, and I have never rooted a device as well. I'm entirely new to this and have no idea what I'm doing. My device has no warranty but I'm still concerned about it. Again, I have no experience at all.
Also, I don't know if I would want to unlock the bootloader as I could lose everything. If there is a way to retain everything reliably (I don't know if those back-up applications are the most effective) that would be convenient.
So, can anyone help me root my virgin Nexus One?
Thanks for your time,
Tread Fox
Mybackup pro backs up apps and data. After you root you can use titanium backup. Also smsbackup and restore for your SMS :]
Alright, that's re-assuring. But what about actually rooting the phone?
Hmm I can't help with rooting because I have an Evo, just sharing some backup knowledge :/
You can use this threads wiki for the N1 and the stickies here:
http://www.nexusoneforum.net/forum/nexus-one-development-hacking/
You need to read several guides until you get a good idea of what you are doing and why.
Use the apps mentioned above to back up your phone info, once rooted you can do a complete and immediate phone backup of everything, like a full image pc backup.
If you do the one-click method, make sure it is for you OS, you will be limited in some things you can do, like fastboot commands and will be unrooted if you dl OTA's.
Read, Read, Read!!!
Before you flash a rom read the op page carefully and the last 20 pages for tips, info, issues etc.
Ken
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
You probably saw this in XDA wiki for N1:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
I would unlock, more options as you get more into flashing and you can't be unrooted by Google OTA's.
This is good guide for the S, but you can glean steps and maybe better understanding for the process. At the bottom in related posts is a root guide. I like the steps, but things like the fastboot and superuser may not be for the N1. However you can find them online. Just an easy to understand guide.
http://jaxov.com/2011/02/install-android-2-3-3-gingerbread-on-nexus-one-manually/
TreadFox said:
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
Click to expand...
Click to collapse
Sorry man, just got your message (phone died on me, and I've been playing with my other toys anyway...)
Yes, your options are to unlock the bootloader or roll back.
Both options will lose all date, so you need to backup either way.
My preference is to unlock the bootloader, but I can understand why people may not want to. Unlocking the bootloader can effect any warranty that's remaining on the phone (the phone has a 1 year warranty, no matter who owns it).
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Read my signature, execute PASSIMG method with FRG33. if it doesn't work (and sometimes it doesn't) - you're out of luck.
TreadFox said:
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Click to expand...
Click to collapse
This is how to go back to FRG33: http://forum.xda-developers.com/showpost.php?p=11745519&postcount=21
But if I were you, I would just unlock your bootloader. Makes life easier.
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
TreadFox said:
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
Click to expand...
Click to collapse
No, nothing has changed. You need to have the Android SDK set up properly. Then just boot into the bootloader by holding down the trackball while pushing the power button. Then open a command prompt in the directory where the fastboot.exe file is (probably C:\Program Files\Android\android-sdk-windows\tools) then just type: fastboot oem unlock
Follow this to set up the, it's easier (just the first post):
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA Premium App
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
TreadFox said:
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
Click to expand...
Click to collapse
If you feel like you are in over your head, you probably are, and have not done enough reading. I just looked at danger-rat's post in the link he provided, and it seems quite straight forward, no? He even tells you how to install the drivers. "Step #3" under "To install the drivers" in the first post TELLS you that windows will detect new hardware and will ask you to install a driver. What seems to be the problem?
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
TreadFox said:
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
Click to expand...
Click to collapse
Well, after you have installed the driver that the computer asked you to install. That's just the driver needed to sync your file and stuff on your sd card. The other driver and adb setup is needed to actually access your phone.
So I asked for it to install the wrong files? What files do I install? Because from that guide it said point to usb driver. I'm only following the guide like you all asked, and nothing happened.
You don't launch fastboot by clicking on it windows.
Sent from my Nexus One using XDA App
first post, yes, i'm new to this... (forum, not flashing, not entirely anyway, i did fiddle with Sony Ericssons and stuff, kindergarden compared to androids)... but not an idiot, to the point:
firmware config. version seems to be RTGB, great britain, right? wrong, a RTUK is not it. I am sort of lost, i bought the phone with 2.1-update1, the 2.2.1 update has not yet been rolled out in my backwards country, so i did an official update over the internet with motorola app etc etc. I have no idea what was the 2.1 fw config. ver., but it strikes me as weird that i have a RTGB one now, the packaging/box/manuals all were German or something that looks like German. And now, i got myself RTUK sbf file, and RDS lite fails to do anything. I require assistance, and an explanation if possible as to why this didnt work? if i chose the wrong sbf, why does it show me having RTGB? and finally which sbf to take and from where (two german one's are available on this forum), but i've seen only one RTGB and it was only 2.1. For comparison, the friend bought the same phone on the same day, but she got one with a qwertz keyboard, mine is normal qwerty, fw config. ver. shows VFDE, did not update hers, it's still 2.1-update1. I can only assume that VF is german for RT and that her phone did not come from an unknows source. The phone company selling these obviously imports them, possibly even from random countries or EU countries at least...
however something did happen, my battery in the notification seems to be not present, there's just a question mark inside what appears to be an empty battery... apps that show battery levels work fine... although, scratch this last one, a reboot fixed it, even though i have not seen it before.
also, help me rack up some posts ^^ ask for info or whatever, i'd like to give a shot at improving my android...
Check the link below. You will get both service and non-service versions of 2.2.1 sbf's.
http://and-developers.com/sbf:milestone221
VF would be vodafone ( service version) while RT would be retail version.
Sent from my Milestone using Tapatalk
Thanks, gonna try asap, will come crying if it explodes in my face...
SuicideTree said:
Thanks, gonna try asap, will come crying if it explodes in my face...
Click to expand...
Click to collapse
It wont. I have done it many times and my face is still intact, as you can see from my avatar.
Sent from my Milestone using Tapatalk
now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]
SuicideTree said:
now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]
Click to expand...
Click to collapse
which version of rsdlite and what OS? rsdlite should not cause your OS to crash.
oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.
SuicideTree said:
oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.
Click to expand...
Click to collapse
Try it and see if it works.
Just finished. Seems to be good. Gonna Continue with the guide then ^^ Many thanks.
instead starting a new topic IDIOT QUESTION but... can someone give me a detailed dumbed down version of this instruction bellow:
If you applied an OTA update before, there is a script run at every system boot that checks and re-flashes the recovery when its checksum doesn't match. In such case, you have to avoid booting to android after the vulnerable recovery flash. Boot directly to recovery when RSD Lite restarts the phone (hold camera button) and from there remove the /system/etc/install-recovery.sh file.
rm -f /system/etc/install-recovery.sh
i am getting this
E:Cant open /cache/recovery/command
just upon entering AOR (power+x)
trying to apply the update regardless i get this
- install from sdcard
finding update package
opening update package
verifying update package
E:EOCD marker occurs after start of EOCD
E:signature verification failed
Instalation aborted
what is the meaning of this?
possible solutions:
"It seems that the key to successful recovery flash in some cases is to not let the phone to boot to android or recovery until the RSD Lite will signal PASS. When the RSD Lite is restarting the phone during flash, hold the D-Pad Up, so the phone enters the bootloader again immediately."
does this work? DIDNT WORK, so i still need help
i'm still combing through many threads mentioning this... either please tell me this works or point me in the right direction -_- thanks
Once you flash the official sbf, you need to flash the vulnerable recovery to enable you to run openrecovery which is used to flash custom roms and much more.
There is a script which checks your recovery image everytime it boots and replaces it with the original if it finds any changes. So you need to remove that script.
Procedure would be as follows.
1. Download and extract androidiani openrecovery to the root if your sdcard. You should have a update.zip file and openrecovery folder.
2. Flash official sbf.
3. Flash vulnerable recovery sbf. When the phone restarts and before it displays Moto logo, press and hold the 'x' key on your keyboard. You should see a triangle with exclamation mark. Press volume up + camera button and choose apply update menu option.
AOR should load up. Choose console option and type the following commands.
rm - rf /system/etc/install-recovery.sh
reboot
That's all.
Sent from my Milestone using Tapatalk
okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?
SuicideTree said:
okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?
Click to expand...
Click to collapse
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.
I suppose there's no harm in trying that, i already had to rename it to something shorter, cause it wouldnt even give me the Start button.... brb
skadude66 said:
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.
Click to expand...
Click to collapse
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
You helped me out with that sileshn!
Yeah, I'll keep this thread up and I'll see what issues he's got.
sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moved files around, renamed and stuff... weird
EDIT2: by the way, is it normal for the vulnerability file not to show any file properties in RSD Lite?
SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moves files around, renamed and stuff... weird
Click to expand...
Click to collapse
Once you get VR, rooting and flashing a custom ROM is a piece of cake, so it shouldn't be that bad once you get there.
SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
Click to expand...
Click to collapse
If you want to flash CM, just install GOT 2.2.1 from here and forget about VR. GOT has VR injected into it. Use the Retail UK sbf.
Once you have CM, you have root.
@skadude : Didn't know it was me.
is cm7 much better over cm6? cause i was looking into that ^^ however if the end goal can be achieved easier with got cm6 i should give that a try, but, what if i wanna play around with this stuff later or something? i'd like to understand what's happening at the moment... anyway, if i go with got solution what are the steps? flash uk sbf, then got or... then cm?
also, got or is better than aor? except apparently having vulnerability alreay in it... anything else?
thanks for all the help, sorry for being not too enlightened, i'll get there ;]]]
Okay, so now we have 3 Atrix HD's in the house and except for the unremoveable battery thing, and the short "battery life" when actively using it, I'd say we pretty much love them. However, I decided to remove some apps, etc. and managed to get my messages, camera and gallery to the "not working" and basically non-existent point. Now on startup I'm getting the Android is Updating message with the never-ending swirl of Starting Apps... I'm positive I've waited long enough as I set it down and went back to bed just to wake up and still see it.
Info - phone IS rooted
running the "jellybean" update
Unfortuanately a couple weeks ago, I UNCHECKED the sync photots for both facebook and gmail, so there are pictures I really don't want to lose.....
I'm definitely not a "pro" like lots of them up here, but am capable of following directions. I'm pretty sure I have to "unroot" my phone via USB/SD card through my laptop....Any help would be greatly appreciated... and the more specific the directions the better!! :cyclops: LOL... Thanks so much.
/COLOR]
Sounds like you deleted a critical OS file. You need to flash back to stock again. Is your boot loader locked or unlocked?
Don't remeber...
ai6908 said:
Sounds like you deleted a critical OS file. You need to flash back to stock again. Is your boot loader locked or unlocked?
Click to expand...
Click to collapse
I Don't rememer if I unlocked the bootloader. Is there a way to check? Thanks.
Follow what's in the website to reload your stock image...
http://www.andromods.com/tips-trick...-qinara-stock-original-firmware-fastboot.html
ai6908 said:
Follow what's in the website to reload your stock image...
http://www.andromods.com/tips-trick...-qinara-stock-original-firmware-fastboot.html
Click to expand...
Click to collapse
I've been trying and I've fallowed everything to the T but everytime it says it falls.
I'm not sure...I have used it before and was able to restore...are you sure it's not a hardware issue?
Sent from my HTC_Flyer_P512_NA using xda app-developers app
Okay, here's where we're at.... it is no longer frozen on that screen and goes thru the setup w/ my gmail, etc.... but then I have a black screen (except for the top row icons...). I can pull down the settings menu and see everything there, but I have no "homescreen"....It's black. It seems like we're in the right direction and I know it's not dead. Anything??
Also wanted to thank you for the help. This place is ALWAYS amazing....
Hey, my son and I are wondering since it's already running 4.1.1 and we can't downgrade, what about flashing a custom rom? Will that flash a totally complete, full home page and everything?? Just a thought.
While trying to search for answers I came across a "xoom forums??" post with a tablet that was doing exactly the same thing....multiple people had that problem, but doesn't seem to have been answered...... not sure if I'm suppose to post links to that or not, but at least I know I'm not alone.....
If you're rooted, than I'm assuming ADB debugging is on. You should be able to unlock your boot loader and load CWM recovery. From there you can wipe cache and dalvik cache. If that doesn't help, you can reflash a stock ROM zip from Skeevys thread. Flashing a zip won't touch your SD card
There is official 4.1.1 available...you can try flashing that...you dont need to downgrade.
Okay, my son installed safetystrap (whatever that is...lol) and when you click Operating system, it says "there is no operating system installed are you sure you want to reboot????
Is this fixable?
Note: We have two other identical Atrix HD's in the house if that helps for any reason.....
Well that's what we are trying to figure out is how to install OS...Lol..
Try install system using fastboot... Look for skeevedudes guide...its in this forum somewhere...
Sent from my MB886 using xda premium
LOL....okay, so do yoiu see why my son says I'm not "ALLOWED" to have a rooted phone if this happens again..... Guess I was just glad to SEE it written out, so that it's a little more def what's going on - but I'm sure everyone up here (except me) already knew that!!!
He's not around today, so my phone is just "sitting" saying "creating rom slot" but never gets off that screen. The good thing is that we can see it's actually charging and we weren't sure before....... Does this sound like something that will eventually be repairable??
You have a soft brick...yes it is fixable...
Okay, thought I had already posted this before but I guess I never hit the submit ....
Before safety strap was installed, we could get the phone (minus the homescreen and os) to come on....the settings, wifi etc.....No we can't seem to get to that point with the safetystrap on. It just goes completely blank and won't let safestrap connect to the computer via usb.
Apparently there is also no way to remove SS without an opperating system. This doesn't sound promising.....ugggg..... I so want my phone back.
Any help would be greatly appreciated.
OK dude. Follow my instructions.
Hold down power and both volume buttons all at once until the phone screen turns black, then continue holding the volume buttons. You will get a menu. Go to AP fastboot mode using the volume down button, select it with the volume up button. Plug your phone into your computer with a data cable. Download RSD lite and the MOTOROLA drivers from the MOTOROLA website. Install both. Download the 4.1.1 sbf file for your phone, there is a thread for it here in the AHD forum. Its a zip file, extract it to your desktop. Open RSD lite, click the browse for file button, select the XML file inside the folder you just unzipped. Hit flash. If you get any errors, let me know I'll send you a different XML file with the getvar lines removed.
Okay, will get it started..... Thanks so much. My son has been working on this for hours and hours. You have no idea how much I appreciate this place and everyone who helps out!! You guys rock! Will let you know what we get.
Here is the website for what youngunn mentioned...
http://www.andromods.com/tips-trick...-qinara-stock-original-firmware-fastboot.html
[FONT="Comic [SIZE="3"]Okay, my son (BlackestPain) is too new here to post the picture links, so I copied and pasted. They're just downloads from his camera pictures. This is where we are right now after following suggestions....[/SIZE]MS"][/FONT]
Okay, here is what I've (chixwithkidz5' son) tried.... Please cut me some slack because I haven't been doing this stuff long....
Getvar file
Getvar removed
RSD Lite connected
RSD Lite failed
\
***** this is what the phone reads after everything
What am I missing ? Thanks - I can use all the decent help I can get.
I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
That's a rather non-descript post. Who's your carrier, what Rom's are you talking about, any custom kernels, did you perform a wipe before installing? As far as the Audio goes, I've got no complaints from the speakers nor using headphones (both hardwired and BT headphones). You do realize that the first boot after installing a fresh Rom can take several minutes, some as long as 8 minutes while everything is set in place. More info so that we can help, please.
alucke said:
I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
Click to expand...
Click to collapse
lol your doing something wrong.
i have flashed most of the available roms, in total hundreds of times, never failed to boot, not even once.
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Is this a rant or are you asking for help? This is a development forum, so not really the place to rant. If you want help, please ask specific questions whilst supplying relevant information
Need education
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
---------- Post added 21st September 2015 at 12:09 AM ---------- Previous post was 20th September 2015 at 11:59 PM ----------
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this Android phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online by self at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus 6 is back in order. I some how managed to use the Root Tool Kit v2.0.4 and "pushed" the factory, I downloaded from Google, to the phone. I assume this restored my ABD allowing debug thereby establishing USB connection between PC and Nexus 6, I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the Nexus 6 bootloader or Fastboot.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
This is the most idiotic post I've seen here all day. Seriously sell your nexus 6 and go buy a different phone if you don't like the phone or face the fact that you either don't know how to use a nexus device or you have a defective phone. But I'm almost entirely convinced this is 100% user error
Sent from my Nexus 6 using XDA Free mobile app
ray6279 said:
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
Click to expand...
Click to collapse
here is a good place to start
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
good luck!
Android documentation is kinda lacking
Its not terrible... Its just not entirely coherent, well organized or complete. A lot of poking around and learn by doing, patching together threads that document how things work ect...
Here is my suggestion:
Follow the second link posted by simms22 above, this one here: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Go here: https://developers.google.com/android/nexus/images?hl=en
And download the latest image for your phone (shamu, the images at the bottom of the list are most recent. All carriers currently use same build, unless your on tmobile or Fi)
Use some kind of unzipping program (not sure if winrar can do .tgz, if not just google "Windows .tgz") to decompress the image you download. This will have a few .img files in it and a .zip Unzip the .zip for the rest of the partition images for the phone.
With these you can use fastboot to re-format partition to stock.
Here is an older guide, while devices may vary a little... and things have changed since 2011, were still mostly talking about system, boot, recovery, data....
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
I would say read through the above guides thoroughly, then manually update your phone to stock.
You will notice the stock flash-all script will
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.10.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.101.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy48m.zip
You probably don't want to do all this... You will notice the last command I showed is fastboot -w update image-shamu-lmy48m.zip (assuming you downloaded the lmy48m image)
We already unzipped this, so rather then flash it in bulk (flashing userdata.img will wipe device) lets flash everything but leave data in place.
So get fastboot working, go to bootloader, and as the script does
With fastboot:
Flash the bootloader
then use fastboot to reboot, to the bootloader
flash the radio
then use fastboot to reboot to the bootloader
then fasboot flash system, recovery, boot and cache images, skipping userdata to avoid wiping the sd card.
At this point reboot. It may take a while for the first boot as android sets itself up and optimizing applications. If things appear to be hung give it 10 minutes before forcing a reboot checking your images and trying again. Pay attention to the output of the commands and make sure there are no errors. If there are read them, and google them.
Now you should be able to boot, and you will be fully stock. This is what it takes to recover from almost any situation. Often you can just flash system to update. Boot will overwrite your kernel, so it is often skipped when custom kernels are used... particularly when not encrypted.
Now find the website for twrp and find the image for your device, then go back to bootloader mode and flash recovery, after flashing reboot directly to recovery.
Also find chainfire's website with the recovery flashable supersu (should be a .zip)
Make sure the supersu install zip is on your phone, and the recovery is on your computer.
Reboot to bootloader and fastboot flash twrp to your recovery partition, then immediately reboot to recovery mode to finish the install.
In recovery make a backup of your working stock system.
After that install supersu
Reboot, and you should be stock and rooted with a backup of your completely stock system.
From here if your want to install a rom reboot to recovery, wipe caches, system and data. On future upgrades backup first, and try only wiping system and caches, then flash the new version of the rom and you wont have to set anything back up. You will have to reinstall xposed if your use it, as well as supersu if your rom does not include it for some reason.
If you do all that, read those guides to the point where you understand each step, and read the thread or at least the last hand full of pages of any rom or utility that you use... Things should work pretty good.
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
And likewise to this post , useless as well
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
nevermind
simms22 said:
nevermind
Click to expand...
Click to collapse
:laugh: :laugh:
Was going to post, and had this thought also....
btw JJD loves his N6 and his speakers Rock!
#nuffsaid
Nexus 6 ftw!
disturb1 said:
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
Click to expand...
Click to collapse
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it either.
What file manager do you use, and did you have gvfs-mtp or kio-mtp installed?
What utilities were you using to mount the mtp drive?
These instructions are for arch linux, https://wiki.archlinux.org/index.php/MTP#simple-mtpfs (I use simple mtpfs), adapt them to your distro, find your distros documentation.
But then you don't really need it to show up in the OS? Does fastboot recognize it? Have you installed udev rules for it?
ok, thanks for all the input. I will give the nexus 6 a try again, root it. Can anyone point me to a custom rom that is somewhat close to stock?
I like Pure Nexus
scryan said:
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it
Click to expand...
Click to collapse
Not sure if I just have issues with lollipop or the hardware and lollipop
I have it rooted now and also still hate it I don't have the sound issues that some have but freezing was a constant with nexus T-Mobile stock ROM or maybe I have a lucky lemon ether way
I don't blame others or look to others to do my rooting rom installation or themes nor do I assume that it the phone every time all I am saying is we need to stop blaming every confused user as noob and assume people are not trying to learn
I been here 3 years but I lurk and learn and move on but I constantly see issues of flaming it is sad ...I see your reply and that fact that you offered help is what I like to see what I would offer if I knew an answer..
Honestly I am just not a fan of the phone but I made my bed and in it I must... hack at it till I am happy...