Related
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
luminuss3 said:
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
Click to expand...
Click to collapse
Your boot image is missing...
When your phone boots in bootloadermode, it should (now, anyway) say: boot.img missing. Or something of that nature. Check this, flash it via fastboot, then everything should be back to normal...
EDIT:
It works with both: CDMA & GSM
luminuss3 said:
After attempting to install franco kernel, my nexus was stuck at the Google logo upon startup. After attempting to recover via clockwork recovery, I found it to be missing (temporary install perhaps?). Currently I have installed clockwork recovery via nexus toolkit. The problem I am now trying to address is that I have no way of putting .zip files on my phone. Some Google searches did not come up with anything quite like this. I am new to this, so any information is good information. Thanks in advance
Click to expand...
Click to collapse
do you know how to use fastboot and adb?
Excuse my lack of knowledge, but how exactly do I flash something over fastboot? Thanks in advance again.
Edit: And I do know how to use adb, however it does not connect. I do not know how to use fastboot
After some playing around with fastboot, I now have a basic understanding. However, I am not sure where I should be flashing that file you have linked.
Today, a friend suggested I try mounting via, and copying roms over that way. However, even with all the drivers installed on my computer, I get nothing.
If anyone has ANY insight on this problem, it would be be greatly appreciated. My new toy is a brick at the moment
Thanks in advance!
luminuss3 said:
Today, a friend suggested I try mounting via, and copying roms over that way. However, even with all the drivers installed on my computer, I get nothing.
If anyone has ANY insight on this problem, it would be be greatly appreciated. My new toy is a brick at the moment
Thanks in advance!
Click to expand...
Click to collapse
I'd seriously try to go back to stock first. I'm not a Windows user but if you have adb, fastboot, and your drivers setup, it should be easy. Mark is a great help in this thread and you can use his script I guess:
http://forum.xda-developers.com/showthread.php?t=1400871
You need to also realize that if you have wiped everything to install a new rom, you have nothing to boot to. Also there is install-recovery.sh file that keeps re-writing your recovery to stock erasing custom recovery (CWR) until you rename or erase that file. So going back to stock would be the safest and then you can try again.
You can use adb in recovery and fastboot in bootloader. If you have everything setup correctly (sdk, adb, fastboot, drivers for windows) either of these commands should recognize your phone:
In Bootloader (the first screen you see with big arrow on top):
Code:
fastboot devices
In recovery:
Code:
adb devices
If you don't have a recovery, then use the first one. If you see your phone's serial number like this
Code:
List of devices attached
HT12HS005115 device
you can now use it to flash things onto your phone. As I said I am not a windows user so I can't be specific, sorry. But adb and fastboot, once you are at their prompt, should work the same.
In general, when fastboot is recognizing your phone in the bootloader, you can use:
Code:
fastboot flash zip YOURFILENAME.zip
changing yourfilename of course. This zip file could be a stock imaqe or a custom recovery. Again, you need someone with windows to give you exact steps, this is just general stuff.
if your phone is yakju build then you can get the stock images from google.
download and unzip the files to your fastboot folder and use these commands, the file names in these commands are for the Android 4.0.1 (ITL41F) build so you will have to change the filenames if you use a different build.
Code:
fastboot devices (to make sure your phone is connect to fastboot)
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip
So I think I've gone and bricked my LG G3.
After the ROM I was using, cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd) from here, kept freezing 20 seconds after startup, I went to update to cm-13.0-20160325-NIGHTLY-d855 (CM13 March 25th). I booted into recovery (TWRP 2.8.7.0) as usual and went to flash both the ROM's .zip file and an Opengapps .zip file using TWRP's queue feature. However, it appeared to get stuck at a line (unfortunately I don't remember what it said exactly. Something involving patching system, I think), so I pulled the battery. I get the feeling this was a super not good thing to do, as my G3 now sits at the "LG - Life's Good" screen indefinitely. Holding Power+Vol.Down does not boot into Recovery, and neither does holding Vol.Up and plugging into my computer activate Download mode.
I tried to be as thorough as I could with exactly the steps I took, so I'm just hoping someone can give me a few pointers on what I can do.
As I type this I had the phone connected to my computer next to me, and I've suddenly heard the Windows "Device connected" sound and the phone is now showing this in the top right corner, in tiny font:
Code:
[784670] Fastboot mode started
[784820] -- reset --
[784820] -- portchange --
Edit: When this occurred, a device named "Android" appeared under the "Other devices" tab in Windows Device Manager. It's got a yellow warning sign next to the icon, and Properties says that the drivers for the device aren't installed.
Perhaps this is relevant to getting it working again.
First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...
bender_007 said:
First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...
Click to expand...
Click to collapse
Many thanks for the reply.
By ADB drivers for the LG G3, do you mean the Lg United Mobile Driver? I have version 3.13.2 of them, if that's what they are.
When I input the commands
Code:
adb devices
or
Code:
fastboot devices
nothing appears, so are there different drivers I should look for?
I'm not too sure how to "fix" partitions, either, but I'm guessing it requires ADB/fastboot.
The file aboot.img and laf.img, will I need to find somewhere to download them from?
Again, I appreciate the response.
In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)
bender_007 said:
In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)
Click to expand...
Click to collapse
I used PdaNet to install the LG drivers, and inputting the command "fastboot devices" now shows
Code:
? fastboot
Inputting "adb devices" does not show anything, however.
I then attempted to flash a recovery, TWRP version 2.8.7.0 with the command "fastboot flash recovery "recovery.img"". However, the phone's screen showed the following:
Code:
[998960] Error: Command never completed
[998960] Error: Auto CMD12 Error
[998960] Error: Command never completed with errors
[998960] Failed Writing block @ 1
How do I fix the partitions and find the files "aboot.img" and "laf.img"?
Thanks for your help so far, I'm glad that there is progress now.
it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor
bender_007 said:
it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor
Click to expand...
Click to collapse
I retried the command fastboot flash recovery recovery.img but it resulted in the same output as before.
I followed the exact instructions to enter TWRP but it just stays at the LG logo screen. I've held Power+Vol.Down for about a minute after quickly releasing it+pressing it again at the LG logo, but it just doesn't do anything.
I've found myself a Lollipop KDZ file. The CyanogenMod I was running, however, ran on Android 6.0 Marshmallow. Will I need a Marshmallow KDZ file instead?
check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)
bender_007 said:
check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)
Click to expand...
Click to collapse
I appreciate the offer to use Teamviewer to help me, but I think it would be best if you typed out some instructions in a reply to this thread so that others with the same issue can refer to here.
Solution
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)
bender_007 said:
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)
Click to expand...
Click to collapse
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.
HexManiacSpeck said:
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.
Click to expand...
Click to collapse
No problem, sometimes you have to trust people
There were people who asked for help, installed teamviewer and didn´t gave any control permissions (which is fine). But they were expecting someone is having soo much free time to explain things (which I would if I had time)
cheers, flad you fixed it
Fixed my G3 I was about to send to trash!
HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" fromhere, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Thanks a million for pointing to this recovery file!
I was also in a situation where all my attempts to flash a recovery were failing due to:
Failed Writing block @ 1
Click to expand...
Click to collapse
The rest of my phone was unusable (no working recovery, no download mode, just the LG logo or this fastboot mode)
I tried several TWRP recovery versions & flavors, but so far, I only successfully reboot in recovery using CyanogenMod recovery file (download.cyanogenmod.org/?device=d855). Though I was not able to do much afterwards apart some adb commands that were not working either.
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p20
dd: /dev/block/mmcblk0p20: write error: I/O error
This recovery img did the trick and I'm now back with a CyanogenMod ROM and a wiped phone.
I own h815 (LG G4), and i have successfully flashed (twrp-3.0.2-0-h815.img) as well as unlocked my bootloader. Now i need to access recovery mode, but my phone goes to safe mode if i try using VOLUME DOWN + POWER. So i used the following command in adb "adb reboot recovery" and it boots my phone, but all i see is laying android with open body and RED triangle and nothing happens.
So if anybody has an idea what could i do, let me know.
P.S. I did try other version TWRP, but the same occurs. And i am running Windows 10 64 bit pro, with all drivers, adb and sdk ready. Also sorry for the provided picture being blurry, it's been taken with old Samsung device.
Preview of the issue: (Just type imgur than .com than \ than fBlaeC1) [with out spaces and than]
Thank you all in advance!
I recall having similar issues. Copy the recovery image to your SD card, and keep a copy in the folder which contains the fastboot exe on your PC.
Open a command prompt and type fastboot boot recovery.img (where recovery.img is the name of the img file you're using). It should boot you in to twrp.
From there, you can flash the image you copied to the SD card using the install command.
Make sense?
Edit: it's explained here in a little more detail (towards the end of the first post): http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
El Presidente81 said:
I recall having similar issues. Copy the recovery image to your SD card, and keep a copy in the folder which contains the fastboot exe on your PC.
Open a command prompt and type fastboot boot recovery.img (where recovery.img is the name of the img file you're using). It should boot you in to twrp.
From there, you can flash the image you copied to the SD card using the install command.
Make sense?
Edit: it's explained here in a little more detail (towards the end of the first post): http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Click to expand...
Click to collapse
Yeah that's what i did, and i used different twrp witch worked. Sadly due to my inpatients i have managed to hard brick my phone. Because i took my battery out when the twrp was trying to root. Since there was no bar, i taught it was in boot loop. After that it won't boot up, it's stuck in "bootloader status: unlocked"...
Well tomorrow i will put it on octopus box, and flash new h185. I just hope, that i'll succeed in rooting this device.
Also the working method for twrp can be found on android root guides. They seem to recommend "Chainfire SuperSU for LG G4" as rooting method.
If you have rooted your device, let me know witch method have you used.
the lost account said:
Yeah that's what i did, and i used different twrp witch worked. Sadly due to my inpatients i have managed to hard brick my phone. Because i took my battery out when the twrp was trying to root. Since there was no bar, i taught it was in boot loop. After that it won't boot up, it's stuck in "bootloader status: unlocked"...
Well tomorrow i will put it on octopus box, and flash new h185. I just hope, that i'll succeed in rooting this device.
Also the working method for twrp can be found on android root guides. They seem to recommend "Chainfire SuperSU for LG G4" as rooting method.
If you have rooted your device, let me know witch method have you used.
Click to expand...
Click to collapse
Try to use lgup to flash the stock files. I think you can do that from any screen. After that do what the other dude said and if will work like a charm
Hi guys,
Yesterday i wanted do flash the official LineageOS.
I flashed the Gyver-kernel, LineageOS and latest gapps..
When i first startet my phone, it did boot up properly and it looked like i was ready to go through the startup configuration..
But then i saw it. I didn't have an installed keyboard. The only textinput method i got was speech input.
After that i formatet my device, so now i am stuck at the Xiaomi logo at startup.
The only connection i can make is from fastboot..
What can i do?
I can't figure out, how to use MiFlash-tool, or if it even works
Sorry for my basic english.
Please help
I don't have a lot of knowledge about custom kernels, but you probably try these steps:
https://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
After installing ADB download the official TWRP again (https://eu.dl.twrp.me/capricorn/) and copy it into the ADB folder. Do the same with the ROM (don't flash a kernel first, just to check if that one works, or see if you can find the original kernel and copy that one into the folder). Keep the USB-cable attached.
Afterwards, in that same folder, click shift + right mouse button and select to open a command window. Type "fastboot devices" to check if the drivers are working correctly.
Then:
"fastboot flash recovery recovery.img"
"fastboot boot recovery.img"
You should be booting to the recovery where you can fix things.
If the kernel doesn't respond for some reason, this topic might help a bit, although note that it's about a different phone. Fastboot commands are the same though.
https://forum.xda-developers.com/showthread.php?t=2131284
Did you btw format the system partition? That might give the problems you are facing.
So here I am again. If you won't be able( I honestly wish you to repair it, it's amazing phone) repair the phone, I maybe will want to buy it.
If you can go to fast boot. You have a good chance to unbrick it. Just extract the original rom to the state where you can see a lot of files. Put fastboot.exe(im copying all minimal adb content to it) and run flash-all-without-lock.bat. i don't remember the name exactly.
its easy bro ... just hold volume up and power go to twrp flash the rom ( or volume down go fast boot flash and install twrp )
Hello community, first of all I clarify that I am using the google translator.
As the title says, my poco f3 has a hard brick, I was trying to flash the miui global rom via fastboot(stock rom was global miui for turkey) but an error occurred in the process (the same as attached in the image), at that moment I got scared because the phone did not start the system.
The bootloader was obviously unlocked, I tried to recover with XiaoMitool but nothing, I couldn't flash super.img either in Xiaomiflash, then I decided to download its stock rom and redo the process but it failed.
Before all this I had tried to install TWRP or OrangeFox but none could be installed, I only got to the TWRP boot but the option to flash the current TWRP did not appear and it did not recognize the internal memory and the OTG with the zip. Right now it only shows the POCO logo and goes directly to fastboot mode.
I'd appreciate your help.
Edit: It does not have the recovery stock
edixon2021 said:
Hello community, first of all I clarify that I am using the google translator.
As the title says, my poco f3 has a hard brick, I was trying to flash the miui global rom via fastboot(stock rom was global miui for turkey) but an error occurred in the process (the same as attached in the image), at that moment I got scared because the phone did not start the system.
The bootloader was obviously unlocked, I tried to recover with XiaoMitool but nothing, I couldn't flash super.img either in Xiaomiflash, then I decided to download its stock rom and redo the process but it failed.
Before all this I had tried to install TWRP or OrangeFox but none could be installed, I only got to the TWRP boot but the option to flash the current TWRP did not appear and it did not recognize the internal memory and the OTG with the zip. Right now it only shows the POCO logo and goes directly to fastboot mode.
I'd appreciate your help.
Edit: It does not have the recovery stock
Click to expand...
Click to collapse
try booting twrp via fastboot and then format data.
Obviously you'll lose your data, but it might give you access to your phone back.
Good morning.
Try to enter with quiet fastboot mode, both in twrp and orange fox, it's the same process. Put the phone in fastboot mode and then open minimal adb.
1. Put the fastboot devices command, the serial number of your mobile should appear on the command screen.
2. Put the command fastboot boot orangefox.img or twrp.img, take a good look at the file you have downloaded, to make the boot easy, it has to be an .img image and not a zip file.
3. If you can get into both fastboot and orangefox, please format the data.
4. Try to flash the miui stock rom with the same process where the error appeared, remember that this rom (it worked for me) has to be the rom for the poco f3 fastboot, since there are 2 versions (I think I have seen this) one which is fastboot and another which is not.
LUCK!
ShAnGoS said:
Good morning.
Try to enter with quiet fastboot mode, both in twrp and orange fox, it's the same process. Put the phone in fastboot mode and then open minimal adb.
1. Put the fastboot devices command, the serial number of your mobile should appear on the command screen.
2. Put the command fastboot boot orangefox.img or twrp.img, take a good look at the file you have downloaded, to make the boot easy, it has to be an .img image and not a zip file.
3. If you can get into both fastboot and orangefox, please format the data.
4. Try to flash the miui stock rom with the same process where the error appeared, remember that this rom (it worked for me) has to be the rom for the poco f3 fastboot, since there are 2 versions (I think I have seen this) one which is fastboot and another which is not.
LUCK!
Click to expand...
Click to collapse
Hello, i had already tried to boot with twrp.img but without success, the good news is that I have already recovered it and the solution was as simple as taking the flash_all.bat from the rom and it could already be in any version of miui.
What I don't understand is why it hadn't worked with XiaoMitool and Xiaomiflash, and I still can't install TWRP because it doesn't recognize internal memory and OTG.
Anyway thanks for your help.
edixon2021 said:
Hello, i had already tried to boot with twrp.img but without success, the good news is that I have already recovered it and the solution was as simple as taking the flash_all.bat from the rom and it could already be in any version of miui.
What I don't understand is why it hadn't worked with XiaoMitool and Xiaomiflash, and I still can't install TWRP because it doesn't recognize internal memory and OTG.
Anyway thanks for your help.
Click to expand...
Click to collapse
Glad you got it sorted, When installing a MIUI stock rom remember to put the Firm wear folder on your C: Drive and remove any spaces from title,
As for TWRP & Orangefox recoverry, i installed these in fast boot mode and use "Temporary Recovery" by downloading RUN_TWRP-Orange Fox FIXED.bat /unzipping/ and running the "RUN_TWRP-Orange Fox FIXED.bat File, once in temporary OF Recovery you can choose to make OF Recovery permanent by installing current version of OF from within OF, Check my post on the EVO-X Thread post 20,
you will also find my post regarding OTG issues,
--------------------------------------------------------------------------
OTG is no longer Now working with Orangefox recovery.
To overcome the OTG showing 0MB or .., remove the OTG adaptor,
reboot into OF Recovery, re-connect your OTG adaptor and
tap ☰ in the bottom right of the main screen to open the MENU,
open Mount, tap USB-STORAGE (wait 5 seconds) the (USB-STORAGE background will turn black), shortly after the check box will enabled, many thanks to Rafsf for the Workaround.
I hope this helps a bit
johnr64 said:
Glad you got it sorted, When installing a MIUI stock rom remember to put the Firm wear folder on your C: Drive and remove any spaces from title,
As for TWRP & Orangefox recoverry, i installed these in fast boot mode and use "Temporary Recovery" by downloading RUN_TWRP-Orange Fox FIXED.bat /unzipping/ and running the "RUN_TWRP-Orange Fox FIXED.bat File, once in temporary OF Recovery you can choose to make OF Recovery permanent by installing current version of OF from within OF, Check my post on the EVO-X Thread post 20,
you will also find my post regarding OTG issues,
--------------------------------------------------------------------------
OTG is no longer Now working with Orangefox recovery.
To overcome the OTG showing 0MB or .., remove the OTG adaptor,
reboot into OF Recovery, re-connect your OTG adaptor and
tap ☰ in the bottom right of the main screen to open the MENU,
open Mount, tap USB-STORAGE (wait 5 seconds) the (USB-STORAGE background will turn black), shortly after the check box will enabled, many thanks to Rafsf for the Workaround.
I hope this helps a bit
Click to expand...
Click to collapse
Thank you very much friend you deserve heaven, finally I was able to install OF permanently.