Hey guys, I just got LG l9 from my friend but it is (I am afraid, not knowing much about mobiles) bricked.
When I turn it on it says:
-------------------------------------
Secure booting unsuccessful!
Cause:
-------------------------------------
and after that it turns off. If I charge it it turns on and shows battery charging. At combination of Volume+, power button it goes in Recovery mode.
It shows "This mode is for data backup service center. After removing and reattaching battery, press power key to reboot and keep using phone" and from there I can't do anything, just able to take out battery.
If I try combination of Volume-, power button it shows little android and loading bar, after few sec it restarts and shows booting unsuccessful.
I am not sure what he did with it, but pretty sure he rooted it. Is it possible to fix it, hope someone will provide me some help
Thanks !
It is possible to fix, you need to unbrick it. Find the stock rom for your device and find a good tutorial on how to flash em. Good luck!
Thanks for the reply ! I found everything I need, but I got problem - cant enter download mode. On combination of Volume+ and plugging cable I get S/W Upgrade, and on combination Volume+&- and plugging cable I get nothing. Any ideas how to get in that download mode? Thanks!
Infam12 said:
Thanks for the reply ! I found everything I need, but I got problem - cant enter download mode. On combination of Volume+ and plugging cable I get S/W Upgrade, and on combination Volume+&- and plugging cable I get nothing. Any ideas how to get in that download mode? Thanks!
Click to expand...
Click to collapse
www.hardreset.info/devices/lg/lg-p760-optimus-l9/emergency-mode
Try that, then in adb, type adb devices and see if your pops up, if not, try fastboot devices. If it popped up in adb, you can sideload the zip file, if on fastboot, you can flash it.
Try that, then in adb, type adb devices and see if your pops up, if not, try fastboot devices. If it popped up in adb, you can sideload the zip file, if on fastboot, you can flash it.
Click to expand...
Click to collapse
Thanks for your patience and answers! Problem is I cant reach emergency-mode. I always get S/W Update. Under adb devices I can see my phone in recovery mode (was thinking maybe emergency=recovery mode). I tried sideload, it starts loading but after some time I get error:closed. I tried doing adb usb before as well but gave no results.: . Any other ideas? Is there any way to "make" phone run ROM from SD card (in recovery mode can't navigate anywhere like I can on my other phone).
Again thanks for your help and time!
Infam12 said:
Thanks for your patience and answers! Problem is I cant reach emergency-mode. I always get S/W Update. Under adb devices I can see my phone in recovery mode (was thinking maybe emergency=recovery mode). I tried sideload, it starts loading but after some time I get error:closed. I tried doing adb usb before as well but gave no results.: . Any other ideas? Is there any way to "make" phone run ROM from SD card (in recovery mode can't navigate anywhere like I can on my other phone).
Again thanks for your help and time!
Click to expand...
Click to collapse
If it sees your phone as recovery, you can be rescued! Run adb shell and once the shell has popped up, type ls and if you see the phone structure of directories, you can exit the shell and push the file from your pc to your phone. But before you push, I want you to try to run adb reboot-bootloader and see if fastboot recognises it.
RAZERZDAHACKER said:
If it sees your phone as recovery, you can be rescued! Run adb shell and once the shell has popped up, type ls and if you see the phone structure of directories, you can exit the shell and push the file from your pc to your phone. But before you push, I want you to try to run adb reboot-bootloader and see if fastboot recognises it.
Click to expand...
Click to collapse
I think I am making some progress. First on adb reboot-bootloader my phone reboots into secure booting unsuccessful, same as before. On the adb shell/ls I get to see cache, charger, data, default.prop, dev, etc, system, temp and lots of other things. I guess that are directories we are looking for. But when I go adb push filename.zip /data/media I get failed to copy filename.zip: Permission denied. Guess nothing can work at first, sorry
https://forum.xda-developers.com/showthread.php?t=2216896 Have you tried this?
RAZERZDAHACKER said:
https://forum.xda-developers.com/showthread.php?t=2216896 Have you tried this?
Click to expand...
Click to collapse
This gets complicated, I found xloader and uboot, but problem occurs when I try to install fastboot drivers, says third party doesn't contain digital signature information?? I think I was close with shell from adb, just how to get privilege to push files? Tried so many methods.. Thanks again on help.
Related
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
anyone knows?
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
Yes, you can access ADB while in a bootloop.
Theonew said:
Yes, you can access ADB while in a bootloop.
Click to expand...
Click to collapse
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
runingwild said:
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
Click to expand...
Click to collapse
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
yes you can I have this before and it's working
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again
Click to expand...
Click to collapse
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
mustafah822000 said:
yes you can I have this before and it's working
Click to expand...
Click to collapse
that can be helpful for me. How did you do it?? was it in bootloop too? not rooted?
Theonew said:
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
Click to expand...
Click to collapse
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
Click to expand...
Click to collapse
Theonew said:
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
Click to expand...
Click to collapse
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
runingwild said:
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
Click to expand...
Click to collapse
Its a driver issue. Check device manager for your "unknown device," then associate adb drivers with it.
you can use adb once the kernel has loaded so root or any other factor shouldn't affect it
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
runingwild said:
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
Click to expand...
Click to collapse
if u are bale to get into fastboot flash a stock ruu and it should work fine
well, what if i cannot access recovery mode or fastboot menu as you have said so. my HTC desire 310 is having bootloop and cant enter recovery. HELP PLEASE!!
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
reaper90 said:
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
Click to expand...
Click to collapse
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
JustinBieber said:
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
Click to expand...
Click to collapse
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
reaper90 said:
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
JustinBieber said:
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
Click to expand...
Click to collapse
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
reaper90 said:
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
Click to expand...
Click to collapse
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
JustinBieber said:
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
Click to expand...
Click to collapse
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
reaper90 said:
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
Click to expand...
Click to collapse
After command prompt has successfully listed my device with its code, I typed in adb sideload (therom).zip and it says * cannot read 'sideload' * The tutorial that you posted doesnt have sideloading a rom
Edit: Okay, I installed SDK Manager did those things and this link really helped me on pushing files through adb. I will test to see if dirty flashing the rom will allow the phone to boot
Edit 2: Damn.. had to wipe everything and do a clean install. Never replace a bootanimation from another phone cause it ****s up your phone and time
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Addicted2xda said:
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Click to expand...
Click to collapse
Yep, I downloaded SDK manager and opened the folder in command prompt, that was the only way I could sideload any files into my phone. I sideloaded the rom, reset everything (including system) and fresh install of the rom. Idk what went wrong the only thing I changed was the boot animation zip, which is very peculiar
But I have to thank reaper90 for helping me tons though
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
VivaSativa said:
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Click to expand...
Click to collapse
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Danny Samuel said:
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Click to expand...
Click to collapse
well i tried that before and it still didnt want to work, like it was priorotizing the first one i put in there or something.. but now i came to a wall... since i waited so long to find a sulution i had the device completely empty and just in bootloader.. it seems i dont have the driver or such for it to charge.. so i plugged it into the wall for a while whilst in fastboot thinking it was charging which it was not..
Now it is completely dead i cannot charge it and my computor cant detect it anymore.. seems i found the meaning of a bricked device
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Esploded said:
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Click to expand...
Click to collapse
Do you have adb? If you do the command is adb reboot recovery. Need to know more it just cycles? If so then try to push both power button and and both volumes until it has lights flashing at the bottom and reboots dont let go until it reboots. Other then that I am not sure. I tried to boot to recovery the manual way and it doesnt work. Which is why i Always use that to reboot recovery. Wait, I figured it out. Hold down volume power dont let go until bootloader comes up then let go of both. use volume down and select recovery and bam!
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
jhr5474 said:
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
Click to expand...
Click to collapse
I'll give the fastboot utility a shot, hopefully it works. Thank you
Esploded said:
I'll give the fastboot utility a shot, hopefully it works. Thank you
Click to expand...
Click to collapse
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
jhr5474 said:
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
Click to expand...
Click to collapse
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Esploded said:
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Click to expand...
Click to collapse
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
jhr5474 said:
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
Click to expand...
Click to collapse
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Esploded said:
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Click to expand...
Click to collapse
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
sdamark said:
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
Click to expand...
Click to collapse
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Esploded said:
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Click to expand...
Click to collapse
No, If you have twrp use adb push and push a rom to your phone and then flash it and your fine.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
If you can get into your rom, go to settings..power and at the bottom disable fastboot
Esploded said:
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
Click to expand...
Click to collapse
1. Charge your phone (about 24 hours).
2. Let him rest (about 24 hours) without turning on.
3. Connect device to PC with original wire (Win7 preferred).
There is possibility that your BB will recognize phone.
Dear Community,
I got my Note 3 Pro Snapdragon Version today and I tried unlocking the bootloader, installing root and TWRP.
Unfortunately after I installed TWRP, WiFi didnt work anymore so I wanted to go back to where I was before.
i tried flashing the GlobalRom with the MiFlash Tool but somehow I'm now stuck with a bootloop.
The phone starts up and shows the MI Logo but doesnt go on. I tried booting TWRP temporarily via fastboot commands so that I can try to flash flashable zip files
but it doesnt let me execute "fastboot boot xyz.img" anymore because my device is locked.
I would really love to hear any solutions or ideas. I dont want any root or something anymore. If someone has an idea Im very happy!!!
thanks a lot in advance and tell me if you need any more infos
Paul/shisaya24
1. keep vol + and vol - pressed while connecting USB to enter adb mode
2. check if phone is connected with "adb devices" in command line, if phone shows up, enter "adb reboot edl"
3. now you can flash via MiFlash
Alex3oe said:
1. keep vol + and vol - pressed while connecting USB to enter adb mode
2. check if phone is connected with "adb devices" in command line, if phone shows up, enter "adb reboot edl"
3. now you can flash via MiFlash
Click to expand...
Click to collapse
First of all, HUGE thanks for your fast answer!
Unfortunately I couldnt get this to work. Since I am stuck at the Logog screen here is what I tried:
Pressing both volume buttons while Logo Screen and plugging USB.
Pressing both colume buttons while fastboot screen is up.
These two didnt enter adb mode, I guess because of the bootloop I'm in
I also tried antering recovery mode with volume up + power button. Pressing both volume buttons didnt help either but when I am in recovery like that it shows my device in adb as "sideload" device.
Maybe that helps ? Can you give further advice or am I doomed?
My idea would be: Is it possible to reflash the device completely only usinf fastboot? The only thing I seem to be able to enter is fastboot...
Is there a way from fastboot to "working phone" ?
or maybe through the "adb sideload" state?
thanks a lot in advance!
Paul
EDIT
tried installing via "adb sideload xyz.zip" command but after shortly showing a status bar on phone screen it aborted and said "Total xfer: 0.00x" on PC screen .
Also: I read "adb reboot edl" brings you to download mode so you can flash something. Tried it but the phone just rebooted the normal system, so it stuck on Logo again...
search miui forum for unbrick, there is 2 or 3 method without opening your device
exp: http://en.miui.com/forum.php?mod=viewthread&tid=257227
Unfortunately they all do not work because they always require either a phone in download mode, and i only get to fastboot and adb sideboard or they require flashing something via fastboot but I can't do that either because it says my device is locked if I try...
Any suggestions how to flash a ROM with fastboot only or with adb sideload?
Thanks a lot
Paul
shisaya24 said:
Unfortunately they all do not work because they always require either a phone in download mode, and i only get to fastboot and adb sideboard or they require flashing something via fastboot but I can't do that either because it says my device is locked if I try...
Any suggestions how to flash a ROM with fastboot only or with adb sideload?
Thanks a lot
Paul
Click to expand...
Click to collapse
I Had The Same Issue Brother ! There are only 2 Things which you can do now .
1. Test Point Method to enter EDL
2.Give it to Service Center . I Gave Mine to Service Center ,They Fixed it in 30 mins or less and it was free
Dharani_V said:
I Had The Same Issue Brother ! There are only 2 Things which you can do now .
1. Test Point Method to enter EDL
2.Give it to Service Center . I Gave Mine to Service Center ,They Fixed it in 30 mins or less and it was free
Click to expand...
Click to collapse
Can I do the test point thing myself or is it risky?
What kind of service center? A general mobile phone repair shop or a Xiaomi special one?
shisaya24 said:
First of all, HUGE thanks for your fast answer!
Unfortunately I couldnt get this to work. Since I am stuck at the Logog screen here is what I tried:
Pressing both volume buttons while Logo Screen and plugging USB.
Pressing both colume buttons while fastboot screen is up.
These two didnt enter adb mode, I guess because of the bootloop I'm in
I also tried antering recovery mode with volume up + power button. Pressing both volume buttons didnt help either but when I am in recovery like that it shows my device in adb as "sideload" device.
Maybe that helps ? Can you give further advice or am I doomed?
My idea would be: Is it possible to reflash the device completely only usinf fastboot? The only thing I seem to be able to enter is fastboot...
Is there a way from fastboot to "working phone" ?
or maybe through the "adb sideload" state?
thanks a lot in advance!
Paul
EDIT
tried installing via "adb sideload xyz.zip" command but after shortly showing a status bar on phone screen it aborted and said "Total xfer: 0.00x" on PC screen .
Also: I read "adb reboot edl" brings you to download mode so you can flash something. Tried it but the phone just rebooted the normal system, so it stuck on Logo again...
Click to expand...
Click to collapse
I've been facing the same (or a similar?) problem about a week ago but managed to get out. Knowing me for having a head like a sieve I made some notes, sadly quite rudimentary
Did you try to flash with MiFlash after "adb reboot edl"? If I remember rightly after "adb reboot edl" you got the logo like booting another way, but the light is blinking red. Then I could flash via MiFlash.
I'm quite sure that if you get a "reboot" after entering "adb reboot edl", your phone will be in edl mode.
I will try that this evening when I am at home again and report. Thanks
Alex3oe said:
I've been facing the same (or a similar?) problem about a week ago but managed to get out. Knowing me for having a head like a sieve I made some notes, sadly quite rudimentary
Did you try to flash with MiFlash after "adb reboot edl"? If I remember rightly after "adb reboot edl" you got the logo like booting another way, but the light is blinking red. Then I could flash via MiFlash.
I'm quite sure that if you get a "reboot" after entering "adb reboot edl", your phone will be in edl mode.
Click to expand...
Click to collapse
Unfortunately this doesnt work. Phone reboots and shows MI Logo but red light doesnt blink and MiFlash doesnt recognize any devices.
Do you have another idea? :/
How did you unlock the bootloader, via official permission or that unofficial hack?
Sent from my Moto G using Tapatalk
I didnt use the official way :/ Im so hoping my phone isnt broken. I wish i owuld have been more patient
shisaya24 said:
I didnt use the official way :/ Im so hoping my phone isnt broken. I wish i owuld have been more patient
Click to expand...
Click to collapse
Only options you have right now are:
1) using test points method which is a but cumbersome and voids warranty if you care about that.
2) go to a xiaomi service center of you have any nearby.
It is hard bricked.
So there is absolutely no option to unlock bootlader via adb sideload or fastboot ?
shisaya24 said:
So there is absolutely no option to unlock bootlader via adb sideload or fastboot ?
Click to expand...
Click to collapse
Apparently, no! Whenever using unofficial methods, read precautions carefully and you missed all as I can see. Wait if someone can help you out.
apply official unlock. then unlock your device from fastboot mode.
asaharaSK said:
apply official unlock. then unlock your device from fastboot mode.
Click to expand...
Click to collapse
That sounds nice and easy. I already applied for official unlock.
But: do you know if u can use the official unlock now? I can only access fastboot and adb sideload mode. Is it possible to activate official unlock from there? Or do I need a working ROM rather?
I would have thought that official unlock doesn't work from fastboot /adb sideload...
shisaya24 said:
That sounds nice and easy. I already applied for official unlock.
But: do you know if u can use the official unlock now? I can only access fastboot and adb sideload mode. Is it possible to activate official unlock from there? Or do I need a working ROM rather?
I would have thought that official unlock doesn't work from fastboot /adb sideload...
Click to expand...
Click to collapse
Does anyone know this?
I have the same problem. I made the same mistakes as shisaya24. I have followed every procedure for unbricking and nothing works. I even applied for an unlock code and got it from Xiomi. I used their mi-unlock app which requires fastboot (pwr/vol-) but it gets to 50% and bombs out. It states it can't verify the phone. Can anyone please help me??
smiley1960 said:
I have the same problem. I made the same mistakes as shisaya24. I have followed every procedure for unbricking and nothing works. I even applied for an unlock code and got it from Xiomi. I used their mi-unlock app which requires fastboot (pwr/vol-) but it gets to 50% and bombs out. It states it can't verify the phone. Can anyone please help me??
Click to expand...
Click to collapse
out of sheer desperation I tried MiPhone again and after a few tries, MiPhone started updating the OS. My phone now works again and I have an unlock code as well.
i was trying to root my phone tecno camon cx air and finally see link how to root my phone then i make every step in this site
and because i'm not pro with root my phone destroyed with last command was : adb reboot
and now my phone show black screen with Tecno and down there powered by android and it's not load the android it's just it's keep doing that but no load the android
i try to press power and volume up to enter recovery mode but nothing happen i let battery dead and try again and when i put the charger my phone auto opens and keep restarting again please i need help
Command
Code:
adb reboot
doesn't destroy anything, it simply re-boots phone, nothing else.
And this re-boot obviously worked well. To me it seems phone's boot-loader got currupted.
Anyway: check wether you can access the phone via ADB
Code:
adb devices
jwoegerbauer said:
Command
Code:
adb reboot
doesn't destroy anything, it simply re-boots phone, nothing else.
And this re-boot obviously worked well. To me it seems phone's boot-loader got currupted.
Anyway: check wether you can access the phone via ADB
Code:
adb devices
Click to expand...
Click to collapse
how i can do that while phone keep restarting
0bito said:
how i can do that while phone keep restarting
Click to expand...
Click to collapse
You need to boot your phone in download mode. Just google it, you just need to press some keys
together.