Related
Need help and I assume I am stuck in a ‘soft brick’ state.
My Captivate does not advance past a kernel flash screen.
Upon boot, I receive the AT&T logo boot animation, then black screen, then with 5 seconds receive the splash screen of the Kernel developer (“Trident”). The phone remains stuck on this screen.
I can, however, initiate download mode and recovery mode (signs of hope).
In download mode I cannot get the device recognized by the multiple PCs I used to access the device by (the USB drivers are on the PC…..as evidenced through its functionality before). Consequently, and SDK / adb and ODIN* is of no help to me as an option to recover the device.
In recovery mode, I can apply sd card zips and have a few available (had several updates, superuser, kernels, etc downloaded prior to this device bricking) to apply. Of the zips available are;
CWM Recovery v3.0.0.5
Voodoo Lagfix
recovery CWM 2.5.1.2
SuperOneClick 1.9.5
ROM Kitchen Froyo ROM
11-254 Trident (Kernel Manager – ytt3r7 )
Click to expand...
Click to collapse
Backup file on device was from the day that the kernel was installed
After applying any of these zips (except the ROM Kitchen file) I will get an abort with the
“E:no misc partition” message.
>>>>>>>>>>>>>>once ROM Kitchen setup is applied it says "successful" then reboot it does the exact same thing as before (sticks in kernel splash screen)
For what its worth, this occurs with no SIM card and no SD card in the device.
*I have successfully used Odin on this device (usb functioning, recognized the device in Odin) and flashed/reset the device prior to this kernel problem.
** the reason I am in this position was because after receiving a warranty replacement (in stock 2.2 Froyo) I received the signature verification error. No amount of sidestepping this worked (I’ve read every page of the guides for this issue and they did not work) so I figured the easiest way around it was simply to replace the kernel (it wasn’t the bootloaders giving me errors). The phone was rooted, had superuser permissions, just could not apply any ROMs because of the sig verification.
To get a kernel to load (ROM manager / recovery mode zips did not work), I figured I would use market apps for this. I downloaded “Kernel Manager” from the market and applied the only kernel available (“Trident”). Once it applied the kernel, it left me stuck in the current stat I’m in.
*** I have read all previous "stuck in boot" threads and none of them have ANY troubleshooting methods available.
Just for clarification before further troubleshooting, you are putting the phone in download mode unconnected from the computer, starting up Odin, then connecting, correct? The only reason I ask is that I had some trouble with the computer seeing my messed up phone when I connected it prior to opening Odin.
correct - though, I've tried it in every sequence....ODIN (PC itself) doesn't see any USB device.
If I could get ODIN to recognize the device, I could wipe the phone and start over.
I guess my question is two-fold.
FIRST - Is it a correct assumption that this device is recoverable (not complete brick)?
SECOND - is there any way to fix the kernel loop from recovery mode?
1. I would assume yes, as you have activity from the phone.
2. Possibly. Hopefully you backed up (or don't care about) your apps, because most solutions at this point have a good chance of losing them. Also, from recovery, the first thing I'd do is a nandroid backup.
If you haven't tried this already, see if you can get Odin to recognize your phone while it's at the boot loop.
Next step would be trying to flash a kernel like Onix. You can do this one from CWM, so there's a chance it could fix your phone.
If that doesn't work, you could to grab a custom rom with a full wipe package (Firefly, for example) and see if you can run that from CWM. As it contains a kernel as part of the package, there is a chance you would be able to get your phone functional again.
I can't guarantee any of these methods, but they might help.
so - likely recoverable IF ODIN can recognize the device
BECAUSE there would be no other way to put the other kernels on the device (if you can't get the OS to load {past the kernel loop}
IF ODIN can recognize the device;
1. wipe/clear the device
2. load a different kernel through ODIN.
or is there another to load a kernel without ODIN?
Actually, from CWM recovery you can flash kernels (like the Onix one). Use the method you used before to get back there (holding V+/V-/power, i'm guessing), and assuming you have a way to get files to and from your micro SD card, just copy the onix kernel to your sd card and put it in your phone.
To flash the kernel, from the recovery menu select the "install zip from sd card" option, then "choose zip from sd card", and then navigate to where you saved it.
Assuming all goes well, it will overwrite the Trident kernel, and since Onix claims to work with stock roms, you should be back up and running.
jmtheiss said:
get files to and from your micro SD card, just copy the onix kernel to your sd card and put it in your phone. .
Click to expand...
Click to collapse
duh! (oy) that was genius....gawd, I can't believe I didn't even consider that.
T-H-A-N-K-S
I will try this
Ragin Caucasian said:
duh! (oy) that was genius....gawd, I can't believe I didn't even consider that.
T-H-A-N-K-S
I will try this
Click to expand...
Click to collapse
No problem. We all have those forest-for-the-trees moments.
Just as a heads-up, the onix kernel will be an intermediate step to a more final solution. The reason I say this is that it's based on I9000 source, so you would either need to flash an I9000 modem, or flash back to stock (overwriting the onix kernel). Either way wouldn't be difficult, but just something to remember.
i thank you for the feedback/help. This should work, unfortunately, it doesn't.
When attempting to load zip from sd-ext I get
E:no misc partition
Click to expand...
Click to collapse
when mounting the "/sd-ext" from CWM, I get
"E:failed to mount /sd-ext (no such file or directory)
Error mountin /sd-ext!
Click to expand...
Click to collapse
even if I attempt to format the /sd-ext, I get
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmblk1p2
Error formatting /sd-ext!
Click to expand...
Click to collapse
So I'm stuck / dependent on ODIN (correct)?
Hmm.. oddly enough, I can't get the mount /sd-ext on my phone to work either (same message). Odin is looking like it might be your only option right now, but we can try a few more things.
I know it's a long shot, but have you tried the "mount USB storage" option on that page and seeing if your computer recognizes that?
Also, do the "wipe cache partition" from the top-level menu, and "wipe dalvik cache" from the advanced menu. Once you've done those, retry earlier steps and see if any of those clear things up.
Just out of curiousity, what version/versions of Odin have you tried?
jmtheiss said:
Hmm.. oddly enough, I can't get the mount /sd-ext on my phone to work either (same message). Odin is looking like it might be your only option right now, but we can try a few more things.
I know it's a long shot, but have you tried the "mount USB storage" option on that page and seeing if your computer recognizes that?
Also, do the "wipe cache partition" from the top-level menu, and "wipe dalvik cache" from the advanced menu. Once you've done those, retry earlier steps and see if any of those clear things up.
Just out of curiousity, what version/versions of Odin have you tried?
Click to expand...
Click to collapse
The sd/ext won't work unless you have an ext partition on your SD card.
Have you tried re installing your drivers?
If you can get to DL mode your comp. should recognize your phone.
I dunno.....
I've tried 2 different PCs (win7....32 and 64 bit environment) neither recognize the device. I keep getting the
E: no misc partition
Click to expand...
Click to collapse
anytime I doing anything with the sdcard (internal / external)
I've been using Odin3 (which is what I used to flash it originally)
Like I said, I can boot into Recovery Mode (get the internal menu) or boot into Download Mode (yellow sign 'downloading....do not turn off target!") but I don't think this really is doing anything because the PC never recognizes it and I can get into this mode whether I'm connected to a PC or not.
When I attempt to run Heimdall it runs and immediately crashes. This is what it displays
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Heimdal Front end 1.1 used to work, but since the device isn't recognized, like ODIN nothing is presented to the application
I'm stumped. I just received this last Friday as a warranty replacement, I have 3 batteries and 2 usb cords, a rubber sleeve for the device willing to sell it all for $50 if anyone wants it.
Is the odin3 you're trying the one-click back to stock? Have you tried Heimdall? What version number shows up when you open it?
I used Odin3 v1.70 with my phone and had good luck. If you're using an earlier one, try using that one. If you're using v1.70, try an earlier version.
And to reiterate the earlier post, if you haven't tried uninstalling and reinstalling the drivers on your pc, that's worth a shot, too.
That dialog you're seeing with adb looks a lot like what happens if you run it without any arguments. Are you doing anything like "adb devices" or "adb reboot recovery"?
awesome!
Good news.....ODIN recognized the device
bad news......completely soft bricked the phone
I got the phone-<!>PC image and now the phone won't turn on again. great
I'll try the flux-capacitor jig fix sometime when I don't feel like strangling someone
Actually, you can use odin from the phone--!--pc screen. If you can get back there, try to flash the one click.
UPDATE
Bought the $10 jig (after my homemade resistor jig didn't work) - which works very well, btw.
* Uninstalled the USB drivers - reinstalled the USB drivers
* Used Odin3 1.8
* phone recognized by Odin.
* Flashed bootloader (what was originally wrong with the phone) and even a new ROM
Everything went FINE through Odin (first for me), even got a progress bar on my phone during the operation
now the phone is completely dead.
Will not give me the soft brick image.....can't go into download mode - nothing, completely unresponsive
$50....who wants it? This is a brand new phone just received as a warranty replacement....FOUR 1500m batteries, TWO USB cables, TV-OUT cable, and a rubber protective case
1. LG Flash Tool
This is the flashing tool that will let you install:
Any .kdz firmware. Ex. V10C_00.kdz
KDZ Files Available:
FROYO
V10C_00.kdz
V10D_00.kdz
V10E_00.kdz
V10K_00.kdz
GINGERBREAD
V20A_00.kdz
V20B_00.kdz
V20C_00.kdz
V20E_00.kdz
V20F_00.kdz
V20P_00.kdz - Official AT&T Gingerbread
V21A_00.kdz
V21B_00.kdz
V21D_00.kdz
V21E_00.kdz
Requirements:
You'll need to have the LG Thrill / Optimus 3D
All your data backed up
All LG Drivers Removed
DOWNLOAD LINK: LG Flash Package - 50 MB
How To Use:
Step 1
Download the .kdz file you want to flash
Extract the files with WinRar or 7zip
Uninstall all LG drivers
Restart computer
Step 2
In the "Drivers" folder, install the "LGUnitedMobileDriver_S4981MAN36AP22_ML_WHQL_Ver_3.6.exe" file
In the "Software" folder, install the "B2CAppSetup.exe" file
In the "SERVER" folder, launch the "shttp3.exe" file
An error may or may not pop up. Just click OK
Check the "I agree with this license, and I accept all items."
Check the "Update entry in main menu."
Check the "Add to startup."
Make the password "admin"
Click "Install"
Launch the "Small HTTP server" from the Start Menu
MINIMIZE the popup. If you close it, the server will quit.
On the TaskBar, a new icon should appear. Right click the icon and go to "Settings"
Select the "HTTP" tab and change the "Port" to "9002"
Click "OK" in the top right corner
Step 3
Navigate to "C:\shttps" on the hard drive
Copy the contents of "WWW Folder" into the "C:\shttps\www" directory
Navigate to "C:\Windows\system32\drivers\etc" on the hard drive
Copy the "hosts" file in "C:\Windows\system32\drivers\etc" to the "ORIG" folder in the LG Flash Package
Delete the "hosts" file from "C:\Windows\system32\drivers\etc"
Copy the "hosts" file from the "MOD" folder in the LG Flash Package to "C:\Windows\system32\drivers\etc"
Step 4
In the "FLASHING" folder, launch "Windows Enabler.exe"
A new icon should appear on the TaskBar. Click the icon to turn it to the "ON" position
In the "FLASHING" folder, install the "msxml.msi" file
Step 5
Open Device Manager
Windows XP - Right Click "My Computer", click the "Hardware" tab, and select "Device Manager"
Windows Vista/7 - In the Start Menu search bar, type "Device Manager" and select it at the top
Unplug your phone (If it is plugged in)
Take out the battery
Step 6
Check Device Manager for the current active "COM Ports"
Boot into DOWNLOAD MODE
Plug the phone into the computer without the battery inserted
Hold [VOL UP + POWER]
Put the battery in and wait until it vibrates or for 3 seconds
Check Device Manager for a NEW "COM Port"
If there is not a new "COM Port", restart Step 5
Step 7
Launch the "UpTestEX_mod2_marwin.exe" file
Change the product type located under the LG Electronics logo to "3GQCT"
Change the PhoneMode to "EMERGENCY"
Navigate to your .kdz file in the "Select kdz file" box
Click "Normal web upgrade test" at the bottom
Click "Upgrade Start" on the pop up screen
On the "Select Country & Language" box, click "Clear phone Software udpate Registry"
Change "Country" to "Different Country"
Change "Language" to your language
Click OK
Your phone is now flashing. DO NOT TOUCH THE PHONE AT ALL. DO NOT UNPLUG THE PHONE.
Step 8 : Varies
If your phone boots properly, ignore this.
Part 1: Booting into recovery
If your phone does not boot and you are stuck in a boot loop:
Boot into RECVOERY MODE
Hold [VOL DOWN + 3D]
Press the POWER button until the phone vibrates
Part 2: Wiping data in recovery
Use VOL DOWN to navigate to "wipe data/factory reset"
Press the "3D" to select it
Use VOL DOWN to navigate to "Yes"
Press the "3D" to select it
Restart the phone
Step 9 : Optional
Root using one of the three SuperOneClick versions in the LG Flash Package folder
Install ClockworkMod or Touch ClockworkMod Recovery with Recovery Manager
2. Entering APNS
This example is for AT&T "4G" HSPA+ APNs
Getting To The APNs
Go to the "Settings" app
Select "Wireless & networks"
Select "Mobile networks"
Select "Access Point Names"
Setting Up The APNs
Press the Menu button
Select "New APN"
Select "Name"
Change it to "AT&T HSPA+"
Select "Ok"
Select "APN"
Change it to "phone"
Select "Ok"
Select "MMSC"
Change it to "http://mmsc.cingular.com"
Select "Ok"
Select "MMS Proxy"
Change it to "wireless.cingular.com"
Select "Ok"
Select "MMS Port"
Change it to "80"
Select "Ok"
Select "MCC"
Change it to "310"
Select "Ok"
Select "MNC"
Change it to "410"
Select "Ok"
APNs SET!
3. Booting into and Navigating Recovery Mode
Booting into Stock Android Recovery
Boot into RECVOERY MODE
Hold [VOL DOWN + 3D]
Press the POWER button until the phone vibrates
Using Stock Android Recovery
VOL + and VOL - is to move up and down
Press the 3D button to select an option
Booting into ClockworkMod Recovery
Boot into RECVOERY MODE
Hold [VOL DOWN + 3D]
Press the POWER button until the phone vibrates
Alternatively for ClockworkMod:
Go to Settings
Go to Privacy
Choose Factory Reset
It will boot into ClockworkMod.
Using ClockworkMod Recovery
VOL + and VOL - is to move up and down
Press the POWER button to select an option
4. Flashing CyanogenMod 10
Step 1. Revert to Complete Stock Gingerbread
Use the "LG Flash Tool" in this post to do this. [I ADVISE USING V21E]
Step 8 in the guide HAS to be done. Make sure you wipe data.
Step 2. Root Phone
Use "Megatron Root" in the second post to do this.
Step 3. Install ClockworkMod
Use "Recovery Manager" in the second post to do this.
DO NOT USE TOUCH CLOCKWORKMOD.
Step 4. Download CM10 & GAPPS
CM10: DOWNLOAD
GAPPS: DOWNLOAD
Step 5. Boot Into CWM and Flash CM10+GAPPS
Use the "Booting into and Navigating Recovery Mode" Guide if you do not know how to navigate ClockworkMod
[COLOR]DO NOT REBOOT[/COLOR]
Step 6. Wipe Data & Reboot
Wipe the data from CWM and reboot.
You should now be running CM10!
[TOOLS]
1. Recovery Manager
This is a flashing tool that will let you install:
Stock Recovery
ClockworkMod Recovery
Touch ClockworkMod Recovery
Requirement:
You'll need to have the LG Thrill / Optimus 3D
You'll need to be rooted.
Superuser and SU have to be updated to the latest app and binary
Update Superuser in the market
Open Superuser app and go to the options
Scroll to the bottom and click "Su binary"
DOWNLOAD LINK: Recovery Manager - 18 MB
How To Use:
Extract the files with WinRar or 7zip
Launch "Recovery Manager.bat"
Make sure your phone is in "USB Debugging Mode" and is plugged in
Choose your option
Wait for the screen to refresh
Boot into recovery to verify it was flashed successfully
2. Megatron Root
This is a root tool by Dan Rosenberg that will let you root:
V20x Firmware
Any other Gingerbread Firmware that SuperOneClick can't root
Requirements:
You'll need to have the LG Thrill / Optimus 3D
LG P920 Drivers installed
DOWNLOAD LINK: Megatron Root - 1 MB
How To Use:
Extract the files with WinRar or 7zip
Make sure your phone is in "USB Debugging Mode" and is plugged in
Launch "run.bat"
Wait for the phone to reboot
Verify that root is enabled
ROOT DONE!
CM10 (In)Compatible Basebands
This is a list of what basebands are compatible with CM10. If it's not compatible, you will not get any cell reception.
CM10 Compatible Basebands
V21D
CM10 Incompatible Basebands
V20P
V21E
Nice compilation.
Please include links to ROMs
20E - http://csmg.lgmobile.com/swdata/WEBSW/LGP920/AAFRML/V20e_00/V20E_00.kdz
20F - http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP920/ABUOML/V20f_00/V20F_00.kdz
20E has RTL support and 20F is the latest one available.
omgomg said:
Nice compilation.
Please include links to ROMs
20E - http://csmg.lgmobile.com/swdata/WEBSW/LGP920/AAFRML/V20e_00/V20E_00.kdz
20F - http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP920/ABUOML/V20f_00/V20F_00.kdz
20E has RTL support and 20F is the latest one available.
Click to expand...
Click to collapse
Alrighty! I'll add them up.
Sent from my Samsung Galaxy S II w/ CM9
This should be a sticky and updated regularly.
Great post
Really nice work - Lestat!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks a lot!!!!
Greetz Paki
Great for newbies..
Great job! But how can I extract the contents of the .kdz firmware file without actually installing it? (Please note that I'm not at all familiar to the LG-way of doing firmware.)
E:V:A said:
Great job! But how can I extract the contents of the .kdz firmware file without actually installing it? (Please note that I'm not at all familiar to the LG-way of doing firmware.)
Click to expand...
Click to collapse
There's currently no point of extracting the contents because they are encrypted.
Sent from my Samsung Galaxy S II w/ CM9
Hello, please help me. i bought optimus 3d p920 from UK, was on stock 2.2.2, had rooted n installed clockwork v5.0.2.0, i have backed up the stock rom via CWR, i software updated from mobile , it was a 4.5mb update n after that the phone is not going past CWR, i tried to restore backup via CWR no luck. please help is my phone is bricked?Thanks
Try to fix permissions.
If it doesn't work, refer on this section to two guides about manually updating via KDZ. It's piece of cake, so don't worry, your phone isn't bricked at all.
Thanks for the reply, i tried to flash kdz file but, after port change step when i try to launch B2CAppSetup.exe , it says no internet connection , connect to internet then continue, even though my net is on. what iam i doing wrong?
Wouldn't work for me. When I got to clicking Start update it jumped straight to the usual update app and told me my phone was on latest firmware... I guess it was to do with the shttp; I couldn't use it because crappy Symantec End Point threw a fit when I extracted the archives so I tried using WAMP (Apache server) and changed the port to 9002 as instructed...
Also my phone went crazy trying to get into download mode. I had to time releasing VOL+PWR when device manager detected the port or it told me I had unplugged it.
After I gave up I had to reboot my phone three times and then set the clock!
I'm stuck with 21a still
sourcewop said:
Hello, please help me. i bought optimus 3d p920 from UK, was on stock 2.2.2, had rooted n installed clockwork v5.0.2.0, i have backed up the stock rom via CWR, i software updated from mobile , it was a 4.5mb update n after that the phone is not going past CWR, i tried to restore backup via CWR no luck. please help is my phone is bricked?Thanks
Click to expand...
Click to collapse
Where did the update cone from? Your service provider?
Sent from my Samsung Galaxy S II w/ CM9
If you need help flashing, download the LG Flash Package, and Recovery Manager. Install TeamViewer and I can flash your phone for you.
Sent from my Samsung Galaxy S II w/ CM9
Right, managed to flash my phone at home on my laptop but after rooting and installing Touch CWM, I finally booted my phone, went through the initial setup wizard and then was asked which launcher app I wanted to use; LG one or GO Launcher???!!!! Bearing in mind that I have formatted the internal and external storage, gone to CWM and done factory reset, where the hell is this coming from? I looked in manage applications and I can see GO Launcher is installed (along with its widgets and themes), ES File explorer is installed and so is AlarmClock Plus... WTF!
I downloaded the KDZ from LG site so I cant see it being dodgy but I am totally confused where it got these apps from and how it installed them... I know you can put .apk files in a certain folder on the sdcard and it will auto install them but I dont have these apk's at all!
Hsd the ROM been really clever and realised I had these apps on before when I tried 21B and found I couldnt root it??
Anyway! Thanks for an awesome guide.. I did have to make a couple of changes to get mine to work...
When installing the B2CApp updater, I had to put the HOSTS file back the orig or it wouldnt install.
When trying to get into Download mode, I had to again time the release of the vol/pwr keys or it said the drivers failed to install...
But thanks a bunch! I am now on V21d
cyberguru said:
Right, managed to flash my phone at home on my laptop but after rooting and installing Touch CWM, I finally booted my phone, went through the initial setup wizard and then was asked which launcher app I wanted to use; LG one or GO Launcher???!!!! Bearing in mind that I have formatted the internal and external storage, gone to CWM and done factory reset, where the hell is this coming from? I looked in manage applications and I can see GO Launcher is installed (along with its widgets and themes), ES File explorer is installed and so is AlarmClock Plus... WTF!
I downloaded the KDZ from LG site so I cant see it being dodgy but I am totally confused where it got these apps from and how it installed them... I know you can put .apk files in a certain folder on the sdcard and it will auto install them but I dont have these apk's at all!
Hsd the ROM been really clever and realised I had these apps on before when I tried 21B and found I couldnt root it??
Anyway! Thanks for an awesome guide.. I did have to make a couple of changes to get mine to work...
When installing the B2CApp updater, I had to put the HOSTS file back the orig or it wouldnt install.
When trying to get into Download mode, I had to again time the release of the vol/pwr keys or it said the drivers failed to install...
But thanks a bunch! I am now on V21d
Click to expand...
Click to collapse
That is strange indeed. I haven't downloaded V21D so I wouldn't know, but you did a data wipe in recovery?
Sent from my Samsung Galaxy S II w/ CM9
Yep, did a full wipe in recovery before doing anything...
Not to worry though, I removed the apps and then took a backup of the ROM for future use!
HEY dark its me it was starting to load but in the middle of the process it said communication error or something?
Hello,
I'm a mega noob. Now that's out of the way I posted a question on tomshardware about a broken tablet. I was directed here when ASUS replied to my question. They said to hold the Power Button and the Volume Down button, if I got there then upload the firmware. I don't know the middle part though! So I see a screen with three options. The first one says "RCK", the second one is the Android Logo with the Android name below, finally there's a box with an arrow coming out pointing at a little android guy and the words "Wipe Data". What should I select, what should I do next?
It is running Android 4.2.1 stock, never unlocked
The tablet was working just fine until one day it got stuck on the loading screen and stayed at the screen. If I can fix it, It's mine!
Thank You,
Fast replies are appreciated.
First off, what is your problem? Also, whatever you do, DO NOT SELECT "WIPE DATA" OR YOU WILL BRICK!!!
Is your bootloader unlocked?
Edit
I updated the my Post with more information.
McGirk242 said:
I updated the my Post with more information.
Click to expand...
Click to collapse
I suggest downloading the firmware from Asus website and downloading the correct firmware. Take care as there are two different versions of the tablet TF300T and TF300G. Once you have downloaded the firmware place it on your SD card. Reboot into the three icon screen and press RCK menu and install/flash the downloaded firmware. If you would like to unlock and root the tablet then I can help you with that too.:good:
Yes you can try the above method to re-flash the stock firmware, however once you have downloaded the firmware zip before you put it on your microSD you will need to unzip this firmware zip and you will find a second zip inside - and this is the zip file that you need to put on your microSD card.
As stated above you can then boot to your bootloader screen and select the RCK which on stock will boot to the stock recovery which will be a green android which should then show a blue progress bar under the green android - let it complete and then the tab should reboot and be all good.
If it does not work you will see the android laying on it's back with chest open - if this is the case you can try the fastboot method to flash the system blob which seems to work even with a locked bootloader - link to my how-to can be found in my sig below, if you need help with any steps just let me know.
A few questions
pjc21 said:
Yes you can try the above method to re-flash the stock firmware, however once you have downloaded the firmware zip before you put it on your microSD you will need to unzip this firmware zip and you will find a second zip inside - and this is the zip file that you need to put on your microSD card.
As stated above you can then boot to your bootloader screen and select the RCK which on stock will boot to the stock recovery which will be a green android which should then show a blue progress bar under the green android - let it complete and then the tab should reboot and be all good.
If it does not work you will see the android laying on it's back with chest open - if this is the case you can try the fastboot method to flash the system blob which seems to work even with a locked bootloader - link to my how-to can be found in my sig below, if you need help with any steps just let me know.
Click to expand...
Click to collapse
So I need to unzip the file from ASUS.com when it's on the MicroSD before or after? Do I put the file on the internal or on an external SD Card? What is the zip file in the zip file called? Thank You, you guys have brought me one step closer to ending this thing.
McGirk242 said:
So I need to unzip the file from ASUS.com when it's on the MicroSD before or after? Do I put the file on the internal or on an external SD Card? What is the zip file in the zip file called? Thank You, you guys have brought me one step closer to ending this thing.
Click to expand...
Click to collapse
I usually download the firmware to the PC first as sometimes these tablets seem to have issues downloading large files.
Which firmware version are you wanting flash/install?
When you download the firmware it will be called, depending on which firmware version - TF300T-WW_epad-10_6_1_15_3-UpdateLauncher.zip
Unzip this to a folder and inside you will find another zip called WW_epad-user-10.6.1.15.3.zip - Copy this zip file to your microSD.
With microSD in tab reboot to bootloader - hold vol- & power - In bootloader menu "vol-" is to move between what icon is highlighted.
"vol+" is to select/execute what is highlighted.
Highlight the "RCK" icon and select.
The tablet should now boot to the stock recovery which should a black screen with a green android with a blue progress bar underneath. This should take between 5-10 minutes to complete and then the tablet should reboot. If so the tablet should boot up to the setup wizard to setup the tab, Done. :good:
If this is not the case and you get a green android laying on it's back with it chest open and I think a red explanation icon it has not worked. I would then try the fastboot method of flashing the system blob. Have a look at my how-to in the sig below for details on this method, you will also need fastboot installed on the pc first - Installing android sdk and updating it to the android version your wanting to flash should also install fastboot and adb drivers.
If the first method does not work and you need help with the second just let me know.
Phone: Huawei Ascend Y300-0100
Problem: After trying to install the Xposed framework using the option "Create .zip and install automatically", the phone will show the Huawei logo, then flash the Teamwin logo, then just show a black screen (while the back, home and menu buttons are lit).
Status before the problem occurred:
- Rooted and custom TWRP custom recovery installed
- user data backed up (sadly no complete image created, as I naively assumed factory roms to be available)
- Tried to install Xposed framework "directly in the system", but still received message "most recent version not active" after restart
Things I have tried and results:
- Recovery mode (Power on and Volume Up): Same thing as normal startup
- Flashing several Firmware versions from SD card (Power on, Volume up and down):
- SDHC Card 32GB (Transcend): Error as soon as Step 2: Installation is reached
- SDHC Card 32GB (SanDisk): During Step 1: Extraction, the progress bar keeps resetting- Flashing TWRP custom recovery again using fastboot: Completes without errors, above behaviour unchanged.
I read on another forum that the success of flashing things from SD cards depends heavily on the SD card itself and I do not have access to any other SD cards at this time, so I would like to try something that doesn't rely on SD cards. I have not been able to find any existing factory roms (.img) for this particular phone (just many dead links). So my first question is:
- Can anyone point me to a source of factory roms for this model that is still online?
I have found firmware versions in the form of "UPDATE.APP" files (that I tried flashing from the SD cards), so my second question is:
- Is there a way to install an UPDATE.APP file without using an SD card?
If there are any other/better solutions to my problem, I am grateful to hear them as well.
Update:
I have found a Perl script by marco.minetti to extract the contents from the UPDATE.APP file, but they all have the same name ("INPUT"), so now I need a way to find out what each file is.
There is a Thread from 2013 by GalaxyUser, in which he talks about a script that "guesses" the files, but the link is a dead google doc.
New questions:
- How do I find the correct files?
- Does anyone have an idea as to why the custom recovery is not working even after reflashing it?
The Windows program "Huawei Update Extractor 0.9.9.5" was able to identify the different files when choosing the profile for G610-C00 and others. After flashing the stock recovery from "Y300-0100 V100R001C00B176CUSTCZEC40D001 TA", the phone boots normally.
I wonder if this is an incompatibility between TWRP recovery and Xposed or a problem with TWRP and .zip installers in general. I will try installing Xposed without TWRP when I have the time and post the results here.
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any thoughts please?
I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.
akhilarora666 said:
type "Oneplus 7 Downgrade Firmware".
Click to expand...
Click to collapse
Thank you for your encouraging message.
That article you mentioned says this:
copy the Rollback package to the phone’s internal storage.
Go to device Settings > System > System Updates > Tap on top right icon > Local upgrade > Select the installation zip package > upgrade > System upgrade completed to 100%.
Click to expand...
Click to collapse
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
akhilarora666 said:
I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.
Click to expand...
Click to collapse
That's not possible when you have no os anymore...
who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
Just stay on xda-developers, no need for suspicious off site downloads.
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Or the unbrick tools: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
In my case, I was stuck too. So i did "fastboot boot recovery.img" tried both android Q and android pie revocery. (version 70 and 65) (editied versions by mauronofrio) one of them worked. I got into the recovery. then installed the android Q stock firmware zip file. Thing is, i dont know why, but once you are on android Q, your phone stops supporting android PIE. Since you were on android Q once, you have to go back there. only then follow the external website i linked.
Like the other guy said, you can stick to XDA and try the unbrick tools. but for me they didnt work. So i followed that website. then everything was fine. Ofcourse its fishy. but once you are back on pie, you can reinstall any pie rom you want.
strongst said:
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Click to expand...
Click to collapse
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)
who ah way said:
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)
Click to expand...
Click to collapse
Your screenshot is the fastboot screen. Stated with: fastboot
If your device is not recognized, maybe you should check your adb drivers etc.
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
Same situation happened to me but due to wipe in twrp vendor image
who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
You used a nandroid backup which is what resulted in the brick. Nandroid backups do not backup firmware
Anyway try
fastboot --set-active=a
Then reboot and see if it boots
Or try
fastboot --set-active=b
If that doesn't work download twrp and flash it to the boot partition
fastboot flash boot whatever
Reboot and you should have twrp
Which twrp to flash? The one for Q firmware. It's obvious
---------- Post added at 22:31 ---------- Previous post was at 22:25 ----------
who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
I do not know how you formatted cache on a device that doesn't have a cache partition