I've had my Verizon LG G2 for almost a year and mistakenly upgraded to Lollipop. I researched downgrading to KitKat and it looked safe; I had dual booted my HP Touchpad with a similar process.
I tried rooting with ADB, but it was giving me fits. I used the LG One Click Root Tool. It worked fine. (Running on Windows 7.)
I installed TWRP v2.8.5.1, and downloaded a stock version of KitKat 4.4.4. (I'll admit, at this point, I had looked at multiple guides. Many had missing links or dead ends, but they were all about the same, and always stock.) I followed instructions on clearing and wiping caches, etc. I believe the exact ROM I tried to install was VS98011A_01.zip. It didn't work. It gave the error:
"assert failed: run_program("/tmp/loki.sh") ==0
E: Error executing updater binary in zip"
I looked for more ROMs and tried ParanoidAndroid "pa_g2-4.0-ALPHA-20131203-vs980.zip". At this point, I started to worry and tried installing the Gapps file I downloaded with the stock ROM, and it installed with no problems.
I then tried to install a newer version of TWRP "twrp-2.8.6.0-vs980.zip". (Again, I hadn't really found any great guides at this point, especially to fix my problem, so I was assuming there was something wrong with my ROMs.) It didn't work, and I tried to install Cyanogen Recovery because I ran across it and remembered it from my HP Touchpad. "cm-10.2-vs98012b.zip" did not work, and gave the error above.
I looked for Loki issues and tried downloading a fresh Loki (sorry, I don't have the link) folder and replaced all the files in the original KK .zip I tried. Same loki error. (Sometimes I'll get a "sysMapFile" error, but not often. At this point, I'd dragged a lot of things over to try to install and get anything to work.)
At this point, I tried the following:
http://forum.xda-developers.com/showthread.php?t=2448960
http://forum.xda-developers.com/showthread.php?t=2451696 (as well as a similar one by downloading a laf.img)
http://forum.xda-developers.com/showthread.php?t=2797190
http://forum.xda-developers.com/showthread.php?t=2432476
http://hackerspace.lifehacker.com/how-to-install-a-rom-via-sideload-1505153925
http://forum.xda-developers.com/showthread.php?t=2318497
http://www.androidayos.com/2014/10/06/fix-bricked-lg-g2-stuck-logo-twrp-bootloops-download-mode/
http://forum.xda-developers.com/showthread.php?t=2448960
There were definitely some more links I used but these were the most promising and the ones I still have open.
Several of the LGFlashTools were very close to working, but there were several issues:
1. I can't get it into Download Mode, as it gives a boot certification error.
2. There were some problems with the phone not showing up in Device Manager under "Ports" with COM41, and I thought I had largely resolved that issue. (Depending on the article I was looking at.)
3. Drivers, I'm not sure if they're an issue; I've downloaded several, and installed them, including 2.0 and a 3.1.
ADB does not recognize my device, as I've tried sideloading, although I can still drag and drop files. (I believe I pushed a file into the device early on and it worked though.)
4. Fastboot recognizes there's a device and can boot it via CMD but will not give a number when I use "fastboot devices". I've researched some flashing via Fastboot, and tried flashing the original KK .zip with it, but it said there wasn't enough space. I have about 14GB left on a 32GB device, however.
I hope I've provided enough information, because I've researched and tried so many ways to unbrick it, short of physically opening the phone as suggested here: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Any advice or suggestions would be greatly appreciated. I would love to know what I did wrong, because I know custom ROMs would be a great alternative to dealing with Lollipop until I can upgrade over a year from now.
Greetings,
I recently got a Pixel 2 XL and the first thing I did was try to root with SuperSU and TWRP. I had some issues with it and someone suggested Magisk. It worked great and I was able to update from the 8.0 to 8.1 with root. I kept up with the latest Magisk installs until the past week or so.
My phones USB port appears to have failed partially. Luckily I can still charge, but there is no way to see the device storage from a PC. Support has defaulted, after much troubleshooting, to an RMA solution with a refurbished phone. Thankfully, this seems to be covered by warranty and isn't going to pose a cost issue. However, through the troubleshooting I was forced to do a factory reset. I looked up some information regarding factory reset with rooted devices. I cannot find the exact tutorial I followed or thread I gained the how-to information, I'm not sure which it was. I simply searched how to factory reset magisk 8.1 device. It was quick and most of the stuff I find now has the same information.
Open Magisk, uninstall. Open TWRP, uninstall. Device Settings, Factory Reset. Easy
This seemed to have worked. I didn't run into any locked hardware issues thankful because I don't have USB to really flash something to it.
Before I continued, prior to attempting the reset I fully backed up the device to my computer using ES File Explorers FTP transfer over the wifi. This was great, lots of photos were able to be saved with no hassle. I copied the entire root directory and have it backed up.
The problem with the reset is that while Magisk remained uninstalled, TWRP has a basic file installed that upgrades to the full app. I still have root, which would have been nice, except I still need to unroot and go back to factory settings before I can send this device in.
Before I make a mistake moving forward, I want to find the best way to unroot, (preferrably relock the boot also), and return to factory stock as it was the day I got it so I can return in it in the best state I can.
I am running rooted android 8.1.0 Pixel 2 XL with kernel 4.4.88 if the helps. When I reset to factory defaults TWRP remains installed and root persists. I cannot connect via USB and run android dev tools to flash anything directly. How can I restore this device? I should have all original kernels backed up. During the root process I remember them saying to copy the old ROMs first and I performed every step exactly. I do have access to move files to and from the device via WiFi. Is it this even possible?
PS, does anyone think the firmware and rooted install could be the problem with the USB? It seems entirely like failed hardware to me but the troubleshooting was extremely thorough and seems to indicate softare/firmware are likely to be the issue instead of the hardware issue that was determined. Could this still rooted device have corrupted the USB transfer? It seems I should do my best to rule this out as well, more so than just giving them a factory reset device. I'd rather keep my phone if it can be fixed easily, than obtain a possibly low quality heavily used refurbished model.
Regards
Did you try removing and reinstalling the drivers?
Sent from my MI 5 using Tapatalk
teddy0209 said:
Did you try removing and reinstalling the drivers?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
I assume you mean for the PC. Yes, I have tried uninstalling and reinstalling both using Microsofts found drivers and directly sent packages from the support team. Updates and 2 different PCs. DevKit installed on the one I originally used to root and a new PC with fresh driver installs.
They wouldn't suggest drivers for the phone, if you know of a way to install new drivers for the phone, please let me know, I'd definitely give that a shot.
Regards
BlazzedTroll said:
I assume you mean for the PC. Yes, I have tried uninstalling and reinstalling both using Microsofts found drivers and directly sent packages from the support team. Updates and 2 different PCs. DevKit installed on the one I originally used to root and a new PC with fresh driver installs.
They wouldn't suggest drivers for the phone, if you know of a way to install new drivers for the phone, please let me know, I'd definitely give that a shot.
Regards
Click to expand...
Click to collapse
I should include all troubleshooting I mentioned for those that think they have a solution for the dead USB. My original request was for the OTA flash directions without USB, but I think a lot of people will want to suggest fixes for the phone as I suggested in the PS section.
Step 1: Check computer software.
Windows users, check to see if you have the latest version of Windows Media Player and have installed all recent system updates. Visit omitted for more information.
Mac users, make sure you install and are using Android File Transfer. Visit omitted for more information.
Step 2: Check for system updates.
On your device, go to "Settings" > Scroll down to "System" > Touch "About phone" (or tablet) > Touch "System updates".
If your device has a modified OS, troubleshooting may not resolve your device issue. Re-image your device back to Android factory settings using the instructions from the following link: omitted
Step 3: Restart your device in safe mode.
With the device on, hold the Power button to get the "Power off" prompt.
Touch and hold "Power off" until the "Reboot to safe mode" prompt appears.
Touch "OK" to reboot in safe mode.
Note: To exit safe mode later, simply restart the device normally.
Step 4: Unlock your device.
Before connecting the device to a computer, if your device is password protected, unlock your device. A locked device will not connect to the computer.
Step 5: Connect USB cable directly into computer.
If the USB cable is connected through a USB hub or extension, unplug the cable from the hub/extension and plug it directly to the computer.
A pop-up window should appear.
Mac users will have the Android File Transfer window appear.
Windows users may have a pop-up window appear. If not: On the computer, click the Windows Start button on the bottom left > click Computer > under Portable Devices, click on the device > click on the device's Internal Storage.
Step 6: Test if you can transfer files.
Try transferring a small file.
If file transfer works, success! No need to do the next steps.
If file transfer still isn't working (no pop-up windows to allow file transfer), proceed to Step 7.
Step 7: Change your USB computer connection settings.
Android 6+ Marshmallow only:
Plug in the device.
Slide down the notifications drawer from the top of the screen.
Touch the notification saying "USB for charging."
Touch the option for "File Transfers".
Test file transfer again (from Step 6). If the file transfer does not work, proceed to Step 8.
Older Android OS Versions:
Go to "Settings", under "Device," touch "Storage" > touch the "Menu" button (three vertical boxes at the top right) > touch "USB computer connection".
Only Media Transfer Protocol (MTP) should be checked. Uncheck MTP, check and then uncheck PTP, then re-check MTP.
Test file transfer again (from Step 6). If the file transfer does not work, proceed to Step 8.
Step 8: Windows Only: Install Google USB Driver.
Go to omitted and click the blue button on the right labeled "Download Google USB Driver."
After the download completes, right click the file ("latest_usb_driver_windows.zip") and select "Extract All."
Follow the USB Driver installation instructions available here: omitted
Test file transfer again. If file transfer still isn't working (no pop-up windows to allow file transfer), proceed to Step 9.
Step 9: Turn on "Developer options" and disable USB debugging.
Go to "Settings."
If using a phone, swipe down the screen with two fingers, then touch "Settings."
If using a tablet, swipe down the screen from the right side of the top of the screen, then touch "Settings."
Scroll down to "System" and touch "Developer options." If you don't see "Developer options," turn them on as follows:
Touch "About phone."
Scroll down to the "Build number."
Touch "Build number" 7 times to activate "Developer options."
Under "Debugging," verify that the box for "USB Debugging" is not checked. If it is checked, touch the checkmark to uncheck "USB Debugging."
Once USB Debugging has been deactivated, test file transfer again.
Step 10: Try different USB connections.
Try plugging the USB cable into a different USB port on the same computer.
Try connecting to the same computer but using a different/spare USB cable.
Try connecting your device to another computer.
Click to expand...
Click to collapse
My apologies on readability, I tried to include HTML formatting. I couldn't figure it out, the options support code highlighting but not the code itself.
Additionally, I tried different USB cables, safe mode, and the factory reset that I could perform.
@BlazzedTroll
Summary:
You've uninstalled Magisk, so you don't have root access when booted. TWRP still remains, so you have root access there.
If I read you correctly, what you need to do is to get rid of TWRP. Right?
Download the corresponding factory image, extract recovery.img and flash that by issuing the Install Image option in TWRP.
Just make sure you've done everything you need to before doing this, since you can't get back to a custom recovery if your USB really is busted. Other things to do could include flashing the system.img the same way to revert any possible /system modifications, etc.
Didgeridoohan said:
@BlazzedTroll
Summary:
You've uninstalled Magisk, so you don't have root access when booted. TWRP still remains, so you have root access there.
If I read you correctly, what you need to do is to get rid of TWRP. Right?
Download the corresponding factory image, extract recovery.img and flash that by issuing the Install Image option in TWRP.
Just make sure you've done everything you need to before doing this, since you can't get back to a custom recovery if your USB really is busted. Other things to do could include flashing the system.img the same way to revert any possible /system modifications, etc.
Click to expand...
Click to collapse
When you say corresponding factory image, does that mean I need the exact one that came on the device? Or just the latest factory image for the right device?
*EDIT* Never mind that, I found the backup folder in the Unified Toolkit which contains a compressed zip just like the ones on the site. I'll use that and transfer to my device over WiFi and use TWRP to flash it and come back with the results.
Thank you for your assistance
@Didgeridoohan
I have a backup locally saved that resembles those packages. I was unable to locate a recovery.img in either my saved file or the one on the site. My version that was backed up was 1.171019.011, which is 8.1. I know my phone came originally with 8.0 so I tried looking at one of the those for a recovery.img and still could not locate one.
In the zip there are several files
bootloader-taimen-tmz12a.img
flash-all.bat
flash-all.sh
flash-base.sh
another zip
radio-taimen-g8998-00164-17... .img
inside the second zip, many more .img files looked promising
abl.img
aes.img
android-info.txt
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dtbo.img
hyp.img
keymaster.img
laf.img
modem.img
pmic.img
rpm.img
system.img
system_other.img
tz.img
vbmeta.img
vendor.img
xbl.img
Same files in all 3 zips I checked.
TWRP only expects recovery.img for "BACKUP EXISTING RECOVERY"
TWRP also has "TWRP FLASH", which I did as one of my troubleshooting steps before and got the Google Pixel 2 XL (taimen) flash. These still keep the TWRP and root, which I believe is to be expected for that flash option.
DELETED
BlazzedTroll said:
I assume you mean for the PC. Yes, I have tried uninstalling and reinstalling both using Microsofts found drivers and directly sent packages from the support team. Updates and 2 different PCs. DevKit installed on the one I originally used to root and a new PC with fresh driver installs.
They wouldn't suggest drivers for the phone, if you know of a way to install new drivers for the phone, please let me know, I'd definitely give that a shot.
Regards
Click to expand...
Click to collapse
You're right, I mean for PC...
You can usually get twrp backups from same device with same rom and flash it on yours via twrp ( ask on your device forum)... You will need system.img, recovery.img, and boot.img... I'm not so sure if you can relock the device without working usb/fastboot...
Sent from my MI 5 using Tapatalk
@BlazzedTroll
My apologies... I'm still not used to these damned A/B devices. :laugh:
If I remember correctly, recovery is included in the boot image, so what you need to do is flash the stock boot.img file to slot A. Don't know if this is possible in TWRP.
teddy0209 said:
You're right, I mean for PC...
You can usually get twrp backups from same device with same rom and flash it on yours via twrp ( ask on your device forum)... You will need system.img, recovery.img, and boot.img... I'm not so sure if you can relock the device without working usb/fastboot...
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
I'll give this a shot, I have system.img and boot.img, as I said in reply to Didgeridoohan, I do not have a recovery.img in the files.
Sad news about relocking, but that should be OK.
Thanks for lending some help
Didgeridoohan said:
@BlazzedTroll
My apologies... I'm still not used to these damned A/B devices. :laugh:
If I remember correctly, recovery is included in the boot image, so what you need to do is flash the stock boot.img file to slot A. Don't know if this is possible in TWRP.
Click to expand...
Click to collapse
That's alright. I don't know much of anything about them. It's easy enough to follow tutorials and if I had my USB connection I could do as you say pretty quickly. The problem is I don't understand what TWRP even is. There doesn't seem to be an option to flash you own custom img. "TWRP FLASH" only lets you select from the latest versions and downloads the one you select and starts the flash. "BACKUP EXISTING RECOVERY" expects a recovery.img and doesn't let me select anything other than that. I could try renaming system.img to recovery.img, but until I find out what the difference between the images is, I'm not to keen on trying that one. Sounds like a good way to get hosed before I return it. At this time, I would think without having USB access the folks at Google would be happy to have root on the phone. Rather return it working, but rooted, than bricked.
So I was trying to follow some other suggestions and it seems like maybe the device is actually not rooted anymore.
There is no SU file located in system/bin or system/xbin.
When I download something like "Root Checker" it gets stuck verifying the root.
I tried to use apps like rashr and flashify to flash a stock recovery and neither app will load properly suggesting no root access.
This means when I ran the uninstalls, everything did uninstall and unroot but the TWRP install must not be very clean (I don't think it's being maintained anymore for most devices). So I need to try and find where this app is located and remove it manually before I run the recovery again. If I solve this I'll post back.
BlazzedTroll said:
So I was trying to follow some other suggestions and it seems like maybe the device is actually not rooted anymore.
There is no SU file located in system/bin or system/xbin.
When I download something like "Root Checker" it gets stuck verifying the root.
I tried to use apps like rashr and flashify to flash a stock recovery and neither app will load properly suggesting no root access.
This means when I ran the uninstalls, everything did uninstall and unroot but the TWRP install must not be very clean (I don't think it's being maintained anymore for most devices). So I need to try and find where this app is located and remove it manually before I run the recovery again. If I solve this I'll post back.
Click to expand...
Click to collapse
You don't have root access, since you uninstalled Magisk. TWRP has it's own root, so while booted to recovery you can still do root stuff...
The only way to restore the stock recovery is to flash the boot image to your device.
And TWRP is pretty much the only maintained custom recovery for most devices...
Just a small note: this demonstrates the issues with using toolkits... It's just to click away and you never really learn how things actually works. Can bite you in the bee-hind when things go south.
Didgeridoohan said:
You don't have root access, since you uninstalled Magisk. TWRP has it's own root, so while booted to recovery you can still do root stuff...
The only way to restore the stock recovery is to flash the boot image to your device.
And TWRP is pretty much the only maintained custom recovery for most devices...
Just a small note: this demonstrates the issues with using toolkits... It's just to click away and you never really learn how things actually works. Can bite you in the bee-hind when things go south.
Click to expand...
Click to collapse
At this point I've just ordered the RMA replacement and I'll send it in. Hopefully those at Google are able to verify that the hardware malfunction is entirely unrelated to the root and they still honor the warranty. If the USB hadn't failed, I would easily flash back to stock as you have suggested. It's a fairly trivial action.
I agree somewhat with the idea that toolkits can be problematic in this way. There was quite a bit involved in running through the toolkit, it wasn't that One-Click root/jailbreak type stuff. I issued all of the commands over ADB and was fairly knowledgeable about what actions I was performing. This issue lies in this toolkits maintenance. The latest update to TWRP removed a ton of features and I'm unable to find the other version. Magisk was fully uninstalled as expected. TWRP did not make it clear that the flashed recovery would in fact contain was is essentially an ad for their toolkit. The placeholder app, as they call it, is literally just an ad that pops up when your recover that says "Don't forget to install us!". You can't even remove that file from the recovery partition, you must reflash to remove it. So the problem isn't just that you don't learn how it works, it's that you aren't forced to go through the changes with a fine-toothed comb as you would creating your own recovery. Had I created my own recovery I would have left it stock so that in the event of a failure such as this you are returned to factory stock without any changes except the unlocked bootloader. I guess in the future I'll have to do this myself. I did take the easy way out and just run the defaults from the toolkit in most cases.
Thanks to you and the others who threw in some helpful suggestions.
For anyone stumbling across this in the future, the problem is a 'semi-rooted' recovery can't be flashed without USB transfer capabilities. The solution is to RMA the faulty hardware hopefully. They should be reflashing all phones they get after repair/refurbish anyway.
Best Regards
For future reference...
BlazzedTroll said:
Greetings,
I recently got a Pixel 2 XL and the first thing I did was try to root with SuperSU and TWRP. I had some issues with it and someone suggested Magisk. It worked great and I was able to update from the 8.0 to 8.1 with root. I kept up with the latest Magisk installs until the past week or so.
My phones USB port appears to have failed partially. Luckily I can still charge, but there is no way to see the device storage from a PC. Support has defaulted, after much troubleshooting, to an RMA solution with a refurbished phone. Thankfully, this seems to be covered by warranty and isn't going to pose a cost issue. However, through the troubleshooting I was forced to do a factory reset. I looked up some information regarding factory reset with rooted devices. I cannot find the exact tutorial I followed or thread I gained the how-to information, I'm not sure which it was. I simply searched how to factory reset magisk 8.1 device. It was quick and most of the stuff I find now has the same information.
Open Magisk, uninstall. Open TWRP, uninstall. Device Settings, Factory Reset. Easy
This seemed to have worked. I didn't run into any locked hardware issues thankful because I don't have USB to really flash something to it.
Before I continued, prior to attempting the reset I fully backed up the device to my computer using ES File Explorers FTP transfer over the wifi. This was great, lots of photos were able to be saved with no hassle. I copied the entire root directory and have it backed up.
The problem with the reset is that while Magisk remained uninstalled, TWRP has a basic file installed that upgrades to the full app. I still have root, which would have been nice, except I still need to unroot and go back to factory settings before I can send this device in.
Before I make a mistake moving forward, I want to find the best way to unroot, (preferrably relock the boot also), and return to factory stock as it was the day I got it so I can return in it in the best state I can.
I am running rooted android 8.1.0 Pixel 2 XL with kernel 4.4.88 if the helps. When I reset to factory defaults TWRP remains installed and root persists. I cannot connect via USB and run android dev tools to flash anything directly. How can I restore this device? I should have all original kernels backed up. During the root process I remember them saying to copy the old ROMs first and I performed every step exactly. I do have access to move files to and from the device via WiFi. Is it this even possible?
PS, does anyone think the firmware and rooted install could be the problem with the USB? It seems entirely like failed hardware to me but the troubleshooting was extremely thorough and seems to indicate softare/firmware are likely to be the issue instead of the hardware issue that was determined. Could this still rooted device have corrupted the USB transfer? It seems I should do my best to rule this out as well, more so than just giving them a factory reset device. I'd rather keep my phone if it can be fixed easily, than obtain a possibly low quality heavily used refurbished model.
Regards
Click to expand...
Click to collapse
Try downloading a stock Fastboot Image for your device then unzip it, collect boot.img, then flash just the stock boot.img from TWRP. Should solve the issue upon the following reboot with no more TWRP or root. If youre on magisk or systemless SuperSU. Not locking the bootloader though lol that's hopeless without usb function unless it's possible to lock bootloader using the terminal command with an WiFi ADB app from another device then follow with "adb reboot bootloader", "fastboot boot TWRP.img", then flash stock boot.img from there. I'm just spitballing the second one lol, but if it'll make it to the TWRP part successfully it should work in theory unless the WiFi ADB connection can't make it past reboot which I've never tried. Should probably get an unlock box like NCK Box Pro or whatever supports your device and you'll always know if the port is ****ed or not and flash back to full locked stock with the box if it isn't. It's what I do now. Handy little ****ers lol.
I am not an expert user but have always been able to root and install custom ROMs over the past years to devices including ASUS A500, Nexus 4 and 7, Samsung P605, Note 4, and note 8.
However, I have obviously done something to my Note 8 and can no longer install TWRP or SU or anything in fact. This happened after I moved from the official Samsung Pie release to the Lineage 17.1 (Android 10) which I ran successfully for a couple of weeks; but I missed the Samsung DEX support and I used this heavily for streaming to my non-smart TV. So whilst I loved the Lineage experience I moved back to the standard Samsung Pie.
This caused a couple of problems in that I could no longer use some of the Samsung apps since the device recognised that it had been rooted and it burned in the warranty bit, and Samsung ell me that the only way around this on the note 8 is to replace the processor board; and this seems to be correct.
So, I now want to go back to Lineage 17.1, since it was stable and I have lost interest in anything Samsung after this experience.
I can no longer install TWRP (or SU or Magisk) to allow me to root and install Lineage. I have done everything on all the helpful forums, including wipes etc, followed install instructions to the letter (many times) and whilst the loading of TWRP via Odin goes through the motions and completes properly, when I try to go into it all I get is the regular Samsung boot stuff. I have tried SU etc via an SD Card but these always give errors, I have tried the no verify software but it too won’t install.
Many attempts have been made to load TWRP and sometimes it screws up the phone but I can always load the latest Samsung software via Odin; here is the latest Samsung software I am using:-
- AP_N950FXXSADTC4_CL16983991_QB29943831_REV00_user_low_ship_meta_OS9.tar.md5
- BL_N950FXXSADTC4_CL16983991_QB29943831_REV00_user_low_ship.tar.md5
- CP_N950FXXSADTB1_CL1300388_QB15232239_SIGNED.tar.md5
- CSC_OLN_N950FOLNADTB1_CL16983991_QB29490845_REV00_user_low_ship.tar.md5
I would appreciate any help whatsoever. Perhaps someone has done the same thing? Maybe I am screwed!
@neilgoodyer
Did you remember to turn OEM unlock on?
When the phone is in download mode, does it say "prenormal" anywhere? If it does, you won't be able to flash TWRP until that disappears, I don't know the exact way to get rid of it, but I usually sign in to my Samsung account on the phone, then check for an update which registers the device, then it soon disappears for me (prenormal)
stonedpsycho said:
@neilgoodyer
Did you remember to turn OEM unlock on?
When the phone is in download mode, does it say "prenormal" anywhere? If it does, you won't be able to flash TWRP until that disappears, I don't know the exact way to get rid of it, but I usually sign in to my Samsung account on the phone, then check for an update which registers the device, then it soon disappears for me (prenormal)
Click to expand...
Click to collapse
Thanks for the advice:
Yes, OEM unlock on. In fact it seems to turn it on automatically when I invoke developer mode. When in download mode I don't get "prenormal" anywhere. The only somewhat negative comment on that screen is the the warranty count is 1 because I previously loaded Lineage 17.1 Odin completes normally indicating all was well but still only the Samsung bootloader.
Samsung Account is working and I am always able to get my backup loaded whenever I have to reload the current Samsung software,.
It's got me bamboozled and without TWRP I can't do anything......, can't even load a previous custom rom and work my way forward from that. I did think about a previous Samsung software release for the Note 8 Exynos but the "archive" at sammobile doesn't show any.
neilgoodyer said:
Thanks for the advice:
Yes, OEM unlock on. In fact it seems to turn it on automatically when I invoke developer mode. When in download mode I don't get "prenormal" anywhere. The only somewhat negative comment on that screen is the the warranty count is 1 because I previously loaded Lineage 17.1 Odin completes normally indicating all was well but still only the Samsung bootloader.
Samsung Account is working and I am always able to get my backup loaded whenever I have to reload the current Samsung software,.
It's got me bamboozled and without TWRP I can't do anything......, can't even load a previous custom rom and work my way forward from that. I did think about a previous Samsung software release for the Note 8 Exynos but the "archive" at sammobile doesn't show any.
Click to expand...
Click to collapse
When you flash TWRP with Odin, does it pass or give any error code? Have you tried a different TWRP version, maybe the one you have has become corrupt somehow.
stonedpsycho said:
When you flash TWRP with Odin, does it pass or give any error code? Have you tried a different TWRP version, maybe the one you have has become corrupt somehow.
Click to expand...
Click to collapse
Thanks, Yes it completes with a PASS. I have tried several versions of Odin, all appear to work but same results unfortunately.
neilgoodyer said:
Thanks, Yes it completes with a PASS. I have tried several versions of Odin, all appear to work but same results unfortunately.
Click to expand...
Click to collapse
Tried a different TWRP?
Like you said above, I too am bamboozled too.
neilgoodyer said:
Thanks, Yes it completes with a PASS. I have tried several versions of Odin, all appear to work but same results unfortunately.
Click to expand...
Click to collapse
Have you tried ticking on the format option in odin so it deletes everything before flashing the firmware? I would have tried to flash just twrp with the format option ticked to see what happens. I would do a little research before just trying to do that though.
Edit: With the phone connected to your PC using command prompt (in your adb location) type in fastboot boot recovery.img and see what happens.
MrMike2182 said:
Have you tried ticking on the format option in odin so it deletes everything before flashing the firmware? I would have tried to flash just twrp with the format option ticked to see what happens. I would do a little research before just trying to do that though.
Edit: With the phone connected to your PC using command prompt (in your adb location) type in fastboot boot recovery.img and see what happens.
Click to expand...
Click to collapse
Thanks, I will research further that suggestion with odin. I did try doing things with adb, however, it doesn't seem to work with the samsung note 8 (mine anyway).
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. After reading some people on forumes saying that this device might not have a locked bootloader, I finally thought that this tablet did not have its bootloader locked. Then I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
I finally used heimdall and was able to flash all the partitions with the stock images. Now I am back in stock version. I would like to flash a TWRP recovery.
Can someone tell me if I have to unlock the bootloader with this device ? If it is, how can unlock it ? I can not find anything in the settings developer section, and can not use a call number input in order to enter a system code as it's a tablet. Do I have to wipe something from the stock recovery in order to see it ?
Thanks for your time.
Hi -yo-.
You don't need to do OEM unlock as this device is so old.
Also twrp-3.2.3-0-lt02ltespr.img is NOT for this device.
For recovery look from here and for ROM here.
Thanks jonezy82 for the answer. Indeed, I figured all of that out.
I decided to get it back stock and not trying to flash anything custom.
Thanks for your time.