I was trying to update to the newest version of MIUI, decided to do a clean install as I have been having some problems lately.
So wiped the phone in BMM recovery and installed the zip for MIUI and GAPPs, but then my BMM removed itself (it did tell me it was doing this, but following the instructions to get it to stay didn't work, and it didn't say why it was doing this).
So now I am stuck with stock recovery, I still have the zips for MIUI and GAPPs on the sd card, but no ROM installed. Without the ROM installed I can't boot to install custom recovery, and without custom recovery I can't install the ROM, so I am kind of stuck here.
Is there a way to install either a custom ROM or recovery from the stock recovery? It doesn't have to be BMM, I originally had that as I was trying different ROMs, but I have decided to stick with MIUI now.
Thanks in advance for any help.
I guess maybe I should look for the stock rom, install that, then install custom recovery and ROM. I will look for that in the meantime while I await any better answers
I have tried flashing a current stock rom from a different country, and also an older version from my country (can't find the current one anywhere), on both was the same result, cannot verify signature.
I am all out of ideas now, is there anything I can do, or is it time to bin the phone?
Final update, have tried various things throughout the day, finally found a way of getting stock rom on that looked like it was going to work, but now my battery is dead, so I guess thats that.
obsidianwings said:
Final update, have tried various things throughout the day, finally found a way of getting stock rom on that looked like it was going to work, but now my battery is dead, so I guess thats that.
Click to expand...
Click to collapse
Don't worry, it's not the end. Cannot verify signature also happens when your battery life is below the safety margin of flashing.
On this phone a working OS is required to charge it, going below the 30% battery flashing requirement is something a lot of people have run into. Including me, with my mothers's phone. You can get it working again, if you have a spare a usb cable.
I had to charge it manually, the only disadvantage is it doesn't stop charging if it reaches max with this method. Therefore you should only charge it for an hr max at a time.
Method 1: Charge the battery manually without an os (warning, you'll have to destroy a usb cable and need celotape)
-Take the battery out of the phone, we're going to charge this manually.
-Cut a usb coord at the other end of where you'd plug it into a pc. (the usb female or microusb side) I used a small usb extension coord.
-Strip back the wire so you have about a centimeter of exposed wire on the red and black wires. If you have any other additional wires/exposed wire, ignore them, you can lookup what these wires are for if you're interested.
-Celotape the exposed red wire to the + shown on the battery and the black exposed wire to the - shown on the battery. Just make sure these two don't touch, it's easy enough by twisting the exposed wire to make it stick together.
-Wait 1 hr.
-Detach the charging wires and put in phone, push the stock firmware through "RSD Lite" with the firmware file named "6.7.2_EDEM-18-SEARET_cfc.xml", or any other, this is a jellybean release.
-Have another go to flash, just by making sure you start with 100% battery life.
Method 2: Make a Motorola factory cable, (warning, you'll have to destroy a micro usb to usb cable)
-For some reason many Motorola phone's power routing is controlled by the OS, without a working one installed, it cannot charge. However, the device was required to be flashed without a battery at the factory, this exploits that method and lets you power your phone through the coord to fix it.
-Cut the usb coord in half, separate the wires, and make the #1 wire attach to the #4 wire in a micro usb arrangement image. As I don't have 10 posts, I can't post links.
-I advise you to use the first method, and this as a last means for various reasons. Plus you can reuse the first method for other things in the future.
obsidianwings said:
I was trying to update to the newest version of MIUI, decided to do a clean install as I have been having some problems lately.
So wiped the phone in BMM recovery and installed the zip for MIUI and GAPPs, but then my BMM removed itself (it did tell me it was doing this, but following the instructions to get it to stay didn't work, and it didn't say why it was doing this).
So now I am stuck with stock recovery, I still have the zips for MIUI and GAPPs on the sd card, but no ROM installed. Without the ROM installed I can't boot to install custom recovery, and without custom recovery I can't install the ROM, so I am kind of stuck here.
Is there a way to install either a custom ROM or recovery from the stock recovery? It doesn't have to be BMM, I originally had that as I was trying different ROMs, but I have decided to stick with MIUI now.
Thanks in advance for any help.
Click to expand...
Click to collapse
First of all, you're not supposed to flash GApps with MIUI. Bad combination.
Second, if you notice the "Removal of BMM" after the ROM installation is over, you have to reboot, go to recovery, system keeper, and press Install BMM.
Anyways, your only solution may be to flash an SBF in fastboot using a fastboot cable, or to see if you could boot up the phone somehow or get it in ADB.
Good luck!
I know I am very late responding, but just wanted to say thanks to everyone for trying to help. By the time these posts were posted I had thrown my phone away, so didn't come on here for quite a while, hence not seeing the replies till now.
I did actually try manually charging the battery as I found the instructions on google, but unfortunately it didn't work. I didn't come across the factory cable idea though, that's interesting.
I had no idea you weren't supposed to install gapps with MIUI, I had had it working for a long time like that. I had thought it said that in the original thread where I got the MIUI rom from, but maybe I was just installing gapps out of habit. Thanks for that though, as I might get MIUI in the future.
As far as pressing "install BMM" in the recovery goes, I did that several times (that's what I meant by following the instructions to get it to stay in OP) but it just wouldn't stick. I figured there was only so long I could sit in recovery wasting battery trying to get BMM to stick so thought I would go ahead and reboot and work on trying to fix things from there
Anyway I appreciate you both trying to help, but I ended up throwing the phone away the day or two after my last post so I didn't see these till now when I logged on to talk about the new phone I just got.
I just went and took a look at the MIUI for atrix 2 thread, and it does say that you can optionally install gapps, so I guess that's why I did.
Related
I found 2 firmware versions on the forum that are dated before the official launch of the phone, an April one, LGP920-V08i-APR25-2011 (which I also have), and a May one, P920-V08j-MAY-03-2011. Some people reported being able to update to other ROMs by installing CWM, but all of them (if I read correctly) had the May ROM initially. Was anyone with the April version able to get a new firmware without the bricking or non-charging battery issues, or are we all who have these prototype phones doomed? I've read the O3D section for a full day, and I'm too terrified to try flashing or installing CWM, even though as an LG GT540 user I've swapped ROMs and unbricked my phone too many times to count.
sandulea said:
I found 2 firmware versions on the forum that are dated before the official launch of the phone, an April one, LGP920-V08i-APR25-2011 (which I also have), and a May one, P920-V08j-MAY-03-2011. Some people reported being able to update to other ROMs by installing CWM, but all of them (if I read correctly) had the May ROM initially. Was anyone with the April version able to get a new firmware without the bricking or non-charging battery issues, or are we all who have these prototype phones doomed? I've read the O3D section for a full day, and I'm too terrified to try flashing or installing CWM, even though as an LG GT540 user I've swapped ROMs and unbricked my phone too many times to count.
Click to expand...
Click to collapse
CWM is your friend.... try and install something after you have made a backup and if all goes wrong just restore your backup...
http://forum.xda-developers.com/showthread.php?t=1202022
Clockwork was my first idea as well, but its installation also causes problems, mainly with the April ROMs.
sandulea said:
http://forum.xda-developers.com/showthread.php?t=1202022
Clockwork was my first idea as well, but its installation also causes problems, mainly with the April ROMs.
Click to expand...
Click to collapse
you dload lg flash tool. shut the phone down. remove battery. connect it pressing vol-up then chose emergency update from menu.it will ask you your IMEI s/n and phone model. insert IMEI without - in between numbers. at 50% it will get stuck saying connection with phone was lost. dsiconect it without pressing anything insett battery and reconnect by pressing vol-up. press retry and wait. it should get you latest lg firmware. and if anything goes wrong you take it back to lg *****ing about how their software messed up your phone.
ps I only said remove battery before starting the process is cause mine had problems if the battery was on when i inserted the IMEI. it was not recognised.
I think I'll have a few more gray hairs after tonight... I went ahead and installed Rom Manager, flashed CWM, and, as I expected, after reboot it would only boot in Clockwork Recovery mode. I started to get really nervous. I then made a backup of the original April v08i ROM (not entirely clean, unfortunately), then I flashed v10B as written here: http://forum.xda-developers.com/showthread.php?t=1186460 . I wiped data, cache and nv dynamic partition, rebooted and it booted into Android! Now I expected it to not charge, but after 5-10 minutes the battery went from 63 to 73 percent (!!!).
I really hope it works out eventually. I'll take the phone off the charger once it's full, then reboot, play some 3d games to bring down the battery and charge it again. If no problems appear, I think I'll wait patiently for the official Gingerbread and Ice Cream Sandwich and stay out of custom ROM trouble.
EDIT: v10b, SIM and SD card in, 2 reboots later, and it's still able to charge, so I guess it's all fine. The battery appears to last longer (v08i drained out fully in a day in moderate use), 3D videos look better, 3d filming isn't as dark, but still a little dark, and surprisingly it feels a little slower, mostly around the launcher. However, I feel like I really dodged the bullet, because I installed CWM thinking I'll be taking my phone to an LG service center on Monday. OTA updating still doesn't work (same auth error as on v08i), so I'll have to update to 2.3 (and 4 if we'll ever have) some other way. But I'll cross that bridge when I get to it, and as far as I know I won't be the only one in this situation.
Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.
My 959V is rooted, had plenty of roms,ect over the last 3 years decided to do Gremlin remover and update it...,
Couple days ago upgraded to the "909" download of CM11,4.4.4, but every site I get it from gives me 908 (even though they all say 909) (last 3 digits of download version). The 908 will not recognize on my Win 7 laptop, but was fine up to now with previous cm11 same phone..
I have used the same cable for the last year for both my Galaxy and 2 Sidekicks phones, data and charging, now the Galaxy only charges, Windows detects but wont recognize, does on the sk4g's
Also (908) will not allow me to paste into sys/media with a " read only issue", although up to now swapped 15 different bootani without problems. Tried 3 different root file managers,same outcome.
Is the driver for the phone firmware windows looks for(on the phone itself) replaceable from sdcard? Im guessing its a bootloader issue and the 908 is the one not to of put on my phone.
Whats the probability I am getting the 909 but the 908 will not allow it to surpass it. Goes through the whole flash and on reboot I have to reenter emails,playstore apps,ect, but on 908 still in settings.
I can/ have been able to swap 1 rom via twrp and sdcard on 908 ( to slimkat4.4.4 and back to 909, but comes up 908) any other roms error before flash(and slimkat does not recognize on usb either).
is it a Kernel fix, and can it be flashed via sdcard? Bootloader via sdcard? Bad usb port? Does charge, and the drivers/ cable verified.
Thank you for any help, been 3 days now, redone my laptops (2) from scratch, everything ,c++,java,netframework,samsung,zadig 2.0, and more.
DId you do a clean upgrade (did a factory reset) before you installed CM11? If you didn't, go into TWRP and do a full backup (/system, /data) and do a factory reset, then boot up the phone and see if your computer will recognize it.
FBis251 said:
DId you do a clean upgrade (did a factory reset) before you installed CM11? If you didn't, go into TWRP and do a full backup (/system, /data) and do a factory reset, then boot up the phone and see if your computer will recognize it.
Click to expand...
Click to collapse
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Floridasun said:
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Click to expand...
Click to collapse
I didnt do a backup, if thats an issue , can I backup 2nd motherboard and apply to the first?
Floridasun said:
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Click to expand...
Click to collapse
You can flash new kernels via recovery but it sounds like your issues are bigger than that. The fact that the 2nd motherboard is recognized via USB but not the 1st suggests that there's some kind of hardware issue. The drivers on your computer are working fine since the 2nd mobo is recognized, and so is your USB cable.
Why not just keep using your 2nd mobo? Is there something wrong with the 1st?
FBis251 said:
You can flash new kernels via recovery but it sounds like your issues are bigger than that. The fact that the 2nd motherboard is recognized via USB but not the 1st suggests that there's some kind of hardware issue. The drivers on your computer are working fine since the 2nd mobo is recognized, and so is your USB cable.
Why not just keep using your 2nd mobo? Is there something wrong with the 1st?
Click to expand...
Click to collapse
O.K., so Ive been playing with the second mobo just to test different angles.
1) E.S. File manager is the culprit, swapped out for a paid app Ive used with Sidekick 4g, Root Explorer, and boot ani. goes fine, on both mobos.
2) The latest gapps (cm 11 w/ gaps 4.4.x) was giving me a "Google servers cannot be reached" error on both mobos, used the gapps for cm 10.1 (jb 4.3) and all is working, both mobos.
3) Was reading that possibly the adb driver is in the kernel, and thats what windows is looking for? Ive tried but can only sd card flash at this point so, giving up. I can bluetooth,wifi share or email files to myself if need be. Im guessing its a hardware issue beings that the 2nd mobo was reflashed identical to to the first. (with exception of one click 2.3.6,and w/a twist oc/uv on the 2nd),1st one will not downgrade at all below 4.4.4 by sd, I was trying to ics a rom guessing the foundation might overwrite any missing stuff then upgrade back to 4.4.4.
One post mentioned that the mtd/bml cross flash is a no-no, could that mess up usb driver identity on the phones side?
Not a big deal, both phones/ roms are working great and have no issues (except 1 doesnt connect to a computer for file transfer). Thank you for your help.
Little early to ask but are you going to be in this forum long enough for lollipop to be ported? I would send you this phone for devving if you think you can get it to transfer files. Also need to get a lcd/digitizer, i have the rest of the phone.
Also, the phone was working fine up to about a month ago, it was recognized by the computer, only difference I made was trying apps, off playstore, five fingers for ebay,different weather apps for widgets,silver/gold prices apps. Thats when it started not recognizing.
I was getting the same error about the google servers, then I tried a earlier version of gapps. Connects now.
Floridasun said:
Little early to ask but are you going to be in this forum long enough for lollipop to be ported? I would send you this phone for devving if you think you can get it to transfer files. Also need to get a lcd/digitizer, i have the rest of the phone.
Click to expand...
Click to collapse
I have no plans to try a Lollipop port, this phone is almost 4 years old now. You might be better off sending the phone to @bhundven since I recently got two dev phones donated to me.
As far as the phone itself goes, the phone should be recognized even if there is no driver for it installed on your computer. You can use this software to verify that
http://www.nirsoft.net/utils/usb_devices_view.html
I don't believe you can even edit anything on the phone to make the USB device not be recognized when plugged in short of bricking your phone, so if there isn't even a USB connection being made, as I mentioned before, it looks like a hardware issue is causing your problems.
In that case, it'll be hard to flash anything without going through a lot of hassle since all the reliable recovery methods we have need that you are able to use your USB port on the phone.
EDIT
If you do still have TWRP available on the phone, flashing any ROM will reflash a kernel, but be careful because the recovery is tied to the kernel and some ROMs have a non-working recovery, so if you happen to flash some of these you'll be stuck with a nice paperweight . The latest CM11 I have posted does have a working kernel/recovery but I still don't think it'll fix your issue.
FBis251 said:
I have no plans to try a Lollipop port, this phone is almost 4 years old now. You might be better off sending the phone to @bhundven since I recently got two dev phones donated to me.
Click to expand...
Click to collapse
I'm currently looking into it, as well as fixing some issues with cm11. I have an SGS4G, so no need to send a phone.
Not just is it a 4 year old phone, but I am not sure how many people even use this as a daily driver anymore.
bhundven said:
I'm currently looking into it, as well as fixing some issues with cm11. I have an SGS4G, so no need to send a phone.
Not just is it a 4 year old phone, but I am not sure how many people even use this as a daily driver anymore.
Click to expand...
Click to collapse
I still use two of them. Great little phones really. I see no need or use for 5.0 I think running this CM11 from you guys is about the end of the road for these phones. A great ride indeed. Ill be sticking around regardless just to see what happens. Thanks guys☺
Hello. This looks like the place I can get the best help.
Got a Xiaomi Mi5 last week - cheap and very cheerful. Having read online about possible fake roms and bloatware I thought the safest option would be to load the official stable rom to be safe.
Attempt 1
Following the MIUI guidance I downloaded the ROM, copied it to my phone in Windows explorer and then used the MIUI updater tool within the phone to load the new ROM.
http://en.miui.com/a-232.html
Everything went swimmingly for a couple of hours, but then the phone began crashing.
Attempt 2
By this stage I realised the above method was no longer available to me. So I got unlocking privalidges, unlocked my phone. Then, using MiFlash I flashed the latest ROM to the phone. Now the crashing problems happen within about a minute. It actually froze the screen first time round so I did it again.
Added fun issue - left my phone on overnight to charge. And it had stopped charging at 58%.
Attempt 3
Downloaded the EU MIUI Rom. Accessed TWRP in my phone and tried to use it to wipe and install. Not sure the wipes were fully effective - got a lot of red writing. And when I went to install the new ROM the internal storage was 0MB.
Had a look at guidance, and I forget what I did, but was finally able to see the zip file on my phone through TWRP. I got the "7" error. Have read how to fix this but seems too risky considering whats gone before.
Desired solution
I would just like any ROM on my phone which works. Don't really care which, I have followed each guide religiously. It may well just be a faulty phone but I don't want to send it back to China without ruling out the problem being me screwing with the software. Especially as I assume i've technically voided warranty... (I can reload Global Developer and relock it though so have hidden it pretty well. Only difference I can tell is that I now get a menu in recovery mode when before I got instruction to go to PCsuite).
Also - I seem to remember there originally being a downloaded_rom file in the internal memory which is no longer there. If im sending it back do I need to recreate one to hide my activity?
Appreciate any advice.
Moley1985 said:
Hello. This looks like the place I can get the best help.
Got a Xiaomi Mi5 last week - cheap and very cheerful. Having read online about possible fake roms and bloatware I thought the safest option would be to load the official stable rom to be safe.
Attempt 1
Following the MIUI guidance I downloaded the ROM, copied it to my phone in Windows explorer and then used the MIUI updater tool within the phone to load the new ROM.
http://en.miui.com/a-232.html
Everything went swimmingly for a couple of hours, but then the phone began crashing.
Attempt 2
By this stage I realised the above method was no longer available to me. So I got unlocking privalidges, unlocked my phone. Then, using MiFlash I flashed the latest ROM to the phone. Now the crashing problems happen within about a minute. It actually froze the screen first time round so I did it again.
Added fun issue - left my phone on overnight to charge. And it had stopped charging at 58%.
Attempt 3
Downloaded the EU MIUI Rom. Accessed TWRP in my phone and tried to use it to wipe and install. Not sure the wipes were fully effective - got a lot of red writing. And when I went to install the new ROM the internal storage was 0MB.
Had a look at guidance, and I forget what I did, but was finally able to see the zip file on my phone through TWRP. I got the "7" error. Have read how to fix this but seems too risky considering whats gone before.
Desired solution
I would just like any ROM on my phone which works. Don't really care which, I have followed each guide religiously. It may well just be a faulty phone but I don't want to send it back to China without ruling out the problem being me screwing with the software. Especially as I assume i've technically voided warranty... (I can reload Global Developer and relock it though so have hidden it pretty well. Only difference I can tell is that I now get a menu in recovery mode when before I got instruction to go to PCsuite).
Also - I seem to remember there originally being a downloaded_rom file in the internal memory which is no longer there. If im sending it back do I need to recreate one to hide my activity?
Appreciate any advice.
Click to expand...
Click to collapse
Greetings and welcome to assist. Xiaomi phones are encrypted by default so you need to wipe your phone in fastboot to access your storage again and you also need to flash latest su zip to disable dm verity. That should clear you internal memory issues and allow you to flash a zip through twrp
Good Luck
Sawdoctor
Cant flash twrp nor the patched magisk boot img to both slot a and b.
Bootloader is unlocked.
Flashing scripts via .bat files for stock zips of both android 10 and 12 results in "FAILED (remote: Partition product not found)" or "FAILED (remote: variable not found)" respectively.
I have no recovery.
When I had twrp, I've made the mistake of wiping my whole android 12 data, storage, and system and flashing an android 10 rom without reading up of the separate a and b boot slots nor the effects of my actions leading to bootlooping. (I've done with this other devices before with no problems). This in turn wiped the twrp recovery I had flashed and left me only fastboot commands and a twrp version up to 3.3 and 3.2 with no hope of getting usb otg to work as it was only available with the later versions of twrp and since I and now technically on an android 10 bootloader, any attempt at that time to flash twrp 3.6 was met with a (remote: Error calling AvbLoadAndVerifyBootImages Load Error) or some kind of other error I have no logs for. Now I cant even tetherboot to twrp 3.2 nor 3.3 and I get that error regardless.
[Boots to bootloader no matter what. Shows as UFS:Micron, Error reason - reboot bootloader - bootloader version is b1c1-0-4-7617406]
I believe I can get access to internal storage to flash these updates once I get a recovery tethered from the bootloader. I do not know if its possible to boot to fastbootd or whatever its called (used for write permissions/sideload update zips) even if I hadn't gotten into this predicament. I will be buying another Pixel 3 in the meantime as I have money to burn and like to hurt myself financially, and emotionally to get to my goal with this device. ( Didn't buy another one, I was committed to the cause!)
I am not a noob nor a pro, but somewhere in between. My biggest point of failure is not reading up on how the partitions are set up and the various issues others had when flashing android 10 and 11 roms. Any suggestions other than "uPdAtE tHe fAsTbOoT aNd AdB dRiVeRs" are not welcomed. Thank you. I will update once I find a soluton to my problem Which I Will.
Again, my main concern right now is getting tethered twrp to work again and need suggestions. I have older versions of platform tools and the latest so please non of those comments I see on literally every other thread.
Edit: I didn't mention this before, but I did have the ability yo sideload when I had twrp at the time before crapping everything out the window, but nothing would work and gave up. Just wanted to add if anyone was wondering.
First update, I used the propriatary "Tool All In One Tool" and I was able to boot to fastbootd, and wipe my data and storage, while updating my stock zip to android 12. Now I can tetherboot twrp 3.6.1_11-0 with the option for usb otg, wish me luck boys. I'm in.
Second update. Still stuck on first update, but weighing my options in the meantime. I flashed twrp via the flash current twrp option, but when I boot to it, touch is disabled so thats great... I can fast boot to only the twrp versions after 3.6+, so not so bad. I have no os installed, but I will try my hand again at that tool all in one tool again. I'll update tomorrow if anything comes of it.
3rd update. FROM THE BRINK OF DEATH!!! WHOOOOOOOOOO!!!!! I got the pixeldust rom flashed and working like a BOSS!!!!! You won't believe the 2 days I've had trying to get this thing to work. All in all 1 out of my 3 flashdrives finally worked with otg. I had a windows recovery drive premade on it so I just copied and pasted the files there without a hitch! Thank you Google for having to make me miss work and actually do research to get this thing working again! Thank you for the guys at Tool All In One Tool for making this recovery possible, I will shout out your thread. If anyone who's in a similar situation needs any help from me or any info, I'll be glad to help. This will be the second to last update. I can also make phone calls and use data so Pixel Dust rom is good to go if that was one of your concerns. See ya!
Final update, I got crdroid flashed with root and safetynet passed, I just found out that google Pay was imbedded in gapps so now I don't need the pay app anymore to do transactions! My banking app also works, got vanced finally installed (couldn't do it on regular stock ROM) some glitches with the ROM here and there but no worries. For who ever reads this. There's hope. I fd up as bad as you can get shy of a hard brick. I still don't know too much but learned near twice as much as I knew just a few days ago. If you need help just DM me and I'll work my hardest to bring the light. This phone is absolutely amazing and on god wished google was a better company to praise. I have more plans for these phones and hope more Roms come out to support it.
I have one question however, how do I make a backup of my system/system_ext partitions? I can make a back up of everything else but that with these two Roms... I have a backup of it with my stock ROM, but it resumed to mount when I used otg... Didn't try internal yet but I'll assume the same, is it a glitch with current twrp?