Hello to all,
I tried to reflash my P8 Lite to covert from single to double sim, but something went wrong. My device have always the screen black, also when I reboot in bootloader mode. The connection throught fastboot in bootloader mode is available.
I flashed several official rom downloaded from Huwei site, but or the device reboot continuously or the device start but the screen shows only some vertical line (like a vga screen out of frequency).
Via fastboot I tried to erase the partitions but I received always this error: "remote not allowed"
Is this a revertible condition?
Thanks to all.
vertical00 said:
Hello to all,
I tried to reflash my P8 Lite to covert from single to double sim, but something went wrong. My device have always the screen black, also when I reboot in bootloader mode. The connection throught fastboot in bootloader mode is available.
I flashed several official rom downloaded from Huwei site, but or the device reboot continuously or the device start but the screen shows only some vertical line (like a vga screen out of frequency).
Via fastboot I tried to erase the partitions but I received always this error: "remote not allowed"
Is this a revertible condition?
Thanks to all.
Click to expand...
Click to collapse
Haaah, i had the same problem.
staska_lt said:
Haaah, i had the same problem.
Click to expand...
Click to collapse
Have you found any kind of solution?
I executed many research on google, is it possible that the boot logo and the boot animation have been deleted and not restored during the rom flash?
When I flash an Android Rom (system, boot, cust, recovery) all the file on the device are clean or there are other area that are not touched? I saw looking the content of the P8Lite stock image that there are other types of images inside, like (vendor.img, fastboot.img, ecc) but i cannot flash to the device via fastboot.
In these days I tried to restore many stock rom, via fastboot and also via the "local update" but my screen is always black or flickering. The phone is fully functional, the touch is working and I can see the screen making a print screen.
Help me! :crying:
Thank you!
vertical00 said:
Have you found any kind of solution?
I executed many research on google, is it possible that the boot logo and the boot animation have been deleted and not restored during the rom flash?
When I flash an Android Rom (system, boot, cust, recovery) all the file on the device are clean or there are other area that are not touched? I saw looking the content of the P8Lite stock image that there are other types of images inside, like (vendor.img, fastboot.img, ecc) but i cannot flash to the device via fastboot.
In these days I tried to restore many stock rom, via fastboot and also via the "local update" but my screen is always black or flickering. The phone is fully functional, the touch is working and I can see the screen making a print screen.
Help me! :crying:
Thank you!
Click to expand...
Click to collapse
I dont really know how it got fixed, because not me fixed it. How i can remeber he flashed stock recovery, then local update and done.
staska_lt said:
I dont really know how it got fixed, because not me fixed it. How i can remeber he flashed stock recovery, then local update and done.
Click to expand...
Click to collapse
Today I restored the stock rom B133, but nothing changed. The telephone is running with the screen black. With the local update did you restored again the same version of the stock rom?
Do you remember the stock rom version? Was the version installed when you bought the cell?
Thank you.
vertical00 said:
Today I restored the stock rom B133, but nothing changed. The telephone is running with the screen black. With the local update did you restored again the same version of the stock rom?
Do you remember the stock rom version? Was the version installed when you bought the cell?
Thank you.
Click to expand...
Click to collapse
I remember that it was lolipop
Related
Hi all,
A friend of mine, had android 1.6 on his gt540 (donut), he asked me to flash a rom that was better than 1.6 . I started with flashing the repartitioning kdz from mur4ik. It hung after step 212. (normal i presume?) and when I wanted to boot in fast boot, i only got a black screen. and when i booted normally, the screen was stil blank... i flashed several kdz roms, (using normal mode and CS_emergency) it said it was done, but the screen showed nothing...
does anybody know what to do?
any help is really appreciated
hmm so i guess you flashed the repartition kdz before the fastboot kdz??
bs828 said:
hmm so i guess you flashed the repartition kdz before the fastboot kdz??
Click to expand...
Click to collapse
Yes I did.
should I flash the fastboot rom first en then the repartition kdz?
thanks in advance
you only need to use the fastboot kdz, partitioning is not really needed and can be done through fastboot
doesn't work...
i flashed succesfully the v20b kdz,
but the phone won't boot...
i can't get an adb or fastboot connection..
do you have any tips?
Can you default partitions through kdz? If so try that and refresh 2.1 with fastboot it could be a problem with the altered partitions.
Sent from my LG-GT540 using XDA
Highly possible idea as you flashed repartition first so the system does not have enough space for a 2.1 rom
how many minutes did you took to install this ROM?
I wait for almost an hour and still sending system is displayed on the screen. will my phone prone to brick? what shall I do?
as in kdz fastboot rom? for me it took 10 mins not more. i tried on 2 gt540s around the same time. Then again my computer might be faster
jaapstreepjan said:
Hi all,
A friend of mine, had android 1.6 on his gt540 (donut), he asked me to flash a rom that was better than 1.6 . I started with flashing the repartitioning kdz from mur4ik. It hung after step 212. (normal i presume?) and when I wanted to boot in fast boot, i only got a black screen. and when i booted normally, the screen was stil blank... i flashed several kdz roms, (using normal mode and CS_emergency) it said it was done, but the screen showed nothing...
does anybody know what to do?
any help is really appreciated
Click to expand...
Click to collapse
It's a common problem. It's because the kdz files you use to flash the euro rom (or the rom you want).
Just Follow this tutorial: http://android.modaco.com/topic/340693-lg-optimus-gt540-boot-logo-problem/
or this (in spanish):
http://www.taringa.net/posts/celulares/10282298/LG-GT540---Falta-animacion-de-encendido-despues-de-flashear.html
Once you flash that files you need to flash a rom using fastboot a recovery.
Sent from my LG GT540 using xda premium
the problem is with Pepephone spanish carrier, i found a fix
http://www.elgrupoinformatico.com/s...droid-phone-android-con-pepephone-t16852.html
[SOLVED]
hi all, i flash latest paranoid android rom, andorid 4.3 , first thing i notices is the first boot, i stuck on boot logo, and i need to reboot, when phone start , i put sim card pin, and errror appear , com.android.phone stopped, i asking for advice in PA page on g+ , all people say reflash... wipe... i do all thing posible, so i tried to flash other rom, stock rom, and i have one more time the first boot problem, (stuck in boot logo) and then com.andorid.phone ERROR
please i need help what can i do??
orti13 said:
hi all, i flash latest paranoid android rom, andorid 4.3 , first thing i notices is the first boot, i stuck on boot logo, and i need to reboot, when phone start , i put sim card pin, and errror appear , com.android.phone stopped, i asking for advice in PA page on g+ , all people say reflash... wipe... i do all thing posible, so i tried to flash other rom, stock rom, and i have one more time the first boot problem, (stuck in boot logo) and then com.andorid.phone ERROR
please i need help what can i do??
Click to expand...
Click to collapse
Ok i had similar issue with stuck on boot logo. Here is fix. ITS SUPER SIMPLE
1. Go download newest SDK developer dot android dot com/sdk/index.html (New on forums so i can't post links)
2. Unzip sdk and naviagte to sdk/platform-tools
3. Use the fastboot and adb program in this folder to fastboot over your new rom.
For me I was rooted on 4.2.2 AOKP and everytime i flashed rom it would succeded but then fail to boot. Read somewhere on google that using old version of fastboot/adb can cause the issue. Updated and eveything worked flawlessly.
dhruvb14 said:
Ok i had similar issue with stuck on boot logo. Here is fix. ITS SUPER SIMPLE
1. Go download newest SDK developer dot android dot com/sdk/index.html (New on forums so i can't post links)
2. Unzip sdk and naviagte to sdk/platform-tools
3. Use the fastboot and adb program in this folder to fastboot over your new rom.
For me I was rooted on 4.2.2 AOKP and everytime i flashed rom it would succeded but then fail to boot. Read somewhere on google that using old version of fastboot/adb can cause the issue. Updated and eveything worked flawlessly.
Click to expand...
Click to collapse
Thanks i will try , bit my principal problema now is when i flash stock ROM i lost CMW recovery so now i have android 4.3 without root without recovery and with android.phone error ... And i dont know exatcly what to do????
I really need help
orti13 said:
Thanks i will try , bit my principal problema now is when i flash stock ROM i lost CMW recovery so now i have android 4.3 without root without recovery and with android.phone error ... And i dont know exatcly what to do????
I really need help
Click to expand...
Click to collapse
This is easy. Turn on phone with power and vol down buttom pressed. When on the bootloader screen plugin to computer and use fastboot to sideload custom recover.
(./fastboot sideload ziptosideload.zip)
Hello,
I own a Huawei P8 L09, bootloader unlocked, rooted and with TWRP recovery.
I tried this morning to flash a new rom using TWRP recovery.
Problem is that I do believe I wiped to many partitions and I ended up with a bootloop.
I could at first access 3 times the emui erecovery (btw, Wifi recovery failed) but not anymore (is it related to the battery level ? I don't know how much I still have)
Following a lot of threads here and on some other forums (I've been searching now for approx. 7 hours...) :
I downloaded a update stock ROM (B170 something), I extracted Boot, System, Recovery and Cust
I entered bootloader mode (it's the only mode I can go to; recovery No, Download mode neither)
and on my computer I typed in the cmd "fastboot flash recovery recovery.img" same with system, cust and boot.
All of them said "Okay" but the bootloop is still there and I can't acess any other mode or shut the device off.
Also, my bootloader indicate that i'm "unlocked" but when I try to do something as :
"fastboot erase cache" it says "remote: not allowed" or something like that.
I tried the SD card flash method but I can't even acess the 3-button mode (doesn't work - bootloop again).
Finally, I've got 2 questions :
1) Is there a solution ? Is there/was there anybody in the same situation ?
2) Does the battery level influence wether I may or not enter any mode ? like b.e. under 30% I can't access recovery or something like that ?
Thanks in advance for your help and sorry for my bad english.
Greetings from Belgium !
Jules
Hi!
I have the same situation as you do, All i know is that you can access the eRecovery only if you're plugged in.
But it's completely useless. Have you found any solutions yet?
Edit:
i struggled and i'm still struggling but i figured out that I need the recovery and boot img of the version i was on previously. In my case that is B350.
The main mirror is down but i managed to find another one: https://mega.nz/#!NAcgQY7Y!I4eRfkaq62J31csv_wZ8_nTzmUbWPX71JUicDysjus8
after flashing them i was able to partially flash (using vol+-&pwr) B170 (it only went up to 90% with my USB attached, fails without USB)
At my surprise it booted B170 even if it didn't complete, however right now it keeps rebooting every minute. I'll update if i manage to fix this
I have the same problem as you both. To flash boot.img and other files by fastboot we need to unlock bootloader. To unlock bootloader we need to have Imei, Product Id and SN, but I can't read it because phone won't turn on.
Anyone know how to get this info?
you can read these info from the packaging box!
I managed to fix my issues (i believe) by continuously flashing and flashing versions. I never really managed to fully OTA update to 100% due to some "CUST error" but from B350 i managed to "update" to B170, then to B200, then to B321a.
Now i just installed TWRP and rooted it and on the process of installing xposed (if possible).
I wasted a good 6-7 hours on everything already
Well now I actually sent my phone in repair, given that it still was under warranty.
If they return it unrepeared, i will try it your way, Nikooo777. Thanks.
TukAliveFra said:
Well now I actually sent my phone in repair, given that it still was under warranty.
If they return it unrepeared, i will try it your way, Nikooo777. Thanks.
Click to expand...
Click to collapse
you gonna pay for the repair..
Hi all,
I'm hoping someone can shed some light on this problem ..
Background:
- Was running Oxygen OS and went to update it to the new beta, booted into TWRP, flashed the file and rebooted - nothing happened, black screen with a constantly lit blue LED.
- Back into recovery but it didn't ask me for a pattern so it no longer recognised the encrypted partitions.
- Ah well, erased everything a few times and booted back into recovery to flash a new ROM, TWRP loads but no longer responds on the touchscreen, it's stuck at the "swipe to allow modifications to system partition" screen
- booted into fastboot, reflashed TWRP, same deal, Tried all 3 available versions but no difference. Also tried the clockworx build.
- flashed stock recovery and tried to sideload the rom but the first time it bombed out at 48% or so, now it just stops with "Xfer 0.0%" ..
- Saw this thread here https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169 and downloaded it but the MSM tool does not recognise any connected device even though I have "Qualcomm HS-USB QDLoader 9008 COM23" in the device manager
I'm going pretty nuts now so any tips appreciated :/
Cheers
K
Right - quick update - managed to get it re-flashed using the MSM Downloader tool after a lot of trial and error .. if anyone has any questions about the process just let me know!
on my phone TWRP shows no files on in any folder. can you pls help?
krrunch said:
Right - quick update - managed to get it re-flashed using the MSM Downloader tool after a lot of trial and error .. if anyone has any questions about the process just let me know!
Click to expand...
Click to collapse
Hi! I believe that I am in the same boat as you were. On short: was rooted & wanted to stock. Flashed stock recovery & last OS from oneplus site and got stuck in boot. Afterwards I was no longer able to see my device in the stock recovery adb install....
Can you give me a hand please! Thank you!
Edit: Got it to work with the qualcomm method
Hello,
You should install Hydrogen OS to unbrick your phone.
After that install TWRP and then install the full rom OOS 5.0.4.
Hi Everyone,
I have an issue with my Oneplus8 pro and below are the details
1. The device was working perfectly. I was interested to root the device and install a custom ROM.
2. The method used was to try and flash a patched boot image for the device but I think i landed up using a wrong boot image file.
3. The OS was on 10.5.10 if I remember correctly. I used a patched image file I suppose of an older firmware. Now restarts and goes to "QUALCOMM Crashdump mode". The only options are
a. reboot to fastboot mode
b. flash the TWRP for Oneplus 8 pro but that doesnt mount by storage so cant really transfer anything to flash again.
Requesting some help to fix the issue and apologies if i have not explained correctly.
Tried booting a stock boot image?
neverborn said:
Tried booting a stock boot image?
Click to expand...
Click to collapse
Hey,
Thank you for a quick repsonse. Yes, i had tried doing that and still the same error however while we speak, i just downloaded the msmDownloadtool and tried using it to flash a stock firmware and finally, i am so happy to see the device boot sucessfully
Thank you once again for tryin to help
Regards
Hello.
Clarify exactly how the procedure took place