Related
So in a preview attepmt to fix my phone , i discovered that dont mater what rom i flash, ether its via fastboot, or regular recovery or TWRP, phone always comes to the same state, even if i use the erase comands on fastboot, or try to format partitions on twrp, once i reboot the phone, it comes back to the original state, even pictures or music, stay there intact after delete them....
Wich leads me here to ask for some help again
My phone its an xt1063 ,the latest build, runing Blur_Version.21.11.23.titan_retug wich stops me from flashing another rom via stock recovery as there are no builds for 21.11.23. Its there something i can check to see if my phone its write protected or freezed? Thanks for your time and help .
Code:
C:\mfastboot-v2>fastboot getvar all > command.txt
(bootloader) version: 0.5
(bootloader) version-bootloader: 4807(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D3239LM
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: D59CBB060F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: Why its emei so important?
(bootloader) meid:
(bootloader) date: 10-23-2014
(bootloader) sku: XT1063
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Dec 2 3:44:40 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retuglb/titan_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.85-23/21:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.23.titan_retug
(bootloader) ro.build.version.full[1]: lb.retuglb.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g668a77b ([email protected]
(bootloader) kernel.version[1]: ilclbld53) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Aug 26 20:21:50 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V48.07-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.07-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V48.07-0-g71b1aae-dirty
(bootloader) tz.git: git=MBM-NG-V48.07-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V48.07-0-ge875a20
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D3239LM
(bootloader) sutinfo:
all: listed above
finished. total time: 0.088s
so, am i doing it wrong? its there something i can do for someone to help me? are there anyone whos interested in such a weird problem? i know it dosnt happen often and at the same time, cant find nothing here or in google, thats why i dare to ask for help in here.
Thanks for your attention, but can anyone explain to me why im not getting any help? so i can fix it,thanks again.
Sorry man,I have no clue what is happening with your phone. Maybe it´s got something to do with writeprotection. Replying just to push your thread for some of the cracks around here can check this out?
All the best to you!
Wolfcity said:
Sorry man,I have no clue what is happening with your phone. Maybe it´s got something to do with writeprotection. Replying just to push your thread for some of the cracks around here can check this out?
All the best to you!
Click to expand...
Click to collapse
Glad is a problem thats not easy to fix than thinking im just being ignored im still trying things to see if i can fix it.
edit: i might be out of luck, i have the exact same problem as this guy http://forum.xda-developers.com/showthread.php?t=1967620 he did not found a solution, probably a hardware problem, but ill keep looking.
Same here
what have you tried?
I tried wiping everything through recovery, fixing permissions, formating partitions, wiping through bootloader, flashing stock kk with no result. When I first saw the problem I was like nah not big deal but no one has managed to solve it
Did you try?
adb shell
getprop ro.boot.write_protect
What is returned from this command 0 or 1?
Tonal4Nagual said:
Did you try?
adb shell
getprop ro.boot.write_protect
What is returned from this command 0 or 1?
Click to expand...
Click to collapse
i get
0
Then your system partition is not write protected.
Sent from my XT1068 using XDA Free mobile app
so for me, the only thing i was not being able to try, is to flash an original rom , even better, but i think it dosnt exists, flash the rom that the phone is asking for
Code:
phone has (motorola/titan_retuglb/titan_umts:4.4.4/KXB23)
i really have no idea wich original phone rom comes after that one. I tried to modify an original 5.0.2 rom
Code:
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US
modify the updater-script script to acept the current rom i have or even erase the part that checks it, but neither work, i get installation aborted. So if someone knows how to modify original roms ,pack them back again , and be able to flash via original recovery, that would be awsome so i can try one more thing.
You propably can't flash anything not original through stock recovery.
Sent from my XT1068 using XDA Free mobile app
i tried to unpack , found the string that checks for the version installed on the phone, modifed that in 3 files , metadata.gpb,metadata , and updater-script, repacked, and when i try to install, i get installation aborted.....
ried to format partitions as per instructed here http://android-revolution-hd.blogspot.mx/2013/10/fix-data-htc-one.html no luck...
so today i tried to install RETLA_XT1063_4.4.4_KXB21.85-24_cid12_CFC_SVC.xml via fastboot, and no go, i couldnt fin an origial rom for the same so i could try to install via original recovery, i also tried the philz recovery and tried to format partitions with it, and instal varius roms, with no luck. im running out of ideas at this point, but tomorrow maight get more, its just frustating that its been 5 days trying to resurect this phone.... any help or feedback from other members with the same problem would be apreciated,
looks like im along on this boat.....i tried a couple of more roms, no good outcome ...will keep looking...
abispac said:
looks like im along on this boat.....i tried a couple of more roms, no good outcome ...will keep looking...
Click to expand...
Click to collapse
do you have a twrp of original rom (even if it doesnt flash) i can figure out original rom from it and then find full firmware and TRY to make a easy installer for you - but i'm thinking this may fail too as im thinking corrupted partiton thats gonna need linux to fix
reefuge said:
do you have a twrp of original rom (even if it doesnt flash) i can figure out original rom from it and then find full firmware and TRY to make a easy installer for you - but i'm thinking this may fail too as im thinking corrupted partiton thats gonna need linux to fix
Click to expand...
Click to collapse
Do you have any suggestion for the storage? When I thry to format using fastboot I get tha raw format is not supported
xGiorgos said:
Do you have any suggestion for the storage? When I thry to format using fastboot I get tha raw format is not supported
Click to expand...
Click to collapse
what are you trying to format /system /cache /userdata ?
reefuge said:
what are you trying to format /system /cache /userdata ?
Click to expand...
Click to collapse
all of them
UPDATE (26.01.2016):
Normal Boot:
It is not booting more than stock logo
Recovery:
boots into TWRP but cannot mount partitions or format them
Fastboot
Connects to flashboot, says it flashed system ok, but not flashed system ok (nothing changes)
Connects to flashboot, says it flashed recovery ok, but not flashed recovery ok (still TWRP)
fastboot erase system, recovery, other partitions, gives an error
SP Flash Tools
DL/Checksum Checkbox Checked, Download goes all the way to 100%, CHECKSUM ERROR, Still not working.
Below recovery.log - log from breaking-up-the-device process up to now
new1.txt - partitions when the device was working correctly
ORIGINAL POST:
Hello.
I started with changing stock TWRP with CWM then proceeded to change stock Vibe UI with Cyanogenmod (from needrom). First Update 2 version then Update 3. The phone was unstable, loosing settings logging out of applications etc.
Decided to change to MIUI (this one)
But first decided to change back to TWRP (this one)
After Partition Format i tried to install MIUI but it failed.
Then i tried this guide: https://www.youtube.com/watch?v=TySRc_DkcFk
All files i downloaded from the links in the guide.
SP flash tool flashed to 100% and then gave me the message BROM ERROR : S_CHKSUM_ERROR (1041)
(I did select "All versions" File)
TWRP Log started giving me E: unable to mount /data (/system /storage and everyting else at once)
Cannot mount partitions manually either
tried fastboot flash recovery to CWM, it says OK but there is still TWRP.
tried flashing recovery through TWRP install - says cannot mount /data
Phone is not in bootloop but stuck on Lenovo logo.
Is this internal storage failure? Can i check or restore stock partitions somehow? Is this maybe TWRP not seeing partitions?
And why i cannot flash partitions through fastboot?
I would appreciate any, even slight help. Thanks.
hi
i am sharing my experience.
i too changed recoveries frequently & not able to mount sd card in recovery,currently i install files needed to be flashed to the internel memory & flash them from there.
i would suggest reinstalling the stock rom first,then install recovery of your choice, copy rom file to the internel memory & then flash it.
arun jog
arun jog said:
currently i install files needed to be flashed to the internel memory & flash them from there.
Click to expand...
Click to collapse
Can i ask you how you do this?
I tried putting img or rom on sd card and flash it from recovery but it said "E: cannot mount /data"
Gogolian said:
Can i ask you how you do this?
I tried putting img or rom on sd card and flash it from recovery but it said "E: cannot mount /data"
Click to expand...
Click to collapse
you need to download stock rom which is flashable thru sp tools from the hackerpowers index thread,use sp flash tools to flash stock rom. since sd card is not mounting it is better you go for this option. i think once your phone boots up sd card might not be detected by the phone, anyway all the best.
arun jog said:
you need to download stock rom which is flashable thru sp tools from the hackerpowers index thread,use sp flash tools to flash stock rom. since sd card is not mounting it is better you go for this option. i think once your phone boots up sd card might not be detected by the phone, anyway all the best.
Click to expand...
Click to collapse
Thanks. I did try with RootJunky's one: http://rootjunkysdl.com/?device=Lenovo K3 Note&folder=Firmware
But unfortuneatly got error:
BROM ERROR : S_CHKSUM_ERROR (1041)
and it's not working
(btw, It's not checksum as it first flashes to 100% then displays the error)
Yet I haven't tried with those. I will.
Gogolian said:
Thanks. I did try with RootJunky's one: http://rootjunkysdl.com/?device=Lenovo K3 Note&folder=Firmware
But unfortuneatly got error:
BROM ERROR : S_CHKSUM_ERROR (1041)
and it's not working
(btw, It's not checksum as it first flashes to 100% then displays the error)
Yet I haven't tried with those. I will.
Click to expand...
Click to collapse
pl ensure DA/DL all with checksum is selected in sp flashtools
arun jog said:
pl ensure DA/DL all with checksum is selected in sp flashtools
Click to expand...
Click to collapse
I was using v5 of SP flash tool I will switch to v3 then.
Did you manage to get your phone out of boot loop
arun jog said:
Did you manage to get your phone out of boot loop
Click to expand...
Click to collapse
Unfortuneatly not. Here's update:
1. v3 version of SPflash dont want to flash had to stick with v5
2. after flashing official rom (K50_a40_S112_150610_row) phone is stuck on Lenovo screen (no bootloop though)
It stayed like that for an hour before i started to do anything else.
fastboot erase <partition> does not work. Gives an error.
i've managed to do a log dump from TWRP - in attachment
Iv'e also noticed that i have a TWRP full backup before i started doing anything, the problem is, I cannot get it on Storage as dthe /data and /system partitions are corrupted.
Is there any way i can restore TWRP backup f.e. through fastboot or SPF tools ?
Is there any way to just Repartition the whole EMMC_USER?
could i dump whole EMMC_USER from other K3 note and somehow flash it onto this one?
EDIT: Also Found Partition logs from the beggining log file (new1.txt)
Gogolian said:
Unfortuneatly not. Here's update:
1. v3 version of SPflash dont want to flash had to stick with v5
2. after flashing official rom (K50_a40_S112_150610_row) phone is stuck on Lenovo screen (no bootloop though)
It stayed like that for an hour before i started to do anything else.
fastboot erase <partition> does not work. Gives an error.
i've managed to do a log dump from TWRP - in attachment
Iv'e also noticed that i have a TWRP full backup before i started doing anything, the problem is, I cannot get it on Storage as dthe /data and /system partitions are corrupted.
Is there any way i can restore TWRP backup f.e. through fastboot or SPF tools ?
Is there any way to just Repartition the whole EMMC_USER?
could i dump whole EMMC_USER from other K3 note and somehow flash it onto this one?
EDIT: Also Found Partition logs from the beggining log file (new1.txt)[/QU
are you able to use your phone. if yes. than keep searching this as well as other forums till you get the solution you are looking for; if its not booting up further than lenovo logo than flash stock rom
Click to expand...
Click to collapse
arun jog said:
Gogolian said:
are you able to use your phone. if yes. than keep searching this as well as other forums till you get the solution you are looking for; if its not booting up further than lenovo logo than flash stock rom
Click to expand...
Click to collapse
Again:
Normal Boot:
It is not booting more than stock logo
Recovery:
boots into TWRP but cannot mount partitions or format them
Fastboot
Connects to flashboot, says it flashed system ok, but not flashed system ok (nothing changes)
Connects to flashboot, says it flashed recovery ok, but not flashed recovery ok (still TWRP)
SP Flash Tools
DL/Checksum Checkbox Checked, Download goes all the way to 100%, CHECKSUM ERROR, Still not working.
Click to expand...
Click to collapse
Gogolian said:
arun jog said:
Again:
Normal Boot:
It is not booting more than stock logo
Recovery:
boots into TWRP but cannot mount partitions or format them
Fastboot
Connects to flashboot, says it flashed system ok, but not flashed system ok (nothing changes)
Connects to flashboot, says it flashed recovery ok, but not flashed recovery ok (still TWRP)
SP Flash Tools
DL/Checksum Checkbox Checked, Download goes all the way to 100%, CHECKSUM ERROR, Still not working.
Click to expand...
Click to collapse
stock rom downloaded from op of index thread? are you following the correct procedure to install stock rom ?
Click to expand...
Click to collapse
arun jog said:
stock rom downloaded from op of index thread? are you following the correct procedure to install stock rom ?
Click to expand...
Click to collapse
My procedure:
Download rom from index tread:
http://forum.xda-developers.com/k3-note/general/organized-thread-lenovo-k3-note-k50-t3158522
Rom: All Official ST/DEV/ROW Roms + OTA -> K50_a40_S112_150610_row
as it says this is the one to flash through SP Flash Tools.
Now i Have SP Flash Tools v5
Download Agent: MTK_AllInOne_DA
Scatter loading file: The file from the archive
Download Only (Actually i tried both - no luck)
I hit Download, then connect the Phone.
The download Starts, Flashes to 100%, then gives BROM ERROR : S_CHKSUM_ERROR (1041)
After restarting the device it goes forever on the loading logo.
In the flash tool have you checked DA/DL under options. I have flashed many times without any problems.
arun jog said:
In the flash tool have you checked DA/DL under options. I have flashed many times without any problems.
Click to expand...
Click to collapse
Yes, I do have it checked. I checked (pun not intended) several times.
Anyway i tried to remove partitions through fastboot or parted but no luck.
Here are fastbot errors:
Code:
C:\adb>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1a800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:frp: 860000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 60000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: AIO_OTFP
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.010s
C:\adb>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.000s
Gogolian said:
Yes, I do have it checked. I checked (pun not intended) several times.
Anyway i tried to remove partitions through fastboot or parted but no luck.
Here are fastbot errors:
Code:
C:\adb>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1a800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:frp: 860000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 60000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: AIO_OTFP
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.010s
C:\adb>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.000s
Click to expand...
Click to collapse
hi,
have you tried from a different system, on windows 8 my phone gives me lot of troubles whereas in windows 7 it is fairly easy.
try it out in case you have not tried it. all the best.
arun jog said:
hi,
have you tried from a different system, on windows 8 my phone gives me lot of troubles whereas in windows 7 it is fairly easy.
try it out in case you have not tried it. all the best.
Click to expand...
Click to collapse
I did, also different drivers - no change
UPDATE:
I managed to get ahold of second K3 Note.
I did FULL memory reas using SP flash tools and FULL memory write on old device.
The problem is - write restarts at aprox 27%
Yet, recovery still stayed TWRP.
I belive i did not unchecked "update cm recovery" under CM12 and noe it keeps flashing back.
Anyway, I still think it's a hardware problem right now.
Thanks for the help guys
Hi Gogolian
did ou solved the problem with the K3 note?
I have exactly the same problem, all exactly the same, and everything I try fails.
It would be very hlepfull if you can comment how did you managed finally
Thanks in advance!
Gogolian said:
I did, also different drivers - no change
UPDATE:
I managed to get ahold of second K3 Note.
I did FULL memory reas using SP flash tools and FULL memory write on old device.
The problem is - write restarts at aprox 27%
Yet, recovery still stayed TWRP.
I belive i did not unchecked "update cm recovery" under CM12 and noe it keeps flashing back.
Anyway, I still think it's a hardware problem right now.
Thanks for the help guys
Click to expand...
Click to collapse
@Gogolian
Did you managed to solve the problem with the k3 note?
I have exactly the same problem.
Thanks
Same problem here, believe the memory (emmc ?) is damaged somehow and needs to be reformatted.
Device is stuck in fastboot mode
screen shows
Device is LOCKED: Status code: 0
IMEI : 00000000000
SKU: 00000
Serial number shows values
Date being shown as 01-01-1970
Bootloader logs shows
fastboot reason: failed to initialize partition table
any advise on how to recover from this?
Fastboot erase userdata plus cache
Sent from my Nexus 6 using XDA-Developers mobile app
get error on erase
MacBook-Pro:~ user$ fastboot devices -l
994f3b10 fastboot usb:337641472X
MacBook-Pro:~ user$ fastboot erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.067s
MacBook-Pro:~ user$ fastboot erase userdata
erasing 'userdata'...
(bootloader) Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.066s
MacBook-Pro:~ user$
fastboot flash bootloader. Are you trying to flash N Preview?
reagan1998 said:
fastboot flash bootloader. Are you trying to flash N Preview?
Click to expand...
Click to collapse
my device was running fine with 5.1 and not sure what caused to get into this stuck where its stuck in fastboot boot
i am just trying to flash factory images from https://developers.google.com/android/nexus/images#shamu
Given the suddenness of your problem as well as the symptoms, I believe the internal memory has failed, meaning a service call. However, I hope I'm wrong.
Regardless, flashing factory images won't work because your bootloader is locked. Assuming this is a software issue you may be able to restore the system by sideloading the Android N OTA through recovery. If you can successfully do that, head to Developer Options in the N preview and enable OEM unlock. From there, unlock the bootloader, so you can flash factory images.
Strephon Alkhalikoi said:
Given the suddenness of your problem as well as the symptoms, I believe the internal memory has failed, meaning a service call. However, I hope I'm wrong.
Regardless, flashing factory images won't work because your bootloader is locked. Assuming this is a software issue you may be able to restore the system by sideloading the Android N OTA through recovery. If you can successfully do that, head to Developer Options in the N preview and enable OEM unlock. From there, unlock the bootloader, so you can flash factory images.
Click to expand...
Click to collapse
- I read some threads on sideload, they need device booted with adb access, since mine is stuck in fastboot, i don't have access to device via adb, would side load still work?
- still looking for zip for side load for nexus 6, if you have pointer for it, please let me know
To sideload the Android N OTA, which is the only thing that will help you here, you need to be able to get into recovery and set the recovery to adb sideload mode. If you cannot get into recovery, you definitely have a hardware problem and will need to get the internal storage chip replaced. As for the Android N OTA zip, check in the General subforum. Of course you could also simply do a quick Google search for "Android N OTA Brick" and get to Google's page of OTA zips that way.
Strephon Alkhalikoi said:
To sideload the Android N OTA, which is the only thing that will help you here, you need to be able to get into recovery and set the recovery to adb sideload mode. If you cannot get into recovery, you definitely have a hardware problem and will need to get the internal storage chip replaced. As for the Android N OTA zip, check in the General subforum. Of course you could also simply do a quick Google search for "Android N OTA Brick" and get to Google's page of OTA zips that way.
Click to expand...
Click to collapse
Android N has a new bootloader, so sideloading it will probably make the device not boot into Android.
---------- Post added at 08:24 PM ---------- Previous post was at 08:23 PM ----------
Have you tried flashing a TWRP recovery and maybe flashing a custom ROM to see if it is a storage issue? This phone is not even two years old, it should not be having internal storage issues.
The Android N OTA I'm talking about includes the bootloader, as it is a full system image. Flashing TWRP will not work as the device has a locked bootloader. But since the device apparently has no partitions at all, the exercise I believe is moot. This is a hardware issue.
Run 'fastboot format cache' and 'fastboot format userdata', then run the most holy words in android 'fastboot oem unlock'. Check this: http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783 it really helped me out of a deep hole.
The only way that will work is if the OP enabled OEM Unlocking in Developer Options prior to the device forgetting its partitions. I hope he did, as having the option enabled doesn't affect the ability to get OTAs from Google. If however his device's EMMC chip failed as I believe, it won't help him resolve this issue.
reagan1998 said:
Run 'fastboot format cache' and 'fastboot format userdata', then run the most holy words in android 'fastboot oem unlock'. Check this: http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783 it really helped me out of a deep hole.
Click to expand...
Click to collapse
apologies for delayed response, i didn't realize there was second page in replies and you guys are still trying to help
here is outout
sh-3.2# fastboot devices
994f3b10 fastboot
sh-3.2# fastboot format cache
Formatting is not supported for filesystem with type ''.
sh-3.2# fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
sh-3.2# fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-71.08(*)
(bootloader) product: shamu
(bootloader) board: shamu
(bootloader) secure: yes
(bootloader) hwrev: 0x83A0
(bootloader) radio: 0x6
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 3072MB Elpida S8 SDRAM DIE=6Gb
(bootloader) cpu: APQ8084 ES1.1
(bootloader) serialno: 994f3b10
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: 7858B30111000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sdi.git: sdi.git
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) aboot.git: git=MBM-NG-V71.08-0-g32b8854
(bootloader) qe:
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.040s
sh-3.2#
If it's failing to initialize the partition table, there's nothing you can do here. It needs to go to Motorola for warranty service.
EDIT: How I can tell? The date was set to 1/1/70. That's the beginning date of the Unix clock, which means something got screwed up internally. That plus the lost IMEI and the failure of the device to find its partitions means a bad device.
Sorry to be the bearer of bad news here, but this isn't something software can fix.
Strephon Alkhalikoi said:
If it's failing to initialize the partition table, there's nothing you can do here. It needs to go to Motorola for warranty service.
EDIT: How I can tell? The date was set to 1/1/70. That's the beginning date of the Unix clock, which means something got screwed up internally. That plus the lost IMEI and the failure of the device to find its partitions means a bad device.
Sorry to be the bearer of bad news here, but this isn't something software can fix.
Click to expand...
Click to collapse
Thanks for looking in, warranty must be void since i had open the back cover .
EDIT: Bad advice given.
Strephon Alkhalikoi said:
I would try anyway. The worst that will happen is they will want to charge you.
Click to expand...
Click to collapse
Which is considered fraud and not condoned by xda.
@zelendel: Echh. I'm not looking to get myself or XDA in trouble. I'll edit my post appropriately. Thank you for the reminder.
Strephon Alkhalikoi said:
@zelendel: Echh. I'm not looking to get myself or XDA in trouble. I'll edit my post appropriately. Thank you for the reminder.
Click to expand...
Click to collapse
Not a worry. I know a lot of people advise it but we don't condone it. This is why the disclosure in the OP of every rom thread. We accept what we do might mean killing our device and having to buy a new one. It's a risk of the hobby.
Hello,
I have an Amazon BLU R1 HD which I flashed with a standard OEM ROM based on the instructions in this forum, its been working great for months until I stupidly accepted an OTA (this one)
{
"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"
}
Since the update the device is stuck in a boot loop. I no longer have adb access to it (adb devices shows nothing) and I've tried to unlock the bootloader using SP Flash Tool and method 2 from here https://forum.xda-developers.com/r1-hd/development/r1-hd-amazon-bootloader-unlock-method-t3426104 but I just get a s_brom_download_da_fail error. I've tried on Windows and Linux, same results.
Can anything be done? Does anyone have any thoughts on this?
Thanks!
g00s3m4n said:
Hello,
I have an Amazon BLU R1 HD which I flashed with a standard OEM ROM based on the instructions in this forum, its been working great for months until I stupidly accepted an OTA (this one)
Since the update the device is stuck in a boot loop. I no longer have adb access to it (adb devices shows nothing) and I've tried to unlock the bootloader using SP Flash Tool and method 2 from here https://forum.xda-developers.com/r1-hd/development/r1-hd-amazon-bootloader-unlock-method-t3426104 but I just get a s_brom_download_da_fail error. I've tried on Windows and Linux, same results.
Can anything be done? Does anyone have any thoughts on this?
Thanks!
Click to expand...
Click to collapse
Since you had converted to OEM version. You most likely already had unlocked bootloader. Also when you take an ota with unlocked bootloader you end up with half re-locked bootloader and a boot loop.
We have already seen this in the forum , and have an easy solution.
But to verify the situation before making changes do this:
Hold volume up while phone is boot looping. it should eventually go to the boot menu. Select fastboot. Connect to your pc.
Open cmd window. type this "fastboot devices" you should get almost instant response. " *your serial number* fastboot"
now that you verified you have the connection type this "fastboot getvar all" the response is a list of partitions then near the end there is the bootloader status
"unlocked = yes"
and
"secure = yes"
if this is true then my assumption is correct. It should be "secure = no" for an unlocked phone.
Now type "fastboot oem unlock" followed by volume up button on phone.
follow that with "fastboot format userdata"
obviously this will factory reset your phone.
mrmazak said:
Since you had converted to OEM version. You most likely already had unlocked bootloader. Also when you take an ota with unlocked bootloader you end up with half re-locked bootloader and a boot loop.
We have already seen this in the forum , and have an easy solution.
But to verify the situation before making changes do this:
Hold volume up while phone is boot looping. it should eventually go to the boot menu. Select fastboot. Connect to your pc.
Open cmd window. type this "fastboot devices" you should get almost instant response. " *your serial number* fastboot"
now that you verified you have the connection type this "fastboot getvar all" the response is a list of partitions then near the end there is the bootloader status
"unlocked = yes"
and
"secure = yes"
if this is true then my assumption is correct. It should be "secure = no" for an unlocked phone.
Now type "fastboot oem unlock" followed by volume up button on phone.
follow that with "fastboot format userdata"
obviously this will factory reset your phone.
Click to expand...
Click to collapse
Thank you, your assumption was correct and that has fixed the problem. Obviously my search foo failed me.
I appreciate the quick reply and assistance.
mrmazak said:
Since you had converted to OEM version. You most likely already had unlocked bootloader. Also when you take an ota with unlocked bootloader you end up with half re-locked bootloader and a boot loop.
We have already seen this in the forum , and have an easy solution.
But to verify the situation before making changes do this:
Hold volume up while phone is boot looping. it should eventually go to the boot menu. Select fastboot. Connect to your pc.
Open cmd window. type this "fastboot devices" you should get almost instant response. " *your serial number* fastboot"
now that you verified you have the connection type this "fastboot getvar all" the response is a list of partitions then near the end there is the bootloader status
"unlocked = yes"
and
"secure = yes"
if this is true then my assumption is correct. It should be "secure = no" for an unlocked phone.
Now type "fastboot oem unlock" followed by volume up button on phone.
follow that with "fastboot format userdata"
obviously this will factory reset your phone.
Click to expand...
Click to collapse
confirmed working. one more phone has been saved. Thanks!
OEM version - boot loop
My BLU R1 HD from Amazon, is stuck at reboot. I have not made any changes to the ROM except OTA updates.
I have provided the fastboot getvar all - details below.
Kindly guide me how to unbrick the phone. I am not looking to root the phone. Thanks in advance.
The values are different from what you had mentioned above
(bootloader) unlocked: no
(bootloader) secure: yes
C:\>fastboot devices
4SPFSKDUOVQWMBFE fastboot
C:\>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a7000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2500000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
I ran the unlock bootloader and it fails as well
C:\>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 90.128s
praxtwin said:
My BLU R1 HD from Amazon, is stuck at reboot. I have not made any changes to the ROM except OTA updates.
I have provided the fastboot getvar all - details below.
Kindly guide me how to unbrick the phone. I am not looking to root the phone. Thanks in advance.
The values are different from what you had mentioned above
(bootloader) unlocked: no
(bootloader) secure: yes
C:\>fastboot devices
4SPFSKDUOVQWMBFE fastboot
C:\>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a7000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2500000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
I ran the unlock bootloader and it fails as well
C:\>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 90.128s
Click to expand...
Click to collapse
Don't have any proven information to give you in your situation. All previous boot loops after taking an OTA have been a result of already having bootloader unlocked.
I would normally suggest trying to do a factory reset in a boot loop situation . So if you can get into recovery mode try to do a reset. If you cannot get into recovery you can try to do a "fastboot format userdata" and / or. "fastboot format cache"
mrmazak said:
Don't have any proven information to give you in your situation. All previous boot loops after taking an OTA have been a result of already having bootloader unlocked.
I would normally suggest trying to do a factory reset in a boot loop situation . So if you can get into recovery mode try to do a reset. If you cannot get into recovery you can try to do a "fastboot format userdata" and / or. "fastboot format cache"
Click to expand...
Click to collapse
Thanks for your suggestion. Unfortunately, Recovery mode doesn't seem to work. I did Factory reset , and then reboot, it stays on white BLU screen.
Additional Info: I did a ROOT INTEGRITY CHECK. It fails stating several files modified. I am not sure if that is an indication of any problems.
So I fastboot'ed again and tried format userdata and cache.
Both result in Failure - Not Allowed.
C:\>fastboot format cache
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
target reported max download size of 134217728 bytes
erasing 'cache'...
FAILED (remote: format for partition 'cache' is not allowed
)
finished. total time: 0.005s
Is this because I do not have ROOT access, that I am not able to format?
Do you think there is anything I could do to get the phone working again. Appreciate your help so much.
praxtwin said:
Thanks for your suggestion. Unfortunately, Recovery mode doesn't seem to work. I did Factory reset , and then reboot, it stays on white BLU screen.
Additional Info: I did a ROOT INTEGRITY CHECK. It fails stating several files modified. I am not sure if that is an indication of any problems.
So I fastboot'ed again and tried format userdata and cache.
Both result in Failure - Not Allowed.
C:\>fastboot format cache
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
target reported max download size of 134217728 bytes
erasing 'cache'...
FAILED (remote: format for partition 'cache' is not allowed
)
finished. total time: 0.005s
Is this because I do not have ROOT access, that I am not able to format?
Do you think there is anything I could do to get the phone working again. Appreciate your help so much.
Click to expand...
Click to collapse
You are not allowed to format from fastboot because , not bootloader unlocked. So not unlocked, no custom recovery, and integrity check says system files are changed.
It is most likely end of line for that device. Only option I can think of is factory repair. Phone must be less than 1 year old. (released July 2016) They have 12 month warranty I believe.
I have the Amazon R1 HD and I too fell victim to the update install that relocked my phone so its stuck in the reboot format. My problem seems to be when attaching my phone to the computer as instructed previously to another Blu...after typing in "fastboot devices" I receive an error code stating the Android device has no drive. I am almost past exasperated. Help, please!
Please help
I tried the spitting flash tool method to get my phone out of bootloop it won't work because I can't turn it off. It's battery has to die out then when I plug it. It automatically goes to the BLU screen and stays there for a bit then powers off and turns on again. I tried plugging it in to my pc and using fastboot devices but I get this error.
'Fastboot' is not recognized as an internal or external command operable program or batch file
And I can't power it off to begin the flash every time I get a timeout and I have all the mtk drivers install and the MT65xx USB vcom drivers I'm so confused I have a week working on this issue
Ghost0711 said:
I tried the spitting flash tool method to get my phone out of bootloop it won't work because I can't turn it off. It's battery has to die out then when I plug it. It automatically goes to the BLU screen and stays there for a bit then powers off and turns on again. I tried plugging it in to my pc and using fastboot devices but I get this error.
'Fastboot' is not recognized as an internal or external command operable program or batch file
And I can't power it off to begin the flash every time I get a timeout and I have all the mtk drivers install and the MT65xx USB vcom drivers I'm so confused I have a week working on this issue
Click to expand...
Click to collapse
You are throwing a lot of different things together, but sounds like none of the steps are right.
If you have been stuck in a boot loop after an OTA update (like title of thread you are in) , and your phone was bootloader unlocked before taking the OTA update, then the following information should help.
If you are in a boot loop for other reason then this will not help.
While the phone in Turing on / off, hold volume up. Eventually it should come to the boot select screen. Use volume button to scroll to fastboot and power button to select.
Now plug usb into pc and open CMD window. Verify you have the fastboot program on pc, and it sees phone by typing "fastboot devices"
Your statement said you got response that fastboot was not recognized command. I suspect you may not have fastboot on pc, but it no fastboot on pc how did you unlock bootloader?
Moving on., Once you have fastboot recognizing the phone , type "fastboot oem unlock"
Should be message on phone screen asking to confirm by pushing volume up.
Next , if phone has stock recovery you can just reboot and stock recovery will wipe /data and phone should reboot.
If phone has custom recovery (twrp) need to format userdata and cache. Type "fastboot format userdata" then "fastboot format cache"
And again I must state that if phone is boot looping for other reasons then this may not help.
Hi All not to sure what is going on but i'll try to explain as much as best as i can hopefully someone help i can get my phone to show up with usb debugging enabled windows device manager just shows it as R1 HD with a yellow " ! " forcing it to install as ADB interface does do much it installs but does not show in adb with "adb devices" phone has debugging turned on and ive installed android aio driver pack from androidmtk.com didn't help though im at a loss my computer recognizes the phone in mtp or ptp if i turn off usb debugging but like i said just shows up as R1 HD with an exclamation mark either way in device manager so im guessing its driver related but i can't find the right driver so i really would be grateful to get some help.
phone version : BLU_R0011UU_V17_GENERIC 15-11-2016 14:41
Build Number: MRA58K
Are you running Windows 7 or 10, 32 bits or 64 bits ? running MTK's usb drivers ? using the OEM Blu usb cable ? tried a different usb port ? Is your Settings > Security > Unknown Sources enabled or disabled - toggle it and reconnect, any difference ?
Check for possible usb drivers conflict, uninstall those & reboot and then try a fresh install, on a different port, with a different PS and/or OS, or a Linux machine (gotta loved my old Dell Laptop D410 with new life, as good as a Chromebook.) Look under Device Manager & check for hidden/unknown devices.
Letitride said:
Are you running Windows 7 or 10, 32 bits or 64 bits ? running MTK's usb drivers ? using the OEM Blu usb cable ? tried a different usb port ? Is your Settings > Security > Unknown Sources enabled or disabled - toggle it and reconnect, any difference ?
Check for possible usb drivers conflict, uninstall those & reboot and then try a fresh install, on a different port, with a different PS and/or OS, or a Linux machine (gotta loved my old Dell Laptop D410 with new life, as good as a Chromebook.) Look under Device Manager & check for hidden/unknown devices.
Click to expand...
Click to collapse
windows 7 32bit. mtk drivers and unknown sources are already enabled also for some reason oem unlock is not in the developer options it should be i thought on my current firm version..
darkensx said:
windows 7 32bit. mtk drivers and unknown sources are already enabled also for some reason oem unlock is not in the developer options it should be i thought on my current firm version..
Click to expand...
Click to collapse
Hmmm, is your bootloader locked or somehow got relocked after an OTA update/flash ?? How long have you owned this - rooted or not, rolled back the firmware ??
Do a manual reboot into bootloader (without using ADB) and post what those values are - especially about firmware, bootloader & unlock status ? pre-loader version ?
Backup any settings & important files on your R1 HD first, pull out any storage mSD card, do a factory reset - and - if you are sure that it is not bootloader LOCKED - download & run one of the dirty-cow-batch file (don't use the newest one as it didn't work on my other R1 HD now on the modified non-Prime version, was getting an error message when I tried to unlock & root it - one of the older one with the Linux option is what I used)
I then installed TWRP, flashed the modified factory rom, ran the debloat batch file also and flashed the latest SuperUser for good measure along with Busybox.
Letitride said:
Hmmm, is your bootloader locked or somehow got relocked after an OTA update/flash ?? How long have you owned this - rooted or not, rolled back the firmware ??
Do a manual reboot into bootloader (without using ADB) and post what those values are - especially about firmware, bootloader & unlock status ? pre-loader version ?
Backup any settings & important files on your R1 HD first, pull out any storage mSD card, do a factory reset - and - if you are sure that it is not bootloader LOCKED - download & run one of the dirty-cow-batch file (don't use the newest one as it didn't work on my other R1 HD now on the modified non-Prime version, was getting an error message when I tried to unlock & root it - one of the older one with the Linux option is what I used)
I then installed TWRP, flashed the modified factory rom, ran the debloat batch file also and flashed the latest SuperUser for good measure along with Busybox.
Click to expand...
Click to collapse
this phone i got second hand guy only had it 4 days i got it yesterday it was factory reset and afaik the phone was not ever modded, unlocked, rooted etc. is reconized in adb on my win 10 64 bit pc
as far as bootloader status these are the values produced from " fastboot getvar all " :
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a7000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2500000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.202s
darkensx said:
this phone i got second hand guy only had it 4 days i got it yesterday it was factory reset and afaik the phone was not ever modded, unlocked, rooted etc. is reconized in adb on my win 10 64 bit pc
as far as bootloader status these are the values produced from " fastboot getvar all " :
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.202s
Click to expand...
Click to collapse
OK, from the last few lines - it indicated your device has an unlockable preloader/bootloader (yet to be done) and once it is, you can root it and install TWRP, and flash the "modified" stock ROM, i.e V2.85
See this thread/post - read the first page & last few pages about some of the discussion, use V10 of the tool - it worked on mine, and if it doesn't - try V8 also.
Make sure you installed & have working ADB and the MTK usb drivers (uninstall & reinstall)
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333
See this about running the batch file.
https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882
Make a note of any error messages on screen. Have fun.