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
So, I got my Photon Q today and I've already unlocked it and I was trying to install TWRP but I messed up somehow.. It still boots into the stock Android ROM and works fine but whenever I try to go into the recovery/Fastboot (Whatever it's called) I get this screen with some info text. At the bottom it says this:
Failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
Whenever I try to flash a recovery with an app it always succeeds but I still get this screen when I try to go into the recovery. Help me.
Have you tried doing 'fastboot flash recovery recovery.img' instead of using 'apps' to flash recovery?
arrrghhh said:
Have you tried doing 'fastboot flash recovery recovery.img' instead of using 'apps' to flash recovery?
Click to expand...
Click to collapse
I have. It says "Preflash validation failed" and nothing on the phone changes. This is really frustrating.
Cwazywazy said:
I have. It says "Preflash validation failed" and nothing on the phone changes. This is really frustrating.
Click to expand...
Click to collapse
Where do you get this error? I've never heard of fastboot spitting out such an error...
I assume you're in fastboot mode when you try this? What does 'fastboot devices' output?
arrrghhh said:
Where do you get this error? I've never heard of fastboot spitting out such an error...
I assume you're in fastboot mode when you try this? What does 'fastboot devices' output?
Click to expand...
Click to collapse
Nevermind, I figured out how to unlock the bootloader and TWRP finally installed successfully.
The only rooting/custom ROM stuff I've done is with my Nexus 7 and that wasn't as hard as this was.
Cwazywazy said:
Nevermind, I figured out how to unlock the bootloader and TWRP finally installed successfully.
The only rooting/custom ROM stuff I've done is with my Nexus 7 and that wasn't as hard as this was.
Click to expand...
Click to collapse
Oh, your bootloader was still locked...
That would do it! Glad you got it working. I hadn't seen that message before, but it makes sense now why I've never seen it before . My Q was unlocked immediately after unboxing!
arrrghhh said:
Oh, your bootloader was still locked...
That would do it! Glad you got it working. I hadn't seen that message before, but it makes sense now why I've never seen it before . My Q was unlocked immediately after unboxing!
Click to expand...
Click to collapse
I have a new problem.. I flashed the latest stable CyanogenMod and it wouldn't boot. (Boot animation just kept on going) So I went into TWRP and tried to do a wipe. For some reason it says "Unable to mount /data" or "internal storage". Even if I go into advanced wipe and choose everything but the external SD card it fails to mount any of it..
Cwazywazy said:
I have a new problem.. I flashed the latest stable CyanogenMod and it wouldn't boot. (Boot animation just kept on going) So I went into TWRP and tried to do a wipe. For some reason it says "Unable to mount /data" or "internal storage". Even if I go into advanced wipe and choose everything but the external SD card it fails to mount any of it..
Click to expand...
Click to collapse
I've heard of other people complaining about this on TWRP.
You should either a) use OpenRecovery or another recovery... or b) use an older version of TWRP. I'm on 2.6.3.1 and it works _flawlessly_.
I haven't had time to update to the latest versions of TWRP to investigate this issue.
As for your CM issue, make sure you wipe (using a recovery that works haha) and also make sure you give it plenty of time to do the first boot - there is sometimes a fsck process which runs at boot and takes a lot longer than usual for the device to actually boot up.
Please help me. I can't find any solution and I can't boot into CMod.
Cwazywazy said:
Please help me. I can't find any solution and I can't boot into CMod.
Click to expand...
Click to collapse
I gave you a solution, please at least try it.
arrrghhh said:
I gave you a solution, please at least try it.
Click to expand...
Click to collapse
Oh. I didn't see that, sorry. Trying it now.
arrrghhh said:
I gave you a solution, please at least try it.
Click to expand...
Click to collapse
Nope. Didn't work. Gave CM about 30 minutes to boot with no luck.
Cwazywazy said:
Nope. Didn't work. Gave CM about 30 minutes to boot with no luck.
Click to expand...
Click to collapse
Without logs I don't know what the issue would possibly be...
I would suggest trying CM10.2 perhaps? Or pull logs (adb logcat) from the failed boot of CM11. Like I said, that fsck process can take a very long time. I haven't personally experienced it, but I recall hearing reports of it taking upwards of an hour - either way, without logs, we don't really know what is going on.
arrrghhh said:
Without logs I don't know what the issue would possibly be...
I would suggest trying CM10.2 perhaps? Or pull logs (adb logcat) from the failed boot of CM11. Like I said, that fsck process can take a very long time. I haven't personally experienced it, but I recall hearing reports of it taking upwards of an hour - either way, without logs, we don't really know what is going on.
Click to expand...
Click to collapse
Here you go. Thanks for trying to help me (I zipped the file so I could use the uploader.)
Cwazywazy said:
Here you go. Thanks for trying to help me (I zipped the file so I could use the uploader.)
Click to expand...
Click to collapse
Not what I was expecting, but this does show an issue with recovery... What is the issue, I am a bit baffled by. I was hoping for a logcat from the CM11 failed boot.
Can you try another recovery? TWRP seems to be failing all over the place for you, even the version that is working fine for me
TWRP is failing to mount a lot of partitions, which is obviously unacceptable. I'm still not sure why the older version wouldn't work for you...
arrrghhh said:
Not what I was expecting, but this does show an issue with recovery... What is the issue, I am a bit baffled by.
Can you try another recovery? TWRP seems to be failing all over the place for you, even the version that is working fine for me
Click to expand...
Click to collapse
I don't know, I tried Clockwork mod which had the same problems. Are there any others I can try?
I was an idiot and I forgot to back up the stock ROM before I flashed CMod..
Cwazywazy said:
I don't know, I tried Clockwork mod which had the same problems. Are there any others I can try?
I was an idiot and I forgot to back up the stock ROM before I flashed CMod..
Click to expand...
Click to collapse
OpenRecovery?
arrrghhh said:
OpenRecovery?
Click to expand...
Click to collapse
I downloaded TWRP from here: http://goo.im/devs/OpenRecovery/asanti which has OpenRecovery in the name so I dunno...
Cwazywazy said:
I downloaded TWRP from here: http://goo.im/devs/OpenRecovery/asanti which has OpenRecovery in the name so I dunno...
Click to expand...
Click to collapse
No, not TWRP... OpenRecovery.
[25-11-2013] Photon Q Open Recovery 2.09
The links may not work in the OP, see here.
It's similar to CWM, but made specifically for the Q. Doesn't seem to have issues like TWRP, as it hasn't been updated in a while and it "just works". I'm still trying to sort out the issues with TWRP, why they affect some devices but not all.
arrrghhh said:
No, not TWRP... OpenRecovery.
[25-11-2013] Photon Q Open Recovery 2.09
The links may not work in the OP, see here.
It's similar to CWM, but made specifically for the Q. Doesn't seem to have issues like TWRP, as it hasn't been updated in a while and it "just works". I'm still trying to sort out the issues with TWRP, why they affect some devices but not all.
Click to expand...
Click to collapse
Ugh. Not working.
It says failed to mount /whatever (Invalid argument)
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 ?
Hi, just tried to do this by flashing the old zip trough TWRP, but i always end to boot in recovery, maybe i'm doing something wrong...?
I tried this today and happened the same, i guess you have to clean flash to downgrade.
Also a tip, if you got stuck in recovery and yet cannot decrypt (doesn't ask for password/pin in TWRP), boot to fastboot mode, use the command "fastboot boot <the img file name for twrp>" so that you can boot directly to the img file from your PC. This way it will ask for your password.
Killua96 said:
Hi, just tried to do this by flashing the old zip trough TWRP, but i always end to boot in recovery, maybe i'm doing something wrong...?
Click to expand...
Click to collapse
You might try flashing again when you get booted back to TWRP. That way, you can get 9.01 flashed to both slots if it's not already. No guarantees, but it's worth a try.
maigre said:
You might try flashing again when you get booted back to TWRP. That way, you can get 9.01 flashed to both slots if it's not already. No guarantees, but it's worth a try.
Click to expand...
Click to collapse
I tried this way too but keep getting booted back to TWRP. Even did a wipe of the caches, system and data (not internal storage).
Is there anything I can still try?
jiatern said:
I tried this way too but keep getting booted back to TWRP. Even did a wipe of the caches, system and data (not internal storage).
Is there anything I can still try?
Click to expand...
Click to collapse
Flash Magisk again.
maigre said:
Flash Magisk again.
Click to expand...
Click to collapse
I did as well but it didn't help. Still the same.
jiatern said:
I did as well but it didn't help. Still the same.
Click to expand...
Click to collapse
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Killua96 said:
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Click to expand...
Click to collapse
Why horrible?
PuCiNhOOO said:
Why horrible?
Click to expand...
Click to collapse
Keyboard continuously crash 'cause the new gesture system, that have longer animations and the recent app one loses the vibration feedback and it' s also a lot confusing.
Anyway you can read the same things in the ota's thread, unfortunately are widespread problems
Killua96 said:
Keyboard continuously crash 'cause the new gesture system, that have longer animations and the recent app one loses the vibration feedback and it' s also a lot confusing.
Anyway you can read the same things in the ota's thread, unfortunately are widespread problems
Click to expand...
Click to collapse
I think they pushed the update too fast from beta to stable... But yes, agree with the gestures bug... Its a fact, but the other stuff is good
Killua96 said:
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Click to expand...
Click to collapse
Can you link me to the exact fastboot rom you flashed? Some said I have to use the downgrade zip from OnePlus to Oreo 5.1.1 then only upgrade to 9.0.1. The OP of the fastboot rom said the rom is not for downgrading.
Did you downgrade to Oreo first or directly flash the 9.0.1 fastboot rom?
jiatern said:
Can you link me to the exact fastboot rom you flashed? Some said I have to use the downgrade zip from OnePlus to Oreo 5.1.1 then only upgrade to 9.0.1. The OP of the fastboot rom said the rom is not for downgrading.
Did you downgrade to Oreo first or directly flash the 9.0.1 fastboot rom?
Click to expand...
Click to collapse
I've wiped everything, then downgraded to Pie directly, but I was in a slightly different situation (only fastboot available).
Just to be sure flash the Oreo one and then upgrade to Pie.
With the whole A/B partition layout it should be easier to downgrade too right?
Hey Guys,
I got a new OP8T and wanted to install LineageOS 19.1 (First time doing something like this, so this might be a dumb question).
before doing anything, I updated OOS to the latest version using the internal update. I then unlocked the bootloader and flashed the latest LOS recovery. After flashing the LOS recovery, my phone goes into a boot loop whenever I try to boot it, after 4-5 loops, it boots into the stock recovery.
I can access fastboot mode though. Does anyone have an idea how I can fix this or what I might have done wrong?
In the recovery I have the option "format data". Might that do a factory reset?
Or should I go into fastboot and try flashing the recovery again?
I also thought about flashing Android 12 OOS from: https://forum.xda-developers.com/t/rom-official-kebab-12-lineageos-19.4484387/page-2#post-87339737
I'm a little afraid to completely bricking the phone now by doing something stupid.
Edit: Tried to "format data". No real changes. Can still boot into recovery and fastboot.
Another thought I had, was that now, after factory resetting, the phone might be back to Android 11, so maybe I could try to flash TWRP for Android 11 and then LineageOS 18.1?
What are your thoughts?
Edit: Forgot to flash the vbmeta.img and dtbo.img partitions.
Flashing them and then flash the recovery again resolved the issue
A factory reset does not downgrade your OS version. Did you flash the dtbo and vbmeta partitions before flashing LOS recovery?
henschn3435 said:
Hey Guys,
I got a new OP8T and wanted to install LineageOS 19.1 (First time doing something like this, so this might be a dumb question).
before doing anything, I updated OOS to the latest version using the internal update. I then unlocked the bootloader and flashed the latest LOS recovery. After flashing the LOS recovery, my phone goes into a boot loop whenever I try to boot it, after 4-5 loops, it boots into the stock recovery.
I can access fastboot mode though. Does anyone have an idea how I can fix this or what I might have done wrong?
In the recovery I have the option "format data". Might that do a factory reset?
Or should I go into fastboot and try flashing the recovery again?
I also thought about flashing Android 12 OOS from: https://forum.xda-developers.com/t/rom-official-kebab-12-lineageos-19.4484387/page-2#post-87339737
I'm a little afraid to completely bricking the phone now by doing something stupid.
Edit: Tried to "format data". No real changes. Can still boot into recovery and fastboot.
Another thought I had, was that now, after factory resetting, the phone might be back to Android 11, so maybe I could try to flash TWRP for Android 11 and then LineageOS 18.1?
What are your thoughts?
Click to expand...
Click to collapse
It's a good thing to look through the official thread before flashing anything.
[ROM][OFFICIAL][kebab][12] LineageOS 19
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
TheNewHEROBRINE said:
A factory reset does not downgrade your OS version. Did you flash the dtbo and vbmeta partitions before flashing LOS recovery?
Click to expand...
Click to collapse
No, I didn't. That was definitely the mistake! I feel pretty stupid right now.... Oh well...
Can I do that now and then flash the recovery again? Thank you!
henschn3435 said:
No, I didn't. That was definitely the mistake! I feel pretty stupid right now.... Oh well...
Can I do that now and then flash the recovery again? Thank you!
Click to expand...
Click to collapse
You can try but I can't assure that it will work.
TheNewHEROBRINE said:
You can try but I can't assure that it will work.
Click to expand...
Click to collapse
Do you have any other idea what I could do?
I thought about using the msm tool to reset the device completely, but that seems kinda drastic...
henschn3435 said:
Do you have any other idea what I could do?
I thought about using the msm tool to reset the device completely, but that seems kinda drastic...
Click to expand...
Click to collapse
What I would do is go into fastboot and flash dtbo, vbmeta and recovery downloaded from here, then reboot into recovery directly from the bootloader menu.
TheNewHEROBRINE said:
What I would do is go into fastboot and flash dtbo, vbmeta and recovery downloaded from here, then reboot into recovery directly from the bootloader menu.
Click to expand...
Click to collapse
Is that the same as the most recent recovery and LOS from LOS official download page?
Anyway you're a huge help! Thank you so much!
The file name is identical so I suppose they are the same. I found the link in the official guide.
TheNewHEROBRINE said:
The file name is identical so I suppose they are the same. I found the link in the official guide.
Click to expand...
Click to collapse
I'll go ahead and try it first thing tomorrow morning
Don't be too anxious about "completely bricking" your phone if you're just trying to upgrade and then flash Lineage. Don't rush, try some things that make sense based on your understanding of the correct procedure, and make a brief note of each step you took to help you later on if things don't work as expected. I've made lots of mistakes ending in boot loops and crash dumps, sometimes by accident and sometimes intentionally, and there's always a way to get out of it unless you do something really out of the ordinary. Keep your mind engaged and you'll have many "Ah-ha!" moments along the way. Don't give up and ask carefully worded questions when you get stuck. It may take a bit longer to get the job done than you expected but it will all work out in the end.
Flashing the partitions and the reflashing the recovery worked! Thank you all for the help!