Related
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.
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.
Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.
yes, of course..
root doesn't delete any of your data
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.
timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?
pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon
The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!
But how is anything going to be written to the system partition if it is locked ?
timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?
bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?
pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?
Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!
I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!
zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.
So I installed CM12S on my device and now i'm just getting a black screen, the phone still vibrates when buttons are pressed and I can get the device into fastboot mode, although I can not see it on screen, I can see it on device manager.
Now I've tried the various methods on this forum using ColorOS and the OnePlus Recovery tool, neither of these change the state of my device.
Currently dealing with OnePlus support at the moment which is awful to say the least, they have booked me in for a remote session which is in 2 weeks ... no appointments before then, ive disputed on PayPal with them currently as I dont think this is good enough, anyone got any other ideas to get my device back up and running?
Thanks
Id say to install adb on your computer so that that way you can reflash the roms manually from your computer. Or at the very least flash stock and then whatever customs from there. Here is a link to the thread with the links in the OP with straight forward step by step instructions. Good luck!
http://forum.xda-developers.com/showthread.php?t=2788632
tinyaznboi said:
Id say to install adb on your computer so that that way you can reflash the roms manually from your computer. Or at the very least flash stock and then whatever customs from there. Here is a link to the thread with the links in the OP with straight forward step by step instructions. Good luck!
http://forum.xda-developers.com/showthread.php?t=2788632
Click to expand...
Click to collapse
I have ADB and can succesfully get into fastboot, although I cannot see it on-screen I can see it listed in device manager in windows, Ive tried flashing several ROMs using the fastboot commands and still cannot get the thing to turn on.
I honestly dont believe the device to be completely dead, to note last time I saw this device on I was at 4% battery. But have also left the phone on charge overnight.
ConEP said:
I have ADB and can succesfully get into fastboot, although I cannot see it on-screen I can see it listed in device manager in windows, Ive tried flashing several ROMs using the fastboot commands and still cannot get the thing to turn on.
I honestly dont believe the device to be completely dead, to note last time I saw this device on I was at 4% battery. But have also left the phone on charge overnight.
Click to expand...
Click to collapse
What do you mean you've tried flashing several ROMs with fastboot? You don't flash ROMs with fastboot. Do you mean the stock images?
Heisenberg said:
What do you mean you've tried flashing several ROMs with fastboot? You don't flash ROMs with fastboot. Do you mean the stock images?
Click to expand...
Click to collapse
Yeah apologies ive flashed CM11S, Color, CM12S, also tried oxygen, cant flash ROMs as I cant even get into TWRP.
ConEP said:
Yeah apologies ive flashed CM11S, Color, CM12S, also tried oxygen, cant flash ROMs as I cant even get into TWRP.
Click to expand...
Click to collapse
What is the outcome when flashing the images with fastboot? Do they succeed or fail?
Heisenberg said:
What is the outcome when flashing the images with fastboot? Do they succeed or fail?
Click to expand...
Click to collapse
All of them seem to be successful (no error messages) but the phone still does nothing afterwards.
ConEP said:
All of them seem to be successful (no error messages) but the phone still does nothing afterwards.
Click to expand...
Click to collapse
You said you've tried this right?
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Heisenberg said:
You said you've tried this right?
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Yep, get all the way through till it goes green, but still nothing after phone just vibrates, no LEDs or screen activity.
ConEP said:
Yep, get all the way through till it goes green, but still nothing after phone just vibrates, no LEDs or screen activity.
Click to expand...
Click to collapse
I'm out of ideas then, sorry.
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