Hello,
I have a Zenfone 2 Laser ( ZE500KL) that remained unused for some months.
Before those months it was running kinda smoothly on Lineage 14 if I can remember
Now, I need the reboot the phone and some problems appear:
First, the boot is stuck on splash screen and I can't access recovery (I can still acess Fastboot)
With fastboot I reinstalled twrp 3.0.2-0 (for ze500kl) and managed to boot on it.
Then I wanted to reinstall a stock rom (or a custom rom, anyway, I want the phone to call send messages)
I tried Lineage 14.1 and two stock roms that are mentionned here https://forum.xda-developers.com/zenfone-2-laser/help/rescue-restore-downgrade-ze500kl-t3657297
Some of them stucked on the progress bar, others failed.
The main problem (I think) is that /system, /cache and /data can't be mounted.
I've tried changing file system to ext2 (and others) and back to ext4 nothing worked.
I've also tried erasing many things with fastboot but I get "Permission denied" when I try something that is not userdata, cache or system
Right now, I'm stuck and don't really know what to do except try again and pray.
If you have some ideas, I'll take
Thank you in advance
EDIT:
For what I understand, I need to redo the partitioning since there seems to be corrupted blocks (and actually I don't really know how to do it )
mobo prblm
Samanuts said:
Hello,
I have a Zenfone 2 Laser ( ZE500KL) that remained unused for some months.
Before those months it was running kinda smoothly on Lineage 14 if I can remember
Now, I need the reboot the phone and some problems appear:
First, the boot is stuck on splash screen and I can't access recovery (I can still acess Fastboot)
With fastboot I reinstalled twrp 3.0.2-0 (for ze500kl) and managed to boot on it.
Then I wanted to reinstall a stock rom (or a custom rom, anyway, I want the phone to call send messages)
I tried Lineage 14.1 and two stock roms that are mentionned here https://forum.xda-developers.com/zenfone-2-laser/help/rescue-restore-downgrade-ze500kl-t3657297
Some of them stucked on the progress bar, others failed.
The main problem (I think) is that /system, /cache and /data can't be mounted.
I've tried changing file system to ext2 (and others) and back to ext4 nothing worked.
I've also tried erasing many things with fastboot but I get "Permission denied" when I try something that is not userdata, cache or system
Right now, I'm stuck and don't really know what to do except try again and pray.
If you have some ideas, I'll take
Thank you in advance
EDIT:
For what I understand, I need to redo the partitioning since there seems to be corrupted blocks (and actually I don't really know how to do it )
Click to expand...
Click to collapse
Looks like u got a faulty motherboard
Phoniex_47 said:
Looks like u got a faulty motherboard
Click to expand...
Click to collapse
Any idea how it happened or how I could fix it ? I used this phone for like 2/3 years before and never had any problem
Related
OK, this mat have been asked many time, but none of the thread I found applies to my case.
My device is Nexus 7 16Gb Wifi, the internal ROM is stock 4.1.2 (I cannot use 4.2.2 because of a backward compatibility issue for an app I have to use)
The recovery is the latest TWRP 20030227 version, with MultiROM bootloader 4.18. An armhf raring build of Ubuntu is also installed in the internal sdcard and all have worked fine until I tried to flash a alternative kernel.
The new kernel I flashed is the M-kernel mr1.1. I flashed it by booting into recovery and chose to install the M-kernels zip file from there. After I have got a kernel flash successful message I chose to reboot system. Then the weird thing began: at first the device seems to be booting because I saw the usual Google logo and then it turned into the boot animation with a colorful cross in the middle of the screen. But then on nothing seems to follow. The boot animation persists forever. I hve also noticed that during the initial boot it somehow skipped the step of choosing ROMs as usual (because I have Ubunto installed), so I also lost the choice of booting into Ubuntu.
I have to press the power button for more than 10 seconds to power off the device. Then I tried to boot into fastboot mode and recovery mode, both works file, so it still looks not bad. I have kept a copy of my working patched kernel which is kernel_kexec_41-2.zip. Booting into recovery and using the command
adb push kernel_kexec_41-2.zip /sdcard/
I managed to copy this zip into the device. Then, once again, I tried to flash this old kernel by installing it in the recovery. The installation exited with a success. However, when I tried to reboot the device, it is still stuck on the boot animation screen. No choose ROM screen either. So, I am totally lost. Can anybody give some hint on where I was doing wrong and how can I get my device working again without totally reflashing a stock rom and loosing all data I have installed previously? Many thanks.
Any helps please.
Let me update the situation. Tried to wipe cache/Dalvik and reflash the kernels (both the original and the newly downloaded omega3 kernel, both changed nothing -- always stuck in the boot animation. Tried MultiROM->Advanced->Inject curr.boot.sector, the screen allowing to choose rom reappeared and from there Ubuntu boots correctly. However, If the internal ROM is chosen in that screen, the device reboots and stuck in the boot animation screen again.
How about if you make a backup?
Then - no matter what follows - no matter what experiments you do - you can always restore just the /data partition. Or any of the other partitions.
Frankly, you should have done it already, but nothing is stopping you from doing it now.
Backups give you power - and freedom - to experiment with very few risks.
good luck.
Thanks! I didn't realize that I can still make a backup even the system is already broken. Did the backup for the data partition and reflashed the stock rom, it now boots ok. Even though I still lost the desktop configuration and the Ubuntu installation.
instanton said:
Thanks! I didn't realize that I can still make a backup even the system is already broken. Did the backup for the data partition and reflashed the stock rom, it now boots ok. Even though I still lost the desktop configuration and the Ubuntu installation.
Click to expand...
Click to collapse
Had it happened that you still had a bootloop after dirty-flashing /system and/or boot (without doing the custom recovery "factory reset" wipe of /data exclusive of /data/media), a backup can still save your bacon: it can be restored and then manually:
- all system app related /data/data/ and /data/app-lib/ folders removed
- all system app updated .apks in /data/app/ deleted
- wipe dalvik-cache
This leaves all market apps and their data intact while starting from scratch from with the base ROM's system apps. Probably doing that reduces the chances of boot loops.
UID mismatch troubles can still occur if you are coming from a "debloated" ROM and dirty-flashing something like a stock ROM (where there are more system apps than in the prior ROM which generated the /data partition); but I think that TWRP's "fix permissions" should take care of that.
But anyway - backups give you flexibility.
hey guys, im back with stupid questions...
I wanted to upgrade my Nexus 7 32gb UMTS to 4.3 and used the Nexus 7 Toolkit (by Mark Skippen).
I was on a custom Rom and wanted to get back to Stock, so i could just use the update process by Google.
Downloading and Installing the ROM (including wipe of user data) by the Toolkit seemed to work and didnt show any error messages.
As is tried to boot my device into Android I got stuck in the bootloader.
When I tried to start it, a small white message "Booting failed" appeared in the top left corner. Nothing else happend.
I did everything again, no changes.
Next step was to google for a few mins, then I tried to install a custom recovery via Toolkit (which worked) and install a zip-file Rom via sideload.
Connection was there, the files got pushed onto the device but then "An Error Occured" popped up and everything stopped.
Installing a zip via usb-otg seemed promising, but this got me errors like "unable to mount /system" and "unable to mount /cache"...
when I tried to reboot from TWRP or ClockwordMod Recovery (tried the earlier described things with both recovieres) I got a message saying
"there is no OS installed, are you sure you want to reboot?"
Please help me, I really dont know how to fix this and I will need my Nexus 7 in 2 days (thats why I tried to reinstall and polish everything )
thanks for your help, I really appreciate it
Edit: tl;dr
Stuck in fastboot, no OS is installed. sideload / installing ROM via ADB / installing ROM via usb-otg doenst work, most certainly because /system and /cache cant be mounted
so AFAIK the real problem is that I cant mount those partitions, otherwise I could install a ROM and get out of fastboot/recovery easily. (just mounting them in custom recoveries didnt work btw)
IchStelleDummeFragen said:
hey guys, im back with stupid questions...
I wanted to upgrade my Nexus 7 32gb UMTS to 4.3 and used the Nexus 7 Toolkit (by Mark Skippen).
I was on a custom Rom and wanted to get back to Stock, so i could just use the update process by Google.
Downloading and Installing the ROM (including wipe of user data) by the Toolkit seemed to work and didnt show any error messages.
As is tried to boot my device into Android I got stuck in the bootloader.
When I tried to start it, a small white message "Booting failed" appeared in the top left corner. Nothing else happend.
I did everything again, no changes.
Next step was to google for a few mins, then I tried to install a custom recovery via Toolkit (which worked) and install a zip-file Rom via sideload.
Connection was there, the files got pushed onto the device but then "An Error Occured" popped up and everything stopped.
Installing a zip via usb-otg seemed promising, but this got me errors like "unable to mount /system" and "unable to mount /cache"...
when I tried to reboot from TWRP or ClockwordMod Recovery (tried the earlier described things with both recovieres) I got a message saying
"there is no OS installed, are you sure you want to reboot?"
Please help me, I really dont know how to fix this and I will need my Nexus 7 in 2 days (thats why I tried to reinstall and polish everything )
thanks for your help, I really appreciate it
Edit: tl;dr
Stuck in fastboot, no OS is installed. sideload / installing ROM via ADB / installing ROM via usb-otg doenst work, most certainly because /system and /cache cant be mounted
so AFAIK the real problem is that I cant mount those partitions, otherwise I could install a ROM and get out of fastboot/recovery easily. (just mounting them in custom recoveries didnt work btw)
Click to expand...
Click to collapse
Well . what you can try for now is download the latest factory images and flash them manually via fastboot .. See how that turns out. You can install any ROM via fastboot .. No issues what so ever.
In the factory images there will be a bootloader IMG.. Flash that first and then flash the remaining images ( I suggest manually or via the .bat or .sh files ) and then see if you can boot up android. Mostly should be possible.
And did you try rebooting inspire of the message " no is installed " appearing on the screen ? Maybe it will boot a ROM ? I remember facing this message after just flashing a rom sometimes. So don't worry.
As long as you have access too fast boot everything can be fixed at least w.r.t software.
Red Devil said:
Well . what you can try for now is download the latest factory images and flash them manually via fastboot .. See how that turns out. You can install any ROM via fastboot .. No issues what so ever.
In the factory images there will be a bootloader IMG.. Flash that first and then flash the remaining images ( I suggest manually or via the .bat or .sh files ) and then see if you can boot up android. Mostly should be possible.
Click to expand...
Click to collapse
It worked!!! Thank you so much.
Still wondering why it didnt flash the factory image as a whole while flashing every part step by step worked perfectly fine...
Red Devil said:
And did you try rebooting inspire of the message " no is installed " appearing on the screen ? Maybe it will boot a ROM ? I remember facing this message after just flashing a rom sometimes. So don't worry.
Click to expand...
Click to collapse
Yes, tried booting, but the device just restarted and returned to fastboot mode.
many thanks again
help plz
this is where I am at as well how do you get out of this. kinda a noob at this so a step by step would be great thanks
ive tried a whole bunch of roms and the behavior seems to be very consistent.
Here's the scenario, same for every rom:
-boot into TWRP, advanced wipe -> wipe everything
-flash rom over adb sideload
-reboot system
-rom comes up just fine the first time, log into google, restore apps
-any time i reboot after, it sits on "Galaxy s4" boot screen, if I then reboot into recovery, TWRP asks for password because it can't mount partitions.
-only way ive found to get out of this is to format data, then reflash.. only until the first reboot again.
stock rom works flawless, the only custom rom that also worked flawless was task650's AOKP 4.2 rom, which was strange but i used it for couple months. now since i i updated to his latest 4.3 release the same issue came up, so i tried again a number of different roms.. no luck
ive exausted my google-fu and these forums, can someone please help... is this a kernel issue? bad hardware? am i just doing something very simple very wrong?
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
jd1639 said:
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
Click to expand...
Click to collapse
same thing, except this time it didnt even boot once, stuck on "galaxy s4" logo, then rebooting back into TWRP prompted a password coz it couldnt mount anything...
i think it gets stuck on boot logo because it cant mount partition same way TWRP cant, but i have no idea why it wouldnt be able to after a reboot or what could be screwing it up
Why don't you try flashing a new recovery?
So, yesterday i tried to install Euphoria OS on my phone, but in all of a sudden, the /cache partition corrupted, i was dumb enough and deleted it via TWRP, making my phone fall into the QPST status.
After fixing it, i proceeded and reflashed KitKat, but the phone only shows 8GB instead of 16GB, so i tried to fix this by flashing TWRP, everything went well, until i upgraded to Lollipop again.
It always bootloops no matter what i do, i really need my phone with my 16GB of storage back, it isn't a Hardware failure since the QPST diagnosis didn't say anything about mobo failures.
I can mount all the partitions, i can wipe it all, i can boot into bootloader and recovery, i can do basically everything but booting the system.
Any light on this? it either happens after i flash TWRP or after i try to root it.
Im running Android 5.1.1 stock.
List of tutorials i have tried (In order): http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289
http://forum.xda-developers.com/nex...unbrick-n4-t2347060/post43164157#post43164157
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Don't you dare tell me to reflash the ROM again, this is the first thing i have done, i did this 20 times already and it never worked. It isn't a ROM problem. It is a partition problem somewhere.
Fixed, had to use LGNPST to reflash JB 4.4.2, then upgraded to a ZIP version of the Lollipop ROM, then flashed the stock one.
I'm having the same problem with my Nexus 4. I read also about LGNPST, but I remember something about flashing the Optimus G cache partition I believe, then manipulating one of the prop files afterwards in order to get your 16gigs back. The problem is that all of the files needed to do this flash are attached to a stupid downloader site and so its full of pop up windows and adware from what I've seen. I can't get mine to boot into system, or bootloader, or recovery, etc. The device will not finish looping for debugging to be enabled, and even trying to boot into download mode is not happening. I've tried all I know to do, especially considering fastboot and adb both utilizeusb debugging. I really am baffled. Any root kits I've tried also don't work so far. Help please.
Hello, this is my first post forgive me if i say something wrong
I have an elephone p7000. I was using it with Aerom (custom rom) then it started showing errors app failures, then i closed phone 3 days ago and it soft bricked. i tried formatting with SP flash tool then flashing some roms including stock roms. Phone never opened always keeped at logo. Then using twrp and Adb command i send rom.zip to my phone and installed it with twrp, after that phone opened but after 10 minutes my phone freaked out. error messages showed up (android stoped working) (system stopped working) or google play stopped working etc. then it soft bricked again. And again data files corrupted. When i tried to wipe data cache calvic unable to mount storage -unable to mount data etc. so i found in another thread (http://forum.xda-developers.com/showthread.php?t=2683787) and used that commands
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
storage fixed then i flashed a stock rom. phone opened but after 30 minutes again system failed android stopped working launcher stopped working google stopped working etc. and now my phone is soft bricked again and when i try to wipe it says unable to mount storage again. So im guessing i must format all things in phone even twrp and install recovery then a stock rom.
i need help what should i do?
Sorry for my bad post english isnt my first language.
anyone to help me ?
is there anybody to help me?
sp flash tool format
helloooooooooo
no one knows how to fix it ? please i really need help im dying for it.
I did format all even recovery with flash tool . then i flashed a new rom.
i opened through twrp flashing 3-4 times but this time android stopped working google stopped working again and went down and bricked phone. please help me what can i do.
Same problem
I have the same problem! Were you able to fix it?