Related
Hi, I apologize up front for the long winded post, but I want to relay as much info as possible in the hope that someone can point out my mistake(s).
This is the 2nd android phone I have managed to brick in the past couple years.. The first was an old dream and I flashed the wrong update file for a different phone by accident, but at least I knew what I did wrong that time.
Fast forward to yesterday. I picked up a brand new LG Optimus 2X (LG-P999 = G2X) From Wind Mobile in Canada running android 2.2.2. I bring it home and load up super one click and it tells me I am rooted, great! After that I loosely followed these instructions: hxxp://wiki.cyanogenmod.com/wiki/LG_Optimus_2X:_Full_Update_Guide to get ClockworkMod Recovery installed via the market (free version).
First little hiccup was that when I opened the mod manager and tried to click on 'Flash ClockworkMod Recover' it gave me an error saying, "Error while downloading from Server. Please make sure that you have a stable internet connection, and that your SD card is inserted and has free space!". That's weird.. I have a brand new 2gb sd card and my 3g connection is working great.. I was able to sort that out by connecting to my home wifi connection and then this message disappeared. When flashing clockwork it asks for my model of phone and I choose the LG G2X from the list. Success! Although when I try to click on the option to boot into recovery -- nothing happens. Since I don't want to power off my phone, I download "Quick Boot" by Sirius Applications Ltd. and try to click the reboot option, but again, nothing happens. The recovery option also does nothing, whats going on here? I finally decide to power down my phone the "normal" way from the home screen.
I boot back up normally and realize that I didn't download cyanogenmod yet, so I go do that. I download update-cm-7.1.0.1-G2x-signed.zip for the T-Mobile G2x, even though mine is not T-Mobile, I read on the internet that I definitely have a G2x even though it is marketed as an LG Optimus 2X. I also download the Google apps gapps-gb-20110828-signed.zip.
Once the files are downloaded, I attempt to copy them up to the memory card, but windows explorer (Im using Windows XP) seems to lock up for a bit and I get a weird error: Cannot copy gapps-gb-20110828-signed.zip: The path is too deep. I have never seen this copy error before. I look it up on google and don't get much help, although it tells me what I already assume, that this error appears when your filename + path combo is too long. But its not too long! gapps-gb-20110828-signed.zip is on my desktop, and I'm copying to the root of F:\ !! The other weird thing is that this gapps-gb-20110828-signed.zip is only 6MB large. I have no problem copying the update-cm-7.1.0.1-G2x-signed.zip which is 93MB! I can copy any other file I throw at it.. BUT I CANT COPY THE GAPPS FILE !? I tried so many things at this point. I renamed gapps-gb-20110828-signed.zip to gapps.zip. I redownloaded it from the mirror. I tried copying it from the root of C:\ and another drive. I tried unzipping it and rezipping it. I always got the same error.
Finally I decided to copy the gapps file to the internal memory, and it copied without a problem. I wasn't sure if I could access that drive from recovery, but I decided to try it, even without gapps since I wasn't having much luck getting it onto the card. In hindsight, I should have maybe tried copying it to another sd card and also tried copying to the same sd card plugged into my computer via sd reader to see if the same problems existed. Even rebooting the phone and my computer would have been some good troubleshooting, but I wasn't aware of what would happen next.
I booted to recovery at this point (I can't remember if I booted via the rom manager link or if I rebooted and held the power and volume down button) and it came up as expected. I first made a backup of the existing system even though I didn't think I really needed it. Then I did the Wipe data/factory reset and Wipe cache partition. Finally, I loaded the cyanogenmod update and was surprised at how it loaded in mere seconds-- my old dream always took at least 1 or 2 minutes even for a smaller file. I then noticed an option to load a zip file from my the other storage (I can't remember the exact name of the option - but it was the place where the gapps file was). I loaded gapps without error and rebooted the phone.
It is at this point that I never booted back into anything again. If I remember correctly, it loaded the first LG symbol as usual, and then I saw another 'fancier' LG logo come up, with no animation or progress bar. I waited on this screen for more than 10 minutes, expecting that it would finally change to cyanogenmod, but nothing ever happened. No problem I thought, I can just boot back into recovery and try again without the gapps perhaps. No dice. I removed and replaced the battery, and then booted up with the power and volume down arrow held. I saw a LG symbol with progress bar, I saw a android character coming out of a box with a progress bar. I let go of the buttons. The phone rebooted. I tried again and again. Nothing.
At this time I was getting quite worried, but I had my phone plugged into the computer still and I noticed that everytime I got to the 'fancier' LG logo screen, the computer would recognize the phone via usb. I decided to see what the internet offered for solutions and I read lots and lots of info.
Everything boiled down to pulling out the battery, holding the volume up and down buttons and then plugging the usb to the computer. I installed all the necessary drivers and ran nvflash in an attempt to either install CWM or even the stock recovery. Getting the computer to recognize the phone properly was a chore in itself. Often it would come up saying 'Unrecognized usb device' or it would simply show up in the device manager with an "!". Sometimes when it showed up with the "!" I would right-click and uninstall it, then unplug and replug and install the driver again and that would work for a time or two.
The problem was that when I ran any commands I found for nvflash, it seemed to take forever to do anything. I mean I would be waiting, and waiting, and waiting, and all the command prompt would say is:
"Nvflash started"
One post I read somewhere said to just try a harmless command of "nvflash --sync" to see if the proper output appeared. I tried it a few times, but all I got was the same "Nvflash started", but then one time I noticed after a while it came up with a new line after that of "rcm version 0X20001". I tried nvflash at least 1000 times, no joke. I wasn't about to let this brand new phone beat me without a fight.
On one occassion I tried using the "One Click Recovery Flasher" that I found, and I attempted to load the stock recovery. The response from nvflash seemed to flow a little quicker this time and I got further in the process then ever before. Since it was now 4am I decided to let it do its thing and I would wake up and check it in the morning. I woke up at 10am and it was exactly where I left it. After 6 hours, I would have expected it to do SOMETHING! Here is what it said:
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x037c704243a08357
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
It apparently was unable to send the fastboot file for some reason. I could try 1000 more times but I am defeated at this point. I am planning to return the phone today and see what they say. If by chance I return it successfully, and I get the same model of phone, I will be super wary of trying to root it again. But I also don't want a phone that I can't "have fun with". Any comments or suggestions are most welcome. I would like to know what I did wrong so that I can learn for "next time". Other than the weird sd card error, I really think I did everything correct. At this point I am thinking there was either something wrong with the sd card or even with the phone itself. Regardless, I thank you for reading my story and I look forward to any helpful responses.
Cheers!
I'm also on wind. The first thing I did was use nvflash to get a recovery. Never never use ROM manager to flash recovery on the g2x. It's a fake flash. Also, try running a vm or dual boot to use Linux. Nvflash worked fine on Linux didn't try on windows. no drivers needed. It recognizes it without doing anything special.
Sdcard problem is because the 2GB card is under /emmc or /sdcard/_Externalsd our something on stock.
tahahawa said:
I'm also on wind. The first thing I did was use nvflash to get a recovery. Never never use ROM manager to flash recovery on the g2x. It's a fake flash.
Click to expand...
Click to collapse
Did the same thing. I am on Linux too, and everything was extremely simple.
BTW, I think Wind's LG doesn't have screen bleeding or rebooting issues. I've never had them.
It sounds like you didn't install the drivers for the APX mode. When you get the explanation mark you need to right click and say update driver, then says I will find myself and browse to the apx directory where you extracted the One Click program for NVFlash. Then when it says the driver is unsigned click yes to continue. Once the apx driver is properly loaded you can flash CWM and reflash any rom you want. Don't worry your phone is not bricked. It is almost impossible to truly brick a G2X.
Did you resolve this issue. I just encountered it myself. Are you in Toronto by any chance. [sigh]. This sucks. I hope you can help shed some light.
Did you see my advice above? Try that. Also try re downloading everything, including all nvflash files.
Sent from my LG-P999 using XDA App
Awesome. Nvflash unbricked the SOB. I used the youtube video (lookup this one: "How To Install CyanogenMod 7 Nightly on T-Mobile G2x after Nandroid Backup") and the G2x P999 ROM from cyanogen, and got my phone back. The video worked perfectly for me and I would recommend it (but of course don't blame me if anything goes wrong... why should I be different? . The T-mobile stuff bugs me though. I wonder why the cyanogen mod has their branding in it. Ah well.
Now that my phone works again, I can figure out how to get those annoying lines to stop moving all over the frickin' place. Then back up this ROM so I have something to recover to. And maybe try the cynaogen Optimus 2x ROM; although it does say in the file name that it is 990 and not 999. And maybe give the fine xda ROM a go (since I found the answer here).
Thanks to Wind Mobile for messing around with the names and making it confusing. The Optimus 2x by Wind is a P999 and the same as what T-Mobile has, and an Optimus 2x looks to be a 990 everywhere else in the world. I guess Wind never intended to make it easy to upgrade these phones from the start (and aren't offering an official Gingerbread, never mind Ice Cream Sandwich upgrade). Now it looks like they won't even be selling them any more. I guess they would cut into the profit of the new more expensive Galaxy when it comes out.
I know I won't use that ROM manager again. At least not for this phone. Wow!
Thanks again for the quick reply and sticking my nose back into the answer.
Regards,
BillR
tahahawa said:
Never never use ROM manager to flash recovery on the g2x. It's a fake flash.
Click to expand...
Click to collapse
Is this true of ROM Manager in general, or is this something particular to the G2x?
dmj2012 said:
Is this true of ROM Manager in general, or is this something particular to the G2x?
Click to expand...
Click to collapse
Just the g2x/optimus 2x.
theshowmecanuck said:
Awesome. Nvflash unbricked the SOB. I used the youtube video (lookup this one: "How To Install CyanogenMod 7 Nightly on T-Mobile G2x after Nandroid Backup") and the G2x P999 ROM from cyanogen, and got my phone back. The video worked perfectly for me and I would recommend it (but of course don't blame me if anything goes wrong... why should I be different? . The T-mobile stuff bugs me though. I wonder why the cyanogen mod has their branding in it. Ah well.
Now that my phone works again, I can figure out how to get those annoying lines to stop moving all over the frickin' place. Then back up this ROM so I have something to recover to. And maybe try the cynaogen Optimus 2x ROM; although it does say in the file name that it is 990 and not 999. And maybe give the fine xda ROM a go (since I found the answer here).
Thanks to Wind Mobile for messing around with the names and making it confusing. The Optimus 2x by Wind is a P999 and the same as what T-Mobile has, and an Optimus 2x looks to be a 990 everywhere else in the world. I guess Wind never intended to make it easy to upgrade these phones from the start (and aren't offering an official Gingerbread, never mind Ice Cream Sandwich upgrade). Now it looks like they won't even be selling them any more. I guess they would cut into the profit of the new more expensive Galaxy when it comes out.
I know I won't use that ROM manager again. At least not for this phone. Wow!
Thanks again for the quick reply and sticking my nose back into the answer.
Regards,
BillR
Click to expand...
Click to collapse
Never flash anything meant for p990. Period. Unless it states it is for both. cyanogenmod had no Tmobile stuff except wifi calling.
Sent from my LG-P999 using XDA App
tahahawa said:
cyanogenmod had no Tmobile stuff except wifi calling.
Click to expand...
Click to collapse
When I first started the phone a message came up asking me if I wanted to run something, and that I could go to the T-Mobile site later if I didn't want to. Now I have been playing with it for the last hour and haven't seen any other TM related stuff, so maybe it was just that one.
The very first time it runs you get that message from the wifi calling app. You should never see it again unless you do a factory reset.
I have an urgent question regarding rooting my new Optimus V (Virg Mob), that if possible, i could use an immediate answer for i have very limited time.
I recently purchased a like new, used Optimus V 2.2 o/s off a friend, that is currently not-activated on the Virgin Mobile network, but have been sending/recieving calls and texts through Wi-Fi apps such as Line2 and netTalk. Is it possible to use sublimewulf's method of rooting the opt_v without service (prefer one click root)? i understand that it says it must be activated, but im curious if Wifi will work just as good, or if there is a simple ''one click root'' method i could use. im just not sure why it must be active, im not sure what is done during the one-click method.
Can I root my Optimus V with a One Click root program/app WITHOUT service/activation? If so, could someone please point me in the direction of the download + instructions? Much thanks, its greatly appreciated for all future help- you have no idea..
Thanks XDA Dev team + members,,
Southcide
Here you go...
http://androidforums.com/optimus-v-...astboot-style-fastest-easiest-way-around.html
Just click the thank button ;-)
Thank you very much, is it normal for the file to be especially large? not sure if the optimus could fit a 173mb file.
Also, what are the chances of this bricking my opt.v or ultimately destoying the operation of the phone??
Also, could you recommend a few ROM's? I heard cyanogenmod is rather popular, but what is it? whats it do- what makes it so special, i guess is what im trying to say. also, is it possible to put the new gingerbread o/s on my opt? would it run as smooth as it runs as is? thanks again, so
what would be a nice ROM to install, and where can they be found (free). also, what are the chances of this root device destroying my handheld, or bricking it? thanks again bro for the fast and accurate response! +thanks for sure!
Oh also,
Asadullah said:
(DEPRECATED)
I no longer support or care to support this is someone wants to take over and deal with this and the complaints go for it. It has not been tried on the 2.2.2 version of android in case you want to try it.
Click to expand...
Click to collapse
What is the meaning of this, under the fastbootroot thread? if this program at least works, why would he tag it as being deprecated? also saying he is tired of the complaints. please exp?
thank you. im trying to avoid the slightest bit of damage done to my new phone.
***EDIT::: Do i download the files (from the link you posted) to my phone, or my pc??
He means the complaints of him not working on it.
All you have to do is download this on your computer, as well as the LG drivers, and choose the [Full Package] option, and it will root your phone. Afterwards, see if you can get into recovery, and if not, run the program again and choose the [Flash a custom recovery] option.
Ive used this several times, never a problem.
Best ROM for me was Harmonia, which can be found on Android Central.
i tried both quickbootroot (your link/app posted above) , and also SuperOneClick v2.2, and neither one worked. I tried SuperOneClick, opened the program, and clicked [Root], (after connecting USB to droid, and turning on debugging), and it froze at Stage 2. How do i fix this, and what could cause it?
Im not sure if the cable im using is a charging cable ,or a data cable. i didnt think it would matter, but anyway, how can i tell, and would this cause it?
When i tried the quickbootroot, i opened the .bat file, the disclaimer came up, i hit [y] and enter, and it just went away- nothing happened...
I also ran the usb drivers exe on the computer (i hope this was right), and nothing happened from it neither.
What did i do wrong, and how do i fix this problem? I just want to root my device already...
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.
hopefully this will help out some people and the developers to make,fix,restore a not so popular phone. I did a total firmware dump and have uploaded to my 4shared folder. If anyone is interested or can tell me how to upload it here for developing i will be more than happy to share with those in need. I also have a spare phone that i would be willing to test anything made from the firmware dump i created.
PLEASE link?
Some time after rooting my Optimus Zone 3 VS425PP, I got locked into a boot loop. There are no custom ROM's, neither recovery nor OS. It's not bricked. Yet, anyway. The loading screen functions, then a little window that says "OPTIMIZING APPS 1 OF 5, PLEASE DO NOT REMOVE THE BATTERY..." appears. I've seen this before, but now, upon reaching "APP 5 OF 5," it reboots and repeats. I've tried several factory resets via the LG RECOVERY (MODIFIED,) as well as safe mode to no avail. Anyone? Anything? Help? The only recourse I can think of would be to re-flash the stock ROM, which I cannot find. Anywhere. Thanks, guys.
i tried contacting judthro for the same file; no luck
Cruise Elroy said:
Some time after rooting my Optimus Zone 3 VS425PP, I got locked into a boot loop. There are no custom ROM's, neither recovery nor OS. It's not bricked. Yet, anyway. The loading screen functions, then a little window that says "OPTIMIZING APPS 1 OF 5, PLEASE DO NOT REMOVE THE BATTERY..." appears. I've seen this before, but now, upon reaching "APP 5 OF 5," it reboots and repeats. I've tried several factory resets via the LG RECOVERY (MODIFIED,) as well as safe mode to no avail. Anyone? Anything? Help? The only recourse I can think of would be to re-flash the stock ROM, which I cannot find. Anywhere. Thanks, guys.
Click to expand...
Click to collapse
Unfortunately, I don't think this file is actually out there. I have REALLY been looking, even contacted the LG Development team. The LG Support Tool, etc. are not going to help you yet as they do not have the firmware on their servers yet. That's why the LG Support Tool will freeze when trying to do an Update Recovery on this phone. -- And I've tried them all: LG Mobile Support Tool, LG PC Suite, Verizon VS425PP Update Tool (from the mounted drive on the phone), LG Flash Tool 2014 to force different KDZ files. All provide nothing. All dead ends. The Optimus won't grab a COM unless it is the right signed firmware for the phone. You'll just sit there in Download Mode or in Debug mode forever with no result. We have to wait for the first update from LG from version VS425PP1 to whatever comes next so they have something to stick on their server. But...if you find something before then, please let me know! The update will eventually be released to the public. It'll probably just take a year or so.
Good thing is Wal-Mart sells these for under $12 (yes, that's right). I picked up seven of these quad-core bad boys at that deal. Just bugs the hell out of me I can't fix the one I over rooted.
this *might* be promising...
Cruise Elroy said:
Some time after rooting my Optimus Zone 3 VS425PP, I got locked into a boot loop. There are no custom ROM's, neither recovery nor OS. It's not bricked. Yet, anyway. The loading screen functions, then a little window that says "OPTIMIZING APPS 1 OF 5, PLEASE DO NOT REMOVE THE BATTERY..." appears. I've seen this before, but now, upon reaching "APP 5 OF 5," it reboots and repeats. I've tried several factory resets via the LG RECOVERY (MODIFIED,) as well as safe mode to no avail. Anyone? Anything? Help? The only recourse I can think of would be to re-flash the stock ROM, which I cannot find. Anywhere. Thanks, guys.
Click to expand...
Click to collapse
well i'll be. this may be a promising link:
google "4share lgvs425pp" and scroll down to the 4shared link. There is a 999MB RAR file claiming to be the VS425PP ROM dump. I'm downloading it now...checking it out.
It works???!!! i have to root this cellphone because i need use with other company...
its not super useful yet
johhnyapplefake said:
well i'll be. this may be a promising link:
google "4share lgvs425pp" and scroll down to the 4shared link. There is a 999MB RAR file claiming to be the VS425PP ROM dump. I'm downloading it now...checking it out.
Click to expand...
Click to collapse
hopefully the op will chime in for insight. The 999MB isn't much good. It appears to be a RAR dump of all the partitions, perhaps made from a lglaf.py script while in download. Nevertheless, i havent found any way yet to push the firmware dump onto the phone.
I've had no luck, either.
johhnyapplefake said:
hopefully the op will chime in for insight. The 999MB isn't much good. It appears to be a RAR dump of all the partitions, perhaps made from a lglaf.py script while in download. Nevertheless, i havent found any way yet to push the firmware dump onto the phone.
Click to expand...
Click to collapse
Meanwhile, as my LG cycles endlessly through my really cool "Jolly Roger" boot animation, I stumbled across a Kyocera Hydro Wave at Walmart for $20. I snapped it up to replace the LG Optimus Zone 3. I had big plans to root it, too., but I should've researched it first. The specs are great... but one check on Cyanogen's website probably would've saved me some trouble. Not one Kyocera device is listed there. XDA thread also throws red flags-no one can get root to stick. Well, I at least learned a lesson. Next time, I plan to purposefully buy a phone that can be rooted, has been rooted, has instructions online to do so, AND has at least one custom ROM available! No wonder this thing was $20! Keep us all posted if you stumble across a bootloop fix of some kind, and I'll do the same.
here is stock recovery for this device https://www.dropbox.com/home/Apps/Flashify/VS425PP/recovery
matt4787!
Either I am unable to open that link from an Android device OR the link given is to an unshared folder? It just asks me to log in and then says 'that folder does not exist in your DropBox...' PLEASE check out the SHARE link from within your DropBox and maybe share a new folder (and drop the stock ROM in there, along with what you might've used to flash it maybe?) We'd be very grateful!
Recovery
https://drive.google.com/file/d/0B1Nk8cx3_QgAeGNxZ1JrUmtFS0E/view?usp=drivesdk
Try now
hope my post helped some ppl. now to get twrp recovery ported here.
Thank you matt4787!!
Sent from my C6740 using XDA-Developers mobile app
To all who have a bricked,phone this phone has an update. Download the LG software assistant and put assistant in repair mode then boot phone normally and wait a bit. Run the repair assistant and let it run. Hopefully if everything runs well as it did me. Mine is restored and running.
Just ordered one. Is there root for this phone? Unlocked bootloader or forgetaboutit?
I rooted this phone and then tried to de-bloat, but I must have deleted too much. Now when I boot all I get is "Security Error - Authentication Fail #9"
I can get to Download mode, but none of the recovery programs recognize the phone. I installed the drivers, but still nothing. Is there anything I can do?
matt4787 said:
To all who have a bricked,phone this phone has an update. Download the LG software assistant and put assistant in repair mode then boot phone normally and wait a bit. Run the repair assistant and let it run. Hopefully if everything runs well as it did me. Mine is restored and running.
Click to expand...
Click to collapse
was your phone in a "security error" loop? for some reason the software assistant won't recognize my phone. it'll identify a plugged in phone when I connect it in download mode, but the device model never shows up
nikicollazo said:
was your phone in a "security error" loop? for some reason the software assistant won't recognize my phone. it'll identify a plugged in phone when I connect it in download mode, but the device model never shows up
Click to expand...
Click to collapse
i forgot to mention that you have to be in download mode to make the assistant recognize the phone. plus make sure the drivers for the phone are installed on your pc
matt4787 said:
i forgot to mention that you have to be in download mode to make the assistant recognize the phone. plus make sure the drivers for the phone are installed on your pc
Click to expand...
Click to collapse
hello as you did to install the drivers , I find no way to reconnoitre the mtp device ! Thank you
angelgabg said:
hello as you did to install the drivers , I find no way to reconnoitre the mtp device ! Thank you
Click to expand...
Click to collapse
this one is troubling. hmm you got the stock rom from lg? if so then try downloading the drivers from verizon.
Any updates on recoveries? I hate being scared of tweaking due to not having a backup .-. Anyone find something? Plz lemme know, thx! Btw kingo root 4.5 seems to have root for this phone but super sume seems to brick it. Just a heads up eace:
Picked up an AT&T Radiant Core for cheap at a store around me. I don't intend to use it with AT&T, it was just such a low price that I figured I'd get it and see if I can break into it just for fun. It's an MTK6739 chipset phone, so in theory it should be easy to pull partitions from this thing with something like SPFT (or Miracle Box, if you paid for it) and do a dirty port of TWRP to get root privileges on it. But this is harder than it seems.
I need an auth file to do anything with SPFT. Apparently this has to do with some kind of "secure boot" mechanism that MediaTeks sometimes have now. There's no stock firmware for this device online from what I can find, nor for the generic version of the device, the Tinno U304AA (AT&T just rebranded it). If I had a stock firmware image, maybe I could risk wiping the partitions and reflashing the stock firmware to get rid of the secure boot stuff.
I saw a guide for how to access the bootloader on the Tinno U304AA generic version, but on the AT&T version of the phone there's no option in the boot select menu (Vol. UP + Power) to get to the bootloader to run a fastboot oem unlock. All the AT&T version has is recovery and normal boot. I'm not sure what I can do to maybe reset this to get the other options. Maybe if I had the stock firmware for the generic version of the phone I could overwrite it and get access to those other options.
Either way, just posting this up for anyone else that got one of these and wants to collaborate/contribute. Maybe with enough collective brainpower we can make something happen.
UPDATE: found a stock system image dump, thank you to @lopestom for directing me to this. This guy's been the MediaTek king for as long as I can remember.
It appears to be a dtbo and system partition dump. It also has the vendor partition and a (partial?) boot image dump. Not sure if things like the full boot and recovery images are stored somewhere in here, I didn't look too deeply into it yet. I have no idea how whoever this is managed to pull these partitions... they either got root access somehow, or they found a proper Download Agent and Auth file to pull it all. Either one of these would be awesome. I reached out to the user to ask them how they did it, we will see what they say if they want to share how they did it.
https://git.rip/dumps/att/u304aa
jasonmerc said:
Picked up an AT&T Radiant Core for cheap at a store around me. I don't intend to use it with AT&T, it was just such a low price that I figured I'd get it and see if I can break into it just for fun. It's an MTK6739 chipset phone, so in theory it should be easy to pull partitions from this thing with something like SPFT (or Miracle Box, if you paid for it) and do a dirty port of TWRP to get root privileges on it. But this is harder than it seems.
I need an auth file to do anything with SPFT. Apparently this has to do with some kind of "secure boot" mechanism that MediaTeks sometimes have now. There's no stock firmware for this device online from what I can find, nor for the generic version of the device, the Tinno U304AA (AT&T just rebranded it). If I had a stock firmware image, maybe I could risk wiping the partitions and reflashing the stock firmware to get rid of the secure boot stuff.
I saw a guide for how to access the bootloader on the Tinno U304AA generic version, but on the AT&T version of the phone there's no option in the boot select menu (Vol. UP + Power) to get to the bootloader to run a fastboot oem unlock. All the AT&T version has is recovery and normal boot. I'm not sure what I can do to maybe reset this to get the other options. Maybe if I had the stock firmware for the generic version of the phone I could overwrite it and get access to those other options.
Either way, just posting this up for anyone else that got one of these and wants to collaborate/contribute. Maybe with enough collective brainpower we can make something happen.
Click to expand...
Click to collapse
OMG! So excited to see this here! My Mom gave my nephew this phone and niece has one. So I've been trying my best to get the thing to at least be a decent phone! I installed a launcher on it, changed the icons and wallpaper and made it look good at least. It will be nice to have someone to talk to about this. The thing has been beyond frustrating! First off though how did you get the computer to recognize it? I can't get Windows or Linux to recognize it and couldn't find any drivers. If you managed that much you got further than I did. I haven't tried with my nieces though. It might just be his phone. She's 13 so it took awhile to pry it from her long enough to find out what kind it was, but I'm willing to try to get it from her once again if the phone can be improved.
sjjtnj said:
OMG! So excited to see this here! My Mom gave my nephew this phone and niece has one. So I've been trying my best to get the thing to at least be a decent phone! I installed a launcher on it, changed the icons and wallpaper and made it look good at least. It will be nice to have someone to talk to about this. The thing has been beyond frustrating! First off though how did you get the computer to recognize it? I can't get Windows or Linux to recognize it and couldn't find any drivers. If you managed that much you got further than I did. I haven't tried with my nieces though. It might just be his phone. She's 13 so it took awhile to pry it from her long enough to find out what kind it was, but I'm willing to try to get it from her once again if the phone can be improved.
Click to expand...
Click to collapse
Linux should just work, plug in the thing and the "drivers" if you will should be there already. Check the phone's settings for USB Debugging in the Developer Options if there's further trouble.
Don't get me wrong too, this phone is, was, and will always be a piece of junk. There's no getting around a screen this bad and 1GB of RAM. I'm actively trying to find a Download Agent and Auth File combo to get this thing to work with SPFT so I can try to port a custom recovery to get us Magisk root permissions at least. Root will make the phone slightly better, but it will still be junk. Unless we can get kernel source for it as well to mess with things like clock speeds and CPU governors (which LEGALLY we are supposed to be guaranteed, but good luck convincing a Chinese company to give it to you) everything we do, if we CAN do anything, will be like deodorant on a turd. It'll smell a little better, but it's still a turd.
jasonmerc said:
Linux should just work, plug in the thing and the "drivers" if you will should be there already. Check the phone's settings for USB Debugging in the Developer Options if there's further trouble.
Don't get me wrong too, this phone is, was, and will always be a piece of junk. There's no getting around a screen this bad and 1GB of RAM. I'm actively trying to find a Download Agent and Auth File combo to get this thing to work with SPFT so I can try to port a custom recovery to get us Magisk root permissions at least. Root will make the phone slightly better, but it will still be junk. Unless we can get kernel source for it as well to mess with things like clock speeds and CPU governors (which LEGALLY we are supposed to be guaranteed, but good luck convincing a Chinese company to give it to you) everything we do, if we CAN do anything, will be like deodorant on a turd. It'll smell a little better, but it's still a turd.
Click to expand...
Click to collapse
Right, I'm considering giving him my current phone when I get a new one. It doesn't seem like I'm going to be able to unlock and root it so I want a phone I can. Mainly for space personally. He's young so he doesn't need it rooted, but I'm thinking if I can root it then I might be able to use it to root my phone. Speaking of rooting I think I found a way to root this phone. It took me a couple days to get the phone since he said he couldn't find it, but I have it now. It just needs to charge, but the battery sucks so it takes forever. I did find out that it does have a decent recovery. I had booted it into recovery and then I was messing around with the keys after the little passed out green guy popped up and suddenly it loaded stock recovery. It had an option to mount the system and flash with adb and everything. The only problem is I kept booting it by messing with keys. So I honestly don't know which ones worked. I kept booting into it last night by messing with them, but now I can't seem to get it to boot into the right recovery now that I'm trying to figure out the right key combination. I will figure it out though (eventually) and let you know what you have to click, but if you get the chance just mess with it and hopefully you'll find it like I did.
Also I was looking up the phones variants and downloaded a couple stock roms that I felt had all the right specs I'm going to try to flash one if I can get it plugged in. I downloaded custom twrp image's for them as well, and even found one twrp that I was able to download in the app. If you used it then you know that it takes you to a download page if you are downloading the wrong twrp.img. So the fact it let me download it in the app meant it tricked twrp into thinking it was that phone. So I'm going to try that stock rom first. Maybe we'll be able to change it to another model. It really needs something flashed, because it's a mess. I thought he messed it up, but after reading what you said maybe it's just the phone. He's young so it doesn't matter as much to him, but I feel bad for my niece. I really need to look into at least getting her another phone. I'm going to work on it later today and see what I can do. First I got to get it to work on the computer, but I may be able to root it without the computer. I'll keep you updated with my progress.
any luck with this?
Yeh, is there a status update?
Sorry, I got a concussion and haven't been able to do much, but really I'm stuck because I can't get it to connect to the computer at all. Not in Windows or Linux. I think he's messed it up beyond repair at this point. The offline root gave me an error around the mounting of the system, but that can be done if you can get the recovery to show up. It's one of the options. I was trying this method. HERE see if you can get it plugged in and to work. Also, Kingoroot gets to 90% on the apk alone. So the computer app might do the trick. Then you can switch it to su. Really a rooted phone can get a lot done with apps like flashify and flashfire that we can't do right now. If you can get even a temp root let me know and I'll tell you what I found out about the apps to unlock the bootloader, flash TWRP, Flash Magisk, then flash ROMs. If you want to try the variant route I was trying then just do a search on google. Some sound just as bad, but other similar phones seem better. You can pick which one you want to try. The phone I have got to a point that it kept deleting applications and stuff on the phone and has trouble with the sd card. So I don't have the stuff I had saved on it anymore. I'm giving him my current phone when I get a new one. It's too messed up to salvage. I hope you have more luck.
sjjtnj said:
Sorry, I got a concussion and haven't been able to do much, but really I'm stuck because I can't get it to connect to the computer at all. Not in Windows or Linux. I think he's messed it up beyond repair at this point. The offline root gave me an error around the mounting of the system, but that can be done if you can get the recovery to show up. It's one of the options. I was trying this method. HERE see if you can get it plugged in and to work. Also, Kingoroot gets to 90% on the apk alone. So the computer app might do the trick. Then you can switch it to su. Really a rooted phone can get a lot done with apps like flashify and flashfire that we can't do right now. If you can get even a temp root let me know and I'll tell you what I found out about the apps to unlock the bootloader, flash TWRP, Flash Magisk, then flash ROMs. If you want to try the variant route I was trying then just do a search on google. Some sound just as bad, but other similar phones seem better. You can pick which one you want to try. The phone I have got to a point that it kept deleting applications and stuff on the phone and has trouble with the sd card. So I don't have the stuff I had saved on it anymore. I'm giving him my current phone when I get a new one. It's too messed up to salvage. I hope you have more luck.
Click to expand...
Click to collapse
I need to unlock my phone U304AA
Ok boys and girls, in case anyone is still wondering here is how to root this sucker.
https://drive.google.com/file/d/1--Ul1ae73zcejNuJ1a7ftq5sTo2VP8Ya/view?usp=drivesdk
Comes with two files. Mtksu amd magisk be sure to use the magisk version included in the zip. Install mtksu then wmagisk, open mtksu and install the top magisk option. Reboot then open magisk hit install when it asks. Now open mtksu scroll to the bottom and hit activate and reboot again. Should be good too go at this point. Oh yeah be sure to click apply at boot in mtksu. Not sure if this had been posted before or not. Now, to find a way to unlock bootloader and install twrp.
Thank you, I tried Mtksu on mine and it didn't work, but it might've been the phone. I don't have one of these anymore, but I hope you all the best of luck. For the bootloader and Twrp try Flashfire or flashify.
MTK bypass method released by some smart dudes out there. I will test if we can use SPFT on this phone now. Stay tuned. This could mean root & recovery in a matter of minutes.
EDIT: It ALMOST works. Technically it bypassed the auth file as advertised. The only thing left now is finding a compatible preloader/scatter file to use.
Used a modified Moto E6 Play scatter file to pull images from the device. Tried flashing over stuff and got an error. Long story short my U304AA is now permanently bricked, so I'm tapping out of this project here
I do have recovery and boot images that (supposedly) work if anyone else wants to try and take over Keep in mind these were pulled with a scatter file from a DIFFERENT phone that's of the same chipset, so not everything is guaranteed to work. For example, the preloader was pulled with the specified parameters but I do NOT know if it's functional
Because I'm tapping out, and because nobody else seems to have anything on this, I'm uploading everything I can. Some pulls are too big to upload and some just won't work for some reason, but use whatever you'd like for anything you can. Hope I did something helpful
I have searched in Google Search and the tutorials forum but not found a tutorial
_____________
Sent from my website: https://topsanphamhay.com/kem-chong-nang-danh-cho-da-dau-mun.html - https://topsanphamhay.com/kem-chong-nang-innisfree-perfect-uv-protection-cream-co-tot-khong.html - https://topsanphamhay.com/kem-chong...ifying-face-fluid-dry-touch-co-tot-khong.html using Iphone X
Well AT&T is giving away lots of Radiant Core devices because of their 3G shutdown: https://www.xda-developers.com/att-3g-shutdown-free-phone/
My wife and I just got one, so now I have two of these but I'm not sure I trust AT&T enough to use the "free" phone that they sent.
It would be great if someone can pickup this project, especially since so many phones are now flooding the market.
I just got 3 of these "free" from AT&T. In fact I don't really need them, I just happen to have phones with an IMEI number that AT&T cannot decipher, so they sent me new phones just in case I can't use 4G.
Anyway, I'm trying to use mine as spare Google assistants scattered around the house, but because they run that crappy Android Go, the Go version of Assistant won't listen to me until I long-press the home button. I would also like to use them when I travel as a spare.
These things are essentially throw-away, so I'm OK to risk bricking one of them.
What I really want to do is install a real version of Android on here, has anyone managed to crack this yet?
I personally have been writing and reading using this tool https://github.com/bkerler/mtkclient, which is much simpler than the others
Its a little rough around the edges, but it certainly works
My final problem is disabling secure boot (I already have a boot.img patched with magisk)
It appears that fastboot is simply not a mode for booting on this model, so I was wondering if anyone knows how to disable AVB by hand with just partition images
kayshinonome said:
I personally have been writing and reading using this tool https://github.com/bkerler/mtkclient, which is much simpler than the others
Its a little rough around the edges, but it certainly works
My final problem is disabling secure boot (I already have a boot.img patched with magisk)
It appears that fastboot is simply not a mode for booting on this model, so I was wondering if anyone knows how to disable AVB by hand with just partition images
Click to expand...
Click to collapse
if it's possible to downgrade the firmware to before the october 2019 patch, it might be possible to mtk-su the device: https://www.att.com/device-support/article/wireless/KM1376142/ATT/ATTU304AA
might be another alternative to trying to disable avb on a locked bootloader
luridphantom said:
if it's possible to downgrade the firmware to before the october 2019 patch, it might be possible to mtk-su the device: https://www.att.com/device-support/article/wireless/KM1376142/ATT/ATTU304AA
might be another alternative to trying to disable avb on a locked bootloader
Click to expand...
Click to collapse
Not possible to do, already tried before when I didn't brick it
KJ7LNW said:
Well AT&T is giving away lots of Radiant Core devices because of their 3G shutdown: https://www.xda-developers.com/att-3g-shutdown-free-phone/
Click to expand...
Click to collapse
Just got mine from this. I'd like to install something like NixOS mobile, but I've never used an android phone before. Will that be possible on this phone? If so, is there a good guide for newbs like myself?