Hi,
I installed a Cyanogenmod ICS 4.0.3. build 17 firmware on my Samsung Galaxy S I9000 almost 5 months ago from a tutorial. The update itself has been a fantastic experience from the start and I'm not sure if my current problem is even related to that firmware update. Apparently new users like me can't post URLs so I can't provide it now. If you need it let me know.
I have to admit that lately the phone has been rebooting every couple of days, or Android's been freezing and I had to remove the battery, but I didn't think too much of it. It wasn't too bad of a problem really, but this morning all of a sudden the device has become totally unusable. Help! :-/
The issue that's started since today is that my phone won't boot anymore. It seems to reboot somewhere during the boot process. There's only two screens that will be shown, before it reboots. When I remove the battery, put it back in and attach the charger, I will only see two charging screens. While charging, the device will also*reboot after a while.*
I can get into download-mode (volume-down + ok-button + power-key) but can't get into recovery mode (volume-up + ok-button + power-key).
Any ideas would be appreciated, thanks!
Greetings,
Adriaan
ps -> I have pictures of the booting screens and the charging screens but wasn't allowed to post them here. Again, if you need to see them please PM.
Hi,
I think you have to reflash using odin. You can be happy to reach download mode
I'll try that, thanks.
switch_42 said:
Hi,
I think you have to reflash using odin. You can be happy to reach download mode
Click to expand...
Click to collapse
just to be sure...
Just to be sure, could you please check that my logic is correct?
First off: the tutorial I had followed had me follow a few procedures:
first I updated Galaxy S with XXJVU Firmware
then rooted Galaxy S on XXJVU Firmware
after that I flashed CM 9, ICS 4.0.3. build 17 to the device
To which of these steps were you referring? My guess would be to take the last one, but perhaps it's wiser to restart the tutorial from the beginning. I'd appreciate any additional support you can give me, you can understand that I don't want to brick my device due to my misunderstandings..
Seems like a high overclock or high underclock
Sent from my GT-I9000
Helloworld294 said:
Seems like a high overclock or high underclock
Click to expand...
Click to collapse
Not sure what you mean there. In any event I've never taken any steps to overclock or underclock my device. Maybe it's going senile and I get to buy a galaxy s III soon
*phew* well my problem's been solved. Since I was able to get into download mode I flashed a baseline rom with Odin and found my way back to ICS. One surprise along the way was that from the same tutorial I had followed (and had happy results from) a few months ago, the step of using Odin to root the device wasn't working, it kept getting stuck at 'zImage' during the process! What's more, after that I was getting the BSOD image (the phone, exclamation mark and computer), which I found could be helped by using a 'One-Click Unbrick for Samsung devices'.
That was a XXJVU firmware. After some snooping around I found a different firmware than the one I had previously used and had switched from a XXJVU firmware to a XXJW4 firmware through a page on XDA-Developers. Did that. It worked. And now I'm back to ICS again, yay!
Thanks for the help along the way!
Related
Ok here goes... This is my first thread post here but I am in serious need of help.
I have searched and searched the forums for a hopeful answer but I have found it difficult to find the answer I seek.
So here is the story:
Bought a GT second hand from Akihabara in Japan which was locked to NTT DoCoMo. I was using it as a WIFI only Tab and all was wonderful till my IT brain decided it could be better and I began to tinker.
I had been looking around for a way to make my Australian Virgin Mobile SIM to work on the tab and found a lot of good answers but nothing that would make it work.
I then had the brilliant idea to change the firmware with a European firmware so I could get all the features enabled from a fresh start. Which is where it all went wrong.
I first tried to flash the tab using Odin 1.7 with the P1000XXJK5 euro firmware from samfirmware.com
This failed and left my tab with the picture of a phone and a pc with a dotted line and in between them an exclamation point in a triangle.
After a lot of fiddling (I dont remember what I did but I managed to get rid of that screen had something to do with retrying the flash and it was very late last night at this point) I managed to try again but Odin just kept failing on running the updated firmware.
I then decided that it would be a good idea to run the Rotohammer firmware by following the instructions on this thread:
http://forum.xda-developers.com/showthread.php?t=895827&highlight=sc-01c
This is where I once again received errors from Odin and now my tab is somewhat bricked.
I tried reflashing but same errors every time. (I currently dont have the errors from Odin but I will update my post when I get home)
I can still get to the downloading screen (Yellow triangle with the Android digging) so I am hopeful all is not lost.
So now you have heard my sob story I will ask two questions....
1. Has anyone actually successfully flashed a Japanese model Tab?
2. My only thought/hope at the moment can anyone direct me to an original NTT DoCoMo firmware so I can at least go back to having WIFI only Tab?
Thanks in advance if you can help
Alex
Yes , i suggest you to wait until you get a right firmware for it !
That would probably work if the partitions are a match !
What is this model called btw ?
"NTT DoCoMo Japanese Tab" or there is any model ? such as M180 for korean , P1000 , P100 Sprint , I800 Verizon , etc..
Br
Oz
I am searching the an original NTT DoCoMo firmware.
Electroboy said:
Yes , i suggest you to wait until you get a right firmware for it !
That would probably work if the partitions are a match !
What is this model called btw ?
"NTT DoCoMo Japanese Tab" or there is any model ? such as M180 for korean , P1000 , P100 Sprint , I800 Verizon , etc..
Br
Oz
Click to expand...
Click to collapse
Oz the model is SC-01C it has a build date of 2010/12
I was thinking considering I can get into the build/download screen maybe trying an emergency firmware recovery using Kies.
Hi,
I'm a fellow SC01 owner. You can get a backup of the stock firmware here: http://www.megaupload.com/?d=OJAK2UZF
Firmware code is SC01COMJK2
I believe there are newer firmwares (which I haven't installed as some of them contain a new bootloader that only allows for signed firmwares, same as the international units) that I have seen mentioned on various Japanese blogs. Let me know if you want me to try to hunt any down for you.
As for my SC01, I installed the custom kernel by koxudaxi and it's working great. Mind you, I've only changed to this kernel and apart from that am running the stock OS. I got his kernel here which can overclock to 1.4GHz: http://koxudaxi.sakura.ne.jp/
The kernel I installed via Heindall is zImage_ntt_2. It looks like he's built a newer version though, I might check that out. I think what you might want to do, is in download mode try to restore the above backup to your unit. Look up the Roto Backup thread to see how to do this. Hopefully since you can get download mode, all is not lost. I personally think it's quite crummy that there are different hardware versions like this which aren't interchangeable though >_<
I'm going to give the original firmware a go today at lunch time and I will let you know how I go. Thanks anyways for the link if all goes well I'll look at possibly trying the the koxudaxi kernel.
UPDATE: Well I'm not having luck getting the firmware to flash to my tab I keep getting "Failed to retrieve config Descriptor" when trying to flash. I will keep plugging away.
UPDATE: Still getting the same problems using heimdall to flash the tab. Any suggestions as to what I could do next?
Recovering a Docomo Tab
I'm currently running Overcome v1.1.3 ROM and richardtrip's V15 kernel on my SC-01C.
acont said:
UPDATE: Well I'm not having luck getting the firmware to flash to my tab I keep getting "Failed to retrieve config Descriptor" when trying to flash. I will keep plugging away.
Click to expand...
Click to collapse
You're getting this error from Heimdall, right? Have you tried Odin 1.7?
Here's how I recovered my Tab using Odin:
1. Following the instructions in http://forum.xda-developers.com/showthread.php?t=895827, specify the P1_add_hidden.pit in the PIT button and select Re-Partition.
2. Specify the stock Docomo ROM when pressing the PDA button.
3. Ignore the Phone and CSC buttons, as the stock ROM already contain these items.
You should be able to restore your Tab to stock settings using this procedure.
If this doesn't work, you might want to check if the USB connection to your PC is ok, and if everything necessary to run Odin is installed on your PC.
Bugger!
Well thanks for your help all of you but I think I have just made matters worse.
Last night I had success in flashing the original docomo firmware provided to me by zetsurin but I think I shouldn't have included the boot images.
Unfortunately I think it is completely bricked now it now wont turn on and when plugged into power (thinking that the battery had died) it just comes up with a white screen.
I can't boot into download mode and I can hold down the power button till I turn blue in the face... So as Bones would say "It's dead Jim"
Unless any of you have anything else I could try as a last ditch shot I might just have to ship it back to Japan and get them to fix it or maybe try Samsung here in Oz.
Serves me right
Thanks again.
acont said:
Last night I had success in flashing the original docomo firmware provided to me by zetsurin but I think I shouldn't have included the boot images.
Click to expand...
Click to collapse
What exactly happened?
The SC01COMJK2 firmware does not contain protected bootloaders, by the way.
acont said:
Unfortunately I think it is completely bricked now it now wont turn on and when plugged into power (thinking that the battery had died) it just comes up with a white screen.
Click to expand...
Click to collapse
I've heard about this happening when the battery runs out. Try connecting the Tab to your PC (not your AC adapter) and let it trickle-charge for an hour or so. If successful, you should see the download screen.
fury1sog unfortunately that didnt work
spoke to the samsung repairers here in Aus and they said they can take a look at it for me hopefully bring life back into my unit and then I will never touch it again
Any thoughts?
Hopefully this post is still being looked at but has anyone got any ideas as to what I could do before I fork out $374 to my tab repaired by Samsung Australia?
According to the repair guys its a faulty board (not an idiot that tried to flash it) and needs to be replaced. Not sure if this is worth my trouble considering I could buy a brand new tab for $599.
There is a positive out of this, the MB will be an Australian MB and I will have a working "Australian" tab instead of the Japanese version.
Considering the unfortunate tragedy in Japan I am not sure I should try and get my friend in Japan to fix it for me.
Thoughts anyone?
I know someone who can unlock it, I have mine unlocked by them.
I was afraid of flashing it myself so I paid to have it unlocked, cost was $20.
I think you better go for the MB replacement, it's cheaper.
For what it's worth, I went to reset my tab to factory using a rotohammer backup I made when I first bought it, and got stuck in a boot loop. So I then used ODIN. Still got a boot loop. Then I tried ODIN repartition... it hung for hours. Knowing the thing was likely bricked I pulled the plug and now I am in the situation as you: I have a crappy icon of a phone + an exclamation + computer image. Dead.
I think the best thing I can do for this junk is to toss it unceremoniously in the bin. Fortunately I also have an iPad which has resumed full-time service.
EDIT: Some signs of hope in here: http://forum.xda-developers.com/showthread.php?t=903257
Try "heimdall close-pc-screen" to see if your tab can get kicked back into the boot loop at least. Mine has failed a repartition, but I can still get it into the boot loop, which is a start. Will experiment over the weekend.
EDIT 2: Well my tab is back up and runing. I reflashed my original roto backup using ODIN with repartition on, then I went into recovery and did a factory restore. Back up like stock now. I think I'm going to sell it though, since it's been badly dis-owned by Samsung.
zetsurin said:
Hi,
I'm a fellow SC01 owner. You can get a backup of the stock firmware here: http://www.megaupload.com/?d=OJAK2UZF
Firmware code is SC01COMJK2
I believe there are newer firmwares (which I haven't installed as some of them contain a new bootloader that only allows for signed firmwares, same as the international units) that I have seen mentioned on various Japanese blogs. Let me know if you want me to try to hunt any down for you.
As for my SC01, I installed the custom kernel by koxudaxi and it's working great. Mind you, I've only changed to this kernel and apart from that am running the stock OS. I got his kernel here which can overclock to 1.4GHz: http://koxudaxi.sakura.ne.jp/
The kernel I installed via Heindall is zImage_ntt_2. It looks like he's built a newer version though, I might check that out. I think what you might want to do, is in download mode try to restore the above backup to your unit. Look up the Roto Backup thread to see how to do this. Hopefully since you can get download mode, all is not lost. I personally think it's quite crummy that there are different hardware versions like this which aren't interchangeable though >_<
Click to expand...
Click to collapse
hi zetsurin!
thanks for teaching me how to unlock the tab.
problem now is, im not able to successfully flash any rom. keeps saying write fail, using odin.
stuck at docomo logo when rebooted.
need help.
also used heimdall. starts downloading. but stuck almost at the end of the tab's progress bar.
argh...
me too ! samsung galaxy tab m180 Korean .... huhu
What ROM is best for a SC-01C?
Hi Guys
I picked up a 2nd hand SC-01C from Yahoo Auction, and am wondering what the best ROM to use with it is...
Looks like this guy has got an Overcome ROM on it OK, (http://chaki-ramone.blogspot.com/2011/06/galaxytabsc-01cgingerbreadromovercome.html), so I wonder if the latest version (http://forum.xda-developers.com/showthread.php?t=1205990) will work OK - anyone tried? (is the SC-01C a GSM-based model??)
I'm not going to use a SIM with it, so I'm not bothered about unlocking - but just want it rooted & want a good balance between speed & battery life. If you were going from scratch with an SC-01C, what would you do? Any suggestions greatfully received!
Thanks in advance?
PS - I'm an iPhone / iPad / Ideos 8150 / Notion Ink Adam owner, all jailbroken / rooted. So I'm not scared about rooting per-se, just worried about trying something that will not work because of anything docomo has done to the Tab!
Acont you could be coma bricked try pluginging it into THE MAINS for at least 4 hours if nothing come up your hard bricked.
Sent from my GT-P1000 using XDA Premium App
zetsurin said:
For what it's worth, I went to reset my tab to factory using a rotohammer backup I made when I first bought it, and got stuck in a boot loop. So I then used ODIN. Still got a boot loop. Then I tried ODIN repartition... it hung for hours. Knowing the thing was likely bricked I pulled the plug and now I am in the situation as you: I have a crappy icon of a phone + an exclamation + computer image. Dead.
I think the best thing I can do for this junk is to toss it unceremoniously in the bin. Fortunately I also have an iPad which has resumed full-time service.
EDIT: Some signs of hope in here: http://forum.xda-developers.com/showthread.php?t=903257
Try "heimdall close-pc-screen" to see if your tab can get kicked back into the boot loop at least. Mine has failed a repartition, but I can still get it into the boot loop, which is a start. Will experiment over the weekend.
EDIT 2: Well my tab is back up and runing. I reflashed my original roto backup using ODIN with repartition on, then I went into recovery and did a factory restore. Back up like stock now. I think I'm going to sell it though, since it's been badly dis-owned by Samsung.
Click to expand...
Click to collapse
Can anyone pls help,, my galaxy tab 7inch gt-p1000r is stuck on phone+pc logo, can't go to download mode, can't go to recovery mode,, can't do anything,, pls someone help me,, I am desperate..
huylang280285 said:
me too ! samsung galaxy tab m180 Korean .... huhu
Click to expand...
Click to collapse
unbricking M180 is done long time ago
Here is a video for you
http://www.ort-jtag.com/blog/?e=15
udhtari said:
Can anyone pls help,, my galaxy tab 7inch gt-p1000r is stuck on phone+pc logo, can't go to download mode, can't go to recovery mode,, can't do anything,, pls someone help me,, I am desperate..
Click to expand...
Click to collapse
What about this P1000R , what is special or different ?
I know P1000L was for south american edition !
lemmy_0 said:
hi zetsurin!
thanks for teaching me how to unlock the tab.
problem now is, im not able to successfully flash any rom. keeps saying write fail, using odin.
stuck at docomo logo when rebooted.
need help.
Click to expand...
Click to collapse
Docomo solution is very soon !
That TAB need JTAGging thats the only way ..
I have the good and dead device in hand , we will release for ORT-JTAG probably this week ..
Best Regards
Oz.
Connected my Samsung Galaxy Tab 8.9 to Kies yesterday and was informed there was a major firmware update (I live in Norway btw). Started the familiar process, all going well until 62% into the installation to the Tab. And there it froze... After a very long time I disconnected, tried the process recommended for emergency recovery. It stopped after 72% (or there around).
Now my device can't reboot, not even hard reset. All is lost and it has to be sent in for service Samsung says. When calling Support they said they were surprised Ice Cream Sandwich was released at this time for the device (sounded like they didn't know it was). Me too - I would have preferred to wait if I could have avoided this!!!
How do you know it was ICS.
Sent from my GT-P7310 using Tapatalk
I don't know it was (can't remember the version number displayed, stupid me!). When I called Samsung Support they said they were "surprised ICS was released now". I didn't claim it was when I called...
You are full of it.
Sent from my GT-P7310 using Tapatalk
Sorry? I'm just trying to report what happened to me so that it can be recorded if more experience the same. If I'm the only one with this problem then that is great (for the rest).
spirous said:
Sorry? I'm just trying to report what happened to me so that it can be recorded if more experience the same. If I'm the only one with this problem then that is great (for the rest).
Click to expand...
Click to collapse
You're the only one saying the Samsung have released ICS.
varsas said:
You're the only one saying the Samsung have released ICS.
Click to expand...
Click to collapse
See the question mark in the title of my post? I don't know or claim this was ICS, I'm trying to find out if it was and is only reporting what I experienced. I did so here assuming I get rational feedback and advice on it.
If it was ICS then others should also have it in Kies now, if nobody else has then it most likely wasn't. But I have seen no reports from others that they have got firmware upgrades to their 8.9 device on Kies now and ICS has been rumored to be around the corner. What did happen was that I got a firmware upgrade - no matter if that was ICS or not.
The idiotic thing was that I was so excited when I saw there was an upgrade on Kies that I ignored taking backup before proceeding. How stupid can you be...
Were you really not able to go recovery mode? When was the last time you used kies before you tried this? Maybe it was an older firmware?
The recovery mode also stopped, after 70-something percent. Might have been a few weeks since I checked Kies last, but not a very long time.
After the recovery mode also hanged, the device only displayed the firmware error page. When trying to hard reset (volume up & start button) I got an Android logo saying it was downloading (which it couldn't have been as it was not connected to anything).
Got it back from repair and it has Android 3.2 (2.6.36.3).
spirous said:
After the recovery mode also hanged, the device only displayed the firmware error page. When trying to hard reset (volume up & start button) I got an Android logo saying it was downloading (which it couldn't have been as it was not connected to anything).
Click to expand...
Click to collapse
Isn't that download mode....As in what you'd want to flash a rom with ODIN?
Did you try flashing the stock firmware back on it before you sent it in for repair?
I kinda messed up my i957 last week when playing around with it. I wasn't paying attention to the 3g vs LTE so it was my bad. Tried some stuff out and the tablet was whacky!
Wound up going to Samsung support page and hunted down original firmware and flashed with ODIN and all was well again.
Glad your back up and running
Hi Guys...
I got a Galaxy Note GT-N7000, and its been more than a week i tried to revived it using the any method i've found in this great forum.
So let me tell u guys the stories of my Note :
1. It was always updated OTA so the last ROM i used is Indonesian Note ICS 4.0.4
2. One day (last Friday) while i was browsing Internet using it, it suddenly got very hot, and the battery seems like draining very fast
3. In the mid day it reboot by its self, and entering countless reboot... a never ending reboot
4. So i tried to enter recovery, and yes sadly i've might triggered the emmc bugs by doing factory reset. But i'm not sure i've done it or not, coz i've a CWM recovery installed.
5. Anyway then i tried to flash stock room found in dr.ketan's thread...many thanks to him for those collection using PC ODIN and i got the "factoryfs" stuck problem
6. I also tried to flash countless kernel over and over, tried install Stock GB and ICS, tried RocketROM, CM10 and it all failed. In dowload mode i still got a Stock Firmware installed. So any ROM i've tried to install using Kernel didn't succed.
7. So i decided to take it to Samsung Service Center nearby, and i found that my battery is BAD, it wont charge (wonder would it because of the battery i got that problem in the first place). Since i got this Note for around 8 months, and the warranty for the battery is 6, the make me bought the new one, ordered and available in 2 days.
8. So I get back to the service center, put the new battery restarted the phone, and it stop on samsung logo (no yellow triangle there). So I complained, and they look into it, and said we may try to install new software, but there's a risk that your Note got damaged. They said the risk is mine and they wont have any responsible for it.
9. So furiously i bargain about my Warranty (12 month), coz the said that i've updated the ROM my self, so i explained to them that it was OTA's update, all i do was press YES, and they said even OTA official update will cancel my warranty. Its getting weird, i got angrier and they just said its their company procedure so there's nothing they can do to help me. So Samsung Indonesia will cancel warranty for every attempt to update the ROM OTA's, only their service center is allowed to do so. Wasted my valuable working hours there...
10. So i get back, determined i officially will do anything to get this Note life back. So i started to look at Forrest1971 (many thanks to him) thread about bricked note and tried many kernel and got one working with adb (T-Kernel V0.9) doing the checking and found faulty partition 9 and 10 and doing the step and finally got the partition fixed. Lost 3GB of space.
Then here came the real problem :
1. Still wont work with ODIN, stuck at Factoryfs with stock ROM GB N7000DXLC2_N7000OLBLC2_N7000DXLC1_HOME.tar and ICS N7000DXLR5_N7000OLBLR2_N7000DXLR1_HOME.tar. But working fine flashing Kernel so my guess it is not the connection problem. I've tried on 1 PC, 2 Laptops, 2 OS (Win7 32bit and WinXP 32 bit) still the same.
2. Then i tried to flashing via Kernel (CWM, Abyss, T-Kernel, CM9 Safe Kernel) i got to do trial and error coz not all ROM can be installed using any given Kernel. Seems that T-Kernel v0.9 is working for most of the ROM. Sorry i didn't keep note about the kernel-rom coupling. Here is the list of ROM i've tried :
cm-9.1.0-n7000 + gapps-ics-20120429-signed
cm-10-20121209-NIGHTLY-n7000 + gapps-ics-20120429-signed
RocketROM v2 XXLS7_stock_odexed
SuperNexus-N7000-BUILD5-20121017 + gapps-jb-20121011-signed
RocketROM_ICS_XXLPY_v1
3. All of those ROM came out with the same problem :
- Freezing on the Samsung/Mod Logo Screen (Got very HOT)
- Entering the "Andoid is Upgrading" and then updating Apps but stuck at random number (# of ###) (Got very HOT), i've tried to wait overnight but stay on the same number
- Succeeded boot up but Freeze after couple of minute (Got very HOT)
4.All those problem seems happened randomly, but most of the time it happened like this :
Stuck and Logo Screen - Reboot by me - Stuck and Upgrading - Reboot by me - Boot fine, but freeze very soon - Reboot by me, and back to the Logo stuck... (but still sometime its just random), the only thing same that it got very hot.
5. This is my last resort, i'll try to flash Supernexus, CM9 or CM10 without the GApps. Now i'm on Supernexus ROM, not yet freeze while i'm typing this. But without the GApps i wont have G-Play, and cant reinstall Apps that i bought in G-Play. Dilemma...
So any thoughts or advices will be greatly appreciated...
I really like this phone, wish i can revived this phone... :fingers-crossed:
Thanks B4 for any comment...
Well, i guess no one have the same problem here...
I'm running the rocket ROM ICS right now, this is the one ROM that got me closer to "STABLE" state.
Still got self reboot, most of the time when i'm using browser (Android, FF, Chrome), or after a long run on youtube or downloading something.
I've also tried the PA Experia ROM by AmniX : http://forum.xda-developers.com/showthread.php?t=2100083
But it was worse than rocket ROM ICS, more likely have the same symptom with the CM9/10 i've tried.
So seems like i've to manage to use this defect/handicapped gadget... :fingers-crossed:
diasdroid said:
Well, i guess no one have the same problem here...
I'm running the rocket ROM ICS right now, this is the one ROM that got me closer to "STABLE" state.
Still got self reboot, most of the time when i'm using browser (Android, FF, Chrome), or after a long run on youtube or downloading something.
I've also tried the PA Experia ROM by AmniX : http://forum.xda-developers.com/showthread.php?t=2100083
But it was worse than rocket ROM ICS, more likely have the same symptom with the CM9/10 i've tried.
So seems like i've to manage to use this defect/handicapped gadget... :fingers-crossed:
Click to expand...
Click to collapse
I would complain to the service center. It's absolutely rubbish that an ota update voids warranty, they're lying through their teeth and I wouldn't stand for it. So long as you have no trace of custom rom or root, they are required by law to fix the phone or replace it within 12 month warranty. If you'd left traces of root or Cwm that's a different story.
Try a second repartition, often a first scan will not find all bad sectors, run through it again just to be safe. Also, after repartitioning its usually the case that stock or tw based Roms won't work without freezes and reboots because they occupy too much space on the emmc. You're best with cm or aokp Roms.
Sent from my GT-N7000 using xda premium
Hello guys,
I have around 2-year old Note GT-N7000 which I tried flashing a week ago. I did a few steps (don't remember any though) and something went wrong. Everything with the phone was working fine except the keyboard was typing 'null' and the screen had a weird problem. The phone will boot normally and the screen would be fine until it turns off (auto off or manually by button). Now if I try to switch on the screen it would start as if it's warming up. A sky with tiny stars kind of scene would appear and the brightness will keep increasing. The phone is functioning at this point and so is screen but nothing can be seen. I know this because I can receive a phone in this state by guessing the swipe location and swiping. Once in this mode, I have no option but to restart the phone. And then again everything works fine as long as I do not let the screen go off.
I got panicked and after a full research of 5 days on XDA, I decided to flash another ROM, probably a JB. I rooted my phone, install CWMR, bought mobile odin pro only to mess the things further. I downloaded the Ultimate Alliance ROM v3 and tried flashing it using the mobile odin. I guess I didn't follow the instructions properly and the phone went into bootloop. I then flashed GB KJ1 using ODIN which landed me at N7000 screen freeze and not able to enter recovery mode. Then I flashed AbyssKernel which helped me boot properly. Once I was in I realized I'm still on GB so probably JB never got installed.
Now the current problems are:
1. The keyboard is still typing nulls
2. The screen is still going into comma
3. There is a yellow triangle at the GT-N7000 screen.
My phone version is:
Baseband version: N7000XXLSO (it was N7000DDLR1 two hours ago)
Kernel: 2.6.35.7-N7000XXKJ1-CL627135
Build No: GINGERBREAD.XXKJ1
Sorry all this is noob stuff and maybe there is a solution in the forum already but after 5 nights of research and lots of messing around, I am not sure what do I do next. I certainly don't want to hard brick the phone.
Desperately need your help to come out of this mess. Even I'm happy to have the oldest stock ROM.
Thanks in anticipation and sorry for the long post.
trunoob said:
Hello guys,
I have around 2-year old Note GT-N7000 which I tried flashing a week ago. I did a few steps (don't remember any though) and something went wrong. Everything with the phone was working fine except the keyboard was typing 'null' and the screen had a weird problem. The phone will boot normally and the screen would be fine until it turns off (auto off or manually by button). Now if I try to switch on the screen it would start as if it's warming up. A sky with tiny stars kind of scene would appear and the brightness will keep increasing. The phone is functioning at this point and so is screen but nothing can be seen. I know this because I can receive a phone in this state by guessing the swipe location and swiping. Once in this mode, I have no option but to restart the phone. And then again everything works fine as long as I do not let the screen go off.
I got panicked and after a full research of 5 days on XDA, I decided to flash another ROM, probably a JB. I rooted my phone, install CWMR, bought mobile odin pro only to mess the things further. I downloaded the Ultimate Alliance ROM v3 and tried flashing it using the mobile odin. I guess I didn't follow the instructions properly and the phone went into bootloop. I then flashed GB KJ1 using ODIN which landed me at N7000 screen freeze and not able to enter recovery mode. Then I flashed AbyssKernel which helped me boot properly. Once I was in I realized I'm still on GB so probably JB never got installed.
Now the current problems are:
1. The keyboard is still typing nulls
2. The screen is still going into comma
3. There is a yellow triangle at the GT-N7000 screen.
My phone version is:
Baseband version: N7000XXLSO (it was N7000DDLR1 two hours ago)
Kernel: 2.6.35.7-N7000XXKJ1-CL627135
Build No: GINGERBREAD.XXKJ1
Sorry all this is noob stuff and maybe there is a solution in the forum already but after 5 nights of research and lots of messing around, I am not sure what do I do next. I certainly don't want to hard brick the phone.
Desperately need your help to come out of this mess. Even I'm happy to have the oldest stock ROM.
Thanks in anticipation and sorry for the long post.
Click to expand...
Click to collapse
Jesus Christ, way to get yourself into a mess... The null keyboard just means you have to reflash the csc correctly. Extract the gb rom file and it should reveal a csc file, input that into the csc part of mobile odin and flash.
Screen problems... How old is your battery?
Triangle issue, just download triangleaway app from play store and run.
Hopefully you've learnt something about following directions to a t. Don't think you've done any lasting damage though, you're lucky.
Sent from my GT-N7000 using xda premium
Thanks a lot for the quick help.
The battery is as old as the phone i.e. about 2 years.
I had flashed the same phone around an year ago and I faced similar screen issue when I tried flashing ICS last year and then I reflashed GB (the current ROM I guess) and the problem disappeared. Do you think it could be because of wrong flashing as well?
Is there is safe route to a relatively safe flashing which could reassure whether I should buy a new battery or not? Or shall I go ahead and invest in the battery regardless?
Thanks once again.
trunoob said:
Thanks a lot for the quick help.
The battery is as old as the phone i.e. about 2 years.
I had flashed the same phone around an year ago and I faced similar screen issue when I tried flashing ICS last year and then I reflashed GB (the current ROM I guess) and the problem disappeared. Do you think it could be because of wrong flashing as well?
Is there is safe route to a relatively safe flashing which could reassure whether I should buy a new battery or not? Or shall I go ahead and invest in the battery regardless?
Thanks once again.
Click to expand...
Click to collapse
Safest flash would be to flash latest gb rom for your region. I'd be amazed if the battery wasn't dead though, they usually only last just over a year. Symptoms of dead battery are screen flicker, sudden power loss and gain, physical swelling (put on flat surface and spin) colour change on screen, amongst other things.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Safest flash would be to flash latest gb rom for your region. I'd be amazed if the battery wasn't dead though, they usually only last just over a year. Symptoms of dead battery are screen flicker, sudden power loss and gain, physical swelling (put on flat surface and spin) colour change on screen, amongst other things.
Click to expand...
Click to collapse
Thanks a lot for the help. I could successfully flash GB 2.3.6 from Dr Ketan's thread and everything is working like charm. The screen issue that I mentioned is gone.
Thanks once again.
trunoob said:
Thanks a lot for the help. I could successfully flash GB 2.3.6 from Dr Ketan's thread and everything is working like charm. The screen issue that I mentioned is gone.
Thanks once again.
Click to expand...
Click to collapse
Good news, well done
Sent from my GT-N7000 using xda premium
We have a AT&T LTE 8.9 which I now deduce is a P7320 model. A year back when I got the 8.9, I rooted it, CWMed and installed a a AOKP ROM and it has been running great since. However, last week I swapped it for another device with my brother who decided I should put it back to the stock ROM so that he could ebay it.
Well with all the timeliness and hectic mode of the festive season, I failed to research thoroughly and flashed it a stock P7300/P7310 ROM. Which rendered it completely dead. It would not respond to anything, power/vol+, power/vol-, power/both vols, usb to pc, usb to wall with no charging icon e.g. Odin doesn't even see it. The only sign of life if that, is that it shows up as an error with QHUSUB_DLOAD in device manager.
Right now, I have the power button taped down to see if I can get anywhere draining the battery. You would think that Odin should at least see it? Is this the end of my tab?
bdbx18 said:
We have a AT&T LTE 8.9 which I now deduce is a P7320 model. A year back when I got the 8.9, I rooted it, CWMed and installed a a AOKP ROM and it has been running great since. However, last week I swapped it for another device with my brother who decided I should put it back to the stock ROM so that he could ebay it.
Well with all the timeliness and hectic mode of the festive season, I failed to research thoroughly and flashed it a stock P7300/P7310 ROM. Which rendered it completely dead. It would not respond to anything, power/vol+, power/vol-, power/both vols, usb to pc, usb to wall with no charging icon e.g. Odin doesn't even see it. The only sign of life if that, is that it shows up as an error with QHUSUB_DLOAD in device manager.
Right now, I have the power button taped down to see if I can get anywhere draining the battery. You would think that Odin should at least see it? Is this the end of my tab?
Click to expand...
Click to collapse
First of all, is your tab booting to AOSP now ??
if not can you see the [Samsung Galaxy Tab Logo], and after what did that happened (is it after you flashed a P7300 Stock ROM??)??
have you ever flashed stock ROM through odin before??
can you at least enter the recovery (CWM)??? cuz that would make things easier
we should know these things before we can help
omarainea said:
First of all, is your tab booting to AOSP now ??
if not can you see the [Samsung Galaxy Tab Logo], and after what did that happened (is it after you flashed a P7300 Stock ROM??)??
have you ever flashed stock ROM through odin before??
can you at least enter the recovery (CWM)??? cuz that would make things easier
we should know these things before we can help
Click to expand...
Click to collapse
The tab is non-responsive to *anything*. It won't boot, tethered or not, after the incorrect stock rom flash. I cannot get into recovery and odin does not see it. I have had a blank screen since.
Yes, I am somewhat familiar with odin/fastload/adb and various other tools for my android phones. Prior to this deadly flash, I had used odin to install cwm and a ROM on it. However, at this point, odin cannot see the tab either.
bdbx18 said:
The tab is non-responsive to *anything*. It won't boot, tethered or not, after the incorrect stock rom flash. I cannot get into recovery and odin does not see it. I have had a blank screen since.
Yes, I am somewhat familiar with odin/fastload/adb and various other tools for my android phones. Prior to this deadly flash, I had used odin to install cwm and a ROM on it. However, at this point, odin cannot see the tab either.
Click to expand...
Click to collapse
I assume that the problem is caused from the bootloader incompatibility
so you're saying that you can't enter the download mode or CWM
and your computer can't recognize your tab through adb connection ether
if this is exactly the case, then I don't think anyone can help you
maybe you should try to take your tab to any close samsung branch
Good luck
omarainea said:
I assume that the problem is caused from the bootloader incompatibility
so you're saying that you can't enter the download mode or CWM
and your computer can't recognize your tab through adb connection ether
if this is exactly the case, then I don't think anyone can help you
maybe you should try to take your tab to any close samsung branch
Good luck
Click to expand...
Click to collapse
You can get JTAG for about $40 so not that bad:
http://www.youtube.com/watch?v=BgL5vWRwh5k#t=22
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-8-9-jtag-brick-repair/