Hello,
I visit this forum every day to stay up to date with all the ROMs. Im trying to help fix a friend's phone and I apologize if this is in the wrong forum but I think this forum contains the audience who can help with this. Basically my friend brought me his G2 (which I rooted and put CM7 on it for him) and it wouldnt boot. I know all the regular ways to recover it but when booting into recovery I get these errors:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
Here is a Pastebin with the recovery log:
http://pastebin.com/qT4KMrUj
Cannot update to the newest recovery using fastboot (CWM version is 3.0.0.5) but i booted to CWM 3.0.2.4 with the fastboot boot recovery.img command. I cannot restore a backup, cannot format /boot or /system (get the "error formatting /system" message). I wiped cache and data and this didnt help. Tried loading a new cm7 zip. If I try to flash the latest recovery in fastboot it doesnt work:
c:\download\android-sdk-windows\tools>fastboot flash recovery recovery-clockwork
-3.0.2.4-vision.img
sending 'recovery' (4466 KB)... OKAY [ 0.760s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 0.780s
I tried loading a PC10IMG.zip from an RUU and I get a failed update on the first item. Im thinking this is some kind of partition issue. Does anyone have any ideas? Ive been searching the whole morning and there are a few threads in other forums regarding this and the best luck someone had was flashing with the PC10IMG.zip to fix it. The phone has the engineering hboot.
Code:
c:\download\android-sdk-windows\tools>fastboot oem listpartition
... INFO[merge_mfg]:(MERGEMFG, 10) block start=0,
size=0 (0 KB)
INFO[radio]:(OTHER, 4) block start=0, size=163840 (0 KB)
INFO[merge_emmc]:(RAW, 4) block start=0, size=4194304 (655360 KB
INFO)
INFO[fat]:(RAW, C00) block start=0, size=0 (0 KB)
INFO[local]:(RAW, 0) block start=0, size=0 (0 KB)
INFO[spcustom]:(RAW, 0) block start=0, size=0 (0 KB)
INFO[microp]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[cpld]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[rcdata]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[a1026]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[tp]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[wimax]:(RAW, 0) block start=0, size=0 (0 KB)
INFO[nv]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[htcdata]:(RAW, 7404) block start=143363, size=2048 (1233216
INFO KB)
INFO[radio_reserve]:(RAW, 7504) block start=145412, size=17915 (
INFO1661741 KB)
INFO[dzsystem]:(DEZERO, 8) block start=197122, size=851453 (4257
INFO26 KB)
INFO[dzdata]:(DEZERO, 8) block start=1048576, size=2723841 (1361
INFO920 KB)
INFO[misc]:(RAW, 7601) block start=163328, size=512 (256 KB)
INFO[hboot]:(RAW, 4701) block start=163841, size=2048 (1024 KB)
INFO[sp1]:(RAW, 3401) block start=165890, size=2048 (1024 KB)
INFO[wifi]:(RAW, 3601) block start=167939, size=2560 (1280 KB)
INFO[recovery]:(RAW, 7101) block start=170500, size=17402 (8701
INFOKB)
INFO[boot]:(RAW, 4801) block start=187903, size=8192 (4096 KB)
INFO[mfg]:(RAW, 7301) block start=196096, size=512 (256 KB)
INFO[misc2]:(RAW, 3101) block start=196609, size=512 (256 KB)
INFO[system]:(EXT3, 8301) block start=197122, size=851453 (42572
INFO6 KB)
INFO[userdata]:(EXT3, 8301) block start=1048576, size=2723841 (1
INFO361920 KB)
INFO[cache]:(EXT3, 8301) block start=3772418, size=419431 (20971
INFO5 KB)
INFO[devlog]:(EXT3, 1901) block start=4191850, size=40960 (20480
INFO KB)
OKAY [ 0.153s]
finished. total time: 0.153s
Thanks!
I just have to comment on the purple smileys all over nice touch lol!
Sent from my HTC Vision using XDA Premium App
xsteven77x said:
I just have to comment on the purple smileys all over nice touch lol!
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Yep, I fixed that with the code box. LOL
Can you use fastboot to boot the newest recovery?
"fastboot boot recovery recovery.img"
It sounds like the paritions are formatted in way the recovery is having a hard time with. The best thing to do would be to flash the older CWR from the 2 series then format and wipe all over the place. The try booting a froyo based rom and you should be good.
Then you can try to go back to CWR 3 series.
1wayjonny said:
Can you use fastboot to boot the newest recovery?
"fastboot boot recovery recovery.img"
It sounds like the paritions are formatted in way the recovery is having a hard time with. The best thing to do would be to flash the older CWR from the 2 series then format and wipe all over the place. The try booting a froyo based rom and you should be good.
Then you can try to go back to CWR 3 series.
Click to expand...
Click to collapse
Yep I tried this. I booted into the CWM 2.5.1.3 and tried to wipe and format /boot and /system but I get errors just like in CWM3.
I had this same issue one time and thought my phone was shot, just take the original shipping rom and flast it via fastboot boot as the PC10IMG.zip to fix this issue.
I know you have tried already, I have been at this stage just keep trying the PC10IMG.zip from a different source but that is the correct way to fix your issue if you tried previous CWR's.
try manually mounting the partition:
e2fsck -p /dev/block/mmcblk0p27
mount /dev/block/mmcblk0p27 /cache
1wayjonny said:
I had this same issue one time and thought my phone was shot, just take the original shipping rom and flast it via fastboot boot as the PC10IMG.zip to fix this issue.
I know you have tried already, I have been at this stage just keep trying the PC10IMG.zip from a different source but that is the correct way to fix your issue if you tried previous CWR's.
Click to expand...
Click to collapse
Can you recommend a particular file to use? Im looking at a list here:
http://shipped-roms.com/index.php?category=android&model=Vision
I would try these:
http://shipped-roms.com/download.php?category=android&model=Vision&file=PC10IMG_Vision_TMOUS_1.12.531.0_Radio_12.18.60.05P_26.01.00.17_M2_test_144460.zip
If that doesn't work try this one
http://shipped-roms.com/download.ph....09b_26.02.01.15_M2_release_149459_signed.zip
If these dont work I would be surprised and yes something more may be messed up.
I'm glad that this issue is getting more attention today. It has been occurring with more and more frequency since the release of the new CWM Recovery and CM7...
Well I thought I was the only one, this happened from using a specific build of the CWR 3 series.
Nice to know its wasn't just me but I def think its has to do with formatting of the partition but could be wrong.
Well, neither of those PC10IMG.zip worked. Im looking at another thread here to hopefully help out. Looks like a partition issue like I thought. Only thing is how to fix it?
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
Guys, I finally figured out how to fix this issue. It took me forever and I thought my recovery was lost but this fixed it.
Couple of things you have to do:
Download the latest ClockworkMod and rename it to recovery.img
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Try to restore again
Yes erase the cache twice from fastboot.
open1your1eyes0 said:
Guys, I finally figured out how to fix this issue. It took me forever and I thought my recovery was lost but this fixed it.
Couple of things you have to do:
Download the latest ClockworkMod and rename it to recovery.img
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Try to restore again
Yes erase the cache twice from fastboot.
Click to expand...
Click to collapse
The problem is that i cant get it to do anything.
Code:
c:\download\android-sdk-windows\tools>fastboot erase cache
erasing 'cache'... FAILED (remote: erasing error!)
finished. total time: 2.829s
c:\download\android-sdk-windows\tools>adb reboot bootloader
error: device not found
c:\download\android-sdk-windows\tools>fastboot flash recovery recovery-clockwork
-3.0.2.4-vision.img
sending 'recovery' (4466 KB)... OKAY [ 0.765s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 0.784s
c:\download\android-sdk-windows\tools>
In the thread i posted above, they talk about using "parted" to get the partitions back but I dont see where you can do thoe ADB commands. They suggest you can do them in recovery but I tried and there is no ADB device when in CWM.
Hopefully this isn't too off topic, but is there a tool that can be used to perform a health check of the internal and external storage of our phones? Everything on my phone is working just fine, but would love that guarantee that it's in good order.
Thanks.
amazinglarry311 said:
try manually mounting the partition:
e2fsck -p /dev/block/mmcblk0p27
mount /dev/block/mmcblk0p27 /cache
Click to expand...
Click to collapse
Where can I issue these commands? I cannot get a shell.
Stupid question about the PC10IMG.zip method...
It probally is but confirm the card is formatted as FAT32 for fastboot
Also is there any swap partitions etc..
If the SDCARD has partitions redo it as one FAT32 partition or use an alternate SDCARD with one FAT32 partition
popokrew said:
The problem is that i cant get it to do anything.
Code:
c:\download\android-sdk-windows\tools>fastboot erase cache
erasing 'cache'... FAILED (remote: erasing error!)
finished. total time: 2.829s
c:\download\android-sdk-windows\tools>adb reboot bootloader
error: device not found
c:\download\android-sdk-windows\tools>fastboot flash recovery recovery-clockwork
-3.0.2.4-vision.img
sending 'recovery' (4466 KB)... OKAY [ 0.765s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 0.784s
c:\download\android-sdk-windows\tools>
In the thread i posted above, they talk about using "parted" to get the partitions back but I dont see where you can do thoe ADB commands. They suggest you can do them in recovery but I tried and there is no ADB device when in CWM.
Click to expand...
Click to collapse
Oh the issue appears to be the fact that adb cannot find your device. Go into device manager and see if you see any missing drivers with the exclamation mark (should be called ADB or something like that).
Force install these drivers I have uploaded: Link
Also after you do "adb reboot bootloader" command you need to install the drivers again because it reboots into another mode.
Make sure you select "Android ADB Interface" as the driver and if it asks you that its not compatible just click Yes anyways.
open1your1eyes0 said:
Guys, I finally figured out how to fix this issue. It took me forever and I thought my recovery was lost but this fixed it.
Couple of things you have to do:
Download the latest ClockworkMod and rename it to recovery.img
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Try to restore again
Yes erase the cache twice from fastboot.
Click to expand...
Click to collapse
nvm found it. for those who might be following this thread and also need it you can find it here
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-vision.img
open1your1eyes0 said:
Oh the issue appears to be the fact that adb cannot find your device. Go into device manager and see if you see any missing drivers with the exclamation mark (should be called ADB or something like that).
Force install these drivers I have uploaded: Link
Also after you do "adb reboot bootloader" command you need to install the drivers again because it reboots into another mode.
Make sure you select "Android ADB Interface" as the driver and if it asks you that its not compatible just click Yes anyways.
Click to expand...
Click to collapse
I can't use adb because I can only get to fastboot and thus, I can only use the fastboot command. Unless I'm missing something? I do have the device in device manager with the driver loaded. I have loaded many radios through fastboot so I know the connection is working. The trick is to get an adb shell, but what state do you want the phone in? Right now I can only get to fastboot or recovery (can't do adb there either).
Sent from my HTC Vision using XDA App
Related
Hello everyone, I made a mistake (I am a big noob) and I don't know how to fix it.
I wanted to have fresh phone (real factory reset) to back-up and start over, so in recovery mode (interim one from paul) I wiped data, cache partition and I also formated cache,data, sdcard and system.
Now, I am stuck on htc quietly brilliant screen, I have access to hboot, recovery etc. I have been looking for a solution for 2 days without succes, I am sad.
Can someone help please ? thanks guys.
You wiped the system so there is no android on there!
Eirher download a new Rom and flash or relock bootloader and use ruu
Sent from my HTC One X using xda premium
Thanks sir, I'll try.
sotirios said:
Thanks sir, what can I do ? Which part I did wrong ? thanks again
Click to expand...
Click to collapse
The part you did wrong: It's true that you wipe (dalvik) cache and data before flashing a custom rom. That will perform a factory reset. Wiping system means deleting android itself, as stated before. That's what you did wrong.
Now, we can't know why you wanted to start all over again, but assuming you already flashed a custom recovery, you wanted to install a custom rom. Just go ahaed and do so, your problem will be fixed.
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
sotirios said:
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
Click to expand...
Click to collapse
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push path/to/custom/rom /sdcard
or for linux/mac:
sudo ./adb push path/to/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
dobbi10k said:
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard
or for linux/mac:
sudo ./adb push pfad/zu/einer/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
Click to expand...
Click to collapse
That wont work as ADB does not work on any of the custom recoveries at the moment. Im stuck in the same situtation at the mo and as phone is branded cant get the RUU to reflash so just playing the waiting game until either ADB/USB mount available in recovery or S-Off available.
See my thread in development thread
http://forum.xda-developers.com/showthread.php?t=1599748
Sent from my HTC One X using XDA
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
"Eirher download a new Rom and flash"
I can't flash, my ssd is wiped too and i can't mount usb with this custom recovery
"That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard"
It doesn't work, it doesn't find my device, even with the adb devices command
sotirios said:
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
Click to expand...
Click to collapse
Go to development thread then shipped ruu ans download specific to ur phone. Follow and Job done
Sent from my HTC One X using XDA
Same problem here! I unfortunatly erase everything from my one x and i can't restore anything!! How can i solve it?? My device is unlocked but stay in s-on mode! Why? From fastboot i can't flash anything! Help!!
Hello folks, problem solved by following leejames instructions :
flash stock recovery
relock bootloader
use ruu
I'm so happy. Thanks.
Mee too!! Thanks a lot!! I'm very very very very very very very very very very very very very very happy!!
1 flash stock recovery
2 relock bootloader
3 use ruu
It works fine!!
I do exactly the same thing , but half way through the RUU process it gives me an error saying i need the correct RUU. anyone can help ?
All you have to do is grab an RUU, run it. now on your pc search for %temp%in there locate ROM.zip. Extract the boot.img and system.img. and push them thru fastboot
Code:
fastboot flash boot boot_signed.img
Code:
fastboot flash system system.img
Code:
adb reboot
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
mahdibassam said:
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
Click to expand...
Click to collapse
Is your bootloader unlocked?
When I do it with an unlocked bootloader the error changes to this:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
Nobody can help me?!! ((
hello everyone
last night i installed the stock image 4.0.4 using FASTBOOT
and it's done seccussfuly BUT...
there is no recovery
i used FASTBOOT to install CWM and used it to root my phone
but every time i reboot i don't get any recovery at all
all i find is green android with red triangle and exclamation mark
how i can restore my recovery ?
That is the stock recovery.
You have to press both volume buttons (and power?) to enter recovery.
But try flashing with Rom Manager if you still have root access.
If not...
Use my guide (sig) to get SU again.
i had 4.0.2 with CMW recovery
then i flashed CM9
then i had the signal bug
and i heared about the fix
so i downloaded the 4.0.4 Stock rom
tell now every thing ok
then i downloaded the SU.ZIP and went to fastboot mode then recovery to install the zip, but it wasn't there
so i downloaded the recovery.img for CMW the normal one and the touch one
and flashed them using fastboot
it worked but when i restart the phone it just disaper
and i do have root access ans i flashed the CWM using rom manager
it show successfully installed but there is no recovery
to access recovery i press vol+, vol-, and power then select Recovery mod
thanx for the fast reply
i tried "fastboot erase recovery" then "fastboot flash recovery recovery.img"
and didn't work
then downloaded the 4.0.2 rom but still no recovery
here is the log:
C:\Users\X-Ahmad\Desktop\jj\r4-galaxynexus-gsm-superboot>fastboot erase recovery
erasing 'recovery'... OKAY
C:\Users\X-Ahmad\Desktop\jj\r4-galaxynexus-gsm-superboot>fastboot flash recovery
tuna-stock-recovery.img
sending 'recovery' (12224 KB)... OKAY
writing 'recovery'... OKAY
C:\Users\X-Ahmad\Desktop\jj\r4-galaxynexus-gsm-superboot>fastboot flash bootload
er bootloader-maguro-primekk15.img
sending 'bootloader' (2308 KB)... OKAY
writing 'bootloader'... OKAY
C:\Users\X-Ahmad\Desktop\jj\r4-galaxynexus-gsm-superboot>fastboot reboot-bootloa
der
rebooting into bootloader... OKAY
C:\Users\X-Ahmad\Desktop\jj\r4-galaxynexus-gsm-superboot>fastboot flash radio ra
dio-maguro-i9250xxkk6.img
sending 'radio' (12288 KB)... OKAY
writing 'radio'... OKAY
C:\Users\X-Ahmad\Desktop\jj\r4-galaxynexus-gsm-superboot>fastboot reboot-bootloa
der
rebooting into bootloader... OKAY
C:\Users\X-Ahmad\Desktop\jj\r4-galaxynexus-gsm-superboot>fastboot -w update imag
e-yakju-icl53f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I9250XXKK6
Serial Number........: 014E0F500E007014
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (4074 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (4406 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (317594 KB)... OKAY
writing 'system'... OKAY
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
rebooting...
C:\Users\X-Ahmad\Desktop\jj\r4-galaxynexus-gsm-superboot>
Click to expand...
Click to collapse
then i root it and downloaded the rom manager to flash CWM recovery mod
and it worked
now how can i update to 4.0.4 without losing my recovery ?
The problem you are having is that the stock os overwrites recovery everytime you boot. You need to flash a rooted stock ROM, flash a rooted kernel, or delete recovery-boot.p file from the system folder.
Sent from my Galaxy Nexus
interesting...
i'll try it and post a reply
thanx alot
ahmad.afef said:
interesting...
i'll try it and post a reply
thanx alot
Click to expand...
Click to collapse
And the winner is ??
sorry i forgot about it
i didn't found the file i have to remove but what i did is
1- booted the recovery IMG using fastboot
2- installed new rom
3- installed recovery
and now it's fine
ahmad.afef said:
sorry i forgot about it
i didn't found the file i have to remove but what i did is
1- booted the recovery IMG using fastboot
2- installed new rom
3- installed recovery
and now it's fine
Click to expand...
Click to collapse
bwcorvus said:
The problem you are having is that the stock os overwrites recovery everytime you boot. You need to flash a rooted stock ROM, flash a rooted kernel, or delete recovery-boot.p file from the system folder.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks ahmad.afef.
I did have success with bwcorvus solution
This 3 commands did the job:
1) mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
2) cd /system
3) mv recovery-from-boot.p recovery (inside /system)
Works like a charm and recovery does not get deleted every time I boot.
Suceess
yah back then i would never understand what is
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
thats why i did the boot thing
now i quit understand a bit of ADB commands
any way, it's good to know
bwcorvus said:
The problem you are having is that the stock os overwrites recovery everytime you boot. You need to flash a rooted stock ROM, flash a rooted kernel, or delete recovery-boot.p file from the system folder.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Just to clarify, that file does not exist on a stock ROM -- it only appears if you've ever applied an OTA update.
Hi! The story goes like this:
A friend of mine gave me a bricked Galaxy Nexus to resurrect: the phone keeps playing the colors animations and never ends booting up, but I can enter fastboot and recovery modes.
Things I tried:
1) efrant guide to return to stock.
Here is the big problem: after doing the 'fastboot oem unlock', at the bottom it appears in red text 'LOCK STATE - UNLOCKED'. But then I do a 'fastboot reboot-bootloader' and it changes to LOCKED again, so I can't complete the steps because of this. I think this is what is causing all the troubles.
2) Flash JB package with Odin.
3) Flash ICS package with Odin.
This last two completed successfully, but the phone is having the same problem, there were no changes. The bootloader version is always PRIMEKK15.
Any hints? Maybe it's a hardware problem and there's no software solution? It's a shame, because I can access fastboot and recovery, but everything I tried doesn't seem to work.
Big thanks.
seems to me that the unlock token is not sticking somehow. have you tried relocking it right after you unlock it? for example, can you 'fastboot boot customrecovery.img' and enter cwm after you unlock?
sent from my i9250
bk201doesntexist said:
seems to me that the unlock token is not sticking somehow. have you tried relocking it right after you unlock it? for example, can you 'fastboot boot customrecovery.img' and enter cwm after you unlock?
sent from my i9250
Click to expand...
Click to collapse
Yes, if I do:
# fastboot oem unlock
# fastboot boot cwm-recovery.img
It enters CWM just fine. The problems seems to be that the changes are not persistent, or at least that's what it shows the info in the fastboot mode. Even after all the things I flashed, the bootloader never changed.
I will be trying to relock it right after unlocking it and I'll post the results.
Thanks.
envidia said:
Even after all the things I flashed, the bootloader never changed.
Thanks.
Click to expand...
Click to collapse
You can try to use the GALAXY NEXUS TOOLKIT V7.8. It has many helpful features for unlocking, rooting, flashing factory images, or separate radio\bootloader images. User-friendly GUI are included.
Feinar said:
You can try to use the GALAXY NEXUS TOOLKIT V7.8. It has many helpful features for unlocking, rooting, flashing factory images, or separate radio\bootloader images. User-friendly GUI are included.
Click to expand...
Click to collapse
He already knows how to use fastboot. There is no need for him to use a toolkit which does nothing different aside from hide the commands from you...
Guess he have his 10 posts now so he won't post for a while ^^
Feinar said:
You can try to use the GALAXY NEXUS TOOLKIT V7.8. It has many helpful features for unlocking, rooting, flashing factory images, or separate radio\bootloader images. User-friendly GUI are included.
Click to expand...
Click to collapse
And don't recommend toolkits to people asking for help, 3/4 of the time they are clueless, recommending it to them will just make them sink deeper in to a god knows how deep pool of sh*t. No offence to you though, just don't recommend toolkits next time
Thanks guys.
I'm reading that people recommend doing an OMAP flash, but only when the phone is completely dead. I can get to fastboot / Odin mode, is there anything that I should try before doing an OMAP flash?
envidia said:
Thanks guys.
I'm reading that people recommend doing an OMAP flash, but only when the phone is completely dead. I can get to fastboot / Odin mode, is there anything that I should try before doing an OMAP flash?
Click to expand...
Click to collapse
i think we already ran out of options. you could try omapflash... although i still think it's an issue with the unlock token/nand.
bk201doesntexist said:
have you tried relocking it right after you unlock it?
Click to expand...
Click to collapse
I've just tried that and it works as expected.
# fastboot oem unlock
*It says the bootloader is unlocked in the phone display*
# fastboot oem lock
*It says the bootloader is locked again in the phone display*
Then I tried flashing the ICL53F 4.0.2 stock image through fastboot, because it uses the bootloader that I have at the moment. It didn't work, it's still stuck at the animation colors. Look at the results, it all seems ok:
Code:
[B]# ./fastboot oem unlock[/B]
...
OKAY [ 10.102s]
[B]# ./fastboot -w update image-yakju-icl53f.zip[/B]
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I9250XXKK6
Serial Number........: 0149C25E0200A00B
--------------------------------------------
checking product...
OKAY [ 0.007s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.008s]
sending 'boot' (4074 KB)...
OKAY [ 0.436s]
writing 'boot'...
OKAY [ 2.510s]
sending 'recovery' (4406 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 4.459s]
sending 'system' (317594 KB)...
OKAY [ 40.473s]
writing 'system'...
OKAY [1387.576s]
erasing 'userdata'...
OKAY [ 0.035s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [262.626s]
erasing 'cache'...
OKAY [ 0.007s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 15.788s]
rebooting...
finished. total time: 1714.590s
The only thing that caught my attention is the fact that the process lasted almost 29 minutes. I don't know if that's normal.
Follow the steps in my guide here (instead of using the fastboot update command), with the following exception: instead of doing step 10, replace that step with: fastboot erase userdata
efrant said:
Follow the steps in my guide here (instead of using the fastboot update command), with the following exception: instead of doing step 10, replace that step with: fastboot erase userdata
Click to expand...
Click to collapse
I did:
Code:
[B]# ./fastboot oem unlock[/B]
...
OKAY [ 9.623s]
finished. total time: 9.623s
[B]# ./fastboot flash bootloader bootloader-maguro-primekk15.img[/B]
sending 'bootloader' (2308 KB)...
OKAY [ 0.324s]
writing 'bootloader'...
OKAY [ 7.972s]
finished. total time: 8.296s
[B]# ./fastboot flash radio radio-maguro-i9250xxkk6.img[/B]
sending 'radio' (12288 KB)...
OKAY [ 1.739s]
writing 'radio'...
OKAY [ 4.395s]
finished. total time: 6.134s
[B]# ./fastboot flash system image-yakju-icl53f/system.img[/B]
sending 'system' (317594 KB)...
OKAY [ 43.399s]
writing 'system'...
OKAY [1387.456s]
finished. total time: 1430.855s
[B]# ./fastboot erase userdata[/B]
erasing 'userdata'...
OKAY [ 0.033s]
finished. total time: 0.033s
[B]# ./fastboot flash boot image-yakju-icl53f/boot.img[/B]
sending 'boot' (4074 KB)...
OKAY [ 0.568s]
writing 'boot'...
OKAY [ 4.384s]
finished. total time: 4.953s
[B]# ./fastboot flash recovery image-yakju-icl53f/recovery.img[/B]
sending 'recovery' (4406 KB)...
OKAY [ 0.620s]
writing 'recovery'...
OKAY [ 4.458s]
finished. total time: 5.079s
[B]# ./fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.007s]
finished. total time: 0.007s
[B]# ./fastboot reboot[/B]
rebooting...
finished. total time: 0.006s
It isn't working, same result as always.
I'm new to this Android world, so I have to ask: could CWM or similar custom recovery offer some additional method to try? Because I can boot CWM recovery, but I don't know if can do something from there.
Thank you guys.
can we get a logcat of the bootloop?
anyways, if you flash cwm, does it stick? it doesnt, i assume. be reminded that /system/recovery-from-boot.p needs to be renamed or removed, if exists.
imo, using cwm to flash a rom won't do much here, given the current situation.
sent from my i9250
bk201doesntexist said:
can we get a logcat of the bootloop?
anyways, if you flash cwm, does it stick? it doesnt, i assume. be reminded that /system/recovery-from-boot.p needs to be renamed or removed, if exists.
imo, using cwm to flash a rom won't do much here, given the current situation.
Click to expand...
Click to collapse
About the logcat, I've read that you have to use adb, but it never worked for me. When I do:
Code:
[B]# ./adb devices[/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
<empty space here>
I can boot the CWM recovery. If I flash it, it doesn't stick. I don't know how to delete /system/recovery-from-boot.p, do I need adb?
I tried the OMAP flash, then tried to unlock the bootloader and after the fastboot reboot-bootloader, it gets locked again.
I'm reading lots of threads with bricked Galaxy Nexus, but never one with this behavior.
Only thing I can suggest is try fast booting a different bootloader version to a newer one.
http://forum.xda-developers.com/showthread.php?t=1587498
Sent from my Galaxy Nexus
The Gingerbread Man said:
Only thing I can suggest is try fast booting a different bootloader version to a newer one.
http://forum.xda-developers.com/showthread.php?t=1587498
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
it seems it always stays on kk15
sent from my i9250
bk201doesntexist said:
it seems it always stays on kk15
sent from my i9250
Click to expand...
Click to collapse
OK then odd, the other thing I'd suggest is go to the Google factory image website https://developers.google.com/android/nexus/images then using mskips tool kit there is a feature to turn the .IMG into .tar (I think its .tar?) which can then be using in Odin mode instead. Flashing this way is different than fast boot and the Google factory images contain boot loader and radio and obviously a ROM.
Sent from my Galaxy Nexus
envidia said:
About the logcat, I've read that you have to use adb, but it never worked for me. When I do:
Code:
[B]# ./adb devices[/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
<empty space here>
Click to expand...
Click to collapse
That is because your ADB driver is not installed. It seems like you have the fastboot driver installed, but not the ADB driver.
envidia said:
I can boot the CWM recovery. If I flash it, it doesn't stick. I don't know how to delete /system/recovery-from-boot.p, do I need adb?
I tried the OMAP flash, then tried to unlock the bootloader and after the fastboot reboot-bootloader, it gets locked again.
I'm reading lots of threads with bricked Galaxy Nexus, but never one with this behavior.
Click to expand...
Click to collapse
Since you've already tried fastboot, odin and omapflash, I doubt anything else will work. The only other thing I can think of that could possibly work is for flash the bootloader using dd, but I doubt it. Most likely a hardware issue.
The Gingerbread Man said:
OK then odd, the other thing I'd suggest is go to the Google factory image website https://developers.google.com/android/nexus/images then using mskips tool kit there is a feature to turn the .IMG into .tar (I think its .tar?) which can then be using in Odin mode instead. Flashing this way is different than fast boot and the Google factory images contain boot loader and radio and obviously a ROM.
Click to expand...
Click to collapse
Thanks, The Gingerbread Man. I've already tried flashing stock images through Odin and there's no change at all.
efrant said:
That is because your ADB driver is not installed. It seems like you have the fastboot driver installed, but not the ADB driver.
Click to expand...
Click to collapse
I'm on Linux, I thought that if fastboot is working, adb should work as well. I'm trying adb with the phone in fastboot mode, should I try in Odin or recovery mode?
efrant said:
Since you've already tried fastboot, odin and omapflash, I doubt anything else will work. The only other thing I can think of that could possibly work is for flash the bootloader using dd, but I doubt it. Most likely a hardware issue.
Click to expand...
Click to collapse
Let's suppose the problem is the NAND flash memory, is it replaceable? Of course I'm not doing it myself, but I'm thinking if the phone has to be replaced by a new one, or can be repaired.
envidia said:
I'm on Linux, I thought that if fastboot is working, adb should work as well. I'm trying adb with the phone in fastboot mode, should I try in Odin or recovery mode?
Click to expand...
Click to collapse
Oops, forgot you were using linux (so no drivers required). But ADB should not work your device is booted in fastboot mode or odin mode. It will only work when you are booted into recovery or into Android.
envidia said:
Let's suppose the problem is the NAND flash memory, is it replaceable? Of course I'm not doing it myself, but I'm thinking if the phone has to be replaced by a new one, or can be repaired.
Click to expand...
Click to collapse
Not really. You would need to replace the motherboard as a whole.
Hi, my kf2 is stucked at fastboot, i'm not able to boot into recovery or system, i have succesfully installed fff-1.4a using a factory cable (because it was bricked with the stock bootloader) and have installed the otter2-twrp-2.4.4.0-recovery.img from hashcode..
It boots and i see the blue kindle logo, and have a menu, but when i select recevery it just turns on the amber light and stays there, i have left it for about 5 minutes waiting to see if it get to revery with no luck.
I tried this:
Code:
sudo fastboot -i 0x18d1 getvar product
< waiting for device >
product: kindle
finished. total time: 0.000s
sudo fastboot -i 0x18d1 oem format
...
OKAY [ 0.068s]
finished. total time: 0.068s
Then
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
sudo fastboot reboot
rebooting...
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
It succeed as you can see, it has the fff bootloader and twrp recovery is installed!!
Then i tried
Code:
sudo fastboot -i 0x18d1 flash zip cm-10.1-20130704-NIGHTLY-otter2.zip
< waiting for device >
sending 'zip' (155204 KB)...
OKAY [ 38.806s]
writing 'zip'...
FAILED (remote: partition does not exist)
finished. total time: 38.813s
It seem like a partition table problem maybe because i'm trying to install Cyanogenmod and not a stock image...
I think maybe i must reformat the partitions but i only have access to fastboot and i have read the documentation of Android Fastboot in OmapPedia but i'm not sure it's a "generic" information and don't want to mess up things more.
I have read many trheads in the forum but all of them use adb and there's not a thread with instructions about it..
Or maybe i need to flash all the images (system, kernel, etc..) with fastboot but i don't know where to get it, the main problem is that i'm not able to boot into recovery and maybe that point to the real problem
Any help is appreciated !!
Thank's
You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
How?
mindmajick said:
You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Maybe it is the problem as fastboot oem format seems to do the job...
I have downloaded the stock update-kindle-6.3.2_D01E_4110520.bin, please can you point to the thread explainig how to do that using fastboot or it's just as easy as rename the file to update.zip and flash it directly?
Edited: also i'm not completely sure it's a kf2 and can't get a hint on how to discover it without knowing the is version :banghead: I've looked one the motherboard and is a MB0090 F3F.
I've downloaded the stock bin for the kf2 too...
Thank' for your quick reply
Well. If you have a kf2... The update you downloaded is wrong. IT'S FOR THE ORIGINAL KINDLE FIRE.
Without knowing what device u have u better slow down a sec. Any advice i give COULD permabrick u of you're on the wrong device.
What color was the BOX it came in? What is the model# on the back? (Same for kf1 AND 2 BUT NOT THE KF HD 7" OR 8").
Be advised- this device is EASY TO BRICK. BE CAREFUL.
--
Sent from my mind to your screen.
---------- Post added at 02:48 AM ---------- Previous post was at 02:40 AM ----------
Also. The correct update file wont work either.
You can only flash image files from fastboot.
--
Sent from my mind to your screen.
It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.
soupmagnet said:
It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.
Click to expand...
Click to collapse
Well you are completely right!! Didn't realize I was flashing it to the kernel partition, I bought this on eBay and it was already bricked, when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Sent from my SPH-D710 using xda premium
LUC4X said:
when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Click to expand...
Click to collapse
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?
Glad you are here soupmagnet!
I didn't even look at the commands he was using but i definitely learned stuff from your posts. Thanks again
--
Sent from my mind to your screen.
Commands used
soupmagnet said:
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?
Click to expand...
Click to collapse
Sorry guys i was out of town...
These are the commands (bootloader & recovery) i've used till now:
sudo fastboot -i 0x18d1 flash bootloader fff-u-boot_v1.4a.bin
< waiting for device >
sending 'bootloader' (243 KB)...
OKAY [ 0.065s]
writing 'bootloader'...
OKAY [ 0.083s]
finished. total time: 0.148s
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 2.705s]
finished. total time: 4.748s
Click to expand...
Click to collapse
Also tryed the twrp from teamw's site in both versions (otter & blaze) just to make sure, by issuing the following commands:
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-blaze.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 1.514s]
finished. total time: 3.054s
Click to expand...
Click to collapse
With this, when i reboot and select the recovery it turns on the amber light for 2 seconds and shuts down.
Then when i install the other recovery version (blaze from teamw):
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-otter.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 0.684s]
finished. total time: 2.224s
Click to expand...
Click to collapse
When select recovery i get the same result: amber light for 2 seconds and turns off.
And with hashcode otter2-twrp-2.4.4.0-recovery.img:
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
< waiting for device >
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 0.894s]
finished. total time: 2.937s
Click to expand...
Click to collapse
It hangs on amber light and i have to manually turn it off holding the power buttom for 10 seconds...
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)
LUC4X said:
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)
Click to expand...
Click to collapse
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?
soupmagnet said:
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.
Click to expand...
Click to collapse
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, i've found you uploaded a system.img to androidfilehost...
What do you think?
I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?
soupmagnet said:
I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?
Click to expand...
Click to collapse
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
LUC4X said:
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.
soupmagnet said:
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.
Click to expand...
Click to collapse
Code:
sudo fastboot flash system system.img
sending 'system' (389120 KB)...
OKAY [ 97.308s]
writing 'system'...
OKAY [ 36.819s]
finished. total time: 134.131s
sudo fastboot erase userdata
erasing 'userdata'...
OKAY [116.935s]
finished. total time: 116.935s
sudo fastboot erase cache
erasing 'cache'...
OKAY [ 29.189s]
finished. total time: 29.189s
sudo fastboot reboot
rebooting...
finished. total time: 0.000s
Must be hardware, it's sad... if it where a SMD flash memory i would try to changed it but it's a tyni BGA chip...
Thank you very much for your help
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
I'll try tonight !!
Sent from my SPH-D710 using xda premium
soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
./usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
... OKAY
Installing x-loader...
sending 'xloader' (128 KB)... OKAY
writing 'xloader'... OKAY
Flash FFF...
sending 'bootloader' (211 KB)... OKAY
writing 'bootloader'... OKAY
Flash TWRP...
sending 'recovery' (5260 KB)... OKAY
writing 'recovery'... OKAY
Resetting bootmode to standard boot...
... OKAY
Loading TWRP...
downloading 'boot.img'... OKAY
booting... OKAY
Click to expand...
Click to collapse
Same as before, it won't reboot after sending the boot to recovery command and if try to get into recovery it turns off after an amber light..
LUC4X said:
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?
Click to expand...
Click to collapse
At the begining i saw you were using "fastboot flash zip...." that's wrong command.. should be "fastboot flash update xxxx.zip"
so if you find the totally package, youcan use it.
also you has mixture the boot.img and bootloader.bin..
recovery is not needed if you can flash the right bootloader and boot.:laugh:
I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
gocks said:
I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
Click to expand...
Click to collapse
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
dandrumheller said:
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
Click to expand...
Click to collapse
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
gocks said:
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
Click to expand...
Click to collapse
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using
Click to expand...
Click to collapse
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
gocks said:
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
Click to expand...
Click to collapse
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
gocks said:
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
Click to expand...
Click to collapse
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
gocks said:
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
Click to expand...
Click to collapse
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did exactly what you told me and this happened:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.371s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.683s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10820 KB)...
OKAY [ 0.235s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.235s]
finished. total time: 0.501s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257307 KB)...
OKAY [ 5.493s]
writing 'system'...
OKAY [ 3.985s]
finished. total time: 9.478s
The othes lines seems to be ok, but the phone continue stucked on the "Your device has been unlock...." and don´t reboot.
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
gocks said:
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
Click to expand...
Click to collapse
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
gocks said:
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
Click to expand...
Click to collapse
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
flashallthetime said:
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
Click to expand...
Click to collapse
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
gocks said:
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
Click to expand...
Click to collapse
Which carrier are you with?
And don't sue me if things get worse
flashallthetime said:
Which carrier are you with?
And don't sue me if things get worse
Click to expand...
Click to collapse
Vivo, its a brazilian one.
Relax, if my phone bricks I wont sue you because my wife will kill me first!
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
gocks said:
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
Click to expand...
Click to collapse
Yes and it seems like you can't right to the system and or data partitions. There's more partitions but they're locked or hidden
Try to format your data in TWRP
and wipe system