Related
I am running the leaked T-mobile froyo rom on my defy.
Today i found my phone not responding. it was stuck in the motorola logo for a very long time and did not load any further.
I decided to reflash my phone with the SBF again to see if i could just start over.
However, when i try flashing the phone, i get stuck at the "erasing flash memory" step.
Is there a hardware problem on my phone? I guessing there may be something wrong with my internal flash memory. Any suggestions?
Thanks!
Here is my solutions, (no guarantee if it dont work or do damage the phone)
Enter the bootloader and re-flash it with RSD lite. Sometimes it will fail when flashing the Code Group 37, ignore it and restart the phone in to bootloader and flash again.
get into recovery mode full wipe
make sure you have the latest version of RSDlite too
Thanks for the replies!
Ok, so i've tried to reflash the sbf several times with the latest rsd lite (4.9) with no luck. The progress gets stuck at "erasing flash memory" and eventually i get a Fail message.
Unfortunately, I cannot access the recovery mode anymore, because i get a "corrupt code" error now due to the failed flashing attempts.
Also, my battery is low now, and it seems like i cannot charge the battery without a firmware. I'm trying to find an alternative way to charge my battery.
If anyone has any other ideas; I would much appreciate it!
Thanks again!
I can't see how it won't reflash?
If it's in bootloader (power & Vol up) then you select the .sbf file it should work?
I didn't realize that it checked the version on your phone?
A little out of the way method to charge your phone.
http://forum.xda-developers.com/showthread.php?t=892026
use the method above to charge your battery and use a linux live cd or boot linux if you have it installed, download a file called sbf_flash and the sbf, copy both to your home directory. Throw up Terminal and run:
sudo chmod +x sbf_flash
sudo ./sbf_flash blahblahblah.sbf
Thats it your done! I don't use RSD anymore because it refuses to work anymore for some reason. The linux method always works for me. Obviously replace blahblahblah.sbf with the correct sbf file name
This will sound nuts as well, but also try flashing on another pc with rsd lite installed.
I couldnt get rsd lite to work on my main pc, (kept getting a flashing failed message).
I installed it on a laptop and it worked fine, the first time.
Thanks for all the suggestions! i'm going to try this once i get home from work.
I feel practically naked without my phone, can't even focus.
I'm really hoping there isnt any hardware problem. Prior to my phone locking up, i noticed several times my CPU usage increased to 100% and would not go back down. I checked my task manager, but couldnt find any apps or services utilizing the CPU to that extent. I had restart my phone to reset the CPU usage.
It could have been a dodgey application.
Was your phone rooted prior to you attempting to flash it?
If so, how did you root? Did you install any custom recoverys?
i dont have any custom recoveries and i rooted with superoneclick
I used the cut USB cable method to power my phone back up. (Thanks!)
I have tried flashing with a different version of RSD lite as well as flashing from a different machine with no luck.
It looks like I'll have to try flashing from linux. I'm not very familiar with the linux environment. Is there a more detailed guide to doing this through linux?
I found a Ubuntu 8.0 CD lying around. I'm hoping to use this.
Thanks again!
zyxwvut, I tried out your method of flashing my phone through linux.
I used ubuntu 8.0 (booted from CD... didn't install anything)
Unfortunately, it didn't help. I'm still getting a flash memory erasing related error.
I have included the error message below:
--------------------------------------------
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
usb_bulk_write -2
!! failed
>> rebooting
usb_bulk_write -2
--------------------------------------------
Sorry to be a pain, but does anyone have any other ideas? Is there a way to manually erase my flash memory? Thanks a ton to everyone for your help so far.
Try to take out battery for 15 minutes. Use this time to download another stock rom (maybe a later release than your old one -> downgradeable). Maybe your downloaded file is broken.
Got stuck in different stages flashing my phone and many times I thought it was finally bricked; but I always could recover it somehow.
Good luck!
Thanks for the suggestion.
I have tried several different roms; even just bootloaders with no luck.
I believe the sbf i am using now is fine because i have successfully flashed this exact file just a month ago.
What's the last ROM it works? flash that sbf may help
The last rom that I flashed that worked was the leaked froyo US T-mobile rom. It is also the rom I have been trying to flash with no luck. =/
hmmmmm. Strange...... I have had several failed flashes. Upon reboot It's gone straight to bootloader with "code corrupt" message.... sbf_flash always seems to work! I say be persistent and keep trying? Maybe you've gone and FUBAR'd your phone..... That sux though! Let us all know if you get it going and how you did it.
On a side not... The leaked froyo from US t-mobile is system version 34.4.9, the exact same version that they just released and made and OFFICIAL rom.... Maybe a warranty replacement is in line for you. If you were on the leaked US froyo, which is official now, and your phone doesnt get past bootloader, maybe they can't tell what you've done to it
Here is the easy solution but need time and minimum $5 charge..
Just sent to Motorola with RMA. (Depends on your warranty, but mine was free except USPS flat rate box.)
Then they send back with froyo version of defy!
I sent mine with same brick issue 2 weeks ago - I installed 2.2 from other countries and rooted and rolled back 2.1, then I got froyo version of defy today.
I have 34.4.9.MB525.T-mobile.en.US (2.2.1) now.
You don't need to tell them too much, I think. Just say, Hang, not boot up.
I read somewhere that sbf_flash will not work properly on linux kernels below 2.6.30
I believe that Ubuntu 8.0 uses 2.6.24 kernel ( I could be wrong about that though )
Try using a newer linux distro with kernel 2.6.30 or above.... I'm thinking that this might work for you!
Also, I think that possibly trying an entirely different distro could help not that Ubuntu isn't capable but maybe theres a weird bug or something. I use Linux Mint live session
Let us know
Sending it back for warranty is the easy way
out LOL! Solving this could help a lot of people in the future
Hi there
FIrst of all sorry for the way i'm talking but well im a foreigner and sometimes make mistakes.
To the point. My Note 2 had Ditto DN4 flashed, it was working fine BUT today it just decided not to. It kept rebooting after 4 sec every time so i decided to reflash rom, i did it aaand still the same problem. Ok then, i grabbed this '3 files ROM with PIT file', sorry but i don't know the proper name. Either way, i tried to flash it using odin and thats when things started to go crazy. For some reasons it did not flashed and i was left with just DOWNLOAD MODE! I have no idea why but odin kept saying FAILED after NAND WRITE line. I panicked, flashed it like 45416165415 times but still did not work. After i read a few threads i thought, that i bricked the device BUT i thought what the hell, I'll flash recovery again aaand IT WORKED!
So now, what I'm asking for. Can anyone tell me what are the steps now? What ROM should i flash, if i had MJ5 bootloader? (well i think so, in Ditto thread they say that it works only on MJ5 but i don't really remember whether i did flash it or not). I'll be really really gratefull for any help. I just don't want to ruin it after that recovery flashed.
Unbelievable things happens frequently when using a custom rom or kernel ，especially on the device like N7105.......My pac-ROM got crashed when converting an app to system folder with Ti-backup and reboot，it blacked screen after the first logo screen， and failed enter recovery despite I pulled out battery. When I got crazy and was about to work it out with odin and it entered rec.....I think maybe the single tar.md5 file will help the most......If you a lucky enough
I have a note 2, that I swear, the Flash is read-only. No odin is capable of writing and actually "sticking". The little bar in the download window on the phone scrolls across, odin says it's successful, resets, and nothing. I've tried openrecovery, cwm, I've flashed stock, I've reflashed kernels, but absolutely nothing seems to allow odin to actually change the bits on the phone. I boot into cwm, switch to download mode, flash twrp, everything scream success, and recovery is still cwm. I flashed stock AT&T releases, it's still cwm.
And the problem is, it appears to be a corrupted cwm, or my partition table is wiped out, or something, because cwm has errors about accessing cache.
Before I toss it in the trash, I want to take one last crack at fixing it. I've watched youtube videos, I've downloaded more large odin files than I can shake a stick at.
Any last suggestions, before one of my favorite phones becomes a piece of electronic trash being ground up for precious metals? All 6 nanograms of 'em?
I'm even willing to try crazy stuff.
Have you tried flashing with a pit file ?
Sent from my SM-N910C using XDA Free mobile app
+1 on repartition
Yes, i317 pit file.
Last round lf flashing was the 4.3 param/sboot, MJ4 kernel. All show green success in Odin, all don't actually seem to actually do anything.
I tried to see if I could sideload from inside cwm recovery, but my device isn't recognized. It gets the model name, but isn't able to match it up with a driver in device manager. I've tried Kies on 2 different machines, it thinks it's all just fine, tells me I'm all recovered, and nothing.
I swear it thinks that flash is a nullfs.
If the bar didn't go across the screen on the phone, I'd look harder at my computer, but the little blue bar scrolls across at the same rate, it all looks like it should.
I've had a horrible run of luck these past couple weeks.. Deep 2nd degree burns, two broken s6 edges from sliding off surface, and a drop all at short Heights, even with case on.. So now that I was laid up in bed recovering from work accident I decided to get my tmobile p607t I just picked up and my edge all sorted out.. This is what I did:
Downgraded from 4.4.4 to 4.4.2
Towelroot and supersu
Installed titanium backup
Decided to install custom rom and make nandroid backup
Installed flashify
Erroneously installed twrp for nexus 6 (it's a real ****ty mistake I wasn't paying enough attention, probably pain killers had something to do with it and didn't realize that for all the mentions of the note in the article that they were actually linking to nexus 6 twrp)
Flashed twrp with flashify, reboot, and would only boot into download mode
Booted into odin tried flashing the same stock 4.4.2 knowing it probably wouldn't fix problem, errored out, unsuccessful
Read something about flashing twrp with odin so tried that, it didn't work, heard cwm may work with odin, Unplugged tablet from pc, power cycled, started up with black screen.
Found out it was on by plugging back into pc and odin showed "Added"
Power cycle odin shows removed and added again.
Installed adb/fastboot and drivers via installer (win7 x64)
Just so see what was going on with tab figured I would try to flash stock again to see what error was, so I would be able to mention it in this post, says no pit partition and screen is still black..
This is the point where I decided to post, during all that I did read a lot and did try searching around for something model specific, but am really concerned about doing anything else without advice.. Not really sure if it's even fixable, but hoping that because odin still sees it, maybe it's not a lost cause.. Even if it is just pointing me in the right direction it'd be helpful. I'd be willing to donate to xda's server costs if it takes really in depth help, I've benefited a lot from the site over many years and never really had to post before because I've never had any real issues, usually much more thorough with reading things. Thanks in advance.
I have family coming over so will more than likely be back to working on it tonight..
Edit:
Jesus in doing a horrible job at life.. Posted in wrong sub.. Should be in note 10.1 2014 forum, please move to correct forum.. Sorry
Edited to add:
It's fixed, I located pit partition file, loaded that and stock rom in odin, attempted to flash but it failed, power cycled and download mode appeared on tablet, without error and odin automatically began flashing, everything is back to normal..
defcomexperiment said:
I've had a horrible run of luck these past couple weeks.. Deep 2nd degree burns, two broken s6 edges from sliding off surface, and a drop all at short Heights, even with case on.. So now that I was laid up in bed recovering from work accident I decided to get my tmobile p607t I just picked up and my edge all sorted out.. This is what I did:
Downgraded from 4.4.4 to 4.4.2
Towelroot and supersu
Installed titanium backup
Decided to install custom rom and make nandroid backup
Installed flashify
Erroneously installed twrp for nexus 6 (it's a real ****ty mistake I wasn't paying enough attention, probably pain killers had something to do with it and didn't realize that for all the mentions of the note in the article that they were actually linking to nexus 6 twrp)
Flashed twrp with flashify, reboot, and would only boot into download mode
Booted into odin tried flashing the same stock 4.4.2 knowing it probably wouldn't fix problem, errored out, unsuccessful
Read something about flashing twrp with odin so tried that, it didn't work, heard cwm may work with odin, Unplugged tablet from pc, power cycled, started up with black screen.
Found out it was on by plugging back into pc and odin showed "Added"
Power cycle odin shows removed and added again.
Installed adb/fastboot and drivers via installer (win7 x64)
Just so see what was going on with tab figured I would try to flash stock again to see what error was, so I would be able to mention it in this post, says no pit partition and screen is still black..
This is the point where I decided to post, during all that I did read a lot and did try searching around for something model specific, but am really concerned about doing anything else without advice.. Not really sure if it's even fixable, but hoping that because odin still sees it, maybe it's not a lost cause.. Even if it is just pointing me in the right direction it'd be helpful. I'd be willing to donate to xda's server costs if it takes really in depth help, I've benefited a lot from the site over many years and never really had to post before because I've never had any real issues, usually much more thorough with reading things. Thanks in advance.
I have family coming over so will more than likely be back to working on it tonight..
Edit:
Jesus in doing a horrible job at life.. Posted in wrong sub.. Should be in note 10.1 2014 forum, please move to correct forum.. Sorry
Edited to add:
It's fixed, I located pit partition file, loaded that and stock rom in odin, attempted to flash but it failed, power cycled and download mode appeared on tablet, without error and odin automatically began flashing, everything is back to normal..
Click to expand...
Click to collapse
Really unlucky but in my country we use to say good end everything good. I hope to have better days from now on.
Sent from my GT-N7100
Thank you, yes things are starting to look much better. Burn is healed, my devices are working as they should..
Hey All!
I have this very interesting problem with my SGH-T989D.
I have for years been installing customs ROMs unto my phone. The last ROM I used was CM11 20141201 Sultan Hercules, with the provided GApps. This was installed using CWM 6.0.4.3. I ran this for months with no issues. Earlier this week, I decided I would try something else. I rebooted and went into CWM recovery and did a few things first. I went and Fixed permissions, and formatted various partitions, and also did a factory reset/wipe of the device. Now when I fixed permissions the time it took seemed odd too me. Like almost a minute, and since then I have been having install issues like crazy. So, I basically ended up using ODIN 1.85 to flash a stock ROM I had from T-Mobile. Which seemed to work fine. When i was satisfied the phone was functioning properly, I then proceeded to install CWM 6.0.4.3 using ODIN. It flashed successfully, and it rebooted my device. However, it brought me to the ODIN emergency download window. where it tells you to plug in your phone to the pc and use KIES to recover to the device. Ok, fine I thought to myself, I'll try that. Now KIES doesn't recognize my device. It's definitely not a driver issue because it used to work fine before these problems. I am assuming it has something to do with the firmware counter on my device. Since it says it's at 6 now, even though it's an official ROM. I have also tried using Lorains thread to re-partition the internal memory using the his unmodified PIT file. But Odin crashes at the SET PARTITION screen when trying to flash it So, honestly I'm at a dead end as to what's going on with my device at the moment. Even when I try to flash an early stock version of a Telus ROM, it just keeps going back to emerg ODIN screen, even though ODIN flashes successfully.
Does anyone have any suggestions for me? If you require more information I will do my best to answer.
Thanks a million in advance.
DrexxHaze said:
Hey All!
I have this very interesting problem with my SGH-T989D.
I have for years been installing customs ROMs unto my phone. The last ROM I used was CM11 20141201 Sultan Hercules, with the provided GApps. This was installed using CWM 6.0.4.3. I ran this for months with no issues. Earlier this week, I decided I would try something else. I rebooted and went into CWM recovery and did a few things first. I went and Fixed permissions, and formatted various partitions, and also did a factory reset/wipe of the device. Now when I fixed permissions the time it took seemed odd too me. Like almost a minute, and since then I have been having install issues like crazy. So, I basically ended up using ODIN 1.85 to flash a stock ROM I had from T-Mobile. Which seemed to work fine. When i was satisfied the phone was functioning properly, I then proceeded to install CWM 6.0.4.3 using ODIN. It flashed successfully, and it rebooted my device. However, it brought me to the ODIN emergency download window. where it tells you to plug in your phone to the pc and use KIES to recover to the device. Ok, fine I thought to myself, I'll try that. Now KIES doesn't recognize my device. It's definitely not a driver issue because it used to work fine before these problems. I am assuming it has something to do with the firmware counter on my device. Since it says it's at 6 now, even though it's an official ROM. I have also tried using Lorains thread to re-partition the internal memory using the his unmodified PIT file. But Odin crashes at the SET PARTITION screen when trying to flash it So, honestly I'm at a dead end as to what's going on with my device at the moment. Even when I try to flash an early stock version of a Telus ROM, it just keeps going back to emerg ODIN screen, even though ODIN flashes successfully.
Does anyone have any suggestions for me? If you require more information I will do my best to answer.
Thanks a million in advance.
Click to expand...
Click to collapse
I think you might have to re-partition your phone. Sultan's ROMs partition your phone a certain way and there is a fix for your phone somewhere on here to allow you to install regular types of custom roms.