Hi All, I'm hoping someone can help me out here.
My Note 4 ATT (N910a) was running stock 5.1.1 which it got from an OTA update. Yesterday the battery died and it went into a boot loop with the Samsung logo. I could still get to the system recovery and also download mode, so I figured all was fine. Of note, the recovery mode at this point had a message stating "dm-verity verification failed." I went ahead and flashed the 5.1.1 firmware found here: http://forum.xda-developers.com/note-4-att/general/note-4-att-5-1-1-odin-files-progress-t3230993 .
I used Odin 3.10 and got a PASS. However, the phone then booted into recovery mode and messages at the bottom are as follows:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Does anyone have an idea I can try? I've attempted multiple flashes with Odin with no success. Any help is greatly appreciated! Cheers.
Update: with the phone powered off and plugged in I only see the battery with a lightning bolt. It will not show charge progress even when left plugged in all day. Does this sound like a hardware problem?
Clear your caches and factory reset from the recovery menu
floatingtrees said:
Clear your caches and factory reset from the recovery menu
Click to expand...
Click to collapse
Just tried this. No errors but it results in the boot loop at samsung logo afterward.
I think ur flash is not successful. Boot into download mode and reflash ur files with odin again. Report back.
xateeq said:
I think ur flash is not successful. Boot into download mode and reflash ur files with odin again. Report back.
Click to expand...
Click to collapse
I just tried again using a different PC and re-downloading the firmware. Same issue rebooting into recovery and then boot loop again.
Update: with the phone powered off and plugged in I only see the battery with a lightning bolt. It will not show charge progress even when left plugged in all day. Does this sound like a hardware problem?
I read somewhere that u need original cable for flashing via odin. I myself used 8 years old nokis cable with success but give it another shot by changing cable. About battery issue, charge phone via wall charger. Some times phone is hanged and using much more power as compared to what it is receiving from standard pc connection.
xateeq said:
I read somewhere that u need original cable for flashing via odin. I myself used 8 years old nokis cable with success but give it another shot by changing cable. About battery issue, charge phone via wall charger. Some times phone is hanged and using much more power as compared to what it is receiving from standard pc connection.
Click to expand...
Click to collapse
Ok, so I re-flashed this morning with stock cable and unfortunately still have the same error messages and boot loop
When I leave the phone plugged in trying to boot it does get quite hot as it cycles through the boot loop. If I leave it plugged in and off the phone shows no sign of charge but does not get warm at all. This was also attempted with the stock wall charger and cable. Seems like I have a nice paperweight for the time being..
Related
hey there!
Ok so I got this problem. My phone felt to the floor like 2 weeks ago and the screen got crashed, everything else works normally, touch is ok, screen is ok, just glass is broken, after 2 days I downloaded some dota apps and it suddenly started rebooting and crashing:
By this I mean, apps stopped working and lots of pop-up messages appeared, after some reboots It stopped turning on, so I decided to root it and installed a custom ROM the one from mike, Android Revolution, this was last week, this weekend it worked fine until sunday when it got bricked because of an outdated recovery from clockwork. I managed to solve this with some help from you guys, but now again.
I flashed the android monday again with same version, it was working well until yesterday at night, it started showing some whatsapp stopped working stuff again, i rebooted it and now a bunch of window errors... reboot it again and well... no luck it stayed in the Android loading window.
After this I was trying to install the stock version ROM from mike also, and that's when it got worse.
Flashed boot and recovery OK, then rebooted and when I tried to install the ROM it just won't let me, failed unknown error, failed remote : 00030000, and other messages, now when I try to flash the recovery again it says low battery, and when I try the script to charge it it won't work, FAILED remote: unknown reason.
What can I do guys? =S (Sorry for the long post, I just don't know what could it be, and I wish by giving that much information someone can find out the reason, contacted HTC and they said it has no guarantee since I rooted and the glass is broken)
can you still access fastboot??
if you can.. then flash the latest CWM 5.8.4.0
It will allow the phone to charge.
faiz02 said:
can you still access fastboot??
if you can.. then flash the latest CWM 5.8.4.0
It will allow the phone to charge.
Click to expand...
Click to collapse
I can but there is some weird reason that won't let me do any flash, either low battery and when it gets charged a bit (because it may charge enough sometimes) it says FAILED remote:00030000 or unknown reason.
Don't know what it could be.
I ran into the exact same problem, the charger script does not help me too (low power on usb port of pc).
Thats how I fix this:
1) disconnect original charger, let's phone die. or use shutdown in fastboot.
2) connect original charger, and wait while phone powered up (He himself off as he does not have enough battery power.). disconnect charger.
3) vol.down and hold power,choose fastboot
4) connect charger
5) choose reboot bootloader (phone will reboot in fastboot)
6) choose reboot bootloader (phone will reboot in fastboot)
7) choose reboot bootloader (phone will reboot in fastboot)
....(do it fast)
249) choose reboot bootloader (phone will reboot in fastboot)
250) choose reboot bootloader (phone will reboot in fastboot)
251) disconnect charger, choose shutdown.
252) go to PC
253) vol down, power up
254) choose fastboot
255) flash the custom recovery with power supply support
256) flash custom kernel
257) don't disconnect USB!
258) fastboot / reboot bootloader / hboot
259) recovery
260) mount USB storage
261) drop zip of custom flash to the phone
262) unmount
263) advanced / restart recovery
264) flash the zip of rom
265) restart phone and dont disturb it, at 30 minute, let hi charge.
266) disconnect USB and connect original charger (1A)
267) Have fun!
It worked but bad news... now as always I am getting the message windows, with some weird apps.
First it was htc.com.bgp or something which I found it was the weather, then whatsapp, then Personalize, pretty much everything I open stops working after a while, what can I do? This was the exact reason that brought me here in the first place. It started showing these messages and I decided to install a custom ROM, it was first stock and locked and happened, now with this Android HD ROM it is still the same.
Thanks man... i was scared like hell when i realised that by script my battery voltage didnt raise up... even worse... it became less... i was reboting bootloader for 1h, but finally it worked... now im charging it to max... then ill flash stock rom
Thanks again.
ok so i had the latest cm13 rom on my phone partition is in ext4 had many issues with the rom so i went to flash the stock rom with odin
while the firmware was loading my usb cable failed and an error popped up saying odin process was aborted then the com port went empty (the phone disappeared) no the phone will not go into download mode while trying to get into download mode every thing looks good till you press the up button an you go to odin mode but with a message: firmware upgrade encountered an issue. please select recovery mode in kies and try again.
however my pc will not recognize my phone any more and i can not get into recovery either
in fact if i just plug the phone in it boots up to this message screen without even touching any buttons
I have tried just about everything i can think of even a unified toolkit but nothing will work as i cant access recovery or odin or kies???
I have also gone threw the forums and was not able to find anything pertaining to this directly
please help
Its been a long time since I booted my Galaxy Note-II (GT-N7100) as I use an iPhone and Nexus 5 as my daily drivers.
The phone wont boot past the Samsung Galaxy Note II GT-N7100 logo. I am able to access the recovery and download mode as well, and I have flashed the latest stock rom from Sammobile using the Odin. The flashing was successful. however the phone doesn't boot past the logo. Also the phone will not power up unless connected to a PC, it wont power up even when connected to a charger and will immediately shut down when the USB cable is disconnected from the PC. I flashed TWRP 3.0.2 Custom Recovery using the Odin and tried installing CM 13 based Rom through the mem card, however the log reads patching image unconditionally and also that "Failed to mount /system" (invalid argument). The phone when restarted into recovery can no longer mount the /system partition. However on flashing the stock rom using Odin, the /system partition is available for mounting. The recovery log also shows MTP enabled, but my PC doesn't detect the phone when in recovery, it only detects the phone in Download mode. I have the Samsung drivers installed. Since the phone is not being detected in recovery I am unable to use the adb.
I am out of ideas and request your suggestions other than approaching a service centre.
If I can somehow access the phone via ADB, I might be able to check the memory partitions for corrupt units, and possibly create a custom PIT file to repartition and suit the available memory units.
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
audit13 said:
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
Click to expand...
Click to collapse
Thanks a lot.
Tried your method and finally the phone has booted into the OS.
Had to replace the battery with another spare one in the process.
However the phone is still not being detected by the PC unless it's in Fastboot/ Download mode.
When connected to a computer, does anything appear on the phone screen? If you're using Windows, nothing new appears in device manager?
sorry to jump in this thread but i am having a similar problem
my completely stock tmobile note 2 is stuck on the samsung logo
i have never flashed it or done anything to it
my phone was working really slow, freezing up and battery draining fast
so i did a hard reset and it fixed the problem of running slow and freezing up for a week or so but battery drained fast
so i bought a replacement battery from ebay and installed it and the next day i restarted my phone and it froze on the samsung logo
i tried turning it off and on and still the same thing
any suggestions or should i start a new thread?
fyi i am a noob
Hi all,
I got a boot loop with toggling between Amazon logo and black screen. Did a wipe of cache & factory reset and it persisted. So i downloaded the bin file for latest version from Amazon's website. I did a side load through ADB. The phone screen shows these and highlights reboot system now option.
Finding update package....
Opening update package...
Verifying update package...
Installing update...
script succeeded: result was [/system]
Install from ADB complete.
So i then do a reboot and it goes in to the boot loop between black screen and Amazon logo. I tried doing it multiple times to the same result. What have i done incorrectly or am i missing something. Is this fixable or is it a lost cause?
This forum had been a great help in getting me do something on this bricked phone. Any help is greatly appreciated.
Thanks
mmsai
it's crazy... mines is doing the same thing.
It all began by only working if the phone was plugged in (if unplugged, it restarts). I was running CM11
I decided to do a factory reset, that's when my troubles began
I did the adb sideload with the factory rom from amazon
It worked for about 24 hours and was usuable, but it still would restart if unplugged, but I'm cool with doing that until I get a new phone.
Now my phone is just boot looping the amazon logo over and over... it'll get your hopes when it makes it to fire logo for that split second then back to the amazon logo it goes.
this is so f'd up
It happened to me when I sideloaded the wrong factory image for my device (i.e. carrier vs unlocked). Try sideloading the other one.
Same problem with me. Moreover I can't go to recovery mode normal way. I can only go recovery mode only when I have phone attached with a computer using usb cable.
Please help with any idea.
I have a Samsung Note 8 GT-N5110 (WiFi only) that is stuck at the Samsung logo.
This started after there was an attempt to flash a non-stock firmware and the device powered off before it was done.
When I attempt to enter Recovery Mode (Volume Up + Home + Power) it displays "Write Fail!" in upper left of the screen.
I am able to enter "Download Mode", so I've tried flashing a stock firmware using Odin.
I've tried both a One-Click recovery based on ODIN3 v1.81 and also tried Odin3 v3.12.10.
Each time, Odin fails, with a message:
write fail!!
SW REV. CHECK FAIL. DEVICE:2, BINARY:1
I've tried various versions of firmware, and nothing seems to work.
I've tried disconnecting the battery for a minute or so, and it still fails.
Any ideas what else I can try?
I have screen shots and detailed logs of what I've been getting, if that helps.
Thanks!
Believe it or not, I still have this device, and have not been able to get it to work!
So, I'll just revive this zombie post more than 2 years later, and see if anyone has any idea on what to do.
I'm in the fourth (fifth? sixth?) week of corona-quarrantine, so plenty of time to look into this!
The tablet needs more power than the computer's USB port can deliver. Thus, it will slowly drain the battery while connected to the computer and working via ADB, Odin or Heimdall. Seems like that has been the case in your earlier attempt, resulting in a corrupt flash memory. I can't tell if it's really defective or just corrupt and in need of formatting.
I'd try to:
1) Charge the battery
2) Copy LineageOS to the MicroSD card
3) Boot into download mode and install TWRP only via Odin or Heimdall. If this works,
4) Boot into Recovery (TWRP, not the stock one!), connect the charger to keep it powered and go from there (wipe and repair the internal flash, install LineageOS)
If this doesn't work, try if you can find any service functions in Odin or Heimdall to wipe and repair the internal flash.
Good Luck!
Ektus.
Hi Ektus,
Thanks for your help!
I will try as you suggested, and see what happens.
I'll let you know how I do.
Thanks!
I had similar problem. What I did is just change the USB cable to new.