Hi everyone. I have a rooted unlocked Nexus 6 with no recovery and (obv) no Android on it. Basically its just an emply mobile phone shell. I know there is plenty life left in it so I would like to make it work again. Either flash TWRP or the Stock recovery I dont mind as long as I can use it again. Im kinda stuck, very inexperienced with all this. Can any one point me with the right direction please? I understand I can only use it with terminal since there is absolutely nothing in the phone.
Anyone please?
If you know how to install TWRP then you can copy any Nexus 6 custom ROM to the device and flash it - with Gapps Pico Arm (not Arm64) if you want Google services.
If it's "empty" how do you know it's rooted?
This phone usually only becomes empty if there is serious problems with the storage - if that is the case, it's unlikely to be fixable. How did it happen?
But if the storage is still OK, and the phone really is unlocked, you can download a stock rom from Google, and flash it using fastboot:
1) install fastboot on your computer
2) start the phone in bootloader mode
3) run the batch file included with the download
(Or do it like dahawthorne said to get a custom rom - provided that the radio-partition still has its contents intact).
Related
I know this is a re-hash of previous questions but coming from the MyTouch3G the nexus one is a bit odd.
I don't want to void the warranty and thus lose my warranty. I've done the 1-click root which allows me to run a couple of apps as su.
But it seems to stop there.
I would really like to checkout some of the custom roms, as my current froyo is messing up pretty bad on all browser connection (very frustrating)
On the MT3G I've never really had to do any adb/fastboot stuff as the images were pretty self-contained and installed all that was needed.
On the nexus one it seems pretty hard to find good steps on the stock bootloader so that I can go back to stock if needed.
On to the questions after all of this:
1. ADB sees the device, yet fastboot doesn't. Any tips?
2. Can I backup the current bootloader/rom via adb/fastboot?
3. Can I install the RA Recovery without unlocking the bootloader, or does that pretty much go hand in hand?
4. If a custom recovery cannot be installed, then I'm guessing no custom roms can either be used, is this correct?
Thanks!
1. use the correct fastboot binary (what os?)
2. no need
3. yes
4. yes
Just unlock the bootloader, there are numerous accounts of getting the phone repaired regardless.
just install rom manager (if for nothing else it will install a recovery on your phone) then you never have to use the program again. It will not mess with the boot loader or anything else.
Its free in the market, the nexus one is the easieest phone to swap roms and such
You don't need another application to install a recovery image, just terminal. flash_image recovery /sdcard/name of recovery.img
yeah but some people dont use ADB, and an app is easier
That's a terminal command, not adb. But can also be executed via adb shell.
either way, often rom manager is simpler to use for people new to rooting and custom rom flashing
The problem
I have a rooted Xperia T, unlocked bootloader, and now I would like to flash a CM rom (10.1.3 stable). I have attempted to use some tutorials to simply boot into recovery using GooManager (flashing TWRP) or ROM Manager (flashing CWMR), but neither of these seem to work - when I attempt to boot into recovery, my phone simply reboots normally.
I then have tried to flash CWMR from my computer (I have a mac), and I can do fine until I reach a message in terminal detailing a failure that I can't seem to find elsewhere on the internet. (See screenshot)
So, I have hit a dead end - can't flash recovery on device, can't flash recovery via desktop.
Screenshots
View attachment 2703144 View attachment 2703145 (Click to enlarge)
Details
USB debugging is enabled
When I am in fastboot the LED is blue (correct fastboot, I rooted my phone)
I have downloaded the CM .zip, the necessary gapps, and have backed up my apps 'n data with TB and simply copying files
I renamed the recovery on my desktop from 15102012.img (as I downloaded it) to cwmrecovery.img for ease of use
What is the problem on my device and on terminal?
What can I do to fix either?
Is there a step I have missed?
Have I missed a really obvious detail (if so, I feel really bad...)
If you need anything else to help me, just let me know.
Thanks guys.
Gepru said:
The problem
I have a rooted Xperia T, unlocked bootloader, and now I would like to flash a CM rom (10.1.3 stable). I have attempted to use some tutorials to simply boot into recovery using GooManager (flashing TWRP) or ROM Manager (flashing CWMR), but neither of these seem to work - when I attempt to boot into recovery, my phone simply reboots normally.
I then have tried to flash CWMR from my computer (I have a mac), and I can do fine until I reach a message in terminal detailing a failure that I can't seem to find elsewhere on the internet. (See screenshot)
So, I have hit a dead end - can't flash recovery on device, can't flash recovery via desktop.
Screenshots
View attachment 2703144 View attachment 2703145 (Click to enlarge)
Details
USB debugging is enabled
When I am in fastboot the LED is blue (correct fastboot, I rooted my phone)
I have downloaded the CM .zip, the necessary gapps, and have backed up my apps 'n data with TB and simply copying files
I renamed the recovery on my desktop from 15102012.img (as I downloaded it) to cwmrecovery.img for ease of use
What is the problem on my device and on terminal?
What can I do to fix either?
Is there a step I have missed?
Have I missed a really obvious detail (if so, I feel really bad...)
If you need anything else to help me, just let me know.
Thanks guys.
Click to expand...
Click to collapse
I would say, try to do it on a native Windows 7 pc. No VMware or something. That's the most safe/relieable option you have.
Alright, I returned to the problem and found a solution:
I installed TWRP via Flashtool for mac, and from there it all went swimmingly. The fact that I forgot to put the CM ROM on my phone was a little stupid, but that too worked out in the end.
Typed happily on my CM 10.2.0 Xperia T
What CM 12 ROM you used?
Gepru said:
Alright, I returned to the problem and found a solution:
I installed TWRP via Flashtool for mac, and from there it all went swimmingly. The fact that I forgot to put the CM ROM on my phone was a little stupid, but that too worked out in the end.
Typed happily on my CM 10.2.0 Xperia T
Click to expand...
Click to collapse
I am using 10.2.0, mint.
Not 12
Ops...
Just a thing: on CM 10.2, have you got problems with microphone? I've used CM starting from last release (11) and I've always found that mic gain is too high. This cause that every record I do is too overdriven.
Can you test it, recording a vocal track very close to mic? I've always liked AOSP based ROM, but this issue made me came back to stock ROM.
Thanks in advance for the reply!
Gepru said:
I am using 10.2.0, mint.
Not 12
Click to expand...
Click to collapse
Im not an expert but have tried almost everything i could find on the web relating to my issue.
Sucessefully rooted with motochopper
Bootloader unlocked by motopocalypse
Now when it comes to entering recovery mode through Rom Manager or GooManager i always end up with the dead android.
Even device update also failed and ends up the same way.
I have already deleted install-recovery.sh but to no avail.
I want to install SlimKat on my device, only thing in my way is a Dead Android whenever i try to enter recover mod. PLEASE HELP.
Motorola Atrix HD
98.4.20.MB886.ATT.en.US
Android 4.1.1
andrewyp said:
Im not an expert but have tried almost everything i could find on the web relating to my issue.
Sucessefully rooted with motochopper
Bootloader unlocked by motopocalypse
Now when it comes to entering recovery mode through Rom Manager or GooManager i always end up with the dead android.
Even device update also failed and ends up the same way.
I have already deleted install-recovery.sh but to no avail.
I want to install SlimKat on my device, only thing in my way is a Dead Android whenever i try to enter recover mod. PLEASE HELP.
Motorola Atrix HD
98.4.20.MB886.ATT.en.US
Android 4.1.1
Click to expand...
Click to collapse
Do you have a custom recovery already installed? Which one? If you don't, remember that in order to flash a new ROM, you need to install a custom recovery.
mauchito said:
Do you have a custom recovery already installed? Which one? If you don't, remember that in order to flash a new ROM, you need to install a custom recovery.
Click to expand...
Click to collapse
Guess i missed this. I will try to do that and update you. Incase you have any guide to direct me too please do so, otherwise i will try to figure it out. Thanks.
andrewyp said:
Guess i missed this. I will try to do that and update you. Incase you have any guide to direct me too please do so, otherwise i will try to figure it out. Thanks.
Click to expand...
Click to collapse
Sure, buddy.
You need to download a custom recovery, this is the option in Android that lets you erase all content in the device and do other things. With a custom recovery you can do even more things, like install .zip archives or ROMs, erase partitions, dalvik cache, etc, etc, a lot of things.
I personally use this one: http://forum.xda-developers.com/showthread.php?t=2552622
Since you are already rooted, I think that you are familiar with fastboot. In order to flash a custom recovery, you need to do this:
1. Download the custom recovery
2. If it's in a .zip, extract the archive so you have one *.img archive.
3. Then, copy that file to the folder where you have the fastboot.exe archive.
4. Open Windows command console and change the directory to the one where you have the files.
5. Turn off your device, then press volume down key and power key. Hold until you see a black screen with white letters. Connect via USB to your computer.
6. Run the following command in the command console of Windows:
fastboot flash recovery recovery.img
Where "recovery.img" is the name of your custom recovery archive, for example, "philz_touch_6.22.7.img"
7. Wait about 6 seconds and in the console you should see something like "done", I don't remember exactly what does it says.
8. You are good to go. Turn off your device. Then press the volume up key and power button. Hold until you see the custom recovery interface.
After this point, you can flash the custom ROM of your preference.
In the Philz link above, it goes to our thread that links to the main one, from there, download the unified moto-msm8960 one labeled for xt925/xt926. Last time I checked it was more up to date than the native mb886 one (not surprising since our CM repo is gone).
Hey guys,
I recently purchased a Mi5 in China and had a hellish experience trying to get a working rooted international ROM on it even though I am definitely not a noob at android. I found out that most issues I had were result of small/stupid mistakes that can be easily avoided with the proper knowledge, so I decided to write a super quick how to on the process for anyone that might need it in the future. There are similar guides out there, and I will refer to some (all credit goes to original posters) but I found that most are incomplete/not updated/plain wrong. Please also note that this guide is updated to June 20th, newer ROM versions might require different steps.
This how to assumes you are familiar with the standard ROM flashing process, in case anyone needs a more detailed explaination of some of the steps, you can reply or search XDA elsewhere, most of the stuff has been mentioned here and there before.
1. Check that your hardware is ok (dial *#*#64663#*#* in dialer, you will enter hardware test mode, check every single item carefully)
2. Request a bootloader unlock from Xiaomi, unlock the bootloader: follow instructions here http://forum.xda-developers.com/mi-5/how-to/unlocking-xiaomi-mi-5-bootloader-t3336243
3. Now that Your bootloader is unlocked, you have 3 main options for working ROMs: Xiaomi's Global Stable, Xiaomi's Global Dev, Xiaomi.eu's unofficial Stable. If you want to play it safe, I suggest to go with the Xiaomi's Global Stable, otherwise choose Xiaomi.eu's unofficial Stable. I did not test extensively all three, so this is just a general recommendation.
4. In any case, you will need to use the official Xiaomi's flashing tool (Miflash) to do your first ROM flash. Just follow the process here: http://en.miui.com/a-234.html and you'll have flashed your new ROM. In case you want to flash Xiaomi.eu's unofficial Stable, follow the same process but get the flashable ROM here: https://xiaomi.eu/community/threads/xiaomi-eu-multilang-rom-for-xiaomi-mi5-unlocked-bl-only-released.31231/
5. Boot into your newly flashed ROM, check once again that hardware is ok (see step 1.). Please also see step 10b for a tidbit of additional info if You're in China.
6. Reboot into bootloader, boot (only boot, no need to install) TWRP, which you can find here as part of Xiaomi.eu's thread above in step 4. inside a zip packaged with a modded bootloader image. do NOT install the modded bootloader image. Also, this is the only version of TWRP that I found working for my device. There are a couple more versions from chinese developers (cofface, ganfan), but booting either resulted in blank screen.
7. Once you are in TWRP, the recovery will ask you for a decryption password, just press cancel, then "Swipe to allow modifications"
8. Sideload (you cannot install from internal storage since you will not be able to access it at the moment) the latest SuperSU stable, which you can find here: http://forum.xda-developers.com/showthread.php?t=1538053. Please note that you WILL need the latest version, anything earlier might just get you a bootloop. And please do NOT format /Data to make it accessible to TWRP as that will also likely result in bootloop. Just sideload whatever you need.
9. Do NOT wipe Dalvik or Cache, reboot into System.
10. Congrats, You're done. Have a beer/coffee/tea and pat yourself on the back.
10b. In case You're in China, and this is Your first Android 5.0+ ROM, you will happen into a "bug" (it's not really a bug, but a result of China's Great Firewall), where whenever you connect to a Wifi, the phone will think you have no internet access and that will cause a whole host of issues (won't reconnect automatically, will try to default to 4G etc.). If so, just enable ADB Debugging and type adb shell "settings put global captive_portal_server httpstat.us/204" . That will mostly solve it (you might still get some weird result with some APs, but toggling Wifi should solve the problem for that AP forever.
Lazer Bear said:
6. Reboot into bootloader, boot (only boot, no need to install) TWRP, which you can find here as part of Xiaomi.eu's thread above in step 4. inside a zip packaged with a modded bootloader image. do NOT install the modded bootloader image. Also, this is the only version of TWRP that I found working for my device. There are a couple more versions from chinese developers (cofface, ganfan), but booting either resulted in blank screen.
Click to expand...
Click to collapse
How do you boot into twrp without flashing it? fastboot boot recovery.img doesn't work for me.. the command was successfull, downloading to the phone, then it's telling me booting, but the phone stay in fastboot.. thx
m_adnan said:
How do you boot into twrp without flashing it? fastboot boot recovery.img doesn't work for me.. the command was successfull, downloading to the phone, then it's telling me booting, but the phone stay in fastboot.. thx
Click to expand...
Click to collapse
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Lazer Bear said:
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Click to expand...
Click to collapse
no, nothing happens on the screen, it stays in fb mode without any reaction. adb and fb devices doesn't return any device connected.. if i do an fb reboot it told me "waiting for any device" so the only option to get it run again is to power off.. yes of course, it's the recovery.img with the modified boot.img..
Lazer Bear said:
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Click to expand...
Click to collapse
i want only to inform you, i get it to work.. the problem was my rom, miui 8.. for miui 8 you will need a new version of twrp, which you can download here: https://yadi.sk/d/oj6Z-0u7sXdw6 after that, i was able to boot to the twrp recovery without flashing it, so i keept everything original like it was and was able to sideload the supersu and get root without to format my data.. when you start the recovery it came in chinese, but when you click on the right button you can choose your language.. that's it.. thank you for you support dude!!
Is it only way to switch from chinese ROM to official global ROM to have unlocked bootloader? If it is, is there any other way of unlocking it, waiting 15 days to get permission seems ridiculous.
Lovely step by step guide. But, any idea if it will wipe the user data and/or internal sdcard when moving from the chinese to international version?
Hi,
I'm working with a Huawei Honour 4x, Android 6.0, Stock Rom, Model: CHE-TL00, EMUI 4.1
I'm looking to root it but could not find anything specific on google or XDA. I've read about systemless root for Android 6.0 but the material largely concerns the nexus phones.
I've got quite an odd brand with a specific model make which differs from other models of the Honour 4x.
Simply put, i'd like to root the device. Can anyone point me towards more information to achieve this ?
I've searched and failed. I'm hoping someone else may know where to look.
#Update: I have twrp installed.
#Update 2: I used TWRP to flash SuperSU. My phone failed to boot afterwards and kept looping. So i recovered using the Nandroid backup.
Back to square one. Any help would really appreciated.
#Update 3: Problem Solved. For anyone who has the same device, here are the steps to take.
1. Flash TWRP using Minimal ADB Flash and Boot
2. Use TWRP to flash the updated version of SuperSU (2.71 Beta). (HAS TO BE THIS VERSION or the latest version!!!)
Used: [BETA-SuperSU-v2.74-2-20160519174328-forced-systemless] or [BETA-SuperSU-v2.71-20160331103524]
3. Reboot; wait for a few minutes for phone to load.
4. Job done. Your phone should be rooted.
TWRP source: https://twrp.me/huawei/huaweihonor4x.html
Thanks for your sharing.
Hi, I recently updated to the 6.0 Rom and am trying to root it (using your guide)
1. Flash TWRP using Minimal ADB Flash and Boot
2. Use TWRP to flash the updated version of SuperSU (2.71 Beta). (HAS TO BE THIS VERSION or the latest version!!!)
Used: [BETA-SuperSU-v2.74-2-20160519174328-forced-systemless] or [BETA-SuperSU-v2.71-20160331103524]
3. Reboot; wait for a few minutes for phone to load.
4. Job done. Your phone should be rooted.
Click to expand...
Click to collapse
I can get my device to reboot into fastboot but it doesn't recognise the device after that?
(Just says "Waiting for device", and nothing shows up if I type 'Fastboot Devices')
Could you tell me what drivers you used? I really want to root it to try and get some space back
follow the steps anyway, dont worry if it say conecting in hisuite, and be sure u have hisuite installed, i.e, u have an hisuite.exe in the folder C:\Program Files (x86)\HiSuite\ .... and for the space, in hi suite desktop app u can uninstall some, goodluck!
Coedy said:
Hi, I recently updated to the 6.0 Rom and am trying to root it (using your guide)
I can get my device to reboot into fastboot but it doesn't recognise the device after that?
(Just says "Waiting for device", and nothing shows up if I type 'Fastboot Devices')
Could you tell me what drivers you used? I really want to root it to try and get some space back
Click to expand...
Click to collapse
I had the same issue. There're a lot of bloatware apps pre-installed which take up crucial internal space. It seems like it is a driver issue.
My process of achieving root was essentially trial and error, so there was a lot of google searching and installing; without making note of everything i installed (when concerning drivers).
So i won't pretend to be an expert but I'll list the most useful places i checked out.
Firstly, i download the basic Android command line tools from the SDK webpage.
Secondly, i followed the steps on the TWRP webpage (can't link as i'm a new user) I download their recommended drivers too.
Thirdly, (Since Huawei do support modification to an extent, you can find a set of their recommended drivers on google or on their webpage). I googled a set of USB drivers for the Honor 4x and downloaded these too.
Following this, I was able to connect my device successfully.
(Failing this, Google has a lot of content on connecting the Honour to Minimal ADB Flash and Boot. Check it out.) :good:
sr993 said:
Hi,
#Update 2: I used TWRP to flash SuperSU. My phone failed to boot afterwards and kept looping. So i recovered using the Nandroid backup.
Click to expand...
Click to collapse
Hi, my model is Ch2-L11 and I'm very noob and very likely to mess up the whole phone, so I was wondering How did you created a nandroid backup?
I installed the minimal adb tool that you suggested in your post. should I use "adb backup all" in cmd? or creating a nandroid backup is different?
Why not sharing where you sourced the TWRP you used is a mystery and makes this correctly referenced thread rather worthless.
thanks for share..