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
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
jimburke57 said:
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
Click to expand...
Click to collapse
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Zepius said:
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Click to expand...
Click to collapse
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
jimburke57 said:
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
Click to expand...
Click to collapse
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Zepius said:
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Click to expand...
Click to collapse
I have followed it already. The images on the first post are my result.
It is showing as unlocked at the booloader and on fastboot oem device-info.
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Zepius said:
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Same thing as before. All of the erase commands get processed, but when it gets the the system.img it fails to write it.
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
jd1639 said:
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
Click to expand...
Click to collapse
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
jimburke57 said:
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
Click to expand...
Click to collapse
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
orangekid said:
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
Click to expand...
Click to collapse
Are you talking about these drivers?
jimburke57 said:
Are you talking about these drivers?
Click to expand...
Click to collapse
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
orangekid said:
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
Click to expand...
Click to collapse
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
jimburke57 said:
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
Click to expand...
Click to collapse
Have you tried flashing stock kitkat (from google) via fastboot?
orangekid said:
Have you tried flashing stock kitkat (from google) via fastboot?
Click to expand...
Click to collapse
yes, many times
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
pantlessjim said:
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
Click to expand...
Click to collapse
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Here is some additional information. When I perform a factory reset in recovery it freezes while formatting /data. And when flashing the stock images, I am able to flash everything successfully except for the system.img
jimburke57 said:
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Click to expand...
Click to collapse
Have you tried just dirty flashing stock / rooted thru recovery?
edit: or restoring a backup?
I tried flashing the Franco kernel for N4 on my N5 by mistake...now my phone gets stuck on the black reboot screen.
How can I fix this?
Using TWRP.
woowhee said:
I tried flashing the Franco kernel for N4 on my N5 by mistake...now my phone gets stuck on the black reboot screen.
How can I fix this?
Using TWRP.
Click to expand...
Click to collapse
you might not be able to fix it. flashing a kernel meant for a different device can vary easily brick any device.
1. if you can get into your recovery, try flashing the right kernel, even an older version if possible.
2. if that doesnt work, flaah the factory img via fastboot and hope for the best.
3. if still no luck, theres a nexus 4 thread in their general section meant just for accidents like this, find it and try what it says.
simms22 said:
you might not be able to fix it. flashing a kernel meant for a different device can vary easily brick any device.
1. if you can get into your recovery, try flashing the right kernel, even an older version if possible.
2. if that doesnt work, flaah the factory img via fastboot and hope for the best.
3. if still no luck, theres a nexus 4 thread in their general section meant just for accidents like this, find it and try what it says.
Click to expand...
Click to collapse
Is there a way to get the factory img onto the phone via TWRP?
Does the bootloader still work?
BirchBarlow said:
Does the bootloader still work?
Click to expand...
Click to collapse
Yes, I'm able to get into TWRP/recovery mode.
woowhee said:
Yes, I'm able to get into TWRP/recovery mode.
Click to expand...
Click to collapse
Then, you are fine, friend:victory:, just do what the guy upstairs said. (simms22)
wipe system, caches, Flash another Rom/kernel for N5
Fastboot flash /boot boot.img
Sent from my Nexus 5 using XDA Premium 4 mobile app
woowhee said:
Yes, I'm able to get into TWRP/recovery mode.
Click to expand...
Click to collapse
Then what's the problem?
He's safe. He just needs to flash using fastboot.
This is the reason why Nexus devices are awesome.:angel:
woowhee said:
I tried flashing the Franco kernel for N4 on my N5 by mistake...now my phone gets stuck on the black reboot screen.
How can I fix this?
Using TWRP.
Click to expand...
Click to collapse
You can solve flashing a wrong kernel, but don`t ever flash a N4 bootloader or you are definately screwed. Get rid of anything N4 related from your fastboot folder bro..
The point in the bootloader is for this very thing. Just plug it into your pc and fastboot it
Unless you have a kernel/ rom zip or backup already in the memory then just use recovery
Sent from my Nexus 5 using Tapatalk
gee2012 said:
You can solve flashing a wrong kernel, but don`t ever flash a N4 bootloader or you are definately screwed. Get rid of anything N4 related from your fastboot folder bro..
Click to expand...
Click to collapse
Thank you, everyone. Disaster aborted.
Hi,
My mobile data no longer works. I've done a lot of research, tried every fix, to no avail. My WiFi works, it's only my mobile data.
Things I've tried:
Following this guide: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Completely reverting to stock
Flashing a stock, rooted 44S + radio files
Flashing ColorOS, and then flashing CM11S using this guide: http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Sticking the SIM card in my Galaxy S3 to see if it works (spoiler: it does)
Restoring previous nandroid while data was working fine
Under ColorOS, I have a notification that says "The NV partition is invalid!". Just thought I'd mention that.
Stupid me didn't backup my EFS. No APNs, unknown IMEI, unknown baseband, etc.
I'm at a loss guys. I'd greatly appreciate your help.
Thanks,
Niko
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
timmaaa said:
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
Click to expand...
Click to collapse
Yup. Sadly didn't work.
You might be outta luck then, the methods you've mentioned above are the only ones that I know of that work. Let this be a lesson to anyone reading, backup your EFS. DO IT.
Transmitted via Bacon
timmaaa said:
You might be outta luck then, the methods you've mentioned above are the only ones that I know of that work. Let this be a lesson to anyone reading, backup your EFS. DO IT.
Transmitted via Bacon
Click to expand...
Click to collapse
You think it would be worth trying to get a new sim card from my carrier?
It isn't the SIM that's the problem, your EFS partition is corrupt.
Transmitted via Bacon
If my EFS partition was corrupt, why does my Wifi work?
That's normal.
Transmitted via Bacon
I FIXED IT! This is exactly what I did.
* Flash ColorOS from this post: https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/
* Download and install OTA updates for ColorOS
* Flash back TWRP
* Flash 44S (Pre-Rooted)
* Boot up phone without SIM in (at this point I checked the settings and to my joy saw that baseband wasn't unknown
* Power down, insert SIM in, reboot
NikoZBK said:
I FIXED IT! This is exactly what I did.
* Flash ColorOS from this post: https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/
* Download and install OTA updates for ColorOS
* Flash back TWRP
* Flash 44S (Pre-Rooted)
* Boot up phone without SIM in (at this point I checked the settings and to my joy saw that baseband wasn't unknown
* Power down, insert SIM in, reboot
Click to expand...
Click to collapse
Hi, have the same issue. Did you flash the ColorOS thru a recovery or thru SDK Tools? and what recovery did you use to flash if you flashed with a recovery?
grneyez said:
Hi, have the same issue. Did you flash the ColorOS thru a recovery or thru SDK Tools? and what recovery did you use to flash if you flashed with a recovery?
Click to expand...
Click to collapse
I flashed ColorOS in fastboot mode, so through SDK tools. I manually flashed every .img. In other words, I just followed the guide in the link I gave.
NikoZBK said:
I flashed ColorOS in fastboot mode, so through SDK tools. I manually flashed every .img. In other words, I just followed the guide in the link I gave.
Click to expand...
Click to collapse
I gonna give it a shot, see what happens. I'm not so good in with SDK tools.
grneyez said:
I gonna give it a shot, see what happens. I'm not so good in with SDK tools.
Click to expand...
Click to collapse
Please post back how it goes.
NikoZBK said:
Please post back how it goes.
Click to expand...
Click to collapse
I will thanks.
NikoZBK said:
Please post back how it goes.
Click to expand...
Click to collapse
Worked like a charm, thanks so much for your help.
timmaaa said:
You might be outta luck then, the methods you've mentioned above are the only ones that I know of that work. Let this be a lesson to anyone reading, backup your EFS. DO IT.
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry, bit of a noob here!
What is the EFS and how would I go about backing it up? I don't see any option for that in TWRP?
Rkr87 said:
Sorry, bit of a noob here!
What is the EFS and how would I go about backing it up? I don't see any option for that in TWRP?
Click to expand...
Click to collapse
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
NikoZBK said:
I FIXED IT! This is exactly what I did.
* Flash 44S (Pre-Rooted)
Click to expand...
Click to collapse
Could I ask you what 44S is? I get the feeling my issue with my phone might be the same as yours. You also did this for a Chinese OPO?
DGX_Goggles said:
Could I ask you what 44S is? I get the feeling my issue with my phone might be the same as yours. You also did this for a Chinese OPO?
Click to expand...
Click to collapse
44S is short for XNPH44S, which is the latest build of CM11S (the stock firmware) for this phone.
Transmitted via Bacon
DGX_Goggles said:
Could I ask you what 44S is? I get the feeling my issue with my phone might be the same as yours. You also did this for a Chinese OPO?
Click to expand...
Click to collapse
No, I did this for the global version, but the steps should work for you as well.
Keeps booting to recovery mode and I have no idea how to install stock rom again. Is there a way through fastboot? oneplus recovery doesn't let you install anything.
have u tried to sideload 5.1.5 full zip?
Bradl79 said:
have u tried to sideload 5.1.5 full zip?
Click to expand...
Click to collapse
How can I side load it? My pc only sees my phone in fastboot mode.
u said it keeps going to recovery, can u not do it via recovery?
why do people play with things they dont know?
LOL! I don't know why this was so funny to me. Basically day 1 of people getting their OnePlus 6's and already "I bricked my phone" threads popping up.
sn0warmy said:
LOL! I don't know why this was so funny to me. Basically day 1 of people getting their OnePlus 6's and already "I bricked my phone" threads popping up.
Click to expand...
Click to collapse
There's no update through recovery and haha yeah lol. I love rooting and messing with things but I'm simply a teenage novice ? So not always the best with it all. Worst comes to worst I just wait for twrp to be released and fix it from there.
Logan0829 said:
There's no update through recovery and haha yeah lol. I love rooting and messing with things but I'm simply a teenage novice So not always the best with it all. Worst comes to worst I just wait for twrp to be released and fix it from there.
Click to expand...
Click to collapse
I'm sure there's a way without TWRP. I'd try to lend a hand but I've been away from OnePlus for so long I don't know how it's different than my Pixel 2 XL.
I'd dig around the OnePlus 5T forums. software wise, it should be the same. You'll probably find a quick solution over there. Good luck!
EDIT: Now I'm curious... Does anyone know if there is a way to lash a factory Oxygen OS image through fastboot commands? That would solve your problem, but I don't know if that's something specific to Pixel devices.
I hope u unlocked ur bootloader, also how the heck did u already soft brick
see if this works
https://www.youtube.com/watch?v=GMlj7rML10o
What did you even do to soft brick it? You could try fast boot flashing the boot.img again and see if it boots, get the one from the root thread if you're on the latest Oxygen OTA.
Chris123NT said:
What did you even do to soft brick it? You could try fast boot flashing the boot.img again and see if it boots, get the one from the root thread if you're on the latest Oxygen OTA.
Click to expand...
Click to collapse
Ended up here. https://forum.xda-developers.com/on...fficial-oxygen-os-t3792244/page4#post76615579 Looks like I'm not the only one.
Logan0829 said:
Ended up here. https://forum.xda-developers.com/on...fficial-oxygen-os-t3792244/page4#post76615579 Looks like I'm not the only one.
Click to expand...
Click to collapse
Ohhh, you flashed the P dev preview. Yeah I don't dare do that until TWRP is out.
Chris123NT said:
Ohhh, you flashed the P dev preview. Yeah I don't dare do that until TWRP is out.
Click to expand...
Click to collapse
No I tried flashing all img files I could from 5.1.3 and no luck. Stuck on boot animation.
Did you try to flash stock boot img 5.1.5 in fastboot ?
EDIT : try to flash in both slots
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
SOLVED!!!!
Had to critical unlock in fastboot and restored to 5.1.3 by flashing all imgs. Then booted up and flashed from local storage 5.1.5. Phone is back up and running again ?
help me...even i soft bricked my one plus 6!
vineet allahabad said:
help me...even i soft bricked my one plus 6!
Click to expand...
Click to collapse
There is an un-brick tool for OP6
Logan0829 said:
Had to critical unlock in fastboot and restored to 5.1.3 by flashing all imgs. Then booted up and flashed from local storage 5.1.5. Phone is back up and running again
Click to expand...
Click to collapse
This is so fracking helpful post, congrats!
stavros67 said:
There is an un-brick tool for OP6
Click to expand...
Click to collapse
Can u guide me to the same same i tried finding!
vineet allahabad said:
Can u guide me to the same same i tried finding!
Click to expand...
Click to collapse
https://androidfilehost.com/?w=files&flid=271466