Please HELP!
I've the following situation: android isn't booting (stuck on splash-screen). I can't enter to Recovery (also stuck on splash-screen). I have an access only to bootloader and fastboot. I can control fasboot via fastboot utility on my PC (USB connects).
I don't need data on my phone, so my task is simple: restore my device. Any ROMs (even without root), any format etc. are approved.
My phone's info: [HTC Desire S-LCD | Gingerbread 2.3.3 | S-OFF | CyanogenMod 7.0.3 | Radio 32.56.00.32U_5.17.05.08 | HBOOT 6.93.1002 (CM7 r2)]
P.S.: I'm really need help, because I need to go soon.
SOLVED!!!!!
WARNING: all data on your phone will be lost!
You will need stock hboot from alpharev.nl and RUU.zip
Following this:
fastboot erase cache
fastboot flash hboot bravo_aplhaspl.img
fastboot reboot-bootloader
fastboot rebootRUU
fastboot flash zip RUU.zip
fastboot reboot-bootloader
fastboot erase cache
fastboot reboot
Now root the phone, install custom ROMs etc.
That's all!
Related
Dear Member,
I'm new to rooring and flashing custom ROMS...
i have a folio 100 and after a lot of googling and hardwork i finally managed to root my device on windows XP.. then i tried to install Jelly Bean / CM10 (4.1.1) Alpha 2 - 27.09.2012 from http://forum.xda-developers.com/showthread.php?t=1864774 and followed the instructions.
initially when i typed fastboot devices i was getting "? fastboot" and rest of the commands returned 0x2 error.
then i treid
fastboot -i 0x955 erase userdata
fastboot -i 0x955 erase system
fastboot -i 0x955 erase cache
fastboot -i 0x955 erase linux
fastboot -i 0x955 erase recovery
till now everything worked like a charm but when i tried to run the last command
fastboot -i 0x955 flash recovery recovery-cwm-6.0.1.4.img
i'm getting error message "unable to load recoveryxxxx.img"
now i treid to reboot the device and its saying "magic value mismatch" please help me out..
Nonlxpe Menteur
leaderrocks said:
Dear Member,
I'm new to rooring and flashing custom ROMS...
i have a folio 100 and after a lot of googling and hardwork i finally managed to root my device on windows XP.. then i tried to install Jelly Bean / CM10 (4.1.1) Alpha 2 - 27.09.2012 from http://forum.xda-developers.com/showthread.php?t=1864774 and followed the instructions.
initially when i typed fastboot devices i was getting "? fastboot" and rest of the commands returned 0x2 error.
then i treid
fastboot -i 0x955 erase userdata
fastboot -i 0x955 erase system
fastboot -i 0x955 erase cache
fastboot -i 0x955 erase linux
fastboot -i 0x955 erase recovery
till now everything worked like a charm but when i tried to run the last command
fastboot -i 0x955 flash recovery recovery-cwm-6.0.1.4.img
i'm getting error message "unable to load recoveryxxxx.img"
now i treid to reboot the device and its saying "magic value mismatch" please help me out..
Click to expand...
Click to collapse
First, download the latest & most stable ROM (at the moment), including the ROM, GAPPS, recovery-cwm-CM10-A3.img & formatsd.zip
http://forum.xda-developers.com/showthread.php?t=1864774
Actually, you just need to flash the recovery through fastboot, other else can done in the recovery.
1. Copy all the ROM, GAPPS & formatsd.zip into your memory card. Then insert it into your Folio.
2. Run command prompt, make sure your tablet is connected with your PC in fastboot mode.
To erase existing/stock recovery. In command prompt, go into the fastboot program folder and type the following commands
Code:
fastboot erase recovery
3. Copy the CWM Recovery into your fastboot adb folder.
To flash CWM Recovery
Code:
fastboot flash recovery recovery-cwm-CM10-A3.img
fastboot reboot
4. Enter Recovery. Before you begin, wipe everything (except external_sd) in the CWM Recovery, after wiped, you can install the 3 zip files one by one. After finish, just reboot system.
Full procedure also stated in the link I provided, please scroll down.
Hope that helps you.
So did above solution help? I had a similar issue, and I resolved it by just booting the recovery image from fastboot, i.e.
Code:
fastboot boot recovery.img
Once you get into recovery you can flash an image which will in most cases flash a recovery image along with it. If not, you can try to flash the recovery image again once you've done a full wipe from the booted recovery.
Download
Lenovo Yoga Book Android 6.0 ROM: androidfilehost.com/?fid=817550096634799507
Intel Flash Utility: 01.org/android-ia/downloads/intel-platform-flash-tool-lite
Custom Recovery: twrp.me/lenovo/lenovoyt_x703f.html
Magisk Root: magiskmanager.com
Flashing ROM
With the yoga book in recovery, either use the intel utility + json files to flash, or these commands to flash with adb tools with the files from the archive. To unlock bootloader, enable dev mode, then settings>developer>oem unlock.
Fastboot Flashing Commands:
fastboot flashing unlock
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot flashing lock
fastboot continue
Click to expand...
Click to collapse
Set Country Code
how to make Halo Keyboard work. Go into Contacts and create a random one, then type into search ####6020# then set country code. This also fixes the "easyimage-country code" error which causes OTA updates to fail. During your system setup process, if you get constant touchpal errors, go into system settings and disable Touchpal app.
OTA Updates
You should now be able to run thru 5+ OTA updates for a few hours till you're at 7.1. These require a locked boot. If you unlock it, then everytime there's a new update you'll have to unroot and relock.
Root
Download twrp and magisk from the above links
$ fastboot flashing unlock
$ fastboot flash recovery twrp.img
go into advanced sideload
$ adb sideload magisk.zip
To get a full Linux desktop experience with chrome with extensions and dev tools, I recommend the "Linux Deploy" and "Xserver" app to install Ubuntu desktop.
there`s already a thread for this here https://forum.xda-developers.com/yoga-book/how-to/yoga-book-yb1-x90f-android-how-to-flash-t3709930
thread closed
Hello. I wanted to flash a stock ROM on my Xiaomi Mi3 (Not Mi3W) and I downloaded an official stock ROM and flashed it using Fastboot.
Here's where I think I messed up. I used the "fastboot erase userdata" on the phone and when it booted up, The system storage is showing fine when I go to settings > storage but the internal storage is showing up as 0.00b and I cannot install any applications.
I've tried reflashing but nothing is working. Any ideas on how I can get it to work? Thanks.
Try to flash again with fastboot but with following comands:
Enter the following commands below by order:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot-bootloader
boot.img ,recovery.img and system.img it should be inside your stock firmware.
Teddy Lo said:
Try to flash again with fastboot but with following comands:
Enter the following commands below by order:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot-bootloader
boot.img ,recovery.img and system.img it should be inside your stock firmware.
Click to expand...
Click to collapse
After much Googling, I was finally able to 'reset' the whole android partition system by flashing a CWM recovery, booting into it, and using ADB to fix it all.
Thank you for bothering to reply my at all. You're amazing.
You Welcome
After successfully rooting using the recovery method, I figured I'd try re-locking the bootloader on this phone.
I have no idea why it was so difficult, but if you're looking to do the same, here's what you'll need to do:
You can obtain your firmware by using Lenovo assistant. Download speeds are good.
Ok, now I'm going to focus on the part where you've gone back to stock, unrooted of course and just want your bootloader locked, with no N/A at boot or how you're not able to receieve updates because you're such a bad person.
Enable hidden files if not already. You'll find your firmware in C:\ProgramData\LMSA\Download\RomFiles\*your firmware folder* if you used the assistant. Open power shell in your firmware folder obviously.
****MAKE SURE YOU ARE FLASHING THE CORRECT FIRMWARE FILES****
DO NOT DO THIS WHILE ROOTED. MAKE SURE TO BE STOCK... everything... with just the bootloader in the unlocked state.
Of course this will reset the device so don't forget to back up/save any important data
Obviously you'll need to have USB debugging enabled prior to flashing. Let's begin!
1) enter fastboot mode
2) check to make sure things are good (device properly detected and showing serial#) with fastboot devices command
3) Now Type (flash) ONLY these commands (files) and yes you need to do that first part THREE times:
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot oem lock
Then your powershell window should say:
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.099s]
finished. total time: 0.101s
PS C:\ProgramData\LMSA\Download\RomFiles\SURFNA_your device firmware_DEFAULT_regulatory_DEFAULT_CFC.xml>
Your phone is now rebooting
If you are having difficulty locking a different device, then perhaps this may help...
In order to lock your bootloader, you must do it immediately after unlocking it.
Hello - it's been about 10 years since I played with any XDA stuff or custom roms. I have a stock Motorola G Power that bricked itself. It will not boot and recovery mode just gives me "No Command". Only option seems to be factory data reset.
Can anyone suggest a procedure to allow me to either re-install the stock software to get into the phone or recover my data? Sadly I had not backed anything up since last summer.
Should I just try to reflash a stock rom to see if i can get in? Will flashing the rom kill the onboard storage?
Cant find the exact same version either:
SOFIA10/QPMS30.80-63-6-8-5
I found 63-6-8-10 and 63-6-8-3 but not the exact same. Phone is Retail US.
Any help would be appreciated.
Ok found the stock rom that matches 63-6-8-5. Do I just try to flash that back to get back into the phone with my existing data?
Uberhare said:
Ok found the stock rom that matches 63-6-8-5. Do I just try to flash that back to get back into the phone with my existing data?
Click to expand...
Click to collapse
You can try flashing the stock from and just skip the erase userdata step.
The firmware contains a file named flash_file.xml contains the flash commands
You can use Online FlashFile Converter to convert the .XML to simple fastboot commands.
You also should check if getvar is-userspace
Code:
fastboot getvar is-userspace
if yes you need to switch between fastboot and fastbootd
If it's no you don't need to worry about fastbootd
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
You can try flashing the stock from and just skip the erase userdata step.
Click to expand...
Click to collapse
Do I need to unlock the bootloader for flashing an original file?
Uberhare said:
Do I need to unlock the bootloader for flashing an original file?
Click to expand...
Click to collapse
No, you shouldn't need to but it's easier if the bootloader is unlocked.
Unlikely, you can unlock the bootloader now anyways.
Unless you enabled OEM Unlocking in Dev Options already.
If you did enable OEM Unlocking, I would Unlock the bootloader.
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Are the steps any different if the bootloader is locked? You mention it is easier if it is unlocked.
Thank you for the tutorial.
Uberhare said:
Are the steps any different if the bootloader is locked? You mention it is easier if it is unlocked.
Thank you for the tutorial.
Click to expand...
Click to collapse
Easier may not be the right word.
If the bootloader is unlocked, you are less likely to have issues flashing.
ADB devices - does not return any devices, although I can see the phone is connected with the Motorola recovery tool.
fastboot getvar is-userspace returns:
is-userspace: no
Finished. Total time: 0.002s
I found where fastbootd is.
C:\Android>fastboot getvar is-userspace
is-userspace: yes
Finished. Total time: 0.002s
Uberhare said:
ADB devices - does not return any devices, although I can see the phone is connected with the Motorola recovery tool.
Click to expand...
Click to collapse
adb devices will not work if the device is in fastboot mode.
Use fastboot devices when it's in fastboot mode.
sd_shadow said:
adb devices will not work if the device is in fastboot mode.
Use fastboot devices when it's in fastboot mode.
Click to expand...
Click to collapse
adb devices does not show anything in either mode. That is why I looked for fastboot mode. Should I trouble shoot that first?
This is what I want with the erase commands deleted at the end? The erase commands are what will kill my data or is there something else I need to remove?
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
echo Press any key to restart the phone!
pause
fastboot reboot
exit
Looks like phone doesn't respond to commands in fastbootd only normal.
I successfully ran the batch file, but the phone still doesn't boot. What is my next step? (besides throwing it against the wall!)
Phone accepts all the files for the current version of software, as well as commands to clear some of the labels. So the userdata is still there, I just can't get to it. Can you read these with a jtag like the older phones?
What if I try to roll it forward to Android 11 through the stock roms?