Database Info

is my nexus S bricked? please help. :(

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...

[Q] Downgrading Nexus S from ICS to Gingerbread.

Hello there,
I've just got a Nexus S which has ICS installed. I must say I've used Android before but am no expert, especially when it comes to the whole ROM scene. While I am a very technical user, from my online research I haven't yet been able to figure out how to best go about the downgrade to 2.3.6.
My concern being that this is not stock anymore and I would not want to brick it by treating it as stock and simply following the standard downgrade or ROM flash directions.
I am attaching a screenshot for everyone to see exactly what I've got on the device.
Any help with this would be immensely appreciated!
Cheers.

Since you said you're a technical user I assume you know how to use fastboot and stuffs. To downgrade to GingerBread, you only need to install a custom recovery (ClockWorkMod) for your phone model and flash a full OTA package. I guess that's all

Well if the phone already has ICS installed, I'm pretty sure it also has Clockworkmod Recovery(aka. CWM or CWR).
Try this:
Turn off your phone.
Turn it on by HOLDING DOWN the power button AND the volume up button. After 2-3 sec. you should see a menu. Scroll down 2 clicks with the volume down button, you should land on 'Recovery '. Press the power button to enter CWR. (Clockworkmod Recovery)
If this procedure takes you to another menu, then you have a functioning CWR. And if so, I would recommend trying one or more of the fine roms in this forum under 'Android Development'. Many of these roms have a lot of features and fixes that you would miss once you've had them.
Try it out, and happy flashing.
PS. To flash most roms, download the rom on your mobile. (it's a zip-file) and go to CWR. Choose 'wipe data/factory reset' and then go to 'advanced' and there you should choose 'wipe dalvik cache'. Go back, choose 'install zip from sdcard' and then 'choose zip from sdcard'. Locate the rom you downloaded and choose it. This will flash the rom. Go back and choose 'reboot system now'. The first boot on any rom will allways take longer than usual. Usually about 2min. Enjoy! ;-)
Sent from my Google Nexus S using xda premium

swaipa said:
Well if the phone already has ICS installed, I'm pretty sure it also has Clockworkmod Recovery(aka. CWM or CWR).
Try this:
Turn off your phone.
Turn it on by HOLDING DOWN the power button AND the volume up button. After 2-3 sec. you should see a menu. Scroll down 2 clicks with the volume down button, you should land on 'Recovery '. Press the power button to enter CWR. (Clockworkmod Recovery)
If this procedure takes you to another menu, then you have a functioning CWR. And if so, I would recommend trying one or more of the fine roms in this forum under 'Android Development'. Many of these roms have a lot of features and fixes that you would miss once you've had them.
Try it out, and happy flashing.
PS. To flash most roms, download the rom on your mobile. (it's a zip-file) and go to CWR. Choose 'wipe data/factory reset' and then go to 'advanced' and there you should choose 'wipe dalvik cache'. Go back, choose 'install zip from sdcard' and then 'choose zip from sdcard'. Locate the rom you downloaded and choose it. This will flash the rom. Go back and choose 'reboot system now'. The first boot on any rom will allways take longer than usual. Usually about 2min. Enjoy! ;-)
Sent from my Google Nexus S using xda premium
Click to expand...
Click to collapse
Not necesarilly, CWM not always remains flashed and have to reflash repeatedly. Try what was recommended here, if not, download Rom manager and reflash.

That worked. Turns out I already had everything I needed to install from an archive.
So I downloaded the official 2.3.6 full ROM and got it installed.
The problem I am facing now is that as soon as the phone boots up, I get a sequence of errors, the first one being "The process com.google.process.gapps has stopped unexpectedly. Please try again."
This gives me a "Force close" button, and that's about it. Then there are subsequent errors for android.process.acore, com.android.providers.calendar and then it just sort of loops back and forth between those.
Unfortunately the problem here being that I cannot tap the Android to get started or anything like that. It looks like I am pretty much stuck.
swaipa, I followed your instructions and everything worked seamlessly.
Any clue as to why I am getting all of these issues now?
Edit: nevermind, I just did the same thing again and it seems to be working well!

Kudos my friend, you're on to a life of flashing.. ;-)
Sent from my Nexus S using xda premium

cant go beyond recovery menu using i9023 with ICS any ideas ?

I able to downgrade from 4.0.3 to 2.3.6
Here is what I did...
http://kishanrathod.blogspot.com/2011/12/downgrade-nexus-s-from-403-to-236.html

hey
http://en.miui.com/a-1.html try this steps and it will work.
At "Downloading flashing tools and ROM pack" instead of ther rom, you should download the official OTA for your model from here http://forum.xda-developers.com/showthread.php?t=1063664.
good luck...
i have a i9023 a put first 2.3.3 and i make de update to 2.3.6.
good luck!

just a question please :
What does "install unlocked boot" or "fast boot" mean , Will it unroot the device ? and after that , If I will install a stock 2.3.6 ROM , will I return 100% factory (including the stock recovery) ?

i`ve check my recovery and it is stock like i had before.
after you finish downgrade LOCK the device using UNLOCK start bat and write LOCK instead of UNLOCK.

euskode said:
That worked. Turns out I already had everything I needed to install from an archive.
So I downloaded the official 2.3.6 full ROM and got it installed.
The problem I am facing now is that as soon as the phone boots up, I get a sequence of errors, the first one being "The process com.google.process.gapps has stopped unexpectedly. Please try again."
This gives me a "Force close" button, and that's about it. Then there are subsequent errors for android.process.acore, com.android.providers.calendar and then it just sort of loops back and forth between those.
Unfortunately the problem here being that I cannot tap the Android to get started or anything like that. It looks like I am pretty much stuck.
swaipa, I followed your instructions and everything worked seamlessly.
Any clue as to why I am getting all of these issues now?
Edit: nevermind, I just did the same thing again and it seems to be working well!
Click to expand...
Click to collapse
im also getting this same issue from installing GB via odin.
cant work out how to fix it.
i dont fully understand swipa's instructions there

[Q] [q] cant enter CWM recovery ??

firsth of all hi to everyone, im new here , so be patient.
i was searching on the forum and try to solve my problem, but no succes.
all the methods ive tried are a no go
my problem here is that im already rooted (razorclaw tool), superuser installed aswell, so i dont know what else do i need to enter on the recovery mod (i know i have to press down power button and volume - , at the same time), no succes either, the TF just restar as always or the little android with an exclamation sign appears and i have to restart the TF again
my problem is that i cant install custom ROMS, because it always skip to home screen or to the android with the exclamation.
i cant see all those options that lot of people tallk(install from zip, backup current rom, install X rom)because i never get to that part....
so my problem again, how to install some tool that will allow me to enter in clockwork mode (??) ??, and enable those option at the intial boot (power button & vloume - at same time ) to be abble to access the install from zip, backup current rom, wipe data , etc etc
please if someone can help me with another step by step i will be really happy

I am having the same problem
Sent from my Transformer TF101 using xda premium

i think i have this problem since i got the " FIX the problem with DOWNGRADE from .21 to .19", something along those lines, with the method someone posted before (add both files to SD card but rename one of those and then apply update)

jesesystem said:
my problem here is that im already rooted (razorclaw tool), superuser installed aswell,
please if someone can help me with another step by step i will be really happy
Click to expand...
Click to collapse
but have you installed CWM recovery?
User RecoveryInstaller to install CWM.
http://forum.xda-developers.com/showthread.php?t=1346180

/agree with @baseballfanz
Check that you have CWM installed. Then you should hold volume down + power button till you see in the screen something like (push vol+ to enter recovery). It will appear on the top of the screen. You have to wait a little since it first appears the ASUS screen and if you stop pushing the buttons at that time, the TF starts normally. You have to hold them a little longer till the text appears in the screen.

AzureusPT said:
/agree with @baseballfanz
Then you should hold volume down + power button till you see in the screen something like (push vol+ to enter recovery). It will appear on the top of the screen. You have to wait a little since it first appears the ASUS screen and if you stop pushing the buttons at that time, the TF starts normally. You have to hold them a little longer till the text appears in the screen.
Click to expand...
Click to collapse
OR you can install 'transformer reboot to recovery' from market

Pepecillo said:
OR you can install 'transformer reboot to recovery' from market
Click to expand...
Click to collapse
If they don't have CWM installed, that will only reboot the TF, not get them to recovery.

AzureusPT said:
If they don't have CWM installed, that will only reboot the TF, not get them to recovery.
Click to expand...
Click to collapse
This is 100%. We've already told you this, in this thread This Thread.
You need to install a recovery image access recovery.
If you are this unsure of what you are doing i HIGHLY suggest stepping back and reading all about SU access and the rooting procedures again.
The "flash a new ROM to ________ device" steps are pretty much the same for every Android device w/o a locked bootloader.
Root
make sure SU access can be obtained
flash a custom recovery image
reboot into recovery
do a nandroid back up
wipe
flash
reboot
If you cannot get to where you want. You are doing something wrong. millions of people have followed these same step on millions of devices w/o any problems.

neidlinger said:
This is 100%. We've already told you this, in this thread This Thread.
You need to install a recovery image access recovery.
If you are this unsure of what you are doing i HIGHLY suggest stepping back and reading all about SU access and the rooting procedures again.
The "flash a new ROM to ________ device" steps are pretty much the same for every Android device w/o a locked bootloader.
Root
make sure SU access can be obtained
flash a custom recovery image
reboot into recovery
do a nandroid back up
wipe
flash
reboot
If you cannot get to where you want. You are doing something wrong. millions of people have followed these same step on millions of devices w/o any problems.
Click to expand...
Click to collapse
Thank you¡¡¡¡¡¡¡
Thats the step i was mising , all the instructions are for ppl that actually had cwm recovery, and i was taking advices from posts about installing custom roms and not the 1sth root
Its solved now ,thank you all for your help.

sorry, my bad for asking for help
Sent from my Transformer TF101 using xda premium

Bobsinclair25 said:
sorry, my bad for asking for help
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
In essence there is nothing wrong with asking for help. Heck even the smartest of android hackers started somewhere, asking questions the selves.
The problem lays in the fact that is is pretty common knowledge and a simple search would of gave you the answers you wanted.
Keep in mind nothing i say is meant to come across rude. Sharp maybe, rude? no. If you take what i say as rude. I'm sorry.

No problem. I have been trying very hard to learn on my own. The problem I had with this was trying to find information specific to the transformer. I have done quite a bit with my other android devices and the transformer is new to me and since I use it at work every day I am probably a bit more cautious about it. Thanks, I am working on it.
Sent from my Transformer TF101 using xda premium

recover options for bricked TF700 Please Help!!!

I just got my TF 700 and rooted an unlocked it, and all was ok, but then installed an app from the app store and now I only get "booting recovery kernel image" I was able to boot to APX mode install the driver and use Universal root toolkit for the TF and install the firmware from ASUS website but I think the boot image file is the problem. The transformer.bct is not for the TF700. Thanks in advace for any help.

xdatester11 said:
I just got my TF 700 and rooted an unlocked it, and all was ok, but then installed an app from the app store and now I only get "booting recovery kernel image" I was able to boot to APX mode install the driver and use Universal root toolkit for the TF and install the firmware from ASUS website but I think the boot image file is the problem. The transformer.bct is not for the TF700. Thanks in advace for any help.
Click to expand...
Click to collapse
Are you able to boot in recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Pretoriano80 said:
Are you able to boot in recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.

xdatester11 said:
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
Click to expand...
Click to collapse
AFAIK the nvflash method doesn't work for TF700 and is possible that you really bricked your device... The only solutionn i can see is to flash a recovery in fastboot mod and flash the Asus stock from there,but if you can't even boot in fastboot then i don't see any other way to recover the device.

xdatester11 said:
No I cannot boot into recovery only APX mode and use nvflash. I am able to flash files. I have flashed the factory firmware from Asus. I think it is the boot image that is still bad. I used the recovery tool BRK_RootKit_v8.0_final to flash the image file but it tries to flash the original TF transformer.bct boot file. I think If I had the correct transformer.bct for the TF700 it would work.
Click to expand...
Click to collapse
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.

xdatester11 said:
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
Click to expand...
Click to collapse
attachment

NVFlash works with the TF700??? That's news to me!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

xdatester11 said:
I was hoping someone would be willing to make a backup of their file using nvflash. I think the zip should help.
Click to expand...
Click to collapse
Sorry mate,but according to this --> http://androidroot.mobi/2012/07/15/nvflash-for-tegra3-transformer-prime/ <-- i don't think you will be able to use nvflash for recovery and it clearly states that you need to get fastboot working in order to use that method. (to get in fastboot mode press Volume down + Power and release the buttons when the message about having 5 second to press Volume Up shows...if this work you will get to a menu with the "USB icon" wich means boot in fastboot mode).
P.S : Can you tell us why you had to mess with nvflash?That is the most advanced way to recover/backup the Transformer 101/201 series and you have really high chances to brick your device for good.
EDIT: I don't think someone here will be able to make a backup for you with nvflash...it will only lead to more bricks.
EDIT 2: Can you please tell us the name of the app that bricked your device so we can avoid other people bricking their device?

The app was transformer reboot recovery I think.
I only used nvflash because it was the only option left as the tab wouldn't work with adb or fastboot.
I guess I'll keep it as a paper weight.

xdatester11 said:
The app was transformer reboot recovery I think.
Click to expand...
Click to collapse
weird, ive been using that app for a couple of days with no issues. but now I think I will uninstall it until someone can confirm that this causes problems.

henbone11 said:
weird, ive been using that app for a couple of days with no issues. but now I think I will uninstall it until someone can confirm that this causes problems.
Click to expand...
Click to collapse
Yes,i also used that app with no issue,but one of the developers behind TWRP advised to not use it at all,because if for some reason your recovery gets corrupted (that app send a custom command to boot into recovery) the device will boot loop trying to get in recovery and without nvflash we don't have many options to recover from that.
"
KEEP AWAY from that app for the moment,just stick with the old good " Volume Down + Power and then Volume UP " method to get into recovery.

Same issues here as well
I had rooted the TF700 ( as i wanted to download a market fix for my region, as i wasnt able to download GTA III) and had installed the eris market fix app :sillymy stupidity) it changed certain values to the original market application. After a reset/ reboot i was stuck at the powered by Nvidia Screen. I tried colding booting/ wiping etc non would work. I tried reinstalling the boot/system files through fastboot still no luck. what i cant understand is the fastboot setup seems to work when i id the Device it shows:
"? Fastboot"
i can reboot, push the system/ boot and recovery files, but cant boot into recovery mode. i have even pushed the twrp 2.2 file through fastboot. My only bet would be to boot into recovery so that i could mount and push custom roms.
I have even tried flashing the rom update through the following command "Fastboot flash update filename" however i get the archive cannot find android-info.txt error .
Is there anyway i could boot into recovery. (previously i could boot into recovery, but when i formatted/ erased the system and boot files i only get 2 options 1. Wipe Data & Cache & 2. Fastboot (USB). I tried holding the vol down button and the power button but that just puts me into blank screen mode and the APX driver pops up on the device manager.
I had to uninstall all my current drivers supporting asus and manually select the asus fastboot interface to get the fastboot working.
Any ideas would be helpful.

shasan2 said:
I had rooted the TF700 ( as i wanted to download a market fix for my region, as i wasnt able to download GTA III) and had installed the eris market fix app :sillymy stupidity) it changed certain values to the original market application. After a reset/ reboot i was stuck at the powered by Nvidia Screen. I tried colding booting/ wiping etc non would work. I tried reinstalling the boot/system files through fastboot still no luck. what i cant understand is the fastboot setup seems to work when i id the Device it shows:
"? Fastboot"
i can reboot, push the system/ boot and recovery files, but cant boot into recovery mode. i have even pushed the twrp 2.2 file through fastboot. My only bet would be to boot into recovery so that i could mount and push custom roms.
I have even tried flashing the rom update through the following command "Fastboot flash update filename" however i get the archive cannot find android-info.txt error .
Is there anyway i could boot into recovery. (previously i could boot into recovery, but when i formatted/ erased the system and boot files i only get 2 options 1. Wipe Data & Cache & 2. Fastboot (USB). I tried holding the vol down button and the power button but that just puts me into blank screen mode and the APX driver pops up on the device manager.
I had to uninstall all my current drivers supporting asus and manually select the asus fastboot interface to get the fastboot working.
Any ideas would be helpful.
Click to expand...
Click to collapse
1The first step is to get your recovery back and working...here's a how-to:
1) Download the recovery from here
2) Follow the instruction on how to flash the recovery in fastboot mode
If the flash went good and you can get in recovery mode follow this steps:
1)Download the 9.4.5.26 firmware from Asus site (the SKU for your region)
2)Extract the .zip file somewere on your desktop (the result will be another .zip file,use it for step 3)
3)Put the extracted zip to a MicroSD card
4)Insert the MicroSD card in your tablet and boot into recovery
5)Install the zip from recovery and restard when done
If all goes well your tablet will be again up and running

Ray of Teamwin
:good::good::good:Thanks a million, seeing the team win screen relieved me. The only problem is i cant boot into recovery (teamwin screen is visible)through the wipe data mode, wherein everything is wiped and it reboots automatically. I cant seem to force the table into recovery without this is there any fastboot command which i can use to force the tablet into recovery.

Need Stock Boot, Recovery, System img
Still no luck with the recovery mode. Every time i wipe the device it automatically reboots. I was wondering if i could get hold of stock recovery, boot and system .img files so that i can push them or flash them through fastboot.
i tried using the blob pack and unpack but i cant seem to get around the blob header thing.
Anyone to spare me stock .img files

End of Infinity
Okay my frustration has led me to "fastboot erase bootloader" and now i am permanently stuck in APX mode.
However as nvflash is not avaliable for tf700t i guess i wont be using this for quiet sometime. Unless nvflash is made available

shasan2 said:
Okay my frustration has led me to "fastboot erase bootloader" and now i am permanently stuck in APX mode.
However as nvflash is not avaliable for tf700t i guess i wont be using this for quiet sometime. Unless nvflash is made available
Click to expand...
Click to collapse
There's a thread (I can't find it again) that talks about this "Reboot into Recovery" app and how it might be bricking TF700T's. This guy wrote in, because he could not get to the recovery menu at all any more and could not do the "PWR+VOL-DOWN" combo. Nothing would happen. Maybe this was the thread, I don't know.
An XDA Mod in another thread said the app *might* be bricking them, but was waiting for confirmation before posting that it does.
I wish to confirm that IT DOES BRICK TF700T's! IT DOES!!!
And there is NOT A DAMN THING you can do! Your PC will not even recognize that the device is connected! You cannot get to the little icons to pick USB Mode, or whatever it's called.
This is the free app, not the other pay one in the Market. I don't know about that one, but this one is called, "Reboot into Recovery" and if you can somehow find that thread if I don't and just copy my post there, I would really appreciate it! I just want to warn people, ya know?
Also, using ANY of the "ROM Managers", whether it's CWM's, or GooMgr's, will take away all ability to get to a recovery menu at boot, at all! The device will still work and everything and boot to your Home Screen and everything. It won't be bricked like the app listed above does to it, but it will take away your recovery menu altogether and the PWR+VOLDOWN thing won't work any more either.
You can Unlock the TF700T, you can Root it. But you cannot use ANY ROM Mgr and you cannot use that Reboot into Recovery app.
But the app I listed above WILL BRICK YOUR DEVICE BEYOND ANY RECOVERY METHOD!
Please pass this on, I am confirming the experience. It doesn't matter if others say it worked for them. It is bricking them at random and even one of the guys who reviewed the app (diff guy than the one who posted here) said it bricked his. It is happening! It is not the user messing up! I did do it right!
Thanks!

I'm not sure if you are talking about the app named "Transformer Reboot to Recovery", but that particular app works fine on the TF700 - I use it all of the time.
The only time that it *can* cause problems is if your recovery is already corrupt or there is some other issue, in which case it can cause a bootloop.
But, if there are no issues, it works fine... There is a risk involved, like I said, if there are pre-existing problems with your device, but if you know that everything is working fine on your device, the app mentioned above works fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jtrosky said:
I'm not sure if you are talking about the app named "Transformer Reboot to Recovery", but that particular app works fine on the TF700 - I use it all of the time.
The only time that it *can* cause problems is if your recovery is already corrupt or there is some other issue, in which case it can cause a bootloop.
But, if there are no issues, it works fine... There is a risk involved, like I said, if there are pre-existing problems with your device, but if you know that everything is working fine on your device, the app mentioned above works fine.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No offense, but I think a huge problem in forums, is that people don't read carefully.
1) I think you are referring to the paid app. Read what I said about that.
2) You're saying what you're saying, in a thread started by a guy who had a running device and who didn't after using the app.
3) I said that it bricks them AT RANDOM.
4) Another problem with forums, is that whenever someone has a problem, A LOT of users want to post responses that ignore the users' experience and they want to act like the problem doesn't "really" exist. If multiple people are posting the same problem, then IT DOES EXIST. It just doesn't exist for YOU! But something working for you, does not mean it works for everybody and it does not mean there is a problem with their device, nor that they did something wrong.
5) And yet another problem with forums, is that when someone like me points things like this out, many users will respond by jumping on me, instead of those who try to make the guy feel like he's hallucinating and who, instead of trying to help him out, or just keep their mouths shut if they have nothing helpful to offer, think the right thing to do is to argue with the person having the problem.
These forums are for help and information. If someone has neither to offer the person, or at least warn others, then why are they responding at all? And why would anyone defend someone doing that?! It's ridiculous! But that's what typically happens, especially in XDA doe some reason (lots of snobs here, who like to prove they are, by doing as I just described).
The bottom line is, you do not run the app I talked about and even if you did, that does not take away from the experience that some have had and the best thing, is to avoid the app, because there's a risk involved and there is no recovery from it. I decided to warn people. You decided to tell us that we're hallucinating and that people should use the app. You did not carefully read what I wrote, or you would have checked the Market to see what the name of the app that does not have a pay version is. The one I am talking about does not.
I will tell you this. I am posting this from my laptop, because I had to return my Tablet and have a replacement shipped and now I have to spend a few days getting it all set up again the way I had it.
Avoid the ROM Mgr apps on the TF700T. And avoid the free app called "Reboot into Recovery". A user told me about it for my device, who had seen it used successfully. However, if you look at the reviews in the Market, you'll see that one of them says it bricked his *WORKING* *FINE* tablet and this thread right here has told you about two more. So just believe it and don't criticize, huh?
Okay Mods, feel free to jump on me again, just like last time.

I agree with many of your points, Zeuszoos, and thanks for pointing that out, but I believe there are many senior members at XDA willing to help if they have knowledge/abilities to do so, that's been my experience so far and hopefully it can be yours too. Of course, a little SEARCH won't hurt before posting one's problem, as you reasonably mentioned yourself
"reboot to recovery" has been in my apps STICKY thread in the sections "apps to avoid" (RED) for quite some time now after first reports of bricking users' devices started popping up and I believe it has helped some users who did a little reading before clicking...

Official Marshmallow 6.0 OTA for canadian xt1563 (telus, koodo, public mobile...)

Marshmallow OTA for canadian xt1563 : https://mega.nz/#!1pxWiSIS!u279kerhsu1HspzFZ4-wrzYfWgtSUqb3o8K8ffLw4lM
For the procedure, look down. Someone posted it on 1st page.
If you altered system ( ex:root) you'll need to go back to stock:
http://forum.xda-developers.com/showpost.php?p=62708260&postcount=5
Root (optional)
TWRP recovery (after applying the OTA) : http://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656
The correct SuperSU: http://forum.xda-developers.com/showpost.php?p=64161125

The X Play is actually XT1563. This firmware is for the Moto G.
Update: the above statement is wrong. I can confirm this update is running perfectly on my Koodo X Play!

bngrybt said:
The X Play is actually XT1563. This firmware is for the Moto G.
Click to expand...
Click to collapse
Yeah, but the file listed on mega has lux_retca in its name. Moto X Play is codenamed as Lux, so maybe it is in fact the right file for XT1563? Maybe, it was just an error from poster MerlinMerlinMerlin?

Hmm... I have a Koodo X Play and just checked for the OTA and it wasn't available for me yet, but that has me wondering now. I don't wanna risk it until I'm sure though. Hopefully this means the OTA is out soon though.

Oops! I messed up the title.
Corrected the incorrect xt1053 by the correct xt1563

Just finished installing it through ADB sideload (I'm a Canadian Koodo user), I reinstalled the stock firmware before so that I could start on a fresh image. I had trouble getting into stock recovery at first. I was seeing a no command message when trying to enter it but, then I found the solution:
To get passed that point, you have to use the hold power + vol up button solution but, it's tricky, I had to try 3-4 times before getting it right. This part is kind of messed up, if you hold power button for too long, the phone interpret it as a reboot command. What worked best for me was holding vol up button alone for 5-6 seconds and then, I'd tap and release power button while still holding volume up button.
Click to expand...
Click to collapse
It worked perfectly...

How do you install it? Simply install it in recovery or do we need to install it by adb?

baskwo said:
How do you install it? Simply install it in recovery or do we need to install it by adb?
Click to expand...
Click to collapse
First, you need to have stock recovery, if you installed TWRP custom recovery, you will need to reinstall stock recovery. Entering stock recovery can be tricky, at first you may get an Android robot laying down with a "No command" message.
To get passed that point, you have to use the hold power + volume up button solution but, it's tricky, I had to try 3-4 times before getting it right. This part is kind of messed up, if you hold power button for too long, the phone interpret it as a reboot command. What worked best for me was holding vol up button alone for 5-6 seconds and then, I'd tap and release power button while still holding volume up button.
Edit: a user reported that this method work better (your mileage may vary)
Press and hold the Power Button for 2-5 seconds, while holding it, press and release the Volume Up button. You should now be seeing all the Recovery options.
Click to expand...
Click to collapse
Once you are booted in stock recovery mode, you can simply follow those steps:
Setup ADB and Fastboot on your PC.
Download the OTA update .zip file on your PC and rename it to ota.zip.
Enable USB debugging:
Go to your phone’s settings » About phone » and tap “Build number” Seven times. This will enable Developer options on your phone.
Now go to Settings » Developer options » and tick the USB debugging check box.
Connect your phone to PC.
Now open the folder where you downloaded the OTA update .zip file and then open a command window inside the folder. To do that, do a “Shift + Right click” on any empty white space inside the folder and select “Open command window here” from the context menu.
Now issue the following window to command window to reboot your device into recovery mode:
adb reboot recovery
└ Check your phone’s screen, if it asks for “Allow USB debugging”, accept it by selecting OK/Yes.
Once in recovery mode, use Volume buttons to navigate up and down between options and Power button to select an option.
Select the “Apply update from ADB” option.
Now issue the following command to finally begin installing the OTA:
adb sideload ota.zip
└ This will begin the OTA installation.
Once the OTA zip is installed, select reboot from the main menu of recovery.
Click to expand...
Click to collapse
Please take note that once Marshmallow is installed, nothing is stopping you from reinstalling TWRP and then, it will work as if nothing ever happened. If you need SuperSU, make sure to use SuperSU 2.62, earlier version may cause problem with Marshmallow. Also, if TWRP , ask if you want to install Root, click "Do not install" as it would install an older version of SuperSU. That's why you need to flash SuperSU 2.62 zipfile.

And if I want to keep TWRP?

Any chance someone could post a TWRP backup after installing the OTA?

baskwo said:
And if I want to keep TWRP?
Click to expand...
Click to collapse
You'll just have to reinstall TWRP after. No big deal, you can easily reinstall it afterward. That's what I did and TWRP is working perfectly as if nothing ever happened.

Nico3d3 said:
You'll just have to reinstall TWRP after. No big deal, you can easily reinstall it afterward.
Click to expand...
Click to collapse
Alright, thank you boy! <3 Where can I find the stock recovery?

baskwo said:
Alright, thank you boy! <3 Where can I find the stock recovery?
Click to expand...
Click to collapse
Just grab it from the original firmware zip file... : http://forum.xda-developers.com/moto-x-play/general/official-stock-firmwares-added-xt1562-t3195364

Nico3d3 said:
Just grab it from the original firmware zip file... : http://forum.xda-developers.com/moto-x-play/general/official-stock-firmwares-added-xt1562-t3195364
Click to expand...
Click to collapse
Does the XT1563_LUX_RETLA_DS_5.1.1_LPD23.118-32_cid12_subsidy-DEFAULT_CFC_v2.xml.zip file is ok if I'm from Koodo? Sorry I'm new to the Moto X Play I worked on a S3 before..

baskwo said:
Does the XT1563_LUX_RETLA_DS_5.1.1_LPD23.118-32_cid12_subsidy-DEFAULT_CFC_v2.xml.zip file is ok if I'm from Koodo? Sorry I'm new to the Moto X Play I worked on a S3 before..
Click to expand...
Click to collapse
Yes, it would work but, knowing how slow download from filefactory is, it would be probably take a looonnnggg time to download. That's why I uploaded the correct recovery.img file on my Google Drive, for the benefit of everyone: https://drive.google.com/file/d/0B-OWWP0oC4yLRDhsSDV0Mng3cVk/view?usp=sharing

Nico3d3 said:
Yes, it would work but, knowing how slow download from filefactory it would be probably take a looonnnggg time to download. That's why I uploaded the correct recovery.img file on my Google Drive, for the benefit of everyone: https://drive.google.com/file/d/0B-OWWP0oC4yLRDhsSDV0Mng3cVk/view?usp=sharing
Click to expand...
Click to collapse
Do you have a link the 5.1.1 fw?
I'd like to do a total fresh install then kick off the ota.

Anyone tested this on the xt1562?
Sent from my XT1562 using XDA Free mobile app

I misread last post, sorry about it, that's why I'm editing my post

Nico3d3 said:
Pleaaassseee, at least take the time to read a bit, no more than one page ago, you will have all informations regarding installation and how it worked.
Click to expand...
Click to collapse
There is nothing on that page about the xt1562, Just asking if anyone tested it on that device
Sent from my XT1562 using XDA Free mobile app

Nico3d3 said:
Pleaaassseee, at least take the time to read a bit, no more than one page ago, all informations regarding installation and how it worked are there.
Click to expand...
Click to collapse
Lol, you should read first before telling someone else
Sent from my Nexus 5 using Tapatalk