Related
Hi, I need the ROM for this phone, more specifically, the boot.img file, as the current kernel is for the older, Indian revision of the On5, and my revision, the USA version SM-G550T1, seems not to have any copies of its firmware floating around. I'm running an OS for the SM-G550FY, which has no audio or camera support. Even if the version isn't an exact match, if you bought this phone in the USA, new, in 2016, your boot.img will probably work. I need this kernel guys. Please, if someone has an On5 in the USA, can I please get a copy of your boot.img and possibly system.img? I really care about the boot.img.
Thanks guys
-Subsentient
Firstly, did you try the updated ones at these locations:
http://www.theandroidsoul.com/galaxy-on5-stock-firmware-2-86761/
http://firmwarefile.com/samsung-sm-g550fy
Secondly, why exactly do you need the boot.img, what problem do you think it'll solve? Is there any specific issue with your current ROM that you are trying to solve?
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Subsentient said:
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Click to expand...
Click to collapse
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
prahladyeri said:
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Subsentient said:
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Click to expand...
Click to collapse
There you are! I just cannot emphasize enough that why don't you guys backup your existing ROMs before flashing a new one? It hardly takes five minutes with CWM/TWRP recovery.
In any case, what happens when you flash the Indian ROM (5.1.1)? I guess that could be your only option.
Otherwise, you can put a request on the CyanogenMod thread for your particular Samsung model.
For future reference, perform device backups and all the research before flashing a custom ROM, not after the fact.
EDIT
If you can contact Samsung support, see if you can manage to get a stock ROM from them that you can flash using ODIN or something.
I contacted them already, they basically told me to go **** myself. The missing ROM is a result of bad parameters I accidentally put in to Heimdall/ODIN flasher. I wanted to back up, but ironically, my first attempt at installing TWRP is what destroyed my ROM.
I've downloaded the kernel source code from Samsung and I'll try compiling it myself. If I create a working boot.img, I'll post it here.
prahladyeri said:
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
boot.img is where the kernel is stored. I know, I decompressed it.
Subsentient said:
boot.img is where the kernel is stored. I know, I decompressed it.
Click to expand...
Click to collapse
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
prahladyeri said:
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
Click to expand...
Click to collapse
The kernel on this device does not have loadable module support. It's entirely monolithic. And, I'm having one hell of a time building a kernel this thing is willing to boot.
I really would love just to get a ROM from someone else's SM-G550T or SM-G550T1.
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
bandtab said:
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
Click to expand...
Click to collapse
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Subsentient said:
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Click to expand...
Click to collapse
thank you!
however, i can't install twrp to my recovery partition anymore because i got FRP locked, and i can't go into my settings to disable it now. so i think my only option really is via odin. i'll see what i can do with this though, thank you very much. i did have twrp on there before but after i got frp locked i can't go into recovery mode at all.
I've been losing my mind trying to make this work.
I think if I installed the stock recovery.img it may work, but I can't find it in the files you sent. Would you or anyone else be able to make a copy of it for me? I would be eternally indebted to whoever could.
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
holydude92 said:
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
Click to expand...
Click to collapse
unfortunately smart switch is incompatible with this model phone for the time being.
I got four of these from T-Mobile when we switched from Verizon ($120 for 4 lines). Three of our Verizon phones worked well on T-Mobile (after a few APN tweaks), but my dad's old Galaxy S3 barely worked at all, and when it did, only got Edge for data. So I set one of the On5 phones up for him.
Everything was going great. I put the TWRP recovery on it, rooted it, froze all the bloatware, and backed up/restored his apps from the old S3. However, he wanted me to see if I could restore all his SMS/MMS. I tried restoring that, and the stock Messaging app started FC'ing. I installed Textra, which worked (and saw the old messages), but he never received new texts (even though he could send). So I tried removing Messaging and Textra, as well as the SMS cache (which seemed to be in "Dialer Storage (Phone SMS/MMS). I removed it, but now I'm getting an error every five seconds about "com.android.phone" and can't seem to get rid of it. I tried to restore the dialer storage backup again, but it just seems to sit forever without installing.
I've looked far and wide for a stock ROM... hoping I could just put this mess behind me, but I'm surprised to find it is nowhere to be found.
My other alternative would be to fix the com.android.phone error, but nothing seems to fix it.
Which cynogenmod or any custom os suits for Samsung Galaxy on 5.......please tell me guys.....I am bored with this official os
I was really hoping to come back to this forum and finally see stock ODIN files for this phone. I really, really want to get rid of the MetroPCS ROM I used to fix it.
Has anyone been able to find it?
I've spent the whole night trying to figure this out, but to no avail. Here goes...
Hey guys, so I was innocently playing around with GravityBox when I restarted my phone so some new settings would kick in, and it sends me into a bootloop. I went into TWRP Recovery, and at first factory reset my phone, hoping it would solve the problem, but it didn't, so I ended up "Formatting Data", which still didn't work. I'm kind of new to this whole flashing/rooting/ business, and I was wondering how I could fix my phone. If turned on, it stays in the booting process with the golden "Axon" letters forever. The model is the US variant, it's bootloader is unlocked via the ZTE Request Form, and it currently has TWRP as it's custom recovery. Help will be much appreciated. Also, it's on OTA B20
Edit: Alright so I've tried to flash to boot.img as well as recovery.img in twrp, but both give me an error. Strangely enough, if I wait out the Axon logo for about 5 minutes, it actually boots up, but as if it was the first time turning it on (asks you to sign in to google, wi-fi setup, fingerpring setup, etc). Another thing I noticed was that it says I only have 4gb of storage, instead of the 64 it originally came with. Every time I reset it/turn it off, it makes me set up the phone again.
Edit #2: Fixed with the help of this thread http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895 Only problem seems to be that Wi-Fi does not work. /:
I had this problem and after restoring system backup in TWRP I losted my signal WiFi Imei ....
But I have 64 GB of storage again
Отправлено с моего HTC One M8 через Tapatalk
raber111 said:
I had this problem and after restoring system backup in TWRP I losted my signal WiFi Imei ....
But I have 64 GB of storage again
Отправлено с моего HTC One M8 через Tapatalk
Click to expand...
Click to collapse
I don't have a TWRP backup to restore to ): if that's what you mean, any other solutions?
I didn't have to but I found a backup on XDA . And I don't really know if you should use it or you should wait till full stock image will release.
Отправлено с моего HTC One M8 через Tapatalk
Did you happen to try the instructions to restore to stock already, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
reddrago said:
Did you happen to try the instructions to restore to stock already, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
Click to expand...
Click to collapse
I'm in the process of doing this as of right now, thank you. Will update.
It sounds like you're going to restore to stock, so perhaps this won't help at this point, but Xposed has a "safe mode" which can be activated during boot-up and perhaps help to resolve these sorts of issues...here's a thread about it:
http://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
This once saved me when I had a boot-loop issue with a tablet a while back. Good luck!
Same boat. last day or so of newegg 14 day return. At this point my decision is between Return or Replace. No ZTE image or flashable modem file means there is no fix for this, as far as I can tell.
FYI,. I have tried all of the possible fixes offered.
Barsky said:
Same boat. last day or so of newegg 14 day return. At this point my decision is between Return or Replace. No ZTE image or flashable modem file means there is no fix for this, as far as I can tell.
FYI,. I have tried all of the possible fixes offered.
Click to expand...
Click to collapse
Newegg is 30 day return.
Sent from my FRD-L04 using Tapatalk
flyer_andy said:
It sounds like you're going to restore to stock, so perhaps this won't help at this point, but Xposed has a "safe mode" which can be activated during boot-up and perhaps help to resolve these sorts of issues...here's a thread about it:
http://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
This once saved me when I had a boot-loop issue with a tablet a while back. Good luck!
Click to expand...
Click to collapse
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.
bricky23 said:
Newegg is 30 day return.
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
Try doing what this thread says, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
If you have any questions feel free to pm,
Pollito788 said:
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.
Click to expand...
Click to collapse
I'm in the exact same boat. Did you ever figure out how to get wifi back?
Pollito788 said:
Try doing what this thread says, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
If you have any questions feel free to pm,
Click to expand...
Click to collapse
Am I missing something. that dev-host site sends me exploit installers. good thing I do nightly acronis images.
Pollito788 said:
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.
Click to expand...
Click to collapse
Flapjack said:
I'm in the exact same boat. Did you ever figure out how to get wifi back?
Click to expand...
Click to collapse
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
Uggg... I'm really frustrated now, because I got it working with tenfar's original modified boot image and rczrider's system backup. Everything was working. Of course, I didn't have root, so like and idiot, I tried to flash SuperSU 2.76. The phone stuck at the LTE screen after that. I tried re-following all my past steps, and can get the phone to boot, but it's acting crazy. I have two empty SIM icons on the taskbar (I had none when it was working fine) and the phone is very jerky and laggy. I cannot shut it down, or connect to PC easily. It will frequently reboot on its own, and I can't even power it down (it'll say "shutting down" for a few minutes, then reboot).
I eventually got it to shutdown, and repeated the "How to reset..." steps, but it's still acting crazy. I've wiped everything except for system. I'm going to try that next.
peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
Would not mind fixing this rather than shipping my packed up axon7 to newegg. Think I have a few days before it has to ship, so I am open to working on it some more.
Thanks.
---------- Post added 08-29-2016 at 12:00 AM ---------- Previous post was 08-28-2016 at 11:51 PM ----------
Flapjack said:
Uggg... I'm really frustrated now, because I got it working with tenfar's original modified boot image and rczrider's system backup. Everything was working. Of course, I didn't have root, so like and idiot, I tried to flash SuperSU 2.76. The phone stuck at the LTE screen after that. I tried re-following all my past steps, and can get the phone to boot, but it's acting crazy. I have two empty SIM icons on the taskbar (I had none when it was working fine) and the phone is very jerky and laggy. I cannot shut it down, or connect to PC easily. It will frequently reboot on its own, and I can't even power it down (it'll say "shutting down" for a few minutes, then reboot).
I eventually got it to shutdown, and repeated the "How to reset..." steps, but it's still acting crazy. I've wiped everything except for system. I'm going to try that next.
Click to expand...
Click to collapse
Try flashing the 2.65 ver over it
peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .
Barsky said:
Try flashing the 2.65 ver over it
Click to expand...
Click to collapse
That's the thing.... I've restored it repeatedly. All traces of 2.67 should be gone. I've completely restored it three times now.
I'm honestly thinking I'm better off returning this phone while it's still working. I wonder if something is wrong with it.
DrakenFX said:
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .
Click to expand...
Click to collapse
tysm bro <3
DrakenFX said:
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .
Click to expand...
Click to collapse
Brings DrakenFX some coffee and nudges him awake. :cyclops:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Reflash it
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Wolfhawke said:
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Click to expand...
Click to collapse
Why? Root works fine with it, this has nothing to do with that.
crixley said:
Why? Root works fine with it, this has nothing to do with that.
Click to expand...
Click to collapse
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
jmill75 said:
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
Click to expand...
Click to collapse
Yes it works fine and the issue has nothing to do with root. Probably half of us using it are rooted without issue
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
tliebeck said:
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
Click to expand...
Click to collapse
Just got my Essential Phone today as well and did the exact same thing, flashed straight from 7.1.1 to P. I thought I was seriously going to have to send the phone back due to a broken Wi-Fi chip or something. You are seriously a lifesaver!
rignfool said:
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
If I take your post at face value... You have a bad flash and need to try again... Or blame your cable... And go buy a new one...
Otherwise... You have a bad download... Or there is something wrong wrong with your zip or batch/script... Or you're not completely unlocked
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Same here but can't roll back to Oreo
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
1jason said:
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
Click to expand...
Click to collapse
Yes flash the july oreo flashall. Bat
Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
I had the same problem. went back to stock on July's build (was on January's stock build previously) and reflashed P. Been smooth sailing ever since
jacksummers said:
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Click to expand...
Click to collapse
The reason is because one of the OTAs did not have the partition you're looking for... And it created a mismatch somewhere...
You DO NOT need to have the same software on A and B... It just makes troubleshooting easier from our perspective... And... It forces you to reflash and probably fix the problem...
As intended... There should ALWAYS be a mismatch between A and B... At least a monthly security update... If not an Android versioning difference
Edited. We are all just trying to help others. Lets keep it that way.
so, uhmmm like yea...... there is this thread here, called the stock images thread (link for posterity https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 ) this is firmware images, directly from essential. I have added the remaining images that you dont get from essential, so that way you can reflash, and get the same version of software on both sides. there are wipe and no wipe bat files in there, twrp11 (the working twrp we have), and the fix red boot (in case you broke verity), and a stockboot.img (coincidentally the same file as called boot in the zip, but renamed for your twrp/rooting pleasure).
These images work great, many many many people have used them to go back and forth between O and P, OTA, or recover from catastrophe. As usual, beware of dragons, make SURE SURE SURE SURE you have a working adb/fastboot environment (use the version that comes with essentials drivers) (you can always do ADB VERSION or FASTBOOT --VERSION ) to check your version and where its working out of. It is 1 stop shopping. I also know the guy that makes the zips
jacksummers said:
Edited. We are all just trying to help others. Lets keep it that way.
Click to expand...
Click to collapse
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
rignfool said:
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
Click to expand...
Click to collapse
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
jacksummers said:
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
Click to expand...
Click to collapse
Wouldn't it be easier to attempt to port the 2 or 3 features we don't have as a separate systemui.apk or framework-res.apk?
And use Magisk?
Since we don't have that fancy hardware photo rendering thingymabob
When I downloaded the lasted OTA update for my OnePlus 8 Pro I thought it was just another hotfix and didn't realize it was a Big Deal Android 11 update. I tried using the normal OTA upgrade processed and kinda screwed myself.
After trying to install in the inactive slot the way I normally upgrade OTA, I ended up bootlooping. So I downloaded the recovery image and tried patching Magisk the long adb way. It wasn't until later that I realized I had to be on the beta channel. I didn't know you needed to disable modules when you upgrade to Android 11, so they might still be in play, but I don't know how to check. I've tried a bunch of stuff without much luck. Here's where I'm at now:
1) Bootloader is unlocked
2) I can get into Recovery Mode fine
3) I can flash the default/unpatched boot.img for my build and boot up fine, but there's no root, and wifi doesn't work and cellular data is really flakey (even though I normally have fine reception here).
4) From an unpatched boot.img I switched Magisk Manager to the beta channel and installed v21.1. Then I patched boot.img to make a new magisk_patched.img from the beta channel.
5) When I try to fastboot flash magisk_patched.img to slot A I bootloop.
6) When I try to fastboot boot magisk_patched.img I get stuck on the red dot with 2 white dots orbiting it for seemingly forever.
7) I think something is wrong in my slot B because I mostly just get stuck in fastboot. This might be an unrelated problem from a while back though.
8) When I try to run adb wait-for-device shell magisk --remove-modules, I just get an error message about magisk not being found.
What can I do to get back to a rooted working patched magisk without wiping all my data and starting from scratch?
I've honestly never seen anyone do this before so I'm curious as to how you'll recover from this
My thought are MSM but you may be able to boot. Problem is the magisk modules are still in play.
The adb command may not work for removal as you may not get that far.
Did the installation go through ok? It was just booting that failed?
Could maybe try to wipe system via recovery and go from there.
I'm not too sure buddy.
Keep us posted how u get on.
Edit: Try to boot the boot img.
What model are you on? BA ? I have the boot images in my guides in the guides section. Feel free to take what you need.
dladz said:
My thought are MSM but you may be able to boot. Problem is the magisk modules are still in play.
Click to expand...
Click to collapse
What is MSM?
dladz said:
Did the installation go through ok? It was just booting that failed?
Click to expand...
Click to collapse
You mean the result of fastboot flash magisk_patched.img? Yeah, that has finished fine every time. I'm either stuck bootlooping or booting up never finishes.
dladz said:
Could maybe try to wipe system via recovery and go from there.
Click to expand...
Click to collapse
Doesn't that delete all my data? I've only tried wiping the cache so far.
dladz said:
Edit: Try to boot the boot img.
Click to expand...
Click to collapse
Do you mean fastboot boot magisk_patched.img? That just spins forever and never finishes booting.
Flashing back to the unpatched boot.img boots up fine, but my wifi won't turn on and my cellular data is flakey (even though I usually have fine reception here).
dladz said:
What model are you on? BA ? I have the boot images in my guides in the guides section. Feel free to take what you need.
Click to expand...
Click to collapse
I have the US hardware, so I extracted the boot.img from 11.IN21AA, which was the same number that showed up after the OTA was applied.
I dunno, I tried a bunch of different stuff, ended up bricking it. Restored it with MSM to Android 11, then unlocked the bootloader, and tried to flash a fresh magisk_patched.img and it refused to boot in the same way, even though everything was completely fresh.
Are we sure the Magisk beta channel is working right now?
Ecna said:
I dunno, I tried a bunch of different stuff, ended up bricking it. Restored it with MSM to Android 11, then unlocked the bootloader, and tried to flash a fresh magisk_patched.img and it refused to boot in the same way, even though everything was completely fresh.
Are we sure the Magisk beta channel is working right now?
Click to expand...
Click to collapse
There hasn't been anyone stating issues.
Are you using lucky patcher?
dladz said:
There hasn't been anyone stating issues.
Are you using lucky patcher?
Click to expand...
Click to collapse
I don't know what lucky patcher is, so I guess not?
Turns out the wifi problem was happening on stock anyway. And EdXposed doesn't support 11 yet either. So I flashed back to 10.5.13 before bothering to set up all my apps. I'm gonna wait a bit longer for until 11 is more ripe.
Ecna said:
I don't know what lucky patcher is, so I guess not?
Turns out the wifi problem was happening on stock anyway. And EdXposed doesn't support 11 yet either. So I flashed back to 10.5.13 before bothering to set up all my apps. I'm gonna wait a bit longer for until 11 is more ripe.
Click to expand...
Click to collapse
Ah ok, that's fine if you don't know what lucky patcher is then that's a good thing
Yes, that patched boot image failed me. Can't boot. Can't find stock to flash. Bumbed.
dladz said:
Ah ok, that's fine if you don't know what lucky patcher is then that's a good thing
Click to expand...
Click to collapse
Hi dladz, can you please give me more info on lucky patcher and how it could affect things. I'm an avid lucky patcher user, and recently had issues with phone not booting, had to do a factory reset. (I wonder if lucky patcher was some how the culprit)
hbhorat said:
Hi dladz, can you please give me more info on lucky patcher and how it could affect things. I'm an avid lucky patcher user, and recently had issues with phone not booting, had to do a factory reset. (I wonder if lucky patcher was some how the culprit)
Click to expand...
Click to collapse
Don't know if you know this or not but you can't even discuss LP on XDA so I'm afraid I can't..
All I know is that it's dodgier than Donald trump's hair and should be avoided like an old woman's waffle.
If you've had problems and lucky patcher was installed that would be top of my list of culprits.
Bootloops, corruption, force closes to name but a few issues, it probably mines for coin using your phone's processor when it's not in use and god only knows what it does with your data, if that's the price of free apps? Id rather pay for them, my data is with more than any app.
Soz mate, that's all I can offer.
Just avoid it.. :good:
When I try to enable wifi (or bluetooth), it says 'Turning on...' underneath the icon but the process never succeeds.
Note:
-Under About > Status I see no MAC address for Wifi or Bluetooth.
-Phone is not rooted.
-Bootloader is unlocked.
-No custom recovery.
-Airplane mode is off.
-I am able to access the internet when I put in my SIM card and use my cellular data.
-EDIT: Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
-EDIT: I keep my SIM out of this phone (it's in my fully working phone). Can insert if need be.
My attempts to solve this issue (none have worked):
-I updated to OxygenOS 11.
-I booted into recovery and wiped everything, including cache. I also did a System Reset.
-I went to Settings > System > Reset Wifi, mobile and Bluetooth. I also did Erase all data (factory reset) in the same place.
Is there anything else left to try? Is there a way to flash the modem image maybe, I remember having to do that with my Nexus 4 many years ago.
Thanks!
A factory reset never finds the root cause. A virus or an old load are the only reasons to use it otherwise find the root cause. Usually a bad setting. If it's software caused the solution is right in front of you.
Network reset, worth a shot.
Clear system cache, can't hurt.
Clear data in sim card tool kit apk.
Both are probably redundant since you already did a hard reset, but try anyway.
Otherwise...
Bad sim card (try reseating it or replace otherwise) , corrupted firmware, or defective hardware.
Which phone do you have? I've seen this when a user has had a Chinese version and converted to global then when they updated to 11 it all went wrong.
If you're not using a converted Chinese phone then it could very well be your boot image. Extract it using payload then flash it.
If not that then MSM restore your current firmware.
dladz said:
Which phone do you have? I've seen this when a user has had a Chinese version and converted to global then when they updated to 11 it all went wrong.
If you're not using a converted Chinese phone then it could very well be your boot image. Extract it using payload then flash it.
If not that then MSM restore your current firmware.
Click to expand...
Click to collapse
Sorry, what is **MSM** restore?
Under About phone the Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
So I extracted all the images(?) using payload and very foolishly decided to
Code:
fastboot flash modem modem.img
The phone doesn't boot up anymore/remains stuck in loading phase (spinner...). I did a
Code:
fastboot flash boot boot.img
+ wipe + factory reset but still stuck in loading phase.
Any ideas as to how I can fix my mistake?
I appreciate all your help guys.
bassamanator said:
Sorry, what is **MSM** restore?
Under About phone the Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
So I extracted all the images(?) using payload and very foolishly decided to
Code:
fastboot flash modem modem.img
The phone doesn't boot up anymore/remains stuck in loading phase (spinner...). I did a
Code:
fastboot flash boot boot.img
+ wipe + factory reset but still stuck in loading phase.
Any ideas as to how I can fix my mistake?
I appreciate all your help guys.
Click to expand...
Click to collapse
Ah yea that's not good. 2025 AFAIK is global mainly sold in the US.
The MSM tool is in discussion I believe and it's a tool you use to restore your phone using EDL mode, to get to EDL.
Power off your phone.
Connect it to your computer (if it turns on again turn it back off)
Then open up the MSM tool and press and hold volume up and down
Your computer will recognise the the device and at this point you should start the process as it will try again to reboot shortly after without any input from you.
This is the thread you need.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Bare in mind this will relock your bootloader but it's easy to get that back unlocked.
Any questions regarding the tool just ask in the thread.
(you shouldn't need to providing you download the right one)
Download the latest firmware within the tool. If you get stuck don't just guess, ask someone.
@dladz
So I've managed to unbrick the phone using that tool. Thanks.
I'm going to install the latest oxygenos again, extract the boot.img from that zip, and flash it again as per your recommendation.
So I flashed OnePlus8ProOxygen_15.O.32_OTA_0320. No wifi. I extracted the boot.img and then flashed it via fastboot. Still no wifi.
Anything else that I can try?
I guess this is a hardware problem?
bassamanator said:
So I flashed OnePlus8ProOxygen_15.O.32_OTA_0320. No wifi. I extracted the boot.img and then flashed it via fastboot. Still no wifi.
Anything else that I can try?
I guess this is a hardware problem?
Click to expand...
Click to collapse
But now you have bt?
blackhawk said:
But now you have bt?
Click to expand...
Click to collapse
No bluetooth either. Same exact issue as with the Wifi, it says Turning on... then it doesn't.
bassamanator said:
No bluetooth either. Same exact issue as with the Wifi, it says Turning on... then it doesn't.
Click to expand...
Click to collapse
How/when did it start? Anything happen to the phone?
bassamanator said:
@dladz
So I've managed to unbrick the phone using that tool. Thanks.
I'm going to install the latest oxygenos again, extract the boot.img from that zip, and flash it again as per your recommendation.
Click to expand...
Click to collapse
So if you've used that tool then it'll have relocked your bootloader.
Did you unlock it again? AFAIK you can't flash another boot image unless you unlock it again.
The only other thing i can recommend (if you really don't want to RMA)
Would be to downgrade to 10 but in all fairness that really shouldn't even be an option at this point, you've flashed a clean OS back as oxygen would have, you've updated via the official OTA route.
No I think it's time to contact OnePlus for an RMA.
Unless someone else had seen this issue personally I haven't.
Had you rooted in the past btw? Flashed many magisk modules??
I find it highly unlikely that they could survive this but you could potentially try the magisk removal command, can never remember it it's in my payload dumper guide.
If no one else chimes in I'd say it's an RMA, I've not seen it before, it's strange.
Also (and please don't put it on here) but is your IMEI missing too?
This could be your EFS partition if so.
Edit: found this super old thread for the OnePlus one, same issue.
I think this is fixable, potentially remotely from OnePlus and or anyone else who has access to the updated tool, might be worth mentioning in the MSM thread if you haven't already.
PS: don't follow the guide in the link btw it's for the 1+1 lol, in just putting it here as a reference
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
blackhawk said:
How/when did it start? Anything happen to the phone?
Click to expand...
Click to collapse
I got the phone used right before Christmas. It still had the protective plastic on it until I removed it today. It really is in mint condition (or looks to be). I've been away and finally got around to moving things over from my old oneplus 3T.
It's certainly possible that I bought a lemon but at this point I'd like to just fix it if I can.
bassamanator said:
I got the phone used right before Christmas. It still had the protective plastic on it until I removed it today. It really is in mint condition (or looks to be). I've been away and finally got around to moving things over from my old oneplus 3T.
It's certainly possible that I bought a lemon but at this point I'd like to just fix it if I can.
Click to expand...
Click to collapse
I think it's fixable now I really do
From what I've been reading I think it's a mixture of partitions that have been borked z namely the EFS and potentially the persist.img partition if the same position structure exists that did back in the day.
With that in mind are you able to use your fingerprint? I only ask as persist is linked to it so if that's not working then we may have a correlation between problems.
If it is then it's a ? Over the theory.
I'll keep reading but from what I can gather it seems that EFS and persist at least were linked, can't be sure if they are this point.
Have a look at that link I sent see if anything raises a flag for you, bare in mind it's for an older device
dladz said:
So if you've used that tool then it'll have relocked your bootloader.
Did you unlock it again? AFAIK you can't flash another boot image unless you unlock it again.
The only other thing i can recommend (if you really don't want to RMA)
Would be to downgrade to 10 but in all fairness that really shouldn't even be an option at this point, you've flashed a clean OS back as oxygen would have, you've updated via the official OTA route.
No I think it's time to contact OnePlus for an RMA.
Unless someone else had seen this issue personally I haven't.
Had you rooted in the past btw? Flashed many magisk modules??
I find it highly unlikely that they could survive this but you could potentially try the magisk removal command, can never remember it it's in my payload dumper guide.
If no one else chimes in I'd say it's an RMA, I've not seen it before, it's strange.
Also (and please don't put it on here) but is your IMEI missing too?
This could be your EFS partition if so.
Edit: found this super old thread for the OnePlus one, same issue.
I think this is fixable, potentially remotely from OnePlus and or anyone else who has access to the updated tool, might be worth mentioning in the MSM thread if you haven't already.
PS: don't follow the guide in the link btw it's for the 1+1 lol, in just putting it here as a reference
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
Yes I had to oem unlock again.
As far as I know the phone was not rooted but it's a used phone. Superficially it's in mint condition, I just removed the plastic film just earlier. I'll post in the MSM thread and checkout the new one you posted.
EDIT: the phone has 2 IMEI numbers.
bassamanator said:
Yes I had to oem unlock again.
As far as I know the phone was not rooted but it's a used phone. Superficially it's in mint condition, I just removed the plastic film just earlier. I'll post in the MSM thread and checkout the new one you posted.
Click to expand...
Click to collapse
I've already posted in the MSM thread for you.
What about your fingerprint? Is that still working?
dladz said:
I think it's fixable now I really do
From what I've been reading I think it's a mixture of partitions that have been borked z namely the EFS and potentially the persist.img partition if the same position structure exists that did back in the day.
With that in mind are you able to use your fingerprint? I only ask as persist is linked to it so if that's not working then we may have a correlation between problems.
If it is then it's a ? Over the theory.
I'll keep reading but from what I can gather it seems that EFS and persist at least were linked, can't be sure if they are this point.
Have a look at that link I sent see if anything raises a flag for you, bare in mind it's for an older device
Click to expand...
Click to collapse
So I've never registered my fingerprint on a smartphone, ever, but I thought I would register one of my toes just to figure this thing out. When I get to the Fingerprint Setup screen I get the following error: Enrollment was not completed. Fingerprint registration error, please try again.
Does this help narrow down the issue?
bassamanator said:
So I've never registered my fingerprint on a smartphone, ever, but I thought I would register one of my toes just to figure this thing out. When I get to the Fingerprint Setup screen I get the following error: Enrollment was not completed. Fingerprint registration error, please try again.
Does this help narrow down the issue?
Click to expand...
Click to collapse
Yea for me it does, it shows there's a correlation between the persist problem and the EFS problem and a direct connection to your IMEI or Mac address issue.
With this in mind I would recommend the persist.img fix thread..
Getting that working may be key to solving the Mac / IMEI problem.
At this point nothing is going to hurt.
Here is the thread you'll need.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Now I have not been through this but again it can't hurt at this point.
dladz said:
Here is the thread you'll need.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Now I have not been through this but again it can't hurt at this point.
Click to expand...
Click to collapse
I was about to say, I want to try something along the lines of
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
Click to expand...
Click to collapse
or something along those lines from this post https://forums.oneplus.com/threads/no-imei-and-no-efs-backup.322534/page-4#post-14545355 on that old oneplus forum thread you posted.
I'll try the new link you posted instead though.
IMEI is fine btw, the phone dials and connects just fine to cellular.
bassamanator said:
I was about to say, I want to try something along the lines of or something along those lines from this post https://forums.oneplus.com/threads/no-imei-and-no-efs-backup.322534/page-4#post-14545355 on that old oneplus forum thread you posted.
I'll try the new link you posted instead though.
IMEI is fine btw, the phone dials and connects just fine to cellular.
Click to expand...
Click to collapse
Ok don't do the EFS fix you do not have an EFS back up.
Give this a shot
go to data/misc/wifi (required root)
-backup file wpa_supplicant.conf in this folder which contains usename and password wifi
- delete all file in this folder
- turn on wifi ( if you careful, you can reboot )
- now you can connect to wifi
- recovery file wpa_supplicant.conf
This isn't my writing. The English is a little broken but you get the point