i am trying to upgrade from ginger bread to jellybean
jelly bean needs a 250mb internal memory for the system so what i did is partition my internal memory using blackrose i did partition it and wipe all the data except the SD after that i notice that the OS is gone so i search for a solution and found this one http://forum.xda-developers.com/wiki/HTC_Nexus_One/Recovery_Images but when i try to command adb devices in cmd ,it didnt displays my device serial or something and if i command adb shell it says error device not found,so i look for another solution,i found solution on fastboot mode,
screenshot of my device when i select bootloader
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i tried
fastboot device
fastboot oem unlock but error occured again it says command error
i tried another
like booting or flashing boot.img and recovery.img
but it both says cannot open boot.img or recovery.img
i think i got my device bricked,anyone can help me please? i cant use my phone now :crying:
If you have blackrose than you have s-off/unlocked bootloader
So you now need to flash a recovery via fastboot and then boot to the new recovery and then flash ROM of choice, do not flash any stock firmware (may have a radio in it which could result in a brick)
http://forum.xda-developers.com/showthread.php?t=2277112
Here are some tips on how to use fastboot properly, if you get stuck and need further help be sure to copy and paste all input/output from cmd/terminal here
Best of luck
Sent from my Nexus 7 using Tapatalk 2
i got this error when trying to unlock bootloader
<bootloader> [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.16s
Click to expand...
Click to collapse
Again, you have black rose, you do not need to run unlocked command - you have s-off
What you need to do is flash a recovery through fastboot and then boot to new recovery and then flash ROM of choice
Do not run fastboot oem unlock - this will do nothing for you
Do not flash factory firmware with out being sure what you are flashing or this can result in a brick, just flash recovery then ROM
Sent from my Nexus 7 using Tapatalk 2
ok thanks got it fix
Related
Windows users should already have :
<<adb drivers>>
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
<<usb drivers>>
------------------------------------------------------------------------------------------------------------------------------------------------------
so u did root. u unlocked bootloader. u flashed a recovery and u installed a new rom. one day u start "digging" things to see if u can delete all the unwanted files so u make the phone faster and accidentally u deleted an important file and now it cant boot and it cant go into recovery. you are wondering what you CAN do now ! The answer is : Everything !
You can either go back to stock rom or
you can re-flash the recovery and then reinstall the rom.
1. Download the platform tools for your machine ( windows , linux or mac-os ). Here i have the adb fastboot for you.
2. Copy the recovery image to a location on your computer thats easier for you. The recovery image should have .img extension. If it is in a zip file, extract the .img file from it before proceeding.
3. Connect the phone to the pc and open cmd inside the fastboot folder you downloaded ( windows ). The others not on windows must use cd [path to their desktop,inside the platform tools where they see the adb file].
** If you are on a boot loop but the pc gets to recognize the phone even for a second then
4. Type
i) adb reboot-bootloader
ii) fastboot flash recovery recovery.img ( the command is: fastboot flash recovery [recovery image path/filename] )
5. When its done , reboot. Hold Volume down and power button to see if u get in recovery mode. :highfive:
Install the rom now the way you already know. There are many guides for that so i won't make a new.
cheers :good:
**Windows users can use this fastboot to unlock bootloader too. Lite fastboot commands guide provided here
**Linux users don't even need to download it , they can just directly download it from their terminal
I hope this thread helps a little those that dont know what to do when they delete an important file. *Pictures coming soon*
Hello community I need your help!
I was running CM 12.1 on my tablet and I wanted to make a factory reset, well... I did and because the tablet has to restart, it did and since then I got stuck on the TeamWin logo page
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And I cannot go to the option, it just stays there
This are some of the output I get from ADB
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
0123456789ABCDEF recovery
And if I uses "adb reboot fastboot" it does, but then the output of "adb devices" and "fastboot devices" is null
I have tried a lot commands, but I always get the same results <waiting for device>
My drivers are working.
I already unplug/plug/restart the table but the <waiting for device> is still there
I still tried with this tool http://forum.xda-developers.com/showthread.php?t=1951254 but it doesnt work, event trying a fastboot command manually doesn't work.
Any ideas!! please help!
DarkWolfSLV
I have the exact same problem i have been trying all day to find a fix but no luck D;
Fixed it DUDE I Kinda Found A Fix i can know access TWRP DDD
1. Download This https://docs.google.com/uc?id=0B4lZE...xport=download
2.connect kindle to pc and boot up the kindle normally
3.extract the Zip and open tha bat file
4. select option 4 It should then say waiting for device
5.open up cmd adb and type adb reboot-bootloader then it should say clearing cashe or user data then after about a min power off ur device then power it back on
6.then it should now say clearing cashe or user data On of them then after a min switch of ur device then back on and team win should load the next problem is that i cant send files through to my kindle so i cant flash anything. maybe i need newdrivers cna someone link me to one.
Edit; reboot The device again and it should boot into cm12 but once again im stuck in a boot loop and unsure of what to do the boot loop is just the cm12 logo it does not go onto the actual os
nvm lol wait about 5 mins it should boot.
I will try to describe exactly what I did. I warn you that if you want to repeat this, then do everything at your own risk!
Original message
1. The cleanest installation possible
We do a COMPLETE cleanup and format the DATA in TWRP not lower than version 3.4... then reboot into bootloader and connect to the PC with a good cable. Run Fastboot on the PC in the command line in turn enter the following commands:
fastboot devices
fastboot erase all
fastboot reboot bootloader
2. Install motoXT1799-2_GLOBAL_2021.02.20_oreo.zip
Use the firmware from here: motoXT1799-2_GLOBAL_2021.02.20_oreo
3. Install Magisk
The latest version of Magic-v22.0.apk must be installed and Magisk-v22.0.zip
4. Go to the developer menu
In the developer menu, we give permissions to unlock the OS bootloader, as well as give permission to debug via USB.
5. Run adb Fastboot on the command line
The phone must be connected to the PC via USB. We enter the command adb devices on the smartphone, a dialog box should appear to allow debugging this device or something like that, respectively, we give permission.
Next, we reboot into the bootloader with the command adb reboot bootloader
6. Blocking
Previously, we copy the stock recovery.img to the folder with adb Fastboot
Enter the commands:
fastboot flash recovery recovery.img
fastbo fastboot flashing lock
We reboot into the system.
7. Delete Magisk as unnecessary
To do this, go to the program select delete see two items select first "restore partitions or something like that" then delete.
8. Do a factory reset
If everything is done correctly, we get a device with Oreo Android 8.1.0 as if it came out of the factory.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've followed the process outlined here. After installing the ZIP, it rebooted, but went back to recovery. When I said reboot system, it said No OS installed.
So, I tried to start over by formatting data and then copying the zip again via ADB Push. Then the trouble starts. After adb push, which takes about 5 minutes, it says
Code:
failed to copy 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip' to '/sdcard/xiaomi.eu.zip': write failed: No space left on device
After that, the data partition seems corrupted. Whenever I go to Install, it shows 0 bytes. Upon Googling I found a solution by formatting to ext2 and back to ext4. Then, it shows again as 100000MB. However, adb push every time fails with same problem.
For some weird reason, I can push to /data. But still running into same problem after installing ROM and rebooting, it goes back into recovery.
I also tried to sideload, but then I run into this issue:
Code:
D:\Tools\ROMs>adb sideload xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip
loading: 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip'
* cannot read 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip' *
So, I'm stuck with a device without any ROM. Any suggestions please?
Did you ask in the MIUI EU forums as well? Since there would be more ppl familiar with these issues than here.
I'm also interested in this since I prefer EU roms. Also you need a specific TWRP version which I believe is still in alpha stage for the 10 Pro since its still a new device. There should be a TWRP thread somewhere here where you can also ask.
I just got my 10 pro and need to wait a few more days to unlock BL, then I will be flashing an EU rom, hence my interest. Hope you find a solution.
Use TWRP from here:
https://forum.xda-developers.com/t/4248449/
fastboot reboot bootloader
fastboot boot TWRP_file_name.img
Format Data, type yes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reboot to recovery.
The internal storage should be visible.
Connect phone to PC and put ROM into phone.
Flash ROM, format data, yes
Reboot to system.
If above not work, make your phone under fastboot mode, Mi-Flash, and flash your stock fastboot MIUI. Don't lock your bootloader.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I previously successfully installed and ran lingeageOS for a long time. In attempting to flash stock android, I'm getting a part-way successfully then failing to a screen titled 'fastbootd' when the flash script attempts to enter userspace fastboot. I'm running Arch Linux and have android tools installed locally as well with the android-tools package. I can start the device into fastboot mode and see it on my PC with `fastboot devices`:
$ fastboot devices
13091FDD4000GY fastboot
I would prefer to install android 11, but I've also tried android 12 with the same end failure result.
How can I troubleshoot this further? Any help is much appreciated!
brian_says_yas said:
View attachment 5517961
I previously successfully installed and ran lingeageOS for a long time. In attempting to flash stock android, I'm getting a part-way successfully then failing to a screen titled 'fastbootd' when the flash script attempts to enter userspace fastboot. I'm running Arch Linux and have android tools installed locally as well with the android-tools package. I can start the device into fastboot mode and see it on my PC with `fastboot devices`:
$ fastboot devices
13091FDD4000GY fastboot
I would prefer to install android 11, but I've also tried android 12 with the same end failure result.
How can I troubleshoot this further? Any help is much appreciated!
Click to expand...
Click to collapse
Hi Brian, have you tried a different usb cable? I only use windows so I can help more if you get a windows PC or run windows from a usb. I also unlock the bootloader manually with the ADB tools, first before using the flash tool.
So I switched to a macbook and a different USB cable both at the same time, and it worked. I'm speechless lol. Thank you for your help! Honestly the biggest benefit here is that I don't have to use Android 12 yet which was buggy as hell on my Pixel 6 Pro before someone did me the favor of stealing it in Miami.