[Q] First post. Help a newbie out please. - AT&T LG Optimus G

Does anyone know why cwm keeps making backups with md5 hash mismatches?
I saw this thread, and I really want to install this debloated rom. I'm afraid to attempt to flash it considering any cwm backup I create seems to end up with an md5 mismatch. Since that's the case, I wouldn't have anything to fall back on if something went wrong.
I'm rooted and on FreeGee v0.5 if that helps anyone know what my issue may be.

Yoreo said:
Does anyone know why cwm keeps making backups with md5 hash mismatches?
I saw this thread, and I really want to install this debloated rom. I'm afraid to attempt to flash it considering any cwm backup I create seems to end up with an md5 mismatch. Since that's the case, I wouldn't have anything to fall back on if something went wrong.
I'm rooted and on FreeGee v0.5 if that helps anyone know what my issue may be.
Click to expand...
Click to collapse
It's a bug with CWM. It should be fixed in the next day or two.

DeathmonkeyGTX said:
It's a bug with CWM. It should be fixed in the next day or two.
Click to expand...
Click to collapse
In the meantime, boot into CWM, adb shell (connect USB), and run the following:
Code:
cd /sdcard/clockworkmod/backup/(YOUR BACKUP NAME HERE)
md5sum *.img > nandroid.md5
You should now be able to restore your backup.
Edit: adding this to my guide

carrett said:
In the meantime, boot into CWM, adb shell (connect USB), and run the following:
Code:
cd /sdcard/clockworkmod/backup/(YOUR BACKUP NAME HERE)
md5sum *.img > nandroid.md5
You should now be able to restore your backup.
Edit: adding this to my guide
Click to expand...
Click to collapse
Thanks guys!
I'm still new to Android OS (came from a jailbroken iPhone 4), and am still in the early learning stages. :silly:

well welcome to android. the IRC is very helpful too for questions. the guys on there are very quick with answers if anything else is needed

Yoreo said:
Does anyone know why cwm keeps making backups with md5 hash mismatches?
I saw this thread, and I really want to install this debloated rom. I'm afraid to attempt to flash it considering any cwm backup I create seems to end up with an md5 mismatch. Since that's the case, I wouldn't have anything to fall back on if something went wrong.
I'm rooted and on FreeGee v0.5 if that helps anyone know what my issue may be.
Click to expand...
Click to collapse
You should use FreeGee again and unroot and then root so that you have TWRP instead of CWM. I was never able to get backups ot work in CWM and mow I use TWRP where my backups have currently failed 0% of the time.

Related

[ROM] 21/Jan 1.3 - MoDaCo Custom ROM

This ROM has been superceded by MCR 1.5 here.
P
aad4321 said:
Sweet, i might give it a shot. quick question tho... will this wipe the device?
Click to expand...
Click to collapse
Modacp said:
I'm pleased to present my MoDaCo Custom Nexus One ROM! No 'wipe' is required to use this ROM.
Click to expand...
Click to collapse
Reading comprehension much?
aad4321 said:
just to confirm, wavesecure add on is a anti theift program which is a monthly service?
Click to expand...
Click to collapse
No, there is no monthly service charge...at least not yet. I have been using wave secure for a little while now, and for a 3rd party security app its pretty damn good.
I tried to flash and got this:
Code:
E:No space left on device
E:Error writing Boot:
E:Failure at line 369:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
I tried to reboot and it wouldn't boot, so I pulled the battery and went back into recovery and tried to apply the NANDROID backup, seemed to apply fine, but now it always boots into bootloader, no matter what I do. I can still make it into recovery so it isn't all lost, but I can't do anything else from there.
Bizarre, never seen an error like that before!
What happens if you try to re-apply the ROM?
P
ccunningham83 said:
I tried to flash and got this:
Code:
E:No space left on device
E:Error writing Boot:
E:Failure at line 369:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
I tried to reboot and it wouldn't boot, so I pulled the battery and went back into recovery and tried to apply the NANDROID backup, seemed to apply fine, but now it always boots into bootloader, no matter what I do. I can still make it into recovery so it isn't all lost, but I can't do anything else from there.
Click to expand...
Click to collapse
did you wipe then restore nandroid?
anyone get tether working on this rom?
Only wireless tether is supported at the moment. Wired tether coming in a future release.
P
modaco said:
Only wireless tether is supported at the moment. Wired tether coming in a future release.
P
Click to expand...
Click to collapse
neither wireless or wired working for me..
Strange, wireless seems to be working for me I think?
P
wireless tethering say "please wait while starting" but never starts...
any suggestions?
modaco said:
Bizarre, never seen an error like that before!
What happens if you try to re-apply the ROM?
P
Click to expand...
Click to collapse
Re-Applying the ROM gets the same result.
I did Wipe and try to re-apply and also wipe and Nandroid. All got me nowhere. I ended up getting it fixed by applying Cyanogens Bacon1.img. I am really interested in your ROM though. Think maybe I got a bad download or something. I will try again and check the md5 sum this time.
my tether puts a signal out and all but i cant connect to it.. only get local
So after downloading the ROM again after the first one didnt work, I got this for the md5 checksum:
Code:
e04970294888313787d0b9d5cb370a12
Which is entirely different than what is posted on the MoDaCo Forum:
Code:
d537e42372a7239dfaf40846ef0b8b4e
However, I could be doing it wrong. This is the first time I tried using md5 checksums to verify a download. However I used two different utilitys to get the same checksum and I don't want to try to flash it again and have it mess up.
ccunningham83 said:
Re-Applying the ROM gets the same result.
I did Wipe and try to re-apply and also wipe and Nandroid. All got me nowhere. I ended up getting it fixed by applying Cyanogens Bacon1.img. I am really interested in your ROM though. Think maybe I got a bad download or something. I will try again and check the md5 sum this time.
Click to expand...
Click to collapse
I can help fix your problem and it is very simple. READ THE FIRST POST BY PAUL. DO NOT WIPE. Do a Nandriod backup then apply the update. Remember do not extract the rom file with I hope WINRAR, just rename update. Let me know if this solves it for you which it should. Kevin
kevinrirvine said:
I can help fix your problem and it is very simple. READ THE FIRST POST BY PAUL. DO NOT WIPE. Do a Nandriod backup then apply the update. Remember do not extract the rom file with I hope WINRAR, just rename update. Let me know if this solves it for you which it should. Kevin
Click to expand...
Click to collapse
Maybe I should have explained everything I did step by step, I did READ THE FIRST POST BY PAUL AND DIDN'T WIPE. Before I even tried flashing, I performed a Nandroid Backup. I booted into recovery, applied the update, got the error message I listed, tired to reboot, got stuck, pulled the battery, booted back into recovery, performed a wipe, reapplied the update, rebooted, still a no-go, rebooted back into recovery, performed a Nandroid restore, after it completed, rebooted, got stuck on bootloader screen, reloaded the ROM on the SD card, tried flashing again, still no luck, ended up flashing Cyanogens Bacon1.img to fix the problem.
I want to give it another try, but I may wait and find out if my md5 sum is correct or maybe try another link if someone post it up.
ccunningham83 said:
Maybe I should have explained everything I did step by step, I did READ THE FIRST POST BY PAUL AND DIDN'T WIPE. Before I even tried flashing, I performed a Nandroid Backup. I booted into recovery, applied the update, got the error message I listed, tired to reboot, got stuck, pulled the battery, booted back into recovery, performed a wipe, reapplied the update, rebooted, still a no-go, rebooted back into recovery, performed a Nandroid restore, after it completed, rebooted, got stuck on bootloader screen, reloaded the ROM on the SD card, tried flashing again, still no luck, ended up flashing Cyanogens Bacon1.img to fix the problem.
I want to give it another try, but I may wait and find out if my md5 sum is correct or maybe try another link if someone post it up.
Click to expand...
Click to collapse
Paul's rom's are only at modaco and I am pretty sure he does not allow other links for I only use his rom's and have one on my Hero Telus, AT&T 3G, and what I like most about them is he keeps them as close to stock as possible, a good thing, and just optimizes them.
Your not going to brick your n1 so I know your gun-shy now but try the link a few more times even and it will work. Also, delete or format your memory card so it the rom is at the root for this might have something to do with it. Want you to have a happy ending. Kevin
The zips are signed, if a download is corrupt it won't flash.
P
kevinrirvine said:
Paul's rom's are only at modaco and I am pretty sure he does not allow other links for I only use his rom's and have one on my Hero Telus, AT&T 3G, and what I like most about them is he keeps them as close to stock as possible, a good thing, and just optimizes them.
Your not going to brick your n1 so I know your gun-shy now but try the link a few more times even and it will work. Also, delete or format your memory card so it the rom is at the root for this might have something to do with it. Want you to have a happy ending. Kevin
Click to expand...
Click to collapse
I need to re-format my sdcard, I still have the three partitions from my G1. I will give that a try, but I am still unsure about the md5 sum issue. Not too worried about bricking the device after all I put my G1 through.
Thank you for posting here on XDA also

[KERNEL] ClockworkMod compatible kernel and ROM Manager support

Ok, here's official clockworkmod and ROM Manager support
For a full/better How To, click here: http://forum.xda-developers.com/showthread.php?t=788099
This thread is a quick rundown, as well as a primer on how to create a proper clockwork compatible kernel.
First, use odin or redbend_ua to flash this kernel:
http://koush.tandtgaming.com//samsung/fascinate/zImage (you will need to package it accordingly for odin, I am lazy and did not do so, see the other thread)
Then, open up ROM Manager and flash recovery (choose Fascinate!).
All done!
Note, using reboot recovery or adb reboot recovery will take you to a "stock" recovery. Simply apply the update.zip on your SD card and clockworkmod will start up. (This method is better known as fakeflash)
Starting up recovery through ROM Manager will take you directly into clockworkmod.
How this works for those that want to develop on this further and create kernels that are ALSO clockworkmod compatible:
I extracted a initramfs from a stock recovery. I modified recovery.rc and fota.rc to allow adbd (and other small fixups). I modified default.prop to enable adbd and root shell. I replaced /res/keys with a test signed version to allow applying update.zip files.
Here is my fascinate initramfs:
http://github.com/koush/fascinate_initramfs
One can build clockwork directly into the kernel if they so choose. Simply take the update.zip on your SD card and pack those files into the initramfs as well. I chose not to do this because I am lazy.
i know this is irrelevant but i hope you can help
i flashed the CMWrecovery file --- i followed the steps to the dot .. and now my phone can't get signal and is rebooting insanely ... help!!!
i did not uninstall the ext2 lag fix - i did not see that in the steps --
i even booted into standard recovery and completed a master reset -- same issue ---
masri1987 said:
i know this is irrelevant but i hope you can help
i flashed the CMWrecovery file --- i followed the steps to the dot .. and now my phone can't get signal and is rebooting insanely ... help!!!
i did not uninstall the ext2 lag fix - i did not see that in the steps --
i even booted into standard recovery and completed a master reset -- same issue ---
Click to expand...
Click to collapse
join the freenode #samsung-fascinate channel... i will try to help you.
Has anyone else tested this? I've yet to get it to boot, so I would caution those looking to install CWM to use the files found in the other thread until we can sort out what's up with this zImage..
i have this up and running with root and cw the only problems im having is my market wont load and it only gives me the "top free" tab and the "just in" tabs on the market...i can not see the top paid tab. i did a odin full restore (everything back to stock) then i rooted and flashed this anyone give me a had to why my market is funny? or how i have bad serves now?thanks to everyone for getting us cw!!
ruthlessbeatle said:
i have this up and running with root and cw the only problems im having is my market wont load and it only gives me the "top free" tab and the "just in" tabs on the market...i can not see the top paid tab. i did a odin full restore (everything back to stock) then i rooted and flashed this anyone give me a had to why my market is funny? or how i have bad serves now?thanks to everyone for getting us cw!!
Click to expand...
Click to collapse
So you're saying you downloaded this specific zImage2 file, then tar'd it, then flashed it over your kernel and it worked? Did you use odin, or redbend?
Or did you just post for help on the bottom of this thread?
namebrandon said:
So you're saying you downloaded this specific zImage2 file, then tar'd it, then flashed it over your kernel and it worked? Did you use odin, or redbend?
Or did you just post for help on the bottom of this thread?
Click to expand...
Click to collapse
lol nahh i flashed it last night with odin but it was zimage not zimage2 is there a difference? i can boot into recovery and even installed zips off my sd card like i said the only real problems i have is serves and market
ruthlessbeatle said:
lol nahh i flashed it last night with odin but it was zimage not zimage2 is there a difference? i can boot into recovery and even installed zips off my sd card like i said the only real problems i have is serves and market
Click to expand...
Click to collapse
Yes, there's a difference. When I posted asking if anyone had gotten this to work, I meant the kernel Koush specifically provided above, in this post. I know in general CWM recovery works.
I would try posting in the thread where you obtained your files for help. That way there are people who are using the same kernel that might help.
namebrandon said:
Yes, there's a difference. When I posted asking if anyone had gotten this to work, I meant the kernel Koush specifically provided above, in this post. I know in general CWM recovery works.
I would try posting in the thread where you obtained your files for help. That way there are people who are using the same kernel that might help.
Click to expand...
Click to collapse
turee that sorry. im noticing more and more problems like i dont have maps and missing apps here and there. thisis my fist time using odin and samsung...should i just odin back to stock everything and then try this recovery?
Alright...so I am confused now and I am not an Android noob....I see all the threads with how to flash the recovery and then this one....but I think we should have ONE thread that walks thru Rooting, flashing recovery etc....AND, in the first post, the instructions tell people how to pack files and etc., but a lot of people have no clue what that means...therefore, we need to have a "packed-ready" files for noobs. There are just a few too many botched phones.
As a noob myself, I think that sounds like a great plan.
Look closer my friend.
Clockworkmod installation how to
namebrandon said:
Look closer my friend.
Clockworkmod installation how to
Click to expand...
Click to collapse
Thanks, I saw that thread....but what I meant was, for a new person to see the following can be extremely confusing:
http://forum.xda-developers.com/showthread.php?t=787834
http://forum.xda-developers.com/showthread.php?t=788099
http://forum.xda-developers.com/showthread.php?t=787168
http://forum.xda-developers.com/showthread.php?t=788256
You know what I mean?
Can someone post a link on how to backup the original stock kernel via ODIN (or some other application) before I go ahead with this? I'd like to just be able to go back to the unmodified kernel if I want to. After a five minute search I couldn't even find a tutorial on ODIN.

Stock Nandroid Image

If anyone needs a stock nandroid image (with root),
http://www.megaupload.com/?d=YWQJRO90
There is no need to flash this unless you messed up or just want to go back to stock (with root).
instructions:
DO NOT install it as update.zip . you are supposed to unzip the file after you download it and place the folder called 2010-09-21.18.31.12 in /sdcard/clockworkmod/backup then you boot into cwm and goto backup and restore -> restore -> 2010-09-21.18.31.12
what is this nandroid ? stock image ? i mean im new to android and i keep seeing nandroid but im not sure what it does
+1 thanks easier then using oden
dialect129 said:
what is this nandroid ? stock image ? i mean im new to android and i keep seeing nandroid but im not sure what it does
Click to expand...
Click to collapse
Nandroid makes a complete backup of your phone, all your data, apps, everything. It's like it takes a snapshot of your phone, and when you restore it your phone will be back to the exact state of when you made the backup.
The image i posted will take your phone back to what it was like when you pulled it out of the package, except with root. In order to use nandroid, you have to flash the cwm kernel and install the recovery for your phone through rom manager.
bubbleywine said:
+1 thanks easier then using oden
Click to expand...
Click to collapse
no problem, yeah i dont like using odin.
wasupwithuman said:
Nandroid makes a complete backup of your phone, all your data, apps, everything. It's like it takes a snapshot of your phone, and when you restore it your phone will be back to the exact state of when you made the backup.
The image i posted will take your phone back to what it was like when you pulled it out of the package, except with root. In order to use nandroid, you have to flash the cwm kernel and install the recovery for your phone through rom manager.
Click to expand...
Click to collapse
so that means if i accidently erased swype i'd have it back again with this one?
dialect129 said:
so that means if i accidently erased swype i'd have it back again with this one?
Click to expand...
Click to collapse
yes it has everything you would have stock. just rooted already.
wasupwithuman said:
yes it has everything you would have stock. just rooted already.
Click to expand...
Click to collapse
sorry for all the question so ok then after that to get all my stuff back would i use titanium for my apps contacts etc?
dialect129 said:
sorry for all the question so ok then after that to get all my stuff back would i use titanium for my apps contacts etc?
Click to expand...
Click to collapse
yeah, you will have to put the information for your gmail account back in, restore anything from titanium. It's completely stock, it has no user infomation on it.
wasupwithuman said:
yeah, you will have to put the information for your gmail account back in, restore anything from titanium. It's completely stock, it has no user infomation on it.
Click to expand...
Click to collapse
titanium does backup contacts to though im thinking
once u sync your gmail u shouldnt have to worry about your contacts, that takes care of all of it.
ksizzle9 said:
once u sync your gmail u shouldnt have to worry about your contacts, that takes care of all of it.
Click to expand...
Click to collapse
yea but i disabled google sync because it kept putting contacts from my old phone in that i didnt want and i cant figure out how to change it online
Is this with todays update?
dialect129 said:
yea but i disabled google sync because it kept putting contacts from my old phone in that i didnt want and i cant figure out how to change it online
Click to expand...
Click to collapse
ok well i tried to flash this with clockwork butttttttttttt it just freezes no luck ..what am i doing wrong
Ok, so I am getting my Fascinate tomorrow (can't wait by the way). I have been cruising the forums doing my research before I attempt to root, flash CWM recovery, etc. I am completely unfamiliar with with using Odin, but have used nandroid via Amon's recovery on my Droid Eris (which is running Froyo by the way).
Here's my question: how do I apply this image? Do I have to be rooted first, or can I go ahead and apply this zip and never have to fool with Oden? I just want to be sure I don't make a mistake. Eris development was firmly established by the time I arrived on the scene, so I have not had to worry about these kinds of things. Sorry if this seems like a noob question?
Sent from my Froyo Eris using XDA App
dlongb13 said:
Is this with todays update?
Click to expand...
Click to collapse
nope, the update is not compatible with root right now. Wait for a dev to release the root friendly vzw update.
bendbowden said:
Ok, so I am getting my Fascinate tomorrow (can't wait by the way). I have been cruising the forums doing my research before I attempt to root, flash CWM recovery, etc. I am completely unfamiliar with with using Odin, but have used nandroid via Amon's recovery on my Droid Eris (which is running Froyo by the way).
Here's my question: how do I apply this image? Do I have to be rooted first, or can I go ahead and apply this zip and never have to fool with Oden? I just want to be sure I don't make a mistake. Eris development was firmly established by the time I arrived on the scene, so I have not had to worry about these kinds of things. Sorry if this seems like a noob question?
Sent from my Froyo Eris using XDA App
Click to expand...
Click to collapse
Everyone is a noob at first.
You need to root first
follow this:
http://forum.androidcentral.com/fasc...-how-root.html
then install cwmrecovery
follow this:
http://forum.xda-developers.com/showthread.php?t=788099
you won't need this nandroid backup.
wasupwithuman said:
If anyone needs a stock nandroid image (with root),
http://www.megaupload.com/?d=YWQJRO90
Click to expand...
Click to collapse
this doesnt seem to work
dialect129 said:
this doesnt seem to work
Click to expand...
Click to collapse
wait it works i had to upzip your file and put it in the folder for the images along with the other back ups then go into rom manager and manage back ups .. thanks i finally have SWYPE BACK!!..yes i did all that for swype lol
dialect129 said:
this doesnt seem to work
Click to expand...
Click to collapse
the link or the nandroid? cause i just tested the link and it works. And someone already tested the nandroid and it worked.
wasupwithuman said:
nope, the update is not compatible with root right now. Wait for a dev to release the root friendly vzw update.
Everyone is a noob at first.
You need to root first
follow this:
http://forum.androidcentral.com/fasc...-how-root.html
then install cwmrecovery
follow this:
http://forum.xda-developers.com/showthread.php?t=788099
you won't need this nandroid backup.
Click to expand...
Click to collapse
I really appreciate the prompt response. I think I am going to wait until a dev develops a root friendly vzw update. Or I may go ahead and root and wait till then ..... decisions, decisions
I saw where you posted that some Sticky topics need to be compiled, wasupwithuman. I could not agree more. A couple more questions for you (maybe these will help someone else too) .... (1) How stable is CWM on the Fascinate? I read somewhere that it is a duct-taped together recovery that will do for now. Is this true??? (2) Should I just wait for a dev to develop a custom recovery (like Amon's on the Eris), or is CWM stable enough as it currently is? There seems to be some confusion about this from topic to topic. (3) This is unrelated, but has anyone confirmed Wireless Tether working on their Fascinate. I believe I read that it was somewhere else, but would like to know for sure. Thanks again!!!
P.S. - First link is down, but I found another guide on XDA and will probably just follow it (considering it uses adb which I am familiar with from my Eris).

(Solved) CWM Problems

I am trying to change my wifes rom on her phone and her trackball is broke. So I installed the latest version of CWM to see if it would enable and need features so I could navigate in recovery. No luck and now I can't back up her via rom manager either I just get an error. So what I am wondering is the an alternate way to work through cwm without the trackball and whats up with this error after I updated it. Thanks in advance for your help
The error is e: can't open /cache/update.zip
(Bad)
Installation aborted
Sent from my thunderbolt using XDA Premium App
superdusto said:
The error is e: can't open /cache/update.zip
(Bad)
Installation aborted
Sent from my thunderbolt using XDA Premium App
Click to expand...
Click to collapse
Make sure the backup file has no spaces between anything like backup-4627 not backup 4627 no spaces you'll get an error
Sent from my ERIS using Tapatalk
TheGratefulDead said:
Make sure the backup file has no spaces between anything like backup-4627 not backup 4627 no spaces you'll get an error
Sent from my ERIS using Tapatalk
Click to expand...
Click to collapse
That wasn't the problem just tried and am still getting the same error
Sent from my Thunderbolt using XDA Premium App
superdusto said:
The error is e: can't open /cache/update.zip
(Bad)
Installation aborted
Sent from my thunderbolt using XDA Premium App
Click to expand...
Click to collapse
I believe that this message implies that the download was bad (i.e., and incomplete file or a mis-matched MD5 signature).
I'm not that familiar with ClockworkMod or ROM manager, but have a peek at this thread: http://www.droidforums.net/forum/koush/47399-upgrade-rom-rom-manager-problem.html since it seems to describe what you are seeing.
If you are downloading your first directly to your phone, you can check your MD5 with Astro File Manager (long-press file name, select details, and wait a little bit for the MD5 checksum to appear).
You could also try my app, AFV (Android File Verifier). It has several checksum options, including MD5 and SHA1. You can use its "Verify Jar-type File" to verify the integrity of a signed file even if you don't know the MD5 checksum.
Cheers!
scary alien said:
I believe that this message implies that the download was bad (i.e., and incomplete file or a mis-matched MD5 signature).
I'm not that familiar with ClockworkMod or ROM manager, but have a peek at this thread: http://www.droidforums.net/forum/koush/47399-upgrade-rom-rom-manager-problem.html since it seems to describe what you are seeing.
If you are downloading your first directly to your phone, you can check your MD5 with Astro File Manager (long-press file name, select details, and wait a little bit for the MD5 checksum to appear).
You could also try my app, AFV (Android File Verifier). It has several checksum options, including MD5 and SHA1. You can use its "Verify Jar-type File" to verify the integrity of a signed file even if you don't know the MD5 checksum.
Cheers!
Click to expand...
Click to collapse
I am not downloading a rom I have the rom. So that doesn't help much. Any other ideas? no recovery options that doesn't use track ball?
superdusto said:
I am not downloading a rom I have the rom. So that doesn't help much. Any other ideas? no recovery options that doesn't use track ball?
Click to expand...
Click to collapse
Yeah, sorry...I wasn't exactly sure...
I know that ClockworkMod lets you navigate its menus without using the trackball, but most rooted folks use Amon_RA's custom recovery.
A while back, I created a trackball-optional version of Amon_RA's recovery for the Eris. Here's the thread I created over on AF re. this:
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
Here's the post in RA's thread over here on XDA: http://forum.xda-developers.com/showpost.php?p=9124095&postcount=83
Hope this helps!
Cheers!
Not sure if this helps but I had the same problem when I flashed my friend fascinate. But they use odin to flash their clockwork (voodoo) I had to run the root script then install the rom to fix the update.zip. Any ideas?
superdusto said:
Not sure if this helps but I had the same problem when I flashed my friend fascinate. But they use odin to flash their clockwork (voodoo) I had to run the root script then install the rom to fix the update.zip. Any ideas?
Click to expand...
Click to collapse
lol...sorry, no. I've only heard that Odin (timely Thor-related reference, eh? ) is used for the Samsung phones.
There are others around that know and have used ClockworkMod on the Eris, but they are relatively few and far between (plus, things certainly seem to be slowing down in the various Eris forums recently). There have also been some unexplained brickings of phones using CWM that have scared off potential users of that custom recovery, so most have stayed with and use Amon_RA's.
scary alien said:
lol...sorry, no. I've only heard that Odin (timely Thor-related reference, eh? ) is used for the Samsung phones.
There are others around that know and have used ClockworkMod on the Eris, but they are relatively few and far between (plus, things certainly seem to be slowing down in the various Eris forums recently). There have also been some unexplained brickings of phones using CWM that have scared off potential users of that custom recovery, so most have stayed with and use Amon_RA's.
Click to expand...
Click to collapse
Well thanks for your help so far is their a post on how to set up adb so I can flash Amon_RA. I think my problem is that I rooted with amon and just downloaded rom manager so I put CWM on it.. Must be affecting my update.zip
superdusto said:
Well thanks for your help so far is their a post on how to set up adb so I can flash Amon_RA. I think my problem is that I rooted with amon and just downloaded rom manager so I put CWM on it.. Must be affecting my update.zip
Click to expand...
Click to collapse
Yes, at the bottom of the first post in the AF forum thread are the installation instructions and one of them is how to do it with adb ("Scenario 4").
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
Sounds like you are already familiar with adb, so you should be very close .
Let me know if you need anything else.
Cheers!
You saved me Thank you so much for your time here have some thanks!!!
superdusto said:
You saved me Thank you so much for your time here have some thanks!!!
Click to expand...
Click to collapse
You are most welcome! Glad you got things going .
I keep getting these warm-and-fuzzies from folks that my efforts for building the trackball-optional recovery was well worth it (with kudos and thanks again to RA for his help in filling-in the key gaps in how to build it).
Cheers!
My trackball has not worked pretty much since I bought the phone. I have found is you plug in your usb charger and lift up firmly the trackball works with no issues at all. Just FYI. And here's to the dev's that keep our end of life eris fast and up to date. And no sense thank GOD. lol
Yep, that is a definite way to work it ... I was unable to ROOT for over 2 months after getting my Eris b/c my trackball didn't work. It wasn't until I found this advice over in DF that I was finally able to negotiate the recovery menu.
HOWEVER (!!!) After almost a year of moderate flashing/recovery use, my USB/AC charger barely works anymore. I have to put weight on the USB near the connec w/ the phone to get it to recognize & charge.
I have tried to install the Amon_ra trkball not req script but couldn't get it to work ... I just use CWM these days b/c I don't need to use the damn thing !
Good thing I am coming up for an UPGRADE
Sparticusx said:
My trackball has not worked pretty much since I bought the phone. I have found is you plug in your usb charger and lift up firmly the trackball works with no issues at all. Just FYI. And here's to the dev's that keep our end of life eris fast and up to date. And no sense thank GOD. lol
Click to expand...
Click to collapse

Stuck in Bootloop, not sure how to fix it.

Hey everyone,
So I was extracting the framework-res.apk to replace the battery .pngs. Everything was going fine but when I was replacing the framework-res.apk in Root Explorer the nook rebooted and thus has sent me into a bootloop. I tried reverting to stock using the sdcard method but it boots into CWM. Not sure if the acclaim_update.zip can be used in CWM i tried anyway getting the error "asset failed: (ro.product.device") == "blaze"
So basically I am extremely stuck. Any suggestions?
Get in CWM and plug your device to the machine you used for root or working nook drivers, in CWM go to mounts and storage> and mount /system, take the stock or custom framework-res.apk and put it in C:\ntroot ( where adb should be) , it will look like this C:\ntroot\framwork-res.apk , open CMD as administrator and run:
Code:
> cd C:\ntroot
> adb devices (Check if your device really gets recognized)
> adb push framework-res.apk /system/framework
Good Luck!
~ Veronica
I went through the process and after a reboot it now is going into a faster bootloop. So I was researching a bit deeper and came across your post on the same process for the /system folder with the acclaim.zip. I went through that process also replacing all folders and still am in a bootloop. I know the adb is pushing properly. Sorry, Im still learning. Your help is greatly appreciated.
Maybe format /system folder and start from strach in CWM? Also what exact folders need replaced?
heric1 said:
I went through the process and after a reboot it now is going into a faster bootloop. So I was researching a bit deeper and came across your post on the same process for the /system folder with the acclaim.zip. I went through that process also replacing all folders and still am in a bootloop. I know the adb is pushing properly. Sorry, Im still learning. Your help is greatly appreciated.
Maybe format /system folder and start from strach in CWM? Also what exact folders need replaced?
Click to expand...
Click to collapse
Well you just messed up with framwork-res.apk which is located in /system/framework folder so that means only the framework folder. Unmount system, wipe cache, dalvik cache and fix permissions i CWM or in adb you fix permissions like this
Code:
adb shell chmod 644 /system/framework/*.apk
and change owner like this:
Code:
chown root /system/framework/*.apk
Good luck!
~ Veronica
Still not working, just constantly rebooting. I am honestly so stumped. Is there any way I just can restore?
heric1 said:
Still not working, just constantly rebooting. I am honestly so stumped. Is there any way I just can restore?
Click to expand...
Click to collapse
When you installed CWM did you make a backup? possibly if so try making a restore, if not then try a hard factory reset , thought i don't know if that or the acclaim_update.zip might work with the CWM we have. I personally did not installed CWM and won't because of this kind of things still for me is not fully tested perhaps not really a must for now. I have tested the adb method while in CMW in my smartphones there is still things to fix in the nook tablet.
Bed time catch you tomorrow, wish you luck!
~ Veronica
Yeah silly me, didn't create a backup in CWM. Also I cannot do a hard factory reset as the bootloop is so fast, it barely reaches the 'read forever' logo. I honestly do not know what I can even do at this point until wait for a custom ROM to flash over everything in CWM. I also PMed Zapcorns who is having a similar issue. Regardless thanks so much thus far and hopefully someone has a fix.
I forgot to tell you to try a wipe data too in CWM, cross fingers. Hopefully that makes it
~ Veronica
Sent from XDA premium using my Nook Tablet
Sadly nope, still stuck.
Well, if it makes you feel any better mine doesn't even loop. It boots to the "read forever" and then just stays there. I'm going to try flashing the acclaim_update zip because that's the only thing I've read so far that might fix it. If it works I will let you know...but I have a sinking feeling I'm screwed.
Can you boot into CWM? If so I think your far from screwed. If you don't have CWM installed you should be able to revert to stock via the sdcard method. I just feel stuck in limbo as I can not revert to stock recovery nor can I flash a ROM as they dont exist yet.
I can get to CWM recovery but now it's just a matter of finding a flashable zip that will undo what my stupidity has wrought. It's encouraging to hear I may not be totally SOL.
Edit: I think we may be in the exact same state. I can't do the factory reset either. All I can do is boot to CWM for now. I did manage to experiment with Indirect's gapp zips and get those to flash.
Denmmurray said:
I can get to CWM recovery but now it's just a matter of finding a flashable zip that will undo what my stupidity has wrought. It's encouraging to hear I may not be totally SOL.
Edit: I think we may be in the exact same state. I can't do the factory reset either. All I can do is boot to CWM for now. I did manage to experiment with Indirect's gapp zips and get those to flash.
Click to expand...
Click to collapse
Did you make a CWM backup when you installed it? or you did not too, the last 2 options that you guys have is try to get a clean CWM backup from a user(Still could simply not work) or try Goncezilla sdcard method to flash stock recovery so bye bye CWM and then try to flash the acclaim_update.zip.
Good Luck to both of you, and hope you learn the lesson and don't mess up around without be cautious.
~ Veronica
Asking for boot.img might be a bit much, plus you said it still has a possibility of not working. I was looking over Goncezilla's post but not quite understanding how to do the process with stock recovery instead of CWM? And also worst case scenario I am assuming when ROMs start coming out I can just flash one over this mess?
Once again thanks and this has been quite a learning experience.
heric1 said:
Asking for boot.img might be a bit much, plus you said it still has a possibility of not working. I was looking over Goncezilla's post but not quite understanding how to do the process with stock recovery instead of CWM? And also worst case scenario I am assuming when ROMs start coming out I can just flash one over this mess?
Once again thanks and this has been quite a learning experience.
Click to expand...
Click to collapse
Have you tried the CWM backups from this site in the ROM's sections - they are NOT flashable zips!
~ Veronica
Never been so happy to see my homescreen! Worked perfectly. Thank you so much for that link and your patience.
heric1 said:
Never been so happy to see my homescreen! Worked perfectly. Thank you so much for that link and your patience.
Click to expand...
Click to collapse
Cool, glad it worked.
Here thank this Guy for take the tame to root with both both methods and upload them
http://forum.xda-developers.com/showpost.php?p=21748940&postcount=57
Sent from XDA premium using my Nook Tablet
lavero.burgos said:
Get in CWM and plug your device to the machine you used for root or working nook drivers, in CWM go to mounts and storage> and mount /system, take the stock or custom framework-res.apk and put it in C:\ntroot ( where adb should be) , it will look like this C:\ntroot\framwork-res.apk , open CMD as administrator and run:
Code:
> cd C:\ntroot
> adb devices (Check if your device really gets recognized)
> adb push framework-res.apk /system/framework
Good Luck!
~ Veronica
Click to expand...
Click to collapse
Where can I get the nook tablet 8gb drivers so I could try this? can you post a link?
mysteriousme said:
Where can I get the nook tablet 8gb drivers so I could try this? can you post a link?
Click to expand...
Click to collapse
If you're stuck in a boot loop, this YouTube vid by raywaldo might help get you out of it:
http://www.youtube.com/watch?v=ZIrgkjen8ro&feature=related

Categories

Resources