Database Users

[solved] Possibly bricked only the recovery partiton?!

okay so after trying some other options i was able to solve this problem, here is the how to in case this has happened to anyone else. my original post is below the how to.
1.flash the sbf that returns your defy to stock eclair using a different T-Mobile sim, after it is done flashing you will seem to still have the problem, except it will say no sim emergency calls only.
2.power off the device and install your original sim from T-mobile.
3.reboot the device and you will not be prompted to setup motoblur, because you device is in soft brick limbo still, but you will have laggy touch responses, be patient with your device as you navigate to settings>privacy>factory reset and confirm. ( this process will take much longer than usual and the progress bar will not show any progress but it will shutdown and reboot as it normally would with a factory reset)
4. you will now be prompted to setup your motoblur account ( if you are not restart the steps until this happens, if it does not happen your device did not actually do a factory reset you will need to try again until it does ask you to setup blur, this is your sign from the moto gods that your device is no longer in softbrick limbo)
5. setup your blur account ( you will still have no recovery menu at this time so don't try and check or you will have to start back over at step one)
6. now navigate to settings>about phone> check for updates
7.download and install the update to froyo ( durring downloading you phone may shut off several times, however if you reboot it will automatically pick up the update where it left off as if your device never powered off to begin with)
8. once you have installed the update you device will be back to froyo stock and your recovery partition will no longer be bricked
9. enjoy your defy once again, and be more careful with your device in future ROOT mods and tweaks, cheers!
10. If this helped you recover your device please thank me for this solution.
okay so i am new to posting on XDA and i will try to organize my problem as best as possible, but i may need much guidance on if i am posting in the proper forum.
here are my details of my device and the problems i am facing with my device currently.
Motorola Defy
MB525
T-mobile US
stock Froyo rom 2.2.1 ROOTED overclocked with milestone overclock to 1224 mhz @ 85% voltage /V6 SUPERCHARGER SCRIPTS. MODDED BUILD.PROP TO REFLECT THE MAX HSUPA CATEGORY 34/MAX HSDPA CATEGORY 36/ GPRS CLASS 10/ HSXPA=2/RO.RIL.VIDEO_MODES=TRUE EVERYTHING ELSE IN BUILD.PROP WAS STOCK EXCEPT WHAT THE V6 SUPERCHARGER SCRIPTS CHANGES. I was running a custom bootscreen that i placed in the location of the old one using ES file explorer with root browsing rights, i had defy Recovery installed but only used it basically as a system restore app ( context of previous statement is relating to system restore if you were talking about a windows machine) used Avast anti virus as root installation w/antitheft installed used system tuner to manage startups down to core services or other services i did want to run at boot i.e. stuff like facebook and weather channel.
DEVICE WAS ALSO SUBSIDY UNLOCKED
SBF started with and reflashed to try to correct problems was JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.OR_JORDANTMO_PO22_HWp3_SERVICE1FF.sbf
****NOW TO THE PROBLEMS****
I was starting to think that maybe the v6 supercharger scripts were not really doing anything performance wise for me as it would disable my overclock settings at boot and i would have to manually invoke them after everything had requested its SU rights at boot. so i decided to get rid of the v6 supercharger scripts and all other softwares pertaining to managing and running the scripts, I decided the best way to do this was to do as i had always done in the past when wanting to re-tweak my phone and use the stock recovery to start fresh with 0 tweaks and only apply the ones i wanted after restoring to stock, when i used the stock recovery this time it didn't work, i booted the phone back up after wiping data/ factory data reset and to my surprise the recovery did nothing but delete the SU.apk the custom boot was still in tact, everything else listed above still in tact except for the phone was obviously throwing errors left and right because there was no SU for apps to request permissions from, so i reinstalled the SU.apk just to make sure i didn't have to deal with the device being slow while restarting the process of doing a full wipe. this time i used the DefySDrecovery.apk i mentioned above to do the same steps and while adding wiping the dalvik cache after wiping data and before invoking the recovery, it then gave me the same error i have always gotten when wiping the cache which is
e:\ cant mount cache partition
e:\ cant find /recovery/caller
e:\ cant find/recovery/cache
(this has never caused problems with the device once recovery was finished)
this time however I was only able to boot(loop) to the moto logo
so i reflashed The above mentioned SBF and the device booted normally i went through the entire setup like it was a new device with blur and google and it finished. when I got to the home screen it was frozen and would not respond to touch it also showed to have no cellular signal, i turned it of and back on and it made me go through blur and gmail setup again, went to home screen same thing frozen with no signal.
i reflashed the SBF again thinking maybe something went wrong as they do sometimes with RSD yet still finished and passed on everything
the above description repeated except for this time it responded to touch for the first few seconds before it froze completely ( oops! sorry one detail to add when i say it froze i mean froze like would respond to nothing, touch, hardware buttons, nothing) i had to pull the battery in both instances to try and start over, after many attempts of getting in the phone and trying to turn on usb debugging before it froze i finally was able to complete the finger olympics and get usb debugging turned on, i was able to root it using superoneclick so that i could have a look at the logcat in ADB. now in my experiences with ADB normally when you run a logcat command it will print to the screen for about two to three hundred lines and then slow down and only print one to six lines at a time as the server is calling actions when i ran a logcat on this device it runs two to three hundred lines slows down and then runs lines until you close the ADB window i let it run a logcat overnight and it was still running lines the next morning with no sign of stopping where you could freeze the window and read over all the crap it was calling to action, looking at the device durring this process i saw force close windows a few times saying the com.android.process has stopped but the home screen never crashed and the phone didn't do a random reboot. so to sum it all up ( so sorry for the lengthy explaination but i wanted you to have the whole problem fully explained in hopes you wouldn't have to ask for more detail)
it freezes and has no service with my T-mobile sim in it ( if i put my at&t sim in it has service but still freezes)
flashing a new SBF doesn't fix the problem as it should
and there is no way to enter the Recovery Menu now its gone, non existant, cant find it, cant fix it, i'm F***** right now Please help if you know how, and if i totally screwed the phone i'm cool with you saying so but it can still be in a respectful way i already feel like an idiot for not being able to correct this with all the knowledge i have of this phone, a negative attitude insinuated is not going to help me in either direction, thanks in advance for any help you may be able to provide.

[Q] green defy fixed sbf flashed no gapps or phone service

Hi All,
Please HELP.
I was a complete noob to rooting until I started this but spurred on by successfully rooting and overclocking / undervolting my defy I thought I would try to install Gingerbread so I can use the stupid stupid sky+ app which no longer supports 2.2.2.
Its all gone horribly wrong and I still dont know why as I checked and rechecked the prep but S..t happens so they say.
I have pretty much given up on this and will buy a new phone tomorrow if I cant sort today but would like to ask everyone that has more knowledge than myself on this subject (which doesn't narrow the field much!) if they have any ideas.
Well where do I start, I bricked my defy.
Apart from when I flash shadows rom (see below) I have only black screen, white led on usb connection, no recovery boot. phone is visible to rsd lite but nothing else. This happened after I lost sd card availability after reset / wipe trying to install a fixed gingerbread rom using RSD lite.
I could not flash back to froyo and every other recovery sbf i tried wouldn't work until I found an old sbf from shadow which actually booted up! YESS!! but then Nooo!. phone screen looks very nice - not sure what version it is but assume ICS (its got spareparts folder which I`ve not seen before) - and works as alarm clock and web browser but no phone function at all - no signal, no call or end call buttons - just not there! this (http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143) is the link where I found shadows version, couldn't wipe in between each step so just flashed 3 files in turn using rsd lite and it seemed to work - phone booted up after 3rd sbf was flashed. The rom is set up for developers and has some developing tools included acr, api demo,dev tools, hstcmd & redlinecap
Main problems:-
The rom is a tmobile version and I`m on vodaphone so maybe this is why there's no phone service but I wasn't prompted for an unlock code so assume its not locked.
The 2nd boot recovery no longer works even after reroot and reinstall (see below). I can surf the web very well via wifi - much quicker than before but downloads dont seem to work but only tried shortfuse.org and that site is apparently down atm and anything that requires google wont work as Gapps got deleted. I cant install GAPPS without boot menu.
recovery from main boot menu is unavailable and zip from sd just reboots.
I also cant connect my phone to my pc via usb and have the sd card available at the same time, as soon as the USB is connected the sd card is not available to the phone, I can see it on the pc and can read / write / delete from the pc - (usb debugging is disabled). when I access the sd card via file manager on phone (with usb disconnected) I can install some programmes that I have transferred from my pc; 2ndinit installed and said 2nd init installed ok again (after re-rooting) but still no blue led on reboot.
I've since tried everything I can think of or search for - After loosing the sd card availability I copied card contents to pc and reformatted sd card on pc. copied back the files immediately before flash attempt to sd as well as the rooted froyo backup I had and nothing changes. I have a titanium backup on the card but have so far been unable to install titanium again to try and restore it. no play acces as no gapps and when I try to access via pc and send it to phone it says installed but its not on the phone. every other file on the sd card results in error parsing file or file type not supported.
BTW when I say originally that I lost sd card availability I have now realised that it was the problem with having the usb installed at the same time which caused it and if I had unplugged it may have worked but still dont understand where this problem came from but I did have usb debugging turned on at the time.
I have scoured these holy pages for 2 whole days and tried several fixes which have probably really messed up everything even more but nothing has changed with the usability (or not) of the phone. A lot of the old links found were dead or taken over by a fake install of filemanager that my antivirus caught was a trojan. Due to this I may have missed an avenue or 2 but think I`ve tried everything I can.
At this stage I do not know exactly what I`ve tried as the list is endless but it includes reflashing the green lense kernel, attempting to reflash the original rom and any other recovery, fixed or stock roms I have found which don't specifically say only for defy+ and the only rom that allows the phone to boot is shadows above and that has no functionality.
I would love to install the latest cm10 build but cant get into the 2ndinit menue so unless someone knows away to flash it using RSD lite I`m stuck.
I do not even know if the cm10 would work as I`ve probably messed up the kernel and the original rom so the 2nd init may not get a look in.
Any help would be greatly appreciated. You'll find me under the stairs mumbling to myself and probably dribbling a bit - my wife thinks I`ve gone mad and is not talking to me until I get another phone or fix this one but I hate admitting defeat on technical problems.:crying:
PS I dont mind if I fix the issues with shadows rom, go back to any stable build or get cm10 working I just need the phone.
Thanks in advance, Tim

update
Hi All,
Just a quick update on this thread as I`ve had a bit more of a play and think I`m getting somewhere possibly.
I have now eliminated the problem of not being able to see the sd card files in file manager when the usb is connected.
How? - i haven't got a clue, i just unsuccessfully tried flashing a few more roms and when I reinstalled shadows rom i could view files whilst connected.
Also the 2ndinit now gives me the green led when it installed the 2nd boot but unfortunately I still dont get the blue led on reboot.
Another strange thing is I dont get the round M logo on boot but motorola written in white??
If I could just get to the CW recovery on boot I could install cm10.
Any suggestions?
Thanks
Tim

fixed by flashing with JDGC_U6_2.13.0
YESS FIXED BY FLASHING JDGC_U6_2.13.0 SBF using RSD lite.
Many thanks to everyone that helped via another thread http://forum.xda-developers.com/showthread.php?t=1217016&page=2, I thought they were far too many issues with this phone to repair but the latest froyo rom and kernal in the above sbf worked fabulously.
As has been said on several posts flashing this SBF will not allow you to return to the uk stock rom after (to return a phone under warranty etc) but if you're stuck with a brick then this should clean up your phone to original settings to allow the install of cm10 or another rom of your choosing (as long as its build 6 or later)

[Q] Major issue with Australian SM-9005, help!

Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.

zuuus said:
Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.
Click to expand...
Click to collapse
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.

ultramag69 said:
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.
Click to expand...
Click to collapse
Hey mate, last version of firmware was the Stock Telstra SM-N9005 / TEL ROM I found on www . sammobile . com/firmwares/2/
I have tried at least 10 different ROMs with no luck, every single one does the same thing.
I did send it off to Telstra to try for a repair, they sent it back to me unrepaired due to nothing to do with the software but a 1/4mm scratch my keys made in the chrome plastic around the edge with the words "unable to be repaired due to physical damage" with a little sticker pointing to the scratch. ****ing ridiculous if you ask me.
Honestly I don't know all that much to do with the modems and csc's so it might be that causing my problems but I have tried a bunch of different ones without any change.
At my wits end here, phone is just over 30 days old and I can't use the damn thing.

try odin back to stock, then use kies to "emergency firmware restoore" Kies can be a life saver in some situation, make sure you use beta 3 version

[Q] [SOLVED] Adventures in CM11, still can't connect to T-Mobile USA.

Hello,
I have a MB525 that I purchased retail in the United States so it was never locked to any carrier. Currently I'm a T-Mobile customer and have no interest in changing that. I have to say I love this phone, mainly because it seems indestructible. Even years later the battery life is still good, but the stock 2.2.2 Froyo has become something of a problem because many of the Apps I would like to use have started requiring newer versions of Android.
I can't stay in the past forever, but I'm not quite ready to give up on this device so I started looking around at my options, and would you believe I found lots of other people who have this device and have worked very hard to produce updated Android OSes for it, and who have reported reasonably good success updating the device. I figured, Its already out of warranty, so I can't void a warranty I don't have. I also figured I'm a reasonably intelligent individual and have enough experience with Unix like operating systems that even if I get in trouble, I'll be able to ask the right questions to get out of trouble. Guess what point I have gotten to?
I started following the guide wikiDOTcyanogenmodDOTorg/w/Install_CM_for_jordan The Framaroot Gimli exploit worked great. I installed bootmenu 6.1 and Clockwork Mod Recovery. Fantastic. At this point, I was able to enter CMR and backup my mostly still factory ROM. If I understand correctly this is a nandroid backup. I copied that backup off of my SD Card to my PC. From this point I felt reasonably confident I could try things and in a worst case scenario restore to this backup.
Now I happen to have a stock ROM that seems to be a bit rare online, Blur_Version.34.4.806.MB525.Latam.en.01, so I figured at this point I'd do a service and create a backup using CWM after having done a factory reset. So I booted into the stock recovery, did a factory reset, restarted, and the OS was in a like new state. Perfect. Rebooted into CWM, and made a second backup of the factory reset state. I copied this off the SD Card to the PC. Now I figured I was ready for real fun.
I figured, I might as well put the most recent Android version I could find that people were reporting success with. This appeared to be @quarkx Kitkat build. The thread is almost a year old and has 500+ replies and so I guessed that most of the major kinks would have been worked out by now. I followed the directions on quarx2kDOTru and installed cm-11-20141015-NIGHTLY-mb52x.zip from Quarx2k.ru, and low and behold it worked. CM11 booted and everything looked great. WiFi worked. Gapps worked. Play store started installing my apps.
There was one small problem. The phone refused to connect to T-Mobile at all. So I did the reasonable thing. I searched and learned about base band switching, and consulted T-Mobile on what would be the correct APN settings. Occasionally it would connect to AT&T for emergency calling, but it never connected to T-Mobile no matter what I did. From my home I was normally getting excellent signal on the stock ROM, so I am reasonably certain that the actual signal in the area was not the problem, and that this had to be some kind of configuration or software issue. A wiser person probably would have gotten on the forum and asked for help, but wisdom be damned, I wanted to do it for myself.
So more research and at some point I thought, Well, I'll go back to the Stock ROM so the phone will be usable again, and I'll take another crack at CM11 again later. It was at this point that I realized that CMR had been replaced with Team Win Recovery Project. This recovery looked to be more feature rich and easier to use, so I accepted that. I backed up my CM11 install. then went to restore my original backup. Well you might have guessed by now that TWRP and CMR don't use exactly the same backup formats. I saw no obvious way to get back to my backup and couldn't find information that would allow reinstalling CMR. This was the first warning signal I foolishly ignored.
At this point I started looking around for slightly earlier builds of CM11 that might not have had the the problem connecting to T-Mobile. Here is where things get fuzzy about how things got into this state, since the work was spread over two days at this point. Somehow between all the flashing backing up and restoring, the device got to a state where the OS never actually finished could do here is yank the battery and reboot into TFRP.
At this point, attempting to restore would just result in the messages 'E: Unable to mount '/cache' and 'E: Unable to mount '/data' in the terminal. So After searching around I learned that I probably needed to format /cache and /data because somehow they were broken. Terminal commands, I can handle this. I start reading up and find the correct command and parameters for the format, and I type into the terminal inside TWRP and low any behold format can't be found. I start looking around the directories in my file system from inside TWRP and I've got a complete directoty structure, but no files in any directories other than on /sdcard. Well fuuuu.
Not sure what made me even try, but copying any file from my sdcard into /data somehow put /data into a state where a TWRP restore would work. So at this point I was able to restore the CM11 backup, and my phone now boots into CM11, 11-20141007-NIGHTLY-mb526. But.... the cellular network still doesn't work.
But now I am wiser and I am back to the point where a wiser person would have asked for help. So... Help?
Is 11-20141007-Nightly-mb526 the best rom an appropriate rom for my device? I'm guessing I missed something because other discussions on this forum mention newer builds, and also, my device is definitely a 525 not a 526.
Is my baseband version EPU93_U_00.60.03 right? The baseband selector allows me to pick from three T-Mobile settings: 3.4.2.-107-4, 3.4.2.-107-9, and 6.xx.0, none of which seems to allow me to connect to the cell network.
Thanks in advance for any assistance offered.
Sorry for the long potato.

Here is what I did to fix my problem.
I started with the original backup of my stock rom, and I used the unyaffs.exe from this thread: http://forum.xda-developers.com/showthread.php?t=1199416 to convert my CMR backup into individual files. I then went into those files, and found \system\etc\motorola\bp_nvm_default\ and pulled out the original radio firmware from my device. From there I used advice from several pages to create my own update.zip, copied it to my SD card and I booted into TWRP and installed the zip there. Reboot and Voila, It connected right at startup to T-Mobile with the normal speeds I get from my home.
Bonus, I attached my zip in case anyone else comes across this and needs it.
My Device has an FCC ID of IHDP56LC1 if that helps anyone match their hardware.

[Q] trying to return to stock - tons of errors in the process

Up until now I had a Galaxy S4 running omega ROM with a custom kernel (can't remeber which) and every so often I experianced a SIM card remove and needed to reboot - the other day, my mom decided to switch cellular compeny, and I recieved a new SIM - It all worked fine, until the next day I got an invalid SIM error and the phone was not usable - So I decided I would return to stock incase it would help or atleast it will return the warranty and allow me to let someone else fix it.
I followed a certain guide in this forum in order to return it to stock, and when the phone booted up - I got a "process.android.acore has stopped working error" - constantly flashing - making the phone unusable.
I wiped the cache and dalvik cache and did a factory reset, and formated every mount on my galaxy - and reflahed the stock firmware - and it fixed it - but now I have a "Samsung keyboard has stopped working" error - making me unable to text ever (tried clearing the app cache and data -didn't work) - and it also shows up when I don't use the samsung keyboard.... and there is the invalid SIM thing... I am stuck and have no Idea how to fix this thing... so... any suggestions?

gilmishal said:
Up until now I had a Galaxy S4 running omega ROM with a custom kernel (can't remeber which) and every so often I experianced a SIM card remove and needed to reboot - the other day, my mom decided to switch cellular compeny, and I recieved a new SIM - It all worked fine, until the next day I got an invalid SIM error and the phone was not usable - So I decided I would return to stock incase it would help or atleast it will return the warranty and allow me to let someone else fix it.
I followed a certain guide in this forum in order to return it to stock, and when the phone booted up - I got a "process.android.acore has stopped working error" - constantly flashing - making the phone unusable.
I wiped the cache and dalvik cache and did a factory reset, and formated every mount on my galaxy - and reflahed the stock firmware - and it fixed it - but now I have a "Samsung keyboard has stopped working" error - making me unable to text ever (tried clearing the app cache and data -didn't work) - and it also shows up when I don't use the samsung keyboard.... and there is the invalid SIM thing... I am stuck and have no Idea how to fix this thing... so... any suggestions?
Click to expand...
Click to collapse
Hi,
I would recommend you to make a factory reset, flash another stock rom as your current one and then wipe again. Maybe your rom was damaged when you downloaded it.
Sent from my Galaxy S4 using Tapatalk

Update
Ok, I managed to download another keyboard and it fixed it... I still think it needs a better fix... I managed to get it to recognise the SIM, but it is not stable and stable - and goes away until I play with it - turning device on and off, wiping cache.