Related
I followed 2 guides to get my phone rooted and get my HBOOT patched to allow S-OFF - AlphaRev and Clockwork Recovery 2.5.0.1.
I want to get rid of the Joker from start up - had I would of known that I would of remained S-ON till they fixed that. That did permanently add Clockwork Recovery to the recovery area. There is a new version I downloaded and told it to install from ZIP and it reloaded and came to 2.5.0.7 but it never permanently patched it in. I am seriously considering going to AmonRA if it is available - I have done so many searches my head is spinning from lack of finds.
Am I missing something or is this something that needs to be done via ADB/Fastboot? If thats the case, I may need some help.
Permanently flashing recoveries has to be done through fastboot with a .img file, the update.zip way will never permanently flash a recovery, unfortunately. Here is a download link for the 2.5.0.7 recovery image, here's how you flash it (you must have the android sdk installed, and you have to have the fastboot.exe command in either \tools or \platform-tools):
Open up a command prompt window and type this:
fastboot flash recovery C:\location\of\recovery.img
When you reboot into recovery again via hboot, it should be 2.5.0.7.
As for the splash screen, that can be changed too (thank god, I hated the joker screen as well). Follow the instructions on this thread, there are plenty of screens to choose from, including the stock t-mobile screen.
If you need anything better explained, I can try to better explain it.
Thanks for the tips. I did find one I wanted - simple and Tmobile-ish. I do have the SDK installed with all updates from the Java Frontend that it uses BUT I still do not have fastboot.exe
I tried one from a friend but it keeps sticking at WAITING FOR DEVICE. Do I need to be in fastboot first on the phone then do this? It is detecting the phone with ADB devices command.
I'm pretty sure you need to be in fastboot to do this. Why the need for permanent recovery anyway?
I tried fastboot mode on the phone and it worked - Thanks for the tip! Flashed just fine and with help of some of the threads on the themes area i got the splash screen modified. (joker is gone - thank goodness!)
I am wanting to change the boot animation - I know how that works but I can't seem to find any for the MT3GS.
Again, I appreciate the tips. They have been helpful. ( I had to transpose what your talking about to the mac - and find fastboot for the mac - HTC had it on their site with a google search )
Yeah, for some reason google stopped compiling fastboot.exe for the sdk, it sucks. I just kept mine from older revisions of the sdk, and I copy it over whenever there's an update.
And at least for me, (@ whoever asked), permanent recoveries are significantly more convenient, and it saves time. It's nice to actually be able to use hboot recovery option, bypassing the stock recovery. It's also nice to be able to write to /system without a r/w overlay or without having to be in recovery.
MusicMan374 said:
Yeah, for some reason google stopped compiling fastboot.exe for the sdk, it sucks. I just kept mine from older revisions of the sdk, and I copy it over whenever there's an update.
And at least for me, (@ whoever asked), permanent recoveries are significantly more convenient, and it saves time. It's nice to actually be able to use hboot recovery option, bypassing the stock recovery. It's also nice to be able to write to /system without a r/w overlay or without having to be in recovery.
Click to expand...
Click to collapse
Not only that but it keeps that wonderfull 800k space free I am a space freak and like all free space and things organized. But the fact that if I screw up a flash - and for some reason I don't have a rom downloaded I can pop in my NANDROID backup card (which is stored in a safe under my foundation) and restore. That way I don't have to download update.zip anymore.
But I am seriously considering AmonRA - I just can't find a copy for my phone. Looks like it is for older phones unless I am missing something.
Does this phone support any other MicroSD cards 16GB or above?
thronka said:
Not only that but it keeps that wonderfull 800k space free I am a space freak and like all free space and things organized. But the fact that if I screw up a flash - and for some reason I don't have a rom downloaded I can pop in my NANDROID backup card (which is stored in a safe under my foundation) and restore. That way I don't have to download update.zip anymore.
But I am seriously considering AmonRA - I just can't find a copy for my phone. Looks like it is for older phones unless I am missing something.
Does this phone support any other MicroSD cards 16GB or above?
Click to expand...
Click to collapse
There is no AmonRA recovery for our phone, I don't believe. It was requested of him after we got s-off, but we don't know since he doesn't own a slide, and it's awfully hard to develop for a phone you don't have, haha
Well the easiest way to flash a recovery is to make sure you have CM7, or CM6, or separately put the files, MTD0 and Flash_Image in /Data/Local So if you have that, Here it is:
You just need to go to terminal Emulator type
Su
Flash_image recovery /sdcard/xxxx/xxxx.img
(Making sure you realize that the x's represent directories and file names)
For example I would put mine on the Root of the SD card and mine would look like this
Flash_Image recovery /sdcard/recovery.img
Sent from my T-Mobile myTouch 3G Slide using XDA App
iDaZzLeFatHoeZz said:
Well the easiest way to flash a recovery is to make sure you have CM7, or CM6, or separately put the files, MTD0 and Flash_Image in /Data/Local So if you have that, Here it is:
You just need to go to terminal Emulator type
Su
Flash_image recovery /sdcard/xxxx/xxxx.img
(Making sure you realize that the x's represent directories and file names)
For example I would put mine on the Root of the SD card and mine would look like this
Flash_Image recovery /sdcard/recovery.img
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Been flashed for a while now. I did not know this method but it is good to have and try when there is an update.
I have been tinkering with the ArayrayMod Revamped files since Arayray moved on to a MyTouch 4G. (traitor! LOL)
Looks like I may be going into the developing side of roms but I am just waiting for approval to post the rom for public viewing. a .32 kernel with Wifi calling included and thats really it - well retaining OC on that rom as well.
Much more tough than I thought doing this by hand - and I always thought my Unix Administration skills would be wasted.
My phone is currently stuck on the boot screen after i mistakenly removed Apex launcher (when it was messed up on monday) whilst forgetting that i had removed the stock launcher
Annoying as i may be, all my stuffs on memory card or on my google account.... so no real loss. I know i can sort it by flashing, but i just couldn't get it to work. Downloaded the latest generic ftf file & (what appears to be) the latest version of flashtool (0.7.0.0 iirc). But whenever i try flashing, it very quickly tells me that its failed.
I think i know the answer to this, but if possible i would really like to retreive the txts that are on the phone. Is there something i can do before flashing..... or do i have to consider them lost
Any help on either of those questions would be very greatfully received!
Not sure where you got your flashtool from, but obviously not the page in the dev section. Try flashing with the latest flashtool and report back. I take it your boot loader isn't unlocked?
You don't need to flash, if you can get into recovery. There mount usb storage, copy Apex.apk onto it, unmount storage, mount sdcard, mount system, and then move Apex.apk into /system/app.
in cmd/terminal:
Code:
adb shell
su
cd /
cp /sdcard/Apex.apk /system/app
that should do the trick. If you cant access recovery, flash with generic files, look for the flashtool in this forum, there should be some links, and tutorials too.
issak42 said:
You don't need to flash, if you can get into recovery. There mount usb storage, copy Apex.apk onto it, unmount storage, mount sdcard, mount system, and then move Apex.apk into /system/app.
in cmd/terminal:
Code:
adb shell
su
cd /
cp /sdcard/Apex.apk /system/app
that should do the trick. If you cant access recovery, flash with generic files, look for the flashtool in this forum, there should be some links, and tutorials too.
Click to expand...
Click to collapse
If that works it would be great. I have tried to get into recovery mode but with no luck..... however that could be the keypress combo i was using. Have found talk of lots of different ways, not necessarily saying what handset its for.
What is the confirmed keypress combo / method for the arc s?
which flashtool works with the latest generic firmware, as i thought i got this but it wouldn't work
mattshaw4 said:
My phone is currently stuck on the boot screen after i mistakenly removed Apex launcher (when it was messed up on monday) whilst forgetting that i had removed the stock launcher
Annoying as i may be, all my stuffs on memory card or on my google account.... so no real loss. I know i can sort it by flashing, but i just couldn't get it to work. Downloaded the latest generic ftf file & (what appears to be) the latest version of flashtool (0.7.0.0 iirc). But whenever i try flashing, it very quickly tells me that its failed.
I think i know the answer to this, but if possible i would really like to retreive the txts that are on the phone. Is there something i can do before flashing..... or do i have to consider them lost
Any help on either of those questions would be very greatfully received!
Click to expand...
Click to collapse
OK, this worked for me when I did something very similar...
start up the phone, and plug it into the computer.
After a while the light on the phone comes on, and the boot animation keeps looping...
The thing is that adb works now so you can install your launcher through adb!
to do this you type in this command on the windows command prompt
Code:
adb install Trebuchet.apk
some notes: -
you may need to type in the path to your copy of adb.exe if you get a "Command not recognised" error.
I used the launcher from CM10 - Trebuchet in the code snippet. You can extract your launcher's apk file from the rom (look in "system/apk"). Then use your launcher's apk name when you type out the command
Good Luck
An update guys.... spent a couple of hours on this only to find a very simple fix......
Using Flashtool in flashmode (?green light)..... noticed the icon for "install apk".... so found a free launcher apk, hit the button & my phone sprung back into life, text messages & all!!!!
Last week I brought a Morotola Xoom on ebay, it had 4.0 installed but I wasn't that impressed with it having got used to stock 4.1 on my phone.
I came across the great guide at http://forum.xda-developers.com/showthread.php?t=1477024 and used this along with http://wiki.cyanogenmod.org/w/Install_CM_for_wingray to unlock, root and install cyanogenmod 10.1 on it.
It was mostly a stress free install (although I managed to miss renaming the stock files that the post says causes Stock Recovery to overwrite CWM but it seems to still work OK.
My issue now is that I don't seem to have all the Google apps. It has gmail but not maps or market. I assumed that gmail isn't part of cyanogenmod so the 'gapps-jb-20130812-signed' file has installed (I think that file is the correct version).
It's not too clear from the instructions they read to me that you install the main CM zip and then Google apps without needing to re-boot in between, is this correct? I've tried a completely fresh install and also wiping the cache partition but no luck. But have not tried re-booting after installing the CM then installing Google Apps in a second boot, worth a try I guess.
Am I just making a simple noob error here? Thanks in advance for any advice.
A update, I've just tried formatting and re-installing again, only this time allowing a reboot into android prior to trying to install Google apps. One thing I've learnt is that the gmail app is part of the base install. Installing google apps appears to go ok but upon rebooting they aren't there. My next test is to try yet another clean install and an old version of gapps (gapps-jb-20120719-signed).
Chris
Motorola Xoom issues with 'Motorola fast-boot' replacing 'clockwork-recovery'
A further update... It's not gone well, it'd defaulted back to Motorola fast-boot protocol support not clockwork-recovery (after me initially forgetting to rename the files even though it's worked for many re-boots until now).
I've then tried to run back through the guidance at http://forum.xda-developers.com/showthread.php?t=1477024 to re-unlock and re-install clockwork-recovery.
However, it's not gone great, for a start it took me a while to work out to turn on usb debugging in Cyanogenmod 10.1 (see http://wiki.cyanogenmod.org/w/Doc:_developer_options) so adb can see it. After a couple of hours of messing about I've managed to get clockwork-recovery back on it.
However when booted into clockwork-recovery I got a 'error: device not found' from 'adb remount'. So I was not able to rename the files to prevent the Motorola fast-boot overwrite of clockwork-recovery eventually happening. When android is booted and it isn't in recovery I get a 'remount failed: Operation not permitted' response to adb remount. Is there another way to rename '/system/recovery-from-boot.p' and '/system/etc/install-recovery.sh' without having to do it do it at that first boot, it is interesting that clockwork-recovery survived several boots.
I've decided not to risk the install of a potentially unsupported zip of Google apps when my recovery situation isn't solid.
Hmm a fun morning, I've lost times now at how many times I've had to reroot it. I've managed to get the Google play store apk and have tried using that (in addition to installing the gapps zip) it is loading but complaining of no network connection.
With regard to renaming the files ' /system/recovery-from-boot.p' and 'system/etc/install-recovery.sh' I've not managed this, when the tablet reboots into clockwork recordery its connection with adb is dropped. I've also tried doing them in terminal when booted and they don't seem to be there.
There doesn't seem to be anyone else commenting on this so I'll just plod along blindly :silly:
c_dunne said:
A further update... It's not gone well, it'd defaulted back to Motorola fast-boot protocol support not clockwork-recovery (after me initially forgetting to rename the files even though it's worked for many re-boots until now).
I've then tried to run back through the guidance at http://forum.xda-developers.com/showthread.php?t=1477024 to re-unlock and re-install clockwork-recovery.
However, it's not gone great, for a start it took me a while to work out to turn on usb debugging in Cyanogenmod 10.1 (see http://wiki.cyanogenmod.org/w/Doc:_developer_options) so adb can see it. After a couple of hours of messing about I've managed to get clockwork-recovery back on it.
However when booted into clockwork-recovery I got a 'error: device not found' from 'adb remount'. So I was not able to rename the files to prevent the Motorola fast-boot overwrite of clockwork-recovery eventually happening. When android is booted and it isn't in recovery I get a 'remount failed: Operation not permitted' response to adb remount. Is there another way to rename '/system/recovery-from-boot.p' and '/system/etc/install-recovery.sh' without having to do it do it at that first boot, it is interesting that clockwork-recovery survived several boots.
I've decided not to risk the install of a potentially unsupported zip of Google apps when my recovery situation isn't solid.
Click to expand...
Click to collapse
Well, I'm with this problem too. I'm trying to solve this problem by myself, but no success at all. It do FC on google play every time it try to update. Every Google App (besides GMail) is doing FC with this CM build.
I tried to:
- Reinstall google apps
- Install another version (compatible with Android 4.2.2)
- Do the wipes again
- Install google play from an outside source (it doen't come with it).
But no success.
Any ideas?
miraidensetsu sorry for my delay in responding, I'm surprised that no other responses to this tread have been made. An update I've now resorted back to the stable release cm-10.0.0. Given it's nearly a year old I'd hope there'll be a stable release of 4.2 out soon.
Initially I had issues with the stock keyboard crashing all the time. But after searching about this I've installed the Google keyboard app and disabled the stock one.
I wanted to install LineageOS.
I followed the tutorial here: https://wiki.lineageos.org/devices/bullhead/install
I completed the folowing steps
Code:
6.) Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
7.) Go back to return to main menu, then select Install.
8.) Navigate to /sdcard, and select the LineageOS .zip package.
But couln't complete the 8th step becaus I think I don't have the LinageOS zip on my phone, How can I move it there?
How can I send LineageOS install package to my phone so I can install it with TWRP ?
I am using Nexus 5x with Windows 10.
Not to worry
Easy. Just boot up your current ROM and USB, SD Card, Bluetooth, WHATEVER means you have available to move the file to your downloads folder or someplace like that. As long as you can navigate to it, TWRP will let you do that when the time comes. Recommend you put your GApps zip file (I prefer nano) and the appropriate L.O.S. su-addon zip in there as well. After all, what's the use of the ROM if it isn't rooted
Now, fire it up in TWRP and do at least one complete, everything you can include backup of the whole thing before you do ANYTHING else. TWO backups are better if you can move one of them completely off device, as in to a USB stick, etc... The more good backups you have, the less the evil Gods of screwing up installs will try to seek you out. Yes, that has been scientifically proven, even if it sounds like superstitious mumbo-jumbo.
Still good? Wipe dalvik, cache, whatver your build recommends, and flash L.O.S., the su-addon, and GApps all at once. Reboot, be just a little bit patient the first time around, and enjoy. Good Luck.
nezlek said:
Easy. Just boot up your current ROM and USB, SD Card, Bluetooth, WHATEVER means you have available to move the file to your downloads folder or someplace like that. As long as you can navigate to it, TWRP will let you do that when the time comes. Recommend you put your GApps zip file (I prefer nano) and the appropriate L.O.S. su-addon zip in there as well. After all, what's the use of the ROM if it isn't rooted
Now, fire it up in TWRP and do at least one complete, everything you can include backup of the whole thing before you do ANYTHING else. TWO backups are better if you can move one of them completely off device, as in to a USB stick, etc... The more good backups you have, the less the evil Gods of screwing up installs will try to seek you out. Yes, that has been scientifically proven, even if it sounds like superstitious mumbo-jumbo.
Still good? Wipe dalvik, cache, whatver your build recommends, and flash L.O.S., the su-addon, and GApps all at once. Reboot, be just a little bit patient the first time around, and enjoy. Good Luck.
Click to expand...
Click to collapse
Sorry I don't know what you mean exactly. Can you exlain a bit more?
My situation looks like this:
1) I don't need to backup anythig.
2) My problem is that I don't have the lineageOS zip on my phone so I can't install it with TWRP
3) because of step 5,6 on the tutorial I believe I don't have any current ROMS!
step 5,6:
Code:
5) Select Wipe and then Advanced Wipe.
6) Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
My assumption is that no ROM will load as the current ROM got deleted during step 5&6.
All I get when I start the phone is GOOGLE sign and the lock sign at the bottom.
4) When I go to Reboot inside TWRP and click System I get "No OS Installed! Are you sure you wish to reboot?"
Can you help?
flex567 said:
Sorry I don't know what you mean exactly. Can you exlain a bit more?
My situation looks like this:
1) I don't need to backup anythig.
2) My problem is that I don't have the lineageOS zip on my phone so I can't install it with TWRP
3) because of step 5,6 on the tutorial I believe I don't have any current ROMS!
step 5,6:
Code:
5) Select Wipe and then Advanced Wipe.
6) Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
My assumption is that no ROM will load as the current ROM got deleted during step 5&6.
All I get when I start the phone is GOOGLE sign and the lock sign at the bottom.
4) When I go to Reboot inside TWRP and click System I get "No OS Installed! Are you sure you wish to reboot?"
Can you help?
Click to expand...
Click to collapse
H'mmm.......... It does appear that you wiped the whole thing, and THAT may make it a bit more of a challenge, but let us try our best. HOPEFULLY your device will recognize the necessary files on a USB stick. You can tell TWRP to MOUNT the USB drive in order to do that if you must, and many devices have no problem and will recognize the device with no added effort, and you just have to navigate to it within TWRP. THAT will be the EASY way, and given what you've described, there isn't anything left on the device to be concerned about with respect to backups, etc... so cross your fingers, and if TWRP can mount and find a USB storage device you just have to flash the three zip files from USB storage as previously described. Otherwise, there is not much I could do personally without the device in hand, although the easiest path forward might be to re-flash a stock ROM and start over again. And please note you would not be the first person reading (or writing) this message to need to do that. Once you get the hang of this, it is not a brutal process, but the first time or two it can be a bit intimidating. Hang in there, the good news is that it is somewhat difficult to totally brick most of these things, so persistence should win out. As long as you can still boot it into TWRP you're fine. Now, one other very important thing. If somehow the bootloader was not unlocked, none of this is going to work at all. SO if that is the case, your only recourse is going to be to get that taken care of first, which requires one of: some finesse with ADB / fastboot, a ROM of some sort (i.e. re-install stock) installed on the device that lets you unlock it by flipping the switch in developer settings , or some other more geeky process that is best supervised by a person who genuinely knows what they are doing and with physical access to the device. There will be no shortage of content out here concerning how-to, but some of the folks writing it are not necessarily technical writers targeting a less experienced audience, even if they are in many cases quite brilliant programmers.
nezlek said:
H'mmm.......... It does appear that you wiped the whole thing, and THAT may make it a bit more of a challenge, but let us try our best. HOPEFULLY your device will recognize the necessary files on a USB stick. You can tell TWRP to MOUNT the USB drive in order to do that if you must, and many devices have no problem and will recognize the device with no added effort, and you just have to navigate to it within TWRP. THAT will be the EASY way, and given what you've described, there isn't anything left on the device to be concerned about with respect to backups, etc... so cross your fingers, and if TWRP can mount and find a USB storage device you just have to flash the three zip files from USB storage as previously described. Otherwise, there is not much I could do personally without the device in hand, although the easiest path forward might be to re-flash a stock ROM and start over again. And please note you would not be the first person reading (or writing) this message to need to do that. Once you get the hang of this, it is not a brutal process, but the first time or two it can be a bit intimidating. Hang in there, the good news is that it is somewhat difficult to totally brick most of these things, so persistence should win out. As long as you can still boot it into TWRP you're fine. Now, one other very important thing. If somehow the bootloader was not unlocked, none of this is going to work at all. SO if that is the case, your only recourse is going to be to get that taken care of first, which requires one of: some finesse with ADB / fastboot, a ROM of some sort (i.e. re-install stock) installed on the device that lets you unlock it by flipping the switch in developer settings , or some other more geeky process that is best supervised by a person who genuinely knows what they are doing and with physical access to the device. There will be no shortage of content out here concerning how-to, but some of the folks writing it are not necessarily technical writers targeting a less experienced audience, even if they are in many cases quite brilliant programmers.
Click to expand...
Click to collapse
The bootloader is unlocked becaues I unlocked it and I see the red sign:
Code:
DEVICE STATE - unlocked
When I click Mount I get the following options, System, Vendor Data, Cache, USB OTG, which one should I select ?
I was able to fix it and I installed it now the Lineage OS works
I had to go to
Code:
Mount > enable MTP
and after that I was able to use
Code:
ADB SHELL
and after that I was able to push the zip to the device. Once it was on the phone I was able to use TWARP to install it.
Code:
$ adb push lineage-15.1-20180430-nightly-bullhead-signed.zip sdcard
The only question I have is why I get this message every time I turn on the phone, how can I remove it? :
Code:
A vendor image mismatch has been detected. Typically this means your vendor images us out of date. Please enousre your vendor image matches OPM2. 171019.029
Since I decided not to install Play Store, how can I now install some programs without the playstore ?
flex567 said:
I was able to fix it and I installed it now the Lineage OS works
I had to go to
Code:
Mount > enable MTP
and after that I was able to use
Code:
ADB SHELL
and after that I was able to push the zip to the device. Once it was on the phone I was able to use TWARP to install it.
Code:
$ adb push lineage-15.1-20180430-nightly-bullhead-signed.zip sdcard
The only question I have is why I get this message every time I turn on the phone, how can I remove it? :
Code:
A vendor image mismatch has been detected. Typically this means your vendor images us out of date. Please enousre your vendor image matches OPM2. 171019.029
Click to expand...
Click to collapse
Wow, you took what I would have thought of as the long way, but so far, so good it would seem. I was thinking you could have simply mounted the USB as an OTG device and flashed directly from that via TWRP. I have ZERO clue about the "vendor image mismatch" message. But now that you have it more or less working, you COULD try putting the zip files into the regular downloads folder, do a dalvik and cache (factory reset) wipe, and re-flash them. You haven't loaded up a bunch of stuff to worry about replacing. Worst case you repeat initial setup. What have you got to lose?
---------- Post added at 08:36 PM ---------- Previous post was at 08:27 PM ----------
flex567 said:
I was able to fix it and I installed it now the Lineage OS works
I had to go to
Code:
Mount > enable MTP
and after that I was able to use
Code:
ADB SHELL
and after that I was able to push the zip to the device. Once it was on the phone I was able to use TWARP to install it.
Code:
$ adb push lineage-15.1-20180430-nightly-bullhead-signed.zip sdcard
The only question I have is why I get this message every time I turn on the phone, how can I remove it? :
Code:
A vendor image mismatch has been detected. Typically this means your vendor images us out of date. Please enousre your vendor image matches OPM2. 171019.029
Since I decided not to install Play Store, how can I now install some programs without the playstore ?
Click to expand...
Click to collapse
Missed that one, sorry. If you did not flash the GApps zip when you installed Lineage, you can hunt down the .APK files for apps you want on the web. That'd be the only way I can think of and a good reason to re-do it before it is too long into the process !!! If you pick the nano or even pico options you won't be dragging much if any Google bloat onto the phone. Personally, while I often find the Play Store to be a pain in the .... I can ignore it until I need something. On some devices it can certainly be most intrusive.
I don't think I will play around with it now for some time.
I was thinking you could have simply mounted the USB as an OTG device and flashed directly from that via TWRP
Click to expand...
Click to collapse
I tried to select the OTG thing but was unable to put the checkmark in.
I also found the fix for Vendor Image mismatch, didn't try if it works though:
https://gist.github.com/MacKentoch/48ad6b91613213ee9774c138267e2ed4#file-fix-lineageos-vendor-mismatch-error-nexus5x-md
I also think this needs to be updated:
https://wiki.lineageos.org/adb_fastboot_guide.html
https://wiki.lineageos.org/devices/bullhead/install
you COULD try putting the zip files into the regular downloads folder
Click to expand...
Click to collapse
I had problems pushing the LineageOS.zip file anywhere else, I coulnt create new folder.
flex567 said:
I was able to fix it and I installed it now the Lineage OS works
I had to go to
and after that I was able to use
and after that I was able to push the zip to the device. Once it was on the phone I was able to use TWARP to install it.
The only question I have is why I get this message every time I turn on the phone, how can I remove it? :
Since I decided not to install Play Store, how can I now install some programs without the playstore ?
Click to expand...
Click to collapse
Congratulations for not installing play store. I think you not installed play services as well. You simply did not install any GApps. That's the first step to get your setup slim and privacy friendly. Next steps are installing f-droid app. From f-droid you can install free software. If you really need apps from play store you can get them with yalp. If they don't run without Google play services you can try microG.
I found a page from which I can download apk files from play store so I will just use that for now.
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Jameswebb97 said:
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Click to expand...
Click to collapse
Use duces script to flash June google factory image.
jlokos said:
Use duces script to flash June google factory image.
Click to expand...
Click to collapse
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Make sure you are trying to open from the correct location, and put .\fastboot
EvilDobe said:
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Click to expand...
Click to collapse
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
simplepinoi177 said:
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Click to expand...
Click to collapse
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Jameswebb97 said:
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
Click to expand...
Click to collapse
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Jameswebb97 said:
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Click to expand...
Click to collapse
EvilDobe said:
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Click to expand...
Click to collapse
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
simplepinoi177 said:
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
Click to expand...
Click to collapse
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
Hey I'm so glad you got it working! Leave me a "Thanks!" would make it up to me ... I'm always happy to help out and get things figured out...yet I don't get the satisfaction of knowing if it does end up helping a lot of the time because a good number don't come back with their experience...so thanks for that! Glad you got it going...
EvilDobe said:
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Click to expand...
Click to collapse
And it's as @EvilDobe means.....
I remember back in the days of the Motorola Droids (OG Droid1, Droid 3, & Droid 4) where you could really mess things up and come out with a big ol' "brick" "paperweight" as there were many instances where you could not come back from (i.e. updating to a certain point, then attempting to downgrade when Google/Motorola/Verizon put blocks that breaks it). But this isn't the case these days. @Jameswebb97, at least with the Pixel 2's, Oreo and/or P(Android OS 9), it's actually more difficult than easy to get that too far gone. The only reason why I can help so many troubleshooting their issues is because I, myself, have wrecked my current device in some serious ways! So I can relate and have experience in helping in the same situations. I've gotten it to where it says "device is corrupt," (which isn't all that uncommon), BUT with the added desperate troubleshooting where I had to wipe/erase, changing partition types, format several partitions, even go about "resizing" the partition to match the "target extraction size" of the Full Factory flash, and even as far as learning to manually flash the various system partitions and that there are two (system_a & system_b) but, in Google's infinite wisdom(?), one flashes to system_a and the other to system_other!!! And I haven't even started on reading others' issues when going after the Slot A and Slot B complications -- I didn't even attempt to touch this in that troubleshooting story.
My point is: I think I've broken my device farther than most people and got it so close to the brink, and yet I was able to bring it back and am still using that same device today (most people would usually, at that point, go and get a RMA replacement). Honestly, as long as you have access to Bootloader Mode (which Google, in their infinite wisdom, seems to have placed it in the main board memory or separate memory rather than storage as to make it always accessible which makes it hard to "lose"), you have a really good (seemingly perfect) "safety net" in which you can always flash back to a working, stock state -- which is why it's the best policy to just make good backups before experimenting so, if anything, you get back to this state and restore all your data. I'm not trying to convince you to root or to try custom ROMs or anything -- even though there are many great reasons and capabilities of rooting -- I am simply appealingl to your sense of curiosity and reassure you so you aren't held back and you don't restrict and limit yourself if you don't want to, but are to fearful to experiment.
I hope you don't take this post as "lecturing" or anything, just some thoughts I hope you consider...
Glad it worked out in the end for you!