I would post this on his thread but XDA won't allow me to until I get a few more posts. So, I figured I would try here. Has anybody that is using his first DataMedia build been able to update to the DataMedia build from 8/17?
I get "Can't open *****/cm-10.1-20130817-UNOFFICIAL-tenderloin_DATAMEDIA.zip(bad)" then "Installation aborted".
Same thing on 2 different TouchPads. Do I need to rerun the whole DataMedia process?
Sent from my SCH-I535 using Tapatalk 4
Just realized this should probably have posted in the Help/Q&A section. If possible, could a Mod please move it? Thanks.
Sent from my SCH-I535 using Tapatalk 4
After digging some more, when trying to view the contents of the zip using ES File Explorer, I get "Central Directory Entry not found." My guess is this is just a bad upload.
Sent from my TouchPad using Tapatalk 4
Or a bad download, download it on your computer (again) and re-check.
daedric said:
Or a bad download, download it on your computer (again) and re-check.
Click to expand...
Click to collapse
Yeah, I figured that. But I downloaded it on my computer, 2 TouchPads, and my phone. Same results every time.
Sent from my TouchPad using Tapatalk 4
No CWM recovery option moboot 0.38
Hi,
I have installed following:
Fresh intsall, repeated first with ACMEuninstall and ACMEinstall3
update-gapps-jb-20130812-signed.zip (tried also with update-gapps-jb-20130301-signed.zip)
moboot_038-tenderloin.zip
update-CWM6_tenderloin-20121215.zip
cm-10.1-20130825-UNOFFICIAL-tenderloin.zip
I have two problems:
- reboot looping -- Some other posts mentioned did work installing ROM and gaqps via CWM Recovery option.
- At bootup menu, there is no CWM recovery option
Thanks for any help
timothy_k said:
Hi,
I have installed following:
Fresh intsall, repeated first with ACMEuninstall and ACMEinstall3
update-gapps-jb-20130812-signed.zip (tried also with update-gapps-jb-20130301-signed.zip)
moboot_038-tenderloin.zip
update-CWM6_tenderloin-20121215.zip
cm-10.1-20130825-UNOFFICIAL-tenderloin.zip
I have two problems:
- reboot looping -- Some other posts mentioned did work installing ROM and gaqps via CWM Recovery option.
- At bootup menu, there is no CWM recovery option
Thanks for any help
Click to expand...
Click to collapse
=======
GOT IT - At boot up - boot Menu, there is an option "boot ClockworkMod" <---- is CWM Recovery
---------- Post added at 10:47 PM ---------- Previous post was at 10:40 PM ----------
timothy_k said:
=======
GOT IT - At boot up - boot Menu, there is an option "boot ClockworkMod" <---- is CWM Recovery
Click to expand...
Click to collapse
================
After boot in to CWM, Perform Wipe (there are two Wipe options), then select install from SD, browse the ROM image file and install it, and then install update-gapps-jb-20130812-signed.zip - No need to reboot in between. After done installing then Reboot . It works
What exactly is the DataMedia that Ive been hearing about? I have the 8/18 version installed and so far so good.
It shrinks the portion of the TP memory that WebOS needs to run. Then combines the data and media partitions so they share the same pot of storage. It allows for the user to install more apps. Nexus devices use this memory strategy. That's the basics of it. I am sure somebody, much smarter than I, can explain in more technical detail.
Sent from my SCH-I535 using Tapatalk 4
sindizzy said:
I have the 8/18 version installed and so far so good.
Click to expand...
Click to collapse
Do you mean the 8/17 version? Did you follow all the instructions in Milaq's thread?
Sent from my SCH-I535 using Tapatalk 4
I am also use the data media but now I want to return back! how can do that?
thanks
Related
I am getting this error while taking a nandroid backup using CWM 5.0.2.6 ''error while making a backup image of /system" on Jelly Blast v3.0.4.
I have 6793 mb free space on sd card so i don't think that free space is a problem. What's going wrong? How do I fix this?
I don't no why ur getting this error
I used this to backup my stock rom and it work try it it might work for u as wellll
http://forum.xda-developers.com/showthread.php?t=2068619
Sent from my GT-S5830i using xda premium
---------- Post added at 11:20 AM ---------- Previous post was at 11:19 AM ----------
Credits:Android now for making it compatible with our device
Works very well for me
Sent from my GT-S5830i using xda premium
rahulnandwani said:
I don't no why ur getting this error
I used this to backup my stock rom and it work try it it might work for u as wellll
http://forum.xda-developers.com/showthread.php?t=2068619
Sent from my GT-S5830i using xda premium
---------- Post added at 11:20 AM ---------- Previous post was at 11:19 AM ----------
Credits:Android now for making it compatible with our device
Works very well for me
Sent from my GT-S5830i using xda premium
Click to expand...
Click to collapse
Well actually he has just shared it and nothing else
You could thank him anyway for sharing
iamareebjamal said:
Well actually he has just shared it and nothing else
You could thank him anyway for sharing
Click to expand...
Click to collapse
Sooo...........
Sent from my GT-S5830i using xda premium
That method also didn't work. Just gets stuck on backing up system 98%. Moreover, even if it would have worked i wanted to know that why normal backup was not working.
Anyways.. while backing up in recovery i noticed that same files are being backed up i.e. names of files/.apks repeating again and again till it gives me the error i mentioned in the first post. And using the above mentioned method while it gets stuck on 98% the filesize of system backup keeps on increasing.. reached around 1.6 gb before i cancelled the process. So, i guess the same happens while backing through recovery and when the card runs out of memory i get that error. Any idea about the problem..?
Sent from my GT-S5830i using Tapatalk 2
oyşş amuga koyam
I think i have the answer
iamashank said:
That method also didn't work. Just gets stuck on backing up system 98%. Moreover, even if it would have worked i wanted to know that why normal backup was not working.
Anyways.. while backing up in recovery i noticed that same files are being backed up i.e. names of files/.apks repeating again and again till it gives me the error i mentioned in the first post. And using the above mentioned method while it gets stuck on 98% the filesize of system backup keeps on increasing.. reached around 1.6 gb before i cancelled the process. So, i guess the same happens while backing through recovery and when the card runs out of memory i get that error. Any idea about the problem..?
Sent from my GT-S5830i using Tapatalk 2
Click to expand...
Click to collapse
Connect your phone to your PC
Go to my computer
Right click on your phones SD and select properties
Go to Tools
Use Error checking " Check the Device for errors "
Check both tick boxes
I think your problem is your phone is attempting to write to a damaged
data block on your SD card, which is what causes the Backup to fail,
this should fix the data block (if any errors are on it)
-Goodluck
kostheback said:
oyşş amuga koyam
Click to expand...
Click to collapse
Use ENGLISH please.
I flashed stock rom using odin and now i am able to take backups. But the great thing is that CWM is not able to restore any backups. I took one backup before i had this problem, i am not able to restore that backup too. Its just says something like error in flashing boot image.. What's going on?
EDIT:
I can restore data,system,cache and sd-ext through advance restore. Only restoring boot image is causing problem. And as a result restore fails. What could be the problem. Tried flashing stock rom again and creating a fresh backup, still the same error.
This might answer it.
I have the same issue and while digging some answers, found following instructions on an outside link, couldn't post the link, so here is the post:
How to create a nandroid backup using CWM guide
This guide will instruct on how to create a nandroid using cwm
a couple of things first:
1. Nandroid simply backs up system and data. it does NOT back up your kernel or modem.
2. For the reasons in note 1, you can only recover to a nandroid on the same build as the one you are on (EC07 - ECO7, EC03 - EC03, and DL17 - DL17). If you try to back up to an EC03 nandroid from an EC07 build, you will softbrick until you flash the proper kernel.
Also, this guide assumes that you are already rooted, and have CWM working on your phone. If not, there are a couple of guides to get you here.
What you need:
Nothing that you don't already have.
What to do:
1. reboot int recovery by powering down, then power back on holding vol up, vol down, and power at the same time. This will boot you into stock recovery.
2. using volume down, highlight 'apply sdcard:update.zip' and select by using the menu button (or where it would be).
3. you should now be in cwm recovery. Depending on which one you are using, the text will either be red or cyan in color. highlight 'backup/restore' using volume keys and select with POWER button.
4. select backup
The back up will start, and will take around 5-10 minutes to complete (depending on how much stuff you have in /data)
5. Once it is done, it will go back to the main cwm menu. Select 'reboot phone now' with power button.
you are done.
This is pretty simple and innocuous. But, as always, ask before you start.
i fixed this by choosing backup to sd card
same problem
I had the same error message when i was doing a nandroid from recovery but when i switch to ext sd as destination worked like a charm in my
GS4 tmo
What is this?
Boot Menu S is a bootstraped recovery.
Bootstraped means that it installs itself in the system partition and
hijacks Androids boot process. This means that it will not protect
your device if you screw up you stock system. Therefore it supports
up to four rom-slots. A rom-slot is stored on your internal storage
and holds one rom. When you flash something to a rom slot it will
not touch your stock system partition and therefore protects you
from a brick.
How do I use this?
Install the app https://play.google.com/store/apps/details?id=se.pajn.bms.manager
Open the app and install the recovery.
Reboot to the recovery.
If you want to enter the recovery during boot hold volume down until the boot animation hungs.
REMEMBER TO NEVER FLASH, WIPE OR RESTORE SOMETHING
TO YOUR STOCK SYSTEM, IT MAY BRICK YOUR DEVICE.
Thanks to
Hashcode and STS dev team for writing Safestrap
TeamWin for writing TWRP
And Developers and Skrilax_CZ for writing 2nd-init
As always you are fully responsible for your device if you brick your device
using this you are on your own. I nor anyone else take any responsibility
for what you do with your device.
Reserved
wow, apparently something good is going on here theoretically via some changes should be also available for 1st tab S users ?
What about s1, buddy?
Sent from my Sony Tablet S using xda app-developers app
So we can start getting some custom roms up in this thread list?!?
Sent from my SGPT12 using Tapatalk 4 Beta
condi said:
wow, apparently something good is going on here theoretically via some changes should be also available for 1st tab S users ?
Click to expand...
Click to collapse
I can't promise anything but I espect so yes. @smgdev here have sent me some device information so I hope that it should be possible. I will start doing some real work towards STS now.
Sent from my XT910 using Tapatalk 4 Beta
See this is where im confused the is no imne number for the device therefore no way to complie or am I totally wrong
What I am intrested in is kernal and radio flashes to the oem software like doomloord but the real shame about the tablet is the sligly aggressive battery "saving" ints in the kernal that are there like the ever present wifi issue ive always found frustrating buttery smooth yes once my wifi kicks in then I can say hold on while I disable and renable the wifi because reuter is going nuts with the constant disconnects and starts a new cache every time it reconnects to it thus filling up its memory ram? And then it causes problems its not a laptop so I dont see why I was given to viao to build hard ware they knew little about and a software system even less ha ha
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
pajn said:
I can't promise anything but I espect so yes. @smgdev here have sent me some device information so I hope that it should be possible. I will start doing some real work towards STS now.
Sent from my XT910 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Awesome, if you use the uninstall option will it boot to the stock recovery like nothing happened?
Sent from my Sony Tablet S using xda premium
pajn said:
I can't promise anything but I espect so yes. @smgdev here have sent me some device information so I hope that it should be possible. I will start doing some real work towards STS now.
Sent from my XT910 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Can you post the apk? And did you use the twrp recovery from the original safestrap?
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
Can you post the apk? And did you use the twrp recovery from the original safestrap?
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
I do want the apk BUT it is a major risk since XTS and the STS are different in a few ways like the bootloader, hardware, system, 2nd init and such so we may have to wait until it is supported.
Sent from my Nexus 4 using xda app-developers app
dex9mm said:
See this is where im confused the is no imne number for the device therefore no way to complie or am I totally wrong
What I am intrested in is kernal and radio flashes to the oem software like doomloord but the real shame about the tablet is the sligly aggressive battery "saving" ints in the kernal that are there like the ever present wifi issue ive always found frustrating buttery smooth yes once my wifi kicks in then I can say hold on while I disable and renable the wifi because reuter is going nuts with the constant disconnects and starts a new cache every time it reconnects to it thus filling up its memory ram? And then it causes problems its not a laptop so I dont see why I was given to viao to build hard ware they knew little about and a software system even less ha ha
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
You can compile the kernel but you can't boot it as we have a locked bootloader, it's solvable with kexec which I have looked into a bit however the kernel is a mess so I don't relay know where to start. But it would be nice to have. With kexec and 2nd-init we have fully worked around the locked bootloader problem.
andyabc said:
Awesome, if you use the uninstall option will it boot to the stock recovery like nothing happened?
Click to expand...
Click to collapse
You can always access the stock recovery because that one is started from the bootloader where a bootstraped recovery is started from the system. What happens when you press uninstall is that it removes every file that is installed in the system partition and restores the hijack binary (currently logwrapper but I will start searching for a new one as Sony starts logwrapper very late (usually it's one of the first things to start as the mounting of the system, user and cache partitions usually are wrapped with logwrapper)).
smgdev said:
Can you post the apk? And did you use the twrp recovery from the original safestrap?
Click to expand...
Click to collapse
Ofcourse. However I don't relay know what you want to use it for. The recovery is just included as a binary so the APK doesn't realy reveal much. Is there anything special that you are searching for?
If you use the current APK on the STS there is a big risk of bricking. I will send you a test build for STS as soon as possible if you don't mind doing some testing, else I have to find someone else.
View attachment BootMenuS.apk
The recovery is TWRP however it isn't exactly the same as in the real safestrap builds because I couldn't compile the master branch of safestrap (probably some configuration error but the error I got from make wasn't very helpful so...) so I used a branch with a later version of TWRP and because TWRP had some big changes in its PartitionManager I had to rework most of the rom slot code.
I will post the full source on Github later.
wow great news !
Thanks so much! Lets see if something magical happens!
Cheers
Vatis
pajn said:
You can compile the kernel but you can't boot it as we have a locked bootloader, it's solvable with kexec which I have looked into a bit however the kernel is a mess so I don't relay know where to start. But it would be nice to have. With kexec and 2nd-init we have fully worked around the locked bootloader problem.
You can always access the stock recovery because that one is started from the bootloader where a bootstraped recovery is started from the system. What happens when you press uninstall is that it removes every file that is installed in the system partition and restores the hijack binary (currently logwrapper but I will start searching for a new one as Sony starts logwrapper very late (usually it's one of the first things to start as the mounting of the system, user and cache partitions usually are wrapped with logwrapper)).
Ofcourse. However I don't relay know what you want to use it for. The recovery is just included as a binary so the APK doesn't realy reveal much. Is there anything special that you are searching for?
If you use the current APK on the STS there is a big risk of bricking. I will send you a test build for STS as soon as possible if you don't mind doing some testing, else I have to find someone else.
View attachment 2083568
The recovery is TWRP however it isn't exactly the same as in the real safestrap builds because I couldn't compile the master branch of safestrap (probably some configuration error but the error I got from make wasn't very helpful so...) so I used a branch with a later version of TWRP and because TWRP had some big changes in its PartitionManager I had to rework most of the rom slot code.
I will post the full source on Github later.
Click to expand...
Click to collapse
I can also help out with testing!
Plays2 said:
I can also help out with testing!
Click to expand...
Click to collapse
Plus me
HOX+Viperx+Alex(V) = revolution
Okey, I post here the version I sent to smgdev in private.
Remember that this is a completely untested version, I have never even seen a STS IRL. It's only based on information smgdev sent and while that info were good there is still some possibility that something isn't right at the first try.
This version doesn't include any hijack and is therefore not modifying any existing files, only adding, so it shouldn't create a brick however as always: nothing can be guaranteed. Also there is risk that the recovery isn't correctly configured and can cause problem so please follow the protocol if you aren’t absolutely sure of what you are doing.
APK: http://ge.tt/3lBh0nk/v/0
Install the app.
On the install screen make sure that it says Device: STS in the top right corner, if it doesn't: abort!
Install the recovery.
Open adb shell and run
Code:
su
reboot-recovery
In the recovery:
Go to backup and make sure that it says the correct free space of your internal storage. If it doesn't: abort!
Do a backup.
Go to mounts and mount system
Go to advanced>file manager and check that /system contains your stock system.
Go to boot options>rom slot 1 and make sure that it says the correct free space of your internal storage. If it doesn't: abort!
Create the slot.
Go to mounts and mount system
Go to advanced>file manager and check that /system only contains lost+found. If it contains your stock system: abort!
Restore your backup
Go to mounts and mount system
Go to advanced>file manager and check that /system contains your stock system (well, the backup of it).
Go to boot options>rom slot 2 and create it
Go to mounts and mount system
Go to advanced>file manager and check that /system only contains lost+found.
Try to delete one rom slot
That should cover most things.
When I run reboot-recovery I get
"Cp can't stat '/system/etc/safestrap/bbx no such file or directory
Unable to chmod /sbin/bbx no such file or directory and a whole bunch of the same line "/system/bin/reboot-recovery[19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 31, 32,35,38,41,42,43,44,45,46,47,48,49,50,51,53] /sbin/bbx not found"
And finally,
"/system/bin/reboot-recovery[55] /sbin/hijack.killall not found
/system/bin/reboot-recovery[57] /sbin/taskset: not found
/system/bin/reboot-recovery[58] /sbin/bbx not found
/system/bin/reboot-recovery[59] /sbin/taskset not found"
Sent from my SGH-I747 using Tapatalk 4 Beta
Plays2 said:
When I run reboot-recovery I get
"Cp can't stat '/system/etc/safestrap/bbx no such file or directory
Unable to chmod /sbin/bbx no such file or directory and a whole bunch of the same line "/system/bin/reboot-recovery[19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 31, 32,35,38,41,42,43,44,45,46,47,48,49,50,51,53] /sbin/bbx not found"
And finally,
"/system/bin/reboot-recovery[55] /sbin/hijack.killall not found
/system/bin/reboot-recovery[57] /sbin/taskset: not found
/system/bin/reboot-recovery[58] /sbin/bbx not found
/system/bin/reboot-recovery[59] /sbin/taskset not found"
Sent from my SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Such a stupid misstake. I will fix it when I get home.
Sent from my XT910 using Tapatalk 4 Beta
pajn said:
Such a stupid misstake. I will fix it when I get home.
Sent from my XT910 using Tapatalk 4 Beta
Click to expand...
Click to collapse
No worries, Thanks!
Sent from my Sony Tablet S using Tapatalk HD
Plays2 said:
No worries, Thanks!
Sent from my Sony Tablet S using Tapatalk HD
Click to expand...
Click to collapse
So, also checked the other files and they seemed good, however always hard to tell.
pajn said:
So, also checked the other files and they seemed good, however always hard to tell.
Click to expand...
Click to collapse
I'm still getting the same error...
It says status:installedv0.8 but those same files are still missing
Sent from my SGH-I747 using Tapatalk 4 Beta
I tried to flash Andybones Stock ME7 Rooted build as to make a nandroid of it right after. I did nandroid before as well. I wiped cache, delv, and data over 6 times. Stuck on white Samsung Galaxy s4 boot screen , I can get into odin. Please help :'( is my phone now a brick?
stang5litre said:
I tried to flash Andybones Stock ME7 Rooted build as to make a nandroid of it right after. I did nandroid before as well. I wiped cache, delv, and data over 6 times. Stuck on white Samsung Galaxy s4 boot screen , I can get into odin. Please help :'( is my phone now a brick?
Click to expand...
Click to collapse
No just chill. Can you get back into recovery? Hold vol up + power while booting
Sent from my SCH-I545 using xda app-developers app
Surge1223 said:
No just chill. Can you get back into recovery? Hold vol up + power while booting
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Hey Yep that worked as far as recovery goes. Thanks so much for that. I know you said you sd card was formated as extFAT. What should I try as far as trying to get that Rom on there? Flash like you said and wipe after and fix permissions? Never had a Rom fail to install sorry for all the questions just wanting to make sure I do this right. Thanks so much for all you help(need that apps to sd feature.) Can't download folder mount insufficient storage even when I delete apps. Thanks again Tried getting in contact with Andy as he put this rom together but no luck on that front yet I am sure he is super busy doing Roms. Also you said that TWRP version I had was probably the reason, it looks like the latest version? Sorry if this is a dumb question used to Clockwork Mod and 4EXT. (TWRPV2.6.0.0 what i have installed)
stang5litre said:
Hey Yep that worked as far as recovery goes. Thanks so much for that. I know you said you sd card was formated as extFAT. What should I try as far as trying to get that Rom on there? Flash like you said and wipe after and fix permissions? Never had a Rom fail to install sorry for all the questions just wanting to make sure I do this right. Thanks so much for all you help(need that apps to sd feature.) Can't download folder mount insufficient storage even when I delete apps. Thanks again Tried getting in contact with Andy as he put this rom together but no luck on that front yet I am sure he is super busy doing Roms. Also you said that TWRP version I had was probably the reason, it looks like the latest version? Sorry if this is a dumb question used to Clockwork Mod and 4EXT. (TWRPV2.6.0.0 what i have installed)
Click to expand...
Click to collapse
Here http://forum.xda-developers.com/showthread.php?p=45452309 are some I posted twrp 2.5.0.2 is what I prefer
Sent from my SCH-I545 using xda app-developers app
Surge1223 said:
Here http://forum.xda-developers.com/showthread.php?p=45452309 are some I posted twrp 2.5.0.2 is what I prefer
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
So do it the same way just with the other version of TWRP? Doing this do I just get that version and rewrite script? Will this keep my other back up as well? Thanks for your help.
stang5litre said:
So do it the same way just with the other version of TWRP? Doing this do I just get that version and rewrite script? Will this keep my other back up as well? Thanks for your help.
Click to expand...
Click to collapse
Just flash any of the zipped recoveries except Twrp 2.6.0.0. You should be able to restore the nandroids you made if you choose to use twrp 2.5.0.2.
*First check the md5 of whatever rom your going to flash. Then follow these steps.*
1. Format system, data, cache and dalvik cache
2. Flash rom.
3. If rom contains firmware update (i.e. a new kernel, or modem etc. ) then fix permissions.
4. Reboot
Sent from my SCH-I545 using xda app-developers app
Thanks!!!
Surge1223 said:
Just flash any of the zipped recoveries except Twrp 2.6.0.0. You should be able to restore the nandroids you made if you choose to use twrp 2.5.0.2.
*First check the md5 of whatever rom your going to flash. Then follow these steps.*
1. Format system, data, cache and dalvik cache
2. Flash rom.
3. If rom contains firmware update (i.e. a new kernel, or modem etc. ) then fix permissions.
4. Reboot
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Yes I am going to use 2.5.0.2 thanks to you Do I leave goo manager on? Formatting my sd card to extFAT again just to make sure... as i am typing this. And I will download the whole file again just in case it was corrupt and go through your steps. Will let you know. Thanks for all your help. Really means a lot Thanks for taking the time to help me out was up all last night.
MD5 Mismatch
Surge1223 said:
Just flash any of the zipped recoveries except Twrp 2.6.0.0. You should be able to restore the nandroids you made if you choose to use twrp 2.5.0.2.
*First check the md5 of whatever rom your going to flash. Then follow these steps.*
1. Format system, data, cache and dalvik cache
2. Flash rom.
3. If rom contains firmware update (i.e. a new kernel, or modem etc. ) then fix permissions.
4. Reboot
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I downloaded a MD5 checker and they are not the same. What is suggested in this scenario? Please see attached. I have stopped at this point. So I don't mess anything up
stang5litre said:
I downloaded a MD5 checker and they are not the same. What is suggested in this scenario? Please see attached. I have stopped at this point. So I don't mess anything up
Click to expand...
Click to collapse
Thats the md5 of a data partition from a backup. I meant check the md5 of whatever rom you were going to flash. Don't worry about the md5 of your nandroids for now.
Surge1223 said:
Thats the md5 of a data partition from a backup. I meant check the md5 of whatever rom you were going to flash. Don't worry about the md5 of your nandroids for now.
Click to expand...
Click to collapse
Won't wiping your system un root your phone? at the wipe screen now
stang5litre said:
Won't wiping your system un root your phone? at the wipe screen now
Click to expand...
Click to collapse
wiped all still says fail...
had to change out my memory card and it did same method and it worked. My other memory card is format fat32 and the 64 is extFAT is there a way to get my phone to read that? when i insert it it says damaged or format. I have formatted it 3 times. Works in computer not in phone. I can mount it after and you can use it but I could not flash a rom from it.
stang5litre said:
Won't wiping your system un root your phone? at the wipe screen now
Click to expand...
Click to collapse
Okay, let me rephrase that. Read the directions posted by the developer of whatever rom your to flash. If there aren't any instructions, you shoudl post asking the dev. But if you know what your doing you're going to be ok, in general only wipe the system parition if you know the rom that you're installing is already pre-rooted. You mentioned you wanted to install the stock root deodex VRUAME7 rom made by andybones. That rom is pre-rooted. Just don't install an OTA.
---------- Post added at 11:34 PM ---------- Previous post was at 11:10 PM ----------
stang5litre said:
wiped all still says fail...
Click to expand...
Click to collapse
Where does it say fail at? What does the message say? Put the rom on your sdcard instead. If not then go to advanced>>copy log to sdcard then send it to me.
Surge1223 said:
Okay, let me rephrase that. Read the directions posted by the developer of whatever rom your to flash. If there aren't any instructions, you shoudl post asking the dev. But if you know what your doing you're going to be ok, in general only wipe the system parition if you know the rom that you're installing is already pre-rooted. You mentioned you wanted to install the stock root deodex VRUAME7 rom made by andybones. That rom is pre-rooted. Just don't install an OTA.
---------- Post added at 11:34 PM ---------- Previous post was at 11:10 PM ----------
Where does it say fail at? What does the message say? Put the rom on your sdcard instead. If not then go to advanced>>copy log to sdcard then send it to me.
Click to expand...
Click to collapse
Got the rom installed had to change the card out to my old card which is fat32 not extFAT. As soon as I did that it flashed with no problems. Thanks for all your help. Question though I have a 64gb sdhc card that is formatted in extFAT but the phone picks it up as damaged but you can look under storage and mount it and it will show 64gb.... this was also the case last night when I was trying to install the rom. I have seen a lot of people saying the s4 is having problems reading extFAT so I was gonna format it to fat32 but when I do I lose half of the 64gb card. Do you know of any solutions for this? I would rather have extFAT for bigger file transfer but at this point I just want 64gb of storage lol. Thanks again for answering all my questions these last few days.
stang5litre said:
Got the rom installed had to change the card out to my old card which is fat32 not extFAT. As soon as I did that it flashed with no problems. Thanks for all your help. Question though I have a 64gb sdhc card that is formatted in extFAT but the phone picks it up as damaged but you can look under storage and mount it and it will show 64gb.... this was also the case last night when I was trying to install the rom. I have seen a lot of people saying the s4 is having problems reading extFAT so I was gonna format it to fat32 but when I do I lose half of the 64gb card. Do you know of any solutions for this? I would rather have extFAT for bigger file transfer but at this point I just want 64gb of storage lol. Thanks again for answering all my questions these last few days.
Click to expand...
Click to collapse
Yeah I dont let windows ever see my exfat card. Mines exfat and works but I formatted it in linux. I dont know how well you know how to use linux...but pm me if you need help
Sent from my SCH-I545 using xda app-developers app
I've uploaded a backup of the stock (rooted) system here: https://www.mediafire.com/?wr9f2n41ig4o8qb
And this is the link to the stock (unrooted) system here: https://www.mediafire.com/?p7iabx8g90exe14
Feel free to get flash happy now that a stock backup exists! To use it, first create a backup (of boot to make it quick) in TWRP, then copy and paste the zip's contents into the folder it creates. It'll have a TWRP/Backups/gibberish/ and in the next folder a list of your backups. If I missed anything let me know. I'll upload the unrooted backup sometime later this week. I used this to restore my defective one to complete stock.
EDIT: To restore system to full stock... (Uninstalled apps, no root, etc)
1) Install TWRP as per here: http://forum.xda-developers.com/showthread.php?t=2790542
2) In TWRP, create a backup of your boot partition
3) Reboot
4) Copy the folder in this zip to the folder in TWRP/Backups/SERIALNUMBER (you'll see another dated backup there)
5) Reboot into TWRP again
6) Restore this backup, then flash or install SuperSU
7) Reboot into Android and download this stock recovery image to its storage: https://builds.casual-dev.com/files...ery-dd-pull-15jun14-KOT49H-build201405027.img
8) Run this command (courtesy of Adam Outler) from a terminal emulator, or adb shell (replace STOCKrecovery.img with the name of your stock recovery file):
AdamOutler said:
su -c 'dd if=/sdcard/STOCKrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
Click to expand...
Click to collapse
9) When it reboots, do NOT factory wipe. Just verify the stock recovery is there. Reboot into Android
10) Use SuperSU's "Uninstall Root" option to completely unroot. DONE!
OPTIONAL: 11) Reboot to recovery, factory reset (if sending to factory!)
I messed up by phone app by trying to remove at&t contacts app and haven't been able to call since. Thanx bro
Glad to help! OP Updated with instructions!
Updated with stock (unrooted) as well!
Can you Please provide new links to the recovery files so I may download them trying to get all files before I decide to buy device been wait for long time for them to be posted
rboone18 said:
Can you Please provide new links to the recovery files so I may download them trying to get all files before I decide to buy device been wait for long time for them to be posted
Click to expand...
Click to collapse
The stock backups, or the recovery images in Adam Outler's thread? My links should still work
Sent from my ASUS PadFone X using XDA Free mobile app
Recovery images please
rboone18 said:
Recovery images please
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2790542
This thread.
Sent from my ASUS PadFone X using XDA Free mobile app
I get webpage not available when trying to download twrp or stock recovery
rboone18 said:
I get webpage not available when trying to download twrp or stock recovery
Click to expand...
Click to collapse
I'll upload them to MediaFire tonight
Sent from my ASUS PadFone X using XDA Free mobile app
Thanks
rboone18 said:
Thanks
Click to expand...
Click to collapse
I am sorry. I don't seem to ahve the TWRP recovery image anywhere on hand. Just the stock recovery pull. I see what you mean, now- his site IS down. Here's the link to stock.
https://www.mediafire.com/?16g1t1n1kcty6w6
If I find TWRP, I will certainly let you know. There's not much you can do with this device and TWRP right now besides make and restore nandroids (which, admittedly, is pretty damn critical).
Well, as soon I have access to all files and what steps that I have to do to restore back to factory then I was thinking I was going to go look at it in the store and buy one but I would never buy one without the ability to restore to factory .
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
I root everything and thank you for all efforts , hope to talk to you again when I able to get all the files. I will download stock recovery tonight. Thanks
DUDE...you might be my hero....
However for some reason when I connect my phone to my PC, it didn't show up. It has TWRP and no operating system. Wonder if it's a Windows 8.1 thing?
zackzuse said:
DUDE...you might be my hero....
However for some reason when I connect my phone to my PC, it didn't show up. It has TWRP and no operating system. Wonder if it's a Windows 8.1 thing?
Click to expand...
Click to collapse
That, I have no solution for. Do you have an OTG cable?
Sent from my ASUS PadFone X using XDA Free mobile app
dibblebill said:
That, I have no solution for. Do you have an OTG cable?
Sent from my ASUS PadFone X using XDA Free mobile app
Click to expand...
Click to collapse
Yes. I'll try that then can also try on Win7.... I guess if not this than a warranty claim...
---------- Post added at 02:21 AM ---------- Previous post was at 01:56 AM ----------
dibblebill said:
That, I have no solution for. Do you have an OTG cable?
Sent from my ASUS PadFone X using XDA Free mobile app
Click to expand...
Click to collapse
My phone dosnt seem to see the files on the USB with the OTG cable:crying:
zackzuse said:
Yes. I'll try that then can also try on Win7.... I guess if not this than a warranty claim...
---------- Post added at 02:21 AM ---------- Previous post was at 01:56 AM ----------
My phone dosnt seem to see the files on the USB with the OTG cable:crying:
Click to expand...
Click to collapse
Dang. I hadn't tested it. It IS heavily dependent on the cable being used, though- I'll say that.
dibblebill said:
I've uploaded a backup of the stock (rooted) system here: https://www.mediafire.com/?wr9f2n41ig4o8qb
And this is the link to the stock (unrooted) system here: https://www.mediafire.com/?p7iabx8g90exe14
Feel free to get flash happy now that a stock backup exists! To use it, first create a backup (of boot to make it quick) in TWRP, then copy and paste the zip's contents into the folder it creates. It'll have a TWRP/Backups/gibberish/ and in the next folder a list of your backups. If I missed anything let me know. I'll upload the unrooted backup sometime later this week. I used this to restore my defective one to complete stock.
EDIT: To restore system to full stock... (Uninstalled apps, no root, etc)
1) Install TWRP as per here: http://forum.xda-developers.com/showthread.php?t=2790542
2) In TWRP, create a backup of your boot partition
3) Reboot
4) Copy the folder in this zip to the folder in TWRP/Backups/SERIALNUMBER (you'll see another dated backup there)
5) Reboot into TWRP again
6) Restore this backup, then flash or install SuperSU
7) Reboot into Android and download this stock recovery image to its storage: https://builds.casual-dev.com/files...ery-dd-pull-15jun14-KOT49H-build201405027.img
8) Run this command (courtesy of Adam Outler) from a terminal emulator, or adb shell (replace STOCKrecovery.img with the name of your stock recovery file):
9) When it reboots, do NOT factory wipe. Just verify the stock recovery is there. Reboot into Android
10) Use SuperSU's "Uninstall Root" option to completely unroot. DONE!
OPTIONAL: 11) Reboot to recovery, factory reset (if sending to factory!)
Click to expand...
Click to collapse
The link to stock ROM is down
FUZER384 said:
The link to stock ROM is down
Click to expand...
Click to collapse
It's working for me on my phone :S Have you tried another computer or location?
Sent from my HTC One using XDA Free mobile app
Sorry its working
Q&A for .3.2.4 Rollback Images
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for .3.2.4 Rollback Images. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
andPS2 said:
i followed the steps but not sure where it went wrong for me
step 2. that would be the 13.3.2.4_rollback for thor correct? (i have 7 inch fire hdx)
was not sure where to flash this - i used rom slot 2
that installs 13.3.0.9_user into rom slot2 (i dont understand why we still have to update to 13.3.1.0 i guess
13.3.0.9 is not vulnerable?)
following the rest of the steps and rebooting kindle fire system recovery comes up
would be nice to put a link to 13.3.1.0 stock into the OP i found it in the forum)
i did reboot kindle (didnt dare to do reset to factory defaults)
that gets me back to 13.3.0.9
retrying the steps and after reboot rebooting into safestrap i see
openrecovery script installing zip (13.3.1.0)
if i let this continue and reboot i get a flashing screen and then a black screen
what am i doing wrong
p.s. luckily i have safestrap so rom slot 1 and stock still work
Click to expand...
Click to collapse
Is the file supposed to be flashed to the stock slot or to one of the other rom slots?
TheCowGod said:
Is the file supposed to be flashed to the stock slot or to one of the other rom slots?
Click to expand...
Click to collapse
Flash it to the stock slot...
TheCowGod said:
Is the file supposed to be flashed to the stock slot or to one of the other rom slots?
Click to expand...
Click to collapse
when you do that part do not pay attention to what the firmware says it is the build.prop has been modified to allow the device to accept the update that you put on the SD card
Where can i find the 3.1.0 update download?
latedays101 said:
Where can i find the 3.1.0 update download?
Click to expand...
Click to collapse
HDX 7, thor: https://s3.amazonaws.com/kindle-fire-updates/update-kindle-13.3.1.0_user_310079820.bin
HDX 8.9, apollo: https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.1.0_user_310079820.bin
i put the 3.1.0 file in the internal storage of my HDX 7 on v 3.2.4 and when i try to initiate the update in settings, it doesn't do anything? any help is appreciated.
edit: nvm got it working, somehow my wifi was connected to some random wifi and you need to turn it off before you can do the update or so call downgrade to 3.1.0.
after I updated 3.1.0 and rebooted, the current version still states 13.3.0.9 under the device menu. Should this have changed to 13.3.1.0? I also tried to update again and received an error in the update boot.
I'm still able to boot into all my rom slots.
thanks.
Great! Thank you so much! I was able to roll back to stock 3.1.0 from nexus rom.
im on 1309 now wth rollback but no way to copy .310 file to root of sdcard lol with amazon. Ive tried to copy thru safe strap but upon reboot its not there..i turned on wifi and downloaded es explorer and mounted rw and now just get copy failed not enough space.. Im on stock with 32 gig left oi
t
Sent from my SM-N900V using XDA Premium 4 mobile app
---------- Post added at 05:26 PM ---------- Previous post was at 05:24 PM ----------
I'm rooted and have safe strap but can't copy 310 file
Sent from my SM-N900V using XDA Premium 4 mobile app
davekaz said:
im on 1309 now wth rollback but no way to copy .310 file to root of sdcard lol with amazon. Ive tried to copy thru safe strap but upon reboot its not there..i turned on wifi and downloaded es explorer and mounted rw and now just get copy failed not enough space.. Im on stock with 32 gig left oi
t
Sent from my SM-N900V using XDA Premium 4 mobile app
---------- Post added at 05:26 PM ---------- Previous post was at 05:24 PM ----------
I'm rooted and have safe strap but can't copy 310 file
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
have you gone back and checked every place you've already posted this question? And see if anybody has answered you. Something tells me if you're having problems just getting the file onto your tablet. You may not have any business doing any modifications quite yet. Unless you are all about false warranty claims.
I'm no pro but I've rooted everything I own . I only repeated problem here because other thread specified this one for problems. I was on nexus rom 2. I have no problem putting files where there supposed to go but this problem of not being able to copy bin from download folder to root of SD card is puzzling. Just wondered if anyone else is having same problem or alert me to what may wrong. Boy you like to ***** more than help maybe you should back off if you have nothing
Sent from my SM-N900V using XDA Premium 4 mobile app
davekaz said:
I'm no pro but I've rooted everything I own . I only repeated problem here because other thread specified this one for problems. I was on nexus rom 2. I have no problem putting files where there supposed to go but this problem of not being able to copy bin from download folder to root of SD card is puzzling. Just wondered if anyone else is having same problem or alert me to what may wrong. Boy you like to ***** more than help maybe you should back off if you have nothing
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you tried using adb push?
If that doesn't work, the only other thing I can think of is doing a factory reset.
Yes and I get a read only file system error. I stated this on original thread
Sent from my SM-N900V using XDA Premium 4 mobile app
---------- Post added at 04:21 AM ---------- Previous post was at 04:20 AM ----------
Thanks for your help
Sent from my SM-N900V using XDA Premium 4 mobile app
davekaz said:
Yes and I get a read only file system error. I stated this on original thread
Sent from my SM-N900V using XDA Premium 4 mobile app
---------- Post added at 04:21 AM ---------- Previous post was at 04:20 AM ----------
Thanks for your help
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
possible bad download? Have you can you move every other file around? I own 3 HDX I personally have not run into any issues as you have described. And have not read of them either.if you do not have any xposed framework installed or anything else that may cripple your system as far as frozen apps exceteraI may consider a factory reset also.
The only thing I did prior that may have caused my problem was after I got nexus rom2 running I tried to flashify twrp on 1324 and it booted to blank screen. Upon reboot safestrap came up and I booted into rom and everything was fine I thought. I was in stock rom. I was able to copy in safestrap the 310 bin file but disappeared on boot. When I adb to push file onto sdcard it comes up with read only file system error..So im stuck in 1324 rollback unable to manipulate any file.. Should of just left it alone till everything settled in the Twrp thread. Thanks for your help ..My bad Thanks again and didnt mean to attack you jim.. Ill work it out or not My stupidity..Thanks again
Sorry if it's been asked before but does it work on13.3.2.7 with necus ROM 2.0.2 installed
dave kaz said:
The only thing I did prior that may have caused my problem was after I got nexus rom2 running I tried to flashify twrp on 1324 and it booted to blank screen. Upon reboot safestrap came up and I booted into rom and everything was fine I thought. I was in stock rom. I was able to copy in safestrap the 310 bin file but disappeared on boot. When I adb to push file onto sdcard it comes up with read only file system error..So im stuck in 1324 rollback unable to manipulate any file.. Should of just left it alone till everything settled in the Twrp thread. Thanks for your help ..My bad Thanks again and didnt mean to attack you jim.. Ill work it out or not My stupidity..Thanks again
Click to expand...
Click to collapse
Can you restore a backup of stock .2.4 ? To stock slot?
jimyv said:
Can you restore a backup of stock .2.4 ? To stock slot?
Click to expand...
Click to collapse
I had nexus 2 for 5 minutes and didn't back it before trying twrp. I corrupted something and windows does not see it as before. I will work it out somehow but thanks for continuing to help.
Sent from my SM-N900V using XDA Premium 4 mobile app
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
I tried stock and nexus 143 neither boot...I'll try to wipe system and try 1324 zip
Sent from my SM-N900V using XDA Premium 4 mobile app
davekaz said:
I had nexus 2 for 5 minutes and didn't back it before trying twrp. I corrupted something and windows does not see it as before. I will work it out somehow but thanks for continuing to help.
Sent from my SM-N900V using XDA Premium 4 mobile app
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
I tried stock and nexus 143 neither boot...I'll try to wipe system and try 1324 zip
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Whatever you do
Do not wipe system! If you are still depending on safestrap ,