Thanks to @peramikic and @rczrider for fulfilling the request. I will post the compressed unmodified system.img if no one (@Unjustified Dev) beats me to it.
Just a note that I was successful in making my A2017U a stock B20. I first relocked my bootloader, then flashed the 4 images from TWRP. I was then able to reapply B20_boot update.
Keeping the request procedure below for archival purposes:
Code:
Hoping someone is still stock running B20 and willing/able to help. You'll need a micro-SD formatted exFAT with at least 8GB, and working ADB.
Following [URL="http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204"]tenfar's method[/URL], please backup both your stock boot and recovery using axon7backup.
Using axon7root, only apply the recovery included in tenfar's package (-r).
Reboot into recovery (volume up and power button). [U]KEEP READ ONLY! Do not slide the slider to make modifications![/U] Make sure under mount button that Micro SDCard is mounted.
On your PC, use the following commands:
[CODE]
adb shell
cd external_sd/
dd if=/dev/block/sde13 of=system.img
This will take a while as it copies ~6GB to your SD card (at least 10 minutes). When it's done, you should be returned to the prompt.
Using tenfar's method again, restore your recovery backup only. (-r)
Compress that file and upload it somewhere.[/CODE]
jkuczera said:
Hoping someone is still stock running B20 and willing/able to help. You'll need a micro-SD formatted exFAT with at least 8GB, and working ADB.
Following tenfar's method, please backup both your stock boot and recovery using axon7backup.
Using axon7root, only apply the recovery included in tenfar's package (-r).
Reboot into recovery (volume up and power button). KEEP READ ONLY! Do not slide the slider to make modifications! Make sure under mount button that Micro SDCard is mounted.
On your PC, use the following commands:
Code:
adb shell
cd external_sd/
dd if=/dev/block/sde13 of=system.img
This will take a while as it copies ~6GB to your SD card (at least 10 minutes). When it's done, you should be returned to the prompt.
Using tenfar's method again, restore your recovery backup only. (-r)
Compress that file and upload it somewhere.
Click to expand...
Click to collapse
@Unjustified Dev is getting his Axon 7 probably Monday and I told him to give us a hand about pulling system_image from untouched b20 , but if someone else can do it before him that will rock too.
DrakenFX said:
@Unjustified Dev is getting his Axon 7 probably Monday and I told him to give us a hand about pulling system_image from untouched b20 , but if someone else can do it before him that will rock too.
Click to expand...
Click to collapse
That's great to hear. Hopefully it's still B20 My attempt to go back to B20 stock failed on the system image. I really don't want to miss out on the next update!
Would be great if the next one was a full image!
jkuczera said:
That's great to hear. Hopefully it's still B20 My attempt to go back to B20 stock failed on the system image. I really don't want to miss out on the next update!
Would be great if the next one was a full image!
Click to expand...
Click to collapse
After all the jumbo-monbo we have giving them about factory images I bet there's be one for us waiting hehehe well hope so lol,
Probably UDev A7 still on B20 and he can give is a hand on this matte or Anyone else who want to help with this request will be great..
EDIT : @jkuczera
Out of my curiosity, i downloaded the Stock B20 backup from Here which you already have + a2017u b20 (inside there is a boot.img) and what i just did was,
- Move / Copy the System B20 Stock to my TWRP backup directory
- Move / Copy the Boot.img to SDCard (which was inside of the a2017u b20 zip file)
- Boot to TWRP
- Wipe Cache - Dalvik - Data - System ( twice as usual , well for me it is )
- Tap Restore > Select to B20 Stock Folder > Restore System
- Tap Install > Tap Install Image > go to where B20 Stock Boot.img is located > Flash Boot image
- Reboot (here is where i was crossing all my finger hehehe)
- Waited for about 10 min. or so and Booted
NOTE : i don't know if this Stock B20 backup is Untouch / UnModified as you request but , restoring the b20 stock backup + boot.img (Wiping all the above / mention partitions) work for me, WIFI - DATA working by the way and TWRP still bootable either by adb or manually
DrakenFX said:
NOTE : i don't know if this Stock B20 backup is Untouch / UnModified as you request but , restoring the b20 stock backup + boot.img (Wiping all the above / mention partitions) work for me, WIFI - DATA working by the way and TWRP still bootable either by adb or manually
Click to expand...
Click to collapse
Try doing a B20_Boot update; it should fail on verifying system. Otherwise you found the golden ticket.
DrakenFX said:
After all the jumbo-monbo we have giving them about factory images I bet there's be one for us waiting hehehe well hope so lol,
Probably UDev A7 still on B20 and he can give is a hand on this matte or Anyone else who want to help with this request will be great..
EDIT : @jkuczera
Out of my curiosity, i downloaded the Stock B20 backup from Here which you already have + a2017u b20 (inside there is a boot.img) and what i just did was,
- Move / Copy the System B20 Stock to my TWRP backup directory
- Move / Copy the Boot.img to SDCard (which was inside of the a2017u b20 zip file)
- Boot to TWRP
- Wipe Cache - Dalvik - Data - System ( twice as usual , well for me it is )
- Tap Restore > Select to B20 Stock Folder > Restore System
- Tap Install > Tap Install Image > go to where B20 Stock Boot.img is located > Flash Boot image
- Reboot (here is where i was crossing all my finger hehehe)
- Waited for about 10 min. or so and Booted
NOTE : i don't know if this Stock B20 backup is Untouch / UnModified as you request but , restoring the b20 stock backup + boot.img (Wiping all the above / mention partitions) work for me, WIFI - DATA working by the way and TWRP still bootable either by adb or manually
Click to expand...
Click to collapse
Like jkuczera said, the B20_Boot will fail since your system is not hash consistent (and recovery partition in not stock) and so will MR2 OTA . While all the right files are there, they are not in the right order (think file layout on the partition). TWRP can supposedly do a system image backups and if you take it with /system read-only when you run TWRP (i did), it is supposed to be a hash consistent. Restoring it where it get's iffy i guess. You are supposed to mount /system read-only and restore system image so TWRP will not modify it when you are done, but someone said did not restore (could be user error). It is also fastboot flashable but i think the fastboot images we have are limited in payload file size, someone i think tried and got the max payload error. I'll zip mine up and see if i can upload it somewhere once i get home. The image will have stock boot and system and TWRP rec, so all that would be needed is to flash stock rec to get correct sigs.
jkuczera said:
Try doing a B20_Boot update; it should fail on verifying system. Otherwise you found the golden ticket.
Click to expand...
Click to collapse
peramikic said:
Like jkuczera said, the B20_Boot will fail since your system is not hash consistent (and recovery partition in not stock) and so will MR2 OTA . While all the right files are there, they are not in the right order (think file layout on the partition). TWRP can supposedly do a system image backups and if you take it with /system read-only when you run TWRP (i did), it is supposed to be a hash consistent. Restoring it where it get's iffy i guess. You are supposed to mount /system read-only and restore system image so TWRP will not modify it when you are done, but someone said did not restore (could be user error). It is also fastboot flashable but i think the fastboot images we have are limited in payload file size, someone i think tried and got the max payload error. I'll zip mine up and see if i can upload it somewhere once i get home. The image will have stock boot and system and TWRP rec, so all that would be needed is to flash stock rec to get correct sigs.
Click to expand...
Click to collapse
what actually fails when i try to apply the zip using Stock Recovery is when check for boot, which System been the first partition to check and pass, boot.img i'm using is the one from tenfar for the whole reason of booting, but what i didn't Test was using a Full stock Boot.img even if i don't boot but to see if pass,
omw to try that report back,
DrakenFX said:
what actually fails when i try to apply the zip using Stock Recovery is when check for boot, which System been the first partition to check and pass, boot.img i'm using is the one from tenfar for the whole reason of booting, but what i didn't Test was using a Full stock Boot.img even if i don't boot but to see if pass,
omw to try that report back,
Click to expand...
Click to collapse
The first check you pass is the fingerprint, which is fine since you have restored stock system. The comes the sha1 check for boot, recover and system. You failed the hash check on the boot partition. Was the boot.img root mod one? that's not going to work.
What's the best way to pull it.... I got mine today. I haven't touched anything.
Sent from my ZTE A2017U using Tapatalk
shoman94 said:
What's the best way to pull it.... I got mine today. I haven't touched anything.
Click to expand...
Click to collapse
Check the OP. I can give you a place to upload to if you need it.
shoman94 said:
What's the best way to pull it.... I got mine today. I haven't touched anything.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Just like JK said in first post, dump your boot and recovery with tenfars tool, then flash modded TWRP only. Make sure you stay in read only in TWRP on the first prompt
I would the do full TWRP backup including system image. then use the dd command above to dump /system part by itself.
Put it all on SD Card. Then flash back the stock recovery with tenfar's tool. You will have the stock backup of main partitions and phone ready for the MR2 OTA.
The main quirk of course is that the current BL unlock zip will most likely not work after MR2 OTAs until someone requests one. So trick is to see if the MR2 can be flashed with BL unlocked but going back to B20 boot, system and recovery
jkuczera said:
Check the OP. I can give you a place to upload to if you need it.
Click to expand...
Click to collapse
Yea, kinda ballsy.... I'll think about it. I can't afford to mess something up at the moment. Lol
Sent from my ZTE A2017U using Tapatalk
peramikic said:
The first check you pass is the fingerprint, which is fine since you have restored stock system. The comes the sha1 check for boot, recover and system. You failed the hash check on the boot partition. Was the boot.img root mod one? that's not going to work.
Click to expand...
Click to collapse
@jkuczera
yeah i take all that back, fails after 40% system fault , was turning things around getting apply from sdcard using stock recovery to work but well we need that system_img unmodified then ...
@jkuczera @DrakenFX check your PM
peramikic said:
@jkuczera @DrakenFX check your PM
Click to expand...
Click to collapse
check your PM
DrakenFX said:
check your PM
Click to expand...
Click to collapse
Done, also check this link on how it should be used
https://github.com/Lrs121/android_resources/wiki/Take-OTA-on-Block-Devices
peramikic said:
Done, also check this link on how it should be used
https://github.com/Lrs121/android_resources/wiki/Take-OTA-on-Block-Devices
Click to expand...
Click to collapse
got it thanks man,
DrakenFX said:
@Unjustified Dev is getting his Axon 7 probably Monday and I told him to give us a hand about pulling system_image from untouched b20 , but if someone else can do it before him that will rock too.
Click to expand...
Click to collapse
I have the system.img 6.4GB I did modified my system file a bit by installing busybox...
Is it ok for you?
If yes I will upload it through MEGA
manu7irl said:
I have the system.img 6.4GB I did modified my system file a bit by installing busybox...
Is it ok for you?
If yes I will upload it through MEGA
Click to expand...
Click to collapse
Needs to be 100% unmodified to pass signature checks. Thanks though!
I@jkuczera I can get back to stock with the untouched twrp backup, then save it for you.
I just restored my system patition from the B20 untouched twrp backup.
But still, I first restored the default recovery then made a factory rest. Then I flashed twrp again also made a format data, then backed up my current system and restored the system backup form the untouched B20.
but still after reboot twrp is asking for a password... I'm on twrp 3.0.2-2.
If I do:
Code:
do if=/dev/zero of=/dev/block/bootdevice/by-name/userdata bs=1m
This will be completely wipe the data partition...
Am I right? @DrakenFX
Could it help with this F***ing encryption??
Related
Update:
I was able to use this method to root the new ICS update. The thread has been edited accordingly.
----------------------------------------------
I was unable to find a single thread that detailed how to root the stock T-Mobile Springboard firmware and keep the boot and recovery partitions intact to allow future updates, so I have consolidated information from other threads and posts, as well as adding a little myself. Full credit goes to the users and thread OP's referenced in the post links below.
The usual warnings apply: Under no circumstances should anyone do this to their device. You are likely to brick your device and render it completey unusable. In addition, you will void your warantee with T-Mobile. So you will have an out-of-warantee brick instead of a nice, functional tablet. Turn back now while there is still time.
Before you begin, I obviously did this to my device without any problems. My device is running full stock T-Mobile Springboard firmware with the following:
Android version: 4.0.3
Baseband version: 314007
Kernel version: 3.0.8
Build number: S7-303uV100R002C201B035
I do not know if it will work on a device with any other version of the firmware. The following also assumes that you have fastboot and ADB installed and functional on your computer.
In describing how to boot into fastboot and recovery modes below, the description of the volume buttons is how they are while in portrait mode in Honeycomb....as this is where I first used this method. In other words, the volume button closer to the power button is volume up and the other volume button is volume down.
1. Download the CWM Recovery image from this post:
http://forum.xda-developers.com/showpost.php?p=23601045&postcount=7
2. Download CWM-SuperSU-v0.95.zip from this post:
http://forum.xda-developers.com/showpost.php?p=27678611&postcount=22
3. Copy the CWM-SuperSU-v0.95.zip file to an sdcard and put the card in your device.
4. Flash the CWM recovery image to your first recovery partition ONLY:
a.) Boot into fastboot by powering down the device and starting it back up by pressing the
volume up and power buttons at the same time. After the device vibrates, release the
power button but keep holding the volume button until it is booted into fastboot.
b.) Once in fastboot, flash the recovery image:
Code:
fastboot flash recovery recovery5.5.0.4.img
5. Press and hold the power key for 10 seconds to reboot the device. It will boot into the
T-mobile firmware.
6. Power down the device in the usual fashion.
7. Boot into recovery by starting the device back up by pressing the volume down and power
buttons at the same time. After the device vibrates, release the power button but keep
holding the volume button until it is booted into CWM Recovery.
8. Choose 'install zip from sdcard' -> 'choose zip from sdcard', then select the
CWM-SuperSU-v0.95.zip file you put on your sdcard above, then confirm installation.
9. Go back to the main menu and select 'reboot system now'. It will boot into the T-Mobile
firmware.
10. Shut the device down again in the usual fashion, then restart normally and boot into the
T-Mobile firmware again.
11. Now you need to get your stock recovery partition back and get rid of CWM recovery.
There are two copies of the stock recovery- one on each 'recovery' and 'recovery2'. You can
get back to stock recovery by extracting an image from 'recovery2' and flashing it back to
'recovery'. The following (using adb from your computer) will dump the image from recovery2
to your sdcard:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/mnt/sdcard2/recovery.img
12. Take the sd card out of your device and copy this file back to your computer, then flash the
first recovery partition with this image as in step 4b above, but with your new recovery.img file.
You are now rooted and your recovery partitions are returned to stock.
Once you are rooted, if you would like to remove some of the T-Mobile bloatware note that the apk files are not in the usual location (/system/app). I found them tucked away in the following directory:
/data/cust/app
Of course, you will need an app like Root Explorer to get to them and delete them...or you can just use adb. I deleted several of the apk files in that directory, rebooted, and everything is working just fine...with less bloatware.
Also, be aware that any changes you make will be permanent. I tried hard reseting the device through the usual android settings menu security method, and I kept root and all of my deleted bloatware was still gone after it finished and rebooted. There does not appear to be a way to get all of your stock stuff back once you start deleting things...so make backups of files before you delete them in case removing them causes unexpected consequences.
Just to add another bit of information - a list of what I believe are the internal partitions and their locations appears below. I got this from the output from 'cat /proc/partitions' and 'mount', as well as further inspection of the stock recovery image that I extracted from my device. As we don't have a functional CWM Recovery, and I am not sure that I would use any version that was built for the Mediapad (i.e. non-Springboard) for backup and restoring, this list should give Springboard users a way to back up their devices. Using the 'dd' command as in the coding box at the bottom of the OP for each of the paritions should result in a partition image stored out on the sdcard. Fastboot then should be able to flash these 'backed up' images back to the device as in step 4b of the OP...with the correct partition names and backup files substituted of course. I did do this for the recovery partition as I detailed in the OP, but have not tried it for the rest of the partitions.
Code:
/misc emmc /dev/block/mmcblk0p14
/vrcb emmc /dev/block/mmcblk0p16
/recovery emmc /dev/block/mmcblk0p17
/recovery2 emmc /dev/block/mmcblk0p18
/boot emmc /dev/block/mmcblk0p19
/system ext4 /dev/block/mmcblk0p20
/cache ext4 /dev/block/mmcblk0p22
/cust ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p27
/tmpdata ext4 /dev/block/mmcblk0p23
/persist ext4 /dev/block/mmcblk0p21
/tombstones ext4 /dev/block/mmcblk0p24
/firmware ext4 /dev/block/mmcblk0p1
Thanks
Many ty's for this.
Thanks you help me rooted my Springboard. Have you try the MediaPad Phone app can we use the tablet for calling? :good:
Do I have to do step 11 ?
Sent from my SpringBoard using XDA Premium App
---------- Post added at 06:11 PM ---------- Previous post was at 05:49 PM ----------
robkaos said:
Do I have to do step 11 ?
Sent from my SpringBoard using XDA Premium App
Click to expand...
Click to collapse
Also can I do it without PC?
Sent from my SpringBoard using XDA Premium App
Can I use the recovery image from the update that is still on my sd card,what is the difference between the I've springboard .rar, and the su files
Sent from my SpringBoard using XDA Premium App
robkaos said:
Do I have to do step 11 ?
......
Also can I do it without PC?
Click to expand...
Click to collapse
If you do not return your recovery partition to stock, then you will not be able to install future firmware updates from T-Mobile as their updates rely on the stock recovery. So no, you don't have to return your recovery partition to stock, but if you don't you will not be able to install future T-Mobile updates. As far as doing this without a computer - you can use a terminal emulator on your Springboard to create the recovery image from 'recovery2'....the commands should be the same. However, you need to fastboot flash that image back to 'recovery', which you must do from your computer with your device in fastboot mode.
robkaos said:
Can I use the recovery image from the update that is still on my sd card....
Click to expand...
Click to collapse
Yes, if you extract the recovery image from the official T-Mobile update package, you can use this image to flash 'recovery' back to stock when you are done.
Some people have reported that they are unable to boot into CWM recovery if it is flashed only to 'recovery' and not also to 'recovery2'. It is my experience that the device seems to alternate which recovery partition it boots into when you sequentially boot it into recovery mode. When I have CWM on 'recovery' and the stock recovery on 'recovery2', my device will boot into CWM every other time I boot into recovery mode. The other times it boots into the stock recovery. If you can't get CWM recovery to appear when you boot into recovery mode, you could do things a bit different than the instructions. Extract the stock recovery image from the official T-Mobile update package. Store this away on your computer. Then, instead of only flashing 'recovery' with CWM recovery, also flash 'recovery2'. Once you are done rooting the device, use your stored image of the stock recovery to flash 'recovery' and 'recovery2' back to stock.
Originally, I used this method to root Honeycomb. I did not have the T-Mobile update package for Honeycomb and so could not simply extract the stock recovery image from that package. You cannot use the 'dd' command as in step 11 above until you are rooted to dump the image of 'recovery2'. So, without a copy of the update package I could not get an image of my recovery partition without already being rooted. But to root, I have to overwrite my recovery partition with CWM recovery, thereby making it impossible to dump a copy of the stock recovery as I had wiped it out and replaced it with CWM. The solution was to only flash one of the recovery partitions and keep the other one as a backup until the device was rooted and the image could then be extracted.
robkaos said:
...what is the difference between the I've springboard .rar, and the su files
Click to expand...
Click to collapse
Not sure what you are asking here...please clarify.
I haVe found two different root files one su zip and the other is for media pad orange Tahiti ,andspringbord .rar which is the difference?there is not a one click Method like motor defy? My phone wasn't such a problem
Sent from my SpringBoard using XDA Premium App
robkaos said:
I haVe found two different root files one su zip and the other is for media pad orange Tahiti ,andspringbord .rar which is the difference?
Click to expand...
Click to collapse
I don't know about the root files for the Mediapad. I know there is a package that contains the su files and a Windows-based command file that contains a string of adb commands that is supposed to work to root both the Mediapad and the Springboard. I think what you are talking about can be found at either one of these locations:
http://www.modaco.com/topic/354579-...-mediapad-t-mobile-springboard-orange-tahiti/
http://www.gamefront.com/files/22185176/Huawei+MediaPad+ROOT+ICS+Android+4.0.x.rar
I tried to use this, and got a 'premission denied' fail pretty early on. I run Linux on my desktop, so perhaps this works under Windows with the specific Springboard drivers and interface software installed, but it sure does not work in Linux. I came up with my method (or rather consolidated the information for 'my' method from multiple other sources) as a result of having this root method fail for me.
robkaos said:
...there is not a one click Method like motor defy? My phone wasn't such a problem
Click to expand...
Click to collapse
If the files that I linked above work for you, then this is going to be about as close to a 'one-click' method as you can get. Unless you modified it, your Motorola Defy is running Android 2.1 (Eclair). This version of Android can be rooted pretty much just by yelling 'ROOT!' at your phone. There is even an app in the market that can be installed and run on an Android v2.1 device that provides a one-click root without the use of a computer. All of the exploits that were used for these one-click root methods were patched in Android v3+. Pretty much every device needs its own unique root method now, and the only way it is a one-click method is if someone has constructed a command script to execute all of the needed commands for you, as in the linked packages above.
xdajunkman said:
Also, be aware that any changes you make will be permanent. I tried hard reseting the device through the usual android settings menu security method, and I kept root and all of my deleted bloatware was still gone after it finished and rebooted. There does not appear to be a way to get all of your stock stuff back once you start deleting things...so make backups of files before you delete them in case removing them causes unexpected consequences.
Click to expand...
Click to collapse
Just to point out - now that the Springboard ICS update is out, and the zip has been captured and archived - there is a backup of complete stock ICS available. Every single partition is in there including system and cust. So worst case scenario if you bork it by zapping the wrong file in system or cust, you can reflash that partition from the bootloader.
Thanks for the clarification
Sent from my SpringBoard using XDA Premium App
cmstlist said:
Just to point out - now that the Springboard ICS update is out, and the zip has been captured and archived - there is a backup of complete stock ICS available. Every single partition is in there including system and cust. So worst case scenario if you bork it by zapping the wrong file in system or cust, you can reflash that partition from the bootloader.
Click to expand...
Click to collapse
You are, of course, correct. That statement of mine is now outdated...you can delete things to your hearts desire. If you mess something up, just reflash the firmware and start over.
Just finished rooting my MediaPad from t-mobile. I had to install into recovery one and two so now I have no original recovery but I don't really care, I've got the latest Android Ice Cream update beforehand. What usefull apps with root access do I need now? I've got ad free and ROM Toolbox. Was there a phone app that I could use now?
Failed updates and can't recover - PLEASE HELP!
xdajunkman said:
You are, of course, correct. That statement of mine is now outdated...you can delete things to your hearts desire. If you mess something up, just reflash the firmware and start over.
Click to expand...
Click to collapse
Well, unfortunately, I've messed things up. Here's what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
Any and all help would be immensely appreciated! How can I get back to some sort of working ROM? Please!
Thanks!
knightpawn said:
Well, unfortunately, I've messed things up. Here's what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
Any and all help would be immensely appreciated! How can I get back to some sort of working ROM? Please!
Thanks!
Click to expand...
Click to collapse
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Any particular locations for the other files via fastboot?
cmstlist said:
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Click to expand...
Click to collapse
Wow! Thanks for the help! I unfortunately, don't have my other computer that has the proper drivers installed to recognize the tablet and to run fastboot on. So, I'll try the fix you are suggesting once I get home today. However, in the meantime, I had some questions with regard to where I should flash the other files.
I understand that recovery.img should go to the recovery and recovery2 partitions.
What about the others? Does boot.img go to a particular partition? Effectively, what would the command line look like? (eg fastboot flash boot boot.img?)
Sorry about the newbie questions. I've installed a number of custom ROMs on phones using CWM, but this is a strange beast.
With regard to your question of whether it boots, well, kind of...it does boot to the T-mobile Springboard screen, then it sits there. I will let it sit for 20-30 minutes and see what happens. Will report back...for sure!
Thanks a ton!
[UPDATE]
So, I had a chance to install the TWRP recovery with the CM10 ROM. I loaded the CM10 ROM with the TWRP which installed successfully. I turned the tablet on and let it sit there for about 10 minutes and sure enough, CM10 runs just fine. However, I did notice that I cannot receive any calls. I am able to make calls, but when someone dials my number, it just goes straight to voicemail.
So, now, I'm wondering, if I can get the stock ICS with International ROM running so that I can try to use this thing as a phone, data and texting tab. I'll try what you suggested when I get home as mentioned earlier.
CM10 has too many problems, why would you want to use it?
cmstlist said:
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Click to expand...
Click to collapse
That worked for me. After playing with vold.fstab I had rendered my Springboard unusable (got the encryption was unsuccessful screen!).
I really wanted to switch the apps installation path to the external sd card but did not succeed.
What am I doing wrong
I have not been able to root my springboard at all. It will go to a black screen that says enter fastboot and it just stays there. When I type to flash the recovery it says it cannot load it. I have adb and fastboot installed...could it be a driver issue? I now know that I am in the correct screen, just can't get this thing rooted. any help would be appreciated thanks.
Well I feel quite stupid. But figured out where I went wrong and for the love of God got my Springboard rooted. *whew*
This is a TWRP backup of the stock firmware for V510 GPE GPAD 8.3. They have already been updated. It is completely stock no mods, no root, no busybox. This should ensure that you are able to take future OTAs without issue. Many GPE users have been having problems with the OTAs. The reason is that the OTA does a system verification and any type of modification causes it to fail.
How to flash this:
1. Reboot into bootloader
2. Flash TWRP if you don't already have it. Current version is 2.8.1.0 fastboot flash recovery xxxxxxxxxxxxx.img (where xxxxx is the filename)
3. Reboot System
4. Copy the entire contents of the zip file to your TWRP/BACKUPS/LG0000XXXXXXXX folder. Make sure you copy the folder 2014-11-30--23-35-25 LRX21P.L004 or 2014-06-26--18-41-18 KTU84P.L002. If you don't have a backups folder, create one in TWRP by choosing Backup, then backup something like the boot partition.
5. Reboot to Recovery Vol Dwn+Pwr or adb reboot recovery.
6. Choose Restore and select 2014-11-30--23-35-25 LRX21P.L004 or 2014-06-26--18-41-18 KTU84P.L002
7. Once finished Reboot System.
8. Upon boot you should be greeted with the usual Setup screens.
9. Reboot into bootloader
10. (Optional for Kit Kat) Flash stock recovery: fastboot flash recovery 17-recovery.img
11. Reboot into system
.
Flashing the stock recovery is optional however if you want a completely stock experience and ensure future OTAs, you probably want to do so. Also note that you must unroot to take any future OTAs.
To reroot flash latest version of TWRP.
Download Links:
LMY47O.L008 with Stock Recovery
TWRP Backup 5.1 LMY47O.L005 with Stock Recovery
TWRP Backup 5.1 LMY47O Thanks @rocket321 for providing the image.
TWRP BACKUP 5.0 LRX21P.L004
TWRP BACKUP 4.4.4 KTU84P.L002
KK Stock Recovery
You did an excellent job on this thread. Thanks for doing this for our small community.
BTW: regarding recovery for our device, the latest (and in fact only) that I see is TWRP 2.7.0.1 in the Original Android Development section.
Agreed. I wasn't able to flash 4.4.4 any other way. Tried everything, kept getting errors. This finally worked!
cam30era said:
You did an excellent job on this thread. Thanks for doing this for our small community.
BTW: regarding recovery for our device, the latest (and in fact only) that I see is TWRP 2.7.0.1 in the Original Android Development section.
Click to expand...
Click to collapse
Figured it will come in handy to have this online for everyone in the future...when I bought the device when it was announced thought there would be more dev on it...but that hasn't been the case. Luckily we at least have twrp.
No partitions selected for restore.
djkinetic said:
This is a TWRP backup of the stock firmware for V510 GPE GPAD 8.3. It has already been updated to 4.4.4. It is completely stock no mods, no root, no busybox. This should ensure that you are able to take future OTAs without issue. Many GPE users have been having problems with the OTA for 4.4.4 The reason is that the OTA does a system verification and any type of modification causes it to fail.
How to flash this:
1. Reboot into bootloader
2. Flash TWRP if you don't already have it. Current version is 2.7.0.1 fastboot flash recovery xxxxxxxxxxxxx.img (where xxxxx is the filename)
3. Reboot System
4. Copy the entire contents of the zip file to your TWRP/BACKUPS/LG0000XXXXXXXX folder. Make sure you copy the folder 2014-06-26--18-41-18 KTU84P.L002. If you don't have a backups folder, create one in TWRP by choosing Backup, then backup something like the boot partition.
5. Reboot to Recovery Vol Dwn+Pwr or adb reboot recovery.
6. Choose Restore and select 2014-06-26--18-41-18 KTU84P.L002
7. Once finished Reboot System.
8. Upon boot you should be greeted with the usual Setup screens.
9. Reboot into bootloader
10. (Optional) Flash stock recovery: fastboot flash recovery 17-recovery.img
11. Reboot into system
.
Flashing the stock recovery is optional however if you want a completely stock experience and ensure future OTAs, you probably want to do so. Also note that you must unroot to take any future OTAs.
Download Links:
TWRP BACKUP 4.4.4 KTU84P.L002
Stock Recovery
Click to expand...
Click to collapse
When I flash this in twrp it fails to flash and i get an error message: No partitions selected for restore. Have twrp 2.7.0.1 installed. Thank you.
Do I unzip the folder before I move it to the backup folder?
1barlog17 said:
Do I unzip the folder before I move it to the backup folder?
Click to expand...
Click to collapse
Delete
Figured out what was going on. finally got it to flash in TWRP. Works great. Thank you for this.
Thanks for this image - was the only way I was able to update.
Sent from my LG-V510 using Tapatalk
I was not able to update using your image and I don't know why. Everything was done correctly as far as I know. I downloaded and unpacked the zip and placed it in the back apps folder of TWRP and rebooted into recovery and tried restore with no success during the system restore it stops halfway through and says failed.
I tried downloading the file twice, installing the file from my computer, changing my SD card, deleting everything and trying, deleting just dalvik cache a,updating the partition separately, and was able to update the boot partition but not system and data. I honestly don't know what the trouble is as I was able to restore my own back up several times.if anybody has any insight into what is happening here please tell me. I would really like to install the update! I don't know why it is not allowing me to.
sleekmason said:
I was not able to update using your image and I don't know why. Everything was done correctly as far as I know. I downloaded and unpacked the zip and placed it in the back apps folder of TWRP and rebooted into recovery and tried restore with no success during the system restore it stops halfway through and says failed.
I tried downloading the file twice, installing the file from my computer, changing my SD card, deleting everything and trying, deleting just dalvik cache a,updating the partition separately, and was able to update the boot partition but not system and data. I honestly don't know what the trouble is as I was able to restore my own back up several times.if anybody has any insight into what is happening here please tell me. I would really like to install the update! I don't know why it is not allowing me to.
Click to expand...
Click to collapse
First off, I use solid explorer, dual pane. Very easy to navigate for me.
I only copied system. I didn't even wipe. All my data and settings were intact. As close to an OTA I could get. The system backup was 790.95mb
It sounds like you did everything right to me. I included a screen shot of what it looked like after i clicked the backup.zip and moved the unzipped backup to the TWRP backup folder.
Sent from my LG-V510 using XDA Premium 4 mobile app
sleekmason said:
I was not able to update using your image and I don't know why. Everything was done correctly as far as I know. I downloaded and unpacked the zip and placed it in the back apps folder of TWRP and rebooted into recovery and tried restore with no success during the system restore it stops halfway through and says failed.
I tried downloading the file twice, installing the file from my computer, changing my SD card, deleting everything and trying, deleting just dalvik cache a,updating the partition separately, and was able to update the boot partition but not system and data. I honestly don't know what the trouble is as I was able to restore my own back up several times.if anybody has any insight into what is happening here please tell me. I would really like to install the update! I don't know why it is not allowing me to.
Click to expand...
Click to collapse
im not sure if this would work
did u try restoring from the internal sd instead of external. as far as I know the backup file should have no issues.
djkinetic said:
im not sure if this would work
did u try restoring from the internal sd instead of external. as far as I know the backup file should have no issues.
Click to expand...
Click to collapse
That was it!! Thank you!
Do I need to uninstall Xposed Framework, unroot, restore the stock kernel, etc., before restoring this system back up TWRP? I assume the answer is no, though I'll need to reinstall those afterward, but I figured I'd check first!
UPDATE: Never mind. I just went ahead and restored it successfully and am in the process of restoring my apps from TiBu now. Thanks again for providing this for those of us who couldn't upgrade to 4.4.4 any other way!
Hey guys,
first off thank you for posting this tutorial, I was able to perform the backup0 and am currently on 4.4.4.
I did, however, run into a slight hiccup when I was trying to flash the stock recovery. I kept getting messages about partitions and so forth. I entered in the following commands from beginning to end:
adb devices
adb reboot bootloader
fastboot flash recovery 17-recovery.img
but as I said I can't get the job done lol.
Any ideas?
ephayzee said:
Hey guys,
first off thank you for posting this tutorial, I was able to perform the backup0 and am currently on 4.4.4.
I did, however, run into a slight hiccup when I was trying to flash the stock recovery. I kept getting messages about partitions and so forth. I entered in the following commands from beginning to end:
adb devices
adb reboot bootloader
fastboot flash recovery 17-recovery.img
but as I said I can't get the job done lol.
Any ideas?
Click to expand...
Click to collapse
A few things to check:
you need to have usb debugging checked on phone
you need the recovery image in same folder as your fastboot.exe/adb files
you need to cd to that directory/folder
TWRP source
Hi,
Can you please tell me where to find TWRP 2.7.x for the V510. I currently have 2.6.3.0, I believe?
Thanks
techinv said:
Hi,
Can you please tell me where to find TWRP 2.7.x for the V510. I currently have 2.6.3.0, I believe?
Thanks
Click to expand...
Click to collapse
It worked fine for me with TWRP 2.6
techinv said:
Hi,
Can you please tell me where to find TWRP 2.7.x for the V510. I currently have 2.6.3.0, I believe?
Thanks
Click to expand...
Click to collapse
Here > http://forum.xda-developers.com/showthread.php?t=2682606
However, download link in OP is currently broken. I PMed the OP about it.
Has anyone gotten the error "E: No partitions selected for restore." when trying to flash the recovery?
Hoping to use this thread to help members who are having bootloops/wifi/etc. issues after flashing different kernels/system images.
If wi-fi is not working (A2017U B20):
bkores said:
Boot into TWRP, then connect your phone to your computer making sure adb is working then execute:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384
This should be your output:
/dev/block/platform/soc/624000.ufshc/by-name # dd if=/dev/zero of=/dev/block/boo
tdevice/by-name/modemst1 bs=16384
dd: writing '/dev/block/bootdevice/by-name/modemst1': No space left on device
129+0 records in
128+0 records out
2097152 bytes (2.0MB) copied, 0.001917 seconds, 1.0GB/s
/dev/block/platform/soc/624000.ufshc/by-name # dd if=/dev/zero of=/dev/block/boo
tdevice/by-name/modemst2 bs=16384
dd: writing '/dev/block/bootdevice/by-name/modemst2': No space left on device
129+0 records in
128+0 records out
2097152 bytes (2.0MB) copied, 0.001829 seconds, 1.1GB/s
/dev/block/platform/soc/624000.ufshc/by-name #
Click to expand...
Click to collapse
You also need the crossed out boot.img from Here
If you're using an SD card, reboot your phone to TWRP. Make sure external SD is mounted in TWRP. On your PC, in the folder where your downloaded and extracted the boot.img, type:
Code:
adb push boot.img /external_sd/b20b_boot.img
adb shell if=/dev/block/sde12 of=/external_sd/boot_backup.img
adb shell if=/external_sd/b20b_boot.img of=/dev/block/sde12
adb reboot
Please post the steps you took to end up with bootloops/wifi issues, what exact issues you are having (wifi/bluetooth/cell/boot logo) as well as which recovery (stock/twrp) you currently have installed.
You and me both my friend, I created a thread like a week ago to gather info about what you are saying here, but seems like they don't want to participate for a fix.
http://forum.xda-developers.com/axon-7/help/post-current-boot-issues-read-posting-t3447987
DrakenFX said:
You and me both my friend, I created a thread like a week ago to gather info about what you are saying here, but seems like they don't want to participate for a fix.
http://forum.xda-developers.com/axon-7/help/post-current-boot-issues-read-posting-t3447987
Click to expand...
Click to collapse
Well, we got two sub-forums covered now. Let's see if anyone bites.
Well I did Draken's B20_Boot TWRP Backup Xposed+Root Edition Provided by DrakenFX , which cause a no boot situation, with no access to recovery. used tenfar's root without bootloader unlock to flash boot and recovery, then Draken's software image booted but no wifi. Still haven't fixed that one yet.
@thjoca3 do you know what system.img file you used? Is it a b20_boot system.img?
jkuczera said:
@thjoca3 do you know what system.img file you used? Is it a b20_boot system.img?
Click to expand...
Click to collapse
That I'm not sure, it's whatever system is packaged with Draken's backup
@thjoca3 here are my current boot and system files. They are both b20_boot.
https://drive.google.com/folderview?id=0Bx04wovXfQGeYlpqSHhvS3Noc28
Exactly what this thread says to do...http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
I downloaded the TWRP backup from that thread, and then downloaded Tenfar's tool from his own thread. I used his thread(Tenfar's) for the acquiring of the tool, as well as downloading a2017U B20 (since B20_boot unlocked is crossed out?). I then flashed the boot and recovery .img(using Tenfar's tool), then restored to the TWRP backup in TWRP provided by rcriderz. Afterwords, my phone booted up, but did not have Wifi access. That seems to bethe only feature missing... At this point I think I'd just rather wait for the first cyanogenmod release, but this is how I got to this point. I did this in the first place because I bricked my device by using GravityBox and rebooting so the settings would kick in. Device info: US Variant, unlocked bootloader via ZTE request form, TWRP installed
jkuczera said:
@thjoca3 here are my current boot and system files. They are both b20_boot.
https://drive.google.com/folderview?id=0Bx04wovXfQGeYlpqSHhvS3Noc28
Click to expand...
Click to collapse
maybe not totally sure how to use this, but I can't seem to get anything bigger than 5gb or so to load on to my sd card, or extract anything that size onto the sd card.
jkuczera said:
@thjoca3 here are my current boot and system files. They are both b20_boot.
https://drive.google.com/folderview?id=0Bx04wovXfQGeYlpqSHhvS3Noc28
Click to expand...
Click to collapse
I know this is not my thread but having it little more info in the following form will help a lot lIssue
- Model :
- Previuos Version :
- Current Version :
- Issue / Problem :
- How happen :
That will help a lot figure things out.
DrakenFX said:
I know this is not my thread but having it little more info in the following form will help a lot lssue
- Model : A2017u
- Previous Version : locked bootloader, twrp, stock rom, was never able to get full root, and always had password needed in twrp, b20_boot
- Current Version : same other than using your system, from the B20_Boot TWRP Backup Xposed+Root Edition (still no root) had to flash boot and recovery from tenfar to get it to boot.
- Issue / Problem : no wifi, cannot copy anything over 5gb to sdcards... cant get back to stock
- How happen : flashed B20_Boot TWRP Backup Xposed+Root Edition via twrp, never lost wifi, till I flashed this.
That will help a lot figure things out.
Click to expand...
Click to collapse
zz
thjoca3 said:
maybe not totally sure how to use this, but I can't seem to get anything bigger than 5gb or so to load on to my sd card, or extract anything that size onto the sd card.
Click to expand...
Click to collapse
The problem is likely the format of your SD card. It needs to be in a format that accepts files > 4GB. I believe exFAT or ext4 should work.
http://kb.sandisk.com/app/answers/d...rger-file-to-a-usb-flash-drive-or-memory-card
Well found an sdcard reader and was able to get files to the sdcard. Restored with warofhero's system image, and my stock boot and recovery, no change with wifi. Also loaded the b20_boot with stock recovery and no wifi.
thjoca3 said:
Well found an sdcard reader and was able to get files to the sdcard. Restored with warofhero's system image, and my stock boot and recovery, no change with wifi. Also loaded the b20_boot with stock recovery and no wifi.
Click to expand...
Click to collapse
Recovery should have zero effect on the outcome of Wi-Fi functioning during normal boot. I believe the issue with wi-fi is a mismatch of boot.img and system.img.
Do you know if warofhero's system image a b20 or a b20_boot?
jkuczera said:
Recovery should have zero effect on the outcome of Wi-Fi functioning during normal boot. I believe the issue with wi-fi is a mismatch of boot.img and system.img.
Do you know if warofhero's system image a b20 or a b20_boot?
Click to expand...
Click to collapse
I tried both on his, neither worked for me. Then I did this
Download rczrider's TWRP System backup, restored in twrp with the boot from tenfar's post - a2017u B20 http://d-h.st/LqR5 (modified from @rczrider‘s backup real stock b20 boot.img) and my wifi is back.
thjoca3 said:
I tried both on his, neither worked for me. Then I did this
Download rczrider's TWRP System backup, restored in twrp with the boot from tenfar's post - a2017u B20 http://d-h.st/LqR5 (modified from @rczrider‘s backup real stock b20 boot.img) and my wifi is back.
Click to expand...
Click to collapse
That's awesome, glad you got it fix.
So you have a full operational device now? Hope this solution help others.
DrakenFX said:
That's awesome, glad you got it fix.
So you have a full operational device now? Hope this solution help others.
Click to expand...
Click to collapse
Yes, appears everything is working now, with the modified boot.
I posted this somewhere else as well but here it goes again.
The booti.img and system have to match and be from the same set. So if you use stock B20 (not _Boot) boot.img then you have to use the same /system. In this case this would be
For locked bootloader use rcrider's boot(no root) + system or tenfar's boot(root) + rcrider's /system
For unlocked bootloader you would use B20_Boot boot+system like one jkuczera posted upthread
Do not mix and match files form different region's either, these are both from US A2017U model.
When bootlooping, there are multiple reasons why this could be:
- wrong modle boot.img
- unrotted boot.img and modded recovery or system while BL is locked
- /system flashed with unsuported SU or Xposed
- boot.img flashed with unsupported kernel/ramdisk patch
- junk in cache/dalvik
- junk in /data
- /data encrypted with key which cannot be decrypted due to altered cryptochain
The way to fix it most of the time is to flash proper boot and system and wipe all user partitions. tenfar's tools can restore boot and recoveries very painlessly. TWRP can take care of the /system and wipes. The only unknown at this point is if the system image can be flashed in TWRP in a OTA consistent state on the B20 version. This should be doable by running TWRP in read only mode but i do not know if that will still let you restore system. It also has to be "System Image" backup (6GB one) from TWRP and not just the /system partition for block consistency. Hope this helps sort out the problems. I might try all this out once i am certain I'll keep the phone, it is currently in trial mode for few more weeks. The full "System Image" for B20_boot was posted here http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53 , (edit: jkuczera's is also System Image and same size). maybe rcrider can put up one for B20 Stock on his MEGA
peramikic said:
The only unknown at this point is if the system image can be flashed in TWRP in a OTA consistent state on the B20 version. This should be doable by running TWRP in read only mode but i do not know if that will still let you restore system. It also has to be "System Image" backup (6GB one) from TWRP and not just the /system partition for block consistency.
Click to expand...
Click to collapse
Thanks for clarifying @peramikic.
For the quote above, I don't understand what you mean by OTA consistent state. Do you mean a state in which OTA would still occur even after bootloader unlock?
jkuczera said:
Thanks for clarifying @peramikic.
For the quote above, I don't understand what you mean by OTA consistent state. Do you mean a state in which OTA would still occur even after bootloader unlock?
Click to expand...
Click to collapse
This probably goes more for the B20 folks, since i doubt we will see an OTA from ZTE that will work on B2-_Boot. But in essence the System Image backups are supposed to produce bit level mirror image of the /system partition so that OTA update will properly hash it. Chances are very high that when you restore regular ext4 backups, while the files are the same they will not be laid out on the partition the same way. That's why /system is strictly read-only now. Even just enabling that RW access in TWRP can alter it. For instance the image you and swehes have posted differs slightly in first 4MB of the files (his has some stuff while your is all 0s) and then again in offset 69bd000 or so where one file is missing from your's i think it's the recovery-from-boot file. It is likely TWRP removed it so it would not get flashed over after reboot with stock recovery, if you allowed RW access to system.
TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
You're the man! Props for all the hard work you've put into this.
TY!!!!
Awesome. I might have to wait a bit to install but glad to see the Pixel getting twrp.
Sent from my Pixel XL using Tapatalk
Wow, and so it begins. Thanks!
Thank you!!
Nice!!! Awesome job @Dees_Troy
Sent from my Pixel XL using Tapatalk
I just installed the IMG w/out issue.
I can't find the zip in TWRP file manager to flash though.
Everything looks encrypted.
EDIT: It went through on the 4th try of flashing the IMG, now I can see my /sdcard and install the zip.
But somehow this killed my OS.
Just flashed the flash-all.bat after removing -w so it doesn't wipe.
Now I'll try TWRP install again.
EDIT 2: Okay, after restoring to stock, the TWRP install went fine.
Maybe it didn't like my elementalx kernel or the existing root. The OP did mention something about root conflicts, I guess it may prevent TWRP installs too? But now I have OS *and* TWRP.
And I'm getting "Unspecified Error" when trying to copy my EFS backup from /sdcard/twrp/backup to my local computer. I am able to copy other non-TWRP files though.
.
.
.
Does a full backup on Pixel include System Image and Vendor Image? I don't recall seeing these on other devices.
Or do I just back up boot, system and data like usual?
***Hey ya'll, don't forget to back up EFS at least once and copy it to your computers!
Yea! Worked perfect!!!
Would the flashable SuperSU v2.78 SR3 zip work?
Looked it up and because of conflicting init binaries between TWRP and the current root method, it just wouldn't work.
While we're still on or near the first page of the thread, I'd like to clarify the whole EFS backup thing.
It's completely unnecessary. You don't need to do it. But the option is there (so no one asks where it went!)
Both the modemst1 and modemst2 partitions are merely a caching area for your modem firmware. They do not contain sensitive data like IMEI, or anything important. You can wipe them and they will be regenerated from scratch! Have no fear, your IMEI cannot be destroyed through means of bad flashes!
The issue with these partitions however is that should they ever become corrupt, the modem firmware will panic and fail to load - this is why you see your IMEI missing in such a case. The modem firmware simply refused to load due to encountering corrupt data. By clearing your modemst partitions (writing zeros to them), your modem firmware would happily load and regenerate the partitions, bringing back full call support & a visible IMEI.
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Yep just want to let ya guys know might want return to stock before doing this. Besides that all good. Good job TWRP team! :good:
CZ Eddie said:
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Click to expand...
Click to collapse
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
FYI on OP - A SuperSU update will be required to allow TWRP and SuperSU to co-exist.
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
delete
CZ Eddie said:
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
Click to expand...
Click to collapse
Do we still flash root the same way after we install TWRP? Or is there an su zip to flash?
Hooray! Cheers!
Man every phone I get, I brick!! Im stuck in a BLU boot loop. Can't find any files out there for this model. Well did see one here
http://clangsm.com/ftpdemo/index.php?dir=Flashes/BLU/Studio%20XL%202/
They want $$ for the download :crying:
Anyone a member there that could get me this file?
Thanks for the help
Try this
Hey
https://www.ineedrom.tk/2017/04/09/blu-studio-xl-2-s0270uu-rom-stock-firmware/
I'm working on twrp. I haven't tried flashing it
edit: I've bricked and re-flashed. It's a good image
what version is this?
dougunder said:
Hey
https://www.ineedrom.tk/2017/04/09/blu-studio-xl-2-s0270uu-rom-stock-firmware/
I'm working on twrp. I haven't tried flashing it
edit: I've bricked and re-flashed. It's a good image
Click to expand...
Click to collapse
is this firmware v08? it rendered my phone inoperable. no cell, no camera and several other issues. the phone came installed with v09
Anyone ever find V09??
I am also in need of BLU_S0270UU_V09_GENERIC firmware for a Studio XL2 , 6.0. Anybody have a source for this???
Thanks ahead!
crmcc said:
I am also in need of BLU_S0270UU_V09_GENERIC firmware for a Studio XL2 , 6.0. Anybody have a source for this???
Thanks ahead!
Click to expand...
Click to collapse
I have a phone arriving tmw. First thing I will be doing is pulling the stock images. So if it has v09 I will link it for you.
I uploaded stock system and boot images to Androd File Host. If you still need them let me know.
mrmazak said:
I have a phone arriving tmw. First thing I will be doing is pulling the stock images. So if it has v09 I will link it for you.
I uploaded stock system and boot images to Androd File Host. If you still need them let me know.
Click to expand...
Click to collapse
Could you send me the links to the stock image? I recently rooted this phone using superSU and now I can't install Magisk due to the fact that superSU modified the boot image
killer13666 said:
Could you send me the links to the stock image? I recently rooted this phone using superSU and now I can't install Magisk due to the fact that superSU modified the boot image
Click to expand...
Click to collapse
here is link to my folder for the studio_XL_2
the stock images are in the zip labled
Blu-Studio_XL-2-__BLU_S0270UU_V09_GENERIC-01-03-2017.zip
the modifoed boot.img file will give root adb shell with ability to set selinux to permissive and then mount /system as rw all without needing superSU or magic installed.
The port zips are current w.i.p. of Cm/LM13 for the studio
mrmazak said:
here is link to my folder for the studio_XL_2
the stock images are in the zip labled
Blu-Studio_XL-2-__BLU_S0270UU_V09_GENERIC-01-03-2017.zip
the modifoed boot.img file will give root adb shell with ability to set selinux to permissive and then mount /system as rw all without needing superSU or magic installed.
The port zips are current w.i.p. of Cm/LM13 for the studio
Click to expand...
Click to collapse
Okay, I downloaded the files, but I'm not quite sure how to flash the images onto my phone.... Please forgive my ignorance as I've never had to do this before
killer13666 said:
Okay, I downloaded the files, but I'm not quite sure how to flash the images onto my phone.... Please forgive my ignorance as I've never had to do this before
Click to expand...
Click to collapse
I assume you already know how to get into twrp, because you were previously attempting to flash magic., So no need to cover that.
Put the boot.img to your phone (same way you put the superSu or magic zips)
To flash the boot.img, select install button in twrp. At lower corner or screen in twrp will appear button "Install Image", select that.
then browse folders same as usual but now will show you the img files available .
select the stock boot.img
next screen is "select Partiton to Flash Image"
select Boot, then "swipe"
this will return you to stock boot.img, as long as you were on V9 before.
You should also be able to flash the system.img the same way, if neede, but I have no way to know If is ok to use as upgrade from V8
must have images unzipped from main archive before putting to phone.
mrmazak said:
I assume you already know how to get into twrp, because you were previously attempting to flash magic., So no need to cover that.
Put the boot.img to your phone (same way you put the superSu or magic zips)
To flash the boot.img, select install button in twrp. At lower corner or screen in twrp will appear button "Install Image", select that.
then browse folders same as usual but now will show you the img files available .
select the stock boot.img
next screen is "select Partiton to Flash Image"
select Boot, then "swipe"
this will return you to stock boot.img, as long as you were on V9 before.
You should also be able to flash the system.img the same way, if neede, but I have no way to know If is ok to use as upgrade from V8
must have images unzipped from main archive before putting to phone.
Click to expand...
Click to collapse
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
---------- Post added at 11:16 AM ---------- Previous post was at 11:05 AM ----------
killer13666 said:
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
Click to expand...
Click to collapse
There isn't an option to flash it to system fyi, that's the only reason I am asking where I should flash it to.
killer13666 said:
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
---------- Post added at 11:16 AM ---------- Previous post was at 11:05 AM ----------
There isn't an option to flash it to system fyi, that's the only reason I am asking where I should flash it to.
Click to expand...
Click to collapse
No, don't put the system image anywhere except in system.
I will need to look at the twrp on the device again tonight.
I know the same recovery before being ported to the studio( on my life Max ) allows flashing system image. That's how I usually do my full reset.
On the studio I assumed it was same. Will update when I get back to PC. ( Tethered recovery is a pain ).
But do you actually need to reflash system though?
mrmazak said:
No, don't put the system image anywhere except in system.
I will need to look at the twrp on the device again tonight.
I know the same recovery before being ported to the studio( on my life Max ) allows flashing system image. That's how I usually do my full reset.
On the studio I assumed it was same. Will update when I get back to PC. ( Tethered recovery is a pain ).
But do you actually need to reflash system though?
Click to expand...
Click to collapse
In trying to get the google assistant to work on my phone, I tried flashing something and I think it messed up the build.prop file along with some other things. I forgot to take a backup before flashing the zip and now my phone doesn't boot. It just has a black screen.
************************EDIT************************
/system won't mount either..............
killer13666 said:
In trying to get the google assistant to work on my phone, I tried flashing something and I think it messed up the build.prop file along with some other things. I forgot to take a backup before flashing the zip and now my phone doesn't boot. It just has a black screen.
************************EDIT************************
/system won't mount either..............
Click to expand...
Click to collapse
system not mounting may be a bigger problem.
I ported different TWRP that has the flash system image option.
same as old one you must use "fastboot boot" to get into it, do not flash it to phone.
https://forum.xda-developers.com/devdb/project/dl/?id=27144
mrmazak said:
system not mounting may be a bigger problem.
I ported different TWRP that has the flash system image option.
same as old one you must use "fastboot boot" to get into it, do not flash it to phone.
https://forum.xda-developers.com/devdb/project/dl/?id=27144
Click to expand...
Click to collapse
Okay, so I figured out why /system wasn't mounting. I accidentally set the rm -rf option instead of formatting the partitions, so I fixed the system partition not mounting. And this port of TWRP fixed my phone, so thank you so much for your help!
And as a side note, why exactly can I not flash TWRP onto the phone? What will happen if I do?
killer13666 said:
Okay, so I figured out why /system wasn't mounting. I accidentally set the rm -rf option instead of formatting the partitions, so I fixed the system partition not mounting. And this port of TWRP fixed my phone, so thank you so much for your help!
And as a side note, why exactly can I not flash TWRP onto the phone? What will happen if I do?
Click to expand...
Click to collapse
When the recovery is flashed inside, the touchscreen in recovery does not work. Making using recovery impossible, unless maybe a USB mouse would work
mrmazak said:
When the recovery is flashed inside, the touchscreen in recovery does not work. Making using recovery impossible, unless maybe a USB mouse would work
Click to expand...
Click to collapse
Is there like a port of CWM that I can flash to this? I remember an old phone of mine (I think it was a Samsung Fascinate), I had CWM on it and it didn't use the touchscreen at all, but rather it used the volume keys to move the selection and used the power button to actually select a menu item.
killer13666 said:
Is there like a port of CWM that I can flash to this? I remember an old phone of mine (I think it was a Samsung Fascinate), I had CWM on it and it didn't use the touchscreen at all, but rather it used the volume keys to move the selection and used the power button to actually select a menu item.
Click to expand...
Click to collapse
there is a "carliv" one . Its a CMW with touch also. But will work without.But it does not see the /data partiton on phone. so only good for install from micro sdcard
mrmazak said:
there is a "carliv" one . Its a CMW with touch also. But will work without.But it does not see the /data partiton on phone. so only good for install from micro sdcard
Click to expand...
Click to collapse
So in other words, it won't let you flash anything that'll modify the data partition as well?
killer13666 said:
So in other words, it won't let you flash anything that'll modify the data partition as well?
Click to expand...
Click to collapse
If all goes well, I may have a custom kernel in a few days that will enable the touchscreen
mrmazak said:
If all goes well, I may have a custom kernel in a few days that will enable the touchscreen
Click to expand...
Click to collapse
Please do let me know how that goes.