Related
I got the update and it is downloaded b/c I see it in the recovery mode. I scroll down to install update, but it will not work.
My phone is rooted, I have CWM, and it is unlocked. How can I get my update completed? I really want to keep stock right now. I don't want to keep checking up on updated ROM's , etc...
Thanks so much. Please - if you respond, break it down easy. step by step. That is what I need. Basics. thanks.
i<3myphone said:
I got the update and it is downloaded b/c I see it in the recovery mode. I scroll down to install update, but it will not work.
My phone is rooted, I have CWM, and it is unlocked. How can I get my update completed? I really want to keep stock right now. I don't want to keep checking up on updated ROM's , etc...
Thanks so much. Please - if you respond, break it down easy. step by step. That is what I need. Basics. thanks.
Click to expand...
Click to collapse
the update will only install with the stock recovery.
i<3myphone said:
I got the update and it is downloaded b/c I see it in the recovery mode. I scroll down to install update, but it will not work.
My phone is rooted, I have CWM, and it is unlocked. How can I get my update completed? I really want to keep stock right now. I don't want to keep checking up on updated ROM's , etc...
Thanks so much. Please - if you respond, break it down easy. step by step. That is what I need. Basics. thanks.
Click to expand...
Click to collapse
As far as my knowledge goes. You wont be able to install OTA's on rooted GN.
Edit
Answer was already given
Heppieboeddah said:
As far as my knowledge goes. You wont be able to install OTA's on rooted GN.
Edit
Answer was already given
Click to expand...
Click to collapse
It's CWM recovery that messes it up not root.
jhuynh said:
It's CWM recovery that messes it up not root.
Click to expand...
Click to collapse
Assumption is the mother of all **** ups...so i assumed that if you are rooted the most common thing is that you have CWM installed...
So how do I get there from here? Do I need to uninstall something and then do the update??
Thanks for the help.
i<3myphone said:
So how do I get there from here? Do I need to uninstall something and then do the update??
Thanks for the help.
Click to expand...
Click to collapse
you could fastboot the stock recovery in...but you might as well fastboot the latest images from google if you do that
ogdobber said:
you could fastboot the stock recovery in...but you might as well fastboot the latest images from google if you do that
Click to expand...
Click to collapse
Ok, I can try that. How do I do that? I am not sure I am familiar with fastboot. I can follow step by step instructions though.
Did you try the instructions on this thread?
http://forum.xda-developers.com/showthread.php?t=1419170&highlight=ota+update
You seem to have the same set up as I do. I've just updated no problem with method 1.
The only instruction missing is that you have to re-root afterwards (you can check with Titanium).
When re-rooting, it got stuck on the Google image. I disconnected from the computer and pulled the battery out. restarted and voilá, all done
ogdobber said:
the update will only install with the stock recovery.
Click to expand...
Click to collapse
Heppieboeddah said:
As far as my knowledge goes. You wont be able to install OTA's on rooted GN.
Edit
Answer was already given
Click to expand...
Click to collapse
jhuynh said:
It's CWM recovery that messes it up not root.
Click to expand...
Click to collapse
Heppieboeddah said:
Assumption is the mother of all **** ups...so i assumed that if you are rooted the most common thing is that you have CWM installed...
Click to expand...
Click to collapse
As I'm sure you all have read the post above this one, neither CWM nor root prevent you from receiving the OTA update. CWM, however, will prevent it from automatically installing, but CWM can easily install the OTA. See link in post above.
---------- Post added at 01:28 PM ---------- Previous post was at 01:21 PM ----------
ogdobber said:
you could fastboot the stock recovery in...but you might as well fastboot the latest images from google if you do that
Click to expand...
Click to collapse
Yes, but if you flash the latest images, you will lose all your data...
I tried doing it via CWM. It was aborted. I just went ahead and uploaded a ROM. The Android Revolution HD one. I kinda gave up trying to do the OTA myself. Thanks for hte help anyway.
efrant said:
As I'm sure you all have read the post above this one, neither CWM nor root prevent you from receiving the OTA update. CWM, however, will prevent it from automatically installing, but CWM can easily install the OTA. See link in post above.
---------- Post added at 01:28 PM ---------- Previous post was at 01:21 PM ----------
Yes, but if you flash the latest images, you will lose all your data...
Click to expand...
Click to collapse
How do I root my Galaxy Nexus on firmware 4.0.4 and a GSM model
thomaswackers said:
How do I root my Galaxy Nexus on firmware 4.0.4 and a GSM model
Click to expand...
Click to collapse
Flash Superuser (Link)
I tried flashing su.zip and it works, however apps are not asking for root permission anymore. Instead they just freeze or say they can't run privileged commands
EDIT: adfree for example will just run as if nothing was wrong, but it doesn't actually update the hostfile, and Superuser doesn't show AdFree in the list of apps
It just seems as if none of the apps are asking for superuser permissions anymore.
veinripper said:
I tried flashing su.zip and it works, however apps are not asking for root permission anymore. Instead they just freeze or say they can't run privileged commands
EDIT: adfree for example will just run as if nothing was wrong, but it doesn't actually update the hostfile, and Superuser doesn't show AdFree in the list of apps
It just seems as if none of the apps are asking for superuser permissions anymore.
Click to expand...
Click to collapse
Try to clear data and cache from SU. Are you sure you flashed the latest version? See link? If that does not help maybe delete and reinstall.
Sent from my Galaxy Nexus using xda premium
Diger36 said:
Try to clear data and cache from SU. Are you sure you flashed the latest version? See link? If that does not help maybe delete and reinstall.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I finally fixed, you were right, it was an older version. I went on the superuser website and got this version: Superuser-3.0.7-efghi-signed.zip
I would post a link but I don't have enough posts.
Flashed in recovery and it works now.
thanks
veinripper said:
I finally fixed, you were right, it was an older version. I went on the superuser website and got this version: Superuser-3.0.7-efghi-signed.zip
I would post a link but I don't have enough posts.
Flashed in recovery and it works now.
thanks
Click to expand...
Click to collapse
No problem mate, and the link was in the second post
Sent from my Galaxy Nexus using xda premium
When you say flash, do you mean through CWM? And if so could I flash a temp CWM so I can just flash this?
jonnyg1097 said:
When you say flash, do you mean through CWM? And if so could I flash a temp CWM so I can just flash this?
Click to expand...
Click to collapse
Yes and Yes (although I didn't try the last one but it should work)
Diger36 said:
Yes and Yes (although I didn't try the last one but it should work)
Click to expand...
Click to collapse
Cool thanks!
Diger36 said:
Yes and Yes (although I didn't try the last one but it should work)
Click to expand...
Click to collapse
How do I 'flash'
with Clockworkmod recovery
I tried to flash through cwm su.zip and gave an error, something with 0 . How do I do it manually?
I tried to install latest version of Super user, but i get error status 0 in CWM.. Help please
How to install cwm recovery? I just flashed my nexus with stock 4.0.4 and flash this kernel..
Check my sig, kids.
Make sure to follow gsm/cdma downloads and you'll be butter.
OK I'm not sure which update broke my root, but I am on IMM67I
I noticed too that in the superuser app there were no requests, and when going into a terminal and typing su I get 'permission denied'.
First port of call was superboot v4.. that hung at the google screen. Then I temp booted CWM and flashed su_ICS_GN.zip...
Once booted still no access in terminal (permission denied), so I deleted su and superuser.apk (how? Surely I need su to delete these?), then flashed again.. exactly the same.
Downloaded the linked file above and got:
Error in Superuser-3.0.7-efghi-signed.zip
(status 0)
installation aborted
Incidentally, this is the same version of su that is in su_ICS_GN.zip
When going into superuser and trying to update the binary, it says 'cant get root'..
Downloaded just the binary only and get exactly the same as above (installation aborted). Looked at the update_script and cannot see anything wrong....
I've just tried to boot an unsecure image so I can push the new su binary.... stuck at the Google screen...
Very confused...
---------- Post added at 10:59 AM ---------- Previous post was at 10:45 AM ----------
OK I used the 'Galaxy Nexus Toolkit' which must have an updated insecure image I guess to push the right su binary..
I had to manually get it into bootloader mode as it didnt reboot (even though it detected the phone at adb).... and then the script continued OK..
i have unlocked Sir G nexus , unlocked with odin method by chainfire (after install 4.0.4 my phone get unlcoked fortunately )
i have andoid system recovery <3e> and there is apply update from cache !
and when i go into it there isnt any file i can update .
i can not root my device now , some giude tells me use some command prompt to flash , that i can not find it either !
i had been through so much **** to buy this phone and dont want to ruin in with ignorance , due to this can any one that root his device tell me how to do it . i really appreciate anyone one read this message
another question is about boot loader unlocking .
my boot loader unlocked by odin method installing 4.0.4 (chainfire)
is there any different between the toolkit unlocked phone and my locked phone , i said above
afraaa said:
i have unlocked Sir G nexus , unlocked with odin method by chainfire (after install 4.0.4 my phone get unlcoked fortunately )
i have andoid system recovery <3e> and there is apply update from cache !
and when i go into it there isnt any file i can update .
i can not root my device now , some giude tells me use some command prompt to flash , that i can not find it either !
i had been through so much **** to buy this phone and dont want to ruin in with ignorance , due to this can any one that root his device tell me how to do it . i really appreciate anyone one read this message
Click to expand...
Click to collapse
fount it myself no need to answer this
---------- Post added at 09:06 PM ---------- Previous post was at 09:03 PM ----------
afraaa said:
another question is about boot loader unlocking .
my boot loader unlocked by odin method installing 4.0.4 (chainfire)
is there any different between the toolkit unlocked phone and my locked phone , i said above
Click to expand...
Click to collapse
found it my selft ,,,, no need to answer this
Wth are you talking about? Unlock bootloader with odin?
Only way i know is with fastboot.
sent from my i9250
Root all samsung g925a g928a g920a ver 5.1.1
ALl version can root with out suppersu
If you want grand check root add binary you need find how add binary to system
Use command adb
adb shell mount mount -o rw,remount /system
then you can push binary suppersu to system.
Donate : CLICK
Link download: https://docs.google.com/uc?id=0B8mSVItI_cqRcXpsTzd1cGlVaDg&export=download
pass team6
use odin flash
after Chimera last night I'm gonna wait on this one a bit... fingers are crossed and hoping it's legit.
Is this working withe the A01J firmware or does it need to be downgraded to AOGG then be flashed?
because i found the same file associated with N920AUCE2APB2 firmware , which is based on mashmallow. So i guess this will be useless for devices with lollipop
maheshwar said:
Is this working withe the A01J firmware or does it need to be downgraded to AOGG then be flashed?
because i found the same file associated with N920AUCE2APB2 firmware , which is based on mashmallow. So i guess this will be useless for devices with lollipop
Click to expand...
Click to collapse
you can test 6.0 do not worry brick if you have stock file android 6.0 extract boot build tar if flash fail root only flash boot stock again done.
tungkick said:
you can test 6.0 do not worry brick if you have stock file android 6.0 extract boot build tar if flash fail root only flash boot stock again done.
Click to expand...
Click to collapse
you got Dl links to the stock boot.img file ?
It would be awesome if this works..
Instructions unclear...hoping someone gives this a try. Also hoping it's not system-less so we are able to use root apps.
Sent from my SAMSUNG-SM-N920A using Tapatalk
any update on this?
blane3298 said:
any update on this?
Click to expand...
Click to collapse
Waiting for the official MM update to try it out since this file is based on MM
tungkick said:
Root all samsung g925a g928a g920a ver 5.1.1
ALl version can root with out suppersu
If you want grand check root add binary you need find how add binary to system
Use command adb
adb shell mount mount -o rw,remount /system
then you can push binary suppersu to system.
Donate : CLICK
Link download: https://docs.google.com/uc?id=0B8mSVItI_cqRcXpsTzd1cGlVaDg&export=download
pass team6
use odin flash
Click to expand...
Click to collapse
total noob question, but how do you push the binary? where do you push it in CMD? just a little new to this. Thanks!:fingers-crossed:
cellit801 said:
total noob question, but how do you push the binary? where do you push it in CMD? just a little new to this. Thanks!:fingers-crossed:
Click to expand...
Click to collapse
you need android sdk and stuff
cellit801 said:
total noob question, but how do you push the binary? where do you push it in CMD? just a little new to this. Thanks!:fingers-crossed:
Click to expand...
Click to collapse
try kingroot can add binary.
Can any one confirm this work on this N920AUCE2APB2 firmware?
I tried it on the firmware just prior to this one. It was not full root. It seemed more of a core root. There was no Su capability. I would not be surprised if it did not work on your current firmware as I believe it to be the security patch for this root method
Check out the about those root files. You can root with the method founds.
Took a cursory look. Seems a bit complicated, but will investigate further when time permits. Thanks for the direction.
Can you provide more directions with the methods involved tried the cmd but kept saying about (missing apk)?. Don't know what that means. Can you assist?
---------- Post added at 10:19 PM ---------- Previous post was at 10:17 PM ----------
mmjs14 said:
Can you provide more directions with the methods involved tried the cmd but kept saying about (missing apk)?. Don't know what that means. Can you assist?
Click to expand...
Click to collapse
Meant reply towards TechNyne66
mmjs14 said:
Can you provide more directions with the methods involved tried the cmd but kept saying about (missing apk)?. Don't know what that means. Can you assist?
---------- Post added at 10:19 PM ---------- Previous post was at 10:17 PM ----------
Meant reply towards TechNyne66
Click to expand...
Click to collapse
If you are having problems I can help over a Facebook video chat. Root works with apps and all. Just teathered for now.
TechNyne66 said:
If you are having problems I can help over a Facebook video chat. Root works with apps and all. Just teathered for now.
Click to expand...
Click to collapse
Hey I am having some issues following his instructions do you mind sending me instructions on how to go through this process. I have some background with rooting but mostly htc and LG rooting I have always ran into issues with rooting samsungs. And I don't have time for a video chat, so much on my plate right now.
hairyson said:
Hey I am having some issues following his instructions do you mind sending me instructions on how to go through this process. I have some background with rooting but mostly htc and LG rooting I have always ran into issues with rooting samsungs. And I don't have time for a video chat, so much on my plate right now.
Click to expand...
Click to collapse
Send me a pm, I sucks at using forms.
So i have a twrp-3.2.0-m8.img flashed as the custom recovery which works fine. I tried to install SuperSU and got the binaries error of which i downloaded a much newer version and flashed it through twrp. From flashing it, this has screwed up my phone and i can only boot into hboot and recovery. When i try to boot it normally, it just stays on the HTC boot screen with the green and black text. How can i fix it back to normal or root it correctly?
Just restore your backup ... you should already make one before you tried to root it.
Post here fastboot getvar all result without serial & imei no then we'll see what you need.
ChiefMustardo said:
So i have a twrp-3.2.0-m8.img flashed as the custom recovery which works fine. I tried to install SuperSU and got the binaries error of which i downloaded a much newer version and flashed it through twrp. From flashing it, this has screwed up my phone and i can only boot into hboot and recovery. When i try to boot it normally, it just stays on the HTC boot screen with the green and black text. How can i fix it back to normal or root it correctly?
Click to expand...
Click to collapse
When I helped you previously, I had to advise you to provide the proper details. So why are you repeating the same mistakes here? You need to help us help you, by posting the proper details.
In addition to the getvar output requested by ckpv5, what versions of SuperSU did you use? "Much newer version" doesn't really tell us anything (at least not specific enough for us to help you).
Your current firmware version greatly affects what version TWRP and SuperSU you need to use to avoid problems that you mentioned (no boot). So we can't begin to properly help, until you provide the proper info.
Additionally, you started another thread asking same/related questions. I won't respond to that thread, as making multiple threads (for related issues) is confusing and will only cause more problems (such as hopping back and forth between the threads). Bump your existing thread, if you have to (and asking subsequent questions in that existing thread is an acceptable way of doing that). But please don't make more threads. I have some input on the specific questions you asked in the other thread:
ChiefMustardo said:
Can someone please explain to me why when i use twrp or cwm no ROM installs and the md5 check fails as does the signature verification and it says that the zip file is corrupt. It isn't because i got it from the skydragon website.
Click to expand...
Click to collapse
Can't say for sure why TWRP is failing, until you provide the getvar info. It can be a mismatch between your current firmware and the TWRP version. But we have no way of telling, unless you provide the requested details.
And are you trying to use multiple TWRP versions, or just the one mentioned? And BTW, there is no TWRP 3.2.0, so I assume you mean 3.0.2, but please confirm.
Also, I would avoid CWM, as it hasn't been updated in a very long time, which can create a lot of issue in itself.
What is the exact file name, or Skydragon version of the ROM you are trying to install (also very important)?
Just because you downloaded from Skydragon website, does not exclude the possibility the file is corrupt. A perfectly working file can get corrupted during download to your phone/computer. Try downloading twice, to eliminate that as a possibility.
You should also turn off MD5 verification in TWRP; which is probably causing the MD5 error (as mentioned by dottat here). MD5 check typically not used for ROMs (particularly if there was no MD5 hash code supplied with the ROM).
Here is my fastboot getvar all
http://prntscr.com/bd24cj
ChiefMustardo said:
Here is my fastboot getvar all
http://prntscr.com/bd24cj
Click to expand...
Click to collapse
It was also the SuperSU 2.46
ChiefMustardo said:
It was also the SuperSU 2.46
Click to expand...
Click to collapse
Skydragon: SkyDragon+M8+v4.0.0+Sense+8+MM
TWRP: twrp-3.0.2-0-m8
Philz touch: philz_touch_6.26.6-m8
1. You used wrong TWRP recovery 2.7.x.x that make your version-main now empty.
2. You installed wrong SuperSU - 2.46 is NOT for Marshmallow.
3. When you install a custom ROM, it is pre-rooted, no need to root before or after the ROM installation.
I suggest you revert to stock first then redo the whole thing ... rooting or installing a custom ROM, these you can do later after you fix your phone.
Read this for the drivers - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
And this for installing RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Once it is back to stock, unlock the bootloader again with the unlock_code.bin that you received from htc. If it is not working, apply for a new one.
Once unlocked and after first boot and run setup & everything - install TWRP 3.0.2-0
then install custom ROM (no need to install SuperSU)
ChiefMustardo said:
It was also the SuperSU 2.46
Click to expand...
Click to collapse
That version is really old, released about Feb 2015!
SuperSU 2.65 is recommended. Anything older than 2.52 or so does not include the ability to root MM, and will fail with no boot/boot loop.
---------- Post added at 12:26 PM ---------- Previous post was at 12:24 PM ----------
ckpv5 said:
3. When you install a custom ROM, it is pre-rooted, no need to root before or after the ROM installation.
Click to expand...
Click to collapse
That is true, its not clear what the OP is currently trying to accomplish. This thread started out asking about root (stock ROM?) than started another thread asking about custom ROMs.
Its one or the other, not both (root vs. custom ROM) since as you mention, custom ROMs are already rooted.
I have tried using RUU to get it back to stock but it gets stuck in the updating 0/7 screen
ChiefMustardo said:
I have tried using RUU to get it back to stock but it gets stuck in the updating 0/7 screen
Click to expand...
Click to collapse
Just kill the process, and start it again. This is a reported issue for some folks.
If the issue reoccurs, we may have to look at USB connection issues.
Are you using the RUU zip method that ckpv5 directed in Post #7 above?
The RUU method you have suggested seems like it isworking.
The RUU worked thank you so much. Now to install SkyDragon ROM.
I tried the RUU.exe multiple times but that didn't work but yeah, ckpv5's method has worked. It is on Optimizing 44 of 153
ChiefMustardo said:
I tried the RUU.exe multiple times but that didn't work but yeah, ckpv5's method has worked.
Click to expand...
Click to collapse
The .exe is finicky. Anything but Windows 7 and USB 2.0 can cause problems with its USB connectivity. The zip method is more reliable (as you've seen).
It worked. How do i install a custom ROM? Do i get twrp 3.0.2 then install the zip from that? Also, do i keep my bootloader locked or unlock it?
ChiefMustardo said:
It worked. How do i install a custom ROM? Do i get twrp 3.0.2 then install the zip from that? Also, do i keep my bootloader locked or unlock it?
Click to expand...
Click to collapse
Read again : http://forum.xda-developers.com/showpost.php?p=67197327&postcount=7
Clearly stated :
ckpv5 said:
Once it is back to stock, unlock the bootloader again with the unlock_code.bin that you received from htc. If it is not working, apply for a new one.
Once unlocked and after first boot and run setup & everything - install TWRP 3.0.2-0
then install custom ROM (no need to install SuperSU)
Click to expand...
Click to collapse
OK thanks. Do I not require s-off then?
Also, i just tried to install the ROM with twrp (slide right to flash) and it said zip file is corrupt.
ChiefMustardo said:
OK thanks. Do I not require s-off then?
Click to expand...
Click to collapse
For the huge majority of mods (flashing custom ROMs, root, and much more) s-off is not needed. S-off is only needed for a few very specific things, such as manually flashing hboot, radio, changing CID or MID, and a few others.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
ChiefMustardo said:
Also, i just tried to install the ROM with twrp (slide right to flash) and it said zip file is corrupt.
Click to expand...
Click to collapse
What ROM specifically? Did you deselect the MD5 check in TWRP, as previously advised?
redpoint73 said:
For the huge majority of mods (flashing custom ROMs, root, and much more) s-off is not needed. S-off is only needed for a few very specific things, such as manually flashing hboot, radio, changing CID or MID, and a few others.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
What ROM specifically? Did you deselect the MD5 check in TWRP, as previously advised?
Click to expand...
Click to collapse
I am using the skydragon ROM (latest for Marshmallow) but in the zip the only file there is system. It also skips the MD5 check and has a progress bar for a bit and then comes up with the corrupt zip message.
after flashing oxygenos 4.1.1 through twrp recovery when i rebooted my phone into recovery stock recovery came i dont have pc right now can anyone help it's very urgent
after flashing new OOS update , should always boot into TWRP first than boot into OS. flash TWRP recovery again ver 3.0.4-1.
anup807 said:
after flashing new OOS update , should always boot into TWRP first than boot into OS. flash TWRP recovery again ver 3.0.4-1.
Click to expand...
Click to collapse
Actually I don't have PC is there any other way
how did you install it earlier?
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
https://www.youtube.com/watch?v=BYUycIr7xQo - try this.
If you've lost your custom recovery after flashing a ROM, I'm assuming that you didn't root immediately afterwards?
In that case, you won't be able to use Flashify and your only option is to wait until you have access to a PC.
You should flash twrp after flashing any rom. Then reboot to recovery to check if it works. Official roms flash official recovery...
Anova's Origin said:
If you've lost your custom recovery after flashing a ROM, I'm assuming that you didn't root immediately afterwards?
In that case, you won't be able to use Flashify and your only option is to wait until you have access to a PC.
Click to expand...
Click to collapse
Can i root my phone through app like kingoroot or any other app then can i flash trwp through falshify
sauravid said:
Can i root my phone through app like kingoroot or any other app then can i flash trwp through falshify
Click to expand...
Click to collapse
If kingoroot works, then yes, you can probably flash TWRP that way.
Anova's Origin said:
If kingoroot works, then yes, you can probably flash TWRP that way.
Click to expand...
Click to collapse
No rooting app is working did you know any app which can work
anup807 said:
how did you install it earlier?
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
- try this.
Click to expand...
Click to collapse
Actually it requre root access. Do you know how to get root access without pc
You could give Kingroot (not Kingoroot) a try. I used to use it on old devices and it does work from time to time. Beware that it does contain a lot of bloat and is suspected to datamine its users. If it successfully roots your phone, I would advise you to clean flash your ROM again after flashing a custom recovery just to make sure it doesn't linger. It it fails to root, then just delete the app (it shouldn't be able to install anything malicious without root access).
Anova's Origin said:
You could give Kingroot (not Kingoroot) a try. I used to use it on old devices and it does work from time to time. Beware that it does contain a lot of bloat and is suspected to datamine its users. If it successfully roots your phone, I would advise you to clean flash your ROM again after flashing a custom recovery just to make sure it doesn't linger. It it fails to root, then just delete the app (it shouldn't be able to install anything malicious without root access).
Click to expand...
Click to collapse
Not working..bro
I would suggest not to take too much risk with rooting without the access to PC. If by chance, something goes wrong, like bootloop or something, you'll be screwed big time.
anup807 said:
I would suggest not to take too much risk with rooting without the access to PC. If by chance, something goes wrong, like bootloop or something, you'll be screwed big time.
Click to expand...
Click to collapse
Ohk bro