Hi , guys,I have a question , I flashed the AOSP6.0 & cm12.1 or based ROMs ,but all of them can't enter system , always stuck at bootanimaitons , and I did double swip before flash , I can't find the reason , so hope you guys who can help me or give me some advices , thanks so much .
Recovery: TWRP 2.8.7
my device: E975
Is your Recoverymenu working?
yup , recovery is working well , and it can install the ROM successfully
try flashing a kdz, maybe is a partition problem, and for the 6.0 of kevinjoa u have to mount system to flash
so when your recovery is workeing then flash another rom... if this rom is working well then your old rom has some issues...
I flashed aosp 6.0, liquid 5.1.1&mokee 51.1 , all of the ROMs booted up and stuck at bootanimations , only my old ROM can boot into system .
I installed 20b kdz , then root & unlock, flash my current ROM , I don't think the ROM will change the partitions , so I can't understand why the problem happened , maybe I should flash another ROM which can boot into system, then try the new ROMs .
try to flash a stockrom (with download mode)
after that all should be normal and you can unlock your bootloader again and flash custom roms...
yup , I will do it when I have time .
I did this like you said before , the ROM I flashed is based stock's , and I don't think the ROM which will change the important parts of phone . I have flashed a ROM which is based on HongKong's 20b KDZ, and it was edited very little , I flash the custom ROMs later , if it won't work either, I will reinstall the KDZ again.
same issue here...can't boot any custom roms( LP/M)
Maybe you have to re install into a new sistem, can you get into the recovery mode?
Sent from my LG-E975 using XDA Free mobile app
I said Stock ROM not STock Based ROM...
In my oppinion he should flash a Stock Rom with LG FlashTool and Downloadmode or whatever...
Important: STOCK ROM not STOCK BASED...
this should help u http://www.droidviews.com/how-to-install-stock-firmware-on-lg-optimus-g/
Every thing i tried.....flash stock rom using flashtool and did freegee.....still same issue always...none of the LP rom boots up...
hey, guys, I flashed official KDZ , and root , unlock it again , then I installed AOSP ROMs and CM or based on it , my phone can't boot into system either.
then I want to get a log to analysis what caused this , but I don't know which log will be right or better , who knows this , pls help me , I want to taste the MM ROMs .
yes, I get into recovery mode, and I installed several ROMs , but it can't get into system .
Only the ROMs which are based on official KDZ , my phone can boot successfully.
Same on my phone
I flashed official E97520b_00.kdz, root the phone , unlock it too , then I installed various ROMs (5.1.1 /6.01) and CM or based on it with various recoveries, made a full wipe or factory reset with and without system, the result is every time the same ----> phone can't boot in any of this systems and shows only the animated bootlogo. It seems to be a problem of ram size - the system is not correct installed. BUT WHY??????
The recovery log shows in the end "unmount of /system failed; no such volume", the catlog from boot "- exec '/system/bin/sh' failed: No such file or directory (2) -"
HELP NEEDED
The recovery log shows in the end "unmount of /system failed; no such volume", the catlog from boot "- exec '/system/bin/sh' failed: No such file or directory (2) -"
System is by default unmounted in TRWP 2.8.7.0 on my E975.
Try to Mount it manually and check if its working.
Maybe Mount/Unmount and install the Rom again, in case manually Mounting/Unmounting works.
Or reboot into Recovery and follow Kevinjoa's instruction http://forum.xda-developers.com/optimus-g-intl/orig-development/romgeehrcaosp6-009-10-15-t3221743 if you use his Rom.
And sounds clear that "unmount of /system failed; no such volume" if system is not mounted, you cant unmount a non-mounted partition
I flashed the AOSP and followed kevinjoa's step, it still stuck at bootanimation , and the recovery notice" unmount of /system failed; no such volume" still there . So bad
hey , guys , I have a good news for you , I have flashed the current RR 6.0.1 ROM on my devices successfully , the only thing I changed is the official kdz--NEU/EUROPE OPEN 20A kdz , here is the site : http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW108106432109876543213/E97520A_00.kdz
the system section is 2G after flash this kdz , so maybe you should have a try , hope this will help you .
thanks M.M.K give the kdz again
Hi people.
I'm in the process of flashing my friend's Samsung Galaxy S4 Mini LTE.
Here's some details:
TWRP version: 2.6.3.0 (The one some dude here made himself)
ROM: cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx
SuperSU installed
Rooted using CM AUTO ROOT
Used Odin 3.09 to install TWRP
Everything is working fine but i'm having an issue flashing GAPPS.
9195 has a Krait 300 - which is an ARM processor so i downloaded the ARM 6.0 Micro package from OpenGapps.
Wiped all partitions, queued up the ROM and GAPPS in TWRP and flashed.
The process goes by fast and smooth, but the phone doesn't boot up after that.
The first time it took 25 or so minutes to boot up and ALL the GAPPS crashed after that.
What should i do?
I tried the following alternatives as well:
Bliss-v6.3-serranoltexx-UNOFFICIAL-20160521-1003
Slim_mini_gapps.BETA.6.0.build.0.x-20160516-2250
benzo-gapps-M-20151011-signed-chroma-r3
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
noppy22 said:
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
Click to expand...
Click to collapse
This worked!
I thought the old TWRP version was the only version compatible with the SGS4Mini.
I'm a Newb sure, but fairly sure this isn't my fault....
Hello, I have spent the past 2 days working on this flash you've stated as well and I can't understand for the life of me what I am doing wrong. You mentioned that TWRP may not have supported the mini but it seems that it does - odin just isn't installing it right? I am hoping people on here have already hashed this out on both ODIN and TWRP for this device and after spending 24 hours figuring this out i'm wondering if it's just some stupid thing i'm doing wrong. I've put the full stuff below which you may largely be able to ignore but what i need to figure out is how to install TWRP 3.0 or higher on my device, and how to keep ODIN from crashing. Can you help?
1. where I started and my goal:
My homestay mother in New Zealand who works for the tech firm Datacom provided me with a Galaxy S4 mini (GT-I9195 spark edition) that she had left over because she got a new phone for her work. I had a galaxy note 2 running default controls due to its setup on KNOXED up verizon, so i thought this was a good opportunity to switch to cyanogen since i've used the service before (someone else went through all this trouble for me and I am eternally grateful). So I am trying to install Cyanogen mod 13 with GAPPS package nano on to it.
2. The file repretoires and guides I used:
TWRP 2.8.1 (originally) and it's accompanied manager
Trying to upgrade to TWRP 3.0.2.0 or 3.1.0
GAPPS arm 6.0 mini/nano/pico (I've tried all three)
Odin 3.12.3 with requisite drivers (shows blue on status bar)
Default Bootloader for Android devices
CMD ADB systems with requisite drivers
CyanogenMod 13 (cm-13.0-20160820-ZNH5YAO0J7) (currently installed and working san-GAPPs)
3. What I've done Start to current:
starting with the phone locked, unrooted, and factory resets not working (company KNOX settings)
Installed Kingroot, superSU, RootChecker, TWRP manager and official ap, P-uninstall = Obtained Root
Attained root on the phone, deleted all KNOX and KGNT protection. = obtained unlocked sim/recovery loader
Installed TWRP 2.8.6 (any more recent installs failed as I will explain below in problems) Attempted to flash it = read success
Failed to boot into TWRP recovery - provided default recovery instead.
downloaded and installed ODIN. Used default boot loader and attempted to install TWRP directly through ODIN = Works
placed CM13 zip file and GAPPS 6.0 - ARMS Nano on SD card.
Created recovery on SD card
Wiped cash, devalk cache, and internal storage = clean partition
Installed BOTH CM13 and GAPPs 6.0 as zip files using TWRP 2.8.6 = worked
rebooted system into new OS
OS got stuck in boot cycle due to GAPPs package. after some googling i found out that Gapps requires TWRP 3.02 or higher (but i couldn't get those to download onto my phone at all. [here enlies the ROOT of my problem - you're allowed to kill me now]
Returned to TWRP and installed JUST CM13 on the device = works great! just no GAPPs! and no ability to download apps
Used Odin, TWRP manager, the official TWRP app, and CMD ADB sideloader to attempt to install all 3.0 and higher TWRP files = all of them failed
now I cannot access a bootloader at all, but can access my OS just fine. It refuses to accept any TWRP bootloaders but without them i cannot install GAPPS
4. Where I am Currently & Problems I'm running in to:
Right now CM13 is on and stable for my device. My Recovery loader is refusing to come up AT ALL. Attempting to install both .img and .tar files of TWRP read as succeeding in the apps but don't come up.
ODIN can't load anything on the device. Either it keeps freezing and crashing any time I touch it or when it does go through the device still can't bring up TWRP. Even when flashing 2.8.6 which originally worked as a recovery file it fails as well. I can't get back to TWRP working at all.
ADB sideloading just results in <waiting for device>. I am clearly using "fastboot" instead of ADB during the point in which i am flashing the recovery file on to it.
5. What I need Help with:
I need to know why TWRP is freezing any time i attempt to install it regardless of version and how to get it properly installed
if someone could point me to a reason odin freezes regardless of what options I tick on or off, file I upload, or whatever i'd love to know
I see 2 ways out of my predicament and i'm not sure which one I should spend more time on: 1) get TWRP 2.8.6 to work again and then find an older GAPP partition to load on to it. or 2) Get TWRP 3.0 or greater to work on it, and then use current GAPP packages. which would be best?
Hello,
it looks like that I'm unable to install a custom rom on my GX8 (see details out device at the end of the post).
FRP disabled, bootloader unlocked (this is at least what the fastboot/bootloader screen is saying)
I'm able to flash twrp-3.1.1-0-rio.img to recovery
I can use twrp on recovery and it seems to be fully functional
When I use twrp in 'read-only' mode, I'm able to reboot the system (stock firmware)
But when I use twrp in modifing mode, booting the system (stock firmware) is no longer possible (even if I only wipe cache and/or dalvik). Restarting the device will always end in twrp/recovery.
Backup is possible. Restore backup succeeds, but booting the system (stock firmware) is not possible. Restarting the device will always end in twrp/recovery.
Nevertheless trying to install a custom rom from zip in twrp. This leads to the following error message:
"E3004: This package is for device: RIO-L01, hwRIO-L01, RIO-L02, hwRIO-L02, RIO-L03, hwRIO-L03, RIO-AL00, hwRiO-AL00, RIO-CL00, hwRIO-CL00, RIO-TL00, hwRIO-TL00; this device is rio.
Updater process ended with ERROR: 7"
Well, patch the custom rom in lines of http://www.lineageosdownloads.com/fix-error-7-lineage-os/, i.e. modifing the 'updater-script' in the zip. Now installing the custom rom zip in twrp is possible. Still unable to reboot system.
Installing gapps and/or chainfire supersu does not improve the situation.
Giving up back to stock rom in lines of https://forum.xda-developers.com/gx...tall-stock-rom-g8-t3370013/page2#post73008458 . This has (so far) worked for me to get back a working mobile phone.
Any suggestions, anyone?
Kind regards,
aanno
PS:
device:
Prod
HUAWEI RIO-L01
Serial
MUYDU16122xxxxxx
IMEI
867115027xxxxxx
Prod Id
2983xxxx
Unlock
9725092227xxxxxx
stock firmware used:
EMUI 4.0
Build
RIO-L01C432B340
Android
6.0.1
Kernel
3.10.49-g06216b3
Custom
CUSTC432D001
I've encountered the same exact problem when I flashed using twrp-3.1.1-0-rio.img. Had to force update to stock rom after it got stuck on bootloop.
Solved it when using the older TWRP 3.0.2-0 which you can get here:
https://forum.xda-developers.com/gx8/development/huawei-g8-gx8-t3324538
Hope it might help you too.
hey guys, I bought this huawei g8 (RIO-AL00) in China about a year ago. recently, i felt huawei stock 5.1.1 rom is suck, so i want to change to stock Android. i unlocked my bootloader, then flush twrp official 3.1.1 and wiped system, cache and data. but when i try to flash official aosp extended, an error occurred: Error 7, your device is not RIO-AL00,RIO-AL01,RIO-AL03 balabala…this device is rio.
i spent more than one day to fix my phone, but it has little effect. somebody said an unofficial twrp 3.0.2 in XDA can fix this error, but there also had an error why i user it to flash rom. the error say my device's…maybe firmware is balabala B22, but flash rom need B35 balabala…
i think that error is because i'm not came from huawei stock 6.0.1 but 5.1.1
anyone can help? thx!
Find the needed firmware (even if it's a different region one ) , use huawei update extractor , flash system. IMG, boot.IMG, cust.IMG via fastboot
Just a quick note regarding cust.IMG , you need to convert it to ext4 format and flash it using the DD command , after doing all of that you are able to flash aosp extended