Database Info

[Q] Serious problem

Hi,
please help me! I hope it is not a brick.
I wanted to make full wipe. I made factory reset in recovery and then wiped sdcard.. Now I cannot boot ROM because there is no one and I have nothing on my SD. So I even cannot copy rom or backup back to phone.
Is there any way out? (
EDIT: I think I can push files (e.g. backup) through adb, right? I installed adb for dummies but when I want to execute SDKmanager.exe. it only opens black window and immediately closes it. I cannot continue

devcager said:
Hi,
please help me! I hope it is not a brick.
I wanted to make full wipe. I made factory reset in recovery and then wiped sdcard.. Now I cannot boot ROM because there is no one and I have nothing on my SD. So I even cannot copy rom or backup back to phone.
Is there any way out? (
EDIT: I think I can push files (e.g. backup) through adb, right? I installed adb for dummies but when I want to execute SDKmanager.exe. it only opens black window and immediately closes it. I cannot continue
Click to expand...
Click to collapse
Access your commands through a terminal window, like start > run > cmd to get into the prompt.
and from there work your way to your directory where you have placed it, and execute the command from that directory directly.

..

Thanks!
In the end I used adb to push backup in recovery...
All this I did because I wanted wipe my device - today I woke up and got a call and found out that my earphone stopped working I am afraid that it is due to condensation and next oxidation... I did not do anything wrong but when you come from cold winter weather into a warm flat it can happen Now I need to send it and hope the warranty will pass..
Anyway, I was looking for complete unroot process and found several advices. I am not clever from them. Is it enough to flash stock ROM? Recovery will be removed as well??

..

Election Day said:
Flash a stock ROM (this will also flash the stock recovery) and relock the bootloader with fastboot oem lock afterwards.
Click to expand...
Click to collapse
Ok. I have everything done but the relocking. Could you tell me how shall I do this? I tried to write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English) Cannot lock it

devcager said:
Ok. I have everything done but the relocking. Could you tell me how shall I do this? I tried to write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English) Cannot lock it
Click to expand...
Click to collapse
1.Switch off your phone
2.Connect your phone to your PC throught the USB cable
3.Switch on phone into fastboot
4.Provided that you have the driver for windows for the phone installed open Start/run/cmd (from your PC)
5.From the Android-SDK/platform-tools run the following "fastboot oem lock".
like :
C:\Android-sdk\platform-tools\fastboot oem lock
this will lock it immediately ...

mahanddeem said:
1.Switch off your phone
2.Connect your phone to your PC throught the USB cable
3.Switch on phone into fastboot
4.Provided that you have the driver for windows for the phone installed open Start/run/cmd (from your PC)
5.From the Android-SDK/platform-tools run the following "fastboot oem lock".
like :
C:\Android-sdk\platform-tools\fastboot oem lock
this will lock it immediately ...
Click to expand...
Click to collapse
it works only in "tools" and then it just says "waiting for device" and stucks When I tried "fastboot devices" it says nothing... I tried to reinstall drivers but maybe I have some old version? When I am in Windows copying files etc. it works well.

1. Make sure you open the command prompt IN in the folder with fastboot.exe.
2. Put the phone in fastboot mode.
3. In the command prompt type fastboot devices.
It will now show your serial number. If not its either you are such a noob that you managed to screw that up or the fastboot drivers are not installed. Or both.

albundy2010 said:
1. Make sure you open the command prompt IN in the folder with fastboot.exe.
2. Put the phone in fastboot mode.
3. In the command prompt type fastboot devices.
It will now show your serial number. If not its either you are such a noob that you managed to screw that up or the fastboot drivers are not installed. Or both.
Click to expand...
Click to collapse
OK. I really dont understand what could have been screwed up. Ok. It doesnt show anything. Just nothing. Cen you please send me the link for the drivers which should work? Maybe there is the problem. Fastboot drivers are something else than drivers for adb to be working? Because I dont know whats wrong. Thanks...

devcager said:
OK. I really dont understand what could have been screwed up. Ok. It doesnt show anything. Just nothing. Cen you please send me the link for the drivers which should work? Maybe there is the problem. Because I dont know whats wrong. Thanks...
Click to expand...
Click to collapse
If you have i9023 you need to add a line into the sdk for driver. You can search the tutorial threads for it.
Sent from my Nexus S using Tapatalk

try this
just check if you have fastboot and adb on the same folder, when I've rooted mine's got this issue, if cmd report "the command is an external one" simply means there is no such program in the folder you are in
copy both adb and fastboot in tools and platform-tools too, so you can run the command in both folder
cd>desktop > cd android>cd android-sdk> cd tools (then run adb or fastboot)
cd>desktop > cd android>cd android_sdk> cd platform-tools (thr run adb or fastboot)

1. Find out exactly what phone model you have if you don't know already.
2. Do the same for your computers os . Including 32 or 64 bit.
3. Combine that info and search the forum or just Google search. How to install fastboot drivers for phone model in step 1 with the os in step 2.

..

Thank you all. I decided to unroot it and relock it using Odin software which was great and quick. So I am done.... Adb has a lot of problems with drivers, commands, paths. This way was much easier

adb has no issues. User error.

albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
+1
Sent from my GT-I9100 using XDA App

albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
Maybe you are right. Maybe it was driver problem which I solved and then immediately used odin. Anyway, it is user friendly and I am finally done with what I wanted

albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
Agreed, but not the user friendliest.
For the OP: Good luck having it repaired!

Blackstone - Fastboot Problem

Well I am trying to Flash the latest fagyi NAND for Blackstone - http://forum.xda-developers.com/showthread.php?t=1914723
So I did everything, but when I reached the fastboot thingy, I did this:
After ROM flashed, took batter out and restarted device.
Blue screen showed up, forced fastboot, ready USB state, so I connected to PC
Then I opened a command prompt, so now what should I enter in the command prompt! I am using fagyi's fastboot!
Thanks, in advance!

Sorry for double posting, but please someone answer me, or atleast give me a tip/advice!

Do you mean this part?
13. Now connect the Blackstone to your Windows OS and open a CLi/Command prompt
14. Within CLi go to the directory where you place the 'adb files & fastboot.exe' files (from step 2)
15. Type: fastboot flash recovery recovery.img (this will flash install the custom CWR)
16. Then type: fastboot boot recovery.img (this will reboot your Blackstone into CWR)
Click to expand...
Click to collapse

post-mortem said:
Do you mean this part?
Click to expand...
Click to collapse
Yeah that exactly!

Step 2 says
2. Extract the 'adb files & fastboot.exe' files to a folder
Click to expand...
Click to collapse
so the 1st question is, do you know what folder you put those files in? Note that we're talking about your computer, not your phone. On your computer, open a command prompt by doing Start -> Run... -> cmd (This is Step 13). Navigate to the folder from Step 2 This is Step 14). Then, type the appropriate commands from Steps 15 & 16.
Still don't get it? Ask away!

Um the files are placed in C:
And when I enter the commands, it says 'File too big to fit in memory"? What do I do now?

So your step 14 should be to type cd c:\, then 15 fastboot flash recovery recovery.img
Is that when you get the error?

Yes, exactly then!

Ok, try redownloading the fastboot program, or install the Android SDK to get the newest version directly from Google.

I've redowloaded it alot of times! And I already have the Android SDK and am using the latest one!

Are you sure that you're using the correct version of all relevant programs? By that, I mean 32 vs 64-bit.

I am not sure about that, how should I know?

Do you get the same error if you type fastboot devices ?

I havent typed that yet!
EDIT: No I get this - "RH104393397 fastboot"

Please Admin/Moderator, lock this thread, my problem is now fixed!

Angat said:
Please Admin/Moderator, lock this thread, my problem is now fixed!
Click to expand...
Click to collapse
Can you tell me how do you fix the problem ? I have the same problem

My Rooted N5, & Android 4.4.2

Hey guys, I have a rooted N5 with CF Auto Root. I have been trying to do a update to 4.4.2. however, every time I download it and go to install, I get a error upon reboot, The update doesn't install. I'm still rather new with rooting phones. I was hoping someone could give me some insight on how to install this? I had a friend tell me its possible to manually install the update if I could locate the files?
Thanks!

Hi,
Take a look here: [INFO] Nexus 5 OTA Help-Desk, read closely

viking37 said:
Hi,
Take a look here: [INFO] Nexus 5 OTA Help-Desk, read closely
Click to expand...
Click to collapse
Ahh, excellent, thank you! However I'm a bit confused on what ADB Sideload is and how to use it. XD

ItsStormy said:
Ahh, excellent, thank you! However I'm a bit confused on what ADB Sideload is and how to use it. XD
Click to expand...
Click to collapse
Install the android-sdk platform- tools, look here for how to https://www.google.nl/url?sa=t&rct=...OWoMssTikMpokJ6TtwEND5A&bvm=bv.61190604,d.bGQ.
Then put the rom/OTA you want in the platform-tools folder, reboot in recovery and select adb sideload and then in cmd type `adb sideload namerom.zip` to flash the zip.

Ooops, got it sorted, thanks guys!

ItsStormy said:
Hi again, so I've gone over the tutorials. However when I attempt to go through the steps within http://forum.xda-developers.com/showthread.php?t=2523217 - I keep getting the error 'adb' is not recognized as an internal or external command, operable program or batch file. What am I doing wrong?
Thanks!
Click to expand...
Click to collapse
You have not created a path, look here http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/ item 5, 6 and 7.

Okay, so apparently thats only a issue if my phone isnt rooted judging by the first tutorial, it states I should follow section B.
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
However, When I boot into Recovery Mode, I get a error stating No Command.

ItsStormy said:
Okay, so apparently thats only a issue if my phone isnt rooted judging by the first tutorial, it states I should follow section B.
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
However, When I boot into Recovery Mode, I get a error stating No Command.
Click to expand...
Click to collapse
Do you have a custom recovery? choose B. If on stock recovery boot in a custom recovery by placing the custom recovery.img in fastboot folder and type in cmd `fastboot boot namerecovery.img`, let it load and flash the OTA in recovery and boot up.

gee2012 said:
Do you have a custom recovery? choose B. If on stock recovery boot in a custom recovery by placing the custom recovery.img in fastboot folder and type in cmd `fastboot boot namerecovery.img`, let it load and flash the OTA in recovery and boot up.
Click to expand...
Click to collapse
Eh. I don't believe so, or I'm not entirely sure, I'm sorry.

ItsStormy said:
Eh. I don't believe so, or I'm not entirely sure, I'm sorry.
Click to expand...
Click to collapse
If you have stock recovery there should stand 3e recovery on top, if so reboot into bootloader and do what i wrote in the prior post. Or sideload the OTA with adb in stock recovery.

Thanks for the help gee2012
I leave you in good hands :good:

I've followed the steps for system variables.
C:\Program Files (x86)\Android\android-sdk;C:\Android-adb
However, I'm still receiving adb is not recognized from the terminal.
Any idea what I might be doing wrong? I'm sorry about noobing this thread up.

ItsStormy said:
I've followed the steps for system variables.
C:\Program Files (x86)\Android\android-sdk;C:\Android-adb
However, I'm still receiving adb is not recognized from the terminal.
Any idea what I might be doing wrong? I'm sorry about noobing this thread up.
Click to expand...
Click to collapse
Dumb question, but is adb.exe in the android-adb folder?

jd1639 said:
Dumb question, but is adb.exe in the android-adb folder?
Click to expand...
Click to collapse
Now that you mention it, apparently not. I did however find this. And it is either in that location. I went into AVD Manager, but I don't see anywhere where I can install ''Android SDK Platform-tools"
The adb tool has moved to platform-tools/
If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"
Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.

ItsStormy said:
I've followed the steps for system variables.
C:\Program Files (x86)\Android\android-sdk;C:\Android-adb
However, I'm still receiving adb is not recognized from the terminal.
Any idea what I might be doing wrong? I'm sorry about noobing this thread up.
Click to expand...
Click to collapse
Best is to install the sdk straight to the C drive, so C:\android-sdk and not in a folder. The path vaiables to add would be \android-sdk\platform-tools.

Please help , Stuck on Loading Screen.

I try to hard reset but I'm still stuck on loading screen. How do I add a zip file to my sd so I can flash it, since it doesn't even detect my oneplus on my computer? Please help me and lend me your knowledge and power =].

Can you boot in bootloader and connect it through adb and fastboo with your pc? in that case it would be easy to reflash everything

I can boot into fastboot and TWRP but I'm wondering how can I add file into my internal hard drive since it doesnt detect the phone on my computer?

Any help with some instructions would be really nice =] :good:

Do you see it using "adb devices" or "fastboot devices" ?
If not, you must update your adb drivers on your computer and reboot it

right now its on MTP USB Device as my device on my Device Manager, can you link me to the proper usb driver? Because I"m pretty sure I updated it and it was working while my phone is working. Also how can I check if its using adb devices?
bud77 said:
Do you see it using "adb devices" or "fastboot devices" ?
If not, you must update your adb drivers on your computer and reboot it
Click to expand...
Click to collapse

Also it said "Windows has determined the driver software for your device is up to date" but doesnt detect my phone?

Anyone still here so they can help me?

So as asked previously, when you connect via fastboot, and boot it into TWRP, do you see it via adb ("adb devices" command in the platform-tools folder)? Did you try adb push <filename> /sdcard/ ?

yes i see adb push , but there's no file there. How can i add file there?
Dzhedaj said:
So as asked previously, when you connect via fastboot, and boot it into TWRP, do you see it via adb ("adb devices" command in the platform-tools folder)? Did you try adb push <filename> /sdcard/ ?
Click to expand...
Click to collapse

Basically i'm in TWRP and i dont see any thing in recover or etc or in my sd, all blank so how can I put an image there to flash?

Anyone still here to have any answers to help?

which jeithis
http://i.imgur.com/378HzRp.png also get this image also

Use an adb push command to send a ROM zip to your phone.
Transmitted via Bacon

@M I N E, go read the sticky posts in the general section. It will explain how to do an adb push command.
@timmaaa and others have done a great job with some write ups for this device.

timmaaa said:
Use an adb push command to send a ROM zip to your phone.
Transmitted via Bacon
Click to expand...
Click to collapse
Or do a factory wipe then go into TWRP -> Advanced -> ADB Sideload -> Swipe
adb sideload <name-of.zip>.zip (ensure the .zip is in the same folder as your fastboot/adb) and then it'll send the zip over to the phone and flash.
I prefer the adb sideload method as it pretty much pushes the file over to the phone and then flashes it afterwards.
Either method is fine though.
If OP has problems with drivers, I recommend using http://forum.xda-developers.com/showthread.php?t=2386956 they work great.

what is the push load command? How can i push something if i dont have any file on my phone to flash? can you guys type out the command?

M I N E said:
what is the push load command? How can i push something if i dont have any file on my phone to flash? can you guys type out the command?
Click to expand...
Click to collapse
Read the post above you that I posted. Use that command as well as the instructions and you can flash a file using adb sideload.

well I try factory swipe nothing there, i check the TWRP , no files is there i mean nothing. And I cant do adb push because my when i type adb devices it doesnt recognized, because how can i turn on debugging if my phone doesnt have any rom?

M I N E said:
well I try factory swipe nothing there, i check the TWRP , no files is there i mean nothing. And I cant do adb push because my when i type adb devices it doesnt recognized, because how can i turn on debugging if my phone doesnt have any rom?
Click to expand...
Click to collapse
You're not reading my message properly. I'm telling you to do adb sideload. Please read what I said carefully word-by-word.
Or do a factory wipe then go into TWRP -> Advanced -> ADB Sideload -> Swipe
adb sideload <name-of.zip>.zip (ensure the .zip is in the same folder as your fastboot/adb) and then it'll send the zip over to the phone and flash.
I prefer the adb sideload method as it pretty much pushes the file over to the phone and then flashes it afterwards.
Click to expand...
Click to collapse
The whole point of adb sideload is that you're sideloading a flashable zip that is not on your phone but on your computer and you're pushing the file onto your phone which will followup with flashing the zip.
You need to be typing adb sideload on your computer with the proper environment for adb set up with the proper drivers installed if you haven't already.

Bootloader unlock

Not needed..............

@jmz will this work on OS 4.5.2

krazyace35 said:
@jmz will this work on OS 4.5.2
Click to expand...
Click to collapse
I don't see why it wouldn't as I am on 4.5.3 and it worked.

jmz said:
I don't see why it wouldn't as I am on 4.5.3 and it worked.
Click to expand...
Click to collapse
Cool thanks I'll give it a try and thanks for this unlock tutorial

jmz said:
You will need a linux box or python installed on windows. Find instructions on the web for that.
Step 1: Download attachment
Step 2: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/manfid
Step 3: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/serial
Now you should have 2 sets of numbers. first should be in the format of 0x0000XX where XX is numbers. And the other is 0xSSSSSSSS.
So now use the downloaded file and execute (obivously replacing the entries with what was returned above.
Code:
./cublock.py XX SSSSSSSS
This will tell you you have unlock.signed now. So move that to your fastboot/adb directory and then reboot to bootloader and issue this command
Code:
adb reboot-bootloader
fastboot -i 0x1949 flash unlock unlock.signed
Once done, get back to android and do the following:
Code:
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
Now go flash my TWRP build in OG dev
Original credit goes to @dpeddi & @vortox for the exploit. I did nothing to this code and it is all their work. So give them thanks
Click to expand...
Click to collapse
Sorry for the noob-ish question. How do you get adb to recognize the fire? When I type "adb devices" there are no devices present.

ryanyz10 said:
Sorry for the noob-ish question. How do you get adb to recognize the fire? When I type "adb devices" there are no devices present.
Click to expand...
Click to collapse
do steps 1 through 6 in this thread
http://forum.xda-developers.com/fire-hd/general/root-supersu-stable-appstore-custom-t3113311

Question
Sorry for another question. When I type ./cublock.py, I get ". is not recognized as an internal or external command".
Sorry again for being annoying lol

ryanyz10 said:
Sorry for another question. When I type ./cublock.py, I get ". is not recognized as an internal or external command".
Sorry again for being annoying lol
Click to expand...
Click to collapse
if on windows you need to get python installed

jmz said:
if on windows you need to get python installed
Click to expand...
Click to collapse
I've got python 3.4.2 installed. Which version would you recommend?
After some researching, people have said that python doesn't work very well on Windows 10, which is what I'm on right now.

jmz said:
You will need a linux box or python installed on windows. Find instructions on the web for that.
Step 1: Download attachment
Step 2: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/manfid
Step 3: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/serial
Now you should have 2 sets of numbers. first should be in the format of 0x0000XX where XX is numbers. And the other is 0xSSSSSSSS.
So now use the downloaded file and execute (obivously replacing the entries with what was returned above.
Code:
./cublock.py XX SSSSSSSS
This will tell you you have unlock.signed now. So move that to your fastboot/adb directory and then reboot to bootloader and issue this command
Code:
adb reboot-bootloader
fastboot -i 0x1949 flash unlock unlock.signed
Once done, get back to android and do the following:
Code:
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
Now go flash my TWRP build in OG dev
Original credit goes to @dpeddi & @vortox for the exploit. I did nothing to this code and it is all their work. So give them thanks
Click to expand...
Click to collapse
Hi jmz,
I have a question here- all that was in your ZIP file was the cublock.py file.
Are we supposed to use this with the rest of draxie's tools in the HDX thread? If so, I was able to get an 'unlock.img' file, but nothing called 'unlock.signed'
maybe you didn't upload all the attachments we needed?
either way, thanks soooo much for your work !

edouble312 said:
Hi jmz,
I have a question here- all that was in your ZIP file was the cublock.py file.
Are we supposed to use this with the rest of draxie's tools in the HDX thread? If so, I was able to get an 'unlock.img' file, but nothing called 'unlock.signed'
maybe you didn't upload all the attachments we needed?
either way, thanks soooo much for your work !
Click to expand...
Click to collapse
sorry, with that tool you only get the unlock.img . I need to correct the post

In my linux box 'cuber' module, required by cublock.py, is not installed; is this the correct source? https://github.com/benesch/cuber
One more question: I forgot to block OTA update so my HD6 updated to 4.5.4, loosing root permissions. What I should do? Need to wait KingRoot supports the new software version or can I proceed to unlock bootloader and install twrp? Or could install, if available, a 4.5.3 recovery through dd? Very thanks.

I sense many roms being ported very soon...

Sure hope so!

I used the tools (cuber) in this post:
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689

So i generated unlock.img, but i am still unable to enter fastboot mode,
i tried changing boot to 4002, i rooted and tried to execute fastboot file, nothing works tbh, how do you suppose i fix this?
thanks in advance

robert896 said:
So i generated unlock.img, but i am still unable to enter fastboot mode,
Click to expand...
Click to collapse
Need more info: Your computer OS, tablet device model (Settings>Device Options), Fire OS version (Device Options>System Updates). Tell exactly what happens when you run: adb reboot-bootloader.

DoLooper said:
Need more info: Your computer OS, tablet device model (Settings>Device Options), Fire OS version (Device Options>System Updates). Tell exactly what happens when you run: adb reboot-bootloader.
Click to expand...
Click to collapse
ok im on ubuntu 15.04 got full adb and fastboot (they work on other devices) --- fire os 4.4.3---device model, kfhd 3rd gen
i also have windows 7 x64 dual booted with full adb and fastboot set up also
when i do adb reboot-bootloader, it restarts but doesnt enter fastboot ,, it boots into normal mode

robert896 said:
device model, kfhd 3rd gen
Click to expand...
Click to collapse
These unlock instructions are for Fire HDs (4th gen). You need a fastboot cable for KFSOWI. Try G+ KFSOWI modding.

I am new to the tablet scene. This is my very first tablet. I would like to root the device and install custom recovery and hopefully custom Rom. Is this the first thing I do or should I start somewhere else?