Hello,
I was wondering what's the best ROM to flash onto the Dell Venue so that I could use it as a daily driver? I obviously want android of course because Windows sucks.
Also are there any guides that I could follow to install this on my phone? I've flashed ROMs on regular android devices but never windows.
Any help would be appreciated!
Thanks!
Hi, I think you could install either Deodexed 408 or CM7. Both of their links are now in Venue Development area, please have a look.
A rooted Deodexed 408, with bundled apps removed to suit your need is really what you might want to use as a normal user. Whereas, CM7 is great for ones who like a highly customizable ROM, or might want to build things on your own.
Just my 2 cents.
I've used Deoxed 408, CM7, and both working MIUI versions (there are 3 floating around XDA, only 2 work completely).
I prefer CM7 for it's look and feel. The MIUI's work great also, but I don't like the "in your face" graphics style. If you like those types of graphics/icons then the MIUI is a good choice. With CWM backup ability, it is easy to load several ROMs, customize them to your liking, and swap back and forth until you find one that you really like.
So i'm trying to get into fastboot mode to install CWM and I can't seem to get into it for the life of me.
I've turned off the power
slide the phone up (to show the keyboard)
held volume down & power
It just shows the dell logo and the phone boots up
I've also tried holding camera & power but I just get a cord connecting to a computer..which i'm sure isn't fast boot mode..any suggestions?
Indian9990 said:
So i'm trying to get into fastboot mode to install CWM and I can't seem to get into it for the life of me.
I've turned off the power
slide the phone up (to show the keyboard)
held volume down & power
It just shows the dell logo and the phone boots up
I've also tried holding camera & power but I just get a cord connecting to a computer..which i'm sure isn't fast boot mode..any suggestions?
Click to expand...
Click to collapse
I was afraid you had a Venue Pro rather than Venue from reading your original post. You can not install Venue specific firmware on to your Venue Pro.
Yea just realized it and there isn't any development for the pro..dang it. Thanks anyways guys!
Sent from my SGH-T989 using Tapatalk
I'm going to go ahead and lock this since it was accidentally placed in the wrong forum. If you would like it reopened and move please feel free to PM me about it.
Thread closed.
Related
Hello,
just bougth a low-cost and really little android phone: Alcatel OT-980. It's quite cheap as long I bought for 79 gpb from new. And it has quite nice specs:
-CPU 600mhz
-256 Rom / 192 Ram
-Android 2.1
-Slide-out QWERTY keyboard
Anyone is working on it? Is it possibile to have root access? What about a new page on XDA for it?
Let's start talking about it guys
So guys no one is interested in it?
I just purchased one of these things and it has a strange fault - the "hang-up" button seems to be constantly depressed so it's always trying to shut itself down. If I hold that button down it goes back to normal, it's like the button logic is in reverse or something.
Has anyone heard of this? It's nearly impossible to get Alcatel support in Australia.
Same one was just released on WIND Mobile in Canada.
Cool
Are you planning to buy one?
Nope, I have all the Androids I need for now.
Sent from my Nexus One using XDA App
I have the OT-981a (Wind version)
It's just another simple android phone.
Alcatel made some changes to the OS.
Took out the update feature (Probably because they will never support updates)
No live wall papers even though the software is installed.
It is running 2.1 update 1
The usual start up to get to programing mode
(Volume down + power) only restores the phone.
Think it would be pretty damn hard to make a rom for this.
Plus not a popular device so don't hold your breath as much as I would love to find a rom to work on this it is not likely.
Note universal androot does work but the NAT Filter is missing so no Wifi tethering ether
djtyres said:
I have the OT-981a (Wind version)
It's just another simple android phone.
Alcatel made some changes to the OS.
Took out the update feature (Probably because they will never support updates)
No live wall papers even though the software is installed.
It is running 2.1 update 1
The usual start up to get to programing mode
(Volume down + power) only restores the phone.
Think it would be pretty damn hard to make a rom for this.
Plus not a popular device so don't hold your breath as much as I would love to find a rom to work on this it is not likely.
Note universal androot does work but the NAT Filter is missing so no Wifi tethering ether
Click to expand...
Click to collapse
- Is there a bootloader mode in addition to this "recovery" mode?
- If it's rootable, and the bootloader is not locked, there is still some chance a custom recovery could be installed. The question is how many devs care to make a recovery and ROM specifically for this phone.
That is exactly my point no one would take the time for this device.
I tried to the usual bootloader sequence but just reset my phone.
Unless it needs the usb plugged in
What if there's another combo that involves booting up while holding one or two of the hard keys?
Sent from my Nexus One using XDA App
I have this phone too and I am really interested in any development
Hard Reset
Anyone know if there is a button combination for a hard reset?
Customer downloaded a brightness app on market and the "0" setting forced his screen to go black. Phone still runs in the background but you don't know where/what you're doing.
Help?
MY_TD2 said:
Anyone know if there is a button combination for a hard reset?
Customer downloaded a brightness app on market and the "0" setting forced his screen to go black. Phone still runs in the background but you don't know where/what you're doing.
Help?
Click to expand...
Click to collapse
Upthread it is reported that power + volume up results in some sort of factory reset. I wouldn't know because I don't have the phone.
Here is an alternate idea, but you'll need someone's help to tell you roughly where to tap on the screen or how many up-down strokes it will take.
- Unlock the phone (swipe, you'll feel the vibration)
- Press Home a few times so you're on your main homescreen.
- Is the Power Widget on one of your homescreens? If so, some hunting and pecking can probably get you to tap on the Brightness icon.
- If not, you may be able to long-press and add a widget blindly, and hopefully that widget will be the Power Widget.
MY_TD2 said:
Anyone know if there is a button combination for a hard reset?
Customer downloaded a brightness app on market and the "0" setting forced his screen to go black. Phone still runs in the background but you don't know where/what you're doing.
Help?
Click to expand...
Click to collapse
Volume Down + Power is hard reset to factory defaults.
It's what the usual recovery combo is on most android phones lol
backup / fs image
I've done a bit of hacking on my phone, got root, and used the adb shell to install busybox etc.
I'm trying to find a way to get a proper image out of the phone, I'm guessing that I can statically compile dd for it, and create dd images of the different partitions of the nand, on the SD, then loop mount them on a linux machine for development.
If there's an easier way, then I'd like to know about it
Based on that I imagine it would be possible to add in some of the changes that the G1 recovery images have for our phone.
Which version of busybox did you install?
Im going to try and catch up here lol
Is there any way to get the stock rom anywhere, or can anyone get them from the phone?
Ok I have found busybox as well as installed it,
I also sent an email asking if we could get support for the ot-981 from clockworkmods (Rom Manager) fingers crossed here.
That way we can a back up of the original rom
I'm trying to get the image off, dd doesn't work because the mtd block devices can't be read (perhaps because they are mounted, but I would still expect dd as root to be able to read them), and tar doesn't help much, because the tar function in busybox doesn't interpret the --exclude or -X parameters to exclude the sdcard dir (to avoid a recursive tar), and to exclude /proc and /dev and /sys.
I'm going to try to cross compile tar for android and hope to get a backup out that way.
Hi guys new to the scene and planning to get this phone as a low budget andriod device.. I hope you guys will be able to find a way to develop for this phone and more importantly upgrade it. It would be a big help! Thanks for all your hard work so far!!!
Hello Everyone, I'm totally lost Usually I can figure these things out myself by just following the directions but this phone is confusing. Not to mention I have no idea what was done to it.
I bought a used Dell Streak 5 after my phone took a dive down a flight of stairs (RIP phone). I thought this Streak was stock since that's what he posted in his ad, but apparently the guy rooted it and has an old version of the DSC rom on it (1.0 I believe). I do not like this rom at all, either because it needs to be updated or because something is wrong with this phone, I don't know. It reboots itself, even while I am on the phone, hangs constantly even when I try to do simple things like open a web page (I'm not expecting much out of a 3 year old phone--email, texting, web browsing, light app use like eBay etc). I want to either restore it to stock or put an updated custom rom on it, but 1) I have no idea what this guy did to it; there doesn't seem to be any recovery software on the phone and 2) every time I follow the directions here (rename the file update.pkg, press both volume buttons while pressing power etc), I get the option to update via the SD card, but after I choose that the phone restarts and hangs on the Dell logo, which forces me to pull the battery and then I'm stuck just going back to the home screen with this rom on here.
I don't know if it's me being stupid (if it is please tell me and if possible, please steer me in the right direction ) or if it's something this guy did to the phone. I can't return it (I would have already if I could). Thanks!
Well, you should certainly be able to restore it to stock, but I'm going to recommend using the current version of DSC and installing a custom recovery. However, before you get to that point we need to make sure your recovery is properly installed.
Your starting point is this thread: Everything you wanted to know about the Streak but were too busy bricking it. Within it you will find a link to the Dell Streak Flashing Guide, which will give you directions on how to enter into fastboot mode. You will also need to get the Dell drivers for ADB, or else the Streak will not be recognized in Windows. You'll find them here.
Once you are familiar with getting into fastboot mode and have the drivers installed, download MultiFlasher from the link in my signature and extract the files within the zip file to a directory on the root of your hard drive. Put your Streak into Fastboot mode, connect the Streak to the PC using the Streak's cable, then run MultiFlasher and follow the prompts to install the recovery image.
For DSC and all rooted stock ROMs I recommend installing Streakmod Recovery (included with MultiFlasher) as ClockworkMod recovery (also included) has an issue with hanging while attempting nandroid backups on stock ROMs.
When I tried to flash cyan fox in cmw it gave me a status 0 error can anyone fix?
We need more info like what did it specifically say. Be as specific as possible
Sent from my Nexus 4 using xda app-developers app
RedJack117 said:
When I tried to flash cyan fox in cmw it gave me a status 0 error can anyone fix?
Click to expand...
Click to collapse
that's "usually" an error you get when the zip is corrupted.
but occasionally you'll get it if your running an i9000 roms (I've had it interchangeably with status 7 before)
I would try re-downloading and flashing the zip again.
if that doesn't work try downloading and flashing fluid kernel
then go to "advanced" and select "reboot recovery".
then try flashing the rom again.
Status 0 error on anything I try to flash using CWM
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
jvrey5 said:
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
I would make sure that you realize that this phone is older and may not be up to the challenge of some of the newer games out there. Based on your PM to me, I understand that this is a secondary phone for you, so if you wanted to play some of the more graphic intensive games, I would do it on your DD.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
After you PM'd me, I started looking around about the Status 0 error being thrown. All signs point to the Updater Script that in the ROMs that you are flashing. My hunch is that once you flashed the CyanAOSP, that changed your build.prop from T959 to i9000 and that is why you are getting the error. I'm pretty sure there is a way to fix it (see below)
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
You should stay as far away from Kies as possible with this specific phone. It had a tendenacy to brick the Vibrants. It worked on my wife's SGS2 back when, but even then I was hesitant to use Kies on it and grinding my teath the whole time.
The zips that you mentioned are probably the standard Root.zip and the CWM zip from s15274n's thread stickied at the top of the Q&A section. Keep those handy.
Click to expand...
Click to collapse
Some answers in-line above.
**********************************
Let's get a few things straight before we start. I am still looking for the Heimdall JFD package, but I think that I know where it is. Pretty sure I put it on one of the external HDDs that I have. I'll try to upload it tonight or tomorrow night, as I am away all weekend with the family. I really don't think that you'll need it, but best to have it and not need it, than need it and not have it.
Theoretically, once you Odin'd back to JFD, I would think that it would've reset your device ID back to T959, but I guess that it didn't. This is what I would do. Odin to stock JFD and then boot it up and let it settle. Root it using the Root.zip that you have already used before. At some point you'll need to pick a ROM to settle on, even if only to get past this hump. (I use Sada's CM11 for my sons' Vibrants. Not that there is anything wrong with any of the others, but I just basically set it and forget it for my boys. I think though that he may have stopped development for it though, so I guess I'll be looking through the dev section myself here in the near future.) Take a look at this thread starting with my post #3 and the response from @nirogu325. I am thinking that if you do the same as he instructed, you will boot past the Status 0 error (since everything that I have seen in searches leads me to believe it is an Updater Script issue). My issue was a Status 7 because of the device ID being changed and the Recovery/Kernel combo weren't letting me flash. I basically opened up the ROM.zip and deleted those line and re-zipped it up and then flashed it (did it all on the phone and no PC, but I'm crazy like that).
Let's let a few of the current device Devs weigh in and see what they think. Already mentioned nirogu325 above, but let's try @epicboy and @dzee206 and @sada23. If they are inclined to come and help, it would be much appreciated.
jvrey5 said:
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
Click to expand...
Click to collapse
As Woody already said, you should odin back to stock 2.1. From there root and go to Jellybean and then KitKat. I'd recommend you stay away from ports that are old and haven't been updated for a while. Not trying to say that the rom I built is the best or anything but so far I haven't ran into any issues and neither has anyone that's used SpiritRom. I say try Spirit Rom 1.5 combined with iyahman's semaphore kernel that was built using linaro 4.9 as it's been stable. If you still run into these issues again I think it may be some software that you use.
The phone only had one major issue before I started messing with it - back & home buttons not working. I honestly can't remember how and what I did to put CyanAOSP on it but I ended up with 2 issues after putting it on. Only the Menu button works (eventhough all 4 lights up) and the USB seems to be grounded. I managed to work with it the past year up until I Odin-ed it back to JFD. When the phone is off and battery still has charge, the loading button would come up followed by the empty batt image at the background. This will loop until the batt dies. The only way to turn it on is by connecting the USB to a power source. Accessing download is easier because all I needed to do is remove batt then press and hold the vol up & down before putting the batt back in. Getting into recovery is a bit trickier. You'll need to wait until you actually see the phone charging before doing the 3-button combo.
Last Saturday, my daughter had a school event and I brought this along because it took better pictures than my S3 knock-off. During the parade, after shooting a video, it would automatically take me to the preview. Since, both back and home buttons were not working, I was stuck. Only option was to reboot it. What makes it interesting is that there is no reboot option on the JFD. It was a good thing that I had my power bank with me. I really did not want to constantly reboot it so I thought of installing one of those virtual button apps. I managed to install ToucherPRO before their presentation which made it much easier. To my surprise, it somehow revived the back button on the device itself - I noticed it when I got home that night to transfer the photos and vids.
I mentioned this so that you guys will have an idea on what I need to go through to get it fixed - somewhat, at least to a more tolerable state. (you won't believe it but the tips of my fingers hurt due to the number of times I have to go into recovery or download)
@Woody
Woody said:
I would make sure that you realize that this phone is older and may not be up to the challenge of some of the newer games out there. Based on your PM to me, I understand that this is a secondary phone for you, so if you wanted to play some of the more graphic intensive games, I would do it on your DD.
Click to expand...
Click to collapse
Yup. I actually find it both weird and interesting - which games work and how they work.
Woody said:
You should stay as far away from Kies as possible with this specific phone. It had a tendenacy to brick the Vibrants. It worked on my wife's SGS2 back when, but even then I was hesitant to use Kies on it and grinding my teath the whole time.
Click to expand...
Click to collapse
Remember I mentioned my hesitation using Heimdall and Bay_wolf's AIO toolkit regarding hijacking drivers and stuff, Kies on this PC is now useless. It won't even recognize the phone after I tried the toolkit - which is good, I guess.
Woody said:
... Take a look at this thread starting with my post #3 and the response from @nirogu325. I am thinking that if you do the same as he instructed, you will boot past the Status 0 error (since everything that I have seen in searches leads me to believe it is an Updater Script issue). ...
Click to expand...
Click to collapse
I read about this when I started going back through the threads. As you mentioned, this is an old phone. Old phone = old threads. What I do is I read everything on page 1 then skip over to the last page, going back. Seems to be more effective specially for DL links.
I was actually reserving this one as part of my 'last option' fix. From experience, editing scripts is far more dangerous than flashing a 'working' one. I managed to root my other DD this way, but went downhill from there - ended up bricking it 3 times.
Anyway, I think I got it - or at least, the correct way of doing it. It took me 3 days....
After day 1, I ended up with 8 update.zips (7 CWM and one ROOT) and at least 2 copies of ROMS, GAPPS, MODEMS, and KERNELS on my SD card - only the update.zips worked, the rest either gave me status 0 or leave me with the 'Vibrant Samsung' bootloop. I had some progress on DAY 2. I read something like what epicboy said:
epicboy said:
As Woody already said, you should odin back to stock 2.1. From there root and go to Jellybean and then KitKat. I'd recommend you stay away from ports that are old and haven't been updated for a while. Not trying to say that the rom I built is the best or anything but so far I haven't ran into any issues and neither has anyone that's used SpiritRom. I say try Spirit Rom 1.5 combined with iyahman's semaphore kernel that was built using linaro 4.9 as it's been stable. If you still run into these issues again I think it may be some software that you use.
Click to expand...
Click to collapse
I tried several JB ROMS listed on the Bible but, the problem was, I can't get into recovery - it was all 'blurry'. When I tried a different JB ROM, it also worked but was still 'blurry' during start up and on recovery. That's when I remembered Woody's post regarding rainbows and bootloaders.
DAY 3: For some reason, everything was flawless. I was able to install JB then KK. EFFORTLESSLY, if I may add.
@epicboy
I'm planning to spend a couple of days more on this Vibrant before I mess with my other phone - a knock-off SGS3. I was drawn to L-Droid because the screenshots and contents of page 1 of their thread was specifically for the T959 and not the I9000. I know it's not really a big deal because the ROM will work and changing the build.prop for 'cosmetic purposes is easy. What really concerns me is the camera. Sadly, the T959 only has only one camera and if the camera app that you're using (stock or otherwise) has a feature to switch from back-to-front and you accidentally press that, it messes it up to the point that you can't use it anymore. I have downloaded the ROM and will try it out in a couple of days. Will send you a PM or reply on the thread regarding my feedback. I've flashed it several times but really haven't been able to do it flawlessly like in DAY 3 - which I find really weird.
Tnx peeps!
I want to perma-unlock the sim so i wont have to use sprint because they suck eggs. But using a program called autorec, i am stuck in fastboot. I have tried the download thing where you power off and plug in the usb to get download mode, but as soon as it powers on it goes directly to fastboot or download mode pops up, then is sent directly to---YOU guessed it! FASTBOOOOOOOOT
So i need to go back to square one, and start from the very stock LG G2 Ls980, help will be appreciated. I will post links of guides i tried but led me to this problem. Also, anyone who would like to post a good guide, no problem, to unlocking the phone to be used on another rom such as AT&T or Tmobile, that would be fantastic. I want to get this phone up and working to replace an old phone, but sprint is a egg sucker.
http://forum.xda-developers.com/showthread.php?t=2729370
http://forum.xda-developers.com/showthread.php?t=2655133
http://forum.xda-developers.com/showthread.php?t=2715496
http://www.droidviews.com/install-twrp-recovery-on-lg-g2-running-android-4-4-2-kitkat/
BTW it is rooted already with ioroot. like i followed in the guide.
more information
Those all say
"fastboot mode started"
udc_start
reset
then just
portchange(where i was trying the download thing)
but it all ends in fastboot: processing commands
I have seen alot of other guides
I still need help, specific instructions for my device would be great. all the info in the first post.
For the speedy reply
I really ****ed it up now due to every flash to stock from fastboot menu on this site. It is black screen cant even access anything, no stock rom ANYWHERE ON THE INTERNET WTF and i am beyond irritated with how many inaccurate threads on this site. The phone altogether is really pissing me off. **** sprint for making their phones just as ****ty as every service they have.
ShawnBrazil said:
I really ****ed it up now due to every flash to stock from fastboot menu on this site. It is black screen cant even access anything, no stock rom ANYWHERE ON THE INTERNET WTF and i am beyond irritated with how many inaccurate threads on this site. The phone altogether is really pissing me off. **** sprint for making their phones just as ****ty as every service they have.
Click to expand...
Click to collapse
I work on that phone all the time and never remember seeing any threads for restoring via fastboot...? The preferred way is via kdz and the LG FlashTool. So once you power off and leave it off for like 30 secs then hold Volume Up and plug in the phone does not get you to Download Mode? Have not seen that one before...
As far as unlocking, especially if you aren't going to use Sprint again, I prefer to use one of the roms that is based off GSM with the Sprint kernel so it'll boot. I like the Energy rom for 4.2.2. Works and looks great. Have installed it for quite a few customers and have never had a complaint (well, one wasn't a fan of the dark theme, but can't please em all...) or anyone bring it back to me. There is a newer one that is like a stock rom but 4.4.2. Haven't tried that one since I like to stick with what I know works and haven't had enough chance to test the new one.
The steps I take are:
Use LG FlashTool to go back to ZV7 update
Root with ioroot (at leave version 22 and 25 works too)
Use Flashify to install the loki-ed TWRP 2.6.3.3
Reboot to recovery
Install Energy rom and ZV8 radio (must flash radio or it will not boot)
...
Profit!
PS: If you need NFC, there's a separate zip to flash.
I have everything for this operation uploaded to my Mega account and have performed it remotely. If you're just completely stuck and you can still get into Download mode, let me know and I can help with whatever else you need.
I picked up this device from walmart for $29.99 with the intentions of learning some new development stuff.I
thought for 30 bucks there's gonna be a lot of these little "duallies" running around why not a cheap candidate?
So far as i can tell there is little info found about this device so I'm looking to collect what little is known about
it in one place in hopes to get a jump on it. First things first, I am responsible for my own actions as you are yours.
If your not sure ask or simply dont do, some of this stuff can brick your device!
*ROOT*
These are the instructions I followed to root.
http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/
dont forget to install supersu
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
and busybox afterwards!
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
*RECOVERY*
Downloaded "TWRP Manager" from play store.
twrp settings, I enabled the sd card patch.
Install twrp\device name :l34c\version i instaled: openrecovery-twrp-2.8.4.0-l34c.img
click install... wait... things will pop up..... things will go away... wait some more...
finally a dialogue that states sucess.
***ISSUES HAVE BEEN REPORTED OF LOSING RECOVERY OR THE ABILITY TO ENTER IT AFTER
A WIPE AS WELL AS PROBLEMS BACKING UP AND OR RESTORING.
I have "injected" twrp manager into the system using titanium backup (link2sd will work also). This seems to
prevent any issues I have read about previously mentioned. Also I have successfully preformed backups as
well as restores, both before and after wiping. I have not figured out how to enter twrp recovery upon boot
yet, so be careful of what you do!
*SAFE TO REMOVE APPS*
yet to come
I use "titanium backup" from the play store, still trimming.I can get it down to about 230MB
available "free" ram at the moment but not consistently.
Ok had an issue with a task manager improperly reporting free available ram... true availability was
around 150mb free. There are apps that have to be replaced when removed, for example a launcher
for a launcher but some do not. Again I'm still trimming and experimenting, right now my system rom
around 244mb free. Most every thing I have done has been on the phone its self without the need of a P.C.
*STOCK BACK UP*
Yet to come
Any candidates for a true stock rom? Ive hacked the crap out of this one so far without the need of a back up... i know tisk tisk tisk!
I'm going for a debloated deodexed stock rom, hopefully!
*DRIVERS*
The only ones I could find that actually work. The Verizon drivers mentioned for the g2, not surprising since it runs on vz towers!
http://forum.xda-developers.com/showthread.php?t=2432476
*TETHERING*
using the android wifi tether 3.3beta2
https://code.google.com/p/android-wifi-tether/
all settings untouched except
device profile
lg optimus 3d
device access does work as well as encryption
*XPOSED*
Does work, im using 2.6.1.
*DPI*
The app I'm using for safe keeping to test dpi settings
https://play.google.com/store/apps/details?id=com.oumugai.densityadjuster
200 not working
170 works
160 native
150 works
140 works
130 works
120 works (looks good)
110 works
Temporarily went back to native dpi for debloating purposes. Will revisit later.
After messing with DPI settings I'm having a"contacts has stopped working " when tapping on the phone app.
DPI set to 120 when I noticed. All dpi switches affect lg home launcher
so you will need another launcher.
ok so far thats what i got. whats the nexts step to a stock AOSP rom?
questions and/or constructive comments wecome
reserved
I've got a few of these that are bootlooping. They show the LG logo, and then TracPhone Wireless splash screen infinitely in a loop.
Two questions.
1 - Is there any way to recover them? I'm hoping for some sort of a dev tool that I could flash a stock image or something (like Odin is for Samsung phones)
2- When these phones started bootlooping, I installed TWRP on the other Fuels that I have, thinking that I didn't want it to happen to them. My understanding of the TWRP that's installed from TWRP manager doesn't flash a modified boot image, so you can't enter TWRP from a powered off (or in my case, bootlooping) phone. Is that correct? I flashed a custom boot image from elsewhere that allows me to tap vol up at the LG logo to boot to TWRP. Any idea if this is enough of a safeguard to in the even of similar boot loops?
Any chance you know how to get it in diag mode? I need to connect it to DFS but can't without diag. Thanks for your help!
DrPhant0m said:
I've got a few of these that are bootlooping. They show the LG logo, and then TracPhone Wireless splash screen infinitely in a loop.
Two questions.
1 - Is there any way to recover them? I'm hoping for some sort of a dev tool that I could flash a stock image or something (like Odin is for Samsung phones)
2- When these phones started bootlooping, I installed TWRP on the other Fuels that I have, thinking that I didn't want it to happen to them. My understanding of the TWRP that's installed from TWRP manager doesn't flash a modified boot image, so you can't enter TWRP from a powered off (or in my case, bootlooping) phone. Is that correct? I flashed a custom boot image from elsewhere that allows me to tap vol up at the LG logo to boot to TWRP. Any idea if this is enough of a safeguard to in the even of similar boot loops?
Click to expand...
Click to collapse
My apologies for the delayed response. I have a lot going on in life.
As for recovering them, use the device you have closest to stock to make a backup. Do this before you attach your account or put any thing in to it after a "fresh wipe". To the best of my knowledge there isnt a tool like odin available, i could be wrong though. You can push a back up to the looping devices via adb. in order to do this you must have previously enabled usb debugging. The instructions are available on the web, i my self dont know how to do this. If you can establish an adb connection im sure you can command it to boot into twrp. For setup and testing use one of the devices that doesnt have a problem to establish adb. There is a little info on another thread i created about investigating the boot process the link is in my signature for the defy. Please be patient with me as i have two jobs and a single father, im not a hacker or developer. just a normal guy that is fascinated by my little robot willing to learn any thing. now that I know this thread is becoming active Ill monitor a little closer. Also if there is any thing i can help with ill be glad to do so. Im wanting to get a second fuel just for dev and learning purposes.
Recovery
Is there a way to access recovery on the lg fuel? I am stuck in a boot loop because I disabled the home screen service as well as other things that I did not pay attention to. I do not have a custom recovery installed.
I've never been able to boot to recovery by way of button press. Seems like there's a way to get into boot loader mode though. Just can't remember off the top of my head, I'm at work now and don't have the fuel with me. I'll see what I can figure out in a few hours when I get home. In the mean time you can try button combos upon boot to include the home button. If we can get ADB talking to it there's a chance I can send you copies of the files needed. Give me more details of what you have done just before the boot looping.
Sent from my ALCATEL A564C using XDA Free mobile app
I bought the optimus fuel a few months ago and i've been using it primarily for a music player/run keeping devices during my jogs. I turned off mobile data and i've noticed that i still see signal bars on the top notification area - does this mean that the radios are still on?
I was wondering if there was some way to completely disable the cellular radios so that i could conserve battery life inbetween days where I don't run?
Thanks!
This is a pretty cool app....
https://play.google.com/store/apps/details?id=com.latedroid.juicedefender
Airplane mode and then turn WiFi back on does the trick. "Radios off" = ton more juice
Has anyone found out anything else for this little phone? I have the LG Optimus Fuel. Had it for a few months now. I rooted it as soon as I got it and uninstalled a few system apps like the LG keyboard, the default SMS app and Chrome along with 2 or 3 other Google apps. It's still running fine.
I installed TWRP recovery and a custom boot image so I could boot into recovery by pressing the up volume button. Works great. I made a full system backup and saved it to my external SD card and saved it to my Debian laptop.
Right now I'm just looking for a custom ROM for this little phone but can't find one. I'd love to get Cyanogenmod on this phone but there are none. I'd port it myself but I'm not able to at the moment.
reemobeens19 said:
...
*ROOT*
These are the instructions I followed to root.
http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/
...
Click to expand...
Click to collapse
I'll expand on the above link because no one can view all of the info in that thread w/o registering for that site [PITA].
Load towelroot (www.towelroot.com). Upon running towelroot, press "welcome to towelroot v3" 3-times (quickly). Change 1337 0 1 0 4 0 to 1337 0 0 0 4 0 (change only the ONE to a ZERO), click "make it ra1n" and you're rooted. :good:
This was verified on an L34C running Android 4.4, Kernel 3.4.0+, build KRT16S.L34CV10c, Sw ver L34CV10c.
YMMV; IANAL
My apologies for the inconvenience, I was unaware for the need to register.
What I would like to do with the L34C is find a ROM with all the phone functionality removed, and few to no Google Apps (let me just add the ones I need). I am not planning on using it as a phone (I still have my old Casio flip-phone, need nothing else). My intention was to experiment with creating a PalmPDA "replacement", something small to carry around for addresses, notes/memos, calendar (you know, the stuff you used to do on PalmOS), and in addition figure out how to do record-level synchronization **locally** (as in I don't need to send my data to some dirt-floor shack in Bangalore just to have it sent back to a device 2 feet away from my computer). Additionally, would line to use it as a basic portable media player. Essentially, trying to re-create the Palm LifeDrive on Android.
To my knowledge there are no roms available for this device. Your best bet in my opinion is to remove apps 1 by 1 after rooting. Google each and find out what the risk and severity of removing them are. I have donated my device to a less fortunate fellow employee. So as of now I'm unable to help with testing. This method is what I do for all of my devices until I'm finally happy with its performance and functionality. Think of Android as the swiss army knife of the computer world, you can do just about any thing with it, you just gotta figure out what tools are useful to you and the ones you can do with out, then you gotta ask Google witch ones Android can function with out. I hope you find what your looking for in the little robot, its a really neat world inside there!
I hate to bump an old thread but, I also don't it necessary to start a new one, at least not yet anyway but, I too am looking for a way to flash stock ROM. I have LG34Cs to use as a reference..
Where is the link to exposed framework at for this phone?
All official twrp 3 images are broken on official site. Last good working was 2.8.7.0.
Here is working twrp 3.1.1 if anyone interested:
Code:
mega.nz/#!I0lhAYAY!fRbQtQjYFI2kiJOD0FSEBPnBJm0JZxpiBaw52kyOfQE
majexuj said:
All official twrp 3 images are broken on official site. Last good working was 2.8.7.0.]
Click to expand...
Click to collapse
What does broken mean in detail? Do I risk to brick my L34C when I flash official twrp 3 images?
Mac23 said:
What does broken mean in detail? Do I risk to brick my L34C when I flash official twrp 3 images?
Click to expand...
Click to collapse
Broken as in doesn't boot into recovery. The phone will still boot into android, assuming you have a working system, and within android with root you can flash a working recovery image over a broken flash with the dd command on the twrp device info page (twrp.me/lg/lgoptimusfuel.html). So no real risk of brick, just possible inconvenience that might require a battery pull.
I built twrp 3.2.1 with same sources but I have not tested it since my battery seems to have completely died and the phone won't boot with usb power alone.
Here is link anyway in case anyone is interested:
Code:
mega.nz/#!ssExSY7S!_B3FcAmclzRwCKTX461Tl_QhpdwwK0tmvhL-6zkKLRw
---