Related
My Nexus 6 has presented me with an interesting challenge. During my attempts/process to root my phone, inevitably, one must reboot your phone. And as the reboot takes place the phone always goes into the "Charge" mode and not the "File Transfer" mode that the phone was in as it began the root process. I'm at a cross in the road because I cannot complete the root process. The only option that has presented itself to me is to restart the phone. And while my phone works properly, it halts the root process. I have just purchased another USB cable that charges and transfers data/syncs to cover that question. Any hints would be appreciated. I have had this phone unlocked using Chainfire's Nexus Root Toolkit a while back. It worked flawlessly. I've not really been interested in a custom ROM/Kernel etc. but in continuing to research this area. I'd like to try and unlock then root the phone again. Any hints would be appreciated
If your phone got the January update from Google, they patched a ton of the "exploits" that previously were/can be used to root Android devices. These were pushed out to the Nexus line by Google and made available for OTA by wireless vendors otherwise. This could be the issue you're running into now. If you haven't updated, then I think you just may need to find an alternative rooting method, as the one you tried may not be 100% compatible or is missing some sort of command to direct the device to go into file transfer/download mode.
wosumner said:
If your phone got the January update from Google, they patched a ton of the "exploits" that previously were/can be used to root Android devices. These were pushed out to the Nexus line by Google and made available for OTA by wireless vendors otherwise. This could be the issue you're running into now. If you haven't updated, then I think you just may need to find an alternative rooting method, as the one you tried may not be 100% compatible or is missing some sort of command to direct the device to go into file transfer/download mode.
Click to expand...
Click to collapse
I really appreciate your perspective. And without a doubt I'll look around and see where this goes. Just reading about all the work that has taken place since I purchased the phone, the landscape is a lot more enticing.
Hi,
I'm brand new to this forum and my name is Jessy, and it's my pleasure to be here!
I recently bought this AT&T GoPhone (for around $29) at Walmart, and I was following this guide to allow me to use my SD Card as an internal memory storage unit for my phone, but I found out that I need to unlock the Bootloader, install TWRP, SuperSU and Link2SD apps to the SD card and my phone. Since this smart phone is similar to the Idol 3, could I use this method to unlock the Bootloader for my phone or do I have to try a different approach?
I appreciate your time and I look forward to contribute further to these forums! Thanks again!
-Jessy
I picked one up on Black Friday, and decided to root it. I was only able to install an older version of SuperSU though (v2.46). First I had to install the PC version of KingRoot (It's in Chinese I believe, but middle button is always "next" or "yes"), root the phone, and then replace KingRoot with SuperSU. Took me a few tries.
This is the guide I used from the forum:
SuperSU Me_6.4.apk
KingRootSetup v3.2.0.1129.exe
1. install kingrootsetup on pc(must have internet connection to work)
2. connect ur phone with ADB enabled from developers option
3. root ur phone by following on screen instructions...
4. after rooting,install supersume on phone
5.open the app,click on big blue button and wait...
done,replaced kingroot with supersu..
-Mario
Merazomo said:
I picked one up on Black Friday, and decided to root it. I was only able to install an older version of SuperSU though (v2.46). First I had to install the PC version of KingRoot (It's in Chinese I believe, but middle button is always "next" or "yes"), root the phone, and then replace KingRoot with SuperSU. Took me a few tries.
This is the guide I used from the forum:
SuperSU Me_6.4.apk
KingRootSetup v3.2.0.1129.exe
1. install kingrootsetup on pc(must have internet connection to work)
2. connect ur phone with ADB enabled from developers option
3. root ur phone by following on screen instructions...
4. after rooting,install supersume on phone
5.open the app,click on big blue button and wait...
done,replaced kingroot with supersu..
-Mario
Click to expand...
Click to collapse
Hey I used this app to remove king root and my phone bricked do you know how to fix?
ipodhero said:
Hey I used this app to remove king root and my phone bricked do you know how to fix?
Click to expand...
Click to collapse
My Alcatel Ideal 4060A froze a few times during the removal of KingRoot, but all I did was: turn off the phone, remove the battery, and finish the procedure once the phone was on. The phone was only $10 on Black Friday, so you could say it was only an experiment on my part. Unless it's a really good phone, where you can go to the manufacture's website and download the original firmware and install it through your PC, there's not much you can do to unbrick a cheap phone that is practically unknown.
Merazomo said:
Mario
Click to expand...
Click to collapse
Thank you Mario for your help! I'm having a little trouble having my phone being recognized by Kingroot, although I have ADB enabled from the developers option, it seems not to pickup my phone still. I'm still trying though and I'll let you know if I get it to work properly, and perhaps document my mistake so others following this post who happen to have the same problem could know what to do.
- Jessy
*UPDATE*
Just wanted to update that I found out what was my mistake, which is a really simple and basic mistake, I apologize!
What I did was that after I had enabled ADB through my phone, it was already connected to my PC right after I had downloaded Kingroot, so my solution here was simple. I turned off my phone first, then I turned it back on while still connected with Kingroot still running then Kingroot finally read my phone and it rooted it as you outlined. Thanks again for your help, it is too valuable for me!
Here's the guide that I'm following so that I could install more apps to the phone through my 64 GB SD card if you guys were interested, to make the phone more useful, and I also installed my obama phone SIM card on it as well (from lifeline wireless, because hey why not? )
Here's the link to add more internal memory to this phone
www
.howtogeek.
com/114667/how-to-install-android-apps-to-the-sd-card-by-default-move-almost-any-app-to-the-sd-card/
shushi_boi said:
Thank you Mario for your help! I'm having a little trouble having my phone being recognized by Kingroot, although I have ADB enabled from the developers option, it seems not to pickup my phone still. I'm still trying though and I'll let you know if I get it to work properly, and perhaps document my mistake so others following this post who happen to have the same problem could know what to do.
- Jessy
*UPDATE*
Just wanted to update that I found out what was my mistake, which is a really simple and basic mistake, I apologize!
What I did was that after I had enabled ADB through my phone, it was already connected to my PC right after I had downloaded Kingroot, so my solution here was simple. I turned off my phone first, then I turned it back on while still connected with Kingroot still running then Kingroot finally read my phone and it rooted it as you outlined. Thanks again for your help, it is too valuable for me!
Here's the guide that I'm following so that I could install more apps to the phone through my 64 GB SD card if you guys were interested, to make the phone more useful, and I also installed my obama phone SIM card on it as well (from lifeline wireless, because hey why not? )
Here's the link to add more internal memory to this phone
www
.howtogeek.
com/114667/how-to-install-android-apps-to-the-sd-card-by-default-move-almost-any-app-to-the-sd-card/
Click to expand...
Click to collapse
No problem. I'm glad you got the phone rooted. I originally picked up the phone to use as an MP3 player, so I removed most of the unnecessary stock apps with "System app remover (ROOT)", but now that I see how good the phone is (at that price), I plan to use it as a backup phone. It even has a notification LED light for unopened messages LOL; anyway, good luck.
My Alcatel bricked too using this method stuck at boot logo and does nothing... Any fix?
Thanks for writing rooting method for Alcatel 4060a Ideal Pop445. Need some help
Merazomo said:
I picked one up on Black Friday, and decided to root it. I was only able to install an older version of SuperSU though (v2.46). First I had to install the PC version of KingRoot (It's in Chinese I believe, but middle button is always "next" or "yes"), root the phone, and then replace KingRoot with SuperSU. Took me a few tries.
This is the guide I used from the forum:
SuperSU Me_6.4.apk
KingRootSetup v3.2.0.1129.exe
1. install kingrootsetup on pc(must have internet connection to work)
2. connect ur phone with ADB enabled from developers option
3. root ur phone by following on screen instructions...
4. after rooting,install supersume on phone
5.open the app,click on big blue button and wait...
done,replaced kingroot with supersu..
-Mario
Click to expand...
Click to collapse
I've been an iPhone user for many years, I'm almost new to android. I have unlocked the bootloader from the hidden developers options in the settings app. I haven't found any thing useful to root my new Alcatel Ideal 4060a (Pop 445) (at&t unlocked). There are tons of bloatwares and many apps that I can't transfer to sd card. I hope you two can help me out here as I don't want to brick my device.
Question 1: Do jessy did something wrong(regarding your given steps to root) that makes her device rooted OR she has just been lucky? Because someone just posted that he/she has bricked his/her device.
Should I go ahead and try my luck with your method you there would be some advice you would like to give?
Question 2: If I would be able to root this device, would I be able to install Android 6.0 Marshmellow?
Don't root this yet
Source thread:
http://forum.xda-developers.com/android/help/alcatel-ideal-4060a-bootloader-custom-t3476422/
c627627 said:
Same answer ValdamarlSaCOCK was given, goes to you too, feel free to ask any questions:
http://forum.xda-developers.com/devdb/project/dl/?id=21707
Click to expand...
Click to collapse
Rooted already.
faxanidu said:
Don't root this yet
Click to expand...
Click to collapse
I have rooted with Kingroot 5; latest windows version on their website. Now I'm working on replacing it with Supersu or Supersu-me.
I think there always be some solution as far as you are seeing something on your phone's screen.
Just a note from another user with an Alcatel Ideal 4060a... (got for $10 from Best Buy on Black Friday)
Don't try using King-O-Root, then proceed to install Super SU from Google Play. It works that first launch, but on rebooting...
It's permanently bricked. And yes, I tried everything, including adb, recovery (doesn't have an option to flash a rom), from-pc flashing (wouldn't connect/wasn't recognized by adb or the other tools), fastboot (wouldn't launch), etc.
I don't know about the alternate Kingroot app, though. That probably works as some people have said it does for this model.
I was stupid and assumed King-O-Root would work as well, since it seems pretty generic and worked for another phone. I've learned my lesson and will now only follow guides for the specific phone model I have.
Why am I even writing this if it's a different rooting app? Cause I spent 6 hours just to end up killing one of my phones, and this is my best attempt at feeling like there was some worth to the waste. (the chance of preventing someone else the misfortunate, and just ranting)
Anyway, I'm going to bed. (So annoying because I only barely was brash enough to go ahead without a phone-specific guide--was on the fence, but landed on the unfortunate side) Argh! Argh! Argh!
Venryx said:
Just a note from another user with an Alcatel Ideal 4060a... (got for $10 from Best Buy on Black Friday)
Don't try using King-O-Root, then proceed to install Super SU from Google Play. It works that first launch, but on rebooting...
It's permanently bricked. And yes, I tried everything, including adb, recovery (doesn't have an option to flash a rom), from-pc flashing (wouldn't connect/wasn't recognized by adb or the other tools), fastboot (wouldn't launch), etc.
I don't know about the alternate Kingroot app, though. That probably works as some people have said it does for this model.
I was stupid and assumed King-O-Root would work as well, since it seems pretty generic and worked for another phone. I've learned my lesson and will now only follow guides for the specific phone model I have.
Why am I even writing this if it's a different rooting app? Cause I spent 6 hours just to end up killing one of my phones, and this is my best attempt at feeling like there was some worth to the waste. (the chance of preventing someone else the misfortunate, and just ranting)
Anyway, I'm going to bed. (So annoying because I only barely was brash enough to go ahead without a phone-specific guide--was on the fence, but landed on the unfortunate side) Argh! Argh! Argh!
Click to expand...
Click to collapse
Any solution for this? I want to replace King-O-Root with Super SU.
None that I know of.
I have another Android phone that I was also trying to get root on, and that one gets it temporarily using King-O-Root as well, but I'm too paranoid to try to make it permanent on that second one. Losing both my Android phones would be too painful.
If anything, I guess try the KingRoot program, from the pc, and then use the "SuperSU Me" app, as the person on the first page of this thread described. That way worked for at least one person apparently. (though the poster just after said it bricked theirs, so beware)
By the way, is your root from King-O-Root temporary (till restart) or permanent? I installed Super SU during the same launch I used King-O-Root, so I never got to see whether King-O-Root itself would have worked as a permanent (though non-ideal) solution. (I know that on my other Android phone it's temporary)
King-O-Root = Bricked Phone
KingRoot5 = Root Successful + it is possible to replace with SuperSU
http://forum.xda-developers.com/devdb/project/dl/?id=21707
Recovery Retrieved!
I was able to pull the recovery from this phone. Can someone make TWRP for this device using the stock recovery?
Here is the actual recovery image file that I pulled:
(Forgot my old XDA password, had to make another account. Can't post links)
https://drive.google.com/file/d/0B9sabhOnOJ42eXg3Vzlxd1liamc/view?usp=sharing"]https://drive.google.com/file/d/0B9sabhOnOJ42eXg3Vzlxd1liamc/view?usp=sharing
Ch3if-0f-Skull5 said:
I was able to pull the recovery from this phone. Can someone make TWRP for this device using the stock recovery?
Here is the actual recovery image file that I pulled:
(Forgot my old XDA password, had to make another account. Can't post links)
https://drive.google.com/file/d/0B9sabhOnOJ42eXg3Vzlxd1liamc/view?usp=sharing"]https://drive.google.com/file/d/0B9sabhOnOJ42eXg3Vzlxd1liamc/view?usp=sharing
Click to expand...
Click to collapse
Did you manage to unlock the bootloader? If not then you cant flash anything and building twrp would be useless.
arolust said:
Did you manage to unlock the bootloader? If not then you cant flash anything and building twrp would be useless.
Click to expand...
Click to collapse
I pulled the boot file. Could someone maybe look at that? I cannot boot to the bootloader.
I could try to flash_image twrp to the recovery and try that.
I got this phone on black friday, shortly after I got root with kingroot 5 pc and it was all great, however I got greedy and replaced kingoroot with supersu :silly:. First reboot and it goes into boot loop. Now its been sitting in a drawer. I think that purify deleted some app it looks at boot.
It looks like the simplest way to get a restore is 'IF' TCL/Alcatel does an update, someone intercepts the signed zip file, then that zip file could be distributed and used with the stock restore.
Hopeful everyone here can work a better solution... thanks for all your hard work everyone.
yes u r right
many time happen with me, Happen with me on asus KA10, But i got fastboot update img lucky. hope that u will get Fast boot image some day or we may able to get recovery for this device . in that case your your phone may start working
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
the core question "How to unlock Alcatel Ideal 4060A (walmart) Bootloader?" still unanswered. Kindly help.
My phone is rooted, but not able to unlock bootloader so far ...
I recently purchased an RCA Voyager III model RCT6973W43 and I've noticed no one has said anything about how to root this one yet. I've heard of users who have had success with rooting the original Voyager and Voyager IIs, but there's nothing on the Voyager III. I think it's possible that the same procedure for rooting those devices might work for the Voyager III, but I don't want to take any chances in case it bricks mine. So is there a whole different procedure with my particular device? Or is the Voyager III simply too new?
Bump
RobinHood16 said:
I recently purchased an RCA Voyager III model RCT6973W43 and I've noticed no one has said anything about how to root this one yet. I've heard of users who have had success with rooting the original Voyager and Voyager IIs, but there's nothing on the Voyager III. I think it's possible that the same procedure for rooting those devices might work for the Voyager III, but I don't want to take any chances in case it bricks mine. So is there a whole different procedure with my particular device? Or is the Voyager III simply too new?
Click to expand...
Click to collapse
Bump!
Yes please!
I tried RCA to see if they would at least update the tablet and turn on the FM receiver. They claim it doesn't have it. I'm pretty sure it has both the FM and a GPS receiver built in. I think I also found a "clone", the DigiLand DL721-RB appears to be the same hardware.
What I'm trying to do is simply enable all the features the hardware has. The Atom x3 is supposed to have pretty much all the standard stuff, my RCA RCT6973w43 (on sale at Walmart right now for $37) does OTG nicely, but if I had the FM also it would be perfect for a tablet based car stereo. If anyone figures it out and can get the FM and or GPS going, I'd be tickled.
I just bought a couple of these for 25 bucks. I would very much like to get them rooted. Any news on if the method for the other Rca's works?
No good. I attempted to root the Voyager III with One Click Root, and it told me it was unrootable for the time being.
Any clues yet?? everyone owns this tablet figured there'd be a root already for this one.
i read where someone tried to root the 43 using 42, and it bricked the tablet, so i'm reluctant to try it. don't know if the 42 and the 43 had the same processor, or what makes them so different it would cause that to happen. maybe we can get a bump.
keep finding tons of people looking for root, but not dice so far. i've only got one cuz they were sold out. actually bought the display model. wish i had more than one so i could experiment. 8(
I'd been able to install twrm halfway then it fails signature verification.
Just got one of these! Bump
yes bump!!!! I can't believe this hasn't been rooted yet. is it because it's an intel x86 architecture?? I'm guessing it would require someone to compile the code for sudo/su/root to run on it??
anything yet?? 8(
---------- Post added at 02:04 AM ---------- Previous post was at 01:39 AM ----------
just as a quick notei found this guys.
http://specdevice.com/showspec.php?id=7920-d3ef-0033-c5870033c587
it's an alco tablet with the same model # as the voyager 3 RCT6973W43.
weird thing is it appears to have a quadcore arm processor, and not an intel atom.
i heard there was a root for the alco from twitter profile @srsrOOT, but they haven't responded yet.
no clue if this will help at all. I would imagine if the alco has an arm proc, and the rca has an intel then we'd need a different su/sudo binary for the RCA because the RCA runs on a CISC processor, and the ARM is a RISC. hope there's some clues here. hit us back with any info you find. 8(
look here
bump
Thought Id try bumping this. Sorry itll prolly be gone soon.
This tablet is begging for a root. I did a bunch of adb uninstalling and got rid of google play stuff. Battery is MUCH better. I suppose a custom rom would immensely improve battery.
TimmyP said:
Thought Id try bumping this. Sorry itll prolly be gone soon.
This tablet is begging for a root. I did a bunch of adb uninstalling and got rid of google play stuff. Battery is MUCH better. I suppose a custom rom would immensely improve battery.
Click to expand...
Click to collapse
Did you guys unlock the boot loader yet?
Code:
adb reboot fastboot
fastboot flashing unlock
If so, you can try and boot the cwm recovery I use on mine(RTC6873W42) to get a root shell. (if the kernel drivers were the same it would actually be full recovery enviroment) And with that root shell you could pull your boot.img . The expected result of the fastboot boot command is an attempted boot to cwm recovery except the screen will be blank, and adb will give root shell access.
Code:
fastboot boot v31-test-rca-recovery-cwm-ramdisk-20170709-2052.img
https://www.androidfilehost.com/?fid=961840155545581102
And with the pulled boot.img you can make the recovery fully boot by swapping the kernel, then manually change some rc files in the ramdisk folder of the boot.img the allow it to be rooted.
When you get that far, and if you need help, just ask.
This doesn't work with an RCT6973W43, I'm afraid. I get the blank screen from "adb reboot fastboot", as is apparently expected, but while the RCT6973W43 is in this mode, Windows doesn't recognize the device at all, as there are no drivers available. Also, it keeps disconnecting and reconnecting, so that "fastboot flashing unlock" can't get a fix on the device -- it's stuck on "< waiting for any device >" forever, and can only be stopped with Ctrl-C. Otherwise, the only way to restore the device to working order is a hard restart.
RobinHood16 said:
This doesn't work with an RCT6973W43, I'm afraid. I get the blank screen from "adb reboot fastboot", as is apparently expected, but while the RCT6973W43 is in this mode, Windows doesn't recognize the device at all, as there are no drivers available. Also, it keeps disconnecting and reconnecting, so that "fastboot flashing unlock" can't get a fix on the device -- it's stuck on "< waiting for any device >" forever, and can only be stopped with Ctrl-C. Otherwise, the only way to restore the device to working order is a hard restart.
Click to expand...
Click to collapse
That connect disconnect is expected when Intel drivers for fastboot not installed. I will link you to my write up on how to install
https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt
Read the document and follow directions in the driver install section. If trouble let me know
Neither of these builds works for me. My build number is RCT6973W43-ANDROID6.0-V16-V1.18.0-M01. Also, even if I could find the correct files, the Intel drivers don't work with my device.
RobinHood16 said:
Neither of these builds works for me. My build number is RCT6973W43-ANDROID6.0-V16-V1.18.0-M01. Also, even if I could find the correct files, the Intel drivers don't work with my device.
Click to expand...
Click to collapse
Sorry this is giving you such trouble,
but if you cant get the drivers to work, then you hae no way to know if these files will not work on your device.
If you are refering to the "tools" then, yes they will not work, as I coded them to not work if build numbers are not matched. But I never suggested tring the "tools". just the unlock and "fastboot boot" steps
again , If you cant get windows drivers to install then , thats as far as you can go.
I had a pictoral 'guide' for doing it, but cant find it right now.
In that case, my only recourse is to give up. It seems to me that they have made this tablet absolutely unrootable.
i managed to unlock bootloader
i used the method here https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt to unlock boot loader only difference is the fastboot screen flashes just input unlock command and keep taping up it works dont really know where to go from here
seasonednovice said:
i used the method here https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt to unlock boot loader only difference is the fastboot screen flashes just input unlock command and keep taping up it works dont really know where to go from here
Click to expand...
Click to collapse
Did you attempt my directions at the end . To boot the modified cwm , to get adb root shell?
Since there is a possibility to connect the Moto 360 2nd via USB, I bought myself a broken watch, opened the back and soldered the USB wires.
Fastboot recognized the Watch and since I am not that familiar with android flashing I thought unlocking the bootloader would be a good idea (don't ask me why - I don't know).
Now the watch is not booting normally, neither into recovery. But fastboot mode works so far...
I think I remembered that I saw a link to firmware files in the internet a few month ago and I am trying to find it for the last 2 days but no results yet.
Has someone an idea where I can find this files? I mean they are still providing updates for outdated Motos so the files should be online somewhere or am I wrong?
Or can I flash any watch recovery to my watch?
If someone wants a solderless USB possibility I may have an Idea btw but you still have to pull the plastic ring around the backside.
I think I forgot to mention that the plan is to downgrade my daily watch back to AW1.5 or 1.6
cheers
Hello,
I just found the OTA file (version: NXH19Q) for motorola 360 2nd gen on this reddit post.
I hope it works for you.
My motorola doesn't work properly either and its stuck on boot animation.
Hi,
thanks but actually I found this link myselfe and was unable to flash it because of the stock recovery.
I got rid of the bootloop by wiping data and cache two times after unlocking the bootloader.
Cheers
Rezoran
I'll try unlocking the bootloader, i've just made the usb cable.
Thanks
Hello,
I am trying too to downgrade my Moto 360 2nd gen (42mm) to AW 1.5 or 1.6. However, I have not found any "trusted" place to download the firmware images for those versions of Android Wear.
Also, in the reddit post mentioned by danger_tweaker, the author states that the firmware image can't be sideloaded to our devices...
I found this repository: [search on Google for "rootjunkysdl moto 360 2nd gen", I am not allowed to post links since I have just registered]
It contains some images labelled with the devices' codenames (I think that the 42mm version is "carp" and the 46mm is "smelt", I have no idea what the "bowfin" is), but I am not sure about how to proceed... I am afraid of bricking my watch.
In the meanwhile, have you made any progress?
Thank you
I have a LG K7 that will boot to system, but no matter how many times I try, it wont boot into either download mode or recovery mode. I've tried the combos of vol down + power and vol up + power and every other combination I can think of. Pulled the battery and it didn't improve.
Anybody ever see something like this? Any suggestions on how to get it to work?
BigZ1 said:
I have a LG K7 that will boot to system, but no matter how many times I try, it wont boot into either download mode or recovery mode. I've tried the combos of vol down + power and vol up + power and every other combination I can think of. Pulled the battery and it didn't improve.
Anybody ever see something like this? Any suggestions on how to get it to work?
Click to expand...
Click to collapse
Tried ADB commands?
adb reboot recovery
adb reboot bootloader
bmwdroid said:
Tried ADB commands?
adb reboot recovery
adb reboot bootloader
Click to expand...
Click to collapse
Yes, and adb devices shows nothing. I'm wondering if the bootloader is locked and maybe that's why I'm having problems.
Also, I'm having problems getting TWRP to load. Do you know what version of TWRP will work with K7?
Do you have to root first before installing TWRP from the playstore?
BigZ1 said:
Yes, and adb devices shows nothing. I'm wondering if the bootloader is locked and maybe that's why I'm having problems.
Click to expand...
Click to collapse
If "adb devices" shows nothing imo it's not recognised so not possible to flash.
Tried other cable/port?
BigZ1 said:
Also, I'm having problems getting TWRP to load. Do you know what version of TWRP will work with K7?
Click to expand...
Click to collapse
No idea as I own a G5.
BigZ1 said:
Do you have to root first before installing TWRP from the playstore?
Click to expand...
Click to collapse
Never did that.
Always flashed directly but I guess so.
bmwdroid said:
If "adb devices" shows nothing imo it's not recognised so not possible to flash.
Tried other cable/port?
No idea as I own a G5.
Never did that.
Always flashed directly but I guess so.
Click to expand...
Click to collapse
tried another cable and different port. Status Quo!
Any other ideas/thoughts?
@BigZ1 sorry, none.
OK, finally can get into firmware mode and also recovery mode. Reason I needed this is to be able to try loading custom roms on this old phone. Now I'm on to the next pothole in the road.
I would like to install twrp. twrp from the playstore wont install unless you are rooted. I am using stock rom android 5 unrooted. I've looked at all the options and from what I see, I have the classic chicken and the egg dilema. Can't flash until my OS is rooted, and cant root without flashing.
The only way out is to use adb to flash the twrp file. Unfortunately I can't get adb devices command to acknowledge any devices. I have usb debugging on, and by connecting to a windows computer, I can view internal storage. So the device is communicating, but not via adb commands.
I tried to use the LGUP tool from LG, but it wont let me select my device, It sees the correct model of phone on Com3, but wont let me select the model. I think it's because LG has turned off their servers and cast us adrift.
If anybody has any ideas, it would be much appreciated.
I think my best bet is to get adb devices to work, or find a way to root my OS. I just cant figure out how to make that work. Help, please!!!!
BTW, in the stock recovry mode, LG has removed everything useful (e.g. install zip, reboot options, wipe cache, etc.) so the only option there is factory data reset. Thanks a lot LG!!!!!
BigZ1 said:
....The only way out is to use adb to flash the twrp file........
Click to expand...
Click to collapse
Sorry to tell you but afaik this won't work.
fastboot flash recovery <filename.img> would be the command but this will only work if it's unlocked.
BigZ1 said:
....Unfortunately I can't get adb devices command to acknowledge any devices. ......
Click to expand...
Click to collapse
I doubt that fastboot will work if adb isn't but it's worth a try.
You are right, a fastboot command would do it. Only reason I mentioned adb devices, is that if adb can't see the devices, fastboot wont either. I'll try it again, but so far no luck.
What I don't understand is why usb debugging lets me look at the internal files, but adb devices doesn't work. Perhaps you are right, the bootloader may be locked. Only thing I could find about that is in developer options I turned on OEM unlock.
Is there any other way to unlock the bootloader?
Sure wish I could get some of the LG tools working. They might enable flashing of twrp recovery or one of the various zip files that would root my OS.
Any more ideas? I'm desperate enough to try most anything....
One more question. When you try to execute adb or fastboot commands, should you be in what LG calls "firmware download" mode? Seems to me that when I did adb or fastboot commands on other vendors phones, I was able to do so while the OS was running.
Grasping for straws....
Well, it looks like you are right. There is a fastboot command
fastboot oem unlock
that would unlock the bootloader. Unfortunately while it's locked, I can't get fastboot to recognize any devices, so I can't unlock it.
Is there any way around this?
BigZ1 said:
Well, it looks like you are right. There is a fastboot command
fastboot oem unlock
that would unlock the bootloader. Unfortunately while it's locked, I can't get fastboot to recognize any devices, so I can't unlock it.
Is there any way around this?
Click to expand...
Click to collapse
Fastboot is afaik only working in download/bootloader mode.
ADB working on any other.
So <adb reboot bootloader > usually gets you there (but adb doesn't work) or switch to it manually.
Idk if you need to flash an unlock.bin by LG.
Got it before 31.12.21 for my G5.
bmwdroid said:
Fastboot is afaik only working in download/bootloader mode.
ADB working on any other.
So <adb reboot bootloader > usually gets you there (but adb doesn't work) or switch to it manually.
Idk if you need to flash an unlock.bin by LG.
Got it before 31.12.21 for my G5.
Click to expand...
Click to collapse
Yeah, I just discovered that LG discontinued support on Dec 31, 2021. So, looks like I'm out of luck for getting anything from them.
My only hope is that someone has that lockbin file and would share it. Sure wish LG hadn't left me high and dry.
Now that LG support is gone, is there any forum that might have some kind of workaround for the bootloader?
anybody got a lockbin file for K7????
BigZ1 said:
Yeah, I just discovered that LG discontinued support on Dec 31, 2021. So, looks like I'm out of luck for getting anything from them.
My only hope is that someone has that lockbin file and would share it. Sure wish LG hadn't left me high and dry.
Now that LG support is gone, is there any forum that might have some kind of workaround for the bootloader?
anybody got a lockbin file for K7????
Click to expand...
Click to collapse
Oh yeah, one more thing. The phone is still of some use to me, if I can find a way to root it. So far all the stuff I tried (kingoroot, supersu, magisk) have failed.
Anybody got any suggestions???
BigZ1 said:
Yeah, I just discovered that LG discontinued support on Dec 31, 2021. So, looks like I'm out of luck for getting anything from them.
My only hope is that someone has that lockbin file and would share it. Sure wish LG hadn't left me high and dry.
Now that LG support is gone, is there any forum that might have some kind of workaround for the bootloader?
anybody got a lockbin file for K7????
Click to expand...
Click to collapse
The file got generated by LG after I entered a long code on their developers site which is afaik different for each device.
So someone elses unlock.bin might even harm your device.
You may be right, but at this point I don't have much to lose.
One thing I would like to do with the K7, is get it rooted. I can move files to the internal storage with usb debugging. I can't install any zip files and that makes it really difficult to find anything that can root it. Thanks again to LG for reducing the recovery menu to "factory reset data" so the phone has almost nothing useful.
If you can figure out a way that I can install zip files, please let me know.
I can't find anything that will let me flash the device without root, and I can;t get to root without some tools in the recovery menu.
Thanks
OK, I have not found a way to root. So I thought I'd take one last look at flashing/upating the firmware. I found a .kdz and a .tot file that I'd like to try. At this point I'm not risking much because the phone isn't worth much to me as is.
So, if you had a .kdz and .tot file to try out, what app would you use to flash it to the K7?
I tried to get LGUP to work and LG flash tool, but cant seem to make them work. If I knew what one to use, it would narrow my search. I'm trying to flash the K7 firmware by running exe files (LG UP, LG flash tool) on Windows 10.
What do you guys use?
BigZ1 said:
OK, I have not found a way to root. So I thought I'd take one last look at flashing/upating the firmware. I found a .kdz and a .tot file that I'd like to try. At this point I'm not risking much because the phone isn't worth much to me as is.
So, if you had a .kdz and .tot file to try out, what app would you use to flash it to the K7?
I tried to get LGUP to work and LG flash tool, but cant seem to make them work. If I knew what one to use, it would narrow my search. I'm trying to flash the K7 firmware by running exe files (LG UP, LG flash tool) on Windows 10.
What do you guys use?
Click to expand...
Click to collapse
So, I managed to find a patched version of LG flash tool (2.0.1.6) on this website (thanks to member ieatacid), that doesn't give me errors immediately after I open it. The first thing I notice is that it doesn't appear to recognize the K7. If I try checking the box for manual mode and adding the file I want to flash, the click start, it tells me to "select model dll file". This is probably a result of flash tool not recognizing the phone. Anyway, where am I supposed to find this .dll file? I've searched everywhere and came up empty handed.
Can anybody give me some enlightenment on what I am doing wrong? Any help at all will be much appreciated.
Is there a tutorial on use of the flash tool? I looked but haven't found it yet. Just some youtube videos that are terse and lacking in detail.
Thanks!
BigZ1 said:
So, I managed to find a patched version of LG flash tool (2.0.1.6) on this website (thanks to member ieatacid), that doesn't give me errors immediately after I open it. The first thing I notice is that it doesn't appear to recognize the K7. If I try checking the box for manual mode and adding the file I want to flash, the click start, it tells me to "select model dll file". This is probably a result of flash tool not recognizing the phone. Anyway, where am I supposed to find this .dll file? I've searched everywhere and came up empty handed.
Can anybody give me some enlightenment on what I am doing wrong? Any help at all will be much appreciated.
Is there a tutorial on use of the flash tool? I looked but haven't found it yet. Just some youtube videos that are terse and lacking in detail.
Thanks!
Click to expand...
Click to collapse
I don't know why I didn't think of this earlier. I own 3 LG phones (LGMS300m1, LM-X210ULMG10r. VS500PP9). I tried all 3 with LGUP tool. The tool recognized 2 of the 3, and failed to ID the LGMS300 (K7). Anybody got any ideas why the tool would recognize some but not others?
I am the only owner of the two phones that LGUP would ID. I guarantee that the bootloader on them was never touched (unlocked or locked, in any way). So that's not the answer.
It would be a big improvement for me, if I could at least get the LGUP tool to work for the K7.
BTW, I tried all 3 phones on the 2016 version of LG Flash Tool. All 3 failed to be identified.
Please, if anybody has a hypothesis for the odd behavior of the LGUP tool, I would love to hear it. Any suggestions are welcome.
BigZ1 said:
I don't know why I didn't think of this earlier. I own 3 LG phones (LGMS300m1, LM-X210ULMG10r. VS500PP9). I tried all 3 with LGUP tool. The tool recognized 2 of the 3, and failed to ID the LGMS300 (K7). Anybody got any ideas why the tool would recognize some but not others?
I am the only owner of the two phones that LGUP would ID. I guarantee that the bootloader on them was never touched (unlocked or locked, in any way). So that's not the answer.
It would be a big improvement for me, if I could at least get the LGUP tool to work for the K7.
BTW, I tried all 3 phones on the 2016 version of LG Flash Tool. All 3 failed to be identified.
Please, if anybody has a hypothesis for the odd behavior of the LGUP tool, I would love to hear it. Any suggestions are welcome.
Click to expand...
Click to collapse
Update on the never ending saga!
I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). I was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes i'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Words of wisdom, anyone?