First of all, my phone isn't rooted and knox is not triggered.
Today I rebooted my mobile phone because the app adhell wasn't working properly and after that my phone got stuck in the boot loop (samsung letters in the screen).
I've tried wiping the cache and flashing the firmware again with ODIN, didn't work. I can't enter to the safe mode and erase adhell neither. Samsung smart switch doesn't recognise my device so I can't use it.
I run out of ideas, what else can I do to get out of the loop without erasing all the data in the phone?
Thanks in advance.
Same thing here, after update (official from samsung), Mine is stuck in a bootloop too.
Anyone, please help?
---------- Post added at 09:31 PM ---------- Previous post was at 09:29 PM ----------
Same thing here...
If Adhell is the cause, then fixing the bootloop is just as simple as removing it. As for how you go about fixing it, you have a few options.
1) Returning phone to store bought from if still under warranty and getting them to help. They'd most probably wipe it or replace it.
2) Full reset wiping data you don't have backed up
3) Custom recovery that lets you delete the files manually, but will probably trip KNOX
You could always try booting into recovery and see if your PC picks up your phone, then backing up what you can from there. But again, that might not be an option because stock recovery. TWRP lets you access files from your PC, but again trips KNOX.
ProdigyThirteen said:
If Adhell is the cause, then fixing the bootloop is just as simple as removing it. As for how you go about fixing it, you have a few options.
1) Returning phone to store bought from if still under warranty and getting them to help. They'd most probably wipe it or replace it.
2) Full reset wiping data you don't have backed up
3) Custom recovery that lets you delete the files manually, but will probably trip KNOX
You could always try booting into recovery and see if your PC picks up your phone, then backing up what you can from there. But again, that might not be an option because stock recovery. TWRP lets you access files from your PC, but again trips KNOX.
Click to expand...
Click to collapse
The phone is not under warranty and I don't have any data backup. How can I install the TWRP recovery in the situation I am now?
Now it doesn't enter to the recovery mode, and I didn't do anything new.
polema said:
The phone is not under warranty and I don't have any data backup. How can I install the TWRP recovery in the situation I am now?
Click to expand...
Click to collapse
First off, download SkipSoft Toolkit, go through the options it gives you until you're on the model of your phone and Android version. Then if you haven't already installed the drivers, do it. SkipSoft has the ones you need there. SkipSoft also downloads all the files you need to root, to flash TWRP, has a stock recovery if you mess up or want to return to stock for whatever reason after.
Then select the option to flash a custom recovery and root. You don't have to root, it won't do it automatically, that's something you have to flash yourself inside of TWRP if you want to. If you do want to root, look into Magisk. It lets you still use apps that normally don't work on rooted devices (it doesn't trip SafetyNet).
As for flashing the recovery, there's a wall of text that SkipSoft gives you to read which I'd recommend going over to make sure you know what you're doing. If you screw up, 99% of the time there is a fix for it so don't panic.
If all goes well, you should see TWRP loading up when you boot into recovery. Then when you connect your phone to your PC, it should appear as normal and you can copy any files you want to back up. TWRP has a Wipe option that will completely clear all installed apps, all app data, any setting changes and set your phone back to stock without deleting the files you have on it to save you from having to copy them all back again after. I'd also recommend making a complete backup of everything through the option in TWRP at that point for future security, and just in case you want to root.
If you have any more questions, just ask. I don't have an answer for everything, but I'll try my best.
ProdigyThirteen said:
First off, download SkipSoft Toolkit, go through the options it gives you until you're on the model of your phone and Android version. Then if you haven't already installed the drivers, do it. SkipSoft has the ones you need there. SkipSoft also downloads all the files you need to root, to flash TWRP, has a stock recovery if you mess up or want to return to stock for whatever reason after.
Then select the option to flash a custom recovery and root. You don't have to root, it won't do it automatically, that's something you have to flash yourself inside of TWRP if you want to. If you do want to root, look into Magisk. It lets you still use apps that normally don't work on rooted devices (it doesn't trip SafetyNet).
As for flashing the recovery, there's a wall of text that SkipSoft gives you to read which I'd recommend going over to make sure you know what you're doing. If you screw up, 99% of the time there is a fix for it so don't panic.
If all goes well, you should see TWRP loading up when you boot into recovery. Then when you connect your phone to your PC, it should appear as normal and you can copy any files you want to back up. TWRP has a Wipe option that will completely clear all installed apps, all app data, any setting changes and set your phone back to stock without deleting the files you have on it to save you from having to copy them all back again after. I'd also recommend making a complete backup of everything through the option in TWRP at that point for future security, and just in case you want to root.
If you have any more questions, just ask. I don't have an answer for everything, but I'll try my best.
Click to expand...
Click to collapse
Thanks for all the help.
I have android 7 nougat in my phone and it's not among the options, what should I do?
{
"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"
}
polema said:
Thanks for all the help.
I have android 7 nougat in my phone and it's not among the options, what should I do?
Click to expand...
Click to collapse
Update SkipSoft, recent version is 1.5.6, 7.0 is in that version.
If you can't update for whatever reasons, you can manually download the TWRP files from here and drop those into C:\Unified_Android_Toolkit\recovery\GalaxyS6Edge, then select any version of Android and follow what it says. Just don't flash the root it provides, use Magisk as I said before.
polema said:
Thanks for all the help.
I have android 7 nougat in my phone and it's not among the options, what should I do?
Click to expand...
Click to collapse
You still having trouble with this?
Finally I managed to repair the phone with smart switch, I've lost my photos/videos but the rest was saved in samsung cloud.
polema said:
Finally I managed to repair the phone with smart switch, I've lost my photos/videos but the rest was saved in samsung cloud.
Click to expand...
Click to collapse
Hi, I am having the same problem as you since yesterday afternoon where it's stuck in a boot loop, my notification light was blinking so when I went to check on it the phone was turned off but the light was still blinking, the light only stopped after the battery drained completely. when I tried to turn the phone on after charging it, it's still stuck in a boot loop, only thing I can do is hold the volume down, power, and home button down to enter the "downloading do not turn off target screen." I downloaded smart switch on my laptop last night to see if I can fix my phone through that but it says unsupported device, and when I try emergency software recovery and initialization option when I enter model name and S/N number and click OK the program closes and nothing happens. polema what did you do to fix your device?
abhi821 said:
Hi, I am having the same problem as you since yesterday afternoon where it's stuck in a boot loop, my notification light was blinking so when I went to check on it the phone was turned off but the light was still blinking, the light only stopped after the battery drained completely. when I tried to turn the phone on after charging it, it's still stuck in a boot loop, only thing I can do is hold the volume down, power, and home button down to enter the "downloading do not turn off target screen." I downloaded smart switch on my laptop last night to see if I can fix my phone through that but it says unsupported device, and when I try emergency software recovery and initialization option when I enter model name and S/N number and click OK the program closes and nothing happens. polema what did you do to fix your device?
Click to expand...
Click to collapse
Flash stock firmware through Odin.
Or try boot your phone to recovery mode (up home and Bixby. If it boots to recovery plug to pc and see if smart switch recognises it.
callumbr1 said:
Flash stock firmware through Odin.
Or try boot your phone to recovery mode (up home and Bixby. If it boots to recovery plug to pc and see if smart switch recognises it.
Click to expand...
Click to collapse
I forgot to mention my phone is a samsung galaxy s6 edge, also I tired the recovery mode but it still does the boot loop. Are there clear instructions to flash stock firmware through Odin?
abhi821 said:
I forgot to mention my phone is a samsung galaxy s6 edge, also I tired the recovery mode but it still does the boot loop. Are there clear instructions to flash stock firmware through Odin?
Click to expand...
Click to collapse
What android version is it and what region and model? Tell me these and I'll post the firmware with the steps to flash.
callumbr1 said:
What android version is it and what region and model? Tell me these and I'll post the firmware with the steps to flash.
Click to expand...
Click to collapse
I got my phone through AT&T in USA model is SM-G925AUCU1AOCE and I not sure what android version I have.
Related
Hi all,
On a regular P500 with stock Android 2.2, build FRF91, software version LG-P500-V10b, the yellow screen Emergency Mode!! appeared after a regular restart and would go any further. I couldn't connect this situation to any of the apps that were installed.
Also, on regular usage, the Emergency mode scrren may appear out of nowhere and the phone is off the network.
This phone is used by my wife, she's not a hacker, she just want's to sleep the baby with melodies from this phone.
If I let the battery out for more that 15min it will boot back the normal way, but it isn't seen by Windows, it senses the device when plugged in but it says "device unplugged"
I followed several guides in the forum, and I saw there are two ways of writing something to the device:
1. "downgrade" the phone to the original firmware, like here Guide for newbies - LG OPTIMUS P500
2. write a new ROM, like here [ROM] (OFFICIAL) [email protected]_2.3.3_v2- Power Menu +franco-kernel+New Boot+ How to Guide
My obvious problem is the phone not being seen by Windows. I started it on purpose in Emergency Mode with Vol up+back key+Power and it appeared in device manager as LGE Mobile USB modem #2.
First I tried to write a new ROM, like at point 2. above, with LGMDP THUNDER v1.5, but I run into this error, after pressing the Start (write ROM button): Error! Partition Table. Here is a screen shot.
The I tried the other option, to "downgrade" the phone to the original firmware, with KDZ Updater.
I found V10E_00.kdz, although I think I should use V10B but I didn't found it. Search on this forum is a pain because it works one time in a hundred (it says something about maintenance).
KDZUpdater did its job successfully but the phone rebooted and halted on "Android" screen, that's it. Then I removed the battery, powered it back up and, surprise, my friend the Emergency Mode!! is back again.
So this phone doesn't seem to be bricked, nor isn't stuck forever in emergency mode, but also is not reliable anymore because of the emergency mode appearing randomly.
Please, slap me in the face with a link saying "dude, search worked for me an here's the fix".
What I can tell you for sure is that I didn't saw the partition table error before on this forum.
hmm... try again with kdz with correct version and do all things again but wait until all works done. don't be so fast
and come here again and tell what happened
If it is stuck on android logo after flashing kdZ, take out battery and press voldown+home+power button to hard reset
Sent from my LG-P500
Indeed it was stuck on the android logo after flashing with KDZ. Hard reset worked!
Thank you! Thank you! Thank you!
After this I had Android 2.2.2 running, then I started LGMobile software updater Agent from LG PC Suite and it updated the OS to 2.3.3. After finishing, the phone rebooted to Emergency mode again, but I did another hard reset and now it works perfectly, it reboots properly.
I guess the root problem was a corrupt file system.
A little offtopic since we are at it. for you guys what proved to be the best rom/kernel combination for best battery life?
Thanks again!
Later edit:
New updates: the phone doesn't behave normally as it began above. Later after the update, I tried to connect the phone to Windows PC and surprise, it didn't saw it as it was supposed to, the problem encountered at the beginning of this post reappeared:
Device driver software was not successfully installed
{
"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"
}
Although I have the correct drivers, because when I connect a friend's LG P500 it is seen properly.
After this, I rebooted the device and, surprise again, it booted to Emergency Mode. I unplugged the battery and let it for a while, then it booted normally but still it isn't seen by Windows.
Is this a software (ROM/Kernel) issue or a hardware issue?
I mention the my friend's LG P500 has the same factory provided update with Android 2.3.3, build GRI40, soft version V20g, kernel 2.6.35.10-perf [email protected] #1 and it doesn't have any problems.
Update: I can not even charge the device after I power it down. When I insert the charger, the emergency screen appears right away and it stays that way. I don't know even if the device is charging.
The workaround is to unplug the battery and leave it for 15-30 min or more and then it starts properly, but the problem in the post above is still present.
lmihaila said:
Update: I can not even charge the device after I power it down. When I insert the charger, the emergency screen appears right away and it stays that way. I don't know even if the device is charging.
The workaround is to unplug the battery and leave it for 15-30 min or more and then it starts properly, but the problem in the post above is still present.
Click to expand...
Click to collapse
Just try using froyo, dont upgrade to gingerbread, and see the problem still persist.
aspee said:
hmm... try again with kdz with correct version and do all things again but wait until all works done. don't be so fast
and come here again and tell what happened
Click to expand...
Click to collapse
What is supposed to be the correct version? I tried these rom's: V10A_00.kdz, V10B_00.kdz, V10E_00.kdz, V20B_00.kdz with KDZ Updater in all possible combinations and got the error "Upgrade error WParam:100. LParam:502" at each attempt.
terratrix said:
If it is stuck on android logo after flashing kdZ, take out battery and press voldown+home+power button to hard reset
Sent from my LG-P500
Click to expand...
Click to collapse
Now this doesn't work anymore, it starts into the Emergency Mode each time.
terratrix said:
Just try using froyo, dont upgrade to gingerbread, and see the problem still persist.
Click to expand...
Click to collapse
I can not flash any rom on it, it stays in the Emergency Mode screen. It is the same thins I mentioned to Aspee above.
Is my phone bricked?!
Now what?
My phone was acting wack so I decided to reboot and all of a sudden I saw the same screen that you are experiencing, but I just battery pulled and everything went back to normal. I have yet to experience this yet again though. (Running 6.5.7? CM7/Franco's kernel v19.?) Happened a while ago don't remember versions. I know I'm not much help but just saying I got this problem as well .
lmihaila said:
What is supposed to be the correct version? I tried these rom's: V10A_00.kdz, V10B_00.kdz, V10E_00.kdz, V20B_00.kdz with KDZ Updater in all possible combinations and got the error "Upgrade error WParam:100. LParam:502" at each attempt.
Now this doesn't work anymore, it starts into the Emergency Mode each time.
I can not flash any rom on it, it stays in the Emergency Mode screen. It is the same thins I mentioned to Aspee above.
Is my phone bricked?!
Now what?
Click to expand...
Click to collapse
if you have emergency mode theres always a chance your phone flash by kdz delete all drivers follow the tutorial on kdz and install the drives they provide and try more then one time because when hi the 1 and last time hi use lg mobile updater to update my phone it stop in midlle and hi was stuck in emergency mode,i tried a lot of times some times windows dont detect my phone others it do but kdz dont i dont count but only several times of tryng the kdz works...
but emergency mode random i never read or see in my phone if you get it work on froyo or gingerbrad and that still happens hi think you should go to warranty and say that in a midle of update byLG software your phone stay that way they will fix it....
Reminder: my phone boots to Emergency Mode after you power it off. While in emergency mode, if you unplug the battery it will boot the same way. If you leave the battery out for more than aprox 15 min, it will bot the OS it has written on it. Why??
After more an more hours spent on it I can conclude to this: my phone is to be seen by Windows only in emergency mode. I was able to flash it with KDZ while in emergency mode but with errors (Upgrage error: Wparam:100 LParam:6).
I was able also to flash it once with LGMDP but it stayed in the emergency mode screen and didn't rebooted itself, so again with an error.
I flashed it with both V10B and V20G and it behaves the same: while in Android, it isn't seen by Windows (with or without USB debugging) and if you reboot, it boots to Emergency Mode. Why??
it´the first time hi read something similar but if you cant or if you have a chance to try in other pc do it but if you cant leave that way take to lg center service and tell them that was making oficial update from their program and phone stuck like that they will fix it for free i dont now how to help you
I tried to connect the phone on three different machines, two Windows Seven and one XP. On XP I had the most success with flashing the phone.
sir lmihaila, i have the same problem. exactly the same. been following this thread since you posted it, still no solutions, got this phone cheap from a friend, it was on LG stock rom, not sure what he did on it, but it already was doing the Emergency mode.
i update a month ago to CM7, tried different kernels and roms, it was still happening on all of them, was about to try kdz, but then i saw your post saying it didnt work..
so until we found a solution, i guess we never turn phone off, or if it did, leave battery out, mine works out of Emergency mode after 5 mins of battery out.
bajie23, I'm glad you posted.
Indeed there is no solution yet, but I did some progress today. I played with the phone with it's battery unlugged and plugged his power adapter.
On a normal P500 the LG logo would appear and it would tell you to put the back cover and battery back. On mine, guess what, the emergency screen appeared.
But with a little knack, I pressed vol down+home+power and plugged the power adapter at the same time and the LG logo appeared as at a normal P500.
Then I inserted the battery, the device showed another wired attention triangle and Android System Recovery logo popped up, then I pressed Home and the Android System Recovery menu appeared. See pictures:
http://imageshack.us/photo/my-images/846/20110915230511.jpg/
http://imageshack.us/photo/my-images/16/20110915233836.jpg/
I could move trough the items in there with vol up - vol down but I couldn't press OK because none of LG P500 button did anything regarding this. I prepared even a new ROM on the SD card, renamed it to update.zip like in the Android System Recovery menu, but in vain because I cannot validate an action.
I exited this mode by unplugging the battery and power adapter,
I tried once again to enter Android System Recovery but I couldn't pass over the emergency screen anymore.
Just for the record, when you shake your phone do you also hear a little piece of something moving in the upper part of the device, right behind the earpiece? Does your handset has dropped marks? Has it ever been dropped, hit?
On my friend's functional P500 this noise isn't heard.
LS: bajie23, you said you tried different kernels and roms, how did you flashed them?
that was my first post. registered here just for this issue.
no moving parts inside, haven't dropped phone yet, no damage showing it has been..
i used clockworkmod recovery to flash - try to google it, there are tutorials, but i cant post links yet on this forum.
i installed recovery mode using "rom manager v4.3.1.3" app..
it simply instals recovery mode on start up. you can go to it by holding volDown+home+power. then vol up and down to navigate, menu button to select.
you can instal. zip from your sd using recovery mode.
problem is with our phone, booting in recovery mode gets you to that F&*%In "Emergency mode!" screen. you need to keep battery detached for 3-5 mins, put battery back then hold volDown+home+power, do not let go until the recovery screen appears.
you can instal kernels and roms using recovery mode, there are options to wipe the cache and everything, tried all of them, but guess what? still F^&*% "Emergency mode"
looks like our problem is deeper than the start up..
*next thing i will try is to revert back to original rom, try to unroot, and see if it helps, even though it doesn't appear to be on the rom or kernel.. then i'll try your step to see if i can get partition table error as well..
**i remember seeing on a site saying Emergency mode is like a test mode for lg that they use to flash..
Hi folks,
I have a Optimus One in the same condition. I tried to update Android to Gingerbread using the LG software and now it's pretty much always in "Emergency mode". I'didn't find any way to flash it again even with the stock rom. It seems that the usb port is not working correctly...
I'm using this procedure to let my P500 boot in "normal" way, and so far it seems to be working:
1) while the O1 is in Emergency mode, and the battery is almost fully charged, connect the charger a few minutes, let's say, 3 -5 min.
2) after that, remove the charger plug AND the battery
3) replace the battery on the phone
4) press the power button for 1-2 sec.
The phone should boot normally.
This procedure doesn't solve the "emergency mode" issue, but at least makes the phone usable.
Update: this procedure isn't working now!
I got this problem, too.
Bought LG P500 on 12nd november, updated to GB 2.3.3, no problems for 20 days.
Then trying to connect to PC I notice that it couldn't see it, nor SD and the phone, too.
After connecting to USB if trying to reboot the device it goes into emergency mode.
After pulling off the battery for 5 minutes it reboot normally but it is still not seen by the Pc.
After removing the battery and booting normally if I try to reeboot again in goes normally.
So I suppose that there is something conflictting connecting to usb that avoid to boot until memory cleared (battery removed).
I sent the device to LG, yesterday, hope they solve the problem, usb issue?
What about you?
partition table error is due to missing of partition.mbn file during selection of files to flash.
to install custom recovery you can follow http://forum.xda-developers.com/showthread.php?t=1318750 (partition file is included here use it if u want for some other purpose, it will be same for p500/optimus one as far as i know)
then flash rom from recovery follow http://forum.xda-developers.com/showthread.php?t=1309744
And if you are stuck at boot logo after flashing rom then factoryreset/format from recovery.
aFTER booting into rom if you see no gsm signal then upgrade baseband using http://forum.xda-developers.com/showthread.php?t=1217504
or
flash any other stock rom http://forum.xda-developers.com/showthread.php?p=19006040#post19006040
or
http://forum.xda-developers.com/showthread.php?t=1324105
mak.3736 said:
partition table error is due to missing of partition.mbn file during selection of files to flash.
to install custom recovery you can follow http://forum.xda-developers.com/showthread.php?t=1318750 (partition file is included here use it if u want for some other purpose, it will be same for p500/optimus one as far as i know)
then flash rom from recovery follow http://forum.xda-developers.com/showthread.php?t=1309744
And if you are stuck at boot logo after flashing rom then factoryreset/format from recovery.
aFTER booting into rom if you see no gsm signal then upgrade baseband using http://forum.xda-developers.com/showthread.php?t=1217504
or
flash any other stock rom http://forum.xda-developers.com/showthread.php?p=19006040#post19006040
or
http://forum.xda-developers.com/showthread.php?t=1324105
Click to expand...
Click to collapse
I had this problem (not the partition table error) not after a flashing but after 20 days past the flashing, before everything was well.
What can be happened?
I realized that there is something wrong with some LG500 motherboards, regarding USB connections. I too tried to flash the phone using LGMDP but I always got the partition table error. My phone, either in Emergency or in normal mode, is always recognized by the PC thru the USB, but when it starts to communicate it locks ... I cannot flash anymore, and actually it seems that USB port is useless.
I know that there are some special cables, apparently suitable for LG500 too, that can set the device in "download" (emergency?) mode, they use a 130k resistor somehow. If this is real, probably some motherboards are faulty, putting randomly the device in emergency mode, even without the mentioned cable. Pullup/pulldown resistor missing on MB? At first attempt to communicate, the USB controller of the phone locks, probably getting an undefined state. This is my impression.
Since my phone is still under warranty I settled to bring the phone to LG repair service...
i have a rooted at&t lg e970. i wanted to unlock the bootloader and install recovery on it. so i downloaded freegee,followed all the steps and twrp was installed on my phone. but when i decided to take a back up of my phone,it got switched off and now it wont boot . vol.up + power also takes a ridiculously long time to boot and doesn't work everytime. when vol.up+power does work, i get a recovery screen with power off,recovery,restart bootloader as options. but whichever option i select,i get a google screen and the phone shuts down. any help in this regard would me much appreciated.
{
"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"
}
i'm getting this message when i try to restore my phone using lgnpst.
i'm getting this message when i try to restore my phone using lgnpst.
can someone help me with this? phone doesn't boot at 67% or 85%. an gives the above error. any help would be greatly appreciated.
Volstagg.The.Valiant said:
can someone help me with this? phone doesn't boot at 67% or 85%. an gives the above error. any help would be greatly appreciated.
Click to expand...
Click to collapse
Does it do anything, like make it to the Rethink Possible screen and then hang?
Volstagg.The.Valiant said:
can someone help me with this? phone doesn't boot at 67% or 85%. an gives the above error. any help would be greatly appreciated.
Click to expand...
Click to collapse
If you look at the read me file it states that 67% and/or 85% means it's complete. Disconnect your phone and reboot. If it gets stuck after the LG splash, then you need to factory reset/wipe data. Hold the pwr button down for 12-15 seconds to make sure the phone powered off. Then press the vol down + pwr to get into the stock factory reset menu.
Sent from my Optimus G using xda app-developers app
adfurgerson said:
Does it do anything, like make it to the Rethink Possible screen and then hang?
Click to expand...
Click to collapse
no at 67% phone tries to reboot and LG start screen appears and then it goes into a loop
mikeylikey said:
If you look at the read me file it states that 67% and/or 85% means it's complete. Disconnect your phone and reboot. If it gets stuck after the LG splash, then you need to factory reset/wipe data. Hold the pwr button down for 12-15 seconds to make sure the phone powered off. Then press the vol down + pwr to get into the stock factory reset menu.
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
i'm getting the factory reset menu and even after confirming the reset phone doesn't boot up
Which freegee did you use, the PC program or the play store app? You may want to try the teenbin alt. with lgnpst, you will need a ROM copied to your SD card to flash from recovery after running teenybin.
adfurgerson said:
Which freegee did you use, the PC program or the play store app? You may want to try the teenbin alt. with lgnpst, you will need a ROM copied to your SD card to flash from recovery after running teenybin.
Click to expand...
Click to collapse
i used the freegee play store app. i shall try the lg dll file with teenybin alt with a ROM in my SD card for flash. problem is even teenybin doesn't seem to work. anyways i shall try this today when i get back from work and shall report on the progress. thanks for helping.
so i tried to flash teenybin to try and install recovery. but at 67% phone tries to reboot but is not rebooting. and then i get a msg saying that the connection to the phone has been lost. tried the same with teeny altbin also. getting the same response.
can someone explain what i'm doing wrong?
so i tried to flash teenybin to try and install recovery. but at 67% phone tries to reboot but is not rebooting. and then i get a msg saying that the connection to the phone has been lost. tried the same with teeny altbin also. getting the same response.
can someone explain what i'm doing wrong?
Sounds like you're bricked.
Sent from my LG Optimus G using XDA Premium 4 mobile app
DeathmonkeyGTX said:
Sounds like you're bricked.
Sent from my LG Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
any solutions to un-brick my phone?
Volstagg.The.Valiant said:
so i tried to flash teenybin to try and install recovery. but at 67% phone tries to reboot but is not rebooting. and then i get a msg saying that the connection to the phone has been lost. tried the same with teeny altbin also. getting the same response.
can someone explain what i'm doing wrong?
Click to expand...
Click to collapse
This is where you you should boot into recovery to flash ROM. Volume up plus power to get to fastboot, with alt you should be able to see recovery menu. If not it will be volume down twice then power.
quick update: installed teenybin successfully and got into recovery mode. but in recovery mode, if i select recovery option and press power button, the google logo flashes and the phone turns off. suggestions?
I'm having the same problems. These teenybins are broken. One stalls at the LG logo after rebooting at 67% with a disconnect, bricks with no bootloader/fastboot. The alternate reboots at 67% and stalls at 85% as well with a Google logo that I've never had before, and then my rom crashes everything I open constantly, e.g. not even able to bring up a keyboard. Both have killed my ADB/fastboot completely.
fierogt42 said:
I'm having the same problems. These teenybins are broken. One stalls at the LG logo after rebooting at 67% with a disconnect, bricks with no bootloader/fastboot. The alternate reboots at 67% and stalls at 85% as well with a Google logo that I've never had before, and then my rom crashes everything I open constantly, e.g. not even able to bring up a keyboard. Both have killed my ADB/fastboot completely.
Click to expand...
Click to collapse
Stalls ? That's what's suppose to happen. The Google logo is normal, I have that too. Your ROM crash ? Flash another one in recovery. Teenybins fixed my phone, I don't think they are broke
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Volstagg.The.Valiant said:
quick update: installed teenybin successfully and got into recovery mode. but in recovery mode, if i select recovery option and press power button, the google logo flashes and the phone turns off. suggestions?
Click to expand...
Click to collapse
You still have fastboot and are able to enter download mode so I think your fine. If no recovery, try to do the bin again after reading the instruction thoroughly. The bins work, it fixed my phone. You may have messed it up somewhere
Maybe I should be more specific. My previous rom that worked perfectly crashed constantly after the teenybin. One teenybin locks me out of everything but download mode, including recovery, and both teenybins also have made my ADB & fastboot stop working completely. Tell me that's normal too.
fierogt42 said:
Maybe I should be more specific. My previous rom that worked perfectly crashed constantly after the teenybin. One teenybin locks me out of everything but download mode, including recovery, and both teenybins also have made my ADB & fastboot stop working completely. Tell me that's normal too.
Click to expand...
Click to collapse
What's normal is I only tried to help and you continue with your attitude you will just have to help yourself
Hey guys
I got really annoyed by not being able to delete photos in Google Images, so I decided to root and fix it.
Now, after having my data wiped in the process of opening the bootloader (had to register on LG dev, etc), I am stuck on the last step - I can't get into TWRP to flash supersu.
I flashed it with the fastboot flash recovery command, but then after doing fastboot reboot, and then using adb reboot recovery, I get into the stock recovery.
I found two fixes, none of which work:
1. after flashing TWRP, turn off, then use HW buttons to get into recovery. On the fifth try, I got to the "erase all data" screen, which allegedly should be ignored. So I ignored it, and it erased all my data again
2. use fastboot boot command to boot TWRP directly. Doesn't work, I get an "unknown command" error.
Any other ideas how can I proceed to rooting my V10 (H960A) would be much appreciated.
Are you sure that you are using the command right for flashing the TWRP?? That should be something like: fastboot flash recovery recovery.img
recovery.img --->twrp
Also you get information whether flashing the recovery was successfull or not. Read the output in the coomand window carefully. Maybe you can post a screenshot or at least the returned message.
Here's a screenshot after going through the process again:
{
"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"
}
Hi,
flashing the recovery seems ok. Afterwards it seems vitally important that you switch off your phone, otherwise the recovery will be replaced by the stock revovery. Only after flashing SuperSu TWRP will be persistent.
Quote from the TWRP install instructions:
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again. You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
Click to expand...
Click to collapse
Also you tried to boot with the recovery image which is also not supported by LG.
I suggest you just flash TWRP again and do not try to reboot into recovery via fastboot command. Instead remove the battery right after flashing TWRP, wait a couple of seconds and put it in again. Then boot into recovery using the button combination decribed above.
I followed these steps three times with my phone (after updating the firmware) and it worked fine every time.
I tried it again and now I got through the whole rooting process.
Now I got stuck on the "Your device can't be checked for corruption" screen, which has been showing up on every boot since unlocking bootloader between the two animations, but now it's been there for a few minutes already.
Now what do I do?
****e, looks like I deleted my OS, while trying to wipe stuff in order to get through the boot freeze.
EDIT: I reinstalled stock ROM. Any ideas why it got stuck after rooting?
EDIT2: Installed the wrong ROM (some Tmobile branded version). Are there any custom ROMs for H960A running MM?
Hi,
no there are currently no Custom Roms for the H960A.
BTW: You will also get the "Your device can't be checked for corruption" screen with the correct ROM version. This is just a reminder popping up after bootloader unlock. After a couple of seconds the normal boot sequence will start.
I know, but the software version number now says H90110c
Also it's running 5.1.1. I can handle not having Nougat, but not back to 5.1 again...
I am searching for a way to get back my stock MM ROM, but there are apparently no ZIP or even kdz versions that work on the internet
Any help would be appreciated.
Yes, there are Android 6 kdz files for the H960A available, even in this forum:
http://forum.xda-developers.com/lg-v10/general/kdz-download-lollipop-kdz-10c-lg-servers-t3332348
Make sure you select the correct H960A version as there are two available: Europe and United Arab Emirates.
If the download does not work when you click on a link click it with the right mouse button select "copy link" (or similar, exact text depends on browser). Then open a new browser tab/windows and paste the link in the address field. Now the download should work.
You need to flash the kdz with LGUP.
In your case I would recommend the "REFURBISH" option in LGUP as it makes sure that the phone is completely wiped and reset.
As the refurbish option normally only allows tot-files to be selected you need to use a little trick. The below instructions are quoted from the LGUP thread (http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803). Please look there if you need further information. You don't need to do the changes in the prop-file described at he beginning of the instructions. If you have not installed LGUP yet you'll find it in that thread as well.
TO DO A FULL WIPE AND INSTALL MM - Open the LGUP on your computer.
Select the option "update" (if not already selected).
FILE PATH: point it towards the MM KDZ file.
IMPORTANT!!!!!!! shut down LGUP!
Now open LGUP again - you will notice that the MM KDZ will still be showing in the FILE PATH section. Select REFURBISH and make sure BIN file is ticked. Press Start. Make cup of tea and be patient
Click to expand...
Click to collapse
Unfortunately, the downloads in that forum don't work, even after copy/pasting the link into Chrome, FF, even MSE...
I got two different kdz files from somewhere on the internet:
Europe H960A20a_00_0316
H960A10c_00_1224
None of them work. I got an error during the initialization phase saying the kdz file is incorrect.
Maybe it's because it says H90110c under version (as I said, I managed to install the wrong ROM after wiping everything)?
This is a nightmare. Please help
Hi i was hoping someone could help me fix my SM-G925F device (willing to donate to anyone that can help me fix it). I will give you abit of information of how im in the situation going back to about a year ago i got a firmware update on my samsung galaxy s6 edge so i started downloading it and my device rebooted and said it was installing the update but halfway through it must of corrupted or failed but my device still booted up and when i went into my settings it said i was on android version 7.0 so thought nothing of it but did start having a few minor issues now and then but anyway on sunday i was playing a game on my phone and it randomly just froze so i waited 2 mins and then it seemed to be working again but then 5 mins later it did it again and i waited around 10 mins and it was still frozen so i had a look on google and it showed me a button combination you can do to restart your device if it does freeze but after it tried rebooting it would just sit on the s6 edge logo screen so i tired looking online again and it told me to go into recovery mode which i did and it showed a little error at the bottom left corner saying "dm-verity error" but i still tried clearing my cache partition but when i rebooted the phone it was still stuck on the s6 edge logo. I decided to reflash my device with a stock rom from sammobile but it failed at system.img and when i try booting my phone i get a error saying "An error has occured while updating the device software. Use the Emergency recovery function in the Smart PC software" so i tried flashing a custom recovery named "TWRP" but that also failed so now when i go into dowload mode by holding down the down volume + home + power buttons and press volume up to enter dowload mode in the top left corner it says:
ODIN MODE
PRODUCT NAME: SM-G925F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
Secure Dowload: Enabled
KNOX WARRANTY VOID: 1 (0x0200)
AP SWREV: B:6 K:2 S:2
I have tried different stock roms that match my device model but now odin fails on boot.img or just stays on initialization
Only a side remark:
As long as dm-verity ( read: Android's verified boot implementation ) isn't got disabled prior to make changes to Android OS any hacking/modding will fail.
jwoegerbauer said:
Only a side remark:
As long as dm-verity ( read: Android's verified boot implementation ) isn't got disabled prior to make changes to Android OS any hacking/modding will fail.
Click to expand...
Click to collapse
I'm only trying to re flash the stock rom but for some reason since i tried flashing twrp it won't let me flash anything while using odin anymore. It will stay on the
initialization stage and say it's failed around 20 mins later. I've tried using different odin versions, different usb cables and even different pc's but nothing seems to be working
iCrazyGaming said:
I'm only trying to re flash the stock rom but for some reason since i tried flashing twrp it won't let me flash anything while using odin anymore. It will stay on the
initialization stage and say it's failed around 20 mins later. I've tried using different odin versions, different usb cables and even different pc's but nothing seems to be working
Click to expand...
Click to collapse
Try this:
1. Use only latest Firmware for your region Official or if you can't find send me private your IMEI or try to
use DBT Germany without branding which you can download from here with free registration
https://updato.com/firmware-archive-select-model/?record=46C645F08BE911E89F15FA163EE8F90B
2. Latest Version of Odin
3. Re-instal your drivers
4. Disable antiviruses if somehow is blocking connections....
Good luck
Teddy Lo said:
Try this:
1. Use only latest Firmware for your region Official or if you can't find send me private your IMEI or try to
use DBT Germany without branding which you can download from here with free registration
https://updato.com/firmware-archive-select-model/?record=46C645F08BE911E89F15FA163EE8F90B
2. Latest Version of Odin
3. Re-instal your drivers
4. Disable antiviruses if somehow is blocking connections....
Good luck
Click to expand...
Click to collapse
Gave all your steps a try but still nothing. Odin recognises my device when it's plugged in but just won't flash it. The status bar in download mode doesn't even show up
iCrazyGaming said:
Gave all your steps a try but still nothing. Odin recognises my device when it's plugged in but just won't flash it. The status bar in download mode doesn't even show up
Click to expand...
Click to collapse
Download the 4 file Rom and flash only BL (bootloader) file.
edit: I recomended the sanfirm windows app to download. After flashing bootloader flash Full soft.
Bet3k said:
Download the 4 file Rom and flash only BL (bootloader) file.
Click to expand...
Click to collapse
The s6 edge stock rom comes as 1 tar file but I've tried extracting it and tried flashing the bootloader file but odin still stays on the initialization stage
iCrazyGaming said:
The s6 edge stock rom comes as 1 tar file but I've tried extracting it and tried flashing the bootloader file but odin still stays on the initialization stage
Click to expand...
Click to collapse
Do you can boot to recovery?
Bet3k said:
Do you can boot to recovery?
Click to expand...
Click to collapse
No i can only get into download mode or it just goes to the An error has occured while updating the device software. Use the Emergency recovery function in the Smart PC software screen. The phone no longer holds it's charge it just turns off as soon as i unplug it
iCrazyGaming said:
No i can only get into download mode or it just goes to the An error has occured while updating the device software. Use the Emergency recovery function in the Smart PC software screen. The phone no longer holds it's charge it just turns off as soon as i unplug it
Click to expand...
Click to collapse
Try to flash only recovery, in options uncheck auto reboot. after flash Press vol- + power + Home when screen goes black quick Change vol - to vol + and un Press power. Sorry for my bad eng
Bet3k said:
Try to flash only recovery, in options uncheck auto reboot. after flash Press vol- + power + Home when screen goes black quick Change vol - to vol + and un Press power. Sorry for my bad eng
Click to expand...
Click to collapse
Sorry only just seen this message. Which file is the recovery file? I have a AP, BL, CP and CSC file
Also I'm using a BTU stock firmware
iCrazyGaming said:
Also I'm using a BTU stock firmware
Click to expand...
Click to collapse
Are you sure you're trying to flash the proper firmware for your device/region? Which version of ODIN are you using?
xSil3nt said:
Are you sure you're trying to flash the proper firmware for your device/region? Which version of ODIN are you using?
Click to expand...
Click to collapse
Yeah the phone was bought from carphone warehouse in the uk so it isn't locked to a certain carrier. I have tried alot of different versions but the latest ones i have tried where 3.14.1, 3.13.3. I honestly don't think it's a problem with the software because it was flashing fine before i tried flashing twrp and it failed ever since then odin just stays on initialization stage and then will just say it's failed about 20 mins later
iCrazyGaming said:
Yeah the phone was bought from carphone warehouse in the uk so it isn't locked to a certain carrier. I have tried alot of different versions but the latest ones i have tried where 3.14.1, 3.13.3. I honestly don't think it's a problem with the software because it was flashing fine before i tried flashing twrp and it failed ever since then odin just stays on initialization stage and then will just say it's failed about 20 mins later
Click to expand...
Click to collapse
Device shows up and you're able to load the file to Odin, and click flash, right? But no progress?/stuck on initialization. I had this exact issue a while back (While I was testing my SHRP builds, was trying to reflash TWRP after my build didn't boot) on Odin 3.13, worked for me when I tried Odin 3.10.7. 3.13 *was* working fine for me earlier, no idea what caused it to stop working, could be worth a shot.
Link to Odin 3.10.7: https://samsungodin.org/download/Odin3_v3.10.7.zip
---------- Post added at 04:07 PM ---------- Previous post was at 04:04 PM ----------
xSil3nt said:
Device shows up and you're able to load the file to Odin, and click flash, right? But no progress?/stuck on initialization. I had this exact issue a while back (While I was testing my SHRP builds, was trying to reflash TWRP after my build didn't boot) on Odin 3.13, worked for me when I tried Odin 3.10.7. 3.13 *was* working fine for me earlier, no idea what caused it to stop working, could be worth a shot.
Link to Odin 3.10.7: https://samsungodin.org/download/Odin3_v3.10.7.zip
Click to expand...
Click to collapse
I'm using a Galaxy Note 5, which share the same SoC, so it is possible that we were having the same/a similar issue.
xSil3nt said:
Device shows up and you're able to load the file to Odin, and click flash, right? But no progress?/stuck on initialization. I had this exact issue a while back (While I was testing my SHRP builds, was trying to reflash TWRP after my build didn't boot) on Odin 3.13, worked for me when I tried Odin 3.10.7. 3.13 *was* working fine for me earlier, no idea what caused it to stop working, could be worth a shot.
Link to Odin 3.10.7: https://samsungodin.org/download/Odin3_v3.10.7.zip
Click to expand...
Click to collapse
I think i tried 3.10.7 a while ago because people recommended it to me and i couldn't get it to work but I'll give it another try. It just feels like my pc is recognising my device but it doesn't have permission to edit anything on the phone
{
"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"
}
This is the results everytime no matter what i do
Can anyone else please help me like i said I'm willing to give money to get it fixed as i have important stuff on the phone that i need
Do you have latest version of Samsung USB drivers ?
---------- Post added at 11:53 PM ---------- Previous post was at 11:41 PM ----------
Try this:
1. Boot into download Mode if you see Warning! screen click vol - (restart)
2. After click vol- quickly press: power+ home+ vol-
3. This time click vol+ (download)
4. Try to flash
5. If flash complete sucessfully wipe data from recovery (skip this if you have important files)
Hello!
I've had AICP on my Z2-wifi tablet for a long time, have not modified it in year but I am having a lot of problems lately. Play Store keeps telling me to clean up my storage to install more apps, but I already have 8gb free.
I decided to Factory Reset and after it rebooted, nothing changed.
Okay then let's access Recovery and do things myself.
Holding Power+Volume Down gives me a purple LED but then AICP still loads.
When the purple led appears, if I lift my finger it turns yellow, then Sony logo again, AICP, Android desktop.
Tried to Reboot into Recovery from AICP but it just won't do it.
Try reboot into Recovery from ADB but it rebooted again directly into android.
"adb reboot recovery"
Went with "adb reboot bootloader" and the tablet reboots into a black screen with the corner led blue. Not accessible from ADB anymore. Nothing on screen. Can't flash twrp is ADB does not detect it. "fastboot flash recovery twrp.img" gives me < waiting for any device >.
I just installed Sony EMMA tool, I need to access fastboot but the tablet just reboots into android. Managed to boot into bootloader black screen with blue led, Emma does not detect it.
Any suggestions?
Tried to get root access with Easy Root Tool
https://forum.xda-developers.com/showthread.php?p=53448680#post53448680
Got this error:
Kernel version is 3.4.0-aicp-g198fdc7
Version does not match 3.4.0-perf-ge4322cd needs patching
Kernel module patched.
Android 5.0 and later only support position-independent executables (-fPIE)
Now trying the Sony Xperia Companion for Windows tool.
https://www.sony.ca/en/electronics/...ts-mobile-phones/xperia-xa2/articles/00236877
It doesn't want to update but there is a Software Repair option. Which does not work. My Tablet is still rebooting to android AICP.
{
"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"
}
Tried the Sony Emma tool.
https://developer.sony.com/develop/open-devices/get-started/flash-tool/download-flash-tool/
Tablet has a black screen and blue LED.
Not detected by Emma.
Installed Android Studio, let's see if a reboot of my PC helps the get the right drivers running.
https://developer.android.com/studio
Installing the Google USB Drivers.
https://developer.android.com/studio/run/win-usb
The tablet is now listed when using "fastboot devices"
Trying to boot into TWRP 3.4 from this thread https://forum.xda-developers.com/xp...y-twrp-3-4-0-castor-windy-sony-t4110865/page3
FAILED: remote: "dtb not found"
Spent over 4 hours trying to fix my tablet today... Will try again tomorrow...
Flashing TWRP 3.2.1 from here.
https://drive.google.com/file/d/15vBMmeAYhnLxP3GTFTBka-kIemxMDb3r/view?usp=sharing
Flash seems to have worked, boot into twrp321.img just turned off the tablet.
Tablet is stuck in a boot loop at AICP colored letters animation.
Flashing TWRP 3.2.1 from this thread now, in case it is different, but file size seems to be the same.
https://forum.xda-developers.com/xperia-z2-tablet/development/7-x-x-carbonrom-cr-5-1-t3654983
Flashing boot.img from AICP weekly
https://dwnld.aicp-rom.com/device/castor_windy/WEEKLY/aicp_castor_windy_q-15.0-WEEKLY-20201002.zip
fastboot error Couldn't parse partition size '0x'
Well... this can't be good...
Flashing using the "fastboot flash:raw boot boot.img" command.
Now i got a bootloop with just Sony Xperia logo and the purple LED flashing.
When holding volume Up + power i get 3 vibrations, then it reboots into black screen and blue LED (fastboot mode).
Running out of ideas...
Sony Emma tool does not see the tablet in fastboot mode.
Xperia Companion wants me to unlock the device, which means going into android, not going to work as all I have now is fastboot mode.
I was hoping I could use this to clean up my mess and reset everything back to default factory settings.
Wanted to try Android Flash Tool, a browser based solution. It is not seeing my tablet.
https://flash.android.com/devices?continue=/custom
Trying Flashtool.net instead.
http://www.flashtool.net/downloads_windows.php
Will try this Sony Stock.
https://forum.xda-developers.com/xp...lipopprerooted231a128z2-tabletsgp511-t3100821
NotAPirate said:
Trying Flashtool.net instead.
http://www.flashtool.net/downloads_windows.php
Will try this Sony Stock.
https://forum.xda-developers.com/xp...lipopprerooted231a128z2-tabletsgp511-t3100821
Click to expand...
Click to collapse
Hey @NotAPirate,,
Got your tag bud!
I have not been able to read through every post you made yet. Just got home from work and read the OP.
Couple things to start trouble shooting, keep in mind i have only read the OP then started typing you a message, so if you are past all of this below, sorry!
.
1. Have you been able to access recovery yet and clean up your tablet? Seen in your OP and that your tab rebooted to AICP when you tried to boot to recovery. After the tablet starts and you see the SONY logo with XPERIA across the center bottom, start tapping the VOLUME UP button, no need to hold the power button. Tap repeatedly till you see a Purple LED, then you will feel vibration and the LED will turn Orange, then you can stop tapping, not sure how many are needed, but to get you in there do it.
2. When you boot the tablet do you see XPERIA across the bottom in the center. The SONY name will be centered in the middle of the tablet and XPERIA will be across the bottom centered while booting from power off or a reboot. I only ask, because older fw does not have XPERIA across the bottom and the older FW does not work well with MARSHMALLOW + ROMS.
3. I am not familiar with EMMA, know what it is, just never used it. I can walk you through the FLASHTOOL steps if you want to start fresh using Flashtool and an FTF. I have always use flashtool and always got my tab fixed and back to original when i Bork something up good. I have links to the pages that give step by step instructions, and have a Pre-ROOTED Android 6.0 SONY Stock ROM in FTF format somewhere. The FTF is what is needed to flash original Sony fw, in case you didn't know. If you did....well my bad then.
I will read through everything in the morning and get back to you then.
Have a good evening or day, which ever place in the world your in.
@NotAPirate,
Read through the thread. Unfortunately i am unable to determine what it is you are trying to do exactly. Is TWRP recovery not installed, or not opening when you try to access recovery?
Also, i did a little research this morning, my wife is getting an XPERIA 5 plus or pro. Anyway, i learned in reading through some threads for her phone, once you UNLOCK the boot-loader, you cannot use EMMA or Sony's Flash Tool, etc. You will need to use flashtool by androxyde. here is the link https://forum.xda-developers.com/showthread.php?t=920746 for some general reading. Here is the link about official Sony tools not working https://xperiafirmware.com/flashtool/ in the middle of the post you will see it. The flash tool they are talking about IS-NOT the one i linked previous.
The above links and info is because you were talking about just re-flashing your device. But before starting from scratch, let's narrow down exactly what the problem you are having is, then we will try to fix that, and re-flash to Stock OS as a last resort.
If you decide to just use flashtool and start over, let me know and i will send you an older version of flashtool that seems to work good for our device, always has for me anyway. The newest may work, i just never tried it.
**If you want to attempt to troubleshoot this without re-flashing to the beginning, please answer the 2nd questions in my previous post as well. It will help me narrow down the problem, as it will give an indication of the FW you are on**
I am not a dev nor do i know all the cmd line tricks to get things done quick like others can, just been using this tablet for 5 years and have been through it all, it seems and know what to check and look for....most of the time anyway..
Plugging the tablet in my usb power supply.
Held volume UP only, when Sony Xperia logos were visible and waited until LED turned yellow and felt vibration.
TWRP 3.2.1-1 loaded!
Formatting Data
Wipe Dalvik/Cache
Wipe System
Wipe Internal
Install AICP weekly
https://dwnld.aicp-rom.com/device/ca...Y-20201002.zip
Install OpenGapps, ARM, Android 10, Nano.https://opengapps.org/
Reboot.
purple Led is flashing a few times on Xperia Logo.
AICP custom rom logo animation.
First time setup of Android, WOOHOO!
Up next, give TWRP 3.4 a shot, and try to root with Magisk.
NotAPirate said:
Plugging the tablet in my usb power supply.
Held volume UP only, when Sony Xperia logos were visible and waited until LED turned yellow and felt vibration.
TWRP 3.2.1-1 loaded!
Formatting Data
Wipe Dalvik/Cache
Wipe System
Wipe Internal
Install AICP weekly
https://dwnld.aicp-rom.com/device/ca...Y-20201002.zip
Install OpenGapps, ARM, Android 10, Nano.https://opengapps.org/
Reboot.
purple Led is flashing a few times on Xperia Logo.
AICP custom rom logo animation.
First time setup of Android, WOOHOO!
Up next, give TWRP 3.4 a shot, and try to root with Magisk.
Click to expand...
Click to collapse
@NotAPirate,
Good deal bro!
Yes the PURPLE flashing LED on boot (at Xperia Log) is normal. No worries there.
AICP from spiritcroc is OFFICIAL and has OTA's. They are under the AICP settings in the Settings panel. In case you were not aware the OTA's worked on AICP.
Now, 3.4 from Spiritcroc, should be installable without an issue. I flashed 3.4 with fast-boot commands in Boot-loader mode.
I personally use MAGISK 20.1 on my device. I ran into a few problems with my audio mods when on MAGISK 20.4. Just an FYI!!!! The newest MAGISK manager is fine. All you need to do is flash in TWRP and reboot. Then open the magisk manager and do your thing. If the app is missing in the app drawer, use a file manager and open the MAGISK zip you flashed and the apk will be in the COMMON folder if not mistaken. Folder may be wrong but looking around will find it.
If i can assist with anything, let me know!!!!