Related
Q&A for [ROM] N5 L Developer Preview LPX13D + IMG & Sys Dump
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
4.4.4 to newest L preview
I am currently running stock rooted 4.4.4 and I want to upgrade to a stock rooted L preview (the one as of today). I also want to do a full wipe of my phone to start fresh. I have already backed up all of my pictures/music/important files to my computer. Can some one offer me advice?
infinte login?
Hi, does someone is having problemns when in the setup you put your password, then it takes infinite to load?
I falsh it by fastboot and I lost recovery, there is only android robot icon, when Im trying to get there, and few my colleagues from polish forum. I cannot flash TWRP, error. Any solution?
emines said:
I falsh it by fastboot and I lost recovery, there is only android robot icon, when Im trying to get there, and few my colleagues from polish forum. I cannot flash TWRP, error. Any solution?
Click to expand...
Click to collapse
Flash again in bootloader mode
---------- Post added at 10:07 PM ---------- Previous post was at 09:20 PM ----------
For root, flash via fast boot : http://forum.xda-developers.com/showpost.php?p=56096429&postcount=2889
Just flashed v3 with /system mounted and unmounted. Mounted, it got stuck just after the MD5 verification, unmounted it flashed successfully but is now stuck on a black screen after rebooting. On TWRP, fresh install, multirom but installed as the primary ROM.
hi how did u flash it?
btw I thought the Nav bar was supposed to match the color of app's as well and not just the status bar
I flashed the zip and set up is force closing... Anybody facing this issue? I flashed via twrp and multirom
how do we turn off and on heads up on the newest L preview? or is it just automatic when in full screen mode?
darshanbangre said:
I flashed the zip and set up is force closing... Anybody facing this issue? I flashed via twrp and multirom
Click to expand...
Click to collapse
Same issue for me!!!
Hello guys...
My questions are fairly simple...hope i can get the best answer and help...tq anyway for everbody reading this...
1. The exact step to flash the latest Lollipop? Is it as easy as flash the flashable zip i found on the OP
2. What will happen to my Root if I install using that zip? Can i return to twrp..or do i lose it?
Tq again guys...
asd87 said:
This is what I get when I enter those commands for fastboot.
[email protected]:~$ adb reboot bootloader
[email protected]:~$ fastboot devices
060327310074fffbfastboot
[email protected]:~$ fastboot flash-all.bat
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
[email protected]:~
Click to expand...
Click to collapse
No, you are doing it wrong. flash-all.bat is batch file, so just double click it to flash everything.
So if I install via fastboot will i lose root and my custom recovery?
What is decryption key?
What is the difference between fastboot flash-all.bat and fastboot flash-all.sh? Thanks?<br />
<br />
Enviado desde mi Nexus 7 mediante Tapatalk
Enviado desde mi Nexus 7 mediante Tapatalk
Getting Root
The rootable boot file is a zip...can I just flash that in a recovery? In the guide you said that it was a boot.img which is confusing me.
jordirpz said:
What is the difference between fastboot flash-all.bat and fastboot flash-all.sh? Thanks?<br />
<br />
Enviado desde mi Nexus 7 mediante Tapatalk
Enviado desde mi Nexus 7 mediante Tapatalk
Click to expand...
Click to collapse
the .bat file is for use on windows.
the .sh file is for use on linux
Thank for reply. And this command erase my internal memory?thanks <br />
<br />
Enviado desde mi Nexus 7 mediante Tapatalk<br/>
Enviado desde mi Nexus 7 mediante Tapatalk
Damn it, I just started doing the fastboot method. Also you took down the instructions from the first page. I just finished flash-all, now what? If I remember correctly I flash twrp right?
@Mylenthes
Flash LPX13D IMG files
Flash twrp
Reboot into recovery
Flash rootable boot.img and then supersu
Reboot
- quote not working on my browser for some reason.
Hi everyone,
I need some help and currently I am a bit desperate. I tried to flash my Poco X3 as I did already a couple of times, but this time it was unable to mount partitions in recovery and therefore I was not able to flash any ROM. That's why I thought it might be good to use the MIFlash tool and fastboot-flash the stock ROM, hoping the partitions will be fine again. While the progress bar in the tool is full and we reach around one hour flashing time, the process seems still not completed (says still "flashing")
Do you have any ideas what could be wrong?
My configuration is as follows:
Poco X3 NFC Global
Windows 10
MiFlash 2020.3.14.0
Stock ROM used: surya_global_images_V12.0.7.0.QJGMIXM_20201221.0000.00_10.0_global_20d93168ac.tgz
Best regards and thank you all for help.
Muenzi
EDIT: Finally, I managed to restore my phone. To save you from reading the whole thread, which is full with creative ideas to unbrick the phone you can jump to the last post. There I described my final solution and ruled out, what probably my mistake with the MiFlash Tool was.
Muenzi said:
Hi everyone,
I need some help and currently I am a bit desperate. I tried to flash my Poco X3 as I did already a couple of times, but this time it was unable to mount partitions in recovery and therefore I was not able to flash any ROM. That's why I thought it might be good to use the MIFlash tool and fastboot-flash the stock ROM, hoping the partitions will be fine again. While the progress bar in the tool is full and we reach around one hour flashing time, the process seems still not completed (says still "flashing")
Do you have any ideas what could be wrong?
My configuration is as follows:
Poco X3 NFC Global
Windows 10
MiFlash 2020.3.14.0
Stock ROM used: surya_global_images_V12.0.7.0.QJGMIXM_20201221.0000.00_10.0_global_20d93168ac.tgz
Best regards and thank you all for help.
Muenzi
Click to expand...
Click to collapse
Did you do anything before you noticed your partitions are fried?
jjgvv said:
Did you do anything before you noticed your partitions are fried?
Click to expand...
Click to collapse
Yes I installed OrangeFox as a recovery. From there on, everything get messed up.
If nescessary to know, the BL is unlocked of course. I backuped all data from the phone. So I do not need a safe way to get them back. I am happy when the phone can operate a reliable OS again.
https://github.com/phhusson/treble_experimentations/releases/download/v300.l/system-roar-arm64-aonly-vanilla.img.xz
Ok extract to .img and fastboot flash the above system image and send me the results to see how seriously your system partition is fried.
jjgvv said:
https://github.com/phhusson/treble_experimentations/releases/download/v300.l/system-roar-arm64-aonly-vanilla.img.xz
Ok extract to .img and fastboot flash the above system image and send me the results to see how seriously your system partition is fried.
Click to expand...
Click to collapse
Thank you for your help. Can you tell me please to which partition this has to be flashed? And what will be the outout I can send you (probably a log file?).
So lets say commands instructions like
fastboot flash system system-roar-arm64-aonly-vanilla.img
Click to expand...
Click to collapse
would be really cool to avoid confussion and mistakes.
Anyway, it is 3 am here and I have to get up in around 4 hours. So I will leave and take a nap. Maybe I can ask you to wait for my reply? And again, thank you so much for your help.
Best regards
Stephan
yes yes fastboot flash system system-roar-arm64-aonly-vanilla.img
Muenzi said:
And what will be the outout I can send you (probably a log file?).
Click to expand...
Click to collapse
I need What happens in the cmd window like:
Code:
Desktop-XCRXAJB > C:\platform tools >
fastboot flash system system-roar-arm64-aonly-vanilla.img
Reported max download size = 2580192068 bytes （ 2.7 GB）
sending 'system' （2070713691 bytes）
OKAY （1576 secs）
writing 'system' （2070713691 bytes）
FAILED （remote : failed to mount 'system' : system partition layout is 'null'）
jjgvv said:
yes yes fastboot flash system system-roar-arm64-aonly-vanilla.img
Click to expand...
Click to collapse
Thats the outout:
Code:
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
sending sparse 'system' 1/3 (786328 KB)...
OKAY [ 21.029s]
writing 'system' 1/3...
FAILED (remote: Partition not found)
finished. total time: 21.031s
So, I have to go now. See you in a couple of hours.
adb shell
parted /dev/block/mmcblk0
print
see you soon
jjgvv said:
adb shell
parted /dev/block/mmcblk0
print
Click to expand...
Click to collapse
Too exciting too sleep. But I really have to. :-D
Thats why last question,
Code:
adb shell
in fastboot or in recovery as in fastboot the command tells me that no device/emulator was found.
Muenzi said:
Too exciting too sleep. But I really have to. :-D
Thats why last question,
Code:
adb shell
in fastboot or in recovery as in fastboot the command tells me that no device/emulator was found.
Click to expand...
Click to collapse
recovery
jjgvv said:
recovery
Click to expand...
Click to collapse
Code:
parted /dev/block/mmcblk0
/sbin/sh: parted: inaccessible or not found
Tab completion showed after mmcblk0:
Code:
parted /dev/block/mmcblk0
mmcblk0 mmcblk0p1
So it seems to be existing with one partition.
Muenzi said:
Code:
parted /dev/block/mmcblk0
/sbin/sh: parted: inaccessible or not found
Tab completion showed after mmcblk0:
Code:
parted /dev/block/mmcblk0
mmcblk0 mmcblk0p1
So it seems to be existing with one partition.
Click to expand...
Click to collapse
oh so probably Orangefox fried your other partitions
jjgvv said:
oh so probably Orangefox fried your other partitions
Click to expand...
Click to collapse
What happens when flash TWRP
jjgvv said:
What happens when flash TWRP
Click to expand...
Click to collapse
I already did. The problem persists. To clarify, all the last steps were already performed with TWRP as recovery. But the problem occurred first under TWRP.
Is there any chance to recreate the partition table?
maybe but complicated
Hi you may try boot from sd card
[HOW TO] BOOT FROM SD CARD [SUCCESSFULLY] on QMobile Z8 with BRICKED/DEAD eMMC
I'm a mechanical engineer, not an IT guy. I can fix machines, perhaps, but not bricked phones. So try anything at your own extreme risk. This is NOT a step by step guide. DEVICE: QMobile Z8, same as Wikio Ridge 4G, (MSM8916). Running Android...
forum.xda-developers.com
jjgvv said:
maybe but complicated
Click to expand...
Click to collapse
Okay if you have any idea, let me know.
or this https://forum.xda-developers.com/t/...dor-partition-for-pt-gsi-rom-mi3-mi4.3878995/
this is create vendor but should be possible to create all
HI sorry friend for this this threead but i didnt find any way how to root miaomi 11T miui 12.5.9 root if some know easy kindly tell me Thanks
Every Android OS can get rooted: you simply have to put a suitable SU binary to Android's filesystem - preferably to /data/local/tmp - and make it executable.
xXx yYy said:
Every Android OS can get rooted: you simply have to put a suitable SU binary to Android's filesystem - preferably to /data/local/tmp - and make it executable.
Click to expand...
Click to collapse
i am new in this things kindly can you some more guide of give me that files thanks
Hi
Anyone know how to restore Mix 3 partition?
I followed https://renegade-project.org/#/en/windows/Installation-guide guide to install Window 11 ARM
cp /sdcard/parted /sbin/ && chmod 755 /sbin/parted umount /data && umount /sdcard parted /dev/block/sda rm 17 # remove userdata
mkpart esp fat32 6559MB 7000MB # 441 MB
after removing user data and make esp partition, the console showed some error and I decided to reboot the devices
In the end I can't boot to TWRP anymore and stuck in fastboot
Tried to
Flash TWRP, no partition recovery error
Boot TWRP directly, only ends up in fastboot mode
MiFlash, error misc no such partition
Any help?
Try flashing a stock ROM via Mi flasher.
EDIT: didn't see that you tried that already.
mX87m said:
Try flashing a stock ROM via Mi flasher.
EDIT: didn't see that you tried that already.
Click to expand...
Click to collapse
It's not working and I stuck on fastboot mode
if there is a calm solution I just went through this same problem, only you will have to make a flash by EDL
The problem is that today there are not many EDL accounts, so you will have to support yourself with someone who has a tool to do it on telegram. I met a friend called Angeluss from Spain who gives remote support and helps you for 20 euros, the truth got me out of trouble and I didn't keep a paperweight
lsolis293 said:
The problem is that today there are not many EDL accounts, so you will have to support yourself with someone who has a tool to do it on telegram. I met a friend called Angeluss from Spain who gives remote support and helps you for 20 euros, the truth got me out of trouble and I didn't keep a paperweight
Click to expand...
Click to collapse
Flashed it with authorized account, only need to pay 5$ for some local tech here
codearm2 said:
Flashed it with authorized account, only need to pay 5$ for some local tech here
Click to expand...
Click to collapse
Complete agree with @codearm2
I don't know what to do at this stage. Can anyone explain in more detail?
Spoiler: stage 5
Make a new folder named etc inside root. Make a file named recovery.fstab
Use THIS FILE as a reference point for fstab and edit it.
You Must edit the Mount Addresses (Like /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system), Alternate Short Mount Addresses (Like /dev/block/mmcblk0p20).
You can get Some of the Mount Addresses by ADB Commands from PC, using adb shell cat /proc/self/mountstats or adb shell cat /proc/self/mounts or adb shell cat /proc/self/mountinfo.
Also check whether the Basic FSType (emmc or ext4) of the partitions match with your devices.
If you fail to know the Alternate Short Mount Addresses, Just erase them.
What guide are you using? Provide link.
Provide recovery or boot link
xXx yYy said:
What guide are you using? Provide link.
Click to expand...
Click to collapse
GitHub
kelvinchinedu said:
Provide recovery or boot link
Click to expand...
Click to collapse
I don't understand. Do I upload it here?