Hi,
A friend gave me a Storage Options Scroll 7" Model 51624 (TCC8902) with 2.1.
I found that cyanogen has a 2.3 Rom for this device so I tried to flash it.
I flashed the clockwork recovery and did my back up. Then I downloaded the rom from cyanogen and installed.
What was my surprise that when I restarted it got stuck on the main screen with the logo "scroll Storage Options"
I tried to enter the recovery but doesn't work!!!
I think my error was the rom I choose for flashing.
I used the Storage Options Scroll 7" resistive 8K, and I know now that mine is the same one but the resistive 4K.
I though I could do something if I could use the Adb commands and some inspiration but the problem is that my computer doesn't recognize the device (Android in yellow on device manager). I installed the Android SDK that has the google usb driver but still not working. I tried the VTC 5.0.0.1 drivers too but no luck either.
I desperately need some help to install the boot recovery and then I'll flash the right rom.
I use windows 7 x64 and a laptop with windows xp 32.
I've been reading the thread http://forum.xda-developers.com/showthread.php?t=1101094 but has 163 posts and I have to say that I didn't read all of them. Anyway I did a search about bricked scroll and didn'f find anything. If someone knows where to point me at I'll be very gratefull. I appologize if my posts is already solved somewhere.
Thanks in advance
there is a guide on getting android adb set up on the pc with modified drivers somewhere...
1st things 1st though, have you tried holding vol up while turning it on to get into recovery?
as long as you installed the custom recovery correctly (which im sure you did if you managed to install another rom), then you should have no problem getting into it.
unless, that is, you dont have any volume buttons to get into recovery / they dont work!
Sent from my MB860 using xda premium
To flash the cyanogen rom I had to enter the clockwork recovery with the power+vol up. So first thing I did after realised it wasn't going to load the rom was to restart the tablet into recovery but it doesn't work.
That's why I was thinking the posibility of flashing clockwork recovery again through the adb commands or maybe the boot.img (I think this img is the one responsible for boot). But as I said my computers don't recognize the device. Both says Android with the yellow warning.
I'm looking for this modified drivers but can't find them. any web site address?
I have downloaded the firmware from Storage options but as I cant enter into the recovery I can flash it.
OK, to be fair I don't know whether to blame LG or Microsoft, but in the middle of upgrading my G2X it looks as if the crappy Windows drivers quit talking to the phone.
The LG software instructed me to do a battery pull and try again, but the result is the phone is now stuck in "S/W Upgrade" display. It won't not respond to the Windows update program. Reinstalling drivers does not help.
It won't boot Android. It's useless.
Rebooting with the sound buttons depressed gives me a black screen, no recovery program.
I have the Android SDK on my Linux laptop, but it doesn't find any USB devices, regardless of whether I do a straight boot or attempt recovery mode.
I have a Linux version of nvflash, which also can't find the device, so http://forum.xda-developers.com/showthread.php?t=1610562 is no help.
What next?
If you have a Windows computer accessible:
http://forum.xda-developers.com/showthread.php?t=1180331
404 land
Sadly most of the links in that thread point to 404s, so I am not able to find the Windows one-click CWM flasher, but I found this
http://search.4shared.com/postDownload/9h4mmcSp/nvflash-cwm_recovery-5027.html
which is a Linux nvflash binary, script, and CWM package. With enough fiddling around I managed to get Linux to detect the device and nvflash to install Clockwork, so I'm at least that far.
Now to figure out how to get rid of that upgrade screen ....
You ran into the exact same thing I ran into about 6 months, literally to a "T".
The link posted above by another member is what I followed, and it fixed the problem for me.
I hope you are able to find the various non-dead files/links!
Good Luck!
Scott
Here is the One-Click NVFlash for windows:
[RECOVERY][APP] 4-28:One-Click NvFlasher ClockWorkMod Touch 5.8.1.3/5.0.2.0/4.0.1.5
Also the KDZ flasher is probably the only way you're going to get the update finished, and you'll have to do that on XP.
XP
I have an XP laptop, but the KDZ flasher crashes when I try checking the phone configuration, and I have not been able to locate a KDZ file for the GX2. Pretty much everything in that thread resolves to a removed file, or a dead domain.
Oh, here's the V21y kdz.
You shouldn't need to check phone configuration, just open the kdz flasher,select the kdz file, and hit go.
EDIT: Yup, from the other thread:
speedsk8x said:
7) Run KDZ_FW_UPD.exe.. Leave the type set to CDMA and the phone mode set to DIAG. DO NOT CLICK ON "Read phone information"
8) Click the folder icon and load the V21E_00.kdz
9) Click launch software update (and pray!)
Click to expand...
Click to collapse
Partial success
I had partial success with these instructions
http://forum.xda-developers.com/showthread.php?t=1248644
... except that the device drivers were not Win7 compatible and I had to chase down the correct drivers by Googling for Nvidia APX drivers. Once that was done, I was able to nvflash back to a stock system and get out of the LG "S/W Update" bootloader problem.
However, the phone radio isn't working. The cited thread recommends updating using either the KZ loader or the LG Update tool after flashing, so I guess that's my next stop.
Decoding the instructions:
Removing the battery, holding down BOTH volume controls, and plugging in USB puts the phone in to "APX" mode. It will show up as an unknown device in Windows, which allows you to install the device driver. After that the nvflash utility can reflash all the phone's memory.
try this
This happend to me a month ago and took me till 4am to solve...
disclaimer this worked for me but your mileage may vary
First update your lg drivers here
dropbox.com/s/8hibwel69plml4w/LG%20_USB%20_Drivers_All_4.9.7.zip
The only way I found to get it out of the s/w update mode was to use this custom nv flasher that restores it to stock V21E over apx mode
dropbox.com/s/g2eli2mjapfhd0k/G2X_V21E_00_NVFlash.zip
it also includes the nvidia apx drivers
you get to apx mode by taking the battery out and holding both volume buttons down while pluging the usb cable in ... you can let go of the buttons after you see the update screen
after that your phone should boot up normal...skip syncing google account... now with your drivers updated try the lg update tool again... to me the lg tool is the most straight forward way to get the updated baseband... after this works you'll be on stock V21Y with new baseband Mar 11 2012...
now for recovery and backup use this and pick CWM 5.0.2.0
dropbox.com/s/odypked2aqha11i/One-Click-G2x-recovery-flasher-04-28-12.rar
after you have that done you can then flash this stock rooted V21Y via copy it to your sd card
dropbox.com/s/4db1h60uj7gmvpq/p999_2.3.4_v21y_4142012.zip
Thanks...
Thanks for the links! I'll try again with those versions and see if I can get the LG updater (which caused all this trouble in the first place) to work properly. I am still getting failures when it is connecting with the phone.
While I do have nvflash working (on the win7 laptop) and am able to flash CWM and install ROMs, the phone still doesn't seem to know it's a phone. The T-mobile wifi calling app says the SIM is bad.
I flashed Eaglesblood ICS, which was easy and looks like it's a great ROM, but the phone still doesn't work.
Check the "Rom for Recovery" thread in the Dev Section. Follow the instructions. It should get you up and running in no time.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Massive fail...
delete please, I post in wrong thread.
Hi everyone, first post here, but I've been reading this forum for some time now.
I've got an asus transformer pad tf300t 3 days ago. Last night, I tried to install cyanogenmod10, I unlocked the device, and installed clockworkmod, everything was fine until I accidentaly entered recovery mode and wipe all data, now the tablet only shows the asus logo and enteres in to a bootloop (I think). I can't enter recovery mode, ADB doesn't recognize it, fastboot neither and I can't even turn it off. I can't enter recovery, it just shows me the asus logo again.
HOWEVER, I waited until the battery drained, connected the usb cable to the tablet (not in the computer) pressed + volume button and without releasing it, connected to pc. Now the computer detects new hardware. I already installed the driver and it says "ASUS TRANSFORMER PRIME APX INTERFACE". Now, i'm not sure if it's the correct driver, but according to hardware administrator, it works fine.
Now, the real cuestion: Is there anything I can do from apx mode to save my tablet? A new bootloader maybe??
Thanks everyone
PS: Sorry for the bad english, It's not my language
from the loop,If you hold the power button for 10s when reboot and immediatly press the volume down button, what you have asus loop or the screen with the 3 icons (RCK ecc) ?
Claudisimo said:
Hi everyone, first post here, but I've been reading this forum for some time now.
I've got an asus transformer pad tf300t 3 days ago. Last night, I tried to install cyanogenmod10, I unlocked the device, and installed clockworkmod, everything was fine until I accidentaly entered recovery mode and wipe all data, now the tablet only shows the asus logo and enteres in to a bootloop (I think). I can't enter recovery mode, ADB doesn't recognize it, fastboot neither and I can't even turn it off. I can't enter recovery, it just shows me the asus logo again.
HOWEVER, I waited until the battery drained, connected the usb cable to the tablet (not in the computer) pressed + volume button and without releasing it, connected to pc. Now the computer detects new hardware. I already installed the driver and it says "ASUS TRANSFORMER PRIME APX INTERFACE". Now, i'm not sure if it's the correct driver, but according to hardware administrator, it works fine.
Now, the real cuestion: Is there anything I can do from apx mode to save my tablet? A new bootloader maybe??
Thanks everyone
PS: Sorry for the bad english, It's not my language
Click to expand...
Click to collapse
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
tobdaryl said:
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
Click to expand...
Click to collapse
Hi.
This procedure can be applied and can solve a same issue if until to brick the tablet I installed Android 4.1.1?
Thank you
tobdaryl said:
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
Click to expand...
Click to collapse
Sadly, the tablet came with Android 4.1.x :S
atoma1972 said:
Hi.
This procedure can be applied and can solve a same issue if until to brick the tablet I installed Android 4.1.1?
Thank you
Click to expand...
Click to collapse
Use of the bootloader information may allow access to recovery, adb, or fastboot. Access to any of the three may allow the ability to recover your tablet.
None of the ways worked for me.... can't access that menu...
Claudisimo said:
None of the ways worked for me.... can't access that menu...
Click to expand...
Click to collapse
If you still have no adb, fastboot, or recovery I don't know how to help.
Same situation
tobdaryl said:
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
Click to expand...
Click to collapse
Hi, I'm in the same situation, only APX accesible, my last rom was 4.2.1, but i have my NVFLASH backup files created with this tool when my device had stock ICS ROM
http://forum.xda-developers.com/showthread.php?t=1894867
Is something or a tutorial that I can do to bring my device alive using NVFLASH?
Thanks
Mynzer said:
Hi, I'm in the same situation, only APX accesible, my last rom was 4.2.1, but i have my NVFLASH backup files created with this tool when my device had stock ICS ROM
http://forum.xda-developers.com/showthread.php?t=1894867
Is something or a tutorial that I can do to bring my device alive using NVFLASH?
Thanks
Click to expand...
Click to collapse
Rayman the dev and op for nvflash suggests this as a first option.
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
Here is the thread where he posted this info.
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/show....php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
UI for blobtools - http://forum.xda-developers.com/show....php?t=2012033
Good Luck!
Note: for recovery I suggest twrp(since you'll be in ICS choose one for ICS and TF300T)!
It Work
tobdaryl said:
Rayman the dev and op for nvflash suggests this as a first option.
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
Here is the thread where he posted this info.
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/show....php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
UI for blobtools - http://forum.xda-developers.com/show....php?t=2012033
Good Luck!
Note: for recovery I suggest twrp(since you'll be in ICS choose one for ICS and TF300T)!
Click to expand...
Click to collapse
Thank you so much, my device comes back from hell, and it's ready to use, the firmware returns to ICS, but I updated again to JB
:good:
Mynzer said:
Thank you so much, my device comes back from hell, and it's ready to use, the firmware returns to ICS, but I updated again to JB
:good:
Click to expand...
Click to collapse
Great! I'm glad I could help.
help...
Mynzer said:
Thank you so much, my device comes back from hell, and it's ready to use, the firmware returns to ICS, but I updated again to JB
:good:
Click to expand...
Click to collapse
Hi Mynzer,
Could you explain here how you do to un brick or avoid bootloop with twrp please ?
Fullpoweradonf said:
Hi Mynzer,
Could you explain here how you do to un brick or avoid bootloop with twrp please ?
Click to expand...
Click to collapse
Of course, my tablet had the bootloop error with TWRP and the new 4.1.2 JB update.
When my device had stock ICS ROM (long time ago), I followed this tutorial, this allow you to create some backup files from your device, which in the future will allow you flash your tablet througth APX mode (more powerfull that fastboot mode) and the NVFLASH utility
http://forum.xda-developers.com/showthread.php?t=1894867
The only isue is that you need a pre-JellyBean bootloader (ICS) in order to make those backup files, if you are in a JB stock ROM (JB-bootloader), you can't make this backup files (Asus block the way that we can backup this files on JB ROMs).
With my backup files, the nvflash tools (from the tutorial above), and the instrutions that post tobdaryl, I manage to restore my tablet to an ICS ROM
If you are interested, there is a online petition (but i don't remember were :silly asking that Asus allows the NVFLASH backup utility on JB-bootloaders. With NVFLASH and ours backup files, we can restore our devices from any type of soft-brick.
In the case that your TF300 had and stock ICS (or you can flash it one), I can assist you in the case that you have troubles making the nvflash backup files with the tutorial
Would be nice if you could use someone else's file to fix a brick. Has anyone tried it.
Mynzer said:
Of course, my tablet had the bootloop error with TWRP and the new 4.1.2 JB update.
When my device had stock ICS ROM (long time ago), I followed this tutorial, this allow you to create some backup files from your device, which in the future will allow you flash your tablet througth APX mode (more powerfull that fastboot mode) and the NVFLASH utility
http://forum.xda-developers.com/showthread.php?t=1894867
The only isue is that you need a pre-JellyBean bootloader (ICS) in order to make those backup files, if you are in a JB stock ROM (JB-bootloader), you can't make this backup files (Asus block the way that we can backup this files on JB ROMs).
With my backup files, the nvflash tools (from the tutorial above), and the instrutions that post tobdaryl, I manage to restore my tablet to an ICS ROM
If you are interested, there is a online petition (but i don't remember were :silly asking that Asus allows the NVFLASH backup utility on JB-bootloaders. With NVFLASH and ours backup files, we can restore our devices from any type of soft-brick.
In the case that your TF300 had and stock ICS (or you can flash it one), I can assist you in the case that you have troubles making the nvflash backup files with the tutorial
Click to expand...
Click to collapse
Could You explain step by step which driver and how do you get up Yours TF300T?
I have the same problem, only recovery starts (TWRP2.5.0.0)
possible brick?...
After downgrade the console from the v. 4.2 to 4.1, following tutorials in this forum, because it would not let me install a Custom Rom (yes the recovery, not the root) I can think of to make a choice Wipe from the Stock 4.1 Recovery and restart WW I stand still Asus logo, white, and trying to restart pushing Recovery again, I go and I follow the fixed logo. I do not recognize the device SDK and have seen many posts and I can not find the solution ... buf! Someone has been the same? ... The strange thing is that lights ...
In case nothing else works (another fix) worked for me!
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps, don't forget to hit thanks button if it works =)
i have an odd question
i have an odd question. i bricked my tab. it's stuck on asus logo and no access to fastboot. just access to apx mode but i haven't nvflash beckup. my question is: did is possible sometime in the future will be able to unbrick my tab. to wait an new solution to arrive, if that is possible, or there no chance for that. can anybody answer to my naive question please
racerocm said:
i have an odd question. i bricked my tab. it's stuck on asus logo and no access to fastboot. just access to apx mode but i haven't nvflash beckup. my question is: did is possible sometime in the future will be able to unbrick my tab. to wait an new solution to arrive, if that is possible, or there no chance for that. can anybody answer to my naive question please
Click to expand...
Click to collapse
If you cannot access to fastboot, IMHO there's nothing you can do. I am in your same boat: no adb and fastboot access, my PC recognize the tablet only in APX mode but with NVflash I cannot do anything because I not have a backup.
Bye
EDIT: I am in this situation after a wrong recovery flash. I flashed a new recovery but I could not load it and I made the (big) mistake to try a wipe from the recovery menu. My Tf300t is now stuck at asus logo and I cannot access to the bootloader anymore. I do not know what to do, is the tablet definitely bricked or there's something I can try before going to ASUS service?
Thanks in advance.
Bye
I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.
XDA Visitor said:
I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.
Click to expand...
Click to collapse
Hard/factory reset would have been my first answer too.
Is your issue similar to this one: Boot verified failed after update PLEADE HELP?
Maybe you can unbrick it like described here: [GUIDE] How to unbrick Acer Iconia A500.
And if you need further help, please register on xda and ask in the thread directly.
Good luck !
Thread closed. Thank you!