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.
Related
OK - some help please? I've replaced/unlocked bootloaders and installed cwm/twrp/custom roms and recovery on a dozen android phones and tablets recently - but the TF300TG has beaten me ....
I have recently:
1. Unlocked bootloader on 4.1.1 device using Asus Unlocker v7 (OK - so there goes any warranty )
2. Upgraded to Android v4.2.1
3. Installed JB TWRP - android remains accessible and functional but cannot access partitions from TWRP
4. Replaced TWRP with CWM (recovery-jb) - no improvement
5. Returned to TWRP. However on reboot, the system immediately boots TWRP instead of full android. I am unable to access either Android proper or Fastboot.????
EDIT: I should also add here that I suspect it was some idiot's(umm - that'll be me) foolish Wipe within the TWRP at step 5 above that caused this disaster - and that this removed more than just data. RTFM Richard!!
Not bad for a 4 day old tablet eh? Since I can no longer access fastboot, my guess is that I may need to rebuild the partitions (or at least the partition table) via ADB Sideload. Make any sense? If so, a little guidance really would be appreciated!
TIA,
Richard
Bump?
riclin54 said:
OK - some help please? I've replaced/unlocked bootloaders and installed cwm/twrp/custom roms and recovery on a dozen android phones and tablets recently - but the TF300TG has beaten me ....
I have recently:
1. Unlocked bootloader on 4.1.1 device using Asus Unlocker v7 (OK - so there goes any warranty )
2. Upgraded to Android v4.2.1
3. Installed JB TWRP - android remains accessible and functional but cannot access partitions from TWRP
4. Replaced TWRP with CWM (recovery-jb) - no improvement
5. Returned to TWRP. However on reboot, the system immediately boots TWRP instead of full android. I am unable to access either Android proper or Fastboot.????
EDIT: I should also add here that I suspect it was some idiot's(umm - that'll be me) foolish Wipe within the TWRP at step 5 above that caused this disaster - and that this removed more than just data. RTFM Richard!!
Not bad for a 4 day old tablet eh? Since I can no longer access fastboot, my guess is that I may need to rebuild the partitions (or at least the partition table) via ADB Sideload. Make any sense? If so, a little guidance really would be appreciated!
TIA,
Richard
Click to expand...
Click to collapse
No-one able to help here??
Would really appreciate some guidance before I blow the tablet away completely!
riclin54 said:
Bump?
Click to expand...
Click to collapse
riclin54 said:
Would really appreciate some guidance before I blow the tablet away completely!
Click to expand...
Click to collapse
Once booted in TWRP go to the Reboot menu and "Power Off" then boot into fastboot (it should NOT skip straight into TWRP unless your volume rocker is busted). Once you've got fastboot back ensure you do get the right TWRP!
f69m said:
First of all go to the bootloader screen by holding power and vol-down.
Double-check the Asus version of your bootloader at the top of the bootloader screen and pick the right TWRP version for it:
For Asus v10.4.*: any TWRP *-jb.blob
For Asus v10.6.1.8.*: only TWRP 2.4.4.0-4.2.blob
For Asus v10.6.1.15.*: any TWRP *-4.2.blob
Hope this is clear enough!
Click to expand...
Click to collapse
Thanks for your suggestion Rhian. However I've not yet sorted this. Perhaps a little more info from me will help you help me
The device is running 'Android cardhu-user bootloader <1.0.0 e> released by "WW_epad-10.6.2.3-20130402" A03'. It was unlocked with Asus Unlock_v7 whilst still running ICS and has had Superuser-3.2-RC3-arm-signed.zip installed.
Currently, on initial power up, the device boots straight into TWRP v2.5.0.0 Recovery. I can execute TWRP commands - however there seems to be an issue with access to partitions. Although I can mount the System partition - Cache & Data as well as Micro SDcard and SD-Ext are unmountable (neither can I see block devices in /dev that relate to these). I am however able to access a shell via adb. Further, both volume toggles appear to be operating as they should.
Rebooting from TWRP alerts that "Root permissions appear to be lost". I have attempted to reinstall Superuser but this has not resolved the matter.
"adb reboot boot-loader" will reboot the device into fastboot mode with the boot screen noting "Key driver not found .. Booting OS" and the version info above. From here, I have attempted to use adb to replace TWRP 2.5.0.0 with version 2.4.4.0. Although the adb commands complete without error, the new recovery is not written and the existing 2.5.0.0 remains in place.
From the Fastboot screen on the device, it can be forced to boot Android where everything seems to operate normally and with all partitions and filesystems appearing to be accessible.
All this suggests to me that there is either a problem with the bootloader itself, or less probably, that there is an issue with one or more of the partitions which is interfering with the boot process. There is however a better than even chance that I'm wrong.
I'm considering reformating and replacing the partitions one by one - however this seems rather extreme and in any case, I've not been able to locate an ASUS source of the partitions images yet.
Doing my head in here Rhian - any suggestions?
Thanks,
Richard
Rhian said:
Once booted in TWRP go to the Reboot menu and "Power Off" then boot into fastboot (it should NOT skip straight into TWRP unless your volume rocker is busted). Once you've got fastboot back ensure you do get the right TWRP!
Click to expand...
Click to collapse
Recovery issue
Hi, i have the latest 10.6.1.15.3 rom. I've installed twrp 5.0.0, 4.2 recovery. Now, i can enter to recovery, but if i want to make something, do nothing. It seems, twrp don't see the sd card. Any idea?
Thanks
[Q&A] [RECOVERY][DROID RAZR HD][KitKat ONLY] ClockWorkMod Recovery 6.0.4.9 [2014-06-
Q&A for [RECOVERY][DROID RAZR HD][KitKat ONLY] ClockWorkMod Recovery 6.0.4.9 [2014-06-08]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][DROID RAZR HD][KitKat ONLY] ClockWorkMod Recovery 6.0.4.9 [2014-06-08]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Question about CWM compatibility
djvita said:
f**n found it mirrored
...
Click to expand...
Click to collapse
Hi, I would like to flash CWM and root the device, however I would like to understand first: I have xt925, on the CWM site there is recovery v6.0.4.4 for it, but it says nothing about OS version. Here, you have 6.0.4.9 done specifically for KitKat. So,
1)Why is recovery different for different OS versions?
1.1)Since recovery can be used to flash different ROMs (e.g. I can flash android 4.0 with it), will it work if it is designed specifically for 4.4?
1.2)Recovery is loaded when OS is not yet loaded, or am I missing something?
2)xt925 and xt926 are different only by the band (GSM vs. CDMA), why are recoveries different for them? Are they really different?
3)For my xt925 (details below), which CWM version should I use - the one on CWM site (6.0.4.4.), the one provided in the quoted post?
Now I have system: 181.46.3.XT925.RCI.en.CA
Android: 4.4.2
Build: KDA20.117-3 as of Oct 15 2014
Kernel: 3.4.42-g2c8ced9-0001-g3e4503c
---
Thank you very much!!!
sorry bro i used twrp, found on droidrzr.
it should work. if you run into any issues just reboot to bootloader and flash the recovery you currently have.
Need help with flashing CWM recovery
killrhythm09 said:
Stock ROMs have a script that will check for stock recovery and install it on boot if it's not there.
If you delete /system/etc/install-recovery.sh, you can keep your custom recovery.
Click to expand...
Click to collapse
nobe1976 said:
After you fastboot flash the recovery in. Unplug you device from PC and tap power button to exit fastboot mode. Then enter bootloader mode and select recovery. Once the custom recovery initializes no need to remove the script like suggested below...
Click to expand...
Click to collapse
Hi, I have just unlocked the bootloader and now I am trying to flash CWM, but I get exactly the same sympthoms: flash is successful, but after that I get into stock recovery.
Since I cannot get into custom recovery, I cannot flash root, hence I cannot delete /system/etc/install-recovery.sh (or am I missing something)?
I have tried both unplugging the device and leaving it plugged - anyway, I get the stock recovery... What am I doing wrong???
I have xt925
After successful CWM flash, I unplug the cable. Then I tap power, the screen goes blank. Then I hold volume up + power, get into boot menu. Then volume down, up - select recovery - get the stock...
I have also tried holding both up and down buttons when powering on to get into bootloader menu - same result
----
Found the solution - I was flashing the images that were not placed into platform-tools directory - looks like it caused the problem.
Once I moved the .img to platform-tools and then flashed - everything worked...
A few months later...
sergeyc said:
Found the solution - I was flashing the images that were not placed into platform-tools directory - looks like it caused the problem.
Once I moved the .img to platform-tools and then flashed - everything worked...
Click to expand...
Click to collapse
A few months later:
I have tried doing factory reset from settings menu, but it never worked - the phone would give me all the warnings and then just shut down. I managed to do a factory reset after booting into recovery though.
Also, I noticed that ROM manager would not start the backup process if I select 'backup current ROM' from it - it would just take me to the recovery and there I would have to select the commands.
Recently, I was planning to install cm12 and when I was trying to do backup, I noticed that often I cannot boot into recovery:
-I started by doing 'backup current ROM' from ROM manager and the phone would just shut down
-A few reboots later, I managed to boot into recovery and make a backup to SD
-Then I moved the backuped folder (/storage/sdcard1/clockwordmod/backup/xxx) to the computer while connected as MTP
-I wanted to make another backup to the phone's local storage and now I cannot boot into recovery - neither from ROM manager, nor from bootloader - it just shows the Moto logo for a few seconds and then goes blank.
Looks like the inability of doing factory reset from settings has something to do with it - the boot into recovery was failing.
Also, maybe my original failures had more to do with the fact that I couldn't boot into recovery, rather than the place where the image is located...
Can such problems be due to the fact that I have moved/deleted backups manually and not via recovery's free old backups process?
Note, the command
dhacker29 said:
...
To install you must have fastboot set up on your pc and then:
Code:
adb reboot bootloader
fastboot flash recovery CWM6049-RAZR-HD_M-KITKAT.img
...
Click to expand...
Click to collapse
never gave me any errors and always reported success.
Has anybody else had such situation when booting into recovery would fail 5 times out of 8 or whatever? Is there any resolution?
Please help.
Thanks in advance!
TWRP?
djvita said:
sorry bro i used twrp, found on droidrzr.
Click to expand...
Click to collapse
Was it this one: (/index.php/topic/30174-q-twrp-26xx/ - I'm not allowed outside links, but this is a suffix for droidrzr site) by any chance?
Any issues?
sergeyc said:
Was it this one: (/index.php/topic/30174-q-twrp-26xx/ - I'm not allowed outside links, but this is a suffix for droidrzr site) by any chance?
Any issues?
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/topic/51883-recoverytwrp-2830-01-05-15/
use this, or look for an earlier version
My version is 182.46.15 xt926 rooted. How to unlock bootloader?
Sent from my DROID RAZR HD using XDA Free mobile app
write2aziz said:
My version is 182.46.15 xt926 rooted. How to unlock bootloader?
Sent from my DROID RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
First off, this is a thread about a recovery, please keep your question about unlocking elsewhere. Second off, you can't unlock .15, this has been discussed extensively.
Sent from my HTC6525LVW using Tapatalk
Noob
What happens if you dont have an unlocked bootloader
Well i have a unlocked bootloader and i want to have recovery with that i can upgrade to lollipop too....
Sent from my DROID RAZR HD using XDA Free mobile app
please, you´re my last hope. I´m getting crazy with this task.
Days ago I bought a new XT925. Only reason for this was: CM11 works on this device.
After starting device a playing around little bit I did the KitKat OTA Update from the phones menu.
Tody I decide to go to CM11. So I unlocked the KitKat bootloader via the Motorola website. The site gave me unlock code and with that unlocking bootloader was successfull.
After that I started to flash custom recovery CWM 6.0.4.4 as described in several threads: fastboot flash recovery myfile.img
And with this I stuck: flashing recovery seems to work ok, but I can´t get access to the new custom recovery; Vol up + power, then chosse recovery makes the phone working and after a while phone boots to Kitkatrom as usual.
I already read so many things all this day here in forum, I´m not sure: Do I have to do something before unlocking bootloader, is there some work to do to prepare bootloader for unlocking ? Why can´t I install CWM recovery ??? Do I need root ? Do I need something else ?
I need to have CM11 on this phone, please help me out
Thank you very much.
CWMRecovery doesn't detect phone?
I try to install cm-11-20140104-SNAPSHOT-M2-xt925.zip from external SD Card. CWM Recovery opens package and tries to install, but it says:
This package is for "xt925,xt926,xt907,vanquish_u,vanquish,scorpion_mini,mb886,quinara,asanti,asanti_c,xt897,xt897c" devices; this is a "".
E:Error in /storage/sdcard1/CM11/cm-11-20140104-SNAPSHOT-M2-xt925.zip"
(Status 7)
This looks to me that CWMRecovery doesn't know about the hardware it is running on?
Shadow71XDA said:
I try to install cm-11-20140104-SNAPSHOT-M2-xt925.zip from external SD Card. CWM Recovery opens package and tries to install, but it says:
This package is for "xt925,xt926,xt907,vanquish_u,vanquish,scorpion_mini,mb886,quinara,asanti,asanti_c,xt897,xt897c" devices; this is a "".
E:Error in /storage/sdcard1/CM11/cm-11-20140104-SNAPSHOT-M2-xt925.zip"
(Status 7)
This looks to me that CWMRecovery doesn't know about the hardware it is running on?
Click to expand...
Click to collapse
CM11 M2 Snapshot is for JellyBean Bootloader, this recovery is for KitKat BL..
You have to install a newer cm11 with this recovery.. search for one cm11 moto_msm8960
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know
I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.
First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.
Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.
fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.
Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.
hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys
@[email protected], possible power button problem?
Hi all,
I thought it be good to warn all Alcatel Pixi 4 (4) owners. The current version of the stock rom of the 4034N, which is sold here in the NL has what I think is a terrible bug.
If you enable unlocking in the development options, go to the fastboot, all it takes is to unlock the flash and your phone will get stuck in the boot animation.
I tried to recover by formatting /data (/data is destroyed as could be expected to protect the userdata), but it does not solve the problem.
Flashing a custom ROM like CM13 solves this problem, but I bet this is the reason why I see so many calls on the Internet for Stock ROMs for the 4034N. Have not found a good stock ROM for it and also Alcatels Mobile Upgrade site does not seems to support the 4034N (probably still one software version for it, so no upgrade required yet?).
So better know what you are doing when messing with this phone.
Anybody got the same experience (I can confirm that this was tested by me and my friends with three different Pixi 4's)...
Best regards,
Peter
Good news!
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
I think I'm seeing the same problem with a 4034X (UK variant, as sold by Tesco Mobile). Unfortunately, the mobile update software isn't working for me as it's detecting that I've already got the latest version of the ROM installed already and won't let me install it again. AIUI, the CM13 system has a few issues, so I'd rather not go that root, so would still like a stock ROM if at all possible. Anyone have any pointers?
Hmm. Have managed to get beyond the resetting user data boot loop with the following procedure:
* boot to recovery (power + vol up)
* from recovery menu, choose "boot to bootloader"
* at bootloader, connect via USB to PC
* run "fastboot -w"
* run "fastboot boot <filename for twrp recovery image>"
* at twrp recovery menu, run the standard "wipe" options
* reboot
Haven't yet finished booting, but it's gone to the standard boot animation, which I never succeeded in getting to before.
Update: 8 minutes and counting into the boot process. Doesn't look like it's going to work.
One question worth asking: does this mean that *all* operations that cause a factory reset on an affected 4034 cause a boot loop? Or is it only unlocking the boot loader?
I managed to soft brick my 4034X simply by allowing my email program to encrypt the device. The encryption apparently failed and now it's stuck on boot animation. As @jh3141 said, the Acatel upgrade tool doesn't work. I guess I need to find a stock ROM, but my Googling hasn't found one yet. Can anyone help?
palbeda said:
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
Click to expand...
Click to collapse
Same here with a 4034D - got my phone back alive and still a unlocked bootloader. rooted it, works great.
Thanks!! :good:
i need help
Tampopo said:
Same here with a 4034D - got my phone back alive and still a unlocked bootloader. rooted it, works great.
Thanks!! :good:
Click to expand...
Click to collapse
Can you brake this down for me? am kind of new to all this but i really need to root my device
jh3141 said:
Hmm. Have managed to get beyond the resetting user data boot loop with the following procedure:
* boot to recovery (power + vol up)
* from recovery menu, choose "boot to bootloader"
* at bootloader, connect via USB to PC
* run "fastboot -w"
* run "fastboot boot <filename for twrp recovery image>"
* at twrp recovery menu, run the standard "wipe" options
* reboot
Haven't yet finished booting, but it's gone to the standard boot animation, which I never succeeded in getting to before.
Update: 8 minutes and counting into the boot process. Doesn't look like it's going to work.
Click to expand...
Click to collapse
Any luck with the UK version 4034X?
I'm stuck in the booting process just like you were.
me too - Pixi 4(4) chaos on unlocking.
Absolutely the same experience here.
I have nuked 2 of these trying to unlock. It is a brilliant phone, but this is a painful feature - as you describe.
My history is in one of the threads on this site. - I agree, I would love a stock ROM for it.
palbeda said:
Hi all,
I thought it be good to warn all Alcatel Pixi 4 (4) owners. The current version of the stock rom of the 4034N, which is sold here in the NL has what I think is a terrible bug.
If you enable unlocking in the development options, go to the fastboot, all it takes is to unlock the flash and your phone will get stuck in the boot animation.
I tried to recover by formatting /data (/data is destroyed as could be expected to protect the userdata), but it does not solve the problem.
Flashing a custom ROM like CM13 solves this problem, but I bet this is the reason why I see so many calls on the Internet for Stock ROMs for the 4034N. Have not found a good stock ROM for it and also Alcatels Mobile Upgrade site does not seems to support the 4034N (probably still one software version for it, so no upgrade required yet?).
So better know what you are doing when messing with this phone.
Anybody got the same experience (I can confirm that this was tested by me and my friends with three different Pixi 4's)...
Best regards,
Peter
Click to expand...
Click to collapse
I also softbricked my 4034X after unlocking the bootloader and couldn't get the phone to boot into recovery or the bootloader. I eventually managed to flash a stock ROM with SP Flashtool as described here https://www.getdroidtips.com/install-official-stock-rom-on-alcatel-pixi-4-4/ - this restored the ability to boot into recovery or bootloader but the ROM wouldn't boot so I couldn't enable developer settings to allow OEM unlocking. I then tried flashing the ROM for the dual-SIM version of the 4034X (risky!) and this booted and I was able to unlock the bootloader and flash TWRP recovery. The next problem was when & flashed CM13 and got an error message saying that TWRP couldn't access /data. It then got stuck in a recovery bootloop. Next I used TWRP to format all the partitions but it still couldn't access /data and broke the ability of the Mobile Upgrade Tool to read the phone. My next step is to try flashing a different custom recovery but I'm rapidly losing the will to live and would be very interested in any suggestions.
UPDATE - got it sorted by re-flashing the dual-SIM 4034X ROM (even though I have the single SIM version!), flashing ctr-6.6-4034 recovery, doing a normal wipe then formatting the /data partition then flashed CM13. I guess the data partition must have got corrupted.
I have exactly the same problem with pixi 4 4043f. I unlocked bootloader and then flashed following your instructions on that link you shared. But I see is a white screen frozen no options shown just booting voice behind.... I have flashed it several times but same results I still cant entry fastboot or recovery... Volume down + power or volume up + power dn take me anywhere just that frozen white screen with booting ring tone in the back and thats it... Kindly guide me
i had a similar problem, but i always wanted to flash cm13, so i was fine.
There is an amazing thread here for our device.
For those of you with the 4034X, i have ported cm13 to it specifically, bu there are too many bugs, but if anyone wants it, just tell me!
also, can i just say, softbrick if you oem lock aswell :,(
i wanted to test something, but after fastboot oem lock, and then fastboot reboot, i get an android being repaired? key combo's not working, adb/fastboot not responding, can't remember how i fixed it when i oem unlocked ...
edit-
got into recovery with key combo, now it's just to fix it!
Can any of you guys with the 4034N try this method of rooting? Without unlocking the bootloader?
Masgisk Rooting
kirito9 said:
Can any of you guys with the 4034N try this method of rooting? Without unlocking the bootloader?
Masgisk Rooting
Click to expand...
Click to collapse
For reference: I tried this on a stock 4034X and it failed (couldn't persuade it to boot the custom recovery without going through the full unlock process). Fortunately, there are now copies of the stock ROM available for download (e.g. https://androidfrog.com/a3nr9) so with any luck I won't need to go back to the dodgy CM13 port that constantly runs out of memory and soft-reboots...
Update: I've installed the stock ROM I linked to above, and it seems to be working pretty well. Only issue was that the scatter file that came with it was apparently broken. Fortunately, one that I had hanging around from attempts to fix this problem last time seemed to work with it. I've attached that to this message in case anyone else needs it.
jh3141 said:
For reference: I tried this on a stock 4034X and it failed (couldn't persuade it to boot the custom recovery without going through the full unlock process). Fortunately, there are now copies of the stock ROM available for download (e.g. https://androidfrog.com/a3nr9) so with any luck I won't need to go back to the dodgy CM13 port that constantly runs out of memory and soft-reboots...
Click to expand...
Click to collapse
Thanks, I'll be sure to add a notice for 4034X users in the Magisk guide. I have yet to see a stable CM13 ROM for MT6580 with 3.18.19 kernel. There seems to be an issue with this device chip and ROMs.
Finally got root on the Pixi4-4034
Hi everyone,
yeah I finally managed to root the alcatel Pixi 4-4 (4034) (3G MODEL). It was really tricky and there are quite some issues you have to deal with.
Therefore please read carefully my instructions and remember I am not responsible for any inconvenience, do it at your own risk.
First of all you have to unlock the bootloader and here comes the first problem. On the Pixi4 this operation leads to a sotfbick because the unlocking process deletes completely the data-partition. The phone can't boot anymore and ends in a bootloop.
To resolve this problem you must reflash the phone with SP-Flash-Tool. After reflashing the bootloader remains unlocked so that you should be able to continue with the rooting process. The second problem is that I could find only one working ROM for flashing. It is for the 4034X, my phone was a 4034D (dual SIM), after flashing I had an 4034X what means that my Pixi became a single-SIM phone, I can live with that.
Here are the necessary steps to obtain root on the Pixi4
1. UNLOCKING BOOTLOADER
- Go to settings -> about phone -> hit many times on "build number" till developer message appears
- Enable "OEM unlocking" located in developer options.
- Switch also "USB debugging" on
- Open the command prompt window (cmd)
- Connect the phone to the PC
- Boot into fastboot-mode by typing "adb reboot bootloader"
- Confirm the debug authorization window on the phone, check "always allow from this computer" (afterwards phone should boot into fastboot, otherwise retype the command above)
- Unlock bootloader by typing "fastboot oem unlock"
WARNING: this deletes the data-partition leading in a softbrick and bootloop,
you have to reflash the phone afterwards to continue rooting!
- Confirm the unlocking with the volume-up key
2. REFLASHING THE PHONE
- I found only this working firmware for the 4034X on this page like described by jh3141:
https://forum.xda-developers.com/android/general/warning-current-pixi-4-4-4034n-t3463154/page2
- You have also to use the scatter file described by jh3141
- After loading the scatter-file in SP-Flash-Tool you have to link the missing img-files in the SP-Flash-Tool-Window
- If you flash the 4034X firmware over an 4034D you will end in a single-SIM phone instead of a dual-SIM.
- After flashing the phone will boot again so that you can continue with flashing the twrp-img.
3. ROOTING THE PHONE
- To root the phone you have to install the twrp-image, the one for the Pixi 4034 you find it here:
https://forum.xda-developers.com/showpost.php?p=68049551&postcount=97
- Download and untar the file at the bottom of the page: twrp-3.1.0-0-4034.tar
- Open the command prompt window (cmd)
- Connect the phone to the PC
- Boot into fastboot-mode by typing "adb reboot bootloader"
- Flash twrp by typing "fastboot flash recovery twrp-3.1.0-0-4034.img"
- Download Super-SU "SR1-SuperSU-v2.78-SR1-20160915123031.zip" from
https://download.chainfire.eu/1003/SuperSU/
and put the zip-file on the phone (external or internal storage)
- With the phone switched off boot into twrp by holding power and volume-up keys togehter
- In twrp go to "Advanced" -> "Terminal" -> Type the following code:
echo "SYSTEMLESS=true" > /data/.supersu
- Go back and choose "Install" -> flash the Super-Su-file (SR1-SuperSU-v2.78-SR1-20160915123031.zip)
- Reboot and you’re done, you have root and super-su on the PIXI4
- If you want to uninstall system-apps proceed to the next step.
4. UNINSTALLING BLOADWARE APPS
- You can’t uninstall system-apps directly from the Android-OS,
if you delete the apps with some uninstall-tools it’s strange but the phone will reinstall them after a reboot.
- To succeed you must uninstall the apps in twrp
- Be careful, uninstalling the wrong apps will end in a bootloop or bootfreeze and you will have to reflash the phone starting at step 2.
- Boot into twrp -> go to "Mount" -> check "System" -> go back and choose "Advanced" -> "File Manager"
- In file-manager navigate to the appropriate app-folders and delete the .apk-files
- IMPORTANT: before rebooting you have to wipe the dalvik-cache
- Go to "Wipe" -> "Advanced Wipe" -> CHECK ONLY "Dalvik / ART Cache"
- Confirm wipe and reboot
I personally like the Pixi4-4034, it’s a very small one that is very useful as second phone especially on holidays .
Have fun.
i bricked my alcatel
i have an alcatel pixi 4 (4) 4034x and when i unlocked the bootloader it softbricked my alcatel, the only solution i did was relflash it using spflashtools
same problem
palbeda said:
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
Click to expand...
Click to collapse
I have exactly the same problem. But I haven't been able to find this Mobile_Upgrade_S_4.5.9. Any help will be greatly appreciated,
thnx,
Herman
update: i found the mobile upgrade tool. But it says the latest firmware is already installed. Earlier i tried spft, flashing seemed to go well but the phone stays in animation/bootloop.
Can anybody help?
Is there a sub forum for the Jelly yet? Want to see the ROMs that come out.
YYeeeeeeaaah!! More software for this little miracle!!
My Jelly Pro was delivered today. Looking good so far - just getting to grips with it.
I'got my Jelly Pro today and need root. Any idea how to root my Jelly?
Custom roms for jelly ?
It's a cool little device, and Unihertz seems to be making things easy for the users. Hoping to get TWRP on mine at some point.
Jelly Pro Stock Boot, Stock Recovery & TWRP
I take ZERO credit for any of this. I just received my Jelly Pro and am reposting information I found useful to get TWRP & root. I take no responsibility if you bork your device.
Enable Developer Options (Settings,About phone,click Build number until you see 'You are now a developer')
Go back to Settings, scroll down to the bottom and you'll see a new ‘Developer Options’ entry right above ‘About phone’
Enable OEM unlocking
Enable USB debugging
I also disable animations, just a preference, but not necessary
Make sure your usb drivers and adb/fastboot is set up on your computer
From terminal:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery twrp_jelly_pro.img
fastboot reboot
(hold volume-up and power to go into recovery)
****if something went wrong and you get a "command not found" message, click volume-up & power a few times to go into stock recovery, then do a factory reset and try again)
****when going into twrp, DO NOT allow modifications
In TWRP, go to ADB Sideload and swipe to start
From term: adb sideload supersu-XXX.zip
Back in TWRP, go ahead and reboot
should have TWRP recovery and root
hopefully we'll start seeing some ROM's for this little guy....
1. Stock boot: https://mega.nz/#!UbZASJTI!weBJa4uu9DGoJglpqHQMf3WE6hHplgqPJ7O5UBjDJAQ
2. Stock Recovery: https://mega.nz/#!9SoTVDbY!dZI7XYYSqwPaq2542lQFh5NNXbrA0KTqDCzy-46Dsd0
3. Twrp recovery: https://mega.nz/#!0WICAZwD!cUSG82h1SnuI_cDHWg9ir2w5xb0T-fAl9MrWeClnRBs
4. Latest Supersu flashable zip: http://www.supersu.com/download
(original post: http://www.unihertz.com/bbs/forum.php?mod=viewthread&tid=67&page=3)
(https://www.kickstarter.com/projects/jellyphone/jelly-the-smallest-4g-smartphone)
(https://www.xda-developers.com/jelly-is-a-2-45-smartphone-that-runs-android-nougat/)
I successfully flashed twrp and supersu, but when I reboot, it just goes right back to twrp, and asks for a pattern to decrypt data... Not sure what I might have done wrong. I was able to reset things by flashing stock boot and recovery via fastboot. (as described at http://www.unihertz.com/bbs/forum.php?mod=viewthread&tid=67&extra=page=1&page=3).
I tried again (fastboot flash twrp, sideload supersu) and this time it worked! Just wanted to leave all this here in case anyone else runs into similar problems. Lovely having root again. Can't wait for Lineage to make its appearance!
I ran into the same issue. When phone was delivered, /data was already encrypted.....with what key I don't know.
User "vineethrp" helped me with a similar issue. He is the one that came up with the TWRP recovery and dumped the boot and recovery images. Here are the instructions on post 22:
http://www.unihertz.com/bbs/forum.php?mod=viewthread&tid=67&extra=page=1&page=2
The issue, he suspects, is dm-verity. DO NOT modify system when you boot into TWRP and click on "Keep Read Only". I was able to root and it is booting again.
can we use magisk su?
I was having trouble booting up to Android with TWRP installed, even with the directions in the original thread, so I reflashed stock boot/recovery and installed Magisk Manager. (I was going to use Magisk anyway.) I used it to patch the stock bootloader from the original thread, then flashed the patched bootloader. Magisk works fine now on my Jelly Pro with stock recovery.
If you use an SD card, Magisk and Xposed won’t work unless they are on internal storage.
Wow, I'm surprised root was gained by someone on this thing, but that is awesome! I reckon I'll haveta do it to mine too!
Reckon this thread will get it's own "Unihertz Jelly" section? Moderators?
Yeah, would be good to have a forum to go to...
Will have to root mine now too
Bad customer service!!!!
Placed order through Unihertz website on 9/26/17. I have not even received a confirmation email regarding the order. I even posted to their customer "service" forum hoping to get some reply. It has been three weeks! Now I find out Amazon is selling the JellyPhone with Prime, while the Unihertz site is listing "21 days to 30" days for shipment. As a company that is trying to break into the consumer market(rather than OEM) they should attempt to take better care of customers.
frogman2401 said:
Placed order through Unihertz website on 9/26/17. I have not even received a confirmation email regarding the order. I even posted to their customer "service" forum hoping to get some reply. It has been three weeks! Now I find out Amazon is selling the JellyPhone with Prime, while the Unihertz site is listing "21 days to 30" days for shipment. As a company that is trying to break into the consumer market(rather than OEM) they should attempt to take better care of customers.
Click to expand...
Click to collapse
I bought one on amazon and emailed [email protected] to cancel my orders. They were still in 'processing' status and hadnt shipped.
Cralex said:
I was having trouble booting up to Android with TWRP installed, even with the directions in the original thread
Click to expand...
Click to collapse
I've managed to install TWRP using that instructions. After that I installed SuperSU, then deinstalled SuperSU and installed Magisk. But one app didn't work well, so I decided to reinstall Magisk. And I've made one big mistake: haven't made backup, and got a softbrick. I've managed to unbrick it, but some things goes wrong.
So now I'm looking for stock firmware to flash. If someone can get TWRP backup of all folders except userdata and cache, please upload somewhere and post here the link.
Username I can't imagine said:
I've managed to install TWRP using that instructions. After that I installed SuperSU, then deinstalled SuperSU and installed Magisk. But one app didn't work well, so I decided to reinstall Magisk. And I've made one big mistake: haven't made backup, and got a softbrick. I've managed to unbrick it, but some things goes wrong.
So now I'm looking for stock firmware to flash. If someone can get TWRP backup of all folders except userdata and cache, please upload somewhere and post here the link.
Click to expand...
Click to collapse
Me too with the exact same problem, PLEASE HELP! SOS! :crying:
---------- Post added at 04:07 PM ---------- Previous post was at 03:18 PM ----------
ishehad said:
Me too with the exact same problem, PLEASE HELP! SOS! :crying:
Click to expand...
Click to collapse
I got along!
I entered into the stock recovery (long press on power button + volume up from power off state, and after the recovery loaded, simultaneously pressing on the 3 physical buttons and the "Home" soft button)
I chose wipe data, and then I chose booting to bootloader.
I re-flashed the TWRP recovery, entered it, and using ADB sideload to re-installed SuperSu, and I rebooted to System mode.
The system has been re-uploaded, and without encryption!
I think the problem was that I made a change to the NVRAM, and as soon as I re-flashed the stock boot and recovery, it checks the integrity of the partitions, and does not agree to boot if they are not original. As soon as I returned the SuperSu from the TWRP it canceled the test and allowed to boot as usual. Just a hypothesis, the main thing is that it works ...
I would watch the Unihertz forum they may post firmware there sometime.
http://www.unihertz.com/bbs/forum.php?mod=forumdisplay&fid=43
ishehad said:
I got along!
I entered into the stock recovery (long press on power button + volume up from power off state, and after the recovery loaded, simultaneously pressing on the 3 physical buttons and the "Home" soft button)
I chose wipe data, and then I chose booting to bootloader.
I re-flashed the TWRP recovery, entered it, and using ADB sideload to re-installed SuperSu, and I rebooted to System mode.
Click to expand...
Click to collapse
So can you please backup system and vendor folders using TWRP and upload? I need them Did you do the backup?
Btw you don't need to "simultaneously pressing on the 3 physical buttons" it works with short press power button + volume up. Sometimes it works at first time, but usually you need to press them several times.