Related
I'm trying fix up a n1 for my mom and for some reason it always reboots. Sometimes it will go a day or so but inevitably it will reboot on its own. I have tried several roms and several flashes of each all with clean installs. It will do it even if I leave it at the android log in screen on the first boot long enough. I have the recommended hboot and the ota radio and its unlocked. The only other thing I can think of is hardware based or the person I bought it from had a bad flash of a radio or hboot? Any and all advice is very welcome, I'm starting to pull my hair out on this one. Thanks in advance.
sent from my Sensation 4G
I would try removing or replacing the SIM and/or SD card, to see if they are the problem (easy fix).
Also, you could see if it's overheating by keeping it cool and seeing if that helps (nothing you can do to fix).
Thanks for the reply but I tried it with both the SD unmounted and sim removed and it still reboots. And it stays quite cool, never really goes above 94. Yeah I'm not really a noob but this one is stumping me.
sent from my Sensation 4G
skyhigh2004 said:
Thanks for the reply but I tried it with both the SD unmounted and sim removed and it still reboots. And it stays quite cool, never really goes above 94. Yeah I'm not really a noob but this one is stumping me.
sent from my Sensation 4G
Click to expand...
Click to collapse
Yeah rebooting without a sim card probably point to a hardware problems IMO.
Recently there was a rash of rebooting with Tmobile and for me a new sim card fixed it. Does it do it when you put the N1 in 2G only mode?
Ihavent tried the 2g thing but I will. I'm using it with my new sim card from my sensation and it still reboots, although much less often.
Sent from my Nexus One using Tapatalk
When you say a clean install, has this included MANUALLY wiping the /system partition? Most people neglect to do this, and when you are installing other ROMs over old ones, sometimes things get left in place because of various upgrade scripts. Try it with a full wipe (you can search for temasek's Extreme Wipe for an easy flashable file to do it all).
bassmadrigal said:
When you say a clean install, has this included MANUALLY wiping the /system partition? Most people neglect to do this, and when you are installing other ROMs over old ones, sometimes things get left in place because of various upgrade scripts. Try it with a full wipe (you can search for temasek's Extreme Wipe for an easy flashable file to do it all).
Click to expand...
Click to collapse
Yes when I say clean I mean I went and manually formatted all partitions including system.
sent from my Sensation 4G
skyhigh2004 said:
Yes when I say clean I mean I went and manually formatted all partitions including system.
sent from my Sensation 4G
Click to expand...
Click to collapse
Just making sure... A lot of people will just do the factory reset/data wipe and say it was a complete wipe.
Any more ideas? Could a faulty battery make this happen? It seams to happen more if you try talking on the phone or use it while its charging.
sent from my Sensation 4G
Yes, if your battery is getting excessively hot, it can cause reboots. You can try getting a cheap replacement. The cheapies may not be very accurate with the battery percentage, but you can at least see if it solves your other problem.
Immediately after the phone rebooted, connect it to ADB and execute:
adb bugreport > bugreport.txt
Check the file, see the last_kmsg log and the last logcat (bugreport has several sections).
If you see "ARM9 has crashed" - your phone's HW is faulty and needs repair.
Can I run that from the phone itself? I don't have ADB installed
I think that can be done in a terminal:
bugreport > /sdcard/bugreport.txt
correct?
Hi ,
my N1 reboot again and run bugreport , I'm not seeing any useful because the log is created AFTER the reboot (check that on timestamp) , there is a way to have the entire log , so I can check what's happening just before the reboot?
thanks in advance!
Last night the phone rebooted again , I did not touch it and today in the morning I get the last_kmsg log, this is the last part:
Quote
[ 904.462921] batt: 80%, 3977 mV, -114 mA (-41 avg), 25.5 C, 1084 mAh
[ 909.237762] msm_pm_wait_state(2, 0, 0, 0) failed 11011
[ 909.237762] msm_sleep(): msm_pm_wait_state failed, 11011
[ 909.237762] ARM9 has CRASHED
[ 909.237762] smem: DIAG '[WCDMA] 02:02:15 FATAL: WCDMA L1 (mdspsync.c:01765) (0)
[ 909.237762] '
[ 909.237762]
[ 909.237762] Restarting Linux version 2.6.37.6-cyanogenmod-01509-g8913be8 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 PREEMPT Wed Jul 27 21:31:24 EDT 2011
[ 909.237762]
No errors detected
So it seems there is HW failure, correct?
Yes, unfortunately, looks like it is.
UPDATE
http://forum.xda-developers.com/showthread.php?p=33043197#post33043197
An app removing WiFi/BT from your Atrix, stopping the reboots. El Noob friendly.
Click to expand...
Click to collapse
Howzit stalkers
There is a serious hardware flaw on our Atrix's (Atrices?) - the WiFi and Bluetooth module from Broadcom goes bust after a while - irrespective of which ROM you are using (even stock is not free from this problem).
You get random reboots, you only get "Error" when trying to connect to WiFi, and if you try again - it reboots. Same with Bluetooth.
That prompted me to make this build. It is CM9 with the WiFi and BT disabled. No more random reboots. This is a stop-gap measure until we can figure out what is causing this (most fingers point to the little battery on the CPU mainboard). This ROM just makes your phone usable again as a, you know, phone. HSPA also works. You can reverse tether with a USB cable to use your PC's internet - if you are interested and you are using Ubuntu I can give you an app I made for this purpose.
Please, keep the discussion on this forum on the topic of FINDING OUT WHAT IS CAUSING THIS.
There is a plethora of other forums with other users also experiencing this problem - no "me too" nonsense, please. It is a recognized problem. The pet protection agency will be forced to euthenize a little fluffy baby kitten if you post a "me too" post.
UPDATE - How to make it work in other ROMS
Some adb shell commands - you should be able to use / know what adb is (I'm no good at clockwork zip scripts - yet - so this will do):
adb shell
su bash
mount
//Then, look for something like "/dev/block/mmcblk0p12 /system ext4" - key is the /system part
mount -o rw,remount /dev/block/mmcblk0p12 /system/
cd /system/lib/modules
mv dhd.ko dhd.ko2
That's it - confirmed to work with Jokersax's 0.6 release and Turl's. Will probably work on older systems as well, seeming that all use the same archaic Froyo f-ing kernel.
Click to expand...
Click to collapse
WHAT IS DISABLED
WiFi
Bluetooth
What doesn't work
Camera (will try to fix this in the next release)
Video Camera
Fingerprint sensor (usual CM9)
Webtop (usual CM9)
Link
http://depositfiles.com/files/o9jyr61a2
http://ifolder.ru/30516689
Reserverd by OP
[ 31.028143] sdhci_tegra_wlan_detect Detecting WLAN
[ 31.028164] mot_wifi_set_carddetect: Nobody to notify
[ 31.029391]
[ 31.029395] Dongle Host Driver, version 4.218.248.32
[ 31.029400] Compiled in /tank/jokersax/cm9/kernel/moto/olympus/wifi-module/wlan/osrc/open-src/src/dhd/linux/../.. on May 7 2012 at 11:40:09
[ 31.328158] mmc1: error -110 whilst initialising SDIO card
WARNING: at /tank/jokersax/cm9/kernel/moto/olympus/lib/kobject.c:595 kobject_put+0x50/0x60()
[ 214.627572] kobject: '<NULL>' (0003da74): is not initialized, yet kobject_put() is being called.
[ 214.627581] Modules linked in: dhd(+)
[ 214.627591] Backtrace:
[ 214.627612] [<c0040010>] (dump_backtrace+0x0/0x10c) from [<c05b68c8>] (dump_stack+0x18/0x1c)
[ 214.627622] r7:c031c6c4 r6:c071fb48 r5:00000253 r4:e83a1e98
[ 214.627647] [<c05b68b0>] (dump_stack+0x0/0x1c) from [<c00bc5b8>] (warn_slowpath_common+0x50/0x68)
[ 214.627663] [<c00bc568>] (warn_slowpath_common+0x0/0x68) from [<c00bc61c>] (warn_slowpath_fmt+0x30/0x38)
[ 214.627673] r7:bf081000 r6:00000000 r5:bf076570 r4:0003da74
[ 214.627692] [<c00bc5ec>] (warn_slowpath_fmt+0x0/0x38) from [<c031c6c4>] (kobject_put+0x50/0x60)
[ 214.627701] r3:00000000 r2:c071fb80
[ 214.627720] [<c031c674>] (kobject_put+0x0/0x60) from [<c03787f0>] (put_driver+0x14/0x18)
[ 214.627729] r4:e98390c0
[ 214.627742] [<c03787dc>] (put_driver+0x0/0x18) from [<c0378938>] (driver_register+0x144/0x164)
[ 214.627757] [<c03787f4>] (driver_register+0x0/0x164) from [<c037994c>] (platform_driver_register+0x4c/0x60)
[ 214.627767] r9:00000000 r8:00000000 r7:bf081000 r6:00000000 r5:e83a0000
[ 214.627782] r4:bf078890
[ 214.627826] [<c0379900>] (platform_driver_register+0x0/0x60) from [<bf049fa4>] (wifi_add_dev+0x24/0x40 [dhd])
[ 214.627870] [<bf049f80>] (wifi_add_dev+0x0/0x40 [dhd]) from [<bf0810bc>] (init_module+0xbc/0x238 [dhd])
[ 214.627902] [<bf081000>] (init_module+0x0/0x238 [dhd]) from [<c003b5c8>] (do_one_initcall+0x40/0x1bc)
[ 214.627912] r5:e83a0000 r4:c07e0c00
[ 214.627932] [<c003b588>] (do_one_initcall+0x0/0x1bc) from [<c00f3880>] (sys_init_module+0xcc/0x200)
[ 214.627941] r9:e83a0000 r8:c003c364 r7:00046bd8 r6:00000000 r5:bf076748
[ 214.627957] r4:5c126008
[ 214.627970] [<c00f37b4>] (sys_init_module+0x0/0x200) from <c003c1e0>] (ret_fast_syscall+0x0/0x2c)
[ 214.627979] r7:00000080 r6:5e0fdb34 r5:5c126008 r4:405ad0f0
[ 214.627995] ---[ end trace 2416c978061dd5a5 ]---
[ 214.628002] Error: Driver 'bcm4329_wlan' is already registered, aborting...
Now I had some experience with WiFi kernel driver development (iMx51 + CSR based WiFi/BT combo chip).
The startup sequence on kernel level will probably go like this:
1) Kernel startup
2) ARM CPU specifics startup
3) Platform specific device setup (setup clocks)
3) Platform driver dependency registration (like, on SDIO 1 there is a WiFI chip that needs driver X to work)
4) Sub-platform driver startup (SPI, SDIO, UART, I2C)
I think this is where we fail first - Error -110 means timeout. Each MMC / SDIO chip has a MMC specific startup sequence, then depending what was given on number 3, it jumps over to SDIO (SDIO is a superset of MMC).
When our BT/WiFi chip is put into SDIO mode, the SDIO commands fail with a time out.
Possible reasons for it failing:
1) Incorrect voltages
2) Skewed clock
3) Busted chip.
4) We talk to it too fast
5) Kernel is messed up
Now, seeing that (through weird loops, check my previous post) I could get the unit running two more times, I do not think it is 3.
Why it could be 1:
Voltage rails needs to start up at the correct sequence for some chips. Like some chips will specify an operating range of between 1.8V and 3.3V. That means if it finds 5V on it, it will shut itself off. Sometimes some chips needs an initial 3V, then after 10 seconds it can be put into 1.8V (in-chip startup). Sometimes, it needs 10seconds to stabilize before you can talk to it (in our case via SDIO).
Why it isn't 1:
I've tried a lot of other kernels. It is all based of the ATT code, and they do the voltage rail setup correctly. I've even reverted back to stock code - no dice.
Why it could be 2
By removing the small cell battery, the drain on the battery was lifted. It could then store up enough current to put itself into the correct clock rate when it was put back.
Why it isn't 2
? Don't know. More needs to be known of the function of this battery. Obviously it is driving some RTC (real time clock). RTC's normally work at 32MHz, (32768, easilly divideable by 2, 4, 8 etc).
Does the Broadcom chip need this RTC? Isn't its clock lines driven by the Tegra2?
Why it could be 4
If the RTC is compromised (number 2) then init will suffer. If the Tegra's clock is not derived from the battery and the Broadcom's is, then there will be a disparity between the 2 units chatting together, as SDIO communication is clock based and not latch based (like SPI). If I'm chatting to you at 32MHz and you are 5% off, then we will not be communicating (if you are an SDIO master and I'm an SDIO slave).
Why it isn't
No idea.
Why it could be 5
Bunch of kernel errors stating un-inited modules pointing to null.
Why it isn't 5
Stock kernels also have the same problem
So, sorry folks, this issue points to a hardware problem.
Our biggest answer will be at the following:
1) What does that battery do?
2) Why is the SDIO subsystem having timeouts?
mirror1
So you deleted two files? A more efficient method would be to make a zip that deletes those files so it could be used with future releases and with turls as well.
Sent from my MB855 using XDA
Can't you just keep wifi and bluetooth off?
jokersax11 said:
So you deleted two files? A more efficient method would be to make a zip that deletes those files so it could be used with future releases and with turls as well.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
No, I've changed the kernel. On arch/arm/mach-tegra/ I've changed board-mot.c to not do wifi init and also removed board-mot-wlan.c from the Makefile. This keeps the SDIO card from being init-ed and is sufficient for the driver not to be registered.
Yes, having an update that is more frugal than having a 125MB update will probably work. But I don't have the inclination to do that now, as making my own custom kernel + ensuring it working with turl's base + a custom update script is not in the depth I want to waddle in now. Unless someone wants to help me with it. It is really a 2 line patch stretching on these 2 files.
As from "just switching off wifi and bluetooth" - there are SDIO interrupts being enabled from the GPIO and (subsequently) on the SDIO card (the Broadcom 4329). That means, even if you disable these 2, IRQ interrupts will still happen = the phone will still reboot.
mvniekerk said:
No, I've changed the kernel. On arch/arm/mach-tegra/ I've changed board-mot.c to not do wifi init and also removed board-mot-wlan.c from the Makefile. This keeps the SDIO card from being init-ed and is sufficient for the driver not to be registered.
Yes, having an update that is more frugal than having a 125MB update will probably work. But I don't have the inclination to do that now, as making my own custom kernel + ensuring it working with turl's base + a custom update script is not in the depth I want to waddle in now. Unless someone wants to help me with it. It is really a 2 line patch stretching on these 2 files.
As from "just switching off wifi and bluetooth" - there are SDIO interrupts being enabled from the GPIO and (subsequently) on the SDIO card (the Broadcom 4329). That means, even if you disable these 2, IRQ interrupts will still happen = the phone will still reboot.
Click to expand...
Click to collapse
If customized kernel, I can make a flash zip for it....really easy. Literally take me like 2 minutes.
Th3Bill said:
If customized kernel, I can make a flash zip for it....really easy. Literally take me like 2 minutes.
Click to expand...
Click to collapse
K, please explain how?
mvniekerk said:
K, please explain how?
Click to expand...
Click to collapse
NP. Assuming you did a boot.img edit, all you would need to do is download a copy of one of Joker's working kernels from Jokersax.com. Overwrite the boot.img and modules with the ones from your "tweaks" and mod name to (no wifi).
Will have a look at it tomorrow. Thanks!
mvniekerk said:
Will have a look at it tomorrow. Thanks!
Click to expand...
Click to collapse
No problemo. I did the same thing once when I had to make an edit to get adb to work my MIUI builds
Is there a way to replicate this issue? I'm curious because I have had no problems with my wifi or bt with any roms I have flashed.
Sent from my MB860 using Tapatalk 2
maulich said:
Is there a way to replicate this issue? I'm curious because I have had no problems with my wifi or bt with any roms I have flashed.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
I don't think it's a guaranteed issue. It seems to be something that happens with some devices over time. At least that's what I gather to be the issue. If you have working wifi and bt, then I wouldn't worry about it at this time
I soo hope this never happens to my atrix!!
Th3Bill, is it possible to create a Generic .zip that can be applied to any cm9 based rom ay any time? Sounds like something I may want kickin around just incase, lol.
Do the reboots happen while the phone is first trying to boot up? Or after wifi or bt is turned on, random reboots start occuring?
Just wanna know what signs I should look out for because I would be hopeless trying to syphon through lines of script. I may as well try reading Japanese lol
ATRIXXIRTA said:
I soo hope this never happens to my atrix!!
Th3Bill, is it possible to create a Generic .zip that can be applied to any cm9 based rom ay any time? Sounds like something I may want kickin around just incase, lol.
Do the reboots happen while the phone is first trying to boot up? Or after wifi or bt is turned on, random reboots start occuring?
Just wanna know what signs I should look out for because I would be hopeless trying to syphon through lines of script. I may as well try reading Japanese lol
Click to expand...
Click to collapse
When you say generic zip, you mean a flash zip that you can just add some files to and use to flash your phone? I have one already made. Only issue...you need to make sure you set the permissions when you use it....so it's not the most user-friendly thing. I will try to make it a bit more user friendly and then up it tonight
By generic I just mean one that can be applied to any rom that's cm9 based (cna,aokp,gummy etc..)
Joker recommended creating a fix to be applied to an existing rom, rather then creating a whole new one with some removed files, scripts, or whatever this rom is missing that removes bt and wifi.
And you said you could possible help create a zip fix.
I was just curious if it would be a fix that can be applied to multiple roms, or would each one need its own specific fix?
Also, where the hell is a good place to start learning the basics of android development.
Seems like the more I try to learn, the more I realize there are othere things I need to know, or should at least have some knowledge of first. Like java, *nix based OS's, and all kinds of other stuff, its pretty overwhelming considering I've had no interest in computers or technology until January when I started working for Rogers, lol.
A good starting point would be awesome. I know google, xda and these forums are good places, but there are soo many abbreviations (html, ttps, http, ip,) that I still don't know, that I end up at least a little confused. lol.
Tryin to read this op is a good example. There like 14 different abbreviations I have no clue about, lol.
Thanks
I just flashed this ROM on my Atrix and so far so good. I have only been running it for an hour now, but usually by now it would have rebooted once or twice. I'll report back tomorrow.
my coworker's sister designed the Atrix antenna and she said that the RTC battery has nothing to do with the wifi module. just my 2 cents.
also, i've had this error for about a month; my solution was to wipe fresh and install CM9 (5.1 jokersax), and NEVER EVER EVER touch the wifi/BT toggles. so far (one month) not a single reboot error. of course, now my data plan is choking pushing towards 3GB in 28 days, but whatever.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So far so good! Not a single reboot with some light to moderate usage. Thank you again for the modified ROM and kernel! Brought my phone back to life.
Fix Modem / Baseband JB AT&T ONLY... Sure did fix my problem!
Diagnosis for: (Random) no sound; no phone connectivity such as: WIFI; BLUETOOTH; GSM.
Can happen: Flashing wrong fw; Flash failure.
NOTE: Android SDK is required, go to your OS below and view "prerequisites" for more information...
Windows 7 methodPrerequisites: Android SDK - Tools and SDK! (install here.)
Instructions:
(1. Make a folder in the directory "C:/" and name it "qinara."
(2. Download the following attachment below: "NON-HLOS.bin" (In the attachments / downloads section)
(3. Place "NON-HLOS.bin" in the "C:/qinara/" folder.
(4. Open a cmd prompt.
(5. Change Directory (CD) the cmd to your install location of Android SDK's Platform Tools (type it in to the command prompt.) to make
a command like the following example. Example: CD C:/users/YOUR-USERNAME/android/sdk/platform-tools
(6. Type the following command in...
Code:
fastboot flash modem C:/qinara/NON-HLOS.bin
(7. Wait for the modem to be sent and installed.
(8. Type the following command in...
Code:
fastboot reboot
(9. When the phone boots everything but gsm will be working, to fix it go to settings. From the main settings menu, go to mobile network. It
will freeze, press the home button. Once you press the home button open up recent apps by pressing the multi-tasking button.
it freezes.
(10. Open up your multi-tasking menu and open settings.
(11. Set "select network" to "automatic," then your done.
Ubuntu / Other Linux-distro methodPrerequisites: Android SDK - Tools only! (to install type the following cmds in terminal...)
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Instructions:
(1. Make a folder in the directory "/home/USERNAME/" and name it "qinara."
(2. Download the following attachment below: "NON-HLOS.bin" (In the attachments / downloads section)
(3. Place "NON-HLOS.bin" in the "/home/USERNAME/qinara/" folder.
(4. Open a terminal.
(5. Type the following command in...
Code:
fastboot flash modem /home/USERNAME/qinara/NON-HLOS.bin
(6. Wait for the modem to be sent and installed.
(7. Type the following command in...
Code:
fastboot reboot
(8. When the phone boots everything but gsm will be working, to fix it go to settings. From the main settings menu, go to mobile network. It
will freeze, press the home button. Once you press the home button open up recent apps by pressing the multi-tasking button.
it freezes.
(9. Open up your multi-tasking menu and open settings.
(10. Set "select network" to "automatic," then your done.
Downloads
-NON-HLOS.bin
Ask any questions below... :fingers-crossed:
Kinda feels that way...but on the Linux instructions just use ~/qinara/NON-HLOS.bin instead of /home/USERNAME/qinara/NON-HLOS.bin
~/ means the users home directory
Also, and I'm gonna add this to my faq, but download the fastboot I linked, rename to moto-fastboot, place it in ~/bin and add that to $PATH in ~/.bashrc (or where ever your preferred disto prefers it to be)
My actual path line in .bashrc (the part above I'm referring to is in bold)
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/share/android/bin:/share/android/adt/sdk/tools:/share/android/adt/eclipse:/share/android/adt/sdk/platform-tools:$HOME/bin:"
For the curious, I keep all my Android stuff on its own partition (/share/android) so all I have to do is add those directories to my $PATH if I decide to disto hop. If you dualboot, you can do the same thing only set the partition as NTFS or ext2 (there's an windows ext2 driver). I disto hop about once a month.
Don't have access to my desktop right now trying to install my new ssd and put Linux mint on it. (Noticed your a Linux guy, do you like mint?) Anyways I'll be sure to add that in later. Thanks.
Sent from my MB886 using xda premium
Mints OK. I prefer Mint Debian, but I'm not a fan of Ubuntu. Pure Debian Stable and Testing is also a good choice.
Arch Linux and its derivatives are nice but aren't noob friendly and are prone to breakage due to being so bleeding edge. Manjaro is a noob friendly distro based on Arch repo snapshots with bug fixes.
About to hop to Slackware 14 myself. Gonna be my first time using it.
All the other distros I've used -- too long ago to be fair and relevant to what's out now.
help...
can you tell me its working or not cause i have some gsm problem no signal due to band change
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28172 KB)...
OKAY [ 2.430s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.720s
Oooooh Cool.....now after trying to find how to get out of the mess that created. I still dont have signal lol
i really need my signal back ...anyone could help me ,,,i am afraid this method does brick my phone ..and another question is if i install the stock rom from RSD lite , will i lost my root access???
yashrab said:
i really need my signal back ...anyone could help me ,,,i am afraid this method does brick my phone ..and another question is if i install the stock rom from RSD lite , will i lost my root access???
Click to expand...
Click to collapse
Yeah this method bricked my phone. I had to go back to stock through RSD, and lost root access. The good news is it was so easy to reacquire root thanks to Dan Rosenberg's programs.
Can I install stock though myth tool.. I think it does work just like RSD?.. Plz tell me cause I am totally noob in this part.. And I don't want to brick my phone..
Sent from my MB886 using xda premium
Moto Atrix work on any GSM carrier or.. ?
skeevydude said:
Mints OK. I prefer Mint Debian, but I'm not a fan of Ubuntu. Pure Debian Stable and Testing is also a good choice.
Arch Linux and its derivatives are nice but aren't noob friendly and are prone to breakage due to being so bleeding edge. Manjaro is a noob friendly distro based on Arch repo snapshots with bug fixes.
About to hop to Slackware 14 myself. Gonna be my first time using it.
All the other distros I've used -- too long ago to be fair and relevant to what's out now.
Click to expand...
Click to collapse
I have question. If I buy Moto Atrix HD will it possible to make it carrier-unlocked so I can use it here in Saudi Arabia where 90% devices are not carrier-locked?
lonesomedove said:
I have question. If I buy Moto Atrix HD will it possible to make it carrier-unlocked so I can use it here in Saudi Arabia where 90% devices are not carrier-locked?
Click to expand...
Click to collapse
You should be able to, but I'll tell ya that some users have gone through multiple places to get it unlocked since not all the unlock services have the updated unlock codes we need.
Nope
Code:
C:\Program Files\Android SDK\sdk\platform-tools>fastboot flash modem C:/qinara/NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28164 KB)...
OKAY [ 2.185s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.429s
Yup. Didn't work.
Any ideas?
BackDoorNoBaby said:
Code:
C:\Program Files\Android SDK\sdk\platform-tools>fastboot flash modem C:/qinara/NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28164 KB)...
OKAY [ 2.185s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.429s
Yup. Didn't work.
Any ideas?
Click to expand...
Click to collapse
You didn't use OUR fastboot. I have a link in our fastboot guide, and a direct link here.
/Thank you for posting the full terminal output, command and all.
//It helps
///Most just post "Help, Help, Help" X doesn't work.
Thanks
skeevydude said:
You didn't use OUR fastboot. I have a link in our fastboot guide, and a direct link here.
/Thank you for posting the full terminal output, command and all.
//It helps
///Most just post "Help, Help, Help" X doesn't work.
Click to expand...
Click to collapse
Got it. Thanks.
I'll check it out after my classes tonight and give an update.
Yup
Yup. That did it. Fixed the issue.
Back to my 4G!
Thanks again.
Anyone tried with CM10.2?
Nope. I know Cyanogenmod has issues at the moment, but I don't know if this will fix it.
Best I can say is to try it. Worst case: you reinstall the ROM. Or you can wait for a release version of CM 10 instead of a nightly.
I can say this didn't brick my phone, so you shouldn't have to worry about it. (but as always - no guarantee)
Sent from my Atrix HD using xda app-developers app
I really need help, I need something like this but for a company in Mexico. I tried this but it didn't worked.
Question if i reflash back to stock eith RSD LITE or myth tools will that fix my baseband i delete my baseband by accident
Dumb me
wcdma and lte network problem
i happen to own the mb886 the lte and wcdma used to work then i mistakenly went to change my base band to cellular (800-mhz) then the network went off so i changed it to (aus2 band (gsm-900/ dcs-1900/wcdma-850/wcdma-pcs-1900) but now am only able to get 2g or edge networks but am also in a 3g coverd area. can you guys please help me out
I have a moto e4 plus (owens) that had a custom rom flashed on it. After a few days of checking it out i decided to flash my stock backup. Upon doing this it got stock on a loop with (BAD KEY) at the top right, and no boot. Even after half an hour nothing happened.
I tried wiping cache after flashing the backup but still nothing. So i returned to the custom rom.
Again after a few days i really wanted to go back to stock, repeat previous process and still no progress. I decided to flash stock again.
I found directions and firmware, i double checked the version and it matched. I even found posts of successful flashing.
I went ahead and attempted but was greeted by a FAILED notice after attempting to start the process.
It failed to flash gpt.bin.
I looked up solutions but most said to just keep going, stupidly i did. Flashed everything, and everything else said PASS.
Rebooted the phone and......nothing. No boot sequence. No bootloader, No recovery. My computer detects it when i plug it in, but i can't access anything. At the moment im stuck using my Wife's ZTE Zmax 2, and my god i already miss my phone.
Does anyone have any sort of advice that could help, i believe there may be a chance since it does get detected by my phone, but im not to sure at the moment.
And i have succesfully flashed stock roms on my previous 3 phones, so i thought this time would be no issue.
Thanks in advance.
PV.Srg said:
Does anyone have any sort of advice that could help, i believe there may be a chance since it does get detected by my phone, but im not to sure at the moment.
Thanks in advance.
Click to expand...
Click to collapse
Just a thought, try using RSDLIte (http://rsdlite.com/rsd-lite-download/) instead of Fastboot. At least one other user on XDA said that was the only way that he could get to write. Not sure why this would be, but what have you got to lose?
Try letting the battery run down and then charging to get into Fastboot mode on your phone.
koop1955 said:
Just a thought, try using RSDLIte (http://rsdlite.com/rsd-lite-download/) instead of Fastboot. At least one other user on XDA said that was the only way that he could get to write. Not sure why this would be, but what have you got to lose?
Try letting the battery run down and then charging to get into Fastboot mode on your phone.
Click to expand...
Click to collapse
same problem with e4 plus and is now hard bricked. computer recognizes it but says I need some driver is cant find and wont power up or read. downloading rsd lite and still no luck I need help
I have the same issue. We messed with the boot partition, so our computer will not recognize the device in fastboot mode. My PC will detect it as this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Battery died and everything, and tried to boot to fastboot but it wouldn't let me do it. @koop1955, RSD Lite won't detect the phone either.
Josh'sDroid said:
I have the same issue. We messed with the boot partition, so our computer will not recognize the device in fastboot mode. My PC will detect it as this:
Battery died and everything, and tried to boot to fastboot but it wouldn't let me do it. @koop1955, RSD Lite won't detect the phone either.
Click to expand...
Click to collapse
Dude.. @Funisillegal fixed his!! Be on the lookout for his thread to the fix
@Funisillegal hasn't posted his solution yet
But, if it helps... I had this issue a few years ago with my LG L70. I used Linux to fix it, but since it was a frequent issue with L70's users I had the stock aboot.img for my device.
@bcrichster could you please get the stock aboot.img for us?
@Funisillegal, is this what you did to fix your problem?
Josh'sDroid said:
@Funisillegal hasn't posted his solution yet
But, if it helps... I had this issue a few years ago with my LG L70. I used Linux to fix it, but since it was a frequent issue with L70's users I had the stock aboot.img for my device.
@bcrichster could you please get the stock aboot.img for us?
@Funisillegal, is this what you did to fix your problem?
Click to expand...
Click to collapse
aboot.img.. Isn't that part of the modem images? All available images are in the stock FW
Sent from my Moto E (4) Plus using Tapatalk
bcrichster said:
aboot.img.. Isn't that part of the modem images? All available images are in the stock FW
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
I completely bricked my device lol.
I used a virtual machine, plugged my device to the computer, then selected the device in the virtual machine. Then the command
Code:
sudo gdisk -l /dev/sdb
wouldn't work so I closed VMWare abruptly. Now Windows will "recognize" the device as this:
:crying:
EDIT:
Followed @BoBo Rich's thread and my PC will recognize the device now.
Why'd tf did you close a terminal abruptly? NEVER DO THAT, just wait for the error closing and finish.. Aww chit.. Did ya try to do my fastboot list I posted in AF, with the proper firmware pkg before that gdisk cmd thing??
Josh'sDroid said:
I completely bricked my device lol.
I used a virtual machine, plugged my device to the computer, then selected the device in the virtual machine. Then the command
Code:
sudo gdisk -l /dev/sdb
wouldn't work so I closed VMWare abruptly. Now Windows will "recognize" the device as this:
:crying:
EDIT:
Followed @boborich's thread and my PC will recognize the device now.
Click to expand...
Click to collapse
I'm sorry man, but I can't read Spanish well, Lol.
Sent from my Moto E (4) Plus using Tapatalk
bcrichster said:
Why'd tf did you close a terminal abruptly? NEVER DO THAT, just wait for the error closing and finish..
Click to expand...
Click to collapse
I'm a noob lol
bcrichster said:
Aww chit.. Did ya try to do my fastboot list I posted in AF, with the proper firmware pkg before that gdisk cmd thing??
Click to expand...
Click to collapse
Nope. Phone won't boot on fastboot mode. So, Windows won't detect it as a fastboot device.
bcrichster said:
I'm sorry man, but I can't read Spanish well, Lol.
Click to expand...
Click to collapse
Don't worry. Sometimes my English won't be perfect as I'd wish it was lol.
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20170425
Rsdlite will not work download xiaomiflashtool for communication to boot sector on hard bricked (device that doesn't power on). Brichster has links up to download factory image for our devices. Now this was done on an XT1776 Qualcomm Owens device from boost Mobile. I have been out of town and will not return to my PC where I have location for USB Bulk drivers that will allow your Windows based PC to communicate to you dead device. My wife is currently uploading drivers to my Google drive and once completed I'll update with those. Second is a USB cable you can sacrifice because the next step with be to cut open shielding and jump power wire. That will allow you communication with PC once drivers are installed. It will the start showing which comm your phone is connected to. That's the hardest part. Once your phone is showing logo in middle of screen you have officially connected to deep boot section. Take zip. File you aquirred from brichster and miflashtool will install sorry I could provide drivers at this moment but Microsoft will not find them not will you be able to install them give me a couple of hours to out together tutorial once I receive drivers her in a couple hours
Attaching the blankflash zip file for the board_id=134, and it uses the latest bootloader from june update : "MBM-NG-VBD.40-0-g7ba36". It will work only for board_id=134 (which is the owens platform).
Please search for blankflash to see the exact process involved. This will get you only upto fastboot. After that you need to know how to use fastboot to restore stock (search forums).
In the latest versions of qboot the "programmer.mbn" is inside the "singleimage.bin". You can extract it for use with other tools from "singleimage.bin" if you are familiar with these files.
morchu said:
Attaching the blankflash zip file for the board_id=134, and it uses the latest bootloader from june update : "MBM-NG-VBD.40-0-g7ba36". It will work only for board_id=134 (which is the owens platform).
Please search for blankflash to see the exact process involved. This will get you only upto fastboot. After that you need to know how to use fastboot to restore stock (search forums).
In the latest versions of qboot the "programmer.mbn" is inside the "singleimage.bin". You can extract it for use with other tools from "singleimage.bin" if you are familiar with these files.
Click to expand...
Click to collapse
Where tf you just come from?! Lol, nice find! And thank you greatly for sharing, this should be a great help for ppl
morchu said:
Attaching the blankflash zip file for the board_id=134, and it uses the latest bootloader from june update : "MBM-NG-VBD.40-0-g7ba36". It will work only for board_id=134 (which is the owens platform).
Please search for blankflash to see the exact process involved. This will get you only upto fastboot. After that you need to know how to use fastboot to restore stock (search forums).
In the latest versions of qboot the "programmer.mbn" is inside the "singleimage.bin". You can extract it for use with other tools from "singleimage.bin" if you are familiar with these files.
Click to expand...
Click to collapse
you wouldnt happen to have one of these for a moto e4 plus with msm 8920 would you? i bricked my phone as well.
I keep receiving the following error from the qboot utility. Any suggestions, @morchu?
Code:
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 0.002] ...cpu.id = 134 (0x86)
[ 0.002] ...cpu.sn = 4150985471 (0xf76b02ff)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.006] ...filename = singleimage.pkg.xml
[ 0.008] Loading programmer
[ 0.008] ...filename = programmer.mbn
[ 0.009] Sending programmer
[ 1.011] ERROR: sahara_download()->IO error
[ 1.011] Check qboot_log.txt for more details
[ 1.012] Total time: 1.013s
[ 1.013]
[ 1.013] qboot version 3.40
[ 1.013]
[ 1.013] DEVICE {
[ 1.014] name = "\\.\COM3",
[ 1.014] flags = "0x64",
[ 1.014] addr = "0x61FE5C",
[ 1.014] sahara.current_mode = "0",
[ 1.014] api.buffer = "0xFA6020",
[ 1.014] cpu.serial = "4150985471",
[ 1.014] cpu.id = "134",
[ 1.014] cpu.sv_sbl = "1",
[ 1.014] cpu.name = "MSM8917",
[ 1.014] storage.type = "eMMC",
[ 1.014] sahara.programmer = "programmer.mbn",
[ 1.014] api.bnr = "0x6F6000",
[ 1.014] }
[ 1.014]
[ 1.014]
[ 1.014] Backup & Restore {
[ 1.014] num_entries = 0,
[ 1.014] restoring = "false",
[ 1.014] backup_error = "not started",
[ 1.014] restore_error = "not started",
[ 1.014] }
FAILED: qb_flash_singleimage()->sahara_download()->IO error
lowrck said:
you wouldnt happen to have one of these for a moto e4 plus with msm 8920 would you? i bricked my phone as well.
Click to expand...
Click to collapse
Umm.. That IS for our Moto E4 Plus 'owens' devices
bcrichster said:
Umm.. That IS for our Moto E4 Plus 'owens' devices
Click to expand...
Click to collapse
So which devices have chipset 8917 and which have 8920? I was under the impression all variants of the e4 plus were 8920... However, It appears the blankflash file posted is to service 8917
---------- Post added at 07:08 PM ---------- Previous post was at 07:00 PM ----------
As far as the qualcomm variants that is
wswjw said:
So which devices have chipset 8917 and which have 8920? I was under the impression all variants of the e4 plus were 8920... However, It appears the blankflash file posted is to service 8917
---------- Post added at 07:08 PM ---------- Previous post was at 07:00 PM ----------
As far as the qualcomm variants that is
Click to expand...
Click to collapse
You won't likely find stuff for 8920 because our 8920 is built on an 8937 chip anyways.. Yeah I know, this is strange as hell to me too and I been in Android for a good minute.. Lol. But the program is worth trying because it'll either work or won't.. But is ya do some crazy math.. 8937-8920=8917.. May be weird but still worth a shot cuz it won't brick it further.. You're already in a heap of trouble if you need that tool so, why not? I know someone who used a Xiaomi flashtool to fix his when he flashed a nicklaus FW (MediaTek) on his owens (Qcom).. He had nothing more to lose so it was worth the effort
bcrichster said:
You won't likely find stuff for 8920 because our 8920 is built on an 8937 chip anyways.. Yeah I know, this is strange as hell to me too and I been in Android for a good minute.. Lol. But the program is worth trying because it'll either work or won't.. But is ya do some crazy math.. 8937-8920=8917.. May be weird but still worth a shot cuz it won't brick it further.. You're already in a heap of trouble if you need that tool so, why not? I know someone who used a Xiaomi flashtool to fix his when he flashed a nicklaus FW (MediaTek) on his owens (Qcom).. He had nothing more to lose so it was worth the effort
Click to expand...
Click to collapse
Yeah I will try anything.. I keep getting Sahara download error when I run the qboot blankflash. Ive tried holding vol + and power when executing the bat or just vol + or clicking the bat file continuously as I read in some other moto bricked device threads, but to no avail.
I also tried the mi flash tool but kept getting an error it couldn't find programmer within the firmware path. Which was one I'd downloaded from a post of yours on another forum I believe. I've heard altering the flash cable might b necessary in order to get it to work, but im not certain in what way.
So it's looking pretty bleek at this point but I'm not giving up hope yet lol
wswjw said:
Yeah I will try anything.. I keep getting Sahara download error when I run the qboot blankflash. Ive tried holding vol + and power when executing the bat or just vol + or clicking the bat file continuously as I read in some other moto bricked device threads, but to no avail.
I also tried the mi flash tool but kept getting an error it couldn't find programmer within the firmware path. Which was one I'd downloaded from a post of yours on another forum I believe. I've heard altering the flash cable might b necessary in order to get it to work, but im not certain in what way.
So it's looking pretty bleek at this point but I'm not giving up hope yet lol
Click to expand...
Click to collapse
Sahara?! OMG, get rid of that iCrap and use something better for Android, like Linux.. Since Android is actually MADE from Linux, it's ur best bet. All hate/bias aside tho, Mac is near useless with Android stuff, basically night vs day in comparison. Some stuff works but most won't for Android. Oh, and only use MS Windows for programs that have no Linux equivalent..
Edit: the mi flash tool needs a modified USB cord and Windows OS..
Sent from my Moto E (4) Plus using Tapatalk
View attachment 5357205
oneplus 6/6t 都可用
警告！不当操作可能会导致手机变砖！
-
20210822 updata
-
project address : https://github.com/edk2-porting
and
Tool download :https://drive.google.com/drive/folders/1GrX9JTVpKwo3WNshqIljPRc9Q6dPJDJJ?usp=sharing
boot download : https://github.com/edk2-porting/edk2-sdm845/releases
drives download : https://github.com/edk2-porting/WOA-Drivers/archive/refs/heads/main.zip
-
Installation tutorial
new tutorial!(English) https://forum.renegade-project.org/t/faq/95
-
article(Chinese) : https://forum.renegade-project.org/t/6-windows/194
-
Device support status
Renegade Project
Renegade Project
renegade-project.org
-
The drive is gradually improving
有问题我会不定期来看的，欢迎提问。
Questions are welcome
It seems better to be merged with the post https://forum.xda-developers.com/t/os-windows-on-arm-polaris.4325377/
la0pe0Ue said:
It seems better to be merged with the post https://forum.xda-developers.com/t/os-windows-on-arm-polaris.4325377/
Click to expand...
Click to collapse
and that thread is locked-moment someone comes up with something groundbreaking or unique it gets shut down-no wonder so much less now on xda (x stands for cut or reduced)
I installed Windows according to this guide and it works.
Mazoch said:
I installed Windows according to this guide and it works.
Click to expand...
Click to collapse
hiow did u do it im keep getting stuck at were u have to enable test mode for divers but the uefi drive dose not let me acces it and help would be greatful thanks my phone is mix2s
Chris3445 said:
hiow did u do it im keep getting stuck at were u have to enable test mode for divers but the uefi drive dose not let me acces it and help would be greatful thanks my phone is mix2s
Click to expand...
Click to collapse
It's been a while since my installation, and frankly I don't remember much about it. Describe your problem in more detail. Rather, you've definitely made a mistake.
Mazoch said:
It's been a while since my installation, and frankly I don't remember much about it. Describe your problem in more detail. Rather, you've definitely made a mistake.
Click to expand...
Click to collapse
So my problem is i do all the steps in the guide were I get stuck is at the part were u have to do the bcdedit for the test mode to trun its one of the last steps be for u can boot up windows like i made the esp partition correctly like I use parted on the computer format both like resized the partition the user data partition made the windows partition and then the ESP partition and then after that part I do the Windows installation where you you know do the install that when thing then the drivers and then before the drivers you have to do that BCD edit for the for the boot files and then like every time I try to open the EFI partition like double click on it with a mouse it says something about security that I don't have permissions and then I try to left click go to properties and then there's no security Tab the uefi partition just wont let me acces it at all I just dint now what step im doing wrong thanks for the reply
Did touch screen work on mi mix 2s cuz i got windows to load but touch dose not work I installed all the divers i dont if its cuz i didnt flash that devcfg file i just did now im redeploying window's and its drivers
I was able to get it I have it fully working
Chris3445 said:
I was able to get it I have it fully working
Click to expand...
Click to collapse
Cool, sorry I didn't help, but I completely forgot about your problem. I'm glad it worked out for you
Mazoch said:
Cool, sorry I didn't help, but I completely forgot about your problem. I'm glad it worked out for you
Click to expand...
Click to collapse
Thanks man the only thing I have a issues with is pluging usb mouse and key bord do u now if there is any way to fix that. Its ok it tought me alot wen trying to install windows on it tho
Chris3445 said:
Thanks man the only thing I have a issues with is pluging usb mouse and key bord do u now if there is any way to fix that. Its ok it tought me alot wen trying to install windows on it tho
Click to expand...
Click to collapse
Unfortunately there is no OTG support for our phone, for the time being you can forget about it. It's also impossible to transfer video with a USB-C cable. Currently, this Windows is such more of a curiosity than a useful system
Do u have usb working I think i was useing tue wrong boot loader or something cuz the newer bootloader works really well with usb there is a way to get usb c to displayed to a monitor i seen. It on telegram and I did fet usb to work its pretty usable for now just not sound yet this project is really dope tho u have to say
I also was wondering if there was a way to flash the boatloader to the phone so i dont have to keep pluging it in the computer
Question,
When trying to reboot to Windows it will eventually blue screen with the message : Stop Code: Driver PNP WATCHDOG. I read thats because I have not flashed the file : http://files.renegade-project.org/devcfg-polaris_FixTS.img
When I try I get the below:
Warning: skip copying devcfg_ab image avb footer (devcfg_ab partition size: 0, devcfg_ab image size: 38444).
Sending 'devcfg_ab' (37 KB) OKAY [ 0.008s]
Writing 'devcfg_ab' OKAY [ 0.004s]
Finished. Total time: 0.031s
Assume the Warning is the problem, I tried resetting everything to stock with the mi flash tool. This was great for my Chinese language skills but the warning still shows when I try to flash.
other laptop, different cable, same thing.
Any advice ?