Database Users

fastboot oem unlock?

So I heard that the XOOM can be unlocked from fastboot.
I did the same process to my Atrix and it said it completed it with a happy OKAY.
ran the command "fastboot oem unlock" from the Atrix in it's fastloader mode.
It gave a friendly OKAY.
I haven't a clue if it is really unlocked. I just figured this might be helpful info, or maybe not.

While I highly doubt it's that easy on our phones, it's interesting that it returned an OK on the command. Can any proper devs chime in? Does it just give an arbitrary 'OKAY' once the command completes, whether successful or not?

DarkSi08 said:
While I highly doubt it's that easy on our phones, it's interesting that it returned an OK on the command. Can any proper devs chime in? Does it just give an arbitrary 'OKAY' once the command completes, whether successful or not?
Click to expand...
Click to collapse
If you do a "fastboot oem anything" it will return OKAY
I am pretty sure its not doing anything. The phone just return OKAY to whatever oem command you try to execute and doesnt do anything.

uskr said:
If you do a "fastboot oem anything" it will return OKAY
I am pretty sure its not doing anything. The phone just return OKAY to whatever oem command you try to execute and doesnt do anything.
Click to expand...
Click to collapse
I can confirm that the fastboot oem *anything* command gives "... OKAY" no matter what is typed.
A for effort though, OP

What does all this mean?
Code:
C:\Users\Ryan>fastboot getvar all
(bootloader) version-bootloader: 1000
(bootloader) product: olympus
(bootloader) secure: no
(bootloader) mid: 001
(bootloader) version: 0.4
(bootloader) serialno: 02884xx
(bootloader) version-baseband: currently un-supported
all: Done
finished. total time: 0.004s
"(bootloader) secure: no"... I'm sure that doesn't mean what I think it does, does it?

I also believe you just gave out your serial number
Sent from my MB860 using XDA App

neer2005 said:
I also believe you just gave out your serial number
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
LOL, nice.
Anyway, I'm sure it was a false alarm... Looked promising, but cant' do anything.
Sorry to make a mess of the forum.

[Q] Bricked Nexus 10: too many links when flashing

Hi everyone,
In the past days I tried to unlock and root my Nexus 10, and looks like something went very wrong.
Right now, I'm stuck with the bootloader screen; the tablet boots into bootloader and I can only go to "bootloader" (power + vol up + vol down) or "download" (power and vol up).
The bootloader screen reads:
PRODUCT NAME: mantra
VARIANT: wifi
H/W VERSION: 8
BOOTLOADER VERSION : MANTAMD003
CARRIER INFO: NONE
SERVIAL NUMBER: XXXXXXXXX
LOCK STATE: UNLOCKED
REBOOT MODE FLAG: NONE
I've tried using different tools, including "Wugs Nexus Root Toolkit" and command line fastboot.
Some fastboot commands seem to work - e.g.:
fastboot devices (it does recognise my device)
fastboot -w (the messages on the screen seem to suggest it's all ok)
fastboot getvar all:
(bootloader) product: manta
(bootloader) variant: wifi-only
(bootloader) serialno: XXXXXXXXX
(bootloader) version-hardware: 8
(bootloader) version-bootloader: MANTAMD03
(bootloader) secure: yes
(bootloader) unlocked: yes
(bootloader) off-mode-charge: enabled(1)
(bootloader) signing: yes
(bootloader) boot partition- type: raw, size: 0x0000000001000000
(bootloader) recovery partition- type: raw, size: 0x0000000001ff0000
(bootloader) metadata partition- type: raw, size: 0x0000000000010000
(bootloader) misc partition- type: raw, size: 0x0000000000400000
(bootloader) cache partition- type: ext4, size: 0x0000000021000000
(bootloader) system partition- type: ext4, size: 0x0000000032000000
(bootloader) userdata partition- type: ext4, size: 0x0000000352c00000
The problem is with commands like:
fastboot flash bootloader bootloader-manta-mantamd03.img
(or any flashing command for what it matters).
None of them works; after waiting for a long while, the error returned is "Too many links".
I have googled the command, but I haven't found anything meaningful. ADB doesn't work - I must use fastboot to unbrick the device.
Any suggestions?
Andres

I haven't unlocked & rooted yet.. just started looking at it today. It seems you can already get into bootloader. Shouldnt you be flashing a recovery in download mode?
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
Also the toolkit has an option for bricked devices. I'd look into that as a last resort.

faiyo said:
I haven't unlocked & rooted yet.. just started looking at it today. It seems you can already get into bootloader. Shouldnt you be flashing a recovery in download mode?
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
Also the toolkit has an option for bricked devices. I'd look into that as a last resort.
Click to expand...
Click to collapse
Hi, thanks for the suggestion.
I've tried to flash a recovery image already - that didn't work. That's why I tried flashing anything. I've also tried the "Back to stock" option in the toolkit, and it hangs when trying to flash anything to the tablet...
Andres

I was still curious so i went googling. I think u should try a different cable and another usb port and different computer. It has fixed this issue for some people. Others said to try odin but what you're doing should really work. Otherwise there is a hardware failure and replacement parts dont seem to be an option... except at best a pogo connector cable in case the microusb jack is borked. I hope someone else chimes in for you. I haven't had any experience with this device. Maybe take some comfort in the asus nexus 10 coming out in a few months?

Have you tried using Wugs to Flash the Stock ROM and Unroot? I have been unable to get ADB to find my Nexus 10, even though it's been listed in the Device Manager of Win 8 with each of the 4 suggested drivers suggested. After getting stuck in a Bootloop I was still able to use the 'Back to Stock' option to recover my Nexus 10.
Good luck.

faiyo said:
I was still curious so i went googling. I think u should try a different cable and another usb port and different computer. It has fixed this issue for some people. Others said to try odin but what you're doing should really work. Otherwise there is a hardware failure and replacement parts dont seem to be an option... except at best a pogo connector cable in case the microusb jack is borked. I hope someone else chimes in for you. I haven't had any experience with this device. Maybe take some comfort in the asus nexus 10 coming out in a few months?
Click to expand...
Click to collapse
Hi all,
thanks for your suggestions/comments. I did quite a lot of reading while trying to get this sorted, and the suggestion to check different cables/ports was popping up a lot.
I was on holiday - I tried all ports of the laptop, and 2 cables, with no success. Let me stress that with my first 2 cables the table was recognised - I couldn't just write (anything).
I didn't have access to more cables/computers and I though that I had done my homework with 2 cables/3 USB ports.
I was wrong; once I was back home I managed to sort it out in few minutes with a third cable.
I hope that my error does help anyone else reading this.
Right now I would like to know if there is some kind of cable that I can buy and know that it will work... Does anyone have any suggestions?

4ndres said:
Hi all,
thanks for your suggestions/comments. I did quite a lot of reading while trying to get this sorted, and the suggestion to check different cables/ports was popping up a lot.
I was on holiday - I tried all ports of the laptop, and 2 cables, with no success. Let me stress that with my first 2 cables the table was recognised - I couldn't just write (anything).
I didn't have access to more cables/computers and I though that I had done my homework with 2 cables/3 USB ports.
I was wrong; once I was back home I managed to sort it out in few minutes with a third cable.
I hope that my error does help anyone else reading this.
Right now I would like to know if there is some kind of cable that I can buy and know that it will work... Does anyone have any suggestions?
Click to expand...
Click to collapse
Definitely stick to non-counterfeit OEM samsung cables as best as you can. In the past few years, Samsung/Apple have bastardized and corrupted the usb standard. It's usually only noticeable for charging, though in any practical use we find one usb cable is actually better than another It's really disappointing.

Flash the factory image via fastboot. And never use toolkits.
Sent from my Galaxy Nexus using XDA Premium HD app

Nexus 7 bootloader issues (unable to update to 4.23)

So this is kind of a long story but basically I had a Nexus 7 8GB model. I bricked it by destroying the bootloader and so I sent it back for RMA.
When the thing came back it worked but was laggy as hell. I did all the normal erases and whatnot, even flashed back to stock, still laggy. I figure the EMMC was toast. So I purchased a used Nexus 7 16GB motherboard from ebay.
The new motherboard worked but came encrypted so it booted and asked for the password. Of course, not knowing the password, I had to get into recovery and do a data reset. After all that I was able to root and a Cyanogen mod based ROM.
The problem I currently have is this: I am unable to flash or update the bootloader which is stuck on 4.13. When I try and push the kitkat bootloader via fastboot I get "BAD PARAMETER" and am unable to get passed this.
In case anyone cares I was able to follow the bricksafe flatline procedure and captured the existing bootloader partition blob which is now saved to my computer. I have tried to push that bootloader back to the device and that works but I CANNOT flash the damn 4.23 (kit kat) bootloader.
Basically my Nexus 7 charges at a snails pace now but works. Any help is very much appreciated!

I don’t think the outdated bootloader is the cause of slow charging. I’m using the latest 4.23 and it charges like a snail too.

possibly you are trying to flash (Google-supplied) trash to your bootloader?
[WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google

bftb0 said:
possibly you are trying to flash (Google-supplied) trash to your bootloader?
[WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google
Click to expand...
Click to collapse
I've checked the version of the bootloader, should be ok. Also I have tried flashing 4.13, lower versions, higher versions, etc.. all fail with the 'bad parameter'.
Also I get this when I do 'fastboot getvar all'.. note the size of the bootloader, on other devices this is a 0x000.. type number. Not on mine
Code:
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: 015d32205a3cDERP
(bootloader) product: grouper
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000368f00000
(bootloader) partition-type:userdata: ext4

Well, before we get too far off into the weeds (flashing) I will first have to agree with Lim Wee Haut - it is pretty unlikely that the bootloader has any effect on charging whatsoever. Tablets that are pure stock can pull 1.8-2A from the Asus OEM charger, so it's not obvious that software is ever the problem.
For instance, when the tablet is booted into the regular OS, it is impossible for the bootloader to be active. It's not like a PC BIOS (where software interrupt calls from the OS can be vectored through the BIOS). At most, the bootloader could set some hardware registers (e.g. in the SMB USB/charger chip) prior to loading the Linux kernel, but once the kernel is active, it is free to reprogram the hardware through it's device driver(s).
And what about when the tablet is completely off? This situation is less obvious to me - after all, when you plug the N7 onto the charger, a "charging animation" is displayed, and *something* is painting the screen... but I don't really know if that activity is being run by bootloader code or something in the tegra3 "miniloader".(The Tegra3 has a small ROM area in it for storing a tiny executable that can be programmed by the system designer and then protected by use of private keys)
In any event, the problem could be the charger, the battery, the cable, or any number of other things. Note that it is possible to observe the charging current using the "Current Widget" app plus a kernel that has the bq2745 current monitor patch in it, but you need to crank down the max clock and screen brightness - what you observe via that app is literally the current flowing ONLY in to the battery, not the total current provided by the charger. That means - because you can only get the tablet down to about 300 mA of consumption with the screen on - that the most charging current you will observe that way is about 1400-1500 mA on a charger that can put out 1.8A @ 5V.
OK, back to the flashing thing: I skimmed through two of the threads related to the "bricksafe flatline" hack, and I got the impression that once you have used that hack, there is no going back to fastboot for flashing bootloaders any longer - you are stuck using nvflash/wheelie thereafter. Is that incorrect? Or was it just that using fastboot with that patched bootloader (4.13-hacked?) causes flashing problems? It would be consistent with what you are reporting.
Sorry for the apparent randomness of this reply, just throwing out some ideas.

Battery Drain - x727 (System Services)

Hey guys! I'm having severe battery drain with only about 1 day of battery life, all being drained by System Services. Any way to diagnose what app or function specifically is causing this? I disabled gps and nfs. But this is still a problem.
I only have wifi and cellular network on.

Use greenify and hibernate system apps. I do it to all of em and it doesnt seem to affect the performance but it does save me that extra juice. Id say I get another 3 hors of sot from 6+ hours.

Most important ones to greenify

Doesn't greenify need root to take full advantage of the app
LeEco Pro3

Yeah but but that should be the least of problems now that we have unlocked bootloader and systemless root. Also xposed installer

Try my settings here...
http://forum.xda-developers.com/showpost.php?p=69867600&postcount=52
I've had wake locks and notification issues before and now they are gone.

Wait you can unlock the bootloader for x727? Can you point me to the thread please? There are often so many I can't find the reliable ones that work.
Also, this phone is pretty new, so no apps installed other than default. So it is so strange to me that it only has 1 day battery life and System Services being the one that takes 56% of the battery drain compared to other things such as OS taking 17%.

nothingto said:
Wait you can unlock the bootloader for x727? Can you point me to the thread please? There are often so many I can't find the reliable ones that work.
Also, this phone is pretty new, so no apps installed other than default. So it is so strange to me that it only has 1 day battery life and System Services being the one that takes 56% of the battery drain compared to other things such as OS taking 17%.
Click to expand...
Click to collapse
http://forum.xda-developers.com/le-pro3/development/x727-model-persistent-bootloader-unlock-t3500388
]
from page 4
I finished the setup and run fastboot again and it is good
so for anyone having the same issue as I was having of not able to unlock, just run: Fastboot Flash aboot emmc_appsboot.mbn
get the file from dr4stic zip file
C:\adb>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.089s]
finished. total time: 0.090s
C:\adb>fastboot oem unlock-go
...
OKAY [ 0.004s]
finished. total time: 0.005s

Bricked A1. a way to access data?

Hello,
My A1 is bricked since few days.
I've made few trys to get access on the data and i don't find any solution.
I can comunicate with the phone via Fastboot, but did not find a way to do something....
with fastboot oem device-info, i have this result:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.060s]
finished. total time: 0.062s
the oem unlock is not allowed.
With ADB, no success, the USB depuration was not on before the brick so....
Does someone know a way to do something?
is there is a way to load something from a SD card to turn on again the device without erasing everything?
Thank you very much.
Regards
Lebenjb

Nope there is no way. You basically hard brick the device. Did you lock the bootloader after modifying system?
The only way I know of is EDM mode, but it requires opening the phone and short curcuit some contact ponit.

Thanks for your answer.
The A1 get bricked by itself using it with the original rom.
I was so interested to have access to save some files!
I have a new phone, so I'm not in hurry, but if someone knows a way to make a recovery with data or just to have access to the files.
Then I will "wipe and delete" to give it to my son
Regards