First,
*
Grateful for the help and attention of those who saw it then
*
My problem is the following,
I own a Razr - XT890 JB. (To my knowledge, the last update provided by Software him, was the "Claro Brazil")
*
I modified my build.prop Mobile, everything went well,
More on grounds of extreme stupidity mine, I opted to return the original
however, when you replace the file did not give priority to the recording file, as it should have done, and rebooted the machine, all unintentionally;
*
From there, caught in the Bootloader screen
*
I tried different ROMs, which came closest is the XDA Rom,RazRi_JB_X-2014-Jul-11.zip
She reaches in the Rom Boot screen, install everything perfectly, plus al relates to a Bootloader,
Other Roms give error, or error in / system / build.prop other give that error related command line "getvar max-download-size"
*
Please, I request immediate help, RSD does not also recognize the device to which the installation commands from it, and I have no great knowledge to try to "solo" via SDK commands, correct me about the errors.
*
But here I am, if you have a forum that I still have hope that helps me is this,
*
If anyone can (and if they work of course) upload or give me a link of a BKP-ROM of this apparatus, I believe that giving the System Restore Partition with Original Build.prop everything is working again, I searched for a good gringos forums , and saw some similar cases are resolved well, but with other devices.
*
*
I hope I was clear enough.
*
*
Without more,
Thank you again.
From A very desperate Brazilian
klizardstz said:
First,
*
Grateful for the help and attention of those who saw it then
*
My problem is the following,
I own a Razr - XT890 JB. (To my knowledge, the last update provided by Software him, was the "Claro Brazil")
*
I modified my build.prop Mobile, everything went well,
More on grounds of extreme stupidity mine, I opted to return the original
however, when you replace the file did not give priority to the recording file, as it should have done, and rebooted the machine, all unintentionally;
*
From there, caught in the Bootloader screen
*
I tried different ROMs, which came closest is the XDA Rom,RazRi_JB_X-2014-Jul-11.zip
She reaches in the Rom Boot screen, install everything perfectly, plus al relates to a Bootloader,
Other Roms give error, or error in / system / build.prop other give that error related command line "getvar max-download-size"
*
Please, I request immediate help, RSD does not also recognize the device to which the installation commands from it, and I have no great knowledge to try to "solo" via SDK commands, correct me about the errors.
*
But here I am, if you have a forum that I still have hope that helps me is this,
*
If anyone can (and if they work of course) upload or give me a link of a BKP-ROM of this apparatus, I believe that giving the System Restore Partition with Original Build.prop everything is working again, I searched for a good gringos forums , and saw some similar cases are resolved well, but with other devices.
*
*
I hope I was clear enough.
*
*
Without more,
Thank you again.
From A very desperate Brazilian
Click to expand...
Click to collapse
As i can read from your post, u do have an unlocked bootloader and u do have installed a custom recovery. U can access the recovery and wipe partitions. If so, all can be solved.
A build.prop change may get you a bootloop, but shouldn't be able to remove the device installation methods and booting of other roms.
There is a huge chance that something in your data partition doesn't match the things that the rom wants to boot, so u get the bootloop. What it is can be difficult to say, only a logcat can provide answers if it works.
There are 4 methods to solve this.
1. hope logcats works and find the root of the problem (can be very difficult, if u dont know what logcat does and how it works)
2. download a custom rom, wipe the system, data and cache partitions and install a fresh custom rom
3. download your newest firmware from here and install by RSD lite when in Fastboot mode (power + volume down)
4. manually flash and wipe the new firmware
D:
Hazou said:
As i can read from your post, u do have an unlocked bootloader and u do have installed a custom recovery. U can access the recovery and wipe partitions. If so, all can be solved.
A build.prop change may get you a bootloop, but shouldn't be able to remove the device installation methods and booting of other roms.
There is a huge chance that something in your data partition doesn't match the things that the rom wants to boot, so u get the bootloop. What it is can be difficult to say, only a logcat can provide answers if it works.
There are 4 methods to solve this.
1. hope logcats works and find the root of the problem (can be very difficult, if u dont know what logcat does and how it works)
2. download a custom rom, wipe the system, data and cache partitions and install a fresh custom rom
3. download your newest firmware from ## and install by RSD lite when in Fastboot mode (power + volume down)
4. manually flash and wipe the new firmware
Click to expand...
Click to collapse
Sorry for the delay dear friend.
I am currently without a computer and unable to respond, since the cell has not returned to work,
tried the "LogCat" and without success, a message that has no logs, not even the XDA App worked,
Should I start worrying?
Also already tried several ROM'S, the only one that installs with success is that I found here on XDA, however the bootloop, since other, or withdrawing the "GetJar" they conclude.
Someone to help this desperate soul?
Grateful friends.
You are my last hope.
klizardstz said:
Sorry for the delay dear friend.
I am currently without a computer and unable to respond, since the cell has not returned to work,
tried the "LogCat" and without success, a message that has no logs, not even the XDA App worked,
Should I start worrying?
Also already tried several ROM'S, the only one that installs with success is that I found here on XDA, however the bootloop, since other, or withdrawing the "GetJar" they conclude.
Someone to help this desperate soul?
Grateful friends.
You are my last hope.
Click to expand...
Click to collapse
I don't get you very good. Just answer my questions so i understand your situation better.
1. How are u installing those roms?
2. Do u have a custom recovery?
3. If u have a custom recovery do u have a nandroid backup to restore your data?
4. If u are installing a new rom from here on xda, do u format system, data, cache? (full wipe)
5. If u still don't know. Read "INDEX/GUIDE, ALL Things RAZR I". Link under this. And go to "J". Read the instructions and read how to use RSD-Lite and were to download your latest firmware.
I have the feeling u are new to android. (maybe i am wrong, sorry) Just an advise for further things, always have a backup plan.
Hope this helps, i will hear it.
Hazou said:
I don't get you very good. Just answer my questions so i understand your situation better.
1. How are u installing those roms?
2. Do u have a custom recovery?
3. If u have a custom recovery do u have a nandroid backup to restore your data?
4. If u are installing a new rom from here on xda, do u format system, data, cache? (full wipe)
5. If u still don't know. Read "INDEX/GUIDE, ALL Things RAZR I". Link under this. And go to "J". Read the instructions and read how to use RSD-Lite and were to download your latest firmware.
I have the feeling u are new to android. (maybe i am wrong, sorry) Just an advise for further things, always have a backup plan.
Hope this helps, i will hear it.
Click to expand...
Click to collapse
Answers:
1 - Various shapes, tried by RSD 6.1.5 and also tried the 6.1.4, I have tried sideloading, and the Recovery of the XT890, both insalam not only the rom I mentioned above
2 - If by "Custom Recovery" you referred to CWM own the "CWM-based Recovery v6.0.1.5" version (Otherwise understand the fast stuff, just redirect me what you mean.)
3 - I do not have backups, just a backup I made before starting the procedures, then my build.prop is still without overwriting permissions
4 - Yes, always before any attempts, I place one Wipe data / factory reset, and still enter the sector of partitions and format the partitions, I'll mount / system, / cache, / data, / and the inside of virtual which is represented as a SDCARD format, all of them, and then install the ROM.
5 - As for reading, I'll check, As the experience in Android, I am not so layman, plus the more technical parts'm starting to learn now, as self-taught, I have extensive knowledge in the areas of computer science and a good reasoning, I believe it will be easy to be guided by you;
Thanks again for the attention paid to me. :good:
klizardstz said:
Answers:
1 - Various shapes, tried by RSD 6.1.5 and also tried the 6.1.4, I have tried sideloading, and the Recovery of the XT890, both insalam not only the rom I mentioned above
2 - If by "Custom Recovery" you referred to CWM own the "CWM-based Recovery v6.0.1.5" version (Otherwise understand the fast stuff, just redirect me what you mean.)
3 - I do not have backups, just a backup I made before starting the procedures, then my build.prop is still without overwriting permissions
4 - Yes, always before any attempts, I place one Wipe data / factory reset, and still enter the sector of partitions and format the partitions, I'll mount / system, / cache, / data, / and the inside of virtual which is represented as a SDCARD format, all of them, and then install the ROM.
5 - As for reading, I'll check, As the experience in Android, I am not so layman, plus the more technical parts'm starting to learn now, as self-taught, I have extensive knowledge in the areas of computer science and a good reasoning, I believe it will be easy to be guided by you;
Thanks again for the attention paid to me. :good:
Click to expand...
Click to collapse
okey, so u have some experience. I just misunderstood you then. my bad, sorry.
Even with a full wipe/format of everything and installing a custom rom u can't get it to boot. It will stay in a bootloop or even worse, don't go past the bootloader unlock screen.
With RSD-Lite (administrator) 6.1.6, 6.1.5 and 6.1.4 and all the drivers installed correctly and ready to run it won't recognize your phone when it is in (ap) fastboot mode. And if it recognizes your phone. At what part does it give an error, what is the error in rsd-lite/phone screen? Getvar error is more like a warning. We can disable that one.
Never seen this what u have. Because u can get into recovery, but the device won't boot. Will wait at your next post to confirm the above
Hazou said:
okey, so u have some experience. I just misunderstood you then. my bad, sorry.
Even with a full wipe/format of everything and installing a custom rom u can't get it to boot. It will stay in a bootloop or even worse, don't go past the bootloader unlock screen.
With RSD-Lite (administrator) 6.1.6, 6.1.5 and 6.1.4 and all the drivers installed correctly and ready to run it won't recognize your phone when it is in (ap) fastboot mode. And if it recognizes your phone. At what part does it give an error, what is the error in rsd-lite/phone screen? Getvar error is more like a warning. We can disable that one.
Never seen this what u have. Because u can get into recovery, but the device won't boot. Will wait at your next post to confirm the above
Click to expand...
Click to collapse
Yes, I have some experience, nothing more than apologize, who should apologize me for the inconvenience,
anyway ...
6.1.6 not tried, however, all other dao errors, and they are variable, depending on the rum,
Ex: Error 1/11, 6/12/8/10 and etc ...
already in CWM also varies, but with other command lines, and yes, even with all procedures, with pull and push the build.prop files, giving the command "chmod 644 build.prop" or even chmod 777 apparently can not the permiçoes there a way to delete the build, and relocate it on the partition / system?
also could not find any error like this, evil technology is that it seems that every problem is like a biological virus, mutates and hinders every time. LOL, since I do not know what to do: /
I look carefully your help friend.
* I've tried replacing build.prop, the original, by others, by the Galaxy S2, nothing more useless
as the part that mentioned at the end of your post, yes, I can do everything, however nothing stops the bootloop.
any suggestions?
klizardstz said:
Yes, I have some experience, nothing more than apologize, who should apologize me for the inconvenience,
anyway ...
6.1.6 not tried, however, all other dao errors, and they are variable, depending on the rum,
Ex: Error 1/11, 6/12/8/10 and etc ...
already in CWM also varies, but with other command lines, and yes, even with all procedures, with pull and push the build.prop files, giving the command "chmod 644 build.prop" or even chmod 777 apparently can not the permiçoes there a way to delete the build, and relocate it on the partition / system?
also could not find any error like this, evil technology is that it seems that every problem is like a biological virus, mutates and hinders every time. LOL, since I do not know what to do: /
I look carefully your help friend.
* I've tried replacing build.prop, the original, by others, by the Galaxy S2, nothing more useless
as the part that mentioned at the end of your post, yes, I can do everything, however nothing stops the bootloop.
any suggestions?
Click to expand...
Click to collapse
I have 2 more suggestions.
1. we manually flash/erase all things through mfastboot and see what happens.
2. We need a micro sdcard and we move the system partition from your phones internal memory to your sdcard, so it can boot from your sdcard. Because you have access to recovery and boot we can try this.
But i need some more time to write this up. especially the second thing. Never done it, but it is possible seen it before and read it. u can search around on the internet about those 2 things before we try anything. Will follow your post or edit this one with the worked out suggestions.
What i find weird about all this. U said u formatted all the partitions and even then with the right stock firmware from your mobile it wouldn't boot or anything. And the formatting off the partitions did work, so there should be no error anywhere normally. Because it does mean there is no memory error and the recovery can read and write stuff. U do have the xt890 and the right stock firmware (JB), don't u?
And next to that. After installing a new rom (with formatting of all partitions(system/cache/data)) u still try to change the build.prop. After a format it shouldn't be there anymore. Can u format everything (manually, not with full wipe, but with the options format system etc., again only system, cahce and ata or u can screw it even more ) again and see with adb through recovery if there is any file left on the system partition. Mount /system and do in adb shell in recovery a search for the build.prop. When in adb shell the command "ls system" should give u a list with all the files in it.
Hazou said:
I have 2 more suggestions.
1. we manually flash/erase all things through mfastboot and see what happens.
2. We need a micro sdcard and we move the system partition from your phones internal memory to your sdcard, so it can boot from your sdcard. Because you have access to recovery and boot we can try this.
But i need some more time to write this up. especially the second thing. Never done it, but it is possible seen it before and read it. u can search around on the internet about those 2 things before we try anything. Will follow your post or edit this one with the worked out suggestions.
What i find weird about all this. U said u formatted all the partitions and even then with the right stock firmware from your mobile it wouldn't boot or anything. And the formatting off the partitions did work, so there should be no error anywhere normally. Because it does mean there is no memory error and the recovery can read and write stuff. U do have the xt890 and the right stock firmware (JB), don't u?
And next to that. After installing a new rom (with formatting of all partitions(system/cache/data)) u still try to change the build.prop. After a format it shouldn't be there anymore. Can u format everything (manually, not with full wipe, but with the options format system etc., again only system, cahce and ata or u can screw it even more ) again and see with adb through recovery if there is any file left on the system partition. Mount /system and do in adb shell in recovery a search for the build.prop. When in adb shell the command "ls system" should give u a list with all the files in it.
Click to expand...
Click to collapse
I'll look around this friend, I wonder if I can really expect his return to the subject, you have been the one to support me here, and do not locate anything about the internet.
So your recommendation would be to wait or try to?
Because ruin even more ...
I have the sd card and just download the mfastboot-v2.zip
make a backup of the rom and try what then?
Is there any tutorial link, or can guide me trough this process?
If it is not possible to just show me that not of, and the way I try, the second part I do not know how to do, never read about it, but I will also look ...
Run the risk of damaging the hardware?
klizardstz said:
I'll look around this friend, I wonder if I can really expect his return to the subject, you have been the one to support me here, and do not locate anything about the internet.
So your recommendation would be to wait or try to?
Because ruin even more ...
I have the sd card and just download the mfastboot-v2.zip
make a backup of the rom and try what then?
Is there any tutorial link, or can guide me trough this process?
If it is not possible to just show me that not of, and the way I try, the second part I do not know how to do, never read about it, but I will also look ...
Run the risk of damaging the hardware?
Click to expand...
Click to collapse
Ok, to fast to much
First do this and post the results.
1. reboot in recovery
2. connect phone (in recovery mode) with usb to PC
3. check with adb if the pc can see the phone with the command: "adb devices". Should give u a device. Name should be a sequence of numbers
4. if in step 3 you get a phone. Type "adb remount" and enter
5. type: "adb shell" and enter
6. type: "mount /system" and enter
7. type: "ls /system" and enter
8. post the results of step 7.
We will see after this what to do next
Results
Hazou said:
Ok, to fast to much
First do this and post the results.
1. reboot in recovery
2. connect phone (in recovery mode) with usb to PC
3. check with adb if the pc can see the phone with the command: "adb devices". Should give u a device. Name should be a sequence of numbers
4. if in step 3 you get a phone. Type "adb remount" and enter
5. type: "adb shell" and enter
6. type: "mount /system" and enter
7. type: "ls /system" and enter
8. post the results of step 7.
We will see after this what to do next
Click to expand...
Click to collapse
So come on friends,
So ... to start already gave an error that bothered me before.
Post the picture, damn contradiction failed: Success
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here's the result ....
hmm, that doesn't look bad.
We try the following steps to get you back to stock. Every step needs to give an 'OKEY' if not, report here.
For this we need to have mfastboot. So download it and set it up.
Download your latest official firmware (4.1.2) for your device. So coming from EU use EU, BR use BR etc. And extract it. Copy mfastboot into those files or copy all the files into the mfastboot directory file.
1. reboot in bootloader
2. do: 'mfastboot devices' and you get medfield******** device. If not, your drivers and mfastboot are not setup properly
3. do: 'mfastboot flash gpt gpt_signed' get 'OKEY'
4. do: 'mfastboot flash motoboot motoboot' get 'OKEY'
5. do: 'mfastboot flash boot boot_signed' get 'OKEY'
6. do: 'mfastboot flash recovery recovery_signed' get 'OKEY'
7. do: 'mfastboot flash motobp motobp' get 'OKEY'
8. do: 'mfastboot flash system sysem_signed' get 'OKEY'
9. do: 'mfastboot flash cdrom cdrom_signed' get 'OKEY'
10. do: 'mfastboot erase cache' get 'OKEY'
11. do: 'mfastboot erase userdata' get 'OKEY'
Report back with what u get. I hope that if u get any error we can fix it.
Hazou said:
hmm, that doesn't look bad.
We try the following steps to get you back to stock. Every step needs to give an 'OKEY' if not, report here.
For this we need to have mfastboot. So download it and set it up.
Download your latest official firmware (4.1.2) for your device. So coming from EU use EU, BR use BR etc. And extract it. Copy mfastboot into those files or copy all the files into the mfastboot directory file.
1. reboot in bootloader
2. do: 'mfastboot devices' and you get medfield******** device. If not, your drivers and mfastboot are not setup properly
3. do: 'mfastboot flash gpt gpt_signed' get 'OKEY'
4. do: 'mfastboot flash motoboot motoboot' get 'OKEY'
5. do: 'mfastboot flash boot boot_signed' get 'OKEY'
6. do: 'mfastboot flash recovery recovery_signed' get 'OKEY'
7. do: 'mfastboot flash motobp motobp' get 'OKEY'
8. do: 'mfastboot flash system sysem_signed' get 'OKEY'
9. do: 'mfastboot flash cdrom cdrom_signed' get 'OKEY'
10. do: 'mfastboot erase cache' get 'OKEY'
11. do: 'mfastboot erase userdata' get 'OKEY'
Report back with what u get. I hope that if u get any error we can fix it.
Click to expand...
Click to collapse
Glad for his preliminary Topic...
However, at the first command line can not, aliases, I tried the following, by having obtained the medfield by adb devices, however the following are recognized as command, however not result in anything ...
I downloaded several fastboot. put in the platform-tools, copied the files Adb & Co. as indicated on the internet, however to no avail, any suggestions?
Here's the Dammit CMD Lines.
U need to be in fastboot (bootloader) mode. From recovery u can get there by doing 'adb reboot bootloader' but the fastest way is just reboot your phone with the key combination volume down + power.
Fastboot mode is the mode before u enter recovery. It is also called bootloader.
Verstuurd van mijn GT-P5110
Youre rock!
Hazou said:
U need to be in fastboot (bootloader) mode. From recovery u can get there by doing 'adb reboot bootloader' but the fastest way is just reboot your phone with the key combination volume down + power.
Fastboot mode is the mode before u enter recovery. It is also called bootloader.
Verstuurd van mijn GT-P5110
Click to expand...
Click to collapse
My dear friend,
I have only two more questions for you,
1-How to turn you into a God?
HUEHUEHUE
2-How to increase your reputation?
- At first, the phone would not update the motoboot, however I had the idea to go giving procedure at all, and by the penultimate system, since it would give flash remake the build.prop. and then the motoboot was smoothly. like a feather on a cliff.
Really do not have words enough to thank you all this support that during all this time gave me.
Consider the topic as closed, and for others who have the same problem, I recommend reading it.
You are a Genius emerged from a magic lamp friend.
eternally Grateful
:good::victory:
1. Could be a problem, maybe if u have connections to Zeus, god, Allah or whoever XD
2. U can hit the thanks button under my posts if u want
Glad to hear all is fine now good luck with whatever u want to do now!
Verstuurd van mijn GT-P5110
Related
hi there,
so i am slightly new at this and have searched for hours and hours trying to find a consistent formula for rooting and installing my g1 to cyanogen mod 4.2 (or latest stable one, thus not cm 5). I seriously stayed up until 1am last night and now i am at work (started at 8) still searching.. I have used google, youtube, and several other cm sites. Basically the problem is there is not one guide and I am not sure if because I followed the CM wiki guide if i can switch because I am having problems with that one. So one question: does anyone know which is the latest and verifiably the best CM 4.latest guide to installing?
I am pretty sure i have rooted the phone because I successfully downgraded to RC29, the old school android OS. However when I try completing this guide: [cant put a URL in but the webpage title is: "G1 CM4.2 installation" and I already completed this wikiguide title: "Full Update Guide - G1/Dream Firmware to CyanogenMod" but it continues into the next page to install cm)
I get freaking stuck. I put all three files on my SD and when I try to push "Alt-A" there is not an option there for it, its not an option on my recovery mode menu. I tried putting the files back there after reformatting several times but still no 'alt-a' so I am stuck on step 5 because there is no option for step 5 on my recovery mode on the above web guide..
Does this mean I did not install something? should I try and install the ota radio, cm update, drc83 zip files separately (like load one on the sd card and install it, then reformat the sd card and then repeat with the other two files?) ? If so what order should I do that in??
Sorry I suck and have not been able to find these answers, there are just a plethora of guides and I am not confident in my modding to start deviating away from the wiki guide in case I brick my beautiful g1..
thanks so much, this has been a huge headache for me.. i literally spent 4 hours yesterday trying to get to this step.. aww...
At Step 5 select "apply any zip from sd" in Recovery.
Select "DRC83_base_defanged.zip" on your SD.
Press Home to confirm flashing.
Then select "update-cm-4.2.x-signed.zip" on your SD to flash CyanogenMod.
After everything is completed reboot your Phone normally.
Edit:
Here is the Link to the Tutorial.
zerocoolriddler said:
At Step 5 select "apply any zip from sd" in Recovery.
.
Click to expand...
Click to collapse
Yup you hit the nail on the head. Sorry I must not have been too clear on what was I was saying earlier. That is exactly the problem, you see I would select that in recovery mode, But "apply any zip from SD" is not there! Did I load some file wrong??
It only gives me:
Android system recovery utility
E: Can't open /cache/recovery/command
Home+Back - reboot system now
ALt+L - toggle log text display
Alt+S - apply sd:update.zip
Alt+W - wipe data/factory reset
could it be this: "E: Can't open /cache/recovery/command" that is the problem? I only found one reference to this message during my internet searches and the guy said it always says that..
So you have CM-Recovery?
Flash Amon_RA`s Recovery, it´s more comfortable to me. I´m using 1.6.2.
For G1: http://forum.xda-developers.com/showthread.php?t=566669
For MT3G(Magic 32b): http://forum.xda-developers.com/showpost.php?p=4029315&postcount=1
Nope. I am also using Flash Amon_RA's recovery.. (v1.6.2)
I loaded it up on the flash drive and also used telnet app to flash it in (wrong terminology? I typed it in the telnet box and hit return and it gave me the # # which I read means I did it right)
Try flashing again using fastboot.
Following Points should be listed:
1. Reboot system now
2. Go to console
3. USB-MS Toggle
4. Backup/Restore
5. Flash zip from sdcard
6. Wipe
7. Partition sdcard
8. Other
9. Power off
Install via Fastboot:
Copy recovery-RA-dream-v1.6.2.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img
maybe i get something wrong
but did you boot into the recovery menu already? (press home and power when you turn the phone on)
from there you can choose your task with the trackball nice and easy...
(you r from vienna?)
zerocoolriddler said:
Try flashing again using fastboot.
Following Points should be listed:
1. Reboot system now
2. Go to console
3. USB-MS Toggle
4. Backup/Restore
5. Flash zip from sdcard
6. Wipe
7. Partition sdcard
8. Other
9. Power off
Install via Fastboot:
Copy recovery-RA-dream-v1.6.2.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img
Click to expand...
Click to collapse
those points are not listed!
I did not try flashing via fastboot before but rather via terminal app.. Do I need some special software for fastbooting? Amon_RA's post says i need "Requires engineerings SPL!" which I do not have ..
and I now I loaded it via fastboot and I cant get out of it! how do I reboot out of fastboot? Because I can do not know how to "fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img" .. can you explain that in more detail?
skarboy- no i am not from vienna but the USA. and yea I tried to boot from the recovery menu but when i am there it does not show the option of flashing zip from sd (see above)
You did not succesfully apply the recovery image then. Find amon_ra 1.6.2, rename it to recovery.img (make sure that you don't accidentally name it to recovery.img.img because of windows explorer on your computer). Put it on the root of your sdcard. From there, open the telnet app and type "su", then type "flash_image recovery /sdcard/recovery.img" power back on to recovery (home+power), and apply DRC83, CM4.2.15.1, and radio 2.22.23.02.
mejorguille said:
You did not succesfully apply the recovery image then. Find amon_ra 1.6.2, rename it to recovery.img (make sure that you don't accidentally name it to recovery.img.img because of windows explorer on your computer). Put it on the root of your sdcard. From there, open the telnet app and type "su", then type "flash_image recovery /sdcard/recovery.img" power back on to recovery (home+power), and apply DRC83, CM4.2.15.1, and radio 2.22.23.02.
Click to expand...
Click to collapse
oh okay. shoot.. I followed your instructions. do I hit return after typing 'su' in telnet? I did and then typed in the flash image stuff and hit return again. it gave me '##'
i am not rebooting in recovery.. hopefully it will work .
can i have all 4 files on the SD card at the same time? or should i erase it then load the DRC83, CM4.2.15.1, and radio 2.22.23.02 files??
also if i dont get the alt+a option should i just keep trying ??
EDIT: NOPE IT did not work, maybe I should just rename the file recovery, i looked under file properties last time but it didnt say it was hiding the file extension.. I am not quite sure what I am doing wrong.. if someone could show lead me through each individual step by step that would be swell.. of post a video (not outdated).
awwwwwww this is soo painful
austriker27 said:
oh okay. shoot.. I followed your instructions. do I hit return after typing 'su' in telnet? I did and then typed in the flash image stuff and hit return again. it gave me '##'
i am not rebooting in recovery.. hopefully it will work .
can i have all 4 files on the SD card at the same time? or should i erase it then load the DRC83, CM4.2.15.1, and radio 2.22.23.02 files??
also if i dont get the alt+a option should i just keep trying ??
EDIT: NOPE IT did not work, maybe I should just rename the file recovery, i looked under file properties last time but it didnt say it was hiding the file extension.. I am not quite sure what I am doing wrong.. if someone could show lead me through each individual step by step that would be swell.. of post a video (not outdated).
awwwwwww this is soo painful
Click to expand...
Click to collapse
First make sure you have all the files needed (recovery.img, DRC83_base_defrangled, CM4.2.15.1, and radio 2.22.23.02). Tell me if you are missing anything. Load them all up on your sdcard. Make sure that none of the files are in any folders. Next you are going to want to download the "terminal emulator" app from the market (by ZTA). Once downloaded, open the app and type "su" (enter). After that, type "flash_image recovery /sdcard/recovery.zip"(enter). Type "reboot recovery" (enter). If you do not see this image below, then something went wrong.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(note, that image shows 1.7 but you are going to want to install 1.6.2. v1.7 is for CM5-based roms)
okay, so after a much needed break of watching the US draw with England (world cup!!) i am back..
yes I have all of those files but my radio file is different (older?).. It is "ota-radio-2_22_19_26I".. should I have the radio file you mentioned? can you link it to me?
EDIT: Okay I found that file that you referenced and downloaded it. I will throw it in my sd card instead of the 26I because it sounds like it is a better radio flash..
also the 'radio', update cm, and DRC83 files are really zipped folders (.zip) that I have not extracted. Do I need to extract the contents into a folder and put the files from these extracted folders on the SD card root (so that there are ZERO folders on the sd? (no one mentioned this)
and so I use terminal emulator as opposed to telnet?? I was using telnet before because the CM wikiguide says so..
You don't need to unzip. They're zipped to flash via Recovery.
Flash the Recovery via Fastboot.
PS: It's called Terminal, not Telnet. ;-)
mejorguille said:
First make sure you have all the files needed (recovery.img, DRC83_base_defrangled, CM4.2.15.1, and radio 2.22.23.02). Tell me if you are missing anything. Load them all up on your sdcard. Make sure that none of the files are in any folders. Next you are going to want to download the "terminal emulator" app from the market (by ZTA). Once downloaded, open the app and type "su" (enter). After that, type "flash_image recovery /sdcard/recovery.zip"(enter). Type "reboot recovery" (enter). If you do not see this image below, then something went wrong.
(note, that image shows 1.7 but you are going to want to install 1.6.2. v1.7 is for CM5-based roms)
Click to expand...
Click to collapse
okay so I tried all that.. and freaking a! awwwwww no success it just gave me the old screen like before
when I typed in "su" it said permission denied so I think I have to go back and do something that I missed. I cant keep track of how many times I have done everything, then erased then tried again.. I wish someone would be specific and just walk me through this without skipping a single detail..
zerocoolriddler said:
You don't need to unzip. They're zipped to flash via Recovery.
Flash the Recovery via Fastboot.
PS: It's called Terminal, not Telnet. ;-)
Click to expand...
Click to collapse
this is exactly what i am talking about everyone is saying something different:
here is the CM site telling me to use telnet:
Open Android Telnet Client and type (include all spaces)
flash_image recovery /sdcard/recovery.img [enter]
If completed correctly you will simply see # # appear on your screen beneath the line you've just typed. If you get the "permission denied" message, type "su" (without quotes), press enter and repeat the previous step. If you get a file not found message, you may need to remount your sd card or make sure you typed the file name correctly.
Press Home key and proceed to next step
austriker27 said:
okay, so after a much needed break of watching the US draw with England (world cup!!) i am back..
yes I have all of those files but my radio file is different (older?).. It is "ota-radio-2_22_19_26I".. should I have the radio file you mentioned? can you link it to me?
EDIT: Okay I found that file that you referenced and downloaded it. I will throw it in my sd card instead of the 26I because it sounds like it is a better radio flash..
also the 'radio', update cm, and DRC83 files are really zipped folders (.zip) that I have not extracted. Do I need to extract the contents into a folder and put the files from these extracted folders on the SD card root (so that there are ZERO folders on the sd? (no one mentioned this)
and so I use terminal emulator as opposed to telnet?? I was using telnet before because the CM wikiguide says so..
Click to expand...
Click to collapse
the 2.22.23.02 radio is newer and its supposed to have better reception and less battery usage as compared to the .26I radio but the difference should be minimal. Everything is supposed to be in a zipped folder exept for the recovery image. Terminal is similar to telnet in that you can put in commands but it works a little different. It is what I usually use to flash recovery's, etc, so since telnet was not working for you I though terminal might make a difference.
Again, open terminal and type:
Code:
su(enter)
flash_image recovery /sdcard/recovery.img(enter)
reboot recovery(enter)
Tell me if this works.
Edit:look at my next post
austriker27 said:
this is exactly what i am talking about everyone is saying something different:
here is the CM site telling me to use telnet:
Open Android Telnet Client and type (include all spaces)
flash_image recovery /sdcard/recovery.img [enter]
If completed correctly you will simply see # # appear on your screen beneath the line you've just typed. If you get the "permission denied" message, type "su" (without quotes), press enter and repeat the previous step. If you get a file not found message, you may need to remount your sd card or make sure you typed the file name correctly.
Press Home key and proceed to next step
Click to expand...
Click to collapse
The "su" command signifies root access. If it says permission denied, then that means that you are not rooted or you skipped a step.
CYANOGEN WIKI said:
Rooting the phone
You need to have root (or 'admin') access to the phone so that you can install whatever software you want and not just what your provider gives you. This is not the same as unlocking your phone.
Finish booting up your phone, and sign-in to your Google account.
If you don't have access to a 3G network, then follow the G1 logon to google via wifi guide to sign-in via wifi. The original guide to do this is out of date.
You could try and add your networks provider's APN. To do this press Menu key -> APN Settings, press Menu again -> Add APN and enter 4 things: Name, MCC (Mobile Country Code), MNC Mobile Network Code and APN - all this info should be available here: http://en.wikipedia.org/wiki/Mobile_network_code and on your network provider's site. The image you booted with might also have the extensive APN list. If so, and you can't get a data connection, then you might try the wifi guide.
Once you're at the Home screen, open the keyboard, and press the Enter (Return) button twice.
Type
telnetd [enter]
Typing will bring up the Contacts screen, but you can just ignore that.
There will be no indication to let you know you did it right. Just continue on to the next step.
If you get an error when trying to connect (step 5), try pressing Enter twice and type "telnetd" and press Enter again
Open the Android Market, and install "Telnet" by ClockworkMod (Formerly by Koushik Dutta)
Open Android Telnet Client, enter "localhost" in the large text box and press connect. (You may have to enter "23" in the smaller text box on the right)
Click to expand...
Click to collapse
Do those steps again.
okay so I am in the telnet client and have entered localhost and 23 and hit return. so now i am in a black screen. i typed in what cm wikiguide told me and it gave me :
## (good sign!)
now do I turn off the phone and go into recovery mode or this where I am missing a step??
Sorry I am so ornery (wow and i can spell) there are just a number of things frustrating me.. besides me knowing this should only take like 2 hours at the most and knowing I keep messing up some mundane detail or something.. Also I am doing it in windows on my macbook and the wireless keeps disconnecting. Also I would take photos of the screens to show you but I do not have any photo software on the windows partition of my laptop (i mostly use mac os x) so I cannot... and i am very tired from working 6 days a week (and only getting 6 hours of sleep last night due to this issue) and frustrated from this whole fiasco.. And I have a headache.. yup call me a whiner if ya want but i am just trying to explain why i am kinda mad...
HALELUJAH! it worked and the android system recovery looks like your image mejor!!!!!!!! hopefully this works, i will let you know.. thanks soo much! i have no idea what i did differently
YESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
wow so that wasnt a giant headache, although now i pretty have the process memorized and have learned tons in the process. I think I may have the longest time to root a g1 record so far of any human haha... Lets see I worked on it yesterday from 8pm-1am while kind of watching world cup. This morning for about 2 hours from 9-1130 at my job. And this afternoon for about 2 hours..So like 9 hours give or take an hour of two.. NEW RECORD!! haha
THANKS SO MUCH for you help guys I love you. Especially mejor because he/she lead me down the finishing stretch... Now to install apps2sd (after my class 6 card comes) and take a nap
Ok so the SD card slot on my phone is toast. Is it possible to install a rom thru the USB cable without using the SD card? =/
Hmm... Ok I have two ideas that i'll quickly check out. One of which will require you to wipe your data/factory reset in recovery, the other if I did get it to work wouldn't require any wiping unless you wanted to.
I'll try 'em both out and tell you if I have any luck doing so
Alright, so here we go..
Results
First idea without having to wipe: no go
Second idea with wiping: WORKS
After doing some digging around the AmonRA github to look for the commands it actually performs while in recovery I figured out exactly how to do what I wanted.
(namely THIS PAGE for those of you who are interested in seeing the exact page I found them on)
How to Flash a ROM Without an SD Card
Prerequisites:
Flash an Amon_RA recovery if you're using Clockwork - I recommend Darch's unofficial (refer to my signature if you need it)
Access to a computer that had AndroidSDK tools on it - you'll be using ADB
Put whichever ROM.zip you want to flash in your android-sdk\tools folder - I would rename it to something simple. (My example which I'll be using for this tut is: C:\AndroidSDK\toosl\kyoukoROM.zip)
Directions:
Reboot into the Amon_RA recovery
Wipe data/factory reset, cache, and dalvik via the recovery menu
Open up cmd/terminal on your computer
Navigate to your android-sdk\tools directory
Enter the following in cmd/terminal:
Code:
adb shell
mount data
*wait a second or two* You may or may not get the "/ #" line returned.
Despite what happens press "Ctrl+C" to break the command and get back to the standard AndroidSDK\tools> directory
Enter the following in cmd/terminal:
(replace "kyoukoROM.zip" with the name you're using)
Code:
adb push ./kyoukoROM.zip /data/
*this will take anywhere from 30sec to a min depending on the rom.zip size*
Then we do this in cmd:
Code:
adb shell
recovery --update_package=DATA:mau5.zip
Wait for it to finish flashing/updating
Reboot
ENJOY
If someone thinks I should post this in the development section as a [GUIDE] let me know and I'll post it there too
Yup I think so marking as a fav this is good knowledge thanks for the post
Root-Hack-Mod-Always™
Post it! This would be a HUGE help to people
Sent from my HERO200 using XDA App
Great work Kyouko! If not to the dev forum, atleast post it to the wiki.
BTW, you should post it to Android forums, as well... if I am not wrong, this will work with any phone.
andythegreenguy said:
Great work Kyouko! If not to the dev forum, atleast post it to the wiki.
BTW, you should post it to Android forums, as well... if I am not wrong, this will work with any phone.
Click to expand...
Click to collapse
Good idea, hopefully it'll help a lot more people there. I'll post it there and change up a couple things (the darch recovery part)
And idk how to edit the wiki
Amazing response! I will have to give this a try thank you!!! I still have a month left before my upgrade and I wanted to be able to change my ROM. Thanks again!
FYI Rom Manager will not flash a clockwork recovery without an SD card, gives an error... looking into other ways to flash a recovery...
**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
Disclaimer: If you are not comfortable with using Fastboot and ADB and editing system files than this guide might not be for you. At this point this is what I have to offer.
Click here for the unofficial twrp image - Latest version as of 12/27/14
So getting right into it.
1. Turn on ADB mode on the watch by going to about and tapping the build info 7 times.
2. Download ADB and Fastboot utilties
3. Plug the watch into the computer and your phone should vibrate and ask you to accept the computers fingerprint, tick the check box to always allow and hit ok
4. Open up a command prompt or terminal inside of where the ADB utilities are located and enter
Code:
adb reboot bootloader
This next step will wipe your data!
5. Now you should be in fastboot, go ahead and on the terminal use the next code and follow prompts to unlock
Code:
fastboot oem unlock
6. Now after you re-set up your watch again you will need to do step 1 and 3 again.
Please do not skip step 6!
7. Go ahead and issue
Code:
adb reboot bootloader
8. Flash unofficial twrp, make sure the recovery image file is in the same location as fastboot than issue
Code:
fastboot flash recovery YOURIMGNAMEHERE.img
9. Upon successfully doing that you should have twrp installed
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB use the proper name of what you downloaded. Issue
Code:
adb push SUPERSUNAMEHERE.zip /sdcard/
11. Issue
Code:
adb reboot recovery
12. than using the very tiny TWRP and somewhat messed up go ahead and use it to install the supersu.zip under the folder /sdcard
13. Enjoy root and twrp.
I will make this guide into a much easier Java program in the very near future to make it easier to use.
This was typed up pretty fast and it is kinda hacky, I will work on a bat script and a shell script if we have enough osx users here. I'm sure someone will come along and make this better if I don't get around to it.
Credits:
Dees-Troy for his TWRP support for dory our fish brother device which worked on our device
Chainfire for all his hard work these many years
Q: ADB complains there is no device listed.
A: Install universal ADB drivers and then go to device manager and under the device with a yellow warning icon go to update driver, Browse my computer, let me pick from list of device drivers, than Google ADB interface. If it still complains turn off debugging, than turn it back on, revoke authorization, then disable and re-enable again.
One more just in case.
Great work!!
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
hatefuel19 said:
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
Click to expand...
Click to collapse
The latest supersu is version 2.36 dated 11.27.2014. 1.94 is well over a year old, you need to update for sure that is why you are force closing.
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
hatefuel19 said:
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
Click to expand...
Click to collapse
I'm here to help! I'm working on adding other mods to my other thread right now I'm working on getting busybox working.
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
---------- Post added at 09:31 PM ---------- Previous post was at 09:28 PM ----------
jimmydigital00 said:
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
Click to expand...
Click to collapse
Disregard I did it again and for some reason it worked. Maybe I need to reboot first.
Recovery
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
adamrobles said:
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
Click to expand...
Click to collapse
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
reflashed
tonu42 said:
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
adamrobles said:
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
Click to expand...
Click to collapse
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
Thank you for that information, I stopped the download of the dump.
Downloading the stock recovery now.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
I must have skipped a step...
installed stock recovery
booted into the watch system
enabled adb debugging
reboot to bootloader
install your recovery image
rebooted
pushed supersu
rebooted to twrp
installed supersu
rebooted to system
adb shell - verified root!
You are awesome! Thank you for taking the time to help me!
HYPE for 5.0.1
'm Hype! can't wait to flash the first 5.0.1 system dump on this as stated by +Darek Ross we MAY be receiving update as early as today!
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
zvieratko said:
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
Click to expand...
Click to collapse
My guide is setup like the one you put there. In order to get adb working again you need to re setup the watch step 6. Read the instructions carefully. I'll post a batch script later to simplify this.
Sent from my A0001 using XDA Free mobile app
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
zvieratko said:
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
Click to expand...
Click to collapse
By default debugging is disabled, I'm not sure how you were able to issue an ADB command on step 7 with out first performing step 6.
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
zvieratko said:
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
Click to expand...
Click to collapse
Ah I see, yea the guide is written as the absolute minimum to work right now. Like I said later today I'll try to post a script that automates all of this, its much easier.
First of all, I would like to say thanks to @DrakenFX, @tenfar, @rczrider, and @tennear for their work on the Axon 7.
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or any other mishaps that may occur. YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*/
This guide is intended to help anyone wishing to return to stock B20 firmware on the A2017U for the purposes of re-locking the bootloader (either for sending a device in for an RMA or whatever you may need). After much trial and error, I have finally come up with a guide and attached all necessary files to do this. I performed the following steps on my Axon 7 2017U on the B29 firmware and successfully downgraded to the B20 firmware with a re-locked bootloader.
Here are the files you will need:
Stock system
Stock boot stack
Stock fastboot
Stock recovery
TWRP
Make sure you have ADB and fastboot set up properly on your computer.
Use the TWRP linked in this post. I know for sure that this version works towards the end of this process when your bootloader is locked again.
After you have the zip files, you will need to move them to your phone to flash in TWRP. Follow these steps:
1. Make a backup of all of your important data. EVERYTHING will be wiped in this process, including internal storage.
2. Power off the phone.
3. Download the the axon7tool executable file from this link: Here Check the post for instructions pertaining to drivers needed.
4. Boot the phone into EDL mode. Do this by holding down the Volume Up and Volume Down keys simultaneously and then plugging the phone in to your computer while keeping these keys pressed. (The phone's screen will be completely black and it will appear like nothing is happening. This is EDL mode.)
5. Open a command prompt in the directory with the axon7tool executable. (Windows: right click while holding shift and select "Open command window here." Linux: Open a terminal and cd into the directory)
6. Dump your gpt with the tool. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -r gpt
Linux: ./axon7tool-1.5-linux -r gpt
7. The axon7tool will automatically reboot you. Reboot to TWRP.
8. Make a backup of your EFS partition by going to "Backup" with only the EFS box checked.
9. Copy the "TWRP" folder from your internal storage to your computer. This folder contains the EFS backup.
10. Go to "Wipe" -> "Advanced" -> "Format Data." Type "yes." WARNING: THIS DELETES ALL DATA. MAKE SURE YOU HAVE A BACKUP.
11. Reboot back into TWRP. Ignore anything TWRP says or asks you to do upon a reboot.
12. Copy the "B20_stock_system," B20_stock_bootstack," and "B20_stock_fastboot" zip files to your internal storage.
13. Flash the stock system zip first, then the boot stack zip, and finally the fastboot zip.
14. At this point you are on the stock B20 system, but with an unlocked bootloader. TWRP will probably be overwritten, so follow these next steps regardless.
15. Reboot the phone and let it get to the set up screen. This step can take a while; my Axon took almost a minute to get off of the ZTE splash screen initially.
16. As soon as you see that the phone boots, power off the phone and reboot to EDL mode.
17. Flash TWRP again with the axon7tool as it has been overwritten at this point and will be necessary soon. Download the linked TWRP recovery image and rename the file to "recovery.bin" Place it in the same folder as the axon7tool. Flash the recovery. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -w recovery
Linux: ./axon7tool-1.5-linux -w recovery
18. Reboot the phone into the bootloader. You can do this by going to TWRP and by choosing reboot to bootloader or by manually doing so.
19. Type "fastboot oem lock" into a command prompt. This will lock your bootloader.
20. After I did this, I thought I was done. However, when I rebooted my phone, I saw that /data required a password to be decrypted upon a reboot. This is why we flashed TWRP. Go into TWRP and format data again.
21. Copy the "TWRP" phone from earlier back onto your internal storage. Restore your EFS in case anything has happened to your IMEI in this process.
22. At this point your phone is completely locked but with a custom recovery. To restore the stock recovery, reboot into EDL mode and replace the TWRP recovery.bin file from a few steps ago with the B20_stock_recovery.bin file you downloaded. Rename the B20_stock_recovery.bin file to recovery.bin and make sure it's in the same folder as the axon7tool.
23. Flash the stock recovery with the same commands for the axon7tool as listed earlier for TWRP.
24. Profit
As tennear has noted, do NOT backup or restore the EFS partition.
Never restore EFS using TWRP. You will lose its contents and probably your IMEI.
@tennear Thanks for the heads up. I'll remove that part from my guide.
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
mortkarg5 said:
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
Click to expand...
Click to collapse
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Yoshi_Guy said:
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Click to expand...
Click to collapse
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
mortkarg5 said:
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
Click to expand...
Click to collapse
You can try, but I'm not sure if it would work. The recovery is for stock b20 so try it at your own discretion.
Every time I try to do the fastboot oem lock it fails, I have the twrp you mentioned in the post and followed the steps as listed. Did you run into this issue?
Sent from my ZTE A2017U using Tapatalk
i can't found same file u can upload again?
Yeah.... most links are dead. Does anyone else have them?
Flapjack said:
Yeah.... most links are dead. Does anyone else have them?
Click to expand...
Click to collapse
I'll fix them.
Yoshi_Guy said:
I'll fix them.
Click to expand...
Click to collapse
Thanks, brotha.
Flapjack said:
Thanks, brotha.
Click to expand...
Click to collapse
Try again, they should be working now.
Yoshi_Guy said:
Try again, they should be working now.
Click to expand...
Click to collapse
Thanks... but holy f*ck... this MEGA bs. What a piece of garbage. Why do I need to create an account?
I'm getting the following error (Win 10). Others have gotten the same error in various versions of linux, as well. The only one who resolved the error had forgot to elevate his terminal (which I've done):
Code:
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
@Yoshi_Guy
In step 22) where stock recovery has to be restored, instead of reusing axon7tool in EDL mode, maybe it would be easier to flash stock recovery by the signed tenfar TWRP itself (by using TWRP Install/flash image option, boot partition). This is a kind of "hara-kiri" (current TWRP destroys itself) but it should work.
Flapjack said:
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
Click to expand...
Click to collapse
That's quite odd, what version of Linux are you using? Also, are you able to try the Windows version of the tool? I've used the tool on Arch Linux and had no problems. Also, the program does need to be run as root, as you mentioned. The signature verification probably failed because you are trying to downgrade your version, I wouldn't recommend using the official ZTE zips entirely. I would take what you need and flash just that, downgrading is rather complex.
Thanks for the guide, but wish you would've used androidfilehost. I hit MEGA quota at 80%, so I'll have to wait til late tonight to give this a shot.
nvm: using megadownloader now