[Recovery][UNOFFICIAL][SM-T320/SM-T325] ClockworkMod Recovery for Tab Pro 8.4 WiFi & LTE
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features
* included in this RECOVERY
* Before flashing it! YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device,
* I will point you out to this message ! ! !
*
*/
By using this recovery you agree with the above terms!
WARNING:
Flashing this will trip you Knox flash and officially void your warranty.
You must use Odin to flash this. I am not going to tell you how to do that (there are lots of references on the web).
Download:
* Current: 2014-06-05 for Tab Pro 8.4 Wifi and LTE
Change Log
* 2014-06-05: Added SM-T325 support and selinux aware backups
* 2014-05-04: Faster install / wipe, latest kernel changes, upstream changes
* 2014-03-17: Added support for SM-T320XX (everything outside of north america)
* 2014-03-13: Set the build device name correctly
* 2014-03-02: Add external sdcard support.
Restoring old stock backups
Backups of the stock ROM using a recovery older than 2014-06-05 do not restore correctly because Samsung doesn't correctly restore the selinux contexts on boot.
Backups made with that version of recovery and later should restore normally.
If you need to restore an old backup do:
* Restore
* Mount /data
* adb shell restorecon -r /data
* Unmount /data
If you don't know how to do all those steps, then my best advice would be to do a factory reset after restoring and that will at least get you back to something that boots.
XDA:DevDB Information
ClockworkMod Recovery [UNOFFICIAL], Tool/Utility for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
Version Information
Status: Stable
Created 2014-03-01
Last Updated 2014-06-05
Reserved
I get a "binary error" from downloaded file.
using Windows 8.1 .
Checked md5 and the checker matches.
7zip says there is a error using archive checker.
Thanks for your efforts
kdkinc said:
I get a "binary error" from downloaded file.
using Windows 8.1 .
Checked md5 and the checker matches.
7zip says there is a error using archive checker.
Thanks for your efforts
Click to expand...
Click to collapse
What gives you a binary error? Is that a message from Odin?
kdkinc said:
I get a "binary error" from downloaded file.
using Windows 8.1 .
Checked md5 and the checker matches.
7zip says there is a error using archive checker.
Thanks for your efforts
Click to expand...
Click to collapse
Hmmm. Just tried uploading and then downloading a version to d-h.st and it really seems like that site corrupts the odin files.
Sigh. Which probably means that no one has tried CyanogenMod yet which is mildly depressing. It's pretty nice on this hardware.
Looks like it's getting corrupt when I upload to dropbox too. I'll try again.
kdkinc said:
I get a "binary error" from downloaded file.
using Windows 8.1 .
Checked md5 and the checker matches.
7zip says there is a error using archive checker.
Thanks for your efforts
Click to expand...
Click to collapse
Try this one (unzip it before flashing with odin): http://d-h.st/eJQ
crpalmer said:
Try this one (unzip it before flashing with odin): http://d-h.st/eJQ
Click to expand...
Click to collapse
success with te new zip file.....we have a winner CWM boots up.
Thank You for the new zip file.
crpalmer said:
Hmmm. Just tried uploading and then downloading a version to d-h.st and it really seems like that site corrupts the odin files.
Sigh. Which probably means that no one has tried CyanogenMod yet which is mildly depressing. It's pretty nice on this hardware.
Click to expand...
Click to collapse
Give us a chance to wake up (and make our backups)
I'm going to be trying CM as soon as I have the backup done and the CM downloaded. At 90% now...
Yup. Looks like the new upload works. I thought that I was the only one facing the issue.
Thanks!
me0wster said:
Yup. Looks like the new upload works. I thought that I was the only one facing the issue.
Thanks!
Click to expand...
Click to collapse
If something doesn't work, please let me know!
Any info on .android_secure not being backed up by this CWR? I think that's how I wound up needing to reimage my device with Kies to get it to boot.
I'm pm'ing an attachment with a ton of logs pulled once I knew there were some potential issues. Unfortunately I don't know which ones are most valuable.
roustabout said:
Any info on .android_secure not being backed up by this CWR? I think that's how I wound up needing to reimage my device with Kies to get it to boot.
I'm pm'ing an attachment with a ton of logs pulled once I knew there were some potential issues. Unfortunately I don't know which ones are most valuable.
Click to expand...
Click to collapse
Nothing much in the logs.
I did confirm that you cannot seem to restore a stock ROM successfully. I didn't have to reflash with Kies/Odin (a factory reset made it work just fine although somewhat defeats the purpose of backing it up). Restoring CM backups do work fine though.
crpalmer said:
Nothing much in the logs.
I did confirm that you cannot seem to restore a stock ROM successfully. I didn't have to reflash with Kies/Odin (a factory reset made it work just fine although somewhat defeats the purpose of backing it up). Restoring CM backups do work fine though.
Click to expand...
Click to collapse
Yeah, my main hesitation in doing the reflash or the reset was that my stock has a lot of stuff kind of painfully disabled and/or removed. I'm not sure how to get Titanium to restore the settings just so after a reset or reflash. I think the reflash is going to be faster than a restore, though, and will be facilitated by a viable titanium backup.
Although, this time through I don't think I've actually deleted anything and it does feel better than it used to, I think because it was looking to run files I hadn't just disabled but flat deleted.
Samsung source code
http://www.androidpolice.com/2014/0...ource-for-tab-pro-8-4-wi-fi-and-lte-variants/
kdkinc said:
Samsung source code
http://www.androidpolice.com/2014/0...ource-for-tab-pro-8-4-wi-fi-and-lte-variants/
Click to expand...
Click to collapse
Excellent news! Looking forward to more development now.
Can someone verify the settings that need to be done in Odin for this please?
vexille said:
Can someone verify the settings that need to be done in Odin for this please?
Click to expand...
Click to collapse
This is flashed in recovery, not ODIN.
Also, OP...this ROM very well, only strange this is Falcon wont work. Says network time must be automatic, which it is. Any ideas?
jmill75 said:
This is flashed in recovery, not ODIN.
Also, OP...this ROM very well, only strange this is Falcon wont work. Says network time must be automatic, which it is. Any ideas?
Click to expand...
Click to collapse
This is the recovery thread.
As for Odin settings, whatever was default worked for me.
From my Pro Tab 8.4
Ha my bad. I was jumping between cm11 thread.
Sent from my VS980 4G using Tapatalk
oops wrong thread.
Related
Presented to the masses is this Odin package (works 100% on my Infuse) to flash this stock ROM with these extra features to your Infuse.
Please use this ROM as a foundation to develop your own ROM off of. I will be focusing my time on the Refuse ROM as much as I can.
See below for features:
* Deodexed
* Rooted
* Tethering (Thanks gtg456x!)
* Completely De-bloated (see the De-bloated section for what was removed)
* 3e Recovery modded
* .tar.md5 for file integrity
Flash the .tar.md5 file using Odin3 v1.81 (included in the download package) using the same steps as found in the Odin flash thread HERE.
After it boots up, it will boot into recovery first. Choose "Clear all User data". Or, if you prefer, when you boot into the rom go to Settings -> Privacy -> Factory Reset to clear /data. (Thanks crawlgsx!)
DEBLOATED:
Removed from /system/app:
* SamsungWidget_FeedAndUpdate.apk
* Days.apk
* BuddiesNow.apk
* 2.8.1_YP_38384.apk
* WISPr_55_Android22.apk
* AT_T_code_scanner_vpl_1.1_aligned.apk
* SamsungWidget_ProgramMonitor.apk
* WriteandGo.apk
* MiniDiary.apk
* Memo.apk
* MediaHub.apk
* myATTVPL_aligned.apk
* Telenav.apk
* com.mobitv.client.tv.apk
* FBAndroid-1.5.2_preload.apk
* androidlauncher_Generic_android2.2-72x72_build_1_1D2011_03_16t09_30.apk
* TetheringManager0326.apk
Remember, I'm not responsible if this bricks you (which I find it very hard to believe that it could...).
Shout-outs!:
gtg465x - Thanks for the info to fix Tethering!
Download Link:
De-Odexed Rooted Stock ROM w/o Bloatware
Sweet! Now if only we could get CWM working with SD cards we'd be all set.
beatblaster said:
Sweet! Now if only we could get CWM working with SD cards we'd be all set.
Click to expand...
Click to collapse
Check my thread. Someone says they successfully flashed my ROM with CWM by using a different SD card instead of the one that came with the phone. Would be nice to get further confirmation of course.
gtg465x said:
Check my thread. Someone says they successfully flashed my ROM with CWM by using a different SD card instead of the one that came with the phone. Would be nice to get further confirmation of course.
Click to expand...
Click to collapse
Just read that and thank goodness I have another one. I'm gonna test out my own flashable zips here in just a sec and report back.
Nice. Will try when I get home
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Thanks! Works like a charm. Hopefully there'll be fully customized ROMs soon such as CM7.
Same here works 100% Thanks. but I can't change files whenever I try to replace files I get this message "there was not enough free disk space to complete the paste operation"
sinan2010 said:
Same here works 100% Thanks. but I can't change files whenever I try to replace files I get this message "there was not enough free disk space to complete the paste operation"
Click to expand...
Click to collapse
Are you doing this in /system? if so, you need to mount /system as read/write.
Code:
adb shell
mount -o remount rw /system
then try again.
If not, where are you seeing the paste operation problem?
h8rift said:
Are you doing this in /system? if so, you need to mount /system as read/write.
Code:
adb shell
mount -o remount rw /system
Click to expand...
Click to collapse
yes in the system. I'm sorry I'm a noob, I don't know how to do it. where can I do it what do I suppose to do with this code sorry
sinan2010 said:
yes in the system. I'm sorry I'm a noob, I don't know how to do it. where can I do it what do I suppose to do with this code sorry
Click to expand...
Click to collapse
USB cable your Infuse4G to your computer, open up Command Prompt and type the commands I placed in the code wrapper above .
Worked perfect! Muchas gracias .
May just be my imagination but it seems to finally not take forever to power off, woohoo!
h8rift said:
USB cable your Infuse4G to your computer, open up Command Prompt and type the commands I placed in the code wrapper above .
Click to expand...
Click to collapse
I just did what you said and I got this
'adb' is not recognized as an internal or external command,
operable program or batch file.
'mount' is not recognized as an internal or external command,
operable program or batch file.
sinan2010 said:
I just did what you said and I got this
'adb' is not recognized as an internal or external command,
operable program or batch file.
'mount' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Sorry, must've gotten ahead of myself. You need to have adb installed (found in the Android SDK).
Hrm I followed the directions exactly but I still have a bunch of Apps that you have listed as debloated installed (or at least market thinks they are)
It also says I still have things such as ADW EX installed but they just FC if I try to launch them.
I also cant launch ROM Manager, it just FC's.
Was I suppose to wipe caches before doing an Odin flash?
Update1: Even loads of freshly installed apps are FC'ing that previously worked.
Ok hello all ! Im a big nood in the android world lol.i switched to infuse from iphone4 so im lost I already have the root program but what else should I do im new? I would love to have faster phone and better battery what do I do?
Sent from my SAMSUNG-SGH-I997 using XDA App
crawlgsx said:
Hrm I followed the directions exactly but I still have a bunch of Apps that you have listed as debloated installed (or at least market thinks they are)
It also says I still have things such as ADW EX installed but they just FC if I try to launch them.
I also cant launch ROM Manager, it just FC's.
Was I suppose to wipe caches before doing an Odin flash?
Update1: Even loads of freshly installed apps are FC'ing that previously worked.
Click to expand...
Click to collapse
Looking into this.
h8rift said:
Looking into this.
Click to expand...
Click to collapse
Try a Factory Reset?
h8rift said:
Try a Factory Reset?
Click to expand...
Click to collapse
I just did a factory reset and just wiped my SD card to be safe.
Did that revert me back to stock, or am I still on this ODIN Rom?
crawlgsx said:
I just did a factory reset and just wiped my SD card to be safe.
Guess I shall try again!
Click to expand...
Click to collapse
Shouldn't need to re-Odin or anything after a factory reset (not sure if that was what you were implying by trying again or not). Just factory reset and sign back in to your Google stuff .
h8rift said:
Shouldn't need to re-Odin or anything after a factory reset (not sure if that was what you were implying by trying again or not). Just factory reset and sign back in to your Google stuff .
Click to expand...
Click to collapse
Indeed I was, thank you for clarification
Testing now!
Hi All,
I have successfully rooted my HTC Incredible S and then, I have installed a custom ROM "Galnet MIUI-Icecream Sandwich ROM-Build:2.11.26" using the ROM Manager App available in the Android Market.
Everything went on well... the back up, clearing the cache etc. are all completed successfully and my mobile rebooted. There was a new screen with a flash image showing MI (in orange letters) with xiaomi.com just below it. I waited for almost 30 minutes but the screen is just showing the same flash image playing some nice notification sound.
Now Should I be worried? Is it a part of the process or is my mobile Bricked ?
Please help...
Have you tried flashing a new ROM in the custom recovery or restoring your back-up? Doesn't sound bricked to me...
DistrictDigital said:
Have you tried flashing a new ROM in the custom recovery or restoring your back-up? Doesn't sound bricked to me...
Click to expand...
Click to collapse
I have recovered it from the backup... it's not bricked
But I am wanting to install some latest and stable custom ROM compatible with HTC Incredile S.
Any suggestions please....
You must ALWAYS check the md5 sum of all of your ROM's. This could have been a very bad thing for your phone and your wallet. Any ROM in your phone's specific Android Development section is almost guaranteed to work. Just re-download your MIUI ROM and enjoy.
DistrictDigital said:
You must ALWAYS check the md5 sum of all of your ROM's. This could have been a very bad thing for your phone and your wallet. Any ROM in your phone's specific Android Development section is almost guaranteed to work. Just re-download your MIUI ROM and enjoy.
Click to expand...
Click to collapse
I understood the later part but regarding the first part in which you said 'You must ALWAYS check the md5 sum of all of your ROM's".....can you please help me understand that.
An MD5 is a long number that will usually be shown next to your ROM download. This number is unique to that particular file.
If something happens during your download that corrupts the ROM file (breaks it), then the MD5 number will be different when you check it. This warns you the file you have got on your computer is different to the original.
There's a good description of how to check and use MD5 on the OpenOffice website - try Googling the words: openoffice md5.
An MD5 is called a 'checksum', there are other ways of working out checksums that you also might see, like CRC or SHA-256. All have benefits and downsides.
In short, checking the MD5 makes sure you aren't flashing a 'bad' copy of the file, which might break your phone.
Hope that helps
skuffle said:
An MD5 is a long number that will usually be shown next to your ROM download. This number is unique to that particular file.
If something happens during your download that corrupts the ROM file (breaks it), then the MD5 number will be different when you check it. This warns you the file you have got on your computer is different to the original.
There's a good description of how to check and use MD5 on the OpenOffice website - try Googling the words: openoffice md5.
An MD5 is called a 'checksum', there are other ways of working out checksums that you also might see, like CRC or SHA-256. All have benefits and downsides.
In short, checking the MD5 makes sure you aren't flashing a 'bad' copy of the file, which might break your phone.
Hope that helps
Click to expand...
Click to collapse
Thanks a lotttt.. it was wonderful knowledge sharing
No worries - glad to help
Rogue XM Touch Recovery v1.5.0-R1
(CWM-based Recovery v5.0.2.8)
For the Asus Transformer TF101
First off, thank you to...
Team Rogue
Koush
CyanogenMod Team
j-r0dd
Solarnz
Roach2010
All I did slap together all their hard work to make it work on the TF101.
Sources
Rogue Recovery
The source and more info for Rouge Recovery is available in the Xoom release thread from Team Rogue. I have not made any modifications to it to work with the TF101. You can find that thread here:
http://forum.xda-developers.com/showthread.php?t=1235170
The discussion of the touch release in that thread begins here:
http://forum.xda-developers.com/showthread.php?t=1235170&page=13#123
Recovery Kernel
I used the kernel from Roach2010's ClockworkMod Recovery 3.2.0.1 release here:
http://forum.xda-developers.com/showthread.php?t=1213723
Device Tree
Mostly based on AOKP's TF101 device tree, just picked out the parts needed to compile the recovery. Particularly BoardConfig.mk:
https://github.com/rburrow87/android_device_asus_tf101_recoveryonly
Updates
[2012-05-25] 1.5.0-R1 (5028-based)
Updated to Rogue XM Recovery v1.5.0 which is touch-enabled with the same features as before. See the Xoom release thread for more information on Rogue Recovery:
http://forum.xda-developers.com/showthread.php?t=1235170
Can also finally use the boot to recovery option available in some ROMs thanks to the recovery boot loop fix from Roach2010 from here:
http://forum.xda-developers.com/showthread.php?t=1213723
Workaround for small menu targets
http://forum.xda-developers.com/showpost.php?p=26142147&postcount=151
If I can figure out a way to just make the menu items taller, I'll make an update. Otherwise I'm waiting for Rogue to implement it first.
[2012-01-14] 1.3.0-R1 (5027-based)
Original release, non-touch
Info
Mounting as USB storage does not work. (Accessing the tablet or SD card from your computer when plugged in via USB)
Installation
I tested this the best I could, but use at your own risk. I am not liable for data loss, spontaneous combustion, temporal anomalies, or anything in between.
Just flash the attached zip from CWM.
There's also an nvflash version that has the recovery.img in it and will only flash the recovery if you prefer that method. Or just so you don't have to unpack the blob file if you need the recovery.img.
Misc:
I did this because I thought it'd be nice to have a newer recovery for our TF101s, but also because I want to learn to do some sort of development even if it's just building for similar devices. I'm still new to using anything like git or using C/Java like this so don't expect miracles right away if bugs come up! I have some experience with other languages, but not in this kind of application.
Thank you, looks nice. Doing a nand backup right now with it.
there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App
Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk
baseballfanz said:
Thank you, looks nice. Doing a nand backup right now with it.
Click to expand...
Click to collapse
Awesome!
will8578 said:
there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I saw that post! I've been watching that thread and trying it out when there's an update.
80slovechild said:
Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
To do that, you have to extract the zip and then unpack the blob file... but I updated the OP with an extra nvflash version that flashes just the recovery and gives you the recovery.img.
Finally...a relatively current back up for the TF!!
THANK YOU!!
Backing up with 3201, then installing this.
Beautiful work!! Works flawlessly!
Finally! A 5.x.x.x CWM recovery
Does this allow flashing from both internal and external?
On my Galaxy Nexus, they also have a touch softkey mod that has softkeys for up, down, back, and select. Not a big deal but something cool to look into if you get bored.
LTE EX Galaxy Nexus - CM9 AOKP
Asus Transformer - Revolver
Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..
luna_c666 said:
Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..
Click to expand...
Click to collapse
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.
Worked for me. Way way way better color scheme and it booted quick! Thanks!
wackydroid said:
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.
Click to expand...
Click to collapse
its definitely not the same as v3.x.... that being said however, simply look at the android_bootable_recovery github to see the differences since v3.x
I think with the latest versions its even possible to use the mount usb with the tablets own MicroSD card where-as in the v3.x tree it wasnt (thanks to v5.x's inclusion of dual mount support, specifically done to support devices with large internal storage)
Still, i have to agree with everyone else, its REALLY nice to finally see a v5.x CWM... using it on my HD2, Evo Shift, and HeroC, it really was a surprising difference from when I was sticking with v3.x
Just awesome!!! Thanks so much!
this needs to be moved to the dev section, but great job!
Sent from my Transformer TF101 using xda premium
Thanks! Installed successfully on two separate rooted B60 TF101's(ARHD 3.2, and Krakd 1.4.2)without any issues. Works great nice job!
New recovery works great!
Just flashed this without any issue. Nice look and feel. Are there more options available under the 'wipe' option, such as ability to wipe only cache or Dalvik cache like the 3.2.0.1 had? I haven't had a chance to look yet and didn't want to chance inadvertently wiping my device. Thanks.
[EDIT] I've now had time to look around and answer my own question. Yes, the other wipe options are there under the wipe menu item. Good to not see that sd card error all the time. So far it seems pretty flawless and better looking, too. I had to reflash my ROM last night and got to put it through it's paces.
Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
I also did a back up and restore and my Wifi is fine.
I did not do the advance backup just the regular backup.
Someone else reported this wifi problems using Roach's 3.2.0.1 CWM also.
jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
Hmm, weird, I'm not sure why the recovery would break that unless it's failing to restore something or possibly failed to back something up. I did several backups and restores when I was checking to see if everything worked and never encountered that. Maybe try restoring the one giving your trouble a couple of times to see if it comes back?
hachamacha said:
Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --
Click to expand...
Click to collapse
Looks like somewhere around CWM 4 is when the switch to tar was made. It has better the speed along with the ability to back up and restore the correct filesystem. Sounds like the progress thing was added somewhere around then as well.
[ Found here: https[colon]//plus.google[dot]com/103583939320326217147/posts/G4VQuCpR25y Sorry, can't make outside links yet. ]
Looking at a kernel zip, it uses dd to put the blob in /dev/block/mmcblk0p4, which is also where the recovery goes... I clearly need to learn more about what's going on here when flashing a kernel or recovery to the same thing and what the function of the blob is.
Looking in the nandroid backuip system tar though, it grabs the /system/lib/modules folder which some kernel zips add to, so the nandroid is backing that up. I'm not sure if nandroid, at least in its current state, is able to back up or restore the kernel itself because of the whole blob thing?
Hmm, perhaps I should make a feature list instead of just saying look at the Xoom release thread!
Hello everyone
I am unable to flash the cm10 rom on my tf300t using TWRP 2.3.3.0. Most forums i read have cwm, but I am having some other issues with cwm so i have to use TWRP. The error is status 7, see attachment below. (I have already verified and md5 is alright)
Any help or pointers are appreciated.
Sent from my Galaxy Nexus using xda app-developers app
the screenshot says no MD5 file is found. Not saying that is your issue, but just an observation since you said you checked it.
Also, it appears the zip file is inside a directory? try moving it to the root of the SD card. sometimes the paths for various functions of the flash assume that you are operating out of the root directory on the SD card.
thorrules said:
Hello everyone
I am unable to flash the cm10 rom on my tf300t using TWRP 2.3.3.0. Most forums i read have cwm, but I am having some other issues with cwm so i have to use TWRP. The error is status 7, see attachment below. (I have already verified and md5 is alright)
Any help or pointers are appreciated.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Please see the line assert failed: getprop("
If you are using a tf300t then your error is in your build.prop file. It does not identify your unit as such.
The file you are trying to flash is the first cm10 download for the JB bootloader. I don't believe you will be pleased with that version.
If you still want to use it you will need to edit your zip to remove the asserts!
tobdaryl said:
Please see the line assert failed: getprop("
If you are using a tf300t then your error is in your build.prop file. It does not identify your unit as such.
The file you are trying to flash is the first cm10 download for the JB bootloader. I don't believe you will be pleased with that version.
If you still want to use it you will need to edit your zip to remove the asserts!
Click to expand...
Click to collapse
Why do you say I would not be pleased with that version? As per http://get.cm/?device=tf300t it seems to have been released on 13-Nov. I was looking for a stable CM10 and that is the most stable I found. Also why does it not identify my unit? Is that an issue with the TWRP? FYI -- TWRP was the first recovery I had flashed, but since it gave status 7 error, I flashed CWM. CWM gave me some MBR signature errors, and it was completely useless, since it would not even take backup of my ROM, so I again moved back to TWRP. Thanks by the way.
mike-y said:
the screenshot says no MD5 file is found. Not saying that is your issue, but just an observation since you said you checked it.
Also, it appears the zip file is inside a directory? try moving it to the root of the SD card. sometimes the paths for various functions of the flash assume that you are operating out of the root directory on the SD card.
Click to expand...
Click to collapse
Actually I had verified MD5 when I downloaded it on the phone (using FileManager app). I will try moving to the root directory, but I feel like that is not the issue. Thank you for your response.
thorrules said:
Why do you say I would not be pleased with that version? As per http://get.cm/?device=tf300t it seems to have been released on 13-Nov. I was looking for a stable CM10 and that is the most stable I found. Also why does it not identify my unit? Is that an issue with the TWRP? FYI -- TWRP was the first recovery I had flashed, but since it gave status 7 error, I flashed CWM. CWM gave me some MBR signature errors, and it was completely useless, since it would not even take backup of my ROM, so I again moved back to TWRP. Thanks by the way.
Actually I had verified MD5 when I downloaded it on the phone (using FileManager app). I will try moving to the root directory, but I feel like that is not the issue. Thank you for your response.
Click to expand...
Click to collapse
That cm10 was released prior to the first cm10 nightly. If I remember correctly it didn't support gps and may not have supported wifi. It was placed in stable because it couldn't be released in nightlies at that point.
The md5 failure is normal if you don't have a properly named md5 file in the same directory as the zip and have the option set to use it.
tobdaryl said:
That cm10 was released prior to the first cm10 nightly. If I remember correctly it didn't support gps and may not have supported wifi. It was placed in stable because it couldn't be released in nightlies at that point.
The md5 failure is normal if you don't have a properly named md5 file in the same directory as the zip and have the option set to use it.
Click to expand...
Click to collapse
Thanks. So I guess that CM10 was not useful to me anyway, I was looking for a stable and complete ROM. I think I will then try something else, maybe superclean, have read that it is stable too. Personally I do not like stock, instead prefer AOKP or CMs but I guess I have no choice then. Any other ROM that you had recommend? (stable + complete)?
About md5, thanks for that, I wasnt really worried about md5, since I had verified it already (before flashing).
thorrules said:
Thanks. So I guess that CM10 was not useful to me anyway, I was looking for a stable and complete ROM. I think I will then try something else, maybe superclean, have read that it is stable too. Personally I do not like stock, instead prefer AOKP or CMs but I guess I have no choice then. Any other ROM that you had recommend? (stable + complete)?
About md5, thanks for that, I wasnt really worried about md5, since I had verified it already (before flashing).
Click to expand...
Click to collapse
I know it says nightly but the recent cm10.1 releases are stable and everything I have used works properly. I don't have a dock so I can't address that. It is a good daily driver for my use.
Some people are bothered by having a 0 directory on the internal sdcard for the first user. Yes it is multi-user. Android 4.2.
tobdaryl said:
I know it says nightly but the recent cm10.1 releases are stable and everything I have used works properly. I don't have a dock so I can't address that. It is a good daily driver for my use.
Some people are bothered by having a 0 directory on the internal sdcard for the first user. Yes it is multi-user. Android 4.2.
Click to expand...
Click to collapse
I dont use a dock either, so that should work for me. I have never tried 4.2 ROM, will look for more details (esp the multi-user thingy) and then try it.
thorrules said:
I dont use a dock either, so that should work for me. I have never tried 4.2 ROM, will look for more details (esp the multi-user thingy) and then try it.
Click to expand...
Click to collapse
OK, that is the reason I mentioned 4.2 and multi-user.
Good Luck!
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
mark7807 said:
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
Click to expand...
Click to collapse
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
exad said:
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
Click to expand...
Click to collapse
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
RC1 and backup system image, vendor image, data and boot.
robocuff said:
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
Click to expand...
Click to collapse
TheBurgh said:
RC1 and backup system image, vendor image, data and boot.
Click to expand...
Click to collapse
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
mark7807 said:
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
Click to expand...
Click to collapse
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
mark7807 said:
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
Click to expand...
Click to collapse
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
TheBurgh said:
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
Click to expand...
Click to collapse
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
mark7807 said:
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
Click to expand...
Click to collapse
Not that I am aware of. Mine is rooted and backups have been smooth sailing.
I recently attempted creating a nandroid backup via TWRP on my rooted Pixel and I'm consistently getting an error: 'cannot create [path]\backup file" message from TWRP. Is there a permission issue that I've overlooked here or does anyone have any thoughts as to why my rooted Pixel would be denying TWRP authority to create the backup?
Thanks
What version of twrp ?
I only use rc1, never seen this.
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
pstgh said:
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
Click to expand...
Click to collapse
When you boot into TWRP did it ask for your unlock PIN? If it doesn't/didn't, either keep rebooting into recovery or turn the phone off and go back into recovery until TWRP does ask for your encryption PIN. Sometimes TWRP doesn't ask, and without the PIN being entered, it can't write to the internal storage.
If you click "Install" in TWRP and see a bunch of gobbledygook it's because the internal storage is still encrypted so TWRP can't do anything with it.
You could probably use USB OTG through the USB-C connector, though, to do a backup to it, if you need to.
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
pstgh said:
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
Click to expand...
Click to collapse
I can't confirm since I've yet to do a successful backup but... Flashify Pro version looks like an option???
also
Anyone know when TWRP 3.1.0-0 will be out for Pixel? Looks like it addresses boot slots which off first glance seems like quite a fundamental feature no?
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
pstgh said:
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
Click to expand...
Click to collapse
Root Explorer does have support for Google Drive. In Root Explorer touch the plus sign in the lower right corner and in the menu that opens choose Google Drive tab.
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
pstgh said:
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
Click to expand...
Click to collapse
It sounds like you've got the right idea. Cut will move the files, copy will do just that. You choose one of the two and browse to the Google Drive tab, find the folder you want to use and then use the little clipboard thing to transfer the files to that folder. If that's what you're doing, the only thing I can think of right off the top of my head would be that you don't have enough space left on Google Drive for the size of the files you're trying to transfer. Try a picture or something and see if it takes that. If so, I'd suspect lack of Drive space is the reason it fails.