Got a one, accidentally wiped data, system and cache.... Had no OS. Tried to RUU.... No go because this phone is 1.31, only have the 1.29 RUU I can find....
Unlocked bootloader again, installed TWRP...
Tried to sideload rom, can't access /data partition.
Can't mount internal memory, listed as 0MB.
tried Fasboot flash of viper rom get, "remote: 24 parsing adroid-info fail."
What do I do next? I have no OS and am still s-on....
I wipe data, system, cache, dalvik cache everytime I flash a rom. Sure you didn't wipe the internal storage?
Hate to say it but perhaps your best bet is to relock the bootloader and bring into sprint for repair. Or you could wait for a newer RUU.
Just curious but did you lock the bootloader before running the RUU?
Ok , got it resolved.
Ended up flashing CWMR via fasboot. Formatted all partitions, reflashed TWRP and ADB Sideload was resurrected.
Thank you Android Gods for giving me the idea.
Thanks for your suggestions, I appreciate it regardless.
Related
This is for my friend's ATT One. Bone stock, unrooted, S-On, no changes made to the device from the store. He took the OTA for Kit Kat and was running fine, then his phone rebooted on him a couple days later and won't go past the white HTC boot screen.
Two problems: First, I cannot use ADB, as it does not detect his phone. When I plug in his phone, it says drivers failed to install for HTC MTP device. I also have an HTC One, unlocked, S-Off, etc., and when I plug mine in, it's detected and ADB works just fine like always (so it's not that I need to reinstall drivers).
Problem 2: the phone seems to hang trying to do a factory reset from the bootloader menu, or from the stock recovery menu. It will start the reset, reboot to the white HTC screen then hang. I left it for more than an hour twice. Nothing doing.
Is there a way to reflash/restore his phone without wiping his sdcard? He's OK losing the data partition, but wiping sdcard is last resort. Using an RUU .exe will wipe his sdcard, as will unlocking his bootloader to try to install a custom recovery. Just not really sure what tools I have at my disposal with a stock recovery and no adb. Will fastboot flashing a rom.zip extracted from the ATT RUU also wipe his sdcard? Or does that only happen with the RUU .exe? Any ideas appreciated..
Shott3r said:
This is for my friend's ATT One. Bone stock, unrooted, S-On, no changes made to the device from the store. He took the OTA for Kit Kat and was running fine, then his phone rebooted on him a couple days later and won't go past the white HTC boot screen.
Click to expand...
Click to collapse
Did you tried wiping /cache?
Shott3r said:
Two problems: First, I cannot use ADB, as it does not detect his phone.
Click to expand...
Click to collapse
ADB can only be used when phone is booted+usb debug on or via custom recovery
Shott3r said:
He's OK losing the data partition
Click to expand...
Click to collapse
I hope so, factory reset is a /data wipe... probably already wiped from your first attempt to factory reset
Shott3r said:
but wiping sdcard is last resort. Using an RUU .exe will wipe his sdcard
Click to expand...
Click to collapse
And the available ruu.exe for at&t is a downgrade in version so it will require s-off.
Shott3r said:
Will fastboot flashing a rom.zip extracted from the ATT RUU also wipe his sdcard? Or does that only happen with the RUU .exe? Any ideas appreciated..
Click to expand...
Click to collapse
you can't flash a rom directly from fastboot. You can flash a rom via a custom recovery or flash a ruu.zip from RUUmode (fastboot oem rebootRUU).
Unfortunately I think there is no way to save /sdcard. You will need to unlock bootloader to flash a custom recovery.
easy way:
flash twrp custom recovery
flash guru reset rom for your version
or
flash twrp custom recovery
flash and use arhd rom
or the long way:
flash twrp
flash arhd
s-off
flash ruu.zip
alray said:
Did you tried wiping /cache?
...
you can't flash a rom directly from fastboot. You can flash a rom via a custom recovery or flash a ruu.zip from RUUmode (fastboot oem rebootRUU).
Unfortunately I think there is no way to save /sdcard. You will need to unlock bootloader to flash a custom recovery.
...
Click to expand...
Click to collapse
I did erase cache first thing. Regarding flashing the ruu.zip from RUUmode, my question is whether flashing the ruu.zip will erase the sdcard? Also does it even matter, since he has KK firmware, and is S-On? Will the ruu.zip from Jellybean 4.3 even flash on his (current) KK firmware?
Any ideas on why the factory reset would hang? Cuz that's best case scenario is to simply factory reset, but it seems not to work presently.
Shott3r said:
I did erase cache first thing. Regarding flashing the ruu.zip from RUUmode, my question is whether flashing the ruu.zip will erase the sdcard? Also does it even matter, since he has KK firmware, and is S-On? Will the ruu.zip from Jellybean 4.3 even flash on his (current) KK firmware?
Any ideas on why the factory reset would hang? Cuz that's best case scenario is to simply factory reset, but it seems not to work presently.
Click to expand...
Click to collapse
ruu will wipe everything.
and no you can't use ruu with s-on because its a downgrade in version.
Is there any way that you know of to get access to the sdcard in the circumstance I've described to try to rescue some files before I set about with the rescue? Doubt it, but just asking.
Shott3r said:
Is there any way that you know of to get access to the sdcard in the circumstance I've described to try to rescue some files before I set about with the rescue? Doubt it, but just asking.
Click to expand...
Click to collapse
maybe you could use remote recovery booting (booting a custom recovery without installing it). Not sure if it still can be done (think it was disabled in 4.2.2)
fastboot boot name_of_recovery.img
then use adb from recovery to copy sdcard content to your computer
adb pull /sdcard C:\somefolder
If you can't boot from a remote recovery, then I think you can say goodbye to those files in your /sdcard
So i've tried to unroot my device and reinstall a stock rom but the device says "process system isnt responding". I have twrp 2.6.3 recovery installed so i've wiped cache, wiped dalvik cache, wiped system, and then installed a stock ruu zip files from htc1guru.com.
Any ideas? The install returns sucessful but still stuck. When i boot into bootloader there is nothing next to "os". Does this suggest that the install infact failed?
The phone is out of warranty so i'm stuck with it.
So here's the situation. I had root, but decided to unroot. So I made a backup with TWRP and copied to my PC, I then proceeded to flash system, cache, data radio, etc from fastboot with the 5.1 factory image, then I re-flashed TWRP and fastboot oem lock . I rebooted, and got a TWRP bootloop, so I did ./fastboot oem erase cache and userdata, reboot and got the four dots endlessly spinning, so I went into TWRP and tried to wipe and get nothing but /data mount errors, then I did a wipe from TWRP and stuidly wiped /system. I can't flash roms, (I tried adb push, installing fails with more mount errors!) and I tried adb sideload the stock ota and that failed with again /data mount errors.
PLEASE HELP! I DON'T NEED A $650 paperweight!
gorei23 said:
So here's the situation. I had root, but decided to unroot. So I made a backup with TWRP and copied to my PC, I then proceeded to flash system, cache, data radio, etc from fastboot with the 5.1 factory image, then I re-flashed TWRP and fastboot oem lock . I rebooted, and got a TWRP bootloop, so I did ./fastboot oem erase cache and userdata, reboot and got the four dots endlessly spinning, so I went into TWRP and tried to wipe and get nothing but /data mount errors, then I did a wipe from TWRP and stuidly wiped /system. I can't flash roms, (I tried adb push, installing fails with more mount errors!) and I tried adb sideload the stock ota and that failed with again /data mount errors.
PLEASE HELP! I DON'T NEED A $650 paperweight!
Click to expand...
Click to collapse
Does anyone know how to enable fastboot oem unlock from TWRP?
Hi,
I've just had my Nexus 6 for a few days, and am using Nexus Root Toolkit v2.0.4. -- it works really well.
There's an option "Flash Stock + Unroot" with "Current status : Soft-bricked/Bootloop"
Anyway, did you try to use Nexus Root Toolkit?
3f62011 said:
Hi,
I've just had my Nexus 6 for a few days, and am using Nexus Root Toolkit v2.0.4. -- it works really well.
There's an option "Flash Stock + Unroot" with "Current status : Soft-bricked/Bootloop"
Anyway, did you try to use Nexus Root Toolkit?
Click to expand...
Click to collapse
Unfortunately, I'm on a Mac. Wine didn't work, either.
ANY HELP APPRECIATED! PLEASE!
Update:
Fixed it!
Did fastboot format cache/userdata
Then TWRP could mount data and then I ADB pushed Chroma and it booted. I was able to allow OEM unlocking from there.
Hello all!
I am having an issue with my Leeco Le2 x52x where it relocks bootloader automaticly and does not alow me to flash any other rom properly.
I have used fastboot oem unlock-go which allows me to flash twrp but not much else. Can not even format boot partition.
Anyone has any peace of info is greatly apriciated
Edit> I get an error in TWRP - E:Unable to wipe '/boot' -- uknown file system 'emmc
Unable to wipe /boot.
scudteshka said:
Hello all!
I am having an issue with my Leeco Le2 x52x where it relocks bootloader automaticly and does not alow me to flash any other rom properly.
I have used fastboot oem unlock-go which allows me to flash twrp but not much else. Can not even format boot partition.
Anyone has any peace of info is greatly apriciated
Edit> I get an error in TWRP - E:Unable to wipe '/boot' -- uknown file system 'emmc
Unable to wipe /boot.
Click to expand...
Click to collapse
Boot partition in le2 cannot be wiped. As for your bootloader relocking problem, flash twrp and then allow it to perform system modifications. Then wipe data. Then wipe system. If that doesn't work, then format data to ext2 using mkef2s and then for mat data again using ext4. Then format data ,system , cache and dalvik cache only. Your bootloader will not relock by itself again. If it still does, then flash lazyflasher to disable dm-verity and unencrypt phone
RandomDelta said:
Boot partition in le2 cannot be wiped. As for your bootloader relocking problem, flash twrp and then allow it to perform system modifications. Then wipe data. Then wipe system. If that doesn't work, then format data to ext2 using mkef2s and then for mat data again using ext4. Then format data ,system , cache and dalvik cache only. Your bootloader will not relock by itself again. If it still does, then flash lazyflasher to disable dm-verity and unencrypt phone
Click to expand...
Click to collapse
Tried it and no budge. Now i am at different problem cause i wanted to return it to stock with "flash all" fastboot rom. Not this thing does random reboots. Not sure if i should open another tread about it. All in all its still usefull phone and i would like to fix it eather way
scudteshka said:
Tried it and no budge. Now i am at different problem cause i wanted to return it to stock with "flash all" fastboot rom. Not this thing does random reboots. Not sure if i should open another tread about it. All in all its still usefull phone and i would like to fix it eather way
Click to expand...
Click to collapse
Are you able to boot to recovery(twrp)?
If yes, try flashing the latest twrp image using twrp on your phone. Then repeat steps mentioned. Finally, flash stock ROM Zip
Ive bricked the bastard but will continue
Is the red LED flashing or stuck when you let it charge?
Hello guys
I tried to flash my K20 Pro today with a custom ROM and somehow ended up with a bootloop (I wiped everything pretty much, Data, Vendor (which was probably the mistake, dunno), System, caches, all that). So, I went ahead and flashed the stock ROM through the MiFlash tool, and I can use the stock ROM. After that, I flash TWRP and repeat the process. Wipe, flash, reboot. And I get the bootloop.
Bootloader is unlocked as should be.
Anyone know what's causing this and what I can do to fix it?
Thanks in advance
EDIT: Just noticed that after this last attempt where it bootlooped into the recovery, everything's encrypted, don't know if that helps but it's there.
Format data
camp70 said:
Format data
Click to expand...
Click to collapse
Had it running on the fastboot MIUI ROM, flashed TWRP, wiped caches, system and data. Then data again. Storage shows up in 3 "partitions" and I can't paste files to them. When I try to reboot back to TWRP it just goes to fastboot and after reflashing TWRP, it still will boot to fastboot instead of the just flashed recovery. Using fastboot oem reboot-recovery if that helps.
After the wipe, doing fastboot boot twrp.img will fire up a "Failed to load/authenticate boot image: Load Error"
Format is not the same that wipe
From MIUI
Install TWRP.
Boot TWRP.
Go to wipe menu and factory reset.
Return to wipe menu and select format data.
At no point do you need to go into the advanced wipe menu.
Return to the main menu.
Go to boot menu.
Select (re)boot recovery to allow TWRP to correctly mount the newly formatted data partition.
Copy across the files you want to flash, then flash them.