Related
I think I may have bricked my A2. All I did was backup my current data, and then restore it as a test to make sure everything was working. Now on boot it hangs at the motorola logo... Any ideas?
Jimmy273 said:
I think I may have bricked my A2. All I did was backup my current data, and then restore it as a test to make sure everything was working. Now on boot it hangs at the motorola logo... Any ideas?
Click to expand...
Click to collapse
Uh oh, my only suggestion is to maybe clear the cache and do a factory reset?
Ya I've tried both of those..
Jimmy273 said:
Ya I've tried both of those..
Click to expand...
Click to collapse
Wait untill the SBF file is made. Or just take it into to AT&T say its just rebooting they won't know and get a new one.
What if they know I rooted it? Would they be able to tell? Also I noticed my backups do not include a boot.img... perhaps this is the issue?
Jimmy273 said:
What if they know I rooted it? Would they be able to tell? Also I noticed my backups do not include a boot.img... perhaps this is the issue?
Click to expand...
Click to collapse
Im saying AT&T will have no clue you rooted it, therefore they should just give you a new one. Say I shut it off turned it back on and it just keeps rebooting.
---------- Post added at 12:24 PM ---------- Previous post was at 12:24 PM ----------
You could always have someone create you a backup and send it to you. You would lose apps but who cares. Just a thought.
if you could create a backup, I could flash it via fastboot and it may work...
Yeah Jimmy just take it back to AT&T.... They will have no clue you rooted it. I can't tell you how many times I have taken back a soft bricked phone to AT&T... just say it hung and started to reboot automatically.
Jim
I probably shouldn't have tried to use a different backup to restore then... Cause now when I boot it takes me to the fastboot screen.. ugh
so can we fastboot images on? if so, just pull the system.img from your cwm backup and fastboot wipe, then flash the system image
the motorola fasboot doesn't seem to let me wipe the system before writing...
maybe something like this would work:http://www.droidforums.net/forum/dr...70-r3l3as3droot-43v3r-root-bionic-v2-1-a.html
Try to get it back to the stage where it just reboots then take it back. Easiest way.
If I could, I would. When I try to erase system through fastboot it says INFO Command restricted.
Man I don't know what to say, every time I soft bricked my Droid X I just SBF'ed but nothing like that is out yet?
you need to really crash that thing man then take it back to att and say you pluged it in last night and when you woke up it was off you turned it on and this is what happenes when i turn it on they will think its a usb charg issue or something thats been my experiance so far
Pirateghost said:
so can we fastboot images on? if so, just pull the system.img from your cwm backup and fastboot wipe, then flash the system image
Click to expand...
Click to collapse
This is the best to try for the time being.
Donation accepted towards an Atrix 2
Can someone put up a backup they did? I think I may have a method to get it working...
I have one still on my phone if I can send it directly from phone I will help you out I don't have access to a computer right now, just let me know how I can help
JRW 28 said:
I have one still on my phone if I can send it directly from phone I will help you out I don't have access to a computer right now, just let me know how I can help
Click to expand...
Click to collapse
Use root explorer. Navigate to the internal or external memory and go to clockworkmod and backup.
Donation accepted towards an Atrix 2
Question guys, if I bought the atrix 2 at best buy can I return this phone to AT&T if this happens to me? Also do you need to buy the warranty for the phone to return it for software repairs after 30 days? Thanks all! I've never bricked or destroyed a cell phone. My wife does but not I, thanks!
---------- Post added at 05:22 PM ---------- Previous post was at 05:20
I'm uploading my system.img to 4shared.com. Will this have any of my personal information on it?
Hello,
I have been crack flashing for a long time, but when I got the Droid Maxx from verizon I was disappointed at the lack of an unlocked bootloader. I had been running safestrap and was getting the phone ready to return for a refund so I can get the developer edition.
So, it looks like using safestrap I completely wiped the system partition. I can get the phone to boot to flashboot mode or to the safestrap flash screen but that is all.
Using RSDlite I attempted to flash 12.9.0, but get the return message "Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL. On the phone it said:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT."
So it looks like the issue might be because I am flashing the FXZ file for 12.15.15, but I cannot find the FXZ file for it.
I also tried using House of Moto. Attached is a screen shot of what I get.
So basically it looks like I have no ROM whatsoever. Is there a way out of this so I can return the phone for a refund?
Thanks in advance!
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
kclantz said:
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
Click to expand...
Click to collapse
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
ahjee said:
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
Click to expand...
Click to collapse
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
rds217 said:
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
Click to expand...
Click to collapse
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
So I just got back from the Verizon store, I went in to see if they could flash the files I need. They told me they couldn't but gave me a number at motorola to see if they would e-mail the files to me.
Unfortunately that didn't work. Motorola said I could send the phone in for a repair, and that was my only option.
I think I'll take the second option and wait until someone posts the files and flash them with RSD Lite.
I just hope that happens soon, as I am wanting to return the phone and get the developer edition. I have until Saturday to return it and I doubt they will give me a refund with it in this state.
ahjee said:
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
Click to expand...
Click to collapse
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
jcase said:
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse
rds217 said:
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
Click to expand...
Click to collapse
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
kclantz said:
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
Click to expand...
Click to collapse
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
erishasnobattery said:
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Thanks, that was what I was afraid of. I guess now I will check obsessively for the new FXZ files. Got have some way to spend my day (you know, as opposed to doing my job ).
So I sold an unopened, sealed Nexus 5 to someone last night and he's having a problem activating the device.
Here is his description of what happened:
"I popped in the SIM card, the loading proceeded as normally. It said it was activating and then a box popped up saying that "android is upgrading system files" or something like that. It restarted and went back to the language selection screen. I pressed English, next and then it went to the connect to wifi screen, froze and then restarted before I could even connect. Now it just loads on the boot"
I had him boot into recovery and do a factory reset, but the result is the same. I had him do a 2nd factory reset just be sure, but again, same result.
My thought is the system upgrade didn't happen correctly and not is corrupted.
What's the best course of action? Can I use the WugFresh toolkit to flash stock and unroot, or would I have to do it through ADB since the phone can't boot into the system?
I don't want to leave the buyer hanging, he seems like a nice guy, but I'm just not sure how to proceed?
Use ADB and flash the factory image for him.
Synyster06Gates said:
Use ADB and flash the factory image for him.
Click to expand...
Click to collapse
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.
SeanPlunk said:
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.
Click to expand...
Click to collapse
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!
switchfo0t said:
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!
Click to expand...
Click to collapse
Hello, I am the buyer of this Nexus device. I was able to successfully do these steps above, and reload the stock image for the Nexus 5. However, I am still running into issues.
WITH SIM:
I was able to get to the home screen after the initial setup, sent a few test text messages to my Google Voice number successfully, and browse on Chrome for a little bit before the device froze and restarted. After it restarted, I let it load up again, tried setting up my Google account on the device, then it froze again. All of the freezing happens within 3-5 minutes of using the phone.
So I decided to go into the bootloader, and do a factory wipe/cache wipe, and proceed without having the sim card in. I was able to get to the wifi selection screen, select my router, but as soon as the keyboard was suppose to pop up, the device froze and restarted. I am now just stuck on the welcome screen.
Any ideas now?
---------- Post added 29th November 2013 at 12:45 AM ---------- Previous post was 28th November 2013 at 11:56 PM ----------
Update: So I'm not sure what happened, but I ended up locking the device through Wug's Nexus Toolkit, inserted my sim card, and proceeded to set up the phone normally. So far everything has been working perfectly fine. I can receive/send texts, make and receive calls, and do normal functions with the phone without it locking up and restarting. Fingers crossed it'll stay like this.
Any idea on why this would've happened in the first place with the device?
---------- Post added at 01:38 AM ---------- Previous post was at 12:45 AM ----------
Update 2: Well, I noticed that it will randomly reboot every half hour or so it seems. It's kind of random, but I'm not sure what else could be causing these random reboots. The phone itself is working fine, but I just started experiencing random restarts.
Are you still on the stock rom or custom?
neomorphix said:
Are you still on the stock rom or custom?
Click to expand...
Click to collapse
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
---------- Post added at 01:49 AM ---------- Previous post was at 01:48 AM ----------
Jaybot said:
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
Click to expand...
Click to collapse
It was working fine earlier. I put it on the charger and got it to about 50%, used it for a little bit, then bam. It froze, and restarted all over again. I can use the phone maybe 5 - 10 minutes before it starts to recharge. Sometimes It'll automatically reboot after even unlocking the device.
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.
Jaybot said:
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.
Click to expand...
Click to collapse
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.
neomorphix said:
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.
Click to expand...
Click to collapse
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.
Jaybot said:
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.
Click to expand...
Click to collapse
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.
neomorphix said:
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.
Click to expand...
Click to collapse
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.
Jaybot said:
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.
Click to expand...
Click to collapse
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Jaybot said:
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
Ok. This just sucks. But as with any mass produced product there is bound to be the ocasional issue.
neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.
theesotericone said:
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.
Click to expand...
Click to collapse
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.
Jaybot said:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
neomorphix said:
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.
Click to expand...
Click to collapse
Just saw that. OP by your earlier symptoms I rules out a stuck power button. With the new info I'd look into it further. If the phone is just looping over and over it could be a stuck power button, Mash the power button repeatedly for a minute. Then try and reboot. A few other people have had this on the N5 already and it's a notorious issue on some Samsung phones.
neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
If it comes to that, how do I go about transferring the warranty over?
I feel really bad, I just don't get it. I bought two of them, the other buyer hasn't had any problems. Both brand new, sealed, in the box. Go figure.
Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
akaplo said:
Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
Click to expand...
Click to collapse
I am in the same boat. Please let me know if you get an unbrick image..
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Chay555 said:
I am in the same boat. Please let me know if you get an unbrick image..
Click to expand...
Click to collapse
akaplo said:
Can someone who has updated to the new PD1 firmware please make an unbrick image for me?
Odin hard bricked my phone last night when I was trying to update. It went through, froze on the Verizon slash screen, then shut off with the red notification LED blinking. I pulled out the battery and tried to restart it, but with no luck. I've tried the PB1 unbrick image from another thread but I can't make it work so I think my phone might be stuck on the new firmware, but I don't know.
I need my phone back! Any help is appreciated.
Click to expand...
Click to collapse
Good news! I was able to get the phone booted up again. Bad News: Its back on Lollipop firmware (BP1.) So what I did was I used the files from jrkuses working root method 3/4/16 and flashed them through Odin. First I flashed the PB1 unbrick image in his OK3 file, then I flashed the Nk2 kernel also included in the OK3 file, and last I flashed a file called VZW_BPB1_KERNEL_ONLY.tar.md5 also in the folder. Flashing those got me booted back on 5.0 safely.
---------- Post added at 08:57 PM ---------- Previous post was at 08:55 PM ----------
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
Thank You very much for the offered help. I just found a fix using jrkuses files in his root method and am now up and running again. Again Thank You.
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
It's definitely a hard brick. I can't boot into recovery, download mode, or anything! I've got a retail phone. You'd be a lifesaver if it works!
Chay555 said:
Thank You very much for the offered help. I just found a fix using jrkuses files in his root method and am now up and running again. Again Thank You.
Click to expand...
Click to collapse
Were you able to boot the phone during your ordeal? I can't get mine to do anything.
akaplo said:
Were you able to boot the phone during your ordeal? I can't get mine to do anything.
Click to expand...
Click to collapse
I was able to boot and I kept freezing at the Verizon splash screen. I did not realize that you couldn't even boot up. It was just a softbrick on my end. I hope you can get everything sorted out
---------- Post added at 09:55 PM ---------- Previous post was at 09:34 PM ----------
stellar0322 said:
So is this a soft brick or a hard brick. It sounds like a soft brick, try re-flashing PB1 kernel, or at worst odin a complete PB1 Stock re-flash. I have had lots of trial and error experience so just try flashing PB1 firmware only without bootloaders and this should fix your issue. If it is a hard brick all I need to know is if you are running a dev edition phone or retail. I just booted up sixperiences s7 edge rom so I can dump files from the new PD1 image, bootloaders and all.
Click to expand...
Click to collapse
Question. Everytime I flash the PD1 firmware on my phone it always gets stuck on the Verizon splash screen. Am I doing something wrong?
Chay555 said:
I was able to boot and I kept freezing at the Verizon splash screen. I did not realize that you couldn't even boot up. It was just a softbrick on my end. I hope you can get everything sorted out
---------- Post added at 09:55 PM ---------- Previous post was at 09:34 PM ----------
Question. Everytime I flash the PD1 firmware on my phone it always gets stuck on the Verizon splash screen. Am I doing something wrong?
Click to expand...
Click to collapse
Just flash stock PD1 using Odin and factory reset in stock recovery afterwards. Once you get used to it, softbricks won't scare you anymore
Nandr0idC0nsumer said:
Just flash stock PD1 using Odin and factory reset in stock recovery afterwards. Once you get used to it, softbricks won't scare you anymore
Click to expand...
Click to collapse
When I flash stock PD1 using Odin and factory reset it still freezes at Verizon splash screen. Any other way I flash PD1 whether it be Kies or Odin outputs the same result.Freeze at Verizon splashscreen
Chay555 said:
When I flash stock PD1 using Odin and factory reset it still freezes at Verizon splash screen. Any other way I flash PD1 whether it be Kies or Odin outputs the same result.Freeze at Verizon splashscreen
Click to expand...
Click to collapse
Reset using stock recovery. it usually takes about 20min on the vzw screen
Only problem is that I have a developer model, keep scouting the community I'm pretty positive someone has retail pit file with partitions. I have hard bricked my phone before I repaired it using win32img creator using an sd card. I never messed with partitions ever again after that.
akaplo said:
It's definitely a hard brick. I can't boot into recovery, download mode, or anything! I've got a retail phone. You'd be a lifesaver if it works!
Click to expand...
Click to collapse
stellar0322 said:
Only problem is that I have a developer model, keep scouting the community I'm pretty positive someone has retail pit file with partitions.
Click to expand...
Click to collapse
Darn. Thanks though! @Nandr0idC0nsumer, is there any way you might be able to get this for me? I posted on your debrick thread but haven't heard from anyone, so I started this thread in hopes to catch someone's (ANYONE'S) eye
In order for someone to do this, they'd have to be on a rooted version on PD1, yes?
akaplo said:
Darn. Thanks though! @Nandr0idC0nsumer, is there any way you might be able to get this for me? I posted on your debrick thread but haven't heard from anyone, so I started this thread in hopes to catch someone's (ANYONE'S) eye
In order for someone to do this, they'd have to be on a rooted version on PD1, yes?
Click to expand...
Click to collapse
Alright. I'm confused
EDIT: looked through the thread now. That's a hardbrick. Nobody has created a debrick image for PD1, so just try the PB1 debrick.
Re-explain what's going on. Unless your device is 100% dead, my debrick thread will not be of any use.
Nandr0idC0nsumer said:
Nobody has created a debrick image for PD1, so just try the PB1 debrick.
Re-explain what's going on. Unless your device is 100% dead, my debrick thread will not be of any use.
Click to expand...
Click to collapse
From the beginning:
Yesterday, I was on rooted OE1, using muniz_ri's build from months ago. I decided to use his thread that had been updated the other day to update my phone to PD1 (Android 6.0). I updated the ROM and the bootloader.
It got stuck on the Samsung boot screen, and after about 40 minutes, I decided to flash the PB1 (Android 5.0) stock ROM. I downloaded the full tar from sammobile and flashed using odin. It went successfully, as far as I could tell. My phone froze on the Verizon boot screen as expected, and after about 10 minutes the screen went black and the notification LED started blinking red. I pulled the battery, put it back in, and tried to power the phone on. It has been completely unresponsive every since. Neither recovery mode nor download mode is accessible.
Obviously, I have a hard brick. I've tried using the PB1 debrick image you (@Nandr0idC0sumer) gave in your other thread with my 16GB external SD card. I followed the steps given there exactly. I've had no luck in getting my phone to respond. I thought that maybe my flash went bad and that my bootloader is still on PD1 while my ROM is PB1, and I would therefore need a PD1 debrick image. Thus, this thread was born.
akaplo said:
From the beginning:
Yesterday, I was on rooted OE1, using muniz_ri's build from months ago. I decided to use his thread that had been updated the other day to update my phone to PD1 (Android 6.0). I updated the ROM and the bootloader.
It got stuck on the Samsung boot screen, and after about 40 minutes, I decided to flash the PB1 (Android 5.0) stock ROM. I downloaded the full tar from sammobile and flashed using odin. It went successfully, as far as I could tell. My phone froze on the Verizon boot screen as expected, and after about 10 minutes the screen went black and the notification LED started blinking red. I pulled the battery, put it back in, and tried to power the phone on. It has been completely unresponsive every since. Neither recovery mode nor download mode is accessible.
Obviously, I have a hard brick. I've tried using the PB1 debrick image you (@Nandr0idC0sumer) gave in your other thread with my 16GB external SD card. I followed the steps given there exactly. I've had no luck in getting my phone to respond. I thought that maybe my flash went bad and that my bootloader is still on PD1 while my ROM is PB1, and I would therefore need a PD1 debrick image. Thus, this thread was born.
Click to expand...
Click to collapse
Unplug your device and open device manager on windows. now plug it in. does device manager refresh as if it detected a new device?
Because sdcard mode will only work if you can get the device into qhsusb_bulk mode.
Nandr0idC0nsumer said:
Reset using stock recovery. it usually takes about 20min on the vzw screen
Click to expand...
Click to collapse
Is good now. Thank You
Chay555 said:
Is good now. Thank You
Click to expand...
Click to collapse
Congrats! You get a cookie.
Nandr0idC0nsumer said:
Unplug your device and open device manager on windows. now plug it in. does device manager refresh as if it detected a new device?
Because sdcard mode will only work if you can get the device into qhsusb_bulk mode.
Click to expand...
Click to collapse
No, it does not. Is there some sort of button combo I should be pressing to get the device into that mode? I've tried long-holding the following combos:
1. Power
2. Power, volume down, and home
3. Power, volume up, and home
akaplo said:
No, it does not. Is there some sort of button combo I should be pressing to get the device into that mode? I've tried long-holding the following combos:
1. Power
2. Power, volume down, and home
3. Power, volume up, and home
Click to expand...
Click to collapse
I've read up on the Snapdragon 80x boot ROMs, and there appears there is only 1 way to get into qhsusb_bulk mode, which is to have the bootloader corrupted and it is automatically triggered.
If it's not in that mode, it's a brick, go to Verizon and tell them it randomly died
there is nothing that can be done from now. good luck dealing with verizon/samsung and I hope you're still in warranty.
PD1 unbrick image.
https://www.androidfilehost.com/?fid=24562946973631519
Hey all! My friend has an s3. He is in a different state so I can't experiment on it quite yet.
He has a lot of files he needs to recover from the internal storage. He already has the sd data.
The issue is that the phone will not fully boot. It gets a little past the verizon logo and crashes.
He has tried wiping cache, and booting without the sdcard in.
What can we do to get those files for him?
Verizon said they can't use their diag machine since the device needs to fully power on for them to service it in that fashion.
Is it possible to flash the stock system partition without overwriting data via Odin?
Bump
tr4nqui1i7y said:
Hey all! My friend has an s3. He is in a different state so I can't experiment on it quite yet.
He has a lot of files he needs to recover from the internal storage. He already has the sd data.
The issue is that the phone will not fully boot. It gets a little past the verizon logo and crashes.
He has tried wiping cache, and booting without the sdcard in.
What can we do to get those files for him?
Verizon said they can't use their diag machine since the device needs to fully power on for them to service it in that fashion.
Click to expand...
Click to collapse
tr4nqui1i7y said:
Is it possible to flash the stock system partition without overwriting data via Odin?
Click to expand...
Click to collapse
Really kind of a tough situation.
Can he get into recovery mode? If so maybe he can pull data from it that way. There's a few ways to do it. It's hard to tell unless I see what the phone does when it boots.
Sorry for the late reply, hardly ever check these forums anymore.
BadUsername said:
Really kind of a tough situation.
Can he get into recovery mode? If so maybe he can pull data from it that way. There's a few ways to do it. It's hard to tell unless I see what the phone does when it boots.
Sorry for the late reply, hardly ever check these forums anymore.
Click to expand...
Click to collapse
I know he can get to stock recovery, because he's wiped cache that way. I don't believe that he is rooted or anything. I won't know for sure until I'm in person. The issue is that he thinks Verizon wants him to send the phone to them. He used a free upgrade. They sent him the replacement phone with a return box, so he's still not sure at the moment. And I haven't used an upgrade in about 4 years so I don't remember ever having to give back a device.
tr4nqui1i7y said:
I know he can get to stock recovery, because he's wiped cache that way. I don't believe that he is rooted or anything. I won't know for sure until I'm in person. The issue is that he thinks Verizon wants him to send the phone to them. He used a free upgrade. They sent him the replacement phone with a return box, so he's still not sure at the moment. And I haven't used an upgrade in about 4 years so I don't remember ever having to give back a device.
Click to expand...
Click to collapse
If he has USB debugging enabled be can use ADB to pull the SD card folder onto his computer in recovery mode.
Otherwise can't do much with stock recovery, if he's rooted you may be able to load TWRP from download mode and boot immediately into recovery mode.
BadUsername said:
If he has USB debugging enabled be can use ADB to pull the SD card folder onto his computer in recovery mode.
Otherwise can't do much with stock recovery, if he's rooted you may be able to load TWRP from download mode and boot immediately into recovery mode.
Click to expand...
Click to collapse
He's got the SD data. We're working on the /data/ partition now. I think it's mainly notes and pics if I'm not mistaken. I'm really hoping that he's rooted and just forgot or something.
We can make it into odin mode.
You don't need root.
Sent from my Nexus 6 using XDA-Developers Legacy app
---------- Post added at 06:00 AM ---------- Previous post was at 05:59 AM ----------
I can probably help you out.
Sent from my Nexus 6 using XDA-Developers Legacy app
whodisname said:
You don't need root.
Sent from my Nexus 6 using XDA-Developers Legacy app
---------- Post added at 06:00 AM ---------- Previous post was at 05:59 AM ----------
I can probably help you out.
Click to expand...
Click to collapse
I'm thinking of trying to flash stock via Odin to see if that will make it boot. Otherwise, it may have to go jtag route.
I am going to attempt to ODIN on it. Unfortunately I don't know what version of android he was on.
Which ODIN files would you recommend? Preferably one that won't need me to wipe the data partition. Also, please provide links if possible. I have found some stuff on my own, but a lot of links are dead.
tr4nqui1i7y said:
I am going to attempt to ODIN on it. Unfortunately I don't know what version of android he was on.
Which ODIN files would you recommend? Preferably one that won't need me to wipe the data partition. Also, please provide links if possible. I have found some stuff on my own, but a lot of links are dead.
Click to expand...
Click to collapse
Odin will wipe everything. Every .tar file I've come across essentially just return the phone to a completely stock state.
Wish I had old stuff but I don't. What have you found?
BadUsername said:
Odin will wipe everything. Every .tar file I've come across essentially just return the phone to a completely stock state.
Wish I had old stuff but I don't. What have you found?
Click to expand...
Click to collapse
Ah, I had found one that said it wasn't going to wipe data. I'll try to find the link again today. They were saying it was like doing an ota update and it would leave data in place.
tr4nqui1i7y said:
Ah, I had found one that said it wasn't going to wipe data. I'll try to find the link again today. They were saying it was like doing an ota update and it would leave data in place.
Click to expand...
Click to collapse
O wait I think I vaguely remember, but that we when the bootloader was unlocked, like 5 years ago.
Make sure you post the for here and I can try to help you, but if it's an older version it won't. You need to make sure the Odin file is the same or newer than your current bootloader.
@BadUsername I found this, which has the crappiest hosting servers I have ever seen. You can only download one file a day, so I need to keep changing my IP if I need more than one file from it. here
This is the no-wipe file i was referring to. I am just not sure if it is an android version that his device will accept. I am not sure if Odin allows you to go forward and backward. Here
tr4nqui1i7y said:
@BadUsername I found this, which has the crappiest hosting servers I have ever seen. You can only download one file a day, so I need to keep changing my IP if I need more than one file from it. here
This is the no-wipe file i was referring to. I am just not sure if it is an android version that his device will accept. I am not sure if Odin allows you to go forward and backward. Here
Click to expand...
Click to collapse
Just open up download mode and post what it says in the top left corner.
Also that file you posted first is the newest one, assuming it's legit it would work. That would for sure wipe everything.
Bottom one is old, probably won't work. Odin should just fail and not let you flash it. If it did work, it would fail at the bootloader stage and brick your phone anyway.
BadUsername said:
O wait I think I vaguely remember, but that we when the bootloader was unlocked, like 5 years ago.
Make sure you post the for here and I can try to help you, but if it's an older version it won't. You need to make sure the Odin file is the same or newer than your current bootloader.
Click to expand...
Click to collapse
That's what I was afraid of. I have no idea how updated he kept the device. And since I can only get into stock recovery and download mode I can't learn much about the device. I wish I could just adb in and grab the data partition off of it. Verizon is hounding him to send the device back or they will charge him $500 or something absurd. Which seems extra crazy since he has had that device since it was released. I thought for sure he would own it by now. Verizon has never asked me for a device back.
Have you found any helpful odin stuff out?
BadUsername said:
Just open up download mode and post what it says in the top left corner.
Click to expand...
Click to collapse
I won't be able to see the device until tonight. I will try to see if he is around the device now so he can let me know. His house has terrible reception and no wifi so I am trying to gather everything before the next time I go there.
@BadUsername Do you know if there is a list of odin files anywhere? This sub seems so disorganized imo. I can't find a helpful sticky or anything.
tr4nqui1i7y said:
I won't be able to see the device until tonight. I will try to see if he is around the device now so he can let me know. His house has terrible reception and no wifi so I am trying to gather everything before the next time I go there.
Click to expand...
Click to collapse
You can still pull nearly everything off the phone with adb from download mode if USB debugging was enabled, you can literally pull every partition and extract what you need.
You can load a very old version of cwm recovery through Odin and flash aroma file manager if you are rooted, if you can get into recovery. Then you can move whatever you want to an external SD card.
Other than that you're likely stuck.