So attempting to flash the M Preview and i got the missing system.img error when using the flash-all command.
I attempted to flash the files one by one and got this error on the first file
error cannot load bootloader-shamu-moto-apq8084-71.11
im sure the answer is right in front of me but I can' figure out what im doing wrong
twostep665 said:
So attempting to flash the M Preview and i got the missing system.img error when using the flash-all command.
I attempted to flash the files one by one and got this error on the first file
error cannot load bootloader-shamu-moto-apq8084-71.11
im sure the answer is right in front of me but I can' figure out what im doing wrong
Click to expand...
Click to collapse
What was the exact command as you typed it?
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.11
twostep665 said:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.11
Click to expand...
Click to collapse
When you type
fastboot devices
Does is your device recognized?
cam30era said:
When you type
fastboot devices
Does is your device recognized?
Click to expand...
Click to collapse
yep... I actually had this problem the other day as well when trying to flash 5.1.1 factory image as well
twostep665 said:
yep
Click to expand...
Click to collapse
Well, I'm not sure what to tell you....
twostep665 said:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.11
Click to expand...
Click to collapse
Did you type ".img" at the end of that command? (without quotes)
Evolution_Tech said:
Did you type ".img" at the end of that command? (without quotes)
Click to expand...
Click to collapse
i tried both ways. with .img at the end and without. both got the same error msg.
twostep665 said:
i tried both ways. with .img at the end and without. both got the same error msg.
Click to expand...
Click to collapse
SDK updated?
Evolution_Tech said:
SDK updated?
Click to expand...
Click to collapse
Aahh. Good point. With a totally new version of Android, that makes sense!
cam30era said:
Aahh. Good point. With a totally new version of Android, that makes sense!
Click to expand...
Click to collapse
I will give that a shot. Thanks.
twostep665 said:
I will give that a shot. Thanks.
Click to expand...
Click to collapse
Also double check and make sure you are typing the file name exactly as it is written, including .img at the end.
cam30era said:
Also double check and make sure you are typing the file name exactly as it is written, including .img at the end.
Click to expand...
Click to collapse
Yep and to expand on this, make sure windows is set to show file extensions and when in doubt, rename complicated named files to be simple whisky remaining descriptive.
rootSU said:
when in doubt, rename complicated named files to be simple whisky remaining descriptive.
Click to expand...
Click to collapse
Like Glenmorangie or Laphroaig?
cam30era said:
Like Glenmorangie or Laphroaig?
Click to expand...
Click to collapse
No, silly. Like Caol Ila, Lagavulin or Bruichladdich - but good effort
rootSU said:
No, silly. Like Caol Ila, Lagavulin or Bruichladdich - but good effort
Click to expand...
Click to collapse
hahaha. Thanks everyone for the help. I got it working last night. Updating the SDK seemed to do the trick.
twostep665 said:
hahaha. Thanks everyone for the help. I got it working last night. Updating the SDK seemed to do the trick.
Click to expand...
Click to collapse
Glad you got it solved.
I had an issue getting the M preview installed as well. Kept failing when trying to
Code:
fastboot -w update image-shamu-MPZ44Q.zip
. Ended up wiping my internal storage and I was in a bit of a pickle so heres what I did: (you need to start off in bootloader mode)
1. Download twrp from HERE
2. Then go to where you downloaded the file and flash it (since I'm using Ubuntu it's in "Downloads")
Code:
cd Downloads && fastboot flash recovery openrecovery-twrp-2.8.5.0-shamu.img
3. When the recovery finishes flashing manually reboot to recovery from the device by pressing the volume up key then press power to select "Recovery"
4. In TWRP go to the "mount" section and make sure that "system" is selected if it isn't. Then reboot to bootloader (if you get the "No OS error" don't worry, just disregard and ignore the SU flash prompt.
5. Now that your system has been re mounted you can manually flash each file but incase you want a copy and paste here it is:
(also make sure you unzip the image-shamu-MPZ44Q.zip file to extract the image-shamu-MPZ44Q folder)
-1
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.11.img
-2 reboot bootloader
-3
Code:
fastboot flash radio radio-shamu-D4.01-9625-05.16+FSG-9625-02.94.img
-4 reboot bootloader
-5
Code:
cd image-shamu-MPZ44Q && fastboot flash system system.img && fastboot flash boot boot.img && fastboot flash cache cache.img && fastboot flash userdata userdata.img && fastboot flash recovery recovery.img && fastboot reboot
PROFIT!
Related
I was rooted and removed some of the bloatware, before applying this update I reinstalled the bloatware and unrooted, when I try to update(5.6.980) it goes through but hangs on updating bp then it says
assert failed: motorola.motoflash("/tmp/bp.img")
E:Error in /tmp/sideload/package.zip
(status 7)
installation aborted
...idk what to do I tried wiping, rooting then unrooting and I keep getting the sam message and I guess thats needed for radio because now my phone can't find it, is there a package file or something i need????????????
anybody....
LRiley said:
anybody....
Click to expand...
Click to collapse
Have you tried flashing bp.img in fastboot?
rynosaur said:
Have you tried flashing bp.img in fastboot?
Click to expand...
Click to collapse
how do I do that?
LRiley said:
how do I do that?
Click to expand...
Click to collapse
I think this will be the file you need.
Then, get fastboot and put that file in the same directory.
Put the phone in AP Flash mode.
Connect with Moto cable to a good USB port.
type in:
Code:
fastboot devices
and verify that your device is shown without restrictions (you'll see a 16-char HEX code/serial id#)
if windows:
Code:
.\fastboot flash bpsw bpsw.img
if linux/unix/Mac:
Code:
./fastboot flash bpsw bpsw.img
reboot into recovery then try the update again.
did it and it says sending, OKAY, writing, (bootloader) command restricted, FAILED...is that right?
LRiley said:
did it and it says sending, OKAY, writing, (bootloader) command restricted, FAILED...is that right?
Click to expand...
Click to collapse
Well, yes, probably. For some reason, only certain partitions are available to flash from AP Fastboot.
rynosaur said:
Well, yes, probably. For some reason, only certain partitions are available to flash from AP Fastboot.
Click to expand...
Click to collapse
no, that means nothing happened. It sent it to the device, but didnt write it. So right where you started.
I got the same error again, I'm gonna root and try again
edru said:
no, that means nothing happened. It sent it to the device, but didnt write it. So right where you started.
Click to expand...
Click to collapse
Well, yeah, that's what I meant. It's normal for that partition to fail out. I'm guessing certain blocks can only be written in raw form from BP/SBF.
now I'm stuck in fastboot wut do I do now
LRiley said:
now I'm stuck in fastboot wut do I do now
Click to expand...
Click to collapse
Stuck? Reflash a non-protected partition, like cdrom. Then.
Code:
fastboot reboot
did it with mdm, but I'm back to square one
In the future, you'll probably get more help by titling your thread something more useful. I have skipped over it a few times already.
What's the output of
Code:
df /system
Edit: scratch that. bp.img is extracted to /tmp, which I'm guessing is a RAM disk. Have you tried running the update again? I'm not sure I understand why it would fail. Regardless, it is flashed using a Motorola utility so I imagine flashing by fastboot won't work.
I flashed it a lot of times but the update always gets stuck at bp
any ideas?
Can you post /cache/recovery/last_log
limaxray said:
Can you post /cache/recovery/last_log
Click to expand...
Click to collapse
where do I get that
LRiley said:
where do I get that
Click to expand...
Click to collapse
I assume you have adb installed? In a terminal, run:
Code:
adb shell
su
cp /cache/recovery/last_log /sdcard/
exit
exit
adb pull /sdcard/last_log <some local directory>
Replacing <some local directory> with wherever is convenient.
Hey all,
A few of us are attempting to put together a solution to unlock the bootloader of the N4 without wiping, and we need your help.
We need dumps of the misc partition of the N4 both in a bootloader locked and unlocked state. I've explained below what we need and how to do it.
Note, this will require you to re-lock and unlock your bootloader, (which will cause your data to be wiped) so do a nandroid and copy it off your device for a later restore.
Novice instructions:
1) You need to start off with an unlocked bootloader.
2) Boot into fastboot mode and plug into your PC.
3) If you don't have ADB and fastboot on your PC, download the attachment from this post and extract the contents to a directory.
4) If you don't have CWM or TWRP flashed, download CWM from here and save as cwm.img in the same directory as in step 3.
5) Open a command prompt in the same directory as in step 3 (i.e., hold the shift key and right click in a blank space in that folder).
6) Flash CWM: fastboot flash recovery cwm.img
7) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
8) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
exit
adb pull /sdcard/misc-unlocked.img
adb reboot bootloader
fastboot oem lock
fastboot reboot-bootloader
9) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
10) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
exit
adb pull /sdcard/misc-locked.img
11) Now you have two files (misc-unlocked.img and misc-lock.img) in the directory you created in step 3. Zip them up and upload them in this thread.
12) Your bootloader is now locked. If you want it unlocked, unlock it using the normal method of "fastboot oem unlock" which will wipe your data, but all you have to do is restore your nandroid, and you will be back to where you started.
Advanced user instructions:
1) Start with an unlocked bootloader
2) Dump the misc partition: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
3) Lock your bootloader
4) Dump the misc partition again: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
5) Upload the files to this thread.
For advanced users only (this has not yet been tested), if you want, you can try flashing the unlocked misc partition:
Code:
adb shell "dd if=/sdcard/misc-unlocked.img of=/dev/block/mmcblk0p19"
to see if it will unlock your device without wiping. But as I said, this has not been tested yet, so do the last step at your own risk.
Edit: nvm
Here is the dump. Thanks for your work.
KyraOfFire said:
Does it wipe sdcard? It need to know if I have to copy everything to the computer.
Thanks,
Click to expand...
Click to collapse
To be safe, you should copy everything to your computer.
Our theory is, once you lock your bootloader with "fastboot oem lock", you should be able to unlock it again without wiping anything just by flashing the misc partition that you dumped when your device was unlocked.
So, the steps themselves will not wipe anything. But, if you use "fastboot oem unlock" to unlock your bootloader (once you have completed all the steps), then it will wipe everything including /sdcard. If you use the command in the "advanced users instructions", the idea is that it won't wipe anything.
KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
Great thanks!
Did you try re-flashing the unlocked misc.img (while you were locked) to see if it unlocked?
I can't flash the misc-unlocked.img
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell "dd if=/sdca
rd/misc-unlocked.img of=/dev/block/mmcblk0p19"
dd: can't open '/sdcard/misc-unlocked.img': No such file or directory
Click to expand...
Click to collapse
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
KyraOfFire said:
I can't flash the misc-unlocked.img
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
Click to expand...
Click to collapse
Try this:
1) Copy the file to /sdcard
2) Reboot into CWM
3) Type in the command
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
KyraOfFire said:
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
Click to expand...
Click to collapse
Not sure why your directories are messed up.
Find where the file is saved, and use that path for the "if" part of the command. For example, if it is saved in /storage/emulate/0, then use this command:
adb shell "dd if=/storage/emulate/0/misc-unlocked.img of=/dev/block/mmcblk0p19"
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
adb shell "dd if=/system/misc-unlocked.img of=/dev/block/mmcblk0p19"
Click to expand...
Click to collapse
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
KyraOfFire said:
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
Click to expand...
Click to collapse
Great, thanks for the confirmation.
Very strange that /sdcard did not work. It worked fine on mine, but we will certainly look into it.
Thanks again.
Glad I could help. Now folks have less things to worry about when they decide to root
KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q? If so, I don't think that will help us too much. I dumped mine when I was on JOP40C (and I will do so again with JOP40D). If you do upgrade, then new dumps would be appreciated.
By the way, could you list the following from your device:
ROM version:
Bootloader:
Radio:
Thanks.
EDIT: If you want to follow the progress, you can have a look at this thread.
efrant said:
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q?
Click to expand...
Click to collapse
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
KyraOfFire said:
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
Click to expand...
Click to collapse
Hmm. Thanks for the offer, but don't bother going through the hassle. If you are already running JOP40D, then it should be ok. Weird that your dump had JVP15Q in it. I'll wait until a couple of the other guys have a look at it (in this thread).
For science
KyraOfFire said:
For science
Click to expand...
Click to collapse
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
osm0sis said:
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
Click to expand...
Click to collapse
I have a feeling that it has something to do with history/logging. My N4 came with JOP40C out of the box, and I would bet that KyraOfFire's came with JVP15Q out of the box.
When i try to push a file or rom on my htc one using sideload, it says "failed" i am currently left out without operating system and evrything wiped out of my device. please help
AHMEDNATOR said:
When i try to push a file or rom on my htc one using sideload, it says "failed" i am currently left out without operating system and evrything wiped out of my device. please help
Click to expand...
Click to collapse
what is your adb version? Have you tried adb push instead of adb sideload?
i dont know what version it is and i am using the squabbi htc toolkit, ive tried push but i didnt get any results
AHMEDNATOR said:
i dont know what version it is and i am using the squabbi htc toolkit, ive tried push but i didnt get any results
Click to expand...
Click to collapse
So let start at the beginning:
Don't use toolkit, use adb and fastboot directly from the command prompt
go there: http://forum.xda-developers.com/showthread.php?t=2317790
follow instructions in above thread to install minimal abd and fastboot on your computer
alray said:
what is your adb version? Have you tried adb push instead of adb sideload?
Click to expand...
Click to collapse
i dont know what adb version i have but ive tried using push with the squabbi htc too, no result in the end or i ll say failed protocol or whatever
AHMEDNATOR said:
i dont know what adb version i have but ive tried using push with the squabbi htc too, no result in the end or i ll say failed protocol or whatever
Click to expand...
Click to collapse
listen mate, I'm ready to help you push or sideload a rom to your phone, but we will not use this toolkit (no disrespect to squabbi btw).
When things goes wrong, better to use adb/fastboot directly from terminal, not using a toolkit.
so go ahead and install adb/fastboot on your computer so we can start troubleshooting.
alray said:
So let start at the beginning:
Don't use toolkit, use adb and fastboot directly from the command prompt
go there: http://forum.xda-developers.com/showthread.php?t=2317790
follow instructions in above thread to install minimal abd and fastboot on your computer
Click to expand...
Click to collapse
ok i am doing as you say, when i am done with this first step, i ll write here. btw my internal memory seems to be completely wiped out as i see 0mb in every folder via TWRP. Please can i add you up on facebook because i have to wait up to five minutes here to reply to you because i am new, it ll go faster on facebook
AHMEDNATOR said:
my internal memory seems to be completely wiped out as i see 0mb in every folder via TWRP.
Click to expand...
Click to collapse
In twrp, when you click on ''install'' does it says ''storage: internal storage: (0 MB)''? If it says 0 MB then you probably have corrupted your data partition...
Please can i add you up on facebook because i have to wait up to five minutes here to reply to you because i am new, it ll go faster on facebook
Click to expand...
Click to collapse
Irc, this restriction only apply for the first 10 posts, only 2 more and you'll get rid of it.
yes it is corrupted i guess, what can i do to fix this problem?
alray said:
In twrp, when you click on ''install'' does it says ''storage: internal storage: (0 MB)''? If it says 0 MB then you probably have corrupted your data partition...
Irc, this restriction only apply for the first 10 posts, only 2 more and you'll get rid of it.
Click to expand...
Click to collapse
yes it is corrupted i guess, what can i do to fix this problem?
AHMEDNATOR said:
yes it is corrupted i guess
Click to expand...
Click to collapse
does it says: ''storage: internal storage: (0 MB)''
Yes or No?
''I guess'' is not enough
in twrp, when you click on ''install'' does it says ''storage: internal storage: (0 MB)''?
Click to expand...
Click to collapse
alray said:
does it says: ''storage: internal storage: (0 MB)''
Yes or No?
''I guess'' is not enough
Click to expand...
Click to collapse
yes sadly
AHMEDNATOR said:
yes sadly
Click to expand...
Click to collapse
ok so you'll need to format your data partition
in twrp, select ''wipe'' then ''format data''
alray said:
ok so you'll need to format your data partition
in twrp, select ''wipe'' then ''format data''
Click to expand...
Click to collapse
ok done mate! what now?
btw, what version of twrp are you using?
alray said:
btw, what version of twrp are you using?
Click to expand...
Click to collapse
v2.6.3.0
AHMEDNATOR said:
ok done mate! what now?
Click to expand...
Click to collapse
This part to do in 2nd - in recovery mode:
make sure your rom.zip is in the same folder of adb and fastboot, if you have installed minimal adb and fastboot, it should be C:\Program\Minimal ADB and Fastboot\
hold shift + right click a blank space in that folder, select ''start command prompt here'' from the contextual menu.
then in the command prompt (with your phone booted in twrp) type:
Code:
adb devices
it should reply your device s/n + recovery, If yes then:
Code:
adb push name_of_rom.zip /sdcard/
should take around 5 min to transfer (there is no progress bar)
---------- Post added at 01:59 PM ---------- Previous post was at 01:57 PM ----------
AHMEDNATOR said:
v2.6.3.0
Click to expand...
Click to collapse
This part to do 1st in bootloader mode (fastboot usb mode)
wait your twrp is outdated and most newer rom require at least twrp 2.6.3.3.
download and save twrp 2.6.3.3 to your adb/fastboot folder
with phone in bootloader mode (fastboot):
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then re-enter recovery and do what I said above
should my phone be in recovery mode or [email protected]
AHMEDNATOR said:
should my phone be in recovery mode or [email protected]
Click to expand...
Click to collapse
see above post, edited in red
@alray where should the adb fastboot folder be located? is it supposed to show up when i plug in my phone?
I installed Android Revolution HD, and I'm stuck in a bootloop.. And in ClockWorkMod Recovery, it says root access is lost... What do I do?
mrchris814 said:
I installed Android Revolution HD, and I'm stuck in a bootloop.. And in ClockWorkMod Recovery, it says root access is lost... What do I do?
Click to expand...
Click to collapse
read the instructions - realize that you need to flash with TWRP recovery not ClockWorkMod - flash TWRP 2.6.3.3 - enter recovery and wipe - push the ROM again - flash again.
Seanie280672 said:
read the instructions - realize that you need to flash with TWRP recovery not ClockWorkMod - flash TWRP 2.6.3.3 - enter recovery and wipe - push the ROM again - flash again.
Click to expand...
Click to collapse
How do I flash TWRP?
mrchris814 said:
How do I flash TWRP?
Click to expand...
Click to collapse
do you know how to use fastboot and ADB ?
Seanie280672 said:
do you know how to use fastboot and ADB ?
Click to expand...
Click to collapse
Not really...
mrchris814 said:
Not really...
Click to expand...
Click to collapse
oh no, well here goes, your going to need it, especially as your in a bootloop.
so download and install this, everything including the drivers, the file must be run as administrator: http://forum.xda-developers.com/showthread.php?t=2588979
then download this img file and put it in the same folder as fastboot and adb that you just installed: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
open a command windows (CMD window) in that same folder, to do this, hold down control & shift & right mouse click on any white area in that folder and select open command window here.
with your phone plugged into the computer and in fastboot USB mode type the following command one at a time
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
let me know when that's done
Seanie280672 said:
oh no, well here goes, your going to need it, especially as your in a bootloop.
so download and install this, everything including the drivers, the file must be run as administrator: http://forum.xda-developers.com/showthread.php?t=2588979
then download this img file and put it in the same folder as fastboot and adb that you just installed: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
open a command windows (CMD window) in that same folder, to do this, hold down control & shift & right mouse click on any white area in that folder and select open command window here.
with your phone plugged into the computer and in fastboot USB mode type the following command one at a time
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
let me know when that's done
Click to expand...
Click to collapse
It's done.
mrchris814 said:
It's done.
Click to expand...
Click to collapse
that was quick, enter recovery, and select wipe, swipe to factory reset then I always go into advanced wipe too and select everything except internal storage.
once done, go back to the main screen of recovery, main screen only, no sub menu's.
download the rom again and put in the same folder as adb and fastboot again.
then with your phone plugged in, rom in the folder, and a command window open type:
Code:
adb push (name-of-rom).zip /sdcard/
takes a while and will look unresponsive but the cmd window will let you know when its done.
once done, unplug your phone, and slect install, select the rom from the list and swipe to begin the install.
Seanie280672 said:
that was quick, enter recovery, and select wipe, swipe to factory reset then I always go into advanced wipe too and select everything except internal storage.
once done, go back to the main screen of recovery, main screen only, no sub menu's.
download the rom again and put in the same folder as adb and fastboot again.
then with your phone plugged in, rom in the folder, and a command window open type:
Code:
adb push (name-of-rom).zip /sdcard/
takes a while and will look unresponsive but the cmd window will let you know when its done.
once done, unplug your phone, and slect install, select the rom from the list and swipe to begin the install.
Click to expand...
Click to collapse
So in the command window, I put the full name of the rom download file?
mrchris814 said:
So in the command window, I put the full name of the rom download file?
Click to expand...
Click to collapse
yeah, easiest way is once you've downloaded the rom, just change the file name to rom.zip then move it to the adb and fastboot folder, then adb push rom.zip /sdcard/
Seanie280672 said:
yeah, easiest way is once you've downloaded the rom, just change the file name to rom.zip then move it to the adb and fastboot folder, then adb push rom.zip /sdcard/
Click to expand...
Click to collapse
Okay.. I'll let you know when I'm finished with all of it.
Seanie280672 said:
yeah, easiest way is once you've downloaded the rom, just change the file name to rom.zip then move it to the adb and fastboot folder, then adb push rom.zip /sdcard/
Click to expand...
Click to collapse
And also, since I already wiped, do I have to do it again in Aroma Installer, or can I continue without wipe?
mrchris814 said:
And also, since I already wiped, do I have to do it again in Aroma Installer, or can I continue without wipe?
Click to expand...
Click to collapse
its only a wipe of data, so I would just go ahead and wipe just to be sure.
Seanie280672 said:
its only a wipe of data, so I would just go ahead and wipe just to be sure.
Click to expand...
Click to collapse
As soon as I hit Finish, the screen went black.. Is that normal?
mrchris814 said:
As soon as I hit Finish, the screen went black.. Is that normal?
Click to expand...
Click to collapse
that happens sometimes, just hold the power button down till the lights on the bottom flash 10 - 15 times, the phone will reset and pick up where it left off and start booting.
Seanie280672 said:
that happens sometimes, just hold the power button down till the lights on the bottom flash 10 - 15 times, the phone will reset and pick up where it left off and start booting.
Click to expand...
Click to collapse
Okay.. Everything is working now.. Thank you so much.. You really saved me with this.
mrchris814 said:
Okay.. Everything is working now.. Thank you so much.. You really saved me with this.
Click to expand...
Click to collapse
your welcome, and learned adb and fastboot along the way too, better than using compiled apps to flash things.
same problem, but different result...
Seanie280672 said:
your welcome, and learned adb and fastboot along the way too, better than using compiled apps to flash things.
Click to expand...
Click to collapse
Hi Seanie,
I followed the instructions on this post, as I was having a similar problem. I installed the Apolo7 v4.1 rom on my phone using CWM instead of TWRP and entered a boot loop. After following your instructions for installing ADB and flashing TWRP, when I try to enter recovery to perform a wipe it won't and goes back into a boot loop wherein it is perpetually trying to enter recovery. Any suggestions?
thanks!
Seanie280672 said:
your welcome, and learned adb and fastboot along the way too, better than using compiled apps to flash things.
Click to expand...
Click to collapse
Seanie, I found your advice very useful. Thanks for taking the time to walk us noobs through. In my case it didn't work at first but after I found the right version of TWRP for my HTC One it worked fine. Thanks!
I recorded my experience here: http://forum.xda-developers.com/htc...m-802w-stuck-bootloader-t2835693#post54576527
Can anybody help my out, because I somehow deleted my OS in my rooted Nexus 6
I tried to use the Nexus Root Toolkit to flash it to stock, but it telling that it can't load it.
load_file: could not allocate 1785963604 bytes
error: cannot load 'C:\Program Files (x86)\WugFresh Development\Nexus Root Toolk
it\data\Factory_Images\shamu\-lyz28e-factory-b542b88a\image-shamu-lyz28e\system.img
What should I do ?
Zleach said:
Can anybody help my out, because I somehow deleted my OS in my rooted Nexus 6
I tried to use the Nexus Root Toolkit to flash it to stock, but it telling that it can't load it.
load_file: could not allocate 1785963604 bytes
error: cannot load 'C:\Program Files (x86)\WugFresh Development\Nexus Root Toolk
it\data\Factory_Images\shamu\-lyz28e-factory-b542b88a\image-shamu-lyz28e\system.img
What should I do ?
Click to expand...
Click to collapse
fastboot flash the stock factory image the right way, via fastboot, while youre in your bootloader. heres a read me with instructions http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
btw, you shouldnt use root toolkits until you are at the point of you knowing what you are doing.
Try to flash stock google image from bootloader if u can get to the bootloader using power and volume down button.
Sent from my Nexus 6 using Tapatalk
I tried the 1st method
but it telling me that in CMD window that "fastboot is not recognized as an internal or external command,
operable program or batch file
Zleach said:
I tried the 1st method
but it telling me that in CMD window that "fastboot is not recognized as an internal or external command,
operable program or batch file
Click to expand...
Click to collapse
Do you have fastboot and abd installed. If so you are opening cmd in wrong place or environmental variable path missing or wrong.
Zleach said:
I tried the 1st method
but it telling me that in CMD window that "fastboot is not recognized as an internal or external command,
operable program or batch file
Click to expand...
Click to collapse
Install this:
http://forum.xda-developers.com/showthread.php?t=2588979
Now you can use fastboot/ADB from anywhere on your PC.
Also, use method #2 from the link provided earlier. Flash-all doesn't work.
prdog1 said:
Do you have fastboot and abd installed. If so you are opening cmd in wrong place or environmental variable path missing or wrong.
Click to expand...
Click to collapse
I'm not sure if I have fastboot and abd installed in my windows
I thought fastboot would be my phone bootloader mode
Zleach said:
I'm not sure if I have fastboot and abd installed in my windows
I thought fastboot would be my phone bootloader mode
Click to expand...
Click to collapse
If not sure you don't. Follow @Evolution_Tech's last post.
Zleach said:
I'm not sure if I have fastboot and abd installed in my windows
I thought fastboot would be my phone bootloader mode
Click to expand...
Click to collapse
Follow the link I provided. You'll be all set.
Evolution_Tech said:
Follow the link I provided. You'll be all set.
Click to expand...
Click to collapse
Haha. Had to edit my post. Yall all look alike.
Thank You
everyone for helping me out
you guys really save me
method 2 plus this video from youtube help me out alot
" youtube.com/watch?v=I5Uwv-dd1y4&feature=iv&src_vid=5ka5dnPghzI&annotation_id=annotation_3822850285"
If you can get in twrp you just have to format data,I was stuck fir 2days
johhnyred23 said:
If you can get in twrp you just have to format data,I was stuck fir 2days
Click to expand...
Click to collapse
I was in twrp in recovery
and I think I formatted the data which might have cause me to wipe out the OS on my Nexus 6
or I might have checked something else to be wipe out
Alternative is copyright rom to sdcard using twrp and flash
Zleach said:
I was in twrp in recovery
and I think I formatted the data which might have cause me to wipe out the OS on my Nexus 6
or I might have checked something else to be wipe out
Click to expand...
Click to collapse
I made a thread you should have read stating just how not to Do this damage lol... Like I did to myself .
Any time you wipe data/format in twrp your gonna delete the whole operating system .
Make sure you check mark oem unlock box in settings\developer options ,Very critical !!
This will always allow you to be able to flash Stock images with fast boot or a tool kit to get the device back to life .
Never oem relock the bootloader with stock recovery cause if you was oem locked/relocked and had deleted the O.S like you did you would have had a bricked phone .
Sent from my Nexus 6 using XDA Free mobile app