Database Develop

[Q] Unmodified factory XT1068 froze during normal use. Bootloops.

Was just using my new XT1068 when it just froze and then refused to ever boot up again. The Android bluelogo on white screen appears and then goes away. Doing this again and again till the battery drains out.
Is there any solution other than returning it ?

icosahedronman said:
Was just using my new XT1068 when it just froze and then refused to ever boot up again. The Android bluelogo on white screen appears and then goes away. Doing this again and again till the battery drains out.
Is there any solution other than returning it ?
Click to expand...
Click to collapse
boot to fastboot mode and factory reset after going to recovery

but it just shows the android logo and does nothing
reefuge said:
boot to fastboot mode and factory reset after going to recovery
Click to expand...
Click to collapse
I get the following Fastboot screen:
AP Fastboot Flash Mode (S)
48.07(*) (sha-eadfa...., 2013-07-09,17:07:22)
CPU: MSM8226 CS
eMMC: 16GB Sandisk RV=07 PV=01 TY=57
DRAM: 1024 MB Elpida S4 SDRAM DIE=4Gb
Battery OK
Device is LOCKED. Status Code: 0
Connect USB Data Cable.
Selecting "Factory" or "Recovery" simply gives me the same old boot loop with the logo screen and blank alternating till batterry die-out.
What is the "Connect USB Data Cable" instruction ? Is that necessary ?

icosahedronman said:
I get the following Fastboot screen:
AP Fastboot Flash Mode (S)
48.07(*) (sha-eadfa...., 2013-07-09,17:07:22)
CPU: MSM8226 CS
eMMC: 16GB Sandisk RV=07 PV=01 TY=57
DRAM: 1024 MB Elpida S4 SDRAM DIE=4Gb
Battery OK
Device is LOCKED. Status Code: 0
Connect USB Data Cable.
Selecting "Factory" or "Recovery" simply gives me the same old boot loop with the logo screen and blank alternating till batterry die-out.
What is the "Connect USB Data Cable" instruction ? Is that necessary ?
Click to expand...
Click to collapse
ok your phone is 100% recoverable if you can still get AP fasboot flash mode
i will sort instructions to help (to follow) as several ways to fix 1st we try simple way
1) get to Ap fast boot mode (hold power and volume down until phone screen fully off and vibrates- count 1,2,3,4,5 and release release both button at same time - should be in AP fast boot mode)
2 use volume down (- ) minus to select recovery DO NOT touch power button
3) Use volume up (seems crazy but is the way) to enter recovery screen will go black
and the fallen android / red triangle comes up....
4) now hold power and quickly tap volume up... should enter recovery (this only works for lollipop) or for kitkat (use 4a)
4a)(optional for kitkat only) hold volume up and quickly tap power.... should enter recovery
5) in recovery volume down to wipe data/factory reset NOW use POWER to select (this take up to 5 mins to complete)
6) repeat with cache
7) reboot
phone should now work

no fallen android/red triangle comes up
When I enter into the AP fastboot mode and select either "Factory Reset" or "Recovery", the phone
again shows the Motorola/Android logo and starts bootlooping again.
I've attached a video of what happens when I select "Recovery" on youtube.
I don't get any fallen android/red triangle.
youtube dot com /watch?v=l_TO68t0DRs&feature=youtu.be
reefuge said:
ok your phone is 100% recoverable if you can still get AP fasboot flash mode
i will sort instructions to help (to follow) as several ways to fix 1st we try simple way
1) get to Ap fast boot mode (hold power and volume down until phone screen fully off and vibrates- count 1,2,3,4,5 and release release both button at same time - should be in AP fast boot mode)
2 use volume down (- ) minus to select recovery DO NOT touch power button
3) Use volume up (seems crazy but is the way) to enter recovery screen will go black
and the fallen android / red triangle comes up....
4) now hold power and quickly tap volume up... should enter recovery (this only works for lollipop) or for kitkat (use 4a)
4a)(optional for kitkat only) hold volume up and quickly tap power.... should enter recovery
5) in recovery volume down to wipe data/factory reset NOW use POWER to select (this take up to 5 mins to complete)
6) repeat with cache
7) reboot
phone should now work
Click to expand...
Click to collapse

icosahedronman said:
When I enter into the AP fastboot mode and select either "Factory Reset" or "Recovery", the phone
again shows the Motorola/Android logo and starts bootlooping again.
I've attached a video of what happens when I select "Recovery" on youtube.
I don't get any fallen android/red triangle.
youtube dot com /watch?v=l_TO68t0DRs&feature=youtu.be
Click to expand...
Click to collapse
Install Motorola device manager (for usb drivers) save and run
https://www.motorola.com/getmdmwin
Now download the xt1068 5.0.2 or 4.4.4 in my signature (this will restore/update or downgrade phone)
extract to desktop ONLY do NOT RUN IT yet
download modified CORRECT auto restore script and extract then copy to the xt1068 5.0.2 or 4.4.4 folder (you should now have 2 auto restore scripts)
Manually put phone into AP FASTBOOT MODE (usb cable plugged in) hold power and volume down till screen goes blank (and may vibrate) still holding count 1,2,3,4,5 and release both to get to AP Fastboot flash mode
and run
Modified auto restore script
even if error appear keep going till end (if it allows)

Thank you!
Man, thank you for this - it really saved my ass
Would have been easier if you had mentioned that your script has to be executed in an ADB environment (containing fastboot.exe) though. :good: But anyway, after studying the error messages it helped me to get my Moto G back to life instead of having to send it to service.

Bootloader / device boot issue

Hoping someone can offer some advice.
So a few days ago my Nokia 8 stopped saving pictures (it was doing this regularly after I flashed the latest (5150) build).
I rebooted the phone only it froze on the Nokia boot logo.
It wouldn't do a forced reboot via the power button, I had to just let the power drain completely to get it to do anything.
I am trying to now flash the latest qlz but I cant get the device in to Download Mode in order to flash.
If I connect it to power (plug or usb) and it gets enough power to turn on then this is what I get:
1. Power and vol+ button held down - boots to Nokia logo, freezes
2. Power and vol- button held down - stays on bootloader unlocked warning screen
3. No buttons held down - stays on bootloader unlocked warning screen
Can anyone advise?
Its almost as if my bootloader is corrupt.
If I try option (1) I do see the device listed via
Code:
adb devices
but its shown as
Code:
NBXXXXXXX unauthorized
and since I have no filesystem access to the device I cant push the key to authorise it.
Any advice humbly appreciated as I really need access to my phone now.
Thanks
Dan

dt_matthews said:
Hoping someone can offer some advice.
So a few days ago my Nokia 8 stopped saving pictures (it was doing this regularly after I flashed the latest (5150) build).
I rebooted the phone only it froze on the Nokia boot logo.
It wouldn't do a forced reboot via the power button, I had to just let the power drain completely to get it to do anything.
I am trying to now flash the latest qlz but I cant get the device in to Download Mode in order to flash.
If I connect it to power (plug or usb) and it gets enough power to turn on then this is what I get:
1. Power and vol+ button held down - boots to Nokia logo, freezes
2. Power and vol- button held down - stays on bootloader unlocked warning screen
3. No buttons held down - stays on bootloader unlocked warning screen
Can anyone advise?
Its almost as if my bootloader is corrupt.
If I try option (1) I do see the device listed via
Code:
adb devices
but its shown as
Code:
NBXXXXXXX unauthorized
and since I have no filesystem access to the device I cant push the key to authorise it.
Any advice humbly appreciated as I really need access to my phone now.
Thanks
Dan
Click to expand...
Click to collapse
The fastest way to fix it is taking to a care centre near you. or any Nokia certified store to reflash it for you. if it's out of warranty they will probably charge you ~$20

Any System update Constant Fail - Fastboot Screen

Hi All,
I'll explain this as clearly and simply as possible and hopefully someone can help :fingers-crossed:
My oem 3T ran out of power, plugged into dash charger and no led, power button held down for 10secs and entered fastboot, got to some options by holding power and volume down, but none of the recovery,wiping cache,delete everything options worked (would always go back to fastboot)
I ended up following the unbrick tutorial on here (link - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
and got it back to factory state, HOWEVER, I cannot update the OS without it going into fastboot, if I THEN turn off and turn back on holding volume down it doesn't take me back to all the options I had (wiping cache, reset system settings ect) but shows me the android logo/loading screen with something like this in yellow text:
>>>> changing to aging
then I'm back to the original state before I tried to update the OS.
Any help would be MASSIVELY appreciated! :highfive:

I think I've discovered the issue to my own problem! - my volume button is stuck on up also!!
didn't realise this with the power button held makes the phone enter fastboot mode is any case - Can't believe there was never a problem with it in the first place and I didn't need to delete absolutely everything off the phone!!!!
https://forums.oneplus.com/threads/fixed-stuck-on-fastboot-mode-no-recovery.744099/

How to stop Nokia 2.3 from auto boot when charger is plugged in?

1. Automatic boot when charger is connected, power off this Nokia 2.3 then connecting the charger is like pressing the power button, it just do a normal start, also power it down while connected to to charger still it just do a normal rebooting.
2. Factory reset is locked (settings>backup and restore>factory reset>) that function is greyed out meanwhile it's not working even if you touch for ages.
3. Build number is not working, (settings>about phone>build number) tapping this function Has to unlock developer options hence this function is not working too There's no way I can enable debugging mode.
4. Recovery boot is locked, pressing power button + Vol- it display this massage "as fastboot is locked..... your phone will restart in (3)s"....., Pressing power button + Vol+ the device just start normally,. Pressing all the three buttons device will not react at all, I tried holding these 3 buttons for 2 minutes but nothing happened.
5. No updates to fix this online currently running android 10 which means there's no android 11 patches for Nokia 2.3 to fix this issues
6. Can't root this device as almost every possibility is off.
PLEASE NOTE: THIS ANDROID 10 ROM AM USING WAS FLASHED TO THIS DEVICE BY A FRIEND MEANWHILE THE UPDATE FROM ANDROID PIE(9) TO ANDROID 10 (R) WAS DONE OFFLINE
IF THERE'S ANYWAY TO FIX THIS PLEASE ADVISE ON WHAT TO BE DONE OR IF THERE'S ANY SOFTWARE THAT CAN FIX THIS PLEASE HELP THIS IS KILLING ME .

Lin12 said:
1. Automatic boot when charger is connected, power off this Nokia 2.3 then connecting the charger is like pressing the power button, it just do a normal start, also power it down while connected to to charger still it just do a normal rebooting.
2. Factory reset is locked (settings>backup and restore>factory reset>) that function is greyed out meanwhile it's not working even if you touch for ages.
3. Build number is not working, (settings>about phone>build number) tapping this function Has to unlock developer options hence this function is not working too There's no way I can enable debugging mode.
4. Recovery boot is locked, pressing power button + Vol- it display this massage "as fastboot is locked..... your phone will restart in (3)s"....., Pressing power button + Vol+ the device just start normally,. Pressing all the three buttons device will not react at all, I tried holding these 3 buttons for 2 minutes but nothing happened.
5. No updates to fix this online currently running android 10 which means there's no android 11 patches for Nokia 2.3 to fix this issues
6. Can't root this device as almost every possibility is off.
PLEASE NOTE: THIS ANDROID 10 ROM AM USING WAS FLASHED TO THIS DEVICE BY A FRIEND MEANWHILE THE UPDATE FROM ANDROID PIE(9) TO ANDROID 10 (R) WAS DONE OFFLINE
IF THERE'S ANYWAY TO FIX THIS PLEASE ADVISE ON WHAT TO BE DONE OR IF THERE'S ANY SOFTWARE THAT CAN FIX THIS PLEASE HELP THIS IS KILLING ME .
Click to expand...
Click to collapse
Any help on this please?

[SOLVED] - Phone severely bricked

Hello,
I was on CrDoid 7.2. (Android 11) It was working normally.
I rebooted to recovery (TWRP 3.5), and flashed CrDroid 6.2 (Android 10).
And it bricked severely the phone. At startup, i get a message
"REV CHECK FAIL, DEVICE:9, BINARY:8 (DTB)"
I really think the situation is hopeless :
- impossible to reach download mode
- impossible reach recovery mode
- BixBy + Volume down + Power + plugging the cable doesn't work
- if the telephone stays plugged, i get a boot-loop (before the message "your bootloader is unlocked, please press power button to continue")
Any help is welcome but i really think i lost my phone. Quite painful. I'm not so rich.
I think the device tree of the ROM i flashed is mistaken.
I played i lost.
Jean

jean_michmich said:
Hello,
I was on CrDoid 7.2. (Android 11) It was working normally.
I rebooted to recovery (TWRP 3.5), and flashed CrDroid 6.2 (Android 10).
And it bricked severely the phone. At startup, i get a message
"REV CHECK FAIL, DEVICE:9, BINARY:8 (DTB)"
I really think the situation is hopeless :
- impossible to reach download mode
- impossible reach recovery mode
- BixBy + Volume down + Power + plugging the cable doesn't work
- if the telephone stays plugged, i get a boot-loop (before the message "your bootloader is unlocked, please press power button to continue")
Any help is welcome but i really think i lost my phone. Quite painful. I'm not so rich.
I think the device tree of the ROM i flashed is mistaken.
I played i lost.
Jean
Click to expand...
Click to collapse
Try the FRP Hijacker Tool. It has also happened to me that nothing worked anymore. The cell phone does not appear in the list, but still worked with the SC-01C and SoftBrick Fixer.

This also happened to me before, and I also couldn't get back to TWRP.
The error "REV CHECK FAIL, DEVICE:9, BINARY:8 (DTB)" means that the version of your device is at 9 and the binary you flashed is at 8. You can't simply downgrade Android versions on Samsung devices.
Are you sure you can't enter download mode? The key combination to enter download mode isn't what you said (" BixBy + Volume down + Power + plugging the cable doesn't work "). Try PLUGGING YOUR PHONE IN YOUR PC + VOLUME DOWN + BIXBY.
If you can access download mode, let me know so I can help you get your device unbricked.

Hello,
My mistake is that I downgraded from 11 to 10. You are probably right.
I think (but i'm not sure) that during downgrading, the sboot.bin is not anymore matching with the Device Tree and it generates a crash during flashing.
@WSC Productions : Huge thanks for the advice about the combo buttons.
@bininga59 : I'll give a try to your solution with the software FRP Hijacker Tool. But the phone is restarting itslef every 5 seconds..I wonder how a connection can be established.
Tonight will be a long night again

jean_michmich said:
Hello,
My mistake is that I downgraded from 11 to 10. You are probably right.
I think (but i'm not sure) that during downgrading, the sboot.bin is not anymore matching with the Device Tree and it generates a crash during flashing.
@WSC Productions : Huge thanks for the advice about the combo buttons.
@bininga59 : I'll give a try to your solution with the software FRP Hijacker Tool. But the phone is restarting itslef every 5 seconds..I wonder how a connection can be established.
Tonight will be a long night again
Click to expand...
Click to collapse
You can definitely go back from A11 to A10. It's the same bootloader (9). If it keeps restarting, then you should get into download mode too. Emergency off and then immediately quieter + Bixby immediately push the USB plug in.

jean_michmich said:
Hello,
My mistake is that I downgraded from 11 to 10. You are probably right.
I think (but i'm not sure) that during downgrading, the sboot.bin is not anymore matching with the Device Tree and it generates a crash during flashing.
@WSC Productions : Huge thanks for the advice about the combo buttons.
@bininga59 : I'll give a try to your solution with the software FRP Hijacker Tool. But the phone is restarting itslef every 5 seconds..I wonder how a connection can be established.
Tonight will be a long night again
Click to expand...
Click to collapse
No problemo. Try @bininga59 's advice, it'll probably work - he probably knows more than I do about Samsung ROMs tbh. If it doesn't though, let me know.

What i didn't know :
Doing Volume down + BixBy Button + plugging cable for simple electric supply
Is not the same as
Doing Volume down + BixBy Button + plugging cable linked to a computer
The cable you plug to the telephone while you are pressing volume down + BixBy must be linked to a computer.
I finally reached the Download Mode
Many thanks again