Related
Now first of all let me get started. I really will tip over PayPal for a beer for anyone who helps with that, because I've spent the whole day and can't get it to work.
Let me first of all explain my situation. I bought a Kindle 7 yesterday for the family business so that the staff can consult e-mails and access Google while being able to block most apps such as Facebook so they don't mess around (they already do it enough with their personnal phones ) and having read a bit about applications that would allow me to creates multiple users, I realised that I had to be rooted.
Now I had rooted my Galaxy S4 in the past and remembered it being an incredibly easy process so I figured, eh, might aswell give it a go, and that's when all the issues started.
I realised that this needs to be done using Bin4ry's method after installing the ADB drivers (hopefully I got all of this right). But here's where the first issue starts.
When I try to install the ADB drivers, I get the following error code :
So at first I was trying to restart my computer but came to the conclusion that it wasn't the issue. So I tried another method !
I tried installing the ADB directly from the Android SDK, using the link and such, which seemed to work well since I didn't have an error message and now the device was actually asking me to authorize for usage as ADB or whatever the message it says.
So I was optimistic and all, but then came the second problem... I tried running Bin4ry's program but now the issue was something else. When it tried running it, instead of saying device absent, it was now saying the the ADB was out of date (see below). After reading online, I was told thats its because the Android ADB and Bin4ry's one are conflicting, so some people suggested killing them in task manager, which I tried but also said they would come back automatically (which they also did). After that I found an ADBFIX little program, but had no clue where to find the Android ADB....
The reason I'm saying all that and making such a long post is to basically say that I've tried as far as my knowledge goes... I've checked the forums and everything, but most ''killing issues'' applied to HTC devices and not directly Amazon...
Please, I'd love help of any kind ...
Thanks..
Simon
s15.postimg(dot)org/ccwn8hbaz/ADB1.jpg
s14.postimg(dot)org/uf795dlz5/ADB2.png
s24.postimg(dot)org/y4ni1pf05/ADB3.jpg
I was told that since I had under 10 posts, I couldn't post any links, but had taken screenshot of my error messages.. Please replace the (dot) in the links above to hopefully help you understand my issues.
You may just want to use Towelroot and not mess with ADB at all. I've seen reports that it works on the newer hdx, so it might work on our kindles as well.
http://lifehacker.com/towelroot-roots-android-kitkat-devices-in-one-tap-no-p-1592226618
Just tried, unfortunately was told that this device isn't supported ...
What generation Kindle did you buy?
Korgot said:
Let me first of all explain my situation. I bought a Kindle 7 yesterday . . .
Click to expand...
Click to collapse
You know the newest Kindle (4th gen) isn't rootable yet. 2013 models (3rd gen) use Firerooter (KFSOWI modding community on Google+). This forum is for earlier models.
I am sorry if this is the wrong place or forum.
I have an HTC 8XT on an MVNO of Sprint. Sprint apparently seems to be withholding a firmware update that would allow this phone to update to 8.1, Sprint 8XTs are running 8.1, but not a single 8XT on my MVNO has gotten it yet.
The current firmware I have is 3030.00.10008.651.
According to HTC the latest is 3030.00.31009.651.
I have taken this phone off my MVNO and left it in a drawer for several months hoping that it would roll off whatever database it might be in. I tried to factory reset and then let it update it over wifi (I know Lumias can do that).
It still says no update found. I chatted with an HTC rep online and reading between the lines, he seemed well aware of Sprint's shenanigans. He hinted that ROMS were 'out there' and an updated ROM, even if it weren't the latest, might be enough to trigger an update. I started my Google Fu. Nothing.
Then I read the FAQ in this forum that said if I needed an HTC ROM I was out of luck.
I know enough about flashing and rooting to be dangerous to my phone . This is not my daily phone, but it's frustrating to buy a device that says "ready for 8.1" and then not be able to roam or send MMS. I'm willing to try some warranty voiding behaviors to update it.
All that to say, is there anything else I can try? Again, apologies if this is the wrong forum. I did try a thread search and saw some close topics, but nothing like this.
Thanks
Well, the simple question is "have you tried the Developer Preview program?" because that bypasses the MO gating when your phone gets updated. Developer-unlock your phone (you don't have to sideload anything, the app just checks to see if you're unlocked), install Preview for Developers from the Store (free app from Microsoft), run it, and enable the installation of preview releases. That *should* let your phone get any relevant updates.
If that doesn't work, then I can't help you any further; I'm not a ROM guy.
GoodDayToDie said:
Well, the simple question is "have you tried the Developer Preview program?" because that bypasses the MO gating when your phone gets updated. Developer-unlock your phone (you don't have to sideload anything, the app just checks to see if you're unlocked), install Preview for Developers from the Store (free app from Microsoft), run it, and enable the installation of preview releases. That *should* let your phone get any relevant updates.
If that doesn't work, then I can't help you any further; I'm not a ROM guy.
Click to expand...
Click to collapse
Thanks for your reply.
I have been enrolled in the Developer Preview and have never gotten an update on this phone. I think I got this phone shortly after 8.1 was pulled from the DP due to the WiFi issue. Then I read on some Sprint boards that those *with* the Developer Preview were having issues installing the 8.1 when it was rolled out, so I wiped the phone. It has been several weeks since I tried Developer Preview on this phone. I thought it was on to WP10 and it wouldn't help me much.
Still, can't hurt to try to install it one more time, but I am not hopeful.
Thanks again for your time.
Edit: I think in my earlier attempts I missed the registration and unlocking of my phone. Trying that now.
Edit 2: Now it seems that sometime in May, Microsoft shut down the process for unlocking 8.0 phones with SDK
You might try to unlock the phone with the Chinese utility, but I am not sure that developer preview program really checks if your phone is unlocked. Is there a new firmware for your model in navifirm?
Lanex777 said:
You might try to unlock the phone with the Chinese utility, but I am not sure that developer preview program really checks if your phone is unlocked. Is there a new firmware for your model in navifirm?
Click to expand...
Click to collapse
My phone is made by HTC. Isn't navifirm exclusively Nokia?
DISCLAIMER:
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
INTRODUCTION
This thread is mainly intended for devs (pro devs don't really belong here because they're pro and this thread is useless), for someone who need help to continue the work for Nova and fix the bugs on Pie (not many left). I'll help as long as you can speak English xD (no google translate because it can cause misunderstandings). However, don't expect me to spend the same time into this as i''ve did when i've had the phone. Yes, i no longer have the phone (it's still dead) and if you're not up to date with that, then you can read the announcement here and i've mentioned that i've got a new phone here. On top of this, i can't build anymore because i can't sign up on Google Cloud Platform anymore. I've wrote about this here at the hidden content (below as a side note).
Users can also help with doing researches, testing things and logs.
I don't know if i'll consider to continue working on it myself alone without the phone. I'd need at least to be able to build and then i'd need people to test new builds / flashable zips. At some point i might consider that because i'm missing this phone and the community xD.
SOURCES
Device: https://github.com/skinzor/android_device_huawei_hwcan/tree/lineage-16.0-last
Vendor: https://github.com/skinzor/proprietary_vendor_huawei/tree/lineage-16.0-last
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
Click to expand...
Click to collapse
There's two branches:
1) lineage-16.0: those ones were used when i've booted Pie the first time. Remember that i've wrote about it here? Those ones were updated from mido's ones.
2) lineage-16.0-last. those ones are the last ones and updated, which i've used in my last build. Those ones were continued from previous branch and updated from tissot ones which were / are updated by another dev (not the same dev as on mido). I recommend to continue with this branch, but it's up to you. You might not be able to get a successful or bootable build anymore with lineage-16.0 branch anyway because lineage's sources were updated since then.
I've used mido's trees as reference for lineage 14 and 15 trees too. You can figure that yourself if you check mido's trees and then Nova's ones, as i've cherry-picked the commits. Why did i use mido's trees? Because:
1) It has the same qcom chipset as Nova.
2) It is a popular phone.
3) A good dev was working on it.
4) It has official lineage support.
Now you might ask why i haven't did myself everything from scratch. Well, as a newbie dev, it would've been much harder and would've took much more time. Also, i'd say that there's no point at all to do something from scratch when it was already done unless you want to go the "hard" way, assuming you have time and want to learn more. I've still learnt a lot since i've started.
There are "universal" commits which are about fixes / improvements that can be related to e.g. the android version or the qcom chipset and those commits are usually found in many device trees, so you just cherry-pick them. A good example would be this commit: hwcan: Use mke2fs to create ext4 images.
FIXING THE BUGS OF LINEAGE 16 / PIE
I assume that you've used lineage-16.0-last branch as i've recommended. I no longer remember what bugs had my last build, but i think that the bluetooth was working, while it wasn't working in the build made from old lineage-16.0 branch. However, i remember that it had a new bug and as far as i remember, it was the RIL, but the baseband was showing up. I think i've tried to fix it and i've got it working (i remember that it was about the blobs), but i don't remember how. As of typing now, i've looked into the logcat which i still have and i've seen this:
Code:
F linker : CANNOT LINK EXECUTABLE "/vendor/bin/tftp_server": library "liboemaids_vendor.so" not found
That kind of error is self explanatory: the blob / lib is missing. After i've seen this, i've remembered that it's a new blob which got added in the original commit and which i've cherry-picked here. I didn't include that blob for a reason, but i don't remember that reason lol (it's not that i've forgot it, but i've skipped it for a reason). I remember that back then i've added the blob manually after i've seen the error, but i don't remember if that's what fixed the RIL, so you can try that and let me know.
As i've said already, i don't remember what bugs had that build besides the RIL, so you can try it and let me know.
At the introduction i've mentioned that i can help. I'll help only here on XDA in this thread because it may help other people too if they're having the same error / problem and after all, it's nice to have a thread like this in my opinion.
You can attach the log or paste it to gist github, pastebin, del.dog or any pasting website, but don't paste it in the XDA post because it just sucks.
Click to expand...
Click to collapse
DOWNLOADS
MEDIAFIRE | ANDROIDFILEHOST
As i've recommended to use lineage-16.0-last branch to build / continue the development, i also recommend to flash that build.
The build from lineage-16.0 branch folder doesn't boot. Back then, when i've seen that it doesn't boot and took a look at the logcat, i've tried the graphic blobs from the tree of zenfone 3 and that one was using them from nokia 7 plus (based on the commit). I had two zips in my PC and i've uploaded both. The first one created is graphic_pie_blobs_zenfone3_nokia_7_plus.zip and the second one sdm_blobs_zenfone3_nokia7_plus.zip, so you flash them in that order. As i've mentioned in that post in which i've said that i've booted Pie, there is some lag / glitches while scrolling, due the display / graphic blobs.
ENDING
As i've promised, i've pushed the tree sources and uploaded my first and last build. The reason i'm willing to help in fixing the bugs is because i'm missing this phone and this community here on XDA (as i've expected xD). It was fun and thanks to this phone and y`all for your support and kind words, i've learnt so many things in this journey. That's simply unforgettable for me.
Hopefully someone will jump on and continue the development further. I'll be here to help.
XDA:DevDB Information
[DEV][9.0] LineageOS 16, ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
ROM OS Version: 9.x Pie
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Testing
Created 2019-01-02
Last Updated 2019-01-05
Reserved
Reserved
Thank you for all the hard work you put into this. I would try to follow the leads, but for me this phone is dead now. I had hoped it would be something, but naw, just a hunk of something. Maybe someone can pick it up and go with it, encouraged everyone to try. If you are thinking about it Robert @#Henkate will help you. Great person, and this phone got me to know him so boom, good phone.
Maybe this should be in off topic thread, but I will post here.
Thank you for the great work that you have done. You gave us nougat, oreo, almost a pie. LineageOS 15.1 is the best firmware I have ever used. EmUi far behind. Thanks again a lot. Pie is full of bugs (I have already tried), counted a huge list of 10 items, but I think it's time to relax. You gave nova a second life and for that I am grateful to you. I found out that you are switching to another phone. Good luck in developing it, you are a good developer, the main thing is to believe in yourself!
Hi enkate... does wifi calling work on 16 ?
thanks
virusdunil said:
Hi enkate... does wifi calling work on 16 ?
thanks
Click to expand...
Click to collapse
He has no way to check. Maybe someone who has flashed it could test.
wow！thx a lot，I will try it now！
Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /
Alee.se said:
Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /
Click to expand...
Click to collapse
With the first build go two files, except for the firmware, responsible for the display. Flash them after flash lineage 16 last build and everything will work
Logcats
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all
Vinnom said:
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all
Click to expand...
Click to collapse
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Disable out sim card
AssasinAkindinov said:
Disable out sim card
Click to expand...
Click to collapse
ye, phone in airmode workrd normally,
AssasinAkindinov said:
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while
Click to expand...
Click to collapse
penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Sorry guys, no mean to be rude here, but this thread is for development purposes. My point in posting was to give a logcat and receive help to try and fix the bugs I found. I know that when possible, #Henkate gonna take a look and give some directions, so work can be done. So, if you wanna test and see if the rom works for you, that's fine, but provide logs, please. It's good to have other logs and be able to compare if the bugs are the same and I think it can help development a lot (no need to flood with logs either, be reasonable).
Unbrick no screen.
To repair the phone (when there is more image) it must start in fastboot mode and then flash boot image) wait for the phone to go off or remove the battery. When it is off plug the usb cable c on your huawei nova and the phone will show that the phone is charging. Now you can reflash another rom but not lineage os 16. Sorry i use google translation
Android 9 with jdi screen
Android 9 with jdi screen
Amazing near.
As it is known, custom firmware was not friends with the jdi screens.
And here came LOS16 on Android 9. Read reviews that it is now not usable even on smartphones with "normal" screens, what can we say about JDI
But from the realization that he had bought a new phone and having a lot of time, the thought crept in to try to put a fresh custom for total disappointment in his smartphone and quiet use of the new.
However, not everything is so simple. After the first launch, the screen began to flicker well, I thought everything had arrived, now it will get dark and the sensor will fail. Cured with just one reboot. more of this did not happen.
Sim cards did not pull out (I have 2 of them), some wrote that because of them there were some problems crashing and rebooting the system (I don’t have that)
After a night out, the interface began to respond with a delay of 0.5 seconds. (It was cured by a complete reboot) ..
Quickstep launcher is often closed with an error
The camera does not remove the drain, installed from the playlist of the market works without comments.
The navigation bar disappeared after a telephone conversation, when the interlocutor first completed the call (It was decided to reboot)
Vkontakte application crashes, but I use Kate Mobile, it flies with a bang.
YouTube crashes
The sound from the conversational dynamics is quiet, I think you can fix it in the mixer_paths but this is not exactly
Waiting for the moment until the screen fails.
All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!
R0mi4 said:
All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!
Click to expand...
Click to collapse
Ты все посты будешь переводить и сюда кидать?) (It is joke)
Every since accepting and updating my Moto G6 (US Retail) to 9.0 (PPS29.118-11-1), it has been laggy. The lags seem to happen mostly when there is some type of I/O operation (like opening an app), or when a background app is doing something on the network - email getting delivered, etc. I've rebooted to recovery, and wiped the cache, but now I am considering doing a factory reset. Anyone else experiencing this? Anyone got any ideas that don't involve me reloading all my apps and data?
Thanks in advance.
-Chris
yeah, i'm also getting some lagginess. it's mostly when i unlock my phone using the fingerprint reader. the transition takes a super long time. i feel it's mostly the animation that's causing the ton of lag. initially after i updated to 9, opening and closing apps would take forever as well. but changing the animation with nova launcher made it a bit snappier; although it's still slower than 8.
No lag here
You guys might want to do a clean firmware install, I don't have any lag on this version I didn't take the OTA just flashed the firmware.
I think I may have resolved at least some of the issue. First, I use a SD card to hold some pictures, and videos, and other data (no apps). I reformated the card from android, and this resolved about 80% of my lag issues. Not sure if there is some kind of disk polling that is done, but with the clean format on the SD card, things most run smoothly now. The other area I'm still seeing a little lag is when scrolling over something in apps like google news where it is trying to pull a video or large image file and there seems to be some delay in the network. At this point, I think the issue is in my wifi network, not my phone (although I'm still no ruling it out). But at least it is better.
kc6wke said:
You guys might want to do a clean firmware install, I don't have any lag on this version I didn't take the OTA just flashed the firmware.
Click to expand...
Click to collapse
Dead on. While I was able to make my G6 better, it was still laggy at times. Yesterday, I bite the bullet, backed up my data, and did a clean flash of the current firmware. Now the phone is smooth as glass. Good call.
Thanks,
-Chris
Noticed the same thing. Reflashed for some other reason and instantly saw the lag that had been getting more and more noticeable disapear.
What do you mean by 'reflashing'? Is that the same as 'restore to factory settings?'
I've read a thread on the Motorola forum where users have done that, with no noticeable results.
Nightwing-1 said:
What do you mean by 'reflashing'? Is that the same as 'restore to factory settings?'
I've read a thread on the Motorola forum where users have done that, with no noticeable results.
Click to expand...
Click to collapse
No, I literally reflashed the ROM.
I downloaded the current official ROM from here:
https://mirrors.lolinet.com/firmware/moto/ali/official/RETUS/
(note the link is for the US Retail channel distribution, if your phone is not RETUS channel, find the matching ROM for the channel your phone is.)
Once downloaded, I used the RSD lite app to flash the phone.
http://download.canadiancontent.net/RSDLite.html
You can google exact directions to use the tool, but basically, you reboot your phone to the bootloader, start RSD Lite, connect the USB cable (I had to use the factory cable on a USB 2.0 port to make this work), select the ROM file, and press Start.
Note: This will wipe your phone! So make a backup of your data.
I'm not familiar with flashing ROMs etc. And I don't want to mess up my phone any further.
Despite the fact that Motorola insist that there is no problem, I'm hoping their forum will convince them that there is.
Thanks for the help, but I'll keep it as it is. Meanwhile I'll be looking around for a dependable Android One phone.
I found one thing that helped:
Go in to 'Settings', 'system', 'Motorola privacy'' and uncheck both the slides in the menu. And I disabled the Google feed on my start screen (Swipe access).
The restart your phone.
The phone is a lot less laggy after that.
update! the August security patch update kind of helped with the lock screen lag I was experiencing.
blueberryapple said:
update! the August security patch update kind of helped with the lock screen lag I was experiencing.
Click to expand...
Click to collapse
Just did a check on my phone, and there is an update on the RETUS channel.
PPS29.118-15-11 / Security patch level: August 1,2019
A few questions about this. Through pure dumb luck, I didn't accept the Pie update, and have turned off automatic system updates in the Developer's options. It gives me a notice of new firmware a few times a day, which I decline, but so far has not updated without my consent. I realize it may do that at any moment regardless of the Developers setting.
So I'm still on Android 8, and would be delighted to stay there. But, if I'm forced to go to 9, would I be able to flash 8 again using the files here? Would that accomplish anything, or would it still insist on going to 9 after I had flashed 8?
The earlier reference to the "current official" rom - does that mean the latest 9 rom?
Why would installing the same v9 rom over again produce any different result from the OTA update to that rom?
Is there any way to turn off the firmware update notices? I've tried lots of things, but they still come.
Just trying to figure out what my options are, and what I should do. There's a 42-page thread on the Lenovo forum about this problem, with no indication that Lenovo/Motorola will lift a finger to fix it, apparently being content to see some unknown number (perhaps all) of the G6's ruined by the update to 9. I called Moto CS, and they blamed Google for the problem. Obviously, I bought the wrong brand of phone. Actually, it's my first smart phone. It seems beginners luck is a myth. At least I know better than to buy a Lenovo computer when Windows 7 becomes dangerous in January.
Anyway, I would appreciate any comments on the G6 thing.
Hello, is it required to have unlocked bootloader when doing re-flashing the official rom?
ici0606 said:
Hello, is it required to have unlocked bootloader when doing re-flashing the official rom?
Click to expand...
Click to collapse
I posted this in another related thread:
-------------------------------------------------------
JimmiH on the Lenovo forum has found "Lenovo Moto Smart Assistant", a new utility from Motorola, which is installed on your PC (Win 7 or 10). Included in the utility is a "rescue" function which appears to do the same thing as RSD Lite - resurrect a phone from any software issues. It downloads the correct official rom and reflashes it to the phone. JimmiH will be reporting back over the next few weeks as to whether the rescue has permanently solved his Pie lagginess issues.
The advantage of this LMSA over RSD Lite is that it runs on Windows 10, and presumably works with USB3 ports, while apparently neither was the case with RSD Lite. And of course you don't have to go hunting for the right rom.
----------------------------------------------------------------
My understanding is that this utility does not require unlocking, and it does not root the phone.
Hello, I tried LMSA for flashing, but it says not supported device, I have model XT1925-4.
ici0606 said:
Hello, I tried LMSA for flashing, but it says not supported device, I have model XT1925-4.
Click to expand...
Click to collapse
RSDLite will work on Windows 10, I have been using it, even on the newest Windows 10 version 1909. It will not work on usb 3 ports though. If you have any USB 2 ports available, plug the cable into one of those and it will work.
xfrobex said:
RSDLite will work on Windows 10, I have been using it, even on the newest Windows 10 version 1909. It will not work on usb 3 ports though. If you have any USB 2 ports available, plug the cable into one of those and it will work.
Click to expand...
Click to collapse
Hm I have just USB 3 on my PC, ok will try on some older one.
But is it required to unlock bootloader, when using RSD Lite?
Thanks.
ici0606 said:
Hm I have just USB 3 on my PC, ok will try on some older one.
But is it required to unlock bootloader, when using RSD Lite?
Thanks.
Click to expand...
Click to collapse
No. RSDLite doesn't require unlocked bootloader.
Peabody424 said:
I posted this in another related thread:
-------------------------------------------------------
JimmiH on the Lenovo forum has found "Lenovo Moto Smart Assistant", a new utility from Motorola, which is installed on your PC (Win 7 or 10). Included in the utility is a "rescue" function which appears to do the same thing as RSD Lite - resurrect a phone from any software issues. It downloads the correct official rom and reflashes it to the phone. JimmiH will be reporting back over the next few weeks as to whether the rescue has permanently solved his Pie lagginess issues.
The advantage of this LMSA over RSD Lite is that it runs on Windows 10, and presumably works with USB3 ports, while apparently neither was the case with RSD Lite. And of course you don't have to go hunting for the right rom.
----------------------------------------------------------------
My understanding is that this utility does not require unlocking, and it does not root the phone.
Click to expand...
Click to collapse
Count me among those watching this thread, in particular looking for evidence that LMSA (or RSD Lite) actually eliminates the lag problem for more than a few days. My phone is a bone stock model XT1925-6 running Android 9, PPSS29.118-15-11-2. Lag improved after the October update but returned in about a week.
I appreciate the efforts of this group in trying to resolve this problem.
My sister-in-law recently switched to TMo and ended up with a "free" G7 Power running Android 9. It's very smooth with no lag at all, so Moto apparently knows how to resolve this problem, they're just not helping us with the G6.
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