Related
Hi all,
I have Gionee elife s5.5 and it had english rom (android 4.2.2) with google play installed. The problem was it kept freezing a couple of times a day, so I tried to reinstall the only official rom I could find (CBT5701A01_A_T2898) with flash tool. After the installation, it got stuck in the boot loop.
I tried:
- entering the recovery mode and cleaning the cache
- entering the recovery mode and factory reset/wipe
- reinstall rom with flash tool with update option
- reinstall rom with flash tool with download option
- reinstall rom with flash tool with download and format option
- reinstall rom with flash tool v3.1344.0.212 and v5.1352.01
So far, no luck. The only answer I can think of is that this rom is not for my phone version. Anybody has any idea what can I do? Or does anybody have some other rom I could try to install?
Thanks in advance.
tchs said:
Hi all,
I have Gionee elife s5.5 and it had english rom (android 4.2.2) with google play installed. The problem was it kept freezing a couple of times a day, so I tried to reinstall the only official rom I could find (CBT5701A01_A_T2898) with flash tool. After the installation, it got stuck in the boot loop.
I tried:
- entering the recovery mode and cleaning the cache
- entering the recovery mode and factory reset/wipe
- reinstall rom with flash tool with update option
- reinstall rom with flash tool with download option
- reinstall rom with flash tool with download and format option
- reinstall rom with flash tool v3.1344.0.212 and v5.1352.01
So far, no luck. The only answer I can think of is that this rom is not for my phone version. Anybody has any idea what can I do? Or does anybody have some other rom I could try to install?
Thanks in advance.
Click to expand...
Click to collapse
Where did you get the phone? Try looking here, translate it using Google.
http://www.mgyun.com/
I bought it on ebay from China. Thanks for the link but no luck. I've downloaded the new rom and the romaster program (I'm guessing I should use it for the installation) but the program is not detecting that the phone is connected via usb. Same thing with vroot.
Since this rom is in another format, I was thinking maybe I could install it via adb option in recovery mode but I'm getting 'device not found' message when I try to start adb shell.
tchs said:
I bought it on ebay from China. Thanks for the link but no luck. I've downloaded the new rom and the romaster program (I'm guessing I should use it for the installation) but the program is not detecting that the phone is connected via usb. Same thing with vroot.
Since this rom is in another format, I was thinking maybe I could install it via adb option in recovery mode but I'm getting 'device not found' message when I try to start adb shell.
Click to expand...
Click to collapse
Have you installed the drivers for the phone?http://gionee.co.in/portfolio/elife-s5-5/#t4
---------- Post added at 03:12 AM ---------- Previous post was at 02:30 AM ----------
Try here, you need to register.
http://www.yougerom.com/bbs/forum.php?mod=viewthread&tid=265
Yes, I installed usb and phone drivers. I also installed adb driver (at least adb driver installer says it is installed as android composite adb interface) and yet when I try adb shell, deamon starts ok but I keep getting the message that the device is not found.
The rom from your link is the same one I already have, but thanks anyway.
All this is very frustrating. Seems like everywhere I go, I hit the wall:
- if the phone has sdcard I could try install rom from there, but it doesn't
- if adb connection works I could try that, but it doesn't
- if romaster detects the phone I could try install it from there, but it doesn't
- sp flash tool is working but I could find only one rom version and it's not working
You did the brushing before installing the flash've used Flashtool?
Have you looked in setting pc, peripherals, if you have something in conflict, if you do not have the yellow exclamation mark?
Also I have just bought this phone, by Liaow, who did the root and installed the Playstore. Now my phone is still stuck in Hong Kong and I do not know when it will arrive in Italy.
How did you like the phone, the battery life, becomes very hot since the minimum thickness?
I don't know what do you mean by 'brushing' so the answer is probably not?
Everything looks ok in pc's control panel, no conflicts or unrecognized devices etc. It's win7 64bit.
I was thinking about buying it via Liaow but in the end I used ebay. It took 3 weeks to arrive, and I paid for DHL express delivery (!) Isn't EU wonderful thing...
I really liked the phone (in the brief time it was working). Display is great, it's fast and the battery would last for a day without a problem. The build is very solid. I wasn't playing any games on it or use any apps that would use cpu extensively, but in normal operational time I didn't notice any significant heating. I even liked the Amigo skin. It has some nice features and was working very fast. The only problem was it kept freezing couple of times a day, usually after long times of inactivity which led me to believe it has some sort of problem with power saving functions in android (or amigo). Oh one other thing: it doesn't have notification led. I miss that.
If you don't get your phone, I know where you can get one very, very cheap. It's stuck in the boot loop, but still...
Brushing think it is to do a full wipe before doing the flash with Flashtool.
When you receive your phone, you've got an update OTA of 98 mb?
Thank you but the phone I have already paid and are waiting for his arrival.
I hope we put less than three weeks since I also took DHL.
In Italy we have a beautiful community where there are developers who work here in Xda, who are fond of Chinese mobile phones and in particular there is a person who develops rom alternatives.
So I guess I would be able to help me if I had the same problem, but I hope I do not have any problems.
You say you had blocks of hibernation in power saving mode enabled, then maybe in normal mode just fine.
I do not usually use the mode energy in any phone I've had.
I prefer to charge the battery when needed.
First I tried only update, after that I tried full wipe.
I did try to disable every power saving mode I could find, but the phone still kept freezing. Although, there are some options that are useful, like limiting cpu for more energy and lower temperature.
I didn't get OTA update, but the seller told me that they had to open the box to install english rom version with google play. Maybe they also installed this update.
got another elife threat here http://forum.xda-developers.com/showthread.php?t=2699708
Here's the quick update: after I manually edited adb_usb.ini file, adb sideload works now. But...none of the rom's I have can be installed with adb (I get 'installation failed' message after transfer).
So, what I need is:
- rom that can be installed via adb sideload
or
- rom that can be installed via flashtool with scatter file (after extensive search of the web, the only rom I could find on several places is the one made 11-03-2014 and this one is not working for me)
Any help would be greatly appreciated.
tchs said:
Here's the quick update: after I manually edited adb_usb.ini file, adb sideload works now. But...none of the rom's I have can be installed with adb (I get 'installation failed' message after transfer).
So, what I need is:
- rom that can be installed via adb sideload
or
- rom that can be installed via flashtool with scatter file (after extensive search of the web, the only rom I could find on several places is the one made 11-03-2014 and this one is not working for me)
Any help would be greatly appreciated.
Click to expand...
Click to collapse
http://bbs.amigo.cn/thread-758-1-1.html
XPAction said:
http://bbs.amigo.cn/thread-758-1-1.html
Click to expand...
Click to collapse
Thanks but I already tried that. This only works with Romaster app and it doesn't recognize my phone being connected while on boot loop or recovery mode.
Even my phone is stuck on boot, can anyone help me
Tired of searching everywhere cant find it anywhere, can anyone please share a link from where I can download rom for my gionee elife S5.5 Indian version, my phone was working fine until I installed beats audio It asked to reboot and the then it never rebooted, stuck on gionee boot animation, I also flashed the Chinese rom but it doesn't support, phone was booting up but the rom is too lagging and unstable. I don't want to go to the service center cause my phone is rooted and warranty will be voided, I just bought it two days back. Is CWM available for this phone cause I couldn't find that too, I'd be more than grateful If anyone can help me out I just need the rom file (Indian version), thanks a million !!!!
i also tried to install beat audios on my gionee s5.5 ... and now it is not statting my phone get stucks at boot animation logo "gionee smatyphone"
Here are some good news people: needrom.com site finally released new rom version and it can be installed via adb sideload. It is CH/EN version and even when you switch it to English, some things still stay in Chinese but hey - at least it's not in boot loop anymore and now you have more options for rom installation.
Thanks dev, was so sick of this phone and its features, especially free mobile heater(owen) + worst sound ever + lots of lags, even flappy bird lags on this phone though I had optimised the cpu performance using set cpu to its max by creating a profile to play flappy bird, mediatek chipset sucks happy after entering the snapdragon world, just bought M8 yesterday and believe me this is the best phone till date though the ram is 2gb the processor is a the beast and there's no comparison to it and when it comes to the sound no one can beat htc, the looks it feels so ****n premium, the touch is like butter smooth, loving it!! Thanks
Sent from my HTC One_M8 using XDA Free mobile app
how to install rom from needrom via adb shell.?? can anyone explain?
FirmwareFile
https://firmwarefile.com/gionee-s5-5 , i've used T8881 version , and it was good
Here you go:
https://1drv.ms/u/s!AshkuG2cY1T0xPZArSsy6iO1e_UnPw
This is a zip file with all the tools and files you need and instructions on how to use them.
What it covers:
Restoring bricked device (as long as download mode still works)
Unlocking bootloader (firmware dependent)
Rooting (any firmware)
Installing a custom recovery (any firmware)
Installing a custom ROM (any firmware)
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
robles4242 said:
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
Click to expand...
Click to collapse
Did you read my guide? You can't flash TWRP unless you successfully unlocked your bootloader with Casual, otherwise you are limited to SafeStrap. Also you can't restore with Kies, you have to use Odin and the files I've included to restore.
yambag said:
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
Click to expand...
Click to collapse
Nice to see people still looking for something like this, so my guide wasn't for nothing!
I was geeked to see this!! but then i got "This item might not exist or is no longer available"
I take it back.. i let it sit on the "failed" page for like 2 min, and randomly it popped up with a download!
Well the auto bootloader didn't work, so now i'm at the root section. However i'm getting an error where ADB isn't detecting my phone. USB debug is on, and i'm definitely in media mode and not installer. The phone shows up in windows and looks good, but adb doesnt detect. I opened command prompt and ran adb /? and found adb devices -l, and it reports "list of devices" and theres nothing in the list. I can't imagine why it's not seeing it. I tried turning on and off debug mode, switching from camera mode to media, changing usb ports. still nothing comes up, but windows sees it fine. grrrr
*edit, well since we can't delete posts i'll leave this here, because i have to. But what i did was re-open the "no you verizon" and it showed DISCONNECTED also. I changed usb ports like 3 times, turned usb debug on and off, changed from installer mode, to camera, to media mode, restarted the phone and the computer multiple times.. and then it just all of a sudden was detected again. So i went with it and it seems to have worked.
-it took 3 times to actually work, you noted it may take multiples, and it sure did. I ran it through the command prompt so i could read the text, and it took 5 times longer and reported much more stuff when it actually worked.
-final edit: if you can't unlock your bootloader, you're still stuck with ditto or alliance from 2014, and lots of apps won't update on android that old. So if you thought this guide was some holy grail, it is not. But still useful if you need the assist, so thanks to the author.
Hi, total noob here, I just bought Verizon note 2 at a yard sale but there is a pin I don't know. When I went to do a factory reset it booted into TWRP, so I am assuming is rooted. Do I need to be able to get into the phone to use your tools? I know nothing about TWRP. I would like to install a newer Android version and unlock it so I can use TMobile. Thanks
Something wrong...
when i try to load this file from the packages folder i get an error message:
"md5 error! Binary is invalid"
none of the other three works for me. they all come back ailed.
any suggestions?
awesome! thanks for posting this, just found my old note 2 and want to get it up and running again for the kids.
Kudos!
Used this to get my Note 2 up and going again temporarily until the Pixel 4a release...
NOTE: I had strange issues with Odin on my modern X570 board (USB 3.2 Gen 2) where I did not receive any errors, yet the process would randomly seem to time out. Sometimes I'd get stuck at flashing boot.img, sometimes it would hang up at the start, once I got to flashing system.img and it seemed to hang....
Used an older PC circa 2013, no issues! Not the first time I've had issues with this newer motherboard and older USB flashing interfaces; had the same issue on my Note 8 (RIP) as well.
excited to try this.
I'm on some rooted 4.4.2 stock-looking rom. Recovery doesn't look custom.
Hoping to be able to install a working Oreo or Pie ROM
great post, bought a couple of these for almost nothing and am having fun playing with them. sadly they are both 4.4.2 but its great fun anyway.
SilentNightx said:
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Click to expand...
Click to collapse
Thank you for sharing. Always difficult to find those tools after a few years!!!
Hi guys,
Hope it's ok if I start this thread, I just wanted to give new users some feedback before/ after unlocking and flashing an India ROM on my sealed China ROM K20 Pro (8/256). It might be useful to some, or maybe even help others. Thanks a lot to Robbo.5000, Madsponge and Hursty UK (hope I got it right?) among others for their help and advice.
- [BUYING PROCESS] My trip with the K20 Pro started here: https://forum.xda-developers.com/k2...ice-to-buy-t3939616/post79918346#post79918346 (about 18 days to get it from China during high season, not too bad I guess). (FYI, the real Global version will come out in Europe in a few weeks but the 8/256 won't be available here.)
- [UNLOCKING PROCESS] I then started the "infamous" unlocking process which triggered the even more "infamous" unlocking wait time. Why did Xiaomi choose to do that? Pretty strange if you ask me. Why should you wait 5 days or more? Anyways, in my case it was almost 6 days. That part of the process went smoothly (I run a kinda old Windows 7 PC). I rebooted the phone and it was unlocked indeed. Then started the stressful process: flashing a +400 euros phone without knowing if it would actually work. Kinda reminded of the time when we "backuped" PS1 (PSX) games, haha.
- [FLASHING PROCESS] I used the official MiFlash tool, with the official India ROM (fastboot file, .TGZ extension). First problem : MiFlash couldn't install the drivers because a /log/ folder was missing, which I had to create manually (didn't see that mentioned on the forum, but might be my OS? Oh well). The rest was OK until I launched the flashing process and hit the "clean all" button (I carefully didn't choose the clean all and lock which would have bricked the phone).
>> Link to the official India ROM Fastboot .TGZ -> http://bigota.d.miui.com/V10.3.3.0....FKINXM_20190711.0000.00_9.0_in_a1c0a15dec.tgz
>> Link to the official MiFlash tool I used -> https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
>> Use the official Xiaomi USB-C cable - do not try another USB cable
>> Important reminder: please change the default option in the flashing tool and DO NOT choose "clean all and lock". Change it to "clean all" only (you don't want to lock it as you might brick it - see posts below about this)
- [STRESSFUL REBOOT] The flashing process ran for about 10 minutes, said "error: Not catch checkpoint (\$fastboot -s .*lock)". Needless to say I was very stressed out at that point, especially with the not cool red message "error" on the right of the tool, in the column "result". I thought the phone was bricked...but no, it just rebooted normally with the India ROM on it. Honestly I don't know what happened, if it was normal or something but I didn't see anyone mentioning this.
Some feedback post flash: everything is fine, the phone seems even faster than on China ROM but it might be just an impression. I do not like the POCO launcher at all, when you're used for 4 years with the classic MIUI launcher it's honestly a pain, I like to see all installed apps on the home and next screens. I had an issue with my Mi Cloud backup (home screen): Mi Cloud said there was no backup even though I did one just before flashing. The rest of the sync process (except home screen - maybe because of POCO launcher?) was fine though: pics, notes, calls, messages, etc. Too bad we're missing NFC but it feels good to be back on "Global" (was coming from a Mi 8 Global phone). Oh yeah, missing the multiple shots option from the China ROM (where you can choose the "best" shot), but it will come to Global one day I guess.
- [MI CLOUD BACKUPS] I can confirm the Mi Cloud home screen backup issue described above is indeed because of the POCO launcher: my previous backups didn't have it (Mi 8 Global, K20 Pro China) and so Mi Cloud couldn't restore from those backups. I now have a POCO launcher backup (daily in Mi Cloud) and I can restore from those. So keep that in mind: if you come from non POCO you won't be able to restore home screen, but same thing if you move from POCO to a non POCO launcher. If you're not familiar with those backups, it's very practical (usually...) when you change phone because you just have to restore it and you'll have all your icons, apps and stuff like before.
[UPDATE] As you might know, a European Global version will be released in a few weeks, let's see if it has the POCO launcher or not.
Thanks again all for the help and let me know if you have more feedback.
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
hippo2s said:
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
Click to expand...
Click to collapse
You need to fully unpack the ROM. It requires unzipping twice. You now need to extract everything from the tar file. After extracting the tar file you should have a folder with all the ROM image files and some .bat files. Point the Mi Flash Tool to this folder.
The phone needs to be booted into fastboot mode. The PC should recognise the phone automatically if it has all the correct drivers installed.
ive been using the indian rom for like 2-3 weeks now, my question is, does it support auto updater trough the updater? or we need to install back trough the mi flash tool
i failed multiple times to flash the global india rom before(using winzip to extract). and I tried again extract the files using winrar and it succeed. i'ved been using it almost 2 weeks now. the issue that i am facing is i cant use earphone mic on discord and whatsapp call. the rest is fine. for the updates, i get it from system app updater in settings.
OK - Managed to get the image folder recognised - the file path was too long - so i renamed it and moved it closer to where the miflash .exe was.
Now MiFlash is not detecting my device - when plugging in phone windows comes up with a 'USB device not recognised' message as well.
In Device Manager it says Unknown USB device (Invalid Configuration Descriptor) - I looked for Xiaomi usb drivers but Windows say i already have the best driver installed...
Any ideas?
hippo2s said:
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
Click to expand...
Click to collapse
I forgot to mention it, yes you do have to extract it (using WinRAR or similar) until you get an actual folder like Robbo.5000 said. I then renamed the rom's parent folder as "raphaelin" because another user mentioned we could have issues if the folder's name was too long.
About the USB connection i didnt change anything, i left it by default.
hippo2s said:
OK - Managed to get the image folder recognised - the file path was too long - so i renamed it and moved it closer to where the miflash .exe was.
Now MiFlash is not detecting my device - when plugging in phone windows comes up with a 'USB device not recognised' message as well.
In Device Manager it says Unknown USB device (Invalid Configuration Descriptor) - I looked for Xiaomi usb drivers but Windows say i already have the best driver installed...
Any ideas?
Click to expand...
Click to collapse
I'm guessing your phone is already in fastboot mode (with the little Mi cartoon guy)?
I installed ADB minimal, the MiFlash drivers but also ADB Lite drivers (mentioned in the big Madsponge thread where you can find the links). That might help.
In MiFlash when i hit Refresh it saw the phone as some ID like 1d23456 or something.
Just installed Qualcomm drivers - didn't help either...
set USB debugg mode - what was the USB connection type? if you remember - thanks in advance
piqiee said:
ive been using the indian rom for like 2-3 weeks now, my question is, does it support auto updater trough the updater? or we need to install back trough the mi flash tool
Click to expand...
Click to collapse
I dont think there is an update since 10.3.3.0 but i guess we'll find out with the next OTA update. I read somewhere an automatic update might lock the phone back (and brick it) so i disabled them for now, until we know more...
Of course Chinese OTA was fine on the China ROM.
hippo2s said:
Just installed Qualcomm drivers - didn't help either...
set USB debugg mode - what was the USB connection type? if you remember - thanks in advance
Click to expand...
Click to collapse
In fastboot mode you cant change it on the phone if i remember, and its set automatically in file transfer mode i think.
Yes I installed those drivers too. I might try a different laptop and usb cable tonight.
Thank you so far for your help.
FYI i used the USB cable shipped with the phone. As for the laptop, is its OS up to date? I installed the latest Windows update before the flashing process.
Hope its gonna work!
DontDamnMe said:
FYI i used the USB cable shipped with the phone. As for the laptop, is its OS up to date? I installed the latest Windows update before the flashing process.
Hope its gonna work!
Click to expand...
Click to collapse
I own the Indian variant, stock rom, bootloader unlocked and rooted. Widevine L1 is still present.
So, I am curious. When you flashed the Indian ROM, did your Widevine level changed from L3 to L1?
If you didn't check, if you don't mind, please install "DRM Info" from playstore and let me know!
I am trying to find whether the Widevine is implemented based on Stock ROM level or its just at device variant level. Thanks in advance!
theincognito said:
I own the Indian variant, stock rom, bootloader unlocked and rooted. Widevine L1 is still present.
So, I am curious. When you flashed the Indian ROM, did your Widevine level changed from L3 to L1?
If you didn't check, if you don't mind, please install "DRM Info" from playstore and let me know!
I am trying to find whether the Widevine is implemented based on Stock ROM level or its just at device variant level. Thanks in advance!
Click to expand...
Click to collapse
I just checked and it says I have L3. Honestly I don't really see a difference (if it's about Netflix HD or not), Netflix videos are still great quality.
DontDamnMe said:
I just checked and it says I have L3. Honestly I don't really see a difference (if it's about Netflix HD or not), Netflix videos are still great quality.
Click to expand...
Click to collapse
Thanks mate. Just one more thing. Could you play "Test Patterns" - S1:E1 video, zoomed out for 2 mins, in Netflix app?
It will initially show "960x540" (right top corner of the screen in zoomed out mode), but after 2 mins, does it change to "1280x720" or still stays at "960x540"??
Again, thanks in advance!
Ok it was the USB cable - device was detected on original USB cable.
Flashed - BUT i made a mistake and had it default to Clean all and Lock !!! ugh...
Flash went thru - but now i am in some thing called Redmi-Recovery 3.0. Red message say "This MIUI version can't be installed on this device."
I can still get into Fastboot and MiFlash can still detect the device - Upon trying to reflash again MiFlash gives error 'Erase Boot Error'
So i think i am F-ed....
Any advice, anyone?
I think its only "soft bricked". Another user had a similar issue and created a thread below. Experts here will be able to help you for sure. If its locked i believe you have to reinstall the China stock ROM.
About Netflix it stays on 960, so no HD i guess...
hippo2s said:
Ok it was the USB cable - device was detected on original USB cable.
Flashed - BUT i made a mistake and had it default to Clean all and Lock !!! ugh...
Flash went thru - but now i am in some thing called Redmi-Recovery 3.0. Red message say "This MIUI version can't be installed on this device."
I can still get into Fastboot and MiFlash can still detect the device - Upon trying to reflash again MiFlash gives error 'Erase Boot Error'
So i think i am F-ed....
Any advice, anyone?
Click to expand...
Click to collapse
Just download the china latest stock rom or china latest dev rom (recovery rom will be enough), no need of mi flash.
Then go to this link and follow the instructions. Since you can access the recovery, you are fine mate.
PS: Use the latest official Mi Assistant app from the MIUI site, not the one given in the link above. But the steps are the same.
Thanks guys I will try. Really worried that phone doesn’t shut down it keeps going into recovery (doesn’t power off) and charging doesn’t seem to work in all these conditions.
Will work quickly
---------- Post added at 12:15 PM ---------- Previous post was at 12:04 PM ----------
err... thats not the Mi PC Suite is it? when i google miphone assistant thats what comes up...
Err...not detecting my phone so the PC Suite can't find the device
This Oneplus X seems to be more difficult than my previous attempts for installing TWRP and custom ROM. I keep getting stuck and nothing returning once in fastboot and executing command "fastboot devices". I just keep getting "< waiting for device >" .
I think I have ADB installed right because while the Oneplus X is on and in normal mode (developer settings enabled with OEM unlocking and USB debugging enabled also) ADB connects. The USB drivers look to work fine because I can see the device (including SD card storage) and transfer files. in ADB and typing in ADB devices, I see the device.
When I run adb reboot bootloader and execute fastboot devices using command.com with administrator privilege, it just returns another prompt. It doens't show any device. I get the same results with Powershell with administrator privelge.
I'm already on my 2nd machine trying to do this although it's a windows 10 also just w/o updates for six months (was off and on the side of office). I had the same issues on my newer machine and thought it's the windows 10 machine I'm using. Researching the internet and here, I see others mention it though I didn't see any solution. I don't have a Linux machine (never really used it though had redhat installed eons ago somewhere). I guess I can do a refresh of my 2nd/older machine and not do any updates to see if that may help with any driver conflict though I don't see any indicators since adb can see the device. I thought trying to install TWRP via sideloader may work but I don't see tutorials and commands via that way.
Also I'm using ADB 1.4.3 in the 2nd windows machine. I had the Minimal ADB and Fastboot version on the other machine.
Anything else I can try?
P.S. The Onyx seems to be harder than putting android on my old HP touchpad! Putting a Tmobile rom on a AT&T Galaxy S4 and custom rom on a Oneplus 2 seemed much easier than the Onyx though unsure why. Onyx and the Oneplus 2 were comparable manufacturing years iirc.
On the 2nd machine, i did a windows 10 reset to basically refresh it (like a fresh install). I started over again and managed to get past the fastboot device problem and it's showing it now. I think the prior problem was the device and driver and even with a re-install, can't seem to get past it. The only difference I did with ADB install was not opting to install google drivers.
I got the bootloader unlocked and the recovery.img file done. Basically I'm following the direction from this page - https://www.technobuzz.net/root-oneplus-x-install-twrp-recovery/ - which seems to be aligned with most youtube and I think same as old pages here.
Now where I'm stuck is when executing "fastboot boot recovery.img" I get the failed (remote : dtb not found) and can't seem to find a solution to this one. Some sites say something about the partition?
Thoughts? hopefully this machine is not too old/dead for some comments/guidance unless I'm posting on the wrong section.
well to share back here and for closure.. looks like the recovery image i used on the site above must be for a different OOS. doing some further searches here and different terms and jumping to another thread from a search result thread (lol), i read that i needed a specific twrp for oos 3.1.4. (odd since recovery is supposed to be independent of ROM version, but that seemed to have work). guess persistence pays after all.
it really did heavily matter having the device recognized properly by windows 10. once i got past the blank fastboot device command execution, i got the another issue due to the phone not knowing how to boot into the recovery version i was trying to install, at least that's how another poster in another thread explained it. hence the right twrp had to be used for oos 3.1.4
Just got my Pixel 6, trying to get everything updated - after a bit of a battle and having to use the web flasher to rescue it, I'm almost there, but currently I've got A13 on one slot and A12 a the other (I uploaded the bootloader on the 12 side at least, so no risk of a hard brick). But every time I try to sideload the OTA, it hangs at 0-7%. Tried the other PC, same issue, different cable, same problem. Using a USB 2.0 hub lets it proceed, but at like... 1% every two minutes. Is there anything faster than this/any workaround for the USB 3.0 bug? I've tried on two different PCs, and reinstalled the Google USB drivers, to no avail.
I'm also totally new to the whole A/B partition thing - I have no idea when I'm flashing to slot A or slot B, apart from the fact that apparently sideload installs to the inactive slot. (Since I did get the new bootloader installed to the other slot at least, can I just switch slots and use the web flasher again? That worked fine for this slot.)
Edit: Sorry, bad phrasing in the title; issue is sideloading the OTA.
Edit 2: PixelFlasher flashes the whole factory image (with the patched boot image)? I thought it just flashed the boot image. Huh.
Jaitsu said:
Just got my Pixel 6, trying to get everything updated - after a bit of a battle and having to use the web flasher to rescue it, I'm almost there, but currently I've got A13 on one slot and A12 a the other (I uploaded the bootloader on the 12 side at least, so no risk of a hard brick). But every time I try to sideload the OTA, it hangs at 0-7%. Tried the other PC, same issue, different cable, same problem. Using a USB 2.0 hub lets it proceed, but at like... 1% every two minutes. Is there anything faster than this/any workaround for the USB 3.0 bug? I've tried on two different PCs, and reinstalled the Google USB drivers, to no avail.
I'm also totally new to the whole A/B partition thing - I have no idea when I'm flashing to slot A or slot B, apart from the fact that apparently sideload installs to the inactive slot. (Since I did get the new bootloader installed to the other slot at least, can I just switch slots and use the web flasher again? That worked fine for this slot.)
Edit: Sorry, bad phrasing in the title; issue is sideloading the OTA.
Edit 2: PixelFlasher flashes the whole factory image (with the patched boot image)? I thought it just flashed the boot image. Huh.
Click to expand...
Click to collapse
Try this - https://flash.android.com/welcome
Aks said:
Try this - https://flash.android.com/welcome
Click to expand...
Click to collapse
That did work for the current slot, yeah - that was how I ended up saving it after I ran into the "Your device is corrupt" error. That flashes it to the current slot, though, and I was trying to figure out how to flash it to the other so I'd have Android 13 on both, and was still a little nervous even after flashing the 13 bootloader without having the entire OTA on that slot. I ended up just sitting out the couple of hours getting the OTA to sideload over USB 2.0, hopefully from here on out I can just use the web flasher or PixelFlasher since I don't have to worry about bricking anymore.
EDIT: Found a fix for fastboot/sideload not working over USB 3! Stick this in a .reg file and run it (or, if you don't trust it, you can always do it by adding these values yourself (they're all REG_BINARY), the reg file's just faster.) After I made these changes I'm able to use at least fastboot over USB 3 with no issue, and MAGNITUDES faster - and I'd imagine it's the same case for sideloading, since I was running into the same issue. No apparent issues caused by doing this.
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100]
"osvc"=hex:00,00
"SkipContainerIdQuery"=hex:01,00,00,00
"SkipBOSDescriptorQuery"=hex:01,00,00,00