I am new to the whole flashing thing. I read a number of guides last night and was finally ready to do it. I downloaded Odin 1.82, had my drivers installed from this thread (Or so I thought) and tried to flash. In Odin, it hangs at "Setupconnection". I couldn't figure out what the problem was and then I noticed when I plug in my Droid Charge, this is what I get...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Odin detects my phone, and I'm able to access the SD card on it from my PC, but like I said it doesn't flash...and I assume that's because of not every driver having been installed. How can I resolve this issue? I'm using the drivers that this site and a number of other sources say to use. I've tried uninstalling and reinstalling them, different cables and different PCs, as well as different versions of Odin.
What confuses me is what I'm reading says to boot into Download Mode with the battery out. How am I supposed to do this when it's not plugged in and no battery? Also, is my phone supposed to stay on when plugged in and the battery is out? Because mine keeps turning off when the battery comes out.
OrbitzXT said:
What confuses me is what I'm reading says to boot into Download Mode with the battery out. How am I supposed to do this when it's not plugged in and no battery? Also, is my phone supposed to stay on when plugged in and the battery is out? Because mine keeps turning off when the battery comes out.
Click to expand...
Click to collapse
Pull the battery, hold VolDown and plug in USB. When the phone is recognized, put the battery back in.
shrike1978 said:
Pull the battery, hold VolDown and plug in USB. When the phone is recognized, put the battery back in.
Click to expand...
Click to collapse
I feel like an idiot. It's working now, thanks a ton. I think I was in recovery mode. I flashed CWM and am now planning to flash Tweak using Odin. What exactly is CWM and how do I use it if I need to? My understanding was that it's a recovery tool. Also for Tweak, I notice one download has a kernel and one doesn't. As a noob, what do these things mean and which should I go with?
After you Odin the rom and cwm, you want to boot into cwm and flash a custom Kernal before you allow the phone to reboot, otherwise the stock Kernal will overwrite CwM with the original recovery... Unless you odin the package that has the Kernal in which case CwM would stick.
FYI - CWM should stick on either of the tweakstock Odin files
dwitherell said:
FYI - CWM should stick on either of the tweakstock Odin files
Click to expand...
Click to collapse
Sorry about that. I didn't mean to give bad info. You have me curious now... Is there something in the process that stops the Kernal from overwriting the recovery?
Adamsaudio said:
Sorry about that. I didn't mean to give bad info. You have me curious now... Is there something in the process that stops the Kernal from overwriting the recovery?
Click to expand...
Click to collapse
No worries - there's an install-recovery.sh script in /system/media/ that - when removed - leaves CWM alone.
Related
Okay, so today I bought a Droid 2 global from a guy from the Cricket Store here in town. I get home and try to program my phone, little did I know that the Droid had been flashed to Cricket, so I go back to the store and get the guy to flash it back to Verizon. He gets the guy to flash it back and he messes it up, then finally he got it flashed back to verizon. I get the phone programed to be on my account, and then when it boots up and asks me to log into my Google Account, now 3G connection is not working. So I called up Verizon thinking maybe they could help me. I spent about an hour on the phone with them and they said it must be a Device defect. So there goes an hour of my time wasted. Anyways, I root the phone using z4root thinking maybe if I load a custom rom on it it will fix my problem. I installed Clockwork and flashed over to CWM and use the Droid Bootstrap to boot into CWM. I execute the Fission Rom Image and it successfully installs. However, when it boots up it hits the boot loader that says "Android" and stays there. I know from previous experience that sometimes it can hang on this screen, so I let it sit for 20 minutes. Still nothing. So I decide to download Monsters Gingerbread Rom and I flash to it. It goes through its process and fails at Installing Radio something. However, I notice that it has flashed the system and the bootloader. So I am like **** I bet it's bricked. I restart the phone and it goes Straight in to the Bootloader screen. So I load up RSD Lite and plug in my phone and it recognizes it. But the name is weird. Here is a screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before using RSD Lite the phone screen says:
Bootloader
D0.11
Err:A5,69,35,00,3D
Batery OK
OK to Program
Connect USB
Data Cable
So I select the 2.3.20 SBF file and try to flash it over. It fails and the phone screen says:
Critical Error
FEBE
0047
The RSD Lite program throws me the Error:
Failed flashing process. Phone[0000]: Error sending JUMP command Device API Error: 0xE0020047 Address: 0x820000000 Command: JUMP (0xE522047); Phone Connected
Is there anything I can do? Or is the phone COMPLETELY Bricked?
I feel like I have turned my Droid Global into an Expensive Paper Weight
----------------
EDIT
----------------
I successfully restored it using a Different SBF. Appears that Error Code 0047 means incompatible SBF.
Anything I can do to fix the 3G issue? I don't know what could be causing it.
----------------
EDIT
----------------
Successfully flashed over Monster Gingerbread. 3G is now working.
Thanks for letting me post this long shpeal, it made me think of things to test and eventually unbricking the phone
You have gingerbread? How'd you do that? I've heard from everyone who's tried it fails..
Sent from my DROID2 GLOBAL using Tapatalk
From what i can tell from his sig, he has three droid phones, the Droid 2 has had a gingerbread leak for awhile. His Global is on Fission 2.4.3, like mine.
Which SBF u used?
I'm having the exact same problem now, I hate it, tried to install to leaked gingerbread rom, but got my phone bricked, dammit!
I already have VRZ A955 2.3.20 1FF SBF file, rsd lite 4.9 and updated drivers, and got the exact same problem, same messages....everything.
Reading first post, saw that u used a different SBF, which one? where did u get it?
plz help, h8 having an awesome bricked phone.
Check my post in this forum:
http://forum.xda-developers.com/showthread.php?t=1060694
Hello all. With 9.2.1.17 I rooted using vipermod (http://forum.xda-developers.com/showthread.php?p=21009605) and kept the root with OTArootkeeper. Everything works fine except I no longer seem to have a recovery mode. I have Clockwork mod, which I installed after rooting and it was working fine until the recent eee pad update to 9.2.1.21. Now, if I try to reboot to recovery I get the green android... then he dies.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have searched the forums and google and while I've found plenty of interesting methods, none of them seem to bypass this issue. CWM will not reboot - the reboot is completely skipped. I used to use an app called Reboot2Recovery and that just gives me that above image.
-That image btw will stick around for a few minutes and then the tablet will reboot itself if left alone.
Some other info: I don't have any mods. I only rooted to be able to use TitaniumBackup. I have tried doing a factory wipe of the tablet but even afterwards, still no recovery possible.
I appreciate any help! I would like to unroot my tablet and just start all over. I have nothing to lose.
Use RecoveryInstaller to install CWM again.
Seems like you lost CWM, what you see now is the stock recovery
Thank you! I feel so stupid that I didn't find that on my own. I tried reinstalling CWM using the adb push and was getting nowhere (I'm not exactly an android guru).
It's working like normal now, but I'm wondering if I unroot now and uninstall CWM will I still be unable to get to the recovery mode? I ask because I am thinking of sending my tablet back to Asus because it won't stop rebooting. I get the feeling that if I can't get the stock recovery to work they won't work on it...
If you flash an official stock rom from asus you'll also have the stock recovery back. But sending it back to asus most likely won't fix your reboot problems as a lot of people reported having them. It seems to be a bug of the ICS firmware.
I'm on rooted 9.2.1.17 and was having sleep of death and reboot issues. Since I flashed ICS kernel 16b I've had no problems. My system has been over 10 days with no reboots. It's worth a try. You can always flash back to ASUS stock from recovery.
I have a Verizon HTC One M8 that can still power on, but will only go to the black screen with an HTC logo in the center and a triangle with an exclamation mark in each of the four corners. This happened while returning my phone to stock. My computer disconnected from the phone half-way through pushing an RUU flash. The cable wasn't unplugged, the computer just made the disconnect sound and the flash stopped. The phone is not recognized as an adb device, but it is recognized as a fastboot device. This gives me some hope that the phone can be recovered, but any attempt to flash an RUU gives me the error: cannot load "file-name". Any suggestions?
Just to help out anybody trying to figure this out:
The phone will not enter recovery
The phone enters something akin to the recovery page if I disconnect it from the PC, but the only option is RUU and pressing the power button will not do anything (picture attached)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once you see the triangle you hold volume up then tap power. Try rebooting your PC, pushing that file takes some ram and a reboot will fix it, also try using the adb and fastboot files from dottats s-on ruu thread. Its in the first post i believe and modify your commands to look like this "HTC_fastboot oem rebootRUU" (without the quotes) ect.........itll help the ram issue. Thanks @dottat for showing me this. Try that and report back.
MotoTurbo said:
Once you see the triangle you hold volume up then tap power. Try rebooting your PC, pushing that file takes some ram and a reboot will fix it, also try using the adb and fastboot files from dottats s-on ruu thread. Its in the first post i believe and modify your commands to look like this "HTC_fastboot oem rebootRUU" (without the quotes) ect.........itll help the ram issue. Thanks @dottat for showing me this. Try that and report back.
Click to expand...
Click to collapse
Interesting, I didn't even know there was a version of adb specifically for HTC phones, though, I actually did this to my phone before that thread was ever made (never got around to trying to fix it until now). I'm at work right now, but I'll try it when I get home and update, thanks for the tip!
curb42 said:
Interesting, I didn't even know there was a version of adb specifically for HTC phones, though, I actually did this to my phone before that thread was ever made (never got around to trying to fix it until now). I'm at work right now, but I'll try it when I get home and update, thanks for the tip!
Click to expand...
Click to collapse
And if you run into any issues hit me up... i can help you out remotely.
dottat said:
And if you run into any issues hit me up... i can help you out remotely.
Click to expand...
Click to collapse
Just got home and ran the RUU with the HTC fastboot and it worked! At least I'm assuming so, I'm at the Verizon splash screen right now. Thanks so much for your help guys (and to HTC)!
Funnily enough, the soft brick worked out for me. If I hadn't bricked it I would have sold it months ago. I'm on a Droid Turbo now and I think I like the M8 better. So thanks again and I'll update if for whatever reason it's still messed up.
curb42 said:
Just got home and ran the RUU with the HTC fastboot and it worked! At least I'm assuming so, I'm at the Verizon splash screen right now. Thanks so much for your help guys (and to HTC)!
Funnily enough, the soft brick worked out for me. If I hadn't bricked it I would have sold it months ago. I'm on a Droid Turbo now and I think I like the M8 better. So thanks again and I'll update if for whatever reason it's still messed up.
Click to expand...
Click to collapse
Awesome man, glad you got it working. Also you can try a factory reset after ruu if you've flashed a bunch of Roms and have iffy data
Hi,
A few days ago I tried to update my SM-P900 tablet after 3 or more years without updating. I tried to flash this ROM (https://forum.xda-developers.com/ga...7-1-xsm-p900-unofficial-cyanogenmod-t3524788/), but it didn't boot. I flashed the recommended bootloader and recovery with Odin, but I'was not able to boot. Somehow, neither booted Lineage 13 (https://forum.xda-developers.com/ga...t/rom-cyanogenmod-13-0-android-6-0-1-t3366834) nor Resurrection (https://forum.xda-developers.com/ga...lopment/rom-resurrection-remix-5-8-2-t3563635). The only ROM I managed to get working is CM 12 (https://forum.xda-developers.com/ga...t/rom-cyanogenmod-12-lollipop-5-0-1-t2971945/). I thought that the problem was the bootloader, and someone suggested that I flash a more recent (at least lollypop) bootloader. According to Phone INFO, my bootloader version was P900XXUANI1. I tried again and again to flash the BL_P900XXU0BPA1.tar.md5 file, but, despite Odin showing the PASS! message, Phone INFO kept showing the same bootloader version. After that someone recommended that I flash the most recent stock image, so that I get a recent bootloader, that is what I tried to do.
I downloaded the file Samsung_SM-P900_(P900XXS0BPL2_P900OXE0BOI1_Russia_v5.0.2)_by_ (FirmwareOS.com) from a sammobile kind of site. What I look for is that ...BPL2 version that seems to work for other people. But after flashing it, the tablet doesn't boot and I can't access download mode. The only thing that i get to boot is the stock recovery, but it doesn't have the flash img option nor the reboot in Download mode that TWRP had. The only options I got are "Update from external storage" and "Update from ADB". Either of them don't let me flash a full factory image nor, apparently, another bootloader or custom recovery. When I try to flash it I get "E: footer is wrong \n E: signature verification failed" and if I do it via ADB, the error shows right away after a 0% transfer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: Other symptoms I found are:
- I can't manage to power off the tablet using just the buttons: it always reboots unless I select the Power off option in the recovery. Also if the tablet is connected by USB to the charger or the computer it always try to boot.
- When the tablet is connected via USB and I try to power it off, the tablet reboots and shows a battery symbol, but is gray and kinda strange.
I'm pretty desperate now. This is my wife's tablet and I tried to update it so that it was more secure. I'm screwed.
Any ideas? Is this fixable?
Thanks in advance.
Regards.
Did you try to download the stock rom which consists of several parts with the samfirm software?
For that you have to check the binary box in SamFirm and to insert device type and region.
Flashing that might work better.
I forgot to update the thread. I managed to fixed the tablet. It turns out the tablet hadn't enought battery to enter download mode and I was messing up with the Vol Up and Vol Down buttons. Really embarrasing. Hahaha. After fully charging the device and pressing down the proper buttons, I managed to enter in Download mode and flash a new image.
Hi all, hope ur doing well
I recently rooted my Tab S3 with the help of TWRP and Magisk
All was well and there were no mishaps or errors. One day I decided i did not want it to be rooted so i flashed the official firmware from the SamMobile website.
Ever since then it has been boot looping, even after multiple flash attempts with varying version of Odin and the official firmware
I will try give as much info on the steps i took in order to help you help me.... if that makes sense
1. I downloaded the firmware from SamMobile and downloaded Odin v1.13.1
2. I selected the BL, AP, CP and CSC files respectively for flashing
3. I flashed the firmware successfully
4. Auto-reboot continued
5. Rebooted into recovery
6. Android Logo appeared and text said "Installing Software Updates"
7. Text changed to "Erasing"
8. The tablet rebooted again showing this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
9. After which the boot loop started (showing black screen and above image.... never showing SAMSUNG logo)
After some googling i found that this is sometimes an issue and a quick way to solve it is to boot into recovery and WIPE CACHE and WIPE DATA/FACTORY RESET
I did this but with no success.
After booting into recovery mode i noticed some interesting text at the bottom of the screen
(Apologies for the poor quality)
Not sure why the dm-verity verification failed but it prevented me from trying other methods such as updating via SD card or ADB.
So I thought let me try installing TWRP again and see if i can do anything from there.
So i booted into download mode and flashed TWRP.... only for it to fail and display this message
"Only official released binaries are allowed to be flashed"
Great. Just another quick google search and it suggests that the official firmware is to be flashed before continuing
so i did it ... again (steps 1-9)
and i am stuck where i started this quest, in a boot loop never getting passed the Galaxy Tab S3 screen
If you know what else i can try or what could be the issue, or even a mistake i made that i was unaware of ... please leave a comment
i appreciate any and all help
Thank you for ur time and sorry for the long post
Much love
justanotherdumbuser <3
I'm taking a long shot here, I don't have Odin in front of me but if I remember correctly, you must uncheck "auto reboot" in the options tab
Raffles727 said:
I'm taking a long shot here, I don't have Odin in front of me but if I remember correctly, you must uncheck "auto reboot" in the options tab
Click to expand...
Click to collapse
hi @Raffles727
thanks for your advice, I have attempted it with "auto reboot" disabled
but as soon as I leave the download screen by holding the power + vol down + home buttons it repeats the same process from step 5-9 without any intervention from me
did I miss something or did I do it correctly?