Several days ago I upgraded my H9 to b373. Root works good with magisk and also with @phhusson's super user. So I decided to use treble ROM PIE v104. Installation was succesful. I also installed @JBolho's kernel and the ROM works just great. I used it for more then three days without any problems. And on today's morning the phone was switched off eventhough yesterday baterry was on 46%. So I put it on charger and wait an hour. And then when I try to switched it on the phone bootloops and ends in stock recovery. So I flashed back stock ROM b373. Instalation process went just fine but right after signing to google account phone's display goes totally black, only capacitive buttons lighted. I try to reboot, then the phone boot normaly but after it boots up I see only baterry with 0%. So I try one more factory reset but it didn't help. So I relock the phone and it boot up and behaves normal and baterry was on 32%. And I try to relock bootloader and same problem appears - black screen and zero baterry. Now I'm back on b369 (unlocked bootloader) that is from my experience the best one and I dont face any problems.
So be careful
modest.young said:
Several days ago I upgraded my H9 to b373. Root works good with magisk and also with @phhusson's super user. So I decided to use treble ROM PIE v104. Installation was succesful. I also installed @JBolho's kernel and the ROM works just great. I used it for more then three days without any problems. And on today's morning the phone was switched off eventhough yesterday baterry was on 46%. So I put it on charger and wait an hour. And then when I try to switched it on the phone bootloops and ends in stock recovery. So I flashed back stock ROM b373. Instalation process went just fine but right after signing to google account phone's display goes totally black, only capacitive buttons lighted. I try to reboot, then the phone boot normaly but after it boots up I see only baterry with 0%. So I try one more factory reset but it didn't help. So I relock the phone and it boot up and behaves normal and baterry was on 32%. And I try to relock bootloader and same problem appears - black screen and zero baterry. Now I'm back on b369 (unlocked bootloader) that is from my experience the best one and I dont face any problems.
So be careful
Click to expand...
Click to collapse
373 isnt applied for our device (yet?)
so i guess noone should flash it.
latest applied version is 371
Did you verify it was compatible with your device ? I'm using B372 through FF and its working fine
The Mero said:
Did you verify it was compatible with your device ? I'm using B372 through FF and its working fine
Click to expand...
Click to collapse
I installed it through @zxz0O0's HURupdater, so I didn't verify compatibility.
I don't have any problem with B373 + TWRP 3.2.1-0 [0.3] + Magisk v17.1 Root
I'm almost sure that B374 will be out in the next days for C432 model, is already out for C635.
The Mero said:
Did you verify it was compatible with your device ? I'm using B372 through FF and its working fine
Click to expand...
Click to collapse
How did you get FF to work? I've tried both VPN and DNS method and neither works.
It was written 1000 times I think, Firmware Finder works only to download the firmware that will be flashed via TWRP, DNS or Proxy method are dead.
C432B373's working fine here, no problem at all.
OP could be wrong...
cioce said:
It was written 1000 times I think, Firmware Finder works only to download the firmware that will be flashed via TWRP, DNS or Proxy method are dead.
Click to expand...
Click to collapse
No DNS method works fine , FF doesnt like android 8 but works fine with 7 . Use Hisuite to downgrade from 8 to 7 then FF to update through DNS
oslo83 said:
C432B373's working fine here, no problem at all.
OP could be wrong...
Click to expand...
Click to collapse
I'm not 100% sure that b373 caused my problem, but it happened when I was on it and downgrading to b369 solved it.
Sent from my STF-L09 using XDA-Developers Legacy app
modest.young said:
I'm not 100% sure that b373 caused my problem, but it happened when I was on it and downgrading to b369 solved it.
Sent from my STF-L09 using XDA-Developers Legacy app
Click to expand...
Click to collapse
You are downgrade? how?
geogsm_1 said:
You are downgrade? how?
Click to expand...
Click to collapse
@zxz0O0's HuRUpdater could be used for both directions - upgrade and downgrade.
Related
Hi guys,
for some reason after I did update to KangVIP I can't get rid off it. Besides I got no wifi and bt and I was going to start over with b023 as suggested but at this point I wont bother anymore.
I did wipe the system, I did advanced wipe using twrp but no matter what I do none of the stock firmwares are going through however the Kanga one always goes through.(KangaVIP goes through only in TWRP)
twrp 2.8.7.0
wipe
advanced wipe
I select all the partitions
mkdosfs process ended with error=1
unable to wipe /usb
unknown mtp message type: 1
unable to wipe /usb
I go back, restart to fastboot, (device is saying there is no OS installed), I restore the recovery, create dload folder on my sdcard, put there 028 (actually I tried all of them already), volume+ volume - power and I get error.
What am I missing ?
Anyone can help ?
Thanks in advance.
Eric
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Hirs_E_Fruit said:
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Click to expand...
Click to collapse
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
77Eric77 said:
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
Click to expand...
Click to collapse
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
I'm stuck on 6.0
I know I can do force update on 5.0 I said it above I just can't do it with 6.0 -> b029, only with your rom.
Anyone else is having this issue ?
The Kanga rom got a quite few problems no wifi and not BT, Google play services crashing (this can be fixed with gapps) my co worker just tried it with his own methods and same issue. After I went through the whole Kanga thread 60% of the posters got problems most of them are ignored.
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
Hirs_E_Fruit said:
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Click to expand...
Click to collapse
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
77Eric77 said:
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
Click to expand...
Click to collapse
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Hirs_E_Fruit said:
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Click to expand...
Click to collapse
The first rom you introduced is working "fine" I get the wifi and bt no problem but once I switch into the latest build it's gone.
Any idea where can I get full clean Rom ?
This one is a no go http://www.needrom.com/download/p8max-dav-703l/
I managed to rollback to 5.1.1 but when I try to force flash it, it says it's not compatible.
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
ajsmsg78 said:
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
Click to expand...
Click to collapse
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
77Eric77 said:
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
Click to expand...
Click to collapse
Really dude?? No worries, it will be the last time I do anything for the P8Max. Maybe you should just sell the phone since you're having all sorts of issues with it....or maybe you should have left it totally stock then. Or maybe read through the Mediapad X2 forums because the two phones are very similar.
i just rooted my phone and installed superstock rom with no problems in rooting or installing twrp and custom rom . but now i have no signal .simple solutions will not help i have no roaming in the setting . looks like the radio.img file is missing . any ideas how to fix it ????
Flash stock to make sure it's working first and it's not a phone issue
*Detection* said:
Flash stock to make sure it's working first and it's not a phone issue
Click to expand...
Click to collapse
Tried . not working nothing can be installed through odin it keeps failing , its something with samsung security may be after the root, its type of a dead phone now /:
jiries said:
Tried . not working nothing can be installed through odin it keeps failing , its something with samsung security may be after the root, its type of a dead phone now /:
Click to expand...
Click to collapse
Maybe IMEI blocked if stolen or contract not paid off, is it 2nd hand?
Did you try using different USB cables and USB ports?
The phone may have to be force flashed using different hardware such as an octopusbox.
audit13 said:
Did you try using different USB cables and USB ports?
The phone may have to be force flashed using different hardware such as an octopusbox.
Click to expand...
Click to collapse
is there any other solution other than the box ??
in older versions of android we had the possibility to put the radio.img and other simpler solutions .
Usually, flashing a complete stock ROM with Odin will flash everything together including the bootloader, baseband/modem, recovery, and system.
Post the Odin log as there may be something in there that can help resolve the issue.
jiries said:
Tried . not working nothing can be installed through odin it keeps failing , its something with samsung security may be after the root, its type of a dead phone now /:
Click to expand...
Click to collapse
Go to daveloper settings and enable OEM unlock
Now flash stock and latest firmware with odin
And use latest odin version
Sent from my [device_name] using XDA-Developers Legacy app
Try installing dev 5.6 roms from alexander...oem hould
*Detection* said:
Maybe IMEI blocked if stolen or contract not paid off, is it 2nd hand?
Click to expand...
Click to collapse
yes it is , but am pretty sure its not stolen , bought from mobile store was almost new when i got it .
i just managed to fix my phone (in phone store lab , probably they used the box).
last time i rooted the phone and then installed "noutfan " custom rom there was no problem with IMEI , signal or software issues , exept for many bugs in firmware and gear VR made the firmware collapse .
after this i installed superstock rom (without flashing bootloader or modem) i installed kernel and everything which was in the aroma installer ( its not the first time that i flash this rom . worked fine before last time) after installation last timei lost the imei and phone signal (before fixing the phone) .
i dont know what went wrong this time ,usually i install custom roms with no problem . now i have 7.0 stock rom (after fixing the phone) and i want to install custom rom but afraid of facing the same ptoblem .
Any ideas ?? what have i done wrong when i have installed superstock last time?? why i lost imei ?? how to avoid this problem when rooting and installing the custom rom ???
First thing i searched everywhere and find out am the only one with this problem....
The problem start after Oreo update first with random restarts and finally freezing screen.
i am now on Oreo update U4 september and the phone is very unstable with rabdom restarts and freezing on a black screen THAT EVEN DONT RESPOND TO FORCE RESTART !!!
So i need to wate till the phone loss all is battery then charging it, power it on to be able to flash official rom again and agian everytime this happen.
the phone can hold sometimes for 400-600 hours after flashing the offical rom and the the problem occure again
i start to believe theres something wrong with Oreo on this phone..So the last thing to do to make sure there is nothing wrong with Hardware i need to Downgrade to Nougat 7 but when i do that using Oden (flashing AP and BL) it show me error ..So i hope someone can help me with another method to downgrade to Nougate or even figure out whats the main problem that cause all this...
sorry for my bad english hope you can help
heider.raheem said:
First thing i searched everywhere and find out am the only one with this problem....
The problem start after Oreo update first with random restarts and finally freezing screen.
i am now on Oreo update U4 september and the phone is very unstable with rabdom restarts and freezing on a black screen THAT EVEN DONT RESPOND TO FORCE RESTART !!!
So i need to wate till the phone loss all is battery then charging it, power it on to be able to flash official rom again and agian everytime this happen.
the phone can hold sometimes for 400-600 hours after flashing the offical rom and the the problem occure again
i start to believe theres something wrong with Oreo on this phone..So the last thing to do to make sure there is nothing wrong with Hardware i need to Downgrade to Nougat 7 but when i do that using Oden (flashing AP and BL) it show me error ..So i hope someone can help me with another method to downgrade to Nougate or even figure out whats the main problem that cause all this...
sorry for my bad english hope you can help
Click to expand...
Click to collapse
Since your on bootloader version 4 (u4) you won't be able to downgrade to nougat which is why you are getting errors in Odin. When flashing firmware do you use CSC or home CSC.
Not sure if it's hardware related or not but if you are getting up to 400 - 600 hrs out of it I would say it:s software related. There are some apps on playstore for hardware test to try if you like. One issue I have had is the processor running to hot and causes me some issues to the point you can't do anything until it cools down.
spawnlives said:
Since your on bootloader version 4 (u4) you won't be able to downgrade to nougat which is why you are getting errors in Odin. When flashing firmware do you use CSC or home CSC.
Not sure if it's hardware related or not but if you are getting up to 400 - 600 hrs out of it I would say it:s software related. There are some apps on playstore for hardware test to try if you like. One issue I have had is the processor running to hot and causes me some issues to the point you can't do anything until it cools down.
Click to expand...
Click to collapse
i use Home CSC ... and i am sure its not the heat that cause the freezing its happen even when device cool.... This weird behavior doesnt have a constant form... most of the time the freezing happen during the first few minuts during setup device ...FORGET TO MENTION ....in TWRP recovery the device is feeling very well and run smooth without any issue at all... is there something to do now in your openion can solve this?
and if not... what samsung can do for the device to bring it life again?... thanks for your replays
heider.raheem said:
i use Home CSC ... and i am sure its not the heat that cause the freezing its happen even when device cool.... This weird behavior doesnt have a constant form... most of the time the freezing happen during the first few minuts during setup device ...FORGET TO MENTION ....in TWRP recovery the device is feeling very well and run smooth without any issue at all... is there something to do now in your openion can solve this?
and if not... what samsung can do for the device to bring it life again?... thanks for your replays
Click to expand...
Click to collapse
I would think if it is hardware related than the issues would also happen in recovery and/or download mode. I have heard of other people having issues when flashing firmware with home CSC.
Some things I would personally try are:
1. You could try smart switch and check for latest firmware or recovery option.
2. Run in safe mode see if that makes a difference
3. In recovery wipe cache/dalvik and reboot
4. In recovery factory reset
5. Flash firmware again with CSC not home CSC.
Problems with options 1,4,5 is you will need to backup your apps and data etc. Option 5 you will have to reinstall twrp.
These options aren't in any order so I would start with 3 first see how it goes then 2 see how it goes then ,1,4 and 5 and see how it goes for each step.
Let me know how it goes
spawnlives said:
I would think if it is hardware related than the issues would also happen in recovery and/or download mode. I have heard of other people having issues when flashing firmware with home CSC.
Some things I would personally try are:
1. You could try smart switch and check for latest firmware or recovery option.
2. Run in safe mode see if that makes a difference
3. In recovery wipe cache/dalvik and reboot
4. In recovery factory reset
5. Flash firmware again with CSC not home CSC.
Problems with options 1,4,5 is you will need to backup your apps and data etc. Option 5 you will have to reinstall twrp.
These options aren't in any order so I would start with 3 first see how it goes then 2 see how it goes then ,1,4 and 5 and see how it goes for each step.
Let me know how it goes
Click to expand...
Click to collapse
Actually steps 1,3,4,5 all have been tried before without making difference but i never tried to run in safe mode (step 2)... i should tried it.... but now i cant cause one of the freezing form and the most occuring one is when blue screen with android logo at the center that appear befor the samsung logo (trying to erasing data befor the first boot after flashing a new rom)...so i have to download a nother oreo firmware from sammobile to make it run ...sorry if i make it complicated for you but this is how my device acting very weird....
Do you think its somthing wrong with Oreo in this s8+ that can be solved when downgraded to Nougat or Upgaraded to Pie maybe?
heider.raheem said:
Actually steps 1,3,4,5 all have been tried before without making difference but i never tried to run in safe mode (step 2)... i should tried it.... but now i cant cause one of the freezing form and the most occuring one is when blue screen with android logo at the center that appear befor the samsung logo (trying to erasing data befor the first boot after flashing a new rom)...so i have to download a nother oreo firmware from sammobile to make it run ...sorry if i make it complicated for you but this is how my device acting very weird....
Do you think its somthing wrong with Oreo in this s8+ that can be solved when downgraded to Nougat or Upgaraded to Pie maybe?
Click to expand...
Click to collapse
Just curious what firmware version are you using.
spawnlives said:
Just curious what firmware version are you using.
Click to expand...
Click to collapse
i use now Oreo G955FXXU4CRI5
heider.raheem said:
i use now Oreo G955FXXU4CRI5
Click to expand...
Click to collapse
Is it working ok or still same problem
spawnlives said:
Is it working ok or still same problem
Click to expand...
Click to collapse
its froze right now it cant even get to samsung logo...and even if i flash the ROM again and get it work it will freez after maximum 600 hours (thats happened 3 times)
I've done a lot of searching but can't seem to find anyone posting about the issue I'm having with DP3 on my 7 Pro. I'm stock on 9.5.10. the flash using local update works fine. Upon reboot, the phone will work for a few seconds, once a while it works for a couple of minutes. Then the screen goes black. If I hit the power button twice, I get a reboot dialog box. I restart and the process starts all over. I went back to 9.5.9 and everything is fine. I tried again going from 9.5.9 to DP3 after a full format. Same thing happens. I suspect the UI is stopping but it just goes black.
Anyone have any ideas?
Just wanted to chime in to say the same thing is happening to me.
Mike02z said:
I've done a lot of searching but can't seem to find anyone posting about the issue I'm having with DP3 on my 7 Pro. I'm stock on 9.5.10. the flash using local update works fine. Upon reboot, the phone will work for a few seconds, once a while it works for a couple of minutes. Then the screen goes black. If I hit the power button twice, I get a reboot dialog box. I restart and the process starts all over. I went back to 9.5.9 and everything is fine. I tried again going from 9.5.9 to DP3 after a full format. Same thing happens. I suspect the UI is stopping but it just goes black.
Anyone have any ideas?
Click to expand...
Click to collapse
You need to downgrade in twrp to 9.5.7 then update your phone to dp3 and everything will be grate. I was on dp 3 till I wanted to try out omni ROM witch is grate but there is more customization on dp3 then any ROM for this phone so go ahead and downgrade and then update to dp3. The region it will not update to dp3 is because its build number is lower then 9.5.10 ok
The challenge is downgrading. Can't install TWRP because I get the error when I try to boot it via fasboot. I can't get to the local upgrade option in settings to install the downgrade zip that OnePlus provides, and I can't fastboot an old version because I get a var error. Any suggestions?
NickMidd91 said:
You need to downgrade in twrp to 9.5.7 then update your phone to dp3 and everything will be grate. I was on dp 3 till I wanted to try out omni ROM witch is grate but there is more customization on dp3 then any ROM for this phone so go ahead and downgrade and then update to dp3. The region it will not update to dp3 is because its build number is lower then 9.5.10 ok
Click to expand...
Click to collapse
Thanks. I tried this and while not as frequent, system UI crashes continue. When I went to bed it was fine. After 5 minutes use this AM, it started going black again. I'm going to wait for the next release before testing again.
Odd that only 2 have reported this here. If it helps, I have 2 SIMS both on Verizon Wireless.
Apparently this is a known issue. Bug has been reported to OnePlus.
why is no one discussing stable android 11 for op7p ? got my update round 3 a.m. this morning. been searching all day for a working twrp since the stable android 11 been released. no luck though......
Hi,
Today I installed the update manually and my phone keeps flashing the TWRP load-screen at boot. It's stuck now. Is that because there is no compatible TWRP version yet? How do I fix this?? Any idea?
There is no working TWRP yet for Android 11. You'll need to flash the stock boot.img or rooted boot.img from one of the threads in the news, guides section.
Edit: TWRP screen flashing is because it's incompatible. I had the same issue on the open betas.
Have the exact same issue as above, Twrp screen flashing, cannot boot back to normal even with adb... anybody has a rooted boot.img link that knows works with Android 11?
Should have checked on xda first *slaps his face*
Always check xda first *slaps his face again*
EDIT: For other poor saps with this issue use this -> https://www.androidfilehost.com/?fid=2188818919693770594 I didnt managed to get booted with rooted img but the original boot img file worked well ... at least I got a phone now...
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
santiagoruel13 said:
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
Click to expand...
Click to collapse
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
dejjem said:
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
Click to expand...
Click to collapse
I mean.. same steps.. that ive used so far amd retain its root.
1. Download rom via o2 updater
2. Flash it via local update
3. Install magisk to inactive slot
4. Reboot.
So if i do this.. wifi wont work??? Is that it???
Finished updating my phone..after downloading it for about 2 hours.
And im quite satisfied with the results. No problems whatsoever..
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
dejjem said:
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
Click to expand...
Click to collapse
i dont mind not having TWRP for the meantime,, i just used TWRP previously for flashing CUSTOM kernels.. hehehehe.
anyways, what problem have you encountered regarding wifi?? i dont seem to experience those,, maybe because i came from stable oos 10.3.8..
what app crashed and problems have you encountered???