Related
Hey,
I've bought a G2. After I rooted it, I noticed the "rooted"-status in the downloadmode. I've read about it. I now fear that I can not exchange the unit if something is broken. The warranty is void?
So i tought about to send it back to amazon (14 days time to send it back) and get another phone?! Do you think this is ja good idea or stupid?
Thx for help.
I've never rooted a phone before but I read that when you successfully unroot the LG G2, the 'rooted' status goes away.
From what I've read, G2's bootloader is unlocked, so you can root and unroot withou LG knowing it. But take a look to the thread "return to stock".
yyz123 said:
I've never rooted a phone before but I read that when you successfully unroot the LG G2, the 'rooted' status goes away.
Click to expand...
Click to collapse
The problem is, that I can no longer unroot the device, when it should be broken. That is the real problem...
edit:
whit "another phone" i mean not a G2. i think i will buy the Sony Z1 or Htc One
I have reconsigned (returned?... send back... you know what i mean :silly: ) the device. I think I'll buy a Sony. So I have no problems with the root.
Cic3ro said:
I have reconsigned (returned?... send back... you know what i mean :silly: ) the device. I think I'll buy a Sony. So I have no problems with the root.
Click to expand...
Click to collapse
hope you don't mess the sony up! the g2 is a far better phone than the sony - if you root, you can unroot and the "rooted" returns to" unrooted" better luck next time
it sounds to me like you have messed your phone up and now you want to send it back and you expect a new one. if I was the person at the other end I would have voided your warranty and if you cant sort it im afraid you should not be flashing anything until you know what you are doing there are far too many people doing this and then returning their phones as "faulty" when basically they messed it up what happens when you do the same to the sony -will u just send that back as well- no wonder manufactures are making it more difficult for people to root in the first place please don't keep doing this as it just makes it worse for the rest of us,who flash stuff and know what they are doing--rant over, hope you take a little time to learn what you are doing in future.
martindar said:
hope you don't mess the sony up! the g2 is a far better phone than the sony - if you root, you can unroot and the "rooted" returns to" unrooted" better luck next time
it sounds to me like you have messed your phone up and now you want to send it back and you expect a new one. if I was the person at the other end I would have voided your warranty and if you cant sort it im afraid you should not be flashing anything until you know what you are doing there are far too many people doing this and then returning their phones as "faulty" when basically they messed it up what happens when you do the same to the sony -will u just send that back as well- no wonder manufactures are making it more difficult for people to root in the first place please don't keep doing this as it just makes it worse for the rest of us,who flash stuff and know what they are doing--rant over, hope you take a little time to learn what you are doing in future.
Click to expand...
Click to collapse
no haha. i think you don't understand me (or i'm to dopy to write understandable english....). the device is not broken. i was thinking about, what could happen, if the device is broken and rooted. i know how to root or flash some rom. that is not my problem. the problem is, that LG has a rootchecker and Sony literally allows the root and flashing roms without unlocking the bootloader. this is why i want to send the G2 back and buy a new Z1.
Cic3ro said:
no haha. i think you don't understand me (or i'm to dopy to write understandable english....). the device is not broken. i was thinking about, what could happen, if the device is broken and rooted. i know how to root or flash some rom. that is not my problem. the problem is, that LG has a rootchecker and Sony literally allows the root and flashing roms without unlocking the bootloader. this is why i want to send the G2 back and buy a new Z1.
Click to expand...
Click to collapse
To my understanding most of the newer devices have indicators buried in the settings to list rooted.
As long as the device powers on you can unroot the LG with the return to stock method and it will show unrooted. You just boot into download mode, and run the tools listed.
If it doesn't power on... then does it matter? It wouldn't be viewable under standard warranty anyways.
Enjoy the other phone if that's your choice, but you made a poor one IMHO.
digitard said:
To my understanding most of the newer devices have indicators buried in the settings to list rooted.
As long as the device powers on you can unroot the LG with the return to stock method and it will show unrooted. You just boot into download mode, and run the tools listed.
If it doesn't power on... then does it matter? It wouldn't be viewable under standard warranty anyways.
Enjoy the other phone if that's your choice, but you made a poor one IMHO.
Click to expand...
Click to collapse
Agreed but it still shows rooted in download mode after going back to stock.
fr8cture said:
Agreed but it still shows rooted in download mode after going back to stock.
Click to expand...
Click to collapse
I don't believe so.
I have the ATT version, and I nuked it with a bad flash and a brain fart that caused me to forget to backup first in TWRP.
I couldn't get anything on the device so I did the restore to stock using the flash tool, and when I was done I'm pretty sure it showed green until I rooted it again.
digitard said:
I don't believe so.
I have the ATT version, and I nuked it with a bad flash and a brain fart that caused me to forget to backup first in TWRP.
I couldn't get anything on the device so I did the restore to stock using the flash tool, and when I was done I'm pretty sure it showed green until I rooted it again.
Click to expand...
Click to collapse
Ah mine showed rooted but I tried the back to stock for all variants and it didn't work (worked the first time not the second) so then I did the vzw only back to stock and that worked but still showed rooted in download mode.
After the unroot yesterday the "rooted" in the downloadmode was gone too
Hello everyone, this is my first post, the one issue that made me register
Ill be as short as i can :
I have a sony xperia P t-mobile locked so:
-Bootloader locked,
-root goes up no problem, works,
-CWM goes up this one,works:
http://forum.xda-developers.com/showthread.php?t=2020895
-i copy the rom on the phone, factory reset all that junk, i start to flash i get the "getprop nypon" aka Status 7 error code(tried several roms, all do the same)
-i go and modify the upgrade script via this method http://forum.xda-developers.com/showthread.php?t=2302599
The rom installs, i install the gapps and whatnot and when i go to reboot it goes brick, i can get it to vibrate for hard reset but thats all(luckily the xperia updater software recovers so its not bricked out atm) but thats all, no other response no sony logo no nothing.
I was trying to flash the CM11 nightly to my phone, and i dont have a clue what have gone wrong... any ideas? should i try another one? did i mess up the flashscript modifying?(i checked for space) Any input and suggestion is highly appreciated, thank you in advance!!
TheGregButcher said:
Hello everyone, this is my first post, the one issue that made me register
Ill be as short as i can :
I have a sony xperia P t-mobile locked so:
-Bootloader locked,
-root goes up no problem, works,
-CWM goes up this one,works:
http://forum.xda-developers.com/showthread.php?t=2020895
-i copy the rom on the phone, factory reset all that junk, i start to flash i get the "getprop nypon" aka Status 7 error code(tried several roms, all do the same)
-i go and modify the upgrade script via this method http://forum.xda-developers.com/showthread.php?t=2302599
The rom installs, i install the gapps and whatnot and when i go to reboot it goes brick, i can get it to vibrate for hard reset but thats all(luckily the xperia updater software recovers so its not bricked out atm) but thats all, no other response no sony logo no nothing.
I was trying to flash the CM11 nightly to my phone, and i dont have a clue what have gone wrong... any ideas? should i try another one? did i mess up the flashscript modifying?(i checked for space) Any input and suggestion is highly appreciated, thank you in advance!!
Click to expand...
Click to collapse
And why exactly are you trying to flash a rom that is for unlocked bootloader only?
No CMs for you., stock based ROMs only..
ChikeD said:
And why exactly are you trying to flash a rom that is for unlocked bootloader only?
No CMs for you., stock based ROMs only..
Click to expand...
Click to collapse
Thanks i knew i was overlooking something... i didnt even know you cant flash "random" stuff with a locked bootloader.
By the way is there a method around this? i failed to find any.
TheGregButcher said:
Thanks i knew i was overlooking something... i didnt even know you cant flash "random" stuff with a locked bootloader.
By the way is there a method around this? i failed to find any.
Click to expand...
Click to collapse
You can't "flash", as this feature in the BIOS, but you can do virtually anything you want with your phone once you have root permission.
Is your bootloader unlockable?
ChikeD said:
You can't "flash", as this feature in the BIOS, but you can do virtually anything you want with your phone once you have root permission.
Is your bootloader unlockable?
Click to expand...
Click to collapse
Sadly no, mine is carrier locked so its bootloader locked as well( if i could i would have did it already) thats what im asking, is there even a method to unlock a not unlockable bootloader? some nifty dark alleyway backdoor etc... way?
TheGregButcher said:
Sadly no, mine is carrier locked so its bootloader locked as well( if i could i would have did it already) thats what im asking, is there even a method to unlock a not unlockable bootloader? some nifty dark alleyway backdoor etc... way?
Click to expand...
Click to collapse
Hmmmm, have you checked in service menu?
There might be unofficial method, I don't know if it's for unlockable bootloader.
Luckily, here it's not allowed bind users to service anymore, and carriers must unlock it if the owner of the phone request it.
ChikeD said:
Hmmmm, have you checked in service menu?
There might be unofficial method, I don't know if it's for unlockable bootloader.
Luckily, here it's not allowed bind users to service anymore, and carriers must unlock it if the owner of the phone request it.
Click to expand...
Click to collapse
yep i checked the service menu thats why i know its not unlockable. i might try to get in touch with t-mobile support and ask them for an unlock code... the only ones i found on the internet, costed quite a sum of money. anyway, i wouldnt even bother with it that much, the speed is acceptable and im okay with the default sony interface, but the phone app freaking out and freezing a lot makes me a bit angry about it...
TheGregButcher said:
yep i checked the service menu thats why i know its not unlockable. i might try to get in touch with t-mobile support and ask them for an unlock code... the only ones i found on the internet, costed quite a sum of money. anyway, i wouldnt even bother with it that much, the speed is acceptable and im okay with the default sony interface, but the phone app freaking out and freezing a lot makes me a bit angry about it...
Click to expand...
Click to collapse
You mean the phone lag issue with incoming/outgoing calls?
It's not too bad in firmware 6.2.A.1.100.
ChikeD said:
You mean the phone lag issue with incoming/outgoing calls?
It's not too bad in firmware 6.2.A.1.100.
Click to expand...
Click to collapse
Yes i mean that. Its not that bad and a complete off/on solves it for a while, still it cripples the main usage of a phone...it can be quite annoying when it ballses up when you need to make an urgent phonecall...
TheGregButcher said:
Yes i mean that. Its not that bad and a complete off/on solves it for a while, still it cripples the main usage of a phone...it can be quite annoying when it ballses up when you need to make an urgent phonecall...
Click to expand...
Click to collapse
Yes that's true, I realy wonder why sony did not fix that yet.
For me it's first of all a phone, the rest is just etras.
Hi all. Please excuse if this has been asked (and answered), but I just spent two days with this phone and have just about torn my hair out.
I have a Verizon S4 (SCH-I545). I got it second-hand, so I don't know if the previous owner took any OTA updates. I wanted to put CM12 on it. However, in that thread, it's made very clear that it won't work without being on the MDK bootloader.
Well, when I execute the command "getprop ro.bootloader" from within Safestrap, I get "I545VRUFNC5".
Obviously, this is not MDK. Is this a bootloader that came after MDK as part of an OTA update? Either way, am I no longer able to Odin flash the MDK bootloader?
Thanks in advance.
Yes..This Bootloader is newer, and locked and cannot be reverted using ODIN. You would need to find a manual copy/change method to revert the Bootloader.
Sent from my SCH-I545 using Tapatalk
Hi KaosMaster. Thanks for your quick reply. So, does a manual copy/change method exist? You can probably surmise that I tried Odin'ing several stock ROMs with MDK packaged in and each one failed for various reasons. Can I do this copy/change action or would Verizon themselves have to do it? If the latter, would they do it without charging me a small fortune?
While I'm on the subject, are there any other gotchas you know of regarding this I545VRUFNC5 bootloader? What other ROMs won't work with it?
Thanks again!
Odin Won't work.
JTAG won't work(tested, phone bricks)
nc5 has root and safestap + limited ROMs with a touchwiz base
Some ROMs:
Hyperdrive
Echoe
Super6 Port
KitPop
Eclipse
Hi XxD34THxX. When you say the phone bricks using JTAG, do you mean it brick bricks? As in, turning the phone into a doorstop?
Do you know if Verizon would revert it back if you made such a request? If so, would it cost anything?
Well... with JTAG, I am pretty sure it turns into a soft brick. I can't confirm.
BWAHAHAHAHAHAHAH
Verizon will just laugh in your face if you asked them that.
XxD34THxX said:
Well... with JTAG, I am pretty sure it turns into a soft brick. I can't confirm.
BWAHAHAHAHAHAHAH
Verizon will just laugh in your face if you asked them that.
Click to expand...
Click to collapse
Arggh! Locked bootloaders are a complete and utter PITA.
What I don't understand is why CM12 requires a specific bootloader to function. To me, that sounds like Windows needing a specific BIOS or bootstrap to work.
Does CM10 have this requirement as well?
BTW, thanks for the rom list. I'll definitely check 'em out.
Yes, it needs an unlocked bootloader(any CM). It DOES need a specific bootstrap to work...
fleggett1 said:
Arggh! Locked bootloaders are a complete and utter PITA.
What I don't understand is why CM12 requires a specific bootloader to function. To me, that sounds like Windows needing a specific BIOS or bootstrap to work.
Does CM10 have this requirement as well?
BTW, thanks for the rom list. I'll definitely check 'em out.
Click to expand...
Click to collapse
Unfortunately you are stuck as no one has successfully downgraded the bootloader. Many developers have tried without success.
CyanogenMod will only work on an MDK device because the kernel is replaced during the flash process. This can only be accomplished with a custom recovery or unlocked bootloader.
FWIW, the MDK bootloader is technically not unlocked. There is a process called "loki" that took advantage of an exploit that was present on MDK which allowed the installation of a custom recovery. It did not unlock or overwrite the MDK recovery.
All bootloader versions past MDK have had this exploit closed.
Do we know if the Marshmallow update updates the bootloader?
Our current root method uses an exploited 5.1 system, so it will not work on 6.0. Someone will need to use a similar exploit on the 6.0 system if the exploit does indeed still work.
If the bootloader is not updated with 6.0, we will be able to go back to 5.1 simply by flashing the 5.1 system. If it is updated, we may have lost root for forever. I will stick with 5.1 for now and I will take the Marshmallow update this Sunday if there is no additional information.
Any way to update to MM if you are using a Verizon V10 on AT&T?
jabreu203 said:
Any way to update to MM if you are using a Verizon V10 on AT&T?
Click to expand...
Click to collapse
you can use the kdz but it's nowhere to be seen
I'm in the same boat with a T-Mobile sim. Waiting for a kdz to get onto Marshmallow.
If you tell me how I can do it.
Unfortunately I clicked update now. :/ I dont know too much but if you tell me how to discover this info I will definitely tell you if the boot loader is adjusted with the update.
jalthejew said:
Unfortunately I clicked update now. :/ I dont know too much but if you tell me how to discover this info I will definitely tell you if the boot loader is adjusted with the update.
Click to expand...
Click to collapse
You should be able to find the bootloader version in a benchmark app, then I could do the same
The bootloader does not actually need to be unlocked at all to root the device. All you need is the KDZ file and some experienced hacking to do it. That's how we got root for the V10 anyways.
i have a weird question to ask. i am using att sim card on a Verizon v10. can i flash a kdz att or even the unlocked version system on the Verizon variant ?
If I'm not mistaken the boot loader for the Verizon Lg G3 wasn't unlocked, they just had to work around that.
hann1balk1ng said:
If I'm not mistaken the boot loader for the Verizon Lg G3 wasn't unlocked, they just had to work around that.
Click to expand...
Click to collapse
I was about to say 'Yes they did, I had twrp and custom roms...' but then I powered it up and remembered they had to use the 'Bump Method' to install twrp alongside the default bootloader and recovery. If you powered on while holding volume down you'd get the default lg recovery, but then if you went to factory reset from there and clicked yes it brought up twrp. So yea, a pretty interesting work around there.
kjcsg said:
I was about to say 'Yes they did, I had twrp and custom roms...' but then I powered it up and remembered they had to use the 'Bump Method' to install twrp alongside the default bootloader and recovery. If you powered on while holding volume down you'd get the default lg recovery, but then if you went to factory reset from there and clicked yes it brought up twrp. So yea, a pretty interesting work around there.
Click to expand...
Click to collapse
@thecubed @IllegalArgument @autoprime @Shelnutt2 @Dees_Troy
Maybe these devs can help if they are still around and have access to a Verizon LG V10 with root and are willing to spend the time to try and help out this thread...
burnsky05 said:
@thecubed @IllegalArgument @autoprime @Shelnutt2 @Dees_Troy
Maybe these devs can help if they are still around and have access to a Verizon LG V10 with root and are willing to spend the time to try and help out this thread...
Click to expand...
Click to collapse
Lets hope so.....
burnsky05 said:
@thecubed @IllegalArgument @autoprime @Shelnutt2 @Dees_Troy
Maybe these devs can help if they are still around and have access to a Verizon LG V10 with root and are willing to spend the time to try and help out this thread...
Click to expand...
Click to collapse
They might not be so inclined. IIRC, they were rightly agitated when someone open-sourced their work, potentially making it easier for manufacturers to prevent in the future, despite them specifically advising against it.
kjcsg said:
I was about to say 'Yes they did, I had twrp and custom roms...' but then I powered it up and remembered they had to use the 'Bump Method' to install twrp alongside the default bootloader and recovery. If you powered on while holding volume down you'd get the default lg recovery, but then if you went to factory reset from there and clicked yes it brought up twrp. So yea, a pretty interesting work around there.
Click to expand...
Click to collapse
The bootloader was still locked, its just that the images were signed to make the boot loader think they were signed.
NetworkingPro said:
The bootloader was still locked, its just that the images were signed to make the boot loader think they were signed.
Click to expand...
Click to collapse
And the original recovery was was modified or somehow the bump script hijacked the factory reset process to divert to twrp. I wonder if the bump script can be modified with the correct paths and info such as pplus instead of vs985.
kjcsg said:
And the original recovery was was modified or somehow the bump script hijacked the factory reset process to divert to twrp. I wonder if the bump script can be modified with the correct paths and info such as pplus instead of vs985.
Click to expand...
Click to collapse
It really wasn't that complicated, honestly. All bump did was sign certain bytes like LG to make the bootloader think TWRP was a truly signed image. The same applied to kernels, or anything else that was bumped. When you flashed the newly bumped recovery image you were literally replacing the factory one.
NetworkingPro said:
It really wasn't that complicated, honestly. All bump did was sign certain bytes like LG to make the bootloader think TWRP was a truly signed image. The same applied to kernels, or anything else that was bumped. When you flashed the newly bumped recovery image you were literally replacing the factory one.
Click to expand...
Click to collapse
My only question then is why would they leave the original, the lg recovery, there when you would power on while holding volume down and have to go through the factory reset button to get to twrp instead of just overwriting the original with twrp completely? Not that it matters too much, I just wish I knew how to do it so I could get the vs990 bumped or somehow get twrp on it. But I think I'd need a good bit of exploit schooling to understand it all haha.
I hope we get at least recovery soon, but I've never understood why recoveries never have a text editor included! (and often not even shell access, much less SU shell access!)
Hi,
I tried to upgrade my US998 from Oreo to Pie using LGUP patched. The upgrade process went well until the phone restarted and have this error message:
"Your device has failed a routine safety check and will not boot..."
I did try using LG Bridge to fix = not working
I did try fastboot boot laf.img (using extracted laf from H93031a_00_OPEN_EU_OP_1105) not working.
Any other solution?
Thanks
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
JanBoyGamer23 said:
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
Click to expand...
Click to collapse
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
jaacoozee said:
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
Click to expand...
Click to collapse
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
JanBoyGamer23 said:
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
Click to expand...
Click to collapse
I'm not sure. Normally I access download mode using volume up and power button. The download mode was there for a sec and then the screen back to
"Your device has failed a routine safety check and will not boot..."
again.
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
JanBoyGamer23 said:
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
Click to expand...
Click to collapse
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
JanBoyGamer23 said:
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
Click to expand...
Click to collapse
Unfortunately my LG V30 is US region. The official bootloader site not support my phone. Thanks for your info anyway
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
schwinn8 said:
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
Click to expand...
Click to collapse
Thanks for the reply.
I didnt install TWRP or any recovery tools to my phone. My phone bootloader still locked thou.
I have read the WTF thread but the problem is I cant get into my Download mode.
Ok, what steps are you using to try to get into download mode? Presumably turning off the phone, then holding the volume up button and plugging in the USB cable (other end already connected to a Windows computer), correct? If that doesn't work, can you try other USB cables? Sometimes a bad cable could prevent the phone from going into download mode.