Develop Bugs

[Q] primoc cdma kernel crash (all kernels)

RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
Original post:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?

wendall911 said:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
Try stock kernel if that crashes then custom rom
Sent from my One V using xda app-developers app

cybervibin said:
Try stock kernel if that crashes then custom rom
Click to expand...
Click to collapse
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.

wendall911 said:
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.
Click to expand...
Click to collapse
Does it happen like this?
http://www.youtube.com/watch?v=IIqT-xd0AqU&feature=youtu.be
I have the same issue man. It's bizarre.

patbushnell said:
Does it happen like this?
I have the same issue man. It's bizarre.
Click to expand...
Click to collapse
Yes, this is the same behaviour. I'm not sure if you're able to dump the dmsg stuff from adb, but certainly same crash. Typically the phone network status shows a little x, right before the reboot. But the lagginess starts happening when the 5 second kernel reboot is issued.
I've tried to change to airplane mode, disable sdcard and everything else I can think of, still crashing and I'm not able to make much of the logging info

When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain

aaronrw said:
When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain
Click to expand...
Click to collapse
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.

wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
You will surely get the RUU to make your phone working perfectly. That's what I did.

patbushnell said:
You will surely get the RUU to make your phone working perfectly. That's what I did.
Click to expand...
Click to collapse
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!

I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
wendall911 said:
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!
Click to expand...
Click to collapse
So are you able to run any other roms without reboots? Or are you only on stock?

MasterTec said:
I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
So are you able to run any other roms without reboots? Or are you only on stock?
Click to expand...
Click to collapse
I applied the OTA update. Only the stock kernel (after update) will boot now. Any non-stock kernel crashes - always seems the last line is rmt_storage, which the IPC to shared memory of the boot loader I believe.

Noob question
wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
Can you link me to a working RUU?

i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...

jetfactor said:
i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...
Click to expand...
Click to collapse
Yes it's possible that you got one with the update already on it however the problem you are having is completely different than the problem we're describing in this thread and could be caused by many other things - not necessarily the OTA update.
Seems a bit off topic for this thread...

More of the rebooting problem
I have 2 phones one with this problem, the other without it. My friend got one of these phones after i installed jelly bean on mine. He had it long enough to have updated the firmware using the stock image. I made a backup of the stock image, but it seems to have been corrupted (zero byte .zip file). I need to get the phone working (stock or updated, at this point there is no preference so long as it works)
In the bootloader, the radio version of the crashing one is:
1.00.00.0928
The working one is:
1.00.00.0521_2
As far I can tell, this is the only difference. I Used the same SD card and the same procedure for wipe/installing the OS with the same files.
Have you found a solution to this? If so, can you point me to the downloads/instructions for how to fix it?

Looking for help
wendall911 said:
RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!

madhephaestus said:
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!
Click to expand...
Click to collapse
hey can i please know how to fix the radio on my phone i have the same problem, my phone will boot and turn on but after 10 seconds in turns off again and boots again? can i please get help ?

[Q] HELP - Wiped the OS off of my Galaxy S3 I747

Alright, well I've come to a problem and I'm not quite sure how to fix it.
The title pretty much says it all, I've completely wiped the operating system off of my phone. There is nothing left, absolutely no data or anything. I was much too hasty and irresponsible, and I fear for the worst. I had previously attempted installing multiple ROMs multiple times using CWM to no avail so I re-rooted and switched over to Team Win. I know before installing a ROM you have to wipe your phone, well... I hit advanced wipe and within that I hit "system", went ahead and wiped. There's nothing left on my phone my phone and there are no ROMs on my SD card. I had backed up my phone before wiping but when I wiped that was also deleted. Before restarting it always warns me "No OS installed on your phone, are you sure you want to reboot?" Of course it's bricked and stays at the "Samsung Galaxy SIII" screen. I attempted putting a stock ROM back on my phone through ODIN, but a'las it didn't work (always stops at "SetupConnection"). I have nothing and there is no way for me to get a new ROM on the phone, I obviously cannot connect to my computer unless through download mode because the phone is bricked. So, what do I do? Is there any hope left for me or am I just completely screwed? The phone is less than a month old.

another option is to purchase a micro sd card and place a ROM and gapps (if required) on it, install the card and boot into recovery.
so when you connect your device to your pc, you're getting a yellow com connection in odin? what link did you follow for a stock ROM?
as long as you can still access recovery and download mode, there is hope, buddy.

xBeerdroiDx said:
another option is to purchase a micro sd card and place a ROM and gapps (if required) on it, install the card and boot into recovery.
so when you connect your device to your pc, you're getting a yellow com connection in odin? what link did you follow for a stock ROM?
as long as you can still access recovery and download mode, there is hope, buddy.
Click to expand...
Click to collapse
Yeah, when I connect to the PC I get a yellow com connection in ODIN. I followed what is, perhaps, a sketchy looking link for the stock ROM... It's not letting me post a link because I'm a new member to the board, though I've looked over this place plenty of times in the past. Should I look for something a bit more official and retry? I don't think it's going to work. Will a ROM work, without an OS? I know that may sound silly but everything I've tried so far has failed.

here's a link to the stock firmware with root already injected: http://forum.xda-developers.com/showthread.php?t=1739426
flash the tar in odin like you have been. make sure the auto reboot box is unticked. if you get a PASS after flashing, unplug the device, pull the battery, replace it and press the recovery button combo. once in recovery, wipe data and wipe cache. reboot.
lemme know if that worked, otherwise throw a ROM on a micro sd card as stated and go that route
btw, a ROM is the OS.

And also, my phone has to be rooted for a ROM to be installed, right? Well there's no guarantee my phone is still rooted since I've wiped literally everything on the phone. I like the idea of a placing it all on an SD card but that could be wasted money and I don't have very much money to spend, especially if a ROM isn't going to replace all of the needed system files which have been deleted.

NovoAevum said:
And also, my phone has to be rooted for a ROM to be installed, right? Well there's no guarantee my phone is still rooted since I've wiped literally everything on the phone. I like the idea of a placing it all on an SD card but that could be wasted money and I don't have very much money to spend, especially if a ROM isn't going to replace all of the needed system files which have been deleted.
Click to expand...
Click to collapse
follow my directions above to flash rooted stock firmware

xBeerdroiDx said:
follow my directions above to flash rooted stock firmware
Click to expand...
Click to collapse
Alright, thanks a lot. My internet is super slow so it'll probably be a while before the file is completely downloaded. Let's hope this works. I'll get back to you when it's all said and done.

xBeerdroiDx said:
follow my directions above to flash rooted stock firmware
Click to expand...
Click to collapse
You have no idea how grateful I am, thank you so very, very much. It worked, I cannot express my gratitude. I truly appreciate it.

NovoAevum said:
You have no idea how grateful I am, thank you so very, very much. It worked, I cannot express my gratitude. I truly appreciate it.
Click to expand...
Click to collapse
booyah.
:good: thats why we're called a community. cheers!

NovoAevum said:
You have no idea how grateful I am, thank you so very, very much. It worked, I cannot express my gratitude. I truly appreciate it.
Click to expand...
Click to collapse
One small thing you can do is to hit the "Thanks" button on xBeerdroiDx's posts.
:good:

im having the same promblem
post-mortem said:
One small thing you can do is to hit the "Thanks" button on xBeerdroiDx's posts.
:good:
Click to expand...
Click to collapse
how did u get your phone to connect to odin

dorvilkervins said:
how did u get your phone to connect to odin
Click to expand...
Click to collapse
Have you installed the Samsung drivers?
---------- Post added at 06:03 PM ---------- Previous post was at 05:27 PM ----------
Can you explain what happened with your phone? How did you "lose everything?" Is it able to boot up into Android? Can you get into recovery (TWRP)? Did you accidentally wipe something you shouldn't have?

I accidentally wiped my OS on my Galaxy S3 AT&T - Please Help!!!
Hello all,
I am a rookie user of smartphones and I have a Samsung Galaxy S3 AT&T. I accidentally wiped my OS leaving me with no OS. The good news is that I can still use Team Win and boot into recovery. How can I download and install a new OS? I live in a rural area with no place to go to get this fixed; so I would really appreciate any and all help on this matter. Thanks for reading
Tyler
---------- Post added at 01:10 AM ---------- Previous post was at 12:24 AM ----------
Hello all,
I am a rookie user of smartphones and I have a Samsung Galaxy S3 AT&T. I accidentally wiped my OS leaving me with no OS. The good news is that I can still use Team Win Development. Using Team Win, how can I download and install a new OS? I live in a rural area with no place to go to get this fixed; so I would really appreciate any and all help on this matter. Thanks for reading
Tyler

Check this:
http://forum.xda-developers.com/showthread.php?t=2363882

Hey Bro, xBeerdroiDx, Indeed this is a great community, but, it is the fellas' and ladies, like you,that have the knowledge and experience ,that do not have to assist anyone ,but do anyway. I am just another member here, but as a brother, you get a pat on the back from the gallery. Your willingness to help is very much appreciated.

me too
so twrp and dl mode are cool...but odin fails and zip in recovery kicks a status 7 error...what to do?
sgh-i747 .....i think my build.prop or bootloader is jacked?

hewhoisnotasothers said:
so twrp and dl mode are cool...but odin fails and zip in recovery kicks a status 7 error...what to do?
sgh-i747 .....i think my build.prop or bootloader is jacked?
Click to expand...
Click to collapse
Did you try \the latest CWM or TWRP? Maybe the ROM needs a more recent bootloader?

gottam
audit13 said:
Did you try \the latest CWM or TWRP? Maybe the ROM needs a more recent bootloader?
Click to expand...
Click to collapse
the bootloader may have been corrupted by a 4.x downgraded flash....i'm not sure how to proceed...

hewhoisnotasothers said:
the bootloader may have been corrupted by a 4.x downgraded flash....i'm not sure how to proceed...
Click to expand...
Click to collapse
Were you on stock 4.3 ROM?

audit13 said:
Were you on stock 4.3 ROM?
Click to expand...
Click to collapse
yes...I have tryed everything i can think of....i can flash recoverys just fine, but i havent found a rom that will boot past the splash screen...most just fail in odin...i don't want to jtag if i dont have to...in theory there should be hope since i can get into DL and twrp....

Updated Magisk Manager - NOW BRICKED?!

Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:

dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504

timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt

The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.

dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk

dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.

kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.

Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:

dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img

This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img

timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?

WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?

@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy

timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!

@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT

Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?

@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up

Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.

adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs

BND-L24

is there any possible way to download firmware for the honor 7x BND-L24 since i bricked mine and all i could find is all the other models just not the one i need.

Not as of yet. I am hoping there will be something soon myself.

we just need someone who still haven't done anything to their phone, and kept a clean backup of everything. Or someone need to reset their phone in order to make the back up. We can download it and use it for our self like new 7x L-24

^ This. Please someone be the hero we need! Lol.

John0074 said:
we just need someone who still haven't done anything to their phone, and kept a clean backup of everything. Or someone need to reset their phone in order to make the back up. We can download it and use it for our self like new 7x L-24
Click to expand...
Click to collapse
Is it possible to make a back up of stock firmware without root or twrp? Just curious.

kingd421 said:
Is it possible to make a back up of stock firmware without root or twrp? Just curious.
Click to expand...
Click to collapse
ya i just checked today. you can do it either way. I am thinking about buying another one to check out my theory.

Anyone tried installing other variations (such as the Indian Roms) to see if it works?

I got ahold of support for Huawei US and they told me mid-March was when they plan to release the stock firmware for the Honor 7x. Hopefully will be released within the next week, 2 at most. Mine isn't bricked, but I am using a really botched custom ROM(no bluetooth, camera, fingerprint reader and Google services do not work, so I have to sideload all my apps, the battery is also crap on the custom rom and the phone heats up a lot faster) I can't wait until they release it, it was my fault that I didn't make a nandroid backup, though, tbf. Won't be too much longer, though <3
---------- Post added at 04:50 PM ---------- Previous post was at 04:40 PM ----------
Here's a screenshot of the support who told me Mid-March. I couldn't directly post it because under 10 posts, but it's quoted here.
imgur(DOT)com/a/uYYuM
Click to expand...
Click to collapse

Jeffrey2457 said:
I got ahold of support for Huawei US and they told me mid-March was when they plan to release the stock firmware for the Honor 7x. Hopefully will be released within the next week, 2 at most. Mine isn't bricked, but I am using a really botched custom ROM(no bluetooth, camera, fingerprint reader and Google services do not work, so I have to sideload all my apps, the battery is also crap on the custom rom and the phone heats up a lot faster) I can't wait until they release it, it was my fault that I didn't make a nandroid backup, though, tbf. Won't be too much longer, though <3
---------- Post added at 04:50 PM ---------- Previous post was at 04:40 PM ----------
Here's a screenshot of the support who told me Mid-March. I couldn't directly post it because under 10 posts, but it's quoted here.
Click to expand...
Click to collapse
Be careful because I was using that same custom Oreo rom and now my Honor 7x is pretty much completely bricked... The rom started crashing and bootlooping on startup and TWRP stopped working too. It just flickers with a dead Android icon when I try to do Power + Volume Up. I can get into the eRecovery and fastboot but I'm not sure if I'll be able to fix it at this point. I just ended up ordering a new phone last night...

ekovv said:
Be careful because I was using that same custom Oreo rom and now my Honor 7x is pretty much completely bricked... The rom started crashing and bootlooping on startup and TWRP stopped working too. It just flickers with a dead Android icon when I try to do Power + Volume Up. I can get into the eRecovery and fastboot but I'm not sure if I'll be able to fix it at this point. I just ended up ordering a new phone last night...
Click to expand...
Click to collapse
Yeah, I'm on currently using it because I was stupid and didn't make a backup and have no way to go back to stock until they release it. I've had to reinstall this ROM about 6 times already in the past 2 weeks just because of boot loops, freezing, and corruption. TWRP also broke on me, but was lucky enough to be able to flash it back with ADB and then reinstall AOSP. I'll definitely try it out again in the future, but I think I'll leave it to those who are more willing to risk it than me lol, at least, until it has a good bill of health for usage.

Jeffrey2457 said:
Yeah, I'm on currently using it because I was stupid and didn't make a backup and have no way to go back to stock until they release it. I've had to reinstall this ROM about 6 times already in the past 2 weeks just because of boot loops, freezing, and corruption. TWRP also broke on me, but was lucky enough to be able to flash it back with ADB and then reinstall AOSP. I'll definitely try it out again in the future, but I think I'll leave it to those who are more willing to risk it than me lol, at least, until it has a good bill of health for usage.
Click to expand...
Click to collapse
Hmm, nice. I did reinstall TWRP with adb, but it still didn't work. Was there anything special you had to do?

Not sure if it would help, but i have a fresh Mate SE arriving tomorrow I could rip a clean dump off of. Which I planned on doing anyway before I did any setup of the device.

ekovv said:
Hmm, nice. I did reinstall TWRP with adb, but it still didn't work. Was there anything special you had to do?
Click to expand...
Click to collapse
Nope, I did it the same way I did it when I first installed AOSP(Errr, relatively, anyway. I originally installed TWRP to install SuperSU Root, but when I disabled root, I somehow bricked my phone, which is why I resorted to AOSP lol, but I installed it by just wiping the encryption and data with TWRP and the installing via the AOSP Image and it worked fine... Sorta... Best AOSP does rn anyway lol)

I do have TWRP backup of system, boot, and data .img for the honor 7x BND-L24 USA. Twrp would came back with error 255 for the data file but looks like it still copied It, So I have

chrisn812 said:
Not sure if it would help, but i have a fresh Mate SE arriving tomorrow I could rip a clean dump off of. Which I planned on doing anyway before I did any setup of the device.
Click to expand...
Click to collapse
I'm in dire need of a clean dump for the Mate SE. Bricked it the day I got it. If you have this, I'd love you forever

Got what you all need
Milly7 said:
Not as of yet. I am hoping there will be something soon myself.
Click to expand...
Click to collapse
I learned from when I had the honor 6x to make a back up first. When I unbricked it I took I returned it got the 7x BND-L24 got twrp installed and made a backup of Sustem, Boot, and data. Hit thanks If you want it and I will post Direct Download link

BiggDipper said:
I learned from when I had the honor 6x to make a back up first. When I unbricked it I took I returned it got the 7x BND-L24 got twrp installed and made a backup of Sustem, Boot, and data. Hit thanks If you want it and I will post Direct Download link
Click to expand...
Click to collapse
Yes, please post a direct link. It will be greatly appreciated.

stock firmware coming next week
Hey folks, just wanted to let you know I got in touch with customer service and they gave me a release date of either March 26 or March 30 for stock firmware. Conversation is attached.

Honor 7x Firmware Backup
Milly7 said:
Yes, please post a direct link. It will be greatly appreciated.
Click to expand...
Click to collapse
I am zipping it now then I will get it uploaded to Gdrive. Then I will make a thread post it up then come back with a link to the thread. You have been here for awhile I am new. Any pointers you can give me to help me make the thread would be greatly appreciated.

BiggDipper said:
I am zipping it now then I will get it uploaded to Gdrive. Then I will make a thread post it up then come back with a link to the thread. You have been here for awhile I am new. Any pointers you can give me to help me make the thread would be greatly appreciated.
Click to expand...
Click to collapse
I have only created a couple of threads, but I recall it being very easy to do. You just want to make sure you post it in the correct section. I would think you could post this in the general section. News, discussion, etc.

OP3 phone is un-usable please help!

Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM

the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.

tnsmani said:
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.
Click to expand...
Click to collapse
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue

the_mentor said:
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue
Click to expand...
Click to collapse
You will need to replace the main board if the issue persist.

Same problem here
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks

New geek said:
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks
Click to expand...
Click to collapse
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.

the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
try using msm v3.0 tool fixes most problems not hardware though

the_mentor said:
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.
Click to expand...
Click to collapse
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.

New geek said:
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.
Click to expand...
Click to collapse
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!

what you will need to do is download the oneplus 3 recovery tool and put the phone into qualcolm mode and restore the phone that way. here is a link https://www.androidexplained.com/oneplus-3-unbrick-return-stock/

New geek said:
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!
Click to expand...
Click to collapse
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM

the_mentor said:
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM
Click to expand...
Click to collapse
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.

tnsmani said:
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.
Click to expand...
Click to collapse
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM

the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
Please share the guide as I am also suffering with same problem.

Still not working
the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
I was about to update here with good news but wife's phone went back to restart loop the next day. I am not sure but probably triggered by her installing whatsapp and facebook. I put the phone away because I have already spend quite a lot of time behind this. Is your's still going? Please list the step by step procedure. Thanks

download from here https://mega.nz/#!zsdnkCDA!UyJRwbJK6kHTDpmesBYao0knaOTwbgu4dSiokV1XLYU then turn off phone run tool,connect phone with volume up pressed,should have a com in the list if so just click start thats it and wait for it to turn green or device restart