Related
Got an at&t tab here, I upgraded to JM6, flashed the modem, and rooted it, all was well, untill I realized that I couldnt get into recovery to wipe. So I went into d/l mode, and couldnt get out, loaded up Odin3 and attempted to flash the bell modem again just to get it to reboot. Well it froze up, and now all I get is a communication error picture: "phone ----- !-----PC"
Help please, its brand new and going to be sold
From my experience you can power off the unit, put it in dl mode again flash the Bell modem with no partion, no pit and with reboot selected and it should do a regular startup!
Sent from my GT-P1000 using Tapatalk
I lost d/l mode. But somehow the second time I attempted to flash JM6 with odin, while seeing this error message, it worked. So its working again.
But I have no recovery anymore is this normal?
UPDATE. Seems after JM6 I have no recovery and no bootanimation(have sound). I get a black screen with a thin vertical line on the right side of the screen. Any advice would be great
The phone --!-- computer problem is solvable.
Power off your phone, and power it back on with holding the volume down button, when you see the --!-- sign release the buttons.
You are now in download mode, although you cant see the little android with the shovel. Connect it to a pc with an odin 1.7 open and you will be able to reflash it.
When I got the error picture: "phone ----- !-----PC" after messing with JM6, I just reflashed it at that screen with the full JM6 package. I dont think you can downgrade from JM6...
I just flash pit file at the phone ----- !-----PC screen then when it reboots it will boot loop. Turn it off then hold vol down and power then when the screen turns on let go of power button but still hold vol down. That will get you in download mode. You can downgrade form JM6 but you have to try 3 to 6 times before it will work. JM6 to jj4 then at&t rom is how I do it.
shep211 said:
I just flash pit file at the phone ----- !-----PC screen then when it reboots it will boot loop. Turn it off then hold vol down and power then when the screen turns on let go of power button but still hold vol down. That will get you in download mode. You can downgrade form JM6 but you have to try 3 to 6 times before it will work. JM6 to jj4 then at&t rom is how I do it.
Click to expand...
Click to collapse
You can downgrade ? Make your guide a bit better please so we can all use it.
shep211 said:
I just flash pit file at the phone ----- !-----PC screen then when it reboots it will boot loop. Turn it off then hold vol down and power then when the screen turns on let go of power button but still hold vol down. That will get you in download mode. You can downgrade form JM6 but you have to try 3 to 6 times before it will work. JM6 to jj4 then at&t rom is how I do it.
Click to expand...
Click to collapse
Interesting that you claim you can get back to JJ4 from JM6. All i get is boot.bin error so id like ro know how you did it?
Sent from my GT-P1000 using XDA App
Cmon guys, read the thread. I got the error fixed, now I have no recovery or boot animation.
Does the tab boot up at all? if it does you can try and do a factory reset from settings and see if that clears it up. You will loose all your settings and third party apps but this seems to be a requirement after flashing
Sent from my GT-P1000 using Tapatalk
Tab boots up fine, everything works, I just have no recovery or bootanimation, the sound plays for the bootani, just no picture.
MotoMudder77 said:
Cmon guys, read the thread. I got the error fixed, now I have no recovery or boot animation.
Click to expand...
Click to collapse
You need to tell us what filename you flashed and what .pit file if any you partitioned with.
It sounds like you flashed P1000OXAJM6.tar without partitioning which is probably not going to work.
Never put the phone into download mode unless you have a file ready to flash.
Flashing the file in my sig will probably fix your Tab.
rotohammer said:
You need to tell us what filename you flashed and what .pit file if any you partitioned with.
It sounds like you flashed P1000OXAJM6.tar without partitioning which is probably not going to work.
Never put the phone into download mode unless you have a file ready to flash.
Flashing the file in my sig will probably fix your Tab.
Click to expand...
Click to collapse
I followed the instructions in the OP of the JM6 thread, and flashed the files that I was linked to in the OP. I checked the box to partition. After I flashed the bell modem as I am on At&t. Then I rooted via SuperoneClickv1.5.5.
Now I have no recovery or boot animation.
I was already d/ling your file to check if that fixes anything.
Ok I tried your(rotohammer) file, and still no luck, it did save me from the root proccess tho.
adb reboot recovery, and adb devices will show the device is in recovery, but I have a backlit screen with a thin line down the right side of it. Which is the same thing I see during boot, after the at&t image.
At startup I will see this screen untill I press the lock button twice, first time shuts the screen off, and second unlocks as normal.
MotoMudder77 said:
Cmon guys, read the thread. I got the error fixed, now I have no recovery or boot animation.
Click to expand...
Click to collapse
I answered your problem yesterday and you didnt pay attention to it i guess.
This Video say it all....! http://www.youtube.com/watch?v=nmpWC73pig4
ive seen the screen you are talking about i messed up and flashed the pda file in the wrong place, what i did though is flashed the Stock ATT firmware in the pda section didn't select partition and this file seemed to re-flash everything there is a thread here in the forum, it should be on the first or second page
better yet here is the link http://files.deodexed.com/ModADroid-Galaxy-Tablet/T-Mobile/ATT_Stock.zip
Hello, i have bricked my Memo pad 7 then me176cx model and need help fixing it. i installed the adb driver and cant get into recovery for some reason, but i can get into the bootloader. but i cant figure out how to flash the update from the asus website threw the bootloader. is there anyway to unbrick it? :good:
clapper66 said:
Hello, i have bricked my Memo pad 7 then me176cx model and need help fixing it. i installed the adb driver and cant get into recovery for some reason, but i can get into the bootloader. but i cant figure out how to flash the update from the asus website threw the bootloader. is there anyway to unbrick it? :good:
Click to expand...
Click to collapse
Dont bother, I have tried for a week straight trying to unbrick mine. I did a factory reset and it destroyed my whole filesystem. :/
i just got mine so i just got a replacement from amazon
Mine was a present and I have no idea where they got it and they tossed the receipt. I'm sol. I'm broke so RMA may take a while as well! xD
Sent from my Galaxy Nexus
---------- Post added at 02:41 AM ---------- Previous post was at 02:36 AM ----------
Also for getting into recovery follow these steps. Turn off. Hold volume down and also power. When Asus pops up release power and keep hold of volume until the bootloader appears. On bootloader go down to boot recovery. When it reboots to an android guy hold volume up and down at the same time. Let go of volume up and do this r over and over until it goes to recovery. The steps are ridiculous but I know it for sure because my last week of trying to fix mine has been hell.
Sent from my Galaxy Nexus
the there is a way
applerulez1 said:
Mine was a present and I have no idea where they got it and they tossed the receipt. I'm sol. I'm broke so RMA may take a while as well! xD
Sent from my Galaxy Nexus
---------- Post added at 02:41 AM ---------- Previous post was at 02:36 AM ----------
Also for getting into recovery follow these steps. Turn off. Hold volume down and also power. When Asus pops up release power and keep hold of volume until the bootloader appears. On bootloader go down to boot recovery. When it reboots to an android guy hold volume up and down at the same time. Let go of volume up and do this r over and over until it goes to recovery. The steps are ridiculous but I know it for sure because my last week of trying to fix mine has been hell.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/help/asus-memo-7-me176cx-t2814046/post57408037#post57408037
clapper66 said:
Hello, i have bricked my Memo pad 7 then me176cx model and need help fixing it. i installed the adb driver and cant get into recovery for some reason, but i can get into the bootloader. but i cant figure out how to flash the update from the asus website threw the bootloader. is there anyway to unbrick it? :good:
Click to expand...
Click to collapse
what update are you trying to flash?
Steps to unbrick (if you can get into fastboot)
clapper66 said:
Hello, i have bricked my Memo pad 7 then me176cx model and need help fixing it. i installed the adb driver and cant get into recovery for some reason, but i can get into the bootloader. but i cant figure out how to flash the update from the asus website threw the bootloader. is there anyway to unbrick it? :good:
Click to expand...
Click to collapse
I bricked mine, but I am adventurous so found a method to recover to factory.
I'm not providing links as they are searchable here on XDA.
The steps are:
1) Get the factory image from Asus
2) Get FB Tethered Recovery Launcher
3) boot into fastboot mode
4) Hook up to computer
5) ensure the device is listed with correct drivers
6) Run ADB (from your platform tools, there is a copy in FBRL folder)
8) copy the zip file from Asus to the device (adb push /path/to/local/file /mnt/sdcard/path/to/file)
9) Run launcher from FB recovery
10) Choose T2 option, follow prompts to let it do it's thing
11) You should boot into CWM on the device
12) install from zip and point to the zip file you pushed earlier
13) Follow the prompts, and presto, restored to factory and can root/update etc.
I'd like to say thanks to the good info posted here and in other threads. I got stuck in a boot loop tonight and had no idea if I'd be able to fix it. Here's what I did (combination of this thread and others)
My method requires an micro SD card and an Internet connection
1. Confirm you can boot into fastboot:
---->Reboot into fastboot (droid boot) by powering device off (hold power button down), then holding down volume up while powering on. I released the up button once the screen went blank. It should eventually present options to reboot into droidboot, reboot, update from SD, etc.
2. Download the newest firmware from ASUS
YOU NEED THE WW version most likely (worldwide?)
3. Save this to the root of your SD card
4. rename file to MOFD_SDUPDATE.zip
5. Insert card into tablet.
6. While in droidboot/fastboot Choose the option to update from SD. It reboots and uploads the firmware. I was pleasantly surprised that I got my tablet back so easily.
Hope this helps some other poor soul.
There are other methods, but in simplicity, yours seems to win the match. Thank you very much.
How did you get cwm?
Sent from my K013 using XDA Free mobile app
JarrelStudios said:
How did you get cwm?
Sent from my K013 using XDA Free mobile app
Click to expand...
Click to collapse
I do not get the option to Update from SD while in DroidBoot...why is that? I get the other options...REBOOT, REBOOT DROIDBOOT, RECOVERY, POWER OFF.
Please help! I've already sent this back to Asus, and they just sent it right back to me.
Shaundiesel said:
I do not get the option to Update from SD while in DroidBoot...why is that? I get the other options...REBOOT, REBOOT DROIDBOOT, RECOVERY, POWER OFF.
Please help! I've already sent this back to Asus, and they just sent it right back to me.
Click to expand...
Click to collapse
Click on recovery. Inside recovery you'll get a "no command" screen. Hit the center of the volume rocker (it'll take a few tries) and you'll see the update command.
jerbear294 said:
Click on recovery. Inside recovery you'll get a "no command" screen. Hit the center of the volume rocker (it'll take a few tries) and you'll see the update command.
Click to expand...
Click to collapse
thanks Jerbear (Love the name, Deadhead!), I did this which brings up regular Android recovery, but no option to update except through ADB.
Shaundiesel said:
thanks Jerbear (Love the name, Deadhead!), I did this which brings up regular Android recovery, but no option to update except through ADB.
Click to expand...
Click to collapse
Try this, then.
In the main thread somebody linked a temporary cwm session. Try booting into it and installing the update from there (Nandroid while you're at it )
Why would I not even have the option though??
Shaundiesel said:
Why would I not even have the option though??
Click to expand...
Click to collapse
I'm not exactly sure.
I need some help. I have average experience with ADB and cannot get ADB to recognize my device. Debugging on of course, and I dowloaded the zip for the drivers. I don't really know where to go from here. Any help will be greatly appreciated! I need to get this thing back up and running!!
gcballard said:
I'd like to say thanks to the good info posted here and in other threads. I got stuck in a boot loop tonight and had no idea if I'd be able to fix it. Here's what I did (combination of this thread and others)
My method requires an micro SD card and an Internet connection
1. Confirm you can boot into fastboot:
---->Reboot into fastboot (droid boot) by powering device off (hold power button down), then holding down volume up while powering on. I released the up button once the screen went blank. It should eventually present options to reboot into droidboot, reboot, update from SD, etc.
2. Download the newest firmware from ASUS
YOU NEED THE WW version most likely (worldwide?)
3. Save this to the root of your SD card
4. rename file to MOFD_SDUPDATE.zip
5. Insert card into tablet.
6. While in droidboot/fastboot Choose the option to update from SD. It reboots and uploads the firmware. I was pleasantly surprised that I got my tablet back so easily.
Hope this helps some other poor soul.
Click to expand...
Click to collapse
I'm at the Android System Recovery, however, there's no option to apply update from SD...only apply update from ADB...
jhenehj said:
I'm at the Android System Recovery, however, there's no option to apply update from SD...only apply update from ADB...
Click to expand...
Click to collapse
In this case use the Intel Atom temporary ClockWorkMod to flash it.
jerbear294 said:
In this case use the Intel Atom temporary ClockWorkMod to flash it.
Click to expand...
Click to collapse
Thanks for your reply...I'm not really sure what you're referring to, but is this about ADB sideloading? I already tried but this comes up...
Now I don't know what to do...so I badly need anyone's help here...thanks in advance!
Hi,
I'm looking to buy a TF701T that the seller has listed as faulty.
He has told me the following:
Bootloader is locked, does go into recovery but never completes it and fails. Something very wrong with it.
Thanks
Is the tablet fixable or not even worth the trouble?
Thanks
Rackers said:
Hi,
I'm looking to buy a TF701T that the seller has listed as faulty.
He has told me the following:
Bootloader is locked, does go into recovery but never completes it and fails. Something very wrong with it.
Thanks
Is the tablet fixable or not even worth the trouble?
Thanks
Click to expand...
Click to collapse
I would be inclined to say no, given that the bootloader is locked and the stock recovery fails. You could however purchase it, and RMA. Asus would more then likely do a board swap and charge you an additional 200+ dollars. If this still interests you, then by all means. After all, dude could be selling it for $20 bucks for all I know.
Thanks for the reply.
I will not be buying in that case!
Well, it depends what the seller considers a fail....
So many people do not know how to use the stock recovery to reflash the stock rom. They get the Andy on his back and think it's the recovery that failed when it actually signifies a perfectly fine recovery not finding an adequate update file in the correct location with the correct file name........
You would need a lot more information about what is wrong with the tablet, what the seller did, what EXACTLY he did to fix it etc.
"Something is seriously wrong" doesn't say anything. Could be as easy as a corrupted data partition.... Who knows?
berndblb said:
Well, it depends what the seller considers a fail....
So many people do not know how to use the stock recovery to reflash the stock rom. They get the Andy on his back and think it's the recovery that failed when it actually signifies a perfectly fine recovery not finding an adequate update file in the correct location with the correct file name........
You would need a lot more information about what is wrong with the tablet, what the seller did, what EXACTLY he did to fix it etc.
"Something is seriously wrong" doesn't say anything. Could be as easy as a corrupted data partition.... Who knows?
Click to expand...
Click to collapse
You can try to put a stockrom on a MicroSD, renamed to T4_SDUPDATE.zip.
Just like the instruction on the asus site.
Maybe this works.
1.Download “WW_10_26_1_18_SDupdate” from ASUS support site.
2.Unzip “WW_10_26_1_18_SDupdate” and put “T4_SDUPDATE.zip” in an empty MicroSD card.(must larger than 2 GB)
3.Turn off your TF701T
4.Insert the MicroSD card with T4_SDUPDATE file.
5.Long press “Volume down” button and “Power” button at the same time until below screen shows up. There is a line reads ”Press key in 5 sec to enter RCK”
6.Soon, press “Volume Up” button and you will see below screen.
7.After waiting a few minutes, you will see an ASUS logo with a status bar. It means update process starts and after about 5 minutes.
Click to expand...
Click to collapse
latest firmware changes to recovery menu
Only use the correct firmware version for your tablet from the ASUS website as NOT stated in number 1 above. The instructions for number 5 & 6 above are not correct for the 11. 4. 1. 29 firmware version. number 5 should be hold down volume down and power key boot into boot menu then ONLY press down volume key to select RCK then up volume to select. No matter what you do!!!!!!!!! Do not do a wipe data from this screen!!!!! Only wipe data from within your newly installed custom recovery! 6 is void.
Also, I think if you just boot/reboot your device with the zip file on the root of the SD card, it should detect the update and then install without going to the boot menu first. Just delete the zip file before you reboot so it will not detect it. If this helped you out, please press the thanks button!
NOTICE: ZV6 or higher Users - Received reports that attempting to revert to ZV5 may brick your device.
Recommend holding off for now, will try to get ZV6. (Also attempting to confirm.)
OK, I know folks have been in need and an anonymous source has been kind enough to share.
Here is the TOT for LS991 ZV5. I'm passing it on to @autoprime who will be adding more below on how to use it.
Please make sure to give Team Codefire a huge thanks for what they do with LG devices.
It's one thing to get restore files, it's a completely different (and much more challenging) one to do things like root it.
Cheers!
ZV5 TOT is out!
Don't use this TOT if you are on ZV6 or higher.. you will brick.
Thanks to an anonymous donor and to @garwynn we now have the ZV5 TOT. No more soft bricks! I have also broken down the TOT and uploaded the individual partitions.
Changelog:
Fix for Google Factory Reset Protection issue that does not allow user to bypass WiFi after performing a ##RTN on the device. User can now bypass WiFi
LG has also implemented a touchscreen enhancement into the software
ZV5 also updates the bootloader version from v0 to v1.
--TOT can be downloaded *HERE*
For those familiar with LG's.. this is flashed the same way as previous models... LG OG, G2, G3 etc etc.
1. Download LG Flash Tool. Swap the included mega.dll (click here to see video)
2. Download the LGFLASH_LG_G4_CODEFIRE.dll
3. Download the ZV5 TOT and unzip it.
4. If LG drivers are not already installed, download and install them.
5. Place phone into download mode
6. Set phones serial COM port to COM41 in Windows Device Manager. Unplug USB cable then plug it back in.
7. Run LG Flash Tool.
8. Select LGFLASH_LG_G4_CODEFIRE.dll for DLL, LS991ZV5_05.tot for TOT and check off "BOARD DL"
9. Hit OK to continue. Now hit the yellow start button. LG Flash Tool should now perform a CRC check on the TOT.
10. Unplug the USB cable again then plug it back in... wait 5-20 seconds and hopefully the flash should now start.
When it finishes it'll boot into miniOS. Hold the power button then press the "Normal Boot" option on the screen.
The above steps are "to the point" and there's not much hand holding so new LG flashers may be a bit confused. Feel free to ask questions in this thread and hopefully other users will chime in and assist with specific questions. But for extra help here is a how-to video going over the process. Only differences is phone model and TOT/DLL files used... rest can be applied.
Also here is a G4 Return to Stock thread... the lower section of the OP has step by step directions and screenshots for the entire LG Flash install process and TOT flash.
--Individual ZV5 partitions to flash manually can be downloaded *HERE*
Stock system.img is not included in that list due to redundancy. The stock rooted ZV5 system.img can be found in the Low Effort Root thread.
--ZV4-to-ZV5 OTA update.zip *NOTYETAVAILABLE*
This was links somewhere previously... I'll have to look for it again.
You must be on ZV4 and have a stock recovery and stock system partition for this to work.
Directions:
1. Rename downloaded .zip into update.zip
2. Remove USB cable from phone.
3. Power phone off.
4. Press and hold volume down + power until you boot into stock recovery.
5. Select "update with adb"
Code:
adb sideload update.zip
Alternate Directions to skip using ADB (needs microSD card):
1. Format microSD card as EXT4.
2. Rename downloaded .zip to update.zip
3. Move update.zip onto external SD card. EZ way would be to stick SD card in phone then connect phone to PC and use MTP.
4. Power off and boot into stock recovery (vol down + power)
5. Select the Update from SDCARD option.
Click to expand...
Click to collapse
thank you so much, whoever leaked this!
and of course OP and codefire..
:highfive:
You guys are awesome!
Edit: Getting a 403 Forbidden on the LGFLASH_LG_G4_CODEFIRE.dll
All fixed! Thanks autoprime!
Went through everything, after rebooting at the end of th LG Flash Tool, phone rebooted to Factory Reset Status 2, blue screen.
UPDATE 1: Now the LG Flash Tool is not even starting to flash. The phone is back in DL mode and eveything is as it should be, but the flash tool is not doing anything
UPDATE 2: Switched USB ports, oddly that made LG Flash Tool Work. USED BOARD DL AND IT WORKED.
Instructions for Linux?
Which TOT file should be used? The one posted by garwynn (1.59GB) or Autoprimes? (1.98GB) TOT? whats the differences?
SGSIIIJB said:
Which TOT file should be used? The one posted by garwynn (1.59GB) or Autoprimes? (1.98GB) TOT? whats the differences?
Click to expand...
Click to collapse
I'm fairly certain they're the same, they're just using different compression methods (.7z in garwynn's post, .zip in autoprime's). .7z is a better method of compression, thus the smaller file size. The .tot files should be the same size when extracted.
Any way of using this TOT method after flashing the US991 firmware(I mistakenly flashed it thinking it's the KDZ for Sprint)? I keep getting "DoDownload Error!!!"
kyle1867 said:
Instructions for Linux?
Click to expand...
Click to collapse
run windows in a virtual machine. or find a windows computer. or reverse LG's download mode protocol, extract the tot and find a way to flash it over a serial connection in linux.
BeardKing said:
I'm fairly certain they're the same, they're just using different compression methods (.7z in garwynn's post, .zip in autoprime's). .7z is a better method of compression, thus the smaller file size. The .tot files should be the same size when extracted.
Click to expand...
Click to collapse
yup
ijball said:
Any way of using this TOT method after flashing the US991 firmware(I mistakenly flashed it thinking it's the KDZ for Sprint)? I keep getting "DoDownload Error!!!"
Click to expand...
Click to collapse
Try flashing the rooted Sprint system.img thru download mode.. just as if you were rooting. putting sprint system.img on the phone might get around the error. actually... as I'm typing this.. you might be able to just edit the build.prop in the us991 rom. if you use a build.prop editor make sureyou also have busybox installed or many buildprop apps wont actually work. and you'll need root to edit build.prop of course.
if no root.. might as well just flash the rooted sprint system.img tho. see how that goes.
Thanks for this! I've been waiting almost a month! So happy it's finally out!!
Quick question; my phone is rooted and has been running xposed for weeks no problem. Today, the phone randomly rebooted and has since been in a boot loop that sometimes ends with "secure boot error error 1006" in top left corner of the android boot screen a second then restarts. I believe can still enter download mode to the point where it asks to "update firmware, do not unplug..."but sometimes I get the secure boot error here as well.
I assume I should attempt to fix this with the tot? Anyone else have any suggestions? I don't want to mess the phone up further if there are easier ways to fix this.
Jessooca said:
Nope. Use the tot and restore it then root it again.
If you've never used a tot or lg tools to restore am LG device it's very easy and won't take long at all.
Click to expand...
Click to collapse
After I completed the tot I attempted to reboot. I now have an security error 1007 error code in the top left and also a security error; authentication problem #9.
Edit: I pulled the battery and now it seems Android is starting and doesn't show the error code but freezes shortly after boot before it restarts itself?
I assume I have to reroot it to get around this error code as well but I am unable to enable mtp or usb debugging before it restarts
Jessooca said:
Nope. Use the tot and restore it then root it again.
If you've never used a tot or lg tools to restore am LG device it's very easy and won't take long at all.
Click to expand...
Click to collapse
Jessooca said:
At the end of flashing the TOT with the Lg Tool you may have been on the screen where you have to "press normal + reboot* hopefully that's the option you pressed. IF you haven't a clue what I am talking about, then you for some reason got a different screen.
Once you use the TOT file and restore using the LG Tool (and the tutorial mentioned) you should be fully back to stock like you just got the phone, without any issues. Did you make sure you chose BOARD at the bottom left of the Manual selection of the dll & added the tot?
Click to expand...
Click to collapse
I responded in PM but yes, I used BOARD and I was able to get to the MiniOS screen where you hold power and select normal + reboot. It's after rebooting where it continues to a) boot loop till a blank screen appears and only a battery pull can trigger another boot B) Gets to android but then freezes before I can even activate C) Shows secure boot error code 1007 or Security error; authetication code #9 and prevents the boot.
The upgrade method triggers the same blue screen as others have mentioned. I really don't know what went wrong with the phone in the first place, I had been rooted and using xposed without any new apps or updates for the last couple of weeks. The phone literally rebooted while it was charging and hasn't been right since even after using the tot.
I may try my other computer for just to test -> Just tried and same thing happened; either boot loops, security error, or makes it past the Sprint Spark screen and android is starting screen before freezing.
Has anyone successfully restored TOT? Seems like a lot of folks are having issues.
Jessooca said:
I have. I tested the file just to make sure it worked. What issue are YOU having?
It's honestly a fairly simple procedure. You can watch this video (I believe it's also mentioned in the beginning of this thread)
https://www.youtube.com/watch?v=1WgXuxDbmbc Pretty much all you need is from 2:45 and on in the video.
Just be sure to select BOARD at the bottom of the screen, when selecting the dll and adding the tot file. At times people have forgot to change it from upgrade to Board.
-After it's finished
Pull the battery, hold Volume UP and Power, let go of Power on the LG Logo screen as mentioned for one second, Press power again while continuing to hold Volume Up and you'll get into recovery, do a wipe and reboot. It should fix any other issues.
Click to expand...
Click to collapse
I'm not having any issues. Just looking ahead if this is a safe recovery path.
mswlogo said:
Has anyone successfully restored TOT? Seems like a lot of folks are having issues.
Click to expand...
Click to collapse
I have. It worked great.
Worked, thanks.
Like a dumb ass i unplugged the phone right at the end blue screen number 2 and it said failed.. am i able to repeat the steps and get it going again or did i just ruin the phone
This is the screen thats shown
This morning I saw that I can update to the new Android 10 version on my Galaxy S10.
I was happy and of course updated directly.
Everything worked fine, the update was downloaded, installed and the phone rebooted.
And from there it hung in a boot loop.
I had already unlocked the bootloader 2 months ago, but only to flash the original firmware again because of an unsuccessful attempt to install TWRP.
Now the Galaxy S10 starts up, shows the information that the boot loader has been unlocked and then the boot logo and vibrates.
Then it goes straight off and starts again.
I cannot use the key combinations to get into the recovery or in the download mode.
How can I solve this problem ?
(Sorry for my bad englisch i come from germany)
You can try following:
Plug your phone in the PC with the USB cable. Then press/hold Bixby + Volume Down and hopefully it will boot to download-mode.
Otherwise try (still plugged in) force shutdown/restart by pressing/ holding Volume Down + Power - as soon as the screen turns off shift to pressing/ holding Bixby + Volume Down for download-mode. Try it at few times as its all about timing.
If still no luck, unplug your phone and let the battery run out. Then press/hold Bixby + Volume Down and plug in to get to download-mode. This may take some time as the phone needs to recharge a little before it reacts.
Once in download-mode flash your software before the update via Odin - I would use Home_CSC first trying to save your data.
Got exactly the same problem today. Don't know which one I flashed in november though
So how to keep (maybe) the data? flash only HOME_CSC?
nikolaus2007 said:
Got exactly the same problem today. Don't know which one I flashed in november though
So how to keep (maybe) the data? flash only HOME_CSC?
Click to expand...
Click to collapse
Yes to using Home_CSC but to be safe I would flash all 4 files (AP - BL - CP - HomeCSC) as some people have reported their storage gets corrupted/ shows wrong capacity.
Use either Samsung 10 (BSKO) or latest Pie (ASJG). Both should be ok as you are flashing the bootloader when using all 4 files.
Norup58 said:
You can try following:
Plug your phone in the PC with the USB cable. Then press/hold Bixby + Volume Down and hopefully it will boot to download-mode.
Otherwise try (still plugged in) force shutdown/restart by pressing/ holding Volume Down + Power - as soon as the screen turns off shift to pressing/ holding Bixby + Volume Down for download-mode. Try it at few times as its all about timing.
If still no luck, unplug your phone and let the battery run out. Then press/hold Bixby + Volume Down and plug in to get to download-mode. This may take some time as the phone needs to recharge a little before it reacts.
Once in download-mode flash your software before the update via Odin - I would use Home_CSC first trying to save your data.
Click to expand...
Click to collapse
Thanks!
I got into the download mode.
I used SamFirm to download the firmware but it was Android 10
Right now i am downloading Andoid Pie from updato.com...
No premium, i am just a free member, so it shows me "20 Hours left"
Where can i download the latest SM-G973F Germany (DBT) Android Pie Firmware for free and without that high speed restriction ?
I think i have to put the home_csc file into the CSC field in odin ?
Didn't work for me, neither ASJG (Pie) nor BSKO (Q).
Had to wipe data, beause system nerver booted again.
Lost all my data. Congrats Samsung to this very best update mechanism. Nerver had on any Nexus nor OnePlus.
Maybe you have more luck.
download mode its not opening idk what i need to do im gonna lose my mind ( sorry for my bad english )
c_j_k said:
Thanks!
I think i have to put the home_csc file into the CSC field in odin ?
Click to expand...
Click to collapse
Yes!
maxmelax said:
download mode its not opening idk what i need to do im gonna lose my mind ( sorry for my bad english )
Click to expand...
Click to collapse
Have you tried all 3 of my suggestions listed above?
Norup58 said:
Yes to using Home_CSC but to be safe I would flash all 4 files (AP - BL - CP - HomeCSC) as some people have reported their storage gets corrupted/ shows wrong capacity.
Use either Samsung 10 (BSKO) or latest Pie (ASJG). Both should be ok as you are flashing the bootloader when using all 4 files.
Click to expand...
Click to collapse
I flashed G973FXXS3ASJG to my Galaxy S10.
First i tried only homeCSC but it was still brick.
Then i flashed only AP, it worked.
But after I set up my smartphone again, I saw that I only have 32 GB of storage even though my Galaxy S10 is the 128 GB version.
Then, as you said, I flashed all four files (AP - BL - CP - HomeCSC).
It still shows me that I only have 32 GB of storage
c_j_k said:
I flashed G973FXXS3ASJG to my Galaxy S10.
First i tried only homeCSC but it was still brick.
Then i flashed only AP, it worked.
But after I set up my smartphone again, I saw that I only have 32 GB of storage even though my Galaxy S10 is the 128 GB version.
Then, as you said, I flashed all four files (AP - BL - CP - HomeCSC).
It still shows me that I only have 32 GB of storage
Click to expand...
Click to collapse
When I first read your post I thought:
Seriously…. Seriously…..
I mean, why the heck would you only flash one file (you were actually warned against this) when it is just as easy to fill-out all 4 slots in Odin? People amaze me!
Okay its Xmas, so back to helping:
‘What you have experienced is a side-effect of using Odin to flash an AP file to your device with the CSC slots left empty. Never flash a full AP file on this range of devices without also filling at least the HOME_CSC slot. It is safe, however, to flash only a recovery image in the AP slot.
To attempt to repair the damage, you need to boot to TWRP, select Advanced Wipe, tick Data, select Repair or Change File System followed by Resize File System. Your /data will return to its former size, but you will probably find you have lost some data.’
Above is quoted from #ianmacd
So, if your phone is on stock Pie (minimum ASIG), with OEM unlocked, try this to get TWRP installed in order to use above rescue.
Go here and download Multidisabler: https://forum.xda-developers.com/ga...ynos/g97xf-multi-disabler-encryption-t3919714
Go here and download TWRP Magisk Patched: https://forum.xda-developers.com/ga...ynos/recovery-twrp-galaxy-s10-magisk-t3919248
Now read post #2 in the TWRP thread for installation guidance…. When you get to no.10 flash the Multidisabler you downloaded instead and then skip to no.12
After no.12 reboot, boot back into TWRP and try the Data fix above.
If all goes well you will have full storage capacity again, TWRP installed and rooted with Magisk.
Norup58 said:
You can try following:
Plug your phone in the PC with the USB cable. Then press/hold Bixby + Volume Down and hopefully it will boot to download-mode.
Otherwise try (still plugged in) force shutdown/restart by pressing/ holding Volume Down + Power - as soon as the screen turns off shift to pressing/ holding Bixby + Volume Down for download-mode. Try it at few times as its all about timing.
If still no luck, unplug your phone and let the battery run out. Then press/hold Bixby + Volume Down and plug in to get to download-mode. This may take some time as the phone needs to recharge a little before it reacts.
Once in download-mode flash your software before the update via Odin - I would use Home_CSC first trying to save your data.
Click to expand...
Click to collapse
i am having the same problem but i cant enter download mode and my pc doesnt recognise the phone to use odin
is there any possible solution to that ? thank you in advance
th3maker said:
i am having the same problem but i cant enter download mode and my pc doesnt recognise the phone to use odin
is there any possible solution to that ? thank you in advance
Click to expand...
Click to collapse
Yeah, I can see you have started a thread with your problem.
If the first two of my suggestions doesnt work for you then you have to let the phone bootloop until the battery dies/ runs dry and then try my third suggestion.
Norup58 said:
When I first read your post I thought:
Seriously…. Seriously…..
I mean, why the heck would you only flash one file (you were actually warned against this) when it is just as easy to fill-out all 4 slots in Odin? People amaze me!
Okay its Xmas, so back to helping:
‘What you have experienced is a side-effect of using Odin to flash an AP file to your device with the CSC slots left empty. Never flash a full AP file on this range of devices without also filling at least the HOME_CSC slot. It is safe, however, to flash only a recovery image in the AP slot.
To attempt to repair the damage, you need to boot to TWRP, select Advanced Wipe, tick Data, select Repair or Change File System followed by Resize File System. Your /data will return to its former size, but you will probably find you have lost some data.’
Above is quoted from #ianmacd
So, if your phone is on stock Pie (minimum ASIG), with OEM unlocked, try this to get TWRP installed in order to use above rescue.
Go here and download Multidisabler: https://forum.xda-developers.com/ga...ynos/g97xf-multi-disabler-encryption-t3919714
Go here and download TWRP Magisk Patched: https://forum.xda-developers.com/ga...ynos/recovery-twrp-galaxy-s10-magisk-t3919248
Now read post #2 in the TWRP thread for installation guidance…. When you get to no.10 flash the Multidisabler you downloaded instead and then skip to no.12
After no.12 reboot, boot back into TWRP and try the Data fix above.
If all goes well you will have full storage capacity again, TWRP installed and rooted with Magisk.
Click to expand...
Click to collapse
Hey Bro, I bricked my phone as well in the morning while updating to android 10 but I just had my bootlocker unlocked but no root on it. Could you tell me if there is any possibility to backup the stuff on my phone? Right not Im waiting for my battery to drain to 0% that I can get into download mode and try something out maybe you have a tip for me
Can someone send me a prepatched magisk ap file for HK 9730 Android 10. I don't know what I did. I just pre patched it myself and flashed with odin just like ANY other update but this time, it gets stuck at Samsung logo. I waited a good while too. Maybe I didn't have the right magisk version which is why I'm asking if someone has a pre patched that works, idk but I don't want to lose my data.
BeastyReedhawk said:
Hey Bro, I bricked my phone as well in the morning while updating to android 10 but I just had my bootlocker unlocked but no root on it. Could you tell me if there is any possibility to backup the stuff on my phone? Right not Im waiting for my battery to drain to 0% that I can get into download mode and try something out maybe you have a tip for me
Click to expand...
Click to collapse
My suggestion is to download the complete stock firmware- be it Pie or 10 (Q) - and then when flashing all 4 files via Odin use the Home_CSC file to try to retain your data.
I use FRIJA to download firmwares as the d/l speed is very good.
Bear in mind, if you at some point intend to root and/or install TWRP your phone will be wiped in the process so backup your stuff before going down that road.
Hi, i have the same problem, i can't access to download mode, i have access to twrp recovery but i can't do anything, if i touch the recovery screen, the phone reboot, have you any suggestion please, to recover my phone?
OK, i find a way accidently!
thks
I am also experiencing this issue that the OP is having with their S10. I also have an S10. There was a software update for my phone and now I wake up to my phone boot looping itself to death.
For someone that lives in the United States, which firmware should I use to recover my phone? I ask because there is like 20+ countries to choose from for the exynos G973F model
Norup58 You saved my life!!!! LOVE YOU. i got into download mode THANKS MAN
LOVE UU
My have a similar problem buh worse... Was updating manually then got the error message.
Tried to put it back into download mode the went into black screen and now doesn't respond to anything. Seems dead
RemixDeluxe said:
I am also experiencing this issue that the OP is having with their S10. I also have an S10. There was a software update for my phone and now I wake up to my phone boot looping itself to death.
For someone that lives in the United States, which firmware should I use to recover my phone? I ask because there is like 20+ countries to choose from for the exynos G973F model
Click to expand...
Click to collapse
Hello,
I have a Samsung Galaxy Note 9 (SM-N9600) that will not boot. So far I have flashed 2 official firmwares with Odin, and on the first boot attempt after flashing, it will show a percentage bar that counts up to around 5 or so percent before skipping to 100 then looping again. It only does the percentage thing on the first boot after flashing. When I try a factory reset from the recovery I get a no pdp scenario error also. I have tried all that I can think of and even took it to a Samsung Service centre but no solution. I would really appreciate any help I can get.