Related
Hi guys,
I was trying to unroot my nexus S using the guide found here (http://forum.xda-developers.com/showthread.php?t=1088494&highlight=unroot)
After clicking start on odin, it started to do its thing and then it failed all of a sudden. and now im stuck on the yellow triangle Downloading screen. I press and hold power nothing happens. i dunoo what to do. I am a complete noob. someone please help. I am attaching the image of the what the screen looks like (http://postimage.org/image/3dhtlidg/)
and here what odin looks like now (http://postimage.org/image/3eqh3vpg/)
ok guys, i took out the battery and put it back on and turned it on again and it powered on but now i have no signal or empty bars. it shows aeroplane now.. i tried different sims no difference.. i get no service.. i think this odin fail at radio damaged my radio somehow..someone please advise me.. please .. i did volume up button + power and tried to go to recovery but i get triangle with exclamation mark. so i took out the battery and reboot it to normal. no signal. just the aeroplane icon. Also when i put the phone in USB mode, i see folders like clockworkmod and im able to see my back up that i made before doing all this. However not able to access it in the phone. I also see that all my apps and everything is gone, but i still some apps folders in the usb mode. what should i do?
First, your link goes to a NxS 4G guide, but you state you got a NxS (non-4G). Which one you got?
Following is for the __NxS only__ (as I have no experience with the 4G):
If a little Droid is holding the "triangle with exclamation mark" then that is normal as you're accessing the stock recovery, press vol up + power again to see the recovery.
Once done that go here and get a full rom flashable zip for your device. Get a "signed" version if available as those are flashable via stock recovery. (*) Put the zip on your sdcard, reboot into recovery again, wipe everything the options allow you to, install zip from sdcard, reboot. You're done with an unrooted, stock phone.
If there's no "signed" you gotta flash the cwm recovery via fastboot first (USB drivers seem to be working and your phone is recognized). Go mount and storage and choose "Mount USB storage" Then continue after the (*) and leave out the reboot after putting the zip on your sdcard.
yeh crap i just realized.. i used the guide for nexus s 4g.. i have the gsm model (non-4g). from here in canada. damn i feeel so stupid... fml..
ok so behind the battery the sticker says my phone model is I9020A and then I went to the page yu asked.. and i found the following two of interest.
Android 2.3.4/GTJ61/UCKE1 Radio/KA3 Bootloader
Works on: I9020A
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Courtesy of XDA forum member scott8281
Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader
Works on: I9020T, I9023
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
My phone before all this mess occured was on GRJ22 build. So can i use the 2nd one here since its official and signed whereas the first one is unsigned. and like u suggested i should try to find a signed rom.
next question, how do i "wipe everything the options allow you to" ..
also when i do vol up + power and scroll to recovery and press power.. google logo comes up and then the droid with white triangle that has exclamation mark. I just cannot load into recovery :$
sorry for being so noob at this :$ But thanks for helping...
Breathe.
No, you cannot use the second flash "Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader" This is not for the I9020A variant.
I can tell you how to get everything back to stock. Are you willing to unlock the bootloader? There is no full signed rom for the I9020A.
You need to:
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide#Unlocking_the_Bootloader
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
Then install
http://forum.xda-developers.com/showthread.php?t=1033269
Then update back to 2.3.4
http://android.clients.google.com/p...5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip
Then lock the bootloader.
Oh okay. yes please I am willing to do anything to get this phone working to normal. and by the way, when i do volume up+power, i see locked stated - unlocked. doesn't that mean my bootloader is already unlocked. I also see the lock icon along with google when i turn on the phone.
cool6324 said:
You need to:
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide#Unlocking_the_Bootloader
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
Then install
http://forum.xda-developers.com/showthread.php?t=1033269
Then update back to 2.3.4
http://android.clients.google.com/p...5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip
Then lock the bootloader.
Click to expand...
Click to collapse
okay so basically i start following the guide from the point it says Installing the ClockworkMod Recovery Image since my bootloader is already unlocked.
one question though, right now when i connect my phone through usb, i am able to see the folder such as clockworkmod in sd card, so if im installing clockworkmod recovery, am i just reinstalling this again?
also for flashing cyanogen mod, i would choose the "method via recovery" right since my phone is not really rooted right now. I don't have the ROM manager app. Thanks a lot cool6324
The rom has to be for your phone. If your phone is an i9020A you got to take the first one you marked red.
@cool6324, I think his phone's bootloader is unlocked as his phone was rooted before and later then 2.3.x, means no Gingerbreak to avoid unlocking the bootloader.
---
forpulse, you got ADB set up and ready to go? (If not go to: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ to learn how to set it up)
If yes, download the rom to your pc. Also download the cwm recovery here. Boot phone into Android. Copy the rom on your sdcard (needs to be in the top folder). Copy the cwm recovery into the \tools (see below, (*))
Keep your phone connected via USB to your pc. Unmount the sdcard (the Droid got to be green not orange anymore), make sure you activated "USB Debugging" in settings (not sure of the right english terms should be in: "Apps/Programs" > Development). Now start a command prompt (windows key + r, then type "cmd", hit enter). (*)Navigate to the \tools inside ADB/SDK folder you created already or created by following the unlockr guide I linked above. To navigate simply type "cd <drive letter>:\<folder name>\tools and confirm with enter. Once inside the right folder you can start using the following commands:
adb devices (this should return you your device's id)
adb reboot bootloader (this takes a few secs and your phone will boot into bootloader menu)
fastboot flash recovery <recovery image name>.img (this should return a time and an "OK")
Now you can continue on your phone:
Navigate into recovery
Wipe > Factory reset, cache and dalvik cache
Mount and Storage > format system/boot
Install zip from sdcard, choose the ROM's name, install, confirm
"Go back" until you can choose "reboot system now", phone should boot into unrooted, stock Android now.
---
one question though, right now when i connect my phone through usb, i am able to see the folder such as clockworkmod in sd card, so if im installing clockworkmod recovery, am i just reinstalling this again?
Click to expand...
Click to collapse
That clockworkmod folder contains so called "Nandroid backups". This contains a full backup of your phone (__if__ you made one).
Did you make one before messing up your phone? If yes, follow my guide above to the point your going into recovery and just hit "backup and store", "restore" instead of flashing a new rom. I'd recommend to "wipe" "factory reset", "cache" and "dalvik cache" before though.
rentaric said:
The rom has to be for your phone. If your phone is an i9020A you got to take the first one you marked red.
@cool6324, I think his phone's bootloader is unlocked as his phone was rooted before and later then 2.3.x, means no Gingerbreak to avoid unlocking the bootloader.
---
forpulse, you got ADB set up and ready to go? (If not go to: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ to learn how to set it up)
If yes, download the rom to your pc. Also download the cwm recovery here. Boot phone into Android. Copy the rom on your sdcard (needs to be in the top folder). Copy the cwm recovery into the \tools (see below, (*))
Keep your phone connected via USB to your pc. Unmount the sdcard (the Droid got to be green not orange anymore), make sure you activated "USB Debugging" in settings (not sure of the right english terms should be in: "Apps/Programs" > Development). Now start a command prompt (windows key + r, then type "cmd", hit enter). (*)Navigate to the \tools inside ADB/SDK folder you created already or created by following the unlockr guide I linked above. To navigate simply type "cd <drive letter>:\<folder name>\tools and confirm with enter. Once inside the right folder you can start using the following commands:
adb devices (this should return you your device's id)
adb reboot bootloader (this takes a few secs and your phone will boot into bootloader menu)
fastboot flash recovery <recovery image name>.img (this should return a time and an "OK")
Now you can continue on your phone:
Navigate into recovery
Wipe > Factory reset, cache and dalvik cache
Mount and Storage > format system/boot
Install zip from sdcard, choose the ROM's name, install, confirm
"Go back" until you can choose "reboot system now", phone should boot into unrooted, stock Android now.
---
That clockworkmod folder contains so called "Nandroid backups". This contains a full backup of your phone (__if__ you made one).
Did you make one before messing up your phone? If yes, follow my guide above to the point your going into recovery and just hit "backup and store", "restore" instead of flashing a new rom. I'd recommend to "wipe" "factory reset", "cache" and "dalvik cache" before though.
Click to expand...
Click to collapse
Yes, i do have ADB set up ready to go but if I understood your right. Do I follow what your saying after following cool6324's guide or don't follow that and do what u suggest. I have not yet started out on his suggestion as I was reading everything and trying to understand. Also, when i go to download the CWM recovery. it says NS4G, so is this again for the sprint 4G model? or it also works on non-4g model which is what i have. I am just confirming this since I don't want to make the same mistake as above. :$
forpulse said:
Yes, i do have ADB set up ready to go but if I understood your right. Do I follow what your saying after following cool6324's guide or don't follow that and do what u suggest. I have not yet started out on his suggestion as I was reading everything and trying to understand.
Click to expand...
Click to collapse
The linked guide's result is equal to mine if you don't flash the CyanogenMod, but the rom cool6324 linked. Just make sure you get a full rom for _your_ device this time
rentaric said:
Copy the rom on your sdcard (needs to be in the top folder). C
Click to expand...
Click to collapse
which top folder are u talking about. is it ".android_secure" ? and I don't extact the ROM zip file right? i just put that directly in "top folder" ? and just to make sure i'm using "Stock-GTJ61-I9020A-Unsigned"
(100mb) found from one of your earlier links.
When I went to download CWM recovery from ur provided link, I saw different ones.. is it only for colour different purposes or there is actually a valuable difference amongst them? or do i download them all... i sound so stupid right now asking such questions:$
I'm really sorry If I am frustrating you with these stupid questions.. i've only had this phones for 2 days and its my first time with android... but thanks again...
forpulse said:
which top folder are u talking about. is it ".android_secure" ? and I don't extact the ROM zip file right? i just put that directly in "top folder" ? and just to make sure i'm using "Stock-GTJ61-I9020A-Unsigned"
(100mb) found from one of your earlier links.
When I went to download CWM recovery from ur provided link, I saw different ones.. is it only for colour different purposes or there is actually a valuable difference amongst them? or do i download them all... i sound so stupid right now asking such questions:$
I'm really sorry If I am frustrating you with these stupid questions.. i've only had this phones for 2 days and its my first time with android... but thanks again...
Click to expand...
Click to collapse
Good morning.
Yes, the difference between those recoveries is just color of text. !!Don't get the 4G version!!
The top folder is the one you access when the usb storage pops up on your pc. The zip file goes in there unextracted.
File size seems correct for a full rom.
Sent from my Nexus S using XDA App
rentaric said:
Good morning.
Yes, the difference between those recoveries is just color of text. !!Don't get the 4G version!!
The top folder is the one you access when the usb storage pops up on your pc. The zip file goes in there unextracted.
File size seems correct for a full rom.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Good Morning,
Alrighty, I think I have understood everything now, although, I'm at work right now so I will begin the process 8 hours later today and get back to you with the results... thanks for being so patient...
Hey rentaric,
i followed your guide and im delighted to say that my phone is back to normal or at least i think so lol.. everything is worked out and so far the phone is running fine. i made calls and what not.. the only issue i got now is... auto-rotate does not work. i cannot type text in landscap mode even though i got auto-rotate checked in display settings.. even in gallery, photos do not auto-rotate.. pretty much auto-rotate does not work whether i turn it on or off :S ..would you happen to anything about this? nonetheless, thank you so much for helping me out..
forpulse said:
Hey rentaric,
i followed your guide and im delighted to say that my phone is back to normal or at least i think so lol.. everything is worked out and so far the phone is running fine. i made calls and what not.. the only issue i got now is... auto-rotate does not work. i cannot type text in landscap mode even though i got auto-rotate checked in display settings.. even in gallery, photos do not auto-rotate.. pretty much auto-rotate does not work whether i turn it on or off :S ..would you happen to anything about this? nonetheless, thank you so much for helping me out..
Click to expand...
Click to collapse
Glad to hear it worked out for you to some degree. Sadly I have no solution to the not workign sensor part. See, I'm not pro myself, I'd just try widgetsoid app first. It got an rotate on/off function in its widget, if that wouldn't work for me I'd prolly flash another rom to see if it's the sensor trying to bully me. In the end hardware failures are still a possibility even on teh NxS.
sounds good.. no worries... i have a feeling this phone might have a defective sensor since it did not work also before with the older ROM which was GRJ22 xxkd1 ... but anyway i'll search/ask around if anyone knows anything... thanks again man...
Hey guys,
Forgive me for being frantic and (probably) not taking the steps needed to research this issue, or not taking the time to do so, but I'm sure you can all presumably imagine -if you've not been in this situation before- that it SUCKS not having a phone in this day in age...
My problem: Atrix 2 (Rooted + CWM Recovery) now won't boot passed the "M" Motorola logo upon start up. It won't even allow me to access the factory Android Recovery by holding down Volume Up, Volume Down, and Power. I think I inadvertently bricked the phone? (Hope not!)
Further, the "M" Motorola logo is skewed in appearance, like its not even loading correctly. I'm not sure what to do. This is my first time rooting and getting experienced with custom ROMS.
Anyone able to help this helpless sap?
Thanks is advance to your replies...
Step 1 is where you tell what you did to get into the state you are in. You wouldn't believe how far it goes toward fixing something if you know how it got broken.
Sent from my MB865 using XDA
If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.
KEB64 said:
If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.
Click to expand...
Click to collapse
Agreed pull the battery. If you run out of juice you'll be in some serious trouble.
Did you try to flash the fkz? Unless you have CWM on Boot it's the only way you can get your phone working.
Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.
pull the battery, put it back in, and hold vol up and down while turning on. choose ap fastboot at the menu. go to the thread in my signature and under the mirrors there is also a download of the return to stock script. run it while in fastboot and plugged in with usb. DO NOT pull the chord until it is done. when it is you should be good.
Apex_Strider said:
Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.
Click to expand...
Click to collapse
Yeah wiping the system partition is a no no unless you flash another rom afterwards. Do like ikrasner says and you should be back to normal.
Sent from my MB865 using XDA
Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!
can you read chinese?
Maybe I can solve your question,but poor of my english.
and what is your phone type?
at&t hktw or china ?
Sent from my ME865 using xda premium
Apex_Strider said:
Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!
Click to expand...
Click to collapse
It should ask you to install 2.3.6. Just go into setting>about phone>check for updates. Or you could go and install one of the roms that are based on 2.3.6 such as Lithium Sonya or SCv5.
Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.
Apex_Strider said:
Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.
Click to expand...
Click to collapse
do not flash this. unzip it on your computer, choose to boot into fast boot in the same place you chose recovery, then run the .bat file that was in the zip.
Sent from my MB865 using XDA
What that file does is reflash your system.img, basically restoring your phone to factory default. And just as a sidenote you cannot flash things with the standard Android Recovery. You need CWM.
did you try apboot mode and ise fastboot to flash system.img ?
Sent from my ME865 using xda premium
Still not working... not sure how to flash from fastboot. I don't have any options to run a file from there, or at least not sure ow to go about that.
Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium
dickluo said:
Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!
Apex_Strider said:
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!
Click to expand...
Click to collapse
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.
jfrank1485 said:
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.
Click to expand...
Click to collapse
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!
Apex_Strider said:
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!
Click to expand...
Click to collapse
I'm glad it work , keep it at hand before doing anything to your phone, it really helps
Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
The only way to download the stock rom backups is to remove the sd card from your phone, plug your sd card into a PC or other device with a card reader, download the stock backups, and place the stock backup rom files on your sd card. Finally place the sd card with the stock backup downloads into your phone.
These backups and information on how to go through this process can be found in this thread on page 2: http://forum.xda-developers.com/showthread.php?t=2001226
The key is to make a backup of your existing rom with twrp and then move the stock backups from your sd card to the twrp/backups/yourdeiceserial/ directory. That creates a backup directory which twrp knows to look for backups in.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app
UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
If that does not work you could drop it in water or something. You have not officially unlocked boot loader so you still have warranty. Or you could just tell sprint it quit working and act completely clueless. At least its bricked with warranty still intact.
matt2k12 said:
Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...
Click to expand...
Click to collapse
Both of the methods above are very effective. When I had the first photon I bricked it and just dropped it in water and did a claim. Depending on the insurance you have that way may cost you $100. The other method should work. When I first got this phone I did the exact same thing and to go back and unlock then flash twrp and in stall a stock backup someone had posted.
Sent from my XT897 using Tapatalk 2
UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Click to expand...
Click to collapse
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.
Hi again yall. You know once I got to thinking about it, I decided to check out the return policy on Amazon Wireless. They will accept any device under warranty for the first 30 days and it is up to Moto for the next 11 months of warranty coverage. They email me a packing label and it ships out 1 day and they ship out the new phone 1 day shipping. Hard to beat, just takes 2 days of shipping and some more fun times with my Epic, 10.1CM style, in the meantime.
Who's to say it wasnt some sort of hardware or software glitch that bricked the phone rather than my screwing around? Nobody knows and it isn't up to the consumer to prove his innocence. I bought everything legally, all the apps at the app store, and only ran the motofail2go root method. Wasn't running any custom Roms, Mods, or anything. I don't feel bad after they got me for another 2 grand for 24 months, and since I have been with Sprint for 10 years;l I have spent well over 10k or 15k with them lifetime.
If any other method pops up between now and when I ship it out I may give it a shot but if not, ah well, capitalism.
matt2k12 said:
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.
Click to expand...
Click to collapse
Try using adb. If your computer has drivers on it for phone you might able to get into fast boot. If that does not work I would try Sprint store first. Have locked my phone up several times while hacking wife off in progress and have used adb every time. Only time i have been truely scared is when i soft bricked my nexus 7. had to stay at work for two hours after i got off to get it to recover because i was scared of her lol.
---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------
If you get adb to recognize device you could take chance and officially unlock boot loader. Then flash twrp. There is a thread in general section about having trouble getting official update. It has a stock recovery in it. Trick would be moving files to recovery section of twrp
I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app
UnicronAlpha99 said:
I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.
I don't blame you, it sounds easier to exchange in your case any way. The main suggestion I have is if you are getting into any type of build.prop or operating system tweaks that have potential to lead to boot loops or cause the phone not to boot, then unlock the bootloader and install custom recovery.
The Moto-fail method seems limited to only be able to run apps that require root. For me this has no use as I want to be able to have complete control over all aspects of the Android OS. There is not a huge mod community for the Q as yet but I believe Cyanogen will be a reality as Interloper continues working on it. I came from an Epic with Cyanogen and soft-bricked it a minimum of 50 times. CWM was very forgiving on that phone, the Q is a lot more finicky and frustrating.
If you have insurance through the carrier then you are going to pay $150 for a refurb if something goes wrong and you hard brick the phone. If you unlock bootloader and install custom recovery then you have a fail-safe in the form of nandroid backups and restores. Then you can mod away with little fear.
Good luck on the new phone and I hope you don't give up after six days of modding with the Q!
Sent from my XT897 using xda app-developers app
matt2k12 said:
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.
Click to expand...
Click to collapse
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?
matt2k12 said:
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?
Click to expand...
Click to collapse
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.
befrosty8612 said:
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.
Click to expand...
Click to collapse
Awesome, I am wanting to do the backdoor root method again but, of course, may brick it. I dont think Amazon will keep sending me new ones.... but maybe!
befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?
matt2k12 said:
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?
Click to expand...
Click to collapse
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?
befrosty8612 said:
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?
Click to expand...
Click to collapse
Thanks for the response. So, all I have to do is: go to fastboot and flash a stock recovery image file and it will automatically wipe the phone, cache, everything, and restore the operating system? Sounds awfully easy! I found some stock files in this post : http://forum.xda-developers.com/showthread.php?t=2001226&page=2 Are these the ones you used before?
Last question: I can flash CWM or TWRP but wont be able to access them if my bootloader is locked, correct? So flashing a stock recovery will allow me to have my stock phone back again, locked and un-rooted? I guess if I cant get it to work with the stock recovery then I can unlock the bootloader and do a CWM or TWRP recovery and then flash the stock .img files?
Thanks again for your help. I already had root with the motofail2go method which I like using but seems like when I try and use some generic root feature from apps from the app store that it will crash/brick the phone cuz obviously those apps are generalized and likely to brick certain percentage of devices....
Ok what does this mean? Something with the bootlaoder obviously. Does it need to be unlocked?
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
y qrecovery1.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (5962 KB)...
OKAY [ 0.479s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.755s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
And on the phone screen it says "invalid image size for partition recovery" twice for both times I tried this method.
You will need to flash the system image as well if you want those, as the recovery image will only flash the recovery. The files in that link are for twrp only... so you'll have to be able to get there first.
With the custom recoveries, I'm not 100% sure whether or not you will be able to use them without being unlocked. I would wait to see if anyone else can answer that question for you, but if you did try it without an unlocked bootloader, you at least have the stock recovery to fall back on if needed.
Sent from my XT897 using xda app-developers app
---------- Post added at 09:16 PM ---------- Previous post was at 09:12 PM ----------
I'm thinking it could either be that your phone is full and the image you're flashing is too large to fit on the space available...
Or you're trying to flash custom software on a locked phone.
Hopefully someone is able to answer that a little better...
Sent from my XT897 using xda app-developers app
You can't alter the stock recovery (flash a custom recovery like twrp or cwm) in fastboot without having the bootloader unlocked. Your options are to unlock your bootloader, flash custom recovery, create a backup of your current setup, download one of the stock working backups, place it in the backups folder for twrp on your external sd card, and restore one of the known working backups in the development section (befrosty linked to one). Or you could use RSD lite to return to stock using a stock factory firmware flash. That involves connecting your phone to your PC and flashing the phone back to factory stock. Information on RSD Lite and links to the FXZ's can be found here.
http://forum.xda-developers.com/showthread.php?t=2095536
Sent from my XT897 using xda app-developers app
Hi all,
thank you for all your tutorial/answers.
I haven't found the answer to my question, so I would like to ask.
The setup:
My phone is a samsung galaxy sgh i-727.
I read all the tutorials on rooting/recovery.
I don't have a windows so I did as follows:
1) Put it into recovery mode. I did this by using a linux machine, together with Heimdall. I used the basic command on Heimdall and used Philz CWM. Everything went well.
2) I was able to put my phone in recovery - cwm mode.
3) I tried to root my phone. I downloaded and put inside my dcim card the SuperSU-0.93-Busybox-1.20.2.zip file. Then I chose to install from sd card. Everything seemed to go well.
4) After it was done, a message appears: your phone is now awesome! Press any key. I selected 'reboot phone'.
From that moment on my phone doesn't work. I mean, it won't turn on a home screen. I can put into recovery mode or download mode, but nothing else.
So I look for the troubleshooting part.
I did a wipeclean on recovery mode. Then I installed the downloaded root again. I check that I don't have a sticky power button.
Can anyone tell me what else can I do?
Thank you so much for your time. I'm eager to learn more about these procedures.
Lizzie
I would flash the stock firmware and start over. Look for vincom's stickies
jd1639 said:
I would flash the stock firmware and start over. Look for vincom's stickies
Click to expand...
Click to collapse
Thanks for your answer!
I have downloaded the stock firmware. However, I can't flash it. I'm using heimdall but I keep getting errors.
I tried to use a new recovery mode. I think one cyanogen recommends. I was able to do that by using the heimdall comands.
But now I enter the recovery mode and I can't find the sdcard. I can't mount it, and I keep getting error messages on the phone of the type:
'can't mount internal sd card!'
So I can't really use any other firmwares.
Thank you for reading,
Lizzie
dont remember ever seeing "your phone is now awesome! Press any key" message, my advice since youre a newb is to borrow/beg/steal a pc
Hey,
Tried to root my phone and things got messy.
I'm at a point where when I try to access the bootloader I get the "No command" screen, which I can bypass with the Power+Up keys and reach the "Android Recovery" screen.
I used "Wipe Data/Factory Reset" which didn't help much.
I can't do much more than that because Windows doesn't recognize my device and so I can't apply anything through ADB.
I tried to install the drivers again, but still nothing. My phone doesn't appear on the Device Manager.
Windows does make a sound of connected USB when I enter bootloader, but soon as it hits the "No Command" screen I hear the sound of a disconnected USB device.
Any idea how to make Windows recognize the device again so I could try to install things back with ADB?
Thanks!
OK, managed to solve this part after some reboots.
I'm now failing to ADB the stock image.
The phone says on top of "Andoird Recovery" that it's 7.1.2/NZH54D.
That's the stock image I've downloaded and when I try to ADB it I get on the windows terminal
"cannot read 'sailfish-nzh54d-factory-127f0583.zip'".
How do I move on from this?
OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.
I would start over from scratch. This guide is really good, it's for Pixel XL, but should be interchangable for Pixel 1 (non-XL), just be careful of the model specific files (salefish vs. marlin)
https://forum.xda-developers.com/pixel-xl/how-to/guide-android-8-oreo-root-stock-rooted-t3660591
TheAsker70 said:
OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.
Click to expand...
Click to collapse
Can't you acces bootloader with "adb reboot bootloader"?
Also make sure u switched on usb debugging in developer options.
Sent from my Google Pixel using XDA Labs
If you get to the screen where you can choose to enter recovery, that is the bootloader. The no command thing is something you always get when you choose to boot to recovery. When on the screen before the no command thing, plug it into your PC. If the PC recognizes it, use fastboot to access it. "Fastboot devices" will show your phone. Adb devices doesn't work there. Bottom line is, it sounds to me you're getting to the bootloader. Just not realizing it.
TheAsker70 said:
OK. Figured this one out as well.
I was flashing the wrong file. Needed to flash the OTA file "sailfish-ota-nzh54d-2163742b".
Now I have my Pixel up and running. OS seems to be there.
BUT... bootloader still not there. I still get the "No Command" page when I enter the bootloader and can only use ADB.
How do I move on from here? Still wanna root, add twrp and a different ROM.
Click to expand...
Click to collapse
The no command screen is a part of the recovery, not bootloader. My easiest suggestion for you is that with the phone powered on press the power button and select restart. Once the screen goes dark, press and hold volume down until it boots to the bootloader. If you can't get that to work then you sir have a problem.
Milly7 said:
The no command screen is a part of the recovery, not bootloader. My easiest suggestion for you is that with the phone powered on press the power button and select restart. Once the screen goes dark, press and hold volume down until it boots to the bootloader. If you can't get that to work then you sir have a problem.
Click to expand...
Click to collapse
Yup. I think I'm good now. Gave up on the ROM thing. Too much headache to maintain it. Sticking to stock. Imperfect, but less headaches.
I wanted to root my device mostly for Titanium backup.
The rest isn't that important to me.
Thanks for the help!