Related
Start by saying I'm very new about Android and smartphone in general.
Four days ago I got my first smartphone, a Xperia Play model R800i and some friends suggested me to install ICS. I searched on the internet and I have found the Xperia Play Development forum. There, I found a really interesting ROM called "New Express ICS".
I downloaded all the files and I started to follow the guide. I'm stuck at the second point (I believe this is ridiculous): I can't get into the Recovery Mode and I didn't get if I can flash the custom kernel (bootics.img) on flash tool.
I haven't rooted my phone, it's 100% virgin, yet.
Can someone explain me what to do? I'm searching answer here and on google for three days and I'm getting even more confused.
Sorry if my english is not perfect, it isn't my first language.
You need to unlock bootloader before fastboot a kernel (bootics.img)
WARNING: THIS VOIDS WARRANTY. YOU HAVE BEEN WARNED.
jeff7424 said:
You need to unlock bootloader before fastboot a kernel (bootics.img)
WARNING: THIS VOIDS WARRANTY. YOU HAVE BEEN WARNED.
Click to expand...
Click to collapse
Thank you very much, I'm going to do this. Is this a good guide?
After that what I have to do? How I will flash the rom? Sorry for all these newbie questions.
You should read all his guides.
http://forum.xda-developers.com/showthread.php?t=1836530
First read root, then unlock bootloader, then install custom roms.
Sent from my R800i
eksasol said:
You should read all his guides.
http://forum.xda-developers.com/showthread.php?t=1836530
First read root, then unlock bootloader, then install custom roms.
Sent from my R800i
Click to expand...
Click to collapse
Thanks for the link, it's very useful! Just a question: what do you mean with "read the root"? I have to root the phone?
I rooted my phone and I found the superuser app on this. Then, I unlocked the bootloader and the superuser app disappered, is it normal?
One more thing, how I flash the custom kernel and the ROM, now?
EDIT: Fail, Superuser is installed, yet, I didn't notice that
EDIT2: Why I can't get into the recovery mode?
unlock bootloader here http://www.xperiagamer.com/Beginners-Guides/unlock-the-bootloader-ramge.html
im not responsible for any damage:good:
Gianmark said:
I rooted my phone and I found the superuser app on this. Then, I unlocked the bootloader and the superuser app disappered, is it normal?
One more thing, how I flash the custom kernel and the ROM, now?
EDIT: Fail, Superuser is installed, yet, I didn't notice that
EDIT2: Why I can't get into the recovery mode?
Click to expand...
Click to collapse
I see you unlock your bootloader, good job! Place the ROM zip into your SD card first. Next, to get into recovery mode, just fastboot the kernel you want.
-Power off phone.
-Hold search button while connecting to PC via USB
-Open flashtool, click the thunderbolt icon, select fastboot
-Select kernel to flash (select your kernel bootics.img)
-Wait for 2 seconds and voila!
After that, power on your phone, when blue LED lights up with a vibration, spam volume button / back button (depends on kernel) then you'll be able to enter recovery
Gianmark said:
One more thing, how I flash the custom kernel and the ROM, now?
EDIT: Fail, Superuser is installed, yet, I didn't notice that
EDIT2: Why I can't get into the recovery mode?
Click to expand...
Click to collapse
Again, read his guide on flashing kernel and roms: http://forum.xda-developers.com/showthread.php?t=2054512
Which kernel you flash is depended on the rom you want to use it with, you need to flash a GB kernel if you want to use GB rom, ICS kernel for ICS, etc, although some kernel are compatible with both ICS and JB. Search the development section for kernels and roms. If you flash a rom and it fail to boot, it mean the kernel currently installed is not compatible with that rom.
About ClockworkMod Recovery:
If you flash a custom kernel, it will likely have ClockworkMod Recovery included. Or if you are using stock Sony firmware, use the "CWM installer version 5" from this link to install CWM. Sometimes you will get a status 7 error when you try flashing a rom, it might mean you have to use a different version of ClockworkMod to flash that rom successfully.
First of all, thank you both!
Can I flash bootics.img in the Flashtool? The fma965's tutorial speaks about a "*.zip" file besides a "*.img" file.
Also, he says to use fastboot package that I have already used to unlock the bootloader.
EDIT: I need Busybox? What is it? I didn't get it.
Gianmark said:
First of all, thank you both!
Can I flash bootics.img in the Flashtool? The fma965's tutorial speaks about a "*.zip" file besides a "*.img" file.
Also, he says to use fastboot package that I have already used to unlock the bootloader.
Click to expand...
Click to collapse
Flash boot.img in Flashtool/Fastboot as instructions above from jeff7424:good:Zip files are what you put on your sd card and flash with cwm recovery, these can be either roms, updates to roms,zip files to change appearance, performance tweaks, too many to mention.
So .img and .ftf files use in Flashtool/Fastboot and zip files use on SD card to flash with CWM recovery.
Not to complicate it too much sometimes the boot.img comes in a .zip file you need to extract this to use in flashtool/fastboot with winra/7z unzip programs
Edit; Busybox download it with Superuser app on your phone or download a app from store to update your busybox
What is it?http://en.wikipedia.org/wiki/BusyBox
But I don't need busybox to flash kernel and ROM, right?
You can get busybox from Play Store, just search Busybox installer, install it, open the app and install busybox.
jeff7424 said:
You can get busybox from Play Store, just search Busybox installer, install it, open the app and install busybox.
Click to expand...
Click to collapse
I didn't get if I need it to flash kernel and ROM.
Root your phone with zergrush, that will give you busybox too.
jeff7424 said:
Root your phone with zergrush, that will give you busybox too.
Click to expand...
Click to collapse
http://puu.sh/1VV8Q
In that case, I've already installed it.
EDIT: What I have to click? http://puu.sh/1VVgK
"Select Kernel to flash"?
EDIT2: I don't need a custom firmware?
Yeah select kernel to flash. Nope you just need an unlocked bootloader.
I DID IT.
But I'm a bit disappointed because Crash Bandicoot disappered...
Thanks everyone, by the way.
For the future update, the phone will format again?
WARNING: Do not use SEUS to update or repair your phone since you have an unlocked bootloader, if not you'll brick your phone.
jeff7424 said:
WARNING: Do not use SEUS to update or repair your phone since you have an unlocked bootloader, if not you'll brick your phone.
Click to expand...
Click to collapse
SEUS?
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
sblantipodi said:
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
Click to expand...
Click to collapse
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
mwalt2 said:
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
Click to expand...
Click to collapse
is there a way to undo this process once done?
sblantipodi said:
is there a way to undo this process once done?
Click to expand...
Click to collapse
Naturally, backtrack your steps.
beekay201 said:
Naturally, backtrack your steps.
Click to expand...
Click to collapse
Can I safely remove all the files copied from the zip ?
sblantipodi said:
Can I safely remove all the files copied from the zip ?
Click to expand...
Click to collapse
Yes.. Restoring whatever in the process..if you modified anything that was there already.
Galaxy Nexus 4.3 NO ROOT w/ SuperSU_1.51.zip
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
innerspace said:
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
Click to expand...
Click to collapse
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
download the most current supersu.zip and flash it in recovery.
if you're using a toolkit (i bet you are) STOP IT.
Zepius said:
download the most current supersu.zip and flash it in recovery.
about 2 minutes prior to your reply, I updated the "Toolkit" along with all the other items (supersu, img, etc..)
And after that, my device is rooted again.
Although, the main reason I started all of this was to update my device's build further, but it seems the OTA update is now gone... I'll have to wait for it appear again and see how it goes...
Zepius said:
I'll keep that in mind...
if you're using a toolkit (i bet you are) STOP IT.
Click to expand...
Click to collapse
Thanks for the reply!
Much appreciated!
Click to expand...
Click to collapse
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
I did, though I'm fuzzy on how exactly, and no, no toolkits here. IIRC I ended up wiping, updating recovery, and then manually flashing, but I had to do it multiple times to get root to stick. Sorry I don't have any better info to provide, glad to hear a) I wasn't the only one who experienced this problem, and b) you got your root back.
If you root your Xperia phone using Framaroot(Gandalf Exploit), and edit /system files, a random reboot occurs. We have to fix this by Remount-Reboot fix which was originally created by [NUT]. ADB version of this tool has already been shared here and here .
But it requires the use of PC to fully root your phone. I found a flashable version of the same tool and wanted to share with you guys
Download
http://nut.xperia-files.com/?dlid=cmVtb3VudHJlYm9vdGZpeA==
Instructions
1)Download framaroot apk
2)Open the app, select Gandalf exploit ("Install SuperSU" should be selected in the dropdown menu)
3)Keep trying until you get Success notification It will notify you to reboot your device
4)Reboot. SuperSU should be visible in your app drawer. If not, repeat the steps 1-4
5)If busybox is installed, fine and good. Or else the tool will install for you
6)Reboot into recovery and flash the zip file
7)Your phone is now fully rooted
You can test whether your phone is fully rooted by modifying any system app(Like you can rename a bloat app in /system/app) and the phone shouldn't reboot. If it reboots, then your phone isn't fully rooted.
Note: As soon as you have installed this rootfixer and you saw it replace the already installed busybox, remove any and all busybox installer apps you have, it will probably break the rootfixer if you update busybox using that app. The version this rootfixer installs is rock solid and is used by most if not every kernel dev working on Xperia line kernels.
Click to expand...
Click to collapse
Credits
[NUT]
Will this work with Flash Gordon?
This message was brought to you from my Sony Xperia M C1905 using Tapatalk.
Number 6 - reboot into recovery and flash zip
Yeah if you have an unlocked bootloader and elixer kernel which is the only way to have recovery on this phone so far.
Alternatively flash Gordon should work but technically needs full root to flash it via that app
Sent from my C1905 using xda app-developers app
dunc4n88 said:
Number 6 - reboot into recovery and flash zip
Yeah if you have an unlocked bootloader and elixer kernel which is the only way to have recovery on this phone so far.
Alternatively flash Gordon should work but technically needs full root to flash it via that app
Sent from my C1905 using xda app-developers app
Click to expand...
Click to collapse
Yes, you will have to have CWM to flash this obviously. The main aim to create this thread is to enable the users to get full root when you dont have PC with you.
Currently, there are two kernels - ELixir and the 'stock kernel with cwm by alvinhochun'. You can create a flashable version of these kernels and use them, So you dont have to depend on PC to get full root.
The reason why it reboots if you edit system files its because the phone is half rooted if you use Framaroot(Gandalf Exploit) you have to full root it and if you full root it you don't need to flash this
OP dont get me wrong but for now cwm is for only UBL....
in UBL reboot fix is not needed...UBL can mount systems...and can edit them without any issue
in locked BL u cant flash anything...so y did u created this/?
and framaroot wont work on dual sim..
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Rooting will also mess up Ota too, but if u install a custom recovery, now that we have stock recovery it will be very easy to revert back for OTAs, there should be a way to root without a custom recovery but I am not sure how though, but with how oneplus makes it so easy to unlock bootloader and flash customers stuff there is really no need to stay stock
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
pileot said:
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Click to expand...
Click to collapse
As far as I know, you'd have to have TWRP to get root.
I don't think getting it rooted will mess up the OTA updates, other users sprovide flashable zips for the OTA anyway.. so you can still flash the zips manually with TWRP to keep you updated.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
To get root yes, you would need TWRP to flash to certain partitions but to keep root no. Your phone will operate just fine with root and stock recovery. Check what the user a few posts above mine said about temporary flashing TWRP to achieve your short term goals
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
TheSvensson said:
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
Click to expand...
Click to collapse
Yes, I have the stock recovery and it is rooted.
The recovery partition has nothing to do with all the other partitions except that it can read and write them.
This is the zip I flashed to get systemless root:
https://www.androidfilehost.com/?fid=24591000424939898
Some users reported that some Root-apps are not supported this way.
I am using Titanium Backup, Adaway, Trimmer and Root Explorer without issues.
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
All I did was manually flash OxygenOS 3.1.3 in TWRP (not flashed but booted) and reflash the root package afterwards.
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
I have an unlocked bootloader and tried this on my PC:
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.709s]
booting...
OKAY [ 0.373s]
finished. total time: 1.092s
Nothing happens, bootloader start screen stays frozen. Until I hold down the power button. Might you know why?
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
i tried to boot into twrp recovery with above command, but the phone seems to be stuck in the bootloader and not responding. Any ideas?
edit: comment above describes exact same behaviour, sorry for double post
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
AcmE85 said:
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
Click to expand...
Click to collapse
Thanks, that twrp img worked for me. The one I was using didnt allow me to boot to it.
AcmE85 said:
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
Click to expand...
Click to collapse
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
hahamuntz said:
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
Click to expand...
Click to collapse
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
AcmE85 said:
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
Click to expand...
Click to collapse
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
hahamuntz said:
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
Click to expand...
Click to collapse
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
AcmE85 said:
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
Click to expand...
Click to collapse
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
hahamuntz said:
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
Click to expand...
Click to collapse
Yes, OTAs will come and because of Root you will get the full OTA regardless, which does not cause any issues with TWRP.
I tried my previous method and the regular OTA would fail because of root which changes the kernel or the system partition.
OnePlus reacted to this and introduced the full rom OTAs at some point.
So with root on my device this is how I do OTAs now:
- get the OTA notification for the full rom
- download but don't install
- move the downloaded zip from android/data/com.oneplus.ota/files/.OnePlusOta to my download folder
- manually boot into twrp and flash full rom zip + SuperSU
AcmE85 said:
Yes, OTAs will come and because of Root you will get the full OTA regardless which does not cause any issues with TWRP.
Click to expand...
Click to collapse
Okay, thanks so much for your help
Thats the question, can "easily" install magisk on stock rom (.236) unrooted ? since magisk thread says that root is not necessary, its ask for stock boot img that cant be obtained w/o root
JIJOK said:
Thats the question, can "easily" install magisk on stock rom (.236) unrooted ? since magisk thread says that root is not necessary, its ask for stock boot img that cant be obtained w/o root
Click to expand...
Click to collapse
Never tried, but even though root may not be needed, unlocked bootloader probably is. Magisk non-system works by patching boot img... If you unlock bootloader you probably can use it.
levone1 said:
Never tried, but even though root may not be needed, unlocked bootloader probably is. Magisk non-system works by patching boot img... If you unlock bootloader you probably can use it.
Click to expand...
Click to collapse
so, can get the image by just unlock the bootloader ? I though root was necessary for that
JIJOK said:
so, can get the image by just unlock the bootloader ? I though root was necessary for that
Click to expand...
Click to collapse
You can unlocked bl by official Sony method, then flash recovery with adb. Boot to recovery and flash Magisk.
Backup ta - https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Unlock bl - https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader
Recovery img - https://androidfilehost.com/?fid=961840155545588613
You can try flashing recovery within locked bl, but I don't think it would work.
levone1 said:
You can unlocked bl by official Sony method, then flash recovery with adb. Boot to recovery and flash Magisk.
Backup ta - https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Unlock bl - https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader
Recovery img - https://androidfilehost.com/?fid=961840155545588613
You can try flashing recovery within locked bl, but I don't think it would work.
Click to expand...
Click to collapse
So, if you was wondering it, no, cant flash it with locked bl.
At the moment Backup ta didnt work, will check that thread
And thanx the help, nice to have you on z1c forum :good:
perfect. thx! i was already wondering, if i had to downgrade my z1c in order to get the recovery back. but now, how i do i flash magisk from here?
when i try to flash, i get an error message saying, that the ftf is in sony elf32 format and that i need bootbridge from @AdrianDC to flash.
anyone ever did that or has a better idea?
just tried it now and ended up in a bootlop
It is many months after this post, but in case this helps anyone, here is the answer.
BootBridge method is pretty simple and it worked for me.
On an un-rooted device. (important)
Just rename magisk zip to "install.zip" put it in a folder called install.
Then with 7zip, create a zip-file, include the bootbridge folders, "META-INF" and "scripts" with the "install folder" you just created.
Then name it "anything_you_like.zip" and flash with TWRP
Basically Magisk is SuperSU alternative and provides SuperSU service for your device. ( roots it )
No problems for me at this point. Working on 14.5.A.0.270 and can also get working on 14.6.A.0.236 but have other problems related to getting compatible recovery on 236.
Eventually in recovery, system mount and unmount break for me, then other mounts eventually fail after trying to get Nanodroid working (My Goal to UnGoogle my Z1c) and can't wipe format or anything (only way to fix is reflash with flashtool)
Deodexed ROM seems to be necessary for Nanodroid and this is causing additional problems for me.
If I have to run with unlocked bootloader, I think AOSP may be a better starting point.