Develop Bugs

[Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ClockworkMod Recovery - Modified for Motorola Xoom​
OK, so this recovery will skip /data/media (Internal storage) when performing nandroid backups and also when you perform a factory reset.
This means that we can now perform nandroid backups without backing up our internal media and removing it everytime you want to do a backup.
Thanks to Bigrushdog and MadIndustries for helping out with the concept of the solution for skipping /data/media.
Also thanks to Koush and all the other developers that have contributed to clockworkmod, without you guys the android world would be completely different.
Thanks also to everyone in #xoom that tested this.
The source code for all changes etc are available through the github repository. The two other projects that have been modified to make this recovery possible can also be viewed through my github account.
Even though this recovery has been tested, I am not liable for any loss of data or any damages done by this recovery.
==============================================
General Notes
When I refer to /data/media, this is the same as /sdcard when the xoom is booted into honeycomb. So any data that is stored in here should be untouched by this recovery.
If you encounter a problem with the filesystem on /data like it has become corrupt, place a blank file called "eraseData" (without the quotes) in the clockworkmod folder on your external sdcard. This will revert to the old way of formatting /data. NOTE: by doing this you will lose everything that you have in /data/media.
Versioning of recovery images:
At the moment I don't have a version number as such, instead each recovery image is timestamped in the format of DDMMYY-HHYY. So the file recovery-solarnz-120511-2030.img was produced on 12 May 2011 at 8:30 PM. This versioning is also shown in recovery when it starts.
==============================================
Downloads
SLOW DOWN AND RELAX
Make sure you download the correct version depending on how you want to flash. I have seen at least two xooms bricked now because they have tried to flash the zip file through fastboot.
Recovery Zip (solarnz-R4c-100611-1150) FLASHED THROUGH CWM
MD5: 1ad409db4030635734b27df02b7e7c1a
Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT
MD5: 20575d4b62bf697f77abca9093877ea3
==============================================
Installation Instructions
Method 1 Flashing through CWM
Download the recovery zip file
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or any other method
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Sit back and relax while recovery flashes the new recovery and reboots into it.
Click to expand...
Click to collapse
Method 2 Without CWM
Download the recovery image (not the zip file)
Pull up your command prompt, then
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
fastboot reboot
Let your Xoom boot up. Then to check out your shiny new recovery,
Code:
adb reboot recovery
Click to expand...
Click to collapse
Also, you can grab Rom Manager or QuickBoot from the market for easy access to recovery.
==============================================
Changelog
Code:
[url=http://bit.ly/k7cZxJ]3.2.0.0 (R4c-100611-1150)[/url]
- Rebuilt recovery, the previous recovery was built off of bad device files.
[url=http://dl.dropbox.com/u/13093938/XDA/Recovery/recovery-solarnz-R4b-060611-1300-cwm.zip]3.2.0.0 (R4b-060611-1300)[/URL]
- Disabled partitioning the sdcard as per request.
[url=http://dl.dropbox.com/u/13093938/XDA/Recovery/recovery-solarnz-R4-050611-1515-cwm.zip]3.2.0.0 (R4-050611-1515)[/URL]
- Included changes from koush's sources upto clockworkmod 3.2.0.0
- Implemented Advanced backup. This allows you to choose what partitions you want to backup.
[url=http://dl.dropbox.com/u/13093938/recovery-solarnz-120511-2030.zip]3.0.2.8 (120511-2030)[/url]
- Fixed mounting the sdcard for some users
[url=http://dl.dropbox.com/u/13093938/recovery-solarnz-080511-1630.img] 3.0.2.8 (080511-1630)[/URL]:
- Modified to skip /data/media or /sdcard in nandroid backups.
- Modified formatting /data to remove directories and folders so we can keep media.
- Place a file called eraseData in the clockworkmod directory on your EXTERNAL sdcard to revert to the normal restoration method.

Great job guys!!!!
Sent from my HTC HD2 using XDA Premium App

You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.

Win
Sent From My Evo

Great job folks!!!
We've gotten used to BRD's awesome formatting of his posts and super clear instructions, would be real nice if we can get this on the new sticky

bigrushdog said:
You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.
Click to expand...
Click to collapse
might be a stupid question but just to clarify: we would obviously not want to flash any recoveries in rom manager thus not having any need for rom manager at at this point correct?

jland22 said:
might be a stupid question but just to clarify: we would obviously not want to flash any recoveries in rom manager thus not having any need for rom manager at at this point correct?
Click to expand...
Click to collapse
Rom manager is still nice as you can quickly reboot to recovery etc from it. It also allows you to select the operation to do in recovery and then restart it will automatically restart and perform the action.
If you flash recovery from Rom Manager, you will end up with the official 3.0.2.5 recovery from Koush that doesn't contain the method of skipping /data/media

bigrushdog said:
You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.
Click to expand...
Click to collapse
What's the difference between this and the one on bigrushdog thread. (3.1)
Sent from my Xoom using XDA Premium App

lokko21 said:
What's the difference between this and the one on bigrushdog thread. (3.1)
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
No difference, BRD used this modified 3.2.8 in his first step on that thread. But this will be the go-forward recovery from now on.

What folder do i need to flash this too?

b0ricua said:
No difference, BRD used this modified 3.2.8 in his first step on that thread. But this will be the go-forward recovery from now on.
Click to expand...
Click to collapse
Gotcha so I'm cool, thanks.

ok just flashed, looks good

Solarnz, thanks for formatting the OP and adding clear instructions!!
You da man!

very cool, but would it be complicated to just make an "exclude" menu before backing up? That way people can just exclude whatever they want ...

thanks to everyone who contributed. We dont always think about how great CWM is and all the wonderful things it does for us until we dont have it anymore I didnt like the feeling of walking around with that stock recovery

running into a problem. I have a wifi only xoom. I had the old 3.0.2.8 recovery installed which i still had after 3.1 update no problems with it at all. I just flashed the 3.0.2.8 one using fastboot but now when i reboot into recovery. All i see is the android with the exclamation mark i do not see clockwork. I have reflash more then once with no luck still.
Edit: wanted to add that if i flash the clockwork from Rom manger which i see is the version 3.0.2.5 i am able to do a adb reboot recovery into recovery with no problems.
Edit2: for some reason the zip flashing in the old recovery works fine and updated to the new recovery. no clue why fastboot is not working. I tried fastboot 5 times every flash said it finished fine but it boots with a android and a exclamation mark. only the zip flashing in recovery works for me.

maybe this is a stupid question, but i dont even see a "media" folder on my xoom. there are folders for music and video. i have my own folder for movies, one for comics, ect. do i have to create a media directory and move everything into it in order to make sure that it doesnt get included? and if so, where does it go?

Prod1702 said:
running into a problem. I have a wifi only xoom. I had the old 3.0.2.8 recovery installed which i still had after 3.1 update no problems with it at all. I just flashed the 3.0.2.8 one using fastboot but now when i reboot into recovery. All i see is the android with the exclamation mark i do not see clockwork. I have reflash more then once with no luck still.
Edit: wanted to add that if i flash the clockwork from Rom manger which i see is the version 3.0.2.5 i am able to do a adb reboot recovery into recovery with no problems.
Edit2: for some reason the zip flashing in the old recovery works fine and updated to the new recovery. no clue why fastboot is not working. I tried fastboot 5 times every flash said it finished fine but it boots with a android and a exclamation mark. only the zip flashing in recovery works for me.
Click to expand...
Click to collapse
Ok, I'm assuming you are on android 3.1 without a modified kernel.
The issue you are having is that with the default boot image, it flashes back the stock recovery every single time you reboot.
Code:
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
(Thanks Berzerker7)
ltracte said:
maybe this is a stupid question, but i dont even see a "media" folder on my xoom. there are folders for music and video. i have my own folder for movies, one for comics, ect. do i have to create a media directory and move everything into it in order to make sure that it doesnt get included? and if so, where does it go?
Click to expand...
Click to collapse
Ok. on our xooms, /sdcard is actually a symlink (think of a shortcut) to /data/media.
So when I say /data/media, you can think of /sdcard (the internal storage).

random one again - will this be available via ROM Manager? it's still 3.0.2.5 there
thanks!

E: can't mount /sdcard/update.zip
or error mounting /sdcard
anyone has encountered this problem plz?
thks

[Q] A100 won't mount emmc or SD Card

My a100, which was running Flex, froze up night before last and I powered down, thinking that would take care of it like it has before. Wrongo! Now all I can do is boot into recovery. Will not mount anything in the system. Any help to fix this would be greatly appreciated.

Try erasing CWM recovery (fastboot erase recovery), place the update.zip (of the official rom) on your external SD card (via card reader, etc.), then attempt to boot into recovery (it should flash the rom).

Theonew said:
Try erasing CWM recovery (fastboot erase recovery), place the update.zip (of the official rom) on your external SD card (via card reader, etc.), then attempt to boot into recovery (it should flash the rom).
Click to expand...
Click to collapse
That's the thing, I can't get it to mount anything including the external sd when I boot into recovery.

j.price said:
That's the thing, I can't get it to mount anything including the external sd when I boot into recovery.
Click to expand...
Click to collapse
CWM recovery will not be there to do that. Maybe the default will be able to.

Theonew said:
CWM recovery will not be there to do that. Maybe the default will be able to.
Click to expand...
Click to collapse
If you have adb pull the recovery log that will show any errors in the fileaystems. I woukd say dump it but if it cant mount external sd that wont work. You verified failed mounting in the mounts menu in recovery?
Tapatalked from my Galaxy S II.

That is correct. Will not mount anything other than the recovery partition.

j.price said:
That is correct. Will not mount anything other than the recovery partition.
Click to expand...
Click to collapse
And did you try adb? Try it from whatever pc you used to get cwm or twrp or whatever recovery on there. It's not really possible for it to only mount recovery or you wouldn't boot at all. In cwm go to mounts and make sure your internal sd and /data does or does not mount. And try to get that log it'll pretty much solve it without random flashing.
Tapatalked from my Galaxy S II.

Won't pull the logs, but I can show you pictures I took of the tablet in Recovery with the errors. Also, if I did what was suggested and tried to run a Stock Recovery what would happen if I did that and went back to full stock or atleast attempted to

j.price said:
Won't pull the logs, but I can show you pictures I took of the tablet in Recovery with the errors. Also, if I did what was suggested and tried to run a Stock Recovery what would happen if I did that and went back to full stock or atleast attempted to
Click to expand...
Click to collapse
I need to see the log not the error on screen, that just says error I need to see what causes it, in the log.
If you go back to full stock its like how Acer intended. You'll need to root and unlock the boot loader again and install cwm or twrp again, if you choose to. I'm not one to throw flashes at a device that isn't working correctly but sometimes that's the only fix. Still haven't mentioned if adb works. If you want to send pics I guess go into mounts and try to mount internal SD or external SD and take a pic of the error. Go ahead and post or send the pics of the error you took already, may explain things enough there.
Tapatalked from my Galaxy S II.

Unintentionally misspoke. Tablet is recognized by ADB in recovery but will not pull the log to my PC. That is why I offered the pictures. But as the log is better, could you just reconfirm first the commands needed to pull the logs via ADB> Maybe I am screwing something up. This is the first time I have had any major issues with Android.

j.price said:
Unintentionally misspoke. Tablet is recognized by ADB in recovery but will not pull the log to my PC. That is why I offered the pictures. But as the log is better, could you just reconfirm first the commands needed to pull the logs via ADB> Maybe I am screwing something up. This is the first time I have had any major issues with Android.
Click to expand...
Click to collapse
Ok if ADB is working then we can fix this. The command is
adb pull /cache/recovery/last_log > last_log
This will pull the log to whatever directory your ADB is launched from, if you have the SDK then it will be in your platform-tools folder. You can either post it here, or send it to me directly.
On your device, in recovery (of course at this point lol) attempt to mount each partition, cache, system, data, internal sd, external sd. Then run that command from your command prompt/terminal depending on what OS you use.
My email is [email protected], you can use this for gtalk if we need to start throwing commands at it, that will be the easier way vs posting and waiting. You can also email me that log directly if you choose. Once this is resolved you or I can post the fix back here for others should they need it.
Once this is done hit me up on gtalk if you can, usable through the gmail website as well, I have to make a phone call or 50 so I won't be checking here for a little bit.

adb gives me the error
C:\Program Files\Android\android-sdk\platform-tools>adb pull /cache/recovery/las
t_log > last_log
The system cannot find message text for message number 0x5 in the message file f
or System.
Click to expand...
Click to collapse
Now it is saying
remote object 'cache/revocery/last_log' does not exist
Click to expand...
Click to collapse

I'm also experiencing this issue where Relix rom froze on me and now recovery can't mound /sdcard/ Any ideas?

A100 won't mount emmc or SD Card
any solution to this??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I also had this problem, most forums say its a bad emmc. I chatted with an acer rep before sending it in, they received it yesterday, hopefully they wont give me problems because of the "unlocking"
UPDATEThey fixed it!! Only thing I can advise is to get on the site and chat with a rep to confirm that its a bad emmc, maybe they dont even boot it up once thats on the ticket

brick
sorry for my bad english, i have this problem im from venezuela and here the guarantee not cover me i send to acer venezuela and his say that is the logic card, why you fix you brick tablet? plsss i need help im trying to solve this brick since 4 month am i love mi tablet!!

etoxz said:
sorry for my bad english, i have this problem im from venezuela and here the guarantee not cover me i send to acer venezuela and his say that is the logic card, why you fix you brick tablet? plsss i need help im trying to solve this brick since 4 month am i love mi tablet!!
Click to expand...
Click to collapse
Its been verified there is a fault in the emmc. There is currently no way to repair it other then sending it to Acer, sorry to say. Acer locked us out of what we need to fix this.
Tapatalked from my Galaxy S II.

I had a similar issue it would load cwm or twrp but it would not load a recovery. it kept saying that files were missing i had to send it back for repair they replaced the main board it is an issue with the hardware not the software. Mine just froze then it died. sorry man. I can say mine was unlocked and they covered it under warranty.

pio_masaki said:
Its been verified there is a fault in the emmc. There is currently no way to repair it other then sending it to Acer, sorry to say. Acer locked us out of what we need to fix this.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
So, has anyone experienced this emmc fault outside of the Relix rom? I'm just curious--I had my tablet for 10 months and this rom for 1 week, and this happened. I loved the rom, but will definitely stay away from it if it's breaking emmc. (I'm a total noob -- not sure if the issue with emmc is hardware vs. software).

eatnosenuggets said:
So, has anyone experienced this emmc fault outside of the Relix rom? I'm just curious--I had my tablet for 10 months and this rom for 1 week, and this happened. I loved the rom, but will definitely stay away from it if it's breaking emmc. (I'm a total noob -- not sure if the issue with emmc is hardware vs. software).
Click to expand...
Click to collapse
Mine happened on a personal build of CM10, other's on CM9, etc. Its a fault with the emmc firmware, not ROM or Kernel dependant.

[Q] Trouble installing ROM. Is the phone bricked?

Hi, total newbie here.
I managed to root my HTC HD Desire.
Then I attempted to install the PACman 19.3 ROM.
I followed the procedure here relating to installing a ROM:
http://www.xda-developers.com/android/how-to-root-the-htc-desire-hd/
But, for the last hour I have had this flashing in different colors
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have obviously done something wrong. Pressing the power button and volume buttons has no effect.
Any help would be hugely appreciated.

cake100 said:
Hi, total newbie here.
I managed to root my HTC HD Desire.
Then I attempted to install the PACman 19.3 ROM.
I followed the procedure here relating to installing a ROM:
http://www.xda-developers.com/android/how-to-root-the-htc-desire-hd/
But, for the last hour I have had this flashing in different colors
I have obviously done something wrong. Pressing the power button and volume buttons has no effect.
Any help would be hugely appreciated.
Click to expand...
Click to collapse
That link is for the Hack kit and not for installing custom roms? what did you exactly do?
In what state is your phone right now?

glevitan said:
That link is for the Hack kit and not for installing custom roms? what did you exactly do?
In what state is your phone right now?
Click to expand...
Click to collapse
Oh!
I hacked the phone originally and rooted it. The video then explains how to install a ROM. I followed those instructions.
The phone is still like the photo is above. There are colors flashing around the pacman logo as the Android flashes green. I assumed it was loading the ROM.
It's been stuck like that for 2 hours.
Cheers

cake100 said:
Oh!
I hacked the phone originally and rooted it. The video then explains how to install a ROM. I followed those instructions.
The phone is still like the photo is above. There are colors flashing around the pacman logo as the Android flashes green. I assumed it was loading the ROM.
It's been stuck like that for 2 hours.
Cheers
Click to expand...
Click to collapse
Did you do a full wipe? That tutorial is not correct. Use this:
http://forum.xda-developers.com/showthread.php?t=1755410

glevitan said:
Did you do a full wipe? That tutorial is not correct. Use this:
http://forum.xda-developers.com/showthread.php?t=1755410
Click to expand...
Click to collapse
When you say 'full wipe', are you talking about clearing the cache?
After rooting the phone using the Advanced Ace Hack Kit, I did this:
Download your ROM of choice [pacman 19.3], do not extract it, and copy the .zip to the device SD card
Rename the file to “update.zip”
Power off your device
To boot in the bootloader, perform a battery pull, reinstate the battery, and hold the volume down and power buttons
Using the volume buttons to navigate, and power button to make selections, boot into Recovery, clear the cache, and select ‘install update from sdcard’.
Which then resulted in my current problem.
I assume I need to pull the battery out to get off this screen?
EDIT: The screen turned black. I couldn't power the phone up using the power button. I connected the USB cable to the PC and managed to boot up back to the same screen as before. Battery must have died.
The PC recognizes the phone is connected, but I am unable to view the SD card/drive.

cake100 said:
When you say 'full wipe', are you talking about clearing the cache?
After rooting the phone using the Advanced Ace Hack Kit, I did this:
Download your ROM of choice [pacman 19.3], do not extract it, and copy the .zip to the device SD card
Rename the file to “update.zip”
Power off your device
To boot in the bootloader, perform a battery pull, reinstate the battery, and hold the volume down and power buttons
Using the volume buttons to navigate, and power button to make selections, boot into Recovery, clear the cache, and select ‘install update from sdcard’.
Which then resulted in my current problem.
I assume I need to pull the battery out to get off this screen?
EDIT: The screen turned black. I couldn't power the phone up using the power button. I connected the USB cable to the PC and managed to boot up back to the same screen as before. Battery must have died.
Click to expand...
Click to collapse
That is not correct. Using video tutorials is useless...Read the thread I linked you, that is how a custom rom is flashed.
Put rom in your sdcard (no rename it)
Boot in recovery
Wipe data/factory reset
wipe cache partition
format system
format data
format cache
Install zip from sdcard
choose zip
Install file (as it is called)
If needed flash GAPPS (after the rom)
Reboot and magic is done.

glevitan said:
That is not correct. Using video tutorials is useless...Read the thread I linked you, that is how a custom rom is flashed.
Put rom in your sdcard (no rename it)
Boot in recovery
Wipe data/factory reset
wipe cache partition
format system
format data
format cache
Install zip from sdcard
choose zip
Install file (as it is called)
If needed flash GAPPS (after the rom)
Reboot and magic is done.
Click to expand...
Click to collapse
Cheers
I got to wipe cache partition, but have no options for "format", using the ClockworkMod Recovery v5.0.27
When I tried installing zip >choose zip>install file (name of zip file), I end up with this:
E:Error in sdcard/d710_PACman-v19.3.0_1.23.zip (status 7)
Installation aborted

cake100 said:
Cheers
I got to wipe cache partition, but have no options for "format", using the ClockworkMod Recovery v5.0.27
When I tried installing zip >choose zip>install file (name of zip file), I end up with this:
E:Error in sdcard/d710_PACman-v19.3.0_1.23.zip (status 7)
Installation aborted
Click to expand...
Click to collapse
that means that your download is probably corrupted. Have you checked md5sum?
Sent from my GT-N7000 using xda app-developers app

Got it up and running with a fresh download of the zip file and I checked md5sum.
Thanks for your help.

Getting /system mount error

After wiping my phone to re-install the ROM i am using (due to issues) i am getting the e /system not mounted error when flashing. I am on a SM-705 using TWRP 2.8 recovery
What i tried so far:
1) Reboot to recovery and try again
2) Reformat the system partition in TWRP
I read somewhere that installing CWM may help.
I also read that installing the stock rom (which i cannot find) via odin will also resolve the issue.
I am unsure on how to proceed, please help!

1H4X3R said:
After wiping my phone to re-install the ROM i am using (due to issues) i am getting the e /system not mounted error when flashing. I am on a SM-705 using TWRP 2.8 recovery
What i tried so far:
1) Reboot to recovery and try again
2) Reformat the system partition in TWRP
I read somewhere that installing CWM may help.
I also read that installing the stock rom (which i cannot find) via odin will also resolve the issue.
I am unsure on how to proceed, please help!
Click to expand...
Click to collapse
2) Reformat or wipe?

ashyx said:
2) Reformat or wipe?
Click to expand...
Click to collapse
Reformat, Wipe --> System (checked) --> Reformat --> FAT

1H4X3R said:
Reformat, Wipe --> System (checked) --> Reformat --> FAT
Click to expand...
Click to collapse
FAT? It should be Ext4.

ashyx said:
FAT? It should be Ext4.
Click to expand...
Click to collapse
Thanks. I just tried Ext4 format but it didn't help either. I was following this guide: https://www.youtube.com/watch?v=VJRKuQf0puE
Anything i can do to resolve this?

1H4X3R said:
Thanks. I just tried Ext4 format but it didn't help either. I was following this guide: https://www.youtube.com/watch?v=VJRKuQf0puE
Anything i can do to resolve this?
Click to expand...
Click to collapse
What is telling you it cannot mount system? Post your recovery.log after getting this error.
Sent from my SM-T280 using XDA-Developers mobile app

Not sure how to do that so i took some screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You need to post the recovery.log. Hit the advanced button then save recovery log.
Post it here as a file or on pastebin.com
Also you realise you are using an outdated version of twrp?
Sent from my SM-T280 using XDA-Developers mobile app

This is the only version of TWRP i could find for my Tablet. It worked just fine for ~ 5 times (installing ROMs 5 times). If you know where i could find a newer version for a SM-705 Tablet please let me know.
Here is the recovery.log file (clicking the attachment pin didn't seem to do anything so i uploaded it this way): https://puu.sh/qgqUb/c0db2985d3.log

1H4X3R said:
This is the only version of TWRP i could find for my Tablet. It worked just fine for ~ 5 times (installing ROMs 5 times). If you know where i could find a newer version for a SM-705 Tablet please let me know.
Here is the recovery.log file (clicking the attachment pin didn't seem to do anything so i uploaded it this way): https://puu.sh/qgqUb/c0db2985d3.log
Click to expand...
Click to collapse
You're a bit behind the times. I have updated twrp several times since.
http://forum.xda-developers.com/showthread.php?t=3074633
I have looked at your recovery log.
Your system partition is not mounting.
This is probably due to incorrect formatting.
You should be able to format it with the wipe options in twrp. Ensure you select ext4 as the partition type.
Wipe>advanced wipe>system>repair or change file system>change file system>EXT4
After formatting try and mount the system partition.
If you can't post the recovery.log again before rebooting.
Sent from my SM-T280 using XDA-Developers mobile app

ashyx said:
You're a bit behind the times. I have updated twrp several times since.
http://forum.xda-developers.com/showthread.php?t=3074633
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok. I will try this and let you know if i am still getting the error. Thanks.

1H4X3R said:
Ok. I will try this and let you know if i am still getting the error. Thanks.
Click to expand...
Click to collapse
See my edits.
Sent from my SM-T280 using XDA-Developers mobile app

ashyx said:
You're a bit behind the times. I have updated twrp several times since.
http://forum.xda-developers.com/showthread.php?t=3074633
I have looked at your recovery log.
Your system partition is not mounting.
This is probably due to incorrect formatting.
You should be able to format it with the wipe options in twrp. Ensure you select ext4 as the partition type.
Wipe>advanced wipe>system>repair or change file system>change file system>EXT4
After formatting try and mount the system partition.
If you can't post the recovery.log again before rebooting.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
After flashing to the new TWRP and reformatting system i made a log file. However, when i insert the SD card in the computer no .log file is there. On TWRP it does say that a log file has been created on the microSD card so idk what is going on.
Update 1: I managed to get a log file after trying to copy log multiple times (this is not after a reformat, that log will come shortly): http://puu.sh/qgLxV/0619e7bb21.log
Update 2: Here is the log from right after the reformat: http://puu.sh/qgLMB/bd38991df8.log
Update 3: When reformatting, i used to receive the error: could not mount system (or similar) but this time i didn't. So i tried to install a ROM but i got the same error as before:
I also got this message twice (now i don't get it anymore):

Your system partition is now mounting.
Make sure 'keep system read only' is not checked under MOUNT.
Your zip should now install.
Sent from my SM-T280 using XDA-Developers mobile app

ashyx said:
Your system partition is now mounting.
Make sure 'keep system read only' is not checked under MOUNT.
Your zip should now install.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well i just tried again, (making sure that system read only is unchecked) and now i am getting the red failed to mount system again. Here is a link to the log (after reformatting and getting the red error message): https://puu.sh/qhotb/348f762b45.log
I tried once again after a restart to reformat but i get the same error (in red text), i did not get this the last few times but i did get this before.
When trying to install the ROM this time, i get no failed to mount error BUT it is still stuck, as in it doesn't install the ROM but rather is stuck at extracting package.
Here is an image of the problem:

You are actually waiting for it to extract the files to system?
Just because it doesn't show progress it doesn't mean it's not happening.
Sent from my SM-T280 using XDA-Developers mobile app

ashyx said:
You are actually waiting for it to extract the files to system?
Just because it doesn't show progress it doesn't mean it's not happening.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
I let it run overnight and it was still stuck on the same screen when i checked in the morning (typically the blue bar fills up slowly from 0-100%, now it is just stuck at 0% solid blue color bar).
I just tried again and i am getting the "unmount of /system failed" error again. When i try to reformat i get a very similar error in red text.

1H4X3R said:
I let it run overnight and it was still stuck on the same screen when i checked in the morning (typically the blue bar fills up slowly from 0-100%, now it is just stuck at 0% solid blue color bar).
I just tried again and i am getting the "unmount of /system failed" error again. When i try to reformat i get a very similar error in red text.
Click to expand...
Click to collapse
Can you post your recovery.log AFTER trying to install the rom?
Sent from my SM-T280 using XDA-Developers mobile app

ashyx said:
Can you post your recovery.log AFTER trying to install the rom?
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
I can only get a recovery.log after a restart as i cannot exit the installer without completely shutting down the device. I can however provide you with a log of after an attempted reformat (which i have done already).
(Huge) Update: I found a recovery file on my computer for the tab that is super old, back when i used to run a 4.4.2 custom ROM on it and i restored from that and it works. However, that specific custom ROM does not have a networking driver (or something of that sort, i cannot connect to my cellular provider) and i want to install the newer 5.0.2 custom ROM i was using before but i don't want to risk another error mounting /system :/ The ROM i used is this one, hope you can help me find a way to get cellular service: selambA ROM.
Update 2: I cannot connect to any google services or anything related to google when i restored the selambA ROM.
Update 3: I tried to reinstall the 5.0.2 ROM but i am getting the same, unmount of /system error :/

1H4X3R said:
I can only get a recovery.log after a restart as i cannot exit the installer without completely shutting down the device. I can however provide you with a log of after an attempted reformat (which i have done already).
(Huge) Update: I found a recovery file on my computer for the tab that is super old, back when i used to run a 4.4.2 custom ROM on it and i restored from that and it works. However, that specific custom ROM does not have a networking driver (or something of that sort, i cannot connect to my cellular provider) and i want to install the newer 5.0.2 custom ROM i was using before but i don't want to risk another error mounting /system :/ The ROM i used is this one, hope you can help me find a way to get cellular service: selambA ROM.
Update 2: I cannot connect to any google services or anything related to google when i restored the selambA ROM.
Update 3: I tried to reinstall the 5.0.2 ROM but i am getting the same, unmount of /system error :/
Click to expand...
Click to collapse
You can pull the log from cache/recovery/last_log after rebooting, but it may not get created if you are hard resetting the device.
Do you know how to use adb?
Sent from my SM-T280 using XDA-Developers mobile app

Unable to install TWRP

Hi
I was running stock European android, unlocked bootloader and rooted with trwp
I decided to install lineage 15.1 plus gapps which I have up and running, used adb push to install
What I can't do is reinstall trwp, neither image or zip as always getting error messages, endpoint something or other... Tried fastboot, adp push... Lineage recovery..
I reckon this might be down to the fact that I didn't format before the install getting rid of the encryption
So any ideas how to install trwp so that i can start correctly all over again
The lineageo recovery doesn't give any real options concerning formatting
Running a moto force z2

What command are you running to send the TWRP image to the device in fastboot? You should be in bootloader mode and you cannot flash the TWRP image to the device. Rather, you should use
Code:
fastboot boot twrp-3.x.x-x.img
Once you boot the TWRP image, you can install it with more persistence using the zip installer from the TWRP website. Since this will alter the boot image, you need to flash Magisk after TWRP if you want root.

Hi
did this
adb devices
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
booting into trwp, wiped all - ok
Flashed from trwp lineage 15.1 - ok
Flashed Gapps - NOT ok
Flashed Magisk -NOT Ok
booted into lineage, installed Magisk app and reflashed TRWP using
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
Flashed Magisk from trwp this time - Ok
Now what do I do to get TRWP to stay inplace as still only lineage recovery, though I flashed the image using the Magisk app
then I did
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
installed mindthegapps using trwp, cleared dalvic et cache, but when booting stuck on verification google informations and can't get into google play
rebooted into recovery, again lineasge, cleared cache and system, when rebooted Gapps worked just nicely
so still no TRWP in permanent place (can live without if need be, but would like it) otherwise all is running
This is long winded but might be of use to others as see many questions like mine on various forums
thanks for your help

minty95 said:
Hi
did this
adb devices
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
booting into trwp, wiped all - ok
Flashed from trwp lineage 15.1 - ok
Flashed Gapps - NOT ok
Flashed Magisk -NOT Ok
booted into lineage, installed Magisk app and reflashed TRWP using
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
Flashed Magisk from trwp this time - Ok
Now what do I do to get TRWP to stay inplace as still only lineage recovery, though I flashed the image using the Magisk app
then I did
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
installed mindthegapps using trwp, cleared dalvic et cache, but when booting stuck on verification google informations and can't get into google play
rebooted into recovery, again lineasge, cleared cache and system, when rebooted Gapps worked just nicely
so still no TRWP in permanent place (can live without if need be, but would like it) otherwise all is running
This is long winded but might be of use to others as see many questions like mine on various forums
thanks for your help
Click to expand...
Click to collapse
These are the steps to follow to get lienage 15.1 to work flawless. I went through this so follow closely.
1) Start out with full stock again.
2)Power off phone, and enter fastboot
3)Fastboot boot twrp-3.2.3-2-nash.img
4)Go to wipe and Choose format data
5)Go back to main screen, choose wipe, choose advance wipe, and wipe system only nothing else
6)Go back to main screen, choose install. Install Lineage 15.1 Once finished do NOT reboot.
7)Go back to main, Install and, flash twrp3.2.3-2.zip
8)Go back to main screen, choose reboot, reboot back into recovery.
9) Next this is important. Flash MIndTheGapps first then flash the SprintFix.zip (If you do not do it this way, you will only get 3G not LTE)
10)Go to reboot, reboot back into recovery, the boot system..
If you follow this it will work no problem.. If you don't flash the twrp-3.2.3-2-nash.zip First reboot back into recovery. Then MindTheGapps, and SprintFix won't work. What ever you do, do not skip the flashing the twrp3.2.3-2-nash.zip, or you will enter Lineage recovery, and it dose not work worth a dam.
After all that, enable Developer Option in setting, turn on USB debugging, Then reboot back to recovery and flash the addonsu-15.1-arm64-signed.zip. When back to system go back to developers option, scroll down Root Access and choose your option.. I choose Apps and ADB.

Si I tried again,
Still can't get TRWP to stay
adb devices
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
booted into TRWP recovery
installed TRWP from zip filet 'twrp-installer-nash-3.2.2-2.zip'
No error message said installing in, slots 1 &2
rebooted into recovery , TRWP gone again recovery lineage by default again
Now I really lost.....
any ideas ?

I just unlocked my Z2 Force, and when I try "fastboot boot twrp-3.3.1-0.img" it just sits there.
It shows:
Sending 'boot.img' (33504 kb)
and it will sit there for literal hours.
Any ideas?

mikiemc73 said:
I just unlocked my Z2 Force, and when I try "fastboot boot twrp-3.3.1-0.img" it just sits there.
It shows:
Sending 'boot.img' (33504 kb)
and it will sit there for literal hours.
Any ideas?
Click to expand...
Click to collapse
Use oem cable, change usb ports. Use 2.0 ports if you have them.

I'm in the same situation as you
mikiemc73 said:
I just unlocked my Z2 Force, and when I try "fastboot boot twrp-3.3.1-0.img" it just sits there.
It shows:
Sending 'boot.img' (33504 kb)
and it will sit there for literal hours.
Any ideas?
Click to expand...
Click to collapse
please help if you've found any solution

PHP:
adb reboot bootloader
fastboot boot '(drag n drop twrp img here)

41rw4lk said:
PHP:
adb reboot bootloader
fastboot boot '(drag n drop twrp img here)
Click to expand...
Click to collapse
no use, it says downloading 'boot.img'
And says FAILED in about 40 secs and the phone gets disconnected.
Am I missing any step in the bootloader before executing command??
or anything else??
Please help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}