Ok, So I dusted off the old G1 for the first time since I got my Nexus in and I wanted to flash a new ROM. I booted into recovery and proceeded to wipe everything and I get Data Wipe Aborted, This message happens for everything I do i.e. Installation aborted, Partitioning aborted, Fixing aborted. The only thing I can do is go into console and mount USB. in console I get this when I try to mount -a [mount: mounting /dev/block/mmcblk0p2 on system/sd failed:No such file or directory. I have a 4g sd card in that has been fully formatted with the laest radio and SPL on it. but thats it.
Can anyone help me? I'll give ya a buck.
Can you get in fastboot or h-boot? if so- then just go back to RC29 or RC7 and go from there... something obviously got borked.... sh!t happens... at least you have your N1
try using the DREAMING.NBH file for your region i..e usa or europe
they can be fouond on cyanogens wiki page easily and re-root your device.
would fix the problem. i had a similar problem and it solved it
I remember running into the same exact messages!
I was low on battery power at the time (~20%), so I left it charging, attempted to wipe/partition/flash after that, and it worked. I'm sure your battery drained a bit and ended up pretty low since the arrival of your N1 lol.
Enjoy
Thanks Fellas
Haha Thanks fellas, I got it workin' I guess it just had to be on for a little bit. Since it hasnt been on since I got my n1. Works fine now. The in-call volume is very low now... Is there a new Kernel I can flash to increase it to at least back to stock or louder? The Louder Volume Hack does not fix it
Related
Im getting the above error in my tittle. I have used the search tool. I have found a lot of solutions but none have worked for me. I'm running Hero-V1.5.5. This problem happened after I flashed or maybe in my attempt to install Debian. Also, my audio is very low on my phone even with audio hack. I had to reroot my phone the other day. Lots of problems since.
Update: I tried to reformat my ext 3 and repair. Now Im stuck in hero boot loop. Man this sucks. I know I can fix this by using dreaimg.nbh. If I did that I would have to reroot. Which would take 5 minutes to do but I would like to avoid this. Any help will be much appreciated!
thanks
bob50963 said:
Im getting the above error in my tittle. I have used the search tool. I have found a lot of solutions but none have worked for me. I'm running Hero-V1.5.5. This problem happened after I flashed or maybe in my attempt to install Debian. Also, my audio is very low on my phone even with audio hack. I had to reroot my phone the other day. Lots of problems since.
Update: I tried to reformat my ext 3 and repair. Now Im stuck in hero boot loop. Man this sucks. I know I can fix this by using dreaimg.nbh. If I did that I would have to reroot. Which would take 5 minutes to do but I would like to avoid this. Any help will be much appreciated!
thanks
Click to expand...
Click to collapse
did you wipe.......?
For some odd reason everytime I try to install the cyanogen rom v4.0.4 I believe its one of the stable ones, I do everything to root my fone and install the rom and my fone says its done w the updates and to reboot it and when I do it stays @ the g1 screen. Now I take the battery out and press the cam and end buttons to reinstall the dreaimg to take it back to rc29 state. When I power it up it works just fine the lil android dude pops up and i put in my info and then just redo the steps to the cyanogen rom and for some reason my fone will install everything I will assume properly and i go to reboot it and it stays on the tmobile g1 screen.
I need help! I have tried and tried and Idk what to do now.
This all started bc I deleted something from the cm updater and my fone hasnt worked since...if ne one can help me plz email me @ [email protected]....
Thanx!
SekSayLiLRaver said:
For some odd reason everytime I try to install the cyanogen rom v4.0.4 I believe its one of the stable ones, I do everything to root my fone and install the rom and my fone says its done w the updates and to reboot it and when I do it stays @ the g1 screen. Now I take the battery out and press the cam and end buttons to reinstall the dreaimg to take it back to rc29 state. When I power it up it works just fine the lil android dude pops up and i put in my info and then just redo the steps to the cyanogen rom and for some reason my fone will install everything I will assume properly and i go to reboot it and it stays on the tmobile g1 screen.
I need help! I have tried and tried and Idk what to do now.
This all started bc I deleted something from the cm updater and my fone hasnt worked since...if ne one can help me plz email me @ [email protected]....
Thanx!
Click to expand...
Click to collapse
try flashing another build. or wait about 15 maybe 20mins and see if goes away. or just do wipe... or i bet its your sd card try getting to the point where it hangs take out the sd card and then turn it on again.
The first boot after each flash or dalvik-cache dump will take a long time. Just be patient.
Fingerlickin said:
The first boot after each flash or dalvik-cache dump will take a long time. Just be patient.
Click to expand...
Click to collapse
Yes a real long time, right fingerlickin. lol
But if you loaded RC29 back then your gonna have to reroot.
I would suggest wiping if you issue isn't fixed by waiting. I've had to wipe a few times jumping between Experimental and Stable builds mainly because of big Donut differences in the build's.
Fixed???
I think it may have fixed it self, I had my friend look @ it and I had taken the sd card out of it and showed him what happened and he left it alone and it came up w/ an update now he did and its working now like normal...SOoO im scared to try again jus bc i dont wanna f*** it up again but Im stubbern and w/ the info ive learned so far on all these sites I just may do it all over again.
Use THIS guide next time.
Fingerlickin said:
Use THIS guide next time.
Click to expand...
Click to collapse
Show off.
And then use this to partition your card.
http://forum.xda-developers.com/showthread.php?t=535914
I quess I'm a show off too.
Cyanogenrom not working???? HELP!
For some reason every time i dl the cyanogen rom on my g1 it doesnt work i do everything have followed every step and it doesnt work....but i downloaded jf just to see if it worked and it did but im still wondering why this cyanogen rom 4.0.4 doesnt work??? [email protected]
So just like everyone else i've got a bricked i9000m. So before i send it off to repair (thats if they take it that is), Im sorta curious what fixes have all you out there tried on your phones?
So far i have flashed with odin1.3 to jh2 and now stuck a the "S" boot screen.
Is there a way to get cwm recovery on a phone that dont boot?
patman18 said:
So just like everyone else i've got a bricked i9000m. So before i send it off to repair (thats if they take it that is), Im sorta curious what fixes have all you out there tried on your phones?
So far i have flashed with odin1.3 to jh2 and now stuck a the "S" boot screen.
Is there a way to get cwm recovery on a phone that dont boot?
Click to expand...
Click to collapse
i bricked my phone many times.i flash back to xxjm8 from samfirmwares.com, thats the password aswell you will have to register its free. if it does not work first time try flashinging again.use ordin 1.7 its good.you can get all your updates from ther without getting confussed on the fourm, i have been stuck on that screen many times trying to root my fone on the new 2.2.1 firmware.go to google type xxjpu galaxy root. the is a web site give you xxjpx rooted with voodoo + some cool tools follow all the steps to the letter,if you can print it off its only three pages .
what about adb ? Did tried it ?
a hammer
i flashed back to jh2 after it was in a boot loop from jk4 and then it wouldnt even turn on.. sent back for repair
bobekk said:
what about adb ? Did tried it ?
Click to expand...
Click to collapse
tried it
i can't get the phone to connect. keep getting the stupid "unmounted sd......." crap.
but the funny thing is i can get in to dnl mode reflash with odin, and everything works fine no error codes. But the phone won't boot. keep getting stuck at the s screen
workaround
I've tried everything i can find, i used adb and mounted the card in windows then formatted the card (there is a how to on here for that) but that didn't work. I've tried multiple roms and kernels but i still have the same problem. It seems that my only option is to send it in for warranty. But, if you want to use your phone over the holidays or wait for samsung to come out with an answer before sending your phone in for repair there is a little work around that you can try to get your phone to boot. The phone will be fully functional except that you cannot use the internal SD nor an external SD. Thus, you won't be able to install or save anything to your phone.
to do this workaround just flash the bell froyo rom (there was another froyo rom that i had working but i can't remember which one) then install the voodoo lagfix kernel. When it boots you will hear the "cool voice" state that it is converting it to the ext4 partition and then it will boot into the OS. there will be a program or two that require a "force close" but at least you're phone will work until you can get it repaired. In settings under SD card you'll notice that it says there is no internal or external disk space that's just because you still have the SD corruption and that this is only a work around to get your phone to boot.
I'm curious, for those having this problem and can get into recovery mode, can you report if you're seeing an error msg under the menu and if so, what does it state? Thanks.
Where can you find the official firmware for the i9000m? I had a custom rom installed but my phone decided to brick - jpu worked fine but the minute i upgraded to jpx... Anyway I want to flash the official firmware and take my phone back to bell.
Thanks
I've ran my phone with the original Eclair rom for a couple weeks. I then figured that I couldn't wait for the froyo rom. I've been running the Spike Speedy OC rom, with the JK4 modem and voodoo lagfix. The phone was running just great, very fast. I then changed the lagfix to overkill ext4. Some hours later, the phone hung up. When I rebooted it, it said that the configuration had changed. I saw that one of the options was back to RFS.
What?? It's formatted as ext4. Oh sh*t. Well it didn't boot back up.
I've tried flashing every different firmware I could find. I then tried to re-format the SD manually and found that the partition table was bad.
I've tried to reformat both SD card partitions. The system one (p2) formatted fine, but the "internal SD" (p1) storage one wouldn't format. When I ran fdisk on it, it told me that the partitions didn't end on cylinder boundaries.
Then, I (mistake) flashed a T959 firmware on it. At that point, I wasn't able to get into the download mode using the 3-button combo. Oh shi*... Now I really messed this up. I've managed to get it into download mode using ADB and flash the bell firmware back on it. Oh yeah!! Here we go again.
After the fact that I had installed the T959 and flashed back I9000 firmware, I couldn't find the /dev/block/mmc*** anymore. As if the SD didn't load up.
At that point I inserted a microSD in, and it was recognized as the internal SD. I managed to partition and use that external microSD card just like the internal one and got the phone to boot and work. However, no storage.
All of which I was trying to do while my USB connection was on-and-off, because the usb connector was damaged. It initially had corrosion because my car plug that was kept on the floor of the car, with all the dirt, water and snow. I used alcohol and a tooth brush to clean it, between flashes. As well, flashing it through a VirtualBox VM since I'm on Ubuntu. Sh*t..
This morning I figured I would stop trying, flashed the JH2 firmware on it and brought it to Bell. I tried to get a refund with the argument that this phone is badly designed - with the samsung movinand flash chip - and that it would fail again even if they fix it. It didn't work out for me since I bought the phone about 40 days ago. I was thinking of getting a refund and buy a Nexus S, when a compatible one comes out. It has a different flash chip - a iNand from Sandisk I believe. Oh well. If it fails again, I can still call VISA and give it a try through the purchase protection plan. I have to mention too that I tried calling bell with my concerns - nothing they would do too.
I don't recommend you take my approach. IMO, maybe try, as root, to check the partitions using fdisk /dev/block/mmc(something) and if they appear ok, try to format the SD card using fat.format /dev/block/mmc(something)p1 - but that's it. I'm an experienced linux user, but I'm not a developper. I don't even clearly understand this ODIN flashing stuff. It's like not all firmware you find on the net have the same amount of components inside. I'm thinking stuff from the other flashing is still remaining, not replaced by the later flashes.
I have to say that the next time I'll approach this using fdisk and fat.format only (If I've got a recovery mode working, with root and adb support). Perhaps I will write down the numbers for where the partitions start and end on this SD card when I get my refurbished phone.
Some might say that I had time to spare... I wrote this for you that might be thinking of fixing your 600$ brick yourself.
Hey
I had posted earlier about my N1 not connecting to my network. I thought the problem was fixed, but I guess I was wrong. The problem is deeper than that. I flashed CM7 Nightly. All was well but the mobile network wasn't working. The reception bars were zero with a small cross on them. I flashed MM's Gingerbread. The network got stuck like that. No bars. On the lockscreen it read "(No Service)|Airtel" (airtel being the name of my service provider). Then I found out that audio wasn't working either. No audio from the speakers or 3.5mm jack. I changed roms, changed sims, everything. Nothing worked. I tried my sim in another phone and it worked perfectly.
I then tried updating the hboot. It seemed to have worked but a reboot later I was back on square one.
I then tried to update my radio (I'm on 4.6. Tried to update to 5.12) but on connecting the USB cable the notification didn't pop up. The charging LED lit up but that's all. I tried mounting my SD card through AmonRA's recovery but my PC did not detect it.
What could be wrong with my Nexus One? I've been using this phone for about 10 months now and after this I'm back to my old Sony Ericsson w705. It's unbearable. Somebody please help me. Any help will be appreciated.
Regards
Raptor
Have you tried returning to stock to see if the situation improves?
You did do a nandroid backup of your stock ROM before flashing everything yes?
DirkGently1 said:
Have you tried returning to stock to see if the situation improves?
You did do a nandroid backup of your stock ROM before flashing everything yes?
Click to expand...
Click to collapse
I rooted when I still had eclair and haven't been on stock ever since. I have a nandroid backup of my stock eclair ROM. I think I'll download a stock FRF91 and try it. I updated the radio to 5.12 but it has had no effect on the problem. I'll try a stock 2.2 ROM tomorrow since it's night here in India right now. Thanks for your response.
Regards
Raptor
Hey, sorry for my long absence. I had been caught up.
Well, here's where I stand: I tried all the roms I could find- stock 2.2, cm 5, cm 6, cm 7, MIUI, 2.3, everything. But my phone just shows no service. Nothing in the device status too. There is no audio, neither through the speaker, nor through the 3.5mm port. And the worst of all, it refuses to mount the SD card. When I connect my N1 to my PC the charging LED glows orange but no USB mount message appears. I've tried mount widgets and apps but nothing happens. I can't even mount the SD card through the recovery (Amon RA, latest). I tried ADB devices but it didn't show any connected devices. What should I do?
I'm currently using my old Sony Ericsson w705 and going from Android to J2ME isn't really something anyone would like. I will be really grateful if someone could help me fix my beloved N1.
Regards
Raptor
I guess you're out of options - restore your phone to stock and send to HTC for repairs. This seems to be the only answer to your troubles.
Read my signature, look there for Unroot/restore guide, PASSIMG method, using FRG33 ROM. Execute the guide. If your phone starts working - great, if not - send to HTC.
Jack_R1 said:
I guess you're out of options - restore your phone to stock and send to HTC for repairs. This seems to be the only answer to your troubles.
Read my signature, look there for Unroot/restore guide, PASSIMG method, using FRG33 ROM. Execute the guide. If your phone starts working - great, if not - send to HTC.
Click to expand...
Click to collapse
I guess that's what I'll have to do. Thanks for your response. I'll get down to restoring it to stock.
Regards
Raptor
Sent from my Nexus One using XDA App
Hey
I tried the PASSIMG.zip method. I got back to stock hoping it would fix the problems but no luck there. I live in India so it's unlikely I will be able to send the phone to HTC. Besides, I unlocked my bootloader so my warranty is void.
Anyway, I think I may have found a lead. After the PASSIMG.zip didn't fix it, I went back to CM7 nightlies. I installed SPB shell ui. It comes with it's own wallpaper and changed my wallpaper to its own wallpaper. Anyway, I was updating the nightly build and I did a complete wipe a couple of times. After I flashed the new build and it booted, I realized that the wallpaper from the SPB shell ui was still there. I have a habit of wiping every time I flash. When I updated again it was gone. But a few builds later it was back.
What I think is that there is something wrong in the system partition and clearing it might solve the problem. But then again, I might be wrong. I would appreciate some advice on this matter.
Regards
Raptor
Edit: I wiped the /system partition through root explorer. It didn't fix the problem. Could there be some other files in the phone memory that could be causing this problem?
Hi guys,
Gone through about 100 threads these last couple of days, but nothing helps, so have to start a new one.
What happened was that the other day my phone started ringing.
The screen however was black, so I could neither see who was calling nor answer the call.
I let it ring out, then I held the power button so it would shutdown.
Tried to restart it, and that's when the fun started.
The phone got stuck in a boot-loop, only showing the Galaxy S logo (not getting to the animated one).
Left it in this loop for several hours, since I've had problems recently with the phone needing to do this cycle 5-10 times before booting up.
This time it wouldn't boot, however.
I've tried putting the phone in a bag of rice for 18 hours, in case of any moisture inside, not helping.
Then I tried recovery-mode, formatting the whole thing, but I got the following error:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
Found this thread to try to fix the format error.
Got into download mode, but Odin does not recognize the phone, and I started believing all hope for fixing it without sending it in was gone.
I've also tried applying a couple of update.zip's from the SD-card, just to have tried it, but every package got Signature verifcation-error.
Anyway, when I headed to bed last night I left the phone in the boot-loop, and to my surprice, 8 hours later it had booted into first-time configuration.
YES!!!
Configured the phone with language etc., then all of a sudden the animated Galaxy S logo appeared...
And it appeared again, and again, and again for about 15 min., until I unplugged the battery.
And now I'm back at square one, stuck in the boot-loop (not getting to the animated logo)...
I have the latest versjon of KIES, not that it probably matters.
Does anyone have an idea of what the problem might be?
What rom were you using? stock or custom? Maybe it has something to do with lagfix if it was activated... im guesing, im not dev just normal user... Maybe try to reinstal usb drivers.
Just use odin 1.3 reflash official rom , everything would be OK.
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
mortenlm said:
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
Click to expand...
Click to collapse
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
porkapple said:
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
Click to expand...
Click to collapse
Well, I would have if I knew... But stupid me thought that a phone was a phone.
How wrong was I?
Anyway, a little update here (the problem is kind of solved now):
Flashed the phone with 2.3.3 Gingerbread I found on dkszone, after running the steps in the previous mentioned thread.
And the phone started like a charm.
But after a few hours of configuring etc, I managed to insert the SD-card again, and all hell broke loose again...
Come to think about it, thats what I did yesterday too, so I've come to the conclusion that the SD-card is the main problem...
However, now the phone is slow... REAL slow... Kind of like my 1.5 year old HTC Touch Diamond 2 with WP6.5...
It takes up to 2 seconds to open menu items, keyboard etc.
Is there any way to fix that?
Or should I flash it with another ROM?
You mean the external sdcard? Maybe try to format it...
OK, so this is what I've now figured out:
The phone is damaged...
It seems that the internal SD has gone AWAL, and internal storage has somehow created itself on the external SD-card, thus the phone crashed when I switched cards...
When trying to format the USB-storage, I receive error: SD-card has been removed
So I guess I have to ship the phone off to Samsung ASAP...