[Q] Uber Noob needs help unlocking bootloader ubuntu. - HTC Sensation

Hello good people, i have the Sensation XE beats by dre and I'm currently stuck at the very last step of unlocking my bootloader. I have Ubuntu 13.04 andd i get the following error message: error: cannot load 'Unlock_code.bin': No such file or directory, - from this entry: sudo fastboot flash /home/Name/Downloads/Unlock_code.bin. I have tried various other combinations, i have a suspicion that its a pathway problem, but i can't figure it out, its my 5 straight hour trying to work this out, would really appreaciate the help. Also smashed my fist into the keyboard. Hopefully some one will take pitty from this last remark and help me.
Kind regards Shabibs.

shabibs said:
Hello good people, i have the Sensation XE beats by dre and I'm currently stuck at the very last step of unlocking my bootloader. I have Ubuntu 13.04 andd i get the following error message: error: cannot load 'Unlock_code.bin': No such file or directory, - from this entry: sudo fastboot flash /home/Name/Downloads/Unlock_code.bin. I have tried various other combinations, i have a suspicion that its a pathway problem, but i can't figure it out, its my 5 straight hour trying to work this out, would really appreaciate the help. Also smashed my fist into the keyboard. Hopefully some one will take pitty from this last remark and help me.
Kind regards Shabibs.
Click to expand...
Click to collapse
Just a question in the /home/NAME/Downloads/Unlock_code.bin did you infact change the NAME to your user name and is the file Unlock_code.bin really in your Downloads folder ?
If you dont know your username you can find it out like this:
Press CTRL + ALT + T
When the terminal opens you'll see something like this
Code:
[email protected]:~$
Where ajax is my user name and home is my computer name.
so in my case destination would go like this /home/ajax/Downloads/Unlock_code.bin or even simpler without user name ~/Downloads/Unlock_code.bin. you can choose which ever method you like.

Ajax1337 said:
Just a question in the /home/NAME/Downloads/Unlock_code.bin did you infact change the NAME to your user name and is the file Unlock_code.bin really in your Downloads folder ?
If you dont know your username you can find it out like this:
Press CTRL + ALT + T
When the terminal opens you'll see something like this
Code:
[email protected]:~$
Where ajax is my user name and home is my computer name.
so in my case destination would go like this /home/ajax/Downloads/Unlock_code.bin or even simpler without user name ~/Downloads/Unlock_code.bin. you can choose which ever method you like.
Click to expand...
Click to collapse
Yes, i did in fact change my name to my username, yes the file in is my downloads folder, i got my token with fastboot being placed in downloads folder as well.
thanks for responding Ajax .

shabibs said:
Yes, i did in fact change my name to my username, yes the file in is my downloads folder, i got my token with fastboot being placed in downloads folder as well.
thanks for responding Ajax .
Click to expand...
Click to collapse
Well UNIX systems are famous for the file hierarchy system if it tells you its not there its most likely not there. Another thing that comes to mind is check captial letters ( for instance user name is always lowercase and folder within your home are all caps ), second maybe try tabbing to the file for ex. /ho[TAB] it should finish to /home and do that for the rest of the path. Im sorry if you think that i am condescending im really not im just not aware how familiar with the linux environment.... i just thougth of something do CTRL + ALT + T type sudo fastboot flash then drag and drop the Unlock_code.bin into the terminal window will write out the path for you.

Thanks again, no worries about being condescending, the drag and drop function dosent work, i however got to here:
sudo fastboot flash /home/name/Downloads/Unlock_code.bin
unknown partition '/home/name/Downloads/Unlock_code.bin'
error: cannot determine image filename for '/home/name/Downloads/Unlock_code.bin'
Ajax1337 said:
Well UNIX systems are famous for the file hierarchy system if it tells you its not there its most likely not there. Another thing that comes to mind is check captial letters ( for instance user name is always lowercase and folder within your home are all caps ), second maybe try tabbing to the file for ex. /ho[TAB] it should finish to /home and do that for the rest of the path. Im sorry if you think that i am condescending im really not im just not aware how familiar with the linux environment.... i just thougth of something do CTRL + ALT + T type sudo fastboot flash then drag and drop the Unlock_code.bin into the terminal window will write out the path for you.
Click to expand...
Click to collapse

shabibs said:
Thanks again, no worries about being condescending, the drag and drop function dosent work, i however got to here:
sudo fastboot flash /home/name/Downloads/Unlock_code.bin
unknown partition '/home/name/Downloads/Unlock_code.bin'
error: cannot determine image filename for '/home/name/Downloads/Unlock_code.bin'
Click to expand...
Click to collapse
The first error i dont understand but the second sounds interesting.
you are typing this
Code:
sudo fastboot flash /home/name/Downloads/Unlock_code.bin
you should be typing this
Code:
sudo fastboot flash unlocktoken /home/name/Downloads/Unlock_code.bin
you are missing unlocktoken part in the command.

Well Axaj your wise ways have made me a man one step nearer a rooted phone. thank you so much.
all the best.
Ajax1337 said:
The first error i dont understand but the second sounds interesting.
you are typing this
Code:
sudo fastboot flash /home/name/Downloads/Unlock_code.bin
you should be typing this
Code:
sudo fastboot flash unlocktoken /home/name/Downloads/Unlock_code.bin
you are missing unlocktoken part in the command.
Click to expand...
Click to collapse

Thanks, Ajax!
Ajax1337 said:
The first error i dont understand but the second sounds interesting.
you are typing this
Code:
sudo fastboot flash /home/name/Downloads/Unlock_code.bin
you should be typing this
Code:
sudo fastboot flash unlocktoken /home/name/Downloads/Unlock_code.bin
you are missing unlocktoken part in the command.
Click to expand...
Click to collapse
Thank you so much for your clear, concise instructions. I was having the same problems and you got me through! :victory:

Related

HowTo (Windows) setup adb and fastboot to run like a DOS command in a command prompt

This will allow you to use adb and fastboot as if they were any other DOS command by typing them in a Command Prompt window from any directory.
Thanks to MERKJONES for giving me the idea... of course it only occurred to me after he mentioned it, that this would be quite useful for a lot of people besides ourselves
There are two ways of doing this.
#1
as per MERKJONES suggestion you can just add the files to your "windows/system32" directory.
#2
I like to keep my files organized in my own folders and be able to put them on any partition that I want. So to do this we just need to add the path of your folder containing adb and fastboot files to the windows Environment path.
IN XP/WINDOWS 7/VISTA
Right click on "my computer"
Left click on "properties"
Then.........
IN VISTA/WINDOWS 7 (this is an extra step for these two OS"s ignore this if you are using XP)
Click on "Advanced System Settings" in the left hand pane.
IN ALL WINDOWS
Make sure you are on the "Advanced" tab of the System Properties Panel.
Click on "Environment Variables" button.
Look for a line/variable that says "Path" in "System variables" pane.
Double click on "Path" to open a new window that should be say "Edit System Variable" or select the "Path" variable and click on the Edit Button.
Navigate to the end of the line/value and add
;path to files (where "path to files" is the location of your adb and fastboot files)
For example for me this is
;E:\AndroidFiles
So your path should look something like this
%SystemRoot%\system32;%SystemRoot%;E\AndroidFiles
Now reboot and you can open up a DOS Command Prompt window and use these programs in any directory you want by just typing them like any other DOS command.
Awesome.... I hope this can help some folks out
or as i have mentioned to MANY people in MANY threads, place the adb and fastboot in your system32 folder and you are good. but why should you use the search function when you can just post a new thread that says the same thing many other threads say
tubaking182 said:
or as i have mentioned to MANY people in MANY threads, place the adb and fastboot in your system32 folder and you are good. but why should you use the search function when you can just post a new thread that says the same thing many other threads say
Click to expand...
Click to collapse
LOL... Was thinking the same thing. This has been talked about over and over
PS... the "other" way of doing it I think was actually written by Stericson originally
momentarylapseofreason said:
LOL... Was thinking the same thing. This has been talked about over and over
PS... the "other" way of doing it I think was actually written by Stericson originally
Click to expand...
Click to collapse
You are right of course, I probably should have checked first... so no offense to anyone there are sooooo many threads to keep up with and a search can often bring up so many threads that is easy to miss something.
Actually I am sure that although Stericson may have also written it... he is far from the first person as it is really quite a common thing ... I just wanted to help let people know there was an easier way of doing things.
or as i have mentioned to MANY people in MANY threads, place the adb and fastboot in your system32 folder and you are good. but why should you use the search function when you can just post a new thread that says the same thing many other threads say
Click to expand...
Click to collapse
No offense.... but I personally don't like throwing file after file into my system32 folder as it can get messy... hence adding it to the Environment Path
Sometimes things can be repeated over and over and still get lost in a long thread... so I tried to make it more obvious for people to find the information
pixel-painter said:
You are right of course, I probably should have checked first... so no offense to anyone there are sooooo many threads to keep up with and a search can often bring up so many threads that is easy to miss something.
Actually I am sure that although Stericson may have also written it... he is far from the first person as it is really quite a common thing ... I just wanted to help let people know there was an easier way of doing things.
No offense.... but I personally don't like throwing file after file into my system32 folder as it can get messy... hence adding it to the Environment Path
Sometimes things can be repeated over and over and still get lost in a long thread... so I tried to make it more obvious for people to find the information
Click to expand...
Click to collapse
you dont have to put it in your system32 folder.
Put your backed up img files (all files from nandroid backup) in the same folder as fastboot, then open command-prompt
you then need to change directory to the location of the folder with this command
cd c:\where ever the fastboot folder is
(if its just in the c drive then the command would look like this)
cd c:\fastboot
enter, and you will then get
C:\fastboot>
then just type these commands.
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
this is how i restore and have been doing it this way everytime no problems.
^^ Sorry but I think you missed the point entirely The idea is to avoid doing that so one can use the programs from any directory.
Both #1 and #2 are really just 2 different ways of accomplishing the same thing
hi im using 5.0.1H build and would like to have root terminal control back. all my commands come back permission denied. Fastboot works for me for nandroid but when i try to follow the instructions on gaining superuser i get this
C:\Documents and Settings\Owner.YOUR-D592011E4B\Desktop\Superuser>adb push bin/s
u /system/bin
error: device not found
C:\Documents and Settings\Owner.YOUR-D592011E4B\Desktop\Superuser>adb shell chmo
d 4755 /system/bin/su
error: device not found
C:\Documents and Settings\Owner.YOUR-D592011E4B\Desktop\Superuser>adb uninstall
koushikdutta.superuser
- waiting for device -
what could i be doing wrong.
Hi,
Try doing:
adb devices see if your phone is recognized by the computer
adb remount enable read /write access
Now you can use your other commands.
maydaysos said:
hi im using 5.0.1H build and would like to have root terminal control back. all my commands come back permission denied. Fastboot works for me for nandroid but when i try to follow the instructions on gaining superuser i get this
C:\Documents and Settings\Owner.YOUR-D592011E4B\Desktop\Superuser>adb push bin/s
u /system/bin
error: device not found
C:\Documents and Settings\Owner.YOUR-D592011E4B\Desktop\Superuser>adb shell chmo
d 4755 /system/bin/su
error: device not found
C:\Documents and Settings\Owner.YOUR-D592011E4B\Desktop\Superuser>adb uninstall
koushikdutta.superuser
- waiting for device -
what could i be doing wrong.
Click to expand...
Click to collapse

[TOOL] sbf Flashing in Linux for Windows with Ubuntu Live CD

Here's a custom Ubuntu LiveCD made with ADB and the Linux sbf_flash script for sbf flashing your Droid 2 if you've failed in Windows with RSDlite or just want to have the convenience of flashing with only two Linux commands.
PLEASE READ ENTIRE POST BEFORE FLASHING ANYTHING!
If you want to follow this tutorial on your existing linux setup the sbf_flash file can be found on Google
READ OR RISK BRICK If you don't have the 2.3.2 update then you can sbf with EITHER the 2.2.0 (stock) or the 2.3.2(OTA update) but only if you don't have the update yet. Once you have the 2.3.2 update (through sbf or update.zip) you can ONLY sbf with the 2.3.2.sbf
Please have your phone charged up if not completely near complete or risk dealing with the consequences
Thanks Androidnite
1. Download 2.2.0.sbf file (for Droid 2 without 2.3.2 update only) or 2.3.20 HERE (for Droid 2's that have the 2.3.20 update) and put it on a flash drive. Yes even if you have one that you used with RSDlite.(this way we know you have the right one and it's all there)
2. Download the LiveCD ISO via torrent file attached below and unzip it and open the file with your choice of torrent program then BURN the downloaded file to a blank CD with your favorite burning software(I like DVD Decrypter or Imgburn). I recommend no faster than 4x in order to prevent burning "coasters".
3. Make sure your computer's BIOS is set to boot from the CD Drive then start your computer with the Disk in the drive.
4. Wait for the language list to pop up select "English". Then select "Try Ubuntu without installing"
5. Take the flash drive you put the .sbf file on and put it in your computer’s USB port and copy it to the same directory as the sbf_flash file. It will be the “Home” folder.
6. Plug your phone in via USB now and turn it off then hold the ‘up’ arrow on the keyboard and power on the phone to go into the bootloader.
NOTE: If your phone is not in operating condition Hold the 'UP' arrow on your keyboard and power on your phone for it to be recognized by your computer by entering the bootloader.
7. Open a command prompt by ‘CTRL+ALT+T’ or Applications>Accessories>Terminal
8. Type the first command then press enter and then do the same with one of the last two commands depending on the sbf you are trying to flash.
For both sbf's
Code:
chmod +x sbf_flash
Then
For the 2.2.0 sbf ONLY*OLD SBF*
Code:
sudo ./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf
Or
For 2.3.2 sbf ONLY
Code:
sudo ./sbf_flash VRZ_A955_2.3.20_1FF_01.sbf
NOTE: every space in the .sbf's title should be taken by an underscore "_" and shouldn't contain other spaces or the command will not be recognized because it doesn't follow the command's syntax.
Now your phone should start flashing. Let it go and it should reboot in 20-30 minutes.
That should be it let me know what problems you have.
Boot Loop?
facelessuser said if you get a boot loop after flashing wipe your data and cache in recovery.
Instructions:
1. Pull your Battery.
2. Replace battery and power on while holding down the X key.
3. Wait for the android triangle to load.
4. Press the Search key (the magnifying glass)
5. Use down arrow and navigate to wipe data/factory reset and press OK.
6. Reboot phone.
Click to expand...
Click to collapse
These instructions are by theecho.
Not getting the updated baseband? From BP_C_01.09.05P to BP_C_01.09.07P
NOTE: Be sure to update your baseband before you load a custom ROM as the update needs to see the blur on your phone.(If you root it before updating you might not be rooted afterward I don't know).
After you sbf with the 2.3.20 sbf file above and you don't see and updated baseband then you can use the Update.zip
to update your baseband by:
1. Download the update.zip and put it in the /sdcard/ folder or the root of the sdcard (same thing)
2. Shutdown D2
3. While you hold the 'X' button on the keyboard, turn on the D2
4. You should be in Stock recovery not Clockwork Recovery.
5. Press the 'magnifying glass' (search) button on keyboard to bring the menu up
6. Use the volume buttons to scroll and the Camera button to Select 'apply sdcard:update.zip'
7. Then choose 'reboot system now' and you should have an updated baseband.
Click to expand...
Click to collapse
Thanks for the info Quackers
Thanks:
First, thanks Matt4542 for putting the flashing in Linux tutorial which the commands I used were adapted from.
Next, a thanks to theecho for hosting the files for everybody’s access and making this really easy for me as I am a newbie to file hosting.
Last, but not least the inspiration for the custom Ubuntu ISO and help while making it...shad0wf0x from the XDA HTC Aria section(s) needs a thank you as well.
Please keep issues on this thread to allow faster responses.
Even if you used the RSDlite method by Darkonion first. RSDlite related posts should go there and Ubuntu method posts stay here.
Thanks and may your Droid 2 live on!
This sounds convenient. I am going to add this to the information directory.
I just want to say Thank you from the bottom of my heart for un-bricking my Droid 2 with the Ubunta Live CD program you created. I truly thought my phone was dead! I would very much like to send a donation your way for all the hard work you put into this. Please let me know by PM on how I can send the donation. Again, Thank you Thank you Thank you!!!!
Sent from my DROID2 using XDA App
lol no problem but i just enabled you to get to the flashing it was matt4542 and his linux tutorial that really fixed your phone....but if you really want to donate just head to the site where the files are hosted http://Droid2files.com and click on the donate button under my pic (yes that's what I really look like lol).
I thank you for wanting to thank me and for wanting to contribute to my well being!
p.s. think about thanking matt4542 and TheEcho for hosting the files (for FREE) and shad0wf0x for inspiring the LiveCD.
newk8600 said:
lol no problem but i just enabled you to get to the flashing it was matt4542 and his linux tutorial that really fixed your phone....but if you really want to donate just head to the site where the files are hosted http://Droid2files.com and click on the donate button under my pic (yes that's what I really look like lol).
I thank you for wanting to thank me and for wanting to contribute to my well being!
p.s. think about thanking matt4542 and TheEcho for hosting the files (for FREE) and shad0wf0x for inspiring the LiveCD.
Click to expand...
Click to collapse
Okay, donation just sent to you and TheEcho!
Now I just need a way to send Matt4542 and shad0wf0x their donation
Well Matt4542's donate link is here and I'm checking with shad0wf0x about his.
And thanks again for your donation(s)!
Got Ubuntu installed - files transferred to "home"/ubuntu directory - phone connected in bootloader - first chmod flash command didn't seem to do anything (returned to $ prompt), 2nd sbf flash gives command not found error - what am I doing wrong?
Jacklad said:
Got Ubuntu installed - files transferred to "home"/ubuntu directory - phone connected in bootloader - first chmod flash command didn't seem to do anything (returned to $ prompt), 2nd sbf flash gives command not found error - what am I doing wrong?
Click to expand...
Click to collapse
Click on the browser icon and navigate to this page. Then try using the copy/paste feature rather than typing it in yourself.
Sent from my DROID2 using XDA App
newk8600 said:
Well Matt4542's donate link is here and I'm checking with shad0wf0x about his.
And thanks again for your donation(s)!
Click to expand...
Click to collapse
You are more than welcome!
Matt's donation has been made, and patiently waiting to make donation to shad0wf0x
Jacklad said:
chmod flash command didn't seem to do anything (returned to $ prompt), 2nd sbf flash gives command not found error - what am I doing wrong?
Click to expand...
Click to collapse
The first command changes permissions (chmod) for 'sbf_flash' giving it the ability to execute (-x) so you won't see anything unless you change directory (cd) to the file and then list it with it's permissions with ('ls -l' both being lowercase L's)
For the second one can you tell me which command it can't find.
Is it troubled with 'sudo' (do with super user priveleges) or with sbf_flash. You might not have typed it in correctly. Remember the space between 'sudo' and './'
Sent from my DROID2 using XDA App
Terri M said:
You are more than welcome!
Matt's donation has been made, and patiently waiting to make donation to shad0wf0x
Click to expand...
Click to collapse
No donation necessary, happy to have helped, if you really want to donate to somebody, donate to the EFF (http://www.eff.org/).
I agree with shad0wf0x the EFF is helping with litigation on behalf of the Yes Men. If you don't know who they are I'd wiki them. They do some pretty amazing things.
Sorry I got off topic. lol
Jacklad said:
Got Ubuntu installed - files transferred to "home"/ubuntu directory - phone connected in bootloader - first chmod flash command didn't seem to do anything (returned to $ prompt), 2nd sbf flash gives command not found error - what am I doing wrong?
Click to expand...
Click to collapse
Alright, I'm having the same problem. I have bootloader up and the files transferred, here is what i typed in the terminal and what it gave me:
[email protected]:~$ chmod +x sbf_flash
[email protected]:~$ sudo ./sbf_flashDROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2 _USERBLD_ SECURE.sbf
sudo: ./sbf_flashDROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2: command not found
[email protected]:~$
I copied and pasted it directly from the post, so I don't know what is going wrong here. Please help.
Sudo ./sbf_flash droid2...... The problem is the lavk of a space netween sbf_glash and the filename
Sent from my DROID2 using XDA App
zibrah3ed said:
Sudo ./sbf_flash droid2...... The problem is the lavk of a space netween sbf_glash and the filename
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Failed again, but in a new way.
[email protected]:~$ chmod +x sbf_flash
[email protected]:~$ sudo ./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2 _USERBLD_ SECURE.sbf
SBF FLASH 1.08 (mbm)
DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2: No such file or directory
!! failed
im guessing that the file in the home folder has a slightly different name with spaces n stuff? I know my name doesnt have the spaces around the _USERBLD_ would that mess it up?
im guessing that the file in the home folder has a slightly different name with spaces n stuff? I know my name doesnt have the spaces around the _USERBLD_ would that mess it up?
Click to expand...
Click to collapse
Yes if the file name isn't exaclty the same it will show an error. Go to the file and right click it and select the filename and copy it. Then put it in place of the filename that registered the error. I'll check into the filename problem.
Sent from my DROID2 using XDA App
Sweet! It's finally started flashing. Hopefully it won't run into anymore weird things. Thanks a ton for the help!!
mgalceran said:
Thanks a ton for the help!!
Click to expand...
Click to collapse
No problem thanks for pointing out the name difference.
Sent from my DROID2 using XDA App
trying to unbrick my cousin's droid 2...i followed the directions carefully and I keep getting "waiting for phone" message in terminal, but I already have the phone plugged in and it is in bootloader mode, why won't it detect?
Thanks a lot for the help! My phone was doing the boot loop so I followed your guide. Now everything is just like it was when I got the phone. When everything was done and the computer said the phone was rebooting I still had the boot loop issue. I then saw where facelessuser said you have to clear the cache, so I did and she booted up normally.
Something funny to note, in the terminal it said Droid X found, I thought that would be an issue but everything worked fine.
Thanks again, you saved me!

Returning to stock, where can I find the stock image?

I need to warranty a phone but I need to turn it back to stock. I am using an older version of TWRP, I am guessing here but do I just download the factory image and flash it and I am done? It seems like everything I get when searching is geared towards the Pixel XL and using ADB rather than TWRP.
Thanks in advance.
Beacuse I part time as an internet troll, I have to chastise you for not reading threw this forum, because well that's why it's there, but hey we all can't use our Brian's all the time, but yes download the factory image for your phone Marlin for Pixel XL and Sailfish for Pixel unzip the file, make sure you have lastest usb drivers installed and click the flash all.bat.
Fastboot and flash factory image.
A wonderful guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
jerryhou85 said:
Fastboot and flash factory image.
A wonderful guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Click to expand...
Click to collapse
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
twilk73 said:
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
Click to expand...
Click to collapse
I'm not a good developer so I cannot answer you that question, but on Google official page, it is recommended to use fastboot or adb to flash factory images...
twilk73 said:
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
Click to expand...
Click to collapse
Because recovery and boot are sort of intermingled now. You would be writing over twrp at the same time you are trying to use it to flash.
Use the flashall bat file. If you want to save data edit out the -w from the bat file.
twilk73 said:
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
Click to expand...
Click to collapse
I am on linux let me just get that out of the way.
So I used adb to fastboot the factory image but nothing happens
the file is in downloads and in the fastboot file. So I type cd Downloads, cd fastboot, fastboot sailfish-nmf260 it all looks good and you can tell adm is working but nothing happens on the phone.
I am current only able to get the phone into fastboot mode I dont know what I messed up but I can no longer even boot into TWRP.
I must have succesfully removed the twrp recovery because no i get the no command screen. If I hold power and press up I can get into the stock android recovery. Is there a way to install the factory image still? Or is the process still the same and I need to adb fastboot? I might need to just do the abd fastboot on a windows computer at work tomorrow.
twilk73 said:
I must have succesfully removed the twrp recovery because no i get the no command screen. If I hold power and press up I can get into the stock android recovery. Is there a way to install the factory image still? Or is the process still the same and I need to adb fastboot? I might need to just do the abd fastboot on a windows computer at work tomorrow.
Click to expand...
Click to collapse
Download the factory image you want here. Unzip the entire contents to the same folder fastboot is located in. Then boot the phone to the bootloader, then plug it in to you computer. Then, if you're using Linux, double click the flash-all.sh file that got unzipped to your fastboot folder. If you're using a Windows computer, double click on the flash-all. bat file instead of the flash-all.sh file. Then sit back and wait. That's about all there is to it. One note. If you want to save your data, open the script you're going to use in a text editor and remove the -w toward the end of the script (remember to save your changes). If you want the phone wiped clean and like new again, just leave it as is.
robocuff said:
Download the factory image you want here. Unzip the entire contents to the same folder fastboot is located in. Then boot the phone to the bootloader, then plug it in to you computer. Then, if you're using Linux, double click the flash-all.sh file that got unzipped to your fastboot folder. If you're using a Windows computer, double click on the flash-all. bat file instead of the flash-all.sh file. Then sit back and wait. That's about all there is to it. One note. If you want to save your data, open the script you're going to use in a text editor and remove the -w toward the end of the script (remember to save your changes). If you want the phone wiped clean and like new again, just leave it as is.
Click to expand...
Click to collapse
ive done these steps but its failing to work. This is exactly what I am doing.
1. Download factory image.
2. Extract factory image into fastboot file.
the fast boot file is in the dowloads folder so I type.
cd Downloads
cd fastboot
fastboot flash-all.sh
iv also tried fastboot the sailfish-nmf260.img and boot.img and flashall. Ive tried several different ways this is what happens no mater what I type.
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
Click to expand...
Click to collapse
On the phone nothing happens. It appears that all I am getting is a list of options but none of the options seem to be working either.
I might add that the fastboot folder I am using was downloaded back when I installed twrp is it possible my fastboot file doesnt have the correct files to get the job done?
twilk73 said:
ive done these steps but its failing to work. This is exactly what I am doing.
1. Download factory image.
2. Extract factory image into fastboot file.
the fast boot file is in the dowloads folder so I type.
cd Downloads
cd fastboot
fastboot flash-all.sh
iv also tried fastboot the sailfish-nmf260.img and boot.img and flashall. Ive tried several different ways this is what happens no mater what I type.
On the phone nothing happens. It appears that all I am getting is a list of options but none of the options seem to be working either.
I might add that the fastboot folder I am using was downloaded back when I installed twrp is it possible my fastboot file doesnt have the correct files to get the job done?
Click to expand...
Click to collapse
Have you tried putting phone in fastboot mode and doubble click the flash all.sh file? That's how it is done on Windows.
Sent from my Google Pixel using XDA Labs
Sgace said:
Have you tried putting phone in fastboot mode and doubble click the flash all.sh file? That's how it is done on Windows.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Basically yes. But with linux you cant just double click. So in terminal I typed "cd Download, cd fastboot, fastboot flash-all.sh" that command will attempt to launch that file.
I feel like the issue is with adb on my laptop I tried making sure its updated but i got nothing so ill try to do it on a work computer when I get free time.
Its pretty crappy right now because I am without a phone but heck I pet the dog today during lunch instead of reading the news feed off my phone so I guess the dog is happy lol.
twilk73 said:
Basically yes. But with linux you cant just double click. So in terminal I typed "cd Download, cd fastboot, fastboot flash-all.sh" that command will attempt to launch that file.
I feel like the issue is with adb on my laptop I tried making sure its updated but i got nothing so ill try to do it on a work computer when I get free time.
Its pretty crappy right now because I am without a phone but heck I pet the dog today during lunch instead of reading the news feed off my phone so I guess the dog is happy lol.
Click to expand...
Click to collapse
I don't think you can flash it with fastboot. In Windows, at the command prompt, you just type flash-all.bat and the batch file will run. It contains all the necessary fastboot commands. Perhaps that's where you're going wrong. Try just typing flash-all.sh. Leave the fastboot out.
twilk73 said:
Basically yes. But with linux you cant just double click. So in terminal I typed "cd Download, cd fastboot, fastboot flash-all.sh" that command will attempt to launch that file.
I feel like the issue is with adb on my laptop I tried making sure its updated but i got nothing so ill try to do it on a work computer when I get free time.
Its pretty crappy right now because I am without a phone but heck I pet the dog today during lunch instead of reading the news feed off my phone so I guess the dog is happy lol.
Click to expand...
Click to collapse
Try this for sailfish (fix accordingly if marlin, username of course is common sense, if still confused, you shouldn't be using linux)
I build and use debian sid
Code:
cd /home/username/Downloads
tar xvf sailfish-opr3.170623.008-factory-bb8bb3a3.zip -C /home/username
cd /home/username/sailfish-opr3.170623.008
tar xvf image-sailfish-opr3.170623.008.zip
cd /home/username/sailfish-opr3.170623.008
./flash-all.sh
If you need the latest adb/fastboot name it something like google.sh
Code:
#!/bin/bash
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
cp platform-tools/adb /usr/bin/adb
cp platform-tools/fastboot /usr/bin/fastboot
piperx said:
Try this for sailfish (fix accordingly if marlin, username of course is common sense, if still confused, you shouldn't be using linux)
I build and use debian sid
Code:
cd /home/username/Downloads
tar xvf sailfish-opr3.170623.008-factory-bb8bb3a3.zip -C /home/username
cd /home/username/sailfish-opr3.170623.008
tar xvf image-sailfish-opr3.170623.008.zip
cd /home/username/sailfish-opr3.170623.008
./flash-all.sh
If you need the latest adb/fastboot name it something like google.sh
Code:
#!/bin/bash
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
cp platform-tools/adb /usr/bin/adb
cp platform-tools/fastboot /usr/bin/fastboot
Click to expand...
Click to collapse
Sorry I wish I could try this. I had access to a windows computer at work and I was able to get everything done. After doing it at work I have a feeling I wasnt placing the files in the correct folder together to get it to start the update. It can be hard doing this on something other than windows for a dummy like me because most of the tutorials for things like this seem to be windows oriented. Regardless its done. I couldnt lock the boot loader on the windows computer though oddly but no big deal because I can do it on my laptop.
Thanks for all the help guys.

Another Bootloop Help Request

I'm trying to resurrect this device. I can't recall the exact past of it because it's been so long. I am definitely unlocked and had a custom ROM. I'm willing to try anything before smash.
I've tried to hold the reset pinhole for 30 seconds many times with no difference.
My current behavior is:
Power on > ASUS logo > Linux penguins > TWRP 3.0.0-0 logo > Repeat
Behavior is the same with Vol down held.
My only hope is with Power + Vol up. I get to a blank screen and then I can see that my Windows 7 PC can't install the drivers.
I can't see the device in ADB command window which I have some experience with.
I'm guessing that my first order of action is to sort out my drivers issue and something with NV flash?
Thank you in advance.
echardcore said:
I'm trying to resurrect this device. I can't recall the exact past of it because it's been so long. I am definitely unlocked and had a custom ROM. I'm willing to try anything before smash.
I've tried to hold the reset pinhole for 30 seconds many times with no difference.
My current behavior is:
Power on > ASUS logo > Linux penguins > TWRP 3.0.0-0 logo > Repeat
Behavior is the same with Vol down held.
My only hope is with Power + Vol up. I get to a blank screen and then I can see that my Windows 7 PC can't install the drivers.
I can't see the device in ADB command window which I have some experience with.
I'm guessing that my first order of action is to sort out my drivers issue and something with NV flash?
Thank you in advance.
Click to expand...
Click to collapse
APX mode and nvflash won't help you unless you generated your device specific nvflash blobs back when the tablet was still working and you would remember that. It's an involved process.
So you cannot boot into the fastboot screen? It goes directly to the TWRP splash screen?
Does it stay there for any length of time or does it immediately reboot?
berndblb said:
APX mode and nvflash won't help you unless you generated your device specific nvflash blobs back when the tablet was still working and you would remember that. It's an involved process.
So you cannot boot into the fastboot screen? It goes directly to the TWRP splash screen?
Does it stay there for any length of time or does it immediately reboot?
Click to expand...
Click to collapse
No fastboot. TWRP logo remains on the screen for a period of time. Maybe 10 seconds. Tablet is in the electronics recycle pile... Are you saying there's a chance?
echardcore said:
No fastboot. TWRP logo remains on the screen for a period of time. Maybe 10 seconds. Tablet is in the electronics recycle pile... Are you saying there's a chance?
Click to expand...
Click to collapse
Yes. 10 seconds should be plenty to use bootit.ko - with a little practice. You may have to try a few times to get it right, but you can always do the process in several steps: First push the file to the sdcard, insmod it on the next try. Some guy even created a little batch file for the commands because he had very small window in which to run them. This is all Greek to you, I know. But read this and you'll understand:
www.transformerforums.com/forum/tra...my-transformer-tf700-boots-only-recovery.html
If you manage to kick it back into the bootloader I would then flash the Asus firmware in fastboot right away. Since you don't remember what was wrong with it to begin with it would be best to start from a clean slate and that would be with a pure stock tablet. It's easy to flash a recovery and custom rom from there....
Instructions for that are here: https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
The link for the Asus firmware is broken again. Get it here: https://www.androidfilehost.com/?fid=817550096634791660
Good luck
Edit: And before you ditch it, send it to me. I'll pay for the shipping. PM me if you can't get it to work
berndblb said:
Yes. 10 seconds should be plenty to use bootit.ko - with a little practice. You may have to try a few times to get it right, but you can always do the process in several steps: First push the file to the sdcard, insmod it on the next try. Some guy even created a little batch file for the commands because he had very small window in which to run them. This is all Greek to you, I know. But read this and you'll understand:
www.transformerforums.com/forum/tra...my-transformer-tf700-boots-only-recovery.html
If you manage to kick it back into the bootloader I would then flash the Asus firmware in fastboot right away. Since you don't remember what was wrong with it to begin with it would be best to start from a clean slate and that would be with a pure stock tablet. It's easy to flash a recovery and custom rom from there....
Instructions for that are here: https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
The link for the Asus firmware is broken again. Get it here: https://www.androidfilehost.com/?fid=817550096634791660
Good luck
Edit: And before you ditch it, send it to me. I'll pay for the shipping. PM me if you can't get it to work
Click to expand...
Click to collapse
Thanks very much! Will let you know. I really appreciate it!
berndblb said:
Yes. 10 seconds should be plenty to use bootit.ko - with a little practice. You may have to try a few times to get it right, but you can always do the process in several steps: First push the file to the sdcard, insmod it on the next try. Some guy even created a little batch file for the commands because he had very small window in which to run them. This is all Greek to you, I know. But read this and you'll understand:
www.transformerforums.com/forum/tra...my-transformer-tf700-boots-only-recovery.html
If you manage to kick it back into the bootloader I would then flash the Asus firmware in fastboot right away. Since you don't remember what was wrong with it to begin with it would be best to start from a clean slate and that would be with a pure stock tablet. It's easy to flash a recovery and custom rom from there....
Instructions for that are here: https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
The link for the Asus firmware is broken again. Get it here: https://www.androidfilehost.com/?fid=817550096634791660
Good luck
Edit: And before you ditch it, send it to me. I'll pay for the shipping. PM me if you can't get it to work
Click to expand...
Click to collapse
No bootloader : (
Also tried the 2nd command alone upon subsequent boots with the same result.
EDIT AGAIN: Also tried adb shell by itself:
Code:
X:\Program Files\ANDROID\SDK\platform-tools>adb shell
~ # ←[6n
WTH?
Code:
X:\Program Files\ANDROID\SDK\platform-tools>adb push bootit.ko /sdcard/
bootit.ko: 1 file pushed. 1.1 MB/s (27690 bytes in 0.023s)
X:\Program Files\ANDROID\SDK\platform-tools>adb shell insmod /sdcard/bootit.ko
error: closed
echardcore said:
No bootloader : (
Also tried the 2nd command alone upon subsequent boots with the same result.
EDIT AGAIN: Also tried adb shell by itself:
Code:
X:\Program Files\ANDROID\SDK\platform-tools>adb shell
~ # ←[6n
WTH?
Code:
X:\Program Files\ANDROID\SDK\platform-tools>adb push bootit.ko /sdcard/
bootit.ko: 1 file pushed. 1.1 MB/s (27690 bytes in 0.023s)
X:\Program Files\ANDROID\SDK\platform-tools>adb shell insmod /sdcard/bootit.ko
error: closed
Click to expand...
Click to collapse
You are close. Looks as if you were able to push bootit.ko to the sdcard, but let's check the file system
run the command
adb ls /sdcard/
berndblb said:
You are close. Looks as if you were able to push bootit.ko to the sdcard, but let's check the file system
run the command
adb ls /sdcard/
Click to expand...
Click to collapse
Ah-ha! I get this if I execute the command over and over as it boots until right when it reaches the TWRP screen.
Code:
X:\Program Files\ANDROID\SDK\platform-tools>adb ls /sdcard/
000041ff 00000000 38880412 .
000041ed 00000000 38880412 ..
echardcore said:
Ah-ha! I get this if I execute the command over and over as it boots until right when it reaches the TWRP screen.
Code:
X:\Program Files\ANDROID\SDK\platform-tools>adb ls /sdcard/
000041ff 00000000 38880412 .
000041ed 00000000 38880412 ..
Click to expand...
Click to collapse
Mhh, no idea what that is. Definitely not what I hoped for
That command was supposed to list the contents of your internal storage and what I wanted to see was booit.ko
Either the command does not get through or it is dead wrong :cyclops:
Let me think about this a little and you keep trying in the meantime :highfive:
Tried to run the commands just now and the pic shows what I get.
It looks as if your return is similar to the first 2 lines from what I get with the ls command.
Don't know if your sdcard is totally hosed so that the kernel module does not even write to it?
What I do not understand is that the insmod command fails on my tablet. My knowledge is insufficient to interpret "bad address", but I suspect that bootit.ko was created for one of the _that kernels and I'm running Katkiss on this tablet which has a different kernel. Sorry, this is the end of the rope for me. I can use tools but I do not create them and cannot adapt them to a different situation... :crying:
I wonder if a format command would stop the loop and enable you to boot back into the bootloader, but this is complete speculation and a long stretch grasping for straws....
But wth - before you recycle it, try to squeeze this into the adb window (everything behind the # is just commentary, do not use):
Code:
adb shell kill -19 recovery #hoping this will give you some more time, try the commands below without it if it does not work
make_ext4fs /dev/block/mmcblk0p8 #should format the data partition
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1 #clear misc partition of any commands stuck there
echardcore said:
I can't see the device in ADB command window which I have some experience with.
I'm guessing that my first order of action is to sort out my drivers issue and something with NV flash?
Thank you in advance.
Click to expand...
Click to collapse
Any luck in FASTBOOT?
Bootlooped Tf700t
echardcore said:
Thanks very much! Will let you know. I really appreciate it!
Click to expand...
Click to collapse
berndblb said:
Yes. 10 seconds should be plenty to use bootit.ko - with a little practice. You may have to try a few times to get it right, but you can always do the process in several steps: First push the file to the sdcard, insmod it on the next try. Some guy even created a little batch file for the commands because he had very small window in which to run them. This is all Greek to you, I know. But read this and you'll understand:
www.transformerforums.com/forum/tra...my-transformer-tf700-boots-only-recovery.html
If you manage to kick it back into the bootloader I would then flash the Asus firmware in fastboot right away. Since you don't remember what was wrong with it to begin with it would be best to start from a clean slate and that would be with a pure stock tablet. It's easy to flash a recovery and custom rom from there....
Instructions for that are here: https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
The link for the Asus firmware is broken again. Get it here: https://www.androidfilehost.com/?fid=817550096634791660
Good luck
Edit: And before you ditch it, send it to me. I'll pay for the shipping. PM me if you can't get it to work
Click to expand...
Click to collapse
I'm sorry, but are you saying that we can ship the bootlooped tablet to you and you can fix it?
I think he's saying, before you throw it away, he's take it off your hands and pay the shipping for you to send it do him. But he's keeping it.
NP
chiefkevbe said:
I'm sorry, but are you saying that we can ship the bootlooped tablet to you and you can fix it?
Click to expand...
Click to collapse
Nektopoli said:
I think he's saying, before you throw it away, he's take it off your hands and pay the shipping for you to send it do him. But he's keeping it.
NP
Click to expand...
Click to collapse
I'm saying: Maybe, under certain circumstances and conditions I may be able to help. But I am not going to advertise a "fix your tablet for free" service here. I don't have the means or the time for that.
I'd rather help you learn how to fix it, but if all fails contact me on PM to discuss this.
berndblb said:
I'm saying: Maybe, under certain circumstances and conditions I may be able to help. But I am not going to advertise a "fix your tablet for free" service here. I don't have the means or the time for that.
I'd rather help you learn how to fix it, but if all fails contact me on PM to discuss this.
Click to expand...
Click to collapse
Thanks again for trying to help me here. I've been playing again with no luck. I think I might try on a Linux box or bootable USB. Probably not until the next time I "work" from home lol.
@echardcore when you hold the VOL-DOWN then press the power on button do you even get the bootloader version readout screen? [See PIC of the TF201t bootloader]
NP
Nope. Goes straight to TWRP splash screen even without holding any volume buttons.
echardcore said:
Nope. Goes straight to TWRP splash screen even without holding any volume buttons.
Click to expand...
Click to collapse
Ok, I'd try sending it a reboot command from a PC with fastboot just to see if the tablet will still respond.
NP
It won't if it's not in fastboot mode
Bootit.ko is your best chance. Give it a shot and if you can't get it done I'll give it a shot

Help Pulling EFI Firmware

Hello,
I am trying to figure out how to either inject a custom bootloader like Clover onto my Nvidia Shield, or to Modify the existing EFI bootloader itself or with a modification to a Recovery program such as TWRP in order to be able to use a custom bootloader to select "Boot From Usb"
I figure I oughta make a backup, but I do not know how to backup my bootloader either....
I think I understand how to look at the shield's partitions now to find the one with the bootloader, I'm just nervous to proceed...
I have been researching for a week and have learned amazing tidbits of knowledge on the sublayers of the shield, and a lot of its partitions...
I was able to install a custom OS, modified GAPPS, and root on my shield, I am just hung up on this final part....
If anyone would care to share even a bread crumb where to start, I Would Be Ever So Grateful
Download Clover EFI Bootloader - MajorGeeks
Clover EFI Bootloader can boot OS X, Windows, and Linux on Mac or PC with UEFI or BIOS firmware.
www.majorgeeks.com
Root Nvidia Shield TV Pro 2019 Version
THIS IS OUTDATED https://forum.xda-developers.com/t/bootmod-root-your-shield-in-1-minute-2015-2017-2019.4524873/ REPLACES THIS IF YOU WANT ANDROID OR USE THIS GUIDE...
forum.xda-developers.com
I forgot to ask, IS THERE A PULL COMMAND FROM FASTBOOT, TO COPY PARTITIONS? MY GOOGLE FU IS SUPER BUT MAN I AM HAVING A HARD TIME FINDING EXACTLY WHAT I'M LOOKING FOR :-(
jenneh said:
I forgot to ask, IS THERE A PULL COMMAND FROM FASTBOOT, TO COPY PARTITIONS? MY GOOGLE FU IS SUPER BUT MAN I AM HAVING A HARD TIME FINDING EXACTLY WHAT I'M LOOKING FOR :-(
Click to expand...
Click to collapse
Typically partions get 1:1 bitwisely copied to PC by dd command ( AFAIK it's present in every Android distribution ) what can be achieved by means of ADB.
Example - for Windows PC only:
Code:
adb devices
adb exec-out "dd if=[BLOCK-NAME-OF-PARTITION-HERE] bs=4096" > C:\[NAME-OF-BACKUP-FILE-HERE]
jwoegerbauer said:
Typically partions get 1:1 bitwisely copied to PC by dd command ( AFAIK it's present in every Android distribution ) what can be achieved by means of ADB.
Example:
Code:
adb devices
adb exec-out "dd if=[BLOCK-NAME-OF-PARTITION-HERE] bs=4096" > C:\[NAME-OF-BACKUP-FILE-HERE]
Click to expand...
Click to collapse
Thank You! That is thinking outside the box haha I kept trying to do it through fastboot knowing there is very limited amount of commands, not realizing that Would Never Work. I appreciate Your Time! I will try adb now!!! It's so funny, it seems like such a simple answer but sometimes we see so many paths, it's hard to know which one to take...
jwoegerbauer said:
Typically partions get 1:1 bitwisely copied to PC by dd command ( AFAIK it's present in every Android distribution ) what can be achieved by means of ADB.
Example - for Windows PC only:
Code:
adb devices
adb exec-out "dd if=[BLOCK-NAME-OF-PARTITION-HERE] bs=4096" > C:\[NAME-OF-BACKUP-FILE-HERE]
Click to expand...
Click to collapse
Hello! May I pry your mind for a moment?
I ran this command on my shield "fastboot erase system" except instead of running it directly in the command line on windows,
I made a batch file for it, and when I ran the batch, it succeeded but it did something strange, it printed this message inside the batch
"
{\rtf1\ansi\deff0\nouicompat{\fonttbl{\f0\fnil\fcharset0 Calibri;}}
{\*\generator Riched20 10.0.19041}\viewkind4\uc1
\pard\sa200\sl276\slmult1\f0\fs22\lang9 fastboot erase system\par
fastboot erase boot\par
\par
}
"
It completely deleted the two commands i had in there and pasted that instead... do you know what that is by any chance or Why it did that? o.o It is fascinating!
I can not understand what you are doing: For me it is complete confusion.
jwoegerbauer said:
I can not understand what you are doing: For me it is complete confusion.
Click to expand...
Click to collapse
No worries, thank you for your time, Seriously. That ADB suggestion was Exactly what I Needed... Have a beautiful day!

Categories

Resources