Related
***MOD EDIT***
THIS ROM ONLY WORKS ON 4.1.26. Please consider another ROM unless you know what you are doing.
History & IntroThe first version was done with 3 different batch files, it ended up being very hacky and even ended up bricking one phone because the cleanup script didn't properly work.
I have rebuilt it from the ground up as a shell script. The initial temp root and file push is done with a batch file, it then fires off the install script on the phone which reports back to the batch with helpful info about what it is doing and what to expect from the phone as it goes. You no longer have to accept any superuser requests either.
The new script has been used on tons of phones now, everything executed exactly as I expected it to. I really didn't want to post this until we had a stock firmware to restore to, after the first release I have been worried about you guys bricking your devices, but what the hell, here it is anyways.
Come chat with us!FeaturesWorks for rooted and non-rooted devices
Deodexed
Reboot Option
Reboot to Recovery option
Ad Blocking
Removed power options headerChangelogAdeo v0.2: (3/9/2011)
Added Unknown Sources checkbox
Added Preferred install location (internal, sdcard, let system decide)Adeo v0.1: (2/28/2011)
Reboot to Recovery option
Ad Blocking
Only remove app/framework Dalvik-Cache (fixes /data app issues)
Removed power options headerFour simple rulesDo NOT do a factory reset if something goes wrong(soft brick), you will lose adb access and have a pretty brick
Do NOT do this if you are not familiar with ADB, if you softbrick you need to use adb to fix it
DO NOT PULL THE BATTERY, EVER WHILE INSTALLING
BE PATIENTHow to Install
Read the four rules above
Read the four rules above, again
Read the four rules above, again, one more time to make sure you've got it
Download the installer (AdeoInstallerv0.1.7z, AdeoUpdaterv0.2.7z)
Hook up your phone via usb with ADB enabled
run INSTALL.bat from the unzipped files
sit back, relax, wait until it reboots (can take upto 5min, be patient!!)
Read the disclaimer below
Enjoy!
DisclaimerIf you brick your device, I cannot be held responsible. Simply restore with the stock SBF to get you phone working again.Video Walkthru
Nice! First basic rom How would someone restore back to stop if you cant do a factory reset? I know on the captivate I had a nice Odin flash to do that.
Thanks
A custom ROM?
I'm going to have to buy an Atrix!
EDIT: Bought it!
EDIT2: And Adeo'd it. All UI lag is gone! This is awesome!
I am running this in my Atrix now - I believe my phone was the 4th phone to have this install perfectly on with no issues. Designgears, you are the man, once again! Thank you for this!
PM sent DG. I cheated an caught link a few minutes early and wanted say thanks! This is running great with no issues and I'm loving the reboot option...
Installed on mine, worked flawlessly. Thanks!
connexion2005 said:
PM sent DG. I cheated an caught link a few minutes early and wanted say thanks! This is running great with no issues and I'm loving the reboot option...
Click to expand...
Click to collapse
Haha, I understand your PM now... you got my file before I posted this.
psufan5 said:
Nice! First basic rom How would someone restore back to stop if you cant do a factory reset? I know on the captivate I had a nice Odin flash to do that.
Thanks
Click to expand...
Click to collapse
the factory reset is only if you brick.
There is no easy way to get back to stock, I will make a thing just like this installer to do that, actually its done, testing it
designgears said:
Haha, I understand your PM now... you got my file before I posted this.
the factory reset is only if you brick.
Click to expand...
Click to collapse
So if all else fails, the factory reset will bring it back to out of the box shape? Just concerned because Im still debating if I want to keep the phone before my 30 days is up etc. Id like to return it as stock obviously, but I also need to test out custom mods before my decision.
Thanks man.
I am curious, what changes were made for the reboot mod?
Also, thanks for the rom!
psufan5 said:
so if all else fails, the factory reset will bring it back to out of the box shape? Just concerned because im still debating if i want to keep the phone before my 30 days is up etc. Id like to return it as stock obviously, but i also need to test out custom mods before my decision.
Thanks man.
Click to expand...
Click to collapse
no no no, do not factory reset if it bricks!!! Read the op!!!!
shawnbuck said:
I am curious, what changes were made for the reboot mod?
Also, thanks for the rom!
Click to expand...
Click to collapse
smali edits in the framework.jar, android.policy.jar and added an image and sting to framework-res.apk
I saw the no factory reset posts lol... I was just curious what can be done to return the phone back to stock once this is all done with.
Thanks.
psufan5 said:
I saw the no factory reset posts lol... I was just curious what can be done to return the phone back to stock once this is all done with.
Thanks.
Click to expand...
Click to collapse
I designed this script to handle payloads, just need to package up one with a new payload with stock files and upload it.
Installed... Removed Laggyness i was getting with blur UI.
as to refering to the blur UI....
this is my second Atrix.. had to bring my first one back because when i was on tier 3 support the other night they fried the sim card reader with an update which was killing data signal to my phone... that phone had no laggyness whats so ever at all. I got this one today out of the box was having laggyness and slow response to key presses.. this fixed that as of so far.
designgears said:
smali edits in the framework.jar, android.policy.jar and added an image and sting to framework-res.apk
Click to expand...
Click to collapse
Nice, I will give this shot. Although I am already running DeOdexed already but I figured may be you got it running better than mine
I am also going to start editing small things like animations. No sense oh having all this power without some eye candy
Hello designgears,
Did you re-signed the apks? If so, could you share the key files you used? The reason I ask for it, it's because I am playing around with the /system/app apks and was getting errors like:
"Package com.motorola.blur.home has no signatures that match those in shared user"
Awesome job, btw!
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
uskr said:
Hello designgears,
Did you re-signed the apks? If so, could you share the key files you used? The reason I ask for it, it's because I am playing around with the /system/app apks and was getting errors like:
"Package com.motorola.blur.home has no signatures that match those in shared user"
Awesome job, btw!
Click to expand...
Click to collapse
Not sure, I didn't get an errors like that.
airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Try a usb port on the back of your PC
airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Download ADB Wireless from the Market. It'll help solve that one for you.
airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Install the Android SDK
install the MOTO drivers it will also install the moto adb drivers with it.
Install the ADB function drivers into the SDK/tools folder
run...cd to the sdk/tools folder... run... adb devices
should show the device is up which means ADB is enabled
I've Google'd the topic and all the comes up are my own post in the Dev sections where I asked how to create/get a logcat. I can "adb logcat" to a text file, then it shows "waiting for device". Now what's the procedure or setup on the S7 end? I've turned On adb debugging options in the S7. Can/ls this done by USB? The "adb devices" command while plugged into the USB shows nothing. I can connect in Fastboot mode and "adb devices" shows nothing also. Or is more of the Android SDK package needed for this?
Did you install the adb drivers?
Sent from my Nexus 7 using Tapatalk 2
giveen said:
Did you install the adb drivers?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hmm, since I've never used adb commands in the past, maybe not! Are they installed from a EXE file or in a INF fashion?
I love you man
http://forum.xda-developers.com/showthread.php?t=1484406
Download and extract, boot up device, make sure ADB is turned on device, then plug it into the computer, go to My Computer > Manage > Device Management, you should see something pop up with a yellow triangle, install the driver, it will ask you for the location point it to where you extracted the download at.
giveen said:
I love you man
http://forum.xda-developers.com/showthread.php?t=1484406
Download and extract, boot up device, make sure ADB is turned on device, then plug it into the computer, go to My Computer > Manage > Device Management, you should see something pop up with a yellow triangle, install the driver, it will ask you for the location point it to where you extracted the download at.
Click to expand...
Click to collapse
I may have never really installed ADB drivers, only Fastboot months ago. I feel like a real noobie again! Thinking that I missed the ADB drivers somehow I found that post on my own but take a look at the link. See anything missing??
wptski said:
I may have never really installed ADB drivers, only Fastboot months ago. I feel like a real noobie again! Thinking that I missed the ADB drivers somehow I found that post on my own but take a look at the link. See anything missing??
Click to expand...
Click to collapse
Um....no?
http://d-h.st/592
giveen said:
Um....no?
http://d-h.st/592
Click to expand...
Click to collapse
Yep, that's a link to the page but where's a link to actual file download? I think the third comment on the page mentions this.
If I'm not missing the driver files, I wonder if it might be that I NVflashed CM10 again but didn't allow it to reboot before restoring a TWRP backup?
All the old links to files have been changed since the DNS problems but I found a link to the old files at StreakDroid and the DNS issued is fixed. Download, unzipped, nothing looks any different to what I already have. I still tried the package anyway and it still can't find it's driver. Next I'm going to NVflash CM10 again and let it boot up fully and try it then before restoring my TWRP backup.
I had the same problem the other day when i flashed mine to CM10.
In the end the procedure which worked for me was to unplug the usb cable from my laptop.
Press the small button to hard power off the device.
Boot the device to CM10 again.
Plug the device in to a different USB port.
Then i went in to device manager and found a "dell" device which i right clicked then update drivers and pointed to the folder where i had the adb drivers downloaded to. It found them and installed the devices as an adbx device.
Then i unplugged from usb again and plugged it back in. At this point i ran the logcat command and it started logging.
jamezz98 said:
I had the same problem the other day when i flashed mine to CM10.
In the end the procedure which worked for me was to unplug the usb cable from my laptop.
Press the small button to hard power off the device.
Boot the device to CM10 again.
Plug the device in to a different USB port.
Then i went in to device manager and found a "dell" device which i right clicked then update drivers and pointed to the folder where i had the adb drivers downloaded to. It found them and installed the devices as an adbx device.
Then i unplugged from usb again and plugged it back in. At this point i ran the logcat command and it started logging.
Click to expand...
Click to collapse
I tried exactly as you outlined and it still didn't find the needed drivers. Funny as it shows a "B10B" as the unknown device and in the two WIN32 INF files that is a Dell parameter ID.
I may try my TWRP backup to ICS-B4 again before I NVflash again sometime today.
EDIT:
Restored my TWRP ICS-B4 backup but it can't find its drivers either and I tried swapping ports also. One thing though, instead of "B10B" showing up in "Other Devices", I get "Android". An NVflash is next, maybe a TWRP backup breaks ADB??
wptski said:
I tried exactly as you outlined and it still didn't find the needed drivers. Funny as it shows a "B10B" as the unknown device and in the two WIN32 INF files that is a Dell parameter ID.
I may try my TWRP backup to ICS-B4 again before I NVflash again sometime today.
EDIT:
Restored my TWRP ICS-B4 backup but it can't find its drivers either and I tried swapping ports also. One thing though, instead of "B10B" showing up in "Other Devices", I get "Android". An NVflash is next, maybe a TWRP backup breaks ADB??
Click to expand...
Click to collapse
Its because I was testing some things out in init.streak7.usb.rc
giveen said:
Its because I was testing some things out in init.streak7.usb.rc
Click to expand...
Click to collapse
Ah, what do you mean? ADB isn't going to work? It didn't work after another NVflash and allowed to boot up.
wptski said:
Ah, what do you mean? ADB isn't going to work? It didn't work after another NVflash and allowed to boot up.
Click to expand...
Click to collapse
It works just fine.
I'm stumped!
Got it! I had use the pick device option route which led to Android to ADB Interface or ADB Composite Interface. I selected the non-composite option, used those same files again and it installed the proper drivers. I have no idea and don't really care. What a PITA!
wptski said:
Got it! I had use the pick device option route which led to Android to ADB Interface or ADB Composite Interface. I selected the non-composite option, used those same files again and it installed the proper drivers. I have no idea and don't really care. What a PITA!
Click to expand...
Click to collapse
Restored my ICS-B4 backup, ran into the exact same issue and used the same solution to install the ADB drivers.
Hey guys,
I'm just trying to port a Rom...
I changed some settings and it installs clearly now, but it has a bootloop...
I'm trying to port the paranoid android rom from HTC One X, I think it's V3.10...
I just googled and searched around and I know that I should get a log via ADB...
The PC finds my device, in device manager it is in "portable devices" as "P880", but doesn't show it in "Computer"... There is just my HDD and my cd burner shown...
I start CMD before debugging phone on PC and type "adb logcat", ADB starts and the message "Waiting for device" appears...
I plug the phone in, boot it and the computer finds the device in device manager... But ADB still "waits for device"... When I open another CMD Window and type "adb devices" it shows a device which is "offline"...
I have installed the latest ADB drivers (needed them for unlocking BL) and LG Software drivers...
Is there any other way to show a log while booting or at least turn the device to "online"?
Thanks in advance!
The phone should be detected as adb device in device manager do you see any driver contains adb in it - you can try droid explorer for log cat but I think it depends on working adb too
Thanks, I will try it later!
do you have adb version 1.0.31? lower versions won't work
also, there's a string in default.prop (in your kernel) with something like "ro.adb.secure=1" --> set it to 0 and re-compile
laufersteppenwolf said:
do you have adb version 1.0.31? lower versions won't work
also, there's a string in default.prop (in your kernel) with something like "ro.adb.secure=1" --> set it to 0 and re-compile
Click to expand...
Click to collapse
Thanks for your reply, I have the newest SDK so I think newest ADB, too, so that's not the problem...
thank you for this hint, I will look into it and will search that string....
I'll report when I find it
Since you have SDK, use ddms.
Tested and.... Nothing -.-
laufersteppenwolf said:
do you have adb version 1.0.31? lower versions won't work
also, there's a string in default.prop (in your kernel) with something like "ro.adb.secure=1" --> set it to 0 and re-compile
Click to expand...
Click to collapse
So, I just checked ADB version: 1.0.31...
I made it to unpack the boot.img (don't ask how ) and changed the "ro.adb.secure=1" to 0 and compiled it...
I just zipped and flashed the rom and connected it to PC and... Goddammit, nothing! Device is still offline... Any other ideas?
Paulo87 said:
Since you have SDK, use ddms.
Click to expand...
Click to collapse
So i just checked ddms... It tells me that it is a old version or sth. like that and I should use "monitor" instead of ddms...
Tried that, but still... Device is offline...
I start freaking out!
BlackDuty said:
So, I just checked ADB version: 1.0.31...
I made it to unpack the boot.img (don't ask how ) and changed the "ro.adb.secure=1" to 0 and compiled it...
I just zipped and flashed the rom and connected it to PC and... Goddammit, nothing! Device is still offline... Any other ideas?
So i just checked ddms... It tells me that it is a old version or sth. like that and I should use "monitor" instead of ddms...
Tried that, but still... Device is offline...
I start freaking out!
Click to expand...
Click to collapse
you can stay with ddms, it's better IMO
now you can try to change "ro.secure=1" to "ro.secure=0", compile and try again now adb should start as soon as possible, even on kernel level
Argghhh
Why didn't you tell it earlier?
Just joking, thank you!
Will try and report...
Another try went wrong...
Okay,
so I recompiled the boot.img with an "ro.security=0" string...
Flashed and restarted, device was found by PC but it's still shown as offline
Tested ADB Logcat DDMS & Moniter, everytime offline...
The device is shown in windows device manager like in attached picture...
Maybe something is wrong there?
.
I tried to reinstall all the drivers, but still nothing new...
I just wanted a f*cking Bootlog, but it looks like I have to write complete android from scratch :laugh:
Maybe you have another idea... *hoping* :silly:
BlackDuty said:
Okay,
so I recompiled the boot.img with an "ro.security=0" string...
Flashed and restarted, device was found by PC but it's still shown as offline
Tested ADB Logcat DDMS & Moniter, everytime offline...
The device is shown in windows device manager like in attached picture...
Maybe something is wrong there?
.
I tried to reinstall all the drivers, but still nothing new...
I just wanted a f*cking Bootlog, but it looks like I have to write complete android from scratch :laugh:
Maybe you have another idea... *hoping* :silly:
Click to expand...
Click to collapse
you don't use linux?! well, try to use a linux OS, and if it doesn't work there, too, do the following:
pull the battery
put it back in and boot the device
i guess it stops somewhere and stays there, right?
pull the battery again
put the battery back in and boot into CWM
now run:
Code:
adb shell
su
cat /proc/last_kmsg >/sdcard/debugging/last_kmsg
ctrl + c
adb pull /sdcard/debugging/last_kmsg C:\debugging\last_kmsg.txt
laufersteppenwolf said:
you don't use linux?! well, try to use a linux OS, and if it doesn't work there, too, do the following:
pull the battery
put it back in and boot the device
i guess it stops somewhere and stays there, right?
pull the battery again
put the battery back in and boot into CWM
now run:
Code:
adb shell
su
cat /proc/last_kmsg >/sdcard/debugging/last_kmsg
ctrl + c
adb pull /sdcard/debugging/last_kmsg C:\debugging\last_kmsg.txt
Click to expand...
Click to collapse
Unfortunatly I can't use linux, just with a terminal over cygwin :|
I will try that method tomorrow, now I have to sleep
Thank you again, you make me feel a little bit smarter then I am atm
Launch SDK Manager and download/install "Google USB Driver"
When the download is complete, follow this tutorial to install the usb driver's. -> Here
Next time you plug your device on boot you will see it as "Android ADB Interface".
Paulo87 said:
Launch SDK Manager and download/install "Google USB Driver"
When the download is complete, follow this tutorial to install the usb driver's. -> Here
Next time you plug your device on boot you will see it as "Android ADB Interface".
Click to expand...
Click to collapse
As you can see in the attached picture in my previous posts, there is already the "ADB Interface" on device manager, or is there any difference between "Android ADB Interface" and "ADB Interface"?
I will try to reinstall it and look into the link to install USB-Drivers you wrote here, later!
Thank you for that many tries to help me! I hope we will find the right way...
Hey, some news:
@Paulo87 : I tried to reinstall the google drivers and use the device as Android ADB Interface and it worked when I am in recovery...
Looked at monitor and ddms, they found a device but there was no "online" or "offline", but a "??"
I flashed the files and rebooted, plugged data cable in and... There is still this MTP-Device shown, no Android ADB Interface...
Tried the same steps there but it told me that in the folder google drivers are no drivers for this MTP device...
I think I will kill me in the next hours
Nah, just joking, but this is really annoying...
@laufersteppenwolf : Tried like you said:
pull battery off -> plug it in -> reboot -> bootloop -> pull battery off -> plug it in -> boot into recovery
plug in usb cable -> type "adb shell" on CMD with admin rights (adb starts server) -> typing "su" (error like /sbin/sh: su not found) -> still trying to pull the kmsg log, but as the SU rights fail, the whole way fails -.-
Any ideas why it is not found?
Thanks...
Try doing what @laufersteppenwolf said without the "su".
Honestly, if nothing work's... Just kill yourself like you said! (Joking)
Don't quit mate, everything has a solution.
Paulo87 said:
Try doing what @laufersteppenwolf said without the "su".
Honestly, if nothing work's... Just kill yourself like you said! (Joking)
Don't quit mate, everything has a solution.
Click to expand...
Click to collapse
I already tried, but it hangs on the last step, it says that "last_kmsg" wasn't find... So if it doesn't exist , it's logical that you can't move it... Something like this
And you really don't want to know how near I am to do that thing what the guy in your picture did... :silly:
Any other suggestions?
BlackDuty said:
@laufersteppenwolf : Tried like you said:
pull battery off -> plug it in -> reboot -> bootloop -> pull battery off -> plug it in -> boot into recovery
plug in usb cable -> type "adb shell" on CMD with admin rights (adb starts server) -> typing "su" (error like /sbin/sh: su not found) -> still trying to pull the kmsg log, but as the SU rights fail, the whole way fails -.-
Any ideas why it is not found?
Thanks...
Click to expand...
Click to collapse
this seems like the rom wasn't flashed?! or the rom has no su binary included...
and when it says, that last_kmsg wouldn't be found, it's most likely that you've got a serious problem with your kernel...
what kernel source are you using?
Honestly, i have no more ideas mate...
Good luck.
Glück
Hey guys,
First of all I'd like to apoligize for my english skills and a thread if I've posted in a wrong one category.
However, I have REALLY serious problem right now and I'll try to explain. Today I decided to reset my phone (settings - back up & reset). This didin't help me as I was expected therefore I wiped out all the data by using TWRP(yes, I'm a noob). Thought that it will erase everything but the ROM. I tried to do a reboot and the phone did the htc quietly brilliant logo but got caught at the beats audio logo screen and never advanced.
Went into recovery and tried to do a factory reset, and a whole bunch of other things (tried to reboot system, but is says that no os installed). The phone still gets stuck at the same screen. Also, I am unable to get it to be accessible on my computer again. it says that installing new device but nothing happens, so I have no way how to get into sdcard and mount a new ROM or something. Is there any way how to fix it?? How to install a new ROM when USB not working and there's no way to take off SD card.....?
Nelayme said:
How to install a new ROM when USB not working and there's no way to take off SD card.....?
Click to expand...
Click to collapse
TWRP has an option to enable adb sideload. Then you can adb push rom.zip
BenPope said:
TWRP has an option to enable adb sideload. Then you can adb push rom.zip
Click to expand...
Click to collapse
Nothing happens, actually. All I can see is " Usage: adb sideload filename.zip, Updating partition details... Starting ADB sideload feature" and that's it. Waited for 5 min and still nothing..
Nelayme said:
Nothing happens, actually. All I can see is " Usage: adb sideload filename.zip, Updating partition details... Starting ADB sideload feature" and that's it. Waited for 5 min and still nothing..
Click to expand...
Click to collapse
You go into TWRP and enable sideload mode, it will do nothing but say sideload is being started. Then copy whatever ROM you want into the same folder as fastboot and adb. Open up a new command window and type "adb sideload rom.zip", obviously name your ROM "rom.zip" and click enter ... In the command window you should see a percentage figure start to increase as it pushes it to your phone. When it's completed just flash the ROM like normal in TWRP.
AllAboutTheCore said:
You go into TWRP and enable sideload mode, it will do nothing but say sideload is being started. Then copy whatever ROM you want into the same folder as fastboot and adb. Open up a new command window and type "adb sideload rom.zip", obviously name your ROM "rom.zip" and click enter ... In the command window you should see a percentage figure start to increase as it pushes it to your phone. When it's completed just flash the ROM like normal in TWRP.
Click to expand...
Click to collapse
I tried doing that myself but never got a percentage showing me anything I freaked out at first ten I just like it do it's thing until it said it transferred
Sent from inside the T.A.R.D.I.S
joselv456 said:
I tried doing that myself but never got a percentage showing me anything I freaked out at first ten I just like it do it's thing until it said it transferred
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
Another option is to just use an OTG cable and flash a ROM from a flash drive.
AllAboutTheCore said:
You go into TWRP and enable sideload mode, it will do nothing but say sideload is being started. Then copy whatever ROM you want into the same folder as fastboot and adb. Open up a new command window and type "adb sideload rom.zip", obviously name your ROM "rom.zip" and click enter ... In the command window you should see a percentage figure start to increase as it pushes it to your phone. When it's completed just flash the ROM like normal in TWRP.
Click to expand...
Click to collapse
Just tried what you said and still nothing. There're somekinda problems with USB, I'm even unable to connect my phone.. When I typed "adb sideload rom.zip" it was saying "error: device not found" only. Will try to reinstall htc sync drivers, but I think it won't help.. Any other ideas how to back my htc to life (didin't try with OTG cable yet)?
Nelayme said:
Just tried what you said and still nothing. There're somekinda problems with USB, I'm even unable to connect my phone.. When I typed "adb sideload rom.zip" it was saying "error: device not found" only. Will try to reinstall htc sync drivers, but I think it won't help.. Any other ideas how to back my htc to life (didin't try with OTG cable yet)?
Click to expand...
Click to collapse
OTG cable should work and is the easiest way to do it but if not you might want to check this thread .. http://forum.xda-developers.com/showthread.php?t=2363516
See this post, might help
http://forum.xda-developers.com/showpost.php?p=44730345&postcount=13
AllAboutTheCore said:
OTG cable should work and is the easiest way to do it but if not you might want to check this thread .. http://forum.xda-developers.com/showthread.php?t=2363516
Click to expand...
Click to collapse
Hey mate,
I just got OTG cable, moved a new Rom into USB stick and tried to mount on TWRP. All I got was "E: Unable to mount '/usb-otg'. Maybe I've missed couple of steps before?
FIXED: All I had to do is to format an USB stick in FAT32. Everything went well and now I can use my phone once again. Thanks a lot for your help, hope it will help to others as well.
Cheers!
HI everyone, i have unlocked Mi Mix with EU Global ROM (rooted) and TWRP installed.
After the phone was playing up, I idiotically removed root and deleted Xposed, and it was OK, but tonight I tried to re-install originial ROM, and now can't do anything with the phone.
I can boot into TWRP, but when i try fastboot, the fastboor screen comes up for 20 seconds, then the phone boots to Mi logo, and nothing happens.
I can't get computer to recognize the phone so can't add new ROM - so unsure how to do anything now
Any help appreciated, thanks!
Jamie
Hello !! i think i can help you , well same thin happened to me and what i did was ----∑ Boot into recovery , plug your phone to computer , download Universal ADB Driver and when it detects Adb Composite click install . Then you will be able to unlock and use fastboot. Hope it helps if not im sorry , this is all i know. Good Luck !!!
If you are able to boot in to twrp why just install the original Chinese rom and start from scratch.
YazumiWuHung said:
Hello !! i think i can help you , well same thin happened to me and what i did was ----∑ Boot into recovery , plug your phone to computer , download Universal ADB Driver and when it detects Adb Composite click install . Then you will be able to unlock and use fastboot. Hope it helps if not im sorry , this is all i know. Good Luck !!!
Click to expand...
Click to collapse
Thanks, will try
jaime4272 said:
If you are able to boot in to twrp why just install the original Chinese rom and start from scratch.
Click to expand...
Click to collapse
Hey, thanks for the reply - in TWRP though I can't see any ROM files, or anything to install?
Download a ROM (from desktop)... boot to TWRP (device)... Mount storage... Copy Rom to device... Flash ROM...
lesscro said:
Download a ROM (from desktop)... boot to TWRP (device)... Mount storage... Copy Rom to device... Flash ROM...
Click to expand...
Click to collapse
Hi, thanks for the reply. the problem is, the computer doesn't recognize phone no matter what I do, and I tried the mount storage option but it only shows the phone internal storage!
Sorry, i'm new to this all, thanks,
Jamie
There is sdcard on Mix, then if you see internal storage you can copy rom on it then when u try to flash, navigate to this zip file...
Other u can flash using MiFlashTool using adb feature....
lesscro said:
There is sdcard on Mix, then if you see internal storage you can copy rom on it then when u try to flash, navigate to this zip file...
Other u can flash using MiFlashTool using adb feature....
Click to expand...
Click to collapse
Thanks! Yeah, I noticed it said SD card - but it's not removable, no? So i don't know how to put ROM onto it, when my computer doesn't recognise it!
Thanks
Jamie
When you boot into TWRP, try "adb devices" on your PC. If it's read there, you can use the "adb push filename.zip /sdcard/" command to push the ROM to your phone and then install it.
admirdante said:
When you boot into TWRP, try "adb devices" on your PC. If it's read there, you can use the "adb push filename.zip /sdcard/" command to push the ROM to your phone and then install it.
Click to expand...
Click to collapse
Thanks, is adb devices the same as mimal ADB and fastboot? As in, the program? I have that installed, although it can't find phone
And sorry for knowing so little, i don't have much Android experince.
Thanks,
Jamie
Check if u have an issue with your driver when device is connected... device manager on windows 10...
If yes, check to install driver from computer (not from web or cd's or something like that), select universal USB/adb feature... and ur device will appear...
Weirdali said:
Thanks, is adb devices the same as mimal ADB and fastboot? As in, the program? I have that installed, although it can't find phone
And sorry for knowing so little, i don't have much Android experince.
Thanks,
Jamie
Click to expand...
Click to collapse
Well, I use minimal ADB and fastboot too. Just run it, and try "adb devices". If it's read, you can try the "adb push". If not, please check your Device Manager to see if it is read there.
admirdante said:
Well, I use minimal ADB and fastboot too. Just run it, and try "adb devices". If it's read, you can try the "adb push". If not, please check your Device Manager to see if it is read there.
Click to expand...
Click to collapse
It doesn't appear in Device Manager, and it always has done before. I installed new drivers (made sure they were correct), rebooted PC, and still doesn;'t show in device manager, so not sure what top do!
Thanks,
Jamie
Weirdali said:
It doesn't appear in Device Manager, and it always has done before. I installed new drivers (made sure they were correct), rebooted PC, and still doesn;'t show in device manager, so not sure what top do!
Thanks,
Jamie
Click to expand...
Click to collapse
Damn. Not sure what to do either. Maybe download a fastboot ROM from their site and flash it trough Miflash? Maybe that'll work? If not, then I'm out of ideas.
lesscro said:
Check if u have an issue with your driver when device is connected... device manager on windows 10...
If yes, check to install driver from computer (not from web or cd's or something like that), select universal USB/adb feature... and ur device will appear...
Click to expand...
Click to collapse
I've 100% installed the right drivers, but the device doesn't show in device manager, or anywhere on my PC! It does charge though, which is weird
Weirdali said:
I've 100% installed the right drivers, but the device doesn't show in device manager, or anywhere on my PC! It does charge though, which is weird
Click to expand...
Click to collapse
if you have a usb OTG adapter you can put a rom on an usb stick mount it in twrp and flash from there
Did you do a total wipe? And left your device totally clean?
Weirdali said:
Thanks, is adb devices the same as mimal ADB and fastboot? As in, the program? I have that installed, although it can't find phone
And sorry for knowing so little, i don't have much Android experince.
Thanks,
Jamie
Click to expand...
Click to collapse
Put your ROM in the same folder as your adb drivers folder. Hold shift while right clicking in this folder and choose "open command window here". Boot into TWRP and goto "advanced", then "adb sideload". Now write in the command prompt "adb devices". It should now show your device id and "sideload" after it. Write "adb sideload name of your rom.zip"
At least your phone isn't totally dead like mine. I powered mine off with a full charge and we to power it back on a little while later and it's totally dead now. Even Xiaomi Flash Tool won't let me flash anything. Sees the phone but won't let me flash anything. I get an error code. Xiaomi, via email says they can't service my phone because I'm in the USA. This will be my last Xiaomi phone. So pissed off