Database Info

[Q] Curious Flashing (and sdcard?) problem!

Hey guys,
I have a problem, which i couldn't solve using the search. Sorry if i was too stupid to search at all
The thing is this:
I have a Nexus S I9020T which i bought as "broken"
It is stuck at the Google logo with the open lock. I thought i could save that device easily but i can't get that thing to work again.
At first: I still have my first android phone here: a Milestone. I had it for a year now and i would say that i flashed pretty much everything to that device. So i know a thing or two about android and flashing. But i have never had a nexus s in my hands before.
So i did this:
I Opened the Bootloader -> success
I flashed a few different CWM recovery -> also no problem here
I flashed a SU_2.3.6.1 which was already on the sdcard and it flashed without an error
I tried to delete all the files of the previous uswer -> at first I could delete all but as soon as i unmount and mount the usb storage, everything is back to the way it was. Means I can't delete or write anything onto the sdcard
Sometimes i have luck and i can write a .zip file to the card but as soon as I try to flash the ROM CWM says : e:can't open /sdcard/***.zip (bad)
so i know, that sometimes the zip files is just... bad. So i downloaded at least 10 different roms. Always the same problem.
I can'T format the SDcard, at every new mount, everything is back to how it was when i got the phone.
I tried to flash with Odin. But the only thing that changed was that i lost the recovery. So i flashed it new and here i am still stuck with that thing
Odin gets stuck while flashing with som PK[][][] thing -> screenshot. Doesn't seem to get further.. so flashin failed... any ideas?
So my question is:
Is there a problem with the SD card?
Is there just a problem with drivers?
Can My Phone be repaired?
Please you guys help me with your knowledge.
I am living in germany and the nexus is bought in the USW at bestbuy in december 2010. Does someone know how the warranty thing is handled for such a scenario?
Thanks a lot guys for even reading my problem.

[Q] [N8010] - Randomly stuck at boot unable to mount internalSD

Hi,
I've been following the forum for a while and have rooted / ROM'd several devices and never had any serious issues, until now:crying:.
I've been running james's rom (Resurrection Remix) on a Samsung N8010, this has been fine and worked perfect for months.
All of a sudden for no apparent reason the tablet has decided to not boot fully and gets stuck at the Samsung 10.1 screen.
I've tried flashing several different roms / restoring to factory / wiping data partitions etc with no luck.
Flashing anything other than the current rom seems to fail as it can't mount the internalSD in order to flash to it.
It appears that somehow the internal memory has screwed itself and is now unable to mount /dev/block/mmcblk1p1.
I've tried to view the logs but it seems as the internal is messed up this errors with similar results.
Trying to browse the internal sd through CWM just crashes CWM.
I can still boot into both odin and CWM with no problems but seem stuck in cwm as i'm unable to flash / return to stock via ODIN. Potentially i was thinking i could flash to stock via odin with the 3 file method to sort the partitions out, but it seems practically impossible to find any of these files anywhere!
These are the errors i seem to get are:
Skipping execution of extendedcommand , file not found
Cant partition non-vfat: datamedia
Can't partition unsafe device: dev/block/mmcblk1p1
Can't format unknown volume: /mmc
Your assistance on the matter would be greatly appretiated!
Thanks in advance,
Ash.

Gash128 said:
Hi,
I've been following the forum for a while and have rooted / ROM'd several devices and never had any serious issues, until now:crying:.
I've been running james's rom (Resurrection Remix) on a Samsung N8010, this has been fine and worked perfect for months.
All of a sudden for no apparent reason the tablet has decided to not boot fully and gets stuck at the Samsung 10.1 screen.
I've tried flashing several different roms / restoring to factory / wiping data partitions etc with no luck.
Flashing anything other than the current rom seems to fail as it can't mount the internalSD in order to flash to it.
It appears that somehow the internal memory has screwed itself and is now unable to mount /dev/block/mmcblk1p1.
I've tried to view the logs but it seems as the internal is messed up this errors with similar results.
Trying to browse the internal sd through CWM just crashes CWM.
I can still boot into both odin and CWM with no problems but seem stuck in cwm as i'm unable to flash / return to stock via ODIN. Potentially i was thinking i could flash to stock via odin with the 3 file method to sort the partitions out, but it seems practically impossible to find any of these files anywhere!
These are the errors i seem to get are:
Skipping execution of extendedcommand , file not found
Cant partition non-vfat: datamedia
Can't partition unsafe device: dev/block/mmcblk1p1
Can't format unknown volume: /mmc
Your assistance on the matter would be greatly appretiated!
Thanks in advance,
Ash.
Click to expand...
Click to collapse
Had this on a older device. Go back to the oldest version of factory rom you can find. Now to note so i can only recommend Sam mobile to find one.sounds liks as you said partition are corrupt. Going back to okd os version will redo partitions Is my thinking . I did this on my Acer a500 with issues as you describe I n ics .I went bach to honeycomb. It is a different file part arrangement.
Good luck and please double check and verify my thinking. Do not want you to brick over my advise
Erica Renee

erica_renee said:
Had this on a older device. Go back to the oldest version of factory rom you can find. Now to note so i can only recommend Sam mobile to find one.sounds liks as you said partition are corrupt. Going back to okd os version will redo partitions Is my thinking . I did this on my Acer a500 with issues as you describe I n ics .I went bach to honeycomb. It is a different file part arrangement.
Good luck and please double check and verify my thinking. Do not want you to brick over my advise
Erica Renee
Click to expand...
Click to collapse
Worked perfect thanks! Wiped and flashed via odin back to 4.0 and then re-flashedback to 4.2.2 now no more problems:laugh:

[q] PLEASE HELP PHONE SAYS SYSTEM UI HAS STOPPED WORKING

hi i need help i recently downloaded an app called pimp my rom...pretty cool i made some changes and rebooted my phone.. i did this for about 3 time and my phone seemed faster ... but i was tweaking with it and rebooted and i got stuck on the rethink possible screen, so i did i factory reset phone booted up fine ...then i got an error (system ui has stopped working) i clicked ok then got another error (setup has stopped working) now i stuck here.. i have the stock ics file on my computer but i have no custom recovery on my phone so i was wondering if i could flash it using the stock recovery or the pc software... but i don't quite know how to can some one please help me, I'm new to forms

come on guys ... i need my phone for monday

Fxz back to stock.
Sent from my MB865 using Tapatalk 2

Antonoram said:
come on guys ... i need my phone for monday
Click to expand...
Click to collapse
Try using RSD lite and flashing anyone of these ROMs depending upon the region your phone is from
http://sbf.droid-developers.org/edison/list.php (it has the list of all available stock ROMS)
You can find RSD lite on this link http://www.mediafire.com/download/5mvfxv88twuvh34/RSDLite5.7.msi
:laugh:

[Q] What type of brick is my Galaxy note 10.1 gt n8010 stuck?

Two days ago my Galaxy Note 10.1 gt-n8010 got stuck at the initial screen (Samsung Galaxy Note 10.1)
It was working normally, and it was last successfully upgraded to a custom rom and CWM 6.0.3.6 a month ago.
The custom rom was (to my best knowledge Android Revolution HD 11.2 - 4.1.2)
Booting into recovery and download modes works.
CWM recovery works partially. Erasing Cache en resetting to factory works, and sometimes results in getting to the second splash screen of the boot process where it again gets stuck (Samsung animation keeps glowing), but more it keeps getting stuck at he first boot screen.
Erasing Dalvic cache leads to immediate reboot.
CWM log files cant be opened / external sd card can't be reached/mounted.
So CWM is only working for a small part.
I've attached images of the CWM screens including a log-screen that shows that files and folders cannot be found.
Using ODIN, to flash a new CWM or custom/original ROM result in a FAIL message.
Tried different ODIN version, two original Samsung data cables and two computers. Alle the same result. FAIL.
I'm hesitant to continue now without some help. I might do more harm and destroy all chances there are to recover this tablet.
I've flashed all my phones and tablets before. I'm not an expert, but never had a mishap, because I triple read the instructions. The situation that arises now is not a result of a failed upgrade/flash, but suddenly appeared one morning.

On the last days i thought i had also broken my tablet and i had more or less the same problem. If i were you i would directly download an official 4.4.2 and flash it via odin. Then if you everything works i would try whatever you want to flash

Try changing recovery. Give TWRP a try. Had it happen with a phone and switching recoveries solved it.
Sent from my SM-N900T using XDA Free mobile app

Well I had the same problem due to toooo many consecutive reboots
I was on gnabo then wid twrp
then I reflashed 4.4.2 update via odin and everything was a breeze after that
and one more thing
be sure to change the recovery cause the same one might not work again
well at least it didn't do worth me
I use philz now

Can't flash anything
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?

Deadbeef said:
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Click to expand...
Click to collapse
are you sure you do not have a bad cable

I've used two different original Samsung cables. Same result.

Brick?
Change a Odin version like odin 3.07 http://forum.xda-developers.com/showthread.php?t=1837605?
your odin shows your device is Samsung I9505 Galaxy S4

Where does Odin show the device is a i9505? It's a n8010.

reCAPTCHA
I am having similar issues (Galaxy Note 10.1 N8010 Gnabo ROM) - stuck on the samsung logo (never managed to get past it though) boots into recovery but can't mount sd card OR internal storage. Can't flash anything using Odin, always gets a Complete(Write) operation failed. Any suggestions ?

Looks like we're both in the same sinking boat.

Sorry for late reply
Deadbeef said:
Where does Odin show the device is a i9505? It's a n8010.
Click to expand...
Click to collapse
Sorry for late reply
Your Odin Screen Shot Say i9505 as your device

Deadbeef said:
Looks like we're both in the same sinking boat.
Click to expand...
Click to collapse
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.

georgesmh said:
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
Click to expand...
Click to collapse
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image

Agyar said:
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Click to expand...
Click to collapse
guys did any of you solve the problem??

georgesmh said:
guys did any of you solve the problem??
Click to expand...
Click to collapse
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.

Agyar said:
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Click to expand...
Click to collapse
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!

georgesmh said:
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
Click to expand...
Click to collapse
I've seen few other occurrences of this on different roms on various forums, so probably not Gnabo issue. also, nobody nowhere had a fix for it

I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?

dmarchant said:
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
Click to expand...
Click to collapse
I don't think it was flash failure, at least not in my case, since device worked without any issue for quite a while after last flashing... what was different now is that my battery was drained out for the first time i quite a while...

[Q] MTK rom, installation aborted

The Afterlife6.0 was said to be compatible with my Nitro 401D which has the aame MTK no.
However, whenever I try to flash it (using cwm) it says installation aborted. It doesnt say any status about it eg Status 6 or Status 7 but i still used the fix for one which is trying to change the name in the updater script to fit the name of my phone but when I looked, it doesnt have that particular line for checking the name. And the other one was changing the directory of the lines in it but I didnt want to change it because i wasnt so sure about the directories myself.
Ive tried downloading from another source, still didnt work. Now Im wondering maybe its my phone so Ive been considering using SP flash to force it in(? Im still not quite sure what it does tho) and also change my custom recovery (currently cwm) to twrp or ctr. Maybe my phone cant flash anything at all so ive been also considering trying to flash a small file or like a test rom, are there any of those?
What should I do next? Im scared of forcing it in causr it says that if the phone has the wrong preloader my phone can never be recovered..

rexel325 said:
The Afterlife6.0 was said to be compatible with my Nitro 401D which has the aame MTK no.
However, whenever I try to flash it (using cwm) it says installation aborted. It doesnt say any status about it eg Status 6 or Status 7 but i still used the fix for one which is trying to change the name in the updater script to fit the name of my phone but when I looked, it doesnt have that particular line for checking the name. And the other one was changing the directory of the lines in it but I didnt want to change it because i wasnt so sure about the directories myself.
Ive tried downloading from another source, still didnt work. Now Im wondering maybe its my phone so Ive been considering using SP flash to force it in(? Im still not quite sure what it does tho) and also change my custom recovery (currently cwm) to twrp or ctr. Maybe my phone cant flash anything at all so ive been also considering trying to flash a small file or like a test rom, are there any of those?
What should I do next? Im scared of forcing it in causr it says that if the phone has the wrong preloader my phone can never be recovered..
Click to expand...
Click to collapse
Your Device name and SOC?

MTKcROM said:
Your Device name and SOC?
Click to expand...
Click to collapse
My device name is Arc Mobile Nitro 401D but I dont know what SOC means (system on a chip if i guessed right) and or what it refers to but if it refers to the MtkXXXX then its mtk6572

rexel325 said:
My device name is Arc Mobile Nitro 401D but I dont know what SOC means (system on a chip if i guessed right) and or what it refers to but if it refers to the MtkXXXX then its mtk6572
Click to expand...
Click to collapse
Do you install CWM successfully? Did you try another custom rom?

MTKcROM said:
Do you install CWM successfully? Did you try another custom rom?
Click to expand...
Click to collapse
From everything I have done on trying to root this phone, I guess MTKdroid tools installed CWM in the process. It is rooted now tho, checked with rootchecker basic. I havent tried any other roms since Afterlife 6.0 is the only one i found.

UPDATE:
Apparently, the CWM wasn't properly installed, my bad :crying:
I tried to install another ROM like Lollifox (will try MIUI later, still downloading) but I don't think I ported it successfully tho because it just showed installation aborted, no Status whatsoever.
I have now flashed Afterlife6.0. However, its now stuck at boot but a while ago it was on boot loop but after wiping caches and doing a hard reset, its now on boot forever. By boot I mean it just shows the Sony logo (supposedly the Arc Mobile logo before I flashed the rom) then the logo disappears and then its just a black screen (a black screen as in its still turned on and not a black screen as you would see when a phone is off).
I'll try to flash my stock rom and root it again so that I could flash other roms for now while waiting for your reply.

try stock rom on the official site. than try to update cwm and try rooting again.

I already fixed it by flashing the stock tho so no worries I guess.
I successfully ported Lollifox but I encountered a problem where I couldn't save anything because my phone doesn't recognize my SD card. It can be seen in the settings/storage though but what the rom can't do is recognize that the "SD card" is internal not external. Its sort of hard to explain, I have 2 storages: Internal memory and Phone storage. The internal memory is the default place where apps go while the Phone storage acts like the SD card of this phone but its internal as well ( at least that's how it acts on the stock ROM). I tried unmounting it (apparently I have that option on Lollifox but its internal so I don't know how that's possible) and remounting it but no dice. Also, since it doesn't recognize the SD card, it kind of explains why there's no USB mass storage option when I connect it.
I tried to port the MIUI and did the 2 ways of porting it told in the site where the rom came from but whenever I flash it, it boots up and gets stuck at the logo of MIUI.
I'm leaning away from Afterlife 6.0 now cause I can't really see it would be a better ROM (and you got to give it that the themes of MIUI and Lollifox are pretty AF) but I think its more suitable (still can't flash it tho) . Can anyone give thoughts on the best rom for this or a fix for these problems?

rexel325 said:
sometimes you need to format the phone memory at the beginning for one time after you install new ROM. Try that and restart the phone. One time i did this like this problem. Sorry for my english.
Click to expand...
Click to collapse

Solved
I think I already solved my own problem though. I just had to do a few tweaks and do a little bit of trial and error myself. However, I still couldn't flash Afterlife (also tried porting it myself and Im suppose to do a logcat or something but I lack free time) but I still have a rom flashed don't worry. Kind of feel sorry it feels like a waste of a thread.
Now Im asking for this thread to be closed(or atleast I think thats how it works cause I dont seem to have that option myself)
Thank you