i've rooted and flashed a few different roms to my phone and came across a problem. i got stuck in a bootloop after flashing a new rom to my phone.
data wipe does nothing and i can't figure out how to fix it. a friend suggested downloading offical stock rom and renameing it update.zip and running it in the recovery but i'm having trouble finding a stock rom for 2.2 droid x.
could anyone please point me in the right direction
Your going to need to SBF, there should be a guide for it in the DX forums. AFAIK you can't do it through recovery, you'll need to download the program and drivers to your computer.
Sent from my ADR6300 using XDA App
i'm still a little new to this stuff. what is SBF?
i found a thread for it. but i either need to do it from recovery or from a computer and the phone has to be put on usb mass storage. my phone is stuck in a bootloop so if i can't do it from recovery, how can i do it at all?
I have a 4G xoom that I am trying to return to stock. I have the stock images from Motorola and I am experienced in flashing so normally this would be a simple process for me, But I absolutely can not get past the 0x120000 error. I am using a Motorola cable (Not the one that comes with Xoom, But I don't have that one.) and I am using a port on the back. System.img refuses to flash and I can not understand why... Any help would be appreciated. I have also tried the adb method of flashing and that did not work either, It flashed and then re-booted with the custom rom.
I have searched but I can not find one, I would prefer a simple flash able .zip as I have CWM but ANY help would be appreciated.
http://developer.motorola.com/products/software/?pubid=987654
ADB is involved, but it's simple enough.
angel.de.marc said:
http://developer.motorola.com/products/software/?pubid=987654
ADB is involved, but it's simple enough.
Click to expand...
Click to collapse
I understand that, that is what I was referring to that I did in my original post. It won't let me flash system.IMG with error 0x120000.
Got this unlocked AT&T Crossover off eBay. Upgraded to Gingerbread via Pantech and rooted it using details on here (Really appreciated)
Unfortunately have deleted a system ap and like an idiot had NOT backed up my stock . The phone still works and I can still talk/transfer to phone via adb/usb cable, but need a stock .img to repair/restore phone to original state as keep getting " files missing" etc... can anyone please help?
Considering buying another, repeating above (Less deletion!!!) making a backup image and copying it across to current phone for a restore, would that work?
Any advice really appreciated. Yes, I know I don't deserve any.....
So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?
Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium
Any ideas?
Sent from my LG-LS970 using xda premium
Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.
No one can help?
Sent from my LG-LS970 using xda premium
Well that sucks...
Sent from my LG-LS970 using xda premium
Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.
I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.
hey all.
so recently i dug out my lg spirit H440n
i am hoping someone however can help me.
A while back i tried to flash cwm recovery on it (noob mistake) and as such ruined the recovery.
now im pretty screwed because i never backed up the stock recovery and am having a really hard time finding a copy of the stock recovery.img which i plan to re-flash
i was hoping someone here could do me a favor and make a copy for me off their device
if it is for some reason not compatible what are my options from here.
im trying to fully return back to stock
any help is appreciated
anyone?