Related
I am not new to any of this, but I am having a problem. VZW is sending me an Incredible, so I need to unroot. I used 2 different methods, both of which failed. Can someone please give me a hand or link me to some other options?
These are the methods I have tried:
http://forum.xda-developers.com/showthread.php?p=8315870
and
http://www.droid-eris.com/tutorials-corner/%28tutorial%29-how-to-unroot-your-droid-eris/
Perhaps you could state what problem you experienced when you tried using the Flashback21 ROM; the only thing that it requires is the Amon_RA recovery (Clockwork is not supported). Other than that, it should flash like any other ROM.
You might also want to mention what the exact bootloader version you have on your phone, whether or not you can use your trackball (for up/down/press actions) without too much trouble.
bftb0
bftb0 said:
Perhaps you could state what problem you experienced when you tried using the Flashback21 ROM; the only thing that it requires is the Amon_RA recovery (Clockwork is not supported). Other than that, it should flash like any other ROM.
You might also want to mention what the exact bootloader version you have on your phone, whether or not you can use your trackball (for up/down/press actions) without too much trouble.
bftb0
Click to expand...
Click to collapse
I was thinking the same thing, how can one help with that little info
btw bftb0, thank you for all the help with the uber technical issues around here. Your knowledge is very much appreciated, yeah I'll say it, thank you bftb0
I do have amon-ra recovery. When I flashed it aborted. The error message states a corrupt file. My phone is rebooting now. I am going to reflash to tell you the exact corrupt file. Give me a minute?
escalavee said:
I do have amon-ra recovery. When I flashed it aborted. The error message states a corrupt file. My phone is rebooting now. I am going to reflash to tell you the exact corrupt file. Give me a minute?
Click to expand...
Click to collapse
Did you try re-downloading the file at all?
E: corrupt file: system/framework/com.htc.resources.apk
E: verification failed.
I am redownloading now. I thought of that a few minutes ago.
Yes, I have full use of the track ball. I don't know what bootloader version I have, and it is rebooting again, so I can't check right now...
Thank you for trying to help!
ETA: HBOOT v 1.49
recovery v 1.6.2
radio 2.42.01.04.27
escalavee said:
E: corrupt file: system/framework/com.htc.resources.apk
E: verification failed.
I am redownloading now. I thought of that a few minutes ago.
Yes, I have full use of the track ball. I don't know what bootloader version I have, and it is rebooting again, so I can't check right now...
Thank you for trying to help!
ETA: HBOOT v 1.49
recovery v 1.6.2
radio 2.42.01.04.27
Click to expand...
Click to collapse
If it doesn't work this time, download it with a different web browser.
gnarlyc said:
If it doesn't work this time, download it with a different web browser.
Click to expand...
Click to collapse
Will do. Thanks.
What happened? I can't access the page now to redownload...
I said screw it and tried to open it with IE, and I got a 404.
Nevermind. I got it. Durf.
escalavee said:
I do have amon-ra recovery. When I flashed it aborted. The error message states a corrupt file. My phone is rebooting now. I am going to reflash to tell you the exact corrupt file. Give me a minute?
Click to expand...
Click to collapse
bad download or you corrupted it when you transfered it from your pc.
Use AFV the from the market to verify the checksum of the zip file on the SD card.
When you transfer large files from the PC you always always need to perform a "safely remove hardware" before you unmount from the Eris or remove the USB cable.
bftb0 said:
bad download or you corrupted it when you transfered it from your pc.
Use AFV the from the market to verify the checksum of the zip file on the SD card.
When you transfer large files from the PC you always always need to perform a "safely remove hardware" before you unmount from the Eris or remove the USB cable.
Click to expand...
Click to collapse
Good to know! Thanks. I will try again and let you guys know.
Again, I really appreciate all the help.
workshed said:
btw bftb0, thank you for all the help with the uber technical issues around here. Your knowledge is very much appreciated, yeah I'll say it, thank you bftb0
Click to expand...
Click to collapse
+1 bftb0 helped me figure out my first bricked eris was fubar, more importantly helped me understand why, so the next time I had a soft brick I had taken the preemptive steps necessary to save it. Thanks bftb0
This is making me crazy!
Another corrupt file: system/framework/framework.odex
I did safely remove hardware, and this download was done on IE instead of FF.
I am going to keep trying until I get this done.
USSENTERNCC1701E said:
+1 bftb0 helped me figure out my first bricked eris was fubar, more importantly helped me understand why, so the next time I had a soft brick I had taken the preemptive steps necessary to save it. Thanks bftb0
Click to expand...
Click to collapse
Hey I saw the post about the thanks cherry... that made me giggle on the inside a little...
ETA: I am a dirty lurker...
Try flashing a different custom ROM, possible your recovery has become corrupted. If flashing another ROM doesn't work reinstall AmonRA and try FlashBack again. If it does work, I'd try FlashBack again, just for ****s and giggles.
Hey do I need the radio image? I can try downloading the one without the radio image...
USSENTERNCC1701E said:
Try flashing a different custom ROM, possible your recovery has become corrupted. If flashing another ROM doesn't work reinstall AmonRA and try FlashBack again. If it does work, I'd try FlashBack again, just for ****s and giggles.
Click to expand...
Click to collapse
You know, I tried flashing nonsensikal 15.2 a couple days ago, and I kept getting a corrupt file error with that as well.
Maybe my recovery IS corrupted!
This is insane.
USSENTERNCC1701E said:
Try flashing a different custom ROM, possible your recovery has become corrupted. If flashing another ROM doesn't work reinstall AmonRA and try FlashBack again. If it does work, I'd try FlashBack again, just for ****s and giggles.
Click to expand...
Click to collapse
Do I have to uninstall my old version of amon-ra before I reinstall?
escalavee said:
This is making me crazy!
Another corrupt file: system/framework/framework.odex
I did safely remove hardware, and this download was done on IE instead of FF.
I am going to keep trying until I get this done.
Click to expand...
Click to collapse
Uh, I know you are in a hurry, but ...
It is impossible for Amon_RA to install a corrupted ROM file.
Read that again: It is impossible for Amon_RA to install a corrupted ROM file.
If it passes the verification step in Amon_RA, then the ROM .zip file is OK
Now, if something fails during the install, then there are three possible causes:
- The SD card is flaky, and file reads are erratic (which could allow the verification pass in Amon_RA to succeed, but the subsequent read to fail).
- Prior operations on the phone have corrupted one or more partitions on the phone so that insufficient space remains in the partition you are writing to.
- Flaky hardware.
Does the error with the specific file you mentioned happened during verification or afterwards during the install process?
bftb0
BTW, there are two different "1.49.nnnn" bootloaders - you need to be precise.
escalavee said:
Hey do I need the radio image? I can try downloading the one without the radio image...
Click to expand...
Click to collapse
escalavee said:
Do I have to uninstall my old version of amon-ra before I reinstall?
Click to expand...
Click to collapse
Not unless you have flashed a new radio at some point, and I would recommend avoiding that. I've lost recovery twice, one of the times I was able to just use jcase's 1 Click Eris Root and the other time I had to reflash the recovery, try the 1 Click first, I need to research the procedure for a Terminal Emulator flash again, last time I used FastBoot instead.
Nevermind, I'd follow bftb0, he's far wiser, and I was doing some rather whimsical stuff with my phone and KGB when I lost my recovery.
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
Hey, everyone. I know this is probably the last thing you want to read, but I could really use some prompt help.
I tried the method posted in: http://forum.xda-developers.com/showthread.php?t=1686551
I got to step 3, but it didn't let me choose recovery. It just started installing the update. However, when it rebooted, it never got past the white HTC boot screen. I pulled the battery, pulled the MicroSD card, went back into the bootloader and tried running Factory Reset. Same result - stuck at white HTC boot screen.
Some more information:
1. Device is completely stock - no customer bootloader, stock Gingerbread OS. (2.3.4. That's why I wanted to try this in the first place. According to HTC, my IMEI number block hasn't been updated for ICS, yet.)
2. I renamed the file "update" as per the thread.
I'm hoping that the devs and contributors here will have mercy on a lowly noob who's having problems. I'm hoping to either return to stock and wait for the ICS update, or get to the point where I can install a custom ROM found here. (I was thinking SpeedROM). But, as my device has Gingerbread (or, potentially nothing at this point), I'm not sure where to go from here.
Thanks so much for any suggestions. You guys are the best, and I love this site.
Not sure if you've tried this yet, just name your file as PH85IMG.zip and place it on your microSD. Boot into bootloader and let it run the update. If this is what you did, then I have no clue what happened.
Just out of curiosity, why didn't you get the official OTA the official way if you're completely stock?
PS - This question belongs in the Q&A subforum. Remember that next time if you don't want to get flamed =)
kered424 said:
Not sure if you've tried this yet, just name your file as PH85IMG.zip and place it on your microSD. Boot into bootloader and let it run the update. If this is what you did, then I have no clue what happened.
Just out of curiosity, why didn't you get the official OTA the official way if you're completely stock?
PS - This question belongs in the Q&A subforum. Remember that next time if you don't want to get flamed =)
Click to expand...
Click to collapse
Thanks! I'm trying that now.
And, I appreciate the advanced notice. Is there a way I can transition the thread, so as to avoid further confrontation?
takingflight005 said:
Thanks! I'm trying that now.
And, I appreciate the advanced notice. Is there a way I can transition the thread, so as to avoid further confrontation?
Click to expand...
Click to collapse
It happens. No worries, the Mods will move it for you.
kered424 said:
Not sure if you've tried this yet, just name your file as PH85IMG.zip and place it on your microSD. Boot into bootloader and let it run the update. If this is what you did, then I have no clue what happened.
Just out of curiosity, why didn't you get the official OTA the official way if you're completely stock?
PS - This question belongs in the Q&A subforum. Remember that next time if you don't want to get flamed =)
Click to expand...
Click to collapse
The official update just never showed up. I literally lost count of the number of times I went into Settings > About phone > HTC software updates > Check now.
I've been on probably 4 chats and 4-5 calls between T-Mobile customer service and HTC tech support. The general consensus is that my phone's IMEI number is in a block that hasn't been authorized for the ICS update, yet. But, I really wanted to upgrade, and I think it's ridiculous that it's been 2 months since the update and my phone can't.
Ok, so I'm first going to apologize, since I've heard that double-posting is very much not accepted by forum communities.
I've tried several times to fix this. I renamed the file as was suggested, and went back into the bootloader. It (apparently) scans the MicroSD card for files, and says "Loading...[PH85IMG.zip]" (It attempts to load PH85DIAG.zip, says no image, and PH85IMG.nbh, and again says no image)
After this, it says "Checking..[PH85IMG.zip]" (That is the only thing it says)
Then, I get the options:
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
If I go into FASTBOOT, it doesn't really help - just reboots either the bootloader (repeating this process, obviously) or the phone, which goes back to the white HTC boot screen it's hanging on.
If I go into RECOVERY, there's not option to install the .zip like the other page suggests, but if I try "Install update from SD card" it gives me "Illegal operation" and reboots.
If I go to FACTORY RESET, it acts like it's reinstalling, but leads to the same problem.
I'm thinking that I just nuked the phone's internal storage, and completely deleted the original OS. Any ideas on how to resolve that?
Or, if that's not the problem, where should I go from here?
It's funny....I troubleshoot computers for a living....but I'm lost right now on this phone.
Thank you for the continued help, gents! I'd really like to not have to throw away a $350, brand new phone....
I would guess you have one of the 3
the wrong carrier's ruu
A bad download of ruu
Renamed wrong (maybe you added ".zip" when it already had the ext but is just hidden by windows 7)
Sent from my SGH-T999 using xda premium
glacierguy said:
I would guess you have one of the 3
the wrong carrier's ruu
A bad download of ruu
Renamed wrong (maybe you added ".zip" when it already had the ext but is just hidden by windows 7)
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hm....well, it's not the third. I doubt the first, unless the wrong file was linked in the thread I mentioned. I'll try downloading the file again.
So, if this still doesn't work for me, let's attack this from a different angle. Are there any other options? Could I change the bootloader, install the leaked ICS ROM, then install another one after that? Like I said, I had been considering trying out Project Butter Speed ROM. I know that the instructions for all that are in the Amaze Bible thread, but there's such a large volume of data there, it's hard to sift through.
Edit: Re-downloaded the file; no change. Any more suggestions?
I've been away a while, but if my memory serves me correct, to install it using ph85img, you must first relock your bootloader. are you locked or unlocked right now?
aj_2423 said:
I've been away a while, but if my memory serves me correct, to install it using ph85img, you must first relock your bootloader. are you locked or unlocked right now?
Click to expand...
Click to collapse
I never unlocked or modified the bootloader in any way. That's why I thought this would work. My impression was that basically everything had to be stock.
takingflight005 said:
I never unlocked or modified the bootloader in any way. That's why I thought this would work. My impression was that basically everything had to be stock.
Click to expand...
Click to collapse
I think you need to reconsider the name of your file. If it shows up as PH85IMG.zip, more likely than not, it is actually named PH85IMG.zip.zip
This is due to how Windows reads files. If the file is of a known file type, it will not show up the extension (even though it IS there).
Try renaming it to PH85IMG and then put it in the root directory of the SD card and then boot into bootloader. It *should* read it.
Keylogger_0 said:
I think you need to reconsider the name of your file. If it shows up as PH85IMG.zip, more likely than not, it is actually named PH85IMG.zip.zip
This is due to how Windows reads files. If the file is of a known file type, it will not show up the extension (even though it IS there).
Try renaming it to PH85IMG and then put it in the root directory of the SD card and then boot into bootloader. It *should* read it.
Click to expand...
Click to collapse
I'm a computer support tech. Trust me, I did not add an extra file extension, lol. Windows does indeed recognize it as a zip file, so I know the extension is properly set. Name is just set to "PH85IMG"
Not trying to sound like a jerk; just making sure people know where I'm coming from.
takingflight005 said:
I'm a computer support tech. Trust me, I did not add an extra file extension, lol. Windows does indeed recognize it as a zip file, so I know the extension is properly set. Name is just set to "PH85IMG"
Not trying to sound like a jerk; just making sure people know where I'm coming from.
Click to expand...
Click to collapse
I understand that, but if you read through the Q&A section, you'll know why I imperatively make that statement. Can you link me to which file you're trying to flash? I'm thinking it might be a wrong file you're trying to flash.
When you flash or update via a stock ruu, it may seem stuck but it isn't, first boot always takes time, read through this thread properly when I get home, the guys seems to be here, so I'm not needed anyways.
Sent from a Galaxy flowing with Jelly Beans.
Keylogger_0 said:
I understand that, but if you read through the Q&A section, you'll know why I imperatively make that statement. Can you link me to which file you're trying to flash? I'm thinking it might be a wrong file you're trying to flash.
Click to expand...
Click to collapse
http://www.4shared.com/zip/V4cIZsvx/OTA_RUBY_ICS_35_S_TMOUS_214531.html
takingflight005 said:
http://www.4shared.com/zip/V4cIZsvx/OTA_RUBY_ICS_35_S_TMOUS_214531.html
Click to expand...
Click to collapse
Try this one. It's the latest one out there. Link is here
Don't forget to give thanks to krook6023 for providing this.
His original thread is here http://forum.xda-developers.com/showthread.php?t=1617644
Anyways, download that one, then rename it to PH85IMG, put it in the microSD card and then boot into bootloader. It should work. Let us know if it does not.
That one worked! The original file I was trying never propmpted me to update. This one went off without a hitch.
Again, my great thanks to everyone in the thread!
Sent from my HTC_Amaze_4G using xda app-developers app
takingflight005 said:
That one worked! The original file I was trying never propmpted me to update. This one went off without a hitch.
Again, my great thanks to everyone in the thread!
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Glad you're up and going. FileFactory has such ****ty download speeds that its possible something became corrupt in the 4 hours or so that it took to download the original. I had a similar issue. Enjoy your ICS man!!!
Sent from my SGH-T999 using xda premium
glacierguy said:
Glad you're up and going. FileFactory has such ****ty download speeds that its possible something became corrupt in the 4 hours or so that it took to download the original. I had a similar issue. Enjoy your ICS man!!!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks! I am really enjoying the new features. Many things that, after I use them, I think "That should have been the way right from the beginning."
The one thing I would like is the stock ICS notification bar....but then, that's why I rooted, isn't it?
takingflight005 said:
The one thing I would like is the stock ICS notification bar....but then, that's why I rooted, isn't it?
Click to expand...
Click to collapse
There's a mod for that
Check themes and apps section
Sent from my SGH-T999 using xda premium
If anyone here could offer any tips or advice, I would appreciate it.
I opened my gTab up to resolder the charge port and all went well. I am a very meticulous person. I even take pictures, go slow and do not make dumb mistakes. But... somewhere I did make a mistake, I guess.
Charge port connector works fine now. Wiggle the charge cable and no interruption or blinking on the indicator light.
But... after putting the motherboard back in and testing it, It sticks at the birds. Thought SOMEHOW I must have bricked it because the charge port repair went perfectly. All connectors snugly in their place and oriented correctly.
I have VeganTab 7.0 Ginger and an older CWM on it (non touch). (or rather I did) So I tried to redo a new rom, booting into CWM. I get the standard "recovery key detected" and "booting recovery kernel image" messages at top left.
But, it just sticks there.
So I decided to try the NVFlasher method here: http://raywaldo.com/2011/01/nvflash-for-dummies/
I tried both the 250 and 300 meg partition file.
Wow... went right into APX mode. (I did not expect it to) I ran the nvflasher file and it seemed to finish correctly and successfully.
When I tried to boot into the newer CWM that's in the package, I still see the older CWM come up and it sticks there as it did before.
I tried rewriting files a couple more times but got the same results.
Part of the prob is I guess, is that I don't remember what bootloader was on ot. 1.1 or 1.2.
Also... does the fact that the nvflasher could write to the internal sd card mean that it is ok and I did not screw something up when I did the charge port repair? Well... I mean, I can not verify that it wrote correctly but it seemed to and said "completed successfully".
I was supposed to be selling this to a lady at the Moose lodge today. She has already paid me money on it
Can anyone help me out here or is all lost?
Thank you for your time,
John Dumas
pede69 said:
I opened my gTab up to resolder the charge port and all went well. I am a very meticulous person. I even take pictures, go slow and do not make dumb mistakes. But... somewhere I did make a mistake, I guess.
Click to expand...
Click to collapse
Did you take the appropriate anti-ESD (electrostatic discharge--static electricity) precautions whilst working on the board? Other people here have--from their problem descriptions which match yours--I think, fried some component on their board while fixing the same charge port problem.
Part of the prob is I guess, is that I don't remember what bootloader was on ot. 1.1 or 1.2.
Click to expand...
Click to collapse
If you do a full nvflash (and the images were written correctly), then bootloader version doesn't matter since the bootloader and the kernels in the images will match.
Also... does the fact that the nvflasher could write to the internal sd card mean that it is ok and I did not screw something up when I did the charge port repair? Well... I mean, I can not verify that it wrote correctly but it seemed to and said "completed successfully".
Click to expand...
Click to collapse
Nvflash does not write to the internal SD card--only CWM or the ROM can manipulate it. Nvflash only works on the built-in NAND flash chip. Ie. There are 2 separate storage devices on the gTab.
Ordinarily, based on the on-screen error messages, I would've said that it was a bootloader/kernel mismatch problem, but, this quote of yours below makes me think that it might be a NAND flash problem:
When I tried to boot into the newer CWM that's in the package, I still see the older CWM come up and it sticks there as it did before.
I tried rewriting files a couple more times but got the same results.
Click to expand...
Click to collapse
Both Recovery and the ROM kernel are read from the NAND flash and then is booted into. So, if you can't get into CWM, then you'll have to:
1. Check if the NAND flash is OK by writing to the device partitions and then reading the important partitions back and comparing the resulting image files byte-for-byte. See this post for the read command to be used after doing a full nvflash.
2. If the NAND flash checks out OK, then use a custom kernel which prints diagnostics to see if it detects any other HW problems. See this post for that. The modified kernel is for bootloader version 1.1 only, so you'll have to be on that bootloader to run it.
Awesome reply... Thank you.
I have formated using nvflash and went to write the file but the zip file that I downloaded did not have a bat file in it to tell nvflash what to do. The files came from here:
http://forum.xda-developers.com/showthread.php?t=861950 >>> "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Neither has a bat file to start an nvflash write.
And no, I did not use an anti-static bag. I know it can happen but I have been repairing computers for 20 years and have not zapped anything yet
I'm getting confused now. Can you point me to the correct file to load with nvflash?
Oh yeah... how do I figure out which bootloader I'm on?
You are most awesome for helping, thank you very much.
John
pede69 said:
I have formated using nvflash and went to write the file but the zip file that I downloaded did not have a bat file in it to tell nvflash what to do. The files came from here:
http://forum.xda-developers.com/showthread.php?t=861950 >>> "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Neither has a bat file to start an nvflash write.
Click to expand...
Click to collapse
According to that thread, it does. The file is called "nvflash_gtablet.bat". You might try to: open a CMD.exe window, change to the correct directory and then type: .\nvflash_gtablet
And no, I did not use an anti-static bag. I know it can happen but I have been repairing computers for 20 years and have not zapped anything yet
Click to expand...
Click to collapse
"Yet"--Always a first time, no?
Oh yeah... how do I figure out which bootloader I'm on?
Click to expand...
Click to collapse
As I said, if you do a full nvflash (ie. create, format, and write all the partitions on the NAND flash), then bootloader version does not matter, as the nvflash zip package will have the bootloader and the correct boot and recovery kernels in the image files to match that bootloader. Still, if you want to determine your bootloader version, see this thread.
What you should do first is write bekit's nvflash package to the NAND, then read the important partitions back, then do a byte-compare. I don't use, or have, Windows, but, I recall a MS-DOS command called fc which might still be present on the newer Windows variants:
Code:
C:\SOME\PATH> [B]fc /b [I]file1.img[/I] [I]file2.img[/I][/B]
Do a file compare using fc on the original image file and the read-back image file. If fc reports that one of the files is smaller/larger but reports no differences, then that's OK because a NAND partition read using nvflash reads the whole partition and not just the image that needs to be written to that partition.
If fc reports that the files are the same, then you can move on to step 2 of post #2.
Thanks again for the info. I will try to absorb and apply what you suggest.
BTW... I only asked the bootloader question because of what you mentioned above... "custom kernel which prints diagnostics - only works with 1.1"
Thank you for being there for me. I'll see what I can do now.
John
PS - Here are the unzipped files from nvflash_gtablet_2010110500.zip
pede69 said:
BTW... I only asked the bootloader question because of what you mentioned above... "custom kernel which prints diagnostics - only works with 1.1"
Click to expand...
Click to collapse
If you write bekit's image files, then you'll be on a 1.1 bootloader.
PS - Here are the unzipped files from nvflash_gtablet_2010110500.zip
Click to expand...
Click to collapse
As the thread says, you need to download two zip files. The batch file is in the other one: nvflash_windows_20100500.zip.
OK... I ignored the windows one because there are no instructions to use it and I thought it was for setting up APX on Windows. So I will re-read the instructions again and see what I may have overlooked, and If I can figure out how to use the both of them.
Thank you,
John
OK... after I get my foot out of my mouth, I'll give it a whirl.
J
Well... put contents of both zip files in one folder and ran nvflash.
Said "Completed successfully"
Still boots to old CWM.
Will go read your other instructions now...
J
Well...
Linux is failing to complete.
The following link has some pics from the gTab screen and also three .img files that was created when running the command on the linked page you referred me to. I could not find a txt file that it created.
.\nvflash --bl bootloader.bin --read 4 ebt.img --read 9 rec.img --read 10 lnx.img
http://jaxehost.com/gtab/
So... I guess all is lost. Not sure how to proceed now.
Thanks,
John
pede69 said:
Said "Completed successfully"
Still boots to old CWM.
Click to expand...
Click to collapse
I'm slighty puzzled now--can you elaborate on this: How did you determine that your CWM is unchanged when you're always stuck at the 3 birds screen? Ie. When the gTab isn't booting into CWM where its version can be seen.
I had assumed thus far that you were going by the "Recovery key detected" & "Booting recovery kernel image" messages. Those are bootloader messages (not CWM!) and depending on the bootloader installed you can sometimes differentiate between different bootloaders by looking at what message is printed. But, this is not a definitive method as many bootloaders print the same messages.
pede69 said:
Linux is failing to complete.
The following link has some pics from the gTab screen...
...
So... I guess all is lost. Not sure how to proceed now.
Click to expand...
Click to collapse
The kernel is stopping at the same place as it is here. Except that it is taking ~20 seconds more than is usual to do so. I have to say that this is a HW problem--probably something on the board. The NAND might still be OK, though.
Inspect the place where you soldered, and around it, for stray solder traces or bridges. Otherwise, something on the board has gotten borked. Sorry.
Hey
Guess I'm giving up and giving the person their money back. Damn, I needed it...
What I was saying is that when I installed the old CWM, I used to access it my pressing the power + volume up button. I thought what I see now is what I seen before when it started it but I may be wrong.
Guess I'll koad bekit back on it.
So is there a file to load JUST the CWM script using nvflash?
Also... is there a diag program that I use nvflash to load that will do a NAND and SD Card test?
Thanks for everything,
John
pede69 said:
Guess I'm giving up and giving the person their money back. Damn, I needed it...
Click to expand...
Click to collapse
Technically, the tablet might not yet be a total loss. The error messages indicate that the soft-key controller (SO340010) is failing to respond. Assuming that this is the only HW problem (a big assumption--there might be other things wrong on the board), the kernels (both in the ROM and in CWM) could then be recompiled without that soft-key device driver. Neither CWM nor the newer ICS+ ROMs require those soft-keys anyway. If the new kernels boot, then the soft-key controller is the only problem. Otherwise, the error messages will again have to be looked at to see what else has failed.
As you can see, all this will involve a fair amount of diagnosing and work. You may be able to use the tablet because you know what's wrong and because you have a custom kernel for the ROM and CWM of your choice, however, I don't think the buyer would like to be stuck with only one choice of ROM. Also, if other critical controllers (the touchscreen or WiFi, for instance) have gone belly up, then there's little hope for any Android ROM.
What I was saying is that when I installed the old CWM, I used to access it my pressing the power + volume up button.
Click to expand...
Click to collapse
Recovery mode is always accessed using power and Vol +. These keys assignments, as far as I know, can't be changed.
Not entirely clear on what you're trying to say here...
So is there a file to load JUST the CWM script using nvflash?
Click to expand...
Click to collapse
This post.
Also... is there a diag program that I use nvflash to load that will do a NAND and SD Card test?
Click to expand...
Click to collapse
Because both the bootloader and both CWM and ROM kernels are loading and running, the NAND is very likely OK. If you want to check the NAND partitions, the standard method is to do a full nvflash, read back the partitions, then check the original and read-back images using fc as I've shown. Alternatively, you could try this technique (I haven't tried it, so tell me how well, or if, it works out):
Edit the batch file you're using to do the full nvflash, and add a --verifypart -1 to the nvflash command line, before the --create flag. Save and run the batch file as usual.
The SD card cannot be tested using nvflash. You need either CWM or a ROM for that.
Thanks rajeevvp...
I'll get back at this unit in a while. Between this and the S3 and Note II issues i'm going through, I need a break.
You any good with Verizon phones? hehe...
Thanks,
John
Thanks rajeevvp...
I'll get back at this unit in a while. Between this and the S3 and Note II issues i'm going through, I need a break.
You any good with Verizon phones? hehe...
Thanks,
John
pede69 said:
You any good with Verizon phones? hehe...
Click to expand...
Click to collapse
Sorry, no--can't help with hardware that I don't have.
Hello everyone, firstly I want to apologise for having my first post here be a forgettable and generic cry for help but I'm at my wits end and I hope that the community is nice enough; I would be very grateful. I rooted my phone as the idea really excited me as the phone had been really behaving erratically, since rooting it the phone performed brilliantly, I was thinking of installing CyanogenMod but it was lost on me, the entire process and caveats frightened me away... And I put my hands in the air admitting I probably didn't respect the process enough, thinking if the worse happened - c'est la vie! Well now it has and I'm feeling sick.
I rooted a few months ago, the Android version was 4.3. Basically I know what I've done and to quote Chromium himself in his thread for the app - I love the app, I'd done nothing at all exotic since rooting the phone - no custom ROM, no custom OS, just did it for the improved performance it affords, and I've been using Fontster all this time. Only recently, thinking I'm really clever I put a ttf font file on the phone via USB, a font that was unavailable in the app itself and thought nothing of it, promptly forgetting I ever did it to be honest.
Chromium said:
https://github.com/Chromium1/Fonts/raw/master/RestoreStockFonts.zip
This feature was available in one of the previous beta versions, but I decided to remove it from the app. One of the key points of this app is that it replaces all styles of fonts included in the rom and that I personally collected (or in some cases made) full sets of the fonts. In addition I edited the classifications of all the fonts so that they dont result in a bootloop when installed. If the user was able to pick their own files the classifications of the fonts will very likely be incorrect and they will soft brick their phone. Considering I already have a bunch of ignorant, uneducated reviews on the play store from people who failed to read the description, I cant imagine how much worse it would get if I left this option in the app.
Click to expand...
Click to collapse
I did not know this prior to I've done; last night I had grown tired of the font I had been using and started installing other fonts and had actually rebooted the phone a few times, and then I did it, didn't I? I must have chosen the font that I had put on the phone manually, the phone reboots and it hanged.
Since then, I've tried Odin and Kies. I needed to flash the stock recovery again and I have access to both Download and Recovery mode, Odin is detecting it all good and most of the internet is in agreement that as I have access to Download mode I am able to save the phone.
I have downloaded the stock ROM from multiple services, I currently have one downloading from http://samsung-updates.com/device/?id=GT-I9300 however but there is no mtd tar file no matter how many times I unzip the folder, using Windows' own file manager and 7zip, and there is no discussion about this anywhere on the Internet, though I am on Windows 8.1!?
Please help, I'm thinking I just need that mtd/tar file to be put in the PDA box?!
Additionally when in recovery mode there is red text -
E: failed to mount /system (Invalid argument)
can't mount '/system' (Invalid argument)
E: failed to mount /system (Invalid argument)
Am I boned?
Any advice or insight would be greatly appreciated; this has really opened my eyes to the pitfalls of dealing in something I have no idea about, I'm through and through a Windows techie.
When you extract the downloaded files what do you see in the folder?
Darke5tShad0w said:
When you extract the downloaded files what do you see in the folder?
Click to expand...
Click to collapse
Thank you DarkestShadow for your reply; it's still downloading (but going from memory; but I'll edit when it's finished) there was a boot image, a META-INF folder, a Modem file, a system file and others - I know this isn't thorough enough. From what I've seen on YouTube and from guides online once the zip is extracted it all becomes a single mtr5 / tar file. And that just isn't happening, it's perplexing as much as it is infuriating.
JJKirby said:
Thank you DarkestShadow for your reply; it's still downloading (but going from memory; but I'll edit when it's finished) there was a boot image, a META-INF folder, a Modem file, a system file and others - I know this isn't thorough enough. From what I've seen on YouTube and from guides online once the zip is extracted it all becomes a single mtr5 / tar file. And that just isn't happening, it's perplexing as much as it is infuriating.
Click to expand...
Click to collapse
Just did some quick research and if you don't get the tar file the stock rom zip can be flashed with recovery
Darke5tShad0w said:
Just did some quick research and if you don't get the tar file the stock rom zip can be flashed with recovery
Click to expand...
Click to collapse
Thank you very much. So if I am reading you correctly, if I can get the stock rom as a zip folder on the phone and flash via the stock recovery it should be good to go?
How would I go about getting the zip on the device? I have an SD card, although it has a lot of personal files which I don't want to lose. Could I use a tablet and computer connection to backup and get the stock rom zip on the SD card, put the SD card in my phone and then....??
JJKirby said:
Thank you very much. So if I am reading you correctly, if I can get the stock rom as a zip folder on the phone and flash via the stock recovery it should be good to go?
How would I go about getting the zip on the device? I have an SD card, although it has a lot of personal files which I don't want to lose. Could I use a tablet and computer connection to backup and get the stock rom zip on the SD card, put the SD card in my phone and then....??
Click to expand...
Click to collapse
Does not matter what method you choose as long as you get your personnel files off and get the zip in.
I did not realize you had stock recovery, so there is a chance it may not work. If not we will have to get you the proper odin type file.
Where are you from? what region/carrier stock are you trying flash on it?
JJKirby said:
Thank you very much. So if I am reading you correctly, if I can get the stock rom as a zip folder on the phone and flash via the stock recovery it should be good to go?
How would I go about getting the zip on the device? I have an SD card, although it has a lot of personal files which I don't want to lose. Could I use a tablet and computer connection to backup and get the stock rom zip on the SD card, put the SD card in my phone and then....??
Click to expand...
Click to collapse
Just take out your sd card and copy all your stuff to pc.then put the zip file on your sd card and flash it, but you do need custom recovry.
Sent from my C6603 using XDA Free mobile app
Arrowblue said:
Just take out your sd card and copy all your stuff to pc.then put the zip file on your sd card and flash it, but you do need custom recovry.
Sent from my C6603 using XDA Free mobile app
Click to expand...
Click to collapse
It is my understanding (And I could be wrong) you can flash stock zips with stock recovery? but of course you need custom recovery for anything else.
Darke5tShad0w said:
Does not matter what method you choose as long as you get your personnel files off and get the zip in.
I did not realize you had stock recovery, so there is a chance it may not work. If not we will have to get you the proper odin type file.
Where are you from? what region/carrier stock are you trying flash on it?
Click to expand...
Click to collapse
I am in the UK. I am downloading I9300XXUGMK6_I9300OXAGMK6_BTU.zip , but even so, it's the whole issue with the fact I can't see the tar / md5 file.
The phone is the Samsung GT-i9300 Galaxy SIII, it's carrier unlocked.
Although I am perfectly happy and confident in flashing a different recovery, I just want to make the phone usable again. I managed to flash the stock recovery no problem. I don't care about flash count and the warranty, I'm upgrading my contract soon anyway, I just need the phone obviously!
JJKirby said:
Although I am perfectly happy and confident in flashing a different recovery, I just want to make the phone usable again. I managed to flash the stock recovery no problem. I don't care about flash count and the warranty, I'm upgrading my contract soon anyway, I just need the phone obviously!
Click to expand...
Click to collapse
Then I suggest this one
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300/philz_touch_6.48.4-i9300.zip.md5
Thank you DarkestShadow you have really surprised me, thank you so much for your assistance. I mean it from the bottom of my heart. Okay so with this file, this will go in the PDA box of Odin yes? And then flash it to the phone, with that done I can then put the stock rom zip on the card, put the card in the phone, boot up to CWM and then presumably follow the on screen prompts?
In the mean time though, I will wait for the download of the zip to finish to see if there is a tar file, if not I will flash CWM and be straight back on here for further assistance which I hope you'll be happy to provide? Do I need to name the zip file of the stock rom anything?
Thanks again.
JJKirby said:
Thank you DarkestShadow you have really surprised me, thank you so much for your assistance. I mean it from the bottom of my heart. Okay so with this file, this will go in the PDA box of Odin yes? And then flash it to the phone, with that done I can then put the stock rom zip on the card, put the card in the phone, boot up to CWM and then presumably follow the on screen prompts?
In the mean time though, I will wait for the download of the zip to finish to see if there is a tar file, if not I will flash CWM and be straight back on here for further assistance which I hope you'll be happy to provide? Do I need to name the zip file of the stock rom anything?
Thanks again.
Click to expand...
Click to collapse
Of course I will continue to help.
Yes in pda, then if it does not auto restart into recovery shut phone off and hold Home, Volume up and Power buttons together. When you see the samsung logo, let go and you'll see it go into custom recovery.
Then choose install zip, storage/sdcard1 and the file should be there, does not need to be named anything special or changed at all just aslong as you recognize it then confirm.
Darke5tShad0w said:
Of course I will continue to help.
Yes in pda, then if it does not auto restart into recovery shut phone off and hold Home, Volume up and Power buttons together. When you see the samsung logo, let go and you'll see it go into custom recovery.
Then choose install zip, storage/sdcard1 and the file should be there, does not need to be named anything special or changed at all just aslong as you recognize it then confirm.
Click to expand...
Click to collapse
Thank you Darkest, probably another silly question; I can just chuck the zip anywhere on the SD card, regardless of all the crap Android has formatted on/for it? - like DCIM, Android etc. as long as it's in the root of the card and I know what it's named.
JJKirby said:
Thank you Darkest, probably another silly question; I can just chuck the zip anywhere on the SD card, regardless of all the crap Android has formatted on/for it? - like DCIM, Android etc. as long as it's in the root of the card and I know what it's named.
Click to expand...
Click to collapse
Nope it doesn't matter as you can navigate around to find it but in the root of the sdcard is the easiest
Darke5tShad0w said:
Nope it doesn't matter as you can navigate around to find it but in the root of the sdcard is the easiest
Click to expand...
Click to collapse
Okay then Darkest, finished downloading SGS3INT-XXUGMK6-BTU-20131216, extracted the zip and lo and behold I have the md5 file! As well as a dll file named SS_DL
Now what? I've completely forgotten, put that md5 file into the PDA box in Odin and commence the flashing, however if I wanted could I flash the custom recovery at a later date? If I intend on using custom OS's / rooting again / just for the ease of mind knowing it's a lot more thorough if I ever soft brick again.
I'm going to sleep now, it's 05:25AM for me, I hope that this help and advice and continue as I really appreciate talking with someone so versed in these matters, my friends and colleagues are all ****ing clueless!
JJKirby said:
Okay then Darkest, finished downloading SGS3INT-XXUGMK6-BTU-20131216, extracted the zip and lo and behold I have the md5 file! As well as a dll file named SS_DL
Now what? I've completely forgotten, put that md5 file into the PDA box in Odin and commence the flashing, however if I wanted could I flash the custom recovery at a later date?
I'm going to sleep now, it's 05:25AM for me, I hope that this help and advice and continue as I really appreciate talking with someone so versed in these matters, my friends and colleagues are all ****ing clueless!
Click to expand...
Click to collapse
Yes that is right here are some instructions ill copy from another post
4.4 Go to DOWNLOAD mode by
4.5 Press the Home, Volume Down and Power buttons together.
4.6 Press Volume Up to continue when prompted.
4.7 Run ODIN on your computer and connect your phone.
4.8 When it recognizes it, check "Auto Reboot" and "F.Reset Time".
4.9 Everything else should be left unchecked.
4.11 Press "PDA" on ODIN and select this file.
4.12 Everything should be as shown here: http://gyazo.com/fea7a1c8b7a7b5bb287fb0a0c70056dc
4.13 Click Start and wait for it to do it's thing. It'll take quite a few minutes.
4.14 When it's finished, you're DONE!!!!
IMPORTANT: If when rebooting, it hangs at the samsung logo for a while then perform STEP 3 (Wipe Device) and then reboot it. Should work. If not then post here and someone may help you OR you can attempt reflashing your stock ROM again.
Yes after all this you can reflash that custom recovery that I posted earlier.
Darke5tShad0w said:
Yes after all this you can reflash that custom recovery that I posted earlier.
Click to expand...
Click to collapse
Thank you for being here for me Darkest, I will try it tomorrow and report back, in the meantime is it possible to flash a custom recovery at any point? I don't want to ever have to go through something this stressful again, and this experience has only made me all the more cautiously confident ie: rom manager/custom roms/rooting etc.
JJKirby said:
Thank you for being here for me Darkest, I will try it tomorrow and report back, in the meantime is it possible to flash a custom recovery at any point? I don't want to ever have to go through something this stressful again, and this experience has only made me all the more cautiously confident ie: rom manager/custom roms/rooting etc.
Click to expand...
Click to collapse
Yes with the i9300 we have the luxury of not having to worry about locked boot loaders etc so it should be able to be flashed with odin when ever you choose.
Darke5tShad0w said:
Yes with the i9300 we have the luxury of not having to worry about locked boot loaders etc so it should be able to be flashed with odin when ever you choose.
Click to expand...
Click to collapse
Thank you for all your help DarkestShadow, it worked like a charm, my S3 is now functioning, basically from the factory condition.
I have since rooted my S3 using CF Auto Root, what would you suggest my course of action to be?
Definitely install a custom recovery and from custom recovery? Can I then install say, a custom ROM but as long as I backup the current state of the phone I could then go back to back; if I wanted to?