Develop Bugs

[Q] Help!!!! Phone Brick!!!!

Ok so i just got my optimus g a couple days ago (LS970) and when i rooted it and unlocked it on zv8 but when i got the zv9 update available i tried installing tht for a ROM and it bricked installing it!!! im freakin out cus i used this guide http://forum.xda-developers.com/show....php?t=2082084 and when i got to sideload it (im using CVM btw) it says in command prompt "Access is Denied" and i dont know how to get past it! Please Help!

Reynolds1029 said:
Ok so i just got my optimus g a couple days ago (LS970) and when i rooted it and unlocked it on zv8 but when i got the zv9 update available i tried installing tht for a ROM and it bricked installing it!!! im freakin out cus i used this guide http://forum.xda-developers.com/show....php?t=2082084 and when i got to sideload it (im using CVM btw) it says in command prompt "Access is Denied" and i dont know how to get past it! Please Help!
Click to expand...
Click to collapse
Just bricked mine installing 9 also. Can't do anything, but mess around in TWRP. LGPNST won't detect my phone. Stuggling here. I guess I need to reactivate the evo for a while. Really pissed.

Hey guys, I've tried installing stock all over again and that won't even work for this problem. what a conundrum.

Reynolds1029 said:
Ok so i just got my optimus g a couple days ago (LS970) and when i rooted it and unlocked it on zv8 but when i got the zv9 update available i tried installing tht for a ROM and it bricked installing it!!! im freakin out cus i used this guide http://forum.xda-developers.com/show....php?t=2082084 and when i got to sideload it (im using CVM btw) it says in command prompt "Access is Denied" and i dont know how to get past it! Please Help!
Click to expand...
Click to collapse
the easy way to get back on your phone is doing the restore method using lgnpst tool..there are differents methods guides..
1)AutoLGNPST-tSilenzio.zip
2)LGNPST-PhantomPhreak53.zip
3)lgnpst-shelnutt.zip
so with these tools you can go back to v7 fool unroot and then update it to v8 and v9 ,just you want to make sure if your phone can get the download mode,,,for more information you can go to irc freenode guyz its is a private chat,,,and then ask them about the lgnpst tools link,im sure they will give you more information about it,,,they have the link for both software restore(v7 and v9 .tot files)if not i posted in general the v9 .tot file link, dont worry your phone still alive,i hope adb to push files directly to custom recovery it doesnt work so the easy and method way is restore it!!!:laugh:

MikeDroid said:
Just bricked mine installing 9 also. Can't do anything, but mess around in TWRP. LGPNST won't detect my phone. Stuggling here. I guess I need to reactivate the evo for a while. Really pissed.
Click to expand...
Click to collapse
did you put your phone into download mode when you tried lgpnst

I want to tell to everybody if you installed the v9 update dont try to root and unlock or install custom recovery,even going back and restor the v7....if you try the phone it wont restar...
---------- Post added at 08:57 AM ---------- Previous post was at 08:44 AM ----------
THIS IS THE GUIDE HOW TO RESTORE IT OR UNROOT IT.....
1. Install LGUnitedMobileDriver_S4981MAN38AP22_ML_WHQL_Ver_3.8.1 (LG USB Drivers)
2. Install LGNPSTv1.3_Lab_Verison_RightClickReg (LGNPST)
3. Install LGNPST_GenericModels_Ver_5_0_12_0 (LGNPST Generic Modules)
4. Install LGNPST_Components_Ver_5_0_20_0 (LGNPST Components)
5. Copy the Models folder to C:\LG Electronics\LGNPST\
6. Start a command prompt as admin
7. Type regsvr32 "C:\LG Electronics\LGNPST\Models\LGNPST_LS970.dll"
8. Download the proper .tot file for your phone
9. Rename .tot to .bin
10. Open LGNPST
11. Select the LGNPST_LS970.dll and your .bin file
12. Press Start
If LGNPST errors out at 85%, turn your phone off and hold the power button until the phone powers on, then release.

never mind....
Sent from my LG-LS970 using xda app-developers app

Fix
Reynolds1029 said:
Ok so i just got my optimus g a couple days ago (LS970) and when i rooted it and unlocked it on zv8 but when i got the zv9 update available i tried installing tht for a ROM and it bricked installing it!!! im freakin out cus i used this guide http://forum.xda-developers.com/show....php?t=2082084 and when i got to sideload it (im using CVM btw) it says in command prompt "Access is Denied" and i dont know how to get past it! Please Help!
Click to expand...
Click to collapse
Accessing Recovery Screen (First Step if you have bricked your phone)
This is our initial step for any problems that might arise. If you can access recovery, usually you're in a perfectly fine situation.
1. Power off your phone by holding Volume down & power at the same time.
2. When the screen shuts off, switch to entering fastboot by holding Volume Up & Power. Release immediately once you see a black screen with some text on the bottom.
3. You should see a black screen with some text at the bottom.
4. Press volume down 2x and then the power button.
5. You should see either TWRP or CWM recovery.
6. Wipe Cache, Dalvic Cache, and Factory Wipe
7. Flash new stock zip. Wipe caches again.
8. Restart.
If you need further help view the full post by AdriVelazquez (HERE)

Reynolds1029 said:
Ok so i just got my optimus g a couple days ago (LS970) and when i rooted it and unlocked it on zv8 but when i got the zv9 update available i tried installing tht for a ROM and it bricked installing it!!! im freakin out cus i used this guide http://forum.xda-developers.com/show....php?t=2082084 and when i got to sideload it (im using CVM btw) it says in command prompt "Access is Denied" and i dont know how to get past it! Please Help!
Click to expand...
Click to collapse
Well good new here for all that brick is that you can go to any sprint store and exchange it as a defective device, but please do all you cn to get it back into working order, simply because Sprint does not have an official rooting policy it simply states "if phone appears rooted , make a note and continue as normal"
Now be ready with the correct verbage as everything in the Sprint world is at managers discretion which simply means a manager can say no and you would have to take it to retention, no body wants this. So just be cool and tell them you did the OTA and this is what happened simple as that. If worse comes to worse just tell ask them to DHRP it since the phone is so new you will get a new 1 anyways.
BUT PLEASE FOR THE SAKE OF ALL US INCLUDING YOURSELF GIVE IT YOUR BEST SHOT AT RETURNING IT TO STOCK , IF YOUR HAVING TROUBLE HIT UP SOME OF THE DEVS ON GTALK , Im sure one of them or I if I am home will do our best to walk you through it.

Hey all i forgot i posted this thread awhile ago sorry kinda just me n my bro went hard at work and finally fixed the phone and i found the probelm.. At the IRC at the time there were different versions of LGNPST i used the one directed to in the guide i used and that was the autoLGNPST and it was version 1.3 but it never recognized the device in download mode so my bro said it had to be a driver issue so im like ok we find a few drivers install just to make sure and at that point we knew that the computer was reconizing the phone because on ADB we can push a file through and i can install a ROM which i did but for some reason it never could install.. it was the lifeless ROM and dont worry i cleared everything but it never booted after that just kept booting into CWM. So im like ok i bring it to the sprint store the next day the Technician wasent there that day so i hada wait till the next day but that night i tried one more time 2 fix this thing and turns out that day the IRC puts up new files and it was a new version of autoLGNPST v2.2 or v2.3 i believe new DLLs and a new .bin file for ZV7 and the old ones were corrupt i used the new files a viola IT WORKED!! BUT... i cant for the life of me get a flippin ROM on here dont matter which ROM i try or if i use CWM or TWRP i cant get a ROM on always either the install fails or i install it and it reboots but just comes up with a blank screen after the LG logo and mind u i use the AiO tool on the forums to unlock the bootloader and root it and install TWRP or CWM and im on ZV8 when im installing them n ive tried many many times and i just wind up LGNPSTing it again backups never work either any help with this would be greatly appreciated

lgnpst 85% error cause: download failed
ALBERTOSCLN said:
I want to tell to everybody if you installed the v9 update dont try to root and unlock or install custom recovery,even going back and restor the v7....if you try the phone it wont restar...
---------- Post added at 08:57 AM ---------- Previous post was at 08:44 AM ----------
THIS IS THE GUIDE HOW TO RESTORE IT OR UNROOT IT.....
1. Install LGUnitedMobileDriver_S4981MAN38AP22_ML_WHQL_Ver_3.8.1 (LG USB Drivers)
2. Install LGNPSTv1.3_Lab_Verison_RightClickReg (LGNPST)
3. Install LGNPST_GenericModels_Ver_5_0_12_0 (LGNPST Generic Modules)
4. Install LGNPST_Components_Ver_5_0_20_0 (LGNPST Components)
5. Copy the Models folder to C:\LG Electronics\LGNPST\
6. Start a command prompt as admin
7. Type regsvr32 "C:\LG Electronics\LGNPST\Models\LGNPST_LS970.dll"
8. Download the proper .tot file for your phone
9. Rename .tot to .bin
10. Open LGNPST
11. Select the LGNPST_LS970.dll and your .bin file
12. Press Start
If LGNPST errors out at 85%, turn your phone off and hold the power button until the phone powers on, then release.
Click to expand...
Click to collapse
This is what my LGNPST does, it shows an error at 85% saying
"Process: Upgrade_Masterbin
"Subproc : Masterbin Donwload
Cause: Download Failed"
I did what you suggested (hold the power button until the phone powers on? rather powers off, right?) I am in donwload mode and tried taking out the battery and restarting into download mode and repeating the flashing process (unitl 85%) various times... always with the same error message as a result... what is the problem?

Cause: Download Failed
zendoo said:
This is what my LGNPST does, it shows an error at 85% saying
"Process: Upgrade_Masterbin
"Subproc : Masterbin Donwload
Cause: Download Failed"
I did what you suggested (hold the power button until the phone powers on? rather powers off, right?) I am in donwload mode and tried taking out the battery and restarting into download mode and repeating the flashing process (unitl 85%) various times... always with the same error message as a result... what is the problem?
Click to expand...
Click to collapse
You managed to solve it

[Q] Strange root problem, please help

Okay it's been a few months since this has happened so I'll try to remember as best as I can; I had rooted my Nexus using WugFresh's kit, everything went fine. It was rooted for about 6 months and eventually got stuck in a boot loop (no clue how this happened, I hadn't installed any kernals, roms, even apps in months). I tried like 4 or 5 different methods to fix the issue; I finally was able to get the phone working again using ODIN mode, it completely restored it to stock (as far as I'm aware).
So I tried to re-root the phone; no luck, using ANY method I've been able to find. The main problem is I can't seem to get into TWRP, every time I try to it simply gives me the dead android with the red exclamation point. I'm not an advanced user by any means, but I'm not totally clueless and I can follow directions. If anyone has any advice for me on this I'd GREATLY appreciate it, I have an excellent 4G signal where I live and the only other internet option is AT&T basic DSL so I'd really like to be able to use my wifi hotspot again. Thanks in advance for your time, I appreciate anyone who takes the time to try to help.

1) android on its back is stock recovery.
2) follow this: http://forum.xda-developers.com/showthread.php?t=1529058
it works 100% of the time if you read and take your time.

it sounds like you have root but cant flash a recovery, let me know if im wrong but if this is the case I would just download goo manager from the market and go into settings and flash a custom recovery and that should fix your recovery problem but sometimes you have to download the recovery twice ive noticed that in the past, let me know if this works for you or you could go through the longer process above but your fix may be very simple

Thanks for the info, I will try this either tonight or tomorrow and get back to you; I certainly hope it works!

jaymazz13 said:
it sounds like you have root but cant flash a recovery, let me know if im wrong but if this is the case I would just download goo manager from the market and go into settings and flash a custom recovery and that should fix your recovery problem but sometimes you have to download the recovery twice ive noticed that in the past, let me know if this works for you or you could go through the longer process above but your fix may be very simple
Click to expand...
Click to collapse
I thought that too, but I tried installing super user and a couple of other root-only apps and it said that my device wasn't rooted. =P

Zepius said:
1) android on its back is stock recovery.
2) follow this: http://forum.xda-developers.com/showthread.php?t=1529058
it works 100% of the time if you read and take your time.
Click to expand...
Click to collapse
This is driving me insane. I'm trying this method; I followed the directions step by step, but my phone is showing that it is unlocked already (when I entered the fastboot oem unlock command in CP it returned FAILED: Invalid Command, but it is showing as unlocked in bootloader.
Now for the weird part; I rebooted to bootloader and tried fastboot flash recovery recovery-clockwork-6.0.2.3-toroplus.img and it returned immediately FAILED: Invalid Argument. I decided to start the process over, and now I can't reboot from CP, it's saying error: device not found.
I really want to just smash this f*%&ing thing into several hundred thousand pieces right about now, so I'm going to take a break for the moment. Are there different types of bootloaders, or is it possible the my bootloader is just corrupted or something?

There are different bootloaders, but the fastboot commands should work just the same. You're on Windows i'm assuming? You could also look at efrant's guide, http://forum.xda-developers.com/showthread.php?t=1626895, as well as his 101 in the general section stickies. It does not make sense that the device would become not found, and I would try reflashing the bootloader. Don't smash the phone!

Have you tried this method?
http://forum.xda-developers.com/showthread.php?t=1400871

lockehart12 said:
Now for the weird part; I rebooted to bootloader and tried fastboot flash recovery recovery-clockwork-6.0.2.3-toroplus.img and it returned immediately FAILED: Invalid Argument. I decided to start the process over, and now I can't reboot from CP, it's saying error: device not found.
Click to expand...
Click to collapse
your drivers are not installed correctly.

[Q] Unique Situation ATT Galaxy Note 2 Help

Ok, this is my first post so forgive if this is in the wrong section...
I have a friend's Galaxy Note 2 ATT that was stuck on the Galaxy Note 2 Boot screen, and it wouldn't go any further.
Because I work for Samsung at the Samsung Experience Shop, I tried running it through our smart reflash tool
-----> This didn't work because it would fully download it onto the phone, but when it got to the Android with the thing spinning in its chest, it would stop and ALWAYS freeze halfway.
Next step I tried doing was going through Samsung Kies and downloading the stock OS and load that, but the same Android with the spinning thing in its chest would show up and it would freeze.
Due to this guy being my friend I told him I would try anything to get his phone to work again (root, to custom recovery, to custom rom)
My steps so far:
1. I have successfully rooted my device via ODIN 1.85 by using CF-Auto-Root
2. Afterwards, I loaded on a custom recovery via ODIN 1.85 which now is philz_touch_6.07.9
Here is my problem now, I've tried searching everywhere and I can't really find the answer...
Whenever I try to side load a rom through ADB through Android tools (its in the right directory and everything because it transfers over), I keep getting an error message "E: Error in /tmp/update.zip (status 7) Installation Aborted."
Now before I get that error I get stuff like getprop("ro.product.device")==t0lte" ||getprop("ro.build.product").... etc. and it goes on and on.
So far the ROMs that I have tried were Cyanogenmod 10.1 and the Pacman Rom, and yes, both are for the correct device like the model name/number match up. And now how I said I thought I rooted the device, whenever I try to reboot into recovery via Philztouch, it says at the top Root Access is missing. Root device, and I click yes. When it reboots into recovery and I want to turn the phone off again, it still says Root Access is missing.
I am open for anything really. My friend just wants his phone to work again. and I've literally exhausted all of my ideas as I keep running into the same issue.
What am I doing wrong? and is something like this possible to fix? Or is my friend SOL?
Thanks for all the help. It's much appreciated.

Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.

rangercaptain said:
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
Click to expand...
Click to collapse
+1 to this^^^^^
Look here»»» http://forum.xda-developers.com/showthread.php?t=1981198
And why not give him something stock instead of a CM Rom??[emoji37]
Plenty of stock 4.3 Rom's in the development section...
Sent from my SAMSUNG-SGH-I317 using Tapatalk

Good advice ^^^^ for your friend.

Ok, thanks for the direct response. I've downloaded the latest TWRP recovery and when I try to push it through ODIN, I still have PhilZ Touch 6..? Sorry, I feel like I'm skipping something simple...
according to a guide, I have to make sure when I'm pushing a custom recovery through ODIN I have to leave Auto Reboot and F. Reset Time UNCHECKED. I made sure they were, and for some reason after it says PASS and thread successful 1 failed 0. When I disconnect the phone and turn it back on into recovery mode, I still has PhilZ Touch...

Use your recovery to flash TWRP. There's a zip version and an odin version.

Ok, I got stock recovery on there just by redoing the CF-Auto Root package through ODIN.
I figured well I can apply the ROM the adb through the stock recovery...
It was going well until I got this error. The last line before the error stated:
"Veryfying update package..."
Error:
E: failed to verify whole-file signature
E: signature verification failed
is that due to the fact that i'm using stock recovery?
In the mean time since that didn't work I'm going to flash TWRP and hopefully that fixes the issue.
I'm kinda just documenting my steps here in case anyone wants to follow and chime in if i'm doing something wrong.
Thanks for the help guys!
************3AM EDIT*****************
Ok so I managed to get TWRP 2.7 on the device as I needed the ability to adb sideload the update.zip to the phone since I can't boot into the phone's OS whatsoever.
This is the error I'm receiving now:
Checking for MD5 file...
Skipping Md5 check: no MD5 file found.
then it restarts and I'm stuck at the Samsung GALAXY Note II screen... what's my next step..? Find a different ROM?
**********Another Edit**************
It has just come to me, I shouldn't have to adb sideload the update.zip or the custom rom... even though I can't get into the phones OS and can't copy and paste to the root of the device. Can't I just copy and paste it to a micro SD card and mount that, and then apply the update from there? And as far as those errors I had earlier, I'm still not sure why I received them...
Again, thanks for all the help

Adb won't work if USB debugging wasn't enabled.
In TWRP you can disable md5 checking.
And you don't unzip the zip file.

Thanks for the reply. ADB didn't work because, in fact, since I haven't been able to turn the phone on, I know USB debugging isn't turned on.
And as far as having the MD5 check, it is unchecked.
I received a success message. However, when I try to boot the phone it still gets stuck at the Samsung Galaxy Note II screen.
******Edit******
Ok ended up using a different ROM, I think PacMan rom? It seemed to work until it got to extracting system files and then the phone sits for a couple minutes, screen turns black. And when I try to wake the screen, only the back and menu buttons come up...
Another thing, even though I've already rooted my device using CF-Auto-Root, When I reboot my device with TWRP I go to reboot and then recovery. Then it warns me saying no OS bla bla bla, and then it says it notices that my phone isn't rooted? And that SuperSU isn't on the device. It asks to install it by swiping. I swipe it starts to install, phone reboots. When I reboot it again, it still tells me that the phone isn't rooted. And with the phone not being rooted, I'm coming to the conclusion why I'm having trouble trying to flash Roms.. Is this a possibility?

Why are you using ADB? just drop the .zip for the ROM you wish to flash onto a micro SD card, and flash from within the TWRP. Don't try to extract the .zip whatsoever.

Zenfone 2 failed update, can't flash stock firmware

I accidentally allowed the 2.20.40.183 OTA update, which rendered my phone useless. I tried putting MOFD_UPDATE of 2.20.40.174 on my SD card, but that didn't work.
Here's a few other things I tried:
Recovery menu: Updating phone, then dead droid. No menu appears.
adb sideload: adb didn't recognize my phone.
fastboot flash: Permission denied, or something along those lines. The write fails. Tried to flash system.img but it never did and nothing happened.
adb sideload through temporary CWM: Unauthorized device. Couldn't sideload.
Flashing through temporary CWM and temporary TWRP: Fails early on with Status 7. 2.20.40.174 is older, and this is apparently reason enough to deny me.
Does anyone have an idea about what I can do to fix this? Could I flash Cyanogenmod, then flash stock over that, using temporary CWM/TWRP?
My bootloader is not unlocked.

PasserbyPassingBy said:
I accidentally allowed the 2.20.40.183 OTA update, which rendered my phone useless. I tried putting MOFD_UPDATE of 2.20.40.174 on my SD card, but that didn't work.
Here's a few other things I tried:
Recovery menu: Updating phone, then dead droid. No menu appears.
adb sideload: adb didn't recognize my phone.
fastboot flash: Permission denied, or something along those lines. The write fails. Tried to flash system.img but it never did and nothing happened.
adb sideload through temporary CWM: Unauthorized device. Couldn't sideload.
Flashing through temporary CWM and temporary TWRP: Fails early on with Status 7. 2.20.40.174 is older, and this is apparently reason enough to deny me.
Does anyone have an idea about what I can do to fix this? Could I flash Cyanogenmod, then flash stock over that, using temporary CWM/TWRP?
My bootloader is not unlocked.
Click to expand...
Click to collapse
I do the same! Now my phone stuck on boot screen.
Does anybody can help us?

http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256

mr_gourav2000 said:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
I'm not going to lie, that guide's a bit hard to read. I'll try to follow as best as I can and reply if this works for me.
I'd still appreciate any other advice others have.

PasserbyPassingBy said:
I'm not going to lie, that guide's a bit hard to read. I'll try to follow as best as I can and reply if this works for me.
I'd still appreciate any other advice others have.
Click to expand...
Click to collapse
All necessary to read.
Hope you fix the problem.

Fixed
I managed to fix my phone, but not with the method Mr Gourav so kindly posted. I chose not to use mr_gourav2000's IntelSoC fix because the guide was written in a way that made it very hard to follow, and I was unsure if MOOREFIELD was supposed to flash briefly or stay on the Device Manager. Regardless, I wasn't going to risk bricking my phone beyond help by pushing on without knowing what i was doing.
The key was bypassing Status 7 (or 1), which prevents you from downgrading firmware. If your phone says something like "Installation failed with Status 1" or "Status 7," or you get the "Can't install this package over newer build" error when you attempt to flash a previous firmware, this fix can help you. Funny enough, the fix was posted by the very same person earlier this year:
http://forum.xda-developers.com/showpost.php?p=65995574&postcount=116
First, download the latest full firmware from Asus' support site: https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
Then, open or extract the .zip file, and go to into UL-Z00A-WW-(Firmware.Version.Number)-user.zip\META-INF\com\google\android\ . Select updater-script (no file extension), and open it in a plain text editor like Notepad++.
Remove lines 1-6, beginning with "(!less_than_int" and ending with "getprop("ro.product.device") + "\".");". The result should look like this.
Then, insert the edited updater-script into the .zip file, overwriting the old updater-script. At this point, I should mention that one of the removed lines probably checked your phone's model number to see if it was compatible with the firmware. I sure hope you downloaded the right file for your phone. If not, brick city here you come.
Finally, put the edited .zip into a microSD card, and insert that into your phone. If you want to use the stock recovery to install the firmware, rename the .zip to MOFD-UPDATE.zip and put it in the root of the SD, then restart the phone and let it update. Presumably. I didn't use the stock recovery. I used the temporary ClockworkMod recovery to fix my phone, so I'm not sure if it's that simple. If you're using that temporary CWM, just go to the zip installation menu and apply the zip from external_sd.
If you were going through the same problems I was, your phone should boot into stock, unrooted firmware again. Pat yourself on the back and never do whatever dumb thing you did to get to this point in the first place (like absentmindedly apply an OTA update in the middle of a lecture)!
Once again, thanks to mr_gourav2000 for posting this fix earlier. I may not have understood the IntelSoC fix, but I did understand this one!

.183 after update takes an extremelynlong time to boot after asus screen aa well. Made me think mynphone crashed, took a bout 10-15 minutes on first boot for me

Redtexan said:
.183 after update takes an extremelynlong time to boot after asus screen aa well. Made me think mynphone crashed, took a bout 10-15 minutes on first boot for me
Click to expand...
Click to collapse
If it's the 1st boot it generally will as it is recreating cache, dalvik-cache or ART...
It seems to take forever to clear cache too when using recovery but about a heartbeat when using fastboot.... Just another quirk of the phone...

Thank you much
I gotta say, this got me on the right path. Though my issue was exactly the same the fix was a little different.
I had to use the next patch and that worked. Recovery is working now and I have to manually update, but still have root, so no real big deal.
Thanks again.

mastet68 said:
I gotta say, this got me on the right path. Though my issue was exactly the same the fix was a little different.
I had to use the next patch and that worked. Recovery is working now and I have to manually update, but still have root, so no real big deal.
Thanks again.
Click to expand...
Click to collapse
You need to flash boot, droidboot and recovery for the build you are using.
I use fastboot to do this but make sure developer settings are enabled and USB debugging is ticked before trying to flash.
To find the img files for the above mentioned, go to Shakalaka's pre-rooted rom thread in Android Developement, you don't need to download the rom if you don't want to but it sure makes rooting easy.
Find the version of Android you need and download boot,droidboot and recovery img files. Flash with fastboot using these commands -
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
***Make sure the right commands are used or it may result in a brick...***

Question attempted to sideload android 13. failed..bricked?

attempted to sideload android 13. i downloaded the ota files for my phone. downloaded platform tools. did the adb reboot recovery. apply update from adb. it made it to 53% then failed. said failed to read command no error. i tried to apply update from adb again right away. it made it to 1% then started saying failed to read file something something over and over and over on my phone screen. i tried to reboot it. probably a bad idea i know. now its stuck on the G with a bar under it that just keeps scrolling but it cant seem to boot up. please help!

seems like a soft brick, use the Android Flash Tool to reflash the os

hxudsh said:
seems like a soft brick, use the Android Flash Tool to reflash the os
Click to expand...
Click to collapse
Not sure if that will work. i cant get into my phone to get to developer options so i cannot unlock the bootloader.

ytsurX said:
attempted to sideload android 13. i downloaded the ota files for my phone. downloaded platform tools. did the adb reboot recovery. apply update from adb. it made it to 53% then failed. said failed to read command no error. i tried to apply update from adb again right away. it made it to 1% then started saying failed to read file something something over and over and over on my phone screen. i tried to reboot it. probably a bad idea i know. now its stuck on the G with a bar under it that just keeps scrolling but it cant seem to boot up. please help!
Click to expand...
Click to collapse
Try using different cables and ports when sideloading. Also use A to C rather than C to C.

ytsurX said:
Not sure if that will work. i cant get into my phone to get to developer options so i cannot unlock the bootloader.
Click to expand...
Click to collapse
it should work, as it flashes the original software it shouldn't matter if you have the bootloader unlocked or not

hxudsh said:
it should work, as it flashes the original software it shouldn't matter if you have the bootloader unlocked or not
Click to expand...
Click to collapse
You don't need the bootloader to actually be unlocked to use Android Flash Tool, but you do need to have OEM Unlocking enabled in Developer Options. If you do, the Flash Tool will unlock the bootloader itself before flashing the images.

ytsurX said:
attempted to sideload android 13. i downloaded the ota files for my phone. downloaded platform tools. did the adb reboot recovery. apply update from adb. it made it to 53% then failed. said failed to read command no error. i tried to apply update from adb again right away. it made it to 1% then started saying failed to read file something something over and over and over on my phone screen. i tried to reboot it. probably a bad idea i know. now its stuck on the G with a bar under it that just keeps scrolling but it cant seem to boot up. please help!
Click to expand...
Click to collapse
Try USB 2.0. I have 9 different random percentage stops over two different PCs and my phone was soft bricked. I grabbed an adapter that downed my USB 3 to 2 and ran again. First shot on a USB 2.0 the OTA went through and brought my phone back to how it was.