Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.
Hi! I realise this if my first post I'd like to tread lightly; but I'm about 4 days into solving my issues and I just want to finish it...
I've had my Nexus i9020a (bought from Koodo) since ~May 2012. I upgraded to ICS sometime in the summer and sometime in the last few weeks it has started rebooting. I hadn't been installing new apps, etc. I'm not sure what the cause is. I 'Factory Reset' today in an attempt to resolve the issue, thinking it may be a program gone AWOL; but it has rebooted a few times since. I *just* looked through rebooting FAQ on this site and have edited the first few features listed there. I'm not sure if it has worked yet, but I'll get back to you on that. For the record, the only programs I have installed now are Swiftkey 3, Handcent and Beats (DDR simulator, updated in November).
In the meantime, before I found the solutions here, I decided to take another shot at unlocking the bootloader and try installing... probably CyanogenMod.
Specs: Windows 7 64 bit with Nexus S I9020a (Koodo) running 4.0.4 (4.1.1/2 OTA haven't come through, despite dozens of attempts at clearing the GSF cache, etc)
So I've been using the Nexus S: Full Update Guide found at:
hxxp://wiki.cyanogenmod.org/wiki/Nexus_S:_Full_Update_Guide
(It won't let me post the link)
I've followed the guide for installing the Android SDK, gone to CMD and typed 'adb devices' and had it show up. Theoretically, the SDK should be running fine.
Next, I turned on the USB debug mode. Then I booted up the bootloader, plugged the NS into the PC... and despite not having issue when the it's turned on (driver installed properly) windows says drivers have not been found for the device. Thus, when I type fastboot devices, it comes up with nothing.
I've been, and will continue perusing forums for this, but so far I haven't seen anyone with this specific problem.
Edit: I have also gone to the directory with fastboot/adb and used cmd to reboot into the bootloader, only to have windows 'ding ding ding' an unrecognised device.
2nd Edit.
I've gotten a stage further! I'll keep the thread open because I may come across something and it's nice to write my issues down. Seems my head can wrap around the problem a bit better. Anyway, I installed PDAnet and BAM, it works. Onto getting CWM installed! Thanks for the, uh, help!
3rd Edit.
CyanogenMod 10.0 stable is booting for the first time!! It's taking a while... but I appear to be on the home stretch! Also, my phone didn't reboot for a few hours before I installed CM. So if I don't end up somehow bricking it... and I mean, this first boot is taking a heck of a long time... The animation sets me at least a bit at ease... maybe 4.0.4 will work out...
Edit 4
I forgot to clear the app and cache data before flashing the ROM to the phone and thus the issue... after a VERY tension filled moment of pulling the battery during first boot... I rebooted, cleared said data and reflashed the ROM. After a boot, I realised I forgot the GAPPS zip and fixed that. Now I'm running CM10 Stable!! I'm stoked that after months of putting it off cuz last time I did it I didn't get anywhere after many days, but now it's done!! Thanks again for such an awesome site!
Thanks for sharing your experience instead of just saying "Mods please delete this i solved my own problem" :good:
My 959V is rooted, had plenty of roms,ect over the last 3 years decided to do Gremlin remover and update it...,
Couple days ago upgraded to the "909" download of CM11,4.4.4, but every site I get it from gives me 908 (even though they all say 909) (last 3 digits of download version). The 908 will not recognize on my Win 7 laptop, but was fine up to now with previous cm11 same phone..
I have used the same cable for the last year for both my Galaxy and 2 Sidekicks phones, data and charging, now the Galaxy only charges, Windows detects but wont recognize, does on the sk4g's
Also (908) will not allow me to paste into sys/media with a " read only issue", although up to now swapped 15 different bootani without problems. Tried 3 different root file managers,same outcome.
Is the driver for the phone firmware windows looks for(on the phone itself) replaceable from sdcard? Im guessing its a bootloader issue and the 908 is the one not to of put on my phone.
Whats the probability I am getting the 909 but the 908 will not allow it to surpass it. Goes through the whole flash and on reboot I have to reenter emails,playstore apps,ect, but on 908 still in settings.
I can/ have been able to swap 1 rom via twrp and sdcard on 908 ( to slimkat4.4.4 and back to 909, but comes up 908) any other roms error before flash(and slimkat does not recognize on usb either).
is it a Kernel fix, and can it be flashed via sdcard? Bootloader via sdcard? Bad usb port? Does charge, and the drivers/ cable verified.
Thank you for any help, been 3 days now, redone my laptops (2) from scratch, everything ,c++,java,netframework,samsung,zadig 2.0, and more.
DId you do a clean upgrade (did a factory reset) before you installed CM11? If you didn't, go into TWRP and do a full backup (/system, /data) and do a factory reset, then boot up the phone and see if your computer will recognize it.
FBis251 said:
DId you do a clean upgrade (did a factory reset) before you installed CM11? If you didn't, go into TWRP and do a full backup (/system, /data) and do a factory reset, then boot up the phone and see if your computer will recognize it.
Click to expand...
Click to collapse
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Floridasun said:
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Click to expand...
Click to collapse
I didnt do a backup, if thats an issue , can I backup 2nd motherboard and apply to the first?
Floridasun said:
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Click to expand...
Click to collapse
You can flash new kernels via recovery but it sounds like your issues are bigger than that. The fact that the 2nd motherboard is recognized via USB but not the 1st suggests that there's some kind of hardware issue. The drivers on your computer are working fine since the 2nd mobo is recognized, and so is your USB cable.
Why not just keep using your 2nd mobo? Is there something wrong with the 1st?
FBis251 said:
You can flash new kernels via recovery but it sounds like your issues are bigger than that. The fact that the 2nd motherboard is recognized via USB but not the 1st suggests that there's some kind of hardware issue. The drivers on your computer are working fine since the 2nd mobo is recognized, and so is your USB cable.
Why not just keep using your 2nd mobo? Is there something wrong with the 1st?
Click to expand...
Click to collapse
O.K., so Ive been playing with the second mobo just to test different angles.
1) E.S. File manager is the culprit, swapped out for a paid app Ive used with Sidekick 4g, Root Explorer, and boot ani. goes fine, on both mobos.
2) The latest gapps (cm 11 w/ gaps 4.4.x) was giving me a "Google servers cannot be reached" error on both mobos, used the gapps for cm 10.1 (jb 4.3) and all is working, both mobos.
3) Was reading that possibly the adb driver is in the kernel, and thats what windows is looking for? Ive tried but can only sd card flash at this point so, giving up. I can bluetooth,wifi share or email files to myself if need be. Im guessing its a hardware issue beings that the 2nd mobo was reflashed identical to to the first. (with exception of one click 2.3.6,and w/a twist oc/uv on the 2nd),1st one will not downgrade at all below 4.4.4 by sd, I was trying to ics a rom guessing the foundation might overwrite any missing stuff then upgrade back to 4.4.4.
One post mentioned that the mtd/bml cross flash is a no-no, could that mess up usb driver identity on the phones side?
Not a big deal, both phones/ roms are working great and have no issues (except 1 doesnt connect to a computer for file transfer). Thank you for your help.
Little early to ask but are you going to be in this forum long enough for lollipop to be ported? I would send you this phone for devving if you think you can get it to transfer files. Also need to get a lcd/digitizer, i have the rest of the phone.
Also, the phone was working fine up to about a month ago, it was recognized by the computer, only difference I made was trying apps, off playstore, five fingers for ebay,different weather apps for widgets,silver/gold prices apps. Thats when it started not recognizing.
I was getting the same error about the google servers, then I tried a earlier version of gapps. Connects now.
Floridasun said:
Little early to ask but are you going to be in this forum long enough for lollipop to be ported? I would send you this phone for devving if you think you can get it to transfer files. Also need to get a lcd/digitizer, i have the rest of the phone.
Click to expand...
Click to collapse
I have no plans to try a Lollipop port, this phone is almost 4 years old now. You might be better off sending the phone to @bhundven since I recently got two dev phones donated to me.
As far as the phone itself goes, the phone should be recognized even if there is no driver for it installed on your computer. You can use this software to verify that
http://www.nirsoft.net/utils/usb_devices_view.html
I don't believe you can even edit anything on the phone to make the USB device not be recognized when plugged in short of bricking your phone, so if there isn't even a USB connection being made, as I mentioned before, it looks like a hardware issue is causing your problems.
In that case, it'll be hard to flash anything without going through a lot of hassle since all the reliable recovery methods we have need that you are able to use your USB port on the phone.
EDIT
If you do still have TWRP available on the phone, flashing any ROM will reflash a kernel, but be careful because the recovery is tied to the kernel and some ROMs have a non-working recovery, so if you happen to flash some of these you'll be stuck with a nice paperweight . The latest CM11 I have posted does have a working kernel/recovery but I still don't think it'll fix your issue.
FBis251 said:
I have no plans to try a Lollipop port, this phone is almost 4 years old now. You might be better off sending the phone to @bhundven since I recently got two dev phones donated to me.
Click to expand...
Click to collapse
I'm currently looking into it, as well as fixing some issues with cm11. I have an SGS4G, so no need to send a phone.
Not just is it a 4 year old phone, but I am not sure how many people even use this as a daily driver anymore.
bhundven said:
I'm currently looking into it, as well as fixing some issues with cm11. I have an SGS4G, so no need to send a phone.
Not just is it a 4 year old phone, but I am not sure how many people even use this as a daily driver anymore.
Click to expand...
Click to collapse
I still use two of them. Great little phones really. I see no need or use for 5.0 I think running this CM11 from you guys is about the end of the road for these phones. A great ride indeed. Ill be sticking around regardless just to see what happens. Thanks guys☺
Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
QuesteU said:
Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried any of the CM based roms from xda ? You may only need to update your recovery. Both of these should work on your device
https://forum.xda-developers.com/ga...0-1r61-rom-resurrection-remix-v5-7-3-t3449444
https://forum.xda-developers.com/ga...m-unofficial-lineageos-14-1-gt-n51xx-t3533329
Latest twrp
https://forum.xda-developers.com/galaxy-note-8-0/development/recovery-twrp-2-8-5-0-t3035004
Good Luck
Sawdoctor
Hey there!
Just ran into some troubles with my GT-N8010. I had been using stock on it for quite awhile, but have been noticing that many of the newer apps do not work with JB. I had rooted and used my Asus Transformer before, figured that it was probably about time to get some more life out of the Note 10.1.
My first option was to upgrade from JB to KitKat. Unfortunately there is not an official update in Canada, but using Odin I should have been able to upgrade it. This is where the issues came. First, it failed twice. I restarted the computer, and tried it once more. Success! It was downloading. It took a few moments, but eventually it failed as well. The download stopped and I was left looking at my tablet having 3/4 of the install complete. I left it for awhile, hoping that it would restart itself or reload. Nothing happened, and I had to restart the tablet.
Situation now: I am stuck at the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
First thing I tried was getting to the download screen, so I have that. I figured I could just flash it back to the offical JB from Canada, but now it's like the computer won't recognize the device. Even unplugging and plugging the USB back in does not even give me the PC Recognizing sound. I moved to a laptop, and it could read the device, but once I installed Samsung USB and Keis, it stopped. Odin doesn't recognize it and I am not sure where to go from here.
Is using the SD card an option? Can I somehow force the computer to read the tablet?
I have looked through the forums, but didn't really see much in the way of help.
I hope to hear from you guys! Thanks in advanced! If I need to provide more information, please ask.
Is using the SD card an option>>> NOT for stock custom rom only .
I don't mind installing a custom rom at this point. If it is still an option at this point the I don't mind at all. If there is anyway you could point me towards that option, I will definitely give it a shot.
The development threads.
You will need to flash a custom recovery tar through Odin .
https://forum.xda-developers.com/showthread.php?t=2490954
Part of the problem is that the Odin, even my PC, are not recognizing the the Tablet is connected through my USB. So I cannot flash anything right now.
I figured it out. It was all because of my cord. I went out and got a new one, flashed 4.4.2 easily. Hope that helps everyone who has issues as I did.
elevenstewart said:
I figured it out. It was all because of my cord. I went out and got a new one, flashed 4.4.2 easily. Hope that helps everyone who has issues as I did.
Click to expand...
Click to collapse
Hi, I've read your posts. Helpful.
I'm in the situation of having tried to flash a custom recovery, to then flash a custom ROM.
Started Odin, began to flash, then Odin showed failed.
Now the n8000 no longer starts, just hangs after the Samsung logo/music.
I do have two different cords, so will try that later.
Question, did you end up flashing a custom ROM later, and if so, which one?
Thanks.
Sent from my SM-N920C using Tapatalk
I have a Samsung Galaxy GT-N8010 (UK version), Android 4.1..2 - i need to get this up to KitKat 4.4.2 as BT Sport app won't run on below v4 - help?
Search this forum its well answered.
Or
Sammobile.
Updato.
Two firmware site