Related
Root MethodAmazon has just released a new firmware update, blocking the fastboot commands necessary for root/custom ROMs (fastboot boot). We need more information about this update. If people could update their tablet to this latest version without getting it stuck in the botloop, we could see the information regarding the update and get root out for this ROM ASAP. Thanks to anyone who sacrifices root/ROMs for development.
List of things you can't do:
Downgrade to an earlier release
Boot a .img from Fastboot
List of things you can do:
Install and use the Google Play Framework and Services
Root
Install Custom ROMS via FlashFire
Remove Lockscreen Ads
Remove Amazon Bloatware
Feel free to comments things that worked/didn't work on your device.
ANYONE WHO IS ON 5.0.x AND WANTS TO GO TO 5.1.1 WITHOUT ANY COMPLICATIONS AND KEEPING TWRP, GO TO THIS LINK: http://forum.xda-developers.com/showthread.php?t=3265594
Can anyone test if the Google Framework Install tutorial works on this update?
It does.
However, DON'T TRY TO DOWNGRADE BACK TO THE 5.0.1 FIRMWARE. IT WILL BRICK YOUR DEVICE. I found that out the hard way. It's stuck in a preloader reboot-loop.
Added list of what you are able to do on the update.
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
blueberry.sky said:
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
You have to go through the setup, but originally I just skipped that part, even though I was next to a Starbucks, and it didn't connect.
Doesn't Starbucks wifi require you to click to agree to their terms of use before you can freely browse or download? So Internet would not actually be available initially to the update script.
Pretty much, I trust amazon on this issue, as far as I can throw them. I don't want to presume that a OTA proccess won't silently connect, while the Fire otherwise appears to be waiting for the ok to connect to wifi.
Bloat removal
Hi just to add this thread it looks like you cannot remove any of the bloat as I was able to do on 5.01
craigs23 said:
Hi just to add this thread it looks like you cannot remove any of the bloat as I was able to do on 5.01
Click to expand...
Click to collapse
Thanks, added.
This is bullsh!t. the ENTIRE reason about 5,000 people bought this tab last week is because of root, fastboot and CM. If I get my tab soon I can offer any assistance you need. I'm not sure if it will be possible to dump any part of the system, boot, etc. without fastboot or twrp, but I'm sure we could figure something out.
blueberry.sky said:
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
When I setup mine it asked to turn on wifi I skipped it and said later.
Sent from my SM-N910T3 using Tapatalk
Has anyone tried kingroot on 5.1.1?
Experts please take a look at this
What was changed in OS 5.1.1?
If anyone can get the frimware update or capture it id like to test it out
running 5.1.1 & all I could manage to load was Google Account manager. The rest (Framework Services, etc) says something like "App not installed" & nothing else, every time I try.
scratch that..... found found a couple that did load for me.
Damn! I did this (tried to downgrade, got bricked) a day before you posted this. I should probably replace mine...
My unrooted Fire upgraded to 5.1.1 last night before I had any idea it was coming. I'm willing to try whatever is needed to assist with further research if I could be of any help.
unlikely it would work, but did anyone on 5.1.1 try
Code:
fastboot -i 0x1949 boot twrpfilename
Sent from my KFFOWI using Tapatalk
5.1.1 update file
Here is the 5.1.1 update file
snap42.com/update-kindle-full_ford-37.5.4.1_user_541112720.bin.zip
EDIT: Solution was to sit with OP5 technician which flashed my ROM to Oxygen 4.5.1. After this didn't do it, I RMA-ed it and got a new OP5.
EDIT: TL;DR: After updating OP5 to 4.5.5, It doesn't recognizes sim nor wifi, and can't rollback to 4.5.3 that did and stuck on phone setup (needs wifi). ADB devices is empty, I have Google USB Driver from SDK, Windows 10
Hello,
I just got a new OP5 today.
Opened it in the store, came with Oxygen 4.5.3 outta the box.
I putted the sim in, and I connected to the store's wifi, all was good and even had a phone call to my mother to check if the mic and speaker are working well.
Then when I got home, I upgraded the OS to 4.5.5 through the settings, where Android suggested. I'm new to OP and android (moved from iphone 5) and so if there is a right way to do it, and that's not it, I wouldn't have known.
Then, OP5 didn't recognize the sim anymore and couldn't start the wifi (switching it on wouldn't work, it would do nothing), so I tried Factory reset. Unfortunately it didn't reset the OS as well and now I'm stuck outside can't use my sim card or connect to my home wifi to setup the device.
Tried installing OP5 usb drivers (show when connecting the OP5 to PC) and press the power button and lower speaker volume together, then flush the 4.5.3 OS through USB, but it doesn't recognize ZIP folder and when I tried to unzip and send boot image (cmd->"adb sideload boot.img) it started and then failed at 0%.
Please help, the phone right now is unusable.
Tried the Factory reset through settings, but it took so long I thought it was stuck, so I did it through recovery screen.
Sounds like you got a lemon... I'd take it back and see if they'll swap it for another. Less than a week should be replaced immediatelly, at least that's been my experience here in Oz...
ultramag69 said:
Sounds like you got a lemon... I'd take it back and see if they'll swap it for another. Less than a week should be replaced immediatelly, at least that's been my experience here in Oz...
Click to expand...
Click to collapse
Why should it be replaced in less than a week? Also, isn't there a fix for adb problem so I could flash 4.3.5? Maybe a remote takeover?
Mine had 4.5.3 on it when I got it, updated to 4.5.4 then manually downloaded full rom, placed on internal memory and flashed 4.5.5 through the settings.
Had zero problems with WIFI before, during and after the update. No problems since.
Generally updating to a higher firmware version won't allow you to regress back to the lower, not sure with Oneplus as this is my first.
I'd also, if you can boot into Android go to settings nd check my IMEI numbers to see if they have been wiped (this can cause the sim to not be recognised) . If you have no IMEI then that is a BIG problem which will require an RMA unless you had backed up your efs files which from your description I doubt..
If the IMEI is OK I would download the full firmware version from here - https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190 - then using PC put the FULL ROM onto the internal memory then go to recovery and flash.
I'd also then unlock my bootloader(Just remember though that the phone will wipe all data after unlocking bootloader) and install TWRP - don't forget to 1st enable developer mode in settings and then allow usb debugging and OEM unlock - make a backup of the working stock rom and put it somewhere safe - home PC, in case this happens again. Best idea is to use the all-in-one tool, here - https://forum.xda-developers.com/on...l-skipsoft-android-toolkit-oneplus-5-t3625419 thankyou MSkip.
ultramag69 said:
Mine had 4.5.3 on it when I got it, updated to 4.5.4 then manually downloaded full rom, placed on internal memory and flashed 4.5.5 through the settings.
Had zero problems with WIFI before, during and after the update. No problems since.
Generally updating to a higher firmware version won't allow you to regress back to the lower, not sure with Oneplus as this is my first.
I'd also, if you can boot into Android go to settings nd check my IMEI numbers to see if they have been wiped (this can cause the sim to not be recognised) . If you have no IMEI then that is a BIG problem which will require an RMA unless you had backed up your efs files which from your description I doubt..
If the IMEI is OK I would download the full firmware version from here - https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190 - then using PC put the FULL ROM onto the internal memory then go to recovery and flash.
I'd also then unlock my bootloader(Just remember though that the phone will wipe all data after unlocking bootloader) and install TWRP - don't forget to 1st enable developer mode in settings and then allow usb debugging and OEM unlock - make a backup of the working stock rom and put it somewhere safe - home PC, in case this happens again. Best idea is to use the all-in-one tool, here - https://forum.xda-developers.com/on...l-skipsoft-android-toolkit-oneplus-5-t3625419 thankyou MSkip.
Click to expand...
Click to collapse
I can't pass the "Connect to Wifi" in the initial setup of the android, as it finds no wifi networks (but of course there are, when I use the sim in my iphone it works properly and there are wifi networks). So I don't know how can I get the IMEI number.
Right now my PC recognizes the OP5 connected via USB, but "adb devices" bring back empty list.
I think that once I get that working, I could unlock the bootloader. But I can't seem to be able to enable dev mode in settings - I can't get there.
I can only get to the recovery screen beyond the initial steps of setting up android.
Right now there is no important data on the phone and I have my laptop which is virgin to ADBs and Drivers (didn't use it to try to resolve it).
What driver and where do I get the right ADB so I could load 4.5.3 from usb to the phone?
When you upgraded, did you wipe cache and dalvik?
Binary Assault said:
When you upgraded, did you wipe cache and dalvik?
Click to expand...
Click to collapse
Wiped after the upgrade whem problems started
Might be wrong but I thought you could skip the wifi select screen on the setup wizard.
If you can get to Android you need to go to settings, scroll down to about phone and tap around 8 times on build number to enable developer settings.
You might be able to, might, pull down the settings menu in the wizard and bypass the wizard.
ultramag69 said:
Might be wrong but I thought you could skip the wifi select screen on the setup wizard.
If you can get to Android you need to go to settings, scroll down to about phone and tap around 8 times on build number to enable developer settings.
You might be able to, might, pull down the settings menu in the wizard and bypass the wizard.
Click to expand...
Click to collapse
It doesn't seem like I can skip it. Can't pull down a menu or anything
I guess only Oneplus can help me now?
Do you have any suggestion on fixing adb so it would recognize the OP5?
No, you need to enable debugging in developer settings for ADB to recognise.
Time to RMA...
ultramag69 said:
No, you need to enable debugging in developer settings for ADB to recognise.
Time to RMA...
Click to expand...
Click to collapse
Welp it is a pickle.
Going to go live chat with OP "level 2" representative.
See if they wipe the phone out and restore an older ROM.
If that't not going to work, RMA it is :/
Shame. A new phone. Took only one picture with my dad when we opened it back at the store. nothing else.
Unfortunately bad things can happen... You just got to be the one who got the dud this time round.....
Here's hoping it's the last time....
you can force update to a fresh installation of 4.5.5 by putting the 4.5.5 full zip into your phone in a folder called "update". Reboot to recovery im assuming you have stock recovery and follow the steps until you find the option that says something along the lines of "Update manually". It will detect if you have an update folder stored on your phone and it will begin reinstalling OOS 4.5.5. It sounds like a software problem but could be a hardware problem. Rule out the first option before RMA the latter.
OcazPrime said:
you can force update to a fresh installation of 4.5.5 by putting the 4.5.5 full zip into your phone in a folder called "update". Reboot to recovery im assuming you have stock recovery and follow the steps until you find the option that says something along the lines of "Update manually". It will detect if you have an update folder stored on your phone and it will begin reinstalling OOS 4.5.5. It sounds like a software problem but could be a hardware problem. Rule out the first option before RMA the latter.
Click to expand...
Click to collapse
When I connect the OP5 to the PC there are no folders under it (Computer -> OP A500 -> no folders), but I'll try and give it a shot. see what happens. Will update this reply.
Update:
After Oneplus flashed Oxygen 4.5.1 on the phone and some other magic I was able to skip wifi step on setup, yet still when I try to activate it it won't budge. the slider won't move and it looks as the page is being refreshed. Also, when I try to get into sim section in settings it would just freeze and alert the program stopped and suggest to close or wait.
Oneplus says it is hardware issue, and the fact it happened when I upgraded to 4.5.5 from settings menus is coincidence. They say I need RMA it.
If anyone knows how to fix it then I'm more than welcome to hear it.
EDIT: it also won't shut off unless I long press the power button.
My tablet is completely stock--bootloader has never been unlocked or modified in any way. After the upgrade to Nougat, bluetooth wasn't working. I read somewhere that a factory reset had helped someone else with a similar problem. I did a factory reset in recovery, which was apparently a mistake. When the tablet rebooted and began the initial setup, it required me to log in to my Google account, providing a message that reads "The way you restored factory settings may pose security risks. Please verify your identity with your Google account. Please connect to the internet first."
This ordinarily wouldn't be a problem; I have access to my Google account and normally have no trouble logging in. However, the tablet defaults to the Google voice keyboard, and I can't figure out how to use that to type my user name and password.
Does any have a suggestion as to how I can do any of the following things?
Change to a different keyboard
Bypass the Google login
Reset the tablet completely so the security prompt doesn't appear
Something else that will allow me to boot my tablet
I have tried multiple times to contact Huawei customer support, as my tablet is still under warranty, but they've ignored me. If anyone has a suggestion, it would be much appreciated.
I solved the problem by plugging in a USB keyboard via OTG. However, the Bluetooth issues weren't resolved, and several system applications were missing or unstable. I ended up unlocking the bootloader and flashing the most recent full firmware update through TWRP. That seems to have solved all of the issues I had.
Sorry about the issues and thanks for posting the update. I am thinking about buying this tablet but I'm reading a lot of weird stuff about it. Still undecided.
direwolf1 said:
I solved the problem by plugging in a USB keyboard via OTG. However, the Bluetooth issues weren't resolved, and several system applications were missing or unstable. I ended up unlocking the bootloader and flashing the most recent full firmware update through TWRP. That seems to have solved all of the issues I had.
Click to expand...
Click to collapse
How did you unlock after upgrading to EMUI 5?
starfall88 said:
How did you unlock after upgrading to EMUI 5?
Click to expand...
Click to collapse
I just requested the unlock code from Huawei, normal method. Then I installed greatslon's TWRP from here: https://androidfilehost.com/?w=files&flid=125388 via fastboot.
direwolf1 said:
I just requested the unlock code from Huawei, normal method. Then I installed greatslon's TWRP from here: https://androidfilehost.com/?w=files&flid=125388 via fastboot.
Click to expand...
Click to collapse
Could you explain how to unlock the bootloader? I have experience installing roms, rooting but have never unlocked bootloader.
Sent from my SM-P550 using Tapatalk
I have spent the better part of the evening trying to figure out what is wrong with the full update package for Android 12 for NA/Global. This is the one way out of the many I tried, that reliably worked for the KB2007 T-Mobile USA device to get it to running Android 12 without issues on the North American/Global firmware.
This ideally is for those of us that have a KB2007 that used the MSM Tool conversion to the EU firmware. Using Local Update does not fully convert to the NA/Global, even when using a full update package, which leaves the device with issues. For some reason, when updating to the KB2005 Android 12 using the full firmware image, you lose the second SIM slot, which just makes it worse. After plenty of flashes to figure this out. I have figured out a complicated mess of a way to do so.
I tried going to a couple of the full updates before Android 12 from the EU and still had issues after the update to Android 12 with performance. That is why I decided upon this longer method. Update using the full KB2005 image to Android 12. Easiest place to get it is from Oxygen Updater. Install it via Local Update. Download the rollback app, install it, and download the rollback package to flash through the rollback app. Rolling back to KB2005 using the downgrade image returns dual-SIM to the KB2007. That will have wiped your device so proceed through the setup until finished. Download Oxygen Updater again, download the stable KB2005 Android 12 incremental update through the System Updater, install it, and you should be as close what a KB2007 can get to a KB2005. I tried the full package update but that always disables dual-SIM after updating to Android 12, whether you do a factory reset before the flash and after or not.
Having an MSM Took to directly convert the KB2007 to KB2005 might have made this somewhat easier.
Sadly, it didn't survive a reboot. SIM 2 is still shown, but disabled. There is no way to enable it that I have found, but at least it is reading the info from the SIM 2. Does anyone know of a way to force the toggle for SIM 2?
dang i was coming here to see if anyone was able to do this and or had issues doing so. looks like if we are on an unloced tmo version phone we might be stuck with oos11 till things get figured out if they do. bummer. i really wish i had not waited when they put them on sale and got the normal 8t vs this tmo version those were sold out by the time i saw the sale though. just like i still cant figure out how to get vowifi / wifi calling working on this ive tried everything i could find online and nothing works to add those settings back
oddly im on the latest version of oos11 on the kb2007 converted and i can see sim 1 and 2 but sim 2 is greyed out. i actually was trying to get that working on oos11 and for me it does not work. did you have it working on 11?
Same problem with 12 here. We accidentally updated to 12 via the OTA update and it not only gave us the same symptom (SIM 2 visible, but disabled), but it also screwed up internet connectivity on SIM 1. Calls and text still seemed to work, but internet only via WiFi.
I spent last night and a good chunk of today troubleshooting it, and finally just went back to fully operational latest version of 11 via MSM and local update. It would be nice to be on the latest version, but browsing through the OnePlus forums, it looks like 12 is still a hot mess anyway.
bummer hopefully someone will figure it out sooner or later. i really dont want to go back to the tmobile rom in order to update
I just talked to OnePlus support center and they confirmed unlocked version will not be stock again Once they will finish selling T-Mobile version webpage will be cleaned from any 8T info. I really want to get unlocked for 399. and now only way to get this go for KB2000 CN version that sill stocked. The price for T-Mobile version is good 349 but based on conversion mess I don't want go for that. Also I am sure TM will stop on OOS11 and will not rollout OOS12 ever.
i agree ^^ any updates from anyone on this? any type of workarounds? this sucks i wish i would just went with the one off amazon instead of directly through oneplus now. we have three here we love the phone but i am not sure we will ever be able to upgrade now.
bigfry said:
Same problem with 12 here. We accidentally updated to 12 via the OTA update and it not only gave us the same symptom (SIM 2 visible, but disabled), but it also screwed up internet connectivity on SIM 1. Calls and text still seemed to work, but internet only via WiFi.
I spent last night and a good chunk of today troubleshooting it, and finally just went back to fully operational latest version of 11 via MSM and local update. It would be nice to be on the latest version, but browsing through the OnePlus forums, it looks like 12 is still a hot mess anyway.
Click to expand...
Click to collapse
Can you check the about page after upgraded to OOS12 is this sill showing wrong picture and missing some info?
bigfry said:
Same problem with 12 here. We accidentally updated to 12 via the OTA update and it not only gave us the same symptom (SIM 2 visible, but disabled), but it also screwed up internet connectivity on SIM 1. Calls and text still seemed to work, but internet only via WiFi.
I spent last night and a good chunk of today troubleshooting it, and finally just went back to fully operational latest version of 11 via MSM and local update. It would be nice to be on the latest version, but browsing through the OnePlus forums, it looks like 12 is still a hot mess anyway.
Click to expand...
Click to collapse
I have the same issue you had with the network on mobile data. I downloaded oos 11 and used magisk to install os11 to keep root , however I still have data isdue on the mobile network. Fine on wifi. Any suggestions?
you may want to try to use the msm tool to go back. or try the posted downgrade tool. i personally used the msm tool to go back to stock then re upgraded to latest 11. i hope i dont get hit with it myself. this was on my daughters phone.
Thanks for sharing this instruction!
So basically:
0) Oxygen Updater can be used to download the full/incremental OOS 11/12 kb2005 images mentioned below. (Probably also need to use MSM tool to rebrand as EU version before all these?)
1) System Update - Local Update to install OOS 12 kb2005 (full);
2) "Rollback app" to OOS 11 (rollback);
3) Regular system update to OOS 12 (incremental).
It seems pretty reasonable. Would you instruct more on what "rollback app/package" you use? This is the closest I found online: https://www.droidwin.com/downgrade-oneplus-8-pro-8t-to-oxygenos-11-android-11/ but please correct me if it is not the right one.
Does this method still work now? Do you have dual-sim dual volte/wifi calling working?
jllll said:
Thanks for sharing this instruction!
So basically:
0) Oxygen Updater can be used to download the full/incremental OOS 11/12 kb2005 images mentioned below. (Probably also need to use MSM tool to rebrand as EU version before all these?)
1) System Update - Local Update to install OOS 12 kb2005 (full);
2) "Rollback app" to OOS 11 (rollback);
3) Regular system update to OOS 12 (incremental).
It seems pretty reasonable. Would you instruct more on what "rollback app/package" you use? This is the closest I found online: https://www.droidwin.com/downgrade-oneplus-8-pro-8t-to-oxygenos-11-android-11/ but please correct me if it is not the right one.
Does this method still work now? Do you have dual-sim dual volte/wifi calling working?
Click to expand...
Click to collapse
I just tried this method and dual sim is not working.
alphahere said:
I just tried this method and dual sim is not working.
Click to expand...
Click to collapse
Thanks. I can't even get rollback app working so I gave up. Dual sim immediately after MSM again. Then I just did regular system update to the latest OOS software. Probably just switch to pixel next year.
I can fix this issue but for this i need
Unpack repack rom which is not possible
I try all kitchens but not workable if anyone can help me to unpack repack rom then i can fix it i even got the problem spot
Just need to test it now
If anyone able to do this just tell and i can fix it
But make sure don't mention payload dumper
I need extract whole rom sys ven prod etc
jllll said:
Thanks. I can't even get rollback app working so I gave up. Dual sim immediately after MSM again. Then I just did regular system update to the latest OOS software. Probably just switch to pixel next year.
Click to expand...
Click to collapse
Concur - Oneplus needs dual sim in the US. The carriers have blocked this for years but that wall in falling. Almost all the flagship and some midrange phones have e-sim and physical sim. So dual sim is here to stay. Oneplus needs to get on board the train.
I have this some issue after upgrading to Android 12. Is there any way to roll-back to Android 11, WITHOUT losing data and needing to wipe? And would it then allow the dual-sim to be working again?
Also, has anyone else tried the above method and had success with having a dual-sim Android 12 using the T-mobile KB2007?
raven911 said:
Also, has anyone else tried the above method and had success with having a dual-sim Android 12 using the T-mobile KB2007?
Click to expand...
Click to collapse
I can fix but need to unpack repack rom
If anyone can guide me tu unpack
System_ext
System
Vendor
Product odm then I'll make fix rom for this
Can build for samsung but in this I'm stuck with dynamic partitions
Mr Hassan said:
I can fix but need to unpack repack rom
If anyone can guide me tu unpack
System_ext
System
Vendor
Product odm then I'll make fix rom for this
Can build for samsung but in this I'm stuck with dynamic partitions
Click to expand...
Click to collapse
If you unpack / repack, then will we lose SafetyNet and Widevine?
raven911 said:
If you unpack / repack, then will we lose SafetyNet and Widevine?
Click to expand...
Click to collapse
Ofcourse not its not rooting process
Even i can do with rooted device but if have fully rw access
Hello everyone. I recently purchased a used Pixel 4. Past owner said WiFi+Data stopped working after updating Android and that the phone is unlocked and carrier-free. I need to unlock bootloader in order to install GrapheneOS but it is greyed out. As you can see in the screenshots, it seems like the phone is not recognizing WiFi and IMEI hardware while booted. IMEI does show up in the barcode menu option in fastboot. System UI crashes if I try to open WiFi config. The only thing I could try was tethering via Bluetooth from my other phone and updating Android OS and apps. Already tried wiping everything and forcing phone to connect to Google while on Bluetooth tethering by pressing (*#*#2432546#*#*) in the dialer as sugested here: https://source.android.com/setup/contribute/flash#preparing-your-device
This doesn't show any success or error message.
One thing that may have happened is this: https://www.phonearena.com/news/google-pixel-android-12-verizon-update-issue_id136367
Apparently Google sent OTA Verizon update to unlocked Pixel 4's by mistake. Maybe the wrong software is what is making it not recognize WiFi+Data?
Current installed build is 12.1.0 (SQ3A.220605.009.A1, Jun 2022). Maybe I should wait for a new SP* instead of SQ* build to come out and try installing it? This is because P is for the main platform branch as explained here: https://source.android.com/setup/start/build-numbers#build-ids-defined
Hopefully it comes out before October since that is the end-of-support date.
OTA builds: https://developers.google.com/android/ota#flame
Other option would be to try out this but it seems the riskiest and last resort option:
Unlock carrier locked bootloader Pixel [BETA]
UPDATE AS OF 16 OF MAY 2023 This project isn't working right now, but I am still working on it. However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get...
forum.xda-developers.com
And yet another option would be to purchase a new board and replace it.
What do you think? I tried submiting the IMEI to T-Mobile's site and it says it is OK to be ported. Verizon's site didn't let me submit the IMEI I don't know why. And for AT&T I didn't find any site for that. IMEI checks say it is not blacklisted.
Did u solve this?