This practical solution I wanted to share here after i couldn't find a solution online is for Nexus 7 devices that can boot into Fastboot. If your device can't boot into fast boot anymore try this solution by K23m from here. And if your device have instead a faulty eMMC that might need replacement or else check here instead.
My Nexus 7 2013 16gb with Toshiba eMMC got stuck on a boot loop two days ago. I used twrp recovery to wipe it all, refresh lineage os or stock ota, yet i couldn't get past the boot loop. Ill spill the beans early here, It fixed and it needed me to zero out all the free space of the eMMC. as soon as i did that i got back to a 100% reliability and fast speeds like the first time i bought it.
But first was how to boot into a working android image to download and run the zeroing utility. The only working image i could run was the old Factory image "razor-jss15j-factory-2e08b83b.tgz" you can google it but ill provide this mirror link just in case it disappears.
I believe that my problem was that i had little space left and it got corrupted in some way maybe because of bad Trim process. in any case the following old factory image is small and have the highest (only?) chance to boot once and allow to reset the empty space values int he eMMC.
I started by following the process under fast boot:
fastboot devices
fastboot oem unlock
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-razor-jss15j.zip
Try booting 4 times if it doesn't work add this step before:
Download the great restore script and files from "[TOOL] 06/22/14 One Click Factory Restore 4.4.4 KTU84P (dead or alive)" here at XDA and download the "Nexus7_2013_KTU84P_Restore.zip WIFI Flo" if you're like me or the other corresponding image for your Nexus 7 version.
First copy the files of the razor-jss15j-factory from the compressed archive inside the same folder as the restore archive and
Run these fast boot commands from within:
fastboot devices
fastboot oem unlock
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash system system.img
fastboot flash recovery twrp-3.2.1-0-flo.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot -w
fastboot -w update image-razor-jss15j.zip
fastboot flash boot boot.img
fastboot reboot
Try booting 4 times with at least one switched off period of 20mn in between till you boot in. ( it is random and its not guaranteed it will work for you like i did for me)
I know some command are redundant and might make you think its stupid to do so but believe me when i say i spent 2 days non stop trying everything i can short of opening the device to heat gun the eMMC chip
These are the last steps i took to finally boot in and i repeated the process as i tried the first time to flash newer images in the hope they will boot too but to no avail.
Now that you booted in the old android version first go to the App Store and download a free zeroing app like" Secure Eraser " by Giuseppe Romano from the app store. after you run it twice, you can reinstall lineage os or your favourite stock version and be relieved.
I hope this amateurish post help you not discard too early your beloved Nexus 7 tablet. its only worth for me is manga reading and youtube sometimes, and for that its a wonder.
jackkill said:
My Nexus 7 2013 16gb with Toshiba eMMC got stuck on a boot loop... The only working image i could run was the old Factory image "razor-jss15j-factory-2e08b83b.tgz"
Click to expand...
Click to collapse
Thank you for sharing the recovery steps but there is an instant and simple fix. While we will never know for sure the cause of this bootloop because no logs were created prior to the repair, the fact that only the old factory image worked provides most likely diagnosis. The Nexus saves some data like DRM files, sensor parameters or camera calibration in the 'persist' partition where it survives wipes and flashes, but occasionally it may be deleted or corrupted, and then Andoid goes into bootloop. The old OS can recreate the needed files on the partition while new ones can not.
To fix it just install a fresh persist.
Incidentally...
the officially available oldest factory image JSS15Q is just as good as your JSS15J
the linked XDA "One Click Factory Restore" script is obsolete, use official Google's instructions instead
filling up empty storage space with Secure Eraser will only accelerate NAND wear out, and trim is implemented since Android 4.3
Yes Nexus 7'13 is still great. I have two of them and no intention to upgrade.
Cheers
k23m said:
Thank you for sharing the recovery steps but there is an instant and simple fix. While we will never know for sure the cause of this bootloop because no logs were created prior to the repair, the fact that only the old factory image worked provides most likely diagnosis. The Nexus saves some data like DRM files, sensor parameters or camera calibration in the 'persist' partition where it survives wipes and flashes, but occasionally it may be deleted or corrupted, and then Andoid goes into bootloop. The old OS can recreate the needed files on the partition while new ones can not.
To fix it just install a fresh persist.
Incidentally...
the officially available oldest factory image JSS15Q is just as good as your JSS15J
the linked XDA "One Click Factory Restore" script is obsolete, use official Google's instructions instead
filling up empty storage space with Secure Eraser will only accelerate NAND wear out, and trim is implemented since Android 4.3
Yes Nexus 7'13 is still great. I have two of them and no intention to upgrade.
Cheers
Click to expand...
Click to collapse
Thank you k23m,
Ill add the Fresh persist solution link for those who can’t boot into Fastboot
and the link to the Hardware Nand bricks fix too
As for my experience, I did try google’s recovery firmware and steps, however it proved ineffective. At some point even the recovery partition stopped working and forced me to only use Fastboot afterward. As i looked everywhere on how to fix the stuck boot and tried the proposed software solutions with no avail, i decided to share my practical experience of what worked for me, in hope it helps someone else facing the same problem.
my Nexus 7 device is already around 4 years old and it was a discounted demo unit form a retail store, It is a fact that the amount of read write have already reached a high level that must have wore the Nand quite a bit already. However, as the secure eraser method solved the problem, I don’t believe that doing so once in the 4 years span is much of a risk in comparison. My device was on post Stock Android 4.3 most of the time and was on Lineage OS Android 7 since last year, Trim clearly failed to perform. And many sources online believe that the way Google implemented Trim isn’t complete and think that the decreasing device performance on android devices must be linked to it.
I am convinced that the problem was software, related to Trim somehow, and as the Land chip i own is a Toshiba, it can be ruled out from the known faulty Nand brand some Nexus 7 have. Moreover, no error message was displayed when performing Fastboot operations. everything was executed with success all the time.
Cheers
jackkill said:
However, as the secure eraser method solved the problem...
Click to expand...
Click to collapse
Many things happened during the repair session and I'd not credit "secure eraser" for the speed improvement.
The "secure eraser" app does not require root (to run fstrim) nor trigger TRIM ever! It just fills up empty storage space. Read the reviews - slow, horrible , inefficient. Let me propose an alternative - boot TWRP and run/install my TRIM script - it will optimize the storage space in seconds, without excessive NAND wear out - see the attachments. Run it whenever you feel that Google's TRIM algo is deficient and it's time for manual override...
:highfive:
About to give up on old Nexus 7 2013 (last ditch)
So I too have a Nexus 7 2013 that I used pretty heavy for the past 4 and half years. The last months, I pretty only used it for podcasts via the PocketCast (best Podcast app and runs on both the major mobile OS's.)
Anyways, it had been getting caught in these bootloops off and on. The last time it successfully booted was on Sunday (4/29). That session lasted until this past Sunday until it decided to reboot on its on and hasn't been usable since.
I tried the ADB tools on a Windows 10 but the only way Windows would talk to the device was when I set it to Recovery mode with the "Install from ADB". I tried a bunch of those stock images from the google developers site But in each case it would either fail the checksums or error messages about header.h.
I should add that I never installed any custom ROMs ,TWRP, or what have you. In fact, I never really paid much attention to the Android Development scene at all until the past couple of days.
I suspect that this device really is dead or that the eMMc storage / or NAND is just completely worn out. I got my money's from it though.
If anyone has any advice on other things to try, I'd be all ears. I'm probably going to move on try my hand with one of the Odroids.
Burgin said:
So I too have a Nexus 7 2013 that I used pretty heavy for the past 4 and half years......
Anyways, it had been getting caught in these bootloops off and on........
I tried a bunch of those stock images from the google developers site But in each case it would either fail the checksums or error messages about header.h.........
I suspect that this device really is dead or that the eMMc storage / or NAND is just completely worn out.
Click to expand...
Click to collapse
I suspect that after 4.5 years the battery is finished. It may charge OK but its increased internal resistance will cause instability and reboots under heavy processing load. The following tests must be done with a very short, quality USB cable connected directly to PC's USB3 port. I insist on USB3 because it can deliver much higher current, sufficient to reliably run your N7 with defective battery.
Please post the output of the following commands:
turn off the Nexus
connect it to your PC
boot the Nexus in fastboot mode (when off press power+vol.dn)
on PC run:
fastboot getvar all
fastboot oem gpt-info
fastboot format cache
Next...
go to your folder with fastboot.exe and adb.exe
download twrp-3.2.1-0-flo.img to the folder
also unzip and copy the attached "twrp-log.bat" to the folder
in the folder open a DOS command window and copy/paste: fastboot boot twrp-3.2.1-0-flo.img [Enter]
when TWRP is up and running (may ask for ADB driver) and you see the menu, double-click on twrp-log.bat
Note, the above steps must be done withn 3 minutes to ensure complete dmesg log
then you will find a new file twrp.txt in the folder
zip up twrp.txt and attach it to your next post
Actually, as a new XDA user you may not be able to attach files or post links, so upload twrp.txt to http://pastebin.com and post only the subpage part, eg. from https://pastebin.com/9cat4t4X7 post only this 9cat4t4X7
Cheers :good:
First, thank you for the quick reply
Moving on. My problem is I can't get anything from the fastboot command. It just says "Waiting for device".
I assume that my USB drivers are totally wrong and I need to start all over in that regard.
When I read from this page, "developer.android.com/studio/run/oem-usb#InstallingDriver", I gather that there are actually two drivers to install, one for the Google USB driver and another specifically for the Nexus 7. Am I reading this correctly? What is this second driver?
(Oh and I did manage to find what I think to be a better quality USB cable.)
k23m said:
I suspect that after 4.5 years the battery is finished. It may charge OK but its increased internal resistance will cause instability and reboots under heavy processing load. The following tests must be done with a very short, quality USB cable connected directly to PC's USB3 port. I insist on USB3 because it can deliver much higher current, sufficient to reliably run your N7 with defective battery.
Cheers :good:
Click to expand...
Click to collapse
Ok, I got past my last issues (bad cable, bad driver setup)
Here are the first three command outputs you requested.
fastboot getvar all
Code:
(bootloader) version-bootloader: FLO-04.08
(bootloader) version-baseband: none
(bootloader) version-hardware: rev_e
(bootloader) version-cdma: N/A
(bootloader) variant: flo 32G
(bootloader) serialno: 07d98df8
(bootloader) product: flo
(bootloader) secure_boot: enabled
(bootloader) lock_state: locked
(bootloader) project: flo
(bootloader) off-mode-charge: yes
(bootloader) uart-on: no
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0x0000000000aee000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x0000000000a00000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000034800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000023000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x00000006b7ffbe00
all:
finished. total time: 0.043s
fastboot oem gpt-info
Code:
(bootloader) partition[1].name = radio
(bootloader) partition[1].first_lba = 131072
(bootloader) partition[1].last_lba = 306143
(bootloader) partition[1].size 87536 KB
(bootloader) partition[2].name = modemst1
(bootloader) partition[2].first_lba = 393216
(bootloader) partition[2].last_lba = 399359
(bootloader) partition[2].size 3072 KB
(bootloader) partition[3].name = modemst2
(bootloader) partition[3].first_lba = 399360
(bootloader) partition[3].last_lba = 405503
(bootloader) partition[3].size 3072 KB
(bootloader) partition[4].name = persist
(bootloader) partition[4].first_lba = 524288
(bootloader) partition[4].last_lba = 554287
(bootloader) partition[4].size 15000 KB
(bootloader) partition[5].name = m9kefs1
(bootloader) partition[5].first_lba = 655360
(bootloader) partition[5].last_lba = 656919
(bootloader) partition[5].size 780 KB
(bootloader) partition[6].name = m9kefs2
(bootloader) partition[6].first_lba = 656920
(bootloader) partition[6].last_lba = 658479
(bootloader) partition[6].size 780 KB
(bootloader) partition[7].name = m9kefs3
(bootloader) partition[7].first_lba = 786432
(bootloader) partition[7].last_lba = 787991
(bootloader) partition[7].size 780 KB
(bootloader) partition[8].name = fsg
(bootloader) partition[8].first_lba = 787992
(bootloader) partition[8].last_lba = 794135
(bootloader) partition[8].size 3072 KB
(bootloader) partition[9].name = sbl1
(bootloader) partition[9].first_lba = 917504
(bootloader) partition[9].last_lba = 920503
(bootloader) partition[9].size 1500 KB
(bootloader) partition[10].name = sbl2
(bootloader) partition[10].first_lba = 920504
(bootloader) partition[10].last_lba = 923503
(bootloader) partition[10].size 1500 KB
(bootloader) partition[11].name = sbl3
(bootloader) partition[11].first_lba = 923504
(bootloader) partition[11].last_lba = 927599
(bootloader) partition[11].size 2048 KB
(bootloader) partition[12].name = aboot
(bootloader) partition[12].first_lba = 927600
(bootloader) partition[12].last_lba = 937839
(bootloader) partition[12].size 5120 KB
(bootloader) partition[13].name = rpm
(bootloader) partition[13].first_lba = 937840
(bootloader) partition[13].last_lba = 938863
(bootloader) partition[13].size 512 KB
(bootloader) partition[14].name = boot
(bootloader) partition[14].first_lba = 1048576
(bootloader) partition[14].last_lba = 1081343
(bootloader) partition[14].size 16384 KB
(bootloader) partition[15].name = tz
(bootloader) partition[15].first_lba = 1179648
(bootloader) partition[15].last_lba = 1180671
(bootloader) partition[15].size 512 KB
(bootloader) partition[16].name = pad
(bootloader) partition[16].first_lba = 1180672
(bootloader) partition[16].last_lba = 1180673
(bootloader) partition[16].size 1 KB
(bootloader) partition[17].name = sbl2b
(bootloader) partition[17].first_lba = 1180674
(bootloader) partition[17].last_lba = 1183673
(bootloader) partition[17].size 1500 KB
(bootloader) partition[18].name = sbl3b
(bootloader) partition[18].first_lba = 1183674
(bootloader) partition[18].last_lba = 1187769
(bootloader) partition[18].size 2048 KB
(bootloader) partition[19].name = abootb
(bootloader) partition[19].first_lba = 1187770
(bootloader) partition[19].last_lba = 1198009
(bootloader) partition[19].size 5120 KB
(bootloader) partition[20].name = rpmb
(bootloader) partition[20].first_lba = 1198010
(bootloader) partition[20].last_lba = 1199033
(bootloader) partition[20].size 512 KB
(bootloader) partition[21].name = tzb
(bootloader) partition[21].first_lba = 1199034
(bootloader) partition[21].last_lba = 1200057
(bootloader) partition[21].size 512 KB
(bootloader) partition[22].name = system
(bootloader) partition[22].first_lba = 1310720
(bootloader) partition[22].last_lba = 3031039
(bootloader) partition[22].size 860160 KB
(bootloader) partition[23].name = cache
(bootloader) partition[23].first_lba = 3031040
(bootloader) partition[23].last_lba = 4177919
(bootloader) partition[23].size 573440 KB
(bootloader) partition[24].name = misc
(bootloader) partition[24].first_lba = 4194304
(bootloader) partition[24].last_lba = 4196351
(bootloader) partition[24].size 1024 KB
(bootloader) partition[25].name = recovery
(bootloader) partition[25].first_lba = 4325376
(bootloader) partition[25].last_lba = 4345855
(bootloader) partition[25].size 10240 KB
(bootloader) partition[26].name = DDR
(bootloader) partition[26].first_lba = 4456448
(bootloader) partition[26].last_lba = 4456463
(bootloader) partition[26].size 8 KB
(bootloader) partition[27].name = ssd
(bootloader) partition[27].first_lba = 4456464
(bootloader) partition[27].last_lba = 4456479
(bootloader) partition[27].size 8 KB
(bootloader) partition[28].name = m9kefsc
(bootloader) partition[28].first_lba = 4456480
(bootloader) partition[28].last_lba = 4456481
(bootloader) partition[28].size 1 KB
(bootloader) partition[29].name = metadata
(bootloader) partition[29].first_lba = 4587520
(bootloader) partition[29].last_lba = 4587583
(bootloader) partition[29].size 32 KB
(bootloader) partition[30].name = userdata
(bootloader) partition[30].first_lba = 4718592
(bootloader) partition[30].last_lba = 61079518
(bootloader) partition[30].size 28180463 KB
(bootloader) partition[31].name =
(bootloader) partition[31].first_lba = 0
(bootloader) partition[31].last_lba = 0
(bootloader) partition[31].size 0 KB
(bootloader) partition[32].name =
(bootloader) partition[32].first_lba = 0
(bootloader) partition[32].last_lba = 0
(bootloader) partition[32].size 0 KB
(bootloader) partition[33].name =
(bootloader) partition[33].first_lba = 0
(bootloader) partition[33].last_lba = 0
(bootloader) partition[33].size 0 KB
(bootloader) partition[34].name =
(bootloader) partition[34].first_lba = 0
(bootloader) partition[34].last_lba = 0
(bootloader) partition[34].size 0 KB
(bootloader) partition[35].name =
(bootloader) partition[35].first_lba = 0
(bootloader) partition[35].last_lba = 0
(bootloader) partition[35].size 0 KB
(bootloader) partition[36].name =
(bootloader) partition[36].first_lba = 0
(bootloader) partition[36].last_lba = 0
(bootloader) partition[36].size 0 KB
(bootloader) partition[37].name =
(bootloader) partition[37].first_lba = 0
(bootloader) partition[37].last_lba = 0
(bootloader) partition[37].size 0 KB
OKAY [ 0.289s]
finished. total time: 0.290s
fastboot format cache
Code:
fastboot format cache
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 143360 4k blocks and 35840 inodes
Filesystem UUID: 582c2894-53a4-11e8-8bf9-f98baf2837a1
Superblock backups stored on blocks:
32768, 98304
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
target didn't report max-download-size
erasing 'cache'...
OKAY [ 0.510s]
sending 'cache' (348 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.522s
---------- Post added at 05:54 PM ---------- Previous post was at 05:47 PM ----------
And the output from twrp.txt comes from the 0y3PKGYw on the pastebin page.
Burgin said:
Ok, I got past my last issues (bad cable, bad driver setup)
Here are the first three command outputs you requested.
.....
fastboot format cache
sending 'cache' (348 KB)...
FAILED (remote: Bootloader is locked.)
....
And the output from twrp.txt comes from the 0y3PKGYw on the pastebin page.
Click to expand...
Click to collapse
Thank you. It looks like you had to unlock it before running TWRP. I see some errors which should go away after you flash the latest factory image from fastboot. Then before you boot the fresh system, please make sure it is still connected to USB3 or a 2 Amp charger. If or when Android is up and running start an app like StabilityTest or some other heavy load benchmark tool. If there are no problems, disconnect the charger and see how it goes without it.
Your battery's stats:
Code:
<5>[ 3.908325] bq27541_get_psp voltage_now= 4040000 uV
<5>[ 3.909149] bq27541_get_capacity = 70% ret= 71
<5>[ 3.909973] bq27541_get_psp temperature= 287 (0.1¢XC)
<5>[ 3.910980] bq27541_get_psp current_now = 356 mA
<5>[ 3.911804] bq27541_get_psp charge_now (compensated) = 2235000 uAh
<5>[ 3.912811] bq27541_get_psp charge_avg (uncompensated) = 2365000 uAh
<5>[ 3.913635] bq27541_get_psp charge_full = 3161000 uAh
<5>[ 3.914611] bq27541_get_psp charge_design = 4090000 uAh
<5>[ 3.915466] bq27541_get_psp energy_now = 8067000 uWh
<5>[ 3.916442] bq27541_get_psp charge_counter = -51000 uWh
<5>[ 3.917266] bq27541_get_psp power_now = 1438000 uW
<5>[ 3.918243] bq27541_get_psp cycle count = 600
There is a huge drop of "charge_full" and very high "cycle count". I'd say the battery is definitely finished. I bet there are no problems or bootloops when it is connected to a good external power source via a short USB cable.
:highfive:
k23m said:
....
[*]in the folder open a DOS command window and copy/paste: fastboot boot twrp-3.2.1-0-flo.img [Enter]
....
Cheers :good:
Click to expand...
Click to collapse
I am a newbie to using TWRP and this is the first time I have attempted to try a Custom ROM for my Nexus 7 2013 (flo).
The above command saved me. I was able to go into TWRP, Wipe, Advanced Wipe, and perform a Wipe of everything except the internal storage.
I then did the adb flash recovery <latest TWRP.img> and now I get the most welcome sight of the TWRP GUI.
Many many thanks.
Related
Hi
Ive been trying all day to get this phone working properly, recently I s-off-ed my phone using alpharev, I attempted to flash the sensation rom which gave me a sdcard error cant mount mmcblk1 sdcard no such file....(mmcqblk0) ect... I fixed this with the fastboot enable command although I still cannot mount my sd either in recovery or when booted. I do have access to fastboot.
I flashed the new reflex rom 2.0.1 which works fine but when I make a call it drops, if I call tmobile it will drop the call, if I call again immediately after it continues with the call as if I'd never disconnected, if I call my partner the call is still connected at her end but if I call her again it just starts a new call and the other line is kept on hold....Wierd, Stranger still is that if I put the phone on speaker it does not disconnect, however if I turned speaker off and put the phone to my ear it disconnects after 10 seconds max.
Ive also tried this without the speaker on and away from my ear and it seems to stay connected, so this happening when I put my phone to my ear?
I dont think this is a technical issue as when I restored my phone to miui rom I had some months ago I was able to make calls without a problem although the signal was bad and it cut out if I moved too much but stayed connected more or less
Any Idea
So I tried re-partitioning my sd changing ext from 4 to 3 and back again, changing radio though I have only tried one, changing ril I have tried 3 of these, I cant make an goldcard because the although I have fastboot I cannot get adb to work, none of the apps for making goldcards detect my phone so I cant flash a new hboot or go back to stock, I am completely lost with this situation, can anyone help?
A while back I have had the same issue with line dropping as soon I put the phone to my ear. Your problem may be different, but maybe my findings will help you too.
I had an app installed, I think it was "Superpower" installed. It manages various settings for power saving, under which a setting for disabling things as soon as the screen turns off.
In my case this was the problem. Because as soon as you put the phone to your ear, the proximity sensor shuts down the screen automatically.
So then the app closed all connections, see? I uninstalled Superpower and it was OK again.
Maybe something similar in your situation, but it could be totally different as well..
Hope it helps!
ried uninstalling some likley coulprits to no avail i'm afraid, I am having trouble sorting out the usb brick I thought if I could get that working I might be able to resolve whatever is wrong, when I enter fastboot oem boot all it is giving me is
>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x21F04
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is T-MOB005
(bootloader) setting->cid::T-MOB005
(bootloader) serial number: HT******18
(bootloader) commandline from head: no_console_suspend=1 msmsdcc_sdioirq=
(bootloader) 1 wire.search_count=5
(bootloader) command line length =456
(bootloader) active commandline: board_bravo.disable_uart3=1 board_bravo.
(bootloader) usb_h2w_sw=1 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.17.05.08 androidboot.cid=T
(bootloader) -MOB005 androidboot.carrier=TMUK androidboot.mid=PB9920000 a
(bootloader) ndroidboot.keycaps=qwerty androidboot.mode=normal androidboo
(bootloader) t.serialno=3118 androidboot.bootloader=0.93.0001 no_
(bootloader) console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:20437 msec
FAILED (status read failed (Too many links))
finished. total time: 4.786s
there is no infotag, googled this and there is no info on this?
try to enable bluetooth if it doesnt then i know what the problem is
reaper7881 said:
try to enable bluetooth if it doesnt then i know what the problem is
Click to expand...
Click to collapse
I can't enable Bluetooth never have I been so happy to see that.
Sent from my HTC Desire using XDA App
i think you have a corrupt misc partition so u need to flash a new 1
let me compile the files for your CID:T-MOB005
THEN ILL UPLOAD AND TELL U HOW TO FLASH
does your usb connectivity work properly
I can fastboot but can't mount SD I can flash from SD if I use a SD reader just can't mount from recovery or pc
If u give my something to flash I can flash it from SD recovery
Sent from my HTC Desire using XDA App
first do fastboot oem enablqxdm 0
then extract and copy the two files in this archive to ur sdcard http://www.mediafire.com/?5h5593mcoblaykq
then install terminal emulator
THIS FIX IS ONLY FOR PHONES THAT ARE TMOBILE BRANDED
CID:T-MOB005
DONT TRY ON OTHER BRANDED PHONES
Ok done what now
Sent from my HTC Desire using XDA App
delete the post will all the fastboot oem boot since ur serial is still in ther
(bootloader) t.serialno=HT here 8 androidboot.bootloader=0.93.0001 no_
(bootloader) console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5
omg come to this page bro. but when u do then
move both files to /data
then open terminal then type
su
chmod 755 /data/flash_image
Im afraid that has not worked, I'm totally stumped
you havent flashed it yet lol
if you have applied the permissions then
in terminal emulator
/data/flash_image misc /data/mtd0.img
re check ur typing to make sure
then reboot and try to enable bluetooth if it enables then were done
delete the post will all the fastboot oem boot since ur serial is still in ther
(bootloader) t.serialno=HT HERE 8 androidboot.bootloader=0.93.0001 no_
(bootloader) console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5
serial number needs deleting in red on ur other post
Ok thanks Bluetooth enables yet to check usb but thank u so much hope this solves my call drop problem
Sent from my HTC Desire using XDA App
no problem bro
reaper7881 said:
no problem bro
Click to expand...
Click to collapse
Cheers reaper much respect all problems gone just by fixing the usb brick apparently it affects radio
i think i have soved the dropping calls
http://www.mediafire.com/download.php?7453qbvf78f5l50 and do the same as before
hello, this desire is kicking my ass, 4 days not fixed? of trying and searching, can some one please help
was on orange,uk,htc branded dont know if was orange branded
tried several roms some they give error or just gets to black htc screen (waited) 30 min nothing
reboot loop after s-off ?
can flash this from gold card, shipped-roms.com/download.php?category=android&model=Bravo&file=OTA_Bravo_Froyrange_CH_2.22.71.4-2.22.71.2_releasevrnkzrd85wxshyvx.zip
but then just reboots continously
here is info i have
READING INFO: OK!
10:50:33 > MODEL: BRAVO / bravo
10:50:33 > VERSION: 0.5/None/0.93.0001
10:50:33 > FIRMWARE: 2.29.405.2/5.11.05.27
10:50:33 > HARDWARE: HBOOT-8x50
10:50:33 > HTC DESIRE READ INFO: END!
-----------------------------------------------------------------
C:\Users\POWERTECH 6000\AppData\Local\Android\android-sdk\platform-tools>fastboo
t oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x21F04
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
(bootloader) serial number: HT03PPL06282
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =417
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.11.05.27 androidboot.cid=1
(bootloader) 1111111 androidboot.carrier=ALL androidboot.mid=PB992**** an
(bootloader) droidboot.keycaps=qwerty androidboot.mode=normal androidboot
(bootloader) .serialno=HT03PPL06282 androidboot.bootloader=0.93.0001 no_c
(bootloader) onsole_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:56610 msec
FAILED (status read failed (Too many links))
finished. total time: 6.879s
which ruu can i use just want to factory or get going in anyway i also noticed bottom end of phone gets really warm sometimes ?
thanks
kammy6000 said:
hello, this desire is kicking my ass, 4 days not fixed? of trying and searching, can some one please help
was on orange,uk,htc branded dont know if was orange branded
tried several roms some they give error or just gets to black htc screen (waited) 30 min nothing
reboot loop after s-off ?
can flash this from gold card, shipped-roms.com/download.php?category=android&model=Bravo&file=OTA_Bravo_Froyrange_CH_2.22.71.4-2.22.71.2_releasevrnkzrd85wxshyvx.zip
but then just reboots continously
here is info i have
READING INFO: OK!
10:50:33 > MODEL: BRAVO / bravo
10:50:33 > VERSION: 0.5/None/0.93.0001
10:50:33 > FIRMWARE: 2.29.405.2/5.11.05.27
10:50:33 > HARDWARE: HBOOT-8x50
10:50:33 > HTC DESIRE READ INFO: END!
-----------------------------------------------------------------
C:\Users\POWERTECH 6000\AppData\Local\Android\android-sdk\platform-tools>fastboo
t oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x21F04
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
(bootloader) serial number: HT03PPL06282
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =417
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.11.05.27 androidboot.cid=1
(bootloader) 1111111 androidboot.carrier=ALL androidboot.mid=PB992**** an
(bootloader) droidboot.keycaps=qwerty androidboot.mode=normal androidboot
(bootloader) .serialno=HT03PPL06282 androidboot.bootloader=0.93.0001 no_c
(bootloader) onsole_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:56610 msec
FAILED (status read failed (Too many links))
finished. total time: 6.879s
which ruu can i use just want to factory or get going in anyway i also noticed bottom end of phone gets really warm sometimes ?
thanks
Click to expand...
Click to collapse
2.3 RUU.
desire
nlooooo said:
2.3 RUU.
Click to expand...
Click to collapse
hi thanks for help , i get error 155 ,please use correct update?
i am putting in fastboot to bypass battery low error!
is this incorrect?
i have s-off
hboot 0.93.001
thanks
kammy6000 said:
hi thanks for help , i get error 155 ,please use correct update?
i am putting in fastboot to bypass battery low error!
is this incorrect?
i have s-off
hboot 0.93.001
thanks
Click to expand...
Click to collapse
You cannot ruu while s-off is there. Make it S-ON and try aggain, but before making s-on flash a custom recovery. Just to be safe
desire
race55 said:
You cannot ruu while s-off is there. Make it S-ON and try aggain, but before making s-on flash a custom recovery. Just to be safe
Click to expand...
Click to collapse
thank you for telling me s must be on that why not work!
i tried to put recovery image bravo from clockwork from fastboot but no work cos i dont have eng boot i think,android flasher need eng boot aswell and i am not rooted
can you please tell me how to put s-off again please so i just factory
thanks
I'm not sure what are you talking about, what custom recovery before you do s-on?
The proper way to do that is to flash downgrade hboot from alpharev via fastboot and then run ruu.
Sent from my HTC Desire using Flashes and Thunders
desire
nlooooo said:
I'm not sure what are you talking about, what custom recovery before you do s-on?
The proper way to do that is to flash downgrade hboot from alpharev via fastboot and then run ruu.
Sent from my HTC Desire using Flashes and Thunders
Click to expand...
Click to collapse
ok sorry, phone was unlocked/ s off by, xtc clip
so no recovery installed!
i tried to write the image from alpharev website with fastboot commands i get starting recovery, then remote not allowed
C:\Users\ kammy\AppData\Local\Android\android-sdk\platform-tools>fastboo
t flash recovery bravo.img.img
sending 'recovery' (3256 KB)...
OKAY [ 0.485s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.502s
C:\Users\kammy\AppData\Local\Android\android-sdk\platform-tools>^A
how can i write the new img please, i am not very good with htc
thanks
kammy6000 said:
ok sorry, phone was unlocked/ s off by, xtc clip
so no recovery installed!
i tried to write the image from alpharev website with fastboot commands i get starting recovery, then remote not allowed
C:\Users\ kammy\AppData\Local\Android\android-sdk\platform-tools>fastboo
t flash recovery bravo.img.img
sending 'recovery' (3256 KB)...
OKAY [ 0.485s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.502s
C:\Users\kammy\AppData\Local\Android\android-sdk\platform-tools>^A
how can i write the new img please, i am not very good with htc
thanks
Click to expand...
Click to collapse
nlooooo ment flash Alpharev downgrader.img then run 2.3 ruu
Sent from my HTC Desire
desire
jmcclue said:
nlooooo ment flash Alpharev downgrader.img then run 2.3 ruu
Sent from my HTC Desire
Click to expand...
Click to collapse
can you tell me how to do that i thought it was through the run fastboot commands (i get errors) is there another way from sd card or something
or is there a exe file? sorry for noob q's
ok do i burn the alpharev iso to disk then boot from it then install new img to phone from the program?
thanks
As I understood you got s-off via htc site?
Then you don't have access to radio and hboot partitions only to recovery, system and data so it's not allowed to flash hboot via fastboot.
You can flash recovery from here:
http://www.clockworkmod.com/rommanager/
download proper recovery.img and flash it via fastboot. You have to type the path correctly to the space where you stored it, ie:
fastboot flash recovery c:\recovery.img
Then go here:
http://forum.xda-developers.com/showthread.php?t=809328
find and flash a rom of your choice. These are custom roms and are flashable from recovery (install zip from sd card command).
desire
nlooooo said:
As I understood you got s-off via htc site?
Then you don't have access to radio and hboot partitions only to recovery, system and data so it's not allowed to flash hboot via fastboot.
You can flash recovery from here:
http://www.clockworkmod.com/rommanager/
download proper recovery.img and flash it via fastboot. You have to type the path correctly to the space where you stored it, ie:
fastboot flash recovery c:\recovery.img
Then go here:
http://forum.xda-developers.com/showthread.php?t=809328
find and flash a rom of your choice. These are custom roms and are flashable from recovery (install zip from sd card command).
Click to expand...
Click to collapse
ok thats straight forward, and i followed it but why does it keep saying ,remote not allowed failed!
i have phone in usb displaying fastboot usb is highlighted!
users\kammy\appdata\local\android\android-sdk\platform-tools\fastboot
i dont get it,why the error
thanks very much
I didn't know what's xtc clip, now I found out and I'm sure that something failed in that process cause have s-off on your device but you actually don't have it cause you can't run fastboot commands. Sorry...
desire
nlooooo said:
I didn't know what's xtc clip, now I found out and I'm sure that something failed in that process cause have s-off on your device but you actually don't have it cause you can't run fastboot commands. Sorry...
Click to expand...
Click to collapse
ok thanks everyone for help, but i will be back with results
kammy6000 said:
ok thanks everyone for help, but i will be back with results
Click to expand...
Click to collapse
ok so now i have recovery clockwork installed i think ,i am able to install a custom rom , cyanogen , then it just crashes at the
load screen the screen goes all fuzzy or it looks like its loading but not going through the whole process
is this lcd,amoled issue?
or something else i am really close but what is stopping it loading
thanks
kammy6000 said:
ok so now i have recovery clockwork installed i think ,i am able to install a custom rom , cyanogen , then it just crashes at the
load screen the screen goes all fuzzy or it looks like its loading but not going through the whole process
is this lcd,amoled issue?
or something else i am really close but what is stopping it loading
thanks
Click to expand...
Click to collapse
ok now i have alpharev hboot cm7, but all roms just crash is there specific roms only please help me
kammy6000 said:
ok now i have alpharev hboot cm7, but all roms just crash is there specific roms only please help me
Click to expand...
Click to collapse
Here you go, just search the thread, for every rom it is written if it's cm7 hboot compatible.
http://forum.xda-developers.com/showthread.php?t=809328
Was gifted a Dinc that was stuck on boot screen, reset did nothing.
DL'd the GB PB31IMG.zip (from Doug's site), ran in HBOOT .... Update is now stuck on step 2, updating the radio.
It reads like this:
Parsing...[SD ZIP]
[1] BOOTLOADER - FAIL-PU
[2} RADIO_VZ - Updating
The progress bar on the right hand side looks to be 95% full, but nothing has changed in, oh, maybe 30 mins.
Don't want to power down quite yet and risk junking it. Maybe should have tried the Froyo stock image??
Tried the Froyo image... same result, except it passed boot loader.
Could HW issues prevent radio updating?
Sent from my ThunderBolt using Tapatalk 2
What I'm looking at.... another 30 min in. May try some older stock images.
Sent from my ThunderBolt using Tapatalk 2
Each time you power down the device during a critical update like this you have a chance of bricking. I hate to say you may have gotten a defective phone.
Yeah it's looking that way. I'm curious as to just what is defective though. It's a freebie so I'm not torn over it. I'll keep playing and see if something works.
Sent from my cm_tenderloin using xda app-developers app
Have you tried a newer ruu that will update hboot? Then you could unlock your bootloader flash a recovery, do a full wipe, and try to flash a rom. Or unlock,fastboot flash misc partition, and try to downgrade to froyo again (hopefully the radio takes), then flash recovery and then the s-off patch. However the radio not updating dosent seem like a good sign.
I think it's officially a paperweight. It won't communicate with the RUU. It will list as a fastboot device but will not pull the identifier token (just says waiting for device). Maybe that is because of the HBOOT version, though. What is the oldest version that will work with the htcdev unlock? This one is on .92.
manhatton said:
I think it's officially a paperweight. It won't communicate with the RUU. It will list as a fastboot device but will not pull the identifier token (just says waiting for device). Maybe that is because of the HBOOT version, though. What is the oldest version that will work with the htcdev unlock? This one is on .92.
Click to expand...
Click to collapse
You need at least 1.02 for the identifier token stuff to work. You should be able to flash just the HBOOT through the bootloader with the PB31IMG.zip from dinc.does-it.net (the link in cmlusco's sig).
Just attempted that and may have found the problem, although I have no clue what it means. On my way to flashing the HBOOT here's where it failed:
c:\Android>fastboot oem rebootRUU
...
(bootloader) msm_nand_erase: failed, block 4091, status 0xC001A0
(bootloader) [ERR] Bad block found: 4091
(bootloader) msm_nand_dm_write_oob 0x1FF60000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF60800 2048 0 failed (-5)
(bootloader) Mark bad block 4091 failed (-5)
(bootloader) msm_nand_erase: failed, block 4092, status 0xC001A0
(bootloader) [ERR] Bad block found: 4092
(bootloader) msm_nand_dm_write_oob 0x1FF80000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF80800 2048 0 failed (-5)
(bootloader) Mark bad block 4092 failed (-5)
(bootloader) msm_nand_erase: failed, block 4093, status 0xC001A0
(bootloader) [ERR] Bad block found: 4093
(bootloader) msm_nand_dm_write_oob 0x1FFA0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFA0800 2048 0 failed (-5)
(bootloader) Mark bad block 4093 failed (-5)
(bootloader) msm_nand_erase: failed, block 4094, status 0xC001A0
(bootloader) [ERR] Bad block found: 4094
(bootloader) msm_nand_dm_write_oob 0x1FFC0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFC0800 2048 0 failed (-5)
(bootloader) Mark bad block 4094 failed (-5)
(bootloader) msm_nand_erase: failed, block 4095, status 0xC001A0
(bootloader) [ERR] Bad block found: 4095
(bootloader) msm_nand_dm_write_oob 0x1FFE0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFE0800 2048 0 failed (-5)
(bootloader) Mark bad block 4095 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF60000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 261824): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 261824
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4091
(bootloader) msm_nand_dm_write_oob 0x1FF60000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF60800 2048 0 failed (-5)
(bootloader) Mark bad block 4091 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF80000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 261888): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 261888
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4092
(bootloader) msm_nand_dm_write_oob 0x1FF80000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FF80800 2048 0 failed (-5)
(bootloader) Mark bad block 4092 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFA0000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 261952): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 261952
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4093
(bootloader) msm_nand_dm_write_oob 0x1FFA0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFA0800 2048 0 failed (-5)
(bootloader) Mark bad block 4093 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFC0000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 262016): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 262016
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4094
(bootloader) msm_nand_dm_write_oob 0x1FFC0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFC0800 2048 0 failed (-5)
(bootloader) Mark bad block 4094 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFE0000 2048 0 failed (-5)
(bootloader) [ERR] flash_write_page failed(errno 262080): page id 131072
(bootloader) [ERR] <Error>partition_write::Failed to write page 262080
(bootloader) [ERR] <Error>Roll back data and mark bad block
(bootloader) Mark Bad block: 4095
(bootloader) msm_nand_dm_write_oob 0x1FFE0000 2048 0 failed (-5)
(bootloader) msm_nand_dm_write_oob 0x1FFE0800 2048 0 failed (-5)
(bootloader) Mark bad block 4095 failed (-5)
(bootloader) [ERR] <Error>partition_write::Too many bad blocks(out of ran
(bootloader) ge)
OKAY [ 0.275s]
finished. total time: 0.277s
After that it shutoff. Any clue what this indicates?
Now, I don't what this is.... Tried rebooting into RUU again and had a different result:
(bootloader) [V=0x0, ERR=0x0, F=0x0, TPD=0x0]
(bootloader) msm_nand_dm_read_oob 0x1FF6A800 2048 0 failed (-117), correc
(bootloader) t 24 bits
(bootloader) [ERR] ECC error has been corrected(errno -117): page id 2618
(bootloader) 45
(bootloader) Polling status on channel 7 out of time...
(bootloader) dmov_exec_cmd ERROR: result: 00000000
(bootloader) [V=0x0, ERR=0x0, F=0x0, TPD=0x0]
(bootloader) msm_nand_dm_read_oob 0x1FF6B000 2048 0 failed (-117), correc
(bootloader) t 24 bits
(bootloader) [ERR] ECC error has been corrected(errno -117): page id 2618
(bootloader) 46
......40 some odd iterations of this later.....
(bootloader) Polling status on channel 7 out of time...
(bootloader) dmov_exec_cmd ERROR: result: 00000000
(bootloader) [V=0x0, ERR=0x0, F=0x0, TPD=0x0]
(bootloader) msm_nand_dm_read_oob 0x1FF7F000 2048 0 failed (-117), correc
(bootloader) t 24 bits
(bootloader) [ERR] ECC error has been corrected(errno -117): page id 2618
(bootloader) 86
(bootloader) Polling status on channel 7 out of time...
(bootloader) dmov_exec_cmd ERROR: result: 00000000
(bootloader) [V=0x0, ERR=0x0, F=0x0, TPD=0x0]
(bootloader) msm_nand_dm_read_oob 0x1FF7F800 2048 0 failed (-117), correc
(bootloader) t 24 bits
(bootloader) [ERR] ECC error has been corrected(errno -117): page id 2618
(bootloader) 87
There was more, but wouldn't show in the window. It also did not shutoff this time, however the command prompt is hung and I cannot navigate the menu with the rocker. ODD
Did you try to flash the bootloader or the ruu? You can only flash a seperate bootloader if you are s-off.
I tried running the RUU executable from the htcdev site first, when that didn't communicate with the phone I tried the 'oem rebootRUU' command to try and flash the 1.07 HBOOT from there. I was thinking of trying to use the 'flash bootloader' command, but figured it wouldn't work s-on.
To use the ruu exe the phone must be booted. And as i said before you cant flash an hboot only update unless you are s-off. You need to flash this http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip thru hboot. Place the file on your sdcard in no folders, named eaxctly PB31IMG.zip. Boot to hboot. It should automaticly find the file and prompt you to press vol up to install. Or you can do the fastboot oem rebootRUU way.
Right, right, right....
The thread was started because flashing the stock image PB31IMG wasn't working, a subsequent step was attempting oem rebootRUU which failed, and I acknowledged the s-on problem.
I'll try the stock image you provided to see if it takes.
Ugggh, this phone....
Well, that image progressed a little further than the first two. Passed bootloader, then...
1 RADIO_VZ - FAIL-PU
2 BOOT - OK
3 RECOVERY - OK
4 SYSTEM - Updating....
Stuck like this for 15 minutes. Seeings how the HBOOT was successfully updated to 1.07, I'm sorely tempted to pull the batt and try to unlock now. Guess I can't make it worse! Here it goes....
Correction. I made it worse. No booting of any sort now.
Not even hboot? Did the rest of the ruu complete or did you stop it?
Not even hboot. I let it sit for 20-25 minutes after I noticed it stuck "updating" then pulled the battery.
I shouldn't have flashed that image without asking for radio info (or md5 for that matter) as I think I remember reading somewhere that there is a particular radio that bricks the phone if it's flashed over itself.
Sent from my ThunderBolt using Tapatalk 2
More likely the batttery pull did it. Sadly we won't know. I hope that you can figure out something.
Sent from my Galaxy Nexus using Tapatalk 2
manhatton said:
Not even hboot. I let it sit for 20-25 minutes after I noticed it stuck "updating" then pulled the battery.
I shouldn't have flashed that image without asking for radio info (or md5 for that matter) as I think I remember reading somewhere that there is a particular radio that bricks the phone if it's flashed over itself.
Sent from my ThunderBolt using Tapatalk 2
Click to expand...
Click to collapse
It was radio 2.15.10.12.20 and it can be flashed over it self without issue, i have done it several times my self. The md5 is just the file url with .md5 on the end ( http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip.md5 ).
All files on dinc.does-it.net have an md5.
Hello everyone,
usually I was able to solve almost any issue with android devices by myself, simply by doing some searching here on the forums and via google. But this time it seems like that I've screwed things up big time, since I couldn't really find anyone having the same issue as I have.
My device is a Nexus 7 2013 LTE. It's unlocked and was running rooted with a custom ROM before, without any real issues. Since I traveled a lot with it, I was using the encryption as well. After I tried wiping the device, things went south. At first TWRP was unable to decrypt the data (?) partition but that was due some outdated version which I got fixed by installing the most recent version of TWRP (3.0.0.0) via fastboot. Unfortunately The device doesn't boot into the OS anymore but at the same time, I can't wipe any of the existing partitions using the TWRP GUI and I haven't even bothered trying to flash any ROM on the device.
Here are some logs:
Code:
Updateing partition details...
...done
Unable to mount storage
Full SELinux support is present.
Data successfully decrypted, new block devices: '/dev/block/dm-0'
Updateing partition details...
...done
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/data' (Invalid argument)
MTP Enabled
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to wipe dalvik
Updating partition details...
...done
Unable to mount storage
I feel like I messed up the partitions or something but I'm not quite sure if that's actually the case. And even if so, wouldn't know how to fix that. If there is any more information I can provide to make troubleshooting easier, I'll gladly do so.
Any help would be highly appreciated, thank you very much.
All you need is:
run: fastboot format userdata
run: fastboot reboot
wait for the long first OS start
k23m said:
All you need is:
run: fastboot format userdata
run: fastboot reboot
wait for the long first OS start
Click to expand...
Click to collapse
Thanks for your reply!
I tried that out, unfortunately without any success.
Code:
[email protected]:~# fastboot devices
0876df52 fastboot
[email protected]:~# fastboot format userdata
formatting 'userdata' partition...
FAILED (command write failed (Bad file descriptor))
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[email protected]:~#
bl4cKz4cK said:
I tried that out, unfortunately without any success
Click to expand...
Click to collapse
Interesting, note...
Code:
fastboot format userdata
Creating filesystem with parameters:
Size: 28856791040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7045115
Block groups: 215
Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
erasing 'userdata'...
OKAY [ 19.767s]
sending 'userdata' (139085 KB)...
OKAY [ 4.797s]
writing 'userdata'...
OKAY [ 5.985s]
finished. total time: 30.564s
Please post the output of fastboot oem gpt-info
bl4cKz4cK said:
I can't wipe any of the existing partitions using the TWRP GUI
Click to expand...
Click to collapse
I see, go TWRP - Wipe - Format Data ('...removes encryption...')
k23m said:
I see, go TWRP - Wipe - Format Data ('...removes encryption...')
Click to expand...
Click to collapse
Code:
[email protected]:~# fastboot oem gpt-info
...
(bootloader) partition[1].name = radio
(bootloader) partition[1].first_lba = 131072
(bootloader) partition[1].last_lba = 306143
(bootloader) partition[1].size 87536 KB
(bootloader) partition[2].name = modemst1
(bootloader) partition[2].first_lba = 393216
(bootloader) partition[2].last_lba = 399359
(bootloader) partition[2].size 3072 KB
(bootloader) partition[3].name = modemst2
(bootloader) partition[3].first_lba = 399360
(bootloader) partition[3].last_lba = 405503
(bootloader) partition[3].size 3072 KB
(bootloader) partition[4].name = persist
(bootloader) partition[4].first_lba = 524288
(bootloader) partition[4].last_lba = 554287
(bootloader) partition[4].size 15000 KB
(bootloader) partition[5].name = m9kefs1
(bootloader) partition[5].first_lba = 655360
(bootloader) partition[5].last_lba = 656919
(bootloader) partition[5].size 780 KB
(bootloader) partition[6].name = m9kefs2
(bootloader) partition[6].first_lba = 656920
(bootloader) partition[6].last_lba = 658479
(bootloader) partition[6].size 780 KB
(bootloader) partition[7].name = m9kefs3
(bootloader) partition[7].first_lba = 786432
(bootloader) partition[7].last_lba = 787991
(bootloader) partition[7].size 780 KB
(bootloader) partition[8].name = fsg
(bootloader) partition[8].first_lba = 787992
(bootloader) partition[8].last_lba = 794135
(bootloader) partition[8].size 3072 KB
(bootloader) partition[9].name = sbl1
(bootloader) partition[9].first_lba = 917504
(bootloader) partition[9].last_lba = 920503
(bootloader) partition[9].size 1500 KB
(bootloader) partition[10].name = sbl2
(bootloader) partition[10].first_lba = 920504
(bootloader) partition[10].last_lba = 923503
(bootloader) partition[10].size 1500 KB
(bootloader) partition[11].name = sbl3
(bootloader) partition[11].first_lba = 923504
(bootloader) partition[11].last_lba = 927599
(bootloader) partition[11].size 2048 KB
(bootloader) partition[12].name = aboot
(bootloader) partition[12].first_lba = 927600
(bootloader) partition[12].last_lba = 937839
(bootloader) partition[12].size 5120 KB
(bootloader) partition[13].name = rpm
(bootloader) partition[13].first_lba = 937840
(bootloader) partition[13].last_lba = 938863
(bootloader) partition[13].size 512 KB
(bootloader) partition[14].name = boot
(bootloader) partition[14].first_lba = 1048576
(bootloader) partition[14].last_lba = 1081343
(bootloader) partition[14].size 16384 KB
(bootloader) partition[15].name = tz
(bootloader) partition[15].first_lba = 1179648
(bootloader) partition[15].last_lba = 1180671
(bootloader) partition[15].size 512 KB
(bootloader) partition[16].name = pad
(bootloader) partition[16].first_lba = 1180672
(bootloader) partition[16].last_lba = 1180673
(bootloader) partition[16].size 1 KB
(bootloader) partition[17].name = sbl2b
(bootloader) partition[17].first_lba = 1180674
(bootloader) partition[17].last_lba = 1183673
(bootloader) partition[17].size 1500 KB
(bootloader) partition[18].name = sbl3b
(bootloader) partition[18].first_lba = 1183674
(bootloader) partition[18].last_lba = 1187769
(bootloader) partition[18].size 2048 KB
(bootloader) partition[19].name = abootb
(bootloader) partition[19].first_lba = 1187770
(bootloader) partition[19].last_lba = 1198009
(bootloader) partition[19].size 5120 KB
(bootloader) partition[20].name = rpmb
(bootloader) partition[20].first_lba = 1198010
(bootloader) partition[20].last_lba = 1199033
(bootloader) partition[20].size 512 KB
(bootloader) partition[21].name = tzb
(bootloader) partition[21].first_lba = 1199034
(bootloader) partition[21].last_lba = 1200057
(bootloader) partition[21].size 512 KB
(bootloader) partition[22].name = system
(bootloader) partition[22].first_lba = 1310720
(bootloader) partition[22].last_lba = 3031039
(bootloader) partition[22].size 860160 KB
(bootloader) partition[23].name = cache
(bootloader) partition[23].first_lba = 3031040
(bootloader) partition[23].last_lba = 4177919
(bootloader) partition[23].size 573440 KB
(bootloader) partition[24].name = misc
(bootloader) partition[24].first_lba = 4194304
(bootloader) partition[24].last_lba = 4196351
(bootloader) partition[24].size 1024 KB
(bootloader) partition[25].name = recovery
(bootloader) partition[25].first_lba = 4325376
(bootloader) partition[25].last_lba = 4345855
(bootloader) partition[25].size 10240 KB
(bootloader) partition[26].name = DDR
(bootloader) partition[26].first_lba = 4456448
(bootloader) partition[26].last_lba = 4456463
(bootloader) partition[26].size 8 KB
(bootloader) partition[27].name = ssd
(bootloader) partition[27].first_lba = 4456464
(bootloader) partition[27].last_lba = 4456479
(bootloader) partition[27].size 8 KB
(bootloader) partition[28].name = m9kefsc
(bootloader) partition[28].first_lba = 4456480
(bootloader) partition[28].last_lba = 4456481
(bootloader) partition[28].size 1 KB
(bootloader) partition[29].name = metadata
(bootloader) partition[29].first_lba = 4587520
(bootloader) partition[29].last_lba = 4587583
(bootloader) partition[29].size 32 KB
(bootloader) partition[30].name = userdata
(bootloader) partition[30].first_lba = 4718592
(bootloader) partition[30].last_lba = 60424158
(bootloader) partition[30].size 27852783 KB
(bootloader) partition[31].name =
(bootloader) partition[31].first_lba = 0
(bootloader) partition[31].last_lba = 0
(bootloader) partition[31].size 0 KB
(bootloader) partition[32].name =
(bootloader) partition[32].first_lba = 0
(bootloader) partition[32].last_lba = 0
(bootloader) partition[32].size 0 KB
(bootloader) partition[33].name =
(bootloader) partition[33].first_lba = 0
(bootloader) partition[33].last_lba = 0
(bootloader) partition[33].size 0 KB
(bootloader) partition[34].name =
(bootloader) partition[34].first_lba = 0
(bootloader) partition[34].last_lba = 0
(bootloader) partition[34].size 0 KB
(bootloader) partition[35].name =
(bootloader) partition[35].first_lba = 0
(bootloader) partition[35].last_lba = 0
(bootloader) partition[35].size 0 KB
(bootloader) partition[36].name =
(bootloader) partition[36].first_lba = 0
(bootloader) partition[36].last_lba = 0
(bootloader) partition[36].size 0 KB
(bootloader) partition[37].name =
(bootloader) partition[37].first_lba = 0
(bootloader) partition[37].last_lba = 0
(bootloader) partition[37].size 0 KB
OKAY [ 0.150s]
finished. total time: 0.150s
[email protected]:~#
Tried formating data as you suggested:
Code:
Formatting Data using make_ext4fs...
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Rebooted recovery (as suggested in the log) but still, no luck. It still asked me for my encryption password by the way so I'm assuming that formatting data did not work.
bl4cKz4cK said:
Rebooted recovery (as suggested in the log) but still, no luck. It still asked me for my encryption password by the way so I'm assuming that formatting data did not work.
Click to expand...
Click to collapse
No worries at all. We could use mke2fs but CWM can do it faster.
download CWM to your folder with fastboot app
boot N7 in fastboot mode
run: fastboot boot recovery-clockwork-touch-6.0.4.3-flo.img
in CWM select mount and storage
do format /data and format /data/media
This should fix it :good:
Note - we're not flashing new recovery, CWM is only temporarily booted
k23m said:
No worries at all. We could use mke2fs but CWM can do it faster.
download CWM to your folder with fastboot app
boot N7 in fastboot mode
run: fastboot boot recovery-clockwork-touch-6.0.4.3-flo.img
in CWM select mount and storage
do format /data and format /data/media
This should fix it :good:
Note - we're not flashing new recovery, CWM is only temporarily booted
Click to expand...
Click to collapse
Thanks again for your continuous support, I really appreciate that.
I gave CWM a go and did the steps you posted. This time there was no error message, however, when I booted back into TWRP, it still asked me for the encryption password.
bl4cKz4cK said:
I gave CWM a go and did the steps you posted. This time there was no error message, however, when I booted back into TWRP, it still asked me for the encryption password.
Click to expand...
Click to collapse
This is getting serious. Let's check now fastboot format userdata - still with errors?
Then please extract "recovery.img" file from your preferred stock factory image or just download this LMY48T
Run fastboot boot recovery.img and do factory reset from it.
Well, how did it go?
I checked TWRP source code and noticed a bug in the Wipe_Encryption() function:
partition.cpp
Code:
} else {
string Command = "flash_image " + Crypto_Key_Location + " /dev/zero";
TWFunc::Exec_Cmd(Command);
}
"flash_image" does not work with "/dev/zero", it insists on a real image file. We can fix it manually from adb shell.
I'm currentyl trying the first thing (fastboot format userdata) and it's still going, since like two hours. I'm gonna leave it running for the night, just to make sure. If that won't work I'm gonna give the stock recovery a go tomorrow.
k23m said:
Well, how did it go?
Click to expand...
Click to collapse
Not too well :/
{
"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"
}
bl4cKz4cK said:
Not too well :/
Click to expand...
Click to collapse
It's OK, just more clean up to do.
Please boot TWRP and run these commands in the following order:
Code:
adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/metadata of=/md
adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/mc
adb shell tar cvzf mm.tgz md mc tmp/recovery.log
adb pull mm.tgz mm.tgz
You will find mm.tgz in your adb app folder, attach it to your next post.
Next adb reboot bootloader
Wait and run: fastboot format cache
I need to see the mm.tgz file before the next step. In the meantime you could try stock recovery reset again but this time use LMY48T from my earlier link.
Instead of ADB you could use a scripted zip run from USB OTG. Let me know if you prefer this option and I'll prepare it for you.
Sorry for the late response, I had little free time to look into this.
For some reason, it doesn't boot int TWRP anymore. I tried to "fastboot boot twrp-3.0.0-0-deb.img" but it gets stuck and never goes past the loading screen. Bootloader still works but neither flashing nor booting a recovery was any successful.
Please extract 'recovery.img' from a stock factory image and check if fastboot boot recovery.img works. Download and try twrp-2.8.6.0 because the newer versions are unreliable for me too. What are the error messages when you are flashing? Did you flash a stock image?
I think I got the same issue... solved it by install a factory image from here.
https://developers.google.com/android/nexus/images#instructions
After that I wiped data and cache via stock recovery. Worked for me
Okay I've tried the following:
Booting twrp-2.8.6.0 via fastboot boot -> works
Booting stock recovery via fastboot boot -> works
However, trying to flash the stock recovery (just like any other recovery) failed.
Code:
sending 'recovery' (8188 KB)...
OKAY [ 0.281s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 90.059s
After that I tried to use the dd commands you posted prior.
Code:
C:\>adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/metadata of=/md
dd: /dev/block/platform/msm_sdcc.1/by-name/metadata: I/O error
C:\>adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/mc
dd: /dev/block/platform/msm_sdcc.1/by-name/misc: I/O error
Finally I tried to flash the stock image using the flash-all.bat:
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.561s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: 0.016s
sending 'radio' (76038 KB)...
OKAY [ 2.524s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 92.572s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28521246720
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6963195
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1741488 inodes and 153337/6963195 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: FLO-04.05
Baseband Version.....: DEB-Z00_2.44.0_0213
Serial Number........: 0876df52
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (7442 KB)...
OKAY [ 0.250s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.054s
Press any key to exit...
bl4cKz4cK said:
trying to flash the stock recovery (just like any other recovery) failed.
Click to expand...
Click to collapse
It's time to have a look at your hardware log:
boot TWRP
connect PC
run: adb shell dmesg > dmesg
find 'dmesg' file in your adb folder
attach it here or upload to http://pastebin.com
k23m said:
It's time to have a look at your hardware log:
boot TWRP
connect PC
run: adb shell dmesg > dmesg
find 'dmesg' file in your adb folder
attach it here or upload to http://pastebin.com
Click to expand...
Click to collapse
There you go.
I download from baidu,just sharing.
v1104 for Android 9
v1210 for Android 10
Changlogs:
2019.12.10更新内容（安卓10）：
1.更新支持官方安卓10的系统。
2.官方系统跨大版本不能使用twrp升级卡刷，建议官方rec卡刷（例如安卓9升级安卓10时），相同安卓版本应该是可以twrp升降级卡刷的。
3.不太会刷机的，不建议乱刷，很容易成砖，刷机属于自愿行为，本人对刷机造成的损失概不负责。
4.另外目前貌似magisk不支持ed模块等。
5.刷了magisk之后，格式化可能会导致进不了系统，如果想格式化，建议先恢复官方boot等分区。
2019.11.04更新内容（安卓9）：
1.升级内置magisk20.0等。
2.删除签名boot功能，替换为防止覆盖TWRP功能，两者都是可以起到防止覆盖twrp的作用。
3.其他功能的调整优化。
4.每次卡刷官方包或root后，执行一次关闭avb2.0校验的功能，防止出现系统损坏提示的情况。
MOD EDIT: Please post only in English according to the FORUM RULES,translation added below:
Changelogs:
2019.12.10 Update (Android 10):
1. Update the system that supports the official Android 10.
2. The official system across the large version can not use the twrp upgrade card brush, it is recommended that the official rec card brush (e.g. Android 9 upgrade Android 10, the same Android version should be able to twrp lift level card brush.
3. Not very brush machine, do not recommend scribbling, it is easy to become brick, brush machine is a voluntary act, I am not responsible for the loss caused by the brush machine.
4. In addition, it seems that magisk does not support ed modules, etc.
5. After brushing the magisk, formatting may result in no system, if you want to format, it is recommended to restore the official boot and other partitions first.
2019.11.04 Update (Android 9):
1. Upgrade built-in magisk20.0, etc.
2. Remove the signature boot function and replace it with the TWRP function, both of which can play a role in preventing overwriting twrp.
3. Adjustment and optimization of other functions.
4. After each card brush official package or root, perform a close avb2.0 check function to prevent the occurrence of system damage prompt.
Twrp Support English?
razu031 said:
Twrp Support English?
Click to expand...
Click to collapse
I flashed 1104,support english and ZHS
using indian variant and having ROM global indian MIUI 11 with android Pie. Will the PIE version work for my device??
Version 11.04 of this TWRP (as well as previous version 09.24) flash correctly on EEA phone w/ EEA Pie Rom (I cannot just boot them fyi) and work with both backup and restore of recommended Nandroid backups, which means, boot, data, system-image (I tested myself, flawless)
@saiz0313: I am not sure if anyone can get in touch with this TWRP dev/team (LR) but I am willing to report the following issue.
As soon as you enable Second Space, w/ or w/o password (does not matter I tested both), it breaks the backup process at data after just a few % with code ERROR: 255 .
Please see attached pictures.
Maybe you don't format data before rebooting system?
Muad.Dib said:
Version 11.04 of this TWRP (as well as previous version 09.24) flash correctly on EEA phone w/ EEA Pie Rom (I cannot just boot them fyi) and work with both backup and restore of recommended Nandroid backups, which means, boot, data, system-image (I tested myself, flawless)
@saiz0313: I am not sure if anyone can get in touch with this TWRP dev/team (LR) but I am willing to report the following issue.
As soon as you enable Second Space, w/ or w/o password (does not matter I tested both), it breaks the backup process at data after just a few % with code ERROR: 255 .
Please see attached pictures.
Click to expand...
Click to collapse
I never have same issue like you.
You can report it to https://www.weibo.com/u/6033736159
It's wzsx150's blog
saiz0313 said:
I never have same issue like you.
You can report it to https://www.weibo.com/u/6033736159
It's wzsx150's blog
Click to expand...
Click to collapse
Thanks.
Did you have Second Space ENABLED when you tried to backup? Because that's what caused me problems.
Apparently it seems to be an issue which roots directly from within TWRP main sources, LR team adapted for this version. Agent_Fabulous version has the exact same issue with exact same error and they mentioned to me there was indeed an issue with Work Profiles/Mutlipe User profiles in TWRP. That's probably a wide issue on all devices.
Anyway I think that's good to mention so people know, they need to find an alternate way to backup their second space settings before deleting it completely, prior making a more complete TWRP backup.
Regards.
Muad.Dib said:
Thanks.
Did you have Second Space ENABLED when you tried to backup? Because that's what caused me problems.
Apparently it seems to be an issue which roots directly from within TWRP main sources, LR team adapted for this version. Agent_Fabulous version has the exact same issue with exact same error and they mentioned to me there was indeed an issue with Work Profiles/Mutlipe User profiles in TWRP. That's probably a wide issue on all devices.
Anyway I think that's good to mention so people know, they need to find an alternate way to backup their second space settings before deleting it completely, prior making a more complete TWRP backup.
Regards.
Click to expand...
Click to collapse
I just backup to internal Storage,and copy to PC.
saiz0313 said:
I just backup to internal Storage,and copy to PC.
Click to expand...
Click to collapse
Yes simple backup/restore on regular phone profile (only 1 profile/user on the phone) also works for me and I can get the backup anywhere I want.
But, if I enable 2nd profile, work profile, 2nd user, through Second Space option (that's a MIUI feature that deals with the work profile feature for you) then it breaks the backup.
So if you are not using this feature yourself, it is not exactly like me
Regards.
----DELETED----
The best & the perfect
This is the ONLY TWRP that works PERFECTLY!!
From my experience, LR.Team's always got the best build for Xiaomi's.
Here's the latest in my folder: https://mega.nz/folder/cMAT3Q4b#7CbPV7sbEuSEdP7cehXJ-w
GUYS, I'M SERIOUS!!
If you don't wanna ended up with bricked device, just use this TWRP.
LR.Teams' TWRP NEVER FAILED ME, not even once since Mi5 - Mi5s Plus - Mi Pad 4 - POCO F1, now Redmi Note 8 Pro.
Plus this one can stick on every update & support OTA.
Hi! I read the dolby not work on Android 10, but V4A works on Android 10?
Hi, I've EU 11.0.3 firmware
I tried official 3.3.1.0 > black screen
Then: 3.3.1.09 Ask password to decrypt files
3.3.1.11 Ask password too
3.3.2B Doesn't work at all > reboot
Spleeny97 said:
Hi, I've EU 11.0.3 firmware
I tried official 3.3.1.0 > black screen
Then: 3.3.1.09 Ask password to decrypt files
3.3.1.11 Ask password too
3.3.2B Doesn't work at all > reboot
Click to expand...
Click to collapse
If you're using this TWRP: ask password > put in your lockscreen password.
3.3.2B working perfectly here, what do you mean by doesn't work at all? bootloop?
Try to flash full ROM & redo again, also 3.3.2B is only for Android 10.
Thanks
I tried 3.3.2B on Android 9... that's why.
And yes I was only my lockscreen passwd.... thank you anyway
I got the working 3.3.1.0 version on the Begonia telegram thread.
What are the differences between this one and the 3.3.2B version ? Should I replace it ?
Spleeny97 said:
Thanks
I tried 3.3.2B on Android 9... that's why.
And yes I was only my lockscreen passwd.... thank you anyway
I got the working 3.3.1.0 version on the Begonia telegram thread.
What are the differences between this one and the 3.3.2B version ? Should I replace it ?
Click to expand...
Click to collapse
the changelog says sth about magisk & another bootloop prevention but nothing more...
I'm using 3.3.2b atm & it's running just like 3.3.1.0 without problem or visible change...
Help! My Redmi Note 8 Pro Bricked!
Hi, please help!
My Redmi Note 8 Pro (China Rom) is stuck on Bootloop. Can't go into recovery, just blinks then goes back to bootloop. Can go into Fastboot however, but I don't know how to flash it. I have downloaded a stock MIUI 11 .TGZ file
(begonia_images_V11.0.3.0.PGGCNXM_20191214.0000.00_9.0_cn_9fed9ef495.tgz)
I already have platform tools and adb tools on my laptop and I was able to get this by typing PS C:\platform-tools> .\fastboot getvar all:
PS C:\platform-tools> .\fastboot getvar all
(bootloader) anti: 1
(bootloader) tokenversion: 2
(bootloader) token: VQECIQEEAlkotQMHYmVnb25pYQIQfduLgMcEMFR69LurrBJk/g==
(bootloader) max-download-size: 0x8000000
(bootloader) variant:
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x0
(bootloader) hw-revision: ca00
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 3638mV
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 1bf76f8000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cust: 34000000
(bootloader) partition-type:cust: ext4
(bootloader) partition-size:exaid: 8000000
(bootloader) partition-type:exaid: ext4
(bootloader) partition-sizeem_misc1: 1000000
(bootloader) partition-typeem_misc1: ext4
(bootloader) partition-size:gsort: 1000000
(bootloader) partition-type:gsort: ext4
(bootloader) partition-size:cache: 1b000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: e0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:vendor: 60000000
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:tee2: 980000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:dtbo: 2000000
(bootloader) partition-type:dtbo: raw data
(bootloader) partition-size:logo: 4000000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:boot: 4000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk2: 200000
(bootloader) partition-type:lk2: raw data
(bootloader) partition-size:lk: 200000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:gz2: 2000000
(bootloader) partition-type:gz2: raw data
(bootloader) partition-size:gz1: 2000000
(bootloader) partition-type:gz1: raw data
(bootloader) partition-size:cam_vpu3: f00000
(bootloader) partition-type:cam_vpu3: raw data
(bootloader) partition-size:cam_vpu2: f00000
(bootloader) partition-type:cam_vpu2: raw data
(bootloader) partition-size:cam_vpu1: f00000
(bootloader) partition-type:cam_vpu1: raw data
(bootloader) partition-size:sspm_2: 100000
(bootloader) partition-type:sspm_2: raw data
(bootloader) partition-size:sspm_1: 100000
(bootloader) partition-type:sspm_1: raw data
(bootloader) partition-size:scp2: 600000
(bootloader) partition-type:scp2: raw data
(bootloader) partition-size:scp1: 600000
(bootloader) partition-type:scp1: raw data
(bootloader) partition-size:audio_dsp: 400000
(bootloader) partition-type:audio_dsp: raw data
(bootloader) partition-size:spmfw: 100000
(bootloader) partition-type:spmfw: raw data
(bootloader) partition-size:boot_para: 1a00000
(bootloader) partition-type:boot_para: raw data
(bootloader) partition-size:md1img: 9600000
(bootloader) partition-type:md1img: raw data
(bootloader) partition-size:nvram: 4000000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:efuse: 80000
(bootloader) partition-type:efuse: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-size:sec1: 200000
(bootloader) partition-type:sec1: raw data
(bootloader) partition-sizetp: 3000000
(bootloader) partition-typetp: raw data
(bootloader) partition-size:seccfg: 800000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizerotect2: 800000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: 800000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-sizeersist: 4678000
(bootloader) partition-typeersist: ext4
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 4000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:nvcfg: 2000000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:vbmeta: 800000
(bootloader) partition-type:vbmeta: raw data
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:expdb: 1400000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:misc: 400000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:recovery: 4000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-sizereloader: 400000
(bootloader) partition-typereloader: raw data
(bootloader) serialno: 6lea7p55amiv6dtc
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) crc: 1
(bootloader) kernel: lk
(bootloader) product: begonia
(bootloader) slot-count: 0
(bootloader) version-baseband: MOLY.LR13.R1.TC8.SP.V1.P82
(bootloader) version-bootloader: begonia-95e44f1-20191021162617-20191213
(bootloader) version-preloader:
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 2.127s
PLEASE HELP!
johnnybee.27 said:
Hi, please help!
My Redmi Note 8 Pro (China Rom) is stuck on Bootloop. Can't go into recovery, just blinks then goes back to bootloop. Can go into Fastboot however, but I don't know how to flash it. I have downloaded a stock MIUI 11 .TGZ file
(begonia_images_V11.0.3.0.PGGCNXM_20191214.0000.00_9.0_cn_9fed9ef495.tgz)
Click to expand...
Click to collapse
wrong thread bro.... this is about TWRP, not brick recovery....
beside, this TWRP ver only support ANDROID 10, not ANDROID 9.