I have a BLU Quattro 4.5 android device and when I try to connect via USB Debug mode and run ADB Device it will not find my phone. I have searched high and low in order to locate the driver with no luck. The generic USB driver from google won't even work. I have even run emulator from the phone and when I type: pm set-install-location 2, it comes back with Killed and then back to command prompt. When I type: pm get-install-location it comes back as 0[auto]. My phones main memory is 1 gb and 1.5 internal usb memory. With all of the main system apps updated on the main drive, the phone cannot handle ANY other apps, even when I put apps on the usb memory it is very sluggish. I need help in trying to install and run all of the apps from the external sd card and just have the system apps running on the main disk. I would also like any help in finding the driver needed to access the phone in ADB.
BLU Quattro 4.5"
4 GB Internal Memory( Broken up to 1 GB Main, 1.5 GB USB Storage, and not sure where the other .5 GB went.)
1 GB Ram
NVIDIA Tegra 1.5 GHZ Quad Core
16 GB Class 10 Micro SD Card
Android 4.0.4 ICS
Unlocked Running Straight Talk/T-Mobile Sim
GOT IT!!!!!!!!!!!!!!!!!!
plymouthrock99 said:
I have a BLU Quattro 4.5 android device and when I try to connect via USB Debug mode and run ADB Device it will not find my phone. I have searched high and low in order to locate the driver with no luck. The generic USB driver from google won't even work. I have even run emulator from the phone and when I type: pm set-install-location 2, it comes back with Killed and then back to command prompt. When I type: pm get-install-location it comes back as 0[auto]. My phones main memory is 1 gb and 1.5 internal usb memory. With all of the main system apps updated on the main drive, the phone cannot handle ANY other apps, even when I put apps on the usb memory it is very sluggish. I need help in trying to install and run all of the apps from the external sd card and just have the system apps running on the main disk. I would also like any help in finding the driver needed to access the phone in ADB.
BLU Quattro 4.5"
4 GB Internal Memory( Broken up to 1 GB Main, 1.5 GB USB Storage, and not sure where the other .5 GB went.)
1 GB Ram
NVIDIA Tegra 1.5 GHZ Quad Core
16 GB Class 10 Micro SD Card
Android 4.0.4 ICS
Unlocked Running Straight Talk/T-Mobile Sim
Click to expand...
Click to collapse
found generic driver from PDANET that finally allowed me to access my phone from ADB and I was able to make the necessary changes. Yippeee! pdanet.co
plymouthrock99 said:
found generic driver from PDANET that finally allowed me to access my phone from ADB and I was able to make the necessary changes. Yippeee!
Click to expand...
Click to collapse
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
londonflu said:
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
Click to expand...
Click to collapse
I have one as well and was able to root it with the latest bin4ry tool! Hopefully Blu will enhance their customer support as they gain more popularity and release some source code or dev tools for the phone. Or at least, since it's rooted, the device can eventually gain support from any devs.
Kah,
Can you post root instructions for us, please?
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Any Information posted in this thread is Great!
I don't mind taking this off track of what the original thread. I like it that it is progressing the way it is, helps me out with other questions and anyone else that starts off with my problem probably wants additional information on what else could be done with these phones.
kah1593 said:
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Click to expand...
Click to collapse
Average
I am still having issues with ram and touchscreen when main storage location gets full. It becomes very unresponsive and the touchscreen becomes very sluggish. Some things I cannot move to the external sd card and all the installed apps still get installed on primary drive even after changing default install location. I need to figure out how to install and run everything, including the android os.
londonflu said:
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
Click to expand...
Click to collapse
plymouthrock99 said:
I am still having issues with ram and touchscreen when main storage location gets full. It becomes very unresponsive and the touchscreen becomes very sluggish. Some things I cannot move to the external sd card and all the installed apps still get installed on primary drive even after changing default install location. I need to figure out how to install and run everything, including the android os.
Click to expand...
Click to collapse
Try using Mounts2SD..
I doubt I'll get much help on this, but I'll give it a shot. I just got my Quattro 4.5 today, and tried to root it with Bin4ry. It never did the first reboot, it just turned the phone off. After a few minutes I turned it back on still connected to USB, Bin4ry tried to finish, but gave a permission denied error on the superuser apk. Now my phone is in continuous boot loop, it gets to the lock screen, but says Go Laucher and system UI has stopped, then reboots. Is this thing bricked? Holding volume down and power just goes to a modem download screen, but no USB connection or anything. :crying:
j21blackjack said:
I doubt I'll get much help on this, but I'll give it a shot. I just got my Quattro 4.5 today, and tried to root it with Bin4ry. It never did the first reboot, it just turned the phone off. After a few minutes I turned it back on still connected to USB, Bin4ry tried to finish, but gave a permission denied error on the superuser apk. Now my phone is in continuous boot loop, it gets to the lock screen, but says Go Laucher and system UI has stopped, then reboots. Is this thing bricked? Holding volume down and power just goes to a modem download screen, but no USB connection or anything. :crying:
Click to expand...
Click to collapse
I'm sorry to hear than man. Which version of Bin4ry did you use? You could try quickly using adb to boot into recovery mode while the phone is still in the process of booting. You'd have to keep sending
Code:
adb reboot recovery
until adb recognizes the device. Hopefully, it'll restart into recovery before it crashes. Not sure if it'll work, but it's an idea.
kah1593 said:
I'm sorry to hear than man. Which version of Bin4ry did you use? You could try quickly using adb to boot into recovery mode while the phone is still in the process of booting. You'd have to keep sending
Code:
adb reboot recovery
until adb recognizes the device. Hopefully, it'll restart into recovery before it crashes. Not sure if it'll work, but it's an idea.
Click to expand...
Click to collapse
Everything is fixed! I figured out how to get into recovery. I was able to do a factory reset from there and everything came back, actually maybe better. Then I found an old version of Bin4ry, v15, and tried again. This time it worked perfectly. This phone is pretty awesome, I just wish there was developer support for it.
j21blackjack said:
Everything is fixed! I figured out how to get into recovery. I was able to do a factory reset from there and everything came back, actually maybe better. Then I found an old version of Bin4ry, v15, and tried again. This time it worked perfectly. This phone is pretty awesome, I just wish there was developer support for it.
Click to expand...
Click to collapse
Great! How'd you manage to get into recovery mode despite the boot loop? In case anyone else runs into the same issue.
kah1593 said:
Great! How'd you manage to get into recovery mode despite the boot loop? In case anyone else runs into the same issue.
Click to expand...
Click to collapse
Hold volume up and power until it turns on. As soon as the screen changes to green, I let go of the power button and keep holding the volume up button until it's in recovery mode. It seems the power button release has to be timed right or else it just sits on the green screen, or powers off again. It takes a couple of tries for me. I probably did 10 factory resets last night before finally getting it rooted, lol. The built in recovery has an option to flash from external storage, kind of makes me wonder how easy this phone would be to get CWM working. Of course, the real problem is getting developers to write the custom ROMs for it. The only thing this $230 phone is missing from its $600 cousins is 4G LTE, but on Tmobile it doesn't even matter right now. It's still blazing fast even on stock with no overclock, I can't imagine how much more awesome it would be with a custom rom.
kah1593 said:
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Click to expand...
Click to collapse
Can anyone post a link of where I'll find the proper drivers? It just shows BLU with an exclamation in my Device Manager. The PDANET trick did not work as it won't detect the device. - and if I can get this working, I'll post an actual tutorial for it.
If anyone could post an update.zip of the original rom that would be fantastic. - and clockwork 6 will run on our devices with some work. but right now, mine is a brick, it still has recovery but the stock rom is effed.
I'm in the same situation. I deleted my contacts.apk in hopes of replacing it with a stock version, now it's stuck in a boot loop, and factory reset doesn't help.
Alright guys, I hit the jackpot. I have CM 10.1 working on my Quattro 4.5. It all began when I read somewhere on the xda forums that the Quattro 4.5 and k-touch v9 are essential the same phone. I said before, my phone was bricked so I figured I do some more research and see what I could do. Turns out that person as right. I found a website ( http://www.needrom.com/phone-roms/k-touch/k-touch-v9/ ) that has 3 roms for the v9, CM 10.1, MIUI 3.4.5, and CM 10, and instructions to install them. I decided to take a leap of faith and follow the directions given for CM 10.1. The installation directions for custom recovery CWM 6.0.1.1 worked perfectly - only problem is after you've installed the recovery, the menus are in Chinese.
Once again, My phone was bricked and essentially completely erased. If your phone isn't bricked, it should be fine as long as you do a factory reset before. I would suggest doing this before installing the CWM recovery because I have no clue how to do the reset using the Chinese menu.
I downloaded the CM 10.1 rom from the website above and gapps for 4.2.2 as well (you can find this with google). If you're using one of the other roms, obviously make sure you're using the proper gapps version.
ADB works while in recovery so use this to push the zips to the phone. I say this because I've discovered the sd card directory changes depending if your phone is bricked or not (i.e. /emmc vs /sdcard).
Flash the rom zip, then gapps - select the 2nd option in the main menu then in the following menu, the 4th option. This should lead you to the directory containing your zip files. Choose the appropriate one, and let the CWM work its magic. ( also from messing around I can also tell you the first option in the main menu is to reboot)
Once you've reboot, everything should work perfectly - WIFI, bluetooth, brightness, camera, video recording, audio, microphone, not a single problem except the volume being much louder than before. It's amazing. I have straighttalk's $30 plan, so I'm still stuck with a dumbphone until I bump up to the unlimited everything at the end of the cycle, so I can't test the phone radio, but I would expect it to work considering everything else does as well. Let me know if I left something out. I would test the other roms, but I'm so happy and content with my phone working again, I don't want to go through the effort just yet.
I found a way to create an English recovery that works from the Chinese version. Just replace the recovery.img provided with this one. Here's the link: https://www.dropbox.com/s/5y6r9gvspvouhbo/recovery.img I don't think this should cause any issues because it hasn't for me, but remember you are using this at your own risk. Though if an issue does arise, I'll try my best to help.
Install with English Recovery?
Did you install with the English recovery, because I am stuck at CM10.1 boot screen installing with the English recovery.
Related
I installed CM7 Alpha Final (SD card version) and was working on getting the interface back to how I had it on the previous version. I used CWM to install "transparent status bar icons.zip" from this thread...
http://forum.xda-developers.com/showthread.php?t=1471066
Upon installation I went to reboot and now I'm stuck on the CyanogenMod7 boot screen and looping endlessly.
If anyone has any idea how I can fix this, I'd really appreciate some help.
Thanks!
Retcon:
I just remembered that I did NOT have this installed on the previous version on CM7. On CM7 i had a standard theme dock, so I think I installed something that just wasn't compatible with CM7 at all. What do I do now?
Thanks.
Most likely that transparent icons xip was not built for cm7 and rather was built for stock firmware. They are not compatible. Reinstall cm7.
What method can I use to reinstall? Since I'm in a bootloop I can't get to CWM. Or is there some kind of "safe mode" I can boot into?
Sent from my T-Mobile G2 using xda premium
Turn the unit on, when you get to the n screen, hold the power button until it turns off. Repeat 8 times and you will be forced into CWM.
If you have adb installed on your pc, plug it in, turn it on and check devices. If you are listed, do an adb shell reboot recovery and that will put you into recovery instantly.
I tried the 8-boot method two different ways...
1. Pressed the power button and released. When I saw the N screen, I pressed again and held until the unit powered down.
2. Pressed and HELD the button through it powering on and not releasing until it shut back down again.
Does it matter which of the above ways I do it? I wasn't able to get it to work. Does it have to be exactly 8 times? I don't think I stopped short but I might've done it more than 8...
Regarding the ADB method, I went ahead and installed the SDK but I'm not seeing my devices in ADB DEVICES. Since this is a new computer, I think I just don't have the right drivers installed. I went to Indirect's root thread to get those drivers but his dropbox link is disabled due to high traffic. Is there somewhere else I could get the appropriate driver? And once I have the correct driver and can see my device in ADB DEVICES (I'm assuming I'll be able to see it even though I'm bootlooping the whole time?), what is the code/line to get it into recovery?
Thanks for your help thus far. I really appreciate someone taking the time the time to help me out.
Oh, and a correction to my original post - I used the internal root method, not SD.
I found a working link for the drivers.
http://www.mediafire.com/?w6y5ld1jeuh65i1
I installed them and I can access my tablet now. I can see my device and its responding to commands.
So all I need now is the command to get into CWM. I tried "adb reboot [bootloader:recovery]" which I saw in the cmd window, but it just gave me a standard reboot.
Thanks!
EDIT: I tried "adb reboot recovery" and that did it. I'm back in business! Thanks for the help, Know-Fear. Although in my n00bishness, step-by-step handholding would've been nice, your replies gave me enough for me to at least know what general direction to look in. I still couldn't get the 8-boot method to work, but maybe that's just a dexterity issue. The adb method worked perfectly once I stumbled my way to the command line.
Make sure when you reinstall you do a partition wipe.
Glad you got it working thus far. Hopefully no more problems will arise after the new install.
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
---
Pls help me root my zte obsidian running android 5.1 Model NO. Z820
I need help too
I also have ZTE obsidian tmobile and really want to root it i cant do much because it only comes with 4gb of space and i cant move apps to the SD card till i root Please help find a root
yeah same issue here all say that it cant after like 10-15 mins its just like nope sry
have you used this
http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Yes, I tried. Its not working.
Is there any other way. I am desperate. It doesnt allow to move the Apps to SD card. There is no way. Locked in 4GB
I have a z820 in need of root as well. I've tried everything, including the link up there, and so far.....nope. Nothing. No apps to SD for me either.
Zte can't root for ****!!!!
I'm so mad because I really tried everything even a computer won't let me tried everything there to like why would the make a zte that can't even move your games or pictures or music to your SD card knowing danm well everybody gone need like we only got 4g that's nothing so what are we so posted to do delete stuff that we like.to trade for the other that we really don't need **** I'm pissed right now I know y'all are to but if anybody finds something please send me the info or con me by [email protected] thank you:good:
Needs update
This Phone really needs an update, it reboots and sucks, we can't even get into fastboot or anything to try to unlock the bootloader someone needs to make this possible because who in the hell uses only 4gb of storage, apps are so big and you can only download like 3 apps then you have to get rid of something if you want another app and its dumb so please someone..HELP US :crying:
Throwing my post up here so I can follow. Need root bad on this thing. I am using lite versions of every app. Lol
Same problem w/ ZTE obsidian..tCan't move to SD card. Anybody figure somethcing out yet?
I've gotten Kingroot to attempt to root it once and the results varied. Usually got 16% but the highest was almost 30% but I can't even get kingroot to even root it anymore.
The phone is not going into fastboot at all. I think the bootloader is locked. The phone will never be rooted.
I might of found a way, but it's untested so, proceed at your own risk, I am not responsible if your phone becomes bricked.
Enable developer mode and tick "OEM Unlocking" in the developer menu
Download SuperSU update zip from Chainfire's site and put it on your sdcard (internal won't work)
Power off your phone and hold power and volume up
Select recovery, wait for the android with the lid open to show up
Hold power and volume up for a couple seconds and let go
A menu should pop up, if not try again until it does
Select "update from sdcard"
Select the SuperSU zip
Let it flash the zip (shouldn't take long)
Choose reboot
See if SuperSU is installed and test that it works
Again, this is untested and would need a couple of people testing it to make sure it works flawlessly, so if this worked, please post that it did.
Nope. Thank you though.
picsles said:
Nope. Thank you though.
Click to expand...
Click to collapse
Any type of error happen or did it not allow it to flash at all?
I can't even get to recovery. Gives me the choice then goes to dead android guy.
Sent from my LGL21G using Tapatalk
Musicmanmike said:
I can't even get to recovery. Gives me the choice then goes to dead android guy.
Sent from my LGL21G using Tapatalk
Click to expand...
Click to collapse
You have to hold down power and vol up for like 2 seconds when you get to the dead android, then you'll get the recovery menu.
When I try to install the update package, I get 'opening update package' followed after less than a second by 'installation aborted'.
I powered down from the Developer Options screen with OEM unlock turned on when trying to update - it appears to turn off during boot as it is off again on restart.
Any suggestions? I looked at the logs that are visible from the recovery screen but they did not seem to have anything useful. Are there logs I can retrieve via ADB to see what the issue is?
My phone has build B18.
Kurrelgyre said:
When I try to install the update package, I get 'opening update package' followed after less than a second by 'installation aborted'.
I powered down from the Developer Options screen with OEM unlock turned on when trying to update - it appears to turn off during boot as it is off again on restart.
Any suggestions? I looked at the logs that are visible from the recovery screen but they did not seem to have anything useful. Are there logs I can retrieve via ADB to see what the issue is?
My phone has build B18.
Click to expand...
Click to collapse
OEM Unlocking is always on for me even after restarts but I haven't tried to flash SuperSU yet. You might wanna get a logcat while doing it and post it here to see if anyone knows what the problem is. I have an older build of the phone (B03) but I dunno if it matters or not.
EDIT: Also every new Kingroot build allows you to attempt to root it for like 2 days and then it just can't for some reason but the thing with 18% still happens.
LUModder said:
You might wanna get a logcat while doing it and post it here to see if anyone knows what the problem is. I have an older build of the phone (B03) but I dunno if it matters or not.
Click to expand...
Click to collapse
The logcat I am familiar with is in ADB. The only way I can find to access the phone from recovery with ADB is to select the flash from ADB option, which puts the phone in sideload mode where you can't pull data off. I was unsure if trying to load the ZIP that way would brick the phone so I haven't tried it.
I also tried using Fastboot and it doesn't recognize the phone at any time.
Is there another way to capture what is happening with the update?
I tried selecting restart in bootloader from the recovery menu with the phone connected to the PC. It stayed at the ZTE splash screen for over 10 minutes but neither fastboot nor ADB was able to communicate with it. I tried various key combinations without effect and finally ended up pulling the battery. Maybe it just froze up during boot for some reason.
I have tried every one-touch root I can find, none of them work. All the manual guides start with unlocking the bootloader - which I can't find any info on for this model. Based on the partition info, it's definitely locked: it has 27 (!) partitions including names like seccfg and oemkeystore. Is this normal for a lollipop device?
As the topic reads, I've been trying most of the day to unlock the bootloader, I went through the process of obtaining my unlock code and my phone status when typing out a code suggested that it allows unlocking of the bootloader - I'm thinking okay cool, hopefully I'll have Cyanogenmod 12.1 on this thing in no time, right? WRONG! The device needs me to download and install fastboot drivers, which I thought should be an easy process but no matter what I do when I look at my phone through the device manager all I see is 'S1Boot Fastboot' - I even attempted using Flashtool (not Emma) and it too says install failed when trying to download the files needed. I just really need some help getting through this part of the problem, I've downloaded the SDK downloaded the USB drivers, updated them with the file from Sony but the end result remains the same. If it makes any difference (which I'm sure it will) I'm on Windows 10.
Thanks for any and all replies .. Edit // I forgot to mention the model is C833 and I recieved the latest OTA update from Sony for Lollipop 5.1.1
Installing the SDK is quite the overkill.
- Install ADB and Fastboot by downloading and running this tiny installer. It'll do the job for you.
- Install Flashtool and be sure that it recognizes your device. The device should be powered on when you open Flashtool the first time.
- Click the "BLU" button and copy/paste the unlock code you received from Sony.
You're done
Be sure to backup important stuff on your phone, in case something goes wrong. Move photos etc. to your SD card or something.
Klaos3000 said:
Installing the SDK is quite the overkill.
- Install ADB and Fastboot by downloading and running this tiny installer. It'll do the job for you.
- Install Flashtool and be sure that it recognizes your device. The device should be powered on when you open Flashtool the first time.
- Click the "BLU" button and copy/paste the unlock code you received from Sony.
You're done
Be sure to backup important stuff on your phone, in case something goes wrong. Move photos etc. to your SD card or something.
Click to expand...
Click to collapse
I appreciate the reply, and I managed to get the bootloader unlocked (I think) as both ADB and Fastboot are acknowledging my phone now. Problem I have now is while in Cyanogen Recovery, I hit the first option and may have soft bricked this phone - the cyanogen wiki stated I could make a backup by booting back into Android which is what I tried to do. I'm in the process now of repairing it with the PC companion hopefully and then I'll give it another go, this isn't my main phone though so basically I'm just tinkering/trying to learn the basics of installing custom ROMs. Thanks again for the reply, and if you have any other suggestions for me be sure to leave em here. BTW, I never installed the full Android Studio, just the zip file for the ADB and Fastboot files, I attempted that at first but found out you didn't really need em in the first place.
The CM Recovery is... pretty crappy, so don't use it if you don't have to. If you soft brick it (i.e end up in a bootloop or something), then just flash or hotboot a kernel with recovery, and you're good to go again, so you don't have to re-flash a ROM.
You can either use fastboot to flash a kernel (if you know how to use a terminal), or you can use Flashtool, QuickIMG etc, so:
Soft brick?
- Download a custom kernel with recovery. Doesn't matter which one if you're planning to flash a ROM straight away. You're planning to flash CM12.1, so you can use a random Ultra kernel like this one.
- Let's say we'll use Flashtool to flash it (since you already have it installed). Open it, hit the lightning bolt, click "fastboot", and then "kernel". Browse and choose the kernel you downloaded. Now disconnect from the computer and remember to press VOL up to enter recovery when it vibrates or the LED lights up.
- You're now in recovery again and you can go ahead and flash CM12.1. Remember to WIPE before or after you've flashed CM12.1. You'll end up with a bootloop if you don't do it. If you do, flash that kernel again and you're back on track.
Klaos3000 said:
The CM Recovery is... pretty crappy, so don't use it if you don't have to. If you soft brick it (i.e end up in a bootloop or something), then just flash or hotboot a kernel with recovery, and you're good to go again, so you don't have to re-flash a ROM.
You can either use fastboot to flash a kernel (if you know how to use a terminal), or you can use Flashtool, QuickIMG etc, so:
Soft brick?
- Download a custom kernel with recovery. Doesn't matter which one if you're planning to flash a ROM straight away. You're planning to flash CM12.1, so you can use a random Ultra kernel like this one.
- Let's say we'll use Flashtool to flash it (since you already have it installed). Open it, hit the lightning bolt, click "fastboot", and then "kernel". Browse and choose the kernel you downloaded. Now disconnect from the computer and remember to press VOL up to enter recovery when it vibrates or the LED lights up.
- You're now in recovery again and you can go ahead and flash CM12.1. Remember to WIPE before or after you've flashed CM12.1. You'll end up with a bootloop if you don't do it. If you do, flash that kernel again and you're back on track.
Click to expand...
Click to collapse
Gonna give all this a shot since the PC companion doesn't seem to be doing anything - I'll post my findings in a few if you're around. Thanks again man, I really appreciate your help.
Edit // Okay, nothing seems to be working now .. Flashtool says that my device has USB Debugging disabled, and whenever I power on the device you see the Sony logo, then a violet led and then the screen stays on and every once in a while it'll show a small battery indicator.
D2084 said:
Gonna give all this a shot since the PC companion doesn't seem to be doing anything - I'll post my findings in a few if you're around. Thanks again man, I really appreciate your help.
Edit // Okay, nothing seems to be working now .. Flashtool says that my device has USB Debugging disabled, and whenever I power on the device you see the Sony logo, then a violet led and then the screen stays on and every once in a while it'll show a small battery indicator.
Click to expand...
Click to collapse
Hmm, plug in the wall charger and charge it for a bit. I highly doubt that it's hardbricked since that's very very hard to achieve on a Sony device. Just kick it into fastboot by holding VOL UP while you plug it into your computer. The blue LED will light up. Then open Flashtool and flash the kernel, or download QuickIMG and flash the kernel (.img) with it. Be sure that it says "connected" before you do anything. Keep also in mind that you have to be in fastboot.
Klaos3000 said:
Hmm, plug in the wall charger and charge it for a bit. I highly doubt that it's hardbricked since that's very very hard to achieve on a Sony device. Just kick it into fastboot by holding VOL UP while you plug it into your computer. The blue LED will light up. Then open Flashtool and flash the kernel, or download QuickIMG and flash the kernel (.img) with it. Be sure that it says "connected" before you do anything. Keep also in mind that you have to be in fastboot.
Click to expand...
Click to collapse
I seem to have a brand new issue now, umm whenever I unplug the device and press VOL UP, I get this distorted screen. It's blue and has what looks to be white wording in the middle, I can't make it out though, this is after I put the kernel you recommended on my device. The kernel is the IMG file, correct?
Just thought I'd give you a bit of an update, I now have Cyanogenmod 12.1 on my Xperia Z Ultra - I flashed the custom recovery that came with the nightly I downloaded and then moved the actual zip to an SD card since like you said Cyanogen Recovery is a bit wonky (I tried sideloading to no avail). I have a couple question though, during the install process I noticed it said something about there 'no such volume' and I was sure I seen two failed prompts too but the ROM is on my phone? Should I look into that at all or is it fine? Most things seem to work .. camera, bluetooth, gonna have to throw my sim in there one of these days and test the cellular radios, but I just wanna say thanks again .. I learned a lot and managed to make something happen even if it's something small like installing a custom rom lol
D2084 said:
Just thought I'd give you a bit of an update, I now have Cyanogenmod 12.1 on my Xperia Z Ultra - I flashed the custom recovery that came with the nightly I downloaded and then moved the actual zip to an SD card since like you said Cyanogen Recovery is a bit wonky (I tried sideloading to no avail). I have a couple question though, during the install process I noticed it said something about there 'no such volume' and I was sure I seen two failed prompts too but the ROM is on my phone? Should I look into that at all or is it fine? Most things seem to work .. camera, bluetooth, gonna have to throw my sim in there one of these days and test the cellular radios, but I just wanna say thanks again .. I learned a lot and managed to make something happen even if it's something small like installing a custom rom lol
Click to expand...
Click to collapse
Just ignore that error. I've seen that myself a couple of times, and I don't know what it means, but it doesn't seem to affect anything.
There are a couple of things to keep in mind. CM12.1 has had some glitchy WiFi in the past, and I believe some people are still experiencing issues, so if you also experience some WiFi issues, it's a CM issue and not a hardware issue. Also, keep in mind that the Ultra GPe (Togari GPe) exists and is also supported by Cyanogen, so be sure to not flash the wrong version since the partitions are different between those two. I believe the recovery system will stop you from flashing it though.
Since Sony devices do not have a default recovery system, we have to bundle it with the kernel, so all custom ROMs around here, including CM, will have a recovery system added, but if you flash a ROM without a recovery system (like a stock ROM that you flash with Flashtool), you'll have to flash a kernel with a recovery yourself.
It's pretty easy to recover from issues and stuff on a Sony device once you know how things work. It's also a good idea to learn how to use flashboot through a terminal since that will potentially save you a lot of time down the road
Klaos3000 said:
Just ignore that error. I've seen that myself a couple of times, and I don't know what it means, but it doesn't seem to affect anything.
There are a couple of things to keep in mind. CM12.1 has had some glitchy WiFi in the past, and I believe some people are still experiencing issues, so if you also experience some WiFi issues, it's a CM issue and not a hardware issue. Also, keep in mind that the Ultra GPe (Togari GPe) exists and is also supported by Cyanogen, so be sure to not flash the wrong version since the partitions are different between those two. I believe the recovery system will stop you from flashing it though.
Since Sony devices do not have a default recovery system, we have to bundle it with the kernel, so all custom ROMs around here, including CM, will have a recovery system added, but if you flash a ROM without a recovery system (like a stock ROM that you flash with Flashtool), you'll have to flash a kernel with a recovery yourself.
It's pretty easy to recover from issues and stuff on a Sony device once you know how things work. It's also a good idea to learn how to use flashboot through a terminal since that will potentially save you a lot of time down the road
Click to expand...
Click to collapse
Everything seems to be working quite well so far, including the wifi but I'll keep what you said in mind. I used the same process to install GApps on it too so now I have the play store and google apps install as well. I have another question though, whenever I plug in a charger to charge the device .. I notice the screen never goes off but stays black and has nothing on display sorta like ambient display, would you know if that's a feature of Cyanogenmod or did I goof somewhere during the install? Thanks in advance for your reply.
D2084 said:
Everything seems to be working quite well so far, including the wifi but I'll keep what you said in mind. I used the same process to install GApps on it too so now I have the play store and google apps install as well. I have another question though, whenever I plug in a charger to charge the device .. I notice the screen never goes off but stays black and has nothing on display sorta like ambient display, would you know if that's a feature of Cyanogenmod or did I goof somewhere during the install? Thanks in advance for your reply.
Click to expand...
Click to collapse
Could it be Daydream? Go to Settings -> Display -> and disable Daydream. Now check again. If it's not Daydream causing it, then it might be a bug. Do a reboot in case it's a small glitch of some kind. If it's still on when charging, then I'm not sure what it could be (other than a bug, that is).
Sorry for the late reply, but I figured out the reboot issue .. I had to turn off the 'wake up' feature when you plug in your device. I have a whole new issue though, I'm not sure if it can be resolved though - I was on the phone with MetroPCS for about an hour trying to figure out why my phone wouldn't connect to their network. I know Cyanogenmod comes with APN's pre-installed but even after the representative tried helping me set up a new APN .. it was a no go, so I switched back to the current phone I'm using - Alcatel Idol 3 4.7 .. anyways, I'd like to hear your input on what the issue could be as I'd really like to go back to using this phone since the software aspect is far more flexible with a custom ROM like Cyanogenmod.
D2084 said:
Sorry for the late reply, but I figured out the reboot issue .. I had to turn off the 'wake up' feature when you plug in your device. I have a whole new issue though, I'm not sure if it can be resolved though - I was on the phone with MetroPCS for about an hour trying to figure out why my phone wouldn't connect to their network. I know Cyanogenmod comes with APN's pre-installed but even after the representative tried helping me set up a new APN .. it was a no go, so I switched back to the current phone I'm using - Alcatel Idol 3 4.7 .. anyways, I'd like to hear your input on what the issue could be as I'd really like to go back to using this phone since the software aspect is far more flexible with a custom ROM like Cyanogenmod.
Click to expand...
Click to collapse
Are you talking about connection to their network altogether, or just data? Do you have reception? Check that data is enabled in Settings -> Data usage.
I can guarantee that this is a software issue, BUT one last question. How old is your SIM card? There have been a few cases when people have been in the same situation as you, got a new SIM, and that fixed the issue. You could do that, or flash another ROM. CM12.1 is beta, so bugs have to be expected, and it's far from a solution if you plan to just flash something and use it for a longer period of time. If you want something very stable and stock, then highly recommend Scrubber's GPe 5.1 port, which is rock solid.
Well my sim card isn't too old, had it for about a year. Once she laced the sim card to the new phone I could make calls and texts but for some reason the Internet wasn't working - she had me go through all the steps to make sure things like data was enabled and airplane mode was off but it still resulted in not being able to establish a connection to the web. So I'm gonna try and flash the GPE rom you're talking about later on tonight once I get home from work and see what happens then - mind leaving me a link to the rom/recovery? Thanks in advance.
D2084 said:
Well my sim card isn't too old, had it for about a year. Once she laced the sim card to the new phone I could make calls and texts but for some reason the Internet wasn't working - she had me go through all the steps to make sure things like data was enabled and airplane mode was off but it still resulted in not being able to establish a connection to the web. So I'm gonna try and flash the GPE rom you're talking about later on tonight once I get home from work and see what happens then - mind leaving me a link to the rom/recovery? Thanks in advance.
Click to expand...
Click to collapse
Sure. Here it is. Remember to download 5.1, and not 5.0. Recovery is included in the ROM, so you don't have to flash anything else.
Quick update, I've flashed the ROM but so far it seems to be stuck in a bootloop, its been stuck on the swaying Google logo for about 10 minutes now. It might be because I sideloaded using a micro SD card because for some odd reason the 'flash the system' option on Flashboot wasn't working for me. So I turned the phone off and will give it another try tomorrow, if you have anymore tips for me I'll be glad to hear em.
D2084 said:
Quick update, I've flashed the ROM but so far it seems to be stuck in a bootloop, its been stuck on the swaying Google logo for about 10 minutes now. It might be because I sideloaded using a micro SD card because for some odd reason the 'flash the system' option on Flashboot wasn't working for me. So I turned the phone off and will give it another try tomorrow, if you have anymore tips for me I'll be glad to hear em.
Click to expand...
Click to collapse
How did you flash it? It must be flashed in recovery on the device and not using Flashtool. Flashtool is strictly for stock Sony ROMs or FTFs. Never use it for anything else besides flashing FTFs and kernels. So:
- Go into recovery
- Remember to wipe! If you don't, you'll get a bootloop
- Install from SD card
- It will probably throw an error at you, but don't touch anything. It's still flashing.
- Reboot
- Wait a couple of minutes.
Klaos3000 said:
How did you flash it? It must be flashed in recovery on the device and not using Flashtool. Flashtool is strictly for stock Sony ROMs or FTFs. Never use it for anything else besides flashing FTFs and kernels. So:
- Go into recovery
- Remember to wipe! If you don't, you'll get a bootloop
- Install from SD card
- It will probably throw an error at you, but don't touch anything. It's still flashing.
- Reboot
- Wait a couple of minutes.
Click to expand...
Click to collapse
Just did everything you just said, will update you tomorrow with results.
Well I did what you said and left the phone to charge overnight - it was in bootloop when I went to sleep and .. bootloop when I woke up (at least it's charged now lol) I'm gonna try again though. I see that CWM has a sideload option, so I'm gonna wipe everything and try to sideload it from the ADB through the command prompt and see what happens. Feel free to leave any other suggestions though.
Got a question though, when I sideload the zip file should I sideload everything within the zip file or just the system image file? Maybe I'm getting bootloop because I'm installing a kernel on top of another kernel?
D2084 said:
Well I did what you said and left the phone to charge overnight - it was in bootloop when I went to sleep and .. bootloop when I woke up (at least it's charged now lol) I'm gonna try again though. I see that CWM has a sideload option, so I'm gonna wipe everything and try to sideload it from the ADB through the command prompt and see what happens. Feel free to leave any other suggestions though.
Got a question though, when I sideload the zip file should I sideload everything within the zip file or just the system image file? Maybe I'm getting bootloop because I'm installing a kernel on top of another kernel?
Click to expand...
Click to collapse
Sideload/flash the .ZIP. Do not extract it. You should simply just boot into recovery, choose "ScrubberPortRom_GPE5.1_LMY47D.zip", flash and wait for a couple of minutes and then reboot. That's it. The first boot should take around 5 minutes.
- Remember to do a full wipe in recovery before you flash
- Flash ScrubberPortRom_GPE5.1_LMY47D.zip
- Reboot
And do share any error messages if you get any while flashing.
Hey guys I desperately need help here. I got this Kindle Fire 8.9" years ago, and got abandoned by my Dad because we live in SEA, can't do much with it, I cannot even get the free apps through Amazon Appstore. I can use fake US CC in this matter to get the free apps but Is that even legit? I have real CC and a legit Amazon account I bought real stuffs from Amazon too back then (books, some shirts and some gadgets) but that doesn't seem to help much.
Anyway sideloading apps from Google Play don't help much since the compatibility are horrible, and sideloading the Google Playstore itself just don't work. I've attempted to install all the Playstore requirements, some installed and some spit out "Parse error - There was a problem parsing the package".
I figure I needed to convert it to a full Android. So searching around I found about "fastboot" but I'm not familiar with it. I only got my hands dirty on Odin and SP Flash Tool.
I followed the instruction here :
http://forum.xda-developers.com/kin...t-install-twrp-android-fire-os-8-5-1-t3278286
Works very well, rooted with KingRoot (which I already have offline), installed FireFlash, flashed the bootloader and recovery (100% like the instruction told me), got into TWRP, did a full backup of the current ROM and reboot. I can get it to the Carousel just fine. I attempted to flash Gapps package for ICS (gapps-ics-20120429-signed.zip) from here (found from googling around, checked the content too) :
https://docs.google.com/file/d/0B6zwjGaKK0GVUll5Sm95LWpNaDg/edit
The installation went quite well, after running Play Store, it crashes constantly. Found another tutorial on installing Google Apps on another forum, which I lost the link, so I want to attempt another Google Play install before went to CyanogenMod.
I noticed something, after each reboot, I need to re-flash TWRP and reboot. When I attempt to reflash TWRP I notice that kfhd8freedom-boot-8.4.6.img didn't have any warning anymore.
The tablet was a gift from my brother in law to my Dad. It was never been reset ever since. In fact after I installed Google Play, it still got my brother in law login in it, even though it doesn't have the Google Play store. So I figure I need to do a factory reset and start 100% fresh, just to be sure.
And this is where it went wrong. After the factory reset the device rebooted into fastboot mode. I don't know why. I see the orange Kindle Fire logo, then the screen went red then "fast boot mode" appear on screen. At this point I cannot do anything to it. Followed every power button tutorials out there, like pressing the power for 20 seconds then release then hold it for 2 seconds, or power plus volume up/volume down, no luck.
I plugged it into my PC, it shows as "Android", and below it "Android ADB". So I tried to use ADB console for it, it didn't respond. However it responds to "fastboot" commands, tried some commands from here :
http://forum.xda-developers.com/showthread.php?t=1474566&page=2
These commands works :
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
But it went straight back to fastboot mode. My guess is that the culprit is kfhd8freedom-boot-8.4.6.img.
Looking around in the forum there're so many obsolete solutions, like Kindle Fire HD First Aide download link are dead and it was intended for Fire 7.
So the questions are :
How would you recommend me to fix this? Fastboot command definitely still working from PC to my Kindle, if that is any help for this case. I really have no clue on what to do next. I only experienced with Odin and SP Flash Tool. I have no experience with fastboot.
I don't have any stock rom at hands, neither can find any googling around. Can anyone provide me with one? Just in case anything bad happen again after I fix this.
Will this work for 8.9"? Since he posted it in Fire 7 forum : http://forum.xda-developers.com/showthread.php?t=1951254
Info on my devices :
Kindle Fire Jem 8.9"
Latest stock (8.5.1_user_5159720) was installed
Rooted with KingRoot before went brick
I have no fastboot cable, but the fastboot command mentioned earlier works on regular USB (OnePlus One's stock cable)
Gapps for ICS was installed within too
I got both Windows 10 and Windows XP PCs at my hand. XP seems to recognize it better as ADB something under "android" in device manager.
I also got Ubuntu 16.04 installation, if needed.
Please help.
Thank you in advance!
Managed to boot into Fire OS
I just use fastboot to flash both kfhd8-twrp-2.8.7.0-recovery.img and kfhd8-u-boot-prod-8.1.4.bin.
After a reboot I went into TWRP, it does a few stuffs then rebooted again automatically.
Blue logo came up, then the orange logo, but it took longer than usual, I was a bit panicking. Forgot that on each first boot Android would take longer than usual.
But then kindle fire up the first time setup *phew*
First I want to get Gapps working on this device. If that working well, I'll stick with stock + GAPPS and custom launcher.
Only after that I will try CM12 on it.
I'll update on this thread later on how it goes.
Did anyone still have the stock recovery.img and boot.img?
Also after completing the initial setup my navigation and status bar went missing
The navigation bar blinks for a second then went black. While the status bar which displays wifi icons and hide the settings are missing. I cannot swipe from above at all.
With the status bar and navigation bar missing I can't do anything in it.
I still have APKs (es file explorer, kingroot, fireflash, all the ROMS like Cyanogen & TWRP) within the internal storage, but I cannot reach them.
Using silk tried to open file:/// it said "Webpage not available". I did this previously to sideload ES file explorer.
I went into recovery (power + volume up) but it went into fastboot mode instead of TWRP. And this time in "fastboot mode" it doesn't recognize either adb or fastboot commands from my PC.
I cannot even factory reset it.
What to do next?
My god, overall my impression so far? The hardware itself are near Apple premium quality.
But it looks like Amazon tried to follow Apple's footstep in term of software too.
Also this got me thinking of not having an android without any dedicated navigation buttons.
Finally SOLVED.
I forgot I can download ES file explorer from Silk. But turn out my Amazon appstore account allowed me to download it instead. Probably because my dad and brother's credentials was wiped clean from it.
I went to find flashfire.apk in my internal storage. Install it, then the unknown source popup warning appeared. Luckily it got the settings button which lead me to that particular option. After I tick it, I need to shut my kindle down, reboot then went to install it again, because there's no navigation bar available.
After it installed, turn out Kingroot's root are still intact. Kingroot's root permission pop up appeared.
Reflashed TWRP and Freedom boot. Shut my Kindle down, volume up + power and I'm in TWRP!!!
I decide I'll just go full CM this time. So, continued this :
http://forum.xda-developers.com/kind...8-5-1-t3278286
Now I'm currently updating the default Google apps from Google Play within CM 12. A little laggy but most definitely far better than FireOS.
I'll be using this Kindle for a week, I'll report here and hopefully can contribute to CM's bug report.
So far : camera, bluetooth, WIFI, GPS works out of the box. Brightness settings don't work.
Just one question, does this fastboot cable thingy "standard"? I saw one seller in my local online shop but it's for Xiaomi. Can I use it for OnePlus One and Kindle?
Oh yeah I got TWRP backup of the stock kindle, but I would still need both stock boot and recovery image. If someone kindly enough to provide me I'll be very thankful.
Checking in
Root are enabled by default, just found out about this. It got build in, barebone SU management, on which you can allow an app to have root access or not, but didn't see any comprehensive root access management like those found in SuperSU.
So installed SuperSU, told SuperSU to just update through TWRP, update binary was a breeze, all done automatically.
Watching YouTube on it was quite convenient. The screen obviously have near-retina display. Much better than viewing it on my Note 10.1 2012 obviously.
No problem browsing on Chrome.
Installed couple of other root apps, transfered it from my cheap chinese phone (Mito) using Bluetooth. All works well.
Tried to play Shooty Skies on it but it stuck on the intro screen. However on my OPO Shooty Skies refuses to run too and stuck on the intro screen. I've unlocked all characters on it I'll just wait for an update then.
Did some theming, custom boot animations works, styles applied, icons and everything applied without any problem at all.
One complain, the sound are too low, even when maxed out. Perhaps because the Dolby isn't supported by this CM yet?
My dad complained that there're too many updates after the initial setup so I use System Cleaner 2 to merge the updates into the system. The app did wonderful job on my Mito :
https://play.google.com/store/apps/details?id=com.flaki.systemcleaner2
Merged all updates into the system. If I don't do this everytime I wipe the device, the device will keep asking for updates. At least on the Gapps. It stuck at the middle, so I restart the System Cleaner 2 and it continue to do its job.
Then when I install Link2SD, which often do better job and more comprehensive apk management, weird things started to happen. It's said SuperSU are not installed. That and also couple of Google Apps. When I run Link2SD, their size is 0.
I think it's most likely caused by System Cleaner 2, couple of apps got interrupted when I merge the updated apk into the system?
So I reboot, then after I got into trebuchet, all the supposedly installed apps are gone. I don't know why. Thus I wipe everything clean again, reflash CM12, and just go into unrooted mode, update the gapps, remove my account and let my dad login using his and do whatever he want with this kindle.
Another minor update.
Since I've downloaded ICS (CM11), I figure I might just try it anyway. Since on whatever softwares I use I prefer older, stable version than bleeding edge and feature-rich but unstable ones.
Take a note I'm not saying CM12 is unstable, no problem so far, only those I pointed out in the previous post. But mostly because CM11 was marked "stable" on CyanogenMod download site.
First impression? It's snappier than CM12, and much more familiar than Lollipop. (since most devices I own still using JellyBean, with the exception of my OPO which already running Marshmellow).
My dad should be familiar with it too. Quite happy with it. But unfortunately the gapps are too outdated. It throws me server errors, and I cannot reach anything within Google Play. I can browse google websites without problem, even google play itself inside the default browser, so it's not connection problem definitely.
Updating the google play manually doesn't fix this. So any solution for this? Perhaps updated gapps for CM11/4.0.4?
Edit : eh nevermind, the Gapps provided for CM12 works with CM11. And very stable too.
Edit : CM11 for Kindle 8.9 is JellyBean 4.4, not ICS.
I guess I'll stick to CM11 for awhile then.
One more question, what does the CM12 recovery do? Can I install it alongside CM11? Is it better than TWRP?
stubbe said:
One more question, what does the CM12 recovery do? Can I install it alongside CM11? Is it better than TWRP?
Click to expand...
Click to collapse
Appears you have gone your own way completely independent of general guidance/solutions offered in the HDX forums. Seemed to work too based on your copious self-reporting. Hope all remains well; you are on an island which isn't necessarily a bad thing.
Hey Davey. Thanks for the response.
Davey126 said:
Appears you have gone your own way completely independent of general guidance/solutions offered in the HDX forums. Seemed to work too based on your copious self-reporting. Hope all remains well; you are on an island which isn't necessarily a bad thing.
Click to expand...
Click to collapse
Lol. Xda isn't my first English speaking forum so I did a search or two before I ask anything. And I've been around here quite awhile just rarely post but xda is my primary resource on mobile customizations.
I do still have couple of unanswered questions tho :
1. I still need the stock FireOS and recovery. I'm very sure I've backed it up but I probably accidentally wiped them in the process because I saved them in the internal storage.
2. Are the fastboot cables universal? This thing is hard to look for in my local stores and I can only find Xiaomi's. Will this work for every fastboot devices out there? I just found out about fastboot from flashing this kindle and I also recently find out my OPO uses fastboot as well so kinda thought it would be handy to keep one around.
3. How does CM12's recovery compares to TWRP? And will it runs fine along CM11 rom? I can try it myself but having late sleeps for days just because I bricked my kindle again isn't cool lol. TWRP does its job well. If it ain't broken I don't want to fix it. But I just want to know why @Hashcode included it in Cm12. If it's worth it I'll go ahead and install it and probably give further reports about it.
So far my dad is enjoying his CM11 powered kindle. Not sure if he finds any new bugs or not but seems that he's not complaining.
Cheers and thanks in advance.
stubbe said:
Hey Davey. Thanks for the response.
Lol. Xda isn't my first English speaking forum so I did a search or two before I ask anything. And I've been around here quite awhile just rarely post but xda is my primary resource on mobile customizations.
I do still have couple of unanswered questions tho :
1. I still need the stock FireOS and recovery. I'm very sure I've backed it up but I probably accidentally wiped them in the process because I saved them in the internal storage.
2. Are the fastboot cables universal? This thing is hard to look for in my local stores and I can only find Xiaomi's. Will this work for every fastboot devices out there? I just found out about fastboot from flashing this kindle and I also recently find out my OPO uses fastboot as well so kinda thought it would be handy to keep one around.
3. How does CM12's recovery compares to TWRP? And will it runs fine along CM11 rom? I can try it myself but having late sleeps for days just because I bricked my kindle again isn't cool lol. TWRP does its job well. If it ain't broken I don't want to fix it. But I just want to know why @Hashcode included it in Cm12. If it's worth it I'll go ahead and install it and probably give further reports about it.
So far my dad is enjoying his CM11 powered kindle. Not sure if he finds any new bugs or not but seems that he's not complaining.
Cheers and thanks in advance.
Click to expand...
Click to collapse
As noted you have gone you own way so the standard responses don't necessarily apply. Quick notes:
- there are several ways of restoring stock FireOS on this device, none clean, all with ramifications. Unless you need FireOS I would stear clear
- no standard way of restoring stock recovery; obtaining a compatible recovery image will be a challenge. TWRP is far superior
- fastboot cables do not work with this device
- I have no knowledge of CM12's recovery. TWRP gets the job done and is universal.
Davey126 said:
As noted you have gone you own way so the standard responses don't necessarily apply. Quick notes:
- there are several ways of restoring stock FireOS on this device, none clean, all with ramifications. Unless you need FireOS I would stear clear
- no standard way of restoring stock recovery; obtaining a compatible recovery image will be a challenge. TWRP is far superior
Click to expand...
Click to collapse
Ah dang. Not that much of a problem though. I just like to keep stocks ROMs around just to be safe. I won't be returning this thing to Amazon anytime soon, and I guess judging by my brief experience with the FireOS it won't be much of a use for our locals using the stock ROM if I or my dad actually decide to sell it.
- fastboot cables do not work with this device
Click to expand...
Click to collapse
Mmm... okay.
- I have no knowledge of CM12's recovery. TWRP gets the job done and is universal.
Click to expand...
Click to collapse
Ok fair enough and besides I don't go to the recovery much other than doing a backup.
Thanks Davey.
stubbe said:
With the status bar and navigation bar missing I can't do anything in it.
I still have APKs (es file explorer, kingroot, fireflash, all the ROMS like Cyanogen & TWRP) within the internal storage, but I cannot reach them.
Using silk tried to open file:/// it said "Webpage not available". I did this previously to sideload ES file explorer.
I went into recovery (power + volume up) but it went into fastboot mode instead of TWRP. And this time in "fastboot mode" it doesn't recognize either adb or fastboot commands from my PC.
I cannot even factory reset it.
What to do next?
My god, overall my impression so far? The hardware itself are near Apple premium quality.
But it looks like Amazon tried to follow Apple's footstep in term of software too.
Also this got me thinking of not having an android without any dedicated navigation buttons.
Click to expand...
Click to collapse
My Kindle Fire HDX (3rd Gen) is stuck in fastboot. After reading some forums, people don't recommend sending attempting to "recover" from the fastboot for the likelihood of bricking the device. Would you mind sharing the vulnerable bootloader + the twrp and the CM file you used? Along with the commands you used to flash. For some reason, the device isn't flashing the twrp image I have. I receive a "unknown partition" error when I try to flash twrp.
Thank you in advance.
Praxxer1 said:
My Kindle Fire HDX (3rd Gen) is stuck in fastboot. After reading some forums, people don't recommend sending attempting to "recover" from the fastboot for the likelihood of bricking the device. Would you mind sharing the vulnerable bootloader + the twrp and the CM file you used? Along with the commands you used to flash. For some reason, the device isn't flashing the twrp image I have. I receive a "unknown partition" error when I try to flash twrp.
Thank you in advance.
Click to expand...
Click to collapse
Answered elsewhere (one 48 other threads you posted to with the same question)
Stuck in Fastboot. I can flash and write and reboot, but 100% of the time it returns to FB. I had flashed freedom boot 8.46 2x. I most recently had lineage 14.1 and twrp 2.78.
Tried every tool in the book zero have worked.
UPDATE 6-9, out of fastboot, now stuck on kindle logo.
tia
KF 8.9hd jem