[REF]Spice Dream Uno Stock OTA URLs - Spice Dream Uno

Introduction:
This is a list of all known OTA's for the Spice Dream Uno
The Dream Uno has it's ROMs built directly by Google, instead of Spice.
Click to expand...
Click to collapse
File List:
None Yet
Click to expand...
Click to collapse
How to flash:
Requirements:
Stock recovery
Unmodified /system
Unmodified /oem
Unlocked bootloader
Basic understanding of command line/shell
Unlock your bootloader
Download and set up adb and fastboot
Reboot into fastboot mode
Open up a command prompt/shell where you saved fastboot
enter into command prompt/shell: "fastboot oem unlock"
Enter recovery mode via onscreen buttons
Enable recovery ui
(How do you do this for this device?)
Set up adb
Select apply update from adb
enter into command prompt: "adb sideload <path to saved update.zip>
Click to expand...
Click to collapse
FAQ:
How to find the ota?
If you're rooted, wait for the device to prompt you to update, then check /cache for the file
If you're not rooted, wait until the same time and do an adb logcat and look for a line with .zip in it
Why isn't the latest ota listed?
We can only list what we have, if the ota from Build X to Build Y isn't listed, we dont have the file for it yet.
How do you setup adb/fastboot
Please read the stickies in the general subforum, this is not a formal guide
Do I need to unlock the bootloader to flash the update zip?
Yes, if you wish to do it manually.
If you allow android to prompt for the update, you do not need to unlock
Can I flash this if I have a custom rom?
No, you must be on a stock AND unmodified rom
Can I flash this if I'm rooted?
Only if you have not modified any files
Click to expand...
Click to collapse
Credits:
Click to expand...
Click to collapse
Changelog:
Sep 21, 2014: Initial page
Click to expand...
Click to collapse
2char

can anybody give me backup of rom

If anyone has seen an ota recently, please let me know.
There is an android-4.4.4_r4 listed on AOSP, and KPW53 should be 4.4.4_r3.
Either it is an ota or another device launched with a newer rom.

Related

Lg G2 LS980 Will not boot

I had stock android installed. And I had rooted. I tried to use flashify to install TWRP, but every time it rebooted it would go into fastboot mode. well, I didn't think it would be an issue if I decided to just let the stock update run it's course instead of flashing a rom. So I had the OTA for kitkat run. The phone rebooted, and will only boot into fastboot, and download mode. I need help to get back to stock of any form, root or no root. Please? I am quite far from any repair center at a hotel for the next few days, so Wi-Fi is quite slow.
i
eddytheyeti2 said:
I had stock android installed. And I had rooted. I tried to use flashify to install TWRP, but every time it rebooted it would go into fastboot mode. well, I didn't think it would be an issue if I decided to just let the stock update run it's course instead of flashing a rom. So I had the OTA for kitkat run. The phone rebooted, and will only boot into fastboot, and download mode. I need help to get back to stock of any form, root or no root. Please? I am quite far from any repair center at a hotel for the next few days, so Wi-Fi is quite slow.
Click to expand...
Click to collapse
at least u need to download another stock firmware to flash it through recovery
:good:
x102x96x said:
at least u need to download another stock firmware to flash it through recovery
:good:
Click to expand...
Click to collapse
I don't have a recovery. I'm at fastboot or download. No recovery...
i
eddytheyeti2 said:
I don't have a recovery. I'm at fastboot or download. No recovery...
Click to expand...
Click to collapse
so flash recovery by adb and then use recovery to install rom
:good:
Hit Thanks
flash twrp to it, while in fast boot using ADB
http://download1983.mediafire.com/k2ahkbsh07sg/wk6p32jj5hg2px9/twrp_2.6.3.3_loki-ls980.img
Cronic2009 said:
flash twrp to it, while in fast boot using ADB
http://download1983.mediafire.com/k2ahkbsh07sg/wk6p32jj5hg2px9/twrp_2.6.3.3_loki-ls980.img
Click to expand...
Click to collapse
Instructions please?
When I flash twrp, should I flash a nonstock rom, or stock? Can you direct me to stock downloads.
open command prompt in ADB and execute
fastboot flash twrpls980.img
*make sure you put the downloaded image in the adb folder or you will have to include the path to where the file is located.
I was on a stock ROM when I flashed it, here you can find some stock files. http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Cronic2009 said:
open command prompt in ADB and execute
fastboot flash twrpls980.img
*make sure you put the downloaded image in the adb folder or you will have to include the path to where the file is located.
I was on a stock ROM when I flashed it, here you can find some stock files. http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Click to expand...
Click to collapse
Can I get a link to download ADB for Windows 8? Is that all I need to type? What if I'm using a different recovery image?
What is the sprint stick rom from that download link?
sorry misread your previous post, those .zips are flashable through TWRP, here is a LS980 ZVA ROM, both odexed/deodexed, http://forum.xda-developers.com/showthread.php?t=2630748
you can flash a custom ROM if you would like, look at the thread in my signature it has tons of custom ROMs and kernels
Cronic2009 said:
sorry misread your previous post, those .zips are flashable through TWRP, here is a LS980 ZVA ROM, both odexed/deodexed, http://forum.xda-developers.com/showthread.php?t=2630748
you can flash a custom ROM if you would like, look at the thread in my signature it has tons of custom ROMs and kernels
Click to expand...
Click to collapse
ADB download?
Download this > http://download1983.mediafire.com/k2...loki-ls980.img
put it in your ADB folder and rename it to recovery.img ( just easier to find it )
plug the phone in
open Command Prompt in ADB folder ( hold shift + windows button in ADB folder )
fastboot flash recovery.img ( if you are using a different recovery image, sub it here, fastboot flash blank.img)
this should give you TWRP recovery, you can the use the .zips to update ROMs
CroI ic2009;518ADB12 said:
Download this > http://download1983.mediafire.com/k2...loki-ls980.img
put it in your ADB folder and rename it to recovery.img ( just easier to find it )
plug the phone in
open Command Prompt in ADB folder ( hold shift + windows button in ADB folder )
fastboot flash recovery.img ( if you are using a different recovery image, sub it here, fastboot flash blank.img)
this should give you TWRP recovery, you can the use the .zips to update ROMs
Click to expand...
Click to collapse
Where do i download adb?
ADB download here http://forum.xda-developers.com/showthread.php?t=2588979
Cronic2009 said:
ADB download here http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
One last question. How do I put ROMs onto the phone in recovery mode?I don't have any rom files for the phone at all yet. Can I flash with ADB?
eddytheyeti2 said:
One last question. How do I put ROMs onto the phone in recovery mode?I don't have any rom files for the phone at all yet. Can I flash with ADB?
Click to expand...
Click to collapse
All these things can be done through ADB yes. Didn't you have to download ADB to root in the first place? You shouldnt have to download again. However if you want to check start up a command prompt and type adb devices. That should pop up something if you have adb installed. I'm not sure if you need to be in a parent folder first though.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Demonlinx said:
All these things can be done through ADB yes. Didn't you have to download ADB to root in the first place? You shouldnt have to download again. However if you want to check start up a command prompt and type adb devices. That should pop up something if you have adb installed. I'm not sure if you need to be in a parent folder first though.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I used ioroot, so no ADB. I'm also not by my laptop at all. Would the rom install command be flash fastboot **********. Zip?
eddytheyeti2 said:
I used ioroot, so no ADB. I'm also not by my laptop at all. Would the rom install comand be flash fastboot **********. Zip?
Click to expand...
Click to collapse
Not if you don't have ADB installed.
Demonlinx said:
Not if you don't have ADB installed.
Click to expand...
Click to collapse
I'm going to download ADB today.
Cronic2009 said:
ADB download here http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
So, I have ADB installed. I am on windows 8 though, and the shift+windows button are not opening the prompt. Furthermore when I plug my phone in the computer says "windows cannot find 'C:\ Program Files (X86)\Mobogenie\Mobogenie.exe'. Make sure you typed the name correctly, and then try again" I have no clue what Mobogenie is!
Advice? if there is any for me?
Edit: I can get the ADB window open, but when I type the command "fastboot flash twrp_2.6.3.3_loki-ls980"
I get the following:
unknown partition 'twrp_2.6.3.3_loki-ls980'
error: cannot determine image filename for 'twrp_2.6.3.3_loki-ls980'
I am not sure what to do... Is the Mobogenie the issue? I have all of the proper drivers installed. though I don't see my device in computer on the laptop. Help please? I don't think I can take the device into sprint or lg, because it was rooted.

[Root] Zenfone 2 Official Android 6.0 Root + Xposed and Downgrade

**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca. If you like his work, please make him a small donation for encouragement.
2. This is a systemless root. Yet you need to unlook Lollipop before upgrading to Marshmallow.
3. Flashing the attached SuperSU file modifies stock boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** to unroot before upgrading to official Android 6.0.
Root:
1. Unlock your device in Lollipop, then upgrade to Android 6.0
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. This TWRP is recommended.
HTML:
adb reboot-bootloader
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp. /OR install the SuperSU in twrp if you saved it in device storage.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Unroot:
Just flash back stock boot.img
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: Download Xposed Installer here
Downgrade to Lollipop:
In case you need to downgrade to Lollipop, follow the instructions with care. Do it at your risk.
Refer to Asus Zentalk Forum and grab the required files from there.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot reboot-bootloader
Now you are back in Lollipop. You can flash back stock recovery(.184 recommended), wipe the device(cache/userdata/system) and then sideload back stock LP or MM as you wish. OR, you can flash custom recovery/boot/system.img start from here.
Good luck!
It worked!Thank you master!I bow now....
I just need root on 6.0.1. Is this going to achieve that?
MikeyLee said:
I just need root on 6.0.1. Is this going to achieve that?
Click to expand...
Click to collapse
According to op it will
Sent from my ASUS_Z00AD using Tapatalk
It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.
pokey006 said:
It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.
Click to expand...
Click to collapse
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?
samcjtsai said:
1. All credits go to @shakalaca and I just try to recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum but, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Works like a charm !! Thanks !!
kamyk70 said:
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?
Click to expand...
Click to collapse
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
when update to 6.0. bootloader unlocked again ! how can i flash twrp ?
pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
No it does not
Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thank You for explaining that to me, appreciated!
To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.
euthic said:
To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.
Click to expand...
Click to collapse
You need to adb sideload all LP .184 images first then use Asus FlashTool to flash RAW Firmware.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
root works perfect along with systemless xposed, but i still cant pass safenet check..(super su disabled, and also xposed) so no AP.. is that normal ?
pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well
ponhei9502 said:
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well
Click to expand...
Click to collapse
Guess your ZF2 is not unlocked in LP first, so that you can't see twrp booting. Since you are in Android 6.0 now, try to downgrade to LP, Unlock it, upgrade to 6.0 and then root.
samcjtsai said:
**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca and I just recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Where are these files again? They aren't in the zip
thanks, works great, was able to downgrade to lollipop with no problem what so ever. Install twrp, gain root again, and rockin custom roms...

[A2017U - B29] "Fastboot Flashing Unlock" returns "Unknown Command" in ADB

[A2017U - B29] "Fastboot Flashing Unlock" returns "Unknown Command" in ADB
Hi !
Quick info: I am not a novice when it comes to rooting / unlocking bootloader / installing TWRP or CWM / installing Xposed Frameworks, etc
I will make this short and sweet.
My Info :
- Axon 7 Gold - A2107U (US variant) with Update B29 installed (A2017UV1.0.0B29)
- Minimal ADB and Fastboot
- Windows 7 x64 Home premium
Here are the steps I have done:
1-
I installed the ADB drivers and Qualcomm WWAN drivers on my computer.
2-
Under Developers settings, I have enabled "OEM Unlocking".
3-
Using Axon7backup.exe, I created 2 backup files: "stock_recovery_backup.img" and "stock_boot_backup.img"
4-
Rebooted in bootloader using "adb reboot bootloader", (my device was listed). I first tried "fastboot oem unlock" then tried "fastboot flashing unlock", both returning "Unknown Command".
HERE IS WHERE I AM CONFUSED:
Normally, anyone would Unlock to bootloader THEN install TWRP, but from what I've seen with Axon7, some people say that Installing TWRP is "required" to unlock the bootloader.
I've seen some say that they have successfully rooted / unlocked bootloader with the B29 update, but I don't see any zip files or threads for the B29.
Could anyone enlighten me on the steps that I (and many others) have to do in order to Unlock the Bootloader and be able to install TWRP and Xposed Framework (and root).
Thank you !
Could anyone enlighten me on the steps that I (and many others) have to do in order to Unlock the Bootloader and be able to install TWRP and Xposed Framework (and root).
Thank you ![/QUOTE]
Ok so the long story short is that the bootloader is not unlockable out of the box. When ZTE released the bootloader unlock, they released a separate ota for it called B20_boot from B20 which modified the fastboot image. It didn't make sense for a lot of people for ZTE to release a separate OTA since it would not allow them to recieve future otas (such as B29) so they are working on a new bootloader unlock. So since you are on B29 and the bootloader is not unlockable out of the box and you cannot update to B20_boot since you are not on B20 this is what you do:
1) I am assuming you already have the tool downloaded since you used it to create the backup files so just follow the same instructions to boot into edl mode, then open a command window where the tool is located. Then execute:
Code:
axon7backup.exe
to start the tool and then
Code:
axon7root.exe -p # -r
where # is your COM Port # in Device Manager. The tool will flash the signed version of TWRP with ZTE's signature from the leaked firehose onto your Axon 7.
2)Hold down volume up and power to exit download mode and boot into recovery which should now be TWRP.
3) Download the bootloader unlock zip from @DrakenFX: https://www.androidfilehost.com/?fid=529152257862665656. Flashing the zip will replace your fastboot image with the one from B20_boot.
4) After you have flashed the zip, reboot to bootloader and just execute
Code:
fastboot oem unlock
and you are good to go!
^^The stock fastboot does not support the unlocking command. There's another fastboot image in the bootloader unlock thread that gets flashed first. *THEN* you can issue the unlock command.
I've been messing with android at least since late 2009 and have seen many variants of unlocking processes. This one is new for me too.
bkores said:
Ok so the long story short is that the bootloader is not unlockable out of the box. When ZTE released the bootloader unlock, they released a separate ota for it called B20_boot from B20 which modified the fastboot image. It didn't make sense for a lot of people for ZTE to release a separate OTA since it would not allow them to recieve future otas (such as B29) so they are working on a new bootloader unlock. So since you are on B29 and the bootloader is not unlockable out of the box and you cannot update to B20_boot since you are not on B20 this is what you do:
1) Go to this thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204. Download @tenfar's tool for A2017U B20(axon7root.exe not axon7backup.exe). There is no tool for B27 or B29 because the OP is no longer active but it will still work(I have tested.)
Click to expand...
Click to collapse
I see that the release a "axon7root-us-b27.zip" here: http://d-h.st/kRgq
"Uploaded By: tenfar
Uploaded On: 2016-09-19 23:10:07"
Should I use the B27 or follow the B20 method ?
EDIT: Should I do following command ?: reboot disemmcwp (to remove protect write, or it's no longer necessary? )
Boutchoo said:
I see that the release a "axon7root-us-b27.zip" here: http://d-h.st/kRgq
"Uploaded By: tenfar
Uploaded On: 2016-09-19 23:10:07"
Should I use the B27 or follow the B20 method ?
Click to expand...
Click to collapse
I edited my original answer. Since you already have axon7backup.exe you don't have to download the tool. And yes you should do "reboot disemmcwp" if you want to be able to make changes to /system
bkores said:
I edited my original answer. Since you already have axon7backup.exe you don't have to download the tool.
Click to expand...
Click to collapse
Nice ! TWRP is now installed !
I was wondering, if I backup my DATA only using TWRP and restore them after doing "fastboot oem unlock", will I be able to get my apps back without breaking my system ?
EDIT: After doing "Fastboot oem unlock", TWRP gives me "Mount: Decrypt Data: Enter Password:"...
EDIT2: Ok now Android is locked... it's asking me to enter a password *NEVER MIND- FORMATED CELL, NOW WORKS*
Edit3: Do I need to flash SuperSU or is it pre-packaged ?
Boutchoo said:
Nice ! TWRP is now installed !
I was wondering, if I backup my DATA only using TWRP and restore them after doing "fastboot oem unlock", will I be able to get my apps back without breaking my system ?
EDIT: After doing "Fastboot oem unlock", TWRP gives me "Mount: Decrypt Data: Enter Password:"...
EDIT2: Ok now Android is locked... it's asking me to enter a password
Click to expand...
Click to collapse
Did you just flash TWRP using -r or flashed the boot image as well using -b? Because if you just flashed TWRP the data decryption thing should not have happened. For some reason ZTE screwed up encryption to the point where if you backup data in TWRP with a pin/password/pattern enabled and then restore from it you will get a data decryption prompt where no password would work, not even your own. If you get this you have no choice but to wipe your data and then do either a Google restore during setup or use Titanium Backup(after you flash SuperSU) if you have it. In the future if you want to backup your data and until ZTE fixes it, you have to disable your pin/password/pattern first.
bkores said:
Did you just flash TWRP using -r or flashed the boot image as well using -b? Because if you just flashed TWRP the data decryption thing should not have happened.
Click to expand...
Click to collapse
I copy pasted your line "axon7root.exe -p 8 -r" only, did nothing else.
Also, do I need to flash SuperSU for the root or is it pre-packaged ?
Boutchoo said:
I copy pasted your line "axon7root.exe -p 8 -r" only, did nothing else.
Also, do I need to flash SuperSU for the root or is it pre-packaged ?
Click to expand...
Click to collapse
Flash SuperSU
bkores said:
Flash SuperSU
Click to expand...
Click to collapse
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Boutchoo said:
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Click to expand...
Click to collapse
You need SuperSU v2.65 as any other version will crash TWRP(no one knows why)
bkores said:
You need SuperSU v2.65 as any other version will crash TWRP(no one knows why)
Click to expand...
Click to collapse
Ah, I see. It's weird !
Also, what does flashing the boot (-b) does with the Axon 7 ? It's weird that only recovery (-r) is necessary.
Boutchoo said:
Ah, I see. It's weird !
Also, what does flashing the boot (-b) does with the Axon 7 ? It's weird that only recovery (-r) is necessary.
Click to expand...
Click to collapse
The modified boot image allows people without an unlocked bootloader to have root however if your bootloader is unlocked you should not do it as you will have the data decryption issue.
Boutchoo said:
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Click to expand...
Click to collapse
Try 2.65

Help Post

Is it possible to install stock image without unlocking the bootloader. I somehow bricked my phone. Usb debugging disabled Oem unlock disabled bootloader locked. In this condition any solution to install stock image?
iamshovonmandal said:
Is it possible to install stock image without unlocking the bootloader. I somehow bricked my phone. Usb debugging disabled Oem unlock disabled bootloader locked. In this condition any solution to install stock image?
Click to expand...
Click to collapse
You might be able to sideload an update.zip from PC, if you can find the update.zip
Code:
adb sideload update.zip
Some Sideload instructions
How to Sideload Android 8.0 Oreo on the Essential Phone - KrispiTech
Essential Phone just received its second Oreo beta update and you can follow these steps to manually sideload to it from Android 7.1.1 Nougat.
krispitech.com
Still looking for the update.zip...
OTA files
essential-static - Browse /ota at SourceForge.net
sourceforge.net
sd_shadow said:
You might be able to sideload an update.zip from PC, if you can find the update.zip
Code:
adb sideload update.zip
Click to expand...
Click to collapse
Thanks gonna try this
iamshovonmandal said:
Thanks gonna try this
Click to expand...
Click to collapse
You should check getvar all to see which firmware is on the device.
Code:
fastboot getvar all
You don't want to install an older update.

11C33 [KB2005] stock boot.

I followed the guide to extract out the C20 boot for KB2005 (international/US)
C20 Stock https://www.androidfilehost.com/?fid=15664248565197183443
MD5 86ed6298490ef8447830e6bdd146f61a
KB2005 C21 https://www.androidfilehost.com/?fid=15664248565197185204
MD5 eedb50fd8b4fe1402fecd1716621d1a3
KB2005 C33 https://www.androidfilehost.com/?fid=15664248565197205355
MD5 72d839a4a6498f7cb8665f9548b21f17
You can patch with your Magisk
How are you extracted this boot.img from your phone? Please tell me.
zeman124 said:
How are you extracted this boot.img from your phone? Please tell me.
Click to expand...
Click to collapse
The sticky has the method
However, the phone must be rooted (su command is used)
zeman124 said:
How are you extracted this boot.img from your phone? Please tell me.
Click to expand...
Click to collapse
You could use the MSM Tool (yes, I'm not kidding!). See section A.1.1 in https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
mingkee said:
The sticky has the method
However, the phone must be rooted (su command is used)
Click to expand...
Click to collapse
Yes it's rooted
zeman124 said:
Yes it's rooted
Click to expand...
Click to collapse
Don't use the MSM Tool - that will give you a copy of your Magisk-patched boot image.
Since your phone is rooted, then you can get a copy of the stock boot from the backup Magisk creates in /data/magisk_backup_<hash value>
Or you could uninstall Magisk>Restore images in Magisk (do NOT reboot!), pull a copy of the boot image using dd, then restore root using Magisk>install>direct install
BillGoss said:
Don't use the MSM Tool - that will give you a copy of your Magisk-patched boot image.
Since your phone is rooted, then you can get a copy of the stock boot from the backup Magisk creates in /data/magisk_backup_<hash value>
Or you could uninstall Magisk>Restore images in Magisk (do NOT reboot!), pull a copy of the boot image using dd, then restore root using Magisk>install>direct install
Click to expand...
Click to collapse
Sorry, what is dd?
zeman124 said:
Sorry, what is dd?
Click to expand...
Click to collapse
It's a Unix command used to read from/write to partitions. You run it as root in a terminal session or in adb shell.
It would look like this:
Code:
su
dd if=/dev/block/by-name/boot<active slot suffix> of=/sdcard/stock-boot.img
where <active slot suffix> is the output of getprop ro.boot.slot_suffix
C21 boot added
mingkee said:
C21 boot added
Click to expand...
Click to collapse
Thanks for posting these. I just went through the upgrade and accidentally pulled and patched the active slot boot image (which I assume was C20). Having this available helped get me out of a little bind.
this is lovely, thank you!
mingkee said:
I followed the guide to extract out the C20 boot for KB2005 (international/US)
C20 Stock https://www.androidfilehost.com/?fid=15664248565197183443
MD5 86ed6298490ef8447830e6bdd146f61a
KB2005 C21 https://www.androidfilehost.com/?fid=15664248565197185204
MD5 eedb50fd8b4fe1402fecd1716621d1a3
You can patch with your Magisk
Click to expand...
Click to collapse
how i install it?
my bootloader is unlock
now I download the KB2005 c21 img file
i tried with adb and didnt work
i tried to download magisk apk and install it directly dont work :/
Grigiac said:
how i install it?
my bootloader is unlock
now I download the KB2005 c21 img file
i tried with adb and didnt work
i tried to download magisk apk and install it directly dont work :/
Click to expand...
Click to collapse
Install in fastbootd
Code:
adb reboot fastboot
Code:
fastboot flash boot
Press space once and drag-and-drop the boot into command window and press enter
mingkee said:
Install in fastbootd
Code:
adb reboot fastboot
Code:
fastboot flash boot
Press space once and drag-and-drop the boot into command window and press enter
Click to expand...
Click to collapse
i did it, and then reboot my devices
what next?
i open magisk and still dont see my phone has been rooted
--
i have oem unlock but dont have root (magisk)
i want to install magisk so i download magisk apk from internet but I need to install it somehow and its not work
There's a full guide how to flash patched boot
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
mingkee said:
There's a full guide how to flash patched boot
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
Click to expand...
Click to collapse
but i dont need to extract the file right?
I download it from here..
I have KB2005_11_c.21 version
and then I run it with adb but nothing change
Grigiac said:
but i dont need to extract the file right?
I download it from here..
I have KB2005_11_c.21 version
and then I run it with adb but nothing change
Click to expand...
Click to collapse
Patch it with Magisk first, copy back to your PC, and flash the patched_boot in fastbootd.
mingkee said:
Patch it with Magisk first, copy back to your PC, and flash the patched_boot in fastbootd.
Click to expand...
Click to collapse
Thanks! Its work
That all what I need
C.33 added

Categories

Resources