Im at the part where you must fast the Recovery.
and it just stopped at
Code:
Sending Recovery...<3954 KB>..
do i reboot it now? or what there was no OK or anything
I just flashed the latest recovery via fastboot in Windows terminal and here's what mine says:
fastboot flash recovery XXX.img
sending 'recovery' (4006 KB)... OKAY
writing 'recovery'... OKAY
Which recovery are you flashing?
i got it. i just closed it and did it again.
Related
Hi,
my nexus one completely unusable, it's been a week since i can't use it. the nexus one can't boot, it just stuck on x. it can't boot to recovery, and also when i try passimg method, it just stuck at bootloader - unzipping. anyone have suggestion to fix it ?,
thanks
You need to give us more details
Like, can you get into fast boot/h boot, using the 3 finger salute?
How did it get to this... What were the last things it did...
i can go to fastboot, i can fastboot flash recovery, system, and boot. but it doesn't change. i can still got the same issue as before.
the last thing i did was playing angry birds. after around 15 minutes playing, it just hang, and i need to pull out the battery to turn it off. starting from that point until now, my nexus one just stuck on X.
Try to remove SD card and boot without it to recovery.
Try to fastboot flash recovery stock_recovery.img (find the stock recovery and flash it), see if you can boot to stock recovery.
You may also want to try:
fastboot boot stock_recovery.img
I've been using an Evo on CM7 and GT-i9000 on ROM Kitchen builds so I thought a Nexus One would be fun.
Booted one up today and it was on Froyo... It tried to update automagic.... but now I can only get into fastboot.
I tried to fastboot flash userdata.img, system.img, recovery.img and boot.img but I'm still stuck on a big stupid X like the original poster.
I've tried to flash a cwm and amon ra img and either way no booting or recovery.
I've never been stuck like this. Even when my GT-i9000 goes into a boot loop it's easy to fix. This is totally beyond me.
I've pulled the microsd and "fastboot update signed-passion-GRI40.zip errors with
Device version-baseband is 4.06.00.12_7'
Update requires '5.08.00.04'
I cannot flash the radio.img inside
"android.d3xt3r01.tk/cyanogen/passion/radios/passion.5.08.00.04.zip"
The bar goes red and all the way to the top and just sits for 10 minutes.
I can fastboot update signed-passion-img-FRG83_0923.zip but I only get an X and lock.
Screen says:
*** UNLOCKED ***
nexusone pvt ship s-on
microp-0b15
Touch panel syn0103
Radio 4.06.00.12_7
Oct 12, 2010 14:33:16
Any ideas?
Try the radio images in the wiki...
this is what happen when i try to boot to recovery,
http://www.youtube.com/watch?v=n8DiTfYXUy4
do you think this is hardware issue ?
Hi rheza02
Did you try fastboot update with the file from HTC?
dl4.htc.com/RomCode/Source_and_Binaries/signed-passion-img-GRI40.zip
I got my N1 booting today but it turns out I have bad hardware. My N1 only boots when it's really cold. hahah.
Anyway. All I did was
fastboot update signed-passion-img-FRG83_0923.zip then connect to wifi to update to GRI40
eseale said:
Hi rheza02
Did you try fastboot update with the file from HTC?
dl4.htc.com/RomCode/Source_and_Binaries/signed-passion-img-GRI40.zip
I got my N1 booting today but it turns out I have bad hardware. My N1 only boots when it's really cold. hahah.
Anyway. All I did was
fastboot update signed-passion-img-FRG83_0923.zip then connect to wifi to update to GRI40
Click to expand...
Click to collapse
the link you given redirect me to htc.com/sea, do you have a new link ?,
thanks
---------------Update
i just trying your method.
and it just stuck when flashing the system.
MacBook-Pro:~ rheza02$ /Users/rheza/Downloads/1.0-FRG83-nexusone-insecure/fastboot-mac update /Users/rheza/Downloads/Applications/signed-passion-img-FRG83_0923.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
ERROR: could not get pipe properties
--------------------------------------------
Bootloader Version...: 0.35.0017
Baseband Version.....: 5.08.00.04
Serial Number........: MB0388888888
--------------------------------------------
checking mid... OKAY
checking product... OKAY
checking version-bootloader... OKAY
checking version-microp... OKAY
checking version-baseband... OKAY
sending 'boot' (2338 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (2564 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (125969 KB)... OKAY
writing 'system'...
any suggestion guys ?
guys, can someone help me please ?
thanks
finally, i able to flash using fastboot update technique.
this is the log
---------------
Rheza02:~ rheza$ /Users/rheza02/Downloads/1.0-FRG83-nexusone-superboot/fastboot-mac update /Users/rheza02/Downloads/signed-passion-img-GRI40.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 0.35.0017
Baseband Version.....: 5.08.00.04
Serial Number........: MB038999823
--------------------------------------------
checking mid... OKAY
checking product... OKAY
checking version-bootloader... OKAY
checking version-microp... OKAY
checking version-baseband... OKAY
sending 'boot' (2318 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (2556 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (130284 KB)... OKAY
writing 'system'... OKAY
rebooting...
and this is what happen after rebooting.
http://www.youtube.com/watch?v=n8DiTfYXUy4
anyone think this is hardware issue ?
Have you tried to cool it down? maybe put it on a stone tile for 30 minutes?
My HTC RMA was finished in one day.
Went out Fedex Tuesday overnight to Texas
Fixed Wednesday in Texas.
It's back in my hands Thursday.
No charge.
Hello!
Having a pretty big problem, as I am trying to help my girlfriend get her phone all recovered and usable again for her. On our HTC Ones, we both use Android Revolution HD and were updating to the latest (4.4 version). With my phone, the installation of TWRP 2.6.3.3, then the rom went completely fine.
On her phone, it is going terribly. I made one mistake and forgot to copy the ROM over to the device before I wiped her system, so I don't have the new file to flash. I attempted to flash the old ROM, which was sitting on her device, but it is extremely slow to the point of we waited about an hour or two and it never installed. I have attempted to sideload, but the file is copying much slower than expected. Heck, everything involving the filesystem is running slow, even data wipes! I tried a full system erase, so now I am at a position where we have no flashable ROMS on the device.
I have tried both adb push and adb sideload to send the file, and both never successfully complete, even after waiting hours.
Where do I go from here? Any idea why flashing roms and file system is running so slow?
Change USB port/cable/computer and try push/sideload again
sent from my mobile device
SaHiLzZ said:
Change USB port/cable/computer and try push/sideload again
sent from my mobile device
Click to expand...
Click to collapse
I tried this already. I know this is not the cause as installing a zip of a new rom literally takes about 2 hours to write to the system.
Even a fastboot flash recovery takes about 30 seconds on her device, tested with multiple cables on two macbook pros. My HTC One flashed normally in less than a second...
When I flashed recovery:
MacBookownloads limitin$ fastboot flash recovery recovery.img
sending 'recovery' (9184 KB)...
OKAY [ 1.333s]
writing 'recovery'...
OKAY [ 0.696s]
finished. total time: 2.029s
When I flashed her phone with the same recovery file (TWRP 2.6.3.3):
MacBookownloads limitin$ fastboot flash recovery recovery.img
sending 'recovery' (9948 KB)...
OKAY [ 1.450s]
writing 'recovery'...
OKAY [ 35.708s]
finished. total time: 37.158s
Same phone. Some hboot version. Only thing I had to do to hers first (I had done mine previously) was use revone to s-off her device, which was successful after a few attempts.
Hello,
I can not flash a recovery on my P9 (EVA L09C432B399) to be able to root my P9. It is under 5.0.1 and android 7.
I tried a lot of TWRP.
Thank you for your help
Did you unlock bootloader, before trying to install twrp recovery ?
Yes it's unlock
chuppito said:
Hello,
I can not flash a recovery on my P9 (EVA L09C432B399) to be able to root my P9. It is under 5.0.1 and android 7.
I tried a lot of TWRP.
Thank you for your help
Click to expand...
Click to collapse
It must be TWRP for EMUI 5.01
https://forum.xda-developers.com/p9/development/twrp-t3565703
There is an enhanced version here
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Btw, Fastboot reporting error or what is exactly the problem?
zgfg said:
It must be TWRP for EMUI 5.01
https://forum.xda-developers.com/p9/development/twrp-t3565703
There is an enhanced version here
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Btw, Fastboot reporting error or what is exactly the problem?
Click to expand...
Click to collapse
thank you, the 2 links recovery do not work on my P9.
So I unlocked the bootloader.
I do :
adb reboot bootloader
fastboot flash recovery "the name of recovery.img"
as soon as i get the message okay, i reboot on the recovery and i still have the recovery stock installed.
The message after validating :
target reported max download size of 471859200 bytes
sending 'recovery' (25254 KB)...
OKAY [ 0.823s]
writing 'recovery'...
OKAY [ 0.325s]
finished. total time: 1.152s
chuppito said:
thank you, the 2 links recovery do not work on my P9.
So I unlocked the bootloader.
I do :
adb reboot bootloader
fastboot flash recovery "the name of recovery.img"
as soon as i get the message okay, i reboot on the recovery and i still have the recovery stock installed.
The message after validating :
target reported max download size of 471859200 bytes
sending 'recovery' (25254 KB)...
OKAY [ 0.823s]
writing 'recovery'...
OKAY [ 0.325s]
finished. total time: 1.152s
Click to expand...
Click to collapse
ha you have 1 error when you flash recovery write command fastboot reboot hold vol+ button and push enter when phone reboot unplug usb cable fast before reboot recovery in another time stock recovery back and must flash twrp again good luck
It's good he finally flash the second time the TWRP 3.1.1-1 by oldDroid - extended Version.
Root done thanks a lot for this second link
I booted with volume + so he probably already had a TWRP.
Thank you
Im stuck in fastboot and I keep getting cannot load system image file when trying to flash a fastboot ROM to get back to stock I used patched image
And at first I flashed the stock recover then used wipe everything and now I'm stuck in fastboot when I power on I dont have recovery I only have fastboot and I tried using sakis tool to get back to recovery but it wasn't in the options so I'm stuck in fastboot but I have an option to get indo edl state which works but my phone will not boot into miui no matter what I try and my PC doesn't have drivers for miflash
Thanks.
Use miflash for flashing tgz official rom
---------- Post added at 11:08 AM ---------- Previous post was at 11:08 AM ----------
Miflash install drivers, see in options
Forgot to close this thread found a compatible miflash and fixed
I just made another thread which one worked for you cause I also am stuck in fastboot and the latest compressed file.
fastboot flash recovery C:\Users\sjs\Desktop\twrp-3.3.1-35-cepheus.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.406s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 1.578s
Simply reboots to fastboot ?!
futiless said:
I just made another thread which one worked for you cause I also am stuck in fastboot and the latest compressed file.
fastboot flash recovery C:\Users\sjs\Desktop\twrp-3.3.1-35-cepheus.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.406s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 1.578s
Simply reboots to fastboot ?!
Click to expand...
Click to collapse
When you flash recovery you have to go in recovery
HTCDevil said:
When you flash recovery you have to go in recovery
Click to expand...
Click to collapse
Whut I knew this look up there
futiless said:
I just made another thread which one worked for you cause I also am stuck in fastboot and the latest compressed file.
fastboot flash recovery C:\Users\sjs\Desktop\twrp-3.3.1-35-cepheus.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.406s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 1.578s
Simply reboots to fastboot ?!
Click to expand...
Click to collapse
Send me a link to the thread brother I will help
[email protected] said:
Whut I knew this look up there
Click to expand...
Click to collapse
fastboot boot trwrp.img
HTCDevil said:
fastboot boot trwrp.img
Click to expand...
Click to collapse
No fastboot reboot then press recovery buttons
Hi,
I'm new to installing a custom ROM, so please be gentle.
What I've done so far: Enable developer mode, flashing is unlocked.
When I do fastboot flash recovery TWRP.img I get:
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16356 KB) OKAY [ 0.637s]
Writing 'recovery' (bootloader) Image not signed
or corrupt
OKAY [ 0.145s]
When I then go into Recovery mode I get the "failed to load kernel" message.
I'd be grateful if someone could guide me through the steps to install ArrowOS.
Thanks.
nofishonfriday said:
Hi,
I'm new to installing a custom ROM, so please be gentle.
What I've done so far: Enable developer mode, flashing is unlocked.
When I do fastboot flash recovery TWRP.img I get:
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16356 KB) OKAY [ 0.637s]
Writing 'recovery' (bootloader) Image not signed
or corrupt
OKAY [ 0.145s]
When I then go into Recovery mode I get the "failed to load kernel" message.
I'd be grateful if someone could guide me through the steps to install ArrowOS.
Thanks.
Click to expand...
Click to collapse
Boot into recovery mode and tell me if you have the flashing_unlocked message on the bottom.
Image not signed or corrupt appear when bootloader is locked, maybe it's still locked?
Hi,
thanks for your reply.
I have it solved meanwhile. I started from scratch again, first installing stock ROM following this method, bootloader was still unlocked, then installing TWRP and ArrowOS image again, this time it worked.