Related
I don't know how strict people are about "searching" things before posting on the forums, but I rather get yelled at by some nerd on the internet, than to have my $350 device screwed over because I followed the wrong tutorial. Anyways here are my questions:
1) I bought this device from someone brand new, and it came out of the box configured to work with Windmobile, but I was able to get my FIDO SIM card to work by simply inputting it into the device. So does this mean that my device is already unlocked?
2) I still have the old 2.2 version on my phone, and I want the new version (2.3), but since I cannot update the OS from the device itself, I don't know what method I should follow from my computer, also I am afraid that I might lose my unlock (if it is) with the update.
Please link me to the proper tutorial, or give me some insight on my problem, Thank you.
I have just moved this question here from the General section, hope that's the right move.
I have just managed to root my old LG P880/4xHD using advice from this forum. Thought I would try on an old phone first. One reason I tried is because I cannot update Android via the usual About phone, Software updates, Check now for updates. The Android version installed is 4.0.3. I am in Australia and it is possible the phone is an overseas model (got it from a friend in LG). Has "Not for Resale" stamped inside the back cover. When I try to update Android, I get an error message "Registered Error - Your device is not registered yet." I had hoped rooting would get around this but it hasn't. Have looked up old forum posts and there is talk of using .kdz files and all sorts of other things. Can anyone help me get around this registration issue but please be aware I am a novice and most of the older posts I read, I couldn't understand, so simple explanations please. Thanks, Peter
pdonahue said:
I have just moved this question here from the General section, hope that's the right move.
I have just managed to root my old LG P880/4xHD using advice from this forum. Thought I would try on an old phone first. One reason I tried is because I cannot update Android via the usual About phone, Software updates, Check now for updates. The Android version installed is 4.0.3. I am in Australia and it is possible the phone is an overseas model (got it from a friend in LG). Has "Not for Resale" stamped inside the back cover. When I try to update Android, I get an error message "Registered Error - Your device is not registered yet." I had hoped rooting would get around this but it hasn't. Have looked up old forum posts and there is talk of using .kdz files and all sorts of other things. Can anyone help me get around this registration issue but please be aware I am a novice and most of the older posts I read, I couldn't understand, so simple explanations please. Thanks, Peter
Click to expand...
Click to collapse
it is a development edition not a consumer edition. read here .
dont try anything else than root if u dont have good knowledge or u will trash the phone.
I thought I would quickly let New Zealand P9 Lite owners know that for the past month I have been in a battle with Huawei. After months of saying they would be releasing EMUI 5 in New Zealand they have confirmed the past month that they, and I use their words "have no intention of releasing this update in New Zealand". Essential our phones stopped being supported in New Zealand in Septemeber 2016.
The good news is Huawei do not understand New Zealand law, they think that their TOS override the consumer guarantees Act. There is two reasons that you can get a full refund, one is that they have been releasing this update overseas and are simply just not releasing it in NZ. The other that last october Nick Stephens from Shellphish found some major bugs in the trust zone that allows a person to bypass the fingerprint scanner. Huawei released an update to this in december 2016 but did not and refuse to release it to NZ.
I talked to MEBI who advised me that the applicable law was.
“there is a guarantee that the manufacturer will take reasonable action to ensure that facilities for repair of the goods and supply of parts for the goods are reasonably available for a reasonable period after the goods are so supplied.” http://www.legislation.govt.nz/act/...sw_096be8ed814da84a_facilities_25_se&p=1&sr=1
That said we have just had a full refund for our 3 p9 lites. I suggest anyone else with a p9 lite that is waiting for these updates follow the same path and get a refund
Hmm, I purchased mine from Noel Leeming in July 2016, am I still eligible for the CGA return? I kinda want Nougat
I noticed on a geekzone post in mid June that someone got a reply from the Huawei Facebook page promising NZ p9 nougat!
Response from Huawei NZ "Please be advised the P9Lite software upgrade will be available in New Zealand towards the end of the year. Thanks"
Hi everyone. I work at Spark and have been talking with our device delivery manager. As of last month Huawei was saying that the update was not in the pipeline.. now they are telling us that the nougat update is in testing. I asked our team, testing what as it's already been released around the world?!
Either way. I got sick of waiting and followed a guide on here to change the localisation to update to b380. Let me tell you Nougat works much better!
Quintman said:
Hi everyone. I work at Spark and have been talking with our device delivery manager. As of last month Huawei was saying that the update was not in the pipeline.. now they are telling us that the nougat update is in testing. I asked our team, testing what as it's already been released around the world?!
Either way. I got sick of waiting and followed a guide on here to change the localisation to update to b380. Let me tell you Nougat works much better!
Click to expand...
Click to collapse
Which guide did you follow? I couldn't find anything for VNS-L22
nzf said:
Which guide did you follow? I couldn't find anything for VNS-L22
Click to expand...
Click to collapse
Yeah it was a combination of a couple threads on here. Let me see if I can put something together.
Below is the steps I used to successfully change my NZ p9 lite to the global Nougat rom. USE AT YOUR OWN RISK. You 100% will reset your phone so backup and remove your data. I do not take any responsibility for this, you are attempting at your own risk. All credit goes to the authors in the links provided.
Step 1: unlock bootloader: https://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
I did not use the tool to ender the code in this link, I just used ADB
Step 2: Using k1ll3r8e ‘s Toolkit, https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873
a. On his post, download pkg.L22C636_DS.zip. This gives you the oem info that you will need.
b. Flash TWRP (recovery) to the phone.
c. Backup stock recovery to be safe!
d. Restore oem in TWRP, but use from L22C636 info.
Step 3: Download Update.zip for VNS-L22C636B140 (have to be honest, not sure if I did B140 or 120…) from https://forum.xda-developers.com/hu...huawei-p9-lite-firmware-compilations-t3517124
A. Create a folder called dload in SD-card main.
B. Extract the file in dload UPDATE.APP folder from update.zip above
C. Turn off phone, disconnect from computer
D. Press both Volume keys (VOL UP and DOWN) and then the power key and hold until the software update starts.
Step 4: This will vary. For me, when I flashed the C636 oeminfo file it somehow relocked my bootloader and removed TWRP… if yours doesn’t you can follow standard procedure to do this.
Now you are on the global B636 rom.
Step 5: im not sure if eventually would get updated or not, but I then used Firmware Finder to force update (can get in play store): https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
I went from B140 to B360 to B380
What a difference!
Very interesting subject. I have enquired with Huawei to verify this. Debatable if I get any response; but worth a shot.
Can anyone download the VNS-L22C636B*** update files from the supplied link? I tried all 3, with both Chrome & Firefox, & no luck.
citizengkar said:
Very interesting subject. I have enquired with Huawei to verify this. Debatable if I get any response; but worth a shot.
Can anyone download the VNS-L22C636B*** update files from the supplied link? I tried all 3, with both Chrome & Firefox, & no luck.
Click to expand...
Click to collapse
Sorry looks like the links are dead now . I do have it downloaded. let me see if I can get it up. If not, you can also use the Firmware finder to download them.
Well, I did receive a response to my query from Huawei. One can only hope it is accurate.
"Dear,
Thank you very much for contacting Huawei.
With regards to your inquiry, we would like to sincerely apologise for the delay as the update is still undergoing some testing on our devices to ensure that our users will fully enjoy the Nougat update for our devices. Not to worry as the update will be ready very soon and that you may stay tuned to our Official FB Page and Consumer Page for further updates pertaining the release of the device's update in the links below:"
Hi All.
I trust you well. I was wondering if I could request your assistance with updating my TF701T to a new version of android. I have tried many methods and none has worked. I am actually more confused now as to where to start and what to download and install. :silly:
If possible maybe direct me where I could get a step by step guide with the links to the correct downloads/procedure.
I imported the pad from USA to South Africa and barely used it.
Kind Regards
Rob
(h-tee-tee-pee-s) androidbiits.com/root-asus-transformer-pad-tf701t-easily/
probably use the versions of magisk + twrp that are linked at the site, as they are tested with that hardware -- the latest versions may not work. i do not own that particular device and am not a programmer -- just trying to help you out. search the web for info if anything is confusing in the instructions -- i can't really walk you through it, but the person at that site may be able to help you out if you get stuck.
you'll need to connect the asus pad to a computer, so you'll need the usb data cable & adb installed on the computer.
you will likely also need open gapps to get the play store + apps working. select processor type, android version, then variant. you can find it here ==> (h-tee-tee-pee-s) opengapps.org <== but i'm not sure how long that will be functional, as hosting is apparently migrating to sourceforge.
please note that there are no w's in either address mentioned previously.
here's an explanation of gapps ==> (h-tee-tee-pee-s + w's) androidfreeapks.com/apk/download-gapps-for-android/
...and there are also download links for various variations at that last address too. cheers!
you will not be able to install *the latest* version of android (it's just plain not out there as a mod for a device this old) but you *can* get something a bit newer than the stock version on it.
best of luck!
one last thing (pertaining to the very first thing you have to do) is unlock the bootloader.
(h...s + w's) asus.com/us/Tablets/The_New_ASUS_Transformer_PadTF701T/HelpDesk_Download/
you will find the utility to do so at the above site. select Android, then under "Utilities"
click "See All Downloads" - therein, the 2nd thing from the bottom in that section is the unlock tool,
which says: Unlock Device App. V1.o (there's only one thing with that name. size is 448.82 kb)
and it will only work from the stock Android version, which i assume is still functional on your device.
Magisk is apparently a newer replacement for SuperSU, which doesn't flag the system as altered...
therefore you *may not* need to install Gapps if using Magisk - that seems logical to me, but i am not certain.
thanks for the assistance Dorkus.........this is killing me....but I will keep the faith and try again
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
bobwho said:
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
Click to expand...
Click to collapse
Same here. I tried to contact Asus but no hope... We're completely blocked unless they do something? No other way to unlock?
greetings all, it is i, dorkus, of the house of mallorcus. haha. my name is actually reni.
xda keeps locking me out for some reason. i've now created 2 accounts (3 including the one from which this comment is posted) one even with a dedicated e-mail address just for this, but if i try to log in with either one, i get some "invalid" whatever message. admins: what have i said that was grossly incorrect? those links may not be presented in absolutely the most coherent way, but they're the best reasonable explanations of the procedure involved that i could find with about an hour or 2 of research, which i did because of intending to get one of these devices myself (which has now occurred! yay). besides that, who else with greater experience has chimed in on this thread? yes, i've reset my password, on both accounts. after i do so, both times: same "invalid" message. it's wasted over an hour of my time, when i'm just trying to help these people. it's highly annoying & if it continues, well, they'll just have to go it on their own.
to the point:
as luck would have it,
i was able to acquire one of these devices, still in superb condition, for a great deal from ebay. i have been in contact with Asus support & the word is: it's an EOL product, so the unlock servers have been shut down & there is currently no recourse end users have for unlocking their devices. i feel it's doubtful that they'll fire up a server again, but maybe we can pester them enough to develop a fastboot unlock tool? it sure would have been nice if it worked like that in the first place, but oh well, like the song says:
you can't always get what you want.
i will surely let you all know if am able to make any progress on unlocking my TF701T.
footnote: i also have a TF700 model which is in fact unlocked, has TWRP installed, and is running Android 5.1.1 {zombie-pop} which works a bit better than the Cyanogen mod flavor that it came to me with: somewhat improved user experience, maybe a little snappier too, but speed improvement is fairly minimal. most importantly, almost all of my apps work on it - a few don't even have an installer for Android 4 at the Play Store. the 701 is noticeably more responsive than the 700 model, even running 4.2.2 - the main issue with it for me is not being able to run all of my apps, some of which are purchased. i'd probably sell the 700 if i could get everything on the 701. oh well. it's an excellent reader + portable video viewing device even at stock. it's definitely worth what i paid in the condition received, but it'd be even better if i could unlock the bootloader & get a newer version of Android on it! i could possibly even be so happy that i'd float a couple bux Tim Duru's way, the guy primarily responsible for porting Android 6+7 (the latter of which apparently does not have a working camera) to this device.
footnote #2: the first day i got the 701, i tried to do a firmware update (proper region, latest available. full battery charge. the battery in the one i picked up is in fantastic condition, the thing is practically brand new + functions nicely... but now Asus won't let me unlock it, even though it's well out of warranty! grrrrr) which crashed mid-way & then it proceeded to get into an update / crash boot loop. i was pretty sad for a while, but did not give up & found a way to restore the original firmware (which turned out to be a very minor upgrade) from the SD card, thanks to information in a post here in the xda forums. that post is the link which follows. my thing would still go into fastboot (albeit slightly corrupted) + recovery mode, which enabled an SD card firmware flash to happen {...and lo, my little slab of Jelly Bean was resurrected...} so i did not require the NvFlash tool at all... but it's still there at the provided links in that thread.
to summarize the procedure:
1) format an SD card to fat32
2) download the appropriate firmware from Asus [**please note the region: if you flash the firmware from a wrong region onto your device, you will -hard- brick it + will then be required to use the NvFlash tool**]
3) un-zip the firmware (not completely, just remove nesting - so you have only one zip file)
4) rename the one remaining zip file: t4_sdupdate.zip
5) put that file on the root directory of SD card, then into the tablet (while turned off)
6) invoke recovery mode (power + vol down) & choose the recover [RCK] box (hit volume up, while it's the selected of the 3 choices) and from there the firmware update happens automatically. you can apparently upgrade to any official firmware by this method, but **cannot** downgrade... so i'd suggest leaving it at 4.2.2 until we are 100% sure that there are zero bootloader unlock options, because apparently the unlock tool, from what i understand, only works from the original 4.2.2
without further ado:
https://forum.xda-developers.com/transformer-tf701/tf701t-nvflash-unbrick-solutiontested-t3742848
it's now a few hours later from my original post, near bedtime for me, and the xda gods let me log into this account to make this edit... and it's even allowing URLs now! will wonders never cease? not sure what the problem was earlier, but it was quite annoying. anyway, if it lets me log into the account with the dedicated xda e-mail address, that's the one i'll use in future. username is renigade.
fly a kite said:
...
Click to expand...
Click to collapse
Hello @fly a kite @dorkus mallorcus @renigade
Please consult the inbox of your private messages. Thanks for your cooperation!
Stay safe and stay healthy!
Regards
Oswald Boelcke
Hi,
for my Google Pixel 5 I want /e/os/.
Two instructions how to accomplish this. To flash /e/os onto a Google Pixel 5, the smartphone need to have Android 12.
My Google Pixel 5 has Android 13 (I received a New Old Stock device in a unopened box with Android 13. So no tinkering
beforehand.)
I found this archive of Android 12 images - all for the Google Pixel 5 and all Android 12:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
How can I determine and choose the correct image to flash?
Cheers!
Etymotics
12.1.0 (SQ3A.220705.003.A1, Jul 2022) is going to be the latest android 12 build which should be compatible.
Hi noidea24,
thank you for your post and the information. That helps me a lot - I was confused by the shear amount of images.
Do you know a thread which may have the things I want to achieve as topic ? I tried to search with keywords
like "Google Pixel 5 /e/os" and similiar, but it looks like the search found all threads containing GOOGLE *and* all threads with PIXEL *and* all....and so forth. I would need a second search engine to skim through the results...\
Cheers!
Etymotics
What are you looking for specifically? There's not really much info on e/os on the pixel 5. It works well, but the development is slow. Why e/os over similar projects with updated android versions like Graphene, Calyx, Copperhead?
e/os is not daily drivable, recommend not to install.
e/os was recommended to me by Marcel Bokhorst, the author of XPrivacy.
But as it seems, I had bad luck with the phone I bought:
The "OEM unlock" is greyed out and I know of no way to unlock the bootloader.
It currently runs on Android13 and last update was Dec. '22.
My intention behind all this was to have a de-googled phone because I [CENSORED] this
tracking and spying and "owning" a device, which I cannot control to 100%.
Anything else I can do to achieve this?
PS: My phone may be is one of these [CENSORED] Verizon devices. It was originally packaged
and as it seems never used before...
Where did you buy your phone? Ebay? A retailer?
Is there a keyword "Locked" or "Unlocked" anywhere on the website?
If the product listing didn't mention anything about it being carrier locked, I suggest requesting a refund or a replacement.
The "OEM Unlock" greyed-out is most definitely due to it being a carrier locked device and you're out of luck.
Also, if you truly want a de-googled OS, I recommend Graphene OS. https://grapheneos.org/
Etymotics said:
e/os was recommended to me by Marcel Bokhorst, the author of XPrivacy.
But as it seems, I had bad luck with the phone I bought:
The "OEM unlock" is greyed out and I know of no way to unlock the bootloader.
It currently runs on Android13 and last update was Dec. '22.
My intention behind all this was to have a de-googled phone because I [CENSORED] this
tracking and spying and "owning" a device, which I cannot control to 100%.
Anything else I can do to achieve this?
PS: My phone may be is one of these [CENSORED] Verizon devices. It was originally packaged
and as it seems never used before...
Click to expand...
Click to collapse
Not to give you false hope but did you connect to wifi on your first time through setup? If you don't, OEM unlock will be greyed out, regardless.
Hi Alex,
(NOT meant as any form of criticism or complaint... )
...I am a little confused here.
Other posts (not necessarily on this forum...can't remember) say: "Pull out the simcard, disable Wifi and DON'T contact anything, only skip through the setup..."
At the moment I only have a simcard of the wrong size...but I enabled Wifi but did not update anything in fear of getting an even stronger patch to disable any form of tinkering.
But as I am still having a locked "OEM unlocking" and a locked bootloader I am open for any kind of tinkering to get
this damn thing freed.
Would these steps ok:
Start the phone,
Setup lockscreen, dark theme, etc..
enable Wifi and download all updates, install updates
Ok? Or what would you suggest?
Cheers!
Etymotics
Etymotics said:
Hi Alex,
(NOT meant as any form of criticism or complaint... )
...I am a little confused here.
Other posts (not necessarily on this forum...can't remember) say: "Pull out the simcard, disable Wifi and DON'T contact anything, only skip through the setup..."
At the moment I only have a simcard of the wrong size...but I enabled Wifi but did not update anything in fear of getting an even stronger patch to disable any form of tinkering.
But as I am still having a locked "OEM unlocking" and a locked bootloader I am open for any kind of tinkering to get
this damn thing freed.
Would these steps ok:
Start the phone,
Setup lockscreen, dark theme, etc..
enable Wifi and download all updates, install updates
Ok? Or what would you suggest?
Cheers!
Etymotics
Click to expand...
Click to collapse
If you're not going to lose data or your not afraid of it, I would:
Factory reset without sim card in
When phone reboots, start setup
Don't put sim in but do connect to wifi
Skip through setup if you want and check if oem unlock is available
I'm not sure of the instructions you have, maybe that's what people believe for Verizon phones but you're not sure if you have one, correct?
Here's my experience:
I have several pixels, all unlocked. If I flash back to stock firmware and skip through setup without connecting to wifi, OEM unlock is greyed out. If I connect wifi on the first time through, it's available.
I've also heard this in tech videos. However, it won't work with Verizon phones. But if yours isn't Verizon, this could be the reason you're not able to unlock.
Hi Alex,
thank you for all your help! By the way: Are there any definite proofs for "my smartphone is a Verizon one" ?
I will try what you wrote and will be back with the result.
Two things came into my mind:
- Shall I install updates/upgrades if offered?
- Would downgrading (if even possible) via Chrome and the "Flash" feature on the Google page with all these images help, if I have a Verizon jail?
Cheers!
Etymotics
Etymotics said:
Hi Alex,
thank you for all your help! By the way: Are there any definite proofs for "my smartphone is a Verizon one" ?
I will try what you wrote and will be back with the result.
Two things came into my mind:
- Shall I install updates/upgrades if offered?
- Would downgrading (if even possible) via Chrome and the "Flash" feature on the Google page with all these images help, if I have a Verizon jail?
Cheers!
Etymotics
Click to expand...
Click to collapse
There may be a way but I'm not entirely sure, perhaps Google well help. I do seem to remember something about the IEMI but that may have been older models.
I wouldn't upgrade anything after setup and it shouldn't offer anything during.
As far as I know, downgrading won't help but I don't think you could from the Google page, as it requires an unlocked bootloader
Hi Alex,
I will try, what you wrote without updating anything ... will be back then...
Hi Alex,
no...unfortunately it does not help to connect to wifi...the "OEM unlock" is still grayed out.
Now....I wanted a de-googled phone to keep my privacy...instead I got a phone which is the
exact opposite. Unfortunately the cost of that thing remains the same...
Anything else, I can try?
Cheers!
Etymotics
Last week-end, i was abble to downgrade a Pixel 5 from A13 to A12 following this page
Navigate this article:
Downgrading your Google Pixel smartphone to stable Android version
Method 1: Leave the beta program
Method 2: Manual downgrade
Using Android Flash Tool
Using Fastboot
choose method 2 : fastboot (at the end of the article)
https://www.xda-developers.com/how-...rom-beta-developer-preview-to-stable-android/
and install e-1.10-s-20230412278810-stable-redfin according to the official instructions https://doc.e.foundation/devices/redfin/install
Hi Piero-e
That sounds very interesting. Did you unlock your bootloader before starting the procedure?
Did you change the bootloader of you device to another one?
Cheers!
Etymotics
Yes, i first unlock the bootloader (using the WiFi connection to another phone)
And flash bootloader and modem,
Then unfortunately my computer don't find the flash-all command, so I used the Gogol online tool to flash the others partitions