Related
Hello, I believed I have an issue. Hope it not to serious. My problem is that i can't get passed the ASUS logo Splash screen.
1st: I was one stock jelly bean rooted cwm recovery v6.0.1.2 and decide I wanted to get on to Hydro 3.6 Jellybean (9/17)
2nd I downloaded the ROM wiped cache,delvic and factory reset then installed, didn't install at first so I tried a mirror and then it installed correctly restarted the tablet and here I am.
3rd: Tried clean rom 2.0 still no luck.
Please help I'm 15 and don't wanna break the bad news to my parents.
Ps: I am able to still boot into CWM recovery 6.0.1.2 tried everything nothing working and able to fastboot but cold boot and wipe data don't work and haven't shut off tablet since accident will remain on and charged.
jekovenatinsley said:
Hello, I believed I have an issue. Hope it not to serious. My problem is that i can't get passed the ASUS logo Splash screen.
1st: I was one stock jelly bean rooted cwm recovery v6.0.1.2 and decide I wanted to get on to Hydro 3.6 Jellybean (9/17)
2nd I downloaded the ROM wiped cache,delvic and factory reset then installed, didn't install at first so I tried a mirror and then it installed correctly restarted the tablet and here I am.
3rd: Tried clean rom 2.0 still no luck.
Please help I'm 15 and don't wanna break the bad news to my parents.
Ps: I am able to still boot into CWM recovery 6.0.1.2 tried everything nothing working and able to fastboot but cold boot and wipe data don't work and haven't shut off tablet since accident will remain on and charged.
Click to expand...
Click to collapse
It's just a softbrick. As long as you can get into fastboot you are ok.
I suggest reflashing the stock jellybean rom. You can download it from the asus website.
As for getting it into your device (i dont know if cwm supprots sd cards yet). You can use the adb push commands or you can flash twrp which supprots flashing from the sd card.
Also next time read the rom thread carefully. It specifically says you should use twrp.
Hey man try this, it works for me (Same situation but i'm 17 xD)
1) Download this http://www.mediafire.com/?5diezc69u1b16f8
2)Extract the "recovery1" folder in C:\ drive
3)Plug the tablet to PC and turn it on while pressing VOL- and POWER, then go to the fastboot mode (is the USB symbol)
4)Download from here ( http://support.asus.com/Download.asp...300T&p=20&s=16 ) the WW of US instead of the version of the tablet you have got, the extract the blob file in the "recovery1" folder
5)Open CMD, type cd c:\recovery1 then press enter
6)Type dir to see if all the files are in the folder
7)type this command fastboot -i 0x0B05 flash system blob
8)After is done, type fastboot -i 0x0B05 reboot
9)Enjoy!
If you can't do any of this steps, post here and I will help you
Fixed It!
ZerOMKD said:
It's just a softbrick. As long as you can get into fastboot you are ok.
I suggest reflashing the stock jellybean rom. You can download it from the asus website.
As for getting it into your device (i dont know if cwm supprots sd cards yet). You can use the adb push commands or you can flash twrp which supprots flashing from the sd card.
Also next time read the rom thread carefully. It specifically says you should use twrp.
Click to expand...
Click to collapse
Hey actually like 10 mins after I posted I was able to install Clean Rom.
I formated every partition except sd card in v6.0.1.2 cwm recovery as well as factory reset and wipe dalvik.
Actually I like cwm recovery better and it does support microsd cards now. This is the jb/touch bootloader.
Thanks for the Help anyways.
.
Same problem, when i try to flash JB Hydro 3.6... i stuck into bootloop... i flash the official asus update and it works... But when i try to flash the hydro rom it doesn't work.... Why?
I guess you have the new JellyBean Bootloader... because of that you can only flash ROM's which are made for it...
.
I know... i update from jb ota to hydro... but when i flash the 3.6 i got bootloop... and now i can flash this rom...
So I unlocked this without much trouble, and then when I was attemoting to use adb to flash images to recovery partition, one would just not work, and I stupidly tried to force it, and now it boots and just sits there.
I've seen a different website saying the Q can run Jellybean, and it also has info on getting the stock rom back .. but NO files. I know how to use the damn recovery tools once theyre booted up - those articles were completely useless. I don;t know what else to do. I tried to get the files that argghhhh jad posted to dropbox but they are not available anymore.
Stuck and been trying to fix this for the last 12 hours
EDIT:
Found stock recovery stuff, but I dont think it's going to help any...
Nevermind I suppose
I see that I can try the stock rar file posted for someone else in here to put into recovery, hope it works, I just dont know if the nernel is ok, but I would think so. It stops at the "unlocked"notificaton screen. anyay, yeah. If I get jellybean on instead ill share the info,
I believe you need to fastboot your recovery, not adb. Then you may be able to flash something back on there.
Sent from my XT897 using xda premium
tetrabyt said:
I believe you need to fastboot your recovery, not adb. Then you may be able to flash something back on there.
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks for the repl! S I actually have been using fastboot because adb for some reason just will not see the device (I checked the version and its correct supposedly). So what I did was take the WWRP rar, pull the contants out and make them into a .zip.and instaled with fastboot flash. The output looked ok:
sending 'userdata' (319120 KB)... OKAY [ 29.814s]
writing 'userdata'... OKAY [ 92.421s]
finished. total time: 122.235s
but what about all the other partitions? I jad done system earlier frok out of the stock zipfile. i think i may just try the entire Stock file insead, or maybe I am missing the fact that I beed to install the kernek into /boot, Any thoughts Thanks much!
EDIT: first im going to fastboot the recovery wit tue TWRP zip file, and try to install it from
I am a little confused, did you manage to get the recovery working? Looks like you were trying to flash the recovery img to your user data partition... Am I misreading your post.
-Saint
Whoaa just saw that. should have unzipped the recovery image and flashed it to the recovery partition with
Fastboot flash recovery recoveryfile.img
Then you can boot into recovery and flash one of the system dumps that these devs have generously posted for when we mess up like this...
Sent from my XT897 using xda premium
tetrabyt said:
Whoaa just saw that. should have unzipped the recovery image and flashed it to the recovery partition with
Fastboot flash recovery recoveryfile.img
Then you can boot into recovery and flash one of the system dumps that these devs have generously posted for when we mess up like this...
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
is this the basic method at present for a stock restore? i was looking at the thread with the files for RSD lite, but i was confused as to whether that was working. thx!
ok so I messed up what to flash from recovery. I had grabbed copies of the system, data, boot, etc for all the partitions thinking i needed to do them all from outside using fastboot,
Herby6262 said:
ok so I messed up what to flash from recovery. I had grabbed copies of the system, data, boot, etc for all the partitions thinking i needed to do them all from outside using fastboot,
Click to expand...
Click to collapse
Ok, the easiest way to get your phone up and running again is to push the newest TWRP from here, put it in your tools folder and push w fastboot:
fastboot flash recovery openrecovery-twrp-2.3.1.0-asanti_c.img
fastboot reboot recovery
Make a backup to your external sd card so that TWRP creates the directory needed to restore the stock system & boot. You should delete this first backup later since it will be broken.
Then download a system & boot image from here, unzip to the /TWRP/BACKUPS/"serial#"/ folder on your external sd. Do full wipes for system, dalvik, & factory reset; then restore Stock from within TWRP. Should be good to go.
:edit:
Just saw that tetrabyt already hit on this, consider this post a more detailed revision.
i must be retardedly doing this the wrong way, i quickly get twrp into recovery and can get in there, and I have the stock photon .zip in 1 big zip and in separate pieces, but how do you get them to the external card.. windows 7 fails to recognize the phone with some message MTP device unknown so I can't transfer it that way ... I dont know. Im about to chuck this thing out the window and be done with it. The whole purpose was to be able to install apps to the sdcard, originally. Only fastboot works from a command prompt, adb doesnt do a damn thing, trying multiple versions of it. I give up
Herby6262 said:
i must be retardedly doing this the wrong way, i quickly get twrp into recovery and can get in there, and I have the stock photon .zip in 1 big zip and in separate pieces, but how do you get them to the external card.. windows 7 fails to recognize the phone with some message MTP device unknown so I can't transfer it that way ... I dont know. Im about to chuck this thing out the window and be done with it. The whole purpose was to be able to install apps to the sdcard, originally. Only fastboot works from a command prompt, adb doesnt do a damn thing, trying multiple versions of it. I give up
Click to expand...
Click to collapse
Do you have an sd adapter or another device you can plug the sd into to transfer from your pc? Does adb fail when booted into TWRP also? Tried uninstalling/re-installing drivers?
Might be able to make a data img you could flash through fastboot, so long as the folder structure was correct... then use recovery from internal storage. Not certain on this: /data/media/sdcard/TWRP/BACKUP/"serial#"/
Maybe someone else can jump in here, this would be my last resort. Use any way possible to get it on external sd first.
-Saint
fallnSaint said:
Do you have an sd adapter or another device you can plug the sd into to transfer from your pc? Does adb fail when booted into TWRP also? Tried uninstalling/re-installing drivers?
Might be able to make a data img you could flash through fastboot, so long as the folder structure was correct... then use recovery from internal storage. Not certain on this: /data/media/sdcard/TWRP/BACKUP/"serial#"/
Maybe someone else can jump in here, this would be my last resort. Use any way possible to get it on external sd first.
-Saint
Click to expand...
Click to collapse
I believe there is a system.img floating around here somewhere.
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1894575
Sent from my XT897 using xda premium
tetrabyt said:
I believe there is a system.img floating around here somewhere.
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1894575
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks a ton for the help Saint, and others. I finally got it back in working order .. yay! Now to install that powermenu update someone made, and see about making android 4 opeate like the older versions, where you could install apps onto the external SD card. Am I correct in assuming they just F'ed it up by changing the /mnt names, while the software was not updated to accomodate those changes? Why the hell is internal memory now "sdcard" ... so odd. I have a friend whose internal storage is named "USB storage" on his phone. It's USB accessible .. but its a freakin flash card. So odd, and stupid. I really felt like 4.0 was a downgrade, personally. What improved? I see nothing, only things taken away (Im sure the underlying scheduler and thread management/memory mgmt is better, but you know what I mean .. anything visible?)
Herby6262 said:
Thanks a ton for the help Saint, and others. I finally got it back in working order .. yay! Now to install that powermenu update someone made, and see about making android 4 opeate like the older versions, where you could install apps onto the external SD card. Am I correct in assuming they just F'ed it up by changing the /mnt names, while the software was not updated to accomodate those changes? Why the hell is internal memory now "sdcard" ... so odd. I have a friend whose internal storage is named "USB storage" on his phone. It's USB accessible .. but its a freakin flash card. So odd, and stupid. I really felt like 4.0 was a downgrade, personally. What improved? I see nothing, only things taken away (Im sure the underlying scheduler and thread management/memory mgmt is better, but you know what I mean .. anything visible?)
Click to expand...
Click to collapse
Good to hear, glad you got her working again. As for how she runs, definitely snappier than older versions of android. Maybe just hardware, but I still see improvements w the wifes epic running ics, guessing that we will see better results once CM is dropped for this phone.
-Saint
Tried this, still stuck on Bootloader Unlocked Screen. TWRP restores don't seem to work right. I tried restoring an old backup I had of the boot/recovery/system with no luck. Everytime I wiped system/dalvik/cache/factory reset before restore. No errors show up.
So, I can go into fastboot, and I can flash files.
I tried RSD Lite 5.7 with this Zip
It flashes everything until RSD wants me to reboot. Then it reboots and gets stuck on the bootloader unlocked screen.
Any ideas?
[Edit] I flash CWM and found out that I can't mound /sdcard which doesn't seem right...
fallnSaint said:
Ok, the easiest way to get your phone up and running again is to push the newest TWRP from here, put it in your tools folder and push w fastboot:
fastboot flash recovery openrecovery-twrp-2.3.1.0-asanti_c.img
fastboot reboot recovery
Make a backup to your external sd card so that TWRP creates the directory needed to restore the stock system & boot. You should delete this first backup later since it will be broken.
Then download a system & boot image from here, unzip to the /TWRP/BACKUPS/"serial#"/ folder on your external sd. Do full wipes for system, dalvik, & factory reset; then restore Stock from within TWRP. Should be good to go.
:edit:
Just saw that tetrabyt already hit on this, consider this post a more detailed revision.
Click to expand...
Click to collapse
After RSD Lite, it might not have booted up because the system image was removed from the file to make it work. Probably if you flash TWRP after doing the RSD file, and restore Rangerbry's system backup, you might be good..
No Luck.
Just tried this.
Got the following Errors during only system restore:
E:Unable to mount '/cache'
E:unable to mount '/data'
Still stuck on Unlocked bootloader screen.
My emmc might be corrupted I think
I do have sprint insurance. Think they can reflash stock?
yogi2010 said:
After RSD Lite, it might not have booted up because the system image was removed from the file to make it work. Probably if you flash TWRP after doing the RSD file, and restore Rangerbry's system backup, you might be good..
Click to expand...
Click to collapse
coolroman123 said:
No Luck.
Just tried this.
Got the following Errors during only system restore:
E:Unable to mount '/cache'
E:unable to mount '/data'
Click to expand...
Click to collapse
Was that in CWM or TWRP recovery? Just trying to make sure the process was correct, haha. I have only started using TWRP on this device, but i think the 2 recoveries use different backup formats?
coolroman123 said:
Tried this, still stuck on Bootloader Unlocked Screen. TWRP restores don't seem to work right. I tried restoring an old backup I had of the boot/recovery/system with no luck. Everytime I wiped system/dalvik/cache/factory reset before restore. No errors show up.
So, I can go into fastboot, and I can flash files.
I tried RSD Lite 5.7 with this Zip
It flashes everything until RSD wants me to reboot. Then it reboots and gets stuck on the bootloader unlocked screen.
Any ideas?
[Edit] I flash CWM and found out that I can't mound /sdcard which doesn't seem right...
Click to expand...
Click to collapse
Can you boot to bootloader or just to fastboot? There are two control files in that RSD zip, one doesn't flash bootloader, try removing that one and forcing the reflashed bootloader. Then try restoring again. About all I can think of if it successfully flashes the other components... Maybe just restore system and not boot or data?
-Saint
Everything you need is here to return to stock WITH ota update.
http://forum.xda-developers.com/showthread.php?t=2001226
The only thing simple is the belief in simplicity.
Hi guys, Im having a little Problem with my tf300. I've been running Baked 6 rom for a couple months and saw that version 7 was released which is full 4.2.1. Backed up, wiped, flashed, and rebooted.
Got stuck at Asus splash screen. unable to turn device off, it just turns right back on to the splash screen. I am able to hold volume down + power to get into TWRP recovery.
Restored back up, rebooted and still stuck on ASUS screen. Tried another backup with same result
Tried re-downloading rom copying it to external memory card and flashing again, still stuck at asus screen.
I am so lost here, not sure if i should throw this thing out the window, or get on my knees and pray.
any help is greatly appreciated.
I have googled the problem and have seen similar issues, but not anybody that can access recovery and still has the problem.
cavz903 said:
Hi guys, Im having a little Problem with my tf300. I've been running Baked 6 rom for a couple months and saw that version 7 was released which is full 4.2.1. Backed up, wiped, flashed, and rebooted.
Got stuck at Asus splash screen. unable to turn device off, it just turns right back on to the splash screen. I am able to hold volume down + power to get into TWRP recovery.
Restored back up, rebooted and still stuck on ASUS screen. Tried another backup with same result
Tried re-downloading rom copying it to external memory card and flashing again, still stuck at asus screen.
I am so lost here, not sure if i should throw this thing out the window, or get on my knees and pray.
any help is greatly appreciated.
I have googled the problem and have seen similar issues, but not anybody that can access recovery and still has the problem.
Click to expand...
Click to collapse
Are you sure to be still rooted ?
Simply question
If you aren't still root, just root again before to try some rom install
philos64 said:
Are you sure to be still rooted ?
Simply question
If you aren't still root, just root again before to try some rom install
Click to expand...
Click to collapse
sorry for the delay - thanks for the reply.
I dont know how to tell if im rooted from recovery.
So just went ahead and flashed the root file i found here:
http://www.androidgadgematic.com/2012/10/root-asus-transformer-pad-tf300-install-cwm.html
flashed Baked 7 and gapps again with same result.
(however i noticed at first reboot the asus screen shows a quick blue loading bar under center logo. then nothing.)
rebooted into TWRP - wiped - flashed root.zip again - restored backup.......asus screen.
another thing i noticed was when i try to install (flash) anything, it says no md5 found or if i select "force md5 check" it fails.
im a seasoned novice. I've gotten myself out of some sticky jams. but im totally lost here....
cavz903 said:
Hi guys, Im having a little Problem with my tf300. I've been running Baked 6 rom for a couple months and saw that version 7 was released which is full 4.2.1. Backed up, wiped, flashed, and rebooted.
Got stuck at Asus splash screen. unable to turn device off, it just turns right back on to the splash screen. I am able to hold volume down + power to get into TWRP recovery.
Restored back up, rebooted and still stuck on ASUS screen. Tried another backup with same result
Tried re-downloading rom copying it to external memory card and flashing again, still stuck at asus screen.
I am so lost here, not sure if i should throw this thing out the window, or get on my knees and pray.
any help is greatly appreciated.
I have googled the problem and have seen similar issues, but not anybody that can access recovery and still has the problem.
Click to expand...
Click to collapse
I suggest flash latest stock with twrp. You will loose twrp but with a working unit you can fastboot twrp again.
tobdaryl said:
I suggest flash latest stock with twrp. You will loose twrp but with a working unit you can fastboot twrp again.
Click to expand...
Click to collapse
thanks
ive looked around. but cant find a flashable stock download.
i did find a method to flash a blob via fastboot. but i dont know how to tell if i have a WW or a TW sku.(to DL firmware from asus site)
is TW for users in Taiwan? and WW for everybody else world wide?
cavz903 said:
thanks
ive looked around. but cant find a flashable stock download.
i did find a method to flash a blob via fastboot. but i dont know how to tell if i have a WW or a TW sku.(to DL firmware from asus site)
is TW for users in Taiwan? and WW for everybody else world wide?
Click to expand...
Click to collapse
The SKU versions on the asus firmware page, are as follows:
- US = USA
- CN = China
- TW = Taiwan
- WW = Worldwide
- DE = Germany
- JP = Japan
- TB = Belgium, Turkey, Luxembourg
But you can flash US or WW, they are compatible
philos64 said:
The SKU versions on the asus firmware page, are as follows:
- US = USA
- CN = China
- TW = Taiwan
- WW = Worldwide
- DE = Germany
- JP = Japan
- TB = Belgium, Turkey, Luxembourg
But you can flash US or WW, they are compatible
Click to expand...
Click to collapse
ok so, downloaded WW stock firmware from Asus site. flashed blob file via fastboot.
it said it finished "okay"
rebooted and, back at the Asus Screen.
and now i dont have recovery either. any suggestions?
thank you
any other ideas? im lost here... thanks
cavz903 said:
any other ideas? im lost here... thanks
Click to expand...
Click to collapse
This is normal. The stock blob contains stock recovery and is flashed over the recovery you have in place.
Time to reflash your twrp.
tobdaryl said:
This is normal. The stock blob contains stock recovery and is flashed over the recovery you have in place.
Time to reflash your twrp.
Click to expand...
Click to collapse
Ok so i will re-flash twrp via fastboot. but then what!? re-root via an update.zip? and flash a few custom rom? beacuse i am still stuck at the Asus boot screen.
cavz903 said:
Ok so i will re-flash twrp via fastboot. but then what!? re-root via an update.zip? and flash a few custom rom? beacuse i am still stuck at the Asus boot screen.
Click to expand...
Click to collapse
Flash the latest twrp (2.4.1.0). There were issues of using 4.2 and custom recoveries. That was the reason for the last two versions of twrp.
All custom roms here I have checked are pre rooted so the only time I flash root is with a stock rom.
If you were not already using twrp 2.4.1.0 then reflash your stock rom. Earlier versions might not flash the roms properly for 4.2. We need to get working first then you can flash your rom choice.
I hope your version of twrp is less than 2.4.1.0 because if not I'm lost at the moment. I'll be thinking and searching while you play.
Good Luck!
Note: Sorry I should have said twrp 2.4.1.0 JellyBean!
cavz903 said:
Ok so i will re-flash twrp via fastboot. but then what!? re-root via an update.zip? and flash a few custom rom? beacuse i am still stuck at the Asus boot screen.
Click to expand...
Click to collapse
How are you getting the roms onto your device to flash them, the TF300 doesn't have any external memory. Unless there is a way to push the file to the internal sdcard via fastboot, that I'm looking into right now, I dont understand how you are able to flash anything besides .img files or an update.zip.
flukeSG2 said:
How are you getting the roms onto your device to flash them, the TF300 doesn't have any external memory. Unless there is a way to push the file to the internal sdcard via fastboot, that I'm looking into right now, I dont understand how you are able to flash anything besides .img files or an update.zip.
Click to expand...
Click to collapse
Flash recovery with fastboot
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot
Note: recovery is in the directory with fastboot on the pc
Flash recovery with adb
adb shell
su
adb push twrp.blob /sdcard/twrp.blob
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
Note: twrp.blob is in the directory with adb and fastboot on the pc and is copied to the sdcard
Flash recovery with android terminal
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
exit
Note: twrp.blob is on the sdcard
/sdcard as used here is an example – paths to both (internal or external) sdcards change with rom and you need to look at the proper path for the sdcard you wish to use. A root browser is what I use for this.
These are examples for the tf300 there are others.
Red text are actual commands typed!
Maybe this will help to explain the most commonly used methods.
Your internal and external sdcards are normally mounted when your tablet is plugged into your pc
I'm sorry I had to respond!
tobdaryl said:
Flash recovery with fastboot
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot
Note: recovery is in the directory with fastboot on the pc
Flash recovery with adb
adb shell
su
adb push twrp.blob /sdcard/twrp.blob
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
Note: twrp.blob is in the directory with adb and fastboot on the pc and is copied to the sdcard
Flash recovery with android terminal
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
exit
Note: twrp.blob is on the sdcard
/sdcard as used here is an example – paths to both (internal or external) sdcards change with rom and you need to look at the proper path for the sdcard you wish to use. A root browser is what I use for this.
These are examples for the tf300 there are others.
Red text are actual commands typed!
Maybe this will help to explain the most commonly used methods.
Your internal and external sdcards are normally mounted when your tablet is plugged into your pc
I'm sorry I had to respond!
Click to expand...
Click to collapse
I apparently don't have drivers for adb for my tf300t. I have no problem with fastboot. I am able to successfully flash the recovery, but I am unable to push any data to my sdcard.
Without being able to fully boot my tablet, I'm not sure I can even get adb to work? If I install drivers for adb, won't I lose my fastboot capabilities that I currently have? My tablet shows up as a fastboot device in my device manager, would I just open it's properties and select new drivers for it?
My next idea is to get ahold of the system.img, boot.img and recovery.img from a rom to flash from fastboot. I can't seem to find these inside any roms I've downloaded yet, where would I find them? I am thinking I would prefer the latest stock asus rom if possible. I've downloaded the rom from Asus website, unzipped it and no .img files in it. I've also downloaded the rooted stock rom from xda here and also no .img files inside it. Does this even sound plausible, to flash those .img files from inside fastboot to make the tablet boot up?
Edit: Small side question, what exactly is "-i 0x0B05" that for? I seem to be able to accomplish flashing things without that small bit in my commands for example I can just type \fastboot flash recovery recovery.img and that works just fine. So what is that small code?
flukeSG2 said:
I apparently don't have drivers for adb for my tf300t. I have no problem with fastboot. I am able to successfully flash the recovery, but I am unable to push any data to my sdcard.
Since you did not provide data about your situation I looked at your previous posts. Notice the big red line in my signature about WIPE DATA.
I'll try to help but this is a hard one to fix. You have to be willing to keep chipping away till I give or we have success. It can be very frustrating.
Without being able to fully boot my tablet, I'm not sure I can even get adb to work? If I install drivers for adb, won't I lose my fastboot capabilities that I currently have? My tablet shows up as a fastboot device in my device manager, would I just open it's properties and select new drivers for it?
My next idea is to get ahold of the system.img, boot.img and recovery.img from a rom to flash from fastboot. I can't seem to find these inside any roms I've downloaded yet, where would I find them? I am thinking I would prefer the latest stock asus rom if possible. I've downloaded the rom from Asus website, unzipped it and no .img files in it. I've also downloaded the rooted stock rom from xda here and also no .img files inside it. Does this even sound plausible, to flash those .img files from inside fastboot to make the tablet boot up?
Edit: Small side question, what exactly is "-i 0x0B05" that for? I seem to be able to accomplish flashing things without that small bit in my commands for example I can just type \fastboot flash recovery recovery.img and that works just fine. So what is that small code?
Click to expand...
Click to collapse
-i 0x0B05 is an identification provided by google for Asus android products. Each vendor is provided with a number. My tablet does not require it either but some do so we just suggest it to everyone.
I'm skipping everything else you asked for the moment.
Prior to flashing CWM were you on JB or ICS?
Either way we need to replace your non working CWM with twrp (2.4.1.0). Here is the link if you were on JB then flash JB if you were on ICS flash ICS.
tobdaryl said:
-i 0x0B05 is an identification provided by google for Asus android products. Each vendor is provided with a number. My tablet does not require it either but some do so we just suggest it to everyone.
I'm skipping everything else you asked for the moment.
Prior to flashing CWM were you on JB or ICS?
Either way we need to replace your non working CWM with twrp (2.4.1.0). Here is the link if you were on JB then flash JB if you were on ICS flash ICS.
Click to expand...
Click to collapse
Hey I appreciate your help man. I was on CM10 JB 4.1.1, but that was before they required us to have the JB Bootloader, which is where I started to mess up at. I've had CWM since I was running CM10, so when I wiped data, it wasn't from a stock recovery, but I'm guessing that doesn't make a difference. Anyways right now, I'm waiting for the battery to charge up a bit, let it die out last night. I will post as soon as I get TWRP flashed.
flukeSG2 said:
Hey I appreciate your help man. I was on CM10 JB 4.1.1, but that was before they required us to have the JB Bootloader, which is where I started to mess up at. I've had CWM since I was running CM10, so when I wiped data, it wasn't from a stock recovery, but I'm guessing that doesn't make a difference. Anyways right now, I'm waiting for the battery to charge up a bit, let it die out last night. I will post as soon as I get TWRP flashed.
Click to expand...
Click to collapse
Good. While waiting you can download the latest ICS stock 9.4.3.30. You will find it in post 3 of this thread.
So I've got an interesting snag now. I've flashed TWRP 4 times, it never takes. When I boot into recovery, it's still CWM. When I use fastboot, it says it's sending and writing are both ok, but when I reboot into recovery it's still CWM 5.5.0.4.
Edit: I even went as far as to try using the JB version of TWRP, because I was on JB before, just not the 4.2.1 that requires JB bootloader. Still gives me the same result.
Edit 2: I have the stock boot.blob also I just tried flashing, same thing, still got CWM after flashing the blob.
flukeSG2 said:
So I've got an interesting snag now. I've flashed TWRP 4 times, it never takes. When I boot into recovery, it's still CWM. When I use fastboot, it says it's sending and writing are both ok, but when I reboot into recovery it's still CWM 5.5.0.4.
Edit: I even went as far as to try using the JB version of TWRP, because I was on JB before, just not the 4.2.1 that requires JB bootloader. Still gives me the same result.
Edit 2: I have the stock boot.blob also I just tried flashing, same thing, still got CWM after flashing the blob.
Click to expand...
Click to collapse
Your recovery has to be the same as your bootloader. Don't mistake JB in rom name and JB bootloader. They are two different things and if your bootloader is ICS then we need ICS.
OK. Let's see what we have to work with now. Boot into CWM, plug your tablet into your pc and check for adb access.(adb devices)
tobdaryl said:
Your recovery has to be the same as your bootloader. Don't mistake JB in rom name and JB bootloader. They are two different things and if your bootloader is ICS then we need ICS.
OK. Let's see what we have to work with now. Boot into CWM, plug your tablet into your pc and check for adb access.(adb devices)
Click to expand...
Click to collapse
It's not charging fast enough on my pc, so I had to disconnect it and plug it into the wall for awhile again. I can pm you if you'd like when I get it fully charged.
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
greydelta38 said:
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
Click to expand...
Click to collapse
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
greydelta38 said:
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
Click to expand...
Click to collapse
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
JoinTheRealms said:
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
Click to expand...
Click to collapse
Yeah - I'm also wondering what bootloader you are running with it.
If you are not current on either flash the bootloader/TWRP package from CROMi-X OP, boot back into system, let it bootloop if it does, boot back into TWRP and reflash the rom.
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
greydelta38 said:
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
Click to expand...
Click to collapse
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
berndblb said:
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
Click to expand...
Click to collapse
sbdags said:
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
Click to expand...
Click to collapse
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
greydelta38 said:
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
Click to expand...
Click to collapse
You need to specifically format data in twrp not just wipe data. Only formatting will restore the device now once data corruption has occurred.
Hi all.
Have bricked my Mi 10 Ultra China Rom.
Have tried to flash a multi Xiaomi.eu Rom. Tried
TWRP. Tried to flash back to Stock Rom with XiaoMiTool V2.
Now, have Stock Recovery. Device hangs by the first white MI Logo in a Loop.
I can boot into Fastboot but adb devices don't shows
the Phone.
Well, any, any Help will be appreciated.
Helmut
if you can get into fastboot it's not bricked don't worry. I think your phone has no image at the moment or that stock image is not compatible in some way. I am laying the blame at Xiaomitoolv2 + stock rom - don't use it, you don't need it, let's forget that & try to get you to EU
This is the EU package to use:
https://www.androidfilehost.com/?fid=8889791610682929474
Use with this fastboot.exe http://www.mediafire.com/file/13j0xr5r4sq2c1w/fastboot.rar/file (unrar and rename it to exe)
if it is rebooting straight to recovery you should be able to wipe data cache partition (this is an option within recovery)- might be enough to fix. Heck, try that first!
Sounds like it is booting to a MIUI logo. OK, wait 20 minutes, if you see a little unlocked padlock icon you put that there by unlocking the phone - it is your clue the phone isn't dead. If it's not happening or that icon isn't unlocked? Go into recovery and wipe. (if it's chinese look at this https://www.devicesfaq.com/en/articles/reset-chinese-device) and see what happens next.
I would not worry about adb devices, for some reason this didn't work for me either as long as you can actually run commands in CMD and the phone responds. How are you putting on the EU ROM - as in, are you running the batch files they supplied; what happens now? (I want you to run the batch file because it wipes the phone and prepares it for you. I think you have a bad stock image there, you see)
If you go to fastboot mode and you're using the fastboot.exe above, I expect the EU package's batch file to work: windows_fastboot_first_install_with_data_format.bat
Because it starts with a full format. The only way it won't do anything is, I guess, drivers on your PC - and if that package still has a fastboot.exe in it, you *must* replace it, no ifs no buts
(Also FYI I was waiting at least 10 minutes on that logo when I first flashed the EU ROM. And that's when it WORKS. It is scary and you'll think it's dead... but it does just take a long time. Some people even had to reboot + wipe data at that point (wipe cache partition is sometimes all it ever needs to get a ROM working). So... Even if this WORKS you WILL be staring at that logo longer than you would like to!)
Try the batch files & come back please
------------------------------------
General status of this phone and its bootloops:
- if it boots straight into fastboot, it has no bootable image - sounds scary but you can just reflash the eu rom with a different fastboot.exe than the one bundled with the EU rom (using a different fastboot is not an optional step!). You can get stuck in this by using the latest fastboot.exe released; it is broken plain & simple
- if it boots into the stuck miui logo wait for like 20 minutes - seriously - anything else is within fastboot. At most might need to wipe the phone or factory reset (Can do this via cmd). Also look at https://www.devicesfaq.com/en/reset/xiaomi-mi-10-ultra
Also thinking about trying twrp again. You say "tried" this and the EU ROM but what actually happened?
Thanks for the fast Reply, ToneLa
Sorry for the Delay, had to charge the Phone!
Have done it like you described: Downloaded the special fastboot.exe, copied it in the "platform-tools-windows"-Folder of the ROM "xiaomi.eu_multi_MI10Ultra_20.9.3_v12-10-fastboot"
and start the Flash Process with the Batch File"windows_fastboot_first_install_with_data_format.bat". Right after the Phone restarts i pressed the Volume-Up Button and cleared the Caches
with "Wipe Data". Was a little of a Blind Flight because all was in Chinese!
After a couple of Minutes the Phone starts in my Language (German)!
Thanks a Lot for the Hint with the special fastboot.exe, i have tried this with the fastboot.exe from the ROM and from the ADB Developer Suite but with no Luck. Ended always in a Loop Boot.
Helmut
Sehr gut
Very happy this worked for you. The key is always fastboot.. The latest release is bugged, its not the ROM's fault, it's very annoying & will cause people grief!
But this is good news, it wasn't bricked, this is why I help people... It feels good when you help a bad situation
Enioy your phone, it will be like new!
helmut.eder said:
Hi all.
Have bricked my Mi 10 Ultra China Rom.
Have tried to flash a multi Xiaomi.eu Rom. Tried
TWRP. Tried to flash back to Stock Rom with XiaoMiTool V2.
Now, have Stock Recovery. Device hangs by the first white MI Logo in a Loop.
I can boot into Fastboot but adb devices don't shows
the Phone.
Well, any, any Help will be appreciated.
Helmut
Click to expand...
Click to collapse
Format data after flash eu rom
dungnghien said:
Format data after flash eu rom
Click to expand...
Click to collapse
Thanks for the Hint! ??
Perhaps...the Updater App on my Phone shows an Update to 20.9.17!
Can't see if this is a Multi Language Rom or China.
Does the Updater now shows only Equal Rom like the installed?
Thanks in advance
Helmut
helmut.eder said:
Perhaps...the Updater App on my Phone shows an Update to 20.9.17!
Can't see if this is a Multi Language Rom or China.
Does the Updater now shows only Equal Rom like the installed?
Thanks in advance
Helmut
Click to expand...
Click to collapse
Updater App doesn't work without TWRP or flash manually. You can reboot to recovery and if you have TWRP you can install it that way (but wipe too within TWRP)
I'm on that one. Weekly and stable are different... Both are multi language, that's the point of the EU Rom
Few bugs in each. I don't think you'll lose anything moving.
But you'll need to do it in TWRP so get that sorted! Flash it like you've done before... And if you switch between them, wipe to prevent errors
I like the weekly rom, some bugs. Videos are green if you use stabilisation. Settings search crashes if you are too slow!
But brilliant.
I would say install weekly if you want to be on the cutting edge and are prepared for some small bugs.
Stable is for 99% of users
And really this is where you want to be. Any new rom will need TWRP then root. I also rooted my phone with latest magisk
Root is great but some banking apps don't work. It's a personal choice, don't rush into it
Thanks for the Insight, ToneLa.
Will stay at the Moment with the 20.9.3.:angel:
Maybe later i will try an Update with the fastboot.exe
and Update Batch File from the Rom.
Thanks for your Efforts.
Helmut
helmut.eder said:
Thanks for the Insight, ToneLa.
Will stay at the Moment with the 20.9.3.:angel:
Maybe later i will try an Update with the fastboot.exe
and Update Batch File from the Rom.
Thanks for your Efforts.
Helmut
Click to expand...
Click to collapse
That rom is great. Weekly is hardly different...!
I did not use the batch files for updating. If you want to update, put on Chinese TWRP, download the update via updater and when at 100% do Reboot to Recovery option (it won't install).
Install in TWRP then wipe and reboot (I didn't even need to wipe... But it's good to)
Going forward the usual way with the EU ROM is via TWRP so it's good to have it
TWRP isn't official yet, suppose you know we are using an odd Chinese version we set to English.. Can dig out the link if you have no idea what I'm talking about
Hi all, I have the same problem: I have a MI Ultra, unlocked the bootloader (waiting for a week), and now I am stuck in a bootloop. I tried what you wrote:
Downloaded the ROM, replaced the fastboot.exe, used the batch file (seem to work without errors), Volume up on first restart, wipe, but I am back in a loop restarting every 2 minutes.
No problem to get into TWRP or Fastboot.
What shall I do?
EDIT::::: No idea why, tried the same thing again, now it works....
Always best to format, not just wipe on first boot. The bat file should do it when using a fastboot ROM, it may not have fully done that, hence the bootloop. But when you use your first .zip file flash from twrp, format data, not just wipe and again if you change ROM branches between stable and weekly.
Sathelp said:
Always best to format, not just wipe on first boot. The bat file should do it when using a fastboot ROM, it may not have fully done that, hence the bootloop. But when you use your first .zip file flash from twrp, format data, not just wipe and again if you change ROM branches between stable and weekly.
Click to expand...
Click to collapse
Big thank you all that contributed to that thread, I have now a great phone with German ROM.
Would you recommend me to use stable or weekly? I have weekly now and everything seems to work fine...
OnkelAlbert said:
Big thank you all that contributed to that thread, I have now a great phone with German ROM.
Would you recommend me to use stable or weekly? I have weekly now and everything seems to work fine...
Click to expand...
Click to collapse
Weekly gets the latest features, but there's a slight risk that a new weekly release might contain bugs that went unnoticed during internal testing by the devs.
The way I do it, is that I'll run weekly - and everytime a new weekly version gets released, I'll wait about 4 days before updating to it.
That's usually enough time for any critical bugs to surface.
Please remember that if you change branches between stable and weekly, you must format data as there may have been a change of partition tables and you could end up with bootloop again.
ToneLa said:
if you can get into fastboot it's not bricked don't worry. I think your phone has no image at the moment or that stock image is not compatible in some way. I am laying the blame at Xiaomitoolv2 + stock rom - don't use it, you don't need it, let's forget that & try to get you to EU
This is the EU package to use:
https://www.androidfilehost.com/?fid=8889791610682929474
Use with this fastboot.exe http://www.mediafire.com/file/13j0xr5r4sq2c1w/fastboot.rar/file (unrar and rename it to exe)
if it is rebooting straight to recovery you should be able to wipe data cache partition (this is an option within recovery)- might be enough to fix. Heck, try that first!
Sounds like it is booting to a MIUI logo. OK, wait 20 minutes, if you see a little unlocked padlock icon you put that there by unlocking the phone - it is your clue the phone isn't dead. If it's not happening or that icon isn't unlocked? Go into recovery and wipe. (if it's chinese look at this https://www.devicesfaq.com/en/articles/reset-chinese-device) and see what happens next.
I would not worry about adb devices, for some reason this didn't work for me either as long as you can actually run commands in CMD and the phone responds. How are you putting on the EU ROM - as in, are you running the batch files they supplied; what happens now? (I want you to run the batch file because it wipes the phone and prepares it for you. I think you have a bad stock image there, you see)
If you go to fastboot mode and you're using the fastboot.exe above, I expect the EU package's batch file to work: windows_fastboot_first_install_with_data_format.bat
Because it starts with a full format. The only way it won't do anything is, I guess, drivers on your PC - and if that package still has a fastboot.exe in it, you *must* replace it, no ifs no buts
(Also FYI I was waiting at least 10 minutes on that logo when I first flashed the EU ROM. And that's when it WORKS. It is scary and you'll think it's dead... but it does just take a long time. Some people even had to reboot + wipe data at that point (wipe cache partition is sometimes all it ever needs to get a ROM working). So... Even if this WORKS you WILL be staring at that logo longer than you would like to!)
Try the batch files & come back please
------------------------------------
General status of this phone and its bootloops:
- if it boots straight into fastboot, it has no bootable image - sounds scary but you can just reflash the eu rom with a different fastboot.exe than the one bundled with the EU rom (using a different fastboot is not an optional step!). You can get stuck in this by using the latest fastboot.exe released; it is broken plain & simple
- if it boots into the stuck miui logo wait for like 20 minutes - seriously - anything else is within fastboot. At most might need to wipe the phone or factory reset (Can do this via cmd). Also look at https://www.devicesfaq.com/en/reset/xiaomi-mi-10-ultra
Also thinking about trying twrp again. You say "tried" this and the EU ROM but what actually happened?
Click to expand...
Click to collapse
hello, i have problems with my 10 ultra. Person I'm new to this, I have downloaded the zip and the fasboot exe but now I don't know how to do it. There is a youtube type tutorial or manual to do steps. thanks i am somewhat lost. i need help
Here is my guide.... https://mega.nz/file/6UAhXCxZ#Np2KwhMnl8obmOvp4b-2R9ajo0zrtz3vwefy-Ya3PLs
Let us all know how you get on. We're here to help you, so no question is a silly question
ToneLa said:
if you can get into fastboot it's not bricked don't worry. I think your phone has no image at the moment or that stock image is not compatible in some way. I am laying the blame at Xiaomitoolv2 + stock rom - don't use it, you don't need it, let's forget that & try to get you to EU
This is the EU package to use:
https://www.androidfilehost.com/?fid=8889791610682929474
Use with this fastboot.exe http://www.mediafire.com/file/13j0xr5r4sq2c1w/fastboot.rar/file (unrar and rename it to exe)
if it is rebooting straight to recovery you should be able to wipe data cache partition (this is an option within recovery)- might be enough to fix. Heck, try that first!
Sounds like it is booting to a MIUI logo. OK, wait 20 minutes, if you see a little unlocked padlock icon you put that there by unlocking the phone - it is your clue the phone isn't dead. If it's not happening or that icon isn't unlocked? Go into recovery and wipe. (if it's chinese look at this https://www.devicesfaq.com/en/articles/reset-chinese-device) and see what happens next.
I would not worry about adb devices, for some reason this didn't work for me either as long as you can actually run commands in CMD and the phone responds. How are you putting on the EU ROM - as in, are you running the batch files they supplied; what happens now? (I want you to run the batch file because it wipes the phone and prepares it for you. I think you have a bad stock image there, you see)
If you go to fastboot mode and you're using the fastboot.exe above, I expect the EU package's batch file to work: windows_fastboot_first_install_with_data_format.bat
Because it starts with a full format. The only way it won't do anything is, I guess, drivers on your PC - and if that package still has a fastboot.exe in it, you *must* replace it, no ifs no buts
(Also FYI I was waiting at least 10 minutes on that logo when I first flashed the EU ROM. And that's when it WORKS. It is scary and you'll think it's dead... but it does just take a long time. Some people even had to reboot + wipe data at that point (wipe cache partition is sometimes all it ever needs to get a ROM working). So... Even if this WORKS you WILL be staring at that logo longer than you would like to!)
Try the batch files & come back please
------------------------------------
General status of this phone and its bootloops:
- if it boots straight into fastboot, it has no bootable image - sounds scary but you can just reflash the eu rom with a different fastboot.exe than the one bundled with the EU rom (using a different fastboot is not an optional step!). You can get stuck in this by using the latest fastboot.exe released; it is broken plain & simple
- if it boots into the stuck miui logo wait for like 20 minutes - seriously - anything else is within fastboot. At most might need to wipe the phone or factory reset (Can do this via cmd). Also look at https://www.devicesfaq.com/en/reset/xiaomi-mi-10-ultra
Also thinking about trying twrp again. You say "tried" this and the EU ROM but what actually happened?
Click to expand...
Click to collapse
Hi, I'm totally stuck... my phone just reboots in TWRP every time no matter what I try.
I just went through the instructions above as a final hope.... but no... completed and rebooted in TWRP...
Can anyone advise how to get out of this?
Thanks in advance.
Update after trying everything I could find on the web and just short Frisbeeing the phone out of the window I reinstalled the Chinese factory recovery, cleared the data .... rebooted and it worked!
Did you format after installing the ROM in twrp? Not just wipe but a proper format where you have to type yes to continue?
Please don't panic, your phone will be fine. Just install the ROM, format and reboot system. Here is a link to my guide.
File on MEGA
mega.nz
Hi guys, I just got my mi 10 ultra today, and now I want to change the rom to eu since I live in Europe... but I am afraid because I see that there are some camera changes in this custom room..? can anyone test out official and custom and confirm it there are such differences because I bought the phone just for it's cam