Related
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
dudekiller said:
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
Click to expand...
Click to collapse
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
quendil said:
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
Click to expand...
Click to collapse
im still getting invalid bootloader img
dudekiller said:
im still getting invalid bootloader img
Click to expand...
Click to collapse
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
quendil said:
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
Click to expand...
Click to collapse
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
dudekiller said:
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
Click to expand...
Click to collapse
Oh damn...
On bootloader when you give the command fastboot devices does it show you anything?
i wonder if the TWRP bug is why i was getting bootloop when flashing Bootanimations the other day?
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
alright guys i figured it out i did a oem lock and unlock and then the factory image worked so im stock right now... it might stay that way for a bit.. lol
comicbookguy72 said:
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
Click to expand...
Click to collapse
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Zepius said:
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Click to expand...
Click to collapse
his first priority is fixing it. his second priority is possibly finding out why he borked it and not making the same mistake again. i've borked stuff learning and fixed it with toolkits.
not everyone wants to learn ADB or fastboot commands, or install the SDK, and NOT EVERYONE HAS TO. not everyone is a would-be developer
dudekiller said:
they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
Click to expand...
Click to collapse
So why did you flash via TWRP then?
Han Solo 1 said:
So why did you flash via TWRP then?
Click to expand...
Click to collapse
i didnt go through the faqs before installing, i looked at the rom and what it offered. it said stable so i wasnt to worried about bugs since i was coming from cm11
I'm fairly new to the modding area, I'm familiar with the VZW S3 and S4, but upgraded to an M8...I rooted, got S OFF with firewater, and booted into twrp...BUT somehow the main factory image was deleted, and I can only boot into twrp..it stays at the HTC logo if I just let it boot...help!!
Is there something similar to Samsung's ODIN mode that I can just reflash a factory image?
roadblock217 said:
I'm fairly new to the modding area, I'm familiar with the VZW S3 and S4, but upgraded to an M8...I rooted, got S OFF with firewater, and booted into twrp...BUT somehow the main factory image was deleted, and I can only boot into twrp..it stays at the HTC logo if I just let it boot...help!!
Is there something similar to Samsung's ODIN mode that I can just reflash a factory image?
Click to expand...
Click to collapse
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Dragbike Racer said:
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Click to expand...
Click to collapse
Tried..doesnt work for me
I can get it to boot past the recovery area, but only stays on the white screen with the green HTC logo...
EDIT:::
I want to try it again, but now somehow I have S ON....and it says TAMPERED, below that UNLOCKED in fastboot..
Really frustrated..
Dragbike Racer said:
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Click to expand...
Click to collapse
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
You can get into recovery...it won't let you restore a back up or nothing ?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
---------- Post added at 12:22 AM ---------- Previous post was at 12:17 AM ----------
roadblock217 said:
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
Click to expand...
Click to collapse
Maybe sonic can get you s-off if all else fails with his java card. I'm not sure in your situation but I know he can do it as I used it. But I would use that as last resort
Sent from my HTC6525LVW using XDA Premium 4 mobile app
roadblock217 said:
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
Click to expand...
Click to collapse
So you were S-OFF and you somehow got turned to S-ON...??
I would say flash the RUU and call it a day, but we don't have one and the one we do have you need S-OFF..
best bet?
get into fastboot/bootloader, and put on a custom recovery.
then, get the TWRP nandroid of the OTA, restore to that.
then, weaksauce/S-OFF
and then you should be back to normal.
If adb/fastboot is not working, I suggest you re-install your drivers, worked for me when I didn't think it would.
opion 2
get TWRP on with fastboot
then
adb sideload any ROM to it and then get back to S-OFF
since you are unlocked you should be ok to do this without being htc dev unlocked.
you could also try htc dev, but i think that is locked.
sorry trying to think of anything else.
andybones said:
So you were S-OFF and you somehow got turned to S-ON...??
I would say flash the RUU and call it a day, but we don't have one and the one we do have you need S-OFF..
best bet?
get into fastboot/bootloader, and put on a custom recovery.
then, get the TWRP nandroid of the OTA, restore to that.
then, weaksauce/S-OFF
and then you should be back to normal.
If adb/fastboot is not working, I suggest you re-install your drivers, worked for me when I didn't think it would.
opion 2
get TWRP on with fastboot
then
adb sideload any ROM to it and then get back to S-OFF
since you are unlocked you should be ok to do this without being htc dev unlocked.
you could also try htc dev, but i think that is locked.
sorry trying to think of anything else.
Click to expand...
Click to collapse
I got TWRP back on, but where can I find a nandroid of the OTA? I tried doing a regular backup before things got weird but would not let me...Now I see the bug that doesnt allow to mount system...
roadblock217 said:
I got TWRP back on, but where can I find a nandroid of the OTA? I tried doing a regular backup before things got weird but would not let me...Now I see the bug that doesnt allow to mount system...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2725001
andybones said:
http://forum.xda-developers.com/showthread.php?t=2725001
Click to expand...
Click to collapse
Thanks...just downloaded and am going to try...
What I'm concerned about is not being able to mount /system now...this is so weird
roadblock217 said:
Thanks...just downloaded and am going to try...
What I'm concerned about is not being able to mount /system now...this is so weird
Click to expand...
Click to collapse
because of this, it most likely will not flash the nandroid then as system is a big part of the ROM and needs to be mounted.
you may have to do what was explained earlier and wipe the Internal, and then you may be able to re-do these steps.
so first try it out.
if it doesnt work, I would then wipe the 5 things instead of the 4
1) data
2) cache
3) dalvik cache
4) system
5) Internal storage (this will remove all your internal storage!)
then reboot from recovery into bootloader, then back into recovery and see if system is mounted, if it is, you can go ahead and either do the nandroid backup or an adb sideload. -- your choice
now,
if NONE of that works,
download the "RUU" that was put together and that *should* fix you right up.
andybones said:
http://forum.xda-developers.com/showthread.php?t=2725001
Click to expand...
Click to collapse
Nope won't work. I think it's because there is no marker folder for the m8 in my SD card where I store my backups. I tried making one, and it won't register that there is a folder there...
roadblock217 said:
Nope won't work. I think it's because there is no marker folder for the m8 in my SD card where I store my backups. I tried making one, and it won't register that there is a folder there...
Click to expand...
Click to collapse
yes.. yes it most certainly will work as my ROM is based off that precise nandroid backup...
this is something you should have had backed up..
but, make yourself a dummy nand backup to create the folder..
just don't backup anything except.. data or cache, just pick one thing. and it'll create the folder for you (tip: backup EVERYTHING (Internal., SD-Card, anything important, etc) when playing with beta ROMs. ESP AOSP beta ROMs..
the folder that gets created will be the same throughout your entire stay on the M8 using TWRP, it will never change (well that phone anyway, if you get a refurb or w.e. obv it will be different, but that phones folder markers will never change within TWRP, so it's to your benefit to have this backed up and ready to go...)
andybones said:
yes.. yes it most certainly will work as my ROM is based off that precise nandroid backup...
this is something you should have had backed up..
but, make yourself a dummy nand backup to create the folder..
just don't backup anything except.. data or cache, just pick one thing. and it'll create the folder for you (tip: backup EVERYTHING (Internal., SD-Card, anything important, etc) when playing with beta ROMs. ESP AOSP beta ROMs..
the folder that gets created will be the same throughout your entire stay on the M8 using TWRP, it will never change (well that phone anyway, if you get a refurb or w.e. obv it will be different, but that phones folder markers will never change within TWRP, so it's to your benefit to have this backed up and ready to go...)
Click to expand...
Click to collapse
Tried it again and again...used a different computer and it WORKED...Thank you so much for your help andybones!
roadblock217 said:
Tried it again and again...used a different computer and it WORKED...Thank you so much for your help andybones!
Click to expand...
Click to collapse
Awesome!
Very welcome.
So what was the result fix?
Did you have to wipe Internal from system not mounting?
Or did the adb sideload work?
Also once it flashed it loaded up if you did not have to wipe Internal, was your storage still there?
Glad that your back up and running.
andybones said:
Awesome!
Very welcome.
So what was the result fix?
Did you have to wipe Internal from system not mounting?
Or did the adb sideload work?
Also once it flashed it loaded up if you did not have to wipe Internal, was your storage still there?
Glad that your back up and running.
Click to expand...
Click to collapse
I had to flash the RUU but it finally worked and was applied..I'm honestly thinking of holding off on doing more to it until I learn more!
Had to wipe pretty much all except my sd card, rebooted to bootloader and back to twrp and it allowed me to write to system. BUT I couldnt get any rom to flash (when I did, it hung on the HTC logo as usual, but the aroma installer said that it was successful..so I gave up on that and did the RUU on a different computer and its back to normal.
roadblock217 said:
I had to flash the RUU but it finally worked and was applied..I'm honestly thinking of holding off on doing more to it until I learn more!
Had to wipe pretty much all except my sd card, rebooted to bootloader and back to twrp and it allowed me to write to system. BUT I couldnt get any rom to flash (when I did, it hung on the HTC logo as usual, but the aroma installer said that it was successful..so I gave up on that and did the RUU on a different computer and its back to normal.
Click to expand...
Click to collapse
It's possible after so long you didn't give the ROM long enough to boot up?
Sounds like RUU might be a cause from flashing AOSP, threads like this are good to warn people, and for when it happens to others, they can read this and know what to do. Maybe think of a new title that could help those in a search to find this thread?
it's a pretty long story but currently my system partition is wiped after it soft bricked, i also couldn't reflash stock roms with twrp so i tried to extract the recovery.img from the stock rom and flashing it over twrp to get the original recovery mode back to flash the update but for some reason it didn't work.
so now i can only boot into EMUI which keeps telling 'getting package info failed' meaning i can't update through it. i'm also able to reach the 'fastboot&rescue mode' screen but i know nothing about adb and even tho i watched 2-3 tutorial videos i couldn't really get it to work. all videos wanted me to boot up the phone and enable usb debugging which i can't. my phone was rooted before and i'm positive i've enabled it in the past but i'm not sure if it's still enabled or not, either way i'm not able to get it working.
is this salvageable?
i'd really appreciate some help if possible, thnx
nope. but even when i had twrp it wouldnt let me flash update.zip's
i still have fastboot screen so my guess is that i have to run it through adb, which i don't know how to do
Rommco05 said:
Hm, and which is your model and last function system?
edit: u can boot to system? If good understand u can
Click to expand...
Click to collapse
last update i had working was frd-l09c432b120
can't boot system
can't boot recovery mode (twrp)
i CAN boot to 'fastboot&recovery mode'
i CAN boot to EMUI (but EMUI keeps telling me 'Getting package info failed', it tries to connect and download but from what i can tell on the screen the download never starts)
Ok. Ive tried running 'adb devices' but i cant see my device, if i type 'fastboot devices' i find one device.
Dont know if im missing something or if this even matters.
But i'll try flashing twrp with fastboot
Rommco05 said:
This is right way
edit: frp is unlocked?
edit1: you need to flash old twrp 3.0.2.0 I think is right (if was your last firmware Marshmallow
Click to expand...
Click to collapse
TWRP is back!!
but how do i flash marshmallow with twrp? and what marshmallow file are you talking about, the one i mentioned above?
because i tried flashing these update.zip's with twrp before but it wouldn't let me.
i'm currently packaging the update.app files into a zip and moving it to the sdcard, that's the only way i can think of to flash these update files with twrp.
since it didn't work last time, i have my doubts but i'll give it a try
Rommco05 said:
Ok, just for clarification, your model is frd-l09c432, right?
Click to expand...
Click to collapse
yes. can't remember how to double check but way back when i downloaded these update files i was extremely careful to download the correct files.
and they worked and been working since they were the newest version, so i guess that has to be my model.
EDIT: and it's twrp-3.1.1-0
yea now it told me corrupt zip, last time i tried i got some other error, think it was some error about writing to system partition.
U can also flash this https://drive.google.com/file/d/0BwXB-CJiljwpS1o4UXo5b1JlRjQ/view and after
Dload this link once http://www.hihonor.com/uk/support/details/index.html?DOC_ID=92101
Rommco05 said:
Ok download this firmware B120 and flash via twrp https://www.androidfilehost.com/?w=files&flid=129477 after this go to reboot and tap reboot recovery. Now you should be in stock recovery and tap factory reset and after reboot. Now you hopefully will be able boot to ROM. (If u got some errors in twrp, don't care, installation must take about with minutes)
Click to expand...
Click to collapse
there's no B120 on that site, only B101 and B131. should i take B131 instead?
Any updates for your issue OP?
Sent from my Honor 8 using XDA Labs
Rommco05 said:
Sorry so flash B131 is better then B120
Click to expand...
Click to collapse
it's up and running again thank you so much, you're a life saver. i'd actually kiss you if you were here lol
i spent a few hours yesterday trying to find zipped update files ready for flashing in twrp, like the ones you linked.
do i have to do a factory reset after that? i haven't tried everything yet but my phone looks and works as if it never even stopped working in the first place.
i'm just happy i got all my files, numbers, photos etc back...
thank you so much once again
EDIT: yea sorry for the delayed response, i had to run an errand
Wow another one rommoco05 :highfive:
Add the fixed tag to the thread OP. Enjoy the device
You both are awesome ???
Rommco05 said:
lol. No u don't need to make factory reset, phone start from like factory reset. Upgrade to Nougat . If u want kiss me, kiss thanks button you're welcome
Click to expand...
Click to collapse
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
JimZiii said:
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
Click to expand...
Click to collapse
If you synced the contacts already then you can from google contacts.
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
JimZiii said:
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
Click to expand...
Click to collapse
Flash the backup of boot files
venugopalu007 said:
Flash the backup of boot files
Click to expand...
Click to collapse
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
JimZiii said:
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
Click to expand...
Click to collapse
For apps backup just download from playstore , because some apps are compitable with mm and some are nougat .so better to download again from playstore after updating to nougat.
Rommco05 said:
Huawei backup is pretty good I start saving my SMS on P8lite and now I have +15000 SMS saved and 2 years old calls logs
Click to expand...
Click to collapse
That was huge bro
Rommco05 said:
Yes, resume SMS take about 15 minutes
Click to expand...
Click to collapse
Bro can you make a guide how to backup and restore in Huawei.
Hey folks; I'm hoping I can get some advice or pointers, or maybe just a slap upside the head with something I've missed.
I have one of the original Shield tablets, and played around with it quite a lot, installing various custom ROMs from the marvelous directions I've found here. When the battery thing happened, I submitted the required info and happily received my new tablet. The original was rooted and customised still, kill-switch averted, and I had two working tablets. I gave the new stock one to my wife.
But then, about three months ago, I was playing with mine again installing a newer ROM than the one I was using (I *think* I was going from an older Bliss rom to one of the Cyanogen), and ... Something Happened (tm). The tablet rebooted in the middle of everything, and now won't boot to an image.
I'm on Windows 10 now, and had some fun getting the drivers working, but they seem to. I can communicate with the tablet through Fastboot, but ADB doesn't see it. I've flashed several versions of TWRP to the tablet, and can boot into that recovery - both through Fastboot and the tablet's power+vol-dn buttons. I've used TWRP to flash several different ROMs, and it *appears* to work (there are no errors), but when I reboot the tablet .... nada. Nothing but the Nvidia boot screen for days.
So now... what have I missed? I'm a little reluctant to flash a stock ROM, but I'm at a loss. I used to have more time to fiddle and figure, and I'm afraid that my impatience is going to kill the thing.
Format system and data see if that works
You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk
skooter32 said:
Format system and data see if that works
Click to expand...
Click to collapse
Have done, but I'll try it again. Thanks
lafester said:
You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I've tried the latest and the not-so-latest, all with similar results.
Hnefatafl said:
I've tried the latest and the not-so-latest, all with similar results.
Click to expand...
Click to collapse
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida
Hnefatafl said:
Have done, but I'll try it again. Thanks
Click to expand...
Click to collapse
Also format data system to something other than ext4 then re format it back
skooter32 said:
Also format data system to something other than ext4 then re format it back
Click to expand...
Click to collapse
can I ask what that should bring?
wiQbold said:
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida
Click to expand...
Click to collapse
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.
Right, well it looks like I've got this thing going. I could flash TWRP 3.1.0-0, but not any 3.1.1. Cyanogenmod 12 worked. Reading up a little more (it got slow at work for a couple of days...) I flashed the firmware to 5.0, and could now install TWRP 3.1.1-1! Then I could install (in this case) Lineage 14.1, which *almost* worked. It booted, but there's no wifi.
Then I found a suggestion - I think it was on these forums somewhere - and restarted. Wiped all data again, flashed Cyanogenmod 12, no gapps. Restarted, checked everything including wifi, and is good. Rebooted back into recovery, performed a factory reset, then installed Lineage 14.1 and gapps. When it rebooted, everything is working!
So. Firmware. Huh.
Thanks all.
Hnefatafl said:
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.
Click to expand...
Click to collapse
do not know if you need the bootloader(blob) from nougat to boot up, that lafester told you. but that sounds plausible. skooter says something from re-formating. so if you tried that all and nothing changes? cache and data partition you wiped also, so it has to be work for my understanding.
went always stock, so can t help you..
but you can use recovery images > twrp > bliss/linage. no need to boot up stock?
wiQbold said:
can I ask what that should bring?
Click to expand...
Click to collapse
I have had similar issues and I tried everything even this plus what harm is it going to be and as the fellow below said if ur in fastboot and recovery with no issues then surely u should be flashing stick to fix Ur problem ?
Let me preface this by saying I'm an idiot, I know just enough to be dangerous. Rooted and I wanted to restore and relock the bootloader. Instead of flashing the factory image first, I skipped that step and relocked the bootloader thinking it would wipe everything anyway. Of course now I realize I'm an idiot and I should not have skipped that step. Now I am soft bricked in the bootloader, and nothing will flash properly. Pretty sure I damaged the bootloader.
So my plea for help is, is there any way to repair or restore the bootloader?
I'm pretty sure as long as you can get into fastboot you can run the flash all bat.
You will have to download and extract the full factory image tho...and it should be like starting from fresh.oem
Also if you just wanted to flash a new bootloader you would just have to make sure it was the one extracted from the factory image you were already on.
noXcape said:
I'm pretty sure as long as you can get into fastboot you can run the flash all bat.
You will have to download and extract the full factory image tho...and it should be like starting from fresh.oem
Also if you just wanted to flash a new bootloader you would just have to make sure it was the one extracted from the factory image you were already on.
Click to expand...
Click to collapse
Well I've tried flash-all multiple times, it runs almost as normal except for one fail in the script (I'll show a pic of that after I go home and try again), and finishes as though it worked but when it reboots it can't get past bootloader. I'll try flashing the bootloader separately too.
Plus whenever I lock or unlock bootloader now it goes through the motion and then says "locked" or "unlocked" but it's faster than it should be and doesn't do that wiping animation at all.
Might be time to delete the old factory images and redownload new stuff
noXcape said:
Might be time to delete the old factory images and redownload new stuff
Click to expand...
Click to collapse
Already using the most recent, been playing around with that twrp beta, magisk, and v4a
Are you on current fastboot/adb?
cntryby429 said:
Are you on current fastboot/adb?
Click to expand...
Click to collapse
I think so, I downloaded it fresh a few weeks ago
trhacker01 said:
I think so, I downloaded it fresh a few weeks ago
Click to expand...
Click to collapse
Check again, I think a new version (late October) is in the most recent package.
I ran into the "stuck in bootloader" issue earlier today after running flash-all, but got out of it using some script by someone named Deuce that flashes the images one by one. I'll try and find a link.
Edit: here it is. This worked for me. Read carefully - you have to unzip the factory image that you've downloaded, then unzip the zip file that's in THAT zip.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
JayBlack_686 said:
Check again, I think a new version (late October) is in the most recent package.
I ran into the "stuck in bootloader" issue earlier today after running flash-all, but got out of it using some script by someone named Deuce that flashes the images one by one. I'll try and find a link.
Edit: here it is. This worked for me. Read carefully - you have to unzip the factory image that you've downloaded, then unzip the zip file that's in THAT zip.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Trying this now but still not working for me. Everytime where it fails is writing the bootloader, and everything else works fine. The bootloader writing fails in this deuce script, the regular flash-all, and flashing the bootloader separately.
Attached pics, 2 during deuce script, one during flash-all, and one during separate bootloader flash.
trhacker01 said:
Trying this now but still not working for me. Everytime where it fails is writing the bootloader, and everything else works fine. The bootloader writing fails in this deuce script, the regular flash-all, and flashing the bootloader separately.
Attached pics, 2 during deuce script, one during flash-all, and one during separate bootloader flash.
Click to expand...
Click to collapse
Sorry to hear that. I also got a bunch of failures during the process, and I don't think it automatically rebooted at the end of the process, but it ended up working on the first try (I was shocked when it did, since I saw so many failure warnings). He says in the thread that if it doesn't work, try formatting user data when prompted...I didn't have to, but may be worth a try, since you expected everything to be wiped anyway. Good luck.
trhacker01 said:
Trying this now but still not working for me. Everytime where it fails is writing the bootloader, and everything else works fine. The bootloader writing fails in this deuce script, the regular flash-all, and flashing the bootloader separately.
Attached pics, 2 during deuce script, one during flash-all, and one during separate bootloader flash.
Click to expand...
Click to collapse
A locked boot loader means you can't flash anything, that's the point. You can still flash an OTA.zip if you can get into stock recovery (you can still side load it in stock recovery I believe). Otherwise, you'll need to unlock the boot loader, and if it won't, and you can't get into Android to allow unlocking, then I'm not sure what, if anything, you can do.
Sent from my Pixel 2 using Tapatalk
danaff37 said:
A locked boot loader means you can't flash anything, that's the point. You can still flash an OTA.zip if you can get into stock recovery (you can still side load it in stock recovery I believe). Otherwise, you'll need to unlock the boot loader, and if it won't, and you can't get into Android to allow unlocking, then I'm not sure what, if anything, you can do.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Exactly.
At this point I'd try sideloading the latest ota.zip. If that doesn't work, I'd consider calling support and telling them your phone won't boot, without mentioning how you got there.
foosion said:
Exactly.
At this point I'd try sideloading the latest ota.zip. If that doesn't work, I'd consider calling support and telling them your phone won't boot, without mentioning how you got there.
Click to expand...
Click to collapse
yeah, good point. If I remember correctly, the Deuce script prompts you to unlock the bootloader at the beginning of the process - have you done that?
JayBlack_686 said:
yeah, good point. If I remember correctly, the Deuce script prompts you to unlock the bootloader at the beginning of the process - have you done that?
Click to expand...
Click to collapse
Yes, it's unlocked whenever trying to flash deuce or anything else. That's one of the strange things actually, it will respond to locking and unlocking, but it goes too quickly, skipping the process of wiping. Yeah I think I might be out of luck on this one.
JayBlack_686 said:
Sorry to hear that. I also got a bunch of failures during the process, and I don't think it automatically rebooted at the end of the process, but it ended up working on the first try (I was shocked when it did, since I saw so many failure warnings). He says in the thread that if it doesn't work, try formatting user data when prompted...I didn't have to, but may be worth a try, since you expected everything to be wiped anyway. Good luck.
Click to expand...
Click to collapse
Yeah I formatted to no avail.
Btw I ran out of my daily thanks, I'll continue as I get more. Thank you all very much for bothering to help me with this!