Database Users

Before I scrap my phone...

Hi All,
I just bought a new Hero two days ago. Since then I performed the following steps:
1.) downloaded the kernel source from HTC
2.) Compiled a kernel.
3.) As root:
a.) adb push newBoot.img /sdcard
b.) # cat /dev/zero > /dev/mtd/mtd2
c.) #flash_image boot /sdcard/newBoot.img
I did not install a recovery image unfortunately.
So.. after doing those steps the phone reboots, and displays
"HTC". It doesn't progress past there.
things i've tried.
1.) Installed a known .img that works. Renamed Recovery-RA-1.5.2.img to /sdcard/newBoot.img
2.) Copied other images that might work to /sdcard/newBoot.img
3.) renamed an image to HERC[DIAG|IMG].zip
Any other ideas I can try? I can boot to fastboot screen. Just not sure what else to do before I scrap it.
Any suggestions welcome.

how long did you wait at the HTC screen? it can take up to 10 minutes after the first boot.

hmm.. I didn't wait more than 5 minutes... I'll give that a try and see what happens. Hopefully that's all there is to it....

or you can just download a stock RUU and flash that.. Will atleast get you back to stock.

OK I tried that.. but since I can't boot into linux, I cannot get any adb commands to respond.
Between the "htc" screen that goes nowhere and the
the fastboot screen, I'm not sure how to install it.
I keep getting a USB 170 error.
still waiting at the HTC screen.

Sitting at the "HTC" screen for over 20 minutes now.. So I'm assuming that it's not going to boot. I'll let it go for a few more minutes.
Is there a way to install the RUU image from the fastboot screen?

fred43 said:
Sitting at the "HTC" screen for over 20 minutes now.. So I'm assuming that it's not going to boot. I'll let it go for a few more minutes.
Is there a way to install the RUU image from the fastboot screen?
Click to expand...
Click to collapse
The phone just needs to be on and connected to the pc when you run the RUU.

I'm assuming by "on and connected" that adb commands need to work?
Unfortunately my phone has 2 states. fastboot, and "HTC" screen that I mentioned above. I am unable to run any adb commands in HTC screen mode ( NO USB device is detected.)
The only way I can detect a USB device is when the phone is in fastboot mode.

fred43 said:
I'm assuming by "on and connected" that adb commands need to work?
Unfortunately my phone has 2 states. fastboot, and "HTC" screen that I mentioned above. I am unable to run any adb commands in HTC screen mode ( NO USB device is detected.)
The only way I can detect a USB device is when the phone is in fastboot mode.
Click to expand...
Click to collapse
If you can get in to fastboot then you should be able to run RUU while booted up in to fastboot. If not then you should be able to flash either a boot.img or RA's recovery img while in fast boot. At that point you should be able to boot the phone or boot in to a recovery image and flash a rom.
Option 1) Copy Recovery-RA-1.5.2.img to your sdcard and do: fastboot boot /sdcard/Recovery-RA-1.5.2.img
Option 2) Download fresh rom (or any rom) and then extract the boot.img from the zip and copy it to your sdcard. And then fastboot boot /sdcard/boot.img
Option 3) You can TRY actually flashing an img through fastboot but I'm pretty sure it's disabled on our phones. fastboot flash recovery /sdcard/Recovery-RA-1.5.2.img
FYI - The kernel source available from HTC is for the GSM Hero, not CDMA. That's why you are having problems.
You can PM me if you have questions.

flipzmode said:
Option 1) Copy Recovery-RA-1.5.2.img to your sdcard and do: fastboot boot /sdcard/Recovery-RA-1.5.2.img
Click to expand...
Click to collapse
Ok this option looks promising. The problem I have is :
"cannot load '/sdcard/boot.img'"
running the command:
"fastboot boot /sdcard/boot.img" ( AS root on my linux machine )
Note: I can see the usb device with fastboot devices
I think this error is happening from the linux machine. I tried this command as a non-root user and got the same response.
flipzmode said:
FYI - The kernel source available from HTC is for the GSM Hero, not CDMA. That's why you are having problems.
Click to expand...
Click to collapse
Ah.. That is why. My original goal was to create a kernel module for the phone... looks like this could be challenging without the correct sources.

Ok this option looks promising. The problem I have is :
"cannot load '/sdcard/boot.img'"
running the command:
"fastboot boot /sdcard/boot.img" ( AS root on my linux machine )
Note: I can see the usb device with fastboot devices
Click to expand...
Click to collapse
Ok try running it off of your computer then. fastboot boot /home/user/boot.img (wherever you actually have it)
Ah.. That is why. My original goal was to create a kernel module for the phone... looks like this could be challenging without the correct sources.
Click to expand...
Click to collapse
Yup. That's our exact problem and why we are somewhat limited on what we can do for modifying stuff.

With HBOOT-1.41.0000, the boot option is disabled apparently...
sudo ~/android/android-sdk-linux_86/tools/fastboot boot ./boot.img
downloading 'boot.img'... FAILED (remote: not allow)

Yea I knew that with our hboot the option to flash via fastboot was disabled, but I have been able to successfully boot through it. That's how I test my boot imgs. Other than trying the RUU while you are in fastboot it seems like it's pretty dead.
What happens if you boot in to the recovery partition? The stock one. Does adb see the phone then?

Well I just tested the RUU, 1.29 version. I got this error:
ERROR[140]: BOOTLOADER VERSION ERROR
The recovery partition ( default one) apparently doesn't exist just shows an
X or something with a phone. ( The default image ?)
What version of fastboot are you using? That seems to be my only hope at this point.

Is this a "with google" branded phone?
The fastboot I have is the one that came with the sdk for windows. It doesn't provide me with any type of version number.

Ok, I got it to boot off of one of the later fresh.zip's boot.img.
The default version of hboot has most options of fastboot disabled.
However, there is a way of getting around it.
1.) boot into fastboot mode
2.) fastboot -s $DEVICEID oem rebootRUU
3.) fastboot whatever, upgrade, boot etc all seem to work.
Still waiting on the boot... still stuck at the "HTC" screen. hopefully it will boot up eventually.

fred43 said:
2.) fastboot -s $DEVICEID oem rebootRUU
Click to expand...
Click to collapse
I knew that command worked with adb (that's how you do a manual RUU) but I didn't think it worked in fastboot. Good to know.
See if you can adb now that it's running off a proper boot.img.

Well looks like I spoke to soon. The boot option apparently ignores the file argument while in oem mode.

OK. so I'm back at square one. IN RUU mode, is there anything I can do?
Can I get a stock image later than 1.29 somewhere? Something that will
pass the security check of the installer.

fred43 said:
OK. so I'm back at square one. IN RUU mode, is there anything I can do?
Can I get a stock image later than 1.29 somewhere? Something that will
pass the security check of the installer.
Click to expand...
Click to collapse
Not that has been made available, no. You didn't answer me earlier. Is your phone stamped "with google" on the back cover?

[Q] Stuck in Bootloader

Hi all,
my nexus wont start after (failed?!) flashing with factory image. bootloader and recovery mode are accessable. i have no backup so i need to flash a new img, but my tablet wont be recognized by my computer anymore(adb drivers not working?!). i tried to deinstall and reinstall the adb drivers alrdy. Device manager shows nexus 7 as Android Phone with "Android Bootloader interface" i cant install adb drivers while in bootloader. in recovery mode i succeeded installing the adb drivers and the tablet is shown correctly in device manager... i need help dont know what to do :crying: .. any suggestions ?

ADB and fastboot drivers are different.

Pirateghost said:
ADB and fastboot drivers are different.
Click to expand...
Click to collapse
yes .. what are u trying to tell me? dont get it.. i used nexus root toolkit to help me apply those drivers.. but it wont work for bootloader/fastboot mode.. i cant flash my tablet because my device wont be recognized by my pc.. im stuck at the bootloaderscreen/fastbootmode....

http://bit.ly/Zqk7pm

and what do u want me to type in there ? i alrdy used google for the last 7 hours ?

oads said:
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
Click to expand...
Click to collapse
SMH
i filled it in for you.....

Pirateghost said:
SMH
i filled it in for you.....
Click to expand...
Click to collapse
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..

no. ADB and fastboot require separate drivers. just install the drivers required for n7 fastboot. there was a link in that list.
there are tutorials here on xda, as well as youtube videos and tutorials on other sites. take a little initiative and learn the ropes. it will help you out later on.

oads said:
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
Click to expand...
Click to collapse
Just relax and take your time.
If your tablet can go into fastboot mode, it is fine and will get better; the only thing standing between it's current state and being brought back to life is a little learning on your part.
Now you see what the problems are with using a toolkit - because they hide all the gory details from you, when the smallest thing goes wrong you are totally helpless due to a lack of understanding about what things are going on underneath the hood. And as it turns out, what "goes on under the hood" isn't really all that complicated either if you do things the full manual way.
Which is not to say that you can not simply just use the toolkit again; if you previously successfully installed drivers that allowed you to talk to the tablet in all of these modes:
- fastboot
- adb w/ custom recovery booted
- adb with Android booted
then it is not evident that you need to be fooling with drivers.
I suggest you read this thread, from start to finish
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Then, go over to your toolkit thread and read it from start to finish. You will see that there are & have been plenty of people in circumstances nearly identical to yours.
good luck

hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?

oads said:
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
Click to expand...
Click to collapse
that does not sound like a problem to me at all.
You communicate with the device using the "fastboot" program when it is in bootloader/fastboot mode, and with the "adb" program when it is in custom recovery boot.
What you see in the device manager appears to be completely normal - In different modes it shows up in different places. It's not supposed to show up with the same driver in different modes.
Code:
fastboot devices
will show you whether you are communicating successfully with the device when it is in bootloader/fastboot mode, and
Code:
adb devices
will show you whether you are communicating successfully with the device in recovery mode.
I suppose your toolkit has some stoopid menu or buttons someplace that will allow you to test for exactly the same thing. Now all you need to do is stop posting here and read a little bit.
good luck

bftb0 said:
Now all you need to do is stop posting here and read a little bit.
good luck
Click to expand...
Click to collapse
well i did read quite a lot today :crying: i cant find my device when i type in adb devices, im pretty sure i have the right drivers installed since i followed the instructions step by step.
this guy seems to have the same problem: http://forum.xda-developers.com/showthread.php?t=1808076
could someone tell me if this could be a possible solution :http://stackoverflow.com/questions/...e-over-usb-via-adb-devices-from-windows-7-x64
also would it be possible to just get into the bootloader (since thats the purpose of adb drivers and i can do this) and just proceed with fastboot commands ? if i type in fastboot devices the tablet will show up...

In your first post, you indicated that you couldn't connect to the tablet that was in bootloader mode with adb.
And then you were told - once vaguely and once quite specifically - that *nobody* can communicate with the tablet using adb when the tablet is in bootloader/fastboot mode.
As stated previously, use the "fastboot" program when the tablet is in bootloader mode, and use the "adb" program when the tablet is booted to the custom recovery (or the regular android boot if USB debugging has been enabled).
You can use either one of these modes to effect a rescue so long as they are working correctly - they don't need to both be working. Eventually you would want that to be the case, but for the moment why don't you just stick with what is working for you.
If you get a device ID printed when you execute "fastboot devices" when the tablet is in boot loader/fastboot mode, that is all you need to reinstall a factory ROM, using nothing but fastboot.

thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g

oads said:
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
Click to expand...
Click to collapse
Well, I can't see what instructions you are following, and there is a possibility of sensitivity to an exact sequence. In particular, is a
fastboot reboot-bootloader
performed after the bootloader is flashed, but before the radio is flashed? It might be important that you are performing the radio flash from one bootloader vs. the other. Just a guess. (Along the same lines, do you see something unexpected happening, such as a boot to the recovery after the radio flash command?)
There are some other threads on this I think. (I have a grouper device not tilapia) But I thought that those threads were about problems with radio flashing when a custom recovery (rather than a stock recovery) was on the phone, but that was for applying the OTA package for tilapia rather than flashing directly from fastboot.
-------------------------------------------------------
[Edit] whoops, wait a minute.... "cannot load"
When you run fastboot from the command line, the file names you give are relative to the current directory. Did you move those image files into the same directory that you are executing the "fastboot" command from?
Alternately you can specify the full pathname to wherever you unpacked the files, for instance
fastboot flash radio C:\myfolder\unpacked\googlen7\4.2.2\radio-tilapia-1231_0.17.0_1025.img

hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?

oads said:
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
Click to expand...
Click to collapse
I would complete the rest of the steps first and see if everything is still working. Your device *should* still work just fine with an old radio firmware. (Boot it up and see what radio firmware the OS reports on the Settings... about device... status page).
I'll pull down the tilapia image and tell you what MD5 I observe for the radio image.

just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio

Pirateghost said:
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Click to expand...
Click to collapse
yes

SHA1
0798439d363beb145d9223a42ed9edf3de1a30f4 nakasig-jdq39-factory-0798439d.tgz
bb824d449f44d2ad43c5d2a463fe1244d2faf525 nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
f406ae9133c56200306d5c7d64d151f21e0be3c4 nakasig-jdq39/image-nakasig-jdq39.zip
MD5
ee8db1ed6ff1c007fe12136d4bc65cd8 nakasig-jdq39-factory-0798439d.tgz
276cb738e5b9e18a088b6a3eef8155ad nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
4cfa996b6513a7fa53db7cbfd1134396 nakasig-jdq39/image-nakasig-jdq39.zip
radio image is 16,777,216 bytes long
---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------
the google - provided instructions (flash-all.sh) have 10 second sleeps after the bootloader resets - are you waiting long enough?
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.18.img
fastboot reboot-bootloader
sleep 10
fastboot flash radio radio-tilapia-1231_0.17.0_1205.img
fastboot reboot-bootloader
sleep 10
Also - something to check since you are rebooting the bootloader - does the device show up correctly in the Windows device manager? (Sometimes with soft reboots I have found the need to pull the USB cable and plug it back in to the PC).

[GUIDE] How To Enter Fastboot Mode

This is the method tried on H815T model. But I think this should work with also other H815 models (other devices cannot say). Thanks to @autoprime, @thecubed and @Unjustified Dev for this.
Disclaimer: I am not responsible if your device gets into any more trouble for this.
Steps:
1. Download & clean install LG Drivers in your pc if u don't have it already.
2. Go into download mode by presing down the UP button and connecting the usb cable to the pc.
3. Go into LG ROOT folder. see this link to download: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
4. Double click on ports.bat to know your COM port. Let's say it's COM4.
5. Open a windows command promt by Shift+Rt Click into the Lg Root folder.
6. Now send these commands:
Code:
Send_Command.exe \\.\COM4
It will reply
Code:
SPECIAL COMMAND : ENTER , LEAVE
#
7. Now command type
Code:
id
It should reply
Code:
uid=(0)root gid=(0)root
#
8. Now type
Code:
dd if=/dev/zero bs=8192 seek=35840 count=5120 of=/dev/block/mmcblk0
It will reply
Code:
#
9. Now pull out your battery, put it back in, go into HARD RESET mode by pressing down DOWN BUTTON+POWER BUTTON together and when the LG logo apprears, release the power button for a second and press it back again.
10. Now in HARD RESET, it will ask you whether you want to reset everything or not. Select "No" and it will take you to fastboot mode.
Special note:
1. @autoprime told me to factory reset everything before starting this whole process. I did as my bootloader was locked. Don't know how it affects in unlocked bootloader.
2. How to get out of fastboot normally: I don't know it quitely. My bootloader was locked, so neither I could flash any system file through fastboot, nor "fastboot reboot" or "fastboot reboot bootloader" worked for me. @autoprime told me to get out of fastboot, manually go into download mode, then pull out your battery and put back in. Actually you can't get out of the fastboot that way until you flash a KDZ.
Thank u. Reply in the comments if fastboot could help you any.

delete

Hi,
Thank you very much for this Guide. Unfortunately, having tried to unbrick my device (H815) previously by hard resetting and not having access to Android to re-activate ADB, the Shell (Send_command.exe) didn't help me (at every command it returns a "FAIL" message, my phone is recognized by Windows by the way).
So I couldn't get into Fastboot by following this Guide.
Hope it works for others, waiting for results!

TheBledard said:
Hi,
Thank you very much for this Guide. Unfortunately, having tried to unbrick my device (H815) previously by hard resetting and not having access to Android to re-activate ADB, the Shell (Send_command.exe) didn't help me (at every command it returns a "FAIL" message, my phone is recognized by Windows by the way).
So I couldn't get into Fastboot by following this Guide.
Hope it works for others, waiting for results!
Click to expand...
Click to collapse
You couldn't get into fastboot or u couldn't flash anything in fastboot? I cannot make my device recognised in adb too, but it is recognised in fastboot. U need to have the adb and fastboot setup in your pc. But I couldn't flash anything in fastboot as it shows my device is locked although someone said, theoritically it was supposed to flash system files through fastboot.

nipun1110 said:
You couldn't get into fastboot or u couldn't flash anything in fastboot? I cannot make my device recognised in adb too, but it is recognised in fastboot. U need to have the adb and fastboot setup in your pc. But I couldn't flash anything in fastboot as it shows my device is locked although someone said, theoritically it was supposed to flash system files through fastboot.
Click to expand...
Click to collapse
I couldn't get into Fastboot at all. Any command typed in send_command.exe gives "Fail" as result... Phone is connected in Download Mode and recognized in Windows, DIAG1 port is COM4.
Screenshot attached

lock bootloader , fastboot unnecessary

29y6145 said:
lock bootloader , fastboot unnecessary
Click to expand...
Click to collapse
True. I didn't realise that before, so gave it a try. But this may help those with unlocked bootloader.
Sent from my LG-H815 using Tapatalk

I always get a "FAIL" reply. Any ideas?

nipun1110 said:
True. I didn't realise that before, so gave it a try. But this may help those with unlocked bootloader.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
With an unlocked bootloader...
Code:
adb reboot bootloader

nobnut said:
With an unlocked bootloader...
Code:
adb reboot bootloader
Click to expand...
Click to collapse
Hahahah tru!

nobnut said:
With an unlocked bootloader...
Code:
adb reboot bootloader
Click to expand...
Click to collapse
maybe u r suggesting to say
fastboot reboot bootloader
right?
Sent from my LG-H815 using Tapatalk

This does not work for me, I have an unlocked bootloader, but just get the response "FAIL".

And... Why don't you just zero the laf partition instead through an adb shell? What does this do that's different?

If we can get into fastboot, can we then do something like
Code:
fastboot boot recovery.img
to get into a custom type recovery and do a backup? I'm on the AT&T H810 version, locked bootloader, I don't know if that means a big fat NO lol or if this method of getting into fastboot mode would even work on my variant.

petermg said:
If we can get into fastboot, can we then do something like
Code:
fastboot boot recovery.img
to get into a custom type recovery and do a backup? I'm on the AT&T H810 version, locked bootloader, I don't know if that means a big fat NO lol or if this method of getting into fastboot mode would even work on my variant.
Click to expand...
Click to collapse
no one should be wiping laf or recovery to get into fastboot. it's a dumbed down fastboot that doesn't let anything flash or boot. the directions I gave OP were in a PM as a last resort because he was stuck in download mode with no booting and wanted to try fastboot. It was never meant to be suggested in public to users who might think they can get anywhere with it.

autoprime said:
no one should be wiping laf or recovery to get into fastboot. it's a dumbed down fastboot that doesn't let anything flash or boot. the directions I gave OP were in a PM as a last resort because he was stuck in download mode with no booting and wanted to try fastboot. It was never meant to be suggested in public to users who might think they can get anywhere with it.
Click to expand...
Click to collapse
Ok then if u suggesting me I should delete the post, I will ask Moderator to do so.
Sent from my LG-H815 using Tapatalk

It's good

Holly molly sir! You are a legend. Long story not so short. My lg got the bootloop bug. Took 2 months to fix, but apparently they changed my locked to three uk H815 "eu open" motherboard with actually unlocked one. So I was finally able to unlock boot-loader, root and **** up (LOL). Apparently I didn't install twrp properly (you'd think "fastboot boot twrp.img" would not install it but run it once) And i was following this to get Android M on. But it requires reboot before boot-loader is flashed. Right when i clicked reboot i figured it wont start in twrp but in stock recovery. So I couldn't even get proper bootloop, it would cut half way into the LG logo. I reckon kdz-ing would havedone the trick, but god it takes ages to DL the kdz file. So in the mean time i found this legendary post. The odd thing was i had to click Yes, on the factory reset screen, but it got me to "Fastboot mode started" and from there i booted into twrp and finished what it had started, currently its Optimising app 35 of 55. Nice one OP, Nice One!

hi i have unlocked bootloader. but i keep getting FAIL as response

nipun1110 said:
8. Now type
Code:
dd if=/dev/zero bs=8192 seek=35840 count=5120 of=/dev/block/mmcblk0
It will reply
Code:
#
Click to expand...
Click to collapse
Hi,
how can I change it back to default Factory reset??

Stuck in Bootloop

US996 Unlocked, stock rom. I was in XDA Forums and saw there were app updates, one being Play Store. I updated. When I tried to get into Play Store, the message "this version of play store is incompatible with your device, go to settings and disable app update (or something like that). I tried but the app was not listed in settings. I tried to reboot and now the phone bootloops. All I can get is the warning that the software cannot be checked for corruption and then a quick display of the LG logo, then screen off, and then LG logo again and then warning screen, etc. If I try to reboot into recovery I get the Factory data reset screens and I answer both "yes" and the phone goes into adb mode.. From adb mode I can fastboot reboot, which puts me back into the above loop, or fastboot bootloader, which merely returns me to the adb screen. What can I do now?

Maybe try relocking the bootloader. I am pretty sure (someone correct me if I am wrong) that that pop-up of the "cannot check for corruption" usually only shows when the bootloader is unlocked.

XP_1 said:
Maybe try relocking the bootloader. I am pretty sure (someone correct me if I am wrong) that that pop-up of the "cannot check for corruption" usually only shows when the bootloader is unlocked.
Click to expand...
Click to collapse
Is that even possible? Don't know how to do it.

PhoneBull said:
Is that even possible? Don't know how to do it.
Click to expand...
Click to collapse
Try entering
Code:
fastboot oem device-info
into Fastboot on your computer to see if it says it is unlocked when in fastboot mode.

XP_1 said:
Try entering
Code:
fastboot oem device-info
into Fastboot on your computer to see if it says it is unlocked when in fastboot mode.
Click to expand...
Click to collapse
I get "FAILED (remote: unknown command)"

Do you have fastboot installed on your computer? (Something you would have had to have intentionally installed) If not google Minimal Fastboot /ADB and install it, enter the supposed ADB screen you are talking about and see if it makes contact with your phone.

XP_1 said:
Do you have fastboot installed on your computer? (Something you would have had to have intentionally installed) If not google Minimal Fastboot /ADB and install it, enter the supposed ADB screen you are talking about and see if it makes contact with your phone.
Click to expand...
Click to collapse
I have the fastboot on the PC that I used to unlock the bootloader.. I enter fastboot on the PC via the administrative command prompt. With the phone in the fastboot mode, I type "fastboot devices" on the PC and get a proper response (LGUS996ab**** fastboot). If I enter ""fastboot reboot" I get the bootloop. If I enter "fastboot bootloader" I wind up in Fastboot Mode on the phone again. I was hoping there was a "fastboot recovery" command but there doesn't seem to be. I don't know what to do next. I am not all that familiar with what can be done from fastboot. My only experience with it was when I unlocked the phone. I am desperate!

Okay, so if you do not have TWRP installed on your phone, then I don't know if you can save your data. You can try to
Code:
fastboot erase cache
and see if it helps, or if not and just reset the device fastboot oem lock I think. Maybe ask around in the unlocking help threads or perhaps someone with more knowledge will chime in. If none of this works, then there are some instructions on how to get your phone back to stock in the News and Guides section.
EDIT: Maybe try the power+volume down. It may work? I have tried it and never got it to successfully work. But you can try it.

XP_1 said:
Okay, so if you do not have TWRP installed on your phone, then I don't know if you can save your data. You can try to
Code:
fastboot erase cache
and see if it helps, or if not and just reset the device fastboot oem lock I think. Maybe ask around in the unlocking help threads or perhaps someone with more knowledge will chime in. If none of this works, then there are some instructions on how to get your phone back to stock in the News and Guides section.
Click to expand...
Click to collapse
Thanks for your help. I DO have TWRP installed and have used it often for backups. But now the only way I know to TRY to get to it is by the power/vol down until LG logo, then release/repress power button sequence but this just gets me into fastboot mode. II have some recent backups saved on my micro SD card - is there any way to flash one of them through fastboot if I load one onto the PC?

Yeah. My bad. Okay, so how I get into TWRP is through the EasyRecowvery.
Go ahead and download it from Git-Hub (1.3b3).
Now extract it and run the cmd program. Enter 5. which is extras and stuff and then enter 5 again in the sub menu which will let you boot into recovery. When you are in recovery, and plugged into your computer, you should be able to either flash or drag and drop like a flash drive on the the phone. Hope that helps a little bit.

XP_1 said:
Yeah. My bad. Okay, so how I get into TWRP is through the EasyRecowvery.
Go ahead and download it from Git-Hub (1.3b3).
Now extract it and run the cmd program. Enter 5. which is extras and stuff and then enter 5 again in the sub menu which will let you boot into recovery. When you are in recovery, and plugged into your computer, you should be able to either flash or drag and drop like a flash drive on the the phone. Hope that helps a little bit.
Click to expand...
Click to collapse
I don't have T-Mobile. I have Verizon Wireless on the US996. Will that work?

PhoneBull said:
I don't have T-Mobile. I have Verizon Wireless on the US996. Will that work?
Click to expand...
Click to collapse
Since you are only rebooting into recovery and not flashing anything it might. If not, it will just fail and not harm anything. Last thing to try is the
Code:
adb reboot recovery
which is the only thing I can think of and I think you already tried it. Otherwise you will need to just go stock.

Fastboot mode issue in MiA1

Hi.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??

Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.

I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.

MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.

oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started

MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.

oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?

MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.

oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.

MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.

oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.

MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.

oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?

wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.

Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!

MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html

I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.