Develop Bugs

CyanogenMod 10.1 - Beta 4 - Discussion thread / Bug report

{
"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"
}
Opening this thread in order for the users to post their issues here instead of the development section or CM10 bug report thread.
This thread refers to discussions/bug reports for CM10.1 (Android 4.2.2) released by arco68 here.
As usual, it would be best to keep an organized fashion of your bug reports for the developers to easily spot them and maybe fix them.
On behalf of the SGW users, big thanks to arco68 and the CyanogenMod Team!
Great job, guys!
Note: bugs concerning custom kernels are to be reported into the corresponding threads! Please, don't post them here.
In order to avoid posting bugs that are not actually bugs, please, make sure you follow this little tutorial before upgrading/installing CM10.1:
For installation, first, make sure you got CM10.1 ROM and the correct Gapps on your External SD Card. Both can be found in the Mirrors section below.
After that, enter CWM and:
select "wipe data / factory reset"
go to "mounts & storage" and format /system. This is extremely important!
under the same menu, format /sdcard (be careful NOT to format /external_sd by mistake)*
install CM10.1 (from the external sd)
install Gapps for JB+ (from the external sd)
reboot your phone
* On newer CWM Recovery versions, you might find the internal memory mounted as /sdcard0 and the external one as /sdcard1. For this case, make sure you don't format /sdcard1 by mistake.
Please, note that every step of this tutorial is mandatory!
For apps backup & restore using Go Backup Pro, please, follow the tutorial below, step by step:
For Backup
1. Make sure you have an external SD card inserted
2. Download Go Backup Pro (of course)
3. Enter the app and go to Settings (from the 3 vertical dots on the right side of the screen)
4. Make sure that for the Backup Path, you have selected External storage (if I'm not mistaken, this is the default setting anyway, but it's good to confirm, just in case)
5. Go back and go to New/Restore Backup section
6. Click Batch Backup (bottom left of the screen)
7. Select what you want to backup*
*Tip: to select/unselect all User Data, all System Settings etc, you have a checkbox on the same row with the actual User Data or System Settings texts.
8. Click Start Backup
9. Wait for it to finish and click Finish
For Restore
1. Assuming that by now you already have a backup to restore, go to New/Restore Backup section again
2. Click Batch Restore
3. Now, pay attention to the User Applications section of that screen. Right underneath the User Application text, you have an option that says "Restore Content".
4. Click on "APK + Data" from Restore Content and select "Restore app only". Now the Restore Content section will show only APK.
5. Uncheck the apps for which you need app data. Those apps won't be restored, for now. Please, go on with the tutorial.
5. Click Start Restore
6. Wait for it to finish and click Finish
7. Now that we chose what apps we want to be restored without app data, let's go back and enter New/Restore Backup section (yeah, again ).
8. Click Batch Restore
9. Uncheck everything*.
*Tip: to select/unselect all User Data, all System Settings etc, you have a checkbox on the same row with the actual User Data or System Settings texts
10. Now, pay attention to the User Applications section of that screen. Right underneath the User Application text, you have an option that says "Restore Content".
11. Click on "APK" from Restore Content and select "Restore app and data". Now the Restore Content section will show APK+ Data.
10. Check only the apps for which you DO need app data to be restored (the ones that were left unrestored from last time ).
11. Click Start Restore
12. Wait for it to finish and click Finish.
How to post a bug report:
Copy-paste the lines below in your post, filling up the required information:
HTML:
[B]Version:[/B] CM10.1 - Beta 4
[B]App/Game/Subject:[/B] WRITE HERE SUBJECT
[B]Bug title:[/B] WRITE HERE BUG TITLE
[B]Probability of occurrence:[/B] WRITE HERE "LOW/MEDIUM/HIGH" (depending on how often the bug occurs)
[B]Description:[/B] WRITE HERE DESCRIPTION
Mirrors:
CM10.1 Beta 4 20140509 (MEGA): here
md5sum: c7e9114d760c0e924919b1be95425048
Gapps 20140507 JB+ (MEGA): here
md5sum: b0d6e6b62cb9149aea5de2531026f33a
Changelog Gapps:
Changelog Gapps 20140507:
* Google Search v3.4.16.1149292.arm
* Google Maps v8.0.0
* Hangouts v2.1.100(1151589-30)
* Google Play Services v4.3.25(1117461-034)
* Google Play Store v4.6.17
* Google Text-to-Speech Engine v3.0.11.1070024
Changelog Gapps 20140209:
* Google Maps v7.6.0
* Hangouts v2.0.303 (1004807-30)
* Google Play Services v4.1.32 (978161-34)
* Google Search v3.2.17.1009776.arm
Changelog Gapps 20131214:
* Google Maps v7.5.0
* Gmail v4.7.1 (946962)
* Google Play Services v4.0.34 (924341-34)
* Google Play Store v4.5.10
* Google Search v3.1.24.941712.arm
* Hangouts v2.0.217 (944332-30)
* Talkback Service v3.5.1
* Google Text-to-speech v2.4.3.864779
Changelog Gapps 20131001:
* Gmail v4.6 (836823)
* Google Search v2.8.8.849369.arm
* Google Hangouts v1.2.018 (849105-30)
Changelog Gapps 20130917:
* Google Maps v7.2.0
Changelog Gapps 20130825:
* Google Search v2.7.9.789824.arm
* Google Hangouts v1.1.2.778356
Changelog Gapps 20130817:
- Google+ (can be redownloaded from Google Play Store, if needed)
* Google Play Store v4.3.11
* Google Maps v7.1.0
Changelog Gapps 20130814:
+ Google Hangouts v1.1.1.753199**
+ Google Maps v7.0.2**
* Hangouts libs
* Google Play Services v3.2.25 (761454-34)
* Google Play Store v4.3.10
+ Google+ v4.0.2.48854689
**Re-added to the new base package from goo.im
Changelog Gapps 20130726:
* Google Hangouts v1.1.1.753199
Changelog Gapps 20130718:
* Google Play Services v3.1.59 (736673-34)
* Google Maps v7.0.2
Changelog Gapps 20130715:
* Google Talkback Service v3.4.0
Changelog Gapps 20130712:
* Google Maps v7.0.1
Changelog Gapps 20130630:
* fixed Hangouts video calling FC
Changelog Gapps 20130628:
* Google Search v2.6.7.721924.arm
* Gmail v4.5.2-714156
Changelog Gapps 20130624:
+ Google Street View (Google Maps addon) v1.8.1.2
+ minor changes
Changelog Gapps 20130612:
+ Gmail v4.5-694836 (the new, beautiful Gmail app)
+ Google Maps v6.14.4
* Google Play Services v3.1.36 (669520-34)
* Google Play Store v4.1.6 (the new Google Play Store)
* Google Search v2.5.8.675703 (the new Google Search with Google Now)
* Google Hangouts (ex Google Talk) v1.0.2.695251
* Google Talkback Service v3.3.2
+ means that the app was newly added
* means that the app was upgraded by replacing it with the newer version
- means that the app was removed
To enable Developer Options: go to Settings -> About Phone and tap the Build Number 7 times to enable Developer Options.
To enable Advanced Reboot options: go to Settings -> Developer Options and check the Advanced Reboot box.
Please, see the screens below for more information.
To swap memories (internal with external SD Cards) in Alpha 3 and above without modifying the vold.fstab file, go to /System/build.prop using any File Explorer with root privileges (recommended X-Plore) and change from 0 to 1 in the code below*:
Before
Code:
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=[COLOR="Blue"]0[/COLOR]
After
Code:
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=[COLOR="Red"]1[/COLOR]
*Thanks to Madridii for this.
Videos
Bugs reported/still occurring so far (Beta 3):
1. Camera/Gallery (To be confirmed in Beta 4)
Camera/Gallery app becomes unresponsive when locking&unlocking the screen multiple times (about 4 times in my tests). After that, if the user chooses to force close the Gallery app, when entering the Camera app again, he will be prompted with the following error message: "Can't connect to the camera".
Please, see the attached screenshot and the log below for more info.
Code:
[ 08-05 15:13:30.010 441: 456 W/ActivityManager ]
Activity idle timeout for ActivityRecord{41225ca0 u0 com.android.gallery3d/com.android.camera.CameraLauncher}
[ 08-05 15:13:31.521 441: 503 I/InputDispatcher ]
Application is not responding: AppWindowToken{414fc260 token=Token{41691380 ActivityRecord{41225ca0 u0 com.android.gallery3d/com.android.camera.CameraLauncher}}} - Window{4122f110 u0 com.android.gallery3d/com.android.camera.CameraLauncher}. It has been 5003.1ms since event, 5001.2ms since wait started. Reason: Waiting because the focused window has not finished processing the input events that were previously delivered to it.
[ 08-05 15:13:31.531 441: 503 I/WindowManager ]
Input event dispatching timed out sending to com.android.gallery3d/com.android.camera.CameraLauncher
[ 08-05 15:13:31.621 441: 503 I/Process ]
Sending signal. PID: 5350 SIG: 3
[ 08-05 15:13:31.621 5350: 5355 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:31.701 5350: 5355 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:31.701 441: 503 I/Process ]
Sending signal. PID: 441 SIG: 3
[ 08-05 15:13:31.701 441: 444 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:31.882 143: 5647 E/CAM_FD ]
cam_conf: In config thread
[ 08-05 15:13:31.992 441: 503 I/Process ]
Sending signal. PID: 553 SIG: 3
[ 08-05 15:13:31.992 553: 560 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:32.002 441: 444 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:32.002 441: 503 I/Process ]
Sending signal. PID: 656 SIG: 3
[ 08-05 15:13:32.002 656: 670 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:32.042 553: 560 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:32.092 656: 670 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:32.212 441: 443 D/dalvikvm ]
GC_CONCURRENT freed 1916K, 21% free 10090K/12716K, paused 4ms+7ms, total 97ms
[ 08-05 15:13:32.212 441: 503 D/dalvikvm ]
WAIT_FOR_CONCURRENT_GC blocked 65ms
[ 08-05 15:13:32.422 441: 503 D/dalvikvm ]
GC_EXPLICIT freed 777K, 21% free 10132K/12716K, paused 4ms+5ms, total 91ms
[ 08-05 15:13:32.632 441: 1243 E/Sensors ]
type : 0, deley : 66667000
[ 08-05 15:13:32.632 441: 1242 E/Sensors ]
type : 0, deley : 20000000
[ 08-05 15:13:33.003 441: 503 I/Process ]
Sending signal. PID: 1051 SIG: 3
[ 08-05 15:13:33.003 1051: 1056 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:33.103 1051: 1056 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:33.113 441: 503 E/ActivityManager ]
ANR in com.android.gallery3d (com.android.gallery3d/com.android.camera.CameraLauncher)
Reason: keyDispatchingTimedOut
After rendering the Panorama shots, when the camera returns to the Panorama Mode for the user to take another panoramic shot, the camera preview is flickering. This happens only if the Auto-Rotate function is ON and the screen in Portrait mode. With the Auto-Rotate OFF, this bug does not occur.
Please, see the attached screenshot for, hopefully, more info on this.
Camera/Gallery app becomes unresponsive when taking a picture, sliding left to see the picture and tapping on it to see it in "full screen" then locking the screen for about 10 seconds. After that, if the user chooses to force close the Gallery app, when entering the Camera app again, the user will be prompted with the following error message: "Can't connect to the camera". Please, see the attached screenshot for more info.
Setting the light exposure to 4 or -4, the icon on the bottom right doesn't show any number (as it does for any other value) and if slide to the left to enter the Gallery and come back to camera app, the icon appears distorted. This happens only for value "4" or "-4". Workaround: switch to any of the other values and then back to 4.
Please, see the attached screenshot for more info.
Zooming in/out doesn't work in video mode. Nothing happens when using two fingers to zoom in or out. No change in the actual image.
Please, see the log below for zooming issue.
Code:
E/QualcommCameraHardware(148): Failed to get maximum zoom value...setting max zoom to zero
2. Text cut off in photo editor (To be confirmed in Beta 4)
The text for the "straighten" option is missing the first 2-3 letters in the default photo editor (please, see the attached screenshot for more info). The options section from that screen cannot be slid more to the left to see the rest of the word.
This happens most likely because the spaces between the icons (options) from the top row of editing options don't adjust to the new screen orientation (Portrait). They look ok in Landscape mode, but it seems that the space between the icons from that row is kept the same no matter of the screen orientation, leading to some of the options not to be completely visible.
3. cLock widget not properly resizing in landscape mode (To be confirmed in Beta 4)
cLock widget does not properly resize when the launcher is set to Landscape mode (launcher auto-rotate option is ON). The widget is cut off (please, see the attached screenshot for more info). The widget looks good in Portrait mode. But when turning the screen to landscape mode, it's cut.
4. Phone encryption (To be confirmed in Beta 4)
Enabling encryption in the Security Settings will make the PIN code for the SIM card (assuming it's set to be requested) not to be requested anymore, thus making the "phone" part of the device unusable. No calls (voice or data), no SMS, no MMS can be sent or received. Workaround: make a nandroid backup before encrypting and restore it afterwards.
If the user turns off the SIM card PIN code request before performing the encryption, after it's finished, the APNs previously set will disappear and there won't be any way to re-add them manually, thus making the data connection unusable. He will be able to make voice calls and send SMS though.
After the encryption, if SIM PIN request is OFF, in the notification drawer and quicksettings panel, the user will be informed that he has no service (please, see the attached screenshots for more info) although, by going into Settings -> About Phone -> Status, he will see that the network is successfully recognized and there is definitely some service. (please, see the attached screenshot for more info on this too).
5. Random reboots after recently closing a phone call (To be confirmed in Beta 4)
From time to time, but apparently more often after recently (not immediately after) closing an incoming voice call, the phone reboots.
This does not happen with kernel 3.4.56 but it does happen with 3.4.57 so it might be because of that reverted commit.
6. Some third party camera apps don't work properly in CyanogenMod. (To be confirmed in Beta 4)
Some third party camera apps don't work with any CM version from CM9 to CM10.1. For example, Camera 360 Ultimate v4.5 works ok on stock Android 4.1.2 and 4.2.2 (tested on Nexus devices) but doesn't work properly with any CyanogenMod version. After taking a picture, the camera preview gets stuck. No change in preview when tilting the phone.
Please, see the log below from the moment when taking a picture with Camera 360. Maybe it helps solve this problem.
Code:
W/System.err( 2142): at vStudio.Android.Camera360.photo.EffectInfoFactory.getParentParam(EffectInfoFactory.java:1433)
W/System.err( 2142): at vStudio.Android.Camera360.photo.EffectInfoFactory.search(EffectInfoFactory.java:1303)
W/System.err( 2142): at vStudio.Android.Camera360.camera.logics.ModeAbstract.setEffect(ModeAbstract.java:106)
W/System.err( 2142): at vStudio.Android.Camera360.camera.logics.ModeNormal.onCameraStartPreview(ModeNormal.java:370)
W/System.err( 2142): at vStudio.Android.Camera360.camera.CameraBaseActivity.onCreate(CameraBaseActivity.java:749)
W/System.err( 2142): at vStudio.Android.Camera360.camera.CameraMain.onCreate(CameraMain.java:551)
V/QualcommCameraHardware( 143): As Auto Focus is not in progress, Cancel Auto Focus is ignored
V/QualcommCameraHardware( 143): cancelAutoFocusInternal X: 0
I/QualcommCameraHardware( 143): stopPreviewInternal X: 0
V/QualcommCameraHardware( 143): initRawSnapshot E
I/QualcommCameraHardware( 143): runframethread: waiting for preview thread to complete.
V/QualcommCameraHardware( 143): initRawSnapshot X
V/QualcommCameraHardware( 143): takePicture: X
I/ShotSingle( 143): ShotSingle::takePicture end
I/CameraHAL( 143): camera_take_picture--- rv 0
I/QualcommCameraHardware( 143): initPreview: old preview thread completed.
QualcommCameraHardware( 143): destroying MemPool record
camera_set_preview_window---: window is NULL
V/QualcommCameraHardware( 143): Overlay object NULL. returning
I/CameraClient( 143): Destroying camera 0
I/CameraHAL( 143): camera_device_close+++: device 0x1f68650
I/SecCameraHardwareInterface( 143): SecCameraHardwareInterface destroyed: pid=143
I/ShotSingle( 143): ShotSingle destroyed: pid=143
I/ShotCommon( 143): ShotCommon destroyed: pid=143
No JNI_OnLoad found in /data/app-lib/vStudio.Android.Camera360-1/libmp3lame.so
I/ActivityManager( 430): Process vStudio.Android.Camera360 (pid 2142) has died.
7. USB tethering does not work
8. USB OTG does not work. (To be confirmed in Beta 4)
XDA:DevDB Information
CyanogenMod 10.1 - Beta 4 - Discussion thread / Bug report, ROM for the Samsung Galaxy W I8150
Contributors
arsradu
ROM OS Version: 4.2.x Jelly Bean
Version Information
Status: Testing
Created 2013-09-29
Last Updated 2014-05-19

charge
Opening off the phone while charging for no reason
sorry my bad english:angel:
I got help from google translate:victory:

Re: CyanogenMod 10.1 - Discussion thread / Bug report
Why blackcat using old xistance kernel? And is he'd using latest bcmdhd wifi driver by arco or just old one? Thanks
-Sent from 4.2.2 powered i8150-

hotheabilly said:
Why blackcat using old xistance kernel? And is he'd using latest bcmdhd wifi driver by arco or just old one? Thanks
-Sent from 4.2.2 powered i8150-
Click to expand...
Click to collapse
arco new bcmdhd wifi driver dont working

The phone had been rebooting often.
Happened occasionally it rebooted even using camera and browsing the net.

I installed this rom. But sometimes, phone is locking and freezing. I am obliged to reboot.
(Sorry for my bad English)

Please rename this rom.
I'm writing this post because I read the whole thread in the Development section and it seems to me that calling this rom CM 10.1 is a bit misleading.
Sure blackcat67 may have done a bunch of work to get this out, but I don't think he has the rights to call it CM.
So I'm asking @blackcat67...PLEASE RENAME YOUR ROM.
Call it something like... [4.2.2][Blackcat]...as Xistance did for his... [4.2.1][Rootbox Alpha 1] ...but please don't call it CyanogenMod.

arsradu said:
Opening this thread in order for the people to post their issues here instead of the development section or CM10 bug report thread.
This thread refers to discussions/bug reports for CyanogenMod 10.1 posted today by blackcat67 here.
As usual it would be best to keep an organized fashion of your bug reports for the developers to easily spot them and maybe fix them.
For that, please, copy-paste this in your posts, editing it accordingly:
HTML:
[B]Version:[/B] CM10.1 - Alpha 1
[B]App/Game/Subject:[/B] WRITE HERE APPNAME
[B]Bug title:[/B] WRITE HERE BUG TITLE
[B]Description:[/B] WRITE HERE BUG DESCRIPTION
Click to expand...
Click to collapse
I Will wait for Arco's or Camcory's version:crying:

Re: CyanogenMod 10.1 - Discussion thread / Bug report
Bernedeboi said:
I Will wait for Arco's or Camcory's version:crying:
Click to expand...
Click to collapse
Do we need to close this thread?
Sent from my GT-I8150 using xda app-developers app

ipromeh said:
Do we need to close this thread?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
I don't know, man.
I would keep it open just in case someone will post another CM10.1.
There is no source thread to discuss for now, that's true. But maybe there will be soon. So, I don't know. I'll leave this decision to mods.
From my point of view, I just want a CM10.1/AOSP 4.2.2 soon, and it's not really important who posts it. So...I don't know. You decide.

Re: CyanogenMod 10.1 - Discussion thread / Bug report
arsradu said:
I don't know, man.
I would keep it open just in case someone will post another CM10.1.
There is no source thread to discuss for now, that's true. But maybe there will be soon. So, I don't know. I'll leave this decision to mods.
From my point of view, I just want a CM10.1/AOSP 4.2.2 soon, and it's not really important who posts it. So...I don't know. You decide.
Click to expand...
Click to collapse
Everybody want that, just patiently waiting. . .
-Sent from 4.2.2 powered i8150-

ipromeh said:
Do we need to close this thread?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
no, we don't have to closed this thread, The Real Devs will post their CM10.1 someday,
we just need to be patient

Re: CyanogenMod 10.1 - Discussion thread / Bug report
arsradu said:
Version: CM10.1 - Alpha 1
Click to expand...
Click to collapse
Hmmm.... How about deleting the CM10.1 version, other users would think that there IS a CM10.1 ROM for the W but its already deleted...
Ehndroix JB with S3 Style Pack :thumbup:

TiTAN-O-One said:
Hmmm.... How about deleting the CM10.1 version, other users would think that there IS a CM10.1 ROM for the W but its already deleted...
Ehndroix JB with S3 Style Pack :thumbup:
Click to expand...
Click to collapse
OK. I edited the OP so that it doesn't contain any link or info related to that post.

Re: CyanogenMod 10.1 - Discussion thread / Bug report
Its time reopen this thread.
Arco has just released CM10.1
Sent from my GT-I8150 using xda premium

Re: CyanogenMod 10.1 - Discussion thread / Bug report
Now we can continue to discuss about cm10.1 here
Sent from my GT-I8150 using xda premium

Re: CyanogenMod 10.1 - Discussion thread / Bug report
Welcome guys to CM10.1 *unbelievable happy face*
---------- Post added at 07:27 PM ---------- Previous post was at 07:26 PM ----------
I'll do a Pristine Flash tomorrow and report here.

Re: CyanogenMod 10.1 - Discussion thread / Bug report
Me too. Feel very happy and excited. I dont know how to express my happiness. Sir is really amazing. Thanks sir
Sent from my GT-I8150 using xda premium

I will flash it now :fingers-crossed:
downloaded
Edit: flashed , it is the smoothest rom ever ... It is the best from the best developer

fo the swap go here
http://forum.xda-developers.com/showpost.php?p=39749848&postcount=22

Refurbished GT-I9192 from China - problem with CM and HW differences

I've recently bought refurbished GT-I9192 from major Chinese reseller.
At the beginning everything was fine, I've upgraded ROM to official KitKat, then tried Cyanogenmod and overall I am happy.
I flashed every released Cyanogenmod daily build but versions released after 2014-07-04 doesn't work and are stuck at boot logo.
After being stuck for 35 seconds colorful dots appear on screen:
{
"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"
}
working builds:
@sekil - cm-11-20140629-NIGHTLY-serranodsxx.zip
@k2wl - cm-11-20140704-UNOFFICIAL-serranodsdd.zip and older
doesn't work:
@k2wl - cm-11-20140723-UNOFFICIAL-serranodsdd.zip and newer
(couldn't find builds between 2014-07-05 - 2014-07-23, not released?)
last_kmsg:
Code:
[ 0.190386] AXI: msm_bus_fabric_init_driver(): msm_bus_fabric_init_driver
[ 0.230703] msm_gpiomux_install: write failure: -22
[ 0.230703] msm_gpiomux_install: write failure: -22
[ 0.230734] msm_gpiomux_install: write failure: -22
[ 0.230734] msm_gpiomux_install: write failure: -22
[ 0.237784] pm8xxx-regulator pm8xxx-regulator.3: Failed to set supply 8921_l29
[ 0.237906] pm8xxx_vreg_probe: regulator_register failed: 8921_l29, rc=-16
[ 0.237906] pm8xxx_vreg_probe: error for 8921_l29, rc=-16
[ 0.246085] msm_rpm_get_status(): Status id 433 not defined for target
[ 0.246085] AXI: msm_bus_rpm_is_mem_interleaved(): Status read for interleaving returned: -22
[ 0.246085] Using interleaved memory by default
[ 0.246299] msm_rpm_get_status(): Status id 433 not defined for target
[ 0.246299] AXI: msm_bus_rpm_is_mem_interleaved(): Status read for interleaving returned: -22
[ 0.246299] Using interleaved memory by default
[ 0.246513] msm_rpm_get_status(): Status id 433 not defined for target
[ 0.246543] AXI: msm_bus_rpm_is_mem_interleaved(): Status read for interleaving returned: -22
[ 0.246543] Using interleaved memory by default
[ 0.246757] msm_rpm_get_status(): Status id 433 not defined for target
[ 0.246757] AXI: msm_bus_rpm_is_mem_interleaved(): Status read for interleaving returned: -22
[ 0.246757] Using interleaved memory by default
[ 0.246970] msm_rpm_get_status(): Status id 433 not defined for target
[ 0.246970] AXI: msm_bus_rpm_is_mem_interleaved(): Status read for interleaving returned: -22
[ 0.246970] Using interleaved memory by default
[ 0.277247] [CAMERA][msm8930_init_cam:1943] Start
[ 0.277643] [msm_camera_gpio_install:274] [Start]
[ 0.323546] qup_i2c qup_i2c.0: Could not get core_clk
[ 0.461284] smd_channel_probe_worker: allocation table not initialized
[ 0.481153] msm_iommu_dev: Could not find context <jpegd_src>
[ 0.481367] msm_iommu_dev: Could not find context <jpegd_dst>
[ 28.154921] BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:1]
I've tried flashing @F4k kernels f4ktion_1.5.7-eur_3g.zip and f4ktion_1.6.0-eur_3gds.zip but it didn't help.
I was eager to try everything so flashed @SilviuMik kernel I9192-Custom-Kernel-Silviu-31072014-Odin-NG2-KitKat.tar.rar onto clean Cyanogenmod and it DID boot successfully but on Cyanogenmod's first-time-wizard-screen got into loop of messages "dialer app stopped".
I reckon some changes in kernel sources made in July have caused mentioned problems.
Moreover I've discovered that my refurbished phone has slightly different hardware from the original version.
Difference lies in CPU which is MSM8930 1.2GHz but original has MSM8960 1.7GHz. I guess rest of hardware is the same as the new phone have.
Does anybody know which git change should I revert to build working ROM?

Juan9066 said:
[/IMG]
Click to expand...
Click to collapse
My kernel is for stock roms not AOSP

SilviuMik said:
My kernel is for stock roms not AOSP
Click to expand...
Click to collapse
Let's say it was act of desperation

Juan9066 said:
Let's say it was act of desperation
Click to expand...
Click to collapse
When i am on stock roms and check Power saving enabled i too get "only" 1200 Mhz , if i uncheck my CPu goes up to 1700
And as i remember all S4 mini variants have 8930

SilviuMik said:
When i am on stock roms and check Power saving enabled i too get "only" 1200 Mhz , if i uncheck my CPu goes up to 1700
And as i remember all S4 mini variants have 8930
Click to expand...
Click to collapse
I guess you're right about 8930.
It's impossible to set on my phone CPU frequency above 1188 MHz using CM's Performance -> Processor options.
Could you compare yours Antutu CPU info page with mine?

Juan9066 said:
I guess you're right about 8930.
It's impossible to set on my phone CPU frequency above 1188 MHz using CM's Performance -> Processor options.
Could you compare yours Antutu CPU info page with mine?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=54656284&postcount=15
Don`t have any other screens atm, my phone is charging now
For the sake of curiosity ... try my rom and see how your CPU is . If u want of course

SilviuMik said:
http://forum.xda-developers.com/showpost.php?p=54656284&postcount=15
For the sake of curiosity ... try my rom and see how your CPU is . If u want of course
Click to expand...
Click to collapse
I've just tried your ROM and is working good.
CPU has still max frequency at 1188 MHz and info from Antutu and CPU-Z is the same as it was on CM.
After enabling "Power saving" option CPU frequency was locked at max 988 MHz.
When it comes to user experience CM is more smooth and I find it performance-wise superior than stock ROM
Just noticed your Antutu score which is 22443. My phone scored 14791 :|

Juan9066 said:
I've just tried your ROM and is working good.
CPU has still max frequency at 1188 MHz and info from Antutu and CPU-Z is the same as it was on CM.
After enabling "Power saving" option CPU frequency was locked at max 988 MHz.
When it comes to user experience CM is more smooth and I find it performance-wise superior than stock ROM
Click to expand...
Click to collapse
That is REALLY strange with your CPU ...
I have no idea what motherboard/cpu u got lol

I have bought a total of 9 phones in China. I9100, 9100G, S3 mini. 6 were fakes but very very close. Eventually something didn't work. Wouldn't be surprised if the processor actually in the machine you have goes that high.

d855 hard brick Qualcomm 9008

Hello everyone . i have really bad problem .. i bricked my phone now it's looking '' Qualcomm 9008''
i tried this topic : http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091
it's not helping me cose it's error : How to fix “No response from the device. Check PMIC first and
if still boot problem, replace AP.”
Really who will fix it . i will pay 20$..
Can anyone help me ?

slyman1 said:
Hello everyone . i have really bad problem .. i bricked my phone now it's looking '' Qualcomm 9008''
i tried this topic : http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091
it's not helping me cose it's error : How to fix “No response from the device. Check PMIC first and
if still boot problem, replace AP.”
Can anyone help me ?
Click to expand...
Click to collapse
MAn, read my post here! the problem is not your phone but the loader you use wich is not good. it happened with me until I used the loader by willcracker.
http://forum.xda-developers.com/lg-g3/help/lg-g3-hardbrick-f-400l-t3352249

majorak said:
MAn, read my post here! the problem is not your phone but the loader you use wich is not good. it happened with me until I used the loader by willcracker.
http://forum.xda-developers.com/lg-g3/help/lg-g3-hardbrick-f-400l-t3352249
Click to expand...
Click to collapse
thank you for reply bro. i tried all but my problem is that :
{
"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"
}
When i try use Lg Smart boot diag it's give me error such :
Code:
>> ---------------------------- Start Logging ----------------------------
>> USB Status : Qualcomm HS-USB QDLoader 9008 (COM48)
>> Ready to access the target board...
>> BootLoader File : LGD850_AATT_ATT.mbn
>> 1. Model : LGD850 , 2. Suffix : AATT , 3. Operator : ATT
>> Bootloader : LGD850_AATT_ATT.mbn
>> AP Chip : MSM8974_G3 , BootLoader : LGD850_AATT_ATT.mbn
>> Trying Connection To Device with sahara protocol for AP Chip.
>> Successfully Connection To Device with sahara protocol for AP Chip.
>> connected with Sahara Protocol successfully.
>> Loading flash to SYS_IMEM.
>> Loading 0 Kbytes to SYS_IMEM.
>> Loading 4 Kbytes to SYS_IMEM.
>> Loading 8 Kbytes to SYS_IMEM.
>> Loading 12 Kbytes to SYS_IMEM.
>> Loading 16 Kbytes to SYS_IMEM.
>> Loading 20 Kbytes to SYS_IMEM.
>> Loading 24 Kbytes to SYS_IMEM.
>> Loading 28 Kbytes to SYS_IMEM.
>> Loading 32 Kbytes to SYS_IMEM.
>> Loading 36 Kbytes to SYS_IMEM.
>> Loading 40 Kbytes to SYS_IMEM.
>> Loading 44 Kbytes to SYS_IMEM.
>> Loading 45 Kbytes to SYS_IMEM.
>> Successfully Loaded to SYS_IMEM.(Total 45 Kbytes)
>> Flash Image was normally loaded to SYS_IMEM.
>> Checking for device status.
>> [Verifying Hello Protocol]
>> Sending Hello request 0 time(s).
>> Sending Hello request 1 time(s).
>> Sending Hello request 2 time(s).
>> Sending Hello request 3 time(s).
>> Sending Hello request 4 time(s).
>> Sending Hello request 5 time(s).
>> Sending Hello request 6 time(s).
>> Sending Hello request 7 time(s).
>> Sending Hello request 8 time(s).
>> Sending Hello request 9 time(s).
>> Failed to get response for Hello request.
>> failed to response for Hello & Security.
>> no response to target device.
>> failed to connect to flash bootloader.
>> AP Chip is not working normally.
>> Saved Log File(LOG_LGD850_AATT_ATT_20160417_045536.txt) successfully.

I know this problem. You need to remove cable and. Battery an wait for phone to switch off emergency mode.
Than use the good boardiag 2.99a . all boardiag 2.99a showed me this msg.
Did you tried the willcracker:
http://forum.xda-developers.com/attachment.php?attachmentid=3357280&d=1433975169
And have you installed the qualcomm drivers (not lg ones)
---------- Post added at 03:47 PM ---------- Previous post was at 03:47 PM ----------
Check port and drivers

majorak said:
I know this problem. You need to remove cable and. Battery an wait for phone to switch off emergency mode.
Than use the good boardiag 2.99a . all boardiag 2.99a showed me this msg.
Did you tried the willcracker:
http://forum.xda-developers.com/attachment.php?attachmentid=3357280&d=1433975169
And have you installed the qualcomm drivers (not lg ones)
---------- Post added at 03:47 PM ---------- Previous post was at 03:47 PM ----------
Check port and drivers
Click to expand...
Click to collapse
Yeah i tried all. And i check all again again again again. Nothing change ..
if anyone will help me really i will be so happy..

slyman1 said:
Yeah i tried all. And i check all again again again again. Nothing change ..
if anyone will help me really i will be so happy..
Click to expand...
Click to collapse
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-all-variants/ try this

Anik49 said:
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-all-variants/ try this
Click to expand...
Click to collapse
i tried it too .. Thank you for reply . Please look at my log files . it above...

Really i tried all .. And bored all. Who will fix it . i will pay 20 $.. I'm really seriously .. When i will see fix it then i will pay fastly 20$.!

man, your last chance is the box ! so take it to repair chop

majorak said:
man, your last chance is the box ! so take it to repair chop
Click to expand...
Click to collapse
i think such too.. But maybe someone can help me with Teamviewer .. I think its my last chance.

slyman1 said:
i think such too.. But maybe someone can help me with Teamviewer .. I think its my last chance.
Click to expand...
Click to collapse
Maybe you have a D851? Is D855 written on the MotherBoard or its D851 instead. Those people who refurbish the G3 somehow make the device think its a D855 where its actually a D851. And when you try flashing a D855 ROM, it gets bricked.
So check the Motherboard. If its a D855, it should be written on the motherboard. And also, the D855 has two points on top of the emmc chip right underneath the camera module.

mickeyasamoah said:
Maybe you have a D851? Is D855 written on the MotherBoard or its D851 instead. Those people who refurbish the G3 somehow make the device think its a D855 where its actually a D851. And when you try flashing a D855 ROM, it gets bricked.
So check the Motherboard. If its a D855, it should be written on the motherboard. And also, the D855 has two points on top of the emmc chip right underneath the camera module.
Click to expand...
Click to collapse
i see my motherboard is d851 bro. i fixed all problem with Octoplus box.
Now phone working normally. Cose when i tried connect phone to octoplus box as 855 , phone is not connected.
But i tried connect as d851 .. all is done and i flashed d851 firmware then unlock phone.
Now i can use with sim card and no problem.. Thank you :victory:

Rooted, Unrooted, Restarted & now my phone is dead.

Hey everyone. I'm new here. Before registering i did read a lot of threads but none of them could help me.
So i will give details of what happened.
I wanted really bad to root my phone, cause i hate the blob emoji. Did it with ease, i installed TWRP and it all went fine.
Then Motorola started asking for an update, and i couldn't do it. It started to p!ss me off, then i decided to remove the root. After trying a lot of things, i did it. I removed it and the phone started normally. But, when i restarted it, it went dead.
Now i only have the LED blinking when i plug the phone on any energy source.
Consulting a couple friends, they told me i could "overwrite" Android all over again on my phone, but my PC can't recognize it. On the device manager, it appears in portuguese the following message: "Unknown USB Device (fail on requesting device descriptor), something like that. Printscreen below.
{
"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"
}
I researched a little and learned about the blankflash, but as i told you, the PC can't even recognize my device. When i try the Motorola Device Manager, it tells me that my driver is "N/A".
I hope you can understand everything i said so far. I'm ready to bury it, but i want to at least try to fix it. Thank you guys so much for reading.

Its call Hardbrick,
currently has no files that will save your Moto G5, what you can do now is to change the card that would cost around $ 200 or repair via jtag that ranges between 50 to 40 $, I hope I have helped

Yukyud said:
Its call Hardbrick,
currently has no files that will save your Moto G5, what you can do now is to change the card that would cost around $ 200 or repair via jtag that ranges between 50 to 40 $, I hope I have helped
Click to expand...
Click to collapse
Thanks, but that is totally not worthy, cause it's almost the price of a new device here in Brazil
anyways i'll look for some technical support that can repair via jtag

xlipe said:
Thanks, but that is totally not worthy, cause it's almost the price of a new device here in Brazil
anyways i'll look for some technical support that can repair via jtag
Click to expand...
Click to collapse
How did you "remove the root"
Simply click unroot in an app may unroot you by removing the su binary but the system will still remain modified
To flash an ota you need a totally unmoderated system kernel & recovery
This requires flashing the stock firmware via fastboot & to make extra sure locking the bootloader (the bootloader will only lock if everything is unmodified)
If you can no longer access the bootloader the only option for this phone at time of posting is either a motherboard replacement or re-imaging with a j-tag at a repair shop

TheFixItMan said:
How did you "remove the root"
Simply click unroot in an app may unroot you by removing the su binary but the system will still remain modified
To flash an ota you need a totally unmoderated system kernel & recovery
This requires flashing the stock firmware via fastboot & to make extra sure locking the bootloader (the bootloader will only lock if everything is unmodified)
If you can no longer access the bootloader the only option for this phone at time of posting is either a motherboard replacement or re-imaging with a j-tag at a repair shop
Click to expand...
Click to collapse
i followed instructions on Youtube, used fastboot and a stock room. But you know, certainly that alone wouldn't be enough. That's why i got bricked lol. Everything just because of the motherf*** blob emoji, i don't even like custom ROMs I will look for local support and find someone who has a Jtag so maybe it's not so dead. Thank you. Really tried everything i could, i even tried to access it on Linux. It was listed on the device list as a Qualcomm device once i prompted lsusb, but still couldn't have access to it (stuck on 'waiting for device')

blakflash is the solution
xlipe said:
i followed instructions on Youtube, used fastboot and a stock room. But you know, certainly that alone wouldn't be enough. That's why i got bricked lol. Everything just because of the motherf*** blob emoji, i don't even like custom ROMs I will look for local support and find someone who has a Jtag so maybe it's not so dead. Thank you. Really tried everything i could, i even tried to access it on Linux. It was listed on the device list as a Qualcomm device once i prompted lsusb, but still couldn't have access to it (stuck on 'waiting for device')
Click to expand...
Click to collapse
running the blakflash file is the solution, the problem is that it has not yet been filtered from motorola ami the same happened to me for testing rom, now my cell phone is a footprint

oxxo.andatti said:
running the blakflash file is the solution, the problem is that it has not yet been filtered from motorola ami the same happened to me for testing rom, now my cell phone is a footprint
Click to expand...
Click to collapse
if you don't mind, we can't keep in touch to follow updates on this, i use Telegram or whatever
i don't want to spend much money on a Android anymore. but in order to buy another phone i'll have to wait till June and it kills me :/
but i want to fix my Moto G5 anyways

Just out of curiosity
Here's what happens when i try to run blankflash
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.008] Total time: 4.008s
[ 4.008]
[ 4.008] qboot version 3.40
[ 4.009]
[ 4.009] DEVICE {
[ 4.009] name = "\\.\COM3",
[ 4.009] flags = "0x64",
[ 4.009] addr = "0x61FE5C",
[ 4.009] api.bnr = "0x2FA2B70",
[ 4.009] }
[ 4.009]
[ 4.009]
[ 4.009] Backup & Restore {
[ 4.009] num_entries = 0,
[ 4.009] restoring = "false",
[ 4.009] backup_error = "not started",
[ 4.009] restore_error = "not started",
[ 4.009] }
[ 4.009]

it is not the file for moto g5 cedric
xlipe said:
Here's what happens when i try to run blankflash
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.008] Total time: 4.008s
[ 4.008]
[ 4.008] qboot version 3.40
[ 4.009]
[ 4.009] DEVICE {
[ 4.009] name = "\\.\COM3",
[ 4.009] flags = "0x64",
[ 4.009] addr = "0x61FE5C",
[ 4.009] api.bnr = "0x2FA2B70",
[ 4.009] }
[ 4.009]
[ 4.009]
[ 4.009] Backup & Restore {
[ 4.009] num_entries = 0,
[ 4.009] restoring = "false",
[ 4.009] backup_error = "not started",
[ 4.009] restore_error = "not started",
[ 4.009] }
[ 4.009]
Click to expand...
Click to collapse
this happens because the blankflash that you are trying to execute is not compatible moto g5 cedric
esto pasa por que el blankflash que estas intentando ejecutar no es compatible moto g5 cedric
---------- Post added at 02:37 PM ---------- Previous post was at 02:33 PM ----------
xlipe said:
if you don't mind, we can't keep in touch to follow updates on this, i use Telegram or whatever
i don't want to spend much money on a Android anymore. but in order to buy another phone i'll have to wait till June and it kills me :/
but i want to fix my Moto G5 anyways
Click to expand...
Click to collapse
I am currently testing many methods, if I find the solution I will upload it. How about we create a group of whatssap to revive bike g5 cedric. Pass me your numbers to add them
actualmente estoy probando muchos metos, en caso de encontrar la solucion la subire. que tal si creamos un grupo de whatssap para revivir moto g5 cedric. pasenme sus numeros para agregarlos

oxxo.andatti said:
this happens because the blankflash that you are trying to execute is not compatible moto g5 cedric
esto pasa por que el blankflash que estas intentando ejecutar no es compatible moto g5 cedric
---------- Post added at 02:37 PM ---------- Previous post was at 02:33 PM ----------
I am currently testing many methods, if I find the solution I will upload it. How about we create a group of whatssap to revive bike g5 cedric. Pass me your numbers to add them
actualmente estoy probando muchos metos, en caso de encontrar la solucion la subire. que tal si creamos un grupo de whatssap para revivir moto g5 cedric. pasenme sus numeros para agregarlos
Click to expand...
Click to collapse
That's an amazing idea! But i strongly recommend you to create the group on Telegram, so you can invite even more users because the privacy is kept and we don't need to share our numbers. Also, because Telegram works like a charm on its desktop version!
But, if it's crucial for you to create a group on Whatsapp, please let me know. But i really think you should try Telegarm - and i forgot to mention that, on Telegram, we can share ANY kind of file, up to 1,5 GB.
Please think and answer me as soon as you can.

If you already have adb drivers installed then perhaps manually assign adb device to the undetected "unknown device", then try flashing stock with cmd, and lock the bootloader if you want to update your phone.

Exanneon said:
If you already have adb drivers installed then perhaps manually assign adb device to the undetected "unknown device", then try flashing stock with cmd, and lock the bootloader if you want to update your phone.
Click to expand...
Click to collapse
that goes beyond my knowledge

1. Go to device manager
2. Select your unknown device (your phone)
3. Right click it and select properties
4. Then go to the driver tab
5. Select update driver
6. Then select browse my computer for driver software
7. Select let me pick from a list of available drivers
8. Untick the compatible drivers checkbox
9. Select adb interface or something like that
10. Then wait for it to install
11. Open up cmd with admin permissions and flash stock, if you dont know how then look for tutorials online "how to flash moto g5 cedric stock firmware"

Exanneon said:
1. Go to device manager
2. Select your unknown device (your phone)
3. Right click it and select properties
4. Then go to the driver tab
5. Select update driver
6. Then select browse my computer for driver software
7. Select let me pick from a list of available drivers
8. Untick the compatible drivers checkbox
9. Select adb interface or something like that
10. Then wait for it to install
11. Open up cmd with admin permissions and flash stock, if you dont know how then look for tutorials online "how to flash moto g5 cedric stock firmware"
Click to expand...
Click to collapse
did you try this before or just a hint?

Guys, i found this:
https://www.techbmc.com/2017/04/How...FIL-Download-To-Unbrick-Qualcomm-devices.html
I'm trying to do it, but i accidentalyl deleted the Stock Rom so i'm downloading it again. But the servers are struggling to provide and my download speed is not good. Will report back with more news.

Exanneon said:
1. Go to device manager
2. Select your unknown device (your phone)
3. Right click it and select properties
4. Then go to the driver tab
5. Select update driver
6. Then select browse my computer for driver software
7. Select let me pick from a list of available drivers
8. Untick the compatible drivers checkbox
9. Select adb interface or something like that
10. Then wait for it to install
11. Open up cmd with admin permissions and flash stock, if you dont know how then look for tutorials online "how to flash moto g5 cedric stock firmware"
Click to expand...
Click to collapse
You do realise this person has no bootloader (hard brick)
You are just describing how to install an adb driver - he already has adb installed
---------- Post added at 01:23 AM ---------- Previous post was at 01:20 AM ----------
xlipe said:
Guys, i found this:
https://www.techbmc.com/2017/04/How...FIL-Download-To-Unbrick-Qualcomm-devices.html
I'm trying to do it, but i accidentalyl deleted the Stock Rom so i'm downloading it again. But the servers are struggling to provide and my download speed is not good. Will report back with more news.
Click to expand...
Click to collapse
This looks interesting - good luck in trying it
I don't have this device at the moment but if it allows you to reflash the bootloader just using the stock firmware files when you can't access fastboot via the phone itself then it will save alot of devices

TheFixItMan said:
You do realise this person has no bootloader (hard brick)
You are just describing how to install an adb driver - he already has adb installed
---------- Post added at 01:23 AM ---------- Previous post was at 01:20 AM ----------
This looks interesting - good luck in trying it
I don't have this device at the moment but if it allows you to reflash the bootloader just using the stock firmware files when you can't access fastboot via the phone itself then it will save alot of devices
Click to expand...
Click to collapse
thanks. still struggling with my sh!tty internet provider and MEGA download quota. lol

help url downloader file
xlipe said:
thanks. still struggling with my sh!tty internet provider and MEGA download quota. lol
Click to expand...
Click to collapse
you can pass the threads of rawprogram xml files and prog_emmc_firehose mbn for xt1671

TheFixItMan said:
You do realise this person has no bootloader (hard brick)
You are just describing how to install an adb driver - he already has adb installed
---------- Post added at 01:23 AM ---------- Previous post was at 01:20 AM ----------
This looks interesting - good luck in trying it
I don't have this device at the moment but if it allows you to reflash the bootloader just using the stock firmware files when you can't access fastboot via the phone itself then it will save alot of devices
Click to expand...
Click to collapse
You still need the device-specific FireHose files.

Shooting Star Max said:
You still need the device-specific FireHose files.
Click to expand...
Click to collapse
Would this be it?
I don't own this device anymore - just providing support

[Utility] MotoFlashPro

{
"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"
}
- = MotoFlashPro = -
Utility to flash for Motorola devices on Qualcomm processors.​
Instruction
Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive in the system.
Connect the device to your PC and set it to fastboot mod.
1. Select in the program window:
- flashfile.xml for full flashing with removal of all user data;
- servicefile.xml for flashing with all user data saved.
2. Press "Start Flash" button to start flashing.
3. When the firmware installation is finished, the device will be automatically rebooted.
The program has the following additional functions:
- reboot-bootloader - bootloader mode reboot;
- clear bootmode - fastboot mode cleaning;
- erase modemst 1/2 - modem cleaning;
- erase userdata+cache - user data and cache cleansing;
- getvar all - device information output;
- oem hw - output of information about the device equipment.
Download in Attached Files
Changelog v1.0.1:
- code optimization;
- improved output of getvar all and oem hw;
- fine aesthetic fixtures.
For the program, we thank
serg_gangubas

Thx!

+Rep
Thanks mate, this tool saved me..
I bricked my device tried Rescue and Smart Assistant tool but that one is ****..
with this tool I was able to unbrick the phone also successfully flash Brazil firmware with android 11.

Glad I could help you!

Hi, do you know how to change the software update channel?

No way. It's not Samsung. Installing firmware from another modification of the phone does not change the software update region.

ilia3367 said:
No way. It's not Samsung. Installing firmware from another modification of the phone does not change the software update region.
Click to expand...
Click to collapse
Thx mate. I was already assuming that . However there are lot of rumours regarding that. Some people are saying that it's possible..

Thanks for this! I'm rooted so the OTA updates are failing of course. I'm not 100% on what is meant by user data. Will the servicefile.xml method allow me to install (update) the latest security patch like an OTA update, not having to setup my phone again?

Mace68 said:
Thanks for this! I'm rooted so the OTA updates are failing of course. I'm not 100% on what is meant by user data. Will the servicefile.xml method allow me to install (update) the latest security patch like an OTA update, not having to setup my phone again?
Click to expand...
Click to collapse
Does anyone know the answer to this?

如果我想從高版本降級到低版本，需要解鎖引導加載程序嗎？？

Hello friends, could someone clarify for me well how is the rooting process? I am from Argentina and I do not speak English, I use the translator and we already know what that means. I would like to know the step by step to achieve the root of the team

ilia3367 said:
¡Me alegro de poder ayu
Click to expand...
Click to collapse
ilia3367 said:
¡Me alegro de poder ayudarte!
Click to expand...
Click to collapse
TengoTengo el Moto g8 plus como venía de fábrica no le he hecho nada podía instalarlo de antemano muchas gracias saludos de sonora

Hola. Te conviene buscar en tu modelo de celular. Si ya abriste el bootloader busca en Chrome como rootera moto g8 Plus o busca los foros para ese modelo.

Cris19752008 said:
Hola. Te conviene buscar en tu modelo de celular. Si ya abriste el bootloader busca en Chrome como rootera moto g8 Plus o busca los foros para ese modelo.
Click to expand...
Click to collapse

Thanks so much, works fine for me, the flash files option!

kyo11111 said:
如果我想從高版本降級到低版本，需要解鎖引導加載程序嗎？
Click to expand...
Click to collapse
本人亲测降级成功
[Guides]Downgrade from android 11 to 10
Part1:Unlock Bootlaoder step1: download and install Rescue and Smart Assistant Tool https://www.motorola.com/us/rescue-and-smart-assistant/p step2: download and install USB drivers...
forum.xda-developers.com

How do we get the most current firmware on our PC? Does motorola have a repository of the stock firmware? Can it somehow be gotten through Rescue and Smart Assistant?

cruban said:
Thx!
Click to expand...
Click to collapse
I installed : XT2201-1_HIPHI_RETEU_12_S1SH32.55-8-8_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml (European firmware Moto edge 30 pro) - Works with all installed Google applications. Multilanguage. No Chineze aplication. https://mirrors.lolinet.com/firmware/moto/hiphi/official/ RETEU
1. First :Android-SDk - WIN platform tools.
2. Extract XT2201-1_HIPHI_RETEU in c:\platform tools after install Android SDK.
3.Copy and paste "bootloader, radio" from chinese firmware in folder.
4. Open MotoFlashPro v1_0_1
5. Select "flashfile"
6 flash
(Phone need to have unlock bootloader)

Help me pls Blank flash error for me
C:\adb\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM4
[ 0.004] Detecting device
[ 0.006] ...cpu.id = 286 (0x11e)
[ 0.006] ...cpu.sn = 3644946228 (0xd9417734)
[ 0.006] Opening singleimage
[ 0.007] Loading package
[ 0.009] ...filename = pkg.xml
[ 0.011] Loading programmer
[ 0.012] ...filename = programmer.elf
[ 0.012] Sending programmer
[ 0.072] ReadFile() failed, GetLastError()=0
[ 0.372] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.378] ERROR: sahara_download()->general error
[ 0.380] Check qboot_log.txt for more details
[ 0.381] Total time: 0.382s
FAILED: qb_flash_singleimage()->sahara_download()->general error
C:\adb\blankflash>pause
Premere un tasto per continuare . . .
Help

ilia3367 said:
View attachment 5259539
- = MotoFlashPro = -
Utility to flash for Motorola devices on Qualcomm processors.​
Instruction
Pre-extract the firmware archive to either an adb&fastboot driver folder or another location on your PC if you are catching firmware from any drive in the system.
Connect the device to your PC and set it to fastboot mod.
1. Select in the program window:
- flashfile.xml for full flashing with removal of all user data;
- servicefile.xml for flashing with all user data saved.
2. Press "Start Flash" button to start flashing.
3. When the firmware installation is finished, the device will be automatically rebooted.
The program has the following additional functions:
- reboot-bootloader - bootloader mode reboot;
- clear bootmode - fastboot mode cleaning;
- erase modemst 1/2 - modem cleaning;
- erase userdata+cache - user data and cache cleansing;
- getvar all - device information output;
- oem hw - output of information about the device equipment.
Download in Attached Files
Changelog v1.0.1:
- code optimization;
- improved output of getvar all and oem hw;
- fine aesthetic fixtures.
For the program, we thank
serg_gangubas
Click to expand...
Click to collapse
Hi i downloaded the MotoFlash Pro etc etc it looks good, i have not flashed Moto G82 yet alto bootloader Unlocked and Root Magisk, but earlier today saw the RSD Lite Tool v RSD_Lite_v6.2.4 tool, it appears this is for Windows 10 & older, i am on W11 Pro, which do you thing is safer and would wiork, i did post on the MOTO G82 device section there is very little activity there, i saw some of ther vids you did on YouTube, regards Durban