Database Info

[Q] [HELP] Loading a ROM on Captivate

Feeling dumb, but I have successfully rooted and loaded (multiple times) ROMS on my Droid Incredible. Though I can't seem to get ROM manager to load a downloaded (CM7) rom onto my captivate - YES the phone is rooted .
I think i'm missing the bootloader, but i'm unsure. All the phone does is go to "Samsung Recovery Utils" and offers the following options only
*reboot system now
*reinstall packages
*delete all user data
*delete cache data
*format internal sd-card
Can anyone tell me what i'm doing wrong or point me to a thread that doesn't just say "download rom, install from SD card and done"?

let me give you a hint. there is a sticky section.....read

dudeicles said:
Feeling dumb, but I have successfully rooted and loaded (multiple times) ROMS on my Droid Incredible. Though I can't seem to get ROM manager to load a downloaded (CM7) rom onto my captivate - YES the phone is rooted .
I think i'm missing the bootloader, but i'm unsure. All the phone does is go to "Samsung Recovery Utils" and offers the following options only
*reboot system now
*reinstall packages
*delete all user data
*delete cache data
*format internal sd-card
Can anyone tell me what i'm doing wrong or point me to a thread that doesn't just say "download rom, install from SD card and done"?
Click to expand...
Click to collapse
Can you give more details? Going from what to what etc....?

chappatti said:
Can you give more details? Going from what to what etc....?
Click to expand...
Click to collapse
Going from Stock Froyo 2.2 to CM7. but when i go into the boot screen it's blue and gives me the options above. Then when I press the "reinstall updates" I get a
E:failed to verify whole-file signature
E:signature verification failed"
I must be doing something just simple and stupid, but thought i'd ask anyways. I'll try to find the sticky and see if it tells me something i haven't tried. Thanks!

SEARCH FOR :captivate signature verification error
FIND:
million threads.
OR READ MY SIG.... the answer is in there.

@TRusselo: I've tried your guide step by step and I still end up at the Android system recovery and not CWM. Is there a step I might be missing? I downloaded the links you gave, followed all instructions and still same problem.
Thanks alot for the guide, if it worked i'd be even happier about it.

dudeicles said:
@TRusselo: I've tried your guide step by step and I still end up at the Android system recovery and not CWM. Is there a step I might be missing? I downloaded the links you gave, followed all instructions and still same problem.
Thanks alot for the guide, if it worked i'd be even happier about it.
Click to expand...
Click to collapse
After doing all the steps, did you reinstall packages in recovery.
Sent from my SGH-I897 using xda premium

b-eock said:
After doing all the steps, did you reinstall packages in recovery.
Click to expand...
Click to collapse
I tried that multiple times.
my understanding is the text at that point should be green, but it's still blue and gives the same exact error. "E:failed to verify whole-file signature E:signature verification failed"

Alright, I tried the Heimdall version which shows more promise, i'm just now unable to boot into any recovery. I hold the volume buttons and power for the 3-5 seconds and it boots to a boot screen with "TALON" on it. but nothing else from there.
Am I missing something else?

to first issue.... you followed the wrong link in my signature....
" 3e recovery fix " is what you were looking for.... since you were having truoble with 3e recovery.... thought that would be self explanatory.....
make sure usb debugging is ONturn OFF anti-virus for 5 minutes or until reboot
plug in phone.
click the bat file in this file.
you will have THE SAME RECOVERY with NO error
signature verification pass...
flash any update.zip package
but since you have a custom kernel with cwm now.....
What heimdall method are you talking about? for recovery? for flashing roms? what are you talking about. heimdall can do alot of stuff. did you upgrade bootloaders? or??
keep trying the button combo.. if it turns on, it will go into recovery.

Please search before posting, on that note thread closed.

Cant access recovery. Have nandroid but cant flash it.

Ive been trying to fix this for two days. This post is a last resort. Ive searched the forum and tried what little I found.
Ive trashed phones and had to fix them but never seen this.
I finally got root on this thing and was flashing CM10 but kept seeing "failed" using TWRP so decided id flash
CWM and give it a try. Once,still TWRP Twice,still TWRP. Third, Black recovery screen then skip to normal boot.
Fourth try it read "error: cannot load 'openrecovery-twrp-2.3.1.0-evita'" and has since with both recoveries.
No access with volume/power method. No access from command prompt. No access through Quick Boot , Rom Toolbox,
etc.
If I posted this wrong Im sorry. I can usually fix these things myself but Im waving the white flag on this one.
I tried adb help but everything I tried said failed. Any help would be greatly appreciated.

ksflat43 said:
Ive been trying to fix this for two days. This post is a last resort. Ive searched the forum and tried what little I found.
Ive trashed phones and had to fix them but never seen this.
I finally got root on this thing and was flashing CM10 but kept seeing "failed" using TWRP so decided id flash
CWM and give it a try. Once,still TWRP Twice,still TWRP. Third, Black recovery screen then skip to normal boot.
Fourth try it read "error: cannot load 'openrecovery-twrp-2.3.1.0-evita'" and has since with both recoveries.
No access with volume/power method. No access from command prompt. No access through Quick Boot , Rom Toolbox,
etc.
If I posted this wrong Im sorry. I can usually fix these things myself but Im waving the white flag on this one.
I tried adb help but everything I tried said failed. Any help would be greatly appreciated.
Click to expand...
Click to collapse
First off stick with twrp cwm is not officially supported on our device and can blank your SD card...can you link me to the cm ROM you were trying to flash it was for our phone not the international one x right?

tactical kitten said:
First off stick with twrp cwm is not officially supported on our device and can blank your SD card...can you link me to the cm ROM you were trying to flash it was for our phone not the international one x right?
Click to expand...
Click to collapse
Thanks for the reply. Ive got the link. first thing I see wrong is it says endeavoru and mine says evita I believe. The CM10 wouldnt install so I
tried flashing CWM recovery and here we are. Heres the link.
Thanks again.
Well, I cant send you the link. It says new users cant post outside links. Sorry. Its from the CM website. Dated 2012-01-07

ksflat43 said:
Thanks for the reply. Ive got the link. first thing I see wrong is it says endeavoru and mine says evita I believe. The CM10 wouldnt install so I
tried flashing CWM recovery and here we are. Heres the link.
Thanks again.
Well, I cant send you the link. It says new users cant post outside links. Sorry. Its from the CM website. Dated 2012-01-07
Click to expand...
Click to collapse
Ok so corrct me if im wrong the cm10 you're trying to install says endeavoru? That's the intl one x not ours....we have the evita like you stated so you're lucky the build prop check is there or if it successfully flashed you'd be bricked...stay in our forum and you'll be fine...now here are your stepsinstall twrp through fastboot
Move the Rom of you're choice onto your phone(mount in twrp)
If you're on hboot 1.14 you have to flash boot.omg seperately
Wipe data system and cache install Rom enjoy...
You may have to format your sd if cwm corrupted it

tactical kitten said:
Ok so corrct me if im wrong the cm10 you're trying to install says endeavoru? That's the intl one x not ours....we have the evita like you stated so you're lucky the build prop check is there or if it successfully flashed you'd be bricked...stay in our forum and you'll be fine...now here are your stepsinstall twrp through fastboot
Move the Rom of you're choice onto your phone(mount in twrp)
If you're on hboot 1.14 you have to flash boot.omg seperately
Wipe data system and cache install Rom enjoy...
You may have to format your sd if cwm corrupted it
Click to expand...
Click to collapse
I cant install through fastboot. I get the "error cant load" message i talked about in the first post. It wont let me near recovery

if u can get in to fastboot but not in to twrp youll probly have to relock your bootloader and ruu back to stock

Reflash twrp 2.3.3.1 for evita in fastboot, also run fastboot erase cache. If your nandroid was made with cwm it wont work with twrp.

[Q] Trouble installing KitKat 9.18.94

My Razr maxx hd (xt926) had been rooted and bootloader unlocked sitting on version 9.16.9 for a while. With KitKat available I downloaded the 9.18.49 rom file and reset the phone flashing it with the Blur_Version.9.30.1.XT926.Verizon.en.US rom and getting everything back to stock. At this point it shows build 9.8.1Q I loaded the KK rom on the SD card and tried to flash from stock recovery.
During verification it aborts, with an error
expects build fingerprint of xt926_verizon/vanquish:4.1.2/9.8.1q-94/56:user release-keys
this device has xt926_verizon/vanquish:4.1.2/9.8.1q-94-1/57:user/r
Any thoughts on how to deal with this?

try this posted by @zachariahpope http://crackflasher.com/blur_version-9-18-94-xt926-verizon-en-us-zip-motorola-droid-razr-hd-cdma-livinginkaos/

billycar11 said:
try this posted by @zachariahpope http://crackflasher.com/blur_versio...zip-motorola-droid-razr-hd-cdma-livinginkaos/
Click to expand...
Click to collapse
That's the file I was trying to flash
Sent from my DROID RAZR HD using Tapatalk

samabuelsamid said:
That's the file I was trying to flash
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
okay then sorry i was confused try this one.
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/edit
posted by @Sabissimo

billycar11 said:
okay then sorry i was confused try this one.
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/edit
posted by @Sabissimo
Click to expand...
Click to collapse
Bad news. I flashed that one from recovery and it put my phone into a boot loop
Time to start over from scratch

samabuelsamid said:
Bad news. I flashed that one from recovery and it put my phone into a boot loop
Time to start over from scratch
Click to expand...
Click to collapse
I was reading that it rewrites your recovery. Go back into your recovery (should be a new version) and try to I stall again.

Yeah you need to install 2 times.
Did it install the recovery?

billycar11 said:
Yeah you need to install 2 times.
Did it install the recovery?
Click to expand...
Click to collapse
I'll let you know later tonight. I had to reflash back to where I was so I'd have a working phone for my workday.

samabuelsamid said:
I'll let you know later tonight. I had to reflash back to where I was so I'd have a working phone for my workday.
Click to expand...
Click to collapse
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:

billycar11 said:
Yeah you need to install 2 times.
Did it install the recovery?
Click to expand...
Click to collapse
iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
Thanks, I'll provide an update of how this works!

iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
This all worked perfectly and I'm now rocking KitKat

iBolski said:
Definitely, the reboot during the install back into recovery is what confused a lot of us who were part of the soak test and tried to apply it manually ourselves.
When you first go into recovery and install the OTA, it will reboot. At that point, it will boot back to the recovery screen. There, you must press volume up + power. That is different from the old vol up+ vol down.
Anyways, once you are back in the "hard to read" recovery (why did they reduce the brightness on the new recovery?), you need to go back and install the OTA again. This time it will continue on where it left off and apply the KK update to your system.
Profit!
You might want to go to my post here (
http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1) and read some of the gotchas. Read them BEFORE you take the update so you don't bork your phone:
Click to expand...
Click to collapse
One other question: My bootloader is unlocked, I'm trying to find the directions to root again under kitkat by manually sideloading. Anyone have a link?

samabuelsamid said:
One other question: My bootloader is unlocked, I'm trying to find the directions to root again under kitkat by manually sideloading. Anyone have a link?
Click to expand...
Click to collapse
All you need to do is flash CWM and then find a sideloadable SU package to sideload under CWM. That's it.

iBolski said:
All you need to do is flash CWM and then find a sideloadable SU package to sideload under CWM. That's it.
Click to expand...
Click to collapse
Thanks. Just a couple more questions before I do this to make sure I don't send my phone back into oblivion and have to start all over again. Is the CWM recovery specific to any particular version of Android, current one available for XT926 on clockworkmod.com download page is 6.0.4.4. Similarly, does SU need to be specific to this phone/KitKat rom?
I've rooted numerous phones before, always using a script like Razr Hd utility. This is my first attempt at manual root so I appreciate your patience

samabuelsamid said:
Thanks. Just a couple more questions before I do this to make sure I don't send my phone back into oblivion and have to start all over again. Is the CWM recovery specific to any particular version of Android, current one available for XT926 on clockworkmod.com download page is 6.0.4.4. Similarly, does SU need to be specific to this phone/KitKat rom?
I've rooted numerous phones before, always using a script like Razr Hd utility. This is my first attempt at manual root so I appreciate your patience
Click to expand...
Click to collapse
You need to download the new CWM for KK. xt926-KK-CWM-6048.img is the name. You can get it from here: http://forum.xda-developers.com/showpost.php?p=52564336&postcount=1

iBolski said:
You need to download the new CWM for KK. xt926-KK-CWM-6048.img is the name. You can get it from here: http://forum.xda-developers.com/showpost.php?p=52564336&postcount=1
Click to expand...
Click to collapse
good thing I asked first
Update: not rooted on KitKat!

samabuelsamid said:
My Razr maxx hd (xt926) had been rooted and bootloader unlocked sitting on version 9.16.9 for a while. With KitKat available I downloaded the 9.18.49 rom file and reset the phone flashing it with the Blur_Version.9.30.1.XT926.Verizon.en.US rom and getting everything back to stock. At this point it shows build 9.8.1Q I loaded the KK rom on the SD card and tried to flash from stock recovery.
During verification it aborts, with an error
expects build fingerprint of xt926_verizon/vanquish:4.1.2/9.8.1q-94/56:user release-keys
this device has xt926_verizon/vanquish:4.1.2/9.8.1q-94-1/57:user/r
Any thoughts on how to deal with this?
Click to expand...
Click to collapse
I have the same problem, but I'm getting the error message that expects your device. What was the image that you used? I have the vanquish:4.1.2/9.8
1Q-94/56:user.

samabuelsamid said:
good thing I asked first
Update: not rooted on KitKat!
Click to expand...
Click to collapse
Then you cannot use CWM and there is no safe strap for KK.
Also, root is now lost, but SamuriHL is working on a theory that might work. Unfortunately, it requires locked phones that have NOT taken the soak or OTA yet and we have to wait for the official KK FXZ image file before he can continue. If the phone has had the OTA or soak applied to it, then it can't be part of the test.

iBolski said:
Then you cannot use CWM and there is no safe strap for KK.
Also, root is now lost, but SamuriHL is working on a theory that might work. Unfortunately, it requires locked phones that have NOT taken the soak or OTA yet and we have to wait for the official KK FXZ image file before he can continue. If the phone has had the OTA or soak applied to it, then it can't be part of the test.
Click to expand...
Click to collapse
Sorry, that should have read NOW rooted. CWM worked fine as did Koush's superuser

samabuelsamid said:
Sorry, that should have read NOW rooted. CWM worked fine as did Koush's superuser
Click to expand...
Click to collapse
you know what, color me stupid.
I've been helping so many people that when I read "no root", I interpreted it as "locked bootloader".
My bad.

(Solved) Soft-bricked, but unable to flash anything but CWM.

Hello, I seem to have soft bricked my tf700.
​I flashed a newish pacman nightly in CWM (after wiping data/cache/dalvik cache), which completed with no errors, then I flashed the corresponding GAPPS. But my device became stuck in the pacman boot intro.
​So I tried flashing slimkat which led to my device not getting past the first bootup screen (where you can enter recovery if pressing the corresponding buttons).
​After this screw-up I stupidly hit the wipe data button on the bootloader. I then tried doing the method of using fastboot to erase system, cache, and all that so I could flash system blob of the newest asus US SKU (that is correct for a US bought tf700 right?). Either this or wiping the data caused me to have a different bootloader as pictured below as I no longer have the android button and it does not ask me to press volume up to access recovery (the only way to access recovery is by hitting the wipe data button in bootloader).
​I can still fastboot flash CWM, but trying to flash TWRP does not work as it finishes but going into recovery causes the tablet to just restart. Trying to flash asus stock as above would always give me an error like the one pictured below. Similar errors occur if trying to flash any rom inside CWM via an external sd card.
​I do not have access to adb as i believe i dont have usb debugging enabled since the pacman rom or any other rom did not ever start. It just gives me the device not found error even after manually installing the drivers on two different computers.
Cant seem to get these pics to load, but copying the url and pasting it works.
http://imgur.com/AaU0GMt
http://imgur.com/vDTVa4B

You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.

tylerleo said:
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
Click to expand...
Click to collapse
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.

gio3505 said:
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
Click to expand...
Click to collapse
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.

tylerleo said:
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
Click to expand...
Click to collapse
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.

gio3505 said:
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
Click to expand...
Click to collapse
Hmm, I'd Download a stock Rom for the device offline, take on the sd card and put it on there real quick and try to flash that, if not, you probably bricked your device. I wouldn't know how to fix it beyond that. Ask the dev that made the Rom were everything that went south and an email to cwm wouldn't hurt either

I am also not sure if I need to have my external sd card formatted a certain way or download a specific CWM to allow flashing the stock rom. Ive spent over 10 hours trying to figure this out, very frustrating.

I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/

gio3505 said:
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
Click to expand...
Click to collapse
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?

berndblb said:
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
Click to expand...
Click to collapse
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?

gio3505 said:
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
Click to expand...
Click to collapse
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!

berndblb said:
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
Click to expand...
Click to collapse
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.

gio3505 said:
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
Click to expand...
Click to collapse
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?

berndblb said:
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
Click to expand...
Click to collapse
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.

gio3505 said:
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
Click to expand...
Click to collapse
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.

berndblb said:
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
Click to expand...
Click to collapse
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.

gio3505 said:
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
Click to expand...
Click to collapse
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...

berndblb said:
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
Click to expand...
Click to collapse
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.

gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Right stop flashing random stuff - you have combinations of JB4.2.1, JB4.1.1 and ICS 4.0.3 just listed there.
Let me put a call out to @lj50036 who may be able to save you but if you have messed the bootloader up with no nvflash backups you are not going to be happy with the result. If you can still get to the bootloader screen then he can perform miraculous superhero acts and *maybe* save your device.

gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Shoot me an email at [email protected]
We can use hangouts see if there is a solution to your issue ...
Thx Josh

[Q] Bricked?

I've been in the samsung family for so long that I didn't realize how different flashing can be. I broke my phone so I bought a Moto G. Rooted it right away with only a little trouble. I installed a Lollipop ROM afterward and couldn't get my phone to boot. Guess who forgot to do a backup of the stock ROM? Yay me... but anyway, I found a stock file and went through all the steps in the screenshot. Each time, I got the okay to move on and I assumed I had the stock file flashed. Upon rebooting, I stay at the "warning, bootloader is unlocked" and phone doesn't go any further. I'm not booting up at all and custom recovery is gone now.
Can anyone help? I'm at my wit's end.
Thanks in advance.

http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware

BBobby said:
http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware
Click to expand...
Click to collapse
That's actually the instructions I used to try to flash back to stock. But when it reboots, it never gets past the warning about bootloader. I can get the TWRP recovery back but from there is there another way to flash the "flashable zip"? With Samsung I could always use ODIN but I don't think it works with Moto G. I can't get the zip to internal storage to flash it.
Thanks for the reply by the way I'm going to try it one more time I think....

http://forum.xda-developers.com/showthread.php?t=2854688
Flashable stock zips. I don't have a PC to do a full reset. But with TWRP and the flashable stock zip I have had absolutely no problem.
If all else fails I would give it a shot
I have the xt 1032 cricket/aio. I am using stock "us retail" and it works just fine. If you have radio issues etc there is also a repository of flashable radio images

BBobby said:
http://forum.xda-developers.com/showthread.php?t=2854688
Flashable stock zips. I don't have a PC to do a full reset. But with TWRP and the flashable stock zip I have had absolutely no problem.
If all else fails I would give it a shot
I have the xt 1032 cricket/aio. I am using stock "us retail" and it works just fine. If you have radio issues etc there is also a repository of flashable radio images
Click to expand...
Click to collapse
I hate sounding dumb... but how will I flash the zip if I can't get it on my phone?

Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip

BBobby said:
Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip
Click to expand...
Click to collapse
Thank you for all your help. I'll give that a shot.

BBobby said:
Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip
Click to expand...
Click to collapse
Quick question. When I go into recovery to flash the zip, do I go to 'advanced' and then ' terminal command'? and go from there? I feel like a noob and I've flashed dozens of roms...

To flash a zip, choose the install option, find the name of the zip, select it, swipe to install it.

audit13 said:
To flash a zip, choose the install option, find the name of the zip, select it, swipe to install it.
Click to expand...
Click to collapse
The problem is that I didn't make a backup. When I tried flashing back to stock using fastboot everything was wiped. I don't even have the original custom ROM that started the whole mess. The stock file flashed but phone won't boot. I never get passed the boot loader warning screen. I did everything to the tee (following the directions that BBobby posted above. Actually did it twice. Isn't there an ODIN type deal for this phone. Brand new and I've broke it dangit.
Oh and I can't get into the phone to enable us debugging.

There is rsd lite but it may not help. Odin doesn't help if you can't enter download mode too. Usb debugging isn't require to flash a rom or install recovery.
It sounds like your phone is not booting because of the bootloade or the data partition is messed up.

I can get into bootloader and I have TWRP installed and can boot into it. I'm starting to think it's a lost cause. Thanks though y'all.

stacalicious said:
I can get into bootloader and I have TWRP installed and can boot into it. I'm starting to think it's a lost cause. Thanks though y'all.
Click to expand...
Click to collapse
I also got similar problem as yours. I have xt1033 dual sim phone and i had flashed lollipop 5.0.2 soak version. When official update was released for xt1033 i got back to kitkat 4.4.4 to download ota. But when i flashed kitkat through fastboot it got stuck on unlocked bootloader screen. Only solution i got still is converting to gpe. Only Gpe firmware boots. Im still finding solution for bootloop

You can get into TWRP? What happens when you use it to flash a custom ROM?

BBobby said:
http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware
Click to expand...
Click to collapse
audit13 said:
You can get into TWRP? What happens when you use it to flash a custom ROM?
Click to expand...
Click to collapse
I originally flashed a custom ROM but it never would get past the loading screen. I went through all the steps to flash back to stock and now all my data is gone. The ROM I had in my download folder is gone as is all my other info. So I get into TWRP but there's nothing in my phone I can flash.

audit13 said:
You can get into TWRP? What happens when you use it to flash a custom ROM?
Click to expand...
Click to collapse
I've flashed dozens, probably hundreds of ROMs in the past and never ran into such an issue. Custom ROM seemed to take, but got stuck. So I used fastboot and followed the directions to the tee in this link http://forum.xda-developers.com/showthread.php?t=2542219
When the ROM is finished flashing (stock that is) it never gets past the bootloader warning screen. If I could just get a zip onto the phone, I could flash through TWRP but I have no idea how to or if it's even possible.

Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.

esd316 said:
Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.
Click to expand...
Click to collapse
So I got into cwm. I can't mount usb storage, but I have an option to use adb sideload? Can I flash stock from there?

http://teamw.in/project/twrp2/233
Instructions on how to flash via fastboot are there in the same download page
---------- Post added at 02:47 AM ---------- Previous post was at 02:43 AM ----------
stacalicious said:
Quick question. When I go into recovery to flash the zip, do I go to 'advanced' and then ' terminal command'? and go from there? I feel like a noob and I've flashed dozens of roms...
Click to expand...
Click to collapse
The moto g just needs to do a wipe. Advanced wipe is not necessary. Then install the zip from the folder. By the way you can flash from USB otg (USB storage device such as a flash drive)

I fixed it!!!
stacalicious said:
I originally flashed a custom ROM but it never would get past the loading screen. I went through all the steps to flash back to stock and now all my data is gone. The ROM I had in my download folder is gone as is all my other info. So I get into TWRP but there's nothing in my phone I can flash.
Click to expand...
Click to collapse
esd316 said:
Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.
Click to expand...
Click to collapse
I'd hug your neck right now if I could get to you!!! I flashed cwm, went to adb sideload and installed a stock rom. My phone is back up and money isn't going to be pissed into the wind because I made a mistake. Thanks to everyone for your help.