Related
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Stephen Wayne Hamilton said:
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Click to expand...
Click to collapse
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
drago10029 said:
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
Click to expand...
Click to collapse
If needed, I could back up my /system folder and send it to you.
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
it's alright man. someone on android forums has already made a custom ROM. so the ball is rolling on out weak old device :laugh:
build.prop?
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
did you ever get around to doing this? there is supposedly a stock image on androidforums but when I opened the Zip, all it had was the stock apps, no build.prop, which I think I blew away with xblast (xposed plugin). now I hang on the boot screen image. there is a stock Rom for the z993 our there, which I suppose I could use, because they are supposed to be the same phone, just different carriers... but then I need to get the at&t apn's and it is just a PITA. so if you could post /system backup or just a stock build.prop, that would be great!
(I'd post links to these rooms but I guess I'm too new of a member... I can provide them if needed.)
I'm way late on this, but just thought I'd post to say that I no longer have the device, and I was never able to fix it.In any case, I hope the rest of you guys get it fixed. It seemed to be a halfway decent phone, although a bit sluggish at times. But beyond that, with all the bloat removed, I'd say it ran pretty well for the duration of time that I had it (less than a month). I currently have a GNote 3 (T-Mobile) and a GNote Pro 12.2" now and it's just awesome, I'm really loving them.
Sorry, accidental double-post (can't figure out how to delete this post, the "Edit/Delete" button doesnt appear to have any option to entirely delete a post).
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
alirezayami said:
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
Click to expand...
Click to collapse
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
alirezayami said:
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
Click to expand...
Click to collapse
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
AlexZap said:
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thnx Alex
I would highly appreciate if anyone tell me what ADB Driver I should use for ZTE Z992. I almost understood all the procedure in the links but now the problem is despite I tried different ADB Drivers, but still ADB reboot-bootloader boots phone again in Normal bootloader.
Also Fastboot devices command does not see the phone, while ADB Devices command see it.
Seems bootloader is locked. Right? What should I do?
This is the method I used when I rooted my avail2 :
http://androidforums.com/zte-avail-2-zte-prelude/821217-how-root-zte-avail-2-z992-guide.html
The author (and I) just used the included drivers from zte that come with the phone. From what I remember, fastboot worked fine. Just hold the volume down button then turn the phone on. It will seem to lock on the start screen, but this is the bootloader. Then connect your cable and try your fastboot commands.
If you are already rooted, you can just download the package here
http://androidforums.com/prelude-all-things-root/797487-cwm-recovery-installer-zte-prelude.html
And skip the middle section, using the impactor to root (13 and 14).
Depending on what's wrong with your phone, you could also try just using the stock recovery and doing a system reset there. It will wipe any bad custom settings, but if the rom is still viable it might get you up and running again. It got me out of a bootloop without re-romming the whole thing. And with titanium backup or system app mover you can reinstall anything you need in the system partition.
*edit - Damn kindle auto correct
Sent from my KFTHWI using Tapatalk
A bit to much fiddling resulted in disaster
Hello XDA forum users,
I'm about ready to toss this phone in the trash. I have an AT&T Avail 2 with model number z992, which is apparently manufactured by a company called ZTE. First I think it would be helpful to explain what I've done to the phone and perhaps others out there can tell me if I've destroyed the phone or if it can be fixed.
A friend of mine sold me the phone for 10 bucks, its in great condition which is why its such a shame that it seems perma-bricked. I have no need for the phone aspect of the device, I simply wanted to "convert" it to a handheld media/application player, like an ipod or tablet for example. The phone comes with several bundled software applications that I find completely useless and wanted them removed, EX. AT&T Navigator and other AT&T software, plus a bunch of google applications.
The first thing I did when I decided to try and customize it was to use Kango's root tool which worked and rooted the phone. I was all excited that it worked and continued by installing the Super User application which allowed me to gain full control over the device. (I should have stopped there.) After the successful phone root I then installed a 3rd party app called NoBloat and used its uninstall options to remove a lot of stuff. I couldn't tell you exactly what all was removed but looking back, it must have been more important than I realized at the time. I know I took out all the AT&T software, then all the Google stuff to, which destroyed the play store. I didn't take out anything that seemed like a system file but apparently the Google stuff is the system files. The phone still worked in this state but it was erratic and things like Contacts would crash even if it was not running. So I considered that a failed attempt and commenced to do a factory reset using the recovery menu (Vol Up + Menu Key + Power button) but the factory reset didn't work, well not like it was supposed to. I had used the restore option before and it made the phone work like it was brand new. Now when the phone is powered on it will boot to the initial setup and ask me to choose a language, then it will get as far as the wireless connection screen (sometime not even that far) and the phone reports that "Unfortunately, Setup Wizard has stopped." and then I tap OK and the setup wizard restarts at the language screen. This is the state it is in now and I do not know how to fix it, I'm beginning to think there currently is no method to fix this.
Things I've tried so far include installing minimal ADB-Fastboot to try and sideload various ROM images, the ones I found here and other places. The phone is not recognized by Windows 7 though and the ADB does not work like it did on a motorola phone I did this to before. I've also purchased an inexpensive 8GB microSD chip with an adapter so I could put the ROM info on that and tried the "Update from external storage option" and that seems like it would work but none of the ROM's I've used will install. I guess because there is some kind of security feature built into the phones hardware which checks the data files for specific tags/sizes and therefore won't accept any of the ROMS I've tried.
There is no means to access the old file system anymore like most guides show, I do not have any CWM's installed nor any backup data whatsoever. It's been reset and now it seems the data it used to restore itself is, while not completely missing, damaged and will not reload anymore. All the guides I've read or watched usually show the user in the operating system or using software on a PC to type out commands. None of that works on this phone though, the phone as I just described it is basically bricked. Is there anything that can fix this, or is the phone a paper weight now? A functional ROM image from AT&T seems unlikely as they have absolutely no relevant information about this on the commercial website and the help and support seems like it's setup for old people who don't understand technology at all. If anyone out there has experience with issues like this then by all means let me know. If more information is necessary then I will be glad to provide it if available.
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Britton Burton said:
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Click to expand...
Click to collapse
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commands
adb.exe push cwm-z993.img /cache
adb.exe shell "su -c 'dd if=/cache/cwm-z993.img of=/dev/block/mmcblk0p17'
This should flash cwm if your phone is rooted and adb shell is working.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commandsp
Click to expand...
Click to collapse
I have not come across that particular file yet, I did try to google it and the only results it had were two and one of those was this post. Would you mind telling me where I might find a copy of the kaw202_recoverflasher.zip?
I managed to find the zip you were talking about and have downloaded it, for anyone else looking for it. I am unable to post links but I would have linked to the files you mentioned. For others looking for the same zip file search for "CWM Recovery Installer ZTE PRELUDE". That's the title of the thread I found the file on that Alex mentioned above. The instructions on the page don't seem like they apply to the situation I'm stuck in but I'll give it a whirl anyway and see if the files work.
If this forum is like the others I've read through so far then there is no real answer to the issue. The phone seems kind of new and not many of the power users on these forums use rinky dink phones like this one. You guys all have the 600 dollar models I guess. What bugs me about this this phone and the state I managed to put it in, is that the damn thing was programmed the first time when it was made. So it seems to me like there should be a way to reprogram the phone the same way the factory did it. Think about it, when they make the phones they don't have any information on the phone at all. It's completely empty, so there must be a way to load the software for the phone even if the phone has no data at all in the main storage. If the files in the recovery flasher.zip file work then I'll post back the results but if it's like the other files I've messed around with (which didn't do anything) then I'm throwing it in the trash can.
Anyway thanks for your response and for pointing me in a different direction Alex
---------- Post added at 09:15 PM ---------- Previous post was at 08:39 PM ----------
HELL YEAH!!! It worked thank you Alex,
I would have never figured this out without your help! The phone now has a version of CWM on it and the recovery menu is different. I just tried to install a ROM and it said successful. After the phone rebooted went back to the setup screen from ZTE but it still did the same thing. However this is progress and I should be able to "wander in the dark" and figure out a way to use the CWM to install a completely new rom. Any recommendations on a ROM to use for the z992?
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Britton Burton said:
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Click to expand...
Click to collapse
ze
Glad I could help, but none of the work was done by me, the guys over at android central did all the heavy lifting, I just pointed you in the right direction. I have a stock system e m image around here somewhere if you need it, tho installation will be a bit more complicated. If azazels rom ever gives you issues, ill dig it up and try and help you install it.
Sent from my KFTHWI using XDA Premium 4 mobile app
Hello everyone,
Here is the sad tale:
I recently got my Kindle Fire HDX and immediately started fiddling with it. Got it rooted and installed GApps using KindleFree. I then decided to buy KindleFree Pro to tweak even more. I fiddled around with the custom launcher option and basically bricked the device all within the same day that I got it! I'm not sure what that option changed exactly behind the scenes but I was able to ADB in and noticed that Launcher-release-signed_82046410.apk has a size of 0kb... that can't be right so I figured I'd start there...
First, I'd like for someone to confirm the size of theirs, if it isn't 0kb (which I doubt it will be) then can someone kindly upload that APK so I can load it up and hopefully get this thing working again?
Alternatively, can anyone suggest a way to simply reflash the stock rom via ADB somehow? I never installed safestrap and I don't think it can be installed via ADB. At least not that I've seen.
Thanks!
ok sorry
mkid89 said:
Hello everyone,
Here is the sad tale:
I recently got my Kindle Fire HDX and immediately started fiddling with it. Got it rooted and installed GApps using KindleFree. I then decided to buy KindleFree Pro to tweak even more. I fiddled around with the custom launcher option and basically bricked the device all within the same day that I got it! I'm not sure what that option changed exactly behind the scenes but I was able to ADB in and noticed that Launcher-release-signed_82046410.apk has a size of 0kb... that can't be right so I figured I'd start there...
First, I'd like for someone to confirm the size of theirs, if it isn't 0kb (which I doubt it will be) then can someone kindly upload that APK so I can load it up and hopefully get this thing working again?
Alternatively, can anyone suggest a way to simply reflash the stock rom via ADB somehow? I never installed safestrap and I don't think it can be installed via ADB. At least not that I've seen.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2786190 and that's why we have safestrap so you don't modify your stock http://www.youtube.com/watch?v=K6fPF5UZsWw
There are a few Devs still working on a way to flash something from fast boot no ETA means no promises seems the only fix for you may be to call Amazon . And maybe someone will chime in with a way to sideload an app I'm not sure. Good luck
I should have listened to the warnings when people said it was easy to brick! I've been modifying devices since the windows mobile days before android and never once have felt this hopeless! Safestrap will be the first thing I do once I get this running again.
The good news is I still have SU root access in ADB without needing a Fastboot cable. I'm thinking everything else but the launcher loads so it is pretty much fully functional but with no gui. It sometimes will even boots to the lock screen but unlocks to a black screen.
I think I should be able to sideload the launcher if someone can get me the apk.
well
mkid89 said:
I should have listened to the warnings when people said it was easy to brick! I've been modifying devices since the windows mobile days before android and never once have felt this hopeless! Safestrap will be the first thing I do once I get this running again.
The good news is I still have SU root access in ADB without needing a Fastboot cable. I'm thinking everything else but the launcher loads so it is pretty much fully functional but with no gui. It sometimes will even boots to the lock screen but unlocks to a black screen.
I think I should be able to sideload the launcher if someone can get me the apk.
Click to expand...
Click to collapse
If your patient somebody savvy enough will come by. and actually I know that I have read that someplace here I couldn't tell you where sorry. And if you're hoping for somebody to drop off the apk for you probably should let them know which firmware you are. Or you could always download the Bin file of your current firmware and exract it. Downloaded to an android rename it .zip and extract
That's a good idea but I don't know where to get the bin file or how to confirm I have the correct one. I had just updated so I believe it was the latest version. I'm thinking it's v13.3.2.1 or maybe v13.3.2.4 it said there were no more updates available so it should be the latest.
It's an 8.9. Don't think I mentioned that.
well
mkid89 said:
That's a good idea but I don't know where to get the bin file or how to confirm I have the correct one. I had just updated so I believe it was the latest version. I'm thinking it's v13.3.2.1 or maybe v13.3.2.4 it said there were no more updates available so it should be the latest.
It's an 8.9. Don't think I mentioned that.
Click to expand...
Click to collapse
8.9 is 14.3.2.4 https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.2.4_user_324002120.bin
Thank you for your help! I actually got it working shortly after my last post but got right into installing safestrap. ?
I'll post a write up tomorrow on what needed to be done in case anyone else has the issue. It's late where I'm at so I need to get some rest before trying to write it all up!
Ok! Now that I have a fresh mind I can document the steps I took to correct this issue.
How did this happen to begin with? I think that when I tried to set a custom launcher as default using KindleFree Pro, the launcher I selected was unable to load properly or something interrupted the process. Either way, it either would only load to the lock screen or just sit on the boot animation. I'm thinking the way that KindleFree works is that it replaces the default launcher apk with a link that points to the launcher you want to replace it with (hence the 0kb size). Either that or something got corrupted during the process of changing the launcher. I'm not sure what KindleFree does behind the scenes so this is all just speculation.
Anyways, on to the good stuff. Once I noticed the launcher was 0kb, thats where I decided to direct my troubleshooting efforts. I posted this thread hoping someone would upload the stock launcher for me to replace it with but jimyv gave me the idea to just grab it from the bin. I ended up finding the bin file here: http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190 before he replied with the direct link. The "Download Software Update" link is a direct link to the .bin file. I changed the extension, opened it up and found the launcher apk per jimyv's suggestion.
Once I had the file, I needed to get it onto the HDX. I more or less followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2588608
Instead of replacing the odex files, I replaced the launcher apk under /system/app/ As soon as it had finished copying over, the device went from the boot splash screen to the lock screen in what can only be described as a magical moment.
Interesting to note: Most people say that if you perform a factory reset from the stock recovery, your hopes of using ADB and having root are gone unless you get a factory/fastboot cable. I actually did perform a factory reset but for some reason was still able to use ADB and did not lose root access. I had used TowelRoot to root the device so I'm wondering if that is a more permanent means of rooting compared to other methods? Either way, I'm glad I didn't lose root. Otherwise I would have needed to wait for a factory cable to be shipped and to root it via ADB.
Fyi that Chinese root method which is posted early on in the rollback thread it will root with ADB only.. And the factory reset thing has not really been consistent throughout each user.. But more or less we have been advising people not to because the chances are greater that you will lose the superuser binaries and you definitely will lose safestrap if installed. What is hard to get through to people is when they are in a boot loop they get in a hurry and start factory resetting and that is not always the best option. Depending on exactly what is going on. Most of the time it is people losing their ADB access and cannot figure out how to uninstall the MTP drivers first then install the ADB drivers..
Good job getting your device back online and thank you very much for the closing write up .
mkid89 said:
Ok! Now that I have a fresh mind I can document the steps I took to correct this issue.
How did this happen to begin with? I think that when I tried to set a custom launcher as default using KindleFree Pro, the launcher I selected was unable to load properly or something interrupted the process. Either way, it either would only load to the lock screen or just sit on the boot animation. I'm thinking the way that KindleFree works is that it replaces the default launcher apk with a link that points to the launcher you want to replace it with (hence the 0kb size). Either that or something got corrupted during the process of changing the launcher. I'm not sure what KindleFree does behind the scenes so this is all just speculation.
Anyways, on to the good stuff. Once I noticed the launcher was 0kb, thats where I decided to direct my troubleshooting efforts. I posted this thread hoping someone would upload the stock launcher for me to replace it with but jimyv gave me the idea to just grab it from the bin. I ended up finding the bin file here: http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190 before he replied with the direct link. The "Download Software Update" link is a direct link to the .bin file. I changed the extension, opened it up and found the launcher apk per jimyv's suggestion.
Once I had the file, I needed to get it onto the HDX. I more or less followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2588608
Instead of replacing the odex files, I replaced the launcher apk under /system/app/ As soon as it had finished copying over, the device went from the boot splash screen to the lock screen in what can only be described as a magical moment.
Interesting to note: Most people say that if you perform a factory reset from the stock recovery, your hopes of using ADB and having root are gone unless you get a factory/fastboot cable. I actually did perform a factory reset but for some reason was still able to use ADB and did not lose root access. I had used TowelRoot to root the device so I'm wondering if that is a more permanent means of rooting compared to other methods? Either way, I'm glad I didn't lose root. Otherwise I would have needed to wait for a factory cable to be shipped and to root it via ADB.
Click to expand...
Click to collapse
could i use this way to fix my fault at this link bro?
http://forum.xda-developers.com/kin...p-kindle-fire-hdx-8-9-doesnt-able-to-t2816663
I took a look. That's a totally different issue than my issue. Mine wasn't getting stuck on the recovery screen. Sorry.
Does anyone know of a custom recovery that has been compiled for the LG L15G (AKA Sunrise)? I've been looking all weekend for one and haven't had any luck. I know there's no official build of either CWM or TWRP available for it, but I'm hoping to find an unofficial build that will work. I have it rooted already, but I've not been able to find a recovery for it and I don't want to do any more hacking till I have that.
Also if anyone can point me towards a decent custom ROM for this thing I'd appreciate it. I haven't had any luck finding that either.
siskulous said:
Does anyone know of a custom recovery that has been compiled for the LG L15G (AKA Sunrise)? I've been looking all weekend for one and haven't had any luck. I know there's no official build of either CWM or TWRP available for it, but I'm hoping to find an unofficial build that will work. I have it rooted already, but I've not been able to find a recovery for it and I don't want to do any more hacking till I have that.
Also if anyone can point me towards a decent custom ROM for this thing I'd appreciate it. I haven't had any luck finding that either.
Click to expand...
Click to collapse
i have this model but i updated it before I knew it would prevent me from rooting it... any way you could upload a backup of your firmware that I can use to downgrade to?
How can you beat a $9 phone
siskulous said:
Does anyone know of a custom recovery that has been compiled for the LG L15G (AKA Sunrise)? I've been looking all weekend for one and haven't had any luck. I know there's no official build of either CWM or TWRP available for it, but I'm hoping to find an unofficial build that will work. I have it rooted already, but I've not been able to find a recovery for it and I don't want to do any more hacking till I have that.
Also if anyone can point me towards a decent custom ROM for this thing I'd appreciate it. I haven't had any luck finding that either.
Click to expand...
Click to collapse
Just picked this phone up too, any luck on getting a ROM for it?
I picked one up....couldn't resist for just $9.82. I didn't let it update, so I was able to root it with Kingroot 4.6. Quite snappy after all the bloatware was removed. Have about 1.5gb of internal memory left, but added an 8gb microSD. I haven't been able to findy any recovery, doubt one exists. Nice little emergency phone to have in the car or backpack.
Just picked this phone up as well, and KingoRoot doesn't work. I wasn't prompted for a firmware update when I first cranked it up so I guess I'm on some version that isn't supported? Can anybody clarify what the status of this device is currently? I've got the Tracfone version.
I just rooted my LG L15G tracphone with KingRoot and it worked immediately. Great!
Next step is to get this 10 dollar phone unlocked.
By the way, my firmware version is: Android 4.4.2
I picked one up last night. Kingroot said my device wasn't supported but clicking "try it" successfully rooted the device!
I replaced Kingroot with SuperSU by following these directions: http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html?m=1
I've removed McAfee, but are the Tracfone bloat apps safe to remove?
Tracfone refused to give me the unlock code because their policy is that the phone must be active and have minutes on it for 12 consecutive months (wtf?)
One unlock website did have our device listed (http://www.imei-unlocker.com) but both their methods said that unlock wasn't available yet. They refunded me for both attempts.
If anyone has a Linux setup, we can compile our own TWRP. I found the kernel source earlier today: http://opensource.lge.com/osSch/list?types=NAME&search=Lgl15g
anuraj1 said:
I picked one up last night. Kingroot said my device wasn't supported but clicking "try it" successfully rooted the device!
I replaced Kingroot with SuperSU by following these directions: **Link removed**
I've removed McAfee, but are the Tracfone bloat apps safe to remove?
Tracfone refused to give me the unlock code because their policy is that the phone must be active and have minutes on it for 12 consecutive months (wtf?)
One unlock website did have our device listed (**Linked Removed***) but both their methods said that unlock wasn't available yet. They refunded me for both attempts.
If anyone has a Linux setup, we can compile our own TWRP. I found the kernel source earlier today: **link removed **]
Click to expand...
Click to collapse
I just got this phone for Christmas. What version of Kingroot did you use? The ones I'm downloading don't work. (The one I've tried says something about no available root strategy and adds me to some stupid que line or something. There is no "try it" button after it does this.) You happen to have the specific APK you used and what version was your phone on when you rooted it?
Currently mine is Android version 4.4.2 with kernel version 3.4.0. I haven't attempted to update it yet as I am to assume that would be a bad idea. Unless you have a version newer then mine, then I guess updating would actually help me in this situation.
Looks like there STILL isn't any custom rom or custom recovery for this phone yet. It's been out since July and thanks to the $10 phone promo, there are tons of these out in the wild so I'm surprised nothing has been done with it yet.
I really want to root it as I want to remove some bloatware like McAfee and Polaris office. I would also like to uninstall Chrome so that I can install it to SD card. (unless Chrome can't be moved to SD card, in which case this would be a waste of time I suppose.) Aside from a few extra Google apps, there really isn't that much bloatware aside from what I already mentioned above. I can wait for a custom rom/recovery (though having a custom recovery would be nice as it would allow me to backup my phone incase something gets messed up). I just want to free up some internal storage by removing the bloatware.
(also, the no outside links thing with new users is annoying. I agree new users shouldn't be allowed to. But please at least code the forum to be smarter. I had to manually remove all the links to a post I quoted before it would let me post. That's kinda stupid. If I quote a post in the same thread I'm responding too that has links, it should be assumed to be safe since the links were posted by a verified member. I would hope the forum could fix that or at least have the common ***king courtesy of removing the links from the quotes for me. )
EDIT:
Ok some interesting news to report. It almost wants to work now. For what ever reason, it randomly decided to finally show me the "Try it" button. (I should have clarified earlier it never displayed that button. It would just say root strategy unavailable and that was the end of it. Now it says there is one and lets me use the Try It button. However it will get to about 60% (though it will randomly stop earlier on other attempts. Sometimes my phone will reboot after it reaches 20% or so) it will just say root failed.
I don't understand why this is seeing that my LG Sunrise is pretty much the same as someone else who managed to root it with Kingroot. It's never been updated. (I even checked for updates and there aren't any).
The only thing I can think of that might be a problem is that the phone isn't yet activated as I have not gotten air time for it yet. Does this root process require the phone to be on an active SIM first?
Root with Root Genius
I have root my LG L15G (Android 4.4.2, kernel 3.4.0+, software version LGL15G10f) with Root Genius for PC v3.0.85.
Of cource, before rooting "Developer options" must be unlocked (5-8 taps on Settings>About Phone>Software information>Build number) and turned on; in "Developer options" must be selected "USB debugging".
After this connect phone to PC. All phone drivers must be installed.
Run Root Genius. When program will ready and say about connect with LG L15G - press one button. After 2-3 minutes root is enabled.
Titanium Backup works. But I have no ideas for unlock the phone to make a possibility work in other GSM-networks, except TracFone's.
Hmm, I had tried Root Genius and that didn't work for me (and yeah I did enable USB debugging. I apparently was using an older build of Root Genius. But I found and used the build you used and still get the unsupported model error. ). My software version is as follows:
Android Version: 4.4.2
Baseband version: M8610B-AAAANAZM-1.0.6060
Kernel version: 3.4.0+
Build number: KOT49I.LGL15G11a
Software version: LGL15G11a
There does appear to be some differences in the software version of mine vs the post above me. I'm guessing they changed something. But that's odd as my phone was brand new just like yours assuming you got it around the same time as me.
EDIT. Ok some bad news. Looks like there was a newer software update (that my phone apparently came with) that blocks root and even prevents download mode from working. (I had attempted to boot into download mode but none of the button combinations work and even the root scripts I've tried can't get it to reboot into download mode)
Seems I'm stuck with a phone I probably can't ever root.
It seems it can still be forced into download mode by using a "56k/130k/910k cable" cable (special cable with resistor on one of the data lines). But they are running for $18 on ebay and way to damn expensive for a simple cable with a resistor installed. Resistors are probably only worth pennies each, so they are way too expensive to be charging that much for it.
If I had a such a cable, the root script I had tried awhile back might have worked as it needs to get the phone into download mode to finish the process.
There seems that there's little hope for your phone but I may have a solution. My LG Sunrise got updated as well and got root access with the update. You can use King Root but not Kingo.
Look it up on Google. So far I've had no success on getting to the recovery mode.
I've tried rooting with KingRoot. It will just say it failed after 20% (sometimes it goes higher, but always end with it saying this).
Note that unlike your phone, mine already had the latest update out of the box.
Apache Thunder said:
I just got this phone for Christmas. What version of Kingroot did you use? The ones I'm downloading don't work. (The one I've tried says something about no available root strategy and adds me to some stupid que line or something. There is no "try it" button after it does this.) You happen to have the specific APK you used and what version was your phone on when you rooted it?
Currently mine is Android version 4.4.2 with kernel version 3.4.0. I haven't attempted to update it yet as I am to assume that would be a bad idea. Unless you have a version newer then mine, then I guess updating would actually help me in this situation.
Looks like there STILL isn't any custom rom or custom recovery for this phone yet. It's been out since July and thanks to the $10 phone promo, there are tons of these out in the wild so I'm surprised nothing has been done with it yet.
I really want to root it as I want to remove some bloatware like McAfee and Polaris office. I would also like to uninstall Chrome so that I can install it to SD card. (unless Chrome can't be moved to SD card, in which case this would be a waste of time I suppose.) Aside from a few extra Google apps, there really isn't that much bloatware aside from what I already mentioned above. I can wait for a custom rom/recovery (though having a custom recovery would be nice as it would allow me to backup my phone incase something gets messed up). I just want to free up some internal storage by removing the bloatware.
(also, the no outside links thing with new users is annoying. I agree new users shouldn't be allowed to. But please at least code the forum to be smarter. I had to manually remove all the links to a post I quoted before it would let me post. That's kinda stupid. If I quote a post in the same thread I'm responding too that has links, it should be assumed to be safe since the links were posted by a verified member. I would hope the forum could fix that or at least have the common ***king courtesy of removing the links from the quotes for me. )
EDIT:
Ok some interesting news to report. It almost wants to work now. For what ever reason, it randomly decided to finally show me the "Try it" button. (I should have clarified earlier it never displayed that button. It would just say root strategy unavailable and that was the end of it. Now it says there is one and lets me use the Try It button. However it will get to about 60% (though it will randomly stop earlier on other attempts. Sometimes my phone will reboot after it reaches 20% or so) it will just say root failed.
I don't understand why this is seeing that my LG Sunrise is pretty much the same as someone else who managed to root it with Kingroot. It's never been updated. (I even checked for updates and there aren't any).
The only thing I can think of that might be a problem is that the phone isn't yet activated as I have not gotten air time for it yet. Does this root process require the phone to be on an active SIM first?
Click to expand...
Click to collapse
If you still haven't got root yet,for me it was McAfee that's been blocking Kingroot every since Nov.
Even though I never set up an account,it was the culprit..I opened the McAfee app created the account and Disabled.
Went to settings,ALL apps,then opened McAfee..Scrolled down to ''manage space'' and deactivated and hit force stop.
Then I ran KingRoot version 4.8.0 from this site.My device rebooted at around 30%,went back to KingRoot and it finished rooting.
THANK YOU!
It took a few tries, but after disabling McAfee's root protection (It completely skipped my mind that this stupid app would have a feature that would interfere. ) KingRoot definitely did it's thing. (I had to re-attempt twice because once it rebooted and failed. So I had to kill the app again and try again. That time it rooted without restarting).
I've already uninstalled McAfee and a few other system apps I need to get rid of. (McAfee on a $10 phone? Yeah..... No.... I'll take my chances. )
I also replaced KingRoot with SuperSU and uninstalled Purify and the KingRoot app that installed the root. After cleaning out unneeded bloatware, this phone is pretty responsive now! It used to lag a little and not register touches some times. But after cleaning out the bloatware (McAfee was probably the main source of the lag) it runs pretty well now!
EDIT:
Ok minor issue. I can't seem to uninstall Chrome (since it's a system app on this phone). It keeps reinstalling it self. It won't stay gone. What would be causing that? I wanted to move Chrome to SD so it doesn't take up space. But this particular phone won't let me.
Seems to happen with Polaris Office as well. Not a big deal at the moment. I can just freeze this app so it won't take up any CPU time/ram. Freezing it seems to work fine. Uninstalling it just results in it mysteriously reinstalling it self....
Does yours lose root after rebooting? I tried to run 'adb reboot recovery' for giggles and SuperSU no longer had root when it failed to start the local and booted normally.
---------- Post added at 04:27 AM ---------- Previous post was at 04:19 AM ----------
anuraj1 said:
If anyone has a Linux setup, we can compile our own TWRP. I found the kernel source earlier today: http://opensource.lge.com/osSch/list?types=NAME&search=Lgl15g
Click to expand...
Click to collapse
I have the Android SDK installed on my desktop but the TWRP porting guide by Dees_Troy is a little bit too vague for a first timer. I was able to extract the stock recovery using dd this afternoon.
I haven't tried to reboot mine into recovery mode. But root sticks when doing normal reboots.
recovery/rom LG-L15G
I am currently working with this phone to provide a twrp recovery that will work properly, please hang on while i work out the bugs. its been a while since i developed anything, was taking a extended break from development
DroidHost said:
I am currently working with this phone to provide a twrp recovery that will work properly, please hang on while i work out the bugs. its been a while since i developed anything, was taking a extended break from development
Click to expand...
Click to collapse
That's really awesome! I'm looking forward to what you come up with. I'd be happy to send you some beer money for your efforts as well!
anuraj1 said:
That's really awesome! I'm looking forward to what you come up with. I'd be happy to send you some beer money for your efforts as well!
Click to expand...
Click to collapse
Hang on to that beer money for now, I am working on zeroing the /laf partition to gain access to fastboot hopefully this will work out, and we will have save and easy way to unlock the bootloader on phone to make it flashable
DroidHost said:
Hang on to that beer money for now, I am working on zeroing the /laf partition to gain access to fastboot hopefully this will work out, and we will have save and easy way to unlock the bootloader on phone to make it flashable
Click to expand...
Click to collapse
That's fantastic. If it would help, I have one of those variable resistor cables that some LG phone requires for supporting baseband or entering the bootloader.
This is the cable I have: http://m.ebay.com/itm/131321398015
It is described here as well: http://forum.xda-developers.com/showthread.php?t=2069564
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
PariahNine said:
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
Click to expand...
Click to collapse
Given your firmware level:
- verify device is still rooted (use towelroot if needed)
- flash twrp recovery
- update bootloader to v3.2.3.2
- unlock bootloader (try 1-click method)
- flash rom of choice (Nexus, CM 11/12/13), SlimLP)
Search through the forums for relevant threads. Ask questions along the way. You have some work ahead (hours) but a nice reward at the other end.
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
PariahNine said:
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
Click to expand...
Click to collapse
Thoughts:
- moving roms between slots (specifically stock) via backup/restore is generally a bad idea in Safestrap; consider yourself lucky if you used this technique
- if the rom in the stock slot (assuming FireOS 13.3.1.0) boots properly then you can safely remove Safestrap v3 via the uninstall option in the apk
- do not wipe anything in Safestrap nor execute a 'factory reset' from the native Kindle recovery menu (bad outcomes)
- keep WiFi off / airplane mode engaged unless you are 100% sure the OTA block is working
- snag a copy of Flashify to install twrp and the 3.2.3 bootloader update
- check MD5 checksums with ES File Explorer or another tool before flashing; especially important for bootloader update!
- backup your existing recovery with Flashify before flashing twrp; leave a copy on the device
- enable USB debugging in Kindle settings (optional but offers additional recovery options should something go wrong)
- flash twrp first and make sure it works (reboot to recovery; have a look around but don't change anything)
- reboot FireOS and then use Flashify to update bootloader. Did I mention you should check MD5?
Post when above tasks are complete or if you have questions. Cover bootloader unlock next. Be aware the above steps carry some risk including permanently bricking the device. Make sure you have a clear understand on what is suppose to happen; double/triple check everything before committing changes. Good luck.
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
PariahNine said:
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Click to expand...
Click to collapse
- use the original apk to remove (uninstall) Safestrap v3 recovery; you do not need to uninstall the apk itself
- uninstalling Safestrap will not impact root
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
PariahNine said:
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
Click to expand...
Click to collapse
The FireOS version number will not change following bootloader update. It is a separate 'component' whose version can not be independently queried or verified. Typically the system (what you see, ie: FireOS) and bootloader are updated together and share the same version identifier. In this instance are only flashing the bookloader update as FireOS will soon be replaced by a different ROM. No need to update it and assume the associated risks.
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
PariahNine said:
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
Click to expand...
Click to collapse
Hum. Best handled by @draxie who developed 1-click. Generally pretty responsive to forum posts. If 1-click doesn't do it can always try the manual approach (a LOT more involved but not risky). Let's see what shakes out.
This is what I'm getting from the batch cmd window:
VirtualBox does not appear to be installed
Downloading 'https://www.virtualbox.org/wiki/Downloads' to 'C:\Users\Pariah\Down
loads\1-Click\1-Click\dwnlds'
Download complete.
Downloading 'http://download.virtualbox.org/virtualbox/5.0.12/VirtualBox-5.0.12-
104815-Win.exe' to 'C:\Users\Pariah\Downloads\1-Click\1-Click\VirtualBox-5.0.12-
104815-Win.exe'
Download complete.
Launching the VirtualBox installer momentarily
Please complete the installation with USB support enabled
Installation complete.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Virtual machine '1-Click' is created and registered.
UUID: 6b44be97-c931-47a5-8eeb-b780f5783b78
Settings file: 'C:\Users\Pariah\VirtualBox VMs\1-Click\1-Click.vbox'
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xf
fffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\Syste
m32\acaptuser64.dll: None of the 1 path(s) have a trust anchor.: \Device\Harddis
kVolume2\Windows\System32\acaptuser64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\ac
aptuser64.dll': rcNt=0xc0000190
Oracle VM VirtualBox Headless Interface 5.0.12
(C) 2008-2015 Oracle Corporation
All rights reserved.
Click to expand...
Click to collapse
And the 1-click instance in Virtual Box is showing "Booting the kernel."
Here is the method I used to block OTA updates.
Originally Posted by berndt_toast
Yeah, I agree. Staying rooted is difficult, but doable. I am still on the rootable version (13.3.1.0) and have stayed on it even through the OTA updates that have been released. I have stopped them from auto-applying (and from even being seen as updates) by doing the following:
I renamed otacerts.zip to otacerts.zip.old in /etc/security/
I also renamed com.amazon.dcp.apk to com.amazon.dcp.apk.old in /system/app/
Doing those prevent OTA updates from working and if you check for updates from the device, it says none are found (at least it has worked for me).
Click to expand...
Click to collapse
Do I need to undo this before proceeding with the bootloader update and unlocking?
PariahNine said:
Here is the method I used to block OTA updates.
Do I need to undo this before proceeding with the bootloader update and unlocking?
Click to expand...
Click to collapse
No - tasks ahead have no dependence on Amazon's update engine.
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
PariahNine said:
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
EncryptedCurse said:
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
Click to expand...
Click to collapse
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Davey126 said:
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Click to expand...
Click to collapse
If you want to give manual unlocking a try:
- use these drivers; you likely need to reinstall when flipping between adb and fastboot
- detail procedure
- suggest browsing this thread for additional info/tips. Lots of noise but some diamonds in the rough too
- careful not to go down a rabbit hole; some solutions are one offs that worked great for the poster due to their familiarity with a particular too, platform or technique
- unlike almost everything else with HDX you can not harm your device with bootloader unlock attempts. It will either work or not with no adverse consequences either way
There are a few excellent posts by @Cl4ncy, @jerryl and others (possibly one of mine) in different threads; unfortunately I wasn't able to surface them in a quick search. Nature of the HDX forums. A gold mine if information that is a bxxtch to access.
Before diving in you may want to flash CM11 or Nexus v4 which can be done with a locked bootloader. Both are rock solid KitKat based roms that will expose the full capabilities of your device and offer continuity to CM13 once unlocked.
Good luck.
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
PariahNine said:
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
Click to expand...
Click to collapse
Happy to hear you were sucesfull. Thanks also for sharing your experiences and insights. Should be helpful to others as they navigate through the process. Every nugget of new information helps!
Hi all,
tl;dr: Tried to hard unbrick my Oneplus X, which was partly succesful (no OS is installed in the process, while there should be). I am now stuck with no OS and only the Oneplus recovery. I want to install an OS, but it says my bootloader is locked. To unlock it, I need an OS ==> vicious circle.
Full story below:
Recently I've decided to reinstall LineageOS on my Oneplus X because I had quite some problems with it (battery drain, apps crashing, wifi slow to connect, ...). I've done it like 5 times before on this device for various reasons, so I didn't expect any problems. I had LineageOS 14.1 and TWRP 3.0.3 installed. When I wiped everything, I wanted to flash the ROM I had ready using TWRP. However, gave an error number 7, saying that the ROM is not compatible for the device, which I am sure was. Remembering I had a similar issue a while back, I installed flashed an updated version of TWRP (3.2.2) using TWRP itself. That was successfull, but here's where the trouble began.
I noticed that TWRP didn't recognise any storage (Internal storage, SD card and USB-OTG all showed up as 0 MB) any longer. Neither could I mount any of the storages. I've tried a lot of things to solve this. After a while, I decided that the only hope left was the 'mega unbrick guide' (https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/) which claims to be able to recover any device, unless it has a hardware problem. I got good hope as I got near the end of the guide. The last step says 'Disconnect phone from PC and boot into system', but here I got stuck on the Oneplus boot logo, making me think that there is no OS installed on the device.
I can still access the recovery using power button and volume down, but the recovery that the mega unbrick guide installs, is the limited Oneplus recovery. It allows to install a ROM from the local storage, or from USB using adb sideload. When I try option 1, nothing happens, no new screen opens or anything. When I try option 2, I enter the adb sideload mode which would normally allow me to sideload a ROM using my pc. My pc confirms I'm in adb sideload mode, and I try to sideload a ROM. It starts fine, but after a few seconds, it says 'Installation failed'. I've tried stock OOS, latest OOS as well as LineageOS 14.1 that was installed before.
Another thing that I can do in the Oneplus recovery is rebooting into fastboot mode, where I should be able to flash the recovery of my choice. Again, my phone confirms I'm in fastboot mode and I try to flash or boot TWRP recovery, but I get the message: 'FAILED (remote: Device not unlocked cannot flash or erase)'. Okay, seems like the bootloader is still locked, so I should just go and unlock it using 'fastboot oem unlock'. This gives the message: 'FAILED (remote: oem unlock is disabled)'. I've been searching around a lot on the internet, and it seems like the only way to enable oem unlock, is in the OS itself in the developer settings. But the problem is, I have no OS and cannot install one because the bootloader is not unlocked... So I'm stuck in this vicious circle.
I've been searching on the internet for hours and starting to lose hope. At this point, I would be happy if I can just have any OS (OxygenOS or LineageOS or something else) running. If I have that, I should be able to take it from there.
Any help is much appreciated. Thank you very much.
Kind regards,
Jeroen
Bump
Update:
Oneplus support could solve the problem for me! Or at least, partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!
I hope I can also help other people with the same problem.
Japeroen said:
Update:
Oneplus support could solve the problem for me! Or at least, partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!
I hope I can also help other people with the same problem.
Click to expand...
Click to collapse
Greatly appreciate your feedback here. I think that I am in the same situation you were. Used what you suggested - using MSM v2.1 that you provided with the system.img, non-hlos and userdata.img from MSM v2.0. The process ends with "Download Complete" written in green but when I check "Verify" it fails exactly @system.img, userdata and non-hlos. I can't boot recovery either after these.
Do you have any clue as to why it is so?
gabytzu338 said:
Greatly appreciate your feedback here. I think that I am in the same situation you were. Used what you suggested - using MSM v2.1 that you provided with the system.img, non-hlos and userdata.img from MSM v2.0. The process ends with "Download Complete" written in green but when I check "Verify" it fails exactly @system.img, userdata and non-hlos. I can't boot recovery either after these.
Do you have any clue as to why it is so?
Click to expand...
Click to collapse
As far as I know, I haven't used the "Verify" button. Right after the green "Download Complete" line, I booted into the OOS stock recovery by pressing volume down and power button (I think? Not sure anymore, I always forget it). From there, I could install OOS with a official ROM image.
Are you sure you moved the correct files from V2.0 to V2.1? The way I knew which files to move, is by first starting the V2.1-program without any added files. Then it told me 'system.img missing' (or something like that), so I knew I had to add that. After adding that, I ran the program again and added the next file it said it was missing etc etc.
Sucks to hear your recovery process doesn't go as "smooth" (it's all relative of course) as mine.
Japeroen said:
As far as I know, I haven't used the "Verify" button. Right after the green "Download Complete" line, I booted into the OOS stock recovery by pressing volume down and power button (I think? Not sure anymore, I always forget it). From there, I could install OOS with a official ROM image.
Are you sure you moved the correct files from V2.0 to V2.1? The way I knew which files to move, is by first starting the V2.1-program without any added files. Then it told me 'system.img missing' (or something like that), so I knew I had to add that. After adding that, I ran the program again and added the next file it said it was missing etc etc.
Sucks to hear your recovery process doesn't go as "smooth" (it's all relative of course) as mine.
Click to expand...
Click to collapse
Hah, did not expect an answer, I've seen your thread on oneplus forums as well, glad you were so quick to answer here. I've found the MSM2.1 uploaded in a google drive with all the files afterwards, after some long hours of searching too. Anyway, I still can't adb sideload anything, the storage seems 'corrupted' to say the least, but there are imporvements from MSM v2.0 and v3.0 flahses. The recovery menu works flawlessly now, no artifacts or freezes, also the phone 'almost' booted. It went to the "Updating android apps" thing.
I don't really know what to do next. Recovery does not help me at all. I can't sideload anything, it renders a "protocol fault" error. Internal storage has 2 empty folders within and that's about it. Also the bootloader is locked now and I can't make any use of fastboot mode.
gabytzu338 said:
Hah, did not expect an answer, I've seen your thread on oneplus forums as well, glad you were so quick to answer here. I've found the MSM2.1 uploaded in a google drive with all the files afterwards, after some long hours of searching too. Anyway, I still can't adb sideload anything, the storage seems 'corrupted' to say the least, but there are imporvements from 2.0 and 3.1 flahses. The recovery menu works flawlessly now, no artifacts or freezes, also the phone 'almost' booted. It went to the "Updating android apps" thing.
I don't really know what to do next. Recovery does not help me at all. I can't sideload anything, it renders a "protocol fault" error. Internal storage has 2 empty folders within and that's about it. Also the bootloader is locked now and I can't make any use of fastboot mode.
Click to expand...
Click to collapse
Haha I know the feeling! But thanks to e-mail notifications.
I also thought that my storage was corrupted at first, given the symptoms I described in my first post, so I didn't expect my OPX to be revived, but hey it's still alive now.
I also had the locked bootloader-thing. The way I could unlock it, is by first installing OOS using the stock recovery (which was installed using the tool), then unlocking it in OOS, so I could install another recovery and eventually another OS.
I'm afraid I already explained the problems I encountered and the procedure I followed pretty detailed. If you have anything that deviates from this, I'm sorry to say that I can't really help you with that, even if I wanted to. Did you perform the exact steps I mentioned (including the V2.1-tool that I linked to)? What exactly do you mean with the "3.1 flash"?
It's also already 2 months ago, so I don't even know exactly what I've done apart from what I've described...
Japeroen said:
Haha I know the feeling! But thanks to e-mail notifications.
I also thought that my storage was corrupted at first, given the symptoms I described in my first post, so I didn't expect my OPX to be revived, but hey it's still alive now.
I also had the locked bootloader-thing. The way I could unlock it, is by first installing OOS using the stock recovery (which was installed using the tool), then unlocking it in OOS, so I could install another recovery and eventually another OS.
I'm afraid I already explained the problems I encountered and the procedure I followed pretty detailed. If you have anything that deviates from this, I'm sorry to say that I can't really help you with that, even if I wanted to. Did you perform the exact steps I mentioned (including the V2.1-tool that I linked to)? What exactly do you mean with the "3.1 flash"?
It's also already 2 months ago, so I don't even know exactly what I've done apart from what I've described...
Click to expand...
Click to collapse
It was a typo, I meant v2.0 and v3.0(for oneplus 3). The op3 unbrick guide suggested that the v3.0 might work for oneplus x as well, so I tried that out too.
Anyway, I've done the process a couple more times and the phone booted untill you set the device up, when you are finished it just reboots. I can see the lock screen, I can't bring down the upper bar or enter the settings, if unlocked it prompts me to the first time set up and upon it's completion the phone reboots. I wiped cache,data did a factory reset. Now it's back with the recovery menu artifacts and not booting anymore either. I will use that tool a couple more times then I am done until further suggestions from this forum. After all, my life does not depends on reviving it, I was gonna give it to my brother, who shattered his phones' touchscreen, until he repairs his. Thank you again for replying, no need to reply to this, unless it can help my case.