Database Info

[Q] Nexus S 4G won't boot past Google Screen!!

I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??

There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).

Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?

deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.

It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )

deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?

deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.

I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.

deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps

Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.

same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...

nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David

I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.

With JB installed: CWM Recovery causes a hang when I try to load into it.

Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Edit: Forgot to also ask, am I just an idiot?

badfontkeming said:
Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Click to expand...
Click to collapse
I have the same issue, no fix yet.

untermensch said:
I have the same issue, no fix yet.
Click to expand...
Click to collapse
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.

I have the exact same problem so I right there with ya
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.

badfontkeming said:
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.
Click to expand...
Click to collapse
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.

EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
I've noticed the same issue, it exists with the latest TWRP flashed via fastboot as well.
The problem with flashing via the terminal is that we don't have root yet, and need a recovery to get it. Looks like the only option is to wait for a fix.

EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
Yeah... the issue is, the reason I'm trying to flash CWM is so I can get root.

krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?

sparky28000 said:
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?
Click to expand...
Click to collapse
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265

krhainos said:
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265
Click to expand...
Click to collapse
Now there is atleast 3 people since I bricked mine also

krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
just curious how are you able to get in APX mode it seems I cant even do that

Drgravy said:
just curious how are you able to get in APX mode it seems I cant even do that
Click to expand...
Click to collapse
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.

krhainos said:
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.
Click to expand...
Click to collapse
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient

Drgravy said:
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient
Click to expand...
Click to collapse
I used the reset hole in place of the power button when fiddling with button combinations. Hold down VOL+, and poke the reset hole with a paperclip and that'll get you in APX mode -- not like it does any of us any good.

I thought I had bricked mine...
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim

I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.

jdeatsch said:
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim
Click to expand...
Click to collapse
Not working for me at all...

untermensch said:
I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.
Click to expand...
Click to collapse
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
---------- Post added at 10:46 PM ---------- Previous post was at 10:40 PM ----------
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse
Weird. When I try to edit this post, I only get 3/4 of the quote and none of my actual post to edit. Anyway...
Just wanted to clarify: not asking for directions. If the file is what I think it is, I know what I'm doing. I just want to know that the file is what I think it is.

It is the Jelly Bean recovery kernel and the ClockWorkMod ramdisk repacked with mkbootimg, then blobpack,
then I added the "-SIGNED-BY-SIGNBLOB-" header with a hex editor. it seems like ADB does not work but I
was able to root with an update.zip
I installed this with fastboot and erased and re-flashed 4 time's before posting to make sure
it would not cause instant brick.
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse

What rom should I flash to get extra Languages?

I've got the Canadian Virgin Mobile Moto G, and I recently unlocked the carrier. I am going to unlock to bootloader to flash a rom with more languages, specifically Portuguese.. What rom should I use, I'm looking for the original Moto G software.

Zehmistah said:
I've got the Canadian Virgin Mobile Moto G, and I recently unlocked the carrier. I am going to unlock to bootloader to flash a rom with more languages, specifically Portuguese.. What rom should I use, I'm looking for the original Moto G software.
Click to expand...
Click to collapse
I'm running CM11 and a quick look the phone tells me that it have Portuguese for brazil and portugal, alternatively try any latin american stock rom: http://sbf.droid-developers.org/phone.php?device=14

Z-WolF said:
I'm running CM11 and a quick look the phone tells me that it have Portuguese for brazil and portugal, alternatively try any latin american stock rom: http://sbf.droid-developers.org/phone.php?device=14
Click to expand...
Click to collapse
Oh man, thank you for the link, I just might use that. Just a refresher, to flash It I would first unlock the bootloader, flash a new recovery, wipe, and then flash the new rom?

Zehmistah said:
Oh man, thank you for the link, I just might use that. Just a refresher, to flash It I would first unlock the bootloader, flash a new recovery, wipe, and then flash the new rom?
Click to expand...
Click to collapse
yep, but you don't need to flash a custom recovery for a Stock ROM.

Z-WolF said:
yep, but you don't need to flash a custom recovery for a Stock ROM.
Click to expand...
Click to collapse
Thank you!!! and one more question, the new rom should still be capable of getting OTA updates from whatever carrier's rom I flashed, correct?

Zehmistah said:
Thank you!!! and one more question, the new rom should still be capable of getting OTA updates from whatever carrier's rom I flashed, correct?
Click to expand...
Click to collapse
****. I think I ****ed up. http://forum.xda-developers.com/showthread.php?t=2727965

Zehmistah said:
****. I think I ****ed up. http://forum.xda-developers.com/showthread.php?t=2727965
Click to expand...
Click to collapse
Zehmistah said:
Okay so I unlocked my bootloader for my Moto G, and when It rebooted it said android was updating apps and then all the processes stopped working. It booted into the android startup but I couldn't get any processes running so it wouldnt work. I tried to reboot and now android doesn't even boot up. Should I flash a custom recovery right now and then wipe??? I haven't done anything to the phone other than carrier unlock and bootloader unlock. please help
Should I try this? http://forum.xda-developers.com/showthread.php?t=2542219 , or is it too risky right now? I'm planning to restore it to another stock firmware anyways.
Click to expand...
Click to collapse
First, don't panic.
Second, explain how do you unlock the bootloader, did you use this?
Third, what does the bootloader screen (Power+VolDown) says in the second to last line before the first break (LOCKED/UNLOCKED).
Fourth, if it says UNLOCKED, try to flash the ROM using this, otherwise try to unlock the bootloader again with the link i posted in the second point.
And don't worry as long as you can enter fastboot mode (bootloader) you can fix everything, and nothing of the things you are doing affects fastboot mode.

They all want money.
Sent from my GT-N7105 using xda app-developers app

Perry2547 said:
They all want money.
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Can you elaborate?

You can add more languages without a custom ROM using MoreLocale 2.

Z-WolF said:
First, don't panic.
Second, explain how do you unlock the bootloader, did you use this?
Third, what does the bootloader screen (Power+VolDown) says in the second to last line before the first break (LOCKED/UNLOCKED).
Fourth, if it says UNLOCKED, try to flash the ROM using this, otherwise try to unlock the bootloader again with the link i posted in the second point.
And don't worry as long as you can enter fastboot mode (bootloader) you can fix everything, and nothing of the things you are doing affects fastboot mode.
Click to expand...
Click to collapse
I used that webstie to unlock the bootloader, and when I went to fastboot it did say UNLOCKED status code: 3.
I left it plugged into my PC last night because It wouldn't turn off, and I think it wasn't charging because now it's off and won't turn on. I'm going to plug it into a wall charger and wait a few to check if it's on.
After that, I'll try the method you said.
EDIT: Seems like charging doesn't work either, weird... because it said it was connecting to my PC last night in Fastboot

Zehmistah said:
I used that webstie to unlock the bootloader, and when I went to fastboot it did say UNLOCKED status code: 3.
I left it plugged into my PC last night because It wouldn't turn off, and I think it wasn't charging because now it's off and won't turn on. I'm going to plug it into a wall charger and wait a few to check if it's on.
After that, I'll try the method you said.
EDIT: Seems like charging doesn't work either, weird... because it said it was connecting to my PC last night in Fastboot
Click to expand...
Click to collapse
That's weird, doing the steps in that page don't make changes big enough in the phone to make something like that happen.
What does it says in the line below UNLOCKED, USB CONNECTED or CONNECT USB DATA CABLE while you had it connected to your pc/wall?
Why don't you try to use another cable?

Z-WolF said:
That's weird, doing the steps in that page don't make changes big enough in the phone to make something like that happen.
What does it says in the line below UNLOCKED, USB CONNECTED or CONNECT USB DATA CABLE while you had it connected to your pc/wall?
Why don't you try to use another cable?
Click to expand...
Click to collapse
I don't remember what it said.
I've tried a few different wall chargers and cables. They seem to charge my other phones but not this one. I'm going to wait an hour and then maybe put it in the freezer for a few minutes

Zehmistah said:
I don't remember what it said.
I've tried a few different wall chargers and cables. They seem to charge my other phones but not this one. I'm going to wait an hour and then maybe put it in the freezer for a few minutes
Click to expand...
Click to collapse
That's a... unorthodox approach, but reading around it just might work.
I can only recommend you to put it in a sealed container and having a rice bag at hand afterwards, just in case.
Now if you can get it to fastboot mode, try to restore a backup (if you did one) or flash a ROM, im assuming that if you can connect a cable and send commands to fastboot it is charging the phone. BTW at this point if you can send commands and are tired trying to fix it, you can execute
Code:
fastboot oem lock
and you can claim the warranty, that behaviour is not normal, maybe something in the hardware side broke but until we test it more we can't be sure.
Now while we wait in for the phone to become a popsicle, can you detail how you unlocked it?

Z-WolF said:
That's a... unorthodox approach, but reading around it just might work.
I can only recommend you to put it in a sealed container and having a rice bag at hand afterwards, just in case.
Now if you can get it to fastboot mode, try to restore a backup (if you did one) or flash a ROM, im assuming that if you can connect a cable and send commands to fastboot it is charging the phone. BTW at this point if you can send commands and are tired trying to fix it, you can execute
Code:
fastboot oem lock
and you can claim the warranty, that behaviour is not normal, maybe something in the hardware side broke but until we test it more we can't be sure.
Now while we wait in for the phone to become a popsicle, can you detail how you unlocked it?
Click to expand...
Click to collapse
Ok, so I bought the phone and got it carrier unlocked, then yesterday I decided to flash a new rom to get the languages so I went to https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Unlocked the bootloader and when the phone was about to restart from cmd it said "FAILED" but rebooted anyways. It went into fastboot again and ti said it was Unlocked, when I selected Normal Reboot, it started up with the bootloader logo and continued on normally. It was then that it displayed the android startup page (Where you select language, sign into google, connect to wifi etc.) like I haven't used the phone before. Shortly after a popup came and said " Android is updating # of apps out of 137", once that was over every single process on the phone crashed.
Now I'm where I am now.
One more thing, I booted it into recovery before I unlocked the bootloader, accidently. Do you think it maybe could've wiped the original OS on the device?

Zehmistah said:
Ok, so I bought the phone and got it carrier unlocked, then yesterday I decided to flash a new rom to get the languages so I went to https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Unlocked the bootloader and when the phone was about to restart from cmd it said "FAILED" but rebooted anyways. It went into fastboot again and ti said it was Unlocked, when I selected Normal Reboot, it started up with the bootloader logo and continued on normally. It was then that it displayed the android startup page (Where you select language, sign into google, connect to wifi etc.) like I haven't used the phone before. Shortly after a popup came and said " Android is updating # of apps out of 137", once that was over every single process on the phone crashed.
Now I'm where I am now.
One more thing, I booted it into recovery before I unlocked the bootloader, accidently. Do you think it maybe could've wiped the original OS on the device?
Click to expand...
Click to collapse
As far as i know, you can't wipe the system with a stock recovery and with a "blank" OS your phone still connects to PC.
i forgotted this existed, at this point you can't lose anything in trying it. i dont recomend the bootloader bricker part for your case.

Z-WolF said:
As far as i know, you can't wipe the system with a stock recovery and with a "blank" OS your phone still connects to PC.
i forgotted this existed, at this point you can't lose anything in trying it. i dont recomend the bootloader bricker part for your case.
Click to expand...
Click to collapse
The phone isnt't being detected when I plug it in.
I've read that leaving the phone 24 hours untouched could also help the battery. I'm going to try that\
EDIT: GOT IT TO TURN ON!!!

Ok, so I got it working. The thread you told me first helped!! It works fine now with the Brazilian software. Thank you very much, you're a life saver.
Now... I've got another moto G to do the same to

Zehmistah said:
Ok, so I got it working. The thread you told me first helped!! It works fine now with the Brazilian software. Thank you very much, you're a life saver.
Now... I've got another moto G to do the same to
Click to expand...
Click to collapse
You had me worried there, i though it was a goner. in the end everything turned out okay.
Happy to be of service.

Not recalled one, APX mode!! HELP!!!

Hello, everybody!
My new tablet, it is not recall one, i received from nvidia because i have a recalled tablet, it is already killed.
But now, my new tablet also sticking in APX mode, i used a nvidia toolbox from a person to flash the first version about this tablet, when it finished, i rebooted my tablet, the screen became black, and never show anything, can't enter fastboot mode, my PC show APX!
What i can do now???:crying::crying::crying:

What toolbox and what firmware? What did you do, step by step, to get in this state?

lafester said:
What toolbox and what firmware? What did you do, step by step, to get in this state?
Click to expand...
Click to collapse
A Chinese man uploaded it on a website, he said this toolbox can flash the first version of this tablet, when i run the flash.bat, the cmd window showed many, system.img is 900+M but was separated as 90+m and flashed many times, also userdata.....
I want to show you a picture about the cmd window when i flash this img, but i don't know how to upload a picture.....sorry:crying::crying::crying:

nobody......

wyy1993 said:
nobody......
Click to expand...
Click to collapse
Have you tried forcing boot into fastboot with volume down?
Was the replacement a K1 and did you flash a ROM for the original?
Anything else you can tell us about this mysterious Chinese man's website? Maybe post a link.
Still got that pic of the console output or a text version?
Any other info that can help us to help you?

durgis said:
Have you tried forcing boot into fastboot with volume down?
Was the replacement a K1 and did you flash a ROM for the original?
Anything else you can tell us about this mysterious Chinese man's website? Maybe post a link.
Still got that pic of the console output or a text version?
Any other info that can help us to help you?
Click to expand...
Click to collapse
I can't forcing boot into fastboot, i tried power button and volume down, nothing happened, the screen always black...
I think the partition is broken, i don't know the replacement is or not K1, but i flashed the original version....
I used this toolbox: http://bbs.gfan.com/android-8245744-1-1.html V2.3
Thanks for your attention!

wyy1993 said:
I think the partition is broken, i don't know the replacement is or not K1, but i flashed the original version....
I used this toolbox: http://bbs.gfan.com/android-8245744-1-1.html V2.3
Click to expand...
Click to collapse
I think you might be right about the partitions being wrong. The easiest way to distinguish the tablet is that the original has a stylus and K1 does not.
I couldn't read much on that forum, but it specifically calls out "nv-recovery-image-shield-tablet-k1-factory0_0_0.zip". So you might have flashed a recovery/rom for the wrong device and bricked it.

durgis said:
I think you might be right about the partitions being wrong. The easiest way to distinguish the tablet is that the original has a stylus and K1 does not.
I couldn't read much on that forum, but it specifically calls out "nv-recovery-image-shield-tablet-k1-factory0_0_0.zip". So you might have flashed a recovery/rom for the wrong device and bricked it.
Click to expand...
Click to collapse
so, do you think my tablet is broken? Forever broken?

wyy1993 said:
so, do you think my tablet is broken? Forever broken?
Click to expand...
Click to collapse
Someone else may come along with a better idea, but I think it's is beyond my abilities.

durgis said:
Someone else may come along with a better idea, but I think it's is beyond my abilities.
Click to expand...
Click to collapse
Okay...anyway, thanks for your reply!

TF700KL root + new Rom?

Hello,
i have a TF700KL, and i want to flash it.
But i don't find Something about it. Only about TF700.
Can You Help me?
Warm regards

Please Guys, i want help... Please...

Thx for ignore me

TF700 & TF700KL same, KL is the last version and the one listed on Asus's Global Website. All files should work once you A) Update firmware to the latest version B) Unlock bootloader. - NP

I did update it to Version VF_V5.0.4.17 but still can't manage to make the unlock app to get installed.
hard resetted3 times also with no GMAIL account, but still nothing
please help me

Donnie87 said:
I did update it to Version VF_V5.0.4.17 but still can't manage to make the unlock app to get installed.
hard resetted3 times also with no GMAIL account, but still nothing
please help me
Click to expand...
Click to collapse
Took me a few minutes to find it and a few hoops to jump through to extract the archive, but the official apk is still out there. Try to install this:
https://www.androidfilehost.com/?fid=5862345805528055095

AMAZING I MANAGED!!! THANK YOU BROOOOOOOOOOOOOOOOOOOOOOOOOOOO
how can I now install a custom rom? I'd just like to have the original one but faster....
and of coruse no I don't want to lose the 4g support
---------- Post added at 02:42 PM ---------- Previous post was at 02:03 PM ----------
I tried to reboot but even if it's unlocked, I have no bootloader. it still remain with the screen normal version

Donnie87 said:
AMAZING I MANAGED!!! THANK YOU BROOOOOOOOOOOOOOOOOOOOOOOOOOOO
how can I now install a custom rom? I'd just like to have the original one but faster....
and of coruse no I don't want to lose the 4g support
---------- Post added at 02:42 PM ---------- Previous post was at 02:03 PM ----------
I tried to reboot but even if it's unlocked, I have no bootloader. it still remain with the screen normal version
Click to expand...
Click to collapse
You are welcome.
Rest assured you do have a bootloader. You may not have the bootloader interface the other Transformers have and possibly there is no way to get fastboot to work on this thing - I don't know.
There is no custom rom for this tablet, and if you do not want to loose 4G you cannot use one made for another Transformer either (no idea if that is even possible, I do not know the KL).
Your best bet is to gain root and uninstall a bunch of cr**, maybe use Greenify - I don't know. Very limited what you can do on stock....
I seem to recall that people got root with Framaroot on this thing. Google it, the info is out there. If I can find it so can you

berndblb said:
You are welcome.
Rest assured you do have a bootloader. You may not have the bootloader interface the other Transformers have and possibly there is no way to get fastboot to work on this thing - I don't know.
There is no custom rom for this tablet, and if you do not want to loose 4G you cannot use one made for another Transformer either (no idea if that is even possible, I do not know the KL).
Your best bet is to gain root and uninstall a bunch of cr**, maybe use Greenify - I don't know. Very limited what you can do on stock....
I seem to recall that people got root with Framaroot on this thing. Google it, the info is out there. If I can find it so can you
Click to expand...
Click to collapse
ok let me get to the keypoints here that made me ask for help, and so you'll see that i'm not just a lazy person that doesn't use google
1) Some people they say that the KL can accept all the roms of the Tf700T. for example katkiss is saying to use one of their roms
1.a) some say that it will brick the device.
so, first question here, what will happen if i'll get a custom rom of the TF700T?
2) some people say that I should have a version of the "unlock bootloder" after unlocking with the asus app.
Well I don't have anything, I just have a small phrase which is "device unlocked" and that's it. nothing else.
3) some say on google that there is a cyanogen mod for the KL. Unfortunately cyanogenmod wiki and forum are down, so I can't find either assistance, either the files.
nothing to do here, then.
4) let's say I'll follow your guide, and i'll flash a custom rom. will I lose the 4g?
4.a) how can I get to the old rom, even original, in order to get 4g back?
5) about root: i managed to root it a long time ago. Unfortunately, even disabling most of the package and all the bloatware, the device really sucks.
that's the main reason why I abandoned there 3 years ago. now it's full of dust, and as I've been working a lot, I wanted to get it back with basic functions, but without waiting 10 seconds from the moment i press on APPS BUTTON and the actual time for which I see the apps page.
so, here's my google searching experience.

Donnie87 said:
1) Some people they say that the KL can accept all the roms of the Tf700T. for example katkiss is saying to use one of their roms
1.a) some say that it will brick the device.
so, first question here, what will happen if i'll get a custom rom of the TF700T?
Click to expand...
Click to collapse
I'd say the first question is: Is there a compatible custom recovery for the KL and how to install it? I do not know that there ever was a custom recovery made for the KL and using one made for another Transformer may or may not brick your device. I do not see a single post from anyone stating that they successfully installed a custom rom or recovery on the KL, so my guess is: It cannot be done unless you develop a custom recovery for this tablet and find a way to flash it.
2) some people say that I should have a version of the "unlock bootloder" after unlocking with the asus app.
Well I don't have anything, I just have a small phrase which is "device unlocked" and that's it. nothing else.
Click to expand...
Click to collapse
Well, there's the first difference to other Transformers: Most of them have a bootloader menu from where you can boot into recovery or into Android and perform a data wipe. Booted into the bootloader you also have fastboot access. The KL does not seem to have any of this. Do you have fastboot working on your PC? Try it, boot with Vol down or Vol Up and then check if you have fastboot access to the tablet. I doubt it....
3) some say on google that there is a cyanogen mod for the KL. Unfortunately cyanogenmod wiki and forum are down, so I can't find either assistance, either the files.
nothing to do here, then.
Click to expand...
Click to collapse
I've only seen post users expressing hope or wishes for CM for the KL. I don't think there ever was a working CM rom for the KL
4) let's say I'll follow your guide, and i'll flash a custom rom. will I lose the 4g?
Click to expand...
Click to collapse
You cannot follow my guide unless you figure out a way to get fastboot working. You could try to flash TWRP recovery using their app or Flashify, but which TWRP?? Which version might be compatible with your bootloader? Nobody knows it seems. But heck! What have you got to loose? You are not going to use the tablet in its current state anyway, so if you brick it - who cares?
But to answer your question: Yes, you would definitely loose the 4G. The software for your modem has its own partition and no rom made for the wifi-only Transformers even knows this partition exists, let alone about the hardware
4.a) how can I get to the old rom, even original, in order to get 4g back?
Click to expand...
Click to collapse
Again: Untested territory. If you had a custom recovery or fastboot you might be able to flash the Asus firmware in either. Maybe

you won't believe me
I was away for 1 month
got back
installed framaroot
installed greenify
now it runs with like 10 apps total (including the keyboard)
tablet STILL UNUSABLE, takes 1 minutes to open youtube, 2 mins to open play store
Id really like to brick it rather than keep it like that
Well, there's the first difference to other Transformers: Most of them have a bootloader menu from where you can boot into recovery or into Android and perform a data wipe. Booted into the bootloader you also have fastboot access. The KL does not seem to have any of this. Do you have fastboot working on your PC? Try it, boot with Vol down or Vol Up and then check if you have fastboot access to the tablet. I doubt it....
Click to expand...
Click to collapse
tried but the max i get is the screen wghere
"press volume button to select
1) enter sd down mode
2) factory reset
3) exit update mode
press power button to enter"
so i then flashed with flashify, read after
berndblb said:
You cannot follow my guide unless you figure out a way to get fastboot working. You could try to flash TWRP recovery using their app or Flashify, but which TWRP?? Which version might be compatible with your bootloader? Nobody knows it seems. But heck! What have you got to loose? You are not going to use the tablet in its current state anyway, so if you brick it - who cares?
But to answer your question: Yes, you would definitely loose the 4G. The software for your modem has its own partition and no rom made for the wifi-only Transformers even knows this partition exists, let alone about the hardware
Click to expand...
Click to collapse
I then flashed the TWMR
when i rebooted it said
"no usb connected"
i then connected to the PC
and it say
"READY FOR DOWNLOAD" with an android picture
i can't boot it up again
what should i do now?
when i now do the FASTBOOT DEVICES command on pc, I see the serial of the asus
it's the first time fastboot sees it
I tried doing "fastboot update kitkatnougatellaxxxx.zip"
but it say that android-info.txt & android-product.txt not find so not flashable
what now, then? I can't even use it with the old OS

You need to boot into the TWRP that you flashed, hold the volume button down and press the power button (hold both) until you get the fastboot screen, the square with [RCK] should be blinking. Now press the volume up button to enter the TWRP recovery console. - NP

Nektopoli said:
You need to boot into the TWRP that you flashed, hold the volume button down and press the power button (hold both) until you get the fastboot screen,
Click to expand...
Click to collapse
this is what i get when i press the button normal boot button
this is what i get when i press the volum down + boot button
I just did flashifty with the latest TMWR recovery for TF700T

help pliz

best bet would be to do a factory reset, I don't believe this rom will work on the KL model. - NP

it doesn't even allow the factory reset, as if i press it it gives the NO USB CONNECTED screen
i'd say it's bricked

Donnie87 said:
it doesn't even allow the factory reset, as if i press it it gives the NO USB CONNECTED screen
i'd say it's bricked
Click to expand...
Click to collapse
Try selecting [1] "Enter SD down mode" which is Enter SD download mode and see if you get to the next menu. - NP

I can't

I mean it doesn't get to the next menu

I've been trying to find the threads on how to re-flash the stock ASUS ROM from the SD cardseeing this is the only way to get the TF700k working but I can't find it know. It involved have the ROM in the root directory on the SDcard and giving it a specific name, this name triggers the tablet to update itself. - NP