Please guys, help me, i'm desperate, so i was trying to unlock the bootloader and found this thread about L90 D405 which is similar to our phone and i noticed that a recognized developer had created a modified aboot.bin and also a custom recovery.So i pushed the aboot.bin into mmcblk0p6.img and then i reboot the device....which killed my phone. Everytime i try to open it up it shows on the display the screen i was seeing before i rebooted the phone with ADB. I want to say that the USB somehow still recognize the phone because i hear the BEEP when i plug it into the phone.I can't enter neither stock recovery or download mode and also KDZ doesn't work it says that the USB is not recognized, so please help me out. :crying:
Here is the link : http://forum.xda-developers.com/showthread.php?t=2770938&page=31
Rephosix said:
Please guys, help me, i'm desperate, so i was trying to unlock the bootloader and found this thread about L90 D405 which is similar to our phone and i noticed that a recognized developer had created a modified aboot.bin and also a custom recovery.So i pushed the aboot.bin into mmcblk0p6.img and then i reboot the device....which killed my phone. Everytime i try to open it up it shows on the display the screen i was seeing before i rebooted the phone with ADB. I want to say that the USB somehow still recognize the phone because i hear the BEEP when i plug it into the phone.I can't enter neither stock recovery or download mode and also KDZ doesn't work it says that the USB is not recognized, so please help me out. :crying:
Here is the link : http://forum.xda-developers.com/showthread.php?t=2770938&page=31
Click to expand...
Click to collapse
WAIT THE PHONE ACTUALLY REBOOTS the problem is that i don't see the screen but i can tap on it and i hear that beep when i unlock the screen i just need aboot.bin because the adb after all still recognize the device, please someone can give me aboot.bin pleaseee!
Rephosix said:
WAIT THE PHONE ACTUALLY REBOOTS the problem is that i don't see the screen but i can tap on it and i hear that beep when i unlock the screen i just need aboot.bin because the adb after all still recognize the device, please someone can give me aboot.bin pleaseee!
Click to expand...
Click to collapse
Okay this is getting weirder, it booted....and guess what i see the screen rotated 180 but the buttons are working as they weren't been rotated, plus that the resolution is lower, i mean i can see the pixels for some reason.
Rephosix said:
Okay this is getting weirder, it booted....and guess what i see the screen rotated 180 but the buttons are working as they weren't been rotated, plus that the resolution is lower, i mean i can see the pixels for some reason.
Click to expand...
Click to collapse
Okay, i was so desperate that i didn't pay attention there was already a aboot.bin on the forums but the problem is that everytime i try:
-dd if=/sdcard/aboot.bin of=/dev/block/mmcblk0p6 through the ADB it says /sdcard/aboot.bin : cannot open file : aboot.bin doesn't exist.
Any solutions?
Hi Reposix,
if you would tell us the ADB commands you used before we might be able to help.
Did you put the about.bin on external SD? /storage/external_SD/about.bin
Did you push it with adb?
Did you adb shell?
Did you su?
Zaaap
Zaaap72 said:
Hi Reposix,
if you would tell us the ADB commands you used before we might be able to help.
Did you put the about.bin on external SD? /storage/external_SD/about.bin
Did you push it with adb?
Did you adb shell?
Did you su?
Zaaap
Click to expand...
Click to collapse
about.bin was put on the SD with the usb, i used this adb command to patch it : dd if=/sdcard/aboot.bin of=/dev/block/mmcblk0p6
The last two questions are invalid since without i wouldn't have been able to use the previous command.BTW, i fixed by replacing destroyed mmcblk0p6 with the stock one, i asked a guy on the forums to give me one, anyways i appreciate your conscientiousness :good: .
The reasons why I asked is:
dd ist not a an adb command, it is a shell command.
So you did 'adb shell', right?
I was not able to dd a block device without root rights.
So, I had to use the commend 'su'.
You put the about.img to SD, my question was real (external) SD or fake internal SD. This could be a reason why the file was not found.
So, happy that you got your phone fixed.:thumbup:
Sent from my Nexus 7 using XDA Free mobile app
Zaaap72 said:
The reasons why I asked is:
dd ist not a an adb command, it is a shell command.
So you did 'adb shell', right?
I was not able to dd a block device without root rights.
So, I had to use the commend 'su'.
You put the about.img to SD, my question was real (external) SD or fake internal SD. This could be a reason why the file was not found.
So, happy that you got your phone fixed.[emoji106]
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
/sdcard/ is a symlink to /storage/emulated/0/
So, he probably put it at the internal SD.
Sent from my D620R [Stock 4.4.2]
Zaaap72 said:
The reasons why I asked is:
dd ist not a an adb command, it is a shell command.
So you did 'adb shell', right?
I was not able to dd a block device without root rights.
So, I had to use the commend 'su'.
You put the about.img to SD, my question was real (external) SD or fake internal SD. This could be a reason why the file was not found.
So, happy that you got your phone fixed.:thumbup:
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Right..i forgot...i used adb shell just like this :
-adb shell
-su
-dd if=/sdcard/%imagename%.img of=/dev/block/mmcblk0p17
-reboot
And it's aboot.BIN not .IMG(i'm writing with caps so you can notice no offense )
And Vagelis is right, i put it on the internal SD not the external.
Thank you for clarifying this. :thumbup:
May help others with a similar problem.
Zaaap
can you help me too
Rephosix said:
Please guys, help me, i'm desperate, so i was trying to unlock the bootloader and found this thread about L90 D405 which is similar to our phone and i noticed that a recognized developer had created a modified aboot.bin and also a custom recovery.So i pushed the aboot.bin into mmcblk0p6.img and then i reboot the device....which killed my phone. Everytime i try to open it up it shows on the display the screen i was seeing before i rebooted the phone with ADB. I want to say that the USB somehow still recognize the phone because i hear the BEEP when i plug it into the phone.I can't enter neither stock recovery or download mode and also KDZ doesn't work it says that the USB is not recognized, so please help me out. :crying:
Here is the link : http://forum.xda-developers.com/showthread.php?t=2770938&page=31
Click to expand...
Click to collapse
HI my pone is bricked, it's dead
i was trying too root my phone and put twrp on it than it got me in recovery mode but i got frustrated because i didn't know how to select the options so i took my battery out with the hope that my phone would just reboot like normal but it didn"t. now i tried the buttons : home and volume down or volume up and connect with usb it just won't work, can you pleas help me... it does connect to my pc but nothing else
@Teamsvg
Don't you think one thread is enough for your issue?
Teamsvg said:
...it does connect to my pc but nothing else
Click to expand...
Click to collapse
And it connects in which mode? ADB? Recovery? Download? Media?
Have you tried the method I recommended in your thread?
http://forum.xda-developers.com/showthread.php?p=54325341
And if you don't answer questions no one can help!
Zaaap
Zaaap72 said:
@Teamsvg
Don't you think one thread is enough for your issue?
And it connects in which mode? ADB? Recovery? Download? Media?
Have you tried the method I recommended in your thread?
http://forum.xda-developers.com/showthread.php?p=54325341
And if you don't answer questions no one can help!
Zaaap
Click to expand...
Click to collapse
I've got the same problem ; phone is not response to ADB , Download, USB , nothing , when i connect to my pc , nothing happens, the only time i see anything is when i pull the battery and plug in USB the sign of no battery is visible
Any things i can try ?
Tried:
Pulling battery and restart
Starting with volume up + power
Starting LG soft and holding volume up while plugging in usb
Al these things diden't help , still screen stays black and no response from usb on pc...
HELP !!
:crying:
please help i have the same promblem.. i copied wrong aboot.img how did you fix it???
Rephosix said:
Right..i forgot...i used adb shell just like this :
-adb shell
-su
-dd if=/sdcard/%imagename%.img of=/dev/block/mmcblk0p17
-reboot
And it's aboot.BIN not .IMG(i'm writing with caps so you can notice no offense )
And Vagelis is right, i put it on the internal SD not the external.
Click to expand...
Click to collapse
please help i have the same problem.. i copied wrong aboot.img how did you fix it???
thanks in advance
please email to me your solution.. if you have time thanks.
[email protected]
tengskie said:
please help i have the same problem.. i copied wrong aboot.img how did you fix it???
thanks in advance
please email to me your solution.. if you have time thanks.
[email protected]
Click to expand...
Click to collapse
http://forum.xda-developers.com/g2-mini/help/bricked-phone-help-t3192435/page2?nocache=1
Related
Hi everyone,
Well I'm in that freak out stage.... where I am sure some of you have been.
Heres my issue...
I have a transformer prime that;
I just unrooted using Vipermod
Then did a factory reset
Now I am stuck in CWM recovery
I attempted to do a restore but after it gets done it brings me back into the recovery
I attempted to ADB but the command prompt opens and closes right away ( I assume from not being in USB debugging, which I cant get into without a rom)
I have no rom's currently downloaded into the prime as I just wiped everything in there as well.
Please i'll gladly pay $5 to anyone who can fix this without it breaking more (hard bricking if I havent already done so)
AHHH please guys help, I'm afraid it will run out of battery soon then I'll be royally screwedddd
anyone?
are you on windows 7?
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
birchnick10 said:
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
Click to expand...
Click to collapse
Turn on your tablet, let it boot into CWM.
Open cmd, cd to the directory with adb (for example cd C:\android), then copy this line of text below and right click > paste in the command prompt window.
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Click to expand...
Click to collapse
That should get you out of CWM into Android, assuming your restore works fine.
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
can i fastboot push a rom to the internal sd card or better yet can i install a rom from the external SD card via Clockwork mod recovery?
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
Navigate to %android sdk folder%\extras\google\usb_driver, open android_winusb.inf and copy the following in the sections
"Google.NTx86" and "Google.NTamd64"
; TF201
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D01&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D03&MI_02
;
; Fastboot for all projects
%SingleBootLoaderInterface% = USB_Install, USB\VID_0B05&PID_4DAF
Click to expand...
Click to collapse
Save the file and then try running the adb command I gave again.
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
birchnick10 said:
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
Click to expand...
Click to collapse
Try the instructions here. Try using this only as a last-ditch resort.
it wont shut off either... i tried both of the above mentions and cant get adb to recognize the prime
Attempted both and stuck at recovery loop without root. any more ideas? is it possible to flash rom from external sd? or is there a recovery I could fastboot rhat has this feature?
Attempted both and neither work. I need to somehow get usb debugging enabled while in clockwork mod. Or figure out a way to install a rom via external SD card while in CWM. Any more help is appreciated!
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
No adb debugging is needed in cwm. Even without any ROM installed. Recovery is different from Android.
Try to long press power (at least ten seconds) to hard reboot, and see if it changes something in device detection.
Did a hard reset and it boots me back into Recovery.
I was able to get a new rom into the internal SD via the emergency/backup.zip method but after it completes and I do a reboot it just boots right back into recovery again.
Any help please is apprecaited.
$5 bounty for a fix via paypal
Oh joy. This one is a spaghetti western in the making.
Okay. Question first : Does Windows 7 RECOGNISE the device in any way shape or form. To find out if this can be done, you need to power up the device and hold the power and volume down buttons, DO NOT press volume up when it suggests a kernel image. If you get three icons, hit vol down once and up once, then plug the USB cable into the PC and the tablet.
If it sees "Something", you've a chance. Download the naked universal USB driver from the dev forum, install it and have your device pick it up on the windows computer. I'm assuming from your comments that you've GOT a working fastboot and adb so I'm going to skip the instructions on that.
If you do have a something, and it's recognised, hit fastboot -i 0x0b05 reboot, if it reboots of it's own accord at this point, you can confirm you have working ADB and Fastboot access. From there you've a few choices. My personal preference would be to ADB push a rom down -after- doing a rebuild of the recovery image via fastboot (I really recommend TWRP for this bit).
http://forum.xda-developers.com/showthread.php?p=26093546#post26093546 - This post here which I wrote will explain how to flash TWRP from fastboot access, presuming you can get it. Once that step is done, wipe EVERYTHING from TWRP, and I mean the whole nine yards, including /system. Raze the memory down to only things it can't actually nuke. Once that's done, reboot to fastboot protocol, get a ROM pushed via ADB and install from inside TWRP.
That -should- get you back in business. Though judging by the tangle you're in, I make no promises.
ADB wont recognize the device. I have installed and uninstalled the drivers about 5 times.
It wont boot into fastboot - just goes directly into Clockwork Mod recovery. Even while holding power and volume down text comes up that says looking for asus recovery. then says clockwork recovery and boots directly into that.
The only way I can get anything into the internal SD card is with MasterZen88's Emergency script tool that puts any 1 file into the internal SD card as backup.zip
It was unrooted prior to all of this as well.
*cringe*
If ADB isn't working -at all- and it's not using the naked USB drivers to get you any kind of workable access. You're starting to smell very much like a hard brick scenario. I'm honestly not sure if there's a way out of that. A lot of the solutions for unbricking absolutely require that the device is able to talk to the outside world, if it's not and the ADB shell is essentially telling you it's talking to dead air, you're in a world of pain.
It's a long shot but it may be worth speaking to ASUS to see if they are willing to, for a fee, restore your tablet to factory settings. Though I can't imagine that will be cheap or simple. If you are able to get an RMA or a means of getting ASUS to poke it, make sure to take photos. Their techies appear to have the worst case of butterfingers in the world.
Go over Pandaball's suggestion, because that's really the last step I can think of before contacting ASUS
Flashed the Broccoli nightly rom I can no longer boot or get back into CWM. Computer cannot start the device. Can someone please help me? Tried all the tools and methods. It won't work unless I can get the device to start when connected to my computer.
RIght now when I press Vol Up and power, it brings me to cold boot linux. Cannot select anything or do anything. When connected to comp, it says device cannot start Code 10. Don't know what else to do. Help please
Looks like you're having an issue similar to mine. You'll need to setup ADB and push another rom to your Prime.
Can you get into recovery?
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
This thing is completely frozen no matter what. I can power off and on but that's about it. The device won't start according to windows. I'm praying I won't have to RMA or something.
You shouldn't be getting that screen pressing vol up and power.....that should be vol down and power, then doing nothing.
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
Thats pretty strange. You kinda screwed unless you can get into recovery or fastboot
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
Hi,
where it says press down to change mode you should be able to highlight the middle icon. If so that is fastboot and you have a chance.
I had a very bricked Prime and it only got that far. Then I followed this post.
You must download the fastboot and adb from the links given. I had some from elsewhere and they didn't work so well.
Also, I am not an Android hacker and I think that the dd command is somehow dangerous. At the end of the day, on my machine, I'm back with AndroWook and latest Motley kernel
Best of luck.
Tritium
Thanks let me try now. I hope it works. How did you get the computer to recognize the prime? Do I need to enable asus sync?
Tritium3.016 said:
Hi,
where it says press down to change mode you should be able to highlight the middle icon. If so that is fastboot and you have a chance.
I had a very bricked Prime and it only got that far. Then I followed this post.
You must download the fastboot and adb from the links given. I had some from elsewhere and they didn't work so well.
Also, I am not an Android hacker and I think that the dd command is somehow dangerous. At the end of the day, on my machine, I'm back with AndroWook and latest Motley kernel
Best of luck.
Tritium
Click to expand...
Click to collapse
It's alive!!! Thanks for the help. :good:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
klutch said:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
Click to expand...
Click to collapse
So when your device turns on its in a recovery loop right? You try to reboot and it goes right back to recovery?
It's ok don't worry, we will get it fixed. If that's what your problem is its referred to brick 1a in the unbrick your prime sticky thread.
We just need to setup ADB if you haven't already, and run one command. PM me if you need some help and ill try my best to get you through it or remotely connect to your computer to help you.
I highly suggest TWRP recovery after you get rebooted.
Sent from my ADR6425LVW using xda premium
klutch said:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
Click to expand...
Click to collapse
This is what I did while in CWM. Below is a copy of an insert from this thread.
http://forum.xda-developers.com/showthread.php?p=24923189#post24923189
Anyhow, so after you have that version installed:
1. Download "ROOTED 9.4.2.21 CWM compatible signed US version"
d - h . s t / r 4 4 -> WITH NO SPACE! (This is from the Primeval: The STOCK stock rom) Thread.
2. EXTRACT IT to the same directory where your ADB is! We only need the BLOBFILE from that zip folder!
3. Once you have the files extracted just run the following on your Command line:
adb push blobfile /sdcard/ ---> Its going to look like its not doing
nothing but dont worry its doing it in the background after 401 or some
seconds the command line will returned to you with a message like this:
1275kb, dadadada...
4. VERY IMPORTANT!: enter:
adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4
(Same as the previews step it will take forever but it will work dude!)
5. DONE! at least this is what worked for me man!
Im so happy now my Asus is freaking Brand NEw again! i was JUST about to through this garbage away but im so happy "dklue" gave me the BLOB concept idea! heheheh i guess i learned something new now..
the thing is the computer is not picking it up i tried diffrent drivers and still nothing i try doing ADB Shell device not found in order to do some commands i have to have it mount and thats the problem what ever i do wont move nothing so basicly is still on CWM only reboot and back again to CWM
Hold power and vol down to boot into CWM. Then you can do the blobfile push. It worked for me
My phone is from chinavasion it is galaxy i8550 WIN clone with lower specs it is mocor droid 2.0.5 with a fake jellybean speadtrum sc6820 it is rooted i connected the phone via adb and reboot into recovery i have stock recovery not cwm and i tried fixing it btw i meessed up my build.prop file but anyways i tried to fix it via adb and i got a permission error and i have a backup of my build.prop tho ...i just gave up and rebooted to recovery and wiped data/factory reset and ofcourse it didnt work but i lost my adb drivers i cant turn on usb debugging so i cant use adb and i dont know how to accesss recovery i keep ending up in the speadtrum factory test where u test phone hardware nothing else please help if u can altho i highly doubt it and also when i used adb to reboot in recovery and used a zip file it would say signature verification failed :crying::fingers-crossed: But i trust in xda please help even to give me the phone combination keys to recovery and that give me a zip that will be accepted PLEASE i only had the phone for a month
What exactly were you trying to fix in your stock recovery? Assuming I understand you correctly?
Sent from my K2_CL using Tapatalk
Fixing
Modding.MyMind said:
What exactly were you trying to fix in your stock recovery? Assuming I understand you correctly?
Sent from my K2_CL using Tapatalk[/QUOT
I just fugured out something the problem occured when i took a backup of my build.prop (original one) from my sd card and replaced it with the one in my system folder and forgot to add permissions to it and i restarted my phone and now its bootlooped. When it happened i tried to fix it before i factory reset my phone and lost access to recovery cuz i use to access it from adb i tried to flash a new one (build file) but i got signature verification failed so i just factory reset and lost my adb drivers so now i cant connect it to my computer to use adb commands to reboot into recovery and idk my combination for recovery it is speadtrum sc6820 .....ps. my phone is rooted and has mocor droid 2.3.5 with 4.2.2 jellybean so u know its a fake jellybean cuz its a cloned phone and i have no cwm :crying:
Click to expand...
Click to collapse
@BenDroid1
You can write the custom recovery to your recovery partition using dd in an android terminal emulator from the play store. You would need to know which partition holds your recovery.
For MY device (your partition is different) it would be as followed in the terminal emulator:
Code:
su
Code:
dd if=/sdcard/customrecovery.img of=/dev/block/mmcblk0p21
/dev/block/mmcblk0p20 is the partition that holds my recovery on my device - yours will be different!
You can also use this method for the boot.img towards the boot partition as well as data to data partition, and so forth.
If you have CWM and you were smart enough to create a backup of your device, then I would write the custom recovery to your recovery partition, boot in to CWM, and restore your device with your backup. Then, reboot, plug device in to your computer, allow the computer to reinstall the drivers and hopefully at this point you should be able to establish connection with adb/fastboot again.
Sent from my K2_CL using Tapatalk
Example 1
Sent from my K2_CL using Tapatalk
Example 2
Sent from my K2_CL using Tapatalk
Cant do that
How do uexpect me to do all of that when everytime i boot my phone the its stuck on the logo and i Dont have cwm ...my phone is bootlooped
BenDroid1 said:
Modding.MyMind said:
What exactly were you trying to fix in your stock recovery? Assuming I understand you correctly?
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
When it happened i tried to fix it before i factory reset my phone and lost access to recovery cuz i use to access it from adb i tried to flash a new one (build file) but i got signature verification failed so i just factory reset and lost my adb drivers so now i cant connect it to my computer to use adb commands to reboot into recovery and idk my combination for recovery it is speadtrum sc6820 .....
Click to expand...
Click to collapse
Because right here according to your quote you mentioned that you resetted your device, lost connection to your adb. Only time you can use ADB is when your phone is running. Only way you can confirm if you lost connection with ADB is if your phone is up and running, you open up command window on pc, then run 'adb devices' and if nothing returns then you have no connection. Otherwise, there is no way to confirm if you lost connection to it. So by your quote above, you made it sound like you got around your bootloop problem but could not connect with using ADB and no longer had CWM on your device.
Try to be more clear next time lol.
Have you tried using fastboot instead of ADB?
Sent from my K2_CL using Tapatalk
Modding.MyMind said:
Because right here according to your quote you mentioned that you resetted your device, lost connection to your adb. Only time you can use ADB is when your phone is running. Only way you can confirm if you lost connection with ADB is if your phone is up and running, you open up command window on pc, then run 'adb devices' and if nothing returns then you have no connection. Otherwise, there is no way to confirm if you lost connection to it. So by your quote above, you made it sound like you got around your bootloop problem but could not connect with using ADB and no longer had CWM on your device.
Try to be more clear next time lol.
Have you tried using fastboot instead of ADB?
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
no i havent and sorrry i ...i will be clearer when i press power plus volme up i get speadtrum factory test where u test phone hardware but no android recovery
Your phone has a bootloader. You need to access your bootloader, select fastboot, plug your device in your pc, open up command window, then type 'fastboot devices'.
If you get your device serial number returned back to you then you have connection. If it returns blank, then you do not have connection which at this point I will not be able to help you.
Sent from my K2_CL using Tapatalk
Modding.MyMind said:
Your phone has a bootloader. You need to access your bootloader, select fastboot, plug your device in your pc, open up command window, then type 'fastboot devices'.
If you get your device serial number returned back to you then you have connection. If it returns blank, then you do not have connection which at this point I will not be able to help you.
Sent from my K2_CL using Tapatalk
Click to expand...
Click to collapse
unfortunately looks like u cant help me cuz neither that wont showup
BenDroid1 said:
unfortunately looks like u cant help me cuz neither that wont showup
Click to expand...
Click to collapse
I'm sorry bro. Maybe someone else on here will pickup where I left off. Good luck friend.
Sent from my K2_CL using Tapatalk
Hello,
today i tried to root my phone who runs on kitkat 44.2 and i v'e made a big mistake
i wanted to make my phone look like the g3
now its rooted but while it got in recovery i didnt know how to select the options so what i did was
i took my battery out and now i tried to get it on again and it won't
it doensn't want to get in recovery nothing
when i connect it with my phone it shows that its connected
i don't know what to do can someone help me pleasss i want it back like the beginning without the root pleas (((((
Sorry @Teamsvg,
but with this description no one can help you.
Please explain what you did.
How did you root?
What did you do to make it G3 like?
Did you flash anything?
I can not believe it bricked because of pulling the battery while in recovery, because I did the same when my phone was all stock and nothing wrong happened.
You may try: http://forum.xda-developers.com/showthread.php?p=54325341
Regards,
Zaaap
hi
Zaaap72 said:
Sorry @Teamsvg,
but with this description no one can help you.
Please explain what you did.
How did you root?
What did you do to make it G3 like?
Did you flash anything?
I can not believe it bricked because of pulling the battery while in recovery, because I did the same when my phone was all stock and nothing wrong happened.
You may try: http://forum.xda-developers.com/showthread.php?p=54325341
Regards,
Zaaap
Click to expand...
Click to collapse
hi, thnks for replying
this is what i tried
https://www.youtube.com/watch?v=KINp9v_GN3o
i didn't enable usb debugging ...
zaap
Zaaap72 said:
Sorry @Teamsvg,
but with this description no one can help you.
Please explain what you did.
How did you root?
What did you do to make it G3 like?
Did you flash anything?
I can not believe it bricked because of pulling the battery while in recovery, because I did the same when my phone was all stock and nothing wrong happened.
You may try: http://forum.xda-developers.com/showthread.php?p=54325341
Regards,
Zaaap
Click to expand...
Click to collapse
My phone is like this: you the screen is black, i forgot to enable usb debugging because i tried to root it in my phone so i ddin't need my computer, i can't get in download mode or recovery nothing ! i tried the buttns( and no my buttons works fine) how can i fix this? the link you've send me ask me to put my phone in download mode : "if your device is bricked and can't boot you'll have to enter the Download Mode, to do that just keep holding the Vol. Up button while inserting the USB cable in the phone( The USB cable must be already plugged into the PC while doing that), and you keep it until you go into the Download Mode."
but it can't ...
Teamsvg said:
My phone is like this: you the screen is black, i forgot to enable usb debugging because i tried to root it in my phone so i ddin't need my computer, i can't get in download mode or recovery nothing ! i tried the buttns( and no my buttons works fine) how can i fix this? the link you've send me ask me to put my phone in download mode : "if your device is bricked and can't boot you'll have to enter the Download Mode, to do that just keep holding the Vol. Up button while inserting the USB cable in the phone( The USB cable must be already plugged into the PC while doing that), and you keep it until you go into the Download Mode."
but it can't ...
Click to expand...
Click to collapse
autoirec is onyl for g2.. not mini. becouse we have locked bootloaders custom recoverys doesnt work. something similiar happened to my phone. i can tell you by confedens that first of all it doesnt sound that you are familiar with custom recoverys and stuff and that you have hard bricked your phone. i had to send mine in after 2 days of trying to make it start again. it is broken. and if you take it to service i wouldnt tell them what you did or that you rooted it.
Try this. If you phone is detected under sdb or sdc you have a chance to unbrick your phone.
I attached the files needed to unbrick G2 mini:
sbl1.img
aboot.img
rpm.img
tz.img
recovery.img - download from here.
Be very careful. The order of partitions for our phone is different from the LG G2. So then you use "gdisk -l /dev/sdb" command, find the partitions numbers of each file attached, and use that number in dd command.
I do not know why on tutorial for G2 there is a warning not to flash original recovery.img on recovery partition. So my advice is to flash all partition except recovery.img and see if your phone enter download mode. If not, flash recovery.img, you have nothing to lose.
If the phone enter download mode flash kdz.
powermetza said:
Try this. If you phone is detected under sdb or sdc you have a chance to unbrick your phone.
I attached the files needed to unbrick G2 mini:
sbl1.img
aboot.img
rpm.img
tz.img
recovery.img - download from here.
Be very careful. The order of partitions for our phone is different from the LG G2. So then you use "gdisk -l /dev/sdb" command, find the partitions numbers of each file attached, and use that number in dd command.
I do not know why on tutorial for G2 there is a warning not to flash original recovery.img on recovery partition. So my advice is to flash all partition except recovery.img and see if your phone enter download mode. If not, flash recovery.img, you have nothing to lose.
If the phone enter download mode flash kdz.
Click to expand...
Click to collapse
Can i use this files on G2 Mini D618?
Thanks!
No you can´t.
Sent from my LG-D620 using XDA Free mobile app
So I recently pulled my G Watch back out and installed the most recent OTA 6.0.1, installed TWRP, the custom kernel, and rooted it. Obviously all of that required ADB to function correctly. It did perfectly. I installed ADB using the 15 Second ADB Installer, and used WinDroid Toolkit to flash TWRP and get into recovery and do the rest, that by default installed the ClockworkMod ADB drivers, all of this on my Windows 10 PC.
Those drivers worked perfectly. Until today.
I did a fresh install of CM13 on my Nexus 5 phone, which my watch was paired to at the time. I wiped everything and started over, so I then went into my watches settings and did the Factory Reset so I could start fresh and resync up with my new rom install on my phone.
But when I try to connect via ADB or even try to list the devices it always states "Unauthorized"...
For whatever reason, no matter what I try it wont bring up the prompt on my phone to authorize this computer.
I revoked Debug permissions on both my watch and my phone, tried different usb ports, turned off and on debugging in all its forms on both my watch and phone, plus restarted all my devices and my PC. I have tried google's adb drivers as well.
Not sure what else there is to possibly try, seems I have covered all my bases here. Just doesn't make sense that it worked and now all the sudden it doesn't...
Glad I'm not the only one having this problem! I've tried same exact methods you mentioned with no luck. Hopefully someone knows what's going on here and provide a solution
Maybe deleting the keys in the computer will fix it. If it works with another computer, then it's the solution. On Mac, they are stored in a folder called .android in the home folder, if I recall correctly. Anyway it should be easy to find online how to delete the keys in the OS you're using.
What I did was first authorise my phone to my pc's adb then I copied adb_keys from /data/misc/adb/ on my phone to my pc. I then copied that while in TWRP on my LG G watch to the same directory /data/misc/adb/ and rebooted to system and voila adb access restored!
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
xymic said:
Thanks for your suggestions guys, but I officially give up figuring this out. Tried other computers and it still says "unauthorized." Tried both Windows 10 and Ubuntu and still the same error. Some thing's definitely happened since Wear 6.0 update or maybe invisible kernel for 6.0?
@Xmaster24 I would try your TWRP way, but I never installed it as I didn't see the need for it. I don't think there's a way to install it now without ADB, is there?
Click to expand...
Click to collapse
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Xmaster24 said:
adb is absolutely not required. seeing as you are running 6.0.1 get the custom TWRP from my root guide here and follow the instructions on flashing the recovery. Seeing as you don't have adb you will just have to power off your watch and boot it up and swipe top left to bottom right as soon as you see something
Click to expand...
Click to collapse
Aaaaaand we're back, Houston! Thanks a lot man. Works great now.
Hello
I have the same problem as author of this thread. How can I get authorize adb? I need it to push some files to internal memory.
I suffer the same problem.
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
koszanty said:
Ok, I found solove for this problem. Just what you need is back to stock for example by this method: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863 or manually("fastboot flash" command): http://forum.xda-developers.com/g-watch/development/how-to-to-stock-rooted-6-0-t3339875 If you will have bootloop, you need to factory reset in twrp and reboot. To boot into twrp when you have bootloop you must enter to bootloader mode and write in cmd "fastboot boot YourTwrpName.img" command. I used twrp from this topic: http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512 After all you can update your watch to actual android wear version and again root/ change kernel.
Sorry for my bad english. I am not native speaker.
Click to expand...
Click to collapse
Sorry, but, with ADB in "unauthorized" state it can't be done.
Guys, read Xmaster24's posts in first page. That's how I fixed it.
turbomann said:
Sorry, but, with ADB in "unauthorized" state it can't be done.
Click to expand...
Click to collapse
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
xymic said:
Guys, read Xmaster24's posts in first page. That's how I fixed it.
Click to expand...
Click to collapse
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
koszanty said:
Why? Fastboot is diffrent thing than adb and it should work without 'adb authorization'. I used this method and it worked for me.
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
koszanty said:
If you don't have copy of adb keys on watch sdcard, probably you cant use his fix(or am I wrong?). By the way, how can I mange files in TWRP mode without working adb? In TWRP is special option/ command for mange files by PC or something like that? If I connect watch to PC I can't see it as mass storage.
Click to expand...
Click to collapse
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
xymic said:
You only need to have adb_keys file on the phone not the watch. In my case, I was able to use adb perfectly fine while I was in TWRP. Basically here's what I did:
1. Copy adb_keys file from your phone to computer. It is located in /data/misc/adb. If you can't see the file, you probably have to authorize your phone first with your computer.
2. Flash TWRP recovery from XMaster24's link using fastboot on your watch.
3. Boot into recovery. You don't need go into any options. While on the recovery homescreen, Just use this command to transfer adb_keys file into your watch:
Code:
adb push adb_keys /data/misc/adb
You can check using "Files" option in recovery to see if the file is transferred into the watch.
4. Reboot your watch and you should be able to access adb now.
You can do it your way as well, but using xmaster24's method saves time, I think
Click to expand...
Click to collapse
In my case adb doesn't worked at all
turbomann said:
You had flash 5.1.1 and then upgrade to 6.0.1? Are there bootloader compatible?
Click to expand...
Click to collapse
It's compatibile but can occur bootloop. If you will have bootloop, you must do that what I write some posts earlier.
I'm realised that my phone with MM do the same bug, unauthorized, I look for adb_keys file but folder ADB is empty, then only remains flash and update on the watch.