Had a motorola droid pro given to me. Don't know much about it. Seems cool enough to tinker with or maybe use on straight talk as a backup phone. It starts up and stops on the red animated logo. It stop starts a couple of times then stops completely. While this is happening it also fades out and dissappears, like normal screen timeout almost. Can achieve bootloader screen but cant find a recovery. People have said there is a stock recovery even if it has not been rooted. Cant find it and dont know if the phone is rooted or unlocked. Seems like it is searching for something to load and just gives up. Since bootloader screen comes up i can probably fix this i would think. Maybe through odin. If i can get cwm on it i should probably be good from there. Need some guidance from someone with odin exp to point me in the right direction so i can fix it myself. What do you think ????
SCH-I535 /MOAR/Wasabi83/xda-app.
Found proper cwm and odin. Cwm has no tar file, nor is there one that i can find to download.Really don't matter cause the odin control panel don't recognize the phone. Downloaded new drivers, it makes the noise when i connect it but thats it.
SCH-I535 / MOAR / WASABI 83 / using tapatalk pro
Related
have searched many hours days an stressed trying to find ANY! answers bricked my samsung moment wont do anything wont power up wont boot into recovery nor download mode to get it to show any signs of life have to remove battery an put it back in then it will show charging when plugged up when i hit power nothing but phone still gets warm any help i would be forever GREATFULL
What happened to it? A little more details would help in resolving your issue...
recovery
was in recovery mode custom recovery 3.1.1 froycystos was running dj07 update rooted on inxane 4,2 kernel flashed noobnls new kernel with updated video drivers cant remember exact build but its noobs newest it was have way through flashing loading bar was half way to be exact an then like the show the office "BOOM ROASTED" phone just cut off half way through flash an went black now its deader than my sexlife LOL ok maybe tmi but im a young guy an woman just make no sense but sorry a lil a.d.d but thats what happened with the phone so been frustrated at the phone an other circumstances
walloftext
Sent from my HTC Desire using Tapatalk
Dont freak out yet.
Huh. Thats kinda strage that it wont even boot into recovery, Becasue when i thought i bricked my droid incredible, I had to go into the recovery menu tell it to mount my phone as a disk drive, After that i had to put the OS back on my phone though a zip file,(Htc sense is my OS) And do a factory reset. So the chances of your phone being bricked are very slim its difficult to birck an android phone but i would try to find a method that will allow you to hook your phone up to your computer so then you could just find your OS as a zip and install it on your phone.
how
no way to find it computer doesnt see my phone nor will the phone do anything wont boot in recovery or download mode or boot period for that matter
It would REALLLLLLLY help if you used punctuation. Commas, periods, and capital letters really help people to read your garbled mess.
I know this was really stupid cause I'm kicking myself right now,but I tried to flash CM7 and didn't flash the update before I rebooted my phone. Now my phone comes on and shows the vibrant screen as usual and goes to the cyanogen mod screen and then goes black after that. I can't get into recovery with the three button method and I have a mac. So I can't use Odin, even though I can get into download mode. Does anyone have any suggestions? I really don't want to try and go through the process of ordering a new phone, even though I do have insurance.
i did also need help.
Need help
I did also!!
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
hechoen said:
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
Click to expand...
Click to collapse
I didn't feel like i really hard bricked it until i saw the USB computer connection error "device pluged in malfunctioned" in more than one PC.
Then i really felt like its a hardware BIOS chipset level problem now but man...
That story cracked me up. That is exactly why I spend days reading before I even root my phone. I made the mistake one time on my old G1 and it could not be revived.
Congrats on getting it working. (especially without flooding the q&a with redundant questions that have been described in detail several places )
hani1400 said:
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Click to expand...
Click to collapse
Wheooooooooowwww,..you just UNBRICKED mine, I know of the Battery pull etc...but the post you referenced
is MAGIC
This was not my first Rom nor Root on this phone, it weirdly happened while doing the GB starter....via ODIN, which i also used before..no clue what went wrong, oh well...
Thank you, thank you "i did"....Yohoooo
Yup i agree i like to read, reread then read as i do. This way i got a pretty good understanding of what I'm doing. Btw i have just started using one click and it is sooooo simple. I love it.
Sent from my SGH-T959V using XDA App
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
diavel said:
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=881162
Im still carrying this phone, stupid baseband unlock for iphone won't come out now I am carrying 2 phones, one as an ipod touch and the galaxy s! Good story, hope it can help others, but I am prepared to jump off of this bandwagon anytime now!
Hi all,
I've spent a good two hours trying to figure this out. Generally I'm pretty good at these things, but there just isn't that much action or information on the Blu Life Play when things go wrong (L100a)
http://forum.xda-developers.com/showthread.php?t=2370987
In reference to the above link, I followed all instructions to a T. My phone is rooted just fine, all that is working perfectly. However, once I tried installing CWM using the first method, mobileuncle, not only did it fail, but it also entirely broke my recovery mode! Whenever I try to boot into recovery (vol+/power) I get a black screen until the phone eventually reboots itself.
I then tried method two using the flashing tool, SPFT. I used something similar pretty often, ODIN, with my old Samsung Epic. Again I run into a problem: I can't keep the phone connected long enough to allow SPFT to finish flashing the recovery. As instructed, I plug in the USB cable with the battery out, my computer chimes to let me know it has recognised the device, but- Three seconds later, it chimes again to let me know it has disconnected.
SPFT follows suit, detecting and starting the flash then getting interrupted 2 seconds later.
My phone is still able to boot, it is not bricked. However, it is very distressing to have no access to a recovery mode.
Help?
I have the same issue. Got my phone replaced under warranty and the new one I got yesterday will not boot to recovery. Only black screen. Hopefully we can figure out the issues.
issact said:
Hi all,
I've spent a good two hours trying to figure this out. Generally I'm pretty good at these things, but there just isn't that much action or information on the Blu Life Play when things go wrong (L100a)
http://forum.xda-developers.com/showthread.php?t=2370987
In reference to the above link, I followed all instructions to a T. My phone is rooted just fine, all that is working perfectly. However, once I tried installing CWM using the first method, mobileuncle, not only did it fail, but it also entirely broke my recovery mode! Whenever I try to boot into recovery (vol+/power) I get a black screen until the phone eventually reboots itself.
I then tried method two using the flashing tool, SPFT. I used something similar pretty often, ODIN, with my old Samsung Epic. Again I run into a problem: I can't keep the phone connected long enough to allow SPFT to finish flashing the recovery. As instructed, I plug in the USB cable with the battery out, my computer chimes to let me know it has recognised the device, but- Three seconds later, it chimes again to let me know it has disconnected.
SPFT follows suit, detecting and starting the flash then getting interrupted 2 seconds later.
My phone is still able to boot, it is not bricked. However, it is very distressing to have no access to a recovery mode.
Help?
Click to expand...
Click to collapse
zironia said:
I have the same issue. Got my phone replaced under warranty and the new one I got yesterday will not boot to recovery. Only black screen. Hopefully we can figure out the issues.
Click to expand...
Click to collapse
Hey, it's good to hear I'm not alone in this. lopestom has been friendly enough to correspond with me about it and he suspects it's a new model of the same phone. I sent him a screen cap of the factory settings screen (VOL-/POW)
In the end we might be out of luck until more people get their hands on the new version of the phone.
Just for reference I have a p5113 model.
A while back I put Cyanogen on my tablet. A few months ago I cracked the screen, only a bit on the corner, of course I can't stand cracked screens so I ordered a replacement. When I installed the screen everything connected fine and dandy so I tried to start it up, but when I did the touch function didn't work. I thought maybe it was just a bad screen that I had ordered, so I got another. When I got the second screen in I replaced it, but this time it was doing the same thing as before where the touch wasn't working! I made sure everything was connected okay and also checked for anything damaged, but everything seemed fine. For some reason I thought maybe hard resetting it would help, but it didn't. At this point I was just trying to get the stock 4.2.2 firmware back on it. I downloaded the firmware, used ODIN to get it onto the tablet. When it restarted after the firmware was loaded on, it was stuck in a bootloop. I heard that it may just need to be factory reset again so I tried to get into recovery mode, but only goes into ODIN/Download mode, which is what my final problem is here.
TL;DR Tablet will not go into recovery mode. Only ODIN/download mode.
I haven't been able to find ANYONE else that has had this problem before. So if anyone knows the source of my problem, I would be very appreciative of your help.
Well you could have fried the capacitive touch circuit with a static charge I have no idea what your skill level is also you could have a bad image or you could have bonked the hardware and it doesn't detect critical boot hardware I'm not that well versed in firmware related boot issues but hopefully some helpful nerd can give you a hand you could also just try again aster you download a new IMG
Sent from my toaster
Samwise13 said:
Just for reference I have a p5113 model.
A while back I put Cyanogen on my tablet. A few months ago I cracked the screen, only a bit on the corner, of course I can't stand cracked screens so I ordered a replacement. When I installed the screen everything connected fine and dandy so I tried to start it up, but when I did the touch function didn't work. I thought maybe it was just a bad screen that I had ordered, so I got another. When I got the second screen in I replaced it, but this time it was doing the same thing as before where the touch wasn't working! I made sure everything was connected okay and also checked for anything damaged, but everything seemed fine. For some reason I thought maybe hard resetting it would help, but it didn't. At this point I was just trying to get the stock 4.2.2 firmware back on it. I downloaded the firmware, used ODIN to get it onto the tablet. When it restarted after the firmware was loaded on, it was stuck in a bootloop. I heard that it may just need to be factory reset again so I tried to get into recovery mode, but only goes into ODIN/Download mode, which is what my final problem is here.
TL;DR Tablet will not go into recovery mode. Only ODIN/download mode.
I haven't been able to find ANYONE else that has had this problem before. So if anyone knows the source of my problem, I would be very appreciative of your help.
Click to expand...
Click to collapse
sounds like a damaged digitizer to me.
may as well get a new tablet as digitizers tend to cost almost the same as a new device...
now... recovery...
this may sound redundant but try flashing the firmware again. when it flashes make sure it says "recovery.img" or similar at some point in the Odin log.
be sure to use the correct pit file and the repartition check box when flashing.
there are usually two or more firmwares per tablet so if one fails to boot recovery try the other.
the site I find that has reliable files is samsung-updates.com but be prepared for slow downloads averaging am hour and a half.
Sent from my SGH-T999 using Tapatalk