Hi,
Can someone do a nandroid backup of the original Singtel HTC Magic Rom? I am having some problem with my accelerometer and compass and just wanted to test if it is problem with the rom I am using or it is a hardware problem that I need to sent back for replacement.
I've tried using flashing back the stock SPL but it doesn't seem to work as well.
Thanks!
Do a search in either the sapphire it dream development forums for an accelerometer fix. I cannot find it now, will paste the link when I do.
I can't seem to find it by searching. It would be good if you can find the link for me.. Thanks a lot!
escaflo said:
I can't seem to find it by searching. It would be good if you can find the link for me.. Thanks a lot!
Click to expand...
Click to collapse
let me try to upload the original nandroid which i'd backup.
know any free upload site?
if not, i'll try upload to yousendit.com
the raw nandroid backup from singtel HTC.
https://www.yousendit.com/download/Y1Rvek9sSWhrWStGa1E9PQ
My auto-rotate/accelerometer isn't working! Not really the fault of the ROM, but here's how to fix it: Go into recovery, drop to console, "mount /data", then "rm /data/misc/akmd* /data/misc/rild*" and reboot.
From CyanogenMod thread.
My auto-rotate/accelerometer isn't working! Not really the fault of the ROM, but here's how to fix it: Go into recovery, drop to console, "mount /data", then "rm /data/misc/akmd* /data/misc/rild*" and reboot.
From CyanogenMod thread.
Thanks for the help Wysie..
Just wondering.. how to I get into console from recovery mode? I am using "fastboot boot recovery-RaV1.1.1H" to get into recovery utility. But once I get there how do I get into console? Using ADB? If ADB, what's the command?
Thanks again!
Star.. thanks for the raw backup.. Will be very useful if it is really a hardware problem..
Once in recovery, try typing:
adb shell
Else you can try:
adb shell mount -a
I may be wrong, sorry I don't have a computer to try out now.
Once in recovery, try typing:
adb shell
Else you can try:
adb shell mount -a
I may be wrong, sorry I don't have a computer to try out now.
star1977 said:
the raw nandroid backup from singtel HTC.
https://www.yousendit.com/download/Y1Rvek9sSWhrWStGa1E9PQ
Click to expand...
Click to collapse
Hey star, which recovery image are you using to recover the nandroid backup? For me, when I try to restore using Nandroid 2.1.1 using the Recovery-RaV1.1.1H it just give me an error.
And Wysie, I think I manage to do it correctly using ADB Shell.. but it is still the same, both the compass and accelerometer doesn't work.
Guess all I've to do now is to flash back the original HTC firmware and bring it back for servicing.
escaflo said:
Hey star, which recovery image are you using to recover the nandroid backup? For me, when I try to restore using Nandroid 2.1.1 using the Recovery-RaV1.1.1H it just give me an error.
And Wysie, I think I manage to do it correctly using ADB Shell.. but it is still the same, both the compass and accelerometer doesn't work.
Guess all I've to do now is to flash back the original HTC firmware and bring it back for servicing.
Click to expand...
Click to collapse
i'm using recovery-RAv1.1.1H.img
u need to unzip the file and just copy the nandroid folder over to the root of ur sdcard.
escaflo: What error are you getting? If it's a mount error, wait about 30 seconds and try again. The recovery needs time to mount the sdcard .
Wysie: It is not the mount error.. I manage to somehow get it to restore.. using the recovery in the RaV 1.0.1 rom.. *pressing the home+power button*
it is weird that the Nandroid backup there can restore.. but the nandroid in the recovery rom..
*Shrug* anyway ...I think it is back to the workshop for this HTC as the prognosis for the accelerometer and compass doesn't look good..
Thanks for all the help Wysie and Star!
Huh? Which recovery were you using before RAv? Hope you sort out your issues soon!
escaflo said:
Wysie: It is not the mount error.. I manage to somehow get it to restore.. using the recovery in the RaV 1.0.1 rom.. *pressing the home+power button*
it is weird that the Nandroid backup there can restore.. but the nandroid in the recovery rom..
*Shrug* anyway ...I think it is back to the workshop for this HTC as the prognosis for the accelerometer and compass doesn't look good..
Thanks for all the help Wysie and Star!
Click to expand...
Click to collapse
Once you boot the phone in the recovery mode you can do:
Code:
adb shell
mount -o rw /data
rm /data/misc/akmd* /data/misc/rild*
reboot
star1977 said:
the raw nandroid backup from singtel HTC.
https://www.yousendit.com/download/Y1Rvek9sSWhrWStGa1E9PQ
Click to expand...
Click to collapse
it is EXPIRED send me one.thanks. email:[email protected]
lynch1983 said:
it is EXPIRED send me one.thanks. email:[email protected]
Click to expand...
Click to collapse
hey, can i have the nandroid back up also ? need it to sent the magic for warrant, much help appriciated. [email protected]
(Singtel original Nanroid backup)
https://www.yousendit.com/transfer.php?action=batch_download&batch_id=YkxLb2VBUzhFd2Z2Wmc9PQ
Related
thanks shady for the toggles and letting me use your theme. After installing boot will take approx 3-5 mins. Update superuser from the market.
Deodexed, Rooted, Overclocked, Webtop via HDMI mod, Toggles, Zipaligned.
....Flash at your own risk....
WIPE DATA/FACTORY RESET
http://depositfiles.com/files/wk7i3b1n1 <----Stock Rooted 2.3.5
http://www.mediafire.com/?rt4v29ompo3am6s <----Alt Link 2.3.5
http://www.multiupload.com/IZVCVPRNGJ <----Alt Link 2.3.5
Good luck and let me know about any issues not already covered.
ps. voice search and maps would not deodex so get them from the market.
http://forum.xda-developers.com/showthread.php?t=1385283
^--This works for us. I cant tell you how many times this has saved me from using rsd just b/c of a bootloop.
There seems to be some confusion with overclocking, If you don't understand it please read through this thread.
http://forum.xda-developers.com/showthread.php?t=1341514
___________________________________________________________________
Stock Rooted Deodxed 2.3.6
http://depositfiles.com/files/dmi40o4qx <----2.3.6
^---This is a cwm backup. You will need to wipe data/factory reset then restore the backup. Extract zip to root of sd card
________________________________
***********MD5**************
StockRootedDeodex 2.3.5 36E1DE744C0144C70AFF4BFD624BA369 *StockRootedOcWebDeodex.zip
StockRootedDeodex 2.3.6 BA6AF46EF4A2E0904422E6F73E8893AE *236_Rooted_Deodex_Do_No_Flash.rar
[Theme's]
1.) adb push framework-res.apk /mnt/sdcard
2.) adb push SystemUI.apk /mnt/sdcard
3.) adb push Settings.apk /mnt/sdcard
4.) adb push BlurPhone.apk /mnt/sdcard
5.) adb push BlurDialer.apk /mnt/sdcard
6.) adb push GoogleQuickSearchBox.apk /mnt/sdcard
7.) su
8.) mount -o rw,remount /dev/null /system
9.) cp /sdcard/framework-res.apk /system/framework
10.) cp /sdcard/SystemUI.apk /system/app (case sensitive)
11.) cp /sdcard/Settings.apk /system/app (case sensitive)
12.)cp /sdcard/BlurPhone.apk /system/app (case sensitive)
13.)cp /sdcard/BlurDialer.apk /system/app (case sensitive)
14.)cp /sdcard/GoogleQuickSearchBox.apk /system/app (case sensitive)
15.) reboot
16.) click thanks!
http://db.tt/qd0dVE0p <--Ics/Artic
Flashable Zip http://www.multiupload.com/9ANWSIAPA9
http://db.tt/21dhrctR <--ICS
Flashable Zip http://www.multiupload.com/SN3DKIIVNI
(Ports from shadys various themes)
***Wanna be sure your not going to boot loop? Make a backup and install the cwm on boot linked above. Commands are the same in recovery omitting 5&6 instead go to mounts and mount /system***
**The first 2 pictures are from Ics/artic, The last 4 pics are from ICS***
You peronally use the unofficial atrix 2 bootstrap for flashing correct?
Awesome man. I'm gonna hide in a corner and see what happens for now, but definitely exciting news.
Jimmy273 said:
You peronally use the unofficial atrix 2 bootstrap for flashing correct?
Click to expand...
Click to collapse
Yes
Everything downloaded well and is up and running!!! BTW boot took no longer than a usual boot on mine
Could you give some clarification on some of the notification drop down toggles and what they are? What is the little sun like icon and the circle arrow icon?
Will leave feedback as more proper use comes
I would guess the sun icon is brightness control and the circle arrow is sync
Sent from my MB865 using xda premium
Flashing it right now!
Jimmy273 said:
You peronally use the unofficial atrix 2 bootstrap for flashing correct?
Click to expand...
Click to collapse
Yes sir I do.
We need some step by step on how to install this ROM.
already flashed, so far so good.
Here is what i dou need to root first)
1: go here and download Bootstrap Recovery
http://forum.xda-developers.com/showthread.php?t=1346977
2: Download the rom and put it on sd card
3: install the app and boot into recovery.
4: do a backup first
5: factory reset
6: flash the rom
7: reboot!
last thing !!!!! Flash at your own risk!!!!!!!!!!
OH almost forgot. HAPPY NEW YEAR!!!!!
Just flashed so far so good
Sent from my MB865 using xda premium
What is this overclocked to and what other changes does it have. Maybe someone thats done it can do a video demonstration on youtube.
Running great so far..awesome job..thought I was gonna have to wait months for something..on point..just came reluctantly over from a g2x due to T-Mobiles lack of sympathy for the broke...any way to get instructions on how to overclock via terminal emulator?
Sent from my MB865 using xda premium
Are we able to restore Nandroid backups successfully? I read in the other thread that .img files were not present in the Nandroid backup. Has that been resolved?
devsk said:
Are we able to restore Nandroid backups successfully? I read in the other thread that .img files were not present in the Nandroid backup. Has that been resolved?
Click to expand...
Click to collapse
Yup! You can use it like you would any other cwm.
pretty much all cwm features are working, nandroid backup, restore, flash rom, wipe......
Thanks for the ROM!
So, let's see if I understand how this works: the only thing we can't do yet without unlocking the bootloader is to install a different kernel. Everything else can be changed, right?
devsk said:
Are we able to restore Nandroid backups successfully? I read in the other thread that .img files were not present in the Nandroid backup. Has that been resolved?
Click to expand...
Click to collapse
Yup! Everything restored perfectly for me...
Sent from my MB865 using xda premium
Its telling me that its at 300-1000Mhz. I don't believe its OC'd? Otherwise, LOVING it. Thanks a ton.
Sent from my MB865 using XDA App
---------- Post added at 09:40 AM ---------- Previous post was at 09:36 AM ----------
Zoide_ said:
Thanks for the ROM!
So, let's see if I understand how this works: the only thing we can't do yet without unlocking the bootloader is to install a different kernel. Everything else can be changed, right?
Click to expand...
Click to collapse
Can't flash new radios either.
Calundle said:
Its telling me that its at 300-1000Mhz. I don't believe its OC'd? Otherwise, LOVING it. Thanks a ton.
Click to expand...
Click to collapse
I think right now its not, but the scripting is there so if you want the OC you have to do it manually via terminal emulator or ADB shell.
I've had no problems as well. Cant wait to see the OC and a theme on it BTW loving the notification toggles!!! If airplane mode was included it would be set!!!
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
hcyplr29 said:
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Couple of things...
Your backup might be corrupt if the md5 doesn't match.
or you might want to try and make sure you have the latest version of CWM installed on your phone. I read in one of the other threads that someone had an md5 mismatch problem that was solved with a newer version of CWM. I hope this helps.
hcyplr29 said:
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I had this happen to me once. Turned out the nand backup was bad....used the previous one I had made and was back in action. Had a few moments to sweat it out though. Just make sure to backup regularly and archives them.
Sent from my SAMSUNG-SGH-I727 using xda premium
same problem
i just encountered the same md5 mismatch problem. i have the lastest version of cwm but it doesnt help. i dont have previous stock roms as this was the first time i backed the rom up. any other solutions?
bshebib said:
i just encountered the same md5 mismatch problem. i have the lastest version of cwm but it doesnt help. i dont have previous stock roms as this was the first time i backed the rom up. any other solutions?
Click to expand...
Click to collapse
Disclaimer: This is just my opinion and I am not responsible if you have issues after taking my advice, etc., etc.
With that said...
Is the only issue that you can't make a backup or have you encountered other problems? Did you flash the superuser zip before making a backup? Did you try making a nadroid backup more than just once and it errored multiple times? Will the phone boot for you?
You could try to boot the phone up and reboot into recovery and try making a backup again. If all else fails you can just reflash everything back to stock and re-root. Make sure to read through all the guides very carefully and then...read them again....and when you get done with that....read them again. =)
1. Reflash stock.tar through Odin.
http://forum.xda-developers.com/showthread.php?t=1342348
2. Reflash CWM through Odin.
http://forum.xda-developers.com/showthread.php?t=1340526
3. Make a nandroid backup!!!
4. Flash SU zip.
5. Reboot
Good luck.
Presbycusis said:
Disclaimer: This is just my opinion and I am not responsible if you have issues after taking my advice, etc., etc.
With that said...
Is the only issue that you can't make a backup or have you encountered other problems? Did you flash the superuser zip before making a backup? Did you try making a nadroid backup more than just once and it errored multiple times? Will the phone boot for you?
You could try to boot the phone up and reboot into recovery and try making a backup again. If all else fails you can just reflash everything back to stock and re-root. Make sure to read through all the guides very carefully and then...read them again....and when you get done with that....read them again. =)
1. Reflash stock.tar through Odin.
http://forum.xda-developers.com/showthread.php?t=1342348
2. Reflash CWM through Odin.
http://forum.xda-developers.com/showthread.php?t=1340526
3. Make a nandroid backup!!!
4. Flash SU zip.
5. Reboot
Good luck.
Click to expand...
Click to collapse
This is exactly how I do it. I've never needed it but have always had it for emergency. Now that ICS is out I've been going back and forth from the sandwich to gingerbread because the bugs are well.......bugging me. I odin'd the leak then I backed it up after I installed cwm so I could always go back to that after testing out these other roms, cwm flashes, and even the backups of ICS, then I root. I basically have started from scratch twice and both times I went back to my backup I got the mismatch ( 2 different backups of the leak). I know its me (possibly cwm) because the cwm ics backup that's out there restores fine.
Sent from my SAMSUNG-SGH-I727 using XDA
Are you extracting on your PC? There seems to be some problems with unzips on the phone causing a mismatch
I've been using 7-zip for mine, and it works great. Extract files on the desktop, place on the external SD using USB
Got this from another forum
You can actually manually do it, and maybe get that backup fixed. Go to the backup folder /sdcard/clockworkmod/backup/*rom name (date and time usually)/
See if there is a nandroid.md5 file in there. If so, delete it, you can back it up if you want but it is busted so no point.
Next step to open adb shell or terminal emulator and type:
Code:
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery
Click to expand...
Click to collapse
Toggle signature works for me alot
Sent from my SAMSUNG-SGH-I727 using XDA
Not totally sure that I'm correct but I had made two backups on one version of cwm and then upgraded my cwm to the touch version and the two backups from the previous version wouldn't restore because of md5 mismatch. Those same two backups had worked several times perfectly on the other version of cwm as well. So I just assumed that maybe the version change had something to do with it.
Sent from a payphone at the quick-e-mart down the street from you
hcyplr29 said:
Trying to restore a stock backup in cwm. I get md5 mismatch error. Cause/solution inquiry.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
If you renamed backup directory to one w spaces... that too will give md5 err. Rename without spaces
Sent from my SAMSUNG-SGH-I727 using xda premium
Just flashed cwm touch from another recovery before trying to flash new rom zip and md5 mismatch accured...after darkwipe..dang..that was close call....think your correct with the change theory...
Sent from my SAMSUNG-SGH-I727 using XDA
Yes
yes that wass the problem. Tnk you NO spaces on backup folder name.
Tnk s
mindmajick said:
If you renamed backup directory to one w spaces... that too will give md5 err. Rename without spaces
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
hisham027 said:
You can actually manually do it, and maybe get that backup fixed. Go to the backup folder /sdcard/clockworkmod/backup/*rom name (date and time usually)/
See if there is a nandroid.md5 file in there. If so, delete it, you can back it up if you want but it is busted so no point.
Next step to open adb shell or terminal emulator and type:
Code:
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery
Click to expand...
Click to collapse
Worked perfect, thanks
adb Problem
Hey Guys,
nice tutorial. Everything worked but the adb shell itself.. I had to type all in one command. My adb shell freezed after entering the second command. Anybody knows how to fix it?
I used SiyahKernel S2-v3.4.1 and the ADB Shell in the Recovery.
funatkill said:
Hey Guys,
nice tutorial. Everything worked but the adb shell itself.. I had to type all in one command. My adb shell freezed after entering the second command. Anybody knows how to fix it?
I used SiyahKernel S2-v3.4.1 and the ADB Shell in the Recovery.
Click to expand...
Click to collapse
Isn't that for the international gs2?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
funatkill said:
Hey Guys,
nice tutorial. Everything worked but the adb shell itself.. I had to type all in one command. My adb shell freezed after entering the second command. Anybody knows how to fix it?
I used SiyahKernel S2-v3.4.1 and the ADB Shell in the Recovery.
Click to expand...
Click to collapse
Try using terminal emulator from your device
ADB Shell
Yeah, it is the international i9100, but the way to fix a broken CWM-backup is the same. I've tested an cm10 alpha and after this I wanted to restore my ICS, because of sdcard problems. So I did a fullwipe and only have had the Recovery left. How can I get a Terminal in there?
I thought about another way to fix the MD5: Maybe its possible to do a MD5Sum within windows over the boot.iso and save it to a .md5-file. You have to format the md5-file the way CMW needs it: "MD5sum /sdcard/.../boot.iso". Would this work properly?
funatkill said:
Yeah, it is the international i9100, but the way to fix a broken CWM-backup is the same. I've tested an cm10 alpha and after this I wanted to restore my ICS, because of sdcard problems. So I did a fullwipe and only have had the Recovery left. How can I get a Terminal in there?
I thought about another way to fix the MD5: Maybe its possible to do a MD5Sum within windows over the boot.iso and save it to a .md5-file. You have to format the md5-file the way CMW needs it: "MD5sum /sdcard/.../boot.iso". Would this work properly?
Click to expand...
Click to collapse
Not sure if it will work or not. Try to follow the steps given in the following thread and also just incase you may need it make a copy of the backup folder. 20 seconds tutorial to fix MD5 mismatch error no terminal needed
hisham027 said:
Not sure if it will work or not. Try to follow the steps given in the following thread and also just incase you may need it make a copy of the backup folder. 20 seconds tutorial to fix MD5 mismatch error no terminal needed
Click to expand...
Click to collapse
I fixed my md5 with the adb shell.. but I had to do this in one command . After reading this tut, I think there only has to be the MD5 of *.img, not of the .tar. Am I right?
Maybe its possible to script a zip-file for CWM which recalculates the MD5 of existing Backups?
The bash commands are simple. You only have to do this in a loop for all folders in /sdcard/clockworkmod/backup.
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.
Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things
Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.
Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks
What recovery are you using? I suck with adb so I got nothing on that front.
It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied
BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.
So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium
EDIT: I solved my own problem. Scroll down to post #8 for the solution.
My problem was that my phone (T-Mobile USA HTC One S) would not boot into ICS anymore, but I was still able to get into recovery (CWM), yet I had no access to the sdcard ("unable to mount /sdcard").
Post #8 below tells you how you can restore access to the sdcard in CWM so that you can push a ROM zip file to the sdcard via adb.
-J
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
archie53 said:
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Unfortunately I didn't have the foresight to make a nandroid backup. My previous phone was a Samsung Galaxy S 4G, which, like most Android phones, has a removable SD-Card that stuff can be copied onto (and then flashed). Not so here obviously.
Is it even possible to push files to the sdcard using the method I tried when in CWM?
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
joshnichols189 said:
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
Click to expand...
Click to collapse
It just got worse. I got the idea to format all partitions (data, system, cache, sdcard) through CWM, and now CWM can't even mount /sdcard/ anymore...
I had to do the same thing:
adb push "NameOfFile.zip /sdcard
then go to install from zip.
Look on sd card and it will be there.
I always rename the zip files to there can be less errors.
you can also do
adb shell pull "nameOfFile.zip /sdcard
make sure the zip file is where your adb and fastboot is
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
LuckyMethod said:
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
Click to expand...
Click to collapse
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
If that doesn't work an easy fix is boot into bootloader, goto fastboot and use "fastboot flash boot boot.img" and so fouth. In the dev section I seen a stock tmobile naindroid. Download it and you'll have your data.img and boot.img. You should be able to flash them without needing to push to /sdcard. letme know how it works
I know you fixed this already just thought this still might help
cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
...cut...
-J
Click to expand...
Click to collapse
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
LuckyMethod said:
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
Click to expand...
Click to collapse
Happy it worked for you. Took me several days to figure this out
Sent from my HTC One S using xda premium
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
j3.cole said:
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Thank you. I changed the title and original post to make it easier for people to find this thread.
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
mrmoretti said:
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
Click to expand...
Click to collapse
IT WORKED! This thread should be made sticky! I'm sure a lot of users who have HTC One S with built-in SD will have the same issue when mucking about with their phone. Thank you!
Bump, as too many people are having this problem.
Sent from my HTC One S using Tapatalk 2
cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
Click to expand...
Click to collapse
THANK YOU SO MUCH! THIS WORKED PERFECTLY!
This should definitely be included in a stickied guide for people like me who have managed to corrupt their recoveries.
Got it after several tries
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
yasir_jan87 said:
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
Click to expand...
Click to collapse
Try to shorten the filename, i.e. "rom.zip".
And try this slightly modified command instead:
adb push rom.zip /sdcard/rom.zip
Sent from my aokp_tenderloin using Tapatalk 2
Clockworkmod 6.0.0.0 Alpha Full touch recovery for the myTouch 4G Slide
As of right now, I don't recommend using this recovery until issues are resolved
How to install using terminal emulator (DD)
1. Download image to your sdcard then
2. Also download and open terminal emulator from the Play then type:
Code:
su
dd if=/sdcard/CWM_recovery_6000.img of=/dev/block/mmcblk0p21
reboot recovery
How to install using adb
1. Download
2. Setup ADB and Fastboot
Code:
adb reboot bootloader
fastboot flash recovery CWM_recovery_6000.img
fastboot reboot
How to install using terminal emulator (Flash_Image)
1. Download image to your sdcard then
2. Also download and open terminal emulator from the Play then type:
Code:
su
flash_image recovery /sdcard/CWM_recovery_6000.img
reboot recovery
Features:
Latest fixes from upstream CM
Power off charging
Full Trackpad support (left and right is disabled because it isn't used)
Openrecovery support (pretty sure)
UI changes
Four times smaller backups
Touch screen GUI
New CWM changes
slick blue theme with some Gnexus bootloader overlay themes
better logging\error detection
I will hopefully soon be able to put it in rom manager
USB Storage doesn't seem to be working. However it should be an easy fix as I had the same problem in 5.5.0.4 before I fixed it
This version of CWM is in alpha so there will most likely be some UI bugs
Thanks:
Kornyone
Koush and Cm team
Holy Crap AGAIN
MAN! You are one BUSY dude XMC! I can't begin to tell you how MUCH everything you do for this community and the MT4Gs is appreciated. I've gotten to feel like a kid at Christmas every time I open up these threads in the past couple of months. That goes for EVERYONE else that is involved.............except James.
WeekendsR2Short said:
MAN! You are one BUSY dude XMC! I can't begin to tell you how MUCH everything you do for this community and the MT4Gs is appreciated. I've gotten to feel like a kid at Christmas every time I open up these threads in the past couple of months. That goes for EVERYONE else that is involved.............except James.
Click to expand...
Click to collapse
Oh come on now james is part of the team too jk lol..
Good stuff xmc when my interview is over i now have an excuse to reflash. ( recovering flashaholic lol )
Oh yeah perms are good on my mint setup too thanks for that help xmc
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
Thanks for all your hard work you make this device fun to have.
I hate being a newb but i got to ask i keep getting a flash_image not found
I am trying to install recovery image with terminal
I am rooted(su works and is updated to latest version)
Downloaded image seems to be good
When i open terminal i do get $ export path= data local bin :$path
I dont recall if this is right, i dont think i remember seeing this before
Any help would be great thanks
Sent from my cm_tenderloin using xda premium
Small input: You cant select with trackpad and with key test trackpad left and trackpad right doesn't work.
used adb method and it worked flawlessly thanks XMC!!!!!
kkeller416 said:
I hate being a newb but i got to ask i keep getting a flash_image not found
I am trying to install recovery image with terminal
I am rooted(su works and is updated to latest version)
Downloaded image seems to be good
When i open terminal i do get $ export path= data local bin :$path
I dont recall if this is right, i dont think i remember seeing this before
Any help would be great thanks
Click to expand...
Click to collapse
Make sure you have busybox installed, if not, grab the installer from the Play store and run it and install it. Other than that, make sure you're doing an _ in flash_image and not a -. I'm on AOKP and it worked fine from the terminal using flash_image.
Thanks for your reply
I was using the commands for terminal emulator (flash image)
When i used the commands for terminal emulator(dd)
It worked fine
Sorry for the confusion
Whats the difference for the two anyways?
Sent from my cm_tenderloin using xda premium
CWM Touch on the Doubleshot is FAR superior to the one for the Vision.
Paitor said:
Small input: You cant select with trackpad and with key test trackpad left and trackpad right doesn't work.
Click to expand...
Click to collapse
Left and right on the trackpad isn't implemented because none of the UI options require moving left or right. But I'll look into why you cant select
Wow you have been busy. I'm psyched we have this now! I loved 4ext touch on glacier, going back to CWM was quite an adjustment. The touch feature is just a novelty obviously but it's a pretty sweet one. I see the backup sizes will be smaller, this is going to help a lot of people. It would be a life saver for me if I didn't just switch to a 32gb sd card literally last night lol. Thanks again!
Sent from my myTouch_4G_Slide using xda app-developers app
aawillma said:
Wow you have been busy. I'm psyched we have this now! I loved 4ext touch on glacier, going back to CWM was quite an adjustment. The touch feature is just a novelty obviously but it's a pretty sweet one. I see the backup sizes will be smaller, this is going to help a lot of people. It would be a life saver for me if I didn't just switch to a 32gb sd card literally last night lol. Thanks again!
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
I can certainly attest to the size differential! I'm getting ready to restore right now just to make sure my eyes aren't lyin' to me BUT my nandroid of MikMiui v1.0 was originally 713mb. My new one using CWM 6.0.0.0 is only 32mb!!! I am dumbfounded!!!:good:
First run: Did not succeed. Message as follows:
*Error while formatting /data!
*E:Error in /cache/recovery/log
*(I/O error)
*E:Failed closing /dev/block/mmcblk0p31
*(I/O error)
(I'm rerunning the 'nand & restore now to check behind myself).
MAJOR ISSUES: Did not succeed. Message as follows:
*CWM-based recovery v5.5.0.4
*Checking MD5 sums.....
*Erasing boot before restore.......
*Restoring system......
*Restoring data.....
*Can't open /cache/recovery/log
*Can't open /cache/recovery/log
*Can't open /cache/recovery/last_log
*Can't open /cache/recovery/last_log
*E:Failed closing /dev/block/mmcblk0p31
*(I/O error)
At present this is where I am stuck and can go no further that I can see. I reran the 32mb restore with the same results. Assuming that the nand was just bad, I tried to restore my 5.5.0.4. built nand with 6.0.0.0. SAME results. I reflashed 5.5.0.4 and tried another restore from my last good one and received the error message listed above. Am I reading this right that partition 31 has been left open for writing before CWM exited? Am I screwed?
HELP?
WeekendsR2Short said:
I can certainly attest to the size differential! I'm getting ready to restore right now just to make sure my eyes aren't lyin' to me BUT my nandroid of MikMiui v1.0 was originally 713mb. My new one using CWM 6.0.0.0 is only 32mb!!! I am dumbfounded!!!:good:
Click to expand...
Click to collapse
Epicness.
Sent from my MIUI V4
Worked like a charm via ADB. The new touch features are pretty sweet. Thanks!
I have some real issues here. See previous post above.....
WeekendsR2Short said:
I have some real issues here. See previous post on page 2.....
Click to expand...
Click to collapse
Uh oh... can you boot?
aawillma said:
Uh oh... can you boot?
Click to expand...
Click to collapse
I can't even get out of CWM. Well...I can but since the boot.img was erased before my restore it just hangs at the boot animation. Battery pull, then back to square 1.
this works flawlessly, you should really send this in too rom manager ASAP.
WeekendsR2Short said:
I can certainly attest to the size differential! I'm getting ready to restore right now just to make sure my eyes aren't lyin' to me BUT my nandroid of MikMiui v1.0 was originally 713mb. My new one using CWM 6.0.0.0 is only 32mb!!! I am dumbfounded!!!:good:
First run: Did not succeed. Message as follows:
*Error while formatting /data!
*E:Error in /cache/recovery/log
*(I/O error)
*E:Failed closing /dev/block/mmcblk0p31
*(I/O error)
(I'm rerunning the 'nand & restore now to check behind myself).
MAJOR ISSUES: Did not succeed. Message as follows:
*CWM-based recovery v5.5.0.4
*Checking MD5 sums.....
*Erasing boot before restore.......
*Restoring system......
*Restoring data.....
*Can't open /cache/recovery/log
*Can't open /cache/recovery/log
*Can't open /cache/recovery/last_log
*Can't open /cache/recovery/last_log
*E:Failed closing /dev/block/mmcblk0p31
*(I/O error)
At present this is where I am stuck and can go no further that I can see. I reran the 32mb restore with the same results. Assuming that the nand was just bad, I tried to restore my 5.5.0.4. built nand with 6.0.0.0. SAME results. I reflashed 5.5.0.4 and tried another restore from my last good one and received the error message listed above. Am I reading this right that partition 31 has been left open for writing before CWM exited? Am I screwed?
HELP?
Click to expand...
Click to collapse
try wiping data just by it self. If so just try flashing a rom not restoring
WeekendsR2Short said:
I can't even get out of CWM. Well...I can but since the boot.img was erased before my restore it just hangs at the boot animation. Battery pull, then back to square 1.
Click to expand...
Click to collapse
Can you ADB flash your boot.img? Or advanced restore just your boot partition?