[Q] How do inject/enable Sprint HiddenMenu.apk in Custom Rom - Android Q&A, Help & Troubleshooting

Hello,
Backstory:
So here's the deal. My provider (Virgin Mobile Data Done Right) changed my phone number, and asked me to update PRL to make it work again.
I don't have a working stockrom backup - neither does anyone else. Neither does Kies, I've spent over two weeks researching this and working with various intermediate developers so don't even go there. I just want to work on making a custom rom do the PRL update.
It seems the easiest way to do this is simply to inject all needed files into the custom rom, but so far I've not had any success in finding the working files.
Things that are not solutions:
1) Flashing System via Odin or Hiemdall, multiple people including myself can confirm that Virgin has somehow blocked this method.
2) Flashing stockrom or Touchwiz KitKat via TWRP (anything below 5.1 lolipop fails to boot, gets caught in hard loop).
(On top of that, you loose baseband because no one on planet earth has a Virgin Mobile Data Done Right tri-band phone. It's a rare OH1 modem. I was fortunate enough to make a backup of modem.bin, before running flash attempts overtop of my custom rom. No thanks to the many fools who told me otherwise)
3) Paying developers to fix the issue. I gave one a brand new phone and another a few bucks, neither of them know how to fix it.
4) Giving up.
Developer Info Needed:
So what I'm looking for is people experienced with HiddenMenu.apk that can give me some tips to get it working on d2refreshspr (Triband) OctOS-L. OctOS-MM does NOT work, never did. OctOS is very aware of the issue but they are probably just as clueless at this point and aren't interested in putting proprietary blobs in their rom. People like @digiblur who have all but decompiled the thing would probably know how it works.
To my knowledge, I need to find the following files:
OmaDmclient.apk
UpdateSettings.apk
HiddenMenu.apk
These files have to be able to run on Lolipop, and they have to be branded for Sprint, preferably for the Galaxy S3 triband, but I'm not sure it exists so well have to make do. I tried injecting the packages from some older KitKat roms and they crash.
Once again, the only rom that ever worked properly on this phone is custom rom OctOS-L, so others are not an option.
Alright devs, let me know some tricks! No noobs.

I have located the stock Sprint KitKat version of HiddenMenu for the S3 tri-band. Unfortunately, I have been unable to execute it on the custom rom as of yet. It does not appear in any of the activity launchers, and the dial-code is not working. I've manually put this into /system/app/HiddenMenu/HiddenMenu.apk
APK for reference:
http://www.fileconvoy.com/dfl.php?id=g8fd96be733233c149998319870a8759deb41050a7
SHA512: dc9a5e06200637da2b1e5c71d16af239a80fa44f7067ab83efa45ac59b9df0016de2b99d97e0cfc023a3ac4be91d4dd6f945303c2184d5232476f0c445440d55 HiddenMenu.apk.zip
- Pulled from:
L710TVPU0AOH1_L710TSPT0AOH1_L710TVPU0AOH1_HOME.tar.gz --> system.img.ext4
(Note that this LT710T Odin dump foolishly contains the NF4 modem, NOT the OH1 as it's name implies)
Without anyone's help, I will continue to google this endless endeavor. :good:

Ran apktool on this thing. Inside the apk of the HiddenMenu it mentions the NF4 variant. Not sure if this is why it's not working or not.
Also tried recompiling it by changing AndroidManifest.xml to add android.intent.category.LAUNCHER as an option so that it appears.
No love. I can't get HiddenMenu to come up.
Ideas?

For anyone encountering this issue. I never got HiddenMenu to work. Not even on a TouchWiz rom, but I found another way.
Look here: http://forum.xda-developers.com/showpost.php?p=67026377&postcount=6
This was way more complex than it should be. Proprietary APK makers should be ashamed.

Related

[Q] SGS3 - Error: “Not Registered on Network”

Error: “Not Registered on Network”
SGS III have JB 4.1.1 (I9300XXDLI8) ROM/baseband, rooted with CF-Root/TWRP.
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
I downloaded and flashed Omega 32.1, thinking that I can always go back if something doesn’t work out. Anyway, long and the short of it, when I restored my S3 through TWRP restore, I found out that it isn’t connecting with my mobile network i.e. Warid Tel with the error “Not Registered on Network”.
By the way I also happen to have the factory unlock code for this SGS3, but unfortunately all the USSD codes I've tried to enter it, doesn't work.
Although, I guess I can take it back and get it re-unlocked again, but that isn’t going to allow me to install custom roms.
Can anyone guide me how to fix this situation, any tips, help, will be highly appreciated.
Regards
Babur
Megneto said:
Error: “Not Registered on Network”
SGS III have JB 4.1.1 (I9300XXDLI8) ROM/baseband, rooted with CF-Root/TWRP.
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
I downloaded and flashed Omega 32.1, thinking that I can always go back if something doesn’t work out. Anyway, long and the short of it, when I restored my S3 through TWRP restore, I found out that it isn’t connecting with my mobile network i.e. Warid Tel with the error “Not Registered on Network”.
By the way I also happen to have the factory unlock code for this SGS3, but unfortunately all the USSD codes I've tried to enter it, doesn't work.
Although, I guess I can take it back and get it re-unlocked again, but that isn’t going to allow me to install custom roms.
Can anyone guide me how to fix this situation, any tips, help, will be highly appreciated.
Regards
Babur
Click to expand...
Click to collapse
Check your IMEI number.
Has it changed?
eggman89 said:
Check your IMEI number.
Has it changed?
Click to expand...
Click to collapse
No it hasn't changed.
The problem was the original "soft unlock"
Megneto said:
...
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
...
Click to expand...
Click to collapse
The problem was the original "soft unlock" - some of those (I believe even some early that were made by NSPro) are rather poor and are based on flashing a special modem binary. You will be able to fix it if you search around for the fix posted by Ariza (even if I believe something happened to the original post).
I am trying to find the fix by Ariza, but so far nothing has turned up. Also, if I search for the user "Ariza" it doesn't help either. Do you remember exact member alias?
Also, does that fix result in permanent resolution of the issue?
Or, is it better to get rid of this SGS3, and get factor unlocked version?
Thanks for your help and patience.
Edit:
I forgot to mention in OP that it correctly identifies the network when I check Status of the device.
Edit 2:
I was able to get hold of the guy who actually did the 'soft' unlocking in the first place, and he confirmed that it was done using NSPro (through Dongle) and is willing to do it again.
But the issue is, it will restrict me to JB 4.1.1 and I can't install any custom ROM.
Hmm ...
Megneto said:
I am trying to find the fix by Ariza, but so far nothing has turned up. Also, if I search for the user "Ariza" it doesn't help either. Do you remember exact member alias?
Also, does that fix result in permanent resolution of the issue?
Or, is it better to get rid of this SGS3, and get factor unlocked version?
Thanks for your help and patience.
Edit:
I forgot to mention in OP that it correctly identifies the network when I check Status of the device.
Edit 2:
I was able to get hold of the guy who actually did the 'soft' unlocking in the first place, and he confirmed that it was done using NSPro (through Dongle) and is willing to do it again.
But the issue is, it will restrict me to JB 4.1.1 and I can't install any custom ROM.
Click to expand...
Click to collapse
The thread was this:
http://forum.xda-developers.com/showthread.php?t=1918601
(in a post towards end I have some of the stuff from the forum where you had to register in order to get the files, and you might still recover some of those links - apparently those are patched versions of the corresponding stock modems which no longer check some of the information from nv_data.bin; you will need to add that modem after each major ROM change).
If you only plan to use 4.1.1 and not upgrade then NsPro should be OK, otherwise you either need a "subscription" to the services of that guy
Thank you for the help. I will go through that thread soon.
I've have also looked at this thread http://forum.xda-developers.com/showthread.php?t=1705650 by UpInTheAir. I have installed android SDK for Winx64 and successfully extracted modem.bin (as a test). I think I'll get the phone back to that guy, so he can patch the modem with NSPro again, once that is done, I'll extract the modem, repackage it so I can install it with CWM and test whether that can eventually help me in experimenting with other ROMs.
I will keep you posted on my progress.
Again thank you for your valued help.
Kind regards.
Babur
Having tried the method mentioned in my previous post, I finally gave up and took the phone for repair.
What transpired from thereon is interesting and confusing. As according to Mr. Repair 'serial number and IMEI' were repaired, nothing more. In fact I extracted the modem and compared it with the one I have, they are exactly same no patch applied.
However, both IMEI and serial number were showing correctly prior to the repair, and even after repair they are same (I double checked those with the original invoice/phone box etc.). So I am not sure how they were damaged when they were showing correctly.
Update:
I've sold the unit question, as I felt not to take any more risks with it, and bought an factory unlocked SGS3. Hopefully I will not face any problems with playing around with custom ROMs from hereon in.
Thank you and kind regards to all.
Babur

[Q] Rom opinion/help?

My stats: Fairly comfortable with computer and other forms of tech, but have only recently began diving into the Android system. I have limited development/programming experience, however, I'm not a novice or noob to it but definitely not advanced. Importantly for those willing to help I understand most terminology and can follow instructions. Thanks in advance.
Phone Stats: AT&T Samsung Galaxy Note SGH-i717
Android Version: 2.3.6 (Gingerbread)
Baseband Version: i717UCLF6
Kernel Version: 2.6.35.11
Build number: GINGERBREAD.UCLA1
Root Access: Yes
Stock Rom: Unsure, bought online.
Carrier/Service Provider: Straight Talk (U.S.) Phone was previously used on the AT&T network exclusively, and done so with an AT&T provided SIM card. After I purchased it, I ordered a new SIM card from Straight Talk (U.S.) and reprogrammed the APN settings under their instruction in order for my phone service to work correctly, and have had no problems with that.
I can't stand being on Gingerbread any longer. I guess, since my phone is an AT&T phone but I'm using it through Straight Talk I can't get any of the OTA updates. I've tried downloading the OTA's several times, both, prior to and post Root access without success in either case.
So here are my questions:
1. Am I doing something incorrectly which might be keeping me from getting OTA updates? Please remember, I've tried downloading the OTA's several times both with and without Root Access and the conclusion is the same each time: "No Updates Available At This Time. Your Phone Appears To Be Up To Date. Try Again In 24hrs."
2. Is my only option at this point to manually update to a newer firmware? If so, should I update to a newer STOCK version or a custom ROM version?
3. If a manual update is the option, after reading my above outline of my own experience with the Android system, what would be way to go? Simple, not overly complex yet doesn't assume the user is either a complete moron or can write code in his sleep. I've checked into a couple of options. Rom Manager seems like it would be a nice route to go, but in the Recovery Setup portion I basically get told I can't use that application because my specific device isn't supported.
I checked out GooManager and, unless it's just me, it seems like it's an app that likes to do all the work without telling you what it's doing exactly, but when it does ask me or tell me information, I'm not always sure how to answer or react to it's warnings.
Plus, I've noticed that sometimes when downloading a ROM, sometimes I have to "flash" the gapps myself and other times I don't.
4. Is it easier to download everything separately and apply them one by one, for example the ROM then gapps then Kernal...etc? Or look for something that has it all in one package?
I have a laptop in which I can download/transfer programs and apps between it and my Note so download space and internet access isn't a problem.
Also, it most likely isn't information that is going to help in anyway, but I live in Oklahoma, United States of America.
Thanks for all the feedback...UnluckyOnion
I'm not answering these in any specific order,
As I kinda just sped read thru most of it...
Since you're rooted, or know how to, goomanager is superior to Rom manager.
It supports this device and has a current version of twrp to install, instead of an outdated cwm.
Just use it to install recovery, then boot your device into recovery and use that. Not the app. You'll be provided with much more information and this is the preferred way of flashing.
Official Updates are always "manual" either with a less than user friendly program called kies, or with a less annoying way (which you may be familiar with seeing as you've rooted) ODIN. Both pc programs used with the phone in download mode connected with usb cable.
Gapps are only needed to flash separately with an aosp based Rom as it's against Google's T.o.S. to include them in am entirely aftermarket compiled firmware, however if it's a Modified version of a stock based Rom (in this case TouchWiz) they can be, and thusly are, included within.
Official or custom is up to you really.
If official..just grab the .tar and flash it with Odin.
If custom, obtain a custom recovery either the way i mentioned above or downloading a .tar of twrp and use Odin to flash that.
Once you have a custom recovery, you'll simply be able to flash a Rom from there.
Roms include a kernel, if you want to use a different one than what is included, that would be flashed after the Rom.
After flashing you'll have to input your carriers apn settings in again.
studacris said:
I'm not answering these in any specific order,
As I kinda just sped read thru most of it...
Since you're rooted, or know how to, goomanager is superior to Rom manager.
It supports this device and has a current version of twrp to install, instead of an outdated cwm.
Just use it to install recovery, then boot your device into recovery and use that. Not the app. You'll be provided with much more information and this is the preferred way of flashing.
Official Updates are always "manual" either with a less than user friendly program called kies, or with a less annoying way (which you may be familiar with seeing as you've rooted) ODIN. Both pc programs used with the phone in download mode connected with usb cable.
Gapps are only needed to flash separately with an aosp based Rom as it's against Google's T.o.S. to include them in am entirely aftermarket compiled firmware, however if it's a Modified version of a stock based Rom (in this case TouchWiz) they can be, and thusly are, included within.
Official or custom is up to you really.
If official..just grab the .tar and flash it with Odin.
If custom, obtain a custom recovery either the way i mentioned above or downloading a .tar of twrp and use Odin to flash that.
Once you have a custom recovery, you'll simply be able to flash a Rom from there.
Roms include a kernel, if you want to use a different one than what is included, that would be flashed after the Rom.
After flashing you'll have to input your carriers apn settings in again.
Click to expand...
Click to collapse
Thanks for all the information and help...more importantly, thanks for taking the time. I have ODIN on my laptop and have always used it when needed but I saw a highly rated and positively commented Mobile version of ODIN in the Play Store that claims you can do everything from the convenience of your phone which sounds appealing, however it's kinda pricey, especially if it doesn't work. Would you recommend the mobile version or PC version? Also, I have been doing a lot of ROM and Root research as of late, and wondered something...Why so many different Galaxy Note's? It seems as though I have the least popular version with the most popular being from the Galaxy Note "N" series, specifically the N7000. If I download and use an application that says it's meant for the Galaxy Note N7000 and I use it on my Galaxy Note SGH-i717, what will happen? Nothing, something, brick, work perfectly, etc...?
The N series is not carrier branded and sold internationally, so naturally it's more popular compared to a north American variant.
DO NOT FLASH ANYTHING FOR THE N7000
IT WILL BRICK YOUR PHONE.
The international version has a different cpu, gpu and antenna, for north American LTE bands to work those key components needed to be different.
So I say again just to stress:
DO NOT FLASH ANYTHING FOR THE N7000
IT WILL BRICK YOUR PHONE.
As for Odin, you're either going to flashing a stock firmware, or if you choose a custom Rom, you'll only need Odin once to flash TWRP. Then all the rest will be done in recovery on the phone itself. No need for it after you've either manually updated to the latest stock rom, or flashed a recovery for use of custom roms
So... imo mobile Odin, though being nifty, is a bit pricey for how little you'll need it, whereas it's free on pc.
I don't think mobile Odin is even available for the i717. It's not listed in supported devices.
I tried installing mobile odin and it's not supported
Thanks for the reply. And an even bigger Thanks for downloading the app and checking. I admire sacrificing your own work just to help me out. So what about yourself? Would you suggest, advise or heed caution to anymore of my questions?
By the way, what are you two running?
As long as you read the op of threads and all other important posts that follow BEFORE ever touching your phone, I'd say try a custom Rom...if you decide you don't like any of them, you can Odin flash the stock jellybean firmware at any point.
I myself am running unofficial aokp compiled and posted by a fellow team member BlownFuze.
Oh yeah, how's it running? Nice and stable or crawling with bugs? Any key selling points?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I'm on the stock 4.1.2 release and rooted.
Everything works, no bugs, but battery sucks. Even after removing and freezing useless processes a stock rom will never be as light and battery friendly as a custom rom.
I just upgraded to the same version. Planned on rooting over weekend. Any success since your last post? Do you nave preferred Root method?
Thanks
Unlucky Orion
Use Odin to flash twrp
Newest version of twrp "should" Sr that you're not rooted and ask if you would like to do so within recovery before booting back into the os.
If not, there's links to an su.zip to flash in twrp for root.
studacris said:
Use Odin to flash twrp
Newest version of twrp "should" Sr that you're not rooted and ask if you would like to do so within recovery before booting back into the os.
If not, there's links to an su.zip to flash in twrp for root.
Click to expand...
Click to collapse
Hey man, thanks, it worked like a charm. I appreciate the help from both you.

Stock Recovery Needed For ZTE Avail 2 (Z992 - AT&T)

I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Stephen Wayne Hamilton said:
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Click to expand...
Click to collapse
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
drago10029 said:
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
Click to expand...
Click to collapse
If needed, I could back up my /system folder and send it to you.
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
it's alright man. someone on android forums has already made a custom ROM. so the ball is rolling on out weak old device :laugh:
build.prop?
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
did you ever get around to doing this? there is supposedly a stock image on androidforums but when I opened the Zip, all it had was the stock apps, no build.prop, which I think I blew away with xblast (xposed plugin). now I hang on the boot screen image. there is a stock Rom for the z993 our there, which I suppose I could use, because they are supposed to be the same phone, just different carriers... but then I need to get the at&t apn's and it is just a PITA. so if you could post /system backup or just a stock build.prop, that would be great!
(I'd post links to these rooms but I guess I'm too new of a member... I can provide them if needed.)
I'm way late on this, but just thought I'd post to say that I no longer have the device, and I was never able to fix it.In any case, I hope the rest of you guys get it fixed. It seemed to be a halfway decent phone, although a bit sluggish at times. But beyond that, with all the bloat removed, I'd say it ran pretty well for the duration of time that I had it (less than a month). I currently have a GNote 3 (T-Mobile) and a GNote Pro 12.2" now and it's just awesome, I'm really loving them.
Sorry, accidental double-post (can't figure out how to delete this post, the "Edit/Delete" button doesnt appear to have any option to entirely delete a post).
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
alirezayami said:
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
Click to expand...
Click to collapse
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
alirezayami said:
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
Click to expand...
Click to collapse
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
AlexZap said:
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thnx Alex
I would highly appreciate if anyone tell me what ADB Driver I should use for ZTE Z992. I almost understood all the procedure in the links but now the problem is despite I tried different ADB Drivers, but still ADB reboot-bootloader boots phone again in Normal bootloader.
Also Fastboot devices command does not see the phone, while ADB Devices command see it.
Seems bootloader is locked. Right? What should I do?
This is the method I used when I rooted my avail2 :
http://androidforums.com/zte-avail-2-zte-prelude/821217-how-root-zte-avail-2-z992-guide.html
The author (and I) just used the included drivers from zte that come with the phone. From what I remember, fastboot worked fine. Just hold the volume down button then turn the phone on. It will seem to lock on the start screen, but this is the bootloader. Then connect your cable and try your fastboot commands.
If you are already rooted, you can just download the package here
http://androidforums.com/prelude-all-things-root/797487-cwm-recovery-installer-zte-prelude.html
And skip the middle section, using the impactor to root (13 and 14).
Depending on what's wrong with your phone, you could also try just using the stock recovery and doing a system reset there. It will wipe any bad custom settings, but if the rom is still viable it might get you up and running again. It got me out of a bootloop without re-romming the whole thing. And with titanium backup or system app mover you can reinstall anything you need in the system partition.
*edit - Damn kindle auto correct
Sent from my KFTHWI using Tapatalk
A bit to much fiddling resulted in disaster
Hello XDA forum users,
I'm about ready to toss this phone in the trash. I have an AT&T Avail 2 with model number z992, which is apparently manufactured by a company called ZTE. First I think it would be helpful to explain what I've done to the phone and perhaps others out there can tell me if I've destroyed the phone or if it can be fixed.
A friend of mine sold me the phone for 10 bucks, its in great condition which is why its such a shame that it seems perma-bricked. I have no need for the phone aspect of the device, I simply wanted to "convert" it to a handheld media/application player, like an ipod or tablet for example. The phone comes with several bundled software applications that I find completely useless and wanted them removed, EX. AT&T Navigator and other AT&T software, plus a bunch of google applications.
The first thing I did when I decided to try and customize it was to use Kango's root tool which worked and rooted the phone. I was all excited that it worked and continued by installing the Super User application which allowed me to gain full control over the device. (I should have stopped there.) After the successful phone root I then installed a 3rd party app called NoBloat and used its uninstall options to remove a lot of stuff. I couldn't tell you exactly what all was removed but looking back, it must have been more important than I realized at the time. I know I took out all the AT&T software, then all the Google stuff to, which destroyed the play store. I didn't take out anything that seemed like a system file but apparently the Google stuff is the system files. The phone still worked in this state but it was erratic and things like Contacts would crash even if it was not running. So I considered that a failed attempt and commenced to do a factory reset using the recovery menu (Vol Up + Menu Key + Power button) but the factory reset didn't work, well not like it was supposed to. I had used the restore option before and it made the phone work like it was brand new. Now when the phone is powered on it will boot to the initial setup and ask me to choose a language, then it will get as far as the wireless connection screen (sometime not even that far) and the phone reports that "Unfortunately, Setup Wizard has stopped." and then I tap OK and the setup wizard restarts at the language screen. This is the state it is in now and I do not know how to fix it, I'm beginning to think there currently is no method to fix this.
Things I've tried so far include installing minimal ADB-Fastboot to try and sideload various ROM images, the ones I found here and other places. The phone is not recognized by Windows 7 though and the ADB does not work like it did on a motorola phone I did this to before. I've also purchased an inexpensive 8GB microSD chip with an adapter so I could put the ROM info on that and tried the "Update from external storage option" and that seems like it would work but none of the ROM's I've used will install. I guess because there is some kind of security feature built into the phones hardware which checks the data files for specific tags/sizes and therefore won't accept any of the ROMS I've tried.
There is no means to access the old file system anymore like most guides show, I do not have any CWM's installed nor any backup data whatsoever. It's been reset and now it seems the data it used to restore itself is, while not completely missing, damaged and will not reload anymore. All the guides I've read or watched usually show the user in the operating system or using software on a PC to type out commands. None of that works on this phone though, the phone as I just described it is basically bricked. Is there anything that can fix this, or is the phone a paper weight now? A functional ROM image from AT&T seems unlikely as they have absolutely no relevant information about this on the commercial website and the help and support seems like it's setup for old people who don't understand technology at all. If anyone out there has experience with issues like this then by all means let me know. If more information is necessary then I will be glad to provide it if available.
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Britton Burton said:
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Click to expand...
Click to collapse
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commands
adb.exe push cwm-z993.img /cache
adb.exe shell "su -c 'dd if=/cache/cwm-z993.img of=/dev/block/mmcblk0p17'
This should flash cwm if your phone is rooted and adb shell is working.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commandsp
Click to expand...
Click to collapse
I have not come across that particular file yet, I did try to google it and the only results it had were two and one of those was this post. Would you mind telling me where I might find a copy of the kaw202_recoverflasher.zip?
I managed to find the zip you were talking about and have downloaded it, for anyone else looking for it. I am unable to post links but I would have linked to the files you mentioned. For others looking for the same zip file search for "CWM Recovery Installer ZTE PRELUDE". That's the title of the thread I found the file on that Alex mentioned above. The instructions on the page don't seem like they apply to the situation I'm stuck in but I'll give it a whirl anyway and see if the files work.
If this forum is like the others I've read through so far then there is no real answer to the issue. The phone seems kind of new and not many of the power users on these forums use rinky dink phones like this one. You guys all have the 600 dollar models I guess. What bugs me about this this phone and the state I managed to put it in, is that the damn thing was programmed the first time when it was made. So it seems to me like there should be a way to reprogram the phone the same way the factory did it. Think about it, when they make the phones they don't have any information on the phone at all. It's completely empty, so there must be a way to load the software for the phone even if the phone has no data at all in the main storage. If the files in the recovery flasher.zip file work then I'll post back the results but if it's like the other files I've messed around with (which didn't do anything) then I'm throwing it in the trash can.
Anyway thanks for your response and for pointing me in a different direction Alex
---------- Post added at 09:15 PM ---------- Previous post was at 08:39 PM ----------
HELL YEAH!!! It worked thank you Alex, ​
I would have never figured this out without your help! The phone now has a version of CWM on it and the recovery menu is different. I just tried to install a ROM and it said successful. After the phone rebooted went back to the setup screen from ZTE but it still did the same thing. However this is progress and I should be able to "wander in the dark" and figure out a way to use the CWM to install a completely new rom. Any recommendations on a ROM to use for the z992?
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Britton Burton said:
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Click to expand...
Click to collapse
ze
Glad I could help, but none of the work was done by me, the guys over at android central did all the heavy lifting, I just pointed you in the right direction. I have a stock system e m image around here somewhere if you need it, tho installation will be a bit more complicated. If azazels rom ever gives you issues, ill dig it up and try and help you install it.
Sent from my KFTHWI using XDA Premium 4 mobile app

Xperia 1 - I got swindled for a 'StoreFrontDemo' phone and I can't seem to flash it?

Hey everyone,
So! I bought a Sony Xperia 1 (J8110-2019) phone from someone on Facebook Marketplace at a very solid price of £250 (RRP is still £850 in the UK) due to the seller describing it as 'in retail demo mode' so they lowered the price. I jumped the gun thinking I was getting a solid deal and just stupidly assumed it to be a feature I could just disable with *#*#73556673*#*#- me believing I was some insane developer with mad coding skills where in realityI had once flashed and rooted my Xperia XZ back in 2016. [Insert 'Hackerman' meme]
Yes... I am fully aware I'm a complete idiot for not doing a full assessment on the phone and am now having to learn a very important lesson from this situation!!
It seems to have a Store Front firmware installed and unsure what firmware to download and flash? I've tried some of the official stock ROMs from XperiFirm and it just continues to boot into constant 10-second cycles of demo videos making general functionality like phone calls pretty much impossible. without interruption. I've tried Customized and UK Service Provider Firmware such as EE and O2 but it always goes back into Store mode.
I was hoping if anyone would have or could elaborate on how to make an executable system flash zip for a 2019 Xperia 1? When I extract files from XperiaFirm ROMS (FTF,ZIP,SIN etc), I don't seem to get any META-INF files and thus cant make the proper .zip that TWRP needs to successfully flash a new repacked stock ROM? It always ends in a boot loop."
Here are some key points to hopefully give you some background:
I've installed TWRP successfully and have attempted to use 3 official firmware to flash whilst in recovery but have been unsuccessful each time with 'Invalid .ZIP format'. I've only a few times got booted whilst bundling together FTF files via Flashtool and doing it that way round but only ever seems to solve half the problem
I can't use the SinExtract feature in Flashtools as the SIN file errors as not being supported yet to use different file versions.
I can't use PRFCreator as it errors as the FTF file being unsupported (Due to it being new I assume)
I attempted to create my own META-INF>Updater-script but am unable to identify what partition my phone would use for mounting on "/dev/block". I only ever seem to get MANIFEST.MF from the files and nothing else. On my XZ I think I used something like:
(package_extract_file("boot.img", "/dev/block/mmcblk0");
package_extract_file("system.sin","/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
I have been able to install Magisk for rooting and verified.
I have used Minimal ADB and Fastboot to install programs like TWRP, SuperSu, Magisk but have never attempted, nor would I even know how to wipe my phone completely and install a clean stock ROM - is this possible?
All drivers, software, and systems are correct and up to date (as far as I am aware)
Would installing the' Service Exchange Firmware' be recommended (if I ever make it that far!) due to it being StoreFront?
I checked the IMEI number to see if it was blacklisted/blocked and it's all good. Not lost or stolen.
Thank you for your time to read and wallow in my woes with me my lovelies! Any help would be GREATLY appreciated you magnificent beasts! x
Bump x
...
the last chance... :good:

Doogee S60 Lite MT6750 arm64

There isn't much development done on this phone and there aren't any updates for stock ROM due to come out. So I've decided to try and port LineageOS from another phone with the same chipset. Problem is that when I follow any guide I can seem to find on here, nothing ever is as the guide states. The copy and paste method doesn't work because the names of the files don't match when I extract the boot.img's. Not to mention that I can't even get the system.img to extract whatsoever. I've tried various tools and have only ever had one tell me about the system.img, and that took hours. It still wouldn't extract it either though. I'm not brand new to Android, it's just been several years since I've really decided to play with them. Currently I have TWRP 3.2.1 installed with the stock ROM rooted with Magisk 24. Even simple modifications on the stock ROM, such as debloating, will cause every app on the phone to not work anymore after a reboot. Ultimately causing me to reflash the stock ROM and going through the root process all over again. Can someone please point me in the proper direction to get rid of this terrible stock ROM and begin building my own port? Thank you ahead of time.

Categories

Resources