Database Develop

[Q] Random reboot into bootloop- cannot access recovery. Please help!

a few days ago my fiance was complaining her basically stock Nexus was rebooting into a bootloop - where it displays the loading X and vibrates and then reboots and repeats every few moments (a few days after her doing the system update)- if I remove the battery for a few minutes then put battery back and reboot it will boot into the OS where it will stay sometimes for a few minutes othertimes an hour or more before going into the bootloop- so I told her I would attempt to flash a new rom. after many hours of messing with the phone and attempting to access the recovery it just will not work- the phone just goes into the bootloop - exactly as mentioned above. I have used fastboot to flash new images (userdata, system, boot, recovery etc) numerous times and it still does the same thing- crashes and reboots into the bootloop from the OS randomly and bootloop when trying to access recovery. I am pretty sure it is a hardware issue (the phone is only 3 months old) but the company i bought the phone from is stating it is a software issue and not covered by tehir warranty.
Problem is I unlocked the bootloader while messing with the rom's yesterday and am now concerned they wont honour the warranty anyway- does anyone have any suggestions as to anything else I can try? As far as I can tell as I cannot access recovery I cannot install any other roms..
Please help- otherwise I will be posting a yourtube video of me destroying a basically brand new nexus one- I really am that frustrated....

a bit more info- it was rooted but still had locked bootloader when this started- rooted using onclickroot or something- which after the update it wasn't rooted anymore- I am wondering if this has caused some low level conflict somehow- I have rooted again using superoneclick - and as stated have unlocked the bootloader.
is there any way to flash a rom using fastboot or adb on this thing- I would hazard surely there is but amongst all the information floating around for this phone I cannot find out how- I am thinking maybe I try and load cyanogen 6 or something if I could work out how to flash a rom using adb (because njo matter how many times I try to flash different recovery images it wont boot into recovery- I can access fastboot etc but as soon as i select recovery I get the bootloop...
and before I get flamed I have spent three days searching and reading and attempting everything short of voodoo witch magic. I thought my X10 was a P.I.A. to root and flash etc but really it was simple compared to the trouble this phone has given me..
I am wondeirng if some of the rom's are incompatible with some hardware- and I don't quite understand the whole radio thing either... can someone explain that?
BTW Im not a total noob- I have been around for a while without an account - then have had this account for a while but mostly just read the forums as I have no real input and knowledge to give...
...help!

Can no one help?
I have managed to get into recovery (by putting the phone in the freezer for ten minutes at a time to reduce the temperature and stabilise it enough to run for 15-20 minutes at a time)...
Have flashed different kernels this way and nothing is stable- it still bootloops because of heat....
I contacted HTC Hong Kong (it was purchased from a Hong Kong company) and they have told me there is a $350 fee to repair it as its a UK phone. Now the phone is exactly 55 days old not three months and I am really really frustrated.
Does anyone know if its worth contacting HTC UK?
I have friends in the UK I can have them send it in and recieve it from repair....
Someone please help- even if its just a comment of "just smash the damn thing..."
Thanks guys sorry about the long self centred posts but I am ready to destroy this phone- it doesnt have a mark on it either- any ideas what its worth for spare parts?

[Q] can someone help me out please

I got a hold of my friends galaxy tab by sprint and he had asked if i can fix it. The problem that he is having is that when you turn the tab on it gets stuck in the "Samsung" screen where it flashes but never fully boots up. Now typically if this occurred on my galaxy s phone i would just simply odin back to stock problem solved. However im not too sure the same applies for a galaxy tab. Can someone please help me out with this and let me know what steps need to be taken.
He did mentioned that before this problem occurred all he did was leave it charging over night and then unplugged it and tried to power it on and thats where he encountered this odd problem.

did he modify it at all?
maybe the kernel got hosed some weird way on the way it got charged, maybe overcharged and crapped out... you could try to reload a kernel...
when this happend with me, I had rooted it and applied cmw 3.0.0 without a kernel to support the ext partition. Try powering it off and holding down the vol button while powering it on. Does it go into download mode. If so get himdell from github (it acts similar to odin) once the drivers are loaded, install the libusb drivers for himdell in the galaxy tab drivers. there should be instructions in the text doc on what to do.
you can use himdell_frontend to flash a new kerenl.

Go to.. Galaxy Tab General
Or to... Galaxy Tab Q&A
This section is for posting of dev projects/guides/ref etc not for questions or general discussion.

when using himdell, is there a file(s) that will restore back to stock ?

AnthonyAldrete said:
when using himdell, is there a file(s) that will restore back to stock ?
Click to expand...
Click to collapse
As others have pointed out, this thread belongs in Q&A or Gen, however, having said that:
There's a discussion on flashing back to stock on a Sprint Tab here: http://forum.xda-developers.com/showthread.php?t=969892&highlight=sprint+stock+firmware
That thread points to another that yields the file, but the discussion in the one I linked looked to be worth reading.
I can't comment personally, as I am running a VZW Tab.
Good luck.

Samsung Galaxy S I9000 - ICS 4.0.3 - Stopped Booting

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!

[Q] Help with G-Note Revival...

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

[Q] Bizarre screen issues after flashing

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