So, I bought a new Wifi Tab and finally convinced the wife that I wasnt going to destroy this thing by rooting it and trying custom ROMs. However, I am not having much luck with CWM. Here is what is going on.
I used Odin to flash CWM 5.0.2.7. Then I promptly made a nandroid. Then I rooted it and made a nandroid with it rooted, then I installed Titanium Backup and promptly backed up everything. Then I copied all of this to my PC before continuing. So I am pretty safe (I thought) unless I manage to spill my drink on it.
I then tried to flash the latest AOKP on it and it seemed to flash ok along with the gapps. However when I tried to boot it, all it would do was reboot into CWM. I tried power off, power on, the reboot within CWM, reflash (multiple times), all to no avail. All it would do is boot straight to CWM.
I figured no problem, I will just use Odin, restore to stock and restore my backup. So I restored to stock, reflashed CWM and put my backup back on my storage and it just fails with MD5 mismatch. I searched around and all I can find about the MD5 is not to rename the folder. I dont rename the folders, just copy them back and forth so thats out. Is there a way to disable this and would I want to?
My only guess is that my USB cable is at fault and somehow it is corrupting my files. It is not the stock cable, but a 3rd party I bought online because it was longer. I've used CWM on both my wife's and my phones with no problems. Does anybody have any suggestions on why anything I try to do with it fails?
Also, I havent done as much searching on this as I should have, but is there a way to just have the Tab mount a folder as a generic usb drive instead of this mtp crap? My skyrocket just mounts like a usb drive and I transfer files on and off with no problems, its quick and painless. This mtp stuff is just annoying.
So I am just updating this in case anybody else comes across the same issue. I suspect it was the cable I was using. I downloaded the zip files with the tablet instead of transferring them with USB and they seemed to flash better. I ended up removing the MD5 file from the CWM backup that was stored on my desktop to force CWM to restore it and it restored but it crashed about 30 seconds after booting up so I think something was corrupted. (Hence why the md5 didnt match). So I just restored to stock, re rooted and restored my apps with TiBu. I still am not running a custom rom as the wife insists she needs the camera even though she has yet to take one pic with it.
Related
To make a long story short my gtab broke so I got another one. Prior to shipping the bad one back I did an nandroid backup and copied to my computer.
I received my new one today, installed clockwork and trying to do a restore.
Error while flashing boot image!
Click to expand...
Click to collapse
is what I receive. What gives? Any thoughts on why I'm seeing this?
I managed to get the "md5 sum mismatch" on my dx, but that was because I renamed the original file and used spaces in the name...
Never managed to get the error you got though
Sent from my DROIDX using XDA App
I've tried so many things. I flashed Vegan ROM over again, performed reboot, went into the fresh clean ROM..then rebooted into recovery to restore. Same error.
I tried partitioning over again, wiping, etc then restoring..same thing. I even tried another nandroid that I took days prior....!! I'm at a loss... argh! I want this image back from my nandroid
Also to add confusion to the mix: I tried taking a backup of nothing basically, and then restoring that and it worked fine. However just none of my 3 nandroid backups takin off my old device restore on this device. Is there a coorelation?
There has to be a way to flash back my nandroid backup...right?
Maybe my bootloader is locked, thus stalling on the boot.img?
ok so now I really jacked it up...tried downloading rom manager from market, installing some recovery and restoring my image, which did nothing but freeze at the viewsonic screen. Now I can't get into recovery anymore
Now I tried nvflashing back to stock... windows 7 crashed at the 11_app_img but it copied scucessfully, and now the tablet won't turn on?wtf!
Okay so I recently got this phone more or less as a toy and have been playing with its hardware and software to get it up to par and usable. I've been very impressed by this thing. I ended up with Trackball optional recovery and CM7 Condemned running very well. I seen Gin-sen-tazz and decided to give it a whirl.
Booted into recovery, did a nandroid then wiped data cache and dalvik and then went to flash the rom. It wouldn't go, told me to do something via adb. So I went to restore the backup of cm7 and get a new download ( didnt verify any md5's )
The back up restore gave me the same sort of error, then told me to do something else via adb. I was pretty peved off at this point and went into rom manager and flashed cwr and made a back up of the fresh cm7 install via cwr, and then tried to install the rom via rom manager and then manually in cwr and it still failed.
I'm still downloading my second copy of the rom and I'll be reporting back, but is there any harm in having both recovery's? I really would prefer to run cwr but I have heard of a few bricks, how wide spread is the epidemic? Boot loader still pushes me into trackball optional recovery when selected.
Just kinda sucks that I have two recoveries and neither will work. I am not very new at the whole rom flashing thing but I am not an expert by any means, and have not yet taken the time to learn my adb skills which I know I should
Alright downloaded and put the new rom on the sd card, booted into trackball optional and it flashed just fine.
I also used cwr to back up cm7 and then restore cm7 just to see if that backup indeed worked, and it did. Now I'm concerned that I don't have a stock back up, I made one in trackball recovery but it wont restore... The only back up I have that's working is the cm7 one via cwr... what would you guys recommend i do?
If you decide you want to flash back to stock 2.1 at some point, there's a couple simple options.
Flashback21 will get you back to the latest OTA(March 2011)...unrooted completely stock 2.1.
http://forum.xda-developers.com/showthread.php?t=792026
This other also gives you the latest March 2011 unrooted stock OTA but leaves your custom recovery.
http://forum.xda-developers.com/showthread.php?t=984274
Dunno if this is what was going on, but the Nandroid restore in Amon_RA for the Eris (and derivatives including the trackball-free recovery, I presume) have a 30% battery charge requirement.
If your battery isn't charged above that level, you'll just get a cryptic message about running nandroid-mobile.sh from adb; it won't say "charge your battery, please".
It pays to read Amon_RA's original post, where he points out that you should always check the recovery log file - the exact reason that you could not run the restore operation is reported in that log file. Rather than complaining about an unknown problem on a forum, you would instead know exactly what the problem was.
You can get at the file ( /cache/recovery/log ) via adb while the same recovery session is running, or you can use the Amon_RA menus to copy it to your SD card for later review. It's just a plain text file. Every time you boot the recovery, it gets overwritten - so you need to either review it right away after a problem occurs, or save it to the SD card.
bftb0
Hi, stupid question here from a relative noob....
I have a Cincinnati Bell Vibrant, that I recently flashed CM7 on (after using Rom Manager to backup up my stock rom). Liked it, but found it too battery-intensive, so I booted into clockworkmod recovery and attempted to restore the backup of my stock rom. It failed on flashing the boot image, and now my phone is stuck on the Vibrant screen, and won't boot. None of the hardware combinations to get into recovery mode are working, but I can get it into download mode. Before I screw things up further, what is the best way to go from here to get the backup restored, or is it even possible at this point?
Thanks
tabbott01 said:
Hi, stupid question here from a relative noob....
I have a Cincinnati Bell Vibrant, that I recently flashed CM7 on (after using Rom Manager to backup up my stock rom). Liked it, but found it too battery-intensive, so I booted into clockworkmod recovery and attempted to restore the backup of my stock rom. It failed on flashing the boot image, and now my phone is stuck on the Vibrant screen, and won't boot. None of the hardware combinations to get into recovery mode are working, but I can get it into download mode. Before I screw things up further, what is the best way to go from here to get the backup restored, or is it even possible at this point?
Thanks
Click to expand...
Click to collapse
This doesn't sound too bad. Basically you want to Odin back to stock. Then reflash the rom you were on, then you can reboot back into recovery and restore your backup. If voodoo was enabled on your backup make sure voodoo is enabled again before restoring(it might work either way, but I'm not sure). When I've done this, I restore a prerooted 2.2 stock Rom without changing the bootloaders, but almost any official stock rom will also work. I'm on the go, so I don't have a link handy, but post back if needed and I will point you to the odin package I use. Good luck.
I also am having some issues with Clockworld recovery. The problem i am having is that when doing a nandriod backup this is the error i am recieving
"E:cant mount /dev/block/mmcblk1p1 (or @)
Cant mount /mnt/sdcard
any suggestions on whats going on?
phone_noobie said:
I also am having some issues with Clockworld recovery. The problem i am having is that when doing a nandriod backup this is the error i am recieving
"E:cant mount /dev/block/mmcblk1p1 (or @)
Cant mount /mnt/sdcard
any suggestions on whats going on?
Click to expand...
Click to collapse
Are you sure the sdcard is good? If so then I would follow the same steps listed above, that way you know your CWR is good.
mattb3 said:
Are you sure the sdcard is good? If so then I would follow the same steps listed above, that way you know your CWR is good.
Click to expand...
Click to collapse
yes it is good because i can see all the videos, pics i have saved in it. Also i put the new ROM on my internal sd card and its there so sd card is def good. What could be causing the problem?
To the op, I would use Odin, no real worries there.
To the other guy with sdcard issue, try moving all files to your PC, format your sdcard, reboot, move files back, flash cwr in ROM mgr, backup work? Move critical files back from PC.
mattb3 said:
This doesn't sound too bad. Basically you want to Odin back to stock. Then reflash the rom you were on, then you can reboot back into recovery and restore your backup. If voodoo was enabled on your backup make sure voodoo is enabled again before restoring(it might work either way, but I'm not sure). When I've done this, I restore a prerooted 2.2 stock Rom without changing the bootloaders, but almost any official stock rom will also work. I'm on the go, so I don't have a link handy, but post back if needed and I will point you to the odin package I use. Good luck.
Click to expand...
Click to collapse
Thanks...that's exactly what I did, except the backup would never quite "take." It completely loaded and cycled through the boot process, but I ended up on a boot-restore loop. So now I've Odin-ed back to stock with the closest build I could find to my stock (which I don't think is out there yet - FROYO.UVJL6.ULTIMOBILE - do you know anywhere to find it?), rooted, and am searching for a good, stable, battery-friendly mod once again.
s15274n said:
try moving all files to your PC, format your sdcard, reboot, move files back, flash cwr in ROM mgr, backup work? Move critical files back from PC.
Click to expand...
Click to collapse
i did try formatting, then moving all the stuff back and am still getting that same error message
^ what rom are you on, if one?
You could always ODIN, and use my option b cwr in the noob guide. I just tested making a backup using trigger 8/22 and know there are no issues. Not really sure whats up on your end. I will say though, I've emailed koush several times that there is an issue with cwr on the vibrant from rom manager, for some it won't even flash.
phone_noobie said:
i did try formatting, then moving all the stuff back and am still getting that same error message
Click to expand...
Click to collapse
try different sd card..or reinstall CWM...
Tried getting a cyagen 9 ICS rom on my 3g wifi 10.1 tab, forgot to install the clockwork stuff, and now it wont work no more. Think i managed to delete everything on it!? Did manage to install clockwork after via odin but now it find no files on sd and nothing else will work. The sd card will not appear via usb on my pc so i cant put new files in!?
Is there any hope for it or is the garbage can next stop?
Magnar, Norway
Apparently you can see the device with odin - I'd recommend doing a full restock, you can follow the guide at the overcome experience: http://www.teamovercome.net/p7500/?page_id=5
Scroll down on that page until you see the "Re-“Stocking” Yer System…" part and follow the instructions there.
Once you do that your tab should be back in working condition and you'll be able to install CWM and a custom ROM with it. And another piece of advice - always (seriously, ALWAYS) do a nandroid backup of your system before flashing ROMs, especially if you aren't 100% sure what you need to do. This way, if something goes wrong, you can always just restore the backup and you're good to go.
Best of luck!
Why don't you just mount your tablet to you PC through - mounts and storage in CWM recovery? It should work. If not, do what the guy above me said.
jippi
Tried mounting usb but it did not work just got error. Tried the full restock and that did the trick. THANKS
That's why reading helps, It clearly says "Flash the zip using CWM" because modified files cannot be flashed by the stock recovery due to Googles restriction's to avoid breaking their EULA, so the work around would be using a personal made CWM. Problem is stock one is only meant to flash update.zip, to specific folder's, when you install a ROM via stock, it just dumps and replaces everything in one place, It's like getting all your 3 Science subject notes mixed in 1 notebook, you have no idea what is what.
Background
Used many hours to set up phone to my liking. Got a problem with earphone-jack, so i handed it in. I couldnt do a proper backup beforehand, cause this required root access. The earphone-jack got replaced, but they also decided to upgrade my phone to the newest firmware? , deleting everything in the process. I will set everything up again in the weekend, but i do NOT want to do this a third time .
I have searched around for guides, but since i cant find a LQ6 kernel, every guide is telling me to use a different kernel. The best thing would be to root only. Does this work with my phone ?
What i need
Root only
Ability to unroot would also be nice
About phone
Model: GT-I9100
Android v. 4.0.4
Baseband: I9100XXLQ6
Kernel: 3.0.15-1068762 [email protected] #3 SMP PREEMPT Wed Aug 29 13:40:41 KST 2012
Build: IMM76D.XWLPX
Other Question
If i get another problem with the phone, backup everything, unroot and hand it in. If they decide to upgrade my firmware again, will i still be able to restore my backup ? What backup program is best to use in your opinion ? I want app settings, launcher settings and homescreen setup to be backed up.
HELP : GOT TWO NEW QUESTIONS
I tried to follow the guide in "theunderling"s signature.
At first i thought the files were supposed to be on the internal SD card, so i put them there and rebooted the phone into recovery. While there i tried to find my files, of course to no luck. I thought that maybe i had to unplug the USB, so i did this while in rec. menu. Still didnt find the files, so i rebooted my phone. Suddenly there were a REALLY LOUD ALARM NOISE coming from my phone. I have never heard that sound from my phone before. It stopped after a while, but has also happened at random times since. WHAT IS THIS ? (To be clear: this came before i ran any of the downloaded programs/scripts/etc).
After this i found an external SD - card and put the files on this. Got root access in a couple of seconds, and everything seemed fine. But now my computer refuses to connect to the phone "couldnt find hardware-ID" or something (Translated from my windows language, so might not be 100 % accurate. HOW TO FIX ?
BTW Thank you all so much for your time. I really appreciate it
1.use the guide in my sig or flash a siyah rooted kernel.
2.a nand backup.
3.you can just flash the firmware you listed back on your phone and that would unroot it.
Download it from sammobile now and keep it on your pc if you need it later(and keep nand backup there also).
4.if you get it back,reroot again and put the nand backup back on your sd card and flash that in cwm.
Dont forget to back up efs folder once you root(keep that on pc).
1. Do as theunderling said, or you can use the PhilZ-CWM6 kernel, which is pure stock based. http://forum.xda-developers.com/showthread.php?t=1877270
2. Do a NANDROID backup. Make sure to have atleast 1.1GB available on your MicroSD card. This is done in CWM recovery.
3. To unroot, I believe flashing a stock kernel will do the job, if you only have flashed a kernel. Also, the SuperSU app included in the PhilZ kernel has an unroot option.
Also, backup you EFS folder. And have atleast two backups of it.
Ignore my no.3 as I was thinking you would be installing a rom later.
That rooting method I said also lets you unroot.
Hi. Thanks so much for your answers. When rooting my phone, two problems arose (See original post). Would be really grateful for any input on those.
Never heard of an alarm sound happening-maybe you set alarm/event.
Anyway,what stage are you at.Are you definitely rooted.Is the phone booting as normal and can you access recovery/download mode.
theunderling said:
Never heard of an alarm sound happening-maybe you set alarm/event.
Anyway,what stage are you at.Are you definitely rooted.Is the phone booting as normal and can you access recovery/download mode.
Click to expand...
Click to collapse
Hi! Did check around for any events/alarms, and im sure its not the issue. Since i couldnt connect to my phone via USB, i tried Kies Air, and the alarm sound started again. Tried a few times, and EVERY time i start Kies air, i will get this sound for 5-10 seconds. It also happened twice when i werent even touching the phone :/
I have tried two programs which require SU - access. Got a prompt when starting them , and they worked fine . Kies Air works fine too btw. (Its the USB - connection that i cant get to work).
Also: For some reason i had SUPERUSER installed from before, and now i cant uninstall it again. Also, when i gave the two programs i tested superuser access, it showed the SUPERUSER icon. (program in big letters)
Just to make it clear again: The alarm sound came after i had fooled around in recovery mode, before ANYTHING where installed.
Youve not answered the previous questions.
You should be flashing a "safe" siyah kernel and backing up your efs folder.You can make a nand backup before that or after.
Just get the .zip file from gohkmoran site and flash via cwm.Then get hktool from play store for your efs.
Then the alarm/usb/pc problems can be looked into.
theunderling said:
Youve not answered the previous questions.
You should be flashing a "safe" siyah kernel and backing up your efs folder.You can make a nand backup before that or after.
Just get the .zip file from gohkmoran site and flash via cwm.Then get hktool from play store for your efs.
Then the alarm/usb/pc problems can be looked into.
Click to expand...
Click to collapse
Sorry, here are some more info:
Download modeI get a warning screen against installing custom os? volume up for install and volume down for reboot. Have never tried DL boot before, so cant say anything about this one
Recovery mode Boots normal and looks exactly like earlier.
Normal Boot Looks like before i rooted. No new programs either.
Could you link directly to which kernel i should use ? I have no idea :/ sry
Sorry,I should have explained a bit more.
Get the siyah kernel file and put it on your sdcard/internalsd
Do the rachmat stuff again.Once you install cwm.zip and su-busybox.zip..........dont reboot.
Install the siyah-s2-v4.01cwm.zip file (whilst your still in temp cwm)you download from his site(google should take you to the file).
Then you end up with a safe kernel and permanent cwm.
Then you can do nand and efs backups
theunderling said:
Sorry,I should have explained a bit more.
Get the siyah kernel file and put it on your sdcard/internalsd
Do the rachmat stuff again.Once you install cwm.zip and su-busybox.zip..........dont reboot.
Install the siyah-s2-v4.01cwm.zip file (whilst your still in temp cwm)you download from his site(google should take you to the file).
Then you end up with a safe kernel and permanent cwm.
Then you can do nand and efs backups
Click to expand...
Click to collapse
What i did
Resetted to factory settings
Installed cwm.zip
Installed su-busybox.zip
Installed Siyah-s2-v4.1.5-CWM.zip
What i got
No more funky alarms. Neither with kies, or any other program. :good:
Pc connection works if i put it in mass storage mode :good:
Got a CWM app, which i used to take a nandroid backup :good:
Still cant find hardware ID. (So i still cant just connect and open folder)
Thanks so much
Most important is the connection thingy (in case its something "serious" But if you feel in an extremely helpful mood, i got two more questions.
For unrooting To unroot i probably need to:
Flash Stock Kernel (from where ???)
install SU-Uninstaller-Signed.zip
What about CWM and SuperUser. How do i get rid of those 2 ?
Backup
For more advanced backup (backup individual apps etc), I `ve heard about a couple different apps: Titanium Pro and Superuser Elite. Do you recommend one of these?
Try this for your hardware problem.I never use kies as its ****
You can use this,or go to sammobile and flash xwlpx to get back to stock.
You can use titanium backup to backup your apps and also "remove" crappy system apps etc(theres a thread that guides you what to/what is safe to remove).
And get your efs backed up.
theunderling said:
You can use this,or go to sammobile and flash xwlpx to get back to stock.
You can use titanium backup to backup your apps and also "remove" crappy system apps etc(theres a thread that guides you what to/what is safe to remove).
And get your efs backed up.
Click to expand...
Click to collapse
Thanks again!!
I dont like Kies either, but wanted to fix my problem of 2 reasons
- I was afraid it was a symptom of something serious
- MDP mode without kies is nice to use when you only need to upload a few files to your phone on the go
WELL, KIES WAS THE SOURCE OF MY PROBLEMS. When i uninstalled Kies - drivers, it worked perfectly.
Have taken backup of my efs now (with HC-Ktool, which i assume u meant ), so now i will start setting up my phone to my liking. Thanks so much :highfive:
So basically got everything i came for
But, hmm still unsure if i will get completely unrooted phone from flashing stock kernel and removing SU. Wont the CWM that came with Siyah still be installed ? Can i uninstall this normally afterwards ? Or can i uninstall it before i remove superuser, and then use the CWM -booter thingy to get rid of SU ?? Hmm sorry for being such a noob.
slimchancex said:
Thanks again!!
I dont like Kies either, but wanted to fix my problem of 2 reasons
- I was afraid it was a symptom of something serious
- MDP mode without kies is nice to use when you only need to upload a few files to your phone on the go
WELL, KIES WAS THE SOURCE OF MY PROBLEMS. When i uninstalled Kies - drivers, it worked perfectly.
Have taken backup of my efs now (with HC-Ktool, which i assume u meant ), so now i will start setting up my phone to my liking. Thanks so much :highfive:
So basically got everything i came for
But, hmm still unsure if i will get completely unrooted phone from flashing stock kernel and removing SU. Wont the CWM that came with Siyah still be installed ? Can i uninstall this normally afterwards ? Or can i uninstall it before i remove superuser, and then use the CWM -booter thingy to get rid of SU ?? Hmm sorry for being such a noob.
Click to expand...
Click to collapse
I am sure that flashing a stock kernel will unroot your phone, kill me if I am worng . (I am noob also.)
CWM will be removed once your on the stock kernel.
Once you set up your phone,make a nand backup of that.
You want to able to use usb so you can use Odin,especially if something goes wrong flashing something and you cant boot phone, or into cwm.
Flashing a stock rom unroots the phone.For warranty,you go into download mode and check binary is at zero,and official firmware is at yes.