[Q&A] USB soft brick + how i fixed it. - Legend Q&A, Help & Troubleshooting

I'm Working on a HTC Legend for a friend.
And after Rooting and Installing a Custom rom, I sudenly could not access the sdcard annymore. So I revert ( STUPID ) to 1.31 rom.
And start over. But I could not get the USB port to work anny more. Getting errors like: error: device not found ,with adb commands. and in windows Unknown Device ( error 43 ) no driver helped.
sollution:
Source: http://android.modaco.com/topic/309961-usb-brickrickrolledb0rked-fixed/
...
Also, SD card functionality has to work. For this, do 'fastboot oem enableqxdm 0' in fastboot mode.
Steps involved:
1. Find out your CID. Go into fastboot mode, and do 'fastboot oem boot'.
The log will say something like the following:
Code:
#INFOTAG:Ramdisk OK
#INFOTAG:smi ok, size = 0
#INFOTAG:hwid 0x0
#INFOTAG:skuid 0x21F04
#INFOTAG:hero panel = 0x0
#INFOTAG:engineerid = 0x0
#INFOMCP dual-die
#INFOMCP dual-die
#INFOTAG:mono-die = 0x0
#INFODevice CID is not super CID
#INFOCID is HTC__E11
In this specific case, the CID is HTC__E11.
2. Get the following mtd0.img from here or from here: mirror provided by SgtDavePwnage.
Edit this image to the CID you found above with a hex editor.
3. Get flash_image from here or from here: mirror provided by SgtDavePwnage.
Move this to /data/ , and flash the modified image using:
"/data/flash_image misc /data/mtd0.img"
You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator:
'cat /sdcard/flash_image > /data/flash_image'
'cat /sdcard/mtd0.img > /data/mtd0.img'
You might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image)
4. Repeat step 3 a couple of times if it doesn't seem to work well.
5. All done! Reboot, you should have normal usb connectivity. Post your 'fastboot oem boot' log and intermediate steps if it fails.
...
Click to expand...
Click to collapse
After that I followed the r4-legend-root Step 1 and skipped step two by placing Clockworkmod as update.zip on the SD.
Recovery Vol up + power. And I was back in the game. { I lost that other game while typing this }
It took me a while to learn all this. In 24 Hours 5 hours of actual work and even more frustration. But I'm There.
I hope this helps you as it did me.
Right now I'm fiddeling with customisations to
[ROM][RC1][17.07.2011] Gingerbread 2.3.3 with HTC Sense 2.1
Getting all his apps in the Rom, saves space in data.

Related

[DEV] hboot & radio disassembly

Hi,
Does anyone know at what address the radio image should be loaded for disassembly, and what is its entrypoint ?
For reference the hboot image has to be loaded at 0x8e000000, and its entrypoint is at 0x8e001000.
For info, the available oem task commands are:
- 28: format userdata
- 29: format system, cache, userdata (will only format system if security is off)
and the available oem rtask commands are:
- 0: ???
- 7: switch to radio bootloader OR at command prompt *
- 8: switch to radio bootloader OR at command prompt *
- 9: ???
* I'm not sure which of 7 or 8 is the radio bootloader and which is the AT command prompt, as from the SPL point of view, they behave the same (read line, push to radio, print response, and exit when "retuoR" is typed).
Also, the Nexus One and Desire hboot images are nearly exactly identical and those commands exist identically in both hboots
Also, the hboot itself issues AT commands to talk to the radio chip, among others, these are present in the hboot binary:
[email protected]=1,%x,%s
[email protected]=2,1,%s
[email protected]?%x
[email protected]=3,%x
[email protected]=7,%d <- this is a good candidate for the mighty security=off quest
[email protected]?AA <- most likely "get security status"
[email protected]=9,%x
[email protected]?40
According to what people have found on other devices, all the other [email protected] commands are related to actual simlock/unlock
Hi, I am very interested in your findings, also myself and Paul from modaco have been playing around with some commands. Did you continue to look into this yourself or not?
Regards
found this myself hexing both the holiday hboot image and the one in the passimg.zip file..
they do have different lines
All we need is an engineers ID over at HTC apparently and input it right after fastboot oem task (id here) and it will request a reason for the security removal...

possible solutions ATRIX error " SVF:105:1:2 "

well tell them that after so much screaming in my room solution for not having the death of my Atrix trying and trying to achieve sarbarlo of the error that I did it "SVF: 105:1:2" clear case of the same mistake that I had: good point we were :::::::::::>
If you let down the volume down button and you get the error on and off the screen:
What I did was just turn on the normal cell and I present some options, with some numbers from 1 to 14 possibly ....
After my cable is connected to the computer normally and opened a command window in windows .....
from there run the following steps:
Remember that you must have a folder with the files: fastboot.exe, adbwinapi and also adbwinusbapi.dll Or search your folder androidsdk, tools
1: Open the command window.
2: Located in the folder where the files are.
3: Run fastboot oem unlock.
4: run fastboot oem unlock # # # # # # # number of device given by the previous command.
5: Wait for the screen says unlocked cell in the upper left.
6: After a long time if not restart remove the battery, reassemble, turn on the cell normally and wait for restart.
NOTE: This will erase everything I had in into your system android and may not work for everyone so that no bad comments beyond that is a false thanks for your attention
Excuse me for my English use google translator
And excuse me if I give false hope that they might not work at all

[Script] Automated Unlock/SuperCID/Temp-Root scripts for Windows and Linux

Obligatory reading before you begin: So You Want to Root and Mod Your HTC Phone
Introduction
Credit goes to Bin4ry for developing the loop-restore trick that applies to many phones, and of course CaptainRewind and jose51197 for being the first to demonstrate its applicability to the HTC Droid Incredible 4G LTE. Since that time, I have put quite a bit of work into writing these automated scripts. I am splitting them out of the original thread so that I can give them a proper home and continue to maintain them. With the start of this thread, I'm also introducing a Linux variant of the script.
{
"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"
}
Usage - typical procedures
All of the below procedures assume you're still using a phone with a locked bootloader and S-ON.
Prerequisites:
Windows users: uninstall any HTC software you currently have installed (e.g. HTC Sync) and install the HTC drivers from this post. Only unlimited.io's S-OFF requires a certain driver version. Other procedures can use the latest version.
All users: Only use a USB 2.0 port on your computer. Do not use a USB 3.0 port. When you connect your phone to the USB cable, ensure it is in Charge Only mode.
HTCDev Unlock: unlock the bootloader, install a custom recovery, and install superuser (for root access):
Flash RUU 2.17.605.2 or run factory reset if you are already on this software version.
... then set these options:
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 1 of the script to unlock the bootloader
... then set these options (yes, again):
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 5 of the script to install either TWRP or CWM recovery
Occasionally, this step needs to be run twice in order for the recovery to boot. It's a quirk of the phone.
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
If you opt for Superuser, you want Superuser-3.1.3-arm-signed.zip
Use task 3 of the script to revert the CID to stock (this will not affect unlock)
Unlimited.io S-OFF (DirtyRacun):
Follow the instructions for DirtyRacun: Fireball at unlimited.io very carefully
When you get to Temproot your phone via any method available, use task 6 of the script to put your phone in temp-root mode.
Continue the instructions for DirtyRacun
Facepalm S-OFF:
Flash RUU 2.17.605.2 or run factory reset if you are already on this software version.
... then set these options:
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 1 of the script to unlock the bootloader
... then set these options (yes, again):
Settings > Developer options > USB debugging = True
Settings > Power > Fast boot = False
Use task 5 of the script to install either TWRP or CWM recovery
Occasionally, this step needs to be run twice in order for the recovery to boot. It's a quirk of the phone.
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
If you opt for Superuser, you want Superuser-3.1.3-arm-signed.zip
Follow the directions for Facepalm S-OFF
Use task 3 of the script to revert the CID to stock (this will not affect unlock or S-OFF)
Flash the DirtyRacun HBOOT from unlimited.io - follow the instructions on the right sidebar
Notice: Windows users can run these commands by removing sudo ./ from each line.
Cautionary Notes about OTAs
When (if) fireball gets an official jellybean release from HTC/Verizon:
It is crucial that users have their CID as VZW__001 (and not SuperCID). It seems OTAs (over-the-air updates) for other HTC devices have caused bricks for users who are S-ON and SuperCID. I strongly recommend users revert their CID after unlocking or doing facepalm S-OFF.
New touch firmware may cause compatibility issues when switching between ROMs. If possible, delay updating while devs work on testing ROMs with the new firmware.
With this said, I really have NO clue whether we will ever get an official jellybean release.
Linux script notes
The linux script will only execute properly in a bash terminal!
After extracting, make runme.sh executable:
Code:
chmod +x runme.sh
Then, run the script:
Code:
./runme.sh
Manual procedures for reference
Windows
Before you begin
Uninstall HTC Sync and any other applications/drivers that come up with a search for "htc" in the uninstall programs list in Windows. Download and install the latest HTC Drivers from this post.
Only use a USB 2.0 port on your computer. Do not use a USB 3.0 port. When you connect your phone to the USB cable, ensure it is in Charge Only mode.
Verify your phone is on the correct software version: Settings > About > Software information: Software number = 2.17.605.2 710RD
If you need to update your phone (from 4.0.3) the RUU is here.
Factory reset your phone: Settings > Storage > Factory data reset
Turn off Fast boot: Settings > Power > Fast boot = Off
Turn on USB debugging: Settings > Developer options > USB debugging = On
Part 1: Obtain temp-root
Open a command prompt in the directory where you extracted Inc4GUnlockV6-Windows.zip. Ensure USB debugging is enabled on your device and verify the connection with:
Code:
adb devices
You should see something like:
List of devices attached
HTXXXXXXXXXX device
Click to expand...
Click to collapse
Start the restore process with
Code:
adb restore fakebackup.ab
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
The command prompt will appear to be hung. At this point you can accept the restore prompt on your phone. When the command prompt returns, type:
Code:
adb reboot
Wait at least 60 seconds (seriously, time it) and you phone should be in temp-root mode. There will be only a status bar on the phone, but no unlock-ring.
Part 2: Apply SuperCID
Apply the SuperCID modification:
Code:
adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/cid"
adb pull /sdcard/cid
copy cid mmcblk0p4.original
hexalter cid 0x214=0x31,0x31,0x31,0x31,0x31,0x31,0x31,0x31
adb push cid /sdcard/
adb shell "dd if=/sdcard/cid of=/dev/block/mmcblk0p4"
adb shell "rm /data/local.prop /sdcard/cid"
del cid
If all went well, reboot your phone to the bootloader and check your cid:
Code:
adb reboot-bootloader
fastboot oem readcid
Verify that your cid is 11111111.
Part 3: Unlock the bootloader
You can now proceed to unlock your bootloader. Start by retrieving your unlock token:
Code:
fastboot oem get_identifier_token
Sign up for an account using a valid e-mail address at htcdev.com. After you have logged in, jump to page 3. Submit your device token. When you receive Unlock_code.bin in your e-mail (check your junk mail folder!), copy it to the directory where you extracted Inc4GUnlockV6-Windows.zip, then type:
Code:
fastboot flash unlocktoken Unlock_code.bin
Follow the on-screen instructions to unlock your bootloader.
Part 4: Flash a custom recovery
Download your preferred recovery, TWRP or CWM, and flash it through fastboot (phone is at the bootloader) using:
Code:
fastboot flash recovery recovery_file_name.img
fastboot reboot-bootloader
If this is the first time flashing a custom recovery, you may have to perform this step twice. It's a quirk of the phone.
Part 5: Root the phone
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
Part 6: Revert your CID to stock
You may want to revert your cid to stock after installing a new ROM. Keeping SuperCID can cause issues with making/receiving phone calls in stock-based ROMs. Make sure you have Superuser installed. Then, with the phone fully booted up, type:
Code:
adb shell "su -c 'dd if=/dev/block/mmcblk0p4 of=/sdcard/cid'"
adb pull /sdcard/cid
hexalter cid 0x214=0x56,0x5A,0x57,0x5F,0x5F,0x30,0x30,0x31
adb push cid /sdcard/
adb shell "su -c 'dd if=/sdcard/cid of=/dev/block/mmcblk0p4'"
adb shell "rm /sdcard/cid"
del cid
Linux
Before you begin
Only use a USB 2.0 port on your computer. Do not use a USB 3.0 port. When you connect your phone to the USB cable, ensure it is in Charge Only mode.
Verify your phone is on the correct software version: Settings > About > Software information: Software number = 2.17.605.2 710RD
If you need to update your phone (from 4.0.3) the RUU is here.
Factory reset your phone: Settings > Storage > Factory data reset
Turn off Fast boot: Settings > Power > Fast boot = Off
Turn on USB debugging: Settings > Developer options > USB debugging = On
Part 1: Obtain temp-root
Open a terminal in the directory where you extracted Inc4GUnlockV6-Linux.zip. Ensure USB debugging is enabled on your device and verify the connection with:
Code:
./adb devices
You should see something like:
List of devices attached
HTXXXXXXXXXX device
Click to expand...
Click to collapse
Start the restore process with
Code:
./adb restore fakebackup.ab
./adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > /dev/null
The terminal will appear to be hung. At this point you can accept the restore prompt on your phone. When the terminal prompt returns, type:
Code:
./adb reboot
Wait at least 60 seconds (seriously, time it) and you phone should be in temp-root mode. There will be only a status bar on the phone, but no unlock-ring.
Part 2: Apply SuperCID
Apply the SuperCID modification:
Code:
./adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/cid"
./adb pull /sdcard/cid
cp cid mmcblk0p4.original
printf '\x31\x31\x31\x31\x31\x31\x31\x31' | dd of=cid bs=1 seek=532 conv=notrunc
./adb push cid /sdcard/
./adb shell "dd if=/sdcard/cid of=/dev/block/mmcblk0p4"
./adb shell "rm /data/local.prop /sdcard/cid"
rm cid
If all went well, reboot your phone to the bootloader and check your cid:
Code:
./adb reboot-bootloader
./fastboot oem readcid
Verify that your cid is 11111111.
Part 3: Unlock the bootloader
You can now proceed to unlock your bootloader. Start by retrieving your unlock token:
Code:
./fastboot oem get_identifier_token
Sign up for an account using a valid e-mail address at htcdev.com. After you have logged in, jump to page 3. Submit your device token. When you receive Unlock_code.bin in your e-mail (check your junk mail folder!), copy it to the directory where you extracted Inc4GUnlockV6-Linux.zip, then type:
Code:
./fastboot flash unlocktoken Unlock_code.bin
Follow the on-screen instructions to unlock your bootloader.
Part 4: Flash a custom recovery
Download your preferred recovery, TWRP or CWM, and flash it through fastboot (phone is at the bootloader) using:
Code:
./fastboot flash recovery recovery_file_name.img
./fastboot reboot-bootloader
If this is the first time flashing a custom recovery, you may have to perform this step twice. It's a quirk of the phone.
Part 5: Root the phone
Flash a super-user app with the su binary through recovery: Superuser, SuperSU, or ClockworkMod Superuser
Part 6: Revert your CID to stock
You may want to revert your cid to stock after installing a new ROM. Keeping SuperCID can cause issues with making/receiving phone calls in stock-based ROMs. Make sure you have Superuser installed. Then, with the phone fully booted up, type:
Code:
./adb shell "su -c 'dd if=/dev/block/mmcblk0p4 of=/sdcard/cid'"
./adb pull /sdcard/cid
printf '\x56\x5A\x57\x5F\x5F\x30\x30\x31' | dd of=cid bs=1 seek=532 conv=notrunc
./adb push cid /sdcard/
./adb shell "su -c 'dd if=/sdcard/cid of=/dev/block/mmcblk0p4'"
./adb shell "rm /sdcard/cid"
rm cid
Changelog
Version 6.2
Linux: Fix incorrect use of grep when busybox is not available; update adb and fastboot executables
Version 6.1
Windows: (Hopefully) fixed hanging procedures due to std redirects
Linux: Allow more diverse device codes returned by adb devices
Version 6.0 - Initial Release (in this thread)
Great tool, wish I had this when I was did mine I wasted valuable angry birds time
Sent from my ADR6300 using xda app-developers app
I assume that is only available in linux not a windows version. Anything automated with this process for s-off would be so great. old laptops, new phones and dumbass users like me isn't really a great mix lol
kramer56 said:
I assume that is only available in linux not a windows version. Anything automated with this process for s-off would be so great. old laptops, new phones and dumbass users like me isn't really a great mix lol
Click to expand...
Click to collapse
I literally just put my palm to my face. You need to re-consider whether leaving your stock ROM is a good idea.
This post is relevant.
deserved. the original inc was just so easy i guess. this seems so much more involved with the windows os
I always flash roms with the og
mdmower said:
I literally just put my palm to my face.
Click to expand...
Click to collapse
I see why the new method is called Facepalm S-OFF now.
Well when i get to here adb restore fakebackup.ab
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; it asks on the phone for a encryption password and the cmd.exe says link not found and just keeps running that for 3 minutes then I exited out
maybe I am not extracting to the proper place, that is unclear to me, sorry
When i run the script it doesn't find my device, asks if i see it listed above as "HTXXXXXXX" but all i can see is
emulator-5554 device
FA29TS301243 device
i have the phone connected as charge only, debugging enabled and fast boot dissabled. running latest android 4.0.4, sense 4.1 official update and yes i have latest htc drivers installed and when i plugged the phone it gets recognized just fine.
what could i be doing wrong? win 7 64 bits by the way.
sidgallup said:
When i run the script it doesn't find my device, asks if i see it listed above as "HTXXXXXXX" but all i can see is
emulator-5554 device
FA29TS301243 device
i have the phone connected as charge only, debugging enabled and fast boot dissabled. running latest android 4.0.4, sense 4.1 official update and yes i have latest htc drivers installed and when i plugged the phone it gets recognized just fine.
what could i be doing wrong? win 7 64 bits by the way.
Click to expand...
Click to collapse
I have not seen a fireball with an FAXXXXXXXXX device code. Are you positive you have the Incredible 4G LTE (and not the Desire 4G LTE or Incredible 2, or Incredible S, or something else)?
It looks like you have two devices plugged in. If so, unplug the other device.
If you have HTC Sync or any other HTC software installed, remove it all and re-install just the driver.
Well in about>phone identity it says model number ADR6410LVW and i'm pretty sure it is in fact a 4g LTE, it says so on the back cover.
Also i've downloaded the 4.0.1.002 drivers from that post in the first place, just got the phone 2 days ago.
sidgallup said:
Well in about>phone identity it says model number ADR6410LVW and i'm pretty sure it is in fact a 4g LTE, it says so on the back cover.
Also i've downloaded the 4.0.1.002 drivers from that post in the first place, just got the phone 2 days ago.
Click to expand...
Click to collapse
that driver is for windows 8 i think you need 3.0.007 something like that.
Aldo101t said:
that driver is for windows 8 i think you need 3.0.007 something like that.
Click to expand...
Click to collapse
The 4.x drivers also work with Win7.
sidgallup said:
Well in about>phone identity it says model number ADR6410LVW and i'm pretty sure it is in fact a 4g LTE, it says so on the back cover.
Also i've downloaded the 4.0.1.002 drivers from that post in the first place, just got the phone 2 days ago.
Click to expand...
Click to collapse
Well, if you're sure, you can give the manual instructions a try. If the emulated device isn't something you can unplug, then you'll have to specify the target device for adb with: adb -s FA29TS301243 ...
well... thing is i'm not familiar at all with command line, that's the reason i wanted to use this automatic method, coming from a rooted+m9 Droid 2 with locked bootloader, Incredible 4g looks to intimidating for someone like me, as much as i want to flash Cm10 i don't wanna take the risk of ending with a brick.
Do i need to use this same tool to get it unlocked using the HTCDev method?
sidgallup said:
well... thing is i'm not familiar at all with command line, that's the reason i wanted to use this automatic method, coming from a rooted+m9 Droid 2 with locked bootloader, Incredible 4g looks to intimidating for someone like me, as much as i want to flash Cm10 i don't wanna take the risk of ending with a brick.
Click to expand...
Click to collapse
If you are not comfortable with the command line and the thrill of potentially bricking your phone, please stick with your stock ROM.
This post is relevant.
mdmower said:
If you are not comfortable with the command line and the thrill of potentially bricking your phone, please stick with your stock ROM.
This post is relevant.
Click to expand...
Click to collapse
Yeah, that's what i'm gonna do for now, i thought rooting this phone will be just as relatively easy as with my old Droid 2 Global but it's a completely different animal.
At least last week HTC announced they are updating stock to 4.2.2, with some luck our 4g LTE is getting the update too
mdmower said:
The 4.x drivers also work with Win7.
Well, if you're sure, you can give the manual instructions a try. If the emulated device isn't something you can unplug, then you'll have to specify the target device for adb with: adb -s FA29TS301243 ...
Click to expand...
Click to collapse
I stand corrected, thanks
Ok one last question just to be completely shure i'm not missing something... can i run the script witile the phone is ON or should i be running it with the phone in bootloader mode?
EDIT: ok i got it to work, that other "emulator" device was related to Blue Stacks App Player, as soon as i uninstalled it the script worked perfectly even when my phone wasn't listed as HTXXXX, just installed CM10 and everything is fine.
c:\Android>fastboot oem get_identifier_token
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
I am stuck on this, how do i get pass this the fastboot is there I see it but it won't run
I use windows vista home premium 32 bit
ok yesterday I got as far as the fast boot token on windows and now today the adb is out of date or something to that effect. every time I click sdk manager it has all the revision updates for platform and tools. yesterday it did none of stuff. My device is not found and when i run task 1 it say daemon not working switch to port 5037 and it does not list any devices. Should I do a factory reset on hboot screen? I just installed htc drivers ending in ....23 and still nothing. UBUNTU was a fail because nothing would auto run at all and I had to keep extracting to folders in which nothing found later not to mention no wireless on ubuntu either.
adb is up to date now but no device found, everything powers up just fine
wrong thread

[Help!] Update System with Terminal Emulator with Error "no space left on device"

[Help!] Update System with Terminal Emulator with Error "no space left on device"
I follow the following instruction to update my Meizu Pro5 with success for several times, but i got an error message "no space left on device" this time. Is there any way to solve this?
1. Enable root
Enable root by tapping on Settings-> Accounts-> My Flyme-> Personal settings (first option) -> System privileges and set it to open - accept disclaimer and confirm.
2. Download and successfully install Busybox (from Google Play or see .apk below)
3. Download and install a Terminal Emulator (from Google Play or see apk below)
4. Download the correct and desired international (i) ROM/firmware (update.zip) for your device
5. Download and use the update.zip (firmware) converter that creates the required system-i.img
Click here to download converter first
Copy system.new.dat and system.transfer.list (from the update.zip) to the folder “in” (see converter folder)
Then start the converting process by starting System-conVERTER.cmd and pressing option 1 [enter]
If successfully converted you can find the system-i.img in the ‘‘out’’ folder.
6. Copy the converted system-img from ‘‘out’’ to the internal memory of your Meizu device
7. Go to Settings-> Display-> Sleep and set it to at least 10 minutes
8. Start the Terminal Emulator and run (type) the super user command
su
A permission popup will come; give permission by tapping allow (always allow).
9. Now run (type) the command for installing the system-img.
dd if=/sdcard/system.img of=/dev/block/platform/XXXXXXX/by-name/system
Replace XXXXXXX with the correct partition system for your device
MX4 Pro = 15540000.dwmmc0
M2 note = mtk-msdc.0
MX4 = mtk-msdc.0 (OR mmcblk0p6)
MX5 = mtk-msdc.0 (OR mmcblk0p18)
Pro 5 = 15570000.ufs
Example for MX5 : dd if=/sdcard/system.img of=/dev/block/platform/mtk-msdc.0/by-name/system
Note: Pro5 might require: dd if=/storage/emulated/0/system.img instead of /sdcard/
10. The installation should start after the ‘‘dd if’’ command, but please note…
…it may seem that the copying/process did NOT start because you didn’t notice it, but it DID start.
do NOT type a new command or whatsoever, just…
…be patient and give your device 5-10 minutes to process.
11. When the process is done you’ll see a # at the very end
Your device should be unresponsive by now - this is normal
12. Now just shutdown your phone (hold power button) and reboot it
13. Once successfully booted your device should be running an I-rom
Once in Flyme again it is wise - but not necessary - to completely reset your phone. Go to settings->about phone->memory->factory data reset-> check both boxes and click start cleaning (this could take 5-10minutes). Always backup your stuff if necessary.

Dual boot Redmi 9(GSi with miui)

prove:
I give a zip file.download and extract it.you can find a video watch it as the prove of this post
You can test GSi ROM without any data loss.....
Requirements:
1.Need a laptop with Linux (window also can do...but Linux is batter for CMD line)
2.Unrooted phone.(magisk patch boot not boot gsi for my case try it if it work or not)
3.vbmeta.img(flash it via 'fastboot flash vbmeta vbmeta.img')
3.java installed in your machine...
4.Working brain to solve Errors.:fingers-crossed::fingers-crossed:
Step 1:
Go to the link and download any official gsi arm64-ab version (I can not boot unofficial gsi..Descendant X....any room which it not boot remember you cannot boot it even fastbood method )
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0IRaTTGUOyl04z17LCE96H
Step 2:
Extract and rename file as 'system.img'...
Step 3:
Now open CMD terminal from where your system.img located and paste this cmd...
simg2img system.img system_raw.img
Error and slove...
You need to install simg2img on Linux...
After install and run this CMD you found error like about header file magic or like something...do not worry... that's mean your system.img file already a raw file and do not need to convert it..just rename this file as 'system_raw.img'
Step 4:
Now open CMD terminal from where your system_raw.img located paste this cmd...
gzip -c system_raw.img > system_raw.gz
Wait for finish..
Step 5:
Now connect your phone with via cable and in developers options turn on usb debugging mood and run this CMA...
adb push system_raw.gz /storage/emulated/0/Download/
Wait for finish........
Step 6:
Now run this CMD..
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
Step 7:
Now run this CMD...
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
You need to varying your identity by fingerprints or parttern if your device has lock function on...after varify you will notice a notification like this...
Dynamic system update
That's mean you can successfully do my instructions....:cyclops::cyclops:..
Wait for finish....
Now you have two option restart or discard....
Tap restart to go to your gsi or discard to destroy gsi install....
On gsi you can do what you want..
If your work or discover finis then reboot the phone with power button option.
After reboot you are now miui and yes no data lost...
After some moments you can again get two options (Restart or discard)...
This process go untill you discard gsi...
If you stay gsi after reboot then run the CMD....
adb shell gsi_tool enable
Now you can stay gsi after reboot how many time you want...
Disable this feature now type this CMD ...
adb shell gsi_tool disable
If you face some problems....tell me want is your problem......
If you can dual boot your device the thanks is free...
Go throw below link for more information...
https://developer.android.com/topic/dsu
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Halloul said:
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Click to expand...
Click to collapse
I think it's better to provide your questions in Redmi note 9 fourms in Xda.
Check it :https://forum.xda-developers.com/redmi-note-9
Halloul said:
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Click to expand...
Click to collapse
Redmi note 9 supporting dynamic storage if it come with android 10 out of box..if you hava fastboot rom then go to image folder on it and find super.img.
If super.img found that's mean your are good to go...
Or if you find system.img and vendor.img then sorry
1st time its works great
Then i want to check another gsi but not showing in the notification menu
Mantipallykrishna said:
1st time its works great
Then i want to check another gsi but not showing in the notification menu
Click to expand...
Click to collapse
If you use two GSI. That's mean you install a a dynamic GSI over a GSI then the problem will happen. Because all GSI can not capable with it. If you flash dynamic GSI over MIui Rom then the problem not happened.when you in MIui then restart to go dynamic GSI.when you are in dynamic GSI then do not reboot your device just power off and then power on your device to go MIui.then you find the dynamic GSI restart option again.even if you can not find the notification then go to your device recovery option and reboot device from recovery mood.
Even if your problem not solve then you can activate GSI from adb cmd
adb shell gsi_tool enable
Then you can go GSI and when you reboot you can not go back MIui but it is good option to use GSI without data loss.to deactivate just run this adb cmd
adb shell gsi_tool disable
Now reboot and then you can back MIui again..
But remember to check if your dynamic GSI can connect you PC via adb.
This method work for me.I also face the same problem like you.hope you can solve your problem.and remember one thing that if you use magisk patched boot.img then you can not boot your dynamic GSI.I think it is a bug hopefully it will solve soon
the first time worked fine, then i tried the command: adb shell gsi_tool enable, for some reason i wasn't able to connect to gsi with adb to turn it off: adb shell gsi_tool disable
i flashed miui with miflash, but now the installation won't start again
just found out that when a micro sd card ist in the phone, for some reason dsu won't show up, i removed the micro sd card, restarted the phone, and now dsu shows in the notification bar
Shas45558 said:
prove:
I give a zip file.download and extract it.you can find a video watch it as the prove of this post
You can test GSi ROM without any data loss.....
Requirements:
1.Need a laptop with Linux (window also can do...but Linux is batter for CMD line)
2.Unrooted phone.(magisk patch boot not boot gsi for my case try it if it work or not)
3.vbmeta.img(flash it via 'fastboot flash vbmeta vbmeta.img')
3.java installed in your machine...
4.Working brain to solve Errors.:fingers-crossed::fingers-crossed:
Step 1:
Go to the link and download any official gsi arm64-ab version (I can not boot unofficial gsi..Descendant X....any room which it not boot remember you cannot boot it even fastbood method )
https://www.google.com/url?sa=t&source=web&rct=j&url=https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list&ved=2ahUKEwj04pKZwfnrAhVLfXAKHV8FAFcQFjAAegQIARAB&usg=AOvVaw0IRaTTGUOyl04z17LCE96H
Step 2:
Extract and rename file as 'system.img'...
Step 3:
Now open CMD terminal from where your system.img located and paste this cmd...
simg2img system.img system_raw.img
Error and slove...
You need to install simg2img on Linux...
After install and run this CMD you found error like about header file magic or like something...do not worry... that's mean your system.img file already a raw file and do not need to convert it..just rename this file as 'system_raw.img'
Step 4:
Now open CMD terminal from where your system_raw.img located paste this cmd...
gzip -c system_raw.img > system_raw.gz
Wait for finish..
Step 5:
Now connect your phone with via cable and in developers options turn on usb debugging mood and run this CMA...
adb push system_raw.gz /storage/emulated/0/Download/
Wait for finish........
Step 6:
Now run this CMD..
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
Step 7:
Now run this CMD...
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
You need to varying your identity by fingerprints or parttern if your device has lock function on...after varify you will notice a notification like this...
Dynamic system update
That's mean you can successfully do my instructions....:cyclops::cyclops:..
Wait for finish....
Now you have two option restart or discard....
Tap restart to go to your gsi or discard to destroy gsi install....
On gsi you can do what you want..
If your work or discover finis then reboot the phone with power button option.
After reboot you are now miui and yes no data lost...
After some moments you can again get two options (Restart or discard)...
This process go untill you discard gsi...
If you stay gsi after reboot then run the CMD....
adb shell gsi_tool enable
Now you can stay gsi after reboot how many time you want...
Disable this feature now type this CMD ...
adb shell gsi_tool disable
If you face some problems....tell me want is your problem......
If you can dual boot your device the thanks is free...
Go throw below link for more information...
https://developer.android.com/topic/dsu
Click to expand...
Click to collapse
its give me proble when in start activity at the end.
===========================================================
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
Exception occurred while executing 'start-activity':
java.lang.IllegalArgumentException: No intent supplied
at android.content.Intent.parseCommandArgs(Intent.java:7790)
at com.android.server.am.ActivityManagerShellCommand.makeIntent(ActivityManagerShellCommand.java:341)
at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:438)
at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:189)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:11390)
at android.os.Binder.shellCommand(Binder.java:936)
at android.os.Binder.onTransact(Binder.java:820)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:5216)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3162)
at com.android.server.am.OppoActivityManagerService.onTransact(OppoActivityManagerService.java:169)
at android.os.Binder.execTransactInternal(Binder.java:1166)
at android.os.Binder.execTransact(Binder.java:1130)
=========================================================
Here Is the error code. Im on A11. Realme C3. But when Im use Dsu and download and install from dsu it works im confused ??
fire7ly said:
its give me proble when in start activity at the end.
===========================================================
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
Exception occurred while executing 'start-activity':
java.lang.IllegalArgumentException: No intent supplied
at android.content.Intent.parseCommandArgs(Intent.java:7790)
at com.android.server.am.ActivityManagerShellCommand.makeIntent(ActivityManagerShellCommand.java:341)
at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:438)
at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:189)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:11390)
at android.os.Binder.shellCommand(Binder.java:936)
at android.os.Binder.onTransact(Binder.java:820)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:5216)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3162)
at com.android.server.am.OppoActivityManagerService.onTransact(OppoActivityManagerService.java:169)
at android.os.Binder.execTransactInternal(Binder.java:1166)
at android.os.Binder.execTransact(Binder.java:1130)
=========================================================
Here Is the error code. Im on A11. Realme C3. But when Im use Dsu and download and install from dsu it works im confused ??
Click to expand...
Click to collapse
Use dsu..it is easy method
Shas45558 said:
Use dsu..it is easy method
Click to expand...
Click to collapse
Yeah You Are Right ! . But Dsu gives Only Aosp Gsis. Which Is not So Great. If Any Ways I use Pixel Gsis it Would Be Great.
fire7ly said:
Yeah You Are Right ! . But Dsu gives Only Aosp Gsis. Which Is not So Great. If Any Ways I use Pixel Gsis it Would Be Great.
Click to expand...
Click to collapse
Hmm...thats is the point...use linux and when you input any cmd you must open cmd pannel from where you kept the rom which you try to installed...
Shas45558 said:
Hmm...thats is the point...use linux and when you input any cmd you must open cmd pannel from where you kept the rom which you try to installed...
Click to expand...
Click to collapse
you mean same directory where gsi present.
fire7ly said:
you mean same directory where gsi present.
Click to expand...
Click to collapse
Yes..
work in poco m3?
how about redmi note 9 pro sir? can you give me a link for the tut?

Categories

Resources