Hi guys, I'm facing a problem with my OPO. Last week I lost my Idea, Wi-Fi and mobile network but yesterday I managed to restore them. The problem is that now I'm on oxygen os and when I try to change rom (like nightly or cos 12), my phone get stuck in bootloop. I've tried to flash via twrp and via fastboot. What can I do to solve this problem?
Thanks in advance
Exactly what have you flashed with fastboot?
Solid-Dado said:
Hi guys, I'm facing a problem with my OPO. Last week I lost my Idea, Wi-Fi and mobile network but yesterday I managed to restore them. The problem is that now I'm on oxygen os and when I try to change rom (like nightly or cos 12), my phone get stuck in bootloop. I've tried to flash via twrp and via fastboot. What can I do to solve this problem?
Thanks in advance
Click to expand...
Click to collapse
Do a full wipe in TWRP (make sure it's TWRP and not OxygenOS's recovery) and you're good to go ahead and flash other ROM
Bobbi lim said:
Do a full wipe in TWRP (make sure it's TWRP and not OxygenOS's recovery) and you're good to go ahead and flash other ROM
Click to expand...
Click to collapse
That isn't the best option, the best option is using fastboot to flash the stock images. Especially considering the IMEI issues he's had, and the issues with ROMs not booting.
Heisenberg said:
That isn't the best option, the best option is using fastboot to flash the stock images. Especially considering the IMEI issues he's had, and the issues with ROMs not booting.
Click to expand...
Click to collapse
Yes I did thought of that but I took into consideration that he might have some data (like pictures) that are important to him so the best way is to at least get the phone up and running before I recommend a fastboot wipe with factory images.
Sent from my Nexus 7 using Tapatalk
Bobbi lim said:
Yes I did thought of that but I took into consideration that he might have some data (like pictures) that are important to him so the best way is to at least get the phone up and running before I recommend a fastboot wipe with factory images.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
His data is perfectly safe, I'd just advise him not to flash the userdata.img and his internal storage won't be wiped. No doubt about it, the right option for him is flashing the stock images.
Heisenberg said:
His data is perfectly safe, I'd just advise him not to flash the userdata.img and his internal storage won't be wiped. No doubt about it, the right option for him is flashing the stock images.
Click to expand...
Click to collapse
The last time I got into a similar situation as him, I didn't flash userdata.IMG but everything wouldn't boot so I tried out flashing another ROM, extract out all the data and used factory images. But no point debating on which method works. Since we both have the common goal of helping the user get his phone working again but to each his own I would say regarding how to address this issue and I respect your opinions [emoji106]
Sent from my Nexus 7 using Tapatalk
Bobbi lim said:
The last time I got into a similar situation as him, I didn't flash userdata.IMG but everything wouldn't boot so I tried out flashing another ROM, extract out all the data and used factory images. But no point debating on which method works. Since we both have the common goal of helping the user get his phone working again but to each his own I would say regarding how to address this issue and I respect your opinions [emoji106]
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It isn't really a matter of opinion though. In a situation like this where the user is experiencing compounded problems, the only way to wipe the slate clean and start fresh (so any errors are removed) is by flashing the stock images. And your own experience isn't necessarily the best benchmark because I've guided dozens of people through flashing the stock images and not a single one has had an issue like you had.
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 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.
May have messed up .....
Stock N5 unrooted and locked.
Was on 5.01 and did a simple factory reset. This ended up with "erasing" hanging for several hours.
Managed to get to fastboot. Any attempt to reboot ended up hanging on "erasing".
Managed to unlock the phone through adb.
Think I managed to install TWRP - it worked once and booted the phone up perfectly (note i still hadnt rooted at this point).
Today, random reboot and it spends ages on the Google wording before going into a boot look with the swirling colours playing.
Got home, put it back into fastboot and (think) managed to root using a one-click tool. TWRP no longer appears and I seem to have stock recovery that I can access but get loads of "cant mount"/"cant open" type messages. ive tried flashing twrp and CWM via ADB and it says successful (takes under a second ?) but neither seem to be present on a reboot ?
How bad have i messed up ??
anyone help ?
Try flashing factory image again and wipe every damn thing before doing that and dont lock the bootloader
again!
bhavstech said:
Try flashing factory image again and wipe every damn thing before doing that and dont lock the bootloader
again!
Click to expand...
Click to collapse
will the factory image include a recovery ? or do i need to do that separately ?
wilbur-force said:
will the factory image include a recovery ? Or do i need to do that separately ?
Click to expand...
Click to collapse
factory image includes everything you dont need to do that seperately!
And don't use a toolkit!
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
bhavstech said:
factory image includes everything you dont need to do that seperately!
Click to expand...
Click to collapse
OK. so i flashed the image and everything worked OK except the recovery which failed ??
wilbur-force said:
OK. so i flashed the image and everything worked OK except the recovery which failed ??
Click to expand...
Click to collapse
the radio flash failed too
"remote flash wipe failure"
It sounds like the first time in bootloader you must have used "fastboot boot recovery..." instead of "fastboot flash recovery..."
Are u using a Windows or Linux pc? If Linux, open a terminal and cd to the directory u downloaded the stock image to, connect ur phone the pc and type "adb reboot bootloader" when the phone reboots type "./flash-all.sh" that should wipe the phone and fix ur issue, it'll flash everything, recovery, rom, radio, and user data
wilbur-force said:
the radio flash failed too
"remote flash wipe failure"
Click to expand...
Click to collapse
did you use flash all.bat or u flash each and everything manually?
Ben36 said:
And don't use a toolkit!
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
Is there a reason you advise against a toolkit? Just curious, since I rely on one heavily and am wondering if it's going to cause problems down the road.
jason.larkin said:
Is there a reason you advise against a toolkit? Just curious, since I rely on one heavily and am wondering if it's going to cause problems down the road.
Click to expand...
Click to collapse
Because if you had read the thread on fastboot you wouldn't be making this post right now. My advice is go read it thoroughly. Don't worry. It's far far easier than it first looks. I remember first reading a post about it years ago thinking omg my brain is going to explode! But just follow the instructions and once you've used it once you'll think wow that was easy and never use a toolkit again
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Ben36 said:
Because if you had read the thread on fastboot you wouldn't be making this post right now. My advice is go read it thoroughly. Don't worry. It's far far easier than it first looks. I remember first reading a post about it years ago thinking omg my brain is going to explode! But just follow the instructions and once you've used it once you'll think wow that was easy and never use a toolkit again
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
I did read that thread....a year ago when I used to do all this manually. Since I discovered the toolkit I haven't had a reason to. Was just curious if there was a technical reason for it or just personal preference.
Flashed the latest RUU from HERE, and it boots into the OS perfectly.
Then, flashed Stock GPE from HERE and also tried LolliGPE from HERE. Both will not get past the boot screen, after waiting over 30min's.
In attempts to fix, the latest full firmware, TWRP, full wipe/dirty wipe, and DH's 5.1 firmware have been flashed, then the custom ROM's flashed again followed. Same issue is persists. Each time, trying to flash the RUU back, boots without issue.
Prior to flashing the latest RUU (hboot method, 0P6BIMG.zip), I have ran all the ROM's mentioned and others without issue.
I'm at a loss of what to try next, or why it's hanging. Right now, i'm leaving it for hours at the boot screen, but I doubt this is going to cure anything and only provide a hot phone during the whole time.
The phone is unlocked, S-OFF, and SuperCID.
Any suggestions i'm willing to try.
Update:
Woke up 6+ hours later, and it was still stuck on the boot screen.
Flashed the latest Fluent ROM found HERE, and it boots fine. Then did a full wipe (Cache, Dalvik Cache, Data, System), then the standalone data wipe, and factory reset. Installed GPE from HERE, and it stuck on the boot screen again after waiting 20min's...
Next step i'm going to try is 4.4.4 RUU, then full latest OEM firmware. If GPE doesn't boot still, i'll try DH's 5.1 firmware.
Still has the same problem.
I have no idea what else to try. Wish I never flashed that damn RUU file!
kcasner said:
Still has the same problem.
I have no idea what else to try. Wish I never flashed that damn RUU file!
Click to expand...
Click to collapse
The stock secure boot.img is probably what's causing you issues.
Choose a Rom, take it's boot.img and fastboot flash it.
fastboot flash boot boot.img
Then flash the Rom.
Profit...!?
Sent from my HTC6525LVW using Tapatalk
santod040 said:
The stock secure boot.img is probably what's causing you issues.
Choose a Rom, take it's boot.img and fastboot flash it.
fastboot flash boot boot.img
Then flash the Rom.
Profit...!?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
That was exactly it, what a relief. Thank you!
kcasner said:
That was exactly it, what a relief. Thank you!
Click to expand...
Click to collapse
Run files are not to blame or the problem. In fact, if you simply flash a full ruu file your phone would boot up fine.
Sent from my Nexus 6 using Tapatalk
dottat said:
Run files are not to blame or the problem. In fact, if you simply flash a full ruu file your phone would boot up fine.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That's what I said in the first post/sentence. The boot.img in the RUU was the root cause for other ROM's not booting. This was verified 3x with identical results.
santod040 was spot on :good:
kcasner said:
That's what I said in the first post/sentence. The boot.img in the RUU was the root cause for other ROM's not booting. This was verified 3x with identical results.
santod040 was spot on :good:
Click to expand...
Click to collapse
I don't think you follow me.
The ruu is the same as stock.
Do you recall having to manually flash an insecure boot img before you flashed your first custom rom?
It's no different.
Sent from my Nexus 6 using Tapatalk
dottat said:
I don't think you follow me.
The ruu is the same as stock.
Do you recall having to manually flash an insecure boot img before you flashed your first custom rom?
It's no different.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Honestly can't recall. I follow; we're on the same page, different lingo.
kcasner said:
Honestly can't recall. I follow; we're on the same page, different lingo.
Click to expand...
Click to collapse
kcasner, I had exactly same issue as you. Could you explain a bit detail on how you get it fixed?
I want to flash DH5.1. Are these correct steps I should following:
1) open DH5.1 zip file, find the boot.img (I found there're two boot.img, stock/boot.img and elite/boot.img, I guess I should use later one)
2) fastboot flash the boot.img
3) boot into recovery to flash DH5.1
4) reboot
Thanks for help!
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 ?