Ok so the strangest thing happened yesterday. I left work, phone fully functional and got in the car to drive away. Where I was parked I was still getting the wifi from the building I work in and I wanted to start streaming music. I turned off wifi and tried to use the data network. No signal. Now, sometimes, it takes a really long time to switch back over to cellular after leaving wifi and especially if I use wifi calling. So, instead of waiting, I pulled the battery like I've done dozens of times before. Only, this time the phone didn't restart. The splash screen comes up and then it shows what appears to be the default android animation. I've never seen this on this phone or any of the roms I've loaded. It never starts the phone; the animation just keeps running. I couldn't get into recovery, it just returned me back to the bootloader screen.
Now when I got home I tried a few things with the all in one tool. I thought if I could load a recovery, I could re-flash my ROM and possibly get the phone working again without data loss. That didn't work. ADB couldn't even identify the device. Then, I downloaded the latest ICS leak onto my sd card, renamed it and put it in my phone. It started to load the file and showed me the 15 or so things that will be updated. I started the update and each of the 15 items said "Fail PU" except nfc. Its as if the partitions are just gone.
As you can see from the image, I have S-off, with unlocked boot loader. So now it appears that the battery doesn't charge on the bootloader screen. I left it plugged in all night in an attempt to charge the battery. I couldn't plug the phone in without it turning on and going right to the bootloader. So, I left it plugged in with the screen on all night and the battery is still dead. Now I can't start the phone to attempt anything further.
I've alreay called T-mobile to do a warranty exchange so there is a new phone on the way. Once I have it I should be albe to get a battery charged and into the old phone and try to restore it. I would like to get it back to factory with S-On with bootloader locked in the event that they decide they don't want to honor my warrany.
Any advice is welcome.
Thanks!
{
"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"
}
Ok so the image cuts off the S-off and hboot version, sorry.
You should lock your bootloader before flashing ics leak
Try flashing eng bootloader by naming it ph85img.zip and flashing in bootloader. That will give u a locked bootloader. Then try flashing ics ruu
All of this after getting a new battery of course.
_________________________
Am I on Candid Camera?
failed pu is full brick. You should check out the unbricking thread in the dev section.
Check it out http://forum.xda-developers.com/showthread.php?t=1627882
Thanks for the replies. I don't think that the unbrick tool supports my situation, but I will give it a try as I don't have much to lose. T-mobile is already sending a replacement so either way I should be ok. I have reverted to my trusty HD2 running ICS 4.04. Flashed probably over 100 ROMS onto the HD2 and never had a problem.
Just curious.
You said that ADB didn't recognize your phone. ADB only sees your phone when the phone is in recovery or fully booted up. When it is in bootloader, you can use fastboot as you have done trying to flash the ICS leak.
Did you try flashing the stock boot.img? The faux's kernel may not work as it is designed for GB. Well, I haven't tried it on my ICS so I'm not too sure.
Well, actually, you should try flashing things in the following order.
1. recovery.img from fastboot. If you can get it flashed successfully, at least you can adb shell into the system and see if your data is intact and nandroid back up to be safe.
2. kernel (boot.img) from fastboot.
3. some gb roms starting with something as close to stock GB as possible. Do it only if you can get recovery to work and flash only from the recovery, initially. RUU zips usually contains more stuff and if flashing fails, like in your ICS case, the system may go crazy.
I hope it helps.
well I got the replacement phone and charged the battery up. I put the battery into the old Amaze and it won't even turn on. It's completely dead. I guess I'm gonna just send it back. No hope for my data. Luckily have a backup from 4/28.
Thanks for the helps folks.
Slavid said:
well I got the replacement phone and charged the battery up. I put the battery into the old Amaze and it won't even turn on. It's completely dead. I guess I'm gonna just send it back. No hope for my data. Luckily have a backup from 4/28.
Thanks for the helps folks.
Click to expand...
Click to collapse
Hey, just wondering, sounds like even if you have rooted your phone and install custom ROM T-Mobile will still honor the warranty. Is that correct? I thought they won't if you have rooted your phone...
Slavid said:
well I got the replacement phone and charged the battery up. I put the battery into the old Amaze and it won't even turn on. It's completely dead. I guess I'm gonna just send it back. No hope for my data. Luckily have a backup from 4/28.
Thanks for the helps folks.
Click to expand...
Click to collapse
Hope you have a better luck with the new phone!
shuvarts said:
Hey, just wondering, sounds like even if you have rooted your phone and install custom ROM T-Mobile will still honor the warranty. Is that correct? I thought they won't if you have rooted your phone...
Click to expand...
Click to collapse
By reading many threads relating to unlocking/warranty, I am convinced that they will honor the warranty as long as the problem you are having is NOT related to the unlocking and subsequent modding of the device by you.
Well, sometimes it's hard to tell what happened if your phone is completely dead, though.
ringochan said:
Hope you have a better luck with the new phone!
By reading many threads relating to unlocking/warranty, I am convinced that they will honor the warranty as long as the problem you are having is NOT related to the unlocking and subsequent modding of the device by you.
Well, sometimes it's hard to tell what happened if your phone is completely dead, though.
Click to expand...
Click to collapse
Failed pu means the memory is shot. Nothing will write to the partitions. Warranty job
That's what I thought. The internal memory must have fried. I've had this happen to SD cards where suddenly they are blank. I imagine the same thing can happen with internal memory.
I already got my new phone and it's all restored, unlocked, s-off and running a custom rom.
thanks everyone.
Related
The 2.3 OTA soft bricked my fathers Fascinate and I want to push it back to 2.2 with ODIN3 so that I can try again. Anyone have a link to drop box or anywhere that I can grab up the stock unrooted image so that I can try again with the OTA?
I used this to get mine to ed05, hope it helps. http://forum.xda-developers.com/showthread.php?t=1178544 in case you need directions you can get them here http://forum.xda-developers.com/showthread.php?t=1026746
larry0071 said:
The 2.3 OTA soft bricked my fathers Fascinate and I want to push it back to 2.2 with ODIN3 so that I can try again. Anyone have a link to drop box or anywhere that I can grab up the stock unrooted image so that I can try again with the OTA?
Click to expand...
Click to collapse
refer to section 4
http://forum.xda-developers.com/showthread.php?t=1238070
It seems that Odin3 and heimdal are not able to see the fascinate.
This is all I can 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"
}
HTC Thunderbolt 4G using Tapatalk.
I've had this Fascinate on this laptop running ODIN many times before I gave it to my father, the drivers were all there and ODIN worked fine. Now, it is like the phone is not even there. Maybe this is past being saved and I just have to accept the warranty replacement. I thought once I got to download mode I was golden.... but it is not acting as I would have expected. This should be a simple cut and dry slam a md5 file at it and reboot. Not so.
Just for informational reasons, after doing the Gingerbread 2.3 OTA the phone was shutting off and required battery pull to restart.... it was doing this a couple times an hour... I did a reset from within the phone menu to try and get it back and this what it did during the auto restart that is done during a factory reset:
This happens no matter what you do, the only way to not do this is to remove the battery and keep it out, hold volume down in and plug in USB cable that is connected to PC. Doing that is how I can show the DOWNLOAD screen. But in download, it is still acting like a brick from the ODIN/HEIMDAL perspective.
I'm calling this puppy dead. I hate to admit defeat, but I guess it is time to suck it up and do the warranty replacement.
larry0071 said:
Just for informational reasons, after doing the Gingerbread 2.3 OTA the phone was shutting off and required battery pull to restart.... it was doing this a couple times an hour... I did a reset from within the phone menu to try and get it back and this what it did during the auto restart that is done during a factory reset:
This happens no matter what you do, the only way to not do this is to remove the battery and keep it out, hold volume down in and plug in USB cable that is connected to PC. Doing that is how I can show the DOWNLOAD screen. But in download, it is still acting like a brick from the ODIN/HEIMDAL perspective.
I'm calling this puppy dead. I hate to admit defeat, but I guess it is time to suck it up and do the warranty replacement.
Click to expand...
Click to collapse
have you actually tried heimdall or just odin? changed usb ports, tried it with battery in and with battery out?
sometimes randomly trying different things works
nitsuj17 said:
have you actually tried heimdall or just odin? changed usb ports, tried it with battery in and with battery out?
sometimes randomly trying different things works
Click to expand...
Click to collapse
x2
Something is up, somewhere for it not to be listed in the COM port. What condition is the cable in? I had to drive all around on Saturday to find a new data cable that would work. After awhile (from rolling it up, twisting, etc) they just don't work well enough to use ODIN. There isn't a Verizon store near me so I ended up finding one at US Cellular. The cables from Radio Shack wouldn't work for me.
sarkozy said:
x2
Something is up, somewhere for it not to be listed in the COM port. What condition is the cable in? I had to drive all around on Saturday to find a new data cable that would work. After awhile (from rolling it up, twisting, etc) they just don't work well enough to use ODIN. There isn't a Verizon store near me so I ended up finding one at US Cellular. The cables from Radio Shack wouldn't work for me.
Click to expand...
Click to collapse
I might know the answer to this, since I have faced the wall of this problem myself. The solution for me was to install Kies, and let it update the driver for the Samsung device. Because Heimdal installs another driver that replaces the Kies driver, and messes it all up. And it seems Heimdal does not replace Odin. Not sure what Heimdal is good for really that Odin cannot do, other than installing Heimdal specific ROMs.
I hope this helps, I know it helped me get a bit further. Now I am stuck at getting a ICS rom or Jelly Bean rom working.
New to the S4 world, but have been a stalker on XDA for a long time; mainly for my Droid RAZR and Kindle Fire HD.. I've searched, and found several threads about being stuck at the boot screen. Most recommendations were to installed a fresh stock firmware along with a .pit file, boot into recovery, and all is well. Not the case for me..
Long story short, I got this phone from a family friend. He said he took an OTA update, and immediately saw the firmware upgrade encountered an issue screen on boot. He had an upgrade on his account, and so he just gave me the phone. He had not idea what firmware he was on..
First thing I noticed is the phone does not take charge. I have a friend with an S4 (none verizon) and he at least confirmed the battery started with ~80% charge.
I tried flashing the MK2 stock firmware through ODIN, and immediately get a response on the phone of fused 6 binary 1, which I found through searching meant that he was on a later firmware (probably NC5), and since we cannot downgrade, thus the error.
I successfully flashed the NC5 stock firmware (ODIN would hang with the .pit file, so the md5 file only was used) from the following link, and am presented with the following issues:
1. Still won't charge when the phone is off.. tried several cables, and a few 2A chargers. Though ODIN still recognizes it when I am in download mode.
2. The phone decides when it wants to boot.. it usually takes me 4-5 battery pulls before it does anything. I know when it boots by the vibrate.
3. Normal boot gets hung up at the Samsung boot screen.. doesn't advance.
4. Can still boot into Download mode when it decides to boot (see #2).
5. Cannot boot into Recovery (stock). It hangs at the Samsung logo with the blue "booting into recovery" up top.
Also, my knox warranty bit is shown as 0x1:
{
"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"
}
Lastly, and strangest of all symptoms is that I've gotten some strange colorful screens when i am trying to boot up
I've replied to a thread about the debrick image for NC5, but no response yet. Could something hardware wise be wrong? Any help is much appreciated!
DTCsk8er said:
New to the S4 world, but have been a stalker on XDA for a long time; mainly for my Droid RAZR and Kindle Fire HD.. I've searched, and found several threads about being stuck at the boot screen. Most recommendations were to installed a fresh stock firmware along with a .pit file, boot into recovery, and all is well. Not the case for me..
Long story short, I got this phone from a family friend. He said he took an OTA update, and immediately saw the firmware upgrade encountered an issue screen on boot. He had an upgrade on his account, and so he just gave me the phone. He had not idea what firmware he was on..
First thing I noticed is the phone does not take charge. I have a friend with an S4 (none verizon) and he at least confirmed the battery started with ~80% charge.
I tried flashing the MK2 stock firmware through ODIN, and immediately get a response on the phone of fused 6 binary 1, which I found through searching meant that he was on a later firmware (probably NC5), and since we cannot downgrade, thus the error.
I successfully flashed the NC5 stock firmware (ODIN would hang with the .pit file, so the md5 file only was used) from the following link, and am presented with the following issues:
1. Still won't charge when the phone is off.. tried several cables, and a few 2A chargers. Though ODIN still recognizes it when I am in download mode.
2. The phone decides when it wants to boot.. it usually takes me 4-5 battery pulls before it does anything. I know when it boots by the vibrate.
3. Normal boot gets hung up at the Samsung boot screen.. doesn't advance.
4. Can still boot into Download mode when it decides to boot (see #2).
5. Cannot boot into Recovery (stock). It hangs at the Samsung logo with the blue "booting into recovery" up top.
Also, my knox warranty bit is shown as 0x1:
Lastly, and strangest of all symptoms is that I've gotten some strange colorful screens when i am trying to boot up
I've replied to a thread about the debrick image for NC5, but no response yet. Could something hardware wise be wrong? Any help is much appreciated!
Click to expand...
Click to collapse
Odin recognizing the phone does not necessarily negate a hardware issue. It sounds like you may have a bad USB port otherwise you would be able to charge the phone. Did it get wet or something?
"It was for freedom that Christ set us free; therefore keep standing firm and do not be subject again to a yoke of slavery." - Galatians 5:1
liljoe727 said:
Odin recognizing the phone does not necessarily negate a hardware issue. It sounds like you may have a bad USB port otherwise you would be able to charge the phone. Did it get wet or something?
"It was for freedom that Christ set us free; therefore keep standing firm and do not be subject again to a yoke of slavery." - Galatians 5:1
Click to expand...
Click to collapse
Thanks for the reply. From what I am told (I have no real reason to not believe a family friend), it did not get wet. That being said, I haven't ruled out something wrong on the charge IC or USB port. I think I might pop open the case and see if I can find any signs of corrosion.. as this could also cause the weird screen issue I am seeing from time to time.
Bump for the weekend crew ..
DTCsk8er said:
Bump for the weekend crew ..
Click to expand...
Click to collapse
Try removing the Screen, and re-inserting all the ribbon cables after cleaning the connectors with alcohol. Just google "Ifixit teardown verizon s4"
npjohnson said:
Try removing the Screen, and re-inserting all the ribbon cables after cleaning the connectors with alcohol. Just google "Ifixit teardown verizon s4"
Click to expand...
Click to collapse
Thanks for your reply. I'll give it a shot tonight. I planned on tearing the whole thing down anyways, just haven't had any time. I'll report back results when finished.
Today I manually flashed 5.1.1 (the device have never been able to upgrade normally, "too low memory.. something") and all went good until I restarted. Now I get error msg "This is a development device not intended for production use", device is locked, I can't flash anything - "Permission denied".
It also seems as I have received a device not made for sale ?!!! I bought this via google store. Has this happened to anyone else ?
sigfrid56 said:
Today I manually flashed 5.1.1 (the device have never been able to upgrade normally, "too low memory.. something") and all went good until I restarted. Now I get error msg "This is a development device not intended for production use", device is locked, I can't flash anything - "Permission denied".
It also seems as I have received a device not made for sale ?!!! I bought this via google store. Has this happened to anyone else ?
Click to expand...
Click to collapse
See post #97 here > http://forum.xda-developers.com/nexus-9/orig-development/root-t2929118/page10
cam30era said:
See post #97 here > http://forum.xda-developers.com/nexus-9/orig-development/root-t2929118/page10
Click to expand...
Click to collapse
If I try to flash a image I get errormsg: "Can not flash any image when device is locked!"
If I try "fastboot oem unlock" the msg is;
ability is 0
Permission denied for this command!
sigfrid56 said:
If I try to flash a image I get errormsg: "Can not flash any image when device is locked!"
If I try "fastboot oem unlock" the msg is;
ability is 0
Permission denied for this command!
Click to expand...
Click to collapse
Try this > fastboot format cache
Then > fastboot format userdata
Note that if this works it will totally wipe your device, including contents of SDcard.
cam30era said:
Try this > fastboot format cache
Then > fastboot format userdata
Note that if this works it will totally wipe your device, including contents of SDcard.
Click to expand...
Click to collapse
Tried it and it didn't help. Device is still locked. and unflashable.
I too am stuck in the same boat as you. I've tried multiple ways to flash/update including sideloading the signed OTA's via stock Recovery. At this point I just think it's RMA time to HTC
sigfrid56 said:
Tried it and it didn't help. Device is still locked. and unflashable.
Click to expand...
Click to collapse
You can try this. Look at post #57 > http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page6
cam30era said:
You can try this. Look at post #57 > http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page6
Click to expand...
Click to collapse
Tried that too, thank you. Didn't work.
sigfrid56 said:
Tried that too, thank you. Didn't work.
Click to expand...
Click to collapse
One last shot. Read post #56 here and try that > http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page6
Try contacting Google, if you got it from them and it has the correct serial they should be able to help you with an exchange. at least, I hope.
cam30era said:
One last shot. Read post #56 here and try that > http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page6
Click to expand...
Click to collapse
Tried that too after looking at #57. Didn't work either. Now my tablet will go to the trashcan.
sigfrid56 said:
Tried that too after looking at #57. Didn't work either. Now my tablet will go to the trashcan.
Click to expand...
Click to collapse
Before you do that, I'd suggest contacting both Google and HTC. If that fails, it's still worth something on eBay.
same problem
UPDATE
Talked to Google and there is definetly no wy to fix it.
I am getting my N9 exchanged by amazon(since i bought it there)
Do not bother trying to fix it yourself - because there is now way.
Sorry for all of ya.
Same problem here. Installed the 5.1.1 update like always. getting this on boot:
{
"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"
}
Contacted Google and they sent me a how-to to wipe cache and factory reset ...
Already tried some of the mentioned workarounds.
None of them worked, since my bootloader ist locked too.
Was hoping for fastboot oem verified -> fastboot wipe cache and userdata, but that did also not help...
I am on the brink of smashing this thing. How can Google screw up an official update like this?
I'll keep you updated for those who are having the same problem right now.
Worst OTA Ever !!!
Same problem, looks like Google really screwed this up!
I tried to unlock the device, but no way to do that from the bootloader, tried to wipe both cache and user data, still cannot unlock / flash ...:crying:
I've just had the same issue, trying to update just to 5.02 I'm getting a replacement from Google. I've never had this happen with one of their devices.
Error BUT OE ROM works/Loads 100%
hi all. I just bought a N9 (I do NOT want to root it) with this same error showing up at charge and when shut off/rebooting stage.
The N9 has factory ROM loaded
BUT the N9 still works 100%. Nothing seems to be wrong with my ROM and any feature I've played with seems to be working perfectly well.
So since I have no intentions of rooting/loading ROMS. I just want the factory ROMs from Google Updates, should this be something I worry about, or just ignore?
I got a smoking deal on this, the keyboard cover and another silicone case with magnetic cover so I really don't want to ask seller for refund.
I spoke with the seller, who is a computer science major about the issue and he profusely apologized and said he will take it back and fix the issue ( so he did this morning).
He rooted the device but never flashed any other ROMS. He just wanted the device rooted. So when he locked it again he figures that it what set off the "tampered flag"/error message.
So maybe since he never flashed another ROM to the device that has everything to do with why it still works 100% still, yet I'm getting the red letter message.
I spoke with HTC about this today and they said if the device is working fine and loading to the ROM no issues, then totally ignore this msg.
I just wanted to ask the seller to remove the error message if he can because if I decide I don't like the size of the device and I try to sell it I'm worried another buyer may be weary of the error message (as they should be really).
UPDATE:
OK, so this is my solution, according to the guy who fixed my N9
"So when you unlock the bootloader it actually allows any android device to be updated easier. So it can be updated either on the tablet directly or manually updated on the computer. Unlocking the bootloader isn't the same as rooting the device.
So I have actually unlocked the bootloader. I was actually running some tests, and the red text appeared because the program I used to factory restore the tablet and lock the bootloader wasn't official. So I took Google's original software for the Nexus 9 and put it on. So everything should work fine now, you will get regular software updates over the air and everything should be fine.
I have turned on and off the tablet 7 times now and there is no text when it is booting up or shutting down. Charging seems to work perfectly fine and it is able to connect to my computer."
maybe that will help others, maybe not.
UPDATE: Feb 11
So Google released a Feb security patch last night and my N9 can not install it. It downloads fine and tries to run but after 1 second of installation it fails and android is on his back with the word ERROR underneath. I am not sure if this ie becasue my factory ROM is re-installed BUT the bootloader is NOT locked again (left unlocked by the last owner). SO I downloaded Wugfresh's NRT and used the RELOCK button and after it wiped my tablet, now the red error "This is a development device not intended for production use" is back on my tablet again. ugh. I'll try using ADB and fastboot to bring back to factory spec. I do not need to have my tablet left in unlocked state as many of you may want. I just want a reliable N9 that updates the factory ROM and security patches OTA. I do not want to have to play with this.
I assume this is no longer an issue?
I had this message during an update to Nougat on a Nexus 9 that arrived that morning from Agros refurbs on Ebay.
I panicked and got here before the update completed but I needn't of worried Nougat went on with no issues at all.
I also got this message during the update to Nougat on a tablet I bought off of eBay. The update went fine and no longer displays that message during boot up. So, I guess it's OK.
well this is becoming quite a ride. thanks to edgardo uchiha i was able to root my sch-i545. then i screwed it up with an improper mod. finally got it back into download mode after several attempts with the phone's buttons and seemed like i was back in rooted vrugoc1 state. then when i restarted it today it said no longer rooted. so i tried to reroot and upon reboot it is now stuck on verizon logo. really want to get this thing in a state that wont cause problems if possible ? being a verizon pos.
devtinagub said:
well this is becoming quite a ride. thanks to edgardo uchiha i was able to root my sch-i545. then i screwed it up with an improper mod. finally got it back into download mode after several attempts with the phone's buttons and seemed like i was back in rooted vrugoc1 state. then when i restarted it today it said no longer rooted. so i tried to reroot and upon reboot it is now stuck on verizon logo. really want to get this thing in a state that wont cause problems if possible ? being a verizon pos.
Click to expand...
Click to collapse
Do a battery pull, then once the phone is off, go into download mode. Then flash stock OF1 with odin (this may take while). After you have successfully booted, root again.
thanks for the tip. like you said time involved due to size of the rom which is downloading now. will try and let you know if it does the trick.
nope pretty sure no go .... let it sit for an hour and no reboot. if it takes longer than that id be surprised. anyone want a pos verizon s4 chunk? what is the hangup on this part?
devtinagub said:
nope pretty sure no go .... let it sit for an hour and no reboot. if it takes longer than that id be surprised. anyone want a pos verizon s4 chunk? what is the hangup on this part?
Click to expand...
Click to collapse
What part of the process did it not boot? Flashing stock OF1?
will try again overnight just in case that wasnt long enough. will reply may be as late as monday after the jig comes in the mail. gonna try different options until i get this thing. trying everything possible to not have to send it in to the shop.
devtinagub said:
will try again overnight just in case that wasnt long enough. will reply may be as late as monday after the jig comes in the mail. gonna try different options until i get this thing. trying everything possible to not have to send it in to the shop.
Click to expand...
Click to collapse
I just had to flash the stock OF1 using Odin3 v1.85. Newest version of Odin would not work for me. I was stuck on the Custom boot screen but was able to get to download mode. I could flash OC1 & OF1 using Odin3 v3.10.7 but the phone would hang on the boot screen. Not sure what version of Odin your using but maybe this helps you.
thanks for the odin 1.85 tip. how long does it take to flash such a large 2gb+ file ? it just seemed that an hour would be long enough to flash so i stopped the process after it seemed to me to hang on odin last line says aboot.mbn. but im gonna let it go overnight just to let it go if it needs that long on the older odin like you said.
still no luck on getting s4 to load past the verizon logo
cant find odin 1.85 without warnings saying this requires a subscription and then those links cause my pc to say this site is loaded with trojans. isnt there a trustable link to download files? just tried again with odin3.10.6 and stock oc1 using my new jig and still no reboot of the phone even after waiting an hour . so i either get no reboot with the large rom file or it reboots but hangs on the verizon logo on the small rom file. its frustrating to not see a progress bar during flash to know if it is doing anything especially on these huge full stock rom files. and i think i may be using the wrong button in odin. shouldnt i be using bl on these full stock oc1 and of1? for me i dont know enough to just grab any version of odin and any version of rom and hit the buttons and know it will work. so kinda back to square 1 on knowing what to do now.
still hangs on verizon logo more on whats goin on
went on YT and found a good 1.85 link and it showed the blue progress bar. mine does not move. glad there is one but sad mine sits. here is a link to my dropbox screen snip of failed attempt to flash fullstock of1 using odin1.85 as described above. it failed quickly in just a few seconds it didnt sit there and try for awhile.
{
"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"
}
one last point about how i may be doing this wrong : i pulled sim and sd card both is that part of the problem?
decided to go back to an angle i gave up a week ago. that was for a couple of days at boot attempts the phone would stop at a screen saying the following : " startup fail! run verizon software repair assistant..." when trying that on my desktop the repair galaxys4 button is grayed out until i put it in download mode and it takes about 10-15 sec to turn red . all looks good until 83% +/- when it says "unable to complete repair because phone was disconnected. try repair again do not unplug phone until repair is complete. obviously i didnt unplug it but something is going wrong. maybe its the same thing that is happening when i try to flash the stock of1 rom and cant complete as described above. just wish it was known what that is causing disconnection....
just so everyone knows who may see this ** i sold the stupid i545 to someone on swappa! ** thank you swappa another successful sale!
and thank you buyer for taking it off my hands i lost only a few bucks. then i turned right around and got an att model sgh-i337 on kitkat for a little less than what i bought the i545 and a little more than i sold it for. so im good again & will be on that forum learning that model. to the moderator this can close.
Hi, I have this phone which I bricked by downloading - I guess - the wrong firmware with sp flash tools.
https://www.freebrowsinglink.com/hoot-p20-pro/
The phone is dead. Whenever I try to download, format+download, or do anything for that matter gives me the following error message:
{
"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"
}
Is there anything I could try to save it from salvage? Thanks.
Do you have the correct stock ROM?
Can you get the phone in adb/fastboot?
Hard Bricked Hoot P20 pro Clone
Phone is completely dead. There is no stock rom, nor support website, only a couple of funny looking web pages located in Bangladesh or Burma, or something like that, and they offer roms for p20 pro clone phones. I tried one and I downloaded the software via sp flash tool, because the regular recovery on the phone itself, whenever I tried to re-install, would give a lot of errors after first boot and/or every reset for that matter; it'd say 'UI stopped working', 'clock stopped working' and so on with a whole sequence of error messages rendering the phone useless. So I tried to find something on the internet, but that did not work out the way I hoped for THanks.
Can you get into the recovery mode?
I am not sure what you are saying when you say "because the regular recovery on the phone itself, whenever I tried to re-install". You need to find "Factory Rest" line in recovery mode that would be the first thing to do. It may take going through fastboot mode usually pressing down on the "power button and volume down button" and then maybe go to recovery in menu press power and then press "power button and volume up button" , but it real depends on the phone, but you need to find "Factory Reset"
I know you can't get into the phone but finding out Device name something like n 1awifi or X1995-2, GPU vendor, GPU used, MODEM M632_05.34.01.73R OCEAN_LATAMDSDS_CUSTMODEM M632_05.34.01.73R OCEAN_LATAMDSDS_CUST (this off a Motorola phone but to give you an idea) will help in trying to find a stock Rom that may work or whether the "firmware" you have gotten is appropriate for your phone. Usually, these things are in file name of the rom or "firmware" so you can see if it is the right one.
But to be honest with you if factory reset doesn't work there is little chance you can unbrick your clone phone without the stock ROM and it appears the custom ROMs being sold are buggy or was not the right one, or someone just to making money.
Hoot P20 Pro Clone
Thanks for the response. As said, phone is dead, even the charging icon for the battery isn't showing up anymore. It had Android 5.1 on it and it has a MTK6580A quad core inside. I bricked the phone after downloading Android 7.1 for MT6580 chip set via SP Flash Tool. I can't start recovery, again phone is completely dead.
How can I resolve the 'enable dram fail (4032)' error in SP Flash Tools? Any ideas? Thanks.
Clone_Cat said:
Thanks for the response. As said, phone is dead, even the charging icon for the battery isn't showing up anymore. It had Android 5.1 on it and it has a MTK6580A quad core inside. I bricked the phone after downloading Android 7.1 for MT6580 chip set via SP Flash Tool. I can't start recovery, again phone is completely dead.
How can I resolve the 'enable dram fail (4032)' error in SP Flash Tools? Any ideas? Thanks.
Click to expand...
Click to collapse
Forget the SP Flash Tool because you don't have any compatible ROM to flash to your phone. What you need to do is get into recovery usually hold the power button down then the volume button down and find "Factory Reset". I may require more manipulation of the power button and volume buttons to negotiate through the menu, but hopefully, in your case, the "Factory Reset" line will be on your first recovery page.
The battery died because of the continuous boot loop. If you get that again take out the battery.
You need to recharge the battery either outside of your phone, or you can try throwing the battery in the freezer for a while stick it back into the phone and plug into the USB charger without pressing any buttons. Google tricks to reviving a dead battery.
The recovery should still be working on your phone. Google how to get into recovery for your phone/manufacture. The procedure should be the same for all phone by the manufacturer.
Bricked Hoot P20 pro Clone
Ok, thank you for your suggestions. I did try format all and download in SP Flash Tools several times in the process, doesn't that erase everything from the phone, even recovery?
Again, and I don't know how important that info might be, the phone went dead after I copied Android 7.1 with SP Flash Tool through the upgrade firmware option. The ROM was meant for DooGee Shoot 2 phone, but it has the same SoC, namely the MT6580A, so I thought it might work.
If the battery went dead and won't charge, like you said, it would explain why the battery icon is not showing up any longer. I tried already to open the back, but I couldn't manage. Don't you need a heat gun for that to soften up the glue? Or is there perhaps a different technique?
Thanks.
Some sort of recovery should be there. It is doubtful it was erased.
ROMs not specifically made for a specific phone are unlikely to work or work well. I recently installed a ROM on my phone from a different region but same model of phone. Everything worked except the modem. I couldn't make a call. Easy fix for me though.
A while back I had a tablet where the battery went completely dead, and no charge icon screen, completely black.. I left it plugged into a USB charger. I bought another battery. By the time I got the new battery. The old battery charged fully and is still working today with no problem. So there is still hope for you. I did take the battery out for about ten minutes and put it back in before connecting it to the USB charger. I do not know if that made a difference. I left the back off while charging because I though I would have to replace the battery.
If your cover is glued on, use a hairdryer not a heat gun. A heating pad may work also. There are YouTube videos out there showing how to take off a glued phone back. You can search for how to replace a battery in a Moto G7, they have a glued back and I know there are how to videos. If the back is plastic tabs, you can use a guitar pick or something like that. There are video out there for that also.