Develop Bugs

[SOLVED]USB BRICKED+SDCARDnot Recognize+Heavy Battery Drain

To all Who are experiencing the problem I faced...Illustrated HERE..
And this is What I've Triedhttp://forum.xda-developers.com/showpost.php?p=19562122&postcount=8 to solve until got a FIX
I am writing this because I am getting PMs for help..and For the future Problems..
A Big Thanks to ckpv5... He helped me through out the days...
The Phone must be S-OFF and must got ROOT access to use this
Here is the Solution .. ..
After this you will have SD-CARD RECOGNIZED+NO BATTERY DRAIN..EVEN BETTER BATTERY BACKUP See my screen Shots
STILL GOT PROBLEM UNSOLVED ..PM me I'll TRY TO SOLVE
SOLUTION
1. First of ALL..do install ADB in you PC and on your Device(If it is bricked.. don’t worry it has adb shel on this already) see help from here http://forum.xda-developers.com/showthread.php?t=690362
Note these commands carefully ..and save these as txt in PC for further help
adb devices
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot erase cache
2. Download these(http://www.multiupload.com/5ZAPJTFXMM) and put them into C drive after UNZIPING by 7ZIP...
3. Put a recovery.img named file of AMON RA recovery.. download from here(http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-desire-v2.0.0.img)
4. Reboot your phone in BOOTLOADER ...Power on by pressing FIRST BACK BUTTON and than POWER simultaneously..
5. Open Command Prompt in PC.. for Windows7 type cmd in search at START button... for XP type run at START search..
6. Go to the directory in cmd prompt....as...
“cd C:\android sdk\tools”
7. Type
“adb devices” Let it load
“adb shel” Let it load
“fastboot erase cache”
“fastboot reboot-bootloader”
“fastbooot oem enableqxdm 0”
“fastbooot oem eraseconfig”
“fastboot erase cache”
“fastboot reboot-bootloader”
NOTE: Do remember to do all above command together and by sequence only...
8. Now it is time to flash the recovery..
9. Rename the download recovery image as “recovery”
10. Put this img file in to “C\android sdk\tools” folder
11. Open command prompt again..
12. Type
“adb devices” Let it load
“adb shel” Let it load
“fastboot erase cache”
“fastboot reboot-bootloader”
“fastboot flash recovery recovery.img”
“fastboot erase cache”
“fastboot reboot-bootloader”
13. Now remove the SD card from the phone and connect it to PC via card reader or anything by which u can easily connect..
14. Put the ROM.zip in the SD card
15. Put the SD card back in the Phone..
16. PowerOn the phone in fastboot mode by pressing VOLUMEDOWN first and than POWER simultaneously..
17. Use volume keys to go up and down..and power to select
18. Go to recovey and press power button..
19. In recovery just go to the WIPE.. and do WIPE of cache..dalvik cache..boot..system...sd-ext...Battery Stats..
20. Now reboot recovery..
21. Now after coming back to recovery in Phone choose INSTALL ZIP FROM SD CARD..
22. Simply choose the ROM.zip file...
23. Let it Flash
24. Wait
25. And
26. ENJOY!!!!!
The PROBLEM IS NO MORE..
Your phone will RECOGNIZE the SD card..
The Battery Drain (Usually having 1% under a minute) Will be Gone
You can use FAstBoot Commander or Android Flasher also to Flash Recoveries or hboots and Bootloaders
SEE SCREENSHOTS HERE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hey, Think I have the battery drain problem with runnymede AIO Rom, was it flashing AMON RA recovery that solved it? or the whole process? I don't have an SD problem.

jacksonliam said:
Hey, Think I have the battery drain problem with runnymede AIO Rom, was it flashing AMON RA recovery that solved it? or the whole process? I don't have an SD problem.
Click to expand...
Click to collapse
for the battery Drain problem.. you can do following things..
1. Wipe Battery stats
2. Install snq kernel
3. If above two doesn't work than only... try the two "oem commands" as I writtten in the procedure..
Actually every time you flash a ROm or everytime deleting and using the phone.. a extra data related to everything as cache configuration is stored in the MEMORY which acually u can not see but it eats battery...
The oem commandsd erases that thing and after this..it is like a new memory having completely blank..
BUT AFTER DOING THIS YOU WILL NOT BE ABLE TO RECOVER ANY DATA ON PHONE MEMORY IF ACCIDENTLY DELETED..
you will need to flash a new Inatall of same ROM..or whichever you want...

YES! You saved my sanity AND my phone! many many thanks!

Matty Matt said:
YES! You saved my sanity AND my phone! many many thanks!
Click to expand...
Click to collapse
.. Happy to help

I am a bit lost...
ADB cannot be used when the phone is in bootloader. So after the instruction to put the phone in to bootloader the proceeding instructions which say:
type adb devices [enter]
type adb shel [enter]
won't achieve anything. In other words, adb devices (whilst the device is in bootloader) will not find any attached devices.
adb "shel" isn't a valid command. Do you mean adb "shell" ? If so, this too isn't going to work while the device is in bootloader, adb will simply reply with "error: device not found".
So I guess what I'm trying to ask is - what is the point of those typing those two commands? In this instance, they don't serve any purpose and can be omitted?

sachin.02 said:
The oem commandsd erases that thing and after this..it is like a new memory having completely blank..
BUT AFTER DOING THIS YOU WILL NOT BE ABLE TO RECOVER ANY DATA ON PHONE MEMORY IF ACCIDENTLY DELETED..
you will need to flash a new Inatall of same ROM..or whichever you want...
Click to expand...
Click to collapse
I just can't understand what do you mean....
How am i supposed to recover any accidently deleted files if i didn't run those commands??????

dlotters said:
I am a bit lost...
ADB cannot be used when the phone is in bootloader. So after the instruction to put the phone in to bootloader the proceeding instructions which say:
type adb devices [enter]
type adb shel [enter]
won't achieve anything. In other words, adb devices (whilst the device is in bootloader) will not find any attached devices.
adb "shel" isn't a valid command. Do you mean adb "shell" ? If so, this too isn't going to work while the device is in bootloader, adb will simply reply with "error: device not found".
So I guess what I'm trying to ask is - what is the point of those typing those two commands? In this instance, they don't serve any purpose and can be omitted?
Click to expand...
Click to collapse
everything is written clearly...
these two commands repairs the USB brick also improves battery life and gives exact information about battery uses.. you will see this after flashing a ROM..
adb shel is correct command..it open the list of commands and details of phone...
Tell me what you need.. than i may solve the problem..

spitjo said:
I just can't understand what do you mean....
How am i supposed to recover any accidently deleted files if i didn't run those commands??????
Click to expand...
Click to collapse
by saying not able to recover any data is just.. if you are using any recover data application from market to recover anything which have been lost by mistake.. than you won't be able to..
BTW this Problem rarely occurs...

I' ve done this as you said in your 1st post but still Display uses more than 60% of battery use (i set brightness to minimum, all is set up to minimum and power saving)
I'm running AIO 3.0.5. CM7r2 hboot, XD2SDX, desire is s-lcd version

kciko said:
I' ve done this as you said in your 1st post but still Display uses more than 60% of battery use (i set brightness to minimum, all is set up to minimum and power saving)
I'm running AIO 3.0.5. CM7r2 hboot, XD2SDX, desire is s-lcd version
Click to expand...
Click to collapse
Calibrate tour battery... It happens that the software doesn't shows exact informations...
The problem is also with guys at cynogen too...
It is normal...
The thing is..after doing this tutorial you must be getting 16 hours battery life as normal use....
Don't worry about display...
Sent from my HTC Runnymede using Tapatalk

is it just me? having problem make adb detect my phone.

napalm.potter said:
is it just me? having problem make adb detect my phone.
Click to expand...
Click to collapse
Have you Downloaded the Tools from the link I've provided

If you have 4ext recovery boot into it and go to tools - usb unbrick. It works for me fine.
Sent from my HTC Desire using XDA App

[Q] Stuck at stock bootloader

I am such a noob and suck at rooting.I got problem during rooting my kindle fire,here's the stories.I try to search all the way in the forum. But,all of it not working. Could you guys help me ?
1) follow root instruction and downloaded KFU
2) successfully installed superuser and go launcher
3) TWRP or CWR or FFF doesn't appear when i reboot back my device to flash custom rom.
4) I tried to run install_driver and run it again and select bootmode menu
5) I choose 3 for recovery.and its brick.luckily i could switch off my kindle.but when i wanna turned it on,its doesnt return to home menu.its stuck at the stock bootloader.
I'm hoping you guys could help me and suggest me the way how to solve it.
I also attach some screen shot of the kindle and my notebooks when i plugged in usb cable in.
Cheers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

it seems to be in fastboot mode - you have to fix your windows driver for fastboot mode, then you can continue with kfu.
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
detailed explanation here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

b63 said:
it seems to be in fastboot mode - you have to fix your windows driver for fastboot mode, then you can continue with kfu.
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
detailed explanation here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
thanks for the advice.I will try it after this and inform you back. Btw, do i need kindle usb cable? for fastboot, since i purchased used kindle so the seller didnt gimme those cable. im currently using sony micro usb cable.

no - every micro usb cable will work

b63 said:
no - every micro usb cable will work
Click to expand...
Click to collapse
i will try to read all of it, try to understand it.and get you know once i already figure it out okay?:cyclops:

i already update my driver.and why in KFU,my device is offline.

21th century apes said:
i already update my driver.and why in KFU,my device is offline.
Click to expand...
Click to collapse
your device seems to be in fastboot mode - you have selected the wrong driver.
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
if the device is in fastboot mode "adb status" is allways "offline".
if you have installed the right driver you can check manually
with "fastboot devices" and "fastboot getvar product".
if you get response to this commands you are good to go.

i finally able to install bootloader and twrp.i thought i never make a mistakes.but unfortunately,during time im backing up stock rom,(nandbackup).i check all the boxes (for the left side) and for right side nothing.its running,when completed.its show huge amount of data (around 780 mb).i really think dat tis is normal for backup.in twrp,and video by tom gt,time for backup for 10 minutes.but me,already 5 hour still stuck in twrp.cant go anywhere.

b63 said:
your device seems to be in fastboot mode - you have selected the wrong driver.
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
if the device is in fastboot mode "adb status" is allways "offline".
if you have installed the right driver you can check manually
with "fastboot devices" and "fastboot getvar product".
if you get response to this commands you are good to go.
Click to expand...
Click to collapse
bro i hope you can help me solve tiz things off.during backup nand.for the first time.its stuck and as i mention previously its stuck 5 hours but for almost 2 days.its still not finish.am i brick my fire?am i miss out something?later i'll attach picture for your preferences.i think when i already booted up kindle fire,its consider no such big issues.maybe for me that not familiar.

21th century apes said:
bro i hope you can help me solve tiz things off.during backup nand.for the first time.its stuck and as i mention previously its stuck 5 hours but for almost 2 days.its still not finish.am i brick my fire?am i miss out something?later i'll attach picture for your preferences.i think when i already booted up kindle fire,its consider no such big issues.maybe for me that not familiar.
Click to expand...
Click to collapse
if you managed to install bootloader and twrp then you are good to go.
you tried to make a backup of the stock firmware and now the twrp is stuck.
i don't know what options you checked, but this should be no problem.
just hold the power button for ~20sec till it turns off and try again.
check only options which exist on your device then the backup should be done in ~10min.

b63 said:
if you managed to install bootloader and twrp then you are good to go.
you tried to make a backup of the stock firmware and now the twrp is stuck.
i don't know what options you checked, but this should be no problem.
just hold the power button for ~20sec till it turns off and try again.
check only options which exist on your device then the backup should be done in ~10min.
Click to expand...
Click to collapse
Thank you dude.Finally im able to use custom rom.oh,yeah .Btw,i got one last question.Why i cant connect my kindle with computer.instead its show my kindle,its only charging.coz i need to backup all my stuff inside my kindle to computer.

21th century apes said:
Thank you dude.Finally im able to use custom rom.oh,yeah .Btw,i got one last question.Why i cant connect my kindle with computer.instead its show my kindle,its only charging.coz i need to backup all my stuff inside my kindle to computer.
Click to expand...
Click to collapse
that depends on the rom you used. some have a option to enable this function.
the best advise would be to search or ask in the section of the rom you used.
great that it's working now - much fun with your kf

hey dude.im already killed my kindle fire and now its dead.here the stories :
i try to backup all my stuff to my computer.as what you told me before,i try to follow.pick ROM that have usb debugging option for transfering data.okay done.but when i transferring my data from kindle to pc.(i dunno what happen) accidentally my kindle fire hang and i disconnect all the cable hoping that my kindle fire will be okay.but thats the end of my kindle fire.its failed to boot.just plain black screen.when i plugged in the cable.led light blinking.like normal.red and yellow.but there's nothing i can do.i open up device manager on my pc,instead of android phone appeared during time im connecting my phone with pc,its appeared usb mass storage (code 10).device cant start and load.hope you could guide me.anybody.
all guide will be kindly appreaciated.thanks.

[Q&A] [GUIDE][ROOT] Smartwatch 3 KNX01V

Q&A for [GUIDE][ROOT] Smartwatch 3 KNX01V
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][ROOT] Smartwatch 3 KNX01V. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

HELP!?
XorZone said:
You have been warned!
Links:
Sony PC Companion
SWR50-rootboot.img@ mega.nz, md5 summ: e2c34b07faa415a6cbb95943649c7eba
Step 1:
Code:
[URL="source.android.com/source/building-devices.html#unlocking-the-bootloader"]Unlocked bootloader[/URL]
1. Enable adb debug
2. adb reboot bootloader
3. fastboot oem unlock (twice if requested)
4. fastboot format cache
5. fastboot format userdata
6. fastboot getvar all (and verify that it is)
7. fastboot reboot
Step 2:
Code:
Updated to the latest KNX01V
[URL="http://www.sonymobile.com/us/tools/pc-companion/"]Install Sony PC Companion[/URL] and use Supports Zone -> Accessories software update -> Smartwatch 3
Step 3:
Code:
Have Flashboot (Sony s1 flash) drivers installed just in case (Install Sony PC Companion and do update as indicated in previous step)
Step 4:
Code:
[COLOR="red"]BOOT [/COLOR][COLOR="Red"](DO NOT EVER FLASH IT!!!)[/COLOR] rooting boot.img
1. Download rooting kernel image (SWR50-rootboot.img)
2. Reboot into bootloader (adb reboot bootloader)
3. fastboot boot SWR50-rootboot.img
4. Wait till device reboots or sits in black screen for a while (1 min+ then reboot it by holding power 10+sec)
Step 5:
Code:
Verify by:
1. adb shell
2. su
3. you should see [email protected]:/ #
Step 6:
Code:
1. Let me know!
2. Use it, dive into GPS investigation or customizations, etc.....
Special thanks:
1. Justin Case for LG G Watch rooting method using LGGW-rootboot.img
2. osm0sis for Android Image Kitchen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?

13noninja said:
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
Click to expand...
Click to collapse
Sounds like your'e missing the right drivers. I'm sorry I don't have a link right now but it should be somewhere on the OP.

13noninja said:
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
Click to expand...
Click to collapse
1. Download and install google usb driver: http://developer.android.com/sdk/win-usb.html
2. Check if you have adb driver in place: adb devices, if not - go into Device Manager and force missing driver to be "Android Composite ADB Interface".
To force it "Update Driver" -> "Browse My Computer" -> "Let me pick from a list ..." -> Select "Google, Inc." on left and "Android Composite ADB Interface" on the right.
Verify that you have adb access, by typing "adb devices", if needed confirm connection on the phone
3. Reboot to bootloader by typing "adb reboot bootloader", you should see "Running Fastboot" on watch screen.
4 Check "fastboot devices", you should see device id followed by fastboot word.
If not - go into Device Manager and force missing driver to be "Android Bootloader Interface" by followinf instructions for adb, but make sure to pick "Google, Inc." on left and "Android Bootloader Interface" on the right.
5. Verify fastboot working by executing fastboot devices.
6. Follow guide.

Got It
Thx XorZone and nobunnysapro, i found the missing drivers and got everything running smoothly.

I can not get my device to show up in adb devices and its driving me crazy. Tried windows 7/8/server 2012R2 ..lol
Now I have done my fair share of custom roms and bootloaders.
OG Droid
Nexus
Nexus 10
Asus Memo Pad (came from alarm company, and could only load one app...now its a full running tablet)
I am sure its a silly thing I have done or am missing...
Thoughts....ideas?..need more info?
Oh and ADB Debugging is on

I can't seem to get it working..
I have the drivers and ADB works fine, i can sideload stuff to watch and install apk and everything.
But when I write "adb reboot boatloader" it does just normal reboot. Can't get into fastboot mode.

Orvils said:
I can't seem to get it working..
I have the drivers and ADB works fine, i can sideload stuff to watch and install apk and everything.
But when I write "adb reboot boatloader" it does just normal reboot. Can't get into fastboot mode.
Click to expand...
Click to collapse
boatloader? I do not think sony included boat on board... JK
correct one is
Code:
adb reboot bo[B]o[/B]tloader

XorZone said:
boatloader? I do not think sony included boat on board... JK
correct one is
Code:
adb reboot bo[B]o[/B]tloader
Click to expand...
Click to collapse
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Sent from my SM-N910F using Tapatalk

Orvils said:
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
1. Are you doing it through USB connection and not over bluetooth?
2. What is your current build number/version in about menu?

Yes I'm doing everything with USB connection.
Build number is KNX01V
Sent from my SM-N910F using Tapatalk

Orvils said:
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Click to expand...
Click to collapse
Always check if adb in general works (may be driver probs in Win):
Code:
adb devices -l
(That's a lowercase L)

A guide for relocking the boot loader? I'm looking to go to lollipop for wear so I'd like to know how to go back to stock.

Fastboot OEM lock, and better reflash using Sony companion before.
I plan to try to get ota as is, then if it'll not work reflash using companion and then if it is still not upgrades I'll relock as last resort.

I have reinstalled Google USB drives over and over again manually and through SDK... When I try to manually point it to the right drivers I don't even get offered the right drivers.. I have google inc. Selected on the left but I dont see android composite or android bootloader interface...help would be much appreciated

Hello, any idea to make it work on lollipop? Thanks!

I have Sony Smartwatch 3 and want to install normal APK via Sideload and USB/PC (do not want to root my smartphone).
Is this possible and which SW i need to install on Windows PC?
Step by step guide (for noobs) would be great. Thanks
Gesendet von meinem SM-T310 mit Tapatalk

Huawei Watch Update 1.4 is here!

Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you are connected to your charging dock.
Make sure you are running the latest update LCB43B.
I did all this on Win 10.
1. Just be fully stock including recovery. Refer to Skin1980's guide here to return to stock if you used his previous kernel or did any other mods like TWRP or root. (http://forum.xda-developers.com/huawei-watch/general/guide-return-to-stock-huawei-watch-t3219596)
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339) (People have reported PDANET drivers are working if the naked drivers do not work for them and are somewhat easier to install.)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip and make sure its located inside the root directory of your adb installation.
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Don't forget to hit the thanks button! I appreciate it!

Thank you. Can you please create a step by step guide for idiots like me, who have never used adb etc..?

hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there

chachin said:
hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there
Click to expand...
Click to collapse
I updated OP check the steps again. adb commands won't work in bootloader. Once in recovery swipe down and select apply update from adb then issue the "adb sideload update.zip" command.

so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
Make sure the update file is inside your root adb directory on your hard drive.

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
It looks like your device is still not visible to adb. Make sure you don't have any other devices connected like a phone with debugging turned on also. And you do need to be in recovery with it awaiting the sideload update.zip command. You seemed to be in the correct place.

Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk

xceebeex said:
Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
YAY! Always the best way to go. Where are u located?

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
But... the phone must be connected on the pc? I can't detect the watch with adb devices..

I was wondering why I couldn't boot to the recovery directly so thanks a ton for the help! Also dayum, the speaker sure is quite loud for a smartwatch!
To the person above no, you do not need to have the phone to your pc connected for it to work.

got it installed like it so far, to me the speaker sounds alot better then the one in the gear s

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk

Tried installing the naked drivers in the link but that fails, any suggestions?

str8spir said:
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Very glad we could help! Just wanted everyone to be as happy as I was when I saw the file drop!

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
Thanks worked flawlessly...

ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
Let me test mine and see if it is visible while waiting on the adb sideload update.zip command

No luck for me installing these drivers

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
C:\ADB>adb devices
List of devices attached
MQB7N15914000616 sideload
This is what I see while in sideload mode inside recovery. Not sure why its not working for you.:crying:

How to root Your MICROMAX IN1B (64GB)

First of all, before i start, I'll make this clear, i have done this procedure and rooted my IN1B successfully BUT if anything goes wrong with your device,
I WILL NOT BE RESPONSIBLE FOR BRICKED DEVICES
PreRequisites (Stuff you will need)
So, Let's get into it.
Before Begining, Here are the things you'll need :-
1. A windows PC with all the necessary drivers.
2. ADB and fastboot which you can get from here.
3. A USB C cable, preferably the original one.
4. Make sure your Device is atleast 60% charged.
5. Backup all your data because the very first step will reset your phone.
NOTE- MICROMAX DOES NOT PROVIDE ANY USB DRIVERS. So i had trouble finding the Drivers too, so i recomend you use "Driver booster" it's free, you can get it from here. After installing the driver booster, let it scan and then update all the drivers related to "Android" and "ADB".
That's it, once you are done with all the above points we are good to start.
These are the PATCHED files you need to flash to root your device.
1. Get the files from Here
After you download the files, copy and paste the files in the folder where ADB & Fastboot is located, if you have not changed the Install location, it should be at this directory- C:\Program Files (x86)\Minimal ADB and Fastboot
After you paste all the 3 downloaded files in the ADB folder, the process will now start.
Unlocking the BootLoader
The first step is to unlock the boot loader.
1. Connect your device with a USB C cable.
2. Enable USB debugging from the developer options-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Now run ADB and run this command- adb devices As you run this, something like this should appear on your mobile-
4. Now allow it and Voila!, you are now connected!
5. Now find "OEM Unlocking" and enable it.
6. Now enter this command- adb reboot bootloader As you run this command your device will reboot and show a black screen with only "fastboot" written on it.
7. Now finally Enter this command- fastboot flashing unlock
8. Now it will ask you to confirm, if you change your mind and dont want to root now, press the "Volume-Down" Button or if you want to root, press the "Volume-Up" button.
NOTE- UNLOCK MAY VOID SOFTARE WARRANTY. FOR DETAILS, CHECK THIS (Read 6e)
9. Awesome! Now you have unlocked your boot loader!!
Flashing the Patched Files
Now remember you need the 3 files i linked above, once you get them, paste them in the ADB folder.
Make sure you DON't change the file names.
Let's Start!
1. Run this command- fastboot flash boot patched_boot.img
2. After that, Run this- fastboot --disable-verification flash vbmeta vbmeta.img
3 And he final command, run this- fastboot flash recovery recovery.img
After all these 3 complete succesfully, Just run- fastboot reboot This will start your device normally, go on and set up your device.
1.As you complete the setup, you should see the magisk app-
2. Now the magisk app will ask you to install the full version, click on confirm and it will install the magisk app, you will have to turn on the "Unknown sources" option.
3. Once it is installed, you can ENJOY YOUR ROOTED IN 1B!!
IF YOU NEED ANY HELP, FEEL FREE TO WRITE IT BELOW, OR DM ME ON TELEGRAM- Âkio or DISCORD- Âkio#7134

Akahat27 said:
First of all, before i start, I'll make this clear, i have done this procedure and rooted my IN1B successfully BUT if anything goes wrong with your device,
I WILL NOT BE RESPONSIBLE FOR BRICKED DEVICES
PreRequisites (Stuff you will need)
So, Let's get into it.
Before Begining, Here are the things you'll need :-
1. A windows PC with all the necessary drivers.
2. ADB and fastboot which you can get from here.
3. A USB C cable, preferably the original one.
4. Make sure your Device is atleast 60% charged.
5. Backup all your data because the very first step will reset your phone.
NOTE- MICROMAX DOES NOT PROVIDE ANY USB DRIVERS. So i had trouble finding the Drivers too, so i recomend you use "Driver booster" it's free, you can get it from here. After installing the driver booster, let it scan and then update all the drivers related to "Android" and "ADB".
That's it, once you are done with all the above points we are good to start.
These are the PATCHED files you need to flash to root your device.
1. Get the files from Here
After you download the files, copy and paste the files in the folder where ADB & Fastboot is located, if you have not changed the Install location, it should be at this directory- C:\Program Files (x86)\Minimal ADB and Fastboot
After you paste all the 3 downloaded files in the ADB folder, the process will now start.
Unlocking the BootLoader
The first step is to unlock the boot loader.
1. Connect your device with a USB C cable.
2. Enable USB debugging from the developer options-
View attachment 5326971
3. Now run ADB and run this command- adb devices As you run this, something like this should appear on your mobile-
View attachment 5326979
4. Now allow it and Voila!, you are now connected!
5. Now find "OEM Unlocking" and enable it.
View attachment 5326983
6. Now enter this command- adb reboot bootloader As you run this command your device will reboot and show a black screen with only "fastboot" written on it.
7. Now finally Enter this command- fastboot flashing unlock
8. Now it will ask you to confirm, if you change your mind and dont want to root now, press the "Volume-Down" Button or if you want to root, press the "Volume-Up" button.
NOTE- UNLOCK MAY VOID SOFTARE WARRANTY. FOR DETAILS, CHECK THIS (Read 6e)
9. Awesome! Now you have unlocked your boot loader!!
Flashing the Patched Files
Now remember you need the 3 files i linked above, once you get them, paste them in the ADB folder.
Make sure you DON't change the file names.
Let's Start!
1. Run this command- fastboot flash boot patched_boot.img
2. After that, Run this- fastboot --disable-verification flash vbmeta vbmeta.img
3 And he final command, run this- fastboot flash recovery recovery.img
After all these 3 complete succesfully, Just run- fastboot reboot This will start your device normally, go on and set up your device.
1.As you complete the setup, you should see the magisk app-
View attachment 5326989
2. Now the magisk app will ask you to install the full version, click on confirm and it will install the magisk app, you will have to turn on the "Unknown sources" option.
3. Once it is installed, you can ENJOY YOUR ROOTED IN 1B!!
IF YOU NEED ANY HELP, FEEL FREE TO WRITE IT BELOW, OR DM ME ON TELEGRAM- Âkio or DISCORD- Âkio#7134
Click to expand...
Click to collapse
ON which android version u have done this given me firmware name

pankspoo said:
ON which android version u have done this given me firmware name
Click to expand...
Click to collapse
I did on the android 10 which it initially came with..