Related
Hi there everyone,
I have a huge problem. Last night i bricked my xoom. I was following a tutorial on this forum. and after unlocking the bootloader it told to flash a file called boot.img after doing so and typing fastboot reboot, the device wouldnt start behind the motorola logo. i tried allot of thing and also did flash some other stock android 4.0.4 boot.img files now with the last one mentioned i managed to get the xoom (wifi) to boot a little further. because the ripple movie with the motorola logo is shown. but it stucks at that movie.
Does anyone know if i can flash an image on the xoom that will atleast fix the problem of not rebooting so i can try another tutorial.
I have searched the internet for solutions, many of them linked to threads on this forum. but almost all download links in these tutorials are old and broken.
Can someone please help me unbrick my device? And maybe a link to a good working unroot tutorial for my xoom wifi with android 4.0.4.
Try get back to Stock.
Download from HERE
and do some OTA updates afterwards so everything will be up to date.
Then wipe and try again from scratch..
Worked for me perfectly just a few days ago.
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Cubanluke88 said:
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Click to expand...
Click to collapse
Indeed it worked. i downloaded the official images and flashed them im on android 3.0.1 again and all seems to work just fine now.
Next problem is i cant find a descent tutorial on this forum how to root the xoom. all download links are either removed due to copyright issues or the links are just broken.
How does it work actually?
1. I unlocked the boot loader wich is very easy.
but then? Do i need to flash a rooted image over the existing? i dont really understand how this works. I rooted my Desire HD with a good tutorial in minutes. Not many people seems to really know how to root the Xoom.
Also i would like to know if the different tutorials are for different android versions or can i aply all tutorials of rooting when i stay on android 3.0.1?
I also tried to flash a recovery.img to the recovery partition and press volume down 3 seconds after the moto logo apears but when i do i get an android robot with a big " ! " on his belly and it takes 5 minutes to load the menu. when im in it tells me there is no sdcard present when i try to flash a rooted rom (zip file).
Is there someone reading this thats willin to explain to me how to do a root the easiest way? Please if links are posted be sure everything on that thread is working. Im pretty sure i will pull it off with some push in the right direction.
Thank you!
(edit) omg im stupid, offcourse the sdcard wont work... it never worked at 3.0.1. on the xoom. can i follow this tutorial:
http://rootzwiki.com/topic/451-how-to-root-the-wifi-only-xoom-301/
Could someone read over it and see if this is a good tutorial? last time i flashed a boot.img the whole xoom got stuck... is that because i had the wrong boot.img on the wrong android version? or should boot.img always work?
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Cubanluke88 said:
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Click to expand...
Click to collapse
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
eos 4.1.1 is simply awesome and its also pre rooted' so your bootloader is unlocked, all you gotta do now is install twrp recovery via fastboot ( my preffered recovery) then flash eos via recovery
Sent from my Xoom using XDA Premium App
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
EOS is a pretty AOSP rom. No theme, though you can apply one if you like and change a few colors. There are various toggle additions you can add that make the user experience much better. It also comes with an overclockable kernel and is very very stable (despite being a nightly) The team has been supporting the Xoom for over a year and is very committed to the Xoom.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
As for flashing, just gotta make sure your text is good before hitting the enter key. Recovery flash should look something like this:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Some instructions for flashing can be found here
While that page is specifically for locking and flashing to return to stock, the commands are universal for fastboot. Hell, if you wanted to, you could manually restore a nandroid backup via fastboot and flashing images.
Hello all,
I know everyone hates people who post without searching the forums first, but I did and I am still very lost on what all I need to do to root my device and get going flashing ROMs with the new 2.20 Root Method.
I have used this thread to get me started (http://forum.xda-developers.com/showthread.php?t=1684382&highlight=root+guide) and I have already downloaded Android SDK from google + Platform-tools + Google USB Driver but I don't want to get going on root because in the instructions from 2.20 Root it states:
10. After unlocking the bootloader, you can flash a custom recovery partition via fastboot, boot into recovery mode, and use a recovery ADB shell or install from an update.zip to install Superuser and su (I do not provide support for custom recoveries, but this is a straightforward process that other people can help with).
I have searched the above linked thread and cannot determine how to generate a custom recovery partition (unless I did when I used the command "adb -backup all" in the platform-tools folder of the Android SDK..Furthermore, I do not know what "Superuser and su" is referencing.
If anyone could point me in the right direction, I dont mind doing the reading myself but I have gotten bogged down in the details. Basically, I want to save all of you the trouble of another noob who has bricked their phone because they didn't do their homework. Thanks all for your help!
TheEmpyre said:
Hello all,
I know everyone hates people who post without searching the forums first, but I did and I am still very lost on what all I need to do to root my device and get going flashing ROMs with the new 2.20 Root Method.
I have used this thread to get me started (http://forum.xda-developers.com/showthread.php?t=1684382&highlight=root+guide) and I have already downloaded Android SDK from google + Platform-tools + Google USB Driver but I don't want to get going on root because in the instructions from 2.20 Root it states:
10. After unlocking the bootloader, you can flash a custom recovery partition via fastboot, boot into recovery mode, and use a recovery ADB shell or install from an update.zip to install Superuser and su (I do not provide support for custom recoveries, but this is a straightforward process that other people can help with).
I have searched the above linked thread and cannot determine how to generate a custom recovery partition (unless I did when I used the command "adb -backup all" in the platform-tools folder of the Android SDK..Furthermore, I do not know what "Superuser and su" is referencing.
If anyone could point me in the right direction, I dont mind doing the reading myself but I have gotten bogged down in the details. Basically, I want to save all of you the trouble of another noob who has bricked their phone because they didn't do their homework. Thanks all for your help!
Click to expand...
Click to collapse
I second this request. I feel like there are loads of helpful threads but after searching for a long time I don't see anything that leads someone new to Android rooting from stock 2.2 to having something like CM10 on their device. All of the write-ups I've found assume more experience than I have. Is there a general guide somewhere that I'm missing? Maybe something that explains rooting, backing up, flashing, etc. from start to finish where we can replace "this is where you root your device" with the new rooting method? I'm assuming it's out there but I can't seem to find it anywhere.
TheEmpyre said:
I have searched the above linked thread and cannot determine how to generate a custom recovery partition
Click to expand...
Click to collapse
You don't need to "generate" anything, not sure where you got that terminology from. Just install Goomanager from the Play Store and use that to install TWRP recovery.
---------- Post added at 09:20 AM ---------- Previous post was at 09:12 AM ----------
TheEmpyre said:
Furthermore, I do not know what "Superuser and su" is referencing.
Click to expand...
Click to collapse
In plain terms a superuser = a root user. But when discussed here, it usually references the app that manages what other apps have root access.
Superuser is required to perform root functions.
You can obtain the app various ways, all discussed here: http://forum.xda-developers.com/showthread.php?t=1954361
TheEmpyre said:
Hello all,
I know everyone hates people who post without searching the forums first, but I did and I am still very lost on what all I need to do to root my device and get going flashing ROMs with the new 2.20 Root Method.
I have used this thread to get me started (http://forum.xda-developers.com/showthread.php?t=1684382&highlight=root+guide) and I have already downloaded Android SDK from google + Platform-tools + Google USB Driver but I don't want to get going on root because in the instructions from 2.20 Root it states:
10. After unlocking the bootloader, you can flash a custom recovery partition via fastboot, boot into recovery mode, and use a recovery ADB shell or install from an update.zip to install Superuser and su (I do not provide support for custom recoveries, but this is a straightforward process that other people can help with).
I have searched the above linked thread and cannot determine how to generate a custom recovery partition (unless I did when I used the command "adb -backup all" in the platform-tools folder of the Android SDK..Furthermore, I do not know what "Superuser and su" is referencing.
If anyone could point me in the right direction, I dont mind doing the reading myself but I have gotten bogged down in the details. Basically, I want to save all of you the trouble of another noob who has bricked their phone because they didn't do their homework. Thanks all for your help!
Click to expand...
Click to collapse
ctennenh said:
I second this request. I feel like there are loads of helpful threads but after searching for a long time I don't see anything that leads someone new to Android rooting from stock 2.2 to having something like CM10 on their device. All of the write-ups I've found assume more experience than I have. Is there a general guide somewhere that I'm missing? Maybe something that explains rooting, backing up, flashing, etc. from start to finish where we can replace "this is where you root your device" with the new rooting method? I'm assuming it's out there but I can't seem to find it anywhere.
Click to expand...
Click to collapse
They are many simple tutorials for rooting but do not know why you guys having hard time. Ok here is
1) You got Android SDK from google + Platform-tools + Google USB Driver -
2) Only for windows - Download htc sync ( It will install necessary htc drivers) - Link
3) Just to check if htc drivers installed properly , open "C:\android-sdk\platform-tools" ( Or folder where adb and fastboot exists) then "Press shift + right click and select "Open command window here" ( open command prompt and cd "folder where adb and fastboot exists).
4) In command window type " adb devices" and see output - If you get output then htc drivers installed properly.
You can skip step 3 and step 4 - These steps are only for verification
5) Goto [ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit and follow the instructions there.
6) Once you successfully root your device using above exploit then goto - [How To] Flash Custom recovery and ROMS after 2.20 root complete the steps to flash custom recovery and if you want to flash ROMS
7) To unlock BOOT LOADER use this link - [INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up , follow the instructions under " BOOTLOADER UNLOCK, SUPER CID, AND S-OFF"
You can also goto this link - [ROOT][2.20] One XL Bootloader unlock & Root guide By XsMagical - Very nice tutorial, if you find above links difficult to follow
Note* : During exploit or flashing recovery they talk about using fastboot commands, In order to execute them you need goto C:\android-sdk\platform-tools" ( Or folder where adb and fastboot exists) then "Press shift + right click and select "Open command window here" ( open command prompt and cd "folder where adb and fastboot exists) and then execute the commands ..
Advice - Do not flash any roms apart from xda
Thank you, abhipati. I haven't seen any simple tutorials that are complete. Everything seems to assume the user knows how to do something mentioned in another thread, which in turn seems to assume something else. Your post seems like a very clear start-to-finish explanation. Maybe it should be made into a stickie in Q&A. I can surely handle step 1 but maybe that could be explained (or at least a link added to an appropriate thread).
If all this is out there somewhere already then I certainly didn't know where to find it. I appreciate your help.
ctennenh said:
Thank you, abhipati. I haven't seen any simple tutorials that are complete. Everything seems to assume the user knows how to do something mentioned in another thread, which in turn seems to assume something else. Your post seems like a very clear start-to-finish explanation. Maybe it should be made into a stickie in Q&A. I can surely handle step 1 but maybe that could be explained (or at least a link added to an appropriate thread).
If all this is out there somewhere already then I certainly didn't know where to find it. I appreciate your help.
Click to expand...
Click to collapse
No problem.
Regarding step 1)
1) Download Android SDK from here {For Windows}
2) Download java you need it - here
Thank you all for helping gather some resources for me that I know are up to date etc. - Thankfully I do know a few unix commands so that I can navigate the command prompt aspects...I'm sure these threads get annoying so thank you very much for getting a new-to-root user up and running. I'll try this all later this evening and throw an update to let you all know how it goes -- hopefully no "bricked my phone" thread in the future
Excellent I have successfully unlocked my bootloader and achieved perm-root! Now on to flashing roms and I have some questions:
1) I have read GuyIncognito's instructions here (http://forum.xda-developers.com/showthread.php?t=1952076) on Flashing ROMs and how to go about doing that and i fully understand the process but I want to confirm (Yes I Have TWRP recovery installed and running) I only need to extract the boot.img out of the winRAR file of the ROM that I downloaded? (CM10 seems to be popular so I'm starting with that as my first ROM) There are so many other files in the package and I'm wondering why do you only need the boot.img file to be present with your adb and fastboot files from the google dev SDK -- the boot.img is only 5 MB and I can hardly believe that it constitutes the whole OS?
2) How do I go about installing gapps after I have flashed my ROM? I have downloaded Gapps so I have the file...do I place it in my SD Card and then enter recovery to install it? or Do have to use adb to flash it
Edit: I also have Superuser app on my stock ROM right now
Any further help is much appreciated, thank you very much.
Boot.img is technically just the kernel, it's the heart of the OS you are installing. Once extracted, rezip rom. Flash boot.img first using fastboot command prompt. Then flash the Rom itself that you rezipped through twrp
You can easily just flash gapps through twrp.
Sent from my HTC One XL using xda premium
InflatedTitan said:
Boot.img is technically just the kernel, it's the heart of the OS you are installing. Once extracted, rezip rom. Flash boot.img first using fastboot command prompt. Then flash the Rom itself that you rezipped through twrp
You can easily just flash gapps through twrp.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks for the reply, the community on XDA kicks a$$, doing some additional reading just plz tell me if I understand this correctly...
1) Copy CM10 zip and Gapps zip into phone storage
2) Follow GuyIncognito's instructions on flashing boot.img
3) Boot into recovery AFTER Flashing boot.img
4) Select "Install" in TWRP
5) Install CM10 zip First
6) Install Gapps zip next
7) Reboot
8) profit?
TheEmpyre said:
Excellent I have successfully unlocked my bootloader and achieved perm-root! Now on to flashing roms and I have some questions:
1) I have read GuyIncognito's instructions here (http://forum.xda-developers.com/showthread.php?t=1952076) on Flashing ROMs and how to go about doing that and i fully understand the process but I want to confirm (Yes I Have TWRP recovery installed and running) I only need to extract the boot.img out of the winRAR file of the ROM that I downloaded? (CM10 seems to be popular so I'm starting with that as my first ROM) There are so many other files in the package and I'm wondering why do you only need the boot.img file to be present with your adb and fastboot files from the google dev SDK -- the boot.img is only 5 MB and I can hardly believe that it constitutes the whole OS?
2) How do I go about installing gapps after I have flashed my ROM? I have downloaded Gapps so I have the file...do I place it in my SD Card and then enter recovery to install it? or Do have to use adb to flash it
Edit: I also have Superuser app on my stock ROM right now
Any further help is much appreciated, thank you very much.
Click to expand...
Click to collapse
follow his instructions and you'll be fine
flash the boot.img in flashboot, reboot in recovery, flash your nameofrom.zip, flash your gapps pkg just like the rom (on your sd card), enjoy...
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
TheEmpyre said:
Thanks for the reply, the community on XDA kicks a$$, doing some additional reading just plz tell me if I understand this correctly...
1) Copy CM10 zip and Gapps zip into phone storage
2) Follow GuyIncognito's instructions on flashing boot.img
3) Boot into recovery AFTER Flashing boot.img
4) Select "Install" in TWRP
5) Install CM10 zip First
6) Install Gapps zip next
7) Reboot
8) profit?
Click to expand...
Click to collapse
yes that;s correct you may wanna backup your sd card 1st as well and do a full wipe before flashing the rom.
Just in case your not familiar with fastboot, the command is fastboot flash boot boot.img
Sent from my HTC One XL using xda premium
Crappyvate said:
follow his instructions and you'll be fine
flash the boot.img in flashboot, reboot in recovery, flash your nameofrom.zip, flash your gapps pkg just like the rom (on your sd card), enjoy...
Click to expand...
Click to collapse
By Flash do you mean using TWRP recovery "install" feature and selecting the CM10.zip I have in my SD Card, and gapps? Just making sure I dont have to do it via command prompt cuz then I may have to do some additional reading
Edit: Just saw you all beat me to it, thanks all, will get back to you after I am running a ROM *crossfingers*
TheEmpyre said:
By Flash do you mean using TWRP recovery "install" feature and selecting the CM10.zip I have in my SD Card, and gapps? Just making sure I dont have to do it via command prompt cuz then I may have to do some additional reading
Click to expand...
Click to collapse
yes install. you dont need to do it from command prompt, additional reading is always good
even though it was put together a while back this http://forum.xda-developers.com/showthread.php?t=1678308 is a very good guide and covers a lot of things of course you should absolutely start here in redpoint indispensable guide to all the resources available to one xl http://forum.xda-developers.com/showthread.php?t=1671237
happy flashing
Alright Looks like I successfully flashed CM10! I flashed gapps with it at the same time but I have run into a problem -- It keeps telling me that all these gapps processes have failed and I have no access to a keyboard! Do I have to reflash gapps?
Hmm ok I think I messed up here....
My phone was essentially non-functional with CM10 -- Nothing worked and it took me a while to navigate to enable USB Debugging on the given mod. One I enabled USB Debugging in CM10 I ran the following:
adb reboot recovery
Once I was in recovery, I Restored a backup of my device that I made BEFORE I obtained permanent root via the toolkit as it was recommended during this time to make a recovery.
Recovery worked successfully, now after reboot it hangs on the HTC screen and then goes black, then reboots again, and again, and again...
I haven't been able to use the volume down + power button to even get back into the bootloader.....hopefully I am not screwed here...Any suggestions?
TheEmpyre said:
Hmm ok I think I messed up here....
My phone was essentially non-functional with CM10 -- Nothing worked and it took me a while to navigate to enable USB Debugging on the given mod. One I enabled USB Debugging in CM10 I ran the following:
adb reboot recovery
Once I was in recovery, I Restored a backup of my device that I made BEFORE I obtained permanent root via the toolkit as it was recommended during this time to make a recovery.
Recovery worked successfully, now after reboot it hangs on the HTC screen and then goes black, then reboots again, and again, and again...
I haven't been able to use the volume down + power button to even get back into the bootloader.....hopefully I am not screwed here...Any suggestions?
Click to expand...
Click to collapse
I think u need to flash that backups boot IMG
omario8484 said:
I think u need to flash that backups boot IMG
Click to expand...
Click to collapse
Yes that would make sense, but the problem is A) How do I access that backup's .img file? B) How can I enter bootloader again? It won't let me using Power+Vol Down, no matter how long I hold it for --- unless I need to hold it longer?
You have to hold it till the buttons flash and goes black... Hold for about 2-3 more seconds and release the power button, but keep the volume down held until you get to a white hboot screen. (it'll have three skating droids)
Sent from my HTC One XL using xda premium
InflatedTitan said:
You have to hold it till the buttons flash and goes black... Hold for about 2-3 more seconds and release the power button, but keep the volume down held until you get to a white hboot screen. (it'll have three skating droids)
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok got it, did a factory reset then re-flashed CM10 boot.img...Flashed CM10 BY ITSELF this time, without doing gapps at the same time, rebooted into recovery after CM10 rolled up, then flashed gapps alone, everything is working smoothly! Now, time to restore my apps
Panicked momentarily, but now I'm back at it.
THANK YOU EVERYONE! Huge ups to all of you for helping a noob find his way
Hello folks,
just wanted to share with you the subject. I'm not a developer, so I cannot go too deeply in the procedure below. what I can ensure is that is working on my personal device, Padfone 2 model A68, bought in Italy with stock firmware IMM76I.WWE_9.8.8.55-0.
DISCLAIMER
should you decide to go for it, remember, I'm just a simple user willing to share a procedure that worked for him, I'm not a smartphone OEM... Accordingly:
I'll not be held responsible if you brick, melt, destroy your device, by following the below procedure... you are the solely and ultimate responsible of your actions and your property.
if after you unlock or root your phone you need to lock it back, or put it in a Virgin "out-of-the-box" state.... cannot help. consider this procedure irreversible.
If you understand the above and concur, well, you can go for the below procedure. otherwise you're kindly requested to stop reading here and NOT continue. tks a lot.
Backgroung
the rooting method is quite straight-forward, getting a stock boot.img and manipulate its ramdisk so that the device can then boot insecure.
Credits
A HUGE thanks to Schriss for his strong support in letting me understand what I was doin on my device:good:
And also a thanks to ChainFire and his insecure adbd (here)
WHAT YOU NEED
1. a padfone 2 with more than 70% battery available, and the above firmware installed (you might wanna try also if your device has different firmware, but I cannot garantee on the results you'll get.
2. this INSECURE ICS boot.img
OR
2a this insecure JB boot.img
OR
2b. you might wanna try this TW JB boot.img from TW JB
3. a valid ADB and FASTBOOT package (lots available within XDA, or already available if you have andorid SDK installed from http://developer.android.com/sdk/index.html)
4. a valid "su" binary, again you can find it in XDA or attached to this post.
5. Valid usb drivers (see mama ASUS website)
6. the infamous "UnLock.apk" (again kindly provided by ASUS)
ONE CLICK procedure (script based) kindly provided by Padfone.cl
here
OR
STEP BY STEP PROCEDURE (MS WINDOWS OS Only)
0. place all of the files (boot.img, adb and fastboot exe's, SU binary) in one folder of your pc and open a cmd session in it.
1. install drivers at point 5 above
2. Unlock your bootloader: install the apk at point 6. above follows all the instructions to get a bootloader unlocked
3. once done the phone can be put in FASTBOOT mode (black screen with "Fastboot MODE !!!" and ASUS LOGO) , with one of the two methods below.
3a. power off device. then push and hold power on + vol up.
3b. if your device is connected to your pc, verify it is in debug mode (under setup/development) and run "adb reboot-bootloader"
4. if not already done connect the device to your pc and wait the drivers selfconfiguring
5. check if fastboot.exe see your device, type in cmd "fastboot devices", if nothing is shown means you're missing drivers, or using a bad fastboot exe.
6. check if your device boots with the insecure img at point 2. of what-you-need list. type in cmd "fastboot boot boot.img"
6a. if it reboots normally... CONGRATS your device is ok with my boot.img and you can root your phone
6b. if it goes into bootloop or bootlock or in QHUSB_DLOAD state, well sorry you cannot go ahead. just push and hold power on your device. it will reboot using its boot.img Sorry no root for you
7. if you're lucky and you get 6a response, you can now ROOT your device
7a. in cmd session type the below
adb remount (system answer "remount succeded" that's a confirmation you can act as superuser)
adb push su /system/bin/
adb shell
chmod 06755 /system/bin/su
type exit, to get off the adb shell.
7b. Collect superuser.apk at the end of this post and place it in same folders of adb.
In cmd session type
"adb push Superuser.apk /system/app
adb shell chmod 06755 /system/app/Superuser.apk"
IF YOU JUST WANT YOUR DEVICE ROOTED PROCEDURE STOPS HERE FOLLOWING IS JUST an ADDED-ON
8. OPTIONAL just in case you want to keep the insecure adbd onboard, not necessary to mantain root condition.
8a. put the device in FASTBOOT mode as above and type in cmd "fastboot flash boot boot.img", this just overwrite your stock boot.img and inoculate the insecure boot.img in your device on a stable basis.
guess it's all.
let me know if it's working for you gentlemen, and remember the disclaimer above and in general just make sure you always know what you're doin... I'll post the boot.img file shortly during today.
reserved
reserved
Hi,
Thanks for a guide, that should make it very easy for Padfone 2 users to get root
Disclaimer mentions going back to Stock and relocking - this would need a separate Guide with disclaimers because it's a little dangerous IF you have flashed anything non-stock into Boot partition and then re-locked. But if rooting was done by fastboot boot, then I believe the device could be re-locked and you would still have your root. Until you flash some Asus official Update which would overwrite /System/bin, making SU disappear.
as for points 8 and 8a, it is possible, that you don't need to permanently flash insecure boot.img. After SU has been pushed to /System/bin, you can try simply rebooting as normal and the file should remain on System partition, which is separate from boot.img. It's quite likely, that root will remain and so no flashing would be needed at all if you want to stay on Stock ROM and just need root
Root is really all about putting SU in /System/bin folder, the rest are tricks to make it happen.
schriss said:
Hi,
Thanks for a guide, that should make it very easy for Padfone 2 users to get root
Disclaimer mentions going back to Stock and relocking - this would need a separate Guide with disclaimers because it's a little dangerous IF you have flashed anything non-stock into Boot partition and then re-locked. But if rooting was done by fastboot boot, then I believe the device could be re-locked and you would still have your root. Until you flash some Asus official Update which would overwrite /System/bin, making SU disappear.
as for points 8 and 8a, it is possible, that you don't need to permanently flash insecure boot.img. After SU has been pushed to /System/bin, you can try simply rebooting as normal and the file should remain on System partition, which is separate from boot.img. It's quite likely, that root will remain and so no flashing would be needed at all if you want to stay on Stock ROM and just need root
Root is really all about putting SU in /System/bin folder, the rest are tricks to make it happen.
Click to expand...
Click to collapse
yes, I got your points I'm amending the first post. tks
Thumbs up guys. U all did it!
Padfone 2 just got epic! I have been following your thread every single day schriss and ivalex. Well done and heaps of gratitude.
After rooting,do you think its possible to flash jellybean using clockworkmod in the near future?Thanks!
Sent from my PadFone 2 using xda app-developers app
Scarletdeath said:
After rooting,do you think its possible to flash jellybean using clockworkmod in the near future?Thanks!
Sent from my PadFone 2 using xda app-developers app
Click to expand...
Click to collapse
this kind of stuff require time and testing. and as you said first we need a good CWM porting, than someone to port CM10 or a stock-modified JB when it will be available.
we'll see
Ivalex said:
this kind of stuff require time and testing. and as you said first we need a good CWM porting, than someone to port CM10 or a stock-modified JB when it will be available.
we'll see
Click to expand...
Click to collapse
I think getting CWM should be very straightfoward as soon as someone dumps Recovery partition with the commands posted earlier or in the other thread. Testing it should also be simple because it can be booted like insecure boot :victory:
A very good step for our padfone2!
4.1 is coming very soon (within Dec if Asus didn't lie on us) and unlocking at this stage may void the OTA.. (Given CWM is not avail ATM and it is uncertain how soon can the new rom.zip can be made)
even OTA can be performed, boot img is updated and need to be exploited again (with your experience I think it will be much more straight forward later on tho )
These makes me struggling whether I should unlock my padfone2 now or not..
Anyway, as said this is really a good step to our padfone2 at this stage, keep it up and I am looking forward to some point that I have no more struggle and unleash my beast at once!
Greatly appreciated! :good::good:
Hmmm I keep failing at the last step 7b. Keep getting err msg that installation failed when SuperSU tried to update the binary. On WWE stock now and have tried various SU binaries all with same results....
Any suggestions?
kahei036 said:
A very good step for our padfone2!
4.1 is coming very soon (within Dec if Asus didn't lie on us) and unlocking at this stage may void the OTA.. (Given CWM is not avail ATM and it is uncertain how soon can the new rom.zip can be made)
even OTA can be performed, boot img is updated and need to be exploited again (with your experience I think it will be much more straight forward later on tho )
These makes me struggling whether I should unlock my padfone2 now or not..
Anyway, as said this is really a good step to our padfone2 at this stage, keep it up and I am looking forward to some point that I have no more struggle and unleash my beast at once!
Greatly appreciated! :good::good:
Click to expand...
Click to collapse
I'm pretty sure that unlocked Padfone 2 can be relocked with fastboot command just like for example HTC One X. Then it would be possible to use Asus OTA updates.
But I also think Asus OTA could be flashed with CWM. Then, same insecure rooting story starts over.
---------- Post added at 05:20 PM ---------- Previous post was at 05:17 PM ----------
turtle76 said:
Hmmm I keep failing at the last step 7b. Keep getting err msg that installation failed when SuperSU tried to update the binary. On WWE stock now and have tried various SU binaries all with same results....
Any suggestions?
Click to expand...
Click to collapse
So you installed SuperSU, then rebooted just to be sure and then tried updating?
Anyway, in case of such problems, I think we could push latest SuperSU.apk and other files same way as SU, we just push them to /System/app folder where all apk belong, then reboot.
schriss said:
I'm pretty sure that unlocked Padfone 2 can be relocked with fastboot command just like for example HTC One X. Then it would be possible to use Asus OTA updates.
But I also think Asus OTA could be flashed with CWM. Then, same insecure rooting story starts over.
---------- Post added at 05:20 PM ---------- Previous post was at 05:17 PM ----------
So you installed SuperSU, then rebooted just to be sure and then tried updating?
Anyway, in case of such problems, I think we could push latest SuperSU.apk and other files same way as SU, we just push them to /System/app folder where all apk belong, then reboot.
Click to expand...
Click to collapse
Worked finally Thks for the advice pal
turtle76 said:
Worked finally Thks for the advice pal
Click to expand...
Click to collapse
Thanks for the advice. I'll add also push and chmod commands for supersu as add-on In case of problem as the one You had.
Inviato dal mio PadFone 2 con Tapatalk 2
Great news
The only thing I was waiting for before deciding on buying this device was to see how well its supported by this community. Thanks guys, may be finally time to let my good ol HTC HD2 rest now
Great work Padfone 2 community!
Would like to know if anyone has tried this on the IMM761.TW_9.8.8.55-0 firmware?
Did it work?
RagnarokRO said:
Great work Padfone 2 community!
Would like to know if anyone has tried this on the IMM761.TW_9.8.8.55-0 firmware?
Did it work?
Click to expand...
Click to collapse
It shld work. I was trying on tw firmware and didn't encountered issues till step 7b which was due to other issue.
getting mine friday did see on asus site there is a tool for unlock of boot loader.
Is this phone and pad any good? Can not wait for mine
I guess I am stupid because I can't get anything to work.
downloaded everything
but I can't make any commands work
I open the cmd and don't know if the " are suppose to be there or not and nothing works
Burley1 said:
I guess I am stupid because I can't get anything to work.
downloaded everything
but I can't make any commands work
I open the cmd and don't know if the " are suppose to be there or not and nothing works
Click to expand...
Click to collapse
Have you switched to the folder that contains fastboot and those stuffs in command prompt?
Hi there,
A while ago I got a OnePlus One which came with ColorOS loaded. I of course googled my way to get the Cyanogenmod and followed these instructions.
http://www.youtube.com/watch?v=QDKOEtN9pbo
I'm currently on the 25R firmware and I know there are some updates after that but the phone doesnt detect any update release. I would like to know why the OTA updates are not being picked up from the phone. Was it simply the easy method mentioned above?
I also thought of reflashing it properly and found some instructions on the web.
Code:
Install Android tools (and drivers if you use Windows-crap). You need the fastboot and adb tools
Get http://dist01.slc.cy...ed-fastboot.zip and unpack it
Enable USB debugging on the phone
Run adb reboot-bootloader
Once bootloader started run: fastboot oem unlock
After automatic reboot, do steps 3 & 4 again
In the directory where you unpacked it, run in a console
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img (or userdata.img for 16G version)
fastboot oem lock
fastboot reboot
These instructions will somehow get the OTA updates working, am I right to assume that this method would rewrite everything and I would lose the recovery software of the ColorOS? Also are the Android tools these?
http://developer.android.com/sdk/index.html
Fastboot and ADB, I can use this one right?
http://forum.xda-developers.com/showthread.php?t=2588979
I appreciate the help and a few explanations.
Cheers.
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
dude777 said:
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
Click to expand...
Click to collapse
If you're looking for a completely fresh install, just go to my guide thread (link in signature) and follow section 8.
Transmitted via Bacon
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood.
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Look on YouTube on how to use this toolbox and it will completely wipe your phone then flash clean.
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
A toolbox is completely unnecessary, and they're more trouble than they're worth. Plus, nobody learns anything even using a toolbox, and that knowledge is crucial for when things go wrong.
Transmitted via Bacon
DON'T use a toolbox please
Learn as you go by doing things properly, I speak from my own experience. These skills and knowledge that you gain will help if you ever run into any issues
Go here to install the adb drivers computer wide so you can flash from any folder on your computer, it makes your life so much easier
http://forum.xda-developers.com/showthread.php?t=2588979
Then follow timmaaa guide on how to start fresh with a complete 44s ROM
Sent from my A0001 using XDA Free mobile app
Thanks guys for the effort here, really like your guides timmaaa very clear and non confusing. Yes I would like to avoid shortcuts as I took the easy route and now the phone goes in hiatus moment when calling. I'll get around this in the weekend and see how that goes.
Cheers.
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
dude777 said:
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
Click to expand...
Click to collapse
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
timmaaa said:
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
Click to expand...
Click to collapse
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
dude777 said:
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
Click to expand...
Click to collapse
You do indeed restore a nandroid backup with the recovery that you made the backup with. And yes it is saved on the phone so you will need to transfer it to your PC. You're not being a pain in the butt, you're doing the right thing and researching before attempting something.
Transmitted via Bacon
Yeah I agree users like you that research crap before attempting something are much preferred over users that blindly use a toolbox then come complaining cuz they messed something up but dunno how to fix it. I always do my research before flashing just like you are doing. Just make sure you install the drivers I linked to computer wide on your windows computer and you should have no problems, no need to install separate SDK for android and copy the files you're flashing into a special folder, etc
info update
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
If you follow timmaaa's guide you should be good to go. I'm a noob myself and just did it over the weekend and its a blast. Good luck
Cheers
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
Lol really? Did u completely ignore reading the thread that you just posted in??
[emoji15] [emoji58]
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom .
Downloads
S5_Root_Tools_2023.7z
EMMC_15_Rom.zip -- Stock QL1 6.0
Directions For Unlocking Stock Phone
I would recommend Windows defender is turned of before starting
1. Download S5_Root_Tools_2023.7z and unzip
2. Make sure Usb debugging is enabled on your phone
3. Plug in phone and run Safestrap.exe and follow directions on command window
4. This process is pretty much 1 click all automatic except following command window prompts
5. This will detect if your phone is EMMC 11 or 15
6. If it detects EMMC 15 it will automatically unlock your bootloaders.
7. Once process is done reboot too twrp and flash rom of choice or use provide one and flash root zip of choice
Regular Magisk
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Magisk Delta
Releases · HuskyDG/magisk-files
Contribute to HuskyDG/magisk-files development by creating an account on GitHub.
github.com
ETFSU
EFTSU Root Solutions
The Largest Database for the Root Solutions on the Internet
eftsu.com
Safteynet Fix Module
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Old Method And Old Downloads
EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip -- Rom Zip
EMMC_11_S5_Root_Tools_2022_V7.7z
-- Files Needed To Root Phone
Instructions To Root And Install Safestrap
**If you already have safestrap installed you can skip to Instructions To Unlock Bootloader
**If you are already rooted but do not have safestrap installed download View attachment S5_Safestrap.apk install then skip to Instructions To Unlock Bootloader**
Directions
1. Download both files and unzip EMMC_15_And_11_S5_Root_Tools_2022_V7.7z
2. Reboot phone too Download Mode by holding Power+VolDwn+HomeButton as phone starts up
3. Plug phone into computer and open the Odin provided in the above file in the Odin_Folder
4. In Odin Choose BL slot and choose the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 Located in the Odin_Folder
5. Flash the file using provided Odin let phone reboot. This will wipe your phone
6. Once phone is rebooted make sure its plugged into computer and phone use recognized by computer
7. Run the Install_One_Click.cmd this should install safestrap. If this method fails countinue with below methods.
8. If above method fails you can reboot and try again or run the Manual_Install_Root_Apps.cmd and try below methods to root
Towel Root Method
These steps are only needed if above root method failed
1. You need too be connected to a network. Try one of towel root apps and if not successful then try the other one. If it doesn't work go to King root section
2. If towel root succeeds then run the click on the super su app and choose to update su binary and choose normal once successfully updated reboot phone
King Root Method
These steps are only needed if towel root failed
1. You will need to be connected to a network. Click on King root app then click try root
2. Once root is successful don't click on the optimize and close the king root app.
3, Run the Manual_Install_SuperSu.cmd
Installing Safestrap
9. This only needs to be done if 1Click bat method failed. Now click on safestrap app and clisk install safestrap click allow in root dialog app once installed click reboot to safestrap
10. Busybox must be installed ifirst if you used towelroot method too root
Instructions To Unlock Bootloader
11. Enter safestrap now in safetrap it will ask you to swipe to allow modding system make sure to do this now . If you have not copied the EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip from the EMMC_15_Bootloader_Unlock_Zip folder do so now Click install tab and choose EMMC_15_SS_Install_QL1_6_0_1_MM_Bootloader_Unlock_AIO_Rom.zip and install.
12. When done phone will power off.
13. Reboot phone to recovery you should now have TWRP recovery installed and the choose wipe the advanced wipe and wipe data only then reboot
14. Phone will reboot and stick on red Verizon screen for probably 15 to 20 min be patient. When finally booted you will have an unlocked bootloader with TWRP recovery running a Deodexed Rooted QL1 stock MM 6.0 Rom Rooted with EFTSU with root hide and safetynet pass module
Disabling Reactivation Lock
Thanks bbsc
1. Follow above directions too obtain safestrap and root
2. Download and flash EMMC_11_NCG_KK_Safestrap_Full.zip in safestrap then wipe data
This has Samsung Setup Wizard removed so you can get through setup
3. Set up a wireless connection or use your SIM-card and internet connection from your provider.
4. Navigate to Settings - Security, find Reactivation Lock and untick it. The phone will ask you for your existing credentials or to register a new Samsung account. Accept too update app then allow google check when it ask
5. Login to your new account and you will be able to untick Reactivation Lock.
6. When it unticked, Navigate to Settings - Backup Reset - Factory data Reset.
7. Phone will reboot too stock recovery and wipe data and remove current samsung account and you are good too go.
8. Now proceed with unlocking bootloader step 11 you have to enter safestrap from the safestrap splash screen on bootup its not installed as a recovery image because stock recovery is needed
Credits
beaups Sourcecode and tool
ryanbg
haggertk For his CID
autonomousperson For compiling the source to a app
magic_man185 For compiling the source
GeTex
klabit87 - Basically Everything
@GSMCHEN Lots of stuff
elliwigy Lots of stuff
afaneh92 -Safestrap and too much too mention
Sourcecode
https://github.com/beaups/SamsungCID
Instructions for downgrading or updating bootloaders can be found here
2022_VZW_EMMC_15_Chipset For Unlocked Dev BL To Downgrade To LL_KK Or Upgrade To MM_And Keep Unlock Bootloader
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4 Root And Unlock Instructions Can Be Found Here EMMC 15 Rooting And Bootloader Unlocking EMMC 11...
forum.xda-developers.com
jrkruse said:
mine
Click to expand...
Click to collapse
Nice job man! [emoji106]
stang5litre Edition 5.0 Roms
stang5litre said:
Nice job man! [emoji106]
stang5litre Edition 5.0 Roms
Click to expand...
Click to collapse
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days
@jrkruse awesome job...!! :good:You definitely must be bored... Lol. May try that on an old one for craps and giggles... Lol. Again, awesome to bring a lil history back to life... :good:
jrkruse said:
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days
Click to expand...
Click to collapse
Nice job man, much appreciated.
If you ever get bored try to make a pre-rooted rom/safestrap recovery (course no bootloader unlock) for the G930U/G935U with the latest firmware UUESACSI1 (Aug 27 2019), since it looks like Samsung has stopped updating this phone, or better yet a root-patcher for a stock sytem.img like you did for the G950/N950. I have uploaded the latest eng-boot vA/10 here: https://forum.xda-developers.com/sho...postcount=1826
jrkruse said:
I was bored so I thought it would be fun to mess around with some old school stuff. Man things were alot more simple back in these days
Click to expand...
Click to collapse
How do I update the bootloader and rom to newer QL1 if I had already unlocked the bootloader and installed twrp with much older stock rom and bootloader?
I still have the stock rom from 2016 when the bootloader unlock method was discovered.
googlephoneFKLenAsh said:
How do I update the bootloader and rom to newer QL1 if I had already unlocked the bootloader and installed twrp with much older stock rom and bootloader?
I still have the stock rom from 2016 when the bootloader unlock method was discovered.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ve...ent/vzwemmc15chipset-dev-bl-unlocked-t4010757
Sent from some device I modified
the rar seems to be corrupted ... says unknown or damaged format. I tried a few of the download points.
Would you be able to re-create / upload?
bigstack said:
the rar seems to be corrupted ... says unknown or damaged format. I tried a few of the download points.
Would you be able to re-create / upload?
Click to expand...
Click to collapse
What are you extracting it with?
Sent from some device I modified
First of all, thank you so very much Jkruse! I followed all of your instructions and everything went perfectly! The reason why I wanted to get this completed on my old S5, is that we want to gift this phone to my wife's mother. The catch is, she only speaks Russian, and I was wondering if I would now be able to flash an international version of firmware on the S5, so that she can have access to Russian as a language option? Is this doable?
Remedy1230 said:
First of all, thank you so very much Jkruse! I followed all of your instructions and everything went perfectly! The reason why I wanted to get this completed on my old S5, is that we want to gift this phone to my wife's mother. The catch is, she only speaks Russian, and I was wondering if I would now be able to flash an international version of firmware on the S5, so that she can have access to Russian as a language option? Is this doable?
Click to expand...
Click to collapse
Its really no easy process to flash an international rom if you are using Verizon then data will probably not work with out some editing. You can always try it but Verizon will probably need Verizon csc stuff to work and build.prop edits.
Sent from some device I modified
Hey thanks for this post! I was worried about using some of the old guides on my phone, glad I found this.
However, I have a question due to why I want to root my phone.
My situation: My phone went through the factory reset process without giving me a warning before doing so. I plan on rooting my phone and trying a few different methods for recovering the files.
My Main Question: Will I be good to go with a fully rooted phone after completing step 12?
I don't feel a need to unlock the bootloader for what I'm doing (although I might do so anyway after I'm done attempting to recover files).
I've never rooted a phone before. Aside from verifying that I'm using the EMMC 15 chipset (I used the eMMC_CID_Checker_apk from this thread:https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529), is there anything else I should do or know about?
SaltedSand said:
Hey thanks for this post! I was worried about using some of the old guides on my phone, glad I found this.
However, I have a question due to why I want to root my phone.
My situation: My phone went through the factory reset process without giving me a warning before doing so. I plan on rooting my phone and trying a few different methods for recovering the files.
My Main Question: Will I be good to go with a fully rooted phone after completing step 12?
I don't feel a need to unlock the bootloader for what I'm doing (although I might do so anyway after I'm done attempting to recover files).
I've never rooted a phone before. Aside from verifying that I'm using the EMMC 15 chipset (I used the eMMC_CID_Checker_apk from this thread:https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529), is there anything else I should do or know about?
Click to expand...
Click to collapse
By the time you root there will be no files to recovery. There is another wipe involved to root so chances are there will not be much left to recover
Sent from some device I modified
jrkruse said:
By the time you root there will be no files to recovery. There is another wipe involved to root so chances are there will not be much left to recover
Sent from some device I modified
Click to expand...
Click to collapse
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...
al50 said:
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but needs device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...
Click to expand...
Click to collapse
Like i said though in order to root you have to wipe again before you can root. So there aren’t going to be much left to recovery after 2 wipes and a repartition
Sent from some device I modified
al50 said:
I'm wondering if he's wanting to root to use a file recovery app, like DiskDigger. It can recover but device needs to be rooted to access the complete internal system to recover files. As he mentioned a few times about recovering/restoring files. I recall using that (DD) a couple times and it actually worked after I mistakenly did a full wipe/reset when I was switching between ROM's and back to stock...
Click to expand...
Click to collapse
Yeah that's what I have in mind.
jrkruse said:
Like i said though in order to root you have to wipe again before you can root. So there aren’t going to be much left to recovery after 2 wipes and a repartition
Sent from some device I modified
Click to expand...
Click to collapse
Yeah I figured, makes sense, but I don't see a mention of wiping before step 12 though. This is why I'm asking if it would be okay for me to stop there, attempt to recover some files, and then continue with the rest of the steps?
Could this potentially screw something up if I do it this way? I'd rather play it safe than sorry, most of my important stuff on this phone is backed up anyway.
SaltedSand said:
Yeah that's what I have in mind.
Yeah I figured, makes sense, but I don't see a mention of wiping before step 12 though. This is why I'm asking if it would be okay for me to stop there, attempt to recover some files, and then continue with the rest of the steps?
Could this potentially screw something up if I do it this way? I'd rather play it safe than sorry, most of my important stuff on this phone is backed up anyway.
Click to expand...
Click to collapse
Flashing the combo firmware so you can root wipes your phone
Sent from some device I modified
jrkruse said:
Flashing the combo firmware so you can root wipes your phone
Sent from some device I modified
Click to expand...
Click to collapse
Ah, I see, but would it be safe for me to stop at step 12 anyway?
I figure I might as well give it a shot anyway, even if It's unlikely I'll recover anything, but I'd rather only wipe it a single time than twice.
SaltedSand said:
Ah, I see, but would it be safe for me to stop at step 12 anyway?
I figure I might as well give it a shot anyway, even if It's unlikely I'll recover anything, but I'd rather only wipe it a single time than twice.
Click to expand...
Click to collapse
If you stop at 12 you will just have king root and some apps work with kingroot but some do not
Sent from some device I modified