Hello,
I am using N7000 and at the moment my phone starts up;
- I can hear the bootsound,
- I can see the bootlogo but its green
- phone boots fully and works because I can receive texts,mails,etc.
So I looked around on the forum and found few things. One of the major things I came across was flash, root errrors but I haven't flashed, root or even updated it. A possible solution was to boot it correct so I followed the manual:
http://forum.xda-developers.com/showthread.php?t=1424997
But I need to find my kernel version which I can find in my phone's settings but I don't see anything its black screen. IS there other ways to find my kernel? I am using dutch phone. international model but I am not sure.
Thank you for reading.
Related
Hello folks
I'm kinda new in this forum, but i'm always told that i have a great potential
I want to be one of the most important android developpers (apps and ROMs, etc)
enough with the introduction
I have a Nexus One, and I've rooted it following the unlockr site
but after the last step (which i think is the devil here) i started to get a pink unlock icon (not a blue one), and after that, whenever i try to access recovery (after holding the power and volume down buttons) i get the nexus x logo with the unlock icon at the bottom for a few seconds, then I get our little green guy (android) with an exclamation mark, and that's it. Nothing happens next, i have to pull out the battery to restart. it only works when i plug my N1 to the computer an run the fastboot-windows.exe boot recovery-RA-nexus-v1.7.0.1.img (i got this from other site)
so what's the problem?
i really want it to act normally!
oh! one other thing
there's an app called universal androot from here Android Applications | TheUnlockr
but it won't work
when i root it says failed!
when i unroot it says that i have to root my phone first (my phone is already rooted!!!!)
any idea what is happening in my N1's mind?
There is no "blue unlock icon". The text on bootloader screen is always pink.
You didn't flash your recovery correctly.
It might be also that you didn't root your phone correctly - you just unlocked the bootloader.
If you want to be a developer, you need to learn to read a lot, so here's a good exercise for starters - there's a Wiki on this site, for Nexus. Find it, find the relevant guides and procedures, do whatever you need to get your phone running a custom ROM of your choice. Also, try to read some more to understand, why does Universal Androot fail, the reason is (most probably) found in the Wiki also.
hmmmmmm..... OK
no problem
i'll go to this wiki and hit the rod
If I had some any problems i'll let u know OK
**Resolved.
Hey all,
This could be a quick answer or hopefully something more. First off, I appreciate you reading this - and all XDA does. It's really nice to see development for the Android system.. so thanks for sure.
Deal is, is that I have a Galaxy Tab with build something like gjj7 - I didnt write it down before the flash.. ugh. Anyway, the post i was reading was installing Clockwork Mod, and recommended the forum below (on XDA)
http://forum.xda-developers.com/showthread.php?t=788108
I used the CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.15.3 because the thread talked about using the JPy file if your ‘Build Number’ wasnt listed.
Odin3 looked great - no errors, all green. Tab did not reboot itself though, just hung. I rebooted, and now it doesn't look to start. If i keep hammering away though, it will show the Galaxy Tab intro screen, but then stop again.
I've seen the battery logo come up a few times too - looked grey - though it was a full charge before the flash.
I did check a Google search and went through all the posts I could on XDA, but just didn't see what I'm looking for. Is it indeed bricked, or because it 'kinda works sometimes not really" is it gonna be ok?
THanks for any replies,
** Edit - I put it in the box to put it away for a while - and when I opened it - the Tab turned on with the Android dude holding a sign. Anyone know why thiswould have turned on after being in the box for a while? I have not tested to see if the computer recognized it - but would like to know if you have a stock Galaxy Tab firmware i can reload.
Hey thanks again for any help -
-Kenny
Hi, I'm no expert, but what I think you may have done is load a kernel only, and you'll need to load a ROM on top in order to get the Tab working again.
I say that because I loaded a .tar file onto my Tab and it hung on the Samsung Galaxy Tab screen. Only when I loaded the JJ4 'full flash' (as I saw it referred to) was I successful in getting my Tab back online. The JJ4 has three .tar files included, one for each slot (Modem, PDA, and CSC).
It's pure guesswork on my part, I am still very new at this, but that might be your issue.
In your shoes I would look for threads about combining kernels and ROMs...?
Hope this helps. And I hope someone will correct me if I'm completely off-track.
k3nnynapalm said:
** Edit - I put it in the box to put it away for a while - and when I opened it - the Tab turned on with the Android dude holding a sign. Anyone know why thiswould have turned on after being in the box for a while? I have not tested to see if the computer recognized it - but would like to know if you have a stock Galaxy Tab firmware i can reload.
Hey thanks again for any help -
-Kenny
Click to expand...
Click to collapse
I'm no expert and havn't done any ROMs for my Tab yet, but I am planning to and thus am reading heavily on the subject.
If I'm not mistaken, the "Android dude holding a sign" is an icon for download mode. This means, you havn't done any ROMs yet, just the kernel part. (Same as above reply)
I suggest that you look at this post ---> http://forum.xda-developers.com/showthread.php?t=932082
It's the one I'm planning to follow. Alterbridge86 has done an excellent job on this post. It has a downloadable step-by-step instruction, as well as the necessary links to files you will need. I suggest you print the instructions so your PC can concentrate on the ROM part.
I hope this helps, and if it does, please click on the thanks below..
Treb71, and SelfP - thank you for the replies guys, I really appreciate that. I finally got a chance to sit down with it again, and recharged it.
I got it into that download mode (power and both volume buttons - seems different everywhere i look, but it worked) and have it being recognized as a Samsung USB Composite Device in device manager. Good to see it can still be found eh?
When you mention Kernal only, - that sounds familiar. What is the difference behind this and ROM? Just the ROM is more of the O/S it uses? Is there a benefit to loading a Kernal thats not the default one that I missed? :S
I'm going to load up those links - that puts me on a great start. I don't normally feel like a total n00b around technology (I'm sure most people on XDA know their stuff) but this experience has humbled me hah.
THanks for the replies!
Hot dog -
It worked.
Basically, reading the PDF he gives here -
http://forum.xda-developers.com/attachment.php?attachmentid=578831&d=1303832984
The first 7 pages talk about backing up, i didn't need to worry about that part and went straight to the Odin3 flash.
Here it hung for a bit. Didnt skip past the "setupconnection" after hitting start (after loading the files of course - as stated) but then i realized the dude holding the sign image I was looking at was not the same as the "Download Mode" sign. The one I was referring to was holding up a sign in the top right corner. Didn't think of 2 versions of it come to think of it.
Anyway, rebooting the tab, reloading the files in Odin, and making sure I was indeed in Download mode - went through.
It was in Netherlands though hahah. Upon boot up I just needed to change some Language settings.
We're good!
I'll continue on with the flash tomorrow (it's late here now) and let you know how the custom firmware is - I figure why not, it's all pretty smooth so far.
You've both been a help, if I could hit thanks a couple more times on your posts you know I would. Let me know if you decide to flash, and if you have any questions or thoughts based on my experiences, and I'll do what I can.
Thanks again XDA - bad ass thread you got going on here the more I learn about it.
-Kenny
Hi all experts,
Yesterday my GT started force closing ALL apps all of sudden. So I tried to reboot the GT and it was stuck at the SAMSUNG logo screen.
When it finally boot(occassionally) to home screen, icons and widgets ALL GONE back to default, apps still force close. Showed setup screens (put in sim...etc). Lookout app shows installed on Market but cannot run. Some apps previously installed showed "free" in Market seems like never installed. Popouts showing force close still.
Open Recovery it shows (see picture). Anyone please HELP!
Well your tab is screwed up lol (for a reason I dunno due to lack of details). Flashing a stock firmware should fix it right away. Charge your tab to the 100%. Go to overcome website and follow the instructions (READ THE GUIDE, then REREAD IT AGAIN) to flash a stock ROM of your choice (or you can flash our stock safe v5 as well. The choice is up to you) once you are done you will be on a pure unrooted stock rom. Feel free to stay on stock or flash w/e custom ROM you desire
I think my GT has always been on stock Rom. I z4rooted it at 2.2 after awhile had all kinds of problems. Then I updated it to gingerbread thru. Kies and it went fine for 2 weeks.
Do you know how to find out which original Rom it is supposed to be with? (I bought it second hand, unbranded international GT-P1000, when I got it it had TGY rom) Let me know what info/detail you need I will post them...
BTW, 1 out of 5/6 times I went to Recovey, it showed something like 'checksum (0)' 'no need to check' but still shows the 'cant access to system/csc/TGY/system' (see picture) When boot it still stucked at logo screen...
anyone expert can help?
DarkPal said:
Flashing a stock firmware should fix it right away. Charge your tab to the 100%. Go to overcome website and follow the instructions (READ THE GUIDE, then REREAD IT AGAIN) to flash a stock ROM of your choice (or you can flash our stock safe v5 as well. The choice is up to you) once you are done you will be on a pure unrooted stock rom. Feel free to stay on stock or flash w/e custom ROM you desire
Click to expand...
Click to collapse
Your question has been answered... We can't help people who DON'T read their responses...
Yeesh....
I did read the responses and brought TAB to local cellphone repair store with Darkpal's solution. I tried 3 of them and none of them were able to solve the problem having tried to flash different roms, and none of them were confident about finding the "original stock rom".
I was suspecting hardware issues, because this TAB I have was second handed therefore I have little idea what "stock rom" it was with, and the larger than usual gap between case and screen on SIM/sd side of the TAB suggested it had been opened.
All in all, I sent my TAB to Connexion2005 who said will JTAG my TAB. Let's wait to hear from him and I will post the result here.
hhc said:
I did read the responses and brought TAB to local cellphone repair store with Darkpal's solution. I tried 3 of them and none of them were able to solve the problem having tried to flash different roms, and none of them were confident about finding the "original stock rom".
I was suspecting hardware issues, because this TAB I have was second handed therefore I have little idea what "stock rom" it was with, and the larger than usual gap between case and screen on SIM/sd side of the TAB suggested it had been opened.
All in all, I sent my TAB to Connexion2005 who said will JTAG my TAB. Let's wait to hear from him and I will post the result here.
Click to expand...
Click to collapse
I am here to report the outcome as promised. Sent the Tab to Connexion2005 for JTAG and got it back after 1 week. It has been over a month and everything works fine. I have to give Connexion2005 the credit to revive my $400 investment. THANK YOU!
Also thanks to all attempted to help in this post. Thread closed!
Hi all,
This is my first post on XDA, but have found it useful in the past when needing info for my original G1 and later my HTC Desire, both of which I rooted and added custom roms on via the threads here.
Now though I am really stuck having cocked up an attempt to install Cyanogenmod 10.2 on my 4X HD.
I have a black screen with red text saying "Stuck on Critical Failure:Unable to start Kernel." and a few more lines.
I initially followed a guide at AndroidLegend but because the links in this guide went to Nightly's for 10.2 I decided to download a stable 10.1 instead. I can't post the link but the comments show the problems I was having.
The end result was that I never managed to install 10.1 and had just gone back to the original factory settings, but along the way on another forum I saw someone mention that the ROM may have the original phone name wrong and to take out the assert name in a config file, which I did (now knowing that that was the last thing I should have done). So upon rebooting I ended up where I am now.
I have searched thoroughly on these forums and have tried numerous fixes none of which none have been successful.
The one that I feel comes closest is this one by RuedasLocas (post number 7) on "Rollback Optimus 4X HD from 4.1.2 JellyBean to 4.0.3 Stock ICS"
I've followed it exactly and tried 3 or 4 times on different PC's and although I can see the phone in Device Manager and change port settings (LGE CDMA USB Serial Port to 41) etc, I never get beyond LGFlash Tool changing from "waiting" to anything downloading in Blue or failing in Red, nothing happens and my phone will just sit there in SafeMode whilst plugged in.
Can anyone suggest anything else that I need to do?
Many thanks if you got this far!
Snookered said:
Hi all,
This is my first post on XDA, but have found it useful in the past when needing info for my original G1 and later my HTC Desire, both of which I rooted and added custom roms on via the threads here.
Now though I am really stuck having cocked up an attempt to install Cyanogenmod 10.2 on my 4X HD.
I have a black screen with red text saying "Stuck on Critical Failure:Unable to start Kernel." and a few more lines.
I initially followed a guide at AndroidLegend but because the links in this guide went to Nightly's for 10.2 I decided to download a stable 10.1 instead. I can't post the link but the comments show the problems I was having.
The end result was that I never managed to install 10.1 and had just gone back to the original factory settings, but along the way on another forum I saw someone mention that the ROM may have the original phone name wrong and to take out the assert name in a config file, which I did (now knowing that that was the last thing I should have done). So upon rebooting I ended up where I am now.
I have searched thoroughly on these forums and have tried numerous fixes none of which none have been successful.
The one that I feel comes closest is this one by RuedasLocas (post number 7) on "Rollback Optimus 4X HD from 4.1.2 JellyBean to 4.0.3 Stock ICS"
I've followed it exactly and tried 3 or 4 times on different PC's and although I can see the phone in Device Manager and change port settings (LGE CDMA USB Serial Port to 41) etc, I never get beyond LGFlash Tool changing from "waiting" to anything downloading in Blue or failing in Red, nothing happens and my phone will just sit there in SafeMode whilst plugged in.
Can anyone suggest anything else that I need to do?
Many thanks if you got this far!
Click to expand...
Click to collapse
when you get to "waiting", plug out your cell phone, eject battery, put the battery back in and hold vol - while plugging it back into comp. lgflashtool should then recognise the device and start flashing.
another thing you can do is use kdz flasher, which has a bit easier interface when compared to lgflashtool.
Many thanks for the speedy reply Flying_Bear, possibly seeing some success, did as you said and a file downloaded to the device, however I am now seeing the image that I have attached.
It looks like it's saying don't remove cable and don't switch off and refresh?
Can you confirm what I should do next?
Thanks again
Snookered said:
Many thanks for the speedy reply Flying_Bear, possibly seeing some success, did as you said and a file downloaded to the device, however I am now seeing the image that I have attached.
It looks like it's saying don't remove cable and don't switch off and refresh?
Can you confirm what I should do next?
Thanks again
Click to expand...
Click to collapse
hmmm, truth to be told, i dont remember seeing that image appear when using lgflashtool. also, i've never seen anyone with similar problem to yours (unable to start kernel)
did you give it some time? if it didnt work, try http://forum.xda-developers.com/showthread.php?t=2069723; it's similar to lgflashtool, but no need to set up ports, and you can track the progress while it's flashing (lParam=x on pictures). try 20a kdz file, if that fails, report here with some more info on what the problem was. hope we can fix things for you
also, can you post the link on tutorial you followed to flash cm, just so i can check what steps you have done? just remove http from the link if you cant post it
Flying_Bear said:
hmmm, truth to be told, i dont remember seeing that image appear when using lgflashtool. also, i've never seen anyone with similar problem to yours (unable to start kernel)
did you give it some time? if it didnt work, try http://forum.xda-developers.com/showthread.php?t=2069723; it's similar to lgflashtool, but no need to set up ports, and you can track the progress while it's flashing (lParam=x on pictures). try 20a kdz file, if that fails, report here with some more info on what the problem was. hope we can fix things for you
also, can you post the link on tutorial you followed to flash cm, just so i can check what steps you have done? just remove http from the link if you cant post it
Click to expand...
Click to collapse
It's working!
Just read your reply and as I wanted to wait to see what you might say I left the phone alone, so it was still attached to the pc showing that image.
I then unplugged it, held the power button down to power it down and then back on again, image of the android came up for a second showing as though it was updating, then the LG logo and then Setup started.
5 minutes later wifi and 3G were working and I was logged into Google.
So problem solved!
I'll hang back from updating further until I've read up more on XDA....thanks so much for your help though!
So I have a Sony Xperia Z1 C6902
And I've been messing around with ROMs, since I didn't know what exactly I wanted I've been installing a lot of different ROMs for about two-three days. I ended up using Slimroms as the ROM and RockZ1 as the kernel. I specifically used that version in particular since I wanted to use KitKat instead of Lolipop.
So after a while of using it, I found out it somehow became not rooted, and I couldn't install SuperSU properly (what with updating binaries and such) and this phone had a previous owner who had the bootloader unlocked and everything unlocked previously with this ROM
So I decided to try to root it using this method then when I went to flash C690X_14.4.A.0.108_KernelOnly.ftf as part of instructions, my phone ended up being stuck on a Blank Screen somehow?
The thing about the Blank Screen is that upon booting, the Sony screen shows up, and then nothing else. However, I can lock the phone, and when I unlock the Sony logo dissapears and I get a completely blank screen. I could touch certain areas and get some kind of feedback on what I assume is the PIN screen. So I just assumed that means the ROM isn't compatible with this kernel, so I flashed C690X_14.4.A.0.157_KernelOnly.ftf ahead of instruction since I couldn't normally access the phone to use Debugging because of the lock PIN.
On boot again, it still didn't show anything, so I just tried a Hard Factory Reset using the red button on the phone. That didn't resolve my problem whatsoever, but when I booted it again and touched the blank screen, I get Phone Dial noises?
Help?? The phone isn't bricked as far as I'm aware, since it can still boot and such, but I can't get into recovery to flash other roms or kernels, and I don't know what to do.
Update, I suppose. I tried the Sony PC Companion method, with repair phone/tablet, and it just gave me an error saying I have modified software and it didn't do anything about it.
Unecessary post, apologies
Unecessary post, apologies