Related
So here's the deal.
it's a long story, but i happened in a short time.
I was unlocking my bootloader and stuff on my nexus one on my mac. using the boot loader.
I used the superboot to unlock it.
and so i succeed in that.
i didn't bother with the install-superboot-mac.sh thing.
i didn't know that by then.
so i went on to search about the cyanogenmod 7, and i can't get the radio refreshed. i read the article in the cm forum.
so, i saw this post somewhere,(...read hundreds of posts now)
that tells me to use the rom manager thing.
so i downloaded it, and i tells me that my phone is not rooted!
so i was wondering how this happened.
i searched online, and i found this post telling me to use that install.bat(which is for windows, mac is the one i mentioned above) thing after i unlock the bootloader.
i was a bit scared.
but i went on to the fast boot manu and i connect my computer,
i put the directory in, and then i threw the install-superboot-mac.sh thing in my phone, successful, so i rebooted my phone.
And after the first not-ANIMATED start up screen, which is the staying-X and the unlocked symbol at the bottom, the screen goes black.
i was not sure what happened. so i pullout the battery and booted it again.
same thing.
it was not until the third time i opened it and waited for it, i realized that it was my screen that's not working!
After the stable X, the system goes to the animated one, but my screen is blacked out, so i can't see.
The bottoms on the phone are still working , yet i can't see a thing!
I can still open the fastboot/bootloader screen, but after that, nothing!
the recovery don't work, it's just an android with the sign.
I'm very worried about this situation.
please reply to me!!
i really need help, since i know nothing about this.
I just thought that 2.3's cool and now i got this....
here's some info that might help,
i have the korean version of the phone, it was cheaper and stuff.
didn't notice a different except that there's no 3g?
i don't really know what's the deal with it.
but it seems to be special or something.
The phone is unlocked, but my computer fails to find it using the adb devices.
im not sure if my phone is usb debbuging.
probably yes.
Everytime i try to load the recovery, it tells me to wait for device.
I really need help!!
OK... so you might have messed up your firmware... no worries... get a custom recovery (like AmonRA recovery)... flash it using fastboot... pop in a custom ROM like CM... flash and reboot...
the thing is i can't load the recovery or the mods. so here's the problem
Do as Craig said.
Put phone into the bootloader screen. White screen with skateboarding androids.
Do your thing with fastboot.
Reboot directly into the freshly flashed recovery and install a ROM.
Read the wiki.
Sent from my Nexus One using XDA App
Read my signature, find a proper guide in Wiki ("Unroot / restore"), execute.
Next time, before you're trying anything, either find a good guide on the internet or try understanding what things actually do before you attempt them.
I've read the wiki, but is my phone compatible with the rom?
my phone's korean version..
im not sure if i can.
and i certainly can't afford another adversity.
reclusivenigma said:
I've read the wiki, but is my phone compatible with the rom?
my phone's korean version..
im not sure if i can.
and i certainly can't afford another adversity.
Click to expand...
Click to collapse
It will work just fine, your phone isn't bricked and will be working fine in no time if you follow the advice in the posts above.
Edit: Am I the only one who wants the word 'Bricked' explicitly defined for the xda forums?
and also, since my screen is out, im not sure of weather my back up data thing is on or not, and usb debugging also
i've tried the ROMs, but the three i tried don't work.
downloading more, but i doubt if there's difference.
the device doesn't tell me to install the update, instead it just goes back to the bootloader screen
i've tried the ROMs, but the three i tried don't work.
downloading more, but i doubt if there's difference.
the device doesn't tell me to install the update, instead it just goes back to the bootloader
...
K, they don't really work, after checking the rom, my phone just goes back to the screen that showed up when i pressed power and volumn down
Why do people insist on receiving their instructions on a golden spoon?
Do you think you're the first one ever that got his phone corrupted? Maybe the second?
Go to Wiki, download FRG33, proceed with instructions for PASSIMG method. PUT ATTENTION THAT YOU'RE NAMING THE FILE RIGHT!
These instructions have been given in 800000000 threads by now. Look for the thread about moving from Vodafone OS version to stock Google OS. Search the forum with the words "restore stock".
What exactly are you doing?
You have a few pieces of advice that will work, but you're not really giving any details about what you are actually trying...?
Here's the link to follow Jack's advice:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my NookColor using Tapatalk
just if you want to know,
i've downloaded the frg33
and i HAVE NAMED it CORRECTLY!
YET, IT doesn'T WORK
im not a retard!
after the 2 min period of searching, which is step 7, my phone goes back to the same screen
CID incorrect!
Update Fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
this shows up a couple of times also
Why ask for help if you're not going to do what people tell you?
With a unlocked bootloadet flash a custom recovery.
Reboot DIRECTLY into that.
Wipe and flash any rom you want.
If you don't know how to do any of the above search or read the wiki.
Sent from my Nexus One using XDA App
As albundy2010 suggested - if you have the bootloader unlocked (I didn't notice that part in the OP), just follow the guide for unlocked bootloader - fastboot flash all the partitions on the device manually. The guide is in the same place, but a different one - this time use "for unlocked bootloader".
tHANKS man!
I was such a f-in idiot...
now i can finally boot into the recovery..
I got it.. thanks guys
It's a tough flashing world out there, hey rec
I am glad you got it working
i was installing the ics repack zclp1 with pc odin but it stuck on data.img
what should i do?
can i remove the cable?
please help ...
you can restart but dont reboot phone any you turn it once the bootloader is flashed you will be safe you can also check the link in my sig
antiguangenius said:
you can restart but dont reboot phone any you turn it once the bootloader is flashed you will be safe you can also check the link in my sig
Click to expand...
Click to collapse
Please stop offering your 'bootloader' advice to guys having problems after flashing Angelom's ICS kernel.
Bootloader is not going to help because their problem is corrupted data partition. Nothing to do with the bootloader whatsoever.
Ok
chasmodo said:
Please stop offering your 'bootloader' advice to guys having problems after flashing Angelom's ICS kernel.
Bootloader is not going to help because their problem is corrupted data partition. Nothing to do with the bootloader whatsoever.
Click to expand...
Click to collapse
ummm read properly before you respond
I SAID HE CAN RESTART THE FLASH BECAUSE THE BOOTLOADER IS FLASHED FIRST SO HE IS SAFE.
i never told him to flash his bootloader obvoiusly he is try to root or install ics so a smart guy will click on the rooted or rom link for help....
PS
look before you leap.....
Let me guess re-partition was on in odin?
If yes u need to call samsung.
avetny said:
Let me guess re-partition was on in odin?
If yes u need to call samsung.
Click to expand...
Click to collapse
you dont need to call samsung.... i have use the repartition few times..... sounds like he has a bad flash chip....
antiguangenius said:
you dont need to call samsung.... i have use the repartition few times..... sounds like he has a bad flash chip....
Click to expand...
Click to collapse
so whats the solution mate? we have tried everything. pit, odin, cwm, kernel flash, it gets stuck either at boot n700 logo or at factoryfs or data.im on odin
antiguangenius said:
ummm read properly before you respond
I SAID HE CAN RESTART THE FLASH BECAUSE THE BOOTLOADER IS FLASHED FIRST SO HE IS SAFE.
i never told him to flash his bootloader obvoiusly he is try to root or install ics so a smart guy will click on the rooted or rom link for help....
PS
look before you leap.....
Click to expand...
Click to collapse
No, you read properly before you respond, and even more properly before dishing out any more useless advice to people with a very specific problem, i.e. bricked phones after flashing Angelom ICS kernel v1.2.
Read this, for instance:
http://forum.xda-developers.com/showpost.php?p=23256341&postcount=405
and this:
http://forum.xda-developers.com/showpost.php?p=23256829&postcount=406
I'll say no more about it.
androidindian said:
so whats the solution mate? we have tried everything. pit, odin, cwm, kernel flash, it gets stuck either at boot n700 logo or at factoryfs or data.im on odin
Click to expand...
Click to collapse
ok ok ok i have took sometime and read almost every one issue.. the problem is indeed global.... due to the 1.2 recovery, angelom rom or what ever.....
I have put some thought into in.... i could be wrong or sound like an idiot to say this but it seem like the boot block for the main flash chip it been corrupted with the wrong header....
for eg. most note is 16gb, lets say with a A14BC ok check sum.... the rom seem to be interfering with that checksum or flash header... so when the odin which has only a specific command to modify that flash chip look for the checksum to proceed.. its not getting it so it waits and waits and waits... which is what its officially programmed to do.. i'm guessing that these it a specific switch odin needs to start with to over ride its normal procedure and reset flash to its original state or there's a higher level program to do this.... these flash chips was programmed in the phone not out so there has to be a way to revive them... its electronics...... it remind me of the boot legged usb flash cards, you will buy one at 32gb months later it wont work properly or at all.
but nevertheless most people getting the N7000 bootlogo and nothing after its just like a pc with a bad harddrive the phone is looking for the Unified Extensible Firmware Interface (UEFI) which is a specification that defines a software interface between an operating system and platform firmware.. its not that because odin can't load it... odin cant load if for many reason which can be the flash chip has been corrupted so the full size cant be read or the checksum mismatched... only fix i believe it there is if odin has a special switch which ignore checksums or it had a grandfather program we don't have access to....
bottom line is the flash chip aka hard drive from the note is not formatted and/or partitioned so its not accepting the firmware aka the os.......
we need the chinese that made these thing to say whats missing.... or a samsung tech so leak something...
PS maybe if someone force a SGS2 rom on it since they're close devices, that might set the flash back in order then try the note rom.... preferably someone with a busted device that wanna take the leap.... will be interested to see where the SGS2 rom flash stops.... crazy idea but who know might work after all the device is already not working...
antiguangenius said:
ok ok ok i have took sometime and read almost every one issue.. the problem is indeed global.... due to the 1.2 recovery, angelom rom or what ever.....
PS maybe if someone force a SGS2 rom on it since they're close devices, that might set the flash back in order then try the note rom.... preferably someone with a busted device that wanna take the leap.... will be interested to see where the SGS2 rom flash stops.... crazy idea but who know might work after all the device is already not working...
Click to expand...
Click to collapse
Those are some really interesting thoughts.
And this chap here http://forum.xda-developers.com/showpost.php?p=23305688&postcount=1
Did something similar and succeeded, though the root cause was different it seems to be matching with your analysis!!
antiguangenius said:
ok ok ok i have took sometime and read almost every one issue.. the problem is indeed global.... due to the 1.2 recovery, angelom rom or what ever.....
I have put some thought into in.... i could be wrong or sound like an idiot to say this but it seem like the boot block for the main flash chip it been corrupted with the wrong header....
for eg. most note is 16gb, lets say with a A14BC ok check sum.... the rom seem to be interfering with that checksum or flash header... so when the odin which has only a specific command to modify that flash chip look for the checksum to proceed.. its not getting it so it waits and waits and waits... which is what its officially programmed to do.. i'm guessing that these it a specific switch odin needs to start with to over ride its normal procedure and reset flash to its original state or there's a higher level program to do this.... these flash chips was programmed in the phone not out so there has to be a way to revive them... its electronics...... it remind me of the boot legged usb flash cards, you will buy one at 32gb months later it wont work properly or at all.
but nevertheless most people getting the N7000 bootlogo and nothing after its just like a pc with a bad harddrive the phone is looking for the Unified Extensible Firmware Interface (UEFI) which is a specification that defines a software interface between an operating system and platform firmware.. its not that because odin can't load it... odin cant load if for many reason which can be the flash chip has been corrupted so the full size cant be read or the checksum mismatched... only fix i believe it there is if odin has a special switch which ignore checksums or it had a grandfather program we don't have access to....
bottom line is the flash chip aka hard drive from the note is not formatted and/or partitioned so its not accepting the firmware aka the os.......
we need the chinese that made these thing to say whats missing.... or a samsung tech so leak something...
PS maybe if someone force a SGS2 rom on it since they're close devices, that might set the flash back in order then try the note rom.... preferably someone with a busted device that wanna take the leap.... will be interested to see where the SGS2 rom flash stops.... crazy idea but who know might work after all the device is already not working...
Click to expand...
Click to collapse
makes a lot of sense.
so do you think its an issue in the chinese i9220 kernel itself? or was it an issue created with angeloms kernel of i9220?
androidindian said:
makes a lot of sense.
so do you think its an issue in the chinese i9220 kernel itself? or was it an issue created with angeloms kernel of i9220?
Click to expand...
Click to collapse
I'm actually running chriskelo rom, i did flash the chinese ics first then the chriskelo... my phone works fine.. before the chriskelo i did flash team ics but was getting massive FC so i tried to flash back the GB but it would just stuck at modem which naturally comes after bootloader.... so what i did was download a GB Modem for recovery then flash it then reflash rocket rom v22 all in recovery and my phone was back up and running in a matter of 20 mins
as response to the i9220 and N7000 differences there must be some internal differences which only samsung knows cant just be language and region thats controlled by the csc...
CSC = Country Sale Code
CSC code depends on the region where the phone was sold.
CSC contains the phone settings (internet, wap, mms...), specific applications which available in certain regions, and operator customizations.
CSC code could be changed by flashing a new firmware (including CSC file) on phone. That will change phone language and settings.
Use *#272*IMEI# code on phone to view the list of the available CSCs, or change CSC.
china have many different mobile rules that the rest of the world so its more than just the firmware.....
I just made a thought.... can someone try to download a firmware that has all the pieces some can be found in my guide in my sig and flash the phone in the reverse order... that is flash only the CSC file then the phone file then the PDA then lastly the bootloader.... can someone please try them individually... and report back...
antiguangenius said:
I'm actually running chriskelo rom, i did flash the chinese ics first then the chriskelo... my phone works fine.. before the chriskelo i did flash team ics but was getting massive FC so i tried to flash back the GB but it would just stuck at modem which naturally comes after bootloader.... so what i did was download a GB Modem for recovery then flash it then reflash rocket rom v22 all in recovery and my phone was back up and running in a matter of 20 mins
as response to the i9220 and N7000 differences there must be some internal differences which only samsung knows cant just be language and region thats controlled by the csc...
CSC = Country Sale Code
CSC code depends on the region where the phone was sold.
CSC contains the phone settings (internet, wap, mms...), specific applications which available in certain regions, and operator customizations.
CSC code could be changed by flashing a new firmware (including CSC file) on phone. That will change phone language and settings.
Use *#272*IMEI# code on phone to view the list of the available CSCs, or change CSC.
china have many different mobile rules that the rest of the world so its more than just the firmware.....
I just made a thought.... can someone try to download a firmware that has all the pieces some can be found in my guide in my sig and flash the phone in the reverse order... that is flash only the CSC file then the phone file then the PDA then lastly the bootloader.... can someone please try them individually... and report back...
Click to expand...
Click to collapse
yes, before sending my phone to samsung yesterday, I did try that with KL8 firmware. starting from the kernel, bootloader, csc, ums, and at the end code/pda, but again stuck at factoryfs.img
http://forum.xda-developers.com/showthread.php?t=1532830 >> just saw this thread, makes me wonder.. if the chinese leak has something to do with this.
but when i was on cf repack, i could easily flash another kernel like angelom or another rom, only after angelom issues started.
were you able to flash via odin a stock rom being on cf kernel ics?
androidindian said:
yes, before sending my phone to samsung yesterday, I did try that with KL8 firmware. starting from the kernel, bootloader, csc, ums, and at the end code/pda, but again stuck at factoryfs.img
http://forum.xda-developers.com/showthread.php?t=1532830 >> just saw this thread, makes me wonder.. if the chinese leak has something to do with this.
but when i was on cf repack, i could easily flash another kernel like angelom or another rom, only after angelom issues started.
were you able to flash via odin a stock rom being on cf kernel ics?
Click to expand...
Click to collapse
I didnt still on ICS but I did went back to GB once no issue,,, but all this ICS issues is hurting my head.... I'm going back to GB NOW... I'll report in a few mins....
So I got myself into really funny situation I'm stuck.
I worked with xperia mini pro everything was fine.
Now I got x8 well older one... And all i did was rooted it with flashtool.
Everything was working fine from that point with root rights like root uninstaller (I just tested didn't deleted anything).
And then I made "factory reset" Deletes everything from sd card and bla bla bla well you guys know what i mean.
After that I wanted to install kernel but it's not that easy. So I first read alot and did not do that. Since it would require bootloader unlock and thats pain with 11W29.
So just after factory rest somehow I bricked my phone...
But it's interesting brick... VERY INTERESTING.
It turns on, it has flash mode. I can update it via update setup and tried to do that.
Nothing helps all I get is :
phone loading normally, then there is no menu, not sony ericsson home, not go launcher, no settings available no nothing...
To explain my problem i will upload screenshot.
And I can't flash it now since it's not bootloader unlocked.
And I can't access anything from phone.
This is what you call hard brick?
Hard brick is when You can't turn on phone, so there isn't any way to install ROM again. In Your case it's strange soft brick, cause it looks like ther isn't any launcher If You can enter into flash mode than You should reinstall stock ROM and kernel using flashtool (with version 0.2.9.1 cause it's more stable with older devices, such as x8).
Its not bricked. / You can use android commander to push recovery.
It's stock already and I tried stock launcher via updatesetup of SE,
And I think i need bootloader unlock to flash it ? or I'm wrong.
And Later on i will try with older version of flashtools
thx for answers guys.
No, unlocked bootloader allows You to install custom kernels, but some ROMs works also with stock SE kernel, so You don't have to unlock bootloader to install custom ROM or back to stock ROM
So i'm back again on same problem....
I have a Question if you wanna flash phone from flashmode u don't have to have unknown sources and debugging turned on.
Since i can't do that...
My following actions :
I will try to install fresh win7 32bit, since now i'm on 64 and on this system i was working with mini pro xperia, so maybe that may be the case...
I'll try to flash it with older version of flashtools 0.2.9.1 I guess if i remember it right (but on this windows OS It gives me : Error Flashing. aborted)
And I installed flashtools drivers and everything i'm 100% sure of that.
What I tried :
I also tried flashing it from Linux / ubuntu . same as with windows i get :
Error flashing. Aborted.
PCC gives me error when i try to repair it.
Update Service Dose everything as normal but same problem remains I don't get launcher or something just that empty desktop
And I would love you guys if you would give me few links to stock firmware of
x8 11W29 / E15i
And if you have something else to suggest please help me ;D
Hello, sorry for necroing thread but i have exactly same problem like OP, and as he didnt post solution i would like to ask how to do it.
Thanks for your time!
X8 OFW
deamerz said:
Hello, sorry for necroing thread but i have exactly same problem like OP, and as he didnt post solution i would like to ask how to do it.
Thanks for your time!
Click to expand...
Click to collapse
Try Flashing This via FlashTool.
TheScriptKitty said:
Try Flashing
Click to expand...
Click to collapse
Hello and thanks for your reply. I tried flashing my x8 with provded ftf file and the problem still remains the same. If it is any help i can normally increase volume, access emergency calls and keyboard and other things. But the screen remains blue. And i also remember that the thing which is supposed to appear here is the language setup, if there is any way to set up main language outside android system i guess that could help.
Again thanks for your reply and your time!
deamerz said:
Hello and thanks for your reply. I tried flashing my x8 with provded ftf file and the problem still remains the same. If it is any help i can normally increase volume, access emergency calls and keyboard and other things. But the screen remains blue. And i also remember that the thing which is supposed to appear here is the language setup, if there is any way to set up main language outside android system i guess that could help.
Again thanks for your reply and your time!
Click to expand...
Click to collapse
Try Flashing a Costume ROM for stock kernel via Recovery.
Here is a list of ROMs. Just make sure you download one that says (Stock).
Hello all!
First of all, I would like to thank the entire XDA for all the help and great developers for all their hard work and everything! You're THE BEST REALLY!
I hope you could help me with my problem :/
A few days ago, I flashed a custom rom (i've changed a lot of them already and this has never happened to me before). After flashing the phone the android system worked perfectly fine but after rebooting, phone just keept (and still is) restarting every 3 seconds. I cannot go into CWM recovery, only into Download mode. I've tried flashing stock rom with odin and in the end when it says > Close serial port and wait until rebooting, phone just keeps rebooting again. (Black screen, flash for a second and then again reboot). I've found someone on YT who has recorded the same problem so that you would understand what am I trying to say.
Type SAMSUNG GALAXY ACE (NEED HELP IT WON'T BOOT!) into YT and you will see the problem. ( i cannot paste the link)
What could i do? Btw, i've searched the forums for solutions but i didn't find a single 1 that would help me I cannot do it even with odin
PLEASEE HELP ME
R: Bricked ace keeps restarting (cannot go into recovery/CWM)
Hi! I think your rom (read only memory) got demaged so nobody can help you now
MeltingSnowman said:
Hi! I think your rom (read only memory) got demaged so nobody can help you now
Click to expand...
Click to collapse
Hello! So the only option would be to change the motherboard I guess?:/ Phone is in warranty unitil 17th of February but I don't know if they will repair it because I don't have stock rom on it anymore :/. I've changed many roms and the latest installed is CM10. Do you think that they will see which ROM and other stuff is on if It doesn't even boot? Is there a change that I could format the intrernal storage to cover up my previous installations? (hope you understand what I am trying to say)
R: Bricked ace keeps restarting (cannot go into recovery/CWM)
I understand what you mean, don't worry I think you should try the recovery procedure to unbrick the Ace as last thing you can do to use it back again. If EVRYTHING you can do (or you want to do) doesen't work send your device to service and hope that Samsung repair it for free because covered by warranty. Probably they will never know what you've done on it because memory is demaged. Some time ago I was too lazy to flash an original stock rom and I could not find the one I needed on the web so I sent my device to service with CWM on and no rom (formatted partition) and got it back with stock rom for free (was in warranty time). Best whishes
Inviato dal mio GT-S5830
Ok was afraid that you wouldn't hehe Yea well I tried like 10 times already with Odin but the problem is when Odin is kind of finished and it's time for phone restarting, phone just gets into a bootloop again (or how is it called). So I don't know :/ Maybe I need a new boot file? I can only enter download mode but unable to enter any recoveries modes although I have CWM. Ok I hope so, will probaby take it to the service tomorrow. Btw, do you know any other recovery procedures besides Odin? And thanks a lot for replying to my problem
If you have download mode still try kies to see if it will flash stock again
Sent from my GT-S5830
Ok thank you! Haven't tried that yet. Gonna try it right now.
Or try a different rom downloaded for xda and reflash, sometimes some roms get corrupted
Sent from my GT-S5830
Tried to use KIES but it says that the phone is unsupported :S Could the problem be that I'm using Win8? I've tried other roms already but I think that MeltingSnowman is right, it's damaged and I guess it's only fixable at service.
Nothing to do with win8 really and what method are you using on odin ? One package method or are you using all options
And try using a diff sd card as i had a damaged one that effected my flashing a while back
Sent from my GT-S5830
Oh ok I just thought that the compatibility could be the problem. I'm using one package method because I cannot find other single files :/. I've serched google already but all I ever found ware one packages. Sd card is fine. Do you maybe know where I could find single files? Please don't think that I am lazy but I really haven't found them
Your single files are in your rom you already have downloaded you just untick one package then apply them one by one which rom are you trying to flash ?
Sent from my GT-S5830
I've downloaded some stock 2.3.6 from SamFirmware but it's only 1 file (.tar )S5830DXKT7_S5830OLBKT3_S5830DXKT5_HOME.tar.md5.
It most likely to be a corrupt file, iv heard all sorts of stories from that site, find a stock rom on here thats flashable through odin and try your one package method again and also download the cooper ops file again, if you go to stickies at the top of this forum you will find what you need and hopefully get your ace to boot up again
http://forum.xda-developers.com/showthread.php?t=1034145
Sent from my GT-S5830
R: Bricked ace keeps restarting (cannot go into recovery/CWM)
1) Kies can't flash firmwares because you need an operative phone connected to PC and if you have anything different from stock rom on your mobile will obiviously say "Uncompatible Device", no matter wich SO you're running
2) A corrupted file from internet is almost impossible to get
3) A demaged bootloader would cause bootloops so if someone knows a way to load a new one to your device you'll be alright
4) One package or 100000 files can't cause a demage like that so the problem is sure not that
Inviato dal mio GT-S5830
Why cant there be a corrupt or faulty file ?
Sent from my GT-S5830
Didn't find any of these files. :/ Only ZIP files which are, If I am not mistaken, only supported by CWM.
MeltingSnowman said:
1) Kies can't flash firmwares because you need an operative phone connected to PC and if you have anything different from stock rom on your mobile will obiviously say "Uncompatible Device", no matter wich SO you're running
2) A corrupted file from internet is almost impossible to get
3) A demaged bootloader would cause bootloops so if someone knows a way to load a new one to your device you'll be alright
4) One package or 100000 files can't cause a demage like that so the problem is sure not that
3) I already tought of that but I couldn't find a way to install it, nor the bootloader itself. Hope some1 could provide this.
Click to expand...
Click to collapse
Did you download the coopers ops file again from the link i sent you and try and get stock XWKTR firmware from samfirmware site i flashed it today and im currently using it and put your phone in download mode and try and flash again ill keep looking around to see if i can help you further
Sent from my GT-S5830
---------- Post added 24th January 2013 at 12:03 AM ---------- Previous post was 23rd January 2013 at 11:56 PM ----------
Here is a link for cwm recovery via odin http://forum.xda-developers.com/showthread.php?t=1465599
Sent from my GT-S5830
Still can't access CWM. Bootloops continue. I don't know what to do anymore. I've tried almost everything really. Will probaby sent it to repair tomorrow, I don't see any other option :/
Good evening from Indonesia guys, okay i've post my problem here before, this is my last post about my problem http://forum.xda-developers.com/showthread.php?t=2768357 , it's about 2 years ago, and now i'm still working hard to find the way how to unbrick my Gnote, i've tried so many way on Google, but there is no result again (like 2 years ago), okay guys, i'm give up for 1 years about my problem, but now i think there is still a way for me to unbrick my Gnote, can you guys help me??
My Gnote problem :
My Gnote stuck on "Samsung Galaxy Note GT-N7000" logo
I've back up my data using Clockworkmod (CWM Recovery) before it's bricked, and i have a copy on my Laptop
I can go to Download Mode
I Can't go to Recovery Mode, my recovery mode was TWRP
When i go to Recovery Mode, its stuck in "TEAMWIN" logo
I can charge my Gnote
My Gnote was unidentified on Samsung Kies
But my Gnote still can be read on Odin or Heimdall
I hope you guys tell me what i have to do to resolve this phone, and give me a solution for my Gnote problem, i know its too late, and you guys asking me about why i don't buy another one after its bricked for 2 years? its because my Gnote was my dad's present when i got a scholarship on junior high school, and i'm so appreciate this present, Thank you guys for the time, sorry about my english, and sorry if I violate the rules of this forum....
Faprillah said:
Good evening from Indonesia guys, okay i've post my problem here before, this is my last post about my problem http://forum.xda-developers.com/showthread.php?t=2768357 , it's about 2 years ago, and now i'm still working hard to find the way how to unbrick my Gnote, i've tried so many way on Google, but there is no result again (like 2 years ago), okay guys, i'm give up for 1 years about my problem, but now i think there is still a way for me to unbrick my Gnote, can you guys help me??
My Gnote problem :
My Gnote stuck on "Samsung Galaxy Note GT-N7000" logo
I've back up my data using Clockworkmod (CWM Recovery) before it's bricked, and i have a copy on my Laptop
I can go to Download Mode
I Can't go to Recovery Mode, my recovery mode was TWRP
When i go to Recovery Mode, its stuck in "TEAMWIN" logo
I can charge my Gnote
My Gnote was unidentified on Samsung Kies
But my Gnote still can be read on Odin or Heimdall
I hope you guys tell me what i have to do to resolve this phone, and give me a solution for my Gnote problem, i know its too late, and you guys asking me about why i don't buy another one after its bricked for 2 years? its because my Gnote was my dad's present when i got a scholarship on junior high school, and i'm so appreciate this present, Thank you guys for the time, sorry about my english, and sorry if I violate the rules of this forum....
Click to expand...
Click to collapse
Soft-bricked is good, download mode and Odin recognisable is better so don't worry we can fix this for you. First though, your English is understandable so keep it up and you didn't violate anything. You even posted in the correct section so +5 for reading.
Looks like your recovery is broken so you need to first make sure your phone is boot-able. Therefore Odin flash a stock rom (this uses the download mode) to reset everything. From there, two ways are available to install recovery, stock update or Odin flash again so choose which one suits you best. Don't use the old KitKat roms (except NightOwl) since they're unsupported. Stable ones are NightOwl roms as it's still in active development.
AutumQueen92 said:
Soft-bricked is good, download mode and Odin recognisable is better so don't worry we can fix this for you. First though, your English is understandable so keep it up and you didn't violate anything. You even posted in the correct section so +5 for reading.
Looks like your recovery is broken so you need to first make sure your phone is boot-able. Therefore Odin flash a stock rom (this uses the download mode) to reset everything. From there, two ways are available to install recovery, stock update or Odin flash again so choose which one suits you best. Don't use the old KitKat roms (except NightOwl) since they're unsupported. Stable ones are NightOwl roms as it's still in active development.
Click to expand...
Click to collapse
Thank you so much for being honest, i'm so appreciate it, okay, i've flash so many recovery system (like Philztouch), but it still stuck in TEAMWIN logo, and there is no result, and i've flash another stock rom from sammobile, i choose the one for Indonesia region, but still no result, there is no difference, or should i try to flas the ginger bread stock rom??i try so many times to find another Dr Ketan Ginger bread stock rom, because the website where he upload the data (hotfile.com) were not open in indonesia (it has been blocked for a reason) so i have to find another website that provide the data, and there is no result again, or might be it's caused by the hardware or not??
Faprillah said:
Thank you so much for being honest, i'm so appreciate it, okay, i've flash so many recovery system (like Philztouch), but it still stuck in TEAMWIN logo, and there is no result, and i've flash another stock rom from sammobile, i choose the one for Indonesia region, but still no result, there is no difference, or should i try to flas the ginger bread stock rom??i try so many times to find another Dr Ketan Ginger bread stock rom, because the website where he upload the data (hotfile.com) were not open in indonesia (it has been blocked for a reason) so i have to find another website that provide the data, and there is no result again, or might be it's caused by the hardware or not??
Click to expand...
Click to collapse
Right now you ignore all of that. Odin flash a stock rom from sammobile, then install the correct recovery based on your stock ROM from this thread http://forum.xda-developers.com/showthread.php?t=1901191. Get the Jellybean rom, it's safer and easier.