Related
I could've swore I read they stopped it? If so then is there anyway to flash the phone and be able to get the baseband? My co-worker's phone keeps rebooting, etc. I don't want to use the LG Update Tool. I bricked my phone and finally got it unbricked after 5 hours.
you are right T-Mobile already stopped rolling out the OTA.
Your only opportunity to get the new baseband is the LG tool
flexnix said:
I could've swore I read they stopped it? If so then is there anyway to flash the phone and be able to get the baseband? My co-worker's phone keeps rebooting, etc. I don't want to use the LG Update Tool. I bricked my phone and finally got it unbricked after 5 hours.
Click to expand...
Click to collapse
Sent From My WeaponG2x
I used the LG tool about an hour after the update was relesed and it went perfectly smooth. What I did was a factory reset before I did it and I dont know if that mattered but I had no problems. I would do it you really have no choice. I thought I read somewhere that someone is working on a version that you can install from SD but I might be wrong and I dont think you will get the new baseband which in my opinion is one of the best things about the update. It is the only part you cant just flash. If you root you can install any ROM like the leaked one or whatever. So I would use the LG updater. The other thing is I have the LG updater on my computer and it starts automatically and it says that their servers are undergoing maintenance so you cant use that either. I hope this helps you
Charlie
flexnix said:
I could've swore I read they stopped it? If so then is there anyway to flash the phone and be able to get the baseband? My co-worker's phone keeps rebooting, etc. I don't want to use the LG Update Tool. I bricked my phone and finally got it unbricked after 5 hours.
Click to expand...
Click to collapse
There are precautions you can take to prevent a bad experience. Most of them are listed on the Forum somewhere. But to recap,
Stock ROM: Install a stock rom. Root does not impact the update, so being rooted is not an issue. Find the Stock Rom and load it.
Standard recovery: Flash the standard recovery. If you are happy with your current rom, do a nand backup first. Then flash the stock ROM.
Factory reset: Throw this in because it can't hurt.
Many of the people that had problems with the LG updater simply did not meet the above steps.
While doing the update, remember, turn off AV, turn off pop up blockers. Turn off FAX programs or any other monitoring program, even screen savers. Do NOT make assumptions. There are several places in the update where the progress appears to stop. Do NOT disconnect. If you have been stopped for a hour, something is wrong. But a few minutes is not out of line. Personally I stopped at 4% for about 5 minutes...then it continued.
Here's the thread to return your device to stock....its pretty good. I can walk through these steps in less than 5 minutes....its really simple. Set your friend up with this.....
http://forum.xda-developers.com/showthread.php?t=1088728
In case you're wondering, the thread above will NOT restore to pure factory like condition. It will NOT restore the original baseband. But all the rest works....its easy to use, simple to follow.....and more than anything else, does not require you to think....only follow. The worst problem people have when doing this is thinking, and assuming. Just follow the steps as is, no ad lib.
Good luck.
I've used the LG Updater on 3 phones, and I haven't had any problems.
I followed this page of instructions from the LG website and had no issues. http://wwwstg.lg.com/us/mobile-phones/G2X-Driver/index.jsp
I used my netbook running Windows 7 Starter Edition.
I just tried updating on the lg website and it says servers down for maintence
Sent from my G2X
kwiggington said:
I just tried updating on the lg website and it says servers down for maintence
Sent from my G2X
Click to expand...
Click to collapse
That is only the first time it runs after you install it. Click start and go to "LGMobile Support Tool" and run the "LGMobile Update" program. It should run this time without the bogus server down message. If you look at the dates in that notice, the maintenance was back in July. Be sure to right click the program and run as administrator if you are running Windows 7. Make sure you install the drivers from within the updater also, as the other driver pack on their website doesn't seem to install all the drivers you need to complete the update. Good luck.
jboxer said:
That is only the first time it runs after you install it. Click start and go to "LGMobile Support Tool" and run the "LGMobile Update" program. It should run this time without the bogus server down message. If you look at the dates in that notice, the maintenance was back in July. Be sure to right click the program and run as administrator if you are running Windows 7. Make sure you install the drivers from within the updater also, as the other driver pack on their website doesn't seem to install all the drivers you need to complete the update. Good luck.
Click to expand...
Click to collapse
I didn't have to run as administrator and I used Windows 7. Following the instructions in the link I posted above I had no issues at all. Drivers were installed separately from the updater, again just following the instructions from that link.
Follow LG's instructions word for word, in order, from start to finish, without skipping any steps, and you shouldn't have any issues.
phburks said:
I didn't have to run as administrator and I used Windows 7. Following the instructions in the link I posted above I had no issues at all. Drivers were installed separately from the updater, again just following the instructions from that link.
Follow LG's instructions word for word, in order, from start to finish, without skipping any steps, and you shouldn't have any issues.
Click to expand...
Click to collapse
Thanks ill try it when i get home
Sent from my G2X
Is anybody working on getting the baseband as a zip that can be flashed, that would be great instead of going through the whole updater tool thing.
Sent from my LG-P999 using XDA App
Updated works awsome now
Sent from my G2X
phburks said:
I didn't have to run as administrator and I used Windows 7.
Click to expand...
Click to collapse
When you ran the program did Windows have a warning box that said this program wants to make changes to your computer, and you had to say yes or no to allow it to continue. That means the program installer set it to admin mode already and Windows confirms you want to run the app as an admin. Without admin mode in Windows 7, programs that flash roms and such simply don't work properly. Looks like LG mitigated a problem by setting the flag during the program install.
jboxer said:
When you ran the program did Windows have a warning box that said this program wants to make changes to your computer, and you had to say yes or no to allow it to continue. That means the program installer set it to admin mode already and Windows confirms you want to run the app as an admin. Without admin mode in Windows 7, programs that flash roms and such simply don't work properly. Looks like LG mitigated a problem by setting the flag during the program install.
Click to expand...
Click to collapse
Yea it asks for that confirmation. The one I used is version 1.5.2.2
I have a problem. I just got my Android a couple of days ago and I really badly want to root it. I've tried multiple different programs and with each one the problem I get is "Waiting for device" in the cmd/terminal (Tried on multiple platforms: Vista, Win7, Ubuntu). I've tried installing drivers too and still didn't work (maybe the wrong drivers?).
Yes I realize that I am a "noob", but I really need some help here.
Got USB Debugging enabled ??
Got the correct upto date drivers ?
You navigated to the right location in ADB ??
azzledazzle said:
Got USB Debugging enabled ??
Got the correct upto date drivers ?
You navigated to the right location in ADB ??
Click to expand...
Click to collapse
>Yes
>I think so, not positive.
> What do you mean?
bumpp someone help?
Well Redownload the drivers and see if that helps, You could try Hasoon2000's All In One Kit to help with this. http://forum.xda-developers.com/showthread.php?t=1604677
As for ADB, (Android Debug Bridge) you should have this already, You need it to get unlock the bootloader and flash superboot (root) http://forum.xda-developers.com/showthread.php?t=1583427
Be sure to check out those links and also look at my FAQ section http://forum.xda-developers.com/showpost.php?p=24884624&postcount=3
I have all the files that it says are necessary to unlock the bootloader. It's just when I type "fastboot oem get_identifier_token" it just sits there saying "waiting for device".
I've tried hansoon's all in one program as well and it didn't work either.
Well that means it cannot find your phone, So the issue lies with the drivers and/or the location from which the command prompt is opened..
Put all of the files into 1 folder called android or adb and move that 1 folder to the root of your C Drive..
This should make navigating easier. Also, In that folder should be adb.exe and fastboot.exe do you have these ?
I fixed this by just playing around with it a bit more. Thanks for the help, though.
infam0us me said:
I fixed this by just playing around with it a bit more. Thanks for the help, though.
Click to expand...
Click to collapse
what exactly did you do? I am stuck with this problem for a long time now. nothing seems to help. what does "playing around" mean?
windows 8.1
htc one s (c2)
morphication said:
what exactly did you do? I am stuck with this problem for a long time now. nothing seems to help. what does "playing around" mean?
windows 8.1
htc one s (c2)
Click to expand...
Click to collapse
Well man, I really wish I could help you out because I remember how frustrating this was for me. This post was 2 and a half years ago though. Just really make sure that your drivers are up to date. If I could remember my exact solution I would help you out for sure.
infam0us me said:
Well man, I really wish I could help you out because I remember how frustrating this was for me. This post was 2 and a half years ago though. Just really make sure that your drivers are up to date. If I could remember my exact solution I would help you out for sure.
Click to expand...
Click to collapse
ok. it was windows 8 not allowing unsigned drivers to install properly. note: not "not installing at all", but "not installing properly". meaning: htc drivers installed somehow, so I was able to see the device and copy files around, but it was not enough for flashing roms.
so I started this guide to disable driver signature:
https://www.youtube.com/watch?v=gmw86KplqmU
... but my laptop is a business laptop and this guide demands BitLocker key if hard drive is encrypted (mine is). I also have a windows 7 desktop machine. So I decided to go the easy and quick way of simply doing flashing on my desktop computer. Windows 7 worked like a charm. But I'm sure the guide above would've helped as well. If somebody tries that, please post results.
Tech Specs:
Processor Type: Quad-Core Cortex A9 Processor(When I turn on the tablet it says Allwinner A31?)
Processor Speed: 1.20 GHz
System Ram: 1 GB
Hard Drive Size: 8GB
Laptop Screen Size: 7 inch
Screen Type: Capacitive Touch Display
Battery Life: 4 hours
Battery Type: 2800mAh Lithium Ion
Network Connection: 802.11b/g/n Wireless LAN
Connector Type: 1 x HDMI, 1 x Headphone, 1 x MiniUSB 2.0
Operating System: Google Android
Accessories Included: AC Adapter,USB Cable
Operating System Version: Android 4.2 Jelly Bean
This thread is a continuation of some of the discussion that was from this thread: http://forum.xda-developers.com/showthread.php?t=2568427
While not at all high end tablets, it's always fun to see what can be squeezed out of them! As stated in the title, this thread will be regarding the following devices: Nobis NB07, Iview 774TPC, and DA-741QHD (which all appear to be the same hardware) rooting and ROMs. That should be pretty simple for now since, we currently have no ROMs and no proven root method. Some have reported success using the Kingoapp. If anyone is able to obtain root, we would like to ask that you make a copy of the firmware and upload it for those of us having trouble doing so. After doing so, we can modify it and hopefully get more our of the software.
You may also post information regarding tweaking the ROMs for these devices and other ways to make them more useful!
Warning: The following may have unforseen effects including breaking your tablet to the point of being unrepairable.
Option #1, Use KingoApp Some users have reported that this did not work for them, at least one user reported that it did.
Instructions per RawX:
For the drivers the easiest method is just using Top Notch Tablets How to install ADB drivers. That worked on the first one, the second one it didn't not entirely sure why, but you can send a email to support and ask them for development drivers for the nobis tablets and they will send the ADB drivers you need. After you have the drivers installed use kingo while the tablet is in usb debug mode BEFORE plugging it into your usb port and do not turn on usb transfer. the first time after it reboots kingo will report that it was not rooted, leave it plugged in and power off and back on and it should report the root worked. This method gives you SuperSU. Both times. I've done this were for clients of mine but its pretty straight forward.
Click to expand...
Click to collapse
The working drivers for me were: VID_1f3a_PID_efe8
Please consider trying this first and give us some feedback. A word of warning though, there has been some discussion on XDA in the past that this may be malware though I'm not sure this was ever confirmed.
Option #2, Flash firmware for an alternate device that can be rooted easily. Warning!!! Currently, there is no way to get back to stock (until someone who gets root with another method makes a copy of the firmware)
Go to this website: http://www.iviewus.com/firmware788TPC/ and download the firmware. Yes, it is for another tablet. However, the tablet appears to have the same specs as ours. Once downloaded. Install the included PhoenixSuit software. Once it is running, click the button at the bottom right to update the software to the newest version (this may not be required). Then, plug in your tablet using the usb port and install the drivers. I used google and found them all within minutes. Once the software recognizes your tablet go to the firmware tab where you have extracted the .img file and select the file. Next, click upgrade to upgrade your tablet (it has instructions to help your tablet be recognized if you are having difficulty). Once the new firmware has been flashed, then download the file RootFromOTA.zip that can be found on various places such as XDA. Move the file onto an external SD card. Then, go to settings -> backup & reset -> Recovery Mode. Your tablet will restart. Once it does, select the bottom option to install from SD card. Install the RootFromOTA.zip and then reboot. Once rebooted, install the supersu app or another root application of your choice.
Credits: As above to RawX
Congrats... You're rooted.
Mods
Currently, I've managed to get great battery life out of my tablet by installing kernel tuner and changing the settings as such:
Governor: Ondemand (default is fantasys)
Max: 1200 MHz (Default is 1200 MHz)
Min: 240 MHz (Default is 120 MHz, but I had trouble with usability at this setting and Ondemand)
I also recommend setting wifi to turn off when the screen is off and turn off autosync.
This seemed to give me a very useable system but with greatly improved battery life. Doing the above and a few other tweaks here and there have made my battery life so that it drains by about 1% overnight when not in use. I also seem to get better battery life while using the tablet. I haven't had any trouble playing games either.
neatojones said:
Option #2, Flash firmware for an alternate device that can be rooted easily. Warning!!! Currently, there is no way to get back to stock (until someone who gets root with another method makes a copy of the firmware)
Go to this website: http://www.iviewus.com/firmware788TPC/ and download the firmware. Yes, it is for another tablet. However, the tablet appears to have the same specs as ours. Once downloaded. Install the included PhoenixSuit software. Once it is running, click the button at the bottom right to update the software to the newest version (this may not be required). Then, plug in your tablet using the usb port and install the drivers. I used google and found them all within minutes. Once the software recognizes your tablet go to the firmware tab where you have extracted the .img file and select the file. Next, click upgrade to upgrade your tablet (it has instructions to help your tablet be recognized if you are having difficulty). Once the new firmware has been flashed, then download the file RootFromOTA.zip that can be found on various places such as XDA. Move the file onto an external SD card. Then, go to settings -> backup & reset -> Recovery Mode. Your tablet will restart. Once it does, select the bottom option to install from SD card. Install the RootFromOTA.zip and then reboot. Once rebooted, install the supersu app or another root application of your choice.
Congrats... You're rooted.
Click to expand...
Click to collapse
I am assuming the camera is not working using this method or did you figure it out?
And also, do you have a link to the drivers you used off hand or what did you search for to find them?
Hippie459MN said:
I am assuming the camera is not working using this method or did you figure it out?
And also, do you have a link to the drivers you used off hand or what did you search for to find them?
Click to expand...
Click to collapse
Nope, still haven't gotten the camera working. We are missing some config files still. Do you need the camera drivers or the tablet drivers?
The camera drivers are : sp2518 and sp0838, though I also see a module being loaded called cam_detect
I don't recall where I got the adb usb drivers for the tablet, but it would probably be a good thing to mention in this thread so if you have them, let me know and I can add it to one of the top posts. If you're having trouble finding them, I'll remove my drivers and go back through the process to find them again.
Looking for the tablet drivers. I am about ready to tap out on this thing for a while. lol Its driving me crazy.
Hippie459MN said:
Looking for the tablet drivers. I am about ready to tap out on this thing for a while. lol Its driving me crazy.
Click to expand...
Click to collapse
OK. The drivers I used were probably: VID_1f3a_PID_efe8 (or something similar)
You can either google that or try downloading the firmware for TP718AQ here: http://www.agptek.com/forum/viewtopic.php?f=22&t=948
Remove all prior drivers for the tablet. Plug it in and tell Windows to use the drivers from the extracted file you download (Will extract to TP718AQ_Update_Firmware\USB Driver).
Sometimes I have to do a little dance with restarting the device and my computer to get it to recognize it.
As a last resort you could try this: http://www.xda-developers.com/andro...r-solves-your-adb-driver-problems-on-windows/
Let me know if you have any problems.
Good Luck!
Ok, I officially give up trying to root this thing. Stupid windows will not install the drivers in both the links you provided and I cant get windows to even try to install anything after removing them then I got the android ADB drivers to install but still zero luck. All rooting apps fail. Hopefully someone will post the image of their rooted NB07. A few claim to have rooted it just fine but I cant win with this thing.
All I want is to be able to run link2sd and a few other apps that require root. This is officially the longest I have owned an un-rooted android device. lol
I'm the one that got the root working using kingo, so for the drivers the easiest method is just using Top Notch Tablets How to install ADB drivers ( I would post a link but I don't have 10 posts yet on XDA)
That worked on the first one, the second one it didn't not entirely sure why, but you can send a email to support and ask them for development drivers for the nobis tablets and they will send the ADB drivers you need. After you have the drivers installed use kingo while the tablet is in usb debug mode BEFORE plugging it into your usb port and do not turn on usb transfer. the first time after it reboots kingo will report that it was not rooted, leave it plugged in and power off and back on and it should report the root worked. This method gives you SuperSU. Both times I've done this were for clients of mine but its pretty straight forward.
Well, I have decided that for now this tablet of mine is un-rootable. I must have tried with 5 or 6 different drivers about 20 times with each with Kingo. I even tried that other program that is all in Chinese that loads some BS app on to your phone with no luck. So, for now, I am going to give up but if anyone has any other ideas or wants me to try something or they have for sure figured out how to root it, let me know as I am happy to help the best I can.
Edit: Oh yeah, Dont know how much this will help anyone but here is some more specific specs on the Nobis NB07 tablet I pulled off it with Hardware Info 3.0.0. Feel free to put the link in the first or second post if you want. Maybe it will help a little bit more.
http://www.hippie459mn.com/nobis_nb07/index.html
:good:
Hippie459MN said:
Well, I have decided that for now this tablet of mine is un-rootable. I must have tried with 5 or 6 different drivers about 20 times with each with Kingo. I even tried that other program that is all in Chinese that loads some BS app on to your phone with no luck. So, for now, I am going to give up but if anyone has any other ideas or wants me to try something or they have for sure figured out how to root it, let me know as I am happy to help the best I can.
Edit: Oh yeah, Dont know how much this will help anyone but here is some more specific specs on the Nobis NB07 tablet I pulled off it with Hardware Info 3.0.0. Feel free to put the link in the first or second post if you want. Maybe it will help a little bit more.
http://www.hippie459mn.com/nobis_nb07/index.html
:good:
Click to expand...
Click to collapse
Thanks to the work of someone on another forum, I have now got TWRP working on our device and am hoping we will soon have a CM working on it as well. Check back in the near future for further details. Maybe if you can't have a rooted stock, we can get a fully functional CM.
I am assuming you need to have root to flash the TWRP recovery correct. This is good news. Would love to have more info on it. Are you working with people on this site or another site? I would love to follow along.
Hippie459MN said:
I am assuming you need to have root to flash the TWRP recovery correct. This is good news. Would love to have more info on it. Are you working with people on this site or another site? I would love to follow along.
Click to expand...
Click to collapse
On another site for now. Just PM's at the moment so not much to follow yet. But, all you'll need is the Phoenixsuit to install it, so you won't have to root your tab first. You'll have root on the new ROM. You'll have to have drivers fully working though. Once fully working I'll link to the site so people can get the files and hopefully we can get this guy some donations for his work.
Awesome! I would go right to CM on this and skip the whole rooting the stock firmware. Would be nice to be able to root the stock firmware though then things would be so much easier. Think the camera will be working on the CM build? If not no big deal but would be nice to have them working.
Keep me (us) posted on the progress.
Hippie459MN said:
Awesome! I would go right to CM on this and skip the whole rooting the stock firmware. Would be nice to be able to root the stock firmware though then things would be so much easier. Think the camera will be working on the CM build? If not no big deal but would be nice to have them working.
Keep me (us) posted on the progress.
Click to expand...
Click to collapse
Not sure about the camera yet. I have CM booting but no touch yet, so this will be the first task. I'll keep everyone posted.
Any word on getting things to work yet?
Currently, we have CM working with no touch screen/camera. I'm not sure what else all isn't working because I'm waiting on my OTG cable to come in for further testing to see what all is going to be required to get the touchscreen going. Right now, it appears we my be looking at compiling our own drivers which could take some time to do. I think we'll get it eventually, but it may take some time. If you don't need touchscreen or camera, it could be working right now.
Sorry for no updates for a while. My work has been delayed on this since I have a son who is sick and in the pediatric ICU. I'll get back to work when things calm down for me.
No worries man. Family first.
Just a question, Hippie...
On the original ROM, can you see your device in ADB? If you can, and type "adb shell" do you get root? If you have adb access but not root, can you try typing sh and see what happens?
Also, could you try loading the rootfromOTA.zip and see if you can get a printout of the error log if possible?
Also, I tried installing this from the recovery on a similar ROM and it acted like it failed. I went back into the ROM and used adb and was able to get root using vroot or kingo...I don't remember which. This may be worth a shot.
Interestingly, I have been looking for alternative ways to root and found this (but we need to find a way to get to the bootloader):http://whiteboard.ping.se/Android/Rooting
I think that the method to get to bootloader is to turn off the tablet, then hold down the back button while tapping the power button 5 times. But, I also googled and found a method for getting to fastboot from adb in android without root as well which may work.
I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:
monogwai said:
I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:
Click to expand...
Click to collapse
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....
berndblb said:
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....
Click to expand...
Click to collapse
I figured that would probably be the case. Now, it's been several years since I've used Linux (Ubuntu Feisty Fawn was the last time I used Linux, and that was just to hack a first gen Xbox), but i'm a command-line based OS guy from the days of old, so I oughta be okay. I'm sure one of the various and sundry tutorials here on xda will help should I get stuck.
So, that being said, I guess I just need to install a distro and grab some adb/fastboot drivers for Linux? Or is that all built in? Is the command line interface sufficient, or will I need some GUI like xwindows (sorry if my info is horribly dated, lol.)
I'd probably better do some reading.
Nobody has any more expertise to proffer?
monogwai said:
Nobody has any more expertise to proffer?
Click to expand...
Click to collapse
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary
berndblb said:
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary
Click to expand...
Click to collapse
This is just the tip I needed. Big thanks!
Well, i assembled the troops- universal naked driver and minimal adb/fastboot on a fresh win 8.1 install. Bootit.ko file in my adb folder. Opened adb, plugged in tablet. Twrp starts. Hear the USB plug in noise, so adb is ready. Adb devices command, shows up recovery like it should. I then run a batch command to automate:
adb push bootit.ko /sdcard/
adb shell insmod /sdcard/bootit.ko
... as per the directions. I get this in response:
adb: error: connect failed: protocol fault <couldn't read status>: no error
on the first command, and 'no device found' on the second.
Now what?
Edit: nevermind. Added 'adb devices' to the batch file and it did it fast as anything. Lol.
New kink: adb command succeeded and i got fastboot access. Formatted 'misc' partition and rebooted-- still with the bootloop. I can still access fastboot, but that's it. Twrp always restarts. So, did SWIM bork the recovery partition too? Wondering if I should try re-flashing twrp, or downloading the original ASUS blob file and restarting from square one?
Edit:
Got impatient, started trying things. Links found thru the forums pointing to original ASUS rom blob are all broken, so i settled for starting with twrp. Downloaded freshest version from twrp.me compatible with the device and flashed it-- same result upon attempting to open twrp.
Took a break. Thought about it, and decided to fastboot erase recovery, and try flashing twrp again. Probably not a great idea... Now I get
Sending 'staging' <7210 kb>...
FAILED <data transfer failure (unknown error)>
So I guess there's a step after erasing to re-init the partition or something?
Just a note to anyone lurking - don't do stuff if you're only half-informed. You can be stupid and impatient like me and have broken stuff.
Impatience is a very bad advisor...
As long as you have fastboot you should be ok. Asus seems to have messed with their website again or they finally took the support pages down permanently.
I have a copy on my server and can upload it tonight.
Patience my friend, patience
berndblb said:
Impatience is a very bad advisor...
I have a copy on my server and can upload it tonight.
Patience my friend, patience
Click to expand...
Click to collapse
This is too true. That's why I threw in that little blurb. :good:
I'll await your link with bated breath.
Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again
berndblb said:
Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again
Click to expand...
Click to collapse
Debate my breath? Well, my breath reeks of Marijuana... I think it's a liberal.
Lol
Just a question: since I'll be repopulating all the partitions with the stock blob, does that affect my unlocked bootloader, or is it gonna be straight up manufacturer reset? I'm sure that's covered in the threads that address the 'buster99' process, but I need to go locate the thread. I didn't fully digest the thread as i'd yet to find the blob I could d/l, until you hooked it up. ?
No, you cannot relocate the bootloader. Flash away
berndblb said:
No, you cannot relocate the bootloader. Flash away
Click to expand...
Click to collapse
Ugh, corrupt archive. ? trying to download from a different server this time.
Edit: same results w/new download. Repairing the archive didn't help either.
Asus, ya'll are killing me! Every link on the interweb linking to a TF700 firmware is broken, and all that can be found are for the 700kl.
Final update:
Found a valid download link for 10.6.1.14.8. Had some difficulties with it (revived the post on the buster99 process) -- followed as written, and had a fail on the last process <invalid state>. Being super impatient (mentioned *that* before, lol), I decided to try and reestablish twrp, as that was the original issue. That took! Flashed 3.0.0-1 (iirc), was able to open twrp, but couldn't mount system or anything. So I formatted the crap out of all partitions, converted /data to f2fs, and was able to successfully flash katkiss nougatella. Wiped the caches, rebooted, and I'm golden! 3 months later, and it finally works.
Moral of the story: don't sell rooted devices to ppl who don't understand what that entails. You can tell a person till ur blue in the face, NO FACTORY WIPE VIA ANDROID -- Odds are, they'll forget. Worked out for me in the long run (took back the 700 and gave a 201 as replacement), but i was never sure I'd come out clean on the other end.
I have similar problem, i can't even go to bootloader.
Just keep bootlooping. Is there any chance of reviving my tf700t?
If yes please advice me step by step process to do that.
Thanks
Not enough information. What can you get to?
What's your ROM, bootloader, recovery?
berndblb said:
Not enough information. What can you get to?
What's your ROM, bootloader, recovery?
Click to expand...
Click to collapse
Thanks you already help on other thread.
It's a long story how this happened.
By the way I was running nougtell version don't remember as it happened in January.
I wanted to transfer some video files on my usb 2tb hard drive, so I did usb otg connection to my tab, i did this thing before and I use es file explorer to do the transfer, few occasions es file hang or whole tablet hang so I have to restart. But in January when this thing happened it just went into bootlooping i can go to fastboot but not recovery or android.
Then I search on many thread i couldn't find any working solution.
My cable was not detecting tab so I couldn't able to push recovery., But the same cable was ok for charging.
Then I bought new cable from eBay it took around a month to arrive.
But in mean time being impatient i tried data wipe from bootloader.
Then even i couldn't able to bootloader after that.
I know being impatient with doing something like this is not good you have to suffer.
Bootloader was latest version .14 at the end and recovery was 3.0.1
Using nogtella rom
Thanks
??
Can anyone confirm this working before I go ruin my phone haha
Clank50AE said:
Can anyone confirm this working before I go ruin my phone haha
Click to expand...
Click to collapse
You won't. Enjoy the better software!
suzook said:
You won't. Enjoy the better software!
Click to expand...
Click to collapse
Thank you for the Swift reply! My RM3 is glitchy as albeit and I'd like more stability. I know it's just the OS but it's very annoying.
Looks great. There's a big red warning to your thread tho that don't use if you're phone is Red Magic 3 it will damage the motherboard. Hmm
Any one besides OP tried this ?
leipnacht said:
Looks great. There's a big red warning to your thread tho that don't use if you're phone is Red Magic 3 it will damage the motherboard. Hmm
Click to expand...
Click to collapse
Everything is the same, other than the CPU. Nothing will happen. If people want to stick with the buggy rm3 sw, than go ahead. Not sure why you would want to.
so if rm3s fw works with rm3, can we try to install it thro twrp???
hagouba said:
so if rm3s fw works with rm3, can we try to install it thro twrp???
Click to expand...
Click to collapse
TWRP states ERROR 7 when i tried this
LE: Avoid using this so called GUIDE, this is a bad joke... I tried using the Tool on RM3 and the cmd remains stuck with at Downloading firehouse program... then after some time "Error]: Download programer FAIL.Please check phone status and reset into edl mode and try again.
Software download FAIL.Press any key exit:
I also swapped USB's, different cable and so on... COM 5 6 and 7 were used
@JerryYin I completely understand now why you were not sharing the tool ???
hagouba said:
so if rm3s fw works with rm3, can we try to install it thro twrp???
Click to expand...
Click to collapse
Absolutely not. Different sized partitions. You need to use the tool 1st.
Alex4455 said:
TWRP states ERROR 7 when i tried this
LE: Avoid using this so called GUIDE, this is a bad joke... I tried using the Tool on RM3 and the cmd remains stuck with at Downloading firehouse program... then after some time "Error]: Download programer FAIL.Please check phone status and reset into edl mode and try again.
Software download FAIL.Press any key exit:
I also swapped USB's, different cable and so on... COM 5 6 and 7 were used
Click to expand...
Click to collapse
Bad joke? Maybe you dont know what you are doing.
I did 3 phones. No issues. Its on your end.
suzook said:
Bad joke? Maybe you dont know what you are doing.
I did 3 phones. No issues. Its on your end.
Click to expand...
Click to collapse
You don't realize this is not a GUIDE, this is a statement and you are telling us to use the tool for something.... You did not provide steps, video, guide, pre-requirements, nothing
This is not my 1st time using this tool so i know how it works, i kept crashing my CN <-> EU roms and needed to use the tool
So, why don't you provide with these 3 x RM3's a video on how did you use the tool, on what hardware did you use it (PC hardware, maybe Ryzen is overkill for the app and does not know how to use the scripts), what drivers you have installed (because this tool does not provide drivers vs the RM3 tool that provides) and all that kind of stuff ?
Alex4455 said:
You don't realize this is not a GUIDE, this is a statement and you are telling us to use the tool for something.... You did not provide steps, video, guide, pre-requirements, nothing
This is not my 1st time using this tool so i know how it works, i kept crashing my CN <-> EU roms and needed to use the tool
So, why don't you provide with these 3 x RM3's a video on how did you use the tool, on what hardware did you use it (PC hardware, maybe Ryzen is overkill for the app and does not know how to use the scripts), what drivers you have installed (because this tool does not provide drivers vs the RM3 tool that provides) and all that kind of stuff ?
Click to expand...
Click to collapse
I'll delete the thread. I was trying to do people a favor. Didn't realize I needed to hold people's hands.
suzook said:
I'll delete the thread. I was trying to do people a favor. Didn't realize I needed to hold people's hands.
Click to expand...
Click to collapse
You shouldn't listen to aggressive people, they're the minority, thanks for whatever you were trying to do. I would like to give it a read if you still have the guide saved
If you speak the truth then please provide us with a picture or anything. First I don't know if rm3s fw is more stable than rm3 but if it is, I would definitely come back to stock rom as I missed the fan and triggers very much.
Sangyedorje said:
You shouldn't listen to aggressive people, they're the minority, thanks for whatever you were trying to do. I would like to give it a read if you still have the guide saved
Click to expand...
Click to collapse
Aggressive people ? Guide ?
The Guide was like this:
Use this tool from this thread (https://forum.xda-developers.com/red-magic-3/how-to/tool-nubia-red-magic-3s-unbirck-tool-t4025207) and enjoy the much more stable firmware of the RM3S "END"
And like i said in my previous posts, i asked him for a detailed explanation because what he said does not work, it always ends up with sahara_rx_data:237, i even tried on my laptop with with windows 7 fresh install
Then he suddenly reacts like a 12 years old and deletes everything
Alex4455 said:
Aggressive people ? Guide ?
The Guide was like this:
Use this tool from this thread (https://forum.xda-developers.com/red-magic-3/how-to/tool-nubia-red-magic-3s-unbirck-tool-t4025207) and enjoy the much more stable firmware of the RM3S "END"
And like i said in my previous posts, i asked him for a detailed explanation because what he said does not work, it always ends up with sahara_rx_data:237, i even tried on my laptop with with windows 7 fresh install
Then he suddenly reacts like a 12 years old and deletes everything
Click to expand...
Click to collapse
Well, you said his post was a bad joke that comes off as aggressive, even if the guide is dangerously unexplained he didn't wrote it with malicious intent so you shouldn't talk to a fellow forum member that way.
I think he is onto something, it seems reasonable that if RM3 and RM3S share so much hardware in common their firmwares won't differ that much either.
Sangyedorje said:
Well, you said his post was a bad joke that comes off as aggressive, even if the guide is dangerously unexplained he didn't wrote it with malicious intent so you shouldn't talk to a fellow forum member that way.
I think he is onto something, it seems reasonable that if RM3 and RM3S share so much hardware in common their firmwares won't differ that much either.
Click to expand...
Click to collapse
Bad Joke of a guide is considered aggressive these days ? Whoaw, the newer generation is way over sensitive
Besides the so called guide, i lost almost 4-5 hours investigating this so called guide with error fixing and so on, here is what worked for me
The below "what worked for me steps" resulted and complete WIPE of the device !
I have no responsibility over bricked devices, i simply shared what some one did not bother to "info"
Do this on your own RISK !
What worked for me as on flashing the RM3s firmware on my RM3 is that 1st of all you need Windows 8.1, i tried on different hardware AMD and Intel with the Unbrick Tool RM3S and does not work on Windows 10 no matter what (windows 7 did not worked on Ryzen and my Laptop)
1. Have Windows 8.1 X64 (i used my Intel Celeron Laptop)
2. Have the drivers for the QDLoader HS-USB Driver_64bit_Setup
3. Download the tool for the Unbrick RM3S
4. Install the QDLoader drivers on the newly installed windows 8.1 and choose to restart
5. Turn the phone off and leave it like that until the Unbrick tool is ready
6. Run the Tool's exe and let it extract (the RM3S Unbrick Tool)
7. Power on the Phone holding PWR and Vol Down
8. Connect to a USB 2.0 port directly in to the motherboard with a quality cable
9. Select EDL mode from the Bootloader menu of the phone
10. Search within Device manager the phone's COM port
11. When the tool is ready, input the COM Number and select continue and install
These steps worked for me and phone booted fine... Conclusion is: I went Back to CN V2.38 and restored backup via TWRP, no performance gain, the device is still seen as RM3 but running with RM3S firmware
GPU and CPU frequency is of a normal SD855
My personal opinion is: This is a waste of time after all the hype I've gotten in to believing it would run like a SD855+
Alex4455 said:
Bad Joke of a guide is considered aggressive these days ? Whoaw, the newer generation is way over sensitive
Besides the so called guide, i lost almost 4-5 hours investigating this so called guide with error fixing and so on, here is what worked for me
The below "what worked for me steps" resulted and complete WIPE of the device !
I have no responsibility over bricked devices, i simply shared what some one did not bother to "info"
Do this on your own RISK !
What worked for me as on flashing the RM3s firmware on my RM3 is that 1st of all you need Windows 8.1, i tried on different hardware AMD and Intel with the Unbrick Tool RM3S and does not work on Windows 10 no matter what (windows 7 did not worked on Ryzen and my Laptop)
1. Have Windows 8.1 X64 (i used my Intel Celeron Laptop)
2. Have the drivers for the QDLoader HS-USB Driver_64bit_Setup
3. Download the tool for the Unbrick RM3S
4. Install the QDLoader drivers on the newly installed windows 8.1 and choose to restart
5. Turn the phone off and leave it like that until the Unbrick tool is ready
6. Run the Tool's exe and let it extract (the RM3S Unbrick Tool)
7. Power on the Phone holding PWR and Vol Down
8. Connect to a USB 2.0 port directly in to the motherboard with a quality cable
9. Select EDL mode from the Bootloader menu of the phone
10. Search within Device manager the phone's COM port
11. When the tool is ready, input the COM Number and select continue and install
These steps worked for me and phone booted fine... Conclusion is: I went Back to CN V2.38 and restored backup via TWRP, no performance gain, the device is still seen as RM3 but running with RM3S firmware
GPU and CPU frequency is of a normal SD855
My personal opinion is: This is a waste of time after all the hype I've gotten in to believing it would run like a SD855+
Click to expand...
Click to collapse
Can you tell if it far more stable and less bug than our rm3 fw? As for the performance it depend on device prosessor.