Frist off I'm not Responsible for anything that happens to your phone!!!
I have made you guys a one click flash bat!
To Convert to the NA(Global) software
Super easy I tested this with my owen device
this has everything in file the you need to flash
latest OOS11 form op site
unlocking bootloader is on your own
Also coming form a experienced DEV!!
unlocking with out token can cause issue!!!
Steps!!
BL MUST BE UNLOCKED!!!!
POP SIM OUT OF DEVICES AND FACTORY RESET WITH NO SIM IN PHONE
KEEP SIM OUT THROW WHOLE PROCESS
RUN THROW SETUP
ENABLE DEBUGGIN
UNZIP MY FILE AN JUST RUN BAT FILE
SIT BACK AN LET IT DO ITS THING
ONCE DONE
CLICK REBOOT TO RECOVERY IN FASTBOOTD
RESET SETTING AND CACHE
REBOOT TAKE OTA THEN FACTORY RESET
BOOM!!!
If you have issue I recommend msm tool to stock
with out sim in phone and following the step after bootloader unlock
CONVERTER: FILE
wanna buy me a coffee
@FizzyAps
If a user had previously came up with the same scripts / set of commands, then even if you created your script independently, it's polite to at least acknowledge the other user's similar work.
@summersofar
I'd be very surprised if these forums didn't have a rule against personal attacks, and you've definitely crossed into those. I understand you're upset, but wouldn't it have been better to make a polite request via PM before starting public arguments?
I actually had a similar situation about 3 months ago, I had created a thread with links to tools another user had found, to make them easily findable, and I forgot to credit them. They sent me a polite PM, asking I take the thread down, along with a list of their reasoning, part of which was so they could post the info more publicly themselves. A quick message or two back and forth, and all that was seen publicly was my thread suddenly getting marked "delete me" with the contents changing to a link to the user who originally found the tools much more detailed thread for them. No pain, no fuss, no hard feelings on any side.
It never hurts to try the polite method first. Save the rudeness for if the polite approach doesn't work.
Are there any issues after converting?
Huliz said:
Are there any issues after converting?
Click to expand...
Click to collapse
no issues
edale1 said:
@FizzyAps
If a user had previously came up with the same scripts / set of commands, then even if you created your script independently, it's polite to at least acknowledge the other user's similar work.
@summersofar
I'd be very surprised if these forums didn't have a rule against personal attacks, and you've definitely crossed into those. I understand you're upset, but wouldn't it have been better to make a polite request via PM before starting public arguments?
I actually had a similar situation about 3 months ago, I had created a thread with links to tools another user had found, to make them easily findable, and I forgot to credit them. They sent me a polite PM, asking I take the thread down, along with a list of their reasoning, part of which was so they could post the info more publicly themselves. A quick message or two back and forth, and all that was seen publicly was my thread suddenly getting marked "delete me" with the contents changing to a link to the user who originally found the tools much more detailed thread for them. No pain, no fuss, no hard feelings on any side.
It never hurts to try the polite method first. Save the rudeness for if the polite approach doesn't work.
Click to expand...
Click to collapse
i agree
i actually did reach out to him for help he never answered so when i fixed the error with my own findings
i posted my Owen finding i posted this
Huliz said:
Are there any issues after converting?
Click to expand...
Click to collapse
no it its super easy
i have no issue even working on verzion
FizzyAps said:
no it its super easy
i have no issue even working on verzion
Click to expand...
Click to collapse
Roger that. I heard updates is pushed faster rather then carrier versions.
I'm not rooted took OTA just fine a
Actually, you can install full ROM if OTA doesn't work out
FizzyAps said:
Frist off I'm not Responsible for anything that happens to your phone!!!
I have made you guys a one click flash bat!
To Convert to the NA(Global) software
Super easy I tested this with my owen device
this has everything in file the you need to flash
latest OOS11 form op site
unlocking bootloader is on your own
Also coming form a experienced DEV!!
unlocking with out token can cause issue!!!
Steps!!
BL MUST BE UNLOCKED!!!!
POP SIM OUT OF DEVICES AND FACTORY RESET WITH NO SIM IN PHONE
KEEP SIM OUT THROW WHOLE PROCESS
RUN THROW SETUP
ENABLE DEBUGGIN
UNZIP MY FILE AN JUST RUN BAT FILE
SIT BACK AN LET IT DO ITS THING
ONCE DONE
CLICK REBOOT TO RECOVERY IN FASTBOOTD
RESET SETTING AND CACHE
REBOOT TAKE OTA THEN FACTORY RESET
BOOM!!!
If you have issue I recommend msm tool to stock
with out sim in phone and following the step after bootloader unlock
CONVERTER: FILE
wanna buy me a coffee
Click to expand...
Click to collapse
I will try it out this weekend
I'd prefer original OnePlus icons
[Thread Cleaned] Thoroughly cleaned, so it seems! I'm sorry this took a while but we're just people too and due to our personal lives it can sometimes take some time for us to step in. For those that experienced this, it was quite clear the conversation spiralled out of control (which was also clear in the amount of reports that poured in). We understand that a discussion can be heated when one really cares about the subject but please refrain from profanity and personal insults. It just doesn't help anyone. Never does.
I'd also like to underline the importance of attribution. It's not because something isn't original work that it's not work. People like acknowledgment for what they add to the community so it's the right thing to do. On XDA we usually demand it:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
read more...
Click to expand...
Click to collapse
On another note I'd like to add that we do not allow discussion on moderator decisions in the thread for obvious reasons. We are, however, more than willing to answer your questions via PM.
Thank you for your time and have an amazing – yet safe – day!
Timmy
Forum Moderator
@Timmmmaaahh!
Thank you and I as well apologize for my reactive behavior... This is a community full of help. So we will ALL continue to honor that... Fizzy is authentic and ground up.. All development is acknowledged where it needs to be, always
Nice. phone is stuck on the boot animation after using this, likely because the following commands failed:
Creating 'system_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed
Creating 'system_ext_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed
Creating 'product_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed
Creating 'vendor_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed
freeza said:
Nice. phone is stuck on the boot animation after using this, likely because the following commands failed:
Creating 'system_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed
Creating 'system_ext_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed
Creating 'product_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed
Creating 'vendor_a' FAILED (remote: 'Not enough space for partition')
fastboot: error: Command failed
Click to expand...
Click to collapse
Same experience BUT I got it to boot by going back into recovery & erasing data again.
Got it
junk0 said:
Same experience BUT I got it to boot by going back into recovery & erasing data again.
Click to expand...
Click to collapse
Same lol. Thanks for the tip
Does the phone stay carrier locked after this?
Anyone know if this works on the Walmart $99 black friday deal for Metro N200 5G? Thanks
Metro PCS n200 & it works just fine. Full flash, no errors as of yet. Thank you!
mingkee said:
I will try it out this weekend
I'd prefer original OnePlus icons
Click to expand...
Click to collapse
When flashing this bat file do I need to do it on bootloader mode?
Related
As Modaco's boot image "Superboot (for Nexus One)" got no more updates after Android build version GRI40 and we're on GRK39F for some time now; and even though the Superboot GRI40 version gave you root as desired (https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/), that Superboot version also caused some problems with wifi connection and had an outdated su binary, as well as an outdated Superuser.apk.
To cut a long story short, i did it on my own: Bexboot. A boot image - especially for Android GRK39F on passion devices. I compiled it (based on a guide by Modaco himself) from the stock GRK39F source of my own Nexus One. Also it includes the lates Superuser.apk (v3.0.5) and the latest su binary (v3.0).
Here you go: https://bexton.net/2011/10/12/bexboot-root-nexus-one-passion-grk39f/
Any feedback highly appreciated.
[UPDATE#1 08.11.2011]:
Please don't use v1 (link above) any longer. Instead use the Bexboot v2.0 (link below). It was rebuilt from a completely clean stock rom, what solves the compatibilty issues, some reported for v1. (Also it includes the latest Superuser.apk (3.0.6), as well as the latest su binary (3.0.3).)
https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
[UPDATE#2 11.12.2011]:
As i forgot to pay the invoice for the server where my blog is running on, it is offline since yesterday. :/ Anyway, i uploaded a copy of the zip archive containing all files you need to root your device to http://www.nahklick.de/user/stephan/bexboot.v2.GRK39F_OTA.zip. To get the instructions, follow this link http://www.google.com/search?q="bexboot"+version+2 and use the Google cache to view the original site. Thx
[UPDATE#3 20.02.2012]:
Files and instructions mirrored at request: http://code.google.com/p/bexboot/
i've posted this on my blog aswell. Nice work
http://patrick.oberdorf.net/2011/10/12/nexus-one-root-rechte-mit-stock-rom/
I've tried that, it does not work.
The fastboot utility says:
downloading 'boot.img'... OKAY
booting... OKAY
Then the phone reboots still not rooted.
zc2 said:
I've tried that, it does not work.
The fastboot utility says:
downloading 'boot.img'... OKAY
booting... OKAY
Then the phone reboots still not rooted.
Click to expand...
Click to collapse
Hi zc2,
sorry for the long response time, i was on a business trip and didn't had the time to check in. I received a bunch of similar issue reports so i did a factory reset and rebuilt the bootloader from a completely clean stock rom.
First comments confirm that it now also works for persons, that had the same issue like you with v1. So if you're still interested in it, check out the updated release version: https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
Hi Bexton, thank you for the response. I actually was able to root my phone using the instructions from the following post:
http://forum.xda-developers.com/showpost.php?p=18527514&postcount=1853
V2 Failed for me
Bexton said:
...use the Bexboot v2.0 (link below)....
Click to expand...
Click to collapse
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
goattee said:
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
Click to expand...
Click to collapse
Have you seen this comment / my answer: https://bexton.net/2011/11/07/bexbo...or-nexus-one-with-android-grk39f/#comment-179 ?
It is much likely due to an issue with your hboot version. Your provider probably pushed a locked SPL in an update that renders fastboot unusable. Maybe the link in my comment can help!? Let me know..
Greetz
Thanks for such a fast reply. I bought the phone in Bangkok. It was a "grey market" item from the Hong Kong market. I am not sure whether my Thai carrier even bothers with such things.
I looked at the link but unfortunately for me, I have only the most primitive understanding of how to deal with the bootloader, etc. So I can't even grasp what aspects of that thread apply to me. I really need step-by-step instructions. So unless I can find someone with more mastery, I guess I will only dream of Cyanogen Mod on my phone.
goattee said:
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
Click to expand...
Click to collapse
Bexton said:
Have you seen this comment / my answer: https://bexton.net/2011/11/07/bexbo...or-nexus-one-with-android-grk39f/#comment-179 ?
It is much likely due to an issue with your hboot version. Your provider probably pushed a locked SPL in an update that renders fastboot unusable. Maybe the link in my comment can help!? Let me know..
Greetz
Click to expand...
Click to collapse
You will get that error if you are trying to use fastboot commands without first having unlocked your bootloader.
That error has nothing to do with the HBOOT version on Nexus One's. You cannot "push" a locked SPL to an N1 if you've already unlocked your bootloader. The bootloader unlock flag is set in the radio NV memory, so once you have unlocked the bootloader, you cannot relock it (unless you have S-OFF), even if you reflash another stock hboot.
efrant said:
You will get that error if you are trying to use fastboot commands without first having unlocked your bootloader.
That error has nothing to do with the HBOOT version on Nexus One's. You cannot "push" a locked SPL to an N1 if you've already unlocked your bootloader. The bootloader unlock flag is set in the radio NV memory, so once you have unlocked the bootloader, you cannot relock it (unless you have S-OFF), even if you reflash another stock hboot.
Click to expand...
Click to collapse
I realize you're trying to clarify. But I don't understand any of the terminology. The only thing I am capable of is following a prescribed procedure. I thought this procedure was going to unlock and root the phone. I guess I was wrong.
I don't have the diagnostic skills to change direction if things don't go in a predictable fashion-- I've only used stock devices up until now and this was my first attempt. I guess the best I can hope for is to make contact with someone more experienced when I am next in the US and have that person assist me. It makes it more difficult because most of what I am finding online is either old (pre-Gingerbread) or it assumes the user has hacked their Nexus One in the past and just needs to bring it up to date.
My goal is to get past the memory problems I am having by installing a custom ROM with a minimal set of apps in phone memory-- and more customizability.
nice man! It worked on the first go! Top job!
I have one question though! Is it safe to flash Clockword Mod recovery and then flash custom ROMs, or will it end in not finding the recovery image as is the case with other efforts to root 2.3.6?
Thanks!
davelis828 said:
nice man! It worked on the first go! Top job!
I have one question though! Is it safe to flash Clockword Mod recovery and then flash custom ROMs, or will it end in not finding the recovery image as is the case with other efforts to root 2.3.6?
Thanks!
Click to expand...
Click to collapse
No prob. You can use: https://bexton.net/android/n1/recoveries/recovery-clockwork-5.0.2.0-passion.img
If needed, here's the full stock GRK39F: https://bexton.net/android/n1/sys/grk39f/ota.zip and here the update: https://bexton.net/android/n1/sys/grk39f/d323ca384aaa.signed-passion-GRK39F-from-GRJ22.d323ca38.zip
o thanx ma! i appreciate your feedback, you did it on both sites aswell
Respect!
Mirror created at request: http://code.google.com/p/bexboot/
I gave superoneclick a go before trying this method. It worked flawlessly.
Sent from my Nexus One using Vodka
Source code availability?
Hi Bexton,
first of all, thanks for your work!
Next, I'd like to replace the Superuser app by Koush' one (https://github.com/koush/Superuser/).
Would it be possible to get the source code of bexboot?
None is available at http://code.google.com/p/bexboot/source/checkout...
Regards,
Patrick.
Please note, this is not compatible with the JB OTA - use the app in the Play store instead for now. Thanks!
Howdy all! So, it's time for me to dig out my release thread template... you know what that means?
The LG Optimus G is now unlocked.
Both the AT&T Version and the Sprint Version have been successfully unlocked with this method.
(To answer your question, if you're wondering, we're going to work on the Canadian version next, then the Korean version)
First off, I'd like to write a few words to LG:
Dear LG, a product will rise and fall on the shoulders of it's community.
If you lock a device, and shut out your community, you lose the backing of a very vocal group of people. When you lose the backing of your community, they no longer recommend your product, and you lose money. HTC has discovered this recently.
Please support your development community, we understand product security plays a role here, but ensure that you cater to your community still.
The second you try to fight your development community by locking them out of your products is the second that I will cease to recommend your products.
Keep this in mind, and I assure you that you will find yourself on the top of the game.
With all of that said, let's get back to the goodies.
What is this?!
This is Project FreeGee, silly!
Have an Optimus G ? This project will allow you to unlock your bootloader, and install whatever you want.
Click to expand...
Click to collapse
How does this work?
For the moment, that is a trade secret. Suffice it to say that we put some ones and zeros in the right places, and good things happen.
This is also my opportunity to say do not allow any OTAs to install without asking if they are compatible. LG could possibly patch this in such a manner that makes it rather hard to ever exploit it again.
Click to expand...
Click to collapse
I'm a skeptic. I demand proof!
Alrighty, here it is:
Once again, taken with my HTC Vivid, that would rather mute me than let me speak.
Damn "nose elimination"! I am not noise, and I will not be silenced! (mmhmhmhpmhmp!!)
Click to expand...
Click to collapse
Okay, I'm game. Where do I get it?
Version 0.3 has a confirmed bug-- camera app crashes phone after a few seconds!
If you have 0.3 installed, simply download this, extract the .zip, and extract the .tar file. Inside the freegee-working directory, you'll find boot-att-freegee.img .
Boot your phone to fastboot, then fastboot flash boot /path/to/boot-att-freegee.img
I will release a quick fix .zip for flashing in CWM tomorrow.
Current Version: 0.5
Changelog:
New in v0.5 Removed LG Security check. You are now free to remove any and all apps.
http://downloads.codefi.re/thecubed/lgoptimusg/att/freegee/FreeGee-0.5_ATT.zip
Currently, the download is Windows-only. I will make a OSX/Linux/Windows version soon!
Click to expand...
Click to collapse
FAQ
Can I flash an OTA after installing this?
No. Flashing an OTA could contain a new bootloader, and it would replace the one we have put on your device. If you flash the new OTA, and it replaces the bootloader but not the boot.img, you could be left in a situation where you could not boot the phone due to a security error. Once you're in that position, the only thing you can do is LGNPST back to stock-- and even then, it is possible that an OTA could enable an anti-rollback feature which would disable LGNPST.
Does this mean I can flash custom ROMs now?
Yes. However, the custom ROM must be made for your device. We're working on a decrapified stock ROM, and AOSP ROMs as well. Be patient for those to come.
Can I install a Nexus 4 system image and boot.img and have it work?
We've tested that, and the answer is no, not yet. Some work needs to be done, but once we figure it out, we'll have a quick and easy AOSP ROM.
Does this mean that we can use the Nexus 4 sources (kernel and android) ?
Short answer: Yes.
This phone is essentially a Nexus 4, with minor differences in GPIOs, memory address space, and partition table layouts.
Kernel source is iffy, since we've got Eco mode and a few other things that actually make me like the Optimus kernel more than the Nexus kernel.
However, this discussion is best suited for a new post.
How can I uninstall this?
I'm working on an easy-uninstall for this as well. Stay tuned for the links...
Click to expand...
Click to collapse
Important Information
To enter bootloader, hold volume UP and power.
Upon entering the bootloader, you will notice that there is no 'menu' to enter fastboot or recovery. Unfortunately, since the stars didn't align properly, we were unable to tell the new bootloader where to load the images that contain the menu from.
In light of that, you'll have to navigate the menu blind. Use the volume keys to change selection, and the power key to select.
The choices are (in order of pressing volume down):
Start - boot the phone normally [already selected]
Restart Bootloader - reboot into the bootloader
Recovery Mode - enter recovery (CWM)
Power Off - powers the phone off
So, to get to Recovery, you would press volume down twice then power.
If you have trouble with this, watch my video below for a demonstration.
Click to expand...
Click to collapse
Instructions!
Please note: this requires root before you can install this! If you haven't rooted your phone yet, now is the time to do so.
Also, ensure that you have ADB drivers installed. This WILL NOT WORK without them.
Before we begin: please make sure you have USB Debugging turned on, your phone is in "Charge Only" mode, and your phone's screen is on and unlocked.
This will allow you to see the root access prompt if your phone asks for it.
Download the .zip from this post
Extract it somewhere on your hard drive
Ensure your screen is on and unlocked
Run the "freegee.bat" script, and follow the instructions.
Do not run this as administrator! the install will fail if you do so.
Once the unlock is complete, check to make sure you have a "backups" folder now in the folder where you put FreeGee. If not, DO NOT REBOOT your phone.
Even a failed unlock will still show the 'congratulations you're unlocked!' text, read the output to see if you have errors!
You should not see any "adb.exe not found" errors, or "tar: invalid magic" errors. Those would be errors in the script.
An error which you can ignore is "No space left on device" after it says erasing old recovery and boot. That's just a side effect of how we clear the old images out.
Click to expand...
Click to collapse
Contact Information
"Mister Cubed, how do I talk to you?"
That's easy! Hop on IRC and join me on Freenode in #lg-optimus-g . I'm in there as IOMonster (or IOMonster_desk, or IOMonster_work, depending on where I am)
There's also a lot of other cool people in there too!
When you hop in IRC, if you've got a question, just ask it. Don't say "halp! i does brick'd my phone, and i dunno wat to does?!!", but rather "can anyone help? my phone is stuck in fastboot mode, and I can't get out of it. I flashed <xyz> and now I'm stuck here."
Asking your full question (even though it might be a long message) helps us figure out the best way to assist you, without us having to lead the conversation and ask all the questions for you.
Also, on IRC (for those of you who have never used IRC) if you say someone's name, it will 'ping' (also called 'highlight') them. This tells us that someone is talking to us. So, if you pop in IRC and say "IOMonster, it worked!", I'll get a notification, and will probably say "that's awesome!" in response.
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the assistance of the following people:
Shelnutt2
g33k3r
kmdm
synergy
jcase
sextape
xboxfanj
...and the support of the entire #lg-optimus-g IRC channel
A project like this is really only a sum of it's parts, and in our case, we're over 9,000!
Please make sure to tell someone on this list that they're awesome if you see them on IRC or (*gasp!*) in real life.
Click to expand...
Click to collapse
All right, that about sums up my post. Did I forget anything? Let me know below...
Can't wait!
Great work guys! Cant wait to lend a hand getting this to us Canadians!!
Yes!
Sent from my LG-E970 using Tapatalk 2
Here we go. Lets make this LG OG what it should have been from the beginning.
Thanks for all the hard work.
Sent from my LG-E970 using xda premium
Thanks once again to you and the project team for your efforts and congratulations on the work completed so far! I will definitely be a willing participant when you guys get around to the Korean model(s). Unsure how much difference there will be in the 3 carriers' for the Korean devices.
Sent from my LG-F180L using xda app-developers app
woot!
I dont even have an lg og and im excited.
Hey thecubed,
Do you guys have the group set up, so I can donate?:good:
Wooo thanks guys. I'll definitely be donating this Friday when I get paid. This was really quick. =D Great work to the whole team.
Sent from my LG-E970 using xda premium
TheCubed!! You (and your team) are my HERO! Thank you for all your hard work.
Q : Is there an option we need to set that will not allow LG to install any OTA updates without my permission? The last update was pushed to my phone and I had no option to stop it from happening.
Awesome work....can't wait...thank you very much!!
Sweet
Looking forward to the official release. Thanks for the good work.
you guys are awesome
Now I can retire my Inspire 4G. I tend to wait for pretty massive spec bumps to happen before I upgrade, and ditching the landscape sliding qwerty was a big deal. However, I'll be damned to something awful before having a phone incapable of a few dozen GB's of capacity. F*** the cloud.
I'm going to best buy later today. Thank you, thecubed. Ideally I'd just like to subscribe to you on Amazon Payments for a while, otherwise I would forget.
Got it
Globalrebel said:
Q : Is there an option we need to set that will not allow LG to install any OTA updates without my permission? The last update was pushed to my phone and I had no option to stop it from happening.
Click to expand...
Click to collapse
I'm wondering the same..
I'm ordering an LGOG when I get home today. It'll be here by Wednesday most likely.
I'll be in touch on IRC. (OverTheStars)
this is great, I thought about not buying this device until you did this! I was going to wait!
just got the phone ....bring on some pure jelly!!!!
when is this going public?
cant wait lol
Did this make it out yet? How's the testing going?
And now we need some ROM devs.
Need link to download the specific software specified in the title of this thread. Came across the one loaded on Google by another xda member but having difficulties downloading it. If you have it mirrored to another cloud service please provide me with the link. I am mostly gunning to get my hands on all of the .img files which come inside it so that I may review them via a hex editor and unlock my bootloader the sneaky way since Huawei refuses to reply back to my emails. Many thanks in advance.
Update: I was able to get my hands on the update.app file. So now will begin extraction and making my changes to hack the bootloader status on my device. If Huawei has responded back to you with your proper bootloader unlock code then you were fortunate. I myself have run out of patience with them and am now handling this on my own personal level.
Modding.MyMind said:
Need link to download the specific software specified in the title of this thread. Came across the one loaded on Google by another xda member but having difficulties downloading it. If you have it mirrored to another cloud service please provide me with the link. I am mostly gunning to get my hands on all of the .img files which come inside it so that I may review them via a hex editor and unlock my bootloader the sneaky way since Huawei refuses to reply back to my emails. Many thanks in advance.
Update: I was able to get my hands on the update.app file. So now will begin extraction and making my changes to hack the bootloader status on my device. If Huawei has responded back to you with your proper bootloader unlock code then you were fortunate. I myself have run out of patience with them and am now handling this on my own personal level.
Click to expand...
Click to collapse
Having trouble getting the bootloader unlock code? Try this:
Most of the issues are that emails sent outside of Shenzhen China business time during the week are not answered. They go into an email black hole. You'd have to send in the bootloader unlock request email really late here in the US or set up some way to send your email later automatically like I did with the Chrome extension Boomerang to get the code for my second HAM2. Currently sending in a request around 9pm EST to 4am EST Sunday - Thursday is the best time to email for the unlock code Sun-Thurs corresponds to Monday-Friday at Huawei in China.
I have emailed outside of those times and not gotten a response. After figuring out the time difference and setting up boomerang for an automated send later feature with my email the code arrived a couple hours after it was sent and I saw it when I woke up the next morning.
Sent from my MT2L03 using Tapatalk
@arcadesdude, thanks for your input, but unfortunately that route has failed me as well. Been at it with these emails since late last year. My guess is that my emails are getting lost in middle of a bunch of other emails they may be receiving or I'm going to their spam mail which they probably ignore. Either case, all attempts have not been successful. I found the EFI image and boot image inside the update.app last night. So far so good as it looks like I can easily hack this update and finally get my bootloader unlocked so I may do what I need to do with it.
Modding.MyMind said:
@arcadesdude, thanks for your input, but unfortunately that route has failed me as well. Been at it with these emails since late last year. My guess is that my emails are getting lost in middle of a bunch of other emails they may be receiving or I'm going to their spam mail which they probably ignore. Either case, all attempts have not been successful. I found the EFI image and boot image inside the update.app last night. So far so good as it looks like I can easily hack this update and finally get my bootloader unlocked so I may do what I need to do with it.
Click to expand...
Click to collapse
You can unlock the bootloader without the bootloader unlock code?
Did you try another email address? Another member on here used another address and got through to Huawei.
Sent from my MT2L03 using Tapatalk
arcadesdude said:
You can unlock the bootloader without the bootloader unlock code?
Did you try another email address? Another member on here used another address and got through to Huawei.
Sent from my MT2L03 using Tapatalk
Click to expand...
Click to collapse
No, the bootloader code is still required. All I am going to do is modify the source via a hex editor so that I can input a code of my choosing and force it to accept that code and thus unlock my bootloader. That is very possible . Should of done this already but I wanted to give Huawei a chance - but they failed.
Modding.MyMind said:
No, the bootloader code is still required. All I am going to do is modify the source via a hex editor so that I can input a code of my choosing and force it to accept that code and thus unlock my bootloader. That is very possible . Should of done this already but I wanted to give Huawei a chance - but they failed.
Click to expand...
Click to collapse
I didn't know you could do that. Is it essentially just flashing your modified bootloader partition to the phone using adb like we flash the recovery partition?
arcadesdude said:
I didn't know you could do that. Is it essentially just flashing your modified bootloader partition to the phone using adb like we flash the recovery partition?
Click to expand...
Click to collapse
Pretty much, but not with adb. Using fastboot.
also, i guess you also need disable the verification chain? but how? I heard it probably start from very beginning, ROM, a real read only rom. if you flash hacked aboot, sbl probably refuse to boot it, right?
xordos said:
also, i guess you also need disable the verification chain? but how? I heard it probably start from very beginning, ROM, a real read only rom. if you flash hacked aboot, sbl probably refuse to boot it, right?
Click to expand...
Click to collapse
With a bootloader being locked you are presumably limited on what can and cannot be flashed. With that in mind should a modification be incorrectly done for a device with a locked bootloader then it would be safe to say that the flash would be denied and no harm done. Because I will be modifying the source to accept my personal code then this will not have any affect towards flashing. The device will even accept it. Then, when I enter my code and reboot, the device will simply say it is unlocked. The only catch to this though is that if I flash back to the original then the bootloader should technically relock itself. I will open a thread on this procedure down the road when I get time and even include my mods so others may compare it with the stock to see the differences.
Modding.MyMind said:
With a bootloader being locked you are presumably limited on what can and cannot be flashed. With that in mind should a modification be incorrectly done for a device with a locked bootloader then it would be safe to say that the flash would be denied and no harm done. Because I will be modifying the source to accept my personal code then this will not have any affect towards flashing. The device will even accept it. Then, when I enter my code and reboot, the device will simply say it is unlocked. The only catch to this though is that if I flash back to the original then the bootloader should technically relock itself. I will open a thread on this procedure down the road when I get time and even include my mods so others may compare it with the stock to see the differences.
Click to expand...
Click to collapse
Regarding the limitation, early I thought you are going to modify/repackage the UPDATE.APP, as that way, if (a big if) it works, ideally you can flash to any partition. (There is some thread in xda that discussion about read/repackage the huawei UPDATE.APP)
But as we discussed briefly long time back, this whole thing is really really risky, if the booting path to fastboot got damage, then pretty much the phone is hard bricked.
Probably if you stick with flash with fastboot, then the risk will be lesser but man, this is scary stuff..
Regarding the validation chain, I got info from following article:
http://www.newandroidbook.com/Articles/aboot.html
A few paragraph after the Figure One.
Let's see...
PS, maybe you can continue try some different email address and sent at correct time to Huawei for the code...
PS2, another thought, maybe inject a superSU to the UPDATE.APP system image will work? not sure how strict they are validating when flashing UPDATE.APP and/or when booting the system partition.
xordos said:
Regarding the limitation, early I thought you are going to modify/repackage the UPDATE.APP, as that way, if (a big if) it works, ideally you can flash to any partition. (There is some thread in xda that discussion about read/repackage the huawei UPDATE.APP)
But as we discussed briefly long time back, this whole thing is really really risky, if the booting path to fastboot got damage, then pretty much the phone is hard bricked.
Probably if you stick with flash with fastboot, then the risk will be lesser but man, this is scary stuff..
Regarding the validation chain, I got info from following article:
http://www.newandroidbook.com/Articles/aboot.html
A few paragraph after the Figure One.
Let's see...
PS, maybe you can continue try some different email address and sent at correct time to Huawei for the code...
Click to expand...
Click to collapse
I won't be using the update.app parsay. Merely needed it so I can locate the images I want by viewing it with a hex editor and then extracting them so that I can solely focus on those images using a hex editor and once I make my patch(s) then I will use fastboot to flash those images to their respective partitions on the device. It really isn't that risky as long as you know what to look for. I won't be that guy that says "oops" in this case lol. So, I'm not worried about possibly bricking this device one bit .
Modding.MyMind said:
I won't be using the update.app parsay. Merely needed it so I can locate the images I want by viewing it with a hex editor and then extracting them so that I can solely focus on those images using a hex editor and once I make my patch(s) then I will use fastboot to flash those images to their respective partitions on the device. It really isn't that risky as long as you know what to look for. I won't be that guy that says "oops" in this case lol. So, I'm not worried about possibly bricking this device one bit .
Click to expand...
Click to collapse
Just curious, what are you planning to do that requires an unlocked bootloader?
ScoobSTi said:
Just curious, what are you planning to do that requires an unlocked bootloader?
Click to expand...
Click to collapse
Something lol
I'm not sure why you can't get the code from Huawei ...but I'm kinda glad you can't. seems your gathering nice info about this phone.
Sent from my MT2L03 using XDA Free mobile app
Modding.MyMind said:
Something lol
Click to expand...
Click to collapse
Just in case you're being super extremely nice and kind and trying to make a ROM for us, the other developer has hit a huge roadblock on CM11/12 you should know about.
ScoobSTi said:
Just in case you're being super extremely nice and kind and trying to make a ROM for us, the other developer has hit a huge roadblock on CM11/12 you should know about.
Click to expand...
Click to collapse
Even he is not plan to build CM, but as the man who build first recovery for us, I think he wont stop until he can play with his own baby in his phone.
Modding.MyMind said:
I won't be using the update.app parsay. Merely needed it so I can locate the images I want by viewing it with a hex editor and then extracting them so that I can solely focus on those images using a hex editor and once I make my patch(s) then I will use fastboot to flash those images to their respective partitions on the device. It really isn't that risky as long as you know what to look for. I won't be that guy that says "oops" in this case lol. So, I'm not worried about possibly bricking this device one bit .
Click to expand...
Click to collapse
1. How are you going to flash image via fastboot if your bootloader is locked?
2. You have to hack fastboot image to pass throuth unlock code verification without or with some random code. But even if you do so, you won't be able to flash fastboot image via fastboot even with unlocked bootloader.
I would'nt touch fastboot at all 'cause it's a high risk to get a hard brick.
I have found unlock code in some partition of my device, but I dunno was it there initially or was written there after unlocking. If the first case is and fastboot just compares entered code with saved one in device, then you can try to make update.app with injected su, as xordos offered, to be able to read this partition.
Injecting su into the update.app woukdnt work. The update.app has it's own crc and such. So to simply say, it won't work. You also answered your questions with remarks 1 and 2. One exception is that yes, you can flash the image. As for risks, it's only there if you mess something up - development typically is about taking risks . The fastboot image won't technically brick the device anyways. At best a soft brick may occur, but to be honest since "bricking" is up for discussion; bricking can occur simply by making a change to the build.prop file and not fixing it's permissions prior to rebooting. Unless you "hard" brick the device, then it can always be recovered.
You said the image or images can't be flashed with a locked bootloader, while yes is technically true, but understand that it isn't 100%, because you see, when your device recieves an update initially the devices bootloader is expected to be locked, right? Yet, magically enough the update goes through, the phone reboots, you either hate or love the new update. Something to think about before actually saying an image can't be flashed . Instead, I would have you ask yourself, "how?".
xordos said:
Even he is not plan to build CM, but as the man who build first recovery for us, I think he wont stop until he can play with his own baby in his phone.
Click to expand...
Click to collapse
And best believe, I want to play
Hi guys,
Just wondering if I can get root without unlocking the bootloader. Seems that I;m hearing that this isn't possible, which makes no sense. I know Verizon is Verizon when it comes to locking things down(They were even blocking free games on dumbphones back in the day so that you would have to buy them, even when the manufacturer included them for free), but it seems that gaining root access is completely different than flashing a new ROM. Am I correct here?
Also, would towelroot work for this phone? I know it's a nice simple solution, but I believe their claim is for phones manufactured before Jun '14.
Lastly, would a solution like Safestrap work here? It's what I used on my last phone (S3), when Verizon locked THAT down.
I know it is a battle fighting Verizon on this, and I know it takes time, I was just wondering if I am reading this right, or if I could root, but run the standard ROM, just with the extra access... Really, the phone is working so well that I just want better control for things like deleting/disabling/freezing stock apps and such.
Thanks for any help!! Sorry if this is in the wrong thread, seemed appropriate.
I am a user of H961N and it is also cannot be rooted.
I think root injection may be the answer.
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
This is the related thread in G4 forum. I have tried this method. However, I have encountered a problem shown below during the process:
Code:
D:\V10\LG_Root>Send_Command.exe \\.\COM8
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#dd if=/dev/block/mmcblk0p51 of=/data/media/0/system.img
FAIL
#ls
FAIL
#
It keeps returning "FAIL" to me no matter what command i enter. I have asked about this in the thread in G4 forum but no one answer me, sad
I think that you may try it and it may work, as the above problem may not due to the phone but my computer.
Where did you get you system.img file? if you are using the one from the g4 it will not work. The file needs to be rooted for your device and then injected.
ivangundampc said:
I am a user of H961N and it is also cannot be rooted.
I think root injection may be the answer.
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
This is the related thread in G4 forum. I have tried this method. However, I have encountered a problem shown below during the process:
Code:
D:\V10\LG_Root>Send_Command.exe \\.\COM8
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#dd if=/dev/block/mmcblk0p51 of=/data/media/0/system.img
FAIL
#ls
FAIL
#
It keeps returning "FAIL" to me no matter what command i enter. I have asked about this in the thread in G4 forum but no one answer me, sad
I think that you may try it and it may work, as the above problem may not due to the phone but my computer.
Click to expand...
Click to collapse
ivangundampc said:
I am a user of H961N and it is also cannot be rooted.
I think root injection may be the answer.
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
This is the related thread in G4 forum. I have tried this method. However, I have encountered a problem shown below during the process:
It keeps returning "FAIL" to me no matter what command i enter. I have asked about this in the thread in G4 forum but no one answer me, sad
I think that you may try it and it may work, as the above problem may not due to the phone but my computer.
Click to expand...
Click to collapse
I'm curious, the 'Fail' just means that it fails to work, right? Phone works fine after that and all? No bricking or need to restore? If so, that's a safe risk. Thanks for the suggestion.
Mikey1969 said:
I'm curious, the 'Fail' just means that it fails to work, right? Phone works fine after that and all? No bricking or need to restore? If so, that's a safe risk. Thanks for the suggestion.
Click to expand...
Click to collapse
Yes, the phone is working fine after I have tried this. So it is a safe risk.
---------- Post added at 12:08 PM ---------- Previous post was at 12:06 PM ----------
spidey44 said:
Where did you get you system.img file? if you are using the one from the g4 it will not work. The file needs to be rooted for your device and then injected.
Click to expand...
Click to collapse
That's why I am trying to clone the system partition but it shows fail
Good luck with this but I have a feeling that unless someone has an exploit laying around, you'll need an unlocked bootloader.
Sent from my LG-H901 using Tapatalk
Should this be in the Q and A sections as this is not development?
Don't have an LG v10 yet, but found this:
www.droidviews.com/how-to-root-lg-v10-with-supersu-v2-56/
Thought I'll share if someone would like to give this a shot.
(try at your own risk, that's all I can write to that, since i can't try myself.)
Thanks for this.....but i was reading that article...it says you root it by flashing the superuser zip in TWRP recovery....um....you cannot flash custom recovery without root....or am i missing something. Im not bashing you for posting the article. I thank you very much for posting it! More like questioning the articles validity.
in99flames said:
Thanks for this.....but i was reading that article...it says you root it by flashing the superuser zip in TWRP recovery....um....you cannot flash custom recovery without root....or am i missing something. Im not bashing you for posting the article. I thank you very much for posting it! More like questioning the articles validity.
Click to expand...
Click to collapse
you need an unlocked bootloader
http://www.droidviews.com/how-to-unlock-bootloader-on-lg-v10/
and adb & fastboot tool, not root
To install a custom recovery
http://www.droidviews.com/how-to-install-twrp-recovery-on-lg-v10-h901/
That's how I usually would do it, the way it's described in the articles, since I still have to get my v10 from Far East can't test it.
And don't worry, I don't feel like you are bashing.
Life's too short to take anything too personal.
Awesome thank you for clearing that up!! I was totally confused for a second there.
GerManiac said:
you need an unlocked bootloader
http://www.droidviews.com/how-to-unlock-bootloader-on-lg-v10/
and adb & fastboot tool, not root
To install a custom recovery
http://www.droidviews.com/how-to-install-twrp-recovery-on-lg-v10-h901/
That's how I usually would do it, the way it's described in the articles, since I still have to get my v10 from Far East can't test it.
And don't worry, I don't feel like you are bashing.
Life's too short to take anything too personal.
Click to expand...
Click to collapse
What you've mention is only working for tmobile V10, since it's bootloader can be easily unlocked while the other are not.
ivangundampc said:
What you've mention is only working for tmobile V10, since it's bootloader can be easily unlocked while the other are not.
Click to expand...
Click to collapse
Thanks for clearing that up. Didn't know that and didn't see that on the article.
Cheers
I think if LG release a genuine ROM file, we could replace recovery parition with rooted one and flash it to our phone, that the only way open but LG hasn't released any ROM file yet.
phillymade said:
Should this be in the Q and A sections as this is not development?
Click to expand...
Click to collapse
Sorry, wasn't sure, as I was asking about development.... Sometimes this is like a scene form the movie Big Trouble... At the airport, "Arrivals or Departures"? "Well, we're arriving at the airport, but then we're going to be departing.".
Title says it all. I haven't gotten past root because every rooter I try fails. Tried rooting on 4.5.5.1 and .2, hoping .3 would solve any issues but it didn't. Really hoping to get a custom ROM on this thing, if anyone could help, much appreciated..
WSADKeysGaming said:
Title says it all. I haven't gotten past root because every rooter I try fails. Tried rooting on 4.5.5.1 and .2, hoping .3 would solve any issues but it didn't. Really hoping to get a custom ROM on this thing, if anyone could help, much appreciated..
Click to expand...
Click to collapse
No need to pre-root. Go for one of the bootloader unlock methods and profit.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Davey126 said:
No need to pre-root. Go for one of the bootloader unlock methods and profit.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Click to expand...
Click to collapse
Your first link shows root as a pre-requisite? Is it still not necessary?
WSADKeysGaming said:
Your first link shows root as a pre-requisite? Is it still not necessary?
Click to expand...
Click to collapse
It is not. This post offers nice summary of the necessary steps including required files.
Davey126 said:
It is not. This post offers nice summary of the necessary steps including required files.
Click to expand...
Click to collapse
I get this error when I run get_code.bat even though running 'adb devices' shows my hdx.
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to copy 'cuber' to '/data/local/tmp/cuber': couldn't read from device
cuber: 0 files pushed. 0.1 MB/s (506072 bytes in 5.020s)
error: no devices/emulators found
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
Press any key to continue . . .
WSADKeysGaming said:
I get this error when I run get_code.bat even though running 'adb devices' shows my hdx.
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to copy 'cuber' to '/data/local/tmp/cuber': couldn't read from device
cuber: 0 files pushed. 0.1 MB/s (506072 bytes in 5.020s)
error: no devices/emulators found
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
Press any key to continue . . .
Click to expand...
Click to collapse
Choices:
- do some basic troubleshooting to resolve the issue (first line offers a clue)
- use the 1-click method
Although preferable you do not need to execute get_code.bar prior to flashing the vulnerable bootloader (aboot) which is where the real magic lies. That said, a mistake at this stage can result in a black screen 'soft-brick' that is difficult to recover. Probably best to stick with 1-click.
Davey126 said:
Choices:
- do some basic troubleshooting to resolve the issue (first line offers a clue)
- use the 1-click method
Although preferable you do not need to execute get_code.bar prior to flashing the vulnerable bootloader (aboot) which is where the real magic lies. That said, a mistake at this stage can result in a black screen 'soft-brick' that is difficult to recover. Probably best to stick with 1-click.
Click to expand...
Click to collapse
Called in sick to work to spend the rest of the day googling my way thru this process and got it to 7.1.2
Sorry guys. I have exactly the same issue as in post #5 above. I do not want a one click type of solution. I would like to understand what the problem is and how to get the right drivers to fix the damn thing. I tried a dozen different drivers, installed correctly, with full reboots, etc, and nothing gets into that device. I use Windows 10. Thank you for any positive thought and solution.
[Thor][Apollo] Unlocking bootloader with any firmware
Hello. At first, I did not invent anything new, just checked some my guess on a other motherboard. All thanks and credits to our great developers. As always, all at your own risk. It does not work on the Fire HDX 8.9 (Saturn)! All steps in this...
forum.xda-developers.com
Reichmann aka realm mann, had the easiest guide imo.
Got a apollo unlocked and twrp'd in 30 minutes.
But take note you are expected to rename aboot file to "aboot_vuln.mbn"
And twrp to whatever the guide prints for the dd command. (I dont recall but just rename your twrp file to whatever that dd command references.)
Doesnt matter what windows. Or at least worked a treat on win7 for me. Reichmann used 10.
Make sure your key code file is generated or if you continue might be bricked judgjng from other posts.
Make sure you typed the commands exactly. Wmic commands are easy to mess up and could be confusing.
If you get an error double check every character of text.
Your disk index result number from wmic command replaces the X after Harddisk in dd command.
But if you dont get the same disk index result from all 3 wmic command or an error? Probably mistyped. Like "partiton".
Just double check and proof read.
Doesnt matter if you do mistype it as long as you retype it correctly eventually.