Related
hi , i have rooted my n1 and loaded ( recovery-RA-nexus-v1.5.3) into it , but because i had problems with the wifi i decided to flash back the original rom , i did everything as instructed , but when i booted my n1 i get stuck on the boot image with the unlock , can you help me please ?
Can you boot into recovery or fastboot and reflash a known good image (download one and check the md5)? If you can get into recovery then you should be able to reflash without any problems.
Wipe the phone with recovery then try the new rom and radio that got leaked today. I am using it with no issues. In this post there is update.zip that you can flash using recovery if you are having issues with fastboot.
http://forum.xda-developers.com/showthread.php?t=632187
yes i can log to fastboot i will try and let you know what will happen
I had to wipe my SD card after rooting and installing Boot rom.
its not working
hi , i did try to flash Passion_Google_WWE_1.07.1700.1
i keep getting the following
Aegean-iMac:1.1-nexusone-superboot apple$ ./fastboot-mac flash boot PASSIMG_Passion_Google_WWE_107.zip
sending 'boot' (80061 KB)... OKAY
writing 'boot'... FAILED (remote: image error! (BootMagic check fail))
aegean-iMac:1.1-nexusone-superboot apple$
the zip file size is 82 MB on disk (81,983,271 bytes)
and when i try to flash it through the recovery mood i end up with " cant open /sdcard/..... (bad )
i did try to download different roms with the same rustles what im doing wrong ?
ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks
zendick said:
ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks
Click to expand...
Click to collapse
There should be an option on fastboot to go to bootloader and then from there recovery should be available, is that option available to you?
yes but recovery won't boot, sits at mt4g boot screen or sits at 3 skaters in center screen, depending on how I access it (ie go to fastboot then back again)
Power down your phone, hold volume down and the power button. That will take you into the hboot screen. You can then select to go into recovery from there.
thats what I have tried, it goes to three skaters center screen does nothing
I have tried flashing recovery from fastboot
tried hboot from fastboot
tried radio from fastboot
NOTHING flashes trust me I have been androiding for a while now never had I had a problem like this.
zendick said:
thats what I have tried, it goes to three skaters center screen does nothing
Click to expand...
Click to collapse
Is three skaters your boot animation or splash screen? Not sure what that is referring to.
the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens
zendick said:
the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens
Click to expand...
Click to collapse
Oh ok, i know what your talking about now. Your on the bootloader screen under fastboot. And when you select recovery option it does not boot into recovery?
correct and like i said I have tried to reflash everything from fastboot but no go
Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error
got recovery to boot but get
e:can't mount /cache/recovery/command
etc
tried to mount, tried to format
no go
What do you mean tried ruu??
zendick said:
Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error
Click to expand...
Click to collapse
Edit: nvm. Is doing RUU better option than loading PD15IMG.ZIP on sdcard and doing it that way?
Sent from my SGH-T959 using XDA App
tried a pd15 and it doesn't complete, drops a failed message
Sounds like you maybe victim of fail-pu. But if thats not the case and you don't care about your "/data" and just want working phone again then I suggest from fastboot you do "fastboot flash recovery recovery.img" which will replace the current recovery.img and flash it to mmcblk0p21. Once thats done do "fastboot erase system -w" and it will nuke everything so /system, /data, ect will all be erased. After that you can enter recovery by selecting it from hboot and then do factory wipe and flash another rom.
Keep in mind you will run in to errors in recovery after -w as its normal but depending on the fail-pu if you do get the failed partition update flag you can't make any changes as the errors will stick because you can't format the drives. Also the new recovery.img for CWMR can be found in dev section if not post here and ill send you.
I don't care at all about the data (I am well backed up) but I can't flash a recovery I have tried through fastboot, I agree the partition is F_D but I will try the erase system -w and see if that lets me do anything
thanks
uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s
Exactly what I got too, seems we have bricked our phones. Wish I had a way of making the phone unable to boot to recovery or at all.
zendick said:
uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
I dont get how a phone can run for weeks since its last flash and have this happen, I made no changes updates etc just running as normal.
Is there a way to wipe evidence of cm of so I can get this phone repaired? To me this obviously a faulty emmc, I just can't see it being anything else.
or is it possible to boot recovery on sd like the nook?
any ideas on how to wipe cm bits atleast?
My phone is OEM unlocked but not rooted (secure boot - enable as so said in fastboot mode).
Basically my phone cannot get to bootup. It doesn't show "Google" on startup or "X" animation. it crashed yesterday and got stuck on the "X" screen animation. So tried to factory wipe and adb wipe stuff. and things gotten worse. And i need my phone urgently to work because i'm waiting for calls for job interviews. so this is an urgent request!
i tried the LG Google Nexus 4 toolkit to flash Google Stock image but i'm getting the error
"failed <remote: flash write failure>"
i can boot to Custom/Stock Recovery without Permenently Flashing it with Clockworkmod or TWRP.
i tried "update from ADB" option in Android system recovery with "adb sideload image-occam-jdq39.zip" and it's able to send it to the device, but i'm getting "Installation aborted"
I'm out of options and i'm really lost....please help!!
Can you flash a recovery using? :
Code:
fastboot flash recovery name-of-recovery.img
If you can, then download a rom and flash it through the recovery that you installed.
chromium96 said:
Can you flash a recovery using? :
Code:
fastboot flash recovery name-of-recovery.img
If you can, then download a rom and flash it through the recovery that you installed.
Click to expand...
Click to collapse
I'm getting the following error in CMD
sending 'recovery' <6398 KB>...
OKAY [ 0.405s ]
writing 'recovery' ....
FAILED <remote: flash write failure>
i'm trying to relock the device so i can replace it under warranty, but the device won't stay lock....wtf?
So guys basically, I wanted to give F2FS a shot, I downloaded the recoveries that the thread told me to, flashed either of them using the fastboot flash boot filename.img
With both of them, and even the latest official TWRP I get this:
sending 'boot' (8182 KB)... OKAY [ 1.056s]
writing 'boot'... OKAY [ 0.182s]
finished. total time: 1.238s
and on my Bootloader screen I get the message FASTBOOT STATUS OKAY
So, you'd think all went fine.
Rebooting into recovery reveals that I have the exact same recovery as before, I've tried like 10 times and the result is always the same one
Are you sure the one you flashed is different to the previous one? Which recovery do you have now and which do you want to flash?
XxM4tzexX said:
Are you sure the one you flashed is different to the previous one? Which recovery do you have now and which do you want to flash?
Click to expand...
Click to collapse
I have TWRP 2.7.0.1 and I'm trying to flash either KT recovery or the latest TWRP 2.7.1.0, I'll try flashing CWM and then change back to one of those to see if I can manage to do that
fastboot boot filename.img worked and I managed to change my filesystems, I'll try creating the zip as the recovery keeps going reverting and 2.7.0.1 isn't able to read my partitions now, I'll update with the results and so far I just booted up and everything seems to be going well.
Edit: Ok, I DL'ed an official TWRP 2.7.1.0 zip and flashed it, my recovery updated successfully, however it isn't able to read my /cache or /data partitions, next, I replaced the recovery.img with the exact same img I used to convert to F2FS (the one provided here) and again booted into the functional recovery through fastboot boot filename.img, I flashed the new zip file and everything seemed to be fine, rebooting to recovery shows that the original TWRP 2.7.1.0 wasn't replaced as I'm unable to mount the data or cache partitions.
Also worth mentioning that using the TWRP manager from the playstore to try to flash .imgs does not work either
The fastboot method listed above is to flash a kernel not recovery, if your trying to flash a new recovery you run
fastboot flash recovery nameofrecovery.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
Fidelator said:
So guys basically, I wanted to give F2FS a shot, I downloaded the recoveries that the thread told me to, flashed either of them using the fastboot flash boot filename.img
Click to expand...
Click to collapse
fastboot flash recovery filename.img
uDude
Magisk updater installed Magisk & said it needed to make a change to continue the update. I clicked the Reboot button. The phone boots into TWRP. I reboot & it goes into TWRP. Repeat.
How can I recover, preferably w/o losing apps & most preferably w/o losing data like pics?
I'm using Android 9 rooted.
kamiller42 said:
Magisk updater installed Magisk & said it needed to make a change to continue the update. I clicked the Reboot button. The phone boots into TWRP. I reboot & it goes into TWRP. Repeat.
How can I recover, preferably w/o losing apps & most preferably w/o losing data like pics?
I'm using Android 9 rooted.
Click to expand...
Click to collapse
Backup>select data and internal storage>use a computer to move the backup file out
restore then
You can also try magisk uninstaller which comes with magisk on github(seach github magisk the uninstaller is in assets)
jjgvv said:
Backup>select data and internal storage>use a computer to move the backup file out
restore then
You can also try magisk uninstaller which comes with magisk on github(seach github magisk the uninstaller is in assets)
Click to expand...
Click to collapse
Good suggestions. Came back to phone & found battery ran out. Charged up & now it boot loops to fast mode only. Argh!
fastboot flash recovery twrp.img where the recovery image should be renamed 'twrp.img' and placed in the fastboot platform tools folder.
then
fastboot reboot recovery
jjgvv said:
fastboot flash recovery twrp.img where the recovery image should be renamed 'twrp.img' and placed in the fastboot platform tools folder.
then
fastboot reboot recovery
Click to expand...
Click to collapse
Tried 3 different cables including OnePlus. Same result.
fastboot boot twrp-3.3.1-x_blu_spark_v9.101_op6t.img
downloading 'boot.img'...
OKAY [ 0.867s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.876s
kamiller42 said:
Tried 3 different cables including OnePlus. Same result.
fastboot boot twrp-3.3.1-x_blu_spark_v9.101_op6t.img
downloading 'boot.img'...
OKAY [ 0.867s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.876s
Click to expand...
Click to collapse
Sorry. I see your rename note. Same result.
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.840s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.848s
I see the platform-tools note. I'm on Linux & the adb & fastboot tools are in /usr/bin, not a platform-tools folder.
Found one.
/usr/lib/android-sdk/platform-tools$ fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.881s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.889s
hmmmmm
fastboot oem unlock (maybe device relocked when battery rn out)
I was able to get back to TWRP by switching slots. Backup fails because Data is encrypted & TWRP is not prompting for PIN. I'll try using the Magisk uninstaller tomorrow (past bedtime). Long shot.
Open to other approaches. Thanks for your help.
kamiller42 said:
I was able to get back to TWRP by switching slots. Backup fails because Data is encrypted & TWRP is not prompting for PIN. I'll try using the Magisk uninstaller tomorrow (past bedtime). Long shot.
Open to other approaches. Thanks for your help.
Click to expand...
Click to collapse
Facing the same authenticate error when trying to boot into twrp.img. I also don't know how useful twrp will be on the other slot if it can't decrypt the data from there so stuck at this stage too.
@kamiller42 Did you manage to resolve this with the Magisk uninstaller?
spinergist said:
Facing the same authenticate error when trying to boot into twrp.img. I also don't know how useful twrp will be on the other slot if it can't decrypt the data from there so stuck at this stage too.
@kamiller42 Did you manage to resolve this with the Magisk uninstaller?
Click to expand...
Click to collapse
Nope. I tried getting by by flashing just the boot image. It erased data & everything, so I flash Android 10 again & re-rooted.
kamiller42 said:
Nope. I tried getting by by flashing just the boot image. It erased data & everything, so I flash Android 10 again & re-rooted.
Click to expand...
Click to collapse
Did you flash all partitions?
Is there a way to only flash the boot partition, then boot into twrp.img, flash that, then reboot into recovery to decrypt the data? I care more about recovering my encrypted data than getting the phone working.
spinergist said:
Did you flash all partitions?
Is there a way to only flash the boot partition, then boot into twrp.img, flash that, then reboot into recovery to decrypt the data? I care more about recovering my encrypted data than getting the phone working.
Click to expand...
Click to collapse
That's what I thought. All was lost when I flash boot image. Technically, I flashed the fast boot partition from this post. https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-6t.3862516/