Develop Bugs

Anyone from N.Ireland offer rooting service

I've noticed a few posters on here are from N.Ireland and was wondering if any of you would root my phone? For a fee of course?
I'm a complete noob at this, I've spent the last four days reading guides and I just can't get it to work. Can get the tinycore linux working on my macbook but can never get past entering this in the terminal:
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/desire After I press return here I get an error.
So I've now thrown in the towel and was hoping a local Android geek could help me out lol
Cheers
Joe

Are you using the TinyCore Live-CD from the MoDaCo guide or the r4 one posted by craigcrawford? the latter had an edited TinyCore build made which was slightly different to the normal one originally posted...
Have a read of this guide, by craigcrawford, never fails to work (so long as you download the right Live-CD - check your HBOOT and download accordingly):
http://android.modaco.com/content/h...sire-easy-rooting-guide-with-tiny-core-linux/

Thanks for the reply, yeah thats the one I'm using. Could it be my tinycore setup? I can't get it to boot from CD so setup a virtual machine on my macbook and ran tinycore through that.
Sorry if that doesn't make sense, I'm a complete noob at all this

Not being an Apple man I don't know if you can boot a Live-CD using a Mac but shouldn't see why not!
Also don't see why a VM wouldn't work but again I've always used a PC and it boots fine so might wanna see if you can borrow a Windows laptop and use that (or, if you're ever in Liverpool, come see me and I'll do it)

Ok going to try it again, I had already installed Linux VM before I downloaded the r4 and didn't know there was Tinycore ISO included with it.
So I've setup a new VM with the ISO from craigcrawford and I'm going to try it one last time. Just want to check something before I start, my phone is unbranded so I'm not using a goldcard do I need to put the rootedupdate.zip on the SD card before i start?

joe_998 said:
Ok going to try it again, I had already installed Linux VM before I downloaded the r4 and didn't know there was Tinycore ISO included with it.
So I've setup a new VM with the ISO from craigcrawford and I'm going to try it one last time. Just want to check something before I start, my phone is unbranded so I'm not using a goldcard do I need to put the rootedupdate.zip on the SD card before i start?
Click to expand...
Click to collapse
Correct, no Goldcard required. Should take about 10 mins all in (did for me on a W7 x4 Ultimate-based machine). Good luck!!

Cheers Eddy, here goes! I'll post how it goes!

Ok getting a bit further into it. Says rebooting into bootloader... FAILED
but then says Step 1 complete and gives instructions on how to continue.
I'm confused
Uploaded with ImageShack.us

Forgot to add, my phone didn't do reboot nor did the screen change at all

Yeah thats not working correctly...something's not right, be it running through a VM or otherwise...
I'd say it might be worth asking advice on (or taking a look at) the rooting guide on MoDaCo as more people there can help (and it works from within a Mac natively)
http://android.modaco.com/content/h...e-now-with-hboot-0-80-and-os-to-1-21-support/

Ok Eddy thanks for your help mate.
Going to phone round a few repair shops in belfast and see if they can do it! It's really started to p*ss me off now!

Would they want to do it, though? I doubt they'd want to potentially brick your phone and have to buy you a new one
What HBOOT are you running on btw?

Well I know of one shop that jailbroke a friends iphone so I'm going to try them to see if they'll give it a go!
I'm running HBOOT 0.80

Right, here's a little guide for a Mac:
- First, download THIS and extract it on to the Mac equivalent of the Desktop
- Copy the 'update.zip' to your SD card - do NOT rename it
- Now open a Terminal window (go to Applications>Utilities, double click 'Terminal' icon) and change directory to the extracted folder. Turn your phone on holding down the back button and you should be in the FASTBOOT screen. Plug your phone into the Mac and it should then read FASTBOOT USB
- In the terminal window type './step1-mac.sh' (without ') and when it finishes it will take you back to the FASTBOOT screen. Press the power button and it will change from FASTBOOT to HBOOT USB
- Select 'Recovery' and when at the screen with the red ! hold vol up and press the power key.
- Select 'wipe data/factory reset' and once complete select 'apply:update.zip' and once this is done reboot the device and you should be rooted

"Now open a Terminal window and cd to the extracted folder"
Eddy I haven't a clue how to open a terminal window and cd to the extracted folder, thats why I was trying the Tinycore guide.
Sorry for being such a noob

*Updated guide above
Don't know what else to put as I'm a Windows man, never used a Mac

Ok think I understand that. Just waiting on the r6 to finish downloading then I'm going to have another crack at it!
Thanks for putting that together Eddy, much appreciated.

Joe, if you are still stuck I should be able to help you out tomorrow free of charge. I think your bootloader is the same version as mine (can't remember off hand) so I still have the files on my netbook to do it, or at least should have.

Still can't get it to work.
Kerso, I'll take you up on that mate, Where abouts are you?
Eddy, thanks very much for your help mate

I am a Mac user but rooting is loads easier on a Windows machine, had mine rooted in no time using a XP based PC.
To open a Terminal window, just click on the magnifying glass search icon type in Terminal and it will appear in the list of matches, just double click it.
CD = change directory in the terminal, that's all. ie CD to the directory where you downloaded the folder it to.
Trouble I had was that OSX was unzipping the downloaded file on completion, I'm not sure how to stop it doing that.

How to Flash Your Vogue - Linux Users

I take no responsibility if you brick your Vogue
Right now I thought that I should put something like this up so that my fellow Linux users can flash their Vogues without having to try and resort to using WINE or installing Windows, like I tried and failed
For this guide I am using Ubuntu Maverick Meerkat 10.10 so if things differ from your setup then I apologise.
Right on to the guide at hand.
1) Go to the following link and download HTCFlasher: Link
Now the it is a .deb file type so if you aren't using a Debain based Linux Distro then you can get the source code here and compile it from there
2) Now you also need the following file to get HTCFlasher to work properly: Link. Again this is a .deb file and I don't know if you can get the source for it or not but oh well.
3) Right, now that you have those two files you can now install them so to do this you need to go and launch the Terminal and do the following
Code:
cd Downloads (I'm assuming here that this is your default download directory)
sudo dpkg -i htcflasher_20080806-1_i386.deb
once you've done that enter your root password - you won't have to do it again
now for the gtkdialog - again do the same as above but with the gtkdialog
Code:
sudo dpkg -i gtkdialog_0.7.20-4_i386.deb
Right now after all that is all installed HTCFlasher will be able to be used properly now. Now on to the fun part, flashing your chosen ROM.
For this part I used NFSFAN's WM6.5 Custom ROM although you can use whatever ROM you want.
1) so once you have your ROM all nicely downloaded and un-RAR'd you need to to into Applications -> Accessories -> HTCFlasher
2) click on the little circle next to the option that says "Get Device Info", plug your Vogue in and click ok. Once it's done it's thing a new window will popup, close out of it and next to the Get Device info line will be soomething similar to this
Code:
CID : [TELNZ001] - ModelID: [VOGU001]
3) Put your phone into bootloader mode by pressing and holding the power+camera button while pushing in the soft reset button with your stylus. This can be awkward to hold but just find your own way to get it done.
4) Now click on the "Flash NBH file" little circle and click ok. Navigate your way to where you extracted your rom, double click it and a little message will pop up saying flash file '/home/user name/Downloads/RUU_signed.nbh'?
Click ok and let it rip. Should only take a couple of minutes. Once the ROM has been flashed click ok on the popup and then you are back to the main HTCFlasher menu do the next step BUT MAKE SURE YOUR VOGUE IS STILL PLUGGED IN!
5) Right so you are back to the main menu, click on the little circle next to Bootloader cmd prompt and click ok. MAKE SURE YOUR VOGUE IS STILL PLUGGED IN OR THIS WILL NOT WORK!
6) Once the Cmd Prompt has opened which is basically instantly type the following code. Please note that when I write {enter} you press the enter key.
Code:
set 16 0 {enter}
task 3 {enter}
Now soft reset your phone and VIOLA!! You have just flashed your Vogue on Linux Give yourself a pat on the back and enjoy your shiney new ROM!
A big thanks goes to mrkite38 who gave me that last bit of code. Without his help my Vogue would still be in bootloader mode

Could a mod please sticky this for me? Just as a reference for othe Linux users

Thanks a lot
Thanks for this info about flashing with Linux.
I had a struggle with finding gtkdialog couldn't be found in 10.10 repos.
But after using your gtkdialog link, everything worked out fine.
Many thanks for that.

Yeah I had heaps of problems trying to kind the gtkdiag files needed as well until I used the magic that is Google haha, took about 30 mins of searching until I found that particular version that worked though.
Glad that it helped you out

Ooh... nice addition. I always get questions about flashing from Linux, but I have no knowledge on the matter...
Thanks for putting this together..
Stuck.

egzthunder1 said:
Ooh... nice addition. I always get questions about flashing from Linux, but I have no knowledge on the matter...
Thanks for putting this together..
Stuck.
Click to expand...
Click to collapse
Yay!! Thanks egzthunder1!!!
Once I figure out how to use Linux ROM Kitchen I'll do another write up for that but at the moment I'm content using NuAngels NuVogue instead of cooking my own ROM

Bootloop

Hey guys,
I was using Sandvolds ICS for some weeks, but since yesterday my phone won't work anymore. I was starting a bike tour, but GPS on Endomondo didn't really work. So I restarted my phone. When I boot it'll show the white screen with green HTC logo, then it'll show the Evervolv animation and this animation will be displayed until I remove the battery, one time I had it running for half an hour.
I tried to boot the phone without sd card and could boot, but after "optimising" apps it kept on crashing because, as it appears, the system data is partly on the sd card.
Now I don't know what to do, what would you recommend? I'd probably just wipe everything and reinstall a backup, but - I don't have a backup

wipe everythin and reflash another rom/same rom...............

2012katas said:
wipe everythin and reflash another rom/same rom...............
Click to expand...
Click to collapse
i guess that'll work, but could anyone recommend another, more time-saving possibility?
greets to india!

Tourist06 said:
Hey guys,
I was using Sandvolds ICS for some weeks, but since yesterday my phone won't work anymore. I was starting a bike tour, but GPS on Endomondo didn't really work. So I restarted my phone. When I boot it'll show the white screen with green HTC logo, then it'll show the Evervolv animation and this animation will be displayed until I remove the battery, one time I had it running for half an hour.
I tried to boot the phone without sd card and could boot, but after "optimising" apps it kept on crashing because, as it appears, the system data is partly on the sd card.
Now I don't know what to do, what would you recommend? I'd probably just wipe everything and reinstall a backup, but - I don't have a backup
Click to expand...
Click to collapse
I got the same situation with you dude!!
I'm now using beta 0.17.1, but after this afternoon everything was wrong.
Then I did a full wipe and installed the latest version of Sandvolds ICS,
It's good and normal before I activate a2sd, but after that
everything went wrong again.
And finally I tried HTC DESIRE-AOKP-milestone6 v2,
It is working normally with INT2EXT, but not very smooth and stable.
actually i don't know what's going on right now :crying:

UserMatty said:
I got the same situation with you dude!!
I'm now using beta 0.17.1, but after this afternoon everything was wrong.
Then I did a full wipe and installed the latest version of Sandvolds ICS,
It's good and normal before I activate a2sd, but after that
everything went wrong again.
And finally I tried HTC DESIRE-AOKP-milestone6 v2,
It is working normally with INT2EXT, but not very smooth and stable.
actually i don't know what's going on right now :crying:
Click to expand...
Click to collapse
hi everybody..i've got the same problem..everything was ok until yesterday with the latest release of the sandvold ics rom..when my phone shutted down for low battery,i put it on charge..after that,i booted it up,and it still remain on the evervolv logo...so i tried to wipe cache,wipe partition,factory reset and format and repartition the sd card..reinstall the rom..and eveything was ok the first time..after that,i enabled the a2sd,and it strucked another time..so i did everything again from the beginning,but this time i enabled the a2sd without any problem..so i started to download from the market all the stuff that i needed,and everything was fine..so i rebooted the phone..and here we go again..strucked!but the worst thing is that without the sd,the phone boot without any problem!now..i bought the sd a week ago..it's a new one..i don't think that it's an sd problem..or also the first times it won't be able to boot up and everything..also i would't be able to install the rom!..so..any suggestion?

Cesk87 said:
hi everybody..i've got the same problem..everything was ok until yesterday with the latest release of the sandvold ics rom..when my phone shutted down for low battery,i put it on charge..after that,i booted it up,and it still remain on the evervolv logo...so i tried to wipe cache,wipe partition,factory reset and format and repartition the sd card..reinstall the rom..and eveything was ok the first time..after that,i enabled the a2sd,and it strucked another time..so i did everything again from the beginning,but this time i enabled the a2sd without any problem..so i started to download from the market all the stuff that i needed,and everything was fine..so i rebooted the phone..and here we go again..strucked!but the worst thing is that without the sd,the phone boot without any problem!now..i bought the sd a week ago..it's a new one..i don't think that it's an sd problem..or also the first times it won't be able to boot up and everything..also i would't be able to install the rom!..so..any suggestion?
Click to expand...
Click to collapse
maybe you can temporarily try DESIRE-AOKP-milestone6 v2
it's also a good choice! and a good rom also.

Hey,
I have the same problem! I also have Sandvolds ICS rom and it gets stuck on the Evervolv loading screen.
It loads up flawlessly without my SD card but then all my stuff is gone.
Any way to backup my data? (EDIT: Nevermind that question, I used backup from recovery)
BTW, SD card works, I can mount it from recovery mode.

Guys, what you say doesn't make me happy!
Maybe it's worth mentioning that I was NOT using the latest version of ICS, but I had no problems for weeks. I'm already waiting for the new Nexus phones, one of them will save me a lot of time and trouble updating to the newest OS and software
Good luck everyone, and please tell us if you manage making your phone working again

tried updating to latest ics via 4ext - fail! i could watch the evervolv animation for hours

Possible Solution
Looking in the Sandvold's thread a lot of people have been claiming that the bootloops is caused by the most recent version of Google Play 3.9.16. Apparently just deleting that will let you boot fine.

AceShinobi said:
Looking in the Sandvold's thread a lot of people have been claiming that the bootloops is caused by the most recent version of Google Play 3.9.16. Apparently just deleting that will let you boot fine.
Click to expand...
Click to collapse
The solution is here: http://forum.xda-developers.com/showthread.php?t=1944766
For me didn't work, but I want to try again and apply the solution directly on the first boot.

AceShinobi said:
Looking in the Sandvold's thread a lot of people have been claiming that the bootloops is caused by the most recent version of Google Play 3.9.16. Apparently just deleting that will let you boot fine.
Click to expand...
Click to collapse
Thanks for your hint, but after a few steps, I was stuck. After downloading the SDK (not mentioned in the tutorial) I experienced problems in the following steps, here is where I had problems
- cd Program Files(x86)/Android/android-sdk/platform-tools/ - I had to enter cd AppData\Local\Android/android-sdk/platform-tools/
- adb shell - command didn't work - I entered adb resulting in lots of text on my screen
- cd /data/data/ - the shell didn't accept this

Tourist06 said:
- cd /data/data/ - the shell didn't accept this
Click to expand...
Click to collapse
Probably because there is no folder /data/data? Have you followed the instructions in this thread? That should work.

Tourist06 said:
Thanks for your hint, but after a few steps, I was stuck. After downloading the SDK (not mentioned in the tutorial) I experienced problems in the following steps, here is where I had problems
- cd Program Files(x86)/Android/android-sdk/platform-tools/ - I had to enter cd AppData\Local\Android/android-sdk/platform-tools/
- adb shell - command didn't work - I entered adb resulting in lots of text on my screen
- cd /data/data/ - the shell didn't accept this
Click to expand...
Click to collapse
Seems like an adb fault.
If you type: adb get-state and adb get-serialno you have in output the infos of your Desire?

freakymonkey said:
Seems like an adb fault.
If you type: adb get-state and adb get-serialno you have in output the infos of your Desire?
Click to expand...
Click to collapse
adb shell will return device not found, adb get-serialno and adb-get-state return unknown
Using 4ext, I mounted system and sd-card
I also tried dietwice's tip (http://forum.xda-developers.com/showpost.php?p=33073702&postcount=8), but at step 3, cd /system/app , it says path not found. I'm no guru, so I don't really know what to do now.
Sorry about the fonts, it's a mess^^

Tourist06 said:
[...] I mounted system and sd-card [...]
Click to expand...
Click to collapse
You need to mount "system" and "USB storage". You have to be connected to your computer.

gartenriese said:
You need to mount "system" and "USB storage". You have to be connected to your computer.
Click to expand...
Click to collapse
Exactly, you have to mount more or less everything, depends on what kind of a2sd you have.
In my case, I had to mount everything because of "standard app2sd"; my "vending" are in /system, /data and /sdext.
Just to be sure, you have to undestand if the phone is connected to the computer. To check this try to write:
...../platform-tools/adb kill-server (press enter)
...../platform-tools/adb start-server (press enter)
NOW plugin your HTC Desire (in Recovery mode) to the computer and digit:
...../platform-tools/adb devices
Should appear at least your Deside (on the right side of the phone code will appear the word"recovery")
If this appear, you can prooced with "adb shell" or all other commands required for the procedure.
I had the same bootloop problem, it was easy to remove all the Play Store files.
Hope helping you.
Mat

Tourist06 said:
adb shell will return device not found, adb get-serialno and adb-get-state return unknown
Using 4ext, I mounted system and sd-card
I also tried dietwice's tip (http://forum.xda-developers.com/showpost.php?p=33073702&postcount=8), but at step 3, cd /system/app , it says path not found. I'm no guru, so I don't really know what to do now.
Sorry about the fonts, it's a mess^^
Click to expand...
Click to collapse
gartenriese said:
You need to mount "system" and "USB storage". You have to be connected to your computer.
Click to expand...
Click to collapse
I think that Tourist06 can't resolve with mounting /system or something else, because he has a problem with adb (adb don't talks with his device).
Have you followed this guide for installing adb?

@freakymonkey: I followed the guide, seemed to work! If I enter the shell I no more need to enter the whole path, entering "adb" will produce text. Please have a look at the following screenshot, hope you can confirm this.
@matteo.rex, no success, here's a screenshot
A pop-up appeared saying there were unidentified devices.
Thanks for your help, guys! My phone isn't working for the sixth day now

Tourist06 said:
A pop-up appeared saying there were unidentified devices.
Click to expand...
Click to collapse
Uhm, this is the problem maybe.
First question: is the phone charging when you plugin it to the pc? (I had a problem with the cable...solved changing it)
Second: could be not an ADB installation problem, but a Driver Installation problem. Check this thread to download it: http://forum.xda-developers.com/showthread.php?t=654047
If typing "ADB" a list of command appear, this mean that it work.
Windows, after the driver installation, have to recognize you Desire also during Recovery, not only during common use.
I hope it could help you!
Let us know!
p.s. I use ADB over Ubuntu, but the work is the same.

Bricked Phone After Magisk Install

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!

[GUIDE] LineageOS 17.1 ROM for Galaxy A50 Android 10 Q

The phone must be installed TWRP Recovery. Use at your own risk, I'm not responsible for bricking your device.
Installation Instructions:
1. Enter TWRP Recovery Mode: Turn power off; Press and hold Volume Up key + Power key, when samsung logo appears release power key only, keep pressing volume up until TWRP recovery appears
2. Select Wipe - Format Data - type "yes" and confirm
3. Copy GSI ROM to your phone
4. Install - Install Image - select lineage-17.1-20200413-UNOFFICIAL-treble_arm64_bvN.img - select System Image and Confirm to flash.
5. Select Reboot - System ( boot without magisk )
6. Setup the Phone
7. INSTALL GAPPS: Enter TWRP Recovery Mode
8. Copy GAPPS zip file from PC to Phone
9. Select Wipe - Advanced Wipe - select "System" - Repair or Change File System - Resize File System - Confirm to Resize.
10. Select Install - select open_gapps-arm64-10.0-nano-20200408.zip and Confirm Flash
11. Reboot - System
12. ROOTING: Enter TWRP Recovery Mode
13. Copy magisk manager apk from pc to phone
14. Reboot to Recovery ( boot with magisk )
15. Connect the phone to internet
16. Install magisk manager
Done!
Download:
LineageOS 17.1 ROM
Open Gapps
WATCH VIDEO HOW TO INSTALL IT: https://youtu.be/u9gDx6VEORo

Thanks. So this is GSI? Bugs?

Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN

Hello everyone
iam in the Process of considering to put LOS on my device.
But the i saw the remarks from InFam0us-1985
Is it therefor not adviceable to use this on a Samsung Galaxy A505FN because this is exactly what i have
Saludos from Spain

DId i Brick my Samsung Galaxy A505FN?
Hello one Question:
"did i Brick my device if for some reason after Trying to flash TWRP it fell back in to OEM-locked and i’ am now in a Boot Loop, ore is the any Hope?
I used Heimdal and at first it did the Job but then it would not start again as expected.
After some attempts to flash it Properly it suddenly fell back in to OEM-Locked!
Pleas if you now some advice it be greatly aprichiatet
My device is a Samsung Galaxy A505FN (Spain)

I found a way to Unbrick my device
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans

hans2020 said:
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans
Click to expand...
Click to collapse
AFAIA, OEM locked you can always flash stock?

I’ am not sure if thats True
InFam0us-1985 said:
AFAIA, OEM locked you can always flash stock?
Click to expand...
Click to collapse
All i know in case of my Samsung Galaxy A50 it is Possible!
To lift the OEM-Lock mode again.
i do not know if that is true for every Device.
Ultimately i was successful to install full Root-access!
I had great difficulty tho to use Heimdall ore any tool on Linux so i ended up using Odin in a VirtuelBox with WinXPpro
but do to no support of Long file names i had to trick there, to to make it work.
I just shorten the Names of every .tar to the first 2 letters.
I was able to successfully flash TWRP with Heimdall but not the Android ROM for my Phone.
I still wonder how to make it work!
There was one Thing i Noticed when Using Odin it seams in the Process he flashes vbmeta.img twice.
That impossible with Heimdall it creates a error message.
Well if anyone - that passes here - knows how to flash a Android 10 ROM of a Samsung Galaxy A50 using Heimdall let me know i tried very very hard to no avail.
I was surprised to learn there is no Good Tool for Linux-user doing this Task.
i only found Old Tutorials!
Is it truly possible that Heimdall dose not support modern Phone-flashing anymore properly?
As of now if a Linux-user ask me about Rooting i would advice him/her to do it in a VritualBox with windows installed.
If you have a License of a Windows Version Higher then XP good otherwise you have to Shorten File names if the very long to make it work.
I scarcely use windows anymore that why i only have a old WinXPpro legally in my Possession.
Unbelievable that the Linux-Community should not have a modern Flash Tool!???
Saludos
Hans
---------- Post added at 12:38 PM ---------- Previous post was at 12:18 PM ----------
Hello to @everyone
I had great difficulty to do this as a Linux User using Heimdall and eventually had to give up (after trying for 3 full days)!
I ended up doing it using Windows out of a VirtualBox!
It was Possible tho to successfully flash TWRP using Heimdall!
It also showed Success when Flashing Android 10 Version for my Phone but would not work.
Using the same Firmware with Odin it worked just fine.
When i compared the Flash-Protocol of Odin with what i did i only Noticed that Odin would flash vbmeta.img twice in the Process something that cant be done with Heimdall as it produces the duplicate error.
I wonder if this is the Reason it would not work.
I was also surprised to Learn, that there is virtual now Tutorial out there using Heimdall on a Modern Phone (last 12 Month ore less).
Is it truly Possible that There is now good solution for Linux Users?
I also Looked in to Fastboot and ADB and other Tools for Linux Platform and they all seam to be outdated!
Also all this Tools could not accomplish the task at hand.
Now if its me and anyone knows how to make it Work on Heimdall let me know as it is a Pretty good tool after all and by now i know it well. I would gladly start to make a tutorial and provide it here for free if i know how to make it work.
I have a txt file where i made a complete Protocol of all i tried if someone is curious ill send it to you.
Saludos Hans
##################################################################
I send some more Details of my Challenge in hope someone my know what it is i have to change!
My Device:
Samsung Galaxy A505FN
I created a .txt file protocol of all i did, i gladly provide it if someone ants to see it.
I analyzed the Whole Firmware-archive and the Pit file of my Phone to eventually find the Problem.
Note:
The Firmware was the correct one as it worked just fine using Odin!!
Analyzing all this, i only noticed two things:
First:
There are 3 seemingly identical files in the Archive and two so called
fota.zip files witch are not Identical
(one in the AP-Packet and one in the CSC-Packet)
Those where:
– cache.img one in the AP-Packet and one in the BL-Packet
– vbmeta.img one in the AP-Packet and one in the BL-Packet
– product.img one in the AP-Packet and one in the BL-Packet
Second:
Once i used Odin to finally flash successfully i noticed that in the Flash-protocol of Odin it seams Odin flashes the vbmeta.img twice in the process!?
Heimdall would not allow me to do so giving me the “Duplicate Error message”
Furthermore i tried one more thing in my desperation to make it work:
i thort: “maybe the order in wish the files a flashed chronologically matters”
So i did exactly that, trying to flash in the same chronological sequence as Odin did.
Note:
Every time i flashed, Heimdall would successfully finish the process but the Phone would not start with android
no matter what i tried.
ALSO i did successfully flash TWRP to my Phone using Heimdall
SO Heimdall works just fine on my system!
I spend a Long Time searching the Internet for a workable Tutorial or glue’s as to what is missing and how i could make it work.
I really want to succeed doing this, as i want to provide my folks offer her in Germany and also English and Spanish speaking Linux-Community with a Tutorial to do this!
I did also drop this Question and Challenge i face in some other Forums no useful answer returned so far
The latest Governmental Abuses and infringement on Peoples Privacy using Corona as excuse, makes it abundantly clear how important this kind a work is!
As for now i think, the only true option for a Linux-User is to run Odin from a Virtual-Box Windows installation, given
you have a legal copy in you're possession and have higher then Windows XP
(else you must change the Filenames of the .tar archives as WIndows XP and lower did not support excessively long filenames.)
Also you have to Install you're Phone USB drivers and have them up and running properly!
Internet access to you're VB makes it all more comfortable, but you can also use Shared folders with the Host-System to do the job.
Note:
I did indeed tried the "WINE-plugin-environment" (Windows 10) under Linux. i could not get it to work.
It was to much messing around make it recognize the USB-connection to the Phone!
I could not get it to work, I don't know if you can?
I guess that would be a nice way for Linux-users if it could be made to work!
What do you guys think, can this be solved?
Pleas let me know if you know the answer to my Challenge!
You're help is not only needed but would be greatly appreciated
Sincerely yours
Hans from Germany

well I Found this from 2017;
Yes you can do fastboot and adb cmd in Linux but you have to install adb and fastboot drivers to Linux by using
1) sudo add-apt-repository ppahablet-team/tools && sudo apt-get update
2) sudo apt-get install android-tools-adb android-tools-fastboot
That's it you get your fastboot and adb cmd’s all the cmds are same just as windows just you need to add sudo in front if not in root
Click to expand...
Click to collapse
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/

Well i do know
Of course i know how to Install a Software on Linux and i did indeed installed those Two
But both of them would not even Detect my device jet Heimdall and Odin had no problem doing that.
Anyhow i might go about and try those Two harder.
And no Iam not confused
thank you anyway
Saludos Hans
InFam0us-1985 said:
well I Found this from 2017;
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
Click to expand...
Click to collapse

I cant call or receive call and send and receive messages via sim
Please help
I cannot call and receive calls
Cannot send and receive messages ,one time passwords, through message
Cannot login through whatssapp .
volte is not enabled
And no option for it to enable
I am from India using jio sim card .
Please help.
If any custom rom is used in my SM-A505F i cant do calls or receive calls nor send or receive messages.
country id : INS
Original firmware of A50 : Atb6

Will this image work with the SM-A505G version?

USB File Transfer Does Not Work
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?

OmariCelestine said:
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?
Click to expand...
Click to collapse
This is what you get with a GSI, finger print wont work either.

InFam0us-1985 said:
This is what you get with a GSI, finger print wont work either.
Click to expand...
Click to collapse
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.

OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
Try with a custom kernel

the project is down? Because I love LineageOs, but the A50 is abandoned :/
---------- Post added at 06:06 AM ---------- Previous post was at 05:57 AM ----------
OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
you need to run into Twrp and it work. But only in TWRP

hey man, the project is being upgraded? Tanks for your time

InFam0us-1985 said:
Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN
Click to expand...
Click to collapse
Got the same problem here. i guess i'm staying on the stock firmware

I have installed lineage-17.1-20210212-UNOFFICIAL-treble_arm64_bvS.
Fingerprint and MTP working.