I am asking this again here, as my previous thread seemed to be hijacked by someone elses question!
I recently decided to root my inspire as i am no longer using it as a phone, so i thought that it would be interesting to do and fun to play around with all of the options available (i recently did the same thing on my Nook Tablet, and that was the single best decision i have made a while!). I started out researching the manual techniques to do it, but i didn't really like the high risk factor there (i really dont want to brick my phone) so i tried Ace Hack Kit. Of course, it has to download the phone from 2.3.5 to be able to work. During this process, it has me hold volume up and power twice, and every time i do that, it flashes up really quick something about holding volume up and volume down and power, but then it skips past that. Anyway, here is where my problem comes in: It says that it should reboot in to hboot, which it does, but that hboot should run a test, then prompt me to continue by pressing volume up, and then should reboot, flashing twice, and that should be the end of it. THe problem is, it does boot in to hboot, but it is just a standard hboot screen asking to recover, load bootloader, etc. When i reboot from there it just boots in to the phone as normal. I have tried 3 different SD cards, all of which work and are recognized by my PC, my other phone and my Nook tablet. I have also inserted a working sim card, just to be sure that wasnt the issue, and i still cant make it work. Does anyone have any experience with his issue, or any idea what i might be doing wrong?
Opening multiple threads on the same issue is frowned upon. Even if someone supposedly hijacked your thread. I read it and only 7 posts ,I'd call that far from hijacked.
Now at the issue on hand. As mentioned in the other thread. Its the SD card. Also their is a hack kit irc go there. Plus pasting the output would help aswell
marsdta said:
Opening multiple threads on the same issue is frowned upon. Even if someone supposedly hijacked your thread. I read it and only 7 posts ,I'd call that far from hijacked.
Now at the issue on hand. As mentioned in the other thread. Its the SD card. Also their is a hack kit irc go there. Plus pasting the output would help aswell
Click to expand...
Click to collapse
OK, as i have stated, i have tried a new SD card (2, actually, with the same results.) as far as an output screen, there is none. Ace Hack Kit goes through the whole downgrade process, my phone gets in to hboot, but it is just a standard hboot screen, and it doesn't downgrade. When my phone restarts, it restarts like i just did a factory reset.
There is an output,copy what ever it says. There probably is something you missed
As too the SD card ,try adifferent one again. Your SD cards are corrupt and you need to find one that works with the kit
Also since your on a sense 3.0 did you do the changing of the boot img before running the kit?
marsdta said:
There is an output,copy what ever it says. There probably is something you missed
As too the SD card ,try adifferent one again. Your SD cards are corrupt and you need to find one that works with the kit
Also since your on a sense 3.0 did you do the changing of the boot img before running the kit?
Click to expand...
Click to collapse
by changing the of the boot img do you mean downgrading it? That is what i am trying to do. The kit is supposed to do it automatically. If that is not what you mean, please explain!
As to the output, copy thing, no, there is none of that. I have followed the instructions about 20 times. After starting the downgrade process, the phone restarts and comes up with a red triangle. At that point i am supposed to hold volume up and power, and it goes and reboots and i do the same thing again. At this point, i am told that the phone will boot into hboot and check the boot image. When it is done, i am supposed to hit volume up to confirm, and then the phone will reboot, this time in to the down graded image. That is where my problem comes in. Instead of checking the boot image, it just goes to a standard hboot screen. There are no error messages or warnings, and i have followed the instructions to the letter.
As far as the cards are concerned, the maker of the kit suggested a 2 or 4gb Sandisk series 4 or 6 SDHC card, so i bought 2 of the series 6 4gb, along with the 2 others that i already have. I also have 2 series 4 4gb and 2 series 4 2gb Sandisk cards, as well as an 8gb and 2 4gb PNY cards. All of the cards recognize in my phone and PC, and the older cards also recognize in my Nook (and were used to root and load custom roms on several other devices), i have not loaded the new cards in to any other devices besides my laptop and the phone for fear of corrupting it. So i find it difficult to believe that the cards could be the problem.
I know what the kit says. What I'm saying is In the command prompt it spits out a lot of info. For example it will say stuff about zergrush and or taco root. THATS the important stuff, this is what is used to allow the downgrade to be possible. If their a failure in the process it would state it there. That's why I keep asking for it. Don't understand your reluctance to do a simple copy and paste
The changing of the boot img is something that is different and you should read about it on attn1 site. Version 3.20 has a slightly different method
marsdta said:
I know what the kit says. What I'm saying is In the command prompt it spits out a lot of info. For example it will say stuff about zergrush and or taco root. THATS the important stuff, this is what is used to allow the downgrade to be possible. If their a failure in the process it would state it there. That's why I keep asking for it. Don't understand your reluctance to do a simple copy and paste
The changing of the boot img is something that is different and you should read about it on attn1 site. Version 3.20 has a slightly different method
Click to expand...
Click to collapse
I appreciate the attempt to help (the reason why i didn't post a direct copy paste was simply as i was in no position at the time to take one, not any reluctance to ultimately do so...) In my recent attempt to provide you with a full copy paste of the process, i was able to figure out what i was doing wrong. For anyone who may have the same or similar issue: format the SD card while it is in the phone from your PC right before starting the process. Thats all it took. Even for a card that was brand new and untouched, or formatted before putting it in the phone, i couldn't get it to work, but it worked doing it that way, and i am now happily rooted and ready to install CM9!
Glad you got it figured out. Formatting the SD card in the phone is a must, since the phone puts important files on the card after formatting.
pazzo02 said:
Glad you got it figured out. Formatting the SD card in the phone is a must, since the phone puts important files on the card after formatting.
Click to expand...
Click to collapse
Wrong. There's no need to format the sdcard to run the Hack Kit, unless your sdcard is not in fat32 system file format. The only requirement is that your sdcard must not be corrupted to work as a goldcard. Corruption of the boot partition of the sdcard can not be solved by formatting and is produced by improper dismount of it.
glevitan said:
Wrong. There's no need to format the sdcard to run the Hack Kit, unless your sdcard is not in fat32 system file format. The only requirement is that your sdcard must not be corrupted to work as a goldcard. Corruption of the boot partition of the sdcard can not be solved by formatting and is produced by improper dismount of it.
Click to expand...
Click to collapse
I'm just speaking from experience. Every SD card I've put in my phone I had to format in the phone because it was giving me problems. After, no problems. Maybe it's just my phone. or the cards weren't FAT32.
You're last sentence is probably where most people screw it up. You can't just yank an SD card out of whatever device it's in, which I think a lot of people do. But I have fixed cards that were removed without unmounting by formatting. Maybe other parts were corrupt but not the boot partition?
pazzo02 said:
I'm just speaking from experience. Every SD card I've put in my phone I had to format in the phone because it was giving me problems. After, no problems. Maybe it's just my phone. or the cards weren't FAT32.
You're last sentence is probably where most people screw it up. You can't just yank an SD card out of whatever device it's in, which I think a lot of people do. But I have fixed cards that were removed without unmounting by formatting. Maybe other parts were corrupt but not the boot partition?
Click to expand...
Click to collapse
As far as I am concerned the boot partition can not be restored by formatting. SDCARD should always be dismounted properly.
Related
Ok Guys.
I created this thread cause in the JACHero thread on at least every page everyone asks how to install it, what am I doing wrong, and why is it broken.
So let me give you step by steps of what exactly I have done for me and others to run Hero with out a problem. I will also create a thread with step by step on how to use Ubuntu Linux Live distro to partition your card.
Things you will need to make this work.
Your Brain
G1 Phone
SD Card reader
And the files I included in this thread.
My phone right now is running.
JACHero 2.3
NEW SPL
cyanogens recovery 1.2
8gb class 6sd with Swapper(Swap file on ext2 sd)
setCPU slightly overclock.
Results.
Ever since I did my new Buttons, and the SPL I included in this write up, I have not had one problem flashing any hero rom at all on my phone, nor did I ever have problem actually running hero roms.
So here goes.
First before you partition your card or do anything make sure your card is at least portioned to fat32, don't worry about any other partitions yet.
OK once you do that go ahead and take the radio zip file I am including in this thread and flash it on your phone.
But first make sure you don't already have new radio installed which is 2.22.19.26I THIS IS VERY IMPORTANT. To check what radio you have, power off your phone, and power it on while holding the camera button.
If you do have new radio you can continue on to flashing the new SPL.
Flashing your SPL. (PLEASE MAKE SURE YOU HAVE THE NEW BUTTONS INSTALLED)
Ok this is where it might get a little tricky, and you might require a SD card reader I know I did and frankly I think this is the best way to do it and I recommend every time you do put a new update on your sd card to update your phone do it through a card reader.
Now after you flash your SPL you might or I should say more then likely will get stuck at the T-Mobile G1 screen, this also might happen after new radio flash in the previous step. If this is the case do not freak out it's normal and your phone is not bricked, but this is why having a sd card reader is important.
Ok so Here is what you do after you have flashed new Radio and SPL(Note:The steps on running Linux live distro and using it to partition your card is coming up). Boot up Live distro of Ubuntu, when its done booting, go ahead and go into the partitioning program while your sd card is hooked up in the computer.
Go ahead and set up two partitions at this time. One EXT3, and of course the other one Fat32. Your ext3 partition doesn't have to be all that big. I actually have mine set up to 512.
Once you are done creating partitions, go ahead and put the latest JACHero on the FAT32 portion and flash away (don't forget to rename to update.zip).
At this point if you follow all of these steps there is no way possible that your phone should not boot right into the system to run the initial setup.
These steps pretty much walk you through steps as if you were starting with a phone that has completly nothing on it.
Also the first boot up after flashing the new ROM, might take a few mins at the HTC screen.
Once your phone loads up and you go through the setup process go ahead and run swapper, it should be an APP that's already pre-installed.
Once you run swapper go into the setting and change the location of your swap file from /sdcard/swapfile.swp to /system/sd/swap.swp
Here is the reason why. The default location is your FAT32 partition. If you all of a sudden mount your phone to the computer with the swap file running on FAT32 you will corrupt your sd card, and then you will have to wipe and reinstall everything.
If you set the location of your swap file on /system/sd/ that's actually your ext2/3 partition and never gets mounted and you never have to turn swapper off.
Well I hope this helps some of you out. I will be writing the walk through on loading up live distro of Linux and partitioning your card sometime today.
I have used this method on a couple different phones and it has worked each time. Also I really recommend installing cyanogens recovery 1.2, as its an excellent way of making a back up of your phone and doing future flashing.
If there is anything anyone thinks that could be done better feel free to post in here.
Remember different people have different ways. I have posted this way cause it has worked for me on my phone and two other phones I setup, and each time there was no hicups.
FILES:
Radio 2_22_19_26I
NEW SPL
CM-Recovery-1.2
Ubuntu Linux Download
DISCLAIMER:
I am not responsible for anything that you might have done to your phone by following these directions. Like I mentioned before so far every time I have used this method, I have had nothing but success.
While I can appreciate this topic, I think you need to speak with less certainty that this will always work properly the first time.
For example - I'm coming from the Ramjet ROM, and the process that I have taken.
Freshly formatted 4gb sd card with a 700mb EXT3 partition, the rest is fat32.
Loaded JACHero 2.3 and renamed update.zip
Wiped twice
Installed ROM
Phone went into boot loop - allowed to run for 10 minutes
Removed battery
Attempted to install ROM a second time
Boot loop again - allowed to run 10 minutes
Wiped again
Installed ROM
Boot loop again - allowed to run 10 minutes
It seems strange, as going from a standard JAC build previously I was able to just wipe, wipe, install and had JACHero 2.1 working without a hitch. I found this strange, as people were complaining about that build, but it seems 2.3 is what's giving me the most headache.
/shrug. Guess I'll go back to Ramjet.
Great post, dude. I've rooted my phone, flashed a few ROMs, including Haykuro's Hero, moved Rosie back to run on the phone instead of the SD card, overclocked and run Swapper. I was still a bit confused and hesitant to flash the JAChero ROM. I'm feeling better about it now. Gonna flash when I get home from work today.
TooSlo said:
While I can appreciate this topic, I think you need to speak with less certainty that this will always work properly the first time.
For example - I'm coming from the Ramjet ROM, and the process that I have taken.
Freshly formatted 4gb sd card with a 700mb EXT3 partition, the rest is fat32.
Loaded JACHero 2.3 and renamed update.zip
Wiped twice
Installed ROM
Phone went into boot loop - allowed to run for 10 minutes
Removed battery
Attempted to install ROM a second time
Boot loop again - allowed to run 10 minutes
Wiped again
Installed ROM
Boot loop again - allowed to run 10 minutes
It seems strange, as going from a standard JAC build previously I was able to just wipe, wipe, install and had JACHero 2.1 working without a hitch. I found this strange, as people were complaining about that build, but it seems 2.3 is what's giving me the most headache.
/shrug. Guess I'll go back to Ramjet.
Click to expand...
Click to collapse
I can completely see what you mean by that. But only reason I decided to make this, because two other phones that were having the exact same problems, started working after I did this.
They both had the same symptoms everyone else, and no one really knows where it came from.
So I made sure they had the right radio, then the right SPL, and every time I did something to the SD Card I killed the partitions completely not just format them.
But I destroyed the partition, recreated it and then formatted it to a file system of my choosing.
my g1 is fine ive flashed every rom here and never gotten stuck on boot loop, if anything the files youre downloading for recovery and spl must be corrupted try re downloading your radio file and spl's again.
Include Disclaimer
I like your post but here is something that I would add to your post.
Even though this has worked every time for you do not assume that it will work for every one, therefore make sure you put a disclaimer out there. As you may have seen before, there have been a lot of posters that have blamed others when their phones were either bricked or stuck in boot loops.
Remember....some people may do something wrong during a step and swear that they followed it perfectly and then blame you.
A detailed disclaimer could be of some help since a lot of people will be taking your post as LAW......
for somereason im not able to update my spl is it something u must do i keep gettin a veification faild message when im tryin to flash it wiht alt + s and i cant seem to update to jachero 2.3 im using a 1 g micro sd im really not sure whats going on i have the proper raido settings and everything. also im not really sure how to create 2 partitions on my memory card im running good ol windows vista
how fast is this running.
i tried it once without swapper and it was way to slow in my eyes in order to use at as an everyday phone.
hope you have something for me (is swapper this perfect solution?)
In my opinion the perfect solution is making a a linux swap partition on your sd card.
However last time I created a linux swap partition and created my swap file there after I rebooted my phone I got stuck at the G1 screen.
I think this might have been cause because of having three partitions on the card but I am not 100% sure.
So instead I just use swapper and make it mount the swap file on my ext3 partition which seems to make this rom run really freaking smooth.
Also I have noticed significant improvements of using ext3 vs ext2, but when research how the two different file systems work it makes sense why it would make a difference.
So to answer your question, is swapper the perfect solution? Im not sure if there is anyone perfect solution but I do know that this sure ass hell makes a huge difference in how your Hero rom runs.
for those having boot loops, how about help us help you, run ddms from sdktools and grab a log of whats going on, this way we can determine an issue, because those asking for help with bootloops and asking for help is like asking me to tell you whats wrong with your car over the phone. we cant tell if we cant see whats going on. so helps us, if you have adb and not the sdktools just type
Code:
adb logcat
this way we can see what your phones trying to do.
Excellent post! I wish I this was available yesterday when I did my first Hero ROM ever. The JAC thread is huugggeeee.
Not to hijack your post, but I'll add my two cents and experiences from yesterday if you do not mind.
-------------
Ok first time on Hero. Coming from DudesCupcake.
Pre
Formatted 1gb SD card 500mb Fat32, and the rest Ext3
hxxp://allshadow.com/forum/viewtopic.php?f=9&t=5870
1. Flashed Radio 2.22.19.26I from (update.zip) successful (camera+power to check)
hxxp://code.google.com/p/sapphire-port-dream/
2. Flashed SPL 1.33.2005 from (renamed update.zip) successful (new three android skateboard logo on bottom)
hxxp://code.google.com/p/sapphire-port-dream/
3. Updated to JACHero r2.2.1 from Page 1
Now I have a boot loop, Hero -> HTC...
After installed 2.2.1 should I pop my SD card out and format it again on my computer?
Trying to do the 2.2.1 again.... Wish me luck!
**Update**
Updating to the 2.2.1 again worked.
Ok, everything works!! Much thanks to Luckenbach for the moral support, and thanks to JAC and all the other guides that I linked in my process. So if anyone else is a noob like me you can do exactly what I did (I provided links for each step where I got it from) you should be ok.
XDA rules!
------
Quick questions for people with loop problems.
is your linux partition ext2 or ext3?
southeastbeast said:
Excellent post! I wish I this was available yesterday when I did my first Hero ROM ever. The JAC thread is huugggeeee.
Not to hijack your post, but I'll add my two cents and experiences from yesterday if you do not mind.
-------------
Ok first time on Hero. Coming from DudesCupcake.
Pre
Formatted 1gb SD card 500mb Fat32, and the rest Ext3
hxxp://allshadow.com/forum/viewtopic.php?f=9&t=5870
1. Flashed Radio 2.22.19.26I from (update.zip) successful (camera+power to check)
hxxp://code.google.com/p/sapphire-port-dream/
2. Flashed SPL 1.33.2005 from (renamed update.zip) successful (new three android skateboard logo on bottom)
hxxp://code.google.com/p/sapphire-port-dream/
3. Updated to JACHero r2.2.1 from Page 1
Now I have a boot loop, Hero -> HTC...
After installed 2.2.1 should I pop my SD card out and format it again on my computer?
Trying to do the 2.2.1 again.... Wish me luck!
**Update**
Updating to the 2.2.1 again worked.
Ok, everything works!! Much thanks to Luckenbach for the moral support, and thanks to JAC and all the other guides that I linked in my process. So if anyone else is a noob like me you can do exactly what I did (I provided links for each step where I got it from) you should be ok.
XDA rules!
------
Click to expand...
Click to collapse
When you do the CAMERA+POWER boot, what exactly does the second line from the top say?
lol I wasn't requesting help, I was adding to your post! To hopefully help other people =)
Oh I know I'm just collecting data right now that's it.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CLPD-4
RADIO-2.22.19.26I
Apr 20 2009,15:30:43
--
Edit: Also changing location of swapper from your info helped a lot! Thanks, I had the SD problem when I pulled out my SD card to put photos back on (instead of using adb) and I got stuck in a boot loop, I thought I was done for. Just rebooted it a few times and it was back up and running. Good tips =D
what do you mean by "new buttons"?
A quick question that ill ask here as to not clutter up JADs thread any more than it alreadsy is.
I have put on 3 of his roms in the last few days and where as they are stable they are dead slow at times for me. I am using a 2g class 2 sd card with an ext3 partition. How much more would a class 6 card speed swapper up? Is one worth getting?
Sorry to post up in this thread again, but I just wanted to provide some more of my experiences here.
I'd picked up Paragon Partition Manager and used that to format my SD card and create the ext3 partition on it as well. It seems something is wonky with how it created it, as every time I've created the partition, even with different sizes, I always get stuck in a boot loop when trying to install JACHero even though any other ROMs will install just fine.
I've put the update.zip onto my older 1gb card that came with my phone just to see if it would install, and though it took a while, it installed without any issues.
After going through the setup process, I attempted to put in my 4gb card with ext3 on it. Lo and behold, boot loop.
Seems something is funky with the way that Paragon Partition Manager creates an ext3 partition.
I'm now going to install an older ROM and go through the "creating an ext2 partition through the G1" method and then attempt to convert it to an ext3 through Cyan's instructions.
I'll try to keep up to date what's going on. I know this place isn't a blog, I'm just hoping someone will point out my idiocy if I'm making any huge mistakes somewhere.
TooSlo said:
While I can appreciate this topic, I think you need to speak with less certainty that this will always work properly the first time.
For example - I'm coming from the Ramjet ROM, and the process that I have taken.
Freshly formatted 4gb sd card with a 700mb EXT3 partition, the rest is fat32.
Loaded JACHero 2.3 and renamed update.zip
Wiped twice
Installed ROM
Phone went into boot loop - allowed to run for 10 minutes
Removed battery
Attempted to install ROM a second time
Boot loop again - allowed to run 10 minutes
Wiped again
Installed ROM
Boot loop again - allowed to run 10 minutes
It seems strange, as going from a standard JAC build previously I was able to just wipe, wipe, install and had JACHero 2.1 working without a hitch. I found this strange, as people were complaining about that build, but it seems 2.3 is what's giving me the most headache.
/shrug. Guess I'll go back to Ramjet.
Click to expand...
Click to collapse
did you try going into recovery and then choosing fix file extensions... that happend to me, it might be because you have no ext 2
... I'm trying to flash a HardSPL onto my possibly-dead Kasier, and I'm currently trying to do it via SD (because the USB isn't reliable for some reason).
I've got the KAISDIAG.nbh and the KAISIMG.nbh (I've tried several different HardSPL versions) on the SD, and when the phone boots I get the gray "Loading..." screen, but that's as far as it ever gets.
How long is it supposed to take, and are there any suggestions on where I might go next?
Have you tried doing it via USB?
USB doesn't work consistently. I can't get the phone to boot into Windows, so no JumpSPL, and when I plug in the USB at the bootloader screen I get "Unrecognized Device".
godefroi said:
... I'm trying to flash a HardSPL onto my possibly-dead Kasier, and I'm currently trying to do it via SD (because the USB isn't reliable for some reason).
I've got the KAISDIAG.nbh and the KAISIMG.nbh (I've tried several different HardSPL versions) on the SD, and when the phone boots I get the gray "Loading..." screen, but that's as far as it ever gets.
How long is it supposed to take, and are there any suggestions on where I might go next?
Click to expand...
Click to collapse
- Did you format the SD card with FAT32? It should be FAT32.
- I always use the name KAISIMG.nbh
- It just loads within less than 5 seconds for me, rather quickly before it asks me to press Power button for upgrading.
So, check if SD card is with FAT32 and check the name of the nbh file first.
Iced Coffee said:
- Did you format the SD card with FAT32? It should be FAT32.
- I always use the name KAISIMG.nbh
- It just loads within less than 5 seconds for me, rather quickly before it asks me to press Power button for upgrading.
So, check if SD card is with FAT32 and check the name of the nbh file first.
Click to expand...
Click to collapse
Yeah, it's FAT32, and I've definitely got the right filename. Bummer. I'll let it "rest" here for a day or two and try again.
godefroi said:
Yeah, it's FAT32, and I've definitely got the right filename. Bummer. I'll let it "rest" here for a day or two and try again.
Click to expand...
Click to collapse
Did you have another HSpl before or this is the 1st time you try to do it ?
Flash HSpl thru SD card is only possible to change from one 3.xx to another 3.zz
Pisca said:
Did you have another HSpl before or this is the 1st time you try to do it ?
Click to expand...
Click to collapse
Ah, no, it's a completely stock Tilt. It's quite possibly dead, but because it's now mine and can't get any -worse-, I'm just playing around with it. Do you have any other suggestions? If I can't get it to boot into WM, how might I be able to get a HSPL on it?
I'm thinking of just task 2a'ing it and seeing if frankenkaiser might be able to resurrect it...
Look at the sticky posts and try to get information from there, before use Task2 or other hard method
Yeah I've gone through lots of stuff, but everything seems to either require booting into WM, or just doesn't work for me. On the last occasion that USB was working, for example, I got into MTTY, but "info 2" and "info 8" just showed nothing, which I understand isn't how it's supposed to be...?
"boot" and "task 0" give "Command Error!!!", which I also gather is not how it's supposed to work.
I must confess never used MTTY
In the same situation but can boot to Windows.
I sympathize with your frustration.
I wound up in a similar situation after trying to flash a stock ROM back to my device (via SD) from a previous 6.5 ROM.
End result after my attempt to flash a stock ROM:
-Device flashed, but only the 6.1 RADIO was successful
-Still have the 6.5 ROM (and no audio and other issues due to the old Radio)
-Can boot to windows
-NO USB sync (via JumpSPL or any other method)
-KAISIMG.nbh SD flash is stuck at the white screen and shows (Loading...)
Still haven't found a solution to this, after reformatting the SD, and multiple attempts at a PC sync/flash. Thinking it might be related to a corrupted SD Card. Ordered a new one and it should arrive any minute.
I'll post my result once it arrives.
Try with a different USB cable, sometimes they tend to go corrupt.
this has happened to me in the past too, try formatting your sd card again. if that doesn't work, try a different sd card. i've got a 4gb that just won't work for sd flashing, and a 1gb that works perfect every time.
godefroi said:
... I'm trying to flash a HardSPL onto my possibly-dead Kasier, and I'm currently trying to do it via SD (because the USB isn't reliable for some reason).
I've got the KAISDIAG.nbh and the KAISIMG.nbh (I've tried several different HardSPL versions) on the SD, and when the phone boots I get the gray "Loading..." screen, but that's as far as it ever gets.
How long is it supposed to take, and are there any suggestions on where I might go next?
Click to expand...
Click to collapse
We have all the same problem. NO SOLUTION at the moment.
Here some link were people talks about this problem and no one give a valid solution:
- LINK: http://forum.xda-developers.com/showthread.php?t=423486&page=55
- LINK: http://forum.xda-developers.com/showthread.php?t=371154&page=15
- LINK: http://forum.xda-developers.com/showthread.php?t=553790
Update: Did try 3 separate SD Cards (1GB AData, 4GB Kingston, and an 8GB AData). All had the same results, with a fresh FAT 32 format (default allocation).
8GB was a brand new card, with no luck.
For the record. I have been able to flash in the past with my 1GB and 4GB cards, with no issue. Multiple cables and PC's have been used with no change to the outcome.
joerao said:
Update: Did try 3 separate SD Cards (1GB AData, 4GB Kingston, and an 8GB AData). All had the same results, with a fresh FAT 32 format (default allocation).
8GB was a brand new card, with no luck.
For the record. I have been able to flash in the past with my 1GB and 4GB cards, with no issue. Multiple cables and PC's have been used with no change to the outcome.
Click to expand...
Click to collapse
You should probably buy a new phone...
ai6908 said:
You should probably buy a new phone...
Click to expand...
Click to collapse
Funny thing is that the phone still works (at least as a phone
No sound, no camera... and the 6.5 ROM that's on there is a bit flaky. I haven't lost hope yet... may try to solder a new USB connector before I put this one to bed.
...or just by a Zune HD, and wait until the new Tegra based phones to ship.
Any better ideas out there?
Load only KAISIMG.nbh and remove other I had the same issue and did this then it worked
Flash with just KAISIMG.nbh
alphonsecorbett said:
Load only KAISIMG.nbh and remove other I had the same issue and did this then it worked
Click to expand...
Click to collapse
If you are referring to removing the KAISDIAG.nbh file from the SD card, and just booting with the KAISIMG.nbh. I tried this just now, with the exact same results. Stuck at "Loading..." at the white screen.
The KAISIMG.nbh I was loading was a newer 6.5 radio. What image were you able to get to work?
Hi!
Some time lurker but it's my first post.
I just created this post because of the 10 posts rule on dev section.
Following this thread:
http://forum.xda-developers.com/showthread.php?t=947950
My problem is:
Phone boots right, after unlocking the screen the error messages start.
Any settings changed get lost after reboot.
Can't change anything, even SD card contents
What I tried:
I can install clockwork (it's the only partition I can change)
But nothing more. Because what ever I copy from pc to SD card get lost when unmounting from pc. Not even NAndroid
With fastboot only flashing recovery works.
With others I get errors, I guess because it can't write to memory.
So I tried ODIN even with 512 .pit. Got firmware from samfirmware.com and other places
(I tried many times with different sources).
All procedure with Odin says sucessfull but when rebooting I got the previous installation unchanged.
It looks like I have a real ROM memory (in the real definition of the word) and nothing can change it. (A real unbrickable phone for ever )
I suspected first from hardware problem but if the problem was that I couldn't write to any partition, not even recovery (it's a single chip on motherboard). And if I mess up with pit and only repartitionate, the phone restarts over and over to bootloader.
If I repeat the steps again with correct files in Odin, it sucessfully reboots to the unchanged installation again. Like it never writed anything. Even the sdcard is unchanged with lot of musics ans photos.
Any ideas?
Thanks in advance
Anyone?
Anyone?
Are there any tool to format / resize change flash memory on Nexus S?
Like there are tools for HDD.
Or go to specific hardware and JTAG?
If you point me any direction it could help a lot.
Its not a single chip from my understanding. The sdcard partition is a seperare chip from the bootloader/recovery. Sounds like it could be a hardware issue. I have never heard of this exact problem though, most commonly the sdcard partition becomes unmountable
Sent from my Nexus S 4G using xda premium
Chip
I believe it's only one chip.
check step 10 on here
w_w_w.ifixit.com/Teardown/Nexus-S-Teardown/4365/2
and it's equal to my own motherboard,
Besides, the SDcard mounted on Nexus S is only ~13G , the rest is partitioned to system, boot, ...
yeah, I'm screwed
Anyone?
I'm screwed.
Anyone know where can I find motherboard to replace it?
(ebay has a lot of digitizers, flexs, etc but not motherboards)
Or maybe one to sell.
Or maybe figured out how to change NAND chip
Contact Samsung. They should repair it. Just sucks because you will be without your phone for two to three weeks.
Sent from my Nexus S 4G using xda premium
Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.
gsmyth said:
Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.
Click to expand...
Click to collapse
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
jujuburi said:
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
This is the first problem I've had with it to be honest, had it or over a year and was using it in my HTC Sensation previously. I'm trying to remember if it was exFAT or FAT32, I remember a ROM (Google Edition S4 ROM) not being compatible with exFAT and checking mine out of curiosity, but just can't recall what it was and never flashed the ROM. I didn't reformat it coming from my Sensation so it hadn't changed in anyway.
Luckily all my photos were backed up to dropbox so nothing lost of too much importance. Need to get a microSD card reader to see if its completely borked or if files can be retrieved.
Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.
Theoriginalgiga said:
Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.
Click to expand...
Click to collapse
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.
gsmyth said:
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.
Click to expand...
Click to collapse
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.
Theoriginalgiga said:
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.
Click to expand...
Click to collapse
Cheers, I had re-downloaded the previous version of the ROM which I was on before hand and made sure to check the md5s but it still wouldn't boot which was annoying, but a full install from scratch may be the way to go. Never had bootloops before and was just worried after I had wiped and started a fresh and it still happened. I think the real lesson is to make sure to backup ANYTHING that is of value to you!
Luckily I had just happened to use the auto backup for photos to dropbox so got off lightly this time!
I have had the EXACT same issue 2 weeks ago.
I bought 2 x 32gig microSD cards (Sandisk)
1 for my phone and 1 for my digital camera.
Recently the 32gig one in my phone just DIED for no reason at all. Lost all my files, music, everything.
I contacted Sandisk, had it repalced. In the meanwhile i purchased a 64gig Samsung one.
I am yet to have an issue with the Samsung 64gig, but only time will tell.
On a plus note, Sandisk sent me a replacement 32gig card very quickly (infact too quick, i purchased the 64gig Samsung one on the idea that the Sandisk replacement was going to take months... in fact it only took 6 days...)
Cheers
How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app
jujuburi said:
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
I always use Fat32 on SD-cards. Why? It works on every Rom, with every kernel, every recovery, on every device, every camera, every computer, all the time.
When not in need of files greater than 4GB Fat32 simply is the way to go, compatibilty-wise.
gsmyth said:
How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Tried the card in a reader connected to my laptop but nothing. I've emailed Sandisk support so will see what they say.
Sent from my GT-I9505 using xda app-developers app
I just wanted to post this here in case it might help someone.
If you have ever had the SD card corrupted issue after installing a ROM or an update the first thing you should check is the kernel. I have found that every time I've had this issue I could still see the SD card in TWRP you couldn't figure out what was going on. I have since learned that the issue usually stems from the kernel. So take and reflash your current kernel or try a new kernel. Hope this helps someone good day
I reformatted my card to FAT32 which solved those issues for me. Be sure to backup anything before doing that as it reformatting will erase the card obviously.
AngryManMLS said:
I reformatted my card to FAT32 which solved those issues for me. Be sure to backup anything before doing that as it reformatting will erase the card obviously.
Click to expand...
Click to collapse
Why format the SD card if just flashing another kernel will fix the issue lol
shadavis08 said:
Why format the SD card if just flashing another kernel will fix the issue lol
Click to expand...
Click to collapse
I could think of a reason, that being (and this is an Android-wide rule) the kernel dictates support for file formats.
If you're using a kernel that has better features than a stock one on a ROM (let's say Gamma vs the stock LineageOS kernel in this case) the better kernel might not support the file-system format the stock one does. It comes down to support for what file-systems a kernel dev chooses to implement.
At least personally, I'd rather move 64GB off my microSD card, format it and move it all back on if it means I get to keep using a better kernel.
Your thought process is flawed. Since the source of the issue is the stock kernel. Geesh
Thinking that it's easier to remove everything and then put it back rather than, simply flashing a different kernel than the stock kernel, first to see if that is the issue, by the way is flawed.
shadavis08 said:
Your thought process is flawed. Since the source of the issue is the stock kernel. Geesh
Click to expand...
Click to collapse
shadavis08 said:
Thinking that it's easier to remove everything and then put it back rather than, simply flashing a different kernel than the stock kernel, first to see if that is the issue, by the way is flawed.
Click to expand...
Click to collapse
I'm not entirely sure what makes my thought process flawed. If the issue is the stock kernel, then the stock kernel likely doesn't support the format the SD card is using, in which case, like you said, swapping kernels would fix that.
I don't disagree with you there.
I also wouldn't call moving everything off, formatting and moving everything back on is a flawed process either.
If I have to choose between massive screen retention using a stock kernel on the V20, or little to no screen retention and better performance by using a custom kernel like Gamma, Gamma is going to win every-time. Even if I have to spend 20 minutes moving stuff off, formatting my SD card and moving it all back on.
It might not be a process that's worth it for some people, but it's by no means flawed.
Your "flash a different kernel to see if that's the issue first" is like me saying I'll plug my desktops Windows 10-formatted SSD into my Windows 7-formatted laptop and see if it'll work.
It could, but I run the risk of it not working properly, which is something you want to avoid in most cases.
And I did say
At least personally
Click to expand...
Click to collapse
which, again, doesn't make my process flawed.
Redline said:
I'm not entirely sure what makes my thought process flawed. If the issue is the stock kernel, then the stock kernel likely doesn't support the format the SD card is using, in which case, like you said, swapping kernels would fix that.
I don't disagree with you there.
I also wouldn't call moving everything off, formatting and moving everything back on is a flawed process either.
If I have to choose between massive screen retention using a stock kernel on the V20, or little to no screen retention and better performance by using a custom kernel like Gamma, Gamma is going to win every-time. Even if I have to spend 20 minutes moving stuff off, formatting my SD card and moving it all back on.
It might not be a process that's worth it for some people, but it's by no means flawed.
Your "flash a different kernel to see if that's the issue first" is like me saying I'll plug my desktops Windows-formatted SSD into my Linux-formatted laptop and see if it'll work.
It could, but I run the risk of it not working properly, which is something you want to avoid in most cases.
And I did say
which, again, doesn't make my process flawed.
Click to expand...
Click to collapse
Wow really dude? I was giving some advice for people that could potentially keep them from losing all their data on the SD card. By simply flashing a different kernel before just wiping a card when the android system throws up an error saying sd card corrupted. You are only here to argue and I would like you to stop. Thank you for over thinking the situation and good day.
shadavis08 said:
You are only here to argue and I would like you to stop. Thank you for over thinking the situation and good day.
Click to expand...
Click to collapse
That's precisely the opposite of the reason why I'm here.
I was here to point out the benefits and potential downsides to doing it either way, but okay.
I don't get t flash kernels on my variant but if ever i saw a corrupt sd card message i'm wondering whether just deleting the android folder (on the card say on a PC) and then re-inserting the card would be enough.
You could simulate this just by pulling the card without un-mounting it and then reinserting and android thinks the card is corrupt
I don't know. I don't have a computer to test with lol
One Twelve said:
I don't get t flash kernels on my variant but if ever i saw a corrupt sd card message i'm wondering whether just deleting the android folder (on the card say on a PC) and then re-inserting the card would be enough.
Click to expand...
Click to collapse
This shouldn't be the case. I say shouldn't because I'm not sure how Android does it exactly, but telling you the SD card is corrupt either means it is, or it can't read the file system itself, not the files.
Deleting the Android folder probably won't do anything, that folder just has data for apps and such that want to store things on the SD card.
I'd imagine you could achieve the same thing with internal storage if you formatted it weirdly from TWRP or something.
Redline said:
This shouldn't be the case. I say shouldn't because I'm not sure how Android does it exactly, but telling you the SD card is corrupt either means it is, or it can't read the file system itself, not the files.
Deleting the Android folder probably won't do anything, that folder just has data for apps and such that want to store things on the SD card.
I'd imagine you could achieve the same thing with internal storage if you formatted it weirdly from TWRP or something.
Click to expand...
Click to collapse
My mistake not Android folder but lost.dir folder needs to be deleted
Back on nougat this happened to me twice on the same card. Formatted once and it happened again and this was back before I tried any custom ROMs or Kernels. Was purely stock rooted with SuperSU so it was definitely something screwy with LGs kernels
Kinda fuzzy but I think it happened first on 10J for TMobile and then again on 10K for my H918
I've not had any problems with my sandisk extreme 128GB for over a year now. On N.
I don't take the card out and swap it about, its been in all this time.