Related
HI I have just been trying to return to stock my XT1570 Motorola X Style.
Originally i unlocked the bootloader and rooted the original 5.1.1. software.
Later the OTA update came out and i cant get it as the phone is rooted.
I did have backups but have lost them now.
The boot loader is intact, the TWRP recovery is there and I can access it.
I flashed a new system using fastboot this system "fastboot_clark_retcn_ds_user_5.1.1_LPH23.145-7_7_release-keys-cid11-retcn_CN.tar" which i believe should be the correct one for China.
The phone boot normally, the warning about unlocking the bootloader and then the motorola graphics, but when all that is done the screen is just blank, the screen is obviously on, as you can see the back light, but it is in the totally black state.
Anyone got any ideas what has happened there.
I have tried flashing other roms for XT1572 and XT1575, however while they work to an extend, obviously some of the internals for the XT1570 are different, modem for instance.
Some expert help would be greatly appreciated.
Hey all......I created a thread awhile back when I borked my phone trying out a new treble rom that was supposed to be so easy even a nOOb could flash it, and it ended up messing up my phone to the point where the only way for me to get it back was to follow the thread to disassemble the phone and short the chip out.
Then, the screen was not responsive on ANY rom I flash except for MM and it worked with any up to B29. I tried a few times to upgrade all in vain but I was always able to flash MM B29 and have it work again.
Flash forward to last night and my itchy trigger upgrade finger did it again and I attempted to flash the Oreo from ZTE. It flashed fine but, again, no responsive screen. I thought well, maybe I could try Nougat again and I flash many different versions and in different ways (used miFlash, EDL tool, MiFavor recovery, twrp) and all resulted in the screen not being responsive. Sigh, so I flashed MM B29 but now it will not detect any sim or even allow wifi to be turned on.
I have tried multiple times to reflash MM B29 using all the different ways above and even went back and forth between roms. I tried the original way most of us first unlocked the bootloader and flashed through all those stepped zip packages from B20 to B29 and still nothing. I finally used twrp to erase/format all data and made certain the partitions were formatted as ext4 and tried again, still no sim.
I realize that my imei is not showing and even tried a program to flash? that to the phone.
NOW, what needs to be said is during ALL of this flashing the phone signal/sim DID show......yes.......the sim DID WORK......when I flashed anything other than MM B29. LOL. Of course, the issue is none of those roms allow the screen to work.
Please, if anyone can help I would appreciate it very much. I'm thinking by flashing the Oreo from ZTE it may have changed something that the MM B29 rom is not changing to allow the phone to read the imei/sims.
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps ?
Syberclone said:
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps
Click to expand...
Click to collapse
I appreciate the suggestions. Unfortunately, the DFU tool doesn't seem to work for me as it remains listed as Disconnected even after choosing the correct port.
I have always flashed the MM B29 EDL rom (A2017U_B29_MARSHMALLOW_FULL_EDL) that contains the correct modem. As I said, it always worked before.
As far as checking APN/network settings, well, there are none to check because the sim is not detected so all of those choices are greyed out. The signal bars fr both sims are blank in the notification area and of course wifi does not turn on.
I just finished another round of trying different roms to flash including LOS 15. LOS came up to the welcome screen (just like all the others) AND the AT&T logo with LTE full signal bars showing. Again, the screen does not respond to touch so it's all useless. I am at a loss as to why flashing MM B29 is no longer working for me.
Stop using guides mentioned in Axon7 thread,or stop listening to other users.Only thing i see here are bricks.
Probably you have hardware fault
The Axon 7 has been the worst phone for being bricked.
I've flashed ROMs on HTC's, Motorola and Google phones all without problems.
There are way too many packages and bootstacks etc, etc that cause problems and confusion.
So I wouldn't say don't follow threads or users advice.
My advice is research, research and research some more.
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
djprez said:
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
Click to expand...
Click to collapse
Did you installed a vendor partition?
Predatorhaze said:
Did you installed a vendor partition?
Click to expand...
Click to collapse
I am not certain. If the Oreo update that I downloaded directly off the ZTE site has one, then yes. If that is the cause, how would I modify it?
@djprez: To my knowledge, ZTE's official B12/B20 do not have a vendor partition. ZTE will almost certainly never add Treble support for the A7, if they are going to do so then now is an ideal time, since the A7 is an end-of-life device and no longer being manufactured.
I got LS997 that was not completely unlocked (Sprint support confirms unlock status but phone did not receive unlock command, and i got no sim card and no previous owners name to re-initiate ota-unlocking process)
First thing i did - i used pathed LGUP and dirtysanta rooted my phone.
Suggested 995 kdz rom was vibrating like crazy (as described in dirtysanta guide) but i got root and started experimenting further.
Than i flashed rootable 996 kdz, rooted, had no vibration problem but got static boot issue, ok, installed mk2000 kernel, no static - all good but still not enough.
LOS16 = gsm/lte unlocked but battery was drained in 5 hours with screen turned off and no camera, got back to 996, rooted, super rom, all good but LTE not operating for some reason. Really enjoyed stock functionality (camera, seconds screen) and decided to get back to stock system.
HOWTO: Root LS997 up to ZV7, did it all, started flashing available 'stockish' roms one by one [this, and this], so there goes bad stuff.
At this moment i was still being able to boot into twrp, so i didn't really notice that phone was bricked, those stockish systems was just hanging in LG logo for hours without any progress. ok, found another one stock ls997 rom in dirtysanta root post, flashed it - and nothing, phone still stuck at lg logo.
LGUP flashing routine that was always helping me recover, now if fully completes partition_dl process but results are the same - lg logo for hours without anything happening, except vibrator motor starting to work on power up on Verizon firmware version and no vibro on 996 variant (as it sould):
996 kdz - stuck on logo
996 kdz- stuck on logo
flashing everything i got from lg-firmwares.com:
US99610g_00_1216 - stuck on logo
US99610f_00_1205 - stuck on logo
US99620f_00_1120 android 8.0 - stuck on logo
VS99512A_06_1114_ARB00 - stuck on logo
download couple more variants and still nothing, phone stucking in lg logo
so how badly i bricked it? is there any method of recovering that i am not aware of?
There is an older thread on returning the LS997 back to stock that may help.
C D said:
There is an older thread on returning the LS997 back to stock that may help.
Click to expand...
Click to collapse
Yeah, thanks, been there.
Unfortunately i'm not meeting 2 of 3 prerequisites:
- Your device needs to be able to boot into TWRP and fastboot mode
- You need access to a computer to run ADB commands to the phone
There are no more twrp presents on device because of kdz uploads from LGUP, i was thinking that it was recovery and aboot partitions that was messing up my system.
And there is no bootable system on device to turn on usb debbuging to run ADB commands as only thing i get is boot logo, fastboot are also locked to 995 or 996 (whatever version i've uploaded last from LGUP, and they are not unlockable because LG recognizes original LS997 hardware identification and refuses to give me unlock.img.
As i get it - the only thing that can tinker with my device is something that can get same hardware access as LGUP (laf is still operational or idk, maybe not, but it should be getting everything up and running but that is not the case anymore for some reason)
So you are saying that LGUP can still see the phone but ADB can't. Did you by any chance do a full system dump of the phone on LGUP before the whole DirtySanta procedure in the beginning? I wonder if those files can help getting things back on track. Not sure if they are device-specific, but I did make a dump of my own LS997, so if you think there's something useful there, let me know, and I can upload the files somewhere.
C D said:
So you are saying that LGUP can still see the phone but ADB can't. Did you by any chance do a full system dump of the phone on LGUP before the whole DirtySanta procedure in the beginning? I wonder if those files can help getting things back on track. Not sure if they are device-specific, but I did make a dump of my own LS997, so if you think there's something useful there, let me know, and I can upload the files somewhere.
Click to expand...
Click to collapse
Yes i did full LGUP backup at first system state, but nature of this backups makes them pretty useless in this system state - because they are just images of partitions.
Only software that can write directly to those partition may be able to utilize those backups, there are a lot of post on this forum describing TWRP routine for making update packages based on LGUP backups.
So unfortunately there is only LGUP, but it only can make backups but can not restore them as it uses some special file format (KDZ) that containing some dll's and data files (like glued partition images with special info of where to put what) and i didn't find a way to make my own KDZ files from backup images.
I'm now getting another idea - that this can be a blowed fuse in CPU ARB protection mechanism, if anyone has experienced ARB 1 please confirm that system should be in this state in case of ARB error
Hello. It's been a year since release of this tablet, so Is there any custom roms available for the SM-T290 (Galaxy Tab A 2019 8 inch")? Like Lineage OS?
Thanks.
carlm3 said:
Hello. It's been a year since release of this tablet, so Is there any custom roms available for the SM-T290 (Galaxy Tab A 2019 8 inch")? Like Lineage OS?
Thanks.
Click to expand...
Click to collapse
Hello friend, unfortunately there is only one rom, made by a member of the forum, an improved version of the stock, but you can try a rom via treble, since our device supports updating by this method, I am testing some myself.
I have a T295 (the only difference is that is has mobile data afaik) and would also like to get Lineage on it, since the stock rom is extremely slow, even with very few apps, disabled animations and whatnot.
How would installing via Treble work on Samsung devices, especifically this one? @Reick7
EDIT: nvm, found it, seems to support both T290 and T295 as in: https://github.com/phhusson/treble_experimentations/wiki
I'm going to try and install it and report back!
Fusseldieb said:
I have a T295 (the only difference is that is has mobile data afaik) and would also like to get Lineage on it, since the stock rom is extremely slow, even with very few apps, disabled animations and whatnot.
How would installing via Treble work on Samsung devices, especifically this one? @Reick7
EDIT: nvm, found it, seems to support both T290 and T295 as in: https://github.com/phhusson/treble_experimentations/wiki
I'm going to try and install it and report back!
Click to expand...
Click to collapse
well, i haven't tested it for a long time, as i've passed the tab to someone else, but the one i tested doesn't work as well as i expected, it was the Resurrection Remix Q
@Reick7 Couldn't get it to work, sadly.
I tried to install Treble but it hangs on the initial boot screen aka "Samsung Tab A" + unlocked bootloader screen, never gets past that and reboots indefinitely.
I tried A, A/B and all sorts of things in TWRP like wiping, resizing and whatnot.
What could be the cause?
Thanks in advance.
Tried downgrading to stock Android 9.0 and flashed everything (BL, AP, CP and CSC), let it boot, shut it down, then put TWRP with vbmeta on it and flashed the LOS GSI (A only) with it.
TWRP succeeded sucessfully, I reboot and it's stuck on the bootloader screen with the unlocked warning, reboots, gets a black screen, reboots, ...
I really have no idea.
Fusseldieb said:
Tried downgrading to stock Android 9.0 and flashed everything (BL, AP, CP and CSC), let it boot, shut it down, then put TWRP with vbmeta on it and flashed the LOS GSI (A only) with it.
TWRP succeeded sucessfully, I reboot and it's stuck on the bootloader screen with the unlocked warning, reboots, gets a black screen, reboots, ...
I really have no idea.
Click to expand...
Click to collapse
hi friend, when we install a stock rom we need to activate developer mode and OEM unlock before making any changes, otherwise your device will be locked.i believe that's the case for you, try to reinstall the same stock system you put in before the lockdown, and about gsi, unfortunately i don't know any that work well.
Reick7 said:
hi friend, when we install a stock rom we need to activate developer mode and OEM unlock before making any changes, otherwise your device will be locked.i believe that's the case for you, try to reinstall the same stock system you put in before the lockdown, and about gsi, unfortunately i don't know any that work well.
Click to expand...
Click to collapse
Yes, I did that. I could install TWRP, but that's about it. No GSI will boot, it doesn't even reach the android boot screen, it just shows the bootloader unlock screen and reboots.
Fusseldieb said:
Yes, I did that. I could install TWRP, but that's about it. No GSI will boot, it doesn't even reach the android boot screen, it just shows the bootloader unlock screen and reboots.
Click to expand...
Click to collapse
unfortunately GSI might even work at all, but the overall performance of the tablet won't allow it to be good, I remember testing some GSI when I had the tablet in my hands, nothing worked
Fusseldieb said:
Tried downgrading to stock Android 9.0 and flashed everything (BL, AP, CP and CSC), let it boot, shut it down, then put TWRP with vbmeta on it and flashed the LOS GSI (A only) with it.
TWRP succeeded sucessfully, I reboot and it's stuck on the bootloader screen with the unlocked warning, reboots, gets a black screen, reboots, ...
I really have no idea.
Click to expand...
Click to collapse
(I know its 1 year old) Tried to flash a newer version?
carlm3 said:
Hello. It's been a year since release of this tablet, so Is there any custom roms available for the SM-T290 (Galaxy Tab A 2019 8 inch")? Like Lineage OS?
Thanks.
Click to expand...
Click to collapse
To answer your question: Yes. This device supports both AOSP and GSI ROMs. If you are searching for a LineageOS ROM, there is one:
[ROM][OFFICIAL][13] LineageOS 20.0 for the SM-T290 (gtowifi)
WARNING: Samsung rolled out a new firmware update starting roughly at the end of January 2023. This contains bootloader version 4. From what we understand with SM-T295 bootloaders, this may or may not permanently lock you out from ever flashing...
forum.xda-developers.com
It does not exist that long yet, but it is an official LineageOS 20 ROM which works, I have installed it on my SM-T290!
greetings,
i try to make it short:
10month ago i bought 3x LG V20 H918 t-mobile brand from ebay, came from HK, same seller
same modell all same same only imei different, me living in germany.
1/3 i bootloader unlocked, rooted with magix, twrp and back to version 20H
up and running fine as EDC , no issues, until yesterday, when it died finally after fuqqed up screen.
so i took 2/3, same process, bootloader unlock, root magisk twrp etc. following the guide i used
to write as simple as possible back in the day. i restored the backup i made with phone 1/3, thing up and running in about 1h.
but it shows simlock ! i have some possibilitys left, ill try lineage OS etc maybe different kernel,
but since im by far no pro with android, my possibilities are limited. did i do s.t. wrong?
i tried different versions of twrp, since it showed the "can not decrypt" screen many times, i tried different versions of stock rom,
i tried using the backup from phone 1/3 and clear install of stock rom, wiped data/system/everything (except micor sd)
always simlock.
any ideas are much appreciated, why does phone 2/3 has simlock, while phone 1/3 was up without any issues :/
thx
for now, i exchanged the mainboards (mainboard from phone 1/3 --> phone 2/3) up and running.
from phone 1/3 only screen was destroyed, mainboard was still fine)
not the smoothest solution but ok for now.
i contacted t-mobile US they seemed to be a little overwhelmed by my concern.
it seems with normal methods there is no chance of getting rid of that simlock, since its supposed to be on a hidden partition on internal memory, and there is just no way to access this one, except with the unlocking code.
when trying to check IMEI from phone 2/3 and enter *#61# (?) it showed IMEI 0....
if s.o. has any ideas on how to extinguish scumsimlock, still much appreciated.