Develop Bugs

Bootlooping Galaxy Nexus

I've done about 3 hours of research on this forum and the internet in general, and I can't seem to find a situation like the one I'm in. I'm not particularly savvy at all of this, but have successfully rooted a few phones and have played with a variety of ROMs for both tablet and phone. I have the Android SDK installed, the drivers for my phone installed on my computer, PDANet, the works. I'm on a Windows 7 laptop.
I had a new JRO03L ROM build for my verizon GNex flashed, and was getting quicker than expected battery drain. So I decided to flash a custom kernel. I must have flashed the incorrect version of this kernel.
When I rebooted after flashing the kernel in CWM, it went into a bootloop on the Google screen. I waited an hour, pulled the battery and tried to boot into hboot (volume down+power button). Lo and behold, I can't get back into CWM! I have no option to enter recovery, I'm only able to start the boot process.
So I plug it into my computer, hoping that I might be able to use the GNex Toolkit (v7.8) to restore to stock and start over, or even just try to use fastboot to ... do something - anything! - and my computer doesn't recognize my phone when in hboot. When in hboot, my device manager recognizes the phone as "SAMSUNG Mobile USB CDC Composite Device" and as a modem. When I start the boot process and it is bootlooping, my computer recognizes it as my phone, but can't install the drivers properly.
Any help would be greatly appreciated, even if you can get me back to stock. I have a nandroid backup on my SDCard; I just need to be able to get to it and flash it. I would be forever in your debt if you can help me out! Thank you in advance!

rs18 said:
I've done about 3 hours of research on this forum and the internet in general, and I can't seem to find a situation like the one I'm in. I'm not particularly savvy at all of this, but have successfully rooted a few phones and have played with a variety of ROMs for both tablet and phone. I have the Android SDK installed, the drivers for my phone installed on my computer, PDANet, the works. I'm on a Windows 7 laptop.
I had a new JRO03L ROM build for my verizon GNex flashed, and was getting quicker than expected battery drain. So I decided to flash a custom kernel. I must have flashed the incorrect version of this kernel.
When I rebooted after flashing the kernel in CWM, it went into a bootloop on the Google screen. I waited an hour, pulled the battery and tried to boot into hboot (volume down+power button). Lo and behold, I can't get back into CWM! I have no option to enter recovery, I'm only able to start the boot process.
So I plug it into my computer, hoping that I might be able to use the GNex Toolkit (v7.8) to restore to stock and start over, or even just try to use fastboot to ... do something - anything! - and my computer doesn't recognize my phone when in hboot. When in hboot, my device manager recognizes the phone as "SAMSUNG Mobile USB CDC Composite Device" and as a modem. When I start the boot process and it is bootlooping, my computer recognizes it as my phone, but can't install the drivers properly.
Any help would be greatly appreciated, even if you can get me back to stock. I have a nandroid backup on my SDCard; I just need to be able to get to it and flash it. I would be forever in your debt if you can help me out! Thank you in advance!
Click to expand...
Click to collapse
Post three of my guide.
Push another rom.zip to your phone and flash it (if you don't already have one there).
If you have one...You're not getting into the correct menu.
You're in ODIN.
Bootloader/Recovery is BOTH volume buttons.

Jubakuba said:
Post three of my guide.
Push another rom.zip to your phone and flash it (if you don't already have one there).
If you have one...You're not getting into the correct menu.
You're in ODIN.
Bootloader/Recovery is BOTH volume buttons.
Click to expand...
Click to collapse
Thank you. I'm an idiot. It's been a long while since I've put this into recovery via physical buttons.
By the way, your guide is excellent. How have I not stumbled across this?

[Q] Stuck in Bootloop

Hello,
I was recently attempting to flash the new Cyanogenmod 10 ROM to my phone and I've found myself in a bootloop (the logo just continuously circles). I actually know what error I made to cause this, but the problem is, I have no access to any recovery menus anymore. All I can access is download mode. I can still use Odin and connect to the phone, but other than that I'm at a loss for what to do. I have backups of everything, I just need to get the phone wiped and back to factory set and start over. Unfortunately, without a recovery menu I don't know what to do.
What should I do from here?

Solved it.
For anyone that has this issue in the future, I plugged into the computer and ran Odin and was able to have it install a stock ICS ROM and I just started over.

Good job with solving the issue on your own! :good:
Your issue and solution had been discussed on these forums already. As a tip for the next time you have an issue, make sure to use the search bar first. Cheers!

Help! stuck at Samsung logo, can't get into recovery

Hi, I'm having trouble booting after flashing the stock jelly bean rom 4.3 from tmobile. Right now it is just stuck on the Samsung logo. The problem may have been that I had installed the slimkat Kitkat rom and tried to go back to stock tmobile rom which was jelly bean. (stupid I know)
The second problem is that my volume up button is broken so I can't hold it long enough to boot into recovery. I am able to get into download mode and use odin if I get lucky and struggle with the up button but it only works in short bursts as it's damaged on the actual board and not the rocker.
Is there any other way I can get into recovery? I can't boot into the os so rebooting from there is out of the question. I'm running out of ideas now.
any suggestions would be greatly appreciated.

Flashing stock was fine. Your roms version doesnt matter, its your base firnware that does. Whenever you go between tw and non-tw roms you have to factory reset or itll hang at boot, which is what is happening to you.
Since you flashed stock, i dont know if itll work or not, but if ADB is set up on your computer, connect while in download mode, open command prompt and type
Adb devices
This will start the service and tell you if its detected.
Next type
Adb reboot recovery
If thats not going to work, youre going to need to find a way to make an odin flashable cm rom (not sure if you can), or get the the volume button fixed.
I dont know of any other way to boot recovery if you cant boot your rom as well.

DocHoliday77 said:
Flashing stock was fine. Your roms version doesnt matter, its your base firnware that does. Whenever you go between tw and non-tw roms you have to factory reset or itll hang at boot, which is what is happening to you.
Since you flashed stock, i dont know if itll work or not, but if ADB is set up on your computer, connect while in download mode, open command prompt and type
Adb devices
This will start the service and tell you if its detected.
Next type
Adb reboot recovery
If thats not going to work, youre going to need to find a way to make an odin flashable cm rom (not sure if you can), or get the the volume button fixed.
I dont know of any other way to boot recovery if you cant boot your rom as well.
Click to expand...
Click to collapse
Thanks for the reply, I do have ADB set up but unfortunately when running the command on adb it's not finding any devices. Odin finds it ok. I also have the android toolkit but it looks like it only works if the phone boots into the os..

Well I got it working now. Playing with a piece of tin foil around the volume up button finally let me hold it long enough to get into recovery. Wiping the cache got it all working properly again. thanks again.

Nice fix man!
As for adb, I figured it wouldn't work, but was worth a shot in case I was wrong. Pretty sure that it requires an insecure kernel since it didnt work though.
And just remember in the future, every time you switch between TWO and nonTW roms you have to factory reset. Glad you got it working!

Did I brick my SM-T900 by rooting from Virtualbox?

Hello,
I just bought a Samsung Galaxy Tab Pro 12.2 (sm-t900). It's my first Android device.
I don't know what I was thinking, but I tried to root it from Windows 7 installed in Virtualbox.
My host OS is Linux.
Now the tablet is stuck at splash screen - it's looping from SM-T900 to Samsung.
I can still power it down to download mode though.
I used this tutorial - http://forum.xda-developers.com/gal...-how-to-root-install-custom-recovery-t3087451.
What I did was (in Virutalbox):
1. Installed Samsung drivers.
2. Downloaded CF-Auto-Root-v2wifi-v2wifixx-smt900.zip.
3. Run Odin.
4. Powered off the tablet into download mode and Attached it to Virtualbox.
5. Selected zip in Odin via PDA and clicked start.
6. It looked like everything went ok, but it was here where tablet tablet was reset.​And I think, it's also here, when things went bad, because tablet was detached from Virtualbox.
And my guess is that Odin couldn't finish flashing.
Or maybe it did, because flashing instructions that was displayed on tablet looked ok.
After 10 seconds it was reset.
And splash screen loop started.
Odin did show "PASS" though, but I don't know how was that possible, since the tablet was detached from Virtualbox.
I can still turn the downloading mode on.
Is there any help or is it trashed?
It serves me right I guess.

as long as you can access download mode it should be re-flashable, also first boot might take awhile (1-5 minutes) after flashing the firmware.
you can try samsung kies 3 if odin gave you problems.
no idea if virtualbox will cause problems, but I would flash from a real windows pc... to avoid problems like this

Hello,
Just to be sure - I only tried to root the tablet.
I have not flashed custom recovery or custom ROM.
And Android version on the tablet is 5.1.1, if I remember correctly from briefly skimming through system settings (before rooting).
To be honest, I am a little bit afraid to do anything now.
However, I have been testing some possibilities and here is what I was able to do:
1. I can go into download mode by pressing power+volume down+home.
2. I can go into recovery (stock, no twrp) by pressing power+volume up+home.
3. While in download mode, Odin says Added.
4. After pressing power for ~ 10 seconds, this information appears:​
SDCARD MODE
UP KEY: NORMAL BOOTING
DOWN KEY: DOWNLOAD MODE
But there is no effect after pressing up or down key.​
So I don't know if I should now:
Try rooting again (no virtualbox of course this time)?
Factory reset? Would it work after aforementioned rooting attempt?
Try flashing stock rom?
Unroot?​If anyone knows what is the best action to take now, I would much appreciate it.

I tried wipe data/factory reset (power+volume up+home) - no effect.
I also tried rooting again and this time on real Windows PC (rooting passed) - no effect.
So after sifting through the forums, my understanding is, that the rooting process at http://forum.xda-developers.com/gal...-how-to-root-install-custom-recovery-t3087451 is for Android 4.x.x.
And since the tablet I bought had 5.1.1, that is the reason it can not now boot.
I will try now recovering to stock ROM (Android 4.x.x).
I just don't know which country the tablet is from.
But after reading similar threads, it seems it is possible to install any official stock ROM.
Just which one to pick?

So I installed stock ROM with Android 4.4.2.
After that rooting worked as expected.
Then I installed TWRP recovery and CM 12.

Note 3 Stuck on Tmobile Splash Screen - How to recover without losing data?

I have a galaxy note 3 which is stuck on the Tmobile splash screen.
I am not sure if this phone is rooted or not.
I don't want to wipe the phone because there is contacts and things which need to be recovered.
We can get into recovery mode, but not into Safe mode.
Can someone provide some tips?

If your contacts are synced with a Google account, they should appear if you sign in on another phone.
Flashing a ROM to a phone will carry risks; therefore, no matter what you do, you may wind up losing all of the data. That being said, you could try reflashing the stock ROM with Odin and it may boot without wiping.
You could also flash TWRP to the phone, boot into TWRP, mount the data partition, connect it to a computer, and copy off the data. Alternatively, you could try and copy information from the phone to a micro SD card in TWRP.

Did you fix your issue? I had this problem when....
Flash Fix said:
I have a galaxy note 3 which is stuck on the Tmobile splash screen.
I am not sure if this phone is rooted or not.
I don't want to wipe the phone because there is contacts and things which need to be recovered.
We can get into recovery mode, but not into Safe mode.
Can someone provide some tips?
Click to expand...
Click to collapse
I hope you have fixed your issue by now however if not then please try this.
1. Remove your battery from the phone
2. Hold your phone (volume down button + home button) then slide the battery in and power the phone. *Note you must hold the (volume down button + home button) until you get the warning about installing custom OS.
+Once you reach Warning OS page, at this point Oden should see your phone so you can download a custom recovery like CWM / TWRP
3. Download (Oden + Device Drivers & TWRP) --- I just found out that I need to post 10 times before I can link to outside files so I hope you get the links. If not then PM me and I will try to send directly to you.
HTML:
https://download.chainfire.eu/354/CF-Root/CF-Auto-Root/CF-Auto-Root-hltetmo-hltetmo-smn900t.zip
CF-Auto-Root which includes your phones correct Oden version
https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar"]TWRP.
4. Extract the CF-Root folder you downloaded using 7zip and you will see Oden. Install Oden on your PC.
5. Connect your phone to your computer and look for a so your connected to Oden and then flash TWRP .tar file to your phone. Once it flashes then your phone should reboot automatically and you should have access to your old data.
This happen to my Note 3 T-Mobile phone when I was trying to flash the wrong versions. If you are confused about the directions then I will do my best to make a video for you. It might take me a day or two to respond with the video. Hope this helps! Let me know how it works out or if you have any questions.
Also, once you gain access to your phone again I recommend taking a look at some of the ROM's on this website! There are some developers who have put quality time into making their ROM's SOLID working systems.
Always remember to give support as this is what makes this community attract real talent!

I do not recommend CWM as it is very outdated.
Rooting is not required to flash TWRP, only Odin and the tar version of TWRP.
The phone can be rooted by flashing supersu from TWRP too.