Related
Not sure where to post this, as I'm quite new here, but here it goes.
Every time I try to flash the CWM in my M2 d2306 I get a screen black with blinking background led at reboot.
Then, I re-flash the kernel and bootbundle, and everything works okay. But then, no CWM.
What must I do in flashtool? I connect via fastboot, then click in Flash kernel with the .img provided in one of the topics here.
Also, I'm sorry for my newbieness... I used to own a WP 7.8 ....
Power + volume up button press(10 seconds) and off the phone
Open flashtool select firmware wait the connect phone message press volume down button connect pc and wait ending firmware flashing
ishakcez said:
Power + volume up button press(10 seconds) and off the phone
Open flashtool select firmware wait the connect phone message press volume down button connect pc and wait ending firmware flashing
Click to expand...
Click to collapse
I'm really sorry if I'm mistaken:
Well, maybe I'm just too dumb, but... ain't this just the same as I said...? Let me try this again:
1. I install CMW. Then, when I reboot, it gets the bootloop.
2. I, then, install the custom VIVO firmware for my Xperia M2 d2306 (realized that I just need to flash the kernel again). The phone DOES boot.
3. I can't enter recovery mode anymore
Context:
The real problem, actually, is that after all this work, ignoring that the recovery mode got broken, I try to uninstall some system apps, like the VIVO BS, Google Magazine, Xperia Lounge, etc... But after I close the Titanium (or NoBloat Free) the shortcut of the app is still there. It does not launch, giving an stop error or something, but if I reboot, it gets fully restored.
I thought it had something to do with the superSu not being installe properly, so I tried to boot into CMW to reinstall SuperSU., thus beggined my loop with the flash->bootloop->flash-bootloop... :crying:
You have system as writable? When i update from 4.3 to 4.4 i had root but not system as writable so i can't to uninstal apps. TB was showing to me that is uninstaling apps but after reboot they were still instaled. So if you don't have system as writable you can't install CWM and have bootloop.
Sent from my D2303
Dzepar said:
. So if you don't have system as writable you can't install CWM and have bootloop.
Click to expand...
Click to collapse
That seems to be the case, thanks! I'll try to figure out how to make /system writable.
Thank you again
I'm on phone but there was tread for that. Search it ?
Good luck.
Sent from my D2303
Root acces possibly lost.
I guess I let something very important slip...
I was trying to fix system, but couldn't write to sony_ric/enabled, so I've redone the rooting, and just after installing SuperSU, via CWM, I got the following error when I tried to power off:
Code:
Root access possibly l
THIS CAN NOT BE UNDO
- No
- Yes - Fix boot (/syst
As you see, it's missing some characters, so I had no idea of what it said. I've googled it a little and soon found that there may be some workaround,
like using TWRP.
Question time:
1) But can we, users of M2, have a stable access to TWRP (didn't found anything saying no, but neither saying yes)?
2) Does it have something to do with my su binaries been messed up?
3) Does it have something to do with the bootloop?
4) Everytime I install the kernel of my custom firmware, I can't access CWM anymore. Can I fix this or is this the default behavior (or both:fingers-crossed?
PS: I followed this topic: [TUT] Fix Mount System in Kitkat After Root
Two questions answered
tkgcmt said:
Question time:
1) But can we, users of M2, have a stable access to TWRP (didn't found anything saying no, but neither saying yes)?
2) Does it have something to do with my su binaries been messed up?
3) Does it have something to do with the bootloop?
4) Everytime I install the kernel of my custom firmware, I can't access CWM anymore. Can I fix this or is this the default behavior (or both:fingers-crossed?
PS: I followed this topic: [TUT] Fix Mount System in Kitkat After Root
Click to expand...
Click to collapse
Well, I guess I found the answer for two of my questions.
A2) Aparently I was using the Google Play Store version, that is known for not being able to update de binaries, and such...
A4) Using the flashtool removes the root somehow. I don't know how I got it working the first time, though, but now none of my apps given root access works. I'll try this: http://forum.xda-developers.com/xperia-m2/general/root-d2303-kitkat-18-3-c-0-40-locked-t2929893
update
Just an update.
The method of Engineer91 didn't worked out for me, as OTA fails to update me to 4.4.2
I've tried to flash the kk with flashtool, ticking (removing from the flash) only the kernel (as seen in androidclub, but then I got a bootloop again.
I'm running out of ideas... does anyone knows what can I do to fix the system not being able to be mounted as writable in the KK (Android 4.4.2)?
This guide will show you how to root Lollipop 5.0.1 for the GT-I9500/i9505 ONLY!
With NOOBS support
Method 1 (GT-I9500)
Steps:
1 - Download cf-auto-root: Click Me
2 - Connect your phone to pc
3 - Open odin
4 - Go to download mode by holding the volume down + home key+ power key at the same time, then press volume up
5 - Extract and Flash the file via odin (AP or PDA)
Method 2 (GT-I9500/GT-I9505)
Steps:
1 - Download philz touch recovery GT-I9500 : pCloud Dropbox
Download philz touch recovery GT-I9505 : pCloud Dropbox
or Download CWM recovery: Click Me
2 - Connect your phone to pc
3 - Open odin
4 - Go to download mode by holding the volume down + home key+ power key at the same time, then press volume up
5 - Flash the recovery via odin (AP or PDA) (if you are on i9505 uncheck auto-reboot)
- After the device reboots
6 - Download the SuperSU or Dropbox
7 - Go to the recovery by holding the volume up + home key + power key at the same time
8- Flash the SuperSU file from recovery (Select "Install zip") and locate the file
9 - Reboot.
Method 3 (GT-I9500)
Steps:
1 - Download philz touch recovery GT-I9500 : Click Me
2 - Connect your phone to pc
3 - Open odin
4 - Go to download mode by holding the volume down + home key+ power key at the same time, then press volume up
5 - Flash the recovery via odin (AP or PDA)
- After the device reboots
6 - Go to the recovery by holding the volume up + home key + power key at the same time
7 - Now go to Philz settings --> Re-root System --> Yes Apply SuperSU
8 - Download SuperSU from Play Store
9 - Open the SuperSU and he should ask you, how do you want to update binary? select NORMAL
Have Fun.
If you dont get philz touch recovery on both i9500 & i9505 then flash the cf-auto-root and follow the steps.
cf-auto-root gt-i9500: Download
cf-auto-root gt-i9505: Download
cf-auto-root credits for method 1 goes to @Chainfire
Your Warranty will be voided!
im not responsible about any soft or hard brick or your phone!
MENTION ME IF YOU USE ANY OF MY LINKS!!
Receive OTA again and keep your data : http://forum.xda-developers.com/galaxy-s4/general/guide-t3024497
Wonderful! Does anyone know if how compatible xposed modules are with the new update?
Giorgios1 said:
Wonderful! Does anyone know if how compatible xposed modules are with the new update?
Click to expand...
Click to collapse
Xposed is incompatible with the ART runtime. That means it won't work on Lollipop.
This thread doesn't belong in Original development,not even in Android development.
Moved to General section.
my experience:
installation failed ----> reboot ----> stuck at samsung logo
Rando81 said:
my experience:
installation failed ----> reboot ----> stuck at samsung logo
Click to expand...
Click to collapse
Exactly the same happened to me .... !!!!
samsung bootloop
i followed all the steps here and my phone got stuck on boot logo.
didnt have enough time to find a proper solution except doing a factory reset delete and cache delete.
didnt work out for me so i flashed the rom again and now it's working.
is there any other way to root my device without any bootloops?
@Rando81 @davie088 @username0101
it works fine with me, but...
try going to a higher version with the recovery
or ill find a another way to root after some tries
Thank u bro...
mdimrankhangr said:
Thank u bro...
Click to expand...
Click to collapse
anytime man!
Azar_98 said:
i followed your method and it kinda worked. installed recovery, system re root. installed supersu from play and it asked me to update binary. i accepted but it failed to update for some reason and asked me to reboot. i clicked reboot and got stuck at bootloop. i tried clearing dalvik and wipe data from recovery, still bootloop. so i guess it tried to modify a system file which did it wrongly and caused it to fail. either the binary isnt compatible with this rom, although it was compatible with chinese aurora 5.0.1. for now, im back to aurora. has anyone had any success rooting this? ill try tomorrow morning again. thanks
Click to expand...
Click to collapse
i dont know bro, it worked for me and some of members as well!
im trying some methods but i cant confirm that it will work with all of you, but try flashing this with odin download
tell me if you rooted your phone!
same problem
tell us if it worked for u
For all that couldn't succeed with the original SuperSU, use this one
Flash from recovery.
Worked for me.
Had the same problem, this is how I fixed!
I followed the instructions in OP, but was stuck in boot animation.
This is what I did to finally get root.
1. Flash CF-Autoroot through ODIN.
2. It should boot, but the SuperSu app is really outdated.
3. Update SuperSu.
4. It should ask you to update the binary.
5. Try updating through the Normal method.
6. For me it failed, and the app told me to reboot and retry.
7. I rebooted the phone, but the phone was stuck in boot animation (just like with the instructions in OP).
8. (Without wiping anything) I flashed Philz Touch recovery through Odin.
9. I downloaded SuperSu app that is flashable through recovery.
10. Rebooted and finally got root!
wta
Millenium3 said:
I followed the instructions in OP, but was stuck in boot animation.
This is what I did to finally get root.
1. Flash CF-Autoroot through ODIN.
2. It should boot, but the SuperSu app is really outdated.
3. Update SuperSu.
4. It should ask you to update the binary.
5. Try updating through the Normal method.
6. For me it failed, and the app told me to reboot and retry.
7. I rebooted the phone, but the phone was stuck in boot animation (just like with the instructions in OP).
8. (Without wiping anything) I flashed Philz Touch recovery through Odin.
9. I downloaded SuperSu app that is flashable through recovery.
10. Rebooted and finally got root!
Click to expand...
Click to collapse
are u keep the zip. file (update superSU v2.45) in the sd card n then install it with philz touch recovery ??
Woking Steps!!
Steps confirmed working:
1. Download and place superSU app into internal or external memory , from http://download.chainfire.eu/695/SuperSU/UPDATE-SuperSU-v2.45.zip
2.Flashed Philz Touch recovery through Odin. from https://my.pcloud.com/publink/show?code=XZs3BkZPWCE8hherxXnBPFJJc7ubQdC3Fv7
3. Boot into recovery, by 3-button combo .
4. Flash superSU app through recovery.
Done !! rooted
Hit Thanks if usefull
i am seeing a lot of ways guys. which way to root is working?
Try the methods above
If not the method 1 then try method 2
anuraagkochar said:
i am seeing a lot of ways guys. which way to root is working?
Click to expand...
Click to collapse
My question to
Sent from my GT-I9500 using XDA Free mobile app
RubbaBand said:
Try the methods above
If not the method 1 then try method 2
Click to expand...
Click to collapse
which above method? there are a lot
SOLVED!
Hey there,
i just tried flashing TWRP (twrp-3.1.0-0-zeroflte.img.tar) via Odin (Odin3_v3.12.4_4) on my Samsung Galaxy S6 on nougat 7.0 and am stuck in bootloop (GALAXY S6-Bootscreen reappearing every 6 seconds). My device is not rooted, but i do have access on TWRP 3.1.1-0 and the Download Mode. I did not care about tripping knox as PingPongRoot doesn't support my Buildnumber (yet).
Is there any way to fix the bootloop without resetting my device to stock?
I tried wiping the caches, but nothing changes.
Any help is appreciated! :angel:
Download mode says:
Product name: SM-G920F
Current binary: Custom
System status: Official
Reactivation lock: Off
Secure download: enabled
Knox warranty void: 1 (0x030c)
Ap Swrev: B:5 K:2 S:2
Note:
I do have a root file (N920_Nougat_Root_SuperSU-No_kernel_included.zip) on my device that could be installed via TWRP, but that doesn't help at all, right?
Reflashing – Odin doesn't recognize S6
I tried reflashing, but Odin does not recognize the S6 at all.
No device is beeing 'added'.
Could i transfer my user data (pictures, music) via adb through twrp to my computer?
I didn't backup, stupid as i am
Problem solved!
I solved the problem by flashing the root file (N920_Nougat_Root_SuperSU-No_kernel_included.zip) via TWRP-Recovery.
After this step, the phone rebooted and all my user data remained. Root & TWRP working just fine. :good:
JoLien said:
I solved the problem by flashing the root file (N920_Nougat_Root_SuperSU-No_kernel_included.zip) via TWRP-Recovery.
After this step, the phone rebooted and all my user data remained. Root & TWRP working just fine. :good:
Click to expand...
Click to collapse
Can you tell the step you took to flash your S6 with TWRP. I have S6 G9200 dual sim. When i flash with TWPR my phone could not boot again. it kept repeating Samsung logo every 6 second.
Thank you
Baba Kay said:
Can you tell the step you took to flash your S6 with TWRP. I have S6 G9200 dual sim. When i flash with TWPR my phone could not boot again. it kept repeating Samsung logo every 6 second.
Thank you
Click to expand...
Click to collapse
1. Google or baidu the following twrp unofficial build "TWRP-3.1.0-G9200-G9208-G9209-G920D-G920P.tar" (Official TWRP builds will not work because they are for G9200 HK version)
2. Open Odin 3.1x.x and and uncheck the "Auto Reboot" option
3. Put the G9200 onto download mode and flash
4. Disconnect the usb cable
5. Hold "Volume Down + Power" (Hard restart) for 5 seconds and once screen goes black immediately release and hold "Volume up + Home + Power" (Launch Recovery)
6. You should see TWRP working If you did above steps correctly.
7. Now you got TWRP but OS is stuck in bootloop.
8. Flash latest Magisk or SuperSu with TWRP.
9. You're good!
KittyChampion said:
1. Google or baidu the following twrp unofficial build "TWRP-3.1.0-G9200-G9208-G9209-G920D-G920P.tar" (Official TWRP builds will not work because they are for G9200 HK version)
2. Open Odin 3.1x.x and and uncheck the "Auto Reboot" option
3. Put the G9200 onto download mode and flash
4. Disconnect the usb cable
5. Hold "Volume Down + Power" (Hard restart) for 5 seconds and once screen goes black immediately release and hold "Volume up + Home + Power" (Launch Recovery)
6. You should see TWRP working If you did above steps correctly.
7. Now you got TWRP but OS is stuck in bootloop.
8. Flash latest Magisk or SuperSu with TWRP.
9. You're good!
Click to expand...
Click to collapse
Thank you
Great job. it works for meeeee
Baba Kay said:
Thank you
Great job. it works for meeeee
Click to expand...
Click to collapse
Did you figure out a way to install Google Play?
KittyChampion said:
1. Google or baidu the following twrp unofficial build "TWRP-3.1.0-G9200-G9208-G9209-G920D-G920P.tar" (Official TWRP builds will not work because they are for G9200 HK version)
2. Open Odin 3.1x.x and and uncheck the "Auto Reboot" option
3. Put the G9200 onto download mode and flash
4. Disconnect the usb cable
5. Hold "Volume Down + Power" (Hard restart) for 5 seconds and once screen goes black immediately release and hold "Volume up + Home + Power" (Launch Recovery)
6. You should see TWRP working If you did above steps correctly.
7. Now you got TWRP but OS is stuck in bootloop.
8. Flash latest Magisk or SuperSu with TWRP.
9. You're good!
Click to expand...
Click to collapse
What version of Magisk should I flash? I read that v14 has problems...
alex27riva said:
What version of Magisk should I flash? I read that v14 has problems...
Click to expand...
Click to collapse
V14 worked fine for me
It checks MD5 than says please wait and stops responding (nvm it was a bad file)
Had same problem, but more intense - my phone did not react to pressing VolumeUp+Home+Power, just bootlooped even in this mode
I don know how much time I pressed VolumeDown+Power (like 2 minutes), but eventually it just powered down
After that I was able to boot into twrp
In TWRP I flashed Magisk16 and wiped dalvik cache
Now It works
Also e2fsck'ed /dev/block/sdaSOMETHING
P.S. sorry, English is not my language
Samsung S6, cannot flash
i have samsung s6 sm-g920i, which is stuck in bootloop mode, i can however go to download mode but i can't flash it using odin with any files (stock rom, custom rom, combination file, twrp )
can't see any increase in the bar of the phone when the flashing process starts ( the phone is just as it is before no line of process increase shown), the phone is recognized by odin ( it shows added with blue line on the com part) but the problem is i can't flash anything in it.
flashing always fails.
won't go to recovery mode as well.
current binary : custom
system status : custom
reactivation lock : off
secure download : enabled
knox warranty void : 1
ap swrev : 8:3 K:2 s:2
sw rev. check fail. device : 2 binary : 1
can anyone please help
thanks in advance
KittyChampion said:
1. Google or baidu the following twrp unofficial build "TWRP-3.1.0-G9200-G9208-G9209-G920D-G920P.tar" (Official TWRP builds will not work because they are for G9200 HK version)
2. Open Odin 3.1x.x and and uncheck the "Auto Reboot" option
3. Put the G9200 onto download mode and flash
4. Disconnect the usb cable
5. Hold "Volume Down + Power" (Hard restart) for 5 seconds and once screen goes black immediately release and hold "Volume up + Home + Power" (Launch Recovery)
6. You should see TWRP working If you did above steps correctly.
7. Now you got TWRP but OS is stuck in bootloop.
8. Flash latest Magisk or SuperSu with TWRP.
9. You're good!
Click to expand...
Click to collapse
You are genius! Thank you very much bro. You saved me! ❤
JoLien said:
Problem solved!
I solved the problem by flashing the root file (N920_Nougat_Root_SuperSU-No_kernel_included.zip) via TWRP-Recovery.
After this step, the phone rebooted and all my user data remained. Root & TWRP working just fine. :good:
Click to expand...
Click to collapse
thank you very for this, i kinda panicked a little after flashing twrp and it stucked at boot loop. i needed my stock rom before flashing different rom. luckily a quick search there i find similar issue
only one problem, i had to make a back up again with supersu after i booted the phone haha
Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !
@Asansi
I'm sorry I can't help you, but may I ask how you rooted the phone? I can't get mine to be properly rooted.
I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA
HackerAce said:
I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA
Click to expand...
Click to collapse
Apologies for ressurecring a zombie thread but, OP has a spark X and you have a Spark, so it would appear that you SENIOR person in that model failed at the very first hurdle.
Am still wonderng if there is an sign of a 7.0 compatible twrp for spark X? Don't suppose anyone has a link to the latest Spark X firmware either?
TWRP versions
Asansi said:
Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !
Click to expand...
Click to collapse
I've tried TWRP 3.0.2-0 (i.e. latest from https://dl.twrp.me/porridgek3/): it flashes Ok but it won't boot up afterwards. I've tried 3.0.2-0 but as you say "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. Have you progressed with this issue? BTW I've emailed TWRP Support (from their web page) asking if they have a working version.
Same problem here, It's pretty annoying. My sister's getting this same phone (on Android 6) soon so I might just make a full backup with TWRP on it and somehow restore it on my phone.
Systemless Root
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?
Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs
Systemless Root
ScreamingSteve said:
Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs
Click to expand...
Click to collapse
Steve,
Have you tried the method detailed in post #7?
johnaaronrose said:
Steve,
Have you tried the method detailed in post #7?
Click to expand...
Click to collapse
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?
TWRP
ScreamingSteve said:
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?
Click to expand...
Click to collapse
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.
johnaaronrose said:
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.
Click to expand...
Click to collapse
Thanks a lot, I'll try your method, the explicit call to boot the TWRP image could really help.
Thanks for your extended explanation tho, showed me some new ways to eventually get this stuff to work.
Sent from my Wileyfox Spark X using XDA Labs
johnaaronrose said:
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?
Click to expand...
Click to collapse
Finally, your advice with "Fastboot boot twrp.img" worked magic!
Got twrp installed, but now I'm facing the same problem as you with the systemless root. I'll dig around a little and see what I can find.
Unlock Bootloader and Root BLU R1 Plus
Yes it has been done
Thanks to @lopestom for all his help and porting TWRP to this device
Thanks to RootJunky for FRP Unlock.img
Thanks to Larry Miller for testing with his device
This has been done to Three 16 G devices and One 32 G device to date
WARNING:
Code:
[B][COLOR="red"]
DO NOT FLASH RECOVERY WITH SP FLASHTOOL AS IT
COULD BRICK DEVICE!![/COLOR][/B]
For use SPFT you need special file. So here's the best way is using ADB-fastboot to unlock bootloader, flash FRP Unlock.img and recovery!!
At all times it is necessary to think in safety not to have a bricked device.
Then for the uninformed users:
Code:
[B][COLOR="Red"]MAKE A BACKUP OF THE ROM WITH TWRP AND COPY FOR YOUR PC![/COLOR][/B]
This method uses adb and fastboot commands to achieve root
Before any actions: copy all that you need from SDcard internal to PC!
If you want backup calls, messages, contacts (different by goggle contatcs or if you can record all the contacts in your google contacts account directly through the contacts application).
For backup, use any application from google play! Save in your PC! After all the processes you can restore them using the same application that you used.
- Instructions to PROCESS:
1. On phone open setting
about phone, tap 7 times in build number
Enable Developer Options
Enable USB Debugging
2. On PC search the folder of adb and fastboot minimal ( included in zip to install }
Unzip and Place unlock.img , recoveryTWRP.img and SR3-SuperSU-v2.79-SR3-20170114223742.zip in adb and fastboot minimal folder
Open adb terminal
Code:
adb devices
to ensure connection
Code:
adb reboot bootloader
Code:
fastboot flash frp unlock.img
Code:
fastboot oem unlock
( Confirm with volume up select on phone )
Code:
fastboot flash recovery recoveryTWRP.img
Fastboot will show image flashed but due to BLUs locking of device fastboot reboot will not function
So ….
Unplug device , Hold power off until device turns off
Hold Volume up and Plug device back into PC ,
Continue to hold volume up until TWRP boots fully
Select Wipe , Select Format Data ( don’t worry if any errors show )
Reboot TWRP Recovery
Select Mount , Select Mount USB Storage
Open Device on PC , Move SR3-SuperSU zip to device external_sd
Unmount
Select Install
Select external_sd
Select SU zip and install in TWRP
Select Reboot System
Phone May reboot several time do not interrupt boot
Unlocked bootloader and TWRP
xposed arm v89 has been tested and works , Gravitybox 6.5.3 has been tested and works
Download link
TWRP_Root_R1_Plus.zip
mirror: TWRP Root R1 Plus.zip
William Smith
XDA:DevDB Information
[TUT] Unblocking & Unlocking - Installing TWRP - ROOT, Kernel for all devices (see above for details)
Contributors
lopestom, donnasbrt1
Source Code: https://forum.xda-developers.com/android/general/blu-blu-vivo-kernel-sources-t3767993
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-09-18
Created 2018-09-19
Last Updated 2018-09-24
More in info: Stock ROM - TWRP - TWRP Backup - Lineage 14.1 (almost bug free)
Link of Stock ROM - TWRP - TWRP Backup - Lineage 14.1 (almost bug free)
Click me post #13
.
lopestom said:
Unlock Bootloader and Root BLU R1 Plus
Yes it has been done
Click to expand...
Click to collapse
This is too late for me. I returned this phone long ago.
Add one more 32G device, very happy now, this has been in the closet waiting for root and today it comes to life! Can't thank you enough!!! Works great!!!
---------- Post added at 12:53 AM ---------- Previous post was at 12:20 AM ----------
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?
Donphillipe said:
Add one more 32G device, very happy now, this has been in the closet waiting for root and today it comes to life! Can't thank you enough!!! Works great!!!
---------- Post added at 12:53 AM ---------- Previous post was at 12:20 AM ----------
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?
Click to expand...
Click to collapse
both of them have built in part of there install, a series of commands that remove other root, But is best to remove su before flash majisk. From the superSU app. in the menu is option to full remove superSU. Do that, then reboot make sure it is ok. Then try magisk. Note that it 'should' work, but it seems you will be first to try it.
Just tried to uninstall SuperUS and it no longer boots, locks up at the BLU screen. I was following these steps: https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Should have made a backup when I had the chance. Oh, well it's like they say, live and forget and forget again.
So I guess I'll cross my fingers that this factory image I downloaded is not full of malware and is on the up and up.
The factory image I downloaded must be corrupt or something else is wrong. I tried flashing the factory image I downloaded "Blu_R0051UU_MT6737M_V13_REPAIR" and I received the error: ERROR: SBROM_DOWNLOAD_DA_FAIL (2004)
I still can boot to TWRP but I have no backup image in this format. If anyone has a factor or TWRP to share, please let me know.
Tried a different laptop, a couple of new cables and the error is still the same (see above) using the latest version of Flash Tool (v5.1828.01) to download the supposed stock ROM found online (http://www.mediafire.com/file/25su5934zm65vgb/Blu_R0051UU_MT6737M_V13_REPAIR.zip). I also deselected everything in Flashtool from the scatter file except "system" and it still would not load. Note that the only way to put the phone in a state that will communicate with the flash tool is to first hold the vol up and power button for a long time and keep holding them in until the BLU logo disappears and the TWRP menu appears. Here you select Reboot and then Power Off and only then will the flash tool try to communicate with the device when you plug the USB cable in. That's when the long red bar moves across the footer of the screen with 100% and a little later the error messages I named above occurs. Looks like I'm bricked unless I can find a kind soul to share a TWRP backup.
Donphillipe said:
Tried a different laptop, a couple of new cables and the error is still the same (see above) using the latest version of Flash Tool (v5.1828.01) to download the supposed stock ROM found online (http://www.mediafire.com/file/25su5934zm65vgb/Blu_R0051UU_MT6737M_V13_REPAIR.zip). I also deselected everything in Flashtool from the scatter file except "system" and it still would not load. Note that the only way to put the phone in a state that will communicate with the flash tool is to first hold the vol up and power button for a long time and keep holding them in until the BLU logo disappears and the TWRP menu appears. Here you select Reboot and then Power Off and only then will the flash tool try to communicate with the device when you plug the USB cable in. That's when the long red bar moves across the footer of the screen with 100% and a little later the error messages I named above occurs. Looks like I'm bricked unless I can find a kind soul to share a TWRP backup.
Click to expand...
Click to collapse
Larry Miller has also supplied a TWRP backup for this device ..thanks Larry
TWRP backup
Donphillipe said:
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?
Click to expand...
Click to collapse
With Supersu installed you can install Magisk and after remove suspersu......
Donphillipe said:
Just tried to uninstall SuperUS and it no longer boots, locks up at the BLU screen. I was following these steps: link
Should have made a backup when I had the chance. Oh, well it's like they say, live and forget and forget again.
So I guess I'll cross my fingers that this factory image I downloaded is not full of malware and is on the up and up.
Click to expand...
Click to collapse
After removed Supersu or Magisk the ROM can't start because have Custom recovery installed and made modified system option..... So in this case need install again supersu or magisk!
At all times it is necessary to think in safety not to have a bricked device.
Then for the uninformed users: MAKE A BACKUP OF THE ROM WITH TWRP AND COPY FOR YOUR PC!
Sent from my BLUBOO Xtouch using XDA Labs
Fixed, can't thank you enough!
Wiped the phone and did a full restore, everything looked good. I rebooted to TWRP tried to install Magisk V 17, 17.1 and 17.2 and all of them fail install with error;
! Boot image patched by unsupported programs
! Please restore stock boot image
Updater process ended with ERROR : 1
Error installing zip file xxxxxx
---------- Post added at 03:25 AM ---------- Previous post was at 03:10 AM ----------
Also fails SafetyNet check, not sure if it is supposed to or not. This is after restoring from the TWRP image supplied above and without rooting with SuperSU.
I no have the device in my hands. So you can install old version of magisk v15 or v16?
So if you need more information so you can enter here: BLU Development Team
Donphillipe said:
Wiped the phone and did a full restore, everything looked good. I rebooted to TWRP tried to install Magisk V 17, 17.1 and 17.2 and all of them fail install with error;
! Boot image patched by unsupported programs
! Please restore stock boot image
Updater process ended with ERROR : 1
Error installing zip file xxxxxx
Also fails SafetyNet check, not sure if it is supposed to or not. This is after restoring from the TWRP image supplied above and without rooting with SuperSU.
Click to expand...
Click to collapse
More in info on device R1 Plus
For anyone having issue with root or device issues .
If you can return to twrp and select power off this will allow required selection for so flashtool .Or if bootloop press and hold button combo and insert USB during power down of bootloop . Button combo for preloader is volume up and then power button then plug in device
Stock ROM here
https://www.mediafire.com/download/nbm2vt2dne5s2pc
TWRP
https://www.mediafire.com/download/hjmjpgepfbnjy7h
TWRP Backup
https://www.mediafire.com/download/eaxx8fla8a9a247
Lineage 14.1 (almost bug free)
https://www.mediafire.com/folder/fqqj9hqqascs0/Lineage 14.1 R1 Plus
Lineage has bug in OFF charging animation phone charges just no animation and rear camera macro focus
No other bugs have been found at this time
Xposed does work with this build v89-sdk25 arm
Thanks to Lopestom and Larry Miller for there support with this
donnasbrt1 said:
For anyone having issue with root or device issues .
If you can return to twrp and select power off this will allow required selection for so flashtool .Or if bootloop press and hold button combo and insert USB during power down of bootloop . Button combo for preloader is volume up and then power button then plug in device
Stock ROM here
https://www.mediafire.com/download/nbm2vt2dne5s2pc
TWRP
https://www.mediafire.com/download/hjmjpgepfbnjy7h
TWRP Backup
https://www.mediafire.com/download/eaxx8fla8a9a247
Lineage 14.1 (almost bug free)
https://www.mediafire.com/folder/fqqj9hqqascs0/Lineage 14.1 R1 Plus
Lineage has bug in OFF charging animation phone charges just no animation and rear camera macro focus
No other bugs have been found at this time
Xposed does work with this build v89-sdk25 arm
Thanks to Lopestom and Larry Miller for there support with this
Click to expand...
Click to collapse
Hello, which driver did you use? I can't get download mode work right
When loading bootloader ..power off device ...press volume up ..then power ( at the same time ) then plug device into pc ..device should load ..then device should flash .. do not flash preloader or imei issues may result
Any update on the progress lineage 14.1 on this phone? I use it for a day waa bit laggy
Not at this time Lineage 14.1 was a test run for the device and I have not had time to finish yet and am also working Resurrection Remix right now .Camera porting has been a bit tricky as there are alot...alot of simlinks on stock rom for camera functions . I will have more time soon to work on it a bit more
donnasbrt1 said:
Not at this time Lineage 14.1 was a test run for the device and I have not had time to finish yet and am also working Resurrection Remix right now .Camera porting has been a bit tricky as there are alot...alot of simlinks on stock rom for camera functions . I will have more time soon to work on it a bit more
Click to expand...
Click to collapse
Any update or ETA? I might put off a phone purchase if a build with a working camera comes along.... P.S. Another annoying bug I face is that videos don't play in some apps e.g. google photos, WhatsApp statuses and on Snapchat. Videos on Youtube and Facebook play fine. Fingers crossed for some good news! Wishing you a happy holiday season!
You can allways run stock rooted with xposed and gavitybox until bugs are worked out. Just a thought .Happy holidays to you also
+1 32G successful
Thanks for this! Waited for so long for a method.
Now: since I'm kinda newbie to root, I'm doubtful on how to detect custom kernels to flash based on this device model. Or is it possible to flash whatever?
I need something like 'ElementalX' or related.