Hi,
This is my first post so please if I'm in the wrong place or doing anything wrong please let me know.
My problem and yes I am the fool to blame! The other night I was playing with root explorer and decided it would be a "great" idea to delete all the folders on my Milestone A854, PDS DATA etc etc.
What harm could it do? I just reinstall a rom back on and all sorted...... Wrong! I reinstalled roms using mini mod and then sbf files with RDS lite both producing the same outcome. A phone that displays the "M" Motorola logo then turns off and tries again......repeatedly!
Any help would be GREATLY appreciated.
Hello,
I know for me, I did the same thing with my Motorola Droid. But the thing is I didn't know what files the Droid had when it was in factory mode. So I decided to flash back to the original, in my case Verizon, SBF file. Then I rebooted, and let my phone update itself to the latest version, then did the whole "rooting" process, with the same rom I've been using.
Hope that helps
~Jin
Thanks Jin,
My problem here is I don't know what it had in the first place? I've tried flashing stock UK SBF but that just puts you in the Motorola boot loop so no opportunity to update.
Any further help/suggestions would be greatly appreciated.
Dave
im sorry if i get it wrong, so u cant get to recovery mode or sort of? i deleted one of the folder on /data n /system before, but i managed to entered recovery mode. n did the rest via console.
Yes I have and can still get to open recovery.
What could I try and do from there? I've tried with updates through this method the same way you put on custom firmware ( put the rom file in the open recovery updates folder).
So what do I need to do via console?
Still stuck with this one have tried stock sbf and custom roms all same problem BOOTLOOP have tried taking battery out then factory reset still same. Don't understand what wenderis means by "do the rest via console" ? So if any one out there can get my brick back to life you will be loved forever.
Related
I've been having trouble with my Vibrant and with T-Mobile in limbo I picked up a N1 off ebay to hold me over. This thing is driving me insane!
The phone came with CM7 installed on it, but the person that shipped it to me didn't erase any of there stuff so I figured I would flash a fresh image on the phone to take care of things. I've flashed my Vibrant a dozen or so times and never had an issue. Flashed the N1 and it comes up with an X made of 4 different colored lines and a little lock at the bottom. I know some roms take a while to load so I let it sit for an hour. Nothing.
Since I've been trying everything I can find out how to recover the phone including all of the guides on the wiki. I'm at my wits end at this point. I can't get into clockwork at all on the phone. It gets stuck in the bootloader and if I select recovery it just takes me back.
I've got droid explorer running, and the phone shows up, but it doesn't show anything on the phone, no folders or files and won't let me load anything on to it. (it says it is, but then stays blank) I have no clue what to do at this point short of taking a sledge hammer to it. (obviously I'm posting this as I consider that to be plan B)
I don't need anything special, I just want a working phone. Is that really so much to ask for?
If ur Phone is running( means u can boot) try flashing cwr from rom manager and flash the rom again or try to hard reset the phone and then see ?
Firstly, I would start of by being more specific about what you have tried.
If you really have tried "everything", then there's nothing anyone can do for you.
I suspect you haven't tried "everything"...?
danger-rat said:
Firstly, I would start of by being more specific about what you have tried.
If you really have tried "everything", then there's nothing anyone can do for you.
I suspect you haven't tried "everything"...?
Click to expand...
Click to collapse
I'm sure I haven't, just what I found in the wiki
I tried the PASSIMG.ZIP and it failed
I tried Amon_Ra's Recovery and the only way I can get it to do anything is to tell it to flash in droid explorer and it just reboots and gets stuck. Now nothing is showing up file wise in droid explorer and I can't transfer the image onto the root.
When I could get into clockwork I tried flashing different roms but it would just go to a screen with the clockwork logo and get stuck.
amolji said:
If ur Phone is running( means u can boot) try flashing cwr from rom manager and flash the rom again or try to hard reset the phone and then see ?
Click to expand...
Click to collapse
I can turn it on to the screen with the multicolored X or the bootloader, that's it. How do I do a hard reset?
n25philly said:
I can turn it on to the screen with the multicolored X or the bootloader, that's it. How do I do a hard reset?
Click to expand...
Click to collapse
in the bootloader I think (dont take my rookie rooting words too serious) theres a hard reset menu under recovery. it will take you to another x and press volume up and power for the menu to pop up.
try fastboot a recovery image (either Amon Ra or CWM) and see if you can get back to recovery after that.
Well I'm assuming you already have a custom recovery since it came with CM and you've, as you said, flashed it (what exactly do you mean by that by the way? flashed another rom?). So all I can recommend is that you wipe a few times and try flashing a few different roms and hopefully one will boot. Not the best advice in the world but its always worked for me before and my N1 and my DEXT before hand when I've messed them up!
You still did not say what you flashed to your phone.
Anyways follow the restore to stock guide.
I don't know what this Droid manager thing is but don't use it. Install the sdk.....
All, please help !!!!
I bought a droid bionic on ebay (seller didn't mention that the software is corrupted) now tired to install ICS using RSD 5.7, it installed correctly, but the phone boots up and gets stuck on the "Droid" screen. Nothing happens from there. I can go to AP boot and/or recovery but can't do anything about it. Please help !!!! Searched the web for two days but no solution. I loaded the following file with RSD, downloaded from different site and tried atleast 5 times.
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.z ip
SamuriHL's House Of Bionic
READ all the OP until you understand it. Any question you can have is probably addressed in the threads. HOB scripts automate most of the things you can screw up.
Good Luck
What happens when you try to use the stock recovery?
rahm0809 said:
All, please help !!!!
I bought a droid bionic on ebay (seller didn't mention that the software is corrupted) now tired to install ICS using RSD 5.7, it installed correctly, but the phone boots up and gets stuck on the "Droid" screen. Nothing happens from there. I can go to AP boot and/or recovery but can't do anything about it. Please help !!!! Searched the web for two days but no solution. I loaded the following file with RSD, downloaded from different site and tried atleast 5 times.
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.z ip
Click to expand...
Click to collapse
The FXZ file, for some reason, won't wipe the /data partition. Your best bet is to boot into Stock Recovery, wipe data, power down. Then boot up into flash mode for RSD Lite. Reflash and then everything should be okay.
The device was probably on Gingerbread and the ICS flash caused the OS to freak out when it saw a /data folder full of Gingerbread things without any sort of preparation laid down.
I could have sworn the FXZ always wipes data...Well, the unmodified FXZ. And it erases internal storage, too....
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk HD
Hi everyone. I have a problem I can't seem to resolve. I tried updating to the OTA jellybean update a couple weeks ago, it seemed to go ok. I then tried to go back to an earlier version of eclipse rom I was using. Now when I power on the phone I get AP Fastboot Flash Mode (S) (Flash Failure). I can select normal boot and it will go into my ICS Rom that I have loaded in slot 1 after going thru my safestrap recovery program. So the phone is not unusable, just very annoying to use. My question is, how can I get the fastboot flash mode flash failure warning to not show up every time I reboot the phone? I've tried loading the Stock JB Rom from verizon, Blur_Version.6.7.246.xt875.verizon.en.us with RSD Lite, but when I try to extract the files with RSD, I get the error "Please check input file. Either XML format is wrong or image files associated with it are missing." I just want to be able to get a stock rom back on my phone, without any errors when I boot it, I don't care if I have root, safestrap, or anything else, I just want a properly working phone. Any suggestions how to get rid of the boot flash failure warning? Thanks!!!! Richard
Update.... Looks like I really screwed it up now. Tried to rsd lite a JB rom, got about 1/2 way, to copying system image, then hung up. Now when I reboot, it won't even go into recovery or normal mode... Stoopid operator malfunction..... Any suggestions on which rom I can try to install via RSD Lite to help get it back going? It will still go into AP fastboot mode.
He's dead, Jim. Nothing is working, no rom will load, they either fail or hang up. Now both of my batteries are dead, and it won't even try to do anything. Any suggestions?? Guess I'm in the market for another phone. Maybe some of the gurus on here have some advice. Thx.
He's alive, Jim!!!!!
rlg999 said:
He's dead, Jim. Nothing is working, no rom will load, they either fail or hang up. Now both of my batteries are dead, and it won't even try to do anything. Any suggestions?? Guess I'm in the market for another phone. Maybe some of the gurus on here have some advice. Thx.
Click to expand...
Click to collapse
Thanks to some other posts on here, http://forum.xda-developers.com/showthread.php?t=2236980 I tried installing the system and preinstall img files manually thru moto fastboot. They seemed to hang up after a few minutes, but I tried to install the files anyway. Afterwards, I was able to get into recovery mode and do a system wipe and reinstall the JB rom that I had on my SD card. Now a couple hours later, I got the pageplus 4g issue fixed again, and just finished rooting it with the tutorial on XDA http://forum.xda-developers.com/showthread.php?t=2256439.
You guys are awesome! Thanks for all your hard work.
OK I purchased a used G flex that was stuck in a constant boot loop. I've followed every guide all over this forum for restoring this phone or even the G2 threads as well. My phone is the ATT D950 version. The phone thinks it's a D959 when trying to flash with the LG Flashtool 1.8.1. I've tried the custom DLL DGUP_8974 with the ATT LGD950AT-01-V20b-310-410-MAR-22-2014+0.tot and the JAN-25-2014+0.tot file too. Neither have worked at all. I fail at the same spot. The one constant thing that I've noticed is. The flash tool doesn't see the phones IMEI#. So I'm thinking it's completely F'ed right now. I use to be able to boot into CWM 6.0.4.8. But now it doesn't boot into anything but download mode. I've tried all of the different methods I could find and I'm at my ends with the phone. If no one has any other idea's to try. I'll just sell it as parts on feebay.
The only other screen I can see is a white screen with what looks to be 3 choices in Korean I believe. I don't know what any of it is so I'm assuming that won't help me either.
For any inquiring minds. I've googled, youtubed, XDA'd, and possibly checked any site that had a reference to fixing this issue. Every guide is fairly similar but an old or newer LG flash tool. I've used the original ATT DLL with the same results. All of the other post I've see are people succeeding pass my point of failure so I think the phone truly is done. And lastly I've tried multiple computers and cables.
Nobody has any idea's on what I could do next?
You could try the trouble kdz to get it booting, download one of the att flash able zips, then use freedom flex to get a recovery and flash the zip you downloaded. Not sure if that'll work, but seems like it should
kintwofan said:
You could try the trouble kdz to get it booting, download one of the att flash able zips, then use freedom flex to get a recovery and flash the zip you downloaded. Not sure if that'll work, but seems like it should
Click to expand...
Click to collapse
Thanks that's one thing I haven't tried and will when I get off work tonight.
By the way forgot my standard disclaimer....so I'm not responsible if this blows your phone up for good, losses the imei (which could possibly be gone already), etc. It's generally not a good idea to flash another versions kdz l, but don't think there's another option with you not having recovery, adb and the build.prop being wrong.
No problem man. I'm not a rookie to the flash game and I do understand the disclaimer lol. The dude I got this phone from who had flashed what looked to be a T-mobile rom and most likely caused this issue. I got it cheap so if it's screwed I'll just sell if on Feebay.
Please close up. I was able to get out my bootloop after discovering my phone still had CWM recovery working. I was able to restore my phone back to an older 4.2.2 rom that I had. If you're stuck and booting into a custom recovery I'd follow one of the recovery boot loop fixes. The one I use I flashed a zipped command that wiped a corrupt partition since I could get into ADB mode to push the files. If you have TWRP, it has an ADB mode that will allow those commands to work. But CWM people will need to sideload the files that will auto push the files needed to correct the corrupt partitions. As always folks, please back up before you flash anything. That's what saved my phone in the end outside of the partition clearing files sideloaded in CWM.
Hi a friend of mine has a Nexus 6 but for some reason it wont get past the google screen, it would just turn off again, and if it is plugged it will just go to the Battery Icon and then off again.
He has tried everything, even flashall.bat to add new stock rom, tried pushing TWRP recovery etc, etc.
Is there a way he can extract EFS folder to see if by any chance that or something else is corrupt?
Thanks! I know XDA Peeps have helped me a lot before and I tried almost everything with him with no avail
He wants to extract the EFS, just in case trying to flash more things or something might break it, he just wants to have a backup just in case.
ZeroHart said:
Hi a friend of mine has a Nexus 6 but for some reason it wont get past the google screen, it would just turn off again, and if it is plugged it will just go to the Battery Icon and then off again.
He has tried everything, even flashall.bat to add new stock rom, tried pushing TWRP recovery etc, etc.
Is there a way he can extract EFS folder to see if by any chance that or something else is corrupt?
Thanks! I know XDA Peeps have helped me a lot before and I tried almost everything with him with no avail
He wants to extract the EFS, just in case trying to flash more things or something might break it, he just wants to have a backup just in case.
Click to expand...
Click to collapse
If he can go into bootloader mode he can flash the stock rom manualy, look here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008, method 2.
ZeroHart said:
Hi a friend of mine has a Nexus 6 but for some reason it wont get past the google screen, it would just turn off again, and if it is plugged it will just go to the Battery Icon and then off again.
He has tried everything, even flashall.bat to add new stock rom, tried pushing TWRP recovery etc, etc.
Is there a way he can extract EFS folder to see if by any chance that or something else is corrupt?
Thanks! I know XDA Peeps have helped me a lot before and I tried almost everything with him with no avail
He wants to extract the EFS, just in case trying to flash more things or something might break it, he just wants to have a backup just in case.
Click to expand...
Click to collapse
Since you want to backup the efs here is my best advice:
Normally you can backup the efs via custom recovery(thats out) or through adb. I don't know the details of adb, nor how one might backup efs in fastboot. I looked through the files in roots I believe the efs partitions are in /dev/block/platform/msm_sdcc.1/by-name/ and the files are probably mdm1m9kefs1 mdm1m9kefs2 mdm1m9kefs3 and mdm1m9kefsc Now this is my best guess and I'm not sure if you can just copy them in adb to save on your comp or wherever, and well you would need to look up some adb commands... But that's all I can say.
What you can do in fastboot is really limited. adb via custom recovery would be the only way really.
I haven't seen any instances of this phone with a corrupted efs yet
Too bad, he tried flashing stock but did not work, not by doing flash all nor by doing one by one, also tried flashing recovery, but when he selects fastboot boot recovery the phone will just turn off again.
He says he is tied and will send it back to t mobile, hopefully they fix it or send him a new one
ZeroHart said:
Too bad, he tried flashing stock but did not work, not by doing flash all nor by doing one by one, also tried flashing recovery, but when he selects fastboot boot recovery the phone will just turn off again.
He says he is tied and will send it back to t mobile, hopefully they fix it or send him a new one
Click to expand...
Click to collapse
Did they flash o.k.?. But won't boot to os. Because I have similar issues. I had it working o.k. was on bliss rom. Then when I woke up phone was on Google logo and won't go any further. I tried flashing the images. They flash only manually. But won't let me go to recovery or the os. Any advice what could went wrong with device.
Nochis said:
Did they flash o.k.?. But won't boot to os. Because I have similar issues. I had it working o.k. was on bliss rom. Then when I woke up phone was on Google logo and won't go any further. I tried flashing the images. They flash only manually. But won't let me go to recovery or the os. Any advice what could went wrong with device.
Click to expand...
Click to collapse
That is exactly what happened to him, everything flashes but it wont get to recovery or OS, if it is plugged it will just show the google screen then battery and that is it
ZeroHart said:
That is exactly what happened to him, everything flashes but it wont get to recovery or OS, if it is plugged it will just show the google screen then battery and that is it
Click to expand...
Click to collapse
What rom he was before this happen?.
Stock Rooted
ZeroHart said:
Stock Rooted
Click to expand...
Click to collapse
So it may be a hardware issue. My guess is something went wrong with the device.