Related
Good evening. Yes I am a n00b when it comes to Android. I have been trying to install the latest 2.2 rom from Cognition, V2.3b6. I have a Samsung Captivate. I get it to install fine except I have no phone. I get no bars and no 3G indicators. I go to status and it says I have no phone #, doesn't know network, etc. It appears it's not seeing the sim card?
I'm using Rom-Manager Clockwork mod to do the install.
Anyone have an idea what I am doing wrong? I have just used Odin 3 one-click to restore to factory (again) and saw I did not have a sim card installed and I've just powered down, reinstalled SIM and I get my 3G indicator and my full signal bars.
Help. I'm nervous about trying to do this again because I don't know why it is doing this. It worked on the first Samsung Captivate I had but I had to exchange it out because it had problems.
I've always believed to stop when I'm not sure what to do next.
Any suggestions would be greatly appreciated. I've just restored to factory. Might re-root it and be done with it.
Are you certain you installed the SIM card correctly? I've done it a bunch of times myself.
Sim card
Yes I did. In fact, when I did the flash from 2.1 to the 2.2 the sim card was already inserted. Was I supposed to remove it first? I hadn't read anywhere about taking it out before flashing to the new rom.
You aren't suppose to flash with a SIM card inserted, or any external SD card inserted either. It won't hurt, try to flash Cognition again. Remember to use ODIN to go back to JF6 first though.
norcal einstein said:
You aren't suppose to flash with a SIM card inserted, or any external SD card inserted either. It won't hurt, try to flash Cognition again. Remember to use ODIN to go back to JF6 first though.
Click to expand...
Click to collapse
Wrong - Always have use cwm & flashed with everything inserted - never a problem except when I screwed the pooch on the TiBu & opted to restore the system files too
OP - sounds like like a bad flash, I'd re-download it & reflash. You already know you can get back with Odin, so there's no downside.
ratflinger said:
Wrong - Always have use cwm & flashed with everything inserted - never a problem except when I screwed the pooch on the TiBu & opted to restore the system files too
OP - sounds like like a bad flash, I'd re-download it & reflash. You already know you can get back with Odin, so there's no downside.
Click to expand...
Click to collapse
Sorry for the back and forth banter, do yourself a favor and remove sim before flashing. It does not always cause problems but has been known to cause your exact issue
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks
Ok guys thanks.
I knew not to have the SD card inserted except when you are flashing rom. It's my understanding the SD card is used for storage. I will try flashing it without the SIM card installed and see how it goes.
kg4zxk said:
Ok guys thanks.
I knew not to have the SD card inserted except when you are flashing rom. It's my understanding the SD card is used for storage. I will try flashing it without the SIM card installed and see how it goes.
Click to expand...
Click to collapse
Just remove all of the cards.
Thanks!
Ok. I reflashed the ROM without the SIM card inserted. I saw it recognized there was no SIM installed and now I have my cellular connection.
Thank you guys for your advice!!!
Sluggish
I do notice that the phone is sluggish now with the 2.2 rom. Geeze.
If you have not done so reboot a couple of times. The lag fix on that build usually works better after a couple boots.
after
kg4zxk said:
I do notice that the phone is sluggish now with the 2.2 rom. Geeze.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
I flashed WCX successfully. It boots up. But no wifi (eternally says it's turning on), no BT, and no phone connection. Exactly what it was doing BEFORE I flashed.
This all began with the OTA AT&T update. Everything worked fine until then.
I even wiped everything in the recovery wipe menu. Still no good. I threw my sim into a buddy's phone. SIM works fine.
So is this phone hardware-borked somehow? Is there a way to test the device to see? Or is there something I need to do software-wise?
Otherwise, I have to flash a stock AT&T ROM and S-ON so I can get it warranty replaced.
Here is how it began... phone arrived in the mail, new from AT&T on the last day of August. This is what I did/what happened:
1. HTCdev unlocked.
2. Rooted.
3. OTA alert came, but I postponed.
4. OTA somehow autostarted on a reboot.
5. OTA failed in usual way like a lot of other people.
6. Wiped all data/ restore to factory original.
7. Got back into Android but Wifi and BT didn't work (like with a lot of people). Mobile data and calling worked fine, as did SMS.
8. Did the S-off late last night.
9. Noticed telephone/data stopped working today.
10. Wiped everything as part of the WCX process, formatted internal SD.
11. Flashed new boot kernel and WCX ROM, from my SD card.
12. Still no Wifi, BT, or Phone/data. Twelve steps of bullsh*t.
13. After a bit of time, a few reboots (maybe that was the "settling in" part your instructions mentioned), now I have mobile data and telephone again. But still no wifi or BT.
WIFI has always sayd "Turning on wifi" or whatever, but it just stays there. BT never turns on when you try. Been like this since the OTA forced itself on me.
Suleeto said:
I flashed WCX successfully. It boots up. But no wifi (eternally says it's turning on), no BT, and no phone connection. Exactly what it was doing BEFORE I flashed.
This all began with the OTA AT&T update. Everything worked fine until then.
I even wiped everything in the recovery wipe menu. Still no good. I threw my sim into a buddy's phone. SIM works fine.
So is this phone hardware-borked somehow? Is there a way to test the device to see? Or is there something I need to do software-wise?
Otherwise, I have to flash a stock AT&T ROM and S-ON so I can get it warranty replaced.
Here is how it began... phone arrived in the mail, new from AT&T on the last day of August. This is what I did/what happened:
1. HTCdev unlocked.
2. Rooted.
3. OTA alert came, but I postponed.
4. OTA somehow autostarted on a reboot.
5. OTA failed in usual way like a lot of other people.
6. Wiped all data/ restore to factory original.
7. Got back into Android but Wifi and BT didn't work (like with a lot of people). Mobile data and calling worked fine, as did SMS.
8. Did the S-off late last night.
9. Noticed telephone/data stopped working today.
10. Wiped everything as part of the WCX process, formatted internal SD.
11. Flashed new boot kernel and WCX ROM, from my SD card.
12. Still no Wifi, BT, or Phone/data. Twelve steps of bullsh*t.
13. After a bit of time, a few reboots (maybe that was the "settling in" part your instructions mentioned), now I have mobile data and telephone again. But still no wifi or BT.
WIFI has always sayd "Turning on wifi" or whatever, but it just stays there. BT never turns on when you try. Been like this since the OTA forced itself on me.
Click to expand...
Click to collapse
You have to flash the kernel manually...his roms are not made for soff users...so there is no script to flash the kernel...
So use fastboot to flash the kernel or flashimagegui.apk located in the themes and app section for the vivid...you may need to do one more flash after flashing the kernel
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
mg2195 said:
You have to flash the kernel manually...his roms are not made for soff users...so there is no script to flash the kernel...
So use fastboot to flash the kernel or flashimagegui.apk located in the themes and app section for the vivid...you may need to do one more flash after flashing the kernel
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Yip. That's hopefully your only problem. You can always confirm your kernel version from System -> About phone -> Software screen.
yes I that the boot.img has to be flashed from the fastboot command across windows, and while in the bootloader. Which is what I did. The instructions are not only specific, but very well written and easy to understand.
Instead of saying:
11. Flashed new boot kernel and WCX ROM, from my SD card.
Click to expand...
Click to collapse
what I should have said was,
11. Flashed new boot kernel via fastboot off of my PC, WIPED EVERYTHING via Recovery, one option at a time, INCLUDING formatting the internal_SD, and THEN flashed WCX ROM from my SD card
Click to expand...
Click to collapse
I am still concerned that there is something else wrong with my phone. This is why I was wondering if there was a way to test it. Because if I understand right, flashbooting FROM MY PC the new boot.img, followed by a complete and categorical wipe, and then flashing WCX should have essentially started EVERYTHING fresh, with no software hangups. As in no programming at all.
But... here I am, with no Bluetooth and no wifi. Mobile data and telephone still working as of this morning.
I just find it strange that everything worked (to the best of my knowledge) fine before the stupid OTA from AT&T.
It frustrates the hell outta me because it makes no sense!
Currently:
Kernel:
3.0.36-WCX-ILLUMINATI-v2
Damn dude, maybe you are having a hardware issue... If the kernel/ROM is properly installed, then I'm out of ideas for now.
If you are s-off... Flash kozmik's kernel... Always solved my bluetooth/WiFi problems...
Usually it's a screwed /system/lib/modules that causes problems like that
Sent from my HTC PH39100 using Tapatalk 2
Where can I find that kernel?
Edit: nvm found his thread...
http://forum.xda-developers.com/showthread.php?t=1572015
Kozmik had no affect.
Going to redo everything
Try an RUU. For some reason my phone scrapped out on me the other day I flashed a Rom and was replacing system apps with aosp apps and it bootlooped and wouldn't even load recovery. Had to ruu then HTC dev unlock then root. Luckily I was s-off
Sent from my HTC Holiday using xda premium
Hi all,
First time poster; be nice please
I've recently upgraded my HTC Velocity with the CM10 and AOKP mods and both have been working great.
Prior to this, I had the ICS ROM installed which was posted by Leigh Kennedy (if memory serves).
Anyway, the issue I'm having is with both of the JB ROMs above, the SD Card is not detectable at all. When the phone boots, sometimes it will mount, sometimes it won't. When it doesn't mount, I do so manually via Settings > Storage > Mount SD Card.
It will mount successfully, and I can browse through the card via File Explorer (with Root Access), so it's definitely accessible.
However I find that any apps that require SD Card access (ie. Camera, Recording Software, Music even) say that there is no SD Card detected/inserted.
I've tried 3 different MicroSD cards (2GB, 8GB and 32GB (32GB is my main card), and completely wiped them and reformatted to FAT32), no change to the detection issue.
I've also tried to format via CWM in Recovery Mode, which shows to be successful on the format, but no change to the issue.
I initially thought it was the 32GB MicroSD card having the problem, but the same issue replicating on 2 other cards tells me otherwise.
I've completely wiped my phone clean each time (Data, System, Cache and Dalvik Cache), no change to the problem (which funnily enough doesn't make a lot of sense as I can access the SD Card in Recovery Mode perfectly fine?)
Any help with this one is greatly appreciated, as I'm at a loss
NB: My SD Card was working fine on ICS, the issue only started after upgrading to the JB ROMs above.
evakq8r said:
Hi all,
First time poster; be nice please
I've recently upgraded my HTC Velocity with the CM10 and AOKP mods and both have been working great.
Prior to this, I had the ICS ROM installed which was posted by Leigh Kennedy (if memory serves).
Anyway, the issue I'm having is with both of the JB ROMs above, the SD Card is not detectable at all. When the phone boots, sometimes it will mount, sometimes it won't. When it doesn't mount, I do so manually via Settings > Storage > Mount SD Card.
It will mount successfully, and I can browse through the card via File Explorer (with Root Access), so it's definitely accessible.
However I find that any apps that require SD Card access (ie. Camera, Recording Software, Music even) say that there is no SD Card detected/inserted.
I've tried 3 different MicroSD cards (2GB, 8GB and 32GB (32GB is my main card), and completely wiped them and reformatted to FAT32), no change to the detection issue.
I've also tried to format via CWM in Recovery Mode, which shows to be successful on the format, but no change to the issue.
I initially thought it was the 32GB MicroSD card having the problem, but the same issue replicating on 2 other cards tells me otherwise.
I've completely wiped my phone clean each time (Data, System, Cache and Dalvik Cache), no change to the problem (which funnily enough doesn't make a lot of sense as I can access the SD Card in Recovery Mode perfectly fine?)
Any help with this one is greatly appreciated, as I'm at a loss
NB: My SD Card was working fine on ICS, the issue only started after upgrading to the JB ROMs above.
Click to expand...
Click to collapse
while the sd not being accessible on your computer is known, you should still be able to access via file browsers and other apps that need access. my camera stores to internal, and Apollo seems to find music on my external without a hitch. Unfortunately it sounds like you've done everything I would suggest, short of trying a Factory Reset
homeslice976 said:
while the sd not being accessible on your computer is known, you should still be able to access via file browsers and other apps that need access. my camera stores to internal, and Apollo seems to find music on my external without a hitch. Unfortunately it sounds like you've done everything I would suggest, short of trying a Factory Reset
Click to expand...
Click to collapse
Thanks for the reply homeslice.
I just tried a Factory Reset then, and unfortunately to no avail
I'm surprised that I'm the only person with this particular issue on this phone (I've seen other posts on different handsets with a similar issue, which was deemed to be the SD Card, but in my case all 3 of the ones I've tested have fallen short of fixing the problem).
Got any other ideas? Because I love both ROMs, but the issue with the SD card is more annoying than anything.
EDIT: Ok, just reformatted everything once more, and installed the PAC-Man ROM, still broken.
Whether it's relevant or not, I even partitioned the SD Card to see whether the phone could pick it up via different apps, no chance.
Where did you partition the card and with what software...
I would recommend either using the phone or recovery...
Windows sometimes makes cards unusuable
Sent from my Holiday using Tapatalk 2
I partitioned the SD card via CWM recovery, twice.
Still don't know what is causing it
Anyone else?
Sent from my HTC Velocity using xda-developers app
Switch recoveries...
I recommend twrp...
Others like wcxrecovery...
Sent from my Holiday using Tapatalk 2
Really? The recovery could be causing this? Hmm.. not something I considered but happy to try it.
Won't he able to do so till late tonight, early tomorrow morning but I'll let you know how it goes.
Thanks for the advice!
Sent from my HTC Velocity using xda-developers app
rignfool said:
Switch recoveries...
I recommend twrp...
Others like wcxrecovery...
Sent from my Holiday using Tapatalk 2
Click to expand...
Click to collapse
OK, so I managed to flash TWRP Recovery successfully (couldn't do it via the Goo Manager, had to flash it manually via adb which was fine).
Sadly, the SD card issue still exists.
One thing I did notice however, with TWRP every time I tried to clear anything (Data/System/Cache/Dalvik Cache/Factory Reset), it came up 'Unable to mount emmc'.
Now I'm not entirely sure what this is, but the only time I have seen it is when loading Bootloader (as eMMC-boot).
Does this have any relevance to my current problem? CWM never used to error out like that.
NB: Having a hard time trying to find a link for download of WCX Recovery (could just be tired from work, who knows), but I'll keep trying.
I am not sure...
Can you make phone calls if your phone boots...
It sounds like you might have lost your efs partition... where your imei lives...
I am not sure how to fix...
I think there is a thread talking about it
Sent from my Holiday using Tapatalk 2
rignfool said:
I am not sure...
Can you make phone calls if your phone boots...
It sounds like you might have lost your efs partition... where your imei lives...
I am not sure how to fix...
I think there is a thread talking about it
Sent from my Holiday using Tapatalk 2
Click to expand...
Click to collapse
Hmm, well the IMEI is still available via About Phone, so not sure if that's the same as what you're referring to.
However, I think I've had a development (not a good one though).
After reflashing CWM I tried mounting and/or reformatting emmc, it's unable to do anything with emmc at all.
When the recovery was TWRP, it didn't like emmc either, so something tells me emmc plus my storage issue are related.
I've done as much as I can think of, short of relocking bootloader and reflashing the RUU for the Velocity (which is currently being downloaded).
Can anyone think of anything else? Or is an RUU flash my absolute last resort?
Thanks for help so far guys, much appreciated.
EDIT: Helps if I actually answer your question rignfool.. lol. Yeah I can do absolutely anything I would normally on this phone with the custom ROM, short of apps accessing storage.
Well.. things have now taken a turn for the worst.
5% into my RUU reflash, ROM Utility crashes and now phone is stuck on an RUU bootloop....
Still trying to work it out, but I get the feeling it's not gonna go well..
evakq8r said:
Well.. things have now taken a turn for the worst.
5% into my RUU reflash, ROM Utility crashes and now phone is stuck on an RUU bootloop....
Still trying to work it out, but I get the feeling it's not gonna go well..
Click to expand...
Click to collapse
Did you relock the bootloader before running the RUU? This is necessary. Also, were you last running an ICS ROM? If you were, you have an ICS boot loader and you need to run an ICS RUU. Lastly, make sure you are in Fastboot USB mode when running the RUU
homeslice976 said:
Did you relock the bootloader before running the RUU? This is necessary. Also, were you last running an ICS ROM? If you were, you have an ICS boot loader and you need to run an ICS RUU. Lastly, make sure you are in Fastboot USB mode when running the RUU
Click to expand...
Click to collapse
Yeah, definitely made sure that bootloader was locked/relocked, as I found the RUU kept crashing when it was unlocked (couldn't read any information off the phone, and the phone auto-booted into Fastboot after relocking the bootloader in any case, as it couldn't load the OS).
And no I wasn't running an ICS ROM at the time (per my initial post of running 2 JB ROMs at different times (CM10 and AOKP)).
After a bit of perseverance I got the RUU to go through successfully, and lo and behold the SD Card issue has miraculously disappeared (which isn't overly surprising considering it's gone right back to Factory Defaults and some).
It seems the PC required the Utility to run in Realtime Priority as opposed to Normal.. lol.
I'll now look into reflashing the relevant JB ROMs and post back shortly with results.
WOOHOO! ..... I mean, yeah, it works now. lol
It seems that during the course of flashing the ROMs previously, my phone lost touch with itself; by that I mean it was unable to access it's own Internal Storage and part of it's External Storage (which seems to be part and parcel of the 'emmc' error I was receiving earlier).
Camera loads, Music loads, it all works! :victory:
Thanks for your help homeslice and rignfool, much appreciated.
Now to enjoy those ROMs to their full potential!
On a side note though, have you ever had an issue reported like this on any other handset homeslice? or rignfool for that matter?
The only time I heard of people not being able to access storage like that... was when their imei got wiped...
From what I understand its a clockwork issue
Sent from my Holiday using Tapatalk 2
The only time I heard of people not being able to access storage like that... was when their imei got wiped...
From what I understand its a clockwork issue
Sent from my Holiday using Tapatalk 2
Click to expand...
Click to collapse
Yup. Our version of cwm likes to corrupt partitions. Glad you got it sorted
Sent from my Vivid 4G using Tapatalk 2
Thanks a bunch guys, much appreciated.
Sent from my Holiday using xda app-developers app
NB: Having a hard time trying to find a link for download of WCX Recovery (could just be tired from work, who knows), but I'll keep trying.[/QUOTE]
When you said NB, i thought of grand theft auto IV. lol. damn you Rockstar for corrupting meeee
that is why i've never tried cwm recovery. only tried twrp and wcx and i've always stuck with wcx recovery i like using the capacitive buttons to scroll instead of the volume buttons
XxSHaDoWxSLaYeRxX said:
When you said NB, i thought of grand theft auto IV. lol. damn you Rockstar for corrupting meeee
Click to expand...
Click to collapse
Haha, I thought of that too when I posted these issues.
ZeRo2o9 said:
that is why i've never tried cwm recovery. only tried twrp and wcx and i've always stuck with wcx recovery i like using the capacitive buttons to scroll instead of the volume buttons
Click to expand...
Click to collapse
Yeah I did manage to find a working recovery image for wcxrecovery eventually, but I find TWRP a lot better to be honest (CWM and WCX are also good though).
I guess it's just personal preference.
I would be ok with this if it wasn't almost every time the phone is left alone.
i thought maybe installing CM would help but it still does it, went back to stock firmware (S5830DTLKI4) with no resolution.
It appeared to only be doing it when it is put to sleep, but after i unlocked it and tried to send a text with my Bell Canada sim card the phone restarted again.
It certainly isnt a SoD, because it is turning itself back on.
wifi is off, GPS is off, Bluetooth is off, and it is doing this on a 100% stock install; no market apps installed, no google account even linked.
so it appears to be restarting when i let it go to sleep, and when i try and send a text using a non-Koodo sim card. (although i dont know the effects with a Koodo sim; never had one)
I went to samfirmware and downloaded a md5 for the UK network Orange, but it didnt fix anything as far as i know, i didnt unlock it but it was still restarting itself.
Im wondering is this a software issue (if so, what is happening and is there a way to fix it?), or is this a hardware issue (perhaps there is a faulty capacitor somewhere on the board that isnt filtering voltage spikes and causing the device to reboot because of that)?
i couldn't find any references to this problem ever really being addressed.
help would be greatly appreciated.
The stock Samsung firmware for a Koodo S5830D is unstable, often when I was using it I would get reboots and freezing and a NO SIM CARD error constantly. If you have it rooted and want to install a custom ROM that won't reboot itself, I would recommend taking a look at CM9.1 RC4.1 by Wayland_ACE. I have never experienced a random reboot on that ROM. http://forum.xda-developers.com/showthread.php?t=1868121
Although of course you have to choose the right ROM for you. If you want to stay on Gingerbread, the official CM ROM (or an unofficial version) for the Ace should do the trick. If you don't care as much about stability experiment!
If the firmware is unstable (as it is with Koodo's stock ROM) it won't matter if it is locked or unlocked, if you want stability, change your ROM.
Narwhal73 said:
The stock Samsung firmware for a Koodo S5830D is unstable, often when I was using it I would get reboots and freezing and a NO SIM CARD error constantly. If you have it rooted and want to install a custom ROM that won't reboot itself, I would recommend taking a look at CM9.1 RC4.1 by Wayland_ACE. I have never experienced a random reboot on that ROM. http://forum.xda-developers.com/showthread.php?t=1868121
Although of course you have to choose the right ROM for you. If you want to stay on Gingerbread, the official CM ROM (or an unofficial version) for the Ace should do the trick. If you don't care as much about stability experiment!
If the firmware is unstable (as it is with Koodo's stock ROM) it won't matter if it is locked or unlocked, if you want stability, change your ROM.
Click to expand...
Click to collapse
i tried installing the rom you linked to but im still getting the reboot problem; is there something im doing wrong?
i wiped the user data, cleared the cache, and wiped dalvik, then installed the rom you linked, using clockwork 5.0.2.6
however it still seems to want to reboot, what is going on here?
blueblitzpup said:
i tried installing the rom you linked to but im still getting the reboot problem; is there something im doing wrong?
i wiped the user data, cleared the cache, and wiped dalvik, then installed the rom you linked, using clockwork 5.0.2.6
however it still seems to want to reboot, what is going on here?
Click to expand...
Click to collapse
In CWM go into mounts and storage> mount /data, /system, /sdcard. Should fix bootloop.
Narwhal73 said:
In CWM go into mounts and storage> mount /data, /system, /sdcard. Should fix bootloop.
Click to expand...
Click to collapse
its not a bootloop though, it's booting into CM and then once the screen goes to sleep the phone restarts itself, just like it did on the stock rom.
i already tried mounting data, system and sdcard, but it didnt help any.
Last resort... After flashing via odin, reboot into recovery & do a factory reset. If the problem persists, stop posting here & rush to service centre with the unrooted stock rom on your phone.
Sent from my GT-S5830 using xda premium
Venomous Viper 119 said:
Last resort... After flashing via odin, reboot into recovery & do a factory reset. If the problem persists, stop posting here & rush to service centre with the unrooted stock rom on your phone.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
i was hoping id get a better answer than that, but ok then.
ive always hit factory reset and clear cache before using a stock rom, else it will boot loop.
i suppose i'll reload the stock firmware and take it in to the nearest mobile center, i dont know how much good itll do though, the phone is from anther carrier and i got no warranty papers when i bought it off a friend.
racer_25 said:
i was hoping id get a better answer than that, but ok then.
ive always hit factory reset and clear cache before using a stock rom, else it will boot loop.
i suppose i'll reload the stock firmware and take it in to the nearest mobile center, i dont know how much good itll do though, the phone is from anther carrier and i got no warranty papers when i bought it off a friend.
Click to expand...
Click to collapse
Since you don't have the warranty, you'll have to pay for the service anyway. Just be sure that the phone serial no. that's on the label after taking out the battery is intact & you are all fine to get a clean service. There's nothing much you can do by yourself as it doesn't appear to be a software problem. But it might quite happen b'coz of a faulty battery. My friend's galaxy y had the issue & a replacement killed it. So may be it with you. Anyways, before buying you can try it out with your friend's battery & hope to see if the issue is solved & then go buy one. If this doesn't help, head for service as said earlier.
Sent from my GT-S5830 using xda premium
Hey guy's Im hoping you can help me.
Last night while browsing my phone froze, so i performed a battery pull and on putting it back in the phone refuses to boot.
If i plug thr charger in alone, the LED's blink orange/green
If i place a battery in the charging light turns on. I have two batteries so I tried them both. Still nothing.
I was able to boot into recovery and tried to clear the clash and do a full reset. upon reboot the phone stuck on the boot screen.
I tried a battery pull once again, and since that I have only been able to get the phone to boot once after numerous tries only to get 7 vibrations.
The power button still works, if i try turning it on while on charge the orange light goes out, but nothing.
Ive tried the battery trick while on the charger alone the green light goes on but again nothing, I've tried different chargers, I'm now at a loss.
While typing this IVe been able to get it to boot once again, but again i get 7 vibrations and nothing.
Any help would be appreciated, I have no phone, while my GNEX is being repaired under warranty
A noob question... you said that you do a full reset... Did you flash the rom again? (give more details.. rooted phone...hboot.. rom...)
Obsy said:
A noob question... you said that you do a full reset... Did you flash the rom again? (give more details.. rooted phone...hboot.. rom...)
Click to expand...
Click to collapse
full reset as in going into recovery and wiping everything, unfortunately, I have note been able to get back in since to try and reflash a new rom.
I'm currently running a stock hboot, with the last stable release of MIUI before MIUI4 cant remember the exact version number. The phone is rooted and locked.
Thanks for the swift response
poseoff said:
full reset as in going into recovery and wiping everything, unfortunately, I have note been able to get back in since to try and reflash a new rom.
I'm currently running a stock hboot, with the last stable release of MIUI before MIUI4 cant remember the exact version number. The phone is rooted and locked.
Thanks for the swift response
Click to expand...
Click to collapse
Why don't you copy the miui zip onto your SD card, and flash it back from recovery? If you are running GB MIUI, the last version for that would be 2.3.30.
Sent from my Nexus One using xda app-developers app
sphinxcs898 said:
Why don't you copy the miui zip onto your SD card, and flash it back from recovery? If you are running GB MIUI, the last version for that would be 2.3.30.
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Agreed, I've preped my SDcard with a Passimg.zip. however I'm at a point where I cant get the phone to turn on constantly. since posting this morning. I've had no success - c'est la vie. I'm reluctantly thinking of moving on, however I really loved my N1 believe it or not it was much more reliable than my GNEX which is in under warranty repair for the 3rd time already!