Related
I'm not a noob to Android. This is actually my third device and my previous two have been rooted and heavily modded. But for some reason I did something wrong while trying to root my Galaxy S II.
While following jivy26's guide on how to root (the Odin guide), I accidentally put the Odin PIT file in the PIT directory and hit start. It said success, but then I was stuck in a boot loop. Now it won't do anything except for go into Android Recovery. I've already tried twice to wipe it, but it starts back with absolutely the same results (the bootloop). Can anyone please help me out here? My dad will kill me if I tell him I have to take it back to exchange it.
Thanks!
it should go into download mode again. hold volume up and down and plug in USB cable.
Thanks! Yes, it did go into download mode. I don't mean to sound like a noob, but is there a guide for similar situations anywhere else on the forum? I glanced around but didn't see much. To be quite honest I freaked out a bit. If someone can direct me to it, I'll happily delete this thread. Otherwise, would you mind telling me what I should do next?
Use this guide to gain root and CWM easily without triggering the flash counter http://forum.xda-developers.com/showthread.php?t=1311081
Thank you very much!
Anytime. When ever I get a new phone I have Noob moments myself. Once rooted though the rest is old hat.
Agreed. As soon as I'm rooted, I'm prepared to flash many, many ROMs. I'm just really glad that this device isn't Motorla - No bootloader to unlock
jtc276 said:
Agreed. As soon as I'm rooted, I'm prepared to flash many, many ROMs. I'm just really glad that this device isn't Motorla - No bootloader to unlock
Click to expand...
Click to collapse
Yup I had an Atrix 2 for 4 days. locked bootloader and very few devs not a popular phone at all. Too bad because for 99 bucks it's really nice.
I had the first Atrix. It was a decent device, but it lagged in many areas where it shouldn't have, and the screen was mediocre (especially compared to the S II). Plus, the dev support was rapidly growing smaller. I'm glad to now have a phone that developers will be supporting until at least the US variants for the S3 are released.
Hello XDA!
I opened a new thread hopefully to open a discussion about improvements I think are beneficial, my experience over the last 24 hours that a couple sticky edits would have saved me (and others) time.
My Story:
Yesterday (5/3) I saw I had around a 250 mb OTA. Excited (hoping for 4.2, assuming was the 4.1.2 that VZW released recently) I kick on WiFi, download and watch as it reboots and appears to install successfully. Time for work to end, grabbed phone off charger as it appeared to be rebooting after successful install, and ran out to catch train home.
Downstairs, at train stop, take a look at phone and heart sinks as it is in a fast splash screen loop, blinking the VZW Galaxy Note 2 screen for about 1 second in endless loop. As I had never seen before was thinking firmware update bricked it and I was looking at least until Tuesday before I'd have a working phone. Luckily, I was able to quickly see that I could still get into download mode, so knew I was (likely) going to be ok.
Get home and a Quick Robin, to the Internetz! later I'm browsing XDA and following the t=t=2024207 walkthu to restore stock. FYI, my device prior to the failed OTA was unrooted stock. At this point I'm not sure if it's going to restore, so I'm trying to do the true stock, no unlocked bootloader in case it has to be RMA'd. I've downloaded all my files, waited patiently for the slow hosting service for the FXZ(?) to download and am grinding through it and of course it fails at the system.img. Luckily, blessedly the awesome community here had released the image that included the unlocked bootloader which I was (after waiting to download, etc etc again) able to successfully get installed via Odin, booted up and working successfully.
So, while the first post section regarding restore to stock does indicate users with latest firmware "L4 OTA Only" shouldn't be attempting to use the Official VRAL I didn't think it applied to me. I would say that a fair amount of individuals looking to take the drastic step of a full restore to stock might be in a scenario like mine, where something significant has happened and likely confirming what OS/firmware/etc you are on might not be feasible. In my case, I assumed never rooted/unlocked vanilla device should be about as receptacle to an "official" restore as any. In this scenario, where a 100% for all devices stock recovery ("alternative") works, 'I feel that it should have been pushed harder than the official or at least blurbed with if you don't know what you are on, use this' While I understand that it is the "official" image, it has requirements for it to work. A co-worker had an ASUS TF300T that tried pushing a recovery image for ICS after he had upgraded to JB and it hard bricked his tablet, with ASUS wanting to charge him about 60% cost of the tablet to replace motherboard. That's heartbreaking, and I am sure since a hard brick wasn't a likely scenario here, why it wasn't mentioned.
Also: The download link for the Alternate Restore lists the file as: I605_VRALJB_Restore.tar.md5.xz which requires that it be unpacked using 7zip AND also that once extracted, it needs to be renamed to kick of the extra extension md5 in order for ODIN to see it properly as a PDA image file. (I605_VRALJB_Restore.tar.md5 ) Neither step is mentioned in the original post, and I had to read through to I believe the 11th page or so before realizing that was the problem. I'm sure with most of the people that are daily users of this forum knew automatically that these steps were required, but I would counter that a thread explaining how to restore Stock is one of the few threads that is likely to reach a larger, inexperienced demographic who would need to know such details.
Lastly, since (I thought) I had an unlocked bootloader, but otherwsie working phone again (Thank you, thank you thank you!) might as well get it rooted, and grab a ODEX'd stripped ROM with the OS release because getting the Software Update nag and not being able to complete or even brick my phone makes my OCD gland flex mightily. Was delighted to see an on-device APK root option which threw me back to the ease of z4root a few years ago with my Droid X. APK installs, and it roots so easily, like it had the functionality out of the box. I grab goo.im manager and install TWRP. Go to boot into custom recovery so I can install my sexy updated OS ROM and enjoy my fun device without all the yucky bloatware I've just ignored/dealt with for the last 2 months and I get the dreaded and in my opinion illegal "VZW unauthorized software" software brick.
Back to the forums, see I need another stock 'alternative' restore to fix AND a little confused, but believe I need to run a "jailbreak" bootloader unlock (CASUAL ?t=2118348) Which I haven't done yet. I have all files downloaded, just paused to post my experiences here.
So, this was main reason for my post, as I can understand some of why walkthru is laid out the way it is above, but why not have this included as part of the stickied root walkthru? It's mentioned thusly:
section 1a is a old method and no longer needs to be used unless the end user wants root only. proceed to Adam Outler's "JAILBREAK" thread linked at the bottom of this section for rooting and unlocking bootloader so custom roms can be flashed!!!
Click to expand...
Click to collapse
I couldn't find the link it refers to at bottom of section? I ended up googling to find guide. ((t=202420)
if this is still a requirement for root, custom ROM/Recovery, I would have made this steps 1-x of the root guide. is it because another person authored it? It would be nice to be able to credit and quote, I know alot of what drives contributors is the 'Thanks" and Donations, be great if XDA admins could round table and find a solution that allows for a consolidated guide for each device and still give each contributor a way to get their +1's and plug donation/web/twitter handle url's
So, is my understanding incorrect of what is needed or do folks agree with me that current setup is not the most efficient way XDA community could be offering instructive guides on Root/Mods? It would be wonderful if XDA Mods upon announcement of devices, when creating the forum threads for device (Development, OG Development, General, etc etc) created a blank thread for the how to root et.al and then allowed it to be edited by the community as a Wiki. Or even if an individual created, allow that person to allow x amount of other community members to edit, add and adjust.
I see droidstyle created a thread about questions for softbrick, and I might have to look at the original sticky thread about how to stock restore, but it seems he/she might have better saturation if this info was included in the original post. The stickied How To recover stock is direct accessible from a google search. I doubt his Q&A thread is or definitely not going to be one of the highest page-ranked sites.
So, please let me know if I'm just out of my mind, off the mark. I will give myself a small escape clause based on the fact that I probably scored about 2 hours of sleep last night messing around trying to get the note running again. I am actually concerned that the instructions for Return to Stock/Root/Etc for the VZW i605 doesn't have the link to unlock bootloader via casual and am hoping that following that process before rooting/customrecovery/ROM is correct, and not going to be another BrickGate for me. I know as OS versions are updated and/or Big Red and Big Blue constantly push patches trying to lock people out of their phones that instructions change and methods break. As new directions are implemented it's easy to lose steps as edits occur on the fly.
Most importanly! I hope this thread comes across as constructive criticism/suggestions, I have nothing but the highest respect for this community and it's contributors. Even skewed, outdated and conflicting information is better than no information and I SUPER appreciate the hard work required to get it out to us. I am most definitely not expressing displeasure with my experience or the content, only using the threads I mentioned as examples of what I personally see as opportunity for improvements XDA could implement that would allow for easier dissemination of the information the community is sharing so unselfishly. I only open it for discussion, so that others like me can access the information quicker with less confusion. I read comments of disgust and exasperation as people are directed to search, rather than post, and they are right, the information is invariably there, and most often or not within the first 5 posts of a thread. But sometimes when a developer talks to another developer, the tiny and considered minor details are not mentioned because it's considered common knowledge, and thats where the noobs, soccer moms and Grandmas can get left scratching their heads trying to puzzle how you got from point a to b. (Stereotypes used for comedic effect, please take no offense) I believe it would save alot of people having to answer the same questions over and over again time and frustration and freeing them to focus their talents on making us the next epic ROM/Kernel/App
thanks for reading! Also, I'm not just drive-by b*tching, if anyone is interested, I would love to show a mock-up of the i605 guide these great contributors have created as I would compile it. I'm passionate about mobile technology and customization, sadly my talents don't lie in the creation of such, only the enjoyment of it. But I'm a hell of a document admin. I create wiki's and KB's/sharepoint admin for a living, and would love to contribute what I know in that way
For those of you looking to root your N3, @Chainfire has updated his one-click app for N3 variants. No official support for the Verizon variant yet, but it's something to keep an eye on. No word on the bootloader as it's not anyone's hands yet.
http://forum.xda-developers.com/showthread.php?t=2466423
That's good to know. Thx.
Sent from my SCH-I545 using Tapatalk 4
unlocked BL NEEDED.
Indeed. This method will not work with a locked bootloader. We have to wait for an exploit in order to root.
suzook said:
unlocked BL NEEDED.
Click to expand...
Click to collapse
I was not aware that this method needed an unlocked bootloader. I should have read more.
Banggugyangu said:
Indeed. This method will not work with a locked bootloader. We have to wait for an exploit in order to root.
Click to expand...
Click to collapse
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
docnok63 said:
I was not aware that this method needed an unlocked bootloader. I should have read more.
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
Click to expand...
Click to collapse
This is great to hear!!1
It sounds as if within days of release we are likely to haveca method for rooting. I would be grateful for unlocking but expect to use Safestrap
docnok63 said:
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
Click to expand...
Click to collapse
Read what I said again.... And you're wrong. You can't write to the recovery image on a locked bootloader phone. That means no custom recovery. What you CAN do.... is bootstrap a recovery. Different process, different results.
If you had read my post more closely, I said that we are going to have to wait on an exploit for root capabilities. Once we have root, I'm sure a bootstrap will follow. Hopefully, exploitative rooting won't trip knox. If it doesn't, then a bootstrap recovery also shouldn't. At that point, a custom ROM (especially if hashcode creates a safestrap) should bypass the software side of knox preventing tripping from that as well.
Banggugyangu said:
Read what I said again.... And you're wrong. You can't write to the recovery image on a locked bootloader phone. That means no custom recovery. What you CAN do.... is bootstrap a recovery. Different process, different results.
If you had read my post more closely, I said that we are going to have to wait on an exploit for root capabilities. Once we have root, I'm sure a bootstrap will follow. Hopefully, exploitative rooting won't trip knox. If it doesn't, then a bootstrap recovery also shouldn't. At that point, a custom ROM (especially if hashcode creates a safestrap) should bypass the software side of knox preventing tripping from that as well.
Click to expand...
Click to collapse
Since you want to argue sematics and I'm just in that kind of mood, my post never stated that SafeStrap involved writing to the recovery partition; simply that it was possible to have a custom recovery run on a device with a locked bootloader.
Neither the ME7 root method nor SafeStrap triggers Knox on the S4 and I don't expect them to for the N3. Of course, all this will be unnecessary if we get the bootloader. We only have a few days to wait for the devices and then a few days more to know for sure.
docnok63 said:
Since you want to argue sematics and I'm just in that kind of mood, my post never stated that SafeStrap involved writing to the recovery partition; simply that it was possible to have a custom recovery run on a device with a locked bootloader.
Neither the ME7 root method nor SafeStrap triggers Knox on the S4 and I don't expect them to for the N3. Of course, all this will be unnecessary if we get the bootloader. We only have a few days to wait for the devices and then a few days more to know for sure.
Click to expand...
Click to collapse
You also never stated anything about a bootstrapped recovery. You posted about chainfire's root method, then argued (wrongly) against those that stated that method wasn't possible due to locked bootloader. Not one person in this thread said anything about not being able to root because of a locked bootloader, just that this particular method wasn't going to work. FFS admit that you were wrong and move on...
Banggugyangu said:
You also never stated anything about a bootstrapped recovery. You posted about chainfire's root method, then argued (wrongly) against those that stated that method wasn't possible due to locked bootloader. Not one person in this thread said anything about not being able to root because of a locked bootloader, just that this particular method wasn't going to work. FFS admit that you were wrong and move on...
Click to expand...
Click to collapse
docnok63 said:
I was not aware that this method needed an unlocked bootloader. I should have read more.
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
Click to expand...
Click to collapse
Silly rabbit. I did admit I was wrong and I my link was for the SafeStrap recovery for the S4. It's time YOU moved on. There's more important issues in life. I'm done with you.
Realistic chance?
I've got an unlocked Droid Bionic. I was chicken and waited till it was out of warranty though. I wanted root so I could do full backups, something I believe was not possibly without it. Like you, I'm waiting for my VzW N3 to come in. I"m not sure how to restore some of my apps, or actually some of the data saved with that. TBpro wont help unless there is root. I've purchase the Asurian extended protection, not to much fine print info on it.. people say manufacturer warranty is voided with root. what about standard extended warranties like Asurian?
Bottom line.. just a guess, and I'll not hold anyone to it. What the odds that the guru's here will unlock our Vzw N3 without tripping knox, or somehow else voiding warrranty.
I'm probably sticking with stock rom for now..but without root, not sure how to get all my app data back. Someone said EZ file could make an apk but didnt see how. Someone else suggested helium makes good app backups without root, but that doesnt work on Motorola..so it wont work for my Droid bionic
Please familiarize yourself with the Forum Rules at the top of every Forum. This is a discussion thread and not a Development thread. It has no place in the Development Forum. I have moved this to the General Section where it should have been all along.
I look forward to your future attention and cooperation.
EFM
docnok63 said:
I was not aware that this method needed an unlocked bootloader. I should have read more.
Absolutely not true. It's completely possible to root a phone with a locked bootloader. It's also possible to install a custom recovery with a locked bootloader.
I'll be working with two of the top Verizon exploit devs from day one to get this device cracked. I won't be stupid enough to promise anything, but I will say this:
1) There was a day one OTA for the Sprint Note 3. No one knows what it did yet. DO NOT TAKE ANY OTA's. As soon as I get the device in my hands and tinker a bit, I'll post how to stop OTA's.
2) We will work tirelessly the first few days to get this done. There's a whole community out there waiting to tinker.
Click to expand...
Click to collapse
Docnoc we all appreciate this post and are confident the people working on this will find something for us. Fingers crossed and donations ready!
edfunkycold said:
Please familiarize yourself with the Forum Rules at the top of every Forum. This is a discussion thread and not a Development thread. It has no place in the Development Forum. I have moved this to the General Section where it should have been all along.
I look forward to your future attention and cooperation.
EFM
Click to expand...
Click to collapse
When I read your post I hear Nucky's voice from seeing your avatar and sig plus your words is how we would talk lol
Apparently Chainfire's method helped designgears root the AT&T version. This took about 3 days. Good news!
http://forum.xda-developers.com/showthread.php?t=2472760
Does this work for the Verizon Note 3 ? Thanks guys.
Ok so a couple of things to note here.
First off it is about a 2% chance that you can just flash a custom recovery. There was a phone recently where the recovery partition had no verification check. With that being said it would be a big over sight. The next thing is that with Hashcode already working on a qualcomm kexec and SS I would be very supprised to see it not work, or there not be a strap method. As for root, if I'm not mistaken, and i could be, but Chainfire relies on you having an unlocked bootloader, as his image just has an init script in the recovery to boot, change ro.secure to false and then flashback the old recovery. With this being said THIS WILL NOT WORK WITH LOCKED DEVICES. If the bootloader allows for a unsigned kernel recovery to boot you can do it, or if it allows for stacksmashing you can do it, but those are two very iffy things. As for a root on this device, its more then likely going to have to come from a security tag that has been created in the linux kernel, that allows unverified code to run.
Second off I think there's something important to point out here, and I'm going to post it back to the days where there was no android. As of right now we have achieved a semi unlocked state (see loki and SS) however this is much like Musclenerd and geohotz grabbing the source code and finding injection points, the big difference was when geohotz found the holygrail, an architecture level exploit. What this translates into our world is much harder since the iPhone has one chip and we have... well Qualcomm, TI, and Samsung to name some. With this being said, and I know its easier said then done, but I think we are going to need a Qualcomm level exploit to really unlock all of these phones. We have seen in the recent couple of days that there are interrupts early on in the boot chain, see rumrunner, are not impossible. The reality is that our holy grail lies in one of two places, a leek, which in reality is more likely to happen since the other option is not always possible, or a base level exploit. The thing to keep in mind is that it too geohotz 2 years to discover the A4 hole, and he was just one man. While a community is much bigger, I urge everyone looking for exploits on new phones to realize that YOU SHOULD NEVER BUY A PHONE THAT YOU DON'T LIKE STOCK.
Hope you all are enjoying your GN3. They really are a great device with or without an unlock!!!
On a side note:
docnok63 said:
Apparently Chainfire's method helped designgears root the AT&T version. This took about 3 days. Good news!
http://forum.xda-developers.com/showthread.php?t=2472760
Click to expand...
Click to collapse
The reason for this is it seems there is a leek there that is allowing him to run a script that flashes over files to the FS. Look at:
designgears said:
As usual, a big shout out to my anonymous source for the file hook-ups!
Click to expand...
Click to collapse
This means that he most likely has some sort of System dump that is signed and has RO.secure disabled. If you look there's actually a full 2.2 GB image that you have to download and flash, meaning that it most likely has something that allows for root, and not actually an exploit.
Hi,
Originally I had opened this thread in LG 5 AT&T forum. But, after a request from @Nitro1max1, I understood that he is right and it should be reached for more useres.
Please find the link for requesting LG to open our bootloader - https://www.change.org/p/lg-electro...utm_source=share_petition&utm_medium=copylink
Hopefully, we could make a change together.
last thing, this is the origina thread - https://forum.xda-developers.com/at...se-kdz-tot-t3587926/post71887733#post71887733
I will switch updating here since it will be more convinent to update in one single place.
Cheers,
Mor
stop
What happens when we reach 100 people?
Hopefully, LG will pay attention to our request. This device is no longer a valuable asset for LG (the newly LG G6 is out), therefore I guess we will have a fair odds with getting an unlocking method.
H840 now officially can unlock bootloader
I signed even though I know they will give a sh...t
The real question is who is the one who holds the responsibility for locking the bootloader,LG or AT&T?
I've included both of then in the petition, but, it will be easier to know who have the upper hand here.
About the H840, they are so lucky
Well, I got some idea that might work - but, maybe someone will prove me wrong.
While searching around for methods to unlock the boot-loader for AT&T varient, I came across lots of information about bricked phones. A method that had been proposed there, is to use some device that have JTAG protocol in order to revive the phone.
Digging around the JTAG subject, I found out that it's basicly an interface that have the ability to write new bootloader and pushing new .kdz images.
So, with using some common sense, it might be, that AT&Ts owners could use this method in order to flash the european bootloader into their system and bypassing this whole signed bootloader issue. after that, flashing a new european .kdz file will support this new bootloader that will transform the phone to EU modle.
Only thing is the IMEI and other modem related drivers needs to be taken in consideration.
What do you think about it?
P.S - I'm trying to get in touch with some JTAG box that might give a clearer picture about this subject.
ForMartha said:
Well, I got some idea that might work - but, maybe someone will prove me wrong.
While searching around for methods to unlock the boot-loader for AT&T varient, I came across lots of information about bricked phones. A method that had been proposed there, is to use some device that have JTAG protocol in order to revive the phone.
Digging around the JTAG subject, I found out that it's basicly an interface that have the ability to write new bootloader and pushing new .kdz images.
So, with using some common sense, it might be, that AT&Ts owners could use this method in order to flash the european bootloader into their system and bypassing this whole signed bootloader issue. after that, flashing a new european .kdz file will support this new bootloader that will transform the phone to EU modle.
Only thing is the IMEI and other modem related drivers needs to be taken in consideration.
What do you think about it?
P.S - I'm trying to get in touch with some JTAG box that might give a clearer picture about this subject.
Click to expand...
Click to collapse
No... nononononono. JTAG will not work, look around the threads. I'll say it one more time:
THE ONLY WAY, ONLY. WAY. THIS PHONE WILL GET A BOOTLOADER UNLOCK OR PERSISTANT ROOT IS BY CREATING A NEW EXPLOIT. DONE. THAT'S IT. LITERALLY NOTHING ELSE WILL WORK.
Honestly Annoying said:
No... nononononono. JTAG will not work, look around the threads. I'll say it one more time:
THE ONLY WAY, ONLY. WAY. THIS PHONE WILL GET A BOOTLOADER UNLOCK OR PERSISTANT ROOT IS BY CREATING A NEW EXPLOIT. DONE. THAT'S IT. LITERALLY NOTHING ELSE WILL WORK.
Click to expand...
Click to collapse
Well - you made your point with saying it.
I had looked in the threads but I didn't understand what lockes us with flashing new boot partition using JTAG method (it's like mounting the entire emmc to a point where it can be written with new bootloader etc.)
Please let me know what I'm missing here..
ForMartha said:
Well - you made your point with saying it.
I had looked in the threads but I didn't understand what lockes us with flashing new boot partition using JTAG method (it's like mounting the entire emmc to a point where it can be written with new bootloader etc.)
Please let me know what I'm missing here..
Click to expand...
Click to collapse
You can find the full explanation if you dig around, but basically for the G5 (and most devices) the bootloader unlock is not located in aboot, it is an actual change in the whole bootchain. You can modify aboot to disable a sig check, but that is not the same as unlocking the bootloader and doing so will break the signature of the aboot.img and hard brick your device.
Question is, what is the real differance between H850 to H820. they are sharing the same physical parts, but the bootloader is diffarent. so, by using external tool that will flash the new bootloader, it could be done, right?
Signed.
Honestly Annoying said:
THE ONLY WAY, ONLY. WAY. THIS PHONE WILL GET A BOOTLOADER UNLOCK OR PERSISTANT ROOT IS BY CREATING A NEW EXPLOIT. DONE. THAT'S IT. LITERALLY NOTHING ELSE WILL WORK.
Click to expand...
Click to collapse
few days ago LG G5 SE (H840 - Euro) was added to list of unlockable devices (probably it's a coincidence and not related to this petition, but also give a hope to owner of other G5 devices)
ayaromenok said:
few days ago LG G5 SE (H840 - Euro) was added to list of unlockable devices (probably it's a coincidence and not related to this petition, but also give a hope to owner of other G5 devices)
Click to expand...
Click to collapse
Yep, I agree. I tend to belive that it's LG's move. let's hope that they will do the same for the H820.
Meanwhile, I've spend sime time speaking with @autoprime (thanks for your time!) and the way he sees it is the following :
1. Finding some exploit in the H820 bootloader that will pretty much will effect all the other devices. Question is, if one will find it - will he share it on XDA or sell it to Qualcomm or LG. Time will tell.
2. Finding some leaked debug bootloader (one which the development team is using or the tech system) - That way we will be able to flash custom boot.img (AKA some open recovery).
Meanwhile, I'm doing some digging around for finding exploits.
Now, let's have our finger crossed for one to happen.
ForMartha said:
The real question is who is the one who holds the responsibility for locking the bootloader,LG or AT&T?
I've included both of then in the petition, but, it will be easier to know who have the upper hand
Click to expand...
Click to collapse
You have to take into account that for carrier-specific models, the CARRIER is actually the customer of LG, not the end user.
Only if you buy an unlocked device you are LG's customer.
So I'd guess that LG cannot provide a bootloader unlock for carrier-specific devices, this goes against the contract. Of course things change when the carrier agrees to the unlocking. But do you really think your carrier will allow this?
T-Mobile USA doesn't seem to care, but Verizon and AT&T?
Here in Europe carriers sell the regular H850, they "just" add additional bloat, so you can flash stock KDZs and unlock the bootloader. But the American carriers seem to stick to a different approach. Customers need to vote with their wallets to change this, but I think most people just don't care.
Well said BabelHuber,
Still, I have wish that it will be released eventually.
LG needs to do this or it will be my last LG phone.
Signed
Signed
hello does anybody know a working method to how to find and download and flash a Stock Rom on my Nokia 7.2 all Tutorials i try so far but did not work well i stuck as well in security patch problem it will not install thats why i want try to find a Stock Rom to flash again with working update
It's pretty easy. Use the NFT tool to flash any full update package and/or flash a full firmware package (HMDSW type).
singhnsk said:
It's pretty easy. Use the NFT tool to flash any full update package and/or flash a full firmware package (HMDSW type).
Click to expand...
Click to collapse
Sorry for the necro, and not asking if phone can be rooted as wow, am not surprised how many asked already lol.
I purchased four unlocked Nokia 7.2 which forced updated to 10 upon bootup. I'm trying to deal with two issues, one of which I believe is either the Google phone dialer stopping all other phone dialer recording programs from working with a message "call to short to record". Phone has an oem unlock feature in developer section and I see the bootloader is locked, and all research says OS 10 stops this from getting unlocked. After seeing absolutely zero posts on YouTube about downgrading a Nokia 7.2 to OS 9, and so many scam sites, I figure best option is to ask here.
Can a Nokia 7.2 be flashed down to OS 9 where bootloader can then be unlocked, or are all the posts I'm seeing, just wishful thinking fakes? Thanks.
Lord-Xanthor said:
Sorry for the necro, and not asking if phone can be rooted as wow, am not surprised how many asked already lol.
I purchased four unlocked Nokia 7.2 which forced updated to 10 upon bootup. I'm trying to deal with two issues, one of which I believe is either the Google phone dialer stopping all other phone dialer recording programs from working with a message "call to short to record". Phone has an oem unlock feature in developer section and I see the bootloader is locked, and all research says OS 10 stops this from getting unlocked. After seeing absolutely zero posts on YouTube about downgrading a Nokia 7.2 to OS 9, and so many scam sites, I figure best option is to ask here.
Can a Nokia 7.2 be flashed down to OS 9 where bootloader can then be unlocked, or are all the posts I'm seeing, just wishful thinking fakes? Thanks.
Click to expand...
Click to collapse
Hi, essentially the only way to downgrade a locked device is via a Nokia Care point or otherwise tools which can replicate what the Nokia Care tools do. All of these will have a price and unfortunately, no free way exists. You can opt for some remote services.
The tutorials on random websites will help in no way because a locked bootloader will not let you flash any device partitions, thereby disallowing downgrades as well. You cannot load an older OTA package from recovery mode because its date will mismatch.
singhnsk said:
Hi, essentially the only way to downgrade a locked device is via a Nokia Care point or otherwise tools which can replicate what the Nokia Care tools do. All of these will have a price and unfortunately, no free way exists. You can opt for some remote services.
The tutorials on random websites will help in no way because a locked bootloader will not let you flash any device partitions, thereby disallowing downgrades as well. You cannot load an older OTA package from recovery mode because its date will mismatch.ii
Click to expand...
Click to collapse
I don't mind paying.
singhnsk said:
Hi, essentially the only way to downgrade a locked device is via a Nokia Care point or otherwise tools which can replicate what the Nokia Care tools do. All of these will have a price and unfortunately, no free way exists. You can opt for some remote services.
The tutorials on random websites will help in no way because a locked bootloader will not let you flash any device partitions, thereby disallowing downgrades as well. You cannot load an older OTA package from recovery mode because its date will mismatch.
Click to expand...
Click to collapse
I have no trouble paying to get this done. It's finding the place to do it that's in the way. I called metro and tmobile and both said they don't offer this service. Least the ones in California I called. One site offered at $4.50 rollback and $8 to root and I am more wary of that then the free ones lol. Any suggestions to real places? Thanks for getting back.
Lord-Xanthor said:
I don't mind paying.
I have no trouble paying to get this done. It's finding the place to do it that's in the way. I called metro and tmobile and both said they don't offer this service. Least the ones in California I called. One site offered at $4.50 rollback and $8 to root and I am more wary of that then the free ones lol. Any suggestions to real places? Thanks for getting back.
Click to expand...
Click to collapse
I will edit this after, if this works so others can try as well. It's not free and is costing me $150 to do. Will update in a few weeks.