Database Info

Need some quick help

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.

Droid RAZR HD @ No Valid PIV block in Sp for system

Hi guys. First, trust me that I have looked at every post I could find regarding this issue and the reason I am starting a new thread it because the fixes are not working for me. First, my phone:
Droid Razr HD Dev Edition, I believe it's the T926, though it doesn't boot now so.....
I had rooted this phone with the Droid Razr HD Utility 1.1. I had it running on T-Mobile fine for quite some time (only HSA speed or whatever they call it, but that's fine I'm out of range for anything better anyway). I had Superuser installed and something like root keeper I think it was called. Anyway my point is everything worked great.
I started getting this popup that seemed to say Motorola wanted to do an update. Now I had ignored the update on my phone for a while as I didn't want to go through the process just yet. Finally I gave in and I let the Motorola from my Windows PC try to push an update. That was the last my phone has booted.
So now all I get is Fastboot. Now if I do the buttons and manually go to fastboot it looks normal and I connect USB and it looks fine. But if I try to run the HD Utility 1.10, 1.20 both fail, RSDLite 5.6 and 6.0 both fail. All I can come up with is No valid PIV block in sp for system. The phone does seem to respond when I try the utility but all I get is failures and it clearly says the phone is locked. RSDLite has no such luck and immediately fails.
I still have the original XT926 xml I used and I also downloaded a VZW_XT926. I'm really SOL here guys and I would so appreciate any help.
I guess the last bit of info I can think to add is that when I plug USB in fresh what looks like Motorola software (what messed me up to begin with) pops up and tells me it wants to repair the phone. Of course like an idiot I've tried that as well.

My guesses are; you are using an outdated utility, outdated fastboot files, outdated RSD lite (there is 6.1 and higher out) and/or your system is corrupted. So make sure all of your tools and files are up to date and report back if you get any further.
Were you on ICS or JB before the update nag? Pretty sure if you were on Jellybean you will have to wait for an xml to be released, I remember reading something like this on DroidRzr.com

coolloser said:
My guesses are; you are using an outdated utility, outdated fastboot files, outdated RSD lite (there is 6.1 and higher out) and/or your system is corrupted. So make sure all of your tools and files are up to date and report back if you get any further.
Were you on ICS or JB before the update nag? Pretty sure if you were on Jellybean you will have to wait for an xml to be released, I remember reading something like this on DroidRzr.com
Click to expand...
Click to collapse
I was on JB so I'll do some more research on that. I saw a 6.1 for RSD but skipped it due to reg req. I'll hunt it down. How do you update Fastboot? I was just updating Razr HD Utility and letting it do it's thing. I have 1.2 now and it has Fastboot inside. Is that what you mean or am I missing a step?
Thanks for your help.

Dagroth said:
I was on JB so I'll do some more research on that. I saw a 6.1 for RSD but skipped it due to reg req. I'll hunt it down. How do you update Fastboot? I was just updating Razr HD Utility and letting it do it's thing. I have 1.2 now and it has Fastboot inside. Is that what you mean or am I missing a step?
Thanks for your help.
Click to expand...
Click to collapse
After Jellybean there needed to be new Fastboot files because of some security change in Android, the newest utility most likely has it. I found this file
http://sbf.droid-developers.org/vanquish/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml.zip
in this thread:
http://www.droidrzr.com/index.php/topic/15828-rsd-lite-stock-412-firmware-restore-not-working/
If you are still stuck after that I suggest signing up on DroidRzr.com and joining the chatroom, those guys know far more than I!

Just an update that nothing I have tried has worked and I remain bricked. I've updated the DroidRAZR Utility, RSDLite, tried numerous images... still bricked. No valid PIV block in SP for system.

Dagroth said:
Just an update that nothing I have tried has worked and I remain bricked. I've updated the DroidRAZR Utility, RSDLite, tried numerous images... still bricked. No valid PIV block in SP for system.
Click to expand...
Click to collapse
Well I finally got it working. I tried as much as I could find, RSD 6.1.4, Droid RAZR Utility 1.2, many many many images since my original wasn't working. Anyway I'll skip all that didn't work.
My problems got compounded when my battery died. The internet goes on about how bad this is. True to form when I found and tried to manually push an image with fastboot I kept getting errors about the batter. Now this phone is the developers edition and I read somewhere about how you can buy this special cable. Like most of you I have dozens of USB cables and at one point my original was misplaced. Ah, your catching on now aren't you? I went hunting and dug up my original cable and the blasted thing just booted right up. No re-imaging, nothing, just booted right up.
Now I "had" successfully (today) sent a fastboot of a new system.img from the Droid RAZR Utility 1.2 and checking my system I do see that indeed that is the img I am on. So this may have been a two fold rescue.
So in the hopes it helps any other poor sap out there. Here is how I fixed my bricked Droid RAZR HD xt926 that had a near dead battery.
Boot into AP Fastboot
On windows computer, navigated to folder where I had extracted Droid_RAZR_HD_Utility_1.20
fastboot flash system system.img >>This worked
fastboot flash boot boot.img >> this failed
I then dug up my original cable, plugged directly into wall adapter and voila - it booted up!
Unfortunately I think I'm on JB now, but hell at least my phone is working again!
Thanks for the replies, thanks for your hard work tearing these phones down and giving us tools to work with and thanks to the *** *** internet for being so awesome and giving us so much at our finger tips!

Unbricked
Dagroth said:
Well I finally got it working. I tried as much as I could find, RSD 6.1.4, Droid RAZR Utility 1.2, many many many images since my original wasn't working. Anyway I'll skip all that didn't work.
My problems got compounded when my battery died. The internet goes on about how bad this is. True to form when I found and tried to manually push an image with fastboot I kept getting errors about the batter. Now this phone is the developers edition and I read somewhere about how you can buy this special cable. Like most of you I have dozens of USB cables and at one point my original was misplaced. Ah, your catching on now aren't you? I went hunting and dug up my original cable and the blasted thing just booted right up. No re-imaging, nothing, just booted right up.
Now I "had" successfully (today) sent a fastboot of a new system.img from the Droid RAZR Utility 1.2 and checking my system I do see that indeed that is the img I am on. So this may have been a two fold rescue.
So in the hopes it helps any other poor sap out there. Here is how I fixed my bricked Droid RAZR HD xt926 that had a near dead battery.
Boot into AP Fastboot
On windows computer, navigated to folder where I had extracted Droid_RAZR_HD_Utility_1.20
fastboot flash system system.img >>This worked
fastboot flash boot boot.img >> this failed
I then dug up my original cable, plugged directly into wall adapter and voila - it booted up!
Unfortunately I think I'm on JB now, but hell at least my phone is working again!
Thanks for the replies, thanks for your hard work tearing these phones down and giving us tools to work with and thanks to the *** *** internet for being so awesome and giving us so much at our finger tips!
Click to expand...
Click to collapse
I was trying to load a different ROM (running 4.4.2) so I could unlock the bootloader and root and hard bricked my phone with the same error message as a result of a failed flash. Using the fastboot command (fastboot flash system system.img) I was able to load the system.img from VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml and now am booting successfully once again.
Dagroth, you pulled my fat outta the fire! Many thanks. I hope this message helps others.

[Q] help needed flashing cm 10.1

I hope I'm not breaking any rules by posting this, but I've tried following guides included within this forum and other guides as well.
Hardware:
VZW SCH-I535.10 16GB
Version: 4.1.2
Baseband: VRBMA2
Kernel: 3.0.31-861013
[email protected] #1
Build: JZO54K.I535VRBMA2
I've always been able to root successfully.
I have gotten once to the CM 10.1 boot screen, but phone ended up getting stuck in a loop. Ever since then, I've attempted to try numerous times again, but winding up with 'this software isn't approved by verizon wireless' or something of that nature. I assume this is because the bootloader is still locked? I've followed quite a few guides in hopes that I was just unlocking the incorrect way.
I've tried flashing using TWRP and Clockwork, but still no luck. I even tried different ROM managers through the play store (I thought, well what the hell it can't hurt).
I'm sick of Samsung's UI! Any help will be much appreciated!
Thanks

Can anyone help out? Still haven't found a solution.

rgt533 said:
Ever since then, I've attempted to try numerous times again, but winding up with 'this software isn't approved by verizon wireless' or something of that nature. I assume this is because the bootloader is still locked?
Click to expand...
Click to collapse
Yes the bootloader is still locked if you are getting that message, use EZ unlock 1.2 apk to unlock then go ahead after you make backup format data/cache/dalvik then flash the rom /gapps

[Q] 4.4.2 Failed - Recover Device Back to JB?

Hi All….received the 4.4.2 download this morning on my RMHD and ran through the install. At reboot the phone got stuck on the Red Moto logo… I let it sit for nearly 45 minutes, assuming it was doing its thing in the background. But at that point I figured it was safe to assume something got hosed. I rebooted back into recovery and did a factory reset. That wound up making things worse…now am in a boot loop between the logo and the Android triage guy (recovery)….
Phone was rooted and locked. And I am complete understanding that I was losing root with this OTA. Been reading all posts in here….please ‘flog’ me if I missed something.
With that said…I have two questions on recovering the device.
1) Can I simply download and copy one of the JB images from the Motorola Firmware site to my SD card and install via recovery (since my recovery appears to be OK)?
2) Or should I/need I follow procedures using RSDLite? And recover this way?
Any comments are appreciated!
Thanks
Doug

Never mind. iBolski's thread "Official KK OTA for 9.30.1 (XT926) users - please read" in the general forum looks like it might do the trick for me...and I won't be able to go to a previous (JB) Android version. This looks easy enough.

I have the same issue except I'm in need of a .zip or set of files for the modem firmware that I need to flash in 4.4.2 183.x.x Stock because I tried to downgrade to 9.30.1 jb and the firmware and the modem downgraded. Could someone create a package I can flash in stock recovery to restore my Droid Razr Maxx HD to to 4.4.2 183.x.x

[Q] Moto G Stuck on Boot

Hi. I've got the Moto G and i decided to unlock the bootloader and then download CWM. That all worked fine but now when i switch my phone on, it gets stuck on the 'Motorola by Google' Logo. It seems like its frozen on there but the power button is able to function, not the volume buttons though. Ive tried RSD Lite but it's not finding my device. I'm 14 so im not very good using a terminal but any guidance would be fine. I've also tried flashing the Paranoid 4.4.4 zip, The Stock Firmware zips and even Gapps but they all come up with the same message,
finding update package
opening update package
verifying update package
Installation Aborted.
Please could any one help me out and explain what went wrong with the phone? THANKS!

How?
burrt said:
You could flash the factory image by Motorola through ADB so it resets everything, I'm sure you can find the link somewhere in the forums (I'm using the 4G version so my method may be different slightly). I found rooting my phone very intuitive from the guides, only problem I had was making sure I had administrative privileges and access in the command window directory.
If I remember correctly, this will probably remove CWM and if you insist on a third party recovery, give TWRP, the problem could be related to CWM.
Click to expand...
Click to collapse
Could you tell me exactly what to do? i dont have much experience but ive downloaded the 4.3 and 4.4.2 Retail zips, extracted them and then opened CMD and tried things such as 'fastboot flash .....zip or image'. Still doesnt work and sometimes i get 'hab' errors and 'image is too large'.

Thanks
burrt said:
I'm not too sure about your problems, were you on Stock 4.4.4 running fine? I'm going to assume you are using the Moto G 3G version.
Although I haven't personally tried this guide myself, from what I see, it is reliable:
[GUIDE] Moto G - Restore stock firmware
Just a helpful tip when you open a terminal (took me a while to figure out when I first rooted my phone), located to the folder where they wan't the terminal and hold Shift + Right Click. This will give you an option "Open command window here", look carefully. Once again, make sure you are downloading the correct files for your device and read the steps carefully, you can minimise a lot of headaches and realise some shortcuts. It is also an 'old' guide so be sure to verify links etc.
Click to expand...
Click to collapse
Thanks so much for helping but i've done that, probably over 5 times. I am on Moto G 4.4.4 and whenever i flash stuff it gives 'hab' warnings and 'invalid piv' and 'image size too big'