Develop Bugs

[Q] need help rooting dinc2 please

so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[

simple29 said:
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
Click to expand...
Click to collapse
what guide are you using? the recovery img has to be in the same folder as fastboot unless you point it towards a different folder

In the same boat as the OP, I've done everything right and I get this error message in cmd with the black screen and white HTC text.
BTW OP - You can go back to using your phone. Take out the battery (with the usb plug out of the phone or computer) and put it back in and turn the phone on normally. You'll just have to go through the process again of fastboot oem rebootRUU to get back to the black screen with white HTC text.
I'm using the CyanogenMod Wiki HTC Incredible 2 Full Update Guide (since I cannot link it in my post), I dunno what the OP is using. Also, the recovery file is in the appropriate location(s) in the android-sdk-windows folder.

im using the cyanogenmod wiki and i tried putting the recovery image for clockwork into the same folder as fastboot and adb and it still gives me that error and i dont have the technical savvy to figure this out
edit: that would be the platform-tools folder in the android sdk folder, thats what i found people did by googling this
and to finalassault, i took out my battery and tried turning it back on normally i just get stuck at the white screen with the green htc lettering so i clearly messed something up unless i just have to wait a few minutes

Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk

nothing is working and im completely lost, thanks for the help though
also i still cant turn my phone on normally

drcrawfo said:
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Same error, except it's just coming up as not able to load this file instead of the other one. Maybe I possibly screwed up whilst doing AlphaRev?
Edit - I just did it a different way and I didn't get an error message:
sending 'recovery' (5022 KB)...
OKAY [ 25.776s]
writing 'recovery'...
OKAY [ 2.254s]
finished. total time: 28.030s
I guess that worked.
Edit 2 - It "worked" but didn't really do anything else. Might have done something wrong on the AlphaRev step. Actually I'll shut up now, something else showed up.
Edit 3 and final edit - Done and done. That was fun.

how did you get it too work???

simple29 said:
how did you get it too work???
Click to expand...
Click to collapse
It sounds like you may have borked your stock rom....if you can boot to hboot and select fastboot then you should be able to flash the CWM from this link http://forum.xda-developers.com/show...php?p=14947083
Follow the instructions on the link not the one from CM Wiki. Make sure you have fastboot.exe and CWM image from the link in the same folder as your adb. If you're using windows 7 64bit then you'll need to run adb in compatability mode (at least that's what I had to do to get it working in 64bit).
You should then be able to flash a rooted, deodexed stock froyo sense rom from this link by Jcase http://forum.xda-developers.com/showthread.php?t=1138274 or use XGunthers Incredibly Debloated Rom here http://forum.xda-developers.com/showthread.php?t=1138202
That should get you up and runnning. Or you could just jump straight into the GB ASOP roms CM7, MIUI, etc.
Let me know if this works for you....

the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
edit: got it in compatibility mode, i suppose i didnt install it right because it looks like it does something for a few seconds then seems to stop

simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
Use the link in my post above.
Sent from my Incredible 2 using Tapatalk

simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
It's okay don't worry...I'm pretty new to this stuff too since I just got into rooting about 2 weeks ago.
Compatability mode is an option in windows 7. Right click on the adb.exe file and select Properties. Once that comes up, you'll need to select the compatability tab on top and choose run in 'Windows XP Service Pack 2' mode (sorry I'm at work and don't have access to my win7 machine). Then click ok and it should run in compatability mode.
Then just follow the flash instructions from the link drcrawfo posted up and you should be good to go!

yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod

ok so idk why but i decided to try taking out the sd card and then when i did the flash recovery cwm thing a whole list of commands came up in the command prompt and i have no clue if thats good or bad or what command i should pick
ill list a few just to see if that helps you guys in helping me out
update <filename>
flashhall
flash <partition> [ <filename> ]
and a few more then there were options that followed
edit: and now for somereason it doesnt flash again but if i do fastboot recovery i still get all those options so is there a way to get the cwm to flash through that way

simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
Hmmm..so you have all your files setup in the same folder and when running the commands from cmd they don't do anything? Does it saying anything is being sent?
This may be beyond my expertise. Have you tried posting in the clockwork mod thread in the development section?
Sent from my Incredible 2

I just want to mention that I didn't end up using the exact commands that are given from the wiki, that didn't seem to work for me. I had to mess around with it (including manually pointing cmd to where it was) to get it to work for me. Had all of the drivers, SDK stuff, the path and everything where they should have been. I hope you get this resolved.

nothing is working out for me this is not fun

same boat as you simple but I can still use my phone. I just gave up as none of the methods seemed to work.

simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
You need to open a command window, change the working directory to where adb/fastboot are located and then type adb.exe at the command prompt.
It sounds like you are trying to double-click the adb.exe from Windows Explorer.

yea i was double clicking, im not too savvy with this stuff, how do you change the directory and all that

[Q] Where do I start?

I bought this Xperia ARC LT15a on Friday and have been having LOTS of trouble figuring out what to do with it. I came on here and I can say the tutorials aren't very noob-friendly because you have your own "lingo" that I dont understand whatsoever.
Now, for you guys to understand my frustration, I am coming from IOS, and was told "rooting" an Android phone is a much simpler process then jailbreaking an iPone. Well, that sure as hell has proven to be wrong since I can't even figure out how to UPDATE my phone >_>
First off, what I'm trying to do is update it to ICS. Sony says you can do it using the PC Companion, but it says I'm up to date. Same thing with the SEUS or whatever you call it...says I'm up to date. I am running Android Ver. 2.3.4 so I'm pretty sure I am NOT up to date...my IM number (or whatever) is listed as compatible with ICS so it should just update via seus or pc companion...but no...
So someone linked me to tutorials on how to FLASH ics to it... but all of the tutorials have dead links and are completely useless to me now...
Can someone PLEASE tell me what to do... I just want to update to ICS and root it, but I can't even f***ing update.........!!!! very frustrating

i felt exactly the same mate haha
but this was my first smartphone full stop lol
is it the tutorial links in general that are dead?
but do some searching, i found pretty much everything i needed on here
and now i can change ROMS, kernels, baseband etc in minutes
im sure someone more helpful will be along soon lol

Right - I haven't posted much but having been pretty much under the same level of noob frustration before I'll try to help....
First - Often, during updates you can be driven mad with reboots and reboot cycles..... hopefully, what is outlined below can be a guide to sorting out any problems you might have.
1. Backup everything.
- go to play store and search for "backup" and you'll find what you need. I use Astro File Manager for application backup and sms backup for messages. I'm not bothered about backing up anything else.
2. Unlock the Bootloader.
- download sdk starter package
Code:
://developer.android.com/sdk/index.html
- so far as I can figure this will facilitate communications between your pc and phone. CyanogenMod Wiki guides you through this process:
Code:
://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
- download latest version of fastboot. Now, you'll never double click on this program to run it. Instead you'll run commands from your command tool which will use the program to do the work.
- record your IMEI - in dialer type in *#06# for your IMEI & write it down.
- get your phone attached in fastboot mode. to do this you turn off your phone and hold the menu button while you attach it via USB to your computer.
- see if you're connected properly. Look for command prompt (Windows Key - All Programs - Accessories). Right click on this and run as administrator. Type in the following: fastboot -i 0x0fce getvar version . It will give an obviously positive message if you are correctly connected - if not, ensure you've attached in properly.
- get code to unlock bootloader - go here:
Code:
://unlockbootloader.sonymobile.com/
and go through the process to get an unlock key. Once you have this, go back to your command prompt and type fastboot -i 0x0fce oem unlock 0xUNLOCKKEY (where UNLOCKKEY is the number you have gotten from Sony website. You should get a confirming message.
Now that you've unlocked the bootloader you need to decide what kind of kernel and ROM you want. You can regard the ROM as software whereas the kernel links the software to the hardware. This is my limited understanding anyway.
3. Now, sometimes people make standalone kernels and sometimes they are kept with the ROM.
This leaves a couple of options
- you can flash a stand-alone kernel using flashtool (
Code:
://androxyde.github.com/
). The process is pretty simple.
- Now, if you download a ROM which advises that you need to extract and flash a file called "boot.img" there is a different method. In this case your ROM zip file can be extracted to find the boot.img file.
When you get the boot.img file you can place it in C:\. Now, all advice will be to place it in the platform-tools folder which is created in step 1. It doesn't matter really so long as you point at the right place when flashing.
(I also think that you can use flashtool in flashmode to do this job....)
4. Now you have a kernel on your Xperia and seeing as you've got the bootloader unlocked you can now unplug the phone and turn it on. While the phone is booting up, keep toggling the volume button and it should go into bootloader. This is a text-based interface that allows you several functions.
Somewhere in there is an option to mount the SD card (for which you need to plug into your comp again)
5. You'll see the phone's SD card in Windows explorer and will be able to put your ROM onto it (NOT the extracted stuff from earlier but the original zip file).
6. You can now install this ROM but first clear all data and the dalvik cache. I also always to the battery stats here too. It might take a little bit of exploring to find these.
7. Now you can go to "install zip from SD Card". Step through and you will find where you put the ROM zip file. Select it and install the ROM.
At this point, you may get a bit frustrated - because it's here that you find things like:
The ROM sucks
Bits don't work or
You can't get it to work
For any of the above try again....
Currently I'm on Paranoid Android ICS ROM which I like but if I can't get the Wi-Fi working there's no way I'll be sticking to it. Another that I really liked and will return to is Boost HD RC4
I hope it works out for you.....
Tony

Canned30 said:
Right - I haven't posted much but having been pretty much under the same level of noob frustration before I'll try to help....
First - Often, during updates you can be driven mad with reboots and reboot cycles..... hopefully, what is outlined below can be a guide to sorting out any problems you might have.
1. Backup everything.
- go to play store and search for "backup" and you'll find what you need. I use Astro File Manager for application backup and sms backup for messages. I'm not bothered about backing up anything else.
2. Unlock the Bootloader.
- download sdk starter package
Code:
://developer.android.com/sdk/index.html
- so far as I can figure this will facilitate communications between your pc and phone. CyanogenMod Wiki guides you through this process:
Code:
://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
- download latest version of fastboot. Now, you'll never double click on this program to run it. Instead you'll run commands from your command tool which will use the program to do the work.
- record your IMEI - in dialer type in *#06# for your IMEI & write it down.
- get your phone attached in fastboot mode. to do this you turn off your phone and hold the menu button while you attach it via USB to your computer.
- see if you're connected properly. Look for command prompt (Windows Key - All Programs - Accessories). Right click on this and run as administrator. Type in the following: fastboot -i 0x0fce getvar version . It will give an obviously positive message if you are correctly connected - if not, ensure you've attached in properly.
- get code to unlock bootloader - go here:
Code:
://unlockbootloader.sonymobile.com/
and go through the process to get an unlock key. Once you have this, go back to your command prompt and type fastboot -i 0x0fce oem unlock 0xUNLOCKKEY (where UNLOCKKEY is the number you have gotten from Sony website. You should get a confirming message.
Now that you've unlocked the bootloader you need to decide what kind of kernel and ROM you want. You can regard the ROM as software whereas the kernel links the software to the hardware. This is my limited understanding anyway.
3. Now, sometimes people make standalone kernels and sometimes they are kept with the ROM.
This leaves a couple of options
- you can flash a stand-alone kernel using flashtool (
Code:
://androxyde.github.com/
). The process is pretty simple.
- Now, if you download a ROM which advises that you need to extract and flash a file called "boot.img" there is a different method. In this case your ROM zip file can be extracted to find the boot.img file.
When you get the boot.img file you can place it in C:\. Now, all advice will be to place it in the platform-tools folder which is created in step 1. It doesn't matter really so long as you point at the right place when flashing.
(I also think that you can use flashtool in flashmode to do this job....)
4. Now you have a kernel on your Xperia and seeing as you've got the bootloader unlocked you can now unplug the phone and turn it on. While the phone is booting up, keep toggling the volume button and it should go into bootloader. This is a text-based interface that allows you several functions.
Somewhere in there is an option to mount the SD card (for which you need to plug into your comp again)
5. You'll see the phone's SD card in Windows explorer and will be able to put your ROM onto it (NOT the extracted stuff from earlier but the original zip file).
6. You can now install this ROM but first clear all data and the dalvik cache. I also always to the battery stats here too. It might take a little bit of exploring to find these.
7. Now you can go to "install zip from SD Card". Step through and you will find where you put the ROM zip file. Select it and install the ROM.
At this point, you may get a bit frustrated - because it's here that you find things like:
The ROM sucks
Bits don't work or
You can't get it to work
For any of the above try again....
Currently I'm on Paranoid Android ICS ROM which I like but if I can't get the Wi-Fi working there's no way I'll be sticking to it. Another that I really liked and will return to is Boost HD RC4
I hope it works out for you.....
Tony
Click to expand...
Click to collapse
I should have mentioned that the only thing I was successful doing was unlocking the bootloader...but then I was told to re-lock it so I could update using the PC companion.......... very annoying
thanks for the detailed reply..
I'm thinking now I wont bother with ICS and ill just root my current version 2.3.4 but yet again ive run into problems with dead links since most have not been updated since this time last year..
*EDIT*
I've tried DooMLords app thing to root, and all I get is a bunch of errors
trying to post a pic with all the errors but im not allowed...............................frustration after frustration after frustration

Try downloading some custom kernels n Roms from this site to see which version of ICS suits not best
There are threads with very explicit details on how to do so, you just need to look
I used to be a noob, on longer the case now.
Currently running acronium 2.4 with doomkernel v04 with WiFi modules, learned how to do all this from here
I'll figure out a site to upload all that I've downloaded so you have access to them with instructions cause some links don't work in other threads
Sent from my LT15i using xda app-developers app

[Q] Galaxy Nexus ADB side load help

Phone Was working fine on latest PA rom until battery died. Upon charging and rebooting up, the Rom some how got corrupted i guess, because it now just boots logo forever. I don't have any roms on the device itself so can't reinstall anything through recovery to try to fix whatever may have got corrupted. I know there is a way to Side Load with TWRP, but am running into difficulties. I do have the drivers for the nexus installed. I can't directly drop files through windows because it doesn't read in recovery and read up upon researching the Side load function. So I downloaded the ABT bundle zip folder and placed it in C folder, but that's where i'm stuck. I've tried looking a few things up but every time i try to run Adb command in the platforms folder it just opens and closes within a second. not sure what i'm missing. i've tried looking at other ways but most other phones have the capability of just throwing it on to the SD card which helps other people. thanks in advance.
Tl:dr Need to get a rom file onto the Nexus, to install and repair my corrupted rom.

you run adb from COMMANDLINE, it sounds like you are trying to double click the adb.exe....that will never work. adb is a commandline tool

ok, i'm pretty much a noob, don't know how to do that but i'll google it first before i bug any more. thanks again.

Since you are using windows, while looking at the explorer window that contains the adb/fastboot exes, hold down shift and right click somewhere in the blank space within the folder...OPEN COMMAND WINDOW HERE
once you have a DOS prompt open in that location, type 'adb devices' without any quotes to see if your device is being recognized.
there is an entire thread dedicated to walking you through this whole process.
start reading here:
http://forum.xda-developers.com/showthread.php?t=1812959
this site contains all the info you need.

I googled it and got it set up and working. it does recognize my device. now i'm reading up on the command to send the zip file. seriously, thanks for the feedback. been sitting here for like 2 hours trying to figure this out without pulling out my hair and tossing the phone lol.

You could have just read the stickies... Why people don't get curious about things like "RETURN TO STOCK ON ANY GALAXY NEXUS VARIANT" or "ANDROID 101", I'll never understand.
a manta wrote this.

f*cked up phone

first of all i want to say that I almost know nothing about rooting and stuff.
I rooted my phone with the all-in-one toolkit and actually didn't know what I was doing. I was just clicking next and did what the screen told me to do. Everything went great and i had no problems until know. I downloaded and flashed the venom dotview tweak but it didn't work and the normal dot view which I reinstalled also didnt work so I decided to do a recovery from the settings app. it was really stupid to do that beacause my softkeys and statusbar are gone know and the flashed apps are still there. Is there a way to have my phone like it was when I bought it? I don't need a root anymore, I just want my phone getting to work normal.
Thanks

CrankyPants said:
first of all i want to say that I almost know nothing about rooting and stuff.
I rooted my phone with the all-in-one toolkit and actually didn't know what I was doing. I was just clicking next and did what the screen told me to do. Everything went great and i had no problems until know. I downloaded and flashed the venom dotview tweak but it didn't work and the normal dot view which I reinstalled also didnt work so I decided to do a recovery from the settings app. it was really stupid to do that beacause my softkeys and statusbar are gone know and the flashed apps are still there. Is there a way to have my phone like it was when I bought it? I don't need a root anymore, I just want my phone getting to work normal.
Thanks
Click to expand...
Click to collapse
Restore you stock ROM nandroid. Look for it in here COLLECTION of Stock backup's seeing as you really didn't bother to provide us with the relevant and more important information such as the CID and Main software version you were on before you decided to mess your phone up and I doubt you made a backup of your device before doing it.

Is your phone still recognized by a pc?
If so, just load another ROM on your sd card.. Wipe everything and flash through recovery. You'll lose all your data, but your phone will be back.
Since you are new to this - CONGRATS! You just learned the most important rule of flashing. Always make a backup first!
Good luck man. It's an easy fix.

I guess I will be the "bad guy" but why are you messing with your phone when you have no clue what you are doing?

Everyone starts somewhere. Im sure we all learned a lot of what we know now by making lots of stupid mistakes. This logic rings true for life... not just phones.

lucas.scott said:
Is your phone still recognized by a pc?
If so, just load another ROM on your sd card.. Wipe everything and flash through recovery. You'll lose all your data, but your phone will be back.
Since you are new to this - CONGRATS! You just learned the most important rule of flashing. Always make a backup first!
Good luck man. It's an easy fix.
Click to expand...
Click to collapse
yes and no, my pc sees him but the phone folder is empty en htc manager gives an error. any idee how to put a rom on the phone?

CrankyPants said:
yes and no, my pc sees him but the phone folder is empty en htc manager gives an error. any idee how to put a rom on the phone?
Click to expand...
Click to collapse
Unlock bootloader,install a custom recovery via adb then download a custom rom of your choice then move it to ext/internal sd.you may use otg.Then go to the custom recovery(TWRP/Cwm/philz) wipe then install zip through the location.

Jyotirdeb said:
Unlock bootloader,install a custom recovery via adb then download a custom rom of your choice then move it to ext/internal sd.you may use otg.Then go to the custom recovery(TWRP/Cwm/philz) wipe then install zip through the location.
Click to expand...
Click to collapse
How to install a custom recovery via adb and what is adb?
sorry I don't know anything

CrankyPants said:
How to install a custom recovery via adb and what is adb?
sorry I don't know anything
Click to expand...
Click to collapse
This is why you shouldn't use all in one toolkits, you don't learn anything like that and if you're not willing to learn then you probably shouldn't mess around with these things in the first place, expect others to then fix the problems for you. I'm not trying to be mean here, just stating fact.
Download the Android SDK
After downloading, extract the .zip file. Then go into folder inside the sdk folder you'll find a folder named "platform-tools" right click that folder and copy it on your desktop(Ease of access). Inside that platform-tools folder you'll find the applications adb and fastboot.
Download HTC Sync Manager in order to install the drivers(If you haven't done so already and just to be sure).
Download custom recovery, either Philz CWM Recovery or TWRP Recovery . Place the downloaded .img recovery file inside the platform-tools folder.
Make sure your phone has USB-Debugging enabled, if you don't have developer mode on phone. Go to Settings > About > Software Information > More > Tap 7times on Build Number. This will enable developer options. Go back to Settings and scroll down to Developer Options, open it and enable USB Debugging.
Connect your phone to the PC, make sure to accept any prompts that might appear on the phone then inside the platform-tools folder, hold shift then right click, then select "Open Command prompt here". Type adb devices if adb picks up your device it'll show you your devices serial number. Next type adb reboot bootloader to boot into bootloader mode then type fastboot devices again just to make sure the device is connected and being picked up by the prompt. Type fastboot flash recovery name_of_recovery_you_downloaded.img MAKE SURE you type in the correct name for the recovery, exactly the same!!!
When it's done, flash ROM of your choice.

I'm a beginner too, but I learnt loads from watching videos from a channel called Sakitech on YouTube. I watched them over a few times to understand the process before doing anything.
Unlook bootloader:
https://www.youtube.com/watch?v=rEVSfwXsx-c&index=3&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA
Turn S-Off:
https://www.youtube.com/watch?v=--Hlms1BuPg&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA&index=4
Install a custom recovery and root your phone
https://www.youtube.com/watch?v=WuHFcGvUjwA&feature=youtu.be
Install a custom rom:
https://www.youtube.com/watch?v=t4KeVs5axtM
Remember to backup before you put your phone under serious surgery!
https://www.youtube.com/watch?v=eda67mn-oXc
Hope this helps.

leongwengheng said:
I'm a beginner too, but I learnt loads from watching videos from a channel called Sakitech on YouTube. I watched them over a few times to understand the process before doing anything.
Unlook bootloader:
https://www.youtube.com/watch?v=rEVSfwXsx-c&index=3&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA
Turn S-Off:
https://www.youtube.com/watch?v=--Hlms1BuPg&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA&index=4
Install a custom recovery and root your phone
https://www.youtube.com/watch?v=WuHFcGvUjwA&feature=youtu.be
Install a custom rom:
https://www.youtube.com/watch?v=t4KeVs5axtM
Remember to backup before you put your phone under serious surgery!
https://www.youtube.com/watch?v=eda67mn-oXc
Hope this helps.
Click to expand...
Click to collapse
Good choice on the videos, these days reading is a bit to tedious for most people. Heck, they don't even read "STOP" on the STOP signs anymore, just drive straight past

I have a super short attention span so I need YouTube to learn anything in life lol.
Sent from my HTC One_M8 using XDA Free mobile app

leongwengheng said:
I have a super short attention span so I need YouTube to learn anything in life lol.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Good luck at school then and later on in your job

Lucky boy having such a commited community here. You could've quite easily ended up with a £600 paper weight. Might want to show some appreciation to everyone holding your hand through a process that you should've read about before doing anything. Must admit, I did like the 'I just kept hitting next without knowing what I was doing', that's probably the best thing I've read lol lol.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

BerndM14 said:
This is why you shouldn't use all in one toolkits, you don't learn anything like that and if you're not willing to learn then you probably shouldn't mess around with these things in the first place, expect others to then fix the problems for you. I'm not trying to be mean here, just stating fact.
Download the Android SDK
After downloading, extract the .zip file. Then go into folder inside the sdk folder you'll find a folder named "platform-tools" right click that folder and copy it on your desktop(Ease of access). Inside that platform-tools folder you'll find the applications adb and fastboot.
Download HTC Sync Manager in order to install the drivers(If you haven't done so already and just to be sure).
Download custom recovery, either Philz CWM Recovery or TWRP Recovery . Place the downloaded .img recovery file inside the platform-tools folder.
Make sure your phone has USB-Debugging enabled, if you don't have developer mode on phone. Go to Settings > About > Software Information > More > Tap 7times on Build Number. This will enable developer options. Go back to Settings and scroll down to Developer Options, open it and enable USB Debugging.
Connect your phone to the PC, make sure to accept any prompts that might appear on the phone then inside the platform-tools folder, hold shift then right click, then select "Open Command prompt here". Type adb devices if adb picks up your device it'll show you your devices serial number. Next type adb reboot bootloader to boot into bootloader mode then type fastboot devices again just to make sure the device is connected and being picked up by the prompt. Type fastboot flash recovery name_of_recovery_you_downloaded.img MAKE SURE you type in the correct name for the recovery, exactly the same!!!
When it's done, flash ROM of your choice.
Click to expand...
Click to collapse
I have one problem. Since I don't have the notification bar anymore, the phone doesn't notificate me. How will I get the USB notification to work?

CrankyPants said:
I have one problem. Since I don't have the notification bar anymore, the phone doesn't notificate me. How will I get the USB notification to work?
Click to expand...
Click to collapse
If there's a pop up it'll show on screen, have you tried the adb devices command to see if your phone gets picked up?
Out of curiousity though, when you used the toolkit didn't you have to enable USB Debugging anyway? I'm not familiar with the toolkit, don't use it myself...? If you already enabled it then it's fine, as long as adb devices picks up your device then you're good to go.

BerndM14 said:
If there's a pop up it'll show on screen, have you tried the adb devices command to see if your phone gets picked up?
Out of curiousity though, when you used the toolkit didn't you have to enable USB Debugging anyway? I'm not familiar with the toolkit, don't use it myself...? If you already enabled it then it's fine, as long as adb devices picks up your device then you're good to go.
Click to expand...
Click to collapse
My device is already wiped so I have no configurations anymore.
I have no softkeys and no statusbar anymore since I recovered my phone with the settings app. So no statusbar means no pop-ups.
The adb devices command sees my device in the list of devices but next to it, it says 'offline'. when normaly it has to say 'device'.

CrankyPants said:
My device is already wiped so I have no configurations anymore.
I have no softkeys and no statusbar anymore since I recovered my phone with the settings app. So no statusbar means no pop-ups.
The adb devices command sees my device in the list of devices but next to it, it says 'offline'. when normaly it has to say 'device'.
Click to expand...
Click to collapse
You see it's supposed to throw a small pop up on the screen of the phone where it wants you to accept the RSA key to connect it to PC. It doesn't have anything to do with the softkeys or the notification bar on the top, it's supposed to be on the screen. I take it you probably can't even get into app drawer anymore in order to go to settings. Doesn't give any pop up on the screen... I think you really did f*** up your device
Did you use Hasoon2000's all in one toolkit? If so you probably had to have flashed a custom recovery, it's like the very next thing to do after you unlock bootloader?

BerndM14 said:
You see it's supposed to throw a small pop up on the screen of the phone where it wants you to accept the RSA key to connect it to PC. It doesn't have anything to do with the softkeys or the notification bar on the top, it's supposed to be on the screen. I take it you probably can't even get into app drawer anymore in order to go to settings. Doesn't give any pop up on the screen... I think you really did f*** up your device
Did you use Hasoon2000's all in one toolkit? If so you probably had to have flashed a custom recovery, it's like the very next thing to do after you unlock bootloader?
Click to expand...
Click to collapse
les us assume he is in stock.So he should have a stock recovery.now Boot into fastboot get the details fastboot getvar all.you will find the mid of your choice.download international fw's ruu open the zip there will be an android-info.txt file.edit the file with your mid(change 0P6B10000 to 0P6BXXXXX) where XXXXX represents your mid.then flash the ruu via recovery.Since he connects his device adb will at least detect it (i hope).
Also open toolkit on the right side it is written "next flash a recovery". Connect your phone and simply select twrp and press flash recovery.this should do it.For more details ask hasoon.

Jyotirdeb said:
les us assume he is in stock.So he should have a stock recovery.now Boot into fastboot get the details fastboot getvar all.you will find the mid of your choice.download international fw's ruu open the zip there will be an android-info.txt file.edit the file with your mid(change 0P6B10000 to 0P6BXXXXX) where XXXXX represents your mid.then flash the ruu via recovery.Since he connects his device adb will at least detect it (i hope).
Also open toolkit on the right side it is written "next flash a recovery". Connect your phone and simply select twrp and press flash recovery.this should do it.For more details ask hasoon.
Click to expand...
Click to collapse
To get getvar all you'll need fastboot commands, will fastboot commands even work if he MIGHT not have enabled USB Debugging or for that matter haven't accepted the RSA key?
That's why I asked about the recovery as well though. I saw that on hasoon's toolkit the flashing of a custom recovery was like the next step on the process which means that this guy should at least have a custom recovery already installed.

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!