Related
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
I don't have it, but I can look into it...
Bibicp said:
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
Click to expand...
Click to collapse
My device is rooted, and the only backup I made with CWM was after I rooted, if I go to update (if my device can find it) will I:
1) Brick out and be screwed?
2) Have to flash my backup (which is rooted, so would that mean I can't update again?)
3) Be ok and keep my rooting?
4) Be ok, and lose my rooting, and have to re-root?
I realize I am kind of answering your question with a question, but I would be happy to see if I can track it down and see what changes there are, if it's safe to install.
FlynnErik said:
My device is rooted, and the only backup I made with CWM was after I rooted, if I go to update (if my device can find it) will I:
1) Brick out and be screwed?
2) Have to flash my backup (which is rooted, so would that mean I can't update again?)
3) Be ok and keep my rooting?
4) Be ok, and lose my rooting, and have to re-root?
I realize I am kind of answering your question with a question, but I would be happy to see if I can track it down and see what changes there are, if it's safe to install.
Click to expand...
Click to collapse
Try backing up your system using clockworkmod recovery first, then go to download mode, flash your firmware version (download from samfirmware or samsung-updates) and flash it with odin.
This way you're unrooted, running stock rom and stock recovery and then you can install the update.
I didn't try to install an update while rooted, but it's not recommended so don't try.
I did a back up after I rooted with CWM
Bibicp said:
Try backing up your system using clockworkmod recovery first, then go to download mode, flash your firmware version (download from samfirmware or samsung-updates) and flash it with odin.
This way you're unrooted, running stock rom and stock recovery and then you can install the update.
I didn't try to install an update while rooted, but it's not recommended so don't try.
Click to expand...
Click to collapse
So is my backup going to be rooted? Or will it be the stock? I am currently rooted stock 4.0.4.
Btw, I have found no information about the update anywhere on the net. Maybe they accidently did a push to us, and pulled it back?
Should I wipe cache, dalvik and FDR before I flash the firmware from those sites or use the backup I made already? (which I am unsure if I should even use since idk if it will be rooted or not lol)
I wasn't going to update till it was time to get JB, but this update that vanished is intriguing enough I might lol
As i know yes when you restore backup with cwm the result will be rooted also as the cwm takes image of the system when doing backup and as you when doing backup was rooted so when restore this backup you will be still rooted if you flash via odin no need to wipe cash and dalvik cash i never read anyone doing this
Even if you do this wipe no harm at all
Sent from my GT-I9100 using xda app-developers app
As mohamed selim said, but wipe your data and do a factory reset in clockworkmod (after backup)
and why will samsung pull back the update?
There's several reasons why this may happen
Bibicp said:
As mohamed selim said, but wipe your data and do a factory reset in clockworkmod (after backup)
and why will samsung pull back the update?
Click to expand...
Click to collapse
They pushed it out to the wrong devices
They pushed it out to early
They found a last minute bug and had to pull back
They are testing it, and not everyone should have gotten the option to get it.
Ok so to get things straight. If/when we go to JB I will need to download a firmware stock from one of the sites listed above, download it.
Do a backup (just to be safe of what I have now)
FDR/Wipe everything
Install the firmware using Odin
If everything looks good, re-flash CWM
Do another backup so I have a clean stock to revert back to down the road if needed.
That sum it up correctly? This way I can bookmark this thread so I don't forget lol.
**EDIT** When I use Odin to restore stock will I lose CWM? If so, what happens if something goes wrong in the Odin restore and I have a boot loop, or etc, what would be my next move since I won't have CWM to restore previous, would I be able to install it like I would if things were going ok?
Sorry for sounding like a n00b, I am still learning all about this, but I think I am getting closer to learning enough to not be a n00b lol. I only have 10 tabs open with this forum instead of 20!
FlynnErik said:
They pushed it out to the wrong devices
They pushed it out to early
They found a last minute bug and had to pull back
They are testing it, and not everyone should have gotten the option to get it.
Ok so to get things straight. If/when we go to JB I will need to download a firmware stock from one of the sites listed above, download it.
Do a backup (just to be safe of what I have now)
FDR/Wipe everything
Install the firmware using Odin
If everything looks good, re-flash CWM
Do another backup so I have a clean stock to revert back to down the road if needed.
That sum it up correctly? This way I can bookmark this thread so I don't forget lol.
**EDIT** When I use Odin to restore stock will I lose CWM? If so, what happens if something goes wrong in the Odin restore and I have a boot loop, or etc, what would be my next move since I won't have CWM to restore previous, would I be able to install it like I would if things were going ok?
Sorry for sounding like a n00b, I am still learning all about this, but I think I am getting closer to learning enough to not be a n00b lol. I only have 10 tabs open with this forum instead of 20!
Click to expand...
Click to collapse
It's not for the wrong device since it's saying P3113, and it's not jelly bean. as I've seen on samsung firmware.com it's 4.0.4.
Well, on my homescreen I put a shortcut for the software update, it still has a circle saying 'N" on it (which probably stands for new), but going in kies I don't find it, It only says it downloaded it but the firmware is up to date.
So probably either they really pulled it back, or it's a bug and they're fixing it. (I really can't wait for jelly bean)
Second, yes it will erase the CWM recovery and go back to stock recovery.
The common mistake people make to get a bootlop is not wiping data/doing a factory reset before flashing a new ROM, so you should go to recovery and do a factory reset, then go to download mode and flash the firmware with odin. If you ever get stuck in a bootloop, try pressing volume down + power key to get to download mode and re flash the ROM. if it's still stuck, try re-downloading the ROM files you downloaded, it could be corrupted.
Awesome!
Bibicp said:
It's not for the wrong device since it's saying P3113, and it's not jelly bean. as I've seen on samsung firmware.com it's 4.0.4.
Well, on my homescreen I put a shortcut for the software update, it still has a circle saying 'N" on it (which probably stands for new), but going in kies I don't find it, It only says it downloaded it but the firmware is up to date.
So probably either they really pulled it back, or it's a bug and they're fixing it. (I really can't wait for jelly bean)
Second, yes it will erase the CWM recovery and go back to stock recovery.
The common mistake people make to get a bootlop is not wiping data/doing a factory reset before flashing a new ROM, so you should go to recovery and do a factory reset, then go to download mode and flash the firmware with odin. If you ever get stuck in a bootloop, try pressing volume down + power key to get to download mode and re flash the ROM. if it's still stuck, try re-downloading the ROM files you downloaded, it could be corrupted.
Click to expand...
Click to collapse
So the one on the site even though its XAR is us? Can I ask why we have that tag? Not something like US or etc? I mean I don't care, just kinda curious since that would make it more simple to know which region gets what, at least for me it would lol.
Thank you so much for the help and the knowledge, I figured I would end up with stock recovery, which is why I wanted to make sure about what if something goes wrong.
As a side thought, where does the backup that CWM makes located? Can I copy and paste that on to my PC so I always have a back up handy? (I would sync it into the cloud). Can I flash that with odin down the road? Or is that only a CWM usable file?
Any more info on the firmware release?....Trying to download it now!
Firmware Version: P3113UEBLH1
OS: Ice Cream Sandwich
OS Version: v4.0.4
Release Date: 08-10-2012
Build Date: 08-10-2012
Changelist: 999349
Gizmo said:
Any more info on the firmware release?....Trying to download it now!
Firmware Version: P3113UEBLH1
OS: Ice Cream Sandwich
OS Version: v4.0.4
Release Date: 08-10-2012
Build Date: 08-10-2012
Changelist: 999349
Click to expand...
Click to collapse
That's all I know about it, where are you downloading it? samsung updates.com? or kies/OTA update?
Bibicp said:
That's all I know about it, where are you downloading it? samsung updates.com? or kies/OTA update?
Click to expand...
Click to collapse
I found it on some foreign site....samsung-updates.com won't let you download the P3113UEBLH1 firmware, Just the Kernel, I don't use Kies! Uploading it right now!
Gizmo said:
I found it on some foreign site....samsung-updates.com won't let you download the P3113UEBLH1 firmware, Just the Kernel, I don't use Kies! Uploading it right now!
Click to expand...
Click to collapse
Alright, tell me if you notice anything different.
Nice
good!
Im downloading it now. Ill post it when its rooted and deodexed
Bibicp said:
I've noticed there was an update on kies this week (P3113UEBLH1), I'm not sure what it was thought.
I've tried upgrading in kies, it was stuck at 0% downloading then connection timed out.
The OTA update didn't find any updates available.
Then next morning, kies said no update available too.
So, Anyone got the update to work, and if so what changes did you notice?
The update is available for flashing with odin on samsung-updates.com , this is the 2nd 4.0.4 update. (I'm still running the old 4.0.4 (P3113UEBLG5))
Click to expand...
Click to collapse
I tried updating it once with KIES and it got to a point and froze on the screen. I had to force the tablet to shut down and rebooted and the tablet was OK. Being a glutton for punishment I tried again with KIES and the LH1 update successfully updated my GT2 7 and the About screen confirms it. Directly after installing and rebooting I started getting error messages about Chrome crashing. I uninstalled Chrome browser and reinstalled it and all is well. No other problems. Do NOT really notice ANY difference at all.
The only problem I have is that NOW I have decided that I would like to root my GT2 7 and I am NOT sure the methods I see out there will work with the P3113UEBLH1 update.
Does anyone know if my GT2 7 - P3113UEBLH1 can be rooted safely??
grobin
I dont think IT is better than CM9
RomsWell said:
Im downloading it now. Ill post it when its rooted and deodexed
Click to expand...
Click to collapse
Can you please tell me what's different than the older UEBLG5 version? and btw can you upload the stock rom itself without root so I can test it? because I couldn't download :s
EDIT: I downloaded it via samsung-updates.com and flashed it with odin.
It's pretty much the same as UEBLG5 I didn't notice anything different, but I downgraded to UEBLG5 as samsung appears to have pushed back this update (UEBLH1), because when I connect the device to kies, it doesn't recognize it.
Bibicp said:
Can you please tell me what's different than the older UEBLG5 version? and btw can you upload the stock rom itself without root so I can test it? because I couldn't download :s
EDIT: I downloaded it via samsung-updates.com and flashed it with odin.
It's pretty much the same as UEBLG5 I didn't notice anything different, but I downgraded to UEBLG5 as samsung appears to have pushed back this update (UEBLH1), because when I connect the device to kies, it doesn't recognize it.
Click to expand...
Click to collapse
I think it broke wifi. Not sure what the change log says about it. If the Cam is fixed i think im just going to add it to the G5 update. And not bother posting this untill its confrimed OTA
RomsWell said:
I think it broke wifi. Not sure what the change log says about it. If the Cam is fixed i think im just going to add it to the G5 update. And not bother posting this untill its confrimed OTA
Click to expand...
Click to collapse
Sorry for the question, but what do you mean comfirmed OTA? Once kies told me about the UEBLG5 update, I couldn't install it with kies as it was lagging.
Next day I found it on the OTA update.
This one showed on kies for a day, then next day neither kies or the OTA udpates showed there was an update so it probably got pulled back?
I'm using the default ROM for my One X and I'd like to update it (I haven't since I got it 6 month ago); do I need to re-lock the bootloader and unroot it before I can use the OTA update? Also it's been a while since I even fiddled with my phones software so I forgot anything else I may have done, is there a way I can check to see what else has been done and if it's safe to update it?
Currently I have:
Android Version: 4.0.3
HTC Sense Version: 4.0
Software Number: 1.73.631.1
HTC SDK API Level: 4.11
HTC Extension Version: HTCExtension_403_1_HA_4
What firmware are u on currently for starters
Sent from my HTC One XL using xda app-developers app
I added the info to the original post
bman3k said:
do I need to re-lock the bootloader and unroot it before I can use the OTA update?
Click to expand...
Click to collapse
Your phone should be factory default before performing OTA updates or results may be unexpected.
Most OTA updates are patch file based and require the files to be exactly what is expected.
There have been known issues with root being detected and the OTA failing.
Rooted phones progressing with an update but root lost after the update.
System files being modified and the OTA failing.
Recovery must be factory; not TWRP or CWM.
CID and MID must suit OTA.
The only modification I would consider safe through all OTA's so far has been SuperCID.
If you have any interest in rooting and flashing custom ROMs, I would suggest rooting and unlocking the bootloader now, while you are on 1.73, and not updating via OTA. The latest 2.20 update will also update your hboot, which plugs the holes by which kernels and radios can be flashed from recovery.
Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms
omario8484 said:
Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms
Click to expand...
Click to collapse
Agree. If you are already BL unlocked and rooted, why go through the hassle of relocking the BL and returning to stock, just to wait for the OTA?
Just flash a JB ROM, as there are already stock and custom JB ROMs posted in Development.
Plus, until the OTA actually hits, we don't know if it will even be rootable. They have plugged the existing root exploits with every successive AT&T OTA for this phone so far. No reason to think any different for the JB update.
Just flash a JB ROM and stay rooted.
Ya I really like viper xl v3 . Just apply fix listed on op and you should be good to go
Sent from my HTC One XL using xda premium
Stock OTA is not WORTH IT IMO, been there
Reselling the phone is probably the only reason i'd revert to stock.
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Ok you're really lucky you didn't just brick your phone.... You want to stay in the att one x forums.... Notice theres a title diff. You're lucky it didn't succesfully flash or your phone would be dead... That's an international one x rom
bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Stick to the ROM's in our forum, I never heard of anything like that ROM for our phone sorry. Lucky you didn't brick it
O damn I feel very stupid now...
Can someone recommend me a JB ROM?
Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Edit: I figured out the Mount function in TWRP, so I know how to add new ROMs now
bman3k said:
O damn I feel very stupid now...
Can someone recommend me a JB ROM? Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Click to expand...
Click to collapse
Try them all, they are all good, the time it takes to ask for other peoples opinions you could have test driven them all yourself.
Are you looking for jb sense?
omario8484 said:
Are you looking for jb sense?
Click to expand...
Click to collapse
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?
bman3k said:
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?
Click to expand...
Click to collapse
Funny that you bring titanium up...titanium helps you back up apps it also backs up your app data...and for sms just download something from the market here's one download the app super backup and you can backup your sms
So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.
bman3k said:
So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.
Click to expand...
Click to collapse
You did a full wipe before hand right?
I did the factory, system, cache and dalvik cache wipes
Edit: I got it to work, not really sure what I did different =/
Hi, as the title states, yesterday I received a notification from Verizon that a new update is ready to be installed. I can only defer it for 5 days, which I did. I'm running TouchWiz Eclipse ROM 1.0. I went ahead and renamed SMD.apk to SMD.bak, because I read somewhere that's what I needed to do to prevent Verizon from pushing updates.
What I wanted to do is confirm that what I did would work (as in prevent Verizon from updating my awesome ROM and thus bricking my device). Also, I think the update is already downloaded and just ready to be installed. Will that affect anything? Would renaming SMD.apk still prevent it from being installed, or is that only to prevent it from being downloaded?? Please halp!!
Cheers,
ED
ExcludedDroid said:
Hi, as the title states, yesterday I received a notification from Verizon that a new update is ready to be installed. I can only defer it for 5 days, which I did. I'm running TouchWiz Eclipse ROM 1.0. I went ahead and renamed SMD.apk to SMD.bak, because I read somewhere that's what I needed to do to prevent Verizon from pushing updates.
What I wanted to do is confirm that what I did would work (as in prevent Verizon from updating my awesome ROM and thus bricking my device). Also, I think the update is already downloaded and just ready to be installed. Will that affect anything? Would renaming SMD.apk still prevent it from being installed, or is that only to prevent it from being downloaded?? Please halp!!
Cheers,
ED
Click to expand...
Click to collapse
Best way to check is to go into Settings/About Phone/Software Update. If it force closes then you're all set. Renaming or uninstalling "smd 1.0" causes the phone to not actively poll for future OTAs from that moment on. Using a file explorer, check in /cache and delete the update.zip for VRBMF1 cuz you deferred the OTA which means it saved to your phone already.
I checked Settings>About device but there's no Check for upgrade option. I assume it was taken out as part of the ROM. I went ahead and deleted some sort of fupgrade in /cache. Then went and wiped cache in recovery and fixed permissions just to top it off. I think I'm good!! Thanks
ExcludedDroid said:
I checked Settings>About device but there's no Check for upgrade option. I assume it was taken out as part of the ROM. I went ahead and deleted some sort of fupgrade in /cache. Then went and wiped cache in recovery and fixed permissions just to top it off. I think I'm good!! Thanks
Click to expand...
Click to collapse
i think eclipse is aosp not touchwiz , iam running the same thing but its aosp eclispe here the link to verified
http://forum.xda-developers.com/showthread.php?t=2142267 if it is you will never have problems of verizon trying to push ota updates
xavierxxx2p said:
i think eclipse is aosp not touchwiz , iam running the same thing but its aosp eclispe here the link to verified
http://forum.xda-developers.com/showthread.php?t=2142267 if it is you will never have problems of verizon trying to push ota updates
Click to expand...
Click to collapse
There is a touchwiz version, it just wasn't updated in awhile and it's pretty buried in the development section.
Sent from my SCH-I535 using Tapatalk 4 Beta
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.
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???