Related
Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared
Please Help!
- UPDATE: SOLVED!
Hi there, I'm having the same problem on my I9000B. Please help me.
This is my story, I had upgraded my 2.1 firmware to VIVO's 2.2 Froyo via KIES with the Kies Registry Patcher (used ZVV). Everything worked perfectly, but I wanted to root my I9000B so I made the terrible mistake of using CF-Root via Odin, (http://forum.xda-developers.com/showthread.php?t=788108) following the exact instructions. The kernel replacement (zImage file) was for the I9000 so I had the touchscreen problems. When the phone booted showed Samsung galaxy S GT-I9000B and then inmeadeatly the "B" dissapeared.
Because of my n000bness I tried to use the zImage file from this ROM (VIVO's) (http://forum.xda-developers.com/showthread.php?t=858483), by downloading my own .tar created file (with 7-zip) of the zImage file. Here is were things went down. I got the android - USB cable boot icon. I could not go into recovery mode but I could do download mode, so I re-flashed VIVO's ROM (the one published here) with Odin:
I used the 803 .pit file, Odin 1.3
I did not check re-partition
I selected the ROM as the PDA file and I left PHONE and CSC blank.
the ROM was downloaded to the phone and Odin did not gave me problems.
My problem here is that I get the black screen with vibrations from time to time on boot. This is exactly what happens:
The phone starts showing "Samsung galaxy S.... GT I9000B (at least shows "B")
I can get into recovery mode but the following appears:
Code:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please us UI menu for format and reboot actions.
copy default media content failed.
Then I did a factory reset, succesfully completed, tried again flashing the ROM but with Re-partition box checked (as instructed here: http://forum.xda-developers.com/showthread.php?t=723596) but the same stuff happens.
Please tell me what to do! I know it was a stupid mistake trying to fix ony the zImage file, and stupider was using CF-Root on my non-compatible device.
PS: I can get into download mode with no problems
Code:
pda i9000bvjjpa
phone i9000bvjjpa
csc i9000bzwjp3
I have exactly the same problem
but i can go into recovery mode and download mode.
the galaxy screen is I9000 and my sgs is I9000B
any ideas?
A friend of mine has the same issue on his SGS. Both recovery and download mode working.
Have you done JUST like this:
Figueiredo81 said:
Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared
Click to expand...
Click to collapse
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Thanks!!
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Margaliini said:
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Click to expand...
Click to collapse
Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.
Please, post the link or give me directions for the Claro's ROM. I am having the same problem here.
Thanks.
gtg2 said:
Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.
Click to expand...
Click to collapse
worked here
thanks
thanks for the help i love you no homo !
Un Loko said:
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Click to expand...
Click to collapse
JM2 with pit method is perfect. my "E: can't mount /dev/block/mmcblk0p1" problem has finally been solved.
Thanks
This worked for me.
http://samsunggalaxysforums.com/sho...CIAL-STOCK-FROYO-2.2.1-IS-OUT!!!!-(i9000XXJPU)
???I bought my Phone from CSpire but stuck on At&t Logo???
Samsung Galaxy s Showcase stuck on the At&t Logo...Will not let me go into Download mode??? Help please?
So i tried to updated to a custom firmware after i JUST received my galaxy S back.
And it got bricked.
It failed during the initial flash with Odin, no big worry i thought as i'll just reflash it. It constantly failed until I changed the USB slot. Now after I've even completed the flash the phone boots up shows the "GT-i9000/m" logo then shows those 9 bars that show its trying to load the battery charger. Then the screen goes black and it tries that over and over again.
Anybody had this problem? I think it's a soft brick and can be resolved before sending it back in and losing the phone for another month.
is download mode working then ? does odin recognise the phone ??
if so download a stock firmware with all 3 files and pit. and use re-partition. and see how that goes.
actually if it is a software problem there are lots of possible procedure to fix that just reflash it with an official firmware using odin
I've tried the following:
use odin 512pit and a tar file and using odin with a 803pit and a tar file.
Both resulted in the same thing.
Is there a specific FW i should try?
edit:
With and without repartitioning.
try JM8 with PIT and pda.modem,csc. and re partition again.
I know wher eto get JM8, but how/where do I get the PDA.modem and csc?
hmm yea i know what u mean, most modern firmwares only come in 1 file now. download that. but im not sure what pit to use. il have a look now.
i think its 512 pit
here try this
Tried everything. I think it might be a hardware error.
Last ditch effort of Jm8 in odin 1.0 now... will let you know if it works.
Edit:Nothing worked.
Gonna go return the phone/send it back to samsung.
Double EDIT:
Flashed the phone back with JL2 that i got from Samsung and checked EVERYTHING in ODIN. Phone went past the boot logo repetition and into the "S" but doesn't do anything more. Just gets stuck after that. (corrupted internal SD)
so if the JL2 didnt succeed what would be on it at present ? if its a custom rom just go back to odin do a flash and disconnect half way through and totally brick the phone..
then blame it on a kies update when you return it. you dont want them to find out you have modified it in any way not recommended by samsung. or they may not replace and may charge you.
Purchased two Bell Canada Samsung Galaxy S as-is from local kijiji.
They all performing the same thing, rebooting at Galaxy S logo, GT-I9000M page, it won't go any further. and there is no recovery mode at start-up.
Here are the steps which I have played with for past two days.
1. Trying to get to recovery mode
- tried ADB, but it doesn't work, since "USB debug" is not on, and it won't accept as a device, and I am not able to turn that on, since I can't even get on the main screen.
- tried three key combo, vol up + home + power on, at least a hundred times for past two days, it doesn't work. fortunately download mode is working (at least I have more option to try). and I know how to get to recovery mode, I played with my friend's before.
2. Trying to use ODIN to flash the firmware
- unchecked "re-partition", unchecked "bootloader", pick 512 as PIT and then choose following as PDA
JH2, JK3, JK4, JL2
always successful on refresh, but phone still does the same, stuck at LOGO page
- also tried, checked "re-partition", and checked "bootloader", pick 512 as PIT and repacking following into PDA, Phone/Modem, CSC, still won't work...
JP series, JH, JK series, JL
At the beginning I though it was problem on CSC, I didn't use correct one to match my phone model #, but what's mine??? I can't go into my phone to check. I checked my friend's I9000, he used I9000BMCJK4, and I assume all JK series should work with me, since our IMEI are similar. And I tried many times on different cache.rft as CSC.tar, still no luck for me
I go crazy now, $400 USD gone. Seriously needing help. Any help is highly appreciated.
try the one jl2 download file and samsungfirmwares.com it flashes a special bootloader that may fix things.. it should be a single file you put in as pda nothing else..
if not they may have permantely trashed internal memory and you are sol.
lgkahn said:
try the one jl2 download file and samsungfirmwares.com it flashes a special bootloader that may fix things.. it should be a single file you put in as pda nothing else..
if not they may have permantely trashed internal memory and you are sol.
Click to expand...
Click to collapse
I have tried one of JL2 file from somewhere (don't remember where), but I will get one JL2 file from samsungfirmwares.com again, see if that works.
Do you mean, only choose the file for PDA, left PIT empty, and get everything uncheck?
permantely trashed internal memory? are these the common problem with this model? I got two of these, and both of them have the same issue, I think, there should be a way to slove it, right? Should I give up these thoughts???
anyways, thanks anyways, I will report back after I flesh JL2 from samsungfirmwares.com
Ok, you need to flash jl2 with pda, repartition, pit file and the secondary boot loader... The SBL(secondary boot loader) is what will actually fix your phone
Hopefully it will work.
Sent from my GT-I9000m using XDA App
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.rfs
<ID:0/005> Sbl.bin
<ID:0/005> zImage
<ID:0/005> factoryfs.rfs
<ID:0/005> modem.bin
<ID:0/005> param.lfs
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Still no luck on this firmware, I9000UGJL2, by the way, should be samfirmware.com instead of samsungfirmwares.com
above message I got from ODIN3 v1.30, it looks fine for refresh, but it doesn't work. the phone keep rebooting, it won't pass LOGO page, again, only download mode I can use.
HELP! HELP! HELP!
any leads???
is "<ID:0/005> Sbl.bin" secondary boot loader???
I got the file for PDA, I9000UGJL2, is this the one? if not, where should I get it? how do I update it?
I did it again, with "re-partition" checked, PIT choosed as s1_odin_20100512.pit, I9000UGJL2_homebinary_add_param.tar (which I just downloaded from samfirmware.com), it still doesn't work.
anything else I can try? maybe something simple I didn't do???
I too am a bell user I had the same problem a few weeks back. This is going to sound messed up, but i'm going to do my best to explain how I solved the problem.
DO NOT MULTI-TASK ON THE COMPUTER WHILE DOING THIS. CLOSE ALL OTHER APPLICATIONS.
-remove external sd and sim card
-go into download mode (hold vol down+power+home).
-turn on ODIN
-plug in usb (both computer and phone)
-check re-partition
-ONLY use the 512 pit file. DO NOT use a rom.
-start ODIN and it should only take a minute. this will wipe your device completely but still allow you to access download mode.
- remove usb close ODIN
- start up ODIN again and connect usb
- use 512 pit and JP1 or JP2 rom.
- After flashing, this SHOULD give you an error and send you straight into recovery mode. you're looking for a specific error code. you need the error to have "sl01" or "sl10" (whichever, i forgot which it was) at the end of the path. if the end of the path has "m(something)" then use a different rom till you get the "sl10".
these errors are internal sd errors which your phone is experiencing right now, but the phone is fixable from the "sl10" error.
continuing...
- once you get the "sl10" error, close ODIN, unplug USB, turn off phone.
- go back into download mode.
- boot up ODIN with 512 pit and ULG2 rom.
- plug in phone
- start flashing.
this can give you two outcomes:
1) fixed galaxy S
2) error code with "m(something)" at the end of the error path.
if it's #2 do this all over again until it works.
This took me 3 days to figure out these steps, 10 hours each day. although it doesnt seem to make sense, my phone is working right now and it is where I am writing all this from. My only explanation is that Bell gets ****ty product from samsung. it's almost impossible to flash custom roms on a bell galaxy i9000 because the internal SD seems to have trouble being mounted.
i hope this helps and i hope it doesnt take long for you to fix this problem.
btw, if it does get fixed data connection wont be available. to enable it go to your apn settings. create new named "Bell" with apn as "pda.bell.ca" and leave all other options blank. data should be restored after that.
Sent from my GT-I9000M using XDA Premium App
jt_kyle said:
I too am a bell user I had the same problem a few weeks back. This is going to sound messed up, but i'm going to do my best to explain how I solved the problem.
DO NOT MULTI-TASK ON THE COMPUTER WHILE DOING THIS. CLOSE ALL OTHER APPLICATIONS.
-remove external sd and sim card
-go into download mode (hold vol down+power+home).
-turn on ODIN
-plug in usb (both computer and phone)
-check re-partition
-ONLY use the 512 pit file. DO NOT use a rom.
-start ODIN and it should only take a minute. this will wipe your device completely but still allow you to access download mode.
- remove usb close ODIN
- start up ODIN again and connect usb
- use 512 pit and JP1 or JP2 rom.
- After flashing, this SHOULD give you an error and send you straight into recovery mode. you're looking for a specific error code. you need the error to have "sl01" or "sl10" (whichever, i forgot which it was) at the end of the path. if the end of the path has "m(something)" then use a different rom till you get the "sl10".
these errors are internal sd errors which your phone is experiencing right now, but the phone is fixable from the "sl10" error.
continuing...
- once you get the "sl10" error, close ODIN, unplug USB, turn off phone.
- go back into download mode.
- boot up ODIN with 512 pit and ULG2 rom.
- plug in phone
- start flashing.
this can give you two outcomes:
1) fixed galaxy S
2) error code with "m(something)" at the end of the error path.
if it's #2 do this all over again until it works.
This took me 3 days to figure out these steps, 10 hours each day. although it doesnt seem to make sense, my phone is working right now and it is where I am writing all this from. My only explanation is that Bell gets ****ty product from samsung. it's almost impossible to flash custom roms on a bell galaxy i9000 because the internal SD seems to have trouble being mounted.
i hope this helps and i hope it doesnt take long for you to fix this problem.
btw, if it does get fixed data connection wont be available. to enable it go to your apn settings. create new named "Bell" with apn as "pda.bell.ca" and leave all other options blank. data should be restored after that.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
great!!! Another option I can try. Thank you.
I will try it out right after my work. so the idea behind this, is bricking it into recovery mode and S10 error code. and then fresh right back with correct ULG2 (is this correct? frist time heard about this rom)
anyways, I will post back with result.
Where can i find this ULG2 rom?
did it work?
Thananjeyen said:
Where can i find this ULG2 rom?
Click to expand...
Click to collapse
I think jt_kyle meant I9000UGJL2
and you can get them from samfirmware.com
Paallikko said:
did it work?
Click to expand...
Click to collapse
yes, lucky I got one of my Bell Samsung phone work. Since I done a million times of refreshing and rebooting and etc... I am not sure what I did, now I still trying to remember last 10 steps I did to make this work.
But definitely, I could not have done this repair without jt_kyle. Thank you so much, jt_kyle.
jt_kyle, Thank you!!!
but none of JP1 or JP2 is givining me the error "tl10", I tried
I9000DXJP1
I9000TGYZSJP2
I9000XXJP1
I9000XXJP2
it come out error started with "m..."
I just keep refreshing each on PDA 3 to 4 times, and choose with re-partition or without. At the end I try a few another ROMs as well, I still get no "tl10", but somehow, just that magicical moment, the screen come out a set of commands that look like format sd card, so I got excited, fresh it with JL2. It is back to work.
still no clue the steps of fixing the problem.
one done, the another one to go.
any more ideas please, and I think I am really close to solve this one now.
Thank you All
FIX
Look for a file called I9000UGJL2Complete follow the same steps pit and so on after your phone boots up youll have a blank baseband then you get the I9000UGJL2 modem and flash it where it says phone this has unbricked a few for me hope this helps
EVERED78 said:
Look for a file called I9000UGJL2Complete follow the same steps pit and so on after your phone boots up youll have a blank baseband then you get the I9000UGJL2 modem and flash it where it says phone this has unbricked a few for me hope this helps
Click to expand...
Click to collapse
if you have a way for me to give you this file i do have it just not sure how to do so because its 286MB
Could it be dead?
Since you have one of the infamous i9000m's it might also just be a dead SD card? You might try calling samsung and trying to get it repaired under warrenty as they are all under a year old (try and flash jl2 first even it will not boot up). It sounds like no receipt may not be an issue.
Lots of info from allgamer's list of i9000m issues in the general section.
At least you have one in the meantime!
same problem
Hey ive got pretty much the same problem that you had. Only differences are that I'm from Australia and am on Virgin network.
My phone became semi bricked one day when it restarted and since the 3 button combinations did not work i ordered in a USB jig which i received today. I used odin 1.8 to try and flash to I9000BVJJPD which i got from samfirmware.com but it ended up stuck on the logo screen vibrating once in a while. I decided to repeat it with no avail and began to use other roms and use .PIT.
This is where my phone became even worse and is now in it's current position; rebooting at the GT-I9000 page. I tried the method that jt_kyle suggested, substituting australian roms instead but it is still in the same position.
Does anyone have any other suggestions or should i just try getting a warranty?
Look for the ugjl2 complette and repeat what I said
Sent from my GT-I9000 using XDA Premium App
EVERED78 said:
if you have a way for me to give you this file i do have it just not sure how to do so because its 286MB
Click to expand...
Click to collapse
I think I have this I9000M_JL2_JL2_JL2_JL2_UG_BMC file, is the same file that you are talking about? JL2 Complete?
I tried this file many times, it won't work neither.
for past one hour I played around this phone, trying to repeat the steps I did for the first phone. Unfortunately, nothing is working for me AGAIN!
but I got these error page all the time, like following...
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(I/O error)
E:copy_dbdata_media:Can't mount SDCARD:
I think that's bigest problem in my case, and for a lot of people in this forum. Do any people has a good solution for this???
New member and somewhat stupid for trying to do this:
Long story short I attempted to throw gingerbread 2.3.X on the phone and now its stuck in either download mode, recovery mode, or if i just turn it on it comes up and says "GALAXY S GT-I9000 Samsung" The last thing that was successful was putting the SpeedMod Kernel on it.
In recovery mode it says "ClockworkMod Recovery v2.5.1.0 SpeedMod ULFK" on top and bottom.
The phone started out with factory settings.
When i try and use the ODIN 3 and try to do the Mast Clear it says :
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> Master Clear Started.....
and then stays like that indefinately...
Same thing with hitting "start"
Please let me know how to fix this, I know there are some really brilliant individuals on this forum and it would be greatly appreciated.
search for odin, download it, follow the steps and flash back to stock. you'll be fine especially since you can get into download mode.
edit: gah you already have odin. do you have one click or the one where u have to put the pit and tar files?
the same advice applies though, find the stock files, and go into download mode, then plug it in and flash back to stock.
i think master clear only works when the phone is on and you have usb debugging enabled.
Ive got ODIN 1.7 and ODIN3. I can get them to both recognize the phone but when I try and hit "start" with v1.7 it ust sits there forever. and Im not able to get ODIN3 to do anything either.
Any way you could provide a more step by step solution?
If you're having problems with ODIN, something that seemed to work for me was to remove my SIM card.
Try removing it and see if you have any luck.
I dont have anything in the phone, no sim and no external.
Just left it alone for a bit and came back and turned the comp back on and everything worked for ODIN. Thanks for the help fellas
Hello, guys.
I was trying to install a new rom to my Galaxy Note. and when wiping out the user data (to get the phone ready to install the new rom) he phone reboot and got stuck on the start up logo. Waited for a long time but it didn't do any thing. So a remove the baterry and turned it back on. But but it did the same.
I then decided to flash it using Odin but it got stuck almost at the end of the proccess. Now my battery is almost dead and the only thing on the screen is a flashing message. Firmware upgrade encounter an issue.
HELP!!! THIS IS MY NEW PHONE!!!!
estebandilone said:
Hello, guys.
I was trying to install a new rom to my Galaxy Note. and when wiping out the user data (to get the phone ready to install the new rom) he phone reboot and got stuck on the start up logo. Waited for a long time but it didn't do any thing. So a remove the baterry and turned it back on. But but it did the same.
I then decided to flash it using Odin but it got stuck almost at the end of the proccess. Now my battery is almost dead and the only thing on the screen is a flashing message. Firmware upgrade encounter an issue.
HELP!!! THIS IS MY NEW PHONE!!!!
Click to expand...
Click to collapse
Which rom you were on before trying to flash? And what did you try to install?
Sent from my GT-N7000 using xda premium
I was on Android 4.0.3 the German realesed.
N7000XXLPY---------4.0.3---------2012 May
I downloaded it from the forum and it was working nicely. I just wanted to try a different rom. But I didn't get to do nothing just to clear the data which never ended and crash my phone..
Stuck after wiping user data, Odin hanging at the end..where exactly did it stop working?
I'd say that it's definitely superbricked.
you can do that:
- go on recovery (Try vol up + home + power)
- mount usb storage and put abyss kernel in a directory
- flash abysskernell4.00
- reboot recovery
- wipe data cache and dalvik
- power off
- power on
if it's stay on boot logo :
- power off
- vol down + home + power (download mode)
- flash your note with odin pc with this method
- dl mobil odin and flash ics open germany with this method
Noizy.
I will try that, but now i have to charged my battery to be able to do it.
When trying to flash the green bar on Odin gets almost to the end ot the proccess but then it just sits there and doesn't do anything...
estebandilone said:
I will try that, but now i have to charged my battery to be able to do it.
When trying to flash the green bar on Odin gets almost to the end ot the proccess but then it just sits there and doesn't do anything...
Click to expand...
Click to collapse
Could you paste the Odin log perhaps? That would help the people around here give you a solution, if any.
Right now I am downloading the files from the commment above... I will try that and post whatever it happened!!! My internet conection is just a Mega so it takes me a while to download all the files to try it... But I am almost done!!
This is what I have on Odin. It almost get to the end of the green bar.
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> factoryfs.img
<ID:0/012> NAND Write Start!!
This is the message Showing..
Is your LPY Rom rooted? If yes, then how?
Did you flash CF-Root LPY kernel, or did you root it using Dr.Ketan's method?
This is a screen shot of the screen.
Yes it's rooted and I used Dr.Ketan's method..
I'm afraid you have a brick on your hands, mate. Take your Note to the
nearest service centre for MoBo replacement.
That I can't do. I bought from a third person... So I don't have any warranty... Let me ask you a question. The fact that I can get into recovery mode doesn't make a difference?
estebandilone said:
This is a screen shot of the screen.
Click to expand...
Click to collapse
Duno if this method will work for u but it works for me n my friend...
1stly i pressume u are able to boot into download mode...
2ndly, d/l a rooted GB Rom...
3rdly, restart pc/lappy
4thly, change another USB port (changed port works for me n my friend)
5thly, fire up PC Odin... put Note into download mode n connect...
Lastly select the rooted GB rom under "PDA"..
keep finger cross
Noted From My G.NOTE Using XDA Premium
I am trying again.
Not working... Don't know what to do
It's superbricked, for sure. All you can do is send it for repairs - motherboard replacement.
[Solve on [email protected]] Similar Case for reference
estebandilone said:
Not working... Don't know what to do
Click to expand...
Click to collapse
Hey dude, I had a similar case when I was upgrading my S2 officially because my USB was loose, I got the update 60% and came to a halt, my phone wasn't even rooted by then.
Here's what I did and here's what you can try:
1. root my phone (for your case, re-root your phone or even unroot then re-root it again, there may be some files damaged when your phone lost power).
2. install original kernel and Stock ROM (there might be original files which are needed from the original to make things work when you switch ROMs)
3. reboot and see if things are fine.
If you get back to running normal, then you can install whatever Custom ROMs you like.
Hope this help! Get back to me with the latest situation.